[linux-cifs-client] is this crash CIFS related?

[aragonx at dcsnow.com]

I recently had two system lockups.  As far as I can tell, these lockups
did not happen until I started using CIFS although I had to roll my own
kernel in order to use a newer version of CIFS.

I have three identical machines located in different facilities.  Two are
local to the machine that has the CIFS mount and one is remote.  The
machine that is at the remote site is the one that has had the lockups. 
It also had many CIFS related error messages in /var/log/messages.

Here is the error that was reported right before the last lockup.  Any
help would be appreciated as this is way over my head.

Dec 16 15:05:01 testbox HWMON:
root at syngo.invalid|LogAgentSelfTest|LogAgentSelfTest_SDM_Message
Dec 16 15:07:47 testbox kernel: Assertion failure in
journal_commit_transaction() at fs/jbd/commit.c:793:
"jh->b_next_transaction == ((void *)0)"
Dec 16 15:07:47 testbox kernel: ----------- [cut here ] --------- [please
bite here ] ---------
Dec 16 15:07:47 testbox kernel: Kernel BUG at fs/jbd/commit.c:793
Dec 16 15:07:47 testbox kernel: invalid opcode: 0000 [5] SMP
Dec 16 15:07:47 testbox kernel: CPU 2
Dec 16 15:07:47 testbox kernel: Modules linked in: nls_utf8 cifs processor
usb_storage usbhid ohci_hcd ehci_hcd i2c_nforce2 i2c_core ipv6 usbcore
e1000 edd e
vdev joydev st sr_mod dm_mod mppVhba qla2400 qla2xxx firmware_class
qla2xxx_conf intermodule sata_nv libata ext3 jbd mptsas mptscsih mptbase
scsi_transport_s as mppUpper sg sd_mod scsi_mod
Dec 16 15:07:47 testbox kernel: Pid: 2759, comm: kjournald Not tainted
2.6.16.59 #2
Dec 16 15:07:47 testbox kernel: RIP: 0010:[<ffffffff8809ef47>]
<ffffffff8809ef47>{:jbd:journal_commit_transaction+4695}
Dec 16 15:07:47 testbox kernel: RSP: 0018:ffff810ffc63bd88  EFLAGS: 00010292
Dec 16 15:07:47 testbox kernel: RAX: 0000000000000075 RBX:
ffff810d527fdbe0 RCX: ffffffff803fda28
Dec 16 15:07:47 testbox kernel: RDX: ffffffff803fda28 RSI:
0000000000000292 RDI: ffffffff803fda20
Dec 16 15:07:47 testbox kernel: RBP: ffff810537296970 R08:
0000000000000000 R09: ffff810ffc63bad8
Dec 16 15:07:47 testbox kernel: R10: 0000000000000040 R11:
0000000000000006 R12: ffff810597bf76d0
Dec 16 15:07:47 testbox kernel: R13: ffff81089c56cd80 R14:
ffff810c14393800 R15: ffff810c1439395c
Dec 16 15:07:47 testbox kernel: FS:  00002b72e95a9b00(0000)
GS:ffff81080006c3c0(0000) knlGS:00000000af1d0bb0
Dec 16 15:07:47 testbox kernel: CS:  0010 DS: 0000 ES: 0000 CR0:
000000008005003b
Dec 16 15:07:48 testbox kernel: CR2: 00000000ccd00000 CR3:
0000000000101000 CR4: 00000000000006e0
Dec 16 15:07:48 testbox kernel: Process kjournald (pid: 2759, threadinfo
ffff810ffc63a000, task ffff810ffe7d6100)
Dec 16 15:07:48 testbox kernel: Stack: 0000000000000000 ffff81089c56cde8
ffff810c14393824 00000f6c00000000
Dec 16 15:07:48 testbox kernel:        ffff8104cf317094 0000000000000000
ffff810ffe7d3000 0000000000000000
Dec 16 15:07:48 testbox kernel:        ffff810b835fdc10 0000000000001305
Dec 16 15:07:48 testbox kernel: Call Trace:
<ffffffff80139d89>{lock_timer_base+41}
<ffffffff880a323b>{:jbd:kjournald+363}
Dec 16 15:07:48 testbox kernel:
<ffffffff80145460>{autoremove_wake_function+0}
<ffffffff80145460>{autoremove_wake_function+0}
Dec 16 15:07:48 testbox kernel: <ffffffff880a34c0>{:jbd:commit_timeout+0}
<ffffffff8010bc5e>{child_rip+8} Dec 16 15:07:48 testbox kernel:
<ffffffff880a30d0>{:jbd:kjournald+0} <ffffffff8010bc56>{child_rip+0}
Dec 16 15:07:48 testbox kernel:
Dec 16 15:07:48 testbox kernel: Code: 0f 0b 68 ff 49 0a 88 c2 19 03 48 89
ef e8 67 c8 ff ff 8b 03
Dec 16 15:07:48 testbox kernel: RIP
<ffffffff8809ef47>{:jbd:journal_commit_transaction+4695} RSP
<ffff810ffc63bd88>
Dec 16 15:22:44 testbox syslogd 1.4.1: restart.


---
Will Yonker



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.