From: Nikola Ciprich <extmaillist@linuxbox.cz>
To: Gerrit Slomma <roadrunner_gs@web.de>
Cc: kvm@vger.kernel.org, nikola.ciprich@linuxbox.cz
Subject: Re: BUG: soft lockup - CPU stuck for ...
Date: Sun, 29 Mar 2009 19:36:10 +0200 [thread overview]
Message-ID: <20090329173610.GA10755@nik-comp.linuxbox.cz> (raw)
In-Reply-To: <loom.20090329T074937-223@post.gmane.org>
Hi,
I was also experiencing this problem a lot for quite a long time (and for
wide range of KVM versions..)
I might be completely wrong as I'm not sure if it was really the reason,
but i THINK it disappeared when I started to use fully preemptible kernel on host..
You might want to try it...
BR
nik
On Sun, Mar 29, 2009 at 07:51:21AM +0000, Gerrit Slomma wrote:
> Robert Wimmer <r.wimmer <at> tomorrow-focus.de> writes:
>
> >
> > Hi,
> >
> > does anyone know how to solve the problem
> > with "BUG: soft lockup - CPU#0 stuck for ..."?
> > Today I got the messages below during compilation
> > of the kernel modules in a guest. Using kvm84 and Kernel 2.6.29
> > as host kernel and 2.6.28 as guest kernel during the
> > hangup of the guest neither ssh or ping was possible.
> > After about 2 minutes the guest was reachable again
> > and I saw the messages below with "dmesg".
> >
> > Maybe it is related with my prev. anserwed posting:
> > http://article.gmane.org/gmane.comp.emulators.kvm.devel/29677
> >
> > Thanks!
> > Robert
> >
> > BUG: soft lockup - CPU#0 stuck for 61s!
> > (...)
>
> Hello
>
> Do you use x86_64 or i686?
> Look at my post here http://article.gmane.org/gmane.comp.emulators.kvm.devel/29833
> And my Bug-report here https://bugzilla.redhat.com/show_bug.cgi?id=492688.
> I do not have the problems while running but after migrating. Problems with
> stuck CPUs vanish if i686 for the host is used - but i am testing further.
>
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
-------------------------------------
Nikola CIPRICH
LinuxBox.cz, s.r.o.
28. rijna 168, 709 01 Ostrava
tel.: +420 596 603 142
fax: +420 596 621 273
mobil: +420 777 093 799
www.linuxbox.cz
mobil servis: +420 737 238 656
email servis: servis@linuxbox.cz
-------------------------------------
next prev parent reply other threads:[~2009-03-29 18:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-28 23:12 BUG: soft lockup - CPU stuck for Robert Wimmer
2009-03-29 7:51 ` Gerrit Slomma
2009-03-29 17:36 ` Nikola Ciprich [this message]
2009-03-30 18:50 ` Gerrit Slomma
-- strict thread matches above, loose matches on Subject: below --
2009-03-30 11:37 Robert Wimmer
2009-03-30 15:55 ` Brian Jackson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090329173610.GA10755@nik-comp.linuxbox.cz \
--to=extmaillist@linuxbox.cz \
--cc=kvm@vger.kernel.org \
--cc=nikola.ciprich@linuxbox.cz \
--cc=roadrunner_gs@web.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.