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.
819 10.2.19 Check SCSI BUS 
851                 when it arbitrated for the SCSI BUS.
877   SCSI BUS check		do not attach on error	buschk:1
993 10.6 SCSI BUS checking boot option.
998 Since SCSI devices shall release the BUS at most 800 nano-seconds after SCSI 
999 RESET has been asserted, any signal to TRUE may indicate a SCSI BUS problem.
1000 Unfortunately, the following common SCSI BUS problems are not detected:
1011 SYMBIOS 53C8XX chips are able to arbitrate for the SCSI BUS as soon as they 
1012 have detected an expected disconnection (BUS FREE PHASE). For this process 
1014 connected to the SCSI BUS.
1018 competing for the SCSI BUS. By the way, when the chip is using SCSI id 7, 
1019 then it will for sure win the next SCSI BUS arbitration.
1022 BUS, using this feature can be extremely unfair. So, you are not advised
1035 SCSI BUS bandwidth if the SCRIPTS execution lasts more than 4 micro-seconds.
1193 you must ensure that lines of the wide part of the SCSI BUS are pulled-up.
1304              Data parity error detected on the PCI BUS.
1313   BF (0x20), then the cause may be likely due to a PCI BUS problem.
1318              on the SCSI BUS that prevents the SCSI protocol from functioning
1321              Indicates that the device released the SCSI BUS when the chip 
1324   Bit 0x02 : RST  SCSI BUS Reset
1325              Generally SCSI targets do not reset the SCSI BUS, although any 
1326              device on the BUS can reset it at any time.
1329   On a faulty SCSI BUS, any error condition among SGE (0x08), UDC (0x04) and 
1332   BUS problem is likely the cause of these errors.
1340           Actual value of control lines on the SCSI BUS.
1342           Actual value of data lines on the SCSI BUS.