From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: "Brian J. Murrell" <brian@interlinx.bc.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: local apic timer ints not working with vmware: nolocala
Date: Wed, 28 May 2003 11:56:29 +0200 [thread overview]
Message-ID: <2C8EEAE5E5C@vcnet.vc.cvut.cz> (raw)
On 27 May 03 at 20:53, Brian J. Murrell wrote:
> Using a distribution (Mandrake's Cooker) patched kernel, I am unable to
> successfully boot at 2.4.20ish kernel on VMware 2.0.4 build 1142. The
> problem seems to be with using local apic timer interrupts. The last few
> lines of the boot sequence before the kernel hangs are (copied by hand, so
> please excuse typos):
>
> Using local APIC timer interrupts.
> calibrating APIC timer ...
> ..... CPU clock speed is 1658.7651 MHz.
> ..... host bus clock speed is 0.0000 MHz.
> cpu: 0, clocks: 0, slice: 0
>
> I do know that I could simply build a kernel with the CONFIG_X86_UP_APIC
> to work around this problem, but that means a "special" kernel just for
> VMware and also means not being able to use vendor supplied kernels, or
> vendor supplied boot media (i.e. CD-ROMs).
Just get VMware 3 or 4 - they (properly) emulate APIC timer and you'll
get information that host bus is running at 66.xxxx MHz. With VMware 2
you have to boot with noapic.
Petr Vandrovec
next reply other threads:[~2003-05-28 9:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-28 9:56 Petr Vandrovec [this message]
2003-05-28 17:34 ` local apic timer ints not working with vmware: nolocalapic brian
2003-05-28 17:42 ` Zwane Mwaikambo
2003-05-30 22:14 ` Brian J. Murrell
2003-05-30 23:23 ` Zwane Mwaikambo
2003-05-31 3:38 ` Brian J. Murrell
2003-05-31 4:41 ` Brian J. Murrell
2003-05-31 6:50 ` Zwane Mwaikambo
2003-05-31 15:21 ` Brian J. Murrell
2003-06-03 11:47 ` Maciej W. Rozycki
2003-06-05 3:04 ` Zwane Mwaikambo
2003-06-05 12:19 ` Maciej W. Rozycki
2003-06-05 17:54 ` Zwane Mwaikambo
2003-06-09 11:57 ` Maciej W. Rozycki
2003-06-10 1:17 ` Zwane Mwaikambo
2003-06-10 11:20 ` Maciej W. Rozycki
2003-05-31 7:03 ` Zwane Mwaikambo
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=2C8EEAE5E5C@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=brian@interlinx.bc.ca \
--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