2012/12/2 Juanjo Amor <[email protected]> > > Hello, > > I've configured a pfsense 2.0.1 64 bits in router-only mode, as a virtual > machine running in VMWare ESXi 5.0 with 4 emulated e1000 devices. > > Last night pfsense did a panic. I'm not sure the cause but I'm very > concerned because pfsense did not auto-rebooted after dumping crash > information. I had to reset the virtual machine. > > Before resetting, I found the console with these messages (I've copied > data by hand, sorry): > > --- interupt, rip = ..., rsp = ... --- > cpu_reset() at cpu_reset+... > db_command() at db_command+... > db_script_exec() at db_script_exec+... > kbd_trap() at db_trap+... > ... > calltrap() at calltrap+... > --- trap 0xc, rip= xxx, rsp= ... --- > _mtx_lock_sleep() ... > _sema_post() ... > ata_completed() ... > taskqueue_run() ... > intr_event_execute_handlers... > ithread_loop .. > fork_exit() > fork_trampoline() at ... > --- trap 0, rip=0, rsp = ..., rbp = 0 --- > Script command 'reset' returned error > db> > > > Do you know the cause which can fail the reset command in db? I've looked > for it in FreeBSD documentation but I cannot find it. > > On the other hand, I'd like to understand the possible cause for the > panic. Before the panic kernel dumped some information about acd0, but > since it had no time information I don't know if it's directly related. In > the meanwhile I decided to deactivate the virtual CD drive since it is not > required. > > The kernel message dumped were: > > <6>arp: 192.168.8.8 moved from 00:50:56:82:68:31 to 00:50:56:82:68:32 on > em1 > acd0: acd0: WARNING - PREVENT_ALLOW taskqueue timeout - completing request > directlyWARNING - PREVENT_ALLOW taskqueue timeout - completing request > directly > acd0: > acd0: WARNING - PREVENT_ALLOW freeing taskqueue zombie requestWARNING - > PREVENT_ALLOW freeing taskqueue zombie request > > Fatal trap 12: page fault while in kernel mode > ... > > > Many thanks in advance. > > Best regards, > > > Juan Jose Amor Iglesias // http://about.me/jjamor > jjamor -at- gmail.com // juanjo -at- dramor.net > > -------------------- Visit my Blog! --------------------- > The Boring Stories Written By DrAmor: http://dramor.net/blog/ > --------------------------------------------------------------- > > _______________________________________________ > List mailing list > [email protected] > http://lists.pfsense.org/mailman/listinfo/list > > Hi Juanjo,
i cannot help much. To less informations, maybe others can guess more out of that short piece of output. The "db>" prompt and db_trap ...bla .... is just debugger stuff. http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-online-ddb.html you got throwed into the debugger console so you had the chance to examine it further by commiting the command "trace" or more deeply inspecting variables, memory heap and so on. for me it looks like a timing issue. i had that seen before on ESXi and ESX Versions 4.xx just under heavy load. the load that caused this panic, was on Storage and CPU. The ESX/i didn't responded, the disc-controller-driver in the vm was waiting on an answer from the emulated disc and the controller while the driver caused an timeout and data couldn't get read/written from/to the VM's system disk. in your case, may be the virtual CD-Drive is connected to a physical one that got used by another VM at the same time? Just guessing. i solved that issue by switching the disc-controller ( not sure yet, was it LSI or buslogic) to the other emulated type and converted the virtual disk. May be a reinstall from a backup would been faster, but i didn't cared, i had to change more than one VM so i scriptet that. hth regards m. -- = = = http://michael-schuh.net/ = = = Projektmanagement - IT-Consulting - Professional Services IT Michael Schuh Postfach 10 21 52 66021 Saarbrücken phone: 0681/8319664 @: m i c h a e l . s c h u h @ g m a i l . c o m = = = Ust-ID: DE251072318 = = =
_______________________________________________ List mailing list [email protected] http://lists.pfsense.org/mailman/listinfo/list
