Bugzilla – Bug 115308
desktop PC crashes upon resume from suspend2disk
Last modified: 2008-09-02 18:07:37 UTC
I did a fresh install of 10.0b4 on my desktop PC and tried S2D on it for the first time. Not that I'd expect it to work on my desktop, but we were asked to test it some time ago... :) Suspending works fine, but resuming leads to a freeze: Suspend2D was done from X via the kpowersave tray icon. On resume, it starts the kernel and loads the image from swap successfully (I think). At least I end up on a text screen showing the usual text messages from resume. X isn't restored. Then, I can switch to the virtual consoles 1-6 and 10 without problems. I can also try to login on the VT, but it only accepts the user name. On return, it hangs and doesn't ask for the PWD. When I try to switch to VT 7 for X, the machine seems to freeze completely - at least I only get a black screen and it doesn't react on keyboard input any more. I'm note really sure how to debug this further - could you perhaps give me some hints what will help you? If you feel that it's a bad idea to S2D on such a machine, please feel free to close this bug. I just tested it out of curiosity.
Created attachment 48802 [details] hwinfo output on my desktop PC
please provide lspci and /var/log/suspend*.log
Well, it should work with desktop pc, too - if the hardware / drivers for the hardware support power management (they should), so it is a good idea to report it. You could try out minimal config with init=/bin/bash, if this works try to add components to the mix until it fails. Debugging is explained a bit in http://www.susewiki.org/index.php?title=ACPI_suspend
# lspci 00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 03) 00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP] 00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40) 00:07.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) 00:07.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 16) 00:07.4 Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40) 00:08.0 Network controller: AVM Audiovisuelles MKTG & Computer System GmbH B1 ISDN (rev 01) 00:09.0 SCSI storage controller: Adaptec AHA-7850 (rev 03) 00:0a.0 Network controller: AVM Audiovisuelles MKTG & Computer System GmbH B1 ISDN (rev 01) 00:0c.0 Multimedia audio controller: Ensoniq ES1371 [AudioPCI-97] (rev 06) 00:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R100 QD [Radeon 7200]
Created attachment 48806 [details] /var/log/suspend2disk.log
Ok, here are the first findings: - S2D works in init=/bin/bash - S2D works in runlevel 3 - S2D works not in rl 5. It seems to crash or hang when trying to switch back to graphics mode. - On every suspend, one of my hard disks is turned off (quite at the beginning of the suspend cycle) and turned on again (short before "Writing image..."). On Resume it seems to be also turned off and on again. - Sometimes, even suspend doesn't work. It finishes nearly everything but hangs before "Writing image...". Further details will follow as soon as this bug occurs again. Further details regarding what exactly causes it to not work will follow.
the aic7xxx combined with the radeon on the same IRQ may be bad. Does it work if you unload the aic driver before suspend?
Woohooo! Yes, now it worked. Two times in a row. Wow... You're my hero OTD :D So I just add "aic7xxx" to UNLOAD_MODULES_BEFORE_SUSPEND2DISK and be happy? Or do you plan to debug this issue further?
not really :-) SCSI being broken wrt suspend is well known (although it thought that the aic7xxx was fixed some time ago because a developer only had this disk controller and needed to fix the driver to debug another problem), so there is not much we can do about this now.
ic.
Because the LATER and REMIND resolutions have been removed, the resolution of this bug has changed from LATER to WONTFIX. If this bug needs to be reconsidered, reopen it and set a future "Target Milestone for Fix."