public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pete Zaitcev <zaitcev@redhat.com>
To: James Bourne <jbourne@mtroyal.ab.ca>
Cc: zaitcev@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: lockups with 2.4.20 (tg3? net/core/dev.c|deliver_to_old_ones)
Date: Fri, 14 Feb 2003 16:02:16 -0500	[thread overview]
Message-ID: <200302142102.h1EL2GE28325@devserv.devel.redhat.com> (raw)
In-Reply-To: <mailman.1045255801.17177.linux-kernel2news@redhat.com>

> Since sometime in December two systems we have on site using P4 HT (one
> Dell 2650 and one Dell 4600, both dual CPU, both ht/mce capable) have been
> locking up without any kernel output and without sysrq keys working (the
> keyboard is locked solid).
>[...]
> Using nmi_watchdog I've managed to get a stack track and ran ksymoops over
> it (attached).

Good report. To tell the truth, I know that this lockup exists,
there's an RH issue-tracker item against me on this.
It is different from the old "porkchop" lockup, which DaveM and
Jeff Garzik fixed.

The stumbling block is that NMI oopser catches a thread which
gets stuck because of the lock, but this does not explain
how the lock was taken.

I think the best resolution would be an instrumentation patch
which records lock takers, and prints them when the thing is
forcefuly oopsed. I should come with it eventually, if someone
does not beat me to it (I wish they did, actually :-)

-- Pete

       reply	other threads:[~2003-02-14 20:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1045255801.17177.linux-kernel2news@redhat.com>
2003-02-14 21:02 ` Pete Zaitcev [this message]
2003-02-26 15:29 lockups with 2.4.20 (tg3? net/core/dev.c|deliver_to_old_ones) Rhodes, Tom
2003-02-26 16:03 ` Jeff Garzik
2003-03-07 23:29   ` Magnus Naeslund(f)
2003-02-26 19:56 ` Pete Zaitcev
2003-02-26 20:54   ` Mikael Pettersson
  -- strict thread matches above, loose matches on Subject: below --
2003-02-26  7:00 Rhodes, Tom
2003-02-26 12:45 ` Denis Vlasenko
2003-02-16 16:09 Manfred Spraul
2003-02-14 20:39 James Bourne
2003-02-18  2:48 ` David S. Miller
2003-02-18  4:21   ` James Bourne
2003-02-18  5:12     ` David S. Miller
2003-02-18  6:04       ` James Bourne

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=200302142102.h1EL2GE28325@devserv.devel.redhat.com \
    --to=zaitcev@redhat.com \
    --cc=jbourne@mtroyal.ab.ca \
    --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