From: "Éric Brunet" <Eric.Brunet@lps.ens.fr>
To: Linux Kernel mailing list <linux-kernel@vger.kernel.org>, pavel@ucw.cz
Subject: swsuspend not working
Date: Thu, 15 Jul 2004 14:10:43 +0200 [thread overview]
Message-ID: <20040715121042.GB9873@lps.ens.fr> (raw)
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
next reply other threads:[~2004-07-15 12:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040715121042.GB9873@lps.ens.fr.suse.lists.linux.kernel>
2004-07-15 12:10 ` Éric Brunet [this message]
2004-07-15 12:18 ` Pavel Machek
2004-07-15 13:23 ` Éric Brunet
2004-07-15 13:21 ` Nigel Cunningham
2004-07-19 19:19 ` Éric Brunet
2004-07-20 13:17 ` Pavel Machek
2004-07-20 15:50 ` Romano Giannetti
2004-07-31 18:20 ` Éric Brunet
2004-08-06 19:06 ` Pavel Machek
2004-08-06 23:54 ` Éric Brunet
2004-08-07 7:13 ` Paul Gortmaker
[not found] ` <20040807140845.GA8353@lps.ens.fr>
2004-08-21 12:14 ` PATCH swsuspend for ne2k-pci cards Éric Brunet
2004-08-23 19:51 ` Pavel Machek
2004-09-01 14:56 ` PATCH (RESENT) " Éric Brunet
2004-07-15 12:47 ` swsuspend not working Stefan Seyfried
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040715121042.GB9873@lps.ens.fr \
--to=eric.brunet@lps.ens.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®