BOOT_IMAGE crashed message and occasional *possibly unrelated crashes?*
by 6th_sense from LinuxQuestions.org on (#4V3R3)
Machine I'm running:
I am currently running Fedora 30 on a recently purchased Laptop:
Machine: Lenovo
Model: P53s
HD: 1TB SSD
RAM: 24GB (8GB onboard)
Video: Nvidia Quadro P520 w/2GB memory GDDR5 64Bit
OS: Fedora 30 with Nvidia drivers installed.
Problem:
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:
https://www.linuxquestions.org/quest...54#post5453154
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.
Code:...
[ +0.001980] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
...Questions:
What do you think is the cause of the problem/problems I am facing.
Do you think the crashes are related to the messages shown in the code sections above?
What should I resort to trying?
Is there any other information that might be relevant to a search for answers, that I should chase down?
I am currently running Fedora 30 on a recently purchased Laptop:
Machine: Lenovo
Model: P53s
HD: 1TB SSD
RAM: 24GB (8GB onboard)
Video: Nvidia Quadro P520 w/2GB memory GDDR5 64Bit
OS: Fedora 30 with Nvidia drivers installed.
Problem:
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:
https://www.linuxquestions.org/quest...54#post5453154
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.
Code:...
[ +0.001980] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
...Questions:
What do you think is the cause of the problem/problems I am facing.
Do you think the crashes are related to the messages shown in the code sections above?
What should I resort to trying?
Is there any other information that might be relevant to a search for answers, that I should chase down?