search for: _pss

Hi all! After booting the server I have this message: irq 50: nobody cared (try booting with the "irqpoll" option) Call Trace: <IRQ> [<ffffffff800c17e6>] __report_bad_irq+0x30/0x7d [<ffffffff800c1a19>] note_interrupt+0x1e6/0x227 [<ffffffff800c0f15>] __do_IRQ+0xbd/0x103 [<ffffffff8006e249>] do_IRQ+0x13f/0x14d [<ffffffff8006ca05>]

...2.1 on my AMD Sempron(tm) machine. It runs gentoo 2.6.21 as dom0 and cpu frequency scaling works in dom0. But inside a domU, cpu frequency scaling is not working. By checking the boot log in domU I found that domU is unable to load the powernow driver: "powernow-k8: BIOS error - no PSB or ACPI _PSS objects" I wonder if it is possible to have cpu frequency scaling support inside domUs? -- Vahid _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

...er hand I found some fixes for powernow-k8 to get rid of some messages. I have an AMD64. powerno-k8 works find with non-XEN kernels, but with XEN-kernels I get the error: powernow-k8: Found 1 AMD Athlon(tm) 64 Processor 3400+ processors (version 2.00.00) powernow-k8: BIOS error - no PSB or ACPI _PSS objects This is normally a BIOS error and a BIOS update can fix it, but it works for me with non-XEN kernels, so in my case it can’t be a BIOS problem. So any information is welcome. Thanks! Shade and sweet water! Stephan -- | Stephan Seitz E-Mail: Nur-Ab-Sal@gmx.de | | P...

These two patches provide the neccessary infrastructure changes for the processor-passthru driver [www.spinics.net/lists/linux-acpi/msg34655.html] to properly function. The first one is quite easy - we just modprobe the processor-passthru driver. The second allows it to work under AMD machines by exposing the PM RDMSR to dom0. It has been tested with 2.6.32 kernel as well to make sure it does

I just upgraded my first Xen guest to the latest 5.2 kernel (2.6.18- 92.1.13.el5xen) and got a kernel error on reboot: powernow-k8: BIOS error - no PSB or ACPI _PSS objects No problems seen yet. I would think that the guest should not try to do any powernow stuff at all. Has anyone else noticed this? Kai -- Kai Sch?tzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com

...on my AMD64 for my first time and so far, everything seems to work pretty fine. :-) I tried to enable cpu frequency support. After booting, I get the following message in Dom0-dmesg: powernow-k8: Found 1 AMD Athlon 64 / Opteron processors (version 1.60.0) powernow-k8: BIOS error - no PSB or ACPI _PSS objects I tried to find answers in the mailing-list archive and with Google, but could not find answers. Is there support in Xen? Are there any patches, I can download anywhere? Would be really nice to get an answer Thanks in advance Kind regards Christian N.B.: I am not sure, if this list (...

...er %idle for both cores, but still core0 gets either 100%sy or 50%sy 50%us sporadically. I've also got this in the logs, possibly due to BIOS, and I don't know if it is related, I've seen it with 6.2 too. Jul 11 20:44:57 app1 kernel: [Firmware Bug]: powernow-k8: No compatible ACPI _PSS objects found. Jul 11 20:44:57 app1 kernel: [Firmware Bug]: powernow-k8: Try again with latest BIOS. Any ideas what the possible cause could be or what can I do to figure this out? It's a rented server so I don't have the ability to toy with the BIOS. Thanks. -- .oO V Oo.

...n my AMD64 for my first time and so far, everything seems to work pretty fine. :-) I tried to enable cpu frequency support. After booting, I get the following message in Dom0-dmesg: powernow-k8: Found 1 AMD Athlon 64 / Opteron processors (version 1.60.0) powernow-k8: BIOS error - no PSB or ACPI _PSS objects I tried to find answers in the mailing-list archive and with Google, but could not find answers. Is there support in Xen? Are there any patches, I can download anywhere? Would be really nice to get an answer Thanks in advance --- snap --- Kind regards Christian -- Tel.: 0641-2097252...

Hi everyone, When I set CONFIG_ACPI_PROCESSOR, CONFIG_CPU_IDLE and CONFIG_INTEL_IDLE to y then I cannot boot Xen; there is a crash. If I turn CONFIG_INTEL_IDLE off then the boot goes well and, after dom0 has booted, xenpm works and gives some sane output, see below. I have tested this with kernels 3.2 to 3.4.6. Is it impossible to use INTEL_IDLE with Xen? If this is a known issue then maybe

Hi everyone, When I set CONFIG_ACPI_PROCESSOR, CONFIG_CPU_IDLE and CONFIG_INTEL_IDLE to y then I cannot boot Xen; there is a crash. If I turn CONFIG_INTEL_IDLE off then the boot goes well and, after dom0 has booted, xenpm works and gives some sane output, see below. I have tested this with kernels 3.2 to 3.4.6. Is it impossible to use INTEL_IDLE with Xen? If this is a known issue then maybe

Xen Community: As many of you are aware, the Xen 4.0 hypervisor is due to ship tomorrow (shhhh, don''t tell anyone) and I wanted to get submissions underway for Xen 4.1 features. I have updated the Roadmap Wiki page (http://wiki.xensource.com/xenwiki/XenRoadMap) with a new section for Xen 4.1 features to be added. Feel free to add your ideas or send me your features and I will update the

Xen Community: As many of you are aware, the Xen 4.0 hypervisor is due to ship tomorrow (shhhh, don''t tell anyone) and I wanted to get submissions underway for Xen 4.1 features. I have updated the Roadmap Wiki page (http://wiki.xensource.com/xenwiki/XenRoadMap) with a new section for Xen 4.1 features to be added. Feel free to add your ideas or send me your features and I will update the

Hello, The following patches are a solution to a problem we have encountered when using the Xen hypervisor: - Need Pxx/Cxx states to save on power consumption when using Xen (we do want those datacenters to consume less power!), - Also need to figure out the Turbo mode so that the scheduler can properly boost a core for CPU bound guests. In essence the Xen hypervisor requires that

Hi, I''ve still have problems with ACPI(?) on Xen. After some system startup or resume CPU temperature goes high although all domUs (and dom0) are idle. On "good" system startup it is about 50-55C, on "bad" - above 67C (most time above 70C). I''ve noticed difference in C-states repored by Xen (attached files). On "bad" startups in addition suspend

There''re basically two methods to enter a given C-state: legacy (hlt + I/O read), and native(using mwait). MWAIT is always preferred when both underlying CPU and OS support, which is a more efficient way to conduct C-state transition. Xen PM relies on Dom0 to parse ACPI Cx/Px information, which involves one step to notify BIOS about a set of capabilities supported by OSPM. One capability

...: [ 9.485821] powernow-k8: Found 1 AMD Athlon(tm) X4 750K Quad Core Processor (4 cpu cores) (version 2.20.00) Sep 5 13:52:39 pcale kernel: [ 9.485836] powernow-k8: Core Performance Boosting: on. Sep 5 13:52:39 pcale kernel: [ 9.485843] [Firmware Bug]: powernow-k8: No compatible ACPI _PSS objects found. Sep 5 13:52:39 pcale kernel: [ 9.485844] [Firmware Bug]: powernow-k8: Try again with latest BIOS. Sep 5 13:52:39 pcale kernel: [ 9.485957] powernow-k8: invalid pstate 1 - bad value 1. Sep 5 13:52:39 pcale kernel: [ 9.485987] powernow-k8: Please report to BIOS manufacturer...

Hi, another issue I''m seeing with 3.0-rc2 and Xen is that there is an unexpectedly high amount of kernel reserved memory. I suspect that Linux allocates page table entries and corresponding data structures for the whole 6GB areas of the provided ''physical RAM map'' even though it has rather big unusable holes in it. [ 0.000000] BIOS-provided physical RAM map: [

..... .......... 0390: 80 0c 00 00 00 80 0c 00 00 00 80 0c 00 00 00 80 ................ 03a0: 0c 00 00 00 80 12 20 06 0c 00 00 00 80 0c 00 00 ...... ......... 03b0: 00 80 0c 00 00 00 80 0c 00 00 00 80 0c 00 00 00 ................ 03c0: 80 0c 00 00 00 80 08 5f 50 53 53 12 4a 0e 07 12 ......._PSS.J... 03d0: 20 06 0c fc 08 00 00 0c b8 88 00 00 0c 0a 00 00 ............... 03e0: 00 0c 0a 00 00 00 0c 00 17 00 00 0c 00 17 00 00 ................ 03f0: 12 20 06 0c 08 07 00 00 0c a6 64 00 00 0c 0a 00 . ........d..... 0400: 00 00 0c 0a 00 00 00 0c 00 12 00 00 0c 00 12 00 ..................