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
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]
Fatal Trap 10: trace trap while in vm86 mode, trying to boot install CD after menu
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.. --Pete PS: pls also send email to thsi addr: pg at eth1 dot com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Opteron problem after recompile is ffs_mountroot: can't find rootvp
thx Kris i went over the kernel config file and it doesn't seem so, i successfully made another 3 kernels w/ more and more components in each, up to the point where the only items i did away with were just the NiC cards teh machine dowsn't have. In each case they all compile fine BUT they all fail on bootup w/ exact same message as the subject line above. I did some digging in the mail list archives and it seems this was a problem w/ the Sparc64 line early last spring. Was this resolved or is it now appearing in this amd64 ARCH that i'm using?? Is there another mail list i should be posting to specifically for the amd64? thx --- Kris Kennaway [EMAIL PROTECTED] wrote: On Tue, Oct 26, 2004 at 07:51:07AM -0700, Peter G wrote: . any suggestions? You removed too much from your kernel config file relative to GENERIC? Kris ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Opteron problem after recompile is ffs_mountroot: can't find rootvp
Generic amd64 kernel boots fine after recompile of 5.2.1 amd64 version on Opteron 146 single proc machine (2GHz) It doesn't mount the root file system the error is: ffs_mountroot: can't find rootvp The Geom list is blank any suggestions? PLS also email your responses to PG_AT_ETH1.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PAE, mem available to user?
Thank you for your response What i'd like to be able to do on this 5.2.1 machine is run a user job that may take up 1.5GB of mem, i'd like it to start swapping which it doesn't do, nor does it panic, nor does it lock up. It stays responsive. Taking what U said i recompiled the kernel as a non PAE build and included options maxusers 512 options MAXDSIZ=(1664*1024*1024) options DFLDSIZ=(1664*1024*1024) and i am now able to start the job and watch it go to about 1.2GB, actually 1.18GB, then either job stops or job coredumps, machine stays nice and responsive and stable. I have it configured w/ 2 large swap files on 2 diffrent spindles but the machine does not start swapping. The only error messages in the logs or dmesg is that this user job core dumped. What tunable parameters can i put into the next kernel build configuration to help me here? KVA_PAGES? setting maxusers to something else? I have a very small kernel requirement i want to maximize my user available space for this job..? Thanx again --P --- Kris Kennaway [EMAIL PROTECTED] wrote: PAE is for addressing 4GB of memory; since you only have about 1.5GB, that's not applicable. You'll need to include more details about your system and kernel configuration, including error messages showing what is going wrong. Kris ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
PAE, mem available to user?
hi all, read thru the archives, esp thru thread: PAE testing results ... from circa May 03. I am getting a diffrent problem on a uniProc machine. with 5.2.1 and a stock PAE build. machine is stable and does not crash, but the big mem user job we want to submit to it, all these jobs die when they start using about 400MB of mem, swap doesn't activate. the user submitted job just core dumps. With previous 4.5 FBSD machines with the following kernel options compiled in (before PAE days) on same machine w/same 1.5GB of physical mem and plenty of swap, we'd get 1.2GB of usable mem for user job and rest would be kernel space. Job would run but not satisfactory, thought modern PAE would be a better bet. The kernel options we had used w/ 4.5 back then were: options MAXDSIZ=(1664*1024*1024) options DFLDSIZ=(1664*1024*1024) current Dmesg is listed below; Thanx in advance and pls reply also to me as i can't subscribe to the list at this point. Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.2.1-RELEASE #0: Sat Mar 27 12:47:33 EST 2004 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/FB5PAE Preloaded elf kernel /boot/kernel/kernel at 0xc0545000. Timecounter i8254 frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) Processor (1208.75-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x642 Stepping = 2 Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR AMD Features=0xc044RSVD,AMIE,DSP,3DNow! real memory = 1610530816 (1535 MB) avail memory = 1559183360 (1486 MB) Pentium Pro MTRR support enabled acpi0: ASUS A7V133-C on motherboard pcibios: BIOS version 2.10 Using $PIR table, 9 entries at 0xc00f1750 acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0xe408-0xe40b on acpi0 acpi_cpu0: CPU on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib0: slot 4 INTD is routed to irq 4 pcib0: slot 10 INTA is routed to irq 10 pcib0: slot 12 INTA is routed to irq 11 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pcib0: slot 1 INTA is routed to irq 11 pcib1: slot 0 INTA is routed to irq 11 pci1: display, VGA at device 0.0 (no driver attached) isab0: PCI-ISA bridge at device 4.0 on pci0 isa0: ISA bus on isab0 atapci0: VIA 82C686B UDMA100 controller port 0xb800-0xb80f at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] pci0: serial bus, USB at device 4.3 (no driver attached) pci0: bridge, PCI-unknown at device 4.4 (no driver attached) fxp0: Intel 82557 Pro/100 Ethernet port 0x9400-0x941f mem 0xe300-0xe30f,0xe600-0xe6000fff irq 10 at device 10.0 on pci0 fxp0: Ethernet address 00:a0:c9:67:e6:7c miibus0: MII bus on fxp0 inphy0: i82555 10/100 media interface on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ahc0: Adaptec 2940 Ultra2 SCSI adapter (OEM) port 0x9000-0x90ff mem 0xe280-0xe2800fff irq 11 at device 12.0 on pci0 aic7890/91: Ultra2 Wide Channel A, SCSI Id=7, 32/253 SCBs fdc0: Enhanced floppy controller (i82077, NE72065 or clone) port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive on fdc0 drive 0 atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: failed to get data. psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface orm0: Option ROMs at iomem 0xd-0xd07ff,0xc-0xc7fff on isa0 pmtimer0 on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounter TSC frequency 1208752739 Hz quality 800 Timecounters tick every 10.000 msec acpi_cpu: throttling enabled, 16 steps (100% to 6.2%), currently 100.0% GEOM: create disk ad0 dp=0xc6f63160 ad0: 38166MB WDC WD400BB-00AUA1 [77545/16/63] at ata0-master UDMA100 ata1-master: DMA limited to UDMA33, non-ATA66 cable or device GEOM: create disk ad2 dp=0xc7110e60 ad2: 29198MB SAMSUNG SV3063H [59323/16/63] at ata1-master UDMA33 acd0: CDROM SAMSUNG SC-148 at ata1-slave PIO4 Waiting 5 seconds for SCSI devices to settle GEOM: create disk da0 dp=0xc6f62c50 sa0 at ahc0 bus 0 target 5 lun 0 sa0: EXABYTE EXB-82058VQANXR0 07T0 Removable Sequential Access SCSI-2 device sa0: 5.000MB/s transfers (5.000MHz, offset 11) da0 at ahc0 bus 0 target 4 lun 0 da0: FUJITSU M2512A 1314 Removable Optical SCSI-2 device da0: 5.000MB/s transfers (5.000MHz, offset 8) da0: Attempt to query device size failed: NOT READY, Medium not present (da0:ahc0:0:4:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0
