January 2023 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1206774] dvb driver fails
by bugzilla_noreply＠suse.com 04 Jan '23

04 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206774 https://bugzilla.suse.com/show_bug.cgi?id=1206774#c7 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby(a)suse.com Flags|needinfo?(Gerhard@Dr-Lorbee | |r.de) | --- Comment #7 from Jiri Slaby <jslaby(a)suse.com> --- The driver was moved to staging and marked as deprecated by: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?… -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206758] xhci_hcd periodically not ready on resume
by bugzilla_noreply＠suse.com 04 Jan '23

04 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206758 https://bugzilla.suse.com/show_bug.cgi?id=1206758#c12 Oliver Neukum <oneukum(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED --- Comment #12 from Oliver Neukum <oneukum(a)suse.com> --- (In reply to Pablo Sanchez from comment #10) > (In reply to Oliver Neukum from comment #8) > > The failure you are seeing is on the PCI level. From your logs it is unclear > > whether the HC that fails to resume is hosting other busses. It is possible > > that it is just not resumed without a device. > > Hi, > > My work-around is to resume, *then* connect the device. Sorry, this probably needs a long explanation. From usbcore's viewpoint your roothub on the XHCI without any device connected to it will be in the state (suspended w. remote wakeup) after your system resumes that is the desired state of the root hub, too. So without devices if your system is suspended, no PM transitions will be done on the roothub. If, however, your system is connected to your phone, the roothub and the phone need to be in (active) before and after the system sleeps. So PM transitions are certainly done. My theory was that your system is generally incapable of a PM transition on the PCI level at that time. If that theory were true, your system should crash with any device that is in (active) attached and it should also crash if you artificially force the roothub into a PM transition on resume, which was my second suggestion. > > > Do you have other devices to test to make sure it is not specific to your > > phone? > > What an excellent idea. As my phone is a Samsung S21, non-root, I hadn't > thought it might be an issue. > > Using another phone (OnePlus Nord), it works. Please attach the output of "lsusb -v" in the working state with that second phone connected. > > Alternatively, if not, it would be necessary to set the "control" > > attribute for your root hub to "on". > > I think you're saying a work-around is for me to create a udev rule. No, that was for testing purposes only. Something is failing on the PCI level. You cannot fix that with a udev rule. So please test whether the fault is related to ASPM by doing Takashi's test. From your log: [26232.379255] xhci_hcd 0000:a4:00.0: Unable to change power state from D3cold to D0, device inaccessible [26232.457787] xhci_hcd 0000:a4:00.0: Unable to change power state from D3cold to D0, device inaccessible These must not happen. If they do, everything after that is as expected, though not as desired. Unfortunately everything before them is as it should be. Hence tests to determine the cause of this issue are needed. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[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 1206758] xhci_hcd periodically not ready on resume
by bugzilla_noreply＠suse.com 04 Jan '23

04 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206758 https://bugzilla.suse.com/show_bug.cgi?id=1206758#c11 --- Comment #11 from Takashi Iwai <tiwai(a)suse.com> --- So it's a Thunderbolt PCI controller, as expected. This might be a similar issue as the upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=216728 Could you check with pcie_aspm=off boot option? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206758] xhci_hcd periodically not ready on resume
by bugzilla_noreply＠suse.com 03 Jan '23

03 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206758 https://bugzilla.suse.com/show_bug.cgi?id=1206758#c10 --- Comment #10 from Pablo Sanchez <pablo(a)blueoakdb.com> --- (In reply to Oliver Neukum from comment #8) > The failure you are seeing is on the PCI level. From your logs it is unclear > whether the HC that fails to resume is hosting other busses. It is possible > that it is just not resumed without a device. Hi, My work-around is to resume, *then* connect the device. > Do you have other devices to test to make sure it is not specific to your > phone? What an excellent idea. As my phone is a Samsung S21, non-root, I hadn't thought it might be an issue. Using another phone (OnePlus Nord), it works. > Alternatively, if not, it would be necessary to set the "control" > attribute for your root hub to "on". I think you're saying a work-around is for me to create a udev rule. I can certainly do this but given that my phone is very generic, non-rooted, I'm not sure whether that's a good solution for regular users. Thoughts? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206758] xhci_hcd periodically not ready on resume
by bugzilla_noreply＠suse.com 03 Jan '23

03 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206758 https://bugzilla.suse.com/show_bug.cgi?id=1206758#c9 Pablo Sanchez <pablo(a)blueoakdb.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(pablo(a)blueoakdb.c | |om) | --- Comment #9 from Pablo Sanchez <pablo(a)blueoakdb.com> --- Created attachment 863813 --> https://bugzilla.suse.com/attachment.cgi?id=863813&action=edit hwinfo, lspci and dmesg Hi, This data was captured with the latest kernel (6.1.1.1-default) This tar-ball contains the following files: 2/hwinfo.phone.bad.txt 2/hwinfo.phone.ok.txt 2/lspci.phone.bad.txt 2/lspci.phone.ok.txt 2/dmesg.bad.txt where, o hwinfo: hwinfo --all --log ... o lspci: lspci -vvxxx o Files with 'ok' are the /before/ state o Files with 'bad' are the /after/, borked state and 'dmesg.txt' is trimmed to capture the resume with the phone connected (borking the driver). Thank you! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206797] New: [RPi3] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
by bugzilla_noreply＠suse.com 03 Jan '23

03 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206797 Bug ID: 1206797 Summary: [RPi3] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 URL: https://openqa.opensuse.org/tests/3008872/modules/jour nal_check/steps/10 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de CC: afaerber(a)suse.com, dmueller(a)suse.com, ivan.ivanov(a)suse.com, mbrugger(a)suse.com Found By: openQA Blocker: Yes With kernel 6.1, openQA shows the following kernel trace on RPi3: kernel: brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50 -- You are receiving this mail because: You are the assignee for the bug.

1 4

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

03 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206697 Ivan Ivanov <ivan.ivanov(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kernel-bugs(a)opensuse.org |ivan.ivanov(a)suse.com -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206758] xhci_hcd periodically not ready on resume
by bugzilla_noreply＠suse.com 03 Jan '23

03 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206758 https://bugzilla.suse.com/show_bug.cgi?id=1206758#c8 --- Comment #8 from Oliver Neukum <oneukum(a)suse.com> --- The failure you are seeing is on the PCI level. From your logs it is unclear whether the HC that fails to resume is hosting other busses. It is possible that it is just not resumed without a device. Do you have other devices to test to make sure it is not specific to your phone? Alternatively, if not, it would be necessary to set the "control" attribute for your root hub to "on". -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206794] Frequent Kernel Crashes due to problem in af_key.c
by bugzilla_noreply＠suse.com 03 Jan '23

03 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206794 https://bugzilla.suse.com/show_bug.cgi?id=1206794#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |tiwai(a)suse.com Resolution|--- |FIXED --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Thanks for the report. I backported the upstream commit b97df039a68b2f3e848e238df5d5d06343ea497b to SLE15-SP4 git branch now. It'll be included in the next maintenance update kernel. -- You are receiving this mail because: You are the assignee for the bug.

1 0