sparc64/93226: DEBUG_LOCKS (really stack_save()) causes panics on sparc64

Marius Strobl marius at
Sun Feb 19 03:59:05 PST 2006

On Thu, Feb 16, 2006 at 06:43:28PM +0100, Antoine Brodin wrote:
> Marius Strobl <marius at> wrote:
> > Ok, how about the attached patch? It uses two pairs of dummy symbols
> > in exception.S to determine in stack_save() whether it was one of the
> > tl0_*() or tl1_*() asm functions; one pair for those in the .trap
> > section that is "magically" placed at the beginning of the .text
> > section via the linker script and the other pair for those in the
> > regular .text section. That way we don't rely on the location of
> > these functions in the kernel and don't have the performance penalty
> > of *search_symbol()/*symbol_values(). For consistency db_backtrace()
> > is changed to also use the new markers instead of bcmp()'ing with
> > the symbol names.
> If this fixes the panic, that's excellent

Yes, does :) Thanks for your help!


This mail was scanned by AntiVir Milter.
This product is licensed for non-commercial use.
See for details.

More information about the freebsd-sparc64 mailing list