25794 – r8169 still does not working properly with some realtek controllers, working after rmmode-modprobe in rc.local only

Bug 25794 - r8169 still does not working properly with some realtek controllers, working after rmmode-modprobe in rc.local only

Summary: r8169 still does not working properly with some realtek controllers, working ...

Status:	RESOLVED OLD

Alias:	None

Product:	Mageia
Classification:	Unclassified
Component:	RPM Packages (show other bugs)
Version:	8
Hardware:	x86_64 Linux

Priority:	Normal Severity: normal
Target Milestone:	---
Assignee:	Kernel and Drivers maintainers
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2019-12-02 01:26 CET by Levchenko Roman
Modified:	2024-08-22 23:02 CEST (History)
CC List:	6 users (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
dmesg_out without r8169 restarting (89.08 KB, text/plain) 2021-08-26 20:39 CEST, Levchenko Roman	Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Levchenko Roman 2019-12-02 01:26:44 CET

Description of problem:

Ethernet cards:
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 02)
        Subsystem: Gigabyte Technology Co., Ltd Onboard Ethernet
        Flags: bus master, fast devsel, latency 0, IRQ 17
        I/O ports at ee00 [size=256]
        Memory at fdbff000 (64-bit, prefetchable) [size=4K]
        Memory at fdbe0000 (64-bit, prefetchable) [size=64K]
        [virtual] Expansion ROM at fdc00000 [disabled] [size=64K]
        Capabilities: [40] Power Management version 3
        Capabilities: [50] MSI: Enable- Count=1/2 Maskable- 64bit+
        Capabilities: [70] Express Endpoint, MSI 01
        Capabilities: [b0] MSI-X: Enable- Count=2 Masked-
        Capabilities: [d0] Vital Product Data
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [140] Virtual Channel
        Capabilities: [160] Device Serial Number 12-34-56-78-12-34-56-78
        Kernel driver in use: r8169
        Kernel modules: r8169
motherboard Gigabyte EP45-UD3LR with onboard Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller - it doesn't work even after module r8169 reload, so it disconnected

05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8169 PCI Gigabit Ethernet Controller (rev 10)
        Subsystem: Realtek Semiconductor Co., Ltd. RTL8169/8110 Family PCI Gigabit Ethernet NIC
        Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 20
        I/O ports at de00 [size=256]
        Memory at fddff000 (32-bit, non-prefetchable) [size=256]
        [virtual] Expansion ROM at fdd00000 [disabled] [size=128K]
        Capabilities: [dc] Power Management version 2
        Kernel driver in use: r8169
        Kernel modules: r8169
the second card - expansion card RTL8169 PCI Gigabit Ethernet Controller, this card starts work after module r8169 reload 

So. now I have to use rc.local with rmmode-modprobe about r8169, because Ethernet Controllers don't work nominally.

Maybe I'm doing something wrong?

Thanks.
Version-Release number of selected component (if applicable):


How reproducible: take the ethernet controllers, named before, install Mageia7, and try to connect after system loaded.


Steps to Reproduce:
1. take the ethernet cards with realtek chipsets, named in discription
2. install Mageia7
3. Try to connect

Comment 1 Alexander Krylov 2019-12-02 08:00:42 CET

Out of curiosity, do you have a kernel-firmware-nonfree-20190926-1.mga7.nonfree.noarch package installed in your system?

Just asking, because I have a GA-P43T-ES3G motherboard with similar integrated Ethernet controller and can't reproduce your problem.
  *-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:04:00.0
       logical name: eth0
       version: 03
       serial: 1c:6f:65:a2:c8:6a
       size: 100Mbit/s
       capacity: 1Gbit/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix vpd bus_master cap_list rom ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=r8169 duplex=full firmware=rtl_nic/rtl8168d-2.fw ip=10.10x.11x.255 latency=0 link=yes multicast=yes port=MII speed=100Mbit/s
       resources: irq:17 ioport:ee00(size=256) memory:dfbff000-dfbfffff memory:dfbf8000-dfbfbfff memory:dfc00000-dfc1ffff

CC: (none) => kafra2005

Comment 2 Levchenko Roman 2019-12-02 11:50:06 CET

(In reply to Alexander Krylov from comment #1)
> Out of curiosity, do you have a
> kernel-firmware-nonfree-20190926-1.mga7.nonfree.noarch package installed in
> your system?
> 

Good day. I'll check about package you've named, thanks.

But:
I have 3 netcards on another mashine:
1. D-Link System Inc DGE-528T Gigabit Ethernet Adapter - expansion card,
with DLG10028C chip (analog Realtek);
2. Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller - onboard (GIGABYTE GA-H81M-S2H motheboard),
serial 40-8D-5C-02-E1-50;
3. Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller - expansion card,
serial 98-DE-D0-01-E6-A3 (TP-Link) - works properly.
All three cards use r8169 module.
Two of them, (1 and 2) - don't work after upgrade from Mageia6 to Mageia7, even indicators on cards are dead, but 
after reload module 
rmmod r8169
modprobe r8169
the Realtek-cards work nice... till next reboot.
All updates on 01.12.2019 - installed.

P.S.
A little offtop: deja vu about tg3 module and Broadcom netcards...

Comment 3 Levchenko Roman 2019-12-02 18:37:40 CET

(In reply to Alexander Krylov from comment #1)
> Out of curiosity, do you have a
> kernel-firmware-nonfree-20190926-1.mga7.nonfree.noarch package installed in
> your system?
> 

Yes, this package has been installed, so, it's not the reason.

Comment 4 Lewis Smith 2019-12-02 19:39:18 CET

@ Levchenko : please say what kernel you are using.
@ Alexander : thank you for your helpful contribution.

Assigning to kernel/drivers.

Assignee: bugsquad => kernel

Comment 5 Levchenko Roman 2019-12-03 00:43:40 CET

(In reply to Lewis Smith from comment #4)
> @ Levchenko : please say what kernel you are using.
> @ Alexander : thank you for your helpful contribution.
> 
> Assigning to kernel/drivers.

God day.

kernel-desktop-5.3.13-2

Comment 6 Levchenko Roman 2019-12-14 20:25:43 CET

Good day.

The last kernel update to kernel-desktop-5.4.2-1, unfortunately, did not solve a problem with r8169.

Comment 7 Thomas Backlund 2019-12-14 20:49:40 CET

please provide output of lspcidrake -v

CC: (none) => tmb

Comment 8 Levchenko Roman 2019-12-14 22:15:41 CET

(In reply to Thomas Backlund from comment #7)
> please provide output of lspcidrake -v

Good day.
This is report of lspcidrake -v on computer, described in first post (description):

[**************]$ lspcidrake -v
ehci_pci        : Intel Corporation|82801JI (ICH10 Family) USB2 EHCI Controller #1 [SERIAL_USB] (vendor:8086 device:3a3a subv:1458 subd:5006)
r8169           : Realtek Semiconductor Co., Ltd.|RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [NETWORK_ETHERNET] (vendor:10ec device:8168 subv:1458 subd:e000) (rev: 02)
unknown         : Intel Corporation|82801JI (ICH10 Family) PCI Express Root Port 5 [BRIDGE_PCI] (vendor:8086 device:3a48)
ehci_pci        : Intel Corporation|82801JI (ICH10 Family) USB2 EHCI Controller #2 [SERIAL_USB] (vendor:8086 device:3a3c subv:1458 subd:5006)
snd_hda_intel   : NVIDIA Corporation|High Definition Audio Controller [MULTIMEDIA_AUDIO_DEV] (vendor:10de device:0be3 subv:1043 subd:8334) (rev: a1)
uhci_hcd        : Intel Corporation|82801JI (ICH10 Family) USB UHCI Controller #1 [SERIAL_USB] (vendor:8086 device:3a34 subv:1458 subd:5004)
r8169           : Realtek Semiconductor Co., Ltd.|RTL8169 PCI Gigabit Ethernet Controller [NETWORK_ETHERNET] (vendor:10ec device:8169) (rev: 10)
uhci_hcd        : Intel Corporation|82801JI (ICH10 Family) USB UHCI Controller #4 [SERIAL_USB] (vendor:8086 device:3a37 subv:1458 subd:5004)
uhci_hcd        : Intel Corporation|82801JI (ICH10 Family) USB UHCI Controller #3 [SERIAL_USB] (vendor:8086 device:3a36 subv:1458 subd:5004)
uhci_hcd        : Intel Corporation|82801JI (ICH10 Family) USB UHCI Controller #6 [SERIAL_USB] (vendor:8086 device:3a39 subv:1458 subd:5004)
unknown         : Intel Corporation|4 Series Chipset DRAM Controller [BRIDGE_HOST] (vendor:8086 device:2e20 subv:1458 subd:5000) (rev: 03)
i2c_i801        : Intel Corporation|82801JI (ICH10 Family) SMBus Controller [SERIAL_SMBUS] (vendor:8086 device:3a30 subv:1458 subd:5001)
unknown         : Intel Corporation|82801 PCI Bridge [BRIDGE_PCI] (vendor:8086 device:244e) (rev: 90)
snd_hda_intel   : Intel Corporation|82801JI (ICH10 Family) HD Audio Controller [MULTIMEDIA_AUDIO_DEV] (vendor:8086 device:3a3e subv:1458 subd:a002)
Card:NVIDIA GeForce 8100 to GeForce 415: NVIDIA Corporation|GT218 [GeForce 210] [DISPLAY_VGA] (vendor:10de device:0a65 subv:1043 subd:8334) (rev: a2)
unknown         : Intel Corporation|82801JI (ICH10 Family) PCI Express Root Port 6 [BRIDGE_PCI] (vendor:8086 device:3a4a)
uhci_hcd        : Intel Corporation|82801JI (ICH10 Family) USB UHCI Controller #2 [SERIAL_USB] (vendor:8086 device:3a35 subv:1458 subd:5004)
unknown         : Intel Corporation|4 Series Chipset PCI Express Root Port [BRIDGE_PCI] (vendor:8086 device:2e21) (rev: 03)
lpc_ich         : Intel Corporation|82801JIR (ICH10R) LPC Interface Controller [BRIDGE_ISA] (vendor:8086 device:3a16 subv:1458 subd:5001)
uhci_hcd        : Intel Corporation|82801JI (ICH10 Family) USB UHCI Controller #5 [SERIAL_USB] (vendor:8086 device:3a38 subv:1458 subd:5004)
unknown         : Intel Corporation|82801JI (ICH10 Family) PCI Express Root Port 1 [BRIDGE_PCI] (vendor:8086 device:3a40)
unknown         : Intel Corporation|82801JI (ICH10 Family) SATA AHCI Controller [STORAGE_SATA] (vendor:8086 device:3a22 subv:1458 subd:b005)
pata_jmicron    : JMicron Technology Corp.|JMB368 IDE controller [STORAGE_IDE] (vendor:197b device:2368 subv:1458 subd:b000)
hub             : Linux 5.4.2-desktop-1.mga7 ehci_hcd|EHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0002)
hub             : Terminus Technology Inc.|USB 2.0 Hub [Hub|Unused|Full speed (or root) hub] (vendor:1a40 device:0101)
hub             : Linux 5.4.2-desktop-1.mga7 ehci_hcd|EHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0002)
hub             : Linux 5.4.2-desktop-1.mga7 uhci_hcd|UHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0001)
hub             : Linux 5.4.2-desktop-1.mga7 uhci_hcd|UHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0001)
usbhid          : Genius|Optical Mouse [Human Interface Device|Boot Interface Subclass|Mouse] (vendor:0458 device:003a)
hub             : Linux 5.4.2-desktop-1.mga7 uhci_hcd|UHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0001)
usbfs           : Powerware|Powerware UPS (vendor:0592 device:0002)
usbhid          : USB|USB Keykoard [Human Interface Device|Boot Interface Subclass|Keyboard] (vendor:1a2c device:0021)
hub             : Linux 5.4.2-desktop-1.mga7 uhci_hcd|UHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0001)
hub             : Linux 5.4.2-desktop-1.mga7 uhci_hcd|UHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0001)
hub             : Linux 5.4.2-desktop-1.mga7 uhci_hcd|UHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0001)
hid_generic     : USB USB Keykoard
hid_generic     : Genius Optical Mouse
hid_generic     : USB USB Keykoard

Comment 9 Levchenko Roman 2019-12-14 22:27:26 CET

(In reply to Thomas Backlund from comment #7)
> please provide output of lspcidrake -v

And here is a report on computer, described in the Comment2 

[***************]$ lspcidrake -v
unknown         : Intel Corporation|8 Series/C220 Series Chipset Family PCI Express Root Port #3 [BRIDGE_PCI] (vendor:8086 device:8c14) (rev: d5)
xhci_pci        : Intel Corporation|8 Series/C220 Series Chipset Family USB xHCI [SERIAL_USB] (vendor:8086 device:8c31 subv:1458 subd:5007) (rev: 05)
xhci_pci        : VIA Technologies, Inc.|VL805 USB 3.0 Host Controller [SERIAL_USB] (vendor:1106 device:3483 subv:1458 subd:5007) (rev: 01)
unknown         : Intel Corporation|8 Series/C220 Series Chipset Family PCI Express Root Port #5 [BRIDGE_PCI] (vendor:8086 device:8c18) (rev: d5)
snd_hda_intel   : NVIDIA Corporation|GK208 HDMI/DP Audio Controller [MULTIMEDIA_AUDIO_DEV] (vendor:10de device:0e0f subv:1462 subd:8c93) (rev: a1)
ehci_pci        : Intel Corporation|8 Series/C220 Series Chipset Family USB EHCI #1 [SERIAL_USB] (vendor:8086 device:8c26 subv:1458 subd:5006) (rev: 05)
r8169           : D-Link System Inc|DGE-528T Gigabit Ethernet Adapter [NETWORK_ETHERNET] (vendor:1186 device:4300 subv:1186 subd:4b10) (rev: 06)
ehci_pci        : Intel Corporation|8 Series/C220 Series Chipset Family USB EHCI #2 [SERIAL_USB] (vendor:8086 device:8c2d subv:1458 subd:5006) (rev: 05)
r8169           : Realtek Semiconductor Co., Ltd.|RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [NETWORK_ETHERNET] (vendor:10ec device:8168 subv:7470 subd:3468) (rev: 06)
unknown         : Intel Corporation|4th Gen Core Processor DRAM Controller [BRIDGE_HOST] (vendor:8086 device:0c00 subv:1458 subd:5000) (rev: 06)
i2c_i801        : Intel Corporation|8 Series/C220 Series Chipset Family SMBus Controller [SERIAL_SMBUS] (vendor:8086 device:8c22 subv:1458 subd:5001) (rev: 05)
unknown         : Intel Corporation|8 Series/C220 Series Chipset Family PCI Express Root Port #4 [BRIDGE_PCI] (vendor:8086 device:8c16) (rev: d5)
snd_hda_intel   : Intel Corporation|8 Series/C220 Series Chipset High Definition Audio Controller [MULTIMEDIA_AUDIO_DEV] (vendor:8086 device:8c20 subv:1458 subd:a002) (rev: 05)
Card:NVIDIA GeForce 635 series and later: NVIDIA Corporation|GK208B [GeForce GT 710] [DISPLAY_VGA] (vendor:10de device:128b subv:1462 subd:8c93) (rev: a1)
mei_me          : Intel Corporation|8 Series/C220 Series Chipset Family MEI Controller #1 [COMMUNICATION_OTHER] (vendor:8086 device:8c3a subv:1458 subd:1c3a) (rev: 04)
unknown         : Intel Corporation|8 Series/C220 Series Chipset Family PCI Express Root Port #6 [BRIDGE_PCI] (vendor:8086 device:8c1a) (rev: d5)
unknown         : Intel Corporation|Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller [BRIDGE_PCI] (vendor:8086 device:0c01) (rev: 06)
lpc_ich         : Intel Corporation|H81 Express LPC Controller [BRIDGE_ISA] (vendor:8086 device:8c5c subv:1458 subd:5001) (rev: 05)
unknown         : Intel Corporation|8 Series/C220 Series Chipset Family PCI Express Root Port #1 [BRIDGE_PCI] (vendor:8086 device:8c10) (rev: d5)
unknown         : Intel Corporation|8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] [STORAGE_SATA] (vendor:8086 device:8c02 subv:1458 subd:b005) (rev: 05)
r8169           : Realtek Semiconductor Co., Ltd.|RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [NETWORK_ETHERNET] (vendor:10ec device:8168 subv:1458 subd:e000) (rev: 0c)
hub             : Linux 5.4.2-desktop-1.mga7 ehci_hcd|EHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0002)
hub             : Intel Corp.|Unknown [Hub|Unused|Full speed (or root) hub] (vendor:8087 device:8008)
hub             : Linux 5.4.2-desktop-1.mga7 xhci-hcd|xHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0002)
usbhid          : USB|USB Keykoard [Human Interface Device|Boot Interface Subclass|Keyboard] (vendor:1a2c device:0021)
usbhid          : Logitech|USB Optical Mouse [Human Interface Device|Boot Interface Subclass|Mouse] (vendor:046d device:c05a)
usbfs           : Powerware|Powerware UPS (vendor:0592 device:0002)
hub             : Linux 5.4.2-desktop-1.mga7 xhci-hcd|xHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0003)
hub             : Linux 5.4.2-desktop-1.mga7 ehci_hcd|EHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0002)
hub             : Intel Corp.|Unknown [Hub|Unused|Full speed (or root) hub] (vendor:8087 device:8000)
hub             : Linux 5.4.2-desktop-1.mga7 xhci-hcd|xHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0002)
hub             : VIA Labs, Inc.|USB2.0 Hub [Hub|Unused|Full speed (or root) hub] (vendor:2109 device:3431)
hub             : Linux 5.4.2-desktop-1.mga7 xhci-hcd|xHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0003)
hid_generic     : USB USB Keykoard
hid_generic     : Logitech USB Optical Mouse
hid_generic     : USB USB Keykoard

Comment 10 Levchenko Roman 2019-12-28 19:50:27 CET

Unfortunately, update to kernel-5.4.6-2.mga7 didn't help. The netcards behaves in the same way.

Comment 11 Giuseppe Ghibò 2019-12-29 18:16:41 CET

I don't know if this could help, or this is the specific case, but I had always some problems with r8169 on some card (e.g. two same cards of different laptops one works and the other don't). Especially with detection. Mostly the old behaviour was that every 1 out of 4 boots the card is not working. I.e. the card is detected but it doesn't trasmit any packet, like if it is was faulty. The solution was to reboot until it works properly (no way to get it working with a simple rmmod/insmod of the r8169  kernel module). It seems that after a certain kernel on one particular card this behaviour had changed, and the r8169 doens't transmit any packet not just 1 out of 4 boots, but ALL the times (I thought at the beginning to the iptables troubles, but either with older 1.6.2 or even newer 1.8.3 the behaviour was the same). After testing all the cables, switches, and even using Category 7 cables, I did some testing on this particular card, and seems that this behaviour changed between kernel (upstream) 4.19.28 and 4.19.32 (i.e. 4.19.28 was working, and 4.19.32 and beyond doesn't). As alternative, with the proprietary kernel module "r8168" (e.g. mirrored at https://github.com/mtorromeo/r8168) instead the card it's detected and works all the times (so it's not a faulty hardware, just have to add "blacklist r8169" and "alias eth0 r8168" in the right places, to avoid overlapping between r8168 and r8169 on the same hardware).

CC: (none) => ghibomgx

Comment 12 Levchenko Roman 2019-12-29 18:36:53 CET

(In reply to Giuseppe Ghibò from comment #11)
> I don't know if this could help, or this is the specific case, but I had
> always some problems with r8169 on some card (e.g. two same cards of
> different laptops one works and the other don't). Especially with detection.
> Mostly the old behaviour was that every 1 out of 4 boots the card is not
> working. I.e. the card is detected but it doesn't trasmit any packet, like
> if it is was faulty. The solution was to reboot until it works properly (no
> way to get it working with a simple rmmod/insmod of the r8169  kernel
> module). It seems that after a certain kernel on one particular card this
> behaviour had changed, and the r8169 doens't transmit any packet not just 1
> out of 4 boots, but ALL the times (I thought at the beginning to the
> iptables troubles, but either with older 1.6.2 or even newer 1.8.3 the
> behaviour was the same). After testing all the cables, switches, and even
> using Category 7 cables, I did some testing on this particular card, and
> seems that this behaviour changed between kernel (upstream) 4.19.28 and
> 4.19.32 (i.e. 4.19.28 was working, and 4.19.32 and beyond doesn't). As
> alternative, with the proprietary kernel module "r8168" (e.g. mirrored at
> https://github.com/mtorromeo/r8168) instead the card it's detected and works
> all the times (so it's not a faulty hardware, just have to add "blacklist
> r8169" and "alias eth0 r8168" in the right places, to avoid overlapping
> between r8168 and r8169 on the same hardware).


Thanks, but I'm afraid it is another case...
All Ethernet Controllers worked good before update to Mageia7.

Comment 13 Levchenko Roman 2019-12-29 18:46:00 CET

(In reply to Giuseppe Ghibò from comment #11)
> I don't know if this could help, or this is the specific case, but I had
>

In addition, computer, described in Comment 8, works with Mageia. from Mageia 3.

Comment 14 Adam Stiburek 2020-01-05 20:44:38 CET

I have same problem. After online upgrade from mga6 to mga7 my network controller (using r8169) did not work. It was on kernel 5.4.6.
Then I booted back to mga6 kernel 4.14.50, where it worked.
So I tried other kernel versions. 5.3.13 and 5.2.16 did not work, finally 5.1.20 works with r8169 module.
Apparently module r8169 does not work correctly since kernel 5.2+. If I look at kernel log, I see some backtrace thrown when starting network.

Attaching the kernel log (sorry for czech locale):
pro 29 17:06:40 localhost.localdomain systemd[1]: Starting LSB: Bring up/down networking...
pro 29 17:06:40 localhost.localdomain systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
pro 29 17:06:40 localhost.localdomain kernel: cfg80211: Loading compiled-in X.509 certificates for regulatory database
pro 29 17:06:40 localhost.localdomain kernel: cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
pro 29 17:06:41 localhost.localdomain network[887]: Spouštím rozhraní pro loopback:  [  OK  ]
pro 29 17:06:41 localhost.localdomain ifplugd(enp3s0)[1068]: ifplugd 0.28 initializing.
pro 29 17:06:41 localhost.localdomain network[887]: Spouštím rozhraní enp3s0:  [  OK  ]
pro 29 17:06:41 localhost.localdomain kernel: Generic FE-GE Realtek PHY r8169-300:00: attached PHY driver [Generic FE-GE Realtek PHY] (mii_bus:phy_addr=r8169-300:00, irq=IGNORE)
pro 29 17:06:41 localhost.localdomain ifplugd(enp3s0)[1068]: Using interface enp3s0/D8:CB:8A:9C:46:5D with driver <r8169> (version: )
pro 29 17:06:41 localhost.localdomain ifplugd(enp3s0)[1068]: Using detection mode: SIOCETHTOOL
pro 29 17:06:41 localhost.localdomain ifplugd(enp3s0)[1068]: Initialization complete, link beat not detected.
pro 29 17:06:41 localhost.localdomain kernel: r8169 0000:03:00.0 enp3s0: Link is Down
pro 29 17:06:41 localhost.localdomain systemd[1]: Started LSB: Bring up/down networking.
pro 29 17:06:41 localhost.localdomain audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=network comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
pro 29 17:06:41 localhost.localdomain kernel: audit: type=1130 audit(1577635601.265:50): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=network comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
pro 29 17:06:41 localhost.localdomain systemd[1]: Reached target Network.
pro 29 17:06:41 localhost.localdomain systemd[1]: Reached target Network is Online.
pro 29 17:06:42 localhost.localdomain kernel: r8169 0000:03:00.0 enp3s0: Link is Up - 100Mbps/Full - flow control rx/tx
pro 29 17:06:42 localhost.localdomain kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready
pro 29 17:06:43 localhost.localdomain ifplugd(enp3s0)[1068]: Link beat detected.
pro 29 17:06:44 localhost.localdomain ifplugd(enp3s0)[1068]: Executing '/etc/ifplugd/ifplugd.action enp3s0 up'.
pro 29 17:06:44 localhost.localdomain kernel: NET: Registered protocol family 17
pro 29 17:06:44 localhost.localdomain dhclient[1142]: DHCPREQUEST for 192.168.1.225 on enp3s0 to 255.255.255.255 port 67
pro 29 17:06:47 localhost.localdomain kernel: ------------[ cut here ]------------
pro 29 17:06:47 localhost.localdomain kernel: NETDEV WATCHDOG: enp3s0 (r8169): transmit queue 0 timed out
pro 29 17:06:47 localhost.localdomain kernel: WARNING: CPU: 1 PID: 0 at net/sched/sch_generic.c:448 dev_watchdog+0x239/0x240
pro 29 17:06:47 localhost.localdomain kernel: Modules linked in: af_packet cfg80211 rfkill binfmt_misc fuse intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi snd_hda_codec_realtek input_leds kvm snd_hda_codec_generic ledtrig_audio snd_hda_intel irqbypass snd_intel_nhlt snd_hda_codec snd_hda_core r8169 realtek crc32_pclmul crc32c_intel ghash_clmulni_intel libphy snd_hwdep snd_pcm snd_timer mei_hdcp iTCO_wdt snd i2c_i801 iTCO_vendor_support soundcore aesni_intel mei_me lpc_ich crypto_simd mei cryptd glue_helper intel_cstate intel_uncore intel_rapl_perf fan acpi_pad thermal evdev nvram xpad ff_memless sch_fq_codel ip_tables x_tables ipv6 crc_ccitt nf_defrag_ipv6 autofs4 hid_generic usbhid hid xhci_pci xhci_hcd ehci_pci ehci_hcd sr_mod firewire_ohci usbcore firewire_core crc_itu_t usb_common nouveau mxm_wmi i2c_algo_bit drm_kms_helper wmi ttm button video drm
pro 29 17:06:47 localhost.localdomain kernel: CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.4.6-desktop-2.mga7 #1
pro 29 17:06:47 localhost.localdomain kernel: Hardware name: MSI MS-7850/Z97 PC Mate(MS-7850), BIOS V4.10 08/11/2015
pro 29 17:06:47 localhost.localdomain kernel: RIP: 0010:dev_watchdog+0x239/0x240
pro 29 17:06:47 localhost.localdomain kernel: Code: 48 85 c0 75 e4 eb 9d 4c 89 ef c6 05 95 76 ad 00 01 e8 7b 24 fb ff 89 d9 4c 89 ee 48 c7 c7 10 49 16 a7 48 89 c2 e8 60 8c 83 ff <0f> 0b e9 7c ff ff ff 0f 1f 44 00 00 48 c7 47 08 00 00 00 00 48 c7
pro 29 17:06:47 localhost.localdomain kernel: RSP: 0018:ffffb4dec00f0e90 EFLAGS: 00010286
pro 29 17:06:47 localhost.localdomain kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
pro 29 17:06:47 localhost.localdomain kernel: RDX: ffff99394eaa7240 RSI: 00000000000000f6 RDI: 0000000000000300
pro 29 17:06:47 localhost.localdomain kernel: RBP: ffff9939489ea480 R08: 0000000000000371 R09: 0000000000aaaaaa
pro 29 17:06:47 localhost.localdomain kernel: R10: 0000000000000000 R11: ffff9939497f2b80 R12: 0000000000000001
pro 29 17:06:47 localhost.localdomain kernel: R13: ffff9939489ea000 R14: 0000000000000000 R15: ffffffffa7205100
pro 29 17:06:47 localhost.localdomain kernel: FS:  0000000000000000(0000) GS:ffff99394ea80000(0000) knlGS:0000000000000000
pro 29 17:06:47 localhost.localdomain kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
pro 29 17:06:47 localhost.localdomain kernel: CR2: 00007ff10610c680 CR3: 00000001d620a005 CR4: 00000000001606e0
pro 29 17:06:47 localhost.localdomain kernel: Call Trace:
pro 29 17:06:47 localhost.localdomain kernel:  <IRQ>
pro 29 17:06:47 localhost.localdomain kernel:  ? qdisc_put_unlocked+0x30/0x30
pro 29 17:06:47 localhost.localdomain kernel:  call_timer_fn+0x2d/0x130
pro 29 17:06:47 localhost.localdomain kernel:  run_timer_softirq+0x19b/0x400
pro 29 17:06:47 localhost.localdomain kernel:  ? tick_sched_timer+0x37/0x70
pro 29 17:06:47 localhost.localdomain kernel:  ? __hrtimer_run_queues+0x110/0x280
pro 29 17:06:47 localhost.localdomain kernel:  ? recalibrate_cpu_khz+0x10/0x10
pro 29 17:06:47 localhost.localdomain kernel:  __do_softirq+0xdf/0x2e5
pro 29 17:06:47 localhost.localdomain kernel:  irq_exit+0xd8/0xe0
pro 29 17:06:47 localhost.localdomain kernel:  smp_apic_timer_interrupt+0x74/0x130
pro 29 17:06:47 localhost.localdomain kernel:  apic_timer_interrupt+0xf/0x20
pro 29 17:06:47 localhost.localdomain kernel:  </IRQ>
pro 29 17:06:47 localhost.localdomain kernel: RIP: 0010:cpuidle_enter_state+0xbc/0x450
pro 29 17:06:47 localhost.localdomain kernel: Code: e8 59 f8 90 ff 80 7c 24 13 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 67 03 00 00 31 ff e8 2b ef 96 ff fb 66 0f 1f 44 00 00 <45> 85 e4 0f 88 92 02 00 00 49 63 cc 4c 8b 3c 24 4c 2b 7c 24 08 48
pro 29 17:06:47 localhost.localdomain kernel: RSP: 0018:ffffb4dec00a3e78 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff13
pro 29 17:06:47 localhost.localdomain kernel: RAX: ffff99394eaaa3c0 RBX: ffffffffa72caf20 RCX: 000000000000001f
pro 29 17:06:47 localhost.localdomain kernel: RDX: 0000000c8e9a0558 RSI: 0000000026c9b581 RDI: 0000000000000000
pro 29 17:06:47 localhost.localdomain kernel: RBP: ffff99394eab3708 R08: 0000000000000002 R09: 0000000000029c40
pro 29 17:06:47 localhost.localdomain kernel: R10: 0000003a5e1de801 R11: ffff99394eaa9380 R12: 0000000000000005
pro 29 17:06:47 localhost.localdomain kernel: R13: ffffffffa72cb118 R14: 0000000000000005 R15: 0000000000000000
pro 29 17:06:47 localhost.localdomain kernel:  ? cpuidle_enter_state+0x97/0x450
pro 29 17:06:47 localhost.localdomain kernel:  cpuidle_enter+0x29/0x40
pro 29 17:06:47 localhost.localdomain kernel:  do_idle+0x228/0x270
pro 29 17:06:47 localhost.localdomain kernel:  cpu_startup_entry+0x19/0x20
pro 29 17:06:47 localhost.localdomain kernel:  start_secondary+0x15f/0x1b0
pro 29 17:06:47 localhost.localdomain kernel:  secondary_startup_64+0xa4/0xb0
pro 29 17:06:47 localhost.localdomain kernel: ---[ end trace 6c54c5d6de7d5336 ]---
pro 29 17:06:49 localhost.localdomain dhclient[1142]: DHCPREQUEST for 192.168.1.225 on enp3s0 to 255.255.255.255 port 67
pro 29 17:07:03 localhost.localdomain dhclient[1142]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 5
pro 29 17:07:08 localhost.localdomain dhclient[1142]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 5
pro 29 17:07:13 localhost.localdomain dhclient[1142]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 9
pro 29 17:07:22 localhost.localdomain dhclient[1142]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 10
pro 29 17:07:24 localhost.localdomain systemd[1]: Starting LSB: Wait for the hotplugged network to be up...
pro 29 17:07:32 localhost.localdomain dhclient[1142]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 14
pro 29 17:07:42 localhost.localdomain systemd[1]: network-up.service: Succeeded.
pro 29 17:07:42 localhost.localdomain kernel: audit: type=1130 audit(1577635662.713:51): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=network-up comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
pro 29 17:07:42 localhost.localdomain kernel: audit: type=1131 audit(1577635662.713:52): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=network-up comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
pro 29 17:07:42 localhost.localdomain audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=network-up comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
pro 29 17:07:42 localhost.localdomain audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=network-up comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
pro 29 17:07:42 localhost.localdomain systemd[1]: Stopped LSB: Wait for the hotplugged network to be up.
pro 29 17:07:42 localhost.localdomain systemd[1]: Reached target Host and Network Name Lookups.
pro 29 17:07:43 localhost.localdomain network-up[1205]: Čekám na spuštění sítě
pro 29 17:07:46 localhost.localdomain dhclient[1142]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 14
pro 29 17:07:48 localhost.localdomain systemd[1]: Stopping LSB: Bring up/down networking...
pro 29 17:07:48 localhost.localdomain ifplugd(enp3s0)[1068]: Killing child.
pro 29 17:07:54 localhost.localdomain network[1610]: Vypínám rozhraní enp3s0:  Failed to kill daemon. (Timer expired)
pro 29 17:07:54 localhost.localdomain ifplugd(enp3s0)[1068]: client: Determining IP information for enp3s0...
pro 29 17:07:54 localhost.localdomain ifplugd(enp3s0)[1068]: Program execution failed, return value is 0.
pro 29 17:07:54 localhost.localdomain kernel: r8169 0000:03:00.0 enp3s0: Link is Down
pro 29 17:07:54 localhost.localdomain network[1610]: [  OK  ]
pro 29 17:07:54 localhost.localdomain network[1610]: Vypínám rozhraní pro loopback:  [  OK  ]
pro 29 17:07:54 localhost.localdomain systemd[1]: network.service: Succeeded.
pro 29 17:07:54 localhost.localdomain audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=network comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
pro 29 17:07:54 localhost.localdomain systemd[1]: Stopped LSB: Bring up/down networking.
pro 29 17:07:54 localhost.localdomain kernel: audit: type=1131 audit(1577635674.297:53): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=network comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
pro 29 17:07:55 localhost.localdomain kernel: Generic FE-GE Realtek PHY r8169-300:00: attached PHY driver [Generic FE-GE Realtek PHY] (mii_bus:phy_addr=r8169-300:00, irq=IGNORE)
pro 29 17:07:55 localhost.localdomain ifplugd(enp3s0)[1068]: Link beat lost.
pro 29 17:07:55 localhost.localdomain kernel: r8169 0000:03:00.0 enp3s0: Link is Down
pro 29 17:07:56 localhost.localdomain kernel: r8169 0000:03:00.0 enp3s0: Link is Up - 100Mbps/Full - flow control rx/tx
pro 29 17:07:56 localhost.localdomain kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready
pro 29 17:07:57 localhost.localdomain ifplugd(enp3s0)[1068]: Link beat detected.
pro 29 17:08:03 localhost.localdomain systemd[1]: Stopped target Network is Online.
pro 29 17:08:48 localhost.localdomain kernel: r8169 0000:03:00.0: invalid short VPD tag 00 at offset 1

CC: (none) => raiko

Comment 15 Levchenko Roman 2020-03-05 20:09:25 CET

Unfortunately, the netcards behaves in the same way.
Additional information about computer with logs - HW-Probe https://linux-hardware.org/?probe=c61a5bbb12

Comment 16 Aurelien Oudelet 2021-07-06 13:17:27 CEST

Mageia 7 is EOL since July 1st 2021.
There will not have any further bugfix for this release.

You are encouraged to upgrade to Mageia 8 as soon as possible.

@reporter, if this bug still apply with Mageia 8, please let us know it.

@packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead.

This bug report will be closed OLD if there is no further notice within 1st September 2021.

Comment 17 Levchenko Roman 2021-08-25 19:05:32 CEST

Good day. 
Unfortunately, the problem is not cured completely: 
Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller - onboard (GIGABYTE GA-H81M-S2H motheboard),
serial 40-8D-5C-02-E1-50, starts after reloading module r8169 only. 

Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller - expansion card,
serial 98-DE-D0-01-E6-A3 (TP-Link) - starts on boot properly.

D-Link System Inc DGE-528T Gigabit Ethernet Adapter - expansion card,
with DLG10028C chip (analog Realtek)- starts on boot properly. 

May be useful https://linux-hardware.org/?probe=46740d8f33

Comment 18 Levchenko Roman 2021-08-25 19:18:54 CEST

A comment17 - it's already on Mageia8.

Comment 19 Pascal Terjan 2021-08-25 19:33:29 CEST

A quick look at the drivers shows cases where it could fail at boot time and work later (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/ethernet/realtek/r8169_main.c#n5104) if realtek module was loaded after r8169, but you would get a message in the logs


Unfortunately https://linux-hardware.org/?probe=c61a5bbb12&log=dmesg is useless due to the flooding of net-fw DROP which removed the boot logs.

Looking at dmesg I see no such message, but see 3 interfaces:

[   10.952640] libphy: r8169: probed
[   10.952853] r8169 0000:03:00.0 eth0: RTL8168g/8111g, XX:XX:XX:XX:XX:XX, XID 4c0, IRQ 34
[   10.952857] r8169 0000:03:00.0 eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko]
 r8169 0000:05:00.0: can't disable ASPM; OS doesn't have ASPM control
[   10.961421] libphy: r8169: probed
[   10.961718] r8169 0000:05:00.0 eth1: RTL8168e/8111e, XX:XX:XX:XX:XX:XX, XID 2c2, IRQ 35
[   10.961723] r8169 0000:05:00.0 eth1: jumbo features [frames: 9194 bytes, tx checksumming: ko]
 r8169 0000:06:00.0: can't disable ASPM; OS doesn't have ASPM control
[   10.994962] libphy: r8169: probed
[   10.995830] r8169 0000:06:00.0 eth2: RTL8168e/8111e, XX:XX:XX:XX:XX:XX, XID 2c2, IRQ 37
[   10.995834] r8169 0000:06:00.0 eth2: jumbo features [frames: 9194 bytes, tx checksumming: ko]


The first two of this list seem to be the problematic ones:
10ec:8168:1458:e000 Realtek Semiconductor Co., Ltd.	RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
10ec:8168:7470:3468 Realtek Semiconductor Co., Ltd.	RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
1186:4300:1186:4b10 D-Link System Inc	DGE-528T Gigabit Ethernet Adapter

Comment 20 Pascal Terjan 2021-08-25 19:37:43 CEST

[   38.464541] Generic FE-GE Realtek PHY r8169-0-300:00: attached PHY driver (mii_bus:phy_addr=r8169-0-300:00, irq=MAC)
[   38.574494] r8169 0000:03:00.0 enp3s0: Link is Down
[   38.590958] RTL8211DN Gigabit Ethernet r8169-0-500:00: attached PHY driver (mii_bus:phy_addr=r8169-0-500:00, irq=MAC)
[   38.835583] r8169 0000:05:00.0 enp5s0: Link is Down
[   38.841745] RTL8211DN Gigabit Ethernet r8169-0-600:00: attached PHY driver (mii_bus:phy_addr=r8169-0-600:00, irq=MAC)
[   39.085547] r8169 0000:06:00.0 enp6s0: Link is Down

CC: (none) => pterjan

Comment 21 Levchenko Roman 2021-08-26 10:06:27 CEST

(In reply to Pascal Terjan from comment #19)
> A quick look at the drivers shows cases where it could fail at boot time and
> work later
> (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/
> drivers/net/ethernet/realtek/r8169_main.c#n5104) if realtek module was
> loaded after r8169, but you would get a message in the logs
> 
> 
> Unfortunately https://linux-hardware.org/?probe=c61a5bbb12&log=dmesg is
> useless due to the flooding of net-fw DROP which removed the boot logs.
> 
> Looking at dmesg I see no such message, but see 3 interfaces:
> 
> [   10.952640] libphy: r8169: probed
> [   10.952853] r8169 0000:03:00.0 eth0: RTL8168g/8111g, XX:XX:XX:XX:XX:XX,
> XID 4c0, IRQ 34
> [   10.952857] r8169 0000:03:00.0 eth0: jumbo features [frames: 9194 bytes,
> tx checksumming: ko]
>  r8169 0000:05:00.0: can't disable ASPM; OS doesn't have ASPM control
> [   10.961421] libphy: r8169: probed
> [   10.961718] r8169 0000:05:00.0 eth1: RTL8168e/8111e, XX:XX:XX:XX:XX:XX,
> XID 2c2, IRQ 35
> [   10.961723] r8169 0000:05:00.0 eth1: jumbo features [frames: 9194 bytes,
> tx checksumming: ko]
>  r8169 0000:06:00.0: can't disable ASPM; OS doesn't have ASPM control
> [   10.994962] libphy: r8169: probed
> [   10.995830] r8169 0000:06:00.0 eth2: RTL8168e/8111e, XX:XX:XX:XX:XX:XX,
> XID 2c2, IRQ 37
> [   10.995834] r8169 0000:06:00.0 eth2: jumbo features [frames: 9194 bytes,
> tx checksumming: ko]
> 
> 
> The first two of this list seem to be the problematic ones:
> 10ec:8168:1458:e000 Realtek Semiconductor Co., Ltd.	RTL8111/8168/8411 PCI
> Express Gigabit Ethernet Controller
> 10ec:8168:7470:3468 Realtek Semiconductor Co., Ltd.	RTL8111/8168/8411 PCI
> Express Gigabit Ethernet Controller
> 1186:4300:1186:4b10 D-Link System Inc	DGE-528T Gigabit Ethernet Adapter

May be here is more informative https://linux-hardware.org/?probe=46740d8f33 and   https://linux-hardware.org/?probe=46740d8f33&log=dmesg

Comment 22 Levchenko Roman 2021-08-26 11:04:47 CEST

(In reply to Pascal Terjan from comment #20)
I'll try to reboot without rmmode-modprobe r8169 in rc.local, may be dmesq give us smth else.

Comment 23 Levchenko Roman 2021-08-26 20:39:34 CEST

Created attachment 12915 [details]
dmesg_out without r8169 restarting

Levchenko Roman 2021-08-26 20:44:09 CEST

Attachment 12915 description: dmesg_out => dmesg_out without r8169 restarting

Comment 24 Levchenko Roman 2021-09-02 08:37:41 CEST

(In reply to Pascal Terjan from comment #20)

In https://bugs.mageia.org/attachment.cgi?id=12915 - dmesg without r8169 restarting

Comment 25 Marja Van Waes 2021-09-06 22:46:19 CEST

(In reply to Levchenko Roman from comment #18)
> A comment17 - it's already on Mageia8.

(Changing Version: to 8)

Version: 7 => 8
CC: (none) => marja11

Comment 26 Marja Van Waes 2024-08-22 23:02:02 CEST

We stopped supporting Mageia 8 almost 8 months ago 
https://blog.mageia.org/en/2023/12/30/mageia-8-end-of-life/

That means we also stopped fixing Mageia 8 bugs and that this bug report needs to be closed, regardless of whether it was fixed for Mageia 8 or not.

If this particular bug did not get fixed for Mageia 8, then we do regret that.

If this issue is still present in Mageia 9 or cauldron, then please reopen this report, write a comment and adjust the "Version:" field.

If you are not yet a member of one or our teams, then please consider becoming one. https://wiki.mageia.org/en/Contributing
Mageia is a community project, meaning that we, the users, make Mageia together.

The more active contributors we have, the more bug reports will get fixed.
Besides, being active in a team can be very rewarding. It was and is certainly rewarding to me :-D

Status: NEW => RESOLVED
Resolution: (none) => OLD

Note You need to log in before you can comment on or make changes to this bug.