linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ammar Faizi <ammar.faizi@students.amikom.ac.id>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	Jakub Kicinski <kuba@kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	"John W. Linville" <linville@tuxdriver.com>,
	Vasanthakumar Thiagarajan <vthiagar@qca.qualcomm.com>,
	Avraham Stern <avraham.stern@intel.com>,
	linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: WARNING: CPU: 2 PID: 633 at net/wireless/sme.c:974 cfg80211_roamed+0x265/0x2a0 [cfg80211]
Date: Wed, 13 Oct 2021 18:27:09 +0700	[thread overview]
Message-ID: <20211013112709.636468-1-ammar.faizi@students.amikom.ac.id> (raw)
In-Reply-To: <874k9l1p19.fsf@tynnyri.adurom.net>

On Wed, Oct 13, 2021 at 12:18 PM Kalle Valo <kvalo@codeaurora.org> wrote:
> >
> > Here is the log:
> >
> > <4>[266728.385936][  T633] ------------[ cut here ]------------
> > <4>[266728.385946][  T633] WARNING: CPU: 2 PID: 633 at net/wireless/sme.c:974 cfg80211_roamed+0x265/0x2a0 [cfg80211]
> > <4>[266728.386040][ T633] Modules linked in: rfcomm xt_CHECKSUM
> > xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp
> > nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6
> > nf_defrag_ipv4 nft_counter nf_tables nfnetlink bridge stp llc bfq cmac
> > algif_hash algif_skcipher af_alg bnep dm_multipath scsi_dh_rdac
> > scsi_dh_emc scsi_dh_alua snd_hda_codec_realtek snd_hda_codec_hdmi
> > uvcvideo snd_hda_codec_generic ledtrig_audio snd_hda_intel
> > videobuf2_vmalloc snd_intel_dspcfg videobuf2_memops snd_intel_sdw_acpi
> > btusb btrtl videobuf2_v4l2 videobuf2_common btbcm snd_hda_codec
> > btintel videodev snd_hda_core bluetooth snd_hwdep wl(OE) mc snd_pcm
> > ecdh_generic snd_seq_midi ecc snd_seq_midi_event edac_mce_amd
> > snd_rawmidi kvm_amd acer_wmi snd_seq sparse_keymap kvm cfg80211
> > wmi_bmof input_leds serio_raw snd_seq_device snd_timer snd soundcore
> > ccp fam15h_power k10temp mac_hid sch_fq_codel msr ip_tables x_tables
> > autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov
> > async_memcpy async_pq
> > <4>[266728.386224][ T633] async_xor async_tx xor raid6_pq libcrc32c
> > raid1 raid0 multipath linear amdgpu iommu_v2 gpu_sched radeon
> > i2c_algo_bit drm_ttm_helper ttm hid_generic drm_kms_helper syscopyarea
> > usbhid crct10dif_pclmul sysfillrect crc32_pclmul sysimgblt hid
> > ghash_clmulni_intel fb_sys_fops cec aesni_intel rc_core rtsx_pci_sdmmc
> > sdhci_pci crypto_simd cqhci r8169 cryptd psmouse ahci xhci_pci
> > rtsx_pci realtek libahci drm sdhci i2c_piix4 xhci_pci_renesas wmi
> > video
> > <4>[266728.386330][ T633] CPU: 2 PID: 633 Comm: wl_event_handle
> > Tainted: G W OE 5.15.0-rc4-for-5.16-io-uring-00060-g4922ab639eb6 #4
> > 8b24b2500a34cedea2e69c8d84eb4c855e713e61
> > <4>[266728.386337][  T633] Hardware name: Acer Aspire ES1-421/OLVIA_BE, BIOS V1.05 07/02/2015
> > <4>[266728.386341][  T633] RIP: 0010:cfg80211_roamed+0x265/0x2a0 [cfg80211]
> > <4>[266728.386408][ T633] Code: 4c 89 f7 49 8d 8d 22 01 00 00 45 0f b6
> > 85 42 01 00 00 6a 02 48 8b 36 e8 79 ab fc ff 48 89 43 08 5a 48 85 c0
> > 0f 85 d6 fd ff ff <0f> 0b 48 8d 65 d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3
> > 0f 0b 48 8b 73
> > <4>[266728.386412][  T633] RSP: 0018:ffffc9000157bdd8 EFLAGS: 00010246
> > <4>[266728.386418][  T633] RAX: 0000000000000000 RBX: ffffc9000157be20 RCX: 0000000000000000
> > <4>[266728.386421][  T633] RDX: 0000000000000002 RSI: 0000000000000000 RDI: ffffffff8109ead2
> > <4>[266728.386425][  T633] RBP: ffffc9000157be10 R08: 0000000000000001 R09: 0000000000000001
> > <4>[266728.386428][  T633] R10: fffffffefb3c8d52 R11: ffff8881328b75b2 R12: 0000000000000cc0
> > <4>[266728.386431][  T633] R13: ffff888105873800 R14: ffff8881328b6580 R15: dead000000000100
> > <4>[266728.386435][  T633] FS:  0000000000000000(0000) GS:ffff888313d00000(0000) knlGS:0000000000000000
> > <4>[266728.386439][  T633] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> > <4>[266728.386443][  T633] CR2: 00007f3033edd000 CR3: 000000011a878000 CR4: 00000000000406e0
> > <4>[266728.386447][  T633] Call Trace:
> > <4>[266728.386456][  T633]  ? wl_update_bss_info.isra.0+0xf5/0x210 [wl 47ce17d152623ac79abb5e1d4a28d4375eb94473]
> > <4>[266728.386555][  T633]  wl_bss_roaming_done.constprop.0+0xc4/0x100 [wl 47ce17d152623ac79abb5e1d4a28d4375eb94473]
> > <4>[266728.386648][  T633]  wl_notify_roaming_status+0x3f/0x60 [wl 47ce17d152623ac79abb5e1d4a28d4375eb94473]
> > <4>[266728.386730][  T633]  wl_event_handler+0x5f/0x140 [wl 47ce17d152623ac79abb5e1d4a28d4375eb94473]
> > <4>[266728.386808][  T633]  ? wl_cfg80211_del_key+0x100/0x100 [wl 47ce17d152623ac79abb5e1d4a28d4375eb94473]
>
> What wireless device and driver you have? Based on the call trace it
> looks like you are using Broadcom's out-of-tree driver called wl.
>

Yes, it is. Here is the info when I load the module.

<5>[329274.450461][T634003] cfg80211: Loading compiled-in X.509 certificates for regulatory database
<5>[329274.451011][T634003] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
<4>[329274.876411][T634003] wlan0: Broadcom BCM4365 802.11 Hybrid Wireless Controller 6.30.223.271 (r587334)
<4>[329274.876424][T634003]
<6>[329275.232559][T634007] wl 0000:02:00.0 wlp2s0: renamed from wlan0
<6>[329294.320737][  T892] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready

Any direction where to go or what to do?

-- 
Ammar Faizi

      reply	other threads:[~2021-10-13 11:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-12 14:52 WARNING: CPU: 2 PID: 633 at net/wireless/sme.c:974 cfg80211_roamed+0x265/0x2a0 [cfg80211] Ammar Faizi
2021-10-13  5:17 ` Kalle Valo
2021-10-13 11:27   ` Ammar Faizi [this message]

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=20211013112709.636468-1-ammar.faizi@students.amikom.ac.id \
    --to=ammar.faizi@students.amikom.ac.id \
    --cc=avraham.stern@intel.com \
    --cc=davem@davemloft.net \
    --cc=johannes@sipsolutions.net \
    --cc=kuba@kernel.org \
    --cc=kvalo@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=netdev@vger.kernel.org \
    --cc=vthiagar@qca.qualcomm.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;
as well as URLs for NNTP newsgroup(s).