Messages in this thread | | | Date | Thu, 15 Jul 2004 14:10:43 +0200 | From | Éric Brunet <> | Subject | swsuspend not working |
| |
Hi,
With Pavel declaring that software suspend was mostly working on non-SMP computers and that only device drivers were to remained to be fixed, I felt that I needed to give it a try.
You see, on the three latest computers I have played with (two laptops and one desktop), I never managed to get suspend to disk to work. The best I got was a year ago for some revision of pmdisk were, for stripped down kernels with no module loaded I could suspend and resume once in a while. Then Patrick released a new version and it never worked again. Then Patrick stopped working on that.
I have never tried swsusp2 because my goal, ultimately, is to have S3 working. I understand that S3 is much more difficult than S4 and that swsusp2 does not deal with S3. So the plan is to have S4 on swsusp, then S3. (Actually, my latest laptop seems to have S3 half working with kernel parameter acpi_sleep=s3_bios, but S4 does not.)
As I said, I felt ready for trying again. I compiled a 2.6.8-rc1 kernel with the barest possible configuration file: support for IDE, ext3,/proc, keyboard and acpi. No mouse, no usb, no framebuffer, no agp, no preempt, no apic, no module, etc. A useless kernel, obviously, but I tried to maximize the odds to have S4 working.
I booted with " root=/dev/hda2 resume=/dev/hda5 init=/bin/sh". No initrd, of course. Once I had a prompt, I mounted /proc and echoed 4 to /proc/acpi/sleep. The screen blinked and 3 seconds later I was back at my shell. The computer did not suspend. One very bad thing happened: in the process, the fan controller was reset. It means that the fan went full speed, while before it was in a low speed/low noise mode set up by the bios. I know I cannot bring it back to the low speed/low noise setting from linux, I must reboot the computer. But anyway, the computer did not suspend.
Here are the kernel messages I got: ----------------------------------------- dsmthdat-0462 [36] ds_method_data_get_val: Uninitialized Local[0] at node df72f10c Freeing memory: .....| PM: Attempting to suspend to disk. PM: snapshotting memory. ACPI: PCI interrupt 0000:00:1f.1[A] -> GSI 11 (level, low) -> IRQ 11 dsmthdat-0462 [36] ds_method_data_get_val: Uninitialized Local[0] at node df72f10c dsmthdat-0462 [36] ds_method_data_get_val: Uninitialized Local[0] at node df72f90c Restarting tasks... done ------------------------------------------- (device 0000:00:1f.1 is the IDE controller. lspci output says it is connected to IRQ 11, but /proc/interrupts gives IRQ 14 for ide0 and nothing for IRQ 11)
What does that mean ? What can I do to debug the problem and have S4 working ? I am leaving for a long WE, but starting on Monday, I am willing to try any patch or any kernel configuration to have things working.
All relevant information on the computer (lspci, dsdt, kernel config, full dmesg) is on http://tudia.nerim.net/bug-reports/
Thanks,
Éric Brunet - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |