From: rct@gherkin.frus.com (Bob Tracy)
To: linux-kernel@vger.kernel.org
Cc: bunk@stusta.de, jikos@jikos.cz, bzolnier@gmail.com
Subject: Re: [BUG] no boot with 2.6.21-rc3 and later
Date: Wed, 21 Mar 2007 13:54:50 -0600 (CST) [thread overview]
Message-ID: <20070321195450.36D5EDBA1@gherkin.frus.com> (raw)
I originally wrote:
> Platform is a Dell CPxJ 650GT notebook. Attempts to boot 2.6.21-rc3
> and -rc4 produce the following console output:
>
> (apparently normal boot)
> ...
> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
> ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
> PIIX4: IDE controller at PCI slot 0000:00:07.1
> PIIX4: chipset revision 1
> PIIX4: not 100% native mode: will probe irqs later
> ide0: BM-DMA at 0x0860-0x0867, BIOS settings: hda:DMA, hdb:pio
> ide1: BM-DMA at 0x0868-0x086f, BIOS settings: hdc:DMA, hdd:pio
> (hangs here)
>
> The next two lines of output for 2.6.21-rc2 and earlier are:
> Probing IDE interface ide0...
> hda: TOSHIBA MK3017GAP, ATA DISK drive
After nine iterations of git-bisect --> compile --> reboot over the past
two days, the commit that caused this problem has been identified.
6bb74df481223731af6c7e0ff3adb31f6442cfcd is first bad commit
commit 6bb74df481223731af6c7e0ff3adb31f6442cfcd
Author: john stultz <johnstul@us.ibm.com>
Date: Mon Mar 5 00:30:50 2007 -0800
[PATCH] clocksource init adjustments (fix bug #7426)
This patch resolves the issue found here:
http://bugme.osdl.org/show_bug.cgi?id=7426
The basic summary is:
(omitted for brevity)
Signed-off-by: John Stultz <johnstul@us.ibm.com>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: "David S. Miller" <davem@davemloft.net>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
:040000 040000 b259cf01f6ad791a0f58c9956e6e0111cb9aa310 0e8fbf31c0bae9ca6039fc7781b53c12f7a67592 M arch
:040000 040000 19bd5cf3c55c6b7947ec66b68eab643c99f15bb8 ef8fda0445287e34eeb466985901ca64191b6539 M drivers
:040000 040000 4f84ad7bdf509ed83efd95d174796f1a6a948b0e 51624663be2fdce8aaeb3b49e188520aa3735d90 M include
:040000 040000 ef82986d4590fed84b9a128da90e65f7e43f43a9 778d0cf7273d7514b436ca4e91a6948f34694972 M kernel
--
-----------------------------------------------------------------------
Bob Tracy WTO + WIPO = DMCA? http://www.anti-dmca.org
rct@frus.com
-----------------------------------------------------------------------
next reply other threads:[~2007-03-21 19:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-21 19:54 Bob Tracy [this message]
2007-03-21 20:18 ` Bartlomiej Zolnierkiewicz
2007-03-21 21:34 ` john stultz
2007-03-21 22:00 ` Bob Tracy
2007-03-21 22:24 ` john stultz
2007-03-22 3:45 ` Bob Tracy
2007-03-22 18:35 ` john stultz
2007-03-22 19:14 ` Bob Tracy
2007-03-22 19:25 ` john stultz
2007-03-22 19:39 ` Bob Tracy
2007-03-22 19:56 ` john stultz
2007-03-22 20:13 ` Bob Tracy
2007-03-22 19:43 ` Thomas Gleixner
2007-03-22 20:25 ` [PATCH] correct slow acpi_pm rating (fixes no boot with 2.6.21-rc3 and later) john stultz
-- strict thread matches above, loose matches on Subject: below --
2007-03-20 1:43 [BUG] no boot with 2.6.21-rc3 and later Bob Tracy
2007-03-20 7:14 ` Jiri Kosina
2007-03-18 1:09 Bob Tracy
2007-03-18 18:59 ` Jiri Kosina
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=20070321195450.36D5EDBA1@gherkin.frus.com \
--to=rct@gherkin.frus.com \
--cc=bunk@stusta.de \
--cc=bzolnier@gmail.com \
--cc=jikos@jikos.cz \
--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
all inboxes | Powered by JetHome®