BOOT_IMAGE crashed message and occasional *possibly unrelated crashes?*
FedoraThis forum is for the discussion of the Fedora Project.
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.
I get a message saying the following, every time I login to the KDE desktop:
Code:
Oops!
We're sorry, it looks like BOOT_IMAGE=(hd0,gpt3)/
vmlinuz-5.3.8-2000.fc30.x86_64 crashed. Please contact the developer if you want to report the issue.
and this disappears within 10-15 seconds, without any problems occuring... except the occasional crash of the machine where I am not able to ping the machine, and I am unable to use any of the keys on the keyboard, and I am unable to ssh to the machine. There is no particular timeline on which this occurs. It could occur after 1 hour of uptime or 5 minutes of uptime.
Immediate Reaction:
My only recourse, after having tried ping and ssh, is to hard reset the machine (holding power button).
Other similar threads:
Unfortunately, this is similar to a question posted for Fedora 23, but, I am not sure it is relevant in this case and the link is below:
It talks about re-creating initrd - which I believe since migrated to initramfs (correct me if I'm wrong) and apparently this is created on the fly with the newer versions of fedora (I have fedora 30 running).
What I have tried:
I have used the abrt tool - It gives me such a long laundry list of problems - including ones that predated the install of Nvidia drivers for the machine.
The output of the following command is possibly relevant:
# abrt info -c kernel --pretty full |less
Code:
Id da6d80c
Component kernel
Count 1
Time 2019-11-11 15:34:01
Command line BOOT_IMAGE=(hd0,gpt3)/vmlinuz-5.3.8-200.fc30.x86_64 root=/dev/mapper/vg_q--trak-lv_root ro resume=/dev/mapper/vg_q--trak-lv_swap rd.lvm.lv=vg_q-trak/lv_root rd.lvm.lv=vg_q-trak/lv_swap rhgb quiet rd.driver.blacklist=nouveau
Package kernel-core-5.3.8-200.fc30
Path /var/spool/abrt/oops-2019-11-11-15:34:01-1110-0
Not reportable
The backtrace does not contain enough meaningful function frames to be reported. It is annoying but it does not necessary signalize a problem with your computer. ABRT will not allow you to create a report in a bug tracking system but you can contact kernel maintainers via e-mail.
The other entries in the abort list look pretty much the same as this one - the note is "Not reportable" and the message that follows is the same.
One entry that differed looks as follows:
Code:
Id eb21e2c
Component kernel
Count 2
Time 2019-11-04 11:14:57
Command line BOOT_IMAGE=(hd0,gpt3)/vmlinuz-5.3.7-200.fc30.x86_64 root=/dev/mapper/vg_q--trak-lv_
root ro resume=/dev/mapper/vg_q--trak-lv_swap rd.lvm.lv=vg_q-trak/lv_root rd.lvm.lv=vg_q-trak/lv_
swap rhgb quiet
Package kernel-core-5.3.7-200.fc30
Path /var/spool/abrt/oops-2019-11-04-11:14:57-1059-0
Not reportable
A kernel problem occurred, but your kernel has been tainted (flags:GW). Explanation:
W - Taint on warning.
Kernel maintainers are unable to diagnose tainted reports.
Not sure that this is of any greater use than the previous one.
I also ran:
Looked at stack trace "dmesg -H": (found the one line that may indicate an error). All the other lines seem to be ok.
I don't know with which tool KDE reports errors and where they are logged. Perhaps you can find out. In any case, this doesn't look like a kernel problem. It rather seems that some KDE configuration file contains the string "BOOT_IMAGE=(hd0,gpt3)/vmlinuz-5.3.8-2000.fc30.x86_64", which KDE tries to execute and fails.
Not knowing anything about KDE, I would perform a brute-force search for that string over all text documents on the PC. Or again, find out where KDE config and log files might be located and check them.
Distribution: Centos 7.x, Fedora (one version behind latest)
Posts: 141
Original Poster
Rep:
Hi berndbausch,
It appears in a popup dialog box (nothing but an X in a circle in the right hand side).
I am under the impression that it isn't a KDE issue - boot image suggests something to do with the booting of the system... Just that it manages to send an error to KDE - or it is possible that some interaction with KDE causes it to pop up.
boot image suggests something to do with the booting of the system...
Errors related to booting should either halt the system, or cause messages to appear in the message buffer. However you haven't found anything remotely related in the message buffer.
Code:
it looks like BOOT_IMAGE=(hd0,gpt3)/
vmlinuz-5.3.8-2000.fc30.x86_64 crashed
To me, this message means: A program named BOOT_IMAGE=(hd0,gpt3)/vmlinuz-5.3.8-2000.fc30.x86_64 crashed. Which makes me think that somewhere, KDE was erroneously configured to run a program with this name. My guess is that KDE pops up the error window because no such program exists.
My Fedora 30 and 31 has been doing that for the last few months. You can send data to the kernel dev's if you want.
Once the kernel has been marked tainted it seems to stay that way for a while. There is a lot of information about tainted kernels online and how to discover more about the module(s) doing it.
Looks like it might have come in with 5.3 - my old F30 system was still on 5.1, never saw the issue. Just updated and 5.3 came in, and so did the message. Also broke my wifi - dkms still builds ok, but the driver won't see my TP-Link dongle. Might have to go find a newer driver source.
Distribution: Centos 7.x, Fedora (one version behind latest)
Posts: 141
Original Poster
Rep:
Quote:
Originally Posted by berndbausch
Errors related to booting should either halt the system, or cause messages to appear in the message buffer. However you haven't found anything remotely related in the message buffer.
Code:
it looks like BOOT_IMAGE=(hd0,gpt3)/
vmlinuz-5.3.8-2000.fc30.x86_64 crashed
To me, this message means: A program named BOOT_IMAGE=(hd0,gpt3)/vmlinuz-5.3.8-2000.fc30.x86_64 crashed. Which makes me think that somewhere, KDE was erroneously configured to run a program with this name. My guess is that KDE pops up the error window because no such program exists.
You are possibly Partially Correct:
Perhaps you are right.... I'm not sure about the inexistent part though...
What this looks like:
This looks like something that isn't supposed to be still running to me - vmlinuz is the initial compressed kernel that is used in order to start the system... boot image is where it is supposed to be running from on the initrd (init ram disk), where this file is found - on hard disk 0 (hd0), with gpt3 (GUID Partition Table).
This looks like a line from grub configuration....
New Thoughts on this:
Not Sure Why a Line from Grub is getting put in a message...
I had to install the new drivers for my Nvidia card - this is the only departure from a standard installation that I can think of - this involves something getting compiled and installed - the compilation may have led to a branch that executes or attempts to execute something that is a grub line on the machine - perhaps I need to check the install shell that causes the automated compile.
Distribution: Centos 7.x, Fedora (one version behind latest)
Posts: 141
Original Poster
Rep:
Quote:
Originally Posted by syg00
Looks like it might have come in with 5.3 - my old F30 system was still on 5.1, never saw the issue. Just updated and 5.3 came in, and so did the message. Also broke my wifi - dkms still builds ok, but the driver won't see my TP-Link dongle. Might have to go find a newer driver source.
Thank you for sharing that!
Related:
I needed to use dkms as well! (for compiling the Nvidia drivers) Perhaps there is something there...
initramfs is the *new* initrd (initramdisk) - it would make sense that this part is involved in the compile - as the driver is needed for the initial startup phase of the system as well.
Distribution: Centos 7.x, Fedora (one version behind latest)
Posts: 141
Original Poster
Rep:
Quote:
Originally Posted by syg00
Looks like it might have come in with 5.3 - my old F30 system was still on 5.1, never saw the issue. Just updated and 5.3 came in, and so did the message. Also broke my wifi - dkms still builds ok, but the driver won't see my TP-Link dongle. Might have to go find a newer driver source.
This Makes Sense Now:
I didn't understand why you thought this was relevant... Now, I do.
Not sure why "Windows" is mentioned - as my machine is exclusively running on Linux at the moment.
Windows is still present in the BIOS and/or in an ESP partition. You can remove it from the BIOS using the efibootmgr command, but it may return if it remains on the ESP. It can be removed directly from BIOS too.
If it was mine, I'd cut down that list of entries. ISTR reading about some pretty flaky Lenovo UEFI BIOS behavior. Possibly Lenovo's BIOS gets overwhelmed by such a long list, and that passes through as corruption of the environment.
Try removing BOOT_IMAGE as a potential problem by removing it from the kernel cmdline at the Grub menu, and if it helps, strike it from /etc/default/grub as well.
I find it hard to imagine how BOOT_IMAGE or the kernel's filename could be connected to anything KDE-related. KDE doesn't care what kernel you are running.
NVidia GPUs don't necessarily require NVidia's tainting drivers. If nothing else solves the problem, try removing to narrow down the problem possibilities. The default FOSS driver works fine on F30 here, e.g. on a really old one currently booted:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
BOOT_IMAGE crashed message and occasional *possibly unrelated crashes?*
