Randall Stewart
9b84f07357
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
2010-01-22 14:25:17 +00:00
2010-01-19 17:20:34 +00:00
2010-01-19 17:20:34 +00:00
2010-01-18 06:48:24 +00:00
2009-09-29 21:25:59 +00:00
2010-01-10 09:20:56 +00:00
2010-01-11 23:15:11 +00:00
2010-01-18 22:46:06 +00:00
2010-01-19 17:20:34 +00:00
2010-01-21 21:31:39 +00:00
2010-01-08 15:44:49 +00:00
2010-01-22 09:54:40 +00:00
2010-01-22 08:45:12 +00:00
2010-01-17 06:20:30 +00:00
2010-01-14 14:30:54 +00:00
2010-01-19 17:20:34 +00:00
2010-01-14 02:48:39 +00:00
2010-01-07 21:01:37 +00:00
2010-01-20 11:58:04 +00:00
2010-01-06 05:58:07 +00:00
2010-01-22 14:25:17 +00:00
2010-01-16 17:08:22 +00:00
2010-01-19 04:29:42 +00:00
2010-01-19 05:00:57 +00:00
2009-08-12 10:44:13 +00:00
2010-01-18 20:34:00 +00:00
2010-01-22 07:53:41 +00:00
2010-01-17 13:07:52 +00:00
2009-11-29 20:47:43 +00:00
2009-09-10 18:33:08 +00:00
2009-07-12 03:53:52 +00:00
2010-01-21 21:59:10 +00:00
2010-01-09 15:59:15 +00:00
2009-10-07 19:50:14 +00:00
2010-01-09 15:43:47 +00:00
2010-01-19 17:20:34 +00:00
2010-01-07 21:01:37 +00:00
2010-01-19 17:20:34 +00:00
2010-01-12 07:49:34 +00:00
2010-01-12 07:49:34 +00:00
2010-01-19 17:20:34 +00:00
2010-01-10 17:44:22 +00:00
2010-01-20 22:45:59 +00:00
2009-11-12 00:36:22 +00:00
2009-10-25 09:48:21 +00:00
2010-01-11 22:42:06 +00:00
2010-01-17 21:26:14 +00:00
2009-08-12 16:27:51 +00:00
2010-01-07 21:01:37 +00:00
9b84f07357