Re: uplcom(4) problem

[Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx>]

:I also get messages like this (which I didn't get with the earlier
:ucom.c)
:
:   ucom0: ucomreadcb: CANCELLED

   I get that too.  it should be ok.  But, shoot, I was hoping I had fixed
   your problem too :-(

:This is what ppp.log says:
:
 
    I'm not a ppp expert.  Do a ktrace -i of the ppp program and put the
    ktrace.out file somewhere where I can fetch it (do not email me the
    kdump output).  That might help me characterize the problem.

    Separately it may be useful to turn on USB debugging in DragonFly land.
    i.e. 'options USB_DEBUG' in your kernel config.  You can then turn on 
    various debugging actions with hw.usb.<blah> sysctls (sysctl hw.usb for
    a list).  It should be possible to tell whether the USB is getting 
    receive data or not that way.

    The only real difference I saw in the linux code was that 0x41/0x61 
    stuff.  Obviously that isn't the problem since it doesn't work under
    Linux either way.  That could mean that it may be difficult to find it
    in DragonFly, I would probably need the device itself and even then I
    might not be able to get it to work.

					-Matt
					Matthew Dillon 
					<dillon@xxxxxxxxxxxxx>

:Oct 17 11:21:46 bluerondo ppp[664]: tun0: Phase: deflink: Connected! 
:Oct 17 11:21:46 bluerondo ppp[664]: tun0: Phase: deflink: opening -> dial 
:Oct 17 11:21:46 bluerondo ppp[664]: tun0: Chat: Phone: ##7# 
:Oct 17 11:21:46 bluerondo ppp[664]: tun0: Chat: deflink: Dial attempt 1 of 1 
:Oct 17 11:21:46 bluerondo ppp[664]: tun0: Chat: Send: AT+CRM=1^M 
:Oct 17 11:21:46 bluerondo ppp[664]: tun0: Chat: Expect(5): OK 
:Oct 17 11:21:51 bluerondo ppp[664]: tun0: Chat: Expect timeout 
:Oct 17 11:21:51 bluerondo ppp[664]: tun0: Chat: Send: AT+CRM=1^M 
:Oct 17 11:21:51 bluerondo ppp[664]: tun0: Chat: Expect(5): OK 
:Oct 17 11:21:56 bluerondo ppp[664]: tun0: Chat: Expect timeout 
:Oct 17 11:21:56 bluerondo ppp[664]: tun0: Warning: Chat script failed