W中的Event 1A到Event 1J以及Event 2A到2F的含义?

本文深入探讨了移动通信中的频内测量与频间测量内容,包括测量小区信息、测量数量、报告准则和触发事件等关键要素,旨在帮助读者理解如何在不同频率范围内进行有效测量。

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

频内测量内容:
1)频内测量小区信息列表
2)频内测量数值(CPICH、Ec/No、CPICH RSCP、RSSI/pathloss)
3)频内测量报告数值
4)报告小区状态
5)测量有效性(有效的UE状态)可选
6)报告准则(频内测量报告准则、周期性测量报告准则、不报告)
频内测量报告的触发事件:
1A:CELL 进入报告范围。
1B:CELL 离开报告范围。
1C:有CELL的信号优于有效集罪差CELL.
1D:最优CELL改变。
1E:一个CELL的导频信号优于绝对门限值。
1F:一个CELL的导频信号差于绝对门限值。

频间测量内容:
1)频间测量小区信息列表
2)频间测量数值(CPICH Ec/No、CPICH RSCP )
3)频内测量报告数值(RSSI、频率质量估计、小区报告信息)
4)报告小区状态
5)测量有效性(有效的UE状态)可选
6)频间集更新
7)报告准则(频间测量报告准则、频内测量报告准则、周期性测量报告准则、不报告)

频间测量报告的触发事件:
2A::最佳载频发生改变,即有非当前载频的信号质量高于当前载频的信号质量
2B::当前使用的载频信号质量低于一门限值,并且一个未使用的估计质量高于一门限值。
2C::某个未使用载频的信号质量高于某一门限值。
2D:当前载频信号质量低于某个门限值。
2E:某个非当前载频信号质量低于某个门限值。

2F:当前载频信号质量高于某个门限值。

http://bbs.c114.net/thread-351840-1-1.html

-dump time is 1970-01-01_08-51-07 -reboot reg is 80 -reset mode is d -reason is kernel_crash -bootcause_cmdline is Reboot into panic -exception_reboot_reason: kernel_crash Vmcoreinfo: -kimage_voffset = 0xffffffbf88000000 -phys_offset = 0x80000000 -kaslr_offset = 0x80000 -vabits_actual = 39 -exception_kernel_version:Linux version 5.15.74 (lhl@ISS) (OHOS (dev) clang version 15.0.4 (llvm-project 81cdec3cd117b1e6e3a9f1ebc4695d790c978463), LLD 15.0.4) #1 SMP PREEMPT Thu Jun 19 11:17:09 CST 2025 -exception_panic_reason:Oops - BUG: Fatal exception -exception_file_infoi: -exception_task_id:2271 -exception_task_family:[malloc-multi-th, 2271][hdcd, 1651] -exception_pc_symbol:[<ffffffc00848ee10>] __vma_adjust+0xc44/0xc78 -exception_stack_info:[<ffffffc00913ac08>] get_exception_stack_info+0x128/0x2a4 [<ffffffc00913afd4>] prepare_exception_info+0x178/0x1d0 [<ffffffc00913bc68>] sysdump_panic_event+0x730/0x92c [<ffffffc00821e0fc>] atomic_notifier_call_chain+0x88/0x100 [<ffffffc0081deaa0>] panic+0x1a8/0x444 [<ffffffc00814bed8>] die+0x2dc/0x2f4 [<ffffffc00814d5b8>] bug_handler+0x54/0xf8 [<ffffffc008139fc0>] brk_handler+0xa8/0x170 [<ffffffc008173c30>] do_debug_exception+0xc4/0x1a8 [<ffffffc00980e968>] el1_dbg+0x48/0x68 [<ffffffc00980e7a4>] el1h_64_sync_handler+0x48/0xa4 [<ffffffc008091b10>] el1h_64_sync+0x7c/0x80 [<ffffffc00848ee10>] __vma_adjust+0xc44/0xc78 [<ffffffc008491bc0>] __split_vma+0x14c/0x260 [<ffffffc008491e18>] __do_munmap+0xf8/0x724 [<ffffffc008492630>] __vm_munmap.llvm.15742267499309760575+0x94/0x180 [<ffffffc00849276c>] __arm64_sys_munmap+0x50/0x68 [<ffffffc008159204>] invoke_syscall+0x6c/0x15c [<ffffffc008159110>] el0_svc_common.llvm.9499517201915720397+0xd4/0x120 [<ffffffc008158fc4>] do_el0_svc+0x34/0xac [<ffffffc00980edb0>] el0_svc+0x2c/0x94 [<ffffffc00980ed20>] el0t_64_sync_handler+0x8c/0xf0 [<ffffffc008091e48>] el0t_64_sync+0x1b4/0x1b8 -dump time is 1970-01-01_22-30-34 -reboot reg is 80 -reset mode is d -reason is kernel_crash -bootcause_cmdline is Reboot into panic -exception_reboot_reason: kernel_crash Vmcoreinfo: -kimage_voffset = 0xffffffbf88000000 -phys_offset = 0x80000000 -kaslr_offset = 0x80000 -vabits_actual = 39 -exception_kernel_version:Linux version 5.15.74 (lhl@ISS) (OHOS (dev) clang version 15.0.4 (llvm-project 81cdec3cd117b1e6e3a9f1ebc4695d790c978463), LLD 15.0.4) #1 SMP PREEMPT Thu Jun 19 11:17:09 CST 2025 -exception_panic_reason:Oops: Fatal exception -exception_file_infoi:not-bugon -exception_task_id:2335 -exception_task_family:[malloc-multi-th, 2335][hdcd, 1563] -exception_pc_symbol:[<ffffffc0084c492c>] kmem_cache_alloc+0x128/0x3dc -exception_stack_info:[<ffffffc00913ac08>] get_exception_stack_info+0x128/0x2a4 [<ffffffc00913afd4>] prepare_exception_info+0x178/0x1d0 [<ffffffc00913bc68>] sysdump_panic_event+0x730/0x92c [<ffffffc00821e0fc>] atomic_notifier_call_chain+0x88/0x100 [<ffffffc0081deaa0>] panic+0x1a8/0x444 [<ffffffc00814bed8>] die+0x2dc/0x2f4 [<ffffffc0081744dc>] __do_kernel_fault+0x298/0x2f4 [<ffffffc0081740d0>] do_bad_area+0x40/0x100 [<ffffffc00987fe4c>] do_translation_fault+0x5c/0x70 [<ffffffc00817364c>] do_mem_abort+0x74/0x138 [<ffffffc00980e844>] el1_abort+0x44/0x68 [<ffffffc00980e7c0>] el1h_64_sync_handler+0x64/0xa4 [<ffffffc008091b10>] el1h_64_sync+0x7c/0x80 [<ffffffc0084c492c>] kmem_cache_alloc+0x128/0x3dc [<ffffffc0081d7e6c>] vm_area_alloc+0x34/0xac [<ffffffc00848fc8c>] mmap_region+0x268/0x728 [<ffffffc00848f754>] do_mmap+0x3d4/0x540 [<ffffffc00845d308>] vm_mmap_pgoff+0xd0/0x234 [<ffffffc008490208>] ksys_mmap_pgoff+0xbc/0x108 [<ffffffc00814b394>] __arm64_sys_mmap+0x44/0x54 [<ffffffc008159204>] invoke_syscall+0x6c/0x15c [<ffffffc008159110>] el0_svc_common.llvm.9499517201915720397+0xd4/0x120 [<ffffffc008158fc4>] do_el0_svc+0x34/0xac [<ffffffc00980edb0>] el0_svc+0x2c/0x94 [<ffffffc00980ed20>] el0t_64_sync_handler+0x8c/0xf0 [<ffffffc008091e48>] el0t_64_sync+0x1b4/0x1b8 -dump time is 1970-01-01_23-09-04 -reboot reg is 80 -reset mode is d -reason is kernel_crash -bootcause_cmdline is Reboot into panic -exception_reboot_reason: kernel_crash Vmcoreinfo: -kimage_voffset = 0xffffffbf88000000 -phys_offset = 0x80000000 -kaslr_offset = 0x80000 -vabits_actual = 39 -exception_kernel_version:Linux version 5.15.74 (lhl@ISS) (OHOS (dev) clang version 15.0.4 (llvm-project 81cdec3cd117b1e6e3a9f1ebc4695d790c978463), LLD 15.0.4) #1 SMP PREEMPT Thu Jun 19 11:17:09 CST 2025 -exception_panic_reason:Oops - BUG: Fatal exception -exception_file_infoi: -exception_task_id:3311 -exception_task_family:[malloc-multi-th, 3311][hdcd, 1535] -exception_pc_symbol:[<ffffffc00848ee10>] __vma_adjust+0xc44/0xc78 -exception_stack_info:[<ffffffc00913ac08>] get_exception_stack_info+0x128/0x2a4 [<ffffffc00913afd4>] prepare_exception_info+0x178/0x1d0 [<ffffffc00913bc68>] sysdump_panic_event+0x730/0x92c [<ffffffc00821e0fc>] atomic_notifier_call_chain+0x88/0x100 [<ffffffc0081deaa0>] panic+0x1a8/0x444 [<ffffffc00814bed8>] die+0x2dc/0x2f4 [<ffffffc00814d5b8>] bug_handler+0x54/0xf8 [<ffffffc008139fc0>] brk_handler+0xa8/0x170 [<ffffffc008173c30>] do_debug_exception+0xc4/0x1a8 [<ffffffc00980e968>] el1_dbg+0x48/0x68 [<ffffffc00980e7a4>] el1h_64_sync_handler+0x48/0xa4 [<ffffffc008091b10>] el1h_64_sync+0x7c/0x80 [<ffffffc00848ee10>] __vma_adjust+0xc44/0xc78 [<ffffffc008491bc0>] __split_vma+0x14c/0x260 [<ffffffc008491e88>] __do_munmap+0x168/0x724 [<ffffffc008492630>] __vm_munmap.llvm.15742267499309760575+0x94/0x180 [<ffffffc00849276c>] __arm64_sys_munmap+0x50/0x68 [<ffffffc008159204>] invoke_syscall+0x6c/0x15c [<ffffffc008159110>] el0_svc_common.llvm.9499517201915720397+0xd4/0x120 [<ffffffc008158fc4>] do_el0_svc+0x34/0xac [<ffffffc00980edb0>] el0_svc+0x2c/0x94 [<ffffffc00980ed20>] el0t_64_sync_handler+0x8c/0xf0 [<ffffffc008091e48>] el0t_64_sync+0x1b4/0x1b8 -dump time is 1970-01-01_23-52-44 -reboot reg is 80 -reset mode is d -reason is kernel_crash -bootcause_cmdline is Reboot into panic -exception_reboot_reason: kernel_crash Vmcoreinfo: -kimage_voffset = 0xffffffbf88000000 -phys_offset = 0x80000000 -kaslr_offset = 0x80000 -vabits_actual = 39 -exception_kernel_version:Linux version 5.15.74 (lhl@ISS) (OHOS (dev) clang version 15.0.4 (llvm-project 81cdec3cd117b1e6e3a9f1ebc4695d790c978463), LLD 15.0.4) #1 SMP PREEMPT Thu Jun 19 11:17:09 CST 2025 -exception_panic_reason:CFI failure (target: 0x7fb3780000) -exception_file_infoi:not-bugon -exception_task_id:2080 -exception_task_family:[irq/128-dwc3, 2080][kthreadd, 2] -exception_pc_symbol:[<ffffffc00913b728>] sysdump_panic_event+0x1f0/0x92c -exception_stack_info:[<ffffffc00913ac08>] get_exception_stack_info+0x128/0x2a4 [<ffffffc00913afd4>] prepare_exception_info+0x178/0x1d0 [<ffffffc00913bc68>] sysdump_panic_event+0x730/0x92c [<ffffffc00821e0fc>] atomic_notifier_call_chain+0x88/0x100 [<ffffffc0081deaa0>] panic+0x1a8/0x444 [<ffffffc0083fc9a0>] __cfi_slowpath_diag+0x1e4/0x230 [<ffffffc0082b56d0>] rcu_do_batch+0x36c/0x8f4 [<ffffffc0082b4fe8>] rcu_core+0x210/0x58c [<ffffffc0082ade4c>] rcu_core_si+0x20/0x30 [<ffffffc008090460>] __do_softirq+0x170/0x5c8 [<ffffffc0081ea344>] do_softirq+0x78/0xf0 [<ffffffc0081ea280>] __local_bh_enable_ip+0xec/0x138 [<ffffffc00813e280>] local_bh_enable+0x28/0x38 [<ffffffc008d507f4>] dwc3_thread_interrupt+0x12bc/0x15d0 [<ffffffc00828ee04>] irq_thread_fn+0x54/0xe4 [<ffffffc00828ea84>] irq_thread+0x1c8/0x3b8 [<ffffffc00821c220>] kthread+0x170/0x1d4 [<ffffffc008095118>] ret_from_fork+0x10/0x20 -dump time is 1970-01-01_08-26-27 -reboot reg is 80 -reset mode is d -reason is kernel_crash -bootcause_cmdline is Reboot into panic -exception_reboot_reason: kernel_crash Vmcoreinfo: -kimage_voffset = 0xffffffbf88000000 -phys_offset = 0x80000000 -kaslr_offset = 0x80000 -vabits_actual = 39 -exception_kernel_version:Linux version 5.15.74 (lhl@ISS) (OHOS (dev) clang version 15.0.4 (llvm-project 81cdec3cd117b1e6e3a9f1ebc4695d790c978463), LLD 15.0.4) #1 SMP PREEMPT Sat Jun 14 17:38:52 CST 2025 -exception_panic_reason:Oops: Fatal exception in interrupt -exception_file_infoi:not-bugon -exception_task_id:14 -exception_task_family:[ksoftirqd/0, 14][kthreadd, 2] -exception_pc_symbol:[<7f9b140000>] 0x7f9b140000 -exception_stack_info:[<ffffffc009165794>] get_exception_stack_info+0x128/0x2a4 [<ffffffc009165b60>] prepare_exception_info+0x178/0x1d0 [<ffffffc0091667f4>] sysdump_panic_event+0x730/0x92c [<ffffffc00821f770>] atomic_notifier_call_chain+0x88/0x100 [<ffffffc0081e0028>] panic+0x1b4/0x458 [<ffffffc00814c94c>] die+0x2cc/0x2f4 [<ffffffc008175984>] __do_kernel_fault+0x298/0x2f4 [<ffffffc0098ab4a8>] do_page_fault+0x2e8/0x694 [<ffffffc008174af4>] do_mem_abort+0x74/0x138 [<ffffffc0098393dc>] el1_abort+0x44/0x68 [<ffffffc009839358>] el1h_64_sync_handler+0x64/0xa4 [<ffffffc008091b10>] el1h_64_sync+0x7c/0x80 [<7f9b140000>] 0x7f9b140000 [<ffffffc0082b6a88>] rcu_core+0x210/0x58c [<ffffffc0082af8ec>] rcu_core_si+0x20/0x30 [<ffffffc008090460>] __do_softirq+0x170/0x5c8 [<ffffffc0081ed0ec>] run_ksoftirqd+0x50/0xac [<ffffffc008224724>] smpboot_thread_fn+0x2d4/0x3d8 [<ffffffc00821d894>] kthread+0x170/0x1d4 [<ffffffc008095118>] ret_from_fork+0x10/0x20 #include <malloc.h> #include <time.h> #include <sched.h> #include <errno.h> #include <string.h> #include <pthread.h> #include "test.h" #define THREAD_MAX_N 8 #define SIZE_ALIGN (4 * sizeof(size_t)) #define MMAP_THRESHOLD 131052 #define FREE_CYCLE 16 #define THRESHOLD (MMAP_THRESHOLD / 16) #define ITER_TIME 80 #define NANOSEC_PER_SEC 1e9 #define MALLOC_TIME (ITER_TIME * (THRESHOLD / (SIZE_ALIGN + 1))) void free_all(void **ptr) { for (int j = 0; j < FREE_CYCLE; j++) { free(ptr[j]); } } void *func(void *arg) { int *val = (int *)arg; cpu_set_t mask; struct timespec ts[2]; int num = 0; void *ptr[FREE_CYCLE]; CPU_ZERO(&mask); CPU_SET(0, &mask); if (sched_setaffinity(0, sizeof(mask), &mask) < 0) { t_error("Set CPU affinity of thread %d failure, ERROR:%s\n", *val, strerror(errno)); return NULL; } for (int i = 0; i < ITER_TIME; ++i) { for (size_t size = 0; size < THRESHOLD; size += SIZE_ALIGN + 1) { if (num == FREE_CYCLE) { free_all(ptr); num = 0; } ptr[num] = malloc(size); if (!ptr[num]) { t_error("Thread %d malloc failed for size %u\n", *val, size); *val = errno; return NULL; } num++; } } *val = 0; return NULL; } int main(int argc, char *argv[]) { struct timespec ts[2]; pthread_attr_t attr; pthread_t tids[THREAD_MAX_N]; int t_result[THREAD_MAX_N] = {0}; int flag = 0; int ret; int i; ret = pthread_attr_init(&attr); if (ret < 0) { t_error("Init pthread attribute failed: %s\n", strerror(errno)); return -1; } clock_gettime(CLOCK_REALTIME, ts); for (i = 0; i < THREAD_MAX_N; ++i) { t_result[i] = i; ret = pthread_create(&tids[i], &attr, func, &t_result[i]); if (ret < 0) { t_error("Create pthread %u failed: %s\n", i, strerror(errno)); flag = -1; break; } } for (i = 0; i < THREAD_MAX_N; ++i) { ret = pthread_join(tids[i], NULL); if (ret < 0) { t_error("Join thread %u failed: %s\n", i, strerror(errno)); } } clock_gettime(CLOCK_REALTIME, ts + 1); (void)pthread_attr_destroy(&attr); double cost = (ts[1].tv_sec - ts[0].tv_sec) * NANOSEC_PER_SEC + (ts[1].tv_nsec - ts[0].tv_nsec); if (!flag) { t_printf("Malloc and free %d threads %d times cost %lf s\n", THREAD_MAX_N, MALLOC_TIME, cost / NANOSEC_PER_SEC); t_status = 0; } return t_status; } 在鸿蒙开发者手机 4.1版本中 使用的时5.15.74版本linux内核,在跑上述的单核cpu多线程malloc和free时,出现了前面所述的几种内核崩溃类型,在最新linux5.15.y版本中是否有相应的解决提交记录
07-20
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值