From: Tejun Heo <htejun@gmail.com>
To: Dominik Schulz <lkml@ds.gauner.org>
Cc: linux-ide@vger.kernel.org
Subject: Re: Possible Bug in sata_via when trying to burn
Date: Thu, 10 May 2007 14:49:10 +0200 [thread overview]
Message-ID: <464314C6.8050802@gmail.com> (raw)
In-Reply-To: <4641DB20.6030606@ds.gauner.org>
Dominik Schulz wrote:
> Hi,
>
> as far as I can see the kernel doesn't complain about anything. Nothing
> in the syslog or anywhere else.
>
> One thing I forgot to mention: It's no permission problem. I get exactly
> the same output as root.
>
> I've put the output of
> wodim -VV blank=all -dev=2,0,0
| Executing 'mode select g1' command on Bus 2 Target 0, Lun 0 timeout 40s
| CDB: 55 10 00 00 00 00 00 00 3C 00
| Sending 60 (0x3C) bytes of data.
| Write Data: 00 00 21 00 00 00 00 00 05 32 41 C4 08 00 00 00 00 00 00 00 00 00 00 96 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
| Errno: 5 (Input/output error), mode select g1 scsi sendcmd: no error
| CDB: 55 10 00 00 00 00 00 00 3C 00
| status: 0x2 (CHECK CONDITION)
| Sense Bytes: 70 00 04 00 00 00 00 0A 00 00 00 00 08 03 00 00
| Sense Key: 0x4 Hardware Error, Segment 0
| Sense Code: 0x08 Qual 0x03 (logical unit communication crc error (ultra-dma/32)) Fru 0x0
| Sense flags: Blk 0 (not valid)
| resid: 60
| cmd finished after 0.001s timeout 40s
It seems commands to transfer data to the device suffers transmission
error. Does the same thing occur even when you're using a SATA
device? The device is already configured at UDMA/33, so it can't be a
cable detection problem. Weird....
Just in case, can you try to reseat or replace the cable? Of the two
IDE connectors, where is the dvd writer connected?
--
tejun
prev parent reply other threads:[~2007-05-10 12:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 9:55 Possible Bug in sata_via when trying to burn Dominik Schulz
2007-05-09 13:50 ` Tejun Heo
2007-05-09 14:30 ` Dominik Schulz
2007-05-10 12:49 ` 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=464314C6.8050802@gmail.com \
--to=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=lkml@ds.gauner.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).