search for: tasklet_act

Just gave 3.0 a spin. Had been running 2.0.7 for the past 3 months or so without problems (aside from intermittent failure during live migration). Anyway, 3.0 seems to have an issue with my machine. It starts up the 4 domains that I''ve got defined (was running 6 user domains with 2.0.7, but two of those were running 2.4 kernels which I can''t seem to build with Xen 3.0 yet, and

...ec da6bccd0 Call Trace: [<c0109c51>] show_stack+0x80/0x96 [<c0100de1>] show_registers+0x15a/0x1d1 [<c010a001>] die+0x106/0x1c4 [<c010a4aa>] do_invalid_op+0xb5/0xbf [<c010985b>] error_code+0x2b/0x30 [<c028cbfa>] net_rx_action+0x484/0x4df [<c01239a9>] tasklet_action+0x7b/0xe0 [<c0123533>] __do_softirq+0x6f/0xef [<c0123632>] do_softirq+0x7f/0x97 [<c0123706>] irq_exit+0x3a/0x3c [<c010d819>] do_IRQ+0x25/0x2c [<c0105efe>] evtchn_do_upcall+0x62/0x82 [<c010988c>] hypervisor_callback+0x2c/0x34 [<c0107673>] cpu_idle+...

...ec da6bccd0 Call Trace: [<c0109c51>] show_stack+0x80/0x96 [<c0100de1>] show_registers+0x15a/0x1d1 [<c010a001>] die+0x106/0x1c4 [<c010a4aa>] do_invalid_op+0xb5/0xbf [<c010985b>] error_code+0x2b/0x30 [<c028cbfa>] net_rx_action+0x484/0x4df [<c01239a9>] tasklet_action+0x7b/0xe0 [<c0123533>] __do_softirq+0x6f/0xef [<c0123632>] do_softirq+0x7f/0x97 [<c0123706>] irq_exit+0x3a/0x3c [<c010d819>] do_IRQ+0x25/0x2c [<c0105efe>] evtchn_do_upcall+0x62/0x82 [<c010988c>] hypervisor_callback+0x2c/0x34 [<c0107673>] cpu_idle+...

...00a c011fcee c0379280 c03792bc c0379280 c02f174c c03792b8 c0379240 c0116d7f 00000000 00000001 c0116b6c c03776e8 00000046 0009f300 c0334800 c0116bd7 0002080b c0104296 c0102e6a Call trace: [<c011fb0e>] rcu_do_batch+0x1a/0x59 [<c011fcee>] rcu_process_callbacks+0x28/0x2c [<c0116d7f>] tasklet_action+0x3a/0x59 [<c0116b6c>] __do_softirq+0x34/0x7d [<c0116bd7>] do_softirq+0x22/0x26 [<c0104296>] do_IRQ+0x1e/0x24 [<c0102e6a>] common_interrupt+0x1a/0x20 [<c0100a77>] default_idl´+0x2b/0x53 [<c0100af3>] cpu_idle+0x40/0x5c [<c0342691>] start_kernel+0x13e/0x14...

...m_event+0x36/0xf3 [<ffffffffa022cd97>] ? net_tx_action+0x1e/0x590 [xen_netback] [<ffffffff8105a1ed>] ? arch_local_irq_restore+0xb/0xd [<ffffffff810066d5>] ? xen_force_evtchn_callback+0xd/0xf [<ffffffff81006c72>] ? check_events+0x12/0x20 [<ffffffff8105a6d5>] ? tasklet_action+0x7f/0xd2 [<ffffffff8105b090>] ? __do_softirq+0xd2/0x19d [<ffffffff81006c72>] ? check_events+0x12/0x20 [<ffffffff8100aadc>] ? call_softirq+0x1c/0x30 [<ffffffff8100c121>] ? do_softirq+0x46/0x81 [<ffffffff8105b214>] ? irq_exit+0x49/0x8b [<ffffffff812a98...

...43] [<ffffffffa0098e36>] ? usb_hcd_unmap_urb_for_dma+0x96/0x190 [usbcore] [ 4.354676] [<ffffffffa0098f9b>] ? __usb_hcd_giveback_urb+0x3b/0x100 [usbcore] [ 4.354835] [<ffffffffa0099bae>] ? usb_giveback_urb_bh+0x8e/0xd0 [usbcore] [ 4.354956] [<ffffffff8106c1a4>] ? tasklet_action+0xf4/0x100 [ 4.355056] [<ffffffff8106c591>] ? __do_softirq+0xf1/0x290 [ 4.355153] [<ffffffff8106c965>] ? irq_exit+0x95/0xa0 [ 4.355244] [<ffffffff813579b5>] ? xen_evtchn_do_upcall+0x35/0x50 [ 4.355352] [<ffffffff815113de>] ? xen_do_hypervisor_callback+0x1e...

I''ve applied julian''s paches to a 2.6.14 gentoo kernel with the appropiate options enabled, and i''m using a modified version of the mpath2.sh script also available on julian''s site http://www.ssi.bg/~ja/ Overall everything works nearly perfectly. Incomming connections to either the fios (PPPoE) connection, or cable modem get routed back out correctly. The

Stamp softlockup thread earlier before do_timer, because the latter is the one to actually trigger lock warning for long-time offline. Or else, I obserevd softlockup warning easily at manual vcpu hot-remove/plug, or when suspend cancel into old context. One point here is to cover both stolen and blocked time to compare with offline threshold. vcpu hotplug falls into ''stolen''

Hi, i have big trouble with a Debian Lenny dom0 and latest kernel 2.6.32.19 with xen-4.0.1rc5. Due some reason the system freezes from time to time. I used kernel 2.6.31.9 with xen-3.4.2 before. The machine doesn''t write anything to serial console so there are no errors or something like that. Perhaps there is something to see from the logs ... Hardware Board: Intel DQ45CB CPU: