December 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1190854] New: amdgpu fails to probe Radeon Pro WX3200
by bugzilla_noreply＠suse.com 01 Dec '21

01 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190854 Bug ID: 1190854 Summary: amdgpu fails to probe Radeon Pro WX3200 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: grasland(a)lal.in2p3.fr QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 852729 --> http://bugzilla.opensuse.org/attachment.cgi?id=852729&action=edit dmesg log, with ANSI color codes On a Dell Precision 3650 equipped with a Radeon Pro WX3200, something very wrong happens during the amdgpu initialization process (or perhaps before, see below), which makes the card unusable on Linux. Thus, I have to fall back to the CPU's built-in graphics for the time being on this machine. The GPU is brand new and works on both the UEFI setup screen and Windows, which suggests to me that the hardware is not completely broken. But of course, this does not fully exclude the possibility of a hardware issue that would only be triggered by the Linux initialization process. You will find attached the dmesg log, with and without ANSI color codes as I personally find dmesg' color output much easier to visually parse. --- Let's have a closer look at the amdgpu logs, since that's what I'm directly interested in here. First we get the standard stuff, nothing special here as far as I can see. The CRAT table bit does looks suspicious, but it also happens during the init of my home Radeon RX 560 that otherwise works fine under Linux, so this does not seem to be a fatal issue... 771 �� [ 3.484654] [drm] amdgpu kernel modesetting enabled. 772 �� [ 3.484700] amdgpu: CRAT table not found 773 �� [ 3.484701] amdgpu: Virtual CRAT table created for CPU 774 �� [ 3.484707] amdgpu: Topology: Add CPU node ...then we get a power management failure, which may or may not be related to the problem at hand... 775 �� [ 3.484764] amdgpu 0000:01:00.0: can't change power state from D3hot to D0 (config space inaccessible) ...then more "normal" stuff, in the sense of stuff that looks close to what I see in the init logs of amdgpu on my RX 560... 776 �� [ 3.484888] [drm] initializing kernel modesetting (POLARIS12 0x1002:0x6981 0x1028:0x2B0D 0x10). 777 �� [ 3.484890] amdgpu 0000:01:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported 778 �� [ 3.484895] [drm] register mmio base: 0x6E900000 779 �� [ 3.484896] [drm] register mmio size: 262144 780 �� [ 3.484898] [drm] add ip block number 0 <vi_common> 781 �� [ 3.484899] [drm] add ip block number 1 <gmc_v8_0> 782 �� [ 3.484899] [drm] add ip block number 2 <tonga_ih> 783 �� [ 3.484900] [drm] add ip block number 3 <gfx_v8_0> 784 �� [ 3.484900] [drm] add ip block number 4 <sdma_v3_0> 785 �� [ 3.484901] [drm] add ip block number 5 <powerplay> 786 �� [ 3.484901] [drm] add ip block number 6 <dm> 787 �� [ 3.484902] [drm] add ip block number 7 <uvd_v6_0> 788 �� [ 3.484902] [drm] add ip block number 8 <vce_v3_0> 789 �� [ 3.484913] amdgpu 0000:01:00.0: amdgpu: Fetched VBIOS from VFCT 790 �� [ 3.484914] amdgpu: ATOM BIOS: 113-D0155200-100 791 �� [ 3.484932] [drm] vm size is 256 GB, 2 levels, block size is 10-bit, fragment size is 9-bit ...however, after this the driver tries to set up MMIO to communicate with the device, and here is where I think things go very wrong. 792 �� [ 3.485705] amdgpu 0000:01:00.0: BAR 2: releasing [mem 0x6100000000-0x61001fffff 64bit pref] 793 �� [ 3.485708] amdgpu 0000:01:00.0: BAR 0: releasing [mem 0x6000000000-0x60ffffffff 64bit pref] 794 �� [ 3.485709] [drm:amdgpu_device_resize_fb_bar [amdgpu]] *ERROR* Problem resizing BAR0 (-16). 795 �� [ 3.485811] amdgpu 0000:01:00.0: BAR 0: assigned [mem 0x6000000000-0x60ffffffff 64bit pref] 796 �� [ 3.485831] amdgpu 0000:01:00.0: BAR 0: error updating (0x00000c != 0xffffffff) 797 �� [ 3.485847] amdgpu 0000:01:00.0: BAR 0: error updating (high 0x000060 != 0xffffffff) 798 �� [ 3.485863] amdgpu 0000:01:00.0: BAR 2: assigned [mem 0x6100000000-0x61001fffff 64bit pref] 799 �� [ 3.485864] amdgpu 0000:01:00.0: BAR 2: error updating (0x00000c != 0xffffffff) 800 �� [ 3.485880] amdgpu 0000:01:00.0: BAR 2: error updating (high 0x000061 != 0xffffffff) 801 �� [ 3.485901] amdgpu 0000:01:00.0: amdgpu: VRAM: 4294967295M 0x000000FFFF000000 - 0x001000FFFEEFFFFF (4294967295M used) 802 �� [ 3.485903] amdgpu 0000:01:00.0: amdgpu: GART: 256M 0x0000000000000000 - 0x000000000FFFFFFF 803 �� [ 3.485905] [drm] Detected VRAM RAM=4294967295M, BAR=4096M 804 �� [ 3.485906] [drm] RAM width 64bits UNKNOWN 805 �� [ 3.485913] [drm] amdgpu: 4294967295M of VRAM memory ready 806 �� [ 3.485914] [drm] amdgpu: 48026M of GTT memory ready. 807 �� [ 3.485916] [drm] GART: num cpu pages 65536, num gpu pages 65536 Failing to set up PCI BARs sounds bad, and concluding from this failed setup process that the GPU has 4 PiB of VRAM sounds even worse. I wouldn't be surprised if this were the point where things really went hopeless. But amdgpu is not the kind of program that will stop cleanly when the first error occurs, so it will first wait for an event that doesn't want to happen... 808 �� [ 3.600399] amdgpu 0000:01:00.0: amdgpu: Wait for MC idle timedout ! [...] 813 �� [ 3.714578] amdgpu 0000:01:00.0: amdgpu: Wait for MC idle timedout ! ...then emits a few more messages that also appear during the successful initialization process of my home RX 560, so which I consider "normal"... 814 �� [ 3.715166] [drm] PCIE GART of 256M enabled (table at 0x000000FFFF900000). 815 �� [ 3.716221] [drm] Chained IB support enabled! 816 �� [ 3.721721] amdgpu: hwmgr_sw_init smu backed is polaris10_smu ...and only then it dies brutally. 817 �� [ 3.726521] amdgpu: 818 �� last message was failed ret is 65535 819 �� [ 3.726522] amdgpu: 820 �� failed to send message 100 ret is 65535 821 �� [ 3.726525] amdgpu: SMC address must be 4 byte aligned. 822 �� [ 3.726525] amdgpu: [AVFS][Polaris10_SetupGfxLvlStruct] Problems copying VRConfig value over to SMC 823 �� [ 3.726526] amdgpu: [AVFS][Polaris10_AVFSEventMgr] Could not Copy Graphics Level table over to SMU 824 �� [ 3.726565] amdgpu: 825 �� last message was failed ret is 65535 826 �� [ 3.726566] amdgpu: 827 �� failed to send message 252 ret is 65535 828 �� [ 3.726566] amdgpu: 829 �� last message was failed ret is 65535 830 �� [ 3.726567] amdgpu: 831 �� failed to send message 253 ret is 65535 832 �� [ 3.726569] amdgpu: 833 �� last message was failed ret is 65535 834 �� [ 3.726570] amdgpu: 835 �� failed to send message 250 ret is 65535 836 �� [ 3.726571] amdgpu: 837 �� last message was failed ret is 65535 838 �� [ 3.726571] amdgpu: 839 �� failed to send message 251 ret is 65535 840 �� [ 3.726572] amdgpu: 841 �� last message was failed ret is 65535 842 �� [ 3.726573] amdgpu: 843 �� failed to send message 254 ret is 65535 844 �� [ 3.861852] [drm] Timeout wait for RLC serdes 0,0 [...] 846 �� [ 3.975981] amdgpu 0000:01:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring gfx test failed (-110) 847 �� [ 3.976112] [drm:amdgpu_device_init.cold [amdgpu]] *ERROR* hw_init of IP block <gfx_v8_0> failed -110 848 �� [ 3.976241] amdgpu 0000:01:00.0: amdgpu: amdgpu_device_ip_init failed 849 �� [ 3.976242] amdgpu 0000:01:00.0: amdgpu: Fatal error during GPU init 850 �� [ 3.976244] amdgpu 0000:01:00.0: amdgpu: amdgpu: finishing device. 851 �� [ 3.977567] amdgpu: probe of 0000:01:00.0 failed with error -110 852 �� [ 3.977650] [drm] amdgpu: ttm finalized --- So, to summarize, it seems something goes wrong at the MMIO setup stage, which may or may not be related to an earlier power management failure. My question is, how can I investigate this further? Here's some random trial and error stuff I already tried to no avail: - Upgrade the UEFI firmware. It's now at the latest release, and it did not change a thing. - Attempt to disable ASPM in case PCIe power management could be the issue (I found reports of an ASPM-related nvidia driver crash that started with the same ACPI error message at the beginning). Does not change anything here, rolled back. - Attempt to downgrade to an earlier amdgpu firmware, as this fixed a similar-looking crash on Arch. Did not help here, went back to the current AMD firmware. - Attempt to set the AMD GPU as the primary GPU in UEFI. This does not fix amdgpu initialization, and it breaks i915 initialization, which is definitely worse. Rolled back. -- You are receiving this mail because: You are the assignee for the bug.

1 12

[Bug 1193142] usb mouse and usb keyboard not recognized by sddm
by bugzilla_noreply＠suse.com 01 Dec '21

01 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1193142 https://bugzilla.suse.com/show_bug.cgi?id=1193142#c7 --- Comment #7 from Takashi Iwai <tiwai(a)suse.com> --- Is it connected over USB type-C dock? If yes, could you try to connect to the built-in port and check whether it's recognized? Currently we have some issues about some type-C connected devices with 5.15.x kernel, and this might be one of them. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192714] [Build 20211114] podman tests triggering gpf in kernel 5.15.1
by bugzilla_noreply＠suse.com 01 Dec '21

01 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1192714 https://bugzilla.suse.com/show_bug.cgi?id=1192714#c29 --- Comment #29 from Jan Kara <jack(a)suse.com> --- Cool, I will add your tested-by tag and submit the patch upstream for inclusion. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193286] New: Kernel panic after waking up laptop from sleep
by bugzilla_noreply＠suse.com 01 Dec '21

01 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1193286 Bug ID: 1193286 Summary: Kernel panic after waking up laptop from sleep Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: openSUSE Leap 15.3 Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: krystof186(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After putting my laptop to sleep from KDE, the system sleeps normally. However, after I reboot, the system works for usually 10-20 seconds and then, the kernel panics. I am suspicious that this might be an issue with swapfile, but I am not sure. Below is the output from the kernel dump browsed via the crash command: KERNEL: /boot/vmlinux-5.3.18-59.34-default.gz DEBUGINFO: /usr/lib/debug/boot/vmlinux-5.3.18-59.34-default.debug DUMPFILE: vmcore [PARTIAL DUMP] CPUS: 8 DATE: Wed Dec 1 12:46:47 CET 2021 UPTIME: 04:05:29 LOAD AVERAGE: 2.09, 1.84, 2.16 TASKS: 1396 NODENAME: krelnb RELEASE: 5.3.18-59.34-default VERSION: #1 SMP Thu Nov 11 12:18:45 UTC 2021 (a2a53aa) MACHINE: x86_64 (1800 Mhz) MEMORY: 11.7 GB PANIC: "Oops: 0010 [#1] SMP PTI" (check log for details) PID: 0 COMMAND: "swapper/5" TASK: ffff8fe8c76b2700 (1 of 8) [THREAD_INFO: ffff8fe8c76b2700] CPU: 5 STATE: TASK_RUNNING (PANIC) Backtrace: PID: 0 TASK: ffff8fe8c76b2700 CPU: 5 COMMAND: "swapper/5" #0 [ffffb94c40208c00] machine_kexec at ffffffffa286fb71 #1 [ffffb94c40208c58] __crash_kexec at ffffffffa295928d #2 [ffffb94c40208d20] crash_kexec at ffffffffa295a14d #3 [ffffb94c40208d38] oops_end at ffffffffa2836cef #4 [ffffb94c40208d58] no_context at ffffffffa2882bbf #5 [ffffb94c40208dc0] do_page_fault at ffffffffa2883e40 #6 [ffffb94c40208df0] page_fault at ffffffffa32012fe [exception RIP: unknown or invalid address] RIP: 0000000000000000 RSP: ffffb94c40208ea0 RFLAGS: 00010206 RAX: 0000000000000000 RBX: 0000000000000100 RCX: ffff8feb2055d780 RDX: 0000000100370af8 RSI: 0000000000000000 RDI: ffff8feac42df738 RBP: ffffb94c40208ee8 R8: ffff8feb2055d7a8 R9: ffffb94c40208ef0 R10: 0000000000000001 R11: 0000000000000000 R12: ffff8feac42df738 R13: 0000000000000000 R14: 0000000000000001 R15: ffff8feac42df738 ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0018 #7 [ffffb94c40208ea0] call_timer_fn at ffffffffa29338bd #8 [ffffb94c40208ed0] run_timer_softirq at ffffffffa293478a #9 [ffffb94c40208f68] __softirqentry_text_start at ffffffffa34000e3 #10 [ffffb94c40208fc8] irq_exit at ffffffffa28a3d45 #11 [ffffb94c40208fd8] smp_apic_timer_interrupt at ffffffffa3202874 #12 [ffffb94c40208ff0] apic_timer_interrupt at ffffffffa3201d9f --- <IRQ stack> --- #13 [ffffb94c400ebdd8] apic_timer_interrupt at ffffffffa3201d9f [exception RIP: cpuidle_enter_state+171] RIP: ffffffffa2efdbeb RSP: ffffb94c400ebe80 RFLAGS: 00000246 RAX: ffff8feb2056cc80 RBX: ffff8feb20577600 RCX: 000000000000001f RDX: 00000d652d6a0b3b RSI: 00000000471c745e RDI: 0000000000000000 RBP: ffffffffa3d5f140 R8: 0000000000000002 R9: 000000000002c500 R10: ffffb94c400ebe60 R11: 0000000000000026 R12: 0000000000000001 R13: 00000d652d6a0b3b R14: 0000000000000001 R15: 0000000000000000 ORIG_RAX: ffffffffffffff13 CS: 0010 SS: 0018 #14 [ffffb94c400ebec0] cpuidle_enter at ffffffffa2efdfb9 #15 [ffffb94c400ebee0] do_idle at ffffffffa28d5637 #16 [ffffb94c400ebf20] cpu_startup_entry at ffffffffa28d5839 #17 [ffffb94c400ebf30] start_secondary at ffffffffa2864f95 #18 [ffffb94c400ebf50] secondary_startup_64_no_verify at ffffffffa2800112 Interesting lines from log: [14714.661283] Bluetooth: hci0: unexpected event for opcode 0xfc2f [14714.679333] Bluetooth: hci0: Intel BT fw patch 0x32 completed & activated [14715.278768] scsi 2:0:0:0: Direct-Access Generic- SD/MMC/MS PRO 1.00 PQ: 0 ANSI: 4 [14715.279009] scsi 2:0:0:0: Attached scsi generic sg1 type 0 [14722.563749] sd 2:0:0:0: [sdb] Attached SCSI removable disk [14726.190059] usb 1-6: USB disconnect, device number 13 [14726.196837] scsi 2:0:0:0: rejecting I/O to dead device [14728.204792] BUG: kernel NULL pointer dereference, address: 0000000000000000 [14728.204796] #PF: supervisor instruction fetch in kernel mode [14728.204798] #PF: error_code(0x0010) - not-present page [14728.204799] PGD 80000001af060067 P4D 80000001af060067 PUD 0 [14728.204802] Oops: 0010 [#1] SMP PTI [14728.204804] CPU: 5 PID: 0 Comm: swapper/5 Kdump: loaded Tainted: P O X N 5.3.18-59.34-default #1 SLE15-SP3 [14728.204806] Hardware name: Dell Inc. Inspiron 7773/0MDTWJ, BIOS 1.13.0 03/05/2020 [14728.204811] RIP: 0010:0x0 [14728.204814] Code: Bad RIP value. [14728.204816] RSP: 0018:ffffb94c40208ea0 EFLAGS: 00010206 [14728.204818] RAX: 0000000000000000 RBX: 0000000000000100 RCX: ffff8feb2055d780 [14728.204820] RDX: 0000000100370af8 RSI: 0000000000000000 RDI: ffff8feac42df738 [14728.204822] RBP: ffffb94c40208ee8 R08: ffff8feb2055d7a8 R09: ffffb94c40208ef0 [14728.204824] R10: 0000000000000001 R11: 0000000000000000 R12: ffff8feac42df738 [14728.204826] R13: 0000000000000000 R14: 0000000000000001 R15: ffff8feac42df738 [14728.204828] FS: 0000000000000000(0000) GS:ffff8feb20540000(0000) knlGS:0000000000000000 [14728.204830] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [14728.204832] CR2: ffffffffffffffd6 CR3: 00000001b158e001 CR4: 00000000003706e0 [14728.204833] Call Trace: [14728.204835] <IRQ> [14728.204839] call_timer_fn+0x2d/0x130 [14728.204842] run_timer_softirq+0x40a/0x440 [14728.204845] ? enqueue_hrtimer+0x39/0x90 [14728.204849] __do_softirq+0xe3/0x2d6 [14728.204852] irq_exit+0xd5/0xe0 [14728.204855] smp_apic_timer_interrupt+0x74/0x130 [14728.204858] apic_timer_interrupt+0xf/0x20 [14728.204860] </IRQ> [14728.204863] RIP: 0010:cpuidle_enter_state+0xab/0x430 [14728.204865] Code: 9b 47 11 5d e8 c6 67 9d ff 49 89 c5 0f 1f 44 00 00 31 ff e8 b7 77 9d ff 80 7c 24 0b 00 0f 85 db 01 00 00 fb 66 0f 1f 44 00 00 <45> 85 e4 0f 89 f4 01 00 00 c7 43 14 00 00 00 00 48 83 c4 10 44 89 [14728.204868] RSP: 0018:ffffb94c400ebe80 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff13 [14728.204870] RAX: ffff8feb2056cc80 RBX: ffff8feb20577600 RCX: 000000000000001f [14728.204872] RDX: 00000d652d6a0b3b RSI: 00000000471c745e RDI: 0000000000000000 [14728.204874] RBP: ffffffffa3d5f140 R08: 0000000000000002 R09: 000000000002c500 [14728.204876] R10: ffffb94c400ebe60 R11: 0000000000000026 R12: 0000000000000001 [14728.204878] R13: 00000d652d6a0b3b R14: 0000000000000001 R15: 0000000000000000 [14728.204882] cpuidle_enter+0x29/0x40 [14728.204885] do_idle+0x1f7/0x270 [14728.204887] cpu_startup_entry+0x19/0x20 [14728.204890] start_secondary+0x155/0x1a0 [14728.204893] secondary_startup_64_no_verify+0xc2/0xd0 [14728.204987] CR2: 0000000000000000 I have secureboot enabled, no modifications to the hardware were made, overclocking is disabled. The system works normally after boot, but I can't put it to sleep - I have to shut it down completely, which is not only annoying, but also time consuming. I will gladly help as much as I can to solve this issue. Laptop: Dell Inspiron 17 (7773) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192714] [Build 20211114] podman tests triggering gpf in kernel 5.15.1
by bugzilla_noreply＠suse.com 01 Dec '21

01 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1192714 https://bugzilla.suse.com/show_bug.cgi?id=1192714#c28 --- Comment #28 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Jan Kara from comment #27) > Created attachment 854199 [details] > [PATCH] bfq: Fix use-after-free with cgroups > > Fabian, can you please try this patch, whether it fixes the KASAN splats you > are getting? Thanks! Appears to work! No KASAN splats after >1.7h of runtime. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192874] During OS booting, the loading installation system progress is very slow with Intel Alder Lake nonVpro system.
by bugzilla_noreply＠suse.com 01 Dec '21

01 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192874 http://bugzilla.opensuse.org/show_bug.cgi?id=1192874#c19 --- Comment #19 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Lin Ellen from comment #18) > May we have a trial version to check at our side? Thank you! The build from the latest git branch (kernel-of-the-day, KOTD) is found in OBS Kernel:SLE15-SP3 repo, http://download.opensuse.org/repositories/Kernel:/SLE15-SP3/pool/ If you have an already installed system, please give it a try. Note that it's an unofficial build, hence it won't boot with Secure Boot. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193124] tumbleweed release 20211124 with kernel 5.15.3 bluetooth fail
by bugzilla_noreply＠suse.com 01 Dec '21

01 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1193124 https://bugzilla.suse.com/show_bug.cgi?id=1193124#c30 --- Comment #30 from Takashi Iwai <tiwai(a)suse.com> --- I built a test kernel with the revert of changes in btintel.c. It's found in OBS home:tiwai:bsc1193124 repo http://download.opensuse.org/repositories/home:/tiwai:/bsc1193124/standard/ Could you verify whether this works again or not? -- You are receiving this mail because: You are the assignee for the bug.

1 0