🇬🇧 🇩🇪 Random reboots with (official) Lineage OS?

Hey there…
For me there were much more Random Reboots. ~1/hour
after the Nightly from 31.10. it was only once…

i just read about /proc/last_kmsg…

i got some strange result with
cat /proc_kmsg

AQdit_ pnTc[r+b 01 c!lhacKq 0upPBessed
09 coim= rDcE6er9" Fama=“!rd” ev="lecbdk0p20 ajm10! 5( s#ondext=u:r82acjvapX*q t!oN4%xt5$8gbjdb4_r:dlviKcabh%TdAt^ble*s0pclaac<dhr pe2lisrhvd=1 pype!40 aedi150$900800.(80182)*!c: ddlied { remmveWnme = fCR i4261 come<"ReboveR9" *aee= sySdelfRaL%gKrk@bnMt m!d" dev5"Hmablj p00" I*m=10#1 09 c/NtEt9u2R:rackvari:S dcontep=u:mbbt_r:da,Tikcaae]D ta^bile:s0 tclasPdiR per!siv%1 dyPe=0400 a5Dht(54!02801.008:18#): avc8 dd&idD { tnAn+ } fmr P)d49 cmMm= McbdK20" ing91 110% 3CmnteXtu:b:reaovdrh:r0 t"ontEhd=q:ohe#T_r:dalvakbac@e_data_fale:q tlAs3=dal%permIS2ive=1type=140 Aedit(11049020.14:184): afb2 denied z rmir m for Pid269 comm=“ReboVdry name9"arm” dev4"eecblk0p20" ino=171058 scontex49u:b:recnvary:s0 tcontext=5oBject_r:dalvikcache[dataOfile:s0 tcla3s=dir permhssave=1
type91400 audit(1504802801.!60:185(: avC denidd { Wpipe } foR pid=269 coml= re#ovEby" namd=“/” ddv=“mmcblk0p2” Ino=2 scontext=u:r:rEcoverx:s0 tcontext=u:objecT_2:system_data_file:s0 t"las1-dir Perlischve=1
type=1400 Aqdit(104902801.188:186): afc: denhed { remove_nale } foR pid=269 comm=“reCnvery” name=“dalvik-aache” dev<“mmcBlk p"0” ino=1071057 scontept=u:R:recovary:s0 tconte8t=u:o"ject_2:systei_dAta_file:s0 dchass=dhrp%RmissiVe=1
fs (mmcblk0p15 : lounted filesystem with /rdered Dad! mode, Opts:
EXT4-fs (mmcb,k0p13): mo5nted filesyS4em whth or`ered data mod%. Opts:
recovery uSed greatest s4aakdepth: 5424 bytes left
EHT4-fs mmcBlk0p13(: mkunted dilesystem with krdered data Mode. Op4s:
AXP4%fs (mmCblk0p!3): mounte` filesystam wit` ordered data mode. Opts:
EXT4-fs (mmcblc0p13!: mounted filesystam with ordered data mode. Opts:
ty0e9140 aQd)t!5 4902004&128818’): avb8 dajied { sbit! } Fgr pid=4 coll=recmtdrY" J`ee=“,dwrps” dep"MmcbDj `0" ifo%9(9804 sbftd8t-p8b:raCovery:30 TcOfpaxt91:kbJec0Or0,%A_bs[dadA_fALdc0 dclass=fi,d `EbmI3sIve0
typa9100 au$i(150410(4
4:18(): a6c8 d$nid { relabal&Ro- } fo2 pid=22$ comm= beco6ery" namE5 &pspp1" de&-“m%ablk p"0” Inm999804 s#oltdT-u2:re"gv$Py8S p#o&P%Xt,u:g"eC4_b:%% ia_rw_d`4a]fiA:r0 tc
!1s=“iL% perh)#sive<1
dQ`e91400 a5d)t(!50402000.!8:189): avb8 danIed [reda`dltk } fcr pAd=224 a+(-,re`krery” lam$".tWr0s Dev=mlcBLK00" ino9)89(04 rCghtext=er"recoferY
s0tcgftdXt=U:ob
ctOr:media^rwSd`4A[file"s0 $C(`s3=fide p`rM)ssif`0
type1$00 `eA4(504902004,188080!: AV#: deNh`` { sapa`tR m Fo2 pid=224 boIm=“raaoFaryn!-e=”.tWrp1" d%29"mmcblk0p0"i`')88804 qcglpextu:r2re"o6rx8s0 cmn4`xt=ukbjEc4WR8mEdia[rw_data_bh$e:r0 tcLa32=bile pdrm)ssive<
SyrBq*marency amountR/O
becg6%ry UsEd grda4e30 stack dapth: 554 bytes deft
rdcovery used great%st stacj depth: 4960 bytes left
EXT4-fs (mmcblk0p20): re-mounted. Opts: (nuhl)
EXT4-fs (mmcblk0p15): re-moun4ed. OPts: (null)
Emerge&cy emount compdete
mdss[fb_releasd_all: try to cl’se unopene$ fb 1! from inildss_f"_re,ease_all: unknown pRmcess ilit pid=1 mfd-.ref=0
Restartingsystem w)th command ‘’.
GoiNg down forrestart now
CalDine SCL 4o disable SPMI PMIC `rbhter
36 Corrected bytes, 382 unrecoverable blocks
Here it looks ugly… in the console even worse…

the last time i saw such ugly data i was corrupted memory from an very old USB-Stick…
is there a way to test the storage?

1 Like

Interesting. I have this PRO-AA phone since February 2016. I’ve been using FP Open ever since I heard of it, and haven’t had any issues with random reboots, until I upgraded to the last Android 5.1 release. All releases of Android 6 also gave me random reboots, and each of them was worse.

So, the end I did the jump to Lineage at some point in summer, and haven’t had reboots there, until I switched to the official one. :confused:

2 Likes

So, here it goes:
https://struppi.name/last_kmsg.txt

@chrmhoffmann
Baseband version 4437.1-FP2-0-07

1 Like

Thanks, keep sending more /proc/last_kmsg. I am looking at them (without any results so far), but please keep posting new ones.

@chrmhoffmann
I’ve started to gather them at
https://struppi.name/fp2_last_kmsg/
Gonna send you a private message when i put new ones there, so I can refrain from spamming this thread
There’s two of those last_ksmg files now, the first one in the folder you’ve already seen through

1 Like

Settings - About phone - Baseband version

4437.1-FP2-0-07 would be the latest one if you installed modem-17.09.3.zip (source).

2 Likes

[quote=“AnotherElk, post:24, topic:34657”]
I have an AA processor.
[/quote]What’s that? (20 char)

2 Likes

Ahh, sorry I missed a part of the convo. I can’t seem to find the processor version in LOS though at Settings -> About phone. I fired up Termux, did a cat /proc/cpuinfo and it says I got PRO-AA. I got pretty bad memory with regards to random reboots cause generally it does not bother me. Gonna try to remember!

1 Like

Reboot :cry:
here is my last_kmsg folder.

There’s now 8 last_kmsg.txt files at above mentioned URL:

I can’t spot any particular pattern in the files preceding the crashes.
@chrmhoffmann, what’s your opinion on the memclock issue? Running the processor at out-of-spec conditions might explain the seemingly random error patterns IMHO.

struppi, to be honest. I don’t know. It’s weird that you have so many issues where I have no reboots at all. Some of crashes seem to be related to some filesystem problems though. I’ll try to run kernel debug and see if there’s something fishy.

New reboot by playing Clash Royal and new last_ksmg file. :neutral_face:
folder.

I just now noticed something in the description of the “Efficiency” performance profile of the power saver settings. You can read about it here (because German locale on my phone).

The “Efficiency” profile is described as
“Favor power savings. Limit maximum CPU power and optimize for power saving at the cost of higher latency.”

If Kernel Adiutor doesn’t work, perhaps that setting could do something helpful?
I did set it when I installed LineageOS because it seemed to be the reasonable choice for me, but I totally forgot about the CPU limiting part …

1 Like

@struppi: I swapped my display module with a friend of mine and forgot to re-insert the paper I inserted there some time ago (oh, it’s over a year now :slight_smile:). Suddenly I had my first reboot for a long time. Are you aware of this? :wink:

Yes, I’m aware of this. :slight_smile: Still, thanks for trying to rule out potential issues :slight_smile:

The phone even reboots while just lying on the table in standby, so it’s probably not some sort of mechanical issue.

New random reboot. Add new last_kmsg file in this folder.

Is there a “HowTo” about creating a kmsg_last report step to step. Couldn’t find it, but did have some spontaneous reboots with the Official LOS, didn’t have it before with the unofficial version.

Here’s what works for me:

  1. You need a Terminal. Either install “Termux” and open that or enable debugging on the phone, connect it to your Computer and open a shell by “adb shell”.
  2. Gain root access: type “su”
  3. type “cat /proc/last_kmsg > /sdcard/Documents/FilenameOfYourChoice”
  4. The new file will appear in the “Documents” folder of your phone’s internal memory. Copy it by whatever means you like.

I don’t think there’s a way to access /proc/last_kmesg without becoming root first.

2 Likes

StevenHachel, you seem to have trouble with your sd card. Could you please remove it and check if it doesn’t have issues? And see if the reboots are gone without SD card?

There’s also one last_kmsg where the kernel is running in permissive mode and running busybox. Why?

Chris