From: Lu Baolu <baolu.lu@linux.intel.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Frederik Schwan <frederik.schwan@linux.com>,
David Woodhouse <dwmw2@infradead.org>,
iommu@lists.linux-foundation.org
Subject: Re: Regression iommu/vt-d bounce buffer
Date: Mon, 13 Jan 2020 10:37:10 +0800 [thread overview]
Message-ID: <687b679b-76c7-15b0-1399-098e0afb3267@linux.intel.com> (raw)
In-Reply-To: <20200110162831.GC28359@8bytes.org>
Hi Joerg,
On 1/11/20 12:28 AM, Joerg Roedel wrote:
> Hi Baolu,
>
> any ideas here?
I am looking at this issue.
Best regards,
baolu
>
> On Mon, Jan 06, 2020 at 04:43:05PM +0100, Frederik Schwan wrote:
>> Hello people,
>> since the introduction of the bounce buffer, a regression with TB3 devices has been introduced.
>> USB devices attached to TB3 refuse to work since. Removing the commits that introduced the bounce buffer, fixes the issue.
>>
>> Commits:
>> 3b53034c268d550d9e8522e613a14ab53b8840d8
>> c5a5dc4cbbf4540c1891cdb2b70cf469405ea61f
>> cfb94a372f2d4ee226247447c863f8709863d170
>> e5e04d051979dbd636a99099b7a595093c50a4bc
>>
>>
>> An excerpt of the trace:
>>> [ +0,000005] WARNING: CPU: 10 PID: 0 at drivers/iommu/intel-iommu.c:3916 bounce_unmap_single+0x103/0x110
>>> [...]
>>> [ +0,000001] Call Trace:
>>> [ +0,000002] <IRQ>
>>> [ +0,000003] usb_hcd_unmap_urb_setup_for_dma+0x9f/0xe0
>>> [ +0,000001] usb_hcd_unmap_urb_for_dma+0x1c/0x170
>>> [ +0,000002] __usb_hcd_giveback_urb+0x36/0x120
>>> [ +0,000008] xhci_giveback_urb_in_irq.isra.0+0x72/0x100 [xhci_hcd]
>>> [ +0,000007] xhci_td_cleanup+0x101/0x140 [xhci_hcd]
>>> [ +0,000007] xhci_irq+0xbf0/0x1db0 [xhci_hcd]
>>> [ +0,000005] __handle_irq_event_percpu+0x44/0x1b0
>>> [ +0,000002] handle_irq_event_percpu+0x34/0x80
>>> [ +0,000002] handle_irq_event+0x37/0x54
>>> [ +0,000002] handle_edge_irq+0xae/0x1f0
>>> [ +0,000002] do_IRQ+0x84/0x140
>>> [ +0,000003] common_interrupt+0xf/0xf
>>> [ +0,000001] </IRQ>
>>
>> Dmesg log and further information have been posted here: https://bugzilla.kernel.org/show_bug.cgi?id=205893
>>
>> Cheers,
>> Frederik
>>
>
>
>
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
prev parent reply other threads:[~2020-01-13 2:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-06 15:43 Regression iommu/vt-d bounce buffer Frederik Schwan
2020-01-10 16:28 ` Joerg Roedel
2020-01-13 2:37 ` Lu Baolu [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=687b679b-76c7-15b0-1399-098e0afb3267@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=frederik.schwan@linux.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.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