From: Sven Riedel <sr@gimp.org>
To: Mark Lord <liml@rtr.ca>
Cc: sr@gimp.org, linux-ide@vger.kernel.org
Subject: Re: Errors and resets using sata_promise and libata 1.20
Date: Sat, 15 Jul 2006 15:20:13 +0200 [thread overview]
Message-ID: <20060715132012.GA18761@localnet> (raw)
In-Reply-To: <44B8E8D6.8020903@rtr.ca>
> >Is there a patch somewhere that didn't make it into the kernel yet, that we
> >can try?
>
> No. And it's quite unfortunate, as this bug prevents proper error handling
> by the SCSI layer, since libata doesn't accurately report what problem it
> saw.
>
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.
Regs,
Sven
--
Sven Riedel sr@gimp.org
next prev parent reply other threads:[~2006-07-15 13:20 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 [this message]
2006-07-15 13:31 ` Greg Freemyer
2006-07-16 7:13 ` Sven Riedel
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=20060715132012.GA18761@localnet \
--to=sr@gimp.org \
--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 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).