![]() | |||||||||||||
Messages in this thread |
On 05-Jan-98 Mika Ruikka wrote: >Error message on the console, before freezes is : >Aiee scheduling in interrupt 0012463d > >Is there any way to get any signs, what might cause such error. I guess >it has something to do with new hardware, but I'd like to know which >hardware is the possible cause. > >System : > redhat5.0 > PentiumII 233 > asus P2L97 motherboard > adaptec2940 SCSIbus > 3com905TX ethernetcard 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 ---------------------------------- | ||||||||||||
| Last update: 2005-03-22 12:41 [W:2.540 / U:0.020 seconds] ©2003-2008 Jasper Spaans | |||||||||||||