Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Trogdor: memory overlap in dts #105

Closed
r-c-n opened this issue Mar 8, 2022 · 1 comment
Closed

Trogdor: memory overlap in dts #105

r-c-n opened this issue Mar 8, 2022 · 1 comment

Comments

@r-c-n
Copy link

r-c-n commented Mar 8, 2022

Warning seen in some kernelci jobs:

Kernel versions: v5.17-rc2 and v5.17-rc3

  [    0.000000] OF: reserved mem: OVERLAP DETECTED!
  [    0.000000] memory@86000000 (0x0000000086000000--0x000000008ec00000) overlaps with memory@8b700000 (0x000000008b700000--0x000000008b710000)
  [    0.000000] earlycon: qcom_geni0 at MMIO 0x0000000000a88000 (options '115200n8')
  [    0.000000] ------------[ cut here ]------------
  [    0.000000] console 'qcom_geni0' already registered
  [    0.000000] WARNING: CPU: 0 PID: 0 at kernel/printk/printk.c:2953 register_console+0x58/0x2a4
  [    0.000000] Modules linked in:
  [    0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted 5.17.0-rc2 #1
  [    0.000000] Hardware name: Google Lazor Limozeen without Touchscreen (rev5 - rev8) (DT)

Preliminary investigation:

sc7180-trogdor.dtsi (included: sc7180-trogdor-lazo-limozeen-nots-r5.dts -> sc7180-trogdor-lazor.dtsi) defines a memory region mpss_mem:

	reserved-memory {
		...

		mpss_mem: memory@86000000 {
			reg = <0x0 0x86000000 0x0 0x2000000>;
			no-map;
		};

that goes from 0x86000000 to 0x88000000. This is later overriden in sc7180-trogdor-lte-sku.dtsi:

&mpss_mem {
	reg = <0x0 0x86000000 0x0 0x8c00000>;
};

and now that region (0x86000000 - 0x8ec00000) overlaps the ipa_fw_mem reserved memory region defined in sc7180.dtsi.

@padovan
Copy link
Contributor

padovan commented Jul 9, 2024

Old issue. (also we are not tracking kernel test failure/issues through GitHub anymore)

@padovan padovan closed this as completed Jul 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants