Wiktor S. Informatyk
Temat: Unable to handle kernel paging request
Witam!Od jakiegos czasu zawiesza nam sie serwer Dell PE 2900 na SLES (Linux x 2.6.5-7.308-smp #1 SMP Mon Dec 10 11:36:40 UTC 2007 x86_64 x86_64 x86_64 GNU/Linux).
Oto zrzut z /var/log/kernel/alert/log
May 24 07:46:03 x kernel: Unable to handle kernel paging request at 0000000000100108 RIP:
May 24 07:46:03 x kernel: <ffffffff801482d8>{free_uid+40}
May 24 07:46:03 x kernel: PML4 141500067 PGD 25354067 PMD 0
May 24 07:46:03 x kernel: Oops: 0002 [1] SMP
May 24 07:46:03 x kernel: CPU 1
May 24 07:46:03 x kernel: Pid: 19116, comm: smbd Tainted: G U (2.6.5-7.308-smp SLES9_SP4_BRANCH-20071210113640)
May 24 07:46:03 x smbd[9448]: [2013/05/24 07:46:03, 0] lib/util_sock.c:get_peer_addr(1232)
May 24 07:46:03 x smbd[9448]: getpeername failed. Error was Transport endpoint is not connected
May 24 07:46:03 x smbd[13246]: [2013/05/24 07:46:03, 0] lib/util_sock.c:get_peer_addr(1232)
May 24 07:46:03 x smbd[13246]: getpeername failed. Error was Transport endpoint is not connected
May 24 07:46:03 x smbd[13246]: [2013/05/24 07:46:03, 0] lib/util_sock.c:get_peer_addr(1232)
May 24 07:46:03 x smbd[13246]: getpeername failed. Error was Transport endpoint is not connected
May 24 07:46:03 x smbd[13246]: [2013/05/24 07:46:03, 0] lib/access.c:check_access(327)
May 24 07:46:03 x kernel: RIP: 0010:[<ffffffff801482d8>] <ffffffff801482d8>{free_uid+40}
May 24 07:46:03 x kernel: RSP: 0018:0000010137a1ddd8 EFLAGS: 00010002
May 24 07:46:03 x kernel: RAX: 0000000000100100 RBX: 000001022311ea40 RCX: 000001022311ea58
May 24 07:46:03 x kernel: RDX: 0000000000200200 RSI: 000001022311ea40 RDI: 000001022311ea40
May 24 07:46:03 x kernel: RBP: 000001019f30f5a0 R08: 0000000000000001 R09: 0000000000000000
May 24 07:46:03 x kernel: R10: 00000000000000ea R11: 0000000000000246 R12: 000000000000000a
May 24 07:46:03 x kernel: R13: 0000010137a1de98 R14: 0000000000000000 R15: ffffffff8011074d
May 24 07:46:03 x kernel: FS: 0000002a9558bbe0(0000) GS:ffffffff805e3a80(0000) knlGS:0000000000000000
May 24 07:46:03 x kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
May 24 07:46:03 x kernel: CR2: 0000000000100108 CR3: 00000000cfb1f000 CR4: 00000000000006e0
May 24 07:46:03 x kernel: Process smbd (pid: 19116, threadinfo 0000010137a1c000, task 0000010226a63380)
May 24 07:46:03 x kernel: Stack: 0000010228122490 ffffffff80149424 0000000000000000 0000010137a1de98
May 24 07:46:03 x kernel: 0000010226a63380 0000010226a63ad8 0000000000000064 ffffffff8014b46a
May 24 07:46:03 x kernel: 0000000000000000 0000010137a1df58
May 24 07:46:03 x kernel: Call Trace:<ffffffff80149424>{__dequeue_signal+388} <ffffffff8014b46a>{dequeue_signal+74}
May 24 07:46:03 x kernel: <ffffffff8014b8f4>{get_signal_to_deliver+308} <ffffffff8010fb75>{do_signal+149}
May 24 07:46:03 x kernel: <ffffffff8013da40>{autoremove_wake_function+0} <ffffffff8021d773>{cap_task_post_setuid+3}
May 24 07:46:03 x kernel: <ffffffff8011074d>{sysret_signal+28} <ffffffff801109ab>{ptregscall_common+103}
May 24 07:46:03 x kernel:
May 24 07:46:03 x kernel:
May 24 07:46:03 x kernel: Code: 48 89 50 08 48 89 02 48 c7 41 08 00 02 20 00 48 c7 43 18 00
Ktos ma jakis pomysl jaka jest tego przyczyna? Ram sprawdzony jest ok, procesor, plyta glowna?