Searched full:panics (Results 1 – 25 of 98) sorted by relevance
1234
174 function panics if180 function panics if186 function panics if
78 In the unlikely event of concurrent panics, only one panicking thread will proceed.
86 If not, the runtime prints a warning or panics the kernel, depending on the
220 Handler functions are expected to take care not to trigger recursive panics.
218 and panics if they are not met.
54 rumptest_threadjoin(); /* panics if fails */ in ATF_TC_BODY()71 rumptest_threadjoin(); /* panics if fails */ in ATF_TC_BODY()
54 rumptest_tsleep(); /* panics if fails */ in ATF_TC_BODY()
4 ramoops provides persistent RAM storage for oops and panics, so they can be55 (defaults to 2: log Oopses and Panics). This can be set to INT_MAX to
10 ramoops provides persistent RAM storage for oops and panics, so they can be78 default: 2 # log oopses and panics
64 * Panics if the key already exists.74 * Panics if the key already exists.310 * Panics if there is not an old page in the trie at the new page's index.
15 * Bytes 0x0 Write panic event to the reg when guest OS panics.
27 # panics. I think it's because the kernel's list of interfaces isn't properly
23 # Verify that error conditions don't cause panics in zfs send
47 mv $nullfs_srcdir/1/test.file $nullfs_srcdir/2/ # panics with lock violation
32 # kern/162362: ufs with snapshot(s) panics when getting full
58 touch $mntpoint/xxxxxxxx # Panics here
53 sed -i -e "/md$mdstart/d" /etc/fstab # clean up before any panics
32 # Various panics seen with WiP kernel code. For example:
30 # turned up quite a few new panics. For example:
29 # No problems seen with SU. Panics with SU+J, just like suj30.sh
28 * Bug in IP code panics the system at close(2) on
67 # was what triggered past panics.
316 # stop panics related to heavy use of shared memory. However, that can317 # (combined with large amounts of physical memory) cause panics at
201 file-system\-related panics.
260 unpredictable results including kernel panics.