Exception in main training loop: module 'cupy.cudnn' has no attribute 'pooling_forward'
See original GitHub issueHi, When I run chainer/examples/imagenet/train_imagenet_data_parallel.py, I got this error.
/home/dnn/.pyenv/versions/ymd/bin/python3 /home/dnn/ymd/chainer/examples/imagenet/train_imagenet_data_parallel.py train.txt val.txt
/home/dnn/ymd/chainer/chainer/training/updaters/multiprocess_parallel_updater.py:164: UserWarning: optimizer.lr is changed to 0.00125 by MultiprocessParallelUpdater for new batch size.
format(optimizer.lr))
Exception in main training loop: module 'cupy.cudnn' has no attribute 'pooling_forward'
Traceback (most recent call last):
File "/home/dnn/ymd/chainer/chainer/training/trainer.py", line 315, in run
update()
File "/home/dnn/ymd/chainer/chainer/training/updaters/standard_updater.py", line 165, in update
self.update_core()
File "/home/dnn/ymd/chainer/chainer/training/updaters/multiprocess_parallel_updater.py", line 237, in update_core
loss = _calc_loss(self._master, batch)
File "/home/dnn/ymd/chainer/chainer/training/updaters/multiprocess_parallel_updater.py", line 271, in _calc_loss
return model(*in_arrays)
File "/home/dnn/ymd/chainer/chainer/link.py", line 242, in __call__
out = forward(*args, **kwargs)
File "/home/dnn/ymd/chainer/examples/imagenet/nin.py", line 28, in forward
h = F.max_pooling_2d(F.relu(self.mlpconv1(x)), 3, stride=2)
File "/home/dnn/ymd/chainer/chainer/functions/pooling/max_pooling_2d.py", line 383, in max_pooling_2d
return func.apply((x,))[0]
File "/home/dnn/ymd/chainer/chainer/function_node.py", line 263, in apply
outputs = self.forward(in_data)
File "/home/dnn/ymd/chainer/chainer/function_node.py", line 369, in forward
return self.forward_gpu(inputs)
File "/home/dnn/ymd/chainer/chainer/functions/pooling/max_pooling_2d.py", line 64, in forward_gpu
return super(MaxPooling2D, self).forward_gpu(x)
File "/home/dnn/ymd/chainer/chainer/functions/pooling/pooling_2d.py", line 54, in forward_gpu
cudnn.pooling_forward(
Will finalize trainer extensions and updater before reraising the exception.
Process _Worker-3:
my environment is
- Chainer version: 5.0.0
- CuPy version: 6.0.0a1
- OS/Platform: Ubuntu18.04
- CUDA/cuDNN version 10.0/7.4.1
Any help would be useful, thanks.
Issue Analytics
- State:
- Created 5 years ago
- Comments:12 (10 by maintainers)
Top Results From Across the Web
Chainer module 'cupy.cudnn' has no attribute ...
I have no clue about the problem now. Exception in main training loop: module 'cupy.cudnn' has no attribute 'softmax_forward' Traceback ...
Read more >Developer Guide :: NVIDIA Deep Learning cuDNN ...
cuDNN offers a context-based API that allows for easy multithreading and (optional) interoperability with NVIDIA ® CUDA ® streams. 1.1.
Read more >「module 'cupy.cudnn' has no attribute 'pooling_forward'」 ...
Exception in main training loop : module 'cupy.cudnn' has no attribute 'pooling_forward' Traceback (most recent call last): File ...
Read more >Cupy Attribute error when running Spacy on GPU - usage
I have installed spacy cuda using the below, to train a model using the GPU, and speed things up. pip install -U spacy[cuda92]...
Read more >https://openi.pcl.ac.cn/OpenI/Paddle/commit/e2ca8e...
+# +# Licensed under the Apache License, Version 2.0 (the "License"); +# you may not use this file except in compliance with the...
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 FreeTop 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
Top GitHub Comments
I hope the problem has been resolved, but just a note: Chainer does not prefer any specific Python environment management tools over the others. If you still have an installation problem with pyenv, do not hesitate to reopen it or open a new issue. Thanks!
I apologize that I unintentionally led the reader not to use a specific python environment.
For the compensation, I show a small reproduction code of the situation which reported by @crook52 (i.e. the reason of my inference). I just guessed that something like this might have happened for his situation.