linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avantika Mathur <mathur@linux.vnet.ibm.com>
To: Girish Shilamkar <girish@clusterfs.com>
Cc: linux-ext4@vger.kernel.org
Subject: jbd2_journal_commit_transaction oops
Date: Thu, 30 Aug 2007 11:16:31 -0700	[thread overview]
Message-ID: <46D7097F.4020501@linux.vnet.ibm.com> (raw)

Hi Girish,

When running fsstress on an x86 machine, I hit the kernel oops below.  The ext4-patch-queue is being tested including the journal checksum patches
I have mounted with -o delalloc,mballoc,data=writeback,journal_checksum

I did not get a chance to look in detail; but it looks like a journal issue.  Do you know what the issue might be?


BUG: unable to handle kernel NULL pointer dereference at virtual address 00000000
 printing eip:
c118ba5d
*pdpt = 000000002560a001
*pde = 0000000000000000
Oops: 0000 [#1]
SMP 
Modules linked in:
CPU:    1
EIP:    0060:[<c118ba5d>]    Not tainted VLI
EFLAGS: 00010257   (2.6.23-rc4-autokern1 #1)
EIP is at crc32_be+0x3d/0x9c
eax: 7e78a276   ebx: 76a2787e   ecx: 00000400   edx: 00000000
esi: 00000000   edi: 00000000   ebp: f56e5200   esp: e61f9e90
ds: 007b   es: 007b   fs: 00d8  gs: 0000  ss: 0068
Process kjournald2 (pid: 5388, ti=e61f8000 task=e3efc000 task.ti=e61f8000)
Stack: ef5fffc0 00000016 c10c762d 0000055e 00000000 00000000 00001000 00000000 
       f50e3e80 7e78a276 00000008 00000000 00000544 eb46aab4 eb46aabc 00000155 
       f585f800 e1e1c968 00000000 eb059428 0000055e 00000000 00000000 e3efc000 
Call Trace:
 [<c10c762d>] jbd2_journal_commit_transaction+0x92a/0x128d
 [<c1029e51>] autoremove_wake_function+0x0/0x33
 [<c1029e51>] autoremove_wake_function+0x0/0x33
 [<c10214f4>] try_to_del_timer_sync+0x42/0x48
 [<c10ca4fd>] kjournald2+0x130/0x307
 [<c1029e51>] autoremove_wake_function+0x0/0x33
 [<c129171c>] __sched_text_start+0x364/0x3ff
 [<c1029e51>] autoremove_wake_function+0x0/0x33
 [<c10ca3cd>] kjournald2+0x0/0x307
 [<c1029a27>] kthread+0x34/0x55
 [<c10299f3>] kthread+0x0/0x55
 [<c1003173>] kernel_thread_helper+0x7/0x10
 =======================
Code: 42 30 d8 0f b6 c0 c1 eb 08 33 1c 85 e0 ae 2a c1 49 74 05 f6 c2 03 75 e5 83 f9 03 76 4c 89 ce 83 ea 04 83 e6 03 c1 e9 02 83 c2 04 <33> 1a 0f b6 c3 c1 eb 08 33 1c 85 e0 ae 2a c1 0f b6 c3 c1 eb 08 
EIP: [<c118ba5d>] crc32_be+0x3d/0x9c SS:ESP 0068:e61f9e90
-- 0:conmux-control -- time-stamp -- Aug/30/07  0:36:46 --
-- 0:conmux-control -- time-stamp -- Aug/30/07  5:56:32 --
(bot:conmon-payload) disconnected


thanks,
Avantika

             reply	other threads:[~2007-08-30 18:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-30 18:16 Avantika Mathur [this message]
2007-08-31  9:21 ` jbd2_journal_commit_transaction oops Girish Shilamkar
2007-08-31 21:32   ` Avantika Mathur
2007-09-13  9:49     ` Girish Shilamkar
2007-11-02  0:40   ` [PATCH][RFC]JBD2: Fix journal checksum kernel oops on NUMA Mingming Cao
2007-11-02  5:20     ` Andreas Dilger
2007-11-02 16:31       ` Badari Pulavarty
2007-11-03  1:36         ` Andreas Dilger
2007-11-05 16:04           ` Badari Pulavarty
2007-11-05 16:15             ` Andreas Dilger
2007-11-05 18:07               ` Badari Pulavarty
2007-11-05 23:21                 ` Mingming Cao
2007-11-06  1:33                   ` Andreas Dilger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46D7097F.4020501@linux.vnet.ibm.com \
    --to=mathur@linux.vnet.ibm.com \
    --cc=girish@clusterfs.com \
    --cc=linux-ext4@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).