thread '<unnamed>' panicked at 'GPU FFT failed!

[810106148]

Describe the bug
A clear and concise description of what the bug is.

Intel® Xeon(R) CPU E5-2697 v2 @ 2.70GHz × 48
llvmpipe (LLVM 6.0, 256 bits)
gtx 2070

To Reproduce
Steps to reproduce the behavior:

1. Run ' lotus-storage-miner run'

2. Run ' lotus-storage-miner pledge-sector '

3. See error
   :13:58.747+0800 INFO sectors sealing/garbage.go:39 Pledge 2, contains []
   ^[[A2020-04-15T22:40:32.966+0800 INFO sectors sealing/garbage.go:63 Publishing deals for 2
   2020-04-15T22:42:01.684+0800 INFO sectors sealing/garbage.go:99 Deals for sector 2: [1193714]
   2020-04-15T23:02:23.153+0800 INFO sectors sealing/sealing.go:124 Start sealing 2
   2020-04-15T23:02:23.292+0800 INFO sectors sealing/states.go:17 performing filling up rest of the sector... {"sector": 2}
   2020-04-15T23:02:23.347+0800 INFO sectors sealing/states.go:62 performing sector replication... {"sector": 2}
   2020-04-16T03:59:58.679+0800 INFO sectors sealing/states.go:120 submitting precommit for sector: 2
   2020-04-16T03:59:58.790+0800 INFO sectors sealing/states.go:131 Sector precommitted: 2
   2020-04-16T04:01:31.595+0800 INFO sectors sealing/states.go:142 precommit message landed on chain: 2
   2020-04-16T04:01:31.596+0800 INFO sectors sealing/states.go:145 precommit for sector 2 made it on chain, will start proof computation at height 178169
   2020-04-16T04:07:31.252+0800 WARN sectors sealing/states.go:163 revert in interactive commit sector step
   2020-04-16T04:07:31.667+0800 WARN sectors sealing/states.go:163 revert in interactive commit sector step
   2020-04-16T04:12:01.440+0800 INFO sectors sealing/states.go:175 scheduling seal proof computation...
   thread '' panicked at 'GPU FFT failed!: GPUError { msg: "\n\n################################ OPENCL ERROR ############################### \n\nError executing function: clEnqueueNDRangeKernel("radix_fft") \n\nStatus error code: CL_MEM_OBJECT_ALLOCATION_FAILURE (-4) \n\nPlease visit the following url for more information: \n\nhttps://www.khronos.org/registry/cl/sdk/1.2/docs/man/xhtml/clEnqueueNDRangeKernel.html#errors \n\n############################################################################# \n" }', src/libcore/result.rs:1165:5
   note: run with RUST_BACKTRACE=1 environment variable to display a backtrace.
   thread '' panicked at 'GPU FFT failed!: GPUError { msg: "\n\n################################ OPENCL ERROR ############################### \n\nError executing function: clEnqueueNDRangeKernel("radix_fft") \n\nStatus error code: CL_MEM_OBJECT_ALLOCATION_FAILURE (-4) \n\nPlease visit the following url for more information: \n\nhttps://www.khronos.org/registry/cl/sdk/1.2/docs/man/xhtml/clEnqueueNDRangeKernel.html#errors \n\n############################################################################# \n" }', src/libcore/result.rs:1165:5
   thread '' panicked at 'GPU FFT failed!: GPUError { msg: "\n\n################################ OPENCL ERROR ############################### \n\nError executing function: clEnqueueNDRangeKernel("radix_fft") \n\nStatus error code: CL_MEM_OBJECT_ALLOCATION_FAILURE (-4) \n\nPlease visit the following url for more information: \n\nhttps://www.khronos.org/registry/cl/sdk/1.2/docs/man/xhtml/clEnqueueNDRangeKernel.html#errors \n\n############################################################################# \n" }', src/libcore/result.rs:1165:5
   thread '' panicked at 'GPU FFT failed!: GPUError { msg: "\n\n################################ OPENCL ERROR ############################### \n\nError executing function: clEnqueueNDRangeKernel("radix_fft") \n\nStatus error code: CL_MEM_OBJECT_ALLOCATION_FAILURE (-4) \n\nPlease visit the following url for more information: \n\nhttps://www.khronos.org/registry/cl/sdk/1.2/docs/man/xhtml/clEnqueueNDRangeKernel.html#errors \n\n############################################################################# \n" }', src/libcore/result.rs:1165:5
   thread '' panicked at 'GPU FFT failed!: GPUError { msg: "\n\n################################ OPENCL ERROR ############################### \n\nError executing function: clEnqueueNDRangeKernel("radix_fft") \n\nStatus error code: CL_MEM_OBJECT_ALLOCATION_FAILURE (-4) \n\nPlease visit the following url for more information: \n\nhttps://www.khronos.org/registry/cl/sdk/1.2/docs/man/xhtml/clEnqueueNDRangeKernel.html#errors \n\n############################################################################# \n" }', src/libcore/result.rs:1165:5
   thread '' panicked at 'GPU FFT failed!: GPUError { msg: "\n\n################################ OPENCL ERROR ############################### \n\nError executing function: clEnqueueNDRangeKernel("radix_fft") \n\nStatus error code: CL_MEM_OBJECT_ALLOCATION_FAILURE (-4) \n\nPlease visit the following url for more information: \n\nhttps://www.khronos.org/registry/cl/sdk/1.2/docs/man/xhtml/clEnqueueNDRangeKernel.html#errors \n\n############################################################################# \n" }', src/libcore/result.rs:1165:5
   2020-04-16T05:14:25.754+0800 WARN sectorbuilder go-sectorbuilder@v0.0.2-0.20200203173614-42d67726bb62/sectorbuild_cgo.go:304 StandaloneSealCommit error: Rust panic: no unwind information
   2020-04-16T05:14:25.755+0800 WARN sectorbuilder go-sectorbuilder@v0.0.2-0.20200203173614-42d67726bb62/sectorbuild_cgo.go:305 sid:2 tkt:{177763 [17 23 248 120 93 52 40 55 178 24 179 169 211 127 243 44 207 4 60 247 94 188 38 101 40 245 11 58 185 3 159 154]} seed:{178169 [60 6 176 5 155 118 83 156 76 247 198 184 174 51 109 83 196 223 191 50 4 240 105 200 244 230 142 68 107 50 187 86]}, ppi:[{34091302912 [154 251 227 206 201 45 238 103 12 124 57 129 139 40 157 216 112 120 12 65 94 94 249 116 27 240 51 48 162 227 53 38]}] rspco:{[154 251 227 206 201 45 238 103 12 124 57 129 139 40 157 216 112 120 12 65 94 94 249 116 27 240 51 48 162 227 53 38] [32 237 41 204 62 120 153 19 222 118 128 228 226 253 212 208 208 167 172 114 35 214 7 50 214 32 19 179 100 77 96 106]}
   2020-04-16T05:14:25.756+0800 WARN sectors sealing/fsm.go:169 sector 2 entered unimplemented state 'SealCommitFailed'

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Version (run lotus --version):
lotus version 0.2.8+git1120298

Additional context
Add any other context about the problem here.

[whyrusleeping]

I think this has been resolved, please open a new issue if it happens again