[Bug 934397] New: Resume from suspend to ram fails when HDD is connected
http://bugzilla.opensuse.org/show_bug.cgi?id=934397 Bug ID: 934397 Summary: Resume from suspend to ram fails when HDD is connected Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers@forge.provo.novell.com Reporter: dario@growingman.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- During resume from suspend, the display content reappears correctly but after a short pause (2-3 secs) the kernel panics, the keyboard is unresponsive with lights flashing. Reset/power cycle is the only way forward. After a long series of tests, I discovered that if I disconnect the extra drive WDC WD30EZRX-00M (3TB), the desktop can resume correctly every time! The additional drive is for storage only. It contains only a Samba share, but it was unmounted (but powered and connected). I persisted with the tests only because I've recently noticed that both Ubuntu and Debian that I installed (in their most recent versions) on a 3rd drive (that too is a WD Caviar Green) can resume from suspend without problems. Only the default graphic driver is installed: bigboy:~ # lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation 82G965 Integrated Graphics Controller (rev 02) Event though I can't seem to have the correct debuginfo package installed to use crash, I was able to read in the dmesg saved by kdump (abstract): [ 165.133021] ata4: SATA link down (SStatus 0 SControl 300) [ 165.133038] ata3: SATA link down (SStatus 0 SControl 300) [ 165.135012] ata6: SATA link down (SStatus 0 SControl 300) [ 166.052486] ata7.00: configured for UDMA/33 [ 169.469022] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 169.470705] ata1.00: configured for UDMA/133 [ 170.182017] ata5: link is slow to respond, please be patient (ready=0) [ 170.183010] ata2: link is slow to respond, please be patient (ready=0) [ 174.824010] ata2: COMRESET failed (errno=-16) [ 174.874021] ata5: COMRESET failed (errno=-16) [ 175.129019] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 175.281767] ata2.00: configured for UDMA/133 Since then I tried to change cable and SATA port with no changes: if that drive is connected, resume fails. I would be happy to provide more info if necessary. Thanks for your help -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=934397
Dario Savella
http://bugzilla.opensuse.org/show_bug.cgi?id=934397
Takashi Iwai
http://bugzilla.opensuse.org/show_bug.cgi?id=934397
--- Comment #2 from Takashi Iwai
http://bugzilla.opensuse.org/show_bug.cgi?id=934397
--- Comment #3 from Dario Savella
http://bugzilla.opensuse.org/show_bug.cgi?id=934397
--- Comment #4 from Dario Savella
http://bugzilla.opensuse.org/show_bug.cgi?id=934397
--- Comment #5 from Takashi Iwai
I tried with kernel 4.0.5-1.gf4cd21b-desktop and the problem is still there. I do have a crash dump if it helps (I can only provide the files, not any skills to look at them).
The dmesg from the crash says:
[ 73.957016] ata3: SATA link down (SStatus 0 SControl 300) [ 73.961017] ata4: SATA link down (SStatus 0 SControl 300) [ 73.961030] ata6: SATA link down (SStatus 0 SControl 300) [ 74.114023] usb 5-1: reset low-speed USB device number 2 using uhci_hcd [ 74.880484] ata7.00: configured for UDMA/33 [ 75.748492] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [ 78.244018] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 78.245701] ata1.00: configured for UDMA/133 [ 79.002184] ata5: link is slow to respond, please be patient (ready=0) [ 79.012012] ata2: link is slow to respond, please be patient (ready=0) [ 83.031024] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 83.184936] ata5.00: configured for UDMA/133 [ 83.704007] ata2: COMRESET failed (errno=-16) [ 85.539018] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 85.663005] sr 6:0:0:0: **** DPM device timeout ****
So this looks like the cause. The recent kernel has a watchdog for async resume workers, and if it expires, it panics. This explains why 3.12 worked; the watchdog was introduced since 3.13. The timeout length is unfortunately fixed in Kconfig, set to 12 as default. And this seems too short. We should extend this to at least a minute, I suppose. Also, it'd be better to be dynamically configuratble. The openSUSE-13.2 test kernel packages with the extended timeout to 60 seconds is being built on OBS home:tiwai:bnc934397 repo. Could you give it a try? It will take some time until the build finishes. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=934397
--- Comment #6 from Dario Savella
http://bugzilla.opensuse.org/show_bug.cgi?id=934397
--- Comment #7 from Dario Savella
I will give it a try. While we wait for the build, could you help me to add the repository you mention ? I can add repositories, but now with the notation you are using.
...but NOT with... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=934397
--- Comment #8 from Takashi Iwai
I will give it a try. While we wait for the build, could you help me to add the repository you mention ? I can add repositories, but now with the notation you are using.
osc ar obs://home:/tiwai:/bnc934397/standard test-kernel The build seems already finished, but not published yet. Meanwhile you can get binaries directly via osc getbinaries home:tiwai:bnc934397/kernel-desktop/standard/x86_64 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=934397
--- Comment #9 from Takashi Iwai
(In reply to Dario Savella from comment #6)
I will give it a try. While we wait for the build, could you help me to add the repository you mention ? I can add repositories, but now with the notation you are using.
osc ar obs://home:/tiwai:/bnc934397/standard test-kernel
Sorry, it's zypper, instead of osc, of course.
The build seems already finished, but not published yet. Meanwhile you can get binaries directly via osc getbinaries home:tiwai:bnc934397/kernel-desktop/standard/x86_64
This is with osc. With directly using osc, you can download the unpublished packages, too. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=934397
--- Comment #10 from Takashi Iwai
http://bugzilla.opensuse.org/show_bug.cgi?id=934397
--- Comment #11 from Dario Savella
http://bugzilla.opensuse.org/show_bug.cgi?id=934397
--- Comment #12 from Takashi Iwai
Good news I suppose. The new kernel resumes from suspend with the drive connected and/or mounted. Just be sure I installed the right thing:
bigboy:~ # cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-3.16.7-1.gf382e20-desktop root=UUID=b914b0a0-964b-4fa7-91c9-a0f8f0b57fcf quiet resume=/dev/sda1 splash=silent quiet showopts crashkernel=256M-:128M clocksource=tsc vga=792
Is there anything else you need from my end ?
Could you give the kernel messages after resume with the new kernel?
What's the release cycle for these fixes? I'm in no hurry, but I'd like to know when to stop worrying about resume.
The change must be safe, so I can take it soon. But, the official update release may take some time for openSUSE 13.2, as usual. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=934397
--- Comment #13 from Dario Savella
http://bugzilla.opensuse.org/show_bug.cgi?id=934397
http://bugzilla.opensuse.org/show_bug.cgi?id=934397#c14
Mark Scott
participants (1)
-
bugzilla_noreply@novell.com