-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jax crashes on TPU in version 0.3.19 #12550
Comments
update: it seems that the problem has to do with version
|
The issue is that the new Another workaround for now is to install the new
I'm working on a new release with a fix. |
@dluo96 Does that happen outside of a docker container? I think that issue is specifically related to docker. |
@hawkinsp the problem happens outside docker for me, but jax This is my repro on v2-32 in case it helps:
Running Python 3.9.12 in my case. |
@pcuenca That doesn't sound like the same issue reported in the first post of this issue. |
@hawkinsp Sorry, I assumed it was the same because the behaviour is similar and affects the same version. I can open a new issue with any details you need, no problem :) |
Hi @hawkinsp, thanks for looking into this. I tested this with the same version of Docker (
|
This should be fixed by jax/jaxlib v0.3.20 which we just released. Hope that helps! |
That solved it for me, thank you so much @hawkinsp! 🚀 |
Description
Hi,
I installed Jax on a TPU V3-8:
However, when running Jax, I get the following error.
I've tried both reinstalling Jax and create a new TPU V3-8, but I get the exact same error.
Running
jax.devices()
does show the TPUs I have on the VMThe problem seems to be related to the execution of Jax on the TPU. If I replicate @mattjj's code in this issue, I'm able to run Jax on the cpu-defined function, but not the tpu-defined one.
What jax/jaxlib version are you using?
jax 0.3.19 / jaxlib 0.3.15
Which accelerator(s) are you using?
TPU
Additional system info
No response
NVIDIA GPU info
No response
The text was updated successfully, but these errors were encountered: