public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ryan Xiao (肖水林)" <Ryan.Xiao@mediatek.com>
To: "tj@kernel.org" <tj@kernel.org>,
	"peterz@infradead.org" <peterz@infradead.org>,
	"vschneid@redhat.com" <vschneid@redhat.com>
Cc: "linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	wsd_upstream <wsd_upstream@mediatek.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"Yongjun Luo (罗勇军)" <Yongjun.Luo@mediatek.com>
Subject: Re: BUG: HANG_DETECT waiting for migration_cpu_stop() complete
Date: Mon, 27 Mar 2023 04:05:31 +0000	[thread overview]
Message-ID: <efdff1c19d9cc18fc041d1ccf0fefc684e6d18d8.camel@mediatek.com> (raw)
In-Reply-To: <a578623ecbae88433876381d3b28ec494f479ab3.camel@mediatek.com>

On Wed, 2023-03-22 at 17:37 +0800, ryan xiao wrote:
Hi Sir:
    Do you have any suggestion for this issue?
Thank you

  reply	other threads:[~2023-03-27  4:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-22  9:37 BUG: HANG_DETECT waiting for migration_cpu_stop() complete Ryan Xiao (肖水林)
2023-03-27  4:05 ` Ryan Xiao (肖水林) [this message]
     [not found] <20220907000741.2496-1-hdanton@sina.com>
2022-09-22  5:40 ` Jing-Ting Wu
  -- strict thread matches above, loose matches on Subject: below --
2022-09-05  2:47 Jing-Ting Wu
2022-09-05  6:44 ` Mukesh Ojha
2022-09-05  8:22   ` Jing-Ting Wu
2022-09-06 18:30     ` Tejun Heo
2022-09-06 20:01       ` Waiman Long
2022-09-06 20:40         ` Waiman Long
2022-09-06 20:50           ` Peter Zijlstra
2022-09-06 21:02             ` Waiman Long
2022-09-23 14:20             ` Mukesh Ojha
2022-09-29 15:13               ` Mukesh Ojha

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=efdff1c19d9cc18fc041d1ccf0fefc684e6d18d8.camel@mediatek.com \
    --to=ryan.xiao@mediatek.com \
    --cc=Yongjun.Luo@mediatek.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=peterz@infradead.org \
    --cc=tj@kernel.org \
    --cc=vschneid@redhat.com \
    --cc=wsd_upstream@mediatek.com \
    /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