Okay, now this is getting weird.

I've got md5-identical 'if_ray.c' on my two systems.  I turned on all the
debug options.

Samples:
>949693697:358463 0:000180: ray0: copying mbuf 0xf069d708 bufp 0x2024 len 60
>ray0: pkt dump:
>	 08 00 00 00 ff ff ff ff   ff ff 00 00 f1 11 5d 32
>	 c2 00 1c 78 4c 7a 00 00   aa aa 03 00 00 00 08 06
>	 00 01 08 00 06 04 00 01   00 00 f1 11 5d 32 c0 81
>	 54 82 00 00 00 00 00 00   c0 81 54 83
>949693697:358643 0:000886: ray0: ray_start issueing 2 
>949693697:359529 0:000175: ray0: sent packet: len 60
>949693697:359704 0:997643: ray0: start free 14 qlen 1 qmax 50
>949693698:357347 0:000227: ray0: ray_cmd_cancel 0x8
>949693698:357574 0:000175: ray0: gotmbuf 0xf069d008
>949693698:357749 0:000163: ray0: mbuf.m_pkthdr.len 42
>949693698:357912 0:000172: ray0: got pulled up mbuf 0xf069d008
>949693698:358084 0:000191: ray0: i 3 previ 255
>949693698:358275 0:000171: ray0: ray_alloc_tx_ccs bufp 0x2820 idx 3 pidx 255 
>949693698:358446 0:000219: ray0: bufp 0x2824 new pktlen 60
>949693698:358665 0:000179: ray0: copying mbuf 0xf069d008 bufp 0x2824 len 60
>ray0: pkt dump:
>	 08 00 00 00 ff ff ff ff   ff ff 00 00 f1 11 5d 32
>	 c2 00 1c 78 4c 7a 00 00   aa aa 03 00 00 00 08 06
>	 00 01 08 00 06 04 00 01   00 00 f1 11 5d 32 c0 81
>	 54 82 00 00 00 00 00 00   c0 81 54 83
>949693698:358844 0:000884: ray0: ray_start issueing 3 
>949693698:359728 0:000172: ray0: sent packet: len 60
>949693698:359900 66:269108: ray0: start free 14 qlen 1 qmax 50

That's from the desktop.


>949693819:668894 0:001038: ray0: interrupt handled 1
>949693819:669932 0:001491: ray0: ray_intr
>949693819:671423 0:000370: ray0: ray_ccs_done idx 0 cmd 0x9 stat 0
>949693819:671793 0:000509: ray0: ray_check_scheduled enter schd 0x0 running 0x0 ready 1
>949693819:672302 0:000689: ray0: ray_check_scheduled exit sched 0x0 running 0x0 ready 1
>949693819:672991 0:000686: ray0: interrupt handled 1
>949693819:673677 0:073970: ray0: ray_intr
>949693819:747647 0:000396: ray0: ray_ccs_done idx 0 cmd 0x9 stat 0
>949693819:748043 0:000526: ray0: ray_check_scheduled enter schd 0x0 running 0x0 ready 1
>949693819:748569 0:000678: ray0: ray_check_scheduled exit sched 0x0 running 0x0 ready 1
>949693819:749247 0:000686: ray0: interrupt handled 1
>949693819:749933 0:150097: ray0: ray_intr
>949693819:900030 0:000389: ray0: ray_ccs_done idx 0 cmd 0x9 stat 0
>949693819:900419 0:000528: ray0: ray_check_scheduled enter schd 0x0 running 0x0 ready 1
>949693819:900947 0:000684: ray0: ray_check_scheduled exit sched 0x0 running 0x0 ready 1
>949693819:901631 0:000681: ray0: interrupt handled 1
>949693819:902312 0:001126: ray0: ray_intr
>949693819:903438 0:000371: ray0: ray_ccs_done idx 0 cmd 0x9 stat 0
>949693819:903809 0:000508: ray0: ray_check_scheduled enter schd 0x0 running 0x0 ready 1
>949693819:904317 0:000685: ray0: ray_check_scheduled exit sched 0x0 running 0x0 ready 1

That's from the laptop.

Why aren't they in the same format?  It looks as though it really is that
the laptop isn't sending, I guess.  ThinkPad, running under CardBus.  Got the
same results with PCMCIA.  Unfortunately, I don't read this well enough to
understand what it's doing.

-s