在调试emmc的时候遇到一个问题，挂载emmc出现如下错误：

~ # mount /dev/mmcblk0 /mnt/

end_request: I/O error, dev mmcblk0, sector 2
EXT4-fs (mmcblk0): unable to read superblock
mmcblk0: error -84 sending status command, retrying
mmcblk0: error -84 sending stop command, original cmd response 0x900, card status 0x900
mmcblk0: error -84 transferring data, sector 0, nr 8, cmd response 0x900, card status 0x100
mmcblk0: retrying using single block read
mmcblk0: error -84 sending status command, retrying
mmcblk0: error -84 sending status command, retrying
mmcblk0: response CRC error sending r/w cmd command, card status 0x900
mmcblk0: error -84 sending status command, retrying

mmcblk0: error -84 transferring data, sector 0, nr 2, cmd response 0x900, card status 0x0mmcblk0: retrying using single block read

虽然有错误，但是挂载应该是成功了。我在挂载前，在mnt目录下建了一个文件，挂载后文件没了，用df -h 查看磁盘的状态，也有报错。

/mnt/bin # df -h

Filesystem                Size      Used Available Use% Mounted on
/dev/root                32.0M     12.8M     19.2M  40% /
tmpfs                    13.1M      4.0K     13.1M   0% /dev
mmcblk0: response CRC error sending r/w cmd command, card status 0x900
mmcblk0: response CRC error sending r/w cmd command, card status 0x900
mmcblk0: error -84 sending status command, retrying
mmcblk0: response CRC error sending r/w cmd command, card status 0x900
mmcblk0: response CRC error sending r/w cmd command, card status 0x900
mmcblk0: response CRC error sending r/w cmd command, card status 0x900
mmcblk0: response CRC error sending r/w cmd command, card status 0x900
mmcblk0: response CRC error sending r/w cmd command, card status 0x900
mmcblk0: response CRC error sending r/w cmd command, card status 0x900
mmcblk0: response CRC error sending r/w cmd command, card status 0x900
mmcblk0: response CRC error sending r/w cmd command, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1798
end_request: I/O error, dev mmcblk0, sector 1799
end_request: I/O error, dev mmcblk0, sector 1800
end_request: I/O error, dev mmcblk0, sector 1801
end_request: I/O error, dev mmcblk0, sector 1802
end_request: I/O error, dev mmcblk0, sector 1803
end_request: I/O error, dev mmcblk0, sector 1804
end_request: I/O error, dev mmcblk0, sector 1805
end_request: I/O error, dev mmcblk0, sector 1806
end_request: I/O error, dev mmcblk0, sector 1807
end_request: I/O error, dev mmcblk0, sector 1808
end_request: I/O error, dev mmcblk0, sector 1809
end_request: I/O error, dev mmcblk0, sector 1810
end_request: I/O error, dev mmcblk0, sector 1811
end_request: I/O error, dev mmcblk0, sector 1812
end_request: I/O error, dev mmcblk0, sector 1813
end_request: I/O error, dev mmcblk0, sector 1814
end_request: I/O error, dev mmcblk0, sector 1815
end_request: I/O error, dev mmcblk0, sector 1816
end_request: I/O error, dev mmcblk0, sector 1817
end_request: I/O error, dev mmcblk0, sector 1818
end_request: I/O error, dev mmcblk0, sector 1819
end_request: I/O error, dev mmcblk0, sector 1820
end_request: I/O error, dev mmcblk0, sector 1821
end_request: I/O error, dev mmcblk0, sector 1822
end_request: I/O error, dev mmcblk0, sector 1823
end_request: I/O error, dev mmcblk0, sector 1824
end_request: I/O error, dev mmcblk0, sector 1825
end_request: I/O error, dev mmcblk0, sector 1826
end_request: I/O error, dev mmcblk0, sector 1827
end_request: I/O error, dev mmcblk0, sector 1828
end_request: I/O error, dev mmcblk0, sector 1829
end_request: I/O error, dev mmcblk0, sector 1830
end_request: I/O error, dev mmcblk0, sector 1831
end_request: I/O error, dev mmcblk0, sector 1832
end_request: I/O error, dev mmcblk0, sector 1833
end_request: I/O error, dev mmcblk0, sector 1834
end_request: I/O error, dev mmcblk0, sector 1835
end_request: I/O error, dev mmcblk0, sector 1836
end_request: I/O error, dev mmcblk0, sector 1837
end_request: I/O error, dev mmcblk0, sector 1838
end_request: I/O error, dev mmcblk0, sector 1839
end_request: I/O error, dev mmcblk0, sector 1840
end_request: I/O error, dev mmcblk0, sector 1841
end_request: I/O error, dev mmcblk0, sector 1842
end_request: I/O error, dev mmcblk0, sector 1843
end_request: I/O error, dev mmcblk0, sector 1844
end_request: I/O error, dev mmcblk0, sector 1845
end_request: I/O error, dev mmcblk0, sector 1846
end_request: I/O error, dev mmcblk0, sector 1847
end_request: I/O error, dev mmcblk0, sector 1848
end_request: I/O error, dev mmcblk0, sector 1849
end_request: I/O error, dev mmcblk0, sector 1850
end_request: I/O error, dev mmcblk0, sector 1851
end_request: I/O error, dev mmcblk0, sector 1852
end_request: I/O error, dev mmcblk0, sector 1853
end_request: I/O error, dev mmcblk0, sector 1854
end_request: I/O error, dev mmcblk0, sector 1855
end_request: I/O error, dev mmcblk0, sector 1856
end_request: I/O error, dev mmcblk0, sector 1857
end_request: I/O error, dev mmcblk0, sector 1858
end_request: I/O error, dev mmcblk0, sector 1859
end_request: I/O error, dev mmcblk0, sector 1860
end_request: I/O error, dev mmcblk0, sector 1861
end_request: I/O error, dev mmcblk0, sector 1862
end_request: I/O error, dev mmcblk0, sector 1863
end_request: I/O error, dev mmcblk0, sector 1864
end_request: I/O error, dev mmcblk0, sector 1865
end_request: I/O error, dev mmcblk0, sector 1866
end_request: I/O error, dev mmcblk0, sector 1867
end_request: I/O error, dev mmcblk0, sector 1868
end_request: I/O error, dev mmcblk0, sector 1869
end_request: I/O error, dev mmcblk0, sector 1870
end_request: I/O error, dev mmcblk0, sector 1871
end_request: I/O error, dev mmcblk0, sector 1872
end_request: I/O error, dev mmcblk0, sector 1873
end_request: I/O error, dev mmcblk0, sector 1874
end_request: I/O error, dev mmcblk0, sector 1875
end_request: I/O error, dev mmcblk0, sector 1876
end_request: I/O error, dev mmcblk0, sector 1877
end_request: I/O error, dev mmcblk0, sector 1878
end_request: I/O error, dev mmcblk0, sector 1879
end_request: I/O error, dev mmcblk0, sector 1880
end_request: I/O error, dev mmcblk0, sector 1881
end_request: I/O error, dev mmcblk0, sector 1882
end_request: I/O error, dev mmcblk0, sector 1883
end_request: I/O error, dev mmcblk0, sector 1884
end_request: I/O error, dev mmcblk0, sector 1885
end_request: I/O error, dev mmcblk0, sector 1886
end_request: I/O error, dev mmcblk0, sector 1887
end_request: I/O error, dev mmcblk0, sector 1888
end_request: I/O error, dev mmcblk0, sector 1889
end_request: I/O error, dev mmcblk0, sector 1890
end_request: I/O error, dev mmcblk0, sector 1891
end_request: I/O error, dev mmcblk0, sector 1892
end_request: I/O error, dev mmcblk0, sector 1893
end_request: I/O error, dev mmcblk0, sector 1894
end_request: I/O error, dev mmcblk0, sector 1895
end_request: I/O error, dev mmcblk0, sector 1896
end_request: I/O error, dev mmcblk0, sector 1897
end_request: I/O error, dev mmcblk0, sector 1898
end_request: I/O error, dev mmcblk0, sector 1899
end_request: I/O error, dev mmcblk0, sector 1900
end_request: I/O error, dev mmcblk0, sector 1901
end_request: I/O error, dev mmcblk0, sector 1902

end_request: I/O error, dev mmcblk0, sector 2051
end_request: I/O error, dev mmcblk0, sector 2052
end_request: I/O error, dev mmcblk0, sector 2053
mmcblk0: error -84 sending status command, retrying
mmcblk0: error -84 sending status command, retrying
mmcblk0: response CRC error sending r/w cmd command, card status 0x900
mmcblk0: error -84 sending status command, retrying
mmcblk0: response CRC error sending r/w cmd command, card status 0x900
mmcblk0: error -84 sending status command, retrying
mmcblk0: error -84 sending status command, retrying
mmcblk0: error -84 sending status command, aborting
end_request: I/O error, dev mmcblk0, sector 1995
FAT-fs (mmcblk0): FAT read failed (blocknr 1995)
df: /mnt: Input/output error

发现能够正常的读写，好像一切都是没问题。


最后找到了原因，板子的SDIO做了兼容，既能够使用emmc，又能够使用TF卡，虽然连到TF卡上的电阻拿掉了，相当于断路，但是sdio的clk频率很大，有100M，多连接的导线相当于一个天线，会产生干扰。

SDIO出错 error -84 sending status command, retrying end_request: I/O error, dev mmcblk0, sector相关推荐

  1. appium 报错：Original error:Could not proxy command to remote server. Original error:socket hang up解决办法

    WebDriverException: Message: An unknown server-side error occurred while processing the command. Ori ...

  2. 【appium报错】Original error:Could not proxy command to remote server. Original error:socket hang up

    博客链接1:系统自带的应用kill掉appium相关的进程 博客链接2:卸载并重装appium相关安装包 如果上面的方法仍不能解决问题 暴力解决:卸载设备上的appium-setting 等appiu ...

  3. appium 报错：Original error:Could not proxy command to remote server. Original error:socket hang up

    记录一下今天遇到的一个问题,上周还跑的好好的脚本,今天运行时appium一值报错 soket hang up  导致根本无法获取系统的toast,这样我就没办法断言用例是否通过了. 这个报错我基本折腾 ...

  4. 自动化测试 appium 会报错 Could not proxy command to remote server. Original error: Error: socket hang up

    问题描述: 最近使用vivo X21A进行APP自动化测试过程中,发现程序运行过程中突然中断,查看报错信息 Error: socket hang up.appium 自动化测试,运行平台 vivo X ...

  5. 使用vue-cli3创建项目的时候出错，ERROR command failed: npm install --loglevel error --registry

    重点:方法三 命令: vue create vue-hello 错误提示: ERROR command failed: npm install --loglevel error --registry ...

  6. appium Original error: Could not proxy command to the remote server. Original error: socket hang up

    appium inspector录制OPPO真机的app时,操作第三步或者第四步就出现报错: Call to 'tap' failed [performTouchAction([{"acti ...

  7. Error while executing topic command : replication factor: 3 larger than available brokers: 0

    刚才创建kafka的Topic时,突然弹出以下出错 翻译以下错误信息可以得到集群中可利用的kafka数量为0,但是需要的副本因子为3,既然可利用的kafka的数量为0是不是我没有开启kafka集群,j ...

  8. 解决VS2012 Express的There was a problem sending the command to the program问题

    问题现象 安装Visual Studio 2012 Express之后,双击打开web.config文件时经常出现"There was a problem sending the comma ...

  9. There was an error running 'go version' command: exec: go: executable file not found in %PATH

    go git 安装好(安装在D盘): 步骤一.点击"Git Bash",输入"go get github.com/astaxie/beego",等一会儿即可.安 ...

最新文章

  1. 小甲鱼python课件源代码_[Python基础] 小甲鱼零基础入门Python学习视频+全套源码课件 Python视频教程 96讲...
  2. Eclipse下Tomcat服务器配置和使用
  3. js 有关object 、array 等引用类型的赋值问题
  4. Spark Scalaa 几个常用的示例
  5. docker nginx tomcat mysql_使用docker部署nginx+tomcat架构(2)：访问mysql数据库
  6. Jenkins+maven+SVN构建java项目中遇到的问题及解决
  7. jar包里面文件修改
  8. 【Python游戏】Python各大游戏合集：超级玛丽、天天酷跑、我的世界、魔塔、雷霆战机 | 附带源码
  9. 华为路由器配置IPSec (手动配置)
  10. flutter web实现微信网页授权登录
  11. promise终止方案
  12. True Liars （POJ - 1417）带权并查集+dp路径
  13. 未能联接game center服务器,苹果game center无法连接服务器怎么办呢？
  14. 神威超级计算机配置,神威太湖轻型超级计算机配置和性能列表
  15. 2021贵州江口中学高考成绩查询,2020铜仁江口县中考分数线 江口县高中录取分数线 江口县中考成绩查询_中考_3773考试网...
  16. [置顶] 黑马程序员 -- 多线程
  17. unknown custom element: ＜router-link＞ - did you register the component correctly? For recursiv
  18. Android Studio：Caused by: java.lang.ClassNotFoundException: Didn‘t find class “...“on path: DexPath*
  19. 【转】Xamarin.Android 入门之：Xamarin+vs2015 环境搭建
  20. 使用swagger org.fasterxml.classmate ResolvedParameterizedMember找不到

热门文章

  1. 【国考报名】国家公务员考试报名照片证件照怎么制作
  2. TRIZ创新方法——剪裁
  3. 自动称重管理软件适应市场的瞬息变幻
  4. flash cs3快捷键大全
  5. 数据可视化 堆叠柱状图 矩形层级图
  6. 用c++编写简单的加减乘除
  7. 裸辞4个月，面试了34家公司，终于找到理想工作了
  8. 大学计算机基础毕业论文答案,计算机本科论文范文
  9. Arduino极速入门教程——两篇文章让你会用Arduino（下）
  10. react实现bilibili的侧边屏幕滚动导航