mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
To: Justin Hibbits <jrh29@po.cwru.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: regression between 2.4.18 and 2.4.21/22
Date: Mon, 6 Oct 2003 01:22:30 +0200	[thread overview]
Message-ID: <200310060122.30129.bzolnier@elka.pw.edu.pl> (raw)
In-Reply-To: <7342FA76-F771-11D7-86F4-000A95841F44@po.cwru.edu>


Please narrow down kernel version if you want your problem to be cared.

Try 2.4.19, 2.4.20.  There are also intermediate prepatches at
http://www.kernel.org/pub/linux/kernel/v2.4/testing/old/

dmesg output and .config can also be useful.

--bartlomiej

On Sunday 05 of October 2003 22:21, Justin Hibbits wrote:
> Something very strange is going on with my machine.  With 2.4.18, I was
> getting 38MB/s on my main system disk (IBM Deskstar 60gxp), and 35 for
> the other drives (Western Digital).  The IBM drive is on a Promise IDE
> controller (ASUS A7V266-E motherboard), and the others are on a PROMISE
> 2069 UDMA133 controller.  However, with 2.4.21 and 2.4.22, it will not
> set the using_dma flag for my IBM drive, but sets it for the others,
> which now get sustained transfer rates of 46MB/s or greater.  I'm using
> the same options for all 3 kernels (at least, for the ATA/IDE options).
>   Any help would be appreciated, and I'll see if maybe I could do
> something with it when I get time.


  parent reply	other threads:[~2003-10-05 23:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-05 20:21 Justin Hibbits
2003-10-05 21:58 ` Mike Fedyk
2003-10-05 22:22   ` Justin Hibbits
2003-10-05 23:22 ` Bartlomiej Zolnierkiewicz [this message]
2003-10-05 23:38   ` Justin Hibbits
2003-10-06 19:06     ` Bartlomiej Zolnierkiewicz
2003-10-06 20:21       ` Justin Hibbits
2003-10-06 20:49         ` 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=200310060122.30129.bzolnier@elka.pw.edu.pl \
    --to=b.zolnierkiewicz@elka.pw.edu.pl \
    --cc=jrh29@po.cwru.edu \
    --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

all inboxes | Powered by JetHome®