Re: panic after 'ifconfig gif0 destroy'

From: J.R. Oldroyd (fbsd_at_opal.com)
Date: 09/30/04

  • Next message: Kris Kennaway: "Re: panic after 'ifconfig gif0 destroy'" 
    Date: Thu, 30 Sep 2004 17:14:19 -0400
To: Ryan Sommers <ryans@gamersimpact.com>

    Here you go:

    # ifconfig gif0 destroy
    [thread 100166]
    Stopped at idestroy_dev+0x9e: cmpl $0,0x3c(%esi)
    db> trace
    idestroy_dev(c3b88b00) at idestroy_dev+0x9e
    idestroy_dev(c3be1700,f0e6cb84,c0671ef4,c3be1700,c35a7800) at idestroy_dev+0x68
    destroy_dev(c35a1700,c35a7800,0,c080a1b8,d8) at destroy_dev+0x10
    if_detach(c35a7800,c35a7800,c35a7800,c0872480,f0e6cbbc) at if_detatch+0x274
    gif_destroy(c35a7800,c087b660,0,c0814dca,db) at gif_destroy+0x80
    gif_clone_destroy(c35a7800,c08724b0,c0872480,f0e6cbf0,c0674076) at gif_clone_destroy+0x67
    ifc_simple_destroy(c0872480,c35a7800,2d,80206979,0) at ifc_simple_destroy+0x1e
    if_clone_destroy(f0e6cc60,f0e6cc14,c0631dee,f0e6cc60,f0e6cc60) at if_clone_destroy+0xf2
    ifioctl(c4285a20,80206979,f0e6cc60,c4274900,0) at ifioctl+0x88
    soo_ioctl(c39f7e58,80206979,f0e6cc60,c3bd2e80,c4274900) at soo_ioctl+0x2b1
    ioctl(c4274900,f0e6cd14,3,7,286) at ioctl+0x3e0
    syscall(2f,2f,2f,1,bfbfe9c0) at syscall+0x213
    Xint0x80_syscall() at Xint0x80_syscall+0x1f
    --- syscall (54, FreeBSD ELF32, ioctl), eip = 0x280cc10b, esp = 0xbfbfe84c, ebp = 0xbfbfe868 ---
    db>

    On Sep 30, 14:03, Ryan Sommers wrote:
    >
    > > After the panic message, the system stops dead. No traceback,
    > > no addresses, nothing more.
    > >
    > > -jr
    >
    > Can you recompile a debugging kernel with DDB support? When the kernel
    > panics it will drop the console into the DDB debugger. Do a 'trace' and
    > then add that to an email.
    >
    > Note: If you can hook it up to a serial console you can just copy&paste
    > the output instead of hand copying it.
    >
    > >
    > >
    > > On Sep 30, 11:58, Kris Kennaway wrote:
    > >> On Thu, Sep 30, 2004 at 02:47:46PM -0400, J.R. Oldroyd wrote:
    > >> > The command:
    > >> > # ifconfig gif0 destroy
    > >> > panic: page fault
    > >> >
    > >> > isn't really ideal behavior.
    > >>
    > >> Nor is this really an ideal bug report ;-)
    > >>
    > >> You need to post a debugging traceback of the panic, or at the very
    > >> least look up the PC address in your kernel with addr2line.
    > >>
    > >> Kris
    > >
    > > _______________________________________________
    > > 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"
    > >
    >
    >
    > --
    > Ryan Sommers
    > ryans@gamersimpact.com
    _______________________________________________
    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: Kris Kennaway: "Re: panic after 'ifconfig gif0 destroy'"

    Relevant Pages

    • Re: odd panics on -current recently
      ... On Sat, 18 Jun 2005, Wesley Morgan wrote: ... Enabled dumps and this is the best trace I can get. ... You didn't post the panic message, which is necessary to determine why the ...
      (freebsd-current)
    • PANIC, maybe mdconfig related
      ... my machine just panicked while I was doing some mdconfig file ... backed vnode things. ... Unfortunately I don't have the panic message, just a trace. ...
      (freebsd-current)
    • SMP kernel panic with traceback
      ... I'm getting crashes when trying to debug mozilla (under KSE). ... The panic message is "panic: ... with interrupts already disabled". ... Attached is the trace. ...
      (freebsd-current)
    • PANIC, maybe mdconfig related
      ... my machine just panicked while I was doing some mdconfig file ... backed vnode things. ... Unfortunately I don't have the panic message, just a trace. ...
      (freebsd-stable)