ifconfig triggers kernel trap on boot

Stefan Bethke stb at lassitu.de
Fri May 22 22:53:13 UTC 2009

Am 22.05.2009 um 21:34 schrieb Attilio Rao:

> Did this happen inside VMware or with normal running?

I encountered this originally on my main server:

FreeBSD 8.0-CURRENT #4: Sat Mar 28 12:46:14 CET 2009
     root at diesel.lassitu.de:/usr/obj/usr/src/sys/DIESEL
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Core(TM)2 Duo CPU     E7300  @ 2.66GHz (2666.77-MHz K8- 
class CPU)
   Origin = "GenuineIntel"  Id = 0x10676  Stepping = 6
   AMD Features=0x20100800<SYSCALL,NX,LM>
   AMD Features2=0x1<LAHF>
   TSC: P-state invariant
   Cores per package: 2
usable memory = 4177514496 (3983 MB)
avail memory  = 4009562112 (3823 MB)
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
  cpu0 (BSP): APIC ID:  0
  cpu1 (AP): APIC ID:  1

This is an Intel DG45FC board.

The same kernel from May 21 also crashes in a VMware instance.  Using  
the same kernel config to create a kernel on the VMware instance also  
panics.  GENERIC from the same sources does not crash in a VMware  
instance; I haven't tried on real hardware yet.  Configs and the  
kernels are at http://www.lassitu.de/freebsd/ifconfig-panic/

I'm currently trying to take out things from the DIESEL config until  
it stops panicking or I end up with stock GENERIC, using my VMware  


Stefan Bethke <stb at lassitu.de>   Fon +49 151 14070811

More information about the freebsd-current mailing list