summaryrefslogtreecommitdiffstats
path: root/usr.bin/tmux/key-bindings.c
diff options
context:
space:
mode:
authorbcook <bcook@openbsd.org>2019-05-10 16:44:36 +0000
committerbcook <bcook@openbsd.org>2019-05-10 16:44:36 +0000
commit1109d94f0ca1f0d81aa692e5552b1330a71e2b91 (patch)
tree8b29300a93318b4af7bcb2a7ad2a3de01a205522 /usr.bin/tmux/key-bindings.c
parentEnable the test on octeon. Ignore the fact that the test cannot work (diff)
downloadwireguard-openbsd-1109d94f0ca1f0d81aa692e5552b1330a71e2b91.tar.xz
wireguard-openbsd-1109d94f0ca1f0d81aa692e5552b1330a71e2b91.zip
Explicitly disable BCM4331 chips present in 2011-2012 Apple Mac systems.
The Mac EFI firmware enables the wireless controller, but does not disable it, so it continues to receive packets and signal interrupts. This was originally seen as an interrupt storm that consumes about 50% of CPU0 on affected machines. The issue was originally discovered in 2012 by Matthew Garret with a partial fix in Grub, then Lukas Wunner added a fix for the Linux kernel in 2016. This piggy-backs on the most-related driver (bwi) for the purpose of detection and mapping the control registers, but does not actually register the driver if the affected chip is detected. See this archived discussion for further analysis of the bug: https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1165355.html ok kettenis stsp
Diffstat (limited to 'usr.bin/tmux/key-bindings.c')
0 files changed, 0 insertions, 0 deletions