On Sun, Nov 18, 2007 at 10:49:05AM +0100, Thomas Klausner wrote:

> I updated to a debug kernel from about 8 hours ago, and the bulk build
> I started then is still running.
> 
> However, in my dmesg output I see:
> pid 12696 (try), uid 0: exited on signal 10 (core dumped)
> pid 19715 (conftest), uid 0: exited on signal 11 (core dumped)
> pid 11407 (conftest), uid 0: exited on signal 6 (core dumped)
> pid 13556 (a2ps), uid 0: exited on signal 11 (core dumped)
> pid 3877 (conftest), uid 0: exited on signal 6 (core dumped)
> pid 5407 (conftest), uid 0: exited on signal 11 (core dumped)
> pid 10971 (conftest), uid 0: exited on signal 6 (core dumped)
> 
> The first one, try, happens when building perl (repeatable for me).
> I'm not sure when the others happened, sorry.

I think this is hardware related. What kind of CPU do you have? Here are
some of the nastier kernel bugs in -current I know about:

- I've seen two reports of an assertion failure in uvm_fault.c.

- There is a longstanding use-after-free in the file descriptor code.

- There is an occasional error from sleepq_unsleep() when triggered from
  the softclock interrupt.

- Job control signals sent from a tty don't work correctly.

I have only been able to reproduce the last one but I'm looking into all
of them.

Thanks,
Andrew