Hello Andres, First your description of my scenario is quite accurate:
1. PowerNap is configured to listen to a TCP Monitor (port 22). 2. Powernap became idled and after 300 seconds of inactivity and performed the action. 2. The action is *powersave* that run all the scripts in /etc/pm/power.d/ and /usr/lib/pm-utils/power.d/ to reduce power consumption while running the machine. Including setting the NIC from 1000Mb/s to 100Mb/s 3. I attempt to SSH into the machine, PowerNap see the connection on port 22 and takes recover action by running the scripts again. Including setting the NIC back from 100Mb/s to 1000Mb/s 4. That speed transition make my NIC to drop packets for about ~18 sec, making the SSH session to fail. As requested you will find attached in pm-logs-config.tar.gz - /etc/powernap/config - /var/log/powernap.log - /var/log/powernap.err (empty) - /var/log/pm-powersave.log* the logs were taken with DEBUG=3 in the config I have captured the output of ethtool eth0 and it shows exactly what you describe, as intended. As a further piece of information, here is the output of the ping command directed to the affected machine just when PowerNap set the NIC from 100Mb/s to 1000Mb/s (triggered by a SSH logging attempt): PING perenold.nat.mberard.eu (192.168.0.1) 56(84) bytes of data. 64 bytes from perenold.nat.mberard.eu (192.168.0.1): icmp_req=1 ttl=64 time=0.287 ms 64 bytes from perenold.nat.mberard.eu (192.168.0.1): icmp_req=2 ttl=64 time=0.188 ms 64 bytes from perenold.nat.mberard.eu (192.168.0.1): icmp_req=3 ttl=64 time=0.302 ms 64 bytes from perenold.nat.mberard.eu (192.168.0.1): icmp_req=4 ttl=64 time=0.200 ms 64 bytes from perenold.nat.mberard.eu (192.168.0.1): icmp_req=22 ttl=64 time=0.379 ms 64 bytes from perenold.nat.mberard.eu (192.168.0.1): icmp_req=23 ttl=64 time=0.120 ms 64 bytes from perenold.nat.mberard.eu (192.168.0.1): icmp_req=24 ttl=64 time=0.109 ms ... --- perenold.nat.mberard.eu ping statistics --- 34 packets transmitted, 17 received, 50% packet loss, time 33008ms rtt min/avg/max/mdev = 0.072/0.181/0.383/0.104 ms As you can see 18 ping packets are lost during the speed transition, during that time the SSH connection is lost. ** Attachment added: "pm-logs-config.tar.gz" https://bugs.launchpad.net/ubuntu/+source/powernap/+bug/730210/+attachment/1892882/+files/pm-logs-config.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/730210 Title: SSH connection killed by eth_speed script [natty] -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
