Boot

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Boot

2,277 Views
peterhygren
Contributor III

Trying to boot on our custom board with IMX6D, this error comes up, and the boot hangs:

Unable to handle kernel NULL pointer dereference at virtual address 00000000

pgd = 80004000

[00000000] *pgd=00000000

Internal error: Oops: 5 [#1] PREEMPT SMP

Modules linked in:

CPU: 1    Not tainted  (3.0.35-1.1.0+yocto+gc27cb38 #1)

PC is at _clk_pll2_main_get_rate+0x38/0x3c

LR is at clk_get_rate+0x34/0x44

pc : [<80058508>]    lr : [<80061a4c>]    psr: a0000093

sp : bfa71e80  ip : 00000080  fp : 80aa7ab0

r10: 60000013  r9 : 80aa7ab0  r8 : 3b5dc100

r7 : 80aa5ab8  r6 : 80aeda88  r5 : 3b5dc100  r4 : 00000001

r3 : 00000016  r2 : 3b5dc0ff  r1 : 3b5dc100  r0 : 1f78a400

Flags: NzCv  IRQs off  FIQs on  Mode SVC_32  ISA ARM  Segment kernel

Control: 10c53c7d  Table: 1000404a  DAC: 00000015

Process kinteractiveup (pid: 59, stack limit = 0xbfa702f0)

Stack: (0xbfa71e80 to 0xbfa72000)

1e80: 800584d0 80061a4c 80aa5b0c 80055284 00018d00 80061a4c f40c4000 80054308

1ea0: 00018d00 80061a4c f40c4000 80054404 00000001 80061a4c 00000000 80056360

1ec0: 80056278 80aa7cf0 3b5dc100 80aedd18 001312d0 001312d0 0011edd8 001312d0

1ee0: 80aeda48 80061b48 ffffffff 3b5dc100 179a7b00 800647f4 0011edd8 000e7ef0

1f00: 800561a0 80aeda44 00000002 00000002 00000002 bfa71f50 80a9fac4 bfe69300

1f20: 80aedd18 8050e3f8 3b5dc100 80064bc8 bfa71f4c 00000000 bfa70000 00000000

1f40: bfa71f74 80039f40 80039f40 00000000 00000001 00060ae0 000f32a0 bff8bf01

1f60: 00000000 80a9fabc 80b0fbd8 80a9fb00 80a9fcc8 8050e3f4 80a9fabc 000f32a0

1f80: 00000000 8037078c bfa70000 8037510c 8c008d90 80039d90 80039d90 00000000

1fa0: bfa71fc4 bff8bf34 00000000 80374f9c 00000013 00000000 00000000 00000000

1fc0: 00000000 8008d97c 80041bfc 00000000 00000000 00000000 00000000 00000000

1fe0: bfa71fe0 bfa71fe0 bff8bf34 8008d8fc 80041bfc 80041bfc 19095f23 eeb4583e

[<80058508>] (_clk_pll2_main_get_rate+0x38/0x3c) from [<80061a4c>] (clk_get_rate+0x34/0x44)

[<80061a4c>] (clk_get_rate+0x34/0x44) from [<80055284>] (_clk_periph_get_rate+0x28/0x54)

[<80055284>] (_clk_periph_get_rate+0x28/0x54) from [<80061a4c>] (clk_get_rate+0x34/0x44)

[<80061a4c>] (clk_get_rate+0x34/0x44) from [<80054308>] (_clk_ahb_get_rate+0x18/0x28)

[<80054308>] (_clk_ahb_get_rate+0x18/0x28) from [<80061a4c>] (clk_get_rate+0x34/0x44)

[<80061a4c>] (clk_get_rate+0x34/0x44) from [<80054404>] (_clk_ipg_get_rate+0x18/0x28)

[<80054404>] (_clk_ipg_get_rate+0x18/0x28) from [<80061a4c>] (clk_get_rate+0x34/0x44)

[<80061a4c>] (clk_get_rate+0x34/0x44) from [<80056360>] (_clk_arm_set_rate+0xe8/0x328)

[<80056360>] (_clk_arm_set_rate+0xe8/0x328) from [<80061b48>] (clk_set_rate+0x44/0x68)

[<80061b48>] (clk_set_rate+0x44/0x68) from [<800647f4>] (set_cpu_freq+0x130/0x3ac)

[<800647f4>] (set_cpu_freq+0x130/0x3ac) from [<80064bc8>] (mxc_set_target+0x10c/0x2b8)

[<80064bc8>] (mxc_set_target+0x10c/0x2b8) from [<8037078c>] (__cpufreq_driver_target+0x4c/0x60)

[<8037078c>] (__cpufreq_driver_target+0x4c/0x60) from [<8037510c>] (cpufreq_interactive_up_task+0x170/0x1b0)

[<8037510c>] (cpufreq_interactive_up_task+0x170/0x1b0) from [<8008d97c>] (kthread+0x80/0x88)

[<8008d97c>] (kthread+0x80/0x88) from [<80041bfc>] (kernel_thread_exit+0x0/0x8)

Code: e8bd8008 eb002545 e3a03016 e0000093 (e8bd8008)

---[ end trace ba5e1069a76348dc ]---

note: kinteractiveup[59] exited with preempt_count 1

Does anyone know what might be causing this? Very thankful for any help.

Best Regards,

Peter Hygren

Labels (2)
Tags (3)
0 Kudos
6 Replies

1,180 Views
patricesarrasin
Contributor III

Hi, for me everything seems to work with the latest kernel...

0 Kudos

1,180 Views
peterhygren
Contributor III

Hi!

That's great Patrice, thanks for letting us know, we'll probably try the latest kernel too.

0 Kudos

1,180 Views
patricesarrasin
Contributor III

Hi, I got the same kind of problem with kernel 3.0.35 build with yocto. By disabling the power management in the kernel, I was able to boot the board correctly. It's a workaround... I did not find the root cause yet.

Let me know if you find anything

Thanks

1,180 Views
AlanZhang
Contributor V

Hi, Peter,

This exception failure occur when uboot load kernel. It seems that your uImage or your uboot env loadaddr is wrong. How did you generate the uImage? Meanwhile, pls check the power supplies like core and ddr supplies!

Regards,

Alan Zhang

0 Kudos

1,180 Views
peterhygren
Contributor III

Hi Alan,

Thanks for responding.

Please look at this thread, where the entire boot log is attached.

IMX6D boot error, log attached, please help

The uImage was created with the Yocto build script described on this page:

How to Test Yocto for i.MX6

I've checked the core and power supplies, they all seem ok, will respond in the other thread with all the actual values.

/Peter

0 Kudos

1,180 Views
AlanZhang
Contributor V

Hi, Peter,

Sorry for late reponse! I tried on LTIB release downloaded from www.freescale.com, it is ok. So I  will try on Yocto release. If you are available, you could double check w/ LTIB releaes.

Regards,

Alan Zhang

0 Kudos