From owner-freebsd-stable@FreeBSD.ORG Tue May 30 13:46:36 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A86B316A600 for ; Tue, 30 May 2006 13:46:36 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 014B343D70 for ; Tue, 30 May 2006 13:46:35 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 1939346CC5; Tue, 30 May 2006 09:46:34 -0400 (EDT) Date: Tue, 30 May 2006 14:46:34 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Michael Ortmann In-Reply-To: <447AAB44.9080402@googlemail.com> Message-ID: <20060530144516.E25073@fledge.watson.org> References: <447AAB44.9080402@googlemail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: reproduceable kernel panic when trying to use tap0 interface (sparc64) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 May 2006 13:46:42 -0000 On Mon, 29 May 2006, Michael Ortmann wrote: > im using 6_stable on sparc64 and get a 100% reproduceable kernel panic. it > crashes when i try to usr/create the tap0 interface. (i discovered it when i > tried to run openvpn). so i guess it may be the tap driver on sparc64. i can > provice kernel core and offer my help. i wrote to the sparc64 mailinglist > before but now i guess its better off here. This sounds like a kernel code alignment bug, which is likely easy to fix. However... > == how to reproduce the kernel panic == > > # cat /dev/zero >/dev/tap0 > > tap0: Ethernet address: 00:bd:00:02:10:00 > panic: trap: memory address not aligned > cpuid = 0 > KDB: enter: panic > [thread 449 tid 100044] > Stopped at kdb_enter+0x3c: ta %xcc, 1 Whoops, the gdb stack trace below looks corrupted and/or wrong. Could you instead provide the output of the "trace" command in DDB? DDB traces can be more reliable under some circumstances, and more resistant to mistakes such as matching the wrong kernel to the wrong core, gdb bugs, and so on. Robert N M Watson