Firefly开源社区

标题: 求工程师解决一下挂载nfs,电脑上网会卡死问题 [打印本页]

作者: tswsblack 时间: 2018-2-7 14:17
标题: 求工程师解决一下挂载nfs,电脑上网会卡死问题
本人在使用rk3399,用的是官方给的ubuntu16.04系统，单用是好的。因为是用于办公，所以进行了集群搭建，服务器是pc版ubuntu16.04系统，用的是nis集群服务，是用nfs将服务器home分区挂到了rk3399的系统上，集群搭建成功，开始上网的时候，浏览器在打开三个网页左右就卡死了，一开始还可以进入字符页面，过一两分钟整个开发板就死机掉了。以前在用rk3288的时候ubuntu14.04也会卡死，但后来将ubuntu14server的boot分区进行替换后，解决了这个问题，但是rk3399的却不行。3288的boot分区可以进行分解但3399的却不行，官方能不能测试一下帮忙解决一下这个问题，同时能不能提供一些解压引导和内核分区的工具。
服务器采用pc版ubuntu14.04,ubuntu16.04以及centos6.9等都试过了，集群可以搭建成功，但是浏览器会出现卡机问题，应该是与nfs功能有关，远程挂载home目录后，上网或者往里面拷东西都会出现死机情况，nfs不是linux最正常的功能吗？更何况板子存储不大一般都会用到nfs的，求解决

作者: leung先森 时间: 2018-2-7 16:07
要描述一下流程，操作细节，提供log，不然别人没法帮你分析。
三个网页就卡死，是浏览文件吗？还是正常上网？

作者: luvings 时间: 2018-2-7 16:15

固件是1130，一边用浏览器播放 nfs 4K 视频，一边看 youku ，一边往板子拷贝视频，没卡死

作者: tswsblack 时间: 2018-2-8 08:49

luvings 发表于 2018-2-7 16:15
固件是1130，一边用浏览器播放 nfs 4K 视频，一边看 youku ，一边往板子拷贝视频，没卡死

我用的也是1130，但我是挂载的服务器home目录，用Nis帐号登陆的

作者: tswsblack 时间: 2018-2-8 08:50

leung先森发表于 2018-2-7 16:07
要描述一下流程，操作细节，提供log，不然别人没法帮你分析。
三个网页就卡死，是浏览文件吗？还是正常上 ...

就是正常上网浏览网页，log放下面

作者: tswsblack 时间: 2018-2-8 08:52
Feb  8 08:22:13 pc3 kernel: [ 59.875722] Final fw_path=/system/etc/firmware/fw_bcm4356a2_ag.bin
Feb  8 08:22:13 pc3 kernel: [ 59.875728] Final nv_path=/system/etc/firmware/nvram_ap6356.txt
Feb  8 08:22:13 pc3 kernel: [ 59.875733] Final conf_path=/system/etc/firmware/config.txt
Feb  8 08:22:13 pc3 kernel: [ 59.877829] dhdsdio_download_code_file: Open firmware file failed /system/etc/firmware/fw_bcm4356a2_ag.bin
Feb  8 08:22:13 pc3 kernel: [ 59.877846] _dhdsdio_download_firmware: dongle image file download failed
Feb  8 08:22:13 pc3 kernel: [ 59.878294] dhd_bus_devreset Failed to download binary to the dongle
Feb  8 08:22:13 pc3 kernel: [ 59.878316] dhd_net_bus_devreset: dhd_bus_devreset: -35
Feb  8 08:22:13 pc3 kernel: [ 59.878331] dhd_wl_ioctl: returning as busstate=0
Feb  8 08:22:13 pc3 kernel: [ 59.878345] dhd_net_bus_devreset: dhd_bus_devreset: -35
Feb  8 08:22:13 pc3 kernel: [ 59.879393] wifi_platform_set_power = 0
Feb  8 08:22:13 pc3 kernel: [ 59.879408] ======== PULL WL_REG_ON(-1) LOW! ========
Feb  8 08:22:13 pc3 kernel: [ 59.879421] [WLAN_RFKILL]: rockchip_wifi_power: 0
Feb  8 08:22:13 pc3 kernel: [ 59.879443] [WLAN_RFKILL]: wifi shut off power.
Feb  8 08:22:13 pc3 kernel: [ 59.879454] wl_android_wifi_on: Failed
Feb  8 08:22:13 pc3 kernel: [ 59.879465] dhd_open : wl_android_wifi_on failed (-35)
Feb  8 08:22:13 pc3 kernel: [ 59.879478] dhd_stop: Enter ffffffc0ef07c000
Feb  8 08:22:13 pc3 kernel: [ 59.879488] wl_android_wifi_off in 1
Feb  8 08:22:13 pc3 kernel: [ 59.879499] wl_android_wifi_off in 2: g_wifi_on=0, on_failure=1
Feb  8 08:22:13 pc3 kernel: [ 59.879511] dhd_wl_ioctl: returning as busstate=0
Feb  8 08:22:13 pc3 kernel: [ 59.879522] dhd_net_bus_devreset: dhd_bus_devreset: -35
Feb  8 08:22:13 pc3 kernel: [ 59.879609] sdioh_disable_func_intr: error for read SDIO_CCCR_IENx : 0xffffff92
Feb  8 08:22:13 pc3 kernel: [ 59.879624] wifi_platform_set_power = 0
Feb  8 08:22:13 pc3 kernel: [ 59.879634] ======== PULL WL_REG_ON(-1) LOW! ========
Feb  8 08:22:13 pc3 kernel: [ 59.879645] [WLAN_RFKILL]: rockchip_wifi_power: 0
Feb  8 08:22:13 pc3 kernel: [ 59.879660] [WLAN_RFKILL]: wifi shut off power.
Feb  8 08:22:13 pc3 kernel: [ 59.879668] wl_android_wifi_off out
Feb  8 08:22:13 pc3 wpa_supplicant[483]: Could not set interface wlan0 flags (UP): Operation not permitted
Feb  8 08:22:13 pc3 kernel: [ 59.896947] dhd_stop: Exit
Feb  8 08:22:13 pc3 kernel: [ 59.896964] dhd_open: Exit ret=-1
Feb  8 08:22:13 pc3 NetworkManager[332]: <error> [1518049333.2706] sup-iface[0x17a41c30,wlan0]: error adding interface: wpa_supplicant couldn't grab this interface.
Feb  8 08:22:13 pc3 wpa_supplicant[483]: WEXT: Could not set interface 'wlan0' UP
Feb  8 08:22:13 pc3 NetworkManager[332]: <info>  [1518049333.2708] device (wlan0): supplicant interface state: starting -> down
Feb  8 08:22:13 pc3 wpa_supplicant[483]: wlan0: Failed to initialize driver interface
Feb  8 08:22:13 pc3 NetworkManager[332]: <info>  [1518049333.2710] device (wlan0): supplicant interface keeps failing, giving up
Feb  8 08:22:24 pc3 rsyslogd-2007: action 'action 9' suspended, next retry is Thu Feb  8 08:22:54 2018 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
Feb  8 08:26:16 pc3 kernel: [  303.142995] EXT4-fs (mmcblk1p6): error count since last fsck: 197
Feb  8 08:26:16 pc3 kernel: [  303.143077] EXT4-fs (mmcblk1p6): initial error at time 1517905886: __ext4_new_inode:1059
Feb  8 08:26:16 pc3 kernel: [  303.143103] EXT4-fs (mmcblk1p6): last error at time 1518049277: ext4_mb_generate_buddy:758
Feb  8 08:26:16 pc3 rsyslogd-2007: action 'action 9' suspended, next retry is Thu Feb  8 08:26:46 2018 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
Feb  8 08:26:21 pc3 kernel: [  307.750976] nfs: server node01 not responding, still trying
Feb  8 08:26:21 pc3 kernel: [  307.751011] nfs: server node01 not responding, still trying
Feb  8 08:26:22 pc3 kernel: [  308.910990] nfs: server node01 not responding, still trying
Feb  8 08:26:24 pc3 kernel: [  310.914956] nfs: server node01 not responding, still trying
Feb  8 08:26:24 pc3 kernel: [  311.110958] nfs: server node01 not responding, timed out
Feb  8 08:26:24 pc3 kernel: [  311.111191] nfs: server node01 not responding, still trying
Feb  8 08:26:24 pc3 kernel: [  311.111214] nfs: server node01 not responding, still trying
Feb  8 08:26:24 pc3 kernel: [  311.111223] nfs: server node01 not responding, still trying
Feb  8 08:26:24 pc3 kernel: [  311.111230] nfs: server node01 not responding, still trying
Feb  8 08:27:40 pc3 rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="436" x-info="http://www.rsyslog.com"] start
Feb  8 08:27:40 pc3 rsyslogd-2222: command 'KLogPermitNonKernelFacility' is currently not permitted - did you already set it via a RainerScript command (v6+ config)? [v8.16.0 try http://www.rsyslog.com/e/2222 ]
Feb  8 08:27:40 pc3 rsyslogd: rsyslogd's groupid changed to 110
Feb  8 08:27:40 pc3 rsyslogd: rsyslogd's userid changed to 106
Feb  8 08:27:40 pc3 rsyslogd-2039: Could not open output pipe '/dev/xconsole':: No such file or directory [v8.16.0 try http://www.rsyslog.com/e/2039 ]
Feb  8 08:27:40 pc3 systemd[189]: keyboard-setup.service: Failed at step EXEC spawning /usr/bin/loadkeys: No such file or directory
Feb  8 08:27:40 pc3 systemd-modules-load[192]: could not open moddep file '/lib/modules/4.4.77/modules.dep.bin'
Feb  8 08:27:40 pc3 rsyslogd-2007: action 'action 9' suspended, next retry is Thu Feb  8 08:28:10 2018 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
Feb  8 08:27:40 pc3 systemd-modules-load[192]: Failed to lookup alias 'lp': Function not implemented
Feb  8 08:27:40 pc3 systemd-modules-load[192]: could not open moddep file '/lib/modules/4.4.77/modules.dep.bin'
Feb  8 08:27:40 pc3 systemd-modules-load[192]: Failed to lookup alias 'ppdev': Function not implemented
Feb  8 08:27:40 pc3 systemd-modules-load[192]: could not open moddep file '/lib/modules/4.4.77/modules.dep.bin'
Feb  8 08:27:40 pc3 systemd-modules-load[192]: Failed to lookup alias 'parport_pc': Function not implemented
Feb  8 08:27:40 pc3 kernel: [ 0.000000] Booting Linux on physical CPU 0x0
Feb  8 08:27:40 pc3 kernel: [ 0.000000] Initializing cgroup subsys cpuset
Feb  8 08:27:40 pc3 systemd-sysctl[217]: Couldn't write '2' to 'net/ipv6/conf/all/use_tempaddr', ignoring: No such file or directory
Feb  8 08:27:40 pc3 kernel: [ 0.000000] Initializing cgroup subsys cpu
Feb  8 08:27:40 pc3 kernel: [ 0.000000] Initializing cgroup subsys cpuacct
Feb  8 08:27:40 pc3 systemd-sysctl[217]: Couldn't write '2' to 'net/ipv6/conf/default/use_tempaddr', ignoring: No such file or directory
Feb  8 08:27:40 pc3 kernel: [ 0.000000] Linux version 4.4.77 (root@node01) (gcc version 4.9.x-google 20140827 (prerelease) (GCC) ) #6 SMP Sat Feb 3 11:58:10 CST 2018
Feb  8 08:27:40 pc3 kernel: [ 0.000000] Boot CPU: AArch64 Processor [410fd034]
Feb  8 08:27:40 pc3 systemd[231]: console-setup.service: Failed at step EXEC spawning /bin/setupcon: No such file or directory
Feb  8 08:27:40 pc3 kernel: [ 0.000000] Reserved memory: failed to reserve memory for node 'drm-logo@00000000': base 0x0000000000000000, size 0 MiB
大概8点23分开始卡，然后日志里面没有卡这段时间的东西，不足道为什么，从27分开始重启

作者: tswsblack 时间: 2018-2-8 09:49
这是Log截图图片

工作区 1_001.png (392.96 KB, 下载次数: 809)

作者: luvings 时间: 2018-3-16 11:35
有线网络试试

作者: tswsblack 时间: 2018-3-16 13:35

luvings 发表于 2018-3-16 11:35
有线网络试试

用的就是有线网

作者: luxinchun 时间: 2018-3-16 16:52
dts 配置有问题，VDD_LOG电压偏小，造成网络工作不正常。需要重新编译dts。具体见我的帖子。

欢迎光临 Firefly开源社区 (https://dev.t-firefly.com/)