Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 25 Jul 2005 22:56:30 +0100 (BST)
From:      Gavin Atkinson <gavin.atkinson@ury.york.ac.uk>
To:        Norberto Meijome <numard@meijome.net>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: Panic on 5.4, 1 second uptime
Message-ID:  <20050725225132.F99788@ury.york.ac.uk>
In-Reply-To: <42E45D20.8010107@meijome.net>
References:  <42E45D20.8010107@meijome.net>

next in thread | previous in thread | raw e-mail | index | archive | help

On Mon, 25 Jul 2005, Norberto Meijome wrote:

> ( This is an exact copy of my post to -questions)
> Hi all,
> I am trying to install 5.4 on a box that's been running Linux. It's a 2 year 
> old 'Snap Appliance 4500' ( 
> http://www.snapappliance.com/page.cfm?name=4500Main&nav=4500 ), with 4 x 120 
> GB EIDE, P4, 512 Mb.
>
> As soon as I try to load the kernel I get :
> --- (copied by hand )
> Fatal trap 10: trace trap while in vm86 mode
> instruction pointer = 0xf000:0xf842
> stack pointer        = 0x0:0xff8
> frame pointer       = 0x0:0x0
> code segment      = base 0x330026, limit 0x1, type 0x9
>                         = DPL 3, pres 1 def32 0, fram 0
> processor eflags  = interrupt enabled, vm86, IOPL=0
> current process   = 0 ()
> trap number        = 10
> panic : trace trap
> uptime : 1 s
> -------------
>
> Every time, the same pointers / segments. This happens right after the kernel 
> memory addresses (data? segment? pls excuse my ignorance) show after pressing 
> an option in the boot menu.

Can you boot in verbose mode and try and get a few of the lines before the 
lines you quoted?  Knowing roughly where in the boot process this happens 
will probably greatly help.

Gavin



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