Fatal trap 19, Stopped at bge_init_locked+ and bge booting problems

Attila Nagy bra at fsn.hu
Thu Feb 23 06:41:29 UTC 2012

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)

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.

More information about the freebsd-stable mailing list