From: Mark Lord <liml@rtr.ca>
To: Jochen Heuer <jogi-kernel@planetzork.ping.de>
Cc: Tejun Heo <htejun@gmail.com>, linux-ide@vger.kernel.org
Subject: Re: Bug or HW? ata1: command timeout, stat 0x50 host_stat 0x4
Date: Tue, 04 Jul 2006 11:31:27 -0400 [thread overview]
Message-ID: <44AA89CF.7000404@rtr.ca> (raw)
In-Reply-To: <20060702000706.GA11103@planetzork.ping.de>
Jochen Heuer wrote:
> On Wed, Jun 28, 2006 at 10:09:12AM +0200, Jochen Heuer wrote:
..
> also not increasing ... Are there any known issues in this area with SMP
> kernels?
Mmm.. there was another thread in lkml about the A8V, where somebody
reported that turning *off* CONFIG_PREEMPT results in much more stable
libata operation for some users.
I have an A8V here, but have not yet put a modern Linux installation onto it.
Cheers
next prev parent reply other threads:[~2006-07-04 15:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-27 18:43 Bug or HW? ata1: command timeout, stat 0x50 host_stat 0x4 Jochen Heuer
2006-06-28 6:33 ` Tejun Heo
2006-06-28 8:09 ` Jochen Heuer
2006-07-02 0:07 ` Jochen Heuer
2006-07-04 15:31 ` Mark Lord [this message]
2006-07-04 22:24 ` Jochen Heuer
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=44AA89CF.7000404@rtr.ca \
--to=liml@rtr.ca \
--cc=htejun@gmail.com \
--cc=jogi-kernel@planetzork.ping.de \
--cc=linux-ide@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).