When emerging kdelibs on a clean computer the process stops after compiling the libksycoca_la.all_cpp.o with the following message: Oops:0002 CPU: 0 EIP: 0010:[<c016f71b>] Not tainted EFLAGS: 00010202 eax: 00000050 ebx: c044b580 ecx: ffffffb0 edx: d3c60000 esi: 00000000 edi: 00000000 ebp: c044b580 esp: d3c61e38 ds: 0018 es:0018 ss: 0018 Process cc1plus (pid: 7585, stackpage=d3c61000) Stack: c044b580 c033fe82 c016f8a1 c044b580 c0340ce0 c0457520 c033fe82 d3c61e6c c044b580 c044c580 d3c61e6c c044c580 00000000 6f727265 30312072 33323936 00313834 c0169ba7 c044b580 c033fe82 c044c580 c0121703 00000000 c042be00 Call Trace: [<c016f8a1>] [<c0169ba7>] [<c0121703>] [<c012147d>] [<c010a4a1>] [<c01175dc>][<c010cc43>] [<c01175dc>] [<c0110018>] [<c01175fc>] [<c01175dc>] [<c012e2eb>] [<c012e413>] [<c012d0a5>] [<c0108b30>] Code: 80 4e 3a 02 f6 43 28 01 75 76 53 e8 95 ff ff ff 83 c4 04 83 <0>Kernel panic: Aiee, killing interrupt handler! In interrupt handler - not syncing
It seems that the problem can be fixed by DE-selecting the APIC option in kernel and selecting APM instead. Other options (like deselecting preempt and low latency patches, adding USE="qt" instead of USE="qtmt") have no effect. The problem seems to exist with the most recent kernel versions (last week kdelibs compiled without much problems).
If the problem is still there, please report it as a kernel/system/whatever problem, not as a kdelibs one.
