Sign in
Sign up
Explore
Enterprise
Education
Search
Help
Terms of use
About Us
Explore
Enterprise
Education
Gitee Premium
Gitee AI
AI teammates
Sign in
Sign up
Fetch the repository succeeded.
description of repo status
Open Source
>
OpenHarmony
>
HarmonyOS Drivers
&&
Donate
Please sign in before you donate.
Cancel
Sign in
Scan WeChat QR to Pay
Cancel
Complete
Prompt
Switch to Alipay.
OK
Cancel
Watch
Unwatch
Watching
Releases Only
Ignoring
23
Star
22
Fork
299
OpenHarmony
/
kernel_linux_patches
Closed
Code
Issues
8
Pull Requests
4
Wiki
Insights
Pipelines
Service
JavaDoc
PHPDoc
Quality Analysis
Jenkins for Gitee
Tencent CloudBase
Tencent Cloud Serverless
悬镜安全
Aliyun SAE
Codeblitz
SBOM
DevLens
Don’t show this again
Update failed. Please try again later!
Remove this flag
Content Risk Flag
This task is identified by
as the content contains sensitive information such as code security bugs, privacy leaks, etc., so it is only accessible to contributors of this repository.
[Bug]: linux-6.6内核启动阶段崩溃
Done
#IAWI1C
liangkz
Opened this issue
2024-10-12 11:17
### 发生了什么问题？ DAYU200 平台升级OpenHarmony v5.0.0（Linux-6.6内核）系统，内核启动阶段发生如下异常： > [ 2.359080] rockchip-vop2 fe040000.vop: [drm:vop2_bind] vp0 assign plane mask: 0x2a, primary plane phy id: 5 [ 2.359110] rockchip-vop2 fe040000.vop: [drm:vop2_bind] vp1 assign plane mask: 0x15, primary plane phy id: 4 [ 2.359124] rockchip-vop2 fe040000.vop: [drm:vop2_bind] vp2 assign plane mask: 0x0, primary plane phy id: -1 [ 2.359205] ------------[ cut here ]------------ [ 2.359214] Failed to attach object property (type: 0xeeeeeeee). Please increase DRM_OBJECT_MAX_PROPERTY[24] by 1 for each time you see this message on the same object type. [ 2.359247] WARNING: CPU: 0 PID: 1 at drivers/gpu/drm/drm_mode_object.c:254 drm_object_attach_property+0x7c/0xc0 [ 2.359266] Modules linked in: [ 2.359277] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.6.22 #1 [ 2.359287] Hardware name: rockchip,rk3568-toybrick-dev-linux-x0 (DT) [ 2.359296] pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 2.359306] pc : drm_object_attach_property+0x7c/0xc0 [ 2.359316] lr : drm_object_attach_property+0x7c/0xc0 [ 2.359326] sp : ffffffc08239a680 [ 2.359333] x29: ffffffc08239a680 x28: ffffff8005e4068c x27: ffffff8005e40080 [ 2.359348] x26: 0000000000003568 x25: ffffffc081b156f0 x24: ffffff8002f91c80 [ 2.359362] x23: ffffff8005e44b23 x22: 0000000000001000 x21: ffffff8005e452d8 [ 2.359375] x20: ffffff8005e40080 x19: ffffff8005e45250 x18: 000000000000002a [ 2.359389] x17: 0000000000000000 x16: 0000000000000001 x15: ffffffc081457f5c [ 2.359402] x14: 0 6.6.22 #1 [ 2.359946] Hardware name: rockchip,rk3568-toybrick-dev-linux-x0 (DT) [ 2.359953] pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 2.359963] pc : drm_object_attach_property+0x7c/0xc0 [ 2.359975] lr : drm_object_attach_property+0x7c/0xc0 [ 2.359985] sp : ffffffc08239a680 [ 2.359992] x29: ffffffc08239a680 x28: ffffff8005e4068c x27: ffffff8005e40080 [ 2.360006] x26: 0000000000003568 x25: ffffffc081b156f0 x24: ffffff8002f91c80 [ 2.360020] x23: ffffff8005e44b23 x22: 0000000000001000 x21: ffffff8005e452d8 [ 2.360033] x20: ffffff8005e40080 x19: ffffff8005e45250 x18: 000000000000002a [ 2.360046] x17: 0000000000000000 x16: 0000000000000001 x15: ffffffc081457f5c [ 2.360060] x14: 0000000000000003 x13: 0000000000000004 x12: 0000000000000001 [ 2.360074] x11: c0000000ffffdfff x10: ffffffc081f5aef8 x9 : 3b1d9621fe45ff00 [ 2.360086] x8 : 3b1d9621fe45ff00 x7 : 0000000000000000 x6 : 332e32202020205b [ 2.360099] x5 : ffffffc0822ec827 x4 : 0000000000000000 x3 : ffffffc08239a3e8 [ 2.360111] x2 : ffffffc08239a3f0 x1 : 00000000ffffdfff x0 : 00000000000000a1 [ 2.360125] Call trace: [ 2.360132] drm_object_attach_property+0x7c/0xc0 [ 2.360142] vop2_plane_init+0x44c/0x4f4 [ 2.360154] vop2_create_crtc+0x474/0xf70 [ 2.360165] vop2_bind+0xe0c/0xf10 [ 2.360176] component_bind_all+0xf8/0x25c [ 2.360188] rockchip_drm_bind+0x130/0x274 [ 2.360198] try_to_bring_up_aggregate_device+0x238/0x2cc [ 2.360210] __component_add+0xac/0x188 [ 2.360222] dw_mipi_dsi_rockchip_host_attach+0x34/0xcc [ 2.360234] dw_mipi_dsi_host_attach+0xc4/0xec [ 2.360245] mipi_dsi_attach+0x3c/0x60 [ 2.360257] HdfDrmPanelEntryInit+0x164/0x1d4 [ 2.360270] HdfDeviceLaunchNode+0x1c0/0x450 [ 2.360282] HdfDeviceAttach+0x68/0x1f0 [ 2.360291] DevHostServiceAddDevice+0x20c/0x35c [ 2.360301] DevHostServiceClntInstallDriver+0xcc/0x1d8 [ 2.360313] DevmgrServiceAttachDeviceHost+0x64/0xf0 [ 2.360324] DevmgrServiceClntAttachDeviceHost+0x70/0xfc [ 2.360335] DevHostServiceStartService+0x3c/0xa4 [ 2.360347] DriverInstallerStartDeviceHost+0x4c/0x10c [ 2.360357] DevmgrServiceStartHostProcess+0x5c/0x1a0 [ 2.360366] DevmgrServiceStartService+0x1b4/0x3d4 [ 2.360378] DeviceManagerStart+0x78/0x134 [ 2.360388] DeviceManagerInit+0x54/0x100 [ 2.360399] __initstub__kmod_devmgr_load__343_47_DeviceManagerInit7+0x1c/0x28 [ 2.360411] do_one_initcall+0x158/0x2a8 [ 2.360423] do_initcall_level+0x108/0x128 [ 2.360434] do_initcalls+0x60/0xa0 [ 2.360444] do_basic_setup+0x40/0x4c [ 2.360453] kernel_init_freeable+0xf0/0x168 [ 2.360462] kernel_init+0x44/0x190 [ 2.360474] ret_from_fork+0x10/0x20 [ 2.360483] ---[ end trace 0000000000000000 ]--- 其中提示“Please increase DRM_OBJECT_MAX_PROPERTY[24] by 1 for each time you see this message on the same object type.” 对比rk3568在 Linux-5.10 内核的补丁，发现 DRM_OBJECT_MAX_PROPERTY 修改为 64，并确认修改为64后，内核启动阶段不会出现上述报错。 建议： linux-6.6\include\drm\drm_mode_object.h 文件中的 #define DRM_OBJECT_MAX_PROPERTY 24 修改为 #define DRM_OBJECT_MAX_PROPERTY 64 ### 期望行为是什么？ 内核启动阶段不出现上述报错。 ### 如何复现该缺陷 DAYU200 编译 OpenHarmony-v5.0.0-Release 代码的 Linux-6.6 内核，系统在启动内核时会打印描述的异常。 ### 其他补充信息 ### 版本或分支信息 - [x] master - [x] 5.0-Beta1 - [ ] Release 4.1 - [ ] Release 4.0 - [ ] Release 3.2
### 发生了什么问题？ DAYU200 平台升级OpenHarmony v5.0.0（Linux-6.6内核）系统，内核启动阶段发生如下异常： > [ 2.359080] rockchip-vop2 fe040000.vop: [drm:vop2_bind] vp0 assign plane mask: 0x2a, primary plane phy id: 5 [ 2.359110] rockchip-vop2 fe040000.vop: [drm:vop2_bind] vp1 assign plane mask: 0x15, primary plane phy id: 4 [ 2.359124] rockchip-vop2 fe040000.vop: [drm:vop2_bind] vp2 assign plane mask: 0x0, primary plane phy id: -1 [ 2.359205] ------------[ cut here ]------------ [ 2.359214] Failed to attach object property (type: 0xeeeeeeee). Please increase DRM_OBJECT_MAX_PROPERTY[24] by 1 for each time you see this message on the same object type. [ 2.359247] WARNING: CPU: 0 PID: 1 at drivers/gpu/drm/drm_mode_object.c:254 drm_object_attach_property+0x7c/0xc0 [ 2.359266] Modules linked in: [ 2.359277] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.6.22 #1 [ 2.359287] Hardware name: rockchip,rk3568-toybrick-dev-linux-x0 (DT) [ 2.359296] pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 2.359306] pc : drm_object_attach_property+0x7c/0xc0 [ 2.359316] lr : drm_object_attach_property+0x7c/0xc0 [ 2.359326] sp : ffffffc08239a680 [ 2.359333] x29: ffffffc08239a680 x28: ffffff8005e4068c x27: ffffff8005e40080 [ 2.359348] x26: 0000000000003568 x25: ffffffc081b156f0 x24: ffffff8002f91c80 [ 2.359362] x23: ffffff8005e44b23 x22: 0000000000001000 x21: ffffff8005e452d8 [ 2.359375] x20: ffffff8005e40080 x19: ffffff8005e45250 x18: 000000000000002a [ 2.359389] x17: 0000000000000000 x16: 0000000000000001 x15: ffffffc081457f5c [ 2.359402] x14: 0 6.6.22 #1 [ 2.359946] Hardware name: rockchip,rk3568-toybrick-dev-linux-x0 (DT) [ 2.359953] pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 2.359963] pc : drm_object_attach_property+0x7c/0xc0 [ 2.359975] lr : drm_object_attach_property+0x7c/0xc0 [ 2.359985] sp : ffffffc08239a680 [ 2.359992] x29: ffffffc08239a680 x28: ffffff8005e4068c x27: ffffff8005e40080 [ 2.360006] x26: 0000000000003568 x25: ffffffc081b156f0 x24: ffffff8002f91c80 [ 2.360020] x23: ffffff8005e44b23 x22: 0000000000001000 x21: ffffff8005e452d8 [ 2.360033] x20: ffffff8005e40080 x19: ffffff8005e45250 x18: 000000000000002a [ 2.360046] x17: 0000000000000000 x16: 0000000000000001 x15: ffffffc081457f5c [ 2.360060] x14: 0000000000000003 x13: 0000000000000004 x12: 0000000000000001 [ 2.360074] x11: c0000000ffffdfff x10: ffffffc081f5aef8 x9 : 3b1d9621fe45ff00 [ 2.360086] x8 : 3b1d9621fe45ff00 x7 : 0000000000000000 x6 : 332e32202020205b [ 2.360099] x5 : ffffffc0822ec827 x4 : 0000000000000000 x3 : ffffffc08239a3e8 [ 2.360111] x2 : ffffffc08239a3f0 x1 : 00000000ffffdfff x0 : 00000000000000a1 [ 2.360125] Call trace: [ 2.360132] drm_object_attach_property+0x7c/0xc0 [ 2.360142] vop2_plane_init+0x44c/0x4f4 [ 2.360154] vop2_create_crtc+0x474/0xf70 [ 2.360165] vop2_bind+0xe0c/0xf10 [ 2.360176] component_bind_all+0xf8/0x25c [ 2.360188] rockchip_drm_bind+0x130/0x274 [ 2.360198] try_to_bring_up_aggregate_device+0x238/0x2cc [ 2.360210] __component_add+0xac/0x188 [ 2.360222] dw_mipi_dsi_rockchip_host_attach+0x34/0xcc [ 2.360234] dw_mipi_dsi_host_attach+0xc4/0xec [ 2.360245] mipi_dsi_attach+0x3c/0x60 [ 2.360257] HdfDrmPanelEntryInit+0x164/0x1d4 [ 2.360270] HdfDeviceLaunchNode+0x1c0/0x450 [ 2.360282] HdfDeviceAttach+0x68/0x1f0 [ 2.360291] DevHostServiceAddDevice+0x20c/0x35c [ 2.360301] DevHostServiceClntInstallDriver+0xcc/0x1d8 [ 2.360313] DevmgrServiceAttachDeviceHost+0x64/0xf0 [ 2.360324] DevmgrServiceClntAttachDeviceHost+0x70/0xfc [ 2.360335] DevHostServiceStartService+0x3c/0xa4 [ 2.360347] DriverInstallerStartDeviceHost+0x4c/0x10c [ 2.360357] DevmgrServiceStartHostProcess+0x5c/0x1a0 [ 2.360366] DevmgrServiceStartService+0x1b4/0x3d4 [ 2.360378] DeviceManagerStart+0x78/0x134 [ 2.360388] DeviceManagerInit+0x54/0x100 [ 2.360399] __initstub__kmod_devmgr_load__343_47_DeviceManagerInit7+0x1c/0x28 [ 2.360411] do_one_initcall+0x158/0x2a8 [ 2.360423] do_initcall_level+0x108/0x128 [ 2.360434] do_initcalls+0x60/0xa0 [ 2.360444] do_basic_setup+0x40/0x4c [ 2.360453] kernel_init_freeable+0xf0/0x168 [ 2.360462] kernel_init+0x44/0x190 [ 2.360474] ret_from_fork+0x10/0x20 [ 2.360483] ---[ end trace 0000000000000000 ]--- 其中提示“Please increase DRM_OBJECT_MAX_PROPERTY[24] by 1 for each time you see this message on the same object type.” 对比rk3568在 Linux-5.10 内核的补丁，发现 DRM_OBJECT_MAX_PROPERTY 修改为 64，并确认修改为64后，内核启动阶段不会出现上述报错。 建议： linux-6.6\include\drm\drm_mode_object.h 文件中的 #define DRM_OBJECT_MAX_PROPERTY 24 修改为 #define DRM_OBJECT_MAX_PROPERTY 64 ### 期望行为是什么？ 内核启动阶段不出现上述报错。 ### 如何复现该缺陷 DAYU200 编译 OpenHarmony-v5.0.0-Release 代码的 Linux-6.6 内核，系统在启动内核时会打印描述的异常。 ### 其他补充信息 ### 版本或分支信息 - [x] master - [x] 5.0-Beta1 - [ ] Release 4.1 - [ ] Release 4.0 - [ ] Release 3.2
Comments (
2
)
Sign in
to comment
Status
Done
Backlog
Doing
Done
Declined
Assignees
Not set
Labels
bug
waiting_for_assign
Not set
Projects
Unprojected
Unprojected
Milestones
No related milestones
No related milestones
Pull Requests
None yet
None yet
Successfully merging a pull request will close this issue.
Branches
No related branch
Branches (
-
)
Tags (
-
)
Planed to start - Planed to end
-
Top level
Not Top
Top Level: High
Top Level: Medium
Top Level: Low
Priority
Not specified
Serious
Main
Secondary
Unimportant
Duration
（hours）
参与者（3）
1
https://gitee.com/openharmony/kernel_linux_patches.git
git@gitee.com:openharmony/kernel_linux_patches.git
openharmony
kernel_linux_patches
kernel_linux_patches
Going to Help Center
Search
Git 命令在线学习
如何在 Gitee 导入 GitHub 仓库
Git 仓库基础操作
企业版和社区版功能对比
SSH 公钥设置
如何处理代码冲突
仓库体积过大，如何减小？
如何找回被删除的仓库数据
Gitee 产品配额说明
GitHub仓库快速导入Gitee及同步更新
什么是 Release（发行版）
将 PHP 项目自动发布到 packagist.org
Comment
Repository Report
Back to the top
Login prompt
This operation requires login to the code cloud account. Please log in before operating.
Go to login
No account. Register
