From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 9pcfs mballoc bug info
Date: Mon, 5 Feb 2001 13:43:02 -0500 [thread overview]
Message-ID: <20010205184310.14DD1199F4@mail.cse.psu.edu> (raw)
For a long time we've had trouble rebooting our fileserver when the network is
busy; 'busy' seems to mean lots of machines try to attach at once. There is a
panic, sometimes it's the mbfree panic, but mostly just a page fault due to a
nil pointer somewhere.
When it happened again last week I looked at some of the faults and through a
tortuous path including a number of leaps of faith started looking at the
locking in getchan and il.c in general, it just looks bogus but I haven't gotten
back to it to convince myself or not.
--jim
next reply other threads:[~2001-02-05 18:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-05 18:43 jmk [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-06 1:01 nemo
2001-02-06 0:45 nemo
2001-02-05 19:06 jmk
2001-02-05 20:23 ` Francisco J Ballesteros
2001-02-05 18:04 nemo
2001-02-05 17:56 ` Boyd Roberts
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=20010205184310.14DD1199F4@mail.cse.psu.edu \
--to=jmk@plan9.bell-labs.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).