Re: Bug#700333: Stack trace

[Thomas Gleixner]

On Sun, 28 Apr 2013, Borislav Petkov wrote:

> On Sun, Apr 28, 2013 at 05:26:07PM +0400, vitalif@xxxxxxxxxx wrote:
> > >When you do a suspend/resume cycle.
> > 
> > OK, yes, I've found it there.
> > 
> > >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?
> > 
> > Yeah, now I'm using a patched kernel and it's OK.
> > 
> > So, does it mean the problem is fixed by this patch or it's just
> > confirmed and should be fixed by another one?
> 
> Well, it makes sense to me, at least: we remove the handler on suspend
> so that the HPET interrupt doesn't fire. If, when the box comes up
> again, the pending interrupt is cleared, then all is fine - we can
> safely register the handler again and everyone goes about their merry
> way.
> 
> But don't worry, if Thomas has an idea, it is almost guaranteed you'll
> get a proper fix soon. :-)

I merged a slightly better fix, you all were on cc. It's going into
3.10 and it's tagged stable, so it will show up in stable kernels
soon.

Thanks,

	tglx
--
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/