No turn off of PC

[Anders H]

When the script Comes to "Terminating signal.."
it stops there and the PC doesn't turn off as expected.
The restart operation works as expected.
Switching back to -386 version works fine and the PC turns off.
I have never seen this on this PC.
(Used Breezy and dapper and several other live distributions.)

[Barry deFreese (bddebian)]

Do you still have this problem with 2.6.15-20 ? Thank you.

[Anders H (anders-hem)]

Hi,

Thanks for your reply.
I can confirm that the problem still exists with the latest dapper
kernel updates.
I also found on dapper forum that some other had posted the same problem.

best regards,

Anders hidmark

Barry deFreese skrev:
> Do you still have this problem with 2.6.15-20 ? Thank you.
>
> ** Changed in: linux-source-2.6.15 linux-image-2.6.15-19-686 (Ubuntu)
> Status: Unconfirmed => Needs Info
>
>

[Brian Murray (brian-murray)]

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 as attachments 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.
4. Please run the command 'sudo dmidecode > dmidecode.log' and attach the resulting file 'dmidecode.log' to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks in advance!

[Anders H (anders-hem)]

Hi Brian,

Thanks for the update: however, I have upgraded to fiesty. Yor info is
very good for future bugs.

regards,

/Anders

On 6/13/07, Brian Murray <email address hidden> wrote:
> 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 as attachments 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.
> 4. Please run the command 'sudo dmidecode > dmidecode.log' and attach the resulting file 'dmidecode.log' to this bug report.
> For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks in advance!
>
> ** Changed in: linux-source-2.6.15 (Ubuntu)
> Assignee: (unassigned) => Brian Murray
>
> --
> No turn off of PC
> https://bugs.launchpad.net/bugs/36967
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Brian Murray (brian-murray)]

I take it the system is powering off properly in Feisty then?

[Brian Murray (brian-murray)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and feel free to submit bug reports in the future.