View Single Post
Old 07-12-04, 01:12 PM   #1
ToastyX
Registered User
 
Join Date: Feb 2004
Posts: 32
Exclamation "screen frozen, but mouse pointer moves" bug

Examples:

http://www.nvnews.net/vbulletin/showthread.php?t=28716
http://www.nvnews.net/vbulletin/showthread.php?t=25222
http://www.nvnews.net/vbulletin/showthread.php?t=25651

There are many more threads on this problem but no solutions. This is not an isolated problem, but I get the feeling NVIDIA doesn't realize the scope of the problem. If you've experienced this problem, please post relevant information so we can get NVIDIA to fix this problem once and for all.

My current relevant hardware:

ASUS A7V600 [VIA KT600] (Upgrading the BIOS didn't make a difference)
PNY GeForce4 Ti 4600

My current relevant software:

Slackware 9.1
GCC 3.2.3
Kernel 2.4.26 (Using 2.4.22, 2.4.23, or 2.4.24 didn't make a difference)
XFree86 4.3.0 (Using 4.4.0 or XOrg didn't make a difference)
NVIDIA-Linux-x86-1.0-6106 (Using 4496 or 4620 didn't make a difference)

Disabling AGP didn't make a difference.
Not enabling fast writes didn't make a difference.
Not enabling SBA didn't make a difference.
Not using framebuffer console didn't make a difference.
Disabling ACPI with acpi=off didn't make a difference.
Disabling APIC with noapic didn't make a difference.
Setting pci=noacpi didn't make a difference.
Setting pci=biosirq didn't make a difference.

It's definitely not a hardware problem. I don't get random segfaults, which would indicate a hardware problem. I can run Quake 3 and Unreal Tournament 2004 for several hours without problems, which wouldn't be possible with bad hardware. I've tested the memory with memtest86 and found no problems. The video card isn't sharing an IRQ with any other device.

The system doesn't really crash. X simply stops responding. The system continues to run in the background. This problem does not occur with the open source "nv" driver.

After dealing with this problem for several months, I finally figured out a pattern. The problem only seems to occur if I run X for several days, then restart it. The "lockup" then occurs within 24 hours or so. I don't know if this is the case with everyone else, but perhaps that might be a clue as to why it happens.
ToastyX is offline