Possible missing file in hal installation
Joe Marcus Clarke
marcus at marcuscom.com
Wed Jan 3 00:54:07 PST 2007
On Wed, 2007-01-03 at 16:26 +0800, manphiz at gmail.com wrote:
> Joe Marcus Clarke wrote:
> > On Mon, 2007-01-01 at 02:12 +0800, manphiz at gmail.com wrote:
> >
> >> I've been frustrating by the hal problem which is probably due to lack
> >> of hald-addon-acpi or similar stuff. here's the output from the commands:
> >>
> >> -----BEGIN PASTE-----
> >>
> >> # hald --daemon=no --verbose=yes
> >> 00:36:17.136 [I] hald.c:469: hal 0.5.8
> >> 00:36:17.136 [I] hald.c:534: Will not daemonize
> >> 00:36:17.136 [I] hald_dbus.c:3238: local server is listening at
> >> unix:path=/var/run/hald/dbus-tc8Wy2La5k,guid=ad4c24e578b961e09af77c004597e701
> >> 00:36:17.146 [I] hald_runner.c:116: Runner has pid 64356
> >> Runner started - allowed paths are
> >> '/usr/local/libexec:/usr/local/libexec/hal/scripts:/usr/local/bin'
> >> 00:36:17.167 [I] hf-usb.c:575: unable to open /dev/usb: Device busy
> >> Run started hald-probe-smbios (10000) (0)
> >> ! full path is '/usr/local/libexec/hald-probe-smbios', program_dir is
> >> '/usr/local/libexec'
> >> 00:36:17.248 [I] hald_dbus.c:3197: 64355: Got a connection
> >> 00:36:17.248 [I] hald_dbus.c:3198: dbus_connection_get_is_connected = 1
> >> 00:36:17.252 [D] hald_dbus.c:1194:
> >> udi=/org/freedesktop/Hal/devices/computer, key=smbios.bios.vendor
> >> hald-probe-smbios info: Setting smbios.bios.vendor='Phoenix'
> >> 00:36:17.252 [D] hald_dbus.c:1194:
> >> udi=/org/freedesktop/Hal/devices/computer, key=smbios.bios.version
> >> hald-probe-smbios info: Setting smbios.bios.version='G.W-0F05'
> >> 00:36:17.253 [D] hald_dbus.c:1194:
> >> udi=/org/freedesktop/Hal/devices/computer, key=smbios.bios.release_date
> >> hald-probe-smbios info: Setting smbios.bios.release_date='03/08/2004'
> >> 00:36:17.253 [D] hald_dbus.c:1194:
> >> udi=/org/freedesktop/Hal/devices/computer, key=smbios.system.manufacturer
> >> hald-probe-smbios info: Setting smbios.system.manufacturer='GREATWALL'
> >> 00:36:17.254 [D] hald_dbus.c:1194:
> >> udi=/org/freedesktop/Hal/devices/computer, key=smbios.system.product
> >> hald-probe-smbios info: Setting smbios.system.product='M620DC'
> >> 00:36:17.254 [D] hald_dbus.c:1194:
> >> udi=/org/freedesktop/Hal/devices/computer, key=smbios.system.version
> >> hald-probe-smbios info: Setting smbios.system.version='G.W-0F05'
> >> 00:36:17.254 [D] hald_dbus.c:1194:
> >> udi=/org/freedesktop/Hal/devices/computer, key=smbios.system.serial
> >> hald-probe-smbios info: Setting smbios.system.serial='20011221'
> >> 00:36:17.255 [D] hald_dbus.c:1194:
> >> udi=/org/freedesktop/Hal/devices/computer, key=smbios.system.uuid
> >> hald-probe-smbios info: Setting
> >> smbios.system.uuid='436F6F70-6572-5370-7572-5F424F415244'
> >> 00:36:17.255 [D] hald_dbus.c:1194:
> >> udi=/org/freedesktop/Hal/devices/computer, key=smbios.chassis.manufacturer
> >> hald-probe-smbios info: Setting smbios.chassis.manufacturer='GREATWALL'
> >> 00:36:17.256 [D] hald_dbus.c:1194:
> >> udi=/org/freedesktop/Hal/devices/computer, key=smbios.chassis.type
> >> hald-probe-smbios info: Setting smbios.chassis.type='Other'
> >> /usr/local/libexec/hald-probe-smbios exited
> >> 00:36:17.257 [I] hald_dbus.c:3175: Client to local_server was disconnected
> >> 00:36:17.257 [I] hald_dbus.c:3185: unregistered
> >> 00:36:17.271 [I] device_info.c:1427: *** Matched file
> >> /usr/local/share/hal/fdi/policy/10osvendor/10-power-mgmt-policy.fdi
> >> 00:36:17.272 [I] device_info.c:1427: *** Matched file
> >> /usr/local/share/hal/fdi/policy/10osvendor/20-storage-methods.fdi
> >> 00:36:17.272 [I] util.c:972: Add callouts for
> >> udi=/org/freedesktop/Hal/devices/computer
> >> Run started hal-system-storage-cleanup-mountpoints (10000) (0)
> >> ! full path is
> >> '/usr/local/libexec/hal/scripts/hal-system-storage-cleanup-mountpoints',
> >> program_dir is '/usr/local/libexec/hal/scripts'
> >> /usr/local/libexec/hal/scripts/hal-system-storage-cleanup-mountpoints exited
> >> 00:36:17.301 [I] hald.c:82: Added device to GDL;
> >> udi=/org/freedesktop/Hal/devices/computer
> >> Run started hald-addon-acpi (0) (0)
> >> ! full path is 'hald-addon-acpi', program_dir is '(null)'
> >> 00:36:17.323 [I] hald.c:95: Started addon hald-addon-acpi for udi
> >> /org/freedesktop/Hal/devices/computer
> >>
> >> -----END PASTE-----
> >>
> >> then it got stuck and CPU ran up to 100%. Evidence shows it is very
> >> likely related to the missing of hald-addon-acpi.
> >>
> >> Here's some system information maybe helpful:
> >>
> >> -----BEGIN PASTE-----
> >>
> >> $ uname -a
> >> FreeBSD localhost. 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #2: Sun Dec 31
> >> 19:42:43 CST 2006 root at localhost.:/usr/obj/usr/src/sys/GENERIC i386
> >>
> >> $ pkg_info | grep hal-0.5.8
> >> hal-0.5.8.20061224 Hardware Abstraction Layer for simplifying device access
> >>
> >> $ /usr/bin/env
> >> DESKTOP_STARTUP_ID=
> >> SHELL=/usr/local/bin/bash
> >> TERM=xterm
> >> CLICOLOR=YES
> >> GTK_RC_FILES=/usr/local/etc/gtk/gtkrc:/home/manphiz/.gtkrc-1.2-gnome2
> >> WINDOWID=18888129
> >> USER=manphiz
> >> GNOME_KEYRING_SOCKET=/var/tmp/keyring-BXcAW6/socket
> >> SESSION_MANAGER=local/localhost.:/tmp/.ICE-unix/52216
> >> FTP_PASSIVE_MODE=YES
> >> PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/usr/X11R6/bin:/home/manphiz/bin
> >> MAIL=/var/mail/manphiz
> >> BLOCKSIZE=K
> >> PWD=/home/manphiz
> >> XMODIFIERS=@im=fcitx
> >> LANG=en_US.UTF-8
> >> HOME=/home/manphiz
> >> SHLVL=2
> >> GNOME_DESKTOP_SESSION_ID=Default
> >> LOGNAME=manphiz
> >> DBUS_SESSION_BUS_ADDRESS=unix:path=/var/tmp/dbus-RoAXiZNHSv,guid=fb2bbd6083c53125a2981d004597f8a1
> >> LC_CTYPE=zh_CN.UTF-8
> >> DISPLAY=:0.0
> >> COLORTERM=gnome-terminal
> >> XAUTHORITY=/home/manphiz/.Xauthority
> >> _=/usr/bin/env
> >>
> >> -----END PASTE-----
> >>
> >> Also, from discussion on ##freebsd at freenode, hald-addon-acpi is
> >> considered to be linux-stuff, so maybe stale configuration is
> >> responsible too. It is also interesting that there are other people who
> >> also got hald-addon-acpi missing but hald still functions correctly, so
> >> maybe something else is indeed the problem.
> >>
> >
> > You should try ktracing hald to see what it's doing. Or recompile it
> > with debugging symbols, then use gdb to break into it and find out where
> > in the code it's looping. The latter would be the most helpful.
> >
> > Joe
> >
> >
> Thanks for reply! But I encountered some difficulty when trying to debug
> with gdb it lost connection to separate thread, which maybe a little bit
> hard for a newbie like me. Anyway, the last line I'd traced to is:
>
>
> hal_device_store_get_type () at device_store.c:118
> 118 if (!type) {
> (gdb)
> 129 type = g_type_register_static (G_TYPE_OBJECT,
> (gdb)
> 0x28462170 in pthread_rwlock_timedwrlock () from /lib/libpthread.so.2
> (gdb)
> Single stepping until exit from function pthread_rwlock_timedwrlock,
> which has no line number information.
>
> Program received signal SIGTRAP, Trace/breakpoint trap.
> 0x2807ab78 in _rtld_bind_start () from /libexec/ld-elf.so.1
> (gdb)
> Single stepping until exit from function _rtld_bind_start,
> which has no line number information.
> Run started hald-probe-smbios (10000) (0)
> ! full path is '/usr/local/libexec/hald-probe-smbios', program_dir is
> '/usr/local/libexec'
> /usr/local/libexec/hald-probe-smbios exited
> Run started hal-system-storage-cleanup-mountpoints (10000) (0)
> ! full path is
> '/usr/local/libexec/hal/scripts/hal-system-storage-cleanup-mountpoints',
> program_dir is '/usr/local/libexec/hal/scripts'
> /usr/local/libexec/hal/scripts/hal-system-storage-cleanup-mountpoints exited
> Run started hald-addon-acpi (0) (0)
> ! full path is 'hald-addon-acpi', program_dir is '(null)'
> ^C[New Thread 0x8082200 (LWP 100166)]
>
> Program received signal SIGINT, Interrupt.
> [Switching to Thread 0x8082200 (LWP 100166)]
> 0x2847143b in pthread_testcancel () from /lib/libpthread.so.2
>
>
> ^C is where I have to terminate the deadloop, just as shown before.
>
> I've attached the ktrace output as well, hoping there would be something
> useful.
No, there is nothing useful here. The ktrace looks good. The last
thing hald does is read the PCI config registers (part of the initial
PCI bus probe). You need to get a full backtrace from hald once it
appears to lock up. To do that, you should run hald manually, then use
gdb to bind to it once it's locked up. Then get a full backtrace.
Joe
--
PGP Key : http://www.marcuscom.com/pgp.asc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-gnome/attachments/20070103/fa4c43b1/attachment.pgp
More information about the freebsd-gnome
mailing list