nx842: Corrupted data during uncompression due to HW issue
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| linux (Ubuntu) |
Fix Released
|
High
|
Tim Gardner | ||
| Wily |
Fix Released
|
High
|
Tim Gardner | ||
| Xenial |
Fix Released
|
Undecided
|
Tim Gardner | ||
Bug Description
== Comment: #0 - Haren Myneni <email address hidden> - 2015-09-19 20:35:29 ==
---Problem Description---
Hardware team reported some rare data corruption during uncompression for nx842 co-processor. It might provide user with invalid data after uncompression. So the fix is add CRC support - means Linux adds CRC flag before calling the nx842 so that CRC will be added and checked during compression and uncompression calls.
Contact Information = <email address hidden>
---uname output---
Ubuntu 15.10
Machine Type = power8
---Debugger---
A debugger is not configured
---Steps to Reproduce---
HW team reported this issue and discussed with them for the possible solution.
Stack trace output:
no
Oops output:
no
System Dump Info:
The system is not configured to capture a system dump.
*Additional Instructions for <email address hidden>:
-Attach sysctl -a output output to the bug.
== Comment: #1 - Haren Myneni <email address hidden> - 2015-09-19 20:36:14 ==
The fix is simple with just adding CRC flags before invoking nx842 coprocessor calls. Posted patch and waiting for maintainer to get in to his tree.
http://
Please include this fix in ubuntu 15.10 release.
| tags: | added: architecture-ppc64le bugnameltc-130892 severity-high targetmilestone-inin--- |
| Changed in ubuntu: | |
| assignee: | nobody → Taco Screen team (taco-screen-team) |
| Ubuntu Foundations Team Bug Bot (crichton) wrote | #1 |
| tags: | added: bot-comment |
| affects: | ubuntu → linux (Ubuntu) |
| Changed in linux (Ubuntu): | |
| assignee: | Taco Screen team (taco-screen-team) → Canonical Kernel Team (canonical-kernel-team) |
| importance: | Undecided → High |
| status: | New → Triaged |
| Tim Gardner (timg-tpi) wrote | #2 |
| bugproxy (bugproxy) wrote Comment bridged from LTC Bugzilla | #3 |
| bugproxy (bugproxy) wrote | #4 |
| Changed in linux (Ubuntu Wily): | |
| assignee: | Canonical Kernel Team (canonical-kernel-team) → Tim Gardner (timg-tpi) |
| status: | Triaged → In Progress |
| Changed in linux (Ubuntu Wily): | |
| status: | In Progress → Fix Committed |
| Launchpad Janitor (janitor) wrote | #5 |
| Changed in linux (Ubuntu Xenial): | |
| status: | Fix Committed → Fix Released |
| tags: |
added: targetmilestone-inin1510 removed: targetmilestone-inin--- |
| Luis Henriques (henrix) wrote | #6 |
| tags: | added: verification-needed-wily |
| tags: | removed: verification-needed-wily |
| Luis Henriques (henrix) wrote | #7 |
| tags: | added: verification-needed-wily |
| tags: |
added: verification-done-wily removed: verification-needed-wily |
| Launchpad Janitor (janitor) wrote | #8 |
| Changed in linux (Ubuntu Wily): | |
| status: | Fix Committed → Fix Released |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/
To change the source package that this bug is filed about visit https:/
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]