Sierra Wireless 340u - NotInitialized

[Shawn J. Goff]

A backgrace from the segfault:

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff6d7dc68 in __gconv () from /usr/lib/libc.so.6
(gdb) bt
#0  0x00007ffff6d7dc68 in __gconv () from /usr/lib/libc.so.6
#1  0x00007ffff6d7d209 in iconv () from /usr/lib/libc.so.6
#2  0x00007ffff7134255 in g_convert_with_iconv () from /usr/lib/libglib-2.0.so.0
#3  0x00007ffff7134498 in g_convert () from /usr/lib/libglib-2.0.so.0
#4  0x00007ffff7bc541a in _mbim_message_read_string_array
(self=self at entry=0x63ba40, array_size=<optimized out>,
relative_offset_array_start=relative_offset_array_start at entry=28) at
mbim-message.c:233
#5  0x00007ffff7bccc8c in
mbim_message_subscriber_ready_status_response_parse
(message=message at entry=0x63ba40,
ready_state=ready_state at entry=0x7fffffffe734,
subscriber_id=subscriber_id at entry=0x7fffffffe748,
    sim_icc_id=sim_icc_id at entry=0x7fffffffe750,
ready_info=ready_info at entry=0x7fffffffe738,
telephone_numbers_count=telephone_numbers_count at entry=0x7fffffffe73c,
telephone_numbers=telephone_numbers at entry=0x7fffffffe758,
    error=error at entry=0x7fffffffe740) at mbim-basic-connect.c:1211
#6  0x0000000000403e94 in query_subscriber_ready_status_ready
(device=0x640840, res=<optimized out>) at mbimcli-basic-connect.c:342
#7  0x00007ffff78caac7 in g_simple_async_result_complete () from
/usr/lib/libgio-2.0.so.0
#8  0x00007ffff78cab29 in ?? () from /usr/lib/libgio-2.0.so.0
#9  0x00007ffff714fe46 in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#10 0x00007ffff7150198 in ?? () from /usr/lib/libglib-2.0.so.0
#11 0x00007ffff715059a in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#12 0x0000000000402c46 in main (argc=1, argv=0x7fffffffe9e8) at mbimcli.c:336

On Wed, May 29, 2013 at 5:09 PM, Shawn J. Goff <shawn7400 at gmail.com> wrote:
> I'm working with a Sierra Wireless (now NetGear) AirCard 340u, and
> there are some problems.
>
> When trying to connect, the modem returns a NotInitialized status. I'm
> not sure what this means. It's registered and attached to the packet
> service. The verbose output is attached.
>
> When querying the subscriber ready status, it has a segfault after
> many string conversion errors; subsequent runs complain about a
> failing assertion. The errors came on stderr and the verbose output is
> on stdout, so there are two attached files for that.
>
>
> The rest of the commands seem to work fine.