From: Jeff Garzik <jeff@garzik.org>
To: "Berck E. Nash" <flyboy@gmail.com>
Cc: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: 2.6.23-rc7-mm1 AHCI ATA errors -- won't boot
Date: Tue, 25 Sep 2007 21:21:02 -0400 [thread overview]
Message-ID: <46F9B3FE.1060905@garzik.org> (raw)
In-Reply-To: <46F9617F.1010508@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1026 bytes --]
Berck E. Nash wrote:
> Jeff Garzik wrote:
>> Once the blame has been squared fixed upon me :) you can use git-bisect
>> to locate the precise change that broke your setup.
>
> Okay, here's the problem:
>
> 268fe6f9f15551be9abedd44a237392675d529d5 is first bad commit
> commit 268fe6f9f15551be9abedd44a237392675d529d5
> Author: Jeff Garzik <jeff@garzik.org>
> Date: Fri Sep 21 07:09:36 2007 -0400
>
> [libata] SCSI: simple TEST UNIT READY simulation
>
> It's trivial to ping the device, and that's a much more sane behavior
> than no-op.
>
> Signed-off-by: Jeff Garzik <jeff@garzik.org>
>
> :040000 040000 44d34cdad073bd623545b8239aca9a113652c6d0
> df6d21f7ce56a4e796f8f856c1f647b0395ab4df M drivers
Does the attached patch change behavior at all? You should be able to
apply it on top of libata-dev.git#upstream or -mm.
If there are still problems, an updated dmesg (w/ the attached patch)
and output from enabling ATA_DEBUG (include/linux/libata.h) would be
very helpful.
Thanks!
Jeff
[-- Attachment #2: patch --]
[-- Type: text/plain, Size: 712 bytes --]
diff --git a/drivers/ata/libata-scsi.c b/drivers/ata/libata-scsi.c
index 3882c72..c9838f1 100644
--- a/drivers/ata/libata-scsi.c
+++ b/drivers/ata/libata-scsi.c
@@ -2800,7 +2800,9 @@ static inline ata_xlat_func_t ata_get_xlat_func(struct ata_device *dev, u8 cmd)
return ata_scsi_start_stop_xlat;
case TEST_UNIT_READY:
- return ata_scsi_tur_xlat;
+ if (ata_id_has_pm(dev->id))
+ return ata_scsi_tur_xlat;
+ return NULL;
}
return NULL;
@@ -3021,6 +3023,7 @@ void ata_scsi_simulate(struct ata_device *dev, struct scsi_cmnd *cmd,
case REZERO_UNIT:
case SEEK_6:
case SEEK_10:
+ case TEST_UNIT_READY: /* only for !PM devices */
ata_scsi_rbuf_fill(&args, ata_scsiop_noop);
break;
next prev parent reply other threads:[~2007-09-26 1:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-24 18:02 2.6.23-rc7-mm1 AHCI ATA errors -- won't boot Berck E. Nash
2007-09-25 1:37 ` Jeff Garzik
2007-09-25 18:14 ` Berck E. Nash
2007-09-25 18:21 ` Jens Axboe
2007-09-25 18:28 ` Berck E. Nash
2007-09-25 18:32 ` Jens Axboe
2007-09-25 19:29 ` Berck E. Nash
2007-09-25 20:40 ` Jeff Garzik
2007-09-25 22:07 ` Berck E. Nash
2007-09-25 22:46 ` Berck E. Nash
2007-09-26 1:21 ` Jeff Garzik [this message]
2007-09-26 2:25 ` Berck E. Nash
2007-09-26 2:33 ` Jeff Garzik
2007-09-26 4:40 ` Jeff Garzik
2007-09-26 10:03 ` Bernd Schmidt
2007-09-26 14:22 ` Berck E. Nash
2007-09-27 1:05 ` Tejun Heo
2007-09-26 14:19 ` Berck E. Nash
2007-10-03 21:18 ` Jeff Garzik
[not found] <fa.7B5oGGPZtkIAG9trDHdybt+z9Qg@ifi.uio.no>
[not found] ` <fa.lh2GEsFivC+TeMBqgRXU+5p7ySM@ifi.uio.no>
[not found] ` <fa.tqIC/0YXN2BDEJQ7WBFuJ0EEUrI@ifi.uio.no>
[not found] ` <fa.Q/HeymU0u7VpG+dN5Lc1DraTos0@ifi.uio.no>
2007-09-25 22:39 ` Robert Hancock
2007-09-26 1:10 ` Jeff Garzik
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=46F9B3FE.1060905@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=flyboy@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).