arm64平台make menuconfig引起问题丢失CONFIG_XXX

2023-11-01 02:30

本文主要是介绍arm64平台make menuconfig引起问题丢失CONFIG_XXX,希望对大家解决编程问题提供一定的参考价值,需要的开发者们随着小编来一起学习吧!

现象:

  SYNC    include/config/auto.conf.cmd
*
* Restart config...
*
*
* General setup
*
Compile also drivers which will not load (COMPILE_TEST) [N/y/?] n
Local version - append to kernel release (LOCALVERSION) [] 
Automatically append version information to the version string (LOCALVERSION_AUTO) [Y/n/?] y
Build ID Salt (BUILD_SALT) [] 
Default init path (DEFAULT_INIT) [] 
出现问题:系统初始化崩溃 panic 
[    0.000000] ITS queue timeout (64 1)
[    0.000000] ITS cmd its_build_mapc_cmd failed
[    0.000000] ITS queue timeout (128 1)
[    0.000000] ITS cmd its_build_invall_cmd failed
[    0.000000] ITS queue timeout (64 1)
[    0.000000] ITS cmd its_build_mapc_cmd failed
[    0.000000] ITS queue timeout (128 1)
[    0.000000] ITS cmd its_build_invall_cmd failed[    5.190467] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000
[    5.191274] Mem abort info:
[    5.191534]   ESR = 0x86000005
[    5.191818]   EC = 0x21: IABT (current EL), IL = 32 bits
[    5.192306]   SET = 0, FnV = 0
[    5.192589]   EA = 0, S1PTW = 0
[    5.192879] [0000000000000000] user address but active_mm is swapper
[    5.193466] Internal error: Oops: 86000005 [#1] SMP
[    5.193916] Modules linked in:
[    5.194205] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.10.110 #74
[    5.194774] Hardware name: Rockchip RK3588-EVB-KS-T1 LP4 V10 Board (DT)
[    5.195386] pstate: 60000089 (nZCv daIf -PAN -UAO -TCO BTYPE=--)
[    5.195940] pc : 0x0
[    5.196146] lr : enqueue_task+0xac/0xc0
[    5.196500] sp : ffffffc01154bb40
[    5.196807] x29: ffffffc01154bb40 x28: ffffffc1edeaa000 
[    5.197303] x27: ffffff81001f2a00 x26: 0000000000000001 
[    5.197798] x25: ffffffc011429584 x24: ffffffc01127a888 
[    5.198294] x23: 0000000000000001 x22: ffffff81001f2a00 
[    5.198789] x21: 000000000000000a x20: ffffff81001f2a00 
[    5.199283] x19: ffffff81fef172c0 x18: 0000000000000000 
[    5.199779] x17: 000000007bd6fd76 x16: 000000002e197337 
[    5.200274] x15: 000000000000000a x14: 000000000002e6aa 
[    5.200768] x13: 0000000000000006 x12: ffffffffffffffff 
[    5.201262] x11: 000000000000007c x10: 00000000ffffffea 
[    5.201757] x9 : 000000000000000d x8 : ffffffc01154b748 
[    5.202252] x7 : 00000000ffffdfff x6 : ffffffc01154b750 
[    5.202747] x5 : 00000000000affa8 x4 : 0000000000000000 
[    5.203242] x3 : 0000000000000000 x2 : 000000000000000a 
[    5.203737] x1 : ffffff81001f2a00 x0 : ffffff81fef172c0 
[    5.204231] Call trace:
[    5.204459]  0x0
[    5.204633]  do_set_cpus_allowed+0x9c/0xc8
[    5.205014]  cpuset_cpus_allowed_fallback+0x50/0x60
[    5.205465]  select_fallback_rq+0xa4/0x148
[    5.205845]  migrate_tasks+0x184/0x298
[    5.206194]  sched_cpu_dying+0x7c/0x11c
[    5.206550]  cpuhp_invoke_callback+0xb8/0x1a4
[    5.206955]  _cpu_up+0x164/0x19c
[    5.207257]  cpu_up+0xb4/0x120
[    5.207542]  bringup_nonboot_cpus+0x8c/0x90
[    5.207931]  smp_init+0x30/0x78
[    5.208225]  kernel_init_freeable+0x10c/0x274
[    5.208629]  kernel_init+0x14/0x118
[    5.208954]  ret_from_fork+0x10/0x30
解决: 原因有一些必要的配置丢失,内核跑飞.
source /etc/profile,安装交叉编译器的脚本配置的环境变量就可以生效
cp arch/arm64/configs/xxx_defconfig .config 
make ARCH=arm64 menuconfig CROSS_COMPILE=aarch64-none-linux-gnu-  menuconfig
make ARCH=arm64 CROSS_COMPILE=aarch64-none-linux-gnu- clean 
make ARCH=arm64 CROSS_COMPILE=aarch64-none-linux-gnu- menuconfig 
make ARCH=arm64 CROSS_COMPILE=aarch64-none-linux-gnu- uImage 
 1.020600] EFI services will not be available.
[    1.021299] smp: Bringing up secondary CPUs ...
I/TC: Secondary CPU 1 initializing
I/TC: Secondary CPU 1 switching to normal world boot
I/TC: Secondary CPU 2 initializing
I/TC: Secondary CPU 2 switching to normal world boot
I/TC: Secondary CPU 3 initializing
I/TC: Secondary CPU 3 switching to normal world boot
I/TC: Secondary CPU 4 initializing
I/TC: Secondary CPU 4 switching to normal world boot
I/TC: Secondary CPU 5 initializing
I/TC: Secondary CPU 5 switching to normal world boot
I/TC: Secondary CPU 6 initializing
I/TC: Secondary CPU 6 switching to normal world boot
I/TC: Secondary CPU 7 initializing
I/TC: Secondary CPU 7 switching to normal world boot
[    1.022876] Detected VIPT I-cache on CPU1
[    1.022876] Detected VIPT I-cache on CPU1
[    1.022907] GICv3: CPU1: found redistributor 100 region 0:0x00000000fe6a0000
[    1.022925] GICv3: CPU1: using allocated LPI pending table @0x00000001000c0000
[    1.022966] CPU1: Booted secondary processor 0x0000000100 [0x412fd050]
[    1.024155] Detected VIPT I-cache on CPU2
[    1.024183] GICv3: CPU2: found redistributor 200 region 0:0x00000000fe6c0000
[    1.024200] GICv3: CPU2: using allocated LPI pending table @0x00000001000d0000
[    1.024239] CPU2: Booted secondary processor 0x0000000200 [0x412fd050]
[    1.025423] Detected VIPT I-cache on CPU3
[    1.025448] GICv3: CPU3: found redistributor 300 region 0:0x00000000fe6e0000
[    1.025465] GICv3: CPU3: using allocated LPI pending table @0x00000001000e0000
[    1.025500] CPU3: Booted secondary processor 0x0000000300 [0x412fd050]
[    1.026668] CPU features: detected: Spectre-v4
[    1.026671] CPU features: detected: Spectre-BHB
[    1.026673] Detected PIPT I-cache on CPU4
[    1.026688] GICv3: CPU4: found redistributor 400 region 0:0x00000000fe700000
[    1.026697] GICv3: CPU4: using allocated LPI pending table @0x00000001000f0000
[    1.026721] CPU4: Booted secondary processor 0x0000000400 [0x414fd0b0]
[    1.027861] Detected PIPT I-cache on CPU5
[    1.027876] GICv3: CPU5: found redistributor 500 region 0:0x00000000fe720000
[    1.027885] GICv3: CPU5: using allocated LPI pending table @0x0000000100100000
[    1.027909] CPU5: Booted secondary processor 0x0000000500 [0x414fd0b0]
[    1.029051] Detected PIPT I-cache on CPU6
[    1.029066] GICv3: CPU6: found redistributor 600 region 0:0x00000000fe740000
[    1.029075] GICv3: CPU6: using allocated LPI pending table @0x0000000100110000
[    1.029099] CPU6: Booted secondary processor 0x0000000600 [0x414fd0b0]
[    1.030233] Detected PIPT I-cache on CPU7
[    1.030248] GICv3: CPU7: found redistributor 700 region 0:0x00000000fe760000
[    1.030258] GICv3: CPU7: using allocated LPI pending table @0x0000000100120000
[    1.030281] CPU7: Booted secondary processor 0x0000000700 [0x414fd0b0]
[    1.030342] smp: Brought up 1 node, 8 CPUs

这篇关于arm64平台make menuconfig引起问题丢失CONFIG_XXX的文章就介绍到这儿,希望我们推荐的文章对编程师们有所帮助!



http://www.chinasem.cn/article/319840

相关文章

mybatis和mybatis-plus设置值为null不起作用问题及解决

《mybatis和mybatis-plus设置值为null不起作用问题及解决》Mybatis-Plus的FieldStrategy主要用于控制新增、更新和查询时对空值的处理策略,通过配置不同的策略类型... 目录MyBATis-plusFieldStrategy作用FieldStrategy类型每种策略的作

linux下多个硬盘划分到同一挂载点问题

《linux下多个硬盘划分到同一挂载点问题》在Linux系统中,将多个硬盘划分到同一挂载点需要通过逻辑卷管理(LVM)来实现,首先,需要将物理存储设备(如硬盘分区)创建为物理卷,然后,将这些物理卷组成... 目录linux下多个硬盘划分到同一挂载点需要明确的几个概念硬盘插上默认的是非lvm总结Linux下多

Python Jupyter Notebook导包报错问题及解决

《PythonJupyterNotebook导包报错问题及解决》在conda环境中安装包后,JupyterNotebook导入时出现ImportError,可能是由于包版本不对应或版本太高,解决方... 目录问题解决方法重新安装Jupyter NoteBook 更改Kernel总结问题在conda上安装了

pip install jupyterlab失败的原因问题及探索

《pipinstalljupyterlab失败的原因问题及探索》在学习Yolo模型时,尝试安装JupyterLab但遇到错误,错误提示缺少Rust和Cargo编译环境,因为pywinpty包需要它... 目录背景问题解决方案总结背景最近在学习Yolo模型,然后其中要下载jupyter(有点LSVmu像一个

解决jupyterLab打开后出现Config option `template_path`not recognized by `ExporterCollapsibleHeadings`问题

《解决jupyterLab打开后出现Configoption`template_path`notrecognizedby`ExporterCollapsibleHeadings`问题》在Ju... 目录jupyterLab打开后出现“templandroidate_path”相关问题这是 tensorflo

如何解决Pycharm编辑内容时有光标的问题

《如何解决Pycharm编辑内容时有光标的问题》文章介绍了如何在PyCharm中配置VimEmulator插件,包括检查插件是否已安装、下载插件以及安装IdeaVim插件的步骤... 目录Pycharm编辑内容时有光标1.如果Vim Emulator前面有对勾2.www.chinasem.cn如果tools工

最长公共子序列问题的深度分析与Java实现方式

《最长公共子序列问题的深度分析与Java实现方式》本文详细介绍了最长公共子序列(LCS)问题,包括其概念、暴力解法、动态规划解法,并提供了Java代码实现,暴力解法虽然简单,但在大数据处理中效率较低,... 目录最长公共子序列问题概述问题理解与示例分析暴力解法思路与示例代码动态规划解法DP 表的构建与意义动

Java多线程父线程向子线程传值问题及解决

《Java多线程父线程向子线程传值问题及解决》文章总结了5种解决父子之间数据传递困扰的解决方案,包括ThreadLocal+TaskDecorator、UserUtils、CustomTaskDeco... 目录1 背景2 ThreadLocal+TaskDecorator3 RequestContextH

关于Spring @Bean 相同加载顺序不同结果不同的问题记录

《关于Spring@Bean相同加载顺序不同结果不同的问题记录》本文主要探讨了在Spring5.1.3.RELEASE版本下,当有两个全注解类定义相同类型的Bean时,由于加载顺序不同,最终生成的... 目录问题说明测试输出1测试输出2@Bean注解的BeanDefiChina编程nition加入时机总结问题说明

关于最长递增子序列问题概述

《关于最长递增子序列问题概述》本文详细介绍了最长递增子序列问题的定义及两种优化解法:贪心+二分查找和动态规划+状态压缩,贪心+二分查找时间复杂度为O(nlogn),通过维护一个有序的“尾巴”数组来高效... 一、最长递增子序列问题概述1. 问题定义给定一个整数序列,例如 nums = [10, 9, 2