Bug#701744: Xen netback regression

2013-08-26 Thread Ward Vandewege
Hi all,

Are there any updates on the final resolution of this bug? It's been a
while, and it's still marked as pending...

Thanks,
Ward.

-- 
Ward Vandewege | CTO, Free Software Foundation
GPG Key: 25F774AB  | http://status.fsf.org/ward
http://fsf.org/blogs/RSS   | http://identi.ca/cure

Do you use free software? Donate to join the FSF and support freedom at
 http://www.fsf.org/register_form?referrer=859


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130827004827.ga30...@countzero.vandewege.net



Bug#611278: linux-image-2.6.32-5-xen-amd64: boot fails when iommu is enabled in bios

2011-01-27 Thread Ward Vandewege
Package: linux-2.6
Version: 2.6.32-30
Severity: important


When enabling the BIOS IOMMU option, the system does not boot.  The kernel
resets itself endlessly.

I've recorded a video of a boot attempt (it is 28MB):

  http://ward.vandewege.net/h8dgt-hibqf/iommu-reset.mov

The hardware is Supermicro H8DGT-HIBQF

  
http://www.supermicro.com/Aplus/motherboard/Opteron6100/SR56x0/H8DGT-HIBQF.cfm 

It is currently running BIOS revision 1.0c (date 10/29/10).

Thanks,
Ward.


-- Package-specific info:
** Version:
Linux version 2.6.32-5-xen-amd64 (Debian 2.6.32-30) (b...@decadent.org.uk) (gcc 
version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Wed Jan 12 05:46:49 UTC 2011

** Command line:
placeholder root=UUID=1ab080f3-e10c-45aa-91c9-a339c384e3b6 ro

** Tainted: W (512)
 * Taint on warning.

** Kernel log:
[  261.667004] xen_allocate_pirq: returning irq 19 for gsi 19
[  261.667124] xen: -- irq=19
[  261.667134] Already setup the GSI :19
[  261.667250] pciback :02:00.0: PCI INT A - GSI 19 (level, low) - IRQ 19
[  261.667384] pciback :02:00.0: PCI INT A disabled
[  390.372087] device vif2.0 entered promiscuous mode
[  390.386288] eth0: port 2(vif2.0) entering forwarding state
[  390.469449] ip_tables: (C) 2000-2006 Netfilter Core Team
[  390.603573] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[  390.604535] CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please 
use
[  390.604639] nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module 
option or
[  390.604639] sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
[  390.635127] physdev match: using --physdev-out in the OUTPUT, FORWARD and 
POSTROUTING chains for non-bridged traffic is not supported anymore.
[  390.658486] physdev match: using --physdev-out in the OUTPUT, FORWARD and 
POSTROUTING chains for non-bridged traffic is not supported anymore.
[  390.668642] physdev match: using --physdev-out in the OUTPUT, FORWARD and 
POSTROUTING chains for non-bridged traffic is not supported anymore.
[  390.668851] physdev match: using --physdev-out in the OUTPUT, FORWARD and 
POSTROUTING chains for non-bridged traffic is not supported anymore.
[  390.776312] pciback: vpci: :02:00.0: assign to virtual slot 0
[  400.848073] vif2.0: no IPv6 routers present
[  404.753819] eth0: port 2(vif2.0) entering disabled state
[  404.776420] eth0: port 2(vif2.0) entering disabled state
[  405.001553] physdev match: using --physdev-out in the OUTPUT, FORWARD and 
POSTROUTING chains for non-bridged traffic is not supported anymore.
[  405.001780] physdev match: using --physdev-out in the OUTPUT, FORWARD and 
POSTROUTING chains for non-bridged traffic is not supported anymore.
[  405.011702] physdev match: using --physdev-out in the OUTPUT, FORWARD and 
POSTROUTING chains for non-bridged traffic is not supported anymore.
[  405.023602] physdev match: using --physdev-out in the OUTPUT, FORWARD and 
POSTROUTING chains for non-bridged traffic is not supported anymore.
[  436.434249] device vif3.0 entered promiscuous mode
[  436.448297] eth0: port 2(vif3.0) entering forwarding state
[  436.504563] physdev match: using --physdev-out in the OUTPUT, FORWARD and 
POSTROUTING chains for non-bridged traffic is not supported anymore.
[  436.516203] physdev match: using --physdev-out in the OUTPUT, FORWARD and 
POSTROUTING chains for non-bridged traffic is not supported anymore.
[  436.525930] physdev match: using --physdev-out in the OUTPUT, FORWARD and 
POSTROUTING chains for non-bridged traffic is not supported anymore.
[  436.526134] physdev match: using --physdev-out in the OUTPUT, FORWARD and 
POSTROUTING chains for non-bridged traffic is not supported anymore.
[  436.781413] pciback: vpci: :02:00.0: assign to virtual slot 0
[  436.783759] pciback :02:00.0: device has been assigned to another 
domain! Over-writting the ownership, but beware.
[  437.964718] pciback :02:00.0: enabling device ( - 0002)
[  437.964899] xen: registering gsi 19 triggering 0 polarity 1
[  437.964908] xen_allocate_pirq: returning irq 19 for gsi 19
[  437.965044] xen: -- irq=19
[  437.965056] Already setup the GSI :19
[  437.965184] pciback :02:00.0: PCI INT A - GSI 19 (level, low) - IRQ 19
[  437.965343] pciback :02:00.0: setting latency timer to 64
[  437.974877] blkback: ring-ref 768, event-channel 9, protocol 1 (x86_64-abi)
[  438.007384] blkback: ring-ref 769, event-channel 10, protocol 1 (x86_64-abi)
[  438.971703] pciback :02:00.0: Driver tried to write to a read-only 
configuration space field at offset 0x68, size 2. This may be harmless, but if 
you have problems with your device:
[  438.971709] 1) see permissive attribute in sysfs
[  438.971713] 2) report problems to the xen-devel mailing list along with 
details of your device obtained from lspci.
[  438.973267] xen: registering gsi 19 triggering 0 polarity 1
[  438.973275] xen_allocate_pirq: returning irq 19 for gsi 19
[  438.973408] xen: -- irq=19
[  438.973417] Already setup the GSI :19
[  

Bug#611234: linux-image-2.6.32-5-xen-amd64: enable CONFIG_XEN_PCI_PASSTHROUGH

2011-01-26 Thread Ward Vandewege
Package: linux-2.6
Version: 2.6.32-30
Severity: wishlist


CONFIG_XEN_PCI_PASSTHROUGH is not enabled by default in this kernel. It would
be nice to change that.

Thanks,
Ward. 

-- Package-specific info:
** Version:
Linux version 2.6.32-5-xen-amd64 (Debian 2.6.32-30) (b...@decadent.org.uk) (gcc 
version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Wed Jan 12 05:46:49 UTC 2011

** Command line:
placeholder root=UUID=1ab080f3-e10c-45aa-91c9-a339c384e3b6 ro

** Tainted: W (512)
 * Taint on warning.

** Kernel log:
[3.794986] md: bindsda3
[3.797518] raid1: raid set md1 active with 2 out of 2 mirrors
[3.797662] md1: detected capacity change from 0 to 20479934464
[3.800146]  md1: unknown partition table
[3.856035] md: md2 stopped.
[3.858805] md: bindsdb4
[3.859160] md: bindsda4
[3.863825] raid1: raid set md2 active with 2 out of 2 mirrors
[3.863967] md2: detected capacity change from 0 to 2047934464
[3.866534]  md2: unknown partition table
[3.877599] device-mapper: uevent: version 1.0.3
[3.878230] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: 
dm-de...@redhat.com
[3.943448] PM: Starting manual resume from disk
[3.943583] PM: Resume from partition 9:2
[3.943585] PM: Checking hibernation image.
[3.944852] PM: Error -22 checking image file
[3.944855] PM: Resume from disk failed.
[3.982004] kjournald starting.  Commit interval 5 seconds
[3.982017] EXT3-fs: mounted filesystem with ordered data mode.
[4.831936] udev[631]: starting version 164
[4.955670] input: Power Button as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3
[4.955855] ACPI: Power Button [PWRB]
[4.956082] input: Power Button as 
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
[4.956238] ACPI: Power Button [PWRF]
[5.161516] EDAC MC: Ver: 2.1.0 Jan 12 2011
[5.166756] EDAC amd64_edac:  Ver: 3.2.0 Jan 12 2011
[5.167301] EDAC amd64: ECC is enabled by BIOS.
[5.167887] EDAC amd64: ECC is enabled by BIOS.
[5.168156] EDAC amd64: ECC is enabled by BIOS.
[5.168415] EDAC amd64: ECC is enabled by BIOS.
[5.168739] EDAC MC: F10h CPU detected
[5.168799] input: PC Speaker as /devices/platform/pcspkr/input/input5
[5.168847] EDAC amd64: f10_probe_valid_hardware() This machine is running 
with DDR3 memory. This is not currently supported. DCHR0=0x3f48090d 
DCHR1=0x3f48090d
[5.168856] EDAC amd64:Contact 'amd64_edac' module MAINTAINER to help 
add support.
[5.177119] piix4_smbus :00:14.0: SMBus Host Controller at 0xb00, 
revision 0
[5.462701] Error: Driver 'pcspkr' is already registered, aborting...
[5.815025] md: md3 stopped.
[5.816108] md: bindsdb5
[5.816383] md: bindsda5
[5.824049] raid1: raid set md3 active with 2 out of 2 mirrors
[5.824266] md3: detected capacity change from 0 to 181553878016
[5.831727]  md3: unknown partition table
[6.464490] Adding 128k swap on /dev/md2.  Priority:-1 extents:1 
across:128k 
[6.665853] EXT3 FS on md1, internal journal
[6.810947] loop: module loaded
[6.985043] mlx4_ib: Mellanox ConnectX InfiniBand driver v1.0-ofed1.5.2 
(August 4, 2010)
[8.335417] ib_srp: ASYNC event= 11 on device= mlx4_0
[8.383296] ib_srp: ASYNC event= 17 on device= mlx4_0
[8.390935] ib_srp: ASYNC event= 9 on device= mlx4_0
[8.537955] igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
[8.539734] ADDRCONF(NETDEV_UP): eth0: link is not ready
[8.546073] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[9.468062] Event-channel device installed.
[9.646168]   alloc irq_desc for 4230 on node -1
[9.646173]   alloc kstat_irqs on node -1
[9.646264]   alloc irq_desc for 4229 on node -1
[9.646268]   alloc kstat_irqs on node -1
[9.646808] XENBUS: Unable to read cpu state
[9.647231] XENBUS: Unable to read cpu state
[9.647566] XENBUS: Unable to read cpu state
[9.647902] XENBUS: Unable to read cpu state
[9.648354] XENBUS: Unable to read cpu state
[9.648761] XENBUS: Unable to read cpu state
[9.649151] XENBUS: Unable to read cpu state
[9.649442] XENBUS: Unable to read cpu state
[9.649718] XENBUS: Unable to read cpu state
[9.650034] XENBUS: Unable to read cpu state
[9.650315] XENBUS: Unable to read cpu state
[9.650588] XENBUS: Unable to read cpu state
[9.650875] XENBUS: Unable to read cpu state
[9.651152] XENBUS: Unable to read cpu state
[9.651585] XENBUS: Unable to read cpu state
[9.652000] XENBUS: Unable to read cpu state
[   11.207121] Bridge firewalling registered
[   11.653335] ADDRCONF(NETDEV_UP): peth0: link is not ready
[   14.552581] igb: peth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
[   14.558686] ADDRCONF(NETDEV_CHANGE): peth0: link becomes ready
[   14.720974] device peth0 entered promiscuous mode
[   14.764960] eth0: port 1(peth0) entering forwarding state
[   15.326131] ADDRCONF(NETDEV_UP): peth1: link is not ready
[   24.600059] 

Bug#611234: linux-image-2.6.32-5-xen-amd64: enable CONFIG_XEN_PCI_PASSTHROUGH

2011-01-26 Thread Ward Vandewege
On Wed, Jan 26, 2011 at 10:03:38PM -0500, Ward Vandewege wrote:
 Package: linux-2.6
 Version: 2.6.32-30
 Severity: wishlist
 
 
 CONFIG_XEN_PCI_PASSTHROUGH is not enabled by default in this kernel. It would
 be nice to change that.

Or, I guess, not - I see now that this option is no longer used. Sorry for
the noise.

Thanks,
Ward.




-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110127031505.ga4...@countzero.vandewege.net