November 2022 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[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