All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Chua <jeff.chua.linux@gmail.com>
To: lkml <linux-kernel@vger.kernel.org>
Cc: Gregory Greenman <gregory.greenman@intel.com>,
	Kalle Valo <kvalo@kernel.org>,
	 "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	 Jakub Kicinski <kuba@kernel.org>,
	Paolo Abeni <pabeni@redhat.com>,
	 Linux Wireless <linux-wireless@vger.kernel.org>,
	Linux Networking <netdev@vger.kernel.org>,
	 Linux Regressions <regressions@lists.linux.dev>,
	Bagas Sanjaya <bagasdotme@gmail.com>
Subject: Linux-6.5 iwlwifi crash
Date: Wed, 5 Jul 2023 15:24:23 +0800	[thread overview]
Message-ID: <CAAJw_Zug6VCS5ZqTWaFSr9sd85k=tyPm9DEE+mV=AKoECZM+sQ@mail.gmail.com> (raw)
In-Reply-To: <b9ab37d2-42bf-cc31-a2c0-a9b604e95530@gmail.com>

Latest linux-6.4 after June 27 crash my whole linux notebook once
iwlwifi is loaded. Anyone seeing this?

Bisect? Or there's a patch for this?

# modprobe iwlwifi
... Whole system frozen!


Here's my system before the crash ...

# dmesg
cfg80211: Loading compiled-in X.509 certificates for regulatory database
Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
iwlwifi 0000:00:14.3: api flags index 2 larger than supported by driver
thermal thermal_zone1: failed to read out thermal zone (-61)
iwlwifi 0000:00:14.3: Sorry - debug buffer is only 4096K while you
requested 65536K

# lspci
00:14.3 Network controller: Intel Corporation Alder Lake-P PCH CNVi
WiFi (rev 01)

# linux git log
commit d528014517f2b0531862c02865b9d4c908019dc4 (HEAD -> master,
origin/master, origin/HEAD)
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jul 4 15:05:12 2023 -0700

# lsmodModule                  Size  Used by
iwlmvm                397312  0
mac80211              626688  1 iwlmvm
iwlwifi               307200  1 iwlmvm
cfg80211              413696  3 iwlmvm,iwlwifi,mac80211


Bisect?

Thanks,
Jeff.

  reply	other threads:[~2023-07-05  7:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230429020951.082353595@lindbergh.monkeyblade.net>
2023-04-29  5:22 ` iwlwifi broken in post-linux-6.3.0 after April 26 Jeff Chua
2023-04-29 14:07   ` Bagas Sanjaya
2023-04-29 18:17     ` Jeff Chua
2023-04-30 10:58       ` Jeff Chua
2023-04-30 17:06         ` Greenman, Gregory
2023-04-30 18:00           ` Greenman, Gregory
2023-04-30 23:57             ` Jeff Chua
2023-05-01  4:46     ` Bagas Sanjaya
2023-07-05  7:24       ` Jeff Chua [this message]
2023-07-05  8:37         ` Linux-6.5 iwlwifi crash Linux regression tracking (Thorsten Leemhuis)
2023-07-05 11:56           ` Jeff Chua
2023-07-05 18:11             ` Larry Finger
2023-07-07  1:56               ` Jeff Chua
2023-07-07  8:43                 ` Linux regression tracking (Thorsten Leemhuis)
2023-07-07  9:48                   ` Thorsten Leemhuis
2023-07-07 18:07                   ` Larry Finger
2023-07-09  0:00                     ` Jeff Chua

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='CAAJw_Zug6VCS5ZqTWaFSr9sd85k=tyPm9DEE+mV=AKoECZM+sQ@mail.gmail.com' \
    --to=jeff.chua.linux@gmail.com \
    --cc=bagasdotme@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gregory.greenman@intel.com \
    --cc=kuba@kernel.org \
    --cc=kvalo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.