All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gonzalo Medina Castro <gonzalo.medina.castro@grupomost.com>
To: xen-devel@lists.xensource.com
Subject: Re: Problem with Dom0 ( SuSE )
Date: Mon, 27 Feb 2006 06:56:15 -0800 (PST)	[thread overview]
Message-ID: <3146449.post@talk.nabble.com> (raw)
In-Reply-To: <fa5897f73f756b9acc3523d7f367d502@cl.cam.ac.uk>


When Dom0 freeze, after reboot it, I found this in messages log:

Feb 27 11:36:59 dbaxixen kernel: megaraid: aborting-912059 cmd=28 <c=2 t=1
l=0>
Feb 27 11:36:59 dbaxixen kernel: megaraid abort: scsi cmd:912059, do now own

I search in google, but I can't found a problem with this module for Xen.

The server is a DELL PowerEdge 2850, with an LSI Logic MegaRAID, I don't
know what only fail if I use disk access trough an ssh connection. If
someone have an idea, I appreciate that. Thanks.


--- Original Message ---
> 
> On 24 Feb 2006, at 19:24, Gonzalo Medina Castro wrote:
> 
> > I install Xen in a SuSE ES 9. The problem is that if I connect to the 
> > server
> > with ssh, and I try to make a tar, or copy files from another server 
> > with
> > rsync, Dom0 down, I neet to reboot it. If I do the same, but directly 
> > on the
> > server, nothing happends, only happend if I try to do this remotely.
> > Any ideas?
> 
> Perhaps a network card problem. Does dom0 print any error
> messages when 
> it fails? What NIC are you using?
> 
>   -- Keir
> 

--
View this message in context: http://www.nabble.com/Problem-with-Dom0-%28-SuSE-%29-t1182898.html#a3146449
Sent from the Xen - Dev forum at Nabble.com.

  reply	other threads:[~2006-02-27 14:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-24 19:24 Problem with Dom0 ( SuSE ) Gonzalo Medina Castro
2006-02-27 10:32 ` Keir Fraser
2006-02-27 14:56   ` Gonzalo Medina Castro [this message]
2006-02-27 15:34   ` Gonzalo Medina Castro
2006-02-28  8:52     ` Keir Fraser
2006-02-28 14:46       ` Gonzalo Medina Castro
2006-02-28 17:17         ` Keir Fraser

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=3146449.post@talk.nabble.com \
    --to=gonzalo.medina.castro@grupomost.com \
    --cc=xen-devel@lists.xensource.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 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.