From: Eugene Shatokhin <eugene.shatokhin@rosalab.ru>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: uhci_hcd: Possible corruption of DMA pool uhci->td_pool
Date: Fri, 13 Dec 2013 12:16:16 +0400 [thread overview]
Message-ID: <52AAC250.7080208@rosalab.ru> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1312111125550.1531-100000@iolanthe.rowland.org>
On 12/11/2013 08:41 PM, Alan Stern wrote:
> On Wed, 11 Dec 2013, Eugene Shatokhin wrote:
>
>> Hi,
>>
>> On ROSA Linux with kernel 3.10.21 with DMA debug options enabled, the
>> kernel sometimes issues a warning about DMA pool corruption (see the log
>> below).
>>
>> That happens sometimes, when the system boots or resumes from
>> hibernation with Samson C01U USB microphone attached.
>>
>> The affected DMA pool is 'uhci->td_pool', uhci_alloc_td() from
>> drivers/usb/host/uhci-hcd.c makes the relevant dma_pool_alloc() calls.
>>
>> Any ideas about how to find what causes this and how to fix it?
>
> This is not an easy sort of thing to track down...
>
>> Here is the relevant part of the system log:
>> ----------------------------
>> [ 22.264332] usb 2-1: new full-speed USB device number 2 using uhci_hcd
>> [ 22.450609] usb 2-1: New USB device found, idVendor=17a0, idProduct=0001
>> [ 22.450626] usb 2-1: New USB device strings: Mfr=1, Product=2,
>> SerialNumber=0
>> [ 22.450639] usb 2-1: Product: Samson C01U
>> [ 22.450649] usb 2-1: Manufacturer: Samson Technologies
>> <...>
>> [ 280.703483] retire_capture_urb: 4494 callbacks suppressed
>> [ 284.961087] uhci_hcd 0000:00:1d.1: dma_pool_alloc uhci_td, efb7b060
>> (corruped)
>> [ 284.961087] 00000000: 00 06 00 00 af 00 00 03 a7 a7 a7 a7 a7 a7 a7 a7
>> ................
>> [ 284.961087] 00000010: a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7
>> ................
>> [ 284.961087] 00000020: a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7
>> ................
>> [ 284.961087] retire_capture_urb: 4343 callbacks suppressed
>> [ 284.961087] uhci_hcd 0000:00:1d.1: dma_pool_alloc uhci_td, efb7b5d0
>> (corruped)
>> [ 284.961087] 00000000: 00 06 00 00 af 00 00 03 a7 a7 a7 a7 a7 a7 a7 a7
>> ................
>> [ 284.961087] 00000010: a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7
>> ................
>> [ 284.961087] 00000020: a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7
>> ................
>> [ 284.961087] cannot submit urb (err = -27)
>> [ 284.961087] cannot submit urb (err = -27)
>> [ 284.961087] cannot submit urb (err = -27)
>> [ 284.961087] cannot submit urb (err = -27)
>> [ 284.961087] cannot submit urb (err = -27)
>> [ 284.961087] cannot submit urb (err = -27)
>> [ 284.961087] cannot submit urb (err = -27)
>> [ 284.961087] cannot submit urb (err = -27)
>> ----------------------------
>>
>> 0xa7 is POOL_POISON_FREED. The memory pages to be allocated from the
>> pool should be filled with such bytes.
>>
>> Each time I observed this problem, the first 8 bytes of the listed
>> memory area were overwritten, with different data each time.
>
> It kind of looks like a hardware bug. Still, it's hard to say.
>
> Can you test the current 3.13-rc kernel? There have been a few recent
> changes in this area that might have an effect.
>
I tested 3.13-rc3 - the problem has not shown up so far.
Regards,
Eugene
--
Eugene Shatokhin, ROSA Laboratory.
www.rosalab.com
prev parent reply other threads:[~2013-12-13 8:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 15:02 uhci_hcd: Possible corruption of DMA pool uhci->td_pool Eugene Shatokhin
2013-12-11 16:41 ` Alan Stern
2013-12-13 8:16 ` Eugene Shatokhin [this message]
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=52AAC250.7080208@rosalab.ru \
--to=eugene.shatokhin@rosalab.ru \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.