[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
nbctfmerge runs for hours on custom i386 kernels
As the Subject: notes, building custom kernels for i386-current (on
amd64-7.0_STABLE host) takes several hours for each kernel. The output
of 'top' shows 'nbctfmerge' (run after the final link of a kernel)
consuming nearly 100 percent of cpu (host is single-core hyperthreaded).
Attaching 'ktruss' to the process shows no output for a prolonged period
of time (CPU-bound, I presume) followed by short bursts of file I/O and/or
"m*map()" calls followed by another prolonged period of CPU-only operation.
I have not observed this behavior when building any of the standard
kernels, but only most if not all of my custom kerenels (which simply
include GENERIC and exclude unecessary items with the "no foo at bar"
I have so-far observed this only on i386 and not any of the other
architectures I build.
|/"\ John D. Baker, KN5UKS NetBSD Darwin/MacOS X
|\ / jdbaker[snail]mylinuxisp[flyspeck]com OpenBSD FreeBSD
| X No HTML/proprietary data in email. BSD just sits there and works!
|/ \ GPGkeyID: D703 4A7E 479F 63F8 D3F4 BD99 9572 8F23 E4AD 1645
Main Index |
Thread Index |