[amd64] Repeated freeze complete freeze 7.04

Also, I'm running an Nvidia card
nvidia-glx 1:1.0.9631
nvidia-kernel-common : 20051028+1

Latest dmesg.

Just did it again, locked, no response to pings while editing an email in firefox.

nothing in syslog, before freeze, just:
Jun 10 11:17:01 vinge /USR/SBIN/CRON[15794]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) MARK --
Jun 10 11:48:02 vinge -- MARK --
Jun 10 12:02:40 vinge syslogd 1.4.1#20ubuntu4: restart.

Punting from linux-source-2.6.17 -> linux-source-2.6.20

Todd:
Can you reproduce the problem then the NVIDIA binary drivers disabled (i.e. with nv as the driver in xorg.conf and then rebooting)?

I have gone back to the "nv" driver, and rebooted.
I'll wait and see if I can repro it.

Todd:
Did the problem continue to occur?

No, it hasn't. I've had the machine running for a week and nothing.

so I guess it looks like it's the nvidia binary driver.

I'll close this, unless there's something I can do to help debug/track down any driver issues otherwise.

...todd..

Well, I spoke too soon. It froze up this morning ( June 19th) after being up for over a week.

I'm going to update everything, from the update manager.

What more information can I provide ?

Todd:
I doubt updating will help. These freezes sound odd - is your machine overclocked? I would very carefully make you way down the list on http://people.redhat.com/davej/hardware-problems.txt (and test as many points on that list as you can, really run memtest for a day etc.) to rule out hardware issues...

okay, will do.
I'm not overclocking , and I'm running memtest now.

I'll look for BIOS updates as well.

I updated my bios to the latest for my motherboard, and that didn't change anything.

Then I found this post: http://www.latenightpc.com/blog/archives/2006/11/23/system-lockup-with-my-new-asus-m2npv-vm-linux-box/#more-253

I found the same entry in my kern.log :

Jul 6 08:02:31 vinge kernel: [ 26.289985] Checking aperture...
Jul 6 08:02:31 vinge kernel: [ 26.289989] CPU 0: aperture @ e400000000 size 32 MB
Jul 6 08:02:31 vinge kernel: [ 26.289991] Aperture too small (32 MB)

I followed his steps more or less, I have a newer BIOS than he documents
I had to enable a feature, increase the size of the frame buffer to 256MB ( I just picked the biggest size) then disable the feature again.

Since then my kern.log has the same entry, but hasn't crashed. It's been over a week where it would crash inside about 3 days before.

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!