"Maybe" False positive error while booting >> ipmi_si dmi-ipmi-si.0: IRQ index 0 not found || ipmi_si IPI0001:00: IRQ index 0 not found || after latest OMV Kernel + Usul updates.

  • Hi wonderful people,


    I am having a never seen before issue that started right after last week's OMV (Debian) Linux Kernel updates and same time Usul upgrades.
    So my current is Openmediavault 5.2.4-1 (Usul) running on Linux 5.4.0-0.bpo.2-amd64 #1 SMP Debian 5.4.8-1~bpo10+1 (2020-01-07) x86_64.


    I premise that I religiously apply updates and then reboot the server as soon as I get each cron alert, within 48 hours which is standard best practice in my lab.
    Starting that time (1/10/2020) I am getting this error during boot up sequence: I noticed it only because I was in front of the panel during the upgrades and reboots, otherwise I would have not even noticed them.


    "ipmi_si dmi-ipmi-si.0: IRQ index 0 not found
    ipmi_si IPI0001:00: IRQ index 0 not found"


    That's it, no other error message ?( , and they show up just at the end of the boot sequence, right before clearing up for the main login prompt.
    IPMI interface on my motherboard (Supermicro) works just fine: I can access, launch reboot/shutdown commands and the java KVM from remote.
    I scoured the net for similar error and I only found one single similar reference for the most recent Clear-linux-native-5.4.2-875 distribution update, right on its official github bug forum.
    They consider it a false positive and marked it as bug. 8|
    May it be also a false positive for this Usul /SMP Debian version?


    I admit I have no knowledge of IPMI modules commands/tools/debug, hence I know not how to query any internal tool for further detail: suggestions are welcome !!
    The reason why I am not going nuts about this is that everything is working perfectly, IPMI interface included: my only concern founded would Usul actually be utilizing IPMI on my motherboard for triggers, power monitoring or other functions and now it is not.


    Alas, I would not even know if they are working or not as I cannot find either ipmi_si or dmi-ipmi-si module/reference in syslog to even query.


    Any takers? Suggestions? Shall I just ignore / "snooze-button-on-worry" for now?


    Yours truly,
    peace and love.
    Jor

    • Offizieller Beitrag

    "snooze-button-on-worry" for now?

    I would do this. The 5.4 kernel is very new and needs more testing. That is the price we pay for using the backports kernel. But if it isn't causing an issue, I wouldn't worry too much.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.6 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!