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 <[EMAIL PROTECTED]>
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 <[EMAIL PROTECTED]>
:040000 040000 44d34cdad073bd623545b8239aca9a113652c6d0
df6d21f7ce56a4e796f8f856c1f647b0395ab4df M drivers
Thanks for debugging!
Can you tell me something about this device?
[ 49.045635] ata2.00: ATA-6: Config Disk, RGL10364, max UDMA/133
[ 49.051677] ata2.00: 640 sectors, multi 1: LBA
[ 49.056321] ata2.00: configured for UDMA/133
It seems like it does not support the 'check power mode' command.
Can you post a text file attachment, containing the output of 'hdparm
--Istdout' ?
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
