Kernel Panic in MX-21.3_fluxbox_x64 Wildflower September 18, 2022
antiX / MX LinuxThis forum is for the discussion of antiX and MX 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.
Kernel Panic in MX-21.3_fluxbox_x64 Wildflower September 18, 2022
I am experiencing random kernel panic incidences.
In the past I had already experienced kernel panics when connecting my bluetooth headphones, since I stopped using bluetooth my computer worked fine for 1 year, but now they came back (without using bluetooth).
I don't know if it is due to a bad driver of my Wi-Fi or if it is due to an update of some software that I use.
I notice that if I use PaleMoon I don't experience kernel panics, but if I use browsers like Brave, Firefox, Chrome I do. I'm not 100% sure about PaleMoon yet. I've experience kernel panic using telegram desktop too.
I have no idea what might be causing this.
Could it have to do with how old my cpu (Intel(R) Celeron(R) CPU N2806 @ 1.60GHz) is?
To be honest. Failing to load bluetooth firmware should not cause a kernel panic. In fact. As many times as I have broke a system. like my motorcycle shop computer which the heat turned the sata connector
into dry breadcrumbs. Never got a kernel panic. Received a no signal on monitor instead.
Can you explain the symptoms of your kernel panic or have a screenshot on what is going on?
Looking at your dmesg output at pastebin. Sure have a lot ram entries. Maybe a bad ram stick?
Quote:
Causes of kernel panic
Kernel panic can be triggered by an inappropriate attempt by the OS to access or write to memory, and can also be caused by software bugs or malware. Other common causes of a kernel panic include:
a bug in the kernel (i.e., in a driver that is part of the kernel);
failure or improper installation of random access memory (RAM) chips;
hard disk damage or data corruption;
defective or corrupted system file, processor or memory;
unsupported hardware;
It might pay to run a live usb session and unmount you internal partition in there and right click and pick check.
Slow processors & big web browsers don't mix very well.
You don't say how much ram you have, but you really need at least 2GB ram with a swap partiton of 2GB also, to run todays mainline web browsers.
You could try using Dillo, it won't work on all web sites, but it is lightweight.
I've 4GB of RAM with a swap partition of 5.6GB. I'll try Dillo thanks.
Quote:
Originally Posted by rokytnji
Can you explain the symptoms of your kernel panic or have a screenshot on what is going on?
My whole system/screen freezes forever and I cannot turn on/off the caps lock led so I assume it's a kernel panic because I tried using Magic SysRq key (REISUB) and it doesn't work either, it's completely dead.
I had a similar problem on another computer when I plugged in the RJ-45 ethernet cable my system/screen would freeze forever (kernel panic), later found out it was because the network card of my motherboard was shutting down out of the blue and I had to install a BIOS patch to get the card to work. I never had a kernel panic on that PC again, I installed one of these BIOS patches: https://www.asrock.com/mb/nvidia/n68-vs3%20fx/#BIOS
The laptop i'm using now also had BIOS problems recognizing peripherals like usb keyboard and mouse so i reinstalled the BIOS too using a programmer clamp and it worked fine for a long time (3 years) except when I use bluetooth which gives me a kernel panic.
I don't have hardware acceleration activated in palemoon and I noticed that when I use palemoon I experience small freezes here and there (only in the browser, my whole system is not freeze or laggy only PaleMoon is, this is not a kernel panic) but when I use the other browsers like Brave, Chrome, Firefox I never experience small freezes in the browser but the whole system is laggy, those BIG browsers use all my resources PaleMoon does not. So far if I just use PaleMoon I don't experience a kernel panic.
Sorry, english is not my first language, spanish is, this is the best way i could explain the problem.
Quote:
Originally Posted by rokytnji
It might pay to run a live usb session and unmount you internal partition in there and right click and pick check.
Failing ram maybe with your dmesg readouts. You user.log is not there by the way.
I had the same problem on this Intel NUC box. I had a failing ssd drive. After putting in new 120 gig ssd drive. No more freeze ups.
You have enough ram to run firefox. It is freezing because of some failing hardware.
Or
Quote:
later found out it was because the network card of my motherboard was shutting down out of the blue and I had to install a BIOS patch to get the card to work. I never had a kernel panic on that PC again, I installed one of these BIOS patches:
FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Jul 18 22:17:50 atavisticblackdisorder kernel: [ 239.426855] mei_txe 0000:00:1a.0: init hw failure.
Jul 18 22:17:50 atavisticblackdisorder kernel: [ 239.433135] mei_txe 0000:00:1a.0: initialization failed.
Looking through your report I'd start with checking hard drive. Easy way for me is to use a live usb MX with gparted in it to unmount and run a check on file system for partitions. Mouse clicks mostly. Don't know what you mean too much about playing with arduino board.
I have a PI but it is too low spec to be of much use. Learned it was cheaper and easier to use a Chrome Box or Intel NUC for cheaper.
At least that is how it is in my area.
FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Jul 18 22:17:50 atavisticblackdisorder kernel: [ 239.426855] mei_txe 0000:00:1a.0: init hw failure.
Jul 18 22:17:50 atavisticblackdisorder kernel: [ 239.433135] mei_txe 0000:00:1a.0: initialization failed.
Looking through your report I'd start with checking hard drive. Easy way for me is to use a live usb MX with gparted in it to unmount and run a check on file system for partitions. Mouse clicks mostly. Don't know what you mean too much about playing with arduino board.
I have a PI but it is too low spec to be of much use. Learned it was cheaper and easier to use a Chrome Box or Intel NUC for cheaper.
At least that is how it is in my area.
Thanks for your answer, but I don't think it's the hdd because before I had a good hdd and I still were having freeze ups when using bluetooth, my hard drive got damaged by these freeze-ups and I replaced the hdd with an old used one. The MX-Linux installer automatically runs gsmartcontrol and it always reported that my disk was damaged but since I stop using bluetooth I didn't experience freeze ups for 1 year till now. So I'm not sure, maybe it's the ram.
I'm gonna try re-installing MX-Linux on a SSD but I don't think it will solve the problem.
Last edited by atavisticdisorder; 07-24-2023 at 10:00 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
