Attaching recovery log files 

Deleted: recovery_logs.zip 88.7 KB

recovery_logs.zip 88.7 KB Download

CC'ing a few people to possibly take a look at this.

Friendly ping to get an update as it is marked as RBB. Thanks

Issue is still seen on 70.0.3538.0/11035.0.0 dev-channel Cyan 

Thanks..!!

Since this is RBB can anyone help suggest an owner please. Thanks

CC people from platform2/installer . Could somebody take a look?

if you have a reliable reproduction, could you bisect it down a bit more for us ?  you've said 10949.0.0 is failing, but what is a good version ?  10895.0.0 is the R69 branch point, so starting with a version around there would be good.

Tried to recover the build On 70.0.3538.0/11036.0.0 via USB(Esc+Reload+Power) After recovery is done ,remove USB -> observed device gets shutdown(Crash is seen) and it takes time to show Welcome screen

Expected: After removing USB OOBE screen should be seen immediately without any delay
Actual: Instead observed Crash is seen after removing USB 

Attaching Recover logs and unable to attach device logs as  issue 863853  is seen on Cyan

Thanks..!!

Deleted: recovery_logs.1536215846-20180906T064545Z-001.zip 91.5 KB

recovery_logs.1536215846-20180906T064545Z-001.zip 91.5 KB Download

we already know 10949.0.0+ is failing.  please try older versions to narrow down the regression range.

C#12>>

Good Build: 69.0.3497.21/10895.10.0
Bad Build:  70.0.3508.3/10930.0.0

Thanks..!!

I was unable to reproduce this issue on a Cyan MP device running R70-11021.6.0

After removing the USB recovery stick, the device rebooted successfully to dev screen without having to manually press the power button again.

Good Build: 70.0.3498.0/10897.0.0
Bad Build:  70.0.3501.0/10908.0.0

Note : 
1)In Bad Builds to get welcome screen 20-30 seconds delay is seen where in good Builds it takes 5 -8 sec time to get Welcome screen
(Please refer Video)
2)Recovery failure issue is seen in 70.0.3500.0/10904.0.0 ,70.0.3499.0/10900.0.0


Attaching Actual and Expected videos for reference

Deleted: Actual_CyanRecovery.mp4 14.2 MB

	Actual_CyanRecovery.mp4 14.2 MB View Download

The immediate issue I see is :
+ exec
[   71.057736] CLKRUN not enabled!
[   71.057742] Modules linked in:
[   71.057750] CPU: 2 PID: 521 Comm: tpmc Tainted: G        W      3.18.0-18552-gfb21b159c65c #2
[   71.057761] Hardware name: GOOGLE Cyan, BIOS Google_Cyan.7287.57.100 01/01/2017
[   71.057770]  0000000000000000 000000007a4efa53 ffff88003ef3fce8 ffffffff9d73a5ef
[   71.057785]  0000000000000000 ffff88003ef3fd40 ffff88003ef3fd28 ffffffff9d0a545e
[   71.057799]  0000000000000000 0000000000000018 ffff88003ef3fdff ffff88017a852800
[   71.057814] Call Trace:
[   71.057821]  [<ffffffff9d73a5ef>] dump_stack+0x4e/0x71
[   71.057832]  [<ffffffff9d0a545e>] warn_slowpath_common+0x84/0x9f
[   71.057842]  [<ffffffff9d0a54ce>] warn_slowpath_fmt+0x55/0x6b
[   71.057854]  [<ffffffff9d3a4aff>] ? tpm_tis_status+0x31/0x4a
[   71.057864]  [<ffffffff9d3a6cd0>] write_mem_bytes+0x57/0xe6
[   71.057875]  [<ffffffff9d3a4993>] write_tpm_byte+0x38/0x4e
[   71.057885]  [<ffffffff9d3a4b37>] tpm_tis_ready+0x1f/0x21
[   71.057896]  [<ffffffff9d3a4ec8>] tpm_tis_recv+0xda/0xf9
[   71.057906]  [<ffffffff9d3a2411>] tpm_transmit+0x1b0/0x201
[   71.057917]  [<ffffffff9d3a3373>] tpm_write+0xa7/0xed
[   71.057927]  [<ffffffff9d196f04>] vfs_write+0xb2/0xf7
[   71.057937]  [<ffffffff9d197565>] SyS_write+0x5d/0x9f
[   71.057948]  [<ffffffff9d740004>] system_call_fastpath+0x21/0x26
[   71.057957] ---[ end trace d33920290e5a7b43 ]---
[   71.057965] ------------[ cut here ]------------

repeatedly in the logs, which seems like the source of the problem?!

Friendly ping. Checking on the progress of these RBBs, please update with an ETA on fixes if this issue is still an RBB. Otherwise please remove the RBB label. Thanks.

Checking on the progress of these RBBs, please update with an ETA on fixes if this issue is still an RBB. 

Otherwise please remove the RBB label. Thanks.

I was also unable to produce this on a 11065.0.0 and with a bad build mentioned #15 (70.0.3501.0/10908.0.0) with a cyan pvt sku2 and it worked fine in both cases.

Moving from RBB to RBS as it looks like we're unable to repro at the moment.

This bug does not have an owner and is marked RBS. Please update with the plan and ETA to fix the issue or remove the RBS label if this is no longer a blocker. Thanks.

bulk edit] Removing Release Block Stable. Please feel free to reapply label with justification in a comment. Thanks.