public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Schaefer <peter.schaefer@gmx.de>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [libata - SII3112] 'Virtual' bad blocks?
Date: Fri, 27 Aug 2004 22:35:34 +0200	[thread overview]
Message-ID: <412F9B16.7020706@gmx.de> (raw)
In-Reply-To: <412F8F93.2010008@pobox.com>

On 27.08.2004 21:46, Jeff Garzik wrote:

> Alan Cox submitted code that makes the errors more specific, rather than 
> treating them all as disk errors.

Can i diff against libata-scsi.c in 2.9.1-rc1 to get this?

> You have either a flaky controller, flaky cable, or flaky disk, one of 
> the three.

Hrmpf. Well, i swapped cables as a first measure. I'll see if the error
travels with it (if not - well, there's still 4 years of guarantee on the
disk :).

Thanks alot for your support and your hard work on libata!

Best regards,

    Peter

      reply	other threads:[~2004-08-27 20:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-27 19:20 [libata - SII3112] 'Virtual' bad blocks? Peter Schaefer
2004-08-27 19:46 ` Jeff Garzik
2004-08-27 20:35   ` Peter Schaefer [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=412F9B16.7020706@gmx.de \
    --to=peter.schaefer@gmx.de \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@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