Bug 106794

Summary: Driver crash while browsing with chrome
Product: xorg Reporter: Roman <freedesktop>
Component: Driver/nouveauAssignee: Nouveau Project <nouveau>
Status: RESOLVED MOVED QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
i915 platform: i915 features:
Description Flags
Kernel Log none

Description Roman 2018-06-03 12:15:45 UTC
Created attachment 139986 [details]
Kernel Log

I executed chromium on the secondary gpu (`DRI_PRIME=1 chromium`). After a bit of idle time on https://medium.com the system hanged for a bit. `dmesg` showed a nouveau driver crash. 

---- Chromium Log ----
[2245:2245:0603/131810.945660:ERROR:buffer_manager.cc(461)] [.DisplayCompositor-0x11f68c3ee800]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error from previous GL command
[2245:2245:0603/131828.527625:ERROR:buffer_manager.cc(461)] [.DisplayCompositor-0x11f68c3ee000]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error from previous GL command

Exact url was: https://medium.com/@MaartenSikkema/using-react-redux-and-webpack-with-dotnet-core-to-build-a-modern-web-frontend-7e2d091b3ba 

---- Versions ----
Linux 4.14.47-1-lts #1 SMP Wed May 30 21:09:23 UTC 2018 x86_64 GNU/Linux

extra/libdrm 2.4.92-1 [installed]
extra/mesa 18.0.4-1 [installed]
extra/xf86-video-nouveau 1.0.15-3 (xorg-drivers) [installed]

Chromium: Version 67.0.3396.62 (Official Build) Arch Linux (64-bit)

---- GPU ----
01:00.0 VGA compatible controller: NVIDIA Corporation GM107GLM [Quadro M2000M] (rev a2)
Comment 1 Martin Peres 2019-12-04 09:40:12 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues/438.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.