From: Robert Hancock <hancockrwd@gmail.com>
To: MadLoisae@gmx.net
Cc: jgarzik@pobox.com, linux-ide@vger.kernel.org
Subject: Re: Fwd: Re: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen - "dead" harddisc until reboot
Date: Thu, 10 Jun 2010 18:58:03 -0600 [thread overview]
Message-ID: <4C118A1B.3040206@gmail.com> (raw)
In-Reply-To: <4C114285.8050201@gmx.net>
On 06/10/2010 01:52 PM, MadLoisae@gmx.net wrote:
> Hi there,
>
> actually I am using kernel 2.6.34, up to now I was in every (stable)
> release since 2.6.30 affected by this issue.
> Today I have reactivated legacy, regrettably deprecated parallel ATA
> support and have disabled libata. Its a shame, libata is much faster
> (about 20% faster I/O measureable) and more forward-looking, but it is
> not a real alternative if it crashes continuous but not reproduceable on
> via-chipsets (google for this, the web is filled of this issue!). I
> know, via chipsets are not very good, but shouldn't we try to make it
> better (or at least best as possible) with newer drivers instead of worse?
> I hope legacy ATA support won't be removed soon from the kernel sources ...
>
> I like trying out a lot, but if the response is so thin it does not make
> fun just looking at the same issue with the same messages again and
> again not able to do anything beside looking at it and resetting the box
> afterwards ...
Have you tried limiting the speed to UDMA2? If that helps then it could
be that the motherboard circuitry, etc. isn't suitable for faster speeds.
Random timeouts are unfortunately quite hard to debug since there's so
many problems that can cause them but the symptoms are the same: could
be that there was an error on the bus that caused something to stall, an
interrupt got lost somehow, etc. Or maybe the timing of device access is
somehow different and thus more likely to trigger whatever the cause is.
There also seem to be a fair number of bugs in these IDE chipsets that
the driver has to work around, could be there is one missing in the
libata version..
next prev parent reply other threads:[~2010-06-11 0:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 19:52 Fwd: Re: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen - "dead" harddisc until reboot MadLoisae
2010-06-11 0:58 ` Robert Hancock [this message]
2010-06-11 18:04 ` MadLoisae
2010-06-12 1:38 ` Robert Hancock
2010-06-14 16:06 ` alois.klingler
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=4C118A1B.3040206@gmail.com \
--to=hancockrwd@gmail.com \
--cc=MadLoisae@gmx.net \
--cc=jgarzik@pobox.com \
--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).