From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 216243] Shutdown successful but machine does not power off
Date: Wed, 20 Jul 2022 15:55:49 +0000 [thread overview]
Message-ID: <bug-216243-208809-mL7kxRmIiz@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216243-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216243
--- Comment #2 from bminaker@uwindsor.ca ---
Sure, I will try, but one question first: once dynamic debug is enabled, and I
get the log, how do I disable it? Is it reset at reboot?
________________________________
From: bugzilla-daemon@kernel.org <bugzilla-daemon@kernel.org>
Sent: Wednesday, July 20, 2022 4:24:45 AM
To: Bruce Minaker <bminaker@uwindsor.ca>
Subject: [Bug 216243] Shutdown successful but machine does not power off
https://bugzilla.kernel.org/show_bug.cgi?id=216243
joey.corleone@mail.ru changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |joey.corleone@mail.ru
--- Comment #1 from joey.corleone@mail.ru ---
Would you mind sharing a new log with xhci dynamic debug enabled as is
described here [1]?
Enable the debug output first, then try to reproduce the issue, and finally
collect the log file.
[1]
https://lore.kernel.org/linux-usb/9d54d0e4-d2db-3896-301e-9d9048599092@linux.intel.com/T/#m011e17c6eedcf0e8fafbedf60caed1c2e8c7579f
--
You may reply to this email to add a comment.
You are receiving this mail because:
You reported the bug.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2022-07-20 15:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 20:56 [Bug 216243] New: Shutdown successful but machine does not power off bugzilla-daemon
2022-07-20 8:24 ` [Bug 216243] " bugzilla-daemon
2022-07-20 15:55 ` bugzilla-daemon [this message]
2022-07-20 17:29 ` bugzilla-daemon
2022-07-20 17:37 ` bugzilla-daemon
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=bug-216243-208809-mL7kxRmIiz@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-usb@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.