public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Alistair John Strachan <alistair-T7eSMZptz7IqdlJmJB21zg@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: 2.6.23-rc1, KVM-AMD problem
Date: Sat, 28 Jul 2007 18:55:41 +0100	[thread overview]
Message-ID: <200707281855.41277.alistair@devzero.co.uk> (raw)

Hi,

I'm getting periodic oopses running KVM-33 on 2.6.23-rc1. Here is a digital 
photo of the oops. Alarmingly, a lot of the time it triple faults the machine 
and I don't get a chance to grab it. This time I was lucky, though.

http://devzero.co.uk/~alistair/kvm-2.6.23-rc1.jpg

Unfortunately, some of the oops text scrolled out of the screen. I will 
endeavour to reproduce the bug over serial console, but I can make no 
guarantees.

The CPU is an AMD X2 BE-2350, chipset is AMD 690G.

-- 
Cheers,
Alistair.

137/1 Warrender Park Road, Edinburgh, UK.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

             reply	other threads:[~2007-07-28 17:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-28 17:55 Alistair John Strachan [this message]
     [not found] ` <200707281855.41277.alistair-T7eSMZptz7IqdlJmJB21zg@public.gmane.org>
2007-07-29  8:16   ` 2.6.23-rc1, KVM-AMD problem Avi Kivity
     [not found]     ` <46AC4CEB.9060401-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-07-29 11:29       ` Alistair John Strachan
     [not found]         ` <200707291229.49155.alistair-T7eSMZptz7IqdlJmJB21zg@public.gmane.org>
2007-07-29 11:34           ` Avi Kivity
     [not found]             ` <46AC7B44.1040509-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-07-29 13:44               ` Alistair John Strachan
     [not found]                 ` <200707291444.18024.alistair-T7eSMZptz7IqdlJmJB21zg@public.gmane.org>
2007-07-29 13:47                   ` Avi Kivity
     [not found]                     ` <46AC9A8D.8060003-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-07-29 14:10                       ` Alistair John Strachan
     [not found]                         ` <200707291510.31731.alistair-T7eSMZptz7IqdlJmJB21zg@public.gmane.org>
2007-07-30 13:00                           ` Avi Kivity
     [not found]                             ` <46ADE0DD.1030505-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-07-30 17:00                               ` Alistair John Strachan
     [not found]                                 ` <200707301800.55671.alistair-T7eSMZptz7IqdlJmJB21zg@public.gmane.org>
2007-07-30 17:05                                   ` Avi Kivity
2007-08-04 13:17                               ` Prakash Punnoor
2007-08-04 14:24                                 ` Alistair John Strachan

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=200707281855.41277.alistair@devzero.co.uk \
    --to=alistair-t7esmzptz7iqdljmjb21zg@public.gmane.org \
    --cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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