2.6.19-rc5: grub is much slower resuming from suspend-to-disk than in 2.6.18
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
This is rather funny; in 2.6.19-rc5 grub is *really* slow loading kernel when I switch on the system after suspend to disk. Actually, after kernel has been loaded, the whole resuming (up to the point I have usable desktop again) takes about three time less than the process of loading kernel + initrd. During loading disk LED is constantly lit. This almost looks like kernel leaves HDD in some strange state, although I always assumed HDD/IDE is completely reinitialized in this case.
Some data:
{pts/0}% grub --version
grub (GNU GRUB 0.97)
{pts/0}% LC_ALL=C ls -l /boot/*2.6.19*
- -rw-r--r-- 1 root root 679116 Nov 11 13:29 /boot/System.map-2.6.19-rc5-1avb
- -rw-r--r-- 1 root root 49252 Nov 11 13:29 /boot/config-2.6.19-rc5-1avb
- -rw-r--r-- 1 root root 692341 Nov 11 13:29 /boot/initrd-2.6.19-rc5-1avb.img
- -rw-r--r-- 1 root root 1493 Nov 11 14:18 /boot/kernel.h-2.6.19-rc5-1avb
- -rw-r--r-- 1 root root 1460690 Nov 11 13:29 /boot/vmlinuz-2.6.19-rc5-1avb
dmesg:
Linux version 2.6.19-rc5-1avb (bor@cooker) (gcc version 4.1.1 20060724 (prerelease) (4.1.1-3mdk)) #1 Sat Nov 11 13:02:51 MSK 2006 BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000e0000 - 00000000000eee00 (reserved)
BIOS-e820: 00000000000eee00 - 00000000000ef000 (ACPI NVS)
BIOS-e820: 00000000000ef000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000001ef60000 (usable)
BIOS-e820: 000000001ef60000 - 000000001ef70000 (ACPI data)
BIOS-e820: 000000001ef70000 - 0000000020000000 (reserved)
BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
495MB LOWMEM available.
Entering add_active_range(0, 0, 126816) 0 entries of 256 used Zone PFN ranges:
DMA 0 -> 4096
Normal 4096 -> 126816
early_node_map[1] active PFN ranges
0: 0 -> 126816
On node 0 totalpages: 126816
DMA zone: 32 pages used for memmap
DMA zone: 0 pages reserved
DMA zone: 4064 pages, LIFO batch:0
Normal zone: 958 pages used for memmap
Normal zone: 121762 pages, LIFO batch:31
DMI 2.3 present.
ACPI: RSDP (v000 TOSHIB ) @ 0x000f0090
ACPI: RSDT (v001 TOSHIB 750 0x00970814 TASM 0x04010000) @ 0x1ef60000
ACPI: FADT (v002 TOSHIB 750 0x00970814 TASM 0x04010000) @ 0x1ef60054
ACPI: DSDT (v001 TOSHIB 4000 0x20020417 MSFT 0x0100000a) @ 0x00000000
ACPI: PM-Timer IO Port: 0xee08
Allocating PCI resources starting at 30000000 (gap: 20000000:dff80000) Detected 747.678 MHz processor.
Built 1 zonelists. Total pages: 125826
Kernel command line: root=/dev/hda2 BOOT_IMAGE=2.6.19-rc5-1avb hdc=ide-cd resume=/dev/hda1 splash=silent vga=791
Local APIC disabled by BIOS -- you can enable it with "lapic" mapped APIC to ffffd000 (013f8000)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0
PID hash table entries: 2048 (order: 11, 8192 bytes)
Console: colour dummy device 80x25
Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar
... MAX_LOCKDEP_SUBCLASSES: 8
... MAX_LOCK_DEPTH: 30
... MAX_LOCKDEP_KEYS: 2048
... CLASSHASH_SIZE: 1024
... MAX_LOCKDEP_ENTRIES: 8192 ... MAX_LOCKDEP_CHAINS: 8192 ... CHAINHASH_SIZE: 4096
memory used by lock dependency info: 904 kB
per task-struct memory footprint: 1200 bytes
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 496600k/507264k available (1710k kernel code, 10180k reserved, 744k data, 188k init, 0k highmem)
virtual kernel memory layout:
fixmap : 0xfffb7000 - 0xfffff000 ( 288 kB)
vmalloc : 0xdf800000 - 0xfffb5000 ( 519 MB)
lowmem : 0xc0000000 - 0xdef60000 ( 495 MB)
.init : 0xc03aa000 - 0xc03d9000 ( 188 kB)
.data : 0xc02abb87 - 0xc0365c94 ( 744 kB)
.text : 0xc0100000 - 0xc02abb87 (1710 kB)Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 1497.01 BogoMIPS (lpj=748508) Mount-cache hash table entries: 512
CPU: After generic identify, caps: 0387f9ff 00000000 00000000 00000000 00000000 00000000 00000000
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 256K
CPU serial number disabled.
CPU: After all inits, caps: 0383f9ff 00000000 00000000 00000040 00000000 00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: Intel Pentium III (Coppermine) stepping 0a
Checking 'hlt' instruction... OK.
ACPI: Core revision 20060707
ACPI: setting ELCR to 0200 (from 0a00)
checking if image is initramfs... it is
Freeing initrd memory: 676k freed
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xfe5ae, last bus=5
PCI: Using configuration type 1
Setting up standard PCI resources
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
ACPI: Assume root bridge [\_SB_.PCI0] bus is 0
PCI quirk: region ee00-ee3f claimed by ali7101 ACPI
PCI quirk: region ef00-ef1f claimed by ali7101 SMB
PCI: Firmware left 0000:00:0a.0 e100 interrupts enabled, disabling Boot video device is 0000:01:00.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 *11)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 10 *11)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 *11)
ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 *11)
ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 *11)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI1._PRT]
ACPI: Power Resource [PFAN] (off)
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
pnp: PnP ACPI: found 12 devices
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
PCI: Bridge: 0000:00:01.0
IO window: disabled.
MEM window: f7f00000-fdffffff
PREFETCH window: 3c000000-3c0fffff
PCI: Bus 2, cardbus bridge: 0000:00:10.0
IO window: 00001000-000010ff
IO window: 00001400-000014ff
PREFETCH window: 30000000-31ffffff
MEM window: 32000000-33ffffff
PCI: Bus 6, cardbus bridge: 0000:00:11.0
IO window: 00001800-000018ff
IO window: 00001c00-00001cff
PREFETCH window: 34000000-35ffffff
MEM window: 36000000-37ffffff
PCI: Bus 10, cardbus bridge: 0000:00:11.1
IO window: 00002000-000020ff
IO window: 00002400-000024ff
PREFETCH window: 38000000-39ffffff
MEM window: 3a000000-3bffffff
PCI: Setting latency timer of device 0000:00:01.0 to 64
PCI: Enabling device 0000:00:10.0 (0000 -> 0003)
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
PCI: setting IRQ 11 as level-triggered
ACPI: PCI Interrupt 0000:00:10.0[A] -> Link [LNKC] -> GSI 11 (level, low) -> IRQ 11
PCI: Enabling device 0000:00:11.0 (0000 -> 0003)
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11
ACPI: PCI Interrupt 0000:00:11.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
PCI: Enabling device 0000:00:11.1 (0000 -> 0003)
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 11
ACPI: PCI Interrupt 0000:00:11.1[B] -> Link [LNKB] -> GSI 11 (level, low) -> IRQ 11
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes) TCP established hash table entries: 16384 (order: 7, 655360 bytes) TCP bind hash table entries: 8192 (order: 6, 360448 bytes)
TCP: Hash tables configured (established 16384 bind 8192)
TCP reno registered
audit: initializing netlink socket (disabled) audit(1163305574.813:1): initialized
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Activating ISA DMA hang workarounds.
vesafb: framebuffer at 0xfc000000, mapped to 0xdf880000, using 3072k, total 16384k
vesafb: mode is 1024x768x16, linelength=2048, pages=9
vesafb: protected mode interface info at c000:775e
vesafb: pmi: set display start = c00c777f, set palette = c00c77e2
vesafb: scrolling: redraw
vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0
Console: switching to colour frame buffer device 128x48
fb0: VESA VGA frame buffer device
Real Time Clock Driver v1.12ac
RAMDISK driver initialized: 16 RAM disks of 32000K size 1024 blocksize
NET: Registered protocol family 1
Using IPI Shortcut mode
Time: tsc clocksource has been installed.
ACPI: (supports S0 S3 S4 S5)
BIOS EDD facility v0.16 2004-Jun-25, 1 devices found
Freeing unused kernel memory: 188k freed
Write protecting the kernel read-only data: 269k
PNP: PS/2 Controller [PNP0303:KBC,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
input: AT Translated Set 2 keyboard as /class/input/input0 Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ALI15X3: IDE controller at PCI slot 0000:00:04.0
ACPI: Unable to derive IRQ for device 0000:00:04.0
ACPI: PCI Interrupt 0000:00:04.0[A]: no GSI
ALI15X3: chipset revision 195
ALI15X3: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xeff0-0xeff7, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xeff8-0xefff, BIOS settings: hdc:DMA, hdd:pioProbing IDE interface ide0...
hda: IC25N020ATDA04-0, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: TOSHIBA DVD-ROM SD-C2502, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 128KiB
hda: 39070080 sectors (20003 MB) w/1806KiB Cache, CHS=38760/16/63, UDMA(33)
hda: cache flushes not supported
hda: hda1 hda2
ReiserFS: hda2: found reiserfs format "3.6" with standard journal
ReiserFS: hda2: using ordered data mode
ReiserFS: hda2: journal params: device hda2, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: hda2: checking transaction log (hda2)
ReiserFS: hda2: Using r5 hash to sort names
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usbohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
ACPI: PCI Interrupt Link [LNKG] enabled at IRQ 11
ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [LNKG] -> GSI 11 (level, low) -> IRQ 11ohci_hcd 0000:00:02.0: OHCI Host Controllerohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 1 ohci_hcd 0000:00:02.0: irq 11, io mem 0xf7eff000
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 3 ports detected
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Detected ALi M1644 chipset
agpgart: AGP aperture is 64M @ 0xf0000000
Yenta: CardBus bridge found at 0000:00:10.0 [12a3:ab01]
Yenta: Enabling burst memory read transactions
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:00:10.0, mfunc 0x01000002, devctl 0x60
input: ImPS/2 Generic Wheel Mouse as /class/input/input1
mice: PS/2 mouse device common for all mice
Yenta: ISA IRQ mask 0x0000, PCI irq 11
Socket status: 30000011
Yenta: CardBus bridge found at 0000:00:11.0 [1179:0001]
Yenta: ISA IRQ mask 0x04b8, PCI irq 11
Socket status: 30000007
Yenta: CardBus bridge found at 0000:00:11.1 [1179:0001]
Yenta: ISA IRQ mask 0x04b8, PCI irq 11
Socket status: 30000007
pccard: PCMCIA card inserted into slot 0
cs: memory probe 0x0c0000-0x0fffff: excluding 0xc0000-0xcbfff 0xe0000-0xfffff
cs: memory probe 0x60000000-0x60ffffff: clean.
cs: memory probe 0xa0000000-0xa0ffffff: clean.
pcmcia: registering new device pcmcia0.0
ACPI: AC Adapter [ADP1] (on-line)
ACPI: Battery Slot [BAT1] (battery present)
ACPI: Battery Slot [BAT2] (battery absent)
ACPI: Power Button (FF) [PWRF]
ACPI: Lid Switch [LID]
ACPI: Transitioning device [FAN] to D3
ACPI: Transitioning device [FAN] to D3
ACPI: Fan [FAN] (off)
ACPI: CPU0 (power states: C1[C1] C2[C2])
ACPI: Thermal Zone [THRM] (29 C)
Time: acpi_pm clocksource has been installed.wlags49_h1_cs v7.18 for PCMCIA, 03/31/2004 14:31:00 by Agere Systems,
http://www.agere.com
*** Modified for kernel 2.6 by Andrey Borzenkov <[email protected]> $Revision:
27 $
*** Station Mode (STA) Support: YES
*** Access Point Mode (AP) Support: YES
eth0: PRI 31 variant 2 version 9.48
eth0: NIC 5 variant 2 version 1.02
eth0: Wireless, io_addr 0x100, irq 11, mac_address 00:02:2D:26:95:6Ctoshiba_acpi: Toshiba Laptop ACPI Extras version 0.18toshiba_acpi: HCI method: \_SB_.VALD.GHCI
ACPI: Video Device [VGA] (multi-head: yes rom: yes post: no)
device-mapper: ioctl: 4.10.0-ioctl (2006-09-14) initialised:
[email protected]
loop: loaded (max 8 devices)
Adding 500432k swap on /dev/hda1. Priority:-1 extents:1 across:500432k
hdc: ATAPI 24X DVD-ROM drive, 128kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFVwdOR6LMutpd94wRAoAzAKCgTTMhOc6N/Qh6dFzaTd4SdshnfQCdGOc1 de5dPLCYihMrnq8XrMQmQ6I=
=Pl3J
-----END PGP SIGNATURE-----
Hi,
Quoted 7 lines · Andrey Borzenkov
This is rather funny; in 2.6.19-rc5 grub is *really* slow loading kernel when I switch on the system after suspend to disk. Actually, after kernel has been loaded, the whole resuming (up to the point I have usable desktop again) takes about three time less than the process of loading kernel + initrd. During loading disk LED is constantly lit. This almost looks like kernel leaves HDD in some strange state, although I always assumed HDD/IDE is completely reinitialized in this case.
Can you please see what's in the /sys/power/disk file?
Rafael
Signature · 2 lines
You never change things by fighting the existing reality. R. Buckminster Fuller
Quoted 8 lines
Quoted 8 lines
This is rather funny; in 2.6.19-rc5 grub is *really* slow loading kernel when I switch on the system after suspend to disk. Actually, after kernel has been loaded, the whole resuming (up to the point I have usable desktop again) takes about three time less than the process of loading kernel + initrd. During loading disk LED is constantly lit. This almost looks like kernel leaves HDD in some strange state, although I always assumed HDD/IDE is completely reinitialized in this case.
Constant LED, it might be the regular DMA culprit. Just a guess, however.
-`J'
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Quoted 11 lines · Rafael J. Wysocki
Hi,
Quoted 7 lines · Andrey Borzenkov
This is rather funny; in 2.6.19-rc5 grub is *really* slow loading kernel when I switch on the system after suspend to disk. Actually, after kernel has been loaded, the whole resuming (up to the point I have usable desktop again) takes about three time less than the process of loading kernel + initrd. During loading disk LED is constantly lit. This almost looks like kernel leaves HDD in some strange state, although I always assumed HDD/IDE is completely reinitialized in this case.
Quoted 2 lines
Can you please see what's in the
/sys/power/diskfile?
{pts/0}% cat /sys/power/disk
shutdown
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFVxe1R6LMutpd94wRAgJvAKCMszsHKt2e7uN4h5SHBj7rixFTWgCffGis 2prTVMIdmr6ny1ORFTjO0GQ=
=sZ2j
-----END PGP SIGNATURE-----
Quoted 12 lines · Andrey Borzenkov
Quoted 11 lines · Rafael J. Wysocki
Hi,
Quoted 7 lines · Andrey Borzenkov
This is rather funny; in 2.6.19-rc5 grub is *really* slow loading kernel when I switch on the system after suspend to disk. Actually, after kernel has been loaded, the whole resuming (up to the point I have usable desktop again) takes about three time less than the process of loading kernel + initrd. During loading disk LED is constantly lit. This almost looks like kernel leaves HDD in some strange state, although I always assumed HDD/IDE is completely reinitialized in this case.
Quoted 5 lines
Quoted 2 lines
Can you please see what's in the
/sys/power/diskfile?{pts/0}% cat
/sys/power/disk
shutdown
Can you please write "platform" to this file before the suspend and see if anything changes?
Rafael
Signature · 2 lines
You never change things by fighting the existing reality. R. Buckminster Fuller
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Quoted 14 lines · Rafael J. Wysocki
Quoted 13 lines · Andrey Borzenkov
Quoted 12 lines · Rafael J. Wysocki
Hi,
Quoted 8 lines · Andrey Borzenkov
This is rather funny; in 2.6.19-rc5 grub is *really* slow loading kernel when I switch on the system after suspend to disk. Actually, after kernel has been loaded, the whole resuming (up to the point I have usable desktop again) takes about three time less than the process of loading kernel + initrd. During loading disk LED is constantly lit. This almost looks like kernel leaves HDD in some strange state, although I always assumed HDD/IDE is completely reinitialized in this case.
Quoted 8 lines
Quoted 4 lines
Quoted 1 line
Can you please see what's in the
/sys/power/diskfile?{pts/0}% cat
/sys/power/disk
shutdownCan you please write "platform" to this file before the suspend and see if anything changes?
No, nothing changes.
I tested a bit more; I currently have 2.6.18.1, 2.6.18.2 and 2.6.19-rc5 installed. Booting after "poweroff" is OK from within all versions - there is no delay. Resuming after suspend under 2.6.18.x is mostly OK, at least it is much less obvious (I had some feeling it may have been "a bit slower" under 2.6.18.2 but may be it is just illusion). Resuming after suspend under 2.6.19-rc5 results in noticeable delay and constantly busy HDD LED during grub phase.
Yes, it is notebook. I will test Pavel's suggestion later.
regards
- -andrey
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFV3J3R6LMutpd94wRAjBoAJ9UBc0KXM4/8ANCwUn17gbHrhTKawCgiJjg qdsJw+JV4LLL4mP5hz+NYVI=
=Y1of
-----END PGP SIGNATURE-----
Quoted 10 lines · Andrey Borzenkov
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1This is rather funny; in 2.6.19-rc5 grub is *really* slow loading kernel when I switch on the system after suspend to disk. Actually, after kernel has been loaded, the whole resuming (up to the point I have usable desktop again) takes about three time less than the process of loading kernel + initrd. During loading disk LED is constantly lit. This almost looks like kernel leaves HDD in some strange state, although I always assumed HDD/IDE is completely reinitialized in this case.
Seems like broken hw, really. No state should survive machine poweroff.
Is it notebook?
Can you try to unplug system for a few minutes / unplug battery if notebook to see if it helps?
Pavel
Signature · 1 line
Thanks for all the (sleeping) penguins.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Quoted 12 lines · Pavel Machek
Quoted 10 lines · Andrey Borzenkov
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1This is rather funny; in 2.6.19-rc5 grub is *really* slow loading kernel when I switch on the system after suspend to disk. Actually, after kernel has been loaded, the whole resuming (up to the point I have usable desktop again) takes about three time less than the process of loading kernel + initrd. During loading disk LED is constantly lit. This almost looks like kernel leaves HDD in some strange state, although I always assumed HDD/IDE is completely reinitialized in this case.
Quoted 3 lines
Seems like broken hw, really. No state should survive machine poweroff.
Well, we do have NVRAM do not we?
Quoted 2 lines
Is it notebook?
Yes.
Quoted 2 lines
Can you try to unplug system for a few minutes / unplug battery if notebook to see if it helps?
No. I unplugged power, removed battery and left it over night. Today morning it has shown exactly the same behavior upon resuming (well, upon power-on after suspend to disk :))
To recap - this never happens upon simple power off; I do not remember this to happen upon suspend to disk until 2.6.19 (I won't claim it never happened, just that I do not remember it). This happens consistently in 2.6.19-rc5. I am very curious which hardware issue may have such pattern. And in any case this does smell like regression (earlier version not triggering this HW issue if any)
- -andrey
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFV+maR6LMutpd94wRAmhxAKDCZvzoUtqQguQL1+WmdT/wi3Y3RACgnXep ra/Qr0wUO43MTAZB2qGWiS0=
=pICz
-----END PGP SIGNATURE-----
Hi,
Quoted 8 lines · Andrey Borzenkov
Quoted 7 lines · Pavel Machek
Quoted 6 lines · Andrey Borzenkov
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1This is rather funny; in 2.6.19-rc5 grub is *really* slow loading kernel when I switch on the system after suspend to disk. Actually, after kernel has been loaded, the whole resuming (up to the point I have usable
The most important question:
What filesystem is your /boot on? I'd bet quite some money that it is reiser or some other journaling FS (not ext3).
Quoted 7 lines
Quoted 7 lines
Quoted 4 lines
desktop again) takes about three time less than the process of loading kernel + initrd. During loading disk LED is constantly lit. This almost looks like kernel leaves HDD in some strange state, although I always assumed HDD/IDE is completely reinitialized in this case.
Seems like broken hw, really. No state should survive machine poweroff.
No. Broken FS / crappy GRUB.
Quoted 1 line
To recap - this never happens upon simple power off; I do not remember this to
I am pretty sure that it will also happen if you do "updatedb &", wait a minute and then do a _HARD_ power off.
I am pretty sure that it has nothing to do with the kernel version, just with the layout of your /boot partition (which of course changes with every kernel update). In other words: until now, you just have been lucky.
Signature · 3 lines
Stefan Seyfried QA / R&D Team Mobile Devices | "Any ideas, John?" SUSE LINUX Products GmbH, Nürnberg | "Well, surrounding them's out."
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Quoted 8 lines · Stefan Seyfried
Hi,
Quoted 5 lines · Andrey Borzenkov
Quoted 4 lines · Pavel Machek
Quoted 3 lines · Andrey Borzenkov
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Quoted 9 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
This is rather funny; in 2.6.19-rc5 grub is *really* slow loading kernel when I switch on the system after suspend to disk. Actually, after kernel has been loaded, the whole resuming (up to the point I have usable
The most important question:
What filesystem is your /boot on? I'd bet quite some money that it is reiser or some other journaling FS (not ext3).
there is no /boot, I use single / which is reiser.
Quoted 14 lines
Quoted 8 lines
Quoted 8 lines
Quoted 5 lines
desktop again) takes about three time less than the process of loading kernel + initrd. During loading disk LED is constantly lit. This almost looks like kernel leaves HDD in some strange state, although I always assumed HDD/IDE is completely reinitialized in this case.
Seems like broken hw, really. No state should survive machine poweroff.
No. Broken FS / crappy GRUB.
Quoted 2 lines
To recap - this never happens upon simple power off; I do not remember this to
Quoted 6 lines
I am pretty sure that it will also happen if you do "updatedb &", wait a minute and then do a _HARD_ power off.
I am pretty sure that it has nothing to do with the kernel version, just with the layout of your /boot partition (which of course changes with every kernel update). In other words: until now, you just have been lucky.
The idea is nice; unfortunately it fails to explain the difference between 'poweroff' and 'suspend disk' cases. I doubt disk layout is changed between them.
regards
- -andrey
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFWL9uR6LMutpd94wRAh0NAJ4o2hU4E/BsMOJXPxqX8OSH8OR/nwCfdLPz DWHM1gAFYTvc9WtyNv+qq08=
=EaDe
-----END PGP SIGNATURE-----
Quoted 41 lines · Andrey Borzenkov
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1Quoted 8 lines · Stefan Seyfried
Hi,
Quoted 5 lines · Andrey Borzenkov
Quoted 4 lines · Pavel Machek
Quoted 3 lines · Andrey Borzenkov
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1Quoted 9 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
This is rather funny; in 2.6.19-rc5 grub is *really* slow loading kernel when I switch on the system after suspend to disk. Actually, after kernel has been loaded, the whole resuming (up to the point I have usable
The most important question:
What filesystem is your /boot on? I'd bet quite some money that it is reiser or some other journaling FS (not ext3).there is no /boot, I use single / which is reiser.
Quoted 17 lines
Quoted 8 lines
Quoted 8 lines
Quoted 5 lines
desktop again) takes about three time less than the process of loading kernel + initrd. During loading disk LED is constantly lit. This almost looks like kernel leaves HDD in some strange state, although I always assumed HDD/IDE is completely reinitialized in this case.
Seems like broken hw, really. No state should survive machine poweroff.
No. Broken FS / crappy GRUB.
Quoted 2 lines
To recap - this never happens upon simple power off; I do not remember this to
I am pretty sure that it will also happen if you do "updatedb &", wait a minute and then do a _HARD_ power off.
Quoted 7 lines
Quoted 3 lines
I am pretty sure that it has nothing to do with the kernel version, just with the layout of your /boot partition (which of course changes with every kernel update). In other words: until now, you just have been lucky.
The idea is nice; unfortunately it fails to explain the difference between 'poweroff' and 'suspend disk' cases. I doubt disk layout is changed between them.
I have not checked if this is true, but it is a possible explanation:
Perhaps the filesystem is not properly unmounted during a suspend? That would mean GRUB is reading from a incoherent filesystem on resume. GRUB's filesystem drivers are not very fancy. It could be it does something silly like check the journal before returning each block.
Maybe its a journal size thing, you could try "sync" before suspend and see if it helps. Another thing would be to create /boot as a separate partition.
Signature · 1 line
Zan Lynx <[email protected]>
Quoted 3 lines · Zan Lynx
I have not checked if this is true, but it is a possible explanation:
Perhaps the filesystem is not properly unmounted during a suspend? That
Of course not.
Quoted 1 line
would mean GRUB is reading from a incoherent filesystem on resume.
Exactly.
Quoted 2 lines
GRUB's filesystem drivers are not very fancy. It could be it does something silly like check the journal before returning each block.
GRUB must not write to the fs, so it probably plays back the journal in memory only and it does this for every file it reads (at least that's how it feels :-)
Quoted 2 lines
Maybe its a journal size thing, you could try "sync" before suspend and see if it helps.
We already sync inside the kernel, it does not help here, though. Blockdev freezing might help.
Quoted 1 line
Another thing would be to create /boot as a separate partition.
Yes, that's what i always advise: /boot on separate ext2 partition. Then GRUB resumes fast.
Signature · 3 lines
Stefan Seyfried QA / R&D Team Mobile Devices | "Any ideas, John?" SUSE LINUX Products GmbH, Nürnberg | "Well, surrounding them's out."
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Quoted 9 lines · Stefan Seyfried
Quoted 3 lines · Zan Lynx
I have not checked if this is true, but it is a possible explanation:
Perhaps the filesystem is not properly unmounted during a suspend? That
Of course not.
Quoted 1 line
would mean GRUB is reading from a incoherent filesystem on resume.
Quoted 9 lines
Exactly.
Quoted 2 lines
GRUB's filesystem drivers are not very fancy. It could be it does something silly like check the journal before returning each block.
GRUB must not write to the fs, so it probably plays back the journal in memory only and it does this for every file it reads (at least that's how it feels :-)
Ah, OK, that makes sense. I did not expect GRUB to be *that* sophisticated :)
Quoted 6 lines
Quoted 2 lines
Maybe its a journal size thing, you could try "sync" before suspend and see if it helps.
We already sync inside the kernel, it does not help here, though. Blockdev freezing might help.
is there patch applicable to vanilla kernel? After repairing reiser several times (due to hard lockups during suspend-to-RAM) that sounds even more interesting.
Quoted 4 lines
Quoted 1 line
Another thing would be to create /boot as a separate partition.
Yes, that's what i always advise: /boot on separate ext2 partition. Then GRUB resumes fast.
well, this is small system, using yet another partition looked like useless waste :)
thank you for explanation
- -andrey
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFWUD1R6LMutpd94wRAtWFAJ92STsDVby88UUWmNVK1q41X96RXgCeN6o4 ilUTLBdKZPsWPkWi5LOKsbg=
=U1xV
-----END PGP SIGNATURE-----
Hi!
Quoted 9 lines
Quoted 5 lines
Quoted 2 lines
Maybe its a journal size thing, you could try "sync" before suspend and see if it helps.
We already sync inside the kernel, it does not help here, though. Blockdev freezing might help.
is there patch applicable to vanilla kernel? After repairing reiser several times (due to hard lockups during suspend-to-RAM) that sounds even more interesting.
Could you do the test Stefan asked? I do not think you'll kill reiserfs by single forced powerdown.
Pavel
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Quoted 8 lines · Pavel Machek
Hi!
Quoted 6 lines
Quoted 5 lines
Quoted 2 lines
Maybe its a journal size thing, you could try "sync" before suspend and see if it helps.
We already sync inside the kernel, it does not help here, though. Blockdev freezing might help.
Quoted 7 lines
Quoted 3 lines
is there patch applicable to vanilla kernel? After repairing reiser several times (due to hard lockups during suspend-to-RAM) that sounds even more interesting.
Could you do the test Stefan asked? I do not think you'll kill reiserfs by single forced powerdown.
well, I did it accidentally :) (forgot to plug in power and after 2 hours on battery notebook simply switched off) and yes, there was some noticeable delay loading grub. I also tried fs freezer without any visible effect. The patches from mm I applied to vanilla kernel:
add-include-linux-freezerh-and-move-definitions-from.patch swsusp-cleanup-whitespace-in-freezer-output.patch swsusp-freeze-filesystems-during-suspend-rev-2.patch swsusp-thaw-userspace-and-kernel-space-separately.patch
Do I need some more patches for this to work?
- -andrey
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFWitgR6LMutpd94wRAjh4AKCnGvpzxHuTEj+xKvEP7YhmESkD1wCffCm3 z0ZM59BV8FZUTy/onowVyW8=
=Vt7w
-----END PGP SIGNATURE-----
Quoted 25 lines · Andrey Borzenkov
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1Quoted 8 lines · Pavel Machek
Hi!
Quoted 6 lines
Quoted 5 lines
Quoted 2 lines
Maybe its a journal size thing, you could try "sync" before suspend and see if it helps.
We already sync inside the kernel, it does not help here, though. Blockdev freezing might help.
Quoted 7 lines
Quoted 3 lines
is there patch applicable to vanilla kernel? After repairing reiser several times (due to hard lockups during suspend-to-RAM) that sounds even more interesting.
Could you do the test Stefan asked? I do not think you'll kill reiserfs by single forced powerdown.
well, I did it accidentally :) (forgot to plug in power and after 2 hours on battery notebook simply switched off) and yes, there was some noticeable delay loading grub. I also tried fs freezer without any visible effect. The patches from mm I applied to vanilla kernel:
Quoted 6 lines
add-include-linux-freezerh-and-move-definitions-from.patch swsusp-cleanup-whitespace-in-freezer-output.patch swsusp-freeze-filesystems-during-suspend-rev-2.patch swsusp-thaw-userspace-and-kernel-space-separately.patch
Do I need some more patches for this to work?
I guess reiserfs would need to respond to filesystem freezing.
Pavel
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Quoted 25 lines · Pavel Machek
Quoted 24 lines · Andrey Borzenkov
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1Quoted 8 lines · Pavel Machek
Hi!
Quoted 6 lines
Quoted 5 lines
Quoted 2 lines
Maybe its a journal size thing, you could try "sync" before suspend and see if it helps.
We already sync inside the kernel, it does not help here, though. Blockdev freezing might help.
Quoted 6 lines
Quoted 3 lines
is there patch applicable to vanilla kernel? After repairing reiser several times (due to hard lockups during suspend-to-RAM) that sounds even more interesting.
Could you do the test Stefan asked? I do not think you'll kill reiserfs by single forced powerdown.
well, I did it accidentally :) (forgot to plug in power and after 2 hours on battery notebook simply switched off) and yes, there was some noticeable delay loading grub. I also tried fs freezer without any visible effect. The patches from mm I applied to vanilla kernel:
Quoted 9 lines
Quoted 6 lines
add-include-linux-freezerh-and-move-definitions-from.patch swsusp-cleanup-whitespace-in-freezer-output.patch swsusp-freeze-filesystems-during-suspend-rev-2.patch swsusp-thaw-userspace-and-kernel-space-separately.patch
Do I need some more patches for this to work?
I guess reiserfs would need to respond to filesystem freezing.
OK the I guess it would have not worked in mm either. As far as I can tell the only FS supporting it so far is XFS.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFWpElR6LMutpd94wRApSWAJ0Wm2Yey6k0Lf0tMO5gBsOBYS5qLACgw8Xj 1rTy08rdsktGkvneKrweENM=
=xUbx
-----END PGP SIGNATURE-----
Hi!
Quoted 7 lines
Quoted 3 lines
The idea is nice; unfortunately it fails to explain the difference between 'poweroff' and 'suspend disk' cases. I doubt disk layout is changed between them.
I have not checked if this is true, but it is a possible explanation:
Perhaps the filesystem is not properly unmounted during a suspend?
We do not/can not unmount filesystems during suspend. But we do sync them.
Pavel
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Quoted 9 lines · Andrey Borzenkov
Hash: SHA1
Quoted 4 lines · Stefan Seyfried
The most important question:
What filesystem is your /boot on? I'd bet quite some money that it is reiser or some other journaling FS (not ext3).there is no /boot, I use single / which is reiser.
ok, so your /boot is on reiser. Q.E.D.
Quoted 9 lines
Quoted 6 lines
I am pretty sure that it will also happen if you do "updatedb &", wait a minute and then do a _HARD_ power off.
I am pretty sure that it has nothing to do with the kernel version, just with the layout of your /boot partition (which of course changes with every kernel update). In other words: until now, you just have been lucky.
The idea is nice; unfortunately it fails to explain the difference between 'poweroff'
filesystem cleanly unmounted
Quoted 1 line
and 'suspend disk'
filesystem unclean.
Quoted 2 lines
cases. I doubt disk layout is changed
between them.
Try the "updatedb &, then _HARD_ poweroff" test described above. It will take long to load grub afterwards.
Signature · 3 lines
Stefan Seyfried QA / R&D Team Mobile Devices | "Any ideas, John?" SUSE LINUX Products GmbH, Nürnberg | "Well, surrounding them's out."
Quoted 27 lines · Stefan Seyfried
Quoted 9 lines · Andrey Borzenkov
Hash: SHA1
Quoted 4 lines · Stefan Seyfried
The most important question:
What filesystem is your /boot on? I'd bet quite some money that it is reiser or some other journaling FS (not ext3).there is no /boot, I use single / which is reiser.
ok, so your /boot is on reiser. Q.E.D.
Quoted 9 lines
Quoted 6 lines
I am pretty sure that it will also happen if you do "updatedb &", wait a minute and then do a _HARD_ power off.
I am pretty sure that it has nothing to do with the kernel version, just with the layout of your /boot partition (which of course changes with every kernel update). In other words: until now, you just have been lucky.
The idea is nice; unfortunately it fails to explain the difference between 'poweroff'
filesystem cleanly unmounted
Quoted 1 line
and 'suspend disk'
Quoted 7 lines
filesystem unclean.
Quoted 2 lines
cases. I doubt disk layout is changed
between them.Try the "updatedb &, then _HARD_ poweroff" test described above. It will take long to load grub afterwards.
Alternatively, you can use a recent -mm kernel with the bdevs freezing patch and see if that helps GRUB. ;-)
Greetings,
Rafael
Signature · 2 lines
You never change things by fighting the existing reality. R. Buckminster Fuller
Quoted 3 lines · Andrey Borzenkov
[...]
This is rather funny; in 2.6.19-rc5 grub is *really* slow loading kernel when I switch on the system after suspend to disk. Actually, after kernel has been loaded, the whole resuming (up to the point I have usable desktop again) takes about three time less than the process of loading kernel + initrd. During loading disk LED is constantly lit. This almost looks like kernel leaves HDD in some strange state, although I always assumed HDD/IDE is completely reinitialized in this case. [...]
I had the same problem (/boot on reiserfs, grub hanging for ages after resume with 2.6.19), but in 2.6.19.1 it seems fixed. Do you still have this bug, Andrey? I didn't find an update on this issue on LKML.
Greetings, Lee
Quoted 10 lines · Lee Garrett
Quoted 8 lines · Andrey Borzenkov
[...]
This is rather funny; in 2.6.19-rc5 grub is *really* slow loading kernel when I switch on the system after suspend to disk. Actually, after kernel has been loaded, the whole resuming (up to the point I have usable desktop again) takes about three time less than the process of loading kernel + initrd. During loading disk LED is constantly lit. This almost looks like kernel leaves HDD in some strange state, although I always assumed HDD/IDE is completely reinitialized in this case.
[...]
Quoted 3 lines
I had the same problem (/boot on reiserfs, grub hanging for ages after resume with 2.6.19), but in 2.6.19.1 it seems fixed. Do you still have this bug, Andrey? I didn't find an update on this issue on LKML.
I'm pretty sure this is just a coincidence, an issue about how the kernel image is actually layed out on your filesystem. I don't think it actually has to do anything with the version.
Signature · 3 lines
Stefan Seyfried QA / R&D Team Mobile Devices | "Any ideas, John?" SUSE LINUX Products GmbH, Nürnberg | "Well, surrounding them's out."
Quoted 11 lines · Stefan Seyfried
Quoted 10 lines · Lee Garrett
Quoted 8 lines · Andrey Borzenkov
[...]
This is rather funny; in 2.6.19-rc5 grub is *really* slow loading kernel when I switch on the system after suspend to disk. Actually, after kernel has been loaded, the whole resuming (up to the point I have usable desktop again) takes about three time less than the process of loading kernel + initrd. During loading disk LED is constantly lit. This almost looks like kernel leaves HDD in some strange state, although I always assumed HDD/IDE is completely reinitialized in this case.
[...]
Quoted 7 lines
Quoted 3 lines
I had the same problem (/boot on reiserfs, grub hanging for ages after resume with 2.6.19), but in 2.6.19.1 it seems fixed. Do you still have this bug, Andrey? I didn't find an update on this issue on LKML.
I'm pretty sure this is just a coincidence, an issue about how the kernel image is actually layed out on your filesystem. I don't think it actually has to do anything with the version.
Isn't the cause just that with that kernel the fs image is left unclean, and grub has to replay the journal, which is slow ?
Xav
Quoted 11 lines · Xavier Bestel
Quoted 8 lines · Stefan Seyfried
Quoted 3 lines · Lee Garrett
I had the same problem (/boot on reiserfs, grub hanging for ages after resume with 2.6.19), but in 2.6.19.1 it seems fixed. Do you still have this bug, Andrey? I didn't find an update on this issue on LKML.
I'm pretty sure this is just a coincidence, an issue about how the kernel image is actually layed out on your filesystem. I don't think it actually has to do anything with the version.
Isn't the cause just that with that kernel the fs image is left unclean,
with all kernels. I don't think it changed from 2.6.19 to 2.6.19.1
Quoted 1 line
and grub has to replay the journal, which is slow ?
Yes. But i think it depends on the actual disk layout _how slow_ it is :-)
Signature · 3 lines
Stefan Seyfried QA / R&D Team Mobile Devices | "Any ideas, John?" SUSE LINUX Products GmbH, Nürnberg | "Well, surrounding them's out."