K 10
svn:author
V 3
rrs
K 8
svn:date
V 27
2010-01-22T14:25:17.869457Z
K 7
svn:log
V 403
This hopefully will fix the network problem I was seeing.
Basically the msg ring interrupt was being re-enabled
inside a spinlock as the thread set it self up for rescheduling.
This won't work since inside the re-enable is another
spin lock.. which means on return from the reenable
the  interrupts have been reenabled. Thus you would
get a clock int and end up panicing holding a spin
lock to long :-o

END