[Kernel-packages] [Bug 2056303] Re: several UBSAN: array-index-out-of-bounds in .../hwmgr/processpptables.c
buntu 6.5.0-21.21~22.04.1-generic 6.5.8 ** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056303/+attachment/5753222/+files/version.log ** Description changed: On one Lenovo machine, using a hwe-22.04 kernel, I get several messages from UBSAN while booting. Previously, on the non-hwe kernel for Jammy, the screen went black shortly after logging in, and that doesn't seem to happen any more, so there is improvement, but it seems still something is going wrong. Attached are the dmesg (where the UBSAN errors are listed), and the output from lspci and the version. + + In the dmesg there is this line, + + [ 19.151801] kfd kfd: amdgpu: STONEY not supported in kfd + + which somewhere was indicated that it would be improved in the hwe + kernel (that's why I tried it). Apparently the issue isn't fully fixex, + but the error seems to be handled better. (Source: + https://forums.linuxmint.com/viewtopic.php?t=410244 ) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056303 Title: several UBSAN: array-index-out-of-bounds in .../hwmgr/processpptables.c Status in linux package in Ubuntu: New Bug description: On one Lenovo machine, using a hwe-22.04 kernel, I get several messages from UBSAN while booting. Previously, on the non-hwe kernel for Jammy, the screen went black shortly after logging in, and that doesn't seem to happen any more, so there is improvement, but it seems still something is going wrong. Attached are the dmesg (where the UBSAN errors are listed), and the output from lspci and the version. In the dmesg there is this line, [ 19.151801] kfd kfd: amdgpu: STONEY not supported in kfd which somewhere was indicated that it would be improved in the hwe kernel (that's why I tried it). Apparently the issue isn't fully fixex, but the error seems to be handled better. (Source: https://forums.linuxmint.com/viewtopic.php?t=410244 ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056303/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056303] Re: several UBSAN: array-index-out-of-bounds in .../hwmgr/processpptables.c
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056303/+attachment/5753221/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056303 Title: several UBSAN: array-index-out-of-bounds in .../hwmgr/processpptables.c Status in linux package in Ubuntu: New Bug description: On one Lenovo machine, using a hwe-22.04 kernel, I get several messages from UBSAN while booting. Previously, on the non-hwe kernel for Jammy, the screen went black shortly after logging in, and that doesn't seem to happen any more, so there is improvement, but it seems still something is going wrong. Attached are the dmesg (where the UBSAN errors are listed), and the output from lspci and the version. In the dmesg there is this line, [ 19.151801] kfd kfd: amdgpu: STONEY not supported in kfd which somewhere was indicated that it would be improved in the hwe kernel (that's why I tried it). Apparently the issue isn't fully fixex, but the error seems to be handled better. (Source: https://forums.linuxmint.com/viewtopic.php?t=410244 ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056303/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056303] [NEW] several UBSAN: array-index-out-of-bounds in .../hwmgr/processpptables.c
Public bug reported: On one Lenovo machine, using a hwe-22.04 kernel, I get several messages from UBSAN while booting. Previously, on the non-hwe kernel for Jammy, the screen went black shortly after logging in, and that doesn't seem to happen any more, so there is improvement, but it seems still something is going wrong. Attached are the dmesg (where the UBSAN errors are listed), and the output from lspci and the version. In the dmesg there is this line, [ 19.151801] kfd kfd: amdgpu: STONEY not supported in kfd which somewhere was indicated that it would be improved in the hwe kernel (that's why I tried it). Apparently the issue isn't fully fixex, but the error seems to be handled better. (Source: https://forums.linuxmint.com/viewtopic.php?t=410244 ) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "dmesg" https://bugs.launchpad.net/bugs/2056303/+attachment/5753220/+files/dmesg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056303 Title: several UBSAN: array-index-out-of-bounds in .../hwmgr/processpptables.c Status in linux package in Ubuntu: New Bug description: On one Lenovo machine, using a hwe-22.04 kernel, I get several messages from UBSAN while booting. Previously, on the non-hwe kernel for Jammy, the screen went black shortly after logging in, and that doesn't seem to happen any more, so there is improvement, but it seems still something is going wrong. Attached are the dmesg (where the UBSAN errors are listed), and the output from lspci and the version. In the dmesg there is this line, [ 19.151801] kfd kfd: amdgpu: STONEY not supported in kfd which somewhere was indicated that it would be improved in the hwe kernel (that's why I tried it). Apparently the issue isn't fully fixex, but the error seems to be handled better. (Source: https://forums.linuxmint.com/viewtopic.php?t=410244 ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056303/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032164] Re: A general-proteciton exception during guest migration to unsupported PKRU machine
Is there an alternative patch in development? This bug (or at least it seems to be this bug) still affects us. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2032164 Title: A general-proteciton exception during guest migration to unsupported PKRU machine Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Triaged Bug description: [Impact] When a host that supports PKRU initiates a guest that lacks PKRU support, the flag is enabled on the guest's fpstate. This information is then passed to userspace through the vcpu ioctl KVM_GET_XSAVE. However, a problem arises when the user opts to migrate the mentioned guest to another machine that does not support PKRU. In this scenario, the new host attempts to restore the guest's fpu registers. Nevertheless, due to the absence of PKRU support on the new host, a general-protection exception takes place, leading to a guest crash. [Fix] The problem is resolved by the following upstream commit: ad856280ddea x86/kvm/fpu: Limit guest user_xfeatures to supported bits of XCR0 Additionally, a subsequent fix tackles the migration problem stemming from the earlier commit: a1020a25e697 KVM: x86: Always enable legacy FP/SSE in allowed user XFEATURES [Test Plan] 1. Set up two machines: one with PKRU support and the other without. 2. Initiate a guest that lacks PKRU support on the machine with PKRU support. 3. Utilize libvirt to migrate the aforementioned guest to a different machine that lacks PKRU support. 4. The error emerges on the destination machine: KVM: entry failed, hardware error 0x8021 If you're running a guest on an Intel machine without unrestricted mode support, the failure can be most likely due to the guest entering an invalid state for Intel VT. For example, the guest maybe running in big real mode which is not supported on less recent Intel processors. EAX=86cf7970 EBX= ECX=0001 EDX=005b0036 ESI=0087 EDI=0087 EBP=87c03e38 ESP=87c03e18 EIP=86cf7d5e EFL=0246 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <00> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2023-07-09T03:03:14.911750Z qemu-system-x86_64: terminating on signal 15 from pid 4134 (/usr/sbin/libvirtd) 2023-07-09 03:03:15.312+: shutting down, reason=destroyed [Where problems could occur] The introduced commits will impact the guest migration process, potentially leading to failures and preventing the guest from operating successfully on the migration destination. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2032164/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1777245] Re: X freezes with kernel 4.15.0-23-generic (AMDGPU)
@jsalisbury: I had the machine tested with this kernel: Linux xa-xubu 4.18.0-041800rc1-generic #201806162031 SMP Sun Jun 17 00:34:22 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux that I found via your link [0]. The result is that in this kernel, the problem is gone. So that sounds like good news! I think there was another commenter asking me to try a (probably different) upstream kernel, but it seems gone now. To them I can report that I didn't try building a kernel myself, but hopefully their proposal was close enough to using the Ubuntu mainline kernel that this test gives them the answer they are looking for. ** Tags added: kernel-fixed-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777245 Title: X freezes with kernel 4.15.0-23-generic (AMDGPU) Status in linux package in Ubuntu: Confirmed Bug description: This is on my parents machine; I only have remote access and not continuously, so this may slow down providing additional information. Since the latest kernel upgrade (from Linux version 4.13.0-43-generic (buildd@lgw01-amd64-026) (gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3.2)) #48-Ubuntu SMP Wed May 16 12:18:48 UTC 2018 (Ubuntu 4.13.0-43.48-generic 4.13.16) to Linux version 4.15.0-23-generic (buildd@lgw01-amd64-055) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 (Ubuntu 4.15.0-23.25-generic 4.15.18) the machine appears to freezes some time soon after booting. It is just X; the machine is still reachable via ssh. I filed this bug using apport-cli, running the older (working) kernel, not the newer (failing) one. In /var/log/kernel I can see the following: Jun 15 23:26:23 xa-xubu kernel: [ 2417.562386] INFO: task Xorg:757 blocked for more than 120 seconds. Jun 15 23:26:23 xa-xubu kernel: [ 2417.562396] Not tainted 4.15.0-23-generic #25-Ubuntu Jun 15 23:26:23 xa-xubu kernel: [ 2417.562399] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jun 15 23:26:23 xa-xubu kernel: [ 2417.562403] XorgD0 757 724 0x0044 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562408] Call Trace: Jun 15 23:26:23 xa-xubu kernel: [ 2417.562424] __schedule+0x297/0x8b0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562430] ? __kfifo_in+0x37/0x50 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562434] schedule+0x2c/0x80 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562559] amd_sched_entity_push_job+0xad/0xf0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562565] ? wait_woken+0x80/0x80 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562653] amdgpu_job_submit+0x9f/0xc0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562723] amdgpu_vm_bo_update_mapping+0x389/0x3f0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562793] ? amdgpu_vm_it_iter_first+0x40/0x40 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562863] amdgpu_vm_bo_update+0x325/0x5b0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562930] amdgpu_gem_va_ioctl+0x524/0x540 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562962] ? drm_gem_handle_create_tail+0x120/0x190 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563028] ? amdgpu_gem_create_ioctl+0xc1/0x270 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563096] ? amdgpu_gem_metadata_ioctl+0x1c0/0x1c0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563115] drm_ioctl_kernel+0x5f/0xb0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563134] ? drm_ioctl_kernel+0x5f/0xb0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563154] drm_ioctl+0x31b/0x3d0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563220] ? amdgpu_gem_metadata_ioctl+0x1c0/0x1c0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563225] ? update_load_avg+0x57f/0x6e0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563231] ? futex_wake+0x8f/0x180 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563290] amdgpu_drm_ioctl+0x4f/0x90 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563296] do_vfs_ioctl+0xa8/0x630 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563300] ? __schedule+0x29f/0x8b0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563304] SyS_ioctl+0x79/0x90 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563309] do_syscall_64+0x73/0x130 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563313] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563317] RIP: 0033:0x7fbd7ddcf5d7 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563319] RSP: 002b:7fff67e69aa8 EFLAGS: 3246 ORIG_RAX: 0010 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563322] RAX: ffda RBX: 0002 RCX: 7fbd7ddcf5d7 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563324] RDX: 7fff67e69af0 RSI: c0286448 RDI: 000e Jun 15 23:26:23 xa-xubu kernel: [ 2417.563326] RBP: 7fff67e69af0 R08: 00010144 R09:
[Kernel-packages] [Bug 1777245] Re: X freezes with kernel 4.15.0-23-generic (AMDGPU)
Yes, the problem started after an upgrade. From what I can see in the logs it seems that first the machine was upgraded from Ubuntu 17.10 to 18.04, apparently without problem. Then a few days later, the working kernel Ubuntu 4.13.0-43.48-generic 4.13.16 was replaced by 4.15.0-23.25-generic 4.15.18 which fails. It will not be so easy to test another kernel, but I'll try. It will definitely be some days before I can report a result, I suspect. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777245 Title: X freezes with kernel 4.15.0-23-generic (AMDGPU) Status in linux package in Ubuntu: Incomplete Bug description: This is on my parents machine; I only have remote access and not continuously, so this may slow down providing additional information. Since the latest kernel upgrade (from Linux version 4.13.0-43-generic (buildd@lgw01-amd64-026) (gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3.2)) #48-Ubuntu SMP Wed May 16 12:18:48 UTC 2018 (Ubuntu 4.13.0-43.48-generic 4.13.16) to Linux version 4.15.0-23-generic (buildd@lgw01-amd64-055) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 (Ubuntu 4.15.0-23.25-generic 4.15.18) the machine appears to freezes some time soon after booting. It is just X; the machine is still reachable via ssh. I filed this bug using apport-cli, running the older (working) kernel, not the newer (failing) one. In /var/log/kernel I can see the following: Jun 15 23:26:23 xa-xubu kernel: [ 2417.562386] INFO: task Xorg:757 blocked for more than 120 seconds. Jun 15 23:26:23 xa-xubu kernel: [ 2417.562396] Not tainted 4.15.0-23-generic #25-Ubuntu Jun 15 23:26:23 xa-xubu kernel: [ 2417.562399] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jun 15 23:26:23 xa-xubu kernel: [ 2417.562403] XorgD0 757 724 0x0044 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562408] Call Trace: Jun 15 23:26:23 xa-xubu kernel: [ 2417.562424] __schedule+0x297/0x8b0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562430] ? __kfifo_in+0x37/0x50 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562434] schedule+0x2c/0x80 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562559] amd_sched_entity_push_job+0xad/0xf0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562565] ? wait_woken+0x80/0x80 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562653] amdgpu_job_submit+0x9f/0xc0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562723] amdgpu_vm_bo_update_mapping+0x389/0x3f0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562793] ? amdgpu_vm_it_iter_first+0x40/0x40 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562863] amdgpu_vm_bo_update+0x325/0x5b0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562930] amdgpu_gem_va_ioctl+0x524/0x540 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562962] ? drm_gem_handle_create_tail+0x120/0x190 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563028] ? amdgpu_gem_create_ioctl+0xc1/0x270 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563096] ? amdgpu_gem_metadata_ioctl+0x1c0/0x1c0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563115] drm_ioctl_kernel+0x5f/0xb0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563134] ? drm_ioctl_kernel+0x5f/0xb0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563154] drm_ioctl+0x31b/0x3d0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563220] ? amdgpu_gem_metadata_ioctl+0x1c0/0x1c0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563225] ? update_load_avg+0x57f/0x6e0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563231] ? futex_wake+0x8f/0x180 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563290] amdgpu_drm_ioctl+0x4f/0x90 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563296] do_vfs_ioctl+0xa8/0x630 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563300] ? __schedule+0x29f/0x8b0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563304] SyS_ioctl+0x79/0x90 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563309] do_syscall_64+0x73/0x130 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563313] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563317] RIP: 0033:0x7fbd7ddcf5d7 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563319] RSP: 002b:7fff67e69aa8 EFLAGS: 3246 ORIG_RAX: 0010 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563322] RAX: ffda RBX: 0002 RCX: 7fbd7ddcf5d7 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563324] RDX: 7fff67e69af0 RSI: c0286448 RDI: 000e Jun 15 23:26:23 xa-xubu kernel: [ 2417.563326] RBP: 7fff67e69af0 R08: 00010144 R09: 000a Jun 15 23:26:23 xa-xubu kernel: [ 2417.563328] R10: 0039 R11: 3246 R12: c0286448 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563330] R13: 000e R14: 55e820965f20 R15: 0 which seems to point to some in-kernel AMD GPU
[Kernel-packages] [Bug 1777245] Re: X freezes with kernel 4.15.0-23-generic (AMDGPU)
Oops, the above message was not supposed to be mailed here... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777245 Title: X freezes with kernel 4.15.0-23-generic (AMDGPU) Status in linux package in Ubuntu: Confirmed Bug description: This is on my parents machine; I only have remote access and not continuously, so this may slow down providing additional information. Since the latest kernel upgrade (from Linux version 4.13.0-43-generic (buildd@lgw01-amd64-026) (gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3.2)) #48-Ubuntu SMP Wed May 16 12:18:48 UTC 2018 (Ubuntu 4.13.0-43.48-generic 4.13.16) to Linux version 4.15.0-23-generic (buildd@lgw01-amd64-055) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 (Ubuntu 4.15.0-23.25-generic 4.15.18) the machine appears to freezes some time soon after booting. It is just X; the machine is still reachable via ssh. I filed this bug using apport-cli, running the older (working) kernel, not the newer (failing) one. In /var/log/kernel I can see the following: Jun 15 23:26:23 xa-xubu kernel: [ 2417.562386] INFO: task Xorg:757 blocked for more than 120 seconds. Jun 15 23:26:23 xa-xubu kernel: [ 2417.562396] Not tainted 4.15.0-23-generic #25-Ubuntu Jun 15 23:26:23 xa-xubu kernel: [ 2417.562399] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jun 15 23:26:23 xa-xubu kernel: [ 2417.562403] XorgD0 757 724 0x0044 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562408] Call Trace: Jun 15 23:26:23 xa-xubu kernel: [ 2417.562424] __schedule+0x297/0x8b0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562430] ? __kfifo_in+0x37/0x50 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562434] schedule+0x2c/0x80 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562559] amd_sched_entity_push_job+0xad/0xf0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562565] ? wait_woken+0x80/0x80 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562653] amdgpu_job_submit+0x9f/0xc0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562723] amdgpu_vm_bo_update_mapping+0x389/0x3f0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562793] ? amdgpu_vm_it_iter_first+0x40/0x40 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562863] amdgpu_vm_bo_update+0x325/0x5b0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562930] amdgpu_gem_va_ioctl+0x524/0x540 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562962] ? drm_gem_handle_create_tail+0x120/0x190 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563028] ? amdgpu_gem_create_ioctl+0xc1/0x270 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563096] ? amdgpu_gem_metadata_ioctl+0x1c0/0x1c0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563115] drm_ioctl_kernel+0x5f/0xb0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563134] ? drm_ioctl_kernel+0x5f/0xb0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563154] drm_ioctl+0x31b/0x3d0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563220] ? amdgpu_gem_metadata_ioctl+0x1c0/0x1c0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563225] ? update_load_avg+0x57f/0x6e0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563231] ? futex_wake+0x8f/0x180 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563290] amdgpu_drm_ioctl+0x4f/0x90 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563296] do_vfs_ioctl+0xa8/0x630 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563300] ? __schedule+0x29f/0x8b0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563304] SyS_ioctl+0x79/0x90 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563309] do_syscall_64+0x73/0x130 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563313] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563317] RIP: 0033:0x7fbd7ddcf5d7 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563319] RSP: 002b:7fff67e69aa8 EFLAGS: 3246 ORIG_RAX: 0010 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563322] RAX: ffda RBX: 0002 RCX: 7fbd7ddcf5d7 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563324] RDX: 7fff67e69af0 RSI: c0286448 RDI: 000e Jun 15 23:26:23 xa-xubu kernel: [ 2417.563326] RBP: 7fff67e69af0 R08: 00010144 R09: 000a Jun 15 23:26:23 xa-xubu kernel: [ 2417.563328] R10: 0039 R11: 3246 R12: c0286448 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563330] R13: 000e R14: 55e820965f20 R15: 0 which seems to point to some in-kernel AMD GPU driver. Since the problem seems to disappear when switching back to the previous kernel, I filed this as a kernel bug. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.13.0-43.48-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64
[Kernel-packages] [Bug 1777245] Re: stom
On Sat 16 Jun 2018 at 14:31:49 +0200, Guus en Anneke wrote: > Hoi Olaf, > eerst startte ik op met > Ubuntu met Linux 4.15.0-23 generic(recovery mode) > Ik kreeg een lange lijst met data. Toen herstelmenu, waarna rare dingen, > gekleurde strepen van letters. > > Opnieuw opgestart met > Ubuntu met Linux 4.13.0-43 generic > Gister ook met deze opgestart. Was nummer 3 in het lijstje en leek op nr 1. > vandaar dat ik vandaag met nr 2 op ging starten om te zien wat die deed.Niet > goed dus. > Ik heb een bug ingediend bij Ubuntu; je kan 'm nalezen op https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777245 Daarin staat ook dat je 7 dagen geleden een nieuwe XUbuntu-versie hebt geinstalleerd (van 17.10 naar 18.04)... daar had ik beter even bij kunnen meekijken! Ik heb dat namelijk op mijn laptop ook gedaan en dat was niet geheel zonder problemen... Ik heb ook de 4.13.0-43 standaard gemaakt voor het opstarten (hopelijk). Wanneer er een nieuwe versie uitkomt, moet je die eens proberen. Ik merk het hier vanzelf want mijn laptop heeft dus dezelfde Ubuntu-versie. Ik zal laten weten wanneer het zover is. Voor de 4.15.0-23-versie heb ik een opstart-optie toegevoegd die ik ergens tegenkwam. Iemand met soortgelijke problemen had er baat bij; als je tijd over hebt moet je maar eens die versie proberen (ik denk niet dat je verschil ziet in het menu) en zien of het helpt. Ik hoor graag wat het effekt is (sukses of niet), dan kan ik dat bij de bugmelding toevoegen. Groetjes, -Olaf. -- ___ Olaf 'Rhialto' Seibert -- Wayland: Those who don't understand X \X/ rhialto/at/falu.nl -- are condemned to reinvent it. Poorly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777245 Title: X freezes with kernel 4.15.0-23-generic (AMDGPU) Status in linux package in Ubuntu: Confirmed Bug description: This is on my parents machine; I only have remote access and not continuously, so this may slow down providing additional information. Since the latest kernel upgrade (from Linux version 4.13.0-43-generic (buildd@lgw01-amd64-026) (gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3.2)) #48-Ubuntu SMP Wed May 16 12:18:48 UTC 2018 (Ubuntu 4.13.0-43.48-generic 4.13.16) to Linux version 4.15.0-23-generic (buildd@lgw01-amd64-055) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 (Ubuntu 4.15.0-23.25-generic 4.15.18) the machine appears to freezes some time soon after booting. It is just X; the machine is still reachable via ssh. I filed this bug using apport-cli, running the older (working) kernel, not the newer (failing) one. In /var/log/kernel I can see the following: Jun 15 23:26:23 xa-xubu kernel: [ 2417.562386] INFO: task Xorg:757 blocked for more than 120 seconds. Jun 15 23:26:23 xa-xubu kernel: [ 2417.562396] Not tainted 4.15.0-23-generic #25-Ubuntu Jun 15 23:26:23 xa-xubu kernel: [ 2417.562399] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jun 15 23:26:23 xa-xubu kernel: [ 2417.562403] XorgD0 757 724 0x0044 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562408] Call Trace: Jun 15 23:26:23 xa-xubu kernel: [ 2417.562424] __schedule+0x297/0x8b0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562430] ? __kfifo_in+0x37/0x50 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562434] schedule+0x2c/0x80 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562559] amd_sched_entity_push_job+0xad/0xf0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562565] ? wait_woken+0x80/0x80 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562653] amdgpu_job_submit+0x9f/0xc0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562723] amdgpu_vm_bo_update_mapping+0x389/0x3f0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562793] ? amdgpu_vm_it_iter_first+0x40/0x40 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562863] amdgpu_vm_bo_update+0x325/0x5b0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562930] amdgpu_gem_va_ioctl+0x524/0x540 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562962] ? drm_gem_handle_create_tail+0x120/0x190 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563028] ? amdgpu_gem_create_ioctl+0xc1/0x270 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563096] ? amdgpu_gem_metadata_ioctl+0x1c0/0x1c0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563115] drm_ioctl_kernel+0x5f/0xb0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563134] ? drm_ioctl_kernel+0x5f/0xb0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563154] drm_ioctl+0x31b/0x3d0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563220] ? amdgpu_gem_metadata_ioctl+0x1c0/0x1c0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563225] ? update_load_avg+0x57f/0x6e0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563231] ? futex_wake+0x8f/0x180 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563290] amdgpu_drm_ioctl+0x4f/0x90 [amdgpu] Jun 15
[Kernel-packages] [Bug 1777245] Re: X freezes with kernel 4.15.0-23-generic (AMDGPU)
** Attachment added: "extract from kernel log for 4.15.0.23-generic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777245/+attachment/5153352/+files/dmesg-4.15.0-23-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777245 Title: X freezes with kernel 4.15.0-23-generic (AMDGPU) Status in linux package in Ubuntu: Confirmed Bug description: This is on my parents machine; I only have remote access and not continuously, so this may slow down providing additional information. Since the latest kernel upgrade (from Linux version 4.13.0-43-generic (buildd@lgw01-amd64-026) (gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3.2)) #48-Ubuntu SMP Wed May 16 12:18:48 UTC 2018 (Ubuntu 4.13.0-43.48-generic 4.13.16) to Linux version 4.15.0-23-generic (buildd@lgw01-amd64-055) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 (Ubuntu 4.15.0-23.25-generic 4.15.18) the machine appears to freezes some time soon after booting. It is just X; the machine is still reachable via ssh. I filed this bug using apport-cli, running the older (working) kernel, not the newer (failing) one. In /var/log/kernel I can see the following: Jun 15 23:26:23 xa-xubu kernel: [ 2417.562386] INFO: task Xorg:757 blocked for more than 120 seconds. Jun 15 23:26:23 xa-xubu kernel: [ 2417.562396] Not tainted 4.15.0-23-generic #25-Ubuntu Jun 15 23:26:23 xa-xubu kernel: [ 2417.562399] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jun 15 23:26:23 xa-xubu kernel: [ 2417.562403] XorgD0 757 724 0x0044 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562408] Call Trace: Jun 15 23:26:23 xa-xubu kernel: [ 2417.562424] __schedule+0x297/0x8b0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562430] ? __kfifo_in+0x37/0x50 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562434] schedule+0x2c/0x80 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562559] amd_sched_entity_push_job+0xad/0xf0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562565] ? wait_woken+0x80/0x80 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562653] amdgpu_job_submit+0x9f/0xc0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562723] amdgpu_vm_bo_update_mapping+0x389/0x3f0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562793] ? amdgpu_vm_it_iter_first+0x40/0x40 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562863] amdgpu_vm_bo_update+0x325/0x5b0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562930] amdgpu_gem_va_ioctl+0x524/0x540 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562962] ? drm_gem_handle_create_tail+0x120/0x190 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563028] ? amdgpu_gem_create_ioctl+0xc1/0x270 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563096] ? amdgpu_gem_metadata_ioctl+0x1c0/0x1c0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563115] drm_ioctl_kernel+0x5f/0xb0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563134] ? drm_ioctl_kernel+0x5f/0xb0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563154] drm_ioctl+0x31b/0x3d0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563220] ? amdgpu_gem_metadata_ioctl+0x1c0/0x1c0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563225] ? update_load_avg+0x57f/0x6e0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563231] ? futex_wake+0x8f/0x180 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563290] amdgpu_drm_ioctl+0x4f/0x90 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563296] do_vfs_ioctl+0xa8/0x630 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563300] ? __schedule+0x29f/0x8b0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563304] SyS_ioctl+0x79/0x90 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563309] do_syscall_64+0x73/0x130 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563313] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563317] RIP: 0033:0x7fbd7ddcf5d7 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563319] RSP: 002b:7fff67e69aa8 EFLAGS: 3246 ORIG_RAX: 0010 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563322] RAX: ffda RBX: 0002 RCX: 7fbd7ddcf5d7 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563324] RDX: 7fff67e69af0 RSI: c0286448 RDI: 000e Jun 15 23:26:23 xa-xubu kernel: [ 2417.563326] RBP: 7fff67e69af0 R08: 00010144 R09: 000a Jun 15 23:26:23 xa-xubu kernel: [ 2417.563328] R10: 0039 R11: 3246 R12: c0286448 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563330] R13: 000e R14: 55e820965f20 R15: 0 which seems to point to some in-kernel AMD GPU driver. Since the problem seems to disappear when switching back to the previous kernel, I filed this as a kernel bug. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu
[Kernel-packages] [Bug 1777245] Re: X freezes with kernel 4.15.0-23-generic (AMDGPU)
** Summary changed: - X freezes + X freezes with kernel 4.15.0-23-generic (AMDGPU) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777245 Title: X freezes with kernel 4.15.0-23-generic (AMDGPU) Status in linux package in Ubuntu: Confirmed Bug description: This is on my parents machine; I only have remote access and not continuously, so this may slow down providing additional information. Since the latest kernel upgrade (from Linux version 4.13.0-43-generic (buildd@lgw01-amd64-026) (gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3.2)) #48-Ubuntu SMP Wed May 16 12:18:48 UTC 2018 (Ubuntu 4.13.0-43.48-generic 4.13.16) to Linux version 4.15.0-23-generic (buildd@lgw01-amd64-055) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 (Ubuntu 4.15.0-23.25-generic 4.15.18) the machine appears to freezes some time soon after booting. It is just X; the machine is still reachable via ssh. I filed this bug using apport-cli, running the older (working) kernel, not the newer (failing) one. In /var/log/kernel I can see the following: Jun 15 23:26:23 xa-xubu kernel: [ 2417.562386] INFO: task Xorg:757 blocked for more than 120 seconds. Jun 15 23:26:23 xa-xubu kernel: [ 2417.562396] Not tainted 4.15.0-23-generic #25-Ubuntu Jun 15 23:26:23 xa-xubu kernel: [ 2417.562399] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jun 15 23:26:23 xa-xubu kernel: [ 2417.562403] XorgD0 757 724 0x0044 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562408] Call Trace: Jun 15 23:26:23 xa-xubu kernel: [ 2417.562424] __schedule+0x297/0x8b0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562430] ? __kfifo_in+0x37/0x50 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562434] schedule+0x2c/0x80 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562559] amd_sched_entity_push_job+0xad/0xf0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562565] ? wait_woken+0x80/0x80 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562653] amdgpu_job_submit+0x9f/0xc0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562723] amdgpu_vm_bo_update_mapping+0x389/0x3f0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562793] ? amdgpu_vm_it_iter_first+0x40/0x40 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562863] amdgpu_vm_bo_update+0x325/0x5b0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562930] amdgpu_gem_va_ioctl+0x524/0x540 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562962] ? drm_gem_handle_create_tail+0x120/0x190 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563028] ? amdgpu_gem_create_ioctl+0xc1/0x270 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563096] ? amdgpu_gem_metadata_ioctl+0x1c0/0x1c0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563115] drm_ioctl_kernel+0x5f/0xb0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563134] ? drm_ioctl_kernel+0x5f/0xb0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563154] drm_ioctl+0x31b/0x3d0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563220] ? amdgpu_gem_metadata_ioctl+0x1c0/0x1c0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563225] ? update_load_avg+0x57f/0x6e0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563231] ? futex_wake+0x8f/0x180 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563290] amdgpu_drm_ioctl+0x4f/0x90 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563296] do_vfs_ioctl+0xa8/0x630 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563300] ? __schedule+0x29f/0x8b0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563304] SyS_ioctl+0x79/0x90 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563309] do_syscall_64+0x73/0x130 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563313] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563317] RIP: 0033:0x7fbd7ddcf5d7 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563319] RSP: 002b:7fff67e69aa8 EFLAGS: 3246 ORIG_RAX: 0010 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563322] RAX: ffda RBX: 0002 RCX: 7fbd7ddcf5d7 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563324] RDX: 7fff67e69af0 RSI: c0286448 RDI: 000e Jun 15 23:26:23 xa-xubu kernel: [ 2417.563326] RBP: 7fff67e69af0 R08: 00010144 R09: 000a Jun 15 23:26:23 xa-xubu kernel: [ 2417.563328] R10: 0039 R11: 3246 R12: c0286448 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563330] R13: 000e R14: 55e820965f20 R15: 0 which seems to point to some in-kernel AMD GPU driver. Since the problem seems to disappear when switching back to the previous kernel, I filed this as a kernel bug. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.13.0-43.48-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2
[Kernel-packages] [Bug 1777245] Re: X freezes
** Description changed: This is on my parents machine; I only have remote access and not continuously, so this may slow down providing additional information. Since the latest kernel upgrade (from Linux version 4.13.0-43-generic (buildd@lgw01-amd64-026) (gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3.2)) #48-Ubuntu SMP Wed May 16 12:18:48 UTC 2018 (Ubuntu 4.13.0-43.48-generic 4.13.16) to Linux version 4.15.0-23-generic (buildd@lgw01-amd64-055) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 (Ubuntu 4.15.0-23.25-generic 4.15.18) the machine appears to freezes some time soon after booting. It is just X; the machine is still reachable via ssh. + + I filed this bug using apport-cli, running the older (working) kernel, + not the newer (failing) one. In /var/log/kernel I can see the following: Jun 15 23:26:23 xa-xubu kernel: [ 2417.562386] INFO: task Xorg:757 blocked for more than 120 seconds. Jun 15 23:26:23 xa-xubu kernel: [ 2417.562396] Not tainted 4.15.0-23-generic #25-Ubuntu Jun 15 23:26:23 xa-xubu kernel: [ 2417.562399] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jun 15 23:26:23 xa-xubu kernel: [ 2417.562403] XorgD0 757 724 0x0044 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562408] Call Trace: Jun 15 23:26:23 xa-xubu kernel: [ 2417.562424] __schedule+0x297/0x8b0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562430] ? __kfifo_in+0x37/0x50 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562434] schedule+0x2c/0x80 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562559] amd_sched_entity_push_job+0xad/0xf0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562565] ? wait_woken+0x80/0x80 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562653] amdgpu_job_submit+0x9f/0xc0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562723] amdgpu_vm_bo_update_mapping+0x389/0x3f0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562793] ? amdgpu_vm_it_iter_first+0x40/0x40 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562863] amdgpu_vm_bo_update+0x325/0x5b0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562930] amdgpu_gem_va_ioctl+0x524/0x540 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562962] ? drm_gem_handle_create_tail+0x120/0x190 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563028] ? amdgpu_gem_create_ioctl+0xc1/0x270 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563096] ? amdgpu_gem_metadata_ioctl+0x1c0/0x1c0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563115] drm_ioctl_kernel+0x5f/0xb0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563134] ? drm_ioctl_kernel+0x5f/0xb0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563154] drm_ioctl+0x31b/0x3d0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563220] ? amdgpu_gem_metadata_ioctl+0x1c0/0x1c0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563225] ? update_load_avg+0x57f/0x6e0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563231] ? futex_wake+0x8f/0x180 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563290] amdgpu_drm_ioctl+0x4f/0x90 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563296] do_vfs_ioctl+0xa8/0x630 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563300] ? __schedule+0x29f/0x8b0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563304] SyS_ioctl+0x79/0x90 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563309] do_syscall_64+0x73/0x130 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563313] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563317] RIP: 0033:0x7fbd7ddcf5d7 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563319] RSP: 002b:7fff67e69aa8 EFLAGS: 3246 ORIG_RAX: 0010 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563322] RAX: ffda RBX: 0002 RCX: 7fbd7ddcf5d7 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563324] RDX: 7fff67e69af0 RSI: c0286448 RDI: 000e Jun 15 23:26:23 xa-xubu kernel: [ 2417.563326] RBP: 7fff67e69af0 R08: 00010144 R09: 000a Jun 15 23:26:23 xa-xubu kernel: [ 2417.563328] R10: 0039 R11: 3246 R12: c0286448 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563330] R13: 000e R14: 55e820965f20 R15: 0 which seems to point to some in-kernel AMD GPU driver. Since the problem seems to disappear when switching back to the previous kernel, I filed this as a kernel bug. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.13.0-43.48-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rhialto 21222 F pulseaudio /dev/snd/controlC0: rhialto 21222 F pulseaudio Date: Sat Jun 16 16:03:46 2018 InstallationDate: Installed on 2017-10-29 (230 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" -
[Kernel-packages] [Bug 1777245] [NEW] X freezes
Public bug reported: This is on my parents machine; I only have remote access and not continuously, so this may slow down providing additional information. Since the latest kernel upgrade (from Linux version 4.13.0-43-generic (buildd@lgw01-amd64-026) (gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3.2)) #48-Ubuntu SMP Wed May 16 12:18:48 UTC 2018 (Ubuntu 4.13.0-43.48-generic 4.13.16) to Linux version 4.15.0-23-generic (buildd@lgw01-amd64-055) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 (Ubuntu 4.15.0-23.25-generic 4.15.18) the machine appears to freezes some time soon after booting. It is just X; the machine is still reachable via ssh. In /var/log/kernel I can see the following: Jun 15 23:26:23 xa-xubu kernel: [ 2417.562386] INFO: task Xorg:757 blocked for more than 120 seconds. Jun 15 23:26:23 xa-xubu kernel: [ 2417.562396] Not tainted 4.15.0-23-generic #25-Ubuntu Jun 15 23:26:23 xa-xubu kernel: [ 2417.562399] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jun 15 23:26:23 xa-xubu kernel: [ 2417.562403] XorgD0 757 724 0x0044 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562408] Call Trace: Jun 15 23:26:23 xa-xubu kernel: [ 2417.562424] __schedule+0x297/0x8b0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562430] ? __kfifo_in+0x37/0x50 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562434] schedule+0x2c/0x80 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562559] amd_sched_entity_push_job+0xad/0xf0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562565] ? wait_woken+0x80/0x80 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562653] amdgpu_job_submit+0x9f/0xc0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562723] amdgpu_vm_bo_update_mapping+0x389/0x3f0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562793] ? amdgpu_vm_it_iter_first+0x40/0x40 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562863] amdgpu_vm_bo_update+0x325/0x5b0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562930] amdgpu_gem_va_ioctl+0x524/0x540 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562962] ? drm_gem_handle_create_tail+0x120/0x190 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563028] ? amdgpu_gem_create_ioctl+0xc1/0x270 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563096] ? amdgpu_gem_metadata_ioctl+0x1c0/0x1c0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563115] drm_ioctl_kernel+0x5f/0xb0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563134] ? drm_ioctl_kernel+0x5f/0xb0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563154] drm_ioctl+0x31b/0x3d0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563220] ? amdgpu_gem_metadata_ioctl+0x1c0/0x1c0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563225] ? update_load_avg+0x57f/0x6e0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563231] ? futex_wake+0x8f/0x180 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563290] amdgpu_drm_ioctl+0x4f/0x90 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563296] do_vfs_ioctl+0xa8/0x630 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563300] ? __schedule+0x29f/0x8b0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563304] SyS_ioctl+0x79/0x90 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563309] do_syscall_64+0x73/0x130 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563313] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563317] RIP: 0033:0x7fbd7ddcf5d7 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563319] RSP: 002b:7fff67e69aa8 EFLAGS: 3246 ORIG_RAX: 0010 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563322] RAX: ffda RBX: 0002 RCX: 7fbd7ddcf5d7 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563324] RDX: 7fff67e69af0 RSI: c0286448 RDI: 000e Jun 15 23:26:23 xa-xubu kernel: [ 2417.563326] RBP: 7fff67e69af0 R08: 00010144 R09: 000a Jun 15 23:26:23 xa-xubu kernel: [ 2417.563328] R10: 0039 R11: 3246 R12: c0286448 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563330] R13: 000e R14: 55e820965f20 R15: 0 which seems to point to some in-kernel AMD GPU driver. Since the problem seems to disappear when switching back to the previous kernel, I filed this as a kernel bug. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.13.0-43.48-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rhialto 21222 F pulseaudio /dev/snd/controlC0: rhialto 21222 F pulseaudio Date: Sat Jun 16 16:03:46 2018 InstallationDate: Installed on 2017-10-29 (230 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: enp1s0no wireless extensions. lono wireless extensions. MachineType: LENOVO 90G9001RNY ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic.efi.signed
