[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1173112936.31337.26.camel@imap.mvista.com>
Date: Mon, 05 Mar 2007 08:42:16 -0800
From: Daniel Walker <dwalker@...sta.com>
To: Ingo Molnar <mingo@...e.hu>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Adrian Bunk <bunk@...sta.de>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Michal Piotrowski <michal.k.k.piotrowski@...il.com>,
Thomas Gleixner <tglx@...utronix.de>,
Emil Karlson <jkarlson@...hut.fi>,
"Michael S. Tsirkin" <mst@...lanox.co.il>,
Soeren Sonnenburg <kernel@....de>
Subject: Re: [5/6] 2.6.21-rc2: known regressions
On Mon, 2007-03-05 at 16:27 +0100, Ingo Molnar wrote:
> * Daniel Walker <dwalker@...sta.com> wrote:
>
> > > > FYI, this is not a "wont boot" problem, this should be a "NMI
> > > > watchdog does not work" problem - which has far lower severity.
> > > > Also, Thomas did a fix for this which is now in -mm.
> > >
> > > yup, you should be able to cross this one off, Adrian. The fix
> > > worked for me, at least.
> >
> > I didn't see a fix for this one go by .. I'll check the usual places I
> > guess ..
>
> find it below.
This fix gets the NMI to tick like the timer (in /proc/interrupts) ..
However, now that it's ticking I don't think it's actually working
properly ..
I used this simple test case given by you a long time ago,
main ()
{
iopl(3);
for (;;)
asm("cli");
}
This doesn't look like a regression tho, 2.6.19-rc6 has the same
behavior ..
Daniel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists