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-next>] [day] [month] [year] [list]
Message-id: <3f9dad41-818e-4637-ab59-87f69b5c9212@enac.fr>
Date:   Thu, 31 Oct 2019 14:04:52 +0100
From:   Luc Novales <luc.novales@...c.fr>
To:     netdev@...r.kernel.org
Subject: Fwd: Bad permanent address 00:10:00:80:00:10 using r8168 module on
 some cards

Hi,

I have no answer from realtek, could you help me for debugging and 
determine if problem is hardware or software and howto solve it ?

In complement, howto get more information about module parameters ?

Best regards

Luc Novales.


-------- Message transféré --------
Sujet : 	Bad permanent address 00:10:00:80:00:10 using r8168 module on 
some cards
Date : 	Tue, 29 Oct 2019 11:28:09 +0100
De : 	Luc Novales <luc.novales@...c.fr>
Pour : 	nicfae@...ltek.com



Hi,

I am Luc Novales from ENAC in France.

We have some problems using tp-link PCI express network adapter (model : 
TG-3468(UN) ver:3.0, P/N:0152502214) under Debian Linux.

We uses this adapters on about 50 training computers.

Using r8168 compiled kernel driver, randomly and for unknown reasons bad 
address 00:10:00:80:00:10 is chosen at boot on some cards, causing some 
hardware address conflict on the network.

After that, 'ethtool -P' command returns bad permanent address and the 
only solution we have to solve this problem is to unplug computer from 
the power (to remove standby power on the adapter).

I didn't found any forum on your site and only this email address to 
have some help :

 1. Is there some users or developers forums ?
 2. Is there some howto debug kernel module ?
 3. Is there some way to make an hard reset to the chipset without
    unplug the computer (workaround before solving the problem) ?

Operating System context is :

lsb_release -a
Distributor ID:    Debian
Description:    Debian GNU/Linux 10 (buster)
Release:    10
Codename:    buster

uname -a
Linux G28-33 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u1 (2019-09-20) 
x86_64 GNU/Linux

modinfo r8168
filename: 
/lib/modules/4.19.0-6-amd64/kernel/drivers/net/ethernet/realtek/r8168.ko
version:        8.047.04-NAPI
license:        GPL
description:    RealTek RTL-8168 Gigabit Ethernet driver
author:         Realtek and the Linux r8168 crew <netdev@...r.kernel.org>
srcversion:     D3FC079D8040CD24274CA37
alias: pci:v00001186d00004300sv00001186sd00004B10bc*sc*i*
alias:          pci:v000010ECd00002600sv*sd*bc*sc*i*
alias:          pci:v000010ECd00002502sv*sd*bc*sc*i*
alias:          pci:v000010ECd00008161sv*sd*bc*sc*i*
alias:          pci:v000010ECd00008168sv*sd*bc*sc*i*
depends:
retpoline:      Y
name:           r8168
vermagic:       4.19.0-6-amd64 SMP mod_unload modversions
parm:           speed_mode:force phy operation. Deprecated by ethtool 
(8). (uint)
parm:           duplex_mode:force phy operation. Deprecated by ethtool 
(8). (uint)
parm:           autoneg_mode:force phy operation. Deprecated by ethtool 
(8). (uint)
parm:           advertising_mode:force phy operation. Deprecated by 
ethtool (8). (uint)
parm:           aspm:Enable ASPM. (int)
parm:           s5wol:Enable Shutdown Wake On Lan. (int)
parm:           s5_keep_curr_mac:Enable Shutdown Keep Current MAC 
Address. (int)
parm:           rx_copybreak:Copy breakpoint for copy-only-tiny-frames (int)
parm:           use_dac:Enable PCI DAC. Unsafe on 32 bit PCI slot. (int)
parm:           timer_count:Timer Interrupt Interval. (int)
parm:           eee_enable:Enable Energy Efficient Ethernet. (int)
parm:           hwoptimize:Enable HW optimization function. (ulong)
parm:           s0_magic_packet:Enable S0 Magic Packet. (int)
parm:           debug:Debug verbosity level (0=none, ..., 16=all) (int)



For information, we can't use stock kernel driver r8169 because card 
fails in a state which it doesn't auto-negotiate and doesn't establish 
any link with the switch (standby power must be remove to unlock the 
adapter).

Best regards

Luc Novales.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ