From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754895Ab1HZQUT (ORCPT ); Fri, 26 Aug 2011 12:20:19 -0400 Received: from caramon.arm.linux.org.uk ([78.32.30.218]:55835 "EHLO caramon.arm.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754724Ab1HZQUP (ORCPT ); Fri, 26 Aug 2011 12:20:15 -0400 Date: Fri, 26 Aug 2011 17:19:51 +0100 From: Russell King - ARM Linux To: Per Forlin , linux-omap@vger.kernel.org Cc: linaro-dev@lists.linaro.org, Nicolas Pitre , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org, Venkatraman S , Linus Walleij , Kyungmin Park , Arnd Bergmann , Sourav Poddar , Chris Ball Subject: Re: [PATCH v9 00/12] use nonblock mmc requests to minimize latency Message-ID: <20110826161951.GA26197@n2100.arm.linux.org.uk> References: <1309539333-2606-1-git-send-email-per.forlin@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1309539333-2606-1-git-send-email-per.forlin@linaro.org> User-Agent: Mutt/1.5.19 (2009-01-05) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org I'm not sure who's responsible for this, but the nonblocking MMC stuff is broken on OMAPs HSMMC: mmcblk0: error -84 transferring data, sector 149201, nr 64, cmd response 0x900, card status 0xb00 mmcblk0: retrying using single block read ------------[ cut here ]------------ WARNING: at /home/rmk/git/linux-2.6-rmk/lib/dma-debug.c:811 check_unmap+0x1ac/0x764() omap_hsmmc omap_hsmmc.0: DMA-API: device driver tries to free DMA memory it has not allocated [device address=0x0000000080933000] [size=20480 bytes] Modules linked in: Backtrace: [] (dump_backtrace+0x0/0x10c) from [] (dump_stack+0x18/0x1c) r7:c1abfcb8 r6:c0186248 r5:c037de51 r4:0000032b [] (dump_stack+0x0/0x1c) from [] (warn_slowpath_common+0x58/0x70) [] (warn_slowpath_common+0x0/0x70) from [] (warn_slowpath_fmt+0x38/0x40) r8:c1abfd50 r7:00000000 r6:00005000 r5:00000000 r4:80933000 [] (warn_slowpath_fmt+0x0/0x40) from [] (check_unmap+0x1ac/0x764) r3:c0367d55 r2:c037e24d [] (check_unmap+0x0/0x764) from [] (debug_dma_unmap_sg+0x100/0x134) [] (debug_dma_unmap_sg+0x0/0x134) from [] (dma_unmap_sg+0x24/0x7c) [] (dma_unmap_sg+0x0/0x7c) from [] (omap_hsmmc_post_req+0x48/0x54) [] (omap_hsmmc_post_req+0x0/0x54) from [] (mmc_start_req+0x9c/0x128) r4:c1a76000 [] (mmc_start_req+0x0/0x128) from [] (mmc_blk_issue_rw_rq+0x80/0x460) r8:c1ab5c00 r7:00000001 r6:c1ab5824 r5:c1ab5824 r4:c1ab5c00 [] (mmc_blk_issue_rw_rq+0x0/0x460) from [] (mmc_blk_issue_rq+0x2cc/0x2fc) [] (mmc_blk_issue_rq+0x0/0x2fc) from [] (mmc_queue_thread+0xa0/0x104) [] (mmc_queue_thread+0x0/0x104) from [] (kthread+0x88/0x90) [] (kthread+0x0/0x90) from [] (do_exit+0x0/0x618) r7:00000013 r6:c003d9a4 r5:c0054f04 r4:c1a7bc7c ---[ end trace 3314ad56daf5d14f ]--- Luckily thinks continue to work, but clearly releasing DMA mappings which drivers don't own is bad news. Unfortunately, I don't have the bandwidth to be able to investigate this at present - well, I could do but then I'd have to drop working on the OMAP4 vs generic suspend/resume code and learn about something I've no current clue about. Can someone please investigate and fix whatever is broken.