Solved Errors at boot [SOLVED]

Solved issue
xlbooyahlx

xlbooyahlx

Well-Known Member
Joined
Jun 26, 2023
Messages
322
Reaction score
280
Credits
2,211
Been using mint for about six months now on multiple machines in the house.
The only one i get boot errors on is my Intel NUC11PHKi7C which has hybrid Intel/Nvidia RTX 2600 graphics.

Here's my system info:

Code: 
System:
  Kernel: 5.15.0-75-generic x86_64 bits: 64 compiler: gcc v: 11.3.0 Desktop: Cinnamon 5.6.8
    tk: GTK 3.24.33 wm: muffin dm: LightDM Distro: Linux Mint 21.1 Vera base: Ubuntu 22.04 jammy
Machine:
  Type: Mini-pc System: Intel Client Systems product: NUC11PHi7 v: M26149-404
    serial: <superuser required> Chassis: Intel Corporation type: 35 v: 2.0
    serial: <superuser required>
  Mobo: Intel model: NUC11PHBi7 v: M26151-403 serial: <superuser required> UEFI: Intel
    v: PHTGL579.0072.2023.0201.2226 date: 02/01/2023
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Touch Keyboard K400 serial: <filter>
    charge: 100% (should be ignored) status: Discharging
CPU:
  Info: quad core model: 11th Gen Intel Core i7-1165G7 bits: 64 type: MT MCP arch: Tiger Lake
    rev: 1 cache: L1: 320 KiB L2: 5 MiB L3: 12 MiB
  Speed (MHz): avg: 3262 high: 4231 min/max: 400/4700 cores: 1: 2738 2: 3511 3: 4231 4: 3488
    5: 3644 6: 3220 7: 3851 8: 1417 bogomips: 44851
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] driver: i915 v: kernel ports: active: none
    empty: DP-1, DP-2, DP-3, DP-4 bus-ID: 00:02.0 chip-ID: 8086:9a49
  Device-2: NVIDIA TU106M [GeForce RTX 2060 Mobile] vendor: Intel driver: nvidia v: 525.116.04
    pcie: speed: 2.5 GT/s lanes: 4 ports: active: none off: HDMI-A-1 empty: DP-5 bus-ID: 01:00.0
    chip-ID: 10de:1f15
  Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: modesetting,nvidia
    unloaded: fbdev,nouveau,vesa gpu: i915,nvidia display-ID: :0 screens: 1
  Screen-1: 0 s-res: 3072x1728 s-dpi: 120
  Monitor-1: HDMI-0 res: 3072x1728 dpi: 64 diag: 1397mm (55")
  OpenGL: renderer: NVIDIA GeForce RTX 2060/PCIe/SSE2 v: 4.6.0 NVIDIA 525.116.04
    direct render: Yes
Audio:
  Device-1: Intel Tiger Lake-LP Smart Sound Audio driver: snd_hda_intel v: kernel bus-ID: 00:1f.3
    chip-ID: 8086:a0c8
  Device-2: NVIDIA TU106 High Definition Audio vendor: Intel driver: snd_hda_intel v: kernel
    pcie: speed: 8 GT/s lanes: 4 bus-ID: 01:00.1 chip-ID: 10de:10f9
  Sound Server-1: ALSA v: k5.15.0-75-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Intel Wi-Fi 6 AX201 driver: iwlwifi v: kernel bus-ID: 00:14.3 chip-ID: 8086:a0f0
  IF: wlp0s20f3 state: up mac: <filter>
  Device-2: Intel Ethernet I225-LM driver: igc v: kernel pcie: speed: 5 GT/s lanes: 1 port: N/A
    bus-ID: 59:00.0 chip-ID: 8086:15f2
  IF: enp89s0 state: down mac: <filter>
  IF-ID-1: nordlynx state: unknown speed: N/A duplex: N/A mac: N/A
Bluetooth:
  Device-1: Intel AX201 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 3-10:6 chip-ID: 8087:0026
  Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block:
    hardware: no software: yes address: <filter>
Drives:
  Local Storage: total: 2.73 TiB used: 1.89 TiB (69.2%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 980 1TB size: 931.51 GiB speed: 31.6 Gb/s
    lanes: 4 serial: <filter> temp: 36.9 C
  ID-2: /dev/nvme1n1 vendor: Western Digital model: WD BLACK SN850X 2000GB size: 1.82 TiB
    speed: 63.2 Gb/s lanes: 4 serial: <filter> temp: 37.9 C
Partition:
  ID-1: / size: 136.68 GiB used: 20.66 GiB (15.1%) fs: ext4 dev: /dev/nvme0n1p2
  ID-2: /boot/efi size: 475.1 MiB used: 6.1 MiB (1.3%) fs: vfat dev: /dev/nvme0n1p1
Swap:
  ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile
Sensors:
  System Temperatures: cpu: 42.0 C mobo: N/A gpu: nvidia temp: 41 C
  Fan Speeds (RPM): N/A
Repos:
  Packages: 2437 apt: 2412 flatpak: 8 snap: 17
  No active apt repos in: /etc/apt/sources.list
  No active apt repos in: /etc/apt/sources.list.d/additional-repositories.list
  Active apt repos in: /etc/apt/sources.list.d/nordvpn.list
    1: deb https: //repo.nordvpn.com//deb/nordvpn/debian stable main
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
    1: deb http: //packages.linuxmint.com vera main upstream import backport
    2: deb http: //archive.ubuntu.com/ubuntu jammy main restricted universe multiverse
    3: deb http: //archive.ubuntu.com/ubuntu jammy-updates main restricted universe multiverse
    4: deb http: //archive.ubuntu.com/ubuntu jammy-backports main restricted universe multiverse
    5: deb http: //security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
  Active apt repos in: /etc/apt/sources.list.d/qbittorrent-team-qbittorrent-stable-jammy.list
    1: deb [arch=amd64 signed-by=/etc/apt/keyrings/qbittorrent-team-qbittorrent-stable-jammy.gpg] https: //ppa.launchpadcontent.net/qbittorrent-team/qbittorrent-stable/ubuntu jammy main
Info:
  Processes: 306 Uptime: 9m Memory: 31.01 GiB used: 2.76 GiB (8.9%) Init: systemd v: 249
  runlevel: 5 Compilers: gcc: 11.3.0 alt: 11/12 Client: Cinnamon v: 5.6.8 inxi: 3.3.13

And here are my errors at boot:

Code: 
 0.208645] ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS10._UPC], AE_ALREADY_EXISTS (20210730/dswload2-326)
[    0.208650] fbcon: Taking over console
[    0.208657] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
[    0.208659] ACPI: Skipping parse of AML opcode: Method (0x0014)
[    0.208661] ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS10._PLD], AE_ALREADY_EXISTS (20210730/dswload2-326)
[    0.208663] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
[    0.208665] ACPI: Skipping parse of AML opcode: Method (0x0014)


[    0.657323] pci 0000:00:07.0: PME# supported from D0 D3hot D3cold
[    0.657345] pci 0000:00:07.0: DPC: RP PIO log size 0 is invalid
[    0.659219] pci 0000:00:07.2: [8086:9a27] type 01 class 0x060400
[    0.659289] pci 0000:00:07.2: PME# supported from D0 D3hot D3cold
[    0.659311] pci 0000:00:07.2: DPC: RP PIO log size 0 is invalid
[    0.661173] pci 0000:00:08.0: [8086:9a11] type 00 class 0x088000

    8.416631] EDAC igen6: v2.5
[    8.442055] Serial bus multi instantiate pseudo device driver INT3515:00: IRQ index 1 not found
[    8.442059] Serial bus multi instantiate pseudo device driver INT3515:00: error -ENXIO: Error requesting irq at index 1: -6
[    8.443207] usblp 3-1.3:1.0: usblp1: USB Bidirectional printer dev 5 if 0 alt 0 proto 2 vid 0x04F9 pid 0x0402

[    9.496796] nvidia-gpu 0000:01:00.3: i2c timeout error e0000000
[    9.496803] ucsi_ccg 0-0008: i2c_transfer failed -110
[    9.496805] ucsi_ccg 0-0008: ucsi_ccg_init failed - -110
[    9.496807] ucsi_ccg: probe of 0-0008 failed with error -110

Are these errors I need to be worried about, or are they indicative of my system bios?
Thanks in advance to all who read, and, or answer ;)
 
Last edited:


G'day @xlbooyahlx and welcome to linux.org :)

This ACPI error is a non-fatal error that can occur, and I take it that you are still able to use the system, but if that is not the case, let us know. They are typically due to the way the manufacturer has laid down the BIOS/UEFI structure, and not due to the Linux kernel, and that is supported by the fact that it only affects one of your machines.

There is a bug report that was filed a year ago with Launchpad, which, if you read it here, you will see how closely it resembles what you are experiencing - https://bugs.launchpad.net/acpi/+bug/1978398

No activity on that since March, but in the report you will see a name Chris Guiver, and Chris, a fellow Aussie, is our own @guiverc , so by my mentioning him, he will be alerted, and may swing by and let us know of any progress in that regard. Chris is on the Ubuntu/Lubuntu team, as is another of our Members.

Given you are on Mint Vera Cinnamon and have been using Mint for a while, you likely know of Timeshift, and I would advocate taking an on demand snapshot before monkeying with anything so you can restore if things go awry.

It is possible that the nVidia drivers did not load properly, and so you could try using the generic Nouveau drivers instead.

It may also be useful if you give us the output from

Code: 
cat /etc/default/grub

so that another helper with more ideas/knowledge than me can make suggestions.

I'll leave you with it but keep an eye on this thread.

Cheers

Chris Turner
wizardfromoz
 
wizardfromoz said:
so by my mentioning him, he will be alerted, and may swing by and let us know of any progress in that regard.
Click to expand...
Sorry I can't offer anything.

My reply was just part of bug-triage, in that the bug report appears to have been filed online (via web browser) thus the fields usually used in evaluating & exploring the issue (& linking with other reports) was never filled. That could have been done via ubuntu-bug linux at initial filing, or even apport-collect by the original poster of the bug report.

It appears I didn't add it to any bug tracking list for me to notice it again either (except by chance on change via IRC for changes made when my box is on; ie. AEST 0800-2230).

I saw it impacting users of jammy and kinetic there (5.15 & 5.19 kernels), but none for lunar (6.2) with that kernel now available (in proposed via edge) for jammy, so that maybe worth testing (only lunar ISOs are available with 6.2, or mantic with 6.3 if your system won't allow different kernel stacks to co-exist such as using nvidia kernel modules), if interested in testing other stacks, but sorry I know nothing about the bug, the issue & can't help. (FYI: The reason for mention of newer kernels was even the links on upstream bugzilla.kernel.org appeared older - but I only quickly scanned)
 
guiverc said:
My reply was just part of bug-triage...
Click to expand...

Thanks, Chris, I wondered as much.

For the OP to be seeing these errors, I expect he may be using "noquiet nosplash" or similar in his /etc/default/grub (I always do).

He may benefit by adding the option acpi=off there, given the errors are non-fatal, but I may just wait until someone more skilled than I in this regard comes along.

Cheers

(other) Chris
 
GRUB_CMDLINE_LINUX_DEFAULT="quiet loglevel=3"
GRUB_CMDLINE_LINUX_DEFAULT="acpi=off"
 
wizardfromoz said:
It may also be useful if you give us the output from

Code: 
cat /etc/default/grub

so that another helper with more ideas/knowledge than me can make suggestions.

I'll leave you with it but keep an eye on this thread.

Cheers

Chris Turner
wizardfromoz
Click to expand...
Code: 
GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=0
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""


Here's the output you asked for (I believe?), and thank you for your insight, and time.

As to Brickwizard's link, I'll do that right now and hope I don't bork anything.
I've got up to date snapshots ready!
I've distro hopped quite a bit on this particular machine, and Mint was the only one that gave me smooth video playback right out of the box (all my machines are HTPCs as well as general purpose running 43" to 55" 4KTVs), so video playback is one of my must haves.

Thank you all, and I'll report back!
 
Condobloke said:
GRUB_CMDLINE_LINUX_DEFAULT="quiet loglevel=3"
GRUB_CMDLINE_LINUX_DEFAULT="acpi=off"
Click to expand...
I edited my grub to that, and after "sudo update-grub2" then rebooted to the longest line of code I'd ever seen with failure to boot, then had to timeshift back.
 
Brickwizard said:
Another possibility is that it may be caused by the Nividia , possible solution ... https://community.linuxmint.com/tutorial/view/176
Click to expand...
no mention of nouveau. in my grub to edit.

Code: 
Graphics:
  Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] driver: i915 v: kernel
    bus-ID: 00:02.0
  Device-2: NVIDIA TU106M [GeForce RTX 2060 Mobile] vendor: Intel
    driver: nvidia v: 525.116.04 bus-ID: 01:00.0
  Display: x11 server: X.Org v: 1.21.1.4 driver: X:
    loaded: modesetting,nvidia unloaded: fbdev,nouveau,vesa gpu: i915,nvidia
    resolution: 3072x1728~60Hz
  OpenGL: renderer: NVIDIA GeForce RTX 2060/PCIe/SSE2
    v: 4.6.0 NVIDIA 525.116.04 direct render: Yes
 
Last edited:
z7vl7abxc said:
are you having any issues with the system or were you just inquiring about the boot errors?
Click to expand...
No issues at all.
I uderstand the ACPI errors are common.
However the Nvidia errors, were concerning.

Code: 
[    9.496796] nvidia-gpu 0000:01:00.3: i2c timeout error e0000000
[    9.496803] ucsi_ccg 0-0008: i2c_transfer failed -110
[    9.496805] ucsi_ccg 0-0008: ucsi_ccg_init failed - -110
[    9.496807] ucsi_ccg: probe of 0-0008 failed with error -110

Just wanted to know if I should be correcting anything. TY ;)
 
agreed. i'd be concerned about similar errors. i read through the thread a couple of times and didn't see anything else listed or mentioned so i wanted to check to make sure.

i use the xfce version of mint so i don't know if the other versions (in case you are using cinnamon or mate) come with a log viewer. if the version you are using has one (or if you are comfortable with dmesg and/or journalctl), are there any other nvidia related errors or warnings that show up regularly after the boot sequence?
 
Ok I found this in a post here:
https://forums.opensuse.org/t/nvidia-gpu-i2c-timeout-error-e0000000/142077
Below messages are harmless and shouldn’t impact any functionality.
nvidia-gpu 0000:01:00.3: i2c timeout error e0000000
ucsi_ccg 0-0008: i2c_transfer failed -110
ucsi_ccg 0-0008: ucsi_ccg_init failed - -110
ucsi_ccg: probe of 0-0008 failed with error -110
Click to expand...

From reading that bug report, it looks like they introduced some code in the kernel for NVIDIA graphics cards which have a USB Type-C interface and when that is the case the NVIDIA I2C driver is loaded. I think the detection logic is at fault and the I2C drivers seems to be incorrectly loaded when no compatible hardware is present.


Anyway, at the end of the bug report a patch was made and you just need to wait for this patch to be merged into the mainline kernel and turn up as a kernel update.


The error messages are harmless.
Click to expand...

The post was from Sept. of 2020 on an opensuse forum that I just stumbled upon while searching the error once again in a deep dive.
In the past I've tried newer kernels up to 6.?, but they just intoduce new problems such as crackling audio during video playback. Since apparently the errors aren't harmful, I'm at peace for now. :)


Thanks to all that answered
 
z7vl7abxc said:
agreed. i'd be concerned about similar errors. i read through the thread a couple of times and didn't see anything else listed or mentioned so i wanted to check to make sure.

i use the xfce version of mint so i don't know if the other versions (in case you are using cinnamon or mate) come with a log viewer. if the version you are using has one (or if you are comfortable with dmesg and/or journalctl), are there any other nvidia related errors or warnings that show up regularly after the boot sequence?
Click to expand...

dmesg was in my OP, and journalct shows nothing unusual, see my previous post, I believe I found the answer, and thank you ;)
 
Apparently the message where I found the answer is still listed as "This message is awaiting moderator approval, and is invisible to normal visitors." maybe because there's an ouside link??
Hopefully it will get approved quickly.
Thanks to all that read, and posted :)
From a post in Sept 2020:
Below messages are harmless and shouldn’t impact any functionality.
nvidia-gpu 0000:01:00.3: i2c timeout error e0000000
ucsi_ccg 0-0008: i2c_transfer failed -110
ucsi_ccg 0-0008: ucsi_ccg_init failed - -110
ucsi_ccg: probe of 0-0008 failed with error -110
Click to expand...

From reading that bug report, it looks like they introduced some code in the kernel for NVIDIA graphics cards which have a USB Type-C interface and when that is the case the NVIDIA I2C driver is loaded. I think the detection logic is at fault and the I2C drivers seems to be incorrectly loaded when no compatible hardware is present.


Anyway, at the end of the bug report a patch was made and you just need to wait for this patch to be merged into the mainline kernel and turn up as a kernel update.


The error messages are harmless.
Click to expand...
 
Last edited:
if i recall correctly my first few posts with links got held up in moderation as well. thank you for sharing the added info. i hope the system continues to work well for you
 
xlbooyahlx said:
...maybe because there's an ouside link??
Click to expand...

Yes - anti-spam protocol. It's either 5 Posts or 5 days, I forget which, in any event you should be fine soon.

Staff are in USA, England and Australia (me), so depending on the locale post from it can take some time.

GRUB_CMDLINE_LINUX_DEFAULT="quiet loglevel=3"
GRUB_CMDLINE_LINUX_DEFAULT="acpi=off"
Click to expand...

I believe those should have been combined in the one line, regrets on that. Also, only

Code: 
sudo update-grub

is required.

If you wish to pursue the nVidia side of things further, the following article I believe to be far more current than that previously provided, and is along the lines of what I was referencing when I said

wizardfromoz said:
It is possible that the nVidia drivers did not load properly, and so you could try using the generic Nouveau drivers instead.
Click to expand...

Install nVidia Drivers

Cheers

Wizard
 
GRUB_CMDLINE_LINUX_DEFAULT="quiet loglevel=3"
GRUB_CMDLINE_LINUX_DEFAULT="acpi=off"
Click to expand...

I believe those should have been combined in the one line, regrets on that.

those lines above show on separate lines in my grub....and all is well.
 
My bad, I plead the 5th (oops, wrong country)
 
You must log in or register to reply here.

Members online

Total: 434 (members: 7, guests: 427)

Latest posts

Top