Re: 2.0.33 lock - ram

Alan Cox (
Tue, 19 May 1998 01:45:12 +0100 (BST)

> A Pentium 166 UP server at my Univeristy is running 2.0.33 + 2 ip_frag
> patch + my vmalloc patch, and is locking every few hours. This seems
> started happening after adding 64Mbyte of ram to the machine (now has
> 128Mbyte).

That sets alarm bells ringing . "After adding 64Mbyte of ram". Dont suppose
you can see if its stable with just the new 64Mbyte alone, or with a different
64Mb second simm (assuming you happen to have one around).

> I used my backport of the print_eip patch to understand where the lock
> happens and it happens always in the same place.
> The kernel is started by a do_page_fault() that then run a do_no_page()
> and continue with ret_from_sys_call. Then the kernel lock after the
> RESTORE_ALL before signal_return: in entry.S.

And it hangs at that point or loops on something ?


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to