January 2025 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1235020] Hard freeze workqueue lockup mediatek bluetooth
by bugzilla_noreply＠suse.com 10 Jan '25

10 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1235020 https://bugzilla.suse.com/show_bug.cgi?id=1235020#c17 --- Comment #17 from Andrea Ippolito <andrea.ippo(a)gmail.com> --- Ok I'm finally there :) ❯ uname -r 6.12.8-1.g33b034c-default Let's see how it goes, I'll report back. Packages from this repo have served me well, with no lockups for the few days I've been running them: https://download.opensuse.org/repositories/Kernel:/stable/standard/ -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1235020] Hard freeze workqueue lockup mediatek bluetooth
by bugzilla_noreply＠suse.com 10 Jan '25

10 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1235020 https://bugzilla.suse.com/show_bug.cgi?id=1235020#c16 --- Comment #16 from Andrea Ippolito <andrea.ippo(a)gmail.com> --- Ok I think I figured out what the problem was. The kernel was there, I just had to choose to boot that one from the advanced boot menu. For some reason it's not bumped back into first position/default boot kernel, probably because my install --force was just reinstalling an already installed kernel version, and therefore no need to update grub was detected. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1235020] Hard freeze workqueue lockup mediatek bluetooth
by bugzilla_noreply＠suse.com 10 Jan '25

10 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1235020 https://bugzilla.suse.com/show_bug.cgi?id=1235020#c15 --- Comment #15 from Andrea Ippolito <andrea.ippo(a)gmail.com> --- Nevermind, I'm still stuck on this one: ❯ uname -r 6.12.8-6.ge4ae43b-default While the command I posted earlier seems to install the package from the other repo, once I reboot I'm running the same kernel still. So I think that while the kernel from the Main Repository (OSS) installs, it's not the one that's booted. I suppose I have to use some allow-vendor-change flag? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1235020] Hard freeze workqueue lockup mediatek bluetooth
by bugzilla_noreply＠suse.com 10 Jan '25

10 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1235020 https://bugzilla.suse.com/show_bug.cgi?id=1235020#c14 --- Comment #14 from Andrea Ippolito <andrea.ippo(a)gmail.com> --- hmm seems like something like this is working: sudo zypper install --repo 3 --force kernel-default 3 is the index of the default repo - I'll just roll back to that one before readding you repo and reinstalling from there - this is a bit of a delicate operation for me ^_^ -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1235020] Hard freeze workqueue lockup mediatek bluetooth
by bugzilla_noreply＠suse.com 10 Jan '25

10 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1235020 https://bugzilla.suse.com/show_bug.cgi?id=1235020#c13 --- Comment #13 from Andrea Ippolito <andrea.ippo(a)gmail.com> --- Hi Takashi, sorry to bother, but I think I got in a strange situation. I thought I was running the kernel from your latest repo, but I'm not sure about that anymore: ❯ uname -r 6.12.8-6.ge4ae43b-default I still had the first suggested repo in my list: https://download.opensuse.org/repositories/Kernel:/stable/standard/ And I added https://download.opensuse.org/repositories/home:/tiwai:/bsc1235020/standard/ on top - but I guess I never installed/updated anything from this one. Now I'm back to this situation: ❯ sudo zypper repos [sudo] password for root: Repository priorities in effect: (See 'zypper lr -P' for details) 70 (raised priority) : 1 repository 99 (default priority) : 6 repositories # | Alias | Name | Enabled | GPG Check | Refresh --+----------------------------------+----------------------------------------+---------+-----------+-------- 1 | Insync | Insync | Yes | (r ) Yes | Yes 2 | download.opensuse.org-non-oss | Main Repository (NON-OSS) | Yes | (r ) Yes | Yes 3 | download.opensuse.org-oss | Main Repository (OSS) | Yes | (r ) Yes | Yes 4 | download.opensuse.org-tumbleweed | Main Update Repository | Yes | (r ) Yes | Yes 5 | home_pzz | home:pzz (openSUSE_Tumbleweed) | Yes | (r ) Yes | Yes 6 | packman | Packman | Yes | (r ) Yes | Yes 7 | repo-debug | openSUSE-Tumbleweed-Debug | No | ---- | ---- 8 | repo-openh264 | Open H.264 Codec (openSUSE Tumbleweed) | Yes | (r ) Yes | Yes 9 | repo-source | openSUSE-Tumbleweed-Source | No | ---- | ---- And yet when I try to update (after a zypper refresh), no update is proposed (I was expecting to be brought back to the tumbleweed "channel"): ❯ sudo zypper update kernel-default Loading repository data... Reading installed packages... No update candidate for 'kernel-default-6.12.8-6.1.ge4ae43b.x86_64'. The highest available version is already installed. Once I'm back on the tw channel, the idea was to add your last repo once again and update again. Super convoluted I know, there must be a way to specify which repo you wanna install from, but --from also didn't work -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1235020] New: Hard freeze workqueue lockup mediatek bluetooth
by bugzilla_noreply＠suse.com 10 Jan '25

10 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1235020 Bug ID: 1235020 Summary: Hard freeze workqueue lockup mediatek bluetooth Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: andrea.ippo(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi, I've been experiencing random lockups on TW for a while now (more than a month): https://community.frame.work/t/workqueue-lockup-opensuse-tw/60430 (I'm the OP here) https://forums.opensuse.org/t/workqueue-lockup-should-i-file-a-bug/180387 I had to switch to Fedora for the past couple of weeks, and surprisingly I never experienced this issue there, which makes me think it might be related to the opensuse kernel (or maybe, just bad luck on TW). The problem seems to be related to bluetooth, as we can see by checking at the logs at the timestamp preceding the BUG - lockup entry by X seconds as specified in the error: Examples: https://pastebin.com/79dj1PeX https://pastebin.com/n3m1S8B7 In both cases if we go back by 58s we get around this part: Jan 02 18:19:33 andromeda kernel: Bluetooth: hci0: Execution of wmt command timed out Jan 02 18:19:33 andromeda kernel: Bluetooth: hci0: Failed to send wmt patch dwnld (-110) Jan 02 18:19:33 andromeda kernel: Bluetooth: hci0: Failed to set up firmware (-110) Jan 02 18:19:33 andromeda kernel: Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported. Jan 02 18:19:35 andromeda kernel: Bluetooth: hci0: Failed to read MSFT supported features (-110) Jan 02 18:19:35 andromeda kernel: Bluetooth: hci0: command 0xfd30 tx timeout Jan 02 18:19:35 andromeda kernel: Bluetooth: hci0: AOSP get vendor capabilities (-110) Jan 02 18:19:35 andromeda bluetoothd[1147]: Failed to set mode: Authentication Failed (0x05) When this happens, my entire DE becomes unresponsive, even systemctl reboot won't work and I'm forced to hard power off. I'm running 6.12.6-1-default Thanks -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1235540] workqueue: Failed to create a worker thread: -ENOMEM
by bugzilla_noreply＠suse.com 10 Jan '25

10 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1235540 https://bugzilla.suse.com/show_bug.cgi?id=1235540#c3 --- Comment #3 from Paul Graff <pj.opensuse(a)gmx.com> --- (In reply to Jiri Slaby from comment #2) > (In reply to Paul Graff from comment #1) > > Created attachment 879507 [details] > > Additional Call Trace information: > > Ugh: > > workqueue: WQ_MEM_RECLAIM uvd:drm_sched_run_job_work [gpu_sched] is flushing !WQ_MEM_RECLAIM events:amdgpu_uvd_idle_work_handler [amdgpu] > > This is a separate bug in amdgpu: > > cancel_delayed_work_sync+0x5e/0x80 > > amdgpu_uvd_ring_begin_use+0x28/0x90 [amdgpu f31b185a6e1dd5c59d7aab35cf9d884fb32124c1] > > This cancels a work from a system_wq which has WQ_MEM_RECLAIM NOT set. > > > amdgpu_ring_alloc+0x40/0x60 [amdgpu f31b185a6e1dd5c59d7aab35cf9d884fb32124c1] > > amdgpu_ib_schedule+0xe8/0x720 [amdgpu f31b185a6e1dd5c59d7aab35cf9d884fb32124c1] > > amdgpu_job_run+0x8e/0x1f0 [amdgpu f31b185a6e1dd5c59d7aab35cf9d884fb32124c1] > > drm_sched_run_job_work+0x238/0x3d0 [gpu_sched 726175b79829de481a9ab4c293fcdba5a844519e] > > This one is running on sched->submit_wq which has WQ_MEM_RECLAIM set (by > drm_sched_init()). > > This is not allowed. > > > process_one_work+0x168/0x320 > > Could you report this (with your backtrace and this comment) at: > https://gitlab.freedesktop.org/drm/amd/-/issues > as this is clearly an amdgpu/drm bug? Hi, thanks for insight on this "Additional Call Trace Information". I created a bug report here :< https://gitlab.freedesktop.org/drm/amd/-/issues/3891 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1234623] DPC: RP PIO log size 0 is invalid (quirk needs to be added)
by bugzilla_noreply＠suse.com 10 Jan '25

10 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234623 https://bugzilla.suse.com/show_bug.cgi?id=1234623#c14 --- Comment #14 from Bjørn Lie <bjorn.lie(a)gmail.com> --- (In reply to Takashi Iwai from comment #13) > OK, I'll follow up the mail thread. BTW I did boot into Windows again just to doublecheck that no new bios was "available", but nope - No bios update for me. Extra info: I have updated the bios since the laptop was new, so meh... - Lazy Asus it seems :-) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1234623] DPC: RP PIO log size 0 is invalid (quirk needs to be added)
by bugzilla_noreply＠suse.com 10 Jan '25

10 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234623 https://bugzilla.suse.com/show_bug.cgi?id=1234623#c13 --- Comment #13 from Takashi Iwai <tiwai(a)suse.com> --- OK, I'll follow up the mail thread. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1234623] DPC: RP PIO log size 0 is invalid (quirk needs to be added)
by bugzilla_noreply＠suse.com 10 Jan '25

10 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234623 https://bugzilla.suse.com/show_bug.cgi?id=1234623#c12 --- Comment #12 from Bjørn Lie <bjorn.lie(a)gmail.com> --- (In reply to Takashi Iwai from comment #11) > What I wanted to verify is that the kernel WARNING still appears even with > the latest BIOS when the PCI quirk patch isn't applied. That is, the > statement from Intel doesn't apply to reality. Is this so? That is correct. As intel said "it might not have ended up in OEM bios yet" Aka it is only fixed on their refrence hardware/bios. -- You are receiving this mail because: You are the assignee for the bug.

1 0