From: yakui_zhao <yakui.zhao@intel.com>
To: Darren Salt <linux@youmustbejoking.demon.co.uk>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: Oopses and ACPI problems (Linus 2.6.29-rc4)
Date: Tue, 10 Feb 2009 09:06:00 +0800 [thread overview]
Message-ID: <1234227960.3706.67.camel@localhost.localdomain> (raw)
In-Reply-To: <gemini.ket9w800w44dc0hvg.linux@youmustbejoking.demon.co.uk>
On Tue, 2009-02-10 at 02:26 +0800, Darren Salt wrote:
> I'm seeing various oopses with -rc4, where -rc3 is fine; config, dmesg
> (captured via netconsole) and decoded oops data attached ¹. The last few
> oopses were followed by a scrambled display and a hard lockup.
>
> All oopses follow an otherwise successful suspend-to-RAM.
>
> Also, I see that Fn-Fx don't seem to be reported via /proc/acpi/events any
> more, or at least I'm seeing no evidence of them via acpi_listen (and, not
> coincidentally, I can't adjust the volume etc. via eeepc-acpi-scripts).
>
> The only other (significant) change is that I've installed X from Debian
> experimental, though -rc3 and 2.6.28.* seem fine with this. (Oh, and I can
> get UXA to cause OOM quite trivially... several Iceweasel tabs is enough.)
>
>From the description it seems that this is a regression.
Will you please use git-bisect to identify which commit causes the
regression?
Thanks.
>
> ¹ Yes, I decided not to include symbol names in the running kernel...
>
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2009-02-10 0:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LFD.2.00.0902081251090.3048@localhost.localdomain>
2009-02-09 18:26 ` Oopses and ACPI problems (Linus 2.6.29-rc4) Darren Salt
2009-02-09 23:49 ` Ingo Molnar
2009-02-10 14:12 ` Darren Salt
2009-02-10 14:54 ` [PATCH 2.6.29-rc4] Restore ACPI reporting via /proc/acpi/events for EeePC & other Asus laptops Darren Salt
2009-02-24 11:31 ` Corentin Chary
2009-02-10 15:04 ` Oopses and ACPI problems (Linus 2.6.29-rc4) Matthew Garrett
2009-02-10 15:15 ` Darren Salt
2009-02-10 15:45 ` Matthew Garrett
2009-02-10 16:03 ` Darren Salt
2009-02-23 16:39 ` Matthew Garrett
2009-02-24 15:29 ` Darren Salt
2009-02-24 16:00 ` Matthew Garrett
2009-02-24 19:45 ` Darren Salt
2009-02-10 16:06 ` Corentin Chary
2009-02-10 19:16 ` Darren Salt
2009-02-11 2:03 ` Matthew Garrett
2009-02-11 1:23 ` yakui_zhao
2009-04-19 1:56 ` [PATCH] eee-laptop: Register as a pci-hotplug device Matthew Garrett
2009-04-19 7:20 ` Corentin Chary
2009-04-19 15:13 ` Matthew Garrett
2009-04-25 14:12 ` Corentin Chary
2009-04-26 17:16 ` Matthew Garrett
2009-04-26 20:51 ` Corentin Chary
2009-02-10 1:06 ` yakui_zhao [this message]
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=1234227960.3706.67.camel@localhost.localdomain \
--to=yakui.zhao@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@youmustbejoking.demon.co.uk \
/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;
as well as URLs for NNTP newsgroup(s).