mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jens Kübler" <cleanerx@au.hadiko.de>
To: linux-kernel@vger.kernel.org
Subject: nforce2 keeps crashing with 2.4.27pre3
Date: Wed, 26 May 2004 17:56:35 +0200	[thread overview]
Message-ID: <200405261756.35333.cleanerx@au.hadiko.de> (raw)

Hi

I have grabbed the latest pre of the kernel and compiled everything. At bootup 
the nforce2 fixup message appears but as soon as I cause heavy network 
traffic the system still locks up. 
I'm using a rtl8169 1Gbit network card which reads data from a 1Gbit connected 
raid10 so transfer rates can get pretty high (some tests gave me about 70MB/s 
reading)

The system runs fine with the apic tack patch that i use since december 
(kernel 2.4.23) except for my new gigabit network card.
I'm importing different network shares via nfs and the gigabit seems to have 
problems with this patch. When traffic rises the kernel considers that the 
nfs server is not responding and waits for it to come back. It does after 
some time and then this cycle starts again and again. Transfer rates drop due 
to this to less than 1Mb/s.

When I installed 2.4.27pre3 i had none of these nfs timeouts but the system 
halt. The whole home directory is imported via nfs and it seemed for me much 
more responsive than with the apic tack patched kernel.

I will be greatful for any suggestions.

Btw: I'm not subscribed so please send cc to me ;-)

Jens


             reply	other threads:[~2004-05-26 15:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-26 15:56 Jens Kübler [this message]
2004-05-26 16:24 ` Jeff Garzik
2004-05-26 17:16   ` Francois Romieu
2004-05-26 17:22     ` Jeff Garzik
2004-05-26 20:47       ` r8169 backport for 2.4.27-pre3 (was: Re: nforce2 keeps crashing with 2.4.27pre3) Francois Romieu
2004-05-27 17:28         ` r8169 backport for 2.4.27-pre3 Jeff Garzik
2004-05-26 17:07 ` nforce2 keeps crashing with 2.4.27pre3 Francois Romieu
2004-05-27 11:01   ` Jens Kübler

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=200405261756.35333.cleanerx@au.hadiko.de \
    --to=cleanerx@au.hadiko.de \
    --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®