From jens@ptchgate.rz.tu-bs.de  Sun Apr  6 18:51:53 2003
Return-Path: <jens@ptchgate.rz.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 <FreeBSD-gnats-submit@freebsd.org>; 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 <FreeBSD-gnats-submit@freebsd.org>; 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])
	by ptchgate.rz.tu-bs.de (8.12.6p2/8.12.6) with ESMTP id h371q3Bg000664
	for <FreeBSD-gnats-submit@freebsd.org>; 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
Cc:
Subject: ipfw2 unalighed access causes kernel panic  
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         50658
>Category:       alpha
>Synopsis:       ipfw2 unalighed access causes kernel panic
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-alpha
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Apr 06 19:00:32 PDT 2003
>Closed-Date:    Tue Jun 03 18:39:44 PDT 2003
>Last-Modified:  Tue Jun 03 18:39:44 PDT 2003
>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:
State-Changed-From-To: open->closed 
State-Changed-By: ticso 
State-Changed-When: Tue Jun 3 18:34:17 PDT 2003 
State-Changed-Why:  
A fix has been commited to -current. 
It very likely also make it into 5.1-RELEASE. 


http://www.freebsd.org/cgi/query-pr.cgi?pr=50658 
>Unformatted:
