Created attachment 1402547 [details] Contents of "Details" of failure in "Problem Reporting" application. Description of problem: Hardware: HP Envy x360 with AMD Ryzen 2500U APU Every time I boot into Fedora I get the following notification: We're sorry, it looks like BOOT_IMAGE=/boot/vmlinuz-4.15.4-300.fc27.x86_64 crashed. Please contact the developer if you want to report the issue. Opening "Problem Reporting" application does not allow me to report the issue. Here is the information from there: Unexpected system error The system has encountered a problem and recovered. Name: kernel-core Version: 4.15.4-300.fc27.x86_64 First Detected: 4 minutes ago Reported: Cannot be reported 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. Version-Release number of selected component (if applicable): Kernel: 4.15.4-300.fc27.x86_64 abrt.x86_64: 2.10.6-2.fc27 How reproducible: Steps to Reproduce: 1. Boot into Fedora and log into KDE Plasma 2. 3. Actual results: Notification saying "We're sorry, it looks like BOOT_IMAGE=/boot/vmlinuz-4.15.4-300.fc27.x86_64 crashed. Please contact the developer if you want to report the issue." Expected results: No error and thus no notification Additional info: Details are attached
Looks like a graphics issue, moving to the graphics team to take a look.
Looks like I have the same problem, but I have nvidia graphics with the nouveau driver. kernel 4.15.6-200.fc26 just came out. I might luck out and it has a fix # abrt-cli ls| grep -B4 -A3 kernel-core id f7dcb5f4a1e7d731dcb2dcf80c10894a207dcfe9 reason: BUG: unable to handle kernel NULL pointer dereference at 0000000000000040 time: Thu 01 Mar 2018 10:23:16 PM CST cmdline: BOOT_IMAGE=/vmlinuz-4.15.4-200.fc26.x86_64 root=/dev/mapper/fedora_jm-root ro rd.lvm.lv=fedora_jm/root rd.lvm.lv=fedora_jm/swap rhgb quiet resume=/dev/mapper/fedora_jm-swap LANG=en_US.UTF-8 package: kernel-core-4.15.4-200.fc26 count: 1 Directory: /var/spool/abrt/oops-20180302 Reported: cannot be reported --
Still getting the same issue on kernel 4.15.6-300.fc27. # abrt-cli ls| grep -B4 -A3 kernel-core id f998c46a1c848b15537d1b469670692fd81d1afb reason: WARNING: CPU: 6 PID: 340 at drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:190 generic_reg_wait+0xee/0x120 [amdgpu] time: Mon 05 Mar 2018 09:38:04 AM EST cmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.6-300.fc27.x86_64 root=UUID=f7548a91-a3d2-4ec2-8573-c7f313417cda ro rhgb quiet LANG=en_US.UTF-8 package: kernel-core-4.15.6-300.fc27 count: 1 Directory: /var/spool/abrt/oops-2018-03-05-09:38:03-933-1 Reported: cannot be reported
I have no idea if what I'm experiencing is genuinely the same issue, given I'm using the Nouveau drivers for nVidia. I even took a moment to remove the xorg-x11-drv-ati . I had been experiencing occasional onscreen graphical corruption in the past, before these suspend failures. Some attempts to get logs today resulted in corruption in text rendering (rectangles the same size as particular letters) which persisted until logout. Logging out seemed to clear things up. It seems very possible that what I'm seeing is a regressing back from "harmless graphical glitches" through to "the system cannot manage graphical memory through a suspend" Of note from suspend tests [root@jm EENG5340ML]# cat /sys/power/disk platform shutdown reboot [suspend] test_resume [root@jm EENG5340ML]# cat /sys/power/pm_test none core processors platform [devices] freezer Mar 6 21:47:08 jm kernel: nouveau 0000:01:00.0: fb: trapped write at 00a0e8e2c0 on channel 2 [0fbae000 DRM] engine 0d [PCE0] client 13 [] subclient 02 [] reason 00000000 [PT_NOT_PRESENT] Mar 6 21:47:08 jm kernel: nouveau 0000:01:00.0: ce0: intr 00000200 Mar 6 21:47:08 jm kernel: nouveau 0000:01:00.0: fb: trapped write at 00a0e8ed30 on channel 2 [0fbae000 DRM] engine 0d [PCE0] client 13 [] subclient 02 [] reason 00000000 [PT_NOT_PRESENT] Mar 6 21:47:08 jm kernel: nouveau 0000:01:00.0: ce0: intr 00000200 Mar 6 21:47:08 jm kernel: nouveau 0000:01:00.0: fb: trapped write at 00a0e8f7c0 on channel 2 [0fbae000 DRM] engine 0d [PCE0] client 13 [] subclient 02 [] reason 00000000 [PT_NOT_PRESENT] Mar 6 21:47:08 jm kernel: nouveau 0000:01:00.0: ce0: intr 00000200
Still getting the same issue on kernels 4.15.8-300.fc27: # abrt-cli ls| grep -B4 -A3 kernel-core id cef0760de6900946d7838647fada3b7ec421c99d reason: WARNING: CPU: 5 PID: 345 at drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:190 generic_reg_wait+0xee/0x120 [amdgpu] time: Thu 15 Mar 2018 12:11:17 AM EDT cmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.8-300.fc27.x86_64 root=UUID=f7548a91-a3d2-4ec2-8573-c7f313417cda ro rhgb quiet LANG=en_US.UTF-8 package: kernel-core-4.15.8-300.fc27 count: 1 Directory: /var/spool/abrt/oops-2018-03-15-00:11:16-1028-1 Reported: cannot be reported -- id fa26eb75701dc624ca91b5e3a9c1d78710f6f0bf reason: i2c_dw_init_master(): WARNING: CPU: 2 PID: 1 at drivers/i2c/busses/i2c-designware-common.c:183 i2c_dw_clk_rate+0x16/0x20 time: Thu 15 Mar 2018 12:11:16 AM EDT cmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.8-300.fc27.x86_64 root=UUID=f7548a91-a3d2-4ec2-8573-c7f313417cda ro rhgb quiet LANG=en_US.UTF-8 package: kernel-core-4.15.8-300.fc27 count: 1 Directory: /var/spool/abrt/oops-2018-03-15-00:11:16-1028-0
Still happening with kernel 4.15.9-300.fc27 # abrt-cli ls | grep -B4 -A3 kernel-core id 082f429c7f3cd9d008453158fe3dcaa873dab40f reason: WARNING: CPU: 6 PID: 339 at drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:190 generic_reg_wait+0xee/0x120 [amdgpu] time: Sun 18 Mar 2018 09:09:10 PM EDT cmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.9-300.fc27.x86_64 root=UUID=f7548a91-a3d2-4ec2-8573-c7f313417cda ro rhgb quiet LANG=en_US.UTF-8 package: kernel-core-4.15.9-300.fc27 count: 1 Directory: /var/spool/abrt/oops-2018-03-18-21:09:09-1025-1 Reported: cannot be reported
Still happening with kernel 4.15.12-301.fc27.x86_64. id 7501a5a34e13f3d03b3fc33a0e9df6f02ba8904e reason: WARNING: CPU: 3 PID: 346 at drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:190 generic_reg_wait+0xee/0x120 [amdgpu] time: Wed 28 Mar 2018 06:17:20 PM EDT cmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.12-301.fc27.x86_64 root=UUID=f7548a91-a3d2-4ec2-8573-c7f313417cda ro rhgb quiet LANG=en_US.UTF-8 package: kernel-core-4.15.12-301.fc27 count: 1 Directory: /var/spool/abrt/oops-2018-03-28-18:17:19-1064-1 Reported: cannot be reported
Still happening with kernel 5.15.17-300-fc27.x86_64. # abrt-cli ls | grep -B4 -A3 kernel-core-4.15.17 id 35192c956690cf434225b13c0aafcab89f496069 reason: WARNING: CPU: 5 PID: 356 at drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:190 generic_reg_wait+0xee/0x120 [amdgpu] time: Fri 20 Apr 2018 09:15:19 AM EDT cmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.17-300.fc27.x86_64 root=UUID=f7548a91-a3d2-4ec2-8573-c7f313417cda ro rhgb quiet LANG=en_US.UTF-8 package: kernel-core-4.15.17-300.fc27 count: 1 Directory: /var/spool/abrt/oops-2018-04-20-09:15:18-1091-1 Reported: cannot be reported -- id 12c4091aa57eb3fbb0cdef8dfcf0d0841b4db45a reason: WARNING: CPU: 2 PID: 345 at drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:190 generic_reg_wait+0xee/0x120 [amdgpu] time: Fri 20 Apr 2018 09:12:46 AM EDT cmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.17-300.fc27.x86_64 root=UUID=f7548a91-a3d2-4ec2-8573-c7f313417cda ro rhgb quiet LANG=en_US.UTF-8 package: kernel-core-4.15.17-300.fc27 count: 1 Directory: /var/spool/abrt/oops-2018-04-20-09:12:45-1089-1 Reported: cannot be reported
I have the same issue on a T480 with an MX150 WARNING: CPU: 7 PID: 9270 at drivers/gpu/drm/nouveau/nvkm/subdev/pmu/base.c:86 nvkm_pmu_reset+0x14c/0x160 [nouveau] BOOT_IMAGE=/vmlinuz-4.15.17-300.fc27.x86_64 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/root rd.lvm.lv=fedora/swap rhgb quiet LANG=en_PH.UTF-8 kernel-core-4.15.17-300.fc27 xorg-x11-drv-nouveau Fedora release 27 (Twenty Seven) W - Taint on warning.
Happening to me on Fedora 28 Kernel 4.17.3-200 Intel UHD 620 Intel i7-8550U Seems to happen on both xorg and wayland. Output of dmesg: https://paste.fedoraproject.org/paste/1oSyPPz97yvUWPuZ2N9aYw
Also happens on Fedora 28 kernel 4.18.7-200.fc28.x86_64 Intel i7-3770 dmesg doesn't show me anything went wrong My log first reports it happening with Fedora 28 kernel 4.17.14-202.fc28.x86_64 at 2018-08-22 22:45:42 right after doing an update The backtrace is: traps: QThread[1836] trap invalid opcode ip:7f95c5786fe0 sp:7f95a5481758 error:0 in libQt5Core.so.5.11.1[7f95c545a000+4d7000] This is with the KDE desktop
Happens on F28 KDE, 4.18.7-200 reason: traps: QThread[2405] trap invalid opcode ip:7f668cbacfe0 sp:7f6666c40758 error:0 in libQt5Core.so.5.11.1[7f668c880000+4d7000] backtrace: traps: QThread[2405] trap invalid opcode ip:7f668cbacfe0 sp:7f6666c40758 error:0 in libQt5Core.so.5.11.1[7f668c880000+4d7000] cmdline: BOOT_IMAGE=/vmlinuz-4.18.7-200.fc28.x86_64 root=/dev/mapper/fedora_localhost--live-root ro resume=/dev/mapper/fedora_localhost--live-swap rd.lvm.lv=fedora_localhost-live/root rd.lvm.lv=fedora_localhost-live/swap rhgb quiet LANG=en_US.UTF-8 abrt_version: 2.10.10 os_info: NAME=Fedora VERSION="28 (Twenty Eight)" ID=fedora VERSION_ID=28 PLATFORM_ID="platform:f28" PRETTY_NAME="Fedora 28 (Twenty Eight)" ANSI_COLOR="0;34" CPE_NAME="cpe:/o:fedoraproject:fedora:28" HOME_URL="https://fedoraproject.org/" SUPPORT_URL="https://fedoraproject.org/wiki/Communicating_and_getting_help" BUG_REPORT_URL="https://bugzilla.redhat.com/" REDHAT_BUGZILLA_PRODUCT="Fedora" REDHAT_BUGZILLA_PRODUCT_VERSION=28 REDHAT_SUPPORT_PRODUCT="Fedora" REDHAT_SUPPORT_PRODUCT_VERSION=28 PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy" cpu: Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz gpu: AMD RX-580 XFX
Can confirm that it is happening on F28 KDE, detailed report from abrt-cli: https://ghostbin.com/paste/hcfe3 I am using proprietary nvidia drivers from RPMFusion cmdline: BOOT_IMAGE=/boot/vmlinuz-4.18.10-200.fc28.x86_64 root=UUID=62bf6187-b8af-4640-ab08-94668af51784 ro modprobe.blacklist=nouveau nvidia-drm.modeset=1 rhgb quiet LANG=en_IN.UTF-8 kernel: 4.18.10-200.fc28.x86_64 CPU: Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz GPU: Nvidia GTX 1050Ti
This crash is occurring for me regularly in F28 KDE running in VBox with Guest Additions installed.
I haven't gotten this error in a while. I believe since at least kernel 4.18 I have been fine. I am now on Fedora 29 kernel version 4.19.2-300.fc29.x86_64 and so far I haven't experienced this issue.
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.