From: Jonathan Nieder <jrnieder@gmail.com>
To: Octavio Alvarez <alvarezp@alvarezp.com>
Cc: Bob Moore <robert.moore@intel.com>,
680707@bugs.debian.org, linux-acpi@vger.kernel.org
Subject: Re: [3.4-rc5 -> 3.4-rc6 regression] Asus P5NSLI: lockup on resume from suspend
Date: Sun, 8 Jul 2012 02:37:58 -0500 [thread overview]
Message-ID: <20120708073758.GC4625@burratino> (raw)
In-Reply-To: <op.wg30yabp6g6bxc@localhost.localdomain>
Hi again,
Octavio Alvarez wrote:
> The problem is a full system lock-up on resume. The HD led stays on.
> The 5-sec power-button cycle isn't enough to get the system back.
> It requires a full mechanical power cycle from the power supply.
>
> I bisected the problem as requested by Alan Stern, and tracked it
> down to the following commit:
[...]
> ACPICA: ACPI 5: Support for new FADT SleepStatus, SleepControl registers
Looks similar to https://bugzilla.kernel.org/show_bug.cgi?id=43641
The purpose of commit 2feec47d4c5f was to add support for ACPI 5
registers. ACPI 5 was published in November, 2011. Your BIOS is from
2008 and uses a version 3 FADT.
I guess we'll have to sift through
5 files changed, 475 insertions(+), 679 deletions(-)
for the unintended change. Hmm.
Could you try the following in order to make the hunt easier?
Please enable ACPI_DEBUG and ACPI_DEBUG_FUNC_TRACE:
scripts/config --enable ACPI_DEBUG
scripts/config --enable ACPI_DEBUG_FUNC_TRACE
make deb-pkg; # maybe with -j4
reboot
Set debug_layer to ACPI_HARDWARE and debug_level to 0xffffffff:
echo 2 >/sys/module/acpi/parameters/debug_layer
echo 0xffffffff >/sys/module/acpi/parameters/debug_level
and get a log of what happens during the suspend and resume that locks
up. You'll probably need to use a serial console or netconsole to get
the log (boot with no_console_suspend to make sure log output
continues to flow during the suspend process). [1] and [2] explain
how to set up a serial console or netconsole.
([3] and [4] describe ACPI debugging and no_console_suspend.)
It's possible and even likely that the kernel won't be awake enough to
say anything interesting at the crucial moment, but I figure it's
worth a try (and at least it can say a little about what happened
during suspend).
Thanks for your patience.
Jonathan
[1] Documentation/serial-console.txt
[2] Documentation/networking/netconsole.txt
[3] Documentation/acpi/debug.txt
[4] Documentation/power/basic-pm-debugging.txt
next prev parent reply other threads:[~2012-07-08 7:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <op.wg3en6ij6g6bxc@localhost.localdomain>
[not found] ` <Pine.LNX.4.44L0.1207072208270.508-100000@netrider.rowland.org>
[not found] ` <20120708025730.GE2961@burratino>
2012-07-08 4:19 ` [3.4-rc5 -> 3.4-rc6 regression] Asus P5NSLI: lockup on resume from suspend Octavio Alvarez
2012-07-08 4:30 ` Jonathan Nieder
2012-07-08 6:39 ` Bug#680707: " Octavio Alvarez
2012-07-08 7:37 ` Jonathan Nieder [this message]
2012-07-08 9:04 ` Jonathan Nieder
2012-07-08 9:46 ` Bug#680707: " Octavio Alvarez
2012-07-08 19:04 ` [PATCH] ACPI: Leave Bus Master Arbitration enabled for suspend/resume Jonathan Nieder
2012-07-08 19:32 ` Jonathan Nieder
2012-07-08 19:43 ` Rafael J. Wysocki
2012-07-08 19:45 ` [PATCH v2] " Jonathan Nieder
2012-07-08 20:08 ` Rafael J. Wysocki
2012-07-08 20:33 ` Moore, Robert
2012-07-08 20:48 ` Rafael J. Wysocki
2012-07-08 20:43 ` Octavio Alvarez
2012-07-08 20:53 ` Rafael J. Wysocki
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=20120708073758.GC4625@burratino \
--to=jrnieder@gmail.com \
--cc=680707@bugs.debian.org \
--cc=alvarezp@alvarezp.com \
--cc=linux-acpi@vger.kernel.org \
--cc=robert.moore@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.