Bug 198091 - hardlock on cold boot or warm boot on slackware-current with kernel-4.14.x
Summary: hardlock on cold boot or warm boot on slackware-current with kernel-4.14.x
Status: NEW
Alias: None
Product: Other
Classification: Unclassified
Component: Bug Tracker (show other bugs)
Hardware: Intel Linux
: P1 blocking
Assignee: Bug Me Administrator
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-12-06 06:07 UTC by nobodino
Modified: 2021-07-04 09:00 UTC (History)
2 users (show)

See Also:
Kernel Version: 4.14.4 and all kernel-4.14 series
Subsystem:
Regression: No
Bisected commit-id:

Attachments
kernel-4.14.4 segfault (2.82 MB, image/jpeg)
2017-12-06 07:21 UTC, nobodino 		Details
Add an attachment (proposed patch, testcase, etc.)

Description nobodino 2017-12-06 06:07:19 UTC 
Each time I upgrade kernel on slackware-current with kernel-4.14.x, generally the system segfaults on the first reboot.
After that, sometimes, it boots normally on second reboot, but there is no rule and no reproducibility on the process: see the reason why slackware-current moved back to kernel-4.9.x series which stable.
see  the thread on slackware linuxquestions forum:
https://www.linuxquestions.org/questions/slackware-14/strange-behavior-with-kernel-4-14-x-4175618207/
Comment 1 nobodino 2017-12-06 06:16:03 UTC 
it happens especially on 32-bit systems.
Comment 2 nobodino 2017-12-06 06:36:19 UTC 
BUG: unable to handle kernel paging request at 9b6bf61
IP: kmem_cache_alloc+0xa3/0x1f0
Comment 3 nobodino 2017-12-06 07:21:01 UTC 
Created attachment 261035 [details]
kernel-4.14.4 segfault
Comment 4 Drei Eck 2021-07-04 09:00:37 UTC 
You reported this at the place where bugs for the bug tracker itself should be reported.

I assume that noone applicable will look at your bug here.

Consider deleting/ closing it here and reporting it at the correct place.



For this reasons, I suggest to close this report here.
Note You need to log in before you can comment on or make changes to this bug.