Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Ashlesha Shintre <ashlesha@kenati.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Portmap on the Encore M3
Date: Mon, 13 Nov 2006 23:38:03 +0000	[thread overview]
Message-ID: <20061113233802.GA17130@linux-mips.org> (raw)
In-Reply-To: <1163443607.6532.9.camel@sandbar.kenati.com>

On Mon, Nov 13, 2006 at 10:46:47AM -0800, Ashlesha Shintre wrote:

> > RPC: sendmsg returned error 128.
> > <4>nfs: RPC call returned error 128 

128 = ENETUNREACH.

> I m trying to boot the 2.6.14.6 kernel onto the Encore M3 board that has
> the MIPS AU1500 processor on it.

For more information [1] about 2.6.14 kernels see http://tinyurl.com/hjexx ;-)

> The .config file contains the following line: CONFIG_PORTMAP=y
> The server from which the NFS is mounted is also running the portmap
> daemon..
> 
> Is there a way to check if the portmap server is functioning properly?
> 
> 
> Also:
> 
> - The BogoMIPS value is 7186 which seems too low for the AU1500 -- how
> can I check that the timer interrupt is being handled correctly?  The
> AU1500 has 2 counters which are used to generate a clock
> 
> - On the serial console I can only see messages upto this point:
> 
> 
> > 16.35 BogoMIPS (lpj=8176)

Sounds about right if your CPU clock hapens to be 8MHz so probably not.
Chances the counter was missprogrammed.  Or are you running uncached?
Uncached will completly devastate performance.

> > calibrate delay done
> > anon vma init done
> > Mount-cache hash table entries: 512
> > Checking for 'wait' instruction...  unavailable.
> > NET: Registered protocol family 16
> > size of au1xxx platform devices is 1
> 
> After this, the serial console 'hangs' -- I can see the RPC error from the log buffer, accessed from the JTAG port..
> --Please give any suggestions as to where I should start looking to narrow down and figure out the problem..

At about this point the actual console driver is registered and takes
over from the early console driver - whatever that may be in your case.
So seems the early console driver is fine but the actual console driver
(that is serial driver) is falling over.

  Ralf

[1] Okay, I'm just trying to convince people to upgrade :-)

  reply	other threads:[~2006-11-13 23:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-13 18:46 Portmap on the Encore M3 Ashlesha Shintre
2006-11-13 23:38 ` Ralf Baechle [this message]
2006-11-14  2:03   ` Ashlesha Shintre
2006-11-14 13:05     ` Ralf Baechle
2006-11-14 13:05       ` Ralf Baechle
2006-11-14 18:28       ` Ashlesha Shintre
2006-11-14 19:11         ` Ralf Baechle
2006-11-15 22:24           ` Ashlesha Shintre
2006-11-20 23:41     ` LPJ value on the AU1500 Ashlesha Shintre

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=20061113233802.GA17130@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=ashlesha@kenati.com \
    --cc=linux-mips@linux-mips.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