Closed gopherbot closed 4 years ago
Change https://golang.org/cl/221058 mentions this issue: [release-branch.go1.14] runtime: guard VZEROUPPER on CPU feature
It also affects 10.13.6 (High Sierra)
@UrbanLegend I think you might be confusing macOS versions with Go versions. This issue should not depend on the macOS version at all. It just requires Go 1.14 and an old processor.
Approving per discussion in a release meeting because this is a serious issue without a workaround.
/cc @cagedmantis @toothrot
My configuration is having this problem. Here is the hardware and OS information:
System Version: macOS 10.14.6 (18G3020) Kernel Version: Darwin 18.7.0 Model Name: Mac Pro Model Identifier: MacPro5,1 Processor Name: Quad-Core Intel Xeon Processor Speed: 2.26 GHz Number of Processors: 2 Total Number of Cores: 8 L2 Cache (per Core): 256 KB L3 Cache (per Processor): 8 MB Hyper-Threading Technology: Enabled Memory: 64 GB Boot ROM Version: 144.0.0.0.0
Chirping in with essentially the same config as @Jonconradt, except my Boot ROM is 138.0.0.0.0.
@cherrymui This issue has been approved. Feel free to merge when you have the opportunity.
@cagedmantis I don't think I have permission to submit to the release branch. I'll have to let you or the release team do that. Thanks.
@cherrymui Sorry for the confusion.
Closed by merging c54e36905b394dea9fbcf816c3a6e6751187258d to release-branch.go1.14.
hi
i have same probleme but i can't see any solution :(
The fix will be released when Go 1.14.1 comes out. For now, you will have to wait (or build a Go distribution for yourself, from tip or with the patch above applied to 1.14).
@randall77 i'm so sorry, how can i build or patch this ?
many thanks
Something like:
git clone https://go.googlesource.com/go goroot
cd goroot
git checkout go1.14
git cherry-pick c54e36905b394dea9fbcf816c3a6e6751187258d
cd src
./make.bash
hi @randall77
thank you for your help, i apply this but this issue not fix my problem.
i can't run hugo 0.66.0
@Shurikken From your log, it looks like the go
binary that was in your PATH
was still Go 1.14. Note that there are many mentions of /usr/local/Cellar/go/1.14
in your output.
It's possible the problem was that you didn't add the newly built go
binary to your PATH after the ./make.bash
step in the instructions @randall77 provided. Try this:
git clone https://go.googlesource.com/go gotip
cd gotip
git checkout go1.14
git cherry-pick c54e36905b394dea9fbcf816c3a6e6751187258d
cd src
./make.bash
export PATH="$(../bin/go env GOROOT)/bin:$PATH"
which go
which go
should point to the go
binary that was built in gotip/bin
. Then, in the same terminal (to preserve the new PATH
environment variable value), you can try go get github.com/gohugoio/hugo@v0.66.0
and see if that helps.
Thank you for helping confirm that this patch will fix the problem in the upcoming Go 1.14.1 release.
@dmitshur hi
i have problem when use cd src ./make.bash :
MacBook-de-user:src acountuser$ ./make.bash
./make.bash: line 165: /Users/acountuser/go1.4/bin/go: No such file or directory
Building Go cmd/dist using /Users/acountuser/go1.4. ()
ERROR: Cannot find /Users/acountuser/go1.4/bin/go.
Set $GOROOT_BOOTSTRAP to a working Go tree >= Go 1.4.
MacBook-de-valentin:src acountuser$ export PATH="$(../bin/go env GOROOT)/bin:$PATH"
-bash: ../bin/go: No such file or directory
MacBook-de-valentin:src acountuser$ which go
MacBook-de-valentin:src acountuser$
I see, the ./make.bash
step failed because /Users/acountuser/go1.4/bin/go
did not exist.
In order to run ./make.bash
, you need to have another Go installation (any recent version that works for you) and set the GOROOT_BOOTSTRAP
environment variable to point to it. Please see https://golang.org/doc/install/source#go14 for full details on this.
The line number here:
/usr/local/Cellar/go/1.14/libexec/src/runtime/preempt_amd64.s:8 fp=0xc000169720 sp=0xc000169718 pc=0x406a670
corroborates the fact that you are still running a vanilla 1.14, not a patched one.
Excuse me i'm newby.... :( i use your solution and apply your code but when i use ./make.bash i have error code... i have go installation i don't understand why :(
Show us. It's hard to debug for you when we can't see what you're doing. Copy-paste your entire shell session here.
Perhaps you can just wait until 1.14.1 comes out.
@dmitshur do we have a timeline for the release of 1.14.1?
@apriendeau We are actively making progress on the work that is necessary to get Go 1.14.1 and 1.13.9 releases out. I don't know the exact day it'll happen, but we're aiming to do it soon. /cc @toothrot @cagedmantis
Method of resolving this if you have go installed using brew:
brew uninstall go && brew uninstall hugo
Then
brew install go && brew install hugo
This will remove an old version of go from your machine, then uninstall hugo compiled with that old version, then reinstall go at 1.14, then reinstall hugo which will compile it with 1.14. Easy peazy.
Did brew patch the CL that fixes this issue into their Go 1.14? Because 1.14.1 with that CL is not out yet.
Method of resolving this if you have go installed using brew:
I just tried this and it didn't work.
Did brew patch the CL that fixes this issue into their Go 1.14?
Sooooooo ... no? :)
(P.S. Hi, @dmitshur! 👋 What interesting timing, this is my first time trying hugo. 😁)
To revert a brew
based install of Go to v1.13.8:
brew uninstall go
brew install go@1.13
echo 'export PATH="/usr/local/opt/go@1.13/bin:$PATH"' >> ~/.bash_profile
brew pin go@1.13
To unpin and permit brew
to update to the latest go
:
brew unpin go@1.13
…and remove the previously inserted line from ~/.bash_profile
.
@apriendeau We are actively making progress on the work that is necessary to get Go 1.14.1 and 1.13.9 releases out. I don't know the exact day it'll happen, but we're aiming to do it soon. /cc @toothrot @cagedmantis
Any updates on a go1.14.1 release?
go1.14.1 is out and has a fix for this issue.
For the record, all Go releases are announced on the low-volume golang-announce mailing list. For 1.14.1, see https://groups.google.com/d/msg/golang-announce/Ix2U_8WWmXo/a2nJkNW5AAAJ.
@dmitshur requested issue #37459 to be considered for backport to the next 1.14 minor release.