From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Wright Subject: Screen corruption and crash at boot with Xen 4.1.0 & linux 2.6.39 on some systems Date: Thu, 2 Jun 2011 14:08:03 +0100 (BST) Message-ID: <28878511.39.1307020083395.JavaMail.root@zimbra.overnetdata.com> References: <22045383.16.1307017943479.JavaMail.root@zimbra.overnetdata.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_38_4843653.1307020083394" Return-path: In-Reply-To: <22045383.16.1307017943479.JavaMail.root@zimbra.overnetdata.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org ------=_Part_38_4843653.1307020083394 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit I have a custom built system based on LFS 6.6 with xen 4.1.0 & linux 2.6.39 built from source. The system boots correctly on one system (after a problem with the USB disk has been worked around), however when I try to boot the same system on another machine the screen corrupts shortly after handover from the bootloader. This happens on 2 out of the 3 machines I have tried it on. I was originally using xen 4.1.0 & linux 2.6.38.7, and with this combination the bootloader would work correctly, xen would work correctly and it would crash and the screen corrupt on the handover from xen to linux. I had a hunt around and found http://wiki.xensource.com/xenwiki/XenPVOPSDRM which talks about the graphics subsystem and says "What is boils down to is: if you want to use a stock kernel from ftp.kernel.org wait till 2.6.39 gets released". As a result I have switched to xen 4.1.0 & linux 2.6.39 but get the same result. The motherboard is a Gigabit GA-MA69VM-S2. The lspci -vvv output is attached. What I did notice is the way the screen resolution changes during boot is different for the two main machines that I test on. On the machine that works, instead of the 80x25 console that I'm used to with xen 3.4.1, I get a much higher resolution output with two penguins at the top with 4.1.0. When I boot the system without the xen hypervisor linux starts at the 80x25 resolution but then quickly puts the screen into high resolution. On the machine that fails, when I boot the system without the xen hypervisor, linux starts at 80x25 resolution, appears to do a resolution change (whole screen flickers) a few seconds later but leaves the resolution at 80x25. Am I doing something wrong? Is this a bug? Is there a workaround? Should I try a different kernel version? I'm happy to live with the 80x25 resolution screen but none of the screen resolution options that I've tried have had any effect. Thanks, Anthony. ------=_Part_38_4843653.1307020083394 Content-Type: application/octet-stream; name=gs_ma69vm_s2-lspci-vvv Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=gs_ma69vm_s2-lspci-vvv 00:00.0 Host bridge: ATI Technologies Inc RS690 Host Bridge Subsystem: Giga-byte Technology Device 5000 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [44] HyperTransport: MSI Mapping Enable+ Fixed+ Capabilities: [b0] Subsystem: ATI Technologies Inc RS690 PCI to PCI Bridge (Internal gfx) 00:12.0 SATA controller: ATI Technologies Inc SB600 Non-Raid-5 SATA (prog-if 01 [AHCI 1.0]) Subsystem: Giga-byte Technology Device b002 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Region 1: I/O ports at Region 2: I/O ports at Region 3: I/O ports at Region 4: I/O ports at f900 [size=16] 00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA) Subsystem: Giga-byte Technology Device a002 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- 01:05.0 VGA compatible controller: ATI Technologies Inc RS690 [Radeon X1200 Series] (prog-if 00 [VGA controller]) Subsystem: Giga-byte Technology Device d000 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- [disabled] Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [80] MSI: Mask- 64bit+ Count=1/1 Enable- Address: 0000000000000000 Data: 0000 02:0f.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8110SC/8169SC Gigabit Ethernet (rev 10) Subsystem: Giga-byte Technology Device e000 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR-