public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Markus Hofmann <markus@gofurther.de>
To: john stultz <johnstul@us.ibm.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.2 - System clock runs too fast
Date: Tue, 2 Mar 2004 15:15:25 +0100	[thread overview]
Message-ID: <200403021515.25751.markus@gofurther.de> (raw)
In-Reply-To: <1077568263.19860.85.camel@cog.beaverton.ibm.com>

Hello John

Now I've had time to check and test the things you told me.

- DMA was enabled for the disk.
- cpu freq was disabled in the BIOS.
- and I think it depends on the laptop's power state. once the clock runs 
normal with power supply and ac. But now I can't relicate this.

regards
Markus

Am Montag, 23. Februar 2004 21:31 schrieb john stultz:
> On Mon, 2004-02-23 at 05:13, Markus Hofmann wrote:
> > After a recompiling kernel my system clock runs now again too slow. Your
> > patch helps with a fast running clock but not with a slow clock. Do you
> > have an idea what to do now?!?
>
> Things to check:
> o Is DMA enabled for the disks on your system
> 	run "/sbin/hdparm /dev/hdX" to see
> o Does the problem show up depending on the laptop's power state?
> 	(ie: does plugging it in or unplugging it change the issue)
> o Does disabling cpu freq change in the BIOS affect anything?
>
> thanks
> -john

      reply	other threads:[~2004-03-02 14:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-10 12:32 2.6.2 - System clock runs too fast Markus Hofmann
2004-02-10 19:48 ` john stultz
2004-02-11  9:07   ` Markus Hofmann
2004-02-11 18:36     ` john stultz
2004-02-20 12:13       ` Markus Hofmann
2004-02-23 13:13       ` Markus Hofmann
2004-02-23 20:31         ` john stultz
2004-03-02 14:15           ` Markus Hofmann [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=200403021515.25751.markus@gofurther.de \
    --to=markus@gofurther.de \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    /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