Searched refs:fail (Results 601 – 613 of 613) sorted by relevance
1...<<2122232425
14042 goto fail; in hat_join_region()14074 fail: in hat_join_region()
1135 may fail in saving a default entry in this file, if you change this3207 partition table fail. This is a bad sign.
2983 % it will fail (although perhaps we could fix that with sufficient work6367 % undone and the next image would fail.
5978 goto fail; in ip_modopen()5986 fail: in ip_modopen()
736 alias likely does not exist, replies will fail. Use this3111 cases, gethostbyname may fail to return the FQDN. In this case
9947 static char *fail = "SCSI transport failed: reason '%s': %s\n"; in st_handle_incomplete() local10104 fail, scsi_rname(pkt->pkt_reason), in st_handle_incomplete()
172 * no service impact - otherwise fail immediately
1595 96-08-31 regex: fix BM fail table generator
14450 … (!m->SPSSocket) { LogMsg("mDNSCoreBeSleepProxyServer: Failed to allocate SPSSocket"); goto fail; } in mDNSCoreBeSleepProxyServer_internal()14461 fail: in mDNSCoreBeSleepProxyServer_internal()
8405 fail
8403 fail
1891 # else the application may fail. It is also expected that applications will2079 # fail to interpret the ^O and ^N escapes properly. Symptom: the :me:19240 # * Corrected hpa/vpa in linux entry. They still fail the worm test.
2145 # else the application may fail. It is also expected that applications will2343 # fail to interpret the ^O and ^N escapes properly. Symptom: the <sgr0>21458 # * Corrected hpa/vpa in linux entry. They still fail the worm test.