[elrepo] Interest in kmod package for lan78xx?

Björn Gerhart gerhart at posteo.de
Tue Jun 6 12:27:33 EDT 2017


> Am 03.06.2017 um 19:32 schrieb Phil Perry <phil at elrepo.org>:
> 
> On 30/05/17 21:53, Björn Gerhart wrote:
>>> On 30/05/17 14:20, Björn Gerhart wrote:
>>>> Hi folks,
>>>> I need to support the USB LAN chip adapter LAN7850 by Microchip. This NIC model already is integrated in later versions of kernel module lan78xx. Yet, it is not part of the el7 kernel package.
>>>> Apparently, support with elrepo's kernel 4.4 package is given.
>>>> However, I would kindly ask if someone else also is interested in a kmod package containing the lan78xx module. Yet, I don't know anything about the backport efforts this would mean for el7 (and maybe for el6 also later on).
>>>> What are your thoughts on that?
>>>> This is the chip's concrete data:
>>>> LAN7850, Vendor ID 0x0424, Product ID 0x7850
>>>> Thanks and best - Björn
>>> 
>>> Hi Björn,
>>> 
>>> I will look at this for you.
>>> 
>>> As you state, kernel-4.4 appears to be the first longterm kernel that supported this device, so we will need to see if we can backport the driver from this kernel. It looks like the driver also depends on the microchip PHY which we will also need to backport as this didn't exist in RHEL7's 3.10 kernel.
>>> 
>>> I will start by trying to backport the driver for RHEL7.
>>> 
>>> In the meantime, Alan's kernel-lt-4.4 and kernel-ml (currently 4.11) packages should support this device on RHEL7.
>>> 
>>> I'll report back here once I have some news. I assume you have the hardware available to test a kmod driver package for RHEL7?
>> Hi Phil, thanks so much for investigating that! Yes, I have the hardware available and would give feedback about the tests.
>> Best - Björn
> 
> Hi Björn,
> 
> I have a driver package for you to test in the elrepo testing repository:
> 
> http://elrepo.org/linux/testing/el7/x86_64/RPMS/kmod-lan78xx-1.0.4-1.el7.elrepo.x86_64.rpm
> 
> I've just uploaded the package so it should show up shortly after syncing to the mirrors.
> 
> If you could please test and let me know how you get on. To install:
> 
> yum --enablerepo=elrepo-testing install kmod-lan78xx
> 
> then reboot.
> 
> The package provides 2 modules, lan78xx.ko and microchip.ko. I'm not sure if microchip.ko needs to be loaded or will get loaded automatically as it doesn't appear to show as a module dependency for lan78xx. So keep an eye what's happening with lsmod / dmesg and load it if you think it's required.
> 
> The driver is based on a patchset[1] by Microcode provided for kernel-3.10.
> 
> Phil
> 
> [1] http://www.microchip.com/wwwproducts/en/LAN7800 <http://www.microchip.com/wwwproducts/en/LAN7800>


Hi Phil,

thanks a lot for that quick service!

These are my observations:
- module microchip gets loaded when lan78xx does. In fact it can get unloaded again without effecting the lan78xx driver. So I can blacklist the microchip module for not getting loaded from the beginning.
- in principle the Ethernet gets configured properly as it seems
- However, once the RJ-45 Ethernet cable is getting connected, the kernel drops a warning as shown below. The messages is not dependent whether the microchip module is loaded or not. So it appears in either case.

Maybe the slowpath warning results on the fact that el7's 3.10 kernel has some backports implemented which the vanilla 3.10 kernel doesn't?

This is what journalctl tells me:
Jun 06 21:15:15 wnlpos4-bg kernel: ------------[ cut here ]------------
Jun 06 21:15:15 wnlpos4-bg kernel: WARNING: at kernel/workqueue.c:1402 __queue_work+0x271/0x320()
Jun 06 21:15:15 wnlpos4-bg kernel: Modules linked in: microchip(OE) lan78xx(OE) ftdi_sio xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun uinput ip6t_rpfilter ipt_REJECT nf_reject_ipv4 ip6t_REJECT nf_reject_ipv6 xt_conntrack ip_set nfnetlink ebtable_nat ebtable_broute bridge stp llc ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter nct6775(OE) hwmon_vid i2c_dev dm_mirror dm_region_hash dm_log dm_mod intel_powerclamp coretemp snd_hda_codec_hdmi intel_rapl iosf_mbi kvm_intel snd_hda_codec_realtek snd_hda_codec_generic kvm snd_hda_intel irqbypass crc32_pclmul snd_hda_codec ghash_clmulni_intel
Jun 06 21:15:15 wnlpos4-bg kernel:  snd_hda_core snd_hwdep aesni_intel snd_seq lrw gf128mul glue_helper ablk_helper cryptd snd_seq_device snd_pcm iTCO_wdt iTCO_vendor_support snd_timer mei_me snd sg mei soundcore i2c_i801 pcspkr tpm_crb acpi_pad nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables ext4 mbcache jbd2 sd_mod crc_t10dif crct10dif_generic hid_multitouch i915 ahci libahci i2c_algo_bit drm_kms_helper crct10dif_pclmul crct10dif_common syscopyarea sysfillrect sysimgblt fb_sys_fops libata drm crc32c_intel e1000e ptp pps_core i2c_hid video i2c_core fjes
Jun 06 21:15:15 wnlpos4-bg kernel: CPU: 1 PID: 15856 Comm: kworker/1:0 Tainted: G           OE  ------------ 3.10.0-514.21.1.el7.x86_64 #1
Jun 06 21:15:15 wnlpos4-bg kernel: Hardware name: WINCOR NIXDORF iPOS plus Advanced/M3-Q170-AIO, BIOS WN STD 00/07 04/10/2017
Jun 06 21:15:15 wnlpos4-bg kernel: Workqueue: events lan78xx_delayedwork [lan78xx]
Jun 06 21:15:15 wnlpos4-bg kernel:  0000000000000000 0000000089354e19 ffff880166bafcf0 ffffffff81686f13
Jun 06 21:15:15 wnlpos4-bg kernel:  ffff880166bafd28 ffffffff81085cb0 ffff88016dc9a700 ffff88008445ab20
Jun 06 21:15:15 wnlpos4-bg kernel:  0000000000001400 ffff880169006800 0000000000011868 ffff880166bafd38
Jun 06 21:15:15 wnlpos4-bg kernel: Call Trace:
Jun 06 21:15:15 wnlpos4-bg kernel:  [<ffffffff81686f13>] dump_stack+0x19/0x1b
Jun 06 21:15:15 wnlpos4-bg kernel:  [<ffffffff81085cb0>] warn_slowpath_common+0x70/0xb0
Jun 06 21:15:15 wnlpos4-bg kernel:  [<ffffffff81085dfa>] warn_slowpath_null+0x1a/0x20
Jun 06 21:15:15 wnlpos4-bg kernel:  [<ffffffff810a63a1>] __queue_work+0x271/0x320
Jun 06 21:15:15 wnlpos4-bg kernel:  [<ffffffff810a66a5>] queue_work_on+0x45/0x50
Jun 06 21:15:15 wnlpos4-bg kernel:  [<ffffffffa0887806>] lan78xx_delayedwork+0x4b6/0x730 [lan78xx]
Jun 06 21:15:15 wnlpos4-bg kernel:  [<ffffffff810a845b>] process_one_work+0x17b/0x470
Jun 06 21:15:15 wnlpos4-bg kernel:  [<ffffffff810a9296>] worker_thread+0x126/0x410
Jun 06 21:15:15 wnlpos4-bg kernel:  [<ffffffff810a9170>] ? rescuer_thread+0x460/0x460
Jun 06 21:15:15 wnlpos4-bg kernel:  [<ffffffff810b0a4f>] kthread+0xcf/0xe0
Jun 06 21:15:15 wnlpos4-bg kernel:  [<ffffffff810b0980>] ? kthread_create_on_node+0x140/0x140
Jun 06 21:15:15 wnlpos4-bg kernel:  [<ffffffff81697518>] ret_from_fork+0x58/0x90
Jun 06 21:15:15 wnlpos4-bg kernel:  [<ffffffff810b0980>] ? kthread_create_on_node+0x140/0x140
Jun 06 21:15:15 wnlpos4-bg kernel: ---[ end trace 0f41e8e2e1885692 ]---
Jun 06 21:15:15 wnlpos4-bg NetworkManager[954]: <info>  [1496776515.9926] device (enp0s20f0u5u5): link connected
Jun 06 21:15:15 wnlpos4-bg NetworkManager[954]: <info>  [1496776515.9935] device (enp0s20f0u5u5): state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]
Jun 06 21:15:15 wnlpos4-bg NetworkManager[954]: <info>  [1496776515.9939] policy: auto-activating connection 'Wired connection 1'
Jun 06 21:15:15 wnlpos4-bg NetworkManager[954]: <info>  [1496776515.9945] device (enp0s20f0u5u5): Activation: starting connection 'Wired connection 1' (e07e93d0-af42-35ad-8832-1bc27a06b518)
Jun 06 21:15:15 wnlpos4-bg NetworkManager[954]: <info>  [1496776515.9946] device (enp0s20f0u5u5): state change: disconnected -> prepare (reason 'none') [30 40 0]
Jun 06 21:15:15 wnlpos4-bg NetworkManager[954]: <info>  [1496776515.9947] manager: NetworkManager state is now CONNECTING
Jun 06 21:15:15 wnlpos4-bg dbus[628]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Jun 06 21:15:15 wnlpos4-bg systemd[1]: Cannot add dependency job for unit microcode.service, ignoring: Unit is not loaded properly: Invalid argument.
Jun 06 21:15:15 wnlpos4-bg dbus-daemon[628]: dbus[628]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Jun 06 21:15:15 wnlpos4-bg NetworkManager[954]: <info>  [1496776515.9950] device (enp0s20f0u5u5): state change: prepare -> config (reason 'none') [40 50 0]
Jun 06 21:15:15 wnlpos4-bg systemd[1]: Starting Network Manager Script Dispatcher Service...
Jun 06 21:15:16 wnlpos4-bg dbus[628]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jun 06 21:15:16 wnlpos4-bg dbus-daemon[628]: dbus[628]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jun 06 21:15:16 wnlpos4-bg systemd[1]: Started Network Manager Script Dispatcher Service.
Jun 06 21:15:16 wnlpos4-bg nm-dispatcher[19160]: req:1 'connectivity-change': new request (4 scripts)
Jun 06 21:15:16 wnlpos4-bg nm-dispatcher[19160]: req:1 'connectivity-change': start running ordered scripts...
Jun 06 21:15:16 wnlpos4-bg NetworkManager[954]: <info>  [1496776516.0078] device (enp0s20f0u5u5): state change: config -> ip-config (reason 'none') [50 70 0]
Jun 06 21:15:16 wnlpos4-bg NetworkManager[954]: <info>  [1496776516.0081] dhcp4 (enp0s20f0u5u5): activation: beginning transaction (timeout in 45 seconds)
Jun 06 21:15:16 wnlpos4-bg NetworkManager[954]: <info>  [1496776516.0096] dhcp4 (enp0s20f0u5u5): dhclient started with pid 19169
Jun 06 21:15:16 wnlpos4-bg dhclient[19169]: DHCPDISCOVER on enp0s20f0u5u5 to 255.255.255.255 port 67 interval 7 (xid=0x3ac53468)
Jun 06 21:15:16 wnlpos4-bg dhclient[19169]: DHCPREQUEST on enp0s20f0u5u5 to 255.255.255.255 port 67 (xid=0x3ac53468)
Jun 06 21:15:16 wnlpos4-bg dhclient[19169]: DHCPOFFER from 172.18.238.1
Jun 06 21:15:16 wnlpos4-bg dhclient[19169]: DHCPACK from 172.18.238.1 (xid=0x3ac53468)
Jun 06 21:15:16 wnlpos4-bg NetworkManager[954]: <info>  [1496776516.1401] dhcp4 (enp0s20f0u5u5):   address 172.18.238.33
Jun 06 21:15:16 wnlpos4-bg NetworkManager[954]: <info>  [1496776516.1402] dhcp4 (enp0s20f0u5u5):   plen 24 (255.255.255.0)
Jun 06 21:15:16 wnlpos4-bg NetworkManager[954]: <info>  [1496776516.1402] dhcp4 (enp0s20f0u5u5):   gateway 172.18.238.1
Jun 06 21:15:16 wnlpos4-bg NetworkManager[954]: <info>  [1496776516.1402] dhcp4 (enp0s20f0u5u5):   server identifier 172.18.131.5
Jun 06 21:15:16 wnlpos4-bg NetworkManager[954]: <info>  [1496776516.1402] dhcp4 (enp0s20f0u5u5):   lease time 691200
Jun 06 21:15:16 wnlpos4-bg NetworkManager[954]: <info>  [1496776516.1402] dhcp4 (enp0s20f0u5u5):   nameserver '172.18.144.10'
Jun 06 21:15:16 wnlpos4-bg NetworkManager[954]: <info>  [1496776516.1403] dhcp4 (enp0s20f0u5u5):   nameserver '172.18.144.12'
Jun 06 21:15:16 wnlpos4-bg NetworkManager[954]: <info>  [1496776516.1403] dhcp4 (enp0s20f0u5u5):   domain name 'wincor-nixdorf.com <http://wincor-nixdorf.com/>'
Jun 06 21:15:16 wnlpos4-bg NetworkManager[954]: <info>  [1496776516.1403] dhcp4 (enp0s20f0u5u5): state changed unknown -> bound
Jun 06 21:15:16 wnlpos4-bg avahi-daemon[627]: Joining mDNS multicast group on interface enp0s20f0u5u5.IPv4 with address 172.18.238.33.
Jun 06 21:15:16 wnlpos4-bg avahi-daemon[627]: New relevant interface enp0s20f0u5u5.IPv4 for mDNS.
Jun 06 21:15:16 wnlpos4-bg avahi-daemon[627]: Registering new address record for 172.18.238.33 on enp0s20f0u5u5.IPv4.
Jun 06 21:15:16 wnlpos4-bg NetworkManager[954]: <info>  [1496776516.1430] device (enp0s20f0u5u5): state change: ip-config -> ip-check (reason 'none') [70 80 0]
Jun 06 21:15:16 wnlpos4-bg dhclient[19169]: bound to 172.18.238.33 -- renewal in 306254 seconds.
Jun 06 21:15:16 wnlpos4-bg NetworkManager[954]: <info>  [1496776516.1486] device (enp0s20f0u5u5): state change: ip-check -> secondaries (reason 'none') [80 90 0]
Jun 06 21:15:16 wnlpos4-bg NetworkManager[954]: <info>  [1496776516.1488] device (enp0s20f0u5u5): state change: secondaries -> activated (reason 'none') [90 100 0]
Jun 06 21:15:16 wnlpos4-bg NetworkManager[954]: <info>  [1496776516.1489] manager: NetworkManager state is now CONNECTED_LOCAL
Jun 06 21:15:16 wnlpos4-bg nm-dispatcher[19160]: req:2 'connectivity-change': new request (4 scripts)
Jun 06 21:15:16 wnlpos4-bg nm-dispatcher[19160]: req:2 'connectivity-change': start running ordered scripts...
Jun 06 21:15:16 wnlpos4-bg NetworkManager[954]: <info>  [1496776516.1539] manager: NetworkManager state is now CONNECTED_GLOBAL
Jun 06 21:15:16 wnlpos4-bg NetworkManager[954]: <info>  [1496776516.1540] policy: set 'Wired connection 1' (enp0s20f0u5u5) as default for IPv4 routing and DNS
Jun 06 21:15:16 wnlpos4-bg NetworkManager[954]: <info>  [1496776516.1572] device (enp0s20f0u5u5): Activation: successful, device activated.
Jun 06 21:15:16 wnlpos4-bg nm-dispatcher[19160]: req:3 'up' [enp0s20f0u5u5]: new request (4 scripts)
Jun 06 21:15:16 wnlpos4-bg nm-dispatcher[19160]: req:3 'up' [enp0s20f0u5u5]: start running ordered scripts...
Jun 06 21:15:16 wnlpos4-bg systemd[1]: Unit iscsi.service cannot be reloaded because it is inactive.
Jun 06 21:15:17 wnlpos4-bg avahi-daemon[627]: Registering new address record for fe80::ddb6:aa23:9e0a:fd61 on enp0s20f0u5u5.*.


And this is the stndout of ip addr, so nothing to be worried here obviously:
5: enp0s20f0u5u5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
   link/ether 00:80:0f:78:50:00 brd ff:ff:ff:ff:ff:ff
   inet 172.18.238.33/24 brd 172.18.238.255 scope global dynamic enp0s20f0u5u5
      valid_lft 691120sec preferred_lft 691120sec
   inet6 fe80::ddb6:aa23:9e0a:fd61/64 scope link
      valid_lft forever preferred_lft forever

Thanks and best!  Björn

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.elrepo.org/pipermail/elrepo/attachments/20170606/51ceda0b/attachment-0001.html>


More information about the elrepo mailing list