From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tomas Kouba Subject: Re: Bad clock ticking in xen0 Date: Thu, 29 Dec 2005 20:36:34 +0100 Message-ID: <43B43AC2.9060807@jikos.cz> References: <43AFC5BC.2000708@jikos.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Keir Fraser wrote: > > On 26 Dec 2005, at 10:28, Tomas Kouba wrote: > >> Attached. >> The lines >> >> (XEN) Local APIC disabled by BIOS -- you can enable it with "lapic" >> (XEN) Local APIC not detected. Using dummy APIC emulation >> >> are a bit strange for me. The BIOS is quite simple PheonixBIOS with >> no options regarding APIC. >> lapic kernel parameter was *surely* used > > > If lapic had been passed on Xen's command line then you would not have > got the first line from Xen (the one that ends "...you can enable it > with "lapic""). It seemed strange to me too. But: $ xm dmesg | grep lapic (XEN) Local APIC disabled by BIOS -- you can enable it with "lapic" $ cat /proc/cmdline lapic root=/dev/hda6 ro console=tty1 Am I missing something? Btw. I have tried live CDs on the notebook and 2.0.6 works fine (clock runs ok) but 3.0 is again too fast. -- Tomas Kouba