From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: george anzinger <george@mvista.com>
Cc: Linus Torvalds <torvalds@transmeta.com>,
"Nakajima, Jun" <jun.nakajima@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: local APIC may cause XFree86 hang
Date: 14 Nov 2002 14:27:22 +0000 [thread overview]
Message-ID: <1037284042.15996.16.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <3DD35A13.9600BF75@mvista.com>
On Thu, 2002-11-14 at 08:08, george anzinger wrote:
> Linus Torvalds wrote:
> >
> > On Wed, 13 Nov 2002, Nakajima, Jun wrote:
> > >
> > > The one instance I saw was that the BIOS was reading 8254 in a tight loop
> > > for a calibration purpose, and it was assuming the time proceeded in a
> > > constant speed, to exit the loop. In other words, it never assumed it could
> > > get interrupts. To vm86, interrupts are invisible, but they have impacts on
> > > the actual speed.
> >
> > That sound slike a perfectly ok thing to do - apart from the hw latching
> > which might confuse the kernel.
>
> Yes, it has been speculated that some "time warps" were
> caused by "someone" reading only one of the two bytes from
> the PIT. It puts the following reads out of sync. If this
> was caused by an interrupt (which, of course, is where the
> PIT is read by the kernel) between two reads, it could well
> cause the "time warps" that have been observed.
The 2.5 kernel also has another bug in the way it handles the latches
reading the exact count value they wrap on. Some chips expose that value
momentarily before resetting
next prev parent reply other threads:[~2002-11-14 13:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-14 1:16 local APIC may cause XFree86 hang Nakajima, Jun
2002-11-14 1:38 ` Linus Torvalds
2002-11-14 8:08 ` george anzinger
2002-11-14 14:27 ` Alan Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-14 0:29 Nakajima, Jun
2002-11-14 0:48 ` Linus Torvalds
2002-11-13 22:29 Mikael Pettersson
2002-11-13 23:19 ` Alan Cox
2002-11-13 23:01 ` Mikael Pettersson
2002-11-13 23:52 ` Linus Torvalds
2002-11-14 7:58 ` Gregoire Favre
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=1037284042.15996.16.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=george@mvista.com \
--cc=jun.nakajima@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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).