All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <andrewm@uow.edu.au>
To: Dylan Griffiths <Dylan_G@bigfoot.com>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: EEPro100 problems in SMP on 2.4.5 ?
Date: Sat, 30 Jun 2001 15:21:23 +1000	[thread overview]
Message-ID: <3B3D61D3.CEDACC4D@uow.edu.au> (raw)
In-Reply-To: <3B3D4A96.A81A13AD@bigfoot.com>

Dylan Griffiths wrote:
> 
>         Hi.  While doing some file tranfers to our new server (a Compaq Proliant
> 8way XEON 500 with 4gb ram and an EEPro100 NIC), the box socked solid (no
> oops, no response via network, no response via console).  The other hardware
> in the system was a Compaq Smart Array 9SMART2 driver).  It's running
> Slackware 7.1.  The other system was a dual P3 450 running Redhat 7.1 (Linux
> velocity.kuro5hin.org 2.4.2-2smp #1 SMP Sun Apr 8 20:21:34 EDT 2001 i686
> unknown) w/ 3c59x NIC.  The Redhat machine experienced no problems.
>         In Uni processor mode, the system is totally stable.  But only using 1/8th
> of its power :-/  We had to roll back to 2.2.19 with a bigmem patch, but
> we'd like to have a stable 2.4 kernel to use (since it's so much better SMP
> wise, throughput wise, etc).

Some things to try:

1: Include `magic sysrq' support in the kernel and use ALT-SYSRQ-T and S
   when it has locked up.   If you get some traces then please feed them
   into `ksymoops -m System.map' and report back.

2: If the above doesn't work, add `nmi_watchdog=1' to the kernel boot
   options.  That may catch the lockup.

3: Replace the NIC with another eepro100.  If the problem goes away then
   chuck the old one.

4: Replace the NIC with one of a different type (ie: swap with the other
   machine). If that fixes it we look at the ethernet driver.  Otherwise
   we look at, umm, the rest of the kernel.

-

  reply	other threads:[~2001-06-30  5:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-30  3:42 EEPro100 problems in SMP on 2.4.5 ? Dylan Griffiths
2001-06-30  5:21 ` Andrew Morton [this message]
2001-06-30 19:34   ` Dylan Griffiths
2001-07-01 16:22     ` John Jasen
2001-06-30 10:04 ` Vibol Hou
  -- strict thread matches above, loose matches on Subject: below --
2001-12-26 20:43 Arturas V
2001-12-26 22:43 ` Legacy Fishtank
2001-12-27  5:21   ` Idrigal (Eric Rautenkranz)
2001-12-27 12:47 Zwane Mwaikambo
2001-12-28 13:49 ` Anton Tinchev
2001-12-28 10:37 Zwane Mwaikambo
2001-12-28 20:43 ` Anton Tinchev
2001-12-28 10:53   ` Zwane Mwaikambo
2001-12-28 20:57     ` Anton Tinchev

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=3B3D61D3.CEDACC4D@uow.edu.au \
    --to=andrewm@uow.edu.au \
    --cc=Dylan_G@bigfoot.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 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.