From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-kernel@vger.kernel.org
Cc: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Subject: SOLVED - Testing IDE-TCQ and Taskfile - doesn't work nicely:)
Date: Wed, 25 Jun 2003 20:22:12 +0200 [thread overview]
Message-ID: <20030625182210.GI29233@lug-owl.de> (raw)
In-Reply-To: <Pine.SOL.4.30.0306250107180.17106-100000@mion.elka.pw.edu.pl>
[-- Attachment #1: Type: text/plain, Size: 1585 bytes --]
On Wed, 2003-06-25 01:08:13 +0200, Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
wrote in message <Pine.SOL.4.30.0306250107180.17106-100000@mion.elka.pw.edu.pl>:
> On Wed, 25 Jun 2003, Jan-Benedict Glaw wrote:
> > On Tue, 2003-06-24 15:44:36 +0200, Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
> > wrote in message <Pine.SOL.4.30.0306241543050.23584-100000@mion.elka.pw.edu.pl>:
> >
> > > Corrected patch below...
> >
> > Taking this 2nd IDE patch, my boot-up looks as shown below. I still have
>
> Thanks for testing, it looks okay now.
>
> > to test the taskfile thing again, but I cannot find my girlfriends
> > digital camera right now:)
Found the cam, downloaded any old pics, recompiled with taskfile I/O and
- nothing. 2.5.73 + your second IDE patch do work flawlessly on my old
box. The "clack clack clack" went away is if had never been
there...
So - thanks a lot for looking at my problem. Please feed your patch to
Linus as it seems to actually solve (at least my) problems.
However, allow me to ask why this occured never bevore (for other
people)? Do they all have only one drive? Does nobody use TCQ? Nobody
with old hardware (though, your patch hasn't touched the core PIIX
parts...)?
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak!
ret = do_actions((curr | FREE_SPEECH) & ~(IRAQ_WAR_2 | DRM | TCPA));
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-06-25 18:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-23 19:45 Testing IDE-TCQ and Taskfile - doesn't work nicely:) Jan-Benedict Glaw
2003-06-23 21:18 ` Bartlomiej Zolnierkiewicz
2003-06-23 22:19 ` Jan-Benedict Glaw
2003-06-23 23:50 ` Jan-Benedict Glaw
2003-06-24 0:53 ` Bartlomiej Zolnierkiewicz
2003-06-24 6:31 ` Jan-Benedict Glaw
2003-06-24 13:44 ` Bartlomiej Zolnierkiewicz
2003-06-24 22:40 ` Jan-Benedict Glaw
2003-06-24 23:08 ` Bartlomiej Zolnierkiewicz
2003-06-25 18:22 ` Jan-Benedict Glaw [this message]
2003-06-25 18:44 ` SOLVED - " Bartlomiej Zolnierkiewicz
2003-06-25 19:05 ` Jan-Benedict Glaw
2003-06-25 19:30 ` Bartlomiej Zolnierkiewicz
2003-06-26 3:21 ` Zwane Mwaikambo
2003-06-26 5:58 ` Jan-Benedict Glaw
2003-06-24 8:06 ` Jens Axboe
2003-06-24 14:28 ` Jeff Garzik
2003-06-24 14:47 ` Jens Axboe
2003-06-24 15:39 ` Jeff Garzik
2003-06-29 2:17 ` Andre Hedrick
2003-06-29 8:14 ` Jan-Benedict Glaw
2003-06-29 9:30 ` Andre Hedrick
2003-06-29 10:45 ` Jan-Benedict Glaw
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=20030625182210.GI29233@lug-owl.de \
--to=jbglaw@lug-owl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).