October 2024 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1225890] [tw][Build 20240531] sysctl kernel parameter 'sysctl: cannot stat /proc/sys/kernel/sched_child_runs_first: No such file or directory'
by bugzilla_noreply＠suse.com 25 Oct '24

25 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1225890 Jozef Pupava <jpupava(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|INVALID |UPSTREAM -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1225893] [tw][Build 20240531] Sysctl 'Sysctl_net_core_optmem_max' value is changed
by bugzilla_noreply＠suse.com 25 Oct '24

25 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1225893 https://bugzilla.suse.com/show_bug.cgi?id=1225893#c1 Jozef Pupava <jpupava(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |UPSTREAM CC| |jpupava(a)suse.com --- Comment #1 from Jozef Pupava <jpupava(a)suse.com> --- Probably changed with kernel update [1] Generally the value is increased e.g. [2] * Thu Sep 01 2022 jslaby(a)suse.cz - Linux 5.19.6 (bsc#1012628). ... - net: Fix data-races around sysctl_optmem_max (bsc#1012628). [1] https://bugzilla.suse.com/show_bug.cgi?id=1012628 [2] https://patchwork.kernel.org/project/linux-crypto/patch/02fd8c825b9d77bfc6c… https://github.com/openSUSE/sys-param-check/pull/23 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1225892] [tw][Build 20240531] sysctl 'Sysctl_kernel_yama_ptrace_scope' value is changed
by bugzilla_noreply＠suse.com 25 Oct '24

25 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1225892 https://bugzilla.suse.com/show_bug.cgi?id=1225892#c1 Jozef Pupava <jpupava(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |UPSTREAM CC| |jpupava(a)suse.com --- Comment #1 from Jozef Pupava <jpupava(a)suse.com> --- * Fri Apr 15 2022 dmueller(a)suse.com - Update config files (bsc#1198722, bsc#1197746). Enable compiled in LSMs on boot * landlock: optional ability for user land applications to sandbox themselves * yama: optional restrict of use of ptrace for nonprivileged users * default to apparmor, list selinux before bpf to avoid bsc#1197746 * bpf: create eBPF based LSMs dynamically - commit 5506937 https://github.com/openSUSE/sys-param-check/pull/23 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1225890] [tw][Build 20240531] sysctl kernel parameter 'sysctl: cannot stat /proc/sys/kernel/sched_child_runs_first: No such file or directory'
by bugzilla_noreply＠suse.com 25 Oct '24

25 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1225890 https://bugzilla.suse.com/show_bug.cgi?id=1225890#c2 Jozef Pupava <jpupava(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |jpupava(a)suse.com Resolution|--- |INVALID --- Comment #2 from Jozef Pupava <jpupava(a)suse.com> --- Looks like part of kernel update https://bugzilla.suse.com/show_bug.cgi?id=1012628 sched_child_runs_first was removed on [1] after [2] [1] https://lore.kernel.org/all/20230920130025.412071-2-bigeasy@linutronix.de/ [2] https://lore.kernel.org/all/20230531124604.137187212@infradead.org/ https://github.com/openSUSE/sys-param-check/pull/23 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231247] PPC64LE: bcc test fails when executing btrfsdist
by bugzilla_noreply＠suse.com 25 Oct '24

25 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231247 Héctor Orón Martínez <hector.oron(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1232292] Machine locks on restore from hibernation after upgrade to kernel-default 5.14.21-150500.55.83-default
by bugzilla_noreply＠suse.com 25 Oct '24

25 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1232292 https://bugzilla.suse.com/show_bug.cgi?id=1232292#c2 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- . *** This bug has been marked as a duplicate of bug 1231578 *** -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1232342] No Ethernet device anymore on RPi3
by bugzilla_noreply＠suse.com 25 Oct '24

25 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1232342 https://bugzilla.suse.com/show_bug.cgi?id=1232342#c2 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- Do you have the dmesg output from the working case, too? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1232342] New: No Ethernet device anymore on RPi3
by bugzilla_noreply＠suse.com 25 Oct '24

25 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1232342 Bug ID: 1232342 Summary: No Ethernet device anymore on RPi3 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: aarch64 URL: https://openqa.opensuse.org/tests/4593773/modules/prep are_firstboot/steps/1 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-15.6-JeOS-for-RPi-aarch64-jeos@RPi3 fails in [prepare_firstboot](https://openqa.opensuse.org/tests/4593773/modules/prepar… Since build 13.376 Leap 15.6 fails to boot RPi3 in openQA. Same problem with Leap 15.5 since build 13.326: https://openqa.opensuse.org/tests/4591682#next_previous Serial connection showed that the problem is Ethernet device is not found (for both Leap 15.5 and 15.6). ## Test suite description Maintainer: fvogt Start JeOS from the HDD image, configure it using the firstboot wizard and then run basic tests. console=tty0 added as needed for aarch64. ## Reproducible Fails since (at least) Build [13.376](https://openqa.opensuse.org/tests/4545136) ## Expected result Last good: [13.375](https://openqa.opensuse.org/tests/4542889) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=aarch64&distri=opensu… -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1225352] [Build 13.199] openQA test fails in prepare_firstboot: RPi3 not booting?
by bugzilla_noreply＠suse.com 25 Oct '24

25 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c52 --- Comment #52 from Guillaume GARDET <guillaume.gardet(a)arm.com> --- (In reply to Fabian Vogt from comment #51) > (In reply to Guillaume GARDET from comment #49) > > Created attachment 878195 [details] > > 15.5 log for no eth0 > > > > A quick check shows eth0 is not found: > > That's bad. Can you create a new bug report for this? Tracked in https://bugzilla.opensuse.org/show_bug.cgi?id=1232342 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1225352] [Build 13.199] openQA test fails in prepare_firstboot: RPi3 not booting?
by bugzilla_noreply＠suse.com 25 Oct '24

25 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c51 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|REOPENED |RESOLVED --- Comment #51 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Guillaume GARDET from comment #49) > Created attachment 878195 [details] > 15.5 log for no eth0 > > A quick check shows eth0 is not found: That's bad. Can you create a new bug report for this? -- You are receiving this mail because: You are the assignee for the bug.

1 0