From mboxrd@z Thu Jan 1 00:00:00 1970 From: Grant Grundler Subject: Re: [parisc-linux] [PATCH] timer_interrupt and gettimeoffset. Date: Wed, 30 Aug 2006 10:52:11 -0600 Message-ID: <20060830165211.GA3999@colo.lackof.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: parisc-linux To: Joel Soete Return-Path: In-Reply-To: List-Id: parisc-linux developers list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: parisc-linux-bounces@lists.parisc-linux.org On Wed, Aug 30, 2006 at 06:38:19PM +0200, Joel Soete wrote: > > 1. The timer interrupt fires, and 'now' comes after 'next_tick' > mmm (just a thought) what's up if now comes after next_tick but cr16 has > already wrap 1, 2, ... times? Every ~4 seconds a 32-bit cycle counter running 1Ghz will wrap. If it wraps twice between any two interrupts, I think we are already screwed. There is no way to detect that with a 32-bit kernel. My hope is the same bug is visible on 64-bit kernel where we have 30 billion or so seconds before the counter will wrap. > > reported problems. Guy, would you mind patching your kernel with this > > patch and testing again? > > Make sense to me but patch doesn't works for me on b2k 32bit kernel ;-( > it was hanging (no error msg on lcd display) just after "Memory: 262144k > available" then I have to force reboot power off/on cycle. I'll give it a go as well. grant _______________________________________________ parisc-linux mailing list parisc-linux@lists.parisc-linux.org http://lists.parisc-linux.org/mailman/listinfo/parisc-linux