明远智睿技术论坛

标题: init: critical process 'healthd' exited 4 times in 4 minutes [打印本页]

作者: 626329489 时间: 2017-6-28 17:20
标题: init: critical process 'healthd' exited 4 times in 4 minutes
求助大侠：我编译的android启动的时候会总是重启，控制台输出信息如下：
用的是明远智睿的iM6Q开发板，不知道为什么，求助。。。
input: USB OPTICAL MOUSE as /devices/soc0/soc.0/2100000.aips-bus/2184200.usb/ci_hdrc.1/usb1/1-1/1-1.2/1-1.2:1.0/0003:2188:0AE1.0001/input/input1
hid-generic 0003:2188:0AE1.0001: input: USB HID v1.11 Mouse [USB OPTICAL MOUSE ] on usb-ci_hdrc.1-1.2/input0
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
0-001a supply DCVDD not found, using dummy regulator
0-001a supply DBVDD not found, using dummy regulator
0-001a supply AVDD not found, using dummy regulator
0-001a supply CPVDD not found, using dummy regulator
0-001a supply MICVDD not found, using dummy regulator
0-001a supply PLLVDD not found, using dummy regulator
0-001a supply SPKVDD1 not found, using dummy regulator
0-001a supply SPKVDD2 not found, using dummy regulator
wm8962 0-001a: customer id 0 revision D
fsl-asrc 2034000.asrc: driver registered
fsl-hdmi-dai hdmi_audio.3: failed to probe. Load HDMI-video first.
fsl-hdmi-dai: probe of hdmi_audio.3 failed with error -12
input: WM8962 Beep Generator as /devices/soc0/soc.0/2100000.aips-bus/21a0000.i2c/i2c-0/0-001a/input/input2
snd-soc-dummy snd-soc-dummy: ASoC: Failed to create platform debugfs directory
imx-wm8962 sound.21: wm8962 <-> 202c000.ssi mapping ok
imx-wm8962 sound.21: snd-soc-dummy-dai <-> 2034000.asrc mapping ok
imx-wm8962 sound.21: wm8962 <-> 202c000.ssi mapping ok
imx-audio-hdmi sound-hdmi.22: initialize HDMI-audio failed. load HDMI-video first!
oprofile: using arm/armv7-ca9
NET: Registered protocol family 26
TCP: cubic registered
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
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: BNEP socket layer initialized
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
Bluetooth: HIDP socket layer initialized
8021q: 802.1Q VLAN Support v1.8
Key type dns_resolver registered
imx6q-pcie 1ffc000.pcie: phy link never came up
imx6q-pcie 1ffc000.pcie: Failed to bring link up!
imx6q-pcie 1ffc000.pcie: failed to initialize host
imx6q-pcie: probe of 1ffc000.pcie failed with error -22
mipi_dsi_pwr_on: disabling
wm8962-supply: disabling
usb_otg_vbus: disabling
regulator-dummy: disabling
imx mcc test is registered.
input: gpio-keys.20 as /devices/soc0/gpio-keys.20/input/input5
rtc-isl1208 0-006f: hctosys: invalid date/time
ALSA device list:
#0: wm8962-audio
Freeing unused kernel memory: 388K (80973000 - 809d4000)
Console: switching to colour dummy device 80x30
EXT4-fs (mmcblk3p5): mounted filesystem with ordered data mode. Opts: barrier=1
fs_mgr: __mount(source=/dev/block/mmcblk3p5,target=/system,type=ext4)=0
EXT4-fs (mmcblk3p4): Ignoring removed nomblk_io_submit option
EXT4-fs (mmcblk3p4): recovery complete
EXT4-fs (mmcblk3p4): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,noauto_da_alloc,errors=panic
fs_mgr: __mount(source=/dev/block/mmcblk3p4,target=/data,type=ext4)=0
EXT4-fs (mmcblk3p6): Ignoring removed nomblk_io_submit option
EXT4-fs (mmcblk3p6): recovery complete
EXT4-fs (mmcblk3p6): mounted filesystem with ordered data mode. Opts: nomblk_io_submit
fs_mgr: __mount(source=/dev/block/mmcblk3p6,target=/cache,type=ext4)=0
EXT4-fs (mmcblk3p7): mounted filesystem with ordered data mode. Opts: (null)
fs_mgr: __mount(source=/dev/block/mmcblk3p7,target=/device,type=ext4)=0
fs_mgr: Unable to open zram conf device /sys/block/zram0/disksize
random: init urandom read with 43 bits of entropy available
init: using deprecated syntax for specifying property 'ro.serialno', use ${name} instead
init: using deprecated syntax for specifying property 'ro.product.manufacturer', use ${name} instead
init: using deprecated syntax for specifying property 'ro.product.model', use ${name} instead
init: cannot find '/system/bin/debuggerd64', disabling 'debuggerd64'
init: cannot find '/system/bin/install-recovery.sh', disabling 'flash_recovery'
logd.auditd: start
root@myimx6ek_6dq:/ # random: nonblocking pool is initialized
init: critical process 'healthd' exited 4 times in 4 minutes; rebooting into recovery mode
SysRq : Emergency Remount R/O
EXT4-fs (mmcblk3p4): re-mounted. Opts: (null)
imx2-wdt 20bc000.wdog: Device shutdown: Expect reboot!
reboot: Restarting system with command 'recovery'

我感觉关键就在下面这句为什么会退出，求解
init: critical process 'healthd' exited 4 times in 4 minutes

作者: 软件01 时间: 2017-6-29 11:19
是不是进入recovery模式了，能不能启动的全部信息发我或贴出来；还有你是用我们的底板和镜像嘛

作者: 626329489 时间: 2017-6-29 13:44
麻烦看附件中的打印信息

作者: 626329489 时间: 2017-6-29 14:17

626329489 发表于 2017-6-29 13:44
麻烦看附件中的打印信息

上面那个问题我内核编译添加驱动后没那个问题了：
make menuconfig
->device driver
->staging drivers
->android
->android binder ipc driver
但是出现如下的新的问题：
healthd: No charger supplies found
healthd: No battery devices found
init: untracked pid 474 exited with status 3
random: nonblocking pool is initialized
init: untracked pid 787 killed by signal 9
init: untracked pid 1110 exited with status 3
init: untracked pid 1283 killed by signal 9
init: untracked pid 1440 killed by signal 9
init: untracked pid 1608 killed by signal 9
init: untracked pid 1774 killed by signal 9
init: untracked pid 1941 killed by signal 9
init: untracked pid 2105 exited with status 3
init: untracked pid 2266 killed by signal 9
init: untracked pid 2422 exited with status 3
init: untracked pid 2591 killed by signal 9
init: untracked pid 2757 exited with status 3
init: untracked pid 2920 exited with status 3
init: untracked pid 3095 killed by signal 9
init: untracked pid 3247 killed by signal 9
init: untracked pid 3443 killed by signal 9
init: untracked pid 3601 killed by signal 9

作者: 626329489 时间: 2017-6-29 14:18

626329489 发表于 2017-6-29 13:44
麻烦看附件中的打印信息

作者: 软件01 时间: 2017-7-3 09:13

626329489 发表于 2017-6-29 14:18
上面那个问题我内核编译添加驱动后没那个问题了：
make menuconfig
->device driver

你好，烧写我们提供的默认的镜像会出现上面的问题嘛？
如果不会的话，请详细按WIKI的环境搭建编译android源码

作者: 626329489 时间: 2017-7-5 19:41

软件01 发表于 2017-7-3 09:13
你好，烧写我们提供的默认的镜像会出现上面的问题嘛？
如果不会的话，请详细按WIKI的环境搭建编译android ...

上面的问题我make menuconfig下android选项下的所有项目都选中后解决了。
现在android系统可以跑起来了，但是由于没有触摸屏因此我插上鼠标来操作，但是发现鼠标操作的时候，非常的卡顿，翻页点击等都非常卡顿，不知道为什么，求助。

欢迎光临明远智睿技术论坛 (http://bbs.myzr.com.cn/)