Also, please note in the trace for some strange reason, the floppy
drive activates after the rcu_sched errors happen -- fucking wierd
shit. I fixed the problem in the debugger patch but seems like to me
it should not generate a crash report when time is frozen for that
kernel instance just because
I coded a workaround and tested it. seems to work.
Jeff
On 10/26/15, Jeffrey Merkey wrote:
> I am calling these functions while polling the keyboard inside the
> debugger:
>
> touch_softlockup_watchdog();
> clocksource_touch_watchdog();
> touch_nmi_watchdog();
>
> Jeff
>
> On 10/25/15, Jeffrey
I am calling these functions while polling the keyboard inside the debugger:
touch_softlockup_watchdog();
clocksource_touch_watchdog();
touch_nmi_watchdog();
Jeff
On 10/25/15, Jeffrey Merkey wrote:
> After using the mdb kernel debugger then exiting, the rcu_sched, due
> to its own internal time
After using the mdb kernel debugger then exiting, the rcu_sched, due
to its own internal timers, rolls over and crashes when it does not
get the timeout window it likes.Not caused by memory corruption,
just caused by the debugger holding the system suspended then when the
system is allowed to r
4 matches
Mail list logo
