Apparently danielt's Debian installer is now mainstream enough it doesn't need it's own dedicated thread!
I'm trying to use this on my brand new PBP, but it kernel panics on startup on boot. I haven't modified the installation at all (yet).
The crash happens at T+13s, well into multiuser startup, and I've pasted the relevant bits blow (does this forum have an attach button? I can't find one). The reference to gpio-key-power looks suspicious.
The kernel version the installer used is linux-image-pinebookpro-arm64 (5.7.19-30-geadcd756eb47-1). Is this new, by any chance? Any ideas of workarounds?
Code: [ 11.094664] raid6: neonx2 gen() 2396 MB/s
[ 11.264662] raid6: neonx2 xor() 1654 MB/s
[ 11.434664] raid6: neonx1 gen() 2065 MB/s
[ 11.456511] input: gpio-key-power as /devices/platform/gpio-key-power/input/input9
[ 11.456641] Unable to handle kernel write to read-only memory at virtual address ffff000002df9000
[ 11.462979] Mem abort info:
[ 11.463231] ESR = 0x9600004e
[ 11.463507] EC = 0x25: DABT (current EL), IL = 32 bits
[ 11.463975] SET = 0, FnV = 0
[ 11.464247] EA = 0, S1PTW = 0
[ 11.464527] Data abort info:
[ 11.464784] ISV = 0, ISS = 0x0000004e
[ 11.465124] CM = 0, WnR = 1
[ 11.465393] swapper pgtable: 4k pages, 48-bit VAs, pgdp=00000000033d0000
[ 11.465981] [ffff000002df9000] pgd=00000000f7ff8003, pud=00000000f7ff7003, pmd=0060000002c00791
[ 11.466751] Internal error: Oops: 9600004e [#1] PREEMPT SMP
[ 11.467242] Modules linked in: btsdio hci_uart brcmfmac btqca btbcm
btintel rockchip_rga gpio_keys(+) raid6_pq(+) panfrost videobuf2_dma_sg
bluetooth hid_multitouch(+) dw_wdt ecdh_generic ecc cw2015_battery
snd_soc_hdmi_codec configfs dm_crypt gpu_sched nf_defrag_ipv6 pwm_fan
cfg80211 rfkill brcmutil nvme nvme_core snd_soc_simple_amplifier
snd_soc_rockchip_i2s snd_soc_rockchip_pcm rockchip_thermal rockchipdrm
analogix_dp dw_hdmi snd_soc_es8316 panel_simple cec dw_mipi_dsi
drm_kms_helper syscopyarea rockchip_saradc sysfillrect sysimgblt
fb_sys_fops uvcvideo drm pwm_bl snd_soc_simple_card
snd_soc_simple_card_utils drm_panel_orientation_quirks
[ 11.472245] CPU: 4 PID: 0 Comm: swapper/4 Not tainted 5.7.0-2-pinebookpro-arm64 #1
[ 11.472909] Hardware name: Pine64 Pinebook Pro (DT)
[ 11.473342] pstate: 000001c5 (nzcv dAIF -PAN -UAO)
[ 11.473776] pc : __memcpy+0x48/0x180
(06-03-2021, 03:59 AM)hjalfi Wrote: Apparently danielt's Debian installer is now mainstream enough it doesn't need it's own dedicated thread!
I'm trying to use this on my brand new PBP, but it kernel panics on startup on boot. I haven't modified the installation at all (yet).
The crash happens at T+13s, well into multiuser startup, and I've pasted the relevant bits blow (does this forum have an attach button? I can't find one). The reference to gpio-key-power looks suspicious.
The kernel version the installer used is linux-image-pinebookpro-arm64 (5.7.19-30-geadcd756eb47-1). Is this new, by any chance? Any ideas of workarounds?
Code: [ 11.094664] raid6: neonx2 gen() 2396 MB/s
[ 11.264662] raid6: neonx2 xor() 1654 MB/s
[ 11.434664] raid6: neonx1 gen() 2065 MB/s
[ 11.456511] input: gpio-key-power as /devices/platform/gpio-key-power/input/input9
[ 11.456641] Unable to handle kernel write to read-only memory at virtual address ffff000002df9000
[ 11.462979] Mem abort info:
[ 11.463231] ESR = 0x9600004e
[ 11.463507] EC = 0x25: DABT (current EL), IL = 32 bits
[ 11.463975] SET = 0, FnV = 0
[ 11.464247] EA = 0, S1PTW = 0
[ 11.464527] Data abort info:
[ 11.464784] ISV = 0, ISS = 0x0000004e
[ 11.465124] CM = 0, WnR = 1
[ 11.465393] swapper pgtable: 4k pages, 48-bit VAs, pgdp=00000000033d0000
[ 11.465981] [ffff000002df9000] pgd=00000000f7ff8003, pud=00000000f7ff7003, pmd=0060000002c00791
[ 11.466751] Internal error: Oops: 9600004e [#1] PREEMPT SMP
[ 11.467242] Modules linked in: btsdio hci_uart brcmfmac btqca btbcm
btintel rockchip_rga gpio_keys(+) raid6_pq(+) panfrost videobuf2_dma_sg
bluetooth hid_multitouch(+) dw_wdt ecdh_generic ecc cw2015_battery
snd_soc_hdmi_codec configfs dm_crypt gpu_sched nf_defrag_ipv6 pwm_fan
cfg80211 rfkill brcmutil nvme nvme_core snd_soc_simple_amplifier
snd_soc_rockchip_i2s snd_soc_rockchip_pcm rockchip_thermal rockchipdrm
analogix_dp dw_hdmi snd_soc_es8316 panel_simple cec dw_mipi_dsi
drm_kms_helper syscopyarea rockchip_saradc sysfillrect sysimgblt
fb_sys_fops uvcvideo drm pwm_bl snd_soc_simple_card
snd_soc_simple_card_utils drm_panel_orientation_quirks
[ 11.472245] CPU: 4 PID: 0 Comm: swapper/4 Not tainted 5.7.0-2-pinebookpro-arm64 #1
[ 11.472909] Hardware name: Pine64 Pinebook Pro (DT)
[ 11.473342] pstate: 000001c5 (nzcv dAIF -PAN -UAO)
[ 11.473776] pc : __memcpy+0x48/0x180
Try installing the latest kernel from Unstable/Sid, maybe? That said, FWIW I haven't had any issues with original Danielt's kernel.
This message was created with 100% recycled electrons
(Nearly) same here
Brand new PBP
it gets to ~ 9sec and then just enters red/green blinking
last line of the output changes from boot to boot
I cannot find any clue in the output.
I still have no idea what happened, but I was able to install Armbian fine and am now using that (although I don't have accelerated graphics yet, probably because I'm still on buster rather than bullseye --- I can't find an Armbian bullseye build).
06-05-2021, 10:07 PM
(This post was last modified: 06-06-2021, 02:45 AM by sepp.)
I was on Armbian (Armbian Focal 5.10.16) too though graphics performance is an issue. Installe nightly Armbian_21.08.0-trunk.31_Pinebook-pro_hirsute_edge_5.12.6_gnome_desktop. Graphics performance good - no issues so far- I stick with it till bullseye gets released
I wonder if you all would get the same result if you did a minimal Debian install with no desktop environment. Today, I posted a video on my experience. Perhaps it could give some ideas.
(06-06-2021, 08:56 PM)jbrock Wrote: I wonder if you all would get the same result if you did a minimal Debian install with no desktop environment. Today, I posted a video on my experience. Perhaps it could give some ideas. tried this too - same result red/gren.
Cosnsole output (I do not know how to capture
that) stops at ~7s after bringing up networking ok and some kernel messages about bluetooth but nothing why it just stops (Had to modify the xtlinux.conf (remove quiet add single)
06-07-2021, 07:49 PM
(This post was last modified: 06-07-2021, 07:50 PM by jbrock.)
This is so perplexing to me.
Have you all tried this image? https://d-i.debian.org/daily-images/arm6...ard-images
I think the included kernel is ready / almost fully ready.
(06-07-2021, 07:49 PM)jbrock Wrote: This is so perplexing to me.
Have you all tried this image? https://d-i.debian.org/daily-images/arm6...ard-images
I think the included kernel is ready / almost fully ready. I actually prepared one today and tried booting it, just for the heck of it - I'm perfectly happy with the system that's already installed on my machine - but the thing came up with black screen :-( I'm not sure what is the exact reason - whether the kernel hasn't yet been updated in the SD card image or the u-boot version in it has some issue.
This message was created with 100% recycled electrons
06-22-2021, 08:35 AM
(This post was last modified: 06-22-2021, 09:05 AM by sepp.)
Finally with the serial console I get the Kernel Panic
Maybe someone can make sense of this:
Code: U-Boot TPL 2020.10-armbian (May 12 2021 - 12:08:59)
Channel 0: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
Channel 1: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
256B stride
lpddr4_set_rate: change freq to 400000000 mhz 0, 1
lpddr4_set_rate: change freq to 800000000 mhz 1, 0
Trying to boot from BOOTROM
Returning to boot ROM...
U-Boot SPL 2020.10-armbian (May 12 2021 - 12:08:59 +0000)
Trying to boot from MMC2
NOTICE: BL31: v2.2(release):a04808c-dirty
NOTICE: BL31: Built : 12:08:50, May 12 2021
U-Boot 2020.10-armbian (May 12 2021 - 12:08:59 +0000)
SoC: Rockchip rk3399
Reset cause: POR
Model: Pine64 Pinebook Pro
DRAM: 3.9 GiB
PMIC: RK808
MMC: mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0
Loading Environment from SPIFlash... Invalid bus 0 (err=-19)
*** Warning - spi_flash_probe_bus_cs() failed, using default environment
In: serial
Out: serial
Err: serial
Model: Pine64 Pinebook Pro
Net: No ethernet found.
starting USB...
Bus usb@fe380000: failed to get usb phy
Port not available.
Bus usb@fe3a0000: failed to get usb phy
Port not available.
Bus usb@fe3c0000: failed to get usb phy
Port not available.
Bus usb@fe3e0000: failed to get usb phy
Port not available.
Bus dwc3: Failed to get PHY0 for dwc3
Port not available.
Bus dwc3: Failed to get PHY0 for dwc3
Port not available.
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:4...
Scanning mmc 1:5...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
945 bytes read in 5 ms (184.6 KiB/s)
U-Boot menu
1: Debian GNU/Linux 11 (bullseye) 5.7.0-2-pinebookpro-arm64
2: Debian GNU/Linux 11 (bullseye) 5.7.0-2-pinebookpro-arm64 (rescue target)
Enter choice: 1: Debian GNU/Linux 11 (bullseye) 5.7.0-2-pinebookpro-arm64
Retrieving file: /initrd.img-5.7.0-2-pinebookpro-arm64
6164004 bytes read in 651 ms (9 MiB/s)
Retrieving file: /vmlinuz-5.7.0-2-pinebookpro-arm64
22477312 bytes read in 2360 ms (9.1 MiB/s)
append: root=PARTLABEL=mmcblk1-RootFS console=ttyS2,1500000n8 console=tty0 ro quiet splash plymouth.ignore-serial-consoles maxcpus=M
Retrieving file: /rk3399-pinebook-pro.dtb
60731 bytes read in 11 ms (5.3 MiB/s)
## Flattened Device Tree blob at 01f00000
Booting using the fdt blob at 0x1f00000
Loading Ramdisk to f493f000, end f4f1fe24 ... OK
Loading Device Tree to 00000000f492d000, end 00000000f493ed3a ... OK
Starting kernel ...
ERROR: rockchip_plat_sip_handler: unhandled SMC (0x82000003)
ERROR: rockchip_plat_sip_handler: unhandled SMC (0x82000003)
ERROR: rockchip_plat_sip_handler: unhandled SMC (0x82000003)
ERROR: rockchip_plat_sip_handler: unhandled SMC (0x82000003)
ERROR: rockchip_plat_sip_handler: unhandled SMC (0x82000003)
ERROR: rockchip_plat_sip_handler: unhandled SMC (0x82000003)
ERROR: rockchip_plat_sip_handler: unhandled SMC (0x82000003)
[ 1.164325] debugfs: File ':interrupt-controller@fee00000' in directory 'domains' already present!
[ 1.164371] debugfs: File ':interrupt-controller@fee00000' in directory 'domains' already present!
[ 1.164402] debugfs: File ':interrupt-controller@fee00000' in directory 'domains' already present!
[ 1.164432] debugfs: File ':interrupt-controller@fee00000' in directory 'domains' already present!
[ 1.164461] debugfs: File ':interrupt-controller@fee00000' in directory 'domains' already present!
[ 1.164491] debugfs: File ':interrupt-controller@fee00000' in directory 'domains' already present!
[ 1.164521] debugfs: File ':interrupt-controller@fee00000' in directory 'domains' already present!
[ 1.164550] debugfs: File ':interrupt-controller@fee00000' in directory 'domains' already present!
[ 1.164580] debugfs: File ':interrupt-controller@fee00000' in directory 'domains' already present!
[ 1.164609] debugfs: File ':interrupt-controller@fee00000' in directory 'domains' already present!
[ 1.164639] debugfs: File ':interrupt-controller@fee00000' in directory 'domains' already present!
[ 1.164668] debugfs: File ':interrupt-controller@fee00000' in directory 'domains' already present!
[ 1.164761] debugfs: File ':interrupt-controller@fee00000' in directory 'domains' already present!
[ 1.164797] debugfs: File ':interrupt-controller@fee00000' in directory 'domains' already present!
[ 1.164831] debugfs: File ':interrupt-controller@fee00000' in directory 'domains' already present!
[ 1.556066] OF: graph: no port node found in /i2c@ff3d0000/fusb30x@22
[ 2.697667] rockchip-dp ff970000.edp: no DP phy configured
[ 7.111350] Internal error: Oops: 9600004e [#1] PREEMPT SMP
[ 7.111845] Modules linked in: hci_uart btqca btbcm gpio_keys(+) panfrost btintel btsdio bluetooth dw_wdt rockchip_rga videobuf2o
[ 7.116762] CPU: 4 PID: 0 Comm: swapper/4 Not tainted 5.7.0-2-pinebookpro-arm64 #1
[ 7.117426] Hardware name: Pine64 Pinebook Pro (DT)
[ 7.117862] pstate: 000001c5 (nzcv dAIF -PAN -UAO)
[ 7.118299] pc : __memcpy+0x48/0x180
[ 7.118627] lr : install_bp_hardening_cb+0x174/0x1c4
[ 7.119065] sp : ffff800011ec3ec0
[ 7.119362] x29: ffff800011ec3ec0 x28: ffff8000114d9ac0
[ 7.119834] x27: ffff8000114ae008 x26: ffff000002df9000
[ 7.120307] x25: 0000000000000001 x24: 0000000000000024
[ 7.120781] x23: ffff8000115f4510 x22: ffff000002df9800
[ 7.121254] x21: ffff8000100dbba8 x20: ffff8000100937c0
[ 7.121727] x19: ffff000002df9080 x18: 0000000000000000
[ 7.122200] x17: 0000000000000000 x16: 0000000000000000
[ 7.122673] x15: 0000000000000000 x14: 0000000000000000
[ 7.123144] x13: 0000000000000000 x12: 0000000000000000
[ 7.123614] x11: 0000000000000000 x10: 00000034b5503510
[ 7.124084] x9 : 0000000000000000 x8 : ffff800010dfb200
[ 7.124556] x7 : 00000000410fd080 x6 : ffff000002df9000
[ 7.125025] x5 : 0000000000000000 x4 : 0000000000000008
[ 7.125494] x3 : d10083ffd503221f x2 : 000000000000001c
[ 7.125964] x1 : ffff8000100dbbb0 x0 : ffff000002df9000
[ 7.126436] Call trace:
[ 7.126663] __memcpy+0x48/0x180
[ 7.126955] detect_harden_bp_fw+0x8c/0xfc
[ 7.127324] check_branch_predictor+0xbc/0x170
[ 7.127721] verify_local_cpu_caps+0x88/0x120
[ 7.128113] verify_local_cpu_capabilities+0x14/0xb4
[ 7.128558] check_local_cpu_capabilities+0x1c/0x34
[ 7.129006] secondary_start_kernel+0x6c/0x104
[ 7.129018] Code: b8404423 b80044c3 36180064 f8408423 (f80084c3)
[ 7.129035] ---[ end trace 78b0ecb9725b4adf ]---
[ 7.130455] Kernel panic - not syncing: Attempted to kill the idle task!
[ 7.130464] SMP: stopping secondary CPUs
[ 7.130474] Kernel Offset: disabled
[ 7.130480] CPU features: 0x090002,2000600c
[ 7.130483] Memory Limit: none
[ 7.132373] ---[ end Kernel panic - not syncing: Attempted to kill the idle task! ]---
(06-07-2021, 11:28 PM)moonwalkers Wrote: (06-07-2021, 07:49 PM)jbrock Wrote: This is so perplexing to me.
Have you all tried this image? https://d-i.debian.org/daily-images/arm6...ard-images
I think the included kernel is ready / almost fully ready. I actually prepared one today and tried booting it, just for the heck of it - I'm perfectly happy with the system that's already installed on my machine - but the thing came up with black screen :-( I'm not sure what is the exact reason - whether the kernel hasn't yet been updated in the SD card image or the u-boot version in it has some issue.
This boots too but you need a serial console to configure (and an usbnet compatible USB2Ether Interface)
|
