Closed Bug 1074063 Opened 10 years ago Closed 10 years ago

[MTBF][B2G] Missing rendering for launched apps

Categories

(Firefox OS Graveyard :: Gaia::System::Window Mgmt, defect)

Product:
Firefox OS Graveyard
Component:
Gaia::System::Window Mgmt
Platform:
ARM
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(blocking-b2g:2.1+, b2g-v2.1 fixed, b2g-v2.2 fixed)

Status:
VERIFIED FIXED
Milestone:
2.1 S7 (24Oct)
Project Flags:
blocking-b2g 2.1+
Tracking Flags:
Tracking Status
b2g-v2.1 --- fixed
b2g-v2.2 --- fixed

People

(Reporter: wachen, Assigned: alive)

References

Details

(Whiteboard: [mtbf])

Attachments

(8 files)

logcat201409291336-e472d80e-mtbf5
62.18 KB, text/x-vhdl
Details
white screen.png
11.32 KB, image/png
Details
FM Radio.png
31.91 KB, image/png
Details
20141013.zip
20.38 KB, application/zip
Details
output_debug_183.zip
453.84 KB, application/zip
Details
logcat.e444da63.zip
1.23 MB, application/zip
Details
output_debug_200.zip
392.54 KB, application/zip
Details
https://github.com/mozilla-b2g/gaia/pull/25448
46 bytes, text/x-github-pull-request
etienne
: review+
bajaj
: approval-gaia-v2.1+
Details | Review
The screen ends in empty app screen. If you tap on home button to go back to homescreen, it will go back to homescreen. However, if you reopen settings, fm radio, messages, and contacts, it would be white or black screen with only the search bar on top. FM radio sometimes would have really strange screen and I will attach the image. D/QSEECOMAPI: ( 9019): QSEECom_get_handle sb_length = 0x2000 D/QSEECOMAPI: ( 9019): App is not loaded in QSEE E/QSEECOMAPI: ( 9019): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt E/QSEECOMAPI: ( 9019): Error::Loading image failed with ret = -1 I/cat ( 270): <4>[245089.963923] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5300 D/QSEECOMAPI: ( 9019): QSEECom_get_handle sb_length = 0x2000 D/QSEECOMAPI: ( 9019): App is not loaded in QSEE E/QSEECOMAPI: ( 9019): Error::Cannot open the file /firmware/image/keymaste.mdt E/QSEECOMAPI: ( 9019): Error::Loading image failed with ret = -1 I/cat ( 270): <4>[245089.972636] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5300 E/QCOMKeyMaster( 9019): Loading keymaster app failied E/keystore( 9019): could not open keymaster device in keystore (Operation not permitted) E/keystore( 9019): keystore keymaster could not be initialized; exiting E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent] E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] D/QSEECOMAPI: ( 9020): QSEECom_get_handle sb_length = 0x2000 D/QSEECOMAPI: ( 9020): App is not loaded in QSEE E/QSEECOMAPI: ( 9020): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt E/QSEECOMAPI: ( 9020): Error::Loading image failed with ret = -1 I/cat ( 270): <4>[245095.005713] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5280 D/QSEECOMAPI: ( 9020): QSEECom_get_handle sb_length = 0x2000 D/QSEECOMAPI: ( 9020): App is not loaded in QSEE E/QSEECOMAPI: ( 9020): Error::Cannot open the file /firmware/image/keymaste.mdt E/QSEECOMAPI: ( 9020): Error::Loading image failed with ret = -1 I/cat ( 270): <4>[245095.015294] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5280 E/QCOMKeyMaster( 9020): Loading keymaster app failied E/keystore( 9020): could not open keymaster device in keystore (Operation not permitted) E/keystore( 9020): keystore keymaster could not be initialized; exiting E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent] E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] D/QSEECOMAPI: ( 9021): QSEECom_get_handle sb_length = 0x2000 D/QSEECOMAPI: ( 9021): App is not loaded in QSEE E/QSEECOMAPI: ( 9021): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt E/QSEECOMAPI: ( 9021): Error::Loading image failed with ret = -1 I/cat ( 270): <4>[245099.045301] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xd0572f80 D/QSEECOMAPI: ( 9021): QSEECom_get_handle sb_length = 0x2000 D/QSEECOMAPI: ( 9021): App is not loaded in QSEE E/QSEECOMAPI: ( 9021): Error::Cannot open the file /firmware/image/keymaste.mdt E/QSEECOMAPI: ( 9021): Error::Loading image failed with ret = -1 I/cat ( 270): <4>[245099.053443] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xd0572f80 E/QCOMKeyMaster( 9021): Loading keymaster app failied E/keystore( 9021): could not open keymaster device in keystore (Operation not permitted) E/keystore( 9021): keystore keymaster could not be initialized; exiting E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent] E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] D/QSEECOMAPI: ( 9022): QSEECom_get_handle sb_length = 0x2000 D/QSEECOMAPI: ( 9022): App is not loaded in QSEE E/QSEECOMAPI: ( 9022): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt E/QSEECOMAPI: ( 9022): Error::Loading image failed with ret = -1 I/cat ( 270): <4>[245104.084736] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5600 D/QSEECOMAPI: ( 9022): QSEECom_get_handle sb_length = 0x2000 D/QSEECOMAPI: ( 9022): App is not loaded in QSEE E/QSEECOMAPI: ( 9022): Error::Cannot open the file /firmware/image/keymaste.mdt E/QSEECOMAPI: ( 9022): Error::Loading image failed with ret = -1 I/cat ( 270): <4>[245104.093154] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5600 E/QCOMKeyMaster( 9022): Loading keymaster app failied E/keystore( 9022): could not open keymaster device in keystore (Operation not permitted) E/keystore( 9022): keystore keymaster could not be initialized; exiting
It might be related with bug 1065010. HOWEVER, PLEASE NOTICE there is a difference between this two bugs. In their situation, they stucked at the beginning of turnning the phone on. In our situation, we run around 2 hours to get this result and the phone is still kind of working
Blocks: MTBF-B2G
Sorry, the logcat is actually from mtbf-5 e472d80e.
Attached image white screen.png —
Attached image FM Radio.png —
Comment on attachment 8496692 [details] logcat201409291336-e472d80e-mtbf5 >--------- beginning of /dev/log/system >I/Vold ( 190): Vold 2.1 (the revenge) firing up >D/Vold ( 190): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media) >D/Vold ( 190): Volume sdcard1 state changing -1 (Initializing) -> 0 (No-Media) >D/Vold ( 190): Volume::createDeviceNode path:/dev/block/vold/179:32, major:179, minor:32 >D/Vold ( 190): Volume sdcard state changing 0 (No-Media) -> 1 (Idle-Unmounted) >D/Vold ( 190): Volume::createDeviceNode path:/dev/block/vold/179:0, major:179, minor:0 >D/Vold ( 190): Volume sdcard state changing 1 (Idle-Unmounted) -> 2 (Pending) >D/Vold ( 190): Volume::createDeviceNode path:/dev/block/vold/179:1, major:179, minor:1 >D/Vold ( 190): Volume::createDeviceNode path:/dev/block/vold/179:2, major:179, minor:2 >D/Vold ( 190): Volume::createDeviceNode path:/dev/block/vold/179:3, major:179, minor:3 >D/Vold ( 190): Volume::createDeviceNode path:/dev/block/vold/179:4, major:179, minor:4 >D/Vold ( 190): Volume::createDeviceNode path:/dev/block/vold/179:5, major:179, minor:5 >D/Vold ( 190): Volume::createDeviceNode path:/dev/block/vold/179:6, major:179, minor:6 >D/Vold ( 190): Volume::createDeviceNode path:/dev/block/vold/179:7, major:179, minor:7 >D/Vold ( 190): Volume::createDeviceNode path:/dev/block/vold/179:8, major:179, minor:8 >D/Vold ( 190): Volume::createDeviceNode path:/dev/block/vold/179:9, major:179, minor:9 >D/Vold ( 190): Volume::createDeviceNode path:/dev/block/vold/179:32, major:179, minor:32 >D/Vold ( 190): Volume sdcard state changing 2 (Pending) -> 1 (Idle-Unmounted) >D/Vold ( 190): Volume::createDeviceNode path:/dev/block/vold/179:10, major:179, minor:10 >W/Vold ( 190): Duplicate state (1) >D/Vold ( 190): Volume::createDeviceNode path:/dev/block/vold/179:11, major:179, minor:11 >W/Vold ( 190): Duplicate state (1) >D/Vold ( 190): Volume::createDeviceNode path:/dev/block/vold/179:12, major:179, minor:12 >W/Vold ( 190): Duplicate state (1) >D/Vold ( 190): Volume::createDeviceNode path:/dev/block/vold/179:13, major:179, minor:13 >W/Vold ( 190): Duplicate state (1) >D/Vold ( 190): Volume::createDeviceNode path:/dev/block/vold/179:14, major:179, minor:14 >W/Vold ( 190): Duplicate state (1) >D/Vold ( 190): Volume::createDeviceNode path:/dev/block/vold/179:15, major:179, minor:15 >W/Vold ( 190): Duplicate state (1) >D/Vold ( 190): Volume::createDeviceNode path:/dev/block/vold/179:16, major:179, minor:16 >W/Vold ( 190): Duplicate state (1) >D/Vold ( 190): Volume::createDeviceNode path:/dev/block/vold/179:17, major:179, minor:17 >W/Vold ( 190): Duplicate state (1) >D/Vold ( 190): Volume::createDeviceNode path:/dev/block/vold/179:18, major:179, minor:18 >W/Vold ( 190): Duplicate state (1) >D/Vold ( 190): Volume::createDeviceNode path:/dev/block/vold/179:19, major:179, minor:19 >W/Vold ( 190): Duplicate state (1) >D/Vold ( 190): Volume::createDeviceNode path:/dev/block/vold/179:20, major:179, minor:20 >W/Vold ( 190): Duplicate state (1) >D/Vold ( 190): Volume::createDeviceNode path:/dev/block/vold/179:21, major:179, minor:21 >W/Vold ( 190): Duplicate state (1) >D/Vold ( 190): Volume::createDeviceNode path:/dev/block/vold/179:22, major:179, minor:22 >W/Vold ( 190): Duplicate state (1) >D/Vold ( 190): Volume::createDeviceNode path:/dev/block/vold/179:23, major:179, minor:23 >W/Vold ( 190): Duplicate state (1) >D/Vold ( 190): Volume::createDeviceNode path:/dev/block/vold/179:24, major:179, minor:24 >W/Vold ( 190): Duplicate state (1) >D/Vold ( 190): Volume::createDeviceNode path:/dev/block/vold/179:25, major:179, minor:25 >W/Vold ( 190): Duplicate state (1) >D/Vold ( 190): Volume::createDeviceNode path:/dev/block/vold/179:26, major:179, minor:26 >W/Vold ( 190): Duplicate state (1) >D/Vold ( 190): Volume::createDeviceNode path:/dev/block/vold/179:27, major:179, minor:27 >W/Vold ( 190): Duplicate state (1) >D/Vold ( 190): Volume::createDeviceNode path:/dev/block/vold/179:28, major:179, minor:28 >W/Vold ( 190): Duplicate state (1) >D/Vold ( 190): Volume::createDeviceNode path:/dev/block/vold/179:29, major:179, minor:29 >W/Vold ( 190): Duplicate state (1) >D/Vold ( 190): Volume::createDeviceNode path:/dev/block/vold/179:30, major:179, minor:30 >W/Vold ( 190): Duplicate state (1) >D/Vold ( 190): Volume::createDeviceNode path:/dev/block/vold/179:64, major:179, minor:64 >D/Vold ( 190): Volume sdcard1 state changing 0 (No-Media) -> 2 (Pending) >D/Vold ( 190): Volume::createDeviceNode path:/dev/block/vold/179:65, major:179, minor:65 >D/Vold ( 190): Volume sdcard1 state changing 2 (Pending) -> 1 (Idle-Unmounted) >E/Vold ( 190): Volume::mountVol DeviceNodes n:1 >I/Vold ( 190): /dev/block/vold/179:30 being considered for volume sdcard >D/Vold ( 190): Volume sdcard state changing 1 (Idle-Unmounted) -> 3 (Checking) >D/fsck_msdos( 608): sectors Per cluster :8 >D/fsck_msdos( 608): boot->ClusterOffset :15744 >I/fsck_msdos( 608): FAT32 Filesystem >D/fsck_msdos( 608): Using cluster_chain_descriptor >I/fsck_msdos( 608): Total clusters 1005642 >I/fsck_msdos( 608): Begin to compare FAT >I/fsck_msdos( 608): ** Phase 2 - Check Cluster Chains >I/fsck_msdos( 608): Begin to handle the cluster chain >D/fsck_msdos( 608): rootDir->head :2 >D/fsck_msdos( 608): Verify Filesystem information >W/fsck_msdos( 608): 2 files, 4022552 free (1005638 clusters) >I/fsck_msdos( 608): free_rb_tree >I/fsck_msdos( 608): free_fragment_tree >I/fsck_msdos( 608): free_fragment_tree >I/fsck_msdos( 608): free_fragment_tree: rb_tree is empty >I/Vold ( 190): Filesystem check completed OK >D/Vold ( 190): Volume sdcard state changing 3 (Checking) -> 4 (Mounted) >E/Vold ( 190): Volume::mountVol DeviceNodes n:1 >I/Vold ( 190): /dev/block/vold/179:65 being considered for volume sdcard1 >D/Vold ( 190): Volume sdcard1 state changing 1 (Idle-Unmounted) -> 3 (Checking) >D/fsck_msdos( 644): sectors Per cluster :64 >D/fsck_msdos( 644): boot->ClusterOffset :375 >I/fsck_msdos( 644): FAT16 Fielsystem >D/fsck_msdos( 644): Using cluster_chain_descriptor >I/fsck_msdos( 644): Total clusters 60024 >I/fsck_msdos( 644): Begin to compare FAT >I/fsck_msdos( 644): ** Phase 2 - Check Cluster Chains >I/fsck_msdos( 644): Begin to handle the cluster chain >D/fsck_msdos( 644): rootDir->head :0 >D/fsck_msdos( 644): Verify Filesystem information >W/fsck_msdos( 644): 2 files, 1920672 free (60021 clusters) >I/fsck_msdos( 644): free_rb_tree >I/fsck_msdos( 644): free_fragment_tree >I/fsck_msdos( 644): free_fragment_tree >I/fsck_msdos( 644): free_fragment_tree: rb_tree is empty >I/Vold ( 190): Filesystem check completed OK >D/Vold ( 190): Volume sdcard1 state changing 3 (Checking) -> 4 (Mounted) >D/NetlinkEvent( 196): Unexpected netlink message. type=0x11 >D/NetlinkEvent( 196): Unexpected netlink message. type=0x11 >D/NetlinkEvent( 196): Unexpected netlink message. type=0x11 >D/NetlinkEvent( 196): Unexpected netlink message. type=0x11 >D/NetlinkEvent( 196): Unexpected netlink message. type=0x11 >D/NetlinkEvent( 196): Unexpected netlink message. type=0x11 >D/NetlinkEvent( 196): Unexpected netlink message. type=0x11 >D/NetlinkEvent( 196): Unexpected netlink message. type=0x11 >D/NetlinkEvent( 196): Unexpected netlink message. type=0x11 >D/NetlinkEvent( 196): Unexpected netlink message. type=0x11 >D/NetlinkEvent( 196): Unexpected netlink message. type=0x11 >D/NetlinkEvent( 196): Unexpected netlink message. type=0x11 >D/NetlinkEvent( 196): Unexpected netlink message. type=0x11 >D/NetlinkEvent( 196): Unexpected netlink message. type=0x11 >W/SocketClient( 196): write error (Broken pipe) >--------- beginning of /dev/log/main >E/QSEECOMAPI: ( 9066): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245314.925313] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5200 >D/QSEECOMAPI: ( 9066): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9066): App is not loaded in QSEE >E/QSEECOMAPI: ( 9066): Error::Cannot open the file /firmware/image/keymaste.mdt >E/QSEECOMAPI: ( 9066): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245314.934280] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5200 >E/QCOMKeyMaster( 9066): Loading keymaster app failied >E/keystore( 9066): could not open keymaster device in keystore (Operation not permitted) >E/keystore( 9066): keystore keymaster could not be initialized; exiting >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent] >E/Diag_Lib( 293): Thread state: conn_id=0, state=RX_THREAD_WAIT_READ >E/Diag_Lib( 293): Thread state: conn_id=0, state=RX_THREAD_CLIENT_TX >E/Diag_Lib( 293): qmi_qmux: TX/RX - RX 17 bytes on conn_id=0 >E/Diag_Lib( 293): 01 10 00 80 03 02 04 D4 1C 51 00 04 00 12 01 00 >E/Diag_Lib( 293): B4 >E/Diag_Lib( 293): qmuxd: TX message on fd=30, to qmux_client_id=0x1, len=51 >E/Diag_Lib( 293): Thread state: conn_id=0, state=RX_THREAD_WAIT_POLL >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] >D/QSEECOMAPI: ( 9067): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9067): App is not loaded in QSEE >E/QSEECOMAPI: ( 9067): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt >E/QSEECOMAPI: ( 9067): Error::Loading image failed with ret = -1 >D/QSEECOMAPI: ( 9067): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9067): App is not loaded in QSEE >E/QSEECOMAPI: ( 9067): Error::Cannot open the file /firmware/image/keymaste.mdt >E/QSEECOMAPI: ( 9067): Error::Loading image failed with ret = -1 >E/QCOMKeyMaster( 9067): Loading keymaster app failied >E/keystore( 9067): could not open keymaster device in keystore (Operation not permitted) >E/keystore( 9067): keystore keymaster could not be initialized; exiting >I/cat ( 270): <4>[245319.969298] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xc2f71c80 >I/cat ( 270): <4>[245319.977224] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xc2f71c80 >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] >E/Diag_Lib( 293): Thread state: conn_id=0, state=RX_THREAD_WAIT_READ >E/Diag_Lib( 293): Thread state: conn_id=0, state=RX_THREAD_CLIENT_TX >E/Diag_Lib( 293): qmi_qmux: TX/RX - RX 17 bytes on conn_id=0 >E/Diag_Lib( 293): 01 10 00 80 03 02 04 D5 1C 51 00 04 00 12 01 00 >E/Diag_Lib( 293): B6 >E/Diag_Lib( 293): qmuxd: TX message on fd=30, to qmux_client_id=0x1, len=51 >E/Diag_Lib( 293): Thread state: conn_id=0, state=RX_THREAD_WAIT_POLL >I/cat ( 270): <6>[245325.031078] mmc0: Starting deferred resume >I/cat ( 270): <6>[245325.090533] mmc0: Deferred resume completed >D/QSEECOMAPI: ( 9068): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9068): App is not loaded in QSEE >E/QSEECOMAPI: ( 9068): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt >E/QSEECOMAPI: ( 9068): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245325.116671] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5f80 >D/QSEECOMAPI: ( 9068): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9068): App is not loaded in QSEE >E/QSEECOMAPI: ( 9068): Error::Cannot open the file /firmware/image/keymaste.mdt >E/QSEECOMAPI: ( 9068): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245325.124249] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5f80 >E/QCOMKeyMaster( 9068): Loading keymaster app failied >E/keystore( 9068): could not open keymaster device in keystore (Operation not permitted) >E/keystore( 9068): keystore keymaster could not be initialized; exiting >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] >D/QSEECOMAPI: ( 9069): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9069): App is not loaded in QSEE >E/QSEECOMAPI: ( 9069): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt >E/QSEECOMAPI: ( 9069): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245330.166237] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5f00 >D/QSEECOMAPI: ( 9069): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9069): App is not loaded in QSEE >E/QSEECOMAPI: ( 9069): Error::Cannot open the file /firmware/image/keymaste.mdt >E/QSEECOMAPI: ( 9069): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245330.173808] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5f00 >E/QCOMKeyMaster( 9069): Loading keymaster app failied >E/keystore( 9069): could not open keymaster device in keystore (Operation not permitted) >E/keystore( 9069): keystore keymaster could not be initialized; exiting >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] >D/QSEECOMAPI: ( 9070): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9070): App is not loaded in QSEE >E/QSEECOMAPI: ( 9070): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt >E/QSEECOMAPI: ( 9070): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245335.205386] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5080 >D/QSEECOMAPI: ( 9070): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9070): App is not loaded in QSEE >E/QSEECOMAPI: ( 9070): Error::Cannot open the file /firmware/image/keymaste.mdt >E/QSEECOMAPI: ( 9070): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245335.213706] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5080 >E/QCOMKeyMaster( 9070): Loading keymaster app failied >E/keystore( 9070): could not open keymaster device in keystore (Operation not permitted) >E/keystore( 9070): keystore keymaster could not be initialized; exiting >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] >D/QSEECOMAPI: ( 9071): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9071): App is not loaded in QSEE >E/QSEECOMAPI: ( 9071): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt >E/QSEECOMAPI: ( 9071): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245340.242127] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5800 >D/QSEECOMAPI: ( 9071): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9071): App is not loaded in QSEE >E/QSEECOMAPI: ( 9071): Error::Cannot open the file /firmware/image/keymaste.mdt >E/QSEECOMAPI: ( 9071): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245340.256418] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5800 >E/QCOMKeyMaster( 9071): Loading keymaster app failied >E/keystore( 9071): could not open keymaster device in keystore (Operation not permitted) >E/keystore( 9071): keystore keymaster could not be initialized; exiting >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] >D/QSEECOMAPI: ( 9072): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9072): App is not loaded in QSEE >E/QSEECOMAPI: ( 9072): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt >E/QSEECOMAPI: ( 9072): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245345.296996] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5800 >D/QSEECOMAPI: ( 9072): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9072): App is not loaded in QSEE >E/QSEECOMAPI: ( 9072): Error::Cannot open the file /firmware/image/keymaste.mdt >E/QSEECOMAPI: ( 9072): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245345.305117] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5800 >E/QCOMKeyMaster( 9072): Loading keymaster app failied >E/keystore( 9072): could not open keymaster device in keystore (Operation not permitted) >E/keystore( 9072): keystore keymaster could not be initialized; exiting >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] >I/cat ( 270): <6>[245347.801526] mmc0: Starting deferred resume >I/cat ( 270): <6>[245347.856931] mmc0: Deferred resume completed >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] >D/QSEECOMAPI: ( 9073): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9073): App is not loaded in QSEE >E/QSEECOMAPI: ( 9073): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt >E/QSEECOMAPI: ( 9073): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245350.336258] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5880 >D/QSEECOMAPI: ( 9073): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9073): App is not loaded in QSEE >E/QSEECOMAPI: ( 9073): Error::Cannot open the file /firmware/image/keymaste.mdt >E/QSEECOMAPI: ( 9073): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245350.352637] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xc6464880 >E/QCOMKeyMaster( 9073): Loading keymaster app failied >E/keystore( 9073): could not open keymaster device in keystore (Operation not permitted) >E/keystore( 9073): keystore keymaster could not be initialized; exiting >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [LOWI-SERVER] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] >D/QSEECOMAPI: ( 9074): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9074): App is not loaded in QSEE >E/QSEECOMAPI: ( 9074): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt >E/QSEECOMAPI: ( 9074): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245355.382739] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5d00 >D/QSEECOMAPI: ( 9074): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9074): App is not loaded in QSEE >E/QSEECOMAPI: ( 9074): Error::Cannot open the file /firmware/image/keymaste.mdt >E/QSEECOMAPI: ( 9074): Error::Loading image failed with ret = -1 >E/QCOMKeyMaster( 9074): Loading keymaster app failied >E/keystore( 9074): could not open keymaster device in keystore (Operation not permitted) >E/keystore( 9074): keystore keymaster could not be initialized; exiting >I/cat ( 270): <4>[245355.390277] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5d00 >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] >D/QSEECOMAPI: ( 9076): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9076): App is not loaded in QSEE >E/QSEECOMAPI: ( 9076): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt >E/QSEECOMAPI: ( 9076): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245360.421434] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5d00 >D/QSEECOMAPI: ( 9076): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9076): App is not loaded in QSEE >E/QSEECOMAPI: ( 9076): Error::Cannot open the file /firmware/image/keymaste.mdt >E/QSEECOMAPI: ( 9076): Error::Loading image failed with ret = -1 >E/QCOMKeyMaster( 9076): Loading keymaster app failied >E/keystore( 9076): could not open keymaster device in keystore (Operation not permitted) >E/keystore( 9076): keystore keymaster could not be initialized; exiting >I/cat ( 270): <4>[245360.430219] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5d00 >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] >D/QSEECOMAPI: ( 9077): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9077): App is not loaded in QSEE >E/QSEECOMAPI: ( 9077): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt >E/QSEECOMAPI: ( 9077): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245365.467318] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5500 >D/QSEECOMAPI: ( 9077): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9077): App is not loaded in QSEE >E/QSEECOMAPI: ( 9077): Error::Cannot open the file /firmware/image/keymaste.mdt >E/QSEECOMAPI: ( 9077): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245365.474943] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5500 >E/QCOMKeyMaster( 9077): Loading keymaster app failied >E/keystore( 9077): could not open keymaster device in keystore (Operation not permitted) >E/keystore( 9077): keystore keymaster could not be initialized; exiting >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] >D/QSEECOMAPI: ( 9078): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9078): App is not loaded in QSEE >E/QSEECOMAPI: ( 9078): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt >E/QSEECOMAPI: ( 9078): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245370.506301] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5300 >D/QSEECOMAPI: ( 9078): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9078): App is not loaded in QSEE >E/QSEECOMAPI: ( 9078): Error::Cannot open the file /firmware/image/keymaste.mdt >E/QSEECOMAPI: ( 9078): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245370.514431] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5300 >E/QCOMKeyMaster( 9078): Loading keymaster app failied >E/keystore( 9078): could not open keymaster device in keystore (Operation not permitted) >E/keystore( 9078): keystore keymaster could not be initialized; exiting >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] >D/QSEECOMAPI: ( 9079): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9079): App is not loaded in QSEE >E/QSEECOMAPI: ( 9079): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt >E/QSEECOMAPI: ( 9079): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245375.541975] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5b00 >D/QSEECOMAPI: ( 9079): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9079): App is not loaded in QSEE >E/QSEECOMAPI: ( 9079): Error::Cannot open the file /firmware/image/keymaste.mdt >E/QSEECOMAPI: ( 9079): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245375.555805] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5b00 >E/QCOMKeyMaster( 9079): Loading keymaster app failied >E/keystore( 9079): could not open keymaster device in keystore (Operation not permitted) >E/keystore( 9079): keystore keymaster could not be initialized; exiting >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] >D/QSEECOMAPI: ( 9080): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9080): App is not loaded in QSEE >E/QSEECOMAPI: ( 9080): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt >E/QSEECOMAPI: ( 9080): Error::Loading image failed with ret = -1 >D/QSEECOMAPI: ( 9080): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9080): App is not loaded in QSEE >E/QSEECOMAPI: ( 9080): Error::Cannot open the file /firmware/image/keymaste.mdt >E/QSEECOMAPI: ( 9080): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245380.600439] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5f00 >I/cat ( 270): <4>[245380.607759] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5f00 >E/QCOMKeyMaster( 9080): Loading keymaster app failied >E/keystore( 9080): could not open keymaster device in keystore (Operation not permitted) >E/keystore( 9080): keystore keymaster could not be initialized; exiting >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] >D/QSEECOMAPI: ( 9081): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9081): App is not loaded in QSEE >E/QSEECOMAPI: ( 9081): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt >E/QSEECOMAPI: ( 9081): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245385.640144] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5880 >D/QSEECOMAPI: ( 9081): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9081): App is not loaded in QSEE >E/QSEECOMAPI: ( 9081): Error::Cannot open the file /firmware/image/keymaste.mdt >E/QSEECOMAPI: ( 9081): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245385.653714] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5880 >E/QCOMKeyMaster( 9081): Loading keymaster app failied >E/keystore( 9081): could not open keymaster device in keystore (Operation not permitted) >E/keystore( 9081): keystore keymaster could not be initialized; exiting >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] >D/QSEECOMAPI: ( 9082): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9082): App is not loaded in QSEE >E/QSEECOMAPI: ( 9082): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt >E/QSEECOMAPI: ( 9082): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245390.684014] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xc2f71f00 >D/QSEECOMAPI: ( 9082): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9082): App is not loaded in QSEE >E/QSEECOMAPI: ( 9082): Error::Cannot open the file /firmware/image/keymaste.mdt >E/QSEECOMAPI: ( 9082): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245390.691565] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xc2f71f00 >E/QCOMKeyMaster( 9082): Loading keymaster app failied >E/keystore( 9082): could not open keymaster device in keystore (Operation not permitted) >E/keystore( 9082): keystore keymaster could not be initialized; exiting >E/Diag_Lib( 293): Thread state: conn_id=0, state=RX_THREAD_WAIT_READ >E/Diag_Lib( 293): Thread state: conn_id=0, state=RX_THREAD_CLIENT_TX >E/Diag_Lib( 293): qmi_qmux: TX/RX - RX 17 bytes on conn_id=0 >E/Diag_Lib( 293): 01 10 00 80 03 02 04 D6 1C 51 00 04 00 12 01 00 >E/Diag_Lib( 293): BA >E/Diag_Lib( 293): qmuxd: TX message on fd=30, to qmux_client_id=0x1, len=51 >E/Diag_Lib( 293): Thread state: conn_id=0, state=RX_THREAD_WAIT_POLL >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] >E/Diag_Lib( 293): Thread state: conn_id=0, state=RX_THREAD_WAIT_READ >E/Diag_Lib( 293): Thread state: conn_id=0, state=RX_THREAD_CLIENT_TX >E/Diag_Lib( 293): qmi_qmux: TX/RX - RX 17 bytes on conn_id=0 >E/Diag_Lib( 293): 01 10 00 80 03 02 04 D7 1C 51 00 04 00 12 01 00 >E/Diag_Lib( 293): B8 >E/Diag_Lib( 293): qmuxd: TX message on fd=30, to qmux_client_id=0x1, len=51 >E/Diag_Lib( 293): Thread state: conn_id=0, state=RX_THREAD_WAIT_POLL >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] >D/QSEECOMAPI: ( 9083): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9083): App is not loaded in QSEE >E/QSEECOMAPI: ( 9083): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt >E/QSEECOMAPI: ( 9083): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245395.740953] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5780 >D/QSEECOMAPI: ( 9083): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9083): App is not loaded in QSEE >E/QSEECOMAPI: ( 9083): Error::Cannot open the file /firmware/image/keymaste.mdt >E/QSEECOMAPI: ( 9083): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245395.754187] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5780 >E/QCOMKeyMaster( 9083): Loading keymaster app failied >E/keystore( 9083): could not open keymaster device in keystore (Operation not permitted) >E/keystore( 9083): keystore keymaster could not be initialized; exiting >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] >D/QSEECOMAPI: ( 9084): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9084): App is not loaded in QSEE >E/QSEECOMAPI: ( 9084): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt >E/QSEECOMAPI: ( 9084): Error::Loading image failed with ret = -1 >D/QSEECOMAPI: ( 9084): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9084): App is not loaded in QSEE >E/QSEECOMAPI: ( 9084): Error::Cannot open the file /firmware/image/keymaste.mdt >E/QSEECOMAPI: ( 9084): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245400.785122] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5980 >I/cat ( 270): <4>[245400.792509] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5980 >E/QCOMKeyMaster( 9084): Loading keymaster app failied >E/keystore( 9084): could not open keymaster device in keystore (Operation not permitted) >E/keystore( 9084): keystore keymaster could not be initialized; exiting >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] >D/QSEECOMAPI: ( 9085): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9085): App is not loaded in QSEE >E/QSEECOMAPI: ( 9085): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt >E/QSEECOMAPI: ( 9085): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245405.824064] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5980 >D/QSEECOMAPI: ( 9085): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9085): App is not loaded in QSEE >E/QSEECOMAPI: ( 9085): Error::Cannot open the file /firmware/image/keymaste.mdt >E/QSEECOMAPI: ( 9085): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245405.832956] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5980 >E/QCOMKeyMaster( 9085): Loading keymaster app failied >E/keystore( 9085): could not open keymaster device in keystore (Operation not permitted) >E/keystore( 9085): keystore keymaster could not be initialized; exiting >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] >D/QSEECOMAPI: ( 9086): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9086): App is not loaded in QSEE >E/QSEECOMAPI: ( 9086): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt >E/QSEECOMAPI: ( 9086): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245410.868861] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5600 >D/QSEECOMAPI: ( 9086): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9086): App is not loaded in QSEE >E/QSEECOMAPI: ( 9086): Error::Cannot open the file /firmware/image/keymaste.mdt >E/QSEECOMAPI: ( 9086): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245410.876615] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5600 >E/QCOMKeyMaster( 9086): Loading keymaster app failied >E/keystore( 9086): could not open keymaster device in keystore (Operation not permitted) >E/keystore( 9086): keystore keymaster could not be initialized; exiting >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [LOWI-SERVER] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] >D/QSEECOMAPI: ( 9087): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9087): App is not loaded in QSEE >E/QSEECOMAPI: ( 9087): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt >E/QSEECOMAPI: ( 9087): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245415.908689] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xc2f71600 >D/QSEECOMAPI: ( 9087): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9087): App is not loaded in QSEE >E/QSEECOMAPI: ( 9087): Error::Cannot open the file /firmware/image/keymaste.mdt >E/QSEECOMAPI: ( 9087): Error::Loading image failed with ret = -1 >E/QCOMKeyMaster( 9087): Loading keymaster app failied >I/cat ( 270): <4>[245415.916826] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xc2f71600 >E/keystore( 9087): could not open keymaster device in keystore (Operation not permitted) >E/keystore( 9087): keystore keymaster could not be initialized; exiting >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] >D/QSEECOMAPI: ( 9088): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9088): App is not loaded in QSEE >E/QSEECOMAPI: ( 9088): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt >E/QSEECOMAPI: ( 9088): Error::Loading image failed with ret = -1 >D/QSEECOMAPI: ( 9088): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9088): App is not loaded in QSEE >E/QSEECOMAPI: ( 9088): Error::Cannot open the file /firmware/image/keymaste.mdt >I/cat ( 270): <4>[245420.967516] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xc6464700 >E/QSEECOMAPI: ( 9088): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245420.975035] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xc6464700 >E/QCOMKeyMaster( 9088): Loading keymaster app failied >E/keystore( 9088): could not open keymaster device in keystore (Operation not permitted) >E/keystore( 9088): keystore keymaster could not be initialized; exiting >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] >E/Diag_Lib( 293): Thread state: conn_id=0, state=RX_THREAD_WAIT_READ >E/Diag_Lib( 293): Thread state: conn_id=0, state=RX_THREAD_CLIENT_TX >E/Diag_Lib( 293): qmi_qmux: TX/RX - RX 17 bytes on conn_id=0 >E/Diag_Lib( 293): 01 10 00 80 03 02 04 D8 1C 51 00 04 00 12 01 00 >E/Diag_Lib( 293): B3 >E/Diag_Lib( 293): qmuxd: TX message on fd=30, to qmux_client_id=0x1, len=51 >E/Diag_Lib( 293): Thread state: conn_id=0, state=RX_THREAD_WAIT_POLL >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] >D/QSEECOMAPI: ( 9089): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9089): App is not loaded in QSEE >E/QSEECOMAPI: ( 9089): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt >E/QSEECOMAPI: ( 9089): Error::Loading image failed with ret = -1 >D/QSEECOMAPI: ( 9089): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9089): App is not loaded in QSEE >E/QSEECOMAPI: ( 9089): Error::Cannot open the file /firmware/image/keymaste.mdt >E/QSEECOMAPI: ( 9089): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245426.009534] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5d80 >I/cat ( 270): <4>[245426.016886] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5d80 >E/QCOMKeyMaster( 9089): Loading keymaster app failied >E/keystore( 9089): could not open keymaster device in keystore (Operation not permitted) >E/keystore( 9089): keystore keymaster could not be initialized; exiting >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] >D/QSEECOMAPI: ( 9090): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9090): App is not loaded in QSEE >E/QSEECOMAPI: ( 9090): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt >E/QSEECOMAPI: ( 9090): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245430.044387] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5100 >D/QSEECOMAPI: ( 9090): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9090): App is not loaded in QSEE >E/QSEECOMAPI: ( 9090): Error::Cannot open the file /firmware/image/keymaste.mdt >E/QSEECOMAPI: ( 9090): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245430.052053] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5100 >E/QCOMKeyMaster( 9090): Loading keymaster app failied >E/keystore( 9090): could not open keymaster device in keystore (Operation not permitted) >E/keystore( 9090): keystore keymaster could not be initialized; exiting >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] >D/QSEECOMAPI: ( 9091): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9091): App is not loaded in QSEE >E/QSEECOMAPI: ( 9091): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt >E/QSEECOMAPI: ( 9091): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245435.096394] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xc2f71f00 >D/QSEECOMAPI: ( 9091): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9091): App is not loaded in QSEE >E/QSEECOMAPI: ( 9091): Error::Cannot open the file /firmware/image/keymaste.mdt >E/QSEECOMAPI: ( 9091): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245435.104033] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xc2f71f00 >E/QCOMKeyMaster( 9091): Loading keymaster app failied >E/keystore( 9091): could not open keymaster device in keystore (Operation not permitted) >E/keystore( 9091): keystore keymaster could not be initialized; exiting >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] >D/QSEECOMAPI: ( 9092): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9092): App is not loaded in QSEE >E/QSEECOMAPI: ( 9092): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt >E/QSEECOMAPI: ( 9092): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245440.140518] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xc6464d80 >D/QSEECOMAPI: ( 9092): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9092): App is not loaded in QSEE >E/QSEECOMAPI: ( 9092): Error::Cannot open the file /firmware/image/keymaste.mdt >E/QSEECOMAPI: ( 9092): Error::Loading image failed with ret = -1 >E/Diag_Lib( 293): Thread state: conn_id=0, state=RX_THREAD_WAIT_READ >E/Diag_Lib( 293): Thread state: conn_id=0, state=RX_THREAD_CLIENT_TX >E/Diag_Lib( 293): qmi_qmux: TX/RX - RX 17 bytes on conn_id=0 >E/Diag_Lib( 293): 01 10 00 80 03 02 04 D9 1C 51 00 04 00 12 01 00 >E/Diag_Lib( 293): B5 >E/Diag_Lib( 293): qmuxd: TX message on fd=30, to qmux_client_id=0x1, len=51 >E/Diag_Lib( 293): Thread state: conn_id=0, state=RX_THREAD_WAIT_POLL >I/cat ( 270): <4>[245440.154713] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xc6464d80 >E/QCOMKeyMaster( 9092): Loading keymaster app failied >E/keystore( 9092): could not open keymaster device in keystore (Operation not permitted) >E/keystore( 9092): keystore keymaster could not be initialized; exiting >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] >D/QSEECOMAPI: ( 9093): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9093): App is not loaded in QSEE >E/QSEECOMAPI: ( 9093): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt >E/QSEECOMAPI: ( 9093): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245445.195972] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xc6464380 >D/QSEECOMAPI: ( 9093): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9093): App is not loaded in QSEE >E/QSEECOMAPI: ( 9093): Error::Cannot open the file /firmware/image/keymaste.mdt >E/QSEECOMAPI: ( 9093): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245445.203618] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xc6464380 >E/QCOMKeyMaster( 9093): Loading keymaster app failied >E/keystore( 9093): could not open keymaster device in keystore (Operation not permitted) >E/keystore( 9093): keystore keymaster could not be initialized; exiting >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] >D/QSEECOMAPI: ( 9094): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9094): App is not loaded in QSEE >E/QSEECOMAPI: ( 9094): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt >E/QSEECOMAPI: ( 9094): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245450.241102] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xc6464d00 >D/QSEECOMAPI: ( 9094): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9094): App is not loaded in QSEE >E/QSEECOMAPI: ( 9094): Error::Cannot open the file /firmware/image/keymaste.mdt >E/QSEECOMAPI: ( 9094): Error::Loading image failed with ret = -1 >E/QCOMKeyMaster( 9094): Loading keymaster app failied >E/keystore( 9094): could not open keymaster device in keystore (Operation not permitted) >E/keystore( 9094): keystore keymaster could not be initialized; exiting >I/cat ( 270): <4>[245450.260909] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xc6464d00 >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] >I/cat ( 270): <6>[245454.763896] mmc0: Starting deferred resume >I/cat ( 270): <6>[245454.818179] mmc0: Deferred resume completed >D/QSEECOMAPI: ( 9098): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9098): App is not loaded in QSEE >E/QSEECOMAPI: ( 9098): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt >E/QSEECOMAPI: ( 9098): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245455.291113] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xc192f800 >D/QSEECOMAPI: ( 9098): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9098): App is not loaded in QSEE >E/QSEECOMAPI: ( 9098): Error::Cannot open the file /firmware/image/keymaste.mdt >E/QSEECOMAPI: ( 9098): Error::Loading image failed with ret = -1 >E/QCOMKeyMaster( 9098): Loading keymaster app failied >E/keystore( 9098): could not open keymaster device in keystore (Operation not permitted) >E/keystore( 9098): keystore keymaster could not be initialized; exiting >I/cat ( 270): <4>[245455.300289] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xc192f800 >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] >E/Diag_Lib( 293): Thread state: conn_id=0, state=RX_THREAD_WAIT_READ >E/Diag_Lib( 293): Thread state: conn_id=0, state=RX_THREAD_CLIENT_TX >E/Diag_Lib( 293): qmi_qmux: TX/RX - RX 17 bytes on conn_id=0 >E/Diag_Lib( 293): 01 10 00 80 03 02 04 DA 1C 51 00 04 00 12 01 00 >E/Diag_Lib( 293): B4 >E/Diag_Lib( 293): qmuxd: TX message on fd=30, to qmux_client_id=0x1, len=51 >E/Diag_Lib( 293): Thread state: conn_id=0, state=RX_THREAD_WAIT_POLL >D/QSEECOMAPI: ( 9099): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9099): App is not loaded in QSEE >E/QSEECOMAPI: ( 9099): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt >E/QSEECOMAPI: ( 9099): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245460.348600] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xcf4f8e00 >D/QSEECOMAPI: ( 9099): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9099): App is not loaded in QSEE >E/QSEECOMAPI: ( 9099): Error::Cannot open the file /firmware/image/keymaste.mdt >E/QSEECOMAPI: ( 9099): Error::Loading image failed with ret = -1 >E/QCOMKeyMaster( 9099): Loading keymaster app failied >E/keystore( 9099): could not open keymaster device in keystore (Operation not permitted) >E/keystore( 9099): keystore keymaster could not be initialized; exiting >I/cat ( 270): <4>[245460.363149] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xcf4f8e00 >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] >E/Diag_Lib( 293): Thread state: conn_id=0, state=RX_THREAD_WAIT_READ >E/Diag_Lib( 293): Thread state: conn_id=0, state=RX_THREAD_CLIENT_TX >E/Diag_Lib( 293): qmi_qmux: TX/RX - RX 17 bytes on conn_id=0 >E/Diag_Lib( 293): 01 10 00 80 03 02 04 DB 1C 51 00 04 00 12 01 00 >E/Diag_Lib( 293): B6 >E/Diag_Lib( 293): qmuxd: TX message on fd=30, to qmux_client_id=0x1, len=51 >E/Diag_Lib( 293): Thread state: conn_id=0, state=RX_THREAD_WAIT_POLL >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] >D/QSEECOMAPI: ( 9102): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9102): App is not loaded in QSEE >E/QSEECOMAPI: ( 9102): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt >E/QSEECOMAPI: ( 9102): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245465.401625] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5600 >D/QSEECOMAPI: ( 9102): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9102): App is not loaded in QSEE >E/QSEECOMAPI: ( 9102): Error::Cannot open the file /firmware/image/keymaste.mdt >E/QSEECOMAPI: ( 9102): Error::Loading image failed with ret = -1 >E/QCOMKeyMaster( 9102): Loading keymaster app failied >E/keystore( 9102): could not open keymaster device in keystore (Operation not permitted) >E/keystore( 9102): keystore keymaster could not be initialized; exiting >I/cat ( 270): <4>[245465.409365] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5600 >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] >D/QSEECOMAPI: ( 9105): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9105): App is not loaded in QSEE >E/QSEECOMAPI: ( 9105): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt >E/QSEECOMAPI: ( 9105): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245470.441071] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5180 >D/QSEECOMAPI: ( 9105): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9105): App is not loaded in QSEE >E/QSEECOMAPI: ( 9105): Error::Cannot open the file /firmware/image/keymaste.mdt >E/QSEECOMAPI: ( 9105): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245470.454974] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5180 >E/QCOMKeyMaster( 9105): Loading keymaster app failied >E/keystore( 9105): could not open keymaster device in keystore (Operation not permitted) >E/keystore( 9105): keystore keymaster could not be initialized; exiting >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [LOWI-SERVER] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] >D/QSEECOMAPI: ( 9108): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9108): App is not loaded in QSEE >E/QSEECOMAPI: ( 9108): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt >E/QSEECOMAPI: ( 9108): Error::Loading image failed with ret = -1 >D/QSEECOMAPI: ( 9108): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9108): App is not loaded in QSEE >E/QSEECOMAPI: ( 9108): Error::Cannot open the file /firmware/image/keymaste.mdt >E/QSEECOMAPI: ( 9108): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245475.485245] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5500 >I/cat ( 270): <4>[245475.492643] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5500 >E/QCOMKeyMaster( 9108): Loading keymaster app failied >E/keystore( 9108): could not open keymaster device in keystore (Operation not permitted) >E/keystore( 9108): keystore keymaster could not be initialized; exiting >E/Diag_Lib( 293): Thread state: conn_id=0, state=RX_THREAD_WAIT_READ >E/Diag_Lib( 293): Thread state: conn_id=0, state=RX_THREAD_CLIENT_TX >E/Diag_Lib( 293): qmi_qmux: TX/RX - RX 17 bytes on conn_id=0 >E/Diag_Lib( 293): 01 10 00 80 03 02 04 DC 1C 51 00 04 00 12 01 00 >E/Diag_Lib( 293): B4 >E/Diag_Lib( 293): qmuxd: TX message on fd=30, to qmux_client_id=0x1, len=51 >E/Diag_Lib( 293): Thread state: conn_id=0, state=RX_THREAD_WAIT_POLL >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] >I/cat ( 270): <6>[245480.516493] mmc0: Starting deferred resume >I/cat ( 270): <6>[245480.570212] mmc0: Deferred resume completed >D/QSEECOMAPI: ( 9109): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9109): App is not loaded in QSEE >E/QSEECOMAPI: ( 9109): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt >E/QSEECOMAPI: ( 9109): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245480.588481] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xc192ff80 >D/QSEECOMAPI: ( 9109): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9109): App is not loaded in QSEE >E/QSEECOMAPI: ( 9109): Error::Cannot open the file /firmware/image/keymaste.mdt >E/QSEECOMAPI: ( 9109): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245480.596787] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xc192ff80 >E/QCOMKeyMaster( 9109): Loading keymaster app failied >E/keystore( 9109): could not open keymaster device in keystore (Operation not permitted) >E/keystore( 9109): keystore keymaster could not be initialized; exiting >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] >D/QSEECOMAPI: ( 9112): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9112): App is not loaded in QSEE >E/QSEECOMAPI: ( 9112): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt >E/QSEECOMAPI: ( 9112): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245485.632271] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xc192ff80 >D/QSEECOMAPI: ( 9112): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9112): App is not loaded in QSEE >E/QSEECOMAPI: ( 9112): Error::Cannot open the file /firmware/image/keymaste.mdt >E/QSEECOMAPI: ( 9112): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245485.639874] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xc192ff80 >E/QCOMKeyMaster( 9112): Loading keymaster app failied >E/keystore( 9112): could not open keymaster device in keystore (Operation not permitted) >E/keystore( 9112): keystore keymaster could not be initialized; exiting >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] >D/QSEECOMAPI: ( 9113): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9113): App is not loaded in QSEE >E/QSEECOMAPI: ( 9113): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt >E/QSEECOMAPI: ( 9113): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245490.687860] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xcf4f8d80 >D/QSEECOMAPI: ( 9113): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9113): App is not loaded in QSEE >E/QSEECOMAPI: ( 9113): Error::Cannot open the file /firmware/image/keymaste.mdt >E/QSEECOMAPI: ( 9113): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245490.695964] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xcf4f8d80 >E/QCOMKeyMaster( 9113): Loading keymaster app failied >E/keystore( 9113): could not open keymaster device in keystore (Operation not permitted) >E/keystore( 9113): keystore keymaster could not be initialized; exiting >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] >E/Diag_Lib( 293): Thread state: conn_id=0, state=RX_THREAD_WAIT_READ >E/Diag_Lib( 293): Thread state: conn_id=0, state=RX_THREAD_CLIENT_TX >E/Diag_Lib( 293): qmi_qmux: TX/RX - RX 17 bytes on conn_id=0 >E/Diag_Lib( 293): 01 10 00 80 03 02 04 DD 1C 51 00 04 00 12 01 00 >E/Diag_Lib( 293): B6 >E/Diag_Lib( 293): qmuxd: TX message on fd=30, to qmux_client_id=0x1, len=51 >E/Diag_Lib( 293): Thread state: conn_id=0, state=RX_THREAD_WAIT_POLL >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] >D/QSEECOMAPI: ( 9115): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9115): App is not loaded in QSEE >E/QSEECOMAPI: ( 9115): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt >E/QSEECOMAPI: ( 9115): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245495.724501] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5580 >D/QSEECOMAPI: ( 9115): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9115): App is not loaded in QSEE >E/QSEECOMAPI: ( 9115): Error::Cannot open the file /firmware/image/keymaste.mdt >E/QSEECOMAPI: ( 9115): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245495.733622] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5580 >E/QCOMKeyMaster( 9115): Loading keymaster app failied >E/keystore( 9115): could not open keymaster device in keystore (Operation not permitted) >E/keystore( 9115): keystore keymaster could not be initialized; exiting >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] >I/cat ( 270): <6>[245500.761109] mmc0: Starting deferred resume >I/cat ( 270): <6>[245500.815504] mmc0: Deferred resume completed >D/QSEECOMAPI: ( 9116): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9116): App is not loaded in QSEE >E/QSEECOMAPI: ( 9116): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt >E/QSEECOMAPI: ( 9116): Error::Loading image failed with ret = -1 >D/QSEECOMAPI: ( 9116): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9116): App is not loaded in QSEE >I/cat ( 270): <4>[245500.828121] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xcf4f8f80 >E/QSEECOMAPI: ( 9116): Error::Cannot open the file /firmware/image/keymaste.mdt >E/QSEECOMAPI: ( 9116): Error::Loading image failed with ret = -1 >E/QCOMKeyMaster( 9116): Loading keymaster app failied >E/keystore( 9116): could not open keymaster device in keystore (Operation not permitted) >E/keystore( 9116): keystore keymaster could not be initialized; exiting >I/cat ( 270): <4>[245500.836018] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xcf4f8f80 >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] >D/QSEECOMAPI: ( 9117): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9117): App is not loaded in QSEE >E/QSEECOMAPI: ( 9117): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt >E/QSEECOMAPI: ( 9117): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245505.875710] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5580 >D/QSEECOMAPI: ( 9117): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9117): App is not loaded in QSEE >E/QSEECOMAPI: ( 9117): Error::Cannot open the file /firmware/image/keymaste.mdt >E/QSEECOMAPI: ( 9117): Error::Loading image failed with ret = -1 >E/QCOMKeyMaster( 9117): Loading keymaster app failied >I/cat ( 270): <4>[245505.884121] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5580 >E/keystore( 9117): could not open keymaster device in keystore (Operation not permitted) >E/keystore( 9117): keystore keymaster could not be initialized; exiting >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] >D/QSEECOMAPI: ( 9118): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9118): App is not loaded in QSEE >E/QSEECOMAPI: ( 9118): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt >E/QSEECOMAPI: ( 9118): Error::Loading image failed with ret = -1 >D/QSEECOMAPI: ( 9118): QSEECom_get_handle sb_length = 0x2000 >D/QSEECOMAPI: ( 9118): App is not loaded in QSEE >E/QSEECOMAPI: ( 9118): Error::Cannot open the file /firmware/image/keymaste.mdt >E/QSEECOMAPI: ( 9118): Error::Loading image failed with ret = -1 >I/cat ( 270): <4>[245510.914596] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5300 >I/cat ( 270): <4>[245510.921990] QSEECOM: qseecom_release: data: released = false, type = 1, data = 0xceea5300 >E/QCOMKeyMaster( 9118): Loading keymaster app failied >E/keystore( 9118): could not open keymaster device in keystore (Operation not permitted) >E/keystore( 9118): keystore keymaster could not be initialized; exiting >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent] >E/QCALOG ( 309): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent]
Attachment #8496692 - Attachment description: logcat201409291336-e47cd8c0-mtbf6 → logcat201409291336-e472d80e-mtbf5
pvt v2.1(aurora) BuildID:20140912000203
[Blocking Requested - why for this release]:
blocking-b2g: --- → 2.1?
Component: MTBF → Stability
Hi Walter, Could you comment more in this bug? We will need more help from other teams.
Flags: needinfo?(wachen)
I can reproduce this easily by not using MTBF: 1. Launch Settings app 2. Select Wi-Fi right after Settings shows up 3. See white screen except status bar
Hi Arthur, Can you please check this bug? Thanks.
Flags: needinfo?(arthur.chen)
The bug should have been fixed in bug 1052256. Ting, are you using the latest master or v2.1?
Flags: needinfo?(arthur.chen) → needinfo?(tchou)
Just talked to Arthur, the STR in comment 9 have been fixed in v2.1 already (I tested with 0904 codebase), so this should be a different issue.
Flags: needinfo?(tchou)
Correction: BuildID should be 20140923160203
Flags: needinfo?(wachen)
Arthur, can you help investigate this then, given ting's comment? Please reachout to ting/walter directly, if you want the affected device as they are able to reproduce this,
blocking-b2g: 2.1? → 2.1+
Flags: needinfo?(arthur.chen)
Since the issue does not happen on Settings app only, it may relate to bug 1066480. Paul & Walter will setup some devices with the patch of bug 1066480 for another run during the weekend, we will check on Monday whether the issue goes away.
Flags: needinfo?(arthur.chen)
It's still pretty weird. Some of the devices reproduced the issue alrdy. Ting-Yu alrdy took one device. The gaia test can still keep running test even if white/black screen happens. It is not a good sign.
I passed the device to Arthur (it was Settings app shows white screen), he pressed home key to bring up the cards view, and tap on Settings app, then the content showed up. He thinks this tends to a rednering issue as the test can still interact with the elements and pass.
(In reply to Ting-Yu Chou [:ting] from comment #17) > I passed the device to Arthur (it was Settings app shows white screen), he > pressed home key to bring up the cards view, and tap on Settings app, then > the content showed up. > > He thinks this tends to a rednering issue as the test can still interact > with the elements and pass. Milan, does this bug sounds like any other in-progress rendering bugs?
Flags: needinfo?(milan)
According to QA, we don't see this bug during this weekend. But we still need to run a longer MTBF round to get more information.
Ken, Unfortunately, it reproduced again in the run started yesterday. Milan, I looked through those bugs. First of all, it is not black striped. Second, it didn't happen immediately after flashed the phone. I think it is unrelated with those bugs.
Flags: needinfo?(kchang)
Peter, can you please have someone to check this problem as well? Thanks.
Flags: needinfo?(kchang) → needinfo?(pchang)
chiajung, please help to check the device.
Flags: needinfo?(pchang) → needinfo?(chung)
I use get_about_memory to get the memory usage. In "white screen" case, we can see that the radio app doesn't alloc any gralloc buffer. After we press home key to switch between homescreen app and radio app for several time, the screen for radio app go back. And we can see some gralloc buffer usage for radio app. Maybe we should add some log to check the gralloc memory allocation failed case. ------- wihte screen: 9.09 MB (100.0%) -- gralloc ├──5.63 MB (61.87%) ── Homescreen (pid=1033)/buffer(width=256, height=256, bpp=4, stride=288) [20] └──3.47 MB (38.13%) -- b2g (pid=235) ├──3.13 MB (34.40%) ── buffer(width=480, height=854, bpp=4, stride=480) [2] ├──0.34 MB (03.71%) ── buffer(width=480, height=46, bpp=4, stride=480) [4] └──0.00 MB (00.03%) ── buffer(width=24, height=24, bpp=4, stride=32) 22.03 MB (100.0%) -- kgsl-memory ├──18.42 MB (83.62%) -- b2g (pid=235) │ ├───4.63 MB (21.03%) ── egl_image [14] │ ├───4.04 MB (18.33%) ── gl [22] │ ├───3.18 MB (14.43%) ── texture [12] │ ├───3.16 MB (14.36%) ── egl_surface [2] │ ├───1.44 MB (06.52%) ── command [23] │ ├───1.36 MB (06.17%) ── any(0) [39] │ ├───0.40 MB (01.81%) ── renderbuffer │ └───0.21 MB (00.96%) ++ (3 tiny) └───3.61 MB (16.38%) -- Homescreen (pid=1033) ├──2.02 MB (09.17%) ── gl [11] ├──0.68 MB (03.09%) ── texture [6] ├──0.60 MB (02.71%) ++ (5 tiny) └──0.31 MB (01.42%) ── command [5] ----------- The radio screen is back. 10.49 MB (100.0%) -- gralloc ├───5.63 MB (53.63%) ── Homescreen (pid=1033)/buffer(width=256, height=256, bpp=4, stride=288) [20] ├───3.38 MB (32.25%) -- b2g (pid=235) │ ├──3.13 MB (29.82%) ── buffer(width=480, height=854, bpp=4, stride=480) [2] │ ├──0.25 MB (02.41%) ── buffer(width=480, height=46, bpp=4, stride=480) [3] │ └──0.00 MB (00.03%) ── buffer(width=24, height=24, bpp=4, stride=32) └───1.48 MB (14.12%) ── FM Radio (pid=19370)/buffer(width=480, height=809, bpp=4, stride=480) 23.05 MB (100.0%) -- kgsl-memory ├──19.45 MB (84.34%) -- b2g (pid=235) │ ├───6.16 MB (26.70%) ── egl_image [15] │ ├───4.04 MB (17.52%) ── gl [22] │ ├───3.18 MB (13.79%) ── texture [12] │ ├───3.16 MB (13.72%) ── egl_surface [2] │ ├───1.44 MB (06.24%) ── command [23] │ ├───0.86 MB (03.73%) ── any(0) [35] │ ├───0.40 MB (01.73%) ── renderbuffer │ └───0.21 MB (00.91%) ++ (3 tiny) └───3.61 MB (15.66%) -- Homescreen (pid=1033) ├──2.02 MB (08.76%) ── gl [11] ├──0.68 MB (02.95%) ── texture [6] ├──0.60 MB (02.59%) ++ (5 tiny) └──0.31 MB (01.36%) ── command [5]
ni Alive since some bugs related happening in gaia before.
Flags: needinfo?(alive)
Walter, gaia needs enabling devtool by default to trace, can you help to add this?
Flags: needinfo?(wachen)
After check the device and discuss witwh :cerv and :kanru, we feel we need Qualcomm's help on it: The problem here is Gralloc allocation fail but low-mem-killer does not kill any other process. We think the ion kernel driver should kick low-mem-killer and make kernel release some memory and return the memory rather than fail silently. While it fails silently, all we can do is: (1) fallback to Shmem and if Shmem allocation fails, it would kick low-mem-killer and allocate memory successfully, however, it may later fail while it tries to upload texture in b2g process, and black/white screen again. (2) exit(0) on allocation fail. From user's view point, this may cause some app never launch but don't know why. (3) fallback to Shmem and while it success, release the Shmem and try gralloc again. This is too hacky to do and should be a bad workaround for this symptom, since the EGLImage creation may still fail while upload. As a result, we think ion kernel driver should try to kick low-mem-killer and allocate memory successfully with some background apps killed.
Flags: needinfo?(chung)
Flags: needinfo?(alive)
(In reply to Chiajung Hung [:chiajung] from comment #27) > After check the device and discuss witwh :cerv and :kanru, we feel we need > Qualcomm's help on it: > > The problem here is Gralloc allocation fail but low-mem-killer does not kill > any other process. We think the ion kernel driver should kick low-mem-killer > and make kernel release some memory and return the memory rather than fail > silently. While it fails silently, all we can do is: > (1) fallback to Shmem and if Shmem allocation fails, it would kick > low-mem-killer and allocate memory successfully, however, it may later fail > while it tries to upload texture in b2g process, and black/white screen > again. > > (2) exit(0) on allocation fail. From user's view point, this may cause some > app never launch but don't know why. > > (3) fallback to Shmem and while it success, release the Shmem and try > gralloc again. This is too hacky to do and should be a bad workaround for > this symptom, since the EGLImage creation may still fail while upload. > > As a result, we think ion kernel driver should try to kick low-mem-killer > and allocate memory successfully with some background apps killed. I wonder if this is a vendor's bug. And we need partner's help.
Flags: needinfo?(frlee)
Hi, Ken, Per comment 27, we do need QC's help. Hi, Paul, I believe we always have it on now.
Flags: needinfo?(wachen) → needinfo?(kchang)
(In reply to Chiajung Hung [:chiajung] from comment #27) > After check the device and discuss witwh :cerv and :kanru, we feel we need > Qualcomm's help on it: > > The problem here is Gralloc allocation fail but low-mem-killer does not kill > any other process. We think the ion kernel driver should kick low-mem-killer > and make kernel release some memory and return the memory rather than fail > silently. While it fails silently, all we can do is: > (1) fallback to Shmem and if Shmem allocation fails, it would kick > low-mem-killer and allocate memory successfully, however, it may later fail > while it tries to upload texture in b2g process, and black/white screen > again. > > (2) exit(0) on allocation fail. From user's view point, this may cause some > app never launch but don't know why. > > (3) fallback to Shmem and while it success, release the Shmem and try > gralloc again. This is too hacky to do and should be a bad workaround for > this symptom, since the EGLImage creation may still fail while upload. > > As a result, we think ion kernel driver should try to kick low-mem-killer > and allocate memory successfully with some background apps killed. Ni :tkundu, here to get input given the feedback of this being a CAF issue.
Flags: needinfo?(tkundu)
per comment27, remove my ni. wait for QC's feedback
Flags: needinfo?(frlee)
Flags: needinfo?(pchang)
Based on comment 24 and comment 27, I think this issue is related to low-mem-killer trigger timing. And you could there are not too much graphic buffer allocation from comment 24. After checking with QA, this is flame with 319Mb configuration but we didn't have this issue with JB version. Walter, please correct me if I'm wrong. Therefore, we need QC's comment on this issue.
Flags: needinfo?(pchang) → needinfo?(wachen)
(In reply to bhavana bajaj [:bajaj] from comment #30) > (In reply to Chiajung Hung [:chiajung] from comment #27) > > After check the device and discuss witwh :cerv and :kanru, we feel we need > > Qualcomm's help on it: > > > > The problem here is Gralloc allocation fail but low-mem-killer does not kill > > any other process. We think the ion kernel driver should kick low-mem-killer > > and make kernel release some memory and return the memory rather than fail > > silently. While it fails silently, all we can do is: > > (1) fallback to Shmem and if Shmem allocation fails, it would kick > > low-mem-killer and allocate memory successfully, however, it may later fail > > while it tries to upload texture in b2g process, and black/white screen > > again. > > > > (2) exit(0) on allocation fail. From user's view point, this may cause some > > app never launch but don't know why. > > > > (3) fallback to Shmem and while it success, release the Shmem and try > > gralloc again. This is too hacky to do and should be a bad workaround for > > this symptom, since the EGLImage creation may still fail while upload. > > > > As a result, we think ion kernel driver should try to kick low-mem-killer > > and allocate memory successfully with some background apps killed. > > Ni :tkundu, here to get input given the feedback of this being a CAF issue. Could you please give us dmesg, logcat logs, output of |adb shell cat /d/ion/heaps/system|, |adb shell /sys/class/kgsl/kgsl/page_alloc|, |adb shell b2g-info| , |adb shell procrank| log when this happens ? It would be great if you also point us to your gaia/gecok SHA1's , branch, device , available memory on your device (look into |adb shell cat /proc/meminfo| . If you can provide a me good STR then I can reproduce this issue on my device and conclude faster. Otherwise I need your help for logs :)
Flags: needinfo?(tkundu) → needinfo?(bbajaj)
Walter, can you please provide the log requested on comment 33?
Flags: needinfo?(kchang)
I can try to run this today. I need some time to set the log up.
Flags: needinfo?(wachen)
Flags: needinfo?(wachen)
I figured that: 1. I can't give the exact dmesg, logcat, or other logs when it just happens. I might be able to get info after MTBF shut down itself (maybe 1~2 minutes after crashed). It's just hard to get it precisely on the time when it crashes. 2. There won't be a good STR, but I can provide you with more information on the test sequence we ran.
Attached file 20141013.zip —
I can give you the phone reproduced the bug 2 days ago. However, I am not able to get b2g-info wachen@WalterDesktop:~/FirefoxOS/tmp/20141013$ adb shell b2g-info Fatal error: Two B2G main processes found (pids 208 and 453) wachen@WalterDesktop:~/FirefoxOS/tmp/20141013$ adb shell b2g-ps APPLICATION SEC USER PID PPID VSIZE RSS WCHAN PC NAME b2g 0 root 208 1 255136 47048 ffffffff b6e918ac S /system/b2g/b2g (Nuwa) 0 root 453 208 54968 384 ffffffff b6e918ac S /system/b2g/b2g (Preallocated a 2 u0_a8975 8975 453 60908 1516 ffffffff b6e918ac S /system/b2g/b2g Homescreen 2 u0_a14091 14091 453 93480 4496 ffffffff b6e918ac S /system/b2g/b2g Messages 2 u0_a15827 15827 453 91708 6344 ffffffff b6e918ac S /system/b2g/b2g Communications 2 u0_a15979 15979 453 69008 4068 ffffffff b6e918ac S /system/b2g/b2g FM Radio 2 u0_a25969 25969 453 65468 2240 ffffffff b6e918ac S /system/b2g/b2g
Gaia 7f738edf66b9298bceef8a4981d05d04fd04e540 Gecko BuildID 20141009141424 Version 34.0a2 ro.build.version.incremental=27 ro.build.date=Thu Sep 4 14:59:02 CST 2014
Flags: needinfo?(wachen)
Flags: needinfo?(wachen)
Depends on: 1069691
(In reply to Walter Chen[:ypwalter][:wachen] from comment #36) > I figured that: > > 1. I can't give the exact dmesg, logcat, or other logs when it just happens. > I might be able to get info after MTBF shut down itself (maybe 1~2 minutes > after crashed). It's just hard to get it precisely on the time when it > crashes. Is it possible to run a bash logging script (as background process) which will be collecting all logs periodically (may be every 30seconds ?) mentioned in Comment 33 on /storage/sdcard1 ?
<7>[347434.303725] DOM Worker: unhandled page fault (11) at 0xb1cc468c, code 0x00f <1>[347434.303740] pgd = d0e5c000 <1>[347434.305490] [b1cc468c] *pgd=05348831, *pte=134826df, *ppte=13482e5f <6>[347434.311826] <6>[347434.311834] Pid: 752, comm: DOM Worker <6>[347434.311844] CPU: 1 Tainted: G W O (3.4.0-g0502ed9-00027-g3c37175 #1) <6>[347434.311857] PC is at 0xb5e00e2e <6>[347434.311864] LR is at 0xb5d8bae3 <6>[347434.311873] pc : [<b5e00e2e>] lr : [<b5d8bae3>] psr: 400e0030 <6>[347434.311878] sp : af0ff890 ip : 00000001 fp : b0c7d100 <6>[347434.311886] r10: b64be244 r9 : b1334938 r8 : b1cc469c <6>[347434.311895] r7 : 00000010 r6 : b1cc468c r5 : 00000000 r4 : b0c7d100 <6>[347434.311905] r3 : 00000000 r2 : af0ff8c0 r1 : b0c7d100 r0 : b1334938 <6>[347434.311915] Flags: nZcv IRQs on FIQs on Mode USER_32 ISA Thumb Segment user <6>[347434.311926] Control: 10c5387d Table: 10e5c06a DAC: 00000015 <6>[347434.311954] [<c010bd74>] (unwind_backtrace+0x0/0xf8) from [<c01118b8>] (__do_user_fault+0xbc/0x134) <6>[347434.311973] [<c01118b8>] (__do_user_fault+0xbc/0x134) from [<c088ae88>] (do_page_fault+0x290/0x400) <6>[347434.311991] [<c088ae88>] (do_page_fault+0x290/0x400) from [<c010029c>] (do_DataAbort+0x34/0x98) <6>[347434.312009] [<c010029c>] (do_DataAbort+0x34/0x98) from [<c08896f4>] (__dabt_usr+0x34/0x40) <6>[347434.312019] Exception stack(0xc3ff5fb0 to 0xc3ff5ff8) <6>[347434.312030] 5fa0: b1334938 b0c7d100 af0ff8c0 00000000 <6>[347434.312044] 5fc0: b0c7d100 00000000 b1cc468c 00000010 b1cc469c b1334938 b64be244 b0c7d100 <6>[347434.312057] 5fe0: 00000001 af0ff890 b5d8bae3 b5e00e2e 400e0030 ffffffff I can see above stack trace in dmesg log. Could you please confirm me whether this stack trace is collected exactly when this issue happens or not ? Please note that I still need more logs which I mentioned in comment 39 and comment 33 . (In reply to Chiajung Hung [:chiajung] from comment #27) > After check the device and discuss witwh :cerv and :kanru, we feel we need > Qualcomm's help on it: > > The problem here is Gralloc allocation fail but low-mem-killer does not kill > any other process. We think the ion kernel driver should kick low-mem-killer > and make kernel release some memory and return the memory rather than fail > silently. While it fails silently, all we can do is: > (1) fallback to Shmem and if Shmem allocation fails, it would kick > low-mem-killer and allocate memory successfully, however, it may later fail > while it tries to upload texture in b2g process, and black/white screen > again. > Do you have any evidence that this issue happens only when device is running very low memory ? I am still waiting for logs to confirm. BTW, it is very unlikely that low memory killer won't be kicked in low memory situation. I guess that there is some other issue which might be causing this.
Unfortunately, our b2g-info patch for a certain bug is not yet applied. I think we might be blocked by it for b2g-info. Also, the zip file of 20131013.zip is after I came to the company and I collect it. I am actually not sure about when it happens as I ran it overnight. I encounter another bug yesterday night. I will try to solve it today and get the result asap.
Flags: needinfo?(wachen)
Tapas, I can't do pulling of information per 30 seconds. We can think from 2 aspects. 1. Even if you pull it every second, we won't know when exactly it has black and white screen. The test will continue anyway when it meet this kind of issue. The reason is that the test frameworkd actually can still control it (HTML dom is complete. It's just that nothing shown on the screen) 2. If I pull it out every 30 seconds, it would greatly affect current way of testing. That is to say, out test timing, memory usage, space usage, and all other aspects are affected. I can try to add it in between a set of tests (like after 5 test cases or so)
Flags: needinfo?(tkundu)
(In reply to Walter Chen[:ypwalter][:wachen] from comment #42) > Tapas, I can't do pulling of information per 30 seconds. > > We can think from 2 aspects. > 1. Even if you pull it every second, we won't know when exactly it has black > and white screen. Sorry, I am not asking you to pull any data over adb connection. I asked you to log all details (See comment 33) on sdcard (>=8GB . Make sure that your sdcard has at least 8GB free space or use a high capacity sdcard) every 10 seconds. I don't think that 8Gb sdcard will fillup in 24-48 hours even if you log all these data (See comment 33) on sdcard for every 10 seconds. You just need to write some logging bash script which will do this in background and restart your test. Without these data , I cannot say that device is running really low in memory when crash has happened. I don't see any other ways to debug it further.
Flags: needinfo?(tkundu) → needinfo?(wachen)
(In reply to Tapas[:tkundu on #b2g/gaia/memshrink/gfx] (always NI me) from comment #40) > <7>[347434.303725] DOM Worker: unhandled page fault (11) at 0xb1cc468c, code > 0x00f > <1>[347434.303740] pgd = d0e5c000 > <1>[347434.305490] [b1cc468c] *pgd=05348831, *pte=134826df, *ppte=13482e5f > <6>[347434.311826] > <6>[347434.311834] Pid: 752, comm: DOM Worker > <6>[347434.311844] CPU: 1 Tainted: G W O > (3.4.0-g0502ed9-00027-g3c37175 #1) > <6>[347434.311857] PC is at 0xb5e00e2e > <6>[347434.311864] LR is at 0xb5d8bae3 > <6>[347434.311873] pc : [<b5e00e2e>] lr : [<b5d8bae3>] psr: 400e0030 > <6>[347434.311878] sp : af0ff890 ip : 00000001 fp : b0c7d100 > <6>[347434.311886] r10: b64be244 r9 : b1334938 r8 : b1cc469c > <6>[347434.311895] r7 : 00000010 r6 : b1cc468c r5 : 00000000 r4 : b0c7d100 > <6>[347434.311905] r3 : 00000000 r2 : af0ff8c0 r1 : b0c7d100 r0 : b1334938 > <6>[347434.311915] Flags: nZcv IRQs on FIQs on Mode USER_32 ISA Thumb > Segment user > <6>[347434.311926] Control: 10c5387d Table: 10e5c06a DAC: 00000015 > <6>[347434.311954] [<c010bd74>] (unwind_backtrace+0x0/0xf8) from > [<c01118b8>] (__do_user_fault+0xbc/0x134) > <6>[347434.311973] [<c01118b8>] (__do_user_fault+0xbc/0x134) from > [<c088ae88>] (do_page_fault+0x290/0x400) > <6>[347434.311991] [<c088ae88>] (do_page_fault+0x290/0x400) from > [<c010029c>] (do_DataAbort+0x34/0x98) > <6>[347434.312009] [<c010029c>] (do_DataAbort+0x34/0x98) from [<c08896f4>] > (__dabt_usr+0x34/0x40) > <6>[347434.312019] Exception stack(0xc3ff5fb0 to 0xc3ff5ff8) > <6>[347434.312030] 5fa0: b1334938 > b0c7d100 af0ff8c0 00000000 > <6>[347434.312044] 5fc0: b0c7d100 00000000 b1cc468c 00000010 b1cc469c > b1334938 b64be244 b0c7d100 > <6>[347434.312057] 5fe0: 00000001 af0ff890 b5d8bae3 b5e00e2e 400e0030 > ffffffff > > > I can see above stack trace in dmesg log. Could you please confirm me > whether this stack trace is collected exactly when this issue happens or not > ? Please note that I still need more logs which I mentioned in comment 39 > and comment 33 . > I always see the log on v2.1 flame-kk during booting. I filed as Bug 1081569.
If this problem is caused by out of gralloc memory, the following log should be in logcat. > SharedBufferManagerParent::RecvAllocateGrallocBuffer -- gralloc buffer allocation failed https://hg.mozilla.org/releases/mozilla-b2g32_v2_0/file/99387ed59305/gfx/layers/ipc/SharedBufferManagerParent.cpp#l189
(In reply to Ting-Yu Chou [:ting] from comment #9) > I can reproduce this easily by not using MTBF: > > 1. Launch Settings app > 2. Select Wi-Fi right after Settings shows up > 3. See white screen except status bar It could be caused by different problem. It seems better as different problem until we know how the problems happen.
It might be better to check if application is set to "active" by gaia side when the problem happened. It triggers to call PresShell::SetIsActive(bool aIsActive). It controls layer buffer free on hide and re-paint.
active is set to application's PresShell::SetIsActive() via BrowserElementParent.
Flags: needinfo?(bbajaj)
Whiteboard: [mtbf]
Bug 1081528 seems a bit similar bug. In the bug's case, system app caused the problem.
Sotaro, Thanks for helping here. Comment 49: For Bug 1081528, I never see blue screen in my cases. I always see either black or white. Comment 46: That bug was fixed in another bug Tapas, It will be even tougher then. First of all, the reason I don't use sd card to do so is sd card fails sometimes during MTBF testing. Secondly, no matter you do the log inside or outside, it will put a heavy loading on phone CPU/memory usage. Thus, we can fail faster and get time difference issue. I did a test run yesterday, and I actually see the bug reproduced after around 5~10 minutes. However, currently, 184 image comes with a bad b2g-info and procrank. I will restart it today and hopefully get you some result today.
Flags: needinfo?(wachen) → needinfo?(tkundu)
(In reply to Walter Chen[:ypwalter][:wachen] from comment #50) > Sotaro, > Thanks for helping here. > > Comment 49: > For Bug 1081528, I never see blue screen in my cases. I always see either > black or white. I did not say Bug 1081528 is related to bug. I just say, the problem symptom could happen because of system app. If we want to fix the bug, we have to make clear which component causes the problem. Before my comment almost comment seems to focused to gralloc buffer allocation. But we seems not have clear evidence to show that.
(In reply to Walter Chen[:ypwalter][:wachen] from comment #50) > I will restart it today and hopefully get you some result > today. I will wait for logs :) . Thanks a lot for your efforts.
Flags: needinfo?(tkundu)
Sotaro, Thanks again for prompt response and clarification. Roger that, and please let me know if there is any other thoughts. Tapas, I will be sending you huge set of data next Monday since I got bug 1077292 relieved a little bit now.
Flags: needinfo?(wachen)
Attached file output_debug_183.zip —
Tapas, let me know if this helps?
Flags: needinfo?(wachen) → needinfo?(tkundu)
Flags: needinfo?(tkundu)
Flags: needinfo?(tkundu)
Whiteboard: [mtbf] → [mtbf][systemsfe]
Gregor/Tim, This needs confirmation on team ownership between sysfe and sysplatform
Flags: needinfo?(timdream)
Flags: needinfo?(anygregor)
(In reply to Candice Serran (:cserran) from comment #55) > Gregor/Tim, > > This needs confirmation on team ownership between sysfe and sysplatform This is not likely to own by neither teams -- all comments points to possible memory allocation issue in the platform.
Flags: needinfo?(timdream)
Flags: needinfo?(anygregor)
Whiteboard: [mtbf][systemsfe] → [mtbf]
(In reply to Tim Guan-tin Chien [:timdream] (MoCo-TPE) (please ni?) from comment #56) > (In reply to Candice Serran (:cserran) from comment #55) > > Gregor/Tim, > > > > This needs confirmation on team ownership between sysfe and sysplatform > > This is not likely to own by neither teams -- all comments points to > possible memory allocation issue in the platform. Can we enable some logging here to make sure its not on us? I guess Alive can flip the right debugging flags in order to get more info here?
Flags: needinfo?(alive)
(In reply to Walter Chen[:ypwalter][:wachen] from comment #54) > Created attachment 8507630 [details] > output_debug_183.zip > > Tapas, let me know if this helps? Could you please tell me device timestamp when you see white/black screen on device . Then I will look for logs near that timestamp in your logs. I am seeing some "unhandled page fault stacktraces" in kernel and I want to confirm whether you are seeing black screen/white screen when these page fault error happens or not.
Flags: needinfo?(wachen)
(In reply to Gregor Wagner [:gwagner] from comment #57) > > Can we enable some logging here to make sure its not on us? I guess Alive > can flip the right debugging flags in order to get more info here? Should be https://bugzilla.mozilla.org/show_bug.cgi?id=1076605#c17
Flags: needinfo?(alive)
Summary: [MTBF][B2G] white & black screen → [MTBF][B2G] Missing rendering for launched apps
Attached file logcat.e444da63.zip —
Tapas, we will give you a video clip for you to see. We have no way to detect the exact timing now. Ting, mtbf-5 / e444da63. white screen: messages, settings, contacts black screen: music http://mtbf-1:8080/job/flame.v2.1.mtbf5.319/label=mtbf-5/200/artifact/mtbf_driver/output_debug_200.zip
Flags: needinfo?(wachen)
Attached file output_debug_200.zip —
Tapas, it actually quite reproducible in this short run. Please see the attached file. We are running another run for you again with video now.
From attachment 8509372 [details], I see mozbrowserloadstart from the app which is opening from cardview, but I don't see it on my Flame when I switch app from cardview: E/GeckoConsole( 206): Content JS LOG at app://system.gaiamobile.org/js/app_window.js:1035 in aw_debug: [AppWindow][Settings][AppWindow_8][2744.345] open with from-cardview E/GeckoConsole( 206): Content JS LOG at app://system.gaiamobile.org/js/app_window.js:1035 in aw_debug: [AppWindow][Settings][AppWindow_8][2744.346] closed,opening,::,open E/GeckoConsole( 206): Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:694 in awm_debug: [AppWindowManager][2744.419]=== Active app now is: ,Settings,=== E/GeckoConsole( 206): Content JS LOG at app://system.gaiamobile.org/js/app_window.js:1035 in aw_debug: [AppWindow][Settings][AppWindow_8][2746.810] Handling mozbrowserloadstart event... Also I see a lot of IPC error messages, not sure if they're related: I/Gecko ( 206): ###!!! [Parent][MessageChannel] Error: Channel error: cannot send/recv
Tapas, It can be reproduced just within a minutes... https://vreplay.mozilla.com/replay/showRecordingExternal.html?key=s6GUAVpp3v4Foax It should be the same for all the devices. I guess you can take a look at this file. output_debug_200.zip
I find out missing rendering issue after bug 1084495 is reproduced. (https://bugzilla.mozilla.org/show_bug.cgi?id=1084495#c6) There is a warning log while I go back to settings app from card view. Then, settings app is rendered normally. W/GeckoConsole( 8599): [JavaScript Warning: "Error in parsing value for 'visibility'. Declaration dropped." {file: "app://system.gaiamobile.org/index.html" line: 0 column: 12 source: "visibility: undefined"}]
Hi Alive, Is it a GAIA issue that you can find someone to take care?
Flags: needinfo?(alive)
I tried to repro locally on my Flame, I see something strange, not sure is this expected: E/GeckoConsole( 1427): Content JS LOG at app://system.gaiamobile.org/js/app_window.js:1035 in aw_debug: [AppWindow][FM Radio][AppWindow_4][657.676] Handling mozbrowsererror event... E/GeckoConsole( 1427): Content JS LOG at app://system.gaiamobile.org/js/app_window.js:1035 in aw_debug: [AppWindow][FM Radio][AppWindow_4][657.683] publishing internal event: crashed E/GeckoConsole( 1427): Content JS LOG at app://system.gaiamobile.org/js/app_window.js:1035 in aw_debug: [AppWindow][FM Radio][AppWindow_4][657.687] publishing external event: crashed E/GeckoConsole( 1427): Content JS LOG at app://system.gaiamobile.org/js/app_window.js:1035 in aw_debug: [AppWindow][FM Radio][AppWindow_4][657.688] ..sleep! I will come back. E/GeckoConsole( 1427): Content JS LOG at app://system.gaiamobile.org/js/app_window.js:1035 in aw_debug: [AppWindow][FM Radio][AppWindow_4][657.820] publishing internal event: suspended E/GeckoConsole( 1427): Content JS LOG at app://system.gaiamobile.org/js/app_window.js:1035 in aw_debug: [AppWindow][FM Radio][AppWindow_4][657.820] publishing external event: suspended ... E/GeckoConsole( 1427): Content JS LOG at app://system.gaiamobile.org/js/app_window.js:1035 in aw_debug: [AppWindow][FM Radio][AppWindow_4][889.372] ...revived! E/GeckoConsole( 1427): Content JS LOG at app://system.gaiamobile.org/js/app_window.js:1035 in aw_debug: [AppWindow][FM Radio][AppWindow_4][889.399] setVisible on browser element:false E/GeckoConsole( 1427): Content JS LOG at app://system.gaiamobile.org/js/app_window.js:1035 in aw_debug: [AppWindow][FM Radio][AppWindow_4][889.399] publishing internal event: resumed E/GeckoConsole( 1427): Content JS LOG at app://system.gaiamobile.org/js/app_window.js:1035 in aw_debug: [AppWindow][FM Radio][AppWindow_4][889.400] publishing external event: resumed E/GeckoConsole( 1427): Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:694 in awm_debug: [AppWindowManager][889.401]handling launchapp E/GeckoConsole( 1427): Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:694 in awm_debug: [AppWindowManager][889.401]launchingapp://fm.gaiamobile.org
(In reply to Ting-Yu Chou [:ting] from comment #62) > From attachment 8509372 [details], I see mozbrowserloadstart from the app > which is opening from cardview, but I don't see it on my Flame when I switch > app from cardview: > > E/GeckoConsole( 206): Content JS LOG at > app://system.gaiamobile.org/js/app_window.js:1035 in aw_debug: > [AppWindow][Settings][AppWindow_8][2744.345] open with from-cardview > E/GeckoConsole( 206): Content JS LOG at > app://system.gaiamobile.org/js/app_window.js:1035 in aw_debug: > [AppWindow][Settings][AppWindow_8][2744.346] closed,opening,::,open > E/GeckoConsole( 206): Content JS LOG at > app://system.gaiamobile.org/js/app_window_manager.js:694 in awm_debug: > [AppWindowManager][2744.419]=== Active app now is: ,Settings,=== > E/GeckoConsole( 206): Content JS LOG at > app://system.gaiamobile.org/js/app_window.js:1035 in aw_debug: > [AppWindow][Settings][AppWindow_8][2746.810] Handling mozbrowserloadstart > event... > It's because in your flame the app is not killed by gecko but in the test it's killed by OOM or something. [AppWindow][Settings][AppWindow_8][1694.296] Handling mozbrowsererror event... [AppWindow][Settings][AppWindow_8][1694.303] publishing internal event: crashed [AppWindow][Settings][AppWindow_8][1694.306] publishing external event: crashed [AppWindow][Settings][AppWindow_8][1694.307] ..sleep! I will come back.
Comment 67 is the correct direction, I got the exact STR now: 1. Launch an app 2. Press home key back to homescreen 3. $ adb shell kill -9 [PID] 4. Launch the same app again from homescreen
BTW, I found AppWindow.destroyBrowser() does not set iframe null and leak it.
Log analysis: Let's focus on settings app (AppWindow_8): It was launched here: * [AppWindow][Settings][AppWindow_8][209.432] Handling mozbrowserloadstart event... Killed here at background: * [AppWindow][Settings][AppWindow_8][1137.441] Handling mozbrowsererror event... Resumed here by launch request (not sure where it's coming from though) * [AppWindow][Settings][AppWindow_8][1150.738] ...revived! Request to be foreground here * [AppWindow][Settings][AppWindow_8][1150.855] publishing internal event: requestforeground * [AppWindow][Settings][AppWindow_8][1150.856] publishing external event: requestforeground VisibilityManager permits and send it to foreground here * [AppWindow][Settings][AppWindow_8][1150.856] set visibility -> ,true * [AppWindow][Settings][AppWindow_8][1150.857] before showing frame Another load starts * [AppWindow][Settings][AppWindow_8][1151.334] Handling mozbrowserloadstart event... Gecko tell us it's in background! * [AppWindow][Settings][AppWindow_8][1151.414] publishing internal event: background <<<<<<< I suspect it's because this is not executed for some reason https://github.com/mozilla-b2g/gaia/blob/master/apps/system/js/app_window.js#L248 I am able to reproduce this in master: * Open clock app. * Back to homescreen. * Invoke TaskManager. * Use AppManager and debug System app then type this in console appWindowManager._apps.AppWindow_1.destroyBrowser(); // to simulate mozbrowsererror * Click the clock card in task manager Now you will see all black clock app. But if you back to homescreen and launch clock by tapping icon you will see the usable clock app again. Gaia issue indeed, but not sure where's the regression coming from.
Assignee: nobody → alive
Component: Stability → Gaia::System::Window Mgmt
Flags: needinfo?(alive)
WOW...I failed to understand why this worked before (will do more investigation)...I think it was ever working...do you? The problem is in showFrame we rely on the hidden class of the browser element to see if we are already shown but we are removing the hidden class as well as the browser element in destroy browser and we are sending it to background on reviving without setting the hidden class.
Attachment #8510280 - Flags: review?(etienne)
Can you simply fix the leak of comment 17 as well?
Flags: needinfo?(alive)
(In reply to Ting-Yu Chou [:ting] from comment #73) > Can you simply fix the leak of comment 17 as well? Correction: comment 70
(In reply to Ting-Yu Chou [:ting] from comment #74) > (In reply to Ting-Yu Chou [:ting] from comment #73) > > Can you simply fix the leak of comment 17 as well? > > Correction: comment 70 Not sure what you want..in destoryBrowser we are removing the DOM element totally, is this insufficient?
Flags: needinfo?(alive)
(In reply to Alive Kuo [:alive][NEEDINFO!] from comment #75) > (In reply to Ting-Yu Chou [:ting] from comment #74) > > (In reply to Ting-Yu Chou [:ting] from comment #73) > > > Can you simply fix the leak of comment 17 as well? > > > > Correction: comment 70 > > Not sure what you want..in destoryBrowser we are removing the DOM element > totally, is this insufficient? Uh..this.iframe is not removed. Lemme do it. Thanks.
Comment on attachment 8510280 [details] [review] https://github.com/mozilla-b2g/gaia/pull/25448 (In reply to Alive Kuo [:alive][NEEDINFO!] from comment #72) > Created attachment 8510280 [details] [review] > https://github.com/mozilla-b2g/gaia/pull/25448 > > WOW...I failed to understand why this worked before (will do more > investigation)...I think it was ever working...do you? > Maybe we broke it when reworking the screenshoting :/
Attachment #8510280 - Flags: review?(etienne) → review+
https://github.com/mozilla-b2g/gaia/commit/39f42dc6a2b4a1932433ca2128901fd2c7b84dc9
Status: NEW → RESOLVED
Closed: 10 years ago
status-b2g-v2.2: --- → fixed
Resolution: --- → FIXED
(In reply to Walter Chen[:ypwalter][:wachen] from comment #61) > Created attachment 8509374 [details] > output_debug_200.zip > > Tapas, it actually quite reproducible in this short run. Please see the > attached file. We are running another run for you again with video now. this seems to be already resolved. Please make a NI to me if I still need to look into your uploaded logs. Thanks a lot :)
Flags: needinfo?(tkundu) → needinfo?(wachen)
status-b2g-v2.1: --- → affected
Flags: needinfo?(wachen)
Tapa, I will NI you again if anything goes wrong. This bug is with v2.1 blocking. Please uplift.
This is a v2.1 blocking bug. Please help with uplifting.
Flags: needinfo?(bbajaj)
Flags: needinfo?(alive)
Comment on attachment 8510280 [details] [review] https://github.com/mozilla-b2g/gaia/pull/25448 [Approval Request Comment] [Bug caused by] (feature/regressing bug #): Regression but not sure which one. [User impact] if declined If an app is ever killed at background, it will not be usable if the user taps app icon or task manager to relaunch it until the user switches to another app and back. [Testing completed] Yes [Risk to taking this patch] (and alternatives if risky): Risk less [String changes made]: No
Flags: needinfo?(alive)
Attachment #8510280 - Flags: approval-gaia-v2.1?
Flags: needinfo?(bbajaj)
Attachment #8510280 - Flags: approval-gaia-v2.1? → approval-gaia-v2.1+
Hi, alive, it is approved, can you help with this one? Thank you so much.
Flags: needinfo?(alive)
I guess release eng will take care of this.
Flags: needinfo?(alive)
Thank you for helping, guys! This bug is now resolved! I see no reproduction of this issue in most recent run. PVT v2.1 build : 20141030161200
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: