From: Robert Hancock <hancockrwd@gmail.com>
To: Kasper Sandberg <lkml@metanurb.dk>
Cc: Torsten Kaiser <just.for.lkml@googlemail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
SCSI development list <linux-scsi@vger.kernel.org>
Subject: Re: sata_sil24 0000:04:00.0: DMA-API: device driver frees DMA sg list with different entry count [map count=13] [unmap count=10]
Date: Wed, 03 Jun 2009 17:33:21 -0600 [thread overview]
Message-ID: <4A270841.7070107@gmail.com> (raw)
In-Reply-To: <1244060503.11698.3.camel@localhost>
Kasper Sandberg wrote:
> On Wed, 2009-06-03 at 21:30 +0200, Torsten Kaiser wrote:
>> On Wed, May 27, 2009 at 1:40 AM, Robert Hancock <hancockrwd@gmail.com> wrote:
>>> Torsten Kaiser wrote:
>>>> On upgrading to 2.6.30-rc1 I enable the DMA-Debugging option
>>>> CONFIG_DMA_API_DEBUG=y
>>>> Since then I get the following or similar errors on each boot:
>>> Please retest with a newer -rc, this patch likely fixes it:
>>>
>>> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=5825627c9463581fd9e70f8285685889ae5bb9bb
>>>
>> Still happens with 2.6.30-rc8 (see trace at the end of the email)
>>
> <snip>
>
> Does this actually give you any problems? should I be scared to give .30
> a test?
If Torsten's diagnosis is correct it's a problem with the DMA debugging
code, not an actual driver bug.
next prev parent reply other threads:[~2009-06-03 23:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-26 19:14 sata_sil24 0000:04:00.0: DMA-API: device driver frees DMA sg list with different entry count [map count=13] [unmap count=10] Torsten Kaiser
2009-05-26 23:40 ` Robert Hancock
2009-05-27 2:11 ` Torsten Kaiser
2009-06-03 19:30 ` Torsten Kaiser
2009-06-03 20:21 ` Kasper Sandberg
2009-06-03 23:33 ` Robert Hancock [this message]
2009-06-04 6:00 ` Torsten Kaiser
2009-06-04 0:02 ` FUJITA Tomonori
2009-06-04 6:12 ` Torsten Kaiser
2009-06-04 6:33 ` FUJITA Tomonori
2009-06-04 7:15 ` Boaz Harrosh
2009-06-04 7:44 ` FUJITA Tomonori
2009-06-04 7:53 ` Jens Axboe
2009-06-04 18:07 ` Torsten Kaiser
2009-06-04 22:43 ` FUJITA Tomonori
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=4A270841.7070107@gmail.com \
--to=hancockrwd@gmail.com \
--cc=just.for.lkml@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lkml@metanurb.dk \
/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