Bug 51457 - Kudzu defaults 21554 based cards to cpqarray driver
Kudzu defaults 21554 based cards to cpqarray driver
Product: Red Hat Linux
Classification: Retired
Component: kudzu (Show other bugs)
i686 Linux
medium Severity high
: ---
: ---
Assigned To: Bill Nottingham
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2001-08-10 12:45 EDT by bugzilla
Modified: 2014-03-16 22:22 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-08-10 12:45:16 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description bugzilla 2001-08-10 12:45:12 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.0; Windows NT; DigExt)

Description of problem:
The Kudzu database is setup to default any DEC 21554 based cards
to the cpqarray driver if it doesn't have a match for the subvendor
and subdevice id. We (Intel) are working on a new card with this chip
that kudzu tries to enable the cpqarray driver. There is a problem in
the cpqarray driver (which also only matches vendor and device Ids)
that tries and accesses our card and causes interrupts to be shot off
and not handled. This caused Redhat 7.1 to hang on the install, as
well as anytime this driver is loaded while one of our boards is in
the system the kernel will hang (endless loop of interrupts) on boot.

The bug is really in the driver. I am contacting Compaq about this.
But, kudzu should not default all 21554 devices to this driver.

How reproducible:

Steps to Reproduce:
1.Install Redhat 7.1 with our board in the system.
(or any board that is not in the kudzu DB with a 21554 bridge chip)
2.Allow kudzu to configure our board when it is detected.
3.Load the cpqarray driver with our board in the system.

Additional info:
Comment 1 Bill Nottingham 2001-08-10 12:47:05 EDT
This was fixed post-7.1; it's changed in the roswell beta.

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