[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2666050d6d50efdbfa3503aa10c0e5ec@yourcmc.ru>
Date: Sat, 27 Apr 2013 19:08:42 +0400
From: vitalif@...rcmc.ru
To: Thomas Gleixner <tglx@...utronix.de>
Cc: Borislav Petkov <bp@...en8.de>,
Ben Hutchings <ben@...adent.org.uk>,
"Venkatesh Pallipadi (Venki)" <venki@...gle.com>,
<700333@...s.debian.org>, LKML <linux-kernel@...r.kernel.org>,
Clemens Ladisch <clemens@...isch.de>
Subject: Re: Bug#700333: Stack trace
> Looks like we can't do anything about that in the HPET code itself.
>
> Vitaliy, could you try that patch ?
Thanks, I've tried it several days ago (and still using a patched
kernel :)) - the box survives.
But at which moment should I check for "Spurious interrupt" in dmesg?
--
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