From: Emmanuel Fleury <emmanuel.fleury@labri.fr>
To: Jens Axboe <axboe@suse.de>
Cc: linux-kernel@vger.kernel.org, GarnierB-02@mail.europcar.com
Subject: Re: [libata] atapi_enabled problem
Date: Thu, 20 Apr 2006 16:45:31 +0200 [thread overview]
Message-ID: <44479E8B.8010003@labri.fr> (raw)
In-Reply-To: <44477D93.50501@labri.fr>
Additional comments:
Emmanuel Fleury wrote:
>
> ata1: translated ATA stat/err 0x51/20 to SCSI SK/ASC/ASCQ 0x3/11/04
> ata1: no sense translation for error 0x20
> ata1: no sense translation for status: 0x51
> ata1: translated ATA stat/err 0x51/20 to SCSI SK/ASC/ASCQ 0x3/11/04
> sr0: CDROM (ioctl) error, command: <6>Test Unit Ready 00 00 00 00 00 00
> sr: Current [descriptor]: sense key: Medium Error
> Additional sense: Unrecovered read error - auto reallocate failed
> ata1: no sense translation for error 0x20
> ata1: no sense translation for status: 0x51
> ata1: translated ATA stat/err 0x51/20 to SCSI SK/ASC/ASCQ 0x3/11/04
> ata1: no sense translation for error 0x20
> ata1: no sense translation for status: 0x51
> ata1: translated ATA stat/err 0x51/20 to SCSI SK/ASC/ASCQ 0x3/11/04
> ata1: no sense translation for error 0x20
> ata1: no sense translation for status: 0x51
> ata1: translated ATA stat/err 0x51/20 to SCSI SK/ASC/ASCQ 0x3/11/04
> ata1: no sense translation for error 0x20
> ata1: no sense translation for status: 0x51
> ata1: translated ATA stat/err 0x51/20 to SCSI SK/ASC/ASCQ 0x3/11/04
> ata1: no sense translation for error 0x20
> ata1: no sense translation for status: 0x51
> ata1: translated ATA stat/err 0x51/20 to SCSI SK/ASC/ASCQ 0x3/11/04
> ata1: no sense translation for error 0x20
> ata1: no sense translation for status: 0x51
> ata1: translated ATA stat/err 0x51/20 to SCSI SK/ASC/ASCQ 0x3/11/04
> ata1: no sense translation for error 0x20
> ata1: no sense translation for status: 0x51
Benoit Garnier did point to me this thread: http://kerneltrap.org/node/5836
The solution proposed can't be applied to me because I have a dual
system where my HD is IDE/ATAPI and my DVD reader is S-ATA.
Indeed, I tried out several possibilities and it appeared that the way
to generate such errors was to set the Intel PIIX/ICH SATA support as
built-in (y). When set as module (m), everything is fine.
Device Drivers --->
SCSI device support --->
SCSI low-level drivers --->
Intel PIIX/ICH SATA support
I might have changed this when hard-coding atapi_enabled=1 in the source.
Does someone see the light now ? (I'm still a bit in the dark)
Regards
--
Emmanuel Fleury | Office: 211
Associate Professor, | Phone: +33 (0)5 40 00 35 24
LaBRI, Domaine Universitaire | Fax: +33 (0)5 40 00 66 69
351, Cours de la Libération | email: emmanuel.fleury@labri.fr
33405 Talence Cedex, France | URL: http://www.labri.fr/~fleury
next prev parent reply other threads:[~2006-04-20 14:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-20 12:24 [libata] atapi_enabled problem Emmanuel Fleury
2006-04-20 14:45 ` Emmanuel Fleury [this message]
2006-04-20 15:07 ` Emmanuel Fleury
2006-04-20 15:28 ` Randy.Dunlap
2006-04-20 15:48 ` Emmanuel Fleury
2006-04-20 16:31 ` Randy.Dunlap
2006-04-21 8:23 ` Emmanuel Fleury
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=44479E8B.8010003@labri.fr \
--to=emmanuel.fleury@labri.fr \
--cc=GarnierB-02@mail.europcar.com \
--cc=axboe@suse.de \
--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