From: Joerg Roedel <joerg.roedel@amd.com>
To: Daniel J Blueman <daniel.blueman@gmail.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [2.6.30-rc1] lockdep false positive in DMA debug API...
Date: Mon, 29 Jun 2009 15:14:40 +0200 [thread overview]
Message-ID: <20090629131440.GN5139@amd.com> (raw)
In-Reply-To: <6278d2220906280405y731f7f2l65472ec5f62dbc83@mail.gmail.com>
On Sun, Jun 28, 2009 at 12:05:17PM +0100, Daniel J Blueman wrote:
> With 2.6.30-rc1, I'm seeing the lockdep validator spinning it's wheels
> [1] (also already seen [2]) on the DMA debug interface, with the
> hashed locks.
If you don't actually mean 2.6.3_1_-rc1 this is a known bug which was
fixed for 2.6.30-final.
Joerg
--
| Advanced Micro Devices GmbH
Operating | Karl-Hammerschmidt-Str. 34, 85609 Dornach bei München
System |
Research | Geschäftsführer: 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-06-29 13:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-28 11:05 [2.6.30-rc1] lockdep false positive in DMA debug API Daniel J Blueman
2009-06-29 13:14 ` Joerg Roedel [this message]
2009-07-05 10:03 ` Daniel J Blueman
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=20090629131440.GN5139@amd.com \
--to=joerg.roedel@amd.com \
--cc=daniel.blueman@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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