public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frank de Lange <frank@unternet.org>
To: Andrew Morton <andrewm@uow.edu.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: QUESTION: Network hangs with BP6 and 2.4.x kernels, hardware related?
Date: Thu, 11 Jan 2001 22:09:43 +0100	[thread overview]
Message-ID: <20010111220943.F3269@unternet.org> (raw)
In-Reply-To: <20010110223015.B18085@unternet.org> <3A5D9D87.8A868F6A@uow.edu.au>
In-Reply-To: <3A5D9D87.8A868F6A@uow.edu.au>; from andrewm@uow.edu.au on Thu, Jan 11, 2001 at 10:48:23PM +1100

OK, just one last addition to what has nearly become my own thread...

I now am fairly certain that the problem (network stalls on multiprocessor systems) is not BP6 or NE2K-PCI specific. I found several postings which relate to similar problems on dissimilar hardware. Another interesting one is:

Re: PROBLEM : Networking stops working with kernel 2.4.0-test11 
  (http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg18722.html)

"...I have an almos identical system as you, 2x200MMX motherboard (Gigabyte
       586DX) also Voodoo3 (2000 pci) the same nic Realtek 8029AS, also a bt848
       tv card, also SCSI (Aic-7880 onboard, but not used).

       I have reported it some time ago, and now all I get with
       2.4.0-test11-pre4 and I think a additional patch is  NETDEV WATCHDOG:
       eth0: transmit timed out, and something in the console about lost irq?

       I can't reproduce it with a uniprocesor kernel, and I have a 3c503 card
       wich uses the 8390 module, so I suppose that the problem it's not in the
       8390, and it seems to be smp related...."


ne2k-pci freezes with APIC error on 2.4.0-testX SMP
  (http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg14468.html)

"...

       When doing massive NFS transfers (2.4 machine as the client) on my SMP
       box
       (Abit BP6 2x celeronA 533mhz (non-overclocked) 64Mb ram, latest
       apt-get-ed
       debian woody) my ne2k-pci card (Realtek Semiconductor Co., Ltd.
       RTL-8029(AS)
        (rev 0)) suddenly stops working. test5 spits that in syslog:..."

More to be found when searching the archives. This problem has been around for
a long, long time (probably since the current level of apic-support was added,
somewhere around 2.3.1x?). It has been reported by several people, several
times. I feel like rigging every apic-related piece of code with a zillion
bells and printk's but that would surely only create more mayhem as this whole
thing seems to be timing-related...

Anyone got any idea's on how to tackle this? Anyone who is 'intimate with' the
apic-related code? It'll take me some time to dive into that part, so if there
is anyone who already has taken the plunge, do tell...

Cheers//Frank

[ who is still running apic-less, without problems [
-- 
  WWWWW      _______________________
 ## o o\    /     Frank de Lange     \
 }#   \|   /                          \
  ##---# _/     <Hacker for Hire>      \
   ####   \      +31-320-252965        /
           \    frank@unternet.org    /
            -------------------------
 [ "Omnis enim res, quae dando non deficit, dum habetur
    et non datur, nondum habetur, quomodo habenda est."  ]
-
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/

  parent reply	other threads:[~2001-01-11 21:10 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-10 21:30 QUESTION: Network hangs with BP6 and 2.4.x kernels, hardware related? Frank de Lange
2001-01-10 22:21 ` Manfred Spraul
2001-01-10 22:29   ` Frank de Lange
2001-01-10 22:40   ` Frank de Lange
2001-01-11 11:48 ` Andrew Morton
2001-01-11 15:22   ` Frank de Lange
2001-01-11 16:55   ` Frank de Lange
2001-01-11 19:18   ` Frank de Lange
     [not found]     ` <3A5E0849.EB428D70@mandrakesoft.com>
2001-01-12  0:28       ` Frank de Lange
2001-01-12 11:40         ` Andrew Morton
2001-01-12 15:06           ` Frank de Lange
2001-01-12 15:36           ` Frank de Lange
2001-01-11 19:38   ` Frank de Lange
2001-01-11 19:49   ` Frank de Lange
2001-01-11 21:09   ` Frank de Lange [this message]
2001-01-11 21:47     ` Jeff Garzik
2001-01-11 21:53       ` Frank de Lange
2001-01-12 14:35       ` David Woodhouse
  -- strict thread matches above, loose matches on Subject: below --
2001-01-12 16:53 Manfred Spraul
2001-01-12 17:02 ` David Woodhouse
2001-01-12 17:16 Manfred Spraul
2001-01-12 17:33 ` Frank de Lange
2001-01-12 17:51   ` Manfred Spraul
2001-01-12 18:25     ` Frank de Lange
2001-01-12 19:04       ` Manfred Spraul
2001-01-12 19:07         ` Frank de Lange
2001-01-12 19:21         ` Frank de Lange
2001-01-12 19:33           ` Manfred Spraul
2001-01-12 19:52             ` Frank de Lange
2001-01-12 19:59               ` Linus Torvalds
2001-01-12 20:03                 ` Ingo Molnar
2001-01-14  0:13                   ` Roeland Th. Jansen
2001-01-14  0:23                     ` Frank de Lange
2001-01-12 20:05                 ` Frank de Lange
2001-01-12 21:21                 ` Frank de Lange
     [not found] <20010112165104.A22465@unternet.org>
2001-01-16 19:23 ` Maciej W. Rozycki

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=20010111220943.F3269@unternet.org \
    --to=frank@unternet.org \
    --cc=andrewm@uow.edu.au \
    --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