From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Re: [Xen-users] pvops dom0 kernel: Unable to locate IOAPIC for GSI 2 and 9 Date: Tue, 23 Mar 2010 10:00:48 -0700 Message-ID: <4BA8F3C0.5040603@goop.org> References: <20100316220353.GC1878@reaktio.net> <9f975f341003181323r14e7843dt6098b86abae9f0c6@mail.gmail.com> <20100318212700.GZ1878@reaktio.net> <201003231623.30700.tobias.geiger@vido.info> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <201003231623.30700.tobias.geiger@vido.info> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Tobias Geiger Cc: xen-devel@lists.xensource.com, kishore kumar , xen-users@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 03/23/2010 08:23 AM, Tobias Geiger wrote: > Hi, > > after having almost no issues with hiccups anymore (HPET was disabled in BIOS > - my fault) i also notices the GSI ERRORs regarding GSI 2 and 9 in my dmesg > > xen dmesg: http://pastebin.ca/1850372 > dom0 dmesg: http://pastebin.ca/1850373 > > is this somehow related with the fact that "xenpm get-cpufreq-states" results > in no output at all, and "xenpm set-scaling-governor ondemand" results in: > > [CPU0] failed to set governor name > [CPU1] failed to set governor name > [CPU2] failed to set governor name > [CPU3] failed to set governor name > [CPU4] failed to set governor name > [CPU5] failed to set governor name > [CPU6] failed to set governor name > [CPU7] failed to set governor name > > - i know this (cpufreq) already worked with a 2.6.33 "xenified" dom0-Kernel... > The 2.6.32 based dom0 trees don't have power management yet. J