From: Dylan Griffiths <Dylan_G@bigfoot.com>
To: Andrew Morton <andrewm@uow.edu.au>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: EEPro100 problems in SMP on 2.4.5 ?
Date: Sat, 30 Jun 2001 13:34:08 -0600 [thread overview]
Message-ID: <3B3E29B0.8B9AB310@bigfoot.com> (raw)
In-Reply-To: <3B3D4A96.A81A13AD@bigfoot.com> <3B3D61D3.CEDACC4D@uow.edu.au>
Andrew Morton wrote:
> 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.
That was locked as well, AFAIK.
> 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.
I'd love to do some of this, but since the box is now being shipped to a
colo facility in New York, I don't really have a choice in the matter.
Hopefully someone here doing SMP + EEPro100 can see if they can reproduce
the issue (2.4.5 kernel).
--
www.kuro5hin.org -- technology and culture, from the trenches.
next prev parent reply other threads:[~2001-06-30 19:33 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
2001-06-30 19:34 ` Dylan Griffiths [this message]
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=3B3E29B0.8B9AB310@bigfoot.com \
--to=dylan_g@bigfoot.com \
--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 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.