On Tue, Jan 8, 2019 at 1:11 AM Eero Tamminen <eero.t.tammi...@intel.com> wrote: > > Hi, > > On 8.1.2019 8.56, Stéphane Marchesin wrote: > > Yes I think the Chrome-side is very simple here: because there isn't > > time or means for in-depth investigation, if a driver crashes too > > much, it gets blacklisted. The situation is not unique, the GPU > > blacklist file is 1700 lines: > > https://chromium.googlesource.com/chromium/src/gpu/+/master/config/software_rendering_list.json > > > > Anyway, IMO if the biggest crashers can be fixed, I think we could > > eventually make a case to reenable. > > Can Chrome crash tracking system provide following information: > * which www-page caused the crash > * upstream Mesa commit used > * upstream kernel commit used > * if crash is from ChromeOS > - what patches have been applied on top of kernel & Mesa
Note that for Chrome OS, we handle the crashes ourselves already. But of course there is no nouveau-based chromebook so that wouldn't help with the issue at hand. > * if crash is from a Linux distro > - distro version and windowing system setup (X/Wayland, compositor) > - package versions for kernel, Mesa, display server and compositor > (to find what kernel & Mesa patches are applied) > * detailed HW information > * backtrace The problem with the backtrace is that Chrome doesn't have the symbols for the driver, so although we (internally, at Google) can get a backtrace, we still need to symbolize it somehow. > ? > > So that developers could try the corresponding combination? The Chrome team has a relationship with a lot of vendors on other OSes. If there is interest, I am sure we can work out something similar between the Chrome team and the nouveau devs, and I'd be happy to play middle man if needed. I think the main roadblock is about symbolizing the backtraces which we have. We can probably start with bugs that happen on "common" distros, for which it should be easy to get symbols. Stéphane > > > - Eero > _______________________________________________ > mesa-dev mailing list > mesa-dev@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/mesa-dev _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev