Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-71926

[RHEL-10.0] add i2c_piix4 to blacklist in AMI

Linking RHIVOS CVEs to...Migration: Automation ...SWIFT: POC ConversionSync from "Extern...XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • rhel-10.1
    • rhel-10.0
    • osbuild
    • No
    • Low
    • 1
    • image-builder-1
    • 1
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • Image Builder 3
    • All
    • None

      What were you trying to do that didn't work?

      Base on the discussion in RHEL-70163, i2c_piix4 is not used in aws. I am suggesting to add i2c_piix4 into blacklist when build aws AMIs.

      What is the impact of this issue to you?

      It reports "i2c i2c-0: Failed! (ff)" during boot on some of aws instance types.

      Amazon Linux does not have i2c_piix4 build in, so we guess it is safe to add it to blacklist on aws.

      Please provide the package NVR for which bug is seen:

      6.12.0-31.el10.x86_64

      How reproducible:

      Steps to reproduce

      launch a RHEl-10.0 aws u-18tb1.112xlarge
      check the dmesg

      Expected results

      No i2c failure during boot

      Actual results

      i2c device appears but cannot work

              thozza@redhat.com Tomas Hozza
              xiliang@redhat.com Frank Liang
              Osbuilders Bot Account Osbuilders Bot Account
              Release Test Team Release Test Team
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

                Created:
                Updated: