Am Samstag, 5. September 2009 19:50:19 schrieb Paul Martin:
> cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN
> adapters drivers/usb/class/cdc-acm.c: Entering acm_tty_open.
> drivers/usb/class/cdc-acm.c: acm_control_msg: rq: 0x22 val: 0x3 len: 0x0 result: 0
> drivers/usb/class/cdc-acm.c: tty_port_block_til_ready returned -512
This is very hard to explain. I can't see how tty_port_block_til_ready()
can return -512
Are you using any non-standard patches?
Alan, does this make sense to you?
Regards
Oliver
commit e1b8b513bcba5313efa8b1637c5d9490a1944236
Author: Oliver Neukum <oliver@xxxxxxxxxx>
Date: Fri Sep 4 19:53:04 2009 +0200
usb:cdc-acm: additional debugging output
diff --git a/drivers/usb/class/cdc-acm.c b/drivers/usb/class/cdc-acm.c
index 2bfc41e..d4e6c05 100644
--- a/drivers/usb/class/cdc-acm.c
+++ b/drivers/usb/class/cdc-acm.c
@@ -610,6 +610,8 @@ static int acm_tty_open(struct tty_struct *tty, struct file *filp)
tasklet_schedule(&acm->urb_task);
rv = tty_port_block_til_ready(&acm->port, tty, filp);
+ if (rv < 0)
+ dbg("tty_port_block_til_ready returned %d", rv);
done:
mutex_unlock(&acm->mutex);
err_out:
