more panics from current (partII)

From: Tomi Vainio - Sun Finland (Tomi.Vainio_at_Sun.COM)
Date: 09/28/03

  • Next message: Antony T Curtis: "Re: UMASS: fatal trap while unplugging floppy drive" 
    Date: Sun, 28 Sep 2003 13:57:07 +0300
To: freebsd-current@freebsd.org

    After adding more disks to this system it dies continously. Last two
    traces look quite the same.

      Tomppa

    ---clipclip---
    login: kernel trap 19 with interrupts disabled
    NMI ... going to debugger
    kernel: type 19 trap, code=0
    Stopped at rtcintr+0x57: call rtcin
    db> trace
    rtcintr(0) at rtcintr+0x57
    Xfastintr8() at Xfastintr8+0x68
    --- interrupt, eip = 0xc037ed02, esp = 0xcd680cdc, ebp = 0xcd680cdc ---
    cpu_idle(73042444,890002c0,bde8241c,c7ffff80,10c2444) at cpu_idle+0x22
    idle_proc(0,cd680d48,c7000000,50082444,c70000df) at idle_proc+0x25
    fork_exit(c01ecd40,0,cd680d48) at fork_exit+0xb1
    fork_trampoline() at fork_trampoline+0x8
    --- trap 0x1, eip = 0, esp = 0xcd680d7c, ebp = 0 ---
    db>
    rtcintr(0) at rtcintr+0x57
    Xfastintr8() at Xfastintr8+0x68
    --- interrupt, eip = 0xc037ed02, esp = 0xcd680cdc, ebp = 0xcd680cdc ---
    db> panic
    panic: from debugger
    Debugger("panic")

    Fatal trap 3: breakpoint instruction fault while in kernel mode
    instruction pointer = 0x8:0xc0375b34
    stack pointer = 0x10:0xcd680a80
    frame pointer = 0x10:0xcd680a8c
    code segment = base 0x0, limit 0xfffff, type 0x1b
                            = DPL 0, pres 1, def32 1, gran 1
    processor eflags = IOPL = 0
    current process = 11 (idle)
    Stopped at rtcintr+0x57: call rtcin
    db>
    panic: from debugger
    Uptime: 7h17m58s
    Dumping 255 MB
     16 32 48 64 80 96 112 128 144 160 176 192 208 224 240
    Dump complete
    Shutting down ACPI
    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.
    Rebooting...
    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"

  • Next message: Antony T Curtis: "Re: UMASS: fatal trap while unplugging floppy drive"

    Relevant Pages

    • STOP MESSAGE - Possibly Causes
      ... Here is the diagnose of the dump file from the debugger: ... Copyright Microsoft Corporation. ... Loading Kernel Symbols ... This means a trap occurred in kernel mode, and it's a trap of a kind ...
      (microsoft.public.windowsxp.help_and_support)
    • Help With Crash Dump Analysis
      ... Here is a crash dump file I analyzed in the debugger does anyone have any ... Loading Kernel Symbols ... Use!analyze -v to get detailed debugging information. ... This means a trap occurred in kernel mode, and it's a trap of a kind ...
      (microsoft.public.windowsxp.general)
    • Fatal trap 12 under RELENG_5_1, anyone who can help?
      ... Fatal trap 12: page fault while in kernel mode ... Should I have given any other commands to the internal debugger to find ...
      (freebsd-current)
    • reproduceable kernel panic when trying to use tap0 interface (sparc64)
      ... im using 6_stable on sparc64 and get a 100% reproduceable kernel panic. ... panic: trap: memory address not aligned ... addr 0x1400726000-0x1400726003,0x1400728000-0x1400728003,0x140072a000-0x140072a003,0x140072c000-0x140072c003,0x140072f000-0x140072f003 on ebus0 ...
      (freebsd-stable)
    • Re: double panic, and whats apic_cmd? (kqemu crash...)
      ... I also have KDB_TRACE and KDB_UNATTENDED in the kernel config. ... GDB is free software, covered by the GNU General Public License, and you are ... Fatal trap 12: page fault while in kernel mode ...
      (freebsd-hackers)