From: erik quanstrom <quanstro@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Fossil errors
Date: Wed, 21 Mar 2007 11:47:21 -0400 [thread overview]
Message-ID: <5004b4c047c1935649ded179c20abc09@coraid.com> (raw)
In-Reply-To: <9ab217670703210629u6668b468h897eaa6bc17534f3@mail.gmail.com>
it means that lock() (/sys/src/9/port/taslock.c:/^lock) is looping way too much
in rendezvous. 0x37a34 is in rendezvous.s.
i don't know fossil or venti very well. it would be hard to say what is wrong with
the threading here without some serious groveling. my wild guess would be that
there are three processes (21 26 23) at the same rendezvous point at the same time.
rendezvous works for two processes.
i wonder why libventi doesn't use the thread library?
- erik
On Wed Mar 21 09:29:52 EDT 2007, devon.odell@gmail.com wrote:
> I installed Inferno on my FreeBSD machine so that I could copy my MP3s
> over to the Plan 9 fileserver. I left last night around midnight, and
> when coming in again this morning, I notice a few kernel messages:
>
> lock 0xf0a685c8 loop key 0xdeaddead pc 0xf01c9af2 held by pc 0xf01c9af2 proc 21
> 26: fossil pc f01ca23d dbgpc 37a34 Rendez (Running) ut 959 st 4926
> bss 703000 qpc 0 nl 0 nd 0 lpc f01c1f5d pri 4
> 21: fossil pc f01bda3e dbgpc 37a34 Rendez (Ready) ut 89555 st 244 bss
> 703000 qpc 0 nl 1 nd 0 lpc f01bd877 pri 3
> lock 0xf0a685c8 loop key 0xdeaddead pc 0xf01c9af2 held by pc 0xf01c9af2 proc 21
> 23: fossil pc f01ca20f dbgpc 37a34 Rendez (Running) ut 352 676 bss
> 703000 qpc 0 nl 0 nd 0 lpc f01c1f5d pri 4
> 21: fossil pc f01xdxxx (unreadable due to terminals) qpc 0 nl 1 nd 0
> lpc f01bd877 pri 3
>
> Not sure what this means. I guess typically 0xdeaddead-like stuff is
> used to signify use of memory after a free, but I'm kind of unsure.
>
> Also, it looks like it decided to randomly stop copying somewhere in
> the middle of my MP3 stream.
>
> *shrugs*
>
> --dho
next prev parent reply other threads:[~2007-03-21 15:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-21 13:29 Devon H. O'Dell
2007-03-21 15:47 ` erik quanstrom [this message]
2007-03-21 15:53 ` Devon H. O'Dell
2007-03-21 15:59 ` erik quanstrom
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=5004b4c047c1935649ded179c20abc09@coraid.com \
--to=quanstro@coraid.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).