On Fri, 8 Mar 2002, Wolfgang Grandegger wrote:
> Adam Wozniak wrote:
> >Thanks so much. I think that fixed it. 1+ iterations without problem.
> The real thank goes to David who found it.
>
> Well, for me the linuxppc_2_4 tree seems to be less up-to-date. It would
> be nice if somebody could
Adam Wozniak wrote:
>On Thu, 7 Mar 2002, Wolfgang Grandegger wrote:
>> David Ashley has reported lately a bug in arch/ppc/mm/ppc_mmu.c (see
>> http://lists.linuxppc.org/linuxppc-embedded/200202/msg00307.html),
>> which seems to be present in the linuxppc_2_4 tree but not in the
>> linuxppc_2_4_d
o
> >./foo 8675 1024
> >done
> >
> >Things pop after about 20 iterations. It'll choose
> a different spot
> >in the kernel to pop depending on what options I've
> compiled into the
> >kernel. I believe I've got some memory corruption
> g
hat options I've compiled into the
>kernel. I believe I've got some memory corruption going on. When I
>poke around with a hardware debugger I see values in kernel structures
>which clearly aren't right.
>
>Any known problems with shared memory in the 2.4.16 kernel o
On Thu, 7 Mar 2002, Wolfgang Grandegger wrote:
> David Ashley has reported lately a bug in arch/ppc/mm/ppc_mmu.c (see
> http://lists.linuxppc.org/linuxppc-embedded/200202/msg00307.html),
> which seems to be present in the linuxppc_2_4 tree but not in the
> linuxppc_2_4_devel tree.
>
> Hope it help
the
kernel. I believe I've got some memory corruption going on. When I
poke around with a hardware debugger I see values in kernel structures
which clearly aren't right.
Any known problems with shared memory in the 2.4.16 kernel on the MPC8260?
This should be easy enough for so
the
kernel. I believe I've got some memory corruption going on. When I
poke around with a hardware debugger I see values in kernel structures
which clearly aren't right.
Any known problems with shared memory in the 2.4.16 kernel on the MPC8260?
This should be easy enough for so
