Subject: Re: ACPI crash on lid close - SMP race?
From: Zhang Rui <rui.zhang@intel.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: "linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
       "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
In-Reply-To: <20081110161105.GA2041@srcf.ucam.org>
References: <20081110161105.GA2041@srcf.ucam.org>
Content-Type: text/plain
Date: Tue, 11 Nov 2008 09:27:14 +0800
Message-Id: <1226366834.15014.60.camel@rzhang-dt>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1382
Lines: 31

well, there is a bug report for this problem:
http://bugzilla.kernel.org/show_bug.cgi?id=11259

and there are some bug reports for a similar problem (system crashes on
lid close if _DOS=1, but on a UP platform).
http://bugzilla.kernel.org/show_bug.cgi?id=6001#c49

but unfortunately we haven't made any progress in this issue. :(

thanks,
rui

On Tue, 2008-11-11 at 00:11 +0800, Matthew Garrett wrote:
> If the _DOS flag on my HP 2510p is set to 0 (ie, signal OS when screen 
> notification is requested, don't change automatically) then it'll crash 
> on random lid open/closes. The trace generally makes little sense and 
> depends on the kernel version and phase of the moon. I'd ignored this as 
> firmware brokenness up until lately, but since having _DOS set to 0 is 
> the only way to get a notification when the display switch key is 
> pressed on this machine I'd be interested in fixing it properly. 
> 
> Unfortunately, I've got no real idea what on earth is going on. The only 
> clue I've found so far is that booting with maxcpus=1 leaves it working 
> perfectly. What parts of the ACPI stack could be triggering this?
> 

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/