From: Christer Weinigel <wingel@acolyte.hack.org>
To: linux-kernel@vger.kernel.org
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Hiroshi MIURA <miura@da-cha.org>,
anders.wallin@mvista.com
Subject: NatSemi SC1200 timer problems
Date: Thu, 21 Mar 2002 17:23:12 +0100 (CET) [thread overview]
Message-ID: <20020321162312.7241DF5B@acolyte.hack.org> (raw)
Hi,
I'm seeing some very strange problems with a NatSemi SC1200 based
system. The problems is that the code to read the PIT counter
sometimes returns the bytes swapped:
outb(0, 0x43);
count = inb(0x40);
count |= inb(0x40) << 8;
This sometimes gives 0x822e instead of 0x2e82 that is reasonable. I
first thought this was a bug in another driver, but sometimes the
counter read from the timer would be 0xd5dd and that value should be
impossible to get, so I'm starting to suspect the hardware.
Besides this, I have a report that the TSC sometimes jumps ahead, so
that the reported time of day will be about 7 seconds more than it
should be.
Does any of this sound familar?
Hiroshi MIURA <miura@da-cha.org> has a patch for a Cyrix CX5520 i8254
timer bug on his web page, but I have been unable to find any
information on the net on what the bug actually is. Could you tell me
a bit more about it? I'm trying to figure out if it has reappeared in
the SC1200 or if this is a completely new problem.
Alan, i think did a patch to disable the TSC on the MediaGX and I have
seen posts by you where you say about the MediaGX that "It reports a
TSC but the TSC is unreliable at least in certain strange
circumstances". Do you refer to the TSC being stopped or turned off
on halt or suspend or is it a completely different problem? Could you
please tell me what kind of problems you saw?
Regards,
Christer (pulling his hair in confusion)
--
"Just how much can I get away with and still go to heaven?"
next reply other threads:[~2002-03-21 16:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-21 16:23 Christer Weinigel [this message]
2002-03-21 16:50 ` Alan Cox
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=20020321162312.7241DF5B@acolyte.hack.org \
--to=wingel@acolyte.hack.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=anders.wallin@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miura@da-cha.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
all inboxes | Powered by JetHome®