Hi all -- I just tried to patch the 2.4.0 test11 kernel with the
RTL 3.0 kernel 2.4 patch and it fails -- how did you get the patch to go
thru?? I am assume from the message below you are running RTL 3.0 under
kernel 2.4.0 test 11 kernel....
Below is a trace of the patches output?
[root@czpc8 linux-2.4.0-test11]# patch -p1 < ../kernel_patch-2.4
patching file `Documentation/Configure.help'
Hunk #1 succeeded at 1592 (offset 22 lines).
Hunk #2 succeeded at 17227 (offset 1193 lines).
patching file `Makefile'
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to Makefile.rej
patching file `arch/alpha/config.in'
Hunk #1 FAILED at 52.
1 out of 1 hunk FAILED -- saving rejects to arch/alpha/config.in.rej
patching file `arch/alpha/kernel/alpha_ksyms.c'
Hunk #4 succeeded at 237 (offset 2 lines).
patching file `arch/alpha/kernel/entry.S'
Hunk #1 succeeded at 152 (offset 2 lines).
Hunk #3 succeeded at 215 (offset 2 lines).
Hunk #5 succeeded at 484 (offset 2 lines).
Hunk #7 FAILED at 694.
Hunk #8 succeeded at 724 (offset 2 lines).
1 out of 8 hunks FAILED -- saving rejects to arch/alpha/kernel/entry.S.rej
patching file `arch/alpha/kernel/irq.c'
Hunk #1 succeeded at 567 (offset 4 lines).
Hunk #3 succeeded at 666 (offset 4 lines).
patching file `arch/alpha/kernel/irq_impl.h'
patching file `arch/alpha/kernel/proto.h'
Hunk #1 succeeded at 92 (offset 17 lines).
patching file `arch/alpha/kernel/smp.c'
Hunk #1 succeeded at 623 with fuzz 2 (offset 9 lines).
Hunk #2 succeeded at 641 (offset -19 lines).
Hunk #3 succeeded at 750 (offset 9 lines).
Hunk #4 succeeded at 792 (offset -17 lines).
patching file `arch/alpha/kernel/traps.c'
Hunk #2 succeeded at 318 (offset 209 lines).
patching file `arch/i386/config.in'
Hunk #1 succeeded at 2 with fuzz 2.
patching file `arch/i386/kernel/Makefile'
Hunk #1 FAILED at 15.
1 out of 1 hunk FAILED -- saving rejects to arch/i386/kernel/Makefile.rej
patching file `arch/i386/kernel/acpi.c'
Hunk #1 succeeded at 1184 with fuzz 2 (offset 88 lines).
Hunk #2 succeeded at 1108 (offset 1 line).
Any suggestion would be most appreciated.
Thanks,
Chris
On Tue, 5 Dec 2000, huib wrote:
> At 09:56 PM 12/4/00 GMT, you wrote:
> >> Just was an idea so you could check if (no realtime linux needed) you
> >> have
> >> those APIC errors, but it seems not needed when you already know that
> >> :-)
> >Well you shouldn't recieve any apic error if you are running with 66MHz
> >bus.
> >I'm starting to get them with 75MHz
> I tried 2.4.0-test11 kernel, no apic errors at all.
>
> >> could those APIC errors be the problem ?
> >
> >No at all - many kernel developer try to find some excuses for their
> >bugs :)....
> Well, this is an unmodified RTAI example...
> Did you ever try RTAI on your bp6?
>
> huib
>
> ----------------------------------------------------------------
> email : [EMAIL PROTECTED]
> ----------------------------------------------------------------
> Tagline for Tuesday, December 05, 2000
> A single fact can spoil a good argument.
> ----------------------------------------------------------------
>
> -- [rtl] ---
> To unsubscribe:
> echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
> echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
> ---
> For more information on Real-Time Linux see:
> http://www.rtlinux.org/rtlinux/
>
>
-- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
---
For more information on Real-Time Linux see:
http://www.rtlinux.org/rtlinux/
