--- zzzz-none-000/linux-4.4.60/kernel/panic.c	2017-04-08 07:53:53.000000000 +0000
+++ dragonfly-4020-701/linux-4.4.60/kernel/panic.c	2018-11-08 13:36:17.000000000 +0000
@@ -25,6 +25,9 @@
 #include <linux/nmi.h>
 #include <linux/console.h>
 
+#define CREATE_TRACE_POINTS
+#include <trace/events/exception.h>
+
 #define PANIC_TIMER_STEP 100
 #define PANIC_BLINK_SPD 18
 
@@ -77,6 +80,7 @@
 	long i, i_next = 0;
 	int state = 0;
 
+	trace_kernel_panic(0);
 	/*
 	 * Disable local interrupts. This will prevent panic_smp_self_stop
 	 * from deadlocking the first cpu that invokes the panic, since
@@ -121,6 +125,18 @@
 	if (!crash_kexec_post_notifiers)
 		crash_kexec(NULL);
 
+#if defined(CONFIG_AVM_FASTIRQ)
+    /*--- der notifier will auch noch was dumpen! ---*/
+	atomic_notifier_call_chain(&panic_notifier_list, 0, buf);
+	kmsg_dump(KMSG_DUMP_PANIC);
+
+	/*
+	 * Note smp_send_stop is the usual smp shutdown function, which
+	 * unfortunately means it may not be hardened to work in a panic
+	 * situation.
+	 */
+	smp_send_stop();
+#else
 	/*
 	 * Note smp_send_stop is the usual smp shutdown function, which
 	 * unfortunately means it may not be hardened to work in a panic
@@ -135,6 +151,7 @@
 	atomic_notifier_call_chain(&panic_notifier_list, 0, buf);
 
 	kmsg_dump(KMSG_DUMP_PANIC);
+#endif/*--- #else ---*//*--- #if defined(CONFIG_AVM_FASTIRQ) ---*/
 
 	/*
 	 * If you doubt kdump always works fine in any situation,
@@ -178,6 +195,9 @@
 			mdelay(PANIC_TIMER_STEP);
 		}
 	}
+
+	trace_kernel_panic_late(0);
+
 	if (panic_timeout != 0) {
 		/*
 		 * This will not be a clean reboot, with everything