Fedora 30 vmlinuz crashing

I decided to convert a brand new Lenovo Thinkpad P52s from Windows 10 (pre-packaged) to Fedora 30. First install went fine and I was using it for about a week before it would no longer boot into Fedora. The errors from abrt would say:

5.0.17-300.fc30.x86_64 crashed

I figure its most likely a bug that needs to be fixed, but I don’t know; I’m new to Fedora and work mostly with CentOS. Also, this is the first time I’ve seen an issue like this.

Here’s my system info:

Kernel: 5.0.17-300.fc30.x86_64

CPU: Intel® Core™ i7-8650U CPU @ 1.90GHz

SSD: 256 GB

RAM: 32 GB

Unfortunately, until the holiday weekend is over, I need something to be able to respond to work related on-call alerts and reinstalled Fedora 30. The same issue is being displayed after a reboot or power on. Any insight would be great appreciated as to why the issue is occurring.

Hi @mmccullough. Welcome to the community. Please go through the posts in #start-here if you haven’t had a chance yet. They include useful information on how we can best use this platform.

Off the top of my head, this could be a kernel regression, but more information will help clear that up. In the meantime, could you please boot into an older kernel? By default, Fedora keeps the last 3—so you should be able to choose an older one from the boot menu and get your system working. Then, could you look at the system logs to see if there’s anything there that gives us a hint? The “problem reporter” tool (abrt) should also notify you of these crashes and ask you to submit problem reports.

This quick-doc has information on viewing the system logs:

https://docs.fedoraproject.org/en-US/quick-docs/viewing-logs/

Hi Francisco, I will definitely check out the starter guide. In the meantime, when I mean I was no longer able to boot into Fedora, I mean I couldn’t even get the boot loader to work. Meaning I couldn’t select an earlier kernel. It plain wasn’t reading the boot partition and kept returning to the boot order screen. In this current installation, the abrt tool doesn’t allow me to report the issue (see screenshots).Screenshot%20from%202019-05-25%2010-23-23

Additionally, the issue exists on the initial installation of Fedora 30. It remains on the kernel upgrade as well (there’s only been one since the release if I’m correct). I’m not a kernel dev so I’m not really sure if these could be related to the boot image crashing after booting into the OS (really strange behavior):

May 25 11:50:20 kernel: RAS: Correctable Errors collector initialized.
May 25 11:50:21 kernel: ACPI Warning: \_SB.PCI0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20181213/nsarguments-59)
May 25 11:50:21 kernel: ACPI Warning: \_SB.PCI0.RP01.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20181213/nsarguments-59)
May 25 11:50:23 kernel: WARNING: CPU: 1 PID: 437 at drivers/gpu/drm/nouveau/nvkm/subdev/pmu/base.c:83 nvkm_pmu_reset+0x148/0x160 [nouveau]
May 25 11:50:31 kernel: WARNING: CPU: 7 PID: 1485 at drivers/gpu/drm/nouveau/nvkm/engine/gr/gf100.c:1521 gf100_gr_init_ctxctl_ext+0x323/0x7d0 [nouveau]
May 25 11:50:33 kernel: WARNING: CPU: 3 PID: 1485 at drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c:204 gf100_vmm_flush_+0x17b/0x190 [nouveau]
May 25 11:50:35 kernel: WARNING: CPU: 1 PID: 1485 at drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c:204 gf100_vmm_flush_+0x17b/0x190 [nouveau]
May 25 11:50:37 kernel: WARNING: CPU: 5 PID: 1485 at drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c:204 gf100_vmm_flush_+0x17b/0x190 [nouveau]
May 25 11:50:39 kernel: WARNING: CPU: 1 PID: 1485 at drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c:204 gf100_vmm_flush_+0x17b/0x190 [nouveau]
May 25 11:50:41 kernel: WARNING: CPU: 0 PID: 1485 at drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c:204 gf100_vmm_flush_+0x17b/0x190 [nouveau]
May 25 11:50:43 kernel: WARNING: CPU: 4 PID: 1485 at drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c:204 gf100_vmm_flush_+0x17b/0x190 [nouveau]
May 25 11:50:45 kernel: WARNING: CPU: 0 PID: 1485 at drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c:204 gf100_vmm_flush_+0x17b/0x190 [nouveau]
May 25 11:50:47 kernel: WARNING: CPU: 4 PID: 1485 at drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c:204 gf100_vmm_flush_+0x17b/0x190 [nouveau]
May 25 18:50:55 kernel: WARNING: CPU: 0 PID: 652 at drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c:204 gf100_vmm_flush_+0x17b/0x190 [nouveau]
May 25 18:50:57 kernel: WARNING: CPU: 0 PID: 652 at drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c:204 gf100_vmm_flush_+0x17b/0x190 [nouveau]
May 25 18:50:57 kernel: WARNING: CPU: 0 PID: 652 at drivers/gpu/drm/nouveau/nvkm/falcon/v1.c:290 falcon_v1_wait_idle.isra.0+0xb0/0xc0 [nouveau]
May 25 18:50:57 kernel: WARNING: CPU: 0 PID: 652 at drivers/gpu/drm/nouveau/nvkm/falcon/v1.c:290 falcon_v1_wait_idle.isra.0+0xb0/0xc0 [nouveau]
May 25 18:50:59 kernel: WARNING: CPU: 0 PID: 652 at drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c:204 gf100_vmm_flush_+0x17b/0x190 [nouveau]
May 25 18:57:02 kernel: WARNING: CPU: 1 PID: 1 at drivers/gpu/drm/nouveau/nouveau_gem.c:160 nouveau_gem_object_close+0x1de/0x210 [nouveau]
May 25 18:57:02 kernel: WARNING: CPU: 1 PID: 1 at drivers/gpu/drm/nouveau/nouveau_gem.c:49 nouveau_gem_object_del+0xb8/0xd0 [nouveau]
May 25 18:57:02 kernel: WARNING: CPU: 1 PID: 1 at drivers/gpu/drm/nouveau/nvkm/subdev/bar/g84.c:35 g84_bar_flush+0xd0/0xe0 [nouveau]
May 25 18:57:02 kernel: WARNING: CPU: 1 PID: 1 at drivers/gpu/drm/nouveau/nvkm/subdev/bar/g84.c:35 g84_bar_flush+0xd0/0xe0 [nouveau]
May 25 18:57:02 kernel: WARNING: CPU: 1 PID: 1 at drivers/gpu/drm/nouveau/nvkm/subdev/bar/g84.c:35 g84_bar_flush+0xd0/0xe0 [nouveau]
May 26 02:04:22 kernel: abrt-applet[2641]: segfault at 0 ip 00007f65ad11701c sp 00007ffcd67e7ba0 error 4 in libreport-gtk.so.0.0.1[7f65ad10f000+9000]
May 27 15:26:53 kernel: traps: TaskSchedulerSi[3146] trap int3 ip:558653433cfb sp:7f0a65384cd0 error:0 in chrome[558650e0f000+6969000]

Do you have an insight into this information

Thanks!

1 Like

I was only allowed to add one screenshot, but this is what abrt shows when I bring it up via the GUI:

1 Like

It looks like an issue with the free/opensource nvidia graphics driver—nouveau.

https://nouveau.freedesktop.org/wiki/

Have you given the non-free nvidia driver from RPMFusion a try yet?

https://rpmfusion.org/Howto/NVIDIA

Francisco,

I was able to install the NVIDIA Quadro drivers and resolved the boot image crashing!

Thanks very much,

Mitch

1 Like