Roland Sommer
2010-08-23 16:32:33 UTC
Hi,
I'm using Ubuntu 10.04 and succesfully installed opensync with synce for
syncing with evolution (all packages out of Ubuntu repository). Although
this is usually working perfectly, sometimes it even crashes my system
(kernel panic).
After rebooting the system I cannot see any errors in any log files. But
having a small script running in background, which greps the output of
ps periodically, I recognize a difference:
Output a few seconds before the system is crashing:
root 1253 1252 0 Aug05 ? 00:00:00 hald-runner
root 3506 1253 0 19:29 ? 00:00:00
/usr/lib/synce-hal/hal-dccm --device-ip=192.168.131.129
--local-ip=192.168.131.1 --log-level=3
root 3513 1 0 19:29 ? 00:00:00 /usr/sbin/pppd
/dev/ttyUSB0 115200 connect /usr/lib/synce-hal/synce-serial-chat
192.168.131.1:192.168.131.129 ms-dns 192.168.131.1 nodefaultroute noauth
local crtscts linkname synce-device0
Output if it's working fine:
root 1226 1224 0 19:34 ? 00:00:00 hald-runner
root 1800 1226 0 19:37 ? 00:00:00
/usr/lib/synce-hal/hal-dccm --rndis --device-ip=169.254.2.1
--local-ip=169.254.2.2 --log-level=3
root 1906 1 0 19:37 ? 00:00:00 dhclient -pf
/var/run/dhclient-synce-eth1.pid -lf /var/run/dhclient-synce-eth1.lease
-cf /usr/share/synce-hal/dhclient.conf eth1
As far as I understand hald-runner starts hal-dccm with the wrong
options and the kernel is getting panic.
How can I convince hal-dccm to use --rdnis (...) everytime?
TIA
Roland
I'm using Ubuntu 10.04 and succesfully installed opensync with synce for
syncing with evolution (all packages out of Ubuntu repository). Although
this is usually working perfectly, sometimes it even crashes my system
(kernel panic).
After rebooting the system I cannot see any errors in any log files. But
having a small script running in background, which greps the output of
ps periodically, I recognize a difference:
Output a few seconds before the system is crashing:
root 1253 1252 0 Aug05 ? 00:00:00 hald-runner
root 3506 1253 0 19:29 ? 00:00:00
/usr/lib/synce-hal/hal-dccm --device-ip=192.168.131.129
--local-ip=192.168.131.1 --log-level=3
root 3513 1 0 19:29 ? 00:00:00 /usr/sbin/pppd
/dev/ttyUSB0 115200 connect /usr/lib/synce-hal/synce-serial-chat
192.168.131.1:192.168.131.129 ms-dns 192.168.131.1 nodefaultroute noauth
local crtscts linkname synce-device0
Output if it's working fine:
root 1226 1224 0 19:34 ? 00:00:00 hald-runner
root 1800 1226 0 19:37 ? 00:00:00
/usr/lib/synce-hal/hal-dccm --rndis --device-ip=169.254.2.1
--local-ip=169.254.2.2 --log-level=3
root 1906 1 0 19:37 ? 00:00:00 dhclient -pf
/var/run/dhclient-synce-eth1.pid -lf /var/run/dhclient-synce-eth1.lease
-cf /usr/share/synce-hal/dhclient.conf eth1
As far as I understand hald-runner starts hal-dccm with the wrong
options and the kernel is getting panic.
How can I convince hal-dccm to use --rdnis (...) everytime?
TIA
Roland