From: Andrew Morton <akpm@linux-foundation.org>
To: Nicolas.Mailhot@LaPoste.net
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
"bugme-daemon@kernel-bugs.osdl.org"
<bugme-daemon@bugzilla.kernel.org>
Subject: Re: [Bug 8136] 2.6.21-rc2-mm2 won't boot
Date: Tue, 6 Mar 2007 16:15:59 -0800 [thread overview]
Message-ID: <20070306161559.e0c7ee71.akpm@linux-foundation.org> (raw)
In-Reply-To: <200703062336.l26NaTZA026385@fire-2.osdl.org>
On Tue, 6 Mar 2007 15:36:29 -0800
bugme-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=8136
>
Let's take this to email.
>
>
>
> ------- Additional Comments From Nicolas.Mailhot@LaPoste.net 2007-03-06 15:36 -------
> Created an attachment (id=10631)
> --> (http://bugzilla.kernel.org/attachment.cgi?id=10631&action=view)
> Printscreen with vesfg disabled and earlyprintk=vga
>
So rc2-mm2 panics due to "MP-BIOS bug: 8254 timer not connected to IO-APIC" and
rc2-mm1 does not.
Could be ACPI, could be x86_64 timer changes, could be something else.
Would you have time to bisect it?
http://www.zip.com.au/~akpm/linux/patches/stuff/bisecting-mm-trees.txt
explains how.
If so, I'd suggest you drill in on the patches between
x86_64-mm-defconfig-update.patch and
optimize-and-simplify-get_cycles_sync.patch: the x86 changes.
next parent reply other threads:[~2007-03-07 0:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200703062336.l26NaTZA026385@fire-2.osdl.org>
2007-03-07 0:15 ` Andrew Morton [this message]
2007-03-07 0:32 ` [Bug 8136] 2.6.21-rc2-mm2 won't boot Rafael J. Wysocki
2007-03-08 21:33 ` Rafael J. Wysocki
2007-03-07 7:36 ` Nicolas Mailhot
2007-03-07 22:06 ` Nicolas Mailhot
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=20070306161559.e0c7ee71.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Nicolas.Mailhot@LaPoste.net \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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