From: Bagas Sanjaya <bagasdotme@gmail.com>
To: beld zhang <beldzhang@gmail.com>, stable@vger.kernel.org
Cc: Linux Regressions <regressions@lists.linux.dev>,
Linux USB <linux-usb@vger.kernel.org>,
Linux Input Devices <linux-input@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: Mon, 29 May 2023 09:21:12 +0700 [thread overview]
Message-ID: <ZHQMGN-LAJk6vHjH@debian.me> (raw)
In-Reply-To: <CAG7aomXP0JHmHytsv5cMsyHzee61BQnG3fc-Y+NLzum7H3DyHA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2137 bytes --]
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
Before suspend, is attaching your mouse not crashing your system?
>
> 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
There is a functionality on Bugzilla to attach above files. Use it.
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
parent reply other threads:[~2023-05-29 2:21 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAG7aomXP0JHmHytsv5cMsyHzee61BQnG3fc-Y+NLzum7H3DyHA@mail.gmail.com>]
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=ZHQMGN-LAJk6vHjH@debian.me \
--to=bagasdotme@gmail.com \
--cc=beldzhang@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--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;
as well as URLs for NNTP newsgroup(s).