Now, looking at the nvidia module source code -- os-interface.c I observed call to os_map_kernel_space being made. The bug may be in calling with wrong mode for opregion (the term used in above commits)

Seeing the same, 260.19.36, 2.6.38rc6.
Funny thing though, I'm seeing this on an AMD machine, but the same driver/kernel combo works just fine on a Xeon workstation.

rprabhu,

Have you had any luck finding which io*remap call fails?

- Gilboa

It is not related to Intel in anyway. I just quoted the Intel commit to show similarity. You can look at os_map_kernel_space function in os-interface.c to see the callpoints. I think it may require a fix in the closed part of the driver. Also, related to your latter comment, yes, it is related to ACPI (check the other commit in my comment which caused this).

A bug has been filed and we'll address the problem in a future release. It shouldn't cause any crashes - the mapping request's memory type is modified to match the kernel's mappings' memory type.

Good to hear that, thanks. I had crash only once with it (of course i switched back to 37 after crash). Another place (and the reason why I presumed the crash was due to it) it caused a nuisance of sorts was when using OSSv4 for sound, it was causing a lot of crackling noise in the speaker while playing music, with ALSA I have had no such issues though (but crash happened when using ALSA).