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

相关文章

线上Java OOM问题定位与解决方案超详细解析

《线上JavaOOM问题定位与解决方案超详细解析》OOM是JVM抛出的错误,表示内存分配失败,:本文主要介绍线上JavaOOM问题定位与解决方案的相关资料,文中通过代码介绍的非常详细,需要的朋... 目录一、OOM问题核心认知1.1 OOM定义与技术定位1.2 OOM常见类型及技术特征二、OOM问题定位工具

Vue3绑定props默认值问题

《Vue3绑定props默认值问题》使用Vue3的defineProps配合TypeScript的interface定义props类型,并通过withDefaults设置默认值,使组件能安全访问传入的... 目录前言步骤步骤1:使用 defineProps 定义 Props步骤2:设置默认值总结前言使用T

Web服务器-Nginx-高并发问题

《Web服务器-Nginx-高并发问题》Nginx通过事件驱动、I/O多路复用和异步非阻塞技术高效处理高并发,结合动静分离和限流策略,提升性能与稳定性... 目录前言一、架构1. 原生多进程架构2. 事件驱动模型3. IO多路复用4. 异步非阻塞 I/O5. Nginx高并发配置实战二、动静分离1. 职责2

解决升级JDK报错:module java.base does not“opens java.lang.reflect“to unnamed module问题

《解决升级JDK报错:modulejava.basedoesnot“opensjava.lang.reflect“tounnamedmodule问题》SpringBoot启动错误源于Jav... 目录问题描述原因分析解决方案总结问题描述启动sprintboot时报以下错误原因分析编程异js常是由Ja

MySQL 表空却 ibd 文件过大的问题及解决方法

《MySQL表空却ibd文件过大的问题及解决方法》本文给大家介绍MySQL表空却ibd文件过大的问题及解决方法,本文给大家介绍的非常详细,对大家的学习或工作具有一定的参考借鉴价值,需要的朋友参考... 目录一、问题背景:表空却 “吃满” 磁盘的怪事二、问题复现:一步步编程还原异常场景1. 准备测试源表与数据

解决Nginx启动报错Job for nginx.service failed because the control process exited with error code问题

《解决Nginx启动报错Jobfornginx.servicefailedbecausethecontrolprocessexitedwitherrorcode问题》Nginx启... 目录一、报错如下二、解决原因三、解决方式总结一、报错如下Job for nginx.service failed bec

SysMain服务可以关吗? 解决SysMain服务导致的高CPU使用率问题

《SysMain服务可以关吗?解决SysMain服务导致的高CPU使用率问题》SysMain服务是超级预读取,该服务会记录您打开应用程序的模式,并预先将它们加载到内存中以节省时间,但它可能占用大量... 在使用电脑的过程中,CPU使用率居高不下是许多用户都遇到过的问题,其中名为SysMain的服务往往是罪魁

MySQ中出现幻读问题的解决过程

《MySQ中出现幻读问题的解决过程》文章解析MySQLInnoDB通过MVCC与间隙锁机制在可重复读隔离级别下解决幻读,确保事务一致性,同时指出性能影响及乐观锁等替代方案,帮助开发者优化数据库应用... 目录一、幻读的准确定义与核心特征幻读 vs 不可重复读二、mysql隔离级别深度解析各隔离级别的实现差异

C++ vector越界问题的完整解决方案

《C++vector越界问题的完整解决方案》在C++开发中,std::vector作为最常用的动态数组容器,其便捷性与性能优势使其成为处理可变长度数据的首选,然而,数组越界访问始终是威胁程序稳定性的... 目录引言一、vector越界的底层原理与危害1.1 越界访问的本质原因1.2 越界访问的实际危害二、基

Python多线程应用中的卡死问题优化方案指南

《Python多线程应用中的卡死问题优化方案指南》在利用Python语言开发某查询软件时,遇到了点击搜索按钮后软件卡死的问题,本文将简单分析一下出现的原因以及对应的优化方案,希望对大家有所帮助... 目录问题描述优化方案1. 网络请求优化2. 多线程架构优化3. 全局异常处理4. 配置管理优化优化效果1.