Lines Matching full:oops
138 * If your failure involves a 'panic', 'Oops', 'warning', or 'BUG', consider
150 like the output/screenshot of an Oops or the output from ``lspci``. Once
406 fatal error where the kernel stop itself) with a 'Oops' (a recoverable error),
498 problem (a 'kernel bug'), a recoverable error (a 'kernel Oops') or a
509 1. A recoverable error (a 'kernel Oops') occurred and the kernel tainted
514 Oops: 0000 [#1] SMP
516 That's the first Oops since boot-up, as the '#1' between the brackets shows.
517 Every Oops and any other problem that happens after that point might be a
518 follow-up problem to that first Oops, even if both look totally unrelated.
519 Rule this out by getting rid of the cause for the first Oops and reproducing
521 a change to the configuration followed by a reboot can eliminate the Oops.
523 the cause for the Oops might already be fixed in the newer Linux kernel
872 are needed to decode messages the kernel prints when a panic, Oops, warning, or
896 Note: If you are dealing with a panic, Oops, warning, or BUG from the kernel,
963 *If your failure involves a 'panic', 'Oops', 'warning', or 'BUG', consider
972 'panic', 'Oops', 'warning', or 'BUG', which increases the chances that someone
1077 like the output/screenshot of an Oops or the output from ``lspci``. Once
1160 * If you are dealing with a 'warning', an 'OOPS' or a 'panic' from the kernel,