From: Greg KH <gregkh@linuxfoundation.org>
To: beld zhang <beldzhang@gmail.com>
Cc: stable@vger.kernel.org
Subject: Re: Fwd: 6.1.30: thunderbolt: Clear registers properly when auto clear isn't in use cause call trace after resume
Date: Sun, 28 May 2023 20:02:35 +0100 [thread overview]
Message-ID: <2023052822-evaluate-essential-52a3@gregkh> (raw)
In-Reply-To: <CAG7aomXP0JHmHytsv5cMsyHzee61BQnG3fc-Y+NLzum7H3DyHA@mail.gmail.com>
On Sun, May 28, 2023 at 02:35:18PM -0400, beld zhang wrote:
> ---------- Forwarded message ---------
> From: beld zhang
> Date: Sun, May 28, 2023 at 2:07 PM
> Subject: Re: 6.1.30: thunderbolt: Clear registers properly when auto
> clear isn't in use cause call trace after resume
> To: Mario Limonciello
>
> On Sun, May 28, 2023 at 8:55 AM Mario Limonciello
> <mario.limonciello@amd.com> wrote:
> >
> > This is specific resuming from s2idle, doesn't happen at boot?
> >
> > Does it happen with hot-plugging or hot-unplugging a TBT3 or USB4 dock too?
> >
> > In addition to checking mainline, can you please attach a full dmesg to
> > somewhere ephemeral like a kernel bugzilla with thunderbolt.dyndbg='+p'
> > on the kernel command line set?
> >
>
> 6.4-rc4:
> *) test 1~4 was done with usb hub with ethernet plugged-in
> model: UE330, usb 3.0 3-port hub & GIgabit Ether adapter
> a rapoo wireless mouse in one of the ports
> 1) no crash at boot
> until [169.099024]
> 2) no crash after plug an extra usb dock
> from [297.004691]
> 3) no crash after remove it
> from [373.273511]
> 4) crash after suspend/resume: 2 call-stacks
> from [438.356253]
> 5) removed that hub(only ac-power left): NO crash after resume
> from [551.820333]
> 6) plug in the hub(no mouse): NO crash after resume
> from [1250.256607]
> 7) put on mouse: CRASH after resume
> from [1311.400963]
> mouse model: Rapoo Wireless Optical Mouse 1620
>
> sorry I have no idea how to fill a proper bug report at kernel
> bugzilla, hope these shared links work.
> btw I have no TB devices to test.
>
> dmesg:
> https://drive.google.com/file/d/1bUWnV7q2ziM4tdTzmuGiVuvEzaLcdfKm/view?usp=sharing
>
> config:
> https://drive.google.com/file/d/1It75_AV5tOzfkXXBAX5zAiZMoeJAe0Au/view?usp=sharing
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.
</formletter>
next prev parent reply other threads:[~2023-05-28 19:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-27 20:15 6.1.30: thunderbolt: Clear registers properly when auto clear isn't in use cause call trace after resume beld zhang
2023-05-27 23:48 ` Bagas Sanjaya
2023-05-28 12:55 ` Mario Limonciello
[not found] ` <CAG7aomVVJyDpKjpZ=k=+9qKY5+13eFjcGPEWZ0T0+NTNfZWDfA@mail.gmail.com>
2023-05-28 18:35 ` Fwd: " beld zhang
2023-05-28 19:02 ` Greg KH [this message]
2023-05-29 2:16 ` Bagas Sanjaya
2023-05-29 7:26 ` Greg KH
2023-05-29 2:21 ` Bagas Sanjaya
2023-05-29 3:23 ` beld zhang
2023-05-29 11:38 ` Mika Westerberg
2023-05-29 18:40 ` beld zhang
2023-05-30 5:41 ` Mika Westerberg
2023-05-30 4:12 ` Mario Limonciello
2023-05-30 4:27 ` beld zhang
2023-05-30 9:10 ` Bagas Sanjaya
2023-05-30 8:03 ` Mika Westerberg
2023-05-30 14:38 ` beld zhang
2023-05-31 7:41 ` Mika Westerberg
2023-08-31 9:20 ` Linux regression tracking #update (Thorsten Leemhuis)
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=2023052822-evaluate-essential-52a3@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=beldzhang@gmail.com \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox