An error I don’t understand!!!

[tismo]

I am running proxmox on an idea pad y410p. It’s a little old but I don’t require a lot from it. I have maybe 1 vm and about 5 lxc containers.
I was working on setting up dashy and all of a sudden I hear the laptop screaming with cpu topping at around 85~ to 90% temp. I checked on the laptop screen and I saw a stream of this
I don’t know what it means. I check on google but didn’t find anything.

I am on proxmox 8 btw.

Error:

196198s.7457891 nouveaux 0000:01:00.0: i2c: aux 000d: magic wait

 

[Philipp Hufnagl]

Hello

Lets have a look if there is more in your Journal with journalctl --since '2023-09-10' > $(hostname)-journal.txt. Please send me the output file.

 

[tismo]

Hello

Lets have a look if there is more in your Journal with journalctl --since '2023-09-10' > $(hostname)-journal.txt. Please send me the output file.

do I send it in a pm?

 

[Philipp Hufnagl]

do I send it in a pm?

Please don't! Just attach it as file with the 'Attach files' button in the bottom left of the reply box!

 

[tismo]

Please don't! Just attach it as file with the 'Attach files' button in the bottom left of the reply box!

Ok i wont. That's why I asked first. do I put the command as is and cat the text file? Sorry I am still learning proxmox

 

[Philipp Hufnagl]

What the command does is looking up your system log with journalctl --since '2023-09-10' and then saves it to a file with > $(hostname)-journal.txt, where $(hostname) is automatically replaced by your hostname.

So after running it, there should be a file in the folder containing the output of the journalctl.

 

[Philipp Hufnagl]

Can you follow? If you have any questions feel free to ask

 

[tismo]

Can you follow? If you have any questions feel free to ask

the site is saying the file is too big. Should I create a pastebin link instead?

 

[tismo]

I have proxmox backup server that was down for the whole of last week and it was spamming the host so I removed all those entries to shrink the file size a little but it's still to large to attach.

 

[Philipp Hufnagl]

Sorry. My misstake! Just set a shorter time interval like journalctl --since '2023-09-24' > $(hostname)-journal.txt.

 

[tismo]

No worries. Thank you for trying to help.

 

[Philipp Hufnagl]

Right now I do not know the root cause, but I think the issue your error is refering to is reported here.

Sep 27 10:18:36 Proxmox kernel: pci 0000:01:00.0: can't claim BAR 6 [mem 0xfff80000-0xffffffff pref]: no compatible bridge window
Sep 27 10:18:36 Proxmox kernel: pci 0000:01:00.0: BAR 6: assigned [mem 0xc1080000-0xc10fffff pref]
Sep 27 10:18:36 Proxmox kernel: pci 0000:00:01.0: PCI bridge to [bus 01-06]
Sep 27 10:18:36 Proxmox kernel: pci 0000:00:01.0:   bridge window [io  0x4000-0x4fff]
Sep 27 10:18:36 Proxmox kernel: pci 0000:00:01.0:   bridge window [mem 0xc0000000-0xc1ffffff]
Sep 27 10:18:36 Proxmox kernel: pci 0000:00:01.0:   bridge window [mem 0x90000000-0xafffffff 64bit pref]
Sep 27 10:18:36 Proxmox kernel: pci 0000:00:1c.0: PCI bridge to [bus 07]
Sep 27 10:18:36 Proxmox kernel: pci 0000:00:1c.0:   bridge window [io  0x3000-0x3fff]
Sep 27 10:18:36 Proxmox kernel: pci 0000:00:1c.0:   bridge window [mem 0xc2500000-0xc25fffff]
Sep 27 10:18:36 Proxmox kernel: pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7 window]
Sep 27 10:18:36 Proxmox kernel: pci_bus 0000:00: resource 5 [io  0x0d00-0xffff window]
Sep 27 10:18:36 Proxmox kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000dffff window]
Sep 27 10:18:36 Proxmox kernel: pci_bus 0000:00: resource 7 [mem 0x8fa00000-0xfeafffff window]
Sep 27 10:18:36 Proxmox kernel: pci_bus 0000:01: resource 0 [io  0x4000-0x4fff]
Sep 27 10:18:36 Proxmox kernel: pci_bus 0000:01: resource 1 [mem 0xc0000000-0xc1ffffff]
Sep 27 10:18:36 Proxmox kernel: pci_bus 0000:01: resource 2 [mem 0x90000000-0xafffffff 64bit pref]
Sep 27 10:18:36 Proxmox kernel: pci_bus 0000:07: resource 0 [io  0x3000-0x3fff]
Sep 27 10:18:36 Proxmox kernel: pci_bus 0000:07: resource 1 [mem 0xc2500000-0xc25fffff]
Sep 27 10:18:36 Proxmox kernel: pci 0000:00:1a.0: quirk_usb_early_handoff+0x0/0x7c0 took 18752 usecs
Sep 27 10:18:36 Proxmox kernel: pci 0000:00:1d.0: quirk_usb_early_handoff+0x0/0x7c0 took 19511 usecs
Sep 27 10:18:36 Proxmox kernel: pci 0000:01:00.1: extending delay after power-on from D3hot to 20 msec
Sep 27 10:18:36 Proxmox kernel: pci 0000:01:00.1: D0 power state depends on 0000:01:00.0
Sep 27 10:18:36 Proxmox kernel: pci 0000:07:00.0: set MSI_INTX_DISABLE_BUG flag

I will have a deeper look to find out what caused this.

 

[tismo]

Right now I do not know the root cause, but I think the issue your error is refering to is reported here.

Sep 27 10:18:36 Proxmox kernel: pci 0000:01:00.0: can't claim BAR 6 [mem 0xfff80000-0xffffffff pref]: no compatible bridge window
Sep 27 10:18:36 Proxmox kernel: pci 0000:01:00.0: BAR 6: assigned [mem 0xc1080000-0xc10fffff pref]
Sep 27 10:18:36 Proxmox kernel: pci 0000:00:01.0: PCI bridge to [bus 01-06]
Sep 27 10:18:36 Proxmox kernel: pci 0000:00:01.0:   bridge window [io  0x4000-0x4fff]
Sep 27 10:18:36 Proxmox kernel: pci 0000:00:01.0:   bridge window [mem 0xc0000000-0xc1ffffff]
Sep 27 10:18:36 Proxmox kernel: pci 0000:00:01.0:   bridge window [mem 0x90000000-0xafffffff 64bit pref]
Sep 27 10:18:36 Proxmox kernel: pci 0000:00:1c.0: PCI bridge to [bus 07]
Sep 27 10:18:36 Proxmox kernel: pci 0000:00:1c.0:   bridge window [io  0x3000-0x3fff]
Sep 27 10:18:36 Proxmox kernel: pci 0000:00:1c.0:   bridge window [mem 0xc2500000-0xc25fffff]
Sep 27 10:18:36 Proxmox kernel: pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7 window]
Sep 27 10:18:36 Proxmox kernel: pci_bus 0000:00: resource 5 [io  0x0d00-0xffff window]
Sep 27 10:18:36 Proxmox kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000dffff window]
Sep 27 10:18:36 Proxmox kernel: pci_bus 0000:00: resource 7 [mem 0x8fa00000-0xfeafffff window]
Sep 27 10:18:36 Proxmox kernel: pci_bus 0000:01: resource 0 [io  0x4000-0x4fff]
Sep 27 10:18:36 Proxmox kernel: pci_bus 0000:01: resource 1 [mem 0xc0000000-0xc1ffffff]
Sep 27 10:18:36 Proxmox kernel: pci_bus 0000:01: resource 2 [mem 0x90000000-0xafffffff 64bit pref]
Sep 27 10:18:36 Proxmox kernel: pci_bus 0000:07: resource 0 [io  0x3000-0x3fff]
Sep 27 10:18:36 Proxmox kernel: pci_bus 0000:07: resource 1 [mem 0xc2500000-0xc25fffff]
Sep 27 10:18:36 Proxmox kernel: pci 0000:00:1a.0: quirk_usb_early_handoff+0x0/0x7c0 took 18752 usecs
Sep 27 10:18:36 Proxmox kernel: pci 0000:00:1d.0: quirk_usb_early_handoff+0x0/0x7c0 took 19511 usecs
Sep 27 10:18:36 Proxmox kernel: pci 0000:01:00.1: extending delay after power-on from D3hot to 20 msec
Sep 27 10:18:36 Proxmox kernel: pci 0000:01:00.1: D0 power state depends on 0000:01:00.0
Sep 27 10:18:36 Proxmox kernel: pci 0000:07:00.0: set MSI_INTX_DISABLE_BUG flag

I will have a deeper look to find out what caused this.

Thank you so much Philipp

 

[Philipp Hufnagl]

Are you using some sort of PCIE passthrough on your GPU?

 

[tismo]

It’s a laptop. I am using the integrated gpu. The only thingI have plugged in it are 2 Ssd drives.
I kinda figured out what was causing the spike in cpu temp. It was pi.alert once I shut down that container the cou went back to normal.
Although this makes me think those errors were just a coincidence with something else that caused them to pop up.
I haven’t had an issue since I updated pi.alert though. I don’t know if the issue that caused me to post here is still present or not.