设为首页收藏本站
切换到宽版

华硕网络产品技术交流平台

 找回密码
 立即注册

QQ登录

只需一步，快速开始

手机号码，快捷登录

华硕网络产品技术交流平台»首页 › 终端设备 › 路由器 › RT-AC86U频繁出现以下日志kernel: bcm63xx_nand ff80180 ...
12下一页
返回列表 发新帖
查看: 20879|回复: 10

[求助] RT-AC86U频繁出现以下日志kernel: bcm63xx_nand ff801800.nand: timeout w...

[复制链接]
1gggddd

8

主题

32

回帖

154

积分

注册会员

Rank: 2

积分
154
发表于 2021-5-8 22:08:48 | 显示全部楼层 |阅读模式
最新固件：3.0.0.4.386_42643-g16dc577
频繁出现以下日志，请问这是什么意思？我该如何解决，。
May  8 21:46:39 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x4May  8 21:46:39 kernel: bcm63xx_nand ff801800.nand: intfc status c80000e0
May  8 21:46:42 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x1
May  8 21:46:42 kernel: bcm63xx_nand ff801800.nand: intfc status f80000e0
May  8 21:46:43 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x1
May  8 21:46:43 kernel: bcm63xx_nand ff801800.nand: intfc status f80000e0
May  8 21:53:22 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x1
May  8 21:53:22 kernel: bcm63xx_nand ff801800.nand: intfc status f80000e0
May  8 21:56:36 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x1
May  8 21:56:36 kernel: bcm63xx_nand ff801800.nand: intfc status f80000e0

微信扫一扫，阅读更方便^_^
回复

使用道具 举报

Dr.Antenna

16

主题

3039

回帖

7717

积分

管理员

Rank: 9Rank: 9Rank: 9

积分
7717

RT-AC68URT-AC86UGT-AC5300
发表于 2021-5-9 20:46:40 | 显示全部楼层
日志前面有出现类似的讯息吗？
nand: Could not find valid ONFI parameter page; aborting
nand: device found, Manufacturer ID: 0xc2, Chip ID: 0xda
nand: Macronix NAND 256MiB 3,3V 8-bit
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
回复 支持 反对

使用道具 举报

1gggddd

8

主题

32

回帖

154

积分

注册会员

Rank: 2

积分
154
 楼主| 发表于 2021-5-9 23:23:35 | 显示全部楼层
Dr.Antenna 发表于 2021-5-9 20:46
日志前面有出现类似的讯息吗？
nand: Could not find valid ONFI parameter page; aborting
nand: device ...

没有注意，使用了救援模式，命令清空了JFFS空间，恢复了出厂模式，此问题没有再现。
但又发现了新问题，如下，请帮忙看一下，
closed unexpectedly是不是表示我手机断wifi？
nf_conntrack: expectation table full 有办法解决吗？是不是关了防火墙能解决此问题，关防火墙，危险大吗？

PS:有使用此路由挂三台CDN挖矿
May  9 13:11:32 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 13:13:34 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 13:15:35 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 13:16:58 kernel: nf_conntrack: expectation table full
May  9 13:16:58 kernel: nf_conntrack: expectation table full
May  9 13:16:58 kernel: nf_conntrack: expectation table full
May  9 13:16:58 kernel: nf_conntrack: expectation table full
May  9 13:16:58 kernel: nf_conntrack: expectation table full
May  9 13:16:58 kernel: nf_conntrack: expectation table full
May  9 13:16:58 kernel: nf_conntrack: expectation table full
May  9 13:16:58 kernel: nf_conntrack: expectation table full
May  9 13:16:58 kernel: nf_conntrack: expectation table full
May  9 13:16:58 kernel: nf_conntrack: expectation table full
May  9 13:17:04 kernel: nf_conntrack: expectation table full
May  9 13:17:04 kernel: nf_conntrack: expectation table full
May  9 13:17:10 kernel: nf_conntrack: expectation table full
May  9 13:17:10 kernel: nf_conntrack: expectation table full
May  9 13:17:10 kernel: nf_conntrack: expectation table full
May  9 13:17:10 kernel: nf_conntrack: expectation table full
May  9 13:17:10 kernel: nf_conntrack: expectation table full
May  9 13:17:10 kernel: nf_conntrack: expectation table full
May  9 13:17:10 kernel: nf_conntrack: expectation table full
May  9 13:17:10 kernel: nf_conntrack: expectation table full
May  9 13:17:10 kernel: nf_conntrack: expectation table full
May  9 13:17:10 kernel: nf_conntrack: expectation table full
May  9 13:17:25 kernel: nf_conntrack: expectation table full
May  9 13:17:25 kernel: nf_conntrack: expectation table full
May  9 13:17:26 kernel: nf_conntrack: expectation table full
May  9 13:17:26 kernel: nf_conntrack: expectation table full
May  9 13:17:26 kernel: nf_conntrack: expectation table full
May  9 13:17:26 kernel: nf_conntrack: expectation table full
May  9 13:17:38 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 13:19:40 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 13:20:13 kernel: nf_conntrack: expectation table full
May  9 13:20:13 kernel: nf_conntrack: expectation table full
May  9 13:20:13 kernel: nf_conntrack: expectation table full
May  9 13:20:13 kernel: nf_conntrack: expectation table full
May  9 13:20:13 kernel: nf_conntrack: expectation table full
May  9 13:20:13 kernel: nf_conntrack: expectation table full
May  9 13:20:13 kernel: nf_conntrack: expectation table full
May  9 13:20:13 kernel: nf_conntrack: expectation table full
May  9 13:20:13 kernel: nf_conntrack: expectation table full
May  9 13:20:13 kernel: nf_conntrack: expectation table full
May  9 13:20:19 kernel: nf_conntrack: expectation table full
May  9 13:20:19 kernel: nf_conntrack: expectation table full
May  9 13:20:19 kernel: nf_conntrack: expectation table full
May  9 13:20:19 kernel: nf_conntrack: expectation table full
May  9 13:20:19 kernel: nf_conntrack: expectation table full
May  9 13:20:19 kernel: nf_conntrack: expectation table full
May  9 13:20:19 kernel: nf_conntrack: expectation table full
May  9 13:20:19 kernel: nf_conntrack: expectation table full
May  9 13:20:19 kernel: nf_conntrack: expectation table full
May  9 13:20:19 kernel: nf_conntrack: expectation table full
May  9 13:20:29 kernel: nf_conntrack: expectation table full
May  9 13:20:29 kernel: nf_conntrack: expectation table full
May  9 13:20:29 kernel: nf_conntrack: expectation table full
May  9 13:20:29 kernel: nf_conntrack: expectation table full
May  9 13:20:30 kernel: nf_conntrack: expectation table full
May  9 13:20:30 kernel: nf_conntrack: expectation table full
May  9 13:20:30 kernel: nf_conntrack: expectation table full
May  9 13:20:30 kernel: nf_conntrack: expectation table full
May  9 13:20:30 kernel: nf_conntrack: expectation table full
May  9 13:20:30 kernel: nf_conntrack: expectation table full
May  9 13:21:43 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 13:23:47 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 13:25:50 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 13:27:53 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 13:29:54 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 13:31:58 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 13:34:01 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 13:36:04 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 13:38:07 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 13:40:10 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 13:42:13 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 13:44:14 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 13:46:22 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 13:48:24 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 13:50:25 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 13:52:28 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 13:54:32 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 13:56:35 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 13:58:38 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 14:00:40 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 14:02:43 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 14:04:46 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 14:06:49 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 14:08:52 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 14:10:55 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 14:12:58 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 14:15:01 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 14:17:05 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 14:19:08 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 14:21:11 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 14:23:14 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 14:25:17 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 14:27:20 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 14:29:23 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 14:31:26 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 14:33:29 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 14:35:32 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 14:37:35 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 14:39:35 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 14:41:38 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 14:43:41 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 14:45:44 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 14:47:47 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 14:49:51 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 14:49:52 kernel: nf_conntrack: expectation table full
May  9 14:49:52 kernel: nf_conntrack: expectation table full
May  9 14:49:52 kernel: nf_conntrack: expectation table full
May  9 14:49:52 kernel: nf_conntrack: expectation table full
May  9 14:49:52 kernel: nf_conntrack: expectation table full
May  9 14:49:52 kernel: nf_conntrack: expectation table full
May  9 14:49:52 kernel: nf_conntrack: expectation table full
May  9 14:49:55 kernel: nf_conntrack: expectation table full
May  9 14:49:55 kernel: nf_conntrack: expectation table full
May  9 14:49:55 kernel: nf_conntrack: expectation table full
May  9 14:49:58 kernel: nf_conntrack: expectation table full
May  9 14:49:58 kernel: nf_conntrack: expectation table full
May  9 14:49:58 kernel: nf_conntrack: expectation table full
May  9 14:49:58 kernel: nf_conntrack: expectation table full
May  9 14:50:00 kernel: nf_conntrack: expectation table full
May  9 14:50:00 kernel: nf_conntrack: expectation table full
May  9 14:50:00 kernel: nf_conntrack: expectation table full
May  9 14:50:00 kernel: nf_conntrack: expectation table full
May  9 14:50:00 kernel: nf_conntrack: expectation table full
May  9 14:50:00 kernel: nf_conntrack: expectation table full
May  9 14:50:05 kernel: nf_conntrack: expectation table full
May  9 14:50:05 kernel: nf_conntrack: expectation table full
May  9 14:50:05 kernel: nf_conntrack: expectation table full
May  9 14:50:05 kernel: nf_conntrack: expectation table full
May  9 14:50:05 kernel: nf_conntrack: expectation table full
May  9 14:50:05 kernel: nf_conntrack: expectation table full
May  9 14:50:05 kernel: nf_conntrack: expectation table full
May  9 14:50:05 kernel: nf_conntrack: expectation table full
May  9 14:50:09 kernel: nf_conntrack: expectation table full
May  9 14:50:09 kernel: nf_conntrack: expectation table full
May  9 14:51:54 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 14:53:57 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 14:56:00 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 14:58:03 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 15:00:06 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 15:02:10 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 15:04:13 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 15:06:16 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 15:08:19 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 15:10:22 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 15:12:25 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 15:14:28 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 15:16:31 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 15:18:34 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 15:20:37 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 15:22:40 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 15:24:43 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 15:26:43 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 15:28:46 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 15:30:49 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 15:32:52 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 15:34:55 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 15:36:58 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 15:39:01 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 15:41:04 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 15:43:07 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 15:45:10 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 15:47:13 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 15:49:17 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 15:51:20 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 15:53:23 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 15:55:26 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 15:57:29 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 15:59:32 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 16:01:35 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 16:03:35 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 16:05:38 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 16:07:41 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 16:09:44 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 16:11:47 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 16:13:50 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 16:15:53 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 16:17:56 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 16:19:59 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 16:22:02 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 16:24:05 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 16:26:08 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 16:28:11 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 16:30:15 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 16:32:18 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 16:34:21 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 16:36:24 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 16:38:27 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 16:40:30 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 16:42:33 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 16:44:36 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 16:46:39 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 16:48:39 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 16:50:42 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 16:52:45 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 16:54:48 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 16:56:51 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 16:58:54 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 17:00:57 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 17:03:00 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 17:05:03 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 17:07:06 miniupnpd[1424]: HTTP Connection from 192.168.50.106 closed unexpectedly
May  9 18:29:34 miniupnpd[1424]: removed 12 unused rules
May  9 18:49:34 miniupnpd[1424]: removed 13 unused rules
May  9 19:09:34 miniupnpd[1424]: removed 12 unused rules
May  9 19:29:35 miniupnpd[1424]: removed 13 unused rules
May  9 19:49:36 miniupnpd[1424]: removed 13 unused rules
May  9 20:09:35 miniupnpd[1424]: removed 13 unused rules
May  9 20:29:35 miniupnpd[1424]: removed 13 unused rules
May  9 20:49:35 miniupnpd[1424]: removed 13 unused rules
May  9 21:19:35 miniupnpd[1424]: removed 12 unused rules
May  9 21:39:35 miniupnpd[1424]: removed 14 unused rules
回复 支持 反对

使用道具 举报

涵哥

299

主题

2915

回帖

9287

积分

管理员

Rank: 9Rank: 9Rank: 9

积分
9287
发表于 2021-5-11 08:45:00 | 显示全部楼层
1gggddd 发表于 2021-5-9 23:23
没有注意，使用了救援模式，命令清空了JFFS空间，恢复了出厂模式，此问题没有再现。
但又发现了新问题， ...

出现这个log是由于LAN端的连线数很大造成的，可能和你的矿机有关系
可以通过telnet执行以下指令
nvram set ct_expect_max=200
nvram commit
reboot
回复 支持 反对

使用道具 举报

1gggddd

8

主题

32

回帖

154

积分

注册会员

Rank: 2

积分
154
 楼主| 发表于 2021-5-11 21:03:22 | 显示全部楼层
涵哥 发表于 2021-5-11 08:45
出现这个log是由于LAN端的连线数很大造成的，可能和你的矿机有关系
可以通过telnet执行以下指令
nvram se ...

感谢，请问ct_expect_max值的大小是怎么计算得来的。
回复 支持 反对

使用道具 举报

1gggddd

8

主题

32

回帖

154

积分

注册会员

Rank: 2

积分
154
 楼主| 发表于 2021-5-11 22:09:16 | 显示全部楼层
本帖最后由 1gggddd 于 2021-5-11 22:11 编辑
涵哥 发表于 2021-5-11 08:45
出现这个log是由于LAN端的连线数很大造成的，可能和你的矿机有关系
可以通过telnet执行以下指令
nvram se ...

按你说的命令修改以后 ，主题问题再现：
May 11 21:54:18 rc_service: httpd 6511:notify_rc restart_wireless
May 11 21:54:19 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x1
May 11 21:54:19 kernel: bcm63xx_nand ff801800.nand: intfc status f80000e0
May 11 21:54:21 wlceventd: wlceventd Start...
May 11 21:54:32 roamast: ROAMING Start...……
May 11 22:06:09 kernel: SHN Release Version: 2.0.1 851496c
May 11 22:06:09 kernel: UDB Core Version: 0.2.18
May 11 22:06:10 kernel: sizeof forward pkt param = 280
May 11 22:06:10 BWDPI: fun bitmap = 3
May 11 22:08:24 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x1
May 11 22:08:24 kernel: bcm63xx_nand ff801800.nand: intfc status f80000e0
回复 支持 反对

使用道具 举报

涵哥

299

主题

2915

回帖

9287

积分

管理员

Rank: 9Rank: 9Rank: 9

积分
9287
发表于 2021-5-12 08:51:05 | 显示全部楼层
1gggddd 发表于 2021-5-11 22:09
按你说的命令修改以后 ，主题问题再现：
May 11 21:54:18 rc_service: httpd 6511:notify_rc restart_wire ...

这个清除JFFS2 partition即可，直接reset或者通过telnet进行如下指令
# mtd_erase_misc2
# reboot
回复 支持 反对

使用道具 举报

1gggddd

8

主题

32

回帖

154

积分

注册会员

Rank: 2

积分
154
 楼主| 发表于 2021-5-12 16:44:43 | 显示全部楼层
涵哥 发表于 2021-5-12 08:51
这个清除JFFS2 partition即可，直接reset或者通过telnet进行如下指令
# mtd_erase_misc2
# reboot

感谢你的解答，
感谢，请问ct_expect_max值的大小是怎么计算得来的，有没有上限或者下限
回复 支持 反对

使用道具 举报

1gggddd

8

主题

32

回帖

154

积分

注册会员

Rank: 2

积分
154
 楼主| 发表于 2021-5-12 21:23:19 | 显示全部楼层
涵哥 发表于 2021-5-11 08:45
出现这个log是由于LAN端的连线数很大造成的，可能和你的矿机有关系
可以通过telnet执行以下指令
nvram se ...

问题依旧。
May 12 20:34:47 kernel: nf_conntrack: expectation table full
May 12 20:34:47 kernel: nf_conntrack: expectation table full
May 12 20:35:02 miniupnpd[1379]: removed 15 unused rules
May 12 20:45:51 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x1
May 12 20:45:51 kernel: bcm63xx_nand ff801800.nand: intfc status f80000e0
May 12 20:51:07 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x4
May 12 20:51:07 kernel: bcm63xx_nand ff801800.nand: intfc status c80000e0
May 12 20:55:03 miniupnpd[1379]: removed 14 unused rules
May 12 20:58:38 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x1
May 12 20:58:38 kernel: bcm63xx_nand ff801800.nand: intfc status f80000e0
May 12 21:11:28 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x1
May 12 21:11:28 kernel: bcm63xx_nand ff801800.nand: intfc status f80000e0
回复 支持 反对

使用道具 举报

发表于 2022-3-14 14:04:49 | 显示全部楼层
涵哥 发表于 2021-5-11 08:45
出现这个log是由于LAN端的连线数很大造成的，可能和你的矿机有关系
可以通过telnet执行以下指令
nvram se ...

原来我的86也有类似的问题

我记得原来有显示和设置连接数的地方，现在找不到了，还是说ml版本才有这功能
回复 支持 反对

使用道具 举报

下一页 »
12下一页
返回列表 发新帖
高级模式
B Color Image Link Quote Code Smilies
您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

关闭

站长推荐上一条 /1 下一条

快速回复 返回列表 搜索 官方QQ群
×

秒后自动关闭

小黑屋|手机版|Archiver|华硕网络产品技术交流平台 ( 苏ICP备16010857号-1 )苏公网安备 32050502000499号

GMT+8, 2024-4-20 04:38 , Processed in 0.039463 second(s), 31 queries .

Powered by Discuz! X3.4

© 2001-2023 Discuz! Team.

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