torture: Stop hanging on panic
By default, the "panic" kernel parameter is zero, which causes the kernel to loop indefinitely after a panic(). The rcutorture scripting will eventually kill the corresponding qemu process, but only after waiting for the full run duration plus a few minutes. This works, but delays notifying the developer of the failure. This commit therefore causes the rcutorture scripting to pass the "panic=-1" kernel parameter, which caused the kernel to instead unceremoniously shut down immediately. This in turn causes qemu to terminate, so that if all of the runs in a given batch panic(), the rcutorture scripting can immediately proceed to the next batch. Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
This commit is contained in:
parent
0beb394878
commit
f716348f29
|
@ -203,6 +203,7 @@ identify_qemu () {
|
||||||
# and the TORTURE_QEMU_INTERACTIVE environment variable.
|
# and the TORTURE_QEMU_INTERACTIVE environment variable.
|
||||||
identify_qemu_append () {
|
identify_qemu_append () {
|
||||||
echo debug_boot_weak_hash
|
echo debug_boot_weak_hash
|
||||||
|
echo panic=-1
|
||||||
local console=ttyS0
|
local console=ttyS0
|
||||||
case "$1" in
|
case "$1" in
|
||||||
qemu-system-x86_64|qemu-system-i386)
|
qemu-system-x86_64|qemu-system-i386)
|
||||||
|
|
Loading…
Reference in New Issue