[SRU Bionic][Cosmic] kernel panic in ipmi_ssif at msg_done_handler
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Critical
|
Canonical Kernel Team | ||
Bionic |
Fix Released
|
Critical
|
Unassigned | ||
Cosmic |
Fix Released
|
Critical
|
Canonical Kernel Team |
Bug Description
[Impact]
When you boot bionic with Boot with i2c and ipmi_ssif enabled on Cavium ThunderX2 systems with a faulty BMC that does not return any data, and the code is trying to print the value if data[2], we get a kernel panic.
[ 484.728410] Unable to handle kernel NULL pointer dereference at virtual address 00000002
[ 484.736496] pgd = ffff0000094a2000
[ 484.739885] [00000002] *pgd=00000047fc
[ 484.748158] Internal error: Oops: 96000005 [#1] SMP
[...]
[ 485.101451] Call trace:
[...]
[ 485.188473] [<ffff000000a46
[ 485.195249] [<ffff000000a45
[ 485.202038] [<ffff0000080f1
[ 485.206994] [<ffff000008083
[ 485.212294] Code: aa1903e1 aa1803e0 b900227f 95fef6a5 (39400aa3)
[Test]
- System with faulty BMC
- Boot with i2c and ipmi_ssif enabled.
[Fix]
Fixed upstream with:
commit f002612b9d86613
Author: Kamlakant Patel <email address hidden>
Date: Tue Mar 13 16:32:27 2018 +0530
ipmi_ssif: Fix kernel panic at msg_done_handler
[Regression Potential]
ipmi_ssif is only loaded on ARM64 systems, this issue is observed only on Cavium ThunderX2 systems with a faulty BMC. The fix does not impact other architectures or vendor systems. Regression potential is low.
summary: |
- [SRU][Bionic] kernel panic in ipmi_ssif at msg_done_handler + [SRU Bionic][Cosmic] kernel panic in ipmi_ssif at msg_done_handler |
Changed in linux (Ubuntu): | |
assignee: | nobody → Canonical Kernel Team (canonical-kernel-team) |
status: | Incomplete → Triaged |
Changed in linux (Ubuntu Bionic): | |
importance: | Undecided → Critical |
status: | New → In Progress |
status: | In Progress → Fix Committed |
Changed in linux (Ubuntu Cosmic): | |
status: | Triaged → Fix Released |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1777716
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.