From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Lenovo T400 problem Date: Tue, 16 Mar 2010 11:59:33 -0400 Message-ID: <20100316155933.GC28821@phenom.dumpdata.com> References: <8686c3cd1003100456g72c20b0ar9d67077d42a5e2ca@mail.gmail.com> <20100315153953.GB30388@phenom.dumpdata.com> <8686c3cd1003160238w626b7802g2d053bc41b8a0ab0@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: <8686c3cd1003160238w626b7802g2d053bc41b8a0ab0@mail.gmail.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Tom Rotenberg Cc: xci-devel@lists.xensource.com, xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org > > What device is under BDF: 0:3.7 ? > No such device in the system. So you have a device that shows up mysteriously _after_ the bootup. That is pretty mysterious. .. snip Hmm, I think there is a mechanism to "re-trigger" the PCI bus scan. Try this: echo 1 > /sys/class/pci_bus/0000:03/device/rescan > > So from reading that it seems that the device in question: 0:3:7 hasn= 't > > been actually authorized for to be used by your guest? > > > Yeap. There is no such device in the system. Full lspci is below: .. > 00:03.0 Communication controller: Intel Corporation Mobile 4 Series > Chipset MEI Controller (rev 07) > 00:03.3 Serial controller: Intel Corporation Mobile 4 Series Chipset > AMT SOL Redirection (rev 07) Hmm, AMT is this fancy chipset that allows the System Admin to turn your machine on/off, BIOS update, etc. I wonder if there is something further on that. Can you turn it off and see what happens? Also, I would suggest Google for 'Intel Mobile 4 Series MEI controller" and look at the spec and see if they mention anything about device at function 7. >=20 >=20 > > > >> (XEN) print_vtd_entries: iommu =3D ffff83013bdf5f90 bdf =3D 0:3:7 gm= fn =3D 6cb6 > >> (XEN) =A0 =A0 root_entry =3D ffff83013bdcc000 > >> (XEN) =A0 =A0 root_entry[0] =3D 137e44001 > >> (XEN) =A0 =A0 context =3D ffff830137e44000 > >> (XEN) =A0 =A0 context[1f] =3D 0_0 > >> (XEN) =A0 =A0 ctxt_entry[1f] not present > > > > Sure enought. Not present it there.. Are there any other entries > > (earlier on) that talk about BDF 0:3:7? > > > > >=20 > It looks that this failure is the result of trying to pass-through > WLAN(3:0.0). Interesting enough,- with this failure(coming 3:0.0 is much different from 0:3.X. It is on a different bus. > periodically once in few minutes) the system boots and runs ok(I can't > tell anything about its stability though). The problem becomes fatal > only when I'm trying to pass-through usb and wlan together. So if you pass in WLAN by itself it works fine. But if you pass in USB + WLAN hell breaks loose? I would look up specs about the WLAN then. > Do you have any ideas were to start looking? .. specs, and turn off AMT. >=20 > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel