search for: intel_idl

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 issu...

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 issu...

...0x12b/0x150 > [ 861.568114] ? reset_hung_task_detector+0x20/0x20 > [ 861.568863] ? kthread_create_worker_on_cpu+0x70/0x70 > [ 861.569598] ret_from_fork+0x3a/0x50 > [ 861.570370] Sending NMI from CPU 2 to CPUs 0-1,3-7: > [ 861.571426] NMI backtrace for cpu 6 skipped: idling at intel_idle+0x7f/0x120 > [ 861.571429] NMI backtrace for cpu 7 skipped: idling at intel_idle+0x7f/0x120 > [ 861.571432] NMI backtrace for cpu 3 skipped: idling at intel_idle+0x7f/0x120 > [ 861.571464] NMI backtrace for cpu 5 skipped: idling at intel_idle+0x7f/0x120 > [ 861.571467] NMI backtrac...

...80 [ 246.764644] kthread+0x12b/0x150 [ 246.765350] ? reset_hung_task_detector+0x20/0x20 [ 246.766052] ? kthread_create_worker_on_cpu+0x70/0x70 [ 246.766777] ret_from_fork+0x3a/0x50 [ 246.767488] Sending NMI from CPU 1 to CPUs 0,2-7: [ 246.768624] NMI backtrace for cpu 5 skipped: idling at intel_idle+0x7f/0x120 [ 246.768648] NMI backtrace for cpu 4 skipped: idling at intel_idle+0x7f/0x120 [ 246.768671] NMI backtrace for cpu 0 skipped: idling at intel_idle+0x7f/0x120 [ 246.768676] NMI backtrace for cpu 7 skipped: idling at intel_idle+0x7f/0x120 [ 246.768678] NMI backtrace for cpu 3 skipped:...

...[ 861.567355] kthread+0x12b/0x150 [ 861.568114] ? reset_hung_task_detector+0x20/0x20 [ 861.568863] ? kthread_create_worker_on_cpu+0x70/0x70 [ 861.569598] ret_from_fork+0x3a/0x50 [ 861.570370] Sending NMI from CPU 2 to CPUs 0-1,3-7: [ 861.571426] NMI backtrace for cpu 6 skipped: idling at intel_idle+0x7f/0x120 [ 861.571429] NMI backtrace for cpu 7 skipped: idling at intel_idle+0x7f/0x120 [ 861.571432] NMI backtrace for cpu 3 skipped: idling at intel_idle+0x7f/0x120 [ 861.571464] NMI backtrace for cpu 5 skipped: idling at intel_idle+0x7f/0x120 [ 861.571467] NMI backtrace for cpu 0 skipped:...

...e cleanup and direct call of cpuidle_idle_call(). There is not much new code here. > >> +obj-$(CONFIG_X86) += default_driver.o > > BTW, that''s a pretty generic name for an x86 specific idle driver... > > I think that on builds that support intel_idle and acpi_idle, > everything in this file will be unused, unless somebody uses some > debugging cmdline params that should have been deleted ages ago. Yes, I agree that the name has to be x86 specific. I think the routines would be used for pre-nehalem architectures that use arch default or...

...8107a795>] ? irq_exit+0x85/0x90 Mar 7 18:54:21 backup03 kernel: [<ffffffff815310ba>] ? smp_apic_timer_interrupt+0x4a/0x60 Mar 7 18:54:21 backup03 kernel: [<ffffffff8100bb93>] ? apic_timer_interrupt+0x13/0x20 Mar 7 18:54:21 backup03 kernel: <EOI> [<ffffffff812e09ce>] ? intel_idle+0xde/0x170 Mar 7 18:54:21 backup03 kernel: [<ffffffff812e09b1>] ? intel_idle+0xc1/0x170 Mar 7 18:54:21 backup03 kernel: [<ffffffff81426707>] ? cpuidle_idle_call+0xa7/0x140 Mar 7 18:54:21 backup03 kernel: [<ffffffff81009fc6>] ? cpu_idle+0xb6/0x110 Mar 7 18:54:21 backup03 kerne...

[cc += linux-pm] Hi Lyude, First of all, thanks a lot for looking into this. On Mon, Jul 16, 2018 at 07:59:25PM -0400, Lyude Paul wrote: > In order to fix all of the spots that need to have runtime PM get/puts() > added, we need to ensure that it's possible for us to call > pm_runtime_get/put() in any context, regardless of how deep, since > almost all of the spots that are

...04:36 kernel: [<ffffffff81071de5>] ? irq_exit+0x85/0x90 Feb 18 05:04:36 kernel: [<ffffffff814f4d70>] ? smp_apic_timer_interrupt+0x70/0x9b Feb 18 05:04:36 kernel: [<ffffffff8100bc13>] ? apic_timer_interrupt+0x13/0x20 Feb 18 05:04:36 kernel: <EOI> [<ffffffff812c49de>] ? intel_idle+0xde/0x170 Feb 18 05:04:36 kernel: [<ffffffff812c49c1>] ? intel_idle+0xc1/0x170 Feb 18 05:04:36 kernel: [<ffffffff813f9ef7>] ? cpuidle_idle_call+0xa7/0x140 Feb 18 05:04:36 kernel: [<ffffffff81009e06>] ? cpu_idle+0xb6/0x110 Feb 18 05:04:36 kernel: [<ffffffff814d40ca>] ? rest...

This is the latest version of https://patchwork.freedesktop.org/series/46815/ With a bunch of fixes to the new fb_helper to prevent it from breaking module loading/unloading with nouveau. Also; lots of documentation fixes and one fix in response to a kbuild bot. Lyude Paul (8): drm/nouveau: Fix bogus drm_kms_helper_poll_enable() placement drm/nouveau: Enable polling even if we have runtime

Next version of https://patchwork.freedesktop.org/series/46815/ Same as previous version, but some small changes made to commit messages and acks/rbs have been added Lyude Paul (5): drm/nouveau: Fix bogus drm_kms_helper_poll_enable() placement drm/nouveau: Remove duplicate poll_enable() in pmops_runtime_suspend() drm/nouveau: Fix deadlock with fb_helper with async RPM requests

Latest version of https://patchwork.freedesktop.org/series/46815/ with some significant improvements: - I finally figured out a clean way to do this entirely with runtime PM helpers, no avoiding grabbing refs required! - Since this new method removes the need for a lot of the other changes I made (although we probably still want those changes, but not for fixing these deadlocks)

...85/0x90 Feb 18 05:04:36 >> kernel: [<ffffffff814f4d70>] ? >> smp_apic_timer_interrupt+0x70/0x9b >> Feb 18 05:04:36 kernel: [<ffffffff8100bc13>] ? >> apic_timer_interrupt+0x13/0x20 >> Feb 18 05:04:36 kernel: <EOI> [<ffffffff812c49de>] ? >> intel_idle+0xde/0x170 Feb 18 05:04:36 kernel: >> [<ffffffff812c49c1>] ? intel_idle+0xc1/0x170 Feb 18 05:04:36 >> kernel: [<ffffffff813f9ef7>] ? cpuidle_idle_call+0xa7/0x140 Feb >> 18 05:04:36 kernel: [<ffffffff81009e06>] ? cpu_idle+0xb6/0x110 >> Feb 18 05:04:36 kerne...

...10e91dc>] ? note_interrupt+0x18c/0x1d0 [<ffffffff810e997d>] ? handle_fasteoi_irq+0xcd/0xf0 [<ffffffff8100faf9>] ? handle_irq+0x49/0xa0 [<ffffffff815315fc>] ? do_IRQ+0x6c/0xf0 [<ffffffff8100b9d3>] ? ret_from_intr+0x0/0x11 <EOI> [<ffffffff812e0bee>] ? intel_idle+0xde/0x170 [<ffffffff812e0bd1>] ? intel_idle+0xc1/0x170 [<ffffffff81426b67>] ? cpuidle_idle_call+0xa7/0x140 [<ffffffff81009fc6>] ? cpu_idle+0xb6/0x110 [<ffffffff8152143c>] ? start_secondary+0x2ac/0x2ef handlers: [<ffffffff813c4260>] (usb_hcd_irq+0x0/0x90) [&lt...

...etting over 700 MB/s. Any other users had this issues with Idrac Enterprise?? On Thu, Feb 22, 2018 at 12:16 AM, Serkan ?oban <cobanserkan at gmail.com> wrote: > "Did you check the BIOS/Power settings? They should be set for high > performance. > Also you can try to boot "intel_idle.max_cstate=0" kernel command line > option to be sure CPUs not entering power saving states. > > On Thu, Feb 22, 2018 at 9:59 AM, Ryan Wilkinson <ryanwilk at gmail.com> > wrote: > > > > > > I have a 3 host gluster replicated cluster that is providing storag...

...72775>] ? irq_exit+0x85/0x90 Feb 1 04:07:15 localhost kernel: [<ffffffff814f8fe0>] ? smp_apic_timer_interrupt+0x70/0x9b Feb 1 04:07:15 localhost kernel: [<ffffffff8100bb93>] ? apic_timer_interrupt+0x13/0x20 Feb 1 04:07:15 localhost kernel: <EOI> [<ffffffff812c999e>] ? intel_idle+0xde/0x170 Feb 1 04:07:15 localhost kernel: [<ffffffff812c9981>] ? intel_idle+0xc1/0x170 Feb 1 04:07:15 localhost kernel: [<ffffffff813fd8b7>] ? cpuidle_idle_call+0xa7/0x140 Feb 1 04:07:15 localhost kernel: [<ffffffff81009fc6>] ? cpu_idle+0xb6/0x110 Feb 1 04:07:15 localhost k...

"Did you check the BIOS/Power settings? They should be set for high performance. Also you can try to boot "intel_idle.max_cstate=0" kernel command line option to be sure CPUs not entering power saving states. On Thu, Feb 22, 2018 at 9:59 AM, Ryan Wilkinson <ryanwilk at gmail.com> wrote: > > > I have a 3 host gluster replicated cluster that is providing storage for our > RHEV environment....

...ff81071de5>] ? irq_exit+0x85/0x90 > Feb 18 05:04:36 kernel: [<ffffffff814f4d70>] ? > smp_apic_timer_interrupt+0x70/0x9b > Feb 18 05:04:36 kernel: [<ffffffff8100bc13>] ? > apic_timer_interrupt+0x13/0x20 > Feb 18 05:04:36 kernel: <EOI> [<ffffffff812c49de>] ? intel_idle+0xde/0x170 > Feb 18 05:04:36 kernel: [<ffffffff812c49c1>] ? intel_idle+0xc1/0x170 > Feb 18 05:04:36 kernel: [<ffffffff813f9ef7>] ? cpuidle_idle_call+0xa7/0x140 > Feb 18 05:04:36 kernel: [<ffffffff81009e06>] ? cpu_idle+0xb6/0x110 > Feb 18 05:04:36 kernel: [<ffffffff...

Latest version of https://patchwork.freedesktop.org/series/46815/ , with one small change re: ilia Lyude Paul (5): drm/nouveau: Fix bogus drm_kms_helper_poll_enable() placement drm/nouveau: Remove duplicate poll_enable() in pmops_runtime_suspend() drm/nouveau: Fix deadlock with fb_helper with async RPM requests drm/nouveau: Use pm_runtime_get_noresume() in connector_detect()

...ffff81076e95>] ? irq_exit+0x85/0x90 May 20 12:16:15 wolfpac kernel: [<ffffffff8151ec20>] ? smp_apic_timer_interrupt+0x70/0x9b May 20 12:16:15 wolfpac kernel: [<ffffffff8100bb93>] ? apic_timer_interrupt+0x13/0x20 May 20 12:16:15 wolfpac kernel: <EOI> [<ffffffff812da8fe>] ? intel_idle+0xde/0x170 May 20 12:16:15 wolfpac kernel: [<ffffffff812da8e1>] ? intel_idle+0xc1/0x170 May 20 12:16:15 wolfpac kernel: [<ffffffff8141c2a7>] ? cpuidle_idle_call+0xa7/0x140 May 20 12:16:15 wolfpac kernel: [<ffffffff81009fc6>] ? cpu_idle+0xb6/0x110 May 20 12:16:15 wolfpac kernel: [...