From: erik quanstrom <quanstro@quanstro.net>
To: xigh@bouyapop.org, 9fans@9fans.net
Subject: Re: [9fans] crashing 9vx
Date: Sun, 30 May 2010 12:30:05 -0400 [thread overview]
Message-ID: <455a9b599b32a95fdfa5ae79083ae99a@kw.quanstro.net> (raw)
In-Reply-To: <4C028B75.8080701@bouyapop.org>
On Sun May 30 12:00:25 EDT 2010, xigh@bouyapop.org wrote:
> You also have to recompile vx library.
>
> Phil
>
> Brian L. Stuart wrote:
> >> OK, somebody sent a hint that it
> >> might make sense to take the -O3 out
> >> of the make flags. Done.
> >>
> >> Result: I can now get through this command:
> >> hget -v http://plan9.bell-labs.com/plan9/download/plan9.iso.bz2>/tmp/iso.bz2
> >> |[2]aux/statusbar plan9.iso
> >>
> >> without an explosion.
> >>
> >
> > This is weird. I just built 9vx on FreeBSD without
> > the -O3. But instead of being more stable, that
> > one crashed on startup, like Charles reported.
> > Namely:
> >
> > 9vx panic: user fault: signo=11 addr=3850cb67 [useraddr=cb67] read=1 eip=80b973c esp=493ffac0
> > aborting, to dump core.
> >
> > With the -O3, the crashes are rare, and seem to be
> > associated with heavy I/O.
you may be right, but it seems too easy to blame gcc.
a better fit for the facts so far would seem to me that
9vx' locking is broken. the optimization may just put
more pressure on broken locking.
putting a couple of prints in the startup will also change
timing. if you can eliminate or cause a crash by adding
or removing prints, then you can be sure that there is a
locking/timing problem in 9vx. although that doesn't prove
that gcc is blameless, it would be a reasonable assumption.
- erik
next prev parent reply other threads:[~2010-05-30 16:30 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-28 4:10 ron minnich
2010-05-28 6:40 ` Philippe Anel
2010-05-28 8:13 ` Philippe Anel
2010-05-28 8:24 ` Philippe Anel
2010-05-28 15:10 ` ron minnich
2010-05-28 15:15 ` Philippe Anel
2010-05-28 15:24 ` ron minnich
2010-05-28 18:36 ` Charles Forsyth
2010-05-28 19:31 ` Philippe Anel
2010-05-28 20:46 ` ron minnich
2010-05-28 21:00 ` erik quanstrom
2010-05-29 3:39 ` ron minnich
2010-05-29 4:05 ` EBo
2010-05-29 5:13 ` ron minnich
2010-05-29 5:45 ` EBo
2010-05-29 4:09 ` erik quanstrom
2010-05-29 5:10 ` ron minnich
2010-05-30 14:46 ` Brian L. Stuart
2010-05-30 15:52 ` ron minnich
2010-05-30 15:59 ` Philippe Anel
2010-05-30 16:30 ` erik quanstrom [this message]
2010-05-31 1:33 ` Brian L. Stuart
2010-05-30 17:08 ` Bakul Shah
2010-05-31 1:14 ` Brian L. Stuart
2010-05-31 2:01 ` ron minnich
2010-05-31 16:32 ` ron minnich
2010-05-31 17:48 ` jake
2010-05-31 18:16 ` EBo
2010-05-31 20:46 ` Jorden M
2010-06-01 11:14 ` Charles Forsyth
2010-06-02 16:40 ` ron minnich
2010-05-29 5:47 ` EBo
2010-10-28 14:00 yy
2010-10-28 14:47 ` Lucio De Re
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=455a9b599b32a95fdfa5ae79083ae99a@kw.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
--cc=xigh@bouyapop.org \
/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).