Re: [Xen-users] DomU with PCI passthrough NIC crashes with fatal DMA error

[Hans Rakers <hans@xxxxxxxx>]

In addition, i just tried the CentOS Plus Xen kernel which has the 
eepro100 driver. Using eepro100 it craps out during boot while 
configuring the interface. Seems there's some major DMA issues when 
using PCI passthrough NICs :{
Backtrace using eepro100 follows:

Bringing up loopback interface:  [  OK  ]
Bringing up interface eth0:  Fatal DMA error! Please use 'swiotlb=force'
----------- [cut here ] --------- [please bite here ] ---------
Kernel BUG at arch/x86_64/kernel/../../i386/kernel/pci-dma-xen.c:365
invalid opcode: 0000 [1] SMP
last sysfs file: /class/net/eth0/address
CPU 0
Modules linked in: ipv6 dm_multipath parport_pc lp parport eepro100 mii 
pcspkr dm_snapshot dm_zero dm_mirror dm_mod xenblk ext3 jbd ehci_hcd 
ohci_hcd uhci_hcd
Pid: 1035, comm: arping Not tainted 2.6.18-53.1.4.el5.centos.plusxen #1
RIP: e030:[<ffffffff8026e9b3>]  [<ffffffff8026e9b3>] 
dma_map_single+0x16b/0x180
RSP: e02b:ffff88001d55bb98  EFLAGS: 00010086
RAX: 000000000000002f RBX: ffff880000df7c02 RCX: ffff88001ff1f070
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000001
RBP: 00000001141dec02 R08: ffff88001f1a79f8 R09: ffff88001d55bb08
R10: 0000000000001b3c R11: ffff88001f4c7078 R12: 000000000000002a
R13: ffff88001ff1f070 R14: ffff88001e47b4c0 R15: ffffc200001ea000
FS:  00002aaaab22baf0(0000) GS:ffffffff8059b000(0000) knlGS:0000000000000000
CS:  e033 DS: 0000 ES: 0000
Process arping (pid: 1035, threadinfo ffff88001d55a000, task 
ffff88001f4e0040)
Stack:  00000000000004d0  ffff88001ed4e000  ffff88001f53d500 
0000000000000100
 ffff88001f53d000  ffffffff880da78c  0000000000000000  ffff88001f53d000
 ffff88001e47b4c0  0000000000000000
Call Trace:
 [<ffffffff880da78c>] :eepro100:speedo_start_xmit+0x136/0x274
 [<ffffffff8040df2a>] __qdisc_run+0xf6/0x1bb
 [<ffffffff8022fdf5>] dev_queue_xmit+0x1ee/0x313
 [<ffffffff8044b5f1>] packet_sendmsg+0x216/0x26c
 [<ffffffff802538c4>] sock_sendmsg+0xf3/0x110
 [<ffffffff80294356>] autoremove_wake_function+0x0/0x2e
 [<ffffffff8026190f>] _read_lock_irq+0x9/0x19
 [<ffffffff802071cf>] find_get_page+0x44/0x4b
 [<ffffffff8021330d>] filemap_nopage+0x188/0x322
 [<ffffffff80208e30>] __handle_mm_fault+0x668/0xf4d
 [<ffffffff803f76a5>] sys_sendto+0x11c/0x14f
 [<ffffffff803f7894>] move_addr_to_user+0x5d/0x78
 [<ffffffff8026187d>] _spin_lock_irq+0x9/0x14
 [<ffffffff80228ace>] do_sigaction+0x189/0x19d
 [<ffffffff802409af>] do_ioctl+0x21/0x6b
 [<ffffffff8025d102>] system_call+0x86/0x8b
 [<ffffffff8025d07c>] system_call+0x0/0x8b


Code: 0f 0b 68 38 1b 47 80 c2 6d 01 59 5b 48 89 e8 5d 41 5c 41 5d
RIP  [<ffffffff8026e9b3>] dma_map_single+0x16b/0x180
 RSP <ffff88001d55bb98>
 <0>Kernel panic - not syncing: Fatal exception



Hans Rakers wrote:
> Hi list,
>
> One of my CentOS 5.1 DomU's is regularly crashing on network activity. 
> It has a pci passthrough for direct communication to a Intel 
> Etherexpress 100 card (e100 driver).
> I managed to grab a kernel crash backtrace through the xen console:
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users