From: Joerg Roedel <joerg.roedel@amd.com>
To: Sergio Monteiro Basto <sergio@sergiomb.no-ip.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
zambrano@broadcom.com, bugme-daemon@bugzilla.kernel.org,
netdev@vger.kernel.org
Subject: Re: [Bugme-new] [Bug 12969] New: WARNING: at lib/dma-debug.c:539 check_sync+0xe9/0x341() (Not tainted)
Date: Fri, 3 Apr 2009 11:57:54 +0200 [thread overview]
Message-ID: <20090403095754.GB22472@amd.com> (raw)
In-Reply-To: <1238725419.17093.21.camel@segulix>
On Fri, Apr 03, 2009 at 03:23:39AM +0100, Sergio Monteiro Basto wrote:
> > > ------------[ cut here ]------------
> > > WARNING: at lib/dma-debug.c:539 check_sync+0xe9/0x341() (Not tainted)
> > > Hardware name: HP Compaq nx6110 (PY501EA#AB9)
> > > b44 0000:02:0e.0: DMA-API: device driver tries to sync DMA memory it has not
> > > allocated [device address=0x0000000075941040] [size=1566 bytes]
> > > Modules linked in: llc bnep l2cap bluetooth autofs4 lm90 hwmon i2c_i801 sunrpc
> > > ipv6 cpufreq_ondemand acpi_cpufreq uinput snd_intel8x0m snd_intel8x0
> > > snd_ac97_codec snd_seq_dummy ac97_bus snd_seq_oss snd_seq_midi_event snd_seq
> > > snd_seq_device snd_pcm_oss snd_mixer_oss snd_pcm b44 ssb firewire_ohci
> > > snd_timer ipw2200 iTCO_wdt mii firewire_core snd iTCO_vendor_support libipw
> > > yenta_socket crc_itu_t lib80211 rsrc_nonstatic soundcore snd_page_alloc joydev
> > > pcspkr wmi serio_raw ata_generic pata_acpi i915 drm i2c_algo_bit i2c_core video
> > > output [last unloaded: scsi_wait_scan]
> > > Pid: 2418, comm: S58ntpd Not tainted 2.6.29-16.fc10.i686.PAE #1
> > > Call Trace:
> > > [<c04396d1>] warn_slowpath+0x7c/0xbd
> > > [<c0457fe1>] ? register_lock_class+0x17/0x290
> > > [<c0458d61>] ? mark_lock+0x1e/0x349
> > > [<c0556448>] ? _raw_spin_unlock+0x74/0x78
> > > [<c0458d61>] ? mark_lock+0x1e/0x349
> > > [<c055a060>] ? check_sync+0x37/0x341
> > > [<c055a112>] check_sync+0xe9/0x341
> > > [<c0711245>] ? _spin_unlock_irqrestore+0x45/0x55
> > > [<c04592db>] ? trace_hardirqs_on+0xb/0xd
> > > [<c055a4d1>] debug_dma_sync_single_for_device+0x2f/0x39
> > > [<f828f722>] dma_sync_single_for_device+0x4a/0x59 [b44]
> > > [<f828f76f>] ssb_dma_sync_single_for_device+0x3e/0x48 [b44]
> > > [<f8291d1e>] b44_recycle_rx+0x18c/0x196 [b44]
> > > [<f8291f9f>] b44_poll+0x277/0x3c0 [b44]
> > > [<c0687bb9>] net_rx_action+0xa1/0x1ca
> > > [<c043e30a>] __do_softirq+0x9d/0x154
> > > [<c043e413>] do_softirq+0x52/0x7e
> > > [<c043e56f>] irq_exit+0x49/0x77
> > > [<c040b22e>] do_IRQ+0x97/0xad
> > > [<c0409dac>] common_interrupt+0x2c/0x34
> >
> > This would appear to be reporting a bug in b44's DMA API usage.
>
> Hi!, are you saying that could be a bug in new DMA-API ? (if we have
> one)
We don't have a new DMA-API. I wrote a piece of code which checks if drivers
use the DMA-API as expected.
> I don't had problems before with this b44 and laptop is not new.
Most things we check for typically have no impact when there is no hardware
IOMMU. The purpose of this debugging code is to find those bugs even without an
hardware IOMMU in the system.
> With kernel 2.6.29, I am testing KMS on new drm/dri Intel video, I also
> have one big warning with i915 reported on
> Bug 12419 - possible circular locking dependency on i915 dma.
>
> What I would like to know is :
> Could bug 12419 make this warning on b44 ? or could DMA-API make the 2
> warnings ? or the 2 warnings are completed different ? and the
> combinations of this questions :)
It is hard to imagine that these two bugs have something to do with each other.
The bugzilla entry is a warning about a locking problem and the DMA-API
debugging code warns about wrong usage of the DMA-API.
Joerg
--
| Advanced Micro Devices GmbH
Operating | Karl-Hammerschmidt-Str. 34, 85609 Dornach bei München
System |
Research | Geschäftsführer: Jochen Polster, Thomas M. McCoy, Giuliano Meroni
Center | Sitz: Dornach, Gemeinde Aschheim, Landkreis München
| Registergericht München, HRB Nr. 43632
next prev parent reply other threads:[~2009-04-03 10:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-12969-10286@http.bugzilla.kernel.org/>
2009-04-01 23:50 ` [Bugme-new] [Bug 12969] New: WARNING: at lib/dma-debug.c:539 check_sync+0xe9/0x341() (Not tainted) Andrew Morton
2009-04-03 2:23 ` Sergio Monteiro Basto
2009-04-03 9:57 ` Joerg Roedel [this message]
[not found] ` <66E4AD309580E34AA457975F33D2A7473FBC6A35EE@IRVEXCHCCR01.corp.ad.broadcom.com>
2009-04-03 10:01 ` Michael Buesch
2009-04-07 14:31 ` Sergio Monteiro Basto
[not found] ` <20090402114402.a89b956d.akpm@linux-foundation.org>
[not found] ` <66E4AD309580E34AA457975F33D2A7473FBC6A3626@IRVEXCHCCR01.corp.ad.broadcom.com>
2009-04-06 19:52 ` Michael Buesch
2009-04-04 23:49 [Bugme-new, Bug, " David Miller
2009-04-05 10:03 ` Michael Buesch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090403095754.GB22472@amd.com \
--to=joerg.roedel@amd.com \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sergio@sergiomb.no-ip.org \
--cc=zambrano@broadcom.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).