WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Re: [Xen-ia64-devel] [PATCH 0/3] IA64: add cpufreq suppo

On Thu, Oct 09, 2008 at 10:34:00AM +0800, Yu, Ke wrote:
> Hi Isaku,
> 
> Thanks for tesing. Please see my comments below.
> 
> Isaku Yamahata wrote:
> > Hi Yu. I tested it and have some comments.
> >
> > - When I run xenpm, xen panics
> >   It panics at 0xf40000000406ba91 =
> >   xen-unstable.hg/xen/drivers/acpi/pmstat.c:98 (addr2line told)
> >   It looks like pxpt->u.pt[pxpt->u.cur] wasn't allocated yet resulting
> >   in NULL pointer reference.
> 
> As Guanquan replied, this is a separate issue of xenpm logic, he will post 
> another patch to fix this issue.

Great.


> > - From the boot message, ondemand governor fails to load.
> >   I'm not sure this error is expected because of my hardware.
> >   I guess this error case haven't been tested and that it caused
> >   the above panic.
> 
> >From the boot message, the BIOS _PSS information is totally messed up. E.g. 
> >1048575us latency is wrong which cause ondemand driver fail to load, also 
> >1048575MHz freq is obviously not correct. There are several possible reasons 
> >of this:
> - BIOS itself is not correct
> - Dom0 ACPICA parsing logic is not correct.
> 
> If the native linux (e.g RHEL5) works, then I tend to believe this is dut to 
> the second reason. The dom0 kernel is bit old and bunch of ACPICA fixes in 
> mainline kernel are not included in dom0. In my case, I also find the _PSS 
> parsing result in my Hitachi itanium 2 box is not correct. This issue is 
> fixed after I pulling two patch from mainline kernel (changeset 677 and 678 
> in http://xenbits.xensource.com/linux-2.6.18-xen.hg)
> 
> Anyway, this is a separate issue. we will try to find other ia64 box to see 
> if this issue can be reproduced and then fixed.
> 
> BTW, is it possible to check in these patch first?

Yes, I'll try them.

I attached DSDT.dsl which I extracted from my tiger4.
It seems that wrong acpi cpuid is used.
acpi cpu id which was passed should be one of
0x00,0x01,0x04,0x05,0x08,0x09,0x0C,0x0D.
But unintended value is used.
-- 
yamahata

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel