All of lore.kernel.org
 help / color / mirror / Atom feed
From: Giacinto Cifelli <gciofono@gmail.com>
To: ofono@ofono.org
Subject: Re: Unsalble cellular connection
Date: Fri, 09 Aug 2019 05:59:32 +0200	[thread overview]
Message-ID: <CAKSBH7Fy-sPKYLMxXw0bK9He7E2u1tu=b9y8cbOrRVyokFEYjA@mail.gmail.com> (raw)
In-Reply-To: <CAA=hcWQ9=UkLmxT-3oRQah8ArUBExz=khvGGt8sMSOD4gv-ogA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1408 bytes --]

Hi,

On Wed, Aug 7, 2019 at 12:27 PM JH <jupiter.hce@gmail.com> wrote:
>
> Hi Giacinto,
>
> Just got response from the hardware contractor.
>
> On 8/3/19, Giacinto Cifelli <gciofono@gmail.com> wrote:
> > Hi jupiter,
>
> > This signal level is output periodically by ofono in a signal.
> > You can try to catch all ofono signals (these are dbus events, not to
> > be confused with signal level and network signaling) with
> > dbus-monitor.
> > But I think the signal is ok.
> > Only the network disables the PDP context. maybe without informing the
> > modem.
> > This is done by several networks.
> >
> >> The trouble is it connected well at
> >> startup, then dropped it, it is hard to convince the hardware
> >> contractor it is hardware problem unless I have strong evidence that
> >> is not the software problem.
> >
> > Ask uBlox how to capture a protocol stack trace, and if it is feasible
> > for your application, do it and have it analyzed by uBlox.
> >
> > Are you on GSM, on LTE catM or on LTE NB-IOT when this happens? On
> > which network operator and country?
>
> It is LTE Cat-M1, the operator is Telstra in Australia. I will be very
> interested in finding out what is going on.

you need stack traces.
Most likely the chipset you are using is the MDM9205, so the trace will be QXDM.

>
> Thank you.
>
> Kind regards,
>
> - jupiter

BR,
Giacinto

  reply	other threads:[~2019-08-09  3:59 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-01 11:01 Unsalble cellular connection 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 [this message]
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
     [not found] <CAA=hcWSVcULFW4jo5q9RsxW4igozgM99oJN6KoZ8UaSLdLhD7g@mail.gmail.com>
2019-08-13 15:00 ` 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
2019-08-17 22:29                 ` JH
     [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
     [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=fQe4cuTfdciqW3hmXHXv-tY2UYd4aLfMVxF5Lx65jbw@mail.gmail.com>
2019-08-19  8:17 ` 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='CAKSBH7Fy-sPKYLMxXw0bK9He7E2u1tu=b9y8cbOrRVyokFEYjA@mail.gmail.com' \
    --to=gciofono@gmail.com \
    --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.