처음 보는 거라 또 질문을 올립니다.

System이 부정기적으로 자꾸 죽기에, kernel configuration에서 Kernel hacking 쪽의
option들을 선택하고 실행해보니,,아래와 같은 message가 display되네요..

이런 경우는 어떻게 접근을 하는게 좋을까요?
비슷한 경험을 해보신분이 계시면 조언 좀 부탁드립니다.

미리 감사드립니다..

=======================================================
[ INFO: possible circular locking dependency detected ]
2.6.19.7 #39
-------------------------------------------------------
swapper/0 is trying to acquire lock:
(&tbl->lock){-+-+}, at: [] pneigh_lookup+0x40/0x178

but task is already holding lock:
(&list->lock#2){-+..}, at: [] neigh_proxy_process+0x21/0xc6

which lock already depends on the new lock.

the existing dependency chain (in reverse order) is:

-> #2 (&list->lock#2){-+..}:
[] __lock_acquire+0x8cd/0x9ab
[] skb_dequeue+0x11/0x41
[] lock_acquire+0x6a/0x84
[] skb_dequeue+0x11/0x41
[] _spin_lock_irqsave+0x4c/0x5c
[] skb_dequeue+0x11/0x41
[] skb_dequeue+0x11/0x41
[] eth_header_cache_update+0x0/0x2b
[] skb_queue_purge+0x1a/0x21
[] neigh_update+0x331/0x38b
[] arp_process+0x59e/0x5db
[] find_usage_backwards+0x62/0x86
[] find_usage_backwards+0x62/0x86
[] check_usage+0x24/0x24e
[] arp_rcv+0x115/0x136
[] process_backlog+0x70/0xee
[] mark_held_locks+0x46/0x62
[] netif_receive_skb+0x15b/0x1d6