From owner-freebsd-stable Tue Feb 12 3:55:46 2002 Delivered-To: freebsd-stable@freebsd.org Received: from sumter.awod.com (sumter.awod.com [208.140.99.1]) by hub.freebsd.org (Postfix) with ESMTP id B788037B404 for ; Tue, 12 Feb 2002 03:55:40 -0800 (PST) Received: from teddy.fas.com (pcp01008475pcs.mplsnt01.sc.comcast.net [68.58.200.215]) by sumter.awod.com (8.8.7/8.12.2) with ESMTP id GAA28143; Tue, 12 Feb 2002 06:48:26 -0500 (EST) (envelope-from stanb@awod.com) Received: from stan by teddy.fas.com with local (Exim 3.34 #1 (Debian)) id 16abQb-0002gG-00; Tue, 12 Feb 2002 06:48:53 -0500 Date: Tue, 12 Feb 2002 06:48:53 -0500 From: stan To: Danny Pansters Cc: FreeBSD Stable Mailing List Subject: Re: Kernel Panic on 4.5 STABLE Message-ID: <20020212114853.GA10230@teddy.fas.com> Mail-Followup-To: Danny Pansters , FreeBSD Stable Mailing List References: <20020209160959.GA1010@teddy.fas.com> <20020211223856.2A31E24D28@mail.ricin.net> <20020212015652.GB32269@teddy.fas.com> <20020212021153.5C39524D28@mail.ricin.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020212021153.5C39524D28@mail.ricin.net> User-Agent: Mutt/1.3.27i X-Editor: gVim X-Operating-System: Debian GNU/Linux X-Kernel-Version: 2.4.17 X-Uptime: 06:40:22 up 8 days, 12:15, 2 users, load average: 0.00, 0.00, 0.00 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Feb 12, 2002 at 03:12:18AM +0100, Danny Pansters wrote: > > > > > Thanks, I've done that 3 times in the last 2 days :-( > > > > > > I've been able to reproduce it with the GENERIC kernel. I also > > removed everythign that I did not absolutley nee, rebuilt the > > kernel, and it's still there :-( > > > > > > Thanks for the advice, and help. > > Hmm well it didn't help much though :-( > > We could take it to a higher level of patheticality (just invented a > word there I think) and consider a reinstall from scratch from > 4.5-REL ISO. If it still happens then well you'll at least be famous > for discovering a major bug... > I got to playing around last night. i decided to manually load the ipfw module, and see if I could reprodice the crash. However, when I tried to load it, I got an error message about it already being loaded. After seatching throguh all the /boot configs etc. I ran kldsatat which still said it was not loaded. So I tried to unload it, which appeared to work. After that I could not reproduce the crash. I suspect that the optional trafshow modules (from portss) may be using some of the same hooks as ipfw does? In any case I reconfigured rc.conf to load ipfw with the open ruleset, and now ipfw -a l no longer panics my mahcine. I'm confident that this is a genuine bug, but at this point, I have spent over 4 days working on it, and (no offense to you inetnded) it's apaprent that I have not atracted the interest of anyone that can really understand the porblem. So, even though I would like to see the bug fixed, I'm just goign to take my workaround, and move on to the work that I had scheduled for this wekend. U;v got to get my wifes ne Debian worksatiation set up, and going. Thanks for all the patient help on this. You were very helpful in geting me to logicly reason through this. -- "They that would give up essential liberty for temporary safety deserve neither liberty nor safety." -- Benjamin Franklin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message