reboot / crash

[Der Geist der Maschine]

First thing, update the kernel via /usr/bin/mrfixit_update.sh and reboot. That has not helped me, though.

Thank you, I have done this now. 'wl_run_escan' doesn't appear to be happening any longer.

That's because mrfixit commented out the corresponding printk. The root-cause for the printks is still there. I doubt that's a issue. Strictly speaking, I don't know, though.

[james64]

I used to get crashes every 24 hours. Now with MrFixIt's epic v 1.5 update, I get crashes every 1 to 2 hours basically rendering the laptop unusable. 121 postings. That was it. Bye.

I keep monitoring this thread https://forum.pine64.org/showthread.php?tid=8207 to see if someone gets the 5.4 kernel running on Debian and give that a try.

Did you ever solve crashes? 4 times for me today. No crashes the previous two days. Only change today was to install the touchpad and ANSI keyboard updates as per wiki instructions.

[xmixahlx]

for reference: zero crashes for me on debian sid arm64 with tsys kernel. ever.

[james64]

inplace upgrade? or clean install? maybe we can just upgrade kernel only. thanks for sharing eh.

[Der Geist der Maschine]

I used to get crashes every 24 hours. Now with MrFixIt's epic v 1.5 update, I get crashes every 1 to 2 hours basically rendering the laptop unusable. 121 postings. That was it. Bye.

I keep monitoring this thread https://forum.pine64.org/showthread.php?tid=8207 to see if someone gets the 5.4 kernel running on Debian and give that a try.

Did you ever solve crashes? 4 times for me today. No crashes the previous two days. Only change today was to install the touchpad and ANSI keyboard updates as per wiki instructions.

We can't be sure that your crashes have the same root-cause as my crashes.

Manjaro's 5.4 kernel does not crash on my system. I was initially running Manjaro from an SD card without any crashes. In the meantime, I installed Debian 10 + Manjaro's kernel on emmc. There are also no crashes.

Info about Manjaro is here https://forum.pine64.org/showthread.php?tid=8248

Nobody succeeded installing Manjaro's kernel on the default Debian. People here are installing a fresh Debian with debootstrap + Manjaro's kernel. If you are not familiar with this process, it's recommended to use Daniel's installer from this thread https://forum.pine64.org/showthread.php?tid=8487

[xmixahlx]

I don't think anyone attempted tsys kernel with Debian 9, and I don't see why you would do that.

if anything, 4.4 kernel and Debian 10+ makes more sense to attempt proper resume/suspend.

[Baldnerd]

Just adding myself to the stack of users experiencing this issue.

Got my PBP ANSI and booted it for the first time Saturday. Had it hard reboot itself while chatting on Discord with the default (included) Debian OS. So I downloaded the latest release of the Debian Desktop Community Build from @Mrfixit2001's GitHub repository (it is a bit newer than the one listed on the Pinebook Pro wiki) and booted from microSD, and just had it hard reboot itself again after running for about 2.5 hours. This time, all I was doing was running the WiDivine update, which sadly was almost finished after a 1.5 hour download - haha! I had nothing else open or running. Just that single terminal window.

Are there any pointers as to why this seems to be happening? I'd love to be running Debian, and just want to know if there is anything I can do to fix this.

Very happy / excited about the PBP otherwise. Beautiful device! Hopefully this is just a hiccup that can be solved since it could lead to data loss if I was working on something important.

[Update] a couple hours later, it just hard booted itself again. Same thing running: just the WiDivine update, and was almost complete.

Thanks, all.

[xmixahlx]

sounds like a kernel issue to me.

anything useful in syslog regarding the lockups?

[Baldnerd]

Really hard to tell @xmixahlx - the syslog is heavily bloated (!!) though I could search through if I knew specifically what to look for. Unfortunately looking at the log also points to the fact that my system locale was set incorrectly and therefore the log timestamps are invalid. I have fixed my system time and should it happen again, it'll be much easier to find the correct spot in the log.

In the meantime, I tried something: as I mentioned, I had it hard reboot 3 times, the most recent 2 were when running the WiDivine update. So, this final time, I set the CPU frequency to 1.01 GHz static set, to prevent the CPU frequency from changing on the fly as is the default. Having set the CPU frequency, the WiDevine upgrade completed successfully, and the PBP remained stable after the update had completed, with no hard reboot.

I can't confirm in my initial tests that this was the cause & solution, but I know that 2x in a row, the upgrade caused the PBP to reboot, then, having set the CPU frequency manually to a static value, the same update completed without issue. So it could be related.

I will continue to monitor things. Fingers crossed that's all it is, as I'm happy to turn off CPU frequency scaling...

[james64]

I reinstalled Debian 9 and for the past 3 days no issues with crash/reboot.

Both yesterday I used PBP for 5+ hours at a time on and off battery. No issues at all.