Re: Oops in pdflush

From: Andreas Schwab <schwab_at_suse.de>
Date: 2004-02-21 01:52:03
Keith Owens <kaos@sgi.com> writes:

> You should be getting a better backtrace than that.  ia64_leave_kernel
> is the start of the interrupt handler for the oops, the preceding trace
> points are the interesting ones but they are missing.
>
> Which compiler are you using?

gcc 3.3.3

>  It could be a compiler fault, not generating correct unwind data.

The unwind check says this:

ERROR: ia64_monarch_init_handler: 186 slots, total region length = 0
1 error detected in 8160 functions.

> Can you try running with the kdb patch to see if that gives a better
> backtrace for the oops?

I'll try.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."
-
To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Received on Fri Feb 20 09:53:30 2004

This archive was generated by hypermail 2.1.8 : 2005-08-02 09:20:22 EST