Mailing List Archive: kernel bad scheduling from idle thread

kernel bad scheduling from idle thread

Oct 13, 2020, 12:26 AM

Post #1 of 4 (409 views)

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.

--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?

John Covici wb2una
covici@ccs.covici.com

Re: kernel bad scheduling from idle thread [ In reply to ]

joost at antarean

Oct 13, 2020, 12:39 AM

Post #2 of 4 (409 views)

Permalink

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

Re: kernel bad scheduling from idle thread [ In reply to ]

covici at ccs

Oct 13, 2020, 1:08 AM

Post #3 of 4 (409 views)

Permalink

On Tue, 13 Oct 2020 03:39:48 -0400,
J. Roeleveld wrote:
>
> 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.
>

This is the first 5.4 kernel I have tried. I did a make oldconfig and
added a number of modules, but I would think the kernel would only
load the ones that are needed. I could not tell you the exact ones,
as I try to make the kernel somewhat general, so I may add things
which may not be necessary for my particular situation.

--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?

John Covici wb2una
covici@ccs.covici.com

Re: kernel bad scheduling from idle thread [ In reply to ]

adamcarter3 at gmail

Oct 15, 2020, 2:29 AM

Post #4 of 4 (409 views)

Permalink

>
> This is the first 5.4 kernel I have tried. I did a make oldconfig and
> added a number of modules, but I would think the kernel would only
> load the ones that are needed. I could not tell you the exact ones,
> as I try to make the kernel somewhat general, so I may add things
> which may not be necessary for my particular situation.
>

I think call traces indicate a kernel bug, not an issue with kernel
configuration. Try .71 - perhaps the issue has already been fixed.

If the issue persists in .71 then you could report to the kernel
maintainers if you have the time and inclination. I've reported a couple.
https://www.kernel.org/doc/html/latest/admin-guide/reporting-bugs.html -
just dont use gmail as they want plain text email.