Evesham Voyager laptop will not shut down

PS Neither hibernate nor suspend work properly either, they don't recover.

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information.

Please include the information requested at [WWW] https://wiki.ubuntu.com/DebuggingACPI as separate attachments.

Thank you very much for offering to help with my shutdown problem. I will attach the information you requested shortly. BTW the site that you referred me to asks for the output of lspci -wnn, -w is not a valid option for lspci so I presume you need the output of -vnn which is what I have attached.

kern.log.0 after suspend

NB it did not resume but had to be shut down with the power button and then restarted.

kern.log.0 after Hibernate

NB It never completed hibernation - had to be shut down with the power button and restarted, although strangely enough it did resume from the hibernated disk image.

NB I have included this information re Hibernate and Suspend as you have asked for it but for my own personal purposes I am really only interested in the machine shutting down cleanly, I would never use Hibernate or Suspend even if they worked properly.

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at [WWW] https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in linux-source-2.6.22.

I am assigning this bug to the 'ubuntu-kernel-acpi' per their bug policy. For future reference you can learn more about their bug policy at https://wiki.ubuntu.com/KernelTeamBugPolicies .

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.

Very sorry but I don't use Ubuntu any more and I have sold the computer that had the problem so I can no longer help you.

Thanks for the update. I'll go ahead and just close this report.