Hi Greg, > Ah, I forgot to change the .name fields on this driver, sorry. Here's a > patch that fixes the problem for me, please let me know if it works for > you or not.
Thanks! This fixed the oops message. However, the hang on close still remains: Last message from debug=1: drivers/usb/serial/digi_acceleport.c: digi_close: TOP: port=1, open_count=0 The digi_close: done never appears... lsmod still shows a usage of 1: digi_acceleport 19172 1 minicom is in "D" state: ps ao pid,command,state,wchan 1488 minicom D down_failed Further debugging showed: serial_close downs &port->sem, then calls digi_close. digi_close calls tty_wait_until_sent. tty_wait_until_sent calls serial_chars_in_buffer. serial_chars_in_buffer tries to down &port->sem again, and here it hangs. Have fun ;-) --jochen ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
