WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [GIT PULL] devel/pat + devel/kms.fixes-0.5 / dma-api che

To: Pasi Kärkkäinen <pasik@xxxxxx>
Subject: Re: [Xen-devel] [GIT PULL] devel/pat + devel/kms.fixes-0.5 / dma-api check_unmap() warning
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Mon, 16 Aug 2010 12:31:33 -0400
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 16 Aug 2010 09:33:09 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100815205216.GU2804@xxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20100806140609.GA3367@xxxxxxxxxxxxxxxxxxx> <20100815204125.GS2804@xxxxxxxxxxx> <20100815205216.GU2804@xxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.20 (2009-12-10)
> > Hello,
> > 
> > I just tried the latest 2.6.32.19 kernel from xen/stable-2.6.32.x branch,
> > which now includes the kms.fixes-0.5, on my radeon/supermicro testbox.
> > 
> > .. And KMS modesetting works properly now in Xen dom0! 
> > My onboard ATI Radeon is the following:
> > 
> > # lspci -v | grep VGA
> > 11:04.0 VGA compatible controller: ATI Technologies Inc ES1000 (rev 02) 
> > (prog-if 00 [VGA controller])
> > 
> > It seems also X starts OK, and I can use the Gnome desktop. 
> > I could even run multiple OpenGL 3D applications! (ok, glxgears :)
> > 
> > Thanks, great work!
> > 
> 
> Hmm, actually it seems I got this in dom0 dmesg:

Good. I had seen this a month ago when I upgraded to FC13 (when it was
rawhide) and it disappeared once I upgraded to the real FC13. So I
blamed it on the alpha-rawhide X org driver. I could not reproduce this on
FC13 with an ES1000 in a SuperMicro (some X8DBN+).

So, can you send to me, please:

 - lspci -vvvv
 - cat /var/log/Xorg.0.log
 - rpm -qa
 - dmidecode
 - dmesg
 - xl dmesg

That way I should have enough data to see if I can track this errant
issue down.
> 
> ------------[ cut here ]------------
> WARNING: at lib/dma-debug.c:802 check_unmap+0x18f/0x615()
> Hardware name: X7SB4/E
> NULL NULL: DMA-API: device driver tries to free DMA memory it has not 
> allocated [device address=0x000000002eecc000] [size=4096 bytes]
> Modules linked in: ipt_MASQUERADE iptable_nat nf_nat bridge stp llc sunrpc 
> ip6t_REJECT nf_conntrack_ipv6 ip6table_filter ip6_tables ipv6 xen_gntdev 
> xen_evtchn xenfs uinput e1000e shpchp iTCO_wdt serio_raw i2c_i801 
> iTCO_vendor_support joydev pcspkr floppy usb_storage video aic79xx output 
> scsi_transport_spi radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core [last 
> unloaded: scsi_wait_scan]
> Pid: 15, comm: events/0 Not tainted 2.6.32.19 #1
> Call Trace:
>  [<ffffffff81059e05>] warn_slowpath_common+0x7c/0x94
>  [<ffffffff81059e74>] warn_slowpath_fmt+0x41/0x43
>  [<ffffffff8124d6d5>] ? check_unmap+0x100/0x615
>  [<ffffffff8124a7ab>] ? xen_virt_to_bus+0x11/0x13
>  [<ffffffff8124d764>] check_unmap+0x18f/0x615
>  [<ffffffff8100eca1>] ? xen_force_evtchn_callback+0xd/0xf
>  [<ffffffff8100f3d2>] ? check_events+0x12/0x20
>  [<ffffffff8124dc56>] debug_dma_free_coherent+0x6c/0x7a
>  [<ffffffffa00411d3>] ttm_tt_free_alloced_pages+0x129/0x180 [ttm]
>  [<ffffffffa00415fd>] ttm_tt_destroy+0x4d/0x8f [ttm]
>  [<ffffffffa0041c00>] ttm_bo_release_list+0x96/0xd5 [ttm]
>  [<ffffffffa0041b6a>] ? ttm_bo_release_list+0x0/0xd5 [ttm]
>  [<ffffffff8123cc75>] kref_put+0x43/0x4d
>  [<ffffffffa0042c1d>] ttm_bo_delayed_delete+0xad/0x121 [ttm]
>  [<ffffffffa0042cb0>] ttm_bo_delayed_workqueue+0x1f/0x34 [ttm]
>  [<ffffffff810754a2>] worker_thread+0x257/0x350
>  [<ffffffff8107544a>] ? worker_thread+0x1ff/0x350
>  [<ffffffffa0042c91>] ? ttm_bo_delayed_workqueue+0x0/0x34 [ttm]
>  [<ffffffff81079f26>] ? autoremove_wake_function+0x0/0x39
>  [<ffffffff8107524b>] ? worker_thread+0x0/0x350
>  [<ffffffff81079c54>] kthread+0x7f/0x87
>  [<ffffffff81013dea>] child_rip+0xa/0x20
>  [<ffffffff81013750>] ? restore_args+0x0/0x30
>  [<ffffffff81013de0>] ? child_rip+0x0/0x20
> ---[ end trace 84e813abe3a8bd4d ]---
> fuse init (API version 7.13)
> end_request: I/O error, dev fd0, sector 0
> end_request: I/O error, dev fd0, sector 0
> DMA-API: debugging out of memory - disabling
> 
> 
> The system is up-to-date Fedora 13, with xen/stable-2.6.32.x dom0 kernel.
> 
> Not fatal, things still seem to work..

Is this during shutdown or startup?

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