From: "Nakajima, Jun" <jun.nakajima@intel.com>
To: torvalds@transmeta.com
Cc: linux-kernel@vger.kernel.org
Subject: RE: local APIC may cause XFree86 hang
Date: Wed, 13 Nov 2002 16:29:48 -0800 [thread overview]
Message-ID: <F2DBA543B89AD51184B600508B68D4000F866009@fmsmsx103.fm.intel.com> (raw)
Are we disabling vm86 code to access to PIT or PIC? I saw some video ROM
code (either BIOS call or far call) did access PIT, confusing the OS.
Thanks,
Jun
> -----Original Message-----
> From: torvalds@transmeta.com [mailto:torvalds@transmeta.com]
> Sent: Wednesday, November 13, 2002 3:53 PM
> To: linux-kernel@vger.kernel.org
> Subject: Re: local APIC may cause XFree86 hang
>
> In article <15826.53818.621879.661253@kim.it.uu.se>,
> Mikael Pettersson <mikpe@csd.uu.se> wrote:
> >
> >Does XFree86 (its core or particular drivers) use vm86() to
> >invoke, possibly graphics card specific, BIOS code?
> >That would explain the hangs I got. The fix would be to
> >disable the local APIC around vm86()'s BIOS calls, just like
> >we now disable it before APM suspend.
>
> It does.
>
> HOWEVER, vm86() mode is very very different from APM, which uses real
> mode. External interrupts in vm86 mode will not be taken inside vm86
> mode - and disabling the local timer (by disabling the APIC) around a
> vm86 mode is definitely _not_ a good idea, since it would be an instant
> denial-of-service attack on SMP machines (the PIT timer only goes to
> CPU0, so we depend on the local timer to do process timeouts etc on
> other CPUs). The vm86 code might just be looping forever.
>
> In other words, if it is really vm86-related, then
> (a) it's a CPU bug
> (b) we're screwed
>
> I bet it's something else. Possibly just timing-specific (the APIC
> makes interrupts much faster), but also possibly something to do with
> the VGA interrupt (some XFree86 drivers actually use the gfx interrupts
> these days)
>
> Linus
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2002-11-14 0:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-14 0:29 Nakajima, Jun [this message]
2002-11-14 0:48 ` local APIC may cause XFree86 hang Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2002-11-14 1:16 Nakajima, Jun
2002-11-14 1:38 ` Linus Torvalds
2002-11-14 8:08 ` george anzinger
2002-11-14 14:27 ` Alan Cox
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=F2DBA543B89AD51184B600508B68D4000F866009@fmsmsx103.fm.intel.com \
--to=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).