[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANL0fFSmqR4F=9bFgVRaKXyCDocwwhxySUBo5x=12900fhWn6A@mail.gmail.com>
Date: Sat, 7 May 2022 16:37:58 +0200
From: Gonsolo <gonsolo@...il.com>
To: Stephen Hemminger <stephen@...workplumber.org>
Cc: Felix Fietkau <nbd@....name>,
Lorenzo Bianconi <lorenzo@...nel.org>,
Ryder Lee <ryder.lee@...iatek.com>,
Shayne Chen <shayne.chen@...iatek.com>,
Sean Wang <sean.wang@...iatek.com>,
Kalle Valo <kvalo@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
Matthias Brugger <matthias.bgg@...il.com>,
linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: Suspend/resume error with AWUS036ACM
Dear Stephen,
> Contact Ubuntu. The rule for upstream is if you load out of tree drivers
> than that kernel is unsupported.
I compiled a stock 5.17.5 kernel from git.kernel.org, installed
without kernel headers (forcing dkms to not build proprietary drivers)
and get the following errors *at boot time* (not suspend/resume):
+0,000386] wlx00c0cab022a0: associate with 8c:6a:8d:9e:2a:88 (try 1/3)
[ +0,001118] ================================================================================
[ +0,000005] UBSAN: invalid-load in net/mac80211/status.c:1164:21
[ +0,000004] load of value 255 is not a valid value for type '_Bool'
[ +0,000003] CPU: 10 PID: 380 Comm: kworker/u256:5 Not tainted 5.17.5 #3
[ +0,000004] Hardware name: To Be Filled By O.E.M. To Be Filled By
O.E.M./X399 Phantom Gaming 6, BIOS P1.31 01/14/2021
[ +0,000003] Workqueue: mt76 mt76u_tx_status_data [mt76_usb]
[ +0,000009] Call Trace:
[ +0,000002] <TASK>
[ +0,000003] dump_stack_lvl+0x4c/0x63
[ +0,000009] dump_stack+0x10/0x12
[ +0,000004] ubsan_epilogue+0x9/0x45
[ +0,000003] __ubsan_handle_load_invalid_value.cold+0x44/0x49
[ +0,000004] ieee80211_tx_status_ext.cold+0x1e/0xb8 [mac80211]
[ +0,000058] ? __radix_tree_delete+0x91/0x100
[ +0,000006] mt76_tx_status_unlock+0x119/0x170 [mt76]
[ +0,000011] mt76x02_send_tx_status+0x1af/0x420 [mt76x02_lib]
[ +0,000009] mt76x02_tx_status_data+0x47/0x70 [mt76x02_lib]
[ +0,000007] mt76u_tx_status_data+0x67/0xc0 [mt76_usb]
[ +0,000005] process_one_work+0x21f/0x3f0
[ +0,000005] worker_thread+0x50/0x3d0
[ +0,000004] ? rescuer_thread+0x390/0x390
[ +0,000003] kthread+0xee/0x120
[ +0,000003] ? kthread_complete_and_exit+0x20/0x20
[ +0,000004] ret_from_fork+0x22/0x30
[ +0,000005] </TASK>
[ +0,000001] ================================================================================
[ +0,003098] wlx00c0cab022a0: RX AssocResp from 8c:6a:8d:9e:2a:88
(capab=0x1411 status=0 aid=16)
I sent the first email because I suspected that the above (locking?)
problem was totally unrelated to the GPU driver.
I hope that this is more helpful.
--
g
Powered by blists - more mailing lists