December 2022 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1206681] New: Massive btrfs errors
by bugzilla_noreply＠suse.com 15 Jan '23

15 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206681 Bug ID: 1206681 Summary: Massive btrfs errors Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: jshand2013(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Made an update with 22/12/2022. I have included dmesg and journalctl logs to show what happens -- You are receiving this mail because: You are the assignee for the bug.

1 11

[Bug 1206408] New: Kernel panic after upgrading from to kernel 6.0.10 (or 6.0.12) from 6.0.8
by bugzilla_noreply＠suse.com 08 Jan '23

08 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206408 Bug ID: 1206408 Summary: Kernel panic after upgrading from to kernel 6.0.10 (or 6.0.12) from 6.0.8 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: rainer.klute(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After upgrading from kernel 6.0.8 to 6.0.10, the system no longer boots. Instead, it stops relatively early in the boot process with the shift lock LED blinking. No error message is shown on the screen. The last message it shows is regarding the IBM trackpoint device on my Lenovo Thinkpad P50 notebook. Same behaviour with kernel 6.0.12. Luckily, I can still boot the 6.0.8 kernel, but I am stuck with that on this particular machine. -- You are receiving this mail because: You are the assignee for the bug.

1 13

[Bug 1206451] New: wlan device QCNFA765 not detected
by bugzilla_noreply＠suse.com 04 Jan '23

04 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206451 Bug ID: 1206451 Summary: wlan device QCNFA765 not detected Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: cgoll(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The wireless network adapter Qualcomm QCNFA765 is not detected with the actual leap kernel. As workaround I am using the kernel from kernel:stable:backport (kernel-default-6.1.0-lp153.2.1.gc3232e1.x86_64) -- You are receiving this mail because: You are the assignee for the bug.

1 11

[Bug 1206683] New: kernel-default 6.1.0-1.1 freezes up 2 different machines
by bugzilla_noreply＠suse.com 01 Jan '23

01 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206683 Bug ID: 1206683 Summary: kernel-default 6.1.0-1.1 freezes up 2 different machines Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: scott.bradnick(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I have 2 systems: 1) Intel Celeron J4115 and Intel GeminiLake [UHD Graphics 600] (driver: i915) 2) Intel Core i7-9850H and Intel CoffeeLake-H GT2 [UHD Graphics 630] along with NVIDIA TU117GLM [Quadro T1000 Mobile] #1 boots to a lightdm login but within 30s-1m of logging in, locks up completely with whatever was last on the screen frozen there and the mouse cursor missing. I'm not sure if it'd just lock up w/o me logging in - I'll try that next time. #2 seems to go through 99% of its boot process, then just as it would kick over to lightdm, it doesn't do anything but freeze up w/ something in the history of the boot process (what looks like dmesg output, the format at least). It boots w/ "splash=silent" and "quiet" REMOVED. #2 generally runs off NVIDIA's latest .run and all was fine prior, I could attempt to possibly use prime-select when booted to the previous kernel and use the iGPU to see if it freezes similarly to #1, but I haven't gotten too adventurous yet. Both work just fine on 6.0.12-1.1 and while I'm kicking around the idea of getting 6.1.1 from https://build.opensuse.org/package/show/Kernel:stable/kernel-default I haven't delved into that either. I'm happy to provide logs and more info, not sure if the freezing/hard lockups will make that impossible. -- You are receiving this mail because: You are the assignee for the bug.

1 42

[Bug 1206697] New: Wireless network disappears on Raspberry Pi 4B after kernel-default 6.0.12
by bugzilla_noreply＠suse.com 01 Jan '23

01 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206697 Bug ID: 1206697 Summary: Wireless network disappears on Raspberry Pi 4B after kernel-default 6.0.12 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: shangshangzikun(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 863687 --> http://bugzilla.opensuse.org/attachment.cgi?id=863687&action=edit dmesg-6.1.1.log After upgrading kernel-default to 6.1.x for my rpi4 (running openSUSE Tumbleweed) from kernel:stable repo, I found my wireless network device (wlan0) was gone. Downgrading to kernel-default 6.0.12 fixes the problem temporarily. May that be a kernel-firmware issue as I suspect? dmesg logs are provided as follows. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1206758] New: xhci_hcd periodically not ready on resume
by bugzilla_noreply＠suse.com 31 Dec '22

31 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1206758 Bug ID: 1206758 Summary: xhci_hcd periodically not ready on resume Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: pablo(a)blueoakdb.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 863753 --> http://bugzilla.opensuse.org/attachment.cgi?id=863753&action=edit Initial attachment - contents described in initial post Hi, To save energy, I started suspending my laptop. This new behavior uncovered a minor software defect. Occasionally, upon resumption a USB controller fails to resume. It manifests itself by my phone no longer recognized by the O/S. Attached is a tar-ball with the following files: o dmesg snippet (grep xhci_hcd) o lsusb -vt: + working.usb.no.phone - working, no phone connected + working.usb.phone - working, phone connected + not.working* - not working, etc. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1206759] Audio output rerouted to different HDMI output after monitor suspend
by bugzilla_noreply＠suse.com 31 Dec '22

31 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1206759 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Kernel |Sound Assignee|kernel-bugs(a)opensuse.org |tiwai(a)suse.com -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206759] Audio output rerouted to different HDMI output after monitor suspend
by bugzilla_noreply＠suse.com 31 Dec '22

31 Dec '22

1 0

[Bug 1206683] kernel 6.1.1 freezes before the gui appears
by bugzilla_noreply＠suse.com 30 Dec '22

30 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1206683 https://bugzilla.suse.com/show_bug.cgi?id=1206683#c30 --- Comment #30 from Scott Bradnick <scott.bradnick(a)suse.com> --- (In reply to Takashi Iwai from comment #28) > (In reply to Frank Kr�ger from comment #25) > > Hopefully Takashi Iwai will provide a test kernel with either the patch or > > the reverted commit as described here: > > https://lore.kernel.org/lkml/35c73172-4e06-3877-56bd-133f9192adc3@leemhuis. > > info/ > > It's being built in OBS home:tiwai:bsc1206683 repo. > Give it a try once after it finishes (and succeeds) the build. Great results so far w/ this build version :) $ uptime && uname -r 12:24:49 up 0:03, 1 user, load average: 0.66, 0.56, 0.26 6.1.1-1.g081acb5-default Even though 3min isn't a whole lot of time, I'd never make it w/o a hard lock on 6.1.0+ otherwise - thanks Takashi! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206702] New: SYS_io_submit and SYS_iogetevents seem not suitable for networking
by bugzilla_noreply＠suse.com 30 Dec '22

30 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1206702 Bug ID: 1206702 Summary: SYS_io_submit and SYS_iogetevents seem not suitable for networking Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Enhancement Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: andreas.wagner(a)aw83.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- IOCB_CMD_PREAD and others exist, but I don't find a way to register a listening socket in a suitable manner. IOCB_CMD_PREAD on a listening socket stops with a segmentation fault in my example-program (https://gitlab.com/andreas.wagner/io_playground) -- You are receiving this mail because: You are the assignee for the bug.

1 3