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@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 on the CC list for the bug.