9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fossil server crashing
Date: Tue,  3 Jun 2003 10:01:46 +0200	[thread overview]
Message-ID: <e996345c68ba6f52adad550991fecf84@plan9.escet.urjc.es> (raw)
In-Reply-To: <20030603032923.GA2474@thefrayedknot.armory.com>

[-- Attachment #1: Type: text/plain, Size: 506 bytes --]

Do you have your kernel sources uptodate wrt sources?
Long ago there was a problem with the scheduler that allowed fossil
to eat the cpu (because of a sleep(0) IIRC).

I also run a fossil updated from sources and it runs just fine.
Have you double checked diff'ing w/ sources? (I'd check fossil and kernel).

Can you try using a fossil that runs off a different disk? (Or perhaps
using a kfs on the disk and starting a fossil running from a file), just
to see if it's a sd thing (I'm using ide).

[-- Attachment #2: Type: message/rfc822, Size: 1949 bytes --]

From: Andrew <afrayedknot@thefrayedknot.armory.com>
To: 9fans@cse.psu.edu
Subject: [9fans] fossil server crashing
Date: Mon, 2 Jun 2003 20:29:23 -0700
Message-ID: <20030603032923.GA2474@thefrayedknot.armory.com>

As the subject says, my fossil server keeps locking up. It is most easy to
duplicate by running the cpu command from a terminal. The disk activity
light on the main hard drive lights up, and stays lit. If i run cpu from
a drawterm connected to the auth server, to connect to the fossil server,
i get the same results but the cryptic message "msgWrite: delay r Rflush
tag 7" when i hit delete on the window. The 7 is actually a number from
somewhere around 3 to usually 40

Everything, including the fossil server mounts their root off the fossil
drive, which happens to be a scsi on a sd53xxx controller.

Any ideas?

this is mostly a recent thing since i pulled from sources

      parent reply	other threads:[~2003-06-03  8:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-03  3:29 Andrew
2003-06-03  3:41 ` Russ Cox
2003-06-03  3:45   ` Andrew
2003-06-03  8:01 ` Fco.J.Ballesteros [this message]

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=e996345c68ba6f52adad550991fecf84@plan9.escet.urjc.es \
    --to=nemo@plan9.escet.urjc.es \
    --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).