Bug 30355 - Unable to read modalias message displayed when installing/removing a kernel
Summary: Unable to read modalias message displayed when installing/removing a kernel
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal minor
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-04-30 10:41 CEST by GG HH
Modified: 2023-07-09 13:55 CEST (History)
4 users (show)

See Also:
Source RPM: ldetect-0.12.8-6.mga9.src.rpm
CVE:
Status comment:


Attachments

Description GG HH 2022-04-30 10:41:23 CEST
I encountered the following message when installing or removing a new kernel :
Unable to read modalias from /sys/bus/pci/devices/0000:e1:00.0/modalias
Unable to read modalias from /sys/bus/pci/devices/0000:e0:06.0/modalias
remove-boot-splash: Format of /boot/initrd-5.17.5-desktop-2.mga9.img not recognized

I do not have identified any bad side effect about it.

I filled the bug against the kernel package but it might as well be related to grub
$ rpm -q  grub2-common 
grub2-common-2.06-16.mga9

My PC is a recent one, upgraded to cauldron just after the installation.
The behaviour is probably the same from the beginning (at least 5.16.11-desktop-1.mga9)

Some investigations i made:
$ grep . /sys/bus/pci/devices/*/modalias
...
/sys/bus/pci/devices/0000:01:00.1/modalias:pci:v000010DEd00002291sv00001043sd0000144Cbc04sc03i00
/sys/bus/pci/devices/0000:02:00.0/modalias:pci:v000014C3d00007961sv00001A3Bsd00004680bc02sc80i00
/sys/bus/pci/devices/0000:03:00.0/modalias:pci:v000010ECd00008162sv00001043sd0000208Fbc02sc00i00
/sys/bus/pci/devices/10000:e0:06.0/modalias:pci:v00008086d00009A0Fsv00000000sd00000000bc06sc04i00
/sys/bus/pci/devices/10000:e1:00.0/modalias:pci:v00008086d0000F1AAsv00008086sd0000390Fbc01sc08i02

The directory of two last lines looks like the message but start with 10000 and not 0000.

$ ll /sys/bus/pci/devices/10000:{e0:06,e1:00}.0
lrwxrwxrwx 1 root root 0 févr. 26 22:33 /sys/bus/pci/devices/10000:e0:06.0 -> ../../../devices/pci0000:00/0000:00:0e.0/pci10000:e0/10000:e0:06.0/
lrwxrwxrwx 1 root root 0 févr. 26 22:33 /sys/bus/pci/devices/10000:e1:00.0 -> ../../../devices/pci0000:00/0000:00:0e.0/pci10000:e0/10000:e0:06.0/10000:e1:00.0/

$ grep -E ^DRIVER /sys/bus/pci/devices/10000:{e0:06,e1:00}.0/uevent
/sys/bus/pci/devices/10000:e0:06.0/uevent:DRIVER=pcieport
/sys/bus/pci/devices/10000:e1:00.0/uevent:DRIVER=nvme

# LANG=C lshw

uranus                      
    description: Notebook
    product: ASUS TUF Gaming F17 FX706HCB_TUF766HCB
    vendor: ASUSTeK COMPUTER INC.
    version: 1.0
    width: 4294967295 bits
    capabilities: smbios-3.3 dmi-3.3 smp vsyscall32
    configuration: boot=normal chassis=notebook family=ASUS TUF Gaming F17 uuid=1F84672F-1E63-4B48-85FC-339548AD0E3A
  *-core
       description: Motherboard
       product: FX706HCB
       vendor: ASUSTeK COMPUTER INC.
       physical id: 0
       version: 1.0
       serial: N101NRCX000WZ3MB
       slot: Default string
     *-firmware
          description: BIOS
          vendor: American Megatrends International, LLC.
          physical id: 0
          version: FX706HCB.310
          date: 11/25/2021
          size: 64KiB
          capacity: 15MiB
          capabilities: pci upgrade shadowing cdboot bootselect socketedrom edd int13floppynec int13floppytoshiba int13floppy360 int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keybo
ard int14serial int17printer int10video acpi usb biosbootspecification uefi
          
       *-storage
             description: RAID bus controller
             product: Volume Management Device NVMe RAID Controller
             vendor: Intel Corporation
             physical id: e
             bus info: pci@0000:00:0e.0
             version: 00
             width: 64 bits
             clock: 33MHz
             capabilities: storage msix pciexpress pm bus_master cap_list
             configuration: driver=vmd latency=0
             resources: iomemory:610-60f iomemory:610-60f irq:0 memory:6104000000-6105ffffff memory:76000000-77ffffff memory:6107100000-61071fffff

     *-pci:1
          description: PCI bridge
          product: 11th Gen Core Processor PCIe Controller #0
          vendor: Intel Corporation
          physical id: 6
          version: 05
          width: 32 bits
          clock: 33MHz
          capabilities: pci pciexpress msi pm normal_decode bus_master cap_list
          configuration: driver=pcieport
          resources: irq:146 memory:76000000-761fffff
        *-storage
             description: Non-Volatile memory controller
             product: Intel Corporation
             vendor: Intel Corporation
             physical id: 0
             version: 03:
             width: 64 bits
             clock: 33MHz
             capabilities: storage pm msi pciexpress msix nvm_express bus_master cap_list
             configuration: driver=nvme latency=0
             resources: irq:-2147483648 memory:76000000-76003fff memory:76004000-76023fff


Even if it does seem to have any bad consequences on my system, i tought that it would make sense to let you know about it.


I also have a lot of unknown key messages in my logs. Mostly e5. In neerly a month :
# head -1 /var/log/messages
Apr  1 09:12:51 uranus anacron[380684]: Job `cron.daily' terminated
# grep -c "Unknown key e5" /var/log/messages
15809
# grep  "Unknown key" /var/log/messages|sed "s/.*asus_wmi: //g"|sort|uniq -c
     22 Unknown key 9e pressed
    107 Unknown key b2 pressed
     64 Unknown key b3 pressed
  15822 Unknown key e5 pressed


Regards
Dick Gevers 2022-04-30 11:27:46 CEST

CC: (none) => dvgevers

GG HH 2022-04-30 11:49:47 CEST

CC: (none) => boulshet

Comment 1 Lewis Smith 2022-04-30 20:41:17 CEST
Thank you for the report.

This is grossly similar to bug 30353:-
"keep getting message: Format of /boot/initrd-x.y.z-desktop-n.mga8.img not recognized when installing new kernel"
although most of the details are different. What is similar is:
- relates to installation/removal of kernel
- and "Format of /boot/initrd-x.y.z-desktop-n.mga?.img not recognized"
- is repetitive
- does not seem harmful

It is a good idea that it relates to Grub2; need to check that other bug.
It is likely that this will become a duplicate of the earlier one.

CC: (none) => lewyssmith

Comment 2 GG HH 2022-04-30 21:05:50 CEST
thanks for answering.

You are probably right and that would mean that the "Unable to read modalias from /sys/bus/pci/devices/" part of the text could be not related to the initrd one.
Comment 3 Lewis Smith 2022-05-01 21:57:38 CEST
The roughly similar bug 30353 is now identified as a duplicate of bug 19049, which is ongoing.
https://bugs.mageia.org/show_bug.cgi?id=30353#c3 confirms it is the bootsplash script (as the message says), and that it is harmless:
"remove-boot-splash: Format of /boot/initrd-5.17.5-desktop-2.mga9.img not recognized"
-----------
But:
> Unable to read modalias from /sys/bus/pci/devices/0000:e1:00.0/modalias
> Unable to read modalias from /sys/bus/pci/devices/0000:e0:06.0/modalias
CC'ing tmb to know whether this matters, or is related.

CC: (none) => tmb

Comment 4 GG HH 2022-05-24 22:18:47 CEST
Well, i probably found where the msg come from
# lspcidrake  > /dev/null 
Unable to read modalias from /sys/bus/pci/devices/0000:e1:00.0/modalias
Unable to read modalias from /sys/bus/pci/devices/0000:e0:06.0/modalias
GG HH 2022-05-24 22:31:49 CEST

Source RPM: kernel-5.17.3-2.mga9.src.rpm => ldetect-0.12.8-6.mga9.src.rpm

Comment 5 Lewis Smith 2023-06-01 21:39:08 CEST
Sorry to have left this.
Is it still happening?
Comment 6 GG HH 2023-06-01 21:54:28 CEST
yes it does

# lspcidrake  > /dev/null 
Unable to read modalias from /sys/bus/pci/devices/0000:e1:00.0/modalias
Unable to read modalias from /sys/bus/pci/devices/0000:e0:06.0/modalias

# rpm -q -f /usr/bin/lspcidrake 
ldetect-0.12.8-6.mga9
Comment 7 Lewis Smith 2023-06-02 19:45:21 CEST
Thanks for the confirmation.
Except I do not see these msgs when executing the same command:
$ sudo lspcidrake  > /dev/null
[sudo] password for lewis: 
$

$ su
Password: 
# lspcidrake  > /dev/null
#

Same version of ldetect. OTOH I do not have Grub.
So what do we do? Do these messages show in the journal? When you raised the bug, it was definitely tied to installing/removing a kernel; then comment 4 changed its orientation. If it does show in the journal (or terminal), I can try at the next kernel update.
Comment 8 GG HH 2023-06-02 22:20:40 CEST
lscpidrake is a tool used by the tools helping to configure a new kernel for being booted.
It provides information about the available hardware. I assume that those information are used for setting the initrd image.
The reason why you do not have the same errors as i do is probably related to the fact that your hardware is not the same as mine.
That is the reason why i provided in my first message.

That being said i do not know how to go on on this issue.
If you need additional information to make progress on this issue i may provide it but i have not clue of what might be usefull for that.

Thanks
Comment 9 Lewis Smith 2023-06-03 21:28:48 CEST
Ping tmb.
This really does need a comment from Thomas.
Comment 10 GG HH 2023-07-09 11:48:01 CEST
any advice ?
Comment 11 Thomas Backlund 2023-07-09 11:52:10 CEST
ignore the message, 
its basically cosmetic when drakx notifies that it does not find the data it assumes would be there...
Comment 12 GG HH 2023-07-09 13:55:14 CEST
thanks

Resolution: (none) => WONTFIX
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.