[Fedora-xen] Dom0 kernels Xen Host connected via remote VNC Session

[Pasi Kärkkäinen]

On Sat, Jan 02, 2010 at 01:10:12PM -0800, Boris Derzhavets wrote:
>    Reports are different  it's easy to see,  but not much.
>    I put in init :-
>        modprobe drm debug=255
>    and rebuilt initrd . It's for sure.
>    Maybe change some other lines ?
>

Hmm.. maybe the 'radeon' module needs some debug parameter aswell?

You could check the radeon module source from the kernel, and figure out
if it has some debug option aswell.. and then enable it.

Then again there is a lot going on with drm/kms/radeon stuff at the
moment, so I'm not surprised if it happens to be broken in 2.6.31.6.

Does it work if you boot the same Jeremy's 2.6.31.6 on baremetal without
Xen? 

-- Pasi

>    Boris.
> 
>    --------------------------------------------------------------------------
> 
>    From: Pasi Kärkkäinen <pasik at iki.fi>
>    To: Boris Derzhavets <bderzhavets at yahoo.com>
>    Cc: fedora-xen at redhat.com; M A Young <m.a.young at durham.ac.uk>
>    Sent: Sat, January 2, 2010 11:26:01 PM
>    Subject: Re: [Fedora-xen] Dom0 kernels Xen Host connected via remote VNC
>    Session
>    On Sat, Jan 02, 2010 at 10:21:14PM +0200, Pasi Kärkkäinen wrote:
>    > On Sat, Jan 02, 2010 at 12:10:36PM -0800, Boris Derzhavets wrote:
>    > >    > Basicly you should extract the initrd image, and change the
>    "modprobe
>    > >    drm"
>    > >    > line to say "modprobe drm debug=255" in the init script. And then
>    > >    > repack the initrd and use the modified initrd instead.
>    > >    Done for Jeremy's 2.6.31.6  - initrd-2.6.31.6.img :-
>    > >
>    > >    init has been modified
>    > >            modprobe -q drm debug=255
>    > >    Image rebuilt :-
>    > >              find . | cpio -o -c | gzip -9 > /boot/initrd-2.6.31.6.img
>    > >    Xen Host reloaded .
>    > >    Dmesg reports now :-
>    > >
>    > >    [drm] Initialized drm 1.1.0 20060810
>    > >    [drm] radeon default to kernel modesetting.
>    > >    [drm] radeon kernel modesetting enabled.
>    > >    [drm:drm_init],
>    > >    [drm:drm_get_dev],
>    > >    xen: registering gsi 16 triggering 0 polarity 1
>    > >    xen_allocate_pirq: returning irq 16 for gsi 16
>    > >    xen: --> irq=16
>    > >    xen_set_ioapic_routing: irq 16 gsi 16 vector 152 ioapic 0 pin 16
>    > >    triggering 1 polarity 1
>    > >    radeon 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
>    > >    radeon 0000:01:00.0: setting latency timer to 64
>    > >    [drm:drm_get_minor],
>    > >    [drm:drm_get_minor], new minor assigned 64
>    > >    [drm:drm_get_minor],
>    > >    [drm:drm_get_minor], new minor assigned 0
>    > >    [drm] radeon: Initializing kernel modesetting.
>    > >    [drm:radeon_driver_load_kms] *ERROR* Failed to initialize radeon,
>    > >    disabling IOCTL
>    > >    [drm:drm_put_minor], release secondary minor 0
>    > >    [drm:drm_put_minor], release secondary minor 64
>    > >    radeon 0000:01:00.0: PCI INT A disabled
>    > >    radeon: probe of 0000:01:00.0 failed with error -22
>    > >
>    >
>    > Hmm.. isn't this the same output as earlier? Are you sure you used the
>    > new initrd? It doesn't look like it..
>    >
>    > You should get much more debug information from drm when it's loaded
>    > with debug=255.
>    >
> 
>    Example here:
>    [1]http://pasik.reaktio.net/xen/pv_ops-dom0-debug/radeondebug/dmesg-2.6.31.4-2009-10-21-with-ttm-patch.txt
> 
>    do "grep -i drm dmesg-2.6.31.4-2009-10-21-with-ttm-patch.txt" and you'll
>    notice there is a lot more debug information..
> 
>    -- Pasi
> 
> References
> 
>    Visible links
>    1. http://pasik.reaktio.net/xen/pv_ops-dom0-debug/radeondebug/dmesg-2..6.31.4-2009-10-21-with-ttm-patch.txt