Description of problem:

On an older Supermicro platform, board model X10SRi-F, execution of the the tools "monitor-edid" or "monitor-get-edid-using-vbe" cause a core dump error in syslog, followed shortly thereafter by a system crash that requires a hard-reset to bring the system back up.

The syslog message is:

Jul 21 00:12:01 localhost kernel: traps: monitor-get-edi[129522] general protection fault ip:7f2312e9e0a8 sp:7fffae140ff8 error:0 in libx86.so.1[7f2312e9d000+14000]
Jul 21 00:12:01 localhost systemd[1]: Created slice Slice /system/systemd-coredump.
Jul 21 00:12:01 localhost systemd[1]: Started Process Core Dump (PID 129523/UID 0).
Jul 21 00:12:01 localhost systemd-coredump[129524]: Resource limits disable core dumping for process 129522 (monitor-get-edi).
Jul 21 00:12:01 localhost systemd-coredump[129524]: Process 129522 (monitor-get-edi) of user 0 dumped core.

Shortly after the core dump message is generated, the system will lock up hard, no other errors are generated.

Unfortunately, this error is unavoidable in my environment, as the "monitor-edid" tools are called routinely by the "OCS Inventory" toolset that is used to catalog system contents.

I only encounter this error (so far) on the Supermicro X10 hardware. I have HP and Dell hardware running the same OS version that do not exhibit the problem.

Version-Release number of selected component (if applicable):

Kernel: 5.14.0-130.el9.x86_64
EDID version: monitor-edid-3.4-1.el9.x86_64
Supermicro X10 BIOS version 3.4 (latest as of 7/22)

How reproducible:

100% reproducible on every execution of problem commands.

Steps to Reproduce:
1. On a Supermicro X10 platform with only integrated video, execute either command
/usr/sbin/monitor-edid
/usr/sbin/monitor-get-edid-using-vbe

2. Observe core dump message in syslog

3. System locks up and require hard reset to restore to operation

Actual results:

Core dump and system lockup

Expected results:

No errors or system interruption

Additional info:

Output from dmidecode is attached.