[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0 ( 2.6.31) on top of Ubuntu 9.04 Server


  • To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
  • From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
  • Date: Wed, 23 Sep 2009 13:25:26 -0700 (PDT)
  • Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
  • Delivery-date: Wed, 23 Sep 2009 13:26:38 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=lxXGgzItuq/JYD6QFW4kPzcDgFu50Qo7OtfqeLqNX3ayg7Rt1w3+Ag9yRMSuaD6ttkGPSZSPFYutU4Z8qc36AGgsQsZfit2K52lSkgrpLQa1IJRn8hekbg0b5sqZ52QEEhqJqfuuWjXgbPoUKXo4sxMQE1intnAiihTmUWH/00s=;
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

>I assume you're saying that it fails with 2.6.31-pvops dom0? 

Yes.

>How does it fail?  Is it completely non-functional? 

Yes, it is completely non-functional.

>Does the whole system crash? 

No, just in text mode.

> Or does X simply fail to start?  

No. It seems to be running.

>Or it does start but is crippled in some way?

It starts due to logs content during system boot up ,
like on F11, where everything is going fine.
I attached both dmesg.log and Xorg.0.log to previous message for Ubuntu 9.04 Server.

> Does it work with 2.6.31 running without Xen?  How do the log files compare?

I will check it tomorrow.

Boris.

--- On Wed, 9/23/09, Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:

From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: [Xen-devel] Re: Attempt to start X-Server at Xen 3.5 Dom0 ( 2.6.31) on top of Ubuntu 9.04 Server
To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>
Cc: "Xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Konrad Rzeszutek Wilk" <konrad.wilk@xxxxxxxxxx>
Date: Wednesday, September 23, 2009, 3:27 PM

On 09/23/09 08:45, Boris Derzhavets wrote:
> Video card Radeon HD 4560.  X-server starts fine under native
> 2.6.28-11-server
> ubuntu kernel.
>
I assume you're saying that it fails with 2.6.31-pvops dom0?  How does
it fail?  Is it completely non-functional?  Does the whole system
crash?  Or does X simply fail to start?   Or it does start but is
crippled in some way?

Does it work with 2.6.31 running without Xen?  How do the log files compare?

Thanks,
    J

>
> X-Windows Setup :-
>
> Downsize the system:
> vi /etc/default/linux-restricted-modules-common:
> DISABLED_MODULES=âath_hal fc fglrx ltm nvâ Install the X11 bare bone:
>
> # aptitude install x-window-system-core
> # aptitude install fluxbox fluxconf #lightwight windows manager
> # aptitude install dillo #lightweight browser
> # aptitude install xfe #lightweight file manager
> # apttitude install synaptic # To install eset & esetroot
> Change /etc/X11/xorg.conf:
> # dpkg-reconfigure xserver-xorg #guided setup
> Edit /etc/X11/xorg.conf (use âgtf 1024 768 60â to obtain the Modeline
> values)
>  X-server starts fine under native Ubuntu Server kernel  and fluxbox
> is completely functional.
>
> Attempt to start at Xen 3.5 Dom0 (with the most recent 2.6.31)
>
> dmesg output :-
> . . . . . .
>
> [   43.572422] xen_set_ioapic_routing: irq 16 gsi 16 vector 16 ioapic
> 0 pin 16 triggering 1 polarity 1
> [   43.572437] pci 0000:01:00.0: PCI INT A -> GSI 16 (level, low) ->
> IRQ 16
> [   43.710523] [drm] Initialized drm 1.1.0 20060810
> [   43.758245] pci 0000:01:00.0: setting latency timer to 64
> [   43.758433] [drm] Initialized radeon 1.31.0 20080528 for
> 0000:01:00.0 on minor 0
> [   43.763134] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [   44.035133] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [   44.035198] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [   44.035263] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [   44.061841] [drm] Setting GART location based on new memory map
> [   44.095779] [drm] Loading RV730/RV740 PFP Microcode
> [   44.095805] [drm] Loading RV730/RV740 CP Microcode
> [   44.110868] [drm] Resetting GPU
> [   44.215007] [drm] writeback test failed
> [   79.050085] [drm] Resetting GPU
> [  243.858191] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [  243.858263] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [  244.132051] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [  244.132115] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [  244.132181] mtrr: type mismatch for d0000000,10000000 old:
> write-back new: write-combining
> [  244.157265] [drm] Setting GART location based on new memory map
> [  244.190885] [drm] Loading RV730/RV740 PFP Microcode
> [  244.190911] [drm] Loading RV730/RV740 CP Microcode
> [  244.205974] [drm] Resetting GPU
> [  244.310103] [drm] writeback test failed
> [  251.220092] [drm] Resetting GPU
>
> Xorg.0.log :-
>
> (II) AIGLX: Screen 0 is not DRI2 capable
> drmOpenDevice: node name is /dev/dri/card0
> drmOpenDevice: open result is 11, (OK)
> drmOpenByBusid: Searching for BusID pci:0000:01:00.0
> drmOpenDevice: node name is /dev/dri/card0
> drmOpenDevice: open result is 11, (OK)
> drmOpenByBusid: drmOpenMinor returns 11
> drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
> (EE) AIGLX error: Calling driver entry point failed(EE) AIGLX:
> reverting to software rendering
> (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so
> (II) GLX: Initialized DRISWRAST GL provider for screen 0
> (II) RADEON(0): Setting screen physical size to 338 x 270
> (II) config/hal: Adding input device AT Translated Set 2 keyboard
> (II) LoadModule: "evdev"
> (II) Loading /usr/lib/xorg/modules/input//evdev_drv.so
> (II) Module evdev: vendor="X.Org Foundation"
>     compiled for 1.6.0, module version = 2.1.1
>     Module class: X.Org XInput Driver
>     ABI class: X.Org XInput driver, version 4.0
> (**) AT Translated Set 2 keyboard: always reports core events
> (**) AT Translated Set 2 keyboard: Device: "/dev/input/event3"
> (II) AT Translated Set 2 keyboard: Found keys
> (II) AT Translated Set 2 keyboard: Configuring as keyboard
> (II) XINPUT: Adding extended input device "AT Translated Set 2
> keyboard" (type: KEYBOARD)
> (**) Option "xkb_rules" "evdev"
> (**) AT Translated Set 2 keyboard: xkb_rules: "evdev"
> (**) Option "xkb_model" "pc105"
> (**) AT Translated Set 2 keyboard: xkb_model: "pc105"
> (**) Option "xkb_layout" "us"
> (**) AT Translated Set 2 keyboard: xkb_layout: "us"
> (II) config/hal: Adding input device Macintosh mouse button emulation
> (**) Macintosh mouse button emulation: always reports core events
> (**) Macintosh mouse button emulation: Device: "/dev/input/event2"
> (II) Macintosh mouse button emulation: Found 3 mouse buttons
> (II) Macintosh mouse button emulation: Found x and y relative axes
> (II) Macintosh mouse button emulation: Configuring as mouse
> (**) Macintosh mouse button emulation: YAxisMapping: buttons 4 and 5
> (**) Macintosh mouse button emulation: EmulateWheelButton: 4,
> EmulateWheelInertia: 10, EmulateWheelTimeout: 200
> (II) XINPUT: Adding extended input device "Macintosh mouse button
> emulation" (type: MOUSE)
> (**) Macintosh mouse button emulation: (accel) keeping acceleration
> scheme 1
> (**) Macintosh mouse button emulation: (accel) filter chain
> progression: 2.00
> (**) Macintosh mouse button emulation: (accel) filter stage 0: 20.00 ms
> (**) Macintosh mouse button emulation: (accel) set acceleration profile 0
> (II) config/hal: Adding input device HID 062a:0001
> (**) HID 062a:0001: always reports core events
> (**) HID 062a:0001: Device: "/dev/input/event4"
> (II) HID 062a:0001: Found 5 mouse buttons
> (II) HID 062a:0001: Found x and y relative axes
> (II) HID 062a:0001: Configuring as mouse
> (**) HID 062a:0001: YAxisMapping: buttons 4 and 5
> (**) HID 062a:0001: EmulateWheelButton: 4, EmulateWheelInertia: 10,
> EmulateWheelTimeout: 200
> (II) XINPUT: Adding extended input device "HID 062a:0001" (type: MOUSE)
> (**) HID 062a:0001: (accel) keeping acceleration scheme 1
> (**) HID 062a:0001: (accel) filter chain progression: 2.00
> (**) HID 062a:0001: (accel) filter stage 0: 20.00 ms
> (**) HID 062a:0001: (accel) set acceleration profile 0
>
> Boris.
>
>


_______________________________________________
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

 


Rackspace

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