From: bert hubert <ahu@ds9a.nl>
To: Brian McEntire <brianm@fsg1.nws.noaa.gov>
Cc: linux-kernel@vger.kernel.org, jgarzik@pobox.com, netdev@oss.sgi.com
Subject: Re: Suggestions with hard lockup on 4 systems, have oops report
Date: Fri, 16 Jul 2004 21:18:50 +0200 [thread overview]
Message-ID: <20040716191850.GA5997@outpost.ds9a.nl> (raw)
In-Reply-To: <Pine.LNX.4.44.0407161025030.20914-200000@fsg1.nws.noaa.gov>
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! :)
You are running one of the kernels not a lot of people outside of red hat
know the details about.
> The systems are:
> Dual Xeon 2.4GHz processors
> 2 GB RAM
> 2 GB swap
> Ethernet controller: PCI device 14e4:16a7 (BROADCOM Corporation) (rev 2)
> Dual channel SCSI storage controller: PCI device 1000:0030 (Symbios
> Logic Inc. (formerly NCR)) (rev 7)
This kind of hardware just asks for 2.6. Furthermore, you'll find that
current kernel hackers will be in a far better position to help you.
> bcm5700-7.1.22-1
In a recent kernel, you will probably be able to use the tg3 driver instead
of this vendor supplied one, which is generally considered to be inferior or
at least uglier than the in kernel one.
> Code; f89b669f <[bcm5700]LM_ServiceInterrupts+cf/230>
> 00000000 <_EIP>:
> Code; f89b669f <[bcm5700]LM_ServiceInterrupts+cf/230> <=====
> 0: c7 03 00 00 00 00 movl $0x0,(%ebx) <=====
I'm no expert, but this strongly looks like problems in the broadcom driver.
> 133 warnings and 7 errors issued. Results may not be reliable.
2.6 also has a built-in ksymoops, which gives far more reliable results.
Good luck!
--
http://www.PowerDNS.com Open source, database driven DNS Software
http://lartc.org Linux Advanced Routing & Traffic Control HOWTO
prev parent reply other threads:[~2004-07-16 19:18 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
2004-07-16 19:18 ` bert hubert [this message]
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=20040716191850.GA5997@outpost.ds9a.nl \
--to=ahu@ds9a.nl \
--cc=brianm@fsg1.nws.noaa.gov \
--cc=jgarzik@pobox.com \
--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).