Bug 25570 - System will reboot during Linux probing the PCI bus on HP's LH4 with NetRAID-2M controller
System will reboot during Linux probing the PCI bus on HP's LH4 with NetRAID-...
Status: CLOSED WORKSFORME
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
7.0
i386 Linux
high Severity high
: ---
: ---
Assigned To: Michael K. Johnson
Brock Organ
www.ami.com
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-02-01 18:54 EST by Venkatesh Ramamurthy
Modified: 2005-10-31 17:00 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-06-05 19:29:28 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)

  None (edit)
Description Venkatesh Ramamurthy 2001-02-01 18:54:44 EST
Installing Linux Redhat7.0/6.2 to HP's LH4(Intel NX chipset) when NetRAID-
2M(AMI MegaRAID Controller) is in the primary bus(64bit).

System will reboot during Linux probing the PCI bus.

HP's NetRAID-2M contains a qlogic chip which is visible to the host bus.

According to the PCI trace:
***************************
Linux initiates I/O read one byte wide to the Qlogic SCSI Chip in the
NetRaid-2M.
Qlogic is not accesible to this type of cycle (I/O read one byte wide).
Linux retry the cycles three times, the last Qlogic initiate target
abort(stop asserted, devsel and trdy deasserted). This is valid!.

However, 180ns later Linux(not certain) resets the system.
My question: Does Linux susceptible to the target abort?

FYI, NetRAID-2M is 64bit adapter which is preferable to go to the 64bit PCI
slots.
Comment 1 Arjan van de Ven 2001-02-02 04:11:55 EST
Does this also happen with the install-floppies (or cd) from the recently
released beta?
Comment 2 Venkatesh Ramamurthy 2001-02-02 13:12:48 EST
The issue could not be reproduced in LH4 systems in AMI Labs. HP Labs have 
confirmed that it was behaving like my above mentioned report. I will pursue 
with HP with using floppy's for installation.
Comment 3 Michael K. Johnson 2001-02-08 16:14:06 EST
peterj@ami.com is actually the person responsible for this driver.
Peter, have you been involved in tracking this down?

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