linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: Mathew George <mathewegeorge@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	Bernie Huang <phhuang@realtek.com>,
	"kvalo@kernel.org" <kvalo@kernel.org>,
	"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: RE: [REGRESSION] Freeze on resume from S3 (bisected)
Date: Thu, 20 Jun 2024 09:33:41 +0000	[thread overview]
Message-ID: <342b6b95d97a4bf09afee15c09481efc@realtek.com> (raw)
In-Reply-To: <E3FF7BC1-725B-40E2-AAF0-CA41A44B9DF9@gmail.com>

Mathew George <mathewegeorge@gmail.com> wrote:
> > Please share Arch Linux image you are using.
> 
> Not sure what you mean by 'image'. 

I feel this problem may be easier to reproduce on Arch Linux, so I would like
to know Arch Linux iso file you installed. 

> As you can see in the crash log attached to my
> previous mail, I built the latest mainline kernel (445e60303883 at the time) with your
> patch applied. I used [this PKGBUILD](https://aur.archlinux.org/packages/linux-git)
> to build it; the file `config` contains the kernel configuration (I did not apply any other
> options), and there are no patches applied except yours.

I will do it as your side. 

> 
> > Could you please help to collect 2 or more crash log?
> > So I can check if there are
> > more than one crash cases.
> 
> When I am back at my system, I will reproduce the issue a few more times with
> this kernel, and attach the logs. In the meantime, you could have a look at the logs
> linked in my first mail. There are logs for most of the bad commits encountered in the
> bisection.

I have seen that, but no clear idea for now, so I will install Arch Linux as yours
in my side.




  reply	other threads:[~2024-06-20  9:33 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-19  4:39 [REGRESSION] Freeze on resume from S3 (bisected) Forty Five
2024-06-19  6:07 ` Ping-Ke Shih
2024-06-19 14:46   ` Forty Five
2024-06-20  8:16     ` Ping-Ke Shih
2024-06-20  8:56       ` Kalle Valo
2024-06-20  9:06         ` Ping-Ke Shih
2024-06-20  9:18       ` Mathew George
2024-06-20  9:33         ` Ping-Ke Shih [this message]
2024-06-20 10:05           ` Mathew George
2024-06-20 11:41             ` Ping-Ke Shih
2024-06-20 11:58               ` Johannes Berg
2024-06-20 13:05               ` Forty Five
2024-06-20 13:41         ` Forty Five
2024-06-28  3:55           ` Ping-Ke Shih
  -- strict thread matches above, loose matches on Subject: below --
2024-06-30 19:11 Forty Five
2024-07-03  7:39 ` Ping-Ke Shih
     [not found] <875xtqjli4.fsf@gmail.com>
2024-06-30 19:20 ` Forty Five
2024-07-01  2:46   ` Ping-Ke Shih
2024-07-01  5:36   ` Ping-Ke Shih
2024-07-01  6:15 Forty Five
2024-07-08 15:55 Forty Five
     [not found] <draft-87msmrdgkb.fsf@gmail.com>
2024-07-08 16:30 ` Forty Five
2024-07-09  1:26   ` Ping-Ke Shih
2024-07-09  4:10     ` Forty Five
2024-07-09  4:25       ` Ping-Ke Shih
2024-07-09 11:49         ` Forty Five
2024-07-11  7:54     ` Forty Five
2024-07-12  0:59       ` Ping-Ke Shih

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=342b6b95d97a4bf09afee15c09481efc@realtek.com \
    --to=pkshih@realtek.com \
    --cc=kvalo@kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mathewegeorge@gmail.com \
    --cc=phhuang@realtek.com \
    --cc=regressions@lists.linux.dev \
    /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).