From owner-freebsd-stable Wed May 29 15:39:32 2002 Delivered-To: freebsd-stable@freebsd.org Received: from pluto.econz.co.nz (pluto.econz.co.nz [202.20.92.4]) by hub.freebsd.org (Postfix) with ESMTP id B66F437B428 for ; Wed, 29 May 2002 15:38:54 -0700 (PDT) Received: from MARKI ([172.16.110.22]) by pluto.econz.co.nz (8.9.3/8.9.3) with SMTP id KAA26803; Thu, 30 May 2002 10:38:34 +1200 (NZST) (envelope-from marki@econz.co.nz) Message-ID: <009e01c20761$8a855050$166e10ac@MARKI> From: "Mark Ibell" To: "Ian Dowse" Cc: References: <200205292152.aa04624@salmon.maths.tcd.ie> Subject: Re: Daily kernel panics on 4.6-RC system Date: Thu, 30 May 2002 10:38:21 +1200 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.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 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 Here's my /etc/make.conf: CFLAGS= -O -pipe COPTFLAGS= -O -pipe NO_KERNELCLEAN= true NO_MAKEDEV= true MODULES_WITH_WORLD= true Maybe worth noting is that the buildworld & buildkernel targets were built with 'make -j4' on a dual CPU machine. I might comment out the COPTFLAGS entry and omit the "-j4" option to make, but then "-j4" & "-O" should be safe shouldn't they? I might try swapping the RAM with another box to see if that helps. Cheers, Mark ----- Original Message ----- From: "Ian Dowse" To: "Mark Ibell" Cc: Sent: Thursday, May 30, 2002 8:52 AM Subject: Re: Daily kernel panics on 4.6-RC system In message <008b01c206b8$981dbcb0$166e10ac@MARKI>, Mark Ibell writes: >We have had trouble with our Dell PowerEdge 1400 server since day one and it >has now got to the point where it kernel panics once or twice a day. The >1400 currently runs 4.6-RC but we have had a similar problem with >4.3-RELEASE & 4.5-RELEASE, although the problem has definitely got a lot >worse since upgrading to 4.6-RC. Perhaps someone can make sense of the >following crash dump info. >Fatal trap 12: page fault while in kernel mode >fault virtual address = 0x50 >fault code = supervisor read, page not present >#6 0xc024100b in tcp_output (tp=0xde1ef7c0) at >/usr/src/sys/netinet/tcp_output.c:942 This crash "shouldn't happen"; the code is trying to read tp->rcv_nxt in the line if (win > 0 && SEQ_GT(tp->rcv_nxt+win, tp->rcv_adv)) but somehow the non-NULL `tp' argument has become NULL during the execution of the function. In the assembly output here, `tp' is kept in one register throughout the whole tcp_output() function, so it must be getting corrupted by one of the functions called by tcp_output(). Are you using any unusual compiler optimisations in /etc/make.conf? There are known issues with using -O2 or greater that would certainly explain these crashes. It would also be worth trying different hardware to determine if this is a software or hardware issue. Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message