All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Tom Rotenberg <tom.rotenberg@gmail.com>
Cc: xci-devel@lists.xensource.com, xen-devel@lists.xensource.com
Subject: Re: Lenovo T400 problem
Date: Tue, 16 Mar 2010 11:59:33 -0400	[thread overview]
Message-ID: <20100316155933.GC28821@phenom.dumpdata.com> (raw)
In-Reply-To: <8686c3cd1003160238w626b7802g2d053bc41b8a0ab0@mail.gmail.com>

> > What device is under BDF: 0:3.7 ?
> No such device in the system.

<laughs> 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.

> 
> 
> >
> >> (XEN) print_vtd_entries: iommu = ffff83013bdf5f90 bdf = 0:3:7 gmfn = 6cb6
> >> (XEN)     root_entry = ffff83013bdcc000
> >> (XEN)     root_entry[0] = 137e44001
> >> (XEN)     context = ffff830137e44000
> >> (XEN)     context[1f] = 0_0
> >> (XEN)     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?
> >
> >
> 
> 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.
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

      reply	other threads:[~2010-03-16 15:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-10 12:56 Lenovo T400 problem Tom Rotenberg
2010-03-15 15:39 ` Konrad Rzeszutek Wilk
2010-03-16  9:38   ` Tom Rotenberg
2010-03-16 15:59     ` Konrad Rzeszutek Wilk [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100316155933.GC28821@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=tom.rotenberg@gmail.com \
    --cc=xci-devel@lists.xensource.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.