Lines Matching refs:BUS

52              10.2.19 Check SCSI BUS 
59       10.6 SCSI BUS checking boot option
544     The driver will try to send a BUS DEVICE RESET message to the target.
825 10.2.19 Check SCSI BUS 
857                 when it arbitrated for the SCSI BUS.
883   SCSI BUS check		donnot attach on error	buschk:1
999 10.6 SCSI BUS checking boot option.
1004 Since SCSI devices shall release the BUS at most 800 nano-seconds after SCSI 
1005 RESET has been asserted, any signal to TRUE may indicate a SCSI BUS problem.
1006 Unfortunately, the following common SCSI BUS problems are not detected:
1017 SYMBIOS 53C8XX chips are able to arbitrate for the SCSI BUS as soon as they 
1018 have detected an expected disconnection (BUS FREE PHASE). For this process 
1020 connected to the SCSI BUS.
1024 competing for the SCSI BUS. By the way, when the chip is using SCSI id 7, 
1025 then it will for sure win the next SCSI BUS arbitration.
1028 BUS, using this feature can be extremally unfair. So, you are not advised 
1041 SCSI BUS bandwidth if the SCRIPTS execution lasts more than 4 micro-seconds.
1199 you must ensure that lines of the wide part of the SCSI BUS are pulled-up.
1334              Data parity error detected on the PCI BUS.
1343   BF (0x20), then the cause may be likely due to a PCI BUS problem.
1348              on the SCSI BUS that prevents the SCSI protocol from functionning
1351              Indicates that the device released the SCSI BUS when the chip 
1354   Bit 0x02 : RST  SCSI BUS Reset
1355              Generally SCSI targets donnot reset the SCSI BUS, although any 
1356              device on the BUS can reset it at any time.
1359   On a faulty SCSI BUS, any error condition among SGE (0x08), UDC (0x04) and 
1362   BUS problem is likely the cause of these errors.
1370           Actual value of control lines on the SCSI BUS.
1372           Actual value of data lines on the SCSI BUS.