请选择 进入手机版 | 继续访问电脑版

华硕路由爱好者社区

 找回密码
 立即注册

手机号码,快捷登录

搜索
查看: 1173|回复: 26

[求助] GT-AC5300 WiFi突然全部崩掉,需要手动重启才正常

[复制链接]

5

主题

31

帖子

111

积分

注册会员

Rank: 2

积分
111
发表于 2019-2-12 00:29:16 | 显示全部楼层 |阅读模式
GT-AC5300 WiFi突然全部崩掉,需要手动重启才正常,有线是正常的,无线用着用着就全崩掉了,时间有时一两天,有时两三天,最长两个星期必崩掉一起,请问各位大佬这是怎么回事
日志如下
Feb 11 22:55:33 kernel: acme-client: https://acme-v01.api.letsencrypt ... mTBj7g/12512328027: bad response
Feb 11 22:55:33 kernel: acme-client: transfer buffer: [{ "type": "http-01", "status": "invalid", "error": { "type": "urn:acme:error:connection", "detail": "Fetching Timeout during connect (likely firewall problem)", "status": 400 }, "uri": "https://acme-v01.api.letsencrypt.org/acme/challenge/SY1U8d_VMjBsMcd7iHe8QaBePAkVX9_e5YnOAmTBj7g/12512328027", "token": "g2H6bVNU86iTRD2NxCpOBYYOOYYs5ZqcZ-43ACesfW
Feb 11 22:57:56 WLCEVENTD: eth7: Disassoc D8:63:75:91:B5:A9
Feb 11 22:57:56 WLCEVENTD: eth7: Disassoc D8:63:75:91:B5:A9
Feb 11 22:57:57 kernel: pgd = ffffffc002554000
Feb 11 22:57:57 kernel: [00000000] *pgd=000000000149a003, *pud=000000000149a003, *pmd=0000000003248003, *pte=0000000000000000
Feb 11 22:57:57 kernel: CPU: 1 PID: 30763 Comm: dcd Tainted: P           O    4.1.27 #2
Feb 11 22:57:57 kernel: Hardware name: Broadcom-v8A (DT)
Feb 11 22:57:57 kernel: task: ffffffc03414b480 ti: ffffffc0025b0000 task.ti: ffffffc0025b0000
Feb 11 22:57:57 kernel: PC is at 0xf7399f44
Feb 11 22:57:57 kernel: LR is at 0x1dc74
Feb 11 22:57:57 kernel: pc : [<00000000f7399f44>] lr : [<000000000001dc74>] pstate: 600e0010
Feb 11 22:57:57 kernel: sp : 00000000ff9708e8
Feb 11 22:57:57 kernel: x12: 000000000009ff10
Feb 11 22:57:57 kernel: x11: 00000000f66ff024 x10: 00000000000a02b4
Feb 11 22:57:57 kernel: x9 : 00000000f66ffb84 x8 : 00000000000a076c
Feb 11 22:57:57 kernel: x7 : 00000000f66ffbb4 x6 : 00000000000a0766
Feb 11 22:57:57 kernel: x5 : 0000000000000000 x4 : 00000000f66ffb68
Feb 11 22:57:57 kernel: x3 : 0000000000000000 x2 : 0000000000000000
Feb 11 22:57:57 kernel: x1 : 000000000007c674 x0 : 0000000000000000
Feb 11 22:59:59 WLCEVENTD: eth6: Assoc D8:63:75:91:B5:A9
Feb 11 23:00:00 rc_service: service 31833:notify_rc restart_letsencrypt
Feb 11 23:00:38 kernel: acme-client: https://acme-v01.api.letsencrypt ... dRVVJo/12512442229: bad response
Feb 11 23:00:38 kernel: acme-client: transfer buffer: [{ "type": "http-01", "status": "invalid", "error": { "type": "urn:acme:error:connection", "detail": "Fetching... wq4GP5Z__gkSmTpQTs: Timeout during connect (likely firewall problem)", "status": 400 }, "uri": "https://acme-v01.api.letsencrypt.org/acme/challenge/cG3tiFi6maC4GnJk4TUT1vGh36YKhyGjD64kVdRVVJo/12512442229", "token": "h2tP0VmQLUoFCgrqjLO3AVuGJwq4GP5Z__gkSmTpQT
Feb 11 23:02:03 disk_monitor: Got SIGALRM...
Feb 11 23:03:15 WLCEVENTD: eth7: Assoc E0:B9:BA:E0:7C:80
Feb 11 23:03:28 WLCEVENTD: eth7: Disassoc E0:B9:BA:E0:7C:80
Feb 11 23:05:00 rc_service: service 32121:notify_rc restart_letsencrypt
Feb 11 23:05:07 kernel: acme-client: https://acme-v01.api.letsencrypt.org/acme/new-authz: bad HTTP: 429
Feb 11 23:05:07 kernel: acme-client: transfer buffer: [{ "type": "urn:acme:error:rateLimited", "detail": "Error creating new authz :: too many failed authorizations recently: see https://letsencrypt.org/docs/rate-limits/", "status": 429 }] (189 bytes)
Feb 11 23:09:37 kernel: pgd = ffffffc0031f4000
Feb 11 23:09:37 kernel: [00000000] *pgd=000000001ca9b003, *pud=000000001ca9b003, *pmd=000000001caf3003, *pte=0000000000000000
Feb 11 23:09:37 kernel: CPU: 1 PID: 31642 Comm: dcd Tainted: P           O    4.1.27 #2
Feb 11 23:09:37 kernel: Hardware name: Broadcom-v8A (DT)
Feb 11 23:09:37 kernel: task: ffffffc03e86e080 ti: ffffffc002648000 task.ti: ffffffc002648000
Feb 11 23:09:37 kernel: PC is at 0xf7546f44
Feb 11 23:09:37 kernel: LR is at 0x1dc74
Feb 11 23:09:37 kernel: pc : [<00000000f7546f44>] lr : [<000000000001dc74>] pstate: 600e0010
Feb 11 23:09:37 kernel: sp : 00000000ffcb6238
Feb 11 23:09:37 kernel: x12: 000000000009ff10
Feb 11 23:09:37 kernel: x11: 00000000f67ff024 x10: 00000000000a02b4
Feb 11 23:09:37 kernel: x9 : 00000000f67ffb84 x8 : 00000000000a076c
Feb 11 23:09:37 kernel: x7 : 00000000f67ffbb4 x6 : 00000000000a0766
Feb 11 23:09:37 kernel: x5 : 0000000000000000 x4 : 00000000f67ffb68
Feb 11 23:09:37 kernel: x3 : 0000000000000000 x2 : 0000000000000000
Feb 11 23:09:37 kernel: x1 : 000000000007c674 x0 : 0000000000000000
Feb 11 23:10:00 rc_service: service 32470:notify_rc restart_letsencrypt
Feb 11 23:10:08 kernel: acme-client: https://acme-v01.api.letsencrypt.org/acme/new-authz: bad HTTP: 429
Feb 11 23:10:08 kernel: acme-client: transfer buffer: [{ "type": "urn:acme:error:rateLimited", "detail": "Error creating new authz :: too many failed authorizations recently: see https://letsencrypt.org/docs/rate-limits/", "status": 429 }] (189 bytes)
Feb 11 23:13:05 WLCEVENTD: eth7: Assoc E0:B9:BA:E0:7C:80
Feb 11 23:13:17 WLCEVENTD: eth7: Disassoc E0:B9:BA:E0:7C:80
Feb 11 23:15:00 rc_service: service 408:notify_rc restart_letsencrypt
Feb 11 23:15:07 kernel: acme-client: https://acme-v01.api.letsencrypt.org/acme/new-authz: bad HTTP: 429
Feb 11 23:15:07 kernel: acme-client: transfer buffer: [{ "type": "urn:acme:error:rateLimited", "detail": "Error creating new authz :: too many failed authorizations recently: see https://letsencrypt.org/docs/rate-limits/", "status": 429 }] (189 bytes)
Feb 11 23:20:00 rc_service: service 783:notify_rc restart_letsencrypt
Feb 11 23:20:39 kernel: acme-client: https://acme-v01.api.letsencrypt ... CExtdY/12512918368: bad response
Feb 11 23:20:39 kernel: acme-client: transfer buffer: [{ "type": "http-01", "status": "invalid", "error": { "type": "urn:acme:error:connection", "detail": "Fetching http://mikeken1992.asuscomm.com/ ... uiN42L_lC5-jPFsT2E: Timeout during connect (likely firewall problem)", "status": 400 }, "uri": "https://acme-v01.api.letsencrypt.org/acme/challenge/bnKl6tiQNVlfhQVS5JQmDDVxVbx2YSyxUmWGgCExtdY/12512918368", "token": "HyRSALLQ_RJdcjlwS_DN3A_dxuiN42L_lC5-jPFsT2
Feb 11 23:21:08 rc_service: cfg_server 1005:notify_rc restart_wireless
Feb 11 23:21:09 kernel: ubi1: attaching mtd9
Feb 11 23:21:09 kernel: ubi1: scanning is finished
Feb 11 23:21:09 kernel: ubi1: attached mtd9 (name "misc1", size 8 MiB)
Feb 11 23:21:09 kernel: ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
Feb 11 23:21:09 kernel: ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
Feb 11 23:21:09 kernel: ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
Feb 11 23:21:09 kernel: ubi1: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
Feb 11 23:21:09 kernel: ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
Feb 11 23:21:09 kernel: ubi1: max/mean erase counter: 4/2, WL threshold: 4096, image sequence number: 1913963574
Feb 11 23:21:09 kernel: ubi1: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 4
Feb 11 23:21:09 kernel: ubi1: background thread "ubi_bgt1d" started, PID 1023
Feb 11 23:21:10 kernel: UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "nvram", R/O mode
Feb 11 23:21:10 kernel: UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
Feb 11 23:21:10 kernel: UBIFS (ubi1:0): FS size: 5840896 bytes (5 MiB, 46 LEBs), journal size 1015809 bytes (0 MiB, 6 LEBs)
Feb 11 23:21:10 kernel: UBIFS (ubi1:0): reserved for root: 275879 bytes (269 KiB)
Feb 11 23:21:10 kernel: UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 4EFAFF37-F891-4CD7-BBFE-8A60474AB116, small LPT model
Feb 11 23:21:10 kernel: UBIFS (ubi1:0): un-mount UBI device 1
Feb 11 23:21:10 kernel: ubi1: detaching mtd9
Feb 11 23:21:10 kernel: ubi1: mtd9 is detached
Feb 11 23:25:00 rc_service: service 1422:notify_rc restart_letsencrypt
Feb 11 23:25:00 rc_service: waitting "restart_wireless" via cfg_server ...
Feb 11 23:25:15 rc_service: skip the event: restart_letsencrypt.
Feb 11 23:30:00 rc_service: service 1653:notify_rc restart_letsencrypt
Feb 11 23:30:00 rc_service: waitting "restart_wireless" via cfg_server ...
Feb 11 23:30:15 rc_service: skip the event: restart_letsencrypt.
Feb 11 23:32:50 kernel: pgd = ffffffc007665000
Feb 11 23:32:50 kernel: [4a434c74] *pgd=0000000000000000, *pud=0000000000000000
Feb 11 23:32:50 kernel: CPU: 0 PID: 4542 Comm: asus_lighttpd Tainted: P           O    4.1.27 #2
Feb 11 23:32:50 kernel: Hardware name: Broadcom-v8A (DT)
Feb 11 23:32:50 kernel: task: ffffffc015d6a080 ti: ffffffc0031dc000 task.ti: ffffffc0031dc000
Feb 11 23:32:50 kernel: PC is at 0xf739c7bc
Feb 11 23:32:50 kernel: LR is at 0xf73ed088
Feb 11 23:32:50 kernel: pc : [<00000000f739c7bc>] lr : [<00000000f73ed088>] pstate: 20000010
Feb 11 23:32:50 kernel: sp : 00000000ffacf718
Feb 11 23:32:50 kernel: x12: 00000000706a4950
Feb 11 23:32:50 kernel: x11: 00000000f73ed088 x10: 00000000002f9518
Feb 11 23:32:50 kernel: x9 : 00000000f73ed0bc x8 : 0000000000000100
Feb 11 23:32:50 kernel: x7 : 00000000f73ed088 x6 : 0000000000000138
Feb 11 23:32:50 kernel: x5 : 0000000000000028 x4 : 00000000002f9ce0
Feb 11 23:32:50 kernel: x3 : 00000000f73ed0f4 x2 : 00000000002f9cd8
Feb 11 23:32:50 kernel: x1 : 00000000706a4978 x0 : 000000004a434c6c
Feb 11 23:33:17 kernel: pgd = ffffffc01ca06000
Feb 11 23:33:17 kernel: [00000000] *pgd=000000002e8ab003, *pud=000000002e8ab003, *pmd=0000000015f24003, *pte=0000000000000000
Feb 11 23:33:17 kernel: CPU: 1 PID: 32547 Comm: dcd Tainted: P           O    4.1.27 #2
Feb 11 23:33:17 kernel: Hardware name: Broadcom-v8A (DT)
Feb 11 23:33:17 kernel: task: ffffffc034244b80 ti: ffffffc0053c8000 task.ti: ffffffc0053c8000
Feb 11 23:33:17 kernel: PC is at 0xf75acf44
Feb 11 23:33:17 kernel: LR is at 0x1dc74
Feb 11 23:33:17 kernel: pc : [<00000000f75acf44>] lr : [<000000000001dc74>] pstate: 600e0010
Feb 11 23:33:17 kernel: sp : 00000000ff90c4e8
Feb 11 23:33:17 kernel: x12: 000000000009ff10
Feb 11 23:33:17 kernel: x11: 00000000f68ff024 x10: 00000000000a02b4
Feb 11 23:33:17 kernel: x9 : 00000000f68ffb84 x8 : 00000000000a076c
Feb 11 23:33:17 kernel: x7 : 00000000f68ffbb4 x6 : 00000000000a0766
Feb 11 23:33:17 kernel: x5 : 0000000000000000 x4 : 00000000f68ffb68
Feb 11 23:33:17 kernel: x3 : 0000000000000000 x2 : 0000000000000000
Feb 11 23:33:17 kernel: x1 : 000000000007c674 x0 : 0000000000000000
Feb 11 23:35:00 rc_service: service 1894:notify_rc restart_letsencrypt
Feb 11 23:35:00 rc_service: waitting "restart_wireless" via cfg_server ...
Feb 11 23:35:15 rc_service: skip the event: restart_letsencrypt.
Feb 11 23:40:00 rc_service: service 2070:notify_rc restart_letsencrypt
Feb 11 23:40:00 rc_service: waitting "restart_wireless" via cfg_server ...
Feb 11 23:40:15 rc_service: skip the event: restart_letsencrypt.
Feb 11 23:45:00 rc_service: service 2311:notify_rc restart_letsencrypt
Feb 11 23:45:00 rc_service: waitting "restart_wireless" via cfg_server ...
Feb 11 23:45:15 rc_service: skip the event: restart_letsencrypt.
Feb 11 23:50:00 rc_service: service 2482:notify_rc restart_letsencrypt
Feb 11 23:50:00 rc_service: waitting "restart_wireless" via cfg_server ...
Feb 11 23:50:16 rc_service: skip the event: restart_letsencrypt.
Feb 11 23:55:00 rc_service: service 2659:notify_rc restart_letsencrypt
Feb 11 23:55:00 rc_service: waitting "restart_wireless" via cfg_server ...
Feb 11 23:55:16 rc_service: skip the event: restart_letsencrypt.
Feb 12 00:00:01 rc_service: service 2896:notify_rc restart_letsencrypt
Feb 12 00:00:01 rc_service: waitting "restart_wireless" via cfg_server ...
Feb 12 00:00:16 rc_service: skip the event: restart_letsencrypt.
Feb 12 00:05:00 rc_service: service 3071:notify_rc restart_letsencrypt
Feb 12 00:05:00 rc_service: waitting "restart_wireless" via cfg_server ...
Feb 12 00:05:15 rc_service: skip the event: restart_letsencrypt.
Feb 12 00:10:00 rc_service: service 3375:notify_rc restart_letsencrypt
Feb 12 00:10:00 rc_service: waitting "restart_wireless" via cfg_server ...
Feb 12 00:10:15 rc_service: skip the event: restart_letsencrypt.
Feb 12 00:15:00 rc_service: service 3652:notify_rc restart_letsencrypt
Feb 12 00:15:00 rc_service: waitting "restart_wireless" via cfg_server ...
Feb 12 00:15:15 rc_service: skip the event: restart_letsencrypt.
Feb 12 00:20:00 rc_service: service 4783:notify_rc restart_letsencrypt
Feb 12 00:20:00 rc_service: waitting "restart_wireless" via cfg_server ...
Feb 12 00:20:15 rc_service: skip the event: restart_letsencrypt.



本帖子中包含更多资源

您需要 登录 才可以下载或查看,没有帐号?立即注册

x

223

主题

2849

帖子

6320

积分

管理员

Rank: 9Rank: 9Rank: 9

积分
6320
发表于 2019-2-12 10:11:25 | 显示全部楼层
你的崩掉是什么现象,搜不到?  能搜到连不上?  连上了无法上网?
看你启用了smart connect ,试着关闭看看,
另外截图最好截到顶部你使用的固件版本
Using wireless to connect to life

335

主题

3715

帖子

8561

积分

管理员

正品行货

Rank: 9Rank: 9Rank: 9

积分
8561

RT-AC88U

发表于 2019-2-12 11:14:10 | 显示全部楼层
WiFi硬件部分会不会有问题了?

5

主题

31

帖子

111

积分

注册会员

Rank: 2

积分
111
 楼主| 发表于 2019-2-12 11:50:29 | 显示全部楼层
Sprite 发表于 2019-2-12 10:11
你的崩掉是什么现象,搜不到?  能搜到连不上?  连上了无法上网?
看你启用了smart connect ,试着关闭看看,
...

WIFI信号搜不到,重启后WIFI信号又出来了,固件是官方最新固件3.0.0.4.384_45149

5

主题

31

帖子

111

积分

注册会员

Rank: 2

积分
111
 楼主| 发表于 2019-2-12 11:51:40 | 显示全部楼层
Master 发表于 2019-2-12 11:14
WiFi硬件部分会不会有问题了?

应该不关硬件的事吧,我之前在狗东上买了个RT-AC5300,也是这样的问题,我才退了,入了GT-AC5300也是这卵样

5

主题

31

帖子

111

积分

注册会员

Rank: 2

积分
111
 楼主| 发表于 2019-2-12 11:53:44 | 显示全部楼层
手动重启后毛事没有,但是总是不间断就出现这种问题,最长不超过两个星期

5

主题

31

帖子

111

积分

注册会员

Rank: 2

积分
111
 楼主| 发表于 2019-2-12 11:58:40 来自手机 | 显示全部楼层
我帮家人从狗东去的RT-AC86U却没有这个问题,坑爹啊

1

主题

20

帖子

53

积分

注册会员

Rank: 2

积分
53
发表于 2019-2-12 14:12:38 来自手机 | 显示全部楼层
看楼主应该是和我差不多应该是断网了,我的断了指示灯却显示全部正常,不过断了不重拨,要手动开关路由才正常,我也是GT-AC5300,我的是路由拨号两天就断一次网最长是六天一断,断了也是全部wifi连不上,必须手动开关重启,固件是45149。我这现象差不多俩月了

5

主题

31

帖子

111

积分

注册会员

Rank: 2

积分
111
 楼主| 发表于 2019-2-12 15:29:00 | 显示全部楼层
風筝 发表于 2019-2-12 14:12
看楼主应该是和我差不多应该是断网了,我的断了指示灯却显示全部正常,不过断了不重拨,要手动开关路由才正 ...

我的也是指示灯全部正常,有时有线和无线一起崩掉,在崩掉的时候如果有线正在上网,那就只崩掉无线,几千块买个路由也不至于这样吧

223

主题

2849

帖子

6320

积分

管理员

Rank: 9Rank: 9Rank: 9

积分
6320
发表于 2019-2-12 16:33:22 | 显示全部楼层
mikeken1992 发表于 2019-2-12 15:29
我的也是指示灯全部正常,有时有线和无线一起崩掉,在崩掉的时候如果有线正在上网,那就只崩掉无线,几千 ...

你切换区域了吗?
Using wireless to connect to life
您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

小黑屋|手机版|Archiver|华硕路由爱好者社区 ( 苏ICP备16010857号-1 )苏公网安备 32050502000499号

GMT+8, 2019-7-22 18:14 , Processed in 0.027509 second(s), 24 queries .

Powered by Discuz! X3.4

© 2001-2017 Comsenz Inc.

快速回复 返回顶部 返回列表