Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 10 Jul 2002 10:02:32 -0400 (EDT)
From:      Andrew Gallatin <gallatin@cs.duke.edu>
To:        "Chris J. Mutter" <cjm@satanii.enemy.org>
Cc:        freebsd-alpha@FreeBSD.ORG
Subject:   Re: kernel trap on a AlphaServer 400
Message-ID:  <15660.15992.992752.254928@grasshopper.cs.duke.edu>
In-Reply-To: <200207080855.g688tqvt088710@satanii.enemy.org>
References:  <200207080855.g688tqvt088710@satanii.enemy.org>

next in thread | previous in thread | raw e-mail | index | archive | help

Chris J. Mutter writes:
 > Hello list,
 > 
 > i upgraded from 4.5-RELEASE-p2 to 4.6-RELEASE-p1 on my main
 > shellbox. 4.5 ran without any troubles for weeks. and now i got a
 > kernel trap after 4days uptime:
 > 
 > --snip--
 > fatal kernel trap:
 > 
 >     trap entry = 0x4 (unaligned access fault)
 >     a0         = 0xfffffe000177f17f
 >     a1         = 0x29
 >     a2         = 0x1
 >     pc         = 0xfffffc0000372e9c
 >     ra         = 0xfffffc0000368414
 >     curproc    = 0xfffffe000d87cc40
 >         pid = 387, comm = sendmail
 > 
 > panic: trap
 > 
 > syncing disks... 10 
 > done
 > Uptime: 4d10h48m38s
 > Automatic reboot in 15 seconds - press a key on the console to abort
 > Rebooting...
 > Copyright (c) 1992-2002 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 4.6-RELEASE-p1 #0: Tue Jul  2 12:00:48 CEST 2002
 >     root@satanii.enemy.org:/usr/obj/usr/src/sys/S2
 > AlphaStation 200/400 ("Avanti")
 > AlphaServer 400 4/60, 166MHz
 > 8192 byte page size, 1 processor.
 > CPU: EV4 (21064) major=2 minor=0
 > OSF PAL rev: 0x100000002012e
 > --snip--
 > 
 > anything i could do against it? (i have no debugging options in the
 > kernel). nothing changed on the hardware side. i had to upgrade because
 > of the latest libc security changes (resolver bug).

For a full stack trace, add ddb to your kernel (see i386/conf/LINT).
For a stack trace with gdb after the crash, you can enable crashdumps.

At the very least, run configure with -g, and build a kernel with
symbols.  The run gdb on that kernel and do list *faulting_address.
Eg, list *0xfffffc0000372e9c

Drew

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15660.15992.992752.254928>