Date: Mon, 08 May 2000 16:33:13 -0400 (EDT) From: John Baldwin <jhb@FreeBSD.org> To: Jonathan Perkin <sketchy@netcraft.com> Cc: freebsd-hackers@FreeBSD.org Subject: RE: Boot panics Message-ID: <200005082033.QAA03631@server.baldwin.cx> In-Reply-To: <20000508201112.B33357@netcraft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 08-May-00 Jonathan Perkin wrote: > Hey guys, got a strange one for you :) Well... you haven't overclocked or anything have you? > Running 4.0-STABLE on a P2-450 Asus P2B-D 512Mb with Cheetah ST39102LW's > connected via U2W Adaptec 7890 PCI. > > Connected up a single drive to ID-0 and installed 4-R, afterwhich cvsup'd to > -stable (as of 18:00 GMT today). Had no problems, happily rebooted new kernel > etc. > > Then shutdown machine and added a second HD at ID-1. Booted machine, boot0 > recognised new HD properly, and booted from ID-0. boot2 then failed to find > /kernel, so I shutdown and removed ID-1 HD. > > Switching on machine with only the original HD connected, boot0 came up fine, > but then promptly rebooted the machine. Odd I thought, so I let it reboot, > and this time after boot0 I got: > > BTX loader 1.00 BTX version is 1.01 > > int=0000000d err=00000000 efl=00010207 eip=00000000 > eax=ffffffff ebx=0001f288 ecx=00000000 edx=00000000 > esi=00000000 edi=00000000 ebp=00094fd8 esp=00094fa8 > cs=002b ds=0033 es=0033 fs=0033 gs=0033 ss=0033 > cs:eip=a3 d8 75 02 00 89 e0 05-a0 0f 00 00 a3 dc 75 02 > ss:esp=00 00 00 00 89 1a 00 00-02 00 e0 ab 44 0a 02 00 > System halted Ok, this ends up being: 00000000 A3D8750200 mov [0x275d8],eax 00000005 89E0 mov eax,esp 00000007 05600F0000 add eax,0xf60 0000000C A3DC750202 mov [0x20275dc],eax Well... since err=000, %ds is valid, and it's a mov instruction, it seems that the GPF (int=0d) could only be caused by exceeding the segment limit on %ds. However, the segment limit on selector 0x0030 is 4 gig, or all addressable memory, and the memory address 0x275d8 is well within that range. My guess is that you have some bad hardware, be it CPU, memory, or disk that results in the global descriptor table being corrupted when this instruction is executed. Your reports of other seemingly random failures during bootup also points to hardware. When you get a BTX fault like this, is it always the same exact fault, or does it vary? Errr, then again... %eip=00 is bad, as that might point to some stack corruption. However, the actual fault doesn't make any sense. Try playing around with the hardware some, swapping stuff in and out, etc. > So now whenever I boot, I either get that message (or similar), a "Boot error" > message, a "Read error" message, or an instant reboot. > > Hope some of this helps. If you need any more info, just holler. > > Cheers > -- > Jonathan Perkin <sketchy@netcraft.com> Voice: +44 (01225) 404422 > "Unix is simple, but it takes a genius to understand the simplicity." > System Administrator - Netcraft. Bath, UK. - http://www.netcraft.com/ -- John Baldwin <jhb@FreeBSD.org> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200005082033.QAA03631>