From: Nikola Ciprich <extmaillist@linuxbox.cz>
To: kvm-devel@lists.sourceforge.net
Subject: paravirt clock stil causing hangs in kvm-65
Date: Mon, 7 Apr 2008 13:53:36 +0200 (CEST) [thread overview]
Message-ID: <alpine.LRH.1.10.0804071230550.3954@linuxbox.linuxbox.cz> (raw)
Hi,
I also tried paravirt clock again in latest git with kvm-65 patch
applied, and problem with cpu-lockups persists:
[10813.654806] BUG: soft lockup - CPU#0 stuck for 61s! [swapper:0]
[10813.655789] CPU 0:
[10813.656624] Modules linked in: virtio_pci virtio_ring virtio_blk virtio
piix dm_snapshot dm_zero dm_mirror dm_mod ide_disk
ide_core sd_mod scsi_mod ext3 jbd ehci_hcd ohci_hcd uhci_hcd
[10813.658805] Pid: 0, comm: swapper Not tainted 2.6.25-rc7 #5
[10813.658805] RIP: 0010:[<ffffffff80222ab2>] [<ffffffff80222ab2>]
native_safe_halt+0x2/0x10
[10813.658805] RSP: 0018:ffffffff805adf50 EFLAGS: 00000296
[10813.658805] RAX: 000000019b08eeb0 RBX: ffffffff805f5000 RCX:
000000019b08eeb0
[10813.658805] RDX: 0000000000000006 RSI: 00000000356832b0 RDI:
ffffffff805adf38
[10813.658805] RBP: 0000000000000da8 R08: 0000000000000000 R09:
0000000000000000
[10813.658805] R10: 0000000000000001 R11: 0000000000000002 R12:
ffffffff802228ed
[10813.658805] R13: 00000000000132a0 R14: ffffffff80200bba R15:
ffff81000100a280
[10813.658805] FS: 0000000000000000(0000) GS:ffffffff80576000(0000)
knlGS:0000000000000000
[10813.658805] CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
[10813.658805] CR2: 00007fac0f852000 CR3: 0000000000201000 CR4:
00000000000006e0
[10813.658805] DR0: 0000000000000000 DR1: 0000000000000000 DR2:
0000000000000000
[10813.658805] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7:
0000000000000400
[10813.658805]
[10813.658805] Call Trace:
[10813.658805] [<ffffffff8020a55b>] ? default_idle+0x3b/0x70
[10813.658805] [<ffffffff8020a520>] ? default_idle+0x0/0x70
[10813.658805] [<ffffffff8020a60e>] ? cpu_idle+0x7e/0xe0
[10813.658805] [<ffffffff80211630>] ? pda_init+0x30/0xb0
Can I somehow help to track this one down??
Additionaly, I'd like to ask two questions:
1) why is kvm-65 patch changing release to -rc7? maybe this is
unintended??
2) I'm getting lot's of following messages on host, what do they mean?
[16836.605669] Ignoring de-assert INIT to vcpu SOMENUMBER
[16836.605687] SIPI to vcpu SOMENUMBER vector 0xSOMENUMBER
BR
nik
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Register now and save $200. Hurry, offer ends at 11:59 p.m.,
Monday, April 7! Use priority code J8TLD2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
next reply other threads:[~2008-04-07 11:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-07 11:53 Nikola Ciprich [this message]
2008-04-07 21:34 ` paravirt clock stil causing hangs in kvm-65 Marcelo Tosatti
2008-04-08 1:18 ` Marcelo Tosatti
2008-04-08 5:59 ` Nikola Ciprich
2008-04-19 15:29 ` Marcelo Tosatti
2008-04-19 16:22 ` Glauber Costa
2008-04-19 16:49 ` Marcelo Tosatti
2008-04-21 7:15 ` Gerd Hoffmann
2008-04-21 8:33 ` [ RfC / patch ] kvmclock fixes Gerd Hoffmann
2008-04-21 9:57 ` Jeremy Fitzhardinge
2008-04-21 13:01 ` Gerd Hoffmann
2008-04-21 13:38 ` Jeremy Fitzhardinge
2008-04-24 13:20 ` paravirt clock stil causing hangs in kvm-65 Glauber Costa
2008-04-26 14:24 ` extmaillist
2008-04-19 16:29 ` 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=alpine.LRH.1.10.0804071230550.3954@linuxbox.linuxbox.cz \
--to=extmaillist@linuxbox.cz \
--cc=kvm-devel@lists.sourceforge.net \
/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.