[fedora-arm] Kernel panic attempting to run Fedora 13 beta in beagleboard xm

[Gordan Bobic]

Ismael Schinca wrote:
> Hello everyone, I tried installing the Fedora 13 beta in the Beagleboard 
> xm board using these instructions:
> 
> http://fedoraproject.org/wiki/Architectures/ARM/BeagleBoardxMSDCard
> 
> with the latest kernel and modules from:
> 
> http://www.angstrom-distribution.org/demo/beagleboard/
> 
> The board boots but I receive the following kernel panic during start up:
> 
> Kernel panic - not syncing: Attempted to kill init!
> 
> 
> Here's the last few output lines from the serial port before this message:
> 
> 
> [ 14.928527] Console: switching to colour frame buffer device 80x30
> 
> [ 14.951416] regulator_init_complete: incomplete constraint
> 
> s, leaving VAUX3 on
> 
> [ 14.958923] regulator_init_complete: incomplete constraints, leaving 
> VDAC on
> 
> [ 14.966552] omap_vout omap_vout: probed for an unknown device
> 
> [ 14.972839] Waiting for root device /dev/mmcblk0p2...
> 
> [ 14.978485] usb 2-2: New USB device found, idVendor=0424, idProduct=9514
> 
> [ 14.986145] usb 2-2: New USB device strings: Mfr=0, Product=0, 
> SerialNumber=0
> 
> [ 14.995910] hub 2-2:1.0: USB hub found
> 
> [ 14.999847] hub 2-2:1.0: 5 ports detected
> 
> [ 15.086975] mmc0: new high speed SDHC card at address 1234
> 
> [ 15.092926] mmcblk0: mmc0:1234 SA04G 3.67 GiB
> 
> [ 15.097778] mmcblk0: p1 p2
> 
> [ 15.203521] kjournald starting. Commit interval 5 seconds
> 
> [ 15.213500] EXT3-fs (mmcblk0p2): using internal journal
> 
> [ 15.218811] EXT3-fs (mmcblk0p2): recovery complete
> 
> [ 15.223724] EXT3-fs (mmcblk0p2): mounted filesystem with writeback data 
> mode
> 
> [ 15.230926] VFS: Mounted root (ext3 filesystem) on device 179:2.
> 
> [ 15.241882] devtmpfs: mounted
> 
> [ 15.244964] Freeing init memory: 204K
> 
> [ 15.288787] Kernel panic - not syncing: Attempted to kill init!
> 
> 
> Please let me know if you have any suggestions or need any additional 
> information.

Trying a few different kernels would probably be a good start. It could 
just be a broken kernel. You might also have a broken/corrupted/missing 
init, but I would expect a more explicit error with words to that effect 
if that was happening. Have you tried booting the kernel with 
init=/bin/bash?

Gordan