Opened 15 months ago

Closed 14 months ago

Last modified 14 months ago

#14349 closed bug (fixed)

wpa_supplicant segfault with atheroswifi driver

Reported by: v.vill Owned by: nobody
Priority: normal Milestone: Unscheduled
Component: Network & Internet Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

Greetings, I'm trying to use the updated FreeBSD11 stack to work with an Atheros wifi card, which has proven to be challenging (see #14249 and #14282).

When connecting to a WPA-encrypted network, wpa_supplicant crashes (see attached); and afterwards no wifi networks are detected, no matter how many processes I kill and respawn. I have to reboot the system to regain proper wifi network scanning. (Interestingly, I seem to be able to get a slow but nearly-stable wifi connection on unencrypted networks.)

I'm running hrev 52205 x86_64 with an AR9565 wifi chip.

Attachments (5)

wpa_supplicant-1153-debug-11-08-2018-18-05-18.report (11.2 KB ) - added by v.vill 15 months ago.
net_server-982-debug-13-08-2018-20-12-22.report (12.0 KB ) - added by v.vill 15 months ago.
IMG_20180813_221010.jpg (1.7 MB ) - added by v.vill 15 months ago.
atheroswifi KDL
wpa_supplicant-1118-debug-28-08-2018-21-41-51.report (15.3 KB ) - added by v.vill 15 months ago.
Updated report
wpa_supplicant-1136-debug-31-08-2018-21-07-41.report (15.3 KB ) - added by v.vill 15 months ago.
Updated report

Download all attachments as: .zip

Change History (20)

comment:1 by waddlesplash, 15 months ago

Wait. So is #14282 fixed then?

comment:2 by v.vill, 15 months ago

Well, in a way (see comment 18). I figured you'd prefer to have different tickets rather than adding noise to #14282.

BTW; see also #14348 (Network preferences window crashes when SSID list gets updated, with the same wifi card).

comment:3 by v.vill, 15 months ago

I’m not entirely sure the bug is triggered by wpa_supplicant; even without using encrypted networks, net_server tends to crash as well (see attached).

by v.vill, 15 months ago

Attachment: IMG_20180813_221010.jpg added

atheroswifi KDL

comment:4 by v.vill, 15 months ago

Also, when trying to regain wifi access by clicking on "Disable" then "Enable" in the Network preferences window, I managed to trigger a vm_page_fault KDL that looks a _lot_ like #14282. I’m not sure whether these are two separate problems, but in any case I’m also attaching it here.

comment:5 by waddlesplash, 15 months ago

Nah, that KDL is completely unrelated to #14282. Please open a new ticket for it.

comment:6 by v.vill, 15 months ago

OK, added as #14355.

comment:7 by v.vill, 15 months ago

FWIW, I can reproduce the bug with a clean install of hrev52273.

comment:8 by waddlesplash, 15 months ago

Clean installs will still have wpa supplicant 2.4 until yesterday evening. After that hrev, they shod have 2.7. Can you see if it's then fixed?

comment:9 by v.vill, 15 months ago

I didn’t have a chance to reproduce the segfault, since it KDL’d before I got to that part :-/

See #14411.

comment:10 by v.vill, 15 months ago

OK, now that #14355 appears to be fixed I could reproduce the segfault again. See attached report.

Last edited 15 months ago by v.vill (previous) (diff)

by v.vill, 15 months ago

Updated report

comment:11 by v.vill, 15 months ago

Huh. Since upgrading to hrev52300 the segfault has no longer been happening. It’s strange, because I can’t see any commit between hrev52297 and 52300 that could explain it.

Another possible factor for this issue, is that when connecting to a known encrypted network, wpa_supplicant has to request permission for accessing the keyring; when the segfault occurred, it always happened _before_ it asked for permission. So, perhaps some behavior changed there (or perhaps it was just a byproduct of #14355, but it did keep crashing for a while even after it was fixed).

tl;dr: seems to be fixed now, at least AFAICS.

comment:12 by v.vill, 15 months ago

Oops, turns out it's not completely gone; I did encounter the segfault again (roughly 1 out of 3 boot ups, with no discernable specific trigger). I'm attaching a new log (very similar though) in case it may help.

by v.vill, 15 months ago

Updated report

comment:13 by waddlesplash, 14 months ago

I managed to somehow trigger this on my machine, though I'm still not sure what the circumstances of it were; after a reboot everything was normal again. I'll try to get it to happen again.

comment:14 by waddlesplash, 14 months ago

Resolution: fixed
Status: newclosed

comment:15 by v.vill, 14 months ago

Brilliant. Thanks!

Note: See TracTickets for help on using tickets.