From owner-freebsd-stable@FreeBSD.ORG Fri Feb 24 01:12:02 2012 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D001A1065675 for ; Fri, 24 Feb 2012 01:12:02 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pw0-f54.google.com (mail-pw0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 624DE8FC1C for ; Fri, 24 Feb 2012 01:12:02 +0000 (UTC) Received: by pbcxa7 with SMTP id xa7so2227817pbc.13 for ; Thu, 23 Feb 2012 17:12:02 -0800 (PST) Received-SPF: pass (google.com: domain of pyunyh@gmail.com designates 10.68.232.230 as permitted sender) client-ip=10.68.232.230; Authentication-Results: mr.google.com; spf=pass (google.com: domain of pyunyh@gmail.com designates 10.68.232.230 as permitted sender) smtp.mail=pyunyh@gmail.com; dkim=pass header.i=pyunyh@gmail.com Received: from mr.google.com ([10.68.232.230]) by 10.68.232.230 with SMTP id tr6mr922531pbc.165.1330045922013 (num_hops = 1); Thu, 23 Feb 2012 17:12:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=/EDSg/PgCtucCP1aICwMEHmwHvO4DiwWpxVDFjFTVZo=; b=UjuOZoJ4HFf6IjTeMczvCqvEg3t87fv64clGRwLHSpDVWVIScCARx0qvHxvTtSfs3o IWcZ0v4/f+kCPMs/gXQUQ1vT1Sv93sC92Jqf7DiPqN1seBuUD7GeFmpAP6ly+KYMwAfx 79tZcmdYgTnQEBes3BeQrlAvoeiZsSxqBlIv8= Received: by 10.68.232.230 with SMTP id tr6mr767753pbc.165.1330045921983; Thu, 23 Feb 2012 17:12:01 -0800 (PST) Received: from pyunyh@gmail.com ([114.111.62.249]) by mx.google.com with ESMTPS id x3sm2871926pbg.35.2012.02.23.17.11.59 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 23 Feb 2012 17:12:01 -0800 (PST) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Fri, 24 Feb 2012 10:11:55 -0800 From: YongHyeon PYUN Date: Fri, 24 Feb 2012 10:11:55 -0800 To: Attila Nagy Message-ID: <20120224181155.GB18456@michelle.cdnetworks.com> References: <4F449E0B.2040909@fsn.hu> <20120223041516.GI6861@michelle.cdnetworks.com> <4F44FF2A.9050505@fsn.hu> <20120223204401.GB13815@michelle.cdnetworks.com> <4F45DF95.9050309@fsn.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4F45DF95.9050309@fsn.hu> User-Agent: Mutt/1.4.2.3i Cc: stable@freebsd.org Subject: Re: Fatal trap 19, Stopped at bge_init_locked+ and bge booting problems X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Feb 2012 01:12:03 -0000 On Thu, Feb 23, 2012 at 07:41:25AM +0100, Attila Nagy wrote: > On 02/23/12 21:44, YongHyeon PYUN wrote: > >I have to ask more information for the controller to Broadcom. > >Not sure whether I can get some hint at this moment though. :-( > Is there anything I can do? I ask this because I have to give back this > server very soon. > > > >Given that you also have USB related errors, could you completely > >remove bge(4) in your kernel and see whether it can successfully > >boot up? > >I think you can add the following entries to /boot/device.hints > >without rebuilding kernel. > > > >hint.bge.0.disabled="1" > >hint.bge.1.disabled="1" > >hint.bge.2.disabled="1" > >hint.bge.3.disabled="1" > This does not help. > Removing bge makes it stop here: > da0 at ciss0 bus 0 scbus0 target 0 lun 0 > da0: Fixed Direct Access SCSI-5 device > da0: 135.168MB/s transfers > da0: Command Queueing enabled > da0: 286070MB (585871964 512 byte sectors: 255H 32S/T 65535C) > panic: bootpc_init: no eligible interfaces > cpuid = 0 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > kdb_backtrace() at kdb_backtrace+0x37 > panic() at panic+0x187 > bootpc_init() at bootpc_init+0x1205 > mi_startup() at mi_startup+0x77 > btext() at btext+0x2c > KDB: enter: panic > [ thread pid 0 tid 100000 ] > Stopped at kdb_enter+0x3b: movq $0,0x976972(%rip) > db> > > Which is completely OK, because there are really no interfaces to boot > from. Note that there is no NMI either (maybe because it would happen > later in the initialization process). > Sadly, I can't boot from disk, but I assume it would work. Ok, I guess you're seeing similar issue that Sean reported. I'll let you when I have experimental patch.