Matthieu CASTET wrote: > I wonder why the device disconnect like (I didn't do anything special) and > why the driver doesn't see that the device is not here.
I'm pretty sure the disconnect is caused by the device firmware bug. ZyDAS haven't fixed this yet. Nevertheless the LED-related hang (infinite loop) that you saw after the disconnect is/was a driver bug. > PS : I use the snapshot driver with 2.6.18 Which snapshot date? > [1] > Sep 22 18:03:55 localhost kernel: usb 4-2: USB disconnect, address 2 > Sep 22 18:03:56 localhost kernel: zd1211rw 4-2:1.0: zd_chip_control_leds > error - > 19 > Sep 22 18:04:27 localhost last message repeated 31 times > Sep 22 18:05:28 localhost last message repeated 61 times > Sep 22 18:06:29 localhost last message repeated 61 times Looks like the housekeeping work functions rescheduled themselves after the disconnect. There was a possible race where this might have happened for a short time, but it is believed to be fixed now. So this all depends on the date of your snapshot. Daniel ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
