linux-kernel - Re: 2.6.24-rc3-mm1 - Kernel Panic on IO-APIC

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: <20071126141713.3dcd492b.akpm@linux-foundation.org>
Date:	Mon, 26 Nov 2007 14:17:13 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Jiri Slaby <jirislaby@...il.com>
Cc:	mingo@...e.hu, riel@...hat.com, kamalesh@...ux.vnet.ibm.com,
	linux-kernel@...r.kernel.org, apw@...dowen.org,
	balbir@...ux.vnet.ibm.com, linux-acpi@...r.kernel.org,
	tglx@...utronix.de, clameter@....com
Subject: Re: 2.6.24-rc3-mm1 - Kernel Panic on IO-APIC

On Mon, 26 Nov 2007 23:08:33 +0100
Jiri Slaby <jirislaby@...il.com> wrote:

> On 11/26/2007 09:45 PM, Ingo Molnar wrote:
> > * Andrew Morton <akpm@...ux-foundation.org> wrote:
> > 
> >> On Mon, 26 Nov 2007 14:39:43 -0500
> >> Rik van Riel <riel@...hat.com> wrote:
> >>
> >>> On Tue, 20 Nov 2007 22:18:39 -0800
> >>> Andrew Morton <akpm@...ux-foundation.org> wrote:
> >>>
> >>>>> ..MP-BIOS bug: 8254 timer not connected to IO-APIC
> >>>>> Kernel panic - not syncing: IO-APIC + timer doesn't work! Try using the 'noapic' kernel parameter
> >>>> ACPI or x86 breakage, I guess.
> >>>>
> >>>> Did 'noapic' work?
> >>> I got the same bug as above, 'noapic' gets past that point 
> >> We still don't know what caused this, afaik.
> > 
> > yes. Is it a regression? If yes, could someone try to bisect it so that 
> > we can fix it? If it's caused by x86.git then the 'mm' branch of the x86 
> > git tree can be used for bisection:
> > 
> >    git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-x86.git
> 
> I did, but it's hard, if you don't know the BAD point. HEAD boots fine and 'x86:
> randomize brk' too (the top of git-x86.patch).

So the bug wasn't in git-x86 in 2.6.24-rc3-mm1.

But it might be in there now, as some patches got moved over.

Or it could be git-acpi.  Or lots of other things.

> Andrew, how do you pull it, git
> #mm doesn't fit to the ids from the patch.

The -mm git tree reimports the plain git-foo.patch files back into a new
git tree, so the commit IDs won't line up.

The way to find the culprit patch in 2.6.24-rc3-mm1 is
http://www.zip.com.au/~akpm/linux/patches/stuff/bisecting-mm-trees.txt.  It
will be quite quick.

> Maybe if you can emit a broken-out with the fresh pull to test?

http://userweb.kernel.org/~akpm/mmotm/ is current.  But it probably won't
compile.  I'd suggest bisecting 2.6.24-rc3-mm1 would be easier.  
-
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/