severity 677638 normal tags 677638 +moreinfo thanks Setting severity of normal because: * You have an option to disable. * This problem is not commonly reported. * Not reproducible on my machine (with the same driver)
Here's the output on my IBM ThinkPad running with the same e1000e device
driver. The NIC is:
00:19.0 Ethernet controller: Intel Corporation 82567LM Gigabit Network
Connection (rev 03)
Subsystem: Lenovo Device 20ee
Flags: fast devsel, IRQ 20
Memory at fc000000 (32-bit, non-prefetchable) [disabled] [size=128K]
Memory at fc025000 (32-bit, non-prefetchable) [disabled] [size=4K]
I/O ports at 1840 [disabled] [size=32]
Capabilities: [c8] Power Management version 2
Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [e0] PCI Advanced Features
Kernel driver in use: e1000e
And here's the output when run on battery:
root@champaran:~# ethtool eth0
Settings for eth0:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 2
Transceiver: internal
Auto-negotiation: on
MDI-X: on
Supports Wake-on: pumbg
Wake-on: d
Current message level: 0x00000007 (7)
drv probe link
Link detected: yes
root@champaran:~# acpi -V
Battery 0: Discharging, 98%, 05:46:05 remaining
Battery 0: design capacity 6813 mAh, last full capacity 5738 mAh = 84%
Adapter 0: off-line
Thermal 0: ok, 39.0 degrees C
Thermal 0: trip point 0 switches to mode critical at temperature 100.0
degrees C
Thermal 0: trip point 1 switches to mode passive at temperature 95.5
degrees C
Thermal 1: ok, 40.0 degrees C
Thermal 1: trip point 0 switches to mode critical at temperature 127.0
degrees C
Cooling 0: LCD 6 of 15
Cooling 1: Processor 0 of 10
Cooling 2: Processor 0 of 10
On Friday 15 June 2012 09:27 PM, Guillem Jover wrote:
> Hi!
>
> Since some time now (I only sat down to track it down pretty recently,
> but this has going on for probably a year or more), laptop-mode-tools
> has broken the wired network (e1000e) whenever I unplug the laptop from
> the wall power.
>
> The culprit is BATT_THROTTLE_ETHERNET=1 in
> «/etc/laptop-mode/conf.d/ethernet.conf».
>
> This turns the working ethernet device from this state:
>
> ,---
> # ethtool eth0
> Settings for eth0:
> Supported ports: [ TP ]
> Supported link modes: 10baseT/Half 10ba
> 100baseT/Half 100baseT/Full
> 1000baseT/Full
> Supported pause frame use: No
> Supports auto-negotiation: Yes
> Advertised link modes: 10baseT/Half 10ba
> 100baseT/Half 100baseT/Full
> 1000baseT/Full
> Advertised pause frame use: No
> Advertised auto-negotiation: Yes
> Speed: 100Mb/s
> Duplex: Full
> Port: Twisted Pair
> PHYAD: 2
> Transceiver: internal
> Auto-negotiation: on
> MDI-X: on
> Supports Wake-on: pumbg
> Wake-on: g
> Current message level: 0x00000001 (1)
> drv
> Link detected: yes
> `---
>
> To this non-working state:
>
> ,---
> # ethtool eth0
> Settings for eth0:
> Supported ports: [ TP ]
> Supported link modes: 10baseT/Half 10ba
> 100baseT/Half 100baseT/Full
> 1000baseT/Full
> Supported pause frame use: No
> Supports auto-negotiation: Yes
> Advertised link modes: 10baseT/Half 10ba
> 100baseT/Half 100baseT/Full
> 1000baseT/Full
> Advertised pause frame use: No
> Advertised auto-negotiation: Yes
> Speed: Unknown!
> Duplex: Unknown! (255)
> Port: Twisted Pair
> PHYAD: 2
> Transceiver: internal
> Auto-negotiation: on
> MDI-X: Unknown
> Supports Wake-on: pumbg
> Wake-on: d
> Current message level: 0x00000001 (1)
> drv
> Link detected: no
> `---
>
> If I set BATT_THROTTLE_ETHERNET to 0, then everything works as before.
>
> I don't think this setting should be enabled by default if it might
> cause this type of breakage, even if it ends up being a driver
> problem.
This is the first report on this behavior.
From your logs, it shows that when switched to battery, nothing is set
correct. Neither the speed, nor the Link.
Could you please set DEBUG=1 in the ethernet module only, and then see
if it can provide more information on what is failing?
e1000e must be a common driver supporting multiple Intel chipsets. I
have no problem setting the default to 0, but like I said, this is the
first time I've heard of this behavior.
> thanks,
> guillem
>
>
--
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
signature.asc
Description: OpenPGP digital signature
