February 2022 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1196200] New: CONFIG_SYSFB_SIMPLEFB=y in .config prevents booting
by bugzilla_noreply＠suse.com 19 Feb '22

19 Feb '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1196200 Bug ID: 1196200 Summary: CONFIG_SYSFB_SIMPLEFB=y in .config prevents booting 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: seppe.hoogzaad(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The kernel version 5.16.8-1-default has the option CONFIG_SYSFB_SIMPLEFB=y in the config. On my computer this leads to a black screen and no contact. I have to shut down hard to recover. The journal is showing no information about what happened. The kernel 5.16.4-1-default did work fine. There are some changes in the .config between the two versions kernel. Compiling the 5.16.8 kernel with ' #CONFIG_SYSFB_SIMPLEFB not set' boots the system normally. The full diff between the Thumbleweed kernel and the one compiled by me is below. The 5.16.8-seppe- kernel is working fine and does not have the 'CONFIG_SYSFB_SIMPLEFB=y'. # diff /boot/config-5.16.8-1-default /boot/config-5.16.8-seppe- 8d7 < # CONFIG_CC_IS_CLANG is not set 11d9 < # CONFIG_AS_IS_LLVM is not set 15d12 < # CONFIG_LD_IS_LLD is not set 18d14 < # CONFIG_CC_CAN_LINK_STATIC is not set 21d16 < # CONFIG_TOOLS_SUPPORT_RELR is not set 34c29 < CONFIG_LOCALVERSION="-1-default" --- > CONFIG_LOCALVERSION="-seppe-" 446d440 < # CONFIG_VM86 is not set 596d589 < # CONFIG_ACPI_CUSTOM_DSDT is not set 673d665 < # CONFIG_X86_SPEEDSTEP_LIB is not set 685d676 < # CONFIG_ARCH_NEEDS_CPU_IDLE_COUPLED is not set 760d750 < # CONFIG_HAVE_64BIT_ALIGNED_ACCESS is not set 842d831 < # CONFIG_HAVE_ARCH_HASH is not set 847,848d835 < # CONFIG_ARCH_EPHEMERAL_INODES is not set < # CONFIG_CPU_NO_EFFICIENT_FFS is not set 853,854d839 < # CONFIG_ARCH_OPTIONAL_KERNEL_RWX is not set < # CONFIG_ARCH_OPTIONAL_KERNEL_RWX_DEFAULT is not set 1000d984 < # CONFIG_HAVE_AOUT is not set 1034d1017 < # CONFIG_HUGETLB_PAGE_SIZE_VARIABLE is not set 2285d2267 < # CONFIG_GENERIC_CPU_DEVICES is not set 2333,2334c2315 < CONFIG_SYSFB_SIMPLEFB=y < # CONFIG_CS_DSP is not set --- > # CONFIG_SYSFB_SIMPLEFB is not set 2508d2488 < # CONFIG_MTD_NAND_OMAP_BCH_BUILD is not set 2567d2546 < # CONFIG_PARPORT_GSC is not set 2623d2601 < # CONFIG_BLK_DEV_COW_COMMON is not set 3505d3482 < # CONFIG_SMSC911X_ARCH_HOOKS is not set 4403d4379 < # CONFIG_SERIAL_8250_FSL is not set 4519d4494 < CONFIG_CRASHER=m 4602d4576 < # CONFIG_I2C_PXA_PCI is not set 5426d5399 < # CONFIG_MFD_TMIO is not set 6483d6455 < # CONFIG_DRM_LIB_RANDOM is not set 6591d6562 < # CONFIG_VGASTATE is not set 6657d6627 < # CONFIG_SND_OPL4_LIB_SEQ is not set 7085d7054 < # CONFIG_SND_SOC_RT5514_SPI_BUILTIN is not set 7435d7403 < CONFIG_USB_XEN_HCD=m 8545d8512 < # CONFIG_COMMON_CLK_NXP is not set 8547,8567d8513 < # CONFIG_COMMON_CLK_PXA is not set < # CONFIG_COMMON_CLK_PIC32 is not set < # CONFIG_COMMON_CLK_STM32MP157 is not set < # CONFIG_COMMON_CLK_STM32F is not set < # CONFIG_COMMON_CLK_STM32H7 is not set < # CONFIG_COMMON_CLK_MMP2 is not set < # CONFIG_CLK_IMX1 is not set < # CONFIG_CLK_IMX25 is not set < # CONFIG_CLK_IMX27 is not set < # CONFIG_CLK_IMX31 is not set < # CONFIG_CLK_IMX35 is not set < # CONFIG_CLK_IMX5 is not set < # CONFIG_CLK_IMX6Q is not set < # CONFIG_CLK_IMX6SL is not set < # CONFIG_CLK_IMX6SLL is not set < # CONFIG_CLK_IMX6SX is not set < # CONFIG_CLK_IMX6UL is not set < # CONFIG_CLK_IMX7D is not set < # CONFIG_CLK_IMX7ULP is not set < # CONFIG_CLK_VF610 is not set < # CONFIG_CLK_INTEL_SOCFPGA is not set 8577,8580d8522 < # CONFIG_SH_TIMER_CMT is not set < # CONFIG_SH_TIMER_MTU2 is not set < # CONFIG_SH_TIMER_TMU is not set < # CONFIG_EM_TIMER_STI is not set 8676,8677d8617 < # CONFIG_SUNXI_MBUS is not set < # CONFIG_SUNXI_SRAM is not set 9261d9200 < # CONFIG_ARM_GIC_V3_ITS is not set 9269,9276d9207 < # CONFIG_RESET_ATH79 is not set < # CONFIG_RESET_AXS10X is not set < # CONFIG_RESET_LANTIQ is not set < # CONFIG_RESET_LPC18XX is not set < # CONFIG_RESET_NPCM is not set < # CONFIG_RESET_SIMPLE is not set < # CONFIG_RESET_SOCFPGA is not set < # CONFIG_RESET_SUNXI is not set 9278,9279d9208 < # CONFIG_RESET_ZYNQ is not set < # CONFIG_RESET_TEGRA_BPMP is not set 9577d9505 < # CONFIG_ARCH_SUPPORTS_HUGETLBFS is not set 9840d9767 < # CONFIG_SECURITY_WRITABLE_HOOKS is not set 9933,9934d9859 < # CONFIG_CC_HAS_AUTO_VAR_INIT_PATTERN is not set < # CONFIG_CC_HAS_AUTO_VAR_INIT_ZERO is not set 10199c10124 < CONFIG_MODULE_SIG_KEY="/home/abuild/rpmbuild/SOURCES/.kernel_signing_key.pem" --- > CONFIG_MODULE_SIG_KEY="certs/signing_key.pem" 10222d10146 < # CONFIG_HAVE_ARCH_BITREVERSE is not set 10251d10174 < # CONFIG_AUDIT_ARCH_COMPAT_GENERIC is not set 10354d10276 < # CONFIG_SG_SPLIT is not set 10356d10277 < # CONFIG_ARCH_NO_SG_CHAIN is not set 10395,10404c10316 < CONFIG_DEBUG_INFO=y < # CONFIG_DEBUG_INFO_REDUCED is not set < # CONFIG_DEBUG_INFO_COMPRESSED is not set < # CONFIG_DEBUG_INFO_SPLIT is not set < # CONFIG_DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT is not set < CONFIG_DEBUG_INFO_DWARF4=y < CONFIG_DEBUG_INFO_BTF=y < CONFIG_PAHOLE_HAS_SPLIT_BTF=y < CONFIG_DEBUG_INFO_BTF_MODULES=y < # CONFIG_GDB_SCRIPTS is not set --- > # CONFIG_DEBUG_INFO is not set 10481d10392 < # CONFIG_CC_HAS_KASAN_SW_TAGS is not set 10568d10478 < # CONFIG_PROVE_RCU is not set 10760,10775d10669 < < CONFIG_SUSE_KERNEL=y < < # < # SUSE Release Details < # < # CONFIG_SUSE_PRODUCT_SLE is not set < # CONFIG_SUSE_PRODUCT_OPENSUSE_LEAP is not set < CONFIG_SUSE_PRODUCT_OPENSUSE_TUMBLEWEED=y < CONFIG_SUSE_PRODUCT_CODE=3 < CONFIG_SUSE_VERSION=0 < CONFIG_SUSE_PATCHLEVEL=0 < CONFIG_SUSE_AUXRELEASE=0 < # CONFIG_SUSE_KERNEL_SUPPORTED is not set < CONFIG_SUSE_KERNEL_RELEASED=y < # end of SUSE Release Details The version: # cat /etc/os-release NAME="openSUSE Tumbleweed" # VERSION="20220215" -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1172292] [META] Support for 64-bit processors on motherboards with 32-bit UEFI (mixed-mode support)
by bugzilla_noreply＠suse.com 19 Feb '22

19 Feb '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1172292 http://bugzilla.opensuse.org/show_bug.cgi?id=1172292#c10 --- Comment #10 from Neil Rickert <nwr10cst-oslnx(a)yahoo.com> --- The good news is that Leap 15.4 Alpha runs very well on 32-bit UEFI. The bad news is that there is still no installer support (for Leap or for Tumbleweed). -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1175646] After bios update, some keyboard function keys not recognized.
by bugzilla_noreply＠suse.com 19 Feb '22

19 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1175646 https://bugzilla.suse.com/show_bug.cgi?id=1175646#c10 --- Comment #10 from Z B <zhonb(a)yahoo.com> --- kernel.org bug report: https://bugzilla.kernel.org/show_bug.cgi?id=209049 However, I ended up downgrading the BIOS, which fixed the problem. Unfortunately I am unable to test the newest kernel against this bug, and I don't think I'll try updating the BIOS again. I guess this can be closed. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1178639] [nouveau] The plasma login screen freezes on kernel 5.9.1 and later
by bugzilla_noreply＠suse.com 18 Feb '22

18 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1178639 https://bugzilla.suse.com/show_bug.cgi?id=1178639#c28 --- Comment #28 from Pawel <rejestracje(a)pawelpieczyrak.pl> --- I switched hardware a year ago, I'm using opensuse on a virtual machine and it's working for the moment. I do not have the previous hardware to be able to check. Thread to close. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1179971] iwlwifi - "Microcode SW error detected"
by bugzilla_noreply＠suse.com 18 Feb '22

18 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1179971 https://bugzilla.suse.com/show_bug.cgi?id=1179971#c13 --- Comment #13 from H��ctor Sanju��n <code(a)hector.link> --- (In reply to Miroslav Bene�� from comment #12) > Is there anything new to report or discuss? It has been a while and the > latest TW kernels might have helped. Indeed. For me the issue happened when connected to the 5Ghz AP. I have switched back to 5Ghz today and I have not seen a single driver error logged, and connection has worked all day. I have no special modprobe settings (things mentioned here did not work for me back in the day). It would seem that this has been "fixed", at least for me. I'm on 5.16.8-1-default from TW with kernel-firmware-iwlwifi-20220119-1.1.noarch. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1182762] uvcvideo: webcam stops working after 3 seconds
by bugzilla_noreply＠suse.com 18 Feb '22

18 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1182762 https://bugzilla.suse.com/show_bug.cgi?id=1182762#c3 Derek Wickersham <derek(a)wickersham.info> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #3 from Derek Wickersham <derek(a)wickersham.info> --- Updated TW today. myhost:/home/myhost # uname -a Linux myhost 5.16.8-1-default #1 SMP PREEMPT Thu Feb 10 11:31:59 UTC 2022 (5d1f5d2) x86_64 x86_64 x86_64 GNU/Linux Camera behavior remains the same. Feb 18 10:48:58 myhost kernel: usb 1-10: USB disconnect, device number 21 Feb 18 10:48:58 myhost kernel: usb 1-10: new high-speed USB device number 22 using xhci_hcd Feb 18 10:48:59 myhost kernel: usb 1-10: New USB device found, idVendor=1f3a, idProduct=100e, bcdDevice= 2.33 Feb 18 10:48:59 myhost kernel: usb 1-10: New USB device strings: Mfr=2, Product=3, SerialNumber=4 Feb 18 10:48:59 myhost kernel: usb 1-10: Product: Android Feb 18 10:48:59 myhost kernel: usb 1-10: Manufacturer: USB Developer Feb 18 10:48:59 myhost kernel: usb 1-10: SerialNumber: 20080411 Feb 18 10:48:59 myhost kernel: usb 1-10: Found UVC 1.00 device Android (1f3a:100e) Feb 18 10:48:59 myhost kernel: usb 1-10: Failed to query (GET_INFO) UVC control 2 on unit 2: -32 (exp. 1). Feb 18 10:49:04 myhost kernel: usb 1-10: Failed to query (GET_INFO) UVC control 2 on unit 1: -110 (exp. 1). Feb 18 10:49:09 myhost pipewire[3056]: spa.v4l2: '/dev/video0' VIDIOC_QUERYCTRL: Connection timed out Feb 18 10:49:09 myhost kernel: usb 1-10: Failed to query (GET_DEF) UVC control 2 on unit 2: -110 (exp. 2). Feb 18 10:49:17 myhost kernel: usb 1-10: USB disconnect, device number 22 Feb 18 10:49:17 myhost kernel: usb 1-10: new high-speed USB device number 23 using xhci_hcd Feb 18 10:49:18 myhost kernel: usb 1-10: New USB device found, idVendor=1f3a, idProduct=1002, bcdDevice= 2.33 Feb 18 10:49:18 myhost kernel: usb 1-10: New USB device strings: Mfr=2, Product=3, SerialNumber=4 Feb 18 10:49:18 myhost kernel: usb 1-10: Product: Android Feb 18 10:49:18 myhost kernel: usb 1-10: Manufacturer: USB Developer Feb 18 10:49:18 myhost kernel: usb 1-10: SerialNumber: 20080411 Feb 18 10:49:18 myhost kernel: usb-storage 1-10:1.0: USB Mass Storage device detected Feb 18 10:49:18 myhost kernel: scsi host6: usb-storage 1-10:1.0 Feb 18 10:49:18 myhost mtp-probe[4873]: checking bus 1, device 23: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-10" Feb 18 10:49:18 myhost mtp-probe[4873]: bus: 1, device: 23 was not an MTP device Feb 18 10:49:18 myhost mtp-probe[4874]: checking bus 1, device 23: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-10" Feb 18 10:49:18 myhost mtp-probe[4874]: bus: 1, device: 23 was not an MTP device Feb 18 10:49:19 myhost kernel: scsi 6:0:0:0: Direct-Access USB 2.0 USB Flash Driver 0100 PQ: 0 ANSI: 2 Feb 18 10:49:19 myhost kernel: sd 6:0:0:0: Attached scsi generic sg2 type 0 Feb 18 10:49:19 myhost kernel: sd 6:0:0:0: Power-on or device reset occurred Feb 18 10:49:19 myhost kernel: sd 6:0:0:0: [sdb] Media removed, stopped polling Feb 18 10:49:19 myhost kernel: sd 6:0:0:0: [sdb] Attached SCSI removable disk -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188896] "BUG: Bad rss-counter state mm:00000000e555b579 type:MM_FILEPAGES val:-256" during build of cross-epiphany-gcc11-bootstrap
by bugzilla_noreply＠suse.com 18 Feb '22

18 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1188896 https://bugzilla.suse.com/show_bug.cgi?id=1188896#c65 --- Comment #65 from LTC BugProxy <bugproxy(a)us.ibm.com> --- ------- Comment From geraldsc(a)de.ibm.com 2022-02-18 09:58 EDT------- (In reply to comment #61) > > This should not be a problem when we have a dump with panic_on_taint setting, > > as that would immediately stop the system at the interesting part, and not have > > all the follow-on messages. > > well, as you can see in the buildlog file, panic_on_taint=5 is set in the > kernel commandline, it just did not have any effect. Sorry, after looking more closely to the kernel code, TAINT_BAD_PAGE has bit number 5, but the panic_on_taint parameter has to be the "Hexadecimal bitmask representing the set of TAINT flags that will cause the kernel to panic". So that would mean that we need a "panic_on_taint=0x20" parameter instead. BTW, the buildlog also shows a "panic=1" parameter, which would add a 1 sec delay before panic. Since we want to be as close as possible to the detection of "Bad page", you might want to remove that. Is there a reason for setting this timeout? Also, buildlog shows that the "Bad page" did occur, again before all the rest went wrong. It also shows this: [ 84s] Increasing log level from now on... [ 84s] [ 27.967679][ T383] sysrq: Changing Loglevel [ 84s] [ 27.967746][ T383] sysrq: Loglevel set to 4 Would it be possible to set the loglevel to 8, or at least 5, so that you would also see KERN_WARNING messages? All the interesting stuff after "Bad page" will be printed with KERN_WARNING, only the "Bad page" line itself is printed with KERN_ALERT, which is why we only see this line in the buildlog. Given that you seem to have such troubles accessing the kernel message log, I would recommend to permanently change the loglevel to at least 5, better 8, to catch them all in your buildlog. Not sure where you'd need to change that, as it seems to be set during run-time and not by kernel parameter. Or add "ignore_loglevel" kernel parameter, but not entirely sure if run-time setting might override this again. OTOH, you probably have reasons to reduce loglevel, but at least using 5 instead of 4 would give so much more useful kernel messages printed with KERN_WARNING ... -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1196152] New: LED trigger not working for NVMe SSD (prepared patch to be re-worked for upstream acceptance)
by bugzilla_noreply＠suse.com 18 Feb '22

18 Feb '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1196152 Bug ID: 1196152 Summary: LED trigger not working for NVMe SSD (prepared patch to be re-worked for upstream acceptance) 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: yan.huang(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This is a follow-up of the *internal* SUSE Bugzilla ticket bsc#1175287 (LED trigger not working for NVMe SSD). Based on a SUSE customer's request, Enzo Matsumiya prepared this patch: https://lore.kernel.org/linux-block/20210503165026.j2gdk6pfljjo566s@hyori/T/ But it was not accepted by the upstream. This new openSUSE Bugzilla ticket is for Enzo's continuous work on the mentioned patch. Enzo will try the "enable disk trigger only in NVMe" approach - that might be easier to get merged. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1196151] New: LED trigger not working for NVMe SSD (prepared patch to be re-worked for upstream acceptance)
by bugzilla_noreply＠suse.com 18 Feb '22

18 Feb '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1196151 Bug ID: 1196151 Summary: LED trigger not working for NVMe SSD (prepared patch to be re-worked for upstream acceptance) 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: yan.huang(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This is a follow-up of the *internal* SUSE Bugzilla ticket bsc#1175287 (LED trigger not working for NVMe SSD). Based on a SUSE customer's request, Enzo Matsumiya prepared this patch: https://lore.kernel.org/linux-block/20210503165026.j2gdk6pfljjo566s@hyori/T/ But it was not accepted by the upstream. This new openSUSE Bugzilla ticket is for Enzo's continuous work on the mentioned patch. Enzo will try the "enable disk trigger only in NVMe" approach - that might be easier to get merged. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1196153] New: LED trigger not working for NVMe SSD (prepared patch to be re-worked for upstream acceptance)
by bugzilla_noreply＠suse.com 18 Feb '22

18 Feb '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1196153 Bug ID: 1196153 Summary: LED trigger not working for NVMe SSD (prepared patch to be re-worked for upstream acceptance) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: SLES 15 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: yan.huang(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This is a follow-up of the *internal* SUSE Bugzilla ticket bsc#1175287 (LED trigger not working for NVMe SSD). Based on a SUSE customer's request, Enzo Matsumiya prepared this patch: https://lore.kernel.org/linux-block/20210503165026.j2gdk6pfljjo566s@hyori/T/ But it was not accepted by the upstream. This new openSUSE Bugzilla ticket is for Enzo's continuous work on the mentioned patch. Enzo will try the "enable disk trigger only in NVMe" approach - that might be easier to get merged. -- You are receiving this mail because: You are the assignee for the bug.

1 1