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#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