Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kernel-6.1.1-ophub Wifi and Ethernet Unstable On GT King Pro (Rev A) and Does NOT Boot On SD Card #861

Closed
JFLim1 opened this issue Dec 25, 2022 · 8 comments

Comments

@JFLim1
Copy link

JFLim1 commented Dec 25, 2022

Hi @ophub,

Would like to provide feedback on the kernel-6.1.1-ophub on GT King Pro (Rev A).

If you boot up with Ethernet Cable connected Ethernet is available on boot up for a while, and after wake up from screen lock, sometimes Ethernet will be loss, NO more Ethernet. Gnome Settings Manager will show "Network Not Available" an "No WIFI"

If you unplug the Ethernet cable, Wifi is only available for 1 to 2 minutes after that NO more WIFI connectivity. Re-plug Ethernet Cable will NOT regain Ethernet connection and NO WIFI too.

If you boot up with NO Ethernet cable, WIFI is only available for 1 to 2 minutes and after that NO more WIFI connectivity. Gnome Settings Manager will show NO WIFI and "No Network". Plugging the Ethernet Cable will NOT trigger Ethernet to be available. Just NO network connectivity at all.

Once WIFI and Network is loss, Shutdown and Reboot basically do not work. Stuck at "A Stop Job is running for Network Manager..." Waiting for it to Stop but it just keep going without stopping. Need power cycle to reboot.

Kernel-6.1.1-ophub still does NOT boot up successfully on SD Card (I/O Errors) or recognise SD Card.

dmesg after unplug Ethernet Cable to trigger the loss of WIFI

[  197.718749] meson8b-dwmac ff3f0000.ethernet eth0: Link is Down
[  316.560836] EXT4-fs (sda2): error count since last fsck: 6
[  316.560858] EXT4-fs (sda2): initial error at time 6: ext4_validate_inode_bitmap:106
[  316.560868] EXT4-fs (sda2): last error at time 1671981604: ext4_mb_clear_bb:6077
[  605.332435] INFO: task kworker/0:2:259 blocked for more than 120 seconds.
[  605.333585]       Tainted: G         C         6.1.1-ophub #1
[  605.339295] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  605.347050] task:kworker/0:2     state:D stack:0     pid:259   ppid:2      flags:0x00000008
[  605.347064] Workqueue: events sdio_irq_work
[  605.347079] Call trace:
[  605.347081]  __switch_to+0xf8/0x19c
[  605.347088]  __schedule+0x510/0x690
[  605.347092]  schedule+0x60/0x98
[  605.347095]  __mmc_claim_host+0x164/0x2d4
[  605.347101]  sdio_irq_work+0x28/0x68
[  605.347105]  process_one_work+0x1dc/0x350
[  605.347111]  worker_thread+0x1b4/0x49c
[  605.347114]  kthread+0xc8/0xe0
[  605.347119]  ret_from_fork+0x10/0x20
[  605.347142] INFO: task kworker/u13:2:577 blocked for more than 120 seconds.
[  605.353952]       Tainted: G         C         6.1.1-ophub #1
[  605.359640] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  605.367403] task:kworker/u13:2   state:D stack:0     pid:577   ppid:2      flags:0x00000008
[  605.367417] Workqueue: brcmf_wq/mmc2:0001:1 brcmf_sdio_dataworker [brcmfmac]
[  605.367539] Call trace:
[  605.367542]  __switch_to+0xf8/0x19c
[  605.367555]  __schedule+0x510/0x690
[  605.367561]  schedule+0x60/0x98
[  605.367567]  schedule_timeout+0x34/0x12c
[  605.367576]  wait_for_common+0x110/0x250
[  605.367582]  wait_for_completion+0x18/0x24
[  605.367588]  mmc_wait_for_req_done+0x30/0x118
[  605.367598]  mmc_wait_for_req+0xc0/0xd8
[  605.367606]  mmc_io_rw_extended+0x1e8/0x2b4
[  605.367615]  sdio_io_rw_ext_helper+0x198/0x1d8
[  605.367624]  sdio_readsb+0x20/0x2c
[  605.367632]  brcmf_sdiod_skbuff_read+0x64/0xe8 [brcmfmac]
[  605.367740]  brcmf_sdiod_recv_pkt+0x100/0x134 [brcmfmac]
[  605.367848]  brcmf_sdiod_recv_buf+0x3c/0x94 [brcmfmac]
[  605.367955]  brcmf_sdio_dpc+0x6f4/0x2218 [brcmfmac]
[  605.368062]  brcmf_sdio_dataworker+0x3c/0x64 [brcmfmac]
[  605.368170]  process_one_work+0x1dc/0x350
[  605.368179]  worker_thread+0x1b4/0x49c
[  605.368185]  kthread+0xc8/0xe0
[  605.368193]  ret_from_fork+0x10/0x20
[  605.368202] INFO: task ksdioirqd/mmc2:580 blocked for more than 120 seconds.
[  605.374393]       Tainted: G         C         6.1.1-ophub #1
[  605.380077] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  605.387840] task:ksdioirqd/mmc2  state:D stack:0     pid:580   ppid:2      flags:0x00000008
[  605.387849] Call trace:
[  605.387852]  __switch_to+0xf8/0x19c
[  605.387862]  __schedule+0x510/0x690
[  605.387867]  schedule+0x60/0x98
[  605.387871]  __mmc_claim_host+0x164/0x2d4
[  605.387878]  sdio_irq_thread+0x74/0x1b4
[  605.387886]  kthread+0xc8/0xe0
[  605.387895]  ret_from_fork+0x10/0x20
[  605.387914] INFO: task NetworkManager:705 blocked for more than 120 seconds.
[  605.394831]       Tainted: G         C         6.1.1-ophub #1
[  605.400519] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  605.408289] task:NetworkManager  state:D stack:0     pid:705   ppid:1      flags:0x0000000c
[  605.408300] Call trace:
[  605.408302]  __switch_to+0xf8/0x19c
[  605.408312]  __schedule+0x510/0x690
[  605.408316]  schedule+0x60/0x98
[  605.408320]  __mmc_claim_host+0x164/0x2d4
[  605.408327]  sdio_claim_host+0x28/0x3c
[  605.408334]  brcmf_sdio_bus_txctl+0x130/0x1e8 [brcmfmac]
[  605.408422]  brcmf_proto_bcdc_query_dcmd+0xe8/0x288 [brcmfmac]
[  605.408491]  brcmf_fil_cmd_data+0x7c/0x154 [brcmfmac]
[  605.408558]  brcmf_fil_cmd_data_get+0x4c/0xc8 [brcmfmac]
[  605.408625]  brcmf_cfg80211_dump_station+0x80/0x150 [brcmfmac]
[  605.408693]  nl80211_dump_station+0xd4/0x180 [cfg80211]
[  605.408836]  netlink_dump+0x1a0/0x330
[  605.408847]  __netlink_dump_start+0x1fc/0x298
[  605.408853]  genl_rcv_msg+0x2b4/0x338
[  605.408859]  netlink_rcv_skb+0x104/0x11c
[  605.408864]  genl_rcv+0x34/0x4c
[  605.408869]  netlink_unicast+0x2a0/0x3e4
[  605.408873]  netlink_sendmsg+0x2b4/0x38c
[  605.408878]  ____sys_sendmsg+0x180/0x254
[  605.408887]  __sys_sendmsg+0xd0/0x130
[  605.408892]  __arm64_sys_sendmsg+0x24/0x30
[  605.408898]  invoke_syscall+0x40/0x100
[  605.408906]  el0_svc_common+0xbc/0x19c
[  605.408911]  do_el0_svc+0x2c/0xb8
[  605.408916]  el0_svc+0x2c/0xa4
[  605.408923]  el0t_64_sync_handler+0x84/0xf0
[  605.408929]  el0t_64_sync+0x19c/0x1a0
@JFLim1 JFLim1 changed the title Kernel-6.1.1-ophub Wifi and Ethernet Unstable On GT King Pro (Rev A) and Does Boot On SD Card Kernel-6.1.1-ophub Wifi and Ethernet Unstable On GT King Pro (Rev A) and Does NOT Boot On SD Card Dec 25, 2022
@ophub
Copy link
Owner

ophub commented Dec 26, 2022

armbian-update -k 5.15.85
armbian-update -k 6.1.1

The online kernel has been adjusted again, you can try to update it. Because the same version cannot be updated, you can update to other versions first and then update back to 6.1.1

@JFLim1
Copy link
Author

JFLim1 commented Dec 26, 2022

armbian-update -k 5.15.85 armbian-update -k 6.1.1

The online kernel has been adjusted again, you can try to update it. Because the same version cannot be updated, you can update to other versions first and then update back to 6.1.1

Hi @ophub,

Thanks for your quick response. Downloaded the new 6.1.1-flippy-80+.

Unfortunately same issue as above. Boot without Ethernet cable connected to GT King Pro (Rev A). Plugin Ethernet cable does not enable Ethernet. Gnome Settings Manager when selecting "Network" shows:

Oops, something has gone wrong. Please contact your software vendor.
NetworkManager needs to be running.

dmesg 6.1.1-flippy-80+_New_20221226 Also Loss Wifi within 1 minute

[  242.673932] task:kworker/0:3     state:D stack:0     pid:267   ppid:2      flags:0x00000008
[  242.673947] Workqueue: events sdio_irq_work
[  242.673966] Call trace:
[  242.673970]  __switch_to+0xf8/0x19c
[  242.673982]  __schedule+0x510/0x690
[  242.673990]  schedule+0x60/0x98
[  242.673997]  __mmc_claim_host+0x164/0x2d4
[  242.674004]  sdio_irq_work+0x28/0x68
[  242.674012]  process_one_work+0x1dc/0x350
[  242.674021]  worker_thread+0x1b4/0x49c
[  242.674027]  kthread+0xc8/0xe0
[  242.674036]  ret_from_fork+0x10/0x20
[  242.674061] INFO: task kworker/u13:2:568 blocked for more than 120 seconds.
[  242.680834]       Tainted: G         C         6.1.1-flippy-80+ #11
[  242.687038] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  242.694801] task:kworker/u13:2   state:D stack:0     pid:568   ppid:2      flags:0x00000008
[  242.694812] Workqueue: brcmf_wq/mmc2:0001:1 brcmf_sdio_dataworker [brcmfmac]
[  242.694928] Call trace:
[  242.694931]  __switch_to+0xf8/0x19c
[  242.694941]  __schedule+0x510/0x690
[  242.694948]  schedule+0x60/0x98
[  242.694956]  schedule_timeout+0x34/0x12c
[  242.694966]  wait_for_common+0x110/0x250
[  242.694973]  wait_for_completion+0x18/0x24
[  242.694981]  mmc_wait_for_req_done+0x30/0x118
[  242.694988]  mmc_wait_for_req+0xc0/0xd8
[  242.694994]  mmc_wait_for_cmd+0x64/0x9c
[  242.695000]  mmc_io_rw_direct+0x98/0x124
[  242.695007]  sdio_readb+0x48/0xa4
[  242.695014]  brcmf_sdio_bus_sleep+0x204/0x4c0 [brcmfmac]
[  242.695121]  brcmf_sdio_dpc+0x138/0x2218 [brcmfmac]
[  242.695227]  brcmf_sdio_dataworker+0x3c/0x64 [brcmfmac]
[  242.695333]  process_one_work+0x1dc/0x350
[  242.695341]  worker_thread+0x1b4/0x49c
[  242.695348]  kthread+0xc8/0xe0
[  242.695356]  ret_from_fork+0x10/0x20
[  242.695363] INFO: task ksdioirqd/mmc2:576 blocked for more than 120 seconds.
[  242.701788]       Tainted: G         C         6.1.1-flippy-80+ #11
[  242.707997] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  242.715767] task:ksdioirqd/mmc2  state:D stack:0     pid:576   ppid:2      flags:0x00000008
[  242.715776] Call trace:
[  242.715779]  __switch_to+0xf8/0x19c
[  242.715789]  __schedule+0x510/0x690
[  242.715796]  schedule+0x60/0x98
[  242.715803]  __mmc_claim_host+0x164/0x2d4
[  242.715810]  sdio_irq_thread+0x74/0x1b4
[  242.715817]  kthread+0xc8/0xe0
[  242.715826]  ret_from_fork+0x10/0x20
[  242.715847] INFO: task NetworkManager:705 blocked for more than 120 seconds.
[  242.722746]       Tainted: G         C         6.1.1-flippy-80+ #11
[  242.728956] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  242.736717] task:NetworkManager  state:D stack:0     pid:705   ppid:1      flags:0x0000000c
[  242.736726] Call trace:
[  242.736729]  __switch_to+0xf8/0x19c
[  242.736738]  __schedule+0x510/0x690
[  242.736745]  schedule+0x60/0x98
[  242.736752]  __mmc_claim_host+0x164/0x2d4
[  242.736759]  sdio_claim_host+0x28/0x3c
[  242.736766]  brcmf_sdio_bus_txctl+0x130/0x1e8 [brcmfmac]
[  242.736873]  brcmf_proto_bcdc_query_dcmd+0xe8/0x288 [brcmfmac]
[  242.736980]  brcmf_fil_cmd_data+0x7c/0x154 [brcmfmac]
[  242.737086]  brcmf_fil_cmd_data_get+0x4c/0xc8 [brcmfmac]
[  242.737193]  brcmf_cfg80211_dump_station+0x80/0x150 [brcmfmac]
[  242.737299]  nl80211_dump_station+0xd4/0x180 [cfg80211]
[  242.737517]  netlink_dump+0x1a0/0x330
[  242.737529]  __netlink_dump_start+0x1fc/0x298
[  242.737538]  genl_rcv_msg+0x2b4/0x338
[  242.737545]  netlink_rcv_skb+0x104/0x11c
[  242.737553]  genl_rcv+0x34/0x4c
[  242.737559]  netlink_unicast+0x2a0/0x3e4
[  242.737567]  netlink_sendmsg+0x2b4/0x38c
[  242.737573]  ____sys_sendmsg+0x180/0x254
[  242.737581]  __sys_sendmsg+0xd0/0x130
[  242.737586]  __arm64_sys_sendmsg+0x24/0x30
[  242.737592]  invoke_syscall+0x40/0x100
[  242.737601]  el0_svc_common+0xbc/0x19c
[  242.737610]  do_el0_svc+0x2c/0xb8
[  242.737618]  el0_svc+0x2c/0xa4
[  242.737623]  el0t_64_sync_handler+0x84/0xf0
[  242.737629]  el0t_64_sync+0x19c/0x1a0

Thanks for your great support.

@ophub ophub closed this as completed Dec 28, 2022
@JFLim1
Copy link
Author

JFLim1 commented Dec 28, 2022

Hi @ophub,

Looking forward to your new kernel 6.1.2 with the WIFI and Ethernet stablility issue resoloved. Currently 6.1.1-flippy-80+ and 6.1.1-ophub WIF NOT working and Ethernet NOT available if cable Not plugin before power up.

@JFLim1
Copy link
Author

JFLim1 commented Jan 1, 2023

Hi @ophub,

Wishing you and team a A Happy & Prosperous New Year!

Just tested your new kerne-6.1.2-ophub. Still have the same WIFI issue. When Ethernet cable not connected to the GT King Pro during Power Up and boot up, WIFI will only be available for a short time may be 1 minute, after that NO more network detected NO WIFI and if you plugin Ethernet Cable it will not be detected just NO Network.

If you select shutdown/power off from the desktop menu, it will NOT shutdown cleanly in the sense that it will keep waiting for "network job to be stopped" with will never stop as network is NOT available.

If you Power Up with Ethernet cable connected to GT King Pro on Power Up to boot, Ethernet is available, Ethernet and Network will be loss after ideal for some time when wake up from screen lock out. Can't understand why.

Do you face similar WIFI issue on your GT King Pro with kernel-6.1.2-ophub or 6.1.1-flippy-80+?

Kernel 5.15.85-flippy-80+o works fine (Ethernet and WIFI stable) except it has issue with KDE Plasma 5.25.y and 5.26.y which I have highlighted before where Power OFF Monitor/Display will result in Loss of Desktop and will NOT reboot to Desktop Environment. The solution is to Delete ".local/share/kscreen/" and ".local/share/kscreen/outputs/" and reboot.

@ophub
Copy link
Owner

ophub commented Jan 4, 2023

Snip20230104_1

Snip20230104_2

Snip20230104_4

My gtk-pro has not been used for a month. Today I installed the latest version and tested the 6.1.2 kernel. My wired network, desktop, screen off/wake up, etc. are all working normally. Bluetooth works fine. My wireless is wifi6, and it has not been driven, so I have not used this wireless.

I have been powered on for 10 hours and the wired network is fine.

@JFLim1
Copy link
Author

JFLim1 commented Jan 4, 2023

I have been powered on for 10 hours and the wired network is fine.

In my case for kernel-6.1.1 or 6.1.2, if Ethernet Cable is connected to the GT King Pro (Rev A) during Power Up to boot, Ethernet connection is available and have Ethernet connections for hours as long as it did NOT enter into "screen lock out". When I power off/shutdown it will NOT Shutdown it stuck on trying to "Stop Network or WPA...".

Now the real issue is when there is NO Enthernet cable connected to GT King Pro during Power Up to boot. It will boot up normally and WIFI will only be available for 1 minute or so and then NO more WIFI or Network access!

For your info, just tested Manjaro-Arm kernel-6.1.2 also have the same issue as your kernel-6.1.2-flippy-80+. So it might be an upstream issue but what is causing it I have no idea.

Will try out the new 6.1.3-flippy-81+ and report the results.

Thank you.

@JFLim1
Copy link
Author

JFLim1 commented Jan 5, 2023

Hi @ophub,

Just tested your new 6.1.3-flippy-81+ kernel on my GT King Pro (Rev A) boot up without Ethernet Cable connected . No WIFI after a few minutes of boot up. For your info, when WIFI is loss after a few minutes of boot up, the "WIFI" logo on the "Top Right Bar" is still there but in "Gnome Settings" the "WIFI" Logo is gone and Network is also Not available.

Screenshot from 2023-01-05 13-30-43

Right after boot up WIFI is available but just for a few minutes and WIFI will be loss. Shutdown/Power OFF will get stuck "Stop job....".

@JFLim1
Copy link
Author

JFLim1 commented Jan 5, 2023

Hi @ophub

Kernel-6.1.3-flippy-81+ boot up with Ethernet Cable connected to GT King Pro (Rev A). Ethernet connection is available. Screen Shot taken right after boot up.

~$ uname -a
Linux opbu 6.1.3-flippy-81+ #23 SMP Wed Jan  4 20:45:50 CST 2023 aarch64 aarch64 aarch64 GNU/Linux

image

Somehow Ethernet speed is indicated at 100 Mb/s, usually it is 1000 Mb/s. On "Gnome Settings" the "WIFI" is also available. The minute the Ethernet Cable is unplugged, WIFI and Network will be loss and "Gnome Settings" will be as the previous message where WIFI and Network will be loss.

Hope this info is useful for you and Unifreq to figure out what is wrong.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants