mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.10-rc1 broke apmd
Date: Mon, 29 Nov 2004 21:40:37 +0100	[thread overview]
Message-ID: <20041129204037.GA3867@elf.ucw.cz> (raw)
In-Reply-To: <16811.11073.511847.968733@alkaid.it.uu.se>

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.

You may workaround it be sleep 1 before hwclock --hctosys, I
guess. But debugging it would be even better :-). Do we freeze
processes during apm suspend? If not, we should...
								Pavel
-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!

      reply	other threads:[~2004-11-29 20:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-29 11:38 Mikael Pettersson
2004-11-29 12:53 ` Pavel Machek
2004-11-29 13:59   ` Mikael Pettersson
2004-11-29 20:40     ` Pavel Machek [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=20041129204037.GA3867@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@csd.uu.se \
    /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

all inboxes | Powered by JetHome®