Re: [MM] glib assertions
FYI, while running suspend/resume stress tests on various modems, MM gives a few glib assertion warnings. I'm going to run gdb to get a backtrace, but wonder if you know where the issue could potentially be. (ModemManager:648): GLib-GIO-CRITICAL **: g_dbus_connection_emit_signal: assertion `G_IS_DBUS_CONNECTION (connection)' failed (ModemManager:648): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed (ModemManager:648): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed Also, I had to take out the following assertion in MMBroadbandModem disabling_step() to prevent a crash. It seems like a race when mm_base_modem_disable() is being called on MMBaseModem and MMBroardbandModem is being disposed. Should we turn the assertion into a condition check instead? case DISABLING_STEP_IFACE_MODEM: g_assert (ctx-self-priv-modem_dbus_skeleton != NULL); Thread 0 (crashed) 0 libc-2.15.so!raise [raise.c : 64 + 0x10] rbx = 0x7fcfdec08260 r12 = 0x7fcf52c4 r13 = 0x7fcfdec073e0 r14 = 0x7fcfdd8d3960 r15 = 0x7fcfdeabd800 rip = 0x7fcfdd224aa5 rsp = 0x7fff300c3e18 rbp = 0x7fcfdd8d4260 Found by: given as instruction pointer in context 1 libc-2.15.so!abort [abort.c : 91 + 0x9] rbx = 0x7fcfdec08260 r12 = 0x7fcf52c4 r13 = 0x7fcfdec073e0 r14 = 0x7fcfdd8d3960 r15 = 0x7fcfdeabd800 rip = 0x7fcfdd225f07 rsp = 0x7fff300c3e20 rbp = 0x7fcfdd8d4260 Found by: call frame info 2 libglib-2.0.so.0.3200.4!g_assertion_message [gtestutils.c : 1861 + 0x4] rbx = 0x7fcfdec08260 r12 = 0x7fcf52c4 r13 = 0x7fcfdec073e0 r14 = 0x7fcfdd8d3960 r15 = 0x7fcfdeabd800 rip = 0x7fcfdd81b83d rsp = 0x7fff300c3f50 rbp = 0x7fcfdd8d4260 Found by: call frame info 3 libglib-2.0.so.0.3200.4!g_assertion_message_expr [gtestutils.c : 1872 + 0xc] rbx = 0x7fcfdddc52d0 r12 = 0x7fcf52c4 r13 = 0x r14 = 0x7fcfdd8d3960 r15 = 0x7fcfdeabd800 rip = 0x7fcfdd81bd12 rsp = 0x7fff300c3fe0 rbp = 0x1b45 Found by: call frame info 4 ModemManager!disabling_step [mm-broadband-modem.c : 6981 + 0x20] rbx = 0x7fcfdec0ed00 r12 = 0x0041 r13 = 0x7fcfdeac4f00 r14 = 0x7fcfdd8d3960 r15 = 0x7fcfdeabd800 rip = 0x7fcfddda6571 rsp = 0x7fff300c4010 rbp = 0x7fcfdeaf4200 Found by: call frame info 5 ModemManager!handle_enable_auth_ready [mm-iface-modem.c : 1216 + 0x4] rbx = 0x7fcfdec0fd30 r12 = 0x0041 r13 = 0x7fcfdeac4f00 r14 = 0x7fcfdd8d3960 r15 = 0x7fcfdeabd800 rip = 0x7fcfddd84379 rsp = 0x7fff300c4020 rbp = 0x7fcfdeaf4200 Found by: call frame info 6 libgio-2.0.so.0.3200.4!g_simple_async_result_complete [gsimpleasyncresult.c : 767 + 0xd] rbx = 0x7fcfdeb03e30 r12 = 0x0041 r13 = 0x7fcfdeac4f00 r14 = 0x7fcfdd8d3960 r15 = 0x7fcfdeabd800 rip = 0x7fcfddbd0447 rsp = 0x7fff300c4050 rbp = 0x7fcfdec0e650 Found by: call frame info 7 ModemManager!authorize_ready [mm-base-modem.c : 1015 + 0x7] rbx = 0x7fcfdeb03e30 r12 = 0x0041 r13 = 0x7fcfdeac4f00 r14 = 0x7fcfdd8d3960 r15 = 0x7fcfdeabd800 rip = 0x7fcfddd7a161 rsp = 0x7fff300c4070 rbp = 0x7fcfdec0e650 Found by: call frame info 8 libgio-2.0.so.0.3200.4!g_simple_async_result_complete [gsimpleasyncresult.c : 767 + 0xd] rbx = 0x7fcfdeb040f0 r12 = 0x0041 r13 = 0x7fcfdeac4f00 r14 = 0x7fcfdd8d3960 r15 = 0x7fcfdeabd800 rip = 0x7fcfddbd0447 rsp = 0x7fff300c4090 rbp = 0x7fcfdec0e650 Found by: call frame info 9 libgio-2.0.so.0.3200.4!complete_in_idle_cb [gsimpleasyncresult.c : 779 + 0x4] rbx = 0x7fcfdec0e650 r12 = 0x0041 r13 = 0x7fcfdeac4f00 r14 = 0x7fcfdd8d3960 r15 = 0x7fcfdeabd800 rip = 0x7fcfddbd0549 rsp = 0x7fff300c40b0 rbp = 0x0001 Found by: call frame info 10 libglib-2.0.so.0.3200.4!g_main_context_dispatch [gmain.c : 2539 + 0x3] rbx = 0x7fcfdec0e650 r12 = 0x0041 r13 = 0x7fcfdeac4f00 r14 = 0x7fcfdd8d3960 r15 = 0x7fcfdeabd800 rip = 0x7fcfdd7fa5c3 rsp = 0x7fff300c40c0 rbp = 0x0001 Found by: call frame info 11 libglib-2.0.so.0.3200.4!g_main_context_iterate [gmain.c : 3146 + 0x7] rbx = 0x7fcfdeabd800 r12 = 0x7fcfdd807d70 r13 = 0x r14 = 0x0002 r15 = 0x0001 rip = 0x7fcfdd7fa940 rsp = 0x7fff300c4150 rbp = 0x0001 Found by: call frame info 12
F17 and 0.9.7.0
I am running Fedora 17 but would like to update to NetworkManager-0.9.7.0. There are src and binary rpms for F18 but it is not practical to use the F18 binaries on F17 so I need to rebuild them on F17 ... no problem ... for NetworkManager itself. But 0.9.7.0 splits out the network-manager-applet into a separate src and binary package. Unfortunately, to build the network-manager-applet package needs NetworkManager-devel and NetworkManager-glib-devel and those packages in turn need the rest of 0.9.7.0 packages and, of course, the NetworkManager-gnome package needs to be removed also. The only way I can see to build the network-manager-applet package is to: 1. stop NetworkManager 2. yum localinstall the 0.9.7.0 NetworkManager packages and remove the old gnome and gtk packages. 3. build network-manager-applet package and install with yum localinstall or rpm 4. start NetworkManaer I believe that this will work but is there any other (simpler) way? Gene ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
failed to set IPv6 default route
I have been doing some work trying to improve IPv6 dhcp support in NetworkManager. This has involved a lot of (virtual) testing. One thing I began to notice is a lot of the following message appearing in syslog: [nm-system.c:1121] nm_system_replace_default_ip6_route(): (p32p1): failed to set IPv6 default route: -7 The only way I have been able to get an IPv6 default route set is to use manual configuration and specify a gateway. Everything else seems to produce this message. OK, is this a bug or is there something about configuration I do not understand? Gene ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [MM] glib assertions
Hey Ben, I created a pair of bug reports in bugzilla for these, to better track them; see the links below. Will follow up on them directly in bugzilla. FYI, while running suspend/resume stress tests on various modems, MM gives a few glib assertion warnings. I'm going to run gdb to get a backtrace, but wonder if you know where the issue could potentially be. (ModemManager:648): GLib-GIO-CRITICAL **: g_dbus_connection_emit_signal: assertion `G_IS_DBUS_CONNECTION (connection)' failed (ModemManager:648): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed (ModemManager:648): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed https://bugzilla.gnome.org/show_bug.cgi?id=684693 Also, I had to take out the following assertion in MMBroadbandModem disabling_step() to prevent a crash. It seems like a race when mm_base_modem_disable() is being called on MMBaseModem and MMBroardbandModem is being disposed. Should we turn the assertion into a condition check instead? case DISABLING_STEP_IFACE_MODEM: g_assert (ctx-self-priv-modem_dbus_skeleton != NULL); https://bugzilla.gnome.org/show_bug.cgi?id=684694 Cheers! -- Aleksander ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: F17 and 0.9.7.0
On 09/23/2012 06:50 AM, Gene Czarcinski wrote: The only way I can see to build the network-manager-applet package is to: 1. stop NetworkManager 2. yum localinstall the 0.9.7.0 NetworkManager packages and remove the old gnome and gtk packages. 3. build network-manager-applet package and install with yum localinstall or rpm 4. start NetworkManaer I believe that this will work but is there any other (simpler) way? Yes, you could use smock. It does chainbuilds and creates a small repo in your home dir to satisfy the dependency chain. I used it as follows to do *exactly* the same thing NM 0.9.7.0 on F17. smock --arch=x86_64 --distro=fedora-17 NetworkManager_src.rpm network-manager-applet-_src.rpm It built both and then in my ~/smock/yum/fedora-17/x86_64/ I've attached a modified version that uses threads to build packages quicker if you are building for multiple arches and distros. -- Nathanael d. Noblet t 403.875.4613 smock-threaded.pl Description: Perl program ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
