Date: Mon, 16 Nov 1998 21:16:34 +0200 (SAT) From: Robert Nordier <rnordier@nordier.com> To: elijah@xor.com (Eli Klein) Cc: current@FreeBSD.ORG Subject: Re: strage happenings with kern.flp/mfsroot.gz Message-ID: <199811161916.VAA03516@ceia.nordier.com> In-Reply-To: <Pine.SUN.4.05.9811160937020.3617-100000@xor.com> from Eli Klein at "Nov 16, 98 09:40:23 am"
next in thread | previous in thread | raw e-mail | index | archive | help
Eli Klein wrote: > jordan had committed some things for me to enable me to install onto a > 486sx25 laptop, but instead, this is what i got: > > Please insert MFS root floppy and press enter: > > - > int=0000000d err=003394d0 efl=00010286 eip=001e4017 > eax=001e4000 ebx=001c3b8b ecx=00000004 edx=0002784c > esi=001ce47e edi=0002767d ebp=00095964 esp=0009e928 > cs=0008 ds=0010 es=0010 fs=0010 gs=0010 ss=0010 > cs:eip=cf fe 08 2a b0 b7 6f 74-f8 6b dd 6e ea e2 d8 61 > ss:esp=c3 2a fa 9a d2 94 00 00-00 00 00 80 02 00 50 a0 > System halted > > I don't know if the assembler output will help at all, but I thought I'd > send it anyways.. again, i have a toshiba T3400C, a 486sx25. Although this is a BTX-generated register dump, the exception is actually happening a few bytes into the kernel startup code. Or what should be the kernel startup code: cs:eip isn't pointing at anything valid. BTX has been told to pass control to the kernel (the 0x94d2 on the stack is the return address of the BTX "exec" syscall) but I'd suspect the kernel just hasn't been loaded correctly. It looks as though the BTX client thinks the kernel entry point is 0x1e4000, but that's just a guess (eax may have been altered). Doubt that this helps much in itself, but that's what can be gotten from the register dump. Maybe Jordan, or someone else, has some ideas based on this. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199811161916.VAA03516>