Messages in this thread | | | Date | Tue, 24 Feb 1998 02:13:19 -0700 | From | Keith Rowland <> | Subject | Determined to fix 2.0.33 Lockups |
| |
Hi everyone,
I joined this list since I saw in the list archives, that others are having the same system lockup problems as I am. I would like to help in tracking this down.
Tonight's lockup has yeilded some additional info that has never been available in the previous 2 months of lock ups. I will provide a more complete report of my system specs and history of my lockup experiences, if this tid bit doesn't prompt one of you with a solution.
My server runs as a colocated web server and this time, the NOC technician reported the following messages scrolled completely up the screen.
Aiee: scheduling in interrupt 001256fd Aiee: scheduling in interrupt 001256fd Aiee: scheduling in interrupt 001256fd Aiee: scheduling in interrupt 001256fd Aiee: scheduling in interrupt 001256fd Aiee: scheduling in interrupt 001256fd
I dug around and this is in sched.c file. Does this help anyone? If not, I'll provide my full report tomorrow.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu
| |