From: Ken Moffat <zarniwhoop@ntlworld.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Lockups with 4.2-rc kernels and qemu
Date: Fri, 28 Aug 2015 04:03:49 +0100 [thread overview]
Message-ID: <20150828030349.GB4266@milliways> (raw)
In-Reply-To: <20150827165258.GA13620@milliways>
On Thu, Aug 27, 2015 at 05:52:58PM +0100, Ken Moffat wrote:
> On Thu, Aug 27, 2015 at 12:59:14PM +0100, Ken Moffat wrote:
> > On Tue, Aug 25, 2015 at 12:40:15AM +0100, Ken Moffat wrote:
> > > (Cc'ing qemu-devel, please keep me in the Cc).
> > >
> > > TL;DR - qemu locks up my machine when I use 4.2-rc kernels.
> > >
> > Previous mail, or at least the copy to qemu, archived at
> > https://lists.gnu.org/archive/html/qemu-devel/2015-08/msg02784.html
> >
> > I started bisecting, but it is going to be a slow business - kernels
> > which seem to be ok after e.g. 3 hours can still lock the box. I
> > left it running overnight, and this morning it was still up - but
> > firefox could no longer connect externally. I eventually tracked
> > that to my logs taking the space. But one reason the logs had
> > become so big was the following (found from this morning's restart):
> >
> > Aug 27 09:50:28 ac4tv kernel: [ 124.279813] BUG: scheduling while
> > atomic: qemu-system-x86/1789/0x00000002
> > Aug 27 09:50:28 ac4tv kernel: [ 124.279819] Modules linked in:
> > psmouse i2c_piix4 asus_atk0110 microcode k10temp
> > Aug 27 09:50:28 ac4tv kernel: [ 124.279828] Preemption disabled
> > at:[<ffffffff8100787c>] kvm_vcpu_ioctl+0x7c/0x580
>
> This is definitely a *different* bug - I just tried the next kernel,
> and started to get these messages (almost 100,000 lines of them in
> the next 4 minutes) : if that had been happening a couple of weeks
> ago, I would have noticed ;-)
>
> But, the end result is that I cannot attempt to bisect the lockups,
> this scheduling while atomic business is preventing me looking for a
> good kernel.
>
> Has anybody had success qith qemu on an x86_64 host running a 4.2-rc
> kernel ? Looks as if I'll have to give up, and hope that the main
> problem doe not spread to 4.1.
>
What will (hopefully) be my last comment on this - I went back to
4.1.3 on the host, and after a couple of hours it locked up. Maybe
in the past I have jsut been lucky. I think in future I'll probably
stick to native builds., it seems to be less painful.
ĸen
--
Il Porcupino Nil Sodomy Est! (if you will excuse my latatian)
aka "The hedgehog song"
prev parent reply other threads:[~2015-08-28 3:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-24 23:40 Lockups with 4.2-rc kernels and qemu Ken Moffat
2015-08-27 11:59 ` Ken Moffat
2015-08-27 16:52 ` Ken Moffat
2015-08-28 3:03 ` Ken Moffat [this message]
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=20150828030349.GB4266@milliways \
--to=zarniwhoop@ntlworld.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox