[Solved] Beaglebone Black can't execute init from eMMC

This forum is for supported devices using an ARMv7 Texas Instruments (TI) SoC.

[Solved] Beaglebone Black can't execute init from eMMC

Postby OldSalt » Tue Nov 03, 2015 6:49 am

Following the procedures for installing on the BBB I get a properly functions SD card. Installing to the eMMC, the board boots and loads the kernel but then fails to execute the init (systemd?) with the following message:
$this->bbcode_second_pass_code('', '[ 4.819475] EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: (null)
[ 4.827679] VFS: Mounted root (ext4 filesystem) on device 179:1.
[ 4.835902] devtmpfs: mounted
[ 4.839639] Freeing unused kernel memory: 588K (c0cab000 - c0d3e000)
[ 4.930621] Starting init: /sbin/init exists but couldn't execute it (error -8)
[ 4.940145] Starting init: /bin/init exists but couldn't execute it (error -8)
[ 4.970340] Starting init: /bin/sh exists but couldn't execute it (error -8)
[ 4.977519] Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.
[ 4.990708] CPU: 0 PID: 1 Comm: swapper Not tainted 4.2.2-1-ARCH #1
[ 4.996997] Hardware name: Generic AM33XX (Flattened Device Tree)
[ 5.003164] [<c001704c>] (unwind_backtrace) from [<c0014224>] (show_stack+0x20/0x24)
[ 5.010955] [<c0014224>] (show_stack) from [<c08b5878>] (dump_stack+0x24/0x28)
[ 5.018214] [<c08b5878>] (dump_stack) from [<c08b2f14>] (panic+0x98/0x21c)
[ 5.025121] [<c08b2f14>] (panic) from [<c08b2354>] (__irq_alloc_descs+0x0/0x1e4)
[ 5.032556] ---[ end Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.
')
Booting from the SD card again, I mounted the eMMC and checked the file system. The /sbin/init is a soft link to /lib/systemd/systemd and permissions seem fine. The systemd file is an ARM executable so I'm a bit stumped as to why it won't execute.

Anyone have an idea what's up?

Thanks,
Last edited by OldSalt on Tue Nov 03, 2015 10:16 pm, edited 1 time in total.
OldSalt
 
Posts: 4
Joined: Mon Nov 02, 2015 4:15 am

Re: Beaglebone Black can't execute init from eMMC

Postby WarheadsSE » Tue Nov 03, 2015 3:38 pm

Boot from the SD and verify that the binaries match sha1sums, it is possible there is some issue with the eMMC and the initial write. If this is the case, we have a solution here in the forums via sysctl.
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: Beaglebone Black can't execute init from eMMC

Postby OldSalt » Tue Nov 03, 2015 7:39 pm

My SD card packages were updated so I started with a new SD and re-installed. Symptoms are the same. Here are the sha1 checksums on the two systemd executables.
$this->bbcode_second_pass_code('', '
[root@alarm alarm]# sha1sum /lib/systemd/systemd mnt/lib/systemd/systemd
c8b06b2340702cbb936131e4d91cb2ca158522d4 /lib/systemd/systemd
c8b06b2340702cbb936131e4d91cb2ca158522d4 mnt/lib/systemd/systemd
[root@alarm alarm]#')
I'll go back and compare the console logs from the successful and unsuccessful boots and see if there are any more clues to be found. Any other tips would be appreciated.
OldSalt
 
Posts: 4
Joined: Mon Nov 02, 2015 4:15 am

Re: Beaglebone Black can't execute init from eMMC

Postby OldSalt » Tue Nov 03, 2015 8:13 pm

So, a couple more data points:
1. When booting from eMMC, console log shows "Card did not respond to voltage select!" early in the boot process. I think this may be a normal part of the drivers sorting out if they are dealing with an SD card or eMMC so may be nothing.
2. Running e2fsck on the eMMC partition showed the free blocks and free inodes count to be zeros rather than the counted values. These were fixed and a second boot and check showed no errors. Unfortunately, the kernel panic still happens.
OldSalt
 
Posts: 4
Joined: Mon Nov 02, 2015 4:15 am

[Solved] Beaglebone Black can't execute init from eMMC

Postby OldSalt » Tue Nov 03, 2015 10:15 pm

It turns out that many of the libraries in /lib and /usr/lib were hosed. I chased down the sysctl solution and extracted the files again which seems to have given valid files.
$this->bbcode_second_pass_code('', 'sysctl -w vm.min_free_kbytes=16384')
This should probably be added to the steps on the BBB installation page.
My thanks to WarheadsSE for the pointer.
OldSalt
 
Posts: 4
Joined: Mon Nov 02, 2015 4:15 am


Return to Texas Instruments (TI)

Who is online

Users browsing this forum: No registered users and 1 guest