mirror of
https://git.yoctoproject.org/poky
synced 2026-09-24 22:36:21 +02:00
7b46ef1a27
The format of the pci BAR warnings we get on qemu boots has
changed in 6.10+ via the following kernel commit:
commit dc4e6f21c3f844ebc1c52b6920b8ec5dfc73f4e8
Author: Puranjay Mohan <puranjay@kernel.org>
Date: Sat Nov 6 16:56:06 2021 +0530
PCI: Use resource names in PCI log messages
Use the pci_resource_name() to get the name of the resource and use it
while printing log messages.
[bhelgaas: rename to match struct resource * names, also use names in other BAR messages]
Link: https://lore.kernel.org/r/20211106112606.192563-3-puranjay12@gmail.com
Signed-off-by: Puranjay Mohan <puranjay12@gmail.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
Since it doesn't appear that we can do regex's in parselogs
and the bar number is now in the middle of the message, we
go with a slightly wider format of the message to ignore.
(From OE-Core rev: 004fc06a7792592f3847d92fc464347a279f998c)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(cherry picked from commit 0a7126604b6536868600d43aff000a426384995c)
[YC: In scarthgap, the breaking backported commit is in >=6.6.130:
fffdb0fece19 ("PCI: Use resource names in PCI log messages")]
Signed-off-by: Yoann Congal <yoann.congal@smile.fr>
Signed-off-by: Paul Barker <paul@pbarker.dev>
36 lines
1.7 KiB
Plaintext
36 lines
1.7 KiB
Plaintext
# psplash
|
|
FBIOPUT_VSCREENINFO failed, double buffering disabled
|
|
|
|
# PCI host bridge to bus 0000:00
|
|
# pci_bus 0000:00: root bus resource [mem 0x10000000-0x17ffffff]
|
|
# pci_bus 0000:00: root bus resource [io 0x1000-0x1fffff]
|
|
# pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]
|
|
# pci 0000:00:00.0: [2046:ab11] type 00 class 0x100000
|
|
# pci 0000:00:00.0: [Firmware Bug]: reg 0x10: invalid BAR (can't size)
|
|
# pci 0000:00:00.0: [Firmware Bug]: reg 0x14: invalid BAR (can't size)
|
|
# pci 0000:00:00.0: [Firmware Bug]: reg 0x18: invalid BAR (can't size)
|
|
# pci 0000:00:00.0: [Firmware Bug]: reg 0x1c: invalid BAR (can't size)
|
|
# pci 0000:00:00.0: [Firmware Bug]: reg 0x20: invalid BAR (can't size)
|
|
# pci 0000:00:00.0: [Firmware Bug]: reg 0x24: invalid BAR (can't size)
|
|
invalid BAR (can't size)
|
|
# 6.10+ the invalid BAR warnings are of this format:
|
|
# pci 0000:00:00.0: [Firmware Bug]: BAR 0: invalid; can't size
|
|
# pci 0000:00:00.0: [Firmware Bug]: BAR 1: invalid; can't size
|
|
# pci 0000:00:00.0: [Firmware Bug]: BAR 2: invalid; can't size
|
|
# pci 0000:00:00.0: [Firmware Bug]: BAR 3: invalid; can't size
|
|
# pci 0000:00:00.0: [Firmware Bug]: BAR 4: invalid; can't size
|
|
# pci 0000:00:00.0: [Firmware Bug]: BAR 5: invalid; can't size
|
|
invalid; can't size
|
|
|
|
# These should be reviewed to see if they are still needed
|
|
wrong ELF class
|
|
fail to add MMCONFIG information, can't access extended PCI configuration space under this bridge
|
|
can't claim BAR
|
|
amd_nb: Cannot enumerate AMD northbridges
|
|
tsc: HPET/PMTIMER calibration failed
|
|
modeset(0): Failed to initialize the DRI2 extension
|
|
glamor initialization failed
|
|
blk_update_request: I/O error, dev fd0, sector 0 op 0x0:(READ)
|
|
floppy: error
|
|
failed to IDENTIFY (I/O error, err_mask=0x4)
|