Crash's and other issues

[Robert Garrett <robgar@xxxxxxxxxxx>]

tcpdump -vvni reveals a series of incorrect tcp checksums, all incoming ones
are valid. 
    192.168.1.3.1029 > 216.240.41.25.119: Flags [P.], cksum 0xc3ea
(incorrect -> 0xd4a8), seq 2255:2270, ack 2504072, win 1795, options
[nop,nop,TS val 236407 ecr 171513783], length 15
    216.240.41.25.119 > 192.168.1.3.1029: Flags [P.], seq 2504072:2505096,
ack 2270, win 128, options [nop,nop,TS val 171514187 ecr 236407], length
1024
    216.240.41.25.119 > 192.168.1.3.1029: Flags [P.], seq 2505096:2506120,
ack 2270, win 128, options [nop,nop,TS val 171514187 ecr 236407], length
1024
    192.168.1.3.1029 > 216.240.41.25.119: Flags [.], cksum 0xc3db
(incorrect -> 0x8bb1), seq 2270, ack 2506120, win 1763, options [nop,nop,TS
val 236416 ecr 171514187], length 0
    216.240.41.25.119 > 192.168.1.3.1029: Flags [P.], seq 2506120:2506532,
ack 2270, win 128, options [nop,nop,TS val 171514187 ecr 236407], length
412
   

I have and can confirm that several of the issues appear to be fixed, but
yet there are a few more that arent. Enabling anything that makes large use
of socket, and or IP code is still a problem. In other words I am not sure
the netisr problem is quite yet fixed. I am going to try a couple of tests
and see what happens

RG