On Wednesday 08 April 2009, Frans Pop wrote:
> Maybe the following will provide some info:
>
> # udevadm test /sys/bus/ccw/devices/0.0.0121
> [...]
> udev_device_new_from_syspath: device 0x42b828 has devpath
> '/devices/css0/0.0.0005/0.0.0121'
> wait_for_file: file '/sys/devices/css0/0.0.0005/0.0.0121/online' appeared
> after 0 loops
> udev_rules_apply_to_event: RUN '/sbin/hwup -A -D $DEVPATH $env{SUBSYSTEM} %b'
> /etc/udev/rules.d/85-sysconfig-hardware.rules:2
> udev_rules_apply_to_event: RUN 'socket:@/org/kernel/udev/monitor'
> /lib/udev/rules.d/95-late.rules:17 udevadm_test: run: '/sbin/hwup -A -D
> /devices/css0/0.0.0005/0.0.0121 ccw '
> udevadm_test: run: 'socket:@/org/kernel/udev/monitor'
>
> Could it be that the last parameter for the call to hwup ("%b") is
> missing? AFAICT the value for that should be "0.0.0121" in this case.
Yes, looks like that's it. After downgrading to udev 0.125 I get:
import_uevent_var: import into environment: 'DRIVER=dasd-eckd'
import_uevent_var: import into environment: 'CU_TYPE=3990'
import_uevent_var: import into environment: 'CU_MODEL=C2'
import_uevent_var: import into environment: 'DEV_TYPE=3390'
import_uevent_var: import into environment: 'DEV_MODEL=02'
import_uevent_var: import into environment: 'MODALIAS=ccw:t3990mC2dt3390dm02'
udevtest: looking at device '/devices/css0/0.0.0005/0.0.0121' from subsystem
'ccw'
wait_for_file: file '/sys/devices/css0/0.0.0005/0.0.0121/online' appeared after
0 loops
udevtest: run: '/sbin/hwup -A -D /devices/css0/0.0.0005/0.0.0121 ccw 0.0.0121'
udevtest: run: 'socket:@/org/kernel/udev/monitor'
Note that those 'import_uevent_var' messages are not displayed with 0.140,
but that may be as expected or unrelated.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
