Skip to content
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

Getting "Floating point exception (core dumped)" Error #687

Open
alvins82 opened this issue Jul 15, 2024 · 4 comments
Open

Getting "Floating point exception (core dumped)" Error #687

alvins82 opened this issue Jul 15, 2024 · 4 comments

Comments

@alvins82
Copy link

alvins82 commented Jul 15, 2024

Playing around with re-creating GPT-2 from the thread. When I run train I get the above error. Screenshot below.

Screenshot 2024-07-15 at 8 18 51 pm Screenshot 2024-07-15 at 8 20 14 pm Screenshot 2024-07-15 at 8 25 58 pm
@diegoasua
Copy link

diegoasua commented Jul 15, 2024

No idea what is going on but maybe try compiling without CuDNN make train_gpt2cu USE_CUDNN=0. Probably not the cause, but just to check. Also run the tests see if they pass

# fp32 test (cudnn not supported)
make test_gpt2cu PRECISION=FP32 && ./test_gpt2cu
# mixed precision cudnn test
make test_gpt2cu USE_CUDNN=1 && ./test_gpt2cu

@alvins82
Copy link
Author

No idea what is going on but maybe try compiling without CuDNN make train_gpt2cu USE_CUDNN=0. Probably not the cause, but just to check. Also run the tests see if they pass

# fp32 test (cudnn not supported)
make test_gpt2cu PRECISION=FP32 && ./test_gpt2cu
# mixed precision cudnn test
make test_gpt2cu USE_CUDNN=1 && ./test_gpt2cu

Both of the tests pass. Also put a screenshot of my torch versions above.

@alvins82
Copy link
Author

No idea what is going on but maybe try compiling without CuDNN make train_gpt2cu USE_CUDNN=0. Probably not the cause, but just to check. Also run the tests see if they pass

# fp32 test (cudnn not supported)
make test_gpt2cu PRECISION=FP32 && ./test_gpt2cu
# mixed precision cudnn test
make test_gpt2cu USE_CUDNN=1 && ./test_gpt2cu
Screenshot 2024-07-15 at 8 29 06 pm

@gordicaleksa
Copy link
Contributor

eyeballing your cmdline i'd say your batch size is too small and is causing an exception in the hellaswag eval, this is a known issue and we have a patch merged into master that basically forces you to use batch size >= 4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants