I saw this error in my syslog when hal-probe-storage is running about my removable medias : Jul 12 09:08:54 localhost hald-probe-storage: [8935]: 09:08:54.413 [D] probe-storage.c:155: Doing probe-storage for /dev/sdd (bus usb) (drive_type disk) (udi=/org/freedesktop/Hal/devices/temp/240) (--only-check-for-fs==0) Jul 12 09:08:54 localhost hald-probe-storage: [8935]: 09:08:54.413 [D] probe-storage.c:407: Checking for file system on /dev/sdd Jul 12 09:08:54 localhost hald-probe-storage: [8935]: 09:08:54.413 [D] probe-storage.c:413: Doing open ("/dev/sdd", O_RDONLY) Jul 12 09:08:54 localhost hald-probe-storage: [8935]: 09:08:54.415 [D] probe-storage.c:416: Cannot open /dev/sdd: No medium found Jul 12 09:08:54 localhost hald[2276]: 09:08:54.422 [I] hald_dbus.c:1366: storage.removable.media_available -> False Jul 12 09:08:54 localhost hald[2276]: 09:08:54.425 [I] blockdev.c:387: entering; exit_type=0, return_code=0 Jul 12 09:08:54 localhost hald[2276]: 09:08:54.431 [I] blockdev.c:141: Add callouts completed udi=/org/freedesktop/Hal/devices/storage_serial_Generic_USB_SM_Reader_058F312D81B_0_2 Jul 12 09:08:54 localhost hald[2276]: 09:08:54.431 [D] device_store.c:516: adding 0xfd2020 to (linux.sysfs_path,/sys/devices/pci0000:00/0000:00:13.5/usb1/1-9/1-9:1.0/host13/target13:0:0/13:0:0:2/block/sdd) Jul 12 09:08:54 localhost hald[2276]: 09:08:54.431 [I] hald.c:108: Added device to GDL; udi=/org/freedesktop/Hal/devices/storage_serial_Generic_USB_SM_Reader_058F312D81B_0_2 Jul 12 09:08:54 localhost hald[2276]: 09:08:54.438 [I] hald_runner.c:659: running_processes 0xfffe90, num = 7 Jul 12 09:08:54 localhost hald[2276]: 09:08:54.438 [I] hald.c:120: Started addon hald-addon-storage for udi /org/freedesktop/Hal/devices/storage_serial_Generic_USB_SM_Reader_058F312D81B_0_2 Jul 12 09:08:54 localhost hald[2276]: 09:08:54.464 [D] hald_dbus.c:3294: udi=/org/freedesktop/Hal/devices/storage_serial_Generic_USB_SM_Reader_058F312D81B_0_2 Jul 12 09:08:54 localhost hald[2276]: 09:08:54.464 [I] hald_dbus.c:3320: AddonIsReady on udi '/org/freedesktop/Hal/devices/storage_serial_Generic_USB_SM_Reader_058F312D81B_0_2' Jul 12 09:08:54 localhost hald[2276]: 09:08:54.466 [D] hald_dbus.c:3294: udi=/org/freedesktop/Hal/devices/storage_serial_Generic_USB_SM_Reader_058F312D81B_0_2 --- Jul 12 09:08:54 localhost hald[2276]: 09:08:54.466 [E] device.c:1705: In hal_device_inc_num_ready_addons for udi=/org/freedesktop/Hal/devices/storage_serial_Generic_USB_SM_Reader_058F312D81B_0_2 but all addons are already ready! --- Jul 12 09:08:54 localhost hald[2276]: 09:08:54.466 [I] hald_dbus.c:3320: AddonIsReady on udi '/org/freedesktop/Hal/devices/storage_serial_Generic_USB_SM_Reader_058F312D81B_0_2' Jul 12 09:08:54 localhost hald-addon-storage: [8936]: 09:08:54.467 [D] addon-storage.c:748: ************************************************** Jul 12 09:08:54 localhost hald-addon-storage: [8936]: 09:08:54.468 [D] addon-storage.c:749: Doing addon-storage for /dev/sdd (bus usb) (drive_type smart_media) (udi /org/freedesktop/Hal/devices/storage_serial_Generic_USB_SM_Reader_058F312D81B_0_2) Jul 12 09:08:54 localhost hald-addon-storage: [8936]: 09:08:54.468 [D] addon-storage.c:750: ************************************************** Reproducible: Always
I don't really see an error. I see the addon trying to open the device to see if there's media. There's no media so it continues on..
(In reply to comment #1) > I don't really see an error. I see the addon trying to open the device to see > if there's media. There's no media so it continues on.. > Isn't it an error ? --- Jul 12 09:08:54 localhost hald[2276]: 09:08:54.466 [E] device.c:1705: In hal_device_inc_num_ready_addons for udi=/org/freedesktop/Hal/devices/storage_serial_Generic_USB_SM_Reader_058F312D81B_0_2 but all addons are already ready! ---
No. Your device caused a system call to block for a while. And HAL didn't get a response from an addon so it assumed after a bit that the addon had gone away and tried to start up another addon. Then the blocked addon came back to life and so it realized that there were 2 addons for a device so it got rid of one.
(In reply to comment #3) > No. Your device caused a system call to block for a while. And HAL didn't get a > response from an addon so it assumed after a bit that the addon had gone away > and tried to start up another addon. Then the blocked addon came back to life > and so it realized that there were 2 addons for a device so it got rid of one. > Ok thanks for your explanation Doug, sorry for the uneeded noise. You can close the report as invalid.
No problem. I had to look into it myself. Does this constantly flood syslog or does it only happen once in your logs?
(In reply to comment #5) > No problem. I had to look into it myself. Does this constantly flood syslog or > does it only happen once in your logs? > The log appears once (at boot) for each usb mass storage I have on my box (flash card reader, MMC/SD card reader, smart-media reader, stick-memroy reader).
(In reply to comment #6) > (In reply to comment #5) > > No problem. I had to look into it myself. Does this constantly flood syslog or > > does it only happen once in your logs? > > > The log appears once (at boot) for each usb mass storage I have on my box > (flash card reader, MMC/SD card reader, smart-media reader, stick-memroy > reader). > It happens about my CD/DVD RW too.
This is not a bug. HAL probes storage devices to see if there is media (be it cards or CDs/DVDs) in there that it could (or should, depending on policy) mount.
