On Mon, Feb 17, 2003 at 06:02:03PM -0800, Linus Torvalds wrote:
> Can you check mjb 1-3 too? The better it gets pinpointed, the easier
> it's going to be to find.
Sure... I'll test them later on.
> Also, if you can figure out _which_ part of the patch makes a
> difference, that would obviously be even better.
I'll try to narrow this down.
> Part of the stuff in mjb is already merged in later kernels (ie
> things like using sequence locks for xtime is already there in
> 2.5.60, so clearly that doesn't seem to be the thing that helps your
> situation).
I don't think it's anything really obvious. If the problem I'm seeing
is the same as the one showing up on *some* IBM NUMA-Q (or whatever
they are) boxen then it's probably not a driver or fs thing --- as we
have nothing in common.
Now... it could be two different problems, except the same kernel
which the IBM people found works for them also works for me.
Oddly, wli has not seen this problem and he's using similar hardware
(I think) to the other IBM people and the same compiler as me.
> Do you use the starfire driver?
Nope.
A stripped down kernel, compile for a 486 with no IO-APIC support (in
an attempt to slow things down and hopefully avoid possible hardware
problems such as overheating) still reboots on me.
The only thing I can think of is a triple-fault... I'm wondering
about using gcc-3.2 instead of 2.95.4 (Debian blah blort blem) on the
off chance it's a weird compiler problem.
--cw
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Feb 23 2003 - 22:00:20 EST