ia64/xen-unstable

changeset 3772:677aebca60b9

bitkeeper revision 1.1169 (420b96d48xPe7Ok5mXEY_QuvSxXLxw)

Improve documentation a little.
author sos22@douglas.cl.cam.ac.uk
date Thu Feb 10 17:16:04 2005 +0000 (2005-02-10)
parents 37ac5c3e6403
children 9ee09144e830
files docs/misc/crashdb.txt
line diff
     1.1 --- a/docs/misc/crashdb.txt	Thu Feb 10 17:15:51 2005 +0000
     1.2 +++ b/docs/misc/crashdb.txt	Thu Feb 10 17:16:04 2005 +0000
     1.3 @@ -34,3 +34,17 @@ and I'm not terribly interested in putti
     1.4  As soon as you reach the debugger, we disable interrupts, the
     1.5  watchdog, and every other CPU, so the state of the world shouldn't
     1.6  change too much behind your back.
     1.7 +
     1.8 +
     1.9 +Reasons why we might fail to reach the debugger:
    1.10 +-----------------------------------------------
    1.11 +
    1.12 +-- In order to stop the other processors, we need to acquire the SMP
    1.13 +   call lock.  If you happen to have crashed in the middle of that,
    1.14 +   you're screwed.
    1.15 +-- If the page tables are wrong, you're screwed
    1.16 +-- If the serial port setup is wrong, badness happens
    1.17 +-- We acquire the console lock at one stage XXX this is unnecessary and
    1.18 +   stupid
    1.19 +-- Obviously, the low level processor state can be screwed in any
    1.20 +   number of wonderful ways