ubuntu 10.04 will not shutdown

When the "sudo shutdown now" command is executed in a terminal, most processes shut down, but the system stays running, and nothing but a black screen is displayed. I have to hard-power-off the machine.

Same here.

Same for me too. all panels etc. disappear but splash screen remains.
Sometimes it just reboots.

Thank you for taking the time to report this bug and helping to make Ubuntu better. We need some more information from you before we can start working on this bug. please at least add the following information (pay attention to lspci's additional options).
First run the following commands:
1) uname -a > uname-a.log
2) dmesg > dmesg.log
3) cp /var/log/dmesg.0 dmesg.0.log
3) sudo lspci -vvnn > lspci-vvnn.log
4) cat /proc/version_signature > version.log
then attach the files separately to the bug report (not pasted into comments or tar/zip-ed).

On my system, selecting shut down, or restart from the menu has no effect. I click shut down, then OK, then ... nothing. Same with restart. Anyways, here are the files that were saved by running the previous commands. This is on a 32 bit system, nVidia driver, current updates as of last night, and installed using Beta 1 media.

I ran lspci and i get output but when i run the other commands in a terminal
i dont get any output in the terminal.

On Mon, Apr 12, 2010 at 9:47 AM, Charlie Kravetz <email address hidden>wrote:

> Thank you for taking the time to report this bug and helping to make Ubuntu
> better. We need some more information from you before we can start working
> on this bug. please at least add the following information (pay attention to
> lspci's additional options).
> First run the following commands:
> 1) uname -a > uname-a.log
> 2) dmesg > dmesg.log
> 3) cp /var/log/dmesg.0 dmesg.0.log
> 3) sudo lspci -vvnn > lspci-vvnn.log
> 4) cat /proc/version_signature > version.log
> then attach the files separately to the bug report (not pasted into
> comments or tar/zip-ed).
>
>
> ** Changed in: ubuntu
> Status: New => Incomplete
>
> --
> ubuntu 10.04 will not shutdown
> https://bugs.launchpad.net/bugs/552316
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Each of the commands should be creating a file in ~/ . The file names are the portion after the ">", so it should have created several .log files in ~/, which is /home/USER_NAME/ .

[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.32-20-generic (buildd@rothera) (gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) ) #29-Ubuntu SMP Fri Apr 9 20:35:55 UTC 2010 (Ubuntu 2.6.32-20.29-generic 2.6.32.11+drm33.2)
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] NSC Geode by NSC
[ 0.000000] Cyrix CyrixInstead
[ 0.000000] Centaur CentaurHauls
[ 0.000000] Transmeta GenuineTMx86
[ 0.000000] Transmeta TransmetaCPU
[ 0.000000] UMC UMC UMC UMC
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f400 (usable)
[ 0.000000] BIOS-e820: 000000000009f400 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 000000007fee0000 (usable)
[ 0.000000] BIOS-e820: 000000007fee0000 - 000000007fee3000 (ACPI NVS)
[ 0.000000] BIOS-e820: 000000007fee3000 - 000000007fef0000 (ACPI data)
[ 0.000000] BIOS-e820: 000000007fef0000 - 000000007ff00000 (reserved)
[ 0.000000] BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
[ 0.000000] BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
[ 0.000000] DMI 2.2 present.
[ 0.000000] Phoenix BIOS detected: BIOS may corrupt low RAM, working around it.
[ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
[ 0.000000] last_pfn = 0x7fee0 max_arch_pfn = 0x100000
[ 0.000000] MTRR default type: uncachable
[ 0.000000] MTRR fixed ranges enabled:
[ 0.000000] 00000-9FFFF write-back
[ 0.000000] A0000-BFFFF uncachable
[ 0.000000] C0000-C7FFF write-protect
[ 0.000000] C8000-FFFFF uncachable
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] 0 base 0000000000 mask FF80000000 write-back
[ 0.000000] 1 base 007FF00000 mask FFFFF00000 uncachable
[ 0.000000] 2 disabled
[ 0.000000] 3 disabled
[ 0.000000] 4 disabled
[ 0.000000] 5 disabled
[ 0.000000] 6 disabled
[ 0.000000] 7 disabled
[ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
[ 0.000000] Scanning 0 areas for low memory corruption
[ 0.000000] modified physical RAM map:
[ 0.000000] modified: 0000000000000000 - 0000000000010000 (reserved)
[ 0.000000] modified: 0000000000010000 - 000000000009f400 (usable)
[ 0.000000] modified: 000000000009f400 - 00000000000a0000 (reserved)
[ 0.000000] modified: 00000000000f0000 - 0000000000100000 (reserved)
[ 0.000000] modified: 0000000000100000 - 000000007fee0000 (usable)
[ 0.000000] modified: 000000007fee0000 - 000000007fee3000 (ACPI NVS)
[ 0.000000] modified: 000000007fee3000 - 000000007fef0000 (ACPI data)
[ 0.000000] modified: 000000007fef0000 - 000000007ff00000 (reserved)
[ 0.000000] modified: 00000000e0000000 - 00000000f0000000 (reserved)
[ 0.000000] modified: 00000000fec00000 - 0000000100000000 (reserved)
[ 0.000000] initial memory mapped : 0 - 00c00000
[ 0.000000] init_memory_mapping: 0000000000000000-...

00:00.0 Memory controller [0580]: nVidia Corporation CK804 Memory Controller [10de:005e] (rev a3)
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0
 Capabilities: [44] HyperTransport: Slave or Primary Interface
  Command: BaseUnitID=0 UnitCnt=15 MastHost- DefDir- DUL-
  Link Control 0: CFlE+ CST- CFE- <LkFail- Init+ EOC- TXO- <CRCErr=0 IsocEn- LSEn- ExtCTL- 64b-
  Link Config 0: MLWI=16bit DwFcIn- MLWO=16bit DwFcOut- LWI=16bit DwFcInEn- LWO=16bit DwFcOutEn-
  Link Control 1: CFlE- CST- CFE- <LkFail+ Init- EOC+ TXO+ <CRCErr=0 IsocEn- LSEn- ExtCTL- 64b-
  Link Config 1: MLWI=8bit DwFcIn- MLWO=8bit DwFcOut- LWI=8bit DwFcInEn- LWO=8bit DwFcOutEn-
  Revision ID: 1.03
  Link Frequency 0: 1.0GHz
  Link Error 0: <Prot- <Ovfl- <EOC- CTLTm-
  Link Frequency Capability 0: 200MHz+ 300MHz+ 400MHz+ 500MHz+ 600MHz+ 800MHz+ 1.0GHz+ 1.2GHz- 1.4GHz- 1.6GHz- Vend-
  Feature Capability: IsocFC+ LDTSTOP+ CRCTM- ECTLT- 64bA- UIDRD-
  Link Frequency 1: 200MHz
  Link Error 1: <Prot- <Ovfl- <EOC- CTLTm-
  Link Frequency Capability 1: 200MHz- 300MHz- 400MHz- 500MHz- 600MHz- 800MHz- 1.0GHz- 1.2GHz- 1.4GHz- 1.6GHz- Vend-
  Error Handling: PFlE+ OFlE+ PFE- OFE- EOCFE- RFE- CRCFE- SERRFE- CF- RE- PNFE- ONFE- EOCNFE- RNFE- CRCNFE- SERRNFE-
  Prefetchable memory behind bridge Upper: 00-00
  Bus Number: 00
 Capabilities: [e0] HyperTransport: MSI Mapping Enable+ Fixed-
  Mapping Address Base: 00000000fee00000

00:01.0 ISA bridge [0601]: nVidia Corporation CK804 ISA Bridge [10de:0050] (rev a3)
 Subsystem: nVidia Corporation Device [10de:cb84]
 Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0

00:01.1 SMBus [0c05]: nVidia Corporation CK804 SMBus [10de:0052] (rev a2)
 Subsystem: nVidia Corporation Device [10de:cb84]
 Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Interrupt: pin A routed to IRQ 10
 Region 0: I/O ports at fc00 [size=32]
 Region 4: I/O ports at 1c00 [size=64]
 Region 5: I/O ports at 1c40 [size=64]
 Capabilities: [44] Power Management version 2
  Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold+)
  Status: D0 PME-Enable- DSel=0 DScale=0 PME-
 Kernel driver in use: nForce2_smbus
 Kernel modules: i2c-nforce2

00:02.0 USB Controller [0c03]: nVidia Corporation CK804 USB Controller [10de:005a] (rev a2) (prog-if 10)
 Subsystem: nVidia Corporation Device [10de:cb84]
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0 (750ns min, 250ns max)
 Interrupt: pin A routed to IRQ 20
 Region 0: Memory at fe02f000 (32-bit, non-prefetchable) [size=4K]
 Capabilities: [44] Power Management version 2
  Flags: PMEClk- DS...

Ubuntu 2.6.32-20.29-generic 2.6.32.11+drm33.2

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

I hope this attachment is what you are seeking

Still eratic when shut down signal itinatiated, sometime it jst reboots, others times, just goes to a blank desktop

here is the lspci -vvnn log

slow learner, here are the other logs

I installed the final release of 10.04 yesterday and I'm having the exact same problem. Shutting down just restarts my computer.

I have the same problem as listed in one of the reply and this is not something that repeats all the time
"On my system, selecting shut down, or restart from the menu has no effect"

The culprit in my case seems to be cause by the OOo quickstarter
every times the problem happens I exit the quickstarter and do the shutdown and it works just fine..
Hope this helps...

I had this problem.
For some reason I uninstalled the hardware driver for my video card
which is a ati radeon HD4570 and guess what - no more issues when
turning off.
Now of course it could be totally unrelated, but I know for sure there
are issues with the driver for this video card. Start up screen is
distorted with the driver enabled.
Hope this helps.

Rev Glenn Louttit
Minister
Innisfail Uniting Church
P.O. Box 632
Innisfail. Qld. 4860
Ph. 07 4061 1180
Mob. 0418 747 204

-----Original Message-----
From: James Fennell <email address hidden>
Reply-to: Bug 552316 <email address hidden>
To: <email address hidden>
Subject: [Bug 552316] Re: ubuntu 10.04 will not shutdown
Date: Fri, 30 Apr 2010 15:32:49 -0000

I installed the final release of 10.04 yesterday and I'm having the
exact same problem. Shutting down just restarts my computer.

Let's be specific on this bug report. The original reporter stated that, When I click Shut Down the computer does not shutdown it just restarts." Those who are reporting that the computer never restarts or hangs on shutdown have a separate issue. Please create a separate report for that.

I am confirming the restart issue. I cannot shut down the computer via software no matter what I do. I have to hold down the power button to turn the computer off. I have a Dell M1530. I am not seeing any error messages in my dmesg nor syslog, so it is as if it is a BIOS issue, however I had no such problems before I installed Lucid. Any suggestions for troubleshooting would be appreciated. This *may* be related to my inability to suspend or hibernate--I get a similar unexpected restart, and Grub seems to think that it was an unsuccessful shutdown. (recordfail variable is set upon reboot)

Confirm that the original bug (any form of shutdown results in a restart instead) also affects me. I am using Lucid and the bug is present when I boot with the 2.6.32.22-generic kernel, but NOT if I select 2.6.31.21-generic. Can post more information if it would be helpful.

I also have the same problem as the original poster. Clicking on shutdown, or trying to shutdown through the terminal, restarts the computer instead of shutting it down. The only way to shutdown, that I have found, is to hold in the main power button for a second or two.

I can confirm this bug too. On shutdown the PC restarts. Ubuntu 10.04-64bit 2.6.32-22-generic #33-Ubuntu SMP.

Multiple file uploads, anyone?

Do you still need some information or files?
When will this bug be assigned to someone who can take care of it?

Michael Werner: Thank you for asking. No further information is required at this time. With over 1000 bugs a week reported, it will be worked as the volunteer developers have time to work this.

I am also having the problem of system hanging at splash screen at shutdown.
But just an addition that I am having this problem since I installed Jaunty
And my current installation (Lucid) is not just an up-gradation of previous versions but a fresh installation.

I can confirm this effects me (reboot when I try to shutdown via the GUI). @Glenn Louttit, I also have an ATI graphics card. I will try uninstalling my driver tonight.

Ubuntu 10.04-64bit 2.6.32-22-generic

I've installed Ubuntu GNU/Linux 10.04 (Lucid Lynx) in 5 computers and 3 of them are affected by this bug:

a) A clean installation: shutdown or restart menu options are ignored. In a terminal, work both commands: "sudo halt" and "sudo reboot".
b) An upgrade from Ubuntu 9.10: shutdown or restart menu options are ignored SOMETIMES. In a terminal, work both commands: "sudo halt" and "sudo reboot".
c) An upgrade from Ubuntu 8.04: shutdown or restart menu options are ignored. In a terminal, work both commands: "sudo halt" and "sudo reboot".

I have also this problem. Ubuntu shows shutdown splash screen, stops services and finaly init exits but computer is not shutting down is still powered on. I treid different combinations of boot options: "acpi=force", "splash", "quiet" none helped.

hi
just installed ubuntu 10.04 on a gateway DX4640-UBC01A nothing on the forums works when you shut it down it goes to a black screen and leaves the power supply on and the cpu fan on. you have to push the power buttion to shut off the power supply and cpu fan . testing i installed vista just to make sure it wasn't something with the motherboard it worked fine.

This bug was reported about 5 months ago. Has a fix been found?

Craig

No it is still the same. I've a Dell Dimension 3000. On shut down it always
restarts after appearing to shut down for about a second. On Madriva One
2010 (Gnome) and XP it shuts down OK. Open Suse 11.3 (Gnome) behaves the
same as 10.04. Ubuntu 9.10 works just fine. It is very frustrating as it
spoils an otherwise excellent version of Ubuntu.

Regards
John

On 29 August 2010 16:07, Craig <email address hidden> wrote:

> This bug was reported about 5 months ago. Has a fix been found?
>
> --
> ubuntu 10.04 will not shutdown
> https://bugs.launchpad.net/bugs/552316
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” package in Ubuntu: Triaged
>
> Bug description:
> Binary package hint: yelp
>
> I'am using Ubuntu 10.04 kernel,2.6.32-18 generic gnome 2.29.92
> When I click Shut Down the computer does not shutdown it just
> restarts.Nothing happens except it just re-boots.
> and of coarse i expected 10.04 to shutdown.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 10.04
> Package: yelp 2.30.0-0ubuntu1
> ProcVersionSignature: Ubuntu 2.6.32-18.27-generic 2.6.32.10+drm33.1
> Uname: Linux 2.6.32-18-generic i686
> NonfreeKernelModules: nvidia
> Architecture: i386
> Date: Wed Mar 31 00:11:25 2010
> ExecutablePath: /usr/bin/yelp
> InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100326)
> ProcEnviron:
> LANG=en_US.utf8
> SHELL=/bin/bash
> SourcePackage: yelp
> XsessionErrors:
> (polkit-gnome-authentication-agent-1:1296): GLib-CRITICAL **:
> g_once_init_leave: assertion `initialization_value != 0' failed
> (yelp:1425): Gtk-CRITICAL **: gtk_misc_set_alignment: assertion
> `GTK_IS_MISC (misc)' failed
> (yelp:1425): Gtk-CRITICAL **: gtk_misc_set_alignment: assertion
> `GTK_IS_MISC (misc)' failed
> (yelp:1425): Gtk-CRITICAL **: gtk_misc_set_alignment: assertion
> `GTK_IS_MISC (misc)' failed
> (yelp:1425): Gtk-CRITICAL **: gtk_misc_set_alignment: assertion
> `GTK_IS_MISC (misc)' failed
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/552316/+subscribe
>

This problem is present in the 10.10 beta.

@Craig, I know it's annoying, but it is open-source. Since support for 9.10 ends next April, I suggest those affected start looking into it.

I can not shutdown the HP ALL-IN-ONE 200 PC with ubuntu.
And the form does not read the files on my desktop:

CCDtoVCD Bugs List

==================

Graham Jones (<email address hidden>)

August 2004.

- cdrdao does not work with the .cue files produced by vcdxbuild on some CD

  recorders - it is necessary to remove the 'FLAGS DCP' lines in the .cue file

  manually before burning the CD (this is really a problem with vcdxbuild,

  because it produces these lines, which do not seem to be necessary as far as

  I can tell).

[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.35-28-generic (buildd@allspice) (gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5) ) #50-Ubuntu SMP Fri Mar 18 18:42:20 UTC 2011 (Ubuntu 2.6.35-28.50-generic 2.6.35.11)
[ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-2.6.35-28-generic root=UUID=b81a4821-6e67-4f2c-a5a9-d21db5d46b78 ro quiet splash
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009e800 (usable)
[ 0.000000] BIOS-e820: 000000000009e800 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 00000000ddd90000 (usable)
[ 0.000000] BIOS-e820: 00000000ddd90000 - 00000000ddd9e000 (ACPI data)
[ 0.000000] BIOS-e820: 00000000ddd9e000 - 00000000ddde0000 (ACPI NVS)
[ 0.000000] BIOS-e820: 00000000ddde0000 - 00000000e0000000 (reserved)
[ 0.000000] BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
[ 0.000000] BIOS-e820: 00000000ffe00000 - 0000000100000000 (reserved)
[ 0.000000] BIOS-e820: 0000000100000000 - 0000000120000000 (usable)
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] DMI present.
[ 0.000000] AMI BIOS detected: BIOS may corrupt low RAM, working around it.
[ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
[ 0.000000] e820 update range: 0000000000000000 - 0000000000001000 (usable) ==> (reserved)
[ 0.000000] e820 remove range: 00000000000a0000 - 0000000000100000 (usable)
[ 0.000000] No AGP bridge found
[ 0.000000] last_pfn = 0x120000 max_arch_pfn = 0x400000000
[ 0.000000] MTRR default type: uncachable
[ 0.000000] MTRR fixed ranges enabled:
[ 0.000000] 00000-9FFFF write-back
[ 0.000000] A0000-BFFFF uncachable
[ 0.000000] C0000-CFFFF write-protect
[ 0.000000] D0000-DFFFF uncachable
[ 0.000000] E0000-EFFFF write-through
[ 0.000000] F0000-FFFFF write-protect
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] 0 base 000000000 mask F00000000 write-back
[ 0.000000] 1 base 100000000 mask FE0000000 write-back
[ 0.000000] 2 base 0E0000000 mask FE0000000 uncachable
[ 0.000000] 3 base 0DDE00000 mask FFFE00000 uncachable
[ 0.000000] 4 base 0DE000000 mask FFE000000 uncachable
[ 0.000000] 5 disabled
[ 0.000000] 6 disabled
[ 0.000000] 7 disabled
[ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
[ 0.000000] e820 update range: 00000000dde00000 - 0000000100000000 (usable)...

I can not shutdown the HP ALL-IN-ONE 200 PC with ubuntu.
And the form does not read the files on my desktop:

Ubuntu 2.6.35-28.50-generic 2.6.35.11

CCDtoVCD Bugs List

==================

Graham Jones (<email address hidden>)

August 2004.

- cdrdao does not work with the .cue files produced by vcdxbuild on some CD

  recorders - it is necessary to remove the 'FLAGS DCP' lines in the .cue file

  manually before burning the CD (this is really a problem with vcdxbuild,

  because it produces these lines, which do not seem to be necessary as far as

  I can tell).

[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.35-28-generic (buildd@allspice) (gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5) ) #50-Ubuntu SMP Fri Mar 18 18:42:20 UTC 2011 (Ubuntu 2.6.35-28.50-generic 2.6.35.11)
[ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-2.6.35-28-generic root=UUID=b81a4821-6e67-4f2c-a5a9-d21db5d46b78 ro quiet splash
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009e800 (usable)
[ 0.000000] BIOS-e820: 000000000009e800 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 00000000ddd90000 (usable)
[ 0.000000] BIOS-e820: 00000000ddd90000 - 00000000ddd9e000 (ACPI data)
[ 0.000000] BIOS-e820: 00000000ddd9e000 - 00000000ddde0000 (ACPI NVS)
[ 0.000000] BIOS-e820: 00000000ddde0000 - 00000000e0000000 (reserved)
[ 0.000000] BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
[ 0.000000] BIOS-e820: 00000000ffe00000 - 0000000100000000 (reserved)
[ 0.000000] BIOS-e820: 0000000100000000 - 0000000120000000 (usable)
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] DMI present.
[ 0.000000] AMI BIOS detected: BIOS may corrupt low RAM, working around it.
[ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
[ 0.000000] e820 update range: 0000000000000000 - 0000000000001000 (usable) ==> (reserved)
[ 0.000000] e820 remove range: 00000000000a0000 - 0000000000100000 (usable)
[ 0.000000] No AGP bridge found
[ 0.000000] last_pfn = 0x120000 max_arch_pfn = 0x400000000
[ 0.000000] MTRR default type: uncachable
[ 0.000000] MTRR fixed ranges enabled:
[ 0.000000] 00000-9FFFF write-back
[ 0.000000] A0000-BFFFF uncachable
[ 0.000000] C0000-CFFFF write-protect
[ 0.000000] D0000-DFFFF uncachable
[ 0.000000] E0000-EFFFF write-through
[ 0.000000] F0000-FFFFF write-protect
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] 0 base 000000000 mask F00000000 write-back
[ 0.000000] 1 base 100000000 mask FE0000000 write-back
[ 0.000000] 2 base 0E0000000 mask FE0000000 uncachable
[ 0.000000] 3 base 0DDE00000 mask FFFE00000 uncachable
[ 0.000000] 4 base 0DE000000 mask FFE000000 uncachable
[ 0.000000] 5 disabled
[ 0.000000] 6 disabled
[ 0.000000] 7 disabled
[ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
[ 0.000000] e820 update range: 000...

i am having the same problem with a recent install of 10.04 on a modified HP dc5100mt PC.
it has a PNY 512mb 8400GS PCI graphics card and the latest nvidia 275.09.07 driver. i have tried several of the "fixes" posted on the ubuntu forms but nothing works. the PC will not shutdown. not even with shutdown -P 0, it always restarts. i am attaching the requested files for debugging purposes. i hope a fix is found soon, i am at my wits end with this one.

it would appear as though my shutdown problem was a result of "wake on lan" being enabled in the BIOS. after disabling it, the computer shuts down correctly. i would encourage others that are experiencing this problem to check the settings in the BIOS. it is also probable that the linux driver for the LAN on board this HP dc5100mt motherboard may need updating.

have the same problem but wake on lan is not enabled in the bios

Edmond Thiebaud, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily kernel folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11.1

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]