bmax121
no symbol: memblock_phys_alloc_try_nid
Currently, there is no immediate solution. You need to troubleshoot it yourself or provide the device to me for further investigation. hello my mobile is android 13 xiaomi Pad 6 kernel : Linux localhost 4.19.157-perf-g85a67ce2994a #1 SMP PREEMPT Fri Jun 30 03:10:45 UTC 2023 aarch64 Toybox
patch ressult :
[+] kernel image_size: 0x03261010 [+] kernel uefi header: false [+] kernel load_offset: 0x00080000 [+] kernel kernel_size: 0x03d44000 [+] kernel page_shift: 12 [+] new kernel image ... [+] linux_banner 1: Linux version 4.19.157-perf-g85a67ce2994a (builder@pangu-build-component-vendor-101509-2chw5-c718x-6mk47) (clang version 10.0.7 for Android NDK, GNU ld (binutils-2.27-bd24d23f) 2.27.0.20170315) #1 SMP PREEMPT Fri Jun 30 03:10:45 UTC 2023 [+] linux_banner offset: 0x1580018 [+] linux_banner 2: Linux version 4.19.157-perf-g85a67ce2994a (builder@pangu-build-component-vendor-101509-2chw5-c718x-6mk47) (clang version 10.0.7 for Android NDK, GNU ld (binutils-2.27-bd24d23f) 2.27.0.20170315) #1 SMP PREEMPT Fri Jun 30 03:10:45 UTC 2023 [+] linux_banner offset: 0x2380038 [+] kernel version major: 4, minor: 19, patch: 157 [+] kallsyms_token_table offset: 0x025d9000 [+] endian: little [+] kallsyms_token_index offset: 0x025d9400 [+] find arm64 relocation kernel_va: 0xffffff8008080000 [+] find arm64 relocation table range: [0x02a72ed8, 0x02d80ea0), count: 0x00020953 [+] apply 0x00020947 relocation entries [+] kallsyms_markers range: [0x025d7f00, 0x025d8fc0), count: 0x00000218 [+] approximate kallsyms_offsets range: [0x023805f0, 0x024064d4) count: 0x000217b9 [+] kallsyms_names offset: 0x02406700 [+] kallsyms_num_syms offset: 0x02406600, value: 0x000217b5 [+] names table linux_banner index: 0x0000e0c5 [+] linux_banner index: 0 [+] kallsyms_offsets offset: 0x02380600 [+] layout kimg: 0x0-0x3261010, kpimg: 0x3262000,0xb1c70, extra: 0x3313c70,0x80, end: 0x3313cf0, start: 0x3d44000 [+] kpimg version: 0 [+] kpimg compile time: [+] kpimg config: android, release [+] tcp_init_sock: type: T, offset: 0x012f0030 [+] map_start: 0x12f0030, max_size: 0x800 [+] kallsyms_lookup_name: type: T, offset: 0x001228d8 [+] printk: type: T, offset: 0x000d71c0 [+] memblock_reserve: type: T, offset: 0x002199f8 [+] memblock_free: type: T, offset: 0x00219960 [+] memblock_mark_nomap: type: T, offset: 0x00219ca0 [?] no symbol: memblock_phys_alloc_try_nid [+] memblock_virt_alloc_try_nid: type: T, offset: 0x029a2120 [+] memblock_alloc_try_nid: type: T, offset: 0x029a1db4 [+] panic: type: T, offset: 0x0003f32c [+] rest_init: type: t, offset: 0x01517718 [+] kernel_init: type: t, offset: 0x015177f8 [?] no symbol: report_cfi_failure [?] no symbol: __cfi_slowpath_diag [?] no symbol: __cfi_slowpath [+] copy_process: type: t, offset: 0x0003c6f0 [+] avc_denied: type: t, offset: 0x0043a7c0 [+] slow_avc_audit: type: T, offset: 0x00439730 [+] input_handle_event: type: t, offset: 0x00a49c08 [+] superkey: matrixhax_hehehehe [+] paging_init: type: T, offset: 0x0298836c [+] patch done: /data/local/tmp/boot/patched-kernel
as you can see some symbols are not found
but i looked at the code in boot and you seems to check if symobl exist or not before using it
but for the memblock_phys_alloc_try_nid you direct using it without checking if it valid or not
you assume it exist in all kernels maybe ?
i am not quit good at kernel developments so i dont know how to solve this
anyway i got this similar symbols :
i hope to get a quick reply so we can solve it
[?] no symbol: memblock_phys_alloc_try_nid
[+] memblock_alloc_try_nid: type: T, offset: 0x029a1db4
They are not the same, please check carefully.
yes i see that is why i am asking here for a sulotion and there other a few missing symbols too i hope i can get a sulotion anyway running this patch will make my mobile stuck at xiaomi logo for ever