打印
[技术问题解答]

android的文件系统启动

[复制链接]
7494|14
手机看帖
扫描二维码
随时随地手机跟帖
跳转到指定楼层
楼主
songshu_yan|  楼主 | 2015-10-12 16:54 | 只看该作者 回帖奖励 |倒序浏览 |阅读模式
我在imx6q上移植android5.0的系统。kernel启动后,文件系统一直加载不了,重复打印binder: 140:140 transaction failed 29189, size 0-0 ,

请各位帮忙分析一下

更多日志:

init: /dev/hw_random not found
Console: switching to colour dummy device 80x30
init: /dev/hw_random not found
device-mapper: table: 254:0: verity: Data device lookup failed
device-mapper: ioctl: error adding target to table
fs_mgr: Error loading verity table (No such file or directory)fs_mgr: Could not set up verified partition, skipping!
EXT4-fs (mmcblk3p4): Ignoring removed nomblk_io_submit option
EXT4-fs (mmcblk3p4): 14 orphan inodes deleted
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
rfkill: BT RF going to : off
init: cannot find '/system/bin/logd', disabling 'logd'
init: cannot find '/system/bin/lmkd', disabling 'lmkd'
init: cannot find '/system/bin/servicemanager', disabling 'servicemanager'
binder: 140:140 transaction failed 29189, size 0-0
init: cannot find '/system/bin/vold', disabling 'vold'
init: cannot find '/system/bin/surfaceflinger', disabling 'surfaceflinger'
init: using deprecated syntax for specifying property 'ro.serialno', use ${name} instead
init: property 'ro.serialno' doesn't exist while expanding '$ro.serialno'
init: cannot expand '$ro.serialno' while writing to '/sys/class/android_usb/android0/iSerial'
init: using deprecated syntax for specifying property 'ro.product.manufacturer', use ${name} instead
init: property 'ro.product.manufacturer' doesn't exist while expanding '$ro.product.manufacturer'
init: cannot expand '$ro.product.manufacturer' while writing to '/sys/class/android_usb/android0/iManufacturer'
init: using deprecated syntax for specifying property 'ro.product.model', use ${name} instead
init: property 'ro.product.model' doesn't exist while expanding '$ro.product.model'
init: cannot expand '$ro.product.model' while writing to '/sys/class/android_usb/android0/iProduct'
init: cannot find '/system/bin/sh', disabling 'console'
init: cannot find '/system/bin/netd', disabling 'netd'
init: cannot find '/system/bin/debuggerd', disabling 'debuggerd'
init: cannot find '/system/bin/debuggerd64', disabling 'debuggerd64'
init: cannot find '/system/bin/drmserver', disabling 'drm'
init: cannot find '/system/bin/mediaserver', disabling 'media'
init: cannot find '/system/bin/installd', disabling 'installd'
init: cannot find '/system/bin/install-recovery.sh', disabling 'flash_recovery'
init: cannot find '/system/bin/keystore', disabling 'keystore'
init: cannot find '/system/bin/rild', disabling 'ril-daemon'
init: cannot find '/system/bin/app_process', disabling 'zygote'
init: cannot find '/system/bin/sh', disabling 'wifi_mac'
init: cannot find '/system/bin/sdcard', disabling 'sdcard'
init: cannot find '/system/bin/magd', disabling 'magd'
android_usb: already disabled
mtp_bind_config
binder: 140:140 transaction failed 29189, size 0-0
binder: 140:140 transaction failed 29189, size 0-0
binder: 140:140 transaction failed 29189, size 0-0
binder: 140:140 transaction failed 29189, size 0-0
binder: 140:140 transaction failed 29189, size 0-0
binder: 140:140 transaction failed 29189, size 0-0
binder: 140:140 transaction failed 29189, size 0-0
binder: 140:140 transaction failed 29189, size 0-0
binder: 140:140 transaction failed 29189, size 0-0

相关帖子

沙发
ach_dmatek| | 2015-10-13 09:46 | 只看该作者
你的system.img文件没有烧写成功。

使用特权

评论回复
板凳
西门扫雪| | 2015-10-13 10:27 | 只看该作者
system.img文件没有烧写成功吧

使用特权

评论回复
地板
songshu_yan|  楼主 | 2015-10-13 10:29 | 只看该作者
ach_dmatek 发表于 2015-10-13 09:46
你的system.img文件没有烧写成功。

我是采用SD卡烧写方式,按照给定的shell脚本将内容下载到sd卡中的,是编译的system.img有问题?还是烧写的不完整呢?

使用特权

评论回复
5
ach_dmatek| | 2015-10-13 10:38 | 只看该作者
编译应该没有问题。估计是烧写没有成功。或者system分区设置的太小。

使用特权

评论回复
6
songshu_yan|  楼主 | 2015-10-13 12:03 | 只看该作者
ach_dmatek 发表于 2015-10-13 10:38
编译应该没有问题。估计是烧写没有成功。或者system分区设置的太小。

我的sytem分区设置了512M,而我的sytem.img只有377.5M。
通过 sudo dd if=system.img of=/dev/sdb5; sync 下载到SD中,应该没有问题吧。

分区大小设置:
# partition size in MB
BOOTLOAD_RESERVE=8
BOOT_ROM_SIZE=8
SYSTEM_ROM_SIZE=512
CACHE_SIZE=512
RECOVERY_ROM_SIZE=8
DEVICE_SIZE=8
MISC_SIZE=6
DATAFOOTER_SIZE=2

使用特权

评论回复
7
songshu_yan|  楼主 | 2015-10-13 12:04 | 只看该作者
西门扫雪 发表于 2015-10-13 10:27
system.img文件没有烧写成功吧

怎么判断SD中的system.img是否完整呢?

使用特权

评论回复
8
ach_dmatek| | 2015-10-14 09:11 | 只看该作者
你看一下Android代码中对system分区设置多大?

使用特权

评论回复
9
songshu_yan|  楼主 | 2015-10-14 11:52 | 只看该作者
ach_dmatek 发表于 2015-10-14 09:11
你看一下Android代码中对system分区设置多大?

谢谢您的耐心解答,我在参数设置中添加了androidboot.selinux=disabled androidboot.dm_verity=disabled后,上面的问题就没有了。

但是我遇到一个新的问题,请您帮忙分析一下。在我的板子中,找不到max11801芯片,所以我在内核配置中去掉了对max11801的支持。我还需要做其它修改吗

日志:
init: /dev/hw_random not found
Console: switching to colour dummy device 80x30
init: /dev/hw_random not found
CPU1: shutdown
charger:
charger: *************** LAST KMSG ***************
charger:
charger: last_kmsg not found. Cold reset?
charger:
CPU2: shutdown
charger: ************* END LAST KMSG *************
charger:
charger: --------------- STARTING CHARGER MODE ---------------
CPU3: shutdown
init: cannot find '/system/bin/sh', disabling 'console'
android_usb: already disabled
mtp_bind_config
healthd: No charger supplies found
healthd: No battery devices found
charger: [65706] device unplugged: shutting down in 10000 (@ 75706)
charger: [75711] shutting down
SysRq : Emergency Remount R/O
Emergency Remount complete
imx2-wdt 20c0000.wdog: Device shutdown: Expect reboot!
Power down.
charger:
charger: *************** LAST KMSG ***************
charger:
charger: last_kmsg not found. Cold reset?
charger:
charger: ************* END LAST KMSG *************
charger:
charger: --------------- STARTING CHARGER MODE ---------------
healthd: No charger supplies found
healthd: No battery devices found
charger: [136104] device unplugged: shutting down in 10000 (@ 146104)
charger: [146110] shutting down
SysRq : Emergency Remount R/O
Emergency Remount complete

使用特权

评论回复
10
ach_dmatek| | 2015-10-14 18:18 | 只看该作者
去掉max11801芯片的驱动配置即可。max11801芯片是和MAX8903芯片联合使用的。你可以在电池检测驱动中给一个默认的ADC值。然后把adc读写部分去掉即可。

使用特权

评论回复
11
songshu_yan|  楼主 | 2015-10-15 14:46 | 只看该作者
ach_dmatek 发表于 2015-10-14 18:18
去掉max11801芯片的驱动配置即可。max11801芯片是和MAX8903芯片联合使用的。你可以在电池检测驱动中给一个 ...

我应该给ADC默认值为多少呢? 我在Android5.0的源码kernel/driver/power/ 和/system/core/healthd/下没有找到关于adc读写的部分,您方便告知一下么。非常感谢!

使用特权

评论回复
12
ach_dmatek| | 2015-10-15 16:45 | 只看该作者
ADC最大是4095.在sabresd_battery.c文件中。找到max11801_read_adc,这里就是度ADC的值。

使用特权

评论回复
13
songshu_yan|  楼主 | 2015-10-15 17:06 | 只看该作者
上面的第二个问题是由于设置了参数androidboot.mode=charger引起的, 现在去掉这个配置则出现下面的问题,
关于“serviermanager”起不来,似乎有很多可能的原因,我这个会不会是电源模块引起的呢?还是其它原因呢

request_suspend_state: wakeup (3->0) at 6061507333 (1970-01-01 00:00:02.748497000 UTC)
init: using deprecated syntax for specifying property 'ro.serialno', use ${name} instead
init: property 'ro.serialno' doesn't exist while expanding '$ro.serialno'
init: cannot expand '$ro.serialno' while writing to '/sys/class/android_usb/android0/iSerial'
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'
CANNOT LINK EXECUTABLE: init: cannot find '/system/bin/install-recovery.sh', disabling 'flash_recovery'
request_suspend_state: wakeup (0->0) at 6153586999 (1970-01-01 00:00:02.840576000 UTC)
android_usb: already disabled
mtp_bind_config
CANNOT LINK EXECUTABLE: request_suspend_state: wakeup (0->0) at 11200391000 (1970-01-01 00:00:07.887382000 UTC)
CANNOT LINK EXECUTABLE: request_suspend_state: wakeup (0->0) at 16241174334 (1970-01-01 00:00:12.928165334 UTC)
CANNOT LINK EXECUTABLE: request_suspend_state: wakeup (0->0) at 21282332334 (1970-01-01 00:00:17.969323335 UTC)
CANNOT LINK EXECUTABLE: init: critical process 'servicemanager' exited 4 times in 4 minutes; rebooting into recovery mode
SysRq : Emergency Remount R/O
EXT4-fs (mmcblk3p4): re-mounted. Opts: (null)
EXT4-fs (mmcblk3p6): re-mounted. Opts: (null)
Emergency Remount complete
imx2-wdt 20c0000.wdog: Device shutdown: Expect reboot!
Restarting system.
....
mxc_restart: Watchdog reset failed to assert reset

使用特权

评论回复
14
quray1985| | 2015-10-16 09:03 | 只看该作者
system.img文件没有烧写成功

使用特权

评论回复
15
songshu_yan|  楼主 | 2015-10-16 13:10 | 只看该作者
quray1985 发表于 2015-10-16 09:03
system.img文件没有烧写成功

我怎样检查我的system烧写有没有成功呢?我是使用SD卡启动的

使用特权

评论回复
发新帖 我要提问
您需要登录后才可以回帖 登录 | 注册

本版积分规则

3

主题

30

帖子

0

粉丝