From: Nirmal Govind <nirmalg-8DAjSxpRXgY@public.gmane.org>
To: "Yu, Luming" <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Mads Paulin <paulin-/w0Os/Ss2Sh/SzgSGea1oA@public.gmane.org>,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: acpi and 2.6.0 kernel - S3 doesn't resume, S4 =infinite loop
Date: Tue, 23 Dec 2003 09:12:34 -0500 [thread overview]
Message-ID: <3FE84D52.8060809@psu.edu> (raw)
In-Reply-To: <3ACA40606221794F80A5670F0AF15F8401720C4F-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
> What could cause S3 resume failure? My T21 works well with S3, S1.
> Could you please narrow down the issue !
> --Luming
After several google searches and reading up on posts by others abt
similar problems with ACPI, I was leaning towards the theory that it's
got something to do with the Intel 855 graphics adapter on both my
Fujitsu and Mads's ASUS. I read on another post that the graphics
card had issues with ACPI (that one wasn't Intel 855)..
But after looking at the syslog, this doesn't seem to be the
problem: there was a message that said it was
looking for "Module char-major-10-134" (the APM module) when it
resumed -- I put in an
alias to set this to off and that error went away. I also removed
all the modules before I suspended and that reduced the number of
errors I get when it resumes. But these are the remaining messages
from syslog:
Dec 23 02:22:13 variance kernel: Back to C!
Dec 23 02:22:13 variance kernel: acpi_processor_perf-0318 [37]
acpi_processor_set_per: Transition failed
Dec 23 02:22:13 variance kernel: cpufreq: resume failed in
->setpolicy/target step on CPU 0
Dec 23 02:22:13 variance kernel: PM: Finishing up.
Dec 23 02:22:13 variance kernel: PCI: Setting latency timer of
device 0000:00:1d.0 to 64
Dec 23 02:22:13 variance kernel: PCI: Setting latency timer of
device 0000:00:1d.1 to 64
Dec 23 02:22:13 variance kernel: PCI: Setting latency timer of
device 0000:00:1d.2 to 64
Dec 23 02:22:13 variance kernel: MCE: The hardware reports a non
fatal, correctable incident occurred on CPU 0.
Dec 23 02:22:13 variance kernel: Bank 1: e2000000000001d5
Dec 23 02:22:13 variance kernel: hda: Wakeup request inited, waiting
for !BSY...
Dec 23 02:22:13 variance kernel: hda: start_power_step(step: 1000)
Dec 23 02:22:13 variance kernel: blk: queue cf4fe000, I/O limit
4095Mb (mask 0xffffffff)
Dec 23 02:22:13 variance kernel: hda: completing PM request, resume
Dec 23 02:22:13 variance kernel: hdc: Wakeup request inited, waiting
for !BSY...
Dec 23 02:22:13 variance kernel: hdc: start_power_step(step: 1000)
Dec 23 02:22:13 variance kernel: hdc: completing PM request, resume
Dec 23 02:22:13 variance kernel: Restarting tasks... done
Dec 23 02:22:13 variance kernel: drivers/usb/host/uhci-hcd.c: 1820:
host system error, PCI problems?
Dec 23 02:22:13 variance kernel: drivers/usb/host/uhci-hcd.c: 1820:
host controller halted. very bad
Dec 23 02:22:13 variance kernel: drivers/usb/host/uhci-hcd.c: 1840:
host system error, PCI problems?
Dec 23 02:22:13 variance kernel: drivers/usb/host/uhci-hcd.c: 1840:
host controller halted. very bad
Dec 23 02:22:13 variance kernel: drivers/usb/host/uhci-hcd.c: 1860:
host system error, PCI problems?
Dec 23 02:22:13 variance kernel: drivers/usb/host/uhci-hcd.c: 1860:
host controller halted. very bad
So looks like there's some problem with the uhci-hcd controller? I
googled and it's a recognized bug:
http://bugzilla.kernel.org/show_bug.cgi?id=1373
The workaround suggested is to rmmod the uhci-hcd module .. I have
it built into the kernel so maybe I need to recompile this as a
module... However, the others have been able to resume, just that
the USB devices don't work.. mine doesn't resume at all.. could this
have to do with the following error above:
cpufreq: resume failed in ->setpolicy/target step on CPU 0
Should I uncheck the CONFIG_X86_ACPI_CPUFREQ=y option in the kernel
config?
Btw, the thermal_zone directory in /proc/acpi is empty.. I did
enable it in
the kernel configure .. the same goes for fan/ - it's also empty. Do
these work for you?
nirmal
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
next prev parent reply other threads:[~2003-12-23 14:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-23 6:19 acpi and 2.6.0 kernel - S3 doesn't resume, S4 =infinite loop Yu, Luming
[not found] ` <3ACA40606221794F80A5670F0AF15F8401720C4F-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2003-12-23 14:12 ` Nirmal Govind [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-22 8:01 acpi and 2.6.0 kernel - S3 doesn't resume, S4 = infinite loop Nirmal Govind
[not found] ` <3FE6A4EF.6070002-8DAjSxpRXgY@public.gmane.org>
2003-12-22 9:59 ` Mads Paulin
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=3FE84D52.8060809@psu.edu \
--to=nirmalg-8dajsxprxgy@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=paulin-/w0Os/Ss2Sh/SzgSGea1oA@public.gmane.org \
/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