ubuntu-phone team mailing list archive
-
ubuntu-phone team
-
Mailing list archive
-
Message #11485
Broken connectivity and wakeup/suspend loop on krillin with RTM
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
since a week or two I notice increased instability of connectivity on
my krillin device during daily usage.
The symptoms are visible in that networking starts failing to connect.
Mostly when switching from WiFi to 3G or back. At some point it just
stops connecting to 3G or WiFi and it stops listing wireless networks
at all. Making phone calls doesn't work any more either although the
indicator suggests it would be registered to GSM.
I just started to examine the logs and found something suspicious in
syslog. It seems that the device was stuck in a wakeup-suspend loop
for the whole night, producing dozens of messages in syslog every
second. Interestingly the battery still survived throughout the night.
I'm not too familiar with the kernel/networkmanager/powerd/ofono
things so I'm having a bit troubles to identify what's actually wrong
and for what component to report the bug. Here's the syslog from last
night:
http://notyetthere.org/data/syslog.wakeuploop
Some more things I tried:
* enabling/disabling flight mode doesn't seem to help. The indicator
claims to reregister to GSM after I enter the SIM PIN, but still
doesn't fix the fact that phone calls can't be done or any data
connection fails.
* rfkill looks ok (nothing blocked) afaict
* the device seems to behave ok otherwise (no spinning processes and
the UI is smooth)
* The device is updated to the latest image (r21) but I noticed this
behaviour with the previous update already.
* I remember that I received a phone call yesterday evening. That was
working fine still. Next time I checked (some hours later),
connectivity was gone but I didn't have time to investigate yesterday
night.
Anyone has an idea what this might be, or could tell me what component
I should file a bug for? I think I can reliably reproduce this when
not rebooting the phone for a couple of days and using it normally for
a while.
Thanks,
Michael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iEYEARECAAYFAlUFo14ACgkQXJwWsxE5x7jMYACggbkYNlhO5/vCXXDs9dZGQXWO
5oIAn3p10TVv2kxP5Cck5OyuTABtXHmX
=3Fd4
-----END PGP SIGNATURE-----
Follow ups