From owner-freebsd-bugs Mon Sep 13 10:22:16 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from host.warwick.net (host.warwick.net [204.255.24.254]) by hub.freebsd.org (Postfix) with ESMTP id 47B77155AD; Mon, 13 Sep 1999 10:22:07 -0700 (PDT) (envelope-from kythorn@scorched.com) Received: from chaos (kythorn.upper.ul.warwick.net [208.228.96.34]) by host.warwick.net (8.9.3/8.9.3) with SMTP id NAA23521; Mon, 13 Sep 1999 13:22:06 -0400 (EDT) Message-ID: <000c01befe0c$84786d20$0200a8c0@chaos> From: "Jay Oliver" To: , References: <002d01befdbc$5b6b7300$0200a8c0@chaos> <19990913120055.A54858@relay.ucb.crimea.ua> Subject: Re: FreeBSD 3.3RC is crashing when using natd. Date: Mon, 13 Sep 1999 13:22:12 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org ----- Original Message ----- From: Ruslan Ermilov To: Jay Oliver Cc: ; Sent: Monday, September 13, 1999 5:00 AM Subject: Re: FreeBSD 3.3RC is crashing when using natd. > On Mon, Sep 13, 1999 at 03:48:23AM -0400, Jay Oliver wrote: > > I have recently cvsup'd to 3.3RC, and just today started using natd on that > > machine. Overall, this went quite well, but I have one issue that I cannot > > seem to resolve by myself. > > > > Starting with the reboot after I had edited /etc/rc.conf and re-compiled my > > kernel for natd (IPDIVERT and IPFIREWALL options) I started getting > > spontaneous reboots. There is no /core after these, nor is there a stack > > dump of any sort resulting from this. The only output produced at all is a > > scant two or three lines: > > > > Panic: sbappendaddr > > Automatic reboot in 15 seconds > > Syncing disks... > > > > With the lack of a core or stack dump, I don't know what information I can > > provide to shed further light on this issue. The machine itself is a simple > > enough pentium 166 with 32 megs of ram. The ethernet cards I am using are > > both Linksys LNE100TX's, using the "pn" device driver. Currently pn0 is > > connected to the hub for my LAN, and pn1 is connected to my ADSL modem. I > > have tried switching the cables and then switching the ifconfig's, etc in > > /etc/rc.conf, but the reboots still are happening. I previously had one of > > these cards in the FreeBSD machine, and was doing the NAT via a Win98 > > machine, this configuration ran without a hitch (On the FreeBSD end of > > things anyway, heh) for over a month, and also ran fine for the past couple > > days since I went to 3.3RC. The reboots themselves don't appear to have any > > rhyme or reason behind them, at least to me, as I FTP'd several hundred megs > > over the course of a few hours without a problem, and then had one of these > > reboots while checking my email (from a different machine, in both cases). > > > > I shall be more than happy to provide any further information that will help > > shed light on this subject, it has completely baffled me. > > > Could you please turn on the kernel debugger (DDB)? > > -- > Ruslan Ermilov Sysadmin and DBA of the > ru@ucb.crimea.ua United Commercial Bank, > ru@FreeBSD.org FreeBSD committer, > +380.652.247.647 Simferopol, Ukraine > > http://www.FreeBSD.org The Power To Serve > http://www.oracle.com Enabling The Information Age > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > I experienced a panic while in kernel debug mode (boot -d). The output of a trace is as follows: Debugger(c02a0dbb,c3286f00,c050f880,c33f5f50,c017f4d7) at Debugger+0x42 panic(c02a23d2,c3286f00,c050f880,820f144,c33f5f70) at panic+0x74 sbappendaddr(c3286f44,c02f9630,c050f880,0) at sbappendaddr+0x2b div_input(c050f880,14,c050f880,8169bc,820f144 at div_input+0x12a ip_input(c050f880) at ip_input+0x69f ipintr(c024dab3,0,27,27,820f144) at ipintr+0x4b swi_net_next() at swi_net_next I hope this helps somewhat. If I was supposed to issue other commands at the db> prompt, please inform me of such, and I will gladly do so, I apologize for having no previous debugging experience. Is there anyway to get this output I have placed above dumped somewhere? I manually typed that into another machine while experiencing the panic, and I will admit, I made a few mistakes the first pass. It took me a second pass to be sure it was correct (damn those f5f's), but I am 100% certain at this time that it is exactly what was displayed as the output of trace at the prompt db> - Jay Oliver kythorn@scorched.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message