aboutsummaryrefslogtreecommitdiffstats
path: root/docs/misc/crashdb.txt
diff options
context:
space:
mode:
authorsos22@douglas.cl.cam.ac.uk <sos22@douglas.cl.cam.ac.uk>2005-02-10 17:16:04 +0000
committersos22@douglas.cl.cam.ac.uk <sos22@douglas.cl.cam.ac.uk>2005-02-10 17:16:04 +0000
commit252678160f674ff6adda60e10e865f1193c3b64f (patch)
tree2e7a67d0917ae2931e2e292598aace7884f1c3d1 /docs/misc/crashdb.txt
parentc4d681a4186247f24c941ba86a19ced71bf7c701 (diff)
downloadxen-252678160f674ff6adda60e10e865f1193c3b64f.tar.gz
xen-252678160f674ff6adda60e10e865f1193c3b64f.tar.bz2
xen-252678160f674ff6adda60e10e865f1193c3b64f.zip
bitkeeper revision 1.1169 (420b96d48xPe7Ok5mXEY_QuvSxXLxw)
Improve documentation a little.
Diffstat (limited to 'docs/misc/crashdb.txt')
-rw-r--r--docs/misc/crashdb.txt14
1 files changed, 14 insertions, 0 deletions
diff --git a/docs/misc/crashdb.txt b/docs/misc/crashdb.txt
index ebf5e9f9b9..a366f72f5d 100644
--- a/docs/misc/crashdb.txt
+++ b/docs/misc/crashdb.txt
@@ -34,3 +34,17 @@ and I'm not terribly interested in putting it back.
As soon as you reach the debugger, we disable interrupts, the
watchdog, and every other CPU, so the state of the world shouldn't
change too much behind your back.
+
+
+Reasons why we might fail to reach the debugger:
+-----------------------------------------------
+
+-- In order to stop the other processors, we need to acquire the SMP
+ call lock. If you happen to have crashed in the middle of that,
+ you're screwed.
+-- If the page tables are wrong, you're screwed
+-- If the serial port setup is wrong, badness happens
+-- We acquire the console lock at one stage XXX this is unnecessary and
+ stupid
+-- Obviously, the low level processor state can be screwed in any
+ number of wonderful ways