MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16811.11073.511847.968733@alkaid.it.uu.se>
Date: Mon, 29 Nov 2004 14:59:29 +0100
From: Mikael Pettersson <mikpe@csd.uu.se>
To: Pavel Machek <pavel@ucw.cz>
CC: linux-kernel@vger.kernel.org
Subject: Re: 2.6.10-rc1 broke apmd
In-Reply-To: <20041129125313.GB3291@elf.ucw.cz>
References: <200411291138.iATBcBiR007342@harpo.it.uu.se>
	<20041129125313.GB3291@elf.ucw.cz>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1223
Lines: 29

Pavel Machek writes:
 > Hi!
 > 
 > > Starting with 2.6.10-rc1, date and time on my old APM-based
 > > laptop is messed up after a resume. Specifically, Emacs and
 > > xclock both make a huge forward leap and then stop updating
 > > their current time displays.
 > > 
 > > The cause is the "jiffies += sleep_length * HZ;" addition
 > > to arch/i386/kernel/time.c:time_resume() which is in conflict
 > > with the hwlock --hctosys that the APM daemon normally does
 > > at resume.
 > 
 > I do not understand why they interfere... time_resume should fix
 > system time, then userland sets it to the right value, again. Unless
 > these two happen in paralel (they should not), nothing bad should happen.
 > 
 > Can you try to suspend, wait, launch hwclock --hctosys manually?

I disabled apmd's automatic hwlock --hctosys and ran it manually
after resume + 5 seconds: no problem. I suspect that apmd runs
really early at resume and that's why it interferes with time_resume.

/Mikael
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/