linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michał Pecio" <michal.pecio@gmail.com>
To: Harry Wentland <harry.wentland@amd.com>
Cc: Raju.Rangoju@amd.com, Sanath.S@amd.com,
	gregkh@linuxfoundation.org, linux-usb@vger.kernel.org,
	mario.limonciello@amd.com, mathias.nyman@linux.intel.com,
	mika.westerberg@linux.intel.com, regressions@lists.linux.dev
Subject: Re: [REGRESSION] usb: acpi: add device link between tunneled USB3 device and USB4 Host Interface
Date: Thu, 3 Oct 2024 23:42:57 +0200	[thread overview]
Message-ID: <20241003234257.7e87b675@foxbook> (raw)
In-Reply-To: <82aa97b6-4b3a-48d3-a022-04563eb01e45@amd.com>

> No 'quiet' option and with loglevel at 4 I still don't seem to see
> any prints.
What's the loglevel of your printks? If they are INFO, NOTICE or DEBUG
they will not appear on loglevel 4. In particular, the patch you are
testing added a dev_info, which is INFO and will not show on level 4.
I would simply change it to dev_err, then it should show.

> Interestingly if I set loglevel to 6 my boot gets much farther but
> then gets stuck at "A start job is running for Load Kernel Modules
> with ever increasing timeout values".
So the kernel isn't crashing, but probably some module gets stuck on
initialization and 'modprobe' never completes.

Not sure if it really gets much further or simply prints more noise?

If Magic SysRq doesn't work, maybe systemd simply disabled it? It does
so by default, unless overriden by custom config files. It looks like
your root FS gets mounted, so those configs may work.

You could also try blacklisting xhci_pci. I don't know what sort of
kernel config you are using, but on Arch Linux xhci_hcd is built-in so
your blacklisting attempt failed, but xhci_pci is a loadable module.

If this helps, then the next logical step is to 'modprobe xhci_pci'
while running 'dmesg -w' and see what happens.

Regards,
Michal

  reply	other threads:[~2024-10-03 21:43 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-02 17:42 [REGRESSION] usb: acpi: add device link between tunneled USB3 device and USB4 Host Interface Harry Wentland
2024-10-02 19:39 ` Mario Limonciello
2024-10-03  5:47 ` Mika Westerberg
2024-10-03 13:10   ` Mario Limonciello
2024-10-03 13:27     ` Mika Westerberg
2024-10-03 13:42       ` Mario Limonciello
2024-10-03 13:47         ` Mika Westerberg
2024-10-03 18:23           ` Harry Wentland
2024-10-03 18:51             ` Harry Wentland
2024-10-03 19:09               ` Mario Limonciello
2024-10-03 19:41                 ` Harry Wentland
2024-10-04  6:20                   ` Mika Westerberg
2024-10-03 19:48               ` Michał Pecio
2024-10-03 20:43                 ` Harry Wentland
2024-10-03 21:42                   ` Michał Pecio [this message]
2024-10-09 21:52           ` Mathias Nyman
2024-10-10  2:23             ` Mario Limonciello
2024-10-10 12:01               ` Mathias Nyman
2024-10-16 19:48                 ` Harry Wentland
2024-10-21 10:56                   ` Mathias Nyman
2024-10-22 12:33                     ` Mathias Nyman

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=20241003234257.7e87b675@foxbook \
    --to=michal.pecio@gmail.com \
    --cc=Raju.Rangoju@amd.com \
    --cc=Sanath.S@amd.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=harry.wentland@amd.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=mathias.nyman@linux.intel.com \
    --cc=mika.westerberg@linux.intel.com \
    --cc=regressions@lists.linux.dev \
    /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).