As a report, I've tried it. I got a freshly built proto area from my machine and copied it (with tar) to an empty ufs slice of my root disk. Then I configured grub to boot off this slice. The result: it gets into a loop printing something like Nested trap, calling reset() Nested trap, calling reset() Nested trap, calling reset() Nested trap, calling reset() Nested trap, calling reset() Nested trap, calling reset() Nested trap, calling reset() Nested trap, calling reset() (and so on) until it reboots. I cannot even boot into kmdb. The behaviour is just the same if I try to boot with -kd. I have found that this message comes from function bop_trap at /onnv/onnv-gate/usr/src/uts/i86pc/os/fakebop.c:1106 but I couldn't quite figure out why it enters bop_trap or why it loops. I also found that bop_trap is called from function bop_trap_handler at both /onnv/onnv-gate/usr/src/uts/i86pc/ml/locore.s:1403 (amd64) and /onnv/onnv-gate/usr/src/uts/i86pc/ml/locore.s:1436 (i386 --> this is my call). bop_trap_handler seems to get registered as some kind of interrupt handler in function bop_idt_init at /onnv/onnv-gate/usr/src/uts/i86pc/os/fakebop.c:1146. This is all I386-specific stuff and I feel pretty much lost. Is there anyone who wants to explain to me what is happening and why my boot loops in this trap handler and reboots? (Perhaps I can gain some insight on the boot process with this...)
Thanks, Douglas This message posted from opensolaris.org _______________________________________________ opensolaris-code mailing list opensolaris-code@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
