From: Darren Salt <linux@youmustbejoking.demon.co.uk>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Ingo Molnar <mingo@elte.hu>,
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>,
Corentin Chary <corentincj@iksaif.net>
Subject: Re: Oopses and ACPI problems (Linus 2.6.29-rc4)
Date: Tue, 24 Feb 2009 15:29:36 +0000 [thread overview]
Message-ID: <50381ED1F0%linux@youmustbejoking.demon.co.uk> (raw)
In-Reply-To: <20090223163934.GA20041@srcf.ucam.org>
I demand that Matthew Garrett may or may not have written...
> Can you try this (entirely untested - I don't have access to the hardware
> right now) patch? It should register the eee code with the PCI hotplug
> core. With luck that'll avoid the oops.
> diff --git a/drivers/platform/x86/Kconfig b/drivers/platform/x86/Kconfig
> index b3866ad..75a560b 100644
> --- a/drivers/platform/x86/Kconfig
> +++ b/drivers/platform/x86/Kconfig
> @@ -307,6 +307,7 @@ config EEEPC_LAPTOP
> select BACKLIGHT_CLASS_DEVICE
> select HWMON
> select RFKILL
> + select HOTPLUG_PCI
Not HOTPLUG_PCI_PCIE?
With that selected (I see no point in testing this otherwise) *and*
pciehp_force=1, I get -EBUSY when the hotplug slot registration is attempted
and no wireless, bluetooth or hot key reporting; wireless & bluetooth are
switched off at that point (I made sure that they were enabled via BIOS
setup). Without that option, all is fine.
(As usual with my kernel builds, these are built in.)
[snip]
--
| Darren Salt | linux or ds at | nr. Ashington, | Toon
| RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army
| + Travel less. Share transport more. PRODUCE LESS CARBON DIOXIDE.
The man who raises a fist has run out of ideas.
next prev parent reply other threads:[~2009-02-24 15:46 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 [this message]
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=50381ED1F0%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=mjg59@srcf.ucam.org \
--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: 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.