From: Avi Kivity <avi@redhat.com>
To: Ed Tomlinson <edt@aei.ca>
Cc: LKML <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: 2.6.30-rc1 A few issues and a stall
Date: Tue, 14 Apr 2009 15:39:42 +0300 [thread overview]
Message-ID: <49E4840E.6010300@redhat.com> (raw)
In-Reply-To: <200904140832.25057.edt@aei.ca>
Ed Tomlinson wrote:
> On Tuesday 14 April 2009 06:03:58 Avi Kivity wrote:
>
>> Ed Tomlinson wrote:
>>
>>> Once the above networking stuff is setup I start kvm with the command below
>>>
>>> QEMU_AUDIO_DRV=alsa kvm -m 1024 -cdrom /mnt/sdc4/divx/archlinux-2009.02-ftp-i686.iso -boot c -smp 3 -usb -usbdevice tablet -vga std -drive file=arch.img -net nic,macaddr=52:54:00:12:34:23 -net tap,ifname=qtap0,script=no -soundhw all -mem-path /hugepages
>>>
>>> which works and the kvm session boots just fine.
>>>
>>> Issue 2. When I attempt to ping outside the kvm session the pc (not just the kvm session) hangs.
>>> Its impossible to kill the kvm session and there are numerious info messages from RCU (tree RCU enabled)
>>> about stalls.
>>>
>>>
>> The rcu messages are likely because a processor has died.
>>
>> Do things work if you drop -mem-path?
>>
>
> It makes no difference. I did notice that one cpu is peged at 100% though. I'll be trying
> CONFIG_PROVE_LOCKING tonight for another problem - might give interesting results.
>
Oh, so this goes away without CONFIG_PROVE_LOCKING?
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2009-04-14 12:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-12 15:24 2.6.30-rc1 A few issues and a stall Ed Tomlinson
2009-04-13 2:05 ` Zhang Rui
2009-04-13 2:50 ` Lin Ming
2009-04-13 22:22 ` Ed Tomlinson
2009-04-14 10:03 ` Avi Kivity
2009-04-14 12:32 ` Ed Tomlinson
2009-04-14 12:39 ` Avi Kivity [this message]
2009-04-14 22:03 ` Ed Tomlinson
2009-04-14 22:54 ` 2.6.30-rc1 A few issues and a stall (nmi_watchdog traceback) Ed Tomlinson
2009-04-14 23:09 ` Stephen Hemminger
2009-04-14 23:54 ` Ed Tomlinson
2009-04-15 1:27 ` Ed Tomlinson
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=49E4840E.6010300@redhat.com \
--to=avi@redhat.com \
--cc=edt@aei.ca \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).