Tim Feeney wrote:
I have a Suse Linux 2.6.3 system that is getting the following errors:
Nov 12 03:42:01 jupiter kernel: Unable to handle kernel paging request at 0000015d9690d5c4 RIP: Nov 12 03:42:01 jupiter kernel: <ffffffff8025010f>{memmove+15}PML4 8063 PGD 0 Nov 12 03:42:01 jupiter kernel: Oops: 0002 [1] Nov 12 03:42:01 jupiter kernel: CPU 0 Nov 12 03:42:01 jupiter kernel: Pid: 26212, comm: DataServer Not tainted Nov 12 03:42:01 jupiter kernel: RIP: 0010:[memmove+15/64] <ffffffff8025010f>{memmove+15} Nov 12 03:42:01 jupiter kernel: RIP: 0010:[<ffffffff8025010f>] <ffffffff8025010f>{memmove+15} Nov 12 03:42:01 jupiter kernel: RSP: 0018:ffffffff804b55e0 EFLAGS: 00010212 Nov 12 03:42:01 jupiter kernel: RAX: 0000000000000004 RBX: 0000000000000002 RCX: 000000000000006b Nov 12 03:42:01 jupiter kernel: RDX: 0000000000000228 RSI: 000001001cf845c8 RDI: 0000015d9690d5c4 Nov 12 03:42:01 jupiter kernel: RBP: 0000000000000003 R08: 000001001cf84548 R09: 0000000000000000 Nov 12 03:42:01 jupiter kernel: R10: 0000000000000004 R11: 0000000000000050 R12: 000001001cf84048 Nov 12 03:42:01 jupiter kernel: R13: 0000000000000004 R14: 00000100134c2b80 R15: 000001001cf84000 Nov 12 03:42:02 jupiter kernel: FS: 0000000000a3d960(005b) GS:ffffffff80537d40(0000) knlGS:0000000000000000 Nov 12 03:42:02 jupiter kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b Nov 12 03:42:03 jupiter kernel: CR2: 0000015d9690d5c4 CR3: 0000000000101000 CR4: 00000000000006a0 Nov 12 03:42:04 jupiter kernel: Process DataServer (pid: 26212, stackpage=100025ed970) Nov 12 03:42:04 jupiter kernel: Stack: ffffffff801c1143 00000100060a84c0 0000000000000004 0000077400000000 Nov 12 03:42:04 jupiter kernel: 00000000000004ec ffffffff804b5abc 0000022817ed2000 ffffffff804b56c8 Nov 12 03:42:04 jupiter kernel: 000001001cf84048 0000000000000004 Nov 12 03:42:04 jupiter kernel: Call Trace:<ffffffff801c1143>{leaf_paste_in_buffer+147} <ffffffff801acfda>{balance_leaf+9690} Nov 12 03:42:04 jupiter kernel: <ffffffff801ad432>{do_balance+162} <ffffffff801bacd8>{fix_nodes+632} Nov 12 03:42:04 jupiter kernel: <ffffffff801c681a>{reiserfs_paste_into_item+154} <ffffffff801b1d92>{reiserfs_get_block+3602} Nov 12 03:42:04 jupiter kernel: <ffffffff80174d49>{__find_get_block+201} <ffffffff80174d49>{__find_get_block+201} Nov 12 03:42:04 jupiter kernel: <ffffffff8017561e>{__block_prepare_write+366} <ffffffff8015836c>{buffered_rmqueue+316} Nov 12 03:42:04 jupiter kernel: <ffffffff801b0f80>{reiserfs_get_block+0} <ffffffff8017609a>{block_prepare_write+26} Nov 12 03:42:04 jupiter kernel: <ffffffff80156528>{generic_file_aio_write_nolock+1304} Nov 12 03:42:04 jupiter kernel: <ffffffff80156957>{generic_file_write_nolock+87} <ffffffff801c42ad>{search_by_key+2189} Nov 12 03:42:04 jupiter kernel: Nov 12 03:42:04 jupiter kernel: Nov 12 03:42:04 jupiter kernel: Code: f3 a5 f6 c2 02 74 02 66 a5 f6 c2 01 74 01 a4 eb 11 48 8d 74 Nov 12 03:42:04 jupiter kernel: RIP <ffffffff8025010f>{memmove+15} RSP <ffffffff804b55e0> Nov 12 03:42:04 jupiter kernel: CR2: 0000015d9690d5c4 Nov 12 03:42:04 jupiter kernel: <4>time.c: Lost 0 timer tick(s)! (rip ffffffff8013d91e)
I am not knowledgable in how to decode this to find out what the problem is. When this happened the system had a loadaverage of 600+. After I rebooted the system if ran ksymoops and got the following snippet that points to an internal application (DataServer) having a problem writing out. Nov 12 03:42:04 jupiter kernel: Process DataServer (pid: 26212, stackpage=100025ed970) Nov 12 03:42:04 jupiter kernel: Stack: ffffffff801c1143 00000100060a84c0 0000000000000004 0000077400000000 Nov 12 03:42:04 jupiter kernel: 00000000000004ec ffffffff804b5abc 0000022817ed2000 ffffffff804b56c8 Nov 12 03:42:04 jupiter kernel: 000001001cf84048 0000000000000004 Nov 12 03:42:04 jupiter kernel: Call Trace:<ffffffff801c1143>{leaf_paste_in_buffer+147} <ffffffff801acfda>{balance_leaf+9690} Nov 12 03:42:04 jupiter kernel: <ffffffff801ad432>{do_balance+162} <ffffffff801bacd8>{fix_nodes+632} Nov 12 03:42:04 jupiter kernel: <ffffffff801c681a>{reiserfs_paste_into_item+154} <ffffffff801b1d92>{reiserfs_get_block+3602} Nov 12 03:42:04 jupiter kernel: <ffffffff80174d49>{__find_get_block+201} <ffffffff80174d49>{__find_get_block+201} Nov 12 03:42:04 jupiter kernel: <ffffffff8017561e>{__block_prepare_write+366} <ffffffff8015836c>{buffered_rmqueue+316} Nov 12 03:42:04 jupiter kernel: <ffffffff801b0f80>{reiserfs_get_block+0} <ffffffff8017609a>{block_prepare_write+26} Nov 12 03:42:04 jupiter kernel: <ffffffff80156528>{generic_file_aio_write_nolock+1304} Nov 12 03:42:04 jupiter kernel: <ffffffff80156957>{generic_file_write_nolock+87} <ffffffff801c42ad>{search_by_key+2189} Nov 12 03:42:04 jupiter kernel: Code: f3 a5 f6 c2 02 74 02 66 a5 f6 c2 01 74 01a4 eb 11 48 8d 74
Any pointers in how to further debug this would be great. Thank you.
Tim
Post to linux-kernel@vger.kernel.org, I'm sure you'd get a quick answer and perhaps a patch to apply. If you need to rebuild, you could go for 2.6.9 instead as many issues have been resolved since then. Regards Sid. -- Sid Boyce .... Hamradio G3VBV and keen Flyer =====LINUX ONLY USED HERE=====