Red Hat Bugzilla – Bug 176756
hal (platform_bus_device) fails to parse floppy device hotplug events
Last modified: 2013-03-05 22:44:38 EST
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b1) Gecko/20050227 Description of problem: the hald/linux/platform_bus_device.c excpects the floppy sysfs entry to be of the form floppy0 (just search this file for floppy%d) while the linux kernel names the device floppy.0 (see drivers/base/platform.c:platform_device_register) Consequently, the hald ignores the floppy related events (which results in a mount point for /dev/fd0 missing in my fstab) Replacing the sscanf() patterns in platform_bus_device.c with floppy.%d fixed this problem for me. I'm running linux 2.6.12-1.1381_FC3 btw, but this problem exists for quite some time. Version-Release number of selected component (if applicable): hal-0.4.7-1.FC3 How reproducible: Always Steps to Reproduce: 1. start hald with --verbose 2. search the log for floppy 3. Actual Results: 17:12:06.698 [I] linux/osspec.c:795: handling /sys/devices/platform/floppy.0 platform 17:12:06.710 [E] linux/common.c:744: /usr/bin/udevinfo returned 60672 for /block/fd1919903348 17:12:06.711 [E] linux/platform_bus_device.c:78: Could not get device file floppy 1919903348 (this strange fd is the result of sscanf failing and nobody caring to check... tsts) Expected Results: 17:12:06.698 [I] linux/osspec.c:795: handling /sys/devices/platform/floppy.0 platform (without the following error messages, and /dev/fd0 appearing in my fstab) Additional info:
Fedora Core 3 is now maintained by the Fedora Legacy project for security updates only. If this problem is a security issue, please reopen and reassign to the Fedora Legacy product. If it is not a security issue and hasn't been resolved in the current FC5 updates or in the FC6 test release, reopen and change the version to match. Thank you!
Fedora Core 3 is not maintained anymore. Setting status to "INSUFFICIENT_DATA". If you can reproduce this bug in the current Fedora release, please reopen this bug and assign it to the corresponding Fedora version.