-
Notifications
You must be signed in to change notification settings - Fork 31.6k
Pooling throws an exception in Tegra TX1 #1906
Copy link
Copy link
Closed
Labels
high prioritymodule: crashProblem manifests as a hard crash, as opposed to a RuntimeErrorProblem manifests as a hard crash, as opposed to a RuntimeErrormodule: nnRelated to torch.nnRelated to torch.nnneeds reproductionEnsure you have actionable steps to reproduce the issue. Someone else needs to confirm the repro.Ensure you have actionable steps to reproduce the issue. Someone else needs to confirm the repro.triagedThis issue has been looked at a team member, and triaged and prioritized into an appropriate moduleThis issue has been looked at a team member, and triaged and prioritized into an appropriate module
Description
Activity
Metadata
Metadata
Assignees
Labels
high prioritymodule: crashProblem manifests as a hard crash, as opposed to a RuntimeErrorProblem manifests as a hard crash, as opposed to a RuntimeErrormodule: nnRelated to torch.nnRelated to torch.nnneeds reproductionEnsure you have actionable steps to reproduce the issue. Someone else needs to confirm the repro.Ensure you have actionable steps to reproduce the issue. Someone else needs to confirm the repro.triagedThis issue has been looked at a team member, and triaged and prioritized into an appropriate moduleThis issue has been looked at a team member, and triaged and prioritized into an appropriate module
Hi all, great work with pytorch. I'm trying to use pytorch in a Jetson TX1, but running into some issues. One of them is pretty simple: pooling doesn't seem to work.
First, some details:
Currently compiling the 0.1.12 tag - will update when done.Tag 1.12 (ccdf54) actually works correctly, with and without cuda.Here's a simple example:
when using MaxPool2d, I get
when using AvgPool2d, oddly I get a different error:AvgPool2d works as expected.Since I'm not too experienced with the internals, I'm not sure what changes matter, but I changed a few things (using cuda or cpu, volatile or not, the tensor size, the pooling parameters) and always got the same result. As a very very approximate workaround I've been using extra striding in my convolutions, but obviously that's not ideal ;).