[nvidia-glx-legacy] GeForce2 Go + Nvidia driver causing system freezes unless cpu scaling is disabled

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please include the information requested at [WWW] https://help.ubuntu.com/community/DebuggingXAutoconfiguration as separate attachments. As well as try some of the troubleshooting steps.

Thanks,
Justin M. Wray

FuturePilot:
Can you check your
/var/log/messages
file for NVRM: Xid messages and report back on whether you find any?

Yes. I did find a few of these
NVRM: Xid (0001:00): 8, Channel 00000000
They showed up right after the freezes.

FuturePilot:
The only people who can help you decipher those are NVIDIA (the Xids are reporting the symptom which is generally that "something timed out"). My guess is that your hardware is being exercised in a way it was not before and this has uncovered an issue (only NVIDIA can tell you what caused it and the reasons are numerous). Xids are mentioned on http://us.download.nvidia.com/XFree86/Linux-x86/1.0-9755/README/chapter-04.html (I know that's not the README for your driver but the information about Xids still applies) and https://help.ubuntu.com/community/BinaryDriverHowto/Nvidia#head-20c0b7106f06055eed889efe3946f560c34a8b1a (again search for Xid towards the bottom).

Only NVIDIA can really help you find out what is causing this. See the note in the BinaryDriverHowto on how to contact them. There is also some tiny chance that the information linked off http://us.download.nvidia.com/XFree86/Linux-x86/1.0-9755/README/appendix-f.html might help you...

Punting from xorg -> linux-restricted-modules-2.6.22 .

Thank you for the help. If anyone else is having this problem, I have found a temporary workaround by disabling powernowd. Add "exit 0" (without the "") right below #! /bin/sh of /etc/init.d/powernowd. Reboot.

FuturePilot:
Hmm. You're the first Intel Pentium 4 owner I've heard of suffering from Bug #109643 . While the workaround appears to be the same it would be surprising to find that the underlying issue was the same...

FuturePilot:
Could you add the output of the following commands:
cat /proc/cpuinfo
lspci
as this may be useful to others...

The other thing that is strange about this is that the issue started occurring in Edgy... If memory serves, Edgy never shipped with cpu scaling enabled.

Futurepilot:
I would keep a close eye on this one as it may take some time to prove that disabling cpu scaling has an impact on the issue.

cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 15
model : 2
model name : Intel(R) Pentium(R) 4 Mobile CPU 1.50GHz
stepping : 4
cpu MHz : 1495.662
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm up
bogomips : 2994.68
clflush size : 64

lspci
00:00.0 Host bridge: Intel Corporation 82845 845 (Brookdale) Chipset Host Bridge (rev 04)
00:01.0 PCI bridge: Intel Corporation 82845 845 (Brookdale) Chipset AGP Bridge (rev 04)
00:1d.0 USB Controller: Intel Corporation 82801CA/CAM USB (Hub #1) (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801CA/CAM USB (Hub #3) (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 42)
00:1f.0 ISA bridge: Intel Corporation 82801CAM ISA Bridge (LPC) (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801CAM IDE U100 (rev 02)
00:1f.5 Multimedia audio controller: Intel Corporation 82801CA/CAM AC'97 Audio Controller (rev 02)
00:1f.6 Modem: Intel Corporation 82801CA/CAM AC'97 Modem Controller (rev 02)
01:00.0 VGA compatible controller: nVidia Corporation NV11 [GeForce2 Go] (rev b2)
02:00.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 78)
02:01.0 CardBus bridge: Texas Instruments PCI4451 PC card Cardbus Controller
02:01.1 CardBus bridge: Texas Instruments PCI4451 PC card Cardbus Controller
02:01.2 FireWire (IEEE 1394): Texas Instruments PCI4451 IEEE-1394 Controller

Setting back to new after prompt reply from author.

The strange thing is that I had powernowd enabled in Dapper and it never froze on me.

(Reporter started an nvnews thread and installed the official NVIDIA .pkg
http://www.nvnews.net/vbulletin/showthread.php?t=96850
but problem does not yet have a resolution)

I think it's pretty safe to say that disabling powernowd has eliminated the freezes. However, this is only a workaround as the underlying problem remains unsolved.

Well i have an intel card. It happens to me when desktop effects are enabled.

The 18 month support period for Gutsy Gibbon 7.10 has reached its end of life -
http://www.ubuntu.com/news/ubuntu-7.10-eol . As a result, we are closing the
linux-restricted-modules-2.6.22 task. It would be helpful if you could test the
new Jaunty Jackalope 9.04 release and confirm if this issue remains -
http://www.ubuntu.com/getubuntu/releasenotes/904overview. If the issue still exists with the Jaunty
release, please update this report by changing the Status of the "linux (Ubuntu)"
task from "Incomplete" to "New". Thanks in advance.

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

This is still an issue with 9.04

Hi Nick,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/releases/karmic . If the issue remains, please run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 134310

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

I've been using karmic with CPU scaling enabled for a couple of weeks now and I haven't been able to reproduce this anymore. I think it's safe to say this has been fixed.