Screen corruption and crash at boot with Xen 4.1.0 & linux 2.6.39 on some systems

Screen corruption and crash at boot with Xen 4.1.0 & linux 2.6.39 on some systems

[Anthony Wright]

[-- Attachment #1: Type: text/plain, Size: 1920 bytes --]

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.

[-- Attachment #2: gs_ma69vm_s2-lspci-vvv --]
[-- Type: application/octet-stream, Size: 11796 bytes --]

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- <TAbort- <MAbort+ >SERR- <PERR- INTx-
	Latency: 32
	Kernel modules: ati-agp

00:01.0 PCI bridge: ATI Technologies Inc RS690 PCI to PCI Bridge (Internal gfx) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 99
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=68
	I/O behind bridge: 0000e000-0000efff
	Memory behind bridge: fde00000-fdffffff
	Prefetchable memory behind bridge: 00000000d8000000-00000000dfffffff
	Secondary status: 66MHz+ FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA- VGA+ MAbort- >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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32
	Interrupt: pin A routed to IRQ 17
	Region 0: I/O ports at ff00 [size=8]
	Region 1: I/O ports at fe00 [size=4]
	Region 2: I/O ports at fd00 [size=8]
	Region 3: I/O ports at fc00 [size=4]
	Region 4: I/O ports at fb00 [size=16]
	Region 5: Memory at fe02f000 (32-bit, non-prefetchable) [size=1K]
	Capabilities: [60] 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-
	Kernel driver in use: ahci

00:13.0 USB Controller: ATI Technologies Inc SB600 USB (OHCI0) (prog-if 10 [OHCI])
	Subsystem: Giga-byte Technology Device 5004
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32, Cache Line Size: 4 bytes
	Interrupt: pin A routed to IRQ 19
	Region 0: Memory at fe02e000 (32-bit, non-prefetchable) [size=4K]
	Kernel driver in use: ohci_hcd

00:13.1 USB Controller: ATI Technologies Inc SB600 USB (OHCI1) (prog-if 10 [OHCI])
	Subsystem: Giga-byte Technology Device 5004
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32, Cache Line Size: 4 bytes
	Interrupt: pin B routed to IRQ 20
	Region 0: Memory at fe02d000 (32-bit, non-prefetchable) [size=4K]
	Kernel driver in use: ohci_hcd

00:13.2 USB Controller: ATI Technologies Inc SB600 USB (OHCI2) (prog-if 10 [OHCI])
	Subsystem: Giga-byte Technology Device 5004
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32, Cache Line Size: 4 bytes
	Interrupt: pin C routed to IRQ 21
	Region 0: Memory at fe02c000 (32-bit, non-prefetchable) [size=4K]
	Kernel driver in use: ohci_hcd

00:13.3 USB Controller: ATI Technologies Inc SB600 USB (OHCI3) (prog-if 10 [OHCI])
	Subsystem: Giga-byte Technology Device 5004
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32, Cache Line Size: 4 bytes
	Interrupt: pin B routed to IRQ 20
	Region 0: Memory at fe02b000 (32-bit, non-prefetchable) [size=4K]
	Kernel driver in use: ohci_hcd

00:13.4 USB Controller: ATI Technologies Inc SB600 USB (OHCI4) (prog-if 10 [OHCI])
	Subsystem: Giga-byte Technology Device 5004
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32, Cache Line Size: 4 bytes
	Interrupt: pin C routed to IRQ 21
	Region 0: Memory at fe02a000 (32-bit, non-prefetchable) [size=4K]
	Kernel driver in use: ohci_hcd

00:13.5 USB Controller: ATI Technologies Inc SB600 USB Controller (EHCI) (prog-if 20 [EHCI])
	Subsystem: Giga-byte Technology Device 5004
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32, Cache Line Size: 64 bytes
	Interrupt: pin D routed to IRQ 18
	Region 0: Memory at fe029000 (32-bit, non-prefetchable) [size=256]
	Capabilities: [c0] 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-
		Bridge: PM- B3+
	Capabilities: [e4] Debug port: BAR=1 offset=00e0
	Kernel driver in use: ehci_hcd

00:14.0 SMBus: ATI Technologies Inc SBx00 SMBus Controller (rev 14)
	Subsystem: Giga-byte Technology Device 4385
	Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Region 0: I/O ports at 0b00 [size=16]
	Capabilities: [b0] HyperTransport: MSI Mapping Enable- Fixed+

00:14.1 IDE interface: ATI Technologies Inc SB600 IDE (prog-if 8a [Master SecP PriP])
	Subsystem: Giga-byte Technology Device 5002
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32
	Interrupt: pin A routed to IRQ 255
	Region 0: I/O ports at <unassigned>
	Region 1: I/O ports at <unassigned>
	Region 2: I/O ports at <unassigned>
	Region 3: I/O ports at <unassigned>
	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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32, Cache Line Size: 4 bytes
	Interrupt: pin A routed to IRQ 11
	Region 0: Memory at fe024000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:14.3 ISA bridge: ATI Technologies Inc SB600 PCI to LPC Bridge
	Subsystem: Giga-byte Technology Device 5001
	Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0

00:14.4 PCI bridge: ATI Technologies Inc SBx00 PCI to PCI Bridge (prog-if 01 [Subtractive decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop+ ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64
	Bus: primary=00, secondary=02, subordinate=02, sec-latency=64
	I/O behind bridge: 0000d000-0000dfff
	Memory behind bridge: fdd00000-fddfffff
	Prefetchable memory behind bridge: fdc00000-fdcfffff
	Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Capabilities: [80] HyperTransport: Host or Secondary Interface
		Command: WarmRst+ DblEnd- DevNum=0 ChainSide- HostHide+ Slave- <EOCErr- DUL-
		Link Control: CFlE- CST- CFE- <LkFail- Init+ EOC- TXO- <CRCErr=0 IsocEn- LSEn- ExtCTL- 64b-
		Link Config: MLWI=16bit DwFcIn- MLWO=16bit DwFcOut- LWI=16bit DwFcInEn- LWO=16bit DwFcOutEn-
		Revision ID: 1.02
		Link Frequency: 1.0GHz
		Link Error: <Prot- <Ovfl- <EOC- CTLTm-
		Link Frequency Capability: 200MHz+ 300MHz- 400MHz+ 500MHz- 600MHz+ 800MHz+ 1.0GHz+ 1.2GHz- 1.4GHz- 1.6GHz- Vend-
		Feature Capability: IsocFC- LDTSTOP+ CRCTM- ECTLT- 64bA- UIDRD- ExtRS- UCnfE-

00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
	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-

00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
	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-

00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
	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-
	Capabilities: [f0] Secure device <?>

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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32, Cache Line Size: 4 bytes
	Interrupt: pin A routed to IRQ 5
	Region 0: Memory at d8000000 (64-bit, prefetchable) [size=128M]
	Region 2: Memory at fdff0000 (64-bit, non-prefetchable) [size=64K]
	Region 4: I/O ports at ee00 [size=256]
	Region 5: Memory at fde00000 (32-bit, non-prefetchable) [size=1M]
	Expansion ROM at <unassigned> [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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32 (8000ns min, 16000ns max), Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 16
	Region 0: I/O ports at de00 [size=256]
	Region 1: Memory at fddff000 (32-bit, non-prefetchable) [size=256]
	[virtual] Expansion ROM at fdc00000 [disabled] [size=128K]
	Capabilities: [dc] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0-,D1+,D2+,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Kernel driver in use: r8169
	Kernel modules: r8169


[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

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

Re: Screen corruption and crash at boot with Xen 4.1.0 & linux 2.6.39 on some systems

[Konrad Rzeszutek Wilk]

On Thu, Jun 02, 2011 at 02:08:03PM +0100, Anthony Wright wrote:
> 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.

We missed a couple of patches and had to revert some.
> 
> 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?

Try git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stable/2.6.39.x

and if that does not work, on top of that branch, also try reverting these two patches:

03a80665341bbb9a57064c2ddeca13b554d56893
("drm/radeon/nouveau: fix build regression on alpha due to Xen changes.)
and 
d87dfdbfc91c5e37288e7e8f7afdd992ba61a60d.
("Revert "ttm: Utilize the DMA API for pages that have TTM_PAGE_FLAG_DMA32 set.")

> 
> 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.


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

Re: Screen corruption and crash at boot with Xen 4.1.0 & linux 2.6.39 on some systems

[Anthony Wright]

Hi Konrad,

Sorry to ask the same question again, but does 2.6.39.1 include the
patches from stable/2.6.39.x  that fixed this problem?

thanks,

Anthony.
[I've cc'd xen-devel as I think I hit reply rather than reply-all a
little while back]

On 07/06/2011 15:52, Konrad Rzeszutek Wilk wrote:
> On Tue, Jun 07, 2011 at 12:42:27PM +0100, Anthony Wright wrote:
>> I ran with the stable/2.6.39.x version and that's fixed the problem
>> (didn't need to do the revert).
>>
>> The first build failed because mm/swapfile.c had an undefined reference
>> to frontswap_init and by default FRONTSWAP is not set.
> <nods>That is fixed now.
>> Are these patches in mainline 2.6.39.1 or will I have to wait for 3.0.0 ?
> No. The VGA support one might show up in 3.0 depending on Linus. I sent an
> email asking him to pull it: https://lkml.org/lkml/2011/6/6/391
> but it could be considered a feature and the merge window for features elapsed :-(
>
> It could also be considered a bug ...  anyhow leaving it up to Linus
> and I would recommend you use 2.6.39.1 and I can respond to this email thread
> whether Linus has pulled the patch or not.
>
>> thanks,
>>
>> Anthony
>>
>> On 02/06/2011 15:51, Konrad Rzeszutek Wilk wrote:
>>> On Thu, Jun 02, 2011 at 02:08:03PM +0100, Anthony Wright wrote:
>>>> 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.
>>> We missed a couple of patches and had to revert some.
>>>> 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?
>>> Try git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stable/2.6.39.x
>>>
>>> and if that does not work, on top of that branch, also try reverting these two patches:
>>>
>>> 03a80665341bbb9a57064c2ddeca13b554d56893
>>> ("drm/radeon/nouveau: fix build regression on alpha due to Xen changes.)
>>> and 
>>> d87dfdbfc91c5e37288e7e8f7afdd992ba61a60d.
>>> ("Revert "ttm: Utilize the DMA API for pages that have TTM_PAGE_FLAG_DMA32 set.")
>>>
>>>> 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.
>>>> _______________________________________________
>>>> Xen-devel mailing list
>>>> Xen-devel@lists.xensource.com
>>>> http://lists.xensource.com/xen-devel

Re: Screen corruption and crash at boot with Xen 4.1.0 & linux 2.6.39 on some systems

[Konrad Rzeszutek Wilk]

On Thu, Jun 09, 2011 at 01:59:26PM +0100, Anthony Wright wrote:
> Hi Konrad,
> 
> Sorry to ask the same question again, but does 2.6.39.1 include the

That is OK.

> patches from stable/2.6.39.x  that fixed this problem?

No. And it looks as Linus did not pull the VGA support for 3.0 so
that will have to wait till 3.1.

In the meatime as an internim solution I would recommend you use
stable/2.6.39.x tree. Not sure why I said "recommend you use 2.6.39.1"
in the previous email - I meant stable/2.6.39.x ..

.. snip.
> >> Are these patches in mainline 2.6.39.1 or will I have to wait for 3.0.0 ?
> > No. The VGA support one might show up in 3.0 depending on Linus. I sent an
> > email asking him to pull it: https://lkml.org/lkml/2011/6/6/391
> > but it could be considered a feature and the merge window for features elapsed :-(
> >
> > It could also be considered a bug ...  anyhow leaving it up to Linus
> > and I would recommend you use 2.6.39.1 and I can respond to this email thread
> > whether Linus has pulled the patch or not.

Re: Screen corruption and crash at boot with Xen 4.1.0 & linux 2.6.39 on some systems

[Anthony Wright]

On 07/06/2011 15:52, Konrad Rzeszutek Wilk wrote:
> No. The VGA support one might show up in 3.0 depending on Linus. I sent an
> email asking him to pull it: https://lkml.org/lkml/2011/6/6/391
> but it could be considered a feature and the merge window for features elapsed :-(
>
> It could also be considered a bug ...  anyhow leaving it up to Linus
> and I would recommend you use 2.6.39.1 and I can respond to this email thread
> whether Linus has pulled the patch or not.
I've been using the stable/vga.support branch reference in the lkml
email on 3.0.0-rc3 and it worked perfectly. I've just upgraded to rc4,
and all I get now is a blank screen. Is there any chance of a fix?

thanks,

Anthony.

Re: Screen corruption and crash at boot with Xen 4.1.0 & linux 2.6.39 on some systems

[Konrad Rzeszutek Wilk]

On Tue, Jun 28, 2011 at 01:10:48PM +0100, Anthony Wright wrote:
> On 07/06/2011 15:52, Konrad Rzeszutek Wilk wrote:
> > No. The VGA support one might show up in 3.0 depending on Linus. I sent an
> > email asking him to pull it: https://lkml.org/lkml/2011/6/6/391
> > but it could be considered a feature and the merge window for features elapsed :-(
> >
> > It could also be considered a bug ...  anyhow leaving it up to Linus
> > and I would recommend you use 2.6.39.1 and I can respond to this email thread
> > whether Linus has pulled the patch or not.
> I've been using the stable/vga.support branch reference in the lkml
> email on 3.0.0-rc3 and it worked perfectly. I've just upgraded to rc4,
> and all I get now is a blank screen. Is there any chance of a fix?

You can respond to this thread: https://lkml.org/lkml/2011/6/6/391

and tell Linus that you are seriously hampered by the lack of the stable/vga.support
and you urge him to pull it in.