From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 23 05:17:39 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9C8F716A4CE for ; Fri, 23 Jan 2004 05:17:39 -0800 (PST) Received: from multiplay.co.uk (www1.multiplay.co.uk [212.42.16.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 221D543D4C for ; Fri, 23 Jan 2004 05:17:22 -0800 (PST) (envelope-from killing@multiplay.co.uk) Received: from steven ([193.123.241.40]) by multiplay.co.uk (multiplay.co.uk [212.42.16.7]) (MDaemon.PRO.v6.8.5.R) with ESMTP id 1-md50000001547.tmp for ; Fri, 23 Jan 2004 13:08:58 +0000 Message-ID: <058401c3e1b4$2e451cb0$7b07000a@steven> From: "Steven Hartland" To: "Bogdan TARU" , References: <20040123125040.GA42187@icomag.de> Date: Fri, 23 Jan 2004 13:24:07 -0000 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 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Spam-Processed: multiplay.co.uk, Fri, 23 Jan 2004 13:08:58 +0000 (not processed: message from valid local sender) X-MDRemoteIP: 193.123.241.40 X-Return-Path: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-hackers@freebsd.org Subject: Re: 4.9 kernel panics on a poweredge 2650 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jan 2004 13:17:39 -0000 may be a silly question have ur booted into single user and force checked the disk may be some sort of fs corruption? Steve / K ----- Original Message ----- From: "Bogdan TARU" To: Sent: 23 January 2004 12:50 Subject: 4.9 kernel panics on a poweredge 2650 > > > Hi hackers, > > I am experiencing kernel panics on a poweredge 2650 each day around > 3am (usually the machine comes up at 3:04am). The kernel panics are > reproductable by running: /etc/periodic/security/100.chksetuid (in > fact by runnning find on /usr with -perms). The problem lies > somewhere in /usr/ports. Deleting the /usr/ports tree doesn't solve > it, trying a cvs up of /usr/ports results in a crash again. > > I googled around a lil' bit, and found: > http://lists.freebsd.org/pipermail/freebsd-hackers/2003-April/000192.html, > and also Terry's answer, but that addresses freebsd 4.7. But my box > is running 4.9-release, and the systems was cleanly installed with > 4.9 from the very beginning, so not upgraded from 4.7 or any other > previous version. > > The dmesg looks like: > > Copyright (c) 1992-2003 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, > 1994 > The Regents of the University of California. All rights > reserved. > FreeBSD 4.9-RELEASE #1: Mon Nov 17 23:47:49 CET 2003 > root@:/usr/src/sys/compile/saturn > Timecounter "i8254" frequency 1193182 Hz > Timecounter "TSC" frequency 1790761584 Hz > CPU: Intel(R) Xeon(TM) CPU 1.80GHz (1790.76-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0xf27 Stepping = 7 > Features=0xbfebfbff > Hyperthreading: 2 logical CPUs > real memory = 2147418112 (2097088K bytes) > avail memory = 2088136704 (2039196K bytes) > Preloaded elf kernel "kernel" at 0xc0312000. > Warning: Pentium 4 CPU: PSE disabled > Pentium Pro MTRR support enabled > Using $PIR table, 9 entries at 0xc00fc430 > npx0: on motherboard > npx0: INT 16 interface > pcib0: on motherboard > pci0: on pcib0 > pci0: (vendor=0x1028, dev=0x000c) at 4.0 irq 11 > pci0: (vendor=0x1028, dev=0x0008) at 4.1 irq 10 > pci0: (vendor=0x1028, dev=0x000d) at 4.2 irq 7 > pci0: at 14.0 > atapci0: port > 0x8b0-0x8bf,0x8d8-0x8db,0x8d0-0x8d7,0x8c8-0x8cb,0x8c0-0x8c7 at device > 15.1 on pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > pci0: at 15.2 irq 5 > isab0: at device 15.3 on > pci0 > isa0: on isab0 > pcib1: on motherboard > pci1: on pcib1 > pcib2: on motherboard > pci2: on pcib2 > pcib3: on motherboard > pci3: on pcib3 > bge0: mem > 0xfcf10000-0xfcf1ffff irq 11 at device 6.0 on pci3 > bge0: Ethernet address: 00:06:5b:f6:48:38 > miibus0: on bge0 > brgphy0: on miibus0 > brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, > 1000baseTX-FDX, auto > bge1: mem > 0xfcf00000-0xfcf0ffff irq 10 at device 8.0 on pci3 > bge1: Ethernet address: 00:06:5b:f6:48:39 > miibus1: on bge1 > brgphy1: on miibus1 > brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, > 1000baseTX-FDX, auto > bge1: mem > 0xfcf00000-0xfcf0ffff irq 10 at device 8.0 on pci3 > bge1: Ethernet address: 00:06:5b:f6:48:39 > miibus1: on bge1 > brgphy1: on miibus1 > brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, > 1000baseTX-FDX, auto > pcib4: on > motherboard > pci4: on pcib4 > pcib8: at device 8.0 on > pci4 > pci5: on pcib8 > pci5: (vendor=0x9005, dev=0x00c5) at 6.0 irq 7 > pci5: (vendor=0x9005, dev=0x00c5) at 6.1 irq 11 > aac0: mem 0xf0000000-0xf7ffffff irq 7 at device 8.1 > on pci4 > aac0: i960RX 100MHz, 118MB cache memory, optional battery present > aac0: Kernel 2.7-1, Build 3170, S/N 5010d3 > aac0: Supported > Options=75c > pcib5: on > motherboard > pci6: on pcib5 > pcib6: on > motherboard > pci7: on pcib6 > pcib7: on > motherboard > pci8: on pcib7 > orm0: