Ubuntu
acpi package

Maverick fails to power down on shutdown command

Asked by Roger Kauffman

I am running Maverick on a 32 bit Intel quad processor with 3 MB ram and several terrabytes of disk space.
I am also running Oracle Virtualbox, ClamAV, Scribus, Open office, Gramps, a Brother HL-3070CW printer (connected as a network printer), and have configured NFS to enable me to exchange files with my netbook which is also running Maverick. Communication is via a Belkin router which also connects the machines to an ADSL 2+ link to the Internet.

My main problem is that when I attempt to shut down the machine either from the desktop GUI or from a command line shutdown command the machine appears to go into a normal shutdown process but then places a series of messages as to what it is doing on the screen until it issues a power down instruction which fails and the machine then hangs. The only way to shut down the machine is to physically hold the power switch for 5 seconds.

I receive a message during boot that a CIR process is unable to load as the memory space allocated is already used. To the best of my knowledge I do not have any infra red services/processes installed in my machine.

I forgot to add that on occasions the system DOES successfully shut down. The problem is not consistent or at least I have not been able to identify the root cause.

I am at a loss as to how to fix this. Any advice would be appreciated.

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu acpi Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#1

Have you logged a bug with acpi?

Revision history for this message
Roger Kauffman (roger-edna) said : 		#2

I guess I am unsure as to whether I have a bug or whether it is my own error causing the problem. I thought it would be useful if I could capture the messages posted on the screen during the shutdown process but I don't seem to be able to do this.

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#3

Could use a camera or cameraphone, you can use photobucket or imageshack to host so you can paste the link here

Revision history for this message
Roger Kauffman (roger-edna) said : 		#4

OK I will give it a go.

Revision history for this message
Roger Kauffman (roger-edna) said : 		#5

Because of the messy way the messages are displayed I attempted to video the process. Unfortunately the camera couldn't focus sufficiently well on the text on the screen. I took a still photo of the final screen, it may be a little more readable but as I suggested it is a mess. Can I use Ubuntu One to put the photo up for you?

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#6

Sure as long as you can paste links on here

Revision history for this message
Roger Kauffman (roger-edna) said : 		#7

OK I guess i am learning the simplest way. I have put the photo up on ImageShack at this URL http://profile.imageshack.us/user/rogerkauffman/

Hope it may be of use.

Revision history for this message
Roger Kauffman (roger-edna) said : 		#8

I apologise. I got the screen shot upload wrong. Hopefully you can read it now.

Revision history for this message
Tobias (ulbricht-tobias) said : 		#9

did you check you have no upgrades appending?

$ sudo aptitude safe-upgrade

did you check to manually turn off the NFS server?

$ sudo /etc/init.d/nfs-kernel-server stop

Revision history for this message
Roger Kauffman (roger-edna) said : 		#10

Thank you Tobias. I tried your suggestion and the upgrades appending check revealed a couple of problems which were corrected but unfortunately this has not solved the original problem. Likewise stopping the NFS kernel had not effect on the problem.

Revision history for this message
Sam_ (and-sam) said : 		#11

> physically hold the power switch for 5 seconds

Rather try MagicSysRq.
http://www.ubuntugeek.com/how-to-use-magic-system-request-keys-in-ubuntu-linux.html

Run MEM test via boot menu.
Boot into a different kernel and verify if the issue remains.
Unplug USB devices.

Check previous log files in /var/log.
syslog.1
kern.log.1
Xorg.1.log

Try mainline kernel and see if the issue remains.
https://wiki.ubuntu.com/Kernel/MainlineBuilds

Reference.
https://wiki.ubuntu.com/DebuggingProcedures
https://wiki.ubuntu.com/DebuggingACPI

Can you help with this problem?

Provide an answer of your own, or ask Roger Kauffman for more information if necessary.

To post a message you must log in.