Look up that address (0012463d) from your System.map file and find out what
function is scheduling in an interrupt. That will give a clue as to the
error and where to go about fixing things. You can also switch the line in
schedule.c from a printk to a panic to freeze the machine when this happens.
It should freeze with interrupts enabled so that you can use
shift-pageup/down to see any other error messages that might be on the
console and grab them before you reboot the machine. If not, you can add an
explicit sti(); before the panic call to enable the keyboard and allow the
screen manipulation.
----------------------------------
E-Mail: Doug Ledford <dledford@dialnet.net>
Date: 05-Jan-98
Time: 01:49:34
----------------------------------