您尚未登录。

楼主 # 2023-12-12 16:50:56

我思故我在
会员
注册时间: 2019-09-03
已发帖子: 244
积分: 243.5

V3s 执行 iperf3 满负荷测试两小时挂了

[  5] 7298.03-7299.06 sec  8.75 MBytes  71.4 Mbits/sec    0    232 KBytes
[  5] 7299.06-7300.09 sec  8.75 MBytes  71.4 Mbits/sec    0    232 KBytes
[  5] 7300.09-7301.12 sec  8.75 MBytes  71.1 Mbits/sec    0    232 KBytes
[  5] 7301.12-7302.00 sec  7.50 MBytes  71.2 Mbits/sec    0    232 KBytes
[  5] 7302.00-7303.03 sec  8.75 MBytes  71.3 Mbits/sec    0    232 KBytes
[  5] 7303.03-7304.06 sec  8.75 MBytes  71.3 Mbits/sec    0    232 KBytes
[  5] 7304.06-7305.09 sec  8.75 MBytes  71.1 Mbits/sec    0    232 KBytes
[  5] 7305.09-7306.13 sec  8.75 MBytes  71.0 Mbits/sec    0    232 KBytes
[  5] 7306.13-7307.02 sec  7.50 MBytes  70.8 Mbits/sec    0    232 KBytes
[  5] 7307.02-7308.05 sec  8.75 MBytes  71.0 Mbits/sec    0    232 KBytes
[  5] 7308.05-7309.08 sec  8.75 MBytes  71.1 Mbits/sec    0    232 KBytes
[  5] 7309.08-7310.11 sec  8.75 MBytes  71.4 Mbits/sec    0    232 KBytes
[  5] 7310.11-7311.14 sec  8.75 MBytes  71.1 Mbits/sec    0    232 KBytes
[  5] 7311.14-7312.02 sec  7.50 MBytes  71.3 Mbits/sec    0    232 KBytes
[  5] 7312.02-7313.06 sec  8.75 MBytes  70.9 Mbits/sec    0    232 KBytes
[ 7458.902753] Unable to handle kernel paging request at virtual address c00d1bc8
[ 7458.910796] pgd = c2690000
[ 7458.913789] [c00d1bc8] *pgd=4000041e(bad)
[ 7458.918245] Internal error: Oops: 8000000d [#1] PREEMPT ARM
[ 7458.924418] Modules linked in:
[ 7458.927813] CPU: 0 PID: 798 Comm: iperf3 Tainted: G    B           4.9.118 #162
[ 7458.935906] Hardware name: sun8iw8
[ 7458.939671] task: c24ee340 task.stack: c268c000
[ 7458.944692] PC is at 0xc00d1bc8
[ 7458.948183] LR is at deactivate_slab+0xbc/0x488
[ 7458.953199] pc : [<c00d1bc8>]    lr : [<c01d1bc8>]    psr: 60000093
[ 7458.953199] sp : c268dcd0  ip : c263e1bc  fp : c3bc27c0
[ 7458.965913] r10: 800c000c  r9 : c263f440  r8 : 800c000b
[ 7458.971698] r7 : c263ecc0  r6 : c34944c0  r5 : c268c000  r4 : c3451680
[ 7458.978925] r3 : c24ee340  r2 : c268dcc0  r1 : 00000000  r0 : 00000001
[ 7458.986156] Flags: nZCv  IRQs off  FIQs on  Mode SVC_32  ISA ARM  Segment none
[ 7458.994154] Control: 10c5387d  Table: 42690059  DAC: 00000051
[ 7459.000516]
[ 7459.000516] PC: 0xc00d1b48:
[ 7459.005240] 1b48  e1a07002 ebffbb0c e5903008 e1a08000 e3130004 1a000011 e5983008 e3130002
[ 7459.014328] 1b68  0a00001e e59f107c e1a00005 e08f1001 ebffbf6a e2505000 03e0400b 0a00000f
[ 7459.023414] 1b88  e1a02007 e1a01006 ebffbf9e e2504000 0a00000c e1a00005 ebffb9c5 ea000007
[ 7459.032500] 1ba8  e59f1044 e1a03007 e1a02006 e1a00005 e08f1001 ebffbfa5 e2504000 aaffffe5
[ 7459.041586] 1bc8  e1a00004 e8bd81f0 e5950004 ebffc237 e2800001 e5850008 e3500001 9affffec
[ 7459.050672] 1be8  e3a04000 eafffff5 00016ba9 00018cc4 e92d43f7 e1a05000 e1a08001 e1a07002
[ 7459.059759] 1c08  e1a09003 ebffbadc e5904008 e1a06000 e2144004 0a000007 e59f10c0 e1a03007
[ 7459.068846] 1c28  e1a02008 e1a00005 e08f1001 ebffbf87 e2504000 ba000003 e5963008 e3130002
[ 7459.077934]
[ 7459.077934] LR: 0xc01d1b48:
[ 7459.082657] 1b48  0a000003 e5962014 e7979002 e3590000 1a00004a e1a0300d e3c39d7f e3a02000
[ 7459.091744] 1b68  e3c9903f e1a08002 e59ba00c e59b3008 e35a0000 e58da03c e58d3000 ba000049
[ 7459.100830] 1b88  e7f001f2 e59d801c e10f2000 e3120080 1a000000 e7f001f2 e59b2014 e3120001
[ 7459.109916] 1ba8  0a000003 e59f13d8 e1a0000b ebff8d81 e7f001f2 e3a00001 e58d3000 ebfd8905
[ 7459.119003] 1bc8  e59b2008 e59d3000 e1530002 1a00001f e59b200c e15a0002 1a00001c e58d805c
[ 7459.128089] 1be8  e1a01fa8 e5db200f e1cb80bc e7ee8858 e7c72391 e5cb200f e1db20be e58b7008
[ 7459.137175] 1c08  e7ce2018 e1cb20be e59b2014 e3120001 0a000003 e59f1368 e1a0000b ebff8d65
[ 7459.146261] 1c28  e7f001f2 e3a00001 ebfd892e e5952004 e3520000 1a000003 e5952000 e3120002
[ 7459.155349]

最近编辑记录 我思故我在 (2023-12-12 16:51:43)

离线

#1 2023-12-12 16:53:18

拉轰的脚踏车
会员
注册时间: 2020-03-20
已发帖子: 288
积分: 222

Re: V3s 执行 iperf3 满负荷测试两小时挂了

您的Linux内核出现了Oops,这是一种严重错误,表明有某些东西引起了内核崩溃。具体原因可能包括硬件问题、驱动程序错误或者内核本身的bug等。

在提供的日志信息中可以看到,错误发生在deactivate_slab+0xbc/0x488,这是内存管理相关的函数。可能的原因包括内存不足、内存损坏,或者可能是某个设备驱动试图访问一个不应该访问的内存区域。

要解决这个问题,你可能需要:

① 检查硬件,尤其是RAM,是否有问题。可以使用诸如memtest86+之类的工具进行内存测试。
② 更新系统和内核到最新版本,如果可能的话。可能存在的内核bug在新版本中可能已经被修复。
③ 检查并更新设备驱动。如果问题与特定的硬件设备或驱动有关,那么更新或重新安装驱动可能有助于解决问题。
④ 如果以上步骤都无效,您可能需要深入跟踪和调试内核以找到确切问题,这可能需要相当熟练的Linux和编程知识。
另外,注意您在运行哪些程序或加载哪些模块时出现了这个错误,这可能会帮助您确定问题的来源。在这个例子中,iperf3进程正在运行当错误发生,可能需要检查与其相关的网络设备或驱动。

离线

#3 2023-12-13 17:25:43

memory
会员
注册时间: 2021-08-11
已发帖子: 483
积分: 459

Re: V3s 执行 iperf3 满负荷测试两小时挂了

29bcd61eb6f3602181ae930c85a3864.png

[  5] 57078.13-57079.02 sec  7.50 MBytes  71.0 Mbits/sec    0    231 KBytes
[  5] 57079.02-57080.05 sec  8.75 MBytes  71.4 Mbits/sec    0    231 KBytes
[57179.206859] Unable to handle kernel NULL pointer dereference at virtual address 0000005a
[57179.215875] pgd = c25d8000
[57179.218873] [0000005a] *pgd=4269e835, *pte=00000000, *ppte=00000000
[57179.225847] Internal error: Oops: 801 [#1] PREEMPT ARM
[57179.231546] Modules linked in:
[57179.234942] CPU: 0 PID: 800 Comm: iperf3 Tainted: G    B           4.9.118 #162
[57179.243045] Hardware name: sun8iw8
[57179.246814] task: c24fb840 task.stack: c24e2000
[57179.251855] PC is at gic_handle_irq+0x40/0x64
[57179.256685] LR is at __irq_svc+0x6c/0xa8
[57179.261033] pc : [<c0101490>]    lr : [<c010b00c>]    psr: 80000193
[57179.261033] sp : c24e3c58  ip : c0111a64  fp : c3467158
[57179.273765] r10: 00000040  r9 : c24e2000  r8 : c0a03cb0
[57179.279557] r7 : c24e3c70  r6 : f1c83000  r5 : c0a03350  r4 : f1c82000
[57179.286794] r3 : c24e3c70  r2 : 00000001  r1 : 00000072  r0 : c340e340
[57179.294035] Flags: Nzcv  IRQs off  FIQs on  Mode SVC_32  ISA ARM  Segment none
[57179.302043] Control: 10c5387d  Table: 425d8059  DAC: 00000051
[57179.308413]
[57179.308413] PC: 0xc0101410:
[57179.313143] 1410  e5943000 e5933010 f57ff04f e3130001 08bd8070 e1a03005 e3a02001 e5940004
[57179.322243] 1430  eb01192e e5943000 e5931000 f57ff04f e1b01121 1afffff6 e8bd8070 c0b5db90
[57179.331342] 1450  e59f3058 e92d41f0 e1a07000 e593408c e1a05003 e2846a01 e594300c e7e91053
[57179.340440] 1470  e2412010 e3520ffb 2a000006 ea000000 e5843010 e1a03007 e3a02001 e59506a4
[57179.349537] 1490  e9011916 eafffff3 e351000f 88bd81f0 e5843010 eaffffef e5863000 eaffffed
[57179.358635] 14b0  c0a03350 00000000 e92d4ff0 e24dd024 e59f41cc e59f51cc e59f71cc e5943000
[57179.367733] 14d0  e2833001 e58d3014 e1a0300d e0033005 e593300c e593200c e58d200c e3c22b02
[57179.376830] 14f0  e583200c eb084d78 e7976300 e3a00c01 eb00cab6 e3a0300a e58d3010 e1a0300d
[57179.385930]
[57179.385930] LR: 0xc010af
[57180.590468] 3fe0: bef89c10 bef89c00 b6eea130 b6ee9600 60000010 00000005 43bfc861 43bfcc61
[57180.599556] [<c0101490>] (gic_handle_irq) from [<c010b00c>] (__irq_svc+0x6c/0xa8)
[57180.607854] Exception stack(0xc24e3c70 to 0xc24e3cb8)
[57180.613454] 3c60:                                     00000001 00000008 60000113 00000111
[57180.622525] 3c80: c0a3bf00 c24e3cc8 00000001 c24e3cd0 c0a03cb0 0000012b 00000040 c3467158
[57180.631595] 3ca0: c0111a64 c24e3cc0 c03eb310 c04e62a8 20000113 ffffffff
[57180.638946] [<c010b00c>] (__irq_svc) from [<c04e62a8>] (net_rx_action+0x128/0x270)
[57180.647347] [<c04e62a8>] (net_rx_action) from [<c0101650>] (__do_softirq+0x198/0x208)
[57180.656042] [<c0101650>] (__do_softirq) from [<c0119560>] (irq_exit+0x90/0xf4)
[57180.664067] [<c0119560>] (irq_exit) from [<c0147978>] (__handle_domain_irq+0x88/0xcc)
[57180.672755] [<c0147978>] (__handle_domain_irq) from [<c0101494>] (gic_handle_irq+0x44/0x64)
[57180.682022] [<c0101494>] (gic_handle_irq) from [<c010b00c>] (__irq_svc+0x6c/0xa8)
[57180.690318] Exception stack(0xc24e3d88 to 0xc24e3dd0)
[57180.695920] 3d80:                   c27e3ca0 b6bda904 00003c70 71f8bfea f8b0315b 67dee951
[57180.704991] 3da0: 38b87ef5 d0533330 39a482bf c24e3f08 00000051 00017c50 59b8e5d8 c24e3ddc
[57180.714060] 3dc0: 1331556d c02f8e1c 20000013 ffffffff
[57180.719671] [<c010b00c>] (__irq_svc) from [<c02f8e1c>] (arm_copy_from_user+0x60/0x3a4)
[57180.728464] [<c02f8e1c>] (arm_copy_from_user) from [<c030b130>] (copy_from_iter+0x27c/0x338)
[57180.737831] [<c030b130>] (copy_from_iter) from [<c05283b0>] (tcp_sendmsg+0x968/0xb1c)
[57180.746526] [<c05283b0>] (tcp_sendmsg) from [<c04cec2c>] (sock_sendmsg+0x14/0x24)
[57180.754830] [<c04cec2c>] (sock_sendmsg) from [<c04cecc0>] (sock_write_iter+0x84/0xac)
[57180.763524] [<c04cecc0>] (sock_write_iter) from [<c01dc9bc>] (__vfs_write+0xe0/0x108)
[57180.772213] [<c01dc9bc>] (__vfs_write) from [<c01dd64c>] (vfs_write+0xb8/0x18c)
[57180.780321] [<c01dd64c>] (vfs_write) from [<c01de490>] (SyS_write+0x3c/0x74)
[

我的也挂了?

离线

#4 2023-12-13 21:06:23

musich
会员
注册时间: 2018-04-17
已发帖子: 249
积分: 281

Re: V3s 执行 iperf3 满负荷测试两小时挂了

原来V3S的网口可以跑这么快,  我的最大才三十多M,

离线

#5 2023-12-14 18:06:45

4610
会员
注册时间: 2022-10-09
已发帖子: 101
积分: 82

Re: V3s 执行 iperf3 满负荷测试两小时挂了

主线上挺稳定的,再挂一晚看看

CPU 75% 2T2R 上下行均稳定90M 过了两级交换机

iperf3 -c XXXX -Z -P2 --bidir -t 0

untitled.png

最近编辑记录 4610 (2023-12-14 18:15:37)

离线

#6 2023-12-15 06:37:40

musich
会员
注册时间: 2018-04-17
已发帖子: 249
积分: 281

Re: V3s 执行 iperf3 满负荷测试两小时挂了

4610 说:

主线上挺稳定的,再挂一晚看看

CPU 75% 2T2R 上下行均稳定90M 过了两级交换机

iperf3 -c XXXX -Z -P2 --bidir -t 0

https://whycan.com/files/members/10513/untitled.png

这个NB, 90多M, 快跑满了.

离线

#7 2023-12-15 10:16:33

wswh2o
会员
注册时间: 2022-07-07
已发帖子: 13
积分: 8

Re: V3s 执行 iperf3 满负荷测试两小时挂了

大包很容易跑满线速

离线

#8 2023-12-15 13:45:59

4610
会员
注册时间: 2022-10-09
已发帖子: 101
积分: 82

Re: V3s 执行 iperf3 满负荷测试两小时挂了

musich 说:
4610 说:

主线上挺稳定的,再挂一晚看看

CPU 75% 2T2R 上下行均稳定90M 过了两级交换机

iperf3 -c XXXX -Z -P2 --bidir -t 0

https://whycan.com/files/members/10513/untitled.png

这个NB, 90多M, 快跑满了.

一整天了没断,应该v3s硬件本身是没问题的

上下行各90M,瓶颈在交换机

最近编辑记录 4610 (2023-12-15 14:22:04)

离线

页脚

工信部备案:粤ICP备20025096号 Powered by FluxBB

感谢为中文互联网持续输出优质内容的各位老铁们。 QQ: 516333132, 微信(wechat): whycan_cn (哇酷网/挖坑网/填坑网) service@whycan.cn