public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Con Kolivas <kernel@kolivas.org>
Cc: Dave Jones <davej@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: IDE CD problems in 2.6.13rc6
Date: Sun, 14 Aug 2005 14:53:02 +0100	[thread overview]
Message-ID: <1124027582.14138.53.camel@localhost.localdomain> (raw)
In-Reply-To: <200508141030.00382.kernel@kolivas.org>

On Sul, 2005-08-14 at 10:30 +1000, Con Kolivas wrote:
> > presumably related, on 2.6.13-rc6. Putting in a cd and trying to read it
> > will cause huge delays and then error out with:
> >
> > ide-cd: cmd 0x28 timed out

(Thats READ_10)

> > hdc: DMA timeout retry
> > hdc: timeout waiting for DMA
> > hdc: status timeout: status=0xd0 { Busy }
> > ide: failed opcode was: unknown
> > hdc: drive not ready for command
> > hdc: ATAPI reset complete

So we asked the drive to do a read and it stayed busy - possibly from
some previous command. In a lot of cases you see the command *after* the
one that broke it. The reset then recovered the drive.


> Even though it apparently works fine I do get these instead though:
> hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> hdc: drive_cmd: error=0x04 { AbortedCommand }
> ide: failed opcode was: 0xec

Thats somewhere between bizarre and fascinating.


  reply	other threads:[~2005-08-14 14:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-13 23:29 IDE CD problems in 2.6.13rc6 Dave Jones
2005-08-14  0:26 ` Con Kolivas
2005-08-14  0:30   ` Con Kolivas
2005-08-14 13:53     ` Alan Cox [this message]
2005-08-14 11:35 ` Bartlomiej Zolnierkiewicz
2005-08-14 13:46   ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2005-08-14 17:43 Voluspa
2005-08-14 19:30 Voluspa
2005-08-14 19:55 Nick Warne
2005-08-14 20:10 Nick Warne
2005-08-14 22:51 Voluspa
2005-08-15  0:37 ` Alan Cox
2005-08-15  0:53   ` Voluspa
2005-08-15 18:30 Nick Warne

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=1124027582.14138.53.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=davej@redhat.com \
    --cc=kernel@kolivas.org \
    --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