"d20d60be28cb4a98a668930353fa3f3e7c0b76c1" (history) in projects: freebsd

Searched hist:d20d60be28cb4a98a668930353fa3f3e7c0b76c1 (Results 1 – 2 of 2) sorted by relevance

/freebsd/sys/amd64/amd64/
H A D	vm_machdep.c	diff d20d60be28cb4a98a668930353fa3f3e7c0b76c1 Sat Mar 14 04:02:15 CET 1998 Tor Egge <tegge@FreeBSD.org> Don't use the standard macros for disabling/enabling interrupt. On SMP systems, this left the mpintr_lock simplelock locked, causing further calls to disable_intr to deadlock or panic. diff d20d60be28cb4a98a668930353fa3f3e7c0b76c1 Sat Mar 14 04:02:15 CET 1998 Tor Egge <tegge@FreeBSD.org> Don't use the standard macros for disabling/enabling interrupt. On SMP systems, this left the mpintr_lock simplelock locked, causing further calls to disable_intr to deadlock or panic.
/freebsd/sys/i386/i386/
H A D	vm_machdep.c	diff d20d60be28cb4a98a668930353fa3f3e7c0b76c1 Sat Mar 14 04:02:15 CET 1998 Tor Egge <tegge@FreeBSD.org> Don't use the standard macros for disabling/enabling interrupt. On SMP systems, this left the mpintr_lock simplelock locked, causing further calls to disable_intr to deadlock or panic. diff d20d60be28cb4a98a668930353fa3f3e7c0b76c1 Sat Mar 14 04:02:15 CET 1998 Tor Egge <tegge@FreeBSD.org> Don't use the standard macros for disabling/enabling interrupt. On SMP systems, this left the mpintr_lock simplelock locked, causing further calls to disable_intr to deadlock or panic.