Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp2354093ybl;
        Thu, 29 Aug 2019 07:10:22 -0700 (PDT)
X-Google-Smtp-Source: APXvYqy6mf6coZ7YasdHTSCAgj10vYw7eOZH/gXjJ96JJzmGnoeDsAOo3pDibbAZtEj5zsvnhiic
X-Received: by 2002:a63:904:: with SMTP id 4mr8063422pgj.397.1567087822462;
        Thu, 29 Aug 2019 07:10:22 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1567087822; cv=none;
        d=google.com; s=arc-20160816;
        b=iPqtWnhDSz64vnEDVdOcH8Oo4wqrNot8zML4glGODMZjRPyYsLTgSHMXhMG7EZcKCu
         9ZKE7ZwcXCNspl2d6vbceSxaNhkbAjs03s+lB+UDsWWlqzZgROfbMIlOM9z2hR56LkfU
         LS33RlYvP1WDoRQLPUY3mRwdyqryIilb4dewZweSr48w9GXLXFHUvJSuxlqPVk1Z02/k
         NA/HEUPM1N7CQDMld1Xi9KY/Ry5eTAOOall/R0TyROqxxLPbtCeTKVcIiS3OKd+kEuEA
         l5afbS7UIet3o+IWbF3w22Si9uJQT7s8TIjuxksJ+Ix5l5a7TwcrgSLFSPP+QozuCvql
         Xnew==
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=dT293HPyj/GFfRbXiQ7miYV2lpHH1pPTBj5mQLoQWnc=;
        b=TBTl/oAfCyPsp03HaYjcKSjtWStRsL6W093poSjEIPvhTyBBP0YFWv8GIolAOghW4j
         dcjpJhenGGR+mEtrknaqIszQA3nhifQwsKz7kiKSKd7S30xUuG8UWIBPDaOD4DTg1A6E
         WE5bGxYzkDOPes0f7ivzqUxRA7tswZ9BYaP0xbN6hm/tDG5md7eH7I2telYaVhpyBqPh
         t2DA9Cd8eULvWv8MH34KFrExGyU1TQnymQcUV8j2dYN9BbYNbleF6LlhqtN9hVC7vMDE
         uOPWssubiEP0i/unJzxF8owG+/D0rxGhpyzc3BiWwW3SpOFJjBVwPpQHSvlQkAO7qrz1
         L3DQ==
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
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67])
        by mx.google.com with ESMTP id q1si2108297pgv.58.2019.08.29.07.10.04;
        Thu, 29 Aug 2019 07:10:22 -0700 (PDT)
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
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1727176AbfH2OIx (ORCPT <rfc822;charleyewang@gmail.com>
        + 99 others); Thu, 29 Aug 2019 10:08:53 -0400
Received: from verein.lst.de ([213.95.11.211]:46554 "EHLO verein.lst.de"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1726518AbfH2OIx (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Thu, 29 Aug 2019 10:08:53 -0400
Received: by verein.lst.de (Postfix, from userid 2407)
        id 04EAF68B20; Thu, 29 Aug 2019 16:08:50 +0200 (CEST)
Date:   Thu, 29 Aug 2019 16:08:49 +0200
From:   Christoph Hellwig <hch@lst.de>
To:     Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>
Cc:     Christoph Hellwig <hch@lst.de>,
        Alan Stern <stern@rowland.harvard.edu>,
        Jens Axboe <axboe@kernel.dk>,
        USB list <linux-usb@vger.kernel.org>,
        linux-block@vger.kernel.org,
        Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: reeze while write on external usb 3.0 hard disk [Bug 204095]
Message-ID: <20190829140849.GA18387@lst.de>
References: <20190817095422.GA4200@lazy.lzy> <Pine.LNX.4.44L0.1908191009490.1506-100000@iolanthe.rowland.org> <20190820072326.GD28968@lst.de> <20190820163722.GA2991@lazy.lzy> <20190826173833.GA4166@lazy.lzy>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20190826173833.GA4166@lazy.lzy>
User-Agent: Mutt/1.5.17 (2007-11-01)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Mon, Aug 26, 2019 at 07:38:33PM +0200, Piergiorgio Sartor wrote:
> any news on this?

Sorry, I've been dropping the ball here, and I'm a little puzzled
on what is going on.  Including on why we are bounce buffering for
xhci at all.  What kind of system (CPU / mainboard) is this?