linux-mips
[Top] [All Lists]

Re: Unknown ARCS message/hang

To: "Erik J. Green" <erik@greendragon.org>
Subject: Re: Unknown ARCS message/hang
From: Guido Guenther <agx@sigxcpu.org>
Date: Fri, 4 Apr 2003 16:35:34 +0200
Cc: linux-mips@linux-mips.org, "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
In-reply-to: <Pine.GSO.3.96.1030404161724.7307D-100000@delta.ds2.pg.gda.pl>
Mail-followup-to: Guido Guenther <agx@sigxcpu.org>, "Erik J. Green" <erik@greendragon.org>, linux-mips@linux-mips.org, "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20030404131935.GF11906@bogon.ms20.nix> <Pine.GSO.3.96.1030404161724.7307D-100000@delta.ds2.pg.gda.pl>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.5.3i
On Fri, Apr 04, 2003 at 04:19:44PM +0200, Maciej W. Rozycki wrote:
> On Fri, 4 Apr 2003, Guido Guenther wrote:
> 
> > > > Obtaining /vmlinux.64 from server
> > > > 1813568+1150976+172144 entry: 0xa8000000211c4000
> > > > 
> > > > *** PROM write error on cacheline 0x1fcd3b00 at PC=0x211c4018 
> > > > RA=0xffffffff9fc5ace4
> > [..snip..] 
> > > 
> > >  0x211c4018 is a mapped address, which you can't use that early in a boot.
> > Isn't 0xa8000000211c4000 in xkphys and therefore unmapped? The PROM only
> > seems to look at the lower 32bits of PC though.
> 
>  0xa8000000211c4000 is indeed in XKPHYS but the code jumps to 0x211c4018.
So either the PROM or (more likely) the start address in the kernel is
bogus. What does
 objdump -x vmlinux | grep 'start address'
say?
Regards,
 -- Guido

<Prev in Thread] Current Thread [Next in Thread>