Arch Linux

hast0011

Member

From: South Germany

Registered: 2014-04-29

Posts: 11

ssh connection seems to stop because of suspend mode

as written in subject the ssh connection to my server seems to stop after a few minutes on my fresh linux installation intended to run as a server.
It runs in console mode only, no display, no keyboard, no X.

ssh runs
sftp runs
suddenly it stops

I can quickly connect a keyboard, then it (the ssh connection) comes to live again for a few minutes.
It also resumes by connecting a usb-stick.

I switched of acpi: systemctl disable acpi   No effect
various BIOS-Settings: no effect
install tlp: no effect (tooo many options)

It seems to shut down my network connection if no events from keyboard detected.

pls help since I tried for a few days now without finding anything useful:-(

Last edited by hast0011 (2014-08-03 00:02:10)

Awebb

Member

Registered: 2010-05-06

Posts: 6,321

Re: ssh connection seems to stop because of suspend mode

lspci and lsusb please. Tell us which network adapter you use, if you can. If it is wireless, chances are that the wifi connection falls asleep. I had this problem on my RaspberryPi, it was fixed with the appropriate modprobe option.

hast0011

Member

From: South Germany

Registered: 2014-04-29

Posts: 11

Re: ssh connection seems to stop because of suspend mode

Hello,

thank you for your reply. It´s about the LAN interface since I did not setup wlan yet.
I did not find a good solution here only a workaround. So here is the data:

[root@shuttle ~]# lspci
00:00.0 Host bridge: VIA Technologies, Inc. VT8375 [KM266/KL266] Host Bridge
00:01.0 PCI bridge: VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP]
00:0a.0 USB controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 62)
00:0a.1 USB controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 62)
00:0a.2 USB controller: VIA Technologies, Inc. USB 2.0 (rev 65)
00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8100/8101L/8139 PCI Fast Ethernet Adapter (rev 10)
00:0c.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller (rev 46)
00:10.0 USB controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
00:10.1 USB controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
00:10.2 USB controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
00:10.3 USB controller: VIA Technologies, Inc. USB 2.0 (rev 82)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50)
01:00.0 VGA compatible controller: S3 Graphics Ltd. VT8375 [ProSavage8 KM266/KL266]

[root@shuttle ~]# lsusb
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 13fd:1840 Initio Corporation INIC-1608 SATA bridge
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

And my workaround for now:

[root@shuttle ~]# crontab -l
*/2 * * * * expect -c 'send alive'

Last edited by hast0011 (2014-08-07 17:49:13)