linux-kernel - Re: acpi_ex_system_memory_space

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: <1250579915.13743.8.camel@minggr.sh.intel.com>
Date:	Tue, 18 Aug 2009 15:18:35 +0800
From:	Lin Ming <ming.m.lin@...el.com>
To:	Sergey Senozhatsky <sergey.senozhatsky@...il.com>
Cc:	"Brown, Len" <len.brown@...el.com>,
	"Moore, Robert" <robert.moore@...el.com>,
	"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: acpi_ex_system_memory_space_handler oops

On Tue, 2009-08-18 at 15:13 +0800, Sergey Senozhatsky wrote:
> On (08/17/09 21:22), Lin Ming wrote:
> > > rc6-git2
> > > 25 successful reboots.
> > >
> > > I'll need some more time to test against rc5.
> > >
> > > /*should I also test DSDT in case region-debug.patch fixed the problem?*/
> > 
> > Yes, please also help to test the custome DSDT.
> > region-debug.patch is just a debug patch.
> > We need to root cause the problem clearly and then work out a clean solution.
> > 
> 
> Hi, Lin
> Looks like DSDT didn't solve the problem (oops on 4th reboot).
> 
> So:
> region-debug.patch	+
> DSDT			-
> 
> /* Is that possible? */

Yes, that is possible. 
The same aml method is re-entered when interpreter lock is released.
So you still see AE_ALREADY_EXISTS error with the custom DSDT, right?

Thanks for the info, I'll continue to look at this issue.
And would you please test the region-debug.patch multiple times to
verify if it really fixes the bug?

Thanks,
Lin Ming

--
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/