9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Erik Quanstrom <quanstro@quanstro.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Experiments in the wild
Date: Sun, 18 Aug 2013 14:05:28 -0400	[thread overview]
Message-ID: <vtwdfof5kxrw6vw8g3ej1kxm.1376849128465@email.android.com> (raw)

Make sure you have modified vl nop.c to emit the anti triple store bit and make sure that there is a proper root.  I had a machine hang just like that this week.

- erik


lucio@proxima.alt.za wrote:

>I have a MikroTik 411 that will soon be deployed as a Wi-Fi link to
>the Internet and in the absence of any other manner to mess with it
>until then, I decided to see how far a Plan 9 installation would go:
>
>	
>	Plan 9
>	cpu0: 680MHz mips 24k be v3.5 rev 0, no fpu
>	cpu0: 16 tlb entries, using 4K pages
>	cpu0: l1 i cache: 512 sets 4 ways 32 bytes/line
>	cpu0: l1 d cache: 256 sets 4 ways 32 bytes/linecaches configured as write-through
>	256M memory: 53M kernel data, 203M user, 1227M swap
>	#l0: atheros71xx: 1Gbps port 0X1A000000 irq 5: d4ca6d7df1ce
>	#l1: atheros71xx: 1Gbps port 0X19000000 irq 4: d4ca6d7df1cf
>
>It stops there, but there are enough lies in the above to accept that
>verdict.
>
>Still, it shows promise, given that this is 9rb created from the
>distribution.  I don't think I have the know-how to fix it (I may do
>at least some digging, though), but I thought others may find this at
>least interesting.
>
>In passing, having to build the user space for MIPS, I found that it
>helps if /mips/bin/contrib is writable by the builder: it is not
>created by default, but it comes in handy for those of us who may have
>something that will be installed in it.
>
>++L
>
>
>

             reply	other threads:[~2013-08-18 18:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-18 18:05 Erik Quanstrom [this message]
2013-08-18 18:26 ` lucio
  -- strict thread matches above, loose matches on Subject: below --
2013-08-18 17:56 lucio

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=vtwdfof5kxrw6vw8g3ej1kxm.1376849128465@email.android.com \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.net \
    /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).