Bug 666472 – sys-kernel/gentoo-sources-4.18.6 ..4.18.8 Kernel panic - not syncing: Attempted to kill init! exit code=0x00000007

• Product: Gentoo Linux
• Status: RESOLVED OBSOLETE

[Description Andrew 2018-09-18 15:28:09 UTC]

There is an error "kernel panic" when moving to the kernel 4.18.6 and above. Kernel "4.17.10" works stably. On another machine, the kernel 4.18.6 is stable. Perhaps the problem is in incompatibility between the kernel and the processor. Previously, there was no such error.

Reproducible: Always

Steps to Reproduce:
1. Install package gentoo-sources-4.18.6 and above.
2  The new kernel is configured with the command "make oldconfig"
3. Build and install new kernel
4. Boot the system with a new kernel



In the error log "kernel panic" there are lines:

--------------------------------------------------------------------------
Kernel panic - not syncing: Attempted to kill init! exit code=0x00000007
sched: Unexpected reschedule of offline CPU#0
--------------------------------------------------------------------------

Disabling the "CONFIG_SCHED_SMT" and "CONFIG_SCHED_MC" options in the kernel does not solve the problem.

[Comment 1 Andrew 2018-09-18 15:32:55 UTC]

Created attachment 547154 [details]
Config of kernel 4.18.6

[Comment 2 Andrew 2018-09-18 15:33:58 UTC]

Created attachment 547156 [details]
Output of command "emerge --info"

[Comment 3 Andrew 2018-09-18 15:35:18 UTC]

Created attachment 547158 [details]
Content of file /proc/cpuinfo

[Comment 4 Jonas Stein 2018-09-19 08:33:16 UTC]

Why do you think this is a bug on gentoo and not in the kernel (upstream)?

[Comment 5 Andrew 2018-09-19 12:03:50 UTC]

I installed the kernel using the package "sys-kernel/gentoo-sources-4.18.6", not the image from the site "https://www.kernel.org/". I agree with  Jonas Stein that most likely is a kernel bug

[Comment 6 Andrew 2018-09-19 13:33:55 UTC]

With the kernel 4.17.19 from the sys-kernel/gentoo-sources-4.17.19 package everything works without errors. The error is most likely in the kernel version 4.18

[Comment 7 Mike Pagano 2018-11-08 18:38:36 UTC]

Hi, Andrew.

Can you test 4.18.17?  If that fails, would you be willing to do a git bisect between the latest working on and the failing kernel?

[Comment 8 Andrew 2018-11-09 09:20:23 UTC]

I have already switched to kernel 4.19. Everything works without errors. Problem solved

[Comment 9 Mike Pagano 2018-11-09 15:23:14 UTC]

Good news