All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 221073] xHCI host controller dies on resume from s2idle on AMD Strix Halo [1022:1587]
Date: Mon, 13 Jul 2026 06:00:47 +0000	[thread overview]
Message-ID: <bug-221073-208809-WqKbN4DLCR@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221073-208809@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=221073

--- Comment #53 from Alexander F (superveridical@gmail.com) ---
Created attachment 310441
  --> https://bugzilla.kernel.org/attachment.cgi?id=310441&action=edit
Power dependency patch attempt klog

For reasons that are unknown to me, the flags variable here

2572    if (flags & AMD_IS_APU)
2573            amdgpu_setup_apu_usb_power_dep(adev);

doesn't have the appropriate bits set, so the code doesn't get executed at all.

To discover this I instrumented the code with the two pirintks, one just before
the if with the dump of the flags, one inside the function before the while
loop.

2379         printk(KERN_INFO "OLOLOLOLOLOLOL 2\n");

2561         unsigned long testt = AMD_IS_APU;
2562
2563         printk(KERN_INFO "LALALALALALALA 1 flags:%*pbl AMD_IS_APU: %*pbl
\n", 64, &flags, 64, &testt);

The flags are indeed different:

Jul 13 08:29:36 rescue-flow kernel: LALALALALALALA 1 flags:2,5 AMD_IS_APU: 17 

Then I commented the offending if out, the second printk appeared in the logs,
but nothing from the loop got printed.

Just in case I supplied klog with debug turned on.

I reverted the previous patch btw. I'm pretty sure AMD is my APU, and 3d
acceleration works nominally(checked with firefox/shadertoy and amdgpu_top). If
it's some misconfiguration on my part(for example my kernel config), please
provide further instructions.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2026-07-13  6:00 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-10 17:46 [Bug 221073] New: xHCI host controller dies on resume from s2idle on AMD Strix Halo [1022:1587] bugzilla-daemon
2026-02-10 18:04 ` [Bug 221073] " bugzilla-daemon
2026-02-11  6:54 ` bugzilla-daemon
2026-02-11 23:04 ` bugzilla-daemon
2026-02-12  8:27 ` bugzilla-daemon
2026-02-12 10:02 ` bugzilla-daemon
2026-02-12 16:15 ` bugzilla-daemon
2026-02-25 11:10 ` bugzilla-daemon
2026-02-26  8:48 ` bugzilla-daemon
2026-02-26  8:50 ` bugzilla-daemon
2026-02-26  9:30 ` bugzilla-daemon
2026-02-26  9:37 ` bugzilla-daemon
2026-02-26 12:16 ` bugzilla-daemon
2026-02-26 12:18 ` bugzilla-daemon
2026-02-26 22:51 ` bugzilla-daemon
2026-02-27 14:04 ` bugzilla-daemon
2026-03-02 16:45 ` bugzilla-daemon
2026-03-02 18:08 ` bugzilla-daemon
2026-03-02 18:14 ` bugzilla-daemon
2026-03-02 19:05 ` bugzilla-daemon
2026-03-03 14:54 ` bugzilla-daemon
2026-03-03 14:55 ` bugzilla-daemon
2026-03-03 14:55 ` bugzilla-daemon
2026-03-03 14:56 ` bugzilla-daemon
2026-03-03 15:05 ` bugzilla-daemon
2026-03-03 15:47 ` bugzilla-daemon
2026-03-03 15:51 ` bugzilla-daemon
2026-03-03 16:59 ` bugzilla-daemon
2026-03-03 17:05 ` bugzilla-daemon
2026-03-03 22:57 ` bugzilla-daemon
2026-03-04  0:20 ` bugzilla-daemon
2026-03-04  9:15 ` bugzilla-daemon
2026-03-06 11:11 ` bugzilla-daemon
2026-03-06 11:40 ` bugzilla-daemon
2026-03-09 10:31 ` bugzilla-daemon
2026-03-11 22:09 ` bugzilla-daemon
2026-03-12  0:04 ` bugzilla-daemon
2026-03-12  6:49 ` bugzilla-daemon
2026-03-12 10:35 ` bugzilla-daemon
2026-03-14  4:29 ` bugzilla-daemon
2026-03-16  0:39 ` bugzilla-daemon
2026-03-17  0:03 ` bugzilla-daemon
2026-03-18 23:18 ` bugzilla-daemon
2026-05-19  9:14 ` bugzilla-daemon
2026-06-17 15:17 ` bugzilla-daemon
2026-06-17 15:50   ` Alan Stern
2026-06-17 15:50 ` bugzilla-daemon
2026-07-08 15:30 ` bugzilla-daemon
2026-07-09  4:46 ` bugzilla-daemon
2026-07-09  9:53 ` bugzilla-daemon
2026-07-09 11:57 ` bugzilla-daemon
2026-07-12 15:23 ` bugzilla-daemon
2026-07-12 16:02 ` bugzilla-daemon
2026-07-13  3:20 ` bugzilla-daemon
2026-07-13  6:00 ` bugzilla-daemon [this message]
2026-07-13 13:06 ` bugzilla-daemon
2026-07-13 13:08 ` bugzilla-daemon
2026-07-13 18:29 ` bugzilla-daemon
2026-07-13 19:14 ` bugzilla-daemon
2026-07-13 19:15 ` bugzilla-daemon
2026-07-13 19:56 ` bugzilla-daemon
2026-07-13 20:28 ` bugzilla-daemon
2026-07-13 20:30 ` bugzilla-daemon
2026-07-13 21:18 ` bugzilla-daemon
2026-07-13 21:52 ` bugzilla-daemon
2026-07-13 21:54 ` bugzilla-daemon
2026-07-13 22:12 ` bugzilla-daemon
2026-07-14  6:46 ` bugzilla-daemon
2026-07-14 13:04 ` 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-221073-208809-WqKbN4DLCR@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.