lkml.org 
[lkml]   [1998]   [Jun]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectTrying to vfree nonexistent vm area

Well, the subject says almost all. I got the following (I think the
ext2_truncate is just debug info):

Jun 23 00:10:34 mylly kernel: ext2_truncate: inode 124663, retrying
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)


Nothing bad did happen, the system is still up and running. Are they
harmless? They last two look scary ... Hmmm, I think they're coming from
mm/vmalloc.c.

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.

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.

Taneli <vahakang@cs.helsinki.fi>




-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu

\
 
 \ /
  Last update: 2005-03-22 13:43    [from the cache]
©2003-2011 Jasper Spaans