linux-kernel - Re: libATA error message doc

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4703D75B.6070608@garzik.org>
Date:	Wed, 03 Oct 2007 13:54:35 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Mike Robak <mrobak@...il.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: libATA error message doc

Mike Robak wrote:
> Does a doc exist that provides a detailed description of the different
> errors that could be produced by libata and its associated drivers?
> The libATA developer's guide provides a very good general description
> of the types of messages, but I'm looking for more detail.
> 
> For example I got this error message last week:
> 
> Sep 27 17:29:26 server kernel: ata2.00: exception Emask 0x0 SAct 0x0
> SErr 0x0 action 0x1
> Sep 27 17:29:26 server kernel: ata2.00: (irq_stat 0x40000001)
> Sep 27 17:29:26 server kernel: ata2.00: tag 0 cmd 0xb0 Emask 0x1 stat
> 0x51 err 0x4 (device error)
> 
> I'd like to know what the following items means?
> 
> (irq_stat 0x40000001)
> tag 0
> cmd 0xb0
> emask 0x1
> stat 0x51
> err 0x4

It's pretty much all defined in the ATA or controller specifications...

Well, except for emask, which is a libata-only invention.

	Jeff



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