From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] 9atom installation report on Acer C710 Chromebook
Date: Sat, 14 Feb 2015 09:52:30 -0800 [thread overview]
Message-ID: <2c5f91b0d593ba029b2bc1616de4aa6e@brasstown.quanstro.net> (raw)
In-Reply-To: <c4f7c074a94d997a943c58b50f51d8db@brasstown.quanstro.net>
On Sat Feb 14 09:40:55 PST 2015, quanstro@quanstro.net wrote:
> > This morning, I decided to install 9atom. The installation went quite
> > well but towards the end, while it is compiling amd64 executables, I got
> > a panic and a freeze.
> >
> > panic: cpu0: cclose 0xfffffffff01c45f8
> > dumpstack: disabled
> > cpu0: exiting
> > cpu1: exiting
>
for those following along at home, the panic is here
if(c->flag&CFREE)
panic("cclose %#p", getcallerpc(&c));
and called from
acid; src(0xfffffffff01c45f8)
/sys/src/nix/port/chan.c:240
235 return;
236 decref(&npath);
237 free(p->s);
238 for(i=0; i<p->mlen; i++)
239 if(p->mtpt[i])
>240 cclose(p->mtpt[i]);
241 free(p->mtpt);
242 free(p);
243 }
244
245 /*
it would be interesting to know if a second try at installation
also fails in the same way. if it does not, then it will look a lot
like a race in chan.c. if it fails in the same way, we really can't
infer anything.
- erik
next prev parent reply other threads:[~2015-02-14 17:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-14 2:42 Ramakrishnan Muthukrishnan
2015-02-14 17:41 ` erik quanstrom
2015-02-14 17:52 ` erik quanstrom [this message]
2015-02-15 6:13 ` Ramakrishnan Muthukrishnan
2015-02-23 4:06 ` Ramakrishnan Muthukrishnan
2015-02-23 14:09 ` erik quanstrom
2015-02-24 4:20 ` Ramakrishnan Muthukrishnan
2015-02-28 17:20 ` Ramakrishnan Muthukrishnan
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=2c5f91b0d593ba029b2bc1616de4aa6e@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--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).