Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 21

Thread: Ubuntu Processor Power State Management

  1. #11
    Join Date
    Jun 2005
    Location
    Toronto, Canada
    Beans
    Hidden!
    Distro
    Xubuntu 16.04 Xenial Xerus

    Re: Ubuntu Processor Power State Management

    Quote Originally Posted by Bowater View Post
    Code:
    Linux version 3.5.0-10-generic (buildd@akateko)
    Code:
    ubuntu@ubuntu:~$ dmesg | grep -i warn 
    [   16.792822] ACPI Warning: 0x00000460-0x0000047f SystemIO conflicts with Region \PMIO 1 (20120320/utaddress-251) 
    [   16.792833] ACPI Warning: 0x00000428-0x0000042f SystemIO conflicts with Region \PMIO 1 (20120320/utaddress-251) 
    [   16.792840] ACPI Warning: 0x00001180-0x000011bf SystemIO conflicts with Region \GPIO 1 (20120320/utaddress-251)
    Again out of curiosity mostly, can you try "acpi_apic_instance=2" with a 3.2x kernel? See:
    - https://bugzilla.kernel.org/show_bug.cgi?id=45851
    - https://bugzilla.kernel.org/show_bug.cgi?id=44991
    - https://lkml.org/lkml/2012/8/14/309

    Also, what does:
    Code:
    cat /proc/cpuinfo | grep 'cpu cores'
    ...report with and without that kernel parameter?

  2. #12
    Join Date
    Apr 2010
    Beans
    46

    Re: Ubuntu Processor Power State Management

    With Kernel parameter
    tim@tim-desktop:~$ cat /proc/cpuinfo | grep 'cpu cores'
    cpu cores : 2
    cpu cores : 2
    tim@tim-desktop:~$

    without kernel parameter
    tim@tim-desktop:~$ cat /proc/cpuinfo | grep 'cpu cores'
    cpu cores : 2
    cpu cores : 2

    Kernel 3.2

    dmesg | grep -i warn : Nothing



    Code:
    tim@tim-desktop:~$  dmesg | grep -i acpi 
    [    0.000000]  BIOS-e820: 00000000bdf55000 - 00000000bdf9f000 (ACPI NVS) 
    [    0.000000]  BIOS-e820: 00000000bdfe4000 - 00000000bdffd000 (ACPI data) 
    [    0.000000] ACPI: Shall use APIC/MADT table 2 
    [    0.000000] ACPI: RSDP 000f6ad0 00024 (v02 PTLTD ) 
    [    0.000000] ACPI: XSDT bdff70b9 0007C (v01 PTLTD  ? XSDT   06040000  LTP 00000000) 
    [    0.000000] ACPI: FACP bdfe8000 000F4 (v03 INTEL  CRESTLNE 06040000 ALAN 00000001) 
    [    0.000000] ACPI: DSDT bdfe9000 05A61 (v02 Intel  CANTIGA  06040000 INTL 20060608) 
    [    0.000000] ACPI: FACS bdf8efc0 00040 
    [    0.000000] ACPI: APIC bdffcd1e 00068 (v01 INTEL  CRESTLNE 06040000 LOHR 0000005A) 
    [    0.000000] ACPI: HPET bdffcd86 00038 (v01 INTEL  CRESTLNE 06040000 LOHR 0000005A) 
    [    0.000000] ACPI: MCFG bdffcdbe 0003C (v01 INTEL  CRESTLNE 06040000 LOHR 0000005A) 
    [    0.000000] ACPI: SLIX bdffcdfa 00176 (v01 Compal JHL00_90 06040000 TBD  00000001) 
    [    0.000000] ACPI: APIC bdffcf70 00068 (v01 PTLTD  ? APIC   06040000  LTP 00000000) 
    [    0.000000] ACPI: BOOT bdffcfd8 00028 (v01 PTLTD  $SBFTBL$ 06040000  LTP 00000001) 
    [    0.000000] ACPI: TCPA bdfef000 00032 (v00                 00000000      00000000) 
    [    0.000000] ACPI: SSDT bdfe7000 00655 (v01  PmRef    CpuPm 00003000 INTL 20050624) 
    [    0.000000] ACPI: SSDT bdfe6000 00259 (v01  PmRef  Cpu0Tst 00003000 INTL 20050624) 
    [    0.000000] ACPI: SSDT bdfe5000 0020F (v01  PmRef    ApTst 00003000 INTL 20050624) 
    [    0.000000] ACPI: BIOS bug: multiple APIC/MADT found, using 2 
    [    0.000000] ACPI: If "acpi_apic_instance=0" works better, notify linux-acpi@vger.kernel.org 
    [    0.000000] ACPI: Local APIC address 0xfee00000 
    [    0.000000] ACPI: PM-Timer IO Port: 0x408 
    [    0.000000] ACPI: Local APIC address 0xfee00000 
    [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) 
    [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) 
    [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) 
    [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) 
    [    0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) 
    [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge) 
    [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) 
    [    0.000000] ACPI: IRQ0 used by override. 
    [    0.000000] ACPI: IRQ2 used by override. 
    [    0.000000] ACPI: IRQ9 used by override. 
    [    0.000000] Using ACPI (MADT) for SMP configuration information 
    [    0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed00000 
    [    0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-27-generic-pae root=UUID=fa16961b-8316-4938-a1b7-f17f0fb506b7 ro quiet splash acpi_apic_instance=2 
    [    0.006217] ACPI: Core revision 20110623 
    [    0.149836] PM: Registering ACPI NVS region at bdf55000 (303104 bytes) 
    [    0.149836] ACPI: bus type pci registered 
    [    0.152862] ACPI: Added _OSI(Module Device) 
    [    0.152864] ACPI: Added _OSI(Processor Device) 
    [    0.152866] ACPI: Added _OSI(3.0 _SCP Extensions) 
    [    0.152868] ACPI: Added _OSI(Processor Aggregator Device) 
    [    0.154254] ACPI: EC: Look up EC in DSDT 
    [    0.157726] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored 
    [    0.158081] ACPI: SSDT bdf1ac20 00265 (v01  PmRef  Cpu0Ist 00003000 INTL 20050624) 
    [    0.158414] ACPI: Dynamic OEM Table Load: 
    [    0.158418] ACPI: SSDT   (null) 00265 (v01  PmRef  Cpu0Ist 00003000 INTL 20050624) 
    [    0.158540] ACPI: SSDT bdf18620 00549 (v01  PmRef  Cpu0Cst 00003001 INTL 20050624) 
    [    0.158857] ACPI: Dynamic OEM Table Load: 
    [    0.158860] ACPI: SSDT   (null) 00549 (v01  PmRef  Cpu0Cst 00003001 INTL 20050624) 
    [    0.216298] ACPI: SSDT bdf19ca0 001CF (v01  PmRef    ApIst 00003000 INTL 20050624) 
    [    0.216653] ACPI: Dynamic OEM Table Load: 
    [    0.216656] ACPI: SSDT   (null) 001CF (v01  PmRef    ApIst 00003000 INTL 20050624) 
    [    0.248145] ACPI: SSDT bdf19f20 0008D (v01  PmRef    ApCst 00003000 INTL 20050624) 
    [    0.248481] ACPI: Dynamic OEM Table Load: 
    [    0.248484] ACPI: SSDT   (null) 0008D (v01  PmRef    ApCst 00003000 INTL 20050624) 
    [    0.269319] ACPI: Interpreter enabled 
    [    0.269319] ACPI: (supports S0 S3 S4 S5) 
    [    0.269319] ACPI: Using IOAPIC for interrupt routing 
    [    0.269319] PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in ACPI motherboard resources 
    [    0.310497] ACPI: EC: GPE = 0x1d, I/O: command/status = 0x66, data = 0x62 
    [    0.310590] ACPI: No dock devices found. 
    [    0.310590] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug 
    [    0.310590] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff]) 
    [    0.328256] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] 
    [    0.328410] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P2._PRT] 
    [    0.328456] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P1._PRT] 
    [    0.328591] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP01._PRT] 
    [    0.328646] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP03._PRT] 
    [    0.328678] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP04._PRT] 
    [    0.328715] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP05._PRT] 
    [    0.328761]  pci0000:00: Requesting ACPI _OSC control (0x1d) 
    [    0.328764]  pci0000:00: ACPI _OSC request failed (AE_NOT_FOUND), returned control mask: 0x1d 
    [    0.328766] ACPI _OSC control for PCIe not granted, disabling ASPM 
    [    0.334224] ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 *5 6 7 10 12 14 15) 
    [    0.334273] ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 5 6 7 *11 12 14 15) 
    [    0.334320] ACPI: PCI Interrupt Link [LNKC] (IRQs 1 *3 4 5 6 7 10 12 14 15) 
    [    0.334367] ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 7 11 12 14 15) *10 
    [    0.334414] ACPI: PCI Interrupt Link [LNKE] (IRQs 1 3 4 5 6 7 10 12 14 15) *0, disabled. 
    [    0.334463] ACPI: PCI Interrupt Link [LNKF] (IRQs 1 3 4 5 6 7 *11 12 14 15) 
    [    0.334510] ACPI: PCI Interrupt Link [LNKG] (IRQs 1 3 4 5 6 7 *10 12 14 15) 
    [    0.334557] ACPI: PCI Interrupt Link [LNKH] (IRQs 1 3 4 5 6 *7 11 12 14 15) 
    [    0.335100] PCI: Using ACPI for IRQ routing 
    [    0.352101] pnp: PnP ACPI init 
    [    0.352122] ACPI: bus type pnp registered 
    [    0.352518] pnp 00:00: Plug and Play ACPI device, IDs PNP0a08 PNP0a03 (active) 
    [    0.352614] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active) 
    [    0.352750] system 00:02: Plug and Play ACPI device, IDs PNP0103 PNP0c01 (active) 
    [    0.352799] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active) 
    [    0.352923] system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active) 
    [    0.352967] pnp 00:05: Plug and Play ACPI device, IDs PNP0b00 (active) 
    [    0.372118] pnp 00:06: Plug and Play ACPI device, IDs PNP0303 (active) 
    [    0.372163] pnp 00:07: Plug and Play ACPI device, IDs SYN070b SYN0700 SYN0002 PNP0f13 (active) 
    [    0.372402] system 00:08: Plug and Play ACPI device, IDs PNP0c02 (active) 
    [    0.372484] pnp 00:09: Plug and Play ACPI device, IDs IFX0102 PNP0c31 (active) 
    [    0.372596] pnp: PnP ACPI: found 10 devices 
    [    0.372598] ACPI: ACPI bus type pnp unregistered 
    [    0.372602] PnPBIOS: Disabled by ACPI PNP 
    [    0.451147] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared 
    [    0.451395] ACPI: AC Adapter [ACAD] (on-line) 
    [    0.451504] ACPI: Lid Switch [LID0] 
    [    0.451547] ACPI: Power Button [PWRB] 
    [    0.451592] ACPI: Power Button [PWRF] 
    [    0.453662] ACPI: acpi_idle registered with cpuidle 
    [    0.472578] ACPI: Deprecated procfs I/F for battery is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared 
    [    0.472587] ACPI: Battery Slot [BAT1] (battery present) 
    [    0.492299] ACPI: Battery Slot [BAT1] (battery present) 
    [    0.992210] acpi device:1f: hash matches 
    [    7.815713] acpi device:02: registered as cooling_device2 
    [    7.815861] ACPI: Video Device [PEGP] (multi-head: yes  rom: no  post: no)

  3. #13
    Join Date
    Jun 2005
    Location
    Toronto, Canada
    Beans
    Hidden!
    Distro
    Xubuntu 16.04 Xenial Xerus

    Re: Ubuntu Processor Power State Management

    From your original post:
    My solution on windows was to change the processor driver from the intel one to a processor driver that was in device manager. The difference between the two is this.

    "Processor" has no sleep states or power management, the "Intel Processor" uses the intelppm driver and allows full power state management. If switching to a processor driver that doesn't allow sleep states "fixes" things, it's likely there's a hardware issue in one (or more) of the CPU cores or L1 caches at that point.
    It sounds like "processor" in windows is just an acpi-disabled state of the regular intel processor driver (I could be wrong). You could try booting with "acpi=off" for a test, though I wouldn't recommend running it that way too long. Since it seems to work in Windows though, it might be worth a try?

  4. #14
    Join Date
    Apr 2010
    Beans
    46

    Re: Ubuntu Processor Power State Management

    That would make sense, acpi=off boots but i have no wifi. Thats the main problem...

  5. #15
    Join Date
    Apr 2010
    Beans
    46

    Re: Ubuntu Processor Power State Management

    So what now?

  6. #16
    Join Date
    Jun 2005
    Location
    Toronto, Canada
    Beans
    Hidden!
    Distro
    Xubuntu 16.04 Xenial Xerus

    Re: Ubuntu Processor Power State Management

    It may be a bit of a stretch, but can you give the following kernel parameters a try:
    - acpi=strict
    - noapic

  7. #17
    Join Date
    Apr 2010
    Beans
    46

    Re: Ubuntu Processor Power State Management

    I tried them and no luck.. Are there any other kernel commands?

  8. #18
    Join Date
    Jun 2005
    Location
    Toronto, Canada
    Beans
    Hidden!
    Distro
    Xubuntu 16.04 Xenial Xerus

    Re: Ubuntu Processor Power State Management

    The whole listing can be found here: http://www.kernel.org/doc/Documentat...parameters.txt.

    Perhaps you should create a launchpad bug report and try to get one of the kernel devs to have a look at it.

  9. #19
    Join Date
    Apr 2010
    Beans
    46

    Re: Ubuntu Processor Power State Management

    processor.nocst=1 what does this do exactly? Because it works, do you want me to do other tests so we can help others? or just mark as solved?
    Last edited by AoFhEkOl; September 3rd, 2012 at 07:39 PM.

  10. #20
    Join Date
    Jun 2005
    Location
    Toronto, Canada
    Beans
    Hidden!
    Distro
    Xubuntu 16.04 Xenial Xerus

    Re: Ubuntu Processor Power State Management

    By all means mark it solved if the issue is solved. As for the parameter, I have never come up against it before. However, looking at post #16 of this link: https://bugzilla.redhat.com/show_bug.cgi?id=727865 gives some explanation as to what might be happening.

Page 2 of 3 FirstFirst 123 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •