Re: Oops in pdflush

From: David Mosberger <>
Date: 2004-02-21 10:09:18
>>>>> On Fri, 20 Feb 2004 18:11:36 +0100, Andreas Schwab <> said:

  Andreas> David Mosberger <> writes:
  >>>>>>> On Fri, 20 Feb 2004 14:34:03 +0100, Andreas Schwab <> said:
  Andreas> This happens regularily on all our Intel Tiger SMP systems,
  Andreas> haven't seen it on UP systems, and neither on any HP system
  Andreas> we have.  Theses oopses are all from different systems
  Andreas> running kernels 2.6.2 and 2.6.3 in various incarnations.

  >> As an additional data-point: we have a tiger here, too, and it's
  >> running 2.6.2-rc2 just fine (it's a build-server so we try not to
  >> reboot it too often).  Are you saying that 2.6.1 was OK and you
  >> started to see the problems only with 2.6.2?

  Andreas> I can't tell when it started, but I think 2.6.1 already had similar
  Andreas> problems.

That's rather strange.  I'm sure the Intel folks test on Tiger all the
time and Andrew also seems to test on his Tiger quite frequently.
Is this with a particular workload?

In any case, it's not good that the stack-trace is truncated.
gcc-3.3.3 should be good enough, so I'm not sure off hand what's going
wrong.  If you could enable unwind-debugging (set UNW_DEBUG to 5 in
arch/ia64/kernel/unwind.c) and capture the resulting output during a
crash, it might get us further.

To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to
More majordomo info at
Received on Fri Feb 20 18:13:44 2004

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