android+mmcblk1,mmcblk1: error -84 transferring data

最新推荐文章于 2023-05-05 09:51:56 发布
最新推荐文章于 2023-05-05 09:51:56 发布
阅读量1.2k 收藏
点赞数
文章标签： android+mmcblk1

/ # hdparm -tT /dev/mmcblk0

/dev/mmcblk0:

mmcblk0: error -84 transferring data, sector 0, nr 512, cmd response 0x900, card status 0xb00

mmcblk0: retrying using single block read

Timing buffer-cache reads:   328 MB in 0.51 seconds = 654735 kB/s

Timing buffered disk reads:mmcblk0: error -84 transferring data, sector 16384, nr 512, cmd response 0x900, card status 0xb00

mmcblk0: retrying using single block read

mmcblk0: error -84 transferring data, sector 16457, nr 439, cmd response 0x900, card status 0x0

end_request: I/O error, dev mmcblk0, sector 16457

mmcblk0: error -84 transferring data, sector 16458, nr 438, cmd response 0x900, card status 0x0

end_request: I/O error, dev mmcblk0, sector 16458

Buffer I/O error on device mmcblk0, logical block 2057

mmcblk0: error -84 transferring data, sector 16477, nr 419, cmd response 0x900, card status 0x0

end_request: I/O error, dev mmcblk0, sector 16477

Buffer I/O error on device mmcblk0, logical block 2059

mmcblk0: error -84 transferring data, sector 16480, nr 416, cmd response 0x900, card status 0x0

end_request: I/O error, dev mmcblk0, sector 16480

mmc0: Got data interrupt 0x00000002 even though no data operation was in progress.

mmcblk0: error -84 transferring data, sector 16485, nr 411, cmd response 0x900, card status 0x0

end_request: I/O error, dev mmcblk0, sector 16485

mmcblk0: error -84 transferring data, sector 16486, nr 410, cmd response 0x900, card status 0x0

end_request: I/O error, dev mmcblk0, sector 16486

Buffer I/O error on device mmcblk0, logical block 2060

mmcblk0: error -84 transferring data, sector 16502, nr 394, cmd response 0x900, card status 0x0

end_request: I/O error, dev mmcblk0, sector 16502

Buffer I/O error on device mmcblk0, logical block 2062

mmcblk0: error -84 transferring data, sector 16505, nr 391, cmd response 0x900, card status 0x0

end_request: I/O error, dev mmcblk0, sector 16505

Buffer I/O error on device mmcblk0, logical block 2063

mmcblk0: error -84 transferring data, sector 16695, nr 201, cmd response 0x900, card status 0x0

end_request: I/O error, dev mmcblk0, sector 16695

Buffer I/O error on device mmcblk0, logical block 2086

mmcblk0: error -84 transferring data, sector 16715, nr 181, cmd response 0x900, card status 0x0

end_request: I/O error, dev mmcblk0, sector 16715

Buffer I/O error on device mmcblk0, logical block 2089

mmcblk0: error -84 transferring data, sector 16748, nr 148, cmd response 0x900, card status 0x0

end_request: I/O error, dev mmcblk0, sector 16748

Buffer I/O error on device mmcblk0, logical block 2093

mmc0: Got data interrupt 0x00000002 even though no data operation was in progress.

mmcblk0: error -84 transferring data, sector 16758, nr 138, cmd response 0x900, card status 0x0

end_request: I/O error, dev mmcblk0, sector 16758

Buffer I/O error on device mmcblk0, logical block 2094

mmcblk0: error -84 transferring data, sector 16789, nr 107, cmd response 0x900, card status 0x0

end_request: I/O error, dev mmcblk0, sector 16789

Buffer I/O error on device mmcblk0, logical block 2098

mmcblk0: error -84 transferring data, sector 16824, nr 72, cmd response 0x900, card status 0x0

end_request: I/O error, dev mmcblk0, sector 16824

mmcblk0: error -84 transferring data, sector 16827, nr 69, cmd response 0x900, card status 0x0

end_request: I/O error, dev mmcblk0, sector 16827

mmcblk0: error -84 transferring data, sector 16862, nr 34, cmd response 0x900, card status 0x0

end_request: I/O error, dev mmcblk0, sector 16862

mmcblk0: error -84 transferring data, sector 16883, nr 13, cmd response 0x900, card status 0x0

end_request: I/O error, dev mmcblk0, sector 16883

mmcblk0: error -84 transferring data, sector 16472, nr 8, cmd response 0x900, card status 0xb00

mmcblk0: retrying using single block read

mmcblk0: error -84 transferring data, sector 16496, nr 8, cmd response 0x900, card status 0xb00

mmcblk0: retrying using single block read

mmcblk0: error -84 transferring data, sector 16896, nr 256, cmd response 0x900, card status 0xb00

mmcblk0: retrying using single block read

mmcblk0: error -84 transferring data, sector 16913, nr 239, cmd response 0x900, card status 0x0

end_request: I/O error, dev mmcblk0, sector 16913

mmcblk0: error -84 transferring data, sector 16961, nr 191, cmd response 0x900, card status 0x0

end_request: I/O error, dev mmcblk0, sector 16961

mmcblk0: error -84 transferring data, sector 16970, nr 182, cmd response 0x900, card status 0x0

end_request: I/O error, dev mmcblk0, sector 16970

mmcblk0: error -84 transferring data, sector 16987, nr 165, cmd response 0x900, card status 0x0

end_request: I/O error, dev mmcblk0, sector 16987

mmcblk0: error -84 transferring data, sector 17013, nr 139, cmd response 0x900, card status 0x0

end_request: I/O error, dev mmcblk0, sector 17013

mmcblk0: error -84 transferring data, sector 17052, nr 100, cmd response 0x900, card status 0x0

end_request: I/O error, dev mmcblk0, sector 17052

mmcblk0: error -84 transferring data, sector 17065, nr 87, cmd response 0x900, card status 0x0

end_request: I/O error, dev mmcblk0, sector 17065

mmcblk0: error -84 transferring data, sector 17073, nr 79, cmd response 0x900, card status 0x0

end_request: I/O error, dev mmcblk0, sector 17073

mmcblk0: error -84 transferring data, sector 17088, nr 64, cmd response 0x900, card status 0x0

end_request: I/O error, dev mmcblk0, sector 17088

mmcblk0: error -84 transferring data, sector 16712, nr 8, cmd response 0x900, card status 0xb00

mmcblk0: retrying using single block read

mmcblk0: error -84 transferring data, sector 16784, nr 8, cmd response 0x900, card status 0xb00

mmcblk0: retrying using single block read

mmc0: Got data interrupt 0x00000002 even though no data operation was in progress.

mmcblk0: error -84 transferring data, sector 16787, nr 5, cmd response 0x900, card status 0x0

end_request: I/O error, dev mmcblk0, sector 16787

mmcblk0: error -84 transferring data, sector 16791, nr 1, cmd response 0x900, card status 0x0

end_request: I/O error, dev mmcblk0, sector 16791

mmcblk0: error -84 transferring data, sector 16784, nr 8, cmd response 0x900, card status 0xb00

mmcblk0: retrying using single block read

mmcblk0: error -84 transferring data, sector 17152, nr 64, cmd response 0x900, card status 0xb00

mmcblk0: retrying using single block read

mmc0: Got data interrupt 0x00000002 even though no data operation was in progress.

mmcblk0: error -84 transferring data, sector 17174, nr 42, cmd response 0x900, card status 0x0

end_request: I/O error, dev mmcblk0, sector 17174

mmcblk0: error -84 transferring data, sector 17187, nr 29, cmd response 0x900, card status 0x0

end_request: I/O error, dev mmcblk0, sector 17187

mmcblk0: error -84 transferring data, sector 16960, nr 8, cmd response 0x900, card status 0xb00

mmcblk0: retrying using single block read

mmcblk0: error -84 transferring data, sector 16968, nr 8, cmd response 0x900, card status 0xb00

mmcblk0: retrying using single block read

mmcblk0: error -84 transferring data, sector 16968, nr 8, cmd response 0x900, card status 0x0

end_request: I/O error, dev mmcblk0, sector 16968

mmcblk0: error -84 transferring data, sector 16984, nr 8, cmd response 0x900, card status 0xb00

mmcblk0: retrying using single block read

mmcblk0: error -84 transferring data, sector 17064, nr 8, cmd response 0x900, card status 0xb00

mmcblk0: retrying using single block read

mmcblk0: error -84 transferring data, sector 17072, nr 8, cmd response 0x900, card status 0xb00

mmcblk0: retrying using single block read

mmcblk0: error -84 transferring data, sector 17168, nr 8, cmd response 0x900, card status 0xb00

mmcblk0: retrying using single block read

mmcblk0: error -84 transferring data, sector 17216, nr 16, cmd response 0x900, card status 0xb00

mmcblk0: retrying using single block read

mmcblk0: error -84 transferring data, sector 17232, nr 32, cmd response 0x900, card status 0xb00

mmcblk0: retrying using single block read

mmcblk0: error -84 transferring data, sector 17264, nr 32, cmd response 0x900, card status 0xb00

mmcblk0: retrying using single block read

mmcblk0: error -84 transferring data, sector 17296, nr 32, cmd response 0x900, card status 0xb00

mmcblk0: retrying using single block read

mmcblk0: error -84 transferring data, sector 17328, nr 32, cmd response 0x900, card status 0xb00

mmcblk0: retrying using single block read

mmcblk0: error -84 transferring data, sector 17360, nr 32, cmd response 0x900, card status 0xb00

mmcblk0: retrying using single block read

mmcblk0: error -84 transferring data, sector 17392, nr 32, cmd response 0x900, card status 0xb00

mmcblk0: retrying using single block read

mmcblk0: error -84 transferring data, sector 17419, nr 5, cmd response 0x900, card status 0x0

end_request: I/O error, dev mmcblk0, sector 17419

mmcblk0: error -84 transferring data, sector 17416, nr 24, cmd response 0x900, card status 0xb00

mmcblk0: retrying using single block read

mmc0: Got data interrupt 0x00000002 even though no data operation was in progress.

mmcblk0: error -84 transferring data, sector 17421, nr 19, cmd response 0x900, card status 0x0

end_request: I/O error, dev mmcblk0, sector 17421

mmcblk0: error -84 transferring data, sector 17440, nr 8, cmd response 0x900, card status 0xb00

mmcblk0: retrying using single block read

mmcblk0: error -84 transferring data, sector 17456, nr 8, cmd response 0x900, card status 0xb00

mmcblk0: retrying using single block read

mmcblk0: error -84 transferring data, sector 17461, nr 3, cmd response 0x900, card status 0x0

end_request: I/O error, dev mmcblk0, sector 17461

mmcblk0: error -84 transferring data, sector 17456, nr 8, cmd response 0x900, card status 0xb00

mmcblk0: retrying using single block read

mmcblk0: error -84 transferring data, sector 17460, nr 4, cmd response 0x900, card status 0x0

end_request: I/O error, dev mmcblk0, sector 17460

hdparm: short read

无可就是九头鸟
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
EMMC的U盘镜像Jetson-Boot-USB.tar.gz
03-10
烧录EMMC引导文件 解压命令： tar xzvf Jetson_Boot_USB.tar.gz 切换到这个目录： cd Jetson_Boot_USB/ 烧录引导文件 sudo ./flash.sh -r jetson-nano-devkit-emmc mmcblk0p1
IMX6Q平台Linux3.14.28出现SD卡-84transferring data错误解决办法
无语僧
03-02 5490
[  322.898452] mmc0: new high speed SDHC card at address 1234[  322.905036] mmcblk0: mmc0:1234 SA16G 14.6 GiB [  322.912228] mmcblk0: error -84 transferring data, sector 0, nr 8, cmd response 0x900, c...
mmcblk0：error -84的解决办法
热门推荐
jasonwang的专栏
10-13 1万+
今天在样机的SD卡上进行读写的时候，内核报错： mmcblk:0 error -84 transferring data, sector 8057, nr 1, cmd response 0x900, card status 0x0 sblk_update_request: I/O error, dev mmcblk0, sector 8057 Buffer I/O erron on dev ...
BPI-Mainline-bsp:支持BananaPi BPI -M1 M1Plus M2 M3
05-11
BPI-主线-bsp 建造 选择一个板，Bananapi_M1，Bananapi_M1_Plus，Bananapi_M2或Bananapi_R1。 $ ./configure Bananapi_M1 编译 $ make 开机 使用32MB FAT32引导分区（从1MB开始）对sdcard进行分区，其余部分使用ext4格式的rootfs分区进行分区。 您可以根据需要更改引导分区的大小。 在启动分区上创建文件boot.cmd。 -------------------------------------------------------- `setenv bootargs console=ttyS0,115200 root=/dev/mmcblk0p2 rootwait panic=10` `load mmc 0:1 0x43000000 bananapi/${fdtfile}` `
BOOT0和BOOT1
12-05
BOOT0和BOOT1。STM32三种启动模式对应的存储介质均是芯片内置的
Android工程之SD卡问题
Tree_in_sea的博客
01-11 1761
/*****************************************************************************  * Author : Elvins Fu    [email protected]  *  * Info : xxx Inc,(C) 2018-01-11, All rights revseved.  *  * Descri
RK3288 android 7.1 EMMC 问题导致卡死在开机logo 界面
qq_35003588的博客
03-27 4761
1、在调试 rk3288 android 7.1 遇到部分机器不能开机的问题 logo 如下： init: Waiting for /dev/.coldboot_done... [ 3.024810] init: Waiting for /dev/.coldboot_done took 0.00s. [ 3.024848] init: /dev/hw_random not found...
MT7620A SD卡初始化失败
Win_cao专栏
01-22 3509
插着TF卡开机，系统启动时TF卡初始化失败。 [ 6.880000] MTK MSDC device init. [ 6.930000] mtk-sd: MediaTek MT6575 MSDC Driver [ 6.940000] sdhci-pltfm: SDHCI platform and OF driver helper [ 6.950000] usbcore: ...
rk3399启动卡在android动画,Android6.0 RK3399 更换64GeMMC后无法启动的问题 · Younix’s Studio...
weixin_39802814的博客
05-26 979
[ 2.002835] dwmmc_rockchip fe310000.dwmmc: IDMAC supports 32-bit address mode.[ 2.002992] dwmmc_rockchip fe310000.dwmmc: Using internal DMA controller.[ 2.003029] dwmmc_rockchip fe310000.dwmm...
putty mmcblk0p2_ssh.7z kindle 修砖工具
01-08
Kindle 修砖教程汇总 (内有多篇教程) http://bbs.duokan.com/forum/thread-64038-1-1.html 深入了解之： 《修砖的原理》 Kindle是一个Linux设备， 支持网络连接。原理上和一台linux电脑一样。 Kindle的MMC Flash有4个分区： main, diags, var, usb。 在图形界面上，用usb导出u盘，只能见到第4个分区。 机器变砖，一般是main或者var文件错误，可以刷镜像恢复。 我们采用fastboot模式修砖。原理是，让Kindle进入刷机模式， 这时候kindle屏幕上是不变化的，也不导出USB磁盘。 kindle这时候是一个fastboot设备，我们在PC上用fastboot.exe给kindle刷机。 Kindle有三种启动模式： fastboot 刷机模式（屏幕无反应）； diags 诊断模式（屏幕文字菜单）； main 正常模式（图形界面，可看书）。 以KT为例： 刷机的全过程，就是一个状态变化的过程： magic key （按住kindle操作） ->HID-Compliant（PC下 mfgTool 操作） -> fastboot （PC下命令行操作） -> diags （文字菜单） -> main （Kindle图形界面） 修砖就是刷镜像。 版本刷匹配了就OK。 下面总结了一些命令行。刷 main kernel的命令行见 第（3）。 具体步骤见 修砖教程汇总里的 KT小白修砖贴。 fastboot.exe的命令格式为： fastboot.exe flash [目标分区] [镜像文件名] 意思就是把 文件 刷入到 目标分区， flash即是刷入。 目标分区有 diags（调试分区）, diags_kernel （调试分区kernel）, kernel （主分区kernel）等。 在fastboot模式下刷机 (1)刷 diags分区 镜像： fastboot.exe flash diags mmcblk0p2_ssh-kt500.img (2)刷 diags分区 kernel， 也就是 diags_kernel : fastboot.exe flash diags_kernel kt_5.0.0_diags_kernel.img (3) 刷主分区 main_kernel， 也就是kernel： fastboot.exe flash kernel kernel_5.0.0.img (4) 设置启动模式为diags fastboot.exe setvar bootmode diags (5)重启Kindle fastboot.exe reboot 重启进入diags模式，然后用dd命令行，恢复主分区 在诊断模式，文字菜单， 依次选择N)、U)、Z)、X)， 打开USB NetWork, 开启SSH。这时候，Kindle和PC之间的连接，模拟为RNDIS网卡，可以从网络登录Kindle，从而用dd命令行，恢复主分区。 （第一次运行需要在Windows下安装RNDIS网卡驱动， Win7/Win7 x64微软自带驱动） (6)在SSH下（用putty登录）， 刷主分区镜像 dd if=/mnt/us/mmcblk0p1.img of=/dev/mmcblk0p1 这里的if 是input file， of是outputfile。 of是固定的分区名，/dev/mmcblk0p1是主分区。 (7)在SSH下（用putty登录）， 清空第三个分区 umount /dev/mmcblk0p3 dd if=/dev/zero of=/dev/mmcblk0p3 (8)重启到正常模式 idme -d --bootmode main reboot -f
VFS_Cannot_open_root_device_mtdblock2_or_unknown-block(2_0)
01-07
linux yaffs配置问题解决办法，曾采用
cx_Oracle.DatabaseError: Error while trying to retrieve text for error ORA-01804段错误 (核心已转储)
程序猿的博客
05-05 793
如何解决：（环境变量的问题）
Datax使用踩坑经历
weixin_43876924的博客
03-22 2086
【代码】Datax使用踩坑经历。
dolphinscheduler调度datax脚本执行错误原因（我见）
Linmeng001的博客
10-13 1673
dolphin调度datax，io问题
SDIO出错 error -84 sending status command, retrying end_request: I/O error, dev mmcblk0, sector
Colorful_lights的博客
03-23 7765
在调试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, re
linux mmc 读写,这个mmc读取linux的原因是什么
weixin_39642998的博客
05-14 465
linux中这个mmc读取问题的原因是什么？请帮忙解决这个问题？请检查下面的内核启动日志帮我解决这个问题..我已经启用了mmc编译的相关驱动程序并使用新创建的内核映像启动了我正在获取内核启动loogs,如下所示mmc0: card lacks mandatory switch function,performance might suffer.mmc0: host does not support...
sd卡休眠不掉电 linux cmd7,已解决: sd卡挂载问题 - Community Forums
weixin_35725147的博客
05-16 1564
我通过sd卡启动linux系统，系统可以正常启动，但是在/dev下只能看到mmcblk0，没有mmcblk0p1分区，无法挂载。而且在系统启动的时候报了如下错误：[ 1. 906221] mmcblk0: error -84 transferring data, sector 0, nr 8, cmd response 0x900,card status 0xb00[ 1. 906223] mmc...
UPS、蓄电池、空开、电缆配置计算方法.pptx
最新发布
04-27
5G通信行业、网络优化、通信工程建设资料
mmcblk1: error -84 transferring data, sector 0, nr 8, cmd.opcode 0x12, cmd.resp 0x900, card status 0x0
07-13
这个错误是与mmcblk1设备上的数据传输有关的。error -84表示数据传输失败，可能是由于设备故障、传输线路问题或者其他硬件故障引起的。sector 0指的是传输数据的扇区号，nr 8表示传输数据的数量，cmd.opcode 0x12表示传输命令的操作码，cmd.resp 0x900表示命令的响应码，card status 0x0表示卡片状态正常。要解决这个问题，你可以尝试以下几个步骤： 1. 检查设备连接：确保设备与主机之间的连接良好，没有松动或损坏的接头。 2. 检查数据线路：排除数据线路故障，可以尝试更换数据线或连接到其他可靠设备进行测试。 3. 检查设备状态：检查设备本身是否正常工作，可以尝试将其连接到其他主机或使用其他存储卡进行测试。 4. 检查驱动程序和固件：确保你使用的驱动程序和固件是最新版本，如果不是，尝试更新它们。 如果以上步骤都不能解决问题，可能需要考虑更换设备或联系厂家进行进一步的技术支持。

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值