# BBG stopped reponding

**URL:** <https://forum.digikey.com/t/bbg-stopped-reponding/44841>\
**Category:** Linux Discussions\
**Created:** [September 12, 2024, 1:38pm UTC](https://forum.digikey.com/t/bbg-stopped-reponding/44841 "2024-09-12T13:38:14Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![chougulemrudula](https://avatars.discourse-cdn.com/v4/letter/c/a698b9/32.png) [@chougulemrudula](https://forum.digikey.com/u/chougulemrudula)\
**Post date:** [September 12, 2024, 1:38pm UTC](https://forum.digikey.com/t/bbg-stopped-reponding/44841/1 "2024-09-12T13:38:14Z")

</div>

Hi,

I have been using bbg running ubuntu 20.04, which is build using Rootfs builder. Recently I upgraded the filesystem. It is running over a few weeks and one day bbg stopped responding and observed the below error:

61145.707069] sdhci-omap 48060000.mmc: error -110 requesting status  
[33](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L33) [61145.707101] mmcblk0: recovery failed!  
[34](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L34) [61145.707182] blk\_update\_request: I/O error, dev mmcblk0, sector 3994280 op 0x0:(READ) flags 0x80700 phys\_seg 4 prio class 0  
[35](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L35) [61145.715788] sdhci-omap 48060000.mmc: error -110 requesting status  
[36](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L36) [61145.715814] mmcblk0: recovery failed!  
[37](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L37) [61145.715870] blk\_update\_request: I/O error, dev mmcblk0, sector 3994280 op 0x0:(READ) flags 0x0 phys\_seg 1 prio class 0  
[38](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L38)  
[39](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L39) [61156.068870] sdhci-omap 48060000.mmc: error -110 requesting status  
[40](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L40) [61156.068904] mmcblk0: recovery failed!  
[41](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L41) [61156.068969] blk\_update\_request: I/O error, dev mmcblk0, sector 3988120 op 0x0:(READ) flags 0x80700 phys\_seg 2 prio class 0  
[42](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L42) [61156.079623] sdhci-omap 48060000.mmc: error -110 requesting status  
[43](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L43) [61156.079650] mmcblk0: recovery failed!  
[44](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L44) [61156.079711] blk\_update\_request: I/O error, dev mmcblk0, sector 3988128 op 0x0:(READ) flags 0x0 phys\_seg 1 prio class 0  
[45](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L45) [61156.087233] sdhci-omap 48060000.mmc: error -110 requesting status  
[46](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L46) [61156.087261] mmcblk0: recovery failed!  
[47](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L47) [61156.087323] blk\_update\_request: I/O error, dev mmcblk0, sector 3988128 op 0x0:(READ) flags 0x0 phys\_seg 1 prio class 0  
[48](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L48) [61156.318440] sdhci-omap 48060000.mmc: error -110 requesting status  
[49](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L49) [61156.318474] mmcblk0: recovery failed!  
[50](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L50) [61156.318531] blk\_update\_request: I/O error, dev mmcblk0, sector 3988128 op 0x0:(READ) flags 0x0 phys\_seg 1 prio class 0  
[51](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L51) [61156.334024] sdhci-omap 48060000.mmc: error -110 requesting status  
[52](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L52) [61156.334048] mmcblk0: recovery failed!  
[53](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L53) [61156.334105] blk\_update\_request: I/O error, dev mmcblk0, sector 3988128 op 0x0:(READ) flags 0x0 phys\_seg 1 prio class 0  
[54](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L54) [61156.568700] sdhci-omap 48060000.mmc: error -110 requesting status  
[55](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L55) [61156.568733] mmcblk0: recovery failed!  
[56](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L56) [61156.568794] blk\_update\_request: I/O error, dev mmcblk0, sector 3988128 op 0x0:(READ) flags 0x0 phys\_seg 1 prio class 0  
[57](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L57) [61156.579724] sdhci-omap 48060000.mmc: error -110 requesting status  
[58](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L58) [61156.579749] mmcblk0: recovery failed!  
[59](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L59) [61156.579808] blk\_update\_request: I/O error, dev mmcblk0, sector 3988128 op 0x0:(READ) flags 0x0 phys\_seg 1 prio class 0  
[60](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L60) [61156.610426] sdhci-omap 48060000.mmc: error -110 requesting status  
[61](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L61) [61156.610453] mmcblk0: recovery failed!  
[62](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L62) [61156.610532] blk\_update\_request: I/O error, dev mmcblk0, sector 904240 op 0x0:(READ) flags 0x80700 phys\_seg 1 prio class 0  
[63](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L63) [61156.618277] sdhci-omap 48060000.mmc: error -110 requesting status  
[64](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L64) [61156.618307] mmcblk0: recovery failed!  
[65](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L65) [61156.618382] blk\_update\_request: I/O error, dev mmcblk0, sector 904240 op 0x0:(READ) flags 0x0 phys\_seg 1 prio class 0  
[66](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L66) [61156.627142] sdhci-omap 48060000.mmc: error -110 requesting status  
[67](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L67) [61156.627174] mmcblk0: recovery failed!  
[68](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L68) [61156.627237] blk\_update\_request: I/O error, dev mmcblk0, sector 904240 op 0x0:(READ) flags 0x0 phys\_seg 1 prio class 0  
[69](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L69) [61156.635709] sdhci-omap 48060000.mmc: error -110 requesting status  
[70](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L70) [61156.635743] mmcblk0: recovery failed!  
[71](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L71) [61156.643865] sdhci-omap 48060000.mmc: error -110 requesting status  
[72](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L72) [61156.643895] mmcblk0: recovery failed!  
[73](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L73) [61156.651731] sdhci-omap 48060000.mmc: error -110 requesting status  
[74](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L74) [61156.651761] mmcblk0: recovery failed!  
[75](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L75) [61156.659566] sdhci-omap 48060000.mmc: error -110 requesting status  
[76](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L76) [61156.659591] mmcblk0: recovery failed!  
[77](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L77) [61156.694069] sdhci-omap 48060000.mmc: error -110 requesting status  
[78](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L78) [61156.694095] mmcblk0: recovery failed!  
[79](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L79) [61156.702659] sdhci-omap 48060000.mmc: error -110 requesting status  
[80](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L80) [61156.702686] mmcblk0: recovery failed!  
[81](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L81) [61156.711343] sdhci-omap 48060000.mmc: error -110 requesting status  
[82](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L82) [61156.711375] mmcblk0: recovery failed!  
[83](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L83) [61156.719933] sdhci-omap 48060000.mmc: error -110 requesting status  
[84](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L84) [61156.719965] mmcblk0: recovery failed!  
[85](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L85) [61156.728193] sdhci-omap 48060000.mmc: error -110 requesting status  
[86](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L86) [61156.728226] mmcblk0: recovery failed!  
[87](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L87) [61156.736179] sdhci-omap 48060000.mmc: error -110 requesting status  
[88](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L88) [61156.736208] mmcblk0: recovery failed!  
[89](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L89) [61156.744037] sdhci-omap 48060000.mmc: error -110 requesting status  
[90](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L90) [61156.744067] mmcblk0: recovery failed!  
[91](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L91) [61156.752237] sdhci-omap 48060000.mmc: error -110 requesting status  
[92](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L92) [61156.752270] mmcblk0: recovery failed!  
[93](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L93) [61156.760234] sdhci-omap 48060000.mmc: error -110 requesting status  
[94](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L94) [61156.760263] mmcblk0: recovery failed!  
[95](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L95) [61156.769281] sdhci-omap 48060000.mmc: error -110 requesting status  
[96](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L96) [61156.769311] mmcblk0: recovery failed!  
[97](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L97) [61156.777328] sdhci-omap 48060000.mmc: error -110 requesting status  
[98](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L98) [61156.777361] mmcblk0: recovery failed!  
[99](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L99) [61156.785294] sdhci-omap 48060000.mmc: error -110 requesting status  
[100](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L100) [61156.785322] mmcblk0: recovery failed!  
[101](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L101) [61156.793188] sdhci-omap 48060000.mmc: error -110 requesting status  
[102](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L102) [61156.793220] mmcblk0: recovery failed!  
[103](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L103) [61156.826662] sdhci-omap 48060000.mmc: error -110 requesting status  
[104](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L104) [61156.826694] mmcblk0: recovery failed!  
[105](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L105) [61156.826989] EXT4-fs error (device mmcblk0p1): \_\_ext4\_find\_entry:1534: inode #3710: comm accounts-daemon: reading directory lblock 0  
[106](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L106) [61156.835070] sdhci-omap 48060000.mmc: error -110 requesting status  
[107](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L107) [61156.835102] mmcblk0: recovery failed!  
[108](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L108) [61156.835178] Buffer I/O error on dev mmcblk0p1, logical block 0, lost sync page write  
[109](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L109) [61156.835280] EXT4-fs (mmcblk0p1): I/O error while writing superblock  
[110](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L110) [61156.897379] sdhci-omap 48060000.mmc: error -110 requesting status  
[111](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L111) [61156.897412] mmcblk0: recovery failed!  
[112](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L112) [61156.922206] sdhci-omap 48060000.mmc: error -110 requesting status  
[113](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L113) [61156.922241] mmcblk0: recovery failed!  
[114](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L114) [61157.014437] sdhci-omap 48060000.mmc: error -110 requesting status  
[115](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L115) [61157.014464] mmcblk0: recovery failed!  
[116](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L116) [61157.022311] sdhci-omap 48060000.mmc: error -110 requesting status  
[117](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L117) [61157.022340] mmcblk0: recovery failed!  
[118](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L118) [61157.292706] sdhci-omap 48060000.mmc: error -110 requesting status  
[119](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L119) [61157.292734] mmcblk0: recovery failed!  
[120](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L120) [61157.303856] sdhci-omap 48060000.mmc: error -110 requesting status  
[121](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L121) [61157.303882] mmcblk0: recovery failed!  
[122](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L122) [61157.533046] sdhci-omap 48060000.mmc: error -110 requesting status  
[123](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L123) [61157.533081] mmcblk0: recovery failed!  
[124](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L124) [61157.541572] sdhci-omap 48060000.mmc: error -110 requesting status  
[125](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L125) [61157.541604] mmcblk0: recovery failed!  
[126](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L126) [61157.549886] sdhci-omap 48060000.mmc: error -110 requesting status  
[127](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L127) [61157.549917] mmcblk0: recovery failed!  
[128](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L128) [61157.557742] sdhci-omap 48060000.mmc: error -110 requesting status  
[129](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L129) [61157.557771] mmcblk0: recovery failed!  
[130](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L130) [61157.565546] sdhci-omap 48060000.mmc: error -110 requesting status  
[131](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L131) [61157.565574] mmcblk0: recovery failed!  
[132](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L132) [61157.573814] sdhci-omap 48060000.mmc: error -110 requesting status  
[133](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L133) [61157.573842] mmcblk0: recovery failed!  
[134](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L134) [61157.581709] sdhci-omap 48060000.mmc: error -110 requesting status  
[135](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L135) [61157.581735] mmcblk0: recovery failed!  
[136](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L136) [61157.589787] sdhci-omap 48060000.mmc: error -110 requesting status  
[137](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L137) [61157.589821] mmcblk0: recovery failed!  
[138](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L138) [61157.597875] sdhci-omap 48060000.mmc: error -110 requesting status  
[139](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L139) [61157.597902] mmcblk0: recovery failed!  
[140](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L140) [61157.605968] sdhci-omap 48060000.mmc: error -110 requesting status  
[141](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L141) [61157.605996] mmcblk0: recovery failed!  
[142](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L142) [61157.614010] sdhci-omap 48060000.mmc: error -110 requesting status  
[143](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L143) [61157.614037] mmcblk0: recovery failed!  
[144](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L144) [61157.622097] sdhci-omap 48060000.mmc: error -110 requesting status  
[145](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L145) [61157.622125] mmcblk0: recovery failed!  
[146](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L146) [61157.630873] sdhci-omap 48060000.mmc: error -110 requesting status  
[147](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L147) [61157.630898] mmcblk0: recovery failed!  
[148](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L148) [61157.638783] sdhci-omap 48060000.mmc: error -110 requesting status  
[149](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L149) [61157.638807] mmcblk0: recovery failed!  
[150](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L150) [61157.646913] sdhci-omap 48060000.mmc: error -110 requesting status  
[151](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L151) [61157.646938] mmcblk0: recovery failed!  
[152](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L152) [61157.654780] sdhci-omap 48060000.mmc: error -110 requesting status  
[153](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L153) [61157.654808] mmcblk0: recovery failed!  
[154](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L154) [61157.663115] sdhci-omap 48060000.mmc: error -110 requesting status  
[155](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L155) [61157.663144] mmcblk0: recovery failed!  
[156](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L156) [61157.670927] sdhci-omap 48060000.mmc: error -110 requesting status  
[157](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L157) [61157.670952] mmcblk0: recovery failed!  
[158](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L158) [61157.678838] sdhci-omap 48060000.mmc: error -110 requesting status  
[159](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L159) [61157.678863] mmcblk0: recovery failed!  
[160](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L160) [61157.686914] sdhci-omap 48060000.mmc: error -110 requesting status  
[161](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L161) [61157.686941] mmcblk0: recovery failed!  
[162](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L162) [61157.687075] EXT4-fs error (device mmcblk0p1): \_\_ext4\_find\_entry:1534: inode #3710: comm accounts-daemon: reading directory lblock 0  
[163](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L163) [61157.694336] sdhci-omap 48060000.mmc: error -110 requesting status  
[164](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L164) [61157.694362] mmcblk0: recovery failed!  
[165](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L165) [61157.694434] Buffer I/O error on dev mmcblk0p1, logical block 0, lost sync page write  
[166](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L166) [61157.694524] EXT4-fs (mmcblk0p1): I/O error while writing superblock  
[167](http://vilterrecip.net/trac/attachment/ticket/1053/SystemStuckwith%20Bluescreen#L167)

I have been debugging this issue for a long time. It happened once and could not reproduce.

Please provide your suggestions/ thoughts.

Thanks

---

<div class="post-metadata">

**Author:** ![RobertCNelson](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/robertcnelson/32/12_2.png) [@RobertCNelson](https://forum.digikey.com/u/RobertCNelson)\
**Post date:** [September 12, 2024, 2:03pm UTC](https://forum.digikey.com/t/bbg-stopped-reponding/44841/2 "2024-09-12T14:03:16Z")

</div>

> [@chougulemrudula](#):
>
> sdhci-omap 48060000.mmc: error -110 requesting status

Your microSD or eMMC on the BBG has now worn out and is dead…

Regards,

---

<div class="post-metadata">

**Author:** ![chougulemrudula](https://avatars.discourse-cdn.com/v4/letter/c/a698b9/32.png) [@chougulemrudula](https://forum.digikey.com/u/chougulemrudula)\
**Post date:** [September 13, 2024, 8:36am UTC](https://forum.digikey.com/t/bbg-stopped-reponding/44841/3 "2024-09-13T08:36:26Z")

</div>

Thanks Robert for your prompt reply.

I did reboot the BBG and then it seems working well. So far i have not observed this issue again,

Please suggest fix or detection methods to resolve this issue.

---

<div class="post-metadata">

**Author:** ![RobertCNelson](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/robertcnelson/32/12_2.png) [@RobertCNelson](https://forum.digikey.com/u/RobertCNelson)\
**Post date:** [September 13, 2024, 2:12pm UTC](https://forum.digikey.com/t/bbg-stopped-reponding/44841/4 "2024-09-13T14:12:05Z")

</div>

Pull important data off of it, and start prepping to use a new microSD, i wouldn’t trust it.

Regards,

---

<div class="post-metadata">

**Author:** ![chougulemrudula](https://avatars.discourse-cdn.com/v4/letter/c/a698b9/32.png) [@chougulemrudula](https://forum.digikey.com/u/chougulemrudula)\
**Post date:** [September 24, 2024, 11:22am UTC](https://forum.digikey.com/t/bbg-stopped-reponding/44841/5 "2024-09-24T11:22:58Z")

</div>

Okay, Sure. Appreciate your suggestions.  
Meanwhile, I started exploring the images that can be flashed to internal memory eMMC. The current filesystem I built using rootfs image builder for ubuntu 20.04. Do we have any method that can convert this filesystem to eMMC format that allows us to use internal memory? or Can I have process for building image which can be flashed to eMMC?

---

<div class="post-metadata">

**Author:** ![RobertCNelson](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/robertcnelson/32/12_2.png) [@RobertCNelson](https://forum.digikey.com/u/RobertCNelson)\
**Post date:** [September 24, 2024, 2:53pm UTC](https://forum.digikey.com/t/bbg-stopped-reponding/44841/6 "2024-09-24T14:53:29Z")

</div>

The scrpts are built-into your image:

Install flashing scripts:

```auto
sudo apt-get update
sudo apt-get install bb-beagle-flasher

```

Configure microSD → eMMC mode:

```auto
sudo cp -v /etc/beagle-flasher/beaglebone-black-microsd-to-emmc /etc/default/beagle-flasher

```

Then, start flasher, will start copying microSD to eMMC…

```auto
sudo beagle-flasher

```

Regards,

---

<div class="post-metadata">

**Author:** ![chougulemrudula](https://avatars.discourse-cdn.com/v4/letter/c/a698b9/32.png) [@chougulemrudula](https://forum.digikey.com/u/chougulemrudula)\
**Post date:** [September 24, 2024, 4:51pm UTC](https://forum.digikey.com/t/bbg-stopped-reponding/44841/7 "2024-09-24T16:51:29Z")

</div>

Thank you for your prompt response. will try the same.

Thanks

---

<div class="post-metadata">

**Author:** ![ppadmanabhan](https://avatars.discourse-cdn.com/v4/letter/p/dbc845/32.png) [@ppadmanabhan](https://forum.digikey.com/u/ppadmanabhan)\
**Post date:** [September 25, 2024, 6:08am UTC](https://forum.digikey.com/t/bbg-stopped-reponding/44841/8 "2024-09-25T06:08:51Z")

</div>

Is there a application like raspberry pi sd card speed test for BBG

---

<div class="post-metadata">

**Author:** ![RobertCNelson](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/robertcnelson/32/12_2.png) [@RobertCNelson](https://forum.digikey.com/u/RobertCNelson)\
**Post date:** [September 25, 2024, 2:18pm UTC](https://forum.digikey.com/t/bbg-stopped-reponding/44841/9 "2024-09-25T14:18:41Z")

</div>

Both devices run Linux. Same tool should work on both.

Regards,

---

<div class="post-metadata">

**Author:** ![chougulemrudula](https://avatars.discourse-cdn.com/v4/letter/c/a698b9/32.png) [@chougulemrudula](https://forum.digikey.com/u/chougulemrudula)\
**Post date:** [October 16, 2024, 1:48pm UTC](https://forum.digikey.com/t/bbg-stopped-reponding/44841/10 "2024-10-16T13:48:41Z")

</div>

Hi Robert,

I tried the above steps and seems like it failed. I am having below errors

sudo apt-get update  
Err:1 [Index of /ubuntu](http://repos.rcn-ee.com/ubuntu) focal InRelease  
Temporary failure resolving ‘[repos.rcn-ee.com](http://repos.rcn-ee.com)’  
Err:2 [http://ports.ubuntu.com](http://ports.ubuntu.com) focal InRelease  
Temporary failure resolving ‘[ports.ubuntu.com](http://ports.ubuntu.com)’  
Reading package lists… Done  
W: Failed to fetch [http://ports.ubuntu.com/dists/focal/InRelease](http://ports.ubuntu.com/dists/focal/InRelease) Temporary failure resolving ‘[ports.ubuntu.com](http://ports.ubuntu.com)’  
W: Failed to fetch [http://repos.rcn-ee.com/ubuntu/dists/focal/InRelease](http://repos.rcn-ee.com/ubuntu/dists/focal/InRelease) Temporary failure resolving ‘[repos.rcn-ee.com](http://repos.rcn-ee.com)’  
W: Some index files failed to download. They have been ignored, or old ones used instead.  
vilter@vilter-recip:~$ sudo apt-get update  
Err:1 [Index of /ubuntu](http://repos.rcn-ee.com/ubuntu) focal InRelease  
Temporary failure resolving ‘[repos.rcn-ee.com](http://repos.rcn-ee.com)’  
Err:2 [http://ports.ubuntu.com](http://ports.ubuntu.com) focal InRelease  
Temporary failure resolving ‘[ports.ubuntu.com](http://ports.ubuntu.com)’  
Reading package lists… Done  
W: Failed to fetch [http://ports.ubuntu.com/dists/focal/InRelease](http://ports.ubuntu.com/dists/focal/InRelease) Temporary failure resolving ‘[ports.ubuntu.com](http://ports.ubuntu.com)’  
W: Failed to fetch [http://repos.rcn-ee.com/ubuntu/dists/focal/InRelease](http://repos.rcn-ee.com/ubuntu/dists/focal/InRelease) Temporary failure resolving ‘[repos.rcn-ee.com](http://repos.rcn-ee.com)’  
W: Some index files failed to download. They have been ignored, or old ones used instead.

Please suggest the further steps to resolve this errors.

Thanks

---

<div class="post-metadata">

**Author:** ![RobertCNelson](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/robertcnelson/32/12_2.png) [@RobertCNelson](https://forum.digikey.com/u/RobertCNelson)\
**Post date:** [October 16, 2024, 2:22pm UTC](https://forum.digikey.com/t/bbg-stopped-reponding/44841/11 "2024-10-16T14:22:01Z")

</div>

Check your network connection.

Regards,

---

<div class="post-metadata">

**Author:** ![chougulemrudula](https://avatars.discourse-cdn.com/v4/letter/c/a698b9/32.png) [@chougulemrudula](https://forum.digikey.com/u/chougulemrudula)\
**Post date:** [October 16, 2024, 5:00pm UTC](https://forum.digikey.com/t/bbg-stopped-reponding/44841/12 "2024-10-16T17:00:49Z")

</div>

Yes, I did fix the network issue. There are certification errors

sudo apt-get install bb-beagle-flasher  
Reading package lists… Done  
Building dependency tree  
Reading state information… Done  
The following additional packages will be installed:  
bb-u-boot-am335x-evm bb-u-boot-am57xx-evm mmc-utils  
The following NEW packages will be installed:  
bb-beagle-flasher bb-u-boot-am335x-evm bb-u-boot-am57xx-evm mmc-utils  
0 upgraded, 4 newly installed, 0 to remove and 1 not upgraded.  
Need to get 736 kB/774 kB of archives.  
After this operation, 2,650 kB of additional disk space will be used.  
Do you want to continue? [Y/n] y  
Err:1 [Index of /ubuntu](https://repos.rcn-ee.com/ubuntu) focal/main armhf bb-u-boot-am335x-evm armhf 2022.04.20240115.0-0~focal+20240115  
Certificate verification failed: The certificate is NOT trusted. The certificate chain uses not yet valid certificate. Could not handshake: Error in the certificate verification. [IP: 5.161.107.156 44  
3]  
Err:2 [Index of /ubuntu](https://repos.rcn-ee.com/ubuntu) focal/main armhf bb-u-boot-am57xx-evm armhf 2022.04.20240115.0-0~focal+20240115  
Certificate verification failed: The certificate is NOT trusted. The certificate chain uses not yet valid certificate. Could not handshake: Error in the certificate verification. [IP: 5.161.107.156 44  
3]  
Err:3 [Index of /ubuntu](https://repos.rcn-ee.com/ubuntu) focal/main armhf bb-beagle-flasher armhf 1.20240717.0-0~focal+20240717  
Certificate verification failed: The certificate is NOT trusted. The certificate chain uses not yet valid certificate. Could not handshake: Error in the certificate verification. [IP: 5.161.107.156 44  
3]  
E: Failed to fetch [https://repos.rcn-ee.com/ubuntu/pool/main/b/bb-u-boot-am335x-evm/bb-u-boot-am335x-evm\_2022.04.20240115.0-0~focal+20240115\_armhf.deb](https://repos.rcn-ee.com/ubuntu/pool/main/b/bb-u-boot-am335x-evm/bb-u-boot-am335x-evm_2022.04.20240115.0-0~focal+20240115_armhf.deb) Certificate verification failed: The certificate is  
NOT trusted. The certificate chain uses not yet valid certificate. Could not handshake: Error in the certificate verification. [IP: 5.161.107.156 443]  
E: Failed to fetch [https://repos.rcn-ee.com/ubuntu/pool/main/b/bb-u-boot-am57xx-evm/bb-u-boot-am57xx-evm\_2022.04.20240115.0-0~focal+20240115\_armhf.deb](https://repos.rcn-ee.com/ubuntu/pool/main/b/bb-u-boot-am57xx-evm/bb-u-boot-am57xx-evm_2022.04.20240115.0-0~focal+20240115_armhf.deb) Certificate verification failed: The certificate is  
NOT trusted. The certificate chain uses not yet valid certificate. Could not handshake: Error in the certificate verification. [IP: 5.161.107.156 443]  
E: Failed to fetch [https://repos.rcn-ee.com/ubuntu/pool/main/b/bb-beagle-flasher/bb-beagle-flasher\_1.20240717.0-0~focal+20240717\_armhf.deb](https://repos.rcn-ee.com/ubuntu/pool/main/b/bb-beagle-flasher/bb-beagle-flasher_1.20240717.0-0~focal+20240717_armhf.deb) Certificate verification failed: The certificate is NOT trusted  
. The certificate chain uses not yet valid certificate. Could not handshake: Error in the certificate verification. [IP: 5.161.107.156 443]  
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

Thanks

---

<div class="post-metadata">

**Author:** ![RobertCNelson](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/robertcnelson/32/12_2.png) [@RobertCNelson](https://forum.digikey.com/u/RobertCNelson)\
**Post date:** [October 16, 2024, 5:11pm UTC](https://forum.digikey.com/t/bbg-stopped-reponding/44841/13 "2024-10-16T17:11:07Z")

</div>

> [@chougulemrudula](#):
>
> Certificate verification failed: The certificate is NOT trusted. The certificate chain uses not yet valid certificate. Could not handshake: Error in the certificate verification.

Your system clock is off… Usually systemd-timesyncd takes a minute or two to update the system time.

Regards,

---

<div class="post-metadata">

**Author:** ![chougulemrudula](https://avatars.discourse-cdn.com/v4/letter/c/a698b9/32.png) [@chougulemrudula](https://forum.digikey.com/u/chougulemrudula)\
**Post date:** [October 16, 2024, 5:24pm UTC](https://forum.digikey.com/t/bbg-stopped-reponding/44841/14 "2024-10-16T17:24:26Z")

</div>

Thanks for your inputs. I set the current date and tried above steps. Seems like it is unable to copy the micro sd card ubuntu filesystem. I have below log

```auto
$ **sudo beagle-flasher** 
--------------------------------------------------------------------------------
Version: [1.20240419.0, merged usr cleanups...]
--------------------------------------------------------------------------------
cat /etc/default/beagle-flasher:
--------------------------------------------------------------------------------
#debug_over_display=tty0
source=/dev/mmcblk0
destination=/dev/mmcblk1
rfs_partition=single
rfs_rootfs_type=ext4
rfs_rootfs_startmb=4
bootloader=/opt/u-boot/bb-u-boot-am335x-evm/install-mmcblk1.sh
flash_back=beaglebone-black-emmc-to-microsd
--------------------------------------------------------------------------------
INFO: /proc/cmdline
INFO: [cat /proc/cmdline]
console=ttyS0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M quiet
--------------------------------------------------------------------------------
INFO: Preparing sysctl
INFO: [sysctl: vm.min_free_kbytes=[16384]
INFO: [sysctl: setting: [sysctl -w vm.min_free_kbytes=16384]
vm.min_free_kbytes = 16384
--------------------------------------------------------------------------------
INFO: [lsblk -i]
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 286.1M 1 loop 
`-veracrypt1 253:0 0 285.9M 0 dm /opt/rcontrol
mmcblk0 179:0 0 14.9G 0 disk 
|-mmcblk0p1 179:1 0 3.9G 0 part /
|-mmcblk0p2 179:2 0 600M 0 part /boot
|-mmcblk0p3 179:3 0 100M 0 part /mnt/setpoints
`-mmcblk0p4 179:4 0 1000M 0 part /mnt/debug
--------------------------------------------------------------------------------
INFO: copying [/dev/mmcblk0] -> [/dev/mmcblk1]
--------------------------------------------------------------------------------
INFO: [source=/dev/mmcblk0] is a valid block device
**ERROR: [destination=/dev/mmcblk1] does not exist**
--------------------------------------------------------------------------------
Example: /etc/default/beagle-flasher
--------------------------------------------------------------------------------
source=/dev/mmcblk0
destination=/dev/mmcblk1
rfs_partition=single
rfs_rootfs_type=ext4
rfs_rootfs_startmb=4
bootloader=/opt/u-boot/bb-u-boot-am335x-evm/install-mmcblk1.sh
flash_back=beaglebone-black-emmc-to-microsd
--------------------------------------------------------------------------------

```

Please suggest further steps.

Thanks

---

<div class="post-metadata">

**Author:** ![RobertCNelson](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/robertcnelson/32/12_2.png) [@RobertCNelson](https://forum.digikey.com/u/RobertCNelson)\
**Post date:** [October 16, 2024, 5:29pm UTC](https://forum.digikey.com/t/bbg-stopped-reponding/44841/15 "2024-10-16T17:29:17Z")

</div>

> [@chougulemrudula](#):
>
> ```auto
> INFO: [source=/dev/mmcblk0] is a valid block device
> **ERROR: [destination=/dev/mmcblk1] does not exist**
> 
> ```

You second storage device doesn’t exist…

What does: `sudo beagle-version` show?

Regards,

---

<div class="post-metadata">

**Author:** ![RobertCNelson](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/robertcnelson/32/12_2.png) [@RobertCNelson](https://forum.digikey.com/u/RobertCNelson)\
**Post date:** [October 16, 2024, 5:32pm UTC](https://forum.digikey.com/t/bbg-stopped-reponding/44841/16 "2024-10-16T17:32:52Z")

</div>

> [@chougulemrudula](#):
>
> ```auto
> INFO: [lsblk -i]
> NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
> loop0 7:0 0 286.1M 1 loop 
> `-veracrypt1 253:0 0 285.9M 0 dm /opt/rcontrol
> mmcblk0 179:0 0 14.9G 0 disk 
> |-mmcblk0p1 179:1 0 3.9G 0 part /
> |-mmcblk0p2 179:2 0 600M 0 part /boot
> |-mmcblk0p3 179:3 0 100M 0 part /mnt/setpoints
> `-mmcblk0p4 179:4 0 1000M 0 part /mnt/debug
> 
> ```

Side note… This complex partition layout structure will not be re-created with the flashing script…

Regards,

---

<div class="post-metadata">

**Author:** ![chougulemrudula](https://avatars.discourse-cdn.com/v4/letter/c/a698b9/32.png) [@chougulemrudula](https://forum.digikey.com/u/chougulemrudula)\
**Post date:** [October 16, 2024, 5:34pm UTC](https://forum.digikey.com/t/bbg-stopped-reponding/44841/17 "2024-10-16T17:34:05Z")

</div>

> [@RobertCNelson](#):
>
> `udo beagle-version`

I am unable to find this command on my sd card

---

<div class="post-metadata">

**Author:** ![chougulemrudula](https://avatars.discourse-cdn.com/v4/letter/c/a698b9/32.png) [@chougulemrudula](https://forum.digikey.com/u/chougulemrudula)\
**Post date:** [October 16, 2024, 5:35pm UTC](https://forum.digikey.com/t/bbg-stopped-reponding/44841/18 "2024-10-16T17:35:10Z")

</div>

can we copy only  
-mmcblk0p1 179:1 0 3.9G 0 part /  
along with uboot to eMMC?

If I delete the last three partitions would it be helpful?

---

<div class="post-metadata">

**Author:** ![RobertCNelson](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/robertcnelson/32/12_2.png) [@RobertCNelson](https://forum.digikey.com/u/RobertCNelson)\
**Post date:** [October 16, 2024, 5:39pm UTC](https://forum.digikey.com/t/bbg-stopped-reponding/44841/19 "2024-10-16T17:39:02Z")

</div>

The `beagle-version` script is provided by: `bb-beagle-version`

```auto
sudo apt-get update
sudo apt-get install bb-beagle-version

```

You can delete them, they just won’t be copied, so don’t expect them in the targed end media.

Regards,

---

<div class="post-metadata">

**Author:** ![chougulemrudula](https://avatars.discourse-cdn.com/v4/letter/c/a698b9/32.png) [@chougulemrudula](https://forum.digikey.com/u/chougulemrudula)\
**Post date:** [October 16, 2024, 5:41pm UTC](https://forum.digikey.com/t/bbg-stopped-reponding/44841/20 "2024-10-16T17:41:40Z")

</div>

yup, make sense. I was unable locate the package. Thanks for the info.

Here is the required details:

sudo beagle-version  
eeprom:[A335BNLT00C02916BBBK21DB]  
model:[TI\_AM335x\_BeagleBone\_Black]  
bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot SPL 2021.10-00011-g6988a046 (Mar 08 2022 - 00:19:27 +0530)]:[location: dd MBR]  
UBOOT: Booted Device-Tree:[am335x-boneblack-uboot-univ.dts]  
UBOOT: Loaded Overlay:[BB-AAIM-LCD-00A1.bb.org-overlays]  
UBOOT: Loaded Overlay:[BB-I2C1-00A0]  
UBOOT: Loaded Overlay:[BB-UART1-00A0]  
UBOOT: Loaded Overlay:[BB-UART2-00A0]  
UBOOT: Loaded Overlay:[BB-UART4-00A0]  
kernel:[5.10.87-bone-rt-r59]  
nodejs:[v10.19.0]  
pkg check: to individually upgrade run: [sudo apt install --only-upgrade]  
WARNING:pkg:[bb-cape-overlays]:[NOT\_INSTALLED]  
WARNING:pkg:[bb-customizations]:[NOT\_INSTALLED]  
WARNING:pkg:[bb-usb-gadgets]:[NOT\_INSTALLED]  
WARNING:pkg:[bb-wl18xx-firmware]:[NOT\_INSTALLED]  
pkg:[kmod]:[27-1ubuntu2]  
WARNING:pkg:[librobotcontrol]:[NOT\_INSTALLED]  
cmdline:[console=ttyS0,115200n8 bone\_capemgr.uboot\_capemgr\_enabled=1 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent\_pool=1M quiet]  
dmesg | grep remote  
dmesg | grep pru  
dmesg | grep pinctrl-single  
[2.017526] pinctrl-single 44e10800.pinmux: 142 pins, size 568  
dmesg | grep gpio-of-helper  
[3.216154] gpio-of-helper ocp:cape-universal: Allocated GPIO id=0 name=‘P8\_03’  
[3.216391] gpio-of-helper ocp:cape-universal: Allocated GPIO id=1 name=‘P8\_04’  
[3.216587] gpio-of-helper ocp:cape-universal: Allocated GPIO id=2 name=‘P8\_05’  
[3.216793] gpio-of-helper ocp:cape-universal: Allocated GPIO id=3 name=‘P8\_06’  
[3.217217] gpio-of-helper ocp:cape-universal: Allocated GPIO id=4 name=‘P8\_07’  
[3.217470] gpio-of-helper ocp:cape-universal: Allocated GPIO id=5 name=‘P8\_08’  
[3.217683] gpio-of-helper ocp:cape-universal: Allocated GPIO id=6 name=‘P8\_09’  
[3.217895] gpio-of-helper ocp:cape-universal: Allocated GPIO id=7 name=‘P8\_10’  
[3.218103] gpio-of-helper ocp:cape-universal: Allocated GPIO id=8 name=‘P8\_11’  
[3.218303] gpio-of-helper ocp:cape-universal: Allocated GPIO id=9 name=‘P8\_12’  
[3.218351] gpio-of-helper ocp:cape-universal: Failed to get gpio property of ‘P8\_13’  
[3.218360] gpio-of-helper ocp:cape-universal: Failed to create gpio entry  
[3.495321] gpio-of-helper ocp:cape-universal: Allocated GPIO id=0 name=‘P8\_03’  
[3.495645] gpio-of-helper ocp:cape-universal: Allocated GPIO id=1 name=‘P8\_04’  
[3.495918] gpio-of-helper ocp:cape-universal: Allocated GPIO id=2 name=‘P8\_05’  
[3.496091] gpio-of-helper ocp:cape-universal: Allocated GPIO id=3 name=‘P8\_06’  
[3.496445] gpio-of-helper ocp:cape-universal: Allocated GPIO id=4 name=‘P8\_07’  
[3.496615] gpio-of-helper ocp:cape-universal: Allocated GPIO id=5 name=‘P8\_08’  
[3.496761] gpio-of-helper ocp:cape-universal: Allocated GPIO id=6 name=‘P8\_09’  
[3.496915] gpio-of-helper ocp:cape-universal: Allocated GPIO id=7 name=‘P8\_10’  
[3.497061] gpio-of-helper ocp:cape-universal: Allocated GPIO id=8 name=‘P8\_11’  
[3.497221] gpio-of-helper ocp:cape-universal: Allocated GPIO id=9 name=‘P8\_12’  
[3.497469] gpio-of-helper ocp:cape-universal: Allocated GPIO id=10 name=‘P8\_13’  
[3.497683] gpio-of-helper ocp:cape-universal: Allocated GPIO id=11 name=‘P8\_14’  
[3.497883] gpio-of-helper ocp:cape-universal: Allocated GPIO id=12 name=‘P8\_15’  
[3.498090] gpio-of-helper ocp:cape-universal: Allocated GPIO id=13 name=‘P8\_16’  
[3.498311] gpio-of-helper ocp:cape-universal: Allocated GPIO id=14 name=‘P8\_17’  
[3.498534] gpio-of-helper ocp:cape-universal: Allocated GPIO id=15 name=‘P8\_18’  
[3.498741] gpio-of-helper ocp:cape-universal: Allocated GPIO id=16 name=‘P8\_19’  
[3.499200] gpio-of-helper ocp:cape-universal: Allocated GPIO id=17 name=‘P8\_20’  
[3.499453] gpio-of-helper ocp:cape-universal: Allocated GPIO id=18 name=‘P8\_21’  
[3.499665] gpio-of-helper ocp:cape-universal: Allocated GPIO id=19 name=‘P8\_22’  
[3.499859] gpio-of-helper ocp:cape-universal: Allocated GPIO id=20 name=‘P8\_23’  
[3.500065] gpio-of-helper ocp:cape-universal: Allocated GPIO id=21 name=‘P8\_24’  
[3.500257] gpio-of-helper ocp:cape-universal: Allocated GPIO id=22 name=‘P8\_25’  
[3.500471] gpio-of-helper ocp:cape-universal: Allocated GPIO id=23 name=‘P8\_26’  
[3.500696] gpio-of-helper ocp:cape-universal: Allocated GPIO id=24 name=‘P8\_27’  
[3.500889] gpio-of-helper ocp:cape-universal: Allocated GPIO id=25 name=‘P8\_28’  
[3.501092] gpio-of-helper ocp:cape-universal: Allocated GPIO id=26 name=‘P8\_29’  
[3.501291] gpio-of-helper ocp:cape-universal: Allocated GPIO id=27 name=‘P8\_30’  
[3.501494] gpio-of-helper ocp:cape-universal: Allocated GPIO id=28 name=‘P8\_31’  
[3.501699] gpio-of-helper ocp:cape-universal: Allocated GPIO id=29 name=‘P8\_32’  
[3.501903] gpio-of-helper ocp:cape-universal: Allocated GPIO id=30 name=‘P8\_33’  
[3.502115] gpio-of-helper ocp:cape-universal: Allocated GPIO id=31 name=‘P8\_34’  
[3.502320] gpio-of-helper ocp:cape-universal: Allocated GPIO id=32 name=‘P8\_35’  
[3.502528] gpio-of-helper ocp:cape-universal: Allocated GPIO id=33 name=‘P8\_36’  
[3.502734] gpio-of-helper ocp:cape-universal: Allocated GPIO id=34 name=‘P8\_37’  
[3.503205] gpio-of-helper ocp:cape-universal: Allocated GPIO id=35 name=‘P8\_38’  
[3.503428] gpio-of-helper ocp:cape-universal: Allocated GPIO id=36 name=‘P8\_39’  
[3.503639] gpio-of-helper ocp:cape-universal: Allocated GPIO id=37 name=‘P8\_40’  
[3.503836] gpio-of-helper ocp:cape-universal: Allocated GPIO id=38 name=‘P8\_41’  
[3.504047] gpio-of-helper ocp:cape-universal: Allocated GPIO id=39 name=‘P8\_42’  
[3.504243] gpio-of-helper ocp:cape-universal: Allocated GPIO id=40 name=‘P8\_43’  
[3.504467] gpio-of-helper ocp:cape-universal: Allocated GPIO id=41 name=‘P8\_44’  
[3.504682] gpio-of-helper ocp:cape-universal: Allocated GPIO id=42 name=‘P8\_45’  
[3.504875] gpio-of-helper ocp:cape-universal: Allocated GPIO id=43 name=‘P8\_46’  
[3.505092] gpio-of-helper ocp:cape-universal: Allocated GPIO id=44 name=‘P9\_11’  
[3.505297] gpio-of-helper ocp:cape-universal: Allocated GPIO id=45 name=‘P9\_12’  
[3.505504] gpio-of-helper ocp:cape-universal: Allocated GPIO id=46 name=‘P9\_13’  
[3.505732] gpio-of-helper ocp:cape-universal: Allocated GPIO id=47 name=‘P9\_14’  
[3.505926] gpio-of-helper ocp:cape-universal: Allocated GPIO id=48 name=‘P9\_15’  
[3.506131] gpio-of-helper ocp:cape-universal: Allocated GPIO id=49 name=‘P9\_16’  
[3.506332] gpio-of-helper ocp:cape-universal: Allocated GPIO id=50 name=‘P9\_17’  
[3.506568] gpio-of-helper ocp:cape-universal: Allocated GPIO id=51 name=‘P9\_18’  
[3.506772] gpio-of-helper ocp:cape-universal: Allocated GPIO id=52 name=‘P9\_19’  
[3.507243] gpio-of-helper ocp:cape-universal: Allocated GPIO id=53 name=‘P9\_20’  
[3.507470] gpio-of-helper ocp:cape-universal: Allocated GPIO id=54 name=‘P9\_21’  
[3.507698] gpio-of-helper ocp:cape-universal: Allocated GPIO id=55 name=‘P9\_22’  
[3.507898] gpio-of-helper ocp:cape-universal: Allocated GPIO id=56 name=‘P9\_23’  
[3.508105] gpio-of-helper ocp:cape-universal: Allocated GPIO id=57 name=‘P9\_24’  
[3.508711] gpio-of-helper ocp:cape-universal: Allocated GPIO id=58 name=‘P9\_25’  
[3.509147] gpio-of-helper ocp:cape-universal: Allocated GPIO id=59 name=‘P9\_26’  
[3.509524] gpio-of-helper ocp:cape-universal: Allocated GPIO id=60 name=‘P9\_27’  
[3.509850] gpio-of-helper ocp:cape-universal: Allocated GPIO id=61 name=‘P9\_28’  
[3.510074] gpio-of-helper ocp:cape-universal: Allocated GPIO id=62 name=‘P9\_29’  
[3.510404] gpio-of-helper ocp:cape-universal: Allocated GPIO id=63 name=‘P9\_30’  
[3.510714] gpio-of-helper ocp:cape-universal: Allocated GPIO id=64 name=‘P9\_31’  
[3.511083] gpio-of-helper ocp:cape-universal: Allocated GPIO id=65 name=‘P9\_41’  
[3.511472] gpio-of-helper ocp:cape-universal: Allocated GPIO id=66 name=‘P9\_91’  
[3.511779] gpio-of-helper ocp:cape-universal: Allocated GPIO id=67 name=‘P9\_42’  
[3.512109] gpio-of-helper ocp:cape-universal: Allocated GPIO id=68 name=‘P9\_92’  
[3.512122] gpio-of-helper ocp:cape-universal: ready  
dmesg | grep wlcore  
lsusb  
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub  
END

[Next page](https://forum.digikey.com/t/bbg-stopped-reponding/44841.md?page=2)
