From owner-freebsd-current@FreeBSD.ORG Thu Nov 10 08:18:22 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 90BFD16A41F for ; Thu, 10 Nov 2005 08:18:22 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id D549A43D49 for ; Thu, 10 Nov 2005 08:18:21 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from flame.pc (adsl-66-124-231-46.dsl.snfc21.pacbell.net [66.124.231.46]) (authenticated bits=0) by igloo.linux.gr (8.13.4/8.13.4/Debian-3) with ESMTP id jAA8HmYb020452; Thu, 10 Nov 2005 10:17:56 +0200 Received: by flame.pc (Postfix, from userid 1001) id CA0AD1165C; Thu, 10 Nov 2005 00:17:36 -0800 (PST) Date: Thu, 10 Nov 2005 00:17:36 -0800 From: Giorgos Keramidas To: Eric Anderson Message-ID: <20051110081736.GA1855@flame.pc> References: <43724C11.5090201@centtech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43724C11.5090201@centtech.com> X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (score=-3.436, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.96, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@ceid.upatras.gr X-Mailman-Approved-At: Thu, 10 Nov 2005 12:12:17 +0000 Cc: FreeBSD Current Subject: Re: Instant reboot on new interface coming up X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Nov 2005 08:18:22 -0000 On 2005-11-09 13:20, Eric Anderson wrote: > I've been having issues lately when trying to bring up a new interface. > It's a hard problem to actually see, because it makes my machine > instantly reboot. > > Here's what I see: > Normally, I use ath0 for wireless, and occasionally I use em0. > Recently, when I was at a location with no wireless and no dhcp support, > I powered up my laptop, plugged in to em0, and did an ifconfig em0 xxx. > After a few seconds, the system spontaneously reboots. I figured > out that killing dhclient on that interface before attempting to > manually configure it helped. > > Now, I also tried to connect using ppp to a GPRS network (via bluetooth > through my cell phone). This used to work just fine, probably a few > months ago. This time, I killed all dhclients, connected the bluetooth > pieces, and then ran rfcomm_pppd, which creates a tun0 interface. When > the interface was created, and brought up without dhclient, everything > worked ok. When I accidentally left dhclient running, and tun0 was > created, when the device got it's IP address, machine rebooted. > > I have various machine logs/dmesg/etc here: > http://www.googlebit.com/freebsd/ > (labeled by date - look for the most current versions) > > I'm running 7.0-CURRENT as of a few days ago. How many days? You need at least a version that includes the following commit, otherwise you may have problems with ACPI or mbuf allocation: % glebius 2005-11-06 16:47:59 UTC % % FreeBSD src repository % % Modified files: % sys/kern kern_mbuf.c % Log: % Fix panic string in last revision. % % Revision Changes Path % 1.15 +1 -1 src/sys/kern/kern_mbuf.c