I'm very close to having a working sshfs setup. I've got:
working fuse.ko module
working version of openssh ssh client
working version of sshfs
I can happily mount remote file systems and use them just fine, but when I try to unmount them, my phone just locks and then reboots. I'd like to try and debug this, but I get no messages in any log that I can see.
So my question is, if I'm getting some kind of kernel panic, where can i see what's actually happening to try and debug this.
Any thoughts on what might be causing this would also be much appreciated.
I'll post full instructions once I get everything working of course.
can you not run "adb shell cat /proc/kmsg" to check for any Kernel Panic's
cat /proc/last_kmsg will get u the details of kernel panic and help u debug
if u want to save it to a file then type
cat /proc/last_kmsg > /sdcard/kmsg.txt
Okay, it's an "Alignment Trap"
Thanks for the info, now I can at least see the fault that's happening. It's an "Alignment trap". I assume this means one of the binaries I've created is messed up somehow. Any ideas on what/how to do about it much appreciated.
Note that this happens if I run 'fusermount -u mountpoint' and also if I run 'umount mountpoint'.
Relevant bits of /proc/last_kmsg:
Code:
[ 4323.039703] Alignment trap: not handling instruction e1903f9f at [<c00cc5dc>]
[ 4323.040069] Unhandled fault: alignment exception (0x011) at 0x00000001
[ 4323.040679] Internal error: : 11 [#1] PREEMPT
[ 4323.041015] last sysfs file: /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
[ 4323.041625] Modules linked in: fuse bcm4329
[ 4323.042877] CPU: 0 Tainted: G W (2.6.34-cyanogenmod #1)
[ 4323.043518] PC is at __destroy_inode+0x7c/0xa0
[ 4323.043853] LR is at __destroy_inode+0x28/0xa0
[ 4323.044494] pc : [<c00cc5e0>] lr : [<c00cc58c>] psr: 20000013
[ 4323.044525] sp : c54b5ee0 ip : 00000010 fp : 00100100
[ 4323.045440] r10: c30358f0 r9 : 00000000 r8 : 00200200
[ 4323.045776] r7 : 00000001 r6 : c54b4000 r5 : 00000000 r4 : c6b41d40
[ 4323.046417] r3 : 00000000 r2 : c54b5ec8 r1 : c54b5ec8 r0 : 00000001
[ 4323.046752] Flags: nzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user
[ 4323.047393] Control: 10c5787d Table: 261bc019 DAC: 00000015
[ 4323.048004]
[ 4323.048004] PC: 0xc00cc560:
----snip lots of register dumps-----
[ 4323.264343] Process fusermount (pid: 2455, stack limit = 0xc54b42f0)
[ 4323.264953] Stack: (0xc54b5ee0 to 0xc54b6000)
-----snip fusermount stack dump--
[ 4323.270294] [<c00cc5e0>] (__destroy_inode+0x7c/0xa0) from [<c00cc610>] (destroy_inode+0xc/0x44)
[ 4323.270935] [<c00cc610>] (destroy_inode+0xc/0x44) from [<c00cba80>] (iput+0x64/0x74)
[ 4323.271575] [<c00cba80>] (iput+0x64/0x74) from [<c00c9f84>] (shrink_dcache_for_umount_subtree+0x24c/0x2e4)
[ 4323.272216] [<c00c9f84>] (shrink_dcache_for_umount_subtree+0x24c/0x2e4) from [<c00ca068>] (shrink_dcache_for_umount+0x4c/0x60)
[ 4323.272888] [<c00ca068>] (shrink_dcache_for_umount+0x4c/0x60) from [<c00bab08>] (generic_shutdown_super+0x1c/0x13c)
[ 4323.273559] [<c00bab08>] (generic_shutdown_super+0x1c/0x13c) from [<c00bac64>] (kill_anon_super+0xc/0x78)
[ 4323.274230] [<c00bac64>] (kill_anon_super+0xc/0x78) from [<c00bb0ec>] (deactivate_super+0x68/0x80)
[ 4323.274597] [<c00bb0ec>] (deactivate_super+0x68/0x80) from [<c00d07dc>] (sys_umount+0x2f8/0x328)
[ 4323.275268] [<c00d07dc>] (sys_umount+0x2f8/0x328) from [<c0025f00>] (ret_fast_syscall+0x0/0x30)
[ 4323.275909] Code: 88bd8010 e3500000 08bd8010 e1903f9f (e2433001)
[ 4323.277313] ---[ end trace 1b75b31a2719ed1f ]---
[ 4323.277954] Kernel panic - not syncing: Fatal exception
[ 4323.278381] [<c002a9ac>] (unwind_backtrace+0x0/0xf0) from [<c03141f0>] (panic+0x58/0xd4)
[ 4323.279052] [<c03141f0>] (panic+0x58/0xd4) from [<c00297f8>] (die+0x2b4/0x304)
[ 4323.279693] [<c00297f8>] (die+0x2b4/0x304) from [<c0025314>] (do_DataAbort+0x80/0x94)
[ 4323.280059] [<c0025314>] (do_DataAbort+0x80/0x94) from [<c0025a2c>] (__dabt_svc+0x4c/0x60)
[ 4323.280700] Exception stack(0xc54b5e98 to 0xc54b5ee0)
[ 4323.281311] 5e80: 00000001 c54b5ec8
[ 4323.281768] 5ea0: c54b5ec8 00000000 c6b41d40 00000000 c54b4000 00000001 00200200 00000000
[ 4323.282409] 5ec0: c30358f0 00100100 00000010 c54b5ee0 c00cc58c c00cc5e0 20000013 ffffffff
[ 4323.283081] [<c0025a2c>] (__dabt_svc+0x4c/0x60) from [<c00cc5e0>] (__destroy_inode+0x7c/0xa0)
[ 4323.283447] [<c00cc5e0>] (__destroy_inode+0x7c/0xa0) from [<c00cc610>] (destroy_inode+0xc/0x44)
[ 4323.284118] [<c00cc610>] (destroy_inode+0xc/0x44) from [<c00cba80>] (iput+0x64/0x74)
[ 4323.284759] [<c00cba80>] (iput+0x64/0x74) from [<c00c9f84>] (shrink_dcache_for_umount_subtree+0x24c/0x2e4)
[ 4323.285430] [<c00c9f84>] (shrink_dcache_for_umount_subtree+0x24c/0x2e4) from [<c00ca068>] (shrink_dcache_for_umount+0x4c/0x60)
[ 4323.286102] [<c00ca068>] (shrink_dcache_for_umount+0x4c/0x60) from [<c00bab08>] (generic_shutdown_super+0x1c/0x13c)
[ 4323.286773] [<c00bab08>] (generic_shutdown_super+0x1c/0x13c) from [<c00bac64>] (kill_anon_super+0xc/0x78)
[ 4323.287414] [<c00bac64>] (kill_anon_super+0xc/0x78) from [<c00bb0ec>] (deactivate_super+0x68/0x80)
[ 4323.287780] [<c00bb0ec>] (deactivate_super+0x68/0x80) from [<c00d07dc>] (sys_umount+0x2f8/0x328)
[ 4323.288421] [<c00d07dc>] (sys_umount+0x2f8/0x328) from [<c0025f00>] (ret_fast_syscall+0x0/0x30)
[ 4323.289062] Rebooting in 5 seconds..
[ 4328.263732] Restarting Linux version 2.6.34-cyanogenmod ([email protected]) (gcc version 4.4.0 (GCC) ) #1 PREEMPT Mon Jun 28 20:07:00 EDT 2010
hope this helps, remove spaces (since I am new user not allowed to post external links )
www rt-embedded com / blog / archives / resolving-alignment-traps /
Any news with this? I would be more than happy to have a working sshfs on my phone
Wish You best luck!
ditto, has anyone managed to get sshfs working?
waspbr said:
ditto, has anyone managed to get sshfs working?
Click to expand...
Click to collapse
I run sshfs on my Epic. I compiled the FUSE kernel module (fuse.ko) from the stock Samsung kernel sources and installed the pre-built userland dependencies (sshfs, fuse-utils, openssh-client, etc.) in a Debian chroot. I mount sshfs "volumes" in the chroot using the "allow_other" option, so that any Android uid/gid can access them.
The chroot probably isn't necessary, but I didn't want to bother compiling the userland dependencies myself. This article gives some directions on how to build a Debian chroot. I don't wase time with the unionfs stuff though, I just bind mount /dev, /dev/pts, /proc, & /sys.
thanks, gonna have a go at it once my schedule clears up
any progress? ive been thinking of using something like this on a Galaxy tab, make it a portal to my remote developer machine.
Sorry to bring up a dead thread, but it seems that there is at least a chance at sshfs. Seeing as I have a need or at least a strong desire to get this working, any chance someone figured it out?
Aaaaaaaaand, reviving this Thread again... sorry...
Anyone managed to get SSHfs properly working?
Thanks!
Related
I am trying an experiment with my Atrix in which I need to be able to build the kernel and have a working wifi module. I have successfully built the faux123's kernel-MB860 (thanks very much!).
I then downloaded faux123's atrix-wifi-module in order to get wifi working. I have built the module, and pushed it to /system/lib/modules. However, wifi doesn't work. Under settings, it just displays "error". dmesg doesn't show nearly as much as a kernel packaged by faux123. Here is my output:
Code:
<4>[ 24.504982] sdhci_tegra_wlan_detect Detecting WLAN
<4>[ 24.504998] mot_wifi_set_carddetect: Nobody to notify
<4>[ 24.507937]
<4>[ 24.507940] Dongle Host Driver, version 4.218.248.31
<4>[ 24.507944] Compiled in /home/kenny/android/atrix-wifi-module/open-src/src/dhd/linux/../.. on Apr 17 2012 at 06:54:15
<6>[ 24.724025] request_suspend_state: wakeup (3->0) at 13492036210 (2012-04-21 19:25:46.351491984 UTC)
<6>[ 24.725196] lm3532_brightness_set: lcd-backlight, 0x4c(76), webtop=0
<7>[ 25.088713] mmc1: queuing CIS tuple 0x91 length 3
<6>[ 25.088824] mmc1: new SDIO card at address 0001
<6>[ 25.534772] usb_ether_get_stats
Whereas, dmesg from a kernel/module packaged by faux123 displays:
Code:
[ 49.811365] sdhci_tegra_wlan_detect Detecting WLAN
[ 49.811403] mot_wifi_set_carddetect: Nobody to notify
[ 49.812815]
[ 49.812818] Dongle Host Driver, version 4.218.248.31
[ 49.812822] Compiled in /home/paul/Froyo/system/vendor/bcm/wlan/osrc/open-src/src/dhd/linux/../.. on Dec 17 2011 at 19:58:57
[ 50.108317] mmc1: queuing CIS tuple 0x91 length 3
[ 50.108350] mmc1: new SDIO card at address 0001
[ 50.136595] alloc static buf at e9980000!
[ 50.136975] F1 signature read @0x18000000=0x9934329
[ 50.139716] DHD: dongle ram size is set to 294912(orig 294912)
[ 50.143537] wl_iw_attach thr:6d0 started
[ 50.143598] wl_iw_bt_init thr:6d1 started
[ 50.143655] dhd_attach thr:6d2 started
[ 50.143706] dhd_attach thr:6d3 started
[ 50.143749] dhd_attach thr:6d4 started
[ 50.191722] dhdsdio_write_vars: Download, Upload and compare of NVRAM succeeded.
[ 50.273753] wifi_get_mac_addr
[ 50.274700] Firmware version = wl0: May 6 2011 13:09:01 version 4.218.248.31
[ 50.442416] eth0: Broadcom Dongle Host Driver mac=40:fc:89:13:a8:83
If I try to do a insmod, I get an invalid argument message.
Code:
# insmod /system/lib/modules/dhd.ko
insmod: init_module '/system/lib/modules/dhd.ko' failed (Invalid argument)
Can someone suggest what I might be missing or doing wrong?
as far as i've researched this problem, it's hardware related. i get the same error (and an accompanying reboot) every time i try to toggle wifi.
http://forum.xda-developers.com/showthread.php?t=1205775
if you have any more success please let me know.
dLo GSR said:
as far as i've researched this problem, it's hardware related.
Click to expand...
Click to collapse
I'm not convinced it is hardware related (other than maybe having the wrong driver), since wifi works great using a true faux123 kernel/module.
I suspect my problem has something to do with how I compiled module or other files that I need to put on the phone.
How did you build it? A little more background might help
Build process ... it works!?!?
First, the good news...the module now works. But I don't understand what I may have done differently this time other than do the builds consecutively.
I retrieved the source:
Code:
$ cd ~/android/faux123-olympus-cm7-kernel
$ git clone https://github.com/faux123/kernel-MB860.git
$ cd ~/android
$ git clone https://github.com/faux123/atrix-wifi-module.git
Then I built:
Code:
$ cd ~/android/faux123-olympus-cm7-kernel/kernel-MB860
$ make ARCH=arm tegra_olympus_cm7_defconfig
$ make ARCH=arm CROSS_COMPILE=/home/kenny/tools/arm-2011.09/bin/arm-none-eabi- -j1
$ cd ../../atrix-wifi-module/open-src/src/dhd/linux/
$ export LINUXSRCDIR=/home/kenny/android/faux123-olympus-cm7-kernel/kernel-MB860
$ make ARCH=arm CROSS_COMPILE=~/tools/arm-2011.09/bin/arm-none-eabi- -j1
$ adb push /home/kenny/android/faux123-olympus-cm7-kernel/kernel-MB860/vendor/bcm/wlan/osrc/open-src/src/dhd/linux/dhd.ko /system/lib/modules/dhd.ko
I had kernel built a few days before I had found the wifi module source. I then tried building the wifi module and pushing the module as shown above.
Since then (over last week or so), I have tried a number of things, including copying files (/etc/firmware/wifi/*) from another phone which has a faux123 kernel. Are these files required? Are there steps in here that I missed?
Hi all
I know this will sound old school but, does anyone know how to get the startup of the sola to show what is actually loading?
Like when you accidentally hit the esc key on your keyboard and the ubuntu boot screen disappears and shows you what is actually happening.
Like I said STOCK STARTUP!
Now mounting system to /system.........
Mounting data to /data..........
Type of thing, similar to MS Windows 98 SE.
I know there must be a way
DEV Device: MB511 (deodexed)
Current System: MT27i
Long Live: V9 Ferrari Rom
code.google.com/p/motorola-flipout-files
I'm also interesting about it. To disable boot logo (bootanimation.zip) and see what's happening behind
Basically nothing, you just get your manufactures logo and thats it. Nothing more nothing less. We probably have to edit a file somewhere
DEV Device: MB511 (deodexed)
Current System: MT27i
Long Live: V9 Ferrari Rom
code.google.com/p/motorola-flipout-files
Ok....... anyone know how to startup in debbugging mode atleast?
DEV Device: MB511 (deodexed)
Current System: MT27i
Long Live: V9 Ferrari Rom
code.google.com/p/motorola-flipout-files
Possiblilty
finally found something that should work except..... you need UART or JTAG access......
Any how thanks Adam Outler!!!!!!!:highfive:
http://forum.xda-developers.com/showpost.php?p=16466682&postcount=5
Edit:
The settings in SBL prompt are
Code:
setenv SWITCH_SEL 6543
setenv PHONE_DEBUG_ON 1
saveenv
Code: Starting kernel at 0x32000000... Uncompressing Linux................................................................................................................................................................................... [ 0.000000] copy: bad source 0 [ 0.000000] mout_audss: bad source 0 [ 0.090142] KERNEL:kernel_sec_get_debug_level_from_boot=0x574f4c44 [ 0.094877] KERNEL:magic_number=0x0 DEBUG LEVEL low!! [ 0.099895] (kernel_sec_set_upload_cause) : upload_cause set 0 [ 5.833835] init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery' sh: can't access tty; job control turned off $ [ 11.433364] init: no such service 'bootanim' [ 24.851663] init: sys_prop: permission denied uid:1000 name:wifi.interface [ 35.227503] init: no such service 'bootanim' [ 38.484304] init: sys_prop: permission denied uid:1000 name:dpm.allowcamera su sh: can't access tty; job control turned off # dmesg|tail [ 47.443068] [email protected] [ 51.363390] mook - wm8994 TTY Off [ 51.666438] eth0: SIOCSIWSCAN : ISCAN [ 51.667822] +++: Set Broadcast ISCAN [ 53.013468] [email protected] [ 54.447852] Send Event ISCAN complete [ 54.448053] eth0 wl_iw_iscan_get_scan buflen_from_user 8192: [ 54.448067] eth0: SIOCGIWSCAN GET broadcast results [ 54.448111] wl_iw_iscan_get_scan return to WE 803 bytes APs=3 [ 84.445803] wl_iw_set_ss_cache_timer_flag called #
This app shows you live dmesg at boot [requires root]. Not exactly what you wanted, but close enough on the geek scale.
https://play.google.com/store/apps/details?id=eu.chainfire.livedmesg.lite
will give it a try. i wish there was a guide on the hijack for the motoboot file.
Edit: thank you! It works like a charm, now to strip it and see how it works. When I get cash I will purchase the full version lol! Chainfire kicks ass! :thumbup:
n2droid said:
This app shows you live dmesg at boot [requires root]. Not exactly what you wanted, but close enough on the geek scale.
https://play.google.com/store/apps/details?id=eu.chainfire.livedmesg.lite
Click to expand...
Click to collapse
I found logcat live wallpaper and loving it!
https://play.google.com/store/apps/details?id=org.jraf.android.logcatlivewallpaperlite
DEV Device: MB511 (deodexed)
Current System: MT27i xICS
Long Live: V9 Ferrari Rom
code.google.com/p/motorola-flipout-files
Hey guys. I'm trying to port Ubuntu Touch to the Beaglebone Black development board. I've already ported CM 10.1. I compiled the Ubuntu Touch files successfully. If I understand correctly, I put the contents of ubuntu-root on my rootfs partition. When I boot, the rootfs is mounted, but there's a kernel panic because it can't find /init, even though it's there. I've set the permissions to rwx for user/group/others as a test. Also, I noticed init is not a binary but a readable script (not sure if this makes a difference). Any thoughts? Thanks in advance.
Below is a snippet of the serial debug output:
Code:
[ 2.614647] davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, driver SMSC LAN8710/LAN8720
[ 2.624626] Detected MACID = 90:59:af:54:8e:7f
[ 2.629256] cpsw 4a100000.ethernet: NAPI disabled
[ 2.636569] input: gpio_keys.13 as /devices/ocp.3/gpio_keys.13/input/input2
[ 2.644458] omap_rtc 44e3e000.rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
[ 2.658486] ALSA device list:
[ 2.661650] No soundcards found.
[ 2.729476] usb 1-1: reset high-speed USB device number 2 using musb-hdrc
[ 2.893267] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[ 2.901818] VFS: Mounted root (ext4 filesystem) on device 179:2.
[ 2.908978] devtmpfs: error mounting -2
[ 2.913274] Freeing init memory: 236K
[ 2.919370] Failed to execute /init. Attempting defaults...
[ 2.927598] Kernel panic - not syncing: No init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.
[ 2.940635] [<c001041d>] (unwind_backtrace+0x1/0x8c) from [<c0498049>] (panic+0x55/0x14c)
[ 2.949181] [<c0498049>] (panic+0x55/0x14c) from [<c04949b3>] (kernel_init+0x67/0x90)
[ 2.957364] [<c04949b3>] (kernel_init+0x67/0x90) from [<c000c17d>] (ret_from_fork+0x11/0x34)
[ 2.966176] drm_kms_helper: panic occurred, switching back to text console
Have you asked the great folks over on IRC (#ubuntu-touch)? They might be able to help you.
It's suggested in the porting guide... https://wiki.ubuntu.com/Touch/Porting
Hello,
now I want to start developing ROMS and kernels for my tablet (Intenso Tab814). It took me alot of time to get my first kernel compiled for the device. This kernel sourced are provided by Intenso: http://www.intenso.de/downloads.php?kategorie=33&produkt=1322562274
I took a compiler from: https://releases.linaro.org/archive/ it's under toolchain and called android.
So know I can luckily start my kernel until to this point:
Code:
[ [email protected]] Warning: unable to open an initial console.
[ [email protected]] VFS: Cannot open root device "(null)" or unknown-block(0,0)
[ [email protected]] Please append a correct "root=" boot option; here are the available partitions:
[ [email protected]] fd00 31636480 cardblksd driver: cardblk
[ [email protected]] fd01 3855600 cardblksd1 00000000-0000-0000-0000-000000000cardblksd1
[ [email protected]] ** enable watchdog
[ [email protected]] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[ [email protected]] [<c0158bfc>] (unwind_backtrace+0x0/0xf8) from [<c0669f30>] (panic+0x70/0x194)
[ [email protected]] [<c0669f30>] (panic+0x70/0x194) from [<c0008d70>] (mount_block_root+0x20c/0x2b0)
[ [email protected]] [<c0008d70>] (mount_block_root+0x20c/0x2b0) from [<c0008fcc>] (prepare_namespace+0x158/0x1a0)
[ [email protected]] [<c0008fcc>] (prepare_namespace+0x158/0x1a0) from [<c0008a50>] (kernel_init+0x130/0x13c)
[ [email protected]] [<c0008a50>] (kernel_init+0x130/0x13c) from [<c01530f0>] (kernel_thread_exit+0x0/0x8)
[ [email protected]] CPU1: stopping
[ [email protected]] [<c0158bfc>] (unwind_backtrace+0x0/0xf8) from [<c014c3e4>] (do_IPI+0x180/0x194)
[ [email protected]] [<c014c3e4>] (do_IPI+0x180/0x194) from [<c0151b8c>] (__irq_svc+0x4c/0xe4)
[ [email protected]] Exception stack(0xdf863f90 to 0xdf863fd8)
[ [email protected]] 3f80: 00000001 00000001 df863fd8 00000000
[ [email protected]] 3fa0: df862000 c08bc9e4 c06709c4 c087c7ec 8000406a 413fc090 00000000 00000000
[ [email protected]] 3fc0: 00000000 df863fd8 c015314c c0153150 60000013 ffffffff
[ [email protected]] [<c0151b8c>] (__irq_svc+0x4c/0xe4) from [<c0153150>] (default_idle+0x24/0x28)
[ [email protected]] [<c0153150>] (default_idle+0x24/0x28) from [<c0153560>] (cpu_idle+0xc0/0xf4)
[ [email protected]] [<c0153560>] (cpu_idle+0xc0/0xf4) from [<80667114>] (0x80667114)
[ [email protected]] m3_nand_reboot_notifier 1023
Now I'm only missing the rootfs for my kernel, please help me with that. I also want to be a developer.
I was also able to break let say the bootloader, I have added a serial connection by solder the GND RX and TX ports with some wires, and connected them via a UART TTL Converter with USB interface to my computer.
I'm running Linux for over 8 years, now I want to start to go ahead and do kernel and not only the application development.
There is only the init process missing, where I can get it from, it must be an EFL executable like you can see in my unpacked kernels from the vendors: https://www.dropbox.com/sh/ykkaguaps2l8vd1/AAAMhdNB-MQ2Bg-xOWPrhC12a/3.0.8?dl=0
But If I uncompress my kernel there is no rootfs, is this rootfs a tmpfs one or a physical one?
I wish anyone of you is willing to help me getting started with development, I know that after the kernel the OS Android is above the whole kernel. So my Android OS will have a self compiled kernel under it's hood.
I also want to customize and get KitKat Android on that tablet in a stable state, where are Android KitKat downloads? I prefer LineageOS or AOKP. I want to stay rooted.
In my existing running kernel I see with the filemanager in the /boot directory is part of the rootfs and there are mali.ko and ump.ko kernel modules for my Mali-400 MP GPU. Must I recompile them from sources everytime, so kernel and the modules do fit toghether?
I'm still not smart enough, but I want to start, I also want to have a home somewhere where I can show my developed ROM's.
Thank you in advance,
AMLOGIC :angel:
What I know is that the error stems from trie_builder.cpp. What I would like to find out is what is causing the duplicate error. Possibilities could be the fact that I flashed a system.img without making a vendor.img for it. I would like help if someone understands what trie_builder.cpp does during init so that I can know what is being duplicated.
Code:
[ 1.639868] (4)[1:init]init: j: Duplicate exact match detected for 'ro.vendor.build.id'
[ 1.641735] (4)[1:init]init: Failed to initialize property area
[ 1.643880] (4)[1:init]init: InitFatalReboot: signal 6
[ 1.679532] (4)[1:init]init: #00 pc 000000000012637c /system/bin/init (android::init::InitFatalReboot(int)+104)
[ 1.679607] (4)[1:init]init: #01 pc 00000000000bd894 /system/bin/init (android::init::InitAborter(char const*)+48)
[ 1.679673] (4)[1:init]init: #02 pc 000000000001595c /system/lib64/libbase.so (android::base::SetAborter(std::__1::function<void (char const*)>&&)::$_3::__invoke(char const*)+76)
[ 1.679734] (4)[1:init]init: #03 pc 0000000000014f8c /system/lib64/libbase.so (android::base::LogMessage::~LogMessage()+364)
[ 1.679790] (4)[1:init]init: #04 pc 0000000000116160 /system/bin/init (android::init::propertyInit()+2012)
[ 1.679846] (4)[1:init]init: #05 pc 00000000000f69f0 /system/bin/init (android::init::SecondStageMain(int, char**)+620)
Did you ever solve this? I'm having the same error, but in the build process.
No I have never been able to solve it