Re: Kernel BUG at slab.c:1930

Re: Kernel BUG at slab.c:1930

[Manfred Spraul]

Hi,

>The following OOPS occured this morning.  This is on a dual CPU machine, 
>there were two oopses, unfortunately the other scrolled off the screen 
>but the process was lockd (nfs related afaik).
>  
>
Unfortunately the first one is the important one :-(

>Here is the oops (written off and typed up), unfortunately I don't know 
>how to convert this to nicely readable symbols ...
>
>Kernel BUG at slab.c:1930
>
That's an oops caused by a consistency check while printing 
/proc/slabinfo. Probably a side effect of the first oops.

--
    Manfred

Re: Kernel BUG at slab.c:1930

[Jaco Kroon]

[-- Attachment #1: Type: text/plain, Size: 2780 bytes --]

Argh, just found this one in the logs:

May 19 09:58:18 fornax kernel BUG at slab.c:1930!
May 19 09:58:18 fornax invalid operand: 0000
May 19 09:58:18 fornax CPU:    0
May 19 09:58:18 fornax EIP:    0010:[<c01372a5>]    Not tainted
May 19 09:58:18 fornax EFLAGS: 00010002
May 19 09:58:18 fornax eax: c7d8b000   ebx: 00000000   ecx: 0000001e   
edx: c12c72b0
May 19 09:58:18 fornax esi: 00003ab6   edi: c12c72b0   ebp: c12c72b0   
esp: ca329f10
May 19 09:58:18 fornax ds: 0018   es: 0018   ss: 0018
May 19 09:58:18 fornax Process vmstat (pid: 27441, stackpage=ca329000)
May 19 09:58:18 fornax Stack: cb69a7e0 c02724f2 0000007c 0000003e 
000047ce 00000200 00000a42 00000a42
May 19 09:58:18 fornax 00000001 c0000000 000001f5 00000246 00001000 
00000000 000047ce 00000000
May 19 09:58:18 fornax cb69a7e0 c12c72b0 00000756 c015e8e3 cb69a7e0 
c12c72b0 ca329f74 cb69a7f8
May 19 09:58:18 fornax Call Trace:    [<c015e8e3>] [<c0140d27>] [<c010773f>]
May 19 09:58:18 fornax
May 19 09:58:18 fornax Code: 0f 0b 8a 07 bc 24 27 c0 ff 44 24 28 01 ce 
8b 00 39 e8 75 e7

but no trace of the other one, which was deffinately a lockd process 
(nfs related afaik).  Oh well, thanks for the help.  At least this 
confirms (for me at least) that there is a problem in the server side 
nfs code.  And now I know about ksymoops.

Jaco

Manfred Spraul wrote:

> Hi,
>
>> The following OOPS occured this morning.  This is on a dual CPU 
>> machine, there were two oopses, unfortunately the other scrolled off 
>> the screen but the process was lockd (nfs related afaik).
>>  
>>
> Unfortunately the first one is the important one :-(
>
>> Here is the oops (written off and typed up), unfortunately I don't 
>> know how to convert this to nicely readable symbols ...
>>
>> Kernel BUG at slab.c:1930
>>
> That's an oops caused by a consistency check while printing 
> /proc/slabinfo. Probably a side effect of the first oops.
>
> -- 
>    Manfred
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe 
> linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


-- 
As long as there are ill-defined goals, bizarre bugs, and unrealistic 
schedules, there will be Real Programmers willing to jump in and Solve 
The Problem, saving the documentation for later.
===========================================
This message and attachments are subject to a disclaimer. Please refer to www.it.up.ac.za/documentation/governance/disclaimer/ for full details.
Hierdie boodskap en aanhangsels is aan 'n vrywaringsklousule onderhewig. Volledige besonderhede is by www.it.up.ac.za/documentation/governance/disclaimer/ beskikbaar.
===========================================


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3174 bytes --]

Kernel BUG at slab.c:1930

[Jaco Kroon]

[-- Attachment #1: Type: text/plain, Size: 1642 bytes --]

Hello all

The following OOPS occured this morning.  This is on a dual CPU machine, 
there were two oopses, unfortunately the other scrolled off the screen 
but the process was lockd (nfs related afaik).

Here is the oops (written off and typed up), unfortunately I don't know 
how to convert this to nicely readable symbols ...

Kernel BUG at slab.c:1930
invalid operand: 0000
CPU: 0
EIP: 0010:[<c01372a5>]         Not Tainted
EFLAGS: 00010002
eax: c7d8b000     ebx: 00000000     ecx: 0000001e     edx: c12c72b0
esi: 00003ab6     edi: cf2c72b0     ebp: c12c72b0     esp: ca329f10
ds: 18      es: 18        ss: 18
Process vmstat (pid: 27441, stack page = ca329000)

Stack:  cbb9a7e0 c02724f2 0000007c 0000003e 000047ce 00000200 00000a42 
00000a42
           00000001 c0000000 000001f5 00000246 00001000 00000000 00047ce 
00000000
           cb69a7e0 c12c72b0 00000756 c015e8e3 cb69a7e0 c12c72b0 
c9329f74 cb69a7f8

Call Trace: [<c015e8e3>] [<c0140d27>] [<c01077377>]

Code: 0f 0b 8a 07 bc 24 27 c0 ff 44 24 28 01 ce 8b 00 39 e8 75 e7

$ uname -a
Linux fornax 2.4.24 #4 SMP Fri Jan 30 08:39:38 SAST 2004 i686 Pentium II 
(Deschutes) GenuineIntel GNU/Linux

Any other information that may be of use?

Jaco

-- 
How come we never talk anymore?
===========================================
This message and attachments are subject to a disclaimer. Please refer to www.it.up.ac.za/documentation/governance/disclaimer/ for full details.
Hierdie boodskap en aanhangsels is aan 'n vrywaringsklousule onderhewig. Volledige besonderhede is by www.it.up.ac.za/documentation/governance/disclaimer/ beskikbaar.
===========================================


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3174 bytes --]

Re: Kernel BUG at slab.c:1930

[Michael Buesch]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wednesday 19 May 2004 12:26, you wrote:
> Here is the oops (written off and typed up), unfortunately I don't know 
> how to convert this to nicely readable symbols ...

There's a tool called ksymoops to decode the symbols.
You can find it on kernel.org

- -- 
Regards Michael Buesch  [ http://www.tuxsoft.de.vu ]

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAq72wFGK1OIvVOP4RAgyVAJ42EI1AM6G3WY0SbbaPimc2BdGFBgCgsh/W
imxw2KsODnNqUS66P64QiPk=
=GBVq
-----END PGP SIGNATURE-----