Searched refs:failed (Results 376 – 383 of 383) sorted by relevance
1...<<111213141516
3140 attempt to determine the size and geometry of the hard disk failed.3145 failed. It's listed as a separate error since the probe sequence
1452 * We have to use target-ma to informs us which device failed to respond.
18994 goto failed;19040 failed:
3061 \f5ksh\fP can handle a failed exec much faster than starting up
9374 failed with an exception. This also fixes a couple of related RefOf and 11334 returned, even if the operation failed.12707 of the opcode failed. The solution to this problem was to13454 failed to cleanup properly by deleting all successfully resolved16235 Fixed a problem where Operation Region initialization failed if
2373 # the researchers who prepared the Decrees page failed to find some of
1329 # (the former is untrue, and the latter failed under UCB/man); standout and9868 # Pn= 0 Call failed19004 # making perfectly synchronized mistakes which I then failed to catch by
1470 # (the former is untrue, and the latter failed under UCB/man); standout and11192 # Pn= 0 Call failed21222 # making perfectly synchronized mistakes which I then failed to catch by