Thanks for posting the problem and a possible soultion.
To help with debugging you could do the following:
A good testcase is a step by step instruction to reproduce your bug starting with driver unloaded and NetworkManager stopped.
Kill NetworkManager
sudo killall NetworkManager
To unload your driver modprobe -r DRIVER .
Then load the driver and start NetworkManager:
sudo NetworkManager
Capture Log
In order to understand whats going on and track down issues, its good to have a full log. To do so, capture the complete test case and submit the whole file (don't cut out what you think is important). Please add markers in the log file so the bug triager can easily see what actions the user takes at what point of time (this isn't essential, but helps a lot).
To capture the syslog, do:
tail -n0 -f /var/log/syslog > /tmp/syslog
and to stop capturing do Ctrl-C (you will have to type your other commands in an other window or tab)
Adding markers is just like adding new lines with an editor that show the triager what happened at what point of time.
(gdb) bt
...
(gdb) bt full
...
(gdb) thread apply all bt full
...
and attach the backtrace above together with your /var/log/syslog to the bug.
Driver Logs
When a bug appears to be driver related or you are asked by a bug triager to submit a driver enabled log, you need to enable driver logging right before you start to capture your testcase. How to do that depends on the driver you use and whether it has been with compiled with debug support.
Thanks for posting the problem and a possible soultion.
To help with debugging you could do the following:
A good testcase is a step by step instruction to reproduce your bug starting with driver unloaded and NetworkManager stopped.
Kill NetworkManager
sudo killall NetworkManager
To unload your driver modprobe -r DRIVER .
Then load the driver and start NetworkManager:
sudo NetworkManager
Capture Log
In order to understand whats going on and track down issues, its good to have a full log. To do so, capture the complete test case and submit the whole file (don't cut out what you think is important). Please add markers in the log file so the bug triager can easily see what actions the user takes at what point of time (this isn't essential, but helps a lot).
To capture the syslog, do:
tail -n0 -f /var/log/syslog > /tmp/syslog
and to stop capturing do Ctrl-C (you will have to type your other commands in an other window or tab)
Adding markers is just like adding new lines with an editor that show the triager what happened at what point of time.
Example marker:
Sep 6 08:12:30 ...
[ clicked on wireless network 'ubuntu']
Sep 6 08:12:31 ...
...
Debugging Crashes
To install debug symbols, add the following line to your /etc/apt/ sources. list
deb http:// ddebs.ubuntu. com/~ubuntu- archive/ ddebs/ gutsy main universe
Then install the appropriate dbgsym packages:
sudo apt-get update manager- dbgsym libnm-util0-dbgsym libnm-glib0-dbgsym libglib2.0-0-dbgsym
sudo apt-get install network-
Then restart NetworkManager:
sudo /etc/dbus- 1/event. d/25NetworkMana ger restart
Attach the debugger to the pid of NetworkManager
sudo gdb /usr/bin/ NetworkManager $(pidof NetworkManager)
...
(gdb) continue
Once it crashes get a backtrace
(gdb) bt
...
(gdb) bt full
...
(gdb) thread apply all bt full
...
and attach the backtrace above together with your /var/log/syslog to the bug.
Driver Logs
When a bug appears to be driver related or you are asked by a bug triager to submit a driver enabled log, you need to enable driver logging right before you start to capture your testcase. How to do that depends on the driver you use and whether it has been with compiled with debug support.