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: Marcelo Tosatti <marcelo@conectiva.com.br>, linux-kernel@vger.kernel.org
Subject: Re: Promise IDE patches
Date: Sun, 19 Oct 2003 15:17:02 +0200	[thread overview]
Message-ID: <20031019131702.GA13067@gondor.com> (raw)
In-Reply-To: <200308270054.27375.bzolnier@elka.pw.edu.pl>

[-- Attachment #1: Type: text/plain, Size: 1893 bytes --]

Hi Bartolomeij, hi Marcelo!

Two months ago, I had problems with a >137GB drive on a promise
controller. These where fixed by a few patches, and the computer runs
fine since then with a patched 2.4.22 kernel.

Unfortunately, as far as I can see, none of the patches got applied to
2.4.23-pre7. I know that Alan had a few objections against the patches,
and they should be addressed, but as things are now, plain 2.4.23-pre7
would lead to severe data corruption if I used it on my computer.

For reference, here is the complete mail where Bartolomeij asked Marcelo
to apply the patches:

On Wed, Aug 27, 2003 at 12:54:27AM +0200, Bartlomiej Zolnierkiewicz wrote:
> Marcelo can you apply these patches?
> 
> On Wednesday 27 of August 2003 00:31, Jan Niehusmann wrote:
> > Hi!
> >
> > Two weeks ago, I tried two patches against 2.4.21 regarding LBA48
> > support. One limits the size of a drive to 137GB if LBA48 is not
> > available. Without this patch, severe data corruption is possible.
> >
> > http://gondor.com/linux/patch-limit48-2.4.21
> >
> > The other one is making LBA48 support work with pdc 20265 controllers.
> >
> > http://gondor.com/linux/patch-pdc-lba48-2.4.22
> >
> > I think they should be candidates for inclusion in 2.4.23, as well as
> > a fix for hdparm -I (and other commands going directly to the drive) on
> > (some?) promise controllers:
> >
> > http://marc.theaimsgroup.com/?l=linux-kernel&m=104250818527780&w=2
> >
> > Jan

Alan mentioned problems with patches 1 and 3, but AFAIK nobody had
problems with patch 2. Consult the archives for details, it's all been
on linux-kernel.

Even though I could easily fix 2.4.23 for myself, I'd really like to
have the official kernel work without local patches. And I guess an
increasing number of people is using drives >137GB, so it can easily hit
other people as well.

Jan


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2003-10-19 13:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-26 22:31 Promise IDE patches Jan Niehusmann
2003-08-26 22:54 ` Bartlomiej Zolnierkiewicz
2003-08-27 14:58   ` Alan Cox
2003-08-27 15:21     ` Bartlomiej Zolnierkiewicz
2003-08-27 14:59   ` Alan Cox
2003-08-27 15:12     ` Jan Niehusmann
2003-08-27 15:20       ` Jan Niehusmann
2003-08-27 15:45       ` Alan Cox
2003-08-27 15:20     ` Bartlomiej Zolnierkiewicz
2003-10-19 13:17   ` Jan Niehusmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-08-27  1:26 Erik Andersen

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=20031019131702.GA13067@gondor.com \
    --to=jan@gondor.com \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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