IPMI BT kernel error messages in Red Hat Enterprise Linux

Issue

The following messages are shown in /var/log/messages and dmesg:

Oct  9 07:57:10 server01 kernel: IPMI: BT reset (takes 5 secs)
Oct  9 07:59:00 server01 kernel: IPMI BT: timeout in RD_WAIT [ ] failed 2 retries, sending error response
Oct  9 07:59:00 server01 kernel: IPMI: BT reset (takes 5 secs)
Oct  9 08:00:51 server01 kernel: IPMI BT: timeout in RD_WAIT [ ] failed 2 retries, sending error response
Oct  9 08:00:51 server01 kernel: IPMI: BT reset (takes 5 secs)
Oct  9 08:02:41 server01 kernel: IPMI BT: timeout in RD_WAIT [ ] failed 2 retries, sending error response
Oct  9 08:02:41 server01 kernel: IPMI: BT reset (takes 5 secs)
Oct  9 08:04:31 server01 kernel: IPMI BT: timeout in RD_WAIT [ ] failed 2 retries, sending error response
Oct  9 08:04:31 server01 kernel: IPMI: BT reset (takes 5 secs)
Oct  9 08:06:21 server01 kernel: IPMI BT: timeout in RD_WAIT [ ] failed 2 retries, sending error response
Oct  9 08:06:21 server01 kernel: IPMI: BT reset (takes 5 secs)
Oct  9 08:08:11 server01 kernel: IPMI BT: timeout in RD_WAIT [ ] failed 2 retries, sending error response
Oct  9 08:08:11 server01 kernel: IPMI: BT reset (takes 5 secs)
Oct  9 08:10:01 server01 kernel: IPMI BT: timeout in RD_WAIT [ ] failed 2 retries, sending error response
Oct  9 08:10:01 server01 kernel: IPMI: BT reset (takes 5 secs)
Oct  9 08:11:52 server01 kernel: IPMI BT: timeout in RD_WAIT [ ] failed 2 retries, sending error response
Oct  9 08:11:52 server01 kernel: IPMI: BT reset (takes 5 secs)
Oct  9 08:13:42 server01 kernel: IPMI BT: timeout in RD_WAIT [ ] failed 2 retries, sending error response
Oct  9 08:13:42 server01 kernel: IPMI: BT reset (takes 5 secs)
Oct  9 08:15:32 server01 kernel: IPMI BT: timeout in RD_WAIT [ ] failed 2 retries, sending error response
Oct  9 08:15:32 server01 kernel: IPMI: BT reset (takes 5 secs)
Oct  9 08:17:22 server01 kernel: IPMI BT: timeout in RD_WAIT [ ] failed 2 retries, sending error response
Oct  9 08:17:22 server01 kernel: IPMI: BT reset (takes 5 secs)

Also, a stuck in D-state modprobe can be seen in process list:

# ps aux | grep D
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root      9880  0.0  0.0   4024   732 ?        D     2014   0:32 /sbin/modprobe ipmi_si