rt patch
Hi,
I have tried the rt patches available on kernel.org. Unfortunately none patches correctly with latests kernel !
Where can I download the good ones ?
Regards,
Steph
Hi,
did you try the patches located at
https://www.kernel.org/pub/linux/kernel/projects/rt/ ?
Use the corresponding mainline kernel, for example if you want to use 3.18.13-rt10, download linux 3.18.13 (from torvald's repo for example) and apply the rt patch on it .
Latest rt patches are for linux 3.18 and 4.0, so if you use the correct version it should work just fine.
Everything is explained on the wiki,
Regards,
Romain
2015-06-09 16:47 GMT+02:00 Stéphane ancelot <[email protected]>:
Quoted 11 lines
Hi,
I have tried the rt patches available on kernel.org. Unfortunately none patches correctly with latests kernel !Where can I download the good ones ?
Regards,
Steph
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi,
Yes, I did ! This is why I asked ....
and kernels from here , why v3.0 and v4.0 kernels, patch errors .
https://www.kernel.org/pub/linux/kernel/
Regards
S.Ancelot
Quoted 10 lines · Romain Perier
Hi,
did you try the patches located at
https://www.kernel.org/pub/linux/kernel/projects/rt/ ?
Use the corresponding mainline kernel, for example if you want to use 3.18.13-rt10, download linux 3.18.13 (from torvald's repo for example) and apply the rt patch on it .
Latest rt patches are for linux 3.18 and 4.0, so if you use the correct version it should work just fine.
Quoted 16 lines
Everything is explained on the wiki,
Regards,
Romain2015-06-09 16:47 GMT+02:00 Stéphane ancelot <[email protected]>:
Quoted 11 lines
Hi,
I have tried the rt patches available on kernel.org. Unfortunately none patches correctly with latests kernel !Where can I download the good ones ?
Regards,
Steph
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi,
It would propably be easier for us if you give the error.... What is the exact error ?
Regards,
Romain
2015-06-10 8:44 GMT+02:00 Stéphane ancelot <[email protected]>:
Quoted 5 lines
Hi,
Yes, I did ! This is why I asked ....
and kernels from here , why v3.0 and v4.0 kernels, patch errors .
Quoted 37 lines
https://www.kernel.org/pub/linux/kernel/
Regards
S.AncelotQuoted 29 lines · Romain Perier
Hi,
did you try the patches located at
https://www.kernel.org/pub/linux/kernel/projects/rt/ ?
Use the corresponding mainline kernel, for example if you want to use 3.18.13-rt10, download linux 3.18.13 (from torvald's repo for example) and apply the rt patch on it .
Latest rt patches are for linux 3.18 and 4.0, so if you use the correct version it should work just fine.Everything is explained on the wiki,
Regards,
Romain2015-06-09 16:47 GMT+02:00 Stéphane ancelot <[email protected]>:
Quoted 13 lines
Hi,
I have tried the rt patches available on kernel.org. Unfortunately none patches correctly with latests kernel !Where can I download the good ones ?
Regards,
Steph
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
here is an example with linux-3.18.13 and patch 3.18.13-rt10:
3.18.13-rt10
zcat ../patches-3.18.13-rt10.tar.gz |patch -p1 --dry-run
patching file arch/arm64/kernel/perf_event.c
Hunk #1 succeeded at 461 (offset -6 lines).
patching file arch/sparc/Kconfig
patching file arch/arm64/Kconfig
Hunk #1 succeeded at 61 (offset -7 lines).
patching file include/linux/notifier.h
patching file include/linux/srcu.h
patching file arch/x86/mm/iomap_32.c
Hunk #1 FAILED at 65.
1 out of 1 hunk FAILED -- saving rejects to file arch/x86/mm/iomap_32.c.rej patching file arch/arm/mm/highmem.c
patching file kernel/futex.c
patching file kernel/softirq.c
Hunk #1 FAILED at 461.
1 out of 1 hunk FAILED -- saving rejects to file kernel/softirq.c.rej patching file arch/arm/include/asm/cmpxchg.h
patching file arch/arm/mm/fault.c
patching file kernel/printk/printk.c
patching file arch/x86/kvm/lapic.c
patching file arch/arm/kvm/arm.c
patching file arch/arm/kvm/psci.c
patching file arch/powerpc/include/asm/kvm_host.h
patching file arch/powerpc/kvm/book3s_hv.c
patching file arch/s390/include/asm/kvm_host.h
patching file arch/s390/kvm/interrupt.c
patching file arch/x86/kvm/lapic.c
Hunk #1 succeeded at 1539 (offset -34 lines).
Hunk #2 succeeded at 1553 (offset -34 lines).
patching file include/linux/kvm_host.h
patching file virt/kvm/async_pf.c
patching file virt/kvm/kvm_main.c
Hunk #2 succeeded at 1741 (offset 1 line).
Hunk #3 succeeded at 1758 (offset 1 line).
Hunk #4 succeeded at 1770 (offset 1 line).
Hunk #5 succeeded at 1879 (offset 1 line).
patching file kernel/locking/rtmutex.c
Hunk #1 FAILED at 1179.
1 out of 1 hunk FAILED -- saving rejects to file kernel/locking/rtmutex.c.rej patching file include/linux/rwsem_rt.h
Hunk #1 FAILED at 20.
1 out of 1 hunk FAILED -- saving rejects to file include/linux/rwsem_rt.h.rej patching file kernel/locking/rt.c
Hunk #1 FAILED at 316.
Hunk #2 FAILED at 327.
Hunk #3 FAILED at 356.
Hunk #4 FAILED at 371.
Hunk #5 FAILED at 396.
5 out of 5 hunks FAILED -- saving rejects to file kernel/locking/rt.c.rej patching file include/linux/hrtimer.h
Reversed (or previously applied) patch detected! Assume -R? [n]
Quoted 51 lines · Romain Perier
Hi,
It would propably be easier for us if you give the error.... What is the exact error ?
Regards,
Romain2015-06-10 8:44 GMT+02:00 Stéphane ancelot <[email protected]>:
Quoted 42 lines
Hi,
Yes, I did ! This is why I asked ....
and kernels from here , why v3.0 and v4.0 kernels, patch errors .https://www.kernel.org/pub/linux/kernel/
Regards
S.AncelotQuoted 29 lines · Romain Perier
Hi,
did you try the patches located at
https://www.kernel.org/pub/linux/kernel/projects/rt/ ?
Use the corresponding mainline kernel, for example if you want to use 3.18.13-rt10, download linux 3.18.13 (from torvald's repo for example) and apply the rt patch on it .
Latest rt patches are for linux 3.18 and 4.0, so if you use the correct version it should work just fine.Everything is explained on the wiki,
Regards,
Romain2015-06-09 16:47 GMT+02:00 Stéphane ancelot <[email protected]>:
Quoted 13 lines
Hi,
I have tried the rt patches available on kernel.org. Unfortunately none patches correctly with latests kernel !Where can I download the good ones ?
Regards,
Steph
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 14 lines · St??phane ancelot
here is an example with linux-3.18.13 and patch 3.18.13-rt10:
3.18.13-rt10zcat ../patches-3.18.13-rt10.tar.gz |patch -p1 --dry-run patching file
arch/arm64/kernel/perf_event.c
Hunk #1 succeeded at 461 (offset -6 lines).
patching filearch/sparc/Kconfig
patching filearch/arm64/Kconfig
Hunk #1 succeeded at 61 (offset -7 lines).
patching fileinclude/linux/notifier.h
patching fileinclude/linux/srcu.h
patching filearch/x86/mm/iomap_32.c
Hunk #1 FAILED at 65.
1 out of 1 hunk FAILED -- saving rejects to filearch/x86/mm/iomap_32.c.rej
It appears you are applying the patch to an Android or other third-party derivative of Linux, instead of Linux proper, or that either the kernel or the patch you have fetched is corrupt. Try re-fetching everything and try again. This sequence works for me:
cd
mkdir junk
cd junk
wget -q ftp://ftp.kernel.org/pub/linux/kernel/v3.0/linux-3.18.11.tar.xz wget -q ftp://ftp.kernel.org/pub/linux/kernel/projects/rt/3.18/patch-3.18.13-rt10.patch.xz tar xf l*xz
cd linux*11
unxz <../pat*xz | patch -p1
There are some (annoying) offset errors, but no fuzzies or rejects like you have been seeing.
Joe
A message that is not in the archive (sent off-list or not yet received): 00f101d0a394$d66f73a0$834e5ae0$@[email protected]
Quoted 24 lines · Andy Pont
Hi Joe,
[snip]
Quoted 10 lines
This sequence works for me:
cd mkdir junk cd junk wget -q ftp://ftp.kernel.org/pub/linux/kernel/v3.0/linux-3.18.11.tar.xz
wget -q
ftp://ftp.kernel.org/pub/linux/kernel/projects/rt/3.18/patch-3.18.13- rt10.patch.xzQuoted 6 lines
tar xf l*xz cd linux*11 unxz <../pat*xz | patch -p1There are some (annoying) offset errors, but no fuzzies or rejects like you have been seeing.
I think the reason you see offset errors is that you are trying to patch 3.18.11 with the 3.18.13 RT patch. A quick test here substituting with :
Quoted 7 lines
wget -q
ftp://ftp.kernel.org/pub/linux/kernel/v3.0/linux-3.18.13.tar.xzgives no such errors!
Andy.
It looks like this is a proxy related problem....
using wget I am unable to use ftp://, but http:// is downloading, however this does not work with the files retrieved.
can you give me working md5sum of files downloaded ? Regards,
Steph
Quoted 1 line · Stéphane ancelot
can you give me working md5sum of files downloaded ?
"These checksums are NOT intended to replace the web of trust. It is merely a way for someone to quickly verify whether contents on one of the many kernel.org mirrors match the contents on the master mirror. While you may use them to quickly verify whether what you have downloaded matches what we have on our central storage system, you should still use the GPG web of trust to verify whether the release tarball actually matches what the kernel developer published." -
https://www.kernel.org/category/signatures.html
Begin forwarded message:
Date: Thu, 11 Jun 2015 01:25:50 +0200 (CEST)
From: Thomas Gleixner
To: Stéphane ancelot
Cc: Romain Perier, [email protected]
Subject: Re: rt patch
[snip]
Quoted 4 lines
here is an example with linux-3.18.13 and patch 3.18.13-rt10:
3.18.13-rt10zcat ../patches-3.18.13-rt10.tar.gz |patch -p1 --dry-run
You are trying to apply a tarball of patches instead of a single combined patch. Use patch-3.18.13-rt10.gz instead.
[snip]
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 27 lines · Ralf Mardorf
Quoted 1 line · Stéphane ancelot
can you give me working md5sum of files downloaded ?
"These checksums are NOT intended to replace the web of trust. It is merely a way for someone to quickly verify whether contents on one of the many kernel.org mirrors match the contents on the master mirror. While you may use them to quickly verify whether what you have downloaded matches what we have on our central storage system, you should still use the GPG web of trust to verify whether the release tarball actually matches what the kernel developer published." -
https://www.kernel.org/category/signatures.htmlBegin forwarded message:
Date: Thu, 11 Jun 2015 01:25:50 +0200 (CEST)
From: Thomas Gleixner
To: Stéphane ancelot
Cc: Romain Perier, [email protected]
Subject: Re: rt patch[snip]
Quoted 4 lines
here is an example with linux-3.18.13 and patch 3.18.13-rt10:
3.18.13-rt10zcat ../patches-3.18.13-rt10.tar.gz |patch -p1 --dry-run
Quoted 8 lines
You are trying to apply a tarball of patches instead of a single combined patch. Use patch-3.18.13-rt10.gz instead.
[snip]
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Ok, I checked,
signatures are right. files well downloaded.
I have always mistake while patching. software release problems?
unxz version 4.999.9beta
patch version 2.6
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Using a more recent system, I have following mistakes:
trying to patch a file not present in the kernel. Sincerely, I do not understand what is the problem !
checking file arch/arm64/kernel/perf_event.c
Hunk #1 succeeded at 461 (offset -6 lines).
checking file arch/sparc/Kconfig
checking file arch/arm64/Kconfig
Hunk #1 succeeded at 61 (offset -7 lines).
checking file include/linux/notifier.h
checking file include/linux/srcu.h
checking file arch/x86/mm/iomap_32.c
Hunk #1 FAILED at 65.
1 out of 1 hunk FAILED
checking file arch/arm/mm/highmem.c
checking file kernel/futex.c
checking file kernel/softirq.c
Hunk #1 FAILED at 461.
1 out of 1 hunk FAILED
checking file arch/arm/include/asm/cmpxchg.h
checking file arch/arm/mm/fault.c
checking file kernel/printk/printk.c
checking file arch/x86/kvm/lapic.c
checking file arch/arm/kvm/arm.c
checking file arch/arm/kvm/psci.c
checking file arch/powerpc/include/asm/kvm_host.h
checking file arch/powerpc/kvm/book3s_hv.c
checking file arch/s390/include/asm/kvm_host.h
checking file arch/s390/kvm/interrupt.c
checking file arch/x86/kvm/lapic.c
Hunk #1 succeeded at 1539 (offset -34 lines).
Hunk #2 succeeded at 1553 (offset -34 lines).
checking file include/linux/kvm_host.h
checking file virt/kvm/async_pf.c
checking file virt/kvm/kvm_main.c
Hunk #2 succeeded at 1741 (offset 1 line).
Hunk #3 succeeded at 1758 (offset 1 line).
Hunk #4 succeeded at 1770 (offset 1 line).
Hunk #5 succeeded at 1879 (offset 1 line).
checking file kernel/locking/rtmutex.c
Hunk #1 FAILED at 1179.
1 out of 1 hunk FAILED
can't find file to patch at input line 1031
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|patches/Revert-rwsem-rt-Do-not-allow-readers-to-nest.patch000066400000000000000000000054511252644363100240520ustar00rootroot00000000000000From 1db4ce56001465fba240916d0c8de7443cafec62 Mon Sep 17 00:00:00 2001 |From: Sebastian Andrzej Siewior <[email protected]> |Date: Wed, 25 Feb 2015 12:16:43 +0100 |Subject: [PATCH] Revert "rwsem-rt: Do not allow readers to nest" | |This behaviour is required by cpufreq and its logic is "okay": It does a |read_lock followed by a try_read_lock. |Lockdep warns if one try a read_lock twice in -RT and vanilla so it |should be good. We still only allow multiple readers as long as it is in |the same process. | |Cc: [email protected] |Signed-off-by: Sebastian Andrzej Siewior <[email protected]> |--- | include/linux/rwsem_rt.h | 1 + | kernel/locking/rt.c | 29 +++++++++++++++++++++++------ | 2 files changed, 24 insertions(+), 6 deletions(-) | |--- a/include/linux/rwsem_rt.h |+++ b/include/linux/rwsem_rt.h
--------------------------
Quoted 43 lines · Stéphane ancelot
Quoted 27 lines · Ralf Mardorf
Quoted 1 line · Stéphane ancelot
can you give me working md5sum of files downloaded ?
"These checksums are NOT intended to replace the web of trust. It is merely a way for someone to quickly verify whether contents on one of the many kernel.org mirrors match the contents on the master mirror. While you may use them to quickly verify whether what you have downloaded matches what we have on our central storage system, you should still use the GPG web of trust to verify whether the release tarball actually matches what the kernel developer published." -
https://www.kernel.org/category/signatures.htmlBegin forwarded message:
Date: Thu, 11 Jun 2015 01:25:50 +0200 (CEST)
From: Thomas Gleixner
To: Stéphane ancelot
Cc: Romain Perier, [email protected]
Subject: Re: rt patch[snip]
Quoted 4 lines
here is an example with linux-3.18.13 and patch 3.18.13-rt10:
3.18.13-rt10zcat ../patches-3.18.13-rt10.tar.gz |patch -p1 --dry-run
Quoted 9 lines
You are trying to apply a tarball of patches instead of a single combined patch. Use patch-3.18.13-rt10.gz instead. [snip]
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.htmlOk, I checked,
signatures are right. files well downloaded.
I have always mistake while patching. software release problems?
Quoted 7 lines
unxz version 4.999.9beta
patch version 2.6
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 3 lines · Stéphane ancelot
Using a more recent system, I have following mistakes:
trying to patch a file not present in the kernel. Sincerely, I do not understand what is the problem !
Ok. This is the last attempt to help you. I told you before, that:
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 1 line
zcat ../patches-3.18.13-rt10.tar.gz |patch -p1 --dry-run
You are trying to apply a tarball of patches instead of a single combined patch. Use patch-3.18.13-rt10.patch.gz instead.
https://www.kernel.org/pub/linux/kernel/projects/rt/3.18/patch-3.18.13-rt10.patch.gz
This file can be applied with "patch -p1" after decompression.
The tarball, which you are trying to use contains a series of patches and CANNOT be applied with patch.
Thanks,
tglx
THANKS GUYS IT IS SOLVED.
Quoted 15 lines · Thomas Gleixner
Quoted 3 lines · Stéphane ancelot
Using a more recent system, I have following mistakes:
trying to patch a file not present in the kernel. Sincerely, I do not understand what is the problem !Ok. This is the last attempt to help you. I told you before, that:
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 1 line
zcat ../patches-3.18.13-rt10.tar.gz |patch -p1 --dry-run
You are trying to apply a tarball of patches instead of a single combined patch. Use patch-3.18.13-rt10.patch.gz instead.
https://www.kernel.org/pub/linux/kernel/projects/rt/3.18/patch-3.18.13-rt10.patch.gz
Quoted 9 lines
This file can be applied with "patch -p1" after decompression.
The tarball, which you are trying to use contains a series of patches and CANNOT be applied with patch.
Thanks,
tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 15 lines · Thomas Gleixner
Quoted 3 lines · Stéphane ancelot
Using a more recent system, I have following mistakes:
trying to patch a file not present in the kernel. Sincerely, I do not understand what is the problem !Ok. This is the last attempt to help you. I told you before, that:
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 1 line
zcat ../patches-3.18.13-rt10.tar.gz |patch -p1 --dry-run
You are trying to apply a tarball of patches instead of a single combined patch. Use patch-3.18.13-rt10.patch.gz instead.
https://www.kernel.org/pub/linux/kernel/projects/rt/3.18/patch-3.18.13-rt10.patch.gz
Quoted 9 lines
This file can be applied with "patch -p1" after decompression.
The tarball, which you are trying to use contains a series of patches and CANNOT be applied with patch.
Thanks,
tglx
Yes, I tried using this patch too. And the kernel was downloaded here :
https://www.kernel.org/pub/linux/kernel/v3.x/linux-3.18.13.tar.xz
note: using ftp://ftp.kernel.org does not reply
Regards,
S.Ancelot
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 9 lines · Stéphane ancelot
Quoted 8 lines · Thomas Gleixner
Quoted 3 lines · Stéphane ancelot
Using a more recent system, I have following mistakes:
trying to patch a file not present in the kernel. Sincerely, I do not understand what is the problem !Ok. This is the last attempt to help you. I told you before, that:
Quoted 7 lines
Quoted 7 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 1 line
zcat ../patches-3.18.13-rt10.tar.gz |patch -p1 --dry-run
You are trying to apply a tarball of patches instead of a single combined patch. Use patch-3.18.13-rt10.patch.gz instead.
https://www.kernel.org/pub/linux/kernel/projects/rt/3.18/patch-3.18.13-rt10.patch.gz
I gave it a try . YES !!! this one rocks !
Quoted 10 lines
Quoted 10 lines
This file can be applied with "patch -p1" after decompression.
The tarball, which you are trying to use contains a series of patches and CANNOT be applied with patch.
Thanks,
tglx
Quoted 7 lines
Yes, I tried using this patch too. And the kernel was downloaded here :
https://www.kernel.org/pub/linux/kernel/v3.x/linux-3.18.13.tar.xznote: using ftp://ftp.kernel.org does not reply
Regards,
S.Ancelot
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Wed, 10 Jun 2015, Stéphane ancelot wrote:
Please:
- Do not top post
- Trim your replies
Quoted 4 lines
here is an example with linux-3.18.13 and patch 3.18.13-rt10:
3.18.13-rt10zcat ../patches-3.18.13-rt10.tar.gz |patch -p1 --dry-run
You are trying to apply a tarball of patches instead of a single combined patch. Use patch-3.18.13-rt10.gz instead.
Thanks,
tglx