From: Jean T. <jt...@bo...> - 2003-07-28 23:15:19
|
On Tue, Jul 29, 2003 at 12:25:46AM +0000, an...@an... wrote: > > 19:03:56.883361 xid:rsp 0f8f748c < 25c2d97f S=6 s=1 T610 series > hint=9124 [ PnP Modem IrCOMM IrOBEX ] (28) > 19:03:56.892315 xid:cmd 0f8f748c > ffffffff S=6 s=2 (14) > 19:03:56.982297 xid:cmd 0f8f748c > ffffffff S=6 s=3 (14) > 19:03:57.072281 xid:cmd 0f8f748c > ffffffff S=6 s=4 (14) > 19:03:57.162279 xid:cmd 0f8f748c > ffffffff S=6 s=5 (14) > 19:03:57.252272 xid:cmd 0f8f748c > ffffffff S=6 s=* sigma hint=c404 [ > Computer LAN Access IrCOMM ] (22) > 19:03:57.292299 snrm:cmd ca=fe pf=1 0f8f748c > 25c2d97f new-ca=c0 > LAP QoS: Baud Rate=4000000bps Max Turn Time=500ms Data > Size=2048B Window Size=7 Add BOFS=0 Min Turn Time=1000us Link Disc=12s > (33) > 19:03:57.402797 ua:rsp ca=c0 pf=1 0f8f748c < 25c2d97f > LAP QoS: Baud Rate=115200bps Max Turn Time=500ms Data Size=256B > Window Size=3 Add BOFS=0 Min Turn Time=50us Link Disc=12s (31) > 19:03:57.402972 rr:cmd > ca=c0 pf=1 nr=0 (2) > 19:03:57.413511 rr:rsp < ca=c0 pf=1 nr=0 (2) > 19:03:57.413612 i:cmd > ca=c0 pf=1 nr=0 ns=0 LM slsap=18 dlsap=00 > CONN_CMD (6) > 19:03:57.420681 i:rsp < ca=c0 pf=1 nr=1 ns=0 LM slsap=00 dlsap=18 > CONN_RSP (6) > 19:03:57.420791 i:cmd > ca=c0 pf=1 nr=1 ns=1 LM slsap=18 dlsap=00 > GET_VALUE_BY_CLASS: "IrDA:IrCOMM" "Parameters" (28) > 19:03:57.429253 i:rsp < ca=c0 pf=1 nr=2 ns=1 LM slsap=00 dlsap=18 > GET_VALUE_BY_CLASS: Success > IrCOMM Parameters Service Type=NINE_WIRE THREE_WIRE Port > Type=PARALLEL (19) > 19:03:57.429502 i:cmd > ca=c0 pf=0 nr=2 ns=2 LM slsap=18 dlsap=00 DISC > (6) > 19:03:57.430617 i:cmd > ca=c0 pf=1 nr=2 ns=3 LM slsap=19 dlsap=00 > CONN_CMD (6) That's a Ericsson phone, correct ? Check towards the bottom of my web page for the workaround for buggy Ericsson phones. If it's not an Ericsson phone, apply the same workaround and test. By the way, you are the first person reporting to me that the VIA driver works, so it gives me more confidence on the driver. > > Real problems to look into : > >> irlmp_state_setup() WATCHDOG_TIMEOUT! > what means this error? , y encounter the line but this only sounds me as > an option in menuconfig :-). Ok, your comment in state_connect() says > that this happend with race condition, with what?, is trying > initializing and at same time connect?. I'll look for this but i think > is very out of my awknoledge. > >> IrLAP, no activity on link! > >> irlap_driver_rcv(), wrong connection address! > info.caddr = skb->data[0] & CBROADCAST; > it seems is here the problem no? info.caddr=0, i think isn't condition > info.cadrr!=self->cadrr > But this estructure(packet or frame) come from a inside layer, not to > via-driver nor irlap, no? > I will look this, for curiosity. > > The third one is *really* scary. > I'll try to printk other variables(IRDA_DEBUG I guess), if you want. The first is a consequence of the stuff seen in the irdadump above, so don't worry. The second as well, actually. For the third, I'll blame that on the phone, but it may be the VIA hardware or driver. > regards, > Angel Have fun... Jean |