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

[Xen-users] pciback lost interrupt / dma_timer_expiry / DMA interrupt re

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] pciback lost interrupt / dma_timer_expiry / DMA interrupt recovery
From: Ben Low <ben@xxxxxxxxx>
Date: Tue, 12 Jun 2007 11:30:56 +1000
Delivery-date: Tue, 12 Jun 2007 09:59:10 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Reply-to: Ben Low <ben-dated-1184030979.fda5c8@xxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hello,

I'm attempting to use the pciback module to pass a USB PCI card to a domU, however shortly after booting the domU my dom0 locks up with 'lost interrupt' and 'dma_timer_expiry' messages to the console. (This is with Xen 3.0.3-1, dom0 and domU's: 2.6.18-4-xen-686 (Debian))

hdc: lost interrupt
hda: dma_timer_expiry: dma status == 0x24
hdc: dma_timer_expiry: dma status == 0x24
ata1: soft resetting port
hda: DMA interrupt recovery
hda: lost interrupt
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: lost interrupt
hda: dma_timer_expiry: dma status == 0x24

I see that a number of other people have reported similar problems:
  http://www.redhat.com/archives/fedora-xen/2006-December/msg00128.html
  http://bugs.centos.org/view.php?id=2021
http://lists.xensource.com/archives/html/xen-users/2006-08/ msg00506.html

These two report similar problems with the domU only (i.e. seems that their dom0 is unaffected): http://lists.xensource.com/archives/html/xen-users/2006-09/ msg00190.html http://lists.xensource.com/archives/html/xen-users/2007-01/ msg00202.html

I'm using pciback to pass a NIC to another domU without any problems - it only seems to occur with the USB card. My system (a Gigabyte GA-8IG1000 motherboard, Intel 865G chipset) shares an IRQ between the on-board USB and IDE/ATA controller - though the USB device I'm trying to pass to the domU is a separate PCI card. With pciback as a module, I'm using the /proc unbind/bind method per the Xen wiki.

dom0# cat /proc/interrupts
           CPU0
  3:          1        Phys-irq  serial
  8:          1        Phys-irq  rtc
  9:          0        Phys-irq  acpi
14:     421010        Phys-irq  ide0
15:    1078091        Phys-irq  ide1
16:          0        Phys-irq  uhci_hcd:usb1, uhci_hcd:usb4
17:          0        Phys-irq  uhci_hcd:usb2
18:     629111        Phys-irq  uhci_hcd:usb3, libata
20:    3185099        Phys-irq  ehci_hcd:usb7
22:    4691928        Phys-irq  plan0
256:    7226629     Dynamic-irq  timer0
257:          0     Dynamic-irq  resched0
258:          0     Dynamic-irq  callfunc0
259:       5435     Dynamic-irq  xenbus
260:        118     Dynamic-irq  console
261:      14453     Dynamic-irq  blkif-backend
262:         42     Dynamic-irq  blkif-backend
263:       1869     Dynamic-irq  blkif-backend
264:        169     Dynamic-irq  blkif-backend
265:     194584     Dynamic-irq  blkif-backend
266:         90     Dynamic-irq  blkif-backend
267:    1191948     Dynamic-irq  vif2.0
268:        305     Dynamic-irq  pciback
269:      63860     Dynamic-irq  blkif-backend
270:       2184     Dynamic-irq  blkif-backend
271:       3717     Dynamic-irq  blkif-backend
272:      13319     Dynamic-irq  blkif-backend
NMI:          0
LOC:          0
ERR:          0
MIS:          0

The separate network card uses IRQ 21, the separate USB card uses IRQs 16, 19, 21.

As others have reported success for using pciback in a similar arrangement, I wonder if the problem is hardware specific (the issue reported to the fedore-xen list also was with a 865G chipset).

Any suggestions for troubleshooting this?

--
Ben Low
ben@xxxxxxxxx

"Never mistake motion for action." - Ernest Hemingway (1899-1961)

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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] pciback lost interrupt / dma_timer_expiry / DMA interrupt recovery, Ben Low <=