From: Andrew Theurer <habanero@linux.vnet.ibm.com>
To: Avi Kivity <avi@redhat.com>
Cc: Tejun Heo <tj@kernel.org>,
kvm@vger.kernel.org, Linux-kernel@vger.kernel.org
Subject: Re: kernel bug in kvm_intel
Date: Thu, 26 Nov 2009 07:47:20 -0600 [thread overview]
Message-ID: <4B0E86E8.7000705@linux.vnet.ibm.com> (raw)
In-Reply-To: <4B0E5901.5050203@redhat.com>
Avi Kivity wrote:
> On 11/26/2009 03:35 AM, Andrew Theurer wrote:
>>
>>> NMI backtrace for cpu 9
>>> CPU 9:
>>> Modules linked in: tun sunrpc af_packet bridge stp ipv6 binfmt_misc
>>> dm_mirror dm_region_hash dm_log dm_multipath scsi_dh dm_mod kvm_intel
>>> kvm uinput sr_mod cdrom ata_generic pata_acpi ata_piix joydev libata
>>> ide_pci_generic usbhid ide_core hid serio_raw cdc_ether usbnet mii
>>> matroxfb_base matroxfb_DAC1064 matroxfb_accel matroxfb_Ti3026
>>> matroxfb_g450 g450_pll matroxfb_misc iTCO_wdt i2c_i801 i2c_core
>>> pcspkr iTCO_vendor_support ioatdma thermal rtc_cmos rtc_core bnx2
>>> rtc_lib dca thermal_sys hwmon sg button shpchp pci_hotplug qla2xxx
>>> scsi_transport_fc scsi_tgt sd_mod scsi_mod crc_t10dif ext3 jbd
>>> mbcache uhci_hcd ohci_hcd ehci_hcd usbcore [last unloaded: processor]
>>> Pid: 5687, comm: qemu-system-x86 Not tainted
>>> 2.6.32-rc7-5e8cb552cb8b48244b6d07bff984b3c4080d4bc9-autokern1 #1
>>> -[7947AC1]-
>>> RIP: 0010:[<ffffffff810b802b>] [<ffffffff810b802b>]
>>> fire_user_return_notifiers+0x31/0x36
>>> RSP: 0018:ffff88095024df08 EFLAGS: 00000246
>>> RAX: 0000000000000000 RBX: 0000000000000800 RCX: ffff88095024c000
>>> RDX: ffff880028340000 RSI: 0000000000000000 RDI: ffff88095024df58
>>> RBP: ffff88095024df18 R08: 0000000000000000 R09: 0000000000000001
>>> R10: 000000caf1fff62d R11: ffff8805b584de40 R12: 00007fffae48e0f0
>>> R13: 0000000000000000 R14: 0000000000000001 R15: 0000000000000000
>>> FS: 00007f45c69d57c0(0000) GS:ffff880028340000(0000)
>>> knlGS:0000000000000000
>>> CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
>>> CR2: fffff9800121056e CR3: 0000000953d36000 CR4: 00000000000026e0
>>> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
>>> DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
>>> Call Trace:
>>> <#DB[1]> <<EOE>> Pid: 5687, comm: qemu-system-x86 Not tainted
>>> 2.6.32-rc7-5e8cb552cb8b48244b6d07bff984b3c4080d4bc9-autokern1 #1
>>> Call Trace:
>>> <NMI> [<ffffffff8100af53>] ? show_regs+0x44/0x49
>>> [<ffffffff812e57b2>] nmi_watchdog_tick+0xc2/0x1b9
>>> [<ffffffff812e4e73>] do_nmi+0xb0/0x252
>>> [<ffffffff812e48a0>] nmi+0x20/0x30
>>> [<ffffffff810b802b>] ? fire_user_return_notifiers+0x31/0x36
>>> <<EOE>> [<ffffffff8100b844>] do_notify_resume+0x62/0x69
>>> [<ffffffff8100bf48>] ? int_check_syscall_exit_work+0x9/0x3d
>>> [<ffffffff8100bf8e>] int_signal+0x12/0x17
>>
>
> That's a bug with the new user return notifiers. Is your host kernel
> preemptible?
preempt is off.
>
> I think I saw this once but I'm not sure. I can't reproduce with a host
> kernel build, some silly guest workload, and 'perf top' to generate an
> nmi load.
>
-Andrew
next prev parent reply other threads:[~2009-11-26 13:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-09 20:04 kernel bug in kvm_intel Andrew Theurer
2009-10-11 5:19 ` Avi Kivity
2009-10-12 18:42 ` Andrew Theurer
2009-10-13 6:50 ` Avi Kivity
2009-10-13 14:04 ` Andrew Theurer
2009-10-14 17:10 ` Avi Kivity
2009-10-15 20:18 ` Andrew Theurer
2009-10-30 18:07 ` Andrew Theurer
2009-10-31 15:47 ` Avi Kivity
2009-10-31 16:25 ` Andrew Theurer
2009-10-31 16:32 ` Avi Kivity
2009-10-31 16:38 ` Avi Kivity
2009-11-01 10:00 ` Tejun Heo
2009-11-01 10:20 ` Avi Kivity
2009-11-01 10:45 ` Tejun Heo
2009-11-01 11:31 ` Avi Kivity
2009-11-18 9:26 ` Tejun Heo
2009-11-26 1:35 ` Andrew Theurer
2009-11-26 1:41 ` Tejun Heo
2009-11-26 10:31 ` Avi Kivity
2009-11-26 13:47 ` Andrew Theurer [this message]
2009-11-29 14:46 ` Avi Kivity
2009-11-30 16:27 ` Andrew Theurer
2009-10-13 14:31 ` Marcelo Tosatti
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=4B0E86E8.7000705@linux.vnet.ibm.com \
--to=habanero@linux.vnet.ibm.com \
--cc=Linux-kernel@vger.kernel.org \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=tj@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).