December 2023 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1215285] [RPi3] dwc2 3f980000.usb: dwc2_hc_halt() Channel can't be halted
by bugzilla_noreply＠suse.com 05 Dec '23

05 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1215285 https://bugzilla.suse.com/show_bug.cgi?id=1215285#c9 Miroslav Beneš <mbenes(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mbenes(a)suse.com --- Comment #9 from Miroslav Beneš <mbenes(a)suse.com> --- The patch from comment 6 is a part of 6.6.4 stable and now merged to our stable branch so it should appear in TW soon. Guillaume, please let us know the outcome. It might be the fix even though the symptoms are different. As mentioned previously. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217344] Linux 6.6.x fails to boot
by bugzilla_noreply＠suse.com 04 Dec '23

04 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217344 https://bugzilla.suse.com/show_bug.cgi?id=1217344#c15 --- Comment #15 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Rigo Wenning from comment #14) > Kernel 6.6.4 installed. When booting, the system boots normally into the X > login screen. When I try to login into the KDE session, the background > images of the plasma screen appear, but the desktop remains empty with only > the mouse pointer shown. > > With kernel 6.5.9 the system starts normally. I will create another bug > report as you said its unrelated and I did not find a similar bug. Then it's a different bug. Please create another one. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217344] Linux 6.6.x fails to boot
by bugzilla_noreply＠suse.com 04 Dec '23

04 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217344 https://bugzilla.suse.com/show_bug.cgi?id=1217344#c14 --- Comment #14 from Rigo Wenning <rigo(a)w3.org> --- Kernel 6.6.4 installed. When booting, the system boots normally into the X login screen. When I try to login into the KDE session, the background images of the plasma screen appear, but the desktop remains empty with only the mouse pointer shown. With kernel 6.5.9 the system starts normally. I will create another bug report as you said its unrelated and I did not find a similar bug. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217503] Ethernet to USB ASIX AX88179A chip connects only when opening network configuration module of Yast2
by bugzilla_noreply＠suse.com 04 Dec '23

04 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217503 https://bugzilla.suse.com/show_bug.cgi?id=1217503#c20 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED --- Comment #20 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Keks Dose from comment #18) > 38: USB 00.0: 0200 Ethernet controller > [Created at usb.122] > Unique ID: Gtr0._FrTcilDi4C > Parent ID: zPk0.xYNhIwdOaa6 > SysFS ID: /devices/pci0000:00/0000:00:14.0/usb4/4-1/4-1:2.0 > SysFS BusID: 4-1:2.0 > Hardware Class: network > Model: "ASIX Electronics AX88179 Gigabit Ethernet" > Hotplug: USB > Vendor: usb 0x0b95 "ASIX Electronics Corp." > Device: usb 0x1790 "AX88179 Gigabit Ethernet" .... > Module Alias: "usb:v0B95p1790d0200dc00dsc00dp00ic02isc0Dip00in00" > Driver Info #0: > Driver Status: cdc_ncm is active > Driver Activation Cmd: "modprobe cdc_ncm" > Driver Info #1: > Driver Status: cdc_mbim is active > Driver Activation Cmd: "modprobe cdc_mbim" The device has two interfaces, and only the first one is loaded while you need the second one. That's the problem. A workaround is like what you did: just let the latter driver module loaded. You can set up a softdep instead of always loading, but I guess it doesn't matter much in either way. As you already found out a workaround, I close the bug now. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217344] Linux 6.6.x fails to boot
by bugzilla_noreply＠suse.com 04 Dec '23

04 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217344 https://bugzilla.suse.com/show_bug.cgi?id=1217344#c12 --- Comment #12 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Tommaso Fonda from comment #10) > (In reply to Takashi Iwai from comment #8) > > At first, try to check whether the latest 6.7-rc still suffers from the same > > problem. If it boots, it's something specific to 6.6.x, and we need to find > > an upstream fix. > > > > If 6.7-rc still doesn't boot, it has to be reported to the upstream. But > > without a proper log, it's a bit difficult to know to whom reporting. I > > guess you'd be asked to perform git bisect in such a case. > > Thanks, I will build 6.7-rc as soon as possible and let you know. There is already a kernel package for 6.7-rc available in OBS Kernel:HEAD repo. It can be tested quickly as well as the kernel in OBS Kernel:stable repo. I suppose you've tested only the Leap standard kernels, so far, right? i.e. you didn't build kernels by yourself? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217344] Linux 6.6.x fails to boot
by bugzilla_noreply＠suse.com 04 Dec '23

04 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217344 https://bugzilla.suse.com/show_bug.cgi?id=1217344#c11 --- Comment #11 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Rigo Wenning from comment #9) > I have also kernel failure with the latest tumbleweed kernel. When > installing it runs dracut for every single core. The system boots. But when > I want to log into KDE, it hangs forever. Console reports a failure to start > powerdevil (for whatever reason). So already the kernel install procedure > seems fishy. > > Again, Kernel 6.5.9 just works fine, boots, KDE runs fine. > > I have a Dell latitude 7490. > > So even if it starts, I think kernel 6.6 has trouble interacting with KDE. > There seems to be something fundamentally wrong. > > BTW, when installed for the first time, the system started and ran fine, > even after reboot. I haven't done any install since then. Now I have updated > to the latest tumbleweed 2023-12-02. That runs fine with kernel 6.5.9 but > does not work with Kernel 6.6. > > I think this is a critical bug If it boots ever, yours can be likely a different issue. There have been already a few different boot problems with 6.6.x. Make sure that your machine still has the boot problem with the latest kernel in OBS Kernel:stable repo, too. And if yes, check whether it shows the very same symptom (no relevant messages even if you boot with nomodeset boot option). -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217344] Linux 6.6.x fails to boot
by bugzilla_noreply＠suse.com 04 Dec '23

04 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217344 https://bugzilla.suse.com/show_bug.cgi?id=1217344#c9 Rigo Wenning <rigo(a)w3.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rigo(a)w3.org --- Comment #9 from Rigo Wenning <rigo(a)w3.org> --- I have also kernel failure with the latest tumbleweed kernel. When installing it runs dracut for every single core. The system boots. But when I want to log into KDE, it hangs forever. Console reports a failure to start powerdevil (for whatever reason). So already the kernel install procedure seems fishy. Again, Kernel 6.5.9 just works fine, boots, KDE runs fine. I have a Dell latitude 7490. So even if it starts, I think kernel 6.6 has trouble interacting with KDE. There seems to be something fundamentally wrong. BTW, when installed for the first time, the system started and ran fine, even after reboot. I haven't done any install since then. Now I have updated to the latest tumbleweed 2023-12-02. That runs fine with kernel 6.5.9 but does not work with Kernel 6.6. I think this is a critical bug -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217344] Linux 6.6.x fails to boot
by bugzilla_noreply＠suse.com 04 Dec '23

04 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217344 https://bugzilla.suse.com/show_bug.cgi?id=1217344#c8 --- Comment #8 from Takashi Iwai <tiwai(a)suse.com> --- At first, try to check whether the latest 6.7-rc still suffers from the same problem. If it boots, it's something specific to 6.6.x, and we need to find an upstream fix. If 6.7-rc still doesn't boot, it has to be reported to the upstream. But without a proper log, it's a bit difficult to know to whom reporting. I guess you'd be asked to perform git bisect in such a case. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217503] Ethernet to USB ASIX AX88179A chip connects only when opening network configuration module of Yast2
by bugzilla_noreply＠suse.com 01 Dec '23

01 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217503 https://bugzilla.suse.com/show_bug.cgi?id=1217503#c19 --- Comment #19 from Keks Dose <cookie170(a)web.de> --- OK, tried, wrote "cdc_mbim.conf" into /etc/modules-load.d with just one line cdc_mbim, restarted, no. I'm not sure it is worth time and effort to hunt this bug while there is an easy workaround. On the other hand we'll have more and more of those adapters, because more and more notebooks come without ethernet socket and people will buy usb2ethnert adapters. Should work on linux™. Close as wontfix? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217503] Ethernet to USB ASIX AX88179A chip connects only when opening network configuration module of Yast2
by bugzilla_noreply＠suse.com 01 Dec '23

01 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217503 https://bugzilla.suse.com/show_bug.cgi?id=1217503#c18 --- Comment #18 from Keks Dose <cookie170(a)web.de> --- (In reply to Stefan Hundhammer from comment #17) > The one that 'hwinfo --netcard' tells you to use; see comment #6. No, doesn't work: hwinfo --netcard 14: PCI 14.3: 0282 WLAN controller [Created at pci.386] Unique ID: Dhtl.qVqUKmQ3GD6 SysFS ID: /devices/pci0000:00/0000:00:14.3 SysFS BusID: 0000:00:14.3 Hardware Class: network Model: "Intel Wi-Fi 6 AX201" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa0f0 "Wi-Fi 6 AX201" SubVendor: pci 0x8086 "Intel Corporation" SubDevice: pci 0x0070 Revision: 0x20 Driver: "iwlwifi" Driver Modules: "iwlwifi" Device File: wlp0s20f3 Features: WLAN Memory Range: 0x603d1dc000-0x603d1dffff (rw,non-prefetchable) IRQ: 16 (321 events) HW Address: 08:6a:c5:4a:8f:99 Permanent HW Address: 08:6a:c5:4a:8f:99 Link detected: yes WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 12 13 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 2.467 2.472 5.18 5.2 5.22 5.24 5.26 5.28 5.3 5.32 5.5 5.52 5.54 5.56 5.58 5.6 5.62 5.64 5.66 5.68 5.7 WLAN encryption modes: WEP40 WEP104 TKIP CCMP WLAN authentication modes: open sharedkey wpa-psk wpa-eap Module Alias: "pci:v00008086d0000A0F0sv00008086sd00000070bc02sc80i00" Driver Info #0: Driver Status: iwlwifi is active Driver Activation Cmd: "modprobe iwlwifi" Config Status: cfg=no, avail=yes, need=no, active=unknown 38: USB 00.0: 0200 Ethernet controller [Created at usb.122] Unique ID: Gtr0._FrTcilDi4C Parent ID: zPk0.xYNhIwdOaa6 SysFS ID: /devices/pci0000:00/0000:00:14.0/usb4/4-1/4-1:2.0 SysFS BusID: 4-1:2.0 Hardware Class: network Model: "ASIX Electronics AX88179 Gigabit Ethernet" Hotplug: USB Vendor: usb 0x0b95 "ASIX Electronics Corp." Device: usb 0x1790 "AX88179 Gigabit Ethernet" Revision: "2.00" Serial ID: "00869C05" Driver: "cdc_ncm" Driver Modules: "cdc_ncm" Device File: enp0s20f0u1c2 HW Address: f8:e4:3b:86:9c:05 Permanent HW Address: f8:e4:3b:86:9c:05 Link detected: no Module Alias: "usb:v0B95p1790d0200dc00dsc00dp00ic02isc0Dip00in00" Driver Info #0: Driver Status: cdc_ncm is active Driver Activation Cmd: "modprobe cdc_ncm" Driver Info #1: Driver Status: cdc_mbim is active Driver Activation Cmd: "modprobe cdc_mbim" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #39 (Hub) And this does not activate ethernet: localhost:/home/AW # modprobe cdc_mbim (as root) I'll write a second file to modules-load.d "cdc_mbim.config" and reboot, but I don't expect success. -- You are receiving this mail because: You are the assignee for the bug.

1 0