After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 760154 - NetworkManager crashes with a segfault when I modprobe my WiFi module
NetworkManager crashes with a segfault when I modprobe my WiFi module
Status: RESOLVED FIXED
Product: NetworkManager
Classification: Platform
Component: general
1.0.x
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2016-01-05 11:54 UTC by daltonfury42
Modified: 2016-01-06 21:44 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
logfile and backtrace (130.27 KB, text/plain)
2016-01-06 20:13 UTC, Thomas Haller
Details

Description daltonfury42 2016-01-05 11:54:11 UTC
I run arch linux (kernel 4.3.3-2-ARCH) and my WiFi card is a RT3290LE. SInce my WiFi signal is very weak, I am trying to install a patched module for the card from AUR (Arch User Repo). But when the driver loads, networkmanager crashes just after renaming of my ethernet interface:

[   61.949615] rt2860 0000:09:00.0 enp9s0f0: renamed from ra0
[   61.982199] NetworkManager[339]: segfault at 8 ip 00000000004ca126 sp 00007fff6887e868 error 4 in NetworkManager[400000+1c5000]

Here is are the entire entries made during loading of the module:

http://pastebin.com/hxxdJZ05
Comment 1 Thomas Haller 2016-01-05 12:25:48 UTC
Can you install debugging symbols and run NetworkManager under gdb to provide a stack trace of the crash?
Comment 2 daltonfury42 2016-01-06 18:04:33 UTC
I did that. But the trace came out empty. Here it is:

http://pastebin.ubuntu.com/14422493/

I guess the modprobe crashed some library. Shall I close this bug?
Comment 3 Thomas Haller 2016-01-06 18:54:33 UTC
I think this is not yet enough to hunt down the issue.

I'm closing this BZ for now, but feel invited to reopen and/or provide more information so we can check again -- especially if you can reproduce the crash it would be appreciated.

thank you
Comment 4 daltonfury42 2016-01-06 18:58:41 UTC
I can reproduce the crash. I am feeling kinda desperate. I need wifi because I live in a college hostel and I can't get internet in my room without it. If you can tell me where exactly to look for information, I will be happy to invest any amount of time on it.
Comment 5 Thomas Haller 2016-01-06 19:05:16 UTC
which distro are you using? I assume you installed NetworkManager from a distribution-provided package? Which NM version? Which package version?


Make sure you install the relevant debugging information, which is usually in a separate package, e.g. NetworkManager-debuginfo on Fedora/RHEL.





Stop NetworkManager, and start it in a debugger:

  systemctl stop NetworkManager
  gdb /sbin/NetworkManager
  > run --debug --log-level=DEBUG


Reproduce the crash, and show the backtrace ("backtrace" command in gdb).


You can also ask for help on #nm on irc.freenode.net.
Comment 6 daltonfury42 2016-01-06 19:14:10 UTC
NM version: networkmanager-1.0.10-2-x86_64

I am using Arch Linux. We have the Arch build system, (ABS) from which we can compile official packages for debugging purposes. More info about it here:

https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces


I did just as it is given in the above wiki, and the trace is posted in comment #2. The only difference is that I had to start with --no-daemon flag and I did not specify a log level. I will redo it and post back the result.


If you are online in the irc, I can come online right now.
Comment 7 Thomas Haller 2016-01-06 19:20:44 UTC
I see...

the backtrace you posted doesn't show a crash inside NetworkManager's code, that's why the cause is unclear.


Can you also provide a logfile with --log-level=TRACE ?   (TRACE is more verbose then DEBUG, but this logging level was only introduced with verion 1.0). For that, configure

[logging]
level=TRACE

in /etc/NetworkManager/NetworkManager.conf and restart + reproduce the crash.


(better attach the logfile in bugzilla then pastebin, because pastebin will eventually expire).
Comment 8 Thomas Haller 2016-01-06 20:13:02 UTC
Created attachment 318381 [details]
logfile and backtrace

Attaching logfile from reporter (via IRC) for later reference.