Re: Issue about domU missing interrupt

G.R.
Mon, 03 Dec 2012 13:06:40 -0000

On Mon, Dec 3, 2012 at 3:06 PM, Zhang, Xiantao
<xiantao.zhang@intel.com>wrote:

>  Maybe you need to  provide more information about your VGA device,  for
> example,  “lspci –vvv”.   In addition,  from your log, seems expansion rom
> bar is not correctly handled.  You may refer to this wiki page to check
> whether something is missed in your side.
> http://wiki.xen.org/wiki/Xen_VGA_Passthrough****
>
> Xiantao****
>
> **
>
I''m using the IGD coming with the H77M chipset, here are the lspci -vvv
output from dom0:
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd
Gen Core processor Graphics Controller (rev 09) (prog-if 00 [VGA
controller])
    Subsystem: ASRock Incorporation Device 0162
    Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
    Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort-
<MAbort- >SERR- <PERR- INTx-
    Latency: 0
    Interrupt: pin A routed to IRQ 95
    Region 0: Memory at f7800000 (64-bit, non-prefetchable) [size=4M]
    Region 2: Memory at e0000000 (64-bit, prefetchable) [size=256M]
    Region 4: I/O ports at f000 [size=64]
    Expansion ROM at <unassigned> [disabled]
    Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
        Address: fee00018  Data: 0000
    Capabilities: [d0] Power Management version 2
        Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
        Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
    Capabilities: [a4] PCI Advanced Features
        AFCap: TP+ FLR+
        AFCtrl: FLR-
        AFStatus: TP-
    Kernel driver in use: i915

And in domU respectively:

00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd
Gen Core processor Graphics Controller (rev 09) (prog-if 00 [VGA
controller])
    Subsystem: ASRock Incorporation Device 0162
    Physical Slot: 2
    Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
    Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort-
<MAbort- >SERR- <PERR- INTx+
    Latency: 64
    Interrupt: pin A routed to IRQ 78
    Region 0: Memory at f1000000 (64-bit, non-prefetchable) [size=4M]
    Region 2: Memory at e0000000 (64-bit, prefetchable) [size=256M]
    Region 4: I/O ports at c100 [size=64]
    Expansion ROM at <unassigned> [disabled]
    Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
        Address: fee33000  Data: 4300
    Capabilities: [d0] Power Management version 2
        Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
        Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
    Kernel driver in use: i915

They are pretty much the same from my point of view except for some
interrupt config.
The ''expansion ROM'' are disabled in both case.
But what does this mean after all? Could you give a brief intro for my
education?

I did not find anything obvious missing from the wiki page.
I would like to note that I''m using an AsRock H77m-itx board.
Even when the chipset is not formally classified as vt-d capable (yes, I
noticed your email domain),
Intel is still shipping H77 based vt-d capable board (
http://www.intel.com/support/motherboards/desktop/sb/CS-030922.htm).
I guess this should not count as a missing piece, right?

Thanks,
Timothy

>  **
>
> *From:* xen-devel-bounces@lists.xen.org [mailto:
> xen-devel-bounces@lists.xen.org] *On Behalf Of *G.R.
> *Sent:* Monday, December 03, 2012 11:48 AM
> *To:* xen-devel
> *Subject:* [Xen-devel] Issue about domU missing interrupt****
>
> ** **
>
> Hi developers,
> I met some domU issues and the log suggests missing interrupt.
> Details from here:
> http://www.gossamer-threads.com/lists/xen/users/263938#263938
> In summary, this is the suspicious log:
>
> (XEN) vmsi.c:122:d32767 Unsupported delivery mode 3
>
> I''ve checked the code in question and found that mode 3 is an
''reserved_1''
> mode.
> I want to trace down the source of this mode setting to root-cause the
> issue.
> But I''m not an xen developer, and am even a newbie as a xen user.
> Could anybody give me instructions about how to enable detailed debug log?
> It could be better if I can get advice about experiments to perform /
> switches to try out etc.
>
> My SW config:
> dom0: Debian wheezy (3.6 experimental kernel, xen 4.1.3-4)
> domU: Debian wheezy 3.2.x stock kernel.
>
> Thanks,
> Timothy****
>


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org