lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <2994F2A2-D844-40B0-9971-C002E5EC49CD@canonical.com>
Date:   Tue, 8 Oct 2019 15:46:10 +0800
From:   Kai-Heng Feng <kai.heng.feng@...onical.com>
To:     Tobias Klausmann <tobias.johannes.klausmann@....thm.de>
Cc:     jeffrey.t.kirsher@...el.com, intel-wired-lan@...ts.osuosl.org,
        linux-kernel@...r.kernel.org, tobias.klausmann@...enet.de
Subject: Re: e1000e regression - 5.4rc1

Hi Tobias,

> On Oct 5, 2019, at 03:52, Tobias Klausmann <tobias.johannes.klausmann@....thm.de> wrote:
> 
> Hello,
> 
> On 04.10.19 19:36, Kai-Heng Feng wrote:
>> Hi Tobias
>> 
>>> On Oct 4, 2019, at 18:34, Tobias Klausmann <tobias.johannes.klausmann@....thm.de> wrote:
>>> 
>>> Hello all,
>>> 
>>> While testing the 5.4rc1 release, i noticed my Ethernet never coming fully up, seemingly having a timeout problem. While bisecting this i landed at the commit dee23594d587386e9fda76732aa5f5a487709510 ("e1000e: Make speed detection on hotplugging cable more reliable") as the first bad commit. And indeed just reverting the commit on top of 5.4rc1 resolves the problem. Let me know if you have further questions, or patches to test!
>> Is runtime PM enabled (i.e. "power/control" = auto)?
> 
> 
> Yes it is set to auto.

Is something like TLP or `powertop --auto-tune` is in use?

Do you still see the issue when "power/control" keeps at "on"?

Kai-Heng

> 
> 
>> Also please attach full dmesg, thanks!
> 
> Attached,
> 
> Tobias
> 
>> 
>> Kai-Heng
>> 
>>> Greetings,
>>> 
>>> Tobias
>>> 
>>> 
>>> lspci:
>>> 
>>> 00:19.0 Ethernet controller: Intel Corporation 82579V Gigabit Network Connection (rev 06)
>>>         DeviceName:  Onboard LAN
>>>         Subsystem: ASUSTeK Computer Inc. P8P67 Deluxe Motherboard
>>>         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
>>>         Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
>>>         Latency: 0
>>>         Interrupt: pin A routed to IRQ 56
>>>         Region 0: Memory at fbf00000 (32-bit, non-prefetchable) [size=128K]
>>>         Region 1: Memory at fbf28000 (32-bit, non-prefetchable) [size=4K]
>>>         Region 2: I/O ports at f040 [size=32]
>>>         Capabilities: [c8] Power Management version 2
>>>                 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
>>>                 Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME-
>>>         Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
>>>                 Address: 00000000fee00698  Data: 0000
>>>         Capabilities: [e0] PCI Advanced Features
>>>                 AFCap: TP+ FLR+
>>>                 AFCtrl: FLR-
>>>                 AFStatus: TP-
>>>         Kernel driver in use: e1000e
>>>         Kernel modules: e1000e
>>> 
> <dmesg.txt>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ