linux-kernel - Re: ACPI crash on lid close

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20081110172946.GA3512@srcf.ucam.org>
Date:	Mon, 10 Nov 2008 17:29:46 +0000
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	Sergio Monteiro Basto <sergio@...giomb.no-ip.org>
Cc:	linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: ACPI crash on lid close - SMP race?

On Mon, Nov 10, 2008 at 05:26:35PM +0000, Sergio Monteiro Basto wrote:
> Hi, About this _DOS , I reported this problem a long time ago, which now
> is on http://bugzilla.kernel.org/show_bug.cgi?id=6001
> Could you put yours comment on it ? 
> 
> On fedora stock kernel, appears one patch, (Now I see that you are the
> author :) ) 
> 
> I tested your patch and it works for me ! 

Yeah, that's the "safe" patch which stops us executing the codepath that 
breaks, but also means I don't get display switch events. Having it set 
to 1 means executing BIOS code that's likely to interfere with the rest 
of the system, so a crash isn't surprising. But a setting of 0 *should* 
be safe, and I'm quite confused as to why it's exploding.

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