piknew Posted June 26, 2018 Posted June 26, 2018 Dear All, today my Opi PC stoppped responding. But I think it is not totally "dead". From other machine I did: root@PKSERVER:~# ssh -vvv pkbackup OpenSSH_6.7p1 Debian-5+deb8u4, OpenSSL 1.0.1t 3 May 2016 debug1: Reading configuration data /etc/ssh/ssh_config debug3: checking match for 'exec "/etc/ssh/pkdata.sh %n"' host pkbackup debug1: Executing command: '/etc/ssh/pkdata.sh pkbackup' debug1: permanently_drop_suid: 0 debug3: command returned status 1 debug1: /etc/ssh/ssh_config line 18: no match 'exec "/etc/ssh/pkdata.sh pkbackup"' debug3: match not found debug1: /etc/ssh/ssh_config line 21: Applying options for * debug2: ssh_connect: needpriv 0 ......................... a lot of lines ................................. debug1: Offering RSA public key: /root/.ssh/id_rsa debug3: send_pubkey_test debug2: we sent a publickey packet, wait for reply debug1: Server accepts key: pkalg ssh-rsa blen 279 debug2: input_userauth_pk_ok: fp cc:d4:2d:54:9e:33:87:8e:ef:e0:b1:e3:dc:25:46:67 debug3: sign_and_send_pubkey: RSA cc:d4:2d:54:9e:33:87:8e:ef:e0:b1:e3:dc:25:46:67 debug1: Authentication succeeded (publickey). Authenticated to pkbackup ([192.168.10.220]:22). debug1: channel 0: new [client-session] debug3: ssh_session2_open: channel_new: 0 debug2: channel 0: send open debug1: Requesting no-more-sessions@openssh.com debug1: Entering interactive session. At this moment this is the last message from ssh. Quite interesting that CTRL+C is not working (session is already on remote machine side). Please note that previously I provided stacktrace which was registered in log: It was related to network driver (dwmac-sun8i): [44339.175188] dwmac-sun8i 1c30000.ethernet: packet dropped [55271.062033] kworker/0:0H: page allocation failure: order:0, mode:0x1080020(GFP_ATOMIC), nodemask=(null) [55271.062702] kworker/0:0H cpuset=/ mems_allowed=0 [55271.063225] CPU: 0 PID: 21267 Comm: kworker/0:0H Not tainted 4.14.18-sunxi #24 [55271.063347] Hardware name: Allwinner sun8i Family [55271.063793] Workqueue: xprtiod xs_tcp_data_receive_workfn [55271.064500] [<c010db15>] (unwind_backtrace) from [<c010a0d9>] (show_stack+0x11/0x14) [55271.064924] [<c010a0d9>] (show_stack) from [<c0868f69>] (dump_stack+0x69/0x78) Maybe this is the way (not kernel itself)? EDIT (from RPI SBC): https://github.com/raspberrypi/linux/issues/2482 Similar issue (I am also using nfs as primary "storage"). In my case also there was "packet dropped". Please note https://github.com/6by9/linux/commit/d9941e07f7b8d34a9404374c0e583ba6e5f25da9 Note to moderator: if this is wrong way - please delete/move it to "trash". EDIT2: I noticed difference to TSO between default and mainline in bonding driver, but no difference in eth interface. default: root@PKSERVER:~# ethtool -k bond0 | grep segmentationtcp-segmentation-offload: off tx-tcp-segmentation: off [requested on] tx-tcp-ecn-segmentation: off [requested on] tx-tcp6-segmentation: off [requested on] generic-segmentation-offload: on tx-fcoe-segmentation: off [fixed] root@PKSERVER:~# ethtool -k eth0 | grep segmentation tcp-segmentation-offload: off tx-tcp-segmentation: off [fixed] tx-tcp-ecn-segmentation: off [fixed] tx-tcp6-segmentation: off [fixed] generic-segmentation-offload: on tx-fcoe-segmentation: off [fixed] root@PKSERVER:~# mainline: root@PKOTHER:~# ethtool -k bond0 | grep segmentation Cannot get device udp-fragmentation-offload settings: Operation not supportedtcp-segmentation-offload: on tx-tcp-segmentation: on tx-tcp-ecn-segmentation: on tx-tcp-mangleid-segmentation: on tx-tcp6-segmentation: on generic-segmentation-offload: on tx-fcoe-segmentation: off [fixed] tx-gre-segmentation: on tx-gre-csum-segmentation: on tx-ipxip4-segmentation: on tx-ipxip6-segmentation: on tx-udp_tnl-segmentation: on tx-udp_tnl-csum-segmentation: on tx-sctp-segmentation: off [fixed] tx-esp-segmentation: off [fixed] root@PKOTHER:~# ethtool -k eth0 | grep segmentation Cannot get device udp-fragmentation-offload settings: Operation not supported tcp-segmentation-offload: off tx-tcp-segmentation: off [fixed] tx-tcp-ecn-segmentation: off [fixed] tx-tcp-mangleid-segmentation: off [fixed] tx-tcp6-segmentation: off [fixed] generic-segmentation-offload: on tx-fcoe-segmentation: off [fixed] tx-gre-segmentation: off [fixed] tx-gre-csum-segmentation: off [fixed] tx-ipxip4-segmentation: off [fixed] tx-ipxip6-segmentation: off [fixed] tx-udp_tnl-segmentation: off [fixed] tx-udp_tnl-csum-segmentation: off [fixed] tx-sctp-segmentation: off [fixed] tx-esp-segmentation: off [fixed] root@PKOTHER:~# For device "pkbackup" ("frozen") I am using 1GBit USB eth1, but until I get physical access to this device - I am not able to confirm what are the settings for this interface).
piknew Posted June 27, 2018 Author Posted June 27, 2018 My plan is (on Friday - when I get physical access to device): 1. Unplug network cable and plug in into built-in eth0 port if successful then get logs/dmesg etc. 2. Move the device neat to PC (or laptop near to this board), connect by UART and try to login (of course I know that it is without initial login prompt). Fortunately I am using portable UPS, so there should be no issue. Any more suggestions? As topic is basically related to other (unfortunately other users the do not confirmed if connect by ssh is working (without debug option it seems that connection is not done at all).
Recommended Posts