linux-kernel - Re: SiI 3512 Serial ATA Controller

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]

Date:	Tue, 22 Jan 2008 16:05:43 -0500
From:	Jeff Garzik <jeff@...zik.org>
To:	Dan Nica <timi@...stal.rdstm.ro>
CC:	linux-kernel@...r.kernel.org,
	Linux IDE mailing list <linux-ide@...r.kernel.org>
Subject: Re: SiI 3512 Serial ATA Controller - kernel 2.6.23

Dan Nica wrote:
> hello
> 
> I have a problem with a serial ata controller
> that uses a SiI 3512 chip.

A complete dmesg, complete lspci would be helpful.


> when I'm trying to add a device thats on the 3512 controller 
> to the array that I have, it give me lots of errors in dmesg
> like this:
> 
> ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x2400000 action 0x0
> ata3.00: BMDMA2 stat 0x8652001
> ata3.00: cmd 35/00:80:3f:5c:03/00:02:00:00:00/e0 tag 0 cdb 0x0 data 327680 
> out
>          res 51/04:80:3f:5e:03/00:00:00:00:00/e0 Emask 0x1 (device error)

That's the device reporting an error, when the system issued a WRITE 
command ("cmd 35/....."), and the SiI controller is happily reporting 
that error to you.

I would worry about the device, if it is reporting errors on WRITE.

	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/