View Single Post
Old 01-15-11, 01:55 PM   #22
voegel
Registered User
 
Join Date: Dec 2010
Posts: 12
Default Re: NVRM: os_schedule: Attempted to yield the CPU while in atomic[...] [260.19.21 x86

Quote:
Originally Posted by jpi110 View Post
At this point, what might yield usable, though not optimal, results would probably be to downgrade to the 195.36.31 drivers. I can't say with certainty as the next set of drivers supposedly fixes bugs so it may depend on your hardware configuration. (Your mileage may vary.)

It netted some flickering in 2D/3D environments for me but did not otherwise introduce spinlock crashes. Try that and see if it works for you. It would certainly confirm in your environment whether or not the driver is the cause.
Unfortunately the 195.xx version is unsuitable for me, because I then have problems with HDMI audio. This only works flawlessly on my hardware with 256.xx and up.

Interestingly though, a downgrade to 256.xx doesn't solve the problem, whereas in Mythbuntu 10.04 I didn't have any trouble with that version.
voegel is offline   Reply With Quote