2742 2012-07-12 06:36:31 +0000 ioatdma error happened on jasperforest platform with edison branch 2012-07-12 14:48:56 +0000 1 1 6 Yocto Project Subprojects Kernel kernel-configuration unspecified JasperForest Multiple RESOLVED WONTFIX Undecided normal 1.1.2 1 yilongx.y.sun bruce.ashfield hongnax.xu jessica.zhang yp.kernel.watcher yp.watcher --- --- --- oldest_to_newest 23022 0 yilongx.y.sun 2012-07-12 06:36:31 +0000 with 1.1.2 edison branch，when i run command "dmesg | grep -i error" to test dmesg, it shows ioatdma errors detailed error message as follows： ######################################################################## #dmesg | grep -i error ioatdma 0000:00:0a.0: channel error register unreachable ioatdma 0000:00:0a.0: channel enumeration error ioatdma 0000:00:0a.1: channel error register unreachable ioatdma 0000:00:0a.1: channel enumeration error ioatdma 0000:00:0a.2: channel error register unreachable ioatdma 0000:00:0a.2: channel enumeration error ioatdma 0000:00:0a.3: channel error register unreachable ioatdma 0000:00:0a.3: channel enumeration error ioatdma 0000:00:0a.4: channel error register unreachable ioatdma 0000:00:0a.4: channel enumeration error ioatdma 0000:00:0a.5: channel error register unreachable ioatdma 0000:00:0a.5: channel enumeration error ioatdma 0000:00:0a.6: channel error register unreachable ioatdma 0000:00:0a.6: channel enumeration error ioatdma 0000:00:0a.7: channel error register unreachable ioatdma 0000:00:0a.7: channel enumeration error ######################################################################## 23025 1 yilongx.y.sun 2012-07-12 06:49:59 +0000 detailed test information： Image location： http://autobuilder03.jf.intel.com/pub/nightly-meta-intel/20120705-4/machines/jasperforest/core-image-sato-sdk-jasperforest-20120705233116.hddimg The commit information as below: Poky/Edison: 8886aee5b9741c05886994967d9ecf420331c600 Meta-intel/Edison: f3040cf1559e631a03f61bab2de99d485bce21df 23055 2 jessica.zhang 2012-07-12 14:48:56 +0000 Since it's a cosmetic error message and given the stage of 1.1.2 we just won't fix it for 1.1.2 and it's fixed in later releases.