From: Darren Salt <linux@youmustbejoking.demon.co.uk> To: Ingo Molnar <mingo@elte.hu> Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>, Len Brown <lenb@kernel.org>, Linus Torvalds <torvalds@linux-foundation.org>, Andrew Morton <akpm@linux-foundation.org>, Jesse Barnes <jbarnes@virtuousgeek.org>, Thomas Gleixner <tglx@linutronix.de>, "H. Peter Anvin" <hpa@zytor.com>, Matthew Garrett <mjg@redhat.com>, Corentin Chary <corentincj@iksaif.net> Subject: Re: Oopses and ACPI problems (Linus 2.6.29-rc4) Date: Tue, 10 Feb 2009 14:12:44 +0000 [thread overview] Message-ID: <5030E21460%linux@youmustbejoking.demon.co.uk> (raw) In-Reply-To: <20090209234911.GB862@elte.hu> [Adding Matthew Garrett & Corentin Chary to Cc] I demand that Ingo Molnar may or may not have written... > * Darren Salt <linux@youmustbejoking.demon.co.uk> 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. > Various folks Cc:-ed. There's been a late, rather large ACPI merge, so > one post-rc3 suspect would be one of these commits: [snip] > 7695fb0: eeepc-laptop: fix oops when changing backlight brightness during eeepc-laptop init No, that one's harmless :-) [snip] > 2b25c9f: eeepc-laptop: use netlink interface That one makes acpid (apparently) useless. The rest of the commit description is: To be prepared for /proc/acpi/event removal we export events also through generic netlink interface. Note that "also". The actual effect of the patch is "instead". Adding the two removed lines (but removing the post-increment of the event count) fixes this. > 5740294: eeepc-laptop: Implement rfkill hotplugging in eeepc-laptop Reverting this fixes the rfkill oops; things work correctly again. I don't know why this appears to be needed, since things work fine without this patch ‒ both Fn-F2 and echoing to /sys/class/rfkill/rfkill0/state ‒ even when I start up with init=/bin/sh and test directly from that shell. (901; BIOS rev. 1808.) [snip] > 2a7dc0d: asus-laptop: use generic netlink interface That one also says "also" where it should say "instead" (not that it affects me). ... oh yes, there's a long delay between output of these two lines during boot: input: ETPS/2 Elantech Touchpad as /class/input/input5 eeepc: Hotkey init flags 0x41 (not seen in .28 or .28.1; not checked later .28.*.) Anyway, a patch for the ACPI reporting problems will follow this message. [snip] -- | Darren Salt | linux or ds at | nr. Ashington, | Toon | RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army | + Output less CO2 => avoid massive flooding. TIME IS RUNNING OUT *FAST*. Life is that brief interlude between nothingness and eternity. -- 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: Darren Salt <linux@youmustbejoking.demon.co.uk> To: Ingo Molnar <mingo@elte.hu> Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>, Len Brown <lenb@kernel.org>, Linus Torvalds <torvalds@linux-foundation.org>, Andrew Morton <akpm@linux-foundation.org>, Jesse Barnes <jbarnes@virtuousgeek.org>, Thomas Gleixner <tglx@linutronix.de>, "H. Peter Anvin" <hpa@zytor.com>, Matthew Garrett <mjg@redhat.com>, Corentin Chary <corentincj@iksaif.net> Subject: Re: Oopses and ACPI problems (Linus 2.6.29-rc4) Date: Tue, 10 Feb 2009 14:12:44 +0000 [thread overview] Message-ID: <5030E21460%linux@youmustbejoking.demon.co.uk> (raw) In-Reply-To: <20090209234911.GB862@elte.hu> [Adding Matthew Garrett & Corentin Chary to Cc] I demand that Ingo Molnar may or may not have written... > * Darren Salt <linux@youmustbejoking.demon.co.uk> 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. > Various folks Cc:-ed. There's been a late, rather large ACPI merge, so > one post-rc3 suspect would be one of these commits: [snip] > 7695fb0: eeepc-laptop: fix oops when changing backlight brightness during eeepc-laptop init No, that one's harmless :-) [snip] > 2b25c9f: eeepc-laptop: use netlink interface That one makes acpid (apparently) useless. The rest of the commit description is: To be prepared for /proc/acpi/event removal we export events also through generic netlink interface. Note that "also". The actual effect of the patch is "instead". Adding the two removed lines (but removing the post-increment of the event count) fixes this. > 5740294: eeepc-laptop: Implement rfkill hotplugging in eeepc-laptop Reverting this fixes the rfkill oops; things work correctly again. I don't know why this appears to be needed, since things work fine without this patch ‒ both Fn-F2 and echoing to /sys/class/rfkill/rfkill0/state ‒ even when I start up with init=/bin/sh and test directly from that shell. (901; BIOS rev. 1808.) [snip] > 2a7dc0d: asus-laptop: use generic netlink interface That one also says "also" where it should say "instead" (not that it affects me). ... oh yes, there's a long delay between output of these two lines during boot: input: ETPS/2 Elantech Touchpad as /class/input/input5 eeepc: Hotkey init flags 0x41 (not seen in .28 or .28.1; not checked later .28.*.) Anyway, a patch for the ACPI reporting problems will follow this message. [snip] -- | Darren Salt | linux or ds at | nr. Ashington, | Toon | RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army | + Output less CO2 => avoid massive flooding. TIME IS RUNNING OUT *FAST*. Life is that brief interlude between nothingness and eternity.
next prev parent reply other threads:[~2009-02-10 14:55 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 [this message] 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 ` Oopses and ACPI problems (Linus 2.6.29-rc4) yakui_zhao 2009-02-10 1:06 ` 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=5030E21460%linux@youmustbejoking.demon.co.uk \ --to=linux@youmustbejoking.demon.co.uk \ --cc=akpm@linux-foundation.org \ --cc=corentincj@iksaif.net \ --cc=hpa@zytor.com \ --cc=jbarnes@virtuousgeek.org \ --cc=lenb@kernel.org \ --cc=linux-acpi@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=mingo@elte.hu \ --cc=mjg@redhat.com \ --cc=rjw@sisk.pl \ --cc=tglx@linutronix.de \ --cc=torvalds@linux-foundation.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: 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.