Ext3 users - May 2001 - oops ext3 in journal_write_metadata_buffer

Hi,
just had an oops while spool uucp mails via uuxqt->postfix->procmail to
multiple mailboxes on an UDMA IDE drive on my Laptop. All filesystems 
are ext3 and i am running 2.2.19 + ext3 + ide udma patches.

When rebooting the system hang - After another reboot everything went
smooth.

invalid operand: 0000
CPU:    0
EIP:    0010:[<c014ca15>]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010292
eax: 0000001d   ebx: 00000000   ecx: 00000004   edx: cfa02000
esi: c5b6b820   edi: c9a3ab60   ebp: 00000000   esp: cfa51e1c
ds: 0018   es: 0018   ss: 0018
Process kjournald (pid: 75, process nr: 10, stackpage=cfa51000)
Stack: 00000132 c014ce0c cfa655a0 c5b6b820 c9a3ab60 cfa51fac cfa655a0 c5b6b820
       00000000 00000000 cfa655d4 cfa655a0 cfa51fac c015006a c9a3ab60 c5b6b820
       cfa51fa8 000006c6 cce77940 c10d9f20 cccb1000 cccb1080 cccb1780 cccb1800
Call Trace: [<c014ce0c>] [<c015006a>] [<c010b389>]
[<c010b0c3>] [<c011918d>] [<c0111aa6>] [<c014c7d8>]
       [<c014c7f4>] [<c014c6bc>] [<c014c6a8>]
[<c0108c2f>] [<c0108c38>]
Code: 0f 0b 83 c4 10 89 f6 8b 4c 24 34 8b 41 18 a8 02 75 2d 83 c4
>>EIP; c014ca15 <journal_write_metadata_buffer+4d/1d8>  
<====Trace; c014ce0c <journal_next_log_block+64/a0>
Trace; c015006a <journal_commit_transaction+572/ed8>
Trace; c010b389 <handle_IRQ_event+3d/78>
Trace; c010b0c3 <do_8259A_IRQ+8f/9c>
Trace; c011918d <do_bottom_half+51/6c>
Trace; c0111aa6 <schedule+146/27c>
Trace; c014c7d8 <kjournald+11c/1cc>
Trace; c014c7f4 <kjournald+138/1cc>
Trace; c014c6bc <kjournald+0/1cc>
Trace; c014c6a8 <commit_timeout+0/10>
Trace; c0108c2f <kernel_thread+1f/38>
Trace; c0108c38 <kernel_thread+28/38>
Code;  c014ca15 <journal_write_metadata_buffer+4d/1d8>
00000000 <_EIP>:
Code;  c014ca15 <journal_write_metadata_buffer+4d/1d8>   <====   0:  
0f 0b                     ud2a      <====Code;  c014ca17
<journal_write_metadata_buffer+4f/1d8>
   2:   83 c4 10                  add    $0x10,%esp
Code;  c014ca1a <journal_write_metadata_buffer+52/1d8>
   5:   89 f6                     mov    %esi,%esi
Code;  c014ca1c <journal_write_metadata_buffer+54/1d8>
   7:   8b 4c 24 34               mov    0x34(%esp,1),%ecx
Code;  c014ca20 <journal_write_metadata_buffer+58/1d8>
   b:   8b 41 18                  mov    0x18(%ecx),%eax
Code;  c014ca23 <journal_write_metadata_buffer+5b/1d8>
   e:   a8 02                     test   $0x2,%al
Code;  c014ca25 <journal_write_metadata_buffer+5d/1d8>
  10:   75 2d                     jne    3f <_EIP+0x3f> c014ca54
<journal_write_metadata_buffer+8c/1d8>
Code;  c014ca27 <journal_write_metadata_buffer+5f/1d8>
  12:   83 c4 00                  add    $0x0,%esp


Flo
-- 
Florian Lohoff                  flo@rfc822.org             +49-5201-669912
     Why is it called "common sense" when nobody seems to have any?

Hi,

On Thu, May 31, 2001 at 06:56:19PM +0200, Florian Lohoff wrote:
> just had an oops while spool uucp mails via uuxqt->postfix->procmail
to
> multiple mailboxes on an UDMA IDE drive on my Laptop. All filesystems 
> are ext3 and i am running 2.2.19 + ext3 + ide udma patches.
ext3-0.0.6b?
> When rebooting the system hang - After another reboot everything went
> smooth.
> 
> invalid operand: 0000
> CPU:    0
> EIP:    0010:[<c014ca15>]
That's a panic message by the looks of things: the "ud2a"
undefined
instruction sequence is used by the kernel's BUG() macro, and ext3
uses that to stop things if it detects an error in one of its assert
tests.  There would have been an ext3 log message just before the
posted oops: could you recover that and let me know what actually went
wrong here?

If there was anything else in the log before this, that might help
too.

Thanks,
 Stephen