also sprach Tomasz Chmielewski <[email protected]> [2006.11.10.1612 +0100]: > I saw similar when using smartctl / smartd with wrong options (without > -d ata; in short, smartd tried to talk "IDE language" to SATA device...). I am using smartd, and you are right: it triggers those messages after being started: [smartd start] kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen kernel: ata2.00: tag 0 cmd 0xb0 Emask 0x2 stat 0x50 err 0x0 (HSM violation) kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) kernel: ata2: soft resetting port kernel: ata2.00: configured for UDMA/133 kernel: ata2: EH complete [...] kernel: ata3: no sense translation for status: 0x50 kernel: ata3: translated ATA stat/err 0x50/00 to SCSI SK/ASC/ASCQ 0xb/00/00 kernel: ata3: status=0x50 { DriveReady SeekComplete } -- martin; (greetings from the heart of the sun.) \____ echo mailto: !#^."<*>"|tr "<*> mailto:"; net@madduck spamtraps: [email protected] "it is only the modern that ever becomes old-fashioned." -- oscar wilde
Attachment:
signature.asc
Description: Digital signature (GPG/PGP)
- References:
- Re: scary messages: HSM violation during boot of 2.6.18/amd64
- From: Tomasz Chmielewski <[email protected]>
- Re: scary messages: HSM violation during boot of 2.6.18/amd64
- Prev by Date: Re: A proposal; making 2.6.20 a bugfix only version.
- Next by Date: Re: [PATCH 02/02] Elf: Align elf notes properly
- Previous by thread: Re: scary messages: HSM violation during boot of 2.6.18/amd64
- Next by thread: Re: scary messages: HSM violation during boot of 2.6.18/amd64
- Index(es):
 |