lkml.org 
[lkml]   [2007]   [Jun]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Bad behaviour after hdparm -M 128
Tino Keitel wrote:
> Hi,
>
> I tried to enable acoustic management on my SATA drive, because
> hdparm -I reported a recommended value of 128, and a current value
> of 0 (off).
>
> I did this:
>
> $ sudo hdparm -M 128 /dev/sda
> /dev/sda:
> setting acoustic management to 128
> HDIO_DRIVE_CMD:ACOUSTIC failed: Input/output error
> acoustic = not supported
>
> It apperently failed, no big deal.
>
> However, I had these messages in the kernel log, and they don't look
> really harmless to me:
>
> ata3.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> ata3.01: cmd ef/42:80:00:00:00/00:00:00:00:00/50 tag 0 cdb 0x0 data 0
> res 51/04:80:00:00:00/00:00:00:00:00/50 Emask 0x1 (device error)
> ata3.01: configured for UDMA/133
> ata3: EH complete
> SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
> sda: Write Protect is off
> sda: Mode Sense: 00 3a 00 00
> SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
>
> Is this expected behaviour?
>
> I used kernel 2.6.21 with the libata PIIX SATA driver and a
> Seagate ST98823AS drive.

Yes, that's expected if the drive rejects the command.

--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2007-06-06 16:33    [from the cache]
©2003-2011 Jasper Spaans. Advertise on this site