Re: Fatal Trap 10: trace trap while in vm86 mode, trying to boot install CD after menu
For completeness sakes of the archives my solution was: to put the following in the /boot/loader.conf it's the only way these machines will boot with FreeBSD given their Serverworks chipsets. hw.hasbrokenint12=1 hw.ata.ata_dma=0 If the previous is ommited after install (after the CDROM is removed, we used a USB CDROM to load them right on the racks) we'd get Fatal Trap 12 Previous exchange: Curiosity question All these blades have Serverworks chipset in them.. DO you recall if your gateways had that same chipset?? I am going to try when next i get a chance(at the loader prompt): set hw.hasbrokenint12=1 set hw.ata.ata_dma=0 because thsi exchange in the archives leads me to believe it's a chipset specific problem: http://groups.google.com/group/muc.lists.freebsd.stable/browse_frm/thread/bb3484c9f7a282/d7d619bf611e0f64?lnk=stq=serverworks+install+group% 3A*freebsd*rnum=5hl=en#d7d619bf611e0f64 On these blades i am trying to install fr a USB CD drive as the only options in the BiOS is boot fr USB Floppy, USB CD, internal HD.. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fatal Trap 10: trace trap while in vm86 mode, trying to boot install CD after menu
Peter G [EMAIL PROTECTED] writes: trying to install 6.1 on a bunch of blade servers, P4 3.06Ghz w/ 2GB RAM SEARCHED THRU ALL THE ARCHIVES AND MAIL LISTS for ANY similar happenings and there are NO valuable clues.. Tried installing Fbsd 6.1, 6.0 and even a hard drive that had 5.4 pre-installed same result always AFTER the boot menu, (picked ACPI disabled and no diff) Fatal Trap 10: trace trap while in vm86 mode They ran Linux just fine.. is there something about Hyperthreading or something that makes these hang?? i also tried to do this in the boot loader prompt after the boot menu w/ no better results: set hw.hasbrokenint12=1 any clues appreciated as to what i should lookit next.. What happens when you try safe mode? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fatal Trap 10: trace trap while in vm86 mode, trying to boot install CD after menu
Thanx for your prompt reply When i try safe mode or any mode... The same effect in ANY mode. i am about to try setting the following at the loader prompt from the boot menu set hw.ata.ata_dma=0 and seeing if thsi helps I do know also taht these blades have a Serverworks chipset and i looked at this exchange from the archives: http://groups.google.com/group/muc.lists.freebsd.stable/browse_frm/thread/bb3484c9f7a282/d7d619bf611e0f64?lnk=stq=serverworks+install+group%3A*freebsd*rnum=5hl=en#d7d619bf611e0f64 The folks in that exchange were able to solve their problems by eliminating their CD drives, I have a USB CDROM that i am attempting to load from when i get the Fatal Trap 10 message,(there is NO option to have a local CD drive here and the BiOS only offers booting fr a USB Floppy or USB CD Drive as THE only options other than fr a local HD inside the blade)... but i also get the same fatal trap error when i transplant a known working IDE HD w/ FBSD 5.4 into 1 of the blades and attempt to boot only from that lone hardrive, so i'm inclined to now look at thsi chipset to see if there is a chipset problem correlation workaround. There are 5 identical blade servers and they ALL act identically as reproducing thsi error. Thanx for your reply, any input is appreciated. -Peter --- Lowell Gilbert wrote: Peter G writes: trying to install 6.1 on a bunch of blade servers, P4 3.06Ghz w/ 2GB RAM SEARCHED THRU ALL THE ARCHIVES AND MAIL LISTS for ANY similar happenings and there are NO valuable clues.. Tried installing Fbsd 6.1, 6.0 and even a hard drive that had 5.4 pre-installed same result always AFTER the boot menu, (picked ACPI disabled and no diff) Fatal Trap 10: trace trap while in vm86 mode They ran Linux just fine.. is there something about Hyperthreading or something that makes these hang?? i also tried to do this in the boot loader prompt after the boot menu w/ no better results: set hw.hasbrokenint12=1 any clues appreciated as to what i should lookit next.. What happens when you try safe mode? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
