SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Some time ago I made a mistake during kernel configuration, and now I can't find the option I switched — unfortunately, I deleted the older config, so I can't do direct comparison.
So, did you delete that older kernel config file? In a later post you wrote:
Quote:
Originally Posted by SlackWar
I don't use /proc/config.gz actually, but of course I do have my own configuration files for both kernels — there are too many differences among them to make any clear conclusion.
So, did you keep the old config file but find that you have made too many changes?
If you really have messed around so much, a better idea might be to start from the original configuration and only modify some few most important changes for you. Does those changes cause your kernel to grow that much? If so, you might want to try to revert some of those changes to keep searching.
I'd like to learn, what is the cause of that BSS — to avoid it during kernel configuration. Filed a bug report — unfortunately, the kernel developers answered: „oh, presently hardly anyone uses that kernel”. Which probably should be understood as: „You know what? We don't care”.
No, I didn't — since there would be much too many options to compare, it's too different to the config file I use. It won't give me any real information.
Do you expect me to switch every spotted difference — one after another — and each time compile, compile, compile, like I had nothing better to do?
Do you expect me to switch every spotted difference — one after another — and each time compile, compile, compile, like I had nothing better to do?
Do you have any better suggestion? There is not much hope of finding someone with a crystal ball being able to tell which of all your custom changes is the one causing this.
However, you do not need to switch them one after another. It will be much faster to do a binary search. At each iteration you switch half of the suspected differences.
This is a bug in the kernel. I made a bzImage compilation using „make allnoconfig”. The 32-bit kernel is „clean”, while immediately after switch to 64-bit that BSS „tail” appears in the kernel binary. And it grows with the number of options/drivers added.
Have a check — it won't take long time.
If that is a big concern, you should try to pinpoint that bug and report it upstreams.
Quote:
Originally Posted by SlackWar
Have a check — it won't take long time.
Quote:
Originally Posted by SlackWar
You may want to examine more closely my posts in this thread; I suggest take a closer look at the first post again (and the post #6).
Quote:
Originally Posted by SlackWar
Please, have another look especially at post #1.
You don't seem to get the responce that you were expecting. I can't say for sure if that is because no one else has been suffering from this bug, but more likely, no one else is willing to spend more time than you trying to track down this problem.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
