From: Krishna Kumar <kumarkr@us.ibm.com>
To: Niranjan <niranjan_cs2905@yahoo.com>
Cc: netdev@oss.sgi.com
Subject: Re: Kernel Panic
Date: Tue, 10 Feb 2004 17:16:52 -0800 [thread overview]
Message-ID: <OF67EB6530.F0E7FBBC-ON88256E37.0006CCC0@us.ibm.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 3510 bytes --]
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> |
| | Sent by: |
| | netdev-bounce@oss|
| | .sgi.com |
| | |
| | |
| | 02/10/2004 04:32 |
| | PM |
| | |
|---------+---------------------------->
>-----------------------------------------------------------------------------------------------------------------|
| |
| To: netdev@oss.sgi.com |
| cc: |
| Subject: Kernel Panic |
| |
>-----------------------------------------------------------------------------------------------------------------|
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:
......
......
[<c01f5850>] dev_queue_xmit [kernel] 0x210
(0xc034de04))
[<c01f98ec>] 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
[<c01015000> 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
[-- Attachment #1.2: Type: text/html, Size: 3666 bytes --]
[-- Attachment #2: pic03043.gif --]
[-- Type: image/gif, Size: 1255 bytes --]
next reply other threads:[~2004-02-11 1:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-11 1:16 Krishna Kumar [this message]
[not found] <4BF21646.60008@gmail.com>
[not found] ` <4BF21BD3.60901@gmail.com>
[not found] ` <4BF21DAD.6050609@gmail.com>
[not found] ` <1274159136.2567.24.camel@edumazet-laptop>
[not found] ` <4BF222C8.6000200@gmail.com>
2010-05-18 5:49 ` kernel panic Eric Dumazet
-- strict thread matches above, loose matches on Subject: below --
2004-02-11 0:32 Kernel Panic Niranjan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=OF67EB6530.F0E7FBBC-ON88256E37.0006CCC0@us.ibm.com \
--to=kumarkr@us.ibm.com \
--cc=netdev@oss.sgi.com \
--cc=niranjan_cs2905@yahoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).