Date: Fri, 15 Apr 2016 15:02:01 +0100 From: "Paul Wootton" <paulw@fisheyehq.com> To: <Freebsd-current@freebsd.org> Cc: "'Konstantin Belousov'" <kostikbel@gmail.com> Subject: RE: Kernel trap when booting inside VirtualBox Message-ID: <1f6801d1971f$62de2100$289a6300$@com> In-Reply-To: <000b01d19506$cb7d8b80$6278a280$@com> References: <17ea940319f36a803594bd00940efe4f@fisheyehq.com> <20160412075534.GC18263@kib.kiev.ua> <000b01d19506$cb7d8b80$6278a280$@com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Apr 12, 2016 at 11:01PM, Paul Wootton wrote: >On Tue, Apr 12, 2016 at 02:02PM, Paul Wootton wrote: > >With the help of Konstantin, I have got a proper disassembly. > >I have recompiled a few times so my new panic is >instruction pointer = 0x20:0xffffffff80fed2d9 >stack pointer = 0x28:0xffffffff824d89c0 >frame pointer = 0x28:0xffffffff824d8a40 >code segment = base 0x0, Limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 >Processor eflags = resume, IOPL = 0 >Current process = 0 (swapper) >[ thread pid 0 tid 100000 ] >Stopped at native_lapic_setup+0x99: lesl %edx,%esp > >and a disassembly gives >0xffffffff80fed2d9 <native_lapic_setup+153>: (bad) 0x99 == 153 > >Now to figure out why I am making bad binaries. >Ive not seen any issues yet with the world, so its not as if every >binary I >make is bad I have found that having CPUTYPE?=native in /etc/make.conf was my issue. Commenting that line out (the only other line I have is KERNCONF) and now I can build a good kernel --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1f6801d1971f$62de2100$289a6300$>