Bug 1188 - [japerforest] I/OAT DMA engine init failed
Summary: [japerforest] I/OAT DMA engine init failed
Status: RESOLVED FIXED
Alias: None
Product: BSPs
Classification: Build System, Metadata & Runtime
Component: bsps-configuration (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Low minor
Target Milestone: 1.2
Assignee: Darren Hart
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2011-06-22 01:54 UTC by wenhua.fan
Modified: 2011-12-16 00:24 UTC (History)
7 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---


Attachments
detailed message (5.16 KB, text/plain)
2011-06-22 01:54 UTC, wenhua.fan
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description wenhua.fan 2011-06-22 01:54:29 UTC
Created attachment 176 [details]
detailed message

There is no such error in Yocto 1.1 M1 testing.

Commit Information:

Tree/Branch: Poky/Master
Poky Commit: 2163461ec94528ecf046a04edc5db3d2dd3a6b8b
Meta Branch: Master
Meta Commit: 76d1178ba1a43cf6457c89717134aeb9f1275fae

Commit Information:

Tree/Branch: Poky/Master
Poky Commit: 2163461ec94528ecf046a04edc5db3d2dd3a6b8b
Meta Branch: Master
Meta Commit: 76d1178ba1a43cf6457c89717134aeb9f1275fae

The error log is as below:

##########
ioatdma: Intel(R) QuickData Technology Driver 4.00
ioatdma 0000:00:0a.0: PCI INT A -> GSI 44 (level, low) -> IRQ 44
ioatdma 0000:00:0a.0: setting latency timer to 64
ioatdma 0000:00:0a.0: channel error register unreachable
ioatdma 0000:00:0a.0: channel enumeration error
ioatdma 0000:00:0a.0: Intel(R) I/OAT DMA Engine init failed
ioatdma 0000:00:0a.0: PCI INT A disabled
.....
##########

The attachment is about this bug's detailed message.
Comment 1 wenhua.fan 2011-06-22 02:05:22 UTC
Sorry, description about commit information appeared two times.

Image location:

http://autobuilder02.pokylinux.org/jasperforest-master/nightly/20110617-1/machines/jasperforest/x86_32/core-image-lsb-sdk-live-jasperforest-20110618060754.hddimg.bz2
Comment 2 Darren Hart 2011-06-23 15:13:43 UTC
Are there any runtime issues or is this simply a new message to the console? I presume this log is from dmesg?
Comment 3 Jiajun Xu 2011-06-23 17:24:48 UTC
The error message is from dmesg. There is no run-time function broken when we test japerforest.
Comment 4 wenhua.fan 2011-08-26 02:11:30 UTC
This issue still exist in Yocto1.1 20110824 build.

Commit information:

Tree/Branch: Poky/Master
Poky Commit id: 6c2b7beac3cd23ed44bd3e195c6360a0932876bf
Meta Branch: Master
Meta commit id: fb15cc4e1c4be75c81acaf6a1dd33675a9142975

Image location:
http://autobuilder02.yoctoproject.org/jasperforest-master/nightly/20110825-2/machines/jasperforest/x86_32/core-image-sato-sdk-jasperforest-20110825232723.hddimg.bz2
Comment 5 Darren Hart 2011-09-06 09:11:11 UTC
Moving to post 1.1 given no detected runtime failure.
Comment 6 yilong, sun 2011-12-13 22:28:01 UTC
There is no such error in Yocto 1.2 M1 testing.

Commit Information:
Tree/Branch: Poky/1.2_M1
Poky Commit: d22daf5c067c57ab1e253b789486aba36e727ed0
Meta Branch: master branch
Meta Commit: 3d5574efe623923b24f78d77f1d4bd8ef8432698

Image location:
http://autobuilder03.jf.intel.com/pub/jasperforest/20111206-1/machines/jasperforest/core-image-lsb-sdk-jasperforest.hddimg
Comment 7 yilong, sun 2011-12-16 00:24:34 UTC
This bug is not reproducible.

Commit Information:
Tree/Branch: Poky/1.2_M1
Poky Commit: b806f726b1db2cb605869c1022ef727c1110255b
Meta Branch: master branch
Meta Commit: b6d5d9a3b06caf578103a04dc5fcf5e476343205

Image location:
http://autobuilder03.jf.intel.com/pub/jasperforest/20111214-1/machines/jasperforest/core-image-lsb-sdk-jasperforest.hddimg