From: Andrew Morton <akpm@linux-foundation.org>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: mingo@elte.hu, riel@redhat.com, kamalesh@linux.vnet.ibm.com,
linux-kernel@vger.kernel.org, apw@shadowen.org,
balbir@linux.vnet.ibm.com, linux-acpi@vger.kernel.org,
tglx@linutronix.de, clameter@sgi.com
Subject: Re: 2.6.24-rc3-mm1 - Kernel Panic on IO-APIC
Date: Mon, 26 Nov 2007 14:17:13 -0800 [thread overview]
Message-ID: <20071126141713.3dcd492b.akpm@linux-foundation.org> (raw)
In-Reply-To: <474B43E1.9080407@gmail.com>
On Mon, 26 Nov 2007 23:08:33 +0100
Jiri Slaby <jirislaby@gmail.com> wrote:
> On 11/26/2007 09:45 PM, Ingo Molnar wrote:
> > * Andrew Morton <akpm@linux-foundation.org> wrote:
> >
> >> On Mon, 26 Nov 2007 14:39:43 -0500
> >> Rik van Riel <riel@redhat.com> wrote:
> >>
> >>> On Tue, 20 Nov 2007 22:18:39 -0800
> >>> Andrew Morton <akpm@linux-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.
next prev parent reply other threads:[~2007-11-26 22:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071120204525.ff27ac98.akpm@linux-foundation.org>
[not found] ` <4743CC0B.9000508@linux.vnet.ibm.com>
2007-11-21 6:18 ` 2.6.24-rc3-mm1 - Kernel Panic on IO-APIC Andrew Morton
2007-11-21 9:22 ` Kamalesh Babulal
2007-11-21 9:29 ` Andrew Morton
2007-11-21 9:43 ` Kamalesh Babulal
2007-11-21 19:33 ` Torsten Kaiser
2007-11-22 10:04 ` Kirill A. Shutemov
2007-11-21 19:22 ` Len Brown
2007-11-21 19:48 ` Torsten Kaiser
2007-11-24 0:49 ` Alexey Dobriyan
2007-11-26 19:39 ` Rik van Riel
2007-11-26 20:33 ` Andrew Morton
2007-11-26 20:45 ` Ingo Molnar
2007-11-26 22:08 ` Jiri Slaby
2007-11-26 22:17 ` Andrew Morton [this message]
2007-11-26 22:22 ` Jiri Slaby
2007-11-26 23:14 ` Jiri Slaby
2007-11-26 23:28 ` Andrew Morton
2007-11-27 17:50 ` Rik van Riel
2007-11-26 20:54 ` Rik van Riel
2007-11-26 20:56 ` Christoph Lameter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071126141713.3dcd492b.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=clameter@sgi.com \
--cc=jirislaby@gmail.com \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=riel@redhat.com \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox