Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
Mikael_Trosell
Participant

Error message in /var/log/messages after upgrade to R81.20

I upgraded a TE1000X box from R81.10 to R81.20 It seems to work fine except for one problem.

In /var/log/messages there is a large amount of log messages of this type.

Sep 27 14:30:15 2023 FW-TE101 kernel:error: PMC:8778 CPU_ID: 19 arch/x86/kvm/pmc.c, pmc_begin_audit_debug_store - Can't read the guest_ds_area 0x95400300 of cr3 0x1f1e33c0, exception = 5
Sep 27 14:30:15 2023 FW-TE101 kernel:error: PMC:8778 CPU_ID: 19 arch/x86/kvm/pmc.c, pmc_begin_audit_debug_store - Can't read the guest_ds_area 0x95400300 of cr3 0x1f1e33c0, exception = 5
Sep 27 14:30:15 2023 FW-TE101 kernel:error: PMC:8778 CPU_ID: 3 arch/x86/kvm/pmc.c, pmc_begin_audit_debug_store - Can't read the guest_ds_area 0x95400300 of cr3 0x1f1e33c0, exception = 5
Sep 27 14:30:15 2023 FW-TE101 kernel:error: PMC:8778 CPU_ID: 3 arch/x86/kvm/pmc.c, pmc_begin_audit_debug_store - Can't read the guest_ds_area 0x95400300 of cr3 0x1f1e33c0, exception = 5
Sep 27 14:30:15 2023 FW-TE101 kernel:error: PMC:8778 CPU_ID: 3 arch/x86/kvm/pmc.c, pmc_begin_audit_debug_store - Can't read the guest_ds_area 0x95400300 of cr3 0x1f1e33c0, exception = 5
Sep 27 14:30:15 2023 FW-TE101 kernel:error: PMC:8778 CPU_ID: 3 arch/x86/kvm/pmc.c, pmc_begin_audit_debug_store - Can't read the guest_ds_area 0x95400300 of cr3 0x1f1e33c0, exception = 5
Sep 27 14:30:15 2023 FW-TE101 kernel:error: PMC:8778 CPU_ID: 3 arch/x86/kvm/pmc.c, pmc_begin_audit_debug_store - Can't read the guest_ds_area 0x95400300 of cr3 0x1f1e33c0, exception = 5

I had problems with the disk space on /var/ log when the message file was 120 Gbytes...

Has anyone encountered a similar problem? I haven't found anything similar when I searched around

Regards

Mikael Trosell

0 Kudos
6 Replies
Tal_Paz-Fridman
Employee
Employee

Hi - have you opened a ticket with TAC? 

I found 2 similar issues and it seems the message are harmless. I suggest opening a ticket so that your case is also investigated. You can point them to this post if needed so that they can refer to the other cases.

0 Kudos
Mikael_Trosell
Participant

Hi,  I'll open a case and see what the result is. I have to increase "log rotation" so that the disk does not get filled in the meantime.

 

0 Kudos
SuedL_Sec
Explorer

Hi Mikael, what was the result of the support case? 

Regards, Viktor

0 Kudos
Mikael_Trosell
Participant

Support wanted more information than I was allowed to send. It works as it should. So I just rotate the syslog file every hour.

0 Kudos
SuedL_Sec
Explorer

Hi Mikael, what was the result of the support case?

Regards, Viktor

0 Kudos
Lesley
Advisor
Advisor

Hi Viktor,

This is the related SK article:

https://support.checkpoint.com/results/sk/sk181544

-------
If you like this post please give a thumbs up(kudo)! 🙂
0 Kudos

Leaderboard

Epsum factorial non deposit quid pro quo hic escorol.

Upcoming Events

    CheckMates Events