Yes you're correct those three patches will give you
1.3 on 2.4.20.
Why it's crashing on boot is another question.
That backtrace seem a bit suspicious.
Any chance you can grab the kdb patches and boot
up with kdb enabled?
Note 2.4.20 did not get a lot of 1.3 testing but
it should at least boot.
On Thu, 2003-10-02 at 09:10, Marc Beuchat wrote:
> Steve,
>
> I was under the impression that the patches I applied were already
> back-ported to linux-2.4.20. In fact, I get no errors when applying the
> three xfs patches (as listed below).
>
> I guess this can have nothing to do with the fact that I am running the
> kernel on a dual process system?
>
> Marc
>
> ----- Original Message -----
> From: "Steve Lord" <lord@xxxxxxx>
> To: "Marc Beuchat" <marc@xxxxxxxx>
> Cc: <linux-xfs@xxxxxxxxxxx>
> Sent: Thursday, October 02, 2003 3:43 PM
> Subject: Re: linux 2.4.20 + xfs 1.3 crashes at boot
>
>
> > On Thu, 2003-10-02 at 08:29, Marc Beuchat wrote:
> > > I have compiled a stock kernel 2.4.20 patched with
> > > linux-2.4.20-core-xfs-1.3.0.patch, linux-xfs-1.3.0.patch and
> > > linux-2.4.20-xfs-1.3.0fixup.patch. Booting on a dual pentium III system,
> the
> > > kernel oops just after initializing the first CPU:
> >
> >
> > This looks rather like you missed something in backporting the
> > patch, the alloc_inode code is different between the kernel the
> > patch was intended for, and the one you used it one. You have to
> > look at what the patch does to the kernel, and what the base kernel
> > looks like, then make your kernel do the same thing. Some of the
> > changes needed by xfs have been incorporated into the base code
> > since 2.4.20 and hence are not present in the patch anymore.
> >
> > Steve
> >
> > --
> >
> > Steve Lord voice: +1-651-683-3511
> > Principal Engineer, Filesystem Software email: lord@xxxxxxx
> >
>
|