linux-kernel - RE: "exception Emask: 0x42" errors with 2.6.22.x and SATA drives

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>] [day] [month] [year] [list]

Date:	Mon, 27 Aug 2007 13:14:15 +0100
From:	"Dermot Bradley" <dermot.bradley@...-mobile.com>
To:	"Alistair John Strachan" <alistair@...zero.co.uk>
Cc:	"Alan Cox" <alan@...rguk.ukuu.org.uk>,
	<linux-kernel@...r.kernel.org>, "Jeff Garzik" <jeff@...zik.org>
Subject: RE: "exception Emask: 0x42" errors with 2.6.22.x and SATA drives

> I've added Jeff to CC in case he's interested about the workaround for
> this drive (I assume you're using the AHCI driver with your ATI
> controller).

Yupe, using AHCI.

I've just rebooted after adding that blacklist line to the kernel and
recompiling but it doesn't seem to have taken effect:

  ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
  ata1.00: ATA-7: WDC WD800BEVS-07RST0, 04.01G04, max UDMA/133
  ata1.00: 156301488 sectors, multi 1: LBA48 NCQ (depth 31/32)

If NCQ is disabled/blacklisted shouldn't the depth say 0/32 ?

I used the string "WDC WD800BEVS-07" in the patch, maybe I should use
"WDC WD800BEVS-07RST0" instead?

cat /sys/bus/scsi/devices/0\:0\:0\:0/model shows "WDC WD800BEVS-07"

Stirk, Lamont & Associates Ltd.
Registered Address: Thomas Andrews House, Queens Road, Belfast,  BT3 9DU
Registered in Northern Ireland, Number: NI 47983. VAT Number: 832 2778 22

-
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/