From: Chr <chunkeey@web.de>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: Johannes Berg <johannes@sipsolutions.net>,
"Luis R. Rodriguez" <mcgrof@gmail.com>,
linux-wireless@vger.kernel.org,
OpenWrt Development List <openwrt-devel@lists.openwrt.org>
Subject: Re: kernel panic on p54pci insertion on mipsel
Date: Wed, 6 Aug 2008 22:50:49 +0200 [thread overview]
Message-ID: <200808062250.49495.chunkeey@web.de> (raw)
In-Reply-To: <489A0970.9030104@wpkg.org>
On Wednesday 06 August 2008 22:28:32 Tomasz Chmielewski wrote:
>
> >>RA; 8004cc30 <handle_IRQ_event+64/d4>
> >>$12; 802e0000 <invalid_pte_table+0/1000>
> >>$14; 802e4588 <per_cpu__runqueues+30/410>
> >>$31; 8004cc30 <handle_IRQ_event+64/d4>
> >>
> >>PC; c0071834 <END_OF_CODE+3fd7aa64/????> <=====
>
> Trace; 8018405c <usb_hcd_irq+68/150>
> Trace; 8001d2bc <try_to_wake_up+78/c8>
> Trace; 8004cc30 <handle_IRQ_event+64/d4>
> Trace; 8004e0dc <handle_percpu_irq+54/ac>
> Trace; 80002ca4 <ret_from_irq+0/4>
> Trace; 8001c310 <__wake_up_common+54/bc>
> Trace; 80001e54 <plat_irq_dispatch+1ac/1d8>
> Trace; 80002ca4 <ret_from_irq+0/4>
> Trace; 80125850 <vscnprintf+14/30>
> Trace; c0070c00 <END_OF_CODE+3fd79e30/????>
> Trace; c0070c98 <END_OF_CODE+3fd79ec8/????>
> Trace; c007118c <END_OF_CODE+3fd7a3bc/????>
>
> Code; c0071828 <END_OF_CODE+3fd7aa58/????>
> 00000000 <_PC>:
> Code; c0071828 <END_OF_CODE+3fd7aa58/????>
> 0: 8ca40150 lw a0,336(a1)
> Code; c007182c <END_OF_CODE+3fd7aa5c/????>
> 4: 24020001 li v0,1
> Code; c0071830 <END_OF_CODE+3fd7aa60/????>
> 8: afa20010 sw v0,16(sp)
> Code; c0071834 <END_OF_CODE+3fd7aa64/????> <=====
> c: 8c820078 lw v0,120(a0) <=====
> Code; c0071838 <END_OF_CODE+3fd7aa68/????>
> 10: 00a08021 move s0,a1
> Code; c007183c <END_OF_CODE+3fd7aa6c/????>
> 14: 30420200 andi v0,v0,0x200
> Code; c0071840 <END_OF_CODE+3fd7aa70/????>
> 18: 1440009f bnez v0,298 <_PC+0x298>
> Code; c0071844 <END_OF_CODE+3fd7aa74/????>
> 1c: 8cb10160 lw s1,352(a1)
> Code; c0071848 <END_OF_CODE+3fd7aa78/????>
> 20: 8c820010 lw v0,16(a0)
>
> Kernel panic - not syncing: Fatal exception in interrupt
>
Ouch?! Are you sure your hardware isn't damaged?
Can you please try another wifi card in your mips,
or "test" the wifi card in a x86?
Regards,
Chr
next prev parent reply other threads:[~2008-08-06 20:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 19:55 kernel panic on p54pci insertion on mipsel Tomasz Chmielewski
2008-08-05 20:12 ` Johannes Berg
2008-08-05 21:54 ` Tomasz Chmielewski
2008-08-05 23:19 ` Luis R. Rodriguez
2008-08-06 8:02 ` Tomasz Chmielewski
2008-08-06 19:02 ` Tomasz Chmielewski
2008-08-06 19:50 ` Chr
2008-08-06 20:04 ` Tomasz Chmielewski
2008-08-06 20:16 ` Johannes Berg
2008-08-06 20:25 ` Tomasz Chmielewski
2008-08-06 20:28 ` Tomasz Chmielewski
2008-08-06 20:34 ` Michael Buesch
2008-08-06 21:14 ` Tomasz Chmielewski
2008-08-06 20:50 ` Chr [this message]
2008-08-06 21:16 ` Tomasz Chmielewski
2008-08-07 8:34 ` Tomasz Chmielewski
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=200808062250.49495.chunkeey@web.de \
--to=chunkeey@web.de \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mangoo@wpkg.org \
--cc=mcgrof@gmail.com \
--cc=openwrt-devel@lists.openwrt.org \
/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).