Sebastien Villanueva Thurmes
2009-Dec-27 21:13 UTC
[Xen-users] running XEN on DELL R200 with SAS6iR ( raid 1 )
Hi,
i try to use XEN 3.2.1-amd64 /Debian gnu linux, kernel 2.6.26-2-xen-amd64 on a
dell poweredge R200 server.
This server use two HDD with a LSISAS1068E raid controller to make the raid
mirroring.
Unfortunatelly, it seems there are some hardware troubles.
Troubles begin with : floppy unable to grab DMA2
ioc0 LSISAS1068e b3 capabilities initator
floppy 0 no floppy controllers found
mptbase: ioc0: initiate recovery
mptbase: ioc0: initiate recovery
mptbase: ioc0: initiate recovery
scsi0: ioc0: LSISAS1068e B3, FwRev = 00192
here is the first big with call traces.
and then i have
16:41:39 db1 kernel: ata1.00: qc timeout (cmd 0xa0)
16:41:39 db1 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
frozen
16:41:39 db1 kernel: ata1.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
16:41:39 db1 kernel: cdb 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00
16:41:39 db1 kernel: res 51/20:03:00:00:00/00:00:00:00:00/a0 Emask 0x5
(timeout)
16:41:39 db1 kernel: ata1.00: status: { DRDY ERR }
16:41:44 db1 kernel: ata1: link is slow to respond, please be patient (ready=0)
16:41:49 db1 kernel: ata1: device not ready (errno=-16), forcing hardreset
16:41:49 db1 kernel: ata1: soft resetting link
16:41:49 db1 kernel: ata1: nv_mode_filter: 0x701f&0x701f->0x701f,
BIOS=0x7000 (0xc0000000) ACPI=0x701f (60:900:0x11)
16:41:49 db1 kernel: ata1.00: configured for UDMA/33
16:41:49 db1 kernel: ata1: EH complete
16:41:54 db1 kernel: ata1.00: qc timeout (cmd 0xa0)
16:41:54 db1 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
frozen
16:41:54 db1 kernel: ata1.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
16:41:54 db1 kernel: cdb 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00
16:41:54 db1 kernel: res 51/20:03:00:00:00/00:00:00:00:00/a0 Emask 0x5
(timeout)
16:41:54 db1 kernel: ata1.00: status: { DRDY ERR }
16:41:59 db1 kernel: ata1: link is slow to respond, please be patient (ready=0)
16:42:04 db1 kernel: ata1: device not ready (errno=-16), forcing hardreset
16:42:04 db1 kernel: ata1: soft resetting link
16:42:04 db1 kernel: ata1: nv_mode_filter: 0x701f&0x701f->0x701f,
BIOS=0x7000 (0xc0000000) ACPI=0x701f (60:900:0x11)
16:42:04 db1 kernel: ata1.00: configured for UDMA/33
16:42:04 db1 kernel: ata1: EH complete
Is there a solution to solve this problem?
Thank you in advance.
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Nick Couchman
2009-Dec-28 03:39 UTC
Re: [Xen-users] running XEN on DELL R200 with SAS6iR ( raid 1 )
I don''t have a solution for you, but I can tell you that I run SLES 10 SP2 with Xen on the PowerEdge R200 platform - Xen 3.2.1 and kernel 2.6.16 - without any trouble. I use the integrated SAS6iR with a RAID1. -Nick>>> On 2009/12/27 at 14:13, Sebastien Villanueva Thurmes<s.villanueva@symbiote-technology.be> wrote:> Hi, > > i try to use XEN 3.2.1-amd64 /Debian gnu linux, kernel 2.6.26-2-xen-amd64 on a > dell poweredge R200 server. > > This server use two HDD with a LSISAS1068E raid controller to make the raid > mirroring. > > Unfortunatelly, it seems there are some hardware troubles. > > Troubles begin with : floppy unable to grab DMA2 > ioc0 LSISAS1068e b3 capabilities initator > floppy 0 no floppy controllers found > mptbase: ioc0: initiate recovery > mptbase: ioc0: initiate recovery > mptbase: ioc0: initiate recovery > > > scsi0: ioc0: LSISAS1068e B3, FwRev = 00192 > > here is the first big with call traces. > > and then i have > > 16:41:39 db1 kernel: ata1.00: qc timeout (cmd 0xa0) > 16:41:39 db1 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action > 0x6 frozen > 16:41:39 db1 kernel: ata1.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0 > 16:41:39 db1 kernel: cdb 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 > 16:41:39 db1 kernel: res 51/20:03:00:00:00/00:00:00:00:00/a0 Emask > 0x5 (timeout) > 16:41:39 db1 kernel: ata1.00: status: { DRDY ERR } > 16:41:44 db1 kernel: ata1: link is slow to respond, please be patient > (ready=0) > 16:41:49 db1 kernel: ata1: device not ready (errno=-16), forcing hardreset > 16:41:49 db1 kernel: ata1: soft resetting link > 16:41:49 db1 kernel: ata1: nv_mode_filter: 0x701f&0x701f->0x701f, BIOS=0x7000 > (0xc0000000) ACPI=0x701f (60:900:0x11) > 16:41:49 db1 kernel: ata1.00: configured for UDMA/33 > 16:41:49 db1 kernel: ata1: EH complete > 16:41:54 db1 kernel: ata1.00: qc timeout (cmd 0xa0) > 16:41:54 db1 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action > 0x6 frozen > 16:41:54 db1 kernel: ata1.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0 > 16:41:54 db1 kernel: cdb 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 > 16:41:54 db1 kernel: res 51/20:03:00:00:00/00:00:00:00:00/a0 Emask > 0x5 (timeout) > 16:41:54 db1 kernel: ata1.00: status: { DRDY ERR } > 16:41:59 db1 kernel: ata1: link is slow to respond, please be patient > (ready=0) > 16:42:04 db1 kernel: ata1: device not ready (errno=-16), forcing hardreset > 16:42:04 db1 kernel: ata1: soft resetting link > 16:42:04 db1 kernel: ata1: nv_mode_filter: 0x701f&0x701f->0x701f, BIOS=0x7000 > (0xc0000000) ACPI=0x701f (60:900:0x11) > 16:42:04 db1 kernel: ata1.00: configured for UDMA/33 > 16:42:04 db1 kernel: ata1: EH complete > > Is there a solution to solve this problem? > > Thank you in advance.-------- This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Stefano Zanella
2009-Dec-28 09:19 UTC
Re: [Xen-users] running XEN on DELL R200 with SAS6iR ( raid 1 )
I haven''t a solution too, but I''ve started working with Xen on
two Dell R710
about 6 months ago; I first tried to install Debian (both Lenny and Squeeze,
i386 and amd64) but all my trials failed due to SAS controller troubles (at
most I was able to see disks during install, but system never finished a
bootstrap correctly). I ended up by installing CentOS with kernel 2.6.18.
Maybe these issues are still around...
Regards,
Stefano
On Mon, Dec 28, 2009 at 4:39 AM, Nick Couchman
<Nick.Couchman@seakr.com>wrote:
> I don''t have a solution for you, but I can tell you that I run
SLES 10 SP2
> with Xen on the PowerEdge R200 platform - Xen 3.2.1 and kernel 2.6.16 -
> without any trouble. I use the integrated SAS6iR with a RAID1.
>
> -Nick
>
> >>> On 2009/12/27 at 14:13, Sebastien Villanueva Thurmes
> <s.villanueva@symbiote-technology.be> wrote:
> > Hi,
> >
> > i try to use XEN 3.2.1-amd64 /Debian gnu linux, kernel
2.6.26-2-xen-amd64
> on a
> > dell poweredge R200 server.
> >
> > This server use two HDD with a LSISAS1068E raid controller to make the
> raid
> > mirroring.
> >
> > Unfortunatelly, it seems there are some hardware troubles.
> >
> > Troubles begin with : floppy unable to grab DMA2
> > ioc0 LSISAS1068e b3 capabilities initator
> > floppy 0 no floppy controllers found
> > mptbase: ioc0: initiate recovery
> > mptbase: ioc0: initiate recovery
> > mptbase: ioc0: initiate recovery
> >
> >
> > scsi0: ioc0: LSISAS1068e B3, FwRev = 00192
> >
> > here is the first big with call traces.
> >
> > and then i have
> >
> > 16:41:39 db1 kernel: ata1.00: qc timeout (cmd 0xa0)
> > 16:41:39 db1 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0
> action
> > 0x6 frozen
> > 16:41:39 db1 kernel: ata1.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0
> tag 0
> > 16:41:39 db1 kernel: cdb 00 00 00 00 00 00 00 00 00 00 00
00
> 00
> > 00 00 00
> > 16:41:39 db1 kernel: res 51/20:03:00:00:00/00:00:00:00:00/a0
> Emask
> > 0x5 (timeout)
> > 16:41:39 db1 kernel: ata1.00: status: { DRDY ERR }
> > 16:41:44 db1 kernel: ata1: link is slow to respond, please be patient
> > (ready=0)
> > 16:41:49 db1 kernel: ata1: device not ready (errno=-16), forcing
> hardreset
> > 16:41:49 db1 kernel: ata1: soft resetting link
> > 16:41:49 db1 kernel: ata1: nv_mode_filter:
0x701f&0x701f->0x701f,
> BIOS=0x7000
> > (0xc0000000) ACPI=0x701f (60:900:0x11)
> > 16:41:49 db1 kernel: ata1.00: configured for UDMA/33
> > 16:41:49 db1 kernel: ata1: EH complete
> > 16:41:54 db1 kernel: ata1.00: qc timeout (cmd 0xa0)
> > 16:41:54 db1 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0
> action
> > 0x6 frozen
> > 16:41:54 db1 kernel: ata1.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0
> tag 0
> > 16:41:54 db1 kernel: cdb 00 00 00 00 00 00 00 00 00 00 00
00
> 00
> > 00 00 00
> > 16:41:54 db1 kernel: res 51/20:03:00:00:00/00:00:00:00:00/a0
> Emask
> > 0x5 (timeout)
> > 16:41:54 db1 kernel: ata1.00: status: { DRDY ERR }
> > 16:41:59 db1 kernel: ata1: link is slow to respond, please be patient
> > (ready=0)
> > 16:42:04 db1 kernel: ata1: device not ready (errno=-16), forcing
> hardreset
> > 16:42:04 db1 kernel: ata1: soft resetting link
> > 16:42:04 db1 kernel: ata1: nv_mode_filter:
0x701f&0x701f->0x701f,
> BIOS=0x7000
> > (0xc0000000) ACPI=0x701f (60:900:0x11)
> > 16:42:04 db1 kernel: ata1.00: configured for UDMA/33
> > 16:42:04 db1 kernel: ata1: EH complete
> >
> > Is there a solution to solve this problem?
> >
> > Thank you in advance.
>
>
>
> --------
> This e-mail may contain confidential and privileged material for the sole
> use of the intended recipient. If this email is not intended for you, or
> you are not responsible for the delivery of this message to the intended
> recipient, please note that this message may contain SEAKR Engineering
> (SEAKR) Privileged/Proprietary Information. In such a case, you are
> strictly prohibited from downloading, photocopying, distributing or
> otherwise using this message, its contents or attachments in any way. If
> you have received this message in error, please notify us immediately by
> replying to this e-mail and delete the message from your mailbox.
> Information contained in this message that does not relate to the business
> of SEAKR is neither endorsed by nor attributable to SEAKR.
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users