From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Garrett Subject: Re: Oopses and ACPI problems (Linus 2.6.29-rc4) Date: Tue, 10 Feb 2009 15:04:31 +0000 Message-ID: <20090210150431.GA26798@srcf.ucam.org> References: <20090209234911.GB862@elte.hu> <5030E21460%linux@youmustbejoking.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from cavan.codon.org.uk ([93.93.128.6]:52552 "EHLO vavatch.codon.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753531AbZBJPEk (ORCPT ); Tue, 10 Feb 2009 10:04:40 -0500 Content-Disposition: inline In-Reply-To: <5030E21460%linux@youmustbejoking.demon.co.uk> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Ingo Molnar , linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org, "Rafael J. Wysocki" , Len Brown , Linus Torvalds On Tue, Feb 10, 2009 at 02:12:44PM +0000, Darren Salt wrote: > 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 th= is patch > =E2=80=92 both Fn-F2 and echoing to /sys/class/rfkill/rfkill0/state =E2= =80=92 even when I > start up with init=3D/bin/sh and test directly from that shell. If this is BIOS version specific I'm going to be upset, but the general= =20 case behaviour is that rfkill only works on the 901 if you either (a)=20 pass force=3D1 to pciehp (which you shouldn't) or (b) have native suppo= rt=20 in a driver. My /guess/ is that you've got pciehp loaded, and there's=20 some kind of awkward race between it and eeepc-laptop. > 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.*.) BIOS bug. There's an explicit delay in the eee bios for some reason, an= d=20 I haven't found any straightforward way to avoid it. --=20 Matthew Garrett | mjg59@srcf.ucam.org -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html