Created attachment 275201 [details] dmesg updated nvidia-drivers last night (after midnight) & when I rebooted my system was unable to achieve video & couldn't be interacted with via keyboard (I had to add sshd in the hard way to work on correcting things), ended up having to roll back to preceding version to get workable system back. Currently just using full arch x86_64 with 0 overlays or ~arch. Kernel is 2.6.38-gentoo-r6 & drivers were 260.19.44 (working) & 270.41.06 (recently requested for STABLE - non-working here with one monitor, no special equipment, on-board ION video with no additional GPU). --- May 30 02:16:45 games2 kernel: [ 21.888162] BUG: unable to handle kernel NULL pointer dereference at 0000000000000a48 May 30 02:16:45 games2 kernel: [ 21.888167] IP: [<ffffffffa0362d96>] _nv008385rm+0xf1/0x115 [nvidia]
Please post your `emerge --info' output too.
Created attachment 275507 [details] Requested emerge --info
Still no solution? I've watched/waited/researched what little I can (http://ubuntuforums.org/archive/index.php/t-1601232.html seemed to show a similarity but was limited to Sony laptops & Ubuntu - they were recommending rolling back to 253 series) but no newer versions have helped - works only with <=260.19.44. Anything newer, doesn't make any difference which kernel/xorg-server/etc that it gets combined with. There was someone suggesting that this stemmed from bad RAM but why would it disappear & seem 100% fine on returning to the original driver version everytime (highly specific memory access? other than 0x00000000)? I practically have 0 problems using older driver that can't be accounted for by other things causing the other problems.
This site also seems to have relevant discussion about a related issue (http://www.nvnews.net/vbulletin/showthread.php?s=66f25a921af239507a725b6214fbdd89&t=155728&page=2). They seem to be having the problem (in a slightly variable combination - but the end results seem to be largely the same). And this site has people who can speak to the potential causation - "Judging from the backtrace, the driver crashed in the same place, accessing a built-in string for the first time.".
Another site where they are discussing this issue (http://www.nvnews.net/vbulletin/showthread.php?t=162538).
http://www.nvnews.net/vbulletin/showthread.php?p=2487046 Posted by AaronP on 10-03-11, 03:07 PM 285.05.09 (prerelease) for Linux x86/x86_64 released Release highlights since 285.03: Added support for the following GPU: GeForce GT 520MX Added support for xserver ABI 11 (xorg-server 1.11). Fixed a bug causing a Linux kernel BUG when retrieving CPU information on some systems. Fixed a bug causing some applications to hang on exit. Fixed a bug causing flickering in some GPU/display combinations. Fixed a bug that prevented the driver from loading on some ION systems. Fixed a bug that could result in poor OpenGL performance after hotplugging a monitor. Fixed a bug causing possible text corruption when recovering from GPU errors. The 285.05.09 NVIDIA Accelerated Linux Graphics Driver Set for Linux/x86 is available for download via FTP. The 285.05.09 NVIDIA Accelerated Linux Graphics Driver Set for Linux/x86_64 is available for download via FTP. Hopefully we can get to testing this version soon as possible?
They followed up with a mini-retraction & a pseudo-promise: Posted by danix on 10-04-11, 04:58 PM The entry "Fixed a bug that prevented the driver from loading on some ION systems" was incorrectly added to the 285.05.09 changelog. The fix for this issue will be in our next beta release. Sorry for the false alarm.
Ok, here we go again but this time maybe it will be a starter. http://www.nvnews.net/vbulletin/showthread.php?p=2493300 AaronP of NVIDIA Corporation posted this @ 10-21-11, 09:16 PM 290.03 (beta) for Linux x86/x86_64 released Release highlights since 285.05.09: Added support for the following GPU: GeForce 510 Fixed a bug that prevented the driver from loading on some systems with integrated graphics. Fixed issues in VDPAU that prevented allocating and displaying extremely large VdpOutputSurfaces. Added support for limiting heap allocations in the OpenGL driver through the use of the __GL_HEAP_ALLOC_LIMIT environment variable. See the README for further details. Added an "Accel" option to the X driver to allow disabling its use of the graphics processing hardware. This is useful when other components, such as CUDA, require exclusive use of the GPU's processing cores. Modified how the OpenGL driver allocates executable memory so it may continue to function properly if /tmp is mounted noexec. As some fallback allocation methods may be prohibited under SELinux policy, the driver now supports detection of this policy as well as manual override of this detection via the __GL_SELINUX_BOOLEANS environment variable. Fixed a bug that caused various GLSL built-in uniforms to not be updated properly when calling glPopAttrib. Improved performance by caching compiled OpenGL shaders to disk. Added a "GLShaderDiskCache" option to the X driver to enable/disable this feature. Added the __GL_SHADER_DISK_CACHE and __GL_SHADER_DISK_CACHE_PATH environment variables for further configuration. See the README for further details. Fixed a bug that caused trapezoid and triangle rendering to be very slow on older GPUs with xorg-server 1.11. The 290.03 NVIDIA Accelerated Linux Graphics Driver Set for Linux/x86 is available for download via FTP. The 290.03 NVIDIA Accelerated Linux Graphics Driver Set for Linux/x86_64 is available for download via FTP. Please see the README (x86 / x86_64) for more information about this release. Please note: This NVIDIA Linux graphics driver release supports GeForce 6xxx and newer NVIDIA GPUs, GeForce4 and older GPUs are supported through the 96.43.xx and 71.86.xx NVIDIA legacy graphics drivers. GeForce FX GPUs are supported through the 173.14.xx NVIDIA legacy graphics drivers. Please also note: If you encounter any problems with the 290.03 NVIDIA Linux graphics driver release, please start a new thread and include a detailed description of the problem, reproduction steps and generate/attach an nvidia-bug-report.log.gz file (please see http://www.nvnews.net/vbulletin/showthread.php?t=46678 for details).
Resolved in newer versions that are in the tree.
