From owner-freebsd-stable@FreeBSD.ORG Wed May 28 09:08:51 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DD5BE1065673 for ; Wed, 28 May 2008 09:08:51 +0000 (UTC) (envelope-from gerrit@pmp.uni-hannover.de) Received: from mrelay1.uni-hannover.de (mrelay1.uni-hannover.de [130.75.2.106]) by mx1.freebsd.org (Postfix) with ESMTP id 47C748FC12 for ; Wed, 28 May 2008 09:08:51 +0000 (UTC) (envelope-from gerrit@pmp.uni-hannover.de) Received: from www.pmp.uni-hannover.de (www.pmp.uni-hannover.de [130.75.117.2]) by mrelay1.uni-hannover.de (8.14.2/8.14.2) with ESMTP id m4S98mXG011495; Wed, 28 May 2008 11:08:49 +0200 Received: from pmp.uni-hannover.de (arc.pmp.uni-hannover.de [130.75.117.1]) by www.pmp.uni-hannover.de (Postfix) with SMTP id 2F0931E5; Wed, 28 May 2008 11:08:48 +0200 (CEST) Date: Wed, 28 May 2008 11:08:48 +0200 From: Gerrit =?ISO-8859-1?Q?K=FChn?= To: freebsd-stable@freebsd.org Message-Id: <20080528110848.560f9f07.gerrit@pmp.uni-hannover.de> In-Reply-To: <20080528002823.GA63696@cdnetworks.co.kr> References: <20080527165232.2acbb00f.gerrit@pmp.uni-hannover.de> <20080528002823.GA63696@cdnetworks.co.kr> Organization: Albert-Einstein-Institut (MPI =?ISO-8859-1?Q?f=FCr?= Gravitationsphysik & IGP =?ISO-8859-1?Q?Universit=E4t?= Hannover) X-Mailer: Sylpheed 2.4.8 (GTK+ 2.12.9; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-PMX-Version: 5.4.1.325704, Antispam-Engine: 2.6.0.325393, Antispam-Data: 2008.5.28.15445 Cc: pyunyh@gmail.com Subject: Re: broken re(4) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 May 2008 09:08:52 -0000 On Wed, 28 May 2008 09:28:23 +0900 Pyun YongHyeon wrote about Re: broken re(4): PY> > Any hints what I should do next to find the culprit? PY> There were similiar reports on this issue. It seems that it's very PY> hard to make re(4) work so many RTL8168/8169/8111 revisions without PY> documentation as different revisions require different workaround. I know. However, in this case I think I have identical hardware, but two boards work, and one doesn't (which seems very strange to me). PY> Anyway, would you try this one? The patch was generated against HEAD PY> but it would apply to STABLE too. PY> http://people.freebsd.org/~yongari/re/re.HEAD.20080519 Thanks. I applied the patch and a new nanobsd image is build right now. I will report later today about the results. cu Gerrit