English

FP2 random reboots - see #rebootsguide for help

bootissues
randomreboots
Tags: #<Tag:0x00007fefbd348758> #<Tag:0x00007fefbd348460>

#599

As far as we know there is no link between the random reboot issue and the display in use. I’d advice you to get in contact with support to have your case looked at.


#600

Like @glouton , I have an older FP2 that still randomly reboots. Is the update expected to reduce / eliminate reboots on previous batches? Mine was purchased in May 2016.


#601

hey @dalq0001, thank you for your clarifying question. Sadly this patch is only for newer Fairphone 2’s where we were able to identify a root cause for reboots and fix it.

If your FP2 is rebooting, and has so from the beginning and you tried all tips in the #rebootsguide, then there is nothing left but to contact support and look with them if this still falls under warranty.


Reboot and battery drain
#602

Thank you for the explanation. I own a Fairphone 2 with Ubuntu Touch running. As I experience the same problem of spontaneous rebooting several times per day I would appreciate to know whether the update would have an impact on Ubuntu Touch in case I would reinstall Fairphone OS and after that install Ubuntu Touch on top of it (as this is the usual way to install Ubuntu Touch). Thank you.


#603

Same here, got a new FP2 and in regards to the overall quality I was expecting better than such reboot problems since the beginning. I will try to fix it following your guide and I will post back if I manage to.


#604

I can confirm now with certainty that the source of my random reboots was the Facebook app. It appears to cause increased stress and overheating triggered by unknown address or undefined instruction loops, hence only indirectly connected to 4G or any other activity that uses hardware more intensively.

For info here is my setup:
Fairphone 2 of August 2016
Open FP OS version 18.02.0 with microG version 0.2.4-108-g464d45d, Xposed version 89-sdk23-arm, and GSM location service
Tested after a factory reset and reinstallation of Open FP.

I collected 5 last_kmsg.log files taken with SysLog immediately after random reboots during a 14-hour period. Among those 5 log files I found that facebook.katana appeared as triggering undefined instructions in 3 of them. One was corrupted and can’t be read. One implicated another app but maybe as a result of previous Facebook activity, I’m keeping the other app under observation but for know it doesn’t appear to cause any problem. Uninstalling the Facebook app definitively solves the random reboot problem. It also reduces overheating and improves battery life.

Here a sample of how facebook.katana appears in the crash logs:

facebook.katana (15848): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
facebook.katana (15848): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
facebook.katana (15848): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
facebook.katana (15848): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
facebook.katana (15848): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
facebook.katana (15848): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
Norm_Shared1 (16098): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
Norm_Shared1 (16098): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
Bg_Shared2 (16114): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
Bg_Shared2 (16114): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
Bg_Shared2 (16114): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
Bg_Shared2 (16114): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
audit: audit_lost=21462 audit_rate_limit=20 audit_backlog_limit=64
audit: rate limit exceeded
Bg_Shared2 (16114): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
Bg_Shared2 (16114): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
Bg_Shared2 (16114): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
Bg_Shared2 (16114): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
Bg_Shared2 (16114): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
Bg_Shared2 (16114): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
Bg_Shared2 (16114): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
Bg_Shared2 (16114): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
Bg_Shared2 (16114): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
Bg_Shared3 (16115): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
Bg_Shared3 (16115): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
Bg_Shared3 (16115): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
Bg_Shared3 (16115): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
Bg_Shared3 (16115): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
Bg_Shared3 (16115): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
Bg_Shared3 (16115): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc
Code: fc60 002b 3c5e 002c (defa) 41f0 
BgHandler (16077): undefined instruction: pc=b47b22bc

No errors detected


Has anyone gotten rid of their random reboots?
:pencil2: A little Guide to... Random Reboots
#605

Thanks @Dr_Cool for updating the #rebootsguide. I don’t know how facebook didn’t make it on the guide yet. I just updated your entry a bit to indicate that this is a issue known for quite a long while now.


#606

Thanks for confirming and improving. This info would have helped me a lot had it been on the guide before I started my tests… :disappointed_relieved:


#607

Confirmed that the Aix Weather widget also causes random reboots. Adding this info to the wiki and will try to contact the authors.


#608

I can’t approve that. I’m running Aix Weather widget since over two years now, first under Fairphone OS, now under LineageOS, and don’t have any reboot issue


#609

Before this last FP2 update that Douwe is referring to, my phone was ‘rather’ stable (after removing AVS anti-virus), but not quite. With Google Maps for instance, it rebooted. And almost every day before the update, it tended to do so likewise.

Now after the update, all seems fine again. “Seems”, because, well, if one has experienced those random reboots often, it takes a while before trust is restored completely. But I’m hopeful.

Anyway, thanks for the update!


#610

Afaik the update Douwe mentioned is not out yet. It’s not a regular monthly update, but a separate one as I understand it.


#611

O well… Then my better experience refers to the update I got about a week ago. It says in Build-nummer: “FP2-gms-18.02.0 release-keys”. Smalbandversie “4437.1-FP2-0-07”. Kernel is of Jan 17 2018.
(Actually, I don’t know which what each number says)

Marc


#612

The reboots with Aix Weather follow a clear pattern and always show in the log files as triggered by an “Unknown symbol address c01026b8,” please see an extract below. They happen overnight, probably when Aix updates data, and a second reboot happens following the overnight one, after I type in the SIM card password and it tries to update data. The reboots then stop. Some hardware or software specificity is causing it, can you please compare my setup above with yours and tell me what is different?

Pid: 20891, comm: aix.AixService]
CPU: 0 Tainted: G W O (3.4.0-ga177cec #1)
PC is at 0x729a71b8
LR is at 0x729a128d
pc : [<729a71b8>] lr : [<729a128d>] psr: 400e0030
sp : b14282a0 ip : 00000000 fp : 12d42420
r10: 12c005e0 r9 : ada19c00 r8 : 00000000
r7 : 00000000 r6 : 12cf42a0 r5 : 6fdc2dc8 r4 : 12c02340
r3 : 00000000 r2 : ffffffff r1 : 00000000 r0 : 70739de0
Flags: nZcv IRQs on FIQs on Mode USER_32 ISA Thumb Segment user
Control: 10c5787d Table: 2dd5806a DAC: 00000015
[] (unwind_backtrace+0x0/0x138) from [] (__do_user_fault+0x104/0x150)
[] (__do_user_fault+0x104/0x150) from [] (do_page_fault+0x384/0x410)
[] (do_page_fault+0x384/0x410) from [] (do_DataAbort+0x144/0x244)
unwind: Unknown symbol address c01026b8
unwind: Index not found c01026b8
aix.AixService]: unhandled page fault (11) at 0x00000000, code 0x005
pgd = edd58000
[00000000] *pgd=00000000

Pid: 20891, comm: aix.1]
CPU: 0 Tainted: G W O (3.4.0-ga177cec #1)


#613

Aix Weather author tells me this is the only reboots case ever reported to him, so I wonder what is specific of my setup that is triggering the misbehavior. Phone is perfectly stable without Facebook and Aix Weather.


#614

Setup on my FP2:

  • FP2 from January 2016, new camera modules
  • LineageOS 14.1-20180206-FP2 w/ microG
  • No Xposed framework installed (or other system modifications)

So my first guess would be that Aix somehow conflicts with Xposed framework.


#615

I have a situation where I can reproduce very easily the reboots: connecting the phone to a camera.

New DSLRs have Wifi connections with smartphones. In my case, my camera sets up an AP, the phone connects there, and then you use an app to control the camera.

Once I connect to my camera, my phone reboots in less than 3 minutes. It first complains that the connection does not reach Internet (of course it doesn’t), I tell it not to ask again, wait for it… wait for it… bam reboot.

I tried reproducing the same situation by connecting it to my AP/router, but deny any access from the phone to Internet. For some reason, here the phone does not complain, does not reboot, and even uses 3/4G to access internet.

I’m baffled that I couldn’t reproduce it that way (maybe because some services like KDE connect still work? I only blocked internet, hmm…), but at least I have a reproducible situation.

So, any hints on what to do about it? dmesg and adb lastlog do not show anything relevant/interesting. maybe I should root the phone, install some basic tools like tcpdump, and try to figure out more stuff.

Cheers,

-- Marcos.

#616

Yeah, you need root so you can extract a last_ksmg.log file, this is the one that gives you relevant info about what was happening right before a crash.


#617

Hello,

I have the same problem.

I tried the following.

  • Get 2 new Farphone 2
  • Get 3 new SIM Cards from my provider T-Mobile Germany
  • I do not use any SD Cards in my FP2
  • I have only installed the Apps comes withe the FP2
  • I have installed the latest FP2 Update

Reboots happens 1 to 2 times a day and if I use Google Maps.


#618

You bought 2 new phones because the first one had random reboots?

Since they are new the solution should be simple: Wait for the update that is supposed to fix them. In the next days you should get an automatic notification to update on your phone. More info in Douwe’s post above.