All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Gecius <jens@gecius.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Longstanding APIC/NE2K bug
Date: 17 Jun 2001 02:25:00 -0400	[thread overview]
Message-ID: <87d783ei83.fsf@maniac.gecius.de> (raw)
In-Reply-To: <20010617000645.A2022@zarq.dhs.org>
In-Reply-To: <20010617000645.A2022@zarq.dhs.org> (rc@zarq.dhs.org's message of "Sun, 17 Jun 2001 00:06:45 -0400")

	rc@zarq.dhs.org writes:

> There has been a bug in the 2.4.x series of kernels for a long time (at
> least -pre9) concerning SMP and ne2k-pci.
> 
> Maciej W. Rozycki posted a patch back during 2.4.0 that fixed this problem
> "[patch] 2.4.0, 2.4.0-ac12: APIC lock-ups" in late January.  I've been
> trying new kernels regularly since, and the patch doesn't seem to have
> made it in (tested 2.4.2, .3, .4 and .5).  Falling back on my patched
> 2.4.0 works fine.
> 
> Symptoms: Network driver locks up.  Repeated messages of "ETH0: Transmit
> timeout" occurs.  Unloading and reloading network drivers does not help,
> reboot is required.  Usually only triggered by heavy network traffic
> (300-400 megs at 700k or so usually does it).

This fits exactly my problems I mentioned a couple weeks ago. Same
question here. Therefore my question: can we expect to see this patch
implemented? If not, any other suggestions?

-- 
Tschoe,                    Get my gpg-public-key here
 Jens                     http://gecius.de/gpg-key.txt

  reply	other threads:[~2001-06-17  6:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-17  4:06 Longstanding APIC/NE2K bug rc
2001-06-17  6:25 ` Jens Gecius [this message]
2001-06-18  6:08 ` Raphael Manfredi

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=87d783ei83.fsf@maniac.gecius.de \
    --to=jens@gecius.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.