From owner-freebsd-questions@FreeBSD.ORG Wed Mar 14 18:50:32 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 00D4016A403 for ; Wed, 14 Mar 2007 18:50:32 +0000 (UTC) (envelope-from freebsd@hyperconx.com) Received: from front.hyperconx.net (front.hyperconx.net [65.74.165.5]) by mx1.freebsd.org (Postfix) with ESMTP id D008213C45B for ; Wed, 14 Mar 2007 18:50:31 +0000 (UTC) (envelope-from freebsd@hyperconx.com) Received: from adsl-69-225-224-190.dsl.skt2ca.pacbell.net ([69.225.224.190] helo=Production) by front.hyperconx.net with esmtpa (Exim 4.53) id 1HRYYS-000G77-2l for freebsd-questions@freebsd.org; Wed, 14 Mar 2007 10:50:32 -0800 From: "Wil Hatfield" To: "'FreeBSD Questions'" Date: Wed, 14 Mar 2007 11:51:05 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <11920492@srv.sem.ipt.ru> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 Importance: Normal X-Antivirus-Scanner: HyperConX Bug-Guard AV on (front.hyperconx.net) Subject: RE: Upgrading from FreeBSD 6.1-Stable to Latest X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Mar 2007 18:50:32 -0000 Taking this thread a little further since it is right in line with my todo list for tonight. I currently have 6.1 installed on a Supermicro machine with two ata drives. There has been a major bug that causes frequent kernel panics which started at 6.0. The following build options seemed to help with quick rebooting and recovery. But of course this week the reboots aren't going to well and it is definately time to upgrade to 6.2-RELEASE (RELENG_6_2) in hopes that whatever is causing the kernel panics is software related and has been fixed. makeoptions DEBUG=-g options DDB, KDB, GDB options INVARIANTS options INVARIANT_SUPPORT options WITNESS_KDB options WITNESS_SKIPSPIN options BREAK_TO_DEBUGGER,ALT_BREAK_TO_DEBUGGER options KDB_UNATTENDED options QUOTA options PMAP_SHPGPERPROC=601 options TCP_DROP_SYNFIN options SMP options IPFILTER options IPFILTER_LOG options IPFILTER_DEFAULT_BLOCK options IPFIREWALL options IPFIREWALL_VERBOSE options DUMMYNET options IPSTEALTH options HZ=2000 #options RESTARTABLE_PANICS options PANIC_REBOOT_WAIT_TIME=5 Will some of these options still work with 6.2-RELEASE or should I omit something here in order to use the 6.2 release properly? I am sure there are some since I am going from a 6.1 prerelease to a release. I am just not sure which ones should be omitted. I still want the capability of the machine rebooting unattended if a panic should occur. Here is some more info in case anybody sees anything that I don't regarding those panics. Never a single vmcore so I have found debugging quite useless. But of course I do understand that I have alot to learn about debugging. Not my forte. ### uname -a ### 123.domain.net 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #0: Thu Apr 20 16:01:16 PDT 2006 wilh@123.domain.net:/usr/obj/usr/src/sys/CUSTOM-KERNEL i386 ### dmesg.today ### Copyright (c) 1992-2006 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 6.1-PRERELEASE #0: Thu Apr 20 16:01:16 PDT 2006 wilh@123.domain.net:/usr/obj/usr/src/sys/CUSTOM-KERNEL Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.20GHz (3206.53-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf43 Stepping = 3 Features=0xbfebfbff Features2=0x641d> AMD Features=0x20100000 Hyperthreading: 2 logical CPUs real memory = 2146893824 (2047 MB) avail memory = 2094931968 (1997 MB) MPTable: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 6 cpu3 (AP): APIC ID: 7 ioapic0: Assuming intbase of 0 ioapic1: Assuming intbase of 24 ioapic2: Assuming intbase of 48 ioapic3: Assuming intbase of 72 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard ioapic2 irqs 48-71 on motherboard ioapic3 irqs 72-95 on motherboard npx0: [FAST] npx0: on motherboard npx0: INT 16 interface cpu0 on motherboard cpu1 on motherboard cpu2 on motherboard cpu3 on motherboard pcib0: pcibus 0 on motherboard pci0: on pcib0 pci0: at device 0.1 (no driver attached) pci0: at device 1.0 (no driver attached) pcib1: irq 16 at device 2.0 on pci0 pci1: on pcib1 pcib2: at device 0.0 on pci1 pci2: on pcib2 pci1: at device 0.1 (no driver attached) pcib3: at device 0.2 on pci1 pci3: on pcib3 pci1: at device 0.3 (no driver attached) pcib4: irq 16 at device 4.0 on pci0 pci4: on pcib4 pcib5: irq 16 at device 6.0 on pci0 pci5: on pcib5 pcib6: at device 28.0 on pci0 pci6: on pcib6 em0: port 0x2000-0x203f mem 0xdd200000-0xdd21ffff irq 24 at device 1.0 on pci6 em0: Ethernet address: 00:30:48:84:f0:04 em1: port 0x2040-0x207f mem 0xdd220000-0xdd23ffff irq 25 at device 2.0 on pci6 em1: Ethernet address: 00:30:48:84:f0:05 uhci0: port 0x1400-0x141f irq 16 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0x1420-0x143f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pci0: at device 29.4 (no driver attached) pci0: at device 29.5 (no driver attached) ehci0: mem 0xdd001400-0xdd0017ff irq 23 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] usb2: EHCI version 1.0 usb2: companion controllers, 2 ports each: usb0 usb1 usb2: on ehci0 usb2: USB revision 2.0 uhub2: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub2: 4 ports with 4 removable, self powered pcib7: at device 30.0 on pci0 pci7: on pcib7 pci7: at device 1.0 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1460-0x146f at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 pci0: at device 31.3 (no driver attached) pmtimer0 on isa0 orm0: at iomem 0xc0000-0xc7fff,0xc8000-0xc8fff on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources (memory) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) Timecounters tick every 1.000 msec IP Filter: v4.1.8 initialized. Default = block all, Logging = enabled ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding disabled, default to deny, logging unlimited ad0: 190782MB at ata0-master UDMA100 ad1: 190782MB at ata0-slave UDMA100 acd0: CDROM at ata1-master UDMA33 SMP: AP CPU #3 Launched! SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! Trying to mount root from ufs:/dev/ad0s1a WARNING: / was not properly dismounted em0: link state changed to UP