From owner-freebsd-current@FreeBSD.ORG Sun May 17 18:46:28 2009 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DD0F21065676; Sun, 17 May 2009 18:46:28 +0000 (UTC) (envelope-from bra@fsn.hu) Received: from people.fsn.hu (people.fsn.hu [195.228.252.137]) by mx1.freebsd.org (Postfix) with ESMTP id 149338FC15; Sun, 17 May 2009 18:46:27 +0000 (UTC) (envelope-from bra@fsn.hu) Message-ID: <4A1057D2.5090800@fsn.hu> Date: Sun, 17 May 2009 20:30:42 +0200 From: Attila Nagy User-Agent: Thunderbird 2.0.0.21 (X11/20090318) MIME-Version: 1.0 To: current@FreeBSD.org, net@freebsd.org X-Stationery: 0.4.8.14 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (people.fsn.hu [0.0.0.0]); Sun, 17 May 2009 20:30:43 +0200 (CEST) Cc: Xin LI Subject: Routing related crash in -CURRENT, introduced between 5th May and yesterday 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: Sun, 17 May 2009 18:46:29 -0000 Hello, Somewhere between 5th May and yesterday there was a (routing related?) change, which causes this machine crash at boot: http://picasaweb.google.com/nagy.attila/20090517Fbsd8Crash#5336859077575768514 http://picasaweb.google.com/nagy.attila/20090517Fbsd8Crash#5336859069031814370 The machine itself is an HP DL380G4 with bge interfaces and netbooted via PXE. A build, compiled on 5th May works fine, but this (compiled today, but with a yesterday build this is also the same) isn't. 7-STABLE also works fine on these kind of machines and this setup. Another interesting thing is while 7-STABLE (and from 5.x to 7-STABLE as of the start of May (that's the latest build we use, if there were bge related changes MFC-ed since that, I don't know)) can boot on this kind of machines with the default hw.bge.allow_asf=1, -CURRENT can't. It stops right after recognizing disk devices, even with verbose boot. That is the point, where DHCP (still netbooting) kicks in... I think these kind of machines are not rare (I admit that not everybody uses netbooting with them, but -CURRENT freezes even when installing from CD, when the installer tries to configure the interfaces), so it would be good to correct (and not MFC what is on HEAD until that) this regression. If I can do any debugging or give more information, please let me know! Thanks,