Ask Your Question

Non-reportable kernel oops on boot

asked 2018-08-25 08:02:44 -0500

I have a fresh install of Fedora 28 with KDE on a Dell Latitude E7240 laptop. Often but not every time I boot, I get an error message saying that "BOOTIMAGE=/vmlinuz4.17.17-200.fc28.x86_64 crashed." Clicking on this notification tells me that the problem can't be reported, but that it was a kernel oops. What should I do about this?

Here's what's in the error window:

reason: traps: QThread[2096] trap invalid opcode ip:7ff48dd65ee0 sp:7ff467d91758 error:0 in[7ff48da3c000+4cd000]

backtrace: traps: QThread[2096] trap invalid opcode ip:7ff48dd65ee0 sp:7ff467d91758 error:0 in[7ff48da3c000+4cd000]

cmdline: BOOT_IMAGE=/vmlinuz-4.17.17-200.fc28.x86_64 root=/dev/mapper/fedora-root ro resume=/dev/mapper/fedora-swap rd.luks.uuid=luks-7a650bb5-bd69-4b73-966b-1877e007cc27 rd.luks.options=discard rhgb quiet

package: kernel-core-4.17.17-200.fc28

component: kernel

hostname: localhost.localdomain

count: 1

first_occurrence: 2018-08-25 15:07:55

last_occurrence: 2018-08-25 15:07:55

user: unknown user

type/analyzer: Kerneloops/abrt-oops

pkg_fingerprint: E08E 7E62 9DB6 2FB1

duphash: 913d3ca671c62c4a2304f3f1ea8bded67351e0c0

os_release: Fedora release 28 (Twenty Eight)

pkg_vendor: Fedora Project

abrt_version: 2.10.10

runlevel: N 5

architecture: x86_64

kernel: 4.17.17-200.fc28.x86_64

uuid: 913d3ca671c62c4a2304f3f1ea8bded67351e0c0

data_directory: /var/spool/abrt/oops-2018-08-25-15:07:55-1005-0
edit retag flag offensive close merge delete


You might want to report this in in the kernel component. The issue is more related to QT5 than the kernel - so I'd report that under the QT component.

lhirlimann gravatar imagelhirlimann ( 2018-08-26 02:20:23 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted

answered 2018-08-26 16:33:01 -0500

Wu gravatar image

Same here, same question. Mine is not fresh install, I've been regularly upgrading with dnf system-upgrade since Fedora 21 or 22, and this started since the latest kernel updates. What should we do about this?

I am not an GNU/Linux expert but from my experience these things and similar crashes after update happen once in every year or two. Can't even remember the last time something like this happened.

I guess, no worries and do nothing about it, and as usual enjoy the OS that works even after something like this crashes.

Check for updates with sudo dnf update --refresh regularly and within next few updates this will be fixed.

Edit: New kernels with the fix already came, while this post is still awaiting moderation.

edit flag offensive delete link more

Question Tools


Asked: 2018-08-25 08:02:44 -0500

Seen: 347 times

Last updated: Aug 26 '18