linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Troß" <mtross@compu-shack.com>
To: "Udo A. Steinberg" <us15@os.inf.tu-dresden.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: CPU Lockup with 2.4.21 and 2.4.22-pre
Date: 22 Jul 2003 12:24:24 +0200	[thread overview]
Message-ID: <1058869462.2352.79.camel@mtross2.csintern.de> (raw)
In-Reply-To: <0001F3D0@gwia.compu-shack.com>

Am Mon, 2003-07-21 um 16.17 schrieb Udo A. Steinberg:
> On Mon, 21 Jul 2003 16:12:26 +0200 Udo A. Steinberg (UAS) wrote:
> 
> UAS> We have a Dual-Xeon machine with Hyperthreading which keeps locking
> up hard,
> UAS> so that not even Sysrq works anymore. I have captured such a lockup
> using the
> UAS> NMI oopser. Below you'll find the lockup fed through ksymoops. Note
> that
> UAS> after CPU3 locked up, CPU2 did too. But that lockup couldn't be
> captured
> UAS> anymore. Kernel is a monolithic 2.4.22-pre6. Problem also happened
> on
> UAS> plain 2.4.21. I can provide more information wrt. hardware, config
> etc.
> UAS> on request.

Would be really useful if you do so.

> Sorry, I used the wrong System.map. Below is the fixed decode. Looks
> like
> the lockup is caused by the 3rd party Compushack FDDI driver.

What makes you believe this? There is no matching code sequence like the
one from your dump in the driver, to be exact: in a driver compiled with
gcc 3.3 and kernel 2.4.21.

> Regards,
> -Udo.

Regards,
Michael


       reply	other threads:[~2003-07-22 10:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0001F3D0@gwia.compu-shack.com>
2003-07-22 10:24 ` Michael Troß [this message]
2003-07-22 11:51   ` CPU Lockup with 2.4.21 and 2.4.22-pre Udo A. Steinberg
     [not found] <0001F49C@gwia.compu-shack.com>
2003-07-22 15:26 ` Michael Troß
2003-07-22 15:30   ` Udo A. Steinberg
     [not found] <0001F474@gwia.compu-shack.com>
2003-07-22 12:55 ` Michael Troß
2003-07-22 14:24   ` Udo A. Steinberg
2003-07-21 14:12 Udo A. Steinberg
2003-07-21 14:17 ` Udo A. Steinberg

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=1058869462.2352.79.camel@mtross2.csintern.de \
    --to=mtross@compu-shack.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=us15@os.inf.tu-dresden.de \
    /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).