From: gabidiaz@gmail.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] venti woes with brand new install
Date: Sat, 8 Sep 2007 16:27:39 +0200 [thread overview]
Message-ID: <ed7ed23769668ac851d859563d0e33b1@cid.9grid.es> (raw)
In-Reply-To: <01405c4bddab6004f67d7e604d29ba72@quanstro.net>
hello
here is what you suggested:
cid% venti/venti -r -L -d -s -c /dev/sdC0/arenas -a 'tcp!127.1!59999' -h 'tcp!127.1!8009'
T+0.0000 venti: conf...
corrupt zblock: 18042e0 b->_size=8192
64 65 66 67 68 69 6a 6b
6c 6d 6e 6f 70 71 72 73
74 75 76 6b 00 00 00 00
20 00 00 cd 22 80 01 b8
venti 1400: suicide: sys: trap: fault read addr=0x0 pc=0x0002120d
cid% acid 1400
/proc/1400/text:386 plan 9 executable
/sys/lib/acid/port
/sys/lib/acid/386
acid: lstk();
abort()+0x0 /sys/src/libc/9sys/abort.c:6
freezblock(b=0x18042e0)+0xf8 /sys/src/cmd/venti/srv/zblock.c:72
s=0x18042e5
fmt=0x4d292
i=0x20
freeifile(f=0xa4960)+0x12 /sys/src/cmd/venti/srv/ifile.c:67
runconfig(file=0xdfffef92,config=0xa49b4)+0x8e /sys/src/cmd/venti/srv/config.c:188
f=0xdfffef92
ok=0x0
line=0x0
s=0x180232e
flds=0x180232e
i=0x2
sv=0x18021d8
av=0x18021f8
initventi(file=0xdfffef92,conf=0xa49b4)+0x3f /sys/src/cmd/venti/srv/config.c:21
threadmain(argv=0xdfffef6c,argc=0x0)+0x139 /sys/src/cmd/venti/srv/venti.c:113
vaddr=0xdfffefa6
haddr=0xdfffefb9
configfile=0xdfffef92
webroot=0x0
mem=0x0
icmem=0x0
bcmem=0x0
_argc=0xfefe0068
_args=0x4e4bc
config=0x1802218
mainlauncher(arg=0x63fd8)+0x18 /sys/src/libthread/main.c:58
launcher386(arg=0x63fd8,f=0x2f8d5)+0x10 /sys/src/libthread/386.c:10
0xfefefefe ?file?:0
acid: acid: *(0x18042e5\s)
acid: *(0x180232e\s)
icmem
acid:
the config file content is:
index main
isect /dev/sdC0/isect
arenas /dev/sdC0/arenas
bloom /dev/sdC0/bloom
mem 10M
bcmem 20M
icmem 30M
with the final \n
thanks
gabi
PD: you function compiled fine :)
> as a salute to the days of typing in machine code from smalltalk
> magazine. (wasted youth!) here is the backtrace complete with
> errors introduced by a faulty connection between the image and
> keyboard.
>
> abort+0x0 /sys/src/libc/9sys/abort.c:6
> freezblock(b=0x17d1f90)+0x38 /sys/src/cmd/venti/srv/zblock.c:63
> freeifile(f=0xa4918)+0x12 /sys/src/cmd/venti/srv/ifile.c:67
> runconfig(file=0xdfffef92,config=0xa496c)+0x8e /sys/src/cmd/venti/srv/config.c:188
> f=0xdfffef92
> ok=0x0
> line=0x0
> s=0x17cff8e
> flds=0x17cff8e
> i=0x2
> sv-0x17cfe68
> av=0x17cfe88
> initventi(file=0xdfffef92,conf=0xa496c)+0x3f /sys/src/cmd/venti/srv/config.c:21
> threadmain(argv=0xdfffef70,argc=0x0)+0x139) /sys/src/cmd/venti/srv/venti.c:113
> vaddr=0xdfffefa6
> haddr=0xdfffefb9
> configfile=0xdfffef92
> webroot=0x0
> mem=0x0
> icmem=0x0
> bcmem=0x0
> _argc=0xfefe0068
> _args-0x4e474
> config=0x17cfea8
> [...]
>
> could you send the output of venti/config? and what does acid
> say to this
>
> acid: *(0x17cff8e\s)
>
> you might also get more information by inspecting how zmagic
> is corrupt, e.g. replace freezblock with something like this.
> (may or may not compile.)
>
> void
> freezblock(ZBlock *b)
> {
> if(b){
> if(memcmp(b->data+b->_size, zmagic, OverflowCheck) != 0){
> int i;
> uchar *s;
> char *fmt;
>
> s = (uchar*)(b->data+b->_size);
> fmt = " %.2x %.2x %.2x %.2x %.2x %.2x %.2x %.2x\n";
>
> fprint(2, "corrupt zblock: %p b->_size=%d", b, b->_size);
> for(i = 0; i < OverflowCheck; i += 8, s += 8)
> fprint(2, fmt, s[0], s[1], s[2], s[3], s[4], s[5], s[6], s[7]);
> abort();
> }
> memset(b->data+b->_size, 0, OverflowCheck);
> free(b->free);
> }
> }
>
> - erik
>
>> Hi everyone!
>> I'm trying to configure a new cpu+auth server using the instructions in the wiki, and I've crossed a problem with venti.
>> Here is what I did:
>> 1, downloaded the sept. 6th iso from plan9 download site
>> 2, installed a fossil+venti system (default setup)
>> 3, followed the wiki instructions to set up a cpu+auth server (compiled my own 9pccpuf kernel with default config)
>> then I rebooted my computer (luckily set up a menu with options to start the old terminal kernel),
>> and got venti suicide, here is a screenshot of the crash: http://jsoros.free.fr/CIMG5212.JPG , after this the computer reboots. We did a little debugging with cinap on irc, here is how we did it:
>> 1, copy /386/bin/venti/venti to 9fat
>> 2, boot into the live-cd
>> 3, run /n/9fat/venti -s -c /dev/sdC0/arenas -a 'tcp!127.1!17034' -h 'tcp!127.1!8000'
>> it suicides here too
>> 4, run acid on the crashed venti, here is the output of acid: http://jsoros.free.fr/CIMG5213.JPG
>> Thanks for any insite on what could be wrong and what I could do to fix it.
>>
>> Regards
>> John
next prev parent reply other threads:[~2007-09-08 14:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-08 12:09 John Soros
2007-09-08 13:43 ` erik quanstrom
2007-09-08 14:27 ` gabidiaz [this message]
2007-09-09 12:01 ` John Soros
2007-09-09 12:05 ` erik quanstrom
2007-09-09 12:57 ` John Soros
2007-09-09 13:08 ` Uriel
2007-09-09 13:13 ` erik quanstrom
2007-09-09 13:22 ` Uriel
2007-09-10 8:12 ` SHRIZZA
2007-09-10 8:39 ` Uriel
2007-09-08 15:27 cinap_lenrek
2007-09-08 16:49 ` erik quanstrom
2007-09-08 17:07 ` cinap_lenrek
2007-09-08 19:08 ` cinap_lenrek
2007-09-08 21:45 ` John Soros
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=ed7ed23769668ac851d859563d0e33b1@cid.9grid.es \
--to=gabidiaz@gmail.com \
--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).