From: john@csplan9.rit.edu
To: 9fans@cse.psu.edu
Subject: [9fans] bitsy boot problems
Date: Fri, 7 Mar 2008 11:18:58 -0500 [thread overview]
Message-ID: <5ecf9fabb34203765365819c226a004f@csplan9.rit.edu> (raw)
I just found two bitsies yesterday, a 3630 and a 3670. I thought I'd try installing on the 3670 because the other one has a useful Linux install on it already. Anyway, both had Linux bootloaders installed already, so I built a kernel and paqdisk, uploaded them, and tried booting. Here's what I get; can anyone help figure out what's wrong here?
206 MHZ ARM, ver 1/part b11/step 8
64M memory: 27M kernel data, 37M user, 226M swap
root is from (paq)[paq]:
paq...paqfs: sysfatal reading block: /dev/flash/ramdisk:
version...panic: boot process died: sys: write on closed pipe pc=0x00006c74
panic: boktrace /kernel/path c0010d6c c011714c c01171a9
ot procc01170f8=c0010d68 ess diec01170fc=c0071110 d: sys:c0117104=c003afdc write c0117128=c003b03c on clos
ed pipe c0117140=c003b2a0 pc=0x00c0117144=c0010d68 006c74c0117148=c003b2a4
c0117150=c006ddcc
c01171b0=c008d9d4 c01171b4=c008d780 c01171bc=c008f5c4 c01171c8=c00795a4
c01171d4=c008d510 c01171d8=c008e740 c01171dc=c008d8d4 c01171e0=c008d510
c01171e8=c008d7bc c01171f4=c008d780 c01171fc=c008f5c4 c0117208=c00795a4
c011721c=c008fa84 c011723c=c00601f8 c0117248=c006b3e0 c0117250=c006b3e8
c011725c=c006dd8c c0117274=c001093c c0117280=c00796c8 c0117284=c0079ba4
c01172ac=c00715e4 c01172b4=c0010920 c01172c8=c001045c c01172e8=c0008248
c01172f0=c0079ba4
it's a wonderful day to die
next reply other threads:[~2008-03-07 16:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-07 16:18 john [this message]
2008-03-07 17:06 ` ron minnich
[not found] <7fdd354d85c5e3ab085996cf0471cba9@csplan9.rit.edu>
2008-03-07 23:31 ` john
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=5ecf9fabb34203765365819c226a004f@csplan9.rit.edu \
--to=john@csplan9.rit.edu \
--cc=9fans@cse.psu.edu \
/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).