Most recent kernel where this bug did not occur: 2.6.14, but has been happending always, with every kernel I tried. Distribution: Debug, hand compiled kernel (2.6.14) Hardware Environment: Dell D610 with ATI Radeon graphic chipset, 1GB RAM, SATA Disk Controller, here is the complete information: diego@calisto:~$ lspci 0000:00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller (rev 03) 0000:00:01.0 PCI bridge: Intel Corporation Mobile 915GM/PM Express PCI Express Root Port (rev 03) 0000:00:1c.0 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1 (rev 03) 0000:00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 03) 0000:00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 03) 0000:00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 (rev 03) 0000:00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 (rev 03) 0000:00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 03) 0000:00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev d3) 0000:00:1e.2 Multimedia audio controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller (rev 03) 0000:00:1e.3 Modem: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Modem Controller (rev 03) 0000:00:1f.0 ISA bridge: Intel Corporation 82801FBM (ICH6M) LPC Interface Bridge (rev 03) 0000:00:1f.2 IDE interface: Intel Corporation 82801FBM (ICH6M) SATA Controller (rev 03) 0000:00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus Controller (rev 03) 0000:01:00.0 VGA compatible controller: ATI Technologies Inc M22 [Radeon Mobility M300] 0000:02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5751 Gigabit Ethernet PCI Express (rev 01) 0000:03:01.0 CardBus bridge: Texas Instruments PCI6515 Cardbus Controller 0000:03:01.5 Communication controller: Texas Instruments PCI6515 SmartCard Controller 0000:03:03.0 Network controller: Intel Corporation PRO/Wireless 2915ABG MiniPCI Adapter (rev 05) diego@calisto:/proc$ cat cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 13 model name : Intel(R) Pentium(R) M processor 2.00GHz stepping : 8 cpu MHz : 798.146 cache size : 2048 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss tm pbe nx est tm2 bogomips : 1598.31 Software Environment: linux 2.6.14, udev 0.76 (Don't know what else do you need, i'm not using any kernel patch) Problem Description: Using the hibernate script the computer goes into suspend mode, afterwards it cannot get back from it. It seems to resume, but the screen is black and there is no disk activity. Steps to reproduce: type hibernate, it goes to sleep wait a few seconds press power on button ==> computer seems to resume and then it blocks hard.
Did you try the tricks described in Documentation/power/video.txt yet?
ok, i have tried all the thing with the seting acpi_sleep, the result is that upon resuming the laptop reboots. i tried the vbetool based trick, no result with that either. I forgot to say that the laptops model is D610m i think that was the complete name. Second, i believe that you have not read what i wrote on the first 3 lines (otherwise you would have noticed that i have a SATA disk and there is still no support for proper suspend/resume on those). And also at the end i say that there is no disk activity at all. Any way, i posted this bug a result to this post from Dave Jones in the kernel planet: http://www.livejournal.com/users/kernelslacker/31234.html. It says: Laptop suspend/standby This is a mixed bag. It's getting a lot better in some ways, and a lot worse in others. There are still a lot of users out there using out of tree implementations like suspend2, which works for them, whilst the in-kernel variant doesn't. But instead of working to get these problems fixed, they happily continue patching, and never report their problems. Additionally, a majority of these bugs are now in drivers. notice the sentence before the last one *never report their problems*. Any way, i just wanted to report this problem even if it is known to kernel hackers.
Can you please try the 2.6.18 kernel and the s2ram tool to suspend to RAM (see http://en.opensuse.org/S2ram)?
Rejecting due to the lack of response.