Bug 1551285
| Summary: | Kernel: Booting with module ipmi_si crashes the kernel | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Dieter Stolte <dstolte> | ||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 26 | CC: | airlied, bskeggs, ewk, hdegoede, ichavero, itamar, jarodwilson, jcline, jglisse, john.j5live, jonathan, josef, kernel-maint, labbott, linville, mchehab, mjg59, rkudyba, steved | ||||
| Target Milestone: | --- | Keywords: | Reopened | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2018-05-29 11:24:42 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Dieter Stolte
2018-03-04 12:20:09 UTC
Please try the scratch build at https://koji.fedoraproject.org/koji/taskinfo?taskID=25506144 *** This bug has been marked as a duplicate of bug 1549316 *** Some questions: 1. is there also a kernel for fedora 26 to test? 2. I installed the rpm kernel-core-4.15.7-200.fc26.x86_64 from updates-testing. is this the proposed fixed kernel? if the answer is yes, then it still fails with above error message. 3. how do I install a scratch build kernel? Hi Dieter, According to the bug this was marked a duplicate of, this got fixed in 4.15.8. I think that build failed for F26, but 4.15.9 should be in updates-testing now. Hi Jeremy, thanks for your reply. I installed kernel 4.15.9-200.fc26.x86_64 but it still crashes on the ipmi module: Mär 19 10:43:08 nas kernel: Linux version 4.15.9-200.fc26.x86_64 (mockbuild.fedoraproject.org) (gcc version 7.3.1 20180130 (Red Hat 7.3.1-2) (GCC)) #1 SMP Mon Mar 12 17:11:43 UTC 2018 ... Mär 19 10:33:42 nas kernel: BUG: unable to handle kernel NULL pointer dereference at 0000000000000030 Thats all from the log files. I made a screenshot with the kernel trace but cant load it from my phone because bluetooth is also broken in fedora 26 at the moment. Trying to fix that. I reopened the bug nevertheless because it is clearly not fixed. Created attachment 1409783 [details]
Kernel Trace with kernel 4.15.9
Screenshot of kernel trace
Can you try a rawhide kernel? The maintainer has been fixing things so it's possible something was missed from stable. Installed kernel-4.16.0-0.rc5.git3.1.fc29.x86_64.rpm from rawhide. Doesnt work, same trace. This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. We're on Fedora 27 with 4.16.7-200.fc27.x86_64 and the BMC/impi no longer respond on a HP DL180 G6. Not sure if this is the same issue, if not let me know and I'll create a new bug report. [Tue May 15 09:03:30 2018] ipmi message handler version 39.2 [Tue May 15 09:03:30 2018] ipmi device interface [Tue May 15 09:03:30 2018] IPMI System Interface driver. [Tue May 15 09:03:30 2018] ipmi_si dmi-ipmi-si.0: ipmi_platform: probing via SMBIOS [Tue May 15 09:03:30 2018] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0 [Tue May 15 09:03:30 2018] ipmi_si: Adding SMBIOS-specified kcs state machine [Tue May 15 09:03:30 2018] ipmi_si IPI0001:00: ipmi_platform: probing via ACPI [Tue May 15 09:03:30 2018] ipmi_si IPI0001:00: [io 0x0ca2] regsize 1 spacing 1 irq 0 [Tue May 15 09:03:30 2018] ipmi_si dmi-ipmi-si.0: Removing SMBIOS-specified kcs state machine in favor of ACPI [Tue May 15 09:03:30 2018] ipmi_si: Adding ACPI-specified kcs state machine [Tue May 15 09:03:30 2018] ipmi_platform: probing via SPMI [Tue May 15 09:03:30 2018] ipmi_si: SPMI: mem 0x0 regsize 1 spacing 1 irq 0 [Tue May 15 09:03:30 2018] ipmi_si: Adding SPMI-specified kcs state machine [Tue May 15 09:03:30 2018] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x20, irq 0 [Tue May 15 09:03:30 2018] ipmi_si IPI0001:00: There appears to be no BMC at this location [Tue May 15 09:03:30 2018] ipmi_si: Trying SPMI-specified kcs state machine at mem address 0x0, slave address 0x0, irq 0 [Tue May 15 09:03:30 2018] ipmi_si ipmi_si.0: Could not set up I/O space [Tue May 15 09:03:30 2018] IPMI SSIF Interface driver I've tried these settings; cat /sys/module/ipmi_si/parameters/kipmid_max_busy_us 100 cat /etc/modprobe.d/ipmi_si.conf options ipmi_si type=kcs ports=0xca8 regspacings=4 This was related to a kernel panic, what you have is a different issue. If you have a working and non-working kernel your best bet is to do a bisect or report the issue to the upstream maintainer directly. Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |