From: Jan Kiszka <jan.kiszka@siemens.com>
To: kvm-devel <kvm@vger.kernel.org>
Subject: kvm-git: oops in is_largepage_backed
Date: Fri, 31 Oct 2008 14:21:45 +0100 [thread overview]
Message-ID: <490B0669.7060000@siemens.com> (raw)
Hi,
during normal use of kvm-userspace
ccabb53f1a84f11896c840391f7ade3756214086 with kernel modules from
b34cc415c4d1b547d0482f774a81370aecf4fc85 on a 2.6.25 OpenSUSE kernel I
just got this oops:
BUG: unable to handle kernel paging request at ffffc20005261808
IP: [<ffffffff8883fcec>] :kvm:is_largepage_backed+0x2f/0xe7
PGD 7f23b067 PUD 7f23c067 PMD 7d7bb067 PTE 0
Oops: 0000 [1] SMP
last sysfs file: /sys/devices/system/cpu/cpu1/cache/index2/shared_cpu_map
CPU 1
Modules linked in: ath_pci o2scr kvm_intel kvm nfsd lockd nfs_acl
auth_rpcgss sunrpc exportfs ip6t_LOG ipt_MASQUERADE xt_pkttype xt_TCPMSS
xt_tcpudp ipt_LOG xt_limit snd_pcm_oss snd_mixer_oss snd_seq
snd_seq_device wlan_tkip i915 drm af_packet ip6t_REJECT
nf_conntrack_ipv6 ipt_REJECT xt_physdev xt_state iptable_mangle
iptable_nat nf_nat iptable_filter ip6table_mangle
nf_conntrack_netbios_ns nf_conntrack_ipv4 nf_conntrack ip_tables
ip6table_filter ip6_tables x_tables ipv6 microcode cpufreq_conservative
cpufreq_userspace cpufreq_powersave acpi_cpufreq bridge bnep fuse usbhid
hid ff_memless ohci_hcd loop mt2060 rfcomm l2cap dvb_usb_dib0700
dib7000p dib7000m dvb_usb wlan_scan_sta dvb_core snd_hda_intel
ath_rate_sample rtc_cmos dib3000mc ppdev pcmcia iTCO_wdt firmware_class
rtc_core parport_pc snd_pcm dibx000_common sdhci iTCO_vendor_support
parport i2c_i801 hci_usb rtc_lib dib0070 ohci1394 snd_timer
snd_page_alloc serio_raw mmc_core ieee1394 i2c_core yenta_socket wlan
joydev video snd_hwdep rsrc_nonstatic sg pcmcia_core snd bluetooth
output battery soundcore ac button ath_hal(P) intel_agp sky2
sha256_generic aes_x86_64 aes_generic cbc dm_crypt crypto_blkcipher
ehci_hcd sd_mod uhci_hcd usbcore dm_snapshot dm_mod edd ext3 mbcache jbd
fan ata_piix ahci libata scsi_mod dock thermal processor [last unloaded:
ath_pci]
Pid: 3043, comm: qemu-system-x86 Tainted: P N
2.6.25.18-0.2-default #1
RIP: 0010:[<ffffffff8883fcec>] [<ffffffff8883fcec>]
:kvm:is_largepage_backed+0x2f/0xe7
RSP: 0018:ffff81000599fa08 EFLAGS: 00010287
RAX: ffffc20005261808 RBX: 0000000000000004 RCX: 0000000000000005
RDX: 00000000000f1000 RSI: ffff81001099c188 RDI: ffffc20005261800
RBP: ffff81000599fa28 R08: 0000000000000021 R09: 0000000000000002
R10: 0000000000000000 R11: 0000000000000004 R12: 00000000000000a4
R13: ffff81003a378740 R14: ffff81003a378740 R15: ffff81003a379cd0
FS: 0000000041afc950(0000) GS:ffff81007f36ee40(0000) knlGS:0000000000000000
CS: 0010 DS: 002b ES: 002b CR0: 000000008005003b
CR2: ffffc20005261808 CR3: 000000003a27b000 CR4: 00000000000026a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process qemu-system-x86 (pid: 3043, threadinfo ffff81000599e000, task
ffff81006adc0380)
Stack: ffff81000599fa38 0000000000000004 00000000000000a4 ffff81003a378740
ffff81000599fb28 ffffffff888413e9 ffff81000599fa68 ffff81000599faf8
000000000002e561 ffff81003a378740 00000000ef76d004 00000000000003bd
Call Trace:
[<ffffffff888413e9>] :kvm:kvm_mmu_pte_write+0x124/0x7c6
[<ffffffff88839e8d>] :kvm:emulator_write_phys+0x37/0x47
[<ffffffff8883d121>] :kvm:emulator_write_emulated_onepage+0x71/0xf9
[<ffffffff8883d20e>] :kvm:emulator_write_emulated+0x65/0x71
[<ffffffff88846695>] :kvm:x86_emulate_insn+0x3d39/0x49ca
[<ffffffff88839d7b>] :kvm:emulate_instruction+0x199/0x267
[<ffffffff88841288>] :kvm:kvm_mmu_page_fault+0x49/0x86
[<ffffffff88867075>] :kvm_intel:handle_exception+0x184/0x2d9
[<ffffffff888673ba>] :kvm_intel:kvm_handle_exit+0x163/0x185
[<ffffffff8883bcfd>] :kvm:kvm_arch_vcpu_ioctl_run+0x600/0x871
[<ffffffff888354b3>] :kvm:kvm_vcpu_ioctl+0xf6/0x485
[<ffffffff802acada>] vfs_ioctl+0x2a/0x78
[<ffffffff802acd6f>] do_vfs_ioctl+0x247/0x261
[<ffffffff802acdde>] sys_ioctl+0x55/0x77
[<ffffffff8020bffa>] system_call_after_swapgs+0x8a/0x8f
[<00007fa121f45b67>]
Code: 41 55 49 89 fd 41 54 49 89 f4 53 48 83 ec 08 48 8b 3f e8 c8 65 ff
ff 48 85 c0 48 89 c6 0f 84 b6 00 00 00 4c 89 e7 e8 05 e0 ff ff <83> 38
00 0f 85 a5 00 00 00 49 8b 7d 00 4c 89 e6 e8 28 62 ff ff
RIP [<ffffffff8883fcec>] :kvm:is_largepage_backed+0x2f/0xe7
RSP <ffff81000599fa08>
CR2: ffffc20005261808
---[ end trace 5b290f44949eab07 ]---
(kernel tained due to madwifi)
qemu was started like this:
qemu-system-x86_64 <some-32-bit-Linux-image> -m 768 -serial stdio \
-net nic,model=virtio -net user
The guest was copying some files via network onto its disk when the oops
happened.
Can anyone make some sense out of it?
Thanks,
Jan - who actually has to reboot now :(
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
reply other threads:[~2008-10-31 13:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=490B0669.7060000@siemens.com \
--to=jan.kiszka@siemens.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.