On entry to GEMM_EX parameter number {9,12} had an illegal value
See original GitHub issueWhen I try to run my jax-based training script on the GPU, it prints the following messages several hundred times but proceeds without an exception.
** On entry to GEMM_EX parameter number 12 had an illegal value
** On entry to GEMM_EX parameter number 9 had an illegal value
The same script doesn’t print any errors when run with a CPU-only build. This error occurs with the pip build and a custom build of master.
To reproduce, run python jax_transformer.py alice.txt
in https://github.com/joschu/jax-exp/
Issue Analytics
- State:
- Created 5 years ago
- Comments:16 (16 by maintainers)
Top Results From Across the Web
On entry to DLASCLS parameter number 4 had an illegal value
Many places on google they say it is because the shape of your input data is not good. My code : %defining variables...
Read more >On entry to DGEMV parameter number 6 had an illegal value
On entry to DGEMV parameter number 6 had an illegal value ... BLAS has a terrible model for error handling; it just prints...
Read more >On entry to DGEMM parameter number 10 had an illegal value
Hi, I'm running a ground state simulation of Heisenberg XYZ model, using a slightly modified boundary condition, in which the XX, ...
Read more >LAPACK dgeev: parameter had illegal value - Physics Forums
On entry to DGEEV parameter number 9 had an illegal value. EDIT: The error occurs in the call of degeev spanning lines 48...
Read more >Fontana Aviation, Inc. v. Beech Aircraft, 432 F.2d 1080
Fontana had been a Beechcraft dealer since 1946. ... illegal demonstrator and stocking requirements were imposed on independent dealers and ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The GEMM_EX problem is now tracked at https://github.com/tensorflow/tensorflow/issues/25761
I think this happens during GEMM autotuning. It may be benign because eventually XLA gives up and uses a generic GEMM, which seems to work:
Snippet from a log (with
TF_CPP_MIN_VLOG_LEVEL=2
set)