https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276697
--- Comment #5 from Christian Weisgerber <na...@freebsd.org> --- I typically have three /dev/uhidN devices on that machine. One from the Yubikey authenticator, two from unrelated USB peripherals. Looking at the ktrace results, I see that firefox spawns a parallel thread for each of my /dev/uhid[0-2] device nodes to check whether the device is an authenticator The threads probing the wrong devices exit quickly, the third one proceeds to establish communications with the authenticator. I wonder whether the results from the threads are mixed up and there is effectively a race between threads for discovering the authenticator. The erratic behavior I observe would fit a race condition. I have now unplugged the other uhid devices, so there is only the single /dev/uhid0 for the authenticator, and so far I have been unable to reproduce the problem. -- You are receiving this mail because: You are the assignee for the bug.
