linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michal Pecio <michal.pecio@gmail.com>
To: Forest <forestix@gaga.casa>
Cc: Mathias Nyman <mathias.nyman@linux.intel.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Alan Stern <stern@rowland.harvard.edu>,
	Heikki Krogerus <heikki.krogerus@linux.intel.com>,
	Stefan Eichenberger <stefan.eichenberger@toradex.com>,
	Pawel Laszczak <pawell@cadence.com>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	regressions@lists.linux.dev
Subject: Re: [REGRESSION][BISECTED] usb: hub: total system freeze after running adb
Date: Thu, 4 Dec 2025 09:23:59 +0100	[thread overview]
Message-ID: <20251204092359.134635bd.michal.pecio@gmail.com> (raw)
In-Reply-To: <3e4vhklrg4692n7hbh0pnrlhjkva68mk5v@sonic.net>

On Thu, 20 Nov 2025 14:18:00 -0800, Forest wrote:
> On Tue, 18 Nov 2025 10:59:29 +0100, Michal Pecio wrote:
> >How can you know nothing is logged if the machine becomes
> >unresponsive?  
> 
> By watching the output of `stdbuf -o0 dmesg --follow` when it happens.
> 
> Same results in a GUI terminal, a text console, and output redirected
> to a `mount -o sync` non-journaled filesystem. I guess it's possible
> that something *tried* to log a message, but if so, it didn't get
> logged. 

This involves userspace, which stops working in cases like panic or
full lockup of all CPUs. So you may be missing some final messages.

If you have a PS/2 port, connect some keyboard and see if LEDs will
start blinking - this means kernel panic.

More reliable solution for getting logs from a broken system is
serial console. Maybe netconsole would work too, I have never tried.
And it seems it may also be possible to use xHCI debug capability
(but it needs a special cable: A-to-A without Vbus).

You could try CONFIG_DRM_PANIC, but it doesn't work on all GPUs yet
and it will only help if it's a panic.

Regards,
Michal

      reply	other threads:[~2025-12-04  8:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-17 20:18 [REGRESSION][BISECTED] usb: hub: total system freeze after running adb Forest
2025-11-18  9:21 ` Mathias Nyman
2025-11-20 22:04   ` Forest
2025-12-02 18:44     ` Forest
2025-12-03 23:41     ` Mathias Nyman
2025-12-05  1:56       ` Forest
2025-12-05 14:57         ` Mathias Nyman
2025-11-18  9:59 ` Michal Pecio
2025-11-20 22:18   ` Forest
2025-12-04  8:23     ` Michal Pecio [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20251204092359.134635bd.michal.pecio@gmail.com \
    --to=michal.pecio@gmail.com \
    --cc=forestix@gaga.casa \
    --cc=gregkh@linuxfoundation.org \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@linux.intel.com \
    --cc=pawell@cadence.com \
    --cc=regressions@lists.linux.dev \
    --cc=stefan.eichenberger@toradex.com \
    --cc=stern@rowland.harvard.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).