| |
|
 |
|
 |
|
|
|
| |
|
|
xen-users
Re: [Xen-users] Ethernet modules craches in domU with pci passthrough
On Wed, Feb 10, 2010 at 09:44:08PM +0200, Andrey Luzgin wrote:
> I do not know where to search, help, please, anybody.
>
> This is error part of dmesg from domU (details of system below):
>
> udev: starting version 146
> Broadcom NetXtreme II Gigabit Ethernet Driver bnx2 v2.0.1 (May 6, 2009)
> bnx2 0000:02:00.0: enabling device (0000 -> 0002)
> alloc irq_desc for 32 on node 0
> alloc kstat_irqs on node 0
> ------------[ cut here ]------------
> Kernel BUG at ffffffff8044e6f5 [verbose debug info unavailable]
> invalid opcode: 0000 [#1] SMP
> last sysfs file: /sys/devices/xen/vbd-51713/block/xvda1/removable
> CPU 0
> Modules linked in: bnx2(+)
> Pid: 1271, comm: modprobe Not tainted 2.6.31-xen-r10 #10
> RIP: e030:[<ffffffff8044e6f5>] [<ffffffff8044e6f5>] 0xffffffff8044e6f5
> RSP: e02b:ffff8801b3d19cc8 EFLAGS: 00010216
> RAX: ffff8801b42ff840 RBX: 0000000000000020 RCX: 0000000000000000
> RDX: 0000000000007900 RSI: 0000000000000000 RDI: 0000000000000020
> RBP: 0000000000000001 R08: 00000000ffffffff R09: 0000000000007900
> R10: 00000b0b00000000 R11: 0000000000000020 R12: 00000000fffffff4
> R13: ffff8801b5047090 R14: ffff8801b535c000 R15: ffff8801b5047000
> FS: 00007fcd29a366f0(0000) GS:ffffc90000000000(0000)
> knlGS:0000000000000000
> CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b
> CR2: 00007fcbb162600f CR3: 00000001b3056000 CR4: 0000000000002660
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> Process modprobe (pid: 1271, threadinfo ffff8801b3d18000, task
> ffff8801b4be1d60)
> Stack:
> ffff8801b5047000 ffffffff8048f214 ffff8801b535c000 20ffffff80490283
> <0> ffff8801b5047000 ffffffff803ea39f ffffffffa000c530 ffff8801b5047000
> <0> ffff8801b535c580 ffffffff803ea404 ffffffffa000c590 ffffffffa0009e25
> Call Trace:
> [<ffffffff8048f214>] ? 0xffffffff8048f214
> [<ffffffff803ea39f>] ? 0xffffffff803ea39f
> [<ffffffff803ea404>] ? 0xffffffff803ea404
> [<ffffffffa0009e25>] ? 0xffffffffa0009e25
> [<ffffffff802ca492>] ? 0xffffffff802ca492
> [<ffffffff8030c7ce>] ? 0xffffffff8030c7ce
> [<ffffffff803eb032>] ? 0xffffffff803eb032
> [<ffffffff803eb7f1>] ? 0xffffffff803eb7f1
> [<ffffffff80444b7f>] ? 0xffffffff80444b7f
> [<ffffffff80444c69>] ? 0xffffffff80444c69
> [<ffffffff80444c1a>] ? 0xffffffff80444c1a
> [<ffffffff80444467>] ? 0xffffffff80444467
> [<ffffffff80443e2d>] ? 0xffffffff80443e2d
> [<ffffffff80444f03>] ? 0xffffffff80444f03
> [<ffffffffa0010000>] ? 0xffffffffa0010000
> [<ffffffff803ebc29>] ? 0xffffffff803ebc29
> [<ffffffffa0010000>] ? 0xffffffffa0010000
> [<ffffffff80207051>] ? 0xffffffff80207051
> [<ffffffff80258fcd>] ? 0xffffffff80258fcd
> [<ffffffff802093f8>] ? 0xffffffff802093f8
> [<ffffffff80209390>] ? 0xffffffff80209390
> Code: 44 f8 ff 41 89 c6 3b 05 ea 71 20 00 0f 82 b1 fd ff ff 48 83 c4 68 31
> c0 5b 5d 41 5c 41 5d 41 5e 41 5f c3 53 83 ff 0f 89 fb 76 04 <0f> 0b eb fe
> 7e 55 e8 88 f1 e1 ff 48 85 c0 74 10 48 8b 40 38 48
> RIP [<ffffffff8044e6f5>] 0xffffffff8044e6f5
> RSP <ffff8801b3d19cc8>
> ---[ end trace c14fe0c5cc1cd90d ]---
>
You need to recompile the kernel with debug information so you can actually
see the function names in the stack trace above.
Also you could use xenctx from dom0 do get a stack trace, see:
http://wiki.xensource.com/xenwiki/XenCommonProblems
There's a chapter about getting a stacktrace with xenctx.
Also, do you have errors in "xm dmesg" ?
-- Pasi
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
| |
|
Home