Repeated messages "Unable to burst-read optrom segment"

Solution Verified - Updated -

Issue

  • Following messages repeating every 10 seconds in /var/log/messages file.
2020-11-03T20:43:30.094311+01:00 hostname kernel - - - qla2xxx [0000:09:00.1]-00f5:2: Unable to burst-read optrom segment (102/7fa70100/752aae000).
2020-11-03T20:43:40.092531+01:00 hostname kernel - - - qla2xxx [0000:09:00.1]-00f5:2: Unable to burst-read optrom segment (102/7fa70100/7018a6000).
2020-11-03T20:43:40.095227+01:00 hostname kernel - - - qla2xxx [0000:09:00.1]-00f5:2: Unable to burst-read optrom segment (102/7fa70100/751fec000).
2020-11-03T20:43:50.086764+01:00 hostname kernel - - - qla2xxx [0000:09:00.1]-00f5:2: Unable to burst-read optrom segment (102/7fa70100/72e4a0000).
2020-11-03T20:43:50.091491+01:00 hostname kernel - - - qla2xxx [0000:09:00.1]-00f5:2: Unable to burst-read optrom segment (102/7fa70100/7cd539000).
2020-11-03T20:43:59.544520+01:00 hostname kernel - - - qla2xxx [0000:09:00.1]-00f5:2: Unable to burst-read optrom segment (102/7fa70180/83fec2000).

Environment

  • Red Hat Enterprise Linux 8.3
    • kernel-4.18.0-240.el8

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content