From: John Goerzen <jgoerzen@complete.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.4.20 panic in scheduler
Date: Tue, 04 Feb 2003 08:18:30 -0600 [thread overview]
Message-ID: <87vg005du1.fsf@christoph.complete.org> (raw)
In-Reply-To: 002901c2cc1a$bc53f4f0$3f00a8c0@witbe
"Paul Rolland" <rol@as2917.net> writes:
> Maybe unrelated, maybe not...
> I too have a Dell 2650, Perc 3/Di and bcm5700, running 2.4.20...
Are you running the RedHat kernel?
If so, check out:
http://lists.us.dell.com/pipermail/linux-poweredge/2002-November/010486.html
There have been many reports on the PowerEdge list of trouble with the
tg3 driver in various RedHat kernels. To date, it seems that the tg3
driver in the stock Linus kernels does not cause the hang, though
there may be some other bugs, especially wrt IPv6. Specifically,
there are serious incompatibilities with Apache when running IPv6:
http://lists.us.dell.com/pipermail/linux-poweredge/2003-February/011532.html
> What I see is the machine hang (really hang, nothing on the console,
> still pinging but nothing else) why doing two or three simultaneous
> copy of a 2 Gb file between the three 75Gb disks I have...
Sounds like the tg3 bug people have been complaining of.
> I other question : bcm5700 is supported in RedHat, as a module
> only. At the same time, Kernel includes support for Broadcomm
> Tigon3... Is it safe to use Tigon3 driver with a bcm5700 hardware ?
As above, it seems it is OK to do so if you are NOT running a RedHat
kernel and you are NOT using IPv6.
The PowerEdge list is a good one. A couple of Dell and RedHat hackers
hang out there, and although I run Debian exclusively, if you want
info about your particular hardware, it's a good place to check.
-- John
prev parent reply other threads:[~2003-02-04 14:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-03 20:33 Kernel 2.4.20 panic in scheduler John Goerzen
2003-02-03 21:35 ` Chris Wright
2003-02-03 21:48 ` John Goerzen
2003-02-04 6:57 ` Paul Rolland
2003-02-04 14:18 ` John Goerzen [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=87vg005du1.fsf@christoph.complete.org \
--to=jgoerzen@complete.org \
--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