public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bart Trojanowski <bart@jukie.net>
To: kvm-devel@lists.sourceforge.net
Cc: Avi Kivity <avi@qumranet.com>, linux-kernel@vger.kernel.org
Subject: Re: [BUG] 2.6.23.1 host freezes when running kvm
Date: Sat, 20 Oct 2007 11:44:45 -0400	[thread overview]
Message-ID: <20071020154445.GA5254@jukie.net> (raw)
In-Reply-To: <20071020000240.GX3962@jukie.net>

* Bart Trojanowski <bart@jukie.net> [071019 20:03]:
> * Bart Trojanowski <bart@jukie.net> [071019 17:00]:
> <snip>
> > 
> > Once the system is booted, I attached using vnc, then I ssh in and ran
> > 'svn update'... and the host machine froze.
> > 
> > The last messages I on my serial console are:
> > 
> > kvm: unhandled rdmsr: 0x417
> > kvm: unhandled rdmsr: 0xc0000400
> <snip>
> > I noticed that linus merged a bunch of KVM changes last week.  I will
> > try those out next.
> 
> It looks like Linus' tree has the fix already.

I spoke too soon.  The latest from Linus' tree also freezes... but it
took overnight to get there.  There was no particular load on it.

This system was previously running 2.6.22.y w/o problems with a similar
kvm pattern.

This time it froze w/o showing any kvm rdmsr messages.  And while it
froze sometime over night, I cannot be sure when.  Here is the SysRq's
"showPc" output:

SysRq : Show Regs
CPU 2:
Modules linked in: kvm_amd kvm rtc_cmos rtc_core rtc_lib
cpufreq_userspace cpufreq_powersave cpufreq_conservative ipv6 bridge
ext2 mbcache loop pcspkr button dm_mirror dm_snapshot dm_mod ide_generic
ide_cd pata_acpi ata_generic serverworks generic ide_core
Pid: 0, comm: swapper Not tainted 2.6.23-git-kvm-gc4ec2071 #1
RIP: 0010:[<ffffffff8020b0db>]  [<ffffffff8020b0db>] default_idle+0x29/0x3d
RSP: 0018:ffff810140a55f30  EFLAGS: 00000246
RAX: 0000000000000000 RBX: ffffffff8066a040 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffffffff805c3350
RBP: ffffffff8066fa00 R08: ffff810140040560 R09: ffff8101006e7e70
R10: ffff810143e0a900 R11: ffffffff8066fa00 R12: ffffffff8024bc8e
R13: ffff810140a55ec8 R14: 000000000d6ed51a R15: ffffffff8066fa00
FS:  00002aaea92f0bf0(0000) GS:ffff810140a1d300(0000) knlGS:0000000000000000
CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
CR2: 00002add9e236140 CR3: 0000000143def000 CR4: 00000000000006e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400

Call Trace:
 [<ffffffff8020b182>] cpu_idle+0x93/0xbb

Are there things I should be looking for?

-Bart

-- 
				WebSig: http://www.jukie.net/~bart/sig/

  reply	other threads:[~2007-10-20 15:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-19 20:20 [BUG] 2.6.23.1 host freezes when running kvm Bart Trojanowski
2007-10-20  0:02 ` Bart Trojanowski
2007-10-20 15:44   ` Bart Trojanowski [this message]
2007-10-21 11:22     ` [kvm-devel] " Avi Kivity
2007-10-22 13:28       ` Bart Trojanowski
2007-10-22 13:41         ` Avi Kivity
2007-10-23 13:54           ` Bart Trojanowski
2007-10-23 14:20             ` Avi Kivity
2007-11-02 17:19               ` Bart Trojanowski
2007-11-04  7:37                 ` Avi Kivity

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=20071020154445.GA5254@jukie.net \
    --to=bart@jukie.net \
    --cc=avi@qumranet.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=linux-kernel@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