Received: by 2002:ac0:8845:0:0:0:0:0 with SMTP id g63csp395127img; Thu, 28 Feb 2019 01:05:34 -0800 (PST) X-Google-Smtp-Source: AHgI3IZ7hFxVxaB7+Yts6uGGo3KRu5tIzF4JjSz+SHIS2DYe+feleWZw6WnSCYB3OZH/Q10Yd/xW X-Received: by 2002:a17:902:8d8e:: with SMTP id v14mr6831368plo.133.1551344734367; Thu, 28 Feb 2019 01:05:34 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1551344734; cv=none; d=google.com; s=arc-20160816; b=D53NVWJ3s7JDdeQ7oWFcf7/kNuha81dXoNDTTSm5SjWgX1V8ALUrJ0lnXwKSVE1pj5 zdYRtT/+awF5QCNFrBsRtzcEnS9DpVItvqcRPXPOVurXwtEc9703p+VpqzN6IbsWtG3w k1o/Y4gXXWBEhAsvefbmi7t6uO7UwOU2Izm/JeP9Qx+qEccGPjgROeFeVNxIREixW1ok kv6Khd6XrRjyB7OxJ/mpmyhvIw/yIEy/d4Eiqc7ZQt2XttI/IrjMsrBmAoUVurQtMV9b IEso5raWVjEG56MJZH5Y0sj5bWl7dVX6nQbyVKIGG6Se3FfAgEcicHuHJti6tr5iOoG9 //Tw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=jpcAoGiytIfmoIAPWOgVFTg0b0mgMCu2KAwlI4UxUyQ=; b=hUKPvC+tvprIcvIhvY3vq7/XKnIP5TH1gllqIRQlktEgLV9GU+bNtUhOEvBrWNLDNU jC0PxxyhPBAY0lLE95X8e55ipNs2BFgYhF78/V4FNkDLkpeTHlS7/h1CWX2RqHEM+OhI U0YQMQ1WesUJt6Jb9ms6UTPvLMlrAhSkEwXn6clUKfpBc3kcd+7EhL7un/olFK+l+usj jj2Fz0if5qKiw1HfKqI4xKD3Xobvw5tDCtgvVkNEY6AlUNogi1hOxOoBwxpRZ5JYQc/Q rx2FF1zFxhzQbQKzP9a2KN39N6F8ZLvotT/JpIlN4pTt+leMfaCYPmelHyl8h5C78dqp qz3Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d23si17581902pfm.181.2019.02.28.01.05.17; Thu, 28 Feb 2019 01:05:34 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732069AbfB1JEW (ORCPT + 99 others); Thu, 28 Feb 2019 04:04:22 -0500 Received: from mx1.redhat.com ([209.132.183.28]:60808 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1732054AbfB1JET (ORCPT ); Thu, 28 Feb 2019 04:04:19 -0500 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 334BA8AE40; Thu, 28 Feb 2019 09:04:19 +0000 (UTC) Received: from localhost (unknown [10.40.205.30]) by smtp.corp.redhat.com (Postfix) with ESMTP id 389B161355; Thu, 28 Feb 2019 09:04:13 +0000 (UTC) Date: Thu, 28 Feb 2019 10:04:12 +0100 From: Stanislaw Gruszka To: Joerg Roedel Cc: Lorenzo Bianconi , Rosen Penev , linux-wireless , Samuel Sieb , Alexander Duyck , iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org Subject: Re: MT76x2U crashes XHCI driver on AMD Ryzen system Message-ID: <20190228090411.GA24938@redhat.com> References: <20190114091841.GA23045@localhost.localdomain> <20190115090400.GA2267@localhost.localdomain> <20190218143742.GA11872@redhat.com> <20190226100535.GA20740@8bytes.org> <20190226103450.GA2989@redhat.com> <20190226104413.GH20740@8bytes.org> <20190226112407.GB2989@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190226112407.GB2989@redhat.com> User-Agent: Mutt/1.8.3 (2017-05-23) X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.27]); Thu, 28 Feb 2019 09:04:19 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Feb 26, 2019 at 12:24:08PM +0100, Stanislaw Gruszka wrote: > On Tue, Feb 26, 2019 at 11:44:13AM +0100, Joerg Roedel wrote: > > On Tue, Feb 26, 2019 at 11:34:51AM +0100, Stanislaw Gruszka wrote: > > > On Tue, Feb 26, 2019 at 11:05:36AM +0100, Joerg Roedel wrote: > > > If sg->offset > PAGE_SIZE is fine then most likely we have problem with > > > alignment. > > > > The map_sg implementation in the AMD IOMMU driver uses sg_phys() which > > handles the sg->page + sg->offset calculation fine. > > > > > Note hat issue is with dma_map_sg(), switching to dma_map_single() > > > by using urb->transfer_buffer instead of urb->sg make things work > > > on AMD IOMMU. > > > > On the other hand this points to a bug in the driver, I'll look further > > if I can spot something there. > > I think so too. And I have done some changes that avoid strange allocation > scheme and use usb synchronous messages instead of allocating buffers > with unaligned sizes. However things work ok on Intel IOMMU and > there is no documentation what are dma_map_sg() requirement versus > dma_map_single() which works. I think there are some unwritten > requirements and things can work on some platforms and fails on others > (different IOMMUs, no-IOMMU on some ARCHes) For the record: we have another bug report with this issue: https://bugzilla.kernel.org/show_bug.cgi?id=202673 I provided there patch that change alignment for page_frag_alloc() and it did not fixed the problem. So this is not alignment issue. Now I think it could be page->refcount issue ... Stanislaw