D&C GLug - Home Page

[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]

Re: [LUG] bad: scheduling from the idle thread

 

Top shows all 4 cores getting on with stuff.Â

It is occurring frequently

[60728.096992] CPU: 1 PID: 0 Comm: swapper/1 Tainted: PÂÂÂÂÂÂÂÂÂÂ OEÂÂ 4.5.0-0.bpo.2-amd64 #1 Debian 4.5.3-2~bpo8+1
[60728.096994] Hardware name: Gigabyte Technology Co., Ltd. P67-DS3-B3/P67-DS3-B3, BIOS F1 05/06/2011
[60728.096996]Â 0000000000000286 eaa939fa29b2d8ea ffffffff8130a125 ffff88042f455e00
[60728.097000]Â ffff88041ce98f40 ffffffff810a899a ffff88042f455e00 ffffffff815b606d
[60728.097002]Â ffffffff81ac24c0 ffff88041cea0000 ffffe8ffffc48fd0 ffffffff81ac24c0
[60728.097005] Call Trace:
[60728.097009]Â [<ffffffff8130a125>] ? dump_stack+0x5c/0x77
[60728.097012]Â [<ffffffff810a899a>] ? dequeue_task_idle+0x2a/0x40
[60728.097014]Â [<ffffffff815b606d>] ? __schedule+0x52d/0x960
[60728.097016]Â [<ffffffff815b64d1>] ? schedule+0x31/0x80
[60728.097018]Â [<ffffffff815b675a>] ? schedule_preempt_disabled+0xa/0x10
[60728.097021]Â [<ffffffff810b9b66>] ? cpu_startup_entry+0x1b6/0x380
[60728.097024]Â [<ffffffff8104d7ca>] ? start_secondary+0x15a/0x1a0
[60728.099348] bad: scheduling from the idle thread!
[60728.099353] CPU: 1 PID: 0 Comm: swapper/1 Tainted: PÂÂÂÂÂÂÂÂÂÂ OEÂÂ 4.5.0-0.bpo.2-amd64 #1 Debian 4.5.3-2~bpo8+1
[60728.099355] Hardware name: Gigabyte Technology Co., Ltd. P67-DS3-B3/P67-DS3-B3, BIOS F1 05/06/2011
[60728.099357]Â 0000000000000286 eaa939fa29b2d8ea ffffffff8130a125 ffff88042f455e00
[60728.099360]Â ffff88041ce98f40 ffffffff810a899a ffff88042f455e00 ffffffff815b606d
[60728.099363]Â 0000000000000004 ffff88041cea0000 ffffe8ffffc48fd0 ffffffff81ac24c0
[60728.099365] Call Trace:
[60728.099369]Â [<ffffffff8130a125>] ? dump_stack+0x5c/0x77
[60728.099372]Â [<ffffffff810a899a>] ? dequeue_task_idle+0x2a/0x40
[60728.099374]Â [<ffffffff815b606d>] ? __schedule+0x52d/0x960
[60728.099377]Â [<ffffffff815b64d1>] ? schedule+0x31/0x80
[60728.099379]Â [<ffffffff815b675a>] ? schedule_preempt_disabled+0xa/0x10
[60728.099382]Â [<ffffffff810b9b66>] ? cpu_startup_entry+0x1b6/0x380
[60728.099384]Â [<ffffffff8104d7ca>] ? start_secondary+0x15a/0x1a0
[60728.101821] bad: scheduling from the idle thread!
[60728.101827] CPU: 1 PID: 0 Comm: swapper/1 Tainted: PÂÂÂÂÂÂÂÂÂÂ OEÂÂ 4.5.0-0.bpo.2-amd64 #1 Debian 4.5.3-2~bpo8+1
[60728.101829] Hardware name: Gigabyte Technology Co., Ltd. P67-DS3-B3/P67-DS3-B3, BIOS F1 05/06/2011
[60728.101830]Â 0000000000000286 eaa939fa29b2d8ea ffffffff8130a125 ffff88042f455e00
[60728.101834]Â ffff88041ce98f40 ffffffff810a899a ffff88042f455e00 ffffffff815b606d
[60728.101836]Â ffffffff81ac24c0 ffff88041cea0000 ffffe8ffffc48fd0 ffffffff81ac24c0
[60728.101839] Call Trace:
[60728.101842]Â [<ffffffff8130a125>] ? dump_stack+0x5c/0x77
[60728.101845]Â [<ffffffff810a899a>] ? dequeue_task_idle+0x2a/0x40
[60728.101848]Â [<ffffffff815b606d>] ? __schedule+0x52d/0x960
[60728.101850]Â [<ffffffff815b64d1>] ? schedule+0x31/0x80
[60728.101852]Â [<ffffffff815b675a>] ? schedule_preempt_disabled+0xa/0x10
[60728.101855]Â [<ffffffff810b9b66>] ? cpu_startup_entry+0x1b6/0x380
[60728.101857]Â [<ffffffff8104d7ca>] ? start_secondary+0x15a/0x1a0
root@Lyrae:/home/akm#



Kernel symbols coming up/down


On Fri, 17 Jun 2016 at 15:24 Robin Cornelius <robin.cornelius@xxxxxxxxx> wrote:
I've had a quick look and i'm confused already.

start_secondary() is the entry point to start up the non boot CPU on
SMP systems, and i can't see where cpu_startup_entry() manages to call
schedule_preempt_disabled() its probably inline code somewhere as that
is part of a mutex locking operation. I can't see directly a driver
involved.

So this looks like a kernel issue for SMP systems? Which begs the
question why are you getting this multiple times, this is a CPU
startup function? Any clever power management that can sleep
CPUs/cores and this is wake up related?

You could try installing the full kernel symbols package, it may give
a slightly better stack trace

On 17 June 2016 at 14:45, Adrian Midgley <amidgley@xxxxxxxxx> wrote:
> Kernel, or a driver for something, if so how should I approach identifying
> the culprit, please?
>
> I've had a few sudden halts, associated with moving the edge of a frame of
> eg Iceweasel --> Firefox-esr or Gimp in the Gnome desktop with the (USB)
> mouse.
> I think they are less with the current version of NVidia's proprietary
> driver controlling the 4-headed video card and four monitors you may recall
> me mentioning earlier.
>
> (BTW, if anyone wants a couple of 2-headed NVidia cards which are very nice
> but don't go up to the largest resolutions with DVI, a very small token
> would secure them.)
>
> On Fri, 17 Jun 2016 at 14:41 Robin Cornelius <robin.cornelius@xxxxxxxxx>
> wrote:
>>
>> Driver bug, Its a warning that the kernel driver is attempting to
>> sleep in the idle thread (which should be non blocking code only) and
>> not try to sleep etc.
>>
>> It is only a warning so is non fatal but i guessing its a ripe way to
>> a deadlock situation with the idle thread stalled waiting for
>> something else to occur.
>>
>>
>>
>> On 17 June 2016 at 13:30, Simon Waters <simon@xxxxxxxxxxxxxx> wrote:
>> > If it works worry a little, if it breaks worry a lot.
>> >
>> > I'd probably try a newer kernel package, or an older one, first. See if
>> > it persists, ilunless you know what triggers it.
>> >
>> > --
>> > The Mailing List for the Devon & Cornwall LUG
>> > https://mailman.dclug.org.uk/listinfo/list
>> > FAQ: http://www.dcglug.org.uk/listfaq
>>
>> --
>> The Mailing List for the Devon & Cornwall LUG
>> https://mailman.dclug.org.uk/listinfo/list
>> FAQ: http://www.dcglug.org.uk/listfaq
>
>
> --
> The Mailing List for the Devon & Cornwall LUG
> https://mailman.dclug.org.uk/listinfo/list
> FAQ: http://www.dcglug.org.uk/listfaq
>

--
The Mailing List for the Devon & Cornwall LUG
https://mailman.dclug.org.uk/listinfo/list
FAQ: http://www.dcglug.org.uk/listfaq
-- 
The Mailing List for the Devon & Cornwall LUG
https://mailman.dclug.org.uk/listinfo/list
FAQ: http://www.dcglug.org.uk/listfaq