PD#SWPL-208253
Problem:
can't patch to kernel for google
Solution:
modify in common_drivers
Verify:
SC2
Test:
boot and play video
Change-Id: If7adf4b52c10ec259f6ce4549f31b215895c828e
Signed-off-by: biao.sun <biao.sun@amlogic.com>
PD#SWPL-192100
Problem:
The 32-bit kernel cannot use the ramdump function.
Because the .text section is typically at 0x00108000,
which will be overwritten by the BL2E/BL33 after
reboot. And the PC side is unable to parse it.
Solution:
1. After kernel panic, use DMA to copy the 0-24MB
region to the 0x09000000 area.
2. Reboot to bl33z, fill compress_section[1] with
the 0x09000000 region.
3. Analyze it using the same method as before.
Verify:
sc2
Change-Id: I3e22beb06321289c6643d3f05ec2d910d5ce0beb
Signed-off-by: dongqing.li <dongqing.li@amlogic.com>
PD#SWPL-195943
Problem:
When analyzing a crash, parameters such as --kaslr
and --kimage_voffset are required, but obtaining
these parameters is challenging.
Solution:
1.Add global string that contains parameter infor
such as kaslr, kimage_voffset, and others.
2.Get parameter: strings DUMP | grep aml_ramdump
Verify:
sc2_ah212
Change-Id: I5847dab4f4f2b09b9fb922ca2f456fee1e59147c
Signed-off-by: dongqing.li <dongqing.li@amlogic.com>
PD#SWPL-191355
Problem:
For the low_mem project, the ramdump driver is
built-in. If many kernel configs are removed
during kernel size trimming, it may lead to build
errors in ramdump parsing info.
The removed configs info can be found in CL 486868.
Solution:
Romove parse info of kimage_voffset when ramdump
drv is built-in.
Verify:
sc2
Change-Id: I36b533bd06e56ca66b87850d01c0b0ad57c3a73c
Signed-off-by: dongqing.li <dongqing.li@amlogic.com>
PD#SWPL-188348
Problem:
ker6.12 souce code is old. And ramdump
is not working properly.
Solution:
1. sync ramdump.c from ker5.15.
2. enable CONFIG_AMLOGIC_RAMDUMP
3. modify TEXTOFFSET=0X0200800 for ker 32bit
Verify:
SC2_AH212
Change-Id: Id19ba0ef1302e9cf4cdf379d10c625519a8eef36
Signed-off-by: dongqing.li <dongqing.li@amlogic.com>
PD#SWPL-160377
Problem:
need to support ramdump of sc2/sm1
Solution:
porting from ker5.15.
Verify:
ah212
Change-Id: I118c9409eb3d4b2dd87d859760b5bb4138091ee6
Signed-off-by: dongqing.li <dongqing.li@amlogic.com>
PD#SWPL-132538
Problem:
The core-dump file cannot be saved to /data in Android.
Solution:
a. Fix BUG for bad page state when lazy_clear_work is running.
b. Print the parameter infor required for the crash tools.
c. Support for storing crashdump files in Android /data/vender/ramdump/
1) When a kernel panic occurs, flush cache all.
2) Restart to uboot stage and compress the full DDR.
3) Set kernel dts rsv mem based on compressed infor.
4) Crop reserved memory sub nodes to reduce mem usage.
5) Kernel stage parsing dts to configure rsv mem.
6) Android init.rc read sysnode, and generate crash file.
Verify:
sc2_ah212
Change-Id: Ic6fba2c305f9e3171445f3b89afa02c75c27a080
Signed-off-by: dongqing.li <dongqing.li@amlogic.com>
PD#SWPL-137107
Problem:
The data in the ramdump crash file is abnormal
because the cache data has not been flushed back.
Solution:
1. Use ipi_stop hook to flush online cpu cache.
2. Use panic_notifier to flush panic cpu cache.
Verify:
sc2_ah212
Change-Id: Ifad5bd4203fdde327b8c2b19357aa2d92586063f
Signed-off-by: dongqing.li <dongqing.li@amlogic.com>
yao zhang1