From: "Michał Pecio" <michal.pecio@gmail.com>
To: 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 21:48:27 +0200 [thread overview]
Message-ID: <20241003214827.4edb8731@foxbook> (raw)
In-Reply-To: <467722db-188f-4487-a837-01e65e194d3b@amd.com>
> It hangs after some messages.
What are those messages?
> I sprinkled printks but don't see any on the console.
Did you use loglevel=3 on the kernel command line? No surprise then,
unless you turn all messages you care about into 'printk(KERN_ERR ...)'
or 'dev_err(...)'.
I would also recommend increasing loglevel to 4 (permanently), because
KERN_WARN is rare and usually tells you about pathological conditions.
The 'quiet' option is an alias for that and used to be a quite popular
default in distributions.
Regards,
Michal
next prev parent reply other threads:[~2024-10-03 19:48 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 [this message]
2024-10-03 20:43 ` Harry Wentland
2024-10-03 21:42 ` Michał Pecio
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=20241003214827.4edb8731@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