I updated titan's kernel to the latest available as of today and it does not give that error again.