From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Lord Subject: Re: 2.6.20 libata cdrom Date: Tue, 01 May 2007 08:54:11 -0400 Message-ID: <46373873.6060704@rtr.ca> References: <20070427175205.GD7809@electro-mechanical.com> <4635C35D.1020807@gmail.com> <20070430202107.GF5942@electro-mechanical.com> <4636C2C7.8090206@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from rtr.ca ([64.26.128.89]:4960 "EHLO mail.rtr.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1031182AbXEAMyO (ORCPT ); Tue, 1 May 2007 08:54:14 -0400 In-Reply-To: <4636C2C7.8090206@gmail.com> Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: Tejun Heo Cc: William Thompson , linux-kernel@vger.kernel.org, IDE/ATA development list , albertcc@tw.ibm.com Tejun Heo wrote: .. >>>> scsi1 : ata_piix >>>> ata2.00: failed to IDENTIFY (I/O error, err_mask=0x1) .. > The err_mask is AC_ERR_DEV indicating that the device raised aborted the > IDENTIFY command. I wonder what's going on. > > Can you change "#undef ATA_DEBUG" in include/linux/libata.h to "#define > ATA_DEBUG" and report the resulting dmesg? There will be a LOT of > messages so you probably want to increase printk buffer size and detach > other devices if possible. It would be best if your root device isn't > driven by libata so that you can just insert the module and store the > resulting dmesg. If the command really was "IDENTIFY", then of course it failed. This is an ATAPI device, and it wants "PACKET_IDENTIFY". Maybe libata somehow thinks it's ATA rather than ATAPI?