Bug 1518190 - Hotspot stopped working
Summary: Hotspot stopped working
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-28 11:46 UTC by Medic Momcilo
Modified: 2018-01-11 05:35 UTC (History)
32 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-01-03 22:04:20 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Medic Momcilo 2017-11-28 11:46:14 UTC
Description of problem:


Version-Release number of selected component (if applicable):
NetworkManager-1:1.8.4-7

How reproducible:
Always

Steps to Reproduce:
1. Boot up
2. Start Hotspot from Wi-Fi settings in Gnome
3. Confirm you will lose WiFi connectivity to other networks

Actual results:
Hotspot not active.

Expected results:
Hotspot active.

Additional info:
Error shown in log when trying manually is:
[momcilo.medic@probook4540s ~]$ nmcli con up Hotspot
Error: Connection activation failed: 802.1X supplicant took too long to authenticate
[momcilo.medic@probook4540s ~]$

Relevant log part:
...
nov 28 12:35:45 probook4540s NetworkManager[1054]: <info>  [1511868945.1235] device (wlo1): Activation: (wifi) connection 'Hotspot' has security, and s
nov 28 12:35:45 probook4540s NetworkManager[1054]: <info>  [1511868945.1236] Config: added 'ssid' value 'probook4540s'
nov 28 12:35:45 probook4540s NetworkManager[1054]: <info>  [1511868945.1237] Config: added 'mode' value '2'
nov 28 12:35:45 probook4540s NetworkManager[1054]: <info>  [1511868945.1237] Config: added 'frequency' value '2412'
nov 28 12:35:45 probook4540s NetworkManager[1054]: <info>  [1511868945.1237] Config: added 'key_mgmt' value 'WPA-PSK'
nov 28 12:35:45 probook4540s NetworkManager[1054]: <info>  [1511868945.1237] Config: added 'psk' value '<hidden>'
nov 28 12:35:45 probook4540s wpa_supplicant[1148]: Note: nl80211 driver interface is not designed to be used with ap_scan=2; this can result in connect
nov 28 12:35:45 probook4540s wpa_supplicant[1148]: Using interface wlo1 with hwaddr 20:68:9d:8f:69:de and ssid "probook4540s"
nov 28 12:35:45 probook4540s wpa_supplicant[1148]: Failed to set beacon parameters
nov 28 12:35:45 probook4540s wpa_supplicant[1148]: Interface initialization failed
nov 28 12:35:45 probook4540s wpa_supplicant[1148]: wlo1: interface state UNINITIALIZED->DISABLED
nov 28 12:35:45 probook4540s wpa_supplicant[1148]: wlo1: AP-DISABLED
nov 28 12:35:45 probook4540s wpa_supplicant[1148]: wlo1: Unable to setup interface.
nov 28 12:35:45 probook4540s wpa_supplicant[1148]: Failed to initialize AP interface
nov 28 12:35:45 probook4540s wpa_supplicant[1148]: wlo1: interface state DISABLED->DISABLED
nov 28 12:35:45 probook4540s wpa_supplicant[1148]: wlo1: AP-DISABLED
nov 28 12:35:45 probook4540s wpa_supplicant[1148]: hostapd_free_hapd_data: Interface wlo1 wasn't started
nov 28 12:35:45 probook4540s wpa_supplicant[1148]: wlo1: CTRL-EVENT-DISCONNECTED bssid=20:68:9d:8f:69:de reason=3 locally_generated=1
nov 28 12:35:45 probook4540s NetworkManager[1054]: <info>  [1511868945.1464] device (wlo1): supplicant interface state: inactive -> disconnected
...

Comment 1 Thomas Haller 2017-11-28 13:29:34 UTC
"stopped" make it sound like this was working on Fedora 26 (previoulsy).
When did it stop working?


This looks like a supplicant or driver issue to me.

Comment 2 Medic Momcilo 2017-11-28 17:57:56 UTC
Yes, I've been running Rawhide for a long period of time with Hotstop active most of the time.
Recently it was failing to start, but I wasn't in a position to troubleshoot and pinpoint actual point in time when it stopped working.

I will try booting older kernel to see if it is a driver issue.

Comment 3 Medic Momcilo 2017-11-28 18:10:22 UTC
It is indeed a kernel issue.
Doesn't work in 4.15.0-0.rc0.git6.1.fc28.x86_64 (and newer)
Still work in 4.15.0-0.rc0.git3.1.fc28.x86_64

I changed component accordingly, if this is not the correct way and I should file a new bug report please do let me know.

Kind regards,
Momcilo "Momo" Medic
(fedorauser).

Comment 4 Laura Abbott 2017-11-28 21:27:00 UTC
The network merge came in during that period so it's probably something there. Your best bet is to do a git bisect to figure out the problem.  Can you share lspci or something else that gives your network card information?

Comment 5 Medic Momcilo 2017-11-30 10:28:38 UTC
Here is the output:

# lspci -vvv -s '03:00.0'
03:00.0 Network controller: Qualcomm Atheros AR9485 Wireless Network Adapter (rev 01)
	Subsystem: Hewlett-Packard Company Device 1785
	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 19
	Region 0: Memory at d0600000 (64-bit, non-prefetchable) [size=512K]
	Expansion ROM at d0680000 [disabled] [size=64K]
	Capabilities: [40] Power Management version 2
		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/4 Maskable+ 64bit+
		Address: 0000000000000000  Data: 0000
		Masking: 00000000  Pending: 00000000
	Capabilities: [70] Express (v2) Endpoint, MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0, Latency L0s unlimited, L1 <64us
			ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- SlotPowerLimit 10.000W
		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 <4us, L1 <64us
			ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp-
		LnkCtl:	ASPM L1 Enabled; 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
			 AtomicOpsCap: 32bit- 64bit- 128bitCAS-
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled
			 AtomicOpsCtl: ReqEn-
		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, ECRCGenCap- ECRCGenEn- ECRCChkCap- ECRCChkEn-
			MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
		HeaderLog: 00000000 00000000 00000000 00000000
	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 00-00-00-00-00-00-00-00
	Kernel driver in use: ath9k
	Kernel modules: ath9k

Comment 6 Laura Abbott 2017-12-04 17:19:41 UTC
Sounds like this is a known issue https://marc.info/?l=linux-kernel&m=151221956904515&w=2 , rawhide will eventually pick the fix

Comment 7 Medic Momcilo 2018-01-03 22:04:20 UTC
This has been fixed in one of the later releases.
Not sure which version specifically.


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