From: Forty Five <mathewegeorge@gmail.com>
To: Ping-Ke Shih <pkshih@realtek.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, 11 Jul 2024 13:24:16 +0530 [thread overview]
Message-ID: <87jzhs9xef.fsf@gmail.com> (raw)
In-Reply-To: <6673a2dc01a941f5900da7393d160005@realtek.com>
[-- Attachment #1: Type: text/plain, Size: 3470 bytes --]
Ping-Ke Shih <pkshih@realtek.com> writes:
> Right. Only apply [1] in every bisection step.
>
> Thanks for the exp #1 and #2. The results are in expectation. Then the new
> bisection will find out another problem.
Here are the bisection results:
git bisect start
# status: waiting for both good and bad commits
# bad: [5bbd9b249880dba032bffa002dd9cd12cd5af09c] Merge tag 'v6.10-p4' of git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6
git bisect bad 5bbd9b249880dba032bffa002dd9cd12cd5af09c
# good: [bcbefbd032df6bfe925e6afeca82eb9d2cc0cb23] wifi: rtw89: add wait/completion for abort scan
git bisect good bcbefbd032df6bfe925e6afeca82eb9d2cc0cb23
# bad: [480e035fc4c714fb5536e64ab9db04fedc89e910] Merge tag 'drm-next-2024-03-13' of https://gitlab.freedesktop.org/drm/kernel
git bisect bad 480e035fc4c714fb5536e64ab9db04fedc89e910
# good: [57f22c8dab6b266ae36b89b073a4a33dea71e762] Merge tag 'strlcpy-removal-v6.8-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux
git bisect good 57f22c8dab6b266ae36b89b073a4a33dea71e762
# good: [43a7548e28a6df12a6170421d9d016c576010baa] Merge tag 'for-6.9-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux
git bisect good 43a7548e28a6df12a6170421d9d016c576010baa
# bad: [8c9c2f851b5a58195ed7ebd67d7c59683d1a02bc] Merge tag 'iommu-updates-v6.9' of git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu
git bisect bad 8c9c2f851b5a58195ed7ebd67d7c59683d1a02bc
# good: [b38061fe9cfa90a781e9e59fc761191fc8b469a1] net: phy: simplify genphy_c45_ethtool_set_eee
git bisect good b38061fe9cfa90a781e9e59fc761191fc8b469a1
# bad: [75c2946db360e625f1447a37f47dbbb38b1dd478] Merge tag 'wireless-next-2024-03-08' of git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next
git bisect bad 75c2946db360e625f1447a37f47dbbb38b1dd478
# good: [d35c9659e56edd9e629b54da8ceca062517d3d6c] Merge branch 'net-gro-cleanups-and-fast-path-refinement'
git bisect good d35c9659e56edd9e629b54da8ceca062517d3d6c
# good: [e8bb2ccff7216d520a7bc33c22484dafebe8147e] Merge branch 'net-group-together-hot-data'
git bisect good e8bb2ccff7216d520a7bc33c22484dafebe8147e
# bad: [85977fc0aa489420709779cbc859966db94be68f] wifi: mac80211: remove TDLS peers only on affected link
git bisect bad 85977fc0aa489420709779cbc859966db94be68f
# good: [c2b22e26755c77299e1dffa2e17374cd28f7f3a7] wifi: mt76: mt7921: fix the unfinished command of regd_notifier before suspend
git bisect good c2b22e26755c77299e1dffa2e17374cd28f7f3a7
# good: [9ad7974856926129f190ffbe3beea78460b3b7cc] wifi: cfg80211: check A-MSDU format more carefully
git bisect good 9ad7974856926129f190ffbe3beea78460b3b7cc
# bad: [68f6c6afbcebdc3acdc6084abfe453f4cba6b9dc] wifi: mac80211: add ieee80211_vif_link_active() helper
git bisect bad 68f6c6afbcebdc3acdc6084abfe453f4cba6b9dc
# bad: [b2edc721716f44e2a7e46eb592321960a1227c7b] wifi: cfg80211: print flags in tracing in hex
git bisect bad b2edc721716f44e2a7e46eb592321960a1227c7b
# bad: [5fcc7c51f9e72d1e62991f8b32be4a5adf44d556] wifi: mac80211: handle netif carrier up/down with link AP during MLO
git bisect bad 5fcc7c51f9e72d1e62991f8b32be4a5adf44d556
# bad: [1c0d21c4b33a41be9090e73f8225813d72ac88d9] wifi: mac80211: remove only link keys during stopping link AP
git bisect bad 1c0d21c4b33a41be9090e73f8225813d72ac88d9
# first bad commit: [1c0d21c4b33a41be9090e73f8225813d72ac88d9] wifi: mac80211: remove only link keys during stopping link AP
And here are crash logs for all the bad commits:
[-- Attachment #2: kdumpst-202407090344.zip --]
[-- Type: application/zip, Size: 33740 bytes --]
[-- Attachment #3: kdumpst-202407091142.zip --]
[-- Type: application/zip, Size: 34769 bytes --]
[-- Attachment #4: kdumpst-202407091506.zip --]
[-- Type: application/zip, Size: 33505 bytes --]
[-- Attachment #5: kdumpst-202407100543.zip --]
[-- Type: application/zip, Size: 35016 bytes --]
[-- Attachment #6: kdumpst-202407101146.zip --]
[-- Type: application/zip, Size: 34688 bytes --]
[-- Attachment #7: kdumpst-202407101230.zip --]
[-- Type: application/zip, Size: 36019 bytes --]
[-- Attachment #8: kdumpst-202407101301.zip --]
[-- Type: application/zip, Size: 33660 bytes --]
[-- Attachment #9: kdumpst-202407101338.zip --]
[-- Type: application/zip, Size: 34355 bytes --]
next prev parent reply other threads:[~2024-07-11 7:54 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <draft-87msmrdgkb.fsf@gmail.com>
2024-07-08 16:30 ` [REGRESSION] Freeze on resume from S3 (bisected) 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 [this message]
2024-07-12 0:59 ` Ping-Ke Shih
2024-07-08 15:55 Forty Five
-- strict thread matches above, loose matches on Subject: below --
2024-07-01 6:15 Forty Five
[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-06-30 19:11 Forty Five
2024-07-03 7:39 ` Ping-Ke Shih
2024-06-19 4:39 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
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
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=87jzhs9xef.fsf@gmail.com \
--to=mathewegeorge@gmail.com \
--cc=kvalo@kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=phhuang@realtek.com \
--cc=pkshih@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).