January 2023 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1206900] hibernation not working. normal operation resumed
by bugzilla_noreply＠suse.com 05 Jan '23

05 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206900 http://bugzilla.opensuse.org/show_bug.cgi?id=1206900#c3 --- Comment #3 from Andreas Stieger <Andreas.Stieger(a)gmx.de> --- Agree (or re-open and adjust the version field) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206900] hibernation not working. normal operation resumed
by bugzilla_noreply＠suse.com 05 Jan '23

05 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206900 http://bugzilla.opensuse.org/show_bug.cgi?id=1206900#c2 --- Comment #2 from Lars-G�ran Andersson <larsg(a)vetulusit.se> --- This is only a problem from a 'saving energy' perspective, so I will upgrade to 15.4 and check if the problem remains. If it's still there I will re-issue a bug report. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206848] khugepaged at 100% CPU
by bugzilla_noreply＠suse.com 05 Jan '23

05 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206848 https://bugzilla.suse.com/show_bug.cgi?id=1206848#c3 --- Comment #3 from Martin Koller <kollix(a)aon.at> --- Created attachment 863890 --> https://bugzilla.suse.com/attachment.cgi?id=863890&action=edit another log after more than 15 minutes 100% CPU -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206848] khugepaged at 100% CPU
by bugzilla_noreply＠suse.com 05 Jan '23

05 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206848 https://bugzilla.suse.com/show_bug.cgi?id=1206848#c2 Martin Koller <kollix(a)aon.at> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(kollix(a)aon.at) | --- Comment #2 from Martin Koller <kollix(a)aon.at> --- Created attachment 863888 --> https://bugzilla.suse.com/attachment.cgi?id=863888&action=edit captured log file -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206900] hibernation not working. normal operation resumed
by bugzilla_noreply＠suse.com 05 Jan '23

05 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206900 http://bugzilla.opensuse.org/show_bug.cgi?id=1206900#c1 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |Andreas.Stieger(a)gmx.de, | |larsg(a)vetulusit.se Component|Basesystem |Kernel Resolution|--- |WONTFIX Assignee|screening-team-bugs(a)suse.de |kernel-bugs(a)opensuse.org Flags| |needinfo?(larsg(a)vetulusit.s | |e) --- Comment #1 from Andreas Stieger <Andreas.Stieger(a)gmx.de> --- (In reply to Lars-G�ran Andersson from comment #0) > Started after a normal update, but cannot remember exactly when. Backtrack and binary search. Start with the kernels, and specify the update. openSUSE Leap 15.3 is EOL now and will not be receiving further updates. Upgrade to Leap 15.4 and try again. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206843] Lenovo T14s Gen3 AMD resume from sleep broken
by bugzilla_noreply＠suse.com 05 Jan '23

05 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206843 https://bugzilla.suse.com/show_bug.cgi?id=1206843#c3 --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- OK, thanks for the info update. AFAIK, oft-seen problems with those docs are about the Realtek Ethernet driver (r8152). You can try to unload r8152 before the suspend, if any. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206843] Lenovo T14s Gen3 AMD resume from sleep broken
by bugzilla_noreply＠suse.com 05 Jan '23

05 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206843 https://bugzilla.suse.com/show_bug.cgi?id=1206843#c2 --- Comment #2 from Christian Goll <cgoll(a)suse.com> --- This seems to be related to my old Dell docking station, which shows also other malfunctions. I will test again with a new Lenovo docking station and report if the problem persists. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206848] khugepaged at 100% CPU
by bugzilla_noreply＠suse.com 05 Jan '23

05 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206848 https://bugzilla.suse.com/show_bug.cgi?id=1206848#c1 Michal Hocko <mhocko(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kollix(a)aon.at Flags| |needinfo?(kollix(a)aon.at) --- Comment #1 from Michal Hocko <mhocko(a)suse.com> --- Could you collect /proc/vmstat during that time period (say every second)[1]? [1] You can use collect_logs from mmdebug-tools package from https://build.opensuse.org/package/binaries/home:mhocko/mmdebug-tools/openS… The command then would be collect_logs -t1s -i /proc/vmstat -o vmstat.log -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206847] BUG: unable to handle page fault for address: ffff8cc50d0c3680
by bugzilla_noreply＠suse.com 05 Jan '23

05 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206847 https://bugzilla.suse.com/show_bug.cgi?id=1206847#c3 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- Not sure whether it's already broken in USB side-storage side or a bug in the scsi layer. At least, the Oops happens at the sbitmap_put() call in scsi_device_unbusy(), at it seems. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206864] Direct Rendering Manager trouble upon resume from suspend to RAM
by bugzilla_noreply＠suse.com 05 Jan '23

05 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206864 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |karl.mistelberger(a)nefkom.ne | |t Flags| |needinfo?(karl.mistelberger | |(a)nefkom.net) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206864] Direct Rendering Manager trouble upon resume from suspend to RAM
by bugzilla_noreply＠suse.com 05 Jan '23

05 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206864 https://bugzilla.suse.com/show_bug.cgi?id=1206864#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Looks like a problem of amdgpu. I suppose it's something new in 6.1.x, and not happening with 6.0.x kernel? If yes, please report to the upstream, e.g. gitlab.freedesktop.org Issues. In anyway, please give the hardware details. -- 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#c16 --- Comment #16 from Pablo Sanchez <pablo(a)blueoakdb.com> --- Unless instructed otherwise, I'll keep following the head of TW: �� $ uname -sr Linux 6.1.2-1-default -- 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#c15 --- Comment #15 from Pablo Sanchez <pablo(a)blueoakdb.com> --- (In reply to Oliver Neukum from comment #8) > It is possible that it is just not resumed without a device. Hey Oliver, Well, another excellent question. Clearly you understand how everything is supposed to work under the hood. Nice. I tried to gather more fine-grained data in the hopes it might help. If not, meh, I burned a few minutes. :p ::: Test 1 ::: 1. Connect phone and note laptop recognizes it. 2. Leave phone connected and suspend. 3. Do not disconnect phone. 4. Resume the laptop. ... Result ... Worked! ::: Test 2 ::: Same as the previous test but replace step 3 with a disconnect/reconnect: 1. Connect phone and note laptop recognizes it. 2. Leave phone connected and suspend. 3a. Disconnect phone. 3b. Wait for a few seconds. 3c. Reconnect phone 4. Resume the laptop. ... Result ... Problem tickled. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206846] sysfs: cannot create duplicate filename '/bus/nvmem/devices/rmem0'
by bugzilla_noreply＠suse.com 04 Jan '23

04 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206846 https://bugzilla.suse.com/show_bug.cgi?id=1206846#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |seppe.hoogzaad(a)gmail.com, | |tiwai(a)suse.com Flags| |needinfo?(seppe.hoogzaad@gm | |ail.com) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- There are actually two kernel warnings: one is about the duplicated sysfs entry for /bus/nvmem/devices/rmem0, while another is the firmware update timeout for rpi. Are both new warnings, or only the former? In anyway, TW already moved to 6.1 kernel. Could you verify whether the issue still persists with the latest kernel or not? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206843] Lenovo T14s Gen3 AMD resume from sleep broken
by bugzilla_noreply＠suse.com 04 Jan '23

04 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206843 https://bugzilla.suse.com/show_bug.cgi?id=1206843#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cgoll(a)suse.com, | |tiwai(a)suse.com Flags| |needinfo?(cgoll(a)suse.com) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Could you check whether it's a regression in the update kernel(s) or it's been broken in all Leap 15.4 kernels? In anyway, please give hwinfo output from Leap 15.4 kernel. When TW kernel works, give the hwinfo output from there, too, in addition to the dmesg outputs from both cases. -- 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#c14 --- Comment #14 from Pablo Sanchez <pablo(a)blueoakdb.com> --- Created attachment 863848 --> https://bugzilla.suse.com/attachment.cgi?id=863848&action=edit working phone: lsusb + dmesg (In reply to Oliver Neukum from comment #12) > > Sorry, this probably needs a long explanation. > > [ trimmed for brevity ] Thank you Oliver for taking the time to explain. I appreciate it! > Please attach the output of "lsusb -v" in the working state with that second > phone connected. Done! The tar-ball contains the following files: o 3/dmesg.nord.txt o 3/lsusb.nord.aft.suspend.txt o 3/lsusb.nord.b4.suspend.txt dmesg captures when I disconnected the phone, suspended and resumed with the phone connected. Thanks again! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206847] New: BUG: unable to handle page fault for address: ffff8cc50d0c3680
by bugzilla_noreply＠suse.com 04 Jan '23

04 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206847 Bug ID: 1206847 Summary: BUG: unable to handle page fault for address: ffff8cc50d0c3680 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: matwey.kornilov(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 863845 --> http://bugzilla.opensuse.org/attachment.cgi?id=863845&action=edit dmesg.txt Hello, I am running openSUSE Leap 15.4 with kernel-default-5.14.21-150400.24.38.1.x86_64 I've faced a system crash and have to kdump outputs for it. The crash occurred during an attempt to connect external hard drive using USB 3.0 adapter. The drive itself has some bad sectors and performs badly, so this seems to triggered the issue. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1206843] New: Lenovo T14s Gen3 AMD resume from sleep broken
by bugzilla_noreply＠suse.com 04 Jan '23

04 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206843 Bug ID: 1206843 Summary: Lenovo T14s Gen3 AMD resume from sleep broken Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 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 actual Leap15.4 kernel does not wake up after a `systemctl suspend` but works fine with the tumbleweed kernel. The `/var/log/messages` just shows the next boot. -- 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#c13 --- Comment #13 from Pablo Sanchez <pablo(a)blueoakdb.com> --- Created attachment 863840 --> https://bugzilla.suse.com/attachment.cgi?id=863840&action=edit pcie_aspm=off test > dmesg output > Could you check with pcie_aspm=off boot option? Hi, Unfortunately this test didn't pan out. Previously, the phone would work on the first boot. With the test, it failed at first-boot. I'm attaching the output of dmesg. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[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#c8 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |UPSTREAM --- Comment #8 from Jiri Slaby <jslaby(a)suse.com> --- The TODO says: +The saa7146-based drivers are one of the few drivers still not using +the vb2 framework, so these drivers are now deprecated with the intent of +removing them altogether by the beginning of 2023. + +In order to keep these drivers they have to be converted to vb2. +If someone is interested in doing this work, then contact the +linux-media mailinglist (https://linuxtv.org/lists.php). So if there are no volunteers, the driver is going away. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[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

[Bug 1206718] [Build 366.2] openQA test fails in opensuse_welcome - opensuse-welcome crashed
by bugzilla_noreply＠suse.com 03 Jan '23

03 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206718 https://bugzilla.suse.com/show_bug.cgi?id=1206718#c1 Max Lin <mlin(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kernel-bugs(a)opensuse.org |kernel-bugs(a)suse.de --- Comment #1 from Max Lin <mlin(a)suse.com> --- Since Leap15's kernel is from SLE15, lets assign it to the internal kernel team. -- 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#c7 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pablo(a)blueoakdb.com Flags| |needinfo?(pablo(a)blueoakdb.c | |om) --- Comment #7 from Takashi Iwai <tiwai(a)suse.com> --- OK, thanks. Could you give hwinfo output as well as the dmesg output? Also check the lspci output and see which device is the failing xhci_hcd (in the case of the original post dmesg.txt, it's 0000:a4:00.0). -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

03 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206794 Bug ID: 1206794 Summary: Frequent Kernel Crashes due to problem in af_key.c Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: Manfred.Haertel(a)lotto-rlp.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- We experienced frequent kernel crashes on some of our OpenSuse based IPSEC Gateways. The crash dump looks like this: [141226.000411][ T3410] BUG: kernel NULL pointer dereference, address: 0000000000000000 [141226.093721][ T3410] #PF: supervisor write access in kernel mode [141226.166051][ T3410] #PF: error_code(0x0002) - not-present page [141226.237334][ T3410] PGD 0 P4D 0 [141226.277176][ T3410] Oops: 0002 [#1] PREEMPT SMP PTI [141226.336929][ T3410] CPU: 13 PID: 3410 Comm: pluto Tainted: G I N 5.14.21-150400.24.33-default #1 SLE15-SP4 018fa6ac9e6418760457307f6579fc12335772aa [141226.513033][ T3410] Hardware name: HPE ProLiant DL380 Gen10/ProLiant DL380 Gen10, BIOS U30 11/13/2019 [141226.625191][ T3410] RIP: 0010:__xfrm_state_delete+0xc0/0x1e0 [141226.694385][ T3410] Code: 02 74 04 48 89 50 08 8b 93 cc 00 00 00 48 b8 22 01 00 00 00 00 ad de 48 89 43 20 85 d2 74 22 48 8b 43 38 48 8b 53 40 48 85 c0 <48> 89 02 74 04 48 89 50 08 48 b8 22 01 00 00 00 00 ad de 48 89 43 [141226.930232][ T3410] RSP: 0018:ffffb6bd410879d0 EFLAGS: 00010246 [141227.002562][ T3410] RAX: 0000000000000000 RBX: ffff9c29c543a700 RCX: 00000000fffffffd [141227.097953][ T3410] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffffffb84e1700 [141227.193343][ T3410] RBP: ffffffffb84e0840 R08: 0000000000000001 R09: 0000000000000002 [141227.288736][ T3410] R10: 0000000000000002 R11: 0000000000000032 R12: ffffffffb84e1700 [141227.384127][ T3410] R13: 0000000000000000 R14: 0000000000000000 R15: ffffffffb84e0840 [141227.479517][ T3410] FS: 00007fe961572040(0000) GS:ffff9c2c70140000(0000) knlGS:0000000000000000 [141227.586435][ T3410] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [141227.665053][ T3410] CR2: 0000000000000000 CR3: 0000000110a4c001 CR4: 00000000007706e0 [141227.760443][ T3410] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [141227.855831][ T3410] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [141227.951222][ T3410] PKRU: 55555554 [141227.993154][ T3410] Call Trace: [141228.031944][ T3410] <TASK> [141228.066541][ T3410] xfrm_state_delete+0x1e/0x40 [141228.123155][ T3410] xfrm_del_sa+0xcf/0x130 [xfrm_user 056771028dad419158fe83c515fe22924b96b850] [141228.230080][ T3410] xfrm_user_rcv_msg+0x26c/0x2e0 [xfrm_user 056771028dad419158fe83c515fe22924b96b850] [141228.344341][ T3410] ? __kmalloc_node_track_caller+0x1ba/0x3b0 [141228.415632][ T3410] ? netlink_deliver_tap+0x3a/0x1f0 [141228.477490][ T3410] ? copy_to_user_tmpl.part.21+0x150/0x150 [xfrm_user 056771028dad419158fe83c515fe22924b96b850] [141228.602229][ T3410] netlink_rcv_skb+0x4e/0x100 [141228.657796][ T3410] xfrm_netlink_rcv+0x30/0x40 [xfrm_user 056771028dad419158fe83c515fe22924b96b850] [141228.768914][ T3410] netlink_unicast+0x1b3/0x280 [141228.825527][ T3410] netlink_sendmsg+0x320/0x450 [141228.882143][ T3410] sock_sendmsg+0x5c/0x70 [141228.933515][ T3410] sock_write_iter+0x97/0x100 [141228.989082][ T3410] new_sync_write+0x1a1/0x1c0 [141229.044648][ T3410] vfs_write+0x220/0x280 [141229.094972][ T3410] ksys_write+0x50/0xe0 [141229.144246][ T3410] ? do_syscall_64+0x67/0x80 [141229.198758][ T3410] ? __x64_sys_poll+0x37/0x140 [141229.255372][ T3410] do_syscall_64+0x58/0x80 [141229.307788][ T3410] ? __task_pid_nr_ns+0x97/0xb0 [141229.365449][ T3410] ? syscall_exit_to_user_mode+0x18/0x40 [141229.432544][ T3410] ? do_syscall_64+0x67/0x80 [141229.487061][ T3410] ? do_syscall_64+0x67/0x80 [141229.541572][ T3410] ? do_syscall_64+0x67/0x80 [141229.596083][ T3410] ? irq_exit_rcu+0x41/0xc0 [141229.649553][ T3410] entry_SYSCALL_64_after_hwframe+0x61/0xcb [141229.719793][ T3410] RIP: 0033:0x7fe960995af3 [141229.772207][ T3410] Code: 0f 1f 80 00 00 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 64 8b 04 25 18 00 00 00 85 c0 75 14 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 55 f3 c3 0f 1f 00 41 54 55 49 89 d4 53 48 89 [141230.008050][ T3410] RSP: 002b:00007ffd0916cad8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 [141230.108679][ T3410] RAX: ffffffffffffffda RBX: 00007ffd0916cf80 RCX: 00007fe960995af3 [141230.204070][ T3410] RDX: 0000000000000028 RSI: 00007ffd0916cf80 RDI: 0000000000000017 [141230.299458][ T3410] RBP: 0000000000000028 R08: 00007ffd0916d4f0 R09: 00007ffd0916cf80 [141230.394847][ T3410] R10: 00007ffd0916d23b R11: 0000000000000246 R12: 000055d3d8f12139 [141230.490237][ T3410] R13: 00007ffd0916d4f0 R14: 00007ffd0916d400 R15: 00000000680f3536 [141230.585630][ T3410] </TASK> [141230.621277][ T3410] Modules linked in: binfmt_misc authenc echainiv cmac rmd160 camellia_generic camellia_aesni_avx2 camellia_aesni_avx_x86_64 camellia_x86_64 cast6_avx_x86_64 cast6_generic cast5_avx_x86_64 cast5_generic cast_common deflate gcm ccm serpent_avx2 serpent_avx_x86_64 serpent_sse2_x86_64 serpent_generic blowfish_generic blowfish_x86_64 blowfish_common twofish_generic twofish_avx_x86_64 twofish_x86_64_3way twofish_x86_64 twofish_common xcbc sha256_ssse3 sha512_ssse3 des_generic libdes xfrm_user ah6 ah4 esp6 esp4 xfrm4_tunnel tunnel4 ipcomp ipcomp6 xfrm6_tunnel xfrm_ipcomp tunnel6 af_key xfrm_algo nfnetlink bluetooth ecdh_generic iptable_nat xt_nat nf_nat nf_conntrack ipt_REJECT nf_reject_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c xt_LOG nf_log_syslog iptable_filter xt_policy xt_TCPMSS xt_tcpudp bpfilter af_packet iscsi_ibft iscsi_boot_sysfs rfkill dmi_sysfs intel_rapl_msr intel_rapl_common ipmi_ssif nfit libnvdimm x86_pkg_temp_thermal intel_powerclamp coretemp [141230.621341][ T3410] kvm_intel nls_iso8859_1 kvm nls_cp437 vfat fat cdc_eem ses usbnet pl2303 usbserial irqbypass pcspkr efi_pstore(N) enclosure mii tg3 mei_me libphy mei lpc_ich mfd_core hpilo acpi_ipmi intel_pch_thermal ioatdma ipmi_si dca ipmi_devintf ipmi_msghandler acpi_tad(N) button fuse configfs ip_tables x_tables ext4 crc16 mbcache jbd2 hid_generic usbhid uas usb_storage sr_mod sd_mod cdrom t10_pi crc32_pclmul crc32c_intel ghash_clmulni_intel mgag200 drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops cec rc_core xhci_pci aesni_intel xhci_pci_renesas drm xhci_hcd ahci smartpqi crypto_simd cryptd libahci ehci_pci ehci_hcd scsi_transport_sas usbcore libata i2c_algo_bit hpwdt wmi sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua scsi_mod msr efivarfs [141232.491336][ T3410] Supported: No, Unsupported modules are loaded [141232.565764][ T3410] CR2: 0000000000000000 [141232.615034][ T3410] ---[ end trace 7154d1cff8910ed6 ]--- [141232.759152][ T3410] RIP: 0010:__xfrm_state_delete+0xc0/0x1e0 [141232.828350][ T3410] Code: 02 74 04 48 89 50 08 8b 93 cc 00 00 00 48 b8 22 01 00 00 00 00 ad de 48 89 43 20 85 d2 74 22 48 8b 43 38 48 8b 53 40 48 85 c0 <48> 89 02 74 04 48 89 50 08 48 b8 22 01 00 00 00 00 ad de 48 89 43 [141233.064192][ T3410] RSP: 0018:ffffb6bd410879d0 EFLAGS: 00010246 [141233.136524][ T3410] RAX: 0000000000000000 RBX: ffff9c29c543a700 RCX: 00000000fffffffd [141233.231919][ T3410] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffffffb84e1700 [141233.327309][ T3410] RBP: ffffffffb84e0840 R08: 0000000000000001 R09: 0000000000000002 [141233.422697][ T3410] R10: 0000000000000002 R11: 0000000000000032 R12: ffffffffb84e1700 [141233.518087][ T3410] R13: 0000000000000000 R14: 0000000000000000 R15: ffffffffb84e0840 [141233.613477][ T3410] FS: 00007fe961572040(0000) GS:ffff9c2c70140000(0000) knlGS:0000000000000000 [141233.720401][ T3410] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [141233.799019][ T3410] CR2: 0000000000000000 CR3: 0000000110a4c001 CR4: 00000000007706e0 [141233.894409][ T3410] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [141233.989799][ T3410] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [141234.085189][ T3410] PKRU: 55555554 [141234.127122][ T3410] Kernel panic - not syncing: Fatal exception in interrupt [141234.241007][ T3410] Kernel Offset: 0x35800000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff) [141234.450223][ T3410] ---[ end Kernel panic - not syncing: Fatal exception in interrupt ]--- We found out that this problem is actually a known problem in af_key.c and a one line patch exists, see https://patchwork.kernel.org/project/netdevbpf/patch/20221102101848.ibvumax… However, it seems that the current OpenSuse 15.4 kernel does NOT include this patch. Applying the patch manually fixed the problem for us. We would like to see the patch included in the OpenSuse kernel. -- 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 02 Jan '23

02 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206758 https://bugzilla.suse.com/show_bug.cgi?id=1206758#c6 --- Comment #6 from Pablo Sanchez <pablo(a)blueoakdb.com> --- Hi, Thank you for instructions on how to proceed. Unfortunately, the problem exists in the earliest 6.0[1]: 6.0.12 kernel-default-6.0.12-1.1.x86_64 I'd like to confirm I'm testing properly. Aside from installing the 'kernel-default' RPM and booting it, do I need to install any other RPMs? For my initial test, I confirmed that I booted the test kernel with 'uname -a' Thx! ::: References ::: [1] - https://download.opensuse.org/history/ -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206782] New: SND_SOC_QCOM_COMMON got disabled on armv7hl
by bugzilla_noreply＠suse.com 02 Jan '23

02 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206782 Bug ID: 1206782 Summary: SND_SOC_QCOM_COMMON got disabled on armv7hl 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: jslaby(a)suse.com QA Contact: qa-bugs(a)suse.de CC: dmueller(a)suse.com, mkubecek(a)suse.com, tiwai(a)suse.com Found By: --- Blocker: --- Due to our: commit a60b1c275c2e99e2b1c9d12a0ce871f2338cf7c6 Author: Takashi Iwai <tiwai(a)suse.de> Date: Mon Nov 30 11:39:07 2020 +0100 Update config files: make CONFIG_SOUNDWIRE=m (bsc#1179201) Also turned it off for unrelated platforms and upstream's (6.1.2 and 6.2-rc1): commit 8d89cf6ff229ff31cd4f73f5b3928564b81fc41e Author: Srinivas Kandagatla <srinivas.kandagatla(a)linaro.org> Date: Thu Nov 24 14:03:51 2022 +0000 ASoC: qcom: cleanup and fix dependency of QCOM_COMMON stable currently has: config/armv7hl/default:# CONFIG_SND_SOC_QCOM_COMMON is not set config/armv7hl/lpae:CONFIG_SND_SOC_QCOM_COMMON=m It needs CONFIG_SOUNDWIRE which is enabled only in lpae. Is this OK? -- You are receiving this mail because: You are the assignee for the bug.

1 1

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

02 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206758 https://bugzilla.suse.com/show_bug.cgi?id=1206758#c5 --- Comment #5 from Takashi Iwai <tiwai(a)suse.com> --- I'd check at first with 6.0 kernel. For example, install the kernel package found in TW history repo: http://download.opensuse.org/history/ and see whether the problem persists. You can find older kernel packages in my OBS kernel repos, too, e.g. OBS home:tiwai:kernel:5.19: http://download.opensuse.org/repositories/home:/tiwai:/kernel:/5.19/standar… -- 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 02 Jan '23

02 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206758 https://bugzilla.suse.com/show_bug.cgi?id=1206758#c4 --- Comment #4 from Pablo Sanchez <pablo(a)blueoakdb.com> --- Suspending my laptop is a recent modification to my workflow. Consequently, I don't know when the issue first cropped up. To check when the issue might have first started, assuming I can suspend, I could test with a Live CD. Is it worth trying Leap 15.4? Reading the feature-set[1], it ships with kernel 5.14.21 Thank you. ::: References ::: [1] - https://en.opensuse.org/Features_15.4 -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

02 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206774 https://bugzilla.suse.com/show_bug.cgi?id=1206774#c6 Gerhard Lorbeer <Gerhard(a)Dr-Lorbeer.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #863767|0 |1 is obsolete| | --- Comment #6 from Gerhard Lorbeer <Gerhard(a)Dr-Lorbeer.de> --- Created attachment 863771 --> https://bugzilla.suse.com/attachment.cgi?id=863771&action=edit hwinfo 6.1 -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

02 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206774 https://bugzilla.suse.com/show_bug.cgi?id=1206774#c5 --- Comment #5 from Gerhard Lorbeer <Gerhard(a)Dr-Lorbeer.de> --- Created attachment 863770 --> https://bugzilla.suse.com/attachment.cgi?id=863770&action=edit hwinfo 6.0 -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

02 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206774 https://bugzilla.suse.com/show_bug.cgi?id=1206774#c4 --- Comment #4 from Gerhard Lorbeer <Gerhard(a)Dr-Lorbeer.de> --- Created attachment 863769 --> https://bugzilla.suse.com/attachment.cgi?id=863769&action=edit dmesg 6.1 -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

02 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206774 https://bugzilla.suse.com/show_bug.cgi?id=1206774#c3 --- Comment #3 from Gerhard Lorbeer <Gerhard(a)Dr-Lorbeer.de> --- Created attachment 863767 --> https://bugzilla.suse.com/attachment.cgi?id=863767&action=edit dmesg 6.0 -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

02 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206774 https://bugzilla.suse.com/show_bug.cgi?id=1206774#c2 --- Comment #2 from Gerhard Lorbeer <Gerhard(a)Dr-Lorbeer.de> --- Created attachment 863766 --> https://bugzilla.suse.com/attachment.cgi?id=863766&action=edit dmesg 6.0 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206575] BUG: kernel NULL pointer dereference
by bugzilla_noreply＠suse.com 02 Jan '23

02 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206575 https://bugzilla.suse.com/show_bug.cgi?id=1206575#c3 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- It's hard to judge, as the dmesg snippet doesn't really show much useful info, as it's a NULL dereference at the early code path... I close this bug as it's not reproduced. Please reopen if this happens again, and hopefully reproducible at will. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206380] intel pseudoraid C220 fails after upgrade to 6.0.12
by bugzilla_noreply＠suse.com 02 Jan '23

02 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206380 https://bugzilla.suse.com/show_bug.cgi?id=1206380#c2 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com Flags| |needinfo?(werwolf131313@gma | |il.com) --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- Could you verify whether the problem persists with 6.1.x TW kernel? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206316] add_drivers+=" i915 " included in /etc/dracut.d/*, cause drm/dri issue(s) that delay initial X startup ~90 seconds
by bugzilla_noreply＠suse.com 02 Jan '23

02 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206316 https://bugzilla.suse.com/show_bug.cgi?id=1206316#c6 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #6 from Takashi Iwai <tiwai(a)suse.com> --- If i915 driver isn't included in initrd automatically even if it's a valid graphics, then that's the problem to be addressed at first. The manual tweak like yours might have some side effect, so likely a WONTFIX issue. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206745] Unnecessary log entries for rtkit
by bugzilla_noreply＠suse.com 02 Jan '23

02 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206745 https://bugzilla.suse.com/show_bug.cgi?id=1206745#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com Component|Kernel |Basesystem Assignee|kernel-bugs(a)opensuse.org |sreeves(a)suse.com --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Reassigned to rtkit package maintainer. -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

02 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206774 https://bugzilla.suse.com/show_bug.cgi?id=1206774#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Gerhard(a)Dr-Lorbeer.de, | |tiwai(a)suse.com Flags| |needinfo?(Gerhard@Dr-Lorbee | |r.de) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Could you give dmesg outputs from both working and non-working cases? Also give the hwinfo outputs from both, too. Please upload the outputs as Bugzilla attachments. -- 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 02 Jan '23

02 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206758 https://bugzilla.suse.com/show_bug.cgi?id=1206758#c3 --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- Is it a regression from the earlier releases? -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

02 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206774 Bug ID: 1206774 Summary: dvb driver fails 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: Gerhard(a)Dr-Lorbeer.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since kernel 6.1.n dvb-driver for older cards (eg SAA7146) failed to load. These cards are installed in many installations of long living vdr's. With new kernel all dvb-server with these cards are bricked. Test to verifiy: Boot with older kernel: driver OK Boot with newer kernel: fail -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206683] kernel 6.1.1 freezes before the gui appears
by bugzilla_noreply＠suse.com 02 Jan '23

02 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206683 https://bugzilla.suse.com/show_bug.cgi?id=1206683#c42 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #42 from Takashi Iwai <tiwai(a)suse.com> --- OK, the fix for the original WiFi problem from Scott has been merged to stable branch for the next TW kernel (along with 6.1.2 update). For rtw88 issue for Dave, it's tracked in another bug 1206767. Let's close the bug entry now. -- You are receiving this mail because: You are the assignee for the bug.

1 0