linux-kernel - Re: linux-next Regression: Unable to locate IOAPIC

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]

Date:	Tue, 10 Jun 2008 22:47:53 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	webmaster@...gonslave.de
Cc:	Daniel Exner <dex@...gonslave.de>, linux-kernel@...r.kernel.org,
	linux-next@...r.kernel.org, linux-acpi@...r.kernel.org
Subject: Re: linux-next Regression: Unable to locate IOAPIC

On Tue, 10 Jun 2008 22:29:10 +0200 Daniel Exner <dex@...gonslave.de> wrote:

> 
> Andrew Morton wrote:
> > On Fri, 6 Jun 2008 19:30:28 +0200 Daniel Exner <dex@...gonslave.de> wrote:
> > > Andrew Morton wrote:
> > > > (cc linux-acpi)
> > > >
> > > > On Thu, 5 Jun 2008 11:00:12 +0200 Daniel Exner <dex@...gonslave.de> 
> wrote:
> > > > > Hi!
> > > > >
> > > > > (Added myself to CC, because I'm not subscribed)
> > > > >
> > > > > with linux-next snapshot 20080604 my Laptop morphes into sitting duck
> > > > > and I think this is due to this:
> > > >
> > > > I assume 2.6.26-rc5 is OK?
> > >
> > > Indeed.. just tried it with (nearly) the same config: no unable to locate
> > > IOAPIC
> > >
> > > Will try todays next snapshot above -rc5 now.
> >
> > OK, thanks.
> >
> > It would be great if you could test 2.6.26-rc5 plus
> > http://userweb.kernel.org/~akpm/git-acpi.patch.  That'll allow us to
> > confirm that the regression is due to changes in the acpi tree.
> Sorry for the delay.. real-life you know ;)
> 
> I guess you'd expect me to confirm the behavior on rc5 with this patch aplied, 
> but .. well this Kernel works!
> 
> So I think the regression is NOT in the acpi tree. Perhaps pci subsystem?

There is behind-the-scenes finger-pointing going on ;)

I don't think we know what caused this regression, sorry.

> If I find time I'll try bisecting it..

That would be fantastic, thanks.  Please don't let us merge this
regression into 2.6.27.  We have a few weeks.

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