Re: [MM] 'qmi-support' branch merged to git master
- From: Aleksander Morgado <aleksander lanedo com>
- To: Bjørn Mork <bjorn mork no>
- Cc: Network Manager <networkmanager-list gnome org>
- Subject: Re: [MM] 'qmi-support' branch merged to git master
- Date: Thu, 30 Aug 2012 10:00:05 +0200
Hey Bjørn,
>
>>> ModemManager[25642]: KEY: 04:00:05:01:00:00:00:00
>>> ModemManager[25642]: Service: 01
>>> ModemManager[25642]: Client ID: 05
>>> ModemManager[25642]: Transaction ID: 04:00
>>>
>>> (ModemManager:25642): GLib-GIO-CRITICAL **: g_simple_async_result_take_error: assertion `error != NULL' failed
>>> Segmentation fault
>>
>> Oh; interesting... can you get me a backtrace?
>
>>>>>>> translated = FAILURE: NoEffect
>
>
> Sure:
>
>
> ModemManager[28552]: [/dev/cdc-wdm0] Received message...
>>>>>>> QMUX:
>>>>>>> length = 19
>>>>>>> flags = 0x80
>>>>>>> service = "wds"
>>>>>>> client = 1
>>>>>>> QMI:
>>>>>>> flags = "response"
>>>>>>> transaction = 4
>>>>>>> tlv_length = 7
>>>>>>> message = "Start Network" (0x0020)
>>>>>>> TLV:
>>>>>>> type = "Result" (0x02)
>>>>>>> length = 4
>>>>>>> value = 01:00:1A:00
> ModemManager[28552]: KEY: 04:00:01:01:00:00:00:00
> ModemManager[28552]: Service: 01
> ModemManager[28552]: Client ID: 01
> ModemManager[28552]: Transaction ID: 04:00
>
> (ModemManager:28552): GLib-GIO-CRITICAL **: g_simple_async_result_take_error: assertion `error != NULL' failed
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x000000000044613b in connect_finish (self=<optimized out>, res=<optimized out>, data=0x7fffffffe118, ipv4_config=0x7fffffffe120, ipv6_config=0x7fffffffe128, error=0x7fffffffe110)
> at mm-bearer-qmi.c:140
> 140 *data = MM_PORT (g_object_ref (result->data));
> (gdb) bt
> #0 0x000000000044613b in connect_finish (self=<optimized out>, res=<optimized out>, data=0x7fffffffe118, ipv4_config=0x7fffffffe120, ipv6_config=0x7fffffffe128, error=0x7fffffffe110)
> at mm-bearer-qmi.c:140
> #1 0x00000000004411d6 in connect_ready (self=0x7da3c0, res=<optimized out>, simple=0x7c5990) at mm-bearer.c:183
> #2 0x00007ffff72763f7 in g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
> #3 0x00007ffff72764f9 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
> #4 0x00007ffff6d09205 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
> #5 0x00007ffff6d09538 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
> #6 0x00007ffff6d09932 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
> #7 0x00000000004376f7 in main (argc=<optimized out>, argv=<optimized out>) at main.c:150
>
>
When we get a 'No-Effect' error as response to Start Network, I was
assuming that it means that the connection was already on and we
succeeded. But; we won't get a packet data handle which we can
afterwards use in Stop Network... (that's the root cause of the segfault).
Maybe we need to retry when we get a No-Effect error? or maybe
autoconnect was on and we're then entitled to use a global handle in
Stop Network?
--
Aleksander
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]