Have you tried booting with the most recent Debian IoT image? If this works then you can eliminate hardware problems. Is there a reason you want to use a 4 year old kernel?
On Friday, December 22, 2017 at 9:50:24 AM UTC-6, vinker vinker wrote: > > Hi， > I got a BBB a few days ago. It has a XAM3359 MPU. It can't boot > from emmc, so I tried to boot it from SD card. However， everytime it > stopped at the same place with the same log. > The image version > is Angstrom-Cloud9-IDE-GNOME-eglibc-ipk-v2012.12-beaglebone-2013.06.20.img. > The follow is the booting message: > > Uncompressing Linux... done, booting the kernel. > [ 0.230005] omap2_mbox_probe: platform not supported > [ 0.243435] tps65217-bl tps65217-bl: no platform data provided > [ 0.328978] bone-capemgr bone_capemgr.8: slot #0: No cape found > [ 0.368036] bone-capemgr bone_capemgr.8: slot #1: No cape found > [ 0.407097] bone-capemgr bone_capemgr.8: slot #2: No cape found > [ 0.446160] bone-capemgr bone_capemgr.8: slot #3: No cape found > [ 0.471219] bone-capemgr bone_capemgr.8: slot #6: BB-BONELT-HDMIN > conflict P8.45 (#5:BB-BONELT-HDMI) > [ 0.483286] bone-capemgr bone_capemgr.8: slot #6: Failed verification > [ 0.491777] bone-capemgr bone_capemgr.8: loader: failed to load slot-6 > BB-BONELT-HDMIN:00A0 (prio 2) > [ 0.520132] omap_hsmmc mmc.4: of_parse_phandle_with_args of 'reset' > failed > [ 0.587312] pinctrl-single 44e10800.pinmux: pin 44e10854 already > requested by 44e10800.pinmux; cannot claim for gpio-leds.7 > [ 0.601997] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.7) status > -22 > [ 0.611188] pinctrl-single 44e10800.pinmux: could not request pin 21 on > device pinctrl-single > [ 11.042147] Unable to handle kernel paging request at virtual address > 004de000 > [ 11.051620] pgd = df580000 > [ 11.055151] [004de000] *pgd=00000000 > [ 11.059825] Internal error: Oops: 5 [#1] SMP THUMB2 > [ 11.066157] Modules linked in: autofs4 > [ 11.071036] CPU: 0 Not tainted (3.8.13 #1) > [ 11.076824] PC is at lg_local_lock_cpu+0xa/0x38 > [ 11.082709] LR is at file_sb_list_del+0x13/0x30 > [ 11.088591] pc : [<c004193a>] lr : [<c0095217>] psr: 00000033 > [ 11.088591] sp : df051f78 ip : 50c5387d fp : 000db9c0 > [ 11.103500] r10: 00000000 r9 : df050000 r8 : c000c7e4 > [ 11.110283] r7 : 00000006 r6 : df04cac0 r5 : df050000 r4 : df5ca6c0 > [ 11.118757] r3 : 004de000 r2 : 004de000 r1 : 00000000 r0 : c065a4e4 > [ 11.127233] Flags: nzcv IRQs on FIQs on Mode SVC_32 ISA Thumb > Segment user > [ 11.136722] Control: 50c5387d Table: 9f580019 DAC: 00000015 > [ 11.144182] Process systemd (pid: 1, stack limit = 0xdf050240) > [ 11.151754] Stack: (0xdf051f78 to 0xdf052000) > [ 11.157545] 1f60: > df5ca6c0 c0095313 > [ 11.168205] 1f80: df5ca6c0 00000000 df04fe80 c0092ebb ffffffff 00000000 > 000f88a8 c0092e5b > [ 11.178854] 1fa0: b6dd3450 c000c641 ffffffff 00000000 0000000b 00000000 > 0000003c b6dd3450 > [ 11.189500] 1fc0: ffffffff 00000000 000f88a8 00000006 000cd980 000f85d0 > 000f6550 000db9c0 > [ 11.200145] 1fe0: 00000000 bea357b4 b6dd46ac b6dd3460 600f0010 0000000b > de7d76df 1b9f2915 > [ 11.210807] [<c004193a>] (lg_local_lock_cpu+0xa/0x38) from [<c0095217>] > (file_sb_list_del+0x13/0x30) > [ 11.222698] [<c0095217>] (file_sb_list_del+0x13/0x30) from [<c0095313>] > (fput+0x37/0x94) > [ 11.233243] [<c0095313>] (fput+0x37/0x94) from [<c0092ebb>] > (filp_close+0x3b/0x44) > [ 11.243102] [<c0092ebb>] (filp_close+0x3b/0x44) from [<c0092e5b>] > (sys_close+0x19/0x3e) > [ 11.253534] [<c0092e5b>] (sys_close+0x19/0x3e) from [<c000c641>] > (ret_fast_syscall+0x1/0x46) > [ 11.264539] Code: 6803 f852 2021 189b (e853) 1f00 > [ 11.270795] ---[ end trace 079fae02e79b2d40 ]--- > [ 11.277758] Kernel panic - not syncing: Attempted to kill init! > exitcode=0x0000000b > [ 11.277758] > [ 11.289629] drm_kms_helper: panic occurred, switching back to text > console > > I googled to find this may mean some hardware , but I'm not familiar with > TI processor. So I don't know which part of the board doesn't work. > I tried to boot another BBB board(a reduced version with AM3352 instead, > and without emmc and HDMI) , using the identical SD card with the same > image. And it boot successfully. > > Can anyone give me some advice on which part to check? Many thanks! > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/30f05eef-435f-42cd-aff3-15e4fd8fedf2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
