From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: beld zhang <beldzhang@gmail.com>
Cc: stable@vger.kernel.org
Subject: Re: 6.1.30: thunderbolt: Clear registers properly when auto clear isn't in use cause call trace after resume
Date: Tue, 30 May 2023 08:41:26 +0300 [thread overview]
Message-ID: <20230530054126.GA45886@black.fi.intel.com> (raw)
In-Reply-To: <CAG7aomVpsyOktPFNAURYF9o32CnZST=49BPBRDRH2w7raLbQ7g@mail.gmail.com>
Hi,
On Mon, May 29, 2023 at 02:40:26PM -0400, beld zhang wrote:
> both
> # rmmod thunderbolt
> # modprobe thunderbolt
> makes many crash logs on my hardware.
>
> try to patch this to 6.1.30 and 6.4-rc4 but are all failed.
You mean patching fails or the patch does not solve the issue at hand?
I managed to boot my test system today and with the patch I don't see
the issue anymore.
> how about continue this on the kernel bugzilla, and post a patch here
> after it is resolved as Greg said ?
Sure works for me.
next prev parent reply other threads:[~2023-05-30 5:43 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
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 [this message]
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=20230530054126.GA45886@black.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--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;
as well as URLs for NNTP newsgroup(s).