On Mon, Aug 29, 2011 at 9:36 PM, Konrad Rzeszutek Wilk
<konrad.wilk@xxxxxxxxxx> 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.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home