Bug#1026804: WIFI doesn't work for kernel 6.1
Hi, need to revert commit 066ecde6d826b4 "mmc: meson-gx: add SDIO interrupt support" http://lists.infradead.org/pipermail/linux-amlogic/2022-December/014532.html upstream has a WIP patch: http://lists.infradead.org/pipermail/linux-amlogic/2022-December/014547.html I don't have time to submit a patch to debian kernel. could someone help? BR. Ning.
Bug#1026804: WIFI doesn't work for kernel 6.1
On Wed, Dec 21, 2022 at 05:29:25PM +0100, Diederik de Haas wrote: > On Wednesday, 21 December 2022 17:11:55 CET Diederik de Haas wrote: > > Given that it worked with 6.0 but no more with 6.1-1~exp1 which I assume is > > a self-built kernel from current master, it seems more likely to be an > > upstream issue/regression. > > I just noticed the following part from that linux-amlogic post: > > I native build kernel from debian's kernel repo: > > https://salsa.debian.org/kernel-team/linux/ with some Amlogic patches: > > https://salsa.debian.org/zhangn1985/linux/-/tree/master/debian/patches/feat > > ures/arm64/meson all follow debian's kernel config. original patches are: https://salsa.debian.org/zhangn1985/linux/-/tree/master/debian/patches/features/npu and 0001, 0002, 0004, 0005, 0006, 0007, 0021, 0022, 0037 in https://salsa.debian.org/zhangn1985/linux/-/tree/master/debian/patches/features/khadas > > That path doesn't seem to exist anymore, but got redirected to 'just' the > master branch and noticed the latest commit "update patches from khadas". > When I looked into that, I saw there were a LOT of additional patches :-O > https://salsa.debian.org/zhangn1985/linux/-/tree/master/debian/patches/ > features/khadas I just want to apply all vendor patches to check whether wifi works. you can review all patches, it not related to WIFI, thus I don't think WIFI could magicly work. > > The test I suggested in my previous reply would still be useful, but it could > also be that your patch-set is at fault. this is reasonable suspect. I also use default debian kernel: https://packages.debian.org/experimental/arm64/linux-image-6.1.0-0-arm64/download WIFI stop work in 2mins. Logs are same, I don't duplicate. Default debian kernel 6.0 is good, and 6.1 is bad, this is a regression. upstream and vendor said they didn't see this issue, thus report to debian for help. BR. Ning.
Bug#1026804: WIFI doesn't work for kernel 6.1
On Wed, Dec 21, 2022 at 05:29:25PM +0100, Diederik de Haas wrote: > On Wednesday, 21 December 2022 17:11:55 CET Diederik de Haas wrote: > > Given that it worked with 6.0 but no more with 6.1-1~exp1 which I assume is > > a self-built kernel from current master, it seems more likely to be an > > upstream issue/regression. > > I just noticed the following part from that linux-amlogic post: > > I native build kernel from debian's kernel repo: > > https://salsa.debian.org/kernel-team/linux/ with some Amlogic patches: > > https://salsa.debian.org/zhangn1985/linux/-/tree/master/debian/patches/feat > > ures/arm64/meson all follow debian's kernel config. These patches are confirmed not related this issue. > > That path doesn't seem to exist anymore, but got redirected to 'just' the > master branch and noticed the latest commit "update patches from khadas". > When I looked into that, I saw there were a LOT of additional patches :-O > https://salsa.debian.org/zhangn1985/linux/-/tree/master/debian/patches/ > features/khadas khadas is the vendor, I tried to apply vendor's patches to make wifi work. you can just use default debian 6.1 kernel, to reproduce the issue. > > The test I suggested in my previous reply would still be useful, but it could > also be that your patch-set is at fault.
Bug#1026804: WIFI doesn't work for kernel 6.1
On Wednesday, 21 December 2022 17:11:55 CET Diederik de Haas wrote: > Given that it worked with 6.0 but no more with 6.1-1~exp1 which I assume is > a self-built kernel from current master, it seems more likely to be an > upstream issue/regression. I just noticed the following part from that linux-amlogic post: > I native build kernel from debian's kernel repo: > https://salsa.debian.org/kernel-team/linux/ with some Amlogic patches: > https://salsa.debian.org/zhangn1985/linux/-/tree/master/debian/patches/feat > ures/arm64/meson all follow debian's kernel config. That path doesn't seem to exist anymore, but got redirected to 'just' the master branch and noticed the latest commit "update patches from khadas". When I looked into that, I saw there were a LOT of additional patches :-O https://salsa.debian.org/zhangn1985/linux/-/tree/master/debian/patches/ features/khadas The test I suggested in my previous reply would still be useful, but it could also be that your patch-set is at fault. signature.asc Description: This is a digitally signed message part.
Bug#1026804: WIFI doesn't work for kernel 6.1
On Wednesday, 21 December 2022 12:47:45 CET Zhang Ning wrote: > Package: linux-image-arm64 > Version: 6.1-1~exp1 > > WIFI works well for my Arm64 SBCs (Khadas VIM1 & VIM3), both are Amlogic > SBC, S905x and A311D, with kernel 6.0 and early versions. > > these two boards are well supported by debian kernel, with all functions > work out of box. > > After update to 6.1, it stops work. > > WIFI doesn't response, please check attached logs. > > before send this bug to debian, I have asked upsteam[0], and device > vendor, whether they observe same issue, but the answers are no. > > thus I suspect this is the problem of debian kernel. > > [0] > http://lists.infradead.org/pipermail/linux-amlogic/2022-December/014544.htm > l Given that it worked with 6.0 but no more with 6.1-1~exp1 which I assume is a self-built kernel from current master, it seems more likely to be an upstream issue/regression. In the linux-amlogic post [0] it was tested with 6.1-rc8. https://tracker.debian.org/pkg/linux shows there have been several uploads of 6.1-rcX to experimental, so could you test those first? signature.asc Description: This is a digitally signed message part.
Bug#1026804: WIFI doesn't work for kernel 6.1
Package: linux-image-arm64 Version: 6.1-1~exp1 Hi Debian Kernel Team WIFI works well for my Arm64 SBCs (Khadas VIM1 & VIM3), both are Amlogic SBC, S905x and A311D, with kernel 6.0 and early versions. these two boards are well supported by debian kernel, with all functions work out of box. After update to 6.1, it stops work. WIFI doesn't response, please check attached logs. before send this bug to debian, I have asked upsteam[0], and device vendor, whether they observe same issue, but the answers are no. thus I suspect this is the problem of debian kernel. [0] http://lists.infradead.org/pipermail/linux-amlogic/2022-December/014544.html [ 363.500845] INFO: task kworker/0:0:7 blocked for more than 120 seconds. [ 363.506290] Tainted: G C 6.1.0-0-arm64 #1 Debian 6.1-1~exp1 [ 363.513749] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.521463] task:kworker/0:0 state:D stack:0 pid:7 ppid:2 flags:0x0008 [ 363.521478] Workqueue: events sdio_irq_work [ 363.521497] Call trace: [ 363.521502] __switch_to+0xe4/0x160 [ 363.521513] __schedule+0x340/0x970 [ 363.521521] schedule+0x58/0xf0 [ 363.521529] __mmc_claim_host+0x104/0x290 [ 363.521538] sdio_irq_work+0x2c/0x90 [ 363.521547] process_one_work+0x1f4/0x460 [ 363.521558] worker_thread+0x188/0x4d0 [ 363.521566] kthread+0xe0/0xe4 [ 363.521573] ret_from_fork+0x10/0x20 [ 363.521596] INFO: task kworker/u13:0:92 blocked for more than 120 seconds. [ 363.528292] Tainted: G C 6.1.0-0-arm64 #1 Debian 6.1-1~exp1 [ 363.535758] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.543544] task:kworker/u13:0 state:D stack:0 pid:92ppid:2 flags:0x0008 [ 363.543557] Workqueue: brcmf_wq/mmc2:0001:1 brcmf_sdio_dataworker [brcmfmac] [ 363.543593] Call trace: [ 363.543596] __switch_to+0xe4/0x160 [ 363.543606] __schedule+0x340/0x970 [ 363.543614] schedule+0x58/0xf0 [ 363.543620] __mmc_claim_host+0x104/0x290 [ 363.543630] sdio_claim_host+0x2c/0x40 [ 363.543638] brcmf_sdio_dataworker+0xa4/0x2174 [brcmfmac] [ 363.543665] process_one_work+0x1f4/0x460 [ 363.543674] worker_thread+0x188/0x4d0 [ 363.543681] kthread+0xe0/0xe4 [ 363.543688] ret_from_fork+0x10/0x20 [ 363.543714] INFO: task NetworkManager:515 blocked for more than 120 seconds. [ 363.550564] Tainted: G C 6.1.0-0-arm64 #1 Debian 6.1-1~exp1 [ 363.557234] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.564613] task:NetworkManager state:D stack:0 pid:515 ppid:1 flags:0x000c [ 363.564622] Call trace: [ 363.564624] __switch_to+0xe4/0x160 [ 363.564632] __schedule+0x340/0x970 [ 363.564638] schedule+0x58/0xf0 [ 363.564643] __mmc_claim_host+0x104/0x290 [ 363.564650] sdio_claim_host+0x2c/0x40 [ 363.564656] brcmf_sdio_bus_txctl+0x124/0x1b0 [brcmfmac] [ 363.564676] brcmf_proto_bcdc_msg+0xb8/0x110 [brcmfmac] [ 363.564695] brcmf_proto_bcdc_query_dcmd+0x48/0x1ec [brcmfmac] [ 363.564713] brcmf_fil_cmd_data+0xe8/0x124 [brcmfmac] [ 363.564733] brcmf_fil_cmd_data_get+0x50/0x80 [brcmfmac] [ 363.564751] brcmf_cfg80211_dump_station+0xc0/0x15c [brcmfmac] [ 363.564770] nl80211_dump_station+0x134/0x240 [cfg80211] [ 363.564808] netlink_dump+0x114/0x2d4 [ 363.564815] __netlink_dump_start+0x154/0x304 [ 363.564831] genl_family_rcv_msg_dumpit+0x8c/0x140 [ 363.564839] genl_rcv_msg+0x1f0/0x264 [ 363.564845] netlink_rcv_skb+0x64/0x130 [ 363.564851] genl_rcv+0x40/0x5c [ 363.564857] netlink_unicast+0x2d4/0x33c [ 363.564862] netlink_sendmsg+0x1d8/0x450 [ 363.564868] sock_sendmsg+0x5c/0x70 [ 363.564876] sys_sendmsg+0x290/0x2f4 [ 363.564880] ___sys_sendmsg+0xb4/0x110 [ 363.564885] __sys_sendmsg+0x8c/0xf0 [ 363.564890] __arm64_sys_sendmsg+0x2c/0x40 [ 363.564895] invoke_syscall+0x50/0x120 [ 363.564903] el0_svc_common.constprop.0+0x4c/0xf4 [ 363.564910] do_el0_svc+0x34/0xd0 [ 363.564916] el0_svc+0x34/0xd4 [ 363.564923] el0t_64_sync_handler+0xf4/0x120 [ 363.564928] el0t_64_sync+0x18c/0x190 [ 363.564937] INFO: task brcmf_wdog/mmc2:534 blocked for more than 120 seconds. [ 363.571596] Tainted: G C 6.1.0-0-arm64 #1 Debian 6.1-1~exp1 [ 363.578802] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.586366] task:brcmf_wdog/mmc2 state:D stack:0 pid:534 ppid:2 flags:0x0008 [ 363.586373] Call trace: [ 363.586375] __switch_to+0xe4/0x160 [ 363.586381] __schedule+0x340/0x970 [ 363.586385] schedule+0x58/0xf0 [ 363.586389] schedule_timeout+0x14c/0x180 [ 363.586395] __wait_for_common+0xd4/0x254 [ 363.586400] wait_for_completion+0x28/0x3c [ 363.586404] mmc_wait_for_req_done+0x30/0xf0 [ 363.586411] mmc_wait_for_req+0xb8/0x10c [ 363.586415] mmc_wait_for_cmd+0x6c/0xb0 [ 363.586420] mmc_io_rw_direct+0xa4/0x140 [ 363.586425] sdio_readb+0x54/0xa4 [ 363.586430]
