Koozali.org: home of the SME Server
Obsolete Releases => SME Server 7.x => Topic started by: tariqf on March 27, 2006, 11:36:28 AM
-
My server is on sme 7b5 - I know this is desperately out of date but it's been running perfect for 4 months until it froze on friday. When I rebooted and looked at my logs the last thing I see is
Mar 24 20:00:27 sme kernel: Assertion failure in journal_start() at fs/jbd/transaction.c:274: "handle->h_transaction->t_journal == journal"
Mar 24 20:00:27 sme kernel: ------------[ cut here ]------------
Mar 24 20:00:27 sme kernel: kernel BUG at fs/jbd/transaction.c:274!
Mar 24 20:00:27 sme kernel: invalid operand: 0000 [#1]
Mar 24 20:00:27 sme kernel: Modules linked in: ppp_mppe(U) ppp_async crc_ccitt ppp_generic(U) slhc vfat fat appletalk(U) ipt_ULOG ipt_REJECT ipt_MASQUERADE
ipt_state ipt_TOS ip_nat_ftp ip_conntrack_ftp iptable_mangle iptable_nat ip_conntrack iptable_filter ip_tables button battery ac usb_storage ohci_hcd ehci_h
cd snd_intel8x0 snd_ac97_codec snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd_page_alloc snd_mpu401_uart snd_rawmidi snd_seq_device snd soundcore sis900 81
39too mii bonding floppy dm_snapshot dm_zero dm_mirror ext3 jbd raid1 dm_mod sata_sis libata sd_mod scsi_mod
Mar 24 20:00:27 sme kernel: CPU: 0
Mar 24 20:00:27 sme kernel: EIP: 0060:[<de89d704>] Not tainted VLI
Mar 24 20:00:27 sme kernel: EFLAGS: 00010212 (2.6.9-11.EL)
Mar 24 20:00:27 sme kernel: EIP is at journal_start+0x45/0x9e [jbd]
Mar 24 20:00:27 sme kernel: eax: 00000073 ebx: c618e64c ecx: de8a7dea edx: c7483ccc
Mar 24 20:00:27 sme kernel: esi: c1438200 edi: c7483000 ebp: 00000000 esp: c7483cc8
Mar 24 20:00:27 sme kernel: ds: 007b es: 007b ss: 0068
Mar 24 20:00:27 sme kernel: Process cp (pid: 582, threadinfo=c7483000 task=d6b34dd0)
Mar 24 20:00:27 sme kernel: Stack: de8a7dea de8a7982 de8a7dae 00000112 de8a7ed0 c0f8c88c c7483d18 00000063
Mar 24 20:00:27 sme kernel: de8df153 c0f8c88c c7483d18 c017fcc5 c0f8c88c c017fd50 cb9b7df4 00000080
Mar 24 20:00:27 sme kernel: c03532e0 c01803eb 00000080 00000080 cceda2ac c08bca08 00000000 00000081
...followed by a call trace.
Please can anyone explain this error or what it could be? I do not want to do a full upgrade of all my packages but am willing to upgrade those that may fix the problem. Should I just upgrade the kernel? I can do this with yum but will this beak anything else if I simply upgrade the kernel?
-
You should post any thing like that to the Bug Tracker, but I suspect the answer will be upgrade to latest release as there has been a 7.0b6/7/8/9 & 7.0pre1/2/3/4 now we are at 7.0rc1