Opened 9 years ago
Closed 6 years ago
#12281 closed bug (fixed)
wpa_supplicant can be crashed easily, and isn't restarted
Reported by: | kallisti5 | Owned by: | axeld |
---|---|---|---|
Priority: | blocker | Milestone: | R1 |
Component: | Network & Internet/Wireless | Version: | R1/Development |
Keywords: | wpa_supplicant | Cc: | |
Blocked By: | Blocking: | ||
Platform: | All |
Description
wpa_supplicant can be crashed easily, and isn't restarted
This is a break apart of these R1 blockers from #7663 to make them more visible.
This might be something we can solve with the launch daemon.
Attachments (1)
Change History (6)
comment:1 by , 9 years ago
Blocking: | 7660 removed |
---|
comment:2 by , 7 years ago
by , 7 years ago
Attachment: | P_20180413_175911[1].jpg added |
---|
iprowifi3945 driver crash - kernel debugger snapshot
comment:3 by , 7 years ago
No, seemed stable in itself. Although I rand into this driver issue while testing on hrev51880 x86 with iprowifi3945 driver (see: P_20180413_175911[1].jpg). Happens during initial bootup after splash screen completion. Didn't reboot computer (just exit debugger and will continue loading desktop fine)).
NOYE: I just can't detect active APs but the driver seems up and running.
comment:4 by , 7 years ago
No system reboot issues with wpa_supplement on hrev51881 x86_64. Seems stable.
comment:5 by , 6 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Is this still happening? During the latest coding sprint I finished mmlr's work on updating wpa_supplicant and I don't remember hitting this problem since then. I'm interested in debug reports if someone can reproduce it.