20240531瑞芯微官方Toybrick TB-RK3588开发板在Debian11下的关机尝试

20240531瑞芯微官方Toybrick TB-RK3588开发板在Debian11下的关机尝试
2024/5/31 9:10


https://t.rock-chips.com/forum.php?mod=forumdisplay&fid=51
在Toybrick的论坛以关键词搜索:关机
可以找到抱怨这个的人很多!


(一)【失败】
https://t.rock-chips.com/forum.php?mod=viewthread&tid=597&highlight=%E5%85%B3%E6%9C%BA
除了拔电源还有其他关机的方式吗

长按PWRON有时候可以有时候不可以

Linux 系统可以使用命令  shutdown   来关机

toybrick@debian:~$ 
toybrick@debian:~$ 
toybrick@debian:~$ shutdown -h now
-bash: shutdown: command not found
toybrick@debian:~$ busybox shutdown -h now
shutdown: applet not found
toybrick@debian:~$ su
Password: 
root@debian:/home/toybrick# 
root@debian:/home/toybrick# shutdown -h now
bash: shutdown: command not found
root@debian:/home/toybrick# 
root@debian:/home/toybrick# reboot -p
bash: reboot: command not found
root@debian:/home/toybrick# su
root@debian:/home/toybrick# su toybrick
toybrick@debian:~$ 
toybrick@debian:~$ reboot -p
bash: reboot: command not found
toybrick@debian:~$ busybox reboot -p
reboot: invalid option -- 'p'
BusyBox v1.30.1 (Debian 1:1.30.1-6+b3) multi-call binary.

Usage: reboot [-d DELAY] [-n] [-f]

Reboot the system

    -d SEC    Delay interval
    -n    Do not sync
    -f    Force (don't go through init)
toybrick@debian:~$ 
toybrick@debian:~$ busybox reboot -d 1
reboot: Operation not permitted
toybrick@debian:~$ 
toybrick@debian:~$ sudo busybox reboot -d 1
toybrick@debian:~$ [  143.922115] systemd[1]: systemd 247.3-7+deb11u4 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +ZSTD +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=unified)
[  143.923213] systemd[1]: Detected architecture arm64.
[  144.036302] systemd[1]: /lib/systemd/system/plymouth-start.service:16: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update your service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.

toybrick@debian:~$ 


https://t.rock-chips.com/forum.php?mod=viewthread&tid=744&highlight=%E5%85%B3%E6%9C%BA
遇到不能关机的情况


toybrick 不能关机  
shutdown now  终端不能关机   关机之后又会重新启动  

只能把电源线了

好像这个板子设计就是这样的,不然每次开机大家插完线还要按power开机,又会有人问为啥不能自动上电开机


https://t.rock-chips.com/forum.php?mod=viewthread&tid=1978&highlight=%E5%85%B3%E6%9C%BA
自己编译安卓源码固件后,关机重启问题


我的TB-RK3399PRODS开发板,用你们的固件烧写后关机和重启正常的。我自己在你们网站下载的源码编译成固件后烧写进开发板后在按关机按钮在安卓桌面显示“Power off”和“Restart”,能正常关机,但是选择“Power off”后开发板会关机,电源灯也不灭,一会后自动启动。不知道什么原因。


https://t.rock-chips.com/forum.php?mod=viewthread&tid=4568&highlight=%E5%85%B3%E6%9C%BA
TB-RK3588X buildroot系统,长按power键关机后自动重启

TB-RK3588X buildroot系统,长按power键,系统进入关机流程,但关机后,又会自动重启,以下是日志。请帮忙分析下原因,谢谢
key_event:
  code     : POWER
  source   : /dev/input/event0
  exec     : "/etc/power-key.sh press"

Requesting system poweroff
[   29.445013] rk860-regulator 2-0042: rk860..... reset
[   29.450497] rk860-regulator 2-0042: force rk860x_reset ok!
[   29.456017] rk860-regulator 0-0043: rk860..... reset
[   29.462076] rk860-regulator 0-0043: force rk860x_reset ok!
[   29.467579] rk860-regulator 0-0042: rk860..... reset
[   29.473635] rk860-regulator 0-0042: force rk860x_reset ok!
[   29.532932] mpp_av1dec av1d-master: shutdown device
[   29.537829] mpp_av1dec av1d-master: shutdown success
[   29.542872] [WLAN_RFKILL]: Enter rfkill_wlan_shutdown
[   29.547917] [WLAN_RFKILL]: rockchip_wifi_power: 0
[   29.552613] [WLAN_RFKILL]: rockchip_wifi_power: toggle = false
[   29.558439] wifi power off
[   29.665582] [WLAN_RFKILL]: wifi shut off power [GPIO105-0]
[   29.671071] [WLAN_RFKILL]: rfkill_set_wifi_bt_power: 0
[   29.676305] xhci-hcd xhci-hcd.7.auto: remove, state 4
[   29.681356] usb usb6: USB disconnect, device number 1
[   29.686866] xhci-hcd xhci-hcd.7.auto: USB bus 6 deregistered
[   29.692769] xhci-hcd xhci-hcd.7.auto: remove, state 4
[   29.697845] usb usb5: USB disconnect, device number 1
[   29.703409] xhci-hcd xhci-hcd.7.auto: USB bus 5 deregistered
[   29.709760] mpp_rkvdec2 fdc48100.rkvdec-core: shutdown device
[   29.715556] mpp_rkvdec2 fdc48100.rkvdec-core: shutdown success
[   29.721443] mpp_rkvdec2 fdc38100.rkvdec-core: shutdown device
[   29.727193] mpp_rkvdec2 fdc38100.rkvdec-core: shutdown success
[   29.733045] mpp_rkvenc2 fdbe0000.rkvenc-core: shutdown device
[   29.738791] mpp_rkvenc2 fdbe0000.rkvenc-core: shutdown success
[   29.744635] mpp_rkvenc2 fdbd0000.rkvenc-core: shutdown device
[   29.750379] mpp_rkvenc2 fdbd0000.rkvenc-core: shutdown success
[   29.756221] mpp-iep2 fdbb0000.iep: shutdown device
[   29.761002] mpp-iep2 fdbb0000.iep: shutdown success
[   29.765878] mpp_vepu2 fdbac000.jpege-core: shutdown device
[   29.771361] mpp_vepu2 fdbac000.jpege-core: shutdown success
[   29.776939] mpp_vepu2 fdba8000.jpege-core: shutdown device
[   29.782414] mpp_vepu2 fdba8000.jpege-core: shutdown success
[   29.787989] mpp_vepu2 fdba4000.jpege-core: shutdown device
[   29.793470] mpp_vepu2 fdba4000.jpege-core: shutdown success
[   29.799046] mpp_vepu2 fdba0000.jpege-core: shutdown device
[   29.804528] mpp_vepu2 fdba0000.jpege-core: shutdown success
[   29.810098] mpp_jpgdec fdb90000.jpegd: shutdown device
[   29.815233] mpp_jpgdec fdb90000.jpegd: shutdown success
[   29.820477] mpp_vdpu2 fdb50400.vdpu: shutdown device
[   29.825431] mpp_vdpu2 fdb50400.vdpu: shutdown success
[   29.830560] dwc3 fc000000.usb: Wakeup sysfs attributes not added
[   29.842467] reboot: Power down
DDR Version V1.07 20220412
LPDDR4X, 2112MHz
channel[0] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB
channel[1] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB
channel[2] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB
channel[3] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB
change to F1: 528MHz
change to F2: 1068MHz
change to F3: 1560MHz
change to F0: 2112MHz


https://t.rock-chips.com/forum.php?mod=viewthread&tid=4570&highlight=%E5%85%B3%E6%9C%BA
TB-RK3588X debian系统,长按power键关机后自动重启

使用TB-RK3588X0-Release_V1.0.1_20230203固件包或者sdk制作的images,在开发板上都出现长按关机后系统自动重启的情况,请帮忙分析下原因。
以下是部分日志

[  OK  ] Stopped Network Time Synchronization.
[  OK  ] Stopped Load/Save Screen B…htness of backlight:backlight.
[  OK  ] Removed slice system-systemd\x2dbacklight.slice.
[  OK  ] Stopped Update UTMP about System Boot/Shutdown.
[  OK  ] Stopped Create Volatile Files and Directories.
[  OK  ] Stopped target Local File Systems.
[  OK  ] Stopped target Local File Systems (Pre).
[  OK  ] Stopped Create Static Device Nodes in /dev.
[  OK  ] Stopped Create System Users.
[  OK  ] Stopped Remount Root and Kernel File Systems.
[  OK  ] Reached target Shutdown.
[  OK  ] Reached target Final Step.
[  OK  ] Finished Power-Off.
[  OK  ] Reached target Power-Off.
[  338.020724] systemd-shutdown[1]: Syncing filesystems and block devices.
[  338.037838] systemd-shutdown[1]: Sending SIGTERM to remaining processes...
[  338.053411] systemd-journald[281]: Received SIGTERM from PID 1 (systemd-shutdow).
[  338.076645] systemd-shutdown[1]: Sending SIGKILL to remaining processes...
[  338.094310] systemd-shutdown[1]: Unmounting file systems.
[  338.096609] [20222]: Remounting '/' read-only in with options '(null)'.
[  338.118306] EXT4-fs (mmcblk0p6): re-mounted. Opts: (null)
[  338.138866] systemd-shutdown[1]: All filesystems unmounted.
[  338.138910] systemd-shutdown[1]: Deactivating swaps.
[  338.139037] systemd-shutdown[1]: All swaps deactivated.
[  338.139049] systemd-shutdown[1]: Detaching loop devices.
[  338.141422] systemd-shutdown[1]: All loop devices detached.
[  338.141449] systemd-shutdown[1]: Stopping MD devices.
[  338.141632] systemd-shutdown[1]: All MD devices stopped.
[  338.141645] systemd-shutdown[1]: Detaching DM devices.
[  338.141804] systemd-shutdown[1]: All DM devices detached.
[  338.141816] systemd-shutdown[1]: All filesystems, swaps, loop devices, MD devices and DM devices detached.
[  338.160178] systemd-shutdown[1]: Syncing filesystems and block devices.
[  338.161406] systemd-shutdown[1]: Powering off.
[  338.339761] rk860-regulator 2-0042: rk860..... reset
[  338.340612] rk860-regulator 2-0042: force rk860x_reset ok!
[  338.341109] rk860-regulator 0-0043: rk860..... reset
[  338.342508] rk860-regulator 0-0043: force rk860x_reset ok!
[  338.343004] rk860-regulator 0-0042: rk860..... reset
[  338.344407] rk860-regulator 0-0042: force rk860x_reset ok!
[  338.390014] mpp_av1dec av1d-master: shutdown device
[  338.390442] mpp_av1dec av1d-master: shutdown success
[  338.390945] [WLAN_RFKILL]: Enter rfkill_wlan_shutdown
[  338.391393] [WLAN_RFKILL]: rockchip_wifi_power: 0
[  338.391808] [WLAN_RFKILL]: rockchip_wifi_power: toggle = false
[  338.392320] wifi power off
[  338.499248] [WLAN_RFKILL]: wifi shut off power [GPIO105-0]
[  338.499729] [WLAN_RFKILL]: rfkill_set_wifi_bt_power: 0
[  338.500469] rockchip-i2s-tdm fddf8000.i2s: failed to clear 1
[  338.501076] rockchip-i2s-tdm fddf8000.i2s: failed to clear on slave mode 1
[  338.501933] rockchip-i2s-tdm fddf8000.i2s: failed to clear 2
[  338.502499] xhci-hcd xhci-hcd.6.auto: remove, state 4
[  338.502951] usb usb6: USB disconnect, device number 1
[  338.503724] xhci-hcd xhci-hcd.6.auto: USB bus 6 deregistered
[  338.504398] xhci-hcd xhci-hcd.6.auto: remove, state 4
[  338.504847] usb usb5: USB disconnect, device number 1
[  338.505829] xhci-hcd xhci-hcd.6.auto: USB bus 5 deregistered
[  338.507264] rkisp_hw fdcc0000.rkisp: rkisp_hw_shutdown
[  338.507732] rkisp_hw fdcb0000.rkisp: rkisp_hw_shutdown
[  338.508212] mpp_rkvdec2 fdc48100.rkvdec-core: shutdown device
[  338.508715] mpp_rkvdec2 fdc48100.rkvdec-core: shutdown success
[  338.509261] mpp_rkvdec2 fdc38100.rkvdec-core: shutdown device
[  338.509764] mpp_rkvdec2 fdc38100.rkvdec-core: shutdown success
[  338.510298] mpp_rkvenc2 fdbe0000.rkvenc-core: shutdown device
[  338.510800] mpp_rkvenc2 fdbe0000.rkvenc-core: shutdown success
[  338.511338] mpp_rkvenc2 fdbd0000.rkvenc-core: shutdown device
[  338.511841] mpp_rkvenc2 fdbd0000.rkvenc-core: shutdown success
[  338.512377] mpp-iep2 fdbb0000.iep: shutdown device
[  338.512811] mpp-iep2 fdbb0000.iep: shutdown success
[  338.513257] mpp_vepu2 fdbac000.jpege-core: shutdown device
[  338.513738] mpp_vepu2 fdbac000.jpege-core: shutdown success
[  338.514245] mpp_vepu2 fdba8000.jpege-core: shutdown device
[  338.514726] mpp_vepu2 fdba8000.jpege-core: shutdown success
[  338.515233] mpp_vepu2 fdba4000.jpege-core: shutdown device
[  338.515714] mpp_vepu2 fdba4000.jpege-core: shutdown success
[  338.516228] mpp_vepu2 fdba0000.jpege-core: shutdown device
[  338.516709] mpp_vepu2 fdba0000.jpege-core: shutdown success
[  338.517217] mpp_jpgdec fdb90000.jpegd: shutdown device
[  338.517665] mpp_jpgdec fdb90000.jpegd: shutdown success
[  338.518172] mpp_vepu2 fdb50000.vepu: shutdown device
[  338.518609] mpp_vepu2 fdb50000.vepu: shutdown success
[  338.519058] mpp_vdpu2 fdb50400.vdpu: shutdown device
[  338.519501] mpp_vdpu2 fdb50400.vdpu: shutdown success
[  338.520084] dwc3 fc000000.usb: Wakeup sysfs attributes not added
[  338.527444] reboot: Power down
DDR V1.09 a930779e06 typ 22/11/21-17:50:56
LPDDR4X, 2112MHz
channel[0] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB
channel[1] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB
channel[2] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB
channel[3] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB
Manufacturer ID:0x1
CH0 RX Vref:30.7%, TX Vref:21.8%,20.8%
CH1 RX Vref:29.7%, TX Vref:21.8%,20.8%
CH2 RX Vref:32.7%, TX Vref:19.8%,20.8%
CH3 RX Vref:30.7%, TX Vref:19.8%,21.8%


toybrick 板子默认不支持关机功能,需要改硬件才能支持

请问是改哪里?是跳线或者更改电阻呢?方便提供一下sch的差异部分吗?

请问改动的地方多吗?麻烦帮忙提供需要修改的地方,我这边修改一下看看,谢谢。

【逮着你购买的淘宝商家的客服使劲问吧!】
修改的地方:感觉原理图部分的差异不是一般的大。
反正做驱动的我是没有看懂,淘宝客服让找自己公司的硬件去看看!

【对于这种设计缺陷,如果Toybrick的服务周到的话,对于购买的用户,全部免费赠送就是了!】
【对于这种设计缺陷,如果Toybrick的服务周到的话,对于购买开发板的用户,全部免费赠送所需要的修改转接板就是了!或者快递回去,免费返工!】
 

本文来自互联网用户投稿,该文观点仅代表作者本人,不代表本站立场。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如若转载,请注明出处:/a/663312.html

如若内容造成侵权/违法违规/事实不符,请联系我们进行投诉反馈qq邮箱809451989@qq.com,一经查实,立即删除!

相关文章

深入分析 Android Service (三)

文章目录 深入分析 Android Service (三)1. Service 与 Activity 之间的通信2. 详细示例:通过绑定服务进行通信2.1 创建一个绑定服务2.2 绑定和通信 3. 优化建议4. 使用场景5. 总结 深入分析 Android Service (三) 1. Service 与 Activity 之间的通信 在 Android …

linux nohup命令详解:持久运行命令,无视终端退出

nohup (全称为 “no hang up”),用于运行一个命令,使其在你退出 shell 或终端会话后继续运行。 基本语法 nohup command [arg1 ...] [&> output_file] &command 是你想要运行的命令。[arg1 ...] 是该命令的参数。&am…

Spring Boot 整合 spring-boot-starter-mail 实现邮件发送和账户激活

😄 19年之后由于某些原因断更了三年,23年重新扬帆起航,推出更多优质博文,希望大家多多支持~ 🌷 古之立大事者,不惟有超世之才,亦必有坚忍不拔之志 🎐 个人CSND主页——Mi…

Wireshark抓包后的报文太大,如何拆分?

背景:抓包获取到一个400多兆的网络数据包.pcapng文件,使用wireshark软件可以正常打开。但需要把文件导出为.json文件,从而方便对报文内容做过滤分析。使用wireshark自带的导出功能导出后发现生成的.json文件大小为2G多,使用notepa…

Java-----Comparable接口和Comparator接口

在Java中&#xff0c;我们会经常使用到自定义类&#xff0c;那我们如何进行自定义类的比较呢? 1.Comparable接口 普通数据的比较 int a10;int b91;System.out.println(a<b); 那自定义类型可不可以这样比较呢&#xff1f;看一下代码 我们发现会报错&#xff0c;因为自定义…

电机控制系列模块解析(25)—— 过压抑制与欠压抑制

一、概念解析 变频器作为一种重要的电机驱动装置&#xff0c;其内置的保护功能对于确保系统安全、稳定运行至关重要。以下是关于变频器过压抑制、欠压抑制&#xff08;晃电抑制&#xff09;、发电功率限制、电动功率限制等保护功能的详细说明&#xff1a; 过压抑制 过压抑制是…

YoloV8改进策略:卷积篇|基于PConv的二次创新|附结构图|性能和精度得到大幅度提高(独家原创)

摘要 在PConv的基础上做了二次创新,创新后的模型不仅在精度和速度上有了质的提升,还可以支持Stride为2的降采样。 改进方法简单高效,需要发论文的同学不要错过! 论文指导 PConv在论文中的描述 论文: 下面我们展示了可以通过利用特征图的冗余来进一步优化成本。如图3所…

golang web补充知识:单元测试

文章目录 golang 单元测试引言单元测试的重要性Go语言单元测试的优势 Go语言单元测试基础testing包辅助测试函数运行单元测试 Mock技术Mock简介GoMock框架介绍编写Mock代码使用Mock进行单元测试 面向测试编程&#xff08;TDD&#xff09;TDD简介TDD的优势TDD的基本步骤Go语言中…

discuz如何添加主导航

大家好&#xff0c;今天教大家怎么样给discuz添加主导航。方法其实很简单&#xff0c;大家跟着我操作既可。一个网站的导航栏是非常重要的&#xff0c;一般用户进入网站的第一印象就是看网站的导航栏。如果大家想看效果的话可以搜索下网创有方&#xff0c;或者直接点击查看效果…

大数据中的电商数仓项目:探秘业务的核心

我学习完一个电商数仓的项目和电影实时推荐项目&#xff0c;便兴冲冲的去面试大数据开发岗&#xff0c;在面试的时候&#xff0c;面试官总是喜欢问&#xff0c;聊聊你为什么要做这个项目以及你这个项目有哪些业务&#xff1f; 我心想&#xff0c;为什么要做这个业务&#xff1f…

重学java 52.集合 斗地主案例

你太锐利了&#xff0c;这些年来&#xff0c;风霜雨雪&#xff0c;踉跄清冷&#xff0c;我相信你所有的苦楚 —— 24.5.30 1 案例介绍 按照斗地主的规则&#xff0c;完成洗牌发牌的动作。 具体规则: 使用54张牌打乱顺序,三个玩家参与游戏&#xff0c;三人交替摸牌&#xff0c…

ipv6基础

地址 前缀子网主机位 PI法则3.14 前缀&#xff1a;3个16位 子网&#xff1a;1个16位 接口ID&#xff1a;4个16位 地址分类 未指定地址 ::/128 &#xff0c;类似于0.0.0.0 本地回环地址 ::1/128 &#xff0c;用于本地测试&#xff0c;类似于127.0.0.1 本地链路地址&#x…

【云原生】kubernetes中pod的生命周期、探测钩子的实战应用案例解析

✨✨ 欢迎大家来到景天科技苑✨✨ &#x1f388;&#x1f388; 养成好习惯&#xff0c;先赞后看哦~&#x1f388;&#x1f388; &#x1f3c6; 作者简介&#xff1a;景天科技苑 &#x1f3c6;《头衔》&#xff1a;大厂架构师&#xff0c;华为云开发者社区专家博主&#xff0c;…

正则匹配优化:匹配排除多个字符串的其他字符串

(^entity|^with|...)\w优化 (?!entity|with|has|index|associations|input)\w(?!): 匹配排除项 效果 继续优化 匹配会过滤掉带有关键字的字段&#xff0c;在过滤的时候是可以加上尾部结束匹配符的 效果&#xff1a;

JS-Lodash工具库

文档&#xff1a;Lodash Documentation orderBy函数&#xff1a;根据条件进行排序 注&#xff1a;第一个是要排序的数组&#xff0c;第二个是根据什么字段进行排序&#xff0c;第三个是排序的方式&#xff08;desc倒序&#xff09; 安装方式&#xff1a;Lodash npm i lodash…

【码银送书第二十期】《游戏运营与出海实战:策略、方法与技巧》

市面上的游戏品种繁杂&#xff0c;琳琅满目&#xff0c;它们是如何在历史的长河中逐步演变成今天的模式的呢&#xff1f;接下来&#xff0c;我们先回顾游戏的发展史&#xff0c;然后按照时间轴来叙述游戏运营的兴起。 作者&#xff1a;艾小米 本文经机械工业出版社授权转载&a…

平衡二叉树(oj题)

一、题目链接&#xff1a; https://leetcode.cn/problems/balanced-binary-tree/submissions/536133365 二、思路 调用深度计算函数&#xff0c;得到每次当前的根结点的左右子树的深度。比较每次得到的左右子树深度之差 如果当前根节点的左右子树的深度差大于1,说明不是平衡…

03-树2 List Leaves(浙大数据结构PTA习题)

03-树2 List Leaves 分数 25 全屏浏览 切换布局 作者 陈越 单位 浙江大学 Given a tree, you are supposed to list all the leaves in the order of top down, and left to right. Input Specification: Each input file contains one test c…

mac 安装java jdk8 jdk11 jdk17 等

oracle官网 https://www.oracle.com/java/technologies/downloads/ 查看当前电脑是英特尔的x86 还是arm uname -m 选择指定版本&#xff0c;指定平台的安装包&#xff1a; JDK8 JDK11的&#xff0c;需要当前页面往下拉&#xff1a; 下载到的安装包&#xff0c;双击安装&#x…

Linux系统编程(六)线程同步机制

本文目录 前述&#xff1a;同步机制的引入及概念一、线程的互斥锁1. 定义2. 互斥锁常用方法3. 相关函数&#xff08;1&#xff09;头文件&#xff08;2&#xff09;创建互斥锁&#xff08;3&#xff09;销毁互斥锁&#xff08;4&#xff09;加锁&#xff08;5&#xff09;解锁 …