public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jeff V. Merkey" <jmerkey@timpanogas.org>
To: Martin Dalecki <dalecki@evision-ventures.com>,
	linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: PATCH: killing read_ahead[]
Date: Thu, 26 Oct 2000 18:47:47 -0600	[thread overview]
Message-ID: <39F8D0B3.B2B6D520@timpanogas.org> (raw)
In-Reply-To: <39F5999B.91DDC98@evision-ventures.com> <39F8C0BA.CF0F284D@timpanogas.org>



"Jeff V. Merkey" wrote:
> 
> Martin,
> 
> A lot of changes.  Have you tested this adequately?   Changes of this
> magnitude this late in the 2.4 cycle could break a lot of stuff.  I'll
> apply your patch, and let you know.
> 
> :-)
> 
> Jeff

Martin,

1.  Adaptec SCSI driver on a 4 x P6 POCA blows up with timeout errors
then hard hangs machine.
2.  DVD-RAM drive gets scsi timeout errors on AMD K6 System.
3.  Cannot see the MASHITA RW-CDROM with ide-scsi loaded with patch.
4.  2.4.0 hard locks on dual processor PIII 400Mhz during kernel boot.

:-)

Well, I tried the patch.  Looks like some SMP issues of some kind.  

Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-10-27  0:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <39F5999B.91DDC98@evision-ventures.com>
2000-10-26 23:39 ` PATCH: killing read_ahead[] Jeff V. Merkey
2000-10-27  0:47   ` Jeff V. Merkey [this message]
     [not found] <Pine.LNX.4.10.10010251036010.1337-100000@penguin.transmeta.com>
2000-10-30 16:35 ` Martin Dalecki
     [not found] <Pine.GSO.4.21.0010251435100.12098-100000@weyl.math.psu.edu>
2000-10-26 20:44 ` Linus Torvalds
2000-10-29 14:43   ` Alexander Viro

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=39F8D0B3.B2B6D520@timpanogas.org \
    --to=jmerkey@timpanogas.org \
    --cc=dalecki@evision-ventures.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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