Bug#1116074: IPMI stops working after BIOS starts Debian/Trixie
Package: installation-reports
Version: debian-live-13.1.0-amd64-standard.iso
Severity: important
Motherboard: Supermicro X8DTI
CPU: Dual Xeon X5675
RAM: 192GB Samsung DDR3 EEC
Short Description: OS (grub?) stops responding to IPMI keyboard
Interface after BIOS handoff to boot disk. Problem is exclusive to
Trixie and not apparent in any other OS that I have tried with this
exact hardware. Sensors and video continue to function normally.
Long Description: Using the Supermicro IPMIView Windows Application
(or the http web interface),the IPMI interface works fully from
initial boot until the BIOS hands off control to the OS (grub?). Once
the Grub OS Selection menu appears on screen, keyboard inputs to the
IPMI controller are not accepted by the computer thereafter. This
behaviour is unique to Debian/Trixie. I have used the IPMI interface
on this computer (same hardware, different drives) with numerous other
OSs and never seen a problem before this. This first arose when I
attempted to install Proxmox built on the Debian/Trixie platform and
IPMI stopped working. People within the Proxmox community had a very
difficult time believing me that this behavior is actually occurring,
instead stating that it cannot happen as described (but it is). I
decided to try to run a LIVE Debian Trixie install to take the Proxmox
overlay out of the equation, and discovered the same issue. When I
return to booting the same computer with the prior boot drive, the
IPMI interface works normally and keyboard inputs are accepted once
again. I.e. The bug is 100% reproducible and appears to be exclusive
to the latest version of Debian/Trixie. i have probably worked with
over a dozen different OS's on the hardware (bare metal) and never had
this issue before. It seems to me that somehow, the OS (grub?) is
turning off the IPMI interface.
Reply to: