From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx3.molgen.mpg.de (mx3.molgen.mpg.de [141.14.17.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 7A5431E4AF; Mon, 8 Apr 2024 16:42:49 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=141.14.17.11 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1712594573; cv=none; b=a2vOwy9FzXzrmZLCia9cCSQGQ0byhcciZGhWMZNubBmTi2v+Vaik5l0lc/t9CP9sAplIJR9PedwlsI2ntgaALCt1hdaaNoz5pRPra22zTX7pSRsOuCrf2Rm6L4VZThNZoWNCAlLKUnS34evVhsrMmqTjLpa/zqCfCc4w+EN29l8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1712594573; c=relaxed/simple; bh=3cfCGhGo+1bKCCJHCSF579dUEsohJffhuL/JLhHgU0k=; h=Message-ID:Date:MIME-Version:Subject:From:To:Cc:References: In-Reply-To:Content-Type; b=aiPFCYZiOGy/pB9MxOBNa3dqMN2NX7bRarlWCnOtUKklJXXbBw20pJw2S12B3hytMaN7yon36t+Frp+TgTH4z2/lX6ouFtqvS/5TQd84XXLqarvJw5fNx5NziNua4EWIgzi6xBEGjWINA+8D0hmac4S4nvZDFQg/PzBOQEcODUc= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=molgen.mpg.de; spf=pass smtp.mailfrom=molgen.mpg.de; arc=none smtp.client-ip=141.14.17.11 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=molgen.mpg.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=molgen.mpg.de Received: from [192.168.0.2] (ip5f5af0ad.dynamic.kabel-deutschland.de [95.90.240.173]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: pmenzel) by mx.molgen.mpg.de (Postfix) with ESMTPSA id C980F61E5FE01; Mon, 8 Apr 2024 18:42:33 +0200 (CEST) Message-ID: <913ed06e-56d0-4504-8af5-26ebac291d07@molgen.mpg.de> Date: Mon, 8 Apr 2024 18:42:32 +0200 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: xhci_hcd 0000:00:14.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 1 comp_code 1 From: Paul Menzel To: Mathias Nyman , =?UTF-8?Q?Micha=C5=82_Pecio?= Cc: Mathias Nyman , linux-usb@vger.kernel.org, LKML References: <58bca6f2-797a-4e20-a476-2294309afdd5@molgen.mpg.de> <20240405113247.743e34b2@foxbook> <7090d3af-18ce-40e1-8ac2-bf18152e5c4a@molgen.mpg.de> <20240406183659.3daf4fa0@foxbook> <20240407142542.036fb02f@foxbook> <1f64af9a-0618-a7da-4acc-f043b6580308@linux.intel.com> Content-Language: en-US In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit [one addition] Am 08.04.24 um 18:37 schrieb Paul Menzel: > Dear Mathias, dear Michał, > > > Thank you very much for your assistance. > > > Am 08.04.24 um 09:17 schrieb Mathias Nyman: >> On 7.4.2024 15.25, Michał Pecio wrote: >>> This (and the absence of any earlier errors on the endpoint) looks >>> like the hardware may be confirming a "successful" transfer twice or >>> the driver may be processing one such confirmation twice. >> >> It's also possible this TD/TRB was cancelled due to the disconnect. >> Could be that even if driver removes the TD from the list and cleans >> out the TRB from the ring buffer (turns TRB to no-op) hardware may >> have read ahead and cached the TRB, and process it anyway. >> >>> [   94.088594] usb 1-2: USB disconnect, device number 8 >>> [   94.089370] xhci_hcd 0000:00:14.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 1 comp_code 1 >>> [   94.089403] xhci_hcd 0000:00:14.0: Looking for event-dma 00000001250310f0 trb-start 0000000125031100 trb-end 0000000125031100 seg-start 0000000125031000 seg-end 0000000125031ff0 >>> [   94.089427] xhci_hcd 0000:00:14.0: last xhci_td_cleanup: first_dma 1250310f0 last_dma 1250310f0 status -115 from finish_td >>> >>> (I say "successful" but it really isn't - the device is no longer >>> listening. But there is no delivery confirmation on isochronous OUT >>> endpoints so the xHC doesn't suspect anything.) >>> >>> Could you try again with this updated debug patch to get more info? >> >> Would also be helpful to add xhci dynamic debug and xhci tracing (two >> separate logs). These will show in detail everything that is going on. >> >> Steps: >> >> mount -t debugfs none /sys/kernel/debug >> echo 'module xhci_hcd =p' >/sys/kernel/debug/dynamic_debug/control >> echo 'module usbcore =p' >/sys/kernel/debug/dynamic_debug/control >> echo 81920 > /sys/kernel/debug/tracing/buffer_size_kb >> echo 1 > /sys/kernel/debug/tracing/events/xhci-hcd/enable >> echo 1 > /sys/kernel/debug/tracing/tracing_on >> < Reproduce issue > >> Send output of dmesg >> Send content of /sys/kernel/debug/tracing/trace >> >> please copy the /sys/kernel/debug/tracing/trace file somewhere as soon >> as possible after reproducing the issue. It grows fast. > > For posterity I created Linux Kernel Bugzilla issue #218695 [1], and > attached the files there. Hopefully everything was captured, that you > need. The discussion could continue on this list, but do as it suits you > best. Just to clarify, although there are six error log lines I only plugged and unplugged the USB headset once. > Kind regards, > > Paul > > > [1]: https://bugzilla.kernel.org/show_bug.cgi?id=218695