All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Jack Steiner <steiner@sgi.com>, Andrew Morton <akpm@osdl.org>,
	Ravikiran G Thirumalai <kiran@in.ibm.com>,
	linux-kernel@vger.kernel.org
Subject: Re: hot cache line due to note_interrupt()
Date: Sat, 15 Nov 2003 00:18:05 -0500	[thread overview]
Message-ID: <3FB5B70D.3090309@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0311141015050.1861-100000@home.osdl.org>

Linus Torvalds wrote:
> The fact is, irqdebug _has_ resulted in a few reports where instead of a 
> silent and total lock-up, the kernel just said "I'll disable this irq" and 
> the machine continued limping along.


I strongly agree.

There are two huge reasons I develop and debug drivers solely in 2.6 
now: kksymoops and irqdebug.  Both have helped a great deal in tracking 
down problems.  Indeed, screaming irqs that lead to lockups are 
instantly detected in 2.6.

But hey... I'm just a developer.  Who can say whether it should be on by 
default?

	Jeff




  reply	other threads:[~2003-11-15  5:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-10 21:58 hot cache line due to note_interrupt() Jack Steiner
2003-11-10 23:00 ` Anton Blanchard
2003-11-11  8:29 ` Ravikiran G Thirumalai
2003-11-11 16:25   ` Anton Blanchard
2003-11-11 19:58   ` Andrew Morton
2003-11-14 17:45     ` Jack Steiner
2003-11-14 17:57       ` Andrew Morton
2003-11-14 18:11         ` Jack Steiner
2003-11-14 18:10       ` David Mosberger
2003-11-14 18:17       ` Linus Torvalds
2003-11-15  5:18         ` Jeff Garzik [this message]
2003-11-14 19:10       ` Anton Blanchard
2003-11-14 19:28         ` Mike Fedyk
  -- strict thread matches above, loose matches on Subject: below --
2003-11-10 19:08 Jack Steiner
2003-11-10 19:22 ` David Mosberger
2003-11-10 20:23 ` Jack Steiner

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=3FB5B70D.3090309@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=akpm@osdl.org \
    --cc=kiran@in.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=steiner@sgi.com \
    --cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.