From mboxrd@z Thu Jan  1 00:00:00 1970
To: 9fans@cse.psu.edu
From: nemo@gsyc.escet.urjc.es
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Message-Id: <20010711164653.91F7C199E4@mail.cse.psu.edu>
Subject: [9fans] flashfs timeout after a time jump
Date: Wed, 11 Jul 2001 19:01:04 +0200
Topicbox-Message-UUID: c590280a-eac9-11e9-9e20-41e7f4b1d025

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