My RP PIO log size is invalid (???)

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Kurt3162
Level 4
Level 4
Posts: 480
Joined: Wed Apr 02, 2014 2:05 pm

My RP PIO log size is invalid (???)

Post by Kurt3162 »

Since I first installed Mint 21.0 on this (then brand new) computer, on boot it always gives me a number of (fleeting) errors.
It's a fast computer (i7-12700H), and I had to film the screen to be able to read them.
Aside those recurring error messages, everything works as expected, so I didn't think anything about it (except that it is new hardware Linux doesn't fully understand yet). Until I found that "RP PIO log" bit on the "Important" tab in the "Logs" app. So it seems to be important after all?
An Internet search didn't yield anything conclusive, besides telling me that a "PIO" is a "Programmable Input/Output" (bless you :roll:)...

Can anybody explain what's going on, if I should do something about it, and what? :shock:

At boot I always see:

Code: Select all

[0.499242] pci 0000:00:07.0: DPC: RP PIO log size 0 is invalid
           (same error 3 times)
At Shutdown I always get (is it related?):

Code: Select all

[OK] Reached target Late Shutdown Services
[OK] Finished System Power Off
[OK] Reached target System Poweer Off.
[120.592325] sd-umoun[3909]: Failed to unmount /oldroot: Device or resource busy
[120.592325] sd-umoun[3990]: Failed to unmount /oldroot/sys: Device or resource busy
[120.592325] shutdown[1]: Failed to finalize file systems, ignoring.


That's the system:

Code: Select all

inxi -fxz
CPU:
  Info: 14-core (6-mt/8-st) model: 12th Gen Intel Core i7-12700H bits: 64
    type: MST AMCP arch: Alder Lake rev: 3 cache: L1: 1.2 MiB L2: 11.5 MiB
    L3: 24 MiB
  Speed (MHz): avg: 565 high: 762 min/max: 400/4679:4700:3500 cores: 1: 716
    2: 762 3: 608 4: 602 5: 437 6: 416 7: 500 8: 574 9: 464 10: 588 11: 613
    12: 657 13: 692 14: 602 15: 492 16: 442 17: 547 18: 464 19: 667 20: 461
    bogomips: 107520
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
    arch_capabilities arch_lbr arch_perfmon art avx avx2 avx_vnni bmi1 bmi2 bts
    clflush clflushopt clwb cmov constant_tsc cpuid cpuid_fault cx16 cx8 de
    ds_cpl dtes64 dtherm dts epb ept ept_ad erms est f16c flexpriority
    flush_l1d fma fpu fsgsbase fsrm fxsr gfni ht hwp hwp_act_window hwp_epp
    hwp_notify hwp_pkg_req ibpb ibrs ibrs_enhanced ida intel_pt invpcid
    invpcid_single lahf_lm lm mca mce md_clear mmx monitor movbe movdir64b
    movdiri msr mtrr nonstop_tsc nopl nx ospke pae pat pbe pcid pclmulqdq
    pdcm pdpe1gb pebs pge pku pln pni popcnt pse pse36 pts rdpid rdrand
    rdseed rdtscp rep_good sdbg sep serialize sha_ni smap smep smx
    split_lock_detect ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm
    tm2 tpr_shadow tsc tsc_adjust tsc_deadline_timer tsc_known_freq umip vaes
    vme vmx vnmi vpclmulqdq vpid waitpkg x2apic xgetbv1 xsave xsavec xsaveopt
    xsaves xtopology xtpr

-----------------------------------------------

inxi -Fxxxrz
System:
  Kernel: 5.15.0-58-generic x86_64 bits: 64 compiler: gcc v: 11.3.0
    Desktop: Cinnamon 5.6.6 tk: GTK 3.24.33 wm: muffin vt: 7 dm: LightDM 1.30.0
    Distro: Linux Mint 21.1 Vera base: Ubuntu 22.04 jammy
Machine:
  Type: Laptop System: Alienware product: Alienware x17 R2 v: 1.11.0
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: Alienware model: 04HR81 v: A01 serial: <superuser required>
    UEFI: Alienware v: 1.11.0 date: 12/14/2022
Battery:
  ID-1: BAT1 charge: 87.0 Wh (100.0%) condition: 87.0/87.0 Wh (100.0%)
    volts: 13.0 min: 11.4 model: COMPAL PABAS0241231 type: Li-ion
    serial: <filter> status: Full cycles: 6
CPU:
  Info: 14-core (6-mt/8-st) model: 12th Gen Intel Core i7-12700H bits: 64
    type: MST AMCP smt: enabled arch: Alder Lake rev: 3 cache: L1: 1.2 MiB
    L2: 11.5 MiB L3: 24 MiB
  Speed (MHz): avg: 482 high: 741 min/max: 400/4679:4700:3500 cores: 1: 433
    2: 440 3: 475 4: 579 5: 643 6: 697 7: 433 8: 419 9: 435 10: 550 11: 422
    12: 405 13: 400 14: 400 15: 400 16: 459 17: 496 18: 741 19: 442 20: 384
    bogomips: 107520
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel Alder Lake-P Integrated Graphics vendor: Dell driver: i915
    v: kernel ports: active: eDP-1
    empty: DP-1, DP-2, DP-3, HDMI-A-1, HDMI-A-2, HDMI-A-3
    bus-ID: 0000:00:02.0 chip-ID: 8086:46a6 class-ID: 0300
  Device-2: NVIDIA vendor: Dell driver: nvidia v: 525.60.11 ports:
    active: none empty: DP-4, DP-5, HDMI-A-4, eDP-2 bus-ID: 0000:01:00.0
    chip-ID: 10de:24e0 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.3 driver: X:
    loaded: modesetting,nvidia unloaded: fbdev,nouveau,vesa gpu: i915
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 98 s-size: 499x280mm (19.6x11.0")
    s-diag: 572mm (22.5")
  Monitor-1: eDP-1 model: LG res: 1920x1080 hz: 165 dpi: 128
    size: 382x215mm (15.0x8.5") diag: 438mm (17.3") modes: 1920x1080
  OpenGL: renderer: Mesa Intel Graphics (ADL GT2) v: 4.6 Mesa 22.0.5
    direct render: Yes
Audio:
  Device-1: Intel Alder Lake PCH-P High Definition Audio vendor: Dell
    driver: sof-audio-pci-intel-tgl bus-ID: 0000:00:1f.3 chip-ID: 8086:51c8
    class-ID: 0401
  Device-2: NVIDIA GA104 High Definition Audio driver: snd_hda_intel
    v: kernel bus-ID: 0000:01:00.1 chip-ID: 10de:228b class-ID: 0403
  Sound Server-1: ALSA v: k5.15.0-58-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 Alder Lake-P PCH CNVi WiFi vendor: Rivet Networks
    driver: iwlwifi v: iwlwifi-stack-public:master:9858:4c7cba27
    bus-ID: 0000:00:14.3 chip-ID: 8086:51f0 class-ID: 0280
  IF: wlo1 state: up mac: <filter>
  Device-2: Realtek Killer E3000 2.5GbE vendor: Dell driver: r8169
    v: kernel port: 3000 bus-ID: 0000:2c:00.0 chip-ID: 10ec:3000 class-ID: 0200
  IF: enp44s0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel type: USB driver: btusb v: 0.8 bus-ID: 3-10:6
    chip-ID: 8087:0033 class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 0 state: down
    bt-service: enabled,running rfk-block: hardware: no software: yes
    address: <filter>
RAID:
  Hardware-1: Intel Volume Management Device NVMe RAID Controller driver: vmd
    v: 0.6 port: N/A bus-ID: 0000:00:0e.0 chip-ID: 8086:467f rev:
    class-ID: 0104
Drives:
  Local Storage: total: 3.68 TiB used: 489.38 GiB (13.0%)
  ID-1: /dev/nvme0n1 model: CA6-8D2048-Q11 NVMe SSSTC 2048GB size: 1.86 TiB
    speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter> rev: 24201114
    temp: 19.9 C scheme: GPT
  ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 980 PRO 2TB size: 1.82 TiB
    speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter> rev: 5B2QGXA7
    temp: 24.9 C scheme: GPT
Partition:
  ID-1: / size: 97.87 GiB used: 33.91 GiB (34.6%) fs: ext4
    dev: /dev/nvme0n1p4
  ID-2: /boot/efi size: 236 MiB used: 99.8 MiB (42.3%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-3: /home size: 97.87 GiB used: 13.94 GiB (14.2%) fs: ext4
    dev: /dev/nvme1n1p4
Swap:
  ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2
    file: /swapfile
Sensors:
  System Temperatures: cpu: 22.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: 3050 apt: 3030 flatpak: 20
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/additional-repositories.list
    1: deb [arch=amd64 signed-by=/usr/share/keyrings/oracle_vbox.gpg] https://download.virtualbox.org/virtualbox/debian jammy contrib
  Active apt repos in: /etc/apt/sources.list.d/google-earth-pro.list
    1: deb [arch=amd64] http://dl.google.com/linux/earth/deb/ stable main
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
    1: deb https://ftp-stud.hs-esslingen.de/pub/Mirrors/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/signal-xenial.list
    1: deb [arch=amd64 signed-by=/usr/share/keyrings/signal-desktop-keyring.gpg] https://updates.signal.org/desktop/apt xenial main
  Active apt repos in: /etc/apt/sources.list.d/vivaldi.list
    1: deb [arch=amd64] https://repo.vivaldi.com/stable/deb/ stable main
  Active apt repos in: /etc/apt/sources.list.d/winehq-jammy.sources
    1: deb [arch=amd64 i386] https://dl.winehq.org/wine-builds/ubuntu jammy main
Info:
  Processes: 423 Uptime: 35m wakeups: 3 Memory: 31.03 GiB
  used: 3.01 GiB (9.7%) Init: systemd v: 249 runlevel: 5 Compilers:
  gcc: 11.3.0 alt: 11 Shell: Bash v: 5.1.16 running-in: gnome-terminal
  inxi: 3.3.13
Last edited by LockBot on Sat Sep 23, 2023 10:00 pm, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
User avatar
SMG
Level 25
Level 25
Posts: 31318
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: My RP PIO log size is invalid (???)

Post by SMG »

Kurt3162 wrote: Thu Mar 23, 2023 11:13 amSince I first installed Mint 21.0 on this (then brand new) computer, on boot it always gives me a number of (fleeting) errors.
Two things to keep in mind for the future:
1) Not all messages on the screen are errors.
2) One can get the messages in the logs.

You have very new hardware and with a 12th-gen Intel CPU it would be better to run a newer kernel version. Recommendation is after the explanation of your question.
Kurt3162 wrote: Thu Mar 23, 2023 11:13 amAt boot I always see:

Code: Select all

[0.499242] pci 0000:00:07.0: DPC: RP PIO log size 0 is invalid
           (same error 3 times)
I found this bug report Bug 209943 - pci 0000:00:07.0: DPC: RP PIO log size 0 is invalid In Comment 44 it indicates:
The patch should end up in distro kernels eventually. I suggest just ignoring the error for now. It really is just a message so it does not affect the funtionality in any way (unless you intent to use PCIe DPC of those root ports).
and comment 52 indicates:
The patch quirking these PCIe root ports was picked up by the PCI maintainer (Bjorn) and should land in v6.1 kernel release.
If you want to see if the 6.1-oem kernel has removed the issue, you can install the latest 6.1-oem kernel with

Code: Select all

sudo apt-get install linux-oem-22.04c
and reboot.
Kurt3162 wrote: Thu Mar 23, 2023 11:13 amAt Shutdown I always get (is it related?):

Code: Select all

[OK] Reached target Late Shutdown Services
[OK] Finished System Power Off
[OK] Reached target System Poweer Off.
[120.592325] sd-umoun[3909]: Failed to unmount /oldroot: Device or resource busy
[120.592325] sd-umoun[3990]: Failed to unmount /oldroot/sys: Device or resource busy
[120.592325] shutdown[1]: Failed to finalize file systems, ignoring.
If any of these were really problems, your computer would not shut down. Because you have not indicated otherwise, I presume it is shutting down (hence the "ignoring" message).
Image
A woman typing on a laptop with LM20.3 Cinnamon.
Kurt3162
Level 4
Level 4
Posts: 480
Joined: Wed Apr 02, 2014 2:05 pm

Re: My RP PIO log size is invalid (???)

Post by Kurt3162 »

Thanks for your reply!
SMG wrote: Sun Mar 26, 2023 7:24 pm 1) Not all messages on the screen are errors.
2) One can get the messages in the logs.
1. Error or not, something claiming being "invalid" doesn't sound too normal to me...
2. I've looked in the logs, and that's why I posted here, as the "Logs" program ("gnome-logs") labeled it "important". I knew the issue wasn't critical since I've had it since the beginning, but I assumed "Logs" knows more than I do (which isn't difficult).

SMG wrote: Sun Mar 26, 2023 7:24 pm If you want to see if the 6.1-oem kernel has removed the issue, you can install the latest 6.1-oem kernel
:shock: Uh, no, thanks, this is my work computer, I definitely don't want to risk breaking it in any way.
(Unless of course it risks having problems if I don't.)

SMG wrote: Sun Mar 26, 2023 7:24 pmIf any of these were really problems, your computer would not shut down. Because you have not indicated otherwise, I presume it is shutting down (hence the "ignoring" message).
Since the very beginning I always get at boot a "Press Ctrl+C to cancel all file system checks in progress" message I've already posted about. Now seeing this message I wondered if the statement "Failed to finalize file systems" at shutdown could be related, if not the cause for this constant need for file system checks.
The solution I was given back then was to disable checks: Obviously, no checks means no failed checks either... :roll:

Now, as I said I don't know anything, but I'm pretty sure that if somebody bothered building some "file system finalizing" procedure at that point, is wasn't just for fun and laughs, it must serve some purpose, doesn't it. I could understand my cutting edge NVME SSDs being too fast or just not what Mint expects, the (only) point is, what can/should I do about it? :shock:
As I said, work computer, very important to me, so I'd like it to be working perfectly, not just "good enough".


Of course, as I said in my first post, I know this is cutting edge hardware and it will take some time before Linux drivers manage to get it all under control, but until then I want to be sure I won't have any catastrophe coming to me. :shock:
User avatar
Pjotr
Level 23
Level 23
Posts: 19884
Joined: Mon Mar 07, 2011 10:18 am
Location: The Netherlands (Holland) 🇳🇱
Contact:

Re: My RP PIO log size is invalid (???)

Post by Pjotr »

Kurt3162 wrote: Mon Mar 27, 2023 4:33 am
SMG wrote: Sun Mar 26, 2023 7:24 pm If you want to see if the 6.1-oem kernel has removed the issue, you can install the latest 6.1-oem kernel
:shock: Uh, no, thanks, this is my work computer, I definitely don't want to risk breaking it in any way.
That official and reliable kernel won't break anything. Furthermore, if it performs unsatisfactorily, you can always simply boot from the previous kernel and remove the offending newer one. I strongly recommend to install it (reboot afterwards):

Code: Select all

sudo apt-get install linux-oem-22.04c
This is how to filter out unimportant error messages during booting:
https://easylinuxtipsproject.blogspot.c ... .html#ID19
(item 19)
Tip: 10 things to do after installing Linux Mint 21.3 Virginia
Keep your Linux Mint healthy: Avoid these 10 fatal mistakes
Twitter: twitter.com/easylinuxtips
All in all, horse sense simply makes sense.
Kurt3162
Level 4
Level 4
Posts: 480
Joined: Wed Apr 02, 2014 2:05 pm

Re: My RP PIO log size is invalid (???)

Post by Kurt3162 »

Pjotr wrote: Mon Mar 27, 2023 4:51 am install linux-oem-22.04c
I'm a little confused here, which kernel version number would that be?
There is no "5.22.0-4" on ~kernel-ppa/mainline (but then again I don't see the 5.19.0-35 I'm currently using either...).

I assume this is a totally different kernel naming scheme, meant to confuse the uninitiated?... :roll:

Pjotr wrote: Mon Mar 27, 2023 4:51 am This is how to filter out unimportant error messages during booting:
https://easylinuxtipsproject.blogspot.c ... .html#ID19
Thanks, will do (although since I'm a noob I'm quite uncomfortable with hiding (potentially important) information).
User avatar
Pjotr
Level 23
Level 23
Posts: 19884
Joined: Mon Mar 07, 2011 10:18 am
Location: The Netherlands (Holland) 🇳🇱
Contact:

Re: My RP PIO log size is invalid (???)

Post by Pjotr »

Kurt3162 wrote: Mon Mar 27, 2023 5:29 am
Pjotr wrote: Mon Mar 27, 2023 4:51 am install linux-oem-22.04c
I'm a little confused here, which kernel version number would that be?
Currently the 6.1.x.
Tip: 10 things to do after installing Linux Mint 21.3 Virginia
Keep your Linux Mint healthy: Avoid these 10 fatal mistakes
Twitter: twitter.com/easylinuxtips
All in all, horse sense simply makes sense.
Kurt3162
Level 4
Level 4
Posts: 480
Joined: Wed Apr 02, 2014 2:05 pm

Re: My RP PIO log size is invalid (???)

Post by Kurt3162 »

I see, thanks.
Any explanation/resource on why it is called "22.04" instead of "6.1.x"?

Or am I right about the uninitiated?...
User avatar
Pjotr
Level 23
Level 23
Posts: 19884
Joined: Mon Mar 07, 2011 10:18 am
Location: The Netherlands (Holland) 🇳🇱
Contact:

Re: My RP PIO log size is invalid (???)

Post by Pjotr »

Kurt3162 wrote: Mon Mar 27, 2023 5:44 am I see, thanks.
Any explanation/resource on why it is called "22.04" instead of "6.1.x"?
It's a meta package for Ubuntu 22.04 / Mint 21.x with varying dependencies ("payload"). See also:
https://wiki.ubuntu.com/Kernel/OEMKernel
Tip: 10 things to do after installing Linux Mint 21.3 Virginia
Keep your Linux Mint healthy: Avoid these 10 fatal mistakes
Twitter: twitter.com/easylinuxtips
All in all, horse sense simply makes sense.
Kurt3162
Level 4
Level 4
Posts: 480
Joined: Wed Apr 02, 2014 2:05 pm

Re: My RP PIO log size is invalid (???)

Post by Kurt3162 »

Great! Thank you.
User avatar
SMG
Level 25
Level 25
Posts: 31318
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: My RP PIO log size is invalid (???)

Post by SMG »

Kurt3162 wrote: Mon Mar 27, 2023 4:33 am2. I've looked in the logs, and that's why I posted here, as the "Logs" program ("gnome-logs") labeled it "important". I knew the issue wasn't critical since I've had it since the beginning, but I assumed "Logs" knows more than I do (which isn't difficult).
I meant checking syslog (text file in /var/log/syslog) or checking journalctl or dmesg (which are run from the terminal).
Kurt3162 wrote: Mon Mar 27, 2023 4:33 am
SMG wrote: Sun Mar 26, 2023 7:24 pmIf any of these were really problems, your computer would not shut down. Because you have not indicated otherwise, I presume it is shutting down (hence the "ignoring" message).
Since the very beginning I always get at boot a "Press Ctrl+C to cancel all file system checks in progress" message I've already posted about. Now seeing this message I wondered if the statement "Failed to finalize file systems" at shutdown could be related, if not the cause for this constant need for file system checks.
The solution I was given back then was to disable checks: Obviously, no checks means no failed checks either... :roll:
I checked the other topic and you indicated it is being triggered by your /home.

Case matters when running the inxi command and you used inxi -fxz when we normally recommend running inxi -Fxxxrz (notice the upper case f), so we don't know your partition info to have a guess as to why you are getting that message about canceling file system checks.

I think Pjotr addressed most of your kernel concerns and questions. The kernel I recommended you to install is not a mainline kernel. It is an OEM Kernels which is created and maintained by Canonical (Ubuntu) based on the 6.1 mainline kernel (similar to how the rest of their kernels are based on mainline kernels, but there are some slight differences to OEM kernels).
Image
A woman typing on a laptop with LM20.3 Cinnamon.
Kurt3162
Level 4
Level 4
Posts: 480
Joined: Wed Apr 02, 2014 2:05 pm

Re: My RP PIO log size is invalid (???)

Post by Kurt3162 »

SMG wrote: Mon Mar 27, 2023 10:41 am you used inxi -fxz when we normally recommend running inxi -Fxxxrz
Oops, sorry, mea culpa, copy-paste error. :shock:
Here it is:

Code: Select all

:~$ inxi -Fxxxrz
System:
  Kernel: 5.15.0-67-generic x86_64 bits: 64 compiler: gcc v: 11.3.0
    Desktop: Cinnamon 5.6.8 tk: GTK 3.24.33 wm: muffin vt: 7 dm: LightDM 1.30.0
    Distro: Linux Mint 21.1 Vera base: Ubuntu 22.04 jammy
Machine:
  Type: Laptop System: Alienware product: Alienware x17 R2 v: 1.12.2
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: Alienware model: 04HR81 v: A01 serial: <superuser required>
    UEFI: Alienware v: 1.12.2 date: 02/24/2023
Battery:
  ID-1: BAT1 charge: 87.0 Wh (100.0%) condition: 87.0/87.0 Wh (100.0%)
    volts: 12.9 min: 11.4 model: COMPAL PABAS0241231 type: Li-ion
    serial: <filter> status: Full cycles: 6
CPU:
  Info: 14-core (6-mt/8-st) model: 12th Gen Intel Core i7-12700H bits: 64
    type: MST AMCP smt: enabled arch: Alder Lake rev: 3 cache: L1: 1.2 MiB
    L2: 11.5 MiB L3: 24 MiB
  Speed (MHz): avg: 581 high: 936 min/max: 400/4600:4700:3500 cores: 1: 739
    2: 936 3: 796 4: 496 5: 657 6: 546 7: 807 8: 400 9: 458 10: 552 11: 525
    12: 557 13: 400 14: 464 15: 503 16: 600 17: 554 18: 575 19: 429 20: 635
    bogomips: 107520
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel Alder Lake-P Integrated Graphics vendor: Dell driver: i915
    v: kernel ports: active: eDP-1
    empty: DP-1, DP-2, DP-3, HDMI-A-1, HDMI-A-2, HDMI-A-3
    bus-ID: 0000:00:02.0 chip-ID: 8086:46a6 class-ID: 0300
  Device-2: NVIDIA vendor: Dell driver: nvidia v: 525.85.05 ports:
    active: none empty: DP-4, DP-5, HDMI-A-4, eDP-2 bus-ID: 0000:01:00.0
    chip-ID: 10de:24e0 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.3 driver: X:
    loaded: modesetting,nvidia unloaded: fbdev,nouveau,vesa gpu: i915
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 98 s-size: 499x280mm (19.6x11.0")
    s-diag: 572mm (22.5")
  Monitor-1: eDP-1 model: LG res: 1920x1080 hz: 165 dpi: 128
    size: 382x215mm (15.0x8.5") diag: 438mm (17.3") modes: 1920x1080
  OpenGL: renderer: Mesa Intel Graphics (ADL GT2) v: 4.6 Mesa 22.2.5
    direct render: Yes
Audio:
  Device-1: Intel Alder Lake PCH-P High Definition Audio vendor: Dell
    driver: sof-audio-pci-intel-tgl bus-ID: 0000:00:1f.3 chip-ID: 8086:51c8
    class-ID: 0401
  Device-2: NVIDIA GA104 High Definition Audio driver: snd_hda_intel
    v: kernel bus-ID: 0000:01:00.1 chip-ID: 10de:228b class-ID: 0403
  Sound Server-1: ALSA v: k5.15.0-67-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 Alder Lake-P PCH CNVi WiFi vendor: Rivet Networks
    driver: iwlwifi v: iwlwifi-stack-public:master:9858:4c7cba27
    bus-ID: 0000:00:14.3 chip-ID: 8086:51f0 class-ID: 0280
  IF: wlo1 state: up mac: <filter>
  Device-2: Realtek Killer E3000 2.5GbE vendor: Dell driver: r8169
    v: kernel port: 3000 bus-ID: 0000:2c:00.0 chip-ID: 10ec:3000 class-ID: 0200
  IF: enp44s0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel type: USB driver: btusb v: 0.8 bus-ID: 3-10:6
    chip-ID: 8087:0033 class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 0 state: down
    bt-service: enabled,running rfk-block: hardware: no software: yes
    address: <filter>
RAID:
  Hardware-1: Intel Volume Management Device NVMe RAID Controller driver: vmd
    v: 0.6 port: N/A bus-ID: 0000:00:0e.0 chip-ID: 8086:467f rev:
    class-ID: 0104
Drives:
  Local Storage: total: 3.68 TiB used: 498.84 GiB (13.2%)
  ID-1: /dev/nvme0n1 model: CA6-8D2048-Q11 NVMe SSSTC 2048GB size: 1.86 TiB
    speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter> rev: 24201114
    temp: 19.9 C scheme: GPT
  ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 980 PRO 2TB size: 1.82 TiB
    speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter> rev: 5B2QGXA7
    temp: 24.9 C scheme: GPT
Partition:
  ID-1: / size: 97.87 GiB used: 27.23 GiB (27.8%) fs: ext4
    dev: /dev/nvme0n1p4
  ID-2: /boot/efi size: 236 MiB used: 100.6 MiB (42.6%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-3: /home size: 97.87 GiB used: 14.1 GiB (14.4%) fs: ext4
    dev: /dev/nvme1n1p4
Swap:
  ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2
    file: /swapfile
Sensors:
  System Temperatures: cpu: 23.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: 3033 apt: 3021 flatpak: 12
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/additional-repositories.list
    1: deb [arch=amd64 signed-by=/usr/share/keyrings/oracle_vbox.gpg] https://download.virtualbox.org/virtualbox/debian jammy contrib
  Active apt repos in: /etc/apt/sources.list.d/google-earth-pro.list
    1: deb [arch=amd64] http://dl.google.com/linux/earth/deb/ 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/signal-xenial.list
    1: deb [arch=amd64 signed-by=/usr/share/keyrings/signal-desktop-keyring.gpg] https://updates.signal.org/desktop/apt xenial main
  Active apt repos in: /etc/apt/sources.list.d/vivaldi.list
    1: deb [arch=amd64] https://repo.vivaldi.com/stable/deb/ stable main
  Active apt repos in: /etc/apt/sources.list.d/winehq-jammy.sources
    1: deb [arch=amd64 i386] https://dl.winehq.org/wine-builds/ubuntu jammy main
Info:
  Processes: 445 Uptime: 1m wakeups: 3 Memory: 31.03 GiB used: 2.3 GiB (7.4%)
  Init: systemd v: 249 runlevel: 5 Compilers: gcc: 11.3.0 alt: 11/12
  Shell: Bash v: 5.1.16 running-in: gnome-terminal inxi: 3.3.13

SMG wrote: Mon Mar 27, 2023 10:41 amThe kernel I recommended you to install is not a mainline kernel. It is an OEM Kernels which is created and maintained by Canonical (Ubuntu) based on the 6.1 mainline kernel (similar to how the rest of their kernels are based on mainline kernels, but there are some slight differences to OEM kernels).
Sure, what I wanted to know is a. in what way it is different from the official Mint kernels (beyond being newer), and b. what known bugs it might have (unfortunately I don't have time for strange new problems). Some posts in this forum made be worry (especially one in the German section).
Point is, I don't want to exchange an (AFAIK) minor annoyance for a heap of new, serious problems... :mrgreen:
User avatar
SMG
Level 25
Level 25
Posts: 31318
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: My RP PIO log size is invalid (???)

Post by SMG »

Kurt3162 wrote: Tue Mar 28, 2023 3:51 am

Code: Select all

Drives:
  Local Storage: total: 3.68 TiB used: 498.84 GiB (13.2%)
  ID-1: /dev/nvme0n1 model: CA6-8D2048-Q11 NVMe SSSTC 2048GB size: 1.86 TiB
    speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter> rev: 24201114
    temp: 19.9 C scheme: GPT
  ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 980 PRO 2TB size: 1.82 TiB
    speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter> rev: 5B2QGXA7
    temp: 24.9 C scheme: GPT
    Partition:
  ID-1: / size: 97.87 GiB used: 27.23 GiB (27.8%) fs: ext4
    dev: /dev/nvme0n1p4
  ID-2: /boot/efi size: 236 MiB used: 100.6 MiB (42.6%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-3: /home size: 97.87 GiB used: 14.1 GiB (14.4%) fs: ext4
    dev: /dev/nvme1n1p4
Swap:
  ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2
    file: /swapfile
Your home partition is on a different drive. Maybe there is a difference in the physical condition of the two drives.
Kurt3162 wrote: Tue Mar 28, 2023 3:51 amSure, what I wanted to know is a. in what way it is different from the official Mint kernels (beyond being newer)
What are you calling an "official Mint kernel"? Linux Mint does not create or maintain their own kernels.

The LTS kernel in Linux Mint is actually the Ubuntu LTS kernel. Same for the HWE (HardWare Enablement) kernel and OEM kernels. They are all Ubuntu kernels.
Kurt3162 wrote: Tue Mar 28, 2023 3:51 am b. what known bugs it might have (unfortunately I don't have time for strange new problems). Some posts in this forum made be worry (especially one in the German section).
I have no clue what you are referencing with respect to "known bugs". Every kernel has known bugs.

As far as something you read on the German forum, you'll have to provide a link because there are a lot of posts on the German forum and I rarely check them.

I gave you a link which describes OEM kernels. OEM = Original Equipment Manufacturer and will have drivers for specific hardware that Dell, Lenovo, or other manufacturers may need. Those manufacturers work with Canonical (Ubuntu) to make sure Ubuntu has the drivers to work on their hardware.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
Kurt3162
Level 4
Level 4
Posts: 480
Joined: Wed Apr 02, 2014 2:05 pm

Re: My RP PIO log size is invalid (???)

Post by Kurt3162 »

SMG wrote: Tue Mar 28, 2023 12:20 pm Your home partition is on a different drive. Maybe there is a difference in the physical condition of the two drives.
Why would there? They are both quite new (<1 year old) SSDs of the same type. :?:
It could, but it isn't very likely.

SMG wrote: Tue Mar 28, 2023 12:20 pm What are you calling an "official Mint kernel"?
The ones Mint's Update Manager serves. It doesn't imply the Mint team make them themselves, but it's clearly the default Mint kernel, isn't it.
Yes, I should had said "default" instead of "official"...

SMG wrote: Tue Mar 28, 2023 12:20 pm Every kernel has known bugs.
Some less than others though, according to the Ubuntu kernel bug tracker. That's why I asked earlier which actual version number "linux-oem-22.04c" was supposed to be, but unfortunately the 6.x kernels don't seem to exist in the bug tracker. :(

SMG wrote: Tue Mar 28, 2023 12:20 pm As far as something you read on the German forum, you'll have to provide a link
Sorry, would had done it, but I didn't keep the URL and I only found it after a long search. It isn't that important anyway.

SMG wrote: Tue Mar 28, 2023 12:20 pm I gave you a link which describes OEM kernels. OEM = Original Equipment Manufacturer and will have drivers for specific hardware that Dell, Lenovo, or other manufacturers may need. Those manufacturers work with Canonical (Ubuntu) to make sure Ubuntu has the drivers to work on their hardware.
Sure, it was useful but it doesn't tell me if this specific kernel does work with my own laptop. Most likely it does, but you must have noticed I'm a little paranoid. I'm a belt, braces and strong glue guy... :mrgreen:
User avatar
SMG
Level 25
Level 25
Posts: 31318
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: My RP PIO log size is invalid (???)

Post by SMG »

Kurt3162 wrote: Tue Mar 28, 2023 12:52 pm Some less than others though, according to the Ubuntu kernel bug tracker. That's why I asked earlier which actual version number "linux-oem-22.04c" was supposed to be, but unfortunately the 6.x kernels don't seem to exist in the bug tracker. :(

Sure, it was useful but it doesn't tell me if this specific kernel does work with my own laptop. Most likely it does, but you must have noticed I'm a little paranoid. I'm a belt, braces and strong glue guy... :mrgreen:
No problem with being safe rather than sorry. I personally wait for feedback from multiple people to make sure a recommendation seems appropriate for certain hardware before recommending it to more people. Had your system not had Nvidia, I would have recommended the 6.0-oem because there was at least one person with an Intel-only system who ran into issues with the 6.1-oem. (They decided to use the kernel on their own; I did not recommend it to them.)

I also think you may be confused by the fact the package only has one name, but the kernel it will install will be different depending upon when you install it because the package name refers to a series.

In LM21 versions, the 5.15 kernel series is the LTS kernel. However, that is not one kernel. There is a new kernel released approximately every 4-6 weeks. The latest version is 5.15.0-69.

Similarly, the linux-oem-22.04c package refers to the 6.1-oem kernel and the latest is 6.1.0-1008.8 or thereabouts. The 6.1-oem changelogs will give you an idea of what has been fixed/changed in each version. If this is the first time you have ever seen a changelog, I will let you know this long list is very normal.

You can also check in Synaptic package manager to see which 6.1-oem versions were made available. Search on the linux-oem-22.04c package name.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
Kurt3162
Level 4
Level 4
Posts: 480
Joined: Wed Apr 02, 2014 2:05 pm

Re: My RP PIO log size is invalid (???)

Post by Kurt3162 »

SMG wrote: Tue Mar 28, 2023 1:37 pm The latest version is 5.15.0-69.
:?: OMG!... "Update Manager" offered me kernel "5.19.0-38" yesterday, which I installed.
Yet on inxi -Fxxxrz that same kernel is indeed named "5.15.0-69-generic". Yet, I checked again right now, "Update Manager" insists on calling it "5.19.0-38"!

The one before was, according to "Update Manager", "5.19.0-35", but in my own inxi -Fxxxrz posted further up it is described as "5.15.0-67-generic".

Don't tell me they don't actively try to confuse people... :(

SMG wrote: Tue Mar 28, 2023 1:37 pm The 6.1-oem changelogs will give you an idea of what has been fixed/changed in each version.
Thanks but changelogs aren't of much use to the average user, unless I'm waiting for some feature to be implemented or some specific bug to be fixed: Knowing what they have tweaked won't tell me if I'm likely to lose half a day or more trying to solve some elusive malfunction...

That been said, under what apocryphal name does the standard, default, Update Manager-supplied, LTS kernel of Mint 21 appear? From what you told me I would had guessed something along the lines of "linux-lts-jammy", or maybe "linux-generic", but there is no such folder. There isn't even a "-focal" or a "-bionic" folder, apparently the latest LTS kernel mentioned is "linux-lts-trusty" (Mint 17!)... :shock:
As there is (obviously) no explanatory readme explaining all those shortcut names, I'm left guessing. (Yes, I understand this is for people who are in the know and/or work there, not for clueless-yet-nosy tourists).

SMG wrote: Tue Mar 28, 2023 1:37 pm You can also check in Synaptic package manager to see which 6.1-oem versions were made available. Search on the linux-oem-22.04c package name.
Thanks, that's interesting.
Although the jury is still out on using the 6.x kernel. I'm waiting to see if the "5.19.0-38" aka "5.15.0-69-generic" I installed yesterday improves/changes anything.
User avatar
SMG
Level 25
Level 25
Posts: 31318
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: My RP PIO log size is invalid (???)

Post by SMG »

Kurt3162 wrote: Wed Mar 29, 2023 4:13 am
SMG wrote: Tue Mar 28, 2023 1:37 pm The latest version is 5.15.0-69.
:?: OMG!... "Update Manager" offered me kernel "5.19.0-38" yesterday, which I installed.
Yet on inxi -Fxxxrz that same kernel is indeed named "5.15.0-69-generic". Yet, I checked again right now, "Update Manager" insists on calling it "5.19.0-38"!

The one before was, according to "Update Manager", "5.19.0-35", but in my own inxi -Fxxxrz posted further up it is described as "5.15.0-67-generic".

Don't tell me they don't actively try to confuse people... :(
What is the output of uname -r?

Linux Mint is supposed to boot to the highest number installed kernel. That means if you have a 5.19 series kernel installed, that is what should show in inxi and in the command I just asked you to run. If it is not, there is a problem with your system and we need to determine what is happening.
Kurt3162 wrote: Wed Mar 29, 2023 4:13 amKnowing what they have tweaked won't tell me if I'm likely to lose half a day or more trying to solve some elusive malfunction...
Why do you think the next update of 5.15 will not cause problems, but the 6.1-oem kernel will? It is just as likely you can get an update in 5.15 that will cost you half a day as it is to lose half a day with 6.1-oem. There is no difference between the two of them that one is more or less likely to cause problems. You are going to have to explain why you think there is a difference because I am not aware of one.

Additionally, if a new kernel causes problems, it only takes a couple of minutes to re-boot your computer into the prior kernel and use it until you have time to troubleshoot what the issue is with the newer kernel.
Kurt3162 wrote: Wed Mar 29, 2023 4:13 amThat been said, under what apocryphal name does the standard, default, Update Manager-supplied, LTS kernel of Mint 21 appear? From what you told me I would had guessed something along the lines of "linux-lts-jammy", or maybe "linux-generic", but there is no such folder. There isn't even a "-focal" or a "-bionic" folder, apparently the latest LTS kernel mentioned is "linux-lts-trusty" (Mint 17!)... :shock:
I'm sorry, but I have no idea what you mean by a folder referring to a kernel.

In my install, the linux-generic package in Synaptic Package Manager is the latest LTS kernel.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
Kurt3162
Level 4
Level 4
Posts: 480
Joined: Wed Apr 02, 2014 2:05 pm

Re: My RP PIO log size is invalid (???)

Post by Kurt3162 »

SMG wrote: Wed Mar 29, 2023 9:27 am What is the output of uname -r?
"5.15.0-69-generic", same as the inxi.

- Waiiit... :idea:

I checked "Update Manager", which defaults to a page "5.19", and on top is "5.19.0-38, Supported until August 2023".
But, there is also an entry "5.15", and on top of that list it says "5.15.0-69, Active, Supported until April 2027"...

So I am indeed using 5.15.0-69, but for some reason I also have four (!) 5.19 kernels I'm apparently not using (never did AFAIK), but which apparently are nevertheless on my computer, and regularly updated.

Okay, mystery solved.
I have no clue how and why I got to have that line of 5.19 kernels, but since I do, and since Alder Lake CPUs are only really understood by (IIRC) kernels 5.16 and higher (because P and E-cores), shouldn't I switch to that mysterious 5.19.0-38? :?:
I've checked the kernel bug list and it looks pretty safe, just four suspend/sleep bugs and a Bluetooth one, and I never use either.

SMG wrote: Wed Mar 29, 2023 9:27 am Why do you think the next update of 5.15 will not cause problems, but the 6.1-oem kernel will?
Because I assume that if it was totally safe it would be the current LTS kernel... :)

Now I admit I know nothing about kernel version politics, and maybe the current flavor of Ubuntu/Mint (jammy/21) is supposed to stay with 5.15 till the end, but the fact is that newer kernels do have some useful improvements (especially for newer hardware like mine), so there is some incentive to update. It's not just the "New! Shiny!" trend.
Of course you might tell me that improvements are backported, but then it becomes very difficult to follow. What about the Alder Lake issue I mentioned? AFAIK it was first implemented in 5.16, has it been backported to 5.15? Since when? :shock:

SMG wrote: Wed Mar 29, 2023 9:27 am I'm sorry, but I have no idea what you mean by a folder referring to a kernel.
Sorry. Check https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D
Where does one find the standard LTS 5.15 kernel changelogs in there?
(I'm hunting for my Alder Lake compatibility. If they backported it, it should appear somewhere in the changelogs)

Thanks for taking the time to help me, BTW! :)
User avatar
SMG
Level 25
Level 25
Posts: 31318
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: My RP PIO log size is invalid (???)

Post by SMG »

Kurt3162 wrote: Wed Mar 29, 2023 11:58 amI checked "Update Manager", which defaults to a page "5.19", and on top is "5.19.0-38, Supported until August 2023".
But, there is also an entry "5.15", and on top of that list it says "5.15.0-69, Active, Supported until April 2027"...
That means there is something wrong with your install. Your system should have booted into the highest installed kernel (ie. a 5.19 kernel).

Do you have more than one Linux-based distro installed? If so, it would seem the other distro is in charge of grub and you will have to run sudo update-grub in the other distro to get the correct kernel to boot in Linux Mint.

If you do not have another Linux-based distro installed, did you install some type of grub customization software?
Kurt3162 wrote: Wed Mar 29, 2023 11:58 am Of course you might tell me that improvements are backported, but then it becomes very difficult to follow. What about the Alder Lake issue I mentioned? AFAIK it was first implemented in 5.16, has it been backported to 5.15? Since when? :shock:
I already told you that your newer hardware should be using a newer kernel for best support. Support is not backported to older kernels.
Kurt3162 wrote: Wed Mar 29, 2023 11:58 amSorry. Check https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D
Where does one find the standard LTS 5.15 kernel changelogs in there?
(I'm hunting for my Alder Lake compatibility. If they backported it, it should appear somewhere in the changelogs)
Why are you looking at a PPA with mainline kernels?
Image
A woman typing on a laptop with LM20.3 Cinnamon.
Kurt3162
Level 4
Level 4
Posts: 480
Joined: Wed Apr 02, 2014 2:05 pm

Re: My RP PIO log size is invalid (???)

Post by Kurt3162 »

SMG wrote: Wed Mar 29, 2023 1:33 pm Do you have more than one Linux-based distro installed?
No, just Mint 21.1 (and a shrunken Win11 partition I use to update my BIOS and other firmware, something which occurs very frequently given the new-ish hardware).

SMG wrote: Wed Mar 29, 2023 1:33 pm If you do not have another Linux-based distro installed, did you install some type of grub customization software?
Neither. You might have noticed I'm rather risk-averse, and I know just enough to put myself in trouble...

SMG wrote: Wed Mar 29, 2023 1:33 pm Support is not backported to older kernels.
I thought so. After all, to even install Mint 21 on this laptop I had to use the "Edge" ISO, the standard one didn't see my SSDs...

SMG wrote: Wed Mar 29, 2023 1:33 pm Why are you looking at a PPA with mainline kernels?
I guess because I don't know better?... :mrgreen:
So where would the changelog for the "5.15" series kernel be? I did an Internet search, but didn't find anything about a 5.15.0-x kernel.
User avatar
SMG
Level 25
Level 25
Posts: 31318
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: My RP PIO log size is invalid (???)

Post by SMG »

Kurt3162 wrote: Thu Mar 30, 2023 8:07 am After all, to even install Mint 21 on this laptop I had to use the "Edge" ISO, the standard one didn't see my SSDs...
There is no Edge ISO for LM21. None have been released. What did you install?
(Maybe that is why the proper kernel is not booting? :? )
Kurt3162 wrote: Thu Mar 30, 2023 8:07 am So where would the changelog for the "5.15" series kernel be? I did an Internet search, but didn't find anything about a 5.15.0-x kernel.
Check this list. It has more than just 5.15 so you will have to check for a specific version.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
Locked

Return to “Installation & Boot”