From: "Paul Rolland" <rol@as2917.net>
To: "'John Goerzen'" <jgoerzen@complete.org>, <linux-kernel@vger.kernel.org>
Subject: Re: Kernel 2.4.20 panic in scheduler
Date: Tue, 4 Feb 2003 07:57:51 +0100 [thread overview]
Message-ID: <002901c2cc1a$bc53f4f0$3f00a8c0@witbe> (raw)
In-Reply-To: <877kch8286.fsf@christoph.complete.org>
Hello,
Maybe unrelated, maybe not...
I too have a Dell 2650, Perc 3/Di and bcm5700, running 2.4.20...
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...
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 ?
Regards,
Paul
> -----Original Message-----
> From: linux-kernel-owner@vger.kernel.org
> [mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of John Goerzen
> Sent: Monday, February 03, 2003 10:49 PM
> To: linux-kernel@vger.kernel.org
> Subject: Re: Kernel 2.4.20 panic in scheduler
>
>
> Chris Wright <chris@wirex.com> writes:
>
> >> Today I experienced a kernel panic running kernel 2.4.20 (plus the
> >> ctx vserver patch; otherwise vanilla) with a bcm5700
> module added in.
> >> It's
> >
> > Have you tried this without the vserver patch? Last I looked it
> > touched many of the code paths in your trace below. Also, if
> > possible, set up a serial console, it'll be a lot easier to
> catch the
> > full trace.
>
> Unfortunately, this is on a production server, and such a
> drastic change to the configuration is not really possible at
> the moment. However, I have gone ahead and sent them this
> info. We will see.
>
> I'm already on the serial console option. Hope to have it soon.
>
> I saw a lot of TCP-related symbols. Is there any chance that
> this is a bug in the bcm5700 module? Or in the TCP stack?
>
> -- John
>
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in the body of a message to
> majordomo@vger.kernel.org More majordomo info at
http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2003-02-04 6:48 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 [this message]
2003-02-04 14:18 ` John Goerzen
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='002901c2cc1a$bc53f4f0$3f00a8c0@witbe' \
--to=rol@as2917.net \
--cc=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