9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jared Jennings <jjenning@gmail.com>
To: 9fans@9fans.net
Subject: [9fans] Plan9 on QNAP TS-212 NAS (kw)
Date: Fri,  8 Jul 2011 23:38:20 -0500	[thread overview]
Message-ID: <CACXGR2Q0bf3dkWGrVT=rkqYrNERe5xdzPuh836CJsbo84A6jVA@mail.gmail.com> (raw)

Hello everyone, I got a QNAP TS-212 filer, because it purports to have
the same processor as the SheevaPlug, but has space in its case for
two SATA hard drives, and a separate power supply, and a cooling fan,
thus neatly avoiding all the problems I foresaw in using a SheevaPlug
as a file server.

Anyway, upon booting 9plug according to the instructions in
booting(8), I got this sort of thing:

Marvell>> tftp 0x1000 kw-example
[...]
Marvell>> tftp 0x800000 9plug
[...]
Marvell>> go 0x800000
## Starting application at 0x00800000 ...

Plan 9 from Bell Labs

l1 D: 16384 bytes, 4 ways 128 sets 32 bytes/line; write-through only
l1 I: 16384 bytes, 4 ways 128 sets 32 bytes/line; write-back type `reg
7 ops, format C' (016) possible
l2 cache: 256K or 512K: 4 ways, 32-byte lines, write-back, sdram only
cpu0: 1200MHz ARM Marvell 88F6281 A1; arm926ej-s arch v5te rev 2.1 part 131
#l0: 88e1116: 100Mbps port 0xf1072000 irq 11: [mac address]
#l1: ether1116: init mii failure
#u/uspurious irqbridge interrupt: 00000010
spurious irqbridge interrupt: 00000010
spurious irqbridge interrupt: 00000010
spurious irqbridge interrupt: 00000010
spurious irqbridge interrupt: 00000010
[repeats for about 15 seconds at more than 100 messages per second,
then the system reboots]

Judging from the place where that message is printed, in
/sys/src/9/kw/trap.c (search for irq%s), the 'bridge' sort of
interrupt is flagged in the CPU status register; the documentation
from Marvell shows what each bit in the low and high interrupt
registers means, but that's not the sort of interrupt I'm getting
spuriously here.

I don't think it's far from working, but I don't know how to advance
from here. Any ideas?



             reply	other threads:[~2011-07-09  4:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-09  4:38 Jared Jennings [this message]
     [not found] <CACXGR2Q0bf3dkWGrVT=rkqYrNERe5xdzPuh836CJsbo84A6jVA@mail.gmail.c>
2011-07-09 15:55 ` erik quanstrom
2011-07-09 20:59   ` Jared Jennings
2011-07-09 22:33     ` Jared Jennings
2011-07-10  0:32       ` Jared Jennings
     [not found]       ` <CACXGR2QsfEkHkfUVu8df+4KeosOLOSVMuAE99ohb-tzY+x9kUQ@mail.gmail.c>
2011-07-10  0:49         ` erik quanstrom
     [not found]     ` <CACXGR2SCEkWaqEPRZqe7tLgDni6BiEc09MVC-v8puJtUPO7iVQ@mail.gmail.c>
2011-07-09 22:40       ` erik quanstrom
2011-07-12 10:55         ` Ethan Grammatikidis
2011-07-12 15:32           ` erik quanstrom
2011-07-12 15:41             ` Ethan Grammatikidis
2011-07-12 15:49             ` ron minnich
     [not found]             ` <CAP6exYJ+4HE4K=axuNcjgiocJKnGy8Kk4V+xjRtf_MO2djzytw@mail.gmail.c>
2011-07-12 16:09               ` erik quanstrom
     [not found]   ` <CACXGR2QQx=8dxFbJ0Y6eiS5dTgRA2AjpNvzQZOaVOEgt-MFnsw@mail.gmail.c>
2011-07-09 22:31     ` erik quanstrom

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='CACXGR2Q0bf3dkWGrVT=rkqYrNERe5xdzPuh836CJsbo84A6jVA@mail.gmail.com' \
    --to=jjenning@gmail.com \
    --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).