커널 패닉....put_page ?? 아님 skb release ???
글쓴이: chxooi / 작성시간: 화, 2010/07/13 - 12:15오후
embeeded 개발중인데요..
아래처럼 깨지는데요..
어디를 의심해봐야 할까요...
어디서부터 "손"을 대야할지 몰라서요...
BUG: unable to handle kernel paging request at 27262524 IP: [<c0144bf4>] put_page+0x6/0xf6 *pdpt = 000000000c31a001 *pde = 0000000000000000 Oops: 0000 [#1] PREEMPT Pid: 0, comm: swapper Tainted: P (2.6.28 #2) EIP: 0060:[<c0144bf4>] EFLAGS: 00010246 CPU: 0 EIP is at put_page+0x6/0xf6 EAX: 27262524 EBX: 27262524 ECX: 00000000 EDX: cc314680 ESI: 00000000 EDI: cc2a8900 EBP: 00002b2a ESP: c055fdfc DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068 Process swapper (pid: 0, ti=c055e000 task=c0521380 task.ti=c055e000) Stack: 00000000 00000000 cc2a8900 00002b2a c0355dad cc2a8900 c055b840 cc2a8900 c0355c70 00000009 c035b30b cc04cc00 c055b858 cc011000 00000000 00000009 cc011380 0000012c cc2a8900 c02a87f6 cc20f340 cc195780 cc195780 c055ff1c Call Trace: [<c0355dad>] skb_release_data+0x69/0x83 [<c0355c70>] __kfree_skb+0x8/0x74 [<c035b30b>] netif_receive_skb+0x240/0x27f [<c02a87f6>] e1000_clean_rx_irq+0xc2/0x49e [<c02a8734>] e1000_clean_rx_irq+0x0/0x49e [<c02a83a4>] e1000_clean+0x1fd/0x58d [<c01179b8>] enqueue_task_rt+0x23/0x43 [<c0115d48>] enqueue_task+0xa/0x14 [<c0115dda>] activate_task+0x17/0x1f [<c0117843>] try_to_wake_up+0xa7/0xa9 [<c035d222>] net_rx_action+0x69/0xfa [<c011ea9e>] __do_softirq+0x53/0xe7 [<d0303403>] SystemISRWrapper+0xe/0x3f [pvrsrvkm] [<c0139a6c>] handle_IRQ_event+0x25/0x4a [<c011eb59>] do_softirq+0x27/0x29 [<c011ed72>] irq_exit+0x32/0x34 [<c0104ed8>] do_IRQ+0x4c/0x94 [<c01039bf>] common_interrupt+0x23/0x28 [<c0108b66>] mwait_idle+0x2d/0x32 [<c0101b0c>] cpu_idle+0x1e/0x63 Code: c0 74 1a 8b 03 25 00 00 08 00 83 f8 01 19 d2 83 e2 02 83 c2 01 89 d8 5b e9 1f fe ff ff 89 d8 5b e9 94 f8 ff ff 55 57 56 53 89 c3 <f7> 00 00 60 00 00 0f 85 db 00 00 00 ff 48 04 0f 94 c0 84 c0 74 EIP: [<c0144bf4>] put_page+0x6/0xf6 SS:ESP 0068:c055fdfc Kernel panic - not syncing: Fatal exception in interrupt
Forums:
BUG: unable to handle kernel
BUG: unable to handle kernel paging request at 27262524.
이미 뭔가 잘못된 상황을 처리하고 있는것 같습니다. 27262524가 처리할수 없는 값인데 처리를 해야하니까 문제가 된다고 친절하게 알려준거죠. 드라이버 (e1000)의 문제일수도 있고, kernel의 버그일수도 있겠죠. 일단 put_page에서부터 거꾸로 추척하겠습니다.
댓글 달기