diff options
| author | Alistair Popple <alistair@popple.id.au> | 2015-06-12 17:18:20 +1000 |
|---|---|---|
| committer | Stewart Smith <stewart@linux.vnet.ibm.com> | 2015-07-06 14:05:46 +1000 |
| commit | f5b38a25712ab74e6f8fcdaa088aaeead9655a71 (patch) | |
| tree | 1bb115ffcdecc79e82cc511155bfd8211f969e58 /core/utils.c | |
| parent | 8e63fedb0dc9d63631e01d5d5d2a1884cab3c9c9 (diff) | |
| download | skiboot-f5b38a25712ab74e6f8fcdaa088aaeead9655a71.zip skiboot-f5b38a25712ab74e6f8fcdaa088aaeead9655a71.tar.gz skiboot-f5b38a25712ab74e6f8fcdaa088aaeead9655a71.tar.bz2 | |
Disable bust_locks for general calls of abort()
Currently bust_locks is set to true whenever abort() is called. This
was done for the lock debugging code which calls abort() as its last
step. If there is a locking error there is a good chance parts of the
console code will be deadlocked (for example if it has a lock on the
scom bus).
However busting locks can cause problems, especially now that flash
data is being read in parallel as this uses the LPC bus. Instead of
getting a nice error message showing where the code aborted it is
likely the message will go missing, or it will be garbled by the flash
data. So instead of always busting locks make it so they're only
busted if they're suspected of being broken.
Signed-off-by: Alistair Popple <alistair@popple.id.au>
Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>
Diffstat (limited to 'core/utils.c')
| -rw-r--r-- | core/utils.c | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/core/utils.c b/core/utils.c index 9c94ecc..f340b4f 100644 --- a/core/utils.c +++ b/core/utils.c @@ -38,8 +38,6 @@ void __noreturn _abort(void) for (;;) ; in_abort = true; - bust_locks = true; - op_display(OP_FATAL, OP_MOD_CORE, 0x6666); prlog(PR_EMERG, "Aborting!\n"); |