From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: Houston, we have May 15, 1953 (says guest when host uses cpufreq, and dies)
Date: Sat, 07 Mar 2009 15:59:07 +0100 [thread overview]
Message-ID: <49B28BBB.4010308@wpkg.org> (raw)
In-Reply-To: <20090218185734.GA26408@amt.cnet>
Marcelo Tosatti schrieb:
>> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow rep_good pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy
>> bogomips : 3993.20
>> TLB size : 1024 4K pages
>> clflush size : 64
>> cache_alignment : 64
>> address sizes : 40 bits physical, 48 bits virtual
>> power management: ts fid vid ttp tm stc
>
> kvm-84 as mentioned. Sorry.
>
It is not stable for me (although I did go through exactly the same routine with kvm-83) - I got an oops.
I'm not sure if the problem is kvm or cpufreq.
This is what I did:
- stopped all kvm-83 guests, removed all kvm-83 modules
- inserted kvm-83 modules, started 9 guests with kvm-84 binary
- inserted cpufreq modules and set the governor to ondemand
- cat /proc/cpuinfo revealed that CPUs are still running at full speed, so I did:
cat /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor
but it didn't return and cat was in "D" state.
- I stopped all guests, removed kvm-84 modules, and got this oops:
Unable to handle kernel paging request at ffffffff88429721 RIP:
[<ffffffff88429721>]
PGD 203067 PUD 207063 PMD 1184dc067 PTE 0
Oops: 0010 [1] PREEMPT SMP
CPU: 0
Modules linked in: loop cpufreq_ondemand powernow_k8 freq_table crc32c libcrc32c vzethdev vznetdev simfs vzrst vzcpt tun vzdquota vzmon ipv6 vzdev xt_tcpudp xt_length ipt_ttl xt_tcpmss xt_TCPMSS iptable_mangle iptable_filter xt_multiport xt_limit ipt_tos ipt_REJECT ip_tables x_tables ib_iser rdma_cm ib_cm iw_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi scsi_transport_iscsi bridge 8021q bonding dm_snapshot dm_mirror dm_multipath dm_mod joydev usbhid hid sata_svw pata_serverworks psmouse ehci_hcd ohci_hcd evdev thermal button ata_generic pata_acpi serio_raw i2c_piix4 tg3 container pcspkr libata usbcore processor i2c_core ssb shpchp pci_hotplug k8temp romfs isofs sd_mod sg mptsas mptscsih mptbase scsi_transport_sas scsi_mod raid1 md_mod
Pid: 20389, comm: kondemand/0 Not tainted 2.6.24-2-pve #1 ovz005
RIP: 0010:[<ffffffff88429721>] [<ffffffff88429721>]
RSP: 0018:ffff810039d09d20 EFLAGS: 00010202
RAX: 0000000000000001 RBX: 00000000ef41d1f5 RCX: ffffffff806cf690
RDX: 0000000000000000 RSI: ffff810080959000 RDI: ffffffff88450e80
RBP: 0000000000000000 R08: 00000000001e8480 R09: 0000000000000000
R10: ffff810001027ee0 R11: 0000000000000001 R12: ffffffff88450e90
R13: ffff810039d09df0 R14: 0000000000000000 R15: 0000000000000000
FS: 00007f93a7d736d0(0000) GS:ffffffff8060b000(0000) knlGS:0000000000000000
CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
CR2: ffffffff88429721 CR3: 0000000000201000 CR4: 00000000000006e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process kondemand/0 (pid: 20389, veid=0, threadinfo ffff810039d08000, task ffff810039d06000)
Stack: 00000000ef41d1f5 0000000000000000 ffffffff88451950 ffff810039d09df0
0000000000000001 ffffffff804aa671 ffffffff8077b1f0 ffff810039d09df0
0000000000000000 00000000ffffffff ffffffff8077b1c0 ffffffff8025ca0a
Call Trace:
[<ffffffff804aa671>] notifier_call_chain+0x51/0x70
[<ffffffff8025ca0a>] __srcu_notifier_call_chain+0x5a/0x90
[<ffffffff8040897d>] cpufreq_notify_transition+0x7d/0xb0
[<ffffffff8846f9ef>] :powernow_k8:powernowk8_target+0x2bf/0x690
[<ffffffff8847671a>] :cpufreq_ondemand:do_dbs_timer+0x26a/0x300
[<ffffffff884764b0>] :cpufreq_ondemand:do_dbs_timer+0x0/0x300
[<ffffffff80252a38>] run_workqueue+0x88/0x120
[<ffffffff80253610>] worker_thread+0x0/0x130
[<ffffffff802536d5>] worker_thread+0xc5/0x130
[<ffffffff80257f70>] autoremove_wake_function+0x0/0x30
[<ffffffff80253610>] worker_thread+0x0/0x130
[<ffffffff80253610>] worker_thread+0x0/0x130
[<ffffffff80257b9b>] kthread+0x4b/0x80
[<ffffffff8020d338>] child_rip+0xa/0x12
[<ffffffff80257b50>] kthread+0x0/0x80
[<ffffffff8020d32e>] child_rip+0x0/0x12
Code: Bad RIP value.
RIP [<ffffffff88429721>]
RSP <ffff810039d09d20>
CR2: ffffffff88429721
---[ end trace e6b0e16fe814aeb1 ]---
note: kondemand/0[20389] exited with preempt_count 1
--
Tomasz Chmielewski
http://wpkg.org
prev parent reply other threads:[~2009-03-07 14:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-18 14:51 Houston, we have May 15, 1953 (says guest when host uses cpufreq, and dies) Tomasz Chmielewski
2009-02-18 16:02 ` Anthony Liguori
2009-02-18 16:11 ` Tomasz Chmielewski
2009-02-18 16:59 ` Avi Kivity
2009-02-18 17:02 ` Tomasz Chmielewski
2009-02-18 20:37 ` Anthony Liguori
2009-02-19 9:15 ` Gerd Hoffmann
2009-02-19 9:20 ` Tomasz Chmielewski
2009-02-19 10:27 ` Gerd Hoffmann
2009-02-18 18:46 ` Marcelo Tosatti
2009-02-18 18:53 ` Tomasz Chmielewski
2009-02-18 18:57 ` Marcelo Tosatti
2009-02-18 19:07 ` Tomasz Chmielewski
2009-02-18 19:10 ` Marcelo Tosatti
2009-02-18 19:18 ` Tomasz Chmielewski
2009-02-18 19:32 ` Marcelo Tosatti
2009-02-18 20:02 ` Tomasz Chmielewski
2009-02-18 20:03 ` Marcelo Tosatti
2009-02-19 14:43 ` Tomasz Chmielewski
2009-03-07 14:59 ` Tomasz Chmielewski [this message]
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=49B28BBB.4010308@wpkg.org \
--to=mangoo@wpkg.org \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
/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