Looking at hald/util.c I can see at least a couple of places that might
be responsible for this. Back in 2005 there was a patch to fix these
reports called "hal-fix-seqfault_if_addon_missing.diff". Unfortunately
hald's util.c has been reworked since then and the issues that patch
addressed may have been inadvertently not been handled by the new code.
To get an idea of which device is causing the issue we need a couple of
log files from a clean start. The files are:
/var/log/messages
/var/log/debug
/var/log/dmesg
Before restarting you should remove or delete the first two existing log
files so they will be freshly created at boot-time (dmesg is recreated
each start). The reason for these two is:
1) both have timestamps that can be matched to events
2) debug inadvertently contains reports of hal_device_added/removed events
through NetworkManager's debug-logging.
Once you've captured the error in the logs please put them together and
attach them to a comment:
$ tar -czvf hald-addon-acpi-debug-logs.tar.gz /var/log/dmesg
/var/log/messages /var/log/debug
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: Triaged => In Progress
--
hald-addon-acpi[5115]: segfault at 0000000025c831f8...error 4, 2.6.22-9 kernel
acpi segfault
https://bugs.launchpad.net/bugs/130221
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
