From: rct@gherkin.frus.com (Bob Tracy)
To: linux-kernel@vger.kernel.org
Cc: jikos@jikos.cz, bzolnier@gmail.com
Subject: Re: [BUG] no boot with 2.6.21-rc3 and later
Date: Mon, 19 Mar 2007 19:43:53 -0600 (CST) [thread overview]
Message-ID: <20070320014353.B1B05DBA1@gherkin.frus.com> (raw)
Jiri wrote:
> Looks like it's related to some change in drivers/ide. As there have been
> only 13 patches in this area between rc2 and rc3, it should take only 3 or
> 4 reboots to figure the offending patch using git-bisect - could you
> please give it a try?
I applied all of the 2.6.21-rc2-rc3 incremental patch except for the
portion applicable to "drivers/ide" files. The problem seems to be
elsewhere: 2.6.21-rc3 minus the drivers/ide changes still hangs at the
same spot during the boot process.
Any ideas where to look next? Thanks!
--
-----------------------------------------------------------------------
Bob Tracy WTO + WIPO = DMCA? http://www.anti-dmca.org
rct@frus.com
-----------------------------------------------------------------------
next reply other threads:[~2007-03-20 1:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-20 1:43 Bob Tracy [this message]
2007-03-20 7:14 ` [BUG] no boot with 2.6.21-rc3 and later Jiri Kosina
-- strict thread matches above, loose matches on Subject: below --
2007-03-21 19:54 Bob Tracy
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-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=20070320014353.B1B05DBA1@gherkin.frus.com \
--to=rct@gherkin.frus.com \
--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