[Top] [All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Problem: Pattern with vertical colored lines on the dom0 screen

  • To: Dietmar Hahn <dietmar.hahn@xxxxxxxxxxxxxx>
  • From: Jean Guyader <jean.guyader@xxxxxxxxx>
  • Date: Fri, 24 Sep 2010 11:19:08 +0100
  • Cc: Xen-devel <Xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Fri, 24 Sep 2010 03:20:06 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=sAfxyu9T6h06Npbd9SoSDszubFxZmFnOvC5TdZqQca7Q70dViMN7JfzlVbEZ4+uOvK i+aob0hD/RoumxIwxyJjkoCO4WKIUGR4NBMaJfjmIKNgQpcoqZTcmOOz9Kh97NBt8dqS wOyap9kEQbUmUIiZkWaA4a5aNoq76h3ypKGzs=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
Hi,

Is it a Lenovo (T410, T510) by any chance?

Jean

On 17 September 2010 14:20, Dietmar Hahn <dietmar.hahn@xxxxxxxxxxxxxx> wrote:
> Hi list,
>
> I have a problem with a new laptop (reproducable on other machines too) and 
> the
> xen hypervisor.
> When the hypervisor gets booted with VESA mode 800x600 I see some messages and
> then the screen contents is switched into a pattern of vertical colored lines
> and never comes back.
> In text mode all works well, but later the pattern appears when the X servers
> starts.
> I disabled VTd in the bios and now all went fine.
> I saw this first with SLES11 SP1 but could reproduce it with the xen-unstable
> hypervisor.
>
> When I start the linux kernel native on the machine with or without VTd all
> is running very well.
>
> Following data:
> cpu: Intel(R) Core(TM) i5 CPU  M 540  @ 2.53GHz with integrated graphics
>
> #lspci
> 00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 02)
> 00:02.0 VGA compatible controller: Intel Corporation Core Processor 
> Integrated Graphics Controller (rev 02)
> 00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series 
> Chipset HECI Controller (rev 06)
> 00:16.2 IDE interface: Intel Corporation 5 Series/3400 Series Chipset PT IDER 
> Controller (rev 06)
> 00:16.3 Serial controller: Intel Corporation 5 Series/3400 Series Chipset KT 
> Controller (rev 06)
> 00:19.0 Ethernet controller: Intel Corporation 82577LM Gigabit Network 
> Connection (rev 05)
> 00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 
> Enhanced Host Controller (rev 05)
> 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High 
> Definition Audio (rev 05)
> 00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI 
> Express Root Port 6 (rev 05)
> 00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 
> Enhanced Host Controller (rev 05)
> 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a5)
> 00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface 
> Controller (rev 05)
> 00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 6 
> port SATA AHCI Controller (rev 05)
> 00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus 
> Controller (rev 05)
> 00:1f.6 Signal processing controller: Intel Corporation 5 Series/3400 Series 
> Chipset Thermal Subsystem (rev 05)
> 48:03.0 CardBus bridge: O2 Micro, Inc. Cardbus bridge (rev 01)
> 48:03.1 CardBus bridge: O2 Micro, Inc. Cardbus bridge (rev 01)
> 48:03.2 SD Host controller: O2 Micro, Inc. Integrated MMC/SD Controller (rev 
> 02)
> 48:03.3 Mass storage controller: O2 Micro, Inc. Integrated MS/xD Controller 
> (rev 02)
> 48:03.4 FireWire (IEEE 1394): O2 Micro, Inc. Firewire (IEEE 1394) (rev 07)
> ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture 
> Generic Non-core Registers (rev 02)
> ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture 
> System Address Decoder (rev 02)
> ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 02)
> ff:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 02)
> ff:02.2 Host bridge: Intel Corporation Core Processor Reserved (rev 02)
> ff:02.3 Host bridge: Intel Corporation Core Processor Reserved (rev 02)
>
> I booted xen with VTd enabled and iommu=verbose an here are the messages:
>
>  \ \/ /___ _ __
>  \  // _ \ '_ \
>  /  \  __/ | | |
>  /_/\_\___|_| |_|
>
>  _  _    _   _     ____  _  _   _  _     _  _  _       _   ____
>  | || |  / _ \ / _ \   |___ \/ |/ _ \ / _ \/ |   / _ \| || |     / _ \ |___ \
>  | || |_| | | | | | |    __) | | | | | (_) | |  | | | | || |_ __| | | |  __) |
>  |__   _| |_| | |_| |   / __/| | |_| |\__, | |  | |_| |__   _|__| |_| | / __/ 
> _
>    |_|(_)___(_)___/___|_____|_|\___/   /_/|_|___\___/   |_|     
> \___(_)_____(_)
>                  |_____|                   |_____|
>   __
>  / /_
>  | '_ \
>  | (_) |
>  \___/
>
> (XEN) Xen version 4.0.0_21091_04-0.2.6 (abuild@) (gcc version 4.3.4 
> [gcc-4_3-branch revision 152973] (SUSE Linux) ) Thu May 20 11:44:41 UTC 2010
> (XEN) Latest ChangeSet: 21091
> (XEN) Console output is synchronous.
> (XEN) Command line: vga=mode-0x314 console=com1,vga com1=38400 sync_console 
> debug=yes guest_loglvl=all iommu=verbose crashkernel=256M@16M
> (XEN) Video information:
> (XEN)  VGA is graphics mode 800x600, 16 bpp
> (XEN)  VBE/DDC methods: V2; EDID transfer time: 1 seconds
> (XEN) Disc information:
> (XEN)  Found 2 MBR signatures
> (XEN)  Found 2 EDD information structures
> (XEN) Xen-e820 RAM map:
> (XEN)  0000000000000000 - 000000000009bc00 (usable)
> (XEN)  000000000009bc00 - 00000000000a0000 (reserved)
> (XEN)  00000000000dc000 - 0000000000100000 (reserved)
> (XEN)  0000000000100000 - 00000000ba95d000 (usable)
> (XEN)  00000000ba95d000 - 00000000bac40000 (reserved)
> (XEN)  00000000bac40000 - 00000000bb27c000 (usable)
> (XEN)  00000000bb27c000 - 00000000bb282000 (reserved)
> (XEN)  00000000bb282000 - 00000000bb3e0000 (usable)
> (XEN)  00000000bb3e0000 - 00000000bb40f000 (reserved)
> (XEN)  00000000bb40f000 - 00000000bb651000 (usable)
> (XEN)  00000000bb651000 - 00000000bb652000 (reserved)
> (XEN)  00000000bb652000 - 00000000bb6d3000 (ACPI NVS)
> (XEN)  00000000bb6d3000 - 00000000bb70f000 (reserved)
> (XEN)  00000000bb70f000 - 00000000bb717000 (usable)
> (XEN)  00000000bb717000 - 00000000bb71f000 (reserved)
> (XEN)  00000000bb71f000 - 00000000bb76f000 (usable)
> (XEN)  00000000bb76f000 - 00000000bb79f000 (ACPI NVS)
> (XEN)  00000000bb79f000 - 00000000bb7de000 (usable)
> (XEN)  00000000bb7de000 - 00000000bb7ff000 (ACPI data)
> (XEN)  00000000bb7ff000 - 00000000bb800000 (usable)
> (XEN)  00000000bb800000 - 00000000c0000000 (reserved)
> (XEN)  00000000e0000000 - 00000000f0000000 (reserved)
> (XEN)  00000000f272c000 - 00000000f272d000 (reserved)
> (XEN)  00000000feaff000 - 00000000feb00000 (reserved)
> (XEN)  00000000fec00000 - 00000000fec10000 (reserved)
> (XEN)  00000000fed00000 - 00000000fed00400 (reserved)
> (XEN)  00000000fed1c000 - 00000000fed90000 (reserved)
> (XEN)  00000000fee00000 - 00000000fee01000 (reserved)
> (XEN)  00000000ff000000 - 0000000100000000 (reserved)
> (XEN)  0000000100000000 - 0000000138000000 (usable)
> (XEN) Kdump: 256MB (262144kB) at 0x1000000
> (XEN) ACPI: RSDP 000F5400, 0024 (r2 FUJ   )
> (XEN) ACPI: XSDT BB7F29E3, 008C (r1 FSC    PC        1080000 FUJ       100)
> (XEN) ACPI: FACP BB7E0000, 00F4 (r3 FSC    PC        1080000 FUJ       100)
> (XEN) ACPI: DSDT BB7E1000, B8C7 (r2 FUJ    FJNB216   1080000 FUJ       100)
> (XEN) ACPI: FACS BB78BFC0, 0040
> (XEN) ACPI: SSDT BB7FE366, 00BA (r1 FUJ    FJNB216   1080000 FUJ       100)
> (XEN) ACPI: HPET BB7FE514, 0038 (r1 FUJ    FJNB216   1080000 FUJ       100)
> (XEN) ACPI: MCFG BB7FE54C, 003C (r1 FUJ    FJNB216   1080000 FUJ       100)
> (XEN) ACPI: SSDT BB7FE588, 042F (r1 FUJ    FJNB216   1080000 FUJ       100)
> (XEN) ACPI: SSDT BB7FE9B7, 02C3 (r1 FUJ    FJNB216   1080000 FUJ       100)
> (XEN) ACPI: APIC BB7FEC7A, 0084 (r1 FUJ    FJNB216   1080000 FUJ       100)
> (XEN) ACPI: SPCR BB7FECFE, 0050 (r1 FUJ    FJNB216   1080000 FUJ       100)
> (XEN) ACPI: SLIC BB7FED4E, 0176 (r1 FSC    PC        1080000 FUJ       100)
> (XEN) ACPI: BOOT BB7FEEC4, 0028 (r1 FUJ    FJNB216   1080000 FUJ       100)
> (XEN) ACPI: ASF! BB7EE000, 00A0 (r16 FUJ    FJNB216   1080000 FUJ       100)
> (XEN) ACPI: DMAR BB7ED000, 00B8 (r1 INTEL  CP_DALE         1 INTL        1)
> (XEN) ACPI: SSDT BB7DF000, 0A50 (r1  PmRef    CpuPm     3000 INTL 20060912)
> (XEN) System RAM: 3606MB (3692780kB)
> (XEN) Domain heap initialised
> (XEN) Processor #0 6:5 APIC version 21
> (XEN) Processor #4 6:5 APIC version 21
> (XEN) Processor #1 6:5 APIC version 21
> (XEN) Processor #5 6:5 APIC version 21
> (XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
> (XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
> (XEN) [VT-D]dmar.c:679: Host address width 36
> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD:
> (XEN) [VT-D]dmar.c:398:   dmaru->address = fed90000
> (XEN) [VT-D]dmar.c:334:   endpoint: 0:1b.0
> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD:
> (XEN) [VT-D]dmar.c:398:   dmaru->address = fed91000
> (XEN) [VT-D]dmar.c:334:   endpoint: 0:2.0
> (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD:
> (XEN) [VT-D]dmar.c:398:   dmaru->address = fed93000
> (XEN) [VT-D]dmar.c:411:   flags: INCLUDE_ALL
> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR:
> (XEN) [VT-D]dmar.c:334:   endpoint: 0:1d.0
> (XEN) [VT-D]dmar.c:334:   endpoint: 0:1a.0
> (XEN) [VT-D]dmar.c:571:   RMRR region: base_addr bb6e9000 end_address bb6fffff
> (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR:
> (XEN) [VT-D]dmar.c:334:   endpoint: 0:2.0
> (XEN) [VT-D]dmar.c:571:   RMRR region: base_addr bde00000 end_address bfffffff
> (XEN) Using scheduler: SMP Credit Scheduler (credit)
> (XEN) Detected 2527.342 MHz processor.
> (XEN) Initing memory sharing.
> (XEN) VMX: Supported advanced features:
> (XEN)  - APIC MMIO access virtualisation
> (XEN)  - APIC TPR shadow
> (XEN)  - Extended Page Tables (EPT)
> (XEN)  - Virtual-Processor Identifiers (VPID)
> (XEN)  - Virtual NMI
> (XEN)  - MSR direct-access bitmap
> (XEN)  - Unrestricted Guest
> (XEN) HVM: ASIDs enabled.
> (XEN) HVM: VMX enabled
> (XEN) HVM: Hardware Assisted Paging detected.
> (XEN) [VT-D]iommu.c:1078: drhd->address = fed91000 iommu->reg = 
> ffff82c3fff57000
> (XEN) [VT-D]iommu.c:1080: cap = c0000020230272 ecap = 1000
> (XEN) [VT-D]iommu.c:1078: drhd->address = fed90000 iommu->reg = 
> ffff82c3fff56000
> (XEN) [VT-D]iommu.c:1080: cap = c9008020e30272 ecap = 1000
> (XEN) [VT-D]iommu.c:1078: drhd->address = fed93000 iommu->reg = 
> ffff82c3fff55000
> (XEN) [VT-D]iommu.c:1080: cap = c9008020630272 ecap = 1000
> (XEN) Intel VT-d Snoop Control not supported.
> (XEN) Intel VT-d DMA Passthrough not supported.
> (XEN) Intel VT-d Queued Invalidation not supported.
> (XEN) Intel VT-d Interrupt Remapping not supported.
> (XEN) I/O virtualisation enabled
> (XEN) I/O virtualisation for PV guests disabled
> (XEN) Enabled directed EOI with ioapic_ack_old on!
> (XEN) Total of 4 processors activated.
> (XEN) ENABLING IO-APIC IRQs
> (XEN)  -> Using old ACK method
> (XEN) TSC is reliable, synchronization unnecessary
> (XEN) Platform timer is 14.318MHz HPET
> (XEN) Allocated console ring of 16 KiB.
> (XEN) microcode.c:73:d32767 microcode: CPU1 resumed
> (XEN) microcode.c:73:d32767 microcode: CPU3 resumed
> (XEN) Brought up 4 CPUs
> (XEN) microcode.c:73:d32767 microcode: CPU2 resumed
> (XEN) Created cpupool 0 with scheduler SMP Credit Scheduler (credit)
> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:0.0
> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:2.0
> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:16.0
> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:16.2
> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:16.3
> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:19.0
> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1a.0
> (XEN) [VT-D]iommu.c:1325: d0:PCIe: map bdf = 0:1b.0
> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1d.0
> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.0
> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.2
> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.3
> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 0:1f.6
> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 48:3.0
> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 48:3.1
> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 48:3.2
> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 48:3.3
> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = 48:3.4
> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = ff:0.0
> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = ff:0.1
> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = ff:2.0
> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = ff:2.1
> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = ff:2.2
> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = ff:2.3
> (XEN) [VT-D]iommu.c:695: iommu_enable_translation: iommu->reg = 
> ffff82c3fff57000
> (XEN) [VT-D]iommu.c:695: iommu_enable_translation: iommu->reg = 
> ffff82c3fff56000
> (XEN) [VT-D]iommu.c:695: iommu_enable_translation: iommu->reg = 
> ffff82c3fff55000
> (XEN) *** LOADING DOMAIN 0 ***
> (XEN)  Xen  kernel: 64-bit, lsb, compat32
> (XEN)  Dom0 kernel: 64-bit, lsb, paddr 0x2000 -> 0x765000
> (XEN) PHYSICAL MEMORY ARRANGEMENT:
> (XEN)  Dom0 alloc.:   0000000132000000->0000000134000000 (874416 pages to be 
> allocated)
> (XEN) VIRTUAL MEMORY ARRANGEMENT:
> (XEN)  Loaded kernel: ffffffff80002000->ffffffff80765000
> (XEN)  Init. ramdisk: ffffffff80765000->ffffffff815b7600
> (XEN)  Phys-Mach map: ffffea0000000000->ffffea00006bbd80
> (XEN)  Start info:    ffffffff815b8000->ffffffff815b84b4
> (XEN)  Page tables:   ffffffff815b9000->ffffffff815c8000
> (XEN)  Boot stack:    ffffffff815c8000->ffffffff815c9000
> (XEN)  TOTAL:         ffffffff80000000->ffffffff81800000
> (XEN)  ENTRY ADDRESS: ffffffff80002000
> (XEN) Dom0 has maximum 4 VCPUs
> (XEN) Scrubbing Free RAM: .done.
> (XEN) Xen trace buffers: disabled
> (XEN) Std. Loglevel: Errors and warnings
> (XEN) Guest Loglevel: All
> (XEN) **********************************************
> (XEN) ******* WARNING: CONSOLE OUTPUT IS SYNCHRONOUS
> (XEN) ******* This option is intended to aid debugging of Xen by ensuring
> (XEN) ******* that all output is synchronously delivered on the serial line.
> (XEN) ******* However it can introduce SIGNIFICANT latencies and affect
> (XEN) ******* timekeeping. It is NOT recommended for production use!
> (XEN) **********************************************
> (XEN) 3... 2... 1...
> (XEN) Xen is relinquishing VGA console.
> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to 
> Xen)
> (XEN) Freed 184kB init memory.
>
> With staring at the console I could see that the switch to the screen pattern 
> is
> around the following messages (but no guarantee):
> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = ff:0.0
> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = ff:0.1
> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = ff:2.0
> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = ff:2.1
> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = ff:2.2
> (XEN) [VT-D]iommu.c:1332: d0:PCI: map bdf = ff:2.3
>
> I would say that this is a problem with the bios tables or with the
> hypervisor not handle these right. Always the switching of the gfx card into
> graphics mode seems to lead to the problem.
> Any help would be very helpful.
> Thanks.
>
> Dietmar.
>
> --
> Company details: http://ts.fujitsu.com/imprint.html
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

 

©2013 Xen Project, A Linux Foundation Collaborative Project. All Rights Reserved.
Linux Foundation is a registered trademark of The Linux Foundation.
Xen Project is a trademark of The Linux Foundation.

Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.