From: Adam Kropelin <akropel1@rochester.rr.com>
To: Brian McEntire <brianm@fsg1.nws.noaa.gov>
Cc: kaos@ocs.com.au, linux-kernel@vger.kernel.org, akpm@zip.com.au,
jgarzik@pobox.com, netdev@oss.sgi.com
Subject: Re: Suggestions with hard lockup on 4 systems, have oops report
Date: Fri, 16 Jul 2004 14:08:12 -0400 [thread overview]
Message-ID: <20040716140812.A8270@mail.kroptech.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0407161025030.20914-200000@fsg1.nws.noaa.gov>; from brianm@fsg1.nws.noaa.gov on Fri, Jul 16, 2004 at 11:01:39AM -0400
On Fri, Jul 16, 2004 at 11:01:39AM -0400, Brian McEntire wrote:
> Thank you for taking time from your busy days to read this. You all
> (kernel maintainers) rock! :)
>
> I have four Linux hosts, with identical hardware and OSs, that exhibit a
> very tough to troubleshoot hang/freeze. About once every two weeks (and
<snip>
> The OS specifics:
> RH 7.2 with latest patches except running kernel 2.4.9-31enterprise for
> CM reasons (at one point, I tried the latest available RH 7.2 kernel but
> it did not improve stability so I went back.)
> bcm5700-7.1.22-1
> nvidia ?? (no RPM listed, didn't know where to find the version.)
You've really got to eliminate the binary bcm5700 and nvidia modules in
order to diagnose this. Based on the oops, bcm5700 looks suspect, but it
could just be the unlucky guy whose memory was stepped on by nvidia or
some other part of the kernel.
Switch to an open NIC like e1000 temporarily (or better yet,
permanently) and see if the lockup persists. Do the same with nvidia. If
you can reproduce the problem without ever having loaded either module
(unloading the module once it's loaded is not sufficient), post the new
oops and you'll have a solid foundation for debugging.
--Adam
next prev parent reply other threads:[~2004-07-16 18:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-16 15:01 Suggestions with hard lockup on 4 systems, have oops report Brian McEntire
2004-07-16 18:08 ` Adam Kropelin [this message]
2004-07-16 19:18 ` bert hubert
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=20040716140812.A8270@mail.kroptech.com \
--to=akropel1@rochester.rr.com \
--cc=akpm@zip.com.au \
--cc=brianm@fsg1.nws.noaa.gov \
--cc=jgarzik@pobox.com \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).