Im running FC5, 2.6.16-1.2133_FC5smp kernel, 3.2ghz P4. I have had yum install newer kernels but none of them boot, hanging randomly during the boot. (thats a different problem, though)
Last night my computer locked up, or at least I thought it did. According gkrellm, it was at 1hr and 6 minutes after I booted the computer. I (hard) rebooted, and finished what I needed to do and went bed, with the computer still on. This morning the computer was fine, but it apparently hung up again, and since it wasn't killed immidietly, the kernel had left me a message, via syslogd:
Code:
essage from syslogd@188-69 at Mon Oct 9 01:11:35 2006 ...
188-69 kernel: Assertion failure in dx_probe() at fs/ext3/namei.c:383: "dx_get_limit(entries) == dx_root_limit(dir, root->info.info_length)"
essage from syslogd@188-69 at Mon Oct 9 01:13:35 2006 ...
188-69 kernel: ------------[ cut here ]------------
essage from syslogd@188-69 at Mon Oct 9 01:13:36 2006 ...
188-69 kernel: kernel BUG at fs/ext3/namei.c:383!
essage from syslogd@188-69 at Mon Oct 9 01:13:36 2006 ...
188-69 kernel: invalid opcode: 0000 [#1]
essage from syslogd@188-69 at Mon Oct 9 01:13:36 2006 ...
188-69 kernel: SMP
essage from syslogd@188-69 at Mon Oct 9 01:13:36 2006 ...
188-69 kernel: CPU: 0
essage from syslogd@188-69 at Mon Oct 9 01:13:37 2006 ...
188-69 kernel: EIP is at dx_probe+0x16e/0x2b4 [ext3]
essage from syslogd@188-69 at Mon Oct 9 01:13:37 2006 ...
188-69 kernel: eax: 00000081 ebx: f6acc8a0 ecx: e679fe68 edx: f8831c52
essage from syslogd@188-69 at Mon Oct 9 01:13:37 2006 ...
188-69 kernel: esi: d6db0418 edi: 00000000 ebp: f5c2ecd0 esp: e679fe64
essage from syslogd@188-69 at Mon Oct 9 01:13:37 2006 ...
188-69 kernel: ds: 007b es: 007b ss: 0068
essage from syslogd@188-69 at Mon Oct 9 01:13:37 2006 ...
188-69 kernel: Process updatedb (pid: 5785, threadinfo=e679f000 task=f7cd08d0)
essage from syslogd@188-69 at Mon Oct 9 01:13:37 2006 ...
188-69 kernel: Stack: <0>f8831c52 f8830ca8 f8831c42 0000017f f8831dd8 00000090 c01b51c1 f6acc8a0
essage from syslogd@188-69 at Mon Oct 9 01:13:37 2006 ...
188-69 kernel: e679fe98 00000000 debe8a00 f73e1180 f6acc8a0 00000000 f88282d2 e679feb4
essage from syslogd@188-69 at Mon Oct 9 01:13:37 2006 ...
188-69 kernel: e679fee0 00000000 f73e1180 debe8ce0 00000000 00000002 c01b575b 00000002
essage from syslogd@188-69 at Mon Oct 9 01:13:37 2006 ...
188-69 kernel: Call Trace:
essage from syslogd@188-69 at Mon Oct 9 01:13:37 2006 ...
188-69 kernel: [<c01b51c1>] avc_has_perm+0x3a/0x44 [<f88282d2>] ext3_htree_fill_tree+0x8c/0x1a0 [ext3]
essage from syslogd@188-69 at Mon Oct 9 01:13:37 2006 ...
188-69 kernel: [<c01b575b>] inode_has_perm+0x54/0x5c [<f8821842>] ext3_readdir+0x1d3/0x551 [ext3]
essage from syslogd@188-69 at Mon Oct 9 01:13:37 2006 ...
188-69 kernel: [<c0173b24>] filldir64+0x0/0xc3 [<c0173ce3>] vfs_readdir+0x66/0x90
essage from syslogd@188-69 at Mon Oct 9 01:13:37 2006 ...
188-69 kernel: [<c0173b24>] filldir64+0x0/0xc3 [<c0173d70>] sys_getdents64+0x63/0xa5
essage from syslogd@188-69 at Mon Oct 9 01:13:37 2006 ...
188-69 kernel: [<c0103db9>] syscall_call+0x7/0xb <0>Code: 0c 29 d0 83 e8 18 c1 e8 03 39 c1 74 29 68 d8 1d 83 f8 68 7f 01 00 00 68 42 1c 83 f8 68 a8 0c 83 f8 68 52 1c 83 f8 e8 cf ce 8f c7 <0f> 0b 7f 01 42 1c 83 f8 83 c4 14 8b 44 24 28 89 44 24 0c 66 8b
I could have sworn there were m's on the fronts of the 'essage'-es, not sure where they went.
Did I break the kernel? updatedb? hdd?
I've googled the assertion error bit, but there wan't anything out there that would help...
Interestingly enough, this is 1 hr and 6 minutes after it rebooted...
Any ideas?
Thanks,
Scott McNeely
EDIT: Not sure what caused the initial problem, but I have resolved the error. I boted up the Fedora installer and did a linux rescue, not mounting any of the hdd, and ran fsck on all my partitions and then e2fsck on my / and /boot partitions. The computer no longer hangs, and I can do ls in my boot partition, a symptom I just discovered in the past day or so.
