public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Niehusmann <jan@gondor.com>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: Andries Brouwer <aebr@win.tue.nl>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: IDE bug - was: Re: uncorrectable ext2 errors
Date: Thu, 14 Aug 2003 00:36:41 +0200	[thread overview]
Message-ID: <20030813223641.GA1921@gondor.com> (raw)
In-Reply-To: <200308130221.26305.bzolnier@elka.pw.edu.pl>

On Wed, Aug 13, 2003 at 02:21:26AM +0200, Bartlomiej Zolnierkiewicz wrote:
> Jan, did removing offending lines from pdc202xx_old.c help?

Ok, now I tried a kernel without the 
"hwif->addressing = (hwif->channel) ? 0 : 1"  line in pdc202xx_old.c,
and yes, now the 160GB drive works without aliasing parts above 137GB
back to the beginning of the drive.

Some simple tests (reading and writing a few 100MB of data) didn't show
any nasty side effects. If you want me to do additional tests, please
tell me. At the moment the drive doesn't contain any data, so I can even
try dangerous things.

Jan


  parent reply	other threads:[~2003-08-13 22:40 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-06 15:03 uncorrectable ext2 errors Jan Niehusmann
2003-08-06 17:06 ` Andreas Dilger
2003-08-06 18:38   ` Jan Niehusmann
2003-08-06 18:52     ` Mike Fedyk
2003-08-06 19:50 ` Jan Niehusmann
2003-08-07 11:06 ` Jan Niehusmann
2003-08-07 12:27   ` LBA48 on Promise 20265 Jan Niehusmann
2003-08-07 21:12   ` uncorrectable ext2 errors Andries Brouwer
2003-08-10 20:55     ` Jan Niehusmann
2003-08-10 21:19       ` Andries Brouwer
2003-08-10 21:34         ` Jan Niehusmann
2003-08-10 21:58           ` Andries Brouwer
2003-08-10 22:10             ` Jan Niehusmann
2003-08-10 22:33               ` IDE bug - was: " Andries Brouwer
2003-08-12 15:36                 ` Alan Cox
2003-08-12 16:32                   ` Bartlomiej Zolnierkiewicz
2003-08-12 22:50                   ` Andries Brouwer
2003-08-13  0:21                     ` Bartlomiej Zolnierkiewicz
2003-08-13  8:03                       ` Jan Niehusmann
2003-08-13  9:25                         ` Jan Niehusmann
2003-08-13 11:16                         ` Alan Cox
2003-08-13 11:20                           ` Jan Niehusmann
2003-08-13 12:12                             ` Jan Niehusmann
2003-08-13 16:31                           ` Jan Niehusmann
2003-08-13 18:38                             ` Alan Cox
2003-08-13 12:21                         ` Bartlomiej Zolnierkiewicz
2003-08-13 13:27                       ` Andries Brouwer
2003-08-13 22:05                         ` Jan Niehusmann
2003-08-13 22:32                           ` Bartlomiej Zolnierkiewicz
2003-08-13 22:36                       ` Jan Niehusmann [this message]
2003-08-13 23:14                         ` Bartlomiej Zolnierkiewicz
2003-08-14  6:37                           ` Jan Niehusmann
2003-08-10 23:01           ` Bartlomiej Zolnierkiewicz

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=20030813223641.GA1921@gondor.com \
    --to=jan@gondor.com \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --cc=aebr@win.tue.nl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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