Bug 179532
| Summary: | wireless networking on ARM | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Base System | Reporter: | Guillaume Bibaut <yom> | ||||||||
| Component: | arm | Assignee: | freebsd-arm (Nobody) <freebsd-arm> | ||||||||
| Status: | Closed FIXED | ||||||||||
| Severity: | Affects Only Me | CC: | avos | ||||||||
| Priority: | Normal | ||||||||||
| Version: | Unspecified | ||||||||||
| Hardware: | Any | ||||||||||
| OS: | Any | ||||||||||
| See Also: | https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=153380 | ||||||||||
| Attachments: |
|
||||||||||
|
Description
Guillaume Bibaut
2013-06-13 10:50:00 UTC
Hi Guillaume, On Thursday 13 June 2013 11:40:44 Guillaume Bibaut wrote: > >Number: 179532 > >Category: arm > >Synopsis: wireless networking on ARM .. > >Environment: > > FreeBSD iaelumx 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r251405M: Wed Jun 12 > 12:50:45 CEST 2013 > root@bsd-current:/root/EfikaMX/obj/arm.armv6/root/EfikaMX/src/efika_mx/sys/ >EFIKA_MX arm > > >Description: > > FreeBSD is crashing when wpa_supplicant is called upon boot on the Genesi > Efika MX smartbook. > > Since I can't copy and paste the result of the crash, I've taken pictures > and put them here : http://iaelu.net/~yom/efikamx/arm-eabi/ > > I got helped by @rayddteam ( ray@ ) on the EFNET IRC subnet, in the > #bsdmips channel. > > The Wireless network was a WPA Personal. > > after some investigations with the help of ray@ > we could at least gather this information with the addr2line command : > /root/EfikaMX/obj/arm.armv6/root/EfikaMX/src/efika_mx/tmp/usr/bin/addr2line > -e /mnt/boot/kernel/kernel c035bc44 > /root/EfikaMX/src/efika_mx/sys/net80211/ieee80211_radiotap.c:138 > > I hope these informations help you to fix the problem, if there is any > solution. I think we might have hit this same bug at work and have a local patch that fixes it. I'll see if I can dust it off and post a patch here. I believe it was only a 3-line patch to if_run.c Regards, -- Ing. Daan Vreeken Vitsch Electronics http://Vitsch.nl/ http://VitschVPN.nl/ tel: +31-(0)40-7113051 KvK nr: 17174380 -- Machines en netwerken op afstand beheren? Vitsch VPN oplossing! Kijk voor meer informatie op: http://www.VitschVPN.nl/ Hi again, On Friday 14 June 2013 10:02:54 Daan Vreeken wrote: > Hi Guillaume, > > On Thursday 13 June 2013 11:40:44 Guillaume Bibaut wrote: > > >Number: 179532 > > >Category: arm > > >Synopsis: wireless networking on ARM ... > > >Description: > > > > FreeBSD is crashing when wpa_supplicant is called upon boot on the Genesi > > Efika MX smartbook. ... > I think we might have hit this same bug at work and have a local patch that > fixes it. I'll see if I can dust it off and post a patch here. I believe it > was only a 3-line patch to if_run.c See the attachments. These patches fix two bugs: o A crash in if_run when using VNET in the kernel. o The correctness of the information passed to the radiotap code in if_run. I think the last patch may fix the crash you are seeing with if_run and wpa_supplicant. If you only want to test that part, you just have to patch if_run.c with the file 'if_run_2013_01_19_radiotap_fix_only.diff' . In case the attachments get mangled in the email, you can also download these files from : http://www.vitsch.nl/pub_diffs/ The following files should be attached to this email : if_run_2013_01_19_radiotap_fix_only.diff if_run_2013_01_19_vnet_fix.diff if_run_2013_01_19_vnet_plus_radiotap_fix.diff All patches are: Sponsored by: Vitsch Electronics Regards, -- Ing. Daan Vreeken Vitsch Electronics http://Vitsch.nl/ http://VitschVPN.nl/ tel: +31-(0)40-7113051 KvK nr: 17174380 -- Machines en netwerken op afstand beheren? Vitsch VPN oplossing! Kijk voor meer informatie op: http://www.VitschVPN.nl/ Is this still an issue for you? I've been able to get ARM boards to connect to wireless networks using WPA2 for a while, with several different wireless NICs. (In reply to Glen Barber from comment #3) It was not an issue anymore when my EfikaMX was still working before I had hardware problem (sadly, my efikamx does not even want to power up correctly). So I guess this report could be closed as fixed. Fixed in base r253756. (In reply to Andriy Voskoboinyk from comment #5) A typo: in base r253757 |
