linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Johnny Luong <johnny.linux-ide@compfazed.com>, linux-ide@vger.kernel.org
Subject: Re: unable to use cdrom/dvd drive after some usage
Date: Mon, 21 Jan 2008 17:01:42 +0900	[thread overview]
Message-ID: <47945166.4060907@gmail.com> (raw)
In-Reply-To: <20080115113406.10d691e3@lxorguk.ukuu.org.uk>

Alan Cox wrote:
> On Mon, 14 Jan 2008 20:46:08 -0800
> Johnny Luong <johnny.linux-ide@compfazed.com> wrote:
> 
>> Hi,
>>
>> If possible, I would like to know if its worthwhile simply just to get another
>> SATA drive / different controller / cable rather than trying to figure out
>> this PATA drive on SATA/PATA controller...  see attached for bug report and
>> config file.  I'm not on this email list so if you can CC that would be 
>> appreciated.
> 
> I don't think so. Wine seems to have fed the drive a command that upset
> it to the point it needed power cycling. That may also however be a
> drive/controller that don't know how to clear data stuck after a wrong
> transfer length from an application. In that case 2.6.24-rc6 (or 2.6.24
> once out) may actually fix the problem.
> 
> If it doesn't then we need to look at it further and find out what is
> going on to crash the drive.

Another possibility is that the drive requires DEVICE RESET to clear its
FIFO or whatever.  I'm working on DEVICE RESET.  Will post patch soon.
Johnny, please hold on to the hardware for testing.

Thanks.

-- 
tejun

  reply	other threads:[~2008-01-21  8:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-15  4:46 unable to use cdrom/dvd drive after some usage Johnny Luong
2008-01-15 11:34 ` Alan Cox
2008-01-21  8:01   ` Tejun Heo [this message]
2008-01-21  8:38     ` Johnny Luong
2008-01-21 15:28       ` Tejun Heo

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=47945166.4060907@gmail.com \
    --to=htejun@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=johnny.linux-ide@compfazed.com \
    --cc=linux-ide@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).