From: Avi Kivity <avi@redhat.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: kvm@vger.kernel.org
Subject: Re: BUG: using smp_processor_id() in preemptible
Date: Sun, 28 Jun 2009 17:11:32 +0300 [thread overview]
Message-ID: <4A477A14.8070801@redhat.com> (raw)
In-Reply-To: <1245852919.21314.56.camel@johannes.local>
On 06/24/2009 05:15 PM, Johannes Berg wrote:
> Hi,
>
> I'm trying to run a test environment in kvm (because uml doesn't have
> lockdep), and am running into the following problems:
>
> 1) I get the $subject warning a lot, when starting kvm:
> [85763.262707] BUG: using smp_processor_id() in preemptible [00000000] code: kvm/13877
> [85763.262719] caller is kvm_write_guest_time+0x40/0x220 [kvm]
> [85763.262722] Pid: 13877, comm: kvm Not tainted 2.6.30-wl-26837-g0ee651a-dirty #54
> [85763.262725] Call Trace:
> [85763.262729] [<ffffffff8041d482>] debug_smp_processor_id+0xf2/0x100
> [85763.262741] [<ffffffffa0331390>] kvm_write_guest_time+0x40/0x220 [kvm]
> [85763.262753] [<ffffffffa0331890>] vcpu_enter_guest+0x320/0x580 [kvm]
> [85763.262780] [<ffffffffa03347f4>] __vcpu_run+0x74/0x2f0 [kvm]
> [85763.262792] [<ffffffffa033571f>] kvm_arch_vcpu_ioctl_run+0x8f/0x200 [kvm]
> [85763.262804] [<ffffffffa0329b48>] kvm_vcpu_ioctl+0x4b8/0x900 [kvm]
> [85763.262816] [<ffffffff802f5216>] vfs_ioctl+0x36/0xb0
> [85763.262819] [<ffffffff802f55f9>] do_vfs_ioctl+0x89/0x320
> [85763.262826] [<ffffffff802f58df>] sys_ioctl+0x4f/0x80
> [85763.262830] [<ffffffff8020b6fb>] system_call_fastpath+0x16/0x1b
>
>
ISTR this was fixed...
> That kernel version is wireless-testing, which is currently based on
> v2.6.30, and the -dirty is for some wireless patches I did.
>
Please post the output of 'git merge-base wireless-testing
origin/master' so I can know what tree to look at.
> 2) The second problem is that it doesn't actually work. I use this
> command line:
> kvm -kernel arch/x86_64/boot/bzImage \
> -hda ../uml/Ubuntu-IntrepidIbex-amd64-root_fs \
> -append "root=/dev/hda console=ttyS0" -curses
>
> and the system hangs after
> Plex86/Bochs VGABios (PCI) current-cvs 12 Jun 2009
> This VGA/VBE Bios is released under the GNU LGPL
>
> Please visit :
> . http://bochs.sourceforge.net
> . http://www.nongnu.org/vgabios
>
> cirrus-compatible VGA is detected
>
> QEMU BIOS - build: 06/12/09
> $Revision: 1.182 $ $Date: 2007/08/01 17:09:51 $
> Options: apmbios pcibios eltorito rombios32
>
> ata0 master: QEMU HARDDISK ATA-7 Hard-Disk (1024 MBytes)
> ata1 master: QEMU DVD-ROM ATAPI-4 CD-Rom/DVD-Rom
>
> Press F12 for boot menu.
>
>
> Decompressing Linux... Parsing ELF... done.
> Booting the kernel.
>
Does it hang or switch to some graphics mode? What happens if you drop
curses?
You can see where it hangs using the monitor 'info registers' and 'x/30i
$eip' commands.
> The guest kernel is the same as the host, but with somewhat different
> config options.
>
> The strange thing here is that the exact same command line, with
> qemu-system-x86_64 instead of kvm works perfectly.
>
That's probably a qemu without kvm support.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-06-28 14:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 14:15 BUG: using smp_processor_id() in preemptible Johannes Berg
2009-06-28 14:11 ` Avi Kivity [this message]
2009-06-29 8:32 ` Johannes Berg
2009-06-29 9:08 ` Avi Kivity
2009-06-29 9:54 ` Johannes Berg
2009-06-29 9:57 ` Johannes Berg
2009-06-29 10:00 ` Avi Kivity
2009-06-29 10:06 ` Johannes Berg
2009-06-29 10:16 ` Avi Kivity
2009-06-29 10:18 ` Johannes Berg
2009-06-29 10:25 ` Avi Kivity
2009-06-29 10:32 ` Johannes Berg
2009-06-29 10:39 ` Avi Kivity
2009-06-29 10:55 ` Johannes Berg
2009-06-29 11:38 ` Avi Kivity
2009-06-29 12:03 ` Johannes Berg
2009-06-29 9:59 ` Avi Kivity
2009-06-29 10:00 ` Johannes Berg
2009-06-29 10:04 ` Avi Kivity
2009-06-29 10:04 ` Johannes Berg
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=4A477A14.8070801@redhat.com \
--to=avi@redhat.com \
--cc=johannes@sipsolutions.net \
--cc=kvm@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