Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 4 Nov 2003 09:35:21 -0500 (EST)
From:      Andrew Gallatin <gallatin@cs.duke.edu>
To:        Kris Kennaway <kris@obsecurity.org>
Cc:        alpha@freebsd.org
Subject:   Re: New alpha 5.x bug
Message-ID:  <16295.47401.948500.681512@grasshopper.cs.duke.edu>
In-Reply-To: <20031101103955.GA42891@rot13.obsecurity.org>
References:  <20031101103955.GA42891@rot13.obsecurity.org>

next in thread | previous in thread | raw e-mail | index | archive | help

Kris Kennaway writes:
 > On a whim, I updated one of the alpha package machines to -current.
 > It lasted a few hours under load before going into an infinite loop
 > displaying the following on the console:
 > 
 > prologue botch: displacement 32
 > frame size botch: adjust register offsets?
 > frame size botch: adjust register offsets?
 > prologue botch: displacement 32
 > frame size botch: adjust register offsets?
 > frame size botch: adjust register offsets?
 > prologue botch: displacement 32

Its coming from the ddb stack trace code.

I imagine that you're probably panic'ing with a trashed stack, and ddb
is horribly confused.  Try disabling ddb traces on panic and LORs and
see if you can get a real panic message (or log the console output to
a file if its via a serial console).

Drew



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16295.47401.948500.681512>