[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xen-bugs
Subject:    [Xen-bugs] [Bug 969] New: Hypervisor does not initialise VGA
From:       bugzilla-daemon () lists ! xensource ! com
Date:       2007-04-18 21:37:06
Message-ID: bug-969-3 () http ! bugzilla ! xensource ! com/bugzilla/
[Download RAW message or body]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=969

           Summary: Hypervisor does not initialise VGA console correctly
           Product: Xen
           Version: unstable
          Platform: x86-64
        OS/Version: Linux
            Status: NEW
          Severity: minor
          Priority: P2
         Component: Hypervisor
        AssignedTo: xen-bugs@lists.xensource.com
        ReportedBy: greenrd@greenrd.org


This bug has existed for over a year, in every snapshot of Xen I have tried
(can't remember if there was a time before that when it worked right). On my
hardware, the hypervisor does not initialise the VGA console correctly,
resulting in unreadable garbage on the display, until X starts, at which point
the display is OK again. (I have tried with and without the option
vga=text-80x50 and the result is the same.)

The workaround is to put console=com1 on the command line, which disables vga
output.

Interestingly, I can reproduce a similar-looking garbage effect if I boot a
normal Linux console with vga=ask and choose 80x60 mode. But from my reading of
the code, xen shouldn't use 80x60 mode by default, and certainly not when I
tell it to use 80x50.

I am running kernel-xen-2.6.20-2925.5.fc7 from Fedora 7 test 3 (which contains
just xen changeset 13132 with compile fix and version string patches) on an
Intel Pentium 4.

>From lspci -v -v:

01:00.0 VGA compatible controller: ATI Technologies Inc RV370 5B60 [Radeon X300
(PCIE)] (prog-if 00 [VGA])
        Subsystem: ATI Technologies Inc Unknown device 0402
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR-
        Latency: 0, Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 11
        Region 0: Memory at d0000000 (32-bit, prefetchable) [size=128M]
        Region 1: I/O ports at dc00 [size=256]
        Region 2: Memory at dfde0000 (32-bit, non-prefetchable) [size=64K]
        Expansion ROM at dfe00000 [disabled] [size=128K]
        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: [58] Express Endpoint IRQ 0
                Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag+
                Device: Latency L0s <128ns, L1 <2us
                Device: AtnBtn- AtnInd- PwrInd-
                Device: Errors: Correctable- Non-Fatal+ Fatal+ Unsupported-
                Device: RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
                Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
                Link: Supported Speed 2.5Gb/s, Width x16, ASPM L0s L1, Port 0
                Link: Latency L0s <128ns, L1 <1us
                Link: ASPM Disabled RCB 64 bytes CommClk+ ExtSynch-
                Link: Speed 2.5Gb/s, Width x16
        Capabilities: [80] Message Signalled Interrupts: 64bit+ Queue=0/0
Enable-
                Address: 0000000000000000  Data: 0000


-- 
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
[prev in list] [next in list] [prev in thread] [next in thread]