linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: walt <w41ter@gmail.com>
To: linux-ide@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Commit 9f10d9ee breaks CD mounting/burning
Date: Wed, 05 Mar 2008 17:16:51 -0800	[thread overview]
Message-ID: <fqngjf$cjf$1@ger.gmane.org> (raw)

Hi Bartolmiej,

For me, this commit causes the problem it's intended to fix:

commit 9f10d9ee0ac6d79d7bc8b9a158bf4a29322d84d3
Author: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Date:   Tue Feb 26 21:50:35 2008 +0100

     ide-cd: fix 'ireason' handling for REQ_TYPE_ATA_PC requests

     This fixes some hangs caused by not finishing the transfer before ending
     the request and also makes use of 'ireason == 1' quirk for spurious IRQs.

When I mount a CD there is a long delay, and I see this error message:

hdc: ide_cd_check_ireason: wrong transfer direction!
cdrom: failed setting lba address space
hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }
ide: failed opcode was: unknown
hdc: drive not ready for command
<repeated many times>

When I revert this commit everything works properly again, including
CD burning.

Here is the drive info:

hdc: TSSTcorpCD/DVDW SH-S182M, ATAPI CD/DVD-ROM drive
hdc: host max PIO5 wanted PIO255(auto-tune) selected PIO4
hdc: UDMA/33 mode selected
hdc: ATAPI 48X DVD-ROM DVD-R-RAM CD-R/RW drive, 2048kB Cache
Uniform CD-ROM driver Revision: 3.20
hdc: UDMA/33 mode selected

I'm happy to try patches or supply more info, just let me know
what you need.

Thanks.


             reply	other threads:[~2008-03-06  1:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-06  1:16 walt [this message]
2008-03-06 21:35 ` Commit 9f10d9ee breaks CD mounting/burning Bartlomiej Zolnierkiewicz
2008-03-07  0:21   ` walt
2008-03-07  5:48   ` Borislav Petkov
2008-03-07 20:39     ` Bartlomiej Zolnierkiewicz
2008-03-07 21:49       ` Borislav Petkov
2008-03-07 22:45         ` Bartlomiej Zolnierkiewicz
2008-03-07 23:35           ` Rafael J. Wysocki

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='fqngjf$cjf$1@ger.gmane.org' \
    --to=w41ter@gmail.com \
    --cc=linux-ide@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).