[ltp] suspend2 with nV Quadro 140M on R61

[Christian Birchinger]

On Sun, Sep 16, 2007 at 04:23:07PM +0200, onion wrote:
>>> Hi,
>>> a few days ago, I finally got suspend2 to work with my new R61 - at least
>>> that was what I tought. Unfortunately, after resuming from suspend
>>> (suspend-to-RAM, suspend-to-disk doesn't work yet but I don't care about
>>> that - I'm interested in suspend-to-ram) CPU usage goes to 100% and stays
>>> there (sometimes I get even 102% or 103% CPU usage :D ). Process 
>>> consuming
>>> all the CPU time is X.org - when I restart X (/etc/init.d/xdm restart)
>>> everything goes back to normal. Well ... sort of. Nvidia driver has
>>> unfortunately problem with the G86 core used by my GPU and for ex. 
>>> dragging
>>> window across the desktop is quite CPU intensive - it can get even as 
>>> high
>>> as ~50%! :( ).
>>>
>>> I'm using nvidia-drivers 100.14.11 (issue persists in 100.14.09, I even
>>> tried 9755 but with that, it didn't worked at all), direct rendering is 
>>> on
>>> (glxinfo)
>>> My kernel is suspend2-sources 2.6.22-1
>>> My xorg.conf: http://pastebin.com/f44c5d44e
>>> My .config: http://pastebin.com/f6037e5f1
>>>
>>> There's thread at NvNews discussing the very same problem, but guys from 
>>> nV
>>> are saying they can't reproduce the problem :( (but apparently I'm not 
>>> the
>>> only one with this problem).
>>> Thread at NvNews:
>>> http://www.nvnews.net/vbulletin/showthread.php?t=87865&page=1
>>
>> I also have a Thinkpad R61 but i'm only getting hit by this bug:
>>
>> http://www.nvnews.net/vbulletin/showthread.php?t=94258
>>
>> NVidia even added a comment:
>>
>> "The fix I referred to earlier was confirmed to resolve this
>> problem. It should be included in the next driver release."
>>
>> But that was months ago and they still didn't release an update
>> or at least a new BETA.
>>
>> Christian
>
> Yes, this is exactly my problem (well, one of them, but this is the most 
> painful one). May I ask - what WM/DE are you using?
>
> Peter
>

I'm using XFCE4, but the bug is not related to the WM but a
simple driver issue which happens on all desktops.

Christian