Re: [Xen-devel] [GIT PULL] devel/pat + devel/kms.fixes-0.5 on RV730 PRO [Radeon HD 4650]

[Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>]

On Tue, Aug 17, 2010 at 11:27:08AM -0700, Boris Derzhavets wrote:
> Complete  dmesg report contains entries :-

Impressive.

Can you give provide:
 lspci -vvv
 full serial log console output?
 and what were you doing when this happend? (starting X, playing games?)


> 
> ------------[ cut here ]------------
> WARNING: at lib/list_debug.c:30 __list_add+0x68/0x81()
> Hardware name: System Product Name
> list_add corruption. prev->next should be next (ffff8801e7d9dda0), but was 
> ffff88017ea4f730. (prev=ffff88017ea4f730).
> Modules linked in: nls_utf8 xt_physdev ppdev ip6table_filter ip6_tables 
> ipt_MASQUERADE iptable_nat nf_nat ipv6 snd_hda_codec_atihdmi 
> snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_pcm_oss snd_hwdep 
> snd_mixer_oss snd_seq_dummy snd_pcm snd_seq_oss snd_seq_midi snd_rawmidi 
> snd_seq_midi_event radeon snd_seq snd_timer ttm drm_kms_helper snd_seq_device 
> drm i2c_algo_bit snd soundcore snd_page_alloc lp asus_atk0110 parport 
> ata_generic pata_acpi pata_jmicron r8169 mii floppy
> Pid: 3813, comm: Xorg Not tainted 2.6.32.19-xen #3
> Call Trace:
>  [<ffffffff81054f3e>] warn_slowpath_common+0x77/0x8f
>  [<ffffffff81054fa3>] warn_slowpath_fmt+0x3c/0x3e
>  [<ffffffffa0093021>] ? ttm_buffer_object_init+0x333/0x35c [ttm]
>  [<ffffffff8121b817>] __list_add+0x68/0x81
>  [<ffffffffa00d69e7>] radeon_object_create+0x1cd/0x1e2 [radeon]
>  [<ffffffffa00d67d2>] ? radeon_ttm_object_object_destroy+0x0/0x48 [radeon]
>  [<ffffffffa00e0bc6>] radeon_gem_object_create+0x8b/0xf9 [radeon]
>  [<ffffffff810449ef>] ? __wake_up+0x3f/0x48
>  [<ffffffffa00e0c34>] ? radeon_gem_create_ioctl+0x0/0xda [radeon]
>  [<ffffffffa00e0c89>] radeon_gem_create_ioctl+0x55/0xda [radeon]
>  [<ffffffff811d6339>] ? avc_has_perm+0x57/0x69
>  [<ffffffffa005d0c7>] drm_ioctl+0x232/0x2ef [drm]
>  [<ffffffff8100fab9>] ? __spin_time_accum+0x21/0x37
>  [<ffffffff8100fd19>] ? __xen_spin_lock+0xb7/0xcd
>  [<ffffffff8111859c>] vfs_ioctl+0x6a/0x82
>  [<ffffffff81118aa8>] do_vfs_ioctl+0x47d/0x4c3
>  [<ffffffff81118b3f>] sys_ioctl+0x51/0x74
>  [<ffffffff8110a4d7>] ? sys_read+0x5c/0x69
>  [<ffffffff81012b42>] system_call_fastpath+0x16/0x1b
> ---[ end trace 5cb030d3ba77eb47 ]---
> ------------[ cut here ]------------
> WARNING: at lib/list_debug.c:30 __list_add+0x68/0x81()
> Hardware name: System Product Name
> list_add corruption. prev->next should be next (ffff8801e7d9dda0), but was 
> ffff88017ea49330. (prev=ffff88017ea4f730).
> Modules linked in: nls_utf8 xt_physdev ppdev ip6table_filter ip6_tables 
> ipt_MASQUERADE iptable_nat nf_nat ipv6 snd_hda_codec_atihdmi 
> snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_pcm_oss snd_hwdep 
> snd_mixer_oss snd_seq_dummy snd_pcm snd_seq_oss snd_seq_midi snd_rawmidi 
> snd_seq_midi_event radeon snd_seq snd_timer ttm drm_kms_helper snd_seq_device 
> drm i2c_algo_bit snd soundcore snd_page_alloc lp asus_atk0110 parport 
> ata_generic pata_acpi pata_jmicron r8169 mii floppy
> Pid: 3813, comm: Xorg Tainted: G        W  2.6.32.19-xen #3
> Call Trace:
>  [<ffffffff81054f3e>] warn_slowpath_common+0x77/0x8f
>  [<ffffffff81054fa3>] warn_slowpath_fmt+0x3c/0x3e
>  [<ffffffffa0093021>] ? ttm_buffer_object_init+0x333/0x35c [ttm]
>  [<ffffffff8121b817>] __list_add+0x68/0x81
>  [<ffffffffa00d69e7>] radeon_object_create+0x1cd/0x1e2 [radeon]
>  [<ffffffffa00d67d2>] ? radeon_ttm_object_object_destroy+0x0/0x48 [radeon]
>  [<ffffffffa00e0bc6>] radeon_gem_object_create+0x8b/0xf9 [radeon]
>  [<ffffffff810449ef>] ? __wake_up+0x3f/0x48
>  [<ffffffffa00e0c34>] ? radeon_gem_create_ioctl+0x0/0xda [radeon]
>  [<ffffffffa00e0c89>] radeon_gem_create_ioctl+0x55/0xda [radeon]
>  [<ffffffff811d6339>] ? avc_has_perm+0x57/0x69
>  [<ffffffffa005d0c7>] drm_ioctl+0x232/0x2ef [drm]
>  [<ffffffff8100fab9>] ? __spin_time_accum+0x21/0x37
>  [<ffffffff8100fd19>] ? __xen_spin_lock+0xb7/0xcd
>  [<ffffffff8111859c>] vfs_ioctl+0x6a/0x82
>  [<ffffffff81118aa8>] do_vfs_ioctl+0x47d/0x4c3
>  [<ffffffff8100f10f>] ? xen_restore_fl_direct_end+0x0/0x1
>  [<ffffffff81118b3f>] sys_ioctl+0x51/0x74
>  [<ffffffff81464c20>] ? do_device_not_available+0x9/0xb
>  [<ffffffff81012b42>] system_call_fastpath+0x16/0x1b
> ---[ end trace 5cb030d3ba77eb48 ]---
> ------------[ cut here ]------------
> WARNING: at lib/list_debug.c:30 __list_add+0x68/0x81()
> Hardware name: System Product Name
> list_add corruption. prev->next should be next (ffff8801e7d9dda0), but was 
> ffff88017ea49330.
> 
> 
> 
> --- On Tue, 8/17/10, Boris Derzhavets <bderzhavets@xxxxxxxxx> wrote:
> 
> From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
> Subject: Re: [Xen-devel] [GIT PULL] devel/pat + devel/kms.fixes-0.5 on RV730 
> PRO [Radeon HD 4650]
> To: "Konrad Rzeszutek Wilk" <konrad.wilk@xxxxxxxxxx>
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> Date: Tuesday, August 17, 2010, 10:50 AM
> 
> Seems to be F13/dracut issue in my case.
> 
> Xen 4.0.1-rc6 & 2.6.32.19 ( KMS  enabled) installed on top of Ubuntu 10.04
> with no  problems.
> 
> --- On Tue, 8/17/10, Boris Derzhavets <bderzhavets@xxxxxxxxx> wrote:
> 
> From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
> Subject: Re: [Xen-devel] [GIT PULL] devel/pat + devel/kms.fixes-0.5 on RV730 
> PRO [Radeon HD 4650]
> To: "Konrad Rzeszutek Wilk" <konrad.wilk@xxxxxxxxxx>
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> Date: Tuesday, August 17, 2010, 3:09 AM
> 
> > How about -v? See if the file RV730_pfp.bin gets put in the initramfs
> image.
>  
> 
> I unzipped and uncpio  initramfs :- 
>       file is not there.
> Tried --fware option of dracut. No luck.
> File gets installed in /lib/fmware/radeon folder , but doesn't get
> included in "initramfs"
> 
> 
> > Did you make sure that the CONFIG_DRM_RADEON is set to 'm'?
> It appears to be set to 'y'
> 
> > After that did you recompile the kernel and modules and re-installed them?
> Yes. 
> 
> --- On Mon, 8/16/10, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx> wrote:
> 
> From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
> Subject: Re: [Xen-devel] [GIT PULL] devel/pat + devel/kms.fixes-0.5 on
>  RV730 PRO [Radeon HD 4650]
> To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> Date: Monday, August 16, 2010, 4:05 PM
> 
> On Mon, Aug 16, 2010 at 11:35:24AM -0700, Boris Derzhavets wrote:
> > > Can you provide the serial output? 
> > No
> > 
> > > Is the error the same as you reported
> > before (were it could not load the firmware code?)
> > 
> > Yes. 
> > Xen System loads up so i have dmesg.log  It's attached
> > 
> > > Can you try fiddling with the dracut options to force it include the
> > proper firmware bits?
> > 
> > Which ones ? That is what happens loading Dom0.
> 
> How about -v? See if the file RV730_pfp.bin gets put in the initramfs
> image. Did you make sure that the CONFIG_DRM_RADEON is set to 'm'? After
> that did you recompile the kernel and modules and re-installed them?
> 
> >
>  
> >
>  Dmesg:
> > 
> > [drm] Loading RV730 CP Microcode
> > platform radeon_cp.0: firmware: requesting radeon/RV730_pfp.bin
> > 
> >      Hangs.... for a while.
> > 
> > r600_cp: Failed to load firmware "radeon/RV730_pfp.bin"
> > [drm:rv770_init] *ERROR* Failed to load firmware!
> > [drm:radeon_driver_load_kms] *ERROR* Fatal error while trying to initialize 
> > radeon.
> > radeon 0000:01:00.0: PCI INT A disabled
> > radeon: probe of 0000:01:00.0 failed with error -2
> > 
> > Proceed with normal load.
> 
> You need to figure out why it isn't including that firmware file on the
> initramfs. 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>       
> -----Inline Attachment Follows-----
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
> 
> 
> 
>       
> -----Inline Attachment Follows-----
> 
> _______________________________________________
> 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


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