system doesnt poweroff after halt

Bug #111003 reported by JdGordon
8
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned
linux-source-2.6.20 (Ubuntu)
Won't Fix
Medium
Unassigned
linux-source-2.6.22 (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

When I try to shutdown the system it does a full shutdown and I hear the hard disk poweroff, but then nothing happens and I have to press the power button to turn it off.. It works fine with 6.06 but every version to date has this issue (7.04 included).
my system is:
celeron 2.4ghz
ECS 651-M motherboard (SiS650 chipset)
512mb ram

Revision history for this message
Brian Murray (brian-murray) 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 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!

Revision history for this message
JdGordon (jdgordy) wrote :

I have since gone back to 6.06, but I can get all the output for you from the live cd (which also doesnt shutdown)..

1) # uname -a
Linux ubuntu 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux

2) attached
3) attached
4) # dmidecode
# dmidecode 2.8
# No SMBIOS nor DMI entry point found, sorry.

cheers

Changed in linux-source-2.6.20:
assignee: brian-murray → ubuntu-kernel-team
importance: Undecided → Medium
status: Needs Info → Confirmed
Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug does not meet the criteria for a stable release update and is being marked as Won't Fix for this particular version of the kernel. You can learn more about the stable release update process at https://wiki.ubuntu.com/StableReleaseUpdates .
However, the issue that you reported is one that should be possible to test with the live environment of the Desktop CD of the development release - Gutsy Gibbon. It would help us greatly if you could test with it so we can work on getting it fixed in the actively developed kernel. You can find out more about the development release at http://www.ubuntu.com/testing/ .
If you do decide to test with the development release of Ubuntu please comment on this bug report and include at least the minimal information requested at http://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks again and we appreciate your help.

Changed in linux-source-2.6.20:
assignee: ubuntu-kernel-team → brian-murray
status: Confirmed → Won't Fix
Revision history for this message
JdGordon (jdgordy) wrote :

Hi,
I finnaly got a chance to test gutsy and the problem still exists

Revision history for this message
Akshay (kiniakshay) wrote : Re: [Bug 111003] Re: system doesnt poweroff after halt

But in Ubuntu 7.04 after kernel update the problem went away.

On 04/11/2007, JdGordon <email address hidden> wrote:
> Hi,
> I finnaly got a chance to test gutsy and the problem still exists
>
> --
> system doesnt poweroff after halt
> https://bugs.launchpad.net/bugs/111003
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
JdGordon (jdgordy) wrote :

On 04/11/2007, Akshay <email address hidden> wrote:
> But in Ubuntu 7.04 after kernel update the problem went away.
Not for me

Changed in linux-source-2.6.22:
assignee: nobody → ubuntu-kernel-team
importance: Undecided → Medium
status: New → Confirmed
Changed in linux-source-2.6.20:
assignee: brian-murray → nobody
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Hardy Heron kernel was recently uploaded for testing. We'd really appreciate it if you could try testing with this newer kernel and verify if this issue still exists. Unfortunately, the Hardy Heron Alpha1 LiveCD was released with the older 2.6.22 kernel. You'll have to manually install the newer Hardy Heron kernel in order to test. This should not be the case for Alpha2. However, here are the instructions to install (if you choose to do so):

1) edit the file /etc/apt/sources.list and add the following line:

deb http://archive.ubuntu.com/ubuntu hardy main restricted

2) sudo apt-get update
3) sudo apt-get install linux-image-2.6.24-1-generic
4) reboot and select the new kernel from the grub menu

After you've tested, please feel free to revert back - ie boot into the old kernel, sudo apt-get remove linux-image-2.6.24-1-generic, and remove the line from /etc/apt/sources.list . Please update this report with your results. Thanks in advance!

Changed in linux:
status: New → Incomplete
Changed in linux-source-2.6.22:
status: Confirmed → Won't Fix
Revision history for this message
JdGordon (jdgordy) wrote :

I wont have access to that computer foir another 3 months, so I wont
be able to test that kernel. I will test it if I remember when I get
back tohugh.

On 04/12/2007, Leann Ogasawara <email address hidden> wrote:
> The Hardy Heron kernel was recently uploaded for testing. We'd really
> appreciate it if you could try testing with this newer kernel and verify
> if this issue still exists. Unfortunately, the Hardy Heron Alpha1
> LiveCD was released with the older 2.6.22 kernel. You'll have to
> manually install the newer Hardy Heron kernel in order to test. This
> should not be the case for Alpha2. However, here are the instructions
> to install (if you choose to do so):
>
> 1) edit the file /etc/apt/sources.list and add the following line:
>
> deb http://archive.ubuntu.com/ubuntu hardy main restricted
>
> 2) sudo apt-get update
> 3) sudo apt-get install linux-image-2.6.24-1-generic
> 4) reboot and select the new kernel from the grub menu
>
> After you've tested, please feel free to revert back - ie boot into the
> old kernel, sudo apt-get remove linux-image-2.6.24-1-generic, and remove
> the line from /etc/apt/sources.list . Please update this report with
> your results. Thanks in advance!
>
> ** Also affects: linux (Ubuntu)
> Importance: Undecided
> Status: New
>
> ** Changed in: linux (Ubuntu)
> Status: New => Incomplete
>
> ** Changed in: linux-source-2.6.22 (Ubuntu)
> Status: Confirmed => Won't Fix
>
> --
> system doesnt poweroff after halt
> https://bugs.launchpad.net/bugs/111003
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
nglnx (nglnx) wrote :

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!

Changed in linux:
status: Incomplete → Invalid
Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.