[SOLVED] Not all CPUs entered broadcast exception handler (Kernel panic)
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Not all CPUs entered broadcast exception handler (Kernel panic)
Strange behavior during installation of Slackware current (19.01.20)
on Lenovo C260 monoblock (Celeron J1850, 4 cores):
Kernel panic - .. Not all CPUs entered broadcast exception handler.
After disabling Core multiprocessing in BIOS kernel does load but
keyboard behaves awfully - response delayed, enters multiple symbols etc.
impossible to use keyboard.
For 14.2 kernel loads but keyboard behaves identically.
The installed Suse 13.1 loads and works normally, keyboard too ...
Can't remember Slackware ever having such problems at installation.
I'd love to know why that works. What was going wrong?
I did not read the entire thread i posted ( it is 100+ posts), but I understand it is an incompatibility issue between some Intel CPUs and Glibc?
It seems it can be solved with a bios or UEFI update for specific vendors but the thread is too chaotic to follow.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.