summaryrefslogtreecommitdiff
path: root/releasenotes/notes/implement-policy-in-code-cbb0216ef5f8224f.yaml
diff options
context:
space:
mode:
authorJulia Kreger <juliaashleykreger@gmail.com>2023-04-26 07:34:29 -0700
committerJulia Kreger <juliaashleykreger@gmail.com>2023-04-26 07:34:29 -0700
commitf2605e928136f88032ef9b4977a076d5c535987b (patch)
tree36024a640a37fd97ea7c1ab87d7a9035d0d602ef /releasenotes/notes/implement-policy-in-code-cbb0216ef5f8224f.yaml
parent7083545731a8d5009f113f87b07710be833b627a (diff)
downloadironic-f2605e928136f88032ef9b4977a076d5c535987b.tar.gz
Remove use of nomodeset by default
The troubleshooting kernel command line option nomodeset unfortunately changes the way framebuffer interactions work with graphics devices which in some cases can result in kernel memory to be used for graphics updates. When this happens on some specific hardware common in rack mount servers with baseboard management controllers, this can cause the memory bus to become locked for a brief time while the graphics update is occuring. This locked memory bus means disk IO can become blocked, and network cards can overflow their buffers resulting in packet loss on top of the latency incurred by the graphics update executing. As such, we've removed the nomodeset option from default usage and added a note describing its removal to the documentation along with a release note. Change-Id: I9084d88c3ec6f13bd64b8707892758fa87dd7f86
Diffstat (limited to 'releasenotes/notes/implement-policy-in-code-cbb0216ef5f8224f.yaml')
0 files changed, 0 insertions, 0 deletions