[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130427154956.GC4358@pd.tnic>
Date: Sat, 27 Apr 2013 17:49:56 +0200
From: Borislav Petkov <bp@...en8.de>
To: vitalif@...rcmc.ru
Cc: Thomas Gleixner <tglx@...utronix.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
On Sat, Apr 27, 2013 at 07:08:42PM +0400, vitalif@...rcmc.ru wrote:
> >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?
When you do a suspend/resume cycle.
The bug says "The photo shows a BUG in hrtimer_interrupt() after making
the hibernation image and while resuming the non-boot CPUs." so I'm
guessing with Thomas' patch it suspends fine now?
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
--
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