March 2023 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1208944] Kernel 6.2.0-1-default does not boot on tumbleweed
by bugzilla_noreply＠suse.com 08 Mar '23

08 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1208944 https://bugzilla.suse.com/show_bug.cgi?id=1208944#c9 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(kesang.neljor@yah | |oo.com) --- Comment #9 from Jiri Slaby <jslaby(a)suse.com> --- Other than mmconfig disabled and lockdown changes, I see nothing obvious: +efi: Remove mem92: MMIO range=[0xc0000000-0xcfffffff] (256MB) from e820 map +e820: remove [mem 0xc0000000-0xcfffffff] reserved -LSM: Security Framework initializing +LSM: initializing lsm=lockdown,capability,integrity,apparmor -PCI: MMCONFIG at [mem 0xc0000000-0xce0fffff] reserved in E820 +PCI: not using MMCONFIG -ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) +ata1: SATA link down (SStatus 4 SControl 300) But lockdown was enabled only with 6.2.1 and this failed for you in 6.2.0 already. Is 6.1.x broken the same way if you artificially disable mmconfig using nommconf kernel parameter? There could be also a scsi/block layer bug, of course. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1208944] Kernel 6.2.0-1-default does not boot on tumbleweed
by bugzilla_noreply＠suse.com 08 Mar '23

08 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1208944 https://bugzilla.suse.com/show_bug.cgi?id=1208944#c8 --- Comment #8 from Jiri Slaby <jslaby(a)suse.com> --- Created attachment 865355 --> https://bugzilla.suse.com/attachment.cgi?id=865355&action=edit dmesg 6.2.1 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1208944] Kernel 6.2.0-1-default does not boot on tumbleweed
by bugzilla_noreply＠suse.com 08 Mar '23

08 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1208944 https://bugzilla.suse.com/show_bug.cgi?id=1208944#c7 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(kesang.neljor@yah | |oo.com) | --- Comment #7 from Jiri Slaby <jslaby(a)suse.com> --- Created attachment 865354 --> https://bugzilla.suse.com/attachment.cgi?id=865354&action=edit dmesg 6.1.8 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209032] New: Keychron K8 kearboard kernel warning: unknown main item tag 0x0
by bugzilla_noreply＠suse.com 08 Mar '23

08 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209032 Bug ID: 1209032 Summary: Keychron K8 kearboard kernel warning: unknown main item tag 0x0 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Minor Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: mpdesouza(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I'm using a Keychron K8 keyboard connected via Bluetooth using the "Windows compatibility mode", and started seeing this on dmesg: [100376.456869] apple 0005:05AC:024F.001B: unknown main item tag 0x0 [100376.457182] apple 0005:05AC:024F.001B: Non-apple keyboard detected; function keys will default to fnmode=2 behavior [100376.457264] input: Keychron K8 as /devices/pci0000:00/0000:00:14.0/usb2/2-10/2-10:1.0/bluetooth/hci0/hci0:768/0005:05AC:024F.001B/input/input64 [100376.462635] apple 0005:05AC:024F.001B: input,hidraw7: BLUETOOTH HID v1.07 Keyboard [Keychron K8] on d4:54:8b:88:20:42 I'm running an updates TW system, kernel 6.2.1-1-default. I started to check the hid-core, on hid_parser_main: ... switch (item->tag) { case HID_MAIN_ITEM_TAG_BEGIN_COLLECTION: ret = open_collection(parser, data & 0xff); break; case HID_MAIN_ITEM_TAG_END_COLLECTION: ret = close_collection(parser); break; case HID_MAIN_ITEM_TAG_INPUT: ret = hid_add_field(parser, HID_INPUT_REPORT, data); break; case HID_MAIN_ITEM_TAG_OUTPUT: ret = hid_add_field(parser, HID_OUTPUT_REPORT, data); break; case HID_MAIN_ITEM_TAG_FEATURE: ret = hid_add_field(parser, HID_FEATURE_REPORT, data); break; default: hid_warn(parser->device, "unknown main item tag 0x%x\n", item->tag); ret = 0; } ... But I don't know the HID protocols in order to detect what is the issue. I can only check that, all these case statements search for a value that is bigger than 0, actually values from 8 to 12. Please let me know if I can provide more information to understand what's going on. Thanks -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1209006] Document how to secureboot-sign manually-built kernel modules on TW kernel >= 6.2.1
by bugzilla_noreply＠suse.com 07 Mar '23

07 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209006 https://bugzilla.suse.com/show_bug.cgi?id=1209006#c8 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |epistemepromeneur(a)free.fr --- Comment #8 from Stefan Dirsch <sndirsch(a)suse.com> --- *** Bug 1208939 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209006] Document how to secureboot-sign manually-built kernel modules on TW kernel >= 6.2.1
by bugzilla_noreply＠suse.com 07 Mar '23

07 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209006 https://bugzilla.suse.com/show_bug.cgi?id=1209006#c7 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |brunopitrus(a)hotmail.com --- Comment #7 from Stefan Dirsch <sndirsch(a)suse.com> --- *** Bug 1208966 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209006] Document how to secureboot-sign manually-built kernel modules on TW kernel >= 6.2.1
by bugzilla_noreply＠suse.com 07 Mar '23

07 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209006 https://bugzilla.suse.com/show_bug.cgi?id=1209006#c6 --- Comment #6 from Michal Suchanek <msuchanek(a)suse.com> --- On Leap we don't need the secondary keyring at all, we have a downstream patch that loads the MOK keys into platform keyring, and verifies modules with platform keyring. In upstream the MOK keys are loaded into machine keyring which then should get loaded into secondary keyring. This option is for loading additional keys (which the name does not reflect) in a specific way different from the default (which the name does not reflect) and is incompatible with machine keyring (which would have to be patched out to enable it). Does not seem to work for me, anyway: cat /proc/keys | grep machine 31db47ec I------ 1 perm 1f0b0000 0 0 keyring .machine: empty -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209006] Document how to secureboot-sign manually-built kernel modules on TW kernel >= 6.2.1
by bugzilla_noreply＠suse.com 07 Mar '23

07 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209006 https://bugzilla.suse.com/show_bug.cgi?id=1209006#c5 --- Comment #5 from Stefan Dirsch <sndirsch(a)suse.com> --- At least on Leap 15.4, where signed kernel modules work, it's set. 15.4 $ zcat /proc/config.gz |grep CONFIG_IMA_KEY CONFIG_IMA_KEYRINGS_PERMIT_SIGNED_BY_BUILTIN_OR_SECONDARY=y whereas on TW it's not. TW $ zcat /proc/config.gz |grep CONFIG_IMA_KEYRINGS_PERMIT_SIGNED_BY_BUILTIN_OR_SECONDARY # CONFIG_IMA_KEYRINGS_PERMIT_SIGNED_BY_BUILTIN_OR_SECONDARY is not set -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209006] Document how to secureboot-sign manually-built kernel modules on TW kernel >= 6.2.1
by bugzilla_noreply＠suse.com 07 Mar '23

07 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209006 https://bugzilla.suse.com/show_bug.cgi?id=1209006#c4 --- Comment #4 from Stefan Dirsch <sndirsch(a)suse.com> --- Michal Suchanek just wrote in the email thread on factory ML --- Shouldn't this be set: config/x86_64/default:# CONFIG_IMA_KEYRINGS_PERMIT_SIGNED_BY_BUILTIN_OR_SECONDARY is not set The MOK keys get added to th secondary keyring, not primary. --- Could this be the issue here? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209024] file terminated with sigsys
by bugzilla_noreply＠suse.com 07 Mar '23

07 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209024 https://bugzilla.suse.com/show_bug.cgi?id=1209024#c3 Michal Suchanek <msuchanek(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #3 from Michal Suchanek <msuchanek(a)suse.com> --- Works with later kernel: Linux jostaberry-5 6.3.0-rc1-1-kvmsmall+ #1 SMP Tue Mar 7 18:47:04 CET 2023 ppc64le ppc64le ppc64le GNU/Linux file /etc/uefi/certs/1F673297.crt /etc/uefi/certs/1F673297.crt: Certificate, Version=3, Serial=00fabed8bf409a5e65, Issuer=openSUSE Secure Boot CA -- You are receiving this mail because: You are the assignee for the bug.

1 0