lost with booting

Matthew Dillon dillon at apollo.backplane.com
Wed Sep 8 11:15:02 PDT 2004


:-On [20040908 11:02], Simon 'corecode' Schubert (corecode at xxxxxxxxxxxx) wrote:
:>okay. this means we should definitely break after a BTX error and *not* 
:>somehow return to business (I've seen a iret somewhere). maybe *then* 
:>we can track the issue.
:
:*nod*
:
:Agreed.
:
:>somehow it seem that *either* esp/ss gets shifted to an area that is 
:>full of 0xff *or* something overflows and kills the whole stack. Or am 
:>I on the wrong track?
:
:I need to read the code, but I see it going to the - stage at least.  Just
:need to see where each part and section are before I can say if you're close
:or not.
:
:-- 
:Jeroen Ruigrok van der Werven <asmodai(at)wxs.nl> / asmodai / kita no mono

    Ok, there are some other things that can be tried.

    The boot1/boot2 code can be relocated, at least within its 64KB segment
    space.

    You can change the location(s) by setting the BOOT_NEWBOOTLOADER define
    in /usr/src/sys/boot/i386/bootasm.h.  See the top of that file.  You
    can then rebuild the boot code via (from /usr/src/sys/boot):

    make obj; make clean; make; make install

    And then reinstall boot1/boot2 using disklabel -B, then reboot and see
    if it works any better.

					-Matt
					Matthew Dillon 
					<dillon at xxxxxxxxxxxxx>





More information about the Bugs mailing list