Bug#941122: linux-image-5.2.0-2-amd64: e1000e is slooow for I219-LM (rev 11)
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Trying to use ethernet controler - but it was very slow (single kilobytes/sec)
* What exactly did you do (or not do) that was effective (or
I took driver from https://github.com/koljah-de/e1000e-dkms-debian/ removed calls to "mmiowb", compiled and installed - and this module works as expected.
Moreover kernel 5.2 from ubuntu also works.
*** End of the template - remove these template lines ***
-- Package-specific info:
Linux version 5.2.0-2-amd64 ([hidden email]) (gcc version 8.3.0 (Debian 8.3.0-21)) #1 SMP Debian 5.2.9-2 (2019-08-21)
** Tainted: OE (12288)
* Out-of-tree module has been loaded.
* Unsigned module has been loaded.
** Kernel log:
[... there were only iptables entries - cut ]
** Model information
product_name: HP EliteBook 840 G6
bios_version: R70 Ver. 01.02.00
board_version: KBC Version 52.4C.00
** USB devices:
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 0424:5534 Standard Microsystems Corp. Hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 007: ID 0408:5343 Quanta Computer, Inc. HP HD Camera
Bus 001 Device 005: ID 06cb:00b7 Synaptics, Inc.
Bus 001 Device 006: ID 045e:070f Microsoft Corp. LifeChat LX-3000 Headset
Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 002: ID 0424:2134 Standard Microsystems Corp. Hub
Bus 001 Device 008: ID 8087:0a2b Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
What do dmesg and ethtool say on respective link speed?
def4ec6dce39 ("e1000e: PCIm function state support") would be in
5.3-rc1 and above and was not backported. If you test the package from
experimental, is the issue gone? If you cherry-pick this commit on
top is the issue gone?
> def4ec6dce39 ("e1000e: PCIm function state support") would be in
> 5.3-rc1 and above and was not backported. If you test the package from
> experimental, is the issue gone? If you cherry-pick this commit on
> top is the issue gone?
I tried installing the linux-image-5.3.0-trunk-amd64 package from
experimental on buster but I still experiencing the same issue.