[lkml]   [2001]   [Jan]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRE: Oops with 4GB memory setting in 2.4.0 stable
Ok, now were making progress. I did as you said and have attached (really!)
the new parsed output. Now we have some useful information (I hope). I still
got lots of warnings on symbols (which I have edited out of the parsed file
for the sake of briefness). What's the next step?


> -----Original Message-----
> From:
> []On Behalf Of Marcelo Tosatti
> Sent: Tuesday, January 16, 2001 7:09 AM
> To: Rainer Mager
> Cc:
> Subject: RE: Oops with 4GB memory setting in 2.4.0 stable
> >>EIP; f889e044 <END_OF_CODE+385bfe34/????> <=====
> Trace; f889d966 <END_OF_CODE+385bf756/????>
> Trace; c0140c10 <vfs_readdir+90/ec>
> Trace; c0140e7c <filldir+0/d8>
> Trace; c0140f9e <sys_getdents+4a/98>
> Trace; c0140e7c <filldir+0/d8>
> It seems the oops is happening in a module's function.
> You have to make ksymoops parse the oops output against a which
> has all modules symbols. Load each module by hand with the insmod -m
> option ("insmod -m module.o") and _append_ the outputs to
> After that you can run ksymoops against this new
[unhandled content-type:application/octet-stream]
 \ /
  Last update: 2005-03-22 13:18    [W:0.088 / U:3.300 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site