Additional info: reporter: libreport-2.9.5 BUG: unable to handle kernel NULL pointer dereference at 0000000000000000 PGD 0 P4D 0 Oops: 0000 [#1] SMP NOPTI Modules linked in: amdkfd amd_iommu_v2 amdgpu chash i2c_algo_bit gpu_sched drm_kms_helper ttm drm crc32c_intel r8169 mii CPU: 0 PID: 653 Comm: udevadm Not tainted 4.17.12-200.fc28.x86_64 #1 Hardware name: Gigabyte Technology Co., Ltd. AB350-Gaming/AB350-Gaming-CF, BIOS F23d 04/17/2018 RIP: 0010:strchr+0x0/0x30 RSP: 0018:ffffc1798126bd10 EFLAGS: 00010246 RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffc1798126bd54 RDX: ffffc1798126bd50 RSI: 0000000000000021 RDI: 0000000000000000 RBP: ffffa00cd513a000 R08: ffffc1798126bd58 R09: ffffa00cd0426000 R10: ffffffff8d132c64 R11: ffffa00cd042612c R12: ffffc1798126bd58 R13: ffffc1798126bd4e R14: ffffa00cd0426000 R15: ffffa00cd1e2b880 FS: 00007fa7d555f180(0000) GS:ffffa00cdec00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000000 CR3: 000000020fe4c000 CR4: 00000000003406f0 Call Trace: device_get_devnode+0x8a/0xd0 dev_uevent+0x170/0x2f0 ? kmem_cache_alloc_trace+0x166/0x1d0 uevent_show+0x94/0x100 dev_attr_show+0x1c/0x40 sysfs_kf_seq_show+0x9f/0x120 seq_read+0x16b/0x460 __vfs_read+0x36/0x170 vfs_read+0x8a/0x140 ksys_read+0x4f/0xb0 do_syscall_64+0x5b/0x160 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7fa7d4184091 RSP: 002b:00007ffe3dc94a88 EFLAGS: 00000246 ORIG_RAX: 0000000000000000 RAX: ffffffffffffffda RBX: 0000555f57487f90 RCX: 00007fa7d4184091 RDX: 0000000000001000 RSI: 0000555f574efc50 RDI: 0000000000000005 RBP: 00007fa7d444f2a0 R08: 0000000000000003 R09: 0000000000000000 R10: 0000555f57420010 R11: 0000000000000246 R12: 0000000000001001 R13: 0000555f574efc50 R14: 0000000000000d68 R15: 00007fa7d444e760 Code: 44 38 c1 75 10 48 83 c0 01 84 c9 74 05 48 39 d0 75 e5 31 c0 c3 44 38 c1 19 c0 83 c8 01 c3 0f 1f 00 66 2e 0f 1f 84 00 00 00 00 00 <0f> b6 07 89 f2 40 38 f0 75 0d eb 12 48 83 c7 01 0f b6 07 38 d0 RIP: strchr+0x0/0x30 RSP: ffffc1798126bd10 CR2: 0000000000000000
Created attachment 1476112 [details] File: dmesg
We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 28 kernel bugs. Fedora 28 has now been rebased to 4.18.10-300.fc28. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 29, and are still experiencing this issue, please change the version to Fedora 29. If you experience different issues, please open a new bug report for those.
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and let us know if the bug is still present on the latest kernel. (Please note: sometimes bugs get mistakenly closed during our mass closing. If you think your bug was closed in error please reopen)
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days