From: sre@kernel.org (Sebastian Reichel)
To: linux-arm-kernel@lists.infradead.org
Subject: 4.5-rc0 regression: GPRS breaks after very short while
Date: Wed, 18 May 2016 16:16:25 +0200 [thread overview]
Message-ID: <20160518141624.GA8025@earth> (raw)
In-Reply-To: <20160518074924.GA20652@amd>
Hi Pavel,
On Wed, May 18, 2016 at 09:49:24AM +0200, Pavel Machek wrote:
> I was afraid another GSM chip desoldered itself in N900, but no, it
> seems to be software this time.
>
> In 4.4, GPRS is rock solid, can survive overnight ping.
>
> In 4.5-rc0 and v4.6, modem fails when I use gprs for like a
> minute. Phone is not usable.
I only send three modem related changes for v4.5:
https://git.kernel.org/cgit/linux/kernel/git/sre/linux-hsi.git/commit/?h=hsi-for-4.5&id=525e1abc6b5a7d8bd9006de1da6e99722305ea2b
HSI: omap_ssi: fix handling ida_simple_get result
https://git.kernel.org/cgit/linux/kernel/git/sre/linux-hsi.git/commit/?h=hsi-for-4.5&id=6bf6ded3008a407ccab5ad72eb59ab71b97cc290
HSI: omap_ssi_port: fix handling of_get_named_gpio result
https://git.kernel.org/cgit/linux/kernel/git/sre/linux-hsi.git/commit/?h=hsi-for-4.5&id=403c5c0650816375527a6feecfb255d9b494dda3
HSI: Remove struct hsi_client private fields from kernel-doc
The last one only changes a comment, so not relevant, the other
two fix error handling during initialization and are most likely
also not the problem. Can you try to bisect the problem?
-- Sebastian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160518/bf6ba04e/attachment.sig>
next prev parent reply other threads:[~2016-05-18 14:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 7:49 4.5-rc0 regression: GPRS breaks after very short while Pavel Machek
2016-05-18 14:16 ` Sebastian Reichel [this message]
2016-05-18 20:12 ` Pavel Machek
2016-05-20 4:12 ` Sebastian Reichel
2016-06-18 10:39 ` Pavel Machek
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=20160518141624.GA8025@earth \
--to=sre@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).