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
WARNING: multiple messages have this Message-ID (diff)
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... >
next prev parent reply other threads:[~2009-02-10 0:54 UTC|newest] Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-02-08 21:01 Linus 2.6.29-rc4 Linus Torvalds 2009-02-09 1:21 ` Arjan van de Ven 2009-02-09 8:28 ` Ingo Molnar 2009-02-09 12:18 ` Avi Kivity 2009-02-09 13:34 ` Gerd Hoffmann 2009-02-09 15:04 ` Steven Noonan 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-09 23:49 ` Ingo Molnar 2009-02-10 14:12 ` Darren Salt 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-10 14:54 ` 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:04 ` Matthew Garrett 2009-02-10 15:15 ` Darren Salt 2009-02-10 15:15 ` Darren Salt 2009-02-10 15:45 ` Matthew Garrett 2009-02-10 15:45 ` Matthew Garrett 2009-02-10 16:03 ` Darren Salt 2009-02-23 16:39 ` Matthew Garrett 2009-02-23 16:39 ` Matthew Garrett 2009-02-24 15:29 ` Darren Salt 2009-02-24 16:00 ` Matthew Garrett 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 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] 2009-02-10 1:06 ` Oopses and ACPI problems (Linus 2.6.29-rc4) yakui_zhao 2009-02-10 14:02 ` [PATCH] Do not account for the address space used by hugetlbfs using VM_ACCOUNT V2 (Was Linus 2.6.29-rc4) Mel Gorman 2009-02-10 23:45 ` Andrew Morton 2009-02-11 11:15 ` Mel Gorman 2009-02-11 9:43 ` Andy Whitcroft 2009-02-11 10:30 ` Mel Gorman 2009-02-11 12:03 ` Andy Whitcroft 2009-02-11 14:20 ` Mel Gorman 2009-02-11 16:03 ` Andy Whitcroft 2009-02-11 16:34 ` Mel Gorman 2009-02-11 16:43 ` Andy Whitcroft
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: linkBe 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.