From: Sven Riedel <sr@gimp.org>
To: Greg Freemyer <greg.freemyer@gmail.com>
Cc: sr@gimp.org, Mark Lord <liml@rtr.ca>, linux-ide@vger.kernel.org
Subject: Re: Errors and resets using sata_promise and libata 1.20
Date: Sun, 16 Jul 2006 09:13:38 +0200 [thread overview]
Message-ID: <20060716071338.GA12932@localnet> (raw)
In-Reply-To: <87f94c370607150631g6f91d6fav511cdd8411b39af5@mail.gmail.com>
On Sat, Jul 15, 2006 at 09:31:01AM -0400, Greg Freemyer wrote:
> On 7/15/06, Sven Riedel <sr@gimp.org> wrote:
> >Ok. Well, since I can duplicate the exact same error here consistently,
> >I'll
> >grab 2.6.18rc1 and report back if I can reproduce the error there or not.
> >
> If you don't want to try the whole 2.6.18.rc1 kernel, the new EH is
> available as a big patch for 2.6.17
>
Well, I got the 2.6.18rc1 kernel and found that I could copy three times the
amount of data onto the array without triggering the error message. So it
looks like that bug got squashed.
OTOH, reading more than a few megabytes from an LVM logical volume crashed the
computer so hard, it didn't even have time to throw out a kernel panic (I
don't have a serial console, so I don't know about that. And I realize LVM
stuff is a different mailinglist, just a heads up for people who want to grab
the rc1 tree and run with it - try the patch instead).
Regs,
Sven
--
Sven Riedel sr@gimp.org
prev parent reply other threads:[~2006-07-16 17:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-12 17:29 Errors and resets using sata_promise and libata 1.20 Erik Frederiksen
2006-07-12 18:04 ` Justin Piszcz
2006-07-14 17:31 ` Mark Lord
2006-07-15 6:50 ` Sven Riedel
2006-07-15 13:08 ` Mark Lord
2006-07-15 13:20 ` Sven Riedel
2006-07-15 13:31 ` Greg Freemyer
2006-07-16 7:13 ` Sven Riedel [this message]
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=20060716071338.GA12932@localnet \
--to=sr@gimp.org \
--cc=greg.freemyer@gmail.com \
--cc=liml@rtr.ca \
--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 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.