[Ubuntu 14.04.3] kernel patches for RAS tools
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
High
|
Leann Ogasawara | ||
Vivid |
Fix Released
|
High
|
Chris J Arges |
Bug Description
[Impact]
Patches required to support RAS on 14.04.3 kernel
[Test Case]
Try using RAS tools on powernv platform.
[Fix]
commit 3f77df7f81526c9
Author: Vasant Hegde <email address hidden>
Date: Fri Feb 13 15:26:33 2015 +0530
powerpc/
Present code checks for update_flash_data in opal_flash_
update_
is the value of FLASH_IMG_READY. Also code update initialization happens
during subsys init.
So if reboot is issued before the subsys init stage then we endup displaying
"Flashing new firmware" message.. which may confuse end user.
This patch fixes above described issue by initializes update_flash status
to invalid state.
Reported-by: Sam Bobroff <email address hidden>
Signed-off-by: Vasant Hegde <email address hidden>
Signed-off-by: Benjamin Herrenschmidt <email address hidden>
Related branches
tags: | added: architecture-ppc64le bugnameltc-124884 severity-high targetmilestone-inin14043 |
Changed in ubuntu: | |
assignee: | nobody → Chris J Arges (arges) |
importance: | Undecided → High |
status: | New → Triaged |
affects: | ubuntu → linux (Ubuntu) |
Changed in linux (Ubuntu Vivid): | |
assignee: | nobody → Chris J Arges (arges) |
importance: | Undecided → High |
status: | New → Triaged |
Changed in linux (Ubuntu): | |
assignee: | Chris J Arges (arges) → Leann Ogasawara (leannogasawara) |
Changed in linux (Ubuntu): | |
status: | Triaged → Fix Committed |
Changed in linux (Ubuntu Vivid): | |
status: | Triaged → Fix Committed |
tags: |
added: verification-done-vivid removed: verification-needed-vivid |
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:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/1461553/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]