Date: Mon, 7 Apr 2003 03:52:03 +0200 (CEST) From: j.roeder@tu-bs.de To: FreeBSD-gnats-submit@FreeBSD.org Subject: alpha/50658: ipfw2 unalighed access causes kernel panic Message-ID: <200304070152.h371q3g7000663@ptchgate.rz.tu-bs.de> Resent-Message-ID: <200304070200.h3720WYt086455@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>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:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200304070152.h371q3g7000663>