You need to specify the kernel version you are running, plus all other variables which causes this panic.
A objdump of panicing code (dev_queue_xmit ? not necessarily, what about eip and register/stack, etc
that have scrolled out of the screen) will be useful. Use serial console (documentation is present in
serial-console.txt) to get full dump information.
- KK
Niranjan <niranjan_cs2905@yahoo.com>
Hi,
I am trying to add cryptoapi support in wireless LAN driver (linux-wlan-ng for Prism based card) for my security project.
While doing so, I am getting a kernel panic. I am not able to debug it as there is no logging of any information related to kernel panic in the log files (/var/log/messages or /var/log/dmesg) when I reboot the system. I have attached the log below available on the screen.
Can anyone please help me in what can be possible error by looking at the log ?
I will greatly appreciate any help in this matter.
Regards,
-Niranjan
Research Assistant, UMASS.
Log available on the screen:
......
......
dev_queue_xmit [kernel] 0x210 (0xc034de04))
neigh_resolve_output [kernel] 0xec (0xc034de1c))
neigh_update
neigh_lookup
arp_process
netif_receive_skb
process_backlog
net_rx_action
do_softirq
do_IRQ
call_do_IRQ
dump_fpu
apm_bios_call_simple
apm_do_idle
apm_cpu_idle
apm_cpu_idle
default_idle
cpu_idle
stext [kernel] 0x0 (0xc034dfe0))
Code: 0f 0b e2 3f d7 25 c0 e9 77 fd ff ff 8d b4 26 00 00 00 00
<0>Kernel Panic: Aiee, killing interrupt handler!
In interrupt handler – not syncing
Do you Yahoo!?
Yahoo! Finance: Get your refund fast by filing online
