search for: arch_cpu_idl

...64 [ 162.380753] prepare_namespace+0x138/0x180 [ 162.381729] kernel_init_freeable+0x25c/0x280 [ 162.382625] kernel_init+0x10/0x100 [ 162.383337] ret_from_fork+0x10/0x18 [ 162.384072] irq event stamp: 3670810 [ 162.384787] hardirqs last enabled at (3670805): [<00000000fa98454e>] arch_cpu_idle+0x14/0x28 [ 162.386505] hardirqs last disabled at (3670806): [<00000000341112e2>] el1_irq+0x74/0x130 [ 162.388107] softirqs last enabled at (3670810): [<00000000d00bd211>] _local_bh_enable+0x20/0x40 [ 162.389880] softirqs last disabled at (3670809): [<00000000e929005c>] irq_e...

...64 [ 162.380753] prepare_namespace+0x138/0x180 [ 162.381729] kernel_init_freeable+0x25c/0x280 [ 162.382625] kernel_init+0x10/0x100 [ 162.383337] ret_from_fork+0x10/0x18 [ 162.384072] irq event stamp: 3670810 [ 162.384787] hardirqs last enabled at (3670805): [<00000000fa98454e>] arch_cpu_idle+0x14/0x28 [ 162.386505] hardirqs last disabled at (3670806): [<00000000341112e2>] el1_irq+0x74/0x130 [ 162.388107] softirqs last enabled at (3670810): [<00000000d00bd211>] _local_bh_enable+0x20/0x40 [ 162.389880] softirqs last disabled at (3670809): [<00000000e929005c>] irq_e...

...re_namespace+0x138/0x180 > [ 162.381729] kernel_init_freeable+0x25c/0x280 > [ 162.382625] kernel_init+0x10/0x100 > [ 162.383337] ret_from_fork+0x10/0x18 > [ 162.384072] irq event stamp: 3670810 > [ 162.384787] hardirqs last enabled at (3670805): [<00000000fa98454e>] arch_cpu_idle+0x14/0x28 > [ 162.386505] hardirqs last disabled at (3670806): [<00000000341112e2>] el1_irq+0x74/0x130 > [ 162.388107] softirqs last enabled at (3670810): [<00000000d00bd211>] _local_bh_enable+0x20/0x40 > [ 162.389880] softirqs last disabled at (3670809): [<00000000e929...

...t;ffffffff8101c3e4>] handle_irq+0x84/0x150 [<ffffffff818146ad>] do_IRQ+0x4d/0xe0 [<ffffffff818122f2>] common_interrupt+0x72/0x72 <EOI> [<ffffffff8105f706>] ? native_safe_halt+0x6/0x10 [<ffffffff81025454>] default_idle+0x24/0x230 [<ffffffff81025f9f>] arch_cpu_idle+0xf/0x20 [<ffffffff810f5adc>] cpu_startup_entry+0x37c/0x7b0 [<ffffffff8104df1b>] start_secondary+0x25b/0x300 ================================= [ INFO: inconsistent lock state ] 3.16.0-0.rc2.git2.1.fc21.x86_64 #1 Not tainted --------------------------------- inconsistent {HARD...

...t;ffffffff8101c3e4>] handle_irq+0x84/0x150 [<ffffffff818146ad>] do_IRQ+0x4d/0xe0 [<ffffffff818122f2>] common_interrupt+0x72/0x72 <EOI> [<ffffffff8105f706>] ? native_safe_halt+0x6/0x10 [<ffffffff81025454>] default_idle+0x24/0x230 [<ffffffff81025f9f>] arch_cpu_idle+0xf/0x20 [<ffffffff810f5adc>] cpu_startup_entry+0x37c/0x7b0 [<ffffffff8104df1b>] start_secondary+0x25b/0x300 ================================= [ INFO: inconsistent lock state ] 3.16.0-0.rc2.git2.1.fc21.x86_64 #1 Not tainted --------------------------------- inconsistent {HARD...

...et_rx_action+0x158/0x360 __do_softirq+0xd1/0x283 irq_exit+0xe9/0x100 xen_evtchn_do_upcall+0x35/0x50 xen_do_hypervisor_callback+0x1e/0x40 <EOI> ? xen_hypercall_sched_op+0xa/0x20 ? xen_hypercall_sched_op+0xa/0x20 ? xen_safe_halt+0x10/0x20 ? default_idle+0x1e/0xd0 ? arch_cpu_idle+0xf/0x20 ? default_idle_call+0x2c/0x40 ? cpu_startup_entry+0x1ac/0x240 ? rest_init+0x77/0x80 ? start_kernel+0x4a7/0x4b4 ? set_init_arg+0x55/0x55 ? x86_64_start_reservations+0x24/0x26 ? xen_start_kernel+0x555/0x561 general protection fault: 0000 [#1] SMP Call Trace: <IR...

...andle_irq+0x84/0x150 > [<ffffffff818146ad>] do_IRQ+0x4d/0xe0 > [<ffffffff818122f2>] common_interrupt+0x72/0x72 > <EOI> [<ffffffff8105f706>] ? native_safe_halt+0x6/0x10 > [<ffffffff81025454>] default_idle+0x24/0x230 > [<ffffffff81025f9f>] arch_cpu_idle+0xf/0x20 > [<ffffffff810f5adc>] cpu_startup_entry+0x37c/0x7b0 > [<ffffffff8104df1b>] start_secondary+0x25b/0x300 > > ================================= > [ INFO: inconsistent lock state ] > 3.16.0-0.rc2.git2.1.fc21.x86_64 #1 Not tainted > ------------------...

...t;ffffffff8101c3e4>] handle_irq+0x84/0x150 [<ffffffff818146ad>] do_IRQ+0x4d/0xe0 [<ffffffff818122f2>] common_interrupt+0x72/0x72 <EOI> [<ffffffff8105f706>] ? native_safe_halt+0x6/0x10 [<ffffffff81025454>] default_idle+0x24/0x230 [<ffffffff81025f9f>] arch_cpu_idle+0xf/0x20 [<ffffffff810f5adc>] cpu_startup_entry+0x37c/0x7b0 [<ffffffff8104df1b>] start_secondary+0x25b/0x300 This patch fixes it by punting the notification delivery through a work item. This ends up adding an extra pointer to kernfs_elem_attr enlarging kernfs_node by a pointer,...

...t;ffffffff8101c3e4>] handle_irq+0x84/0x150 [<ffffffff818146ad>] do_IRQ+0x4d/0xe0 [<ffffffff818122f2>] common_interrupt+0x72/0x72 <EOI> [<ffffffff8105f706>] ? native_safe_halt+0x6/0x10 [<ffffffff81025454>] default_idle+0x24/0x230 [<ffffffff81025f9f>] arch_cpu_idle+0xf/0x20 [<ffffffff810f5adc>] cpu_startup_entry+0x37c/0x7b0 [<ffffffff8104df1b>] start_secondary+0x25b/0x300 This patch fixes it by punting the notification delivery through a work item. This ends up adding an extra pointer to kernfs_elem_attr enlarging kernfs_node by a pointer,...

...rvisor_callback+0x1e/0x40 <EOI> [<ffffffff810013aa>] ? xen_hypercall_sched_op+0xa/0x20 [<ffffffff810013aa>] ? xen_hypercall_sched_op+0xa/0x20 [<ffffffff8100a830>] ? xen_safe_halt+0x10/0x20 [<ffffffff8101ec84>] ? default_idle+0x24/0xc0 [<ffffffff8101e28f>] ? arch_cpu_idle+0xf/0x20 [<ffffffff810b2276>] ? cpuidle_idle_call+0xd6/0x1d0 [<ffffffff81091312>] ? __atomic_notifier_call_chain+0x12/0x20 [<ffffffff810b24a5>] ? cpu_idle_loop+0x135/0x1e0 [<ffffffff810b256b>] ? cpu_startup_entry+0x1b/0x70 [<ffffffff810b25b0>] ? cpu_startup_entry...

...0f4028>] handle_irq_event+0x48/0x70 [<ffffffff810f71ca>] handle_fasteoi_irq+0x5a/0x100 [<ffffffff81004512>] handle_irq+0x22/0x40 [<ffffffff817691fa>] do_IRQ+0x5a/0xd0 [<ffffffff8175f76f>] ret_from_intr+0x0/0x13 [<ffffffff8100b876>] arch_cpu_idle+0x26/0x30 [<ffffffff810a5b4e>] cpu_startup_entry+0xce/0x410 [<ffffffff81743d4e>] start_secondary+0x255/0x25c other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&amp...

...f 0000000000000000 000000007ff70200 0706c00180000000 000000000000000c 000001bf6f331c58 ffffffffffffffff 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000001 000000007ff70200 0000000000a8b2f0 00000000001034f6 000003e000317e00 #0 [3e000317e28] arch_cpu_idle at 103842 #1 [3e000317e48] do_idle at 17ad18 #2 [3e000317e80] cpu_startup_entry at 17af16 #3 [3e000317ea8] arch_call_rest_init at eac934 > > Wei Wang (2): > virtio_pci: use queue idx instead of array idx to set up the vq > virtio: don't allocate vqs when names[i] = NULL &...

Hi all, I have 5 CentOS 7 virtual guests installed (all fully patched to latest release) and i have the following error in all of them: systemd-journald[7779]: File /run/log/journal/b4a41f4214ca44f898638301891a6f2e/system.journal corrupted or uncleanly shut down, renaming and replacing. ?? .. And I don't understand why. I have configured "Storage=volatile" in journald.conf ...

...andle_irq+0x84/0x150 > [<ffffffff818146ad>] do_IRQ+0x4d/0xe0 > [<ffffffff818122f2>] common_interrupt+0x72/0x72 > <EOI> [<ffffffff8105f706>] ? native_safe_halt+0x6/0x10 > [<ffffffff81025454>] default_idle+0x24/0x230 > [<ffffffff81025f9f>] arch_cpu_idle+0xf/0x20 > [<ffffffff810f5adc>] cpu_startup_entry+0x37c/0x7b0 > [<ffffffff8104df1b>] start_secondary+0x25b/0x300 > > This patch fixes it by punting the notification delivery through a > work item. This ends up adding an extra pointer to kernfs_elem_attr > enlarg...

...rupt+0x162/0x170 [ 728.993298] <EOI> [ 728.993566] [<ffffffffae91ad90>] ? __cpuidle_text_start+0x8/0x8 [ 728.994377] [<ffffffffae91af96>] ? native_safe_halt+0x6/0x10 [ 728.995161] [<ffffffffae91adae>] default_idle+0x1e/0xc0 [ 728.995869] [<ffffffffae2366e3>] arch_cpu_idle+0x23/0xb0 [ 728.996568] [<ffffffffae2f5dea>] cpu_startup_entry+0x14a/0x1e0 [ 728.997330] [<ffffffffae2571b7>] start_secondary+0x1f7/0x270 [ 728.998077] [<ffffffffae2000d5>] start_cpu+0x5/0x14 [ 728.998721] Code: 89 45 c8 e8 3f fe ff ff 44 8b 4d d0 41 01 c7 44 29 cb 74 41 4...

...? xen_hypercall_sched_op+0xa/0x20 Jul 03 11:31:23 antares.fsoft.nnet kernel: [<ffffffff8100b330>] ? xen_safe_halt+0x10/0x20 Jul 03 11:31:23 antares.fsoft.nnet kernel: [<ffffffff8101ea94>] ? default_idle+0x24/0xf0 Jul 03 11:31:23 antares.fsoft.nnet kernel: [<ffffffff8101f49f>] ? arch_cpu_idle+0xf/0x20 Jul 03 11:31:23 antares.fsoft.nnet kernel: [<ffffffff810adc92>] ? cpu_startup_entry+0x312/0x3e0 Jul 03 11:31:23 antares.fsoft.nnet kernel: [<ffffffff816445c7>] ? rest_init+0x77/0x80 Jul 03 11:31:23 antares.fsoft.nnet kernel: [<ffffffff81d77130>] ? start_kernel+0x4d0/0...

From: Yang Zhang <yang.zhang.wz at gmail.com> Implement a generic idle poll which resembles the functionality found in arch/. Provide weak arch_cpu_idle_poll function which can be overridden by the architecture code if needed. Interrupts arrive which may not cause a reschedule in idle loops. In KVM guest, this costs several VM-exit/VM-entry cycles, VM-entry for interrupts and VM-exit immediately. Also this becomes more expensive than bare metal....

Further to my last post, I have removed the xen-pciback module from the Dom0 kernel, and reloaded it as modprobe xen-pciback passthrough=1 I now have the PCI device on the DomU matching the Dom0 Device usb usb1: SerialNumber: 0000:00:1a.0 instead of 0000:00:00.0 However I now have this error ehci_hcd 0000:00:1a.0: Unlink after no-IRQ? Controller is probably using the wrong IRQ. does

...46d7 R09: ffffed003b5c46d6 > R10: ffffed003b5c46d6 R11: ffff8801dae236b3 R12: 0000000000000000 > R13: ffffffff88e07c78 R14: ffffffff899ebe60 R15: 0000000000000000 > arch_safe_halt arch/x86/include/asm/paravirt.h:94 [inline] > default_idle+0xc7/0x450 arch/x86/kernel/process.c:500 > arch_cpu_idle+0x10/0x20 arch/x86/kernel/process.c:491 > default_idle_call+0x6d/0x90 kernel/sched/idle.c:93 > cpuidle_idle_call kernel/sched/idle.c:153 [inline] > do_idle+0x3aa/0x570 kernel/sched/idle.c:262 > cpu_startup_entry+0x10c/0x120 kernel/sched/idle.c:368 > rest_init+0xe1/0xe4 init/mai...

...hypercall_sched_op+0xa/0x20 Jul 03 11:31:23 myDom0.mynetwork.net kernel: [<ffffffff8100b330>] ? xen_safe_halt+0x10/0x20 Jul 03 11:31:23 myDom0.mynetwork.net kernel: [<ffffffff8101ea94>] ? default_idle+0x24/0xf0 Jul 03 11:31:23 myDom0.mynetwork.net kernel: [<ffffffff8101f49f>] ? arch_cpu_idle+0xf/0x20 Jul 03 11:31:23 myDom0.mynetwork.net kernel: [<ffffffff810adc92>] ? cpu_startup_entry+0x312/0x3e0 Jul 03 11:31:23 myDom0.mynetwork.net kernel: [<ffffffff816445c7>] ? rest_init+0x77/0x80 Jul 03 11:31:23 myDom0.mynetwork.net kernel: [<ffffffff81d77130>] ? start_kernel+0...