[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bug#989778: Regression in at least 5.10.y and mainline: Firewire audio interface fails to work properly (when booted under Xen)
- To: Salvatore Bonaccorso <carnil@xxxxxxxxxx>
- From: 小太 <nospam@xxxxxxxx>
- Date: Sun, 27 Jun 2021 04:17:03 +1000
- Cc: Robin Murphy <robin.murphy@xxxxxxx>, 989778-maintonly@xxxxxxxxxxxxxxx, Jianxiong Gao <jxgao@xxxxxxxxxx>, Christoph Hellwig <hch@xxxxxx>, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, iommu@xxxxxxxxxxxxxxxxxxxxxxxxxx, Marek Szyprowski <m.szyprowski@xxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxx
- Delivery-date: Sat, 26 Jun 2021 18:18:11 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
Hi Robin,
On Mon, Jun 14, 2021 at 02:29:08PM +0100, Robin Murphy wrote:
> On 2021-06-13 07:29, Salvatore Bonaccorso wrote:
> > A user in Debian reported the above issue, which was reproducible with
> > 5.13-rc5 and 5.10.y as packaged in Debian and found that 85a5a6875ca9
> > ("swiotlb: don't modify orig_addr in swiotlb_tbl_sync_single") that
> > introduced the issue.
>
> Sounds like it's probably the same thing as being discussed over here:
>
> https://lore.kernel.org/linux-iommu/2e899de2-4b69-c4b6-33a6-09fb8949d2fd@xxxxxxx/
Thanks for the pointer, it seems that now it has been fixed upstream
with 5f89468e2f06 ("swiotlb: manipulate orig_addr when tlb_addr has
offset").
I've checked out upstream v5.13 b7050b242430f3170e0b57f5f55136e44cb8dc66 (which includes the above commit) and confirmed that my issue is now resolved.
Now to wait for it to reach Debian :)
|
