From owner-freebsd-alpha@FreeBSD.ORG Sun Apr 6 19:00:34 2003 Return-Path: Delivered-To: freebsd-alpha@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E062E37B401 for ; Sun, 6 Apr 2003 19:00:34 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id D068F43FAF for ; Sun, 6 Apr 2003 19:00:32 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h3720WUp086456 for ; Sun, 6 Apr 2003 19:00:32 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h3720WYt086455; Sun, 6 Apr 2003 19:00:32 -0700 (PDT) Resent-Date: Sun, 6 Apr 2003 19:00:32 -0700 (PDT) Resent-Message-Id: <200304070200.h3720WYt086455@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-alpha@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, j.roeder@tu-bs.de Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EF07837B401 for ; Sun, 6 Apr 2003 18:51:52 -0700 (PDT) Received: from ptchgate.rz.tu-bs.de (ptchgate.rz.tu-bs.de [134.169.246.49]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1295843F93 for ; Sun, 6 Apr 2003 18:51:52 -0700 (PDT) (envelope-from jens@ptchgate.rz.tu-bs.de) Received: from ptchgate.rz.tu-bs.de (localhost [127.0.0.1]) h371q3Bg000664 for ; Mon, 7 Apr 2003 03:52:03 +0200 (CEST) (envelope-from jens@ptchgate.rz.tu-bs.de) Received: (from root@localhost) by ptchgate.rz.tu-bs.de (8.12.6p2/8.12.6/Submit) id h371q3g7000663; Mon, 7 Apr 2003 03:52:03 +0200 (CEST) Message-Id: <200304070152.h371q3g7000663@ptchgate.rz.tu-bs.de> Date: Mon, 7 Apr 2003 03:52:03 +0200 (CEST) From: j.roeder@tu-bs.de To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Subject: alpha/50658: ipfw2 unalighed access causes kernel panic X-BeenThere: freebsd-alpha@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Alpha List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Apr 2003 02:00:35 -0000 >Number: 50658 >Category: alpha >Synopsis: ipfw2 unalighed access causes kernel panic >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-alpha >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Apr 06 19:00:32 PDT 2003 >Closed-Date: >Last-Modified: >Originator: jens >Release: FreeBSD 5.0-RELEASE-p7 alpha >Organization: TU-Braunschweig >Environment: System: FreeBSD ptchgate.rz.tu-bs.de 5.0-RELEASE-p7 FreeBSD 5.0-RELEASE-p7 #1: Mon Mar 31 02:29:29 CEST 2003 root@ptchgate.rz.tu-bs.de:/home/bsd/src/sys/alpha/compile/FIREWALL alpha >Description: Unfortunately the kernel doesn't write a message to /var/log/message when it panics and reboot is too quick to write every down by hand. Anyway, so when using "ipfw show" commanid it usually complains about "unalighned access". The output one can disable with the sysctl variable, as a posting in the news said and promised no further damage. This seems not to be right, as ocasionally the "ipfw show" command causes a kernel panic "kernel trap" due to "unalighend access of ipfw". This errow happens quite often when the "show" command is used. Chances about 1-30 in average. >How-To-Repeat: install several had full dynnamic rules and use "ipfw show" several times until the kernel panics >Fix: no idea due to my limited skills >Release-Note: >Audit-Trail: >Unformatted: