Reply 400 of 1037, by CoffeeOne
red-ray wrote on 2020-03-08, 16:14:OK and it's much as I expected. I suspect the HP software was active when you did this and if the HP software is inactive is the […]
CoffeeOne wrote on 2020-03-08, 14:49:OK, kernel logging was simply disabled, so I had to click on the icon, that was all that was missing.
OK and it's much as I expected. I suspect the HP software was active when you did this and if the HP software is inactive is the retry rate lower?
- When act starts with 3x this is some other entity reading the DIMM temperature and the first 4 are when SIV is reading the SPD data.
- When act starts with E8 this is some other entity switching the PCA9544 mux
- When act starts with C8 this is some other entity accessing salve 0x60 memory buffer
- When act starts with C9 this is some other entity accessing salve 0x61 memory buffer
It would be interesting to get a driver log when all the HP software is inactive to see if any of the above go away.
I am also wondering if the HP software uses any locks. From Menu->Windows->Processes Right/Click on the PID button and select Locks to find out. Attached is what I just got for SIV64X so you know what to expect.
Hello,
I made some screenshots while all HP services were running:
HP service cisserv -> locks
HP service fio-agent -> locks
HP service fio-msrv -> locks
HP service ProliantMonitor -> locks
and last but not least SIV -> locks