Re: WARN_ON report from clockevents_program_event

[Thomas Gleixner]

On Mon, 18 Apr 2011, Dave Jones wrote:
> On Mon, Apr 18, 2011 at 09:35:19AM +0200, Thomas Gleixner wrote:
>  > > hrtimer: interrupt took 47180328 ns
>  > 
>  > Huch, what did you do to make the timer interrupt run 47ms ? There is
>  > something badly wrong.
> 
> This is probably a 'root shot himself in the foot' thing.
> 
> I ran my system call fuzzer from a wrong shell, which was a very bad idea.
> (It seems to have actually destroyed the hardware, no longer even POSTs. oops).

Yikes. That's scary. Did you end up injecting malicious microcode ?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/