All of lore.kernel.org
 help / color / mirror / Atom feed
* Intel IGP VGA-passthrough to Ubuntu 11.04/openSUSE domU doesn't quite work
@ 2011-08-29 15:50 Martin Meier
  2011-08-29 19:36 ` Konrad Rzeszutek Wilk
  0 siblings, 1 reply; 3+ messages in thread
From: Martin Meier @ 2011-08-29 15:50 UTC (permalink / raw)
  To: intel-gfx, xen-devel

Hi,
when comparing the dmesgs from a Ubuntu 11.04+xorg-edgers-ppa running on real
hardware ver. running in a HVM-domU, I see this change in dmesg:

real:
[    2.306326] [drm:intel_wait_for_vblank], vblank wait timed out
[    2.307140] [drm:gen6_fdi_link_train], FDI_RX_IIR 0x700
[    2.307143] [drm:gen6_fdi_link_train], FDI train 1 done.
[    2.307798] [drm:gen6_fdi_link_train], FDI_RX_IIR 0x600
[    2.307801] [drm:gen6_fdi_link_train], FDI train 2 done.
[    2.307802] [drm:gen6_fdi_link_train], FDI train done.

domU:
[    3.658150] [drm:intel_wait_for_vblank], vblank wait timed out
[    3.658962] [drm:gen6_fdi_link_train], FDI_RX_IIR 0x700
[    3.658966] [drm:gen6_fdi_link_train], FDI train 1 done.
[    3.659625] [drm:gen6_fdi_link_train], FDI_RX_IIR 0x0
[    3.660129] [drm:gen6_fdi_link_train], FDI_RX_IIR 0x0
[    3.660633] [drm:gen6_fdi_link_train], FDI_RX_IIR 0x0
[    3.661137] [drm:gen6_fdi_link_train], FDI_RX_IIR 0x0
[    3.661140] [drm:gen6_fdi_link_train] *ERROR* FDI train 2 fail!
[    3.661142] [drm:gen6_fdi_link_train], FDI train done.

The desktop looks OK on real hardware.
In a domU the display shows 'no signal' and turns it self off during
the boot process.
The domU stays up and does not crash, oops, seg-faults, etc.

I've tried
chvt 1 / 7
xset dpms force off / on
xrandr  --off / --auto
with no visible change.

Hardware:
DQ67SW (vt-d enabled)
i5 2400
Display connected via DVI-D / DVI-I+VGA adapter

Software:
domU kernel: 3.1.0-rc3 x86 32 bit
dom0 kernel: 3.0.3
(git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git) x86_64
xen 4.2-unstable (xen_changeset          : Thu Aug 25 12:03:14 2011
+0100 23791:227130622561)


A short test with openSUSE-NET-Build0136-x86_64.iso shows the same behaviour.

On the other hand, XP-SP3 with the GFX_XP32_6.14.10.5361_PV.exe works
quite well with the same configuration.

Thanks,
Martin

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Intel IGP VGA-passthrough to Ubuntu 11.04/openSUSE domU doesn't quite work
  2011-08-29 15:50 Intel IGP VGA-passthrough to Ubuntu 11.04/openSUSE domU doesn't quite work Martin Meier
@ 2011-08-29 19:36 ` Konrad Rzeszutek Wilk
  2011-09-05 16:16   ` [Xen-devel] " Martin Meier
  0 siblings, 1 reply; 3+ messages in thread
From: Konrad Rzeszutek Wilk @ 2011-08-29 19:36 UTC (permalink / raw)
  To: Martin Meier; +Cc: intel-gfx, xen-devel

On Mon, Aug 29, 2011 at 05:50:23PM +0200, Martin Meier wrote:
> Hi,
> when comparing the dmesgs from a Ubuntu 11.04+xorg-edgers-ppa running on real
> hardware ver. running in a HVM-domU, I see this change in dmesg:
> 
> real:
> [    2.306326] [drm:intel_wait_for_vblank], vblank wait timed out
> [    2.307140] [drm:gen6_fdi_link_train], FDI_RX_IIR 0x700
> [    2.307143] [drm:gen6_fdi_link_train], FDI train 1 done.
> [    2.307798] [drm:gen6_fdi_link_train], FDI_RX_IIR 0x600
> [    2.307801] [drm:gen6_fdi_link_train], FDI train 2 done.
> [    2.307802] [drm:gen6_fdi_link_train], FDI train done.
> 
> domU:
> [    3.658150] [drm:intel_wait_for_vblank], vblank wait timed out
> [    3.658962] [drm:gen6_fdi_link_train], FDI_RX_IIR 0x700
> [    3.658966] [drm:gen6_fdi_link_train], FDI train 1 done.
> [    3.659625] [drm:gen6_fdi_link_train], FDI_RX_IIR 0x0
> [    3.660129] [drm:gen6_fdi_link_train], FDI_RX_IIR 0x0
> [    3.660633] [drm:gen6_fdi_link_train], FDI_RX_IIR 0x0
> [    3.661137] [drm:gen6_fdi_link_train], FDI_RX_IIR 0x0
> [    3.661140] [drm:gen6_fdi_link_train] *ERROR* FDI train 2 fail!
> [    3.661142] [drm:gen6_fdi_link_train], FDI train done.
> 
> The desktop looks OK on real hardware.
> In a domU the display shows 'no signal' and turns it self off during
> the boot process.
> The domU stays up and does not crash, oops, seg-faults, etc.
> 
> I've tried
> chvt 1 / 7
> xset dpms force off / on
> xrandr  --off / --auto
> with no visible change.
> 
> Hardware:
> DQ67SW (vt-d enabled)
> i5 2400
> Display connected via DVI-D / DVI-I+VGA adapter
> 
> Software:
> domU kernel: 3.1.0-rc3 x86 32 bit
> dom0 kernel: 3.0.3
> (git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git) x86_64

An you have CONFIG_DMAR enabled?

> xen 4.2-unstable (xen_changeset          : Thu Aug 25 12:03:14 2011
> +0100 23791:227130622561)
> 
> 
> A short test with openSUSE-NET-Build0136-x86_64.iso shows the same behaviour.
> 
> On the other hand, XP-SP3 with the GFX_XP32_6.14.10.5361_PV.exe works
> quite well with the same configuration.

That is pretty neat.
> 
> Thanks,
> Martin
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [Xen-devel] Intel IGP VGA-passthrough to Ubuntu 11.04/openSUSE domU doesn't quite work
  2011-08-29 19:36 ` Konrad Rzeszutek Wilk
@ 2011-09-05 16:16   ` Martin Meier
  0 siblings, 0 replies; 3+ messages in thread
From: Martin Meier @ 2011-09-05 16:16 UTC (permalink / raw)
  To: Konrad Rzeszutek Wilk; +Cc: intel-gfx, xen-devel

On Mon, Aug 29, 2011 at 9:36 PM, Konrad Rzeszutek Wilk
<konrad.wilk@oracle.com> wrote:
> On Mon, Aug 29, 2011 at 05:50:23PM +0200, Martin Meier wrote:
>> Hi,
>> when comparing the dmesgs from a Ubuntu 11.04+xorg-edgers-ppa running on real
>> hardware ver. running in a HVM-domU, I see this change in dmesg:
>>
>> real:
>> [    2.306326] [drm:intel_wait_for_vblank], vblank wait timed out
>> [    2.307140] [drm:gen6_fdi_link_train], FDI_RX_IIR 0x700
>> [    2.307143] [drm:gen6_fdi_link_train], FDI train 1 done.
>> [    2.307798] [drm:gen6_fdi_link_train], FDI_RX_IIR 0x600
>> [    2.307801] [drm:gen6_fdi_link_train], FDI train 2 done.
>> [    2.307802] [drm:gen6_fdi_link_train], FDI train done.
>>
>> domU:
[..]
>> [    3.661137] [drm:gen6_fdi_link_train], FDI_RX_IIR 0x0
>> [    3.661140] [drm:gen6_fdi_link_train] *ERROR* FDI train 2 fail!
>> [    3.661142] [drm:gen6_fdi_link_train], FDI train done.

Hm, this might be a symptom of an earlier error in the boot process I
hadn't noticed last week:

real:
i915 0000:00:02.0: setting latency timer to 64
[drm:intel_opregion_setup], graphic opregion physical addr: 0xbc8d6018
[drm:intel_opregion_setup], Public ACPI methods supported
[drm:intel_opregion_setup], SWSCI supported
[drm:intel_opregion_setup], ASLE supported
[drm:intel_detect_pch], Found CougarPoint PCH
[drm:intel_parse_bios], Using VBT from OpRegion: $VBT SNB/IVB-DESKTOPd

domU.
i915 0000:00:02.0: setting latency timer to 64
[drm:intel_opregion_setup], graphic opregion physical addr: 0xbc8d6018
drm:intel_opregion_setup], opregion signature mismatch
i915 0000:00:02.0: irq 64 for MSI/MSI-X
[drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[drm] Driver supports precise vblank timestamp query.
[drm:parse_general_definitions], crt_ddc_bus_pin: 5

By searching for "opregion signature mismatch" I found in intel_opregion.c:

#define OPREGION_SIGNATURE "IntelGraphicsMem"
[..]
        pci_read_config_dword(dev->pdev, PCI_ASLS, &asls);
        DRM_DEBUG_DRIVER("graphic opregion physical addr: 0x%x\n", asls);
        if (asls == 0) {
                DRM_DEBUG_DRIVER("ACPI OpRegion not supported!\n");
                return -ENOTSUPP;
        }

        base = acpi_os_ioremap(asls, OPREGION_SIZE);
        if (!base)
                return -ENOMEM;

        if (memcmp(base, OPREGION_SIGNATURE, 16)) {
                DRM_DEBUG_DRIVER("opregion signature mismatch\n");
                err = -EINVAL;
                goto err_out;
        }


On the xen side(/var/log/xen/qemu-dm-domU.log) I see:

register_vga_regions: register_vga: igd_opregion = bc8d6018
dm-command: hot insert pass-through pci dev
register_real_device: Assigning real physical device 00:02.0 ...
pt_iomul_init: Error: pt_iomul_init can't open file
/dev/xen/pci_iomul: No such file or directory: 0x0:0x2.0x0
pt_register_regions: IO region registered (size=0x00400000 base_addr=0xfe000004)
pt_register_regions: IO region registered (size=0x10000000 base_addr=0xd000000c)
pt_register_regions: IO region registered (size=0x00000040 base_addr=0x0000f001)
register_vga_regions: register_vga: igd_opregion = bc8d6018
pt_msi_setup: msi mapped with pirq 37
pci_intx: intx=1
register_real_device: Real physical device 00:02.0 registered successfuly!
IRQ type = MSI-INTx
igd_pci_read: pci_config_read: 0:0.0: addr=0 len=2 val=ffff8086
igd_pci_read: pci_config_read: 0:0.0: addr=2 len=2 val=ffff0100
pt_iomem_map: e_phys=e0000000 maddr=d0000000 type=8 len=268435456
index=2 first_map=1
pt_iomem_map: e_phys=f1000000 maddr=fe000000 type=0 len=4194304
index=0 first_map=1
pt_ioport_map: e_phys=c100 pio_base=f000 len=64 index=4 first_map=1
igd_pci_read: pci_config_read: 0:0.0: addr=0 len=2 val=ffff8086
igd_pci_read: pci_config_read: 0:0.0: addr=2 len=2 val=ffff0100

Is "can't open file /dev/xen/pci_iomul" a real problem?


I'm not sure where to go from here...

>> Hardware:
>> DQ67SW (vt-d enabled)
>> i5 2400
>> Display connected via DVI-D / DVI-I+VGA adapter
>>
>> Software:
>> domU kernel: 3.1.0-rc3 x86 32 bit
>> dom0 kernel: 3.0.3
>> (git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git) x86_64
>
> An you have CONFIG_DMAR enabled?

Yes, CONFIG_DMAR is set to 'y' for the dom0.

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2011-09-05 16:16 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-08-29 15:50 Intel IGP VGA-passthrough to Ubuntu 11.04/openSUSE domU doesn't quite work Martin Meier
2011-08-29 19:36 ` Konrad Rzeszutek Wilk
2011-09-05 16:16   ` [Xen-devel] " Martin Meier

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.