Re: Bug#700333: Stack trace

2013-04-30 Thread vitalif
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 for the fix! But where did you post it - on LKML? (I didn't see it because I'm not subscribed to LKML?) -- To unsubscribe from this list: send the li

Re: Bug#700333: Stack trace

2013-04-28 Thread Thomas Gleixner
On Sun, 28 Apr 2013, Borislav Petkov wrote: > On Sun, Apr 28, 2013 at 05:26:07PM +0400, vita...@yourcmc.ru 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 hibernat

Re: Bug#700333: Stack trace

2013-04-28 Thread Borislav Petkov
On Sun, Apr 28, 2013 at 05:26:07PM +0400, vita...@yourcmc.ru 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 > >gu

Re: Bug#700333: Stack trace

2013-04-28 Thread vitalif
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 kerne

Re: Bug#700333: Stack trace

2013-04-27 Thread Borislav Petkov
On Sat, Apr 27, 2013 at 07:08:42PM +0400, vita...@yourcmc.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 whic

Re: Bug#700333: Stack trace

2013-04-27 Thread vitalif
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

Re: Bug#700333: Stack trace

2013-04-25 Thread Thomas Gleixner
On Mon, 22 Apr 2013, Thomas Gleixner wrote: > With the patch below, the box should survive and we should see a > > "Spurious HPET timer interrupt on HPET timer..." entry in dmesg. > > That's a first workaround to confirm my theory. I'll look into the > HPET code how we can avoid that at all. Lo

Re: Bug#700333: Stack trace

2013-04-22 Thread Thomas Gleixner
On Sun, 21 Apr 2013, Borislav Petkov wrote: > + tglx. > > On Sun, Apr 21, 2013 at 01:38:33AM +0400, vita...@yourcmc.ru wrote: > > >>Stack trace picture is here: > > >>http://vmx.yourcmc.ru/var/pics/IMG_20130306_141045.jpg > > > > > >Vitaliy reported that his system crashes when suspending to disk

Re: Bug#700333: Stack trace

2013-04-20 Thread Borislav Petkov
+ tglx. On Sun, Apr 21, 2013 at 01:38:33AM +0400, vita...@yourcmc.ru wrote: > >>Stack trace picture is here: > >>http://vmx.yourcmc.ru/var/pics/IMG_20130306_141045.jpg > > > >Vitaliy reported that his system crashes when suspending to disk. > >This > >was a regression from 3.2 to 3.7, and remains

Re: Bug#700333: Stack trace

2013-04-20 Thread vitalif
Stack trace picture is here: http://vmx.yourcmc.ru/var/pics/IMG_20130306_141045.jpg Vitaliy reported that his system crashes when suspending to disk. This was a regression from 3.2 to 3.7, and remains in 3.8. Some details of this system are in the bug log at .

Re: Bug#700333: Stack trace

2013-03-10 Thread Ben Hutchings
On Wed, 2013-03-06 at 15:27 +0400, vita...@yourcmc.ru wrote: [...] > Stack trace picture is here: > http://vmx.yourcmc.ru/var/pics/IMG_20130306_141045.jpg Vitaliy reported that his system crashes when suspending to disk. This was a regression from 3.2 to 3.7, and remains in 3.8. Some details of