Re: [PATCH] blacklist NCQ on Seagate Barracuda ST380817AS
- From: Paolo Ornati <ornati@xxxxxxxxxxxxx>
- Date: Sun, 30 Sep 2007 17:52:07 +0200
On Sun, 30 Sep 2007 11:43:38 -0400
Jeff Garzik <jeff@xxxxxxxxxx> wrote:
it isn't supported here:
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Did you actually try my suggestion?
Yes ("libata.fua=1" is ok I think, or it should just be "libata.fua"?):
...
[ 0.000000] Kernel command line: root=/dev/sda6 ro vga=0x305 libata.fua=1
...
[ 285.004166] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x2 frozen
...
That message is normal, because libata defaults to FUA==off.
--
Paolo Ornati
Linux 2.6.23-rc8-ga64314e6 on x86_64
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [PATCH] blacklist NCQ on Seagate Barracuda ST380817AS
- From: Jeff Garzik
- Re: [PATCH] blacklist NCQ on Seagate Barracuda ST380817AS
- References:
- [PATCH] blacklist NCQ on Seagate Barracuda ST380817AS
- From: Paolo Ornati
- Re: [PATCH] blacklist NCQ on Seagate Barracuda ST380817AS
- From: Alan Cox
- Re: [PATCH] blacklist NCQ on Seagate Barracuda ST380817AS
- From: Paolo Ornati
- Re: [PATCH] blacklist NCQ on Seagate Barracuda ST380817AS
- From: Jeff Garzik
- Re: [PATCH] blacklist NCQ on Seagate Barracuda ST380817AS
- From: Paolo Ornati
- Re: [PATCH] blacklist NCQ on Seagate Barracuda ST380817AS
- From: Jeff Garzik
- [PATCH] blacklist NCQ on Seagate Barracuda ST380817AS
- Prev by Date: File corruption when using kernels 2.6.18+
- Next by Date: Re: [PATCH] fix console change race exposed by CFS
- Previous by thread: Re: [PATCH] blacklist NCQ on Seagate Barracuda ST380817AS
- Next by thread: Re: [PATCH] blacklist NCQ on Seagate Barracuda ST380817AS
- Index(es):
Relevant Pages
|
|
