From: Chris Wilson <chris@jakdaw.org>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: linux-kernel@vger.kernel.org,
Zwane Mwaikambo <zwane@linux.realnet.co.sz>
Subject: Re: P4/i845 Strange clock drifting
Date: Mon, 8 Apr 2002 14:49:23 +0100 [thread overview]
Message-ID: <20020408144923.4566d3fc.chris@jakdaw.org> (raw)
In-Reply-To: <200204051752.TAA02715@harpo.it.uu.se>
Hi Mikael,
I've now applied your patch so that APIC's get enabled even though the
bios has disabled them.
I really should have saved the dmi messages to another machine when the
machine first came up as it appears to have crashed now :(
The machine was completely idle other than for an ssh session running
ntpdate every ten minutes (my original problem is that the clock appears
to stop/slow down periodically).
>From memory the dmi messages just had a bios date, and the mobo model
(Supermicro P4SBE). Once I've got the NOC to reboot the system I'll switch
it back to a kernel that doesn't attempt to enable the APIC and send you
the full dmi strings.
> This should work (and is known to work on many P6 and K7 boards),
> but your BIOS may have problems with the local APIC.
> - does apm --suspend work? does the resume afterwards work?
I don't have APM support compiled in and will have disabled anything power
management related in the BIOS setup.
I guess that I'm not going to get APIC going on this system then - does
anyone have any other suggestions on what to try next to debug the clock
drift problem? Short of dropping the server into the nearest skip....
Are the APIC thing and the clock thing likely to be related??
Cheers,
Chris
next prev parent reply other threads:[~2002-04-08 13:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-05 17:52 Mikael Pettersson
2002-04-08 13:49 ` Chris Wilson [this message]
2002-04-09 9:33 ` Chris Wilson
-- strict thread matches above, loose matches on Subject: below --
2002-04-03 14:52 "Fernández-Victorio Arévalo, Gonzalo"
2002-04-03 14:10 Chris Wilson
2002-04-03 14:17 ` Zwane Mwaikambo
2002-04-05 12:28 ` Chris Wilson
2002-04-05 14:31 ` Zwane Mwaikambo
2002-04-05 15:01 ` Chris Wilson
2002-04-05 16:40 ` Maciej W. Rozycki
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=20020408144923.4566d3fc.chris@jakdaw.org \
--to=chris@jakdaw.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
--cc=zwane@linux.realnet.co.sz \
/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®