I’m connecting a USB device to the Beaglebone Black. The device (a custom STM32 based board) has a virtual COM port over USB, which naturally appears as /dev/ttyACM0 on the Beagle, as expected.
However, the first time I disconnect the device from the Beagle, I do not get remove events from the Beagle kernel (using udevadm to monitor this). This means that the /dev/ttyACM0 remains.
On reconnecting the device, the remove events finally appear (!), and then the new add events. From here on, disconnects and reconnects do the right thing (the kernel reports remove and add events at the time they happen).
Has anyone else encountered this issue?