From: Jeff Sickel <jas@corpus-callosum.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] arm httpd
Date: Sun, 9 Nov 2014 19:47:17 -0600 [thread overview]
Message-ID: <CF371531-05F5-4EB6-A045-64DFD961B07B@corpus-callosum.com> (raw)
In-Reply-To: <09aeb45d6625e40fba13f98b078d9d8c@ladd.quanstro.net>
> On Nov 9, 2014, at 2:21 PM, erik quanstrom <quanstro@quanstro.net> wrote:
>
> On Sun Nov 9 14:51:37 EST 2014, jas@corpus-callosum.com wrote:
>>
>>> On Nov 9, 2014, at 1:42 PM, erik quanstrom <quanstro@quanstro.net> wrote:
>>>
>>> the aside leads me to believe that there is something wrong with the segment
>>> copy on fork. since the semaphore in question is in the data segment,
>>> i'm going to guess that you're running the labs kernel, and you're hitting the
>>> page caching issue we've seen before. does this happen on an atom kernel?
>>
>> Only happens in the labs ARM kernel. The labs mips and 386 kernels work fine
>> in this situation.
>
> my thinking is that this isn't a defect in the arch-specific bits but rather a timing
> bug. in that case, only manifesting on certain hardware is not diagnostic.
>
> do you have any reason to believe this is not a timing bug? it does fit the pattern
> rarely seen on x86 systems. (actually (cf. the console appliance) there were ways
> to really make x86 systems suffer by forking fast enough on slow hardware.)
Well, sys/src/libc/9sys/time.c did change about the time I started seeing this bug
on my old dreamplug.
-jas
next prev parent reply other threads:[~2014-11-10 1:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-09 15:34 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 [this message]
2014-11-09 20:28 ` Skip Tavakkolian
-- strict thread matches above, loose matches on Subject: below --
2013-11-17 21:54 [9fans] arm & httpd Jeff Sickel
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
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=CF371531-05F5-4EB6-A045-64DFD961B07B@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).