On Sat, 2014-12-27 at 11:20 +0000, Toni Mueller wrote:
[...]
> I am confused because the output is really not that much more verbose
> than the screnshots, but here you are:
>
>
> [ 22.224014] INFO: rcu_sched self-detected stall on CPU { 1} (t=5251 jiffies g=-153 c=-154 q=307)
What happened to the first 22 seconds of the log?
> [ 22.232010] INFO: rcu_sched detected stalls on CPUs/tasks: { 1} (detected by 0, t=5252 jiffies, g=-153, c=-154, q=307)
> [ 22.232010] CPU: 0 PID: 122 Comm: systemd-udevd Not tainted 3.16.0-0.bpo.4-686-pae #1 Debian 3.16.7-ckt2-1~bpo70+1
> [ 22.232010] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
> [ 22.232010] task: f6c96560 ti: f6cd6000 task.ti: f6cd6000
> [ 22.232010] Stack:
> [ 22.232010] Call Trace:
[...]
I don't understand why the stack information is not printed here.
Please add 'debug' to the kernel command line; that should force it to
really log everything.
Ben.
--
Ben Hutchings
It is easier to change the specification to fit the program than vice versa.
Attachment:
signature.asc
Description: This is a digitally signed message part