Comment 1 for bug 190938

Thank you for your bug report. However, we need some more information in order to provide the developers with the information they need to fix this bug. Please attach the output of the following commands(after you've returned from resume):
sudo lspci -vvnn > ~/lspci-vvnn
uname -a > ~/uname-a
cat /proc/version_signature > ~/version_signature
lshal > /tmp/lshal.txt
/var/log/kern.log

all files are located in your home directory, except for the latest, which is a log file.
Please also include the output of this before you resume:
-Open a Terminal and type
sudo /etc/init.d/hal stop
sudo hald --verbose=yes --daemon=no 2>&1 | tee /tmp/hal.log
-Wait for the output the command generates to settle down
Resume
-Go back to the terminal where the sudo hald... comand was executed, press Ctrl+c and execute this:
sudo /etc/init.d/hal start
Now hald is running normally again, it was running in verbose mode earlier.

Please attach the following files:
/tmp/hal.log

Regards