Bug 14130
Summary: | system hangs while resuming to disk | ||
---|---|---|---|
Product: | Power Management | Reporter: | Andrzej (adk_rzeszow) |
Component: | Hibernation/Suspend | Assignee: | power-management_other |
Status: | REJECTED INSUFFICIENT_DATA | ||
Severity: | blocking | CC: | ikalvachev, lenb, rjw, rui.zhang, yakui.zhao |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.27, 2.6.30.5 | Subsystem: | |
Regression: | Yes | Bisected commit-id: | |
Bug Depends on: | |||
Bug Blocks: | 7216 | ||
Attachments: | lspci and acpidump output |
Description
Andrzej
2009-09-06 10:21:39 UTC
I guess 2.6.31-rc9 also hangs? hi, Andrzej Will you please double check whether it hangs in course of hibernation/resume? Will you please check whether the suspend/resume can work on your box? If it can work, please attach the output of dmesg after suspend/resume. Thanks. > I guess 2.6.31-rc9 also hangs? Yes, it also hangs. > Will you please double check whether it hangs in course of hibernation/resume? I tried to start my system with minimal set of processes and modules and it also hangs, so I guess it's a kernel issue. > Will you please check whether the suspend/resume can work on your box? If it can work, please attach the output of dmesg after suspend/resume. Suspending to RAM works. Dmesg output: [ 128.606343] PM: Syncing filesystems ... done. [ 128.610952] Freezing user space processes ... (elapsed 0.00 seconds) done. [ 128.611904] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done. [ 128.612193] Suspending console(s) (use no_console_suspend to debug) [ 128.652032] sd 0:0:1:0: [sdb] Synchronizing SCSI cache [ 128.739613] sd 0:0:1:0: [sdb] Stopping disk [ 128.956248] sd 0:0:0:0: [sda] Synchronizing SCSI cache [ 128.956490] sd 0:0:0:0: [sda] Stopping disk [ 131.016337] ns558 00:0b: disabled [ 131.016511] parport_pc 00:0a: disabled [ 131.016729] serial 00:09: disabled [ 131.016803] ACPI handle has no context! [ 131.071603] ehci_hcd 0000:00:03.3: PCI INT D disabled [ 131.071651] ehci_hcd 0000:00:03.3: PME# disabled [ 131.084035] ohci_hcd 0000:00:03.2: PCI INT C disabled [ 131.084073] ohci_hcd 0000:00:03.1: PCI INT B disabled [ 131.084108] ohci_hcd 0000:00:03.0: PCI INT A disabled [ 131.084337] Intel ICH 0000:00:02.7: PCI INT C disabled [ 131.100714] ACPI: Preparing to enter system sleep state S3 [ 131.101039] Disabling non-boot CPUs ... [ 131.104004] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106 [ 131.104004] Intel machine check architecture supported. [ 131.104004] Intel machine check reporting enabled on CPU#0. [ 131.104004] CPU0: Intel P4/Xeon Extended MCE MSRs (12) available [ 131.104004] CPU0: Thermal LVT vector (0xfa) already installed [ 131.104004] Back to C! [ 131.104004] ACPI: Waking up from system sleep state S3 [ 131.116050] pata_sis 0000:00:02.5: restoring config space at offset 0x1 (was 0x2100001, writing 0x2100005) [ 131.148621] Intel ICH 0000:00:02.7: PCI INT C -> GSI 18 (level, low) -> IRQ 18 [ 131.158046] ohci_hcd 0000:00:03.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20 [ 131.180057] ohci_hcd 0000:00:03.1: PCI INT B -> GSI 21 (level, low) -> IRQ 21 [ 131.204052] ohci_hcd 0000:00:03.2: PCI INT C -> GSI 22 (level, low) -> IRQ 22 [ 131.228058] ehci_hcd 0000:00:03.3: PME# disabled [ 131.228066] ehci_hcd 0000:00:03.3: PCI INT D -> GSI 23 (level, low) -> IRQ 23 [ 131.228078] ehci_hcd 0000:00:03.3: PME# disabled [ 131.312542] ata1.01: ACPI cmd ef/03:0c:00:00:00:b0 filtered out [ 131.312549] ata1.01: ACPI cmd ef/03:45:00:00:00:b0 filtered out [ 131.312660] ata2.00: ACPI cmd ef/03:0c:00:00:00:a0 filtered out [ 131.312666] ata2.00: ACPI cmd ef/03:44:00:00:00:a0 filtered out [ 131.443305] serial 00:09: activated [ 131.444733] parport_pc 00:0a: activated [ 131.445566] ns558 00:0b: activated [ 131.448349] ata2.00: configured for UDMA/66 [ 131.576035] sd 0:0:0:0: [sda] Starting disk [ 136.320290] ata1.00: ACPI cmd ef/03:0c:00:00:00:a0 filtered out [ 136.320297] ata1.00: ACPI cmd ef/03:45:00:00:00:a0 filtered out [ 136.382120] ata1.00: configured for UDMA/100 [ 136.388417] ata1.01: configured for UDMA/100 [ 136.423747] sd 0:0:1:0: [sdb] Starting disk [ 142.004838] Restarting tasks ... done. > with new kernel versions. did old versions work? if yes, what is the latest version that worked? > product: NV28 [GeForce4 Ti 4200 AGP 8x] > vendor: nVidia Corporation are you using the same graphics drivers on the new failing kernel as you did in the old working kernel? > what is the latest version that worked? It seems to be 2.6.29. It's interesting, but the same kernel (2.6.27) which hangs with OpenSuSE works with Debian - so 2.6.27 might be good, but this is OpenSuse's issue. > are you using the same graphics drivers on the new failing kernel > as you did in the old working kernel? Yes. I'm using version 96.43.13 which works with all kernels tested by me (from 2.6.18 to 2.6.30, tomorrow I will try to compile latest 2.6.31). I also downloaded 2.6.30-1 image from Debian repository (to have a kernel not configured by me, without patches applied by me and without nVidia driver). However, it also hangs. > I will try to compile latest 2.6.31
Update: 2.6.31 also hangs.
Do you have module/driver that loads firmware? (wifi?) I'm having similar problem with e100 driver that started using external firmware since 2.6.29. The workaround is to embed the firmware into the kernel main blob. Also take a look of linux-2.6/Documentation/power/basic-pm-debugging.txt Hi, Andrzej thanks for the test. Will you please do the hibernation test under console mode? (Enter the init level 3). If the issue still exists, please attach the output of lspci -vxxx, acpidump. Thanks. > Do you have module/driver that loads firmware? (wifi?) I guess, that rt73usb loads some kind of binary firmware. > Will you please do the hibernation test under console mode? In console mode it still hangs. I also tried to boot a very basic system (booting with init=/bin/bash and only mounting swap partition) and the issue still exists. Created attachment 23390 [details]
lspci and acpidump output
Output from lspci and acpidump.
the problem still exists in 2.6.32, right? please run "echo disk > /sys/power/state; dmesg > dmesg-hibernate" and see if you can get the dmesg after the hibernation failure. If yes, or you can get the similar info in other ways, please attach the sys log after hibernation. If no, please attach the screen shot when system hangs. bug closed as there is no response from the bug reporter. please re-open it if the problem still exists in the latest upstream kernel. |