This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

init: Failed to open socket 'property_service:'

Hi All,

I am trying to boot custom board with 4AJ.2.5P2 OMAP4 Jelly Bean. While booting, I got error as init: Failed to open socket 'property_service': Address family not supported by protocol and kernel was getting crashed.

I've used the below bootargs.

setenv bootargs 'console=ttyO2,115200n8 mem=1G androidboot.console=ttyO2 root=/dev/mmcblk0p2 rw rootdelay=2 rootfstype=ext3 init=/init vram=32M omapfb.vram=0:16M androidboot.console=ttyO2 consoleblank=0'
setenv bootcmd 'mmcinit 0;fatload mmc 0 0x80000000 uImage; bootm 0x80000000'
boot

These are the logs, i got

cannot apply mgr(lcd2) on inactive device
[ 3.384948] Console: switching to colour frame buffer device 160x48
[ 3.438201] cannot apply mgr(lcd2) on inactive device
[ 3.443969] cannot aply mgr(lcd)--invalid device
[ 3.449310] omapfb omapfb: failed to apply dispc config
[ 3.455230] cannot aply mgr(tv)--invalid device
[ 3.460418] omapfb omapfb: failed to apply dispc config
[ 3.466674] cannot apply mgr(lcd2) on inactive device
[ 3.473510] omapfb omapfb: failed to apply dispc config
[ 3.481842] omapdss DPI: Could not find exact pixel clock. Requested 71000 kHz, got 69818 kHz
[ 3.497100] VUSB: incomplete constraints, leaving on
[ 3.504638] twl_rtc twl_rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
[ 3.514099] ALSA device list:
[ 3.517669] No soundcards found.
[ 3.522155] Waiting 2sec before mounting root device...
[ 5.576232] kjournald starting. Commit interval 5 seconds
[ 5.580352] EXT3-fs (mmcblk0p2): using internal journal
[ 5.582672] EXT3-fs (mmcblk0p2): recovery complete
[ 5.582702] EXT3-fs (mmcblk0p2): mounted filesystem with ordered data mode
[ 5.582763] VFS: Mounted root (ext3 filesystem) on device 179:2.
[ 5.583251] Freeing init memory: 272K
[ 5.616943] init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj instead.
[ 5.802490] init: could not open /dev/keychord
[ 5.808410] init: cannot open '/initlogo.rle'
[ 6.206970] rproc remoteproc0: skipping power up until last virtio device ipu_c0
[ 6.217071] virtio_rpmsg_bus virtio0: rpmsg host is online
[ 6.223083] init: Failed to open socket 'property_service': Address family not supported by protocol
[ 6.223602] init: init startup failure
[ 6.223999] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100
[ 6.224029]
[ 6.248352] CPU1: stopping
[ 6.251495] Backtrace:
[ 6.254730] [<c00193e8>] (dump_backtrace+0x0/0x110) from [<c0539a8c>] (dump_stack+0x18/0x1c)
[ 6.264160] r6:c079b980 r5:ed302000 r4:00000001 r3:00000000
[ 6.271423] [<c0539a74>] (dump_stack+0x0/0x1c) from [<c001ac1c>] (handle_IPI+0x1ac/0x1c4)
[ 6.280700] [<c001aa70>] (handle_IPI+0x0/0x1c4) from [<c0008514>] (gic_handle_irq+0x64/0x68)
[ 6.290161] [<c00084b0>] (gic_handle_irq+0x0/0x68) from [<c053d800>] (__irq_svc+0x40/0x70)
[ 6.299560] Exception stack(0xed303bd8 to 0xed303c20)
[ 6.305419] 3bc0: 60000013 60000013
[ 6.314605] 3be0: c07c4444 00000000 c0801c5c 00000003 c0801c8e c07c4430 00000044 00000001
[ 6.323913] 3c00: 00000000 ed303cd4 ed303bd0 ed303c20 c053d018 c0049adc 60000013 ffffffff
[ 6.333190] r7:ed303c0c r6:ffffffff r5:60000013 r4:c0049adc
[ 6.340301] [<c0049684>] (vprintk+0x0/0x5b0) from [<c0539cfc>] (printk+0x24/0x2c)
[ 6.348876] [<c0539cd8>] (printk+0x0/0x2c) from [<c0329f78>] (__dev_printk+0x4c/0x8c)
[ 6.357788] r3:ed305480 r2:c06f5b34 r1:c06ae2c4 r0:c06c7618
[ 6.364898] [<c0329f2c>] (__dev_printk+0x0/0x8c) from [<c0329ff8>] (_dev_info+0x40/0x48)
[ 6.374114] [<c0329fb8>] (_dev_info+0x0/0x48) from [<c04786c0>] (rpmsg_probe+0x354/0x450)
[ 6.383422] r3:00000035 r2:00000001 r1:c06f5904
[ 6.389221] [<c047836c>] (rpmsg_probe+0x0/0x450) from [<c02da778>] (virtio_dev_probe+0xe4/0x154)
[ 6.399230] [<c02da694>] (virtio_dev_probe+0x0/0x154) from [<c032dbb4>] (driver_probe_device+0xa4/0x220)
[ 6.409942] [<c032db10>] (driver_probe_device+0x0/0x220) from [<c032de0c>] (__device_attach+0x44/0x48)
[ 6.420349] r8:c086bf84 r7:c032ddc8 r6:ed303e28 r5:ed306e18 r4:c07f5e90
[ 6.428527] r3:ffffffff
[ 6.431945] [<c032ddc8>] (__device_attach+0x0/0x48) from [<c032c210>] (bus_for_each_drv+0x68/0x94)
[ 6.442077] r5:00000000 r4:ed306e18
[ 6.446563] [<c032c1a8>] (bus_for_each_drv+0x0/0x94) from [<c032dedc>] (device_attach+0xa0/0xc0)
[ 6.456512] r7:ed2db428 r6:c07d52a4 r5:ed306e4c r4:ed306e18
[ 6.463745] [<c032de3c>] (device_attach+0x0/0xc0) from [<c032ce4c>] (bus_probe_device+0x8c/0xb0)
[ 6.473571] r6:c07d52a4 r5:ed306e18 r4:ed306e18 r3:ed04a4c0
[ 6.480834] [<c032cdc0>] (bus_probe_device+0x0/0xb0) from [<c032ba3c>] (device_add+0x5dc/0x68c)
[ 6.490692] r6:00000000 r5:ed306e20 r4:ed306e18 r3:c07d3a08
[ 6.497772] [<c032b460>] (device_add+0x0/0x68c) from [<c032bb08>] (device_register+0x1c/0x20)
[ 6.507476] [<c032baec>] (device_register+0x0/0x20) from [<c02da8a4>] (register_virtio_device+0x78/0x94)
[ 6.518188] r4:ed306e10 r3:ed306f94
[ 6.522674] [<c02da82c>] (register_virtio_device+0x0/0x94) from [<c04767e0>] (rproc_add_virtio_dev+0x68/0xf8)
[ 6.533874] r5:00000007 r4:ed306a00
[ 6.538360] [<c0476778>] (rproc_add_virtio_dev+0x0/0xf8) from [<c0473b44>] (rproc_fw_config_virtio+0x344/0x554)
[ 6.549774] [<c0473800>] (rproc_fw_config_virtio+0x0/0x554) from [<c0473f24>] (rproc_loader_thread+0xc4/0x10c)
[ 6.561096] [<c0473e60>] (rproc_loader_thread+0x0/0x10c) from [<c006a5fc>] (kthread+0x9c/0xa0)
[ 6.570861] r8:00000000 r7:c0473e60 r6:ed2db400 r5:00000002 r4:ed031dc8
[ 6.579315] [<c006a560>] (kthread+0x0/0xa0) from [<c004cd68>] (do_exit+0x0/0x804)
[ 6.587829] r7:00000013 r6:c004cd68 r5:c006a560 r4:ed031dc8
[ 6.595062] Rebooting in 5 seconds..

UPDATE:

We had changed lot in kernel. Now the above mentioned errors are no more. But, I am facing the problem in surface flinger.

When Surface flinger is started, crash is occurred and at last, logcat shows that "service 'SurfaceFlinger' died" and "[FramebufferSurface] setDefaultBufferSize: dimensions cannot be 0 (w=0, h=0)"

I've attached the recent logs. Please help me to debug it.

4807.logs.txt

Any Guidance will be appreciated!!