On 04/18/2012 03:42 PM, Chris Friesen wrote:
I have a 2.6.34.10-based kernel with udev-161 (also tested with udevadm from udev-173). When I run "udevadm info --attribute-walk --path=/block/sda" it just shows the device itself, and doesn't walk the whole chain showing the parents. Is there anything I can do, or am I caught with a kernel that isn't properly supported? I'm not subscribed to the hotplug list, so cc'ing me would be appreciated. I don't know what's causing the problem, but I find it suspicious that /sys/block/sda is a directory rather than a symlink like it is on my 2.6.35.14 laptop. I'm poking around in the udevadm code now. Some possibly-useful information:
I forgot to include this....this might be useful as well: root@typhoon-base-unit0:/root> udevadm info -q path -n /dev/sda /block/sda For comparison, on my 2.6.35.14 laptop I get: [cfriesen@blah log]$ udevadm info -q path -n /dev/sda /devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda -- Chris Friesen Software Developer GENBAND chris.friesen@xxxxxxxxxxx www.genband.com -- To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
