http://bugzilla.suse.com/show_bug.cgi?id=1023783 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fvogt@suse.com, | |mstaudt@suse.com, | |tiwai@suse.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1023783 http://bugzilla.suse.com/show_bug.cgi?id=1023783#c2 --- Comment #2 from Fabian Vogt --- (In reply to David Patiño from comment #0)

I've not realized this issue until now but since last year, at least, openSUSE 42.2 versions for RPi3 have an issue with vc4 driver as I'll explain next. I've downloaded an openSUSE 42.2 image for RPi3 from the https://en.opensuse.org/HCL:Raspberry_Pi3 source web, and write it in SD card.

When did you download it? Temporarily the config.sh in the image had a bug with exact this symptom. Maybe you just got hit by that.

After boot the system and whitout changing anything I've launched Firefox and I've started to open links in new windows then, sometimes when first window is open, sometimes anothers, but always happen (later or earlier), the system crashes and provokes a reboot or logout, . To show the problem, I've started a <> though an ssh connection before launch firefox and I've seen an vc4 buffer allocation error as the attached file. That issue makes the system unusable.

This happens as the vc4 driver keeps buffer objects in memory unnecessarily (or something like that, mstaudt knows more about it) and it's the reason 3d acceleration (and also 2d accel using glamor, which is currently interconnected) are disabled by default in openSUSE and SLES. In the future this should be fixed by using CMA and then there's enough space for more BOs.

Any idea how to fix it? Ive tried disable vc4 module adding it to the 50-blacklist.conf file in udev rules but with vc4 disabled the desktop colours are wrong...

That way you disabled the vc4 kernel driver which forces the system to use efifb instead, which is known to be broken. You only need to disable hw acceleration by writing this into /etc/X11/xorg.conf.d/20-kms.conf: Section "Device" Identifier "kms gfx" Driver "modesetting" Option "AccelMethod" "none" EndSection

Thanks for your help

-- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1023783 http://bugzilla.suse.com/show_bug.cgi?id=1023783#c4 --- Comment #4 from David Patiño --- Created attachment 713026 --> http://bugzilla.suse.com/attachment.cgi?id=713026&action=edit Xorg.0.log info -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1023783 http://bugzilla.suse.com/show_bug.cgi?id=1023783#c6 --- Comment #6 from David Patiño --- (In reply to Max Staudt from comment #3)

(In reply to Fabian Vogt from comment #2)

...

That way you disabled the vc4 kernel driver which forces the system to use efifb instead, which is known to be broken. You only need to disable hw acceleration by writing this into /etc/X11/xorg.conf.d/20-kms.conf:

Section "Device" Identifier "kms gfx" Driver "modesetting" Option "AccelMethod" "none" EndSection

After doing the above, please also delete /etc/X11/xorg.conf.d/20-fbdev.conf in order to not confuse the system with contradictory settings.

OMG! That seems to fix the problem when vc4 is enabled. Thank you very much. On the other hand, I dont have /etc/X11/xorg.conf.d/20-fbdev.conf file. I've downloaded my current image file around November'16, but the last image I've tested is from January'17. Many thanks, also for the explanation. -- You are receiving this mail because: You are on the CC list for the bug.