Date: Tue, 26 Sep 2017 22:11:22 -0400 (EDT) From: Mike Andrews <mandrews@bit0.com> To: Hans Petter Selasky <hps@selasky.org> Cc: freebsd-usb@freebsd.org Subject: Re: umodem0, Cisco USB serial console, and quirks Message-ID: <alpine.BSF.2.21.1709262210180.33243@beast.int.bit0.com> In-Reply-To: <0c4022f3-bd21-49b5-cadd-daeb9f1f3081@selasky.org> References: <alpine.BSF.2.21.1709191021260.34953@beast.int.bit0.com> <d9dbef0b-c22e-c7ea-34a2-f36e9e768745@selasky.org> <alpine.BSF.2.21.1709191205280.1218@beast.int.bit0.com> <0c4022f3-bd21-49b5-cadd-daeb9f1f3081@selasky.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 19 Sep 2017, Hans Petter Selasky wrote:
> On 09/19/17 18:15, Mike Andrews wrote:
>> <OPEN|TRANSFERRING|STARTED|SHORT_XFER_OK|BDMA_ENABLE|BDMA_NO_POST_SYNC|BDMA_SETUP|CAN_CANCEL_IMMED|DOING_CALLBACK|0>
>> 12:03:37.726830 usbus4.3 SUBM-BULK-EP=00000082,SPD=FULL,NFR=1,SLEN=0,IVAL=0
>> frame[0] READ 1024 bytes
>> flags 0xa <SHORT_XFER_OK|PIPE_BOF|0>
>> status 0xcf023
>
> Hi,
>
> Look for:
>
> XXXX-BULK-EP=00000082
>
> This is the USB read transfer. The other side is not returning any data, so
> neither is "cu" printing anything. Maybe you can try to get a similar trace
> from the system where it works?
>
> Looks to me like some kind of protocol error, that the Cisco USB serial
> console needs some kind of activation.
Took me a few days to get around to getting usbmon going on Linux. The
verbose dump is too large for the list, so:
https://www.bit0.com/tmp/usbmon-ciscoasa-verbose.txt
https://www.bit0.com/tmp/usbmon-ciscoasa.txt
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.21.1709262210180.33243>