Accumulation of problems in embedded Linux startup process--ebai problem of supplementing kernel panic __linux

Accumulation of problems in embedded Linux startup process

Bowen Original Address: http://blog.csdn.net/dzassn/article/details/1953993

1.Bad Magic Number

# # Booting image at 33000000
... Bad Magic number
OMAP5912 OSK # (TFTP download good kernel uimage after stop here, can't start kernel)

Problem reason: The startup parameter is set incorrectly and 0x30000000 cannot be performed.

Some Development Board SDRAM is not in 0x33000000, so can not kernel uimage download to 0x33000000 run. As my previous bootcmd parameters are: setenv bootcmd tftpboot 33000000 uimage/; Bootm 33000000. But the SDRAM address of board Omap5912 is 0x100000000, the parameter is changed to setenv bootcmd tftpboot 10000000; BOOTM can start kernel after 10000000.

2. Start stop in "Starting kernel ..."

TFTP from server 192.168.167.170; Our IP address is 192.168.167.15
Filename ' uimage '
Load address:0x10000000
Loading: ##################### ############################################
         ############################################################## ###
done
Bytes transferred = 2025908 (1ee9b4 hex)
booting image at 10000000 ...
Image Name:   linux-2.6.18-mh8_pro500-versatil
image Type:   ARM Linux Kernel image (uncompressed)
Data Size:    2025844 Bytes =  1.9 MB
Load address:30008000
Entry point:  30008000
Verifying Checksum ... Ok
OK
starting kernel   ... (Stuck here)

Problem reason: Most of kernel did not compile successfully.

Verify that the Configure parameters are configured correctly and that the correct target compilation platform, such as smdk2410, is selected.

3. Cannot start kernel

Starting kernel
... Uncompressing Linux ... ...... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ....
... ... ... done, booting the kernel, and so on ... done, and the.

Problem reason: May be bootargs parameter setting error, confirm Bootargs setting is correct.

4. Cannot mount NFS

Eth0:link up
ip-config:complete:
     device=eth0, addr=192.168.167.15, mask=255.255.255.0, gw=192.168.167.254,
     host=192.168.167.15, domain=, nis-domain= (none),
     bootserver=192.168.167.170, rootserver=192.168.167.170,  Rootpath=
looking up port of RPC 100003/2 in 192.168.167.170
root-nfs:unable to get NFSD port number from server, Using default
looking up port of RPC 100005/1 in 192.168.167.170
root-nfs:unable to get mountd port number from Server, using default
mount:server 192.168.167.170 not responding, timed out
Root-nfs:server returned error-5 W Hile mounting/work/nfs/rootfs_bluetooth_omap
vfs:unable to mount Root FS via NFS, trying floppy.
Vfs:cannot Open Root Device "NFS" or Unknown-block (2,0) Please
append a correct "root=" boot option
Kernel C-not syncing:VFS:Unable to Mount Root fs on Unknown-block (2,0)

Problem reason: This situation is typically an NFS configuration issue.

Confirm that the IP address information for NFS is set correctly in the Uboot Bootargs parameter and that the host machine/etc/exports configured properly, resets the NFS service, and tries the connection again. Also note the settings for the console and mem two parameters within the Bootargs. kernel2.6 after the console is best set to Ttysac0,mem also according to the actual situation of the Development Board set correctly.

5. File system does not boot problem

Eth0:link up
ip-config:complete:
      device=eth0, addr=192.168.167.15, mask=255.255.255.0, gw=192.168.167.254,
     host=192.168.167.15, domain=, nis-domain= (none),
     bootserver=192.168.167.170, rootserver=192.168.167.170, Rootpath=
looking up port ' RPC 100003/2 on 192.168.167.170
looking ' up port ' RPC 100005/1 on 192.168.167.170
  vfs:mounted Root (NFS filesystem).
Freeing init memory:128k
/sbin/initkernel panic-not syncing:attempted to kill init!

Problem reason: The production of the file system is missing the need to run BusyBox libcrypt.so Library, the new version of the library will be short notice, the old edition (1.60) did not.

Note: Running a BusyBox file system requires at least several libraries as follows:

Ld-linux.so.x

Libc.so.6

Libcrypt.so.x

Newer versions of BusyBox may also require

Libm.so.6

Libgcc_s.so.x

(x is version number)

6. File system does not boot issue 2

Eth0:link up
ip-config:complete:
     device=eth0, addr=192.168.167.15, mask=255.255.255.0, gw=192.168.167.254,
     host=192.168.167.15, domain=, nis-domain= (none),
     bootserver=192.168.167.170, rootserver=192.168.167.170, Rootpath=
looking up port ' RPC 100003/2 on 192.168.167.170
looking ' up port ' RPC 100005/1 on 192.168.167.170
  vfs:mounted Root (NFS filesystem).
Freeing init memory:128k
Kernel panic-not syncing:no init found.  Try passing init= option to kernel.

Problem reason 1: Compared to an available file system found that the lack of ld-linux.so.x library, the file system only ld-linux.so.x connection files, less copy the library file.

Problem Reason 2: The compiler used is 4.3.x, but the kernel did not add support for Ebai.

Solution:

Modify Kernel Features--->
[*] Use the ARM Eabi to compile the kernel
[*] Allow old ABI binaries to run with this kernel (Experimenta)
Put this on the election.

Problem reason 3:nand The ECC check problem when Flash starts.

Solution:

Modify Device Drivers--->

[*] Memory Technology Device (MTD) Support--->
[*] NAND Device Support--->

[*] s3c2410 NAND Hardware ECC
8. Cannot get account UID information

Could not get password database information for UID of current Process:user '??? ' Unknown or no memory to allocate
PA  ssWOrd entry
Unknown username "root" in message bus configuration file
could don't get password database information For UID of the current Process:user "???" Unknown or no memory to allocate password entry-
start message bu S:could not get UID and GID for username "root"

Problem Reason:

Situation one: There is a problem with the system account validation. It is suspected that the call to Getuid, GetGuid did not return the correct value, may be the lack of account validation related libraries, after the actual investigation found that the lack of libnss_files library. After copying the Libnss_files library of the cross compiler to the file system, the boot file system succeeded.

Situation Two: The system does not have a root account. Can be seen by the WhoAmI command.

Create an account manually.

#vi/etc/passwd
root:x:0:0:root:/root:/bin/sh
Kyo:x:500:500:kyo:/home/kyo:/bin/bash

Add a group

#vi Group
Root:x:0:root

9.

Freeing init memory:128k
init started:busybox v1.6.1 (2007-08-27 14:33:15 CST) multi-call binary starting
PID 83 4, TTY ': '/etc/init.d/rcs '
cannot run '/etc/init.d/rcs ': No such file or directory

found that no/etc/init.d/rcs file system can start as normal. It seems that the RCS is only used to set some random boot parameters, and the file can not be normal operation.

Note: This is not a mistake, is found by accident! :)

10.

During the Linux kernel boot process, the character driver written by itself prompts Lp:driver loaded but no devices found when the device node is created.

At present, this problem has not found a specific reason, which I use the YAFFS2 file system to prompt this error, the current preliminary determination is in the process of configuring the kernel, the specific reason for the analysis ...