From: Tino Keitel <tino.keitel@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: Bad behaviour after hdparm -M 128
Date: Wed, 6 Jun 2007 08:47:44 +0200 [thread overview]
Message-ID: <20070606064744.GA14552@dose.home.local> (raw)
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.
Regards,
Tino
next reply other threads:[~2007-06-06 6:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 6:47 Tino Keitel [this message]
[not found] <fa.DWgGSeKzniALToNSyX9W5NibA1w@ifi.uio.no>
2007-06-06 14:29 ` Bad behaviour after hdparm -M 128 Robert Hancock
2007-06-06 15:44 ` Henrique de Moraes Holschuh
2007-06-06 16:24 ` Björn Steinbrink
2007-06-06 16:48 ` Henrique de Moraes Holschuh
2007-06-06 17:51 ` Björn Steinbrink
2007-06-06 21:03 ` Henrique de Moraes Holschuh
2007-06-06 21:36 ` Björn Steinbrink
2007-06-06 21:52 ` Henrique de Moraes Holschuh
2007-06-07 15:45 ` Mark Lord
2007-06-08 1:50 ` Henrique de Moraes Holschuh
2007-06-11 9:22 ` Tino Keitel
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=20070606064744.GA14552@dose.home.local \
--to=tino.keitel@gmx.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