April 2023 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1210793] New: Processes stuck waiting jbd2_fc_begin_commit prevent zombies from being killed
by bugzilla_noreply＠suse.com 24 Apr '23

24 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1210793 Bug ID: 1210793 Summary: Processes stuck waiting jbd2_fc_begin_commit prevent zombies from being killed 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: moio(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 866543 --> https://bugzilla.suse.com/attachment.cgi?id=866543&action=edit dmesg output Context: a stress test of Rancher running in k3d, using latest Docker, on an updated openSUSE 15.4 results in the k3s process to die (expected), but its children are not reaped (not expected). Main system partition is ext4 on devicemapper. According to Aleksa, who already gave a first look: "the issue causing the k3s zombie to not be reaped appears to actually be that many processes on the machine (including still-alive threads of the zombie group leader of k3s that isn't being reaped) are stuck waiting in jbd2_fc_begin_commit+0xef/0x120 (waiting for journal->j_fc_wait ) and kjournald2 also appears to be stuck in jbd2_journal_commit_transaction+0x16b/0x1a90 (which is also waiting for journal->j_fc_wait )" `echo w >/proc/sysrq-trigger` was executed after a fresh reboot and the immediate reproduction of the issue - full dmesg output is attached. A kernel dump was also collected via `echo c >/proc/sysrq-trigger` immediately afterwards, and the result is attached. (Switching to the rescue target and proceeding from there, as recommended in https://documentation.suse.com/sles/15-SP4/single-html/SLES-tuning/#cha-tun…, was attempted but did not work, specifically starting kdump would hang indefinitely). Dump is available at: https://mysuse-my.sharepoint.com/:f:/g/personal/moio_suse_com/EpT94_BHipJAs… For reference, the main zombie process in the files above has PID 7276: root 7276 19.9 0.0 0 0 ? Zl 18:45 1:36 [k3s] <defunct> I remain available for any other information and I am open to offer a tmate session if that helps. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1202244] Battery charging even though there is not charger
by bugzilla_noreply＠suse.com 24 Apr '23

24 Apr '23

http://bugzilla.suse.com/show_bug.cgi?id=1202244 http://bugzilla.suse.com/show_bug.cgi?id=1202244#c9 --- Comment #9 from Takashi Iwai <tiwai(a)suse.com> --- Also, is this a regression from earlier versions? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1202244] Battery charging even though there is not charger
by bugzilla_noreply＠suse.com 24 Apr '23

24 Apr '23

http://bugzilla.suse.com/show_bug.cgi?id=1202244 http://bugzilla.suse.com/show_bug.cgi?id=1202244#c8 --- Comment #8 from Takashi Iwai <tiwai(a)suse.com> --- Thanks. Could you try to blacklist ucsi_acpi module? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1202244] Battery charging even though there is not charger
by bugzilla_noreply＠suse.com 24 Apr '23

24 Apr '23

http://bugzilla.suse.com/show_bug.cgi?id=1202244 http://bugzilla.suse.com/show_bug.cgi?id=1202244#c7 --- Comment #7 from Cosmin Tanczel <cosmin.tanczel(a)gmail.com> --- Created attachment 866538 --> http://bugzilla.suse.com/attachment.cgi?id=866538&action=edit dmesg -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1202244] Battery charging even though there is not charger
by bugzilla_noreply＠suse.com 24 Apr '23

24 Apr '23

http://bugzilla.suse.com/show_bug.cgi?id=1202244 http://bugzilla.suse.com/show_bug.cgi?id=1202244#c6 Cosmin Tanczel <cosmin.tanczel(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(cosmin.tanczel@gm | |ail.com) | --- Comment #6 from Cosmin Tanczel <cosmin.tanczel(a)gmail.com> --- Created attachment 866537 --> http://bugzilla.suse.com/attachment.cgi?id=866537&action=edit hwinfo -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1202244] Battery charging even though there is not charger
by bugzilla_noreply＠suse.com 24 Apr '23

24 Apr '23

http://bugzilla.suse.com/show_bug.cgi?id=1202244 http://bugzilla.suse.com/show_bug.cgi?id=1202244#c5 --- Comment #5 from Takashi Iwai <tiwai(a)suse.com> --- Then please provide the information requested in comment 2. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1202244] Battery charging even though there is not charger
by bugzilla_noreply＠suse.com 24 Apr '23

24 Apr '23

http://bugzilla.suse.com/show_bug.cgi?id=1202244 http://bugzilla.suse.com/show_bug.cgi?id=1202244#c4 Cosmin Tanczel <cosmin.tanczel(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #4 from Cosmin Tanczel <cosmin.tanczel(a)gmail.com> --- Did some more investigation on this one and it seems that nano Yubikey presence makes the system think it has a power charger plugged in. If I remove the Yubikey from the laptop, the system runs fine, otherwise it things a charger is connected but the delivered power is not enough. Since I configured the power-profile to change to/from Performance and Balanced depending on the charger presence, this affects the battery performance since the system will never switch to/from Performance/Balance while the Yubikey is inserted. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1210639] New: Kernel 6.2+ fails to boot on Intel Atom x5-Z8300
by bugzilla_noreply＠suse.com 24 Apr '23

24 Apr '23

http://bugzilla.suse.com/show_bug.cgi?id=1210639 Bug ID: 1210639 Summary: Kernel 6.2+ fails to boot on Intel Atom x5-Z8300 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: filippo.bonazzi(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Ever since the update to kernel 6.2 my MicroOS Desktop install on an old Intel Atom x5-Z8300 netbook fails to boot. It was working fine up to kernels 6.1.X. This is what I see at boot: [16.358810][ T587] atomisp-isp2 0000:00:03.0: atomisp: Error -2 while requesting firmware shisp_2401a0_v21.bin ^ this line was present at boot on older kernels too, but it still worked [16.414042][ T587] atomisp-isp2 0000:00:03.0: IUNIT power-off timeout. [16.414108][ T587] atomisp-isp2 0000:00:03.0: Failed to switch off ISP And it just freezes there. Sometimes I've also seen a line at the end such as this one: [...] watchdog: BUG: soft lockup - CPU#... stuck for ...s! but this line is not showing up right now that I'm trying to report it. This appears to be the same bug that someone else reported for Ubuntu https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015794 -- You are receiving this mail because: You are the assignee for the bug.

1 11

[Bug 1210718] Laptop charging broken after kernel update to 5.14.21-150400.24.60
by bugzilla_noreply＠suse.com 24 Apr '23

24 Apr '23

http://bugzilla.suse.com/show_bug.cgi?id=1210718 http://bugzilla.suse.com/show_bug.cgi?id=1210718#c2 Tengström <ordermind(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #2 from Tengström <ordermind(a)gmail.com> --- After debugging this a little bit further, it seems that the fact that it worked after downgrading the kernel was a bit of a coincidence. This turned out to be an issue with the power cord/adapter so I will close this issue. Thanks for your time! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1210698] Superblock checksum does not match when resizing ext4 file system twice in a row
by bugzilla_noreply＠suse.com 24 Apr '23

24 Apr '23

http://bugzilla.suse.com/show_bug.cgi?id=1210698 http://bugzilla.suse.com/show_bug.cgi?id=1210698#c1 Jan Kara <jack(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS Priority|P5 - None |P3 - Medium Assignee|kernel-bugs(a)opensuse.org |jack(a)suse.com --- Comment #1 from Jan Kara <jack(a)suse.com> --- Thanks for report. It seems we are missing upstream commit a408f33e895 ("ext4: fix bad checksum after online resize"). As I've checked it was reported in our git-fixes process but I didn't get to backporting it yet. I'll look into it. -- You are receiving this mail because: You are the assignee for the bug.

1 0