From: "Matt H." <lkml@lpbproductions.com>
To: ross@datscreative.com.au
Cc: linux-kernel@vger.kernel.org
Subject: Re: NForce2, Ross Dickson's timer patch on 2.6.1
Date: Mon, 12 Jan 2004 12:15:11 -0700 [thread overview]
Message-ID: <200401121215.11503.lkml@lpbproductions.com> (raw)
In-Reply-To: <20040112173554.GA792@tesore.local>
Ditto here, using nforce2. I've been up for about a week and a half and my
clock is skew'ed by at least 20 mins .
Matt H.
On Monday 12 January 2004 10:35 am, Jesse Allen wrote:
> Hi Ross,
>
> I have a version of your timer patch (io_apic.c) for kernel 2.6.1. It is
> attached. I have been monitoring a problem with it. It seems that with
> the patch, I gain 1 seconds time over 10 minutes (roughly). So I gain
> about 2-3 mintues a day. I haven't taken exact measurements, but I know it
> ends up about 20 minutes difference after a week. This is not good, which
> would require resetting the time often.
>
> I tried the 2.6.1 kernel without the timer patch. The timer is now back in
> PIC mode, and interrupt 7 has the old noise. Synched the time with my
> watch. At first, I noticed no gain in time over 10 minutes. However the
> next day, I found it gained 1-2 seconds. Now it is about 7 seconds ahead a
> few days later now. This is much better.
>
> So I'm left to thinking, the patch does two things, maybe one thing right,
> and one possibly very wrong:
>
> 1) It does place the timer in APIC mode.
> 2) But the timer seems to be fed extra interrupts, maybe the same that is
> found on irq 7 without the patch (is this possible?)
>
> I remember someone making a comment which might explain the issue:
> http://marc.theaimsgroup.com/?l=linux-kernel&m=107098440019588&w=2
>
> I don't think the patch was much different now than it was then. So I
> think there is something wrong with setting up the timer this way. I don't
> know if you worked something out with Maciej. I don't know much about
> interrupt controller programming so... if maybe you can explain to me
> anything I'm missing. For now I've dropped the patch.
>
>
> Jesse
>
>
> PS: I have run with disconnect on, and without your ack patch since I got
> that surpise BIOS update. No lockups have occurred in the past month,
> since that. So the disconnect problem is a BIOS bug. (Shuttle has not
> responded)
>
> PSS: CC me, I'm not subscribed right now.
next prev parent reply other threads:[~2004-01-12 18:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-12 17:35 NForce2, Ross Dickson's timer patch on 2.6.1 Jesse Allen
2004-01-12 19:08 ` Daniel Drake
2004-01-12 19:15 ` Matt H. [this message]
2004-01-13 16:56 Ross Dickson
2004-01-16 0:22 ` Daniel Drake
2004-01-16 0:02 ` Prakash K. Cheemplavam
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=200401121215.11503.lkml@lpbproductions.com \
--to=lkml@lpbproductions.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ross@datscreative.com.au \
/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;
as well as URLs for NNTP newsgroup(s).