Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#1874 - Cannot compile kernel (make problem)

Attached to Project: Arch Linux
Opened by Brice Carpentier (brice) - Friday, 03 December 2004, 22:59 GMT
Last edited by Judd Vinet (judd) - Tuesday, 07 December 2004, 17:59 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To Judd Vinet (judd)
Architecture not specified
Severity High
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

Hi,
While trying to compile a kernel, I noticed my system freezed.
After looking for the cause (you can imagine how many times the system was hard rebooted), I eventually found that at a certain time, make was spawning about a thousand processes, and that the RAM memory got fulled.
I didn't find why make got crazy though, and it's even happening with an unpatched kernel while only "make clean bzImage modules" (and it of course happens with arch's kernel26 PKGBUILD).
Probably a problem in the base packages, so I'd say it's of high severity, since a new user could install arch, update the system, and then become unable to compile his own kernel (and thus think arch sux)
This task depends upon

Closed by  Judd Vinet (judd)
Thursday, 13 January 2005, 22:13 GMT
Reason for closing:  Works for me
Comment by Judd Vinet (judd) - Tuesday, 07 December 2004, 17:59 GMT
This sounds like it will be a fun one. So far I haven't been able to reproduce it with 2.6 or 2.4 on two different machines.

what are the ~1000 processes make is spawning? cc, ld, etc?
Comment by dorphell (dorphell) - Wednesday, 05 January 2005, 20:29 GMT
Sounds like bad memory banks to me, try replacing your memory sticks?

Loading...