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

Distance-1 graph coloring segfault #275

Closed
brian-kelley opened this issue Jul 25, 2018 · 5 comments
Closed

Distance-1 graph coloring segfault #275

brian-kelley opened this issue Jul 25, 2018 · 5 comments
Assignees

Comments

@brian-kelley
Copy link
Contributor

The graph coloring done when initializing MT Gauss-Seidel sometimes segfaults when processing a graph from Drekar (24K rows/cols, 5.6M entries), especially with a high number of OpenMP threads (seems to happen about 80% of the time with 64 threads on a KNL with this particular graph). The graph and a unit test to replicate the crash are here - coloring is run in unit_test/KokkosKernels_graph_openmp.exe by the test called "BMK_replicate_color_crash". The test verifies that the graph is actually symmetric and that all entries are in the valid range 0...numRows-1. When the test succeeds, the graph is colored using around 96 colors.

I'm using kokkos d6e8d32 and kokkos-kernels e463b6e (both up-to-date from develop branches). The graph coloring handle is created with all default settings.

@lucbv lucbv added the bug label Aug 20, 2018
@lucbv
Copy link
Contributor

lucbv commented Aug 20, 2018

@brian-kelley is this still happening?

@brian-kelley
Copy link
Contributor Author

@lucbv I just ran the crash replication test with the newest kokkos/kokkos-kernels and it's still happening. Also, the crash replication branch is now rebased on the current kokkos-kernels develop.

@srajama1
Copy link
Contributor

@lucbv : Do you have time to look at this. It would be nice to fix it before next update.

@srajama1
Copy link
Contributor

@brian-kelley just fixed this in #451 .. Thanks, Brian !

@srajama1
Copy link
Contributor

We don't close till the changes are in master, when we do the master + Trilinos integration we will close all "InDevelop" issues.

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

No branches or pull requests

4 participants