Mark Schneider
2011-Aug-13 15:33 UTC
Re: [Xen-devel] BUG: soft lockup - CPU#0 stuck for 61s! [swapper:0]
Thanks a lot for your answer Konrad. I use xen 4.1.2* (sources from the site of Boris with patches based on xen 4.1.1 I guess). I have created debian packages and deployed them on the xen debian live image (kernel 3.0.1 final with such kernel config: http://www.it-infrastrukturen.com/fileadmin/linux/debian-live-xen/config-3.0.1) You could easy test it on another hardware booting the image from USB stick. I use for tests HP DL385 g7 servers with 32GB RAM and RAID5 (4 x 15k SAS drives) or RADI50 (8 x 15k SAS drives) rsync -avP rsync://www.it-infrastrukturen.ch/ftp/xen411-wheezy-kernel3-amd64-live-gnome-binary-hybrid.iso . dd if=./xen411-wheezy-kernel3-amd64-live-gnome-binary-hybrid.iso of=/dev/sdX bs=1M more details at: http://www.it-infrastrukturen.com/fileadmin/linux/debian-live-xen/README.xen-live In live mode you can add additional packages however after reboot they are gone. It is possible to prepare persistent USB stick (script) to save addons on the stick. I use HVM domU domain for squeeze 6.0.2.1. DomU (HVM) domains for wheezy don''t have such limits. Thank you / regars, Mark Ps. I hope to start a new thread with this mail (no reference header inside) Am 13.08.2011 17:15, schrieb Konrad Rzeszutek Wilk:> On Wed, Aug 10, 2011 at 10:59:55PM +0200, Mark Schneider wrote: > >> Hello, >> >> I can''t boot HVM with debian squeeze 6.0.2.1 when I use more than >> 4VCPUs in the hvm.cfg file (s. some error messages from the console >> are below) >> > Mark, what version of Xen are you using? Did you try using 4.1.1? > > >> I am wondering about the following lines: >> # --- >> #root@xen411dom0:/etc/xen# xm console 7 >> [ 134.220058] BUG: soft lockup - CPU#0 stuck for 61s! [swapper:0] >> [ 134.220058] Modules linked in: uhci_hcd thermal ehci_hcd ata_piix >> xen_netfront libata xen_blkfront floppy usbcore thermal_sys nls_base >> scsi_mod >> [ 134.292664] CPU 0: >> [ 134.292664] Modules linked in: uhci_hcd thermal ehci_hcd ata_piix >> xen_netfront libata xen_blkfront floppy usbcore thermal_sys nls_base >> scsi_mod >> [ 134.319566] Pid: 0, comm: swapper Not tainted 2.6.32-5-amd64 #1 HVM domU >> # --- >> >> Do I need some patches or special additional setting of my the squeezy HVM? >> >> Thank you / regards, >> Mark >> >> -- >> ms@it-infrastrukturen.org >> >> # --- >> root@xen411dom0:/etc/xen# xm console 7 >> [ 134.220058] BUG: soft lockup - CPU#0 stuck for 61s! [swapper:0] >> [ 134.220058] Modules linked in: uhci_hcd thermal ehci_hcd ata_piix xen_netfront libata xen_blkfront floppy usbcore thermal_sys nls_base scsi_mod >> [ 134.292664] CPU 0: >> [ 134.292664] Modules linked in: uhci_hcd thermal ehci_hcd ata_piix xen_netfront libata xen_blkfront floppy usbcore thermal_sys nls_base scsi_mod >> [ 134.319566] Pid: 0, comm: swapper Not tainted 2.6.32-5-amd64 #1 HVM domU >> [ 134.369933] RIP: 0010:[<ffffffff8102c58c>] [<ffffffff8102c58c>] native_safe_halt+0x2/0x3 >> [ 134.369933] RSP: 0018:ffffffff8142ded0 EFLAGS: 00000246 >> [ 134.420796] RAX: ffffffff8142dfd8 RBX: ffffffff814d67d0 RCX: 0000000000000000 >> [ 134.420796] RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000001 >> [ 134.420796] RBP: ffffffff81011dce R08: 0000000000000000 R09: 0000000081528d90 >> [ 134.470673] R10: 00000000fffede31 R11: 0000000000000001 R12: ffffffff814d4dc0 >> [ 134.470673] R13: ffffffff8102cdcc R14: ffffffff8102cdcc R15: ffff88020bd80710 >> [ 134.521042] FS: 00007f6b183817a0(0000) GS:ffff880008c00000(0000) knlGS:0000000000000000 >> [ 134.521042] CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b >> [ 134.521042] CR2: 00007f6b17c6de10 CR3: 000000020c797000 CR4: 00000000000006f0 >> [ 134.571410] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 >> [ 134.571410] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 >> [ 134.571410] Call Trace: >> [ 134.571410] [<ffffffff81017201>] ? default_idle+0x34/0x51 >> [ 134.571410] [<ffffffff8101758d>] ? c1e_idle+0xf5/0xfb >> [ 134.621779] [<ffffffff8100feb1>] ? cpu_idle+0xa2/0xda >> [ 134.621779] [<ffffffff814f3140>] ? early_idt_handler+0x0/0x71 >> [ 134.621779] [<ffffffff814f3cdd>] ? start_kernel+0x3dc/0x3e8 >> [ 134.621779] [<ffffffff814f33b7>] ? x86_64_start_kernel+0xf9/0x106 >> udevd[98]: worker [107] unexpectedly returned with status 0x0100 >> >> udevd[98]: worker [107] failed while handling ''/devices/pci0000:00/0000:00:01.1'' >> >> udevd[98]: worker [109] unexpectedly returned with status 0x0100 >> >> udevd[98]: worker [109] failed while handling ''/devices/pci0000:00/0000:00:01.2'' >> >> >> udevadm settle - timeout of 180 seconds reached, the event queue contains: >> /sys/devices/vif-0 (509) >> /sys/devices/vif-0/net/eth0 (629) >> /sys/devices/pci0000:00/0000:00:01.1/host0 (636) >> /sys/devices/pci0000:00/0000:00:01.1/host0/scsi_host/host0 (637) >> /sys/devices/pci0000:00/0000:00:01.1/host1 (638) >> /sys/devices/pci0000:00/0000:00:01.1/host1/scsi_host/host1 (639) >> [ 199.716053] BUG: soft lockup - CPU#0 stuck for 61s! [swapper:0] >> [ 199.716053] Modules linked in: scsi_wait_scan(+) uhci_hcd thermal ehci_hcd ata_piix xen_netfront libata xen_blkfront floppy usbcore thermal_sys nls_base scsi_mod >> [ 199.792417] CPU 0: >> [ 199.804323] Modules linked in: scsi_wait_scan(+) uhci_hcd thermal ehci_hcd ata_piix xen_netfront libata xen_blkfront floppy usbcore thermal_sys nls_base scsi_mod >> [ 199.828661] Pid: 0, comm: swapper Not tainted 2.6.32-5-amd64 #1 HVM domU >> [ 199.828661] RIP: 0010:[<ffffffff8102c58c>] [<ffffffff8102c58c>] native_safe_halt+0x2/0x3 >> [ 199.828661] RSP: 0018:ffffffff8142ded0 EFLAGS: 00000246 >> [ 199.828661] RAX: ffffffff8142dfd8 RBX: ffffffff814d67d0 RCX: 0000000000000000 >> [ 199.828661] RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000001 >> [ 199.828661] RBP: ffffffff81011dce R08: 0000000000000000 R09: 0000000081528d90 >> [ 199.828661] R10: 00000000fffede31 R11: 0000000000000001 R12: ffffffff814d4dc0 >> [ 199.828661] R13: ffffffff8102cdcc R14: ffffffff8102cdcc R15: ffff88020bd80710 >> [ 199.828661] FS: 00007f6b183817a0(0000) GS:ffff880008c00000(0000) knlGS:0000000000000000 >> [ 199.828661] CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b >> [ 199.828661] CR2: 00007f6b17c6de10 CR3: 000000020c797000 CR4: 00000000000006f0 >> [ 199.828661] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 >> [ 199.828661] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 >> [ 199.828661] Call Trace: >> [ 199.828661] [<ffffffff81017201>] ? default_idle+0x34/0x51 >> [ 199.828661] [<ffffffff8101758d>] ? c1e_idle+0xf5/0xfb >> [ 199.828661] [<ffffffff8100feb1>] ? cpu_idle+0xa2/0xda >> [ 199.828661] [<ffffffff814f3140>] ? early_idt_handler+0x0/0x71 >> [ 199.828661] [<ffffffff814f3cdd>] ? start_kernel+0x3dc/0x3e8 >> [ 199.828661] [<ffffffff814f33b7>] ? x86_64_start_kernel+0xf9/0x106 >> [ 242.368420] INFO: task modprobe:110 blocked for more than 120 seconds. >> [ 242.397772] "echo 0> /proc/sys/kernel/hung_task_timeout_secs" disables this message. >> [ 242.433087] modprobe D ffff88020c750000 0 110 1 0x00000008 >> [ 242.467191] ffff88020c750000 0000000000000086 ffff88020bc31eb8 ffff88020bc31eb4 >> [ 242.529192] 0000000000000001 ffffffff8114017a 000000000000f9e0 ffff88020bc31fd8 >> [ 242.580440] 0000000000015780 0000000000015780 ffff88020c7e0710 ffff88020c7e0a08 >> [ 242.643053] Call Trace: >> [ 242.655368] [<ffffffff8114017a>] ? sysfs_addrm_finish+0x1d/0x20a >> [ 242.682685] [<ffffffff812fbab6>] ? mutex_lock+0xd/0x31 >> [ 242.706564] [<ffffffff812fbab6>] ? mutex_lock+0xd/0x31 >> [ 242.730188] [<ffffffff8106a173>] ? async_synchronize_cookie_domain+0xac/0x106 >> [ 242.770192] [<ffffffff81064f1a>] ? autoremove_wake_function+0x0/0x2e >> [ 242.801989] [<ffffffff810689cd>] ? __blocking_notifier_call_chain+0x51/0x5f >> [ 242.839526] [<ffffffff8106a1e9>] ? async_synchronize_full+0x10/0x2c >> [ 242.853035] [<ffffffff8107aa93>] ? sys_init_module+0x18c/0x21a >> [ 242.865641] [<ffffffff81010b42>] ? system_call_fastpath+0x16/0x1b >> [ 242.878727] INFO: task modprobe:114 blocked for more than 120 seconds. >> [ 242.892536] "echo 0> /proc/sys/kernel/hung_task_timeout_secs" disables this message. >> [ 242.923819] modprobe D ffff88020c750000 0 114 1 0x00000008 >> [ 242.950968] ffff88020c750000 0000000000000086 ffff88020bc7feb8 ffff88020bc7feb4 >> [ 242.980742] 0000000000000001 ffffffff8114017a 000000000000f9e0 ffff88020bc7ffd8 >> [ 243.010580] 0000000000015780 0000000000015780 ffff88020c7e0e20 ffff88020c7e1118 >> [ 243.045486] Call Trace: >> [ 243.056195] [<ffffffff8114017a>] ? sysfs_addrm_finish+0x1d/0x20a >> [ 243.079447] [<ffffffff812fbab6>] ? mutex_lock+0xd/0x31 >> [ 243.101785] [<ffffffff812fbab6>] ? mutex_lock+0xd/0x31 >> [ 243.120773] [<ffffffff8106a173>] ? async_synchronize_cookie_domain+0xac/0x106 >> [ 243.144224] [<ffffffff81064f1a>] ? autoremove_wake_function+0x0/0x2e >> [ 243.157902] [<ffffffff810689cd>] ? __blocking_notifier_call_chain+0x51/0x5f >> [ 243.179377] [<ffffffff8106a1e9>] ? async_synchronize_full+0x10/0x2c >> [ 243.199721] [<ffffffff8107aa93>] ? sys_init_module+0x18c/0x21a >> [ 243.220748] [<ffffffff81010b42>] ? system_call_fastpath+0x16/0x1b >> [ 243.243504] INFO: task modprobe:156 blocked for more than 120 seconds. >> [ 243.266942] "echo 0> /proc/sys/kernel/hung_task_timeout_secs" disables this message. >> [ 243.292222] modprobe D 0000000000000000 0 156 1 0x00000000 >> [ 243.323701] ffff88020f097100 0000000000000082 0000000000000000 ffffffff8105a8dc >> [ 243.359538] 0000000000000000 0000000000000292 000000000000f9e0 ffff88020bf15fd8 >> [ 243.378636] 0000000000015780 0000000000015780 ffff88020bed8710 ffff88020bed8a08 >> [ 243.397627] Call Trace: >> [ 243.403676] [<ffffffff8105a8dc>] ? try_to_del_timer_sync+0x63/0x6c >> [ 243.416619] [<ffffffff812fbab6>] ? mutex_lock+0xd/0x31 >> [ 243.427784] [<ffffffff812fbab6>] ? mutex_lock+0xd/0x31 >> [ 243.444511] [<ffffffff812e7966>] ? klist_next+0x3c/0xa7 >> [ 243.462728] [<ffffffff8106a173>] ? async_synchronize_cookie_domain+0xac/0x106 >> [ 243.488071] [<ffffffff81064f1a>] ? autoremove_wake_function+0x0/0x2e >> [ 243.501905] [<ffffffff810689cd>] ? __blocking_notifier_call_chain+0x51/0x5f >> [ 243.516667] [<ffffffff8106a1e9>] ? async_synchronize_full+0x10/0x2c >> [ 243.529964] [<ffffffff8107aa93>] ? sys_init_module+0x18c/0x21a >> [ 243.542466] [<ffffffff81010b42>] ? system_call_fastpath+0x16/0x1b >> >> >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xensource.com >> http://lists.xensource.com/xen-devel >>-- ms@it-infrastrukturen.org _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Konrad Rzeszutek Wilk
2011-Aug-24 15:30 UTC
Re: [Xen-devel] BUG: soft lockup - CPU#0 stuck for 61s! [swapper:0]
On Sat, Aug 13, 2011 at 05:33:24PM +0200, Mark Schneider wrote:> Thanks a lot for your answer Konrad.Mark, I am just getting to this email. You are still experiencing this issue right?> > I use xen 4.1.2* (sources from the site of Boris with patches based > on xen 4.1.1 I guess). > I have created debian packages and deployed them on the xen debian > live image (kernel 3.0.1 final with such kernel config: http://www.it-infrastrukturen.com/fileadmin/linux/debian-live-xen/config-3.0.1) > > You could easy test it on another hardware booting the image from > USB stick. I use for tests HP DL385 g7 servers with 32GB RAM and > RAID5 (4 x 15k SAS drives) or RADI50 (8 x 15k SAS drives) > > rsync -avP rsync://www.it-infrastrukturen.ch/ftp/xen411-wheezy-kernel3-amd64-live-gnome-binary-hybrid.iso . > dd if=./xen411-wheezy-kernel3-amd64-live-gnome-binary-hybrid.iso of=/dev/sdX bs=1M > > more details at: > http://www.it-infrastrukturen.com/fileadmin/linux/debian-live-xen/README.xen-live > > In live mode you can add additional packages however after reboot > they are gone. > It is possible to prepare persistent USB stick (script) to save > addons on the stick. > > I use HVM domU domain for squeeze 6.0.2.1. DomU (HVM) domains for > wheezy don''t have such limits.OK, so if I use http://cdimage.debian.org/debian-cd/6.0.2.1/amd64/iso-dvd/debian-6.0.2.1-amd64-DVD-1.iso I should be able to reproduce what you have. Can you also send me your guest config file please? _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel