GNOME Bugzilla – Bug 755737
Segmentation fault when in an area with many access points/SSID's
Last modified: 2015-09-30 11:55:51 UTC
For the past ~2 months I have experienced an issue that while I am on my schools campus specific area's that have a high number of wireless access points networkmanager will consistently segfault in a loop were it segfaults restarts then segfaults again. I am running Arch Linux release 4.1.6-1-ARCH with no modifications to the kernel they push out. Below is some relevant information from logs feel free to let me know what other information you would like! -- Associated dmesg output [ 76.705241] NetworkManager[583]: segfault at 0 ip 0000000000499477 sp 00007ffe31647900 error 4 in NetworkManager[400000+1c0000] [ 77.376862] IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready [ 77.390130] IPv6: ADDRCONF(NETDEV_UP): enp4s0: link is not ready [ 77.655075] IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready [ 77.856536] userif-4: sent link down event. [ 77.856540] userif-4: sent link up event. [ 80.262845] NetworkManager[2080]: segfault at 0 ip 0000000000499477 sp 00007fff45bacdb0 error 4 in NetworkManager[400000+1c0000] [ 80.686807] IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready [ 80.700197] IPv6: ADDRCONF(NETDEV_UP): enp4s0: link is not ready [ 81.027315] IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready [ 81.317488] userif-4: sent link down event. [ 81.317491] userif-4: sent link up event. [ 83.654968] NetworkManager[2157]: segfault at 0 ip 0000000000499477 sp 00007fff9cb60b70 error 4 in NetworkManager[400000+1c0000] [ 84.204278] IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready [ 84.217983] IPv6: ADDRCONF(NETDEV_UP): enp4s0: link is not ready [ 84.649539] IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready [ 85.034974] userif-4: sent link down event. [ 85.034977] userif-4: sent link up event. [ 87.207126] NetworkManager[2231]: segfault at 0 ip 0000000000499477 sp 00007fffe7f23a50 error 4 in NetworkManager[400000+1c0000] [ 87.705538] IPv6: ADDRCONF(NETDEV_UP): enp4s0: link is not ready [ 87.717177] IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready [ 87.937298] IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready [ 88.193111] userif-4: sent link down event. [ 88.193114] userif-4: sent link up event. [ 90.508827] NetworkManager[2305]: segfault at 0 ip 0000000000499477 sp 00007ffe887e20b0 error 4 in NetworkManager[400000+1c0000] [ 90.958618] IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready [ 90.972172] IPv6: ADDRCONF(NETDEV_UP): enp4s0: link is not ready [ 91.340024] IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready [ 91.711716] userif-4: sent link down event. [ 91.711718] userif-4: sent link up event. [ 93.886504] NetworkManager[2379]: segfault at 0 ip 0000000000499477 sp 00007ffe8d6ecc00 error 4 in NetworkManager[400000+1c0000] [ 94.455224] IPv6: ADDRCONF(NETDEV_UP): enp4s0: link is not ready [ 94.467293] IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready [ 94.925059] IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready [ 95.442430] userif-4: sent link down event. [ 95.442432] userif-4: sent link up event. [ 97.507673] NetworkManager[2445]: segfault at 0 ip 0000000000499477 sp 00007fff4dac5680 error 4 in NetworkManager[400000+1c0000] --Below is a reduced output of lspci -v 04:00.0 Ethernet controller: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller (rev 13) Subsystem: Micro-Star International Co., Ltd. [MSI] Device 1102 Flags: bus master, fast devsel, latency 0, IRQ 34 Memory at f7300000 (64-bit, non-prefetchable) [size=256K] I/O ports at c000 [size=128] Capabilities: [40] Power Management version 3 Capabilities: [58] Express Endpoint, MSI 00 Capabilities: [c0] MSI: Enable+ Count=1/16 Maskable+ 64bit+ Capabilities: [d8] MSI-X: Enable- Count=16 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [180] Device Serial Number ff-6e-b5-e6-44-8a-5b-ff Kernel driver in use: alx Kernel modules: alx 05:00.0 Network controller: Intel Corporation Wireless 7260 (rev 6b) Subsystem: Intel Corporation Dual Band Wireless-AC 7260 Flags: bus master, fast devsel, latency 0, IRQ 30 Memory at f7200000 (64-bit, non-prefetchable) [size=8K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Device Serial Number 28-b2-bd-ff-ff-10-f1-5d Capabilities: [14c] Latency Tolerance Reporting Capabilities: [154] Vendor Specific Information: ID=cafe Rev=1 Len=014 <?> Kernel driver in use: iwlwifi Kernel modules: iwlwifi
Also I am running NetworkManager 1.0.6
It would be best if you could get a backtrace when the crash happens. Ensure to install debugging information, and then something like, systemctl stop NetworkManager gdb /sbin/NetworkManager > run --debug ... reproduce crash > backtrace
I would help if you could recompile network-manager package first so that there are debugging symbols in the backtrace. [1] https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces [2] https://wiki.archlinux.org/index.php/Step-by-step_debugging_guide
Actually, it might be the bug fixed in Red Hat bugzilla (https://bugzilla.redhat.com/show_bug.cgi?id=1266003). The fix is http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=nm-1-0&id=9736327b2616861dfec181e88f908a18b22d781c
(In reply to Thomas Haller from comment #2) > It would be best if you could get a backtrace when the crash happens. > > Ensure to install debugging information, and then something like, > > systemctl stop NetworkManager > gdb /sbin/NetworkManager > > run --debug > > ... reproduce crash > > > backtrace (In reply to Jiri Klimes from comment #3) > I would help if you could recompile network-manager package first so that > there are debugging symbols in the backtrace. > > [1] https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces > [2] https://wiki.archlinux.org/index.php/Step-by-step_debugging_guide I just recompiled with debugging and since this is location dependent I will try to get there asap to get you more information. Thanks!
Starting program: /usr/bin/NetworkManager --debug [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". [New Thread 0x7ffff26de700 (LWP 4389)] NetworkManager[4388]: <info> NetworkManager (version 1.0.6) is starting... NetworkManager[4388]: <info> Read config: /etc/NetworkManager/NetworkManager.conf [New Thread 0x7ffff1edd700 (LWP 4390)] NetworkManager[4388]: <info> VPN: loaded org.freedesktop.NetworkManager.openvpn NetworkManager[4388]: <info> VPN: loaded org.freedesktop.NetworkManager.pptp [New Thread 0x7ffff16dc700 (LWP 4391)] NetworkManager[4388]: <info> Loaded settings plugin keyfile: (c) 2007 - 2015 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. NetworkManager[4388]: <info> keyfile: new connection /etc/NetworkManager/system-connections/#redacted NetworkManager[4388]: <info> keyfile: new connection /etc/NetworkManager/system-connections/#redacted NetworkManager[4388]: <info> keyfile: new connection /etc/NetworkManager/system-connections/#redacted NetworkManager[4388]: <info> keyfile: new connection /etc/NetworkManager/system-connections/#redacted NetworkManager[4388]: <info> keyfile: new connection /etc/NetworkManager/system-connections/#redacted NetworkManager[4388]: <info> keyfile: new connection /etc/NetworkManager/system-connections/#redacted NetworkManager[4388]: <info> keyfile: new connection /etc/NetworkManager/system-connections/#redacted NetworkManager[4388]: <info> keyfile: new connection /etc/NetworkManager/system-connections/#redacted NetworkManager[4388]: <info> keyfile: new connection /etc/NetworkManager/system-connections/#redacted NetworkManager[4388]: <info> keyfile: new connection /etc/NetworkManager/system-connections/#redacted NetworkManager[4388]: <info> keyfile: new connection /etc/NetworkManager/system-connections/#redacted NetworkManager[4388]: <info> keyfile: new connection /etc/NetworkManager/system-connections/#redacted NetworkManager[4388]: <info> keyfile: new connection /etc/NetworkManager/system-connections/#redacted NetworkManager[4388]: <info> keyfile: new connection /etc/NetworkManager/system-connections/#redacted NetworkManager[4388]: <info> keyfile: new connection /etc/NetworkManager/system-connections/#redacted NetworkManager[4388]: <info> keyfile: new connection /etc/NetworkManager/system-connections/#redacted NetworkManager[4388]: <info> keyfile: new connection /etc/NetworkManager/system-connections/#redacted NetworkManager[4388]: <info> monitoring kernel firmware directory '/usr/lib/firmware'. NetworkManager[4388]: <info> rfkill1: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.4/0000:05:00.0/ieee80211/phy0/rfkill1) (driver iwlwifi) NetworkManager[4388]: <info> WiFi hardware radio set enabled NetworkManager[4388]: <info> WWAN hardware radio set enabled NetworkManager[4388]: <info> Loaded device plugin: NMVxlanFactory (internal) NetworkManager[4388]: <info> Loaded device plugin: NMVlanFactory (internal) NetworkManager[4388]: <info> Loaded device plugin: NMVethFactory (internal) NetworkManager[4388]: <info> Loaded device plugin: NMTunFactory (internal) NetworkManager[4388]: <info> Loaded device plugin: NMMacvlanFactory (internal) NetworkManager[4388]: <info> Loaded device plugin: NMInfinibandFactory (internal) NetworkManager[4388]: <info> Loaded device plugin: NMGreFactory (internal) NetworkManager[4388]: <info> Loaded device plugin: NMEthernetFactory (internal) NetworkManager[4388]: <info> Loaded device plugin: NMBridgeFactory (internal) NetworkManager[4388]: <info> Loaded device plugin: NMBondFactory (internal) NetworkManager[4388]: <info> Loaded device plugin: NMWwanFactory (/usr/lib/NetworkManager/libnm-device-plugin-wwan.so) NetworkManager[4388]: <info> Loaded device plugin: NMTeamFactory (/usr/lib/NetworkManager/libnm-device-plugin-team.so) NetworkManager[4388]: <info> Loaded device plugin: NMAtmManager (/usr/lib/NetworkManager/libnm-device-plugin-adsl.so) NetworkManager[4388]: <info> Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/libnm-device-plugin-bluetooth.so) NetworkManager[4388]: <info> Loaded device plugin: NMWifiFactory (/usr/lib/NetworkManager/libnm-device-plugin-wifi.so) NetworkManager[4388]: <info> WiFi enabled by radio killswitch; enabled by state file NetworkManager[4388]: <info> WWAN enabled by radio killswitch; enabled by state file NetworkManager[4388]: <info> WiMAX enabled by radio killswitch; enabled by state file NetworkManager[4388]: <info> Networking is enabled by state file NetworkManager[4388]: <info> (enp4s0): new Ethernet device (carrier: OFF, driver: 'alx', ifindex: 2) NetworkManager[4388]: <info> (enp4s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] NetworkManager[4388]: <info> (docker0): new Bridge device (carrier: OFF, driver: 'bridge', ifindex: 4) NetworkManager[4388]: <info> (vmnet8): driver 'unknown' does not support carrier detection. NetworkManager[4388]: <info> (vmnet8): driver 'unknown' does not support carrier detection. NetworkManager[4388]: <info> (vmnet8): new Ethernet device (carrier: UNKNOWN, driver: 'unknown', ifindex: 7) NetworkManager[4388]: <info> (lo): link connected NetworkManager[4388]: <info> (lo): new Generic device (carrier: ON, driver: 'unknown', ifindex: 1) NetworkManager[4388]: <info> (wlp5s0): using nl80211 for WiFi device control NetworkManager[4388]: <info> (wlp5s0): driver supports Access Point (AP) mode NetworkManager[4388]: <info> (wlp5s0): new 802.11 WiFi device (carrier: UNKNOWN, driver: 'iwlwifi', ifindex: 3) NetworkManager[4388]: <info> (wlp5s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] NetworkManager[4388]: <info> (vmnet1): driver 'unknown' does not support carrier detection. NetworkManager[4388]: <info> (vmnet1): driver 'unknown' does not support carrier detection. NetworkManager[4388]: <info> (vmnet1): new Ethernet device (carrier: UNKNOWN, driver: 'unknown', ifindex: 5) NetworkManager[4388]: <info> (vmnet2): driver 'unknown' does not support carrier detection. NetworkManager[4388]: <info> (vmnet2): driver 'unknown' does not support carrier detection. NetworkManager[4388]: <info> (vmnet2): new Ethernet device (carrier: UNKNOWN, driver: 'unknown', ifindex: 6) NetworkManager[4388]: <info> wpa_supplicant running NetworkManager[4388]: <info> (wlp5s0) supports 5 scan SSIDs NetworkManager[4388]: <info> (wlp5s0): supplicant interface state: starting -> ready NetworkManager[4388]: <info> (wlp5s0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42] Program received signal SIGSEGV, Segmentation fault. on_bss_proxy_acquired (proxy=0x922c20, result=0x96f910, user_data=<optimized out>) at supplicant-manager/nm-supplicant-interface.c:157 157 in supplicant-manager/nm-supplicant-interface.c (gdb)
(In reply to Jiri Klimes from comment #4) > Actually, it might be the bug fixed in Red Hat bugzilla > (https://bugzilla.redhat.com/show_bug.cgi?id=1266003). > > The fix is > http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=nm-1- > 0&id=9736327b2616861dfec181e88f908a18b22d781c (In reply to juliovalcarcel3 from comment #6) > Program received signal SIGSEGV, Segmentation fault. > on_bss_proxy_acquired (proxy=0x922c20, result=0x96f910, user_data=<optimized > out>) > at supplicant-manager/nm-supplicant-interface.c:157 > 157 in supplicant-manager/nm-supplicant-interface.c > (gdb) Thank you for reproducing. It is as Jirka said and it's already fixed: master: http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=33527341b1e35034a4f1736df4bc98f8ac8418ab nm-1-0: http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=9736327b2616861dfec181e88f908a18b22d781c