From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.5 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_2 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 91883C433E6 for ; Mon, 20 Jul 2020 08:51:45 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 7509222B4D for ; Mon, 20 Jul 2020 08:51:45 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728092AbgGTIvo (ORCPT ); Mon, 20 Jul 2020 04:51:44 -0400 Received: from mx2.suse.de ([195.135.220.15]:43350 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727058AbgGTIvo (ORCPT ); Mon, 20 Jul 2020 04:51:44 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id C21ABADC2; Mon, 20 Jul 2020 08:51:49 +0000 (UTC) Message-ID: <1595235102.2531.7.camel@suse.de> Subject: Re: uas: bug: [sda] tag#21 uas_eh_abort_handler 0 uas-tag 6 inflight: IN From: Oliver Neukum To: "Tj (Elloe Linux)" , Greg KH Cc: linux-usb Date: Mon, 20 Jul 2020 10:51:42 +0200 In-Reply-To: References: <9268a7b4-217e-e76d-af9a-9c5b4f6fe54a@elloe.vision> <20200719110901.GE266150@kroah.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.26.6 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-usb-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-usb@vger.kernel.org Am Sonntag, den 19.07.2020, 12:55 +0100 schrieb Tj (Elloe Linux): > On 19/07/2020 12:09, Greg KH wrote: > > On Sun, Jul 19, 2020 at 11:22:10AM +0100, Tj (Elloe Linux) wrote: > > Where is an error here? Those looks ok to me. > > These repeated 'zaps' and resets every 30 seconds or so are not errors? They are errors. But whose errors? 0x28 looks like a READ10 to me. In other words at least Test Unit Ready and READ_CAPACITY have already worked at this stage. Without a trace it is not clear what exactly this read is for. Is it always the same READ? This looks like the error handling UAS does when a command times out. > They never stop even though the devices are not mounted nor being > accessed (by users). > > > > [ 199.939976] blk_update_request: I/O error, dev sda, sector 500117464 > > > op 0x0:(READ) flags 0x80700 phys_seg 5 prio class 0 > > > > So only the block layer is reporting errors, not the USB layer? Any usb > > controller errors? The error is from the SCSI layer strictly speaking. It notices that a command is taking longer than allowed and directs UAS to do error handling. SUbsequently an error is reported up to the block layer. The problem is that we have a lot of unusual stuff being tested. Regards Oliver