From: Lyndon Nerenberg <lyndon@orthanc.ca>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Too many checkpages() diagnostics ...
Date: Tue, 27 May 2014 13:52:40 -0700 [thread overview]
Message-ID: <B62C213A-BE4E-450F-A62B-F72AF9EAC997@orthanc.ca> (raw)
In-Reply-To: <8f0f35fc0a4976c35bcec0d4ffa1b8b2@proxima.alt.za>
[-- Attachment #1: Type: text/plain, Size: 749 bytes --]
On May 26, 2014, at 11:57 PM, lucio@proxima.alt.za wrote:
> I was more frequent when there was a duplicate entry in
> /lib/ndb/kestell (happens to be the description of my local network),
> it's improved since I fixed that. There may still be some trouble in
> the database, but I could not spot any errors.
For me, ndb/dns rarely trips the diagnostic. In almost every case I've examined, the diagnostic is triggered when something in the process of forking. The rfcmirror/idmirror scripts trip it with all the cp commands they run (although it's rc itself that's breaking). mk blows up when doing the fork/exec of the build recipe commands. I'm trying to collect a set of stack traces to see if I can find a pattern.
--lyndon
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 817 bytes --]
next prev parent reply other threads:[~2014-05-27 20:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 23:14 Lyndon Nerenberg
2014-05-26 23:41 ` Steve Simon
2014-05-26 23:44 ` Lyndon Nerenberg
2014-05-26 23:47 ` Steve Simon
2014-05-27 0:27 ` Lyndon Nerenberg
2014-05-27 13:08 ` Anthony Sorace
2014-05-27 22:56 ` Lyndon Nerenberg
2014-05-27 10:43 ` Charles Forsyth
2014-05-27 6:46 ` lucio
2014-05-27 6:57 ` lucio
2014-05-27 20:52 ` Lyndon Nerenberg [this message]
2014-05-27 13:36 ` 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=B62C213A-BE4E-450F-A62B-F72AF9EAC997@orthanc.ca \
--to=lyndon@orthanc.ca \
--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).