Hi all,
my problem is that I have made in an Ubuntu 10.04 domU, pciback for a
Ethernet card, and when I try to ifup eth1, the system crash.
All seems ok, in fact, when I execute "lspci" in domU, I get the pci
id
device:
00:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708
Gigabit Ethernet (rev 12)
The network card driver is loaded fine. This is the result of dmesg |
grep -E "bnx2|eth" on domU:
[ 2.052897] Initialising Xen virtual ethernet driver.
[ 2.303866] Broadcom NetXtreme II Gigabit Ethernet Driver bnx2
v2.0.23b (Feb 01, 2011)
[ 2.304003] bnx2 0000:00:00.0: enabling device (0000 -> 0002)
[ 2.304237] bnx2 0000:00:00.0: Xen PCI enabling IRQ: 19
[ 2.320865] eth1: Broadcom NetXtreme II BCM5708 1000Base-T (B2) PCI-X
64-bit 133MHz found at mem d2000000, IRQ 19, node addr 00:10:18:39:9a:f0
[ 13.490065] eth0: no IPv6 routers present
When I execute "ifup eth1", the system hangs, and after force reboot,
I
get the next message:
[ 2.690875] ------------[ cut here ]------------
[ 2.690888] kernel BUG
at /home/kernel-ppa/COD/linux/drivers/pci/msi.c:314!
[ 2.690895] invalid opcode: 0000 [#1] SMP
[ 2.690903] last sysfs
file: /sys/devices/pci-0/pci0000:00/0000:00:00.0/device
[ 2.690910] CPU 0
[ 2.690914] Modules linked in: bnx2 lp xen_netfront parport
xen_pcifront xen_blkfront
[ 2.690932]
[ 2.690937] Pid: 400, comm: ifconfig Not tainted
2.6.37-020637-generic #201101050908 /
[ 2.690943] RIP: e030:[<ffffffff81300d7b>] [<ffffffff81300d7b>]
free_msi_irqs+0x8b/0x130
[ 2.690959] RSP: e02b:ffff880037d6bc58 EFLAGS: 00010286
[ 2.690964] RAX: ffff88003a018000 RBX: 0000000000000000 RCX:
ffff880039c00680
[ 2.690971] RDX: 0000000000000000 RSI: 00000000000000ff RDI:
ffff880039c00470
[ 2.690977] RBP: ffff880037d6bc88 R08: 0000000000000000 R09:
0000000000000000
[ 2.690983] R10: ffff88003ffe5a58 R11: 0000000000000000 R12:
ffff88003839ba80
[ 2.690990] R13: 0000000000000001 R14: ffff88003839ba90 R15:
ffff88003644c000
[ 2.690999] FS: 00007f4ee31d1700(0000) GS:ffff88003ffd2000(0000)
knlGS:0000000000000000
[ 2.691007] CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b
[ 2.691014] CR2: 00007f4ee2d7bbdc CR3: 0000000038795000 CR4:
0000000000002660
[ 2.691021] DR0: 0000000000000000 DR1: 0000000000000000 DR2:
0000000000000000
[ 2.691028] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7:
0000000000000400
[ 2.691035] Process ifconfig (pid: 400, threadinfo ffff880037d6a000,
task ffff880038385b00)
[ 2.691042] Stack:
[ 2.691046] ffff88003644c8f8 ffff88003644c000 ffff8800375f86c0
0000000000000000
[ 2.691059] ffff8800375f8700 ffffffffa00445f0 ffff880037d6bca8
ffffffff813015fd
[ 2.691071] 0000000100000001 0000000000000001 ffff880037d6bcd8
ffffffffa0040442
[ 2.691084] Call Trace:
[ 2.691094] [<ffffffffa00445f0>] ? bnx2_poll_msix+0x0/0xd0 [bnx2]
[ 2.691103] [<ffffffff813015fd>] pci_disable_msi+0x3d/0x50
[ 2.691111] [<ffffffffa0040442>] bnx2_free_irq+0xc2/0xd0 [bnx2]
[ 2.691120] [<ffffffffa00473ea>] bnx2_open+0x16a/0x42c [bnx2]
[ 2.691129] [<ffffffff814b690e>] __dev_open+0x8e/0xe0
[ 2.691137] [<ffffffff814b5a56>] __dev_change_flags+0x96/0x170
[ 2.691144] [<ffffffff814b62e8>] dev_change_flags+0x28/0x70
[ 2.691153] [<ffffffff8151b5e7>] devinet_ioctl+0x5c7/0x710
[ 2.691161] [<ffffffff8151c863>] inet_ioctl+0x63/0x80
[ 2.691168] [<ffffffff814a27b2>] sock_do_ioctl+0x32/0x60
[ 2.691175] [<ffffffff814a2d17>] sock_ioctl+0x107/0x280
[ 2.691184] [<ffffffff8116eafd>] vfs_ioctl+0x1d/0x50
[ 2.691190] [<ffffffff8116f5cd>] do_vfs_ioctl+0x6d/0x1f0
[ 2.691198] [<ffffffff8115d2d1>] ? sys_faccessat+0x171/0x1b0
[ 2.691206] [<ffffffff8116f7d7>] sys_ioctl+0x87/0xa0
[ 2.691214] [<ffffffff8100c0c2>] system_call_fastpath+0x16/0x1b
[ 2.691220] Code: ed 7e 22 31 db 89 df 41 03 7c 24 0c e8 9f fd dc ff
48 83 78 48 00 75 13 83 c3 01 44 39 eb 75 e5 49 8b 44 24 10 4c 8d 60 f0
eb a4 <0f> 0b eb fe 90 4c 89 ff ff 15 07 cf 70 00 4d 8b a7 f8 08 00 00
[ 2.691318] RIP [<ffffffff81300d7b>] free_msi_irqs+0x8b/0x130
[ 2.691326] RSP <ffff880037d6bc58>
[ 2.691332] ---[ end trace a66562e0bfc96760 ]---
The curious thing, is that the two IP address configured, are able to
respond to ping requests, but not at the ssh request.
Please, any help are wellcome.
Thanks in advance.
--
Francisco Barrera
francisco.barrera@empelt.es
http://www.empelt.es
________________________________________________________________________
Antes de imprimir este e-mail piense en su responsabilidad compromiso
con el medio ambiente
AVISO LEGAL
Este mensaje y los documentos anexos que pudiera incluir se dirige
exclusivamente a su/s destinatario/s y puede contener información
privilegiada o confidencial. Si no es ud. el destinatario del mensaje,
le rogamos que lo comunique inmediatamente al remitente y proceda a su
destrucción. La utilización, grabación, divulgación, copia o cualquier
otro uso de la información sin el consentimiento de EMPELT está
prohibida en virtud de la legislación vigente.
EMPELT cumple la Ley Orgánica 15/99 de 14 de Diciembre de Protección de
Datos de Carácter Personal. Su e-mail y datos personales pueden estar
incluidos en un fichero para su tratamiento. En cualquier momento puede
ejercer sus derechos de acceso, rectificación, cancelación y oposición,
mediante el envío de un e-mail o comunicación por escrito.
________________________________________________________________________
Before printing think about your responsability and commitment with the
environment
DISCLAIMER
This message and all its attached documents is intended exclusively for
its addressee(s) and may contain information that is confidential and
protected by a professional privilege or whose disclosure is prohibited
by law. If this message has been received by mistake, please we require
to notify the sender immediately via e-mail and delete it. Any
dissemination, copy, disclosure or, in any other way, using any of the
information without the EMPELT consent is strictly prohibited by law.
EMPELT meets the Organica Law 15/99 of December 14 for the Protection of
Personal Data. Your e-mail and personal information can be included in a
file for treatment. In any moment you can exercise their rigths of
access, rectification, cancellation and oposition by sending and e-mail
or written communication.
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users