Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 24 Feb 2012 10:11:55 -0800
From:      YongHyeon PYUN <pyunyh@gmail.com>
To:        Attila Nagy <bra@fsn.hu>
Cc:        stable@freebsd.org
Subject:   Re: Fatal trap 19, Stopped at bge_init_locked+ and bge booting problems
Message-ID:  <20120224181155.GB18456@michelle.cdnetworks.com>
In-Reply-To: <4F45DF95.9050309@fsn.hu>
References:  <4F449E0B.2040909@fsn.hu> <20120223041516.GI6861@michelle.cdnetworks.com> <4F44FF2A.9050505@fsn.hu> <20120223204401.GB13815@michelle.cdnetworks.com> <4F45DF95.9050309@fsn.hu>

next in thread | previous in thread | raw e-mail | index | archive | help
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: <COMPAQ RAID 0  VOLUME OK> 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.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120224181155.GB18456>