[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <64bb37e0906032300h5ff0878agf312ba43df2d991@mail.gmail.com>
Date: Thu, 4 Jun 2009 08:00:22 +0200
From: Torsten Kaiser <just.for.lkml@...glemail.com>
To: Kasper Sandberg <lkml@...anurb.dk>
Cc: Robert Hancock <hancockrwd@...il.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
SCSI development list <linux-scsi@...r.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]
On Wed, Jun 3, 2009 at 10:21 PM, Kasper Sandberg <lkml@...anurb.dk> 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@...il.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?
No, other then the warning from this debug code I do not have any problems.
As I'm using Gentoo unstable this is triggered most often when I
install an upgrade to some package.
I would expect, if this really would write wrong data to the harddisk,
I would have already destroyed my system.
So while I think there is a problem somewhere that should be fixed,
I'm still using the .30 kernel for my system.
Torsten
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists