Similar Aiee problem
Aiee, Killing Interrupt Handler (Bill Harris)
See my posting, "Similar problem", dated 11/19/97.
Here's an update to that posting: I've seen two more
occurrences on my production system, but with a different
call trace. Here's the call trace for the second event:
Nov 23 16:51:25 fw1 kernel: Call Trace: [ip_rcv+947/980]
[sock_wake_async+50/108] [sys_shutdown+55/96]
[arp_free_entry+85/112] [kfree_skb+136/224]
[arp_check_expire+162/368] [sys_recvmsg+84/392]
Nov 23 16:51:25 fw1 kernel: [check_region+3/36]
[do_signal+443/640] [init+784/892] [do_signal+565/640]
[init+8/892] [do_shell+41/196] [sys_setitimer+56/208]
[wake_up+36/224]
The third call trace was identical to the second.
In all cases, the Code string is identical:
Code: 8a 16 89 d0 83 e0 0f 8d 3c 86 89 7c 24 2c 83
3d 44 52 02 03
If anyone else is having a problem, it would be interesting
to know your hardware type, CPU type, memory size, type of
NIC, and anything else that might be germane to this problem.
Although none of these Aiee events have resulted in a
hang, I, too, would like to know what is causing the
problem.
Dan
|
