9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: nemo@gsyc.escet.urjc.es
To: 9fans@cse.psu.edu
Subject: [9fans] flashfs timeout after a time jump
Date: Wed, 11 Jul 2001 19:01:04 +0200	[thread overview]
Message-ID: <20010711164653.91F7C199E4@mail.cse.psu.edu> (raw)

Hi,

	If I echo to /dev/time and make the time jump into the future I
get a broken channel message as soon as I try to write to the flashfs;
i.e. I've to reboot.

Reads seems to be ok though. Any clue or any pointer where to start
looking at it?

AFAIK, the flashfs is not hanging up due to time outs and the kernel
routines still use MACH(0) ticks, not tod.

This happens to me after a resume because I'm now adjusting the bitsy tod
according to the sleeping time; but it also happens if I manually
`echo NNNNN >/dev/time'. Is it just me? Or other bitsies  exhibit
the same behaviour too?

thanks



             reply	other threads:[~2001-07-11 17:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-11 17:01 nemo [this message]
2001-07-11 23:10 ` Boyd Roberts
2001-07-12  8:32 ` Douglas A. Gwyn
2001-07-12  6:49 nemo
2001-07-12  8:59 nemo

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=20010711164653.91F7C199E4@mail.cse.psu.edu \
    --to=nemo@gsyc.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).