You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This appears like it might be an aspeed fsi scom driver issue because accessing the exact same scom address from the sbefifo backend works correctly. Compare a pdbg threadstatus command on a thread on p3 between sbefifo and default backends:
The successful case (SBE FIFO op PIB driver): kernel_fsi_probe open(/sys/class/fsi-master/fsi0/slave@00:00/raw)=4 kernel_fsi_probe open(/sys/class/fsi-master/fsi1/slave@03:00/raw)=5 Translating target addr 0xf0040 -> 0x200f0040 on /proc3/pib pib_read[153]: rc = 0, addr = 0x00000000200f0040, data = 0xbc20000000000000, target = /proc3/pib
Failing case (kernel SCOM driver): kernel_fsi_probe open(/sys/class/fsi-master/fsi0/slave@00:00/raw)=4 PIB open (/dev/scom4) = 5 Translating target addr 0xf0040 -> 0x200f0040 on /proc3/pib kernel_pib_getscom fd=5 kernel_pib_getscom[226]: Failed to read scom addr 0x00000000200f0040 pib_read[153]: rc = 1, addr = 0x00000000200f0040, data = 0x007683e801000000, target = /proc3/pib
The text was updated successfully, but these errors were encountered:
This appears like it might be an aspeed fsi scom driver issue because accessing the exact same scom address from the sbefifo backend works correctly. Compare a pdbg threadstatus command on a thread on p3 between sbefifo and default backends:
The successful case (SBE FIFO op PIB driver):
kernel_fsi_probe open(/sys/class/fsi-master/fsi0/slave@00:00/raw)=4 kernel_fsi_probe open(/sys/class/fsi-master/fsi1/slave@03:00/raw)=5 Translating target addr 0xf0040 -> 0x200f0040 on /proc3/pib pib_read[153]: rc = 0, addr = 0x00000000200f0040, data = 0xbc20000000000000, target = /proc3/pib
Failing case (kernel SCOM driver):
kernel_fsi_probe open(/sys/class/fsi-master/fsi0/slave@00:00/raw)=4 PIB open (/dev/scom4) = 5 Translating target addr 0xf0040 -> 0x200f0040 on /proc3/pib kernel_pib_getscom fd=5 kernel_pib_getscom[226]: Failed to read scom addr 0x00000000200f0040 pib_read[153]: rc = 1, addr = 0x00000000200f0040, data = 0x007683e801000000, target = /proc3/pib
The text was updated successfully, but these errors were encountered: