Re: Suspend resume problem (WAS Re: [ANNOUNCE] 3.8.10-rt6)

2013-05-03 Thread Steven Rostedt
On Fri, 2013-05-03 at 11:59 +0200, Sebastian Andrzej Siewior wrote: > > > As the NMI dump only happens because of the time jump, which as you > > said, is -rt only, I wouldn't say that the NMI deadlock is a mainline > > bug. > > The reason for the NMI was a bug in the -RT tree but if something e

Re: Suspend resume problem (WAS Re: [ANNOUNCE] 3.8.10-rt6)

2013-05-03 Thread Sebastian Andrzej Siewior
On 04/30/2013 08:08 PM, Steven Rostedt wrote: >> This NMI releated deadlock is a problem which should also trigger >> mainline, right? > > Well, yeah, as sending out a NMI stack dump is sorta the last resort, > and is dangerous to do printks from NMI context. So we did bad and we upgrade to bad a

Re: Suspend resume problem (WAS Re: [ANNOUNCE] 3.8.10-rt6)

2013-05-02 Thread Sebastian Andrzej Siewior
On 05/01/2013 12:31 AM, Borislav Petkov wrote: > Didn't tlgx fix a similar issue upstream already? > > 77c675ba18836. He did as it seems. Sebastian -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info

Re: Suspend resume problem (WAS Re: [ANNOUNCE] 3.8.10-rt6)

2013-04-30 Thread Borislav Petkov
On Tue, Apr 30, 2013 at 07:09:48PM +0200, Sebastian Andrzej Siewior wrote: > Now, the time jump on the other hand is the real issue here and is > RT-only. It looks like we get a big number of timer updates via > tick_do_update_jiffies64() because according to ktime_get() that much > time really pas

Re: Suspend resume problem (WAS Re: [ANNOUNCE] 3.8.10-rt6)

2013-04-30 Thread Clark Williams
On Tue, 30 Apr 2013 14:18:24 -0500 Clark Williams wrote: > On Tue, 30 Apr 2013 19:09:48 +0200 > Sebastian Andrzej Siewior wrote: > > > * Clark Williams | 2013-04-29 16:19:25 [-0500]: > > > > >On Mon, 29 Apr 2013 22:12:02 +0200 > > >Sebastian Andrzej Siewior wrote: > > >> - suspend / resum

Re: Suspend resume problem (WAS Re: [ANNOUNCE] 3.8.10-rt6)

2013-04-30 Thread Clark Williams
On Tue, 30 Apr 2013 19:09:48 +0200 Sebastian Andrzej Siewior wrote: > * Clark Williams | 2013-04-29 16:19:25 [-0500]: > > >On Mon, 29 Apr 2013 22:12:02 +0200 > >Sebastian Andrzej Siewior wrote: > >> - suspend / resume seems to program program the timer wrong and wait > >> ages until i

Re: Suspend resume problem (WAS Re: [ANNOUNCE] 3.8.10-rt6)

2013-04-30 Thread Steven Rostedt
On Tue, 2013-04-30 at 19:09 +0200, Sebastian Andrzej Siewior wrote: > The next thing that happens is that RCU assumes nobody is doing any > progress (for almost 28secs) and triggers NMIs & printks to get some > attention. I have a trace where > - CPU0: arch_trigger_all_cpu_backtrace_handler() => p

Suspend resume problem (WAS Re: [ANNOUNCE] 3.8.10-rt6)

2013-04-30 Thread Sebastian Andrzej Siewior
* Clark Williams | 2013-04-29 16:19:25 [-0500]: >On Mon, 29 Apr 2013 22:12:02 +0200 >Sebastian Andrzej Siewior wrote: >> - suspend / resume seems to program program the timer wrong and wait >> ages until it continues. > >It has to be something we're doing when we apply RT to v3.8.x, sin