WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] dom0 crash, require assistance interpretting logs and c

To: Ben Holt <ben@xxxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] dom0 crash, require assistance interpretting logs and config suggestions
From: "Fajar A. Nugraha" <fajar@xxxxxxxxx>
Date: Tue, 13 Apr 2010 13:16:36 +0700
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 12 Apr 2010 23:17:47 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4BC22D19.2070801@xxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <4BC22D19.2070801@xxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Mon, Apr 12, 2010 at 3:12 AM, Ben Holt <ben@xxxxxxxxxxxxxxxx> wrote:
> Hello,
>
> I have experienced a dom0 crash where the system became unreachable via the
> network and the console was unresponsive.  I would appreciate help
> interpretting the logs and any configuration change suggestions.
>
> It is a stock Debian Lenny dom0 running xen 3.2.1 with kernel
> 2.6.26-2-xen-amd64 and an AMD Athlon IIx4 with 4 GB of RAM.

that's a somewhat old, known-to-have-bugs kernel. The bugs might not
be directly related to your problems though.


> Apr 11 04:23:00 xenserver kernel: [277145.647458] ata2.00: status: { DRDY }
> Apr 11 04:23:00 xenserver kernel: [277145.647467] ata2: hard resetting link
> Apr 11 04:23:00 xenserver kernel: [277145.647486] ata1.00: exception Emask
> 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
> Apr 11 04:23:00 xenserver kernel: [277145.647496] ata1.00: cmd
> ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
> Apr 11 04:23:00 xenserver kernel: [277145.647497]          res
> 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> Apr 11 04:23:00 xenserver kernel: [277145.647515] ata1.00: status: { DRDY }
> Apr 11 04:23:00 xenserver kernel: [277145.647523] ata1: hard resetting link
> Apr 11 04:23:01 xenserver kernel: [277146.131362] ata2: softreset failed
> (device not ready)
> Apr 11 04:23:01 xenserver kernel: [277146.131378] ata2: failed due to HW
> bug, retry pmp=0

I'd start by making sure the HW itself is fine (perhaps by booting a
normal, non-xen, known-good kernel and doing something like "dd
if=/dev/sda of=/dev/null bs=1M").

Have you tried latest opensuse xen kernel?
http://code.google.com/p/gentoo-xen-kernel/downloads/list

-- 
Fajar

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users