From: Jeff Garzik <jeff@garzik.org>
To: Paolo Ornati <ornati@fastwebnet.it>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, Tejun Heo <htejun@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-ide@vger.kernel.org
Subject: Re: [PATCH] blacklist NCQ on Seagate Barracuda ST380817AS
Date: Sun, 30 Sep 2007 11:59:45 -0400 [thread overview]
Message-ID: <46FFC7F1.6080409@garzik.org> (raw)
In-Reply-To: <20070930175207.5bfa89a8@localhost>
Paolo Ornati wrote:
> On Sun, 30 Sep 2007 11:43:38 -0400
> Jeff Garzik <jeff@garzik.org> 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
> ...
Is libata built into the kernel, or a module?
If it is a module, using the kernel command line won't work.
Jeff
next prev parent reply other threads:[~2007-09-30 15:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-30 14:05 [PATCH] blacklist NCQ on Seagate Barracuda ST380817AS Paolo Ornati
2007-09-30 14:17 ` Tejun Heo
2007-09-30 14:42 ` Paolo Ornati
2007-09-30 14:29 ` Alan Cox
2007-09-30 14:46 ` Paolo Ornati
2007-09-30 15:05 ` Jeff Garzik
2007-09-30 15:28 ` Paolo Ornati
2007-09-30 15:43 ` Jeff Garzik
2007-09-30 15:52 ` Paolo Ornati
2007-09-30 15:59 ` Jeff Garzik [this message]
2007-09-30 16:03 ` Paolo Ornati
2007-09-30 17:26 ` Mark Lord
2007-09-30 17:29 ` Tejun Heo
2007-09-30 17:43 ` Mark Lord
2007-09-30 17:51 ` Tejun Heo
2007-09-30 18:54 ` Mark Lord
2007-09-30 19:01 ` Mark Lord
2007-10-02 9:19 ` Tejun Heo
2007-10-02 15:40 ` Paolo Ornati
[not found] <fa.ernzRd7lGBTxTXHl/DtyMhz/rPk@ifi.uio.no>
2007-09-30 23:45 ` Robert Hancock
2007-10-01 7:21 ` Paolo Ornati
2007-10-01 8:09 ` Jiri Slaby
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46FFC7F1.6080409@garzik.org \
--to=jeff@garzik.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ornati@fastwebnet.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.