From: Jonas Bonn <jonas@norrbonn.se>
To: ofono@ofono.org
Subject: Re: Unsalble cellular connection
Date: Sat, 17 Aug 2019 16:09:25 +0200 [thread overview]
Message-ID: <4f986d7d-e3b7-a3e3-eeff-df0b848f3438@norrbonn.se> (raw)
In-Reply-To: <CAA=hcWTb79iKcxmuCxBK59ybuegAv37i0e4UCf176wcSDrEr=w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1213 bytes --]
Hi JH,
On 17/08/2019 13:55, JH wrote:
> On 8/17/19, JH <jupiter.hce@gmail.com> wrote:
>> On 8/16/19, Daniel Wagner <wagi@monom.org> wrote:
>>> The NTP code is just telling it can't reach the server. This has no
>>> direct connenction to the next entry.
>>
>> So that from NTP, don't need to worry about it.
>>
>>> This message is from the kernel via RTNL interface. The kernel tells
>>> ConnMan the interface state has changed.
>>
>> OK, all from kernel, what could make the kernel to delete the link?
What does the kernel log show?
>>
>>
>>>> connmand[213]: Skipping disconnect of /ubloxqmi_0/context1, network is
>>>> connecting.
>>>> connmand[213]: ipconfig state 2 ipconfig method 1
>>
>>> Your log does not contain the debug information (connmand -d).
>>
>> I attached two log files running in debug, doesn't seem
>>
>> $ OFONO_QMI_DEBUG=1 ofonod -d
>>
>> $ connmand -d
>
> Oops, pressed wrong key, both debug log files attached, looks even
> less information from running ofono -n and connman -n by systemd.
>
It looks like you've multiple instances of connman and ofono running
there, that's why you've got nothing in the logs. Give this another try.
/Jonas
next prev parent reply other threads:[~2019-08-17 14:09 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAA=hcWSVcULFW4jo5q9RsxW4igozgM99oJN6KoZ8UaSLdLhD7g@mail.gmail.com>
2019-08-13 15:00 ` Unsalble cellular connection Jonas Bonn
2019-08-14 11:11 ` JH
2019-08-14 13:00 ` Jonas Bonn
2019-08-15 11:33 ` Daniel Wagner
2019-08-15 12:45 ` JH
2019-08-15 14:58 ` Daniel Wagner
2019-08-17 11:53 ` JH
2019-08-17 11:55 ` JH
2019-08-17 14:09 ` Jonas Bonn [this message]
2019-08-17 22:29 ` JH
[not found] <CAOf5uw=fQe4cuTfdciqW3hmXHXv-tY2UYd4aLfMVxF5Lx65jbw@mail.gmail.com>
2019-08-19 8:17 ` Jonas Bonn
[not found] <CAOf5uw=6hQkfhAt=OWH+mim30NyOHU6Z8GVMJ6yKCEf=1NFw8w@mail.gmail.com>
2019-08-19 7:50 ` Jonas Bonn
2019-08-19 7:56 ` Jonas Bonn
[not found] <CAOf5uw=2U6MkcKP8OzWNyzwvxjAvYLdXuDASFVEjnWvMQ0fjHw@mail.gmail.com>
2019-08-19 1:51 ` JH
2019-08-19 5:38 ` Jonas Bonn
2019-08-19 14:18 ` JH
2019-08-01 11:01 JH
2019-08-01 18:16 ` Giacinto Cifelli
2019-08-02 10:46 ` JH
2019-08-02 17:43 ` Giacinto Cifelli
2019-08-07 10:27 ` JH
2019-08-09 3:59 ` Giacinto Cifelli
2019-08-09 12:56 ` JH
2019-08-11 11:57 ` JH
2019-08-11 13:37 ` Giacinto Cifelli
2019-08-12 6:54 ` JH
2019-08-12 22:09 ` JH
2019-08-13 6:42 ` Jonas Bonn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4f986d7d-e3b7-a3e3-eeff-df0b848f3438@norrbonn.se \
--to=jonas@norrbonn.se \
--cc=ofono@ofono.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.