Hi,
I'm running Truenas Scale 22-12-RC1 with motherboard ASRock X570M Pro4. Truenas Scale crashes many time a day with the broken BIOS message. Please see below?
Nov 28 04:28:51 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 28 04:43:26 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 28 04:57:03 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 28 09:23:53 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 28 16:58:59 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 28 21:45:01 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 29 02:10:25 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 29 02:26:05 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 29 02:32:26 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 29 02:38:16 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 29 02:44:10 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 29 02:58:29 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 29 03:04:26 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS
Nov 29 03:10:12 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 29 03:16:01 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 29 03:31:38 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 29 03:49:20 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 29 04:03:55 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS
Nov 29 04:09:49 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 29 04:26:19 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 29 04:32:23 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS
Nov 29 04:46:07 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
The hardware in question is as follow:
*-generic:1
description: Encryption controller
product: Starship/Matisse Cryptographic Coprocessor PSPCPP
vendor: Advanced Micro Devices, Inc. [AMD]
physical id: 0.1
bus info: pci@0000:0d:00.1
version: 00
width: 32 bits
clock: 33MHz
capabilities: pm pciexpress msi msix bus_master cap_list
configuration: driver=ccp latency=0
resources: irq:144 memory:fc300000-fc3fffff memory:fc408000-fc409fff
I have reapplied the firmware but I'm still getting the error message. Is the BIOS truely broken or is it something else? Please advise?
Thanks,
James
I'm running Truenas Scale 22-12-RC1 with motherboard ASRock X570M Pro4. Truenas Scale crashes many time a day with the broken BIOS message. Please see below?
Nov 28 04:28:51 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 28 04:43:26 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 28 04:57:03 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 28 09:23:53 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 28 16:58:59 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 28 21:45:01 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 29 02:10:25 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 29 02:26:05 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 29 02:32:26 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 29 02:38:16 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 29 02:44:10 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 29 02:58:29 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 29 03:04:26 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS
Nov 29 03:10:12 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 29 03:16:01 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 29 03:31:38 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 29 03:49:20 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 29 04:03:55 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS
Nov 29 04:09:49 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 29 04:26:19 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 29 04:32:23 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS
Nov 29 04:46:07 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
The hardware in question is as follow:
*-generic:1
description: Encryption controller
product: Starship/Matisse Cryptographic Coprocessor PSPCPP
vendor: Advanced Micro Devices, Inc. [AMD]
physical id: 0.1
bus info: pci@0000:0d:00.1
version: 00
width: 32 bits
clock: 33MHz
capabilities: pm pciexpress msi msix bus_master cap_list
configuration: driver=ccp latency=0
resources: irq:144 memory:fc300000-fc3fffff memory:fc408000-fc409fff
I have reapplied the firmware but I'm still getting the error message. Is the BIOS truely broken or is it something else? Please advise?
Thanks,
James