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] Intel Quad NIC made visible in guest -> system crash

To: Xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Intel Quad NIC made visible in guest -> system crash
From: Alexander Menk <alex.menk.lists2@xxxxxxxxxxxxxx>
Date: Tue, 09 Jun 2009 12:32:54 +0300
Cc:
Delivery-date: Tue, 09 Jun 2009 02:33:42 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:content-type :date:message-id:mime-version:x-mailer:content-transfer-encoding; bh=9Iuc8/zzDEIKDlCH47iJ9Akyv3/vickwExhmnWvmthI=; b=wEgWDCi0gMzr1gAxs4Y+NixLrcVorWPOhP9J+UtK2fGcTCHSOjDX/uUQnVe2GhHoN5 WSNfKlbeBXlALBCiK3POTBK8KvQ0tBpR0QPtbynsZU1aoaaK6Cd3qjSroQkZmNbSusCT HKfLROITjvYdPGk9AmTr/mk+ihesT4d8OvOmI=
Domainkey-signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=subject:from:to:content-type:date:message-id:mime-version:x-mailer :content-transfer-encoding; b=eLMkn+zWIvZqA4Xtu+oNjqOgXnkMZzc2UBxituuGUmKVzbJ4QdUn+fO64Z4Elfvf3w KXTDeYaDY6QWunvANWpn+QupVqQuQumoZkKGJktVCAEChZneNqgTedaDLs0gIjoKZq0F S3XKf/wljvSRDz2Jr5BL8vRtOiWPz057oBcUg=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi!

we have two Intel Quad Nic 82576, PCI ID 8086:10E8 and use the igb
driver 1.3.19.3 on Debian 5.0.1.

I used the pciback.hide XEN kernel parameter and made on of the NIC's
interfaces available in a DomU.

Now, when I am starting the VM, the system crashes (log attached)

I also tried to boot with the irqpoll option - the Interrupt Disabled
message still appears when I try to start the VM.

Is that a serious driver problem or something that is easy to fix?

Best Regards,
  Alexander


Jun  9 10:39:56 dom0 kernel: [ 2362.408134] pciback 0000:10:00.1:
enabling device (0000 -> 0003)
Jun  9 10:39:56 dom0 kernel: [ 2362.408134] ACPI: PCI Interrupt
0000:10:00.1[B] -> GSI 17 (level, low) -> IRQ 17
Jun  9 10:39:56 dom0 kernel: [ 2362.408134] pciback 0000:10:00.1: Driver
tried to write to a read-only configuration space field at offset 0xa8,
size 2. This may be harmless, but if you have problems with your device:
Jun  9 10:39:56 dom0 kernel: [ 2362.408134] 1) see permissive attribute
in sysfs
Jun  9 10:39:56 dom0 kernel: [ 2362.408134] 2) report problems to the
xen-devel mailing list along with details of your device obtained from
lspci.
Jun  9 10:39:56 dom0 kernel: [ 2362.408134] PCI: Setting latency timer
of device 0000:10:00.1 to 64
Jun  9 10:39:56 dom0 kernel: [ 2362.408134] get owner for dev 1 get 7 
Jun  9 10:39:56 dom0 kernel: [ 2362.408134] map irq failed
Jun  9 10:39:56 dom0 kernel: [ 2362.412135] get owner for dev 1 get 7 
Jun  9 10:39:56 dom0 kernel: [ 2362.412135] map irq failed
Jun  9 10:39:56 dom0 kernel: [ 2362.412135] error enable msi for guest 7
status fffffff0
Jun  9 10:40:01 dom0 /USR/SBIN/CRON[8617]: (root) CMD (if
[ -x /usr/bin/vnstat ] && [ `ls /var/lib/vnstat/ | wc -l` -ge 1 ];
then /usr/bin/vnstat -u; fi)
Jun  9 10:40:04 dom0 kernel: [ 2370.648947] vif7.0: no IPv6 routers
present
Jun  9 10:41:42 dom0 kernel: [ 2468.316595] kjournald starting.  Commit
interval 5 seconds
Jun  9 10:41:42 dom0 kernel: [ 2468.316595] EXT3 FS on dm-14, internal
journal
Jun  9 10:41:42 dom0 kernel: [ 2468.316595] EXT3-fs: recovery complete.
Jun  9 10:41:42 dom0 kernel: [ 2468.316595] EXT3-fs: mounted filesystem
with ordered data mode.
Jun  9 10:45:01 dom0 /USR/SBIN/CRON[8639]: (root) CMD (if
[ -x /usr/bin/vnstat ] && [ `ls /var/lib/vnstat/ | wc -l` -ge 1 ];
then /usr/bin/vnstat -u; fi)
Jun  9 10:50:01 dom0 /USR/SBIN/CRON[8645]: (root) CMD (if
[ -x /usr/bin/vnstat ] && [ `ls /var/lib/vnstat/ | wc -l` -ge 1 ];
then /usr/bin/vnstat -u; fi)
Jun  9 10:55:01 dom0 /USR/SBIN/CRON[8651]: (root) CMD (if
[ -x /usr/bin/vnstat ] && [ `ls /var/lib/vnstat/ | wc -l` -ge 1 ];
then /usr/bin/vnstat -u; fi)
Jun  9 11:00:01 dom0 /USR/SBIN/CRON[8657]: (root) CMD (if
[ -x /usr/bin/vnstat ] && [ `ls /var/lib/vnstat/ | wc -l` -ge 1 ];
then /usr/bin/vnstat -u; fi)
Jun  9 11:05:01 dom0 /USR/SBIN/CRON[8663]: (root) CMD (if
[ -x /usr/bin/vnstat ] && [ `ls /var/lib/vnstat/ | wc -l` -ge 1 ];
then /usr/bin/vnstat -u; fi)
Jun  9 11:07:24 dom0 kernel: [ 4010.214397] irq 17: nobody cared (try
booting with the "irqpoll" option)
Jun  9 11:07:24 dom0 kernel: [ 4010.214438] Pid: 0, comm: swapper Not
tainted 2.6.26-2-xen-amd64 #1
Jun  9 11:07:24 dom0 kernel: [ 4010.214469] 
Jun  9 11:07:24 dom0 kernel: [ 4010.214470] Call Trace:
Jun  9 11:07:24 dom0 kernel: [ 4010.214515]  <IRQ>  [<ffffffff8037c718>]
irq_ignore_unhandled+0x1c/0x32
Jun  9 11:07:24 dom0 kernel: [ 4010.214564]  [<ffffffff8025f9f3>]
__report_bad_irq+0x30/0x72
Jun  9 11:07:24 dom0 kernel: [ 4010.214595]  [<ffffffff8025fcbc>]
note_interrupt+0x287/0x2c7
Jun  9 11:07:24 dom0 kernel: [ 4010.214628]  [<ffffffff802605a7>]
handle_level_irq+0xc3/0x116
Jun  9 11:07:24 dom0 kernel: [ 4010.214661]  [<ffffffff8020e13e>] do_IRQ
+0x4e/0x9a
Jun  9 11:07:24 dom0 kernel: [ 4010.214691]  [<ffffffff8037d42c>]
evtchn_do_upcall+0x13c/0x1fc
Jun  9 11:07:24 dom0 kernel: [ 4010.214724]  [<ffffffff8020bbde>]
do_hypervisor_callback+0x1e/0x30
Jun  9 11:07:24 dom0 kernel: [ 4010.214755]  <EOI>  [<ffffffff8020e795>]
xen_safe_halt+0x90/0xa6
Jun  9 11:07:24 dom0 kernel: [ 4010.214796]  [<ffffffff8020a0c8>]
xen_idle+0x2e/0x66
Jun  9 11:07:24 dom0 kernel: [ 4010.214825]  [<ffffffff80209cd6>]
cpu_idle+0x97/0xb9
Jun  9 11:07:24 dom0 kernel: [ 4010.214858] 
Jun  9 11:07:24 dom0 kernel: [ 4010.214880] handlers:
Jun  9 11:07:24 dom0 kernel: [ 4010.214903] [<ffffffff8039c058>]
(usb_hcd_irq+0x0/0xab)
Jun  9 11:07:24 dom0 kernel: [ 4010.214940] [<ffffffff8039c058>]
(usb_hcd_irq+0x0/0xab)
Jun  9 11:07:24 dom0 kernel: [ 4010.214977] [<ffffffffa0183eb0>]
(igb_intr+0x0/0x100 [igb])
Jun  9 11:07:24 dom0 kernel: [ 4010.215021] Disabling IRQ #17



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