Thats fine
> Jun 23 00:28:32 mylly kernel: Trying to vfree() nonexistent vm area
> (c6869000)
> Jun 23 00:28:32 mylly kernel: Trying to vfree() nonexistent vm area
> (c6869000)
Definitely bad
> harmless? They last two look scary ... Hmmm, I think they're coming from
> mm/vmalloc.c.
Something tried to free memory it forgot to allocate. Extremely bad in
fact.
> I didn't do anything special, first compiled wine and then tried to use
> it. With 96M I don't think it was swapping too much, but can't say for
> sure.
See if WINE is what trips it. Its the one oddity I can think of
> Kernel 2.1.106ac4 compiled with gcc-2.7.2.3. It has been up for almost two
> hours. UP kernel on an UP machine.
Can you mail me (privately) the full config for the box
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu