BUG at slab.c:1244! 2.4.5-ac13

2001-06-15 Thread Lars Gaarden

I tend to get these after a few days uptime. This one locked X
hard, ping and ssh over net etc still worked ok.
Pretty standard x86 PC hardware.


kernel BUG at slab.c:1244!
invalid operand: 
CPU:0
EIP:0010:[]
EFLAGS: 00213082
eax: 001b   ebx: cfffc768   ecx: c0217700   edx: 0002906e
esi: c8a5b000   edi: c8a5b9aa   ebp: 00012800   esp: ca2e7df8
ds: 0018   es: 0018   ss: 0018
Process X (pid: 11139, stackpage=ca2e7000)
Stack: c01e5225 04dc ceac71b4 c0273fa0 0007 0002 c8a5b000 
1000
0020 00203246 c01a4e86 0a1c 0007 c58a97a0  
09e0
c01a4671 09e0 0007 ce146ad4 09e0 c01d34e0 c58a94b4 
ca2e6000
Call Trace: [] [] [] [] []
[] [] [] [] [] 
[]
[] [] []

Code: 0f 0b 83 c4 08 8b 6b 10 f7 c5 00 04 00 00 74 53 b8 a5 c2 0f


ksymoops 0.7c on i686 2.4.5-ac13.  Options used
  -V (default)
  -k /proc/ksyms (default)
  -l /proc/modules (default)
  -o /lib/modules/2.4.5-ac13/ (default)
  -m /usr/src/linux/System.map (default)

Warning: You did not tell me where to find symbol information.  I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc.  ksymoops -h explains the options.

invalid operand: 
CPU:0
EIP:0010:[]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00213082
eax: 001b   ebx: cfffc768   ecx: c0217700   edx: 0002906e
esi: c8a5b000   edi: c8a5b9aa   ebp: 00012800   esp: ca2e7df8
ds: 0018   es: 0018   ss: 0018
Process X (pid: 11139, stackpage=ca2e7000)
Stack: c01e5225 04dc ceac71b4 c0273fa0 0007 0002 c8a5b000 
1000
0020 00203246 c01a4e86 0a1c 0007 c58a97a0  
09e0
c01a4671 09e0 0007 ce146ad4 09e0 c01d34e0 c58a94b4 
ca2e6000
Call Trace: [] [] [] [] []
[] [] [] [] [] 
[]
[] [] []
Code: 0f 0b 83 c4 08 8b 6b 10 f7 c5 00 04 00 00 74 53 b8 a5 c2 0f

 >>EIP; c012842f<=
Trace; c01a4e86 
Trace; c01a4671 
Trace; c01d34e0 
Trace; c01d35df 
Trace; c01d34e0 
Trace; c01a233d 
Trace; c01d34e0 
Trace; c01a265c 
Trace; c01a26de 
Trace; c0130c93 
Trace; c0117e65 
Trace; c0130df9 
Trace; c0106b17 
Trace; c010002b 
Code;  c012842f 
 <_EIP>:
Code;  c012842f<=
0:   0f 0b ud2a  <=
Code;  c0128431 
2:   83 c4 08  add$0x8,%esp
Code;  c0128434 
5:   8b 6b 10  mov0x10(%ebx),%ebp
Code;  c0128437 
8:   f7 c5 00 04 00 00 test   $0x400,%ebp
Code;  c012843d 
e:   74 53 je 63 <_EIP+0x63> c0128492 

Code;  c012843f 
   10:   b8 a5 c2 0f 00mov$0xfc2a5,%eax


1 warning issued.  Results may not be reliable.--

-- 
LarsG

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



BUG at slab.c:1244! 2.4.5-ac13

2001-06-15 Thread Lars Gaarden

I tend to get these after a few days uptime. This one locked X
hard, ping and ssh over net etc still worked ok.
Pretty standard x86 PC hardware.


kernel BUG at slab.c:1244!
invalid operand: 
CPU:0
EIP:0010:[c012842f]
EFLAGS: 00213082
eax: 001b   ebx: cfffc768   ecx: c0217700   edx: 0002906e
esi: c8a5b000   edi: c8a5b9aa   ebp: 00012800   esp: ca2e7df8
ds: 0018   es: 0018   ss: 0018
Process X (pid: 11139, stackpage=ca2e7000)
Stack: c01e5225 04dc ceac71b4 c0273fa0 0007 0002 c8a5b000 
1000
0020 00203246 c01a4e86 0a1c 0007 c58a97a0  
09e0
c01a4671 09e0 0007 ce146ad4 09e0 c01d34e0 c58a94b4 
ca2e6000
Call Trace: [c01a4e86] [c01a4671] [c01d34e0] [c01d35df] [c01d34e0]
[c01a233d] [c01d34e0] [c01a265c] [c01a26de] [c0130c93] 
[c0117e65]
[c0130df9] [c0106b17] [c010002b]

Code: 0f 0b 83 c4 08 8b 6b 10 f7 c5 00 04 00 00 74 53 b8 a5 c2 0f


ksymoops 0.7c on i686 2.4.5-ac13.  Options used
  -V (default)
  -k /proc/ksyms (default)
  -l /proc/modules (default)
  -o /lib/modules/2.4.5-ac13/ (default)
  -m /usr/src/linux/System.map (default)

Warning: You did not tell me where to find symbol information.  I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc.  ksymoops -h explains the options.

invalid operand: 
CPU:0
EIP:0010:[c012842f]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00213082
eax: 001b   ebx: cfffc768   ecx: c0217700   edx: 0002906e
esi: c8a5b000   edi: c8a5b9aa   ebp: 00012800   esp: ca2e7df8
ds: 0018   es: 0018   ss: 0018
Process X (pid: 11139, stackpage=ca2e7000)
Stack: c01e5225 04dc ceac71b4 c0273fa0 0007 0002 c8a5b000 
1000
0020 00203246 c01a4e86 0a1c 0007 c58a97a0  
09e0
c01a4671 09e0 0007 ce146ad4 09e0 c01d34e0 c58a94b4 
ca2e6000
Call Trace: [c01a4e86] [c01a4671] [c01d34e0] [c01d35df] [c01d34e0]
[c01a233d] [c01d34e0] [c01a265c] [c01a26de] [c0130c93] 
[c0117e65]
[c0130df9] [c0106b17] [c010002b]
Code: 0f 0b 83 c4 08 8b 6b 10 f7 c5 00 04 00 00 74 53 b8 a5 c2 0f

 EIP; c012842f kmalloc+12f/1d8   =
Trace; c01a4e86 alloc_skb+de/190
Trace; c01a4671 sock_alloc_send_skb+71/108
Trace; c01d34e0 unix_stream_sendmsg+0/2e0
Trace; c01d35df unix_stream_sendmsg+ff/2e0
Trace; c01d34e0 unix_stream_sendmsg+0/2e0
Trace; c01a233d sock_sendmsg+81/a4
Trace; c01d34e0 unix_stream_sendmsg+0/2e0
Trace; c01a265c sock_readv_writev+8c/98
Trace; c01a26de sock_writev+36/40
Trace; c0130c93 do_readv_writev+183/254
Trace; c0117e65 sys_gettimeofday+1d/94
Trace; c0130df9 sys_writev+41/54
Trace; c0106b17 system_call+33/38
Trace; c010002b startup_32+2b/a5
Code;  c012842f kmalloc+12f/1d8
 _EIP:
Code;  c012842f kmalloc+12f/1d8   =
0:   0f 0b ud2a  =
Code;  c0128431 kmalloc+131/1d8
2:   83 c4 08  add$0x8,%esp
Code;  c0128434 kmalloc+134/1d8
5:   8b 6b 10  mov0x10(%ebx),%ebp
Code;  c0128437 kmalloc+137/1d8
8:   f7 c5 00 04 00 00 test   $0x400,%ebp
Code;  c012843d kmalloc+13d/1d8
e:   74 53 je 63 _EIP+0x63 c0128492 
kmalloc+192/1d8
Code;  c012843f kmalloc+13f/1d8
   10:   b8 a5 c2 0f 00mov$0xfc2a5,%eax


1 warning issued.  Results may not be reliable.--

-- 
LarsG

-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/