From owner-freebsd-stable@FreeBSD.ORG  Mon Jan 17 22:11:23 2005
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id E817416A4CE
	for <stable@freebsd.org>; Mon, 17 Jan 2005 22:11:23 +0000 (GMT)
Received: from mail.gmx.net (pop.gmx.net [213.165.64.20])
	by mx1.FreeBSD.org (Postfix) with SMTP id D39D643D39
	for <stable@freebsd.org>; Mon, 17 Jan 2005 22:11:22 +0000 (GMT)
	(envelope-from nakal@nurfuerspam.de)
Received: (qmail invoked by alias); 17 Jan 2005 22:11:21 -0000
Received: from p5487CD85.dip.t-dialin.net (EHLO localhost.localdomain)
	(84.135.205.133)
	by mail.gmx.net (mp007) with SMTP; 17 Jan 2005 23:11:21 +0100
X-Authenticated: #989277
From: Martin <nakal@nurfuerspam.de>
To: stable@freebsd.org
In-Reply-To: <1103832537.770.28.camel@klotz.local>
References: <1103832537.770.28.camel@klotz.local>
Content-Type: text/plain
Date: Mon, 17 Jan 2005 23:11:18 +0100
Message-Id: <1105999878.68178.16.camel@klotz.local>
Mime-Version: 1.0
X-Mailer: Evolution 2.0.3 FreeBSD GNOME Team Port 
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Subject: Re: Update to -STABLE breaks re(4) [CONT'D]
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Production branch of FreeBSD source code
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jan 2005 22:11:24 -0000


Here a followup:

> After reboot, re(4) "Realtek RTL8110S" could not be detected
> automatically. It is statically compiled into the kernel.
> The dmesg said something like "Could not send TCP packet in
> loopback mode" or similar.

This has been fixed for me, some time in January.

> Next, I added if_re_load="YES" to /boot/loader.conf (tried
> a workaround). The PC always rebooted before reaching the
> "beastie menu".

This problem still remains. I know it's weird to load a
module while it has been compiled in statically, but
it's still a bug, IMO.

Steps to reproduce:
1) On FreeBSD/amd64, compile re(4) support into a STABLE kernel.
2) Add if_re_load="YES" to /boot/loader.conf.
3) Reboot.

What happens?

After loading the kernel image, re(4) module is about to be loaded
and the machine does a a hard reset instantly.

I hope it helps to find the problem.

Martin