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-devel

Re: [Xen-devel] ata_piix SATA driver - Invalid opcode?!

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] ata_piix SATA driver - Invalid opcode?!
From: Adam Nielsen <adam.nielsen@xxxxxxxxx>
Date: Fri, 9 Jun 2006 12:22:16 +1000
Delivery-date: Thu, 08 Jun 2006 19:22:42 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20060608144133.6b969846@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20060608144133.6b969846@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> Does anyone know of any issues with the ata_piix (Intel ICH5/6) driver
> and SATA disks?  Has anyone got this configuration going?

I just tried switching the BIOS on this PC to SATA 'combination' mode,
which I've used in the past to access the disks using the normal PIIX
IDE driver.  Unfortunately that results in a bad crash - it looks like
Xen just isn't going to work on this PC :-(

Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ide0: I/O resource 0x1F0-0x1F7 not free.
ide0: ports already in use, skipping probe
(XEN) BUG at irq.c:541
(XEN) ----[ Xen-3.0.2-2    Not tainted ]----
(XEN) CPU:    0
(XEN) EIP:    e008:[<ff11dea5>] pirq_guest_unbind+0x1f5/0x320
(XEN) EFLAGS: 00010096   CONTEXT: hypervisor
(XEN) eax: 00000000   ebx: ffbe6380   ecx: 00000001   edx: 00000000
(XEN) esi: ff18bd00   edi: ff162e00   ebp: 00000246   esp: ff175f04
(XEN) cr0: 8005003b   cr3: 3ee77000
(XEN) ds: e010   es: e010   fs: 0000   gs: 0000   ss: e010   cs: e008
(XEN) Xen stack trace from esp=ff175f04:
(XEN)    ff159779 ff162e00 0000021d 00000001 00000001 00000000 00000058 ffbf4ac0
(XEN)    00000010 00000000 ffbf0080 ff1053e3 ffbf0080 00000009 ffbe9080 ff114ab7
(XEN)    14d473e0 00000000 00000000 ffffffda ff175f84 c1521ea4 c1520000 ff105637
(XEN)    ffbf0080 00000010 c1521ea4 ff105c7a ff175f88 c1521ea4 0000001c 00000000
(XEN)    00000003 00000010 00000000 00000000 00000000 00000000 00000000 ffbe9080
(XEN)    ffbe9080 00000009 00000010 ff14a463 c1521ea4 00000000 fbfc5000 00000009
(XEN)    00000010 c1520000 00000010 000d0000 c0101207 00000061 00000203 c1521ea0
(XEN)    0000e021 0000007b 0000007b 00000000 00000000 00000000 ffbe9080
(XEN) Xen call trace:
(XEN)    [<ff11dea5>] pirq_guest_unbind+0x1f5/0x320
(XEN)    [<ff1053e3>] __evtchn_close+0x73/0x2a0
(XEN)    [<ff114ab7>] reprogram_timer+0x27/0xd0
(XEN)    [<ff105637>] evtchn_close+0x27/0x30
(XEN)    [<ff105c7a>] do_event_channel_op+0xda/0x140
(XEN)    [<ff14a463>] hypercall+0x53/0x57
(XEN)
(XEN) ************************************
(XEN) CPU0 FATAL TRAP 6 (invalid opcode), ERROR_CODE 0000, IN INTERRUPT CONTEXT.
(XEN) System shutting down -- need manual reset.
(XEN) ************************************

Cheers,
Adam.

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