Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#13744 - [nvidia] 180.xx causes system freeze
Attached to Project:
Arch Linux
Opened by Nekody Lenkner (ladislaio) - Wednesday, 11 March 2009, 05:10 GMT
Last edited by Allan McRae (Allan) - Friday, 12 June 2009, 04:13 GMT
Opened by Nekody Lenkner (ladislaio) - Wednesday, 11 March 2009, 05:10 GMT
Last edited by Allan McRae (Allan) - Friday, 12 June 2009, 04:13 GMT
|
DetailsDescription:
Since kernel 2.6.28 has been out, the nvidia drivers have been making my entire system to freeze. Additional info: extra/nvidia 180.29-3 extra/nvidia-utils 180.29-3 core/kernel-headers 2.6.27.6-2 (base) core/kernel26 2.6.28.7-1 (base) rolling back to the 2.6.27 set of drivers fixes this problem. Using the current kernel with the xf86-video-nv 2.1.12-1 driver also works(without openGL, of course) I cannot ssh in or even ping the computer, and there is nothing in the log files near the time at which the computer froze. REISUB does not work either. I have a Geforce 7300 GS graphics card. Steps to reproduce: Start X with the nvidia driver Wait (usually between 15 min and one hour) |
This task depends upon
Closed by Allan McRae (Allan)
Friday, 12 June 2009, 04:13 GMT
Reason for closing: Fixed
Additional comments about closing: See comments
Friday, 12 June 2009, 04:13 GMT
Reason for closing: Fixed
Additional comments about closing: See comments
dmesg produced these error messages:
NVRM: Xid (0006:00): 26, Ch 000001ff M 00001ffc D ffffffff intr ffffffff
NVRM: Xid (0006:00): 1, Ch 000001ff M 00001ffc D ffffffff intr ffffffff
NVRM: Xid (0006:00): 26, Ch 000001ff M 00001ffc D ffffffff intr ffffffff
NVRM: Xid (0006:00): 1, Ch 000001ff M 00001ffc D ffffffff intr ffffffff
NVRM: Xid (0006:00): 6, PE01ff 1ffc ffffffff 00004f6c 037102d7 001cabe4
NVRM: Xid (0006:00): 6, PE0000 02fc 00000001 00004f6c 037102d7 001cabe4
None of these errors are found in the logs near the times that the system entered unrecoverable freezes.
Using google, I have discovered that this is most likely an upstream bug that sometimes happens with multi core CPU's and nvidia Geforce 7 GPU's.
Using x64 the only difference is that these are the messages:
NVRM: Xid (0006:00): 6, PE0000 05e0 ff000000 0000fbd4 ff1d171b ff1d171b
NVRM: Xid (0006:00): 13, 0000 80016100 0000008a 00000404 ff91827b 00004000
NVRM: Xid (0006:00): 6, PE0000 0100 00000003 0000fbd4 ff282828 00000002
NVRM: Xid (0006:00): 13, 0000 80016100 0000008a 00000404 ffd7d7d7 00004000
I have tried the the different boot options suggested in the Nvidia forums, including the turning off of one of the cores, and have tried using the Nvidia packages from the source.
My system is:
| AMD Athlon(tm) 64 X2 Dual Core Processor 5200+ | M2N32-SLI Deluxe (MCP55/C51) | GeForce 7300 GT |
| Using a custom kernel 2.6.29.3 | NVIDIA 185.18.08 (beta)
The nvidia is configured to use MSI interrups (NVreg_EnableMSI=1), in any way i don't have any problems with IO-APIC interrupts.
Thank you for the suggestion of the beta drivers, djgera.
Bug report can be closed as far as I can tell, upstream fixed it.
BTW: if you update to 185.18.14 don't use MSI interrupts, is broken.