Summary: | [NVE7] Chrome can cause a nouveau 'multiple instances of buffer' message when overlaying a menu leading to X lockup | ||
---|---|---|---|
Product: | xorg | Reporter: | Bryan O'Donoghue <pure.logic> |
Component: | Driver/nouveau | Assignee: | Nouveau Project <nouveau> |
Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> |
Severity: | critical | ||
Priority: | medium | CC: | peter |
Version: | unspecified | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Bryan O'Donoghue
2015-08-03 00:44:37 UTC
Can you say a bit more about your desktop environment? I've never seen this, and I use both chrome and nouveau on a regular basis on a GF108 which is fairly similar to kepler, at least wrt how buffers are added to validation lists. Are you using a compositor, if so which one, and how is it configured? Is there optimus involved, if so are you using DRI2 or DRI3? Are you using GLAMOR + DRI3 in the nouveau DDX? Compositor : I've tried on gnome+metacity, fluxbox, lxde and KDE. DRI: Looks like DRI2 [ 8.723] (--) Depth 24 pixmap format is 32 bpp [ 8.725] (II) NOUVEAU(0): Opened GPU channel 0 [ 8.728] (II) NOUVEAU(0): [DRI2] Setup complete [ 8.728] (II) NOUVEAU(0): [DRI2] DRI driver: nouveau [ 8.728] (II) NOUVEAU(0): [DRI2] VDPAU driver: nouveau GLAMOR: and so therefore not using GLAMOR + DRI3 Also having X lockups, triggered by chromium and/or gnome-shell. Linux 4.1.4-1-ARCH libdrm-2.4.62-1 mesa-10.6.3-1 Running ArchLinux, so using all the latests versions. Using XFCE does not fix the problem, as chromium alone can trigger it. Aug 12 15:15:53 imac.office.nl kernel: nouveau E[chromium[2045]] fail set_domain Aug 12 15:15:53 imac.office.nl kernel: nouveau E[chromium[2045]] validating bo list Aug 12 15:15:53 imac.office.nl kernel: nouveau E[chromium[2045]] validate: -22 Aug 12 15:15:53 imac.office.nl kernel: nouveau E[chromium[2045]] fail set_domain Aug 12 15:15:53 imac.office.nl kernel: nouveau E[chromium[2045]] validating bo list Aug 12 15:15:53 imac.office.nl kernel: nouveau E[chromium[2045]] validate: -22 [..] Aug 12 13:05:24 imac.office.nl kernel: nouveau E[ PFIFO][0000:01:00.0] write fault at 0x0010fc0000 [PTE] from GR/GPC0/PROP_0 on channel 0x001f7d9000 [gnome-shell[906]] Aug 12 13:05:24 imac.office.nl kernel: nouveau E[ PFIFO][0000:01:00.0] PGRAPH engine fault on channel 8, recovering... I've recently pushed some patches which solved this issue in Witcher 2. They should end up in Mesa 11.0.2 when that is released, but are already at mesa HEAD: http://cgit.freedesktop.org/mesa/mesa/commit/?id=d4e650b07bc80075f0d088e7d85df9efa45e11bd http://cgit.freedesktop.org/mesa/mesa/commit/?id=3a6b9a7830c3df14ffcfbbf57c82ea08bd59ef04 http://cgit.freedesktop.org/mesa/mesa/commit/?id=1d8cba9b51b7a6e7dbf3f0d3f53b5c232fd0b5b2 I have no idea if these will help with the issues you guys see with Chrome, but... they might! Ilia I'm running kernel 4.3-rcX right now and I don't see this issue any longer. However I do see something else (which I'll post to a separate bug). I guess it would be worthwhile getting a ppa for mesa and trying it out... Unbeknownst to me as I was writing this, 11.0.2 got released as an "emergency" release and only contained a handful of fixes not including mine. Will have to wait for 11.0.3. |
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.