Thank you for your bug report. If the machine completely freezes, then
that's unlikely to be a HAL issue, but a kernel issue instead. Are you
running this from within Gnome/KDE? If so, could you please try running
it from a console instead (CTRL+ALT+F1). Does it freeze like this, and
are there any error messages displayed at the point that the machine
freezes? Could you please take a photograph of the screen?

If it crashes from the terminal but you don't see any useful messages,
then please try again from the terminal after changing the kernel
loglevel. To do this, run the following before starting HAL:

echo 8 | sudo tee /proc/sys/kernel/printk

Could you also please also attach the following additional information:

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" after a fresh boot 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.

Thanks in advance

** Changed in: hal (Ubuntu)
       Status: New => Incomplete

-- 
hal foreground/verbose mode crashes system
https://bugs.launchpad.net/bugs/304786
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to