[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <21806.17257.971957.13215@mariner.uk.xensource.com>
Date: Wed, 15 Apr 2015 11:54:33 +0100
From: Ian Jackson <Ian.Jackson@...citrix.com>
To: Michael Chan <mchan@...adcom.com>
CC: Prashant <prashant@...adcom.com>,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
Boris Ostrovsky <boris.ostrovsky@...cle.com>,
"David Vrabel" <david.vrabel@...rix.com>,
Thadeu Lima de Souza Cascardo <cascardo@...ux.vnet.ibm.com>,
Vlad Yasevich <vyasevich@...il.com>,
<xen-devel@...ts.xensource.com>, <netdev@...r.kernel.org>
Subject: Re: tg3 NIC driver bug in 3.14.x under Xen [and 3 more messages]
Prashant writes ("Re: tg3 NIC driver bug in 3.14.x under Xen [and 3 more messages]"):
> I tried to reproduce the problem on 32 bit 3.14.34 stable kernel
> baremetal, with iommu=soft swiotlb=force but no luck, no drops or
> errors. I did not try with Xen 64 bit yet. Btw I need a pcie analyzer
> trace to confirm the problem. Is it feasible to capture at your end ?
In private correspondence with Prashant we have established that
Prashant was using a different kernel configuration. Prashant
provided me with their kernel and module binaries, which work in my
environment.
I have also established that I can reproduce the problem with 3.14.37
(`iommu=soft swiotlb=force' baremetal => all rx wholly corrupted).
The kernel config I was using is here:
http://logs.test-lab.xenproject.org/osstest/logs/50387/build-i386-pvops/build/config
As far as I am aware no-one at Broadcom has attempted a build and test
using my kernel config.
Thanks,
Ian.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists