My Oracle Support Banner

Analyzing TO/BTO/DTO and BERR/DBERR Solaris Crash Dumps (Doc ID 1003640.1)

Last updated on JANUARY 30, 2019

Applies to:

Solaris Operating System - Version 8.0 and later
All Platforms
***Checked for relevance on 30-Jul-2013***

Goal

When a system panics with a bad trap from an MMU miss, it is because the MMU does not have a translation entry for the virtual address(VA) used in the instruction to a physical(hardware) address(PA).
TO/BTO/DTO and BERR/DBERR panics are similar, in that they are caused by referencing an illegal address. In this case, however, the illegal address is the physical address(PA).

For practical purposes, a TO/BTO/DTO is caused by a PA that's valid for the system, but there is nothing at the address the PA is referencing, or the device at that address did not respond in time.

A BERR/DBERR, indicates that the PA being used is always illegal, or is reserved for the system.

Further details about TO/BTO/DTO/BERR/DBERR events, may be obtained from the specific processor reference manual.

Note:

TO = Timeout
BTO = Bus Timeout
DTO = Disrupting Timeout
BERR = Bus Error
DBERR = Disrupting Bus Error

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.