12-12-2019, 05:35 AM
(This post was last modified: 12-12-2019, 10:16 AM by tsago.
Edit Reason: further results
)
Hi pjsf, I click the power button, get prompted for what I want to do, and select reboot (GUI button).
Are you implying that the "reboot" button actually incorrectly does a suspend?
Had help from mrfixit2001 on the chat yesterday.
Hypothesis was that maybe eMMC is bad.
I removed the eMMC module, then prepared an SD-card image of the debian build:
1, burned pinebookpro-debian-mrfixit-191127.img to SD
2, booted up and upgraded with the upgrade script
3, shut down, boot up
4, Restart test => works OK (improvement from tests off eMMC)
5, I still get stuck during bootup if UART is connected and I am getting serial console output to my PC). Getting stuck on:
[ 0.000000] GIC: PPI partition interrupt-partition-0[0] { /cpus/cpu@0[0] /cpus/cpu@1[1] /cpus/cpu@2[2] /cpus/cpu@3[3] }
[ 0.000000] GIC: PPI partition interrupt-partition-1[1] { /cpus/cpu@100[4] /cpus/cpu@101[5] }
6, Shutdown test => works fine
So it looks like there's something wrong with my eMMC module...
Are you implying that the "reboot" button actually incorrectly does a suspend?
Had help from mrfixit2001 on the chat yesterday.
Hypothesis was that maybe eMMC is bad.
I removed the eMMC module, then prepared an SD-card image of the debian build:
1, burned pinebookpro-debian-mrfixit-191127.img to SD
2, booted up and upgraded with the upgrade script
3, shut down, boot up
4, Restart test => works OK (improvement from tests off eMMC)
5, I still get stuck during bootup if UART is connected and I am getting serial console output to my PC). Getting stuck on:
[ 0.000000] GIC: PPI partition interrupt-partition-0[0] { /cpus/cpu@0[0] /cpus/cpu@1[1] /cpus/cpu@2[2] /cpus/cpu@3[3] }
[ 0.000000] GIC: PPI partition interrupt-partition-1[1] { /cpus/cpu@100[4] /cpus/cpu@101[5] }
6, Shutdown test => works fine
So it looks like there's something wrong with my eMMC module...