I've been doing a lot of panicing recently trying to track down a dtrace
problem, and have noticed that only the first call of doadump() shows a
progress display, resulting in uncertainty as to whether or not the dump is
happening, at least with a low amount of RAM dumping to a ramdisk (the
panicing machine is a VM)
This fixes it for me:
--- a/sys/amd64/amd64/minidump_machdep.c
+++ b/sys/amd64/amd64/minidump_machdep.c
@@ -226,6 +226,9 @@ minidumpsys(struct dumperinfo *di)
struct minidumphdr mdhdr;
retry_count = 0;
+ for (i = 0; i < 10; i++)
+ progress_track[i].visited = 0;
+
retry:
retry_count++;
counter = 0;
--
Sorry for the below...
The information contained in this message is confidential and intended for the
addressee only. If you have received this message in error, or there are any
problems with its content, please contact the sender.
iCritical is a trading name of Critical Software Ltd. Registered in England:
04909220.
Registered Office: IC2, Keele Science Park, Keele, Staffordshire, ST5 5NH.
This message has been scanned for security threats by iCritical.
www.icritical.com
_______________________________________________
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
