edgy shutdown unexpected

Thanks for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.
Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command 'uname -a' in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' and attach the resulting file 'dmesg.log' to this bug report.
3. Please run the command 'sudo lspci -vvnn > lspci-vvnn.log' and attach the resulting file 'lspci-vvnn.log' to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at http://wiki.ubuntu.com/DebuggingKernelProblems . Thanks in advance!

Linux geoffrey-desktop 2.6.17-10-386 #2 Fri Oct 13 18:41:40 UTC 2006 i686 GNU/Linux

Okay, the CPU fan definitely Does Not run with Edgy.
From the time that I choose Edgy from the Grub menu, the CPU promptly stops. If I let the system boot up, log in, and let the GUI and desktop load, the fan remains motionless.

Otherwise, the fans runs on Dapper and Windows XP.

I haven't altered anything manually on this box, Edgy seems to have installed with this problem.

temporary fix:
after some online reading, I tried the solution described here:

http://www.vmware.com/community/message.jspa?messageID=332390

In my case, the BIOS of my machine controls the fan, and upon boot up, when ACPI kicks in, the fan shuts off.

I edited /boot/grub/menu.lst and found the line for my kernel
and added

acpi=off noacpi

to the end of that.

so mine looks like:

title Ubuntu, kernel 2.6.17-11-386
root (hd0,1)
kernel /boot/vmlinuz-2.6.17-11-386 root=UUID=0a5a4656-cf6d-4dc0-acd9-25908ebd2177 ro splash acpi=off noacpi
initrd /boot/initrd.img-2.6.17-11-386
savedefault
boot

(end grub menu)
it goes without saying this isn't the definitive cure for this problem, but my fan is running.

By, now, I've upgraded to feisty, and still require the acpi=off noacpi parameters to get the fan running.
for my machine, which is a very common chipset, this problem is still at large.
this isn't the kind of thing I like to explain to new/prospective linux/ubuntu users.

Hi Evan,

The 18 month support period for Edgy Eft 6.10 has reached it's end of life. As a result, we are closing the linux-source-2.6.17 Edgy Eft kernel task. However, Hardy Heron 8.04 was recently released. It would be helpful if you could test the new release and verify if this is still an issue - http://www.ubuntu.com/getubuntu/download . You should be able to test your bug using the LiveCD.

I've opened a new task for the the Hardy kernel "linux" to the bug report. Please let us know if this problem still persists. 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!