[Linux-cluster] repeatable assertion failure, what does it mean?

[Adam Cassar]

occurs on mount on a new fs

kernel BUG at /usr/src/GFS/cluster/gfs-kernel/src/dlm/lock.c:397!
invalid operand: 0000 [#1]
SMP 
Modules linked in: lock_dlm dlm cman gfs lock_harness 8250 serial_core
dm_mod
CPU:    1
EIP:    0060:[<f8989b8a>]    Not tainted
EFLAGS: 00010282   (2.6.8.1) 
EIP is at do_dlm_lock+0x1d6/0x1ea [lock_dlm]
eax: 00000001   ebx: ffffffea   ecx: c03478b4   edx: 000059e8
esi: c1af2600   edi: f7c7ac80   ebp: 00000000   esp: f6c23e2c
ds: 007b   es: 007b   ss: 0068
Process lock_dlm (pid: 23452, threadinfo=f6c22000 task=f6f8b290)
Stack: f898da49 f4882e60 00000010 00000000 00000000 ffffffea 00000003
00000005 
       0000005d 00000000 00000000 20202020 30312020 20202020 20202020
20202020 
       30202020 f6c20018 00000001 c1af2600 00000005 c1af2600 00000001
f8989c5e 
Call Trace:
 [<f8989c5e>] lm_dlm_lock+0x6e/0x7f [lock_dlm]
 [<f8989cbb>] lm_dlm_lock_sync+0x4c/0x62 [lock_dlm]
 [<f8988181>] id_test_and_set+0xf8/0x21f [lock_dlm]
 [<f89884e9>] claim_jid+0x3b/0x110 [lock_dlm]
 [<f8988a71>] process_start+0x372/0x4e1 [lock_dlm]
 [<f898d49b>] dlm_async+0x1fc/0x315 [lock_dlm]
 [<c01157c8>] default_wake_function+0x0/0x12
 [<c01157c8>] default_wake_function+0x0/0x12
 [<f898d29f>] dlm_async+0x0/0x315 [lock_dlm]
 [<c0102161>] kernel_thread_helper+0x5/0xb
Code: 0f 0b 8d 01 80 df 98 f8 c7 04 24 40 e0 98 f8 e8 5a f2 78 c7kernel
BUG at /usr/src/GFS/cluster/gfs-kernel/src/dlm/lock.c:397!
invalid operand: 0000 [#1]
CPU:    1
EIP:    0060:[<f8989b8a>]    Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010282   (2.6.8.1) 
eax: 00000001   ebx: ffffffea   ecx: c03478b4   edx: 000059e8
esi: c1af2600   edi: f7c7ac80   ebp: 00000000   esp: f6c23e2c
ds: 007b   es: 007b   ss: 0068
Stack: f898da49 f4882e60 00000010 00000000 00000000 ffffffea 00000003
00000005 
       0000005d 00000000 00000000 20202020 30312020 20202020 20202020
20202020 
       30202020 f6c20018 00000001 c1af2600 00000005 c1af2600 00000001
f8989c5e 
 [<f8989c5e>] lm_dlm_lock+0x6e/0x7f [lock_dlm]
 [<f8989cbb>] lm_dlm_lock_sync+0x4c/0x62 [lock_dlm]
 [<f8988181>] id_test_and_set+0xf8/0x21f [lock_dlm]
 [<f89884e9>] claim_jid+0x3b/0x110 [lock_dlm]
 [<f8988a71>] process_start+0x372/0x4e1 [lock_dlm]
 [<f898d49b>] dlm_async+0x1fc/0x315 [lock_dlm]
 [<c01157c8>] default_wake_function+0x0/0x12
 [<c01157c8>] default_wake_function+0x0/0x12
 [<f898d29f>] dlm_async+0x0/0x315 [lock_dlm]
 [<c0102161>] kernel_thread_helper+0x5/0xb

Code: 0f 0b 8d 01 80 df 98 f8 c7 04 24 40 e0 98 f8 e8 5a f2 78 c7


>>EIP; f8989b8a <pg0+38533b8a/3fba8000>   <=====

>>ebx; ffffffea <__kernel_rt_sigreturn+1baa/????>
>>ecx; c03478b4 <console_sem+0/14>
>>edx; 000059e8 Before first symbol
>>esi; c1af2600 <pg0+169c600/3fba8000>
>>edi; f7c7ac80 <pg0+37824c80/3fba8000>
>>esp; f6c23e2c <pg0+367cde2c/3fba8000>

Code;  f8989b8a <pg0+38533b8a/3fba8000>
00000000 <_EIP>:
Code;  f8989b8a <pg0+38533b8a/3fba8000>   <=====
   0:   0f 0b                     ud2a      <=====
Code;  f8989b8c <pg0+38533b8c/3fba8000>
   2:   8d 01                     lea    (%ecx),%eax
Code;  f8989b8e <pg0+38533b8e/3fba8000>
   4:   80 df 98                  sbb    $0x98,%bh
Code;  f8989b91 <pg0+38533b91/3fba8000>
   7:   f8                        clc    
Code;  f8989b92 <pg0+38533b92/3fba8000>
   8:   c7 04 24 40 e0 98 f8      movl   $0xf898e040,(%esp,1)
Code;  f8989b99 <pg0+38533b99/3fba8000>
   f:   e8 5a f2 78 c7            call   c778f26e <_EIP+0xc778f26e>
c0118df8 <panic+0/119>