From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <9ec71d3874fdd404d8cb37689c588d2f@csplan9.rit.edu>
To: 9fans@9fans.net
Date: Thu, 13 Mar 2008 17:14:26 -0400
From: john@csplan9.rit.edu
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: [9fans] more bitsy stuff
Topicbox-Message-UUID: 788c8a30-ead3-11e9-9d60-3106f5b1d025

So it turns out that I can build a kernel that will boot Axel's old
paqdisk without a problem, but if I use my own kernel with my own
freshly created paqdisk, I get the crash below:


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 c0010d28 c011714c c01171a9

ot procc01170f8=c0010d24 ess diec01170fc=c0070aec d: sys:c0117104=c003afe4  write c0117128=c003b044 on clos

ed pipe c0117140=c003b2a8 pc=0x00c0117144=c0010d24 006c74
c0117148=c003b2ac
c0117150=c006d790

c01171b0=c008d610 c01171b4=c008d3bc c01171bc=c008f200 c01171c8=c0078f94

c01171d4=c008d14c c01171d8=c008e37c c01171dc=c008d510 c01171e0=c008d14c

c01171e8=c008d3f8 c01171f4=c008d3bc c01171fc=c008f200 c0117208=c0078f94

c011721c=c008f6c0 c011723c=c006022c c0117248=c006add0 c0117250=c006add8

c011725c=c006d750 c0117274=c00108f8 c0117280=c00790b8 c0117284=c0079594

c01172ac=c0070fc0 c01172b4=c00108dc c01172c8=c0010418 c01172e8=c0008248

c01172f0=c0079594

it's a wonderful day to die

This makes me think that there was perhaps a change in mkpaqfs along
the line?  To look at the error, it seems that there's something wrong
with my ramdisk image; any insights, anyone?  Who has been maintaining
the bitsy stuff?


John