9b84f07357
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 |
||
|---|---|---|
| .. | ||
| adm5120 | ||
| alchemy | ||
| atheros | ||
| cavium | ||
| compile | ||
| conf | ||
| idt | ||
| include | ||
| malta | ||
| mips | ||
| rmi | ||
| sentry5 | ||
| sibyte | ||