>>> On 17.08.13 at 01:16, ar16 <[email protected]> wrote: > I run Opensuse 12.3 in a number of Xen VPS guests (@ Linode); Been > running stable for a long time. > > After recent Xen client updates over the last couple of days, to > > rpm -qa | grep -i xen | sort > ipset-kmp-xen-6.19_k3.7.10_1.1-32.1.x86_64 > kernel-xen-3.7.10-1.16.1.x86_64 > xen-libs-4.3.0_09-266.1.x86_64 > xen-tools-domU-4.3.0_09-266.1.x86_64 > xtables-addons-kmp-xen-2.3_k3.7.10_1.1-83.1.x86_64 > > under high-load (e.g. a src build) the client is fairly frequently, but > randomly locking up. THe only notice I have is that my SSH session to > the VPS simply disconnects ... no errors in the shell, or in system > message. @ the attached admin Serial console I see only the sudden > onest of, > > ... > [ 484.176059] BUG: soft lockup - CPU#2 stuck for 22s! > [sh:21413] > [ 512.176064] BUG: soft lockup - CPU#2 stuck for 23s! > [sh:21413] > [ 548.176060] BUG: soft lockup - CPU#2 stuck for 22s! > [sh:21413] > [ 576.176074] BUG: soft lockup - CPU#2 stuck for 22s! > [sh:21413] > [ 604.176055] BUG: soft lockup - CPU#2 stuck for 22s! > [sh:21413] > [ 632.176060] BUG: soft lockup - CPU#2 stuck for 22s! > [sh:21413] > ... > > and then it just loops/repeats continuously, requiring a hard-restart of > the VPS to get out of the loop, and recover.
Without knowing the context of those lockups, it's very hard to tell anything. > Guest boot config is unchanged, and quite simple > > cat /boot/grub/menu.lst > default 0 > timeout 1 > title PVGRUB > root (hd0) > kernel /boot/vmlinuz-xen root=/dev/xvdc noresume > xencons=hvc0 kbdtype=us text nofb selinux=0 > apparmor=0 edd=off noshell showopts > splash=verbose > initrd /boot/initrd-xen > > Appears to be a frequent xen-related issue > > https://www.google.com/search?q=BUG+"soft+lockup"+xen > > with not much conclusive resolution. See bug 768714 for pretty clear indication that this is also an issue without Xen involved. Where the problem stems from requires - as said above - at least seeing more that the bare "soft lockup" messages. And as with any suspected regressions, specifying just _to_ which package versions you updated, and not at the same time also _from_ which ones is also at best half helpful. Jan -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
