On Sat, May 04, 2002 at 21:54:08 +0200, Martin Blapp wrote: > Hi all, > > I experiment very strange problems here at the moment with > a new server. > > Buildworld survives about 30 secondy, the errors are SIG4 (90%) > and SIG11 (10%). And I cannot compile any important programs :-/ > > I've exchanged all relevant parts: > > - Power Supply: 300W, for PIV with additional CPU supply > - CPU (PIV, 2Ghz, 512K cache) > - Ram with ECC correction > - Board (Intel D845BG) > - SCSI Card. (it happens also on ATA) > > We have these boards running fine here. And now to the strange part. > It does not happen with STABLE. > > This let's me beleave that this is a CURRENT problem. >
Unfortunately not. Since 1 week these types of errors (cc -pipe exiting with some signal) also occurs on -stable for me with a P-IV 1.7GHz. I tried to figure out which commit to RELENG_4 introduced the problems and found that the problems began with the ipfilter update to v3.4.27. But this seems not to be the real cause, as a workaround I found (dropping -pipe from CFLAGS) has nothing to do with ipfilter. Here are some symptoms from my /var/log/messages pid 92638 (cc), uid 0: exited on signal 4 (core dumped) pid 44494 (cc), uid 0: exited on signal 10 (core dumped) pid 23068 (sed), uid 0: exited on signal 11 (core dumped) pid 19046 (egrep), uid 0: exited on signal 4 (core dumped) pid 28452 (sed), uid 0: exited on signal 11 (core dumped) pid 65784 (cpp0), uid 0: exited on signal 4 (core dumped) pid 61931 (sed), uid 0: exited on signal 10 (core dumped) pid 80953 (cc), uid 0: exited on signal 10 (core dumped) pid 32562 (cc), uid 0: exited on signal 10 (core dumped) pid 12812 (sed), uid 0: exited on signal 11 (core dumped) pid 36423 (cc), uid 0: exited on signal 10 (core dumped) pid 87631 (cc), uid 0: exited on signal 4 (core dumped) pid 58087 (sed), uid 0: exited on signal 11 (core dumped) Again: there are no hardware problems (memory, cooling, etc.) here, it is only related to some kernels. Booting a kernel which is old enough makes the system running flawlessly. Would be nice if that could be resolved before -RELEASE (but it seems to be a difficult bug to track down). Best regards Udo Schweigert -- Udo Schweigert, Siemens AG | Voice : +49 89 636 42170 CT IC 3, Siemens CERT | Fax : +49 89 636 41166 D-81730 Muenchen / Germany | email : [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
