From: Geert Uytterhoeven <geert@linux-m68k.org>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: loswillios <loswillios@gmail.com>,
kyle@mcmartin.ca, linux-wireless@vger.kernel.org,
developers@islsm.org, linux-mips@linux-mips.org
Subject: Re: prism54 - MIPS do_be() trap caught
Date: Tue, 27 Nov 2007 18:25:06 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.64.0711271824350.14777@anakin> (raw)
In-Reply-To: <43e72e890711270917o309441a0g99ac435a629b6d5e@mail.gmail.com>
On Tue, 27 Nov 2007, Luis R. Rodriguez wrote:
> Changing subject, CC'ing linux-mips, perhaps they can help.
>
> On Nov 26, 2007 7:54 PM, loswillios <loswillios@gmail.com> wrote:
> > Jan Willies wrote:
> > > Luis R. Rodriguez wrote:
> > >> Actually I've been informed this is not unaligned access problem but
> > >> instead it occurs on do_be() or ip22_be_interrupt() on MIPS. I'll have
> > >> to check how that works, I do not yet understand how this is reached.
> > >
> > > I will try a new build with prism54 in the next days and let you know if
> > > that issue is still present.
> >
> > Still the same problem with 2.6.23.1:
> >
> > root@OpenWrt:/# ifconfig eth1 up
> > eth1: resetting device...
> > eth1: uploading firmware...
> > eth1: firmware version: 1.0.4.3
> > eth1: firmware upload complete
> > eth1: interface reset complete
> >
> > root@OpenWrt:/# iwlist eth1 scanning
> > Data bus error, epc == c011518c, ra == c01146cc
> > Oops[#1]:
> > Cpu 0
> > $ 0 : 00000000 1000b800 abad0000 00000032
> > $ 4 : 00000001 c00c8000 00000013 00000001
> > $ 8 : 0000003c 80102bd4 ffffffff 81e2101c
> > $12 : ffffffff 00000580 2ab8af24 00000498
> > $16 : 81e21680 000000fa 81339380 0000004a
> > $20 : 81339380 00000000 a1e80000 81339000
> > $24 : 00000000 2abd55e0
> > $28 : 813b4000 813b5cc8 00000019 c01146cc
> > Hi : 00000000
> > Lo : 00000580
> > epc : c011518c Not tainted
> > ra : c01146cc Status: 1000b803 KERNEL EXL IE
> > Cause : 0000001c
> > PrId : 00029007
>
> I can see that this comes from arch/mips/kernel/traps.c do_be() but I
> fail to see when this is triggered. Perhaps someone from linux-mips
> might be able to help shed some light here. I tried looking into the
> stack trace before but I couldn't find any code that made me suspect
> of a possible big endian problem (it seems that may be the problem?).
> The stack trace used to look like this:
BE = bus error, not big endian here.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2007-11-27 17:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-27 17:17 prism54 - MIPS do_be() trap caught Luis R. Rodriguez
2007-11-27 17:25 ` Geert Uytterhoeven [this message]
2007-11-27 18:08 ` Maciej W. Rozycki
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=Pine.LNX.4.64.0711271824350.14777@anakin \
--to=geert@linux-m68k.org \
--cc=developers@islsm.org \
--cc=kyle@mcmartin.ca \
--cc=linux-mips@linux-mips.org \
--cc=linux-wireless@vger.kernel.org \
--cc=loswillios@gmail.com \
--cc=mcgrof@gmail.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