On Tuesday, October 13, 2020 9:26:08 AM CEST John Covici wrote:
> Hi.  I am getting a very bad problem on my new kernel that I did after
> my last update.  It gave me the following sequence over and over for a
> while, and then stopped with the messages, but the system crashed.  I
> then went back to my old kernel which had been working for more than a
> month and got a couple of the same traces, but I hope its stopped, so
> I can write this message.  A google search finds nothing relevant.
> 
> Here is what I get:
> 
> Oct 13 02:34:40 ccs.covici.com kernel: bad: scheduling from the idle
> thread!
> Oct 13 02:34:40 ccs.covici.com kernel: CPU: 5 PID: 0 Comm: swapper/5
> Tainted: P        W  O      5.4.69-gentoo #1
> Oct 13 02:34:40 ccs.covici.com kernel: Hardware name: Supermicro Super
> Server/X11SCA-W, BIOS 1.2 12/05/2019
> Oct 13 02:34:40 ccs.covici.com kernel: Call Trace:
> Oct 13 02:34:40 ccs.covici.com kernel:  dump_stack+0x71/0x98
> Oct 13 02:34:40 ccs.covici.com kernel:  dequeue_task_idle+0x1f/0x28
> Oct 13 02:34:40 ccs.covici.com kernel:  __schedule+0x167/0x5d6
> Oct 13 02:34:40 ccs.covici.com kernel:  schedule_idle+0x2a/0x33
> Oct 13 02:34:40 ccs.covici.com kernel:  do_idle+0x1d0/0x1f2
> Oct 13 02:34:40 ccs.covici.com kernel:  cpu_startup_entry+0x1d/0x1f
> Oct 13 02:34:40 ccs.covici.com kernel:  start_secondary+0x17b/0x198
> Oct 13 02:34:40 ccs.covici.com kernel:  secondary_startup_64+0xa4/0xb0
> Oct 13 02:34:40 ccs.covici.com kernel: bad: scheduling from the idle
> thread!
> Oct 13 02:34:40 ccs.covici.com kernel: CPU: 5 PID: 0 Comm: swapper/5
> Tainted: P        W  O      5.4.69-gentoo #1
> Oct 13 02:34:40 ccs.covici.com kernel: Hardware name: Supermicro Super
> Server/X11SCA-W, BIOS 1.2 12/05/2019
> Oct 13 02:34:40 ccs.covici.com kernel: Call Trace:
> Oct 13 02:34:40 ccs.covici.com kernel:  dump_stack+0x71/0x98
> Oct 13 02:34:40 ccs.covici.com kernel:  dequeue_task_idle+0x1f/0x28
> Oct 13 02:34:40 ccs.covici.com kernel:  __schedule+0x167/0x5d6
> Oct 13 02:34:40 ccs.covici.com kernel:  schedule_idle+0x2a/0x33
> Oct 13 02:34:40 ccs.covici.com kernel:  do_idle+0x1d0/0x1f2
> Oct 13 02:34:40 ccs.covici.com kernel:  cpu_startup_entry+0x1d/0x1f
> Oct 13 02:34:40 ccs.covici.com kernel:  start_secondary+0x17b/0x198
> Oct 13 02:34:40 ccs.covici.com kernel:  secondary_startup_64+0xa4/0xb0
> 
> 
> How would I even be able to find out what is happening here?
> 
> Any thoughts appreciated.

Which kernel versions have you tried?
And which additional kernel modules have you added?

I myself am using 5.4.66 as previous versions were causing kernel panics.

--
Joost




Reply via email to