From: "Rusty Lynch" <rusty@linux.co.intel.com>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>,
"Benoit GRANGE" <Benoit.GRANGE@fr.tiscali.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: REÂ : Clock is suddently ticking too fast ! [Kernel2.4.19-pre10-ac2, Intel]
Date: Tue, 26 Nov 2002 15:30:08 -0800 [thread overview]
Message-ID: <010201c295a3$c24d5110$94d40a0a@amr.corp.intel.com> (raw)
In-Reply-To: <1038354638.2534.76.camel@irongate.swansea.linux.org.uk>
> On Tue, 2002-11-26 at 20:22, Benoit GRANGE wrote:
> > Alan Said:
> > > Does this stop if you boot with "noapic"
> > I will try, but the clock frenzy happens only once every full moon...
> > it won't be easy to tell.
> > By the way, can you refer me to some nice documents explaining what is
apic ?
> > Regards,
> > Benoit Grange
>
There is also the "Multiprocessor Specification" that talks about APIC.
You can get to the document from:
http://www.intel.com/design/pentium/datashts/242016.htm
> Old IBM PC has PIC (peripheral interrupt controller) - does the 16 IRQ
> lines and attaches them to the CPU
>
> Modern PC also as APIC (advanced peripheral interrupt controller) which
> is in two parts - locsl apic is on the CPU, and talks over a link to one
> or more io-apics that attach to the devices on the bus
>
> "noapic" says to run the box like an old IBM PC
>
> -
> 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 prev parent reply other threads:[~2002-11-26 23:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8B5E8461FFB6B44F85E3504A81AF3D9117616C@frparex01.fr.tiscali.com>
2002-11-26 23:50 ` RE " Alan Cox
2002-11-26 23:30 ` Rusty Lynch [this message]
[not found] <r1_1038354638.2534.76.camel@irongate.swansea.linux.org.uk>
2002-11-28 13:24 ` Bill Davidsen
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='010201c295a3$c24d5110$94d40a0a@amr.corp.intel.com' \
--to=rusty@linux.co.intel.com \
--cc=Benoit.GRANGE@fr.tiscali.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.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®