Re: panic after 'ifconfig gif0 destroy'

From: Ryan Sommers (ryans_at_gamersimpact.com)
Date: 09/30/04

  • Next message: Barney Wolff: "Re: wifi on 5.3, sort of OT" 
    Date: Thu, 30 Sep 2004 14:03:26 -0600 (MDT)
To: "J.R. Oldroyd" <fbsd@opal.com>

    > 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: Barney Wolff: "Re: wifi on 5.3, sort of OT"

    Relevant Pages

    • Re: Logging a kernel panic (remotely)
      ... panics from time to time. ... Unfortunately we have no remote console. ... I'll try and get a serial console hooked up at some point but I may not be ... The problem as I understand it is that when a kernel ...
      (Debian-User)
    • kdump and crash(8) [more Re: tracking down a lockup problem]
      ... I wrote about how to use the console (including serial ... console) to view kernel OOPS, BUGs, and PANICs. ... There is a howto for using kdump: ... when the kernel panics, kdump takes over, dumps the system ...
      (Fedora)
    • Re: System Freezes When MBufClust Usages Rises
      ... When it freezes, the number of Kbytes allocated to network is roughly 160,000. ... Are there any other parameters that would help us to allocate more memory to the kernel networking? ... Remember that if you run out of clusters, you may experience network deadlocks that prevent SSH sessions from operating, so direct console access may be required to effectively monitor the system when in an extreme state of low memory in the network stack. ... My advice would be to use a serial console anyway, if possible, when debugging, as it means you can use a second machine to copy and paste DDB output into a file to e-mail out later. ...
      (freebsd-net)
    • Re: Logging a kernel panic (remotely)
      ... panics from time to time. ... Is there a way to get the kernel to either to to write the panic to disk or to log it remotely? ... I'll try and get a serial console hooked up at some point but I may not be able to get on site for a few weeks. ...
      (Debian-User)
    • Re: Random panics with 5.3-REL, SMP
      ... "Random panics" is a little vague as a starting point, ... explicit call to panicby code that has detected a failure of a kernel ... A stack trace can be generated using the "trace" ... - In terms of debugging information, it would be very useful if you could ...
      (freebsd-current)