Stuck in Bootanimation

98 views
Skip to first unread message

Torsten Appelhagen

unread,
Nov 15, 2019, 6:44:42 AM11/15/19
to Android-x86
Hi all,
now that I've got some hardware again I would like to continue working on the LTE modem issues (another thread in this group). Unfortunately a fresh build of Oreo-x86_64 gets stuck in boot animation on this device.
What makes me wonder: In VMware it basically works...?
On my laptop (HP ZBook) I cannot boot Android at all, none of the modes (live, Vulcan, no hardware support) works, I even cannot switch to the console.
In a VM this image works with HW support disabled (only then)!
On the intended device (Pentium N4200 with Intel Graphics 500) only the bootanimantion repeats endlessly, but at least here I can switch to the root console to check DMESG and LOGCAT.
I found the following crash information:
--------- beginning of crash
06-26 00:07:02.299  1537  1584 F libc    : Fatal signal 7 (SIGBUS), code 2, fault addr 0x71b7c7f0 in tid 1584 (system-server-i), pid 1537 (system_server)
06-26 00:07:02.311  1590  1590 I crash_dump64: type=1400 audit(0.0:165): avc: denied { search } for name="/" dev="tmpfs" ino=9221 scontext=u:r:crash_dump:s0 tcontext=u:object_r:tmpfs:s0 tclass=dir permissive=1
06-26 00:07:02.312  1590  1590 I crash_dump64: type=1400 audit(0.0:166): avc: denied { getattr } for path="/vendor" dev="tmpfs" ino=1990 scontext=u:r:crash_dump:s0 tcontext=u:object_r:tmpfs:s0 tclass=lnk_file permissive=1
06-26 00:07:02.312  1590  1590 I crash_dump64: type=1400 audit(0.0:167): avc: denied { read } for name="vendor" dev="tmpfs" ino=1990 scontext=u:r:crash_dump:s0 tcontext=u:object_r:tmpfs:s0 tclass=lnk_file permissive=1
06-26 00:07:02.331  1591  1591 I crash_dump64: obtaining output fd from tombstoned, type: kDebuggerdTombstone
06-26 00:07:02.331  1445  1445 I /system/bin/tombstoned: received crash request for pid 1537
06-26 00:07:02.331  1591  1591 I crash_dump64: performing dump of process 1537 (target tid = 1584)
06-26 00:07:02.332  1591  1591 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
06-26 00:07:02.332  1591  1591 F DEBUG   : Build fingerprint: '[...]11061727:userdebug/dev-keys'
06-26 00:07:02.332  1591  1591 F DEBUG   : Revision: '0'
06-26 00:07:02.332  1591  1591 F DEBUG   : ABI: 'x86_64'
06-26 00:07:02.332  1591  1591 F DEBUG   : pid: 1537, tid: 1584, name: system-server-i  >>> system_server <<<
06-26 00:07:02.332  1591  1591 F DEBUG   : signal 7 (SIGBUS), code 2 (BUS_ADRERR), fault addr 0x71b7c7f0
06-26 00:07:02.332  1591  1591 F DEBUG   :     rax 0000000070b97ea8  rbx 0000000012dc31b0  rcx 62f8abbd5c1afd69  rdx 0000000012dc31b0
06-26 00:07:02.332  1591  1591 F DEBUG   :     rsi 0000000012dc24d0  rdi 0000000070c1ff88
06-26 00:07:02.332  1591  1591 F DEBUG   :     r8  0000000000000007  r9  00007b0820df3c60  r10 fffffffffffff92e  r11 00007b08bac86778
06-26 00:07:02.332  1591  1591 F DEBUG   :     r12 0000000012c4c900  r13 0000000012c4c900  r14 000000007103f138  r15 0000000012dc1eb8
06-26 00:07:02.332  1591  1591 F DEBUG   :     cs  0000000000000033  ss  000000000000002b
06-26 00:07:02.332  1591  1591 F DEBUG   :     rip 0000000071b7c7f0  rbp 0000000012dc24d0  rsp 00007b0820df3d18  eflags 0000000000010246
06-26 00:07:02.840  1591  1591 F DEBUG   : 
06-26 00:07:02.840  1591  1591 F DEBUG   : backtrace:
06-26 00:07:02.840  1591  1591 F DEBUG   :     #00 pc 00000000006b27f0  /system/framework/x86_64/boot.oat (offset 0x1d3000) (java.util.stream.ReferencePipeline.filter)
06-26 00:07:02.840  1591  1591 F DEBUG   :     #01 pc 000000000137b47e  /system/framework/oat/x86_64/services.odex (offset 0x5ac000) (com.android.server.om.OverlayManagerSettings.selectWhereUser+142)
06-26 00:07:02.840  1591  1591 F DEBUG   :     #02 pc 0000000001377ea6  /system/framework/oat/x86_64/services.odex (offset 0x5ac000) (com.android.server.om.OverlayManagerServiceImpl.updateOverlaysForUser+134)
06-26 00:07:02.840  1591  1591 F DEBUG   :     #03 pc 0000000001373bcc  /system/framework/oat/x86_64/services.odex (offset 0x5ac000) (com.android.server.om.OverlayManagerService.onSwitchUser+108)
06-26 00:07:02.840  1591  1591 F DEBUG   :     #04 pc 00000000013737f5  /system/framework/oat/x86_64/services.odex (offset 0x5ac000) (com.android.server.om.OverlayManagerService.lambda$-com_android_server_om_OverlayManagerService_9907+725)
06-26 00:07:02.840  1591  1591 F DEBUG   :     #05 pc 000000000136a3f5  /system/framework/oat/x86_64/services.odex (offset 0x5ac000) (com.android.server.om.-$Lambda$Whs3NIaASrs6bpQxTTs9leTDPyo.run+261)
06-26 00:07:02.840  1591  1591 F DEBUG   :     #06 pc 00000000005fdcdf  /system/framework/oat/x86_64/services.odex (offset 0x5ac000) (com.android.server.SystemServerInitThreadPool.lambda$-com_android_server_SystemServerInitThreadPool_2249+271)
06-26 00:07:02.840  1591  1591 F DEBUG   :     #07 pc 00000000005ac5f7  /system/framework/oat/x86_64/services.odex (offset 0x5ac000) (com.android.server.-$Lambda$Ganck_s9Kl5o2K6eVDoQTKLc-6g.run+231)
06-26 00:07:02.840  1591  1591 F DEBUG   :     #08 pc 00000000005f9439  /system/framework/x86_64/boot.oat (offset 0x1d3000) (java.util.concurrent.Executors$RunnableAdapter.call+73)
06-26 00:07:02.840  1591  1591 F DEBUG   :     #09 pc 00000000005f7daa  /system/framework/x86_64/boot.oat (offset 0x1d3000) (java.util.concurrent.FutureTask.run+250)
06-26 00:07:02.840  1591  1591 F DEBUG   :     #10 pc 000000000061ba50  /system/framework/x86_64/boot.oat (offset 0x1d3000) (java.util.concurrent.ThreadPoolExecutor.runWorker+1200)
06-26 00:07:02.840  1591  1591 F DEBUG   :     #11 pc 000000000062bd13  /system/framework/x86_64/boot.oat (offset 0x1d3000) (java.util.concurrent.ThreadPoolExecutor$Worker.run+67)
06-26 00:07:02.840  1591  1591 F DEBUG   :     #12 pc 0000000001756c0e  /system/framework/x86_64/boot-framework.oat (offset 0x609000) (com.android.internal.util.ConcurrentUtils$1$1.run+94)
06-26 00:07:02.840  1591  1591 F DEBUG   :     #13 pc 0000000000611514  /system/lib64/libart.so (art_quick_invoke_stub+756)
06-26 00:07:02.840  1591  1591 F DEBUG   :     #14 pc 00000000001470d7  /system/lib64/libart.so (art::ArtMethod::Invoke(art::Thread*, unsigned int*, unsigned int, art::JValue*, char const*)+215)
06-26 00:07:02.840  1591  1591 F DEBUG   :     #15 pc 0000000000527ab6  /system/lib64/libart.so (art::InvokeWithArgArray(art::ScopedObjectAccessAlreadyRunnable const&, art::ArtMethod*, art::ArgArray*, art::JValue*, char const*)+86)
06-26 00:07:02.840  1591  1591 F DEBUG   :     #16 pc 0000000000528f34  /system/lib64/libart.so (art::InvokeVirtualOrInterfaceWithJValues(art::ScopedObjectAccessAlreadyRunnable const&, _jobject*, _jmethodID*, jvalue*)+724)
06-26 00:07:02.840  1591  1591 F DEBUG   :     #17 pc 0000000000553095  /system/lib64/libart.so (art::Thread::CreateCallback(void*)+1349)
06-26 00:07:02.840  1591  1591 F DEBUG   :     #18 pc 0000000000079f0b  /system/lib64/libc.so (__pthread_start(void*)+27)
06-26 00:07:02.840  1591  1591 F DEBUG   :     #19 pc 0000000000028c5d  /system/lib64/libc.so (__start_thread+61)
06-26 00:07:02.840  1591  1591 F DEBUG   :     #20 pc 0000000000027555  /system/lib64/libc.so (__bionic_clone+53)
06-26 00:07:03.232  1591  1591 E crash_dump64: unable to connect to activity manager: No such file or directory
06-26 00:07:03.233  1445  1445 E /system/bin/tombstoned: Tombstone written to: /data/tombstones/tombstone_46


...and I assume this could be the cause?

So my questions are, is this probably caused by some recent changes in Android-x86 which will be fixed soon? Or does it look like I broke something?
If it's the latter has anybody a hint for me where I should start searching?

Thanks!

BR
Torsten

Chih-Wei Huang

unread,
Nov 15, 2019, 9:26:31 AM11/15/19
to Android-x86
Torsten Appelhagen <bors...@gmail.com> 於 2019年11月15日 週五 下午7:44寫道：
>
> Hi all,
> now that I've got some hardware again I would like to continue working on the LTE modem issues (another thread in this group). Unfortunately a fresh build of Oreo-x86_64 gets stuck in boot animation on this device.
> What makes me wonder: In VMware it basically works...?
> On my laptop (HP ZBook) I cannot boot Android at all, none of the modes (live, Vulcan, no hardware support) works, I even cannot switch to the console.
> In a VM this image works with HW support disabled (only then)!
> On the intended device (Pentium N4200 with Intel Graphics 500) only the bootanimantion repeats endlessly, but at least here I can switch to the root console to check DMESG and LOGCAT.

Sounds like an old CPU.
Does it meet the x86_64 ABI requirement?

> I found the following crash information:
[deleted]
> ...and I assume this could be the cause?
>
> So my questions are, is this probably caused by some recent changes in Android-x86 which will be fixed soon? Or does it look like I broke something?
> If it's the latter has anybody a hint for me where I should start searching?

Does 8.1-r3 work for you?
There is no change in oreo-x86 since 8.1-r3.


--
Chih-Wei
Android-x86 project
http://www.android-x86.org

Torsten Appelhagen

unread,
Nov 15, 2019, 10:01:07 AM11/15/19
to Android-x86
> On the intended device (Pentium N4200 with Intel Graphics 500) only the bootanimantion repeats endlessly, but at least here I can switch to the root console to check DMESG and LOGCAT.

Sounds like an old CPU.
Does it meet the x86_64 ABI requirement?

in fact it's quite a new one - started in 2016 but for the N-series of mobile processors there was no successor yet...

Does 8.1-r3 work for you?
There is no change in oreo-x86 since 8.1-r3.

will check, our latest download was r2 I think. Thanks! 

Torsten Appelhagen

unread,
Nov 15, 2019, 10:09:26 AM11/15/19
to Android-x86
oh, I forgot:

RC2 worked, after that we started building our own images.

Torsten Appelhagen

unread,
Nov 15, 2019, 11:20:30 AM11/15/19
to Android-x86
Downloaded and tested:
RC3 works except for the Touchscreen (a little bit strange because THAT was working before, I don't remember any changes by us).
While I was at it I also checked 9 RC1 - which also starts (without Touch), but the settings app cannot be opened (the search element on top is shown but the rest of the window is empty until a message appears if I want to wait or stop the app). I didn't check further for the moment.

So that means the crash is cause by something we have changed. Damn. :(

Have a nice weekend anyway!
Reply all
Reply to author
Forward
0 new messages