lp:~guoqingjiang/ubuntu/+source/linux-mtk/+git/jammy

Owned by GuoqingJiang
Get this repository:
git clone https://git.launchpad.net/~guoqingjiang/ubuntu/+source/linux-mtk/+git/jammy
Only GuoqingJiang can upload to this repository. If you are GuoqingJiang please log in for upload directions.

Branches

Name Last Modified Last Commit
gjiang-next 2024-06-04 05:54:26 UTC
UBUNTU: SAUCE: (no-up) apusys: sw_logger: Check dma addr in sw_logger_remove

Author: GuoqingJiang
Author Date: 2024-06-04 05:06:46 UTC

UBUNTU: SAUCE: (no-up) apusys: sw_logger: Check dma addr in sw_logger_remove

BugLink: https://bugs.launchpad.net/bugs/2067439

In case platform_load_apusys_rv failed to load firmware, then the path
would not be triggered, which means 'handle' (dma address) is not set.

apu_probe -> apu_config_setup -> sw_logger_config_init -> sw_logger_buf_alloc

But in sw_logger_remove, dma_unmap_single or dma_free_coherent is called
unconditionally, which causes the trace.

[ 423.296113] WARNING: CPU: 4 PID: 1270 at drivers/iommu/dma-iommu.c:859 iommu_dma_unmap_page+0xc4/0xe0
...
[ 423.296322] Call trace:
[ 423.296324] iommu_dma_unmap_page+0xc4/0xe0
[ 423.296327] dma_unmap_page_attrs+0x38/0x1d0
[ 423.296332] sw_logger_remove+0x78/0x9c [apusys]
[ 423.296401] platform_remove+0x5c/0x74
[ 423.296406] __device_release_driver+0x19c/0x280
[ 423.296410] driver_detach+0x12c/0x17c
[ 423.296413] bus_remove_driver+0x74/0x130
[ 423.296416] driver_unregister+0x38/0x70
[ 423.296419] platform_driver_unregister+0x1c/0x30
[ 423.296423] sw_logger_exit+0x30/0xa0 [apusys]
[ 423.296470] apusys_exit+0x74/0xa0 [apusys]

Signed-off-by: Guoqing Jiang <guoqing.jiang@canonical.com>

master-next 2024-03-14 09:39:37 UTC
UBUNTU: Ubuntu-mtk-5.15.0-1030.35

Author: Jian Hui Lee
Author Date: 2024-03-14 09:39:37 UTC

UBUNTU: Ubuntu-mtk-5.15.0-1030.35

Signed-off-by: Jian Hui Lee <jianhui.lee@canonical.com>

12 of 2 results
This repository contains Public information 
Everyone can see this information.

Subscribers