There are netcp error on dmesg
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-keystone (Ubuntu) |
Fix Released
|
Critical
|
Ike Panhc |
Bug Description
[ 21.362456] keystone-netcp 2090000.netcp: bad response context, got 0x00000000
[ 21.363082] keystone-netcp 2090000.netcp: bad response context, got 0x00000000
[ 21.363097] keystone-netcp 2090000.netcp: bad response context, got 0x00000000
[ 21.363112] keystone-netcp 2090000.netcp: bad response context, got 0x00000000
[ 21.370198] keystone-netcp 2090000.netcp: bad response context, got 0x00000000
[ 21.370213] keystone-netcp 2090000.netcp: bad response context, got 0x00000000
[ 21.370224] keystone-netcp 2090000.netcp: bad response context, got 0x00000000
[ 21.902777] keystone-netcp 2090000.netcp: bad response context, got 0x00000000
$ cat /proc/version
Linux version 3.13.0-6-keystone (buildd@kishi06) (gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-12ubuntu1) ) #9-Ubuntu SMP Tue Jun 24 15:59:35 UTC 2014
Related branches
Changed in linux-keystone (Ubuntu): | |
importance: | Undecided → High |
Changed in linux-keystone (Ubuntu): | |
status: | Fix Released → In Progress |
importance: | High → Critical |
assignee: | Ike Panhc (ikepanhc) → Garrett Ding (g-ding) |
Changed in linux-keystone (Ubuntu): | |
assignee: | Garrett Ding (g-ding) → Ike Panhc (ikepanhc) |
status: | In Progress → Fix Released |
Looks like disable CONFIG_ IOMMU_SUPPORT can fix this issue