The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Mikko Rapeli <mikko.rapeli@iki.fi>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: early boot lockup with 2.6.23-rc1
Date: Sat, 11 Aug 2007 07:42:18 +0300	[thread overview]
Message-ID: <20070811044218.GA1899@nalle> (raw)
In-Reply-To: <20070810192030.GB1916@nalle>

On Fri, Aug 10, 2007 at 10:20:31PM +0300, Mikko Rapeli wrote:
> I've bisected thus far, if it helps:

Bisect came to this conclusion:

git-bisect start
# good: [4eb6bf6bfb580afaf1e1a1d30cba17a078530cf4] lots-of-architectures: enable arbitary speed tty support
git-bisect good 4eb6bf6bfb580afaf1e1a1d30cba17a078530cf4
# bad: [773208946a132fb733ba273ee8562814f828cc28] Revert "USB: fix gregkh-usb-usb-use-menuconfig-objects"
git-bisect bad 773208946a132fb733ba273ee8562814f828cc28
# bad: [dc690d8ef842b464f1c429a376ca16cb8dbee6ae] Merge master.kernel.org:/pub/scm/linux/kernel/git/gregkh/driver-2.6
git-bisect bad dc690d8ef842b464f1c429a376ca16cb8dbee6ae
# good: [15028aad00ddf241581fbe74a02ec89cbb28d35d] [TG3]: Update version to 3.78.
git-bisect good 15028aad00ddf241581fbe74a02ec89cbb28d35d
# bad: [82afee684fe3badaf5ee3fc5b6fda687d558bfb5] Merge master.kernel.org:/pub/scm/linux/kernel/git/cooloney/blackfin-2.6
git-bisect bad 82afee684fe3badaf5ee3fc5b6fda687d558bfb5
# bad: [c39736823232bc3ca113c8228fa852c09fba300e] Remove old i386 setup code
git-bisect bad c39736823232bc3ca113c8228fa852c09fba300e
# good: [5be865661516263d90317a6b35b588a2d7c3cb55] String-handling functions for the new x86 setup code.
git-bisect good 5be865661516263d90317a6b35b588a2d7c3cb55
# good: [3b53d3045bbb8ea3c9dce663b102eab0903817c5] MCA support for new x86 setup code
git-bisect good 3b53d3045bbb8ea3c9dce663b102eab0903817c5
# good: [7052fdd890bda0b3904674b69a1d24aec0a10d67] Code for actual protected-mode entry
git-bisect good 7052fdd890bda0b3904674b69a1d24aec0a10d67
# good: [f2d98ae63dc64dedb00499289e13a50677f771f9] Linker script for the new x86 setup code
git-bisect good f2d98ae63dc64dedb00499289e13a50677f771f9
# bad: [91a6c462b02d8dc02dbe95e5a407d78078a38d01] Use the new x86 setup code for x86-64; unify with i386
git-bisect bad 91a6c462b02d8dc02dbe95e5a407d78078a38d01
# bad: [4fd06960f120e02e9abc802a09f9511c400042a5] Use the new x86 setup code for i386
git-bisect bad 4fd06960f120e02e9abc802a09f9511c400042a5



      parent reply	other threads:[~2007-08-11  4:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-08 22:31 early boot lockup with 2.6.23-rc1 Mikko Rapeli
2007-08-09  0:02 ` Andrew Morton
2007-08-09  4:57   ` Mikko Rapeli
2007-08-09  5:09     ` Andrew Morton
2007-08-09  5:24       ` Mikko Rapeli
2007-08-09  7:25 ` H. Peter Anvin
2007-08-09  7:53   ` Mikko Rapeli
2007-08-09 18:23   ` Mikko Rapeli
2007-08-09 19:43     ` Mikko Rapeli
2007-08-09 22:26       ` H. Peter Anvin
2007-08-10 16:33         ` Mikko Rapeli
2007-08-10 16:45           ` H. Peter Anvin
2007-08-10 19:20             ` Mikko Rapeli
2007-08-10 19:32               ` H. Peter Anvin
2007-08-10 19:50                 ` Mikko Rapeli
2007-08-10 22:38               ` Mikko Rapeli
2007-08-10 22:50                 ` H. Peter Anvin
2007-08-11  4:42               ` Mikko Rapeli [this message]

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=20070811044218.GA1899@nalle \
    --to=mikko.rapeli@iki.fi \
    --cc=hpa@zytor.com \
    --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