Nvidia gpu i2c timeout error e0000000

Arch Linux

You are not logged in.

#1 2020-12-31 01:02:26

[SOLVED] Error shown at login promt: nvidia, ucsi_ccg and more

When I get my login prompt after the boot process instead of just «arch login: » it says

Although there is this message I can log in and use Xorg.
I have installed arch two times. Both times and when booting the USB flash installation medium these errors happend but there are some differences and some additional errors. The first time i used EFISTUB directly with efibootmgr, the nouveau driver and the mainboard firmware that was already installed. The second time I used systemd-boot, the nvidia driver and updated the firmware for the mainboard (current install). Both times i used /boot as ESP-mountpoint and implemented amd microcode updates. More information later.

My PC components

Mainboard: B450 TOMAHAWK MAX (MS-7C02)

CPU: AMD Ryzen 5 3600

GPU: Nvidia RTX 2070 Super

Some Error Output:

With my first install sometimes the system randomly froze during the startup of Arch. Also, the messages after the login prompt weren’t there sometimes. There were no freezes with this current install (yet) but since there still were these messages I thought there still is a or even the same problem.
At first I thought it has something to do with the GPU drivers. There were actually some additional errors with nouveau that I could see with dmesg and I also got an error like «nouveau . pmu:firmware unavailable» when booting the USB flash installation medium. I switched to nvidia drivers when It still was my first install but there were some differences to the current install. I think these «__common_interrupt: No irq handler for vector» were not there (really not sure) and I think the last two error messages that are after the login prompt «sd 8:0. were also not there yet. Something else that is different is that with my current install at the end of the boot process is this: first there is nothing behind «Arch login:» , but right after that is shown there is a black screen for half a second and then the login prompt is back with the error messages. So that black screen is new. Also with systemd-boot there are two boot entries in my UEFI boot menu now while there was only one with efibootmgr, but that’s probably the firmware’s fault. (And no it’s not that one of them is from the first install.) Also when I enable the timeout option in the systemd-boot config the resolution is lower between selecting Arch and the login prompt for some reason. But those two things don’t bother me as much.
I read that there can be some problems with some hardware using EFISTUB so I might try GRUB.
The only other thing I could think of is adding some kernel parameters or maybe switching to linux-lts and nvidia-lts?
Currently the kernel parameters are default + amd microcode.

(rant)But usually the solutions to something nvidia related bring some disadvantages with them. I think most or all of my problems are Nvidia related and they are not fun. I also have some screen tearing and audio problems. I really want to switch to an AMD GPU but that’s not easy/cheap because of the GPU situation. Would the problems be the same on other Distros because they use the same driver and bootloader and kernel or should I maybe try another one until I have another GPU if there is no good fix to my problem?

Last edited by JimNeedsHelp (2020-12-31 02:14:22)

#2 2020-12-31 01:10:04

Re: [SOLVED] Error shown at login promt: nvidia, ucsi_ccg and more

Do you have an actual issue or are you just wondering about the messages? Watchdog HW and the interrupt flood are AMD CPU related, the i2c timeout seems somewhat normal but I don’t see any ill-effects on my setup. the sdb messages aren’t errors. The flicker is normal during the modesetting switch, can happen on every GPU and driver, might be alleviated with the nvidia-drm.modeset=1 kernel parameter. The ACPI errors are normal on nearly every BIOS, you seem to get off lucky that only the linux query is ignored (. they are generally unlikely to be relevant, but this one is almost guaranteed), ccp is a AMD CPU/BIOS feature.

Most of those can only be «fixed» with a UEFI update, but they are also completely harmless to normal system usage.

FWIW a variety of errors can happen for all sorts of reasons (racy behaviour due to multi-threaded startup leading to a few things being initalized «too soon» e.g.) and they will be logged regardless of your HW setup they might recover immediately after the error messages or be not actually relevant to how you are intending to use your system. If this annoys you set a lower log level (. with the caveat that you might miss actual issues) or learn to filter and ignore issues that aren’t relevant in your head.

Last edited by V1del (2020-12-31 01:33:54)

#3 2020-12-31 01:47:03

Re: [SOLVED] Error shown at login promt: nvidia, ucsi_ccg and more

Thanks V1del, I thought that these log messages are abnormal. I forgot to mention an important reason though that made me think there is a bigger problem with these messages: With my first install sometimes the system randomly froze during the startup of Arch. I will edit that into my post. Also, the messages after the login prompt weren’t there sometimes. There were no freezes with this install (yet) but since there still were these messages I thought there still is a or even the same problem. I will try the kernel parameter tomorrow and ignore these messages after the login prompt now.

Last edited by JimNeedsHelp (2020-12-31 01:49:10)

Источник

Arch Linux

You are not logged in.

#1 2019-07-21 09:37:13

Nvidia/Bumblebee freezes at boot (nvidia-gpu i2c timeout error)

I installed Arch yesterday and rebooted a few times, installing more programs via the package manager.
But today I when I tried to boot, the system suddenly freezes right after I enter my luks passphrase.
I get two lines of output on the screen before that happens:

and then the cursor will stop blinking and become «stuck», showing just as an unblinking underscore and I cannot even switch to virtual terminals anymore or hit CTRL+ALT+DEL. Just keep power button pressed for a few seconds is the only thing to do, but the freezing happens on next restart again, even when I choose «Arch (fallback initramfs)» from the grub menu.
How would I even start finding out what to do here?

Edit:
I booted from Arch iso, chrooted into the system again and issued another

and for what it’s worth the system now still freezes but it changes the screen resolution before doing so, from the rough huge starting fonts to the fine resolution, and the cursor becomes invisible. And it only shows the second line mentioned above now, not the «recovering journal» one anymore. But it still freezes.

Last edited by millus (2019-07-21 11:19:49)

#2 2019-07-21 09:43:04

Re: Nvidia/Bumblebee freezes at boot (nvidia-gpu i2c timeout error)

you could try add ‘rd.debug’ to kernel parameters and maybe that will give some more output

also remove ‘quiet’ option if present

and in general: check smartctl -a for all disks, run a memtest, etc.

Last edited by frostschutz (2019-07-21 09:43:36)

#3 2019-07-21 09:43:16

Re: Nvidia/Bumblebee freezes at boot (nvidia-gpu i2c timeout error)

Also, if you can elaborate on what you installed and how, that may help shed some light on what has happened.

Mod note: Not an installation issue, moving to NC.

Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

#4 2019-07-21 10:13:35

Re: Nvidia/Bumblebee freezes at boot (nvidia-gpu i2c timeout error)

@frostschutz
Thanks! Looking at those debug messages it freezes after displaying

However, googling for boot freeze on ^this message yields nothing substantial it seems.
I will add ignore_loglevel and try again in a moment.

@WorMzy
Thanks for that page. I added «rd.debug» as frostschutz said instead of «debug» as that wiki page says for now, as I wasn’t sure if it’s ok to add both.
Regarding what I installed, well a large amount of programs as I just set up the system, with X and Xfce4 and lightdm and nvidia drivers and all, probably 2+ GB in packages in total.

Edit:
So I re-ran the boot process, this time with

and the last message is

so I guess this means something is wrong with the nvidia graphics driver, huh?
The system is an optimus system, switching via bumblebee between intel iGPU and nvidia discreete card — well or it is supposed to become that kind of system, when it works..

The depressing thing is that this forum posting is actually the top result on google now, while other results seem to be not substantial for this problem

Some more messages before this:

Edit:
I added ‘bbswitch’ to modules in mkinitcpio.conf and tried again.
Now the last 4 messages were:

Edit:
I removed bumblebee package (and primus/primus_vk packages as they depend on it), now the system doesn’t freeze anymore and the VTs are fine, but the VT 7 that is supposed to startup LightDM stays completely black.
ps reveals that Xorg and lightdm are running though.
I stopped lightdm and killed Xorg and manually started it in VT and indeed a black screen comes up. So since yesterday I already was in X (Xfce4) just fine, before I installed bumbleblee, now if it still doesn’t work again after removing it (I also removed the module in mkinitcpio.conf again accordingly) that means some other package must still be interfering, right?

Do you think it even makes sense to start to try debugging this or should I just do a complete reinstall of the system instead because it might be easiest in terms of effort required?
The problem is that again I have no idea what I am actually looking for now. I had a look at /var/log/Xorg.0.log but wasn’t sure what I was expecting to actually see there. When I google for the actual i2c timeout error message all I find are basically some kernel code things it seems.
I had installed bumblebee following the Arch wiki page, that means enabling the service and adding my user to its group, a pretty simple and straightforward process, so I wonder what went wrong there.
(I edited the thread title to reflect that it’s not really luks-related or anything but rather a bumblebee/nvidia issue.)

Last edited by millus (2019-07-21 11:45:20)

Источник

Arch Linux

You are not logged in.

#1 2021-09-20 01:33:11

[Solved] nvidia-settings and conky issues but drivers seem to work

For the past couple of months, I have been unable to start nvidia-settings and conky fails to read the GPU (which causes it not to start automatically). This had all been working previously, but I don’t remember the exact versions of nvidia drivers and kernels at which it stopped working.

I haven’t found any obvious issues or errors in log files.

Would really appreciate any help investigating this! I don’t know where to look to figure out where the problem is.

The problems
nvidia-settings won’t start

conky doesn’t start automatically. When started manually, this error message appears in the console and conky does not display any info from the GPU.

System info
I am currently running arch zen, but I have the same issue in the standard and lts kernels. I am running wayland and gnome.

GPU is found and is on. This is a desktop with an AMD Ryzen 7 3700X that does not have a GPU, so the Nvidia card is the only GPU. I do not have nvidia-prime installed (and installing nvidia-prime did not work for me, as it did for another user https://github.com/brndnmtthws/conky/issues/928 )

glx seems to find everything

There don’t seem to be any error messages in dmesg (except for I2C timeout that I believe is ok)

I don’t have any special X11 configs

nvidia drivers do find my monitor

I have the following libs installed

Last edited by ogrefish (2021-09-26 18:48:30)

Источник

Arch Linux

You are not logged in.

#1 2021-02-14 15:16:32

[SOLVED] Nvidia card not using any drivers

I have recently installed a fresh Arch in a notebook running an Nvidia GPU. I installed the nvidia package and made sure nouveau was blacklisted, but the driver seems to not be loaded. Tensorflow does not recognize the card, and both nvidia-smi and nvidia-settings tell me something is wrong with the drivers.

I have an Asus rog zephyrus g14, and I’m using the latest linux-zen-g14 kernel with no changes.

Output of nvidia-smi:

NVIDIA-SMI has failed because it couldn’t communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running.

Output of nvidia-settings:

ERROR: NVIDIA driver is not loaded

ERROR: Unable to load info from any available system

Output of lspci -k:

00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Root Complex
Subsystem: Advanced Micro Devices, Inc. [AMD] Renoir Root Complex
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Renoir IOMMU
Subsystem: Advanced Micro Devices, Inc. [AMD] Renoir IOMMU
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge
00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge
Kernel driver in use: pcieport
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge
00:02.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge
Kernel driver in use: pcieport
00:02.4 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge
Kernel driver in use: pcieport
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus
Kernel driver in use: pcieport
00:08.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus
Kernel driver in use: pcieport
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 51)
Subsystem: ASUSTeK Computer Inc. Device 1f11
Kernel driver in use: piix4_smbus
Kernel modules: i2c_piix4, sp5100_tco
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
Subsystem: ASUSTeK Computer Inc. Device 1f11
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 3
Kernel driver in use: k10temp
Kernel modules: k10temp
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 5
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 6
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 7
01:00.0 VGA compatible controller: NVIDIA Corporation TU106M [GeForce RTX 2060 Max-Q] (rev a1)
Subsystem: ASUSTeK Computer Inc. Device 1f11
Kernel modules: nouveau
01:00.1 Audio device: NVIDIA Corporation TU106 High Definition Audio Controller (rev a1)
Subsystem: ASUSTeK Computer Inc. Device 1f11
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
01:00.2 USB controller: NVIDIA Corporation TU106 USB 3.1 Host Controller (rev a1)
Subsystem: ASUSTeK Computer Inc. Device 1f11
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
01:00.3 Serial bus controller [0c80]: NVIDIA Corporation TU106 USB Type-C UCSI Controller (rev a1)
Subsystem: ASUSTeK Computer Inc. Device 1f11
Kernel driver in use: nvidia-gpu
Kernel modules: i2c_nvidia_gpu
02:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a)
Subsystem: Intel Corporation Device 0084
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi
03:00.0 Non-Volatile memory controller: Sandisk Corp WD Blue SN550 NVMe SSD (rev 01)
Subsystem: Sandisk Corp WD Blue SN550 NVMe SSD
Kernel driver in use: nvme
04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Renoir (rev c5)
Subsystem: ASUSTeK Computer Inc. Device 1f11
Kernel driver in use: amdgpu
Kernel modules: amdgpu
04:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device 1637
Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device 1637
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
04:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor
Subsystem: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor
Kernel driver in use: ccp
Kernel modules: ccp
04:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir USB 3.1
Subsystem: ASUSTeK Computer Inc. Device 201f
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
04:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir USB 3.1
Subsystem: ASUSTeK Computer Inc. Device 201f
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
04:00.5 Multimedia controller: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor (rev 01)
Subsystem: ASUSTeK Computer Inc. Device 1f11
Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x
04:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller
Subsystem: ASUSTeK Computer Inc. Device 1f11
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
05:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 81)
Subsystem: ASUSTeK Computer Inc. Device 1f11
Kernel driver in use: ahci
05:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 81)
Subsystem: ASUSTeK Computer Inc. Device 1f11
Kernel driver in use: ahci

The graphics card does not list nvidia as one of the available modules, and since nouveau is blacklisted, no driver is in use.

Output of pacman -Qs nvidia:

Output of dmesg | grep nvidia:

I have tried purging and reinstalling nvidia with no change.

This is my first post ever and I don’t know what logs or commands would be helpful, so I’ll be happy to change anything and provide any extra information needed.

Last edited by spicybread (2021-02-14 16:41:40)

Источник

When I get my login prompt after the boot process instead of just «arch login: » it says

"arch login: [    3.520017] nvidia-gpu 0000:26:00.3: i2c timeout error e0000000
[    3.520026] ucsi_ccg 0-0008: i2c_transfer failed -110
[    3.520032] ucsi_ccg 0-0008: ucsi_ccg_init failed - -110
[    3.544793] sd 8:0:0:0: [sdb] No Caching mode page found
[    3.544798] sd 8:0:0:0: [sdb] Assuming drive cache: write through 

Although there is this message I can log in and use Xorg.
I have installed arch two times. Both times and when booting the USB flash installation medium these errors happend but there are some differences and some additional errors. The first time i used EFISTUB directly with efibootmgr, the nouveau driver and the mainboard firmware that was already installed. The second time I used systemd-boot, the nvidia driver and updated the firmware for the mainboard (current install). Both times i used /boot as ESP-mountpoint and implemented amd microcode updates. More information later.

My PC components

• Mainboard: B450 TOMAHAWK MAX (MS-7C02)

• CPU: AMD Ryzen 5 3600

• GPU: Nvidia RTX 2070 Super

Some Error Output:

systemctl --failed
  UNIT LOAD ACTIVE SUB DESCRIPTION
0 loaded units listed.

journalctl -p 3 -xb
Dec 30 23:43:39 arch kernel: __common_interrupt: 1.55 No irq handler for vector
Dec 30 23:43:39 arch kernel: __common_interrupt: 2.55 No irq handler for vector
Dec 30 23:43:39 arch kernel: __common_interrupt: 3.55 No irq handler for vector
Dec 30 23:43:39 arch kernel: __common_interrupt: 4.55 No irq handler for vector
Dec 30 23:43:39 arch kernel: __common_interrupt: 5.55 No irq handler for vector
Dec 30 23:43:39 arch kernel: __common_interrupt: 6.55 No irq handler for vector
Dec 30 23:43:39 arch kernel: __common_interrupt: 7.55 No irq handler for vector
Dec 30 23:43:39 arch kernel: __common_interrupt: 8.55 No irq handler for vector
Dec 30 23:43:39 arch kernel: __common_interrupt: 9.55 No irq handler for vector
Dec 30 23:43:39 arch kernel: __common_interrupt: 10.55 No irq handler for vector
Dec 30 23:43:39 arch kernel: sp5100-tco sp5100-tco: Watchdog hardware is disabled
Dec 30 23:43:40 arch kernel: nvidia-gpu 0000:26:00.3: i2c timeout error e0000000
Dec 30 23:43:40 arch kernel: ucsi_ccg 3-0008: i2c_transfer failed -110
Dec 30 23:43:40 arch kernel: ucsi_ccg 3-0008: ucsi_ccg_init failed - -110
Dec 30 23:43:40 arch kernel: sd 8:0:0:0: [sdb] No Caching mode page found
Dec 30 23:43:40 arch kernel: sd 8:0:0:0: [sdb] Assuming drive cache: write through 

dmesg
(of course these are just some interesting snippets)
[    0.156500] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[    0.168738] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-7f] only partially covers this bridge
[    2.206173] acpi_cpufreq: overriding BIOS provided _PSD data
[    2.286362] ccp 0000:28:00.1: ccp: unable to access the device: you might be running a broken BIOS.
[    3.374946] ucsi_ccg: probe of 3-0008 failed with error -110 

With my first install sometimes the system randomly froze during the startup of Arch. Also, the messages after the login prompt weren’t there sometimes. There were no freezes with this current install (yet) but since there still were these messages I thought there still is a or even the same problem.
At first I thought it has something to do with the GPU drivers. There were actually some additional errors with nouveau that I could see with dmesg and I also got an error like «nouveau … pmu:firmware unavailable» when booting the USB flash installation medium. I switched to nvidia drivers when It still was my first install but there were some differences to the current install. I think these «__common_interrupt: No irq handler for vector» were not there (really not sure) and I think the last two error messages that are after the login prompt «sd 8:0…: were also not there yet. Something else that is different is that with my current install at the end of the boot process is this: first there is nothing behind «Arch login:» , but right after that is shown there is a black screen for half a second and then the login prompt is back with the error messages. So that black screen is new. Also with systemd-boot there are two boot entries in my UEFI boot menu now while there was only one with efibootmgr, but that’s probably the firmware’s fault. (And no it’s not that one of them is from the first install.) Also when I enable the timeout option in the systemd-boot config the resolution is lower between selecting Arch and the login prompt for some reason. But those two things don’t bother me as much.
I read that there can be some problems with some hardware using EFISTUB so I might try GRUB.
The only other thing I could think of is adding some kernel parameters or maybe switching to linux-lts and nvidia-lts?
Currently the kernel parameters are default + amd microcode.

(rant)But usually the solutions to something nvidia related bring some disadvantages with them. I think most or all of my problems are Nvidia related and they are not fun. I also have some screen tearing and audio problems… I really want to switch to an AMD GPU but that’s not easy/cheap because of the GPU situation. Would the problems be the same on other Distros because they use the same driver and bootloader and kernel or should I maybe try another one until I have another GPU if there is no good fix to my problem?

Thanks

Last edited by JimNeedsHelp (2020-12-31 02:14:22)