Comment 78 for bug 355155

Also, I have Nvidia 6200, using the 180.xx driver (I believe 37 was 8.10, 44 now 9.04).

As a whole, I am impressed with Jaunty, but it cannot be used until this issue is resolved.

The others are correct, I see in the logs (last -n15) indicated crash, but ALAS the word appears in no other log:
crazy pts/1 :0.0 Tue May 19 22:08 still logged in
crazy pts/0 :0.0 Tue May 19 18:10 still logged in
crazy tty7 :0 Tue May 19 18:09 still logged in
reboot system boot 2.6.28-11-generi Tue May 19 18:07 - 00:08 (06:00)
crazy pts/0 :0.0 Mon May 18 22:43 - crash (19:24)
crazy tty7 :0 Mon May 18 22:43 - crash (19:24)
reboot system boot 2.6.28-11-generi Mon May 18 22:42 - 00:08 (1+01:25)
crazy pts/1 :0.0 Mon May 18 21:31 - crash (01:10)
crazy pts/0 :0.0 Mon May 18 21:30 - crash (01:11)
crazy tty7 :0 Mon May 18 21:30 - crash (01:11)
reboot system boot 2.6.28-11-generi Mon May 18 21:29 - 00:08 (1+02:38)
nutty pts/3 localhost Mon May 18 12:52 - 19:05 (06:13)
wishful pts/2 nowhere.special Mon May 18 12:42 - 19:05 (06:23)
crazy pts/0 :0.0 Mon May 18 00:21 - crash (21:08)
crazy pts/1 :0.0 Mon May 18 00:03 - crash (21:26)
crazy pts/0 :0.0 Mon May 18 00:00 - 00:04 (00:04)
crazy tty7 :0 Sun May 17 23:59 - crash (21:30)
reboot system boot 2.6.28-11-generi Sun May 17 23:58 - 00:08 (2+00:09)
nutty pts/2 localhost Sun May 17 16:13 - 19:19 (03:05)
wishful pts/1 nowhere.special May 17 16:13 - 19:19 (03:05)

Funny, I guess I haven't had to use the power button to kill the machine before, that could be why I don't know the 'crash' status.

For the developers out there, I do applaud your efforts, I know dealing with many hardware types cannot be predicted flawlessly; but, is there any way I could help you determine the approximate problem? Have you been able to reproduce this odd little bug? Do you have a suspicious culprit that can be tested?