From owner-freebsd-alpha Wed May 15 14:46:55 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 3123837B407 for ; Wed, 15 May 2002 14:46:49 -0700 (PDT) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id RAA18140; Wed, 15 May 2002 17:46:48 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g4FLkIl35153; Wed, 15 May 2002 17:46:18 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15586.55082.170680.378288@grasshopper.cs.duke.edu> Date: Wed, 15 May 2002 17:46:18 -0400 (EDT) To: Rich Bud Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: natd sig 10 under stable In-Reply-To: <20020515160407.T28044-100000@nemesis.fortean.com> References: <20020515160407.T28044-100000@nemesis.fortean.com> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid 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 Rich Bud writes: > BTW, Craig Burgess posted about a sig 10 in natd back in february under > different conditions. I didn't see any replies, so i'm guessing this is > the same problem... Probably, but this is much more useful information that Craig was ever able to supply. With your information, it may be possible to diagnose & fix the problem. > Program received signal SIGBUS, Bus error. > 0x120008614 in AliasHandleQuestion (count=1, q=0x11feb911, pmax=0x11feb926 "", nbtarg=0x11feb838) at /usr/src/lib/libalias/alias_nbt.c:290 > 290 switch ( ntohs(q->type) ) { > (gdb) ptype q > type = struct { > u_short type; > u_short class; > } * > q = (NBTNsQuestion *) 0x11feb911, q->class = 1, q->type = 0 > This address is unaligned. Is one of machdep.unaligned_sigbus == 1, machdep.unaligned_fix == 0 true? (or the uac equivalent) If not, perhaps the unaligned fixup handler needs to be enhanced to handle a new sort of instruction. Can you disassemble the code at the faulting PC & see what instruction generated the access, please? (or enable unaligned printing via uac -p in the shell which starts natd). Thanks, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message