On Tuesday, 27 August 2019 09:33:39 CEST Anilkumar Kolli wrote: [...] > > [ 4312.884650] The reading for sensor 4 is 0x002041f7 > > [ 4312.891499] The reading for sensor 5 is 0x002051f4 > > [ 4312.896415] Couldn't get reading for sensor 6 > > [ 4312.901189] Couldn't get reading for sensor 7 > > [ 4312.905561] The reading for sensor 8 is 0x002081e0 > > [ 4312.909902] The reading for sensor 9 is 0x002091f7 > > [ 4312.914645] Couldn't get reading for sensor 10 > > [ 4312.919364] The reading for sensor 11 is 0x0020b1fa > > [ 4312.923791] The reading for sensor 12 is 0x0020c1fa > > [ 4312.928621] Couldn't get reading for sensor 13 > > [ 4312.933425] The reading for sensor 14 is 0x0020e1f4 > > [ 4312.937941] The reading for sensor 15 is 0x0020f1e7 > > [ 4313.942700] Rebooting in 3 seconds.. > > > > Maybe can be fixed by a different kernel (for the remoteproc). But I > > don't > > have this kernel at the moment. > > > > The write of an "assert", sends 'WMI_FORCE_FW_HANG_CMDID' WMI command to > target firmware. > This WMI command forces the target to assert. Yes, but it shouldn't kill the complete system. Kind regards, Sven
Attachment:
signature.asc
Description: This is a digitally signed message part.
