Re: kernel BUG at mm/slab.c:610

2007-03-14 Thread Chris Rankin
Marco Berizzi wrote:
> Here is:
>
> Mar 14 03:42:25 Mimosa kernel: [ cut here ]
> Mar 14 03:42:25 Mimosa kernel: kernel BUG at mm/slab.c:610!
> Mar 14 03:42:25 Mimosa kernel: invalid opcode:  [#1]
> Mar 14 03:42:25 Mimosa kernel: Modules linked in: sch_sfq sch_htb
cls_fw
> nf_nat_pptp nf_nat_proto_gre nf_conntrack_pptp nf_conntrack_proto_gre
> nf_nat_ftp nf_conntrack_ftp 3c59x mii
> Mar 14 03:42:25 Mimosa kernel: CPU: 0
> Mar 14 03:42:25 Mimosa kernel: EIP: 0060:[] Not
tainted
> VLI
> Mar 14 03:42:25 Mimosa kernel: EFLAGS: 00010046 (2.6.20 #1)
> Mar 14 03:42:25 Mimosa kernel: EIP is at free_block+0xd9/0xf0
> Mar 14 03:42:25 Mimosa kernel: eax: 0008 ebx: c100 ecx:
> c0e7d4e0 edx: c101cfa0
> Mar 14 03:42:25 Mimosa kernel: esi: c121 edi: c1176560 ebp:
>  esp: c119bef0
> Mar 14 03:42:25 Mimosa kernel: ds: 007b es: 007b ss: 0068
> Mar 14 03:42:25 Mimosa kernel: Process events/0 (pid: 3, ti=c119a000
> task=c118f030 task.ti=c119a000)
> Mar 14 03:42:25 Mimosa kernel: Stack: c1213a10 161c9ed5 c1210010
> c1210010 c121 161c9ed5 c1176560 c014d201
> Mar 14 03:42:25 Mimosa kernel:  c1180420 c1176560
> c1180d60 c014d220 c014d26b  
> Mar 14 03:42:25 Mimosa kernel: c03b7ae0 c03b7ae0 0282
> c0123d37  c118f13c 007b 508b
> Mar 14 03:42:25 Mimosa kernel: Call Trace:
> Mar 14 03:42:25 Mimosa kernel: [] drain_array+0x91/0xb0
> Mar 14 03:42:25 Mimosa kernel: [] cache_reap+0x0/0xf0
> Mar 14 03:42:25 Mimosa kernel: [] cache_reap+0x4b/0xf0
> Mar 14 03:42:25 Mimosa kernel: [] run_workqueue+0x67/0x130
> Mar 14 03:42:25 Mimosa kernel: [] worker_thread+0x13a/0x170
> Mar 14 03:42:25 Mimosa kernel: []
> default_wake_function+0x0/0x10
> Mar 14 03:42:25 Mimosa kernel: []
__wake_up_common+0x37/0x70
> Mar 14 03:42:25 Mimosa kernel: []
> default_wake_function+0x0/0x10
> Mar 14 03:42:25 Mimosa kernel: [] worker_thread+0x0/0x170
> Mar 14 03:42:25 Mimosa kernel: [] kthread+0xb6/0xc0
> Mar 14 03:42:25 Mimosa kernel: [] kthread+0x0/0xc0
> Mar 14 03:42:25 Mimosa kernel: []
> kernel_thread_helper+0x7/0x14
> Mar 14 03:42:25 Mimosa kernel: ===
> Mar 14 03:42:25 Mimosa kernel: Code: ff 83 c4 0c 5b 5e 5f 5d c3 8b 57
20
> 29 d0 89 da 89 46 18 89 f8 e8 78 f1 ff ff eb da 89 33 8b 46 04 89 5e
04
> 89 18 89 43 04 eb cb <0f> 0b 90 8d 74 26 00 eb fe 8b 52 0c e9 57 ff ff
> ff 8d b6 00 00
> Mar 14 03:42:25 Mimosa kernel: EIP: [] free_block+0xd9/0xf0
> SS:ESP 0068:c119bef0

> Only to tell you, that on the console linux was printing
> this message:

> atkbd.c: Spurious ACK on isa0060/serio0. Some program might be trying
> access hardware directly.

That sounds familiar... I had similar trouble with 2.6.20.1 (running UP on a 
200 MHz Pentium MMX
machine) when I unloaded the nf_conntrack_h323 kernel module. The messages 
continued until I
rebooted, although I never saw an oops. I am currently avoiding the problem by 
*not* unloading any
netfilter modules.

Cheers,
Chris




___ 
All new Yahoo! Mail "The new Interface is stunning in its simplicity and ease 
of use." - PC Magazine
http://uk.docs.yahoo.com/nowyoucan.html
-
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/


Re: kernel BUG at mm/slab.c:610

2007-03-14 Thread Pekka Enberg

On 3/14/07, Marco Berizzi <[EMAIL PROTECTED]> wrote:

Only to tell you, that on the console linux was printing
this message:

atkbd.c: Spurious ACK on isa0060/serio0. Some program might be trying
access hardware directly.


Probably unrelated. CONFIG_SLAB_DEBUG should tell us what's corrupting the slab.
-
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/


Re: kernel BUG at mm/slab.c:610

2007-03-14 Thread Marco Berizzi
Marco Berizzi wrote:

> Pekka Enberg wrote:
>
> Hi Pekka,
>
> > So, can you please repost the original oops?
>
> Here is:
>
> Mar 14 03:42:25 Mimosa kernel: [ cut here ]
> Mar 14 03:42:25 Mimosa kernel: kernel BUG at mm/slab.c:610!
> Mar 14 03:42:25 Mimosa kernel: invalid opcode:  [#1]
> Mar 14 03:42:25 Mimosa kernel: Modules linked in: sch_sfq sch_htb
cls_fw
> nf_nat_pptp nf_nat_proto_gre nf_conntrack_pptp nf_conntrack_proto_gre
> nf_nat_ftp nf_conntrack_ftp 3c59x mii
> Mar 14 03:42:25 Mimosa kernel: CPU:0
> Mar 14 03:42:25 Mimosa kernel: EIP:0060:[]Not
tainted
> VLI
> Mar 14 03:42:25 Mimosa kernel: EFLAGS: 00010046   (2.6.20 #1)
> Mar 14 03:42:25 Mimosa kernel: EIP is at free_block+0xd9/0xf0
> Mar 14 03:42:25 Mimosa kernel: eax: 0008   ebx: c100   ecx:
> c0e7d4e0   edx: c101cfa0
> Mar 14 03:42:25 Mimosa kernel: esi: c121   edi: c1176560   ebp:
>    esp: c119bef0
> Mar 14 03:42:25 Mimosa kernel: ds: 007b   es: 007b   ss: 0068
> Mar 14 03:42:25 Mimosa kernel: Process events/0 (pid: 3, ti=c119a000
> task=c118f030 task.ti=c119a000)
> Mar 14 03:42:25 Mimosa kernel: Stack: c1213a10 161c9ed5 c1210010
> c1210010 c121 161c9ed5 c1176560 c014d201
> Mar 14 03:42:25 Mimosa kernel: c1180420 c1176560
> c1180d60 c014d220 c014d26b  
> Mar 14 03:42:25 Mimosa kernel:c03b7ae0 c03b7ae0 0282
> c0123d37  c118f13c 007b 508b
> Mar 14 03:42:25 Mimosa kernel: Call Trace:
> Mar 14 03:42:25 Mimosa kernel:  [] drain_array+0x91/0xb0
> Mar 14 03:42:25 Mimosa kernel:  [] cache_reap+0x0/0xf0
> Mar 14 03:42:25 Mimosa kernel:  [] cache_reap+0x4b/0xf0
> Mar 14 03:42:25 Mimosa kernel:  [] run_workqueue+0x67/0x130
> Mar 14 03:42:25 Mimosa kernel:  [] worker_thread+0x13a/0x170
> Mar 14 03:42:25 Mimosa kernel:  []
> default_wake_function+0x0/0x10
> Mar 14 03:42:25 Mimosa kernel:  []
__wake_up_common+0x37/0x70
> Mar 14 03:42:25 Mimosa kernel:  []
> default_wake_function+0x0/0x10
> Mar 14 03:42:25 Mimosa kernel:  [] worker_thread+0x0/0x170
> Mar 14 03:42:25 Mimosa kernel:  [] kthread+0xb6/0xc0
> Mar 14 03:42:25 Mimosa kernel:  [] kthread+0x0/0xc0
> Mar 14 03:42:25 Mimosa kernel:  []
> kernel_thread_helper+0x7/0x14
> Mar 14 03:42:25 Mimosa kernel:  ===
> Mar 14 03:42:25 Mimosa kernel: Code: ff 83 c4 0c 5b 5e 5f 5d c3 8b 57
20
> 29 d0 89 da 89 46 18 89 f8 e8 78 f1 ff ff eb da 89 33 8b 46 04 89 5e
04
> 89 18 89 43 04 eb cb <0f> 0b 90 8d 74 26 00 eb fe 8b 52 0c e9 57 ff ff
> ff 8d b6 00 00
> Mar 14 03:42:25 Mimosa kernel: EIP: [] free_block+0xd9/0xf0
> SS:ESP 0068:c119bef0

Only to tell you, that on the console linux was printing
this message:

atkbd.c: Spurious ACK on isa0060/serio0. Some program might be trying
access hardware directly.


-
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/


Re: kernel BUG at mm/slab.c:610

2007-03-14 Thread Marco Berizzi
Pekka Enberg wrote:

Hi Pekka,

> So, can you please repost the original oops?

Here is:

Mar 14 03:42:25 Mimosa kernel: [ cut here ]
Mar 14 03:42:25 Mimosa kernel: kernel BUG at mm/slab.c:610!
Mar 14 03:42:25 Mimosa kernel: invalid opcode:  [#1]
Mar 14 03:42:25 Mimosa kernel: Modules linked in: sch_sfq sch_htb cls_fw
nf_nat_pptp nf_nat_proto_gre nf_conntrack_pptp nf_conntrack_proto_gre
nf_nat_ftp nf_conntrack_ftp 3c59x mii
Mar 14 03:42:25 Mimosa kernel: CPU:0
Mar 14 03:42:25 Mimosa kernel: EIP:0060:[]Not tainted
VLI
Mar 14 03:42:25 Mimosa kernel: EFLAGS: 00010046   (2.6.20 #1)
Mar 14 03:42:25 Mimosa kernel: EIP is at free_block+0xd9/0xf0
Mar 14 03:42:25 Mimosa kernel: eax: 0008   ebx: c100   ecx:
c0e7d4e0   edx: c101cfa0
Mar 14 03:42:25 Mimosa kernel: esi: c121   edi: c1176560   ebp:
   esp: c119bef0
Mar 14 03:42:25 Mimosa kernel: ds: 007b   es: 007b   ss: 0068
Mar 14 03:42:25 Mimosa kernel: Process events/0 (pid: 3, ti=c119a000
task=c118f030 task.ti=c119a000)
Mar 14 03:42:25 Mimosa kernel: Stack: c1213a10 161c9ed5 c1210010
c1210010 c121 161c9ed5 c1176560 c014d201
Mar 14 03:42:25 Mimosa kernel: c1180420 c1176560
c1180d60 c014d220 c014d26b  
Mar 14 03:42:25 Mimosa kernel:c03b7ae0 c03b7ae0 0282
c0123d37  c118f13c 007b 508b
Mar 14 03:42:25 Mimosa kernel: Call Trace:
Mar 14 03:42:25 Mimosa kernel:  [] drain_array+0x91/0xb0
Mar 14 03:42:25 Mimosa kernel:  [] cache_reap+0x0/0xf0
Mar 14 03:42:25 Mimosa kernel:  [] cache_reap+0x4b/0xf0
Mar 14 03:42:25 Mimosa kernel:  [] run_workqueue+0x67/0x130
Mar 14 03:42:25 Mimosa kernel:  [] worker_thread+0x13a/0x170
Mar 14 03:42:25 Mimosa kernel:  []
default_wake_function+0x0/0x10
Mar 14 03:42:25 Mimosa kernel:  [] __wake_up_common+0x37/0x70
Mar 14 03:42:25 Mimosa kernel:  []
default_wake_function+0x0/0x10
Mar 14 03:42:25 Mimosa kernel:  [] worker_thread+0x0/0x170
Mar 14 03:42:25 Mimosa kernel:  [] kthread+0xb6/0xc0
Mar 14 03:42:25 Mimosa kernel:  [] kthread+0x0/0xc0
Mar 14 03:42:25 Mimosa kernel:  []
kernel_thread_helper+0x7/0x14
Mar 14 03:42:25 Mimosa kernel:  ===
Mar 14 03:42:25 Mimosa kernel: Code: ff 83 c4 0c 5b 5e 5f 5d c3 8b 57 20
29 d0 89 da 89 46 18 89 f8 e8 78 f1 ff ff eb da 89 33 8b 46 04 89 5e 04
89 18 89 43 04 eb cb <0f> 0b 90 8d 74 26 00 eb fe 8b 52 0c e9 57 ff ff
ff 8d b6 00 00
Mar 14 03:42:25 Mimosa kernel: EIP: [] free_block+0xd9/0xf0
SS:ESP 0068:c119bef0

Here is from another machine:

Mar 14 08:53:47 Gemini kernel: [ cut here ]
Mar 14 08:53:47 Gemini kernel: kernel BUG at mm/slab.c:610!
Mar 14 08:53:47 Gemini kernel: invalid opcode:  [#1]
Mar 14 08:53:47 Gemini kernel: Modules linked in: nf_nat_pptp
nf_nat_proto_gre nf_conntrack_pptp nf_conntrack_proto_gre nf_nat_ftp
nf_conntrack_ftp 3c59x mii
Mar 14 08:53:47 Gemini kernel: CPU:0
Mar 14 08:53:47 Gemini kernel: EIP:0060:[]Not tainted
VLI
Mar 14 08:53:47 Gemini kernel: EFLAGS: 00010046   (2.6.20 #1)
Mar 14 08:53:47 Gemini kernel: EIP is at free_block+0xd6/0xf0
Mar 14 08:53:47 Gemini kernel: eax: 8000   ebx: c100   ecx:
c9ae64e0   edx: c1135cc0
Mar 14 08:53:47 Gemini kernel: esi: c121   edi: c1176560   ebp:
   esp: c119bef0
Mar 14 08:53:47 Gemini kernel: ds: 007b   es: 007b   ss: 0068
Mar 14 08:53:47 Gemini kernel: Process events/0 (pid: 3, ti=c119a000
task=c118f030 task.ti=c119a000)
Mar 14 08:53:47 Gemini kernel: Stack: c1179a10 110b04c7 c1210010
c1210010 c121 110b04c7 c1176560 c014d5f1
Mar 14 08:53:47 Gemini kernel: c1180420 c1176560
c1180d60 c014d610 c014d65b  
Mar 14 08:53:47 Gemini kernel:c03b7a60 c03b7a60 0282
c0124157  c118f13c 0076 5e32
Mar 14 08:53:47 Gemini kernel: Call Trace:
Mar 14 08:53:47 Gemini kernel:  [] drain_array+0x91/0xb0
Mar 14 08:53:47 Gemini kernel:  [] cache_reap+0x0/0xf0
Mar 14 08:53:47 Gemini kernel:  [] cache_reap+0x4b/0xf0
Mar 14 08:53:47 Gemini kernel:  [] run_workqueue+0x67/0x130
Mar 14 08:53:47 Gemini kernel:  [] worker_thread+0x13a/0x170
Mar 14 08:53:47 Gemini kernel:  []
default_wake_function+0x0/0x10
Mar 14 08:53:47 Gemini kernel:  [] __wake_up_common+0x37/0x70
Mar 14 08:53:47 Gemini kernel:  []
default_wake_function+0x0/0x10
Mar 14 08:53:47 Gemini kernel:  [] worker_thread+0x0/0x170
Mar 14 08:53:47 Gemini kernel:  [] kthread+0xb6/0xc0
Mar 14 08:53:47 Gemini kernel:  [] kthread+0x0/0xc0
Mar 14 08:53:47 Gemini kernel:  []
kernel_thread_helper+0x7/0x10
Mar 14 08:53:47 Gemini kernel:  ===
Mar 14 08:53:47 Gemini kernel: Code: ff 83 c4 0c 5b 5e 5f 5d c3 8b 57 20
29 d0 89 da 89 46 18 89 f8 e8 7b f1 ff ff eb da 89 33 8b 46 04 89 5e 04
89 18 89 43 04 eb cb <0f> 0b 90 8d b4 26 00 00 00 00 eb fe 8b 52 0c e9
57 ff ff ff 8d
Mar 14 08:53:47 Gemini kernel: EIP: [] free_block+0xd6/0xf0
SS:ESP 0068:c119bef0

> Also, please enable
> CONFIG_DEBUG_SLAB  and try to reproduce. Thanks.

I'm 

Re: kernel BUG at mm/slab.c:610

2007-03-14 Thread Pekka Enberg

Hi Marco,

On 3/14/07, Marco Berizzi <[EMAIL PROTECTED]> wrote:

Hello everybody. Sorry for posting to this list, but I'm pretty lost.


Don't worry, this is the proper mailing list for bug reports.

On 3/14/07, Marco Berizzi <[EMAIL PROTECTED]> wrote:

I don't think this is related to buggy hardware because it is happening
on 3 different boxes with the same hardware config.


No, looks like someone is feeding a bad pointer to slab. The debug
check is relatively new and in previous kernels the problem would
might have gone unnoticed causing silent corruption of the slab.

On 3/14/07, Marco Berizzi <[EMAIL PROTECTED]> wrote:

ksymoops 2.4.10 on i686 2.6.20.  Options used



From Documentation/oops-tracing.txt:


"NOTE: ksymoops is useless on 2.6.  Please use the Oops in its original format
(from dmesg, etc).  Ignore any references in this or other docs to "decoding
the Oops" or "running it through ksymoops".  If you post an Oops from 2.6 that
has been run through ksymoops, people will just tell you to repost it."

So, can you please repost the original oops? Also, please enable
CONFIG_DEBUG_SLAB  and try to reproduce. Thanks.
-
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/


kernel BUG at mm/slab.c:610

2007-03-14 Thread Marco Berizzi
Hello everybody. Sorry for posting to this list,
but I'm pretty lost.
I'm experimenting this kernel panic on 3 different
slackware linux boxes. The harware is the same, and
also the .config with vanilla 2.6.20
I don't think this is related to buggy hardware
because it is happening on 3 different boxes with
the same hardware config.
Unfortunately the bug isn't reproducible but it is
happening at least once a week.
May anoybody point me the step to try to spot this
bug?

TIA

ksymoops 2.4.10 on i686 2.6.20.  Options used
  -V (default)
  -k /proc/ksyms (default)
  -l /proc/modules (default)
  -o /lib/modules/2.6.20/ (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.

Error (regular_file): read_ksyms stat /proc/ksyms failed
ksymoops: No such file or directory
No modules in ksyms, skipping objects
No ksyms, skipping lsmod
Mar 14 03:42:25 Mimosa kernel: kernel BUG at mm/slab.c:610!
Mar 14 03:42:25 Mimosa kernel: CPU:0
Mar 14 03:42:25 Mimosa kernel: EIP:0060:[]
Not tainted VLI
Using defaults from ksymoops -t elf32-i386 -a i386
Mar 14 03:42:25 Mimosa kernel: EFLAGS: 00010046   (2.6.20 #1)
Mar 14 03:42:25 Mimosa kernel: eax: 0008   ebx: c100
   ecx: c0e7d4e0   edx: c101cfa0
Mar 14 03:42:25 Mimosa kernel: esi: c121   edi: c1176560
   ebp:    esp: c119bef0
Mar 14 03:42:25 Mimosa kernel: ds: 007b   es: 007b   ss: 0068
Mar 14 03:42:25 Mimosa kernel: Stack: c1213a10 161c9ed5
c1210010 c1210010 c121 161c9ed5 c1176560 c014d201
Mar 14 03:42:25 Mimosa kernel: c1180420
c1176560 c1180d60 c014d220 c014d26b  
Mar 14 03:42:25 Mimosa kernel:c03b7ae0 c03b7ae0
0282 c0123d37  c118f13c 007b 508b
Mar 14 03:42:25 Mimosa kernel: Call Trace:
Mar 14 03:42:25 Mimosa kernel:  []
drain_array+0x91/0xb0
Mar 14 03:42:25 Mimosa kernel:  [] cache_reap+0x0/0xf0
Mar 14 03:42:25 Mimosa kernel:  []
cache_reap+0x4b/0xf0
Mar 14 03:42:25 Mimosa kernel:  []
run_workqueue+0x67/0x130
Mar 14 03:42:25 Mimosa kernel:  []
worker_thread+0x13a/0x170
Mar 14 03:42:25 Mimosa kernel:  []
default_wake_function+0x0/0x10
Mar 14 03:42:25 Mimosa kernel:  []
__wake_up_common+0x37/0x70
Mar 14 03:42:25 Mimosa kernel:  []
default_wake_function+0x0/0x10
Mar 14 03:42:25 Mimosa kernel:  []
worker_thread+0x0/0x170
Mar 14 03:42:25 Mimosa kernel:  [] kthread+0xb6/0xc0
Mar 14 03:42:25 Mimosa kernel:  [] kthread+0x0/0xc0
Mar 14 03:42:25 Mimosa kernel:  []
kernel_thread_helper+0x7/0x14
Mar 14 03:42:25 Mimosa kernel: Code: ff 83 c4 0c 5b 5e 5f 5d
c3 8b 57 20 29 d0 89 da 89 46 18 89 f8 e8 78 f1 ff ff eb da
89 33 8b 46 04 89 5e 04 89 18 89 43 04 eb cb <0f> 0b 90 8d
74 26 00 eb fe 8b 52 0c e9 57 ff ff ff 8d b6 00 00


 >>EIP; c014ca99<=

 >>ebx; c100 
 >>ecx; c0e7d4e0 
 >>edx; c101cfa0 
 >>esi; c121 
 >>edi; c1176560 
 >>esp; c119bef0 

Trace; c014d201 
Trace; c014d220 
Trace; c014d26b 
Trace; c0123d37 
Trace; c0123f3a 
Trace; c01123e0 
Trace; c0112427 <__wake_up_common+37/70>
Trace; c01123e0 
Trace; c0123e00 
Trace; c01271a6 
Trace; c01270f0 
Trace; c01036a3 

This architecture has variable length instructions, decoding
before eip
is unreliable, take these instructions with a pinch of salt.

Code;  c014ca6e 
 <_EIP>:
Code;  c014ca6e 
0:   ff 83 c4 0c 5b 5e incl   0x5e5b0cc4(%ebx)
Code;  c014ca74 
6:   5fpop%edi
Code;  c014ca75 
7:   5dpop%ebp
Code;  c014ca76 
8:   c3ret
Code;  c014ca77 
9:   8b 57 20  mov0x20(%edi),%edx
Code;  c014ca7a 
c:   29 d0 sub%edx,%eax
Code;  c014ca7c 
e:   89 da mov%ebx,%edx
Code;  c014ca7e 
   10:   89 46 18  mov%eax,0x18(%esi)
Code;  c014ca81 
   13:   89 f8 mov%edi,%eax
Code;  c014ca83 
   15:   e8 78 f1 ff ffcall   f192
<_EIP+0xf192>
Code;  c014ca88 
   1a:   eb da jmpfff6
<_EIP+0xfff6>
Code;  c014ca8a 
   1c:   89 33 mov%esi,(%ebx)
Code;  c014ca8c 
   1e:   8b 46 04  mov0x4(%esi),%eax
Code;  c014ca8f 
   21:   89 5e 04  mov%ebx,0x4(%esi)
Code;  c014ca92 
   24:   89 18 mov%ebx,(%eax)
Code;  c014ca94 
   26:   89 43 04  mov%eax,0x4(%ebx)
Code;  c014ca97 
   29:   eb cb jmpfff6
<_EIP+0xfff6>

This decode from eip onwards shou

kernel BUG at mm/slab.c:610

2007-03-14 Thread Marco Berizzi
Hello everybody. Sorry for posting to this list,
but I'm pretty lost.
I'm experimenting this kernel panic on 3 different
slackware linux boxes. The harware is the same, and
also the .config with vanilla 2.6.20
I don't think this is related to buggy hardware
because it is happening on 3 different boxes with
the same hardware config.
Unfortunately the bug isn't reproducible but it is
happening at least once a week.
May anoybody point me the step to try to spot this
bug?

TIA

ksymoops 2.4.10 on i686 2.6.20.  Options used
  -V (default)
  -k /proc/ksyms (default)
  -l /proc/modules (default)
  -o /lib/modules/2.6.20/ (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.

Error (regular_file): read_ksyms stat /proc/ksyms failed
ksymoops: No such file or directory
No modules in ksyms, skipping objects
No ksyms, skipping lsmod
Mar 14 03:42:25 Mimosa kernel: kernel BUG at mm/slab.c:610!
Mar 14 03:42:25 Mimosa kernel: CPU:0
Mar 14 03:42:25 Mimosa kernel: EIP:0060:[c014ca99]
Not tainted VLI
Using defaults from ksymoops -t elf32-i386 -a i386
Mar 14 03:42:25 Mimosa kernel: EFLAGS: 00010046   (2.6.20 #1)
Mar 14 03:42:25 Mimosa kernel: eax: 0008   ebx: c100
   ecx: c0e7d4e0   edx: c101cfa0
Mar 14 03:42:25 Mimosa kernel: esi: c121   edi: c1176560
   ebp:    esp: c119bef0
Mar 14 03:42:25 Mimosa kernel: ds: 007b   es: 007b   ss: 0068
Mar 14 03:42:25 Mimosa kernel: Stack: c1213a10 161c9ed5
c1210010 c1210010 c121 161c9ed5 c1176560 c014d201
Mar 14 03:42:25 Mimosa kernel: c1180420
c1176560 c1180d60 c014d220 c014d26b  
Mar 14 03:42:25 Mimosa kernel:c03b7ae0 c03b7ae0
0282 c0123d37  c118f13c 007b 508b
Mar 14 03:42:25 Mimosa kernel: Call Trace:
Mar 14 03:42:25 Mimosa kernel:  [c014d201]
drain_array+0x91/0xb0
Mar 14 03:42:25 Mimosa kernel:  [c014d220] cache_reap+0x0/0xf0
Mar 14 03:42:25 Mimosa kernel:  [c014d26b]
cache_reap+0x4b/0xf0
Mar 14 03:42:25 Mimosa kernel:  [c0123d37]
run_workqueue+0x67/0x130
Mar 14 03:42:25 Mimosa kernel:  [c0123f3a]
worker_thread+0x13a/0x170
Mar 14 03:42:25 Mimosa kernel:  [c01123e0]
default_wake_function+0x0/0x10
Mar 14 03:42:25 Mimosa kernel:  [c0112427]
__wake_up_common+0x37/0x70
Mar 14 03:42:25 Mimosa kernel:  [c01123e0]
default_wake_function+0x0/0x10
Mar 14 03:42:25 Mimosa kernel:  [c0123e00]
worker_thread+0x0/0x170
Mar 14 03:42:25 Mimosa kernel:  [c01271a6] kthread+0xb6/0xc0
Mar 14 03:42:25 Mimosa kernel:  [c01270f0] kthread+0x0/0xc0
Mar 14 03:42:25 Mimosa kernel:  [c01036a3]
kernel_thread_helper+0x7/0x14
Mar 14 03:42:25 Mimosa kernel: Code: ff 83 c4 0c 5b 5e 5f 5d
c3 8b 57 20 29 d0 89 da 89 46 18 89 f8 e8 78 f1 ff ff eb da
89 33 8b 46 04 89 5e 04 89 18 89 43 04 eb cb 0f 0b 90 8d
74 26 00 eb fe 8b 52 0c e9 57 ff ff ff 8d b6 00 00


 EIP; c014ca99 free_block+d9/f0   =

 ebx; c100 pg0+c3b000/3fc39400
 ecx; c0e7d4e0 pg0+ab84e0/3fc39400
 edx; c101cfa0 pg0+c57fa0/3fc39400
 esi; c121 pg0+e4b000/3fc39400
 edi; c1176560 pg0+db1560/3fc39400
 esp; c119bef0 pg0+dd6ef0/3fc39400

Trace; c014d201 drain_array+91/b0
Trace; c014d220 cache_reap+0/f0
Trace; c014d26b cache_reap+4b/f0
Trace; c0123d37 run_workqueue+67/130
Trace; c0123f3a worker_thread+13a/170
Trace; c01123e0 default_wake_function+0/10
Trace; c0112427 __wake_up_common+37/70
Trace; c01123e0 default_wake_function+0/10
Trace; c0123e00 worker_thread+0/170
Trace; c01271a6 kthread+b6/c0
Trace; c01270f0 kthread+0/c0
Trace; c01036a3 kernel_thread_helper+7/14

This architecture has variable length instructions, decoding
before eip
is unreliable, take these instructions with a pinch of salt.

Code;  c014ca6e free_block+ae/f0
 _EIP:
Code;  c014ca6e free_block+ae/f0
0:   ff 83 c4 0c 5b 5e incl   0x5e5b0cc4(%ebx)
Code;  c014ca74 free_block+b4/f0
6:   5fpop%edi
Code;  c014ca75 free_block+b5/f0
7:   5dpop%ebp
Code;  c014ca76 free_block+b6/f0
8:   c3ret
Code;  c014ca77 free_block+b7/f0
9:   8b 57 20  mov0x20(%edi),%edx
Code;  c014ca7a free_block+ba/f0
c:   29 d0 sub%edx,%eax
Code;  c014ca7c free_block+bc/f0
e:   89 da mov%ebx,%edx
Code;  c014ca7e free_block+be/f0
   10:   89 46 18  mov%eax,0x18(%esi)
Code;  c014ca81 free_block+c1/f0
   13:   89 f8 mov%edi,%eax
Code;  c014ca83 free_block+c3/f0
   15:   e8 78 f1 ff ffcall   f192
_EIP+0xf192
Code;  c014ca88 free_block+c8/f0
   1a:   eb da

Re: kernel BUG at mm/slab.c:610

2007-03-14 Thread Pekka Enberg

Hi Marco,

On 3/14/07, Marco Berizzi [EMAIL PROTECTED] wrote:

Hello everybody. Sorry for posting to this list, but I'm pretty lost.


Don't worry, this is the proper mailing list for bug reports.

On 3/14/07, Marco Berizzi [EMAIL PROTECTED] wrote:

I don't think this is related to buggy hardware because it is happening
on 3 different boxes with the same hardware config.


No, looks like someone is feeding a bad pointer to slab. The debug
check is relatively new and in previous kernels the problem would
might have gone unnoticed causing silent corruption of the slab.

On 3/14/07, Marco Berizzi [EMAIL PROTECTED] wrote:

ksymoops 2.4.10 on i686 2.6.20.  Options used



From Documentation/oops-tracing.txt:


NOTE: ksymoops is useless on 2.6.  Please use the Oops in its original format
(from dmesg, etc).  Ignore any references in this or other docs to decoding
the Oops or running it through ksymoops.  If you post an Oops from 2.6 that
has been run through ksymoops, people will just tell you to repost it.

So, can you please repost the original oops? Also, please enable
CONFIG_DEBUG_SLAB  and try to reproduce. Thanks.
-
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/


Re: kernel BUG at mm/slab.c:610

2007-03-14 Thread Marco Berizzi
Pekka Enberg wrote:

Hi Pekka,

 So, can you please repost the original oops?

Here is:

Mar 14 03:42:25 Mimosa kernel: [ cut here ]
Mar 14 03:42:25 Mimosa kernel: kernel BUG at mm/slab.c:610!
Mar 14 03:42:25 Mimosa kernel: invalid opcode:  [#1]
Mar 14 03:42:25 Mimosa kernel: Modules linked in: sch_sfq sch_htb cls_fw
nf_nat_pptp nf_nat_proto_gre nf_conntrack_pptp nf_conntrack_proto_gre
nf_nat_ftp nf_conntrack_ftp 3c59x mii
Mar 14 03:42:25 Mimosa kernel: CPU:0
Mar 14 03:42:25 Mimosa kernel: EIP:0060:[c014ca99]Not tainted
VLI
Mar 14 03:42:25 Mimosa kernel: EFLAGS: 00010046   (2.6.20 #1)
Mar 14 03:42:25 Mimosa kernel: EIP is at free_block+0xd9/0xf0
Mar 14 03:42:25 Mimosa kernel: eax: 0008   ebx: c100   ecx:
c0e7d4e0   edx: c101cfa0
Mar 14 03:42:25 Mimosa kernel: esi: c121   edi: c1176560   ebp:
   esp: c119bef0
Mar 14 03:42:25 Mimosa kernel: ds: 007b   es: 007b   ss: 0068
Mar 14 03:42:25 Mimosa kernel: Process events/0 (pid: 3, ti=c119a000
task=c118f030 task.ti=c119a000)
Mar 14 03:42:25 Mimosa kernel: Stack: c1213a10 161c9ed5 c1210010
c1210010 c121 161c9ed5 c1176560 c014d201
Mar 14 03:42:25 Mimosa kernel: c1180420 c1176560
c1180d60 c014d220 c014d26b  
Mar 14 03:42:25 Mimosa kernel:c03b7ae0 c03b7ae0 0282
c0123d37  c118f13c 007b 508b
Mar 14 03:42:25 Mimosa kernel: Call Trace:
Mar 14 03:42:25 Mimosa kernel:  [c014d201] drain_array+0x91/0xb0
Mar 14 03:42:25 Mimosa kernel:  [c014d220] cache_reap+0x0/0xf0
Mar 14 03:42:25 Mimosa kernel:  [c014d26b] cache_reap+0x4b/0xf0
Mar 14 03:42:25 Mimosa kernel:  [c0123d37] run_workqueue+0x67/0x130
Mar 14 03:42:25 Mimosa kernel:  [c0123f3a] worker_thread+0x13a/0x170
Mar 14 03:42:25 Mimosa kernel:  [c01123e0]
default_wake_function+0x0/0x10
Mar 14 03:42:25 Mimosa kernel:  [c0112427] __wake_up_common+0x37/0x70
Mar 14 03:42:25 Mimosa kernel:  [c01123e0]
default_wake_function+0x0/0x10
Mar 14 03:42:25 Mimosa kernel:  [c0123e00] worker_thread+0x0/0x170
Mar 14 03:42:25 Mimosa kernel:  [c01271a6] kthread+0xb6/0xc0
Mar 14 03:42:25 Mimosa kernel:  [c01270f0] kthread+0x0/0xc0
Mar 14 03:42:25 Mimosa kernel:  [c01036a3]
kernel_thread_helper+0x7/0x14
Mar 14 03:42:25 Mimosa kernel:  ===
Mar 14 03:42:25 Mimosa kernel: Code: ff 83 c4 0c 5b 5e 5f 5d c3 8b 57 20
29 d0 89 da 89 46 18 89 f8 e8 78 f1 ff ff eb da 89 33 8b 46 04 89 5e 04
89 18 89 43 04 eb cb 0f 0b 90 8d 74 26 00 eb fe 8b 52 0c e9 57 ff ff
ff 8d b6 00 00
Mar 14 03:42:25 Mimosa kernel: EIP: [c014ca99] free_block+0xd9/0xf0
SS:ESP 0068:c119bef0

Here is from another machine:

Mar 14 08:53:47 Gemini kernel: [ cut here ]
Mar 14 08:53:47 Gemini kernel: kernel BUG at mm/slab.c:610!
Mar 14 08:53:47 Gemini kernel: invalid opcode:  [#1]
Mar 14 08:53:47 Gemini kernel: Modules linked in: nf_nat_pptp
nf_nat_proto_gre nf_conntrack_pptp nf_conntrack_proto_gre nf_nat_ftp
nf_conntrack_ftp 3c59x mii
Mar 14 08:53:47 Gemini kernel: CPU:0
Mar 14 08:53:47 Gemini kernel: EIP:0060:[c014ce86]Not tainted
VLI
Mar 14 08:53:47 Gemini kernel: EFLAGS: 00010046   (2.6.20 #1)
Mar 14 08:53:47 Gemini kernel: EIP is at free_block+0xd6/0xf0
Mar 14 08:53:47 Gemini kernel: eax: 8000   ebx: c100   ecx:
c9ae64e0   edx: c1135cc0
Mar 14 08:53:47 Gemini kernel: esi: c121   edi: c1176560   ebp:
   esp: c119bef0
Mar 14 08:53:47 Gemini kernel: ds: 007b   es: 007b   ss: 0068
Mar 14 08:53:47 Gemini kernel: Process events/0 (pid: 3, ti=c119a000
task=c118f030 task.ti=c119a000)
Mar 14 08:53:47 Gemini kernel: Stack: c1179a10 110b04c7 c1210010
c1210010 c121 110b04c7 c1176560 c014d5f1
Mar 14 08:53:47 Gemini kernel: c1180420 c1176560
c1180d60 c014d610 c014d65b  
Mar 14 08:53:47 Gemini kernel:c03b7a60 c03b7a60 0282
c0124157  c118f13c 0076 5e32
Mar 14 08:53:47 Gemini kernel: Call Trace:
Mar 14 08:53:47 Gemini kernel:  [c014d5f1] drain_array+0x91/0xb0
Mar 14 08:53:47 Gemini kernel:  [c014d610] cache_reap+0x0/0xf0
Mar 14 08:53:47 Gemini kernel:  [c014d65b] cache_reap+0x4b/0xf0
Mar 14 08:53:47 Gemini kernel:  [c0124157] run_workqueue+0x67/0x130
Mar 14 08:53:47 Gemini kernel:  [c012435a] worker_thread+0x13a/0x170
Mar 14 08:53:47 Gemini kernel:  [c0112810]
default_wake_function+0x0/0x10
Mar 14 08:53:47 Gemini kernel:  [c0112857] __wake_up_common+0x37/0x70
Mar 14 08:53:47 Gemini kernel:  [c0112810]
default_wake_function+0x0/0x10
Mar 14 08:53:47 Gemini kernel:  [c0124220] worker_thread+0x0/0x170
Mar 14 08:53:47 Gemini kernel:  [c01275c6] kthread+0xb6/0xc0
Mar 14 08:53:47 Gemini kernel:  [c0127510] kthread+0x0/0xc0
Mar 14 08:53:47 Gemini kernel:  [c01036c7]
kernel_thread_helper+0x7/0x10
Mar 14 08:53:47 Gemini kernel:  ===
Mar 14 08:53:47 Gemini kernel: Code: ff 83 c4 0c 5b 5e 5f 5d c3 8b 57 20
29 d0 89 da 89 46 18 89 f8 e8 7b f1 ff ff eb da 89 33 8b 46 04 89 5e 04
89 18 89 43 04 eb cb 0f 0b 90 8d b4 26 00 00 00 00 eb

Re: kernel BUG at mm/slab.c:610

2007-03-14 Thread Marco Berizzi
Marco Berizzi wrote:

 Pekka Enberg wrote:

 Hi Pekka,

  So, can you please repost the original oops?

 Here is:

 Mar 14 03:42:25 Mimosa kernel: [ cut here ]
 Mar 14 03:42:25 Mimosa kernel: kernel BUG at mm/slab.c:610!
 Mar 14 03:42:25 Mimosa kernel: invalid opcode:  [#1]
 Mar 14 03:42:25 Mimosa kernel: Modules linked in: sch_sfq sch_htb
cls_fw
 nf_nat_pptp nf_nat_proto_gre nf_conntrack_pptp nf_conntrack_proto_gre
 nf_nat_ftp nf_conntrack_ftp 3c59x mii
 Mar 14 03:42:25 Mimosa kernel: CPU:0
 Mar 14 03:42:25 Mimosa kernel: EIP:0060:[c014ca99]Not
tainted
 VLI
 Mar 14 03:42:25 Mimosa kernel: EFLAGS: 00010046   (2.6.20 #1)
 Mar 14 03:42:25 Mimosa kernel: EIP is at free_block+0xd9/0xf0
 Mar 14 03:42:25 Mimosa kernel: eax: 0008   ebx: c100   ecx:
 c0e7d4e0   edx: c101cfa0
 Mar 14 03:42:25 Mimosa kernel: esi: c121   edi: c1176560   ebp:
    esp: c119bef0
 Mar 14 03:42:25 Mimosa kernel: ds: 007b   es: 007b   ss: 0068
 Mar 14 03:42:25 Mimosa kernel: Process events/0 (pid: 3, ti=c119a000
 task=c118f030 task.ti=c119a000)
 Mar 14 03:42:25 Mimosa kernel: Stack: c1213a10 161c9ed5 c1210010
 c1210010 c121 161c9ed5 c1176560 c014d201
 Mar 14 03:42:25 Mimosa kernel: c1180420 c1176560
 c1180d60 c014d220 c014d26b  
 Mar 14 03:42:25 Mimosa kernel:c03b7ae0 c03b7ae0 0282
 c0123d37  c118f13c 007b 508b
 Mar 14 03:42:25 Mimosa kernel: Call Trace:
 Mar 14 03:42:25 Mimosa kernel:  [c014d201] drain_array+0x91/0xb0
 Mar 14 03:42:25 Mimosa kernel:  [c014d220] cache_reap+0x0/0xf0
 Mar 14 03:42:25 Mimosa kernel:  [c014d26b] cache_reap+0x4b/0xf0
 Mar 14 03:42:25 Mimosa kernel:  [c0123d37] run_workqueue+0x67/0x130
 Mar 14 03:42:25 Mimosa kernel:  [c0123f3a] worker_thread+0x13a/0x170
 Mar 14 03:42:25 Mimosa kernel:  [c01123e0]
 default_wake_function+0x0/0x10
 Mar 14 03:42:25 Mimosa kernel:  [c0112427]
__wake_up_common+0x37/0x70
 Mar 14 03:42:25 Mimosa kernel:  [c01123e0]
 default_wake_function+0x0/0x10
 Mar 14 03:42:25 Mimosa kernel:  [c0123e00] worker_thread+0x0/0x170
 Mar 14 03:42:25 Mimosa kernel:  [c01271a6] kthread+0xb6/0xc0
 Mar 14 03:42:25 Mimosa kernel:  [c01270f0] kthread+0x0/0xc0
 Mar 14 03:42:25 Mimosa kernel:  [c01036a3]
 kernel_thread_helper+0x7/0x14
 Mar 14 03:42:25 Mimosa kernel:  ===
 Mar 14 03:42:25 Mimosa kernel: Code: ff 83 c4 0c 5b 5e 5f 5d c3 8b 57
20
 29 d0 89 da 89 46 18 89 f8 e8 78 f1 ff ff eb da 89 33 8b 46 04 89 5e
04
 89 18 89 43 04 eb cb 0f 0b 90 8d 74 26 00 eb fe 8b 52 0c e9 57 ff ff
 ff 8d b6 00 00
 Mar 14 03:42:25 Mimosa kernel: EIP: [c014ca99] free_block+0xd9/0xf0
 SS:ESP 0068:c119bef0

Only to tell you, that on the console linux was printing
this message:

atkbd.c: Spurious ACK on isa0060/serio0. Some program might be trying
access hardware directly.


-
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/


Re: kernel BUG at mm/slab.c:610

2007-03-14 Thread Pekka Enberg

On 3/14/07, Marco Berizzi [EMAIL PROTECTED] wrote:

Only to tell you, that on the console linux was printing
this message:

atkbd.c: Spurious ACK on isa0060/serio0. Some program might be trying
access hardware directly.


Probably unrelated. CONFIG_SLAB_DEBUG should tell us what's corrupting the slab.
-
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/


Re: kernel BUG at mm/slab.c:610

2007-03-14 Thread Chris Rankin
Marco Berizzi wrote:
 Here is:

 Mar 14 03:42:25 Mimosa kernel: [ cut here ]
 Mar 14 03:42:25 Mimosa kernel: kernel BUG at mm/slab.c:610!
 Mar 14 03:42:25 Mimosa kernel: invalid opcode:  [#1]
 Mar 14 03:42:25 Mimosa kernel: Modules linked in: sch_sfq sch_htb
cls_fw
 nf_nat_pptp nf_nat_proto_gre nf_conntrack_pptp nf_conntrack_proto_gre
 nf_nat_ftp nf_conntrack_ftp 3c59x mii
 Mar 14 03:42:25 Mimosa kernel: CPU: 0
 Mar 14 03:42:25 Mimosa kernel: EIP: 0060:[c014ca99] Not
tainted
 VLI
 Mar 14 03:42:25 Mimosa kernel: EFLAGS: 00010046 (2.6.20 #1)
 Mar 14 03:42:25 Mimosa kernel: EIP is at free_block+0xd9/0xf0
 Mar 14 03:42:25 Mimosa kernel: eax: 0008 ebx: c100 ecx:
 c0e7d4e0 edx: c101cfa0
 Mar 14 03:42:25 Mimosa kernel: esi: c121 edi: c1176560 ebp:
  esp: c119bef0
 Mar 14 03:42:25 Mimosa kernel: ds: 007b es: 007b ss: 0068
 Mar 14 03:42:25 Mimosa kernel: Process events/0 (pid: 3, ti=c119a000
 task=c118f030 task.ti=c119a000)
 Mar 14 03:42:25 Mimosa kernel: Stack: c1213a10 161c9ed5 c1210010
 c1210010 c121 161c9ed5 c1176560 c014d201
 Mar 14 03:42:25 Mimosa kernel:  c1180420 c1176560
 c1180d60 c014d220 c014d26b  
 Mar 14 03:42:25 Mimosa kernel: c03b7ae0 c03b7ae0 0282
 c0123d37  c118f13c 007b 508b
 Mar 14 03:42:25 Mimosa kernel: Call Trace:
 Mar 14 03:42:25 Mimosa kernel: [c014d201] drain_array+0x91/0xb0
 Mar 14 03:42:25 Mimosa kernel: [c014d220] cache_reap+0x0/0xf0
 Mar 14 03:42:25 Mimosa kernel: [c014d26b] cache_reap+0x4b/0xf0
 Mar 14 03:42:25 Mimosa kernel: [c0123d37] run_workqueue+0x67/0x130
 Mar 14 03:42:25 Mimosa kernel: [c0123f3a] worker_thread+0x13a/0x170
 Mar 14 03:42:25 Mimosa kernel: [c01123e0]
 default_wake_function+0x0/0x10
 Mar 14 03:42:25 Mimosa kernel: [c0112427]
__wake_up_common+0x37/0x70
 Mar 14 03:42:25 Mimosa kernel: [c01123e0]
 default_wake_function+0x0/0x10
 Mar 14 03:42:25 Mimosa kernel: [c0123e00] worker_thread+0x0/0x170
 Mar 14 03:42:25 Mimosa kernel: [c01271a6] kthread+0xb6/0xc0
 Mar 14 03:42:25 Mimosa kernel: [c01270f0] kthread+0x0/0xc0
 Mar 14 03:42:25 Mimosa kernel: [c01036a3]
 kernel_thread_helper+0x7/0x14
 Mar 14 03:42:25 Mimosa kernel: ===
 Mar 14 03:42:25 Mimosa kernel: Code: ff 83 c4 0c 5b 5e 5f 5d c3 8b 57
20
 29 d0 89 da 89 46 18 89 f8 e8 78 f1 ff ff eb da 89 33 8b 46 04 89 5e
04
 89 18 89 43 04 eb cb 0f 0b 90 8d 74 26 00 eb fe 8b 52 0c e9 57 ff ff
 ff 8d b6 00 00
 Mar 14 03:42:25 Mimosa kernel: EIP: [c014ca99] free_block+0xd9/0xf0
 SS:ESP 0068:c119bef0

 Only to tell you, that on the console linux was printing
 this message:

 atkbd.c: Spurious ACK on isa0060/serio0. Some program might be trying
 access hardware directly.

That sounds familiar... I had similar trouble with 2.6.20.1 (running UP on a 
200 MHz Pentium MMX
machine) when I unloaded the nf_conntrack_h323 kernel module. The messages 
continued until I
rebooted, although I never saw an oops. I am currently avoiding the problem by 
*not* unloading any
netfilter modules.

Cheers,
Chris




___ 
All new Yahoo! Mail The new Interface is stunning in its simplicity and ease 
of use. - PC Magazine
http://uk.docs.yahoo.com/nowyoucan.html
-
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/