From: Jeff Sickel <jas@corpus-callosum.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] arm & httpd
Date: Sun, 17 Nov 2013 15:54:43 -0600 [thread overview]
Message-ID: <71F713A4-13CE-424C-B148-7F0238DB9E57@corpus-callosum.com> (raw)
Has anyone else experienced new builds of the sources arm tree getting hung up with semacquire?
99: httpd pc cac0 dbgpc cac0 Semacquire (Wakeme) ut 1 st 2 bss 168000 qpc 608157d8 nl 0 nd 0 lpc 608758c4 pri 10
acid: lstk()
semacquire()+0xc /sys/src/libc/9syscall/semacquire.s:6
lock(l=0x31208)+0x20 /sys/src/libc/port/lock.c:10
plock()+0x8 /sys/src/libc/port/malloc.c:80
pv=0x31208
poolalloc(p=0x35a24,n=0x2c)+0xc /sys/src/libc/port/pool.c:1223
v=0xd970
mallocz(size=0x24,clr=0x1)+0x18 /sys/src/libc/port/malloc.c:221
v=0x5ffffd39
getnetconninfo(fd=0xffffffff,dir=0x5ffffeec)+0x78 /sys/src/libc/9sys/getnetconninfo.c:59
path=0x0
nci=0xb
spec=0x0
d=0x0
netname=0x28
dolisten(address=0xd16dc)+0x134 /sys/src/cmd/ip/httpd/httpd.c:291
spotchk=0x1
dir=0x74656e2f
ctl=0xa
ndir=0x74656e2f
nctl=0xb
swamped=0x0
nci=0x161c40
data=0x313aa
conn=0x73
scheme=0xd16e6
c=0x38898
t=0x5ffffeb4
ok=0xa284
main(argc=0x0,argv=0x5fffff9c)+0x1c0 /sys/src/cmd/ip/httpd/httpd.c:138
address=0x38846
_argc=0x0
_args=0x0
_main+0x28 /sys/src/libc/arm/main9.s:19
I see this on the second http request, the first completes successfully, and don’t yet know if it’s a dns configuration error or something else.
-jas
next reply other threads:[~2013-11-17 21:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-17 21:54 Jeff Sickel [this message]
2013-11-17 22:04 ` Steve Simon
2013-11-17 22:33 ` Jeff Sickel
2013-11-17 23:40 ` erik quanstrom
2013-11-18 10:12 ` Richard Miller
2013-11-18 14:15 ` erik quanstrom
2014-11-09 15:34 [9fans] arm httpd Jeff Sickel
2014-11-09 19:42 ` erik quanstrom
2014-11-09 19:51 ` Jeff Sickel
2014-11-09 20:21 ` erik quanstrom
2014-11-10 1:47 ` Jeff Sickel
2014-11-09 20:28 ` Skip Tavakkolian
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=71F713A4-13CE-424C-B148-7F0238DB9E57@corpus-callosum.com \
--to=jas@corpus-callosum.com \
--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).