Lenovo T400 problem

Lenovo T400 problem

[Tom Rotenberg]

Hi all,
Environment:
I'm trying to run T400 with USB and WLAN assigned to my HVM (Windows
XP). I'm using XEN 3.4 19696 changeset.

Facts:
Running both of them together stuck my machine in Windows splash
screen with following output:

(XEN) [VT-D]iommu.c:694: iommu_fault:DMA Read: 0:3.7 addr 6cb6000
REASON 2 iommu->reg = ffff828bfff57000
(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
(XEN) domctl.c:910:d0 ioport_map:remove f_gport=13c0 f_mport=1c00 np=20
(XEN) domctl.c:886:d0 ioport_map:add f_gport=13c0 f_mport=1c00 np=20
(XEN) domctl.c:910:d0 ioport_map:remove f_gport=1320 f_mport=1860 np=20
(XEN) domctl.c:886:d0 ioport_map:add f_gport=1320 f_mport=1860 np=20
(XEN) domctl.c:910:d0 ioport_map:remove f_gport=13a0 f_mport=18e0 np=20
(XEN) domctl.c:886:d0 ioport_map:add f_gport=13a0 f_mport=18e0 np=20
(XEN) domctl.c:910:d0 ioport_map:remove f_gport=1340 f_mport=1880 np=20
(XEN) domctl.c:886:d0 ioport_map:add f_gport=1340 f_mport=1880 np=20
(XEN) domctl.c:910:d0 ioport_map:remove f_gport=1380 f_mport=18c0 np=20
(XEN) domctl.c:886:d0 ioport_map:add f_gport=1380 f_mport=18c0 np=20
(XEN) domctl.c:910:d0 ioport_map:remove f_gport=1360 f_mport=18a0 np=20
(XEN) domctl.c:886:d0 ioport_map:add f_gport=1360 f_mport=18a0 np=20
(XEN) domctl.c:845:d0 memory_map:remove: gfn=c0004 mfn=fc220 nr_mfns=4
(XEN) domctl.c:835:d0 memory_map:add: gfn=c0004 mfn=fc220 nr_mfns=4
(XEN) domctl.c:845:d0 memory_map:remove: gfn=c0002 mfn=fc227 nr_mfns=1
(XEN) domctl.c:835:d0 memory_map:add: gfn=c0002 mfn=fc227 nr_mfns=1

[  111.912950] ACPI: EC: missing write data confirmation, don't expect
it any longer.
[  117.420570] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
[  117.420675] ata1.00: cmd ca/00:08:57:8e:7d/00:00:00:00:00/e0 tag 0
dma 4096 out
[  117.420676]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask
0x4 (timeout)
[  117.420909] ata1.00: status: { DRDY }
[  117.421007] ata1: soft resetting link
[  117.424560] ata2.00: qc timeout (cmd 0xa0)
[  117.424659] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
[  117.424757] ata2.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
[  117.424757]          cdb 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
[  117.424758]          res 51/24:03:00:00:00/00:00:00:00:00/a0 Emask
0x5 (timeout)
[  117.425063] ata2.00: status: { DRDY ERR }
[  117.425159] ata2: soft resetting link
[  117.756622] e1000e: peth0 NIC Link is Down
[  117.771953] eth0: port 1(peth0) entering disabled state
[  117.916846] ata2.00: configured for UDMA/100
[  117.916955] ata2: EH complete
[  120.721163] e1000e: peth0 NIC Link is Up 1000 Mbps Full Duplex,
Flow Control: None
[  120.724795] eth0: port 1(peth0) entering learning state
[  120.728294] eth0: topology change detected, propagating
[  120.728386] eth0: port 1(peth0) entering forwarding state

ACPI or SATA errors can vary(sometimes I get only one of them before
the machine dies on me...).

USB and WLAN are sharing the same IRQ line(17) and I'm running with
XEN MSI disabled. Another device on the same line is Audio. But this
sharing doesn't cause me problems.

Have someone encountered this or similar issues?
 Tom.

Re: Lenovo T400 problem

[Konrad Rzeszutek Wilk]

On Wed, Mar 10, 2010 at 02:56:48PM +0200, Tom Rotenberg wrote:
> Hi all,
> Environment:
> I'm trying to run T400 with USB and WLAN assigned to my HVM (Windows
> XP). I'm using XEN 3.4 19696 changeset.


> 
> Facts:
> Running both of them together stuck my machine in Windows splash
> screen with following output:
> 
> (XEN) [VT-D]iommu.c:694: iommu_fault:DMA Read: 0:3.7 addr 6cb6000


What device is under BDF: 0:3.7 ?
> REASON 2 iommu->reg = ffff828bfff57000


Hmm.. you really need the secret key decoder to figure that one out.
I think it is 'Present bit in context entry is clear"'

Looking at "http://download.intel.com/technology/computing/vptech/Intel(r)_VT_for_Direct_IO.pdf "
it says:

"Present Flag: The present field is used by software to indicate to
hardware whether the contextentry
is present and initialized. Software may Clear the present field for
context entries
corresponding to device functions that are not present in the platform.
If the present field of a
context-entry used to process a DMA request is Clear, the DMA request is
blocked, resulting in a
translation fault."


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?



> (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?

Re: Lenovo T400 problem

[Tom Rotenberg]

On Mon, Mar 15, 2010 at 5:39 PM, Konrad Rzeszutek Wilk
<konrad.wilk@oracle.com> wrote:
> On Wed, Mar 10, 2010 at 02:56:48PM +0200, Tom Rotenberg wrote:
>
>
> What device is under BDF: 0:3.7 ?
No such device in the system.

>
>
> Hmm.. you really need the secret key decoder to figure that one out.
> I think it is 'Present bit in context entry is clear"'
>
> Looking at "http://download.intel.com/technology/computing/vptech/Intel(r)_VT_for_Direct_IO.pdf "
> it says:
>
> "Present Flag: The present field is used by software to indicate to
> hardware whether the contextentry
> is present and initialized. Software may Clear the present field for
> context entries
> corresponding to device functions that are not present in the platform.
> If the present field of a
> context-entry used to process a DMA request is Clear, the DMA request is
> blocked, resulting in a
> translation fault."
>
>
> 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:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory
Controller Hub (rev 07)
00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI
Express Graphics Port (rev 07)
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)
00:19.0 Ethernet controller: Intel Corporation 82567LM Gigabit Network
Connection (rev 03)
00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB
UHCI Controller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB
UHCI Controller #5 (rev 03)
00:1a.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB
UHCI Controller #6 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2
EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio
Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express
Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express
Port 2 (rev 03)
00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express
Port 4 (rev 03)
00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express
Port 5 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB
UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB
UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB
UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2
EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
00:1f.0 ISA bridge: Intel Corporation ICH9M-E LPC Interface Controller (rev 03)
00:1f.2 IDE interface: Intel Corporation ICH9M/M-E 2 port SATA IDE
Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03)
01:00.0 VGA compatible controller: ATI Technologies Inc Mobility
Radeon HD 3400 Series
03:00.0 Network controller: Intel Corporation Wireless WiFi Link 5100
15:00.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ba)
15:00.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04)
15:00.2 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro
Host Adapter (rev 21)
15:00.3 System peripheral: Ricoh Co Ltd R5C843 MMC Host Controller (rev 11)
15:00.4 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host
Adapter (rev 11)
15:00.5 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 11)


>
>> (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
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.
Do you have any ideas were to start looking?

Re: Lenovo T400 problem

[Konrad Rzeszutek Wilk]

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