From: Robert Hancock <hancockrwd@gmail.com>
To: David Fries <david@fries.net>
Cc: linux-kernel@vger.kernel.org, d.stussy@yahoo.com,
Joao Ramos <joao.ramos@inov.pt>,
Linus Torvalds <torvalds@osdl.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [bisected] 2.6.31 regression sis5513 PIO Mode 0 hang
Date: Sat, 03 Oct 2009 18:57:42 -0600 [thread overview]
Message-ID: <4AC7F306.2040409@gmail.com> (raw)
In-Reply-To: <20091003025415.GA28295@spacedout.fries.net>
On 10/02/2009 08:54 PM, David Fries wrote:
> I just did a git bisection from 2.6.30 to 2.6.31 because 2.6.31 will
> not boot on this system. d.stussy@yahoo.com's post September 12th
> looks the same, different CPU but both have sis5513 IDE chips. His
> would normally init the ethernet chip next, mine would do PS/2 next,
> both hang right after the Uniform CD-ROM message.
>
> This was bisected down to chaging PIO mode 0 for probing. What
> problem was that patch trying to solve? Reverting just that patch at
> the top of 2.6.31 tree works. I can test patches.
>
> Assigned bugzilla.kernel.org bug 14310
Well, it's the right thing to do (libata does it) but presumably doing
that in old IDE is triggering some kind of bug. Unless there's a
specific problem it was solving, or someone is interested in debugging
in detail (I'm certainly not interested in drivers/ide) it should likely
be reverted as we've done without it for so long..
next prev parent reply other threads:[~2009-10-04 0:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-03 2:54 [bisected] 2.6.31 regression sis5513 PIO Mode 0 hang David Fries
[not found] ` <328926.65135.qm@web84205.mail.re3.yahoo.com>
2009-10-03 13:01 ` David Fries
2009-10-04 0:57 ` Robert Hancock [this message]
2009-10-05 2:55 ` David Fries
2009-10-05 3:58 ` David Miller
2009-10-06 4:06 ` David Fries
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=4AC7F306.2040409@gmail.com \
--to=hancockrwd@gmail.com \
--cc=d.stussy@yahoo.com \
--cc=david@fries.net \
--cc=joao.ramos@inov.pt \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.