Date: Fri, 7 Aug 2015 17:39:53 -0400 (EDT) From: Walter Cramer <wfc@mintsol.com> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-fs@freebsd.org Subject: Re: BTX halted Message-ID: <20150807172126.H12135@mulder.mintsol.com> In-Reply-To: <2241493.vMCzZXQH3f@ralph.baldwin.cx> References: <1429520064.12915.56.camel@data-b104.adm.slu.se> <2241493.vMCzZXQH3f@ralph.baldwin.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
FWIW, I've gotten very similar errors with SuperMicro H8SMi-2 motherboards= =20 (NOT on their FreeBSD Compatible list) with a 10.1-Release & RootOnZFS=20 test HD. Switching the BIOS settings from "optimal" to "failsafe" fixes=20 the problem; setting ACPI to v3.0 brings it back. I have an idle H2SMi-2 test system, but not much free time in the next=20 week. Walter Cramer On Fri, 7 Aug 2015, John Baldwin wrote: > On Monday, April 20, 2015 08:54:24 AM Karli Sj=F6berg wrote: >> Hey all! >> >> I was just upgrading one of our storage's to 10-STABLE as per Bug >> 191348[*] when something strange happened after writing new boot code >> and rebooting: >> >> BTX loader 1.00 BTX version is 1.02 >> Consoles: internal video/keyboard >> BIOS drive C: is disk8 >> BIOS drive D: is disk9 >> >> int=3D00000000 err=3D00000000 efl=3D00010246 eip=3D00037d34 >> eax=3D00000001 ebx=3D00000000 ecx=3D00000000 edx=3D00000000 >> esi=3D00000000 edi=3D00000000 ebp=3D0008f600 esp=3D0008f598 >> cs=3D002b ds=3D0033 es=3D0033 fs=3D0033 gs=3D0033 ss=3D0033 >> cs:eip=3Df7 35 d0 f4 03 00 85 f6-74 05 89 3e 89 5e 04 89 >> c2 e9 cc 00 00 00 66 c7-45 ea 00 00 89 d8 c1 e8 >> ss:esp=3D00 00 20 00 00 00 00 00-00 00 00 00 00 00 00 00 >> 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 >> BTX halted >> >> Never happened to me before. I then booted with a 10.1-RELEASE CD and >> wrote bootcode from that, same problem. 9.3; same there... >> >> Any pointers? > > Hmm, looks like a divide-by-zero fault: > > 00000000 F735D0F40300 div dword [dword 0x3f4d0] > 00000006 85F6 test esi,esi > 00000008 7405 jz 0xf > 0000000A 893E mov [esi],edi > 0000000C 895E04 mov [esi+0x4],ebx > 0000000F 89C2 mov edx,eax > 00000011 E9CC000000 jmp dword 0xe2 > 00000016 66C745EA0000 mov word [ebp-0x16],0x0 > 0000001C 89D8 mov eax,ebx > > Are you using ZFS or UFS? Also, do you have the world build from when yo= u > did this? If so we can use gdb on the 'loader.sym' file to map the fault= ing > instruction (eip above) to a source line. > > --=20 > John Baldwin > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150807172126.H12135>