FS#41598 - [linux] not able to rename wireless interface to persistent name with error

Attached to Project: Arch Linux
Opened by Javier (jevv) - Sunday, 17 August 2014, 23:17 GMT
Last edited by Dave Reisner (falconindy) - Sunday, 01 October 2017, 22:07 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

According to journalctl, the problem started with linux 3.14.5-1 and systemd-udevd 213. Prior to that there was no problem, with linux 3.14.4-1 and systemd-udevd 212. Sounds like an udevd problem. See:

Jun 05 21:10:32 lm-3 kernel: Linux version 3.14.4-1-ARCH (nobody@var-lib-archbuild-testing-x86_64-tobias) (gcc version 4.9.0 20140507 (prerelease) (GCC) ) #1 SMP PREEMPT Tue May 13 16:41:39 CEST 2014
...
Jun 05 21:10:32 lm-3 systemd-udevd[59]: starting version 212
...
Jun 05 21:10:44 lm-3 systemd-udevd[178]: renamed network interface wlan0 to lm-3-rtlwifi-wl
...
...
Jun 05 21:42:18 lm-3 kernel: Linux version 3.14.5-1-ARCH (nobody@var-lib-archbuild-testing-x86_64-tobias) (gcc version 4.9.0 20140521 (prerelease) (GCC) ) #1 SMP PREEMPT Sun Jun 1 07:36:23 CEST 2014
...
Jun 05 21:42:18 lm-3 systemd-udevd[57]: starting version 213
...
Jun 05 21:42:31 lm-3 systemd-udevd[178]: error changing net interface name wlan0 to lm-3-rtlwifi-wl: Invalid argument

From this point on, and until now, the renaming of the wireless interface has not happened ever:

Aug 17 16:16:42 lm-3 kernel: Linux version 3.16.1-1-ARCH (nobody@var-lib-archbuild-testing-x86_64-tobias) (gcc version 4.9.1 (GCC) ) #1 SMP PREEMPT Thu Aug 14 07:40:19 CEST 2014
...
Aug 17 16:16:42 lm-3 systemd-udevd[59]: starting version 215
...
Aug 17 16:16:52 lm-3 systemd-udevd[194]: error changing net interface name wlan0 to lm-3-rtlwifi-wl: Invalid argument

I'm specifying the setting through:

% cat /etc/udev/rules.d/80-net-setup-link-persistent.rules
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:01:c0:14:60:16", NAME="lm-3-intel-wd"
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:01:c0:14:60:17", NAME="lm-3-r8169-wd"
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:0d:f0:ad:4d:cd", NAME="lm-3-rtlwifi-wl"

Please notice how the 2 first interfaces, which are wired ones, are renamed OK, with no problem, following the same udev rules. So given that the rules work for wired interfaces, and that they were working without problems for all interfaces before, it must be that a change in systemd-udevd or/and linux is not allowing the rename any longer.

Some additional messages associated to the interface, prior to the failure:

Jun 05 21:42:31 lm-3 kernel: rtl8723ae: Using firmware rtlwifi/rtl8723fw_B.bin
Jun 05 21:42:31 lm-3 kernel: ieee80211 phy0: Selected rate control algorithm 'rtl_rc'
Jun 05 21:42:31 lm-3 kernel: rtlwifi: wireless switch is on

Not sure if it's more like a linux module issue, or a systemd-udevd issue. The packages information I'll provide corresponding to up to date Arch on a X86_64 linux mint 2 box...


Additional info:
* package version(s)

local/linux 3.16.1-1 (base)
local/linux-api-headers 3.14.1-1
local/linux-firmware 20140603.a4f3bc0-1
local/libsystemd 215-4
local/systemd 215-4
local/systemd-sysvcompat 215-4 (base)

* config and/or log files etc.

% cat /etc/udev/rules.d/80-net-setup-link-persistent.rules
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:01:c0:14:60:16", NAME="lm-3-intel-wd"
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:01:c0:14:60:17", NAME="lm-3-r8169-wd"
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:0d:f0:ad:4d:cd", NAME="lm-3-rtlwifi-wl"

% lsmod | 'grep' rtl8723ae
rtl8723ae 80108 0
rtl8723_common 17920 1 rtl8723ae
rtl_pci 25931 1 rtl8723ae
rtlwifi 54662 2 rtl_pci,rtl8723ae
mac80211 514630 3 rtl_pci,rtlwifi,rtl8723ae

% lsmod | 'grep' wifi
rtlwifi 54662 2 rtl_pci,rtl8723ae
mac80211 514630 3 rtl_pci,rtlwifi,rtl8723ae
cfg80211 454161 2 mac80211,rtlwifi

% sudo lspci -vvv | less
04:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8723AE PCIe Wireless Network Adapter
Subsystem: Realtek Semiconductor Co., Ltd. Device 0733
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, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 17
Region 0: I/O ports at 3000 [size=256]
Region 2: Memory at e0600000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Address: 0000000000000000 Data: 0000
Capabilities: [70] Express (v2) Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1 <64us
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+ TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <512ns, L1 <64us
ClockPM+ Surprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
DevCap2: Completion Timeout: Not Supported, TimeoutDis+, LTR-, OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis+, LTR-, OBFF Disabled
LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-
Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1-
EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
Capabilities: [100 v1] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-
Capabilities: [140 v1] Virtual Channel
Caps: LPEVC=0 RefClk=100ns PATEntryBits=1
Arb: Fixed- WRR32- WRR64- WRR128-
Ctrl: ArbSelect=Fixed
Status: InProgress-
VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
Status: NegoPending- InProgress-
Capabilities: [160 v1] Device Serial Number 01-23-87-fe-ff-4c-e0-00
Kernel driver in use: rtl8723ae
Kernel modules: rtl8723ae



Steps to reproduce:
This task depends upon

Closed by  Dave Reisner (falconindy)
Sunday, 01 October 2017, 22:07 GMT
Reason for closing:  None
Additional comments about closing:  Works for reporter
Comment by Dave Reisner (falconindy) - Sunday, 17 August 2014, 23:48 GMT
> Not sure if it's more like a linux module issue, or a systemd-udevd issue.
Could you please sort this out? It's more likely to be a kernel issue since there's been no relevant udev changes in the given timespan, and the behavior is inconsistent across different drivers.
Comment by Javier (jevv) - Tuesday, 19 August 2014, 02:46 GMT
Well, I'm no expert.

Any ways, I confirmed on a laptop that an intel wireless interface is getting renamed. So it seems it might be the linux module.
Comment by David Futcher (bobbo) - Wednesday, 20 August 2014, 13:24 GMT
Experienced this issue with Linux 3.4.67 and systemd 215-4.1. Downgraded systemd to 212-3 (did not change kernel) and interface renaming now works as expected; appears to be a systemd specific issue.
Comment by Javier (jevv) - Saturday, 30 July 2016, 22:02 GMT
It's pretty much working now, with linux 4.6.4-1, and systemd 230-7. Can be closed.

Thanks!
Comment by mattia (nTia89) - Sunday, 01 October 2017, 15:41 GMT
is this issue still valid?
Comment by Javier (jevv) - Sunday, 01 October 2017, 19:40 GMT
Not for me, as indicated in my last comment, :) Perhaps I forgot to request closure? Doing it now...

Loading...