November 2022 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1204342] MATE CPU Frequency Monitoring stuck at lowest CPU speed
by bugzilla_noreply＠suse.com 03 Nov '22

03 Nov '22

1 0

[Bug 1204342] MATE CPU Frequency Monitoring stuck at lowest CPU speed
by bugzilla_noreply＠suse.com 03 Nov '22

03 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1204342 http://bugzilla.opensuse.org/show_bug.cgi?id=1204342#c2 --- Comment #2 from Larry Rainey <llrainey15(a)gmail.com> --- I can confirm that this displays the correct CPU frequencies in Tumbleweed: cat /proc/cpuinfo | grep MHz | awk -F: '{ print $2}' | awk -F"." '{ ORS="" ; print $1 }' -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204342] MATE CPU Frequency Monitoring stuck at lowest CPU speed
by bugzilla_noreply＠suse.com 03 Nov '22

03 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204342 https://bugzilla.suse.com/show_bug.cgi?id=1204342#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |llrainey15(a)gmail.com, | |tiwai(a)suse.com Flags| |needinfo?(llrainey15@gmail. | |com) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Sounds more like an issue of the applet. Which package is it? You can check other means (e.g. powertop) for verifying whether the TW kernel reports properly or not, too. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204854] New: tpm tpm0: invalid TPM_STS.x 0xff, dumping stack for forensics
by bugzilla_noreply＠suse.com 03 Nov '22

03 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204854 Bug ID: 1204854 Summary: tpm tpm0: invalid TPM_STS.x 0xff, dumping stack for forensics Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Starting with openSUSE Tumbleweed 20221027 I get error messages regarding the TPM of my notebook (see below): kernel: efi: ACPI=0x62bfe000 ACPI 2.0=0x62bfe014 SMBIOS=0x5e922000 TPMFinalLog=0x628d8000 ESRT=0x5e8a4818 MEMATTR=0x595db018 MOKvar=0x597c3000 RNG=0x5e8a5b18 TPMEventLog=0x595d4018 kernel: ACPI: TPM2 0x0000000062BFD000 00004C (v04 DELL Dell Inc 00000002 01000013) kernel: ACPI: Reserving TPM2 table memory at [mem 0x62bfd000-0x62bfd04b] kernel: tpm_tis STM0125:00: 2.0 TPM (device-id 0x0, rev-id 78) kernel: tpm tpm0: invalid TPM_STS.x 0xff, dumping stack for forensics kernel: CPU: 6 PID: 1 Comm: swapper/0 Not tainted 6.0.3-1-default #1 openSUSE Tumbleweed 50a6ebc5cb1873d6b9c639843cdd1ed0089a1281 kernel: Hardware name: Dell Inc. XPS 13 9310 2-in-1/0NVVG0, BIOS 2.12.0 07/05/2022 kernel: Call Trace: kernel: <TASK> kernel: dump_stack_lvl+0x44/0x5c kernel: tpm_tis_status.cold+0x19/0x1e kernel: tpm_tis_send_data+0x3e/0x260 kernel: tpm_tis_send_main+0x33/0x130 kernel: tpm_transmit+0xd4/0x3e0 kernel: tpm_transmit_cmd+0x25/0x90 kernel: tpm2_pcr_read+0x177/0x300 kernel: tpm_pcr_read+0x59/0x70 kernel: ima_calc_boot_aggregate_tfm+0x10e/0x190 kernel: ? _prb_read_valid+0x22d/0x2a0 kernel: ? prb_read_valid+0x17/0x20 kernel: ? desc_read_finalized_seq+0x2f/0x90 kernel: ? console_emit_next_record.constprop.0+0x62/0x280 kernel: ? _prb_read_valid+0x22d/0x2a0 kernel: ima_calc_boot_aggregate+0xc3/0xf0 kernel: ? hash_setup+0xc7/0xc7 kernel: ima_add_boot_aggregate+0xb0/0x143 kernel: ima_init+0x5e/0xa9 kernel: init_ima+0x22/0xb1 kernel: ? hash_setup+0xc7/0xc7 kernel: do_one_initcall+0x41/0x200 kernel: kernel_init_freeable+0x223/0x27f kernel: ? rest_init+0xd0/0xd0 kernel: kernel_init+0x16/0x130 kernel: ret_from_fork+0x1f/0x30 kernel: </TASK> Operating System: openSUSE Tumbleweed 20221027 Kernel Version: 6.0.3-1-default (64-bit) Graphics Platform: X11 Processors: 8 �� 11th Gen Intel�� Core�� i7-1165G7 @ 2.80GHz Memory: 15,0 GiB of RAM Graphics Processor: Mesa Intel�� Xe Graphics Manufacturer: Dell Inc. Product Name: XPS 13 9310 2-in-1 -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1191784] update of kernel shows message in dracut processing; no modules crc32c and bcm2835-sdhost
by bugzilla_noreply＠suse.com 03 Nov '22

03 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1191784 http://bugzilla.opensuse.org/show_bug.cgi?id=1191784#c4 Thomas Zimmermann <tzimmermann(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tzimmermann(a)suse.com --- Comment #4 from Thomas Zimmermann <tzimmermann(a)suse.com> --- When I install a kernel, I can see that error message happening for bmc2835-dma. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1202950] radeon [Radeon 6450] Blank screen (Kernel driver regression on Leap 15.4)
by bugzilla_noreply＠suse.com 03 Nov '22

03 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1202950 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Offline Upgrade to 15.4 |radeon [Radeon 6450] Blank |stops before starting |screen (Kernel driver |installer |regression on Leap 15.4) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1202950] Offline Upgrade to 15.4 stops before starting installer
by bugzilla_noreply＠suse.com 03 Nov '22

03 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1202950 http://bugzilla.opensuse.org/show_bug.cgi?id=1202950#c22 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tzimmermann(a)suse.com Component|X.Org |Kernel Assignee|gfx-bugs(a)suse.de |kernel-bugs(a)opensuse.org QA Contact|gfx-bugs(a)suse.de |qa-bugs(a)suse.de --- Comment #22 from Stefan Dirsch <sndirsch(a)suse.com> --- Kernel issue. Reassigning. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204315] [RPi] Kernel 6.0 - [drm] *ERROR* could not acquire memory range
by bugzilla_noreply＠suse.com 02 Nov '22

02 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204315 https://bugzilla.suse.com/show_bug.cgi?id=1204315#c26 --- Comment #26 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- (In reply to Thomas Zimmermann from comment #24) > > The term *ERROR* in the bug report is somewhat misleading. This is what kernel log shows. git show 4aae79f77e3a9c53b225a5b2c35951f568156eee :-) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1196357] [riscv64][Unmatched] system boot takes long time at efistub
by bugzilla_noreply＠suse.com 02 Nov '22

02 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1196357 https://bugzilla.suse.com/show_bug.cgi?id=1196357#c7 Chester Lin <chester.lin(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #7 from Chester Lin <chester.lin(a)suse.com> --- Checked the DT and found that the uSD device is MMC_SPI: ------- localhost:~ # hexdump -C /sys/firmware/devicetree/base/soc/spi@10050000/mmc@0/compatible 00000000 6d 6d 63 2d 73 70 69 2d 73 6c 6f 74 00 |mmc-spi-slot.| 0000000d ------- Kernel log while probing mmc: localhost:~ # dmesg | grep SD [ 16.791410] mmc_spi spi1.0: SD/MMC host mmc0, no DMA, no WP, no poweroff [ 16.849477] mmc0: new SDHC card on SPI -------- It looks like a hardware limitation since Unmatched relies on SPI interface to access cards and there's no dedicated SD/SDIO controller on the board. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204315] [RPi] Kernel 6.0 - [drm] *ERROR* could not acquire memory range
by bugzilla_noreply＠suse.com 02 Nov '22

02 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204315 https://bugzilla.suse.com/show_bug.cgi?id=1204315#c25 --- Comment #25 from Thomas Zimmermann <tzimmermann(a)suse.com> --- Hi, if we absolutely want to fix that with code, we could disable sysfb after registering the first simple-framebuffer at [1]. By invoking sysfb_disable(), [2] no devices will be created from EFI framebuffers; hence no error. I still think we should simply set CONFIG_SYSFB=n if possible. Once I have my RPi3 build ready, I'll try either option. [1] https://elixir.bootlin.com/linux/v6.0.6/source/drivers/of/platform.c#L587 [2] https://elixir.bootlin.com/linux/v6.0.6/source/drivers/firmware/sysfb.c#L63 -- You are receiving this mail because: You are the assignee for the bug.

1 0