主题 : 2.6.31 kernel 上电后 停在小企鹅logo界面 进不了2.2的android系统 复制链接 | 浏览器收藏 | 打印
级别: 新手上路
UID: 33474
精华: 0
发帖: 11
金钱: 55 两
威望: 11 点
贡献值: 0 点
综合积分: 22 分
注册时间: 2010-12-01
最后登录: 2011-02-11
楼主  发表于: 2011-01-10 16:36

 2.6.31 kernel 上电后 停在小企鹅logo界面 进不了2.2的android系统

求救:
  出现  “Kernel panic - not syncing: Attempted to kill init!”
   百度说,配置
Kernel Features  --->
[*] Use the ARM EABI to compile the kernel                  
[*]   Allow old ABI binaries to run with this kernel (EXPERIMENTA)
配置后,仍然出现上述那句 panic
设置启动参数输入到串口,启动参数为:
“noinitrd console=ttymxc0,115200 root=ubi0:rootfs rootfstype=ubifs ubi.mtd=2 init=/init rw wvga"
内核的boot option 也是如上所设置!!
文件系统用mkfs.ubifs和ubinize工具的制作!!


启动后串口打印信息如下:
RedBoot> exec -c "noinitrd console=ttymxc0,115200 root=ubi0:rootfs rootfstype=ubifs ubi.mtd=2 init=/init rw wvga"
entry=0x90008000, target=0x90008000
Using base address 0x00100000 and length 0x0027ca14
Uncompressing Linux....................................................................................................................................................................... done, booting the kernel.

Linux version 2.6.31-506-g30df573 (root@lwj-desktop) (gcc version 4.1.2) #192 PREEMPT Mon Jan 10 15:21:22 CST 2011
CPU: ARMv7 Processor [412fc085] revision 5 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: Freescale MX51 3-Stack Board
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 109728

Kernel command line: noinitrd console=ttymxc0,115200 root=ubi0:rootfs rootfstype=ubifs ubi.mtd=2 init=/init rw wvga

PID hash table entries: 2048 (order: 11, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 432MB = 432MB total
Memory: 432444KB available (4692K code, 858K data, 148K init, 0K highmem)
SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:368
MXC IRQ initialized
MXC_Early serial console at MMIO 0x73fbc000 (options '115200')
console [ttymxc0] enabled
Console: colour dummy device 80x30
Calibrating delay loop... 799.53 BogoMIPS (lpj=3997696)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
regulator: core version 0.5
NET: Registered protocol family 16
i.MX IRAM pool: 128 KB@0xdb840000
IRAM READY
CPU is i.MX51 Revision 3.0
MXC GPIO hardware
Using SDMA I.API
MXC DMA API initialized
bio: create slab <bio-0> at 0
SCSI subsystem initialized
CSPI: mxc_spi-0 probed
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
MXC I2C driver
MXC I2C driver
IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)
Bluetooth: Core ver 2.15
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
mc13892 Rev 2.0 FinVer 2 detected
Initializing regulators for 3-stack.
regulator: SW1: 600 <--> 1375 mV
regulator: SW2: 900 <--> 1850 mV
regulator: SW3: 1100 <--> 1850 mV
regulator: SW4: 1100 <--> 1850 mV
regulator: SWBST: 0 mV
regulator: VIOHI: 0 mV
regulator: VPLL: 1050 <--> 1800 mV
regulator: VDIG: 1050 <--> 1800 mV
regulator: VSD: 1800 <--> 3150 mV
regulator: VUSB2: 2400 <--> 2775 mV
regulator: VVIDEO: 2500 <--> 2775 mV
regulator: VAUDIO: 2300 <--> 3000 mV
regulator: VCAM: 2500 <--> 3000 mV fast normal
regulator: VGEN1: 1200 <--> 3150 mV
regulator: VGEN2: 1200 <--> 3150 mV
regulator: VGEN3: 1800 <--> 2900 mV
regulator: VUSB: 0 mV
regulator: GPO1: 0 mV
regulator: GPO2: 0 mV
regulator: GPO3: 0 mV
regulator: GPO4: 0 mV
mc13892 0-0008: Loaded
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
NET: Registered protocol family 1
LPMode driver module loaded
Static Power Management for Freescale i.MX51
PM driver module loaded
sdram autogating driver module loaded
Bus freq driver module loaded
WVGA LCD is primary
mxc_dvfs_core_probe
DVFS driver module loaded
i.MXC CPU frequency driver
DVFS PER driver module loaded
ashmem: initialized
JFFS2 version 2.2. (NAND) (SUMMARY)  漏 2001-2006 Red Hat, Inc.
msgmni has been set to 844
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
mxc_ipu mxc_ipu: Channel already disabled 9
mxc_ipu mxc_ipu: Channel already uninitialized 9
Console: switching to colour frame buffer device 100x30
mxc_ipu mxc_ipu: Channel already disabled 7
mxc_ipu mxc_ipu: Channel already uninitialized 7
mxc_ipu mxc_ipu: Channel already disabled 10
mxc_ipu mxc_ipu: Channel already uninitialized 10
Serial: MXC Internal UART driver
mxcintuart.0: ttymxc0 at MMIO 0x73fbc000 (irq = 31) is a Freescale i.MX
console handover: boot [ttymxc0] -> real [ttymxc0]
mxcintuart.1: ttymxc1 at MMIO 0x73fc0000 (irq = 32) is a Freescale i.MX

mxcintuart.2: ttymxc2 at MMIO 0x7000c000 (irq = 33) is a Freescale i.MX

brd: module loaded

loop: module loaded

pmem_adsp: 1 init

pmem_gpu: 3 init

FEC ENET Version 0.2

FEC MAC Address(default): 0 80 3f c ff ff

fec: PHY @ 0x1f, ID 0x00008201 -- RTL8201CP

eth0: ethernet 00:80:3f:0c:ff:ff

PPP generic driver version 2.4.2

MXC MTD nand Driver 3.0

NAND device: Manufacturer ID: 0xec, Chip ID: 0xd7 (Samsung NAND 4GiB 3,3V 8-bit)

Bad block table not found for chip 0

RedBoot partition parsing not available

Creating 5 MTD partitions on "NAND 4GiB 3,3V 8-bit":

0x000000000000-0x000000300000 : "bootloader"

0x000000300000-0x000000800000 : "nand.kernel"

0x000000800000-0x000010800000 : "nand.rootfs"

0x000010800000-0x000020800000 : "nand.userfs1"

0x000020800000-0x000080000000 : "nand.userfs2"

UBI: attaching mtd2 to ubi0

UBI: physical eraseblock size:   524288 bytes (512 KiB)

UBI: logical eraseblock size:    516096 bytes

UBI: smallest flash I/O unit:    4096

UBI: VID header offset:          4096 (aligned 4096)

UBI: data offset:                8192

UBI: volume 0 ("rootfs") re-sized from 163 to 503 LEBs

UBI: attached mtd2 to ubi0

UBI: MTD device name:            "nand.rootfs"

UBI: MTD device size:            256 MiB

UBI: number of good PEBs:        512

UBI: number of bad PEBs:         0

UBI: max. allowed volumes:       128

UBI: wear-leveling threshold:    4096

UBI: number of internal volumes: 1

UBI: number of user volumes:     1

UBI: available PEBs:             0

UBI: total number of reserved PEBs: 512

UBI: number of PEBs reserved for bad PEB handling: 5

UBI: max/mean erase counter: 1/0

UBI: image sequence number: 0

ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver

UBI: background thread "ubi_bgt0d" started, PID 1070

fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller

fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1

fsl-ehci fsl-ehci.0: irq 18, io base 0x73f80000

fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00

usb usb1: configuration #1 chosen from 1 choice

hub 1-0:1.0: USB hub found

hub 1-0:1.0: 1 port detected


fsl-ehci fsl-ehci.1: Freescale On-Chip EHCI Host Controller

fsl-ehci fsl-ehci.1: new USB bus registered, assigned bus number 2

fsl-ehci fsl-ehci.1: irq 14, io base 0x73f80200

fsl-ehci fsl-ehci.1: USB 2.0 started, EHCI 1.00

usb usb2: configuration #1 chosen from 1 choice

hub 2-0:1.0: USB hub found

hub 2-0:1.0: 1 port detected


fsl-ehci fsl-ehci.2: Freescale On-Chip EHCI Host Controller

fsl-ehci fsl-ehci.2: new USB bus registered, assigned bus number 3

fsl-ehci fsl-ehci.2: irq 16, io base 0x73f80400

fsl-ehci fsl-ehci.2: USB 2.0 started, EHCI 1.00

usb usb3: configuration #1 chosen from 1 choice

hub 3-0:1.0: USB hub found

hub 3-0:1.0: 1 port detected

Initializing USB Mass Storage driver...

usbcore: registered new interface driver usb-storage

USB Mass Storage support registered.

mice: could not register psaux device, error: -16

mice: PS/2 mouse device common for all mice

MXC keypad loaded

clk: Unable to get requested clock: kpp_clk

input: mxckpd as /devices/virtual/input/input0

mc13892
rtc probe start

pmic_rtc pmic_rtc.1: rtc core: registered pmic_rtc as rtc0

mc13892 rtc probe succeed

i2c /dev entries driver

Linux video capture interface: v2.00

   Setting mclk to 27 MHz,csi=0

find the ov7725 camera.

sccb(i2c) register reset.

mxc_v4l2_output mxc_v4l2_output.0: Registered device video1

MXC WatchDog Driver 2.0

clk: Unable to get requested clock: wdog_clk

MXC Watchdog # 0 Timer: initial timeout 60 sec

device-mapper: uevent: version 1.0.3

device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-devel@redhat.com

Bluetooth: Virtual HCI driver ver 1.3

VPU initialized

mxsdhci: MXC Secure Digital Host Controller Interface driver

mxsdhci: MXC SDHCI Controller Driver.

mmc0: SDHCI detect irq 128 irq 1 INTERNAL DMA

mxsdhci: MXC SDHCI Controller Driver.

mmc1: SDHCI detect irq 136 irq 2 INTERNAL DMA

Registered led device: pmic_ledsr

Registered led device: pmic_ledsg

Registered led device: pmic_ledsb

usbcore: registered new interface driver usbhid

usbhid: v2.6:USB HID core driver


logger: created 64K log 'log_main'

logger: created 256K log 'log_events'

logger: created 64K log 'log_radio'

logger: created 64K log 'log_system'

Advanced Linux Sound Architecture Driver Version 1.0.20.

No device for DAI imx-ssi-1-0

No device for DAI imx-ssi-1-1

No device for DAI imx-ssi-2-0

No device for DAI imx-ssi-2-1

DMA Sound Buffers Allocated:UseIram=1 buf->addr=1fff6000 buf->area=db856000 size=24576

DMA Sound Buffers Allocated:UseIram=1 buf->addr=a93c0000 buf->area=fa066000 size=24576

asoc: WM8731 <-> imx-ssi-2-0 mapping ok

ALSA device list:

  #0: imx-3stack (WM8731)

TCP cubic registered

NET: Registered protocol family 10

IPv6 over IPv4 tunneling driver

NET: Registered protocol family 17

Bluetooth: L2CAP ver 2.13

Bluetooth: L2CAP socket layer initialized

Bluetooth: SCO (Voice Link) ver 0.6

Bluetooth: SCO socket layer initialized

Bluetooth: RFCOMM TTY layer initialized

Bluetooth: RFCOMM socket layer initialized

Bluetooth: RFCOMM ver 1.11

Bluetooth: BNEP (Ethernet Emulation) ver 1.3

Bluetooth: BNEP filters: protocol multicast

Bluetooth: HIDP (Human Interface Emulation) ver 1.2

RPC: Registered udp transport module.

RPC: Registered tcp transport module.

VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 2


regulator_init_complete: incomplete constraints, leaving GPO4 on

regulator_init_complete: incomplete constraints, leaving GPO3 on

regulator_init_complete: incomplete constraints, leaving GPO2 on

regulator_init_complete: incomplete constraints, leaving GPO1 on

regulator_init_complete: incomplete constraints, leaving VGEN3 on

regulator_init_complete: incomplete constraints, leaving VGEN2 on

regulator_init_complete: incomplete constraints, leaving VUSB2 on

regulator_init_complete: incomplete constraints, leaving VPLL on

regulator_init_complete: incomplete constraints, leaving VIOHI on

input: mxc_ts as /devices/virtual/input/input1

mxc input touchscreen loaded

mmc0: new high speed SD card at address 1234

mmcblk0: mmc0:1234 SD01G 972 MiB

mmcblk0: p1

pmic_rtc pmic_rtc.1: setting system clock to 1970-01-01 00:27:12 UTC (1632)


UBIFS: mounted UBI device 0, volume 0, name "rootfs"

UBIFS: file system size:   254435328 bytes (248472 KiB, 242 MiB, 493 LEBs)

UBIFS: journal size:       10452992 bytes (10208 KiB, 9 MiB, 21 LEBs)

UBIFS: media format:       w4/r0 (latest is w4/r0)

UBIFS: default compressor: lzo

UBIFS: reserved for root:  0 bytes (0 KiB)

VFS: Mounted root (ubifs filesystem) on device 0:10.

Freeing init memory: 148K

Warning: unable to open an initial console.

Kernel panic - not syncing: Attempted to kill init!
级别: 新手上路
UID: 33474
精华: 0
发帖: 11
金钱: 55 两
威望: 11 点
贡献值: 0 点
综合积分: 22 分
注册时间: 2010-12-01
最后登录: 2011-02-11
1楼  发表于: 2011-01-10 17:30
补充:
百度上查到说,如果使用linux 2.6.xx内核,应该实现创建节点console、null。转到rootfs/dev/目录来创建:
sudo mknod console c 5 1
sudo mknod null c 1 3
否则就会提示“Warning: unable to open an initial console.
Kernel panic - not syncing: Attempted to kill init!”的类似错误

对于上述提示,不知在哪里在初始化时就建立节点?
尝试在init.rc里添加
mknod /dev/console c 5 1
mknod /dev/null c 1 3
重新生成ubi格式的android文件系统,下载后运行还是同样的问题!!!
请问是否由于上述没有建立console节点引起的pannic?
如果是的话,我应该在那个文件里实现节点建立???
级别: 荣誉会员
UID: 34761
精华: 0
发帖: 1348
金钱: 6835 两
威望: 1367 点
贡献值: 0 点
综合积分: 2696 分
注册时间: 2010-12-21
最后登录: 2017-06-02
2楼  发表于: 2011-01-10 18:00
是Mini6410么?
为什么不使用友善提供的2.6.36内核?
级别: 新手上路
UID: 33474
精华: 0
发帖: 11
金钱: 55 两
威望: 11 点
贡献值: 0 点
综合积分: 22 分
注册时间: 2010-12-01
最后登录: 2011-02-11
3楼  发表于: 2011-01-11 10:56
版主,版主,快显灵~~~~
级别: 新手上路
UID: 40848
精华: 0
发帖: 1
金钱: 5 两
威望: 1 点
贡献值: 0 点
综合积分: 2 分
注册时间: 2011-03-23
最后登录: 2011-03-25
4楼  发表于: 2011-03-23 10:57
LZ,你好!,请问我的android系统也是停留在小企鹅界面,并且不前进,用串口线打印信息,一直就到
hub 2-0:1.0: USB hub found

hub 2-0:1.0: 1 port detected这儿,不往下跑。请问是什么原因,谢谢!
级别: 圣骑士
UID: 9690
精华: 0
发帖: 369
金钱: 1955 两
威望: 415 点
贡献值: 0 点
综合积分: 738 分
注册时间: 2009-10-10
最后登录: 2017-11-21
5楼  发表于: 2011-03-23 11:14
commandline里面的init=/init,好像不能直接越过linuxrc,hacker同学说里面有一线触摸的协议部分,而一线触摸在init里面做的
^很多问题的背后都是简单的原因......
级别: 荣誉会员
UID: 34780
精华: 0
发帖: 1219
金钱: 6230 两
威望: 1246 点
贡献值: 0 点
综合积分: 2438 分
注册时间: 2010-12-21
最后登录: 2017-09-18
6楼  发表于: 2011-03-23 11:31
你的kernel是怎么弄来的? kernel.org下载的官方版本?
看调试信息, 似乎你的kernel没有加入Android的补丁