> On Sat, 7 Feb 1998, Michael Collins wrote:
>
> > Couldn't get a free page ...
> > eth0: Couldn't allocate a sk_buff of size 114
> > cpp: output pipe has been closed
> > gcc: Internal complier error: program cc1 got fatal signal 11
>
> In most cases, signal 11 indicates a hardware problem. By any chance, did
> you overclock your CPU, or use over-agressive timing settings for your
> RAMs?
No - notice the Couldn't get a free page message? It was definately an
out of memory situation. 2.0.33/34pre2 still don't do too well under
certain conditions: eg at work a 386 with 8 megs and everything but swap
over NFS will still deadlock in kswapd when running gcc.
-ben
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu