Created attachment 105608 [details]
Here is the config :
cpu : AMD64
Video card : 7600GT (NV40 family)
kernel : 3.16.1
nouveau-dri : 10.2.6
xf86-video-nouveau : 1.0.10
mesa : 10.2.6
flashplugin : 18.104.22.1680
gnome-shell : 3.12.2
firefox : 31.0
When I want to see the video at this link (nouvelle-twingo.renault.fr/), the screen freezes after the first part, when some controls appear on the screen (don't know if I'm clear...). I can still VT switch (slowly) and reboot.
Here is the complete dmesg. There are a lot of :
[ 976.757586] [TTM] Failed to find memory space for buffer 0xffff8800cf357c00 eviction
[ 976.757593] [TTM] No space for ffff8800cf357c00 (900 pages, 3600K, 3M)
[ 976.757595] [TTM] placement=0x00070002 (1)
[ 976.757597] [TTM] has_type: 1
[ 976.757598] [TTM] use_type: 1
[ 976.757599] [TTM] flags: 0x0000000A
[ 976.757600] [TTM] gpu_offset: 0x00000000
[ 976.757601] [TTM] size: 131072
[ 976.757602] [TTM] available_caching: 0x00070000
[ 976.757603] [TTM] default_caching: 0x00010000
And then :
nouveau E[gnome-shell] fail ttm_validate
[ 979.430184] nouveau E[gnome-shell] validate vram_list
[ 979.430194] nouveau E[gnome-shell] validate: -12
[ 1058.789582] nouveau E[ PGRAPH][0000:01:00.0] ERROR nsource: LIMIT_COLOR nstatus: PROTECTION_FAULT
[ 1058.789611] nouveau E[ PGRAPH][0000:01:00.0] ch 3 [0x0013c000 gnome-shell] subc 7 class 0x4097 mthd 0x1808 data 0x00000000
[ 1111.505273] nouveau E[ DRM] GPU lockup - switching to software fbcon
[ 1126.781591] nouveau E[Xorg.bin] failed to idle channel 0xcccc0001 [Xorg.bin]
It doesn't seem a duplicate of another bug I had (74320).
Created attachment 105609 [details]
Added journalctl --system log file
Disable vdpau. (Just remove it entirely.) It's known to hang nv4x cards, and provides no benefit.
I already remove all files in /usr/lib/vdpau/ for bug 74320 (after each upgrade). Are there other files to remove?
(In reply to comment #3)
> I already remove all files in /usr/lib/vdpau/ for bug 74320 (after each
> upgrade). Are there other files to remove?
Oh. Sorry, I wasn't paying close enough attention.
You're running out of vram, which the various software doesn't handle particularly well.
So sending a bug to gnome-shell (at least) could be valid? (and close this one?)
(In reply to comment #5)
> So sending a bug to gnome-shell (at least) could be valid? (and close this
No, gnome-shell is most likely fine. The problem is probably the nv30 gallium driver not dealing with the errors properly.
So, for this bug, should I just change :
Product -> Mesa
Component -> which one? I can't find an entry related with gallium and nouveau. Maybe 'Drivers\DRI\nouveau'? Or 'Other'?
And thanks for your help.
(In reply to comment #7)
> So, for this bug, should I just change :
> Product -> Mesa
> Component -> which one? I can't find an entry related with gallium and
> nouveau. Maybe 'Drivers\DRI\nouveau'? Or 'Other'?
> And thanks for your help.
Sure. Or you can leave it alone. It's not like it's a different group of people... I always look at the two groups together anyways.
-- 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/131.