My server is experiencing random reboots, and I haven't been able to locate any logs explaining the cause. Below are the system details. OS: Debian 12.8 (bookworm) Hardware: SMC (SYS-111E-FWTR) kernel: Linux Dev-test 6.1.0-28-rt-amd64 #1 SMP PREEMPT_RT Debian 6.1.119-1 (2024-11-22) x86_64 GNU/Linux Drivers: ice (v1.15.5) iavf(v4.12.6) mlx5_core(24.10-1.1.4) ipmitool mc watchdog get Watchdog Timer Use: SMS/OS (0x44) Watchdog Timer Is: Started/Running Watchdog Timer Logging: On Watchdog Timer Action: No action (0x00) Pre-timeout interrupt: None Pre-timeout interval: 0 seconds Timer Expiration Flags: (0x10) * SMS/OS Initial Countdown: 300.0 sec Present Countdown: 249.5 sec last reboot reboot system boot 6.1.0-28-rt-amd6 Wed Feb 26 08:46 still running reboot system boot 6.1.0-28-rt-amd6 Wed Feb 26 07:18 - 08:43 (01:25) reboot system boot 6.1.0-28-rt-amd6 Tue Feb 25 20:42 - 08:43 (12:01) ~# uptime 10:15:03 up 1:28, 7 users, load average: 7.28, 7.76, 7.75 :~# date Wed Feb 26 10:15:05 AM EAT 2025 ~# HISTTIMEFORMAT='%Y-%m-%d %H:%M:%S ' history | grep reboot 186 2025-02-26 08:47:45 reboot 203 2025-02-26 08:47:45 reboot 250 2025-02-26 08:47:45 reboot 267 2025-02-26 08:47:45 reboot' I tried disabling watchdog action by suspecting wdt causing reboot. Verified dmesg and journal logs but no clue.

I have Many server booted up to Debian 12 connected to a common switch. All I know is their BMC Macs and bmc passwords for each unit(all of them not from same manufacturer). Is there a standard way to find out all Eth Interfaces IP address of the corresponding BMC Mac (Unit)? Is the any Ipmitool command to get IP Addresses of all the NICs? Hint: 1. I Only have IP address of one of those units and I can ssh into it(This is my DHCP server). 2. On the machine mentioned above, I can run arp-scan and get all the ip addresses of those other machines which are connected to the same switch but how do I tell which ip belongs to what corresponding BMC Mac address.

I am trying to install AlmaLinux 8.8 via use IPMI. I tried several times but installer every time stuck at same step. At first I thought the problem was in the alma iso file so I downloaded the updated version 8.8 from the almalinux official page and tried again. this did not work. I installed the proxmox iso file to see if the problem applies to almalinux 8.8 and it installed successfully. i think the problem applies to almalinux 8.8. when i check the logs i don't see any problem. what do you think is the problem? logs;

My server supports IPMI, so I can run a script like this: ~~~ fanspeed() { # 0 C => 10, 55 C => 10, 65 C => 100 sensors -j | jq '[.[]["temp1"]["temp1_input"]] | (max-55)*(100/(65-55)) | if . 100 then 100 else .|floor end end'; } autofan() { setspeed() { ipmitool -I lanplus -H drac -U root -P password raw 0x30 0x30 0x02 0xff $@ } while true; do fanspeed=fanspeed printf "$fanspeed "$(setspeed $fanspeed) sleep 1 done } ~~~ This keeps the CPU temp 55 C. But this sounds like a job for fancontrol. Can fancontrol use IPMI to control the fan?

I have a MSI MS-S0121 Mainboard with an AST2150 BMC controller with IPMI 2.0. I'm using ipmiconsole from freeipmi and serial-over-lan (SOL) to access the BIOS. The default baudrate of 19200 is quite slow, so i would like to set it to 115200 baud. But it seems that i can only set it to the value of 19200 it's already on:

[marvin@t5600 ~]$ ipmi-config -h 172.16.0.158 --username=admin --password=admin --commit -e SOL_Conf:Volatile_Bit_Rate=19200
[marvin@t5600 ~]$ ipmi-config -h 172.16.0.158 --username=admin --password=admin --commit -e SOL_Conf:Volatile_Bit_Rate=115200
ERROR: Failed to commit `SOL_Conf:Volatile_Bit_Rate'
[marvin@t5600 ~]$ ipmi-config -h 172.16.0.158 --username=admin --password=admin --checkout > bmc.conf

#
# Section UserX Comments 
#
# In the following User sections, users should configure usernames, passwords, 
# and access rights for IPMI over LAN communication. Usernames can be set to any 
# string with the exception of User1, which is a fixed to the "anonymous" 
# username in IPMI. 
#
# For IPMI over LAN access for a username, set "Enable_User" to "Yes", 
# "Lan_Enable_IPMI_Msgs" to "Yes", and "Lan_Privilege_Limit" to a privilege 
# level. The privilege level is used to limit various IPMI operations for 
# individual usernames. It is recommended that atleast one username be created 
# with a privilege limit "Administrator", so all system functions are available 
# to atleast one username via IPMI over LAN. For security reasons, we recommend 
# not enabling the "anonymous" User1. For most users, "Lan_Session_Limit" can be 
# set to 0 (or ignored) to support an unlimited number of simultaneous IPMI over 
# LAN sessions. 
#
# If your system supports IPMI 2.0 and Serial-over-LAN (SOL), 
# a"SOL_Payload_Access" field may be listed below. Set the "SOL_Payload_Access" 
# field to "Yes" or "No" to enable or disable this username's ability to access 
# SOL. 
#
# Please do not forget to uncomment those fields, such as "Password", that may 
# be commented out during the checkout. 
#
# Some motherboards may require a "Username" to be configured prior to other 
# fields being read/written. If this is the case, those fields will be set to 
# . 
#
Section User1
	## Give Username
	## Username                                   NULL
	## Give password or blank to clear. MAX 16 chars (20 chars if IPMI 2.0 supported).
	## Password                                   
	## Possible values: Yes/No or blank to not set
	## Enable_User                                
	## Possible values: Yes/No
	Lan_Enable_IPMI_Msgs                          Yes
	## Possible values: Yes/No
	Lan_Enable_Link_Auth                          Yes
	## Possible values: Yes/No
	Lan_Enable_Restricted_to_Callback             No
	## Possible values: Callback/User/Operator/Administrator/OEM_Proprietary/No_Access
	Lan_Privilege_Limit                           Administrator
	## Possible values: 0-17, 0 is unlimited; May be reset to 0 if not specified
	## Lan_Session_Limit                          
	## Possible values: Yes/No
	SOL_Payload_Access                            Yes
EndSection
Section User2
	## Give Username
	Username                                      Operator
	## Give password or blank to clear. MAX 16 chars (20 chars if IPMI 2.0 supported).
	## Password                                   
	## Possible values: Yes/No or blank to not set
	## Enable_User                                
	## Possible values: Yes/No
	Lan_Enable_IPMI_Msgs                          Yes
	## Possible values: Yes/No
	Lan_Enable_Link_Auth                          Yes
	## Possible values: Yes/No
	Lan_Enable_Restricted_to_Callback             No
	## Possible values: Callback/User/Operator/Administrator/OEM_Proprietary/No_Access
	Lan_Privilege_Limit                           Operator
	## Possible values: 0-17, 0 is unlimited; May be reset to 0 if not specified
	## Lan_Session_Limit                          
	## Possible values: Yes/No
	SOL_Payload_Access                            Yes
EndSection
Section User3
	## Give Username
	Username                                      admin
	## Give password or blank to clear. MAX 16 chars (20 chars if IPMI 2.0 supported).
	## Password                                   
	## Possible values: Yes/No or blank to not set
	## Enable_User                                
	## Possible values: Yes/No
	Lan_Enable_IPMI_Msgs                          Yes
	## Possible values: Yes/No
	Lan_Enable_Link_Auth                          Yes
	## Possible values: Yes/No
	Lan_Enable_Restricted_to_Callback             No
	## Possible values: Callback/User/Operator/Administrator/OEM_Proprietary/No_Access
	Lan_Privilege_Limit                           Administrator
	## Possible values: 0-17, 0 is unlimited; May be reset to 0 if not specified
	## Lan_Session_Limit                          
	## Possible values: Yes/No
	SOL_Payload_Access                            Yes
EndSection
Section User4
	## Give Username
	Username                                      OEM
	## Give password or blank to clear. MAX 16 chars (20 chars if IPMI 2.0 supported).
	## Password                                   
	## Possible values: Yes/No or blank to not set
	## Enable_User                                
	## Possible values: Yes/No
	Lan_Enable_IPMI_Msgs                          Yes
	## Possible values: Yes/No
	Lan_Enable_Link_Auth                          Yes
	## Possible values: Yes/No
	Lan_Enable_Restricted_to_Callback             No
	## Possible values: Callback/User/Operator/Administrator/OEM_Proprietary/No_Access
	Lan_Privilege_Limit                           OEM_Proprietary
	## Possible values: 0-17, 0 is unlimited; May be reset to 0 if not specified
	## Lan_Session_Limit                          
	## Possible values: Yes/No
	SOL_Payload_Access                            Yes
EndSection
#
# Section Lan_Channel Comments 
#
# In the Lan_Channel section, general IPMI over LAN can be enabled for disabled. 
# In the below, "Volatile" configurations are immediately configured onto the 
# BMC and will have immediate effect on the system. "Non_Volatile" 
# configurations are only available after the next system reset. Generally, both 
# the "Volatile" and "Non_Volatile" equivalent fields should be configured 
# identically. 
#
# To enable IPMI over LAN, typically "Access_Mode" should be set to 
# "Always_Available". "Channel_Privilege_Limit" should be set to the highest 
# privilege level any username was configured with. Typically, this is set to 
# "Administrator". 
#
# "User_Level_Auth" and "Per_Message_Auth" are typically set to "Yes" for 
# additional security. 
#
Section Lan_Channel
	## Possible values: Disabled/Pre_Boot_Only/Always_Available/Shared
	Volatile_Access_Mode                          Always_Available
	## Possible values: Yes/No
	Volatile_Enable_User_Level_Auth               Yes
	## Possible values: Yes/No
	Volatile_Enable_Per_Message_Auth              Yes
	## Possible values: Yes/No
	Volatile_Enable_Pef_Alerting                  Yes
	## Possible values: Callback/User/Operator/Administrator/OEM_Proprietary
	Volatile_Channel_Privilege_Limit              OEM_Proprietary
	## Possible values: Disabled/Pre_Boot_Only/Always_Available/Shared
	Non_Volatile_Access_Mode                      Always_Available
	## Possible values: Yes/No
	Non_Volatile_Enable_User_Level_Auth           Yes
	## Possible values: Yes/No
	Non_Volatile_Enable_Per_Message_Auth          Yes
	## Possible values: Yes/No
	Non_Volatile_Enable_Pef_Alerting              Yes
	## Possible values: Callback/User/Operator/Administrator/OEM_Proprietary
	Non_Volatile_Channel_Privilege_Limit          OEM_Proprietary
EndSection
#
# Section Lan_Conf Comments 
#
# In the Lan_Conf section, typical networking configuration is setup. Most users 
# will choose to set "Static" for the "IP_Address_Source" and set the 
# appropriate "IP_Address", "MAC_Address", "Subnet_Mask", etc. for the machine. 
#
Section Lan_Conf
	## Possible values: Unspecified/Static/Use_DHCP/Use_BIOS/Use_Others
	IP_Address_Source                             Static
	## Give valid IP address
	IP_Address                                    172.16.0.158
	## Give valid MAC address
	MAC_Address                                   AA:AA:AA:AA:AA:AA
	## Give valid Subnet Mask
	Subnet_Mask                                   255.255.0.0
	## Give valid IP address
	Default_Gateway_IP_Address                    0.0.0.0
	## Give valid MAC address
	Default_Gateway_MAC_Address                   00:00:00:00:00:00
EndSection
#
# Section Lan_Conf_Auth Comments 
#
# In the Lan_Conf_Auth section, allowable authentication mechanisms for IPMI 1.5 
# is configured. Most users will want to set all "MD5" authentication to "Yes" 
# and the rest to "No". If you have configured a NULL username and a NULL 
# password, you will also want to configure some of the "None" fields to "Yes" 
# to allow "None" authentication to work. Some motherboards do not allow you to 
# enable OEM authentication, so you may wish to set all OEM related fields to 
# "No". 
#
Section Lan_Conf_Auth
	## Possible values: Yes/No
	Callback_Enable_Auth_Type_None                Yes
	## Possible values: Yes/No
	Callback_Enable_Auth_Type_MD5                 Yes
	## Possible values: Yes/No
	Callback_Enable_Auth_Type_Straight_Password   Yes
	## Possible values: Yes/No
	User_Enable_Auth_Type_None                    Yes
	## Possible values: Yes/No
	User_Enable_Auth_Type_MD5                     Yes
	## Possible values: Yes/No
	User_Enable_Auth_Type_Straight_Password       Yes
	## Possible values: Yes/No
	Operator_Enable_Auth_Type_None                Yes
	## Possible values: Yes/No
	Operator_Enable_Auth_Type_MD5                 Yes
	## Possible values: Yes/No
	Operator_Enable_Auth_Type_Straight_Password   Yes
	## Possible values: Yes/No
	Admin_Enable_Auth_Type_None                   Yes
	## Possible values: Yes/No
	Admin_Enable_Auth_Type_MD5                    Yes
	## Possible values: Yes/No
	Admin_Enable_Auth_Type_Straight_Password      Yes
	## Possible values: Yes/No
	OEM_Enable_Auth_Type_None                     Yes
	## Possible values: Yes/No
	OEM_Enable_Auth_Type_MD5                      Yes
	## Possible values: Yes/No
	OEM_Enable_Auth_Type_Straight_Password        Yes
EndSection
#
# Section Lan_Conf_Security_Keys Comments 
#
# If your system supports IPMI 2.0 and Serial-over-LAN (SOL), a K_g BMC key may 
# be configurable. The K_g key is an optional key that can be set for two key 
# authentication in IPMI 2.0. It is optionally configured. Most users will want 
# to set this to zero (or blank). 
#
Section Lan_Conf_Security_Keys
	## Give string or blank to clear. Max 20 bytes, prefix with 0x to enter hex
	K_G                                           0x0000000000000000000000000000000000000000
EndSection
#
# Section Lan_Conf_User_Security Comments 
#
# The following user security configuration options are optionally implemented 
# by the vendor. They may not be available your system and may not be visible 
# below. 
#
# The following configuration supports the ability for the BMC to disable a user 
# if a number of bad passwords are entered sequentially. 
# "Bad_Password_Threshold" determines the number of bad passwords that must be 
# entered sequentially. "Attempt_Count_Reset_Interval" determines the range of 
# time the bad passwords must occur in. "User_Lockout_Interval" determines the 
# time a user will be locked off if the bad password threshold is reached. If 
# set to "Yes", "Enable_Event_Message_When_User_Disabled" will inform the BMC to 
# log an event message when a user is disabled. 
#
Section Lan_Conf_User_Security
EndSection
#
# Section Lan_Conf_Misc Comments 
#
# The following miscellaneous configuration options are optionally implemented 
# by the vendor. They may not be available your system and may not be visible 
# below. 
#
# If set to "Yes", "Enable_Gratuitous_ARPs" will inform the BMC to regularly 
# send out Gratuitous ARPs to allow other machines on a network resolve the 
# BMC's MAC Address. Many users will want to set this to "Yes" because it offers 
# the easiest way to support BMC IP Address resolution. However, it will 
# increase traffic on your network. The "Gratuitous_ARP_Interval" can be used to 
# set the period a Gratuitous ARP is always sent. 
#
# If set to "Yes", "Enable_ARP_Response" will inform the BMC torespond to ARP 
# requests from other machines. 
#
Section Lan_Conf_Misc
EndSection
#
# Section Rmcpplus_Conf_Privilege Comments 
#
# If your system supports IPMI 2.0 and Serial-over-LAN (SOL),cipher suite IDs 
# may be configurable below. In the Rmcpplus_Conf_Privilege section, maximum 
# user privilege levels allowed for authentication under IPMI 2.0 (including 
# Serial-over-LAN) are set for each supported cipher suite ID. Each cipher suite 
# ID supports different sets of authentication, integrity, and encryption 
# algorithms for IPMI 2.0. Typically, the highest privilege level any username 
# configured should set for support under a cipher suite ID. This is typically 
# "Administrator". 
#
Section Rmcpplus_Conf_Privilege
	## Possible values: Unused/User/Operator/Administrator/OEM_Proprietary
	Maximum_Privilege_Cipher_Suite_Id_0           OEM_Proprietary
	## Possible values: Unused/User/Operator/Administrator/OEM_Proprietary
	Maximum_Privilege_Cipher_Suite_Id_1           OEM_Proprietary
	## Possible values: Unused/User/Operator/Administrator/OEM_Proprietary
	Maximum_Privilege_Cipher_Suite_Id_2           OEM_Proprietary
	## Possible values: Unused/User/Operator/Administrator/OEM_Proprietary
	Maximum_Privilege_Cipher_Suite_Id_3           OEM_Proprietary
EndSection
#
# Section SOL_Conf Comments 
#
# If your system supports IPMI 2.0 and Serial-over-LAN (SOL), the following 
# configuration options will allow SOL configuration. 
#
# For most users that want to enable SOL, minimally "Enable_SOL" should be set 
# to "Yes" and "SOL_Privilege_Level" should be set to the highest privilege 
# level any username configured can authenticate with (typically 
# "Administrator"). For security purposes, "Force_SOL_Payload_Authentication" 
# and "Force_SOL_Payload_Encryption" should be set to "Yes", however forced 
# authentication and/or encryption depends on the cipher suite IDs supported. 
# The "Non_Volatile_Bit_Rate" and "Volatile_Bit_Rate" should both be set to the 
# appropriate baud rate for your system. This is typically the same baud rate 
# configured in the BIOS and/or operating system. 
#
Section SOL_Conf
	## Possible values: Yes/No
	Enable_SOL                                    Yes
	## Possible values: Callback/User/Operator/Administrator/OEM_Proprietary
	SOL_Privilege_Level                           Administrator
	## Possible values: Yes/No
	Force_SOL_Payload_Authentication              No
	## Possible values: Yes/No
	Force_SOL_Payload_Encryption                  No
	## Give a non-zero valid integer. Each unit is 5ms
	Character_Accumulate_Interval                 20
	## Give a valid number
	Character_Send_Threshold                      80
	## Give a valid integer
	SOL_Retry_Count                               7
	## Give a valid integer. Interval unit is 10ms
	SOL_Retry_Interval                            250
	## Possible values: Serial/9600/19200/38400/57600/115200
	Non_Volatile_Bit_Rate                         19200
	## Possible values: Serial/9600/19200/38400/57600/115200
	Volatile_Bit_Rate                             19200
	## Give a valid port number
	## SOL_Payload_Port_Number                    623
EndSection

Any suggestions?

I'm trying to clean up known or bogus error messages that shows up in the log when I boot my Debian server, in order to more clearly see actual errors. Now it's come to this: Base address is zero, assuming no IPMI interface Since I know that my system ([Supermicro H8SGL](https://www.supermicro.com/Aplus/motherboard/Opteron6000/SR56x0/H8SGL.cfm)) does _not_ have IPMI (gotta pay extra - I didn't) it appears that the vendor sets the base address to zero to mark a non-existing feature, something that the kernel frowns upon according to the [kernel patch](https://github.com/torvalds/linux/commit/1574608f5f4204440d6d9f52b971aba967664764) introducing the message. From the changelog: > **ipmi:dmi: Ignore IPMI SMBIOS entries with a zero base address** > >Looking at logs from systems all over the place, it looks like tons of broken systems exist that set the base address to zero. I can only guess that is some sort of non-standard idea to mark the interface as not being present. It can't be zero, anyway, so just complain and ignore it. Can I tell the kernel at boot with some kind of flag that I don't even want it to try doing whatever it does in order to end up with this error? I'm not sure if this is a module that is being autoloaded, something built in to the kernel, or something else... There is a possibly-relevant question here at U&L, https://unix.stackexchange.com/questions/470359/boot-error-ipmidmi-invalid-offset-0 but the answer is basically "just try newer kernels" and a bunch of people in forums who thinks it relates to Windows and SSDs, so it is not very helpful.