Chia Pos Plotting Error?

Support
1

Issue Report

Environment

  • Operating System:
  • Pulsar/Advanced CLI/Docker:
    Ubuntu 23.04
    Docker gemini-3g-2023-oct-31

Problem

subspace-farmer-all2  | 2023-11-05T14:59:24.706955Z  INFO single_disk_farm{disk_farm_index=1}: subspace_farmer::single_disk_farm::plotting: Plotting sector (54.64% complete) sector_index=153
subspace-farmer-all2  | 2023-11-05T14:59:39.570109Z  INFO single_disk_farm{disk_farm_index=0}: subspace_farmer::single_disk_farm::plotting: Plotting sector (54.29% complete) sector_index=152
subspace-farmer-all2  | 2023-11-05T15:11:55.301771Z  INFO single_disk_farm{disk_farm_index=1}: subspace_farmer::single_disk_farm::plotting: Plotting sector (55.00% complete) sector_index=154
subspace-farmer-all2  | 2023-11-05T15:12:18.779485Z  INFO single_disk_farm{disk_farm_index=0}: subspace_farmer::single_disk_farm::plotting: Plotting sector (54.64% complete) sector_index=153
subspace-farmer-all2  | thread 'plotting-0.21' panicked at crates/subspace-proof-of-space/src/chiapos/table.rs:305:49:
subspace-farmer-all2  | index out of bounds: the len is 15113 but the index is 60523
subspace-farmer-all2  | note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
subspace-farmer-all2  | thread 'plotting-0.21' panicked at crates/subspace-proof-of-space/src/chiapos/table.rs:305:49:
subspace-farmer-all2  | index out of bounds: the len is 15113 but the index is 18446744073709535971
subspace-farmer-all2  | Error: Background task plotting-0 panicked

Screenshot 2023-11-05 at 22.25.33
Screenshot 2023-11-05 at 22.25.331666×414 117 KB

2

Most likely you have memory issues: defective modules, unstable XML, etc.
That error can’t happen on stable computer.

I have seen it myself and had to increase DDR4 voltage to fix ASUS-optimized XMP profile.

Turns out Subspace is a good memory stability test, memtest64 wasn’t able to find issues for me, while Subspace did.

1 Like
3

I Use Intel 13700k
And DRAM RAM Corsair Dominator Platinum 64GB (2x32GB) RGB 5600 DDR5 (CMT64GX5M2B5600C40)
With XMP enabled

Handle 0x000E, DMI type 17, 92 bytes
Memory Device
	Array Handle: 0x000C
	Error Information Handle: Not Provided
	Total Width: 64 bits
	Data Width: 64 bits
	Size: 32 GB
	Form Factor: DIMM
	Set: None
	Locator: Controller0-DIMM1
	Bank Locator: BANK 0
	Type: DDR5
	Type Detail: Synchronous
	Speed: 5600 MT/s
	Manufacturer: Corsair
	Serial Number: 00000000
	Asset Tag: 9876543210
	Part Number: CMT64GX5M2B5600C40
	Rank: 2
	Configured Memory Speed: 5600 MT/s
	Minimum Voltage: 1.1 V
	Maximum Voltage: 1.25 V
	Configured Voltage: 1.1 V
	Memory Technology: DRAM
	Memory Operating Mode Capability: Volatile memory
	Firmware Version: Not Specified
	Module Manufacturer ID: Bank 3, Hex 0x9E
	Module Product ID: Unknown
	Memory Subsystem Controller Manufacturer ID: Unknown
	Memory Subsystem Controller Product ID: Unknown
	Non-Volatile Size: None
	Volatile Size: 32 GB
	Cache Size: None
	Logical Size: None
4

Then your XMP is unstable.

If you’re using ASUS board make sure to use XMP II (one that is flashed in the memory module) rather than XMP I (where ASUS tweaks some parameters and can cause instability).

Otherwise consider bumping a voltage a bit (do your research about how much is actually safe) or dial down XMP.

Either way this is not a bug in Subspace implementation, but rather a hardware issue.

1 Like
5

I think so, too. because orther pc not error