Date: Mon, 29 Apr 2002 20:44:29 +0200 From: Udo Schweigert <Udo.Schweigert@siemens.com> To: Brian Somers <brian@freebsd-services.com> Cc: Ruslan Ermilov <ru@FreeBSD.ORG>, Darren Reed <darrenr@reed.wattle.id.au>, Doug Barton <DougB@FreeBSD.ORG>, current@FreeBSD.ORG, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: ipfilter not broken for me Message-ID: <20020429184429.GA30349@alaska.cert.siemens.de> In-Reply-To: <200204291645.g3TGj54G081944@hak.lan.Awfulhak.org> References: <20020427141441.GC35685@sunbay.com> <200204291645.g3TGj54G081944@hak.lan.Awfulhak.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Apr 29, 2002 at 17:45:05 +0100, Brian Somers wrote: >> On Sat, Apr 27, 2002 at 04:01:28PM +1000, Darren Reed wrote: > >> In some email I received from Doug Barton, sie wrote: > > >> On Fri, 26 Apr 2002, Ruslan Ermilov wrote: > > >>=20 > > > >> I tested this on i386 only with 2 days old -CURRENT (today's is > > > >> broken due to the import of latest IPFilter suite) > > >>=20 > > >> I updated to the latest and greatest last night around midnight > > >> and built/installed -current just fine. What about the ipfilter import = >> is > > >> broken, and have you let Darren know? I haven't seen anything on the li= >> sts > > >> about it... > >>=20 > >> I have not received any email about it. I tested building all the ipfilt= >> er > >> binaries and kernel after the import and came up clean. if ref5 was a bit > >> quicker.... > >>=20 >> That was probably a local problem on one of the Brian's fast machines >> where I initially attempted to finally test my patch (unsynched cvsup >> update?). Sorry for the false alarm, I can't check it right now anyway. > > Yes... I've had periods where the compiler drops cores all over the > place, and other periods where things work fine. It's on a P4-1.7Ghz > and has behaved like this since about last August. > > The only variable is the kernel - some kernels work and some don't. > I've spent many 10s of hours trying to track it down, and I still > have no idea what causes it - except that some kernels ``just work'' > and some don't. > > Maybe it depends on the humidity in the room when a kernel is built > or something - and I'm only half joking here ! > > FWIW ru, /boot/kernel/kernel seems ok now. /boot/kernel.sig/kernel > isn't. > I discovered the same problem here for a P4-1.7Ghz with -stable. First thing I discovered: this only happens if you have "-pipe" in your CFLAGS in /etc/make.conf. It seems something with pipe handling is broken on these fast machines, which makes cc fail. Currently I'm trying to figure out which commit brought that in. Probabilty is high that it has to do with ipfilter, but I'm not quite sure. Definitively it is not a problem local to Brian. 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 : Udo.Schweigert@siemens.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020429184429.GA30349>