Date: Wed, 28 May 2008 11:08:48 +0200 From: Gerrit =?ISO-8859-1?Q?K=FChn?= <gerrit@pmp.uni-hannover.de> To: freebsd-stable@freebsd.org Cc: pyunyh@gmail.com Subject: Re: broken re(4) 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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 28 May 2008 09:28:23 +0900 Pyun YongHyeon <pyunyh@gmail.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080528110848.560f9f07.gerrit>