[Xen-bugs] [Bug 915] VPCI crashes domU kernel with dedicated NIC when changing MTU to 9000

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=915


muhammad.atif@xxxxxxxxxx changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |muhammad.atif@xxxxxxxxxx




------- Comment #2 from muhammad.atif@xxxxxxxxxx  2007-09-06 20:49 -------
I am facing the same issue. I am using Xen 3.1.0, Hardware is x86_64, with
IWILL motherboard. I have exported the PCI to domU through PCI back and have
tried various other values for MTU, it crashes on all of them. I have tried
swiotld=force parameter for dom0 at boot time, it has no effect.

My log is..
-------------------------------------------------------------------------------

[  243.220048] Fatal DMA error! Please use 'swiotlb=force'
[  243.220073] ----------- [cut here ] --------- [please bite here ] ---------
[  243.220078] Kernel BUG at
arch/x86_64/kernel/../../i386/kernel/pci-dma-xen.c:341
[  243.220082] invalid opcode: 0000 [1] SMP
[  243.220086] CPU 0
[  243.220089] Modules linked in: ipv6 nfs lockd sunrpc evdev e1000 pcspkr
af_packet 8250 serial_core ext3 jbd mbcache raid10 raid456 xor raid1 raid0
multipath linear md_mod dm_mod
[  243.220112] Pid: 2961, comm: ifconfig Not tainted 2.6.19-4-generic-amd64 #2
[  243.220116] RIP: e030:[<ffffffff80277e82>]  [<ffffffff80277e82>]
dma_map_single+0x162/0x1e0
[  243.220127] RSP: e02b:ffff88001e9d9cd8  EFLAGS: 00010292
[  243.220131] RAX: 000000000000003e RBX: ffff88001eb1c012 RCX:
ffffffff80493388
[  243.220134] RDX: ffffffff80493388 RSI: 0000000000000001 RDI:
0000000000000000
[  243.220137] RBP: 0000000005588012 R08: 0000000000000000 R09:
0000000000000000
[  243.220141] R10: 000000000000003c R11: 0000000000000000 R12:
0000000000002000
[  243.220145] R13: ffff880001834870 R14: ffffc20000014000 R15:
ffff88001fee1500
[  243.220153] FS:  00002b1d622d96f0(0000) GS:ffffffff8053b000(0000)
knlGS:0000000000000000
[  243.220157] CS:  e033 DS: 0000 ES: 0000 CR0: 000000008005003b
[  243.220160] CR2: 0000000000000000 CR3: 000000001eb22000 CR4:
0000000000000660
[  243.220164] Process ifconfig (pid: 2961, threadinfo ffff88001e9d8000, task
ffff88001eeaa180)
[  243.220167] Stack:  0000000000000000 ffff88001eb1c012 ffff88001fd4a280
0000000000000001
[  243.220175]  0000000000000000 ffffffff880c7303 ffff8800018e0a80
0000000000000000
[  243.220181]  ffff880001834870 0000000000002002 000000ff000000ff
ffff8800000d9c40
[  243.220187] Call Trace:
[  243.220201]  [<ffffffff880c7303>] :e1000:e1000_alloc_rx_buffers+0x243/0x370
[  243.220212]  [<ffffffff880c4616>] :e1000:e1000_up+0x2d6/0x330
[  243.220220]  [<ffffffff880c46dc>] :e1000:e1000_reinit_locked+0x6c/0x80
[  243.220229]  [<ffffffff880c673b>] :e1000:e1000_change_mtu+0x21b/0x250
[  243.220237]  [<ffffffff803ca828>] __dev_get_by_name+0x88/0xa0
[  243.220242]  [<ffffffff803ca56f>] dev_set_mtu+0x2f/0x70
[  243.220248]  [<ffffffff803cc564>] dev_ioctl+0x2a4/0x3c0
[  243.220253]  [<ffffffff8026a079>] _spin_lock_irqsave+0x9/0x20
[  243.220259]  [<ffffffff802248b1>] __up_read+0x21/0xb0
[  243.220266]  [<ffffffff803c21f0>] sock_ioctl+0x230/0x260
[  243.220272]  [<ffffffff80246ddf>] do_ioctl+0x2f/0xa0
[  243.220277]  [<ffffffff80233de3>] vfs_ioctl+0x293/0x2d0
[  243.220283]  [<ffffffff802523ac>] sys_ioctl+0x6c/0xb0
[  243.220289]  [<ffffffff80265a86>] system_call+0x86/0x8b
[  243.220294]  [<ffffffff80265a00>] system_call+0x0/0x8b
[  243.220298]
[  243.220299]
[  243.220300] Code: 0f 0b 68 d8 73 44 80 c2 55 01 0f 1f 40 00 4d 85 ed 74 1b
49
[  243.220316] RIP  [<ffffffff80277e82>] dma_map_single+0x162/0x1e0
[  243.220321]  RSP <ffff88001e9d9cd8>
[  243.220324]  Segmentation fault
root@vp202:~#
Message from syslogd@node02 at Fri Sep  7 04:42:25 2007 ...
node02 kernel: [  243.220082] invalid opcode: 0000 [1] SMP


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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