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 02 Nov '22

02 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 02 Nov '22

02 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

[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#c24 --- Comment #24 from Thomas Zimmermann <tzimmermann(a)suse.com> --- Hi (In reply to Andreas F�rber from comment #23) > (In reply to Takashi Iwai from comment #22) > > The kernel should avoid setting such a known bad config combo, or at least, > > it should give more useful information at runtime if the known bad kconfig > > combo must be still applicable. > > Wouldn't the best solution be to implement efifb as drm driver? > I assume it uses runtime callback hooks beyond just accessing the memory > area like simpledrm does. I considered the idea of implementing some sort of 'efidrm'. It's not really the fix here, but would make the whole situation less confusing. > > Also, I would ask to avoid upstream fixes as depending on "ARM" just because > we happened to encounter it there - please make it !X86 or whatever > applicable. RISC-V, C-Sky or MIPS may well run into similar > simple-framebuffer issues. The term *ERROR* in the bug report is somewhat misleading. There's nothing broken here, there's no loss of functionality. It's a minor problem with how we deal with the framebuffer resource. Is is possible that the ARM EFI stubs create the EFI framebuffer from some other source than the DT's simple-framebuffer node? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204786] Boot is hanging when intel Ethernet Controller I225-LM [8086:15f2] is enabled
by bugzilla_noreply＠suse.com 02 Nov '22

02 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204786 https://bugzilla.suse.com/show_bug.cgi?id=1204786#c6 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com Flags| |needinfo?(bechir.kahla@suse | |.com) --- Comment #6 from Takashi Iwai <tiwai(a)suse.com> --- Could you check whether it's a regression in the update kernel? That is, install the old Leap 15.4 GA kernel and confirm the behavior. Also, please check with the latest kernel in OBS Kernel:SLE15-SP4 repo, too. http://download.opensuse.org/repositories/Kernel:/SLE15-SP4/pool/ -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204952] System crashes when booting first time after kernel update
by bugzilla_noreply＠suse.com 02 Nov '22

02 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204952 https://bugzilla.suse.com/show_bug.cgi?id=1204952#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Well, this doesn't mean that it's a kernel bug at all... Such a reboot could be triggered by other means, too. If you have an evidence of a kernel crash, or better the stack trace of a crash, we can go further for analysis. But without that info, it's basically no way to diagnose, unfortunately. -- 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#c23 --- Comment #23 from Andreas F�rber <afaerber(a)suse.com> --- (In reply to Takashi Iwai from comment #22) > The kernel should avoid setting such a known bad config combo, or at least, > it should give more useful information at runtime if the known bad kconfig > combo must be still applicable. Wouldn't the best solution be to implement efifb as drm driver? I assume it uses runtime callback hooks beyond just accessing the memory area like simpledrm does. Also, I would ask to avoid upstream fixes as depending on "ARM" just because we happened to encounter it there - please make it !X86 or whatever applicable. RISC-V, C-Sky or MIPS may well run into similar simple-framebuffer issues. -- 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#c22 --- Comment #22 from Takashi Iwai <tiwai(a)suse.com> --- Well, if a driver is broken with an allowed set of kconfig and if you know that the combination breaks, it can be called as a "bug" to be fixed -- leaving it as-is is no solution at all, even if we work around by disabling a certain kconfig for a certain platform. The kernel should avoid setting such a known bad config combo, or at least, it should give more useful information at runtime if the known bad kconfig combo must be still applicable. -- 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#c21 --- Comment #21 from Thomas Zimmermann <tzimmermann(a)suse.com> --- Hi (In reply to Takashi Iwai from comment #20) > Then how would you "fix" it in the upstream side? It shouldn't rely on the > random kconfig choice done by user. No fix needed. > > (In reply to Thomas Zimmermann from comment #19) > > (In reply to Thomas Zimmermann from comment #18) > > > (In reply to Takashi Iwai from comment #17) > > > > Then maybe better to have as Kconfig dependency, e.g. > > > > > > > > --- a/drivers/gpu/drm/tiny/Kconfig > > > > +++ b/drivers/gpu/drm/tiny/Kconfig > > > > @@ -69,6 +69,7 @@ config DRM_PANEL_MIPI_DBI > > > > config DRM_SIMPLEDRM > > > > tristate "Simple framebuffer driver" > > > > depends on DRM && MMU > > > > + depends on SYSFB=n > > > > select APERTURE_HELPERS > > > > select DRM_GEM_SHMEM_HELPER > > > > select DRM_KMS_HELPER > > > > > > Why? It has nothing to do with the driver. > > > > It would, BTW, prevent it from being used on x86, etc. > > Why x86 still needs sysfb when simpledrmfb is enabled? Do you think of the > situation to allow user switching via boot option or such? sysfb is the component that creates the platform device for the EFI framebuffer. simpledrm is the driver that binds to that device. > > And, what did you have in mind by "disabling CONFIG_SYSFB"? > If it were only about ARM, you can put a restriction in the kconfig, too. Setting CONFIG_SYSFB=n in our for arm-based platforms kernel config should resolve the warning. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1196373] JeOS: proc-sys-fs-binfmt_misc.mount: failed
by bugzilla_noreply＠suse.com 02 Nov '22

02 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1196373 http://bugzilla.opensuse.org/show_bug.cgi?id=1196373#c24 Martin Loviska <mloviska(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mloviska(a)suse.com --- Comment #24 from Martin Loviska <mloviska(a)suse.com> --- (In reply to Fabian Vogt from comment #7) > We definitely need that in kernel-default-base. > > Fixed with https://build.opensuse.org/request/show/958417. Can it be added to sles[1] as well, please? https://openqa.suse.de/tests/9823967#step/df01_sh/6 I think we are also missing these: > nfs_layout_.* quota_.* [1] https://build.suse.de/package/view_file/SUSE:SLE-15-SP5:GA/kernel-default-b… -- 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#c20 --- Comment #20 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Thomas Zimmermann from comment #18) > (In reply to Takashi Iwai from comment #17) > > Then maybe better to have as Kconfig dependency, e.g. > > > > --- a/drivers/gpu/drm/tiny/Kconfig > > +++ b/drivers/gpu/drm/tiny/Kconfig > > @@ -69,6 +69,7 @@ config DRM_PANEL_MIPI_DBI > > config DRM_SIMPLEDRM > > tristate "Simple framebuffer driver" > > depends on DRM && MMU > > + depends on SYSFB=n > > select APERTURE_HELPERS > > select DRM_GEM_SHMEM_HELPER > > select DRM_KMS_HELPER > > Why? It has nothing to do with the driver. Then how would you "fix" it in the upstream side? It shouldn't rely on the random kconfig choice done by user. (In reply to Thomas Zimmermann from comment #19) > (In reply to Thomas Zimmermann from comment #18) > > (In reply to Takashi Iwai from comment #17) > > > Then maybe better to have as Kconfig dependency, e.g. > > > > > > --- a/drivers/gpu/drm/tiny/Kconfig > > > +++ b/drivers/gpu/drm/tiny/Kconfig > > > @@ -69,6 +69,7 @@ config DRM_PANEL_MIPI_DBI > > > config DRM_SIMPLEDRM > > > tristate "Simple framebuffer driver" > > > depends on DRM && MMU > > > + depends on SYSFB=n > > > select APERTURE_HELPERS > > > select DRM_GEM_SHMEM_HELPER > > > select DRM_KMS_HELPER > > > > Why? It has nothing to do with the driver. > > It would, BTW, prevent it from being used on x86, etc. Why x86 still needs sysfb when simpledrmfb is enabled? Do you think of the situation to allow user switching via boot option or such? And, what did you have in mind by "disabling CONFIG_SYSFB"? If it were only about ARM, you can put a restriction in the kconfig, too. -- 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#c19 --- Comment #19 from Thomas Zimmermann <tzimmermann(a)suse.com> --- (In reply to Thomas Zimmermann from comment #18) > (In reply to Takashi Iwai from comment #17) > > Then maybe better to have as Kconfig dependency, e.g. > > > > --- a/drivers/gpu/drm/tiny/Kconfig > > +++ b/drivers/gpu/drm/tiny/Kconfig > > @@ -69,6 +69,7 @@ config DRM_PANEL_MIPI_DBI > > config DRM_SIMPLEDRM > > tristate "Simple framebuffer driver" > > depends on DRM && MMU > > + depends on SYSFB=n > > select APERTURE_HELPERS > > select DRM_GEM_SHMEM_HELPER > > select DRM_KMS_HELPER > > Why? It has nothing to do with the driver. It would, BTW, prevent it from being used on x86, etc. -- 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#c18 --- Comment #18 from Thomas Zimmermann <tzimmermann(a)suse.com> --- (In reply to Takashi Iwai from comment #17) > Then maybe better to have as Kconfig dependency, e.g. > > --- a/drivers/gpu/drm/tiny/Kconfig > +++ b/drivers/gpu/drm/tiny/Kconfig > @@ -69,6 +69,7 @@ config DRM_PANEL_MIPI_DBI > config DRM_SIMPLEDRM > tristate "Simple framebuffer driver" > depends on DRM && MMU > + depends on SYSFB=n > select APERTURE_HELPERS > select DRM_GEM_SHMEM_HELPER > select DRM_KMS_HELPER Why? It has nothing to do with the driver. -- 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#c17 --- Comment #17 from Takashi Iwai <tiwai(a)suse.com> --- Then maybe better to have as Kconfig dependency, e.g. --- a/drivers/gpu/drm/tiny/Kconfig +++ b/drivers/gpu/drm/tiny/Kconfig @@ -69,6 +69,7 @@ config DRM_PANEL_MIPI_DBI config DRM_SIMPLEDRM tristate "Simple framebuffer driver" depends on DRM && MMU + depends on SYSFB=n select APERTURE_HELPERS select DRM_GEM_SHMEM_HELPER select DRM_KMS_HELPER -- 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#c16 --- Comment #16 from Thomas Zimmermann <tzimmermann(a)suse.com> --- Hi I can see the error message on my RPi3. But it's non-critical and we could just ignore it. (In reply to Takashi Iwai from comment #15) > Then maybe we need drm_aperture_remove_conflicting_pci_framebuffers()? e.g. IMHO the code works as expected. It's just that we're seeing two devices for the the same framebuffer. The first is created from the device-tree node [1] and the second is created from the EFI stub that's on the RPi. [2] But the EFI thing just another reference to the device-tree entry, so the memory overlaps. I have to verify all of this, but a fix would be to disable CONFIG_SYSFB on arm if this has no negative impact on other arm systems. [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_simpl… -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1200616] Returning from SMM crashes 64bit KVM guest kernel
by bugzilla_noreply＠suse.com 02 Nov '22

02 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1200616 https://bugzilla.suse.com/show_bug.cgi?id=1200616#c12 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #12 from Jiri Slaby <jslaby(a)suse.com> --- Merged to upstream as: 055f37f8 KVM: x86: emulator: update the emulation mode after rsm d087e0f7 KVM: x86: emulator: introduce emulator_recalc_and_set_mode So I pushed it to stable. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1204705] Kernel 6.0.3: NULL pointer dereference + Plasma 5.26.1 session not working; 6.0.2 works
by bugzilla_noreply＠suse.com 02 Nov '22

02 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204705 https://bugzilla.suse.com/show_bug.cgi?id=1204705#c26 --- Comment #26 from Takashi Iwai <tiwai(a)suse.com> --- Steven submitted the fix patch to the upstream https://lore.kernel.org/r/20221101191009.1e7378c8@rorschach.local.home I backported it to stable branch now. A test kernel in OBS home:tiwai:bsc1204705 was built with this patch. You can test with it, too. -- 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 02 Nov '22

02 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204342 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Other |Kernel Assignee|screening-team-bugs(a)suse.de |kernel-bugs(a)opensuse.org -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204277] IPMI of power8 machine (type 8247-22L) is not accessible after firmware upgrade
by bugzilla_noreply＠suse.com 02 Nov '22

02 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204277 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs(a)suse.de |kernel-bugs(a)opensuse.org -- 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#c15 --- Comment #15 from Takashi Iwai <tiwai(a)suse.com> --- Then maybe we need drm_aperture_remove_conflicting_pci_framebuffers()? e.g. --- a/drivers/gpu/drm/tiny/simpledrm.c +++ b/drivers/gpu/drm/tiny/simpledrm.c @@ -626,6 +626,8 @@ static struct drm_display_mode simpledrm_mode(unsigned int width, return mode; } +static struct drm_driver simpledrm_driver; + static struct simpledrm_device *simpledrm_device_create(struct drm_driver *drv, struct platform_device *pdev) { @@ -714,6 +716,11 @@ static struct simpledrm_device *simpledrm_device_create(struct drm_driver *drv, if (!res) return ERR_PTR(-EINVAL); + ret = drm_aperture_remove_conflicting_framebuffers(res->start, resource_size(res), + true, &simpledrm_driver); + if (ret) + return ERR_PTR(ret); + ret = devm_aperture_acquire_from_firmware(dev, res->start, resource_size(res)); if (ret) { drm_err(dev, "could not acquire memory range %pr: error %d\n", res, ret); ~ -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204936] New: Can't install kernel-default-5.3.18-150300.59.98.1.x86_64
by bugzilla_noreply＠suse.com 02 Nov '22

02 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1204936 Bug ID: 1204936 Summary: Can't install kernel-default-5.3.18-150300.59.98.1.x86_64 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: openSUSE Leap 15.3 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: opensuse(a)dschung.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I'm failing to install the current Kernel: --- Checking for file conflicts: .........................................................................................................................................................................[done] installing package kernel-default-5.3.18-150300.59.98.1.x86_64 needs 2MB on the /boot filesystem ( 1/56) Installing: kernel-default-5.3.18-150300.59.98.1.x86_64 .....................................................................................................................................[error] Installation of kernel-default-5.3.18-150300.59.98.1.x86_64 failed: Error: Subprocess failed. Error: RPM failed: Command exited with status 1. Abort, retry, ignore? [a/r/i] (a): a Warning: %posttrans scripts skipped while aborting: kernel-default-5.3.18-150300.59.98.1.x86_64.rpm Problem occurred during or after installation or removal of packages: Installation has been aborted as directed. Please see the above error message for a hint. --- My /boot has much more space available than the needed 2MB: naumann:/home/ich # df -h /boot/ Filesystem Size Used Avail Use% Mounted on /dev/md126 246M 113M 121M 49% /boot -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1204940] New: Package hardware:rtl88x2bu does not build anymore
by bugzilla_noreply＠suse.com 01 Nov '22

01 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1204940 Bug ID: 1204940 Summary: Package hardware:rtl88x2bu does not build anymore Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: eyadlorenzo(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- As the title says, the package at https://build.opensuse.org/package/show/hardware/rtl88x2bu does not build anymore with openSUSE Tumbleweed. I found a new package that works at https://github.com/RinCat/RTL88x2BU-Linux-Driver, but it would require re-writing the new spec file. If anyone is up for it, thank you! -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1204695] [Build 20221024] openQA test fails in setitimer01
by bugzilla_noreply＠suse.com 01 Nov '22

01 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204695 https://bugzilla.suse.com/show_bug.cgi?id=1204695#c1 Martin Doucha <martin.doucha(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |martin.doucha(a)suse.com --- Comment #1 from Martin Doucha <martin.doucha(a)suse.com> --- The test was recently rewritten but it appears that it found a kernel bug. I've modified the test to print the wrong values returned by setitimer() in the third parameter and tried a few experiments with different timer values. The experiment works like this: new_timer = old_timer = {0}; new_timer.it_value.tv_usec = 9234; setitimer(type, &new_timer, NULL); new_timer.it_value.tv_usec = 10345; old_timer.it_value.tv_usec = 18456; setitimer(type, &new_timer, &old_timer); Here we check that old_timer.it_value.tv_usec < 18456 and fail because the kernel sets it to 19234. I've tried multiple value combinations and the kernel always set old_timer to 10000us more than it should be when the timer type is ITIMER_VIRTUAL or ITIMER_PROF. ITIMER_REAL appears to work correctly. The cloned job with modified test is here: https://openqa.opensuse.org/tests/2846894#step/setitimer01/8 -- 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 01 Nov '22

01 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204315 https://bugzilla.suse.com/show_bug.cgi?id=1204315#c14 --- Comment #14 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- (In reply to Thomas Zimmermann from comment #13) > Two simpledrms? I wonder where the second one comes from. Maybe one from > the DT and another one from the EFI framebuffer? But is that even possible? The bootloader, Broadcom one (not the U-Boot), is inserting simple-framebuffer compatible device into 'chosen' devicetree node at runtime. > > The logs indicate that one of the simpledrm instances created a framebuffer > device. So there should be a console on the screen. (?) Yes, there is graphical console, at least over HDMI, see comment#9. -- 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 01 Nov '22

01 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204315 https://bugzilla.suse.com/show_bug.cgi?id=1204315#c13 --- Comment #13 from Thomas Zimmermann <tzimmermann(a)suse.com> --- (In reply to Ivan Ivanov from comment #12) > (In reply to Takashi Iwai from comment #11) > > > Could you check what conflicts in those memory area by looking at > > /proc/iomem? > > /proc/iomem don't show anything. > > Error starts in devm_aperture_acquire(), where simpledrm tries to > add new resource to the list of apertures, but finds that there is > already one which cover same memory region. And it looks like the > aperture was added by ... simpledrm module. Two simpledrms? I wonder where the second one comes from. Maybe one from the DT and another one from the EFI framebuffer? But is that even possible? The logs indicate that one of the simpledrm instances created a framebuffer device. So there should be a console on the screen. (?) > > simple-framebuffer simple-framebuffer.0: Conflicting range [mem > 0x3e402000-0x3ebeb000 flags 0x200] with simple-framebuffer: > 3e402000.framebuffer range: [mem 0x3e402000-0x3ebfa000 flags 0x200] > > I am not sure that is difference between simple-framebuffer.0 and > 3e402000.framebuffer devices. Above shows that when simple-framebuffer.0 > device > try to register 0x3e402000-0x3ebfa000 aperture it finds that the same was > already registred for 3e402000.framebuffer devices. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1183962] System freeze when wake up from sleep
by bugzilla_noreply＠suse.com 01 Nov '22

01 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1183962 http://bugzilla.opensuse.org/show_bug.cgi?id=1183962#c2 Cosmin Tanczel <cosmin.tanczel(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Cosmin Tanczel <cosmin.tanczel(a)gmail.com> --- Solved by latest kernel. -- 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 01 Nov '22

01 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1202244 http://bugzilla.opensuse.org/show_bug.cgi?id=1202244#c3 Cosmin Tanczel <cosmin.tanczel(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from Cosmin Tanczel <cosmin.tanczel(a)gmail.com> --- Not sure what update solved the problem, but seems to be working as expected now. The only somehow related thing I did was changing from tlp to power-profiles-daemon. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1194086] Touchpad scrolling is not working on some boots
by bugzilla_noreply＠suse.com 01 Nov '22

01 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1194086 https://bugzilla.suse.com/show_bug.cgi?id=1194086#c49 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(tiwai(a)suse.com) | --- Comment #49 from Takashi Iwai <tiwai(a)suse.com> --- It seems that the upstream didn't react to my submitted patch (somehow the input subsystem upstream handling is slower / less responsive in these days, unfortunately). Likely need to resubmit. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190256] Keyboard not working after cold-boot on ASUS Zenbook 14 UM425UA with Tumbleweed 20210904
by bugzilla_noreply＠suse.com 01 Nov '22

01 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1190256 https://bugzilla.suse.com/show_bug.cgi?id=1190256#c64 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(tiwai(a)suse.com) | --- Comment #64 from Takashi Iwai <tiwai(a)suse.com> --- Possibly, but I believe it's still safer to keep the workaround. It's always a timing issue. The upstreamed patch was somehow forgotten since it was submitted during the big change in i8042 quirk handling. I'll try to resubmit. -- 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 01 Nov '22

01 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204315 https://bugzilla.suse.com/show_bug.cgi?id=1204315#c12 --- Comment #12 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- (In reply to Takashi Iwai from comment #11) > Could you check what conflicts in those memory area by looking at > /proc/iomem? /proc/iomem don't show anything. Error starts in devm_aperture_acquire(), where simpledrm tries to add new resource to the list of apertures, but finds that there is already one which cover same memory region. And it looks like the aperture was added by ... simpledrm module. simple-framebuffer simple-framebuffer.0: Conflicting range [mem 0x3e402000-0x3ebeb000 flags 0x200] with simple-framebuffer: 3e402000.framebuffer range: [mem 0x3e402000-0x3ebfa000 flags 0x200] I am not sure that is difference between simple-framebuffer.0 and 3e402000.framebuffer devices. Above shows that when simple-framebuffer.0 device try to register 0x3e402000-0x3ebfa000 aperture it finds that the same was already registred for 3e402000.framebuffer devices. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1194086] Touchpad scrolling is not working on some boots
by bugzilla_noreply＠suse.com 01 Nov '22

01 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1194086 https://bugzilla.suse.com/show_bug.cgi?id=1194086#c48 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |jslaby(a)suse.com Resolution|FIXED |--- Flags| |needinfo?(tiwai(a)suse.com) --- Comment #48 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Takashi Iwai from comment #29) > OK, thanks for confirmation. The workaround patch was merged in stable > branch and destined for TW release in a near future. Again, it's not in upstream yet, so what's the status of the patch, please? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190256] Keyboard not working after cold-boot on ASUS Zenbook 14 UM425UA with Tumbleweed 20210904
by bugzilla_noreply＠suse.com 01 Nov '22

01 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1190256 https://bugzilla.suse.com/show_bug.cgi?id=1190256#c63 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |jslaby(a)suse.com Resolution|FIXED |--- Flags| |needinfo?(tiwai(a)suse.com) --- Comment #63 from Jiri Slaby <jslaby(a)suse.com> --- What's the state of this? The patch is still enabled in master and stable. So can it be dropped? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204915] New: No sound from Internal Speakers with Kernel 6.0.5
by bugzilla_noreply＠suse.com 01 Nov '22

01 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1204915 Bug ID: 1204915 Summary: No sound from Internal Speakers with Kernel 6.0.5 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dev(a)cubiclenate.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- 6.0.2 sound worked fine, 6.0.3, no sound worked. 6.0.5 the internal speakers do not work, sound through bluetooth and HDMI works. Here is dmesg ouput regarding sound. [ 8.233503] input: sof-hda-dsp Mic as /devices/pci0000:00/0000:00:1f.3/skl_hda_dsp_generic/sound/card0/input24 [ 8.233570] input: sof-hda-dsp Headphone as /devices/pci0000:00/0000:00:1f.3/skl_hda_dsp_generic/sound/card0/input25 [ 8.233625] input: sof-hda-dsp HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1f.3/skl_hda_dsp_generic/sound/card0/input26 [ 8.233682] input: sof-hda-dsp HDMI/DP,pcm=4 as /devices/pci0000:00/0000:00:1f.3/skl_hda_dsp_generic/sound/card0/input27 [ 8.233740] input: sof-hda-dsp HDMI/DP,pcm=5 as /devices/pci0000:00/0000:00:1f.3/skl_hda_dsp_generic/sound/card0/input28 -- You are receiving this mail because: You are the assignee for the bug.

1 1