Date: Sun, 11 Nov 2007 20:23:53 +0000 From: =?UTF-8?B?6Z+T5a625qiZIEJpbGwgSGFja2Vy?= <askbill@conducive.net> To: freebsd-current@freebsd.org Subject: Re: Reproducible problems with re(4) on RELENG_7 and HEAD Message-ID: <473764D9.6060609@conducive.net> In-Reply-To: <bef9a7920711111158k199ec3f0uf0e26d7cbf2345f2@mail.gmail.com> References: <507457093.20071111190706@rulez.sk> <bef9a7920711111045r2d3be987k9d5f52a133dcaad4@mail.gmail.com> <47375ADD.2020001@conducive.net> <bef9a7920711111158k199ec3f0uf0e26d7cbf2345f2@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Aryeh Friedman wrote: >> OS build: >> >> FreeBSD chameleon.triligon.to 7.0-BETA1 FreeBSD 7.0-BETA1 #0: Sat Oct 20 >> 22:37:19 UTC 2007 root@chameleon.triligon.local:/usr/obj/usr/src/sys/WBH_ULE >> i386 > > FreeBSD monster 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Sun Nov 11 > 05:22:44 EST 2007 > aryeh@monster:/usr/obj/FreeBSD/FreeBSD-current/src/sys/MONSTER amd64 > > (I always do a cvs right before kernel builds so it is as recent as > about 10 mins before the above0 > _______________________________________________ My 8- stuff is on another MB (Asus P5K at the moment - restricted to add-on NIC's as the onboard one is a POS.) I *hope* the OP is not planning production use of 8-CURRENT just yet.... and you had mentioned this as a 'while ago' problem in your case, so was that not still under 7-something? Has it recurred under 8-? Can you 'make' it happen again? The OP's network environment can just as easily be a contributor as the NIC & drivers. All these are external, so only a good quality cable back-to-back eliminates them from the equation, and the OP may not have that option, even with site-tech help, on boxen he's never laid eyes on. I'll test what I can to see if it occurs here, but what has been mentioned so far has been done, and has not been problematic - yet. Bill
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?473764D9.6060609>