linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Robert Hancock <hancockr@shaw.ca>
Cc: linux-ide@vger.kernel.org
Subject: Re: 2.6.28: Timeout problem with AHCI SATA DVD drive
Date: Mon, 29 Dec 2008 17:56:29 +0900	[thread overview]
Message-ID: <495890BD.9070504@kernel.org> (raw)
In-Reply-To: <4957F97B.2050002@shaw.ca>

Robert Hancock wrote:
> Peter Klotz wrote:
>> Robert Hancock wrote:
>>> OK, so it's a "test unit ready" command that got sent to the drive
>>> and it timed out, then the resets after that all failed. That's
>>> essentially the simplest command there is, so it seems likely that
>>> the drive went off into the weeds and stopped talking to us. Whether
>>> or not we can do anything to prevent it, I'm not sure.
>>>
>>> You're sure the drive always detects that same disc properly in Windows?
>>
>> You are right. I finally was able to reproduce this behavior in
>> Windows.  The event log filled up with errors while the disc kept
>> spinning.
>>
>> So this may be a drive firmware issue?
> 
> Almost certainly - you could see if there's a firmware update available..

If there's difference in frequency of it happening, it could be due to
the difference in which commands are used when polling for media
presence.  Windows only uses GET_EVENT_STATUS_NOTIFICATION while we
use a few more commands in combination including TUR.

If the drive actually is going nuts on TUR, disabling media polling
using hal-disable-polling might help.  If the drive just wanna check
out spontaneously, then, well...

-- 
tejun

      reply	other threads:[~2008-12-29  8:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-27  9:10 2.6.28: Timeout problem with AHCI SATA DVD drive Peter Klotz
2008-12-27 19:11 ` Robert Hancock
2008-12-28  7:00   ` Peter Klotz
2008-12-28 22:11     ` Robert Hancock
2008-12-29  8:56       ` Tejun Heo [this message]

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=495890BD.9070504@kernel.org \
    --to=tj@kernel.org \
    --cc=hancockr@shaw.ca \
    --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).