I get a similar output when provoking the bug with gnome-system-monitor,
although the part where the device is suddenly removed and reinitialized
a few seconds later (959.866236-982.994272) does not occur. The call
stack is only slightly different from mine (see dmesg.log and
traces.diff).

Since the other bug is provoked by netspeed_applet, I suspect that tuco
(and most of the other posters) use NetworkManager to configure their
WLANs. As mentioned above, this immediately kills the system, too (I use
the "manual configuration"). Their machines boot up, try to use
NetworkManager and provoke a kernel? bug that prevents most applications
from being launched (including GDM), rendering the system unusable.

Although I do not get the connection issue when using gnome-system-
monitor, I have already seen this output together with the
URB/usb_read_write_sync messages from his syslog after some random
lockups (they are probably all aspects of the same problem) of my system
(parts from my kern.log are attached, they are NOT RELATED to the gnome-
system-manager issue!). The last timestamp in my kern.log (3502.807284)
is plainly wrong, the system was long rebooted by then.

I have compressed the logs to upload them as a single file.

** Attachment added: "dmesg.log, traces.diff, kern.log"
   http://launchpadlibrarian.net/15240747/logs.tar.bz2

-- 
gnome-system-monitor crashes when wifi (fwlanusb) statistics are queried
https://bugs.launchpad.net/bugs/222213
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to