ipmi_si module spams kernel log with "ipmi_si 00:05: Could not set the global enables: 0xcc."

Bug #1483214 reported by Felix Matouschek
28
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned
Vivid
Fix Released
Medium
Stefan Bader
openipmi (Ubuntu)
Invalid
Undecided
Unassigned
Vivid
Invalid
Undecided
Unassigned

Bug Description

Hello,

after upgrading my system to 14.04.3 LTS and installing the Vivid-LTS-Enablement-Stack the kernel log of my system is spammed with the following message by the "impi_si" kernel module:

...
[ 2268.244383] ipmi_si 00:05: Could not set the global enables: 0xcc.
[ 2269.451974] ipmi_si 00:05: Could not set the global enables: 0xcc.
[ 2270.252290] ipmi_si 00:05: Could not set the global enables: 0xcc.
[ 2271.452749] ipmi_si 00:05: Could not set the global enables: 0xcc.
[ 2272.253057] ipmi_si 00:05: Could not set the global enables: 0xcc.
...

This bug is already known to the ipmi_si kernel module maintainer and seems to be fixed in 4.0+ kernels.

Is it possible to backport this fix to the Vivid 3.19 kernel?

Please see this mail thread: https://<email address hidden>/msg02425.html

IPMI functionality seems to be unaffected by this bug but as I said it spams the kernel log and that is rather annoying.

System information:

lsb_release -rd:
    Description: Ubuntu 14.04.3 LTS
    Release: 14.04

apt-cache policy openipmi:

    openipmi:
      Installiert: 2.0.18-0ubuntu7.1
      Installationskandidat: 2.0.18-0ubuntu7.1
      Versionstabelle:
     *** 2.0.18-0ubuntu7.1 0
            500 http://de.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
            100 /var/lib/dpkg/status
         2.0.18-0ubuntu7 0
            500 http://de.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

Greetings,
Felix

Revision history for this message
Felix Matouschek (felix-matouschek) wrote :
Robie Basak (racb)
tags: added: server-next
Stefan Bader (smb)
affects: linux-meta-lts-vivid (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
status: New → Fix Released
Changed in linux (Ubuntu Vivid):
importance: Undecided → Medium
status: New → Triaged
Changed in openipmi (Ubuntu):
status: New → Invalid
Changed in openipmi (Ubuntu Vivid):
status: New → Invalid
Revision history for this message
Felix Matouschek (felix-matouschek) wrote :

Does Fix Released mean I should go back to Kernel 3.13 meanwhile?! (shows Kernel 3.13 when hovering on it)

Would be cool if this could be ported back to the 3.19 Kernel.

Revision history for this message
Stefan Bader (smb) wrote :

The fix released is for the development branch (Wily/15.10) which is using kernel 4.1 currently. Not sure how launchpad decides what use as summary for the link. The fix looks to be backportable. Might just be a few iterations to go through the process. Right now I would prepare a replacement 3.19 HWE kernel for Trusty/14.04 for you to try. I let you know where to get that from when it is ready.

Changed in linux (Ubuntu Vivid):
assignee: nobody → Stefan Bader (smb)
Revision history for this message
Stefan Bader (smb) wrote :

Test kernel (download all *.deb files and install with "sudo dpkg -i *.deb") can be found at:

http://people.canonical.com/~smb/lp1483214/

Revision history for this message
Stefan Bader (smb) wrote :

With that kernel you should get an error message once about the BMC needing fixing.

Revision history for this message
Felix Matouschek (felix-matouschek) wrote :

I will test it soon, the system is in production use so I have to wait until the end of the day.

Revision history for this message
Felix Matouschek (felix-matouschek) wrote :

Tested your kernel, it is working fine!

As you said, the error message only appears once!

Thank you!

I guess this can be merged...

Revision history for this message
Stefan Bader (smb) wrote :

SRU Justtification

Impact: The driver code changed in 3.19 to do periodic checks on irq and message settings
  commit d9b7e4f717a167610a49ceb9e5969e80146c89a8
  ipmi: Periodically check to see if irqs and messages are set right
This causes repeated error messages in the logs for certain BMCs which do not allow to disable the irq mode in the global config even when they do not support irqs.

Fix: Cherry-pick upstream commit 1e7d6a45f6b10bc48a1453bca3d829e210546571 which adds a quirk to detect this situation and avoids touching those bits. This was done in 4.0, so the only affected kernel is 3.19.

Testcase: With an affected BMC and without the patch, errors repeatedly get logged. With the patch applied, there will be only a single message in the log.

Brad Figg (brad-figg)
Changed in linux (Ubuntu Vivid):
status: Triaged → Fix Committed
Revision history for this message
Luis Henriques (henrix) wrote :

This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-vivid' to 'verification-done-vivid'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: verification-needed-vivid
Revision history for this message
Felix Matouschek (felix-matouschek) wrote :

The 3.19.0-27.29 kernel broke something with our RAID array.... but it seems like IPMI is working.

I can't keep the system down for too long... will try again on friday afternoon...

Revision history for this message
Felix Matouschek (felix-matouschek) wrote :

Everything works as expected!

...
[ 153.182919] IPMI Watchdog: driver initialized
[ 219.205870] IPMI System Interface driver.
[ 219.205929] ipmi_si: probing via ACPI
[ 219.205961] ipmi_si 00:05: [io 0x0ca2] regsize 1 spacing 1 irq 0
[ 219.205964] ipmi_si: Adding ACPI-specified kcs state machine
[ 219.205985] ipmi_si: probing via SMBIOS
[ 219.205987] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
[ 219.205989] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
[ 219.205992] ipmi_si: probing via SPMI
[ 219.205994] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
[ 219.205996] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
[ 219.205999] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
[ 219.339114] ipmi_si: The BMC does not support clearing the recv irq bit, compensating, but the BMC needs to be fixed.
[ 219.374485] ipmi_si 00:05: Found new BMC (man_id: 0x002a7c, prod_id: 0x0728, dev_id: 0x20)
[ 219.374497] ipmi_si 00:05: IPMI kcs interface initialized
[ 219.382763] ipmi device interface
[ 219.399583] IPMI Watchdog: driver initialized
...

tags: added: verification-done-vivid
removed: verification-needed-vivid
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (14.6 KiB)

This bug was fixed in the package linux - 3.19.0-28.30

---------------
linux (3.19.0-28.30) vivid; urgency=low

  [ Luis Henriques ]

  * Release Tracking Bug
    - LP: #1490606

  [ Gary Wang ]

  * SAUCE: i915_bpo: drm/i915: set CDCLK if DPLL0 enabled during resuming
    from S3
    - LP: #1490035

  [ Timo Aaltonen ]

  * Revert "SAUCE: i915_bpo: drm/i915/skl: DDI-E and DDI-A shares 4 lanes."
    - LP: #1490038

linux (3.19.0-27.29) vivid; urgency=low

  [ Brad Figg ]

  * Release Tracking Bug
    - LP: #1485113

  [ Adam Lee ]

  * SAUCE: serial: 8250_pci: Add support for Pericom PI7C9X795[1248]
    - LP: #1480142

  [ Arun Siluvery ]

  * SAUCE: i915_bpo: drm/i915/gen8: Add infrastructure to initialize WA
    batch buffers
    - LP: #1484486
  * SAUCE: i915_bpo: drm/i915/gen8: Re-order init pipe_control in lrc mode
    - LP: #1484486
  * SAUCE: i915_bpo: drm/i915/gen8: Add WaDisableCtxRestoreArbitration
    workaround
    - LP: #1484486
  * SAUCE: i915_bpo: drm/i915/gen8: Add
    WaFlushCoherentL3CacheLinesAtContextSwitch workaround
    - LP: #1484486
  * SAUCE: i915_bpo: drm/i915: Bail out early if WA batch is not available
    for given Gen
    - LP: #1484486
  * SAUCE: i915_bpo: drm/i915/gen8: Add WaClearSlmSpaceAtContextSwitch
    workaround
    - LP: #1484486
  * SAUCE: i915_bpo: drm/i915: Update
    WaFlushCoherentL3CacheLinesAtContextSwitch
    - LP: #1484486
  * SAUCE: i915_bpo: drm/i915: Enable WA batch buffers for Gen9
    - LP: #1484486
  * SAUCE: i915_bpo: drm/i915/gen9: Add WaDisableCtxRestoreArbitration
    workaround
    - LP: #1484486
  * SAUCE: i915_bpo: drm/i915: Update wa_ctx_emit() macro as per kernel
    coding guidelines
    - LP: #1484486
  * SAUCE: i915_bpo: drm/i915/gen9: Add
    WaFlushCoherentL3CacheLinesAtContextSwitch workaround
    - LP: #1484486
  * SAUCE: i915_bpo: drm/i915/gen9: Add
    WaSetDisablePixMaskCammingAndRhwoInCommonSliceChicken
    - LP: #1484486
  * SAUCE: i915_bpo: drm/i915:skl: Add WaEnableGapsTsvCreditFix
    - LP: #1484486

  [ Chris Wilson ]

  * SAUCE: i915_bpo: drm/i915: Use two 32bit reads for select 64bit
    REG_READ ioctls
    - LP: #1484482
  * SAUCE: i915_bpo: drm/i915: Replace WARN inside I915_READ64_2x32 with
    retry loop
    - LP: #1484482
  * SAUCE: i915_bpo: drm/i915: Mark PIN_USER binding as GLOBAL_BIND without
    the aliasing ppgtt
    - LP: #1484482
  * SAUCE: i915_bpo: drm/i915: Declare the swizzling unknown for L-shaped
    configurations
    - LP: #1484482

  [ Damien Lespiau ]

  * SAUCE: i915_bpo: drm/i915/skl: Don't expose the top most plane on gen9
    display
    - LP: #1484486

  [ Daniel Vetter ]

  * SAUCE: i915_bpo: drm/i915: Fixup dp mst encoder selection
    - LP: #1484482

  [ David Weinehall ]

  * SAUCE: i915_bpo: drm/i915: Allow parsing of variable size child device
    entries from VBT
  * SAUCE: i915_bpo: drm/i915: Allow parsing of variable size child device
    entries from VBT, addendum v2
    - LP: #1484482

  [ Jani Nikula ]

  * SAUCE: i915_bpo: drm/i915/skl: WaIgnoreDDIAStrap is forever, always
    init DDI A
    - LP: #1484486
  * SAUCE: i915_bpo: drm/i915: reduce indent in i9xx_hpd_irq_handler
    - LP: #1484531
  * SAUCE: i915_bpo: drm/i91...

Changed in linux (Ubuntu Vivid):
status: Fix Committed → Fix Released
Revision history for this message
Elias Abacioglu (raboo) wrote :

I'm running trusty with wily kernel 4.2.0-35-generic, linux-generic-lts-wily.

It's also affected by the same problem.

Revision history for this message
Stefan Bader (smb) wrote :

Please open a new bug report by running "ubuntu-bug linux" on the machine that you think is affected. The fix which this bug report is about was a 4.0 change and is contained in the 4.2 kernel.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.