| 1 |
On Tuesday, October 13, 2020 9:26:08 AM CEST John Covici wrote: |
| 2 |
> Hi. I am getting a very bad problem on my new kernel that I did after |
| 3 |
> my last update. It gave me the following sequence over and over for a |
| 4 |
> while, and then stopped with the messages, but the system crashed. I |
| 5 |
> then went back to my old kernel which had been working for more than a |
| 6 |
> month and got a couple of the same traces, but I hope its stopped, so |
| 7 |
> I can write this message. A google search finds nothing relevant. |
| 8 |
> |
| 9 |
> Here is what I get: |
| 10 |
> |
| 11 |
> Oct 13 02:34:40 ccs.covici.com kernel: bad: scheduling from the idle |
| 12 |
> thread! |
| 13 |
> Oct 13 02:34:40 ccs.covici.com kernel: CPU: 5 PID: 0 Comm: swapper/5 |
| 14 |
> Tainted: P W O 5.4.69-gentoo #1 |
| 15 |
> Oct 13 02:34:40 ccs.covici.com kernel: Hardware name: Supermicro Super |
| 16 |
> Server/X11SCA-W, BIOS 1.2 12/05/2019 |
| 17 |
> Oct 13 02:34:40 ccs.covici.com kernel: Call Trace: |
| 18 |
> Oct 13 02:34:40 ccs.covici.com kernel: dump_stack+0x71/0x98 |
| 19 |
> Oct 13 02:34:40 ccs.covici.com kernel: dequeue_task_idle+0x1f/0x28 |
| 20 |
> Oct 13 02:34:40 ccs.covici.com kernel: __schedule+0x167/0x5d6 |
| 21 |
> Oct 13 02:34:40 ccs.covici.com kernel: schedule_idle+0x2a/0x33 |
| 22 |
> Oct 13 02:34:40 ccs.covici.com kernel: do_idle+0x1d0/0x1f2 |
| 23 |
> Oct 13 02:34:40 ccs.covici.com kernel: cpu_startup_entry+0x1d/0x1f |
| 24 |
> Oct 13 02:34:40 ccs.covici.com kernel: start_secondary+0x17b/0x198 |
| 25 |
> Oct 13 02:34:40 ccs.covici.com kernel: secondary_startup_64+0xa4/0xb0 |
| 26 |
> Oct 13 02:34:40 ccs.covici.com kernel: bad: scheduling from the idle |
| 27 |
> thread! |
| 28 |
> Oct 13 02:34:40 ccs.covici.com kernel: CPU: 5 PID: 0 Comm: swapper/5 |
| 29 |
> Tainted: P W O 5.4.69-gentoo #1 |
| 30 |
> Oct 13 02:34:40 ccs.covici.com kernel: Hardware name: Supermicro Super |
| 31 |
> Server/X11SCA-W, BIOS 1.2 12/05/2019 |
| 32 |
> Oct 13 02:34:40 ccs.covici.com kernel: Call Trace: |
| 33 |
> Oct 13 02:34:40 ccs.covici.com kernel: dump_stack+0x71/0x98 |
| 34 |
> Oct 13 02:34:40 ccs.covici.com kernel: dequeue_task_idle+0x1f/0x28 |
| 35 |
> Oct 13 02:34:40 ccs.covici.com kernel: __schedule+0x167/0x5d6 |
| 36 |
> Oct 13 02:34:40 ccs.covici.com kernel: schedule_idle+0x2a/0x33 |
| 37 |
> Oct 13 02:34:40 ccs.covici.com kernel: do_idle+0x1d0/0x1f2 |
| 38 |
> Oct 13 02:34:40 ccs.covici.com kernel: cpu_startup_entry+0x1d/0x1f |
| 39 |
> Oct 13 02:34:40 ccs.covici.com kernel: start_secondary+0x17b/0x198 |
| 40 |
> Oct 13 02:34:40 ccs.covici.com kernel: secondary_startup_64+0xa4/0xb0 |
| 41 |
> |
| 42 |
> |
| 43 |
> How would I even be able to find out what is happening here? |
| 44 |
> |
| 45 |
> Any thoughts appreciated. |
| 46 |
|
| 47 |
Which kernel versions have you tried? |
| 48 |
And which additional kernel modules have you added? |
| 49 |
|
| 50 |
I myself am using 5.4.66 as previous versions were causing kernel panics. |
| 51 |
|
| 52 |
-- |
| 53 |
Joost |
Archives