Bug 84066 – [Milan beta 5] \"Unknown bridge resource\" repeated in dmesg

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 84066 - [Milan beta 5] \"Unknown bridge resource\" repeated in dmesg

Summary:	[Milan beta 5] \"Unknown bridge resource\" repeated in dmesg

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	kernel (Show other bugs)
Sub Component:
Version:	9
Hardware:	All Linux

Priority	medium Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Arjan van de Ven
QA Contact:	Brian Brock
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2003-02-11 15:11 EST by Larry Troan
Modified:	2016-04-18 05:39 EDT (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2003-12-16 19:24:31 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
dmesg.smp.txt (14.90 KB, text/plain) 2003-02-11 15:12 EST, Larry Troan	no flags	Details
dmesg.txt (8.25 KB, text/plain) 2003-02-11 15:12 EST, Larry Troan	no flags	Details
lspci-n.txt (1.07 KB, text/plain) 2003-02-18 08:42 EST, Larry Troan	no flags	Details
lspci.txt (2.00 KB, text/plain) 2003-02-18 08:43 EST, Larry Troan	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Larry Troan 2003-02-11 15:11:20 EST

[Milan beta 5]  On a discovery w/ A00 bios, 512MB ram, Perc 4/SC attached to
internal backplane, and 2.4.18-12.4smp/up.

Dmesg reports:

"PCI: Probing PCI hardware
Unknown bridge resource 2: assuming transparent
Unknown bridge resource 0: assuming transparent
Unknown bridge resource 1: assuming transparent
Unknown bridge resource 2: assuming transparent
Unknown bridge resource 2: assuming transparent
Unknown bridge resource 0: assuming transparent
Unknown bridge resource 2: assuming transparent
Unknown bridge resource 0: assuming transparent
Unknown bridge resource 1: assuming transparent
Unknown bridge resource 2: assuming transparent
Unknown bridge resource 0: assuming transparent
Unknown bridge resource 1: assuming transparent
Unknown bridge resource 2: assuming transparent
Unknown bridge resource 0: assuming transparent
Unknown bridge resource 0: assuming transparent
Unknown bridge resource 0: assuming transparent
Unknown bridge resource 1: assuming transparent
Unknown bridge resource 2: assuming transparent
Unknown bridge resource 0: assuming transparent
Unknown bridge resource 2: assuming transparent"

Occurs in both UP and SMP kernels.

----------
Action by: ccooper
Issue Registered
----------
Action by: ccooper
Dmesg of smp kernel

Status set to: Info
Attachment: <a href="?module=download&fid=870">dmesg.smp.txt</a>

----------
Action by: ccooper
Dmesg of UP kernel

Attachment: <a href="?module=download&fid=871">dmesg.txt</a>

----------
Action by: arjanv
no big deal, unknown bridges are not a problem.
lspci + lscpi -n might get it supported for an erratum if we can test


----------
Action by: ltroan


Category set to: Applications
Status set to: Waiting on Tech


Pushing to Bugzilla for errata consideration.
ISSUE TRACKER 6479, opened as sev 3.

Comment 1 Larry Troan 2003-02-11 15:12:02 EST

Created attachment 90008 [details]
dmesg.smp.txt

Comment 2 Larry Troan 2003-02-11 15:12:43 EST

Created attachment 90009 [details]
dmesg.txt

Comment 3 Larry Troan 2003-02-11 15:14:39 EST

Can you provide lspci and lspci -n so we can attampt to fix in errata?

Comment 4 Larry Troan 2003-02-18 08:42:33 EST

Created attachment 90153 [details]
lspci-n.txt

Comment 5 Larry Troan 2003-02-18 08:43:13 EST

Created attachment 90154 [details]
lspci.txt

Comment 6 Arjan van de Ven 2003-02-18 09:15:22 EST

this message shouldn't happen anymore in gingin beta5

Comment 7 Larry Troan 2003-02-18 15:57:28 EST

ALSO ISSUE TRACKER 15613 (AS2.1)

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