linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Charlton Harrison <charlton@dynet.com>
To: linux-kernel@vger.kernel.org
Subject: PROBLEM: 2.4.19 & 2.4.20 hang without oops...
Date: Tue, 7 Jan 2003 00:52:29 -0600	[thread overview]
Message-ID: <20030107005229.A28504@bach.dynet.com> (raw)

Hello Everyone,


I'd like to report a (probable) kernel bug in v2.4.19 and v2.4.20.
This problem does NOT appear in 2.4.18 and I've had to go back to
that kernel for now.

The problem is as follows:
While attempting to copy about 50GB of data onto an NFS-mounted partition,
the `cp -a` process will go for a while, then my machine will hang/freeze up.

I can reproduce it very easily and quickly on kernel 2.4.19 and 2.4.20,
and most of the time happens before even copying 10GB worth of data.
I am unable to reproduce the problem on kernel 2.4.18.

Here are the specifics:

HARDWARE:

Dual (SMP) P3-500,  supermicro MB,  512MB ECC buffered SDRAM.
3c905b ethernet card.
EIDE hard drive operating on a 16MHz (UDMA *disabled*) bus.


SOFTWARE:

Compiled the kernel with Redhat GCC v2.96.
(I also compiled v2.4.18 the same way and it works)


I am very concerned about this bug and that it doesn't seem to be fixed
in the latest Linux 2.4 kernels.

For additional information,  please feel free to e-mail me.  Or, if you
happen to know something about this bug already,  please e-mail me.

Thanks!


Charlton Harrison
charlton@dynet.com

             reply	other threads:[~2003-01-07  6:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-07  6:52 Charlton Harrison [this message]
2003-01-08 14:45 ` PROBLEM: 2.4.19 & 2.4.20 hang without oops Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2003-01-07 16:25 Matthew Costello
2003-01-11  6:35 Matthew Costello

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=20030107005229.A28504@bach.dynet.com \
    --to=charlton@dynet.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;
as well as URLs for NNTP newsgroup(s).