fatal trap 12 in kernel mode

From: Dave (dmehler26_at_woh.rr.com)
Date: 10/25/05

  • Next message: David Kirchner: "i386/55603, i386/59959, kern/75850, fixed in 6.0?"
    To: <freebsd-questions@freebsd.org>
    Date: Tue, 25 Oct 2005 14:18:10 -0400
    
    

    Hello,
    I'm trying to do a 5.4-release install on an older box, it's an AT
    motherboard, and i hope that's not my problem. I'm getting the below error
    and would appreciate any help.
    Thanks.
    Dave.

    Insert boot floppy and press Enter
    /acpi.ko text=0x414fc data=0x1dc4+0x112c syms=[0x4+0x7670+0x4+0x9d05]
    can't open '/boot/beastie.4th': inappropriate file type or format

    /
    Hit [Enter] to boot immediately, or any other key for command prompt.
    Booting [/kernel]...
    Copyright (c) 1992-2005 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.4-RELEASE #0: Sun May 8 10:21:06 UTC 2005
        root@harlow.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC
    Timecounter "i8254" frequency 1193182 Hz quality 0
    CPU: AMD-K6(tm) 3D processor (450.17-MHz 586-class CPU)
      Origin = "AuthenticAMD" Id = 0x58c Stepping = 12
      Features=0x8021bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8,PGE,MMX>
      AMD Features=0x80000800<SYSCALL,3DNow!>
    real memory = 268435456 (256 MB)
    avail memory = 248946688 (237 MB)
    K6-family MTRR support enabled (2 registers)
        ACPI-0159: *** Error: AcpiLoadTables: Could not get RSDP,
    AE_NO_ACPI_TABLES
        ACPI-0213: *** Error: AcpiLoadTables: Could not load tables:
    AE_NO_ACPI_TABL
        ACPI-0213: *** Error: AcpiLoadTables: Could not load tables:
    AE_NO_ACPI_TABLES
    ACPI: table load failed: AE_NO_ACPI_TABLES
    npx0: <math processor> on motherboard
    npx0: INT 16 interface
    cpu0 on motherboard
    pcib0: <VIA 82C598MVP (Apollo MVP3) host bridge> pcibus 0 on motherboard
    pir0: <PCI Interrupt Routing Table: 4 Entries> on motherboard
    pci0: <PCI bus> on pcib0
    agp0: <VIA 82C598 (Apollo MVP3) host to PCI bridge> mem
    0xe0000000-0xe3ffffff at
    agp0: <VIA 82C598 (Apollo MVP3) host to PCI bridge> mem
    0xe0000000-0xe3ffffff at device 0.0 on pci0
    pcib1: <PCI-PCI bridge> at device 1.0 on pci0
    pci1: <PCI bus> on pcib1
    isab0: <PCI-ISA bridge> at device 7.0 on pci0
    isa0: <ISA bus> on isab0
    atapci0: <VIA 82C586B UDMA33 controller> port
    0xe000-0xe00f,0x376,0x170-0x177,0x
    atapci0: <VIA 82C586B UDMA33 controller> port
    0xe000-0xe00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0
    ata0: channel #0 on atapci0
    ata1: channel #1 on atapci0
    rl0: <RealTek 8139 10/100BaseTX> port 0xe800-0xe8ff mem
    0xe4000000-0xe40000ff ir
    rl0: <RealTek 8139 10/100BaseTX> port 0xe800-0xe8ff mem
    0xe4000000-0xe40000ff irq 10 at device 17.0 on pci0
    miibus0: <MII bus> on rl0
    rlphy0: <RealTek internal media interface> on miibus0
    rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
    rl0: Ethernet address: 00:08:54:00:f3:3b
    ohci0: <NEC uPD 9210 USB controller> mem 0xe4001000-0xe4001fff irq 9 at
    device 1
    ohci0: <NEC uPD 9210 USB controller> mem 0xe4001000-0xe4001fff irq 9 at
    device 18.0 on pci0
    usb0: OHCI version 1.0
    usb0: <NEC uPD 9210 USB controller> on ohci0
    usb0: USB revision 1.0
    uhub0: NEC OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
    uhub0: 3 ports with 3 removable, self powered
    ohci1: <NEC uPD 9210 USB controller> mem 0xe4002000-0xe4002fff irq 9 at
    device 1
    ohci1: <NEC uPD 9210 USB controller> mem 0xe4002000-0xe4002fff irq 9 at
    device 18.1 on pci0
    usb1: OHCI version 1.0
    usb1: <NEC uPD 9210 USB controller> on ohci1
    usb1: USB revision 1.0
    uhub1: NEC OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
    uhub1: 2 ports with 2 removable, self powered
    pci0: <serial bus, USB> at device 18.2 (no driver attached)
    orm0: <ISA Option ROM> at iomem 0xc0000-0xc7fff on isa0
    pmtimer0 on isa0
    atkbdc0: <Keyboard controller (i8042)> at port 0x64,0x60 on isa0
    atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0
    kbd0 at atkbd0
    fdc0: <Enhanced floppy controller> at port 0x3f0-0x3f5 irq 6 drq 2 on isa0
    fd0: <1440-KB 3.5" drive> on fdc0 drive 0
    sc0: <System console> at flags 0x100 on isa0
    sc0: VGA <16 virtual consoles, flags=0x100>
    sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
    sio0: type 16550A, console
    sio1: configured irq 3 not in bitmap of probed irqs 0
    sio1: port may not be enabled
    vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
    unknown: <PNP0303> can't assign resources (port)
    unknown: <PNP0501> can't assign resources (port)
    unknown: <PNP0700> can't assign resources (port)
    Timecounter "TSC" frequency 450165168 Hz quality 800
    Timecounters tick every 10.000 msec
    md0: Preloaded image </mfsroot> 4423680 bytes at 0xc0a34270
    ad0: 9541MB <WDC WD100EB-00BHF0/15.15M15> [19386/16/63] at ata0-master
    UDMA33
    acd0: CDROM <ATAPI CDROM/V1.50> at ata1-slave PIO4

    Fatal trap 12: page fault while in kernel mode
    fault virtual address = 0x1
    fault code = supervisor write, page not present
    instruction pointer = 0x8:0xc04b4e34
    stack pointer = 0x10:0xcbf37c5c
    frame pointer = 0x10:0xcbf37c64
    code segment = base 0x0, limit 0xfffff, type 0x1b
                            = DPL 0, pres 1, def32 1, gran 1
    processor eflags = interrupt enabled, resume, IOPL = 0
    current process = 4 (g_down)
    trap number = 12
    panic: page fault
    Uptime: 3s
    Cannot dump. No dump device defined.
    Automatic reboot in 15 seconds - press a key on the console to abort
    kernel trap 12 with interrupts disabled

    Fatal trap 12: page fault while in kernel mode
    fault virtual address = 0x0
    fault code = supervisor write, page not present
    instruction pointer = 0x8:0xc05ebbcd
    stack pointer = 0x10:0xcbf37a60
    frame pointer = 0x10:0xcbf37a6c
    code segment = base 0x0, limit 0xfffff, type 0x1b
                            = DPL 0, pres 1, def32 1, gran 1
    processor eflags = resume, IOPL = 0
    current process = 4 (g_down)
    trap number = 12
    panic: page fault
    Uptime: 5s
    Cannot dump. No dump device defined.
    Automatic reboot in 15 seconds - press a key on the console to abort
    --> Press a key on the console to reboot,
    --> or switch off the system now.

    _______________________________________________
    freebsd-questions@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-questions
    To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"


  • Next message: David Kirchner: "i386/55603, i386/59959, kern/75850, fixed in 6.0?"

    Relevant Pages

    • panic: APIC: Previous IPI is stuck
      ... pcibus 0 on motherboard ... <Parallel port bus> on ppc0 ... GEOM_MIRROR: Device mirror0: provider da0 detected. ... Disk da1 attached to usr2. ...
      (freebsd-stable)
    • Newest Stack-180 CP/M system with motherboard option and networking
      ... CPU and includes 1 meg of ram and one serial port for terminal I/O The ... GIDE board has two IDE ports called Primary and Secondary which allow ... It is a ATX type motherboard that these ... and another IDE interface. ...
      (comp.os.cpm)
    • 5.3-RELEASE: SMP: system clock has died
      ... I have an ASUS P2B-DS motherboard with dual P2 400MHz CPU's. ... <Parallel port bus> on ppc0 ... unknown: can't assign resources ...
      (freebsd-stable)
    • Re: VIA IDE controller not detected on RELENG_6
      ... indicates strongly that what you have is an Asus motherboard with an VIA ... your system then the PATA controller should be recognized correctly. ... atapci0: port ... 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 15.1 on pci0 ...
      (freebsd-stable)
    • Need help troubleshooting a Compaq Presario SR1365CL (ASUS K8S-LA)
      ... I'm trying to fix a Compaq Presario SR1365CL. ... somehow decided that the hard drive was at fault. ... BIOS can be entered and changed and it does recognize the hard drive. ... either the motherboard or BIOS was at fault. ...
      (sci.electronics.repair)