Failed to start process error reports when automatic reporting is enabled

Failed to start Process error reports when automatic reporting is enabled

During the start, it shows always the following error message:

Failed to start Process error reports when automatic reporting is enabled.

Here is the log:

3 Answers 3

Since a couple of days I have the same appearing on screen before the graphics kick in. It’s appearing with some other messages I’ve not seen earlier:

A day or two ago all power options under the [Settings] menu were gone. A reboot of the box brought them back.

As ‘zero-coding’ is asking: what is wrong?

It seems solved on my machine now. I’ve removed all gnome extensions and also all power monitor things like lm-sensors. From then on the messages are gone in the reports and on screen.

Disabling the apport service did it for me on Ubuntu 22.10:

Hot Network Questions

To subscribe to this RSS feed, copy and paste this URL into your RSS reader.

Site design / logo © 2023 Stack Exchange Inc; user contributions licensed under CC BY-SA . rev 2023.1.16.43160

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.

Источник

Ошибка процесса сообщает об ошибке при запуске

Всякий раз, когда я загружаю Ubuntu, он загружается правильно, пока не появится диспетчер отображения. Сказав gdm3.service , появится сообщение об ошибке » Failed to start process error reports when automatic reporting is enabled «и прокрутите вниз, но через некоторое время все еще загружается нормально. Когда я попробовал другое ядро, появилось другое сообщение об ошибке. В нем говорилось:» Failed to start System Security Services Daemon «и некоторые зависимости безопасности. Все статьи, которые я могу найти, устарели. Пожалуйста, помогите. Журналы:

Sep 22 15:57:12 thecoder3281f-LIFEBOOK-E734 systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Sep 22 15:57:12 thecoder3281f-LIFEBOOK-E734 systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Sep 22 15:57:12 thecoder3281f-LIFEBOOK-E734 systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Sep 22 15:57:12 thecoder3281f-LIFEBOOK-E734 systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Sep 22 15:57:12 thecoder3281f-LIFEBOOK-E734 systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Sep 22 15:57:12 thecoder3281f-LIFEBOOK-E734 systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Sep 22 15:57:12 thecoder3281f-LIFEBOOK-E734 systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Sep 22 15:57:12 thecoder3281f-LIFEBOOK-E734 systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Sep 22 15:57:12 thecoder3281f-LIFEBOOK-E734 systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Sep 22 15:57:12 thecoder3281f-LIFEBOOK-E734 systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Sep 22 15:57:12 thecoder3281f-LIFEBOOK-E734 systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Sep 22 15:57:12 thecoder3281f-LIFEBOOK-E734 systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Sep 22 15:57:12 thecoder3281f-LIFEBOOK-E734 systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Sep 22 15:57:12 thecoder3281f-LIFEBOOK-E734 systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Sep 22 15:57:12 thecoder3281f-LIFEBOOK-E734 systemd[1]: Failed to start Process error reports when automatic reporting is enabled. —Truncated output—

Источник

Failed to start process automatic reporting is enabled

I’ve recently installed Ubuntu 22.04 on my laptop, and all was running smoothly until this morning, when I tried to log in and got an error: Oh no! Something has gone wrong. A problem has occurred and the system can’t recover. All extensions have been disabled as a precaution. I tried multiple again, and it didn’t work. When I try to log in, the desktop will be briefly displayed before this error message pops up, prompting me to log out and try again. After pressing the Log out button, the following flashes across the screen: [FAILED] Failed to start Process automatic reporting is enabled.

Something I noticed is that when the desktop flashes, the application icons in the sidebar were slightly different then they normally are. I’m not exactly sure what this means, though.

So I used CTRL ALT F3 to open up a command line interface. Network seems to be working, as I updated and upgraded the system, but to no avail.

I’m able to read logs, but frankly, I don’t really know what they mean, or which one to even take a look at. If somebody could help me out here, that would be greatly appreciated.

Some other info: I have a Lenovo Ideapad Flex 5, dual-booting Ubuntu 22.04 with Windows 11. Windows works just fine when I boot it. I am able to enter recovery mode and root shell.

Update: I tried to boot again, and for some reason it became stuck on these two lines of text:

I was unable to reproduce this on recovery mode, only on normal boot.

Источник

apport-autoreport.service loaded failed failed Process error reports when automatic reporting is enabled

I am not getting this error when I open my terminal:

I followed this recommendation and reboot my system, but it is still the same message.

After that, I got a prompt that made me choose between lightdm and gdm3, and I chose gdm3 did not allow me to fix the issue.

1 Answer 1

apport-autoreport.service loaded failed failed Process error reports when automatic reporting is enabled

is probably unrelated to the package lightdm. The message can be confirmed by running:

Recent upgrades/updates on Ubuntu seem to trigger this apport-autoreport.service error. The apport automatic crash report uploading, called whoopsie, becomes disconnected tfrom the local system’s /var/crash store of reports, and dies, reporting nothing to Canonical.

Here is a solution:

Details: The whoopsie.path is a systemd stanza that tells whoopsie package, which uploads things from /var/crash to Canonical for reporting, that /var/crash is the directory that should be checked (and monitored) for crash reports, which itself is directed via apport-autoreport.path .

Note: The apport mechanism had previously been a security problem.

Источник

VCSA 6.5 fails to start File System Check and Network Service

During the startup of the VMware VCSA 6.5, you may experience some issues that impede the appliance to properly boot.

The errors are the following:

• Failed to start File System Check
• Failed to start Network Service

Failed to start File System Check

The error occurs during the boot process. The appliance shows the error «Failed to start File System Check» and it’s stuck in Emergency Mode.

To fix this error run the command:

Answer yes to all questions about repairs, inodes and fixing issues.

After fixing all detected issues, reboot the VCSA by selecting Actions > Power > Reset option from the console.

Click OK to confirm.

After rebooting you may experience another error related to Network Service.

Failed to start Network Service

Another issue you can experience during the boot process is the «Failed to start Network Service» error.

Type the root password and launch the BASH shell.

Run the command:

Answer yes to all questions in order to fix all detected errors.

After rebooting the VCSA, the system boots successfully.

Accessing the vCenter Server from the preferred browser, the appliance is now up and running.

So far the new VCSA 6.5 didn’t satisfy me because it crashes too often and it is not so robust as the Windows-based vCenter. Hopefully VMware will improve the appliance making it more stable and reliable.

Источник

This bug affects 4 people

1. 18.04 install won’t boot, maybe issue with systemd-tmpfiles-setup
   

   I dual boot with Ubuntu 18.04 and Win 10. My setup has worked fine for months. Last time I booted into my linux drive was maybe two weeks ago, I don’t remember anything remarkable but maybe something happened that I didn’t notice. I sat down to get some work done today and now my install won’t boot at all.

   I’ve run file system check on the volume, all good. I’ve checked the boot log and seen two failed to starts. One is «Failed to start Process error reports when automatic reporting is enabled». It doesn’t seem like this is the error that’s causing the boot issue because the other one that pops up seems more serious. That is: «Failed to start Create Volatile Files and Directories». When I looked deeper at that service status (after booting into recovering, enabling networking and going to root) it said that the service failed.

   I also ran a bootrepair from a livedisk, that didn’t seem to do anything.

   Any suggestions? I’m trying to avoid having to do a fresh install cause then I have to spend time getting my environment up and running again and that’s a massive pain.

   Screenshots (sorry, couldn’t screencap so I took photos):

   1) This is what I see when I try to boot. The Ubuntu loading screen goes for a couple minutes then I see this (with the character errors)

   2) Then the prev screen will refresh after a couple mins and fix the character errors and show me this:

   3) Failure from the bootlog

   4) Finally, here’s what I get when I check the service status.

   Last edited by ajgreeny; December 30th, 2018 at 08:52 PM.

   Reason: Large images replaced with thumbnails.

   ---

2. Re: 18.04 install won’t boot, maybe issue with systemd-tmpfiles-setup
   

   It looks like you logged in as root. Ubuntu is configured not to really use root user, but use sudo command whenever you need to do something administrative.

   Forum rules on root vs. sudo
   http://ubuntuforums.org/showthread.php?t=1486138
   http://xkcd.com/149/

   ---

3. Re: 18.04 install won’t boot, maybe issue with systemd-tmpfiles-setup
   

   Hi d00d1234,

   It looks like you ran into this bug.

   Can you please try running the following command to make sure that the ownership of your root folder (/) actually belongs to root:

   chown root.root /

   ---

less /var/log/syslog

Oct 30 16:24:11 pve systemd[1]: Starting Daily apt download activities...
Oct 30 16:24:11 pve systemd[1]: apt-daily.service: Succeeded.
Oct 30 16:24:11 pve systemd[1]: Finished Daily apt download activities.
Oct 30 16:48:18 pve kernel: [173437.500346] perf: interrupt took too long (3913 > 3911), lowering kernel.perf_event_max_sample_rate to 51000
Oct 30 16:55:01 pve systemd[1]: Starting Cleanup of Temporary Directories...
Oct 30 16:55:01 pve systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
Oct 30 16:55:01 pve systemd[1]: Finished Cleanup of Temporary Directories.
Oct 30 17:17:01 pve CRON[426631]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Oct 30 18:17:02 pve CRON[436051]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Oct 30 19:07:51 pve smartd[1393]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 73 to 74
Oct 30 19:17:01 pve CRON[445480]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Oct 30 20:17:01 pve CRON[454794]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Oct 30 20:39:42 pve pvedaemon[242158]: <root@pam> successful auth for user 'root@pam'
Oct 30 20:39:48 pve pvedaemon[458412]: stop VM 101: UPID:pve:0006FEAC:011DD73C:635E93BC:qmstop:101:root@pam:
Oct 30 20:39:48 pve pvedaemon[242158]: <root@pam> starting task UPID:pve:0006FEAC:011DD73C:635E93BC:qmstop:101:root@pam:
Oct 30 20:39:48 pve kernel: [187327.921107] fwbr101i0: port 2(tap101i0) entered disabled state
Oct 30 20:39:48 pve kernel: [187327.944850] fwbr101i0: port 1(fwln101i0) entered disabled state
Oct 30 20:39:48 pve kernel: [187327.944901] vmbr0: port 2(fwpr101p0) entered disabled state
Oct 30 20:39:48 pve kernel: [187327.945235] device fwln101i0 left promiscuous mode
Oct 30 20:39:48 pve kernel: [187327.945239] fwbr101i0: port 1(fwln101i0) entered disabled state
Oct 30 20:39:48 pve kernel: [187327.966272] device fwpr101p0 left promiscuous mode
Oct 30 20:39:48 pve kernel: [187327.966275] vmbr0: port 2(fwpr101p0) entered disabled state
Oct 30 20:39:48 pve qmeventd[1388]: read: Connection reset by peer
Oct 30 20:39:48 pve systemd[1]: 101.scope: Succeeded.
Oct 30 20:39:48 pve systemd[1]: 101.scope: Consumed 1d 9h 5min 47.663s CPU time.
Oct 30 20:39:49 pve kernel: [187328.621929] vfio_mdev 00000000-0000-0000-0000-000000000101: Removing from iommu group 148
Oct 30 20:39:49 pve kernel: [187328.621948] vfio_mdev 00000000-0000-0000-0000-000000000101: MDEV: detaching iommu
Oct 30 20:39:49 pve pvedaemon[242158]: <root@pam> end task UPID:pve:0006FEAC:011DD73C:635E93BC:qmstop:101:root@pam: OK
Oct 30 20:39:49 pve qmeventd[458434]: Starting cleanup for 101
Oct 30 10:17:01 pve CRON[359997]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Oct 30 11:17:01 pve CRON[369733]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Oct 30 12:17:01 pve CRON[379429]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Oct 30 12:56:56 pve pvestatd[1704]: auth key pair too old, rotating..
Oct 30 13:17:01 pve CRON[388800]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Oct 30 14:17:01 pve CRON[398114]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Oct 30 15:17:01 pve CRON[407893]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Oct 30 16:17:01 pve CRON[417268]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Oct 30 16:24:11 pve systemd[1]: Starting Daily apt download activities...
Oct 30 16:24:11 pve systemd[1]: apt-daily.service: Succeeded.
Oct 30 16:24:11 pve systemd[1]: Finished Daily apt download activities.
Oct 30 16:48:18 pve kernel: [173437.500346] perf: interrupt took too long (3913 > 3911), lowering kernel.perf_event_max_sample_rate to 51000
Oct 30 16:55:01 pve systemd[1]: Starting Cleanup of Temporary Directories...
Oct 30 16:55:01 pve systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
Oct 30 16:55:01 pve systemd[1]: Finished Cleanup of Temporary Directories.
Oct 30 17:17:01 pve CRON[426631]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Oct 30 18:17:02 pve CRON[436051]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Oct 30 19:07:51 pve smartd[1393]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 73 to 74
Oct 30 19:17:01 pve CRON[445480]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Oct 30 20:17:01 pve CRON[454794]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Oct 30 20:39:42 pve pvedaemon[242158]: <root@pam> successful auth for user 'root@pam'
Oct 30 20:39:48 pve pvedaemon[458412]: stop VM 101: UPID:pve:0006FEAC:011DD73C:635E93BC:qmstop:101:root@pam:
Oct 30 20:39:48 pve pvedaemon[242158]: <root@pam> starting task UPID:pve:0006FEAC:011DD73C:635E93BC:qmstop:101:root@pam:
Oct 30 20:39:48 pve kernel: [187327.921107] fwbr101i0: port 2(tap101i0) entered disabled state
Oct 30 20:39:48 pve kernel: [187327.944850] fwbr101i0: port 1(fwln101i0) entered disabled state
Oct 30 20:39:48 pve kernel: [187327.944901] vmbr0: port 2(fwpr101p0) entered disabled state
Oct 30 20:39:48 pve kernel: [187327.945235] device fwln101i0 left promiscuous mode
Oct 30 20:39:48 pve kernel: [187327.945239] fwbr101i0: port 1(fwln101i0) entered disabled state
Oct 30 20:39:48 pve kernel: [187327.966272] device fwpr101p0 left promiscuous mode
Oct 30 20:39:48 pve kernel: [187327.966275] vmbr0: port 2(fwpr101p0) entered disabled state
Oct 30 20:39:48 pve qmeventd[1388]: read: Connection reset by peer
Oct 30 20:39:48 pve systemd[1]: 101.scope: Succeeded.
Oct 30 20:39:48 pve systemd[1]: 101.scope: Consumed 1d 9h 5min 47.663s CPU time.
Oct 30 20:39:49 pve kernel: [187328.621929] vfio_mdev 00000000-0000-0000-0000-000000000101: Removing from iommu group 148
Oct 30 20:39:49 pve kernel: [187328.621948] vfio_mdev 00000000-0000-0000-0000-000000000101: MDEV: detaching iommu
Oct 30 20:39:49 pve pvedaemon[242158]: <root@pam> end task UPID:pve:0006FEAC:011DD73C:635E93BC:qmstop:101:root@pam: OK
Oct 30 20:39:49 pve qmeventd[458434]: Starting cleanup for 101
Oct 31 14:39:18 pve nvidia-vgpu-mgr[604651]: VgpuConfig {#012    vgpu_type: 259,#012    vgpu_name: "GRID RTX6000-4Q",#012    vgpu_class: "Quadro",#012    vgpu_signature: [],#012    features: "Quadro-Virtual-DWS,5.0;GRID-Virtual-WS,2.0;GRID-
Virtual-WS-Ext,2.0",#012    max_instances: 6,#012    num_heads: 4,#012    max_resolution_x: 7680,#012    max_resolution_y: 4320,#012    max_pixels: 58982400,#012    frl_config: 60,#012    cuda_enabled: 1,#012    ecc_supported: 1,#012    mig
_instance_size: 0,#012    multi_vgpu_supported: 0,#012    vdev_id: 0x1e301328,#012    pdev_id: 0x1e30,#012    fb_length: 0xec000000,#012    mappable_video_size: 0x400000,#012    fb_reservation: 0x14000000,#012    encoder_capacity: 0x64,#012
    bar1_length: 0x100,#012    frl_enable: 1,#012    adapter_name: "GRID RTX6000-4Q",#012    adapter_name_unicode: "GRID RTX6000-4Q",#012    short_gpu_name_string: "TU102GL-A",#012    licensed_product_name: "NVIDIA RTX Virtual Workstation",
#012    vgpu_extra_params: [],#012}
Oct 31 14:39:18 pve nvidia-vgpu-mgr[604651]: notice: vmiop_log: (0x0): gpu-pci-id : 0x1800
Oct 31 14:39:18 pve nvidia-vgpu-mgr[604651]: notice: vmiop_log: (0x0): vgpu_type : Quadro
Oct 31 14:39:18 pve nvidia-vgpu-mgr[604651]: notice: vmiop_log: (0x0): Framebuffer: 0xec000000
Oct 31 14:39:18 pve nvidia-vgpu-mgr[604651]: notice: vmiop_log: (0x0): Virtual Device Id: 0x1e30:0x1328
Oct 31 14:39:18 pve nvidia-vgpu-mgr[604651]: notice: vmiop_log: (0x0): FRL Value: 60 FPS
Oct 31 14:39:18 pve nvidia-vgpu-mgr[604651]: notice: vmiop_log: ######## vGPU Manager Information: ########
Oct 31 14:39:18 pve nvidia-vgpu-mgr[604651]: notice: vmiop_log: Driver Version: 460.73.01
Oct 31 14:39:18 pve nvidia-vgpu-mgr[604651]: notice: vmiop_log: (0x0): vGPU supported range: (0x70001, 0x90002)
Oct 31 14:39:18 pve nvidia-vgpu-mgr[604651]: notice: vmiop_log: (0x0): Init frame copy engine: syncing...
Oct 31 14:39:18 pve nvidia-vgpu-mgr[604651]: notice: vmiop_log: (0x0): vGPU migration enabled
Oct 31 14:39:18 pve nvidia-vgpu-mgr[604651]: notice: vmiop_log: display_init inst: 0 successful
Oct 31 14:39:18 pve kernel: [252097.865254] [nvidia-vgpu-vfio] 00000000-0000-0000-0000-000000000601: vGPU migration disabled
Oct 31 14:39:18 pve pvedaemon[601591]: <root@pam> end task UPID:pve:0009394B:0180ABD5:635F90BD:qmstart:601:root@pam: OK
Oct 31 14:39:25 pve kernel: [252104.672891] kvm [604504]: ignored rdmsr: 0x10f data 0x0
Oct 31 14:39:25 pve kernel: [252104.672924] kvm [604504]: ignored rdmsr: 0x123 data 0x0
Oct 31 14:39:25 pve kernel: [252104.672946] kvm [604504]: ignored rdmsr: 0xc0011020 data 0x0
Oct 31 14:39:26 pve pvedaemon[604682]: starting vnc proxy UPID:pve:00093A0A:0180AF4D:635F90C6:vncproxy:601:root@pam:
Oct 31 14:39:26 pve pvedaemon[242158]: <root@pam> starting task UPID:pve:00093A0A:0180AF4D:635F90C6:vncproxy:601:root@pam:
Oct 31 14:40:24 pve pvedaemon[242158]: worker exit
Oct 31 14:40:24 pve pvedaemon[1732]: worker 242158 finished
Oct 31 14:40:24 pve pvedaemon[1732]: starting 1 worker(s)
Oct 31 14:40:24 pve pvedaemon[1732]: worker 604891 started
Oct 31 14:43:48 pve nvidia-vgpu-mgr[604651]: notice: vmiop_log: ######## Guest NVIDIA Driver Information: ########
Oct 31 14:43:48 pve nvidia-vgpu-mgr[604651]: notice: vmiop_log: Driver Version: 510.85.02
Oct 31 14:43:48 pve nvidia-vgpu-mgr[604651]: error: vmiop_log: (0x0): Incompatible Guest/Host drivers: Guest VGX version is newer than the maximum version supported by the Host. Disabling vGPU.
Oct 31 14:43:48 pve nvidia-vgpu-mgr[604651]: error: vmiop_log: (0x0): VGPU message 1 failed, result code: 0x6a
Oct 31 14:43:48 pve nvidia-vgpu-mgr[604651]: error: vmiop_log: (0x0):         0x1e, 0xe, 0x100, 0x100,
Oct 31 14:43:48 pve nvidia-vgpu-mgr[604651]: error: vmiop_log: (0x0):         0x100, 0x1e17ea1, '510.85.02', 'rel/gpu_drv/r510/r513_40-519', 'Private r513_40 rel/gpu_drv/r510/r513_40-519 unknown'
Oct 31 14:43:48 pve nvidia-vgpu-mgr[604651]: notice: vmiop_log: (0x0): Shared memory (0x5) is already valid: new PA=0x42c10d000, current PA:0x39876b000
Oct 31 14:43:48 pve nvidia-vgpu-mgr[604651]: notice: vmiop_log: (0x0): Shared memory (0x6) is already valid: new PA=0x100000000, current PA:0x121cfe000
Oct 31 14:43:48 pve nvidia-vgpu-mgr[604651]: notice: vmiop_log: (0x0): Shared memory (0x6) is already valid: new PA=0x400000000, current PA:0x121cfe000
Oct 31 14:43:48 pve nvidia-vgpu-mgr[604651]: notice: vmiop_log: (0x0): Shared memory (0x6) is already valid: new PA=0x42c10c000, current PA:0x121cfe000
Oct 31 14:44:18 pve nvidia-vgpu-mgr[604651]: notice: vmiop_log: (0x0): Shared memory (0x6) is already valid: new PA=0x400000000, current PA:0x121cfe000
Oct 31 14:44:18 pve nvidia-vgpu-mgr[604651]: notice: vmiop_log: (0x0): Shared memory (0x5) is already valid: new PA=0x400000000, current PA:0x39876b000
Oct 31 14:44:18 pve nvidia-vgpu-mgr[604651]: notice: vmiop_log: (0x0): Ring (0x3) is already valid: new PA=0x400000000, current PA:0x39d075000
Oct 31 14:44:18 pve nvidia-vgpu-mgr[604651]: notice: vmiop_log: (0x0): Ring (0x4) is already valid: new PA=0x400000000, current PA:0x109f24000
Oct 31 14:44:18 pve nvidia-vgpu-mgr[604651]: notice: vmiop_log: (0x0): Ring (0x2) is already valid: new PA=0x400000000, current PA:0x15dd92000
Oct 31 14:44:18 pve nvidia-vgpu-mgr[604651]: notice: vmiop_log: (0x0): Ring (0x2) is already valid: new PA=0x400000000, current PA:0x15dd92000
Oct 31 14:44:18 pve nvidia-vgpu-mgr[604651]: notice: vmiop_log: (0x0): Ring (0x2) is already valid: new PA=0x400000000, current PA:0x15dd92000
Oct 31 14:44:18 pve nvidia-vgpu-mgr[604651]: notice: vmiop_log: (0x0): Ring (0x2) is already valid: new PA=0x42c133000, current PA:0x15dd92000
Oct 31 14:44:18 pve nvidia-vgpu-mgr[604651]: notice: vmiop_log: (0x0): Ring (0x3) is already valid: new PA=0x400000000, current PA:0x39d075000
Oct 31 14:44:18 pve nvidia-vgpu-mgr[604651]: notice: vmiop_log: (0x0): Ring (0x3) is already valid: new PA=0x400000000, current PA:0x39d075000
Oct 31 14:44:18 pve nvidia-vgpu-mgr[604651]: notice: vmiop_log: (0x0): Ring (0x3) is already valid: new PA=0x42c134000, current PA:0x39d075000
Oct 31 14:44:18 pve nvidia-vgpu-mgr[604651]: notice: vmiop_log: (0x0): Ring (0x4) is already valid: new PA=0x400000000, current PA:0x109f24000
Oct 31 14:44:18 pve nvidia-vgpu-mgr[604651]: notice: vmiop_log: (0x0): Ring (0x4) is already valid: new PA=0x400000000, current PA:0x109f24000
Oct 31 14:44:18 pve nvidia-vgpu-mgr[604651]: notice: vmiop_log: (0x0): Ring (0x4) is already valid: new PA=0x42c111000, current PA:0x109f24000
Oct 31 14:44:18 pve nvidia-vgpu-mgr[604651]: notice: vmiop_log: (0x0): Shared memory (0x5) is already valid: new PA=0x400000000, current PA:0x39876b000
Oct 31 14:44:18 pve nvidia-vgpu-mgr[604651]: notice: vmiop_log: (0x0): Shared memory (0x5) is already valid: new PA=0x400000000, current PA:0x39876b000
Oct 31 14:44:18 pve nvidia-vgpu-mgr[604651]: notice: vmiop_log: (0x0): Shared memory (0x5) is already valid: new PA=0x42c110000, current PA:0x39876b000
Oct 31 14:44:18 pve nvidia-vgpu-mgr[604651]: notice: vmiop_log: (0x0): Shared memory (0x6) is already valid: new PA=0x400000000, current PA:0x121cfe000
Oct 31 14:44:18 pve nvidia-vgpu-mgr[604651]: notice: vmiop_log: (0x0): Shared memory (0x6) is already valid: new PA=0x400000000, current PA:0x121cfe000
Oct 31 14:44:18 pve nvidia-vgpu-mgr[604651]: notice: vmiop_log: (0x0): Shared memory (0x6) is already valid: new PA=0x42c10e000, current PA:0x121cfe000
Oct 31 14:44:48 pve nvidia-vgpu-mgr[604651]: notice: vmiop_log: (0x0): Shared memory (0x6) is already valid: new PA=0x400000000, current PA:0x121cfe000
Oct 31 14:44:48 pve nvidia-vgpu-mgr[604651]: notice: vmiop_log: (0x0): Shared memory (0x5) is already valid: new PA=0x400000000, current PA:0x39876b000
Oct 31 14:44:48 pve nvidia-vgpu-mgr[604651]: notice: vmiop_log: (0x0): Ring (0x3) is already valid: new PA=0x400000000, current PA:0x39d075000
Oct 31 14:44:48 pve nvidia-vgpu-mgr[604651]: notice: vmiop_log: (0x0): Ring (0x4) is already valid: new PA=0x400000000, current PA:0x109f24000
Oct 31 14:44:48 pve nvidia-vgpu-mgr[604651]: notice: vmiop_log: (0x0): Ring (0x2) is already valid: new PA=0x400000000, current PA:0x15dd92000
Oct 31 14:44:48 pve nvidia-vgpu-mgr[604651]: notice: vmiop_log: (0x0): Ring (0x2) is already valid: new PA=0x400000000, current PA:0x15dd92000