From: Patrick Dreker <patrick@dreker.de>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: IDE Timeout problem on Intel PIIX3 (Triton 2) chipset
Date: Tue, 29 Jun 2004 16:48:35 +0200 [thread overview]
Message-ID: <200406291648.35114.patrick@dreker.de> (raw)
In-Reply-To: <200406282221.48896.bzolnier@elka.pw.edu.pl>
Am Montag, 28. Juni 2004 22:21 schrieb Bartlomiej Zolnierkiewicz:
> > What can I do to debug this problem?
> "diff -u" on "lspci -s 07.1 -xxx" outputs for 2.4.20 and 2.4.21 kernels.
>
> Doing bisection search on 2.4.21-pre kernels would also help.
2.4.21-pre1 is the first non-working kernel, 2.4.20 works. When generating the
configs for 2.4.21-pre1 (make oldconfig based on the working 2.4.20 config) I
was asked "Use IDE Taskfile I/O" which defaulted to no and I kept that
default (i.e. "Don't use Taskfile I/O").
lspci -s 07.1 -xxx shows no difference between a working (2.4.20) kernel and a
non-working (2.4.21-pre1) kernel.
This caught my eye, but was probably obvious to you:
2.4.21-pre1 reports IDE Version 7.00beta-2.4 while 2.4.20 reports version 6.31
Patrick
--
Patrick Dreker
GPG KeyID : 0xFCC2F7A7 (Patrick Dreker)
Fingerprint: 7A21 FC7F 707A C498 F370 1008 7044 66DA FCC2 F7A7
Key available from keyservers
next prev parent reply other threads:[~2004-06-29 14:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-28 12:48 IDE Timeout problem on Intel PIIX3 (Triton 2) chipset Patrick Dreker
2004-06-28 20:21 ` Bartlomiej Zolnierkiewicz
2004-06-28 23:25 ` Patrick Dreker
2004-06-29 14:48 ` Patrick Dreker [this message]
[not found] <E1Bevgk-0007jR-4F@rhn.tartu-labor>
2004-06-28 18:47 ` Meelis Roos
-- strict thread matches above, loose matches on Subject: below --
2004-06-28 20:27 Chris Rankin
2004-06-29 1:21 ` Patrick Dreker
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=200406291648.35114.patrick@dreker.de \
--to=patrick@dreker.de \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--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 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.