Bug 4020 – PCI peer discovery cycle finds 255 peers! (TI TravelMate 5100 laptop)

Bug 4020 - PCI peer discovery cycle finds 255 peers! (TI TravelMate 5100 laptop)

Summary:	PCI peer discovery cycle finds 255 peers! (TI TravelMate 5100 laptop)

Status:	CLOSED NOTABUG

Aliases:	None

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

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	David Lawrence
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-07-13 16:30 EDT by Jason M. Sullivan
Modified:	2008-05-01 11:37 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	1999-08-19 15:48:01 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Jason M. Sullivan 1999-07-13 16:30:09 EDT

When the Redhat 6.0 Linux kernal boots up on my TravelMate,
it goes though some sort of PCI peer probing thing with
messages of the form (typed from memory)

PCI: found peer at 0x00
PCI: found peer at 0x01

...and this continues up until...

PCI: found peer at 0xff

...needless to say, this takes a while. A good 15min on a
P120 with 24Mb of RAM.  I'm guessing this isn't supposed to
happen (I don't have 255 of anything PCI related in this
laptop).  Is there some sort of boot param. that I can enter
to limit this probing annoyance?

Comment 1 Bill Nottingham 1999-07-13 17:00:59 EDT

Try booting with the 'nopeer' option.

Comment 2 Anonymous 1999-07-14 21:35:59 EDT

That did it.  Thanks!

I read in the BootPrompt documetation (duh, shoulda gone there first)
about the argument, but I don't quite understand the nature of why
the PCI bus freaks out without it.  Oh well.  Thanks again!

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