Bug#762791: Bug#776000: Bug#762791: laptop-mode-tools: At boot eth0 fails
Control: tags -1 + moreinfo Is this issue still reproducible with newer kernel setups? Regards, Salvatore
Bug#762791: Bug#776000: Bug#762791: laptop-mode-tools: At boot eth0 fails
On Wednesday 08 July 2015 03:38 AM, Matthew Gabeler-Lee wrote: So, does this bug get moved to ethtool, or back to l-m-t? There's certainly nothing in ethtool's manpage that suggests this should be necessary, but working around it in l-m-t is easy. There are just too many such devices, with different/odd cases. Accommodating them all under LMT will be impossible. For this very reason, LMT also has a module to work around such cases until the actual bug gets solved. Please have a look at the exec-commands module in LMT You should use that. As noted earlier, I never had problems getting the speed change to take effect as long as the duplex setting was included. It is annoying that it always drops and re-acquires the link when doing this, even if the new setting is the same as the old setting, but I expect that is a completely separate issue. Since there is no legit bug in LMT, I'm going to merge the 2 bugs with 776000. -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System signature.asc Description: OpenPGP digital signature
Bug#762791: laptop-mode-tools: At boot eth0 fails
Control: retitle -1 RealTek RTL-8169 driver incapable of changing advertised speed without including duplex setting Control: forcemerge 776000 768121 762791 So let's re-cap every thing. 776000 was created for the very same driver and is assigned to the kernel. The other 2 bugs are still with l-m-t. In 768121, Matthew has mentioned the same error, that ethtool is incapable to changing to the advertised speed. He also mentioned that using the combination of speed/duplex together, does work. But on my tests, they do not. It is just that the command now does not report any error string, but the settings do not come into effect. rrs@chutzpah:~$ sudo ethtool -s eth1 speed 100 duplex half 22:30 ♒♒♒ ☺ rrs@chutzpah:~$ sudo ethtool eth1 Settings for eth1: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Link partner advertised pause frame use: Symmetric Receive-only Link partner advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: pumbg Current message level: 0x0033 (51) drv probe ifdown ifup Link detected: no 22:30 ♒♒♒ ☺ Matthew and Stefano, Will it be possible for you to test/verify the same with an active link ? I just don't have an ethernet cable any more. Just run the above mentioned ethtool command and see if it applies the requested speed. On Monday 29 September 2014 03:06 AM, Stefano Callegari wrote: Il dom, set 28, 2014 at 11:35:42 +0530, Ritesh Raj Sarraf scrisse: Once your machine has booted up, you can then do a restart of the laptop mode service. It will print all the debug logs onto the console. You can then copy paste the logs $ETHTOOL -s $DEVICE speed $MAX_SPEED 21 +++ /sbin/ethtool -s eth0 speed 1000 ++ ret='Cannot advertise speed 1000' ++ exit_status=0 ++ log VERBOSE 'Cannot advertise speed 1000' ++ ret='Cannot advertise speed 1000' Turns out the driver is not playing well with ethtool. The deivce reports that is has that capability, but is not acting accordingly. rrs@chutzpah:~$ sudo ethtool -s eth1 speed 1000 Cannot advertise speed 1000 22:07 ♒♒♒ ☺ rrs@chutzpah:~$ sudo ethtool -s eth1 speed 100 Cannot advertise speed 100 22:07 ♒♒♒ ☺ And every time we try to set the speed, the driver spits the following through the kernel. [15646.176453] r8169 :08:00.0 eth1: rtl_ocp_gphy_cond == 1 (loop: 10, delay: 25). [15646.176874] r8169 :08:00.0 eth1: rtl_ocp_gphy_cond == 1 (loop: 10, delay: 25). [15646.177291] r8169 :08:00.0 eth1: rtl_ocp_gphy_cond == 1 (loop: 10, delay: 25). [15650.112354] r8169 :08:00.0 eth1: rtl_ocp_gphy_cond == 1 (loop: 10, delay: 25). [15650.112768] r8169 :08:00.0 eth1: rtl_ocp_gphy_cond == 1 (loop: 10, delay: 25). [15650.113177] r8169 :08:00.0 eth1: rtl_ocp_gphy_cond == 1 (loop: 10, delay: 25). [15651.962170] r8169 :08:00.0 eth1: rtl_ocp_gphy_cond == 1 (loop: 10, delay: 25). [15651.962583] r8169 :08:00.0 eth1: rtl_ocp_gphy_cond == 1 (loop: 10, delay: 25). [15651.962996] r8169 :08:00.0 eth1: rtl_ocp_gphy_cond == 1 (loop: 10, delay: 25). [15665.323675] r8169 :08:00.0 eth1: rtl_ocp_gphy_cond == 1 (loop: 10, delay: 25). [15665.324089] r8169 :08:00.0 eth1: rtl_ocp_gphy_cond == 1 (loop: 10, delay: 25). [15665.324499] r8169 :08:00.0 eth1: rtl_ocp_gphy_cond == 1 (loop: 10, delay: 25). The advertised links to ethtool are: rrs@chutzpah:~$ sudo ethtool eth1 Settings for eth1: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Link partner advertised link modes: 10baseT/Half 10baseT/Full
Bug#762791: Bug#776000: Bug#762791: laptop-mode-tools: At boot eth0 fails
On Tue, 2015-07-07 at 22:38 +0530, Ritesh Raj Sarraf wrote: Control: retitle -1 RealTek RTL-8169 driver incapable of changing advertised speed without including duplex setting Control: forcemerge 776000 768121 762791 So let's re-cap every thing. 776000 was created for the very same driver and is assigned to the kernel. The other 2 bugs are still with l-m-t. In 768121, Matthew has mentioned the same error, that ethtool is incapable to changing to the advertised speed. He also mentioned that using the combination of speed/duplex together, does work. [...] That's a bug/limitation of ethtool, not the driver. Ben. -- Ben Hutchings Hoare's Law of Large Problems: Inside every large problem is a small problem struggling to get out. signature.asc Description: This is a digitally signed message part
Bug#768121: Bug#776000: Bug#762791: laptop-mode-tools: At boot eth0 fails
On 07/07/2015 02:51 PM, Ben Hutchings wrote: That's a bug/limitation of ethtool, not the driver. So, does this bug get moved to ethtool, or back to l-m-t? There's certainly nothing in ethtool's manpage that suggests this should be necessary, but working around it in l-m-t is easy. As noted earlier, I never had problems getting the speed change to take effect as long as the duplex setting was included. It is annoying that it always drops and re-acquires the link when doing this, even if the new setting is the same as the old setting, but I expect that is a completely separate issue. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762791: Bug#776000: Bug#762791: laptop-mode-tools: At boot eth0 fails
On Tue, 2015-07-07 at 18:08 -0400, Matthew Gabeler-Lee wrote: On 07/07/2015 02:51 PM, Ben Hutchings wrote: That's a bug/limitation of ethtool, not the driver. So, does this bug get moved to ethtool, or back to l-m-t? There's certainly nothing in ethtool's manpage that suggests this should be necessary, but working around it in l-m-t is easy. [...] I think there are multiple bugs here, since Ritesh said that a particular driver was failing to change mode when both speed and duplex were specified. Fixing the issue in ethtool is not quite as trivial as it might seem, s o l-m-t should be changed to work around that for now. Ben. -- Ben Hutchings If the facts do not conform to your theory, they must be disposed of. signature.asc Description: This is a digitally signed message part
Bug#762791: laptop-mode-tools: At boot eth0 fails
Il ven, set 26, 2014 at 11:03:24 +0200, To Ritesh Raj Sarraf scrisse: Il ven, set 26, 2014 at 01:50:22 +0530, Ritesh Raj Sarraf scrisse: Then I don't have much ideas. Perhaps you could set DEBUG=1 for this module, and then try to see what changes occur. Ok, I'll try with debug=1. See you tomorrow Sorry, I see the debug during the boot but I can't retrieve it to show you. It's too quick for to use ctrl+s to try to have a complete list of the debug and how copy and paste to you? No log saves these lines. Any clue? Thanks -- Stefano Callegari ste...@infinito.it -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762791: laptop-mode-tools: At boot eth0 fails
Once your machine has booted up, you can then do a restart of the laptop mode service. It will print all the debug logs onto the console. You can then copy paste the logs On Sun, Sep 28, 2014 at 11:31 PM, Stefano Callegari ste...@infinito.it wrote: Il ven, set 26, 2014 at 11:03:24 +0200, To Ritesh Raj Sarraf scrisse: Il ven, set 26, 2014 at 01:50:22 +0530, Ritesh Raj Sarraf scrisse: Then I don't have much ideas. Perhaps you could set DEBUG=1 for this module, and then try to see what changes occur. Ok, I'll try with debug=1. See you tomorrow Sorry, I see the debug during the boot but I can't retrieve it to show you. It's too quick for to use ctrl+s to try to have a complete list of the debug and how copy and paste to you? No log saves these lines. Any clue? Thanks -- Stefano Callegari ste...@infinito.it -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com Necessity is the mother of invention.
Bug#762791: laptop-mode-tools: At boot eth0 fails
Il dom, set 28, 2014 at 11:35:42 +0530, Ritesh Raj Sarraf scrisse: Once your machine has booted up, you can then do a restart of the laptop mode service. It will print all the debug logs onto the console. You can then copy paste the logs Only the last lines (shift+pageup can't show more): # Handle Speed Throttling ret=`$ETHTOOL -s $DEVICE speed $MAX_SPEED 21` exit_status=$?; log VERBOSE $ret; if [ $exit_status -eq 0 ]; then log VERBOSE Restored speed to $MAX_SPEED Mbit for $DEVICE else log VERBOSE Could not restore speed for $DEVICE fi fi # Shut down interface if [ x$DISABLE_ETHERNET = x1 ]; then if $IPTOOL link show $DEVICE | grep -q NO-CARRIER; then log VERBOSE ethernet: Disabling ethernet device $DEVICE $IPTOOL link set dev $DEVICE down else log VERBOSE ethernet: Not disabling ethernet device $DEVICE with active carrier. fi elif [ x$DISABLE_ETHERNET = x0 ]; then $IPTOOL link set dev $DEVICE up log VERBOSE ethernet: Re-enabling ethernet device $DEVICE fi done else log VERBOSE Ethernet module is disabled. fi ++ '[' x1 = x1 ']' ++ '[' -x /sbin/ethtool ']' ++ ETHTOOL=/sbin/ethtool ++ '[' -x /sbin/mii-tool ']' ++ MIITOOL=/sbin/mii-tool ++ '[' -x /bin/ip ']' ++ IPTOOL=/bin/ip ++ '[' 1 -eq 1 ']' ++ '[' 0 -eq 1 ']' ++ THROTTLE_ETHERNET=0 ++ '[' x0 = x1 ']' ++ DISABLE_ETHERNET=2 ++ for DEVICE in '$ETHERNET_DEVICES' ++ log VERBOSE 'ethernet: eth0' ++ '[' x1 = x1 ']' ++ '[' -x /usr/bin/logger -a VERBOSE '!=' STATUS ']' ++ '[' VERBOSE = MSG ']' ++ '[' VERBOSE = ERR ']' ++ '[' VERBOSE = VERBOSE ']' ++ '[' x0 = x1 ']' ++ '[' VERBOSE = VERBOSE ']' ++ '[' 1 = 0 ']' ++ '[' x1 = x1 ']' $ETHTOOL -s $DEVICE wol d 21 +++ /sbin/ethtool -s eth0 wol d ++ ret= ++ exit_status=0 ++ log VERBOSE '' ++ '[' x1 = x1 ']' ++ '[' -x /usr/bin/logger -a VERBOSE '!=' STATUS ']' ++ '[' VERBOSE = MSG ']' ++ '[' VERBOSE = ERR ']' ++ '[' VERBOSE = VERBOSE ']' ++ '[' x0 = x1 ']' ++ '[' VERBOSE = VERBOSE ']' ++ '[' 1 = 0 ']' ++ '[' 0 -eq 0 ']' ++ log VERBOSE 'Enabled wakeup-on-LAN for eth0' ++ '[' x1 = x1 ']' ++ '[' -x /usr/bin/logger -a VERBOSE '!=' STATUS ']' ++ '[' VERBOSE = MSG ']' ++ '[' VERBOSE = ERR ']' ++ '[' VERBOSE = VERBOSE ']' ++ '[' x0 = x1 ']' ++ '[' VERBOSE = VERBOSE ']' ++ '[' 1 = 0 ']' $MIITOOL -v $DEVICE 2/dev/null | grep capabilities | tr ' ' '\n' | sort -n | sed -ne '/^1.*/p' | cut -d b -f1 +++ cut -d b -f1 +++ sed -ne '/^1.*/p' +++ /sbin/mii-tool -v eth0 +++ sort -n +++ tr ' ' '\n' +++ grep capabilities ++ speed='10 10 100 100 1000 1000' ++ '[' -z '10 10 100 100 1000 1000' ']' ++ max_s=0 ++ min_s=10 ++ for s in '$speed' ++ '[' 10 -gt 0 ']' ++ max_s=10 ++ '[' 10 -lt 10 ']' ++ min_s=10 ++ for s in '$speed' +++ sed -ne '/^1.*/p' +++ /sbin/mii-tool -v eth0 +++ grep capabilities +++ sort -n +++ cut -d b -f1 ++ speed='10 10 100 100 1000 1000' ++ '[' -z '10 10 100 100 1000 1000' ']' ++ max_s=0 ++ min_s=10 ++ for s in '$speed' ++ '[' 10 -gt 0 ']' ++ max_s=10 ++ '[' 10 -lt 10 ']' ++ min_s=10 ++ for s in '$speed' ++ '[' 10 -gt 10 ']' ++ '[' 10 -lt 10 ']' ++ for s in '$speed' ++ '[' 100 -gt 10 ']' ++ max_s=100 ++ '[' 100 -lt 10 ']' ++ for s in '$speed' ++ '[' 100 -gt 100 ']' ++ '[' 100 -lt 10 ']' ++ for s in '$speed' ++ '[' 1000 -gt 100 ']' ++ max_s=1000 ++ '[' 1000 -lt 10 ']' ++ for s in '$speed' ++ '[' 1000 -gt 1000 ']' ++ '[' 1000 -lt 10 ']' ++ MAX_SPEED=1000 ++ case $THROTTLE_SPEED in ++ THROTTLE_SPEED=10 ++ '[' x0 = x1 ']' $ETHTOOL -s $DEVICE speed $MAX_SPEED 21 +++ /sbin/ethtool -s eth0 speed 1000 ++ ret='Cannot advertise speed 1000' ++ exit_status=0 ++ log VERBOSE 'Cannot advertise speed 1000' ++ '[' 10 -gt 10 ']' ++ '[' 10 -lt 10 ']' ++ for s in '$speed' ++ '[' 100 -gt 10 ']' ++ max_s=100 ++ '[' 100 -lt 10 ']' ++ for s in '$speed' ++ '[' 100 -gt 100 ']' ++ '[' 100 -lt 10 ']' ++ for s in '$speed' ++ '[' 1000 -gt 100 ']' ++ max_s=1000 ++ '[' 1000 -lt 10 ']' ++ for s in '$speed' ++ '[' 1000 -gt 1000 ']' ++ '[' 1000 -lt 10 ']' ++ MAX_SPEED=1000 ++ case $THROTTLE_SPEED in ++ THROTTLE_SPEED=10 ++ '[' x0 = x1 ']' $ETHTOOL -s $DEVICE speed $MAX_SPEED 21 +++ /sbin/ethtool -s eth0 speed 1000 ++ ret='Cannot advertise speed 1000' ++ exit_status=0 ++ log VERBOSE 'Cannot advertise speed 1000' ++ '[' x1 = x1 ']' ++ '[' -x /usr/bin/logger -a VERBOSE '!=' STATUS ']' ++ '[' VERBOSE = MSG ']' ++ '[' VERBOSE = ERR ']' ++ '[' VERBOSE = VERBOSE ']' ++ '[' x0 = x1 ']' ++ '[' VERBOSE = VERBOSE ']' ++ '[' 1 = 0 ']' ++ '[' 0 -eq 0 ']' ++ log VERBOSE 'Restored speed to
Bug#762791: laptop-mode-tools: At boot eth0 fails
Il gio, set 25, 2014 at 04:53:13 +0530, Ritesh Raj Sarraf scrisse: On Thursday 25 September 2014 04:40 PM, Stefano Callegari wrote: If it is set to 1, you need to set it to 0, and then re-test your scenario. I think to remember to have tested it with 0 but not has seemed the solution. I'll try again but I'll say you if it's ok tomorrow morning. Thanks. I'll wait for your results. The other suspicion I have with this card family, is that they are more flaky when compared to Intel card. Previously, the other laptop had an Intel card, that used the e1000e driver. With that card, the issues were none to the best of my knowledge. Let's see what you results are. Accordingly we'll act further. No... Again this morning, the eth0 has gone up and down until I done the log in into kde. Below an example from the log: Sep 26 09:27:04 hpdv5 systemd-udevd[184]: Network interface NamePolicy= disabled on kernel commandline, ignoring. Sep 26 09:27:04 hpdv5 kernel: [ 339.688970] r8169 :03:00.0 eth0: link up Sep 26 09:27:05 hpdv5 laptop-mode: Laptop mode Sep 26 09:27:05 hpdv5 laptop-mode: enabled, active Sep 26 09:27:05 hpdv5 laptop-mode: (Data-loss sensitive features disabled.) Sep 26 09:27:05 hpdv5 systemd[1]: Starting Session c67 of user stefano. Sep 26 09:27:05 hpdv5 systemd[1]: Started Session c67 of user stefano. Sep 26 09:27:05 hpdv5 kernel: [ 340.601747] r8169 :03:00.0 eth0: link down [cut] Sep 26 09:27:08 hpdv5 kernel: [ 343.780266] r8169 :03:00.0 eth0: link up Sep 26 09:27:09 hpdv5 laptop-mode: Laptop mode Sep 26 09:27:09 hpdv5 laptop-mode: enabled, active [unchanged] Sep 26 09:27:09 hpdv5 laptop-mode: (Data-loss sensitive features disabled.) Sep 26 09:27:09 hpdv5 laptop-mode: Laptop mode Sep 26 09:27:09 hpdv5 laptop-mode: enabled, active [unchanged] Sep 26 09:27:09 hpdv5 laptop-mode: (Data-loss sensitive features disabled.) Sep 26 09:27:09 hpdv5 laptop-mode: Laptop mode Sep 26 09:27:09 hpdv5 laptop-mode: enabled, active [unchanged] Sep 26 09:27:09 hpdv5 laptop-mode: (Data-loss sensitive features disabled.) Sep 26 09:27:09 hpdv5 laptop-mode: Laptop mode Sep 26 09:27:09 hpdv5 laptop-mode: enabled, active [unchanged] Sep 26 09:27:09 hpdv5 laptop-mode: (Data-loss sensitive features disabled.) Sep 26 09:27:09 hpdv5 laptop-mode: Laptop mode Sep 26 09:27:09 hpdv5 laptop-mode: enabled, not active Sep 26 09:27:09 hpdv5 systemd[1]: Starting Session c70 of user stefano. Sep 26 09:27:09 hpdv5 systemd[1]: Started Session c70 of user stefano. Sep 26 09:27:09 hpdv5 kernel: [ 344.957705] r8169 :03:00.0 eth0: link down and ~ bash $ grep -e ^\w /etc/laptop-mode/conf.d/ethernet.conf DEBUG=0 CONTROL_ETHERNET=1 BATT_THROTTLE_ETHERNET=0 LM_AC_THROTTLE_ETHERNET=0 NOLM_AC_THROTTLE_ETHERNET=0 THROTTLE_SPEED=slowest DISABLE_WAKEUP_ON_LAN=1 ETHERNET_DEVICES=eth0 DISABLE_ETHERNET_ON_BATTERY=0 Again the LAN led on the router blinks. p.s.: The router has also Gbit and when I power on the laptop the led shows me the link at 100Mbit. PS: I intend to do a new Laptop Mode Tools release soon, to ensure it makes it before the Debian freeze. A quick turnaround will be highly appreciated. As I have say you yesterday, in a day if I reboot the laptop the eth0 hasn't this behavior anymore, so I can show the tests only tomorrow. Sorry.. Thanks -- Stefano Callegari ste...@infinito.it -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762791: laptop-mode-tools: At boot eth0 fails
Then I don't have much ideas. Perhaps you could set DEBUG=1 for this module, and then try to see what changes occur. On Fri, Sep 26, 2014 at 1:40 PM, Stefano Callegari ste...@infinito.it wrote: Il gio, set 25, 2014 at 04:53:13 +0530, Ritesh Raj Sarraf scrisse: On Thursday 25 September 2014 04:40 PM, Stefano Callegari wrote: If it is set to 1, you need to set it to 0, and then re-test your scenario. I think to remember to have tested it with 0 but not has seemed the solution. I'll try again but I'll say you if it's ok tomorrow morning. Thanks. I'll wait for your results. The other suspicion I have with this card family, is that they are more flaky when compared to Intel card. Previously, the other laptop had an Intel card, that used the e1000e driver. With that card, the issues were none to the best of my knowledge. Let's see what you results are. Accordingly we'll act further. No... Again this morning, the eth0 has gone up and down until I done the log in into kde. Below an example from the log: Sep 26 09:27:04 hpdv5 systemd-udevd[184]: Network interface NamePolicy= disabled on kernel commandline, ignoring. Sep 26 09:27:04 hpdv5 kernel: [ 339.688970] r8169 :03:00.0 eth0: link up Sep 26 09:27:05 hpdv5 laptop-mode: Laptop mode Sep 26 09:27:05 hpdv5 laptop-mode: enabled, active Sep 26 09:27:05 hpdv5 laptop-mode: (Data-loss sensitive features disabled.) Sep 26 09:27:05 hpdv5 systemd[1]: Starting Session c67 of user stefano. Sep 26 09:27:05 hpdv5 systemd[1]: Started Session c67 of user stefano. Sep 26 09:27:05 hpdv5 kernel: [ 340.601747] r8169 :03:00.0 eth0: link down [cut] Sep 26 09:27:08 hpdv5 kernel: [ 343.780266] r8169 :03:00.0 eth0: link up Sep 26 09:27:09 hpdv5 laptop-mode: Laptop mode Sep 26 09:27:09 hpdv5 laptop-mode: enabled, active [unchanged] Sep 26 09:27:09 hpdv5 laptop-mode: (Data-loss sensitive features disabled.) Sep 26 09:27:09 hpdv5 laptop-mode: Laptop mode Sep 26 09:27:09 hpdv5 laptop-mode: enabled, active [unchanged] Sep 26 09:27:09 hpdv5 laptop-mode: (Data-loss sensitive features disabled.) Sep 26 09:27:09 hpdv5 laptop-mode: Laptop mode Sep 26 09:27:09 hpdv5 laptop-mode: enabled, active [unchanged] Sep 26 09:27:09 hpdv5 laptop-mode: (Data-loss sensitive features disabled.) Sep 26 09:27:09 hpdv5 laptop-mode: Laptop mode Sep 26 09:27:09 hpdv5 laptop-mode: enabled, active [unchanged] Sep 26 09:27:09 hpdv5 laptop-mode: (Data-loss sensitive features disabled.) Sep 26 09:27:09 hpdv5 laptop-mode: Laptop mode Sep 26 09:27:09 hpdv5 laptop-mode: enabled, not active Sep 26 09:27:09 hpdv5 systemd[1]: Starting Session c70 of user stefano. Sep 26 09:27:09 hpdv5 systemd[1]: Started Session c70 of user stefano. Sep 26 09:27:09 hpdv5 kernel: [ 344.957705] r8169 :03:00.0 eth0: link down and ~ bash $ grep -e ^\w /etc/laptop-mode/conf.d/ethernet.conf DEBUG=0 CONTROL_ETHERNET=1 BATT_THROTTLE_ETHERNET=0 LM_AC_THROTTLE_ETHERNET=0 NOLM_AC_THROTTLE_ETHERNET=0 THROTTLE_SPEED=slowest DISABLE_WAKEUP_ON_LAN=1 ETHERNET_DEVICES=eth0 DISABLE_ETHERNET_ON_BATTERY=0 Again the LAN led on the router blinks. p.s.: The router has also Gbit and when I power on the laptop the led shows me the link at 100Mbit. PS: I intend to do a new Laptop Mode Tools release soon, to ensure it makes it before the Debian freeze. A quick turnaround will be highly appreciated. As I have say you yesterday, in a day if I reboot the laptop the eth0 hasn't this behavior anymore, so I can show the tests only tomorrow. Sorry.. Thanks -- Stefano Callegari ste...@infinito.it -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com Necessity is the mother of invention.
Bug#762791: laptop-mode-tools: At boot eth0 fails
Il ven, set 26, 2014 at 01:50:22 +0530, Ritesh Raj Sarraf scrisse: Then I don't have much ideas. Perhaps you could set DEBUG=1 for this module, and then try to see what changes occur. Ok, I'll try with debug=1. See you tomorrow [cut] Ciao -- Stefano Callegari ste...@infinito.it -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762791: laptop-mode-tools: At boot eth0 fails
Package: laptop-mode-tools Version: 1.65-2 Severity: normal Dear Maintainer, from some morning, when I boot my laptop I have a lot of lines like Sep 25 08:10:06 hpdv5 laptop-mode: Laptop mode Sep 25 08:10:06 hpdv5 laptop-mode: enabled, not active Sep 25 08:10:06 hpdv5 kernel: [ 76.966266] r8169 :03:00.0 eth0: rtl_phyar_cond == 1 (loop: 20, delay: 25). Sep 25 08:10:06 hpdv5 kernel: [ 76.967192] r8169 :03:00.0 eth0: rtl_phyar_cond == 1 (loop: 20, delay: 25). Sep 25 08:10:06 hpdv5 kernel: [ 76.967963] r8169 :03:00.0 eth0: rtl_phyar_cond == 1 (loop: 20, delay: 25). Sep 25 08:10:06 hpdv5 kernel: [ 76.968742] r8169 :03:00.0 eth0: rtl_phyar_cond == 1 (loop: 20, delay: 25). Sep 25 08:10:06 hpdv5 avahi-daemon[2365]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.40. Sep 25 08:10:06 hpdv5 avahi-daemon[2365]: New relevant interface eth0.IPv4 for mDNS. Sep 25 08:10:06 hpdv5 avahi-daemon[2365]: Registering new address record for 192.168.1.40 on eth0.IPv4. Sep 25 08:10:06 hpdv5 kernel: [ 76.997522] r8169 :03:00.0 eth0: link down Sep 25 08:10:06 hpdv5 kernel: [ 76.997613] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready and the led on my router show the link down. This above every few second (the router led blink like Christmas), mainly until I log in into kdm/kde (thanks to knemo?), but sometimes I must restart the network service. Some notice: - I unplug the battery and use the AC with an UPS (I haven't tried with the battery); - I haven't IPv6 on my LAN and I have tried to disable it by sysctl but not resolves; - I use ifupdown + guessnet and I have the same problem if I set eth0 'auto' or 'allow-hotplug'; - If I reboot the laptop, the eth0 runs without problems (and this is a big problem because I must wait next morning to verify any change/solutions). When few days ago I have set CONTROL_ETHERNET from 'auto' to '0', at the morning boot, the eth0 runs ok. Below the eth0 data (with CONTROL_ETHERNET set to 0): 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 02) Subsystem: Hewlett-Packard Company Device 3603 Flags: bus master, fast devsel, latency 0, IRQ 47 I/O ports at 6000 [size=256] Memory at d401 (64-bit, prefetchable) [size=4K] Memory at d400 (64-bit, prefetchable) [size=64K] Expansion ROM at dd20 [disabled] [size=64K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable+ Count=1/2 Maskable- 64bit+ Capabilities: [70] Express Endpoint, MSI 01 Capabilities: [b0] MSI-X: Enable- Count=2 Masked- Capabilities: [d0] Vital Product Data Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel Capabilities: [160] Device Serial Number 00-00-00-00-00-00-00-00 Kernel driver in use: r8169 ~ -su # ethtool eth0 Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Link partner advertised pause frame use: Symmetric Receive-only Link partner advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: d Current message level: 0x0033 (51) drv probe ifdown ifup Link detected: yes Thanks -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (903, 'unstable'), (500, 'testing'), (400, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages laptop-mode-tools depends on: ii lsb-base4.1+Debian13 ii psmisc 22.21-2 ii util-linux 2.20.1-5.8 Versions of packages laptop-mode-tools recommends: ii ethtool 1:3.16-1 ii hdparm 9.43-1.1 ii net-tools 1.60-26 ii python-qt4 4.11.2+dfsg-1 ii sdparm 1.07-1 ii udev215-4 ii wireless-tools 30~pre9-8
Bug#762791: laptop-mode-tools: At boot eth0 fails
On Thursday 25 September 2014 01:54 PM, Stefano wrote: from some morning, when I boot my laptop I have a lot of lines like Sep 25 08:10:06 hpdv5 laptop-mode: Laptop mode Sep 25 08:10:06 hpdv5 laptop-mode: enabled, not active Sep 25 08:10:06 hpdv5 kernel: [ 76.966266] r8169 :03:00.0 eth0: rtl_phyar_cond == 1 (loop: 20, delay: 25). Sep 25 08:10:06 hpdv5 kernel: [ 76.967192] r8169 :03:00.0 eth0: rtl_phyar_cond == 1 (loop: 20, delay: 25). Sep 25 08:10:06 hpdv5 kernel: [ 76.967963] r8169 :03:00.0 eth0: rtl_phyar_cond == 1 (loop: 20, delay: 25). Sep 25 08:10:06 hpdv5 kernel: [ 76.968742] r8169 :03:00.0 eth0: rtl_phyar_cond == 1 (loop: 20, delay: 25). Sep 25 08:10:06 hpdv5 avahi-daemon[2365]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.40. Sep 25 08:10:06 hpdv5 avahi-daemon[2365]: New relevant interface eth0.IPv4 for mDNS. Sep 25 08:10:06 hpdv5 avahi-daemon[2365]: Registering new address record for 192.168.1.40 on eth0.IPv4. Sep 25 08:10:06 hpdv5 kernel: [ 76.997522] r8169 :03:00.0 eth0: link down Sep 25 08:10:06 hpdv5 kernel: [ 76.997613] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready and the led on my router show the link down. I recently bought an HP laptop and was given the same NIC. 14:18:27 rrs@learner:~$ dmesg | grep -i r8169 [ 15.871007] r8169 :0f:00.0: firmware: direct-loading firmware rtl_nic/rtl8168g-2.fw [ 15.913285] r8169 :0f:00.0 eth0: link down [ 50.541260] r8169 :0f:00.0 eth0: link down [38935.041500] r8169 :0f:00.0 eth0: link down [38935.189645] r8169 :0f:00.0 eth0: link down [49182.668076] r8169 :0f:00.0 eth0: link down [49207.921116] r8169 :0f:00.0 eth0: link down [49209.894375] r8169 :0f:00.0: no hotplug settings from platform [49211.957799] r8169 :0f:00.0 eth0: link down [49216.449479] r8169 :0f:00.0 eth0: link down [64739.158471] r8169 :0f:00.0 eth0: link down [64741.412907] r8169 :0f:00.0: no hotplug settings from platform [64744.395701] r8169 :0f:00.0 eth0: link down [64744.531811] r8169 :0f:00.0 eth0: link down [64748.150777] r8169 :0f:00.0 eth0: link down [67293.376212] r8169 :0f:00.0 eth0: link down [67295.343379] r8169 :0f:00.0: no hotplug settings from platform [67297.329963] r8169 :0f:00.0 eth0: link down [67302.085830] r8169 :0f:00.0 eth0: link down [76245.133588] r8169 :0f:00.0: no hotplug settings from platform [76246.900415] r8169 :0f:00.0 eth0: rtl_ocp_gphy_cond == 1 (loop: 10, delay: 25). [76246.900784] r8169 :0f:00.0 eth0: rtl_ocp_gphy_cond == 1 (loop: 10, delay: 25). [76246.901159] r8169 :0f:00.0 eth0: rtl_ocp_gphy_cond == 1 (loop: 10, delay: 25). [76246.960167] r8169 :0f:00.0 eth0: link down [76248.565476] r8169 :0f:00.0 eth0: link down I haven't faced your problem because I haven't used the ethernet NIC much. I am on the wifi only. We made a recent power saving change in the ethernet module to ensure that we actually power down the device. commit 8fff5eb2bfdde0fa15d8e7813d2399af78d1f064 Author: Stefan Huber shu...@sthu.org Date: Sun May 25 09:41:20 2014 +0200 ethernet: replace sysfs/enabled by 'ip link down' Disabeling the ethernet pci device via echo 0 to sysfs attr enabled does not necessarily power down the device but rather decrements the enabled counter. Even if the counter reaches 0 the device may still drain power. Shutting down the ethernet device via 'ip link set dev DEV down', however, reduces power consumptions to 0 mW as indicated by powertop. The idea is to completely disable the battery when on battery. It is a use case. Can you check what the settings are for the following in /etc/laptop-mode/conf.d/ethernet.conf ? DISABLE_ETHERNET_ON_BATTERY=1 If it is set to 1, you need to set it to 0, and then re-test your scenario. -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com Necessity is the mother of invention.
Bug#762791: laptop-mode-tools: At boot eth0 fails
Il gio, set 25, 2014 at 02:32:39 +0530, Ritesh Raj Sarraf scrisse: [cut] The idea is to completely disable the battery when on battery. It is a use case. Can you check what the settings are for the following in /etc/laptop-mode/conf.d/ethernet.conf ? DISABLE_ETHERNET_ON_BATTERY=1 Yes, it's set so. If it is set to 1, you need to set it to 0, and then re-test your scenario. I think to remember to have tested it with 0 but not has seemed the solution. I'll try again but I'll say you if it's ok tomorrow morning. Thanks. -- Stefano Callegari ste...@infinito.it -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762791: laptop-mode-tools: At boot eth0 fails
On Thursday 25 September 2014 04:40 PM, Stefano Callegari wrote: If it is set to 1, you need to set it to 0, and then re-test your scenario. I think to remember to have tested it with 0 but not has seemed the solution. I'll try again but I'll say you if it's ok tomorrow morning. Thanks. I'll wait for your results. The other suspicion I have with this card family, is that they are more flaky when compared to Intel card. Previously, the other laptop had an Intel card, that used the e1000e driver. With that card, the issues were none to the best of my knowledge. Let's see what you results are. Accordingly we'll act further. PS: I intend to do a new Laptop Mode Tools release soon, to ensure it makes it before the Debian freeze. A quick turnaround will be highly appreciated. -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com Necessity is the mother of invention.
