Re: Oops in pdflush

Andreas Schwab
2004-02-20T14:52:03Z

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."