mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Robbert Kouprie" <robbert@jvb.tudelft.nl>
To: "'Stephan von Krawczynski'" <skraw@ithnet.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: NIC lockup in 2.4.17 (SMP/APIC/Intel 82557)
Date: Thu, 31 Jan 2002 01:27:47 +0100	[thread overview]
Message-ID: <002a01c1a9ee$1b6ddd20$020da8c0@nitemare> (raw)
In-Reply-To: <20020130220659.29bd66f5.skraw@ithnet.com>

Thanks for your reaction Stephan, but I seriously doubt the change below
would fix the problem... Also, as the problem appears randomly, and
usually after some uptime, I obviously can not know about it being fixed
if I constantly upgrade the kernel. I'd rather wait and see if it
appears again in time after I did a kernel upgrade, and not trying every
-pre while there's no mention on the mailing list of such bug being
fixed.

Anyway, I just rebooted with 2.4.18-pre7-ac1, we'll see if it helps.

Regards,
- Robbert


radium:/usr/src# diff -u linux.18p3-ac2/drivers/net/eepro100.c
linux.18p7-ac1/drivers/net/eepro100.c 
--- linux.18p3-ac2/drivers/net/eepro100.c       Fri Dec 21 18:41:54 2001
+++ linux.18p7-ac1/drivers/net/eepro100.c       Thu Jan 31 00:35:56 2002
@@ -28,7 +28,7 @@
 */
 
 static const char *version =
-"eepro100.c:v1.09j-t 9/29/99 Donald Becker
http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html\n"
+"eepro100.c:v1.09j-t 9/29/99 Donald Becker
http://www.scyld.com/network/eepro100.html\n"
 "eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V.
Savochkin <saw@saw.sw.com.sg> and others\n";
 
 /* A few user-configurable values that apply to all boards.


> -----Original Message-----
> From: Stephan von Krawczynski [mailto:skraw@ithnet.com] 
> Sent: woensdag 30 januari 2002 22:07
> To: Robbert Kouprie
> Cc: linux-kernel@vger.kernel.org
> Subject: Re: NIC lockup in 2.4.17 (SMP/APIC/Intel 82557)
> 
> 
> On Wed, 30 Jan 2002 20:29:15 +0100
> "Robbert Kouprie" <robbert@jvb.tudelft.nl> wrote:
> 
> > Not much new, but still:
> > 
> > Today I got the same problem again with 2.4.18-pre3-ac2. Network
> > connections stuck, NFS mounts stuck. Bringing down/up the interface
> > doesn't help. Seems like the NIC is really in trouble here. Only a
> > reboot would bring the nick back in use.
> > 
> > Still no testcase though, and I have no idea on how to 
> investigate this
> > :(
> > Can anyone give a hint as where to seek?
> 
> How about www.kernel.org? Download _latest_ kernel-patch 
> (-pre7) and tell us
> about it. As long as you are trying only old pre's there is 
> not much of
> a chance any important brain will listen to you.
> 
> Regards,
> Stephan
> (no important brain)
> 


  reply	other threads:[~2002-01-31  0:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-22  8:51 Robbert Kouprie
2002-01-22 14:53 ` James Bourne
2002-01-30 19:29   ` Robbert Kouprie
2002-01-30 21:06   ` Stephan von Krawczynski
2002-01-31  0:27     ` Robbert Kouprie [this message]
2002-01-31 12:35     ` Stephan von Krawczynski
2002-01-31 16:32       ` Ben Greear
2002-01-31 16:52         ` Robbert Kouprie
2002-01-31 17:54           ` Ben Greear
2002-01-31 19:17             ` Robbert Kouprie
2002-02-01 17:52           ` PCI Problems [was Re: NIC lockup in 2.4.17 (SMP/APIC/Intel 82557)] Edward S. Marshall
2002-02-01 18:16             ` nick
2002-02-01 19:44               ` Ken Brownfield
2002-02-01 23:54             ` Alan Cox
     [not found] <Pine.LNX.4.33.0201201531570.6499-100000@coffee.psychology.mcmaster.ca>
2002-01-21 10:06 ` NIC lockup in 2.4.17 (SMP/APIC/Intel 82557) Robbert Kouprie
     [not found] <yqo1ygkd8np.fsf@penguin.ucs.ed.ac.uk>
2002-01-20 21:53 ` Robbert Kouprie
2002-01-21 18:48   ` Jussi Laako
  -- strict thread matches above, loose matches on Subject: below --
2002-01-20 19:16 Robbert Kouprie

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='002a01c1a9ee$1b6ddd20$020da8c0@nitemare' \
    --to=robbert@jvb.tudelft.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=skraw@ithnet.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

Powered by JetHome