mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Zwane Mwaikambo <zwane@holomorphy.com>
Cc: Luuk van der Duim <l.a.van.der.duim@student.rug.nl>,
	<linux-kernel@vger.kernel.org>
Subject: Re: 2.5.59-mm6
Date: Mon, 27 Jan 2003 21:11:37 +0100	[thread overview]
Message-ID: <5.1.1.6.2.20030127210954.00c73468@pop.gmx.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0301271414230.28141-100000@montezuma.mastece nde.com>

At 02:17 PM 1/27/2003 -0500, Zwane Mwaikambo wrote:
>On Mon, 27 Jan 2003, Mike Galbraith wrote:
>
> > (something seems funky with nmi_watchdog... hard lock = no_more_nmi_ticks
> > .  Anybody out there know enough about local APIC to explain why idle=poll
> > gives nice 1 second nmi, but everything else depends upon cpu load?... and
> > why when hardlock happens, it _stops_)
>
>Because we base the performance counter on unhalted cycles, whilst the
>normal idle function does an hlt. I think the K7 can do halted too.

(well bugger, I _know_ I'm gonna regret this;)

When can the darn thing actually trigger an oops?

         -Mike


  parent reply	other threads:[~2003-01-27 20:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-27 12:27 2.5.59-mm6 Luuk van der Duim
2003-01-27 18:50 ` 2.5.59-mm6 Mike Galbraith
2003-01-27 19:17   ` 2.5.59-mm6 Zwane Mwaikambo
     [not found]   ` <Pine.LNX.4.44.0301271414230.28141-100000@montezuma.mastece nde.com>
2003-01-27 20:11     ` Mike Galbraith [this message]
2003-01-27 21:13       ` 2.5.59-mm6 Zwane Mwaikambo
  -- strict thread matches above, loose matches on Subject: below --
2003-01-27  7:10 2.5.59-mm6 Andrew Morton
2003-01-27  8:17 ` 2.5.59-mm6 Andres Salomon
2003-01-27  8:24   ` 2.5.59-mm6 Joshua Kwan
2003-01-27  8:40     ` 2.5.59-mm6 Andrew Morton
2003-01-27  8:46       ` 2.5.59-mm6 Joshua Kwan
2003-01-27  9:51 ` 2.5.59-mm6 Helge Hafting

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=5.1.1.6.2.20030127210954.00c73468@pop.gmx.net \
    --to=efault@gmx.de \
    --cc=l.a.van.der.duim@student.rug.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zwane@holomorphy.com \
    /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

all inboxes | Powered by JetHome®