From: Mark Lord <liml@rtr.ca>
To: Norman Diamond <n0diamond@yahoo.co.jp>
Cc: Chuck Ebbert <cebbert@redhat.com>,
linux-ide@vger.kernel.org, Jens Axboe <jens.axboe@oracle.com>
Subject: Re: Kernel bug crashing in HDIO_DRIVE_TASKFILE
Date: Wed, 25 Feb 2009 11:24:59 -0500 [thread overview]
Message-ID: <49A570DB.8090401@rtr.ca> (raw)
In-Reply-To: <26917692A9574F3A9363ED5253B42D2F@DIAMOND8600>
Norman Diamond wrote:
..
> Does anyone know when this bug was added? 2.6.19 is too old for my needs,
> but the range 2.6.24 to 2.6.26 might be OK if they had taskfiles working.
> Maybe I should look for a Slax version that had a kernel from 2.6.24 or so,
> since I can probably customize it in a single day by now. But if the bug
> was already present in 2.6.24 then it would be a waste of time.
..
Heh.. the question could be more like, does anyone know which few kernels
that HDIO_DRIVE_TASKFILE ever worked completely on? :)
I know I have to patch drivers/ide rather heavily to get a working,
reliable HDIO_DRIVE_TASKFILE on it.
Much better is to move to libata, and use ATA_16 with SG_IO,
for a standard, working way of doing this kind of stuff.
Cheers
next prev parent reply other threads:[~2009-02-25 16:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-24 11:36 Kernel bug crashing in HDIO_DRIVE_TASKFILE Norman Diamond
2009-02-24 22:10 ` Chuck Ebbert
2009-02-25 11:43 ` Norman Diamond
2009-02-25 16:24 ` Mark Lord [this message]
2009-02-25 19:35 ` Bartlomiej Zolnierkiewicz
2009-02-25 21:18 ` Norman Diamond
2009-02-25 22:43 ` Mark Lord
2009-02-26 11:56 ` Norman Diamond
2009-02-28 3:14 ` Robert Hancock
2009-03-01 0:58 ` Norman Diamond
2009-03-01 1:16 ` Alan Cox
2009-03-01 11:06 ` Robert Hancock
2009-03-02 0:24 ` Norman Diamond
2009-03-02 2:38 ` Robert Hancock
2009-03-02 11:43 ` Norman Diamond
2009-03-11 22:33 ` Bartlomiej Zolnierkiewicz
2009-03-11 23:00 ` Norman Diamond
-- strict thread matches above, loose matches on Subject: below --
2009-03-03 11:44 Norman Diamond
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=49A570DB.8090401@rtr.ca \
--to=liml@rtr.ca \
--cc=cebbert@redhat.com \
--cc=jens.axboe@oracle.com \
--cc=linux-ide@vger.kernel.org \
--cc=n0diamond@yahoo.co.jp \
/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).