From owner-freebsd-alpha Wed May 15 19:29:17 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from nemesis.fortean.com (nemesis.fortean.com [209.42.194.41]) by hub.freebsd.org (Postfix) with ESMTP id 1BB9A37B400 for ; Wed, 15 May 2002 19:29:14 -0700 (PDT) Received: from nemesis.fortean.com. (nemesis.fortean.com. [209.42.194.41]) by nemesis.fortean.com (8.12.3/8.12.2) with ESMTP id g4G2SbvR030088; Wed, 15 May 2002 22:28:37 -0400 (EDT) (envelope-from rbud@fortean.com) Date: Wed, 15 May 2002 22:28:37 -0400 (EDT) From: Rich Bud Reply-To: Rich Bud To: Andrew Gallatin Cc: freebsd-alpha@freebsd.org Subject: Re: natd sig 10 under stable In-Reply-To: <15586.64342.316609.71281@grasshopper.cs.duke.edu> Message-ID: <20020515221034.S30036-100000@nemesis.fortean.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > Please apply this to your system (cd /usr/src/sys; patch < thepatch), > rebuild your kernel & reboot to see if your natd problem is fixed. That seems to fix the crash, thanks. To answer your earlier 2 emails... yes, i have CPUTYPE=ev56 set in /etc/make.conf, and ldwu seems to be the winner, if i'm interpreting this correctly: Prepatch: pid 2704 (natd): unaligned access: va=0x11feb911 pc=0x120008994 ra=0x120008a04 op=0xc Postpatch: pid 384 (natd): unaligned access: va=0x11feb921 pc=0x120008994 ra=0x120008a04 op=ldwu Rich PS: as a side note, do you know why 'x/i' in gdb does not match the op= in the unaligned access line? I get this, pre and post patch: (gdb) x/i 0x120008994 0x120008994 : ldq t12,-30184(gp) If this isn't a simple answer, don't concern yourself; i was just curious. ;) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message