Created attachment 34870 [details] kernel.log I caught it after resume from s2ram
Just for the record, Alex reported this bug to kernel bugzilla in the same time : https://bugzilla.kernel.org/attachment.cgi?id=25936 And also 2 months ago already on FDO, but mixed with other issues about s2ram and s2disk : http://bugs.freedesktop.org/show_bug.cgi?id=26521 Another user (Michal) caught the same trace there too : http://bugs.freedesktop.org/attachment.cgi?id=34299
I caught it with 2.6.34-rc4, and looks like it happens every third time after suspend to ram.
Created attachment 35081 [details] 2.6.34-rc4 kernel log
Forgot to mention, may be that can help, I have nouveau built in kernel not as module.
I reproduced it on 2.6.34-rc5 and 2.6.34-rc6, seems like nobody from nouveau team isn't interested in fixing this bug
Bugs can be non trivial to fix if you never hit them yourself. In this case it would be nice to know what value "mem->mem_type" has in ttm_pci_offset. So if you feel like poking around, that's where i would start. 0 is system, 1 is gart, 2 is vram, other is bad.
So if can give some instructions I can help you with investigation
Adding this to the beginning of the ttm_bo_pci_offset function should print the value every time, you may have to revert it afterwards because of flooded logs. printk(KERN_INFO TTM_PFX "mem->mem_type %d\n", mem->mem_type);
I still can't reproduce exactly this bug with proposed debugging but I have following error or something like this after which system or just X completely freeze and doesn't respond May 3 00:37:40 loki kernel: [47292.941614] video LNXVIDEO:01: Restoring backlight state May 3 00:37:40 loki kernel: [47293.171676] [TTM] mem->mem_type 2 May 3 00:37:40 loki kernel: [47293.185220] [drm] nouveau 0000:01:00.0: PFIFO_DMA_PUSHER - Ch 2 May 3 00:37:40 loki kernel: [47293.186640] [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/0 Mthd 0x0000 Data 0x0f000000 May 3 00:37:40 loki kernel: [47293.186651] [drm] nouveau 0000:01:00.0: PFIFO_DMA_PUSHER - Ch 2 it happens on resume from ram also
*** This bug has been marked as a duplicate of bug 26521 ***
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.