end_request: I/O error, dev mtdblock2, sector 0 Buffer I
2015-05-18 11:28
453 查看
内核移植时遇到这个错误:
end_request: I/O error, dev mtdblock2, sector 0 Buffer I/O error on device mtdblock2, logical block 0
![](https://img-blog.csdn.net/20150518112623465?watermark/2/text/aHR0cDovL2Jsb2cuY3Nkbi5uZXQvdWNhbjIz/font/5a6L5L2T/fontsize/400/fill/I0JBQkFCMA==/dissolve/70/gravity/Center)
原因分析:由于内核是通过uboot烧写到nandflash中,因此uboot产生的ecc校验码与内核的ecc校验码不同,所以需要关闭内核的ecc校验。
解决方法:
打开内核目录中的s3c2410.c文件在内核源码中的drivers/mtd/nand目录中
在s3c2410_nand_init_chip()函数中修改如下:
end_request: I/O error, dev mtdblock2, sector 0 Buffer I/O error on device mtdblock2, logical block 0
原因分析:由于内核是通过uboot烧写到nandflash中,因此uboot产生的ecc校验码与内核的ecc校验码不同,所以需要关闭内核的ecc校验。
解决方法:
打开内核目录中的s3c2410.c文件在内核源码中的drivers/mtd/nand目录中
在s3c2410_nand_init_chip()函数中修改如下:
相关文章推荐
- end_request: I/O error, dev mtdblock2, sector 0 Buffer I
- end_request: I/O error, dev mtdblock3, sector 0
- end_request: I/O error, dev mtdblock3, sector 0
- end_request: I/O error, dev mtdblock4, sector 0
- CentOS7中开机出现end_request:I/O error,dev fd0,sector 0的解决办法
- Buffer I/O error on device mmcblk0p3, logical block .../end_request: I/O error, dev mmcblk0, sector
- end_request: I/O error, dev mtdblock3, sector 0
- SDIO出错 error -84 sending status command, retrying end_request: I/O error, dev mmcblk0, sector
- end_request: I/O error, dev sdi, sector 硬盘 故障
- CentOS7.0开机报错end_request IO error dev fd0 sector 0
- RHEL7.0启动时end_request I/O error及piix4_smbus错误提示处理
- end_request: I/O error
- error -27257: Pending web_reg_save_param/reg_find/create_html_param[_ex] request(s) detected and reset at the end of iteration number 1
- u-boot无法保存环境变量的问题 error:end address not on sector boundary
- error: start and/or end address not on sector boundary解决
- u-boot无法保存环境变量的问题 error:end address not on sector boundary
- tomcat报错:Error parsing HTTP request header
- SharePoint Designer cannot open site error " the server could not complete your request"
- Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible. <class 'sqlalchemy.exc.OperationalError'> (HTTP 500) (Request-ID: req-6ac88345-ce5a
- The server encountered an internal error () that prevented it from fulfilling this request.