HP Pavilion a650e (amd64 running Ubuntu/i386) doesn't reboot

00:00.0 Host bridge: nVidia Corporation nForce3 Host Bridge (rev a4)
00:01.0 ISA bridge: nVidia Corporation nForce3 LPC Bridge (rev f6)
00:01.1 SMBus: nVidia Corporation nForce3 SMBus (rev a4)
00:02.0 USB Controller: nVidia Corporation nForce3 USB 1.1 (rev a5)
00:02.1 USB Controller: nVidia Corporation nForce3 USB 1.1 (rev a5)
00:02.2 USB Controller: nVidia Corporation nForce3 USB 2.0 (rev a2)
00:05.0 Ethernet controller: nVidia Corporation nForce3 Ethernet (rev a5)
00:08.0 IDE interface: nVidia Corporation nForce3 IDE (rev a5)
00:0a.0 PCI bridge: nVidia Corporation nForce3 PCI Bridge (rev a2)
00:0b.0 PCI bridge: nVidia Corporation nForce3 AGP Bridge (rev a4)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:00.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX 5500] (rev a1)
02:04.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 07)
02:04.1 Input device controller: Creative Labs SB Live! Game Port (rev 07)
02:05.0 SCSI storage controller: LSI Logic / Symbios Logic 53c895 (rev 02)
02:09.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link)

Matt,

Please attach the contents of these commands:

lspci -vv # more detail
sudo dmidecode
sudp lshw

and the portion of /var/log/messages that includes when you had to power cycle in case there is something at the tail end that hangs up the reboot.

Can you hibernate or suspend to RAM?

These were the last messages in the log:

Mar 15 16:03:35 localhost kernel: [493787.108000] nfsd: last server has exited
Mar 15 16:03:35 localhost kernel: [493787.108000] nfsd: unexporting all filesyst
ems
Mar 15 16:03:35 localhost kernel: [493787.108000] RPC: failed to contact portmap
 (errno -5).
Mar 15 16:03:35 localhost exiting on signal 15

nothing unusual there.

This is quite likely an ACPI problem. One of my questions was if you have ever been able to hibernate or suspend.

The HP website indicates there is a BIOS update for this motherboard:

http://h10025.www1.hp.com/ewfrf/wc/softwareDownloadIndex?softwareitem=pv-22976-2&lc=en&cc=us&dlc=en&tool=softwareCategory&product=428235&query=pavillion%20a650e&os=228

Another option to try is to boot with 'acpi=off' and try a shutdown.

On Thu, Mar 22, 2007 at 07:28:38PM -0000, Tim Gardner wrote:
> This is quite likely an ACPI problem. One of my questions was if you
> have ever been able to hibernate or suspend.

I can't test it right now because I'm using the system for ISO testing for
the beta release. It's a desktop system and I don't normally try; I don't
recall whether it has worked or not in the past.

> The HP website indicates there is a BIOS update for this motherboard:
>
> http://h10025.www1.hp.com/ewfrf/wc/softwareDownloadIndex?softwareitem=pv-22976-2&lc=en&cc=us&dlc=en&tool=softwareCategory&product=428235&query=pavillion%20a650e&os=228

I'm not sure how to install this safely without having Windows on the machine.

> Another option to try is to boot with 'acpi=off' and try a shutdown.

I will try this, and hibernate and suspend, when I have the opportunity.

--
 - mdz

The problem is still here with 2.6.22-9.25. I will see what happens with acpi=off.

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!

This old issue turned out to be the fault of the nvidia driver. If I switch to using nv, the system reboots fine.

Hi mdz,

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with the latest development release of Ubuntu? (ISOs are available from cdimage.ubuntu.com)

If it remains an issue, could you also attach a new /var/log/Xorg.0.log?
Thanks in advance.

On Fri, Nov 07, 2008 at 08:29:18AM -0000, Bryce Harrington wrote:
> Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with the latest development release of Ubuntu? (ISOs are available from cdimage.ubuntu.com)
>
> If it remains an issue, could you also attach a new /var/log/Xorg.0.log?
> Thanks in advance.

It was still an issue earlier in Intrepid, but at some point I switched back
to the nv driver because nvidia was broken, and haven't gotten around to
retesting with nvidia.

--
 - mdz

I just upgraded from Intrepid to Jaunty, and had this happen even when using the nv driver in fact.

Since this bug has a long time here without activity, is it possible to test if this behaviour is still occurring in latest release of Ubuntu Lucid or even better with Maverick? Thanks in advance.

On Thu, Sep 30, 2010 at 06:51:28PM -0000, Kamus wrote:
> Since this bug has a long time here without activity, is it possible to
> test if this behaviour is still occurring in latest release of Ubuntu
> Lucid or even better with Maverick? Thanks in advance.

The system in question still exhibits this behavior with Maverick, though
it's unclear whether it's related to the NVIDIA driver.

The graphics card in it actually died (the fan siezed up and it overheated)
and will need to be replaced anyway. This should help to isolate the
problem.

--
 - mdz

[Expired for nvidia-graphics-drivers-173 (Ubuntu) because there has been no activity for 60 days.]