From: Ed Tomlinson <edt@aei.ca>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Avi Kivity <avi@redhat.com>,
netdev@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: 2.6.30-rc1 A few issues and a stall
Date: Sun, 12 Apr 2009 11:24:06 -0400 [thread overview]
Message-ID: <200904121124.07193.edt@aei.ca> (raw)
[-- Attachment #1: Type: text/plain, Size: 1997 bytes --]
Hi,
I got tired of building out of tree DRM drivers so decided to try 2.6.30-rc1. For simple tasks
it works fine, for slightly more complex ones it is not quite as good...
Here is an example. I normally start a kvm session with the commands below:
ed@grover ~/vm $ sudo modprobe tun
ed@grover ~/vm $ sudo brctl addbr br0
ed@grover ~/vm $ sudo ifconfig br0 192.168.100.254 netmask 255.255.255.0 up
ed@grover ~/vm $ sudo tunctl -b -u ed -t qtap0
qtap0
ed@grover ~/vm $ sudo brctl addif br0 qtap0
ed@grover ~/vm $ sudo ifconfig qtap0 up 0.0.0.0 promisc
ed@grover ~/vm $ sudo iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
iptables v1.4.2: can't initialize iptables table `nat': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
Issue 1 - I need to manually modprobe be get iptables to work. This exact procedure worked in 2.6.29.
ed@grover ~/vm $ sudo modprobe nf_nat
ed@grover ~/vm $ sudo modprobe ipt_MASQUERADE
ed@grover ~/vm $ sudo iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
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.
Issue 3. ACPI is having fun during startup. This does not seem to cause problems later but is
noisy and probably should be fixed before .30's release.
I've attached a complete log of what happens including a Sysrq+T, its a bit big to inline, along with
my config.
BTW the DRM driver works as advertised.
Hope this helps,
Ed Tomlinson
[-- Attachment #2: 30-rc1_1.gz --]
[-- Type: application/x-gzip, Size: 24185 bytes --]
[-- Attachment #3: config.gz --]
[-- Type: application/x-gzip, Size: 15536 bytes --]
next reply other threads:[~2009-04-12 15:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-12 15:24 Ed Tomlinson [this message]
2009-04-13 2:05 ` 2.6.30-rc1 A few issues and a stall 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
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=200904121124.07193.edt@aei.ca \
--to=edt@aei.ca \
--cc=avi@redhat.com \
--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).