sparc64/93226: DEBUG_LOCKS (really stack_save()) causes panics
kris at obsecurity.org
Sun Feb 19 12:54:50 PST 2006
On Sun, Feb 19, 2006 at 12:58:55PM +0100, Marius Strobl wrote:
> On Thu, Feb 16, 2006 at 06:43:28PM +0100, Antoine Brodin wrote:
> > Marius Strobl <marius at alchemy.franken.de> 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!
Thanks for fixing!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-sparc64/attachments/20060219/a6108fe9/attachment.bin
More information about the freebsd-sparc64