# git rev-parse -q --verify fbe1bf1e5ff1e3b298420d7a8434983ef8d72bd1^{commit}
# git fetch -q -n -f git://fs.ozlabs.ibm.com/kernel/linus master
warning: The last gc run reported the following. Please correct the root cause
and remove .git/gc.log.
Automatic cleanup will not be performed until the file is removed.

warning: There are too many unreachable loose objects; run 'git prune' to remove them.

# git rev-parse -q --verify fbe1bf1e5ff1e3b298420d7a8434983ef8d72bd1^{commit}
fbe1bf1e5ff1e3b298420d7a8434983ef8d72bd1
# git checkout -q -f -B kisskb fbe1bf1e5ff1e3b298420d7a8434983ef8d72bd1
# git clean -qxdf
# < git log -1
# commit fbe1bf1e5ff1e3b298420d7a8434983ef8d72bd1
# Author: Linus Torvalds <torvalds@linux-foundation.org>
# Date:   Sun Oct 15 12:02:02 2023 -0700
# 
#     Revert "x86/smp: Put CPUs into INIT on shutdown if possible"
#     
#     This reverts commit 45e34c8af58f23db4474e2bfe79183efec09a18b, and the
#     two subsequent fixes to it:
#     
#       3f874c9b2aae ("x86/smp: Don't send INIT to non-present and non-booted CPUs")
#       b1472a60a584 ("x86/smp: Don't send INIT to boot CPU")
#     
#     because it seems to result in hung machines at shutdown.  Particularly
#     some Dell machines, but Thomas says
#     
#      "The rest seems to be Lenovo and Sony with Alderlake/Raptorlake CPUs -
#       at least that's what I could figure out from the various bug reports.
#     
#       I don't know which CPUs the DELL machines have, so I can't say it's a
#       pattern.
#     
#       I agree with the revert for now"
#     
#     Ashok Raj chimes in:
#     
#      "There was a report (probably this same one), and it turns out it was a
#       bug in the BIOS SMI handler.
#     
#       The client BIOS's were waiting for the lowest APICID to be the SMI
#       rendevous master. If this is MeteorLake, the BSP wasn't the one with
#       the lowest APIC and it triped here.
#     
#       The BIOS change is also being pushed to others for assimilation :)
#     
#       Server BIOS's had this correctly for a while now"
#     
#     and it does look likely to be some bad interaction between SMI and the
#     non-BSP cores having put into INIT (and thus unresponsive until reset).
#     
#     Link: https://bbs.archlinux.org/viewtopic.php?pid=2124429
#     Link: https://www.reddit.com/r/openSUSE/comments/16qq99b/tumbleweed_shutdown_did_not_finish_completely/
#     Link: https://forum.artixlinux.org/index.php/topic,5997.0.html
#     Link: https://bugzilla.redhat.com/show_bug.cgi?id=2241279
#     Acked-by: Thomas Gleixner <tglx@linutronix.de>
#     Cc: Ashok Raj <ashok.raj@intel.com>
#     Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
# < /opt/cross/kisskb/korg/gcc-13.1.0-nolibc/mips-linux/bin/mips-linux-gcc --version
# < /opt/cross/kisskb/korg/gcc-13.1.0-nolibc/mips-linux/bin/mips-linux-ld --version
# < git log --format=%s --max-count=1 fbe1bf1e5ff1e3b298420d7a8434983ef8d72bd1
# make -s -j 160 ARCH=mips O=/kisskb/build/linus-rand_allnoconfig_mips-gcc13 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-13.1.0-nolibc/mips-linux/bin/mips-linux-  allnoconfig
# < make -s -j 160 ARCH=mips O=/kisskb/build/linus-rand_allnoconfig_mips-gcc13 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-13.1.0-nolibc/mips-linux/bin/mips-linux-  help
# make -s -j 160 ARCH=mips O=/kisskb/build/linus-rand_allnoconfig_mips-gcc13 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-13.1.0-nolibc/mips-linux/bin/mips-linux-  olddefconfig
# make -s -j 160 ARCH=mips O=/kisskb/build/linus-rand_allnoconfig_mips-gcc13 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-13.1.0-nolibc/mips-linux/bin/mips-linux-  
Completed OK
# rm -rf /kisskb/build/linus-rand_allnoconfig_mips-gcc13
# Build took: 0:00:25.464491