Bug 126342 (customkernel)
| Summary: | Meta bug: custom built kernels | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Brian Stein <bstein> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | rawhide | CC: | aleksey, alessandroselli, barryn, bernhard.jantscher, bugzilla, chenxia1, daniel.haenssgen, dberger, eber67, emmanuel.druon, fedora_bugzilla, gallantfox, gangaraju.chowki, grivital, helbermg, iorlov89, john, marcel.elias, mike.miller, mikhail.v.gavrilov, mr-4, nitinics, pproche, prigault, ram5019, satellitgo, sheldon.corey, srikanth.venkataraman, stanl, stevenward666, timarbuckle, tithonus.hf, triage, vinixda, vitti570, wtogami, yaricp |
| Target Milestone: | --- | Keywords: | Tracking, Triaged |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | http://mail.nl.linux.org/kernelnewbies/ | ||
| Whiteboard: | |||
| Fixed In Version: | kernel-6.8.8-300.fc40 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2024-05-03 01:41:48 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
*** Bug 126142 has been marked as a duplicate of this bug. *** In addition, it may be worth verifying your bug is present in the latest kernel you can download from www.kernel.org and if so, file a bug in the http://bugs.kernel.org bugtracker *** Bug 113192 has been marked as a duplicate of this bug. *** URL in comment #2 should be http://bugme.osdl.org *** Bug 113961 has been marked as a duplicate of this bug. *** *** Bug 114366 has been marked as a duplicate of this bug. *** *** Bug 126390 has been marked as a duplicate of this bug. *** *** Bug 126418 has been marked as a duplicate of this bug. *** *** Bug 137409 has been marked as a duplicate of this bug. *** *** Bug 105993 has been marked as a duplicate of this bug. *** *** Bug 18957 has been marked as a duplicate of this bug. *** *** Bug 120512 has been marked as a duplicate of this bug. *** *** Bug 107082 has been marked as a duplicate of this bug. *** *** Bug 58395 has been marked as a duplicate of this bug. *** *** Bug 124632 has been marked as a duplicate of this bug. *** *** Bug 132753 has been marked as a duplicate of this bug. *** *** Bug 125882 has been marked as a duplicate of this bug. *** *** Bug 111077 has been marked as a duplicate of this bug. *** *** Bug 134125 has been marked as a duplicate of this bug. *** *** Bug 125882 has been marked as a duplicate of this bug. *** *** Bug 140500 has been marked as a duplicate of this bug. *** How then is feedback supposed to get back to module owners? Why not just mark them WONTFIX? What is the policy for the case the bug is introduced by a Red Hat's patch? (Example - bug 125882). *** Bug 140500 has been marked as a duplicate of this bug. *** *** Bug 150445 has been marked as a duplicate of this bug. *** <cynic mode on> Maybe it would be better if Redhat would stick to the standard Linus kernel instead of introducing patches which make things worse. <cynic mode off> I agree with the text from Arjan van de Ven, but if redhat introduces patches which break good working configuration settings of the standard kernel, then it is the responsibility of redhat to fix it and not group my bug report (bug 150445) under this bug. > <cynic mode on> > Maybe it would be better if Redhat would stick to the standard Linus > kernel instead of introducing patches which make things worse. > <cynic mode off> Under the 2.6 kernel development model, there *are* going to be some long-term differences between vendor kernels and the mainline kernel, and that's the way Linus wants it!! For example: http://kerneltrap.org/node/4590 > NOTE! I'd personally hate some of the security things. For > example, I think the "randomize code addresses" is absolutely > horrible, just because of the startup overhead it implies > (specifically no pre-linking). I also immensely dislike > exec-shield because of the segment games it plays - I think it > makes sense in the short run but not in the long run, so I > much prefer that one as a "vendor feature", not as a "core > feature". > > So when I talk about security, I have this double-standard where > I end up convinced that many features are things that _I_ should > not do, but others likely should ;) In your case, however, it looks like the patch relates to a feature that could make it into the mainline kernel in the not-too-distant future, for what that's worth. > I agree with the text from Arjan van de Ven, but if redhat > introduces patches which break good working configuration settings > of the standard kernel, then it is the responsibility of redhat to > fix it and not group my bug report (bug 150445) under this bug. No, it's only Red Hat's *responsibility* to fix it if it breaks their default .configs. It would be nice for them to fix these types of issues, but it's not a *duty* of theirs, and it's something that people can patch at the same time that they're modifying the .config. If you would prefer to run a mainline kernel without the Red Hat patches, you can actually do that and it should work (but Red Hat won't support you -- but Fedora's not officially supported anyway so that's not really an issue here). *** Bug 150504 has been marked as a duplicate of this bug. *** *** Bug 150786 has been marked as a duplicate of this bug. *** Latest dev kernel 2.6.11-1.1185_FC4 on make bzImage barphs: LD .tmp_vmlinux1 arch/i386/kernel/built-in.o(.init.text+0x1b21): In function `init_IRQ': : undefined reference to `irq_ctx_init' arch/i386/kernel/built-in.o(.init.text+0x1b38): In function `init_IRQ': : undefined reference to `irq_ctx_init' *** Bug 152187 has been marked as a duplicate of this bug. *** *** Bug 155040 has been marked as a duplicate of this bug. *** *** Bug 155123 has been marked as a duplicate of this bug. *** Okay I have hit the same thing as comment # 30, which is but 155123. I see they are dups, but the search in bugzilla did not come up with anything for my search on irq_ctx_init . I think the difference here, is that what I'm hearing is that YOU MUST compile your kernel with kernel debugging ON else your kernel wont compile. *** Bug 166828 has been marked as a duplicate of this bug. *** *** Bug 171203 has been marked as a duplicate of this bug. *** *** Bug 178865 has been marked as a duplicate of this bug. *** I used the same source, same config file and same compiler. This should result in the same kernel, don't you think? Solved I was able to compile a runnable duplicate of the precompiled kernel by adding a "make oldconfig" step to the build procedure: make mrproper cp /boot/config-2.6.11-1.1369_FC4smp .config make oldconfig make make module_install make install make oldconfig only changed the date and kernel name in the .config file but it obviously changed some things elsewhere because the kernel now boots and runs. *** Bug 179067 has been marked as a duplicate of this bug. *** *** Bug 196563 has been marked as a duplicate of this bug. *** *** Bug 202291 has been marked as a duplicate of this bug. *** *** Bug 206580 has been marked as a duplicate of this bug. *** Based on the date this bug was created, it appears to have been reported against rawhide during the development of a Fedora release that is no longer maintained. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained. If this bug remains in NEEDINFO thirty (30) days from now, we will automatically close it. If you can reproduce this bug in a maintained Fedora version (7, 8, or rawhide), please change this bug to the respective version and change the status to ASSIGNED. (If you're unable to change the bug's version or status, add a comment to the bug and someone will change it for you.) Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we're following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. *** Bug 453498 has been marked as a duplicate of this bug. *** *** Bug 712593 has been marked as a duplicate of this bug. *** *** Bug 798464 has been marked as a duplicate of this bug. *** *** Bug 799772 has been marked as a duplicate of this bug. *** With default stock install of Fedora 17, still experiencing this issue. Why are we not on RC6 yet? *** Bug 799772 has been marked as a duplicate of this bug. *** Please don't change the fields in this bug. *** Bug 799585 has been marked as a duplicate of this bug. *** *** Bug 802117 has been marked as a duplicate of this bug. *** *** Bug 802116 has been marked as a duplicate of this bug. *** *** Bug 802144 has been marked as a duplicate of this bug. *** *** Bug 813580 has been marked as a duplicate of this bug. *** *** Bug 815115 has been marked as a duplicate of this bug. *** *** Bug 817698 has been marked as a duplicate of this bug. *** *** Bug 858592 has been marked as a duplicate of this bug. *** *** Bug 860712 has been marked as a duplicate of this bug. *** *** Bug 860712 has been marked as a duplicate of this bug. *** *** Bug 1049827 has been marked as a duplicate of this bug. *** *** Bug 1052770 has been marked as a duplicate of this bug. *** *** Bug 1055785 has been marked as a duplicate of this bug. *** *** Bug 1067698 has been marked as a duplicate of this bug. *** *** Bug 1146725 has been marked as a duplicate of this bug. *** *** Bug 1173902 has been marked as a duplicate of this bug. *** *** Bug 1178321 has been marked as a duplicate of this bug. *** *** Bug 1178322 has been marked as a duplicate of this bug. *** *** Bug 1178324 has been marked as a duplicate of this bug. *** *** Bug 1191378 has been marked as a duplicate of this bug. *** *** Bug 1197974 has been marked as a duplicate of this bug. *** *** Bug 1195402 has been marked as a duplicate of this bug. *** *** Bug 1207282 has been marked as a duplicate of this bug. *** *** Bug 1210440 has been marked as a duplicate of this bug. *** *** Bug 1221029 has been marked as a duplicate of this bug. *** *** Bug 1302346 has been marked as a duplicate of this bug. *** *** Bug 1335820 has been marked as a duplicate of this bug. *** Hi, I want to build a custom kernel. Previously, i did: - install kernel src rpm of kernel 4.4.9 - download kernelpatch 4.4.10 i start the build, as non-root, on my fedora 23 pc, with: rpmbuild -ba kernel.spec [enter] however, the build stops with: SPECS]$ rpmbuild -ba kernel.spec Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.mrPP7W + umask 022 + cd /home/krusader/rpmbuild/BUILD + patch_command='patch -p1 -F1 -s' ++ find /home/krusader/rpmbuild/BUILD -maxdepth 1 -type d -name 'kernel-4.*' ++ grep -x -v /home/krusader/rpmbuild/BUILD/kernel-4.4.fc23 + sharedirs= + : + '[' -d kernel-4.4.fc23 ']' + cd kernel-4.4.fc23 + for i in 'linux-*' + '[' -d linux-4.4.10-300.fc23.x86_64 ']' + rm -rf deleteme.x86_64 + mv linux-4.4.10-300.fc23.x86_64 deleteme-linux-4.4.10-300.fc23.x86_64 + cd .. + '[' '!' -d kernel-4.4.fc23/vanilla-4.4 ']' + cd kernel-4.4.fc23 + cp -al vanilla-4.4 linux-4.4.10-300.fc23.x86_64 + rm -rf deleteme-linux-4.4.10-300.fc23.x86_64 + cd linux-4.4.10-300.fc23.x86_64 + '[' '!' -d .git ']' + git init Initialized empty Git repository in /home/krusader/rpmbuild/BUILD/kernel-4.4.fc23/linux-4.4.10-300.fc23.x86_64/.git/ + git config user.email kernel-team + git config user.name 'Fedora Kernel Team' + git config gc.auto 0 + git add . + git commit -a -q -m baseline + xzcat /home/krusader/rpmbuild/SOURCES/patch-4.4.10.xz + patch -p1 -F1 -s Reversed (or previously applied) patch detected! Assume -R? [n] I am clueless what to do now? Thanks, - Roland (In reply to Roland from comment #80) > Hi, > > I want to build a custom kernel. > Previously, i did: > - install kernel src rpm of kernel 4.4.9 > - download kernelpatch 4.4.10 > > > i start the build, as non-root, on my fedora 23 pc, with: > rpmbuild -ba kernel.spec [enter] > > however, the build stops with: > > SPECS]$ rpmbuild -ba kernel.spec > Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.mrPP7W > + umask 022 > + cd /home/krusader/rpmbuild/BUILD > + patch_command='patch -p1 -F1 -s' > ++ find /home/krusader/rpmbuild/BUILD -maxdepth 1 -type d -name 'kernel-4.*' > ++ grep -x -v /home/krusader/rpmbuild/BUILD/kernel-4.4.fc23 > + sharedirs= > + : > + '[' -d kernel-4.4.fc23 ']' > + cd kernel-4.4.fc23 > + for i in 'linux-*' > + '[' -d linux-4.4.10-300.fc23.x86_64 ']' > + rm -rf deleteme.x86_64 > + mv linux-4.4.10-300.fc23.x86_64 deleteme-linux-4.4.10-300.fc23.x86_64 > + cd .. > + '[' '!' -d kernel-4.4.fc23/vanilla-4.4 ']' > + cd kernel-4.4.fc23 > + cp -al vanilla-4.4 linux-4.4.10-300.fc23.x86_64 > + rm -rf deleteme-linux-4.4.10-300.fc23.x86_64 > + cd linux-4.4.10-300.fc23.x86_64 > + '[' '!' -d .git ']' > + git init > Initialized empty Git repository in > /home/krusader/rpmbuild/BUILD/kernel-4.4.fc23/linux-4.4.10-300.fc23.x86_64/. > git/ > + git config user.email kernel-team > + git config user.name 'Fedora Kernel Team' > + git config gc.auto 0 > + git add . > + git commit -a -q -m baseline > + xzcat /home/krusader/rpmbuild/SOURCES/patch-4.4.10.xz > + patch -p1 -F1 -s > Reversed (or previously applied) patch detected! Assume -R? [n] > > I am clueless what to do now? > Thanks, > - Roland Did you follow the directions at https://fedoraproject.org/wiki/Building_a_custom_kernel ? save yourself the energy. I am migrated to kubuntu. *** Bug 1368670 has been marked as a duplicate of this bug. *** *** Bug 1398395 has been marked as a duplicate of this bug. *** *** Bug 1558217 has been marked as a duplicate of this bug. *** FEDORA-2024-010fe8772a (kernel-6.8.8-300.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2024-010fe8772a FEDORA-2024-010fe8772a (kernel-6.8.8-300.fc40) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report. |
The linux kernel source code can be configured in a very fine grained way, leading to an absolutely enormous amount of different possible combinations. Due to the sheer amount of possible combinations, it is not possible to make sure every combination or kernel option can be successfully built from the source code we use for the kernel rpms. In addition it is possible to (de)select options that render a computer unbootable. Therefore we cannot provide tailored help about the bug you filed regarding compiling custom kernels. If you need help with or advice about building kernels, we recommend subscribing to one of the following mailing lists and ask questions on these lists (after searching the archives). fedora-list http://www.redhat.com/mailman/listinfo/fedora-list kernelnewbies.org http://mail.nl.linux.org/kernelnewbies/