Status Update
Comments
ak...@google.com <ak...@google.com> #2
1. Emulator version
2. Run the emulator from command line with “$ANDROID_SDK_ROOT/emulator/emulator -avd <NameOfAVD> -verbose -show-kernel” and send the resulting logs
3. Any relevant Logcat logs
4. The results of running “adb shell top” in the command line.
For more information on what’s needed and how to obtain this information please read the guide at
ro...@veeva.com <ro...@veeva.com> #3
Sure, the emulator version is still the same of the one stated in the title: 32.1.12
.
I've attached all the log required.
Please let me know if I can help with some other tests.
jv...@google.com <jv...@google.com>
bo...@google.com <bo...@google.com> #4
[ 53.423375] type=1400 audit(1681373286.256:38): avc: denied { read } for comm="Binder:210_2" name="wakeup34" dev="sysfs" ino=19031 scontext=u:r:system_suspend:s0 tcontext=u:object_r:sysfs:s0 tclass=dir permissive=0
[ 53.426360] type=1400 audit(1681373286.256:39): avc: denied { read } for comm="Binder:210_2" name="wakeup35" dev="sysfs" ino=19094 scontext=u:r:system_suspend:s0 tcontext=u:object_r:sysfs:s0 tclass=dir permissive=0
VERBOSE | ColorBuffer 223, allocation size and type index: 9175040, 10, allocated memory property: 206, requested memory property: 0
VERBOSE | ColorBuffer 224, allocation size and type index: 9175040, 10, allocated memory property: 206, requested memory property: 0
VERBOSE | ColorBuffer 225, allocation size and type index: 9175040, 10, allocated memory property: 206, requested memory property: 0
error: kvm run failed Bad address
EAX=0a71f000 EBX=b70c1580 ECX=000b45a0 EDX=b700d000
ESI=000b45a0 EDI=b700e000 EBP=c4651118 ESP=c4651040
EIP=f0c4c7b7 EFL=00200202 [-------] CPL=3 II=0 A20=1 SMM=0 HLT=0
ES =002b 00000000 ffffffff 00c0f300 DPL=3 DS [-WA]
CS =0023 00000000 ffffffff 00c0fb00 DPL=3 CS32 [-RA]
SS =002b 00000000 ffffffff 00c0f300 DPL=3 DS [-WA]
DS =002b 00000000 ffffffff 00c0f300 DPL=3 DS [-WA]
FS =0073 e4f51810 00dc0fff 00d0f300 DPL=3 DS [-WA]
GS =006b c4654480 ffffffff 00d0f300 DPL=3 DS [-WA]
LDT=0000 00000000 00000000 00000000
TR =0040 00069000 0000206f 00008b00 DPL=0 TSS64-busy
GDT= fffffe0000067000 0000007f
IDT= fffffe0000000000 00000fff
CR0=80050033 CR2=00000000c172c000 CR3=0000000023a7a000 CR4=000406e0
DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000
DR6=00000000ffff0ff0 DR7=0000000000000400
EFER=0000000000000d01
Code=04 38 f3 0f 6f 4c 38 10 f3 0f 6f 54 38 20 f3 0f 6f 5c 38 30 <66> 0f e7 07 66 0f e7 4f 10 66 0f e7 57 20 66 0f e7 5f 30 8d 7f 40 39 fb 77 cf 0f ae f8 e9
INFO | Wait for emulator (pid 12414) 20 seconds to shutdown gracefull
bo...@google.com <bo...@google.com> #5
-feature -Vulkan
hs...@google.com <hs...@google.com> #6
ro...@veeva.com <ro...@veeva.com> #7
Mmm, it seems to be related to the CPU: my OS is on an external SSD and right now I'm on a different PC with an Intel i7-4770K and here it seems to work.
The freeze happens on an AMD Ryzen 7 5800X, kernel version was 6.1.0-1007-oem
. Now on with the Intel I'm using 6.1.0-1009-oem
.
Unfortunately I will be unable to test on the 5800X until the 30th of April.
hs...@google.com <hs...@google.com> #8
Let me test the same kernel and see if that makes any difference.
ro...@veeva.com <ro...@veeva.com> #9
Sure, once I'll be back to my 5800X, I'm available for some remote debugging, if needed.
hs...@google.com <hs...@google.com> #10
However, only Chrome itself was wrong. The AVD itself is alive and working fine.
I did not run into problem because I compiled the emulator from emu-master-dev which should be around 33.1.4. At that time, all prebuilt emulators failed to recognize my GPU so I had to hack the code a bit and build my own.
Anyway, my experiment results show either emulator 33.1.4 or emulator 32.1.12 with "-feature -Vulkan" can bring the Chrome to normal.
When you get access to your AMD platform, can you try the same thing? Let's see if the mysterious KVM error is a result of Chrome or it is a separate issue at all. Thanks!
ro...@veeva.com <ro...@veeva.com> #11
For me the emulator becomes unusable: the navigation bar back and home button can't be clicked. I have to close it and cold boot it.
And sure, once I'll be back to my 5800X I'll test again and report back.
ro...@veeva.com <ro...@veeva.com> #12
Hey, sorry for the delay, I was finally able to test and I can confirm that starting a 32.1.12 emulator with -feature -Vulkan
brings Chrome to normal.
Is it possible to modify the avd configuration of an existing emulator to always start the it with Vulkan disabled? I have many emulators and I would like to be able to start them directly from Android Studio.
Btw, let me know if I should do more tests. I'm also available if you want me to run a debug version of the emulator or have a remote session with zoom or teamviewer.
aa...@gmail.com <aa...@gmail.com> #13
Same issue here:
added library libvulkan.so
createGlobalVkEmulation:927 Selecting Vulkan device: AMD Radeon RX 6800 XT (RADV NAVI21)
initialize: Supports id properties, got a vulkan device UUID
I0516 19:55:52.901322 32440 VkCommonOperations.cpp:1181] Initializing VkEmulation features:
I0516 19:55:52.901330 32440 VkCommonOperations.cpp:1182] glInteropSupported: true
I0516 19:55:52.901333 32440 VkCommonOperations.cpp:1183] useDeferredCommands: true
I0516 19:55:52.901337 32440 VkCommonOperations.cpp:1185] createResourceWithRequirements: true
I0516 19:55:52.901339 32440 VkCommonOperations.cpp:1186] useVulkanComposition: false
I0516 19:55:52.901343 32440 VkCommonOperations.cpp:1187] useVulkanNativeSwapchain: false
I0516 19:55:52.901347 32440 VkCommonOperations.cpp:1188] enable guestRenderDoc: false
I0516 19:55:52.901350 32440 VkCommonOperations.cpp:1189] ASTC LDR emulation mode: 1
I0516 19:55:52.901354 32440 VkCommonOperations.cpp:1190] enable ETC2 emulation: true
I0516 19:55:52.901357 32440 VkCommonOperations.cpp:1191] enable Ycbcr emulation: false
I0516 19:55:52.901361 32440 VkCommonOperations.cpp:1192] guestUsesAngle: false
I0516 19:55:52.901364 32440 VkCommonOperations.cpp:1193] useDedicatedAllocations: true
I0516 19:55:52.901368 32440 FrameBuffer.cpp:418] Graphics Adapter Vendor Google (AMD)
I0516 19:55:52.901371 32440 FrameBuffer.cpp:419] Graphics Adapter Android Emulator OpenGL ES Translator (AMD Radeon RX 6800 XT (navi21, LLVM 15.0.7, DRM 3.52, 6.3.2-zen1-1-zen))
I0516 19:55:52.901375 32440 FrameBuffer.cpp:420] Graphics API Version OpenGL ES 3.0 (4.6 (Core Profile) Mesa 23.0.3)
I0516 19:55:52.901378 32440 FrameBuffer.cpp:421] Graphics API Extensions GL_OES_EGL_sync GL_OES_EGL_image GL_OES_EGL_image_external GL_OES_depth24 GL_OES_depth32 GL_OES_element_index_uint GL_OES_texture_float GL_OES_texture_float_linear GL_OES_compressed_paletted_texture GL_OES_compressed_ETC1_RGB8_texture GL_OES_depth_texture GL_OES_texture_half_float GL_OES_texture_half_float_linear GL_OES_packed_depth_stencil GL_OES_vertex_half_float GL_OES_texture_npot GL_OES_rgb8_rgba8 GL_EXT_color_buffer_float GL_EXT_color_buffer_half_float GL_EXT_texture_format_BGRA8888 GL_APPLE_texture_format_BGRA8888
I0516 19:55:52.901386 32440 FrameBuffer.cpp:422] Graphics Device Extensions N/A
And the crash:
I0516 19:56:10.141743 32674 VkDecoderGlobalState.cpp:426] Creating Vulkan instance for app: Chromium
error: kvm run failed Bad address
RAX=00007c95f6287000 RBX=00007c95f63a0400 RCX=0000000000000000 RDX=0000000000119400
RSI=0000000000801000 RDI=00007c95f6287000 RBP=00007c95f6a88000 RSP=00007c95fafee080
R8 =00007c95f6288000 R9 =00007c95fafee110 R10=0000368e00347800 R11=00000000000000c0
R12=00007c95fafee110 R13=0000000000119400 R14=0000000000000000 R15=0000000000001680
RIP=00007c98fddfacf4 RFL=00000206 [-----P-] CPL=3 II=0 A20=1 SMM=0 HLT=0
ES =0000 0000000000000000 00000000 00000000
CS =0033 0000000000000000 ffffffff 00a0fb00 DPL=3 CS64 [-RA]
SS =002b 0000000000000000 ffffffff 00c0f300 DPL=3 DS [-WA]
DS =0000 0000000000000000 00000000 00000000
FS =0000 00007c95faff2000 00000000 00000000
GS =0000 00007c97d929e1b0 00000000 00000000
LDT=0000 0000000000000000 00000000 00000000
TR =0040 fffffe0000079000 00004087 00008b00 DPL=0 TSS64-busy
GDT= fffffe0000077000 0000007f
IDT= fffffe0000000000 00000fff
CR0=80050033 CR2=00007c95f6a88000 CR3=0000000062608000 CR4=000406a0
DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000
DR6=00000000ffff0ff0 DR7=0000000000000400
EFER=0000000000000d01
Code=41 0f 6f 4c 30 10 f3 41 0f 6f 54 30 20 f3 41 0f 6f 5c 30 30 <66> 41 0f 7f 00 41 0f 29 48 10 41 0f 29 50 20 41 0f 29 58 30 4d 8d 40 40 4c 39 c3 77 bf 48
Driver info:
lspci -k | grep -A 3 -E "(VGA|3D)"
0b:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] (rev c1)
Subsystem: Tul Corporation / PowerColor Navi 21 [Radeon RX 6800/6800 XT / 6900 XT]
Kernel driver in use: amdgpu
Kernel modules: amdgpu
Using the vulkan-radeon
package on arch linux.
bo...@google.com <bo...@google.com>
aw...@google.com <aw...@google.com> #14
We have made some fairly significant changes in how we interact with Vulkan in the Canary. Is it possible for you to try 33.1.6 (or the upcomming 33.1.12). I have successfully run on AMD+RADV on a 6900XT.
ro...@veeva.com <ro...@veeva.com> #15
Hi, I just tested 33.1.12
and it still freezes when opening Chrome if I start it from Android Studio.
I tried also to collect some logs starting it from command line with emulator -avd Nexus_5_API_30_Play -verbose -show-kernel &> emu.log
but it doesn't even start (see log attached).
Please let me know if I can help with some other tests.
mi...@gmail.com <mi...@gmail.com> #16
This happened to me too with the latest android 13 image, ryzen 5700g(iGPU), arch linux lates kernel. Running it with -feature -Vulkan
fixes it.
Bug report collection in the gui doesn't work, I let it run for at least 10 minutes and it didn't finish. I have attached the command line -verbose -show-kernel
logs.
aa...@gmail.com <aa...@gmail.com> #17
Hi, just tested the latest version 3.1.16
and that won;'t even boot (just a gray screen)
This is an Arch linux with vulkan drivers:
lspci -k | grep -A 3 -E "(VGA|3D)"
0b:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] (rev c1)
Subsystem: Tul Corporation / PowerColor Navi 21 [Radeon RX 6800/6800 XT / 6900 XT]
Kernel driver in use: amdgpu
Kernel modules: amdgpu
See attached log (with -verbose -show-kernel)
aw...@google.com <aw...@google.com> #18
X Error of failed request: BadDrawable (invalid Pixmap or Window parameter)
Major opcode of failed request: 155 (DRI2)
Minor opcode of failed request: 12 (DRI2SwapInterval )
Resource id in failed request: 0x5a00001
Serial number of failed request: 138
Current serial number in output stream: 139
DEBUG | Hostapd main loop has stopped.
This error should be fixed when 33.1.17 releases.
aw...@google.com <aw...@google.com>
ed...@gmail.com <ed...@gmail.com> #19
This was not and is not fixed.
This issue is regarding the emulator completely freezing after opening Chrome. This issue's title specifies as such and the issue is further detailed in the logs presented in
The issue where the emulator fails to boot in
(And only after writing a very lengthy comment here do I realize that this issue should likely be marked as a duplicate of
bo...@google.com <bo...@google.com>
pb...@gmail.com <pb...@gmail.com> #20
th...@mitutoyo-ctl.de <th...@mitutoyo-ctl.de> #21
Emulated device: Pixel 7, Medium Phone API 41, both Android 14, x86_64.
Description
Android Studio Version: Android Studio Electric Eel | 2022.1.1 Patch 2
Emulator Version (Emulator--> Extended Controls--> Emulator Version): 32.1.12-9751036 HAXM / KVM Version: KVM 12.0.0
Host Operating System: Ubuntu 22.04.2 LTS
CPU Manufacturer: AMD CPU Virtualization is supported 64-bit CPU
RAM: 64201 MB
GPU: AMD Radeon RX 7900 XTX
Build Fingerprint:
Steps to Reproduce Bug:
Expected Behavior:
Chrome opens and the emulator is still usable.
Observed Behavior:
The emulator freezes.