[rsbac] Kernel errors

[Kim Scholte]

Hi again,

Once again I encountered the error while running 'find ./ -name
"*nss*tar.gz"' as root.
For some strange reason I get error messages like the ones bellow. I've
connected a nullmodem cable on the server so I can monitor it from another
server, which is also the reason I can supply the messages :) (the computer
itself hangs).

Amon asked me to send a System.map, but since it's about 300kb, I uploaded
it to http://www.i-vision.be/System.map.
(what does a system.map do btw ? :)

The kernel itself is 2.4.18-rsbac-1.2.0-pre6 (downloaded from the /kernel
section on the rsbac page)

So, here's an example: (they keep on comming, with a growing call trace).

Code: fe af 15 08 08 00 00 00 08 00 00 00 00 00 00 00 11 00 00 00
 invalid operand: 0000
CPU:    0
EIP:    0010:[<cff1c4c4>]    Not tainted
EFLAGS: 00010286
eax: cff1e400   ebx: cff1c4c0   ecx: 00000000   edx: cf8bf0a4
esi: 00000000   edi: cf8bf09c   ebp: cf8bf0a4   esp: cf8beff8
ds: 0018   es: 0018   ss: 0018
Process find (pid: 508, stackpage=cf8bf000)
Stack: cf8bf0a4 c0184a07 cff1c4c0 cf8bf0a4 cf8bf154 cf8bf1ac cf8bf130
cf8bf110
       00000000 c0184ae6 cff1c4c0 00000000 cf8bf0a4 cf8bf09c c0192954
cff1c4c0
       cf8bf0a4 cf8bf09c cf8bf154 cf8bf1ac cf8bf130 40000000 00000000
c017fcc0
Call Trace: [<c0184a07>] [<c0184ae6>] [<c0192954>] [<c017fcc0>] [<c018030a>]
   [<c01924a3>] [<c018030a>] [<c018030a>] [<c01924a3>] [<c018030a>]
[<c0184a00>
   [<c019bcc1>] [<c010714a>] [<c018030a>] [<c019c134>] [<c010714a>]
[<c0193d82>
   [<c010714a>] [<c0107380>] [<c010af66>] [<c0107f8f>] [<c010a2e8>]
[<c01d8545>
   [<c01b88b2>] [<c01b89d3>] [<c01d5267>] [<c01d527b>] [<c01944b1>]
[<c010714a>
   [<c0107380>] [<c01144e6>] [<c010714a>] [<c0107380>] [<c0107380>]
[<c0107380>
   [<c010714a>] [<c010714f>] [<c01073ff>] [<c017f7a0>] [<c0184a07>]
[<c017fcc0>
   [<c018030a>] [<c01924a3>] [<c0106d4c>] [<c0184a07>] [<c0184ae6>]
[<c0192954>
   [<c017f7a0>] [<c0184a07>] [<c018030a>] [<c01924a3>] [<c018030a>]
[<c018030a>
   [<c019bcc1>] [<c010714a>] [<c017f7a0>] [<c0184a07>] [<c019c134>]
[<c010714a>
   [<c0193d82>] [<c010714a>] [<c0107380>] [<c010af66>] [<c0107f8f>]
[<c010a2e8>
   [<c01d8545>] [<c01b88b2>] [<c01b89d3>] [<c01d5267>] [<c01d527b>]
[<c01944b1>
   [<c010714a>] [<c0107380>] [<c01144e6>] [<c010714a>] [<c0107380>]
[<c0107380>
   [<c0107380>] [<c010714a>] [<c010714f>] [<c01073ff>] [<c01924a3>]
[<c018030a>
   [<c01924a3>] [<c0106d4c>] [<c0184a07>] [<c0184ae6>] [<c0192954>]
[<c01924a3>
   [<c018030a>] [<c017fcc0>] [<c018030a>] [<c01924a3>] [<c018030a>]
[<c019bcc1>
   [<c010714a>] [<c01e8150>] [<c01de963>] [<c019c134>] [<c010714a>]
[<c0193d82>
   [<c010714a>] [<c010ff50>] [<c01e6da2>] [<c01e8220>] [<c01de117>]
[<c01e723d>
   [<c01d5267>] [<c01d527b>] [<c01944b1>] [<c010714a>] [<c010ff50>]
[<c01144e6>
   [<c010714a>] [<c010ff50>] [<c010ff50>] [<c010ff50>] [<c010714a>]
[<c010714f>
   [<c01102a7>] [<c010ff50>] [<c01b89d3>] [<c0126bc5>] [<c012805b>]
[<c0128423>
   [<c011ddd1>] [<c0106d4c>] [<c01191e2>] [<c0119275>] [<c01145f5>]
[<c010714a>
   [<c010714f>] [<c01102a7>] [<c010ff50>] [<c013760d>] [<c012d7b4>]
[<c012d702>
   [<c0106d4c>] [<c012da63>] [<c0106c5b>]



Regards,
Kim

> ----- Original Message -----
> From: "Amon Ott" <ao@rsbac.org>
> To: <rsbac@rsbac.org>
> Sent: Monday, April 15, 2002 10:25 AM
> Subject: Re: [rsbac] Kernel errors
>
>
> > On Saturday, 13. April 2002 13:41, Kim Scholte wrote:
> > > Sorry to bother again,
> >
> > This list is meant for bothering. :)
> >
> > > but i've installed the linux-2.4.18+rsbac-1.2.0-pre6
> > > kernel but I'm getting the errors you see bellow this night. So I did
a
> > > "find / -name tmpwatch", which gave a lot of the errors noted bellow
and
> > > finally crashed my computer.
> > >
> > > So, anyone know what's wrong? And what I can do to get it working
again?
> >
> > > Nightly errors:
> > > Oops: 0002
> > > CPU:    0
> > > EIP:    0010:[<c01402de>]    Not tainted
> > > Call Trace: [<c012ce09>] [<c012da7c>] [<c0106c5b>]
> > >
> > > Code: ff 0b 0f 94 c0 84 c0 0f 84 05 01 00 00 8d 43 18 89 c6 39 73
> > >  <1>Unable to handle kernel NULL pointer dereference at virtual
address
> > > 00000001
> > >  printing eip:
> > > c011924a
> > > *pde = 00000000
> >
> > Could you please send me the corresponding System.map to find the
> functions
> > involved?
> >
> > NULL dereferences are quite serious, but usually pretty easy to find and
> fix.
> >
> > Amon.
> > --
> > http://www.rsbac.org