Re: 5.4pre panic

From: Kris Kennaway (kris_at_obsecurity.org)
Date: 03/30/05

  • Next message: Ulrich Spoerlein: "boot0: To beep or not to beep?" 
    Date: Wed, 30 Mar 2005 06:27:56 -0800
To: Rene Ladan <r.c.ladan@student.tue.nl>

    On Wed, Mar 30, 2005 at 04:17:08PM +0200, Rene Ladan wrote:
    > On Wed, Mar 30, 2005 at 05:51:04AM -0800, Kris Kennaway wrote:
    > > On Wed, Mar 30, 2005 at 12:11:23PM +0200, Rene Ladan wrote:
    > > > Got this panic with auto-reboot (no dump :( ), saved from dmesg on
    > > > 5.4pre 2003-05-29 09:49 UTC
    > > >
    > > > processor eflags = IOPL = 0
    > > > current process = 29 (swi1: net)
    > > > trap number = 3
    > > > panic: breakpoint instruction fault
    > >
    > > I'd have expected this panic to be the result of setting a breakpoint,
    > > i.e. requesting the kernel to panic at this location. Are you
    > > absolutely certain this is not the case?
    > I did not set a breakpoint, maybe some application was doing it for me.
    > I was working in X at the moment.
    >
    > > If so, you should try to use
    > > DDB to obtain a traceback to find out what it was doing.
    > I have DDB/KDB in my kernelconfig, but auto-reboot without dump doesn't
    > help much, does it?

    The point is to disable "auto-reboot" (I assume you mean
    DDB_UNATTENDED?) and obtain the traceback manually from the ddb prompt
    when it panics.

    Kris

  • Next message: Ulrich Spoerlein: "boot0: To beep or not to beep?"

    Relevant Pages