Searched refs:unexpected (Results 1 – 25 of 69) sorted by relevance
123
86 echo $FUNCNAME $memory: unexpected fail >&289 echo $FUNCNAME $memory: unexpected offline >&2100 echo $FUNCNAME $memory: unexpected success >&2103 echo $FUNCNAME $memory: unexpected online >&2114 echo $FUNCNAME $memory: unexpected fail >&2117 echo $FUNCNAME $memory: unexpected offline >&2128 echo $FUNCNAME $memory: unexpected success >&2131 echo $FUNCNAME $memory: unexpected offline >&2
104 echo $FUNCNAME $cpu: unexpected fail >&2107 echo $FUNCNAME $cpu: unexpected offline >&2117 echo $FUNCNAME $cpu: unexpected success >&2120 echo $FUNCNAME $cpu: unexpected online >&2130 echo $FUNCNAME $cpu: unexpected fail >&2133 echo $FUNCNAME $cpu: unexpected offline >&2143 echo $FUNCNAME $cpu: unexpected success >&2146 echo $FUNCNAME $cpu: unexpected offline >&2
24 this is an expected message, otherwise it is called an unexpected message.45 unexpected message list. The application posts receive buffers through calls52 placed in the unexpected message list. Otherwise the match is processed,58 the software unexpected message list for a matching receive. If a match is68 hardware, as the matching unexpected message is being passed from the hardware
26 feature will have unexpected results.60 that doesn't support this feature will have unexpected results.85 that doesn't support this feature will have unexpected results.124 that doesn't support this feature will have unexpected results.
62 unexpected times and/or unexpected addresses, possibly leading to data65 unexpected times. However, to protect against general data leakage and
25 unexpected transaction.
68 be unexpected results in the application.
166 Print a warning message when an unexpected interrupt is received.170 Don't print a message when an unexpected interrupt is received. This172 to be an interaction between video and floppy. The unexpected
1515 unexecpted||unexpected1516 unexepected||unexpected1517 unexpcted||unexpected1518 unexpectd||unexpected1519 unexpeted||unexpected1520 unexpexted||unexpected
44 ERROR: Description of unexpected error
92 applications should abort on unexpected errors, or otherwise
90 5 _/B 32 bad page referenced or some unexpected page flags144 unexpected page flags. This indicates a hardware problem or a kernel bug;
41 ABI is completely unexpected to Linux. Syscall User Dispatch, therefore
148 cause unexpected behaviour and can be a security hazard.
159 * unexpected default value (it should divide by 1
22 pages are being allocated and freed, as unexpected state changes
237 unexpected behaviour from DMA API implementations if the scatterlist
54 the unexpected high value is coming from. The *irq* context can be
122 might otherwise unexpected use libraries from /lib or /lib64
86 instructions appearing in unexpected places if no special care is taken.
294 This means that an unexpected call to a non-whitelisted function exists306 It also helps verify that there are no unexpected calls to funcB() which may
182 Note: The kernel reports -EINVAL for any unexpected data. The caller245 Note: The kernel reports -EINVAL for any unexpected data. The caller
253 it may be necessary to rebuild the .so. Also there may be unexpected results
223 libbpf: ELF relo #0 in section #6 has unexpected type 2 in .../bpf_tcp_nogpl.o
422 include unexpected packet truncation.432 could include unexpected header truncation
