From: Pavel Machek <pavel@ucw.cz>
To: pali.rohar@gmail.com, sre@kernel.org,
kernel list <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-omap@vger.kernel.org, tony@atomide.com, khilman@kernel.org,
aaro.koskinen@iki.fi, ivo.g.dimitrov.75@gmail.com,
patrikbachan@gmail.com, serge@hallyn.com
Subject: 4.5-rc0 regression: GPRS breaks after very short while
Date: Wed, 18 May 2016 09:49:24 +0200 [thread overview]
Message-ID: <20160518074924.GA20652@amd> (raw)
Hi!
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.
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
WARNING: multiple messages have this Message-ID (diff)
From: pavel@ucw.cz (Pavel Machek)
To: linux-arm-kernel@lists.infradead.org
Subject: 4.5-rc0 regression: GPRS breaks after very short while
Date: Wed, 18 May 2016 09:49:24 +0200 [thread overview]
Message-ID: <20160518074924.GA20652@amd> (raw)
Hi!
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.
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next reply other threads:[~2016-05-18 7:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 7:49 Pavel Machek [this message]
2016-05-18 7:49 ` 4.5-rc0 regression: GPRS breaks after very short while Pavel Machek
2016-05-18 14:16 ` Sebastian Reichel
2016-05-18 14:16 ` Sebastian Reichel
2016-05-18 20:12 ` Pavel Machek
2016-05-18 20:12 ` Pavel Machek
2016-05-20 4:12 ` Sebastian Reichel
2016-05-20 4:12 ` Sebastian Reichel
2016-06-18 10:39 ` Pavel Machek
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=20160518074924.GA20652@amd \
--to=pavel@ucw.cz \
--cc=aaro.koskinen@iki.fi \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=pali.rohar@gmail.com \
--cc=patrikbachan@gmail.com \
--cc=serge@hallyn.com \
--cc=sre@kernel.org \
--cc=tony@atomide.com \
/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.