Asus h170m-e d3 problem with pci network card

Issues related to hardware problems
JohnK2020
Posts: 19
Joined: 2018/06/27 12:08:17

Re: Asus h170m-e d3 problem with pci network card

Post by JohnK2020 » 2018/06/27 15:33:44

With 8139too:

Code: Select all

# lspci -v

02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8100/8101L/8139 PCI Fast Ethernet Adapter (rev 10)
        Subsystem: Realtek Semiconductor Co., Ltd. RTL-8100/8101L/8139 PCI Fast Ethernet Adapter
        Flags: bus master, medium devsel, latency 32, IRQ 18
        I/O ports at 2000 [size=256]
        Memory at c8010000 (32-bit, non-prefetchable) [size=256]
        [virtual] Expansion ROM at c8000000 [disabled] [size=64K]
        Kernel driver in use: [size=150][b]8139too[/b][/size]
        Kernel modules: 8139cp, 8139too

03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
        Subsystem: ASUSTeK Computer Inc. Device 8677
        Flags: bus master, fast devsel, latency 0, IRQ 124
        I/O ports at e000 [size=256]
        Memory at f7004000 (64-bit, non-prefetchable) [size=4K]
        Memory at f7000000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: [40] Power Management version 3
        Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
        Capabilities: [70] Express Endpoint, MSI 01
        Capabilities: [b0] MSI-X: Enable- Count=4 Masked-
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [140] Virtual Channel
        Capabilities: [160] Device Serial Number 01-00-00-00-68-4c-e0-00
        Capabilities: [170] Latency Tolerance Reporting
        Capabilities: [178] L1 PM Substates
        Kernel driver in use: r8168
        Kernel modules: r8169, r8168

But with 8139cp there is no driver in use

Code: Select all

02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8100/8101L/8139 PCI Fast Ethernet Adapter (rev 10)
        Subsystem: Realtek Semiconductor Co., Ltd. RTL-8100/8101L/8139 PCI Fast Ethernet Adapter
        Flags: medium devsel, IRQ 18
        I/O ports at 2000 [size=256]
        Memory at c8010000 (32-bit, non-prefetchable) [size=256]
        [virtual] Expansion ROM at c8000000 [disabled] [size=64K]
        Kernel modules: 8139cp, 8139too

03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
        Subsystem: ASUSTeK Computer Inc. Device 8677
        Flags: bus master, fast devsel, latency 0, IRQ 124
        I/O ports at e000 [size=256]
        Memory at f7004000 (64-bit, non-prefetchable) [size=4K]
        Memory at f7000000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: [40] Power Management version 3
        Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
        Capabilities: [70] Express Endpoint, MSI 01
        Capabilities: [b0] MSI-X: Enable- Count=4 Masked-
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [140] Virtual Channel
        Capabilities: [160] Device Serial Number 01-00-00-00-68-4c-e0-00
        Capabilities: [170] Latency Tolerance Reporting
        Capabilities: [178] L1 PM Substates
        Kernel driver in use: r8168
        Kernel modules: r8169, r8168


And what lshw outputs:

Code: Select all

 lshw -C network
  *-network UNCLAIMED
       description: Ethernet controller
       product: RTL-8100/8101L/8139 PCI Fast Ethernet Adapter
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 0
       bus info: pci@0000:02:00.0
       version: 10
       width: 32 bits
       clock: 33MHz
       configuration: latency=32 maxlatency=64 mingnt=32
       resources: ioport:2000(size=256) memory:c8010000-c80100ff memory:c8000000-c800ffff
  *-network
       description: Ethernet interface
       product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 0
       bus info: pci@0000:03:00.0
       logical name: enp3s0
       version: 15
       serial: 70:8b:cd:7f:2e:11
       size: 100Mbit/s
       capacity: 1Gbit/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=r8168 driverversion=8.045.08-NAPI duplex=full ip=192.168.10.210 latency=0 link=yes multicast=yes port=twisted pair speed=100Mbit/s
       resources: irq:124 ioport:e000(size=256) memory:f7004000-f7004fff memory:f7000000-f7003fff

No device name assigned because of no suitable driver loaded I suppose
Maybe problem is not with NIC but with chipset ?
I tried different cards and relult all the same - no ping, no traffic (
And no messages in dmesg

User avatar
TrevorH
Site Admin
Posts: 33202
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: Asus h170m-e d3 problem with pci network card

Post by TrevorH » 2018/06/27 15:36:16

Look in dmesg for errors please.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke

JohnK2020
Posts: 19
Joined: 2018/06/27 12:08:17

Re: Asus h170m-e d3 problem with pci network card

Post by JohnK2020 » 2018/06/27 15:49:35

These are all errors I could find in dmesg:

Code: Select all

[    0.017759] ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20130517/dswload-194)
[    0.113521] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
[    0.139293] pci 0000:02:00.0: BAR 1: error updating (0xc8010000 != 0xc0010000)

[    0.458257] ACPI Error: No object attached to node ffff932bef433e88 (20130517/exresnte-127)
[    0.458261] ACPI Error: Method parse/execution failed [\_SB_.PCI0.XHC_.RHUB.HS01._PLD] (Node ffff932bef433ed8), AE_AML_NO_
[    0.458700] ACPI Error: No object attached to node ffff932bef433e88 (20130517/exresnte-127)
[    0.458702] ACPI Error: Method parse/execution failed [\_SB_.PCI0.XHC_.RHUB.HS02._PLD] (Node ffff932bef433f28), AE_AML_NO_
[    0.459156] ACPI Error: No object attached to node ffff932bef433e88 (20130517/exresnte-127)
[    0.459158] ACPI Error: Method parse/execution failed [\_SB_.PCI0.XHC_.RHUB.HS03._PLD] (Node ffff932bef433f78), AE_AML_NO_
[    0.459593] ACPI Error: No object attached to node ffff932bef433e88 (20130517/exresnte-127)
[    0.459595] ACPI Error: Method parse/execution failed [\_SB_.PCI0.XHC_.RHUB.HS04._PLD] (Node ffff932bef433fc8), AE_AML_NO_
[    0.460049] ACPI Error: No object attached to node ffff932bef433e88 (20130517/exresnte-127)
[    0.460051] ACPI Error: Method parse/execution failed [\_SB_.PCI0.XHC_.RHUB.HS05._PLD] (Node ffff932bef436028), AE_AML_NO_
[    0.460486] ACPI Error: No object attached to node ffff932bef433e88 (20130517/exresnte-127)
[    0.460488] ACPI Error: Method parse/execution failed [\_SB_.PCI0.XHC_.RHUB.HS06._PLD] (Node ffff932bef436078), AE_AML_NO_
[    0.460939] ACPI Error: No object attached to node ffff932bef433e88 (20130517/exresnte-127)
[    0.460941] ACPI Error: Method parse/execution failed [\_SB_.PCI0.XHC_.RHUB.HS07._PLD] (Node ffff932bef4360c8), AE_AML_NO_
[    0.461375] ACPI Error: No object attached to node ffff932bef433e88 (20130517/exresnte-127)
[    0.461377] ACPI Error: Method parse/execution failed [\_SB_.PCI0.XHC_.RHUB.HS08._PLD] (Node ffff932bef436118), AE_AML_NO_
[    0.461830] ACPI Error: No object attached to node ffff932bef433e88 (20130517/exresnte-127)
[    0.461832] ACPI Error: Method parse/execution failed [\_SB_.PCI0.XHC_.RHUB.HS09._PLD] (Node ffff932bef436168), AE_AML_NO_
[    0.462266] ACPI Error: No object attached to node ffff932bef433e88 (20130517/exresnte-127)
[    0.462268] ACPI Error: Method parse/execution failed [\_SB_.PCI0.XHC_.RHUB.HS10._PLD] (Node ffff932bef4361b8), AE_AML_NO_


JohnK2020
Posts: 19
Joined: 2018/06/27 12:08:17

Re: Asus h170m-e d3 problem with pci network card

Post by JohnK2020 » 2018/06/27 15:50:54

I should do it in my first message:

Code: Select all

Linux localhost.localdomain 3.10.0-862.3.3.el7.x86_64 #1 SMP Fri Jun 15 04:15:27 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

User avatar
TrevorH
Site Admin
Posts: 33202
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: Asus h170m-e d3 problem with pci network card

Post by TrevorH » 2018/06/27 16:05:40

I meant specifically from loading the 8139cp or 8139too modules. So look at the output from dmesg (or in /var/log/messages) then modprobe -r one and modprobe the other then look in the same place for new messages since you looked the first time.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke

JohnK2020
Posts: 19
Joined: 2018/06/27 12:08:17

Re: Asus h170m-e d3 problem with pci network card

Post by JohnK2020 » 2018/06/27 16:23:24

I think the problem not with my card or its driver but with pci slot.
Maybe this is my case: viewtopic.php?t=6925

Loading & unloading drivers gives no messages, just at startup:

Code: Select all

Jun 27 19:09:24 localhost NetworkManager[848]: <warn>  [1530115764.6495] device (enp2s0): Activation: failed for connection 'enp2s0'
Jun 27 19:09:24 localhost NetworkManager[848]: <info>  [1530115764.6504] device (enp2s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Jun 27 19:09:31 localhost NetworkManager[848]: <info>  [1530115771.5835] device (enp2s0): state change: disconnected -> unmanaged (reason 'removed', sys-iface-state: 'removed')

JohnK2020
Posts: 19
Joined: 2018/06/27 12:08:17

Re: Asus h170m-e d3 problem with pci network card

Post by JohnK2020 » 2018/06/27 17:55:59

As a variant I tested loading Kali linux 4.13.0 (Debian 6.4.0-9) from usb stick
The problem is the same - no traffic flows.
In /var/log/messages found just:

Code: Select all

8139cp: 000:02:00.0: This (id 10ec:8139 rev 10) is not an 8139C+ compartible chip, use 8139too

JohnK2020
Posts: 19
Joined: 2018/06/27 12:08:17

Re: Asus h170m-e d3 problem with pci network card

Post by JohnK2020 » 2018/06/28 08:06:38

Maybe it will help

Code: Select all

dmesg | grep -Ei -C2 'enp|ethernet|realtek|8139'
[    0.115923] pci 0000:01:00.0: System wakeup disabled by ACPI
[    0.115945] pci 0000:00:1c.0: PCI bridge to [bus 01-02]
[    0.116004] pci 0000:02:00.0: [10ec:8139] type 00 class 0x020000
[    0.116022] pci 0000:02:00.0: reg 0x10: [io  0x0000-0x00ff]
[    0.116031] pci 0000:02:00.0: reg 0x14: [mem 0x00000000-0x000000ff]
--
[    0.662521] device-mapper: uevent: version 1.0.3
[    0.662595] device-mapper: ioctl: 4.37.0-ioctl (2017-09-20) initialised: dm-devel@redhat.com
[    0.818733] 8139cp: 8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004)
[    0.818748] 8139cp 0000:02:00.0: This (id 10ec:8139 rev 10) is not an 8139C+ compatible chip, use 8139too
[    0.821314] usb 1-9: new low-speed USB device number 2 using xhci_hcd
[    0.822850] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[    0.822855] r8169 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control
[    0.826313] r8169 0000:03:00.0: irq 121 for MSI/MSI-X
[    0.827033] r8169 0000:03:00.0 eth0: RTL8168h/8111h at 0xffffb3a10066e000, 70:8b:cd:7f:2e:b5, XID 14100800 IRQ 121
[    0.827036] r8169 0000:03:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
[    0.834108] 8139too: 8139too Fast Ethernet driver 0.9.28
[    0.834193] 8139too 0000:02:00.0: enabling device (0000 -> 0003)
[    0.835116] 8139too 0000:02:00.0 eth1: RealTek RTL8139 at 0xffffb3a100670000, 00:1e:2c:5a:05:44, IRQ 18
[    0.844246] libata version 3.00 loaded.
[    0.867566] ahci 0000:00:17.0: version 3.0
--
[    6.174365] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[    6.205528] snd_hda_intel 0000:00:1f.3: irq 125 for MSI/MSI-X
[    6.266222] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC887-VD: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:line
[    6.266234] snd_hda_codec_realtek hdaudioC0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[    6.266242] snd_hda_codec_realtek hdaudioC0D0:    hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
[    6.266248] snd_hda_codec_realtek hdaudioC0D0:    mono: mono_out=0x0
[    6.266253] snd_hda_codec_realtek hdaudioC0D0:    dig-out=0x11/0x0
[    6.266258] snd_hda_codec_realtek hdaudioC0D0:    inputs:
[    6.266265] snd_hda_codec_realtek hdaudioC0D0:      Front Mic=0x19
[    6.266271] snd_hda_codec_realtek hdaudioC0D0:      Rear Mic=0x18
[    6.266277] snd_hda_codec_realtek hdaudioC0D0:      Line=0x1a
[    6.295824] cryptd: max_cpu_qlen set to 100
[    6.331385] Adding 3932156k swap on /dev/mapper/centos-swap.  Priority:-1 extents:1 across:3932156k FS
--
[    7.477483] type=1305 audit(1530171946.492:3): audit_pid=810 old=0 auid=4294967295 ses=4294967295 res=1
[    7.746324] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[    8.266492] 8139too 0000:02:00.0 enp2s0: link up, 100Mbps, full-duplex, lpa 0xFFFF
[   12.444235] r8169 0000:03:00.0 enp3s0: link down
[   12.444351] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[   18.413457] PPP generic driver version 2.4.2
[   20.724444] ------------[ cut here ]------------
[   20.724469] WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:356 dev_watchdog+0x248/0x260
[   20.724477] NETDEV WATCHDOG: enp2s0 (8139too): transmit queue 0 timed out
[   20.724482] Modules linked in: ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_log_ipv4 nf_log_common xt_LOG iptable_nat nf_nat_ipv4 nf_nat ppp_synctty ppp_async crc_ccitt ppp_generic slhc ipt_REJECT nf_reject_ipv4 nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack iptable_filter intel_powerclamp coretemp intel_rapl kvm irqbypass crc32_pclmul ghash_clmulni_intel aesni_intel lrw gf128mul glue_helper ablk_helper snd_hda_codec_hdmi cryptd snd_hda_codec_realtek snd_hda_codec_generic iTCO_wdt mei_wdt iTCO_vendor_support eeepc_wmi asus_wmi ppdev sparse_keymap rfkill snd_hda_intel mxm_wmi snd_hda_codec snd_hda_core snd_hwdep snd_seq snd_seq_device snd_pcm snd_timer sg snd pcspkr i2c_i801 soundcore joydev shpchp parport_pc parport mei_me mei pinctrl_sunrisepoint pinctrl_intel acpi_pad wmi ip_tables xfs
[   20.724592]  libcrc32c raid1 sr_mod cdrom sd_mod crc_t10dif crct10dif_generic i915 iosf_mbi i2c_algo_bit drm_kms_helper ahci syscopyarea sysfillrect sysimgblt fb_sys_fops libahci drm crct10dif_pclmul crct10dif_common 8139too libata crc32c_intel serio_raw r8169 8139cp mii video i2c_hid i2c_core dm_mirror dm_region_hash dm_log dm_mod
[   20.724645] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.10.0-862.3.3.el7.x86_64 #1
[   20.724652] Hardware name: System manufacturer System Product Name/H170M-E D3, BIOS 2001 09/22/2016
--
[   20.724961]  [<ffffffffa0a000d5>] start_cpu+0x5/0x14
[   20.724967] ---[ end trace 759ef0f12ce0625b ]---
[   23.744202] 8139too 0000:02:00.0 enp2s0: link up, 100Mbps, full-duplex, lpa 0xFFFF
[   35.744203] 8139too 0000:02:00.0 enp2s0: link up, 100Mbps, full-duplex, lpa 0xFFFF
[   47.744205] 8139too 0000:02:00.0 enp2s0: link up, 100Mbps, full-duplex, lpa 0xFFFF
[   84.938144] tun: Universal TUN/TAP device driver, 1.6
[   84.938152] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[   95.744295] 8139too 0000:02:00.0 enp2s0: link up, 100Mbps, full-duplex, lpa 0xFFFF
[  107.744410] 8139too 0000:02:00.0 enp2s0: link up, 100Mbps, full-duplex, lpa 0xFFFF
[  119.744518] 8139too 0000:02:00.0 enp2s0: link up, 100Mbps, full-duplex, lpa 0xFFFF
[  131.744617] 8139too 0000:02:00.0 enp2s0: link up, 100Mbps, full-duplex, lpa 0xFFFF
[  143.744797] 8139too 0000:02:00.0 enp2s0: link up, 100Mbps, full-duplex, lpa 0xFFFF
[  155.744847] 8139too 0000:02:00.0 enp2s0: link up, 100Mbps, full-duplex, lpa 0xFFFF
[  167.744985] 8139too 0000:02:00.0 enp2s0: link up, 100Mbps, full-duplex, lpa 0xFFFF
[  179.745097] 8139too 0000:02:00.0 enp2s0: link up, 100Mbps, full-duplex, lpa 0xFFFF
[  191.745223] 8139too 0000:02:00.0 enp2s0: link up, 100Mbps, full-duplex, lpa 0xFFFF
[  203.745332] 8139too 0000:02:00.0 enp2s0: link up, 100Mbps, full-duplex, lpa 0xFFFF
[  215.745431] 8139too 0000:02:00.0 enp2s0: link up, 100Mbps, full-duplex, lpa 0xFFFF
[  227.745545] 8139too 0000:02:00.0 enp2s0: link up, 100Mbps, full-duplex, lpa 0xFFFF
[  331.652547] r8169 0000:03:00.0 enp3s0: link down
[  331.652652] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[  348.088327] r8169 0000:03:00.0 enp3s0: link up
[  348.088346] IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready

JohnK2020
Posts: 19
Joined: 2018/06/27 12:08:17

Re: Asus h170m-e d3 problem with pci network card

Post by JohnK2020 » 2018/06/28 23:08:53

Code: Select all

yum --enablerepo=elrepo-kernel install kernel-ml
Even with this kernel i have the same error :(

Post Reply