On Fri, Feb 23, 2007 at 08:31:44PM +0100, Martin Husemann wrote:
> On Sat, Feb 24, 2007 at 06:13:10AM +1100, matthew green wrote:
> > from this 'ok' prompt type 'ctrace' - it will give you the stack
> > trace, including the offending pc...

Gives:
	SIR Reset

	Watchdog Reset
	Externally Initiated Reset
	ok ctrace
	PC: fffffffff0002a80
	Last leaf: Fast Data Access MMU Miss

> Also, please check which of the following options you can add without
> the problem going away: LOCKDEBUG, DEBUG, DIAGNOSTIC.

DIAGNOSTIC fails where the same kernel with DIAGNOSTIC+DEBUG succeeds.  
No LOCKDEBUG on both of them.  DEBUG also changes locore.s:

	#ifndef DEBUG
	#define UTRAP(type)     sir; VTRAP(type, slowtrap)
	#else
	#define UTRAP(type)     VTRAP(type, slowtrap)
	#endif

> There are three new assembler routines, two of which are not used if
> LOCKDEBUG is enabled. DEBUG adds some window handling changes, which could
> hide bugs, and also DEBUG and DIAGNOSTIC (to different degrees) modify
> the timing, which could affect race conditions.
> 
> One of my regular test machines is broken right now (disk to be replaced
> on monday), the other one seems to work fine (it has just done a native
> build.sh) - but maybe I'm lucky, or using some magic combination of options
> that hides the bug.
> 
> 
> Martin

-- 
Juergen Hannken-Illjes - hannken@eis.cs.tu-bs.de - TU Braunschweig (Germany)