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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id E0C2DC433EF for ; Sat, 7 May 2022 15:39:13 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1385715AbiEGPm6 (ORCPT ); Sat, 7 May 2022 11:42:58 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57374 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1385709AbiEGPm5 (ORCPT ); Sat, 7 May 2022 11:42:57 -0400 Received: from netrider.rowland.org (netrider.rowland.org [192.131.102.5]) by lindbergh.monkeyblade.net (Postfix) with SMTP id D860B27B2C for ; Sat, 7 May 2022 08:39:10 -0700 (PDT) Received: (qmail 74655 invoked by uid 1000); 7 May 2022 11:39:10 -0400 Date: Sat, 7 May 2022 11:39:10 -0400 From: Alan Stern To: James Dutton Cc: USB mailing list Subject: Re: usb disk drive disconnect making readonly Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-usb@vger.kernel.org On Fri, May 06, 2022 at 09:48:58PM +0100, James Dutton wrote: > On Fri, 6 May 2022 at 15:35, Alan Stern wrote: > > > > > > Hi Alan, > > > > > > Here are some log messages. I suspect the storage device is going into > > > some sort of sleep mode, and the kernel does not seem to be able to > > > wake it up again. > > > The device is a USB to NVME adapter. Using the chip: Realtek RTL9210 > > > The log is perfectly normal up until the 2nd line below onwards: > > ... > > > > That log isn't sufficient. > > > > It would be a big help if instead of sending your kernel log file, you send > > the output of the "dmesg" program. And don't send just the part > > starting where the problem begins; we need to see what happened before > > that as well. > > > > In addition, it would help if you enable USB debugging before the > > problem occurs: > > > > echo 'module usbcore =p' >/sys/kernel/debug/dynamic_debug/control > > > > Hi, > > I will try to get some more logs the next time it happens. > dmesg is not available. As the disk has essentially failed at that > point, nothing works (no keyboard input), so the only way I have got > any useful output has been with rsyslog over the network, and then > show the syslog output on that remote machine. You can try booting with a network console and increasing the log level (so that debug messages are sent to the console). Alan Stern