Re: Compiling kernel locks system.

"Vivaldi" ([email protected] via lfs-support Mailing List) <[email protected]> Fri, 12 Dec 2025 07:11:15 -0600
Newsgroups gmane.linux.lfs.support
Message-ID <[email protected]>
On 12/12/25 4:31 AM, Rainer Fiebig ([email protected] via lfs-support 
Mailing List) wrote:
> Am 12.12.25 um 00:22 schrieb Vivaldi ([email protected] via
> lfs-support Mailing List):
>> On 12/11/25 10:18 AM, Rainer Fiebig ([email protected] via lfs-support
>> Mailing List) wrote:
>>> Am 09.12.25 um 13:36 schrieb Vivaldi ([email protected] via
>>> lfs-support Mailing List):
>>>> I'm running LFS/BLFS 12.4 and built a mid-release LFS (r12.4-47-systemd)
>>>> but can't compile a kernel.  Everything goes well through chapter 9 but
>>>> compiling the kernel is quite slow and eventually locks my box.  I've no
>>>> choice but to power down.
>>> Perhaps your system ran out of memory and began to swap (slow) until
>>> there wasn't any swap-space left (lock).
>>>
>>> Rainer
>>>
>>>
>>>
>> I had the same thought and your reply prompted me to try something I'd
>> been contemplating.  Bottom line, I can successfully compile LFS
>> 12.4-47/linux-6.17.9 using chroot when booted into 12.4 if I I don't
>> start X.
> You could get a better idea of what's going on (cpu-/memory-/swap-usage)
> by running "top" from an other x-terminal or VT.  "vmstat" and "free"
> provide a snapshot of the current memory-situation.
>
>> This makes little sense to me as I previously reported I can compile
>> when booted into 12.4 in X if not using chroot.  Plus, I've always
>> compiled a new installation from a window opened in X.    I did so this
>> time with 12.4-47 and things worked as usual through chapter 9.  My
>> procedure is to make an image after finishing chapter 8.  I then restore
>> the image and use the "Entering the Chroot Environment" instructions
>> from chapter 7 from a window opened in X.  Is that wrong?
> I'm not sure what you mean by "image".  A backup?  And why would you
> restore that "image" instead of simply continuing where you left?
>
>
> Rainer
>
>
I'll try cpu-/memory-swap-usage this weekend.  But I still wonder why 
there's a problem compiling a kernel with chroot as I can easily compile 
a 6.17.9 kernel from LFS 12.4 in X without using chroot.  And why can I 
compile all LFS 12.4-47 packages until I attempt compiling a kernel with 
chroot?

I should have said I restore the image if necessary.  I create an image 
with fsarchiver and do usually then proceed.  But I'll sometimes resume 
later and may have restored another image in the interim.

-- 
http://lists.linuxfromscratch.org/sympa/info/lfs-support
Unsubscribe: See the above information page