From owner-freebsd-isp@FreeBSD.ORG Tue Dec 26 21:35:34 2006 Return-Path: X-Original-To: FreeBSD-ISP@FreeBSD.org Delivered-To: FreeBSD-ISP@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7906B16A403 for ; Tue, 26 Dec 2006 21:35:34 +0000 (UTC) (envelope-from jan@digitaldaemon.com) Received: from digitaldaemon.com (digitaldaemon.com [63.105.9.34]) by mx1.freebsd.org (Postfix) with SMTP id 58D7413C46E for ; Tue, 26 Dec 2006 21:35:32 +0000 (UTC) (envelope-from jan@digitaldaemon.com) Received: (qmail 26384 invoked by uid 98); 26 Dec 2006 21:09:08 -0000 Received: from 63.105.9.34 by digitaldaemon.com (envelope-from , uid 89) with qmail-scanner-1.25 (clamdscan: 0.87/1195. Clear:RC:1(63.105.9.34):. Processed in 0.064548 secs); 26 Dec 2006 21:09:08 -0000 X-Qmail-Scanner-Mail-From: jan@digitaldaemon.com via digitaldaemon.com X-Qmail-Scanner: 1.25 (Clear:RC:1(63.105.9.34):. Processed in 0.064548 secs) Received: from digitaldaemon.com (HELO ?160.63.102.2?) (63.105.9.34) by digitaldaemon.com with SMTP; 26 Dec 2006 21:09:08 -0000 Message-ID: <45918F6E.90006@digitaldaemon.com> Date: Tue, 26 Dec 2006 16:09:02 -0500 From: Jan Knepper User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: FreeBSD ISP , FreeBSD Hackers Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: 6.1-RELEASE / 6.2 Kernel Crash... X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Dec 2006 21:35:34 -0000 All, (sorry for the cross post) Something goofy is going on with a 6.x kernel. Dual Opteron Server (Tyan motherboard). 2 GB RAM... 2 x 256 GB SATA HD's. Just upgraded this machine from FreeBSD 5.5-STABLE to 6.2RC# and than down to 6.1-RELEASE. For some reason FreeBSD 6.1 seems to be very unstable. I use a custom kernel, (most devices not present in the system have been removed). When I create an SMP kernel after an undefined about of time which I have seen varying from 5 minutes up to about 6 hours the kernel will just hang. Things that seem to accelerate/aggrevate this are running CVSup from a repository on the same system. Something else that seems to push it is dd if=/dev/ad4 if=/dev/ad6 bs=64m (copying the master disk to the supposed slave, however geom is not active and module geom_mirror is not loaded! When I take SMP out of the kernel config and rebuild and install instead of hanging, the system seems to crash and reboot when I perform the same action. Also... When I first upgraded I did get an error during boot: kernel: module_register_init: MOD_LOAD (amr_linux, 0xffffffff805db120, 0) error 6 I disabled device amr (under RAID controllers) in the kernel config which took care of this. Following the bootlog. If any of you had any idea what the problem might be I definitely would like to know. Thanks! Jan syslogd: kernel boot file is /boot/kernel/kernel kernel: Copyright (c) 1992-2006 The FreeBSD Project. kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 kernel: The Regents of the University of California. All rights reserved. kernel: FreeBSD 6.1-RELEASE #4: Tue Dec 26 12:03:35 EST 2006 kernel: root@digitaldaemon.com:/usr/src/sys/amd64/compile/digitaldaemon kernel: Timecounter "i8254" frequency 1193182 Hz quality 0 kernel: CPU: AMD Opteron(tm) Processor 246 (1993.53-MHz K8-class CPU) kernel: Origin = "AuthenticAMD" Id = 0xf5a Stepping = 10 kernel: Features=0x78bfbff kernel: AMD Features=0xe0500800 kernel: real memory = 2147418112 (2047 MB) kernel: avail memory = 2065596416 (1969 MB) kernel: ACPI APIC Table: kernel: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs kernel: cpu0 (BSP): APIC ID: 0 kernel: cpu1 (AP): APIC ID: 1 kernel: MADT: Forcing active-low polarity and level trigger for SCI kernel: ioapic0 irqs 0-23 on motherboard kernel: ioapic1 irqs 24-27 on motherboard kernel: ioapic2 irqs 28-31 on motherboard kernel: netsmb_dev: loaded kernel: acpi0: on motherboard kernel: acpi0: Power Button (fixed) kernel: Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0x5008-0x500b on acpi0 kernel: cpu0: on acpi0 kernel: acpi_throttle0: on cpu0 kernel: cpu1: on acpi0 kernel: pcib0: port 0xcf8-0xcff on acpi0 kernel: pci0: on pcib0 kernel: pcib1: at device 6.0 on pci0 kernel: pci3: on pcib1 kernel: ohci0: mem 0xff3fd000-0xff3fdfff irq 19 at device 0.0 on pci3 kernel: ohci0: [GIANT-LOCKED] kernel: usb0: OHCI version 1.0, legacy support kernel: usb0: on ohci0 kernel: usb0: USB revision 1.0 kernel: uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 kernel: uhub0: 3 ports with 3 removable, self powered kernel: ohci1: mem 0xff3fe000-0xff3fefff irq 19 at device 0.1 on pci3 kernel: ohci1: [GIANT-LOCKED] kernel: usb1: OHCI version 1.0, legacy support kernel: usb1: on ohci1 kernel: usb1: USB revision 1.0 kernel: uhub1: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 kernel: uhub1: 3 ports with 3 removable, self powered kernel: xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0x8080-0x80ff mem 0xff3ff800-0xff3ff87f irq 16 at device 10.0 on pci3 kernel: miibus0: on xl0 kernel: ukphy0: on miibus0 kernel: ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto kernel: xl0: Ethernet address: 00:04:75:ad:ac:0a kernel: atapci0: port 0x8c00-0x8c07,0x8880-0x8883,0x8800-0x8807,0x8480-0x8483,0x8400-0x840f mem 0xff3ffc00-0xff3fffff irq 17 at device 11.0 on pci3 kernel: ata2: on atapci0 kernel: ata3: on atapci0 kernel: ata4: on atapci0 kernel: ata5: on atapci0 kernel: fwohci0: mem 0xff3ff000-0xff3ff7ff,0xff3f8000-0xff3fbfff irq 19 at device 12.0 on pci3 kernel: fwohci0: OHCI version 1.10 (ROM=1) kernel: fwohci0: No. of Isochronous channels is 4. kernel: fwohci0: EUI64 00:e0:81:00:00:30:4c:06 kernel: fwohci0: Phy 1394a available S400, 2 ports. kernel: fwohci0: Link S400, max_rec 2048 bytes. kernel: firewire0: on fwohci0 kernel: fwe0: on firewire0 kernel: if_fwe0: Fake Ethernet address: 02:e0:81:30:4c:06 kernel: fwe0: Ethernet address: 02:e0:81:30:4c:06 kernel: fwe0: if_start running deferred for Giant kernel: sbp0: on firewire0 kernel: fwohci0: Initiate bus reset kernel: fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode kernel: firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) kernel: firewire0: bus manager 0 (me) kernel: isab0: at device 7.0 on pci0 kernel: isa0: on isab0 kernel: atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 7.1 on pci0 kernel: ata0: on atapci1 kernel: ata1: on atapci1 kernel: pci0: at device 7.2 (no driver attached) kernel: pci0: at device 7.3 (no driver attached) kernel: pci0: at device 7.5 (no driver attached) kernel: pcib2: at device 10.0 on pci0 kernel: pci2: on pcib2 kernel: bge0: mem 0xff1f0000-0xff1fffff irq 24 at device 9.0 on pci2 kernel: miibus1: on bge0 kernel: brgphy0: on miibus1 kernel: brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto kernel: bge0: Ethernet address: 00:e0:81:2d:ee:f7 kernel: pci0: at device 10.1 (no driver attached) kernel: pcib3: at device 11.0 on pci0 kernel: pci1: on pcib3 kernel: pci0: at device 11.1 (no driver attached) kernel: pcib4: on acpi0 kernel: pci4: on pcib4 kernel: pcib5: at device 1.0 on pci4 kernel: pci5: on pcib5 kernel: pci5: at device 0.0 (no driver attached) kernel: pci5: at device 0.1 (no driver attached) kernel: acpi_button0: on acpi0 kernel: atkbdc0: port 0x60,0x64 irq 1 on acpi0 kernel: atkbd0: irq 1 on atkbdc0 kernel: kbd0 at atkbd0 kernel: atkbd0: [GIANT-LOCKED] kernel: psm0: irq 12 on atkbdc0 kernel: psm0: [GIANT-LOCKED] kernel: psm0: model IntelliMouse Explorer, device ID 4 kernel: sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 kernel: sio0: type 16550A kernel: sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 kernel: sio1: type 16550A kernel: fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 kernel: fdc0: [FAST] kernel: ppc0: port 0x378-0x37f irq 7 on acpi0 kernel: ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode kernel: ppbus0: on ppc0 kernel: orm0: at iomem 0xc0000-0xccfff,0xcd000-0xd17ff,0xd1800-0xd1fff,0 xd2000-0xd2fff on isa0 kernel: sc0: at flags 0x100 on isa0 kernel: sc0: VGA <16 virtual consoles, flags=0x300> kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 kernel: ugen0: American Power Conversion Back-UPS RS 1500 FW:8.g9 .D USB FW:g9, rev 1.10/1.06, addr 2 kernel: Timecounters tick every 1.000 msec kernel: ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding enabled, default to deny, logging limited to 100 packets/entry by default kernel: acd0: DVDR at ata0-master UDMA33 kernel: ad4: 238475MB at ata2-master SATA150 kernel: ad6: 238475MB at ata3-master SATA150 kernel: SMP: AP CPU #1 Launched! kernel: Trying to mount root from ufs:/dev/ad4s1a From owner-freebsd-isp@FreeBSD.ORG Tue Dec 26 22:45:13 2006 Return-Path: X-Original-To: FreeBSD-ISP@FreeBSD.org Delivered-To: FreeBSD-ISP@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 21D6C16A407 for ; Tue, 26 Dec 2006 22:45:13 +0000 (UTC) (envelope-from tim@halenet.com.au) Received: from helen.halenet.com.au (helen.halenet.com.au [203.55.33.243]) by mx1.freebsd.org (Postfix) with ESMTP id 3A46013C492 for ; Tue, 26 Dec 2006 22:45:12 +0000 (UTC) (envelope-from tim@halenet.com.au) Received: from localhost (localhost.halenet.com.au [127.0.0.1]) by helen.halenet.com.au (Postfix) with ESMTP id D608311443; Wed, 27 Dec 2006 08:18:06 +1000 (EST) X-Virus-Scanned: amavisd-new at halenet.com.au Received: from helen.halenet.com.au ([127.0.0.1]) by localhost (helen.halenet.com.au [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FDpfhI73fx3t; Wed, 27 Dec 2006 08:18:04 +1000 (EST) Received: from laptopt (wireless-48-200.halenet.com.au [61.88.48.200]) by helen.halenet.com.au (Postfix) with SMTP id 706891143F; Wed, 27 Dec 2006 08:18:02 +1000 (EST) Message-ID: <004c01c7293b$d5e03b40$6500a8c0@laptopt> From: "Tim McCullagh" To: "Jan Knepper" , "FreeBSD ISP" References: <45918F6E.90006@digitaldaemon.com> Date: Wed, 27 Dec 2006 08:18:55 +1000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3028 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 Cc: Subject: Re: 6.1-RELEASE / 6.2 Kernel Crash... X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Dec 2006 22:45:13 -0000 Hi Jan try editing your loader.conf I had a similar sounding issue. As soon as I did the following the system became stable immediately. It was also on a Tyan Mainboard, although with dual Xeon's # vi /boot/loader.conf hint.apic.0.disabled="1" Regards Tim ----- Original Message ----- From: "Jan Knepper" To: "FreeBSD ISP" ; "FreeBSD Hackers" Sent: Wednesday, December 27, 2006 7:09 AM Subject: 6.1-RELEASE / 6.2 Kernel Crash... > All, (sorry for the cross post) > > Something goofy is going on with a 6.x kernel. > > Dual Opteron Server (Tyan motherboard). 2 GB RAM... 2 x 256 GB SATA HD's. > Just upgraded this machine from FreeBSD 5.5-STABLE to 6.2RC# and than down > to 6.1-RELEASE. > For some reason FreeBSD 6.1 seems to be very unstable. I use a custom > kernel, (most devices not present in the system have been removed). > > When I create an SMP kernel after an undefined about of time which I have > seen varying from 5 minutes up to about 6 hours the kernel will just hang. > Things that seem to accelerate/aggrevate this are running CVSup from a > repository on the same system. > Something else that seems to push it is dd if=/dev/ad4 if=/dev/ad6 bs=64m > (copying the master disk to the supposed slave, however geom is not active > and module geom_mirror is not loaded! > > When I take SMP out of the kernel config and rebuild and install instead > of hanging, the system seems to crash and reboot when I perform the same > action. > > Also... When I first upgraded I did get an error during boot: > kernel: module_register_init: MOD_LOAD (amr_linux, 0xffffffff805db120, 0) > error 6 > I disabled device amr (under RAID controllers) in the kernel config which > took care of this. > > Following the bootlog. If any of you had any idea what the problem might > be I definitely would like to know. > > Thanks! > Jan > > > > syslogd: kernel boot file is /boot/kernel/kernel > kernel: Copyright (c) 1992-2006 The FreeBSD Project. > kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, > 1993, 1994 > kernel: The Regents of the University of California. All rights reserved. > kernel: FreeBSD 6.1-RELEASE #4: Tue Dec 26 12:03:35 EST 2006 > kernel: root@digitaldaemon.com:/usr/src/sys/amd64/compile/digitaldaemon > kernel: Timecounter "i8254" frequency 1193182 Hz quality 0 > kernel: CPU: AMD Opteron(tm) Processor 246 (1993.53-MHz K8-class CPU) > kernel: Origin = "AuthenticAMD" Id = 0xf5a Stepping = 10 > kernel: > Features=0x78bfbff > kernel: AMD Features=0xe0500800 > kernel: real memory = 2147418112 (2047 MB) > kernel: avail memory = 2065596416 (1969 MB) > kernel: ACPI APIC Table: > kernel: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > kernel: cpu0 (BSP): APIC ID: 0 > kernel: cpu1 (AP): APIC ID: 1 > kernel: MADT: Forcing active-low polarity and level trigger for SCI > kernel: ioapic0 irqs 0-23 on motherboard > kernel: ioapic1 irqs 24-27 on motherboard > kernel: ioapic2 irqs 28-31 on motherboard > kernel: netsmb_dev: loaded > kernel: acpi0: on motherboard > kernel: acpi0: Power Button (fixed) > kernel: Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0x5008-0x500b on > acpi0 > kernel: cpu0: on acpi0 > kernel: acpi_throttle0: on cpu0 > kernel: cpu1: on acpi0 > kernel: pcib0: port 0xcf8-0xcff on acpi0 > kernel: pci0: on pcib0 > kernel: pcib1: at device 6.0 on pci0 > kernel: pci3: on pcib1 > kernel: ohci0: mem 0xff3fd000-0xff3fdfff > irq 19 at device 0.0 on pci3 > kernel: ohci0: [GIANT-LOCKED] > kernel: usb0: OHCI version 1.0, legacy support > kernel: usb0: on ohci0 > kernel: usb0: USB revision 1.0 > kernel: uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > kernel: uhub0: 3 ports with 3 removable, self powered > kernel: ohci1: mem 0xff3fe000-0xff3fefff > irq 19 at device 0.1 on pci3 > kernel: ohci1: [GIANT-LOCKED] > kernel: usb1: OHCI version 1.0, legacy support > kernel: usb1: on ohci1 > kernel: usb1: USB revision 1.0 > kernel: uhub1: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > kernel: uhub1: 3 ports with 3 removable, self powered > kernel: xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0x8080-0x80ff mem > 0xff3ff800-0xff3ff87f irq 16 at device 10.0 on pci3 > kernel: miibus0: on xl0 > kernel: ukphy0: on miibus0 > kernel: ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > kernel: xl0: Ethernet address: 00:04:75:ad:ac:0a > kernel: atapci0: port > 0x8c00-0x8c07,0x8880-0x8883,0x8800-0x8807,0x8480-0x8483,0x8400-0x840f mem > 0xff3ffc00-0xff3fffff irq 17 at device 11.0 on pci3 > kernel: ata2: on atapci0 > kernel: ata3: on atapci0 > kernel: ata4: on atapci0 > kernel: ata5: on atapci0 > kernel: fwohci0: mem > 0xff3ff000-0xff3ff7ff,0xff3f8000-0xff3fbfff irq 19 at device 12.0 on pci3 > kernel: fwohci0: OHCI version 1.10 (ROM=1) > kernel: fwohci0: No. of Isochronous channels is 4. > kernel: fwohci0: EUI64 00:e0:81:00:00:30:4c:06 > kernel: fwohci0: Phy 1394a available S400, 2 ports. > kernel: fwohci0: Link S400, max_rec 2048 bytes. > kernel: firewire0: on fwohci0 > kernel: fwe0: on firewire0 > kernel: if_fwe0: Fake Ethernet address: 02:e0:81:30:4c:06 > kernel: fwe0: Ethernet address: 02:e0:81:30:4c:06 > kernel: fwe0: if_start running deferred for Giant > kernel: sbp0: on firewire0 > kernel: fwohci0: Initiate bus reset > kernel: fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode > kernel: firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) > kernel: firewire0: bus manager 0 (me) > kernel: isab0: at device 7.0 on pci0 > kernel: isa0: on isab0 > kernel: atapci1: port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 7.1 on pci0 > kernel: ata0: on atapci1 > kernel: ata1: on atapci1 > kernel: pci0: at device 7.2 (no driver attached) > kernel: pci0: at device 7.3 (no driver attached) > kernel: pci0: at device 7.5 (no driver attached) > kernel: pcib2: at device 10.0 on pci0 > kernel: pci2: on pcib2 > kernel: bge0: mem > 0xff1f0000-0xff1fffff irq 24 at device 9.0 on pci2 > kernel: miibus1: on bge0 > kernel: brgphy0: on miibus1 > kernel: brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, > 1000baseTX, 1000baseTX-FDX, auto > kernel: bge0: Ethernet address: 00:e0:81:2d:ee:f7 > kernel: pci0: at device 10.1 (no > driver attached) > kernel: pcib3: at device 11.0 on pci0 > kernel: pci1: on pcib3 > kernel: pci0: at device 11.1 (no > driver attached) > kernel: pcib4: on acpi0 > kernel: pci4: on pcib4 > kernel: pcib5: at device 1.0 on pci4 > kernel: pci5: on pcib5 > kernel: pci5: at device 0.0 (no driver attached) > kernel: pci5: at device 0.1 (no driver attached) > kernel: acpi_button0: on acpi0 > kernel: atkbdc0: port 0x60,0x64 irq 1 on > acpi0 > kernel: atkbd0: irq 1 on atkbdc0 > kernel: kbd0 at atkbd0 > kernel: atkbd0: [GIANT-LOCKED] > kernel: psm0: irq 12 on atkbdc0 > kernel: psm0: [GIANT-LOCKED] > kernel: psm0: model IntelliMouse Explorer, device ID 4 > kernel: sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags > 0x10 on acpi0 > kernel: sio0: type 16550A > kernel: sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 > kernel: sio1: type 16550A > kernel: fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 > drq 2 on acpi0 > kernel: fdc0: [FAST] > kernel: ppc0: port 0x378-0x37f irq 7 on > acpi0 > kernel: ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode > kernel: ppbus0: on ppc0 > kernel: orm0: at iomem > 0xc0000-0xccfff,0xcd000-0xd17ff,0xd1800-0xd1fff,0 > xd2000-0xd2fff on isa0 > kernel: sc0: at flags 0x100 on isa0 > kernel: sc0: VGA <16 virtual consoles, flags=0x300> > kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff > on isa0 > kernel: ugen0: American Power Conversion Back-UPS RS 1500 FW:8.g9 .D USB > FW:g9, rev 1.10/1.06, addr 2 > kernel: Timecounters tick every 1.000 msec > kernel: ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding > enabled, default to deny, logging limited to 100 packets/entry by default > kernel: acd0: DVDR at ata0-master UDMA33 > kernel: ad4: 238475MB at ata2-master SATA150 > kernel: ad6: 238475MB at ata3-master SATA150 > kernel: SMP: AP CPU #1 Launched! > kernel: Trying to mount root from ufs:/dev/ad4s1a > > _______________________________________________ > freebsd-isp@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-isp > To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org" > From owner-freebsd-isp@FreeBSD.ORG Wed Dec 27 00:03:23 2006 Return-Path: X-Original-To: FreeBSD-ISP@FreeBSD.org Delivered-To: FreeBSD-ISP@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0330416A4C8 for ; Wed, 27 Dec 2006 00:03:23 +0000 (UTC) (envelope-from jan@digitaldaemon.com) Received: from digitaldaemon.com (digitaldaemon.com [63.105.9.34]) by mx1.freebsd.org (Postfix) with SMTP id 2026713C48C for ; Wed, 27 Dec 2006 00:03:19 +0000 (UTC) (envelope-from jan@digitaldaemon.com) Received: (qmail 2421 invoked by uid 98); 27 Dec 2006 00:03:07 -0000 Received: from 63.105.9.34 by digitaldaemon.com (envelope-from , uid 89) with qmail-scanner-1.25 (clamdscan: 0.87/1195. Clear:RC:1(63.105.9.34):. Processed in 0.084973 secs); 27 Dec 2006 00:03:07 -0000 X-Qmail-Scanner-Mail-From: jan@digitaldaemon.com via digitaldaemon.com X-Qmail-Scanner: 1.25 (Clear:RC:1(63.105.9.34):. Processed in 0.084973 secs) Received: from digitaldaemon.com (HELO ?160.63.102.2?) (63.105.9.34) by digitaldaemon.com with SMTP; 27 Dec 2006 00:03:06 -0000 Message-ID: <4591B834.2040200@digitaldaemon.com> Date: Tue, 26 Dec 2006 19:03:00 -0500 From: Jan Knepper User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Tim McCullagh References: <45918F6E.90006@digitaldaemon.com> <004c01c7293b$d5e03b40$6500a8c0@laptopt> In-Reply-To: <004c01c7293b$d5e03b40$6500a8c0@laptopt> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD ISP Subject: Re: 6.1-RELEASE / 6.2 Kernel Crash... X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Dec 2006 00:03:23 -0000 Hmmm... I put that in for now... but does that not mean you basically disabled SMP as well? I thought (could be wrong) that SMP required APCI to be active? When you run "top" does it display with process runs on CPU 0/1? Thanks! Jan Tim McCullagh wrote: > Hi Jan > > try editing your loader.conf > > I had a similar sounding issue. As soon as I did the following the > system became stable immediately. It was also on a Tyan Mainboard, > although with dual Xeon's > > # vi /boot/loader.conf > hint.apic.0.disabled="1" > > > Regards > > Tim > ----- Original Message ----- From: "Jan Knepper" > To: "FreeBSD ISP" ; "FreeBSD Hackers" > > Sent: Wednesday, December 27, 2006 7:09 AM > Subject: 6.1-RELEASE / 6.2 Kernel Crash... > > >> All, (sorry for the cross post) >> >> Something goofy is going on with a 6.x kernel. >> >> Dual Opteron Server (Tyan motherboard). 2 GB RAM... 2 x 256 GB SATA >> HD's. >> Just upgraded this machine from FreeBSD 5.5-STABLE to 6.2RC# and than >> down to 6.1-RELEASE. >> For some reason FreeBSD 6.1 seems to be very unstable. I use a custom >> kernel, (most devices not present in the system have been removed). >> >> When I create an SMP kernel after an undefined about of time which I >> have seen varying from 5 minutes up to about 6 hours the kernel will >> just hang. Things that seem to accelerate/aggrevate this are running >> CVSup from a repository on the same system. >> Something else that seems to push it is dd if=/dev/ad4 if=/dev/ad6 >> bs=64m (copying the master disk to the supposed slave, however geom >> is not active and module geom_mirror is not loaded! >> >> When I take SMP out of the kernel config and rebuild and install >> instead of hanging, the system seems to crash and reboot when I >> perform the same action. >> >> Also... When I first upgraded I did get an error during boot: >> kernel: module_register_init: MOD_LOAD (amr_linux, >> 0xffffffff805db120, 0) error 6 >> I disabled device amr (under RAID controllers) in the kernel config >> which took care of this. >> >> Following the bootlog. If any of you had any idea what the problem >> might be I definitely would like to know. >> >> Thanks! >> Jan >> >> >> >> syslogd: kernel boot file is /boot/kernel/kernel >> kernel: Copyright (c) 1992-2006 The FreeBSD Project. >> kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, >> 1993, 1994 >> kernel: The Regents of the University of California. All rights >> reserved. >> kernel: FreeBSD 6.1-RELEASE #4: Tue Dec 26 12:03:35 EST 2006 >> kernel: root@digitaldaemon.com:/usr/src/sys/amd64/compile/digitaldaemon >> kernel: Timecounter "i8254" frequency 1193182 Hz quality 0 >> kernel: CPU: AMD Opteron(tm) Processor 246 (1993.53-MHz K8-class CPU) >> kernel: Origin = "AuthenticAMD" Id = 0xf5a Stepping = 10 >> kernel: >> Features=0x78bfbff >> >> kernel: AMD Features=0xe0500800 >> kernel: real memory = 2147418112 (2047 MB) >> kernel: avail memory = 2065596416 (1969 MB) >> kernel: ACPI APIC Table: >> kernel: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs >> kernel: cpu0 (BSP): APIC ID: 0 >> kernel: cpu1 (AP): APIC ID: 1 >> kernel: MADT: Forcing active-low polarity and level trigger for SCI >> kernel: ioapic0 irqs 0-23 on motherboard >> kernel: ioapic1 irqs 24-27 on motherboard >> kernel: ioapic2 irqs 28-31 on motherboard >> kernel: netsmb_dev: loaded >> kernel: acpi0: on motherboard >> kernel: acpi0: Power Button (fixed) >> kernel: Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 >> kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0x5008-0x500b >> on acpi0 >> kernel: cpu0: on acpi0 >> kernel: acpi_throttle0: on cpu0 >> kernel: cpu1: on acpi0 >> kernel: pcib0: port 0xcf8-0xcff on acpi0 >> kernel: pci0: on pcib0 >> kernel: pcib1: at device 6.0 on pci0 >> kernel: pci3: on pcib1 >> kernel: ohci0: mem >> 0xff3fd000-0xff3fdfff irq 19 at device 0.0 on pci3 >> kernel: ohci0: [GIANT-LOCKED] >> kernel: usb0: OHCI version 1.0, legacy support >> kernel: usb0: on ohci0 >> kernel: usb0: USB revision 1.0 >> kernel: uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 >> kernel: uhub0: 3 ports with 3 removable, self powered >> kernel: ohci1: mem >> 0xff3fe000-0xff3fefff irq 19 at device 0.1 on pci3 >> kernel: ohci1: [GIANT-LOCKED] >> kernel: usb1: OHCI version 1.0, legacy support >> kernel: usb1: on ohci1 >> kernel: usb1: USB revision 1.0 >> kernel: uhub1: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 >> kernel: uhub1: 3 ports with 3 removable, self powered >> kernel: xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0x8080-0x80ff >> mem 0xff3ff800-0xff3ff87f irq 16 at device 10.0 on pci3 >> kernel: miibus0: on xl0 >> kernel: ukphy0: on miibus0 >> kernel: ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto >> kernel: xl0: Ethernet address: 00:04:75:ad:ac:0a >> kernel: atapci0: port >> 0x8c00-0x8c07,0x8880-0x8883,0x8800-0x8807,0x8480-0x8483,0x8400-0x840f >> mem 0xff3ffc00-0xff3fffff irq 17 at device 11.0 on pci3 >> kernel: ata2: on atapci0 >> kernel: ata3: on atapci0 >> kernel: ata4: on atapci0 >> kernel: ata5: on atapci0 >> kernel: fwohci0: mem >> 0xff3ff000-0xff3ff7ff,0xff3f8000-0xff3fbfff irq 19 at device 12.0 on >> pci3 >> kernel: fwohci0: OHCI version 1.10 (ROM=1) >> kernel: fwohci0: No. of Isochronous channels is 4. >> kernel: fwohci0: EUI64 00:e0:81:00:00:30:4c:06 >> kernel: fwohci0: Phy 1394a available S400, 2 ports. >> kernel: fwohci0: Link S400, max_rec 2048 bytes. >> kernel: firewire0: on fwohci0 >> kernel: fwe0: on firewire0 >> kernel: if_fwe0: Fake Ethernet address: 02:e0:81:30:4c:06 >> kernel: fwe0: Ethernet address: 02:e0:81:30:4c:06 >> kernel: fwe0: if_start running deferred for Giant >> kernel: sbp0: on firewire0 >> kernel: fwohci0: Initiate bus reset >> kernel: fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode >> kernel: firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) >> kernel: firewire0: bus manager 0 (me) >> kernel: isab0: at device 7.0 on pci0 >> kernel: isa0: on isab0 >> kernel: atapci1: port >> 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 7.1 on pci0 >> kernel: ata0: on atapci1 >> kernel: ata1: on atapci1 >> kernel: pci0: at device 7.2 (no driver attached) >> kernel: pci0: at device 7.3 (no driver attached) >> kernel: pci0: at device 7.5 (no driver attached) >> kernel: pcib2: at device 10.0 on pci0 >> kernel: pci2: on pcib2 >> kernel: bge0: >> mem 0xff1f0000-0xff1fffff irq 24 at device 9.0 on pci2 >> kernel: miibus1: on bge0 >> kernel: brgphy0: on miibus1 >> kernel: brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, >> 1000baseTX, 1000baseTX-FDX, auto >> kernel: bge0: Ethernet address: 00:e0:81:2d:ee:f7 >> kernel: pci0: at device 10.1 >> (no driver attached) >> kernel: pcib3: at device 11.0 on pci0 >> kernel: pci1: on pcib3 >> kernel: pci0: at device 11.1 >> (no driver attached) >> kernel: pcib4: on acpi0 >> kernel: pci4: on pcib4 >> kernel: pcib5: at device 1.0 on pci4 >> kernel: pci5: on pcib5 >> kernel: pci5: at device 0.0 (no driver attached) >> kernel: pci5: at device 0.1 (no driver attached) >> kernel: acpi_button0: on acpi0 >> kernel: atkbdc0: port 0x60,0x64 irq 1 >> on acpi0 >> kernel: atkbd0: irq 1 on atkbdc0 >> kernel: kbd0 at atkbd0 >> kernel: atkbd0: [GIANT-LOCKED] >> kernel: psm0: irq 12 on atkbdc0 >> kernel: psm0: [GIANT-LOCKED] >> kernel: psm0: model IntelliMouse Explorer, device ID 4 >> kernel: sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 >> flags 0x10 on acpi0 >> kernel: sio0: type 16550A >> kernel: sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on >> acpi0 >> kernel: sio1: type 16550A >> kernel: fdc0: port 0x3f0-0x3f5,0x3f7 >> irq 6 drq 2 on acpi0 >> kernel: fdc0: [FAST] >> kernel: ppc0: port 0x378-0x37f irq 7 >> on acpi0 >> kernel: ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode >> kernel: ppbus0: on ppc0 >> kernel: orm0: at iomem >> 0xc0000-0xccfff,0xcd000-0xd17ff,0xd1800-0xd1fff,0 >> xd2000-0xd2fff on isa0 >> kernel: sc0: at flags 0x100 on isa0 >> kernel: sc0: VGA <16 virtual consoles, flags=0x300> >> kernel: vga0: at port 0x3c0-0x3df iomem >> 0xa0000-0xbffff on isa0 >> kernel: ugen0: American Power Conversion Back-UPS RS 1500 FW:8.g9 .D >> USB FW:g9, rev 1.10/1.06, addr 2 >> kernel: Timecounters tick every 1.000 msec >> kernel: ipfw2 (+ipv6) initialized, divert loadable, rule-based >> forwarding enabled, default to deny, logging limited to 100 >> packets/entry by default >> kernel: acd0: DVDR at ata0-master UDMA33 >> kernel: ad4: 238475MB at ata2-master SATA150 >> kernel: ad6: 238475MB at ata3-master SATA150 >> kernel: SMP: AP CPU #1 Launched! >> kernel: Trying to mount root from ufs:/dev/ad4s1a >> >> _______________________________________________ >> freebsd-isp@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-isp >> To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org" >> > > _______________________________________________ > freebsd-isp@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-isp > To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org" > > From owner-freebsd-isp@FreeBSD.ORG Wed Dec 27 01:24:30 2006 Return-Path: X-Original-To: FreeBSD-ISP@FreeBSD.org Delivered-To: FreeBSD-ISP@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EB84916A412 for ; Wed, 27 Dec 2006 01:24:30 +0000 (UTC) (envelope-from jan@digitaldaemon.com) Received: from digitaldaemon.com (digitaldaemon.com [63.105.9.34]) by mx1.freebsd.org (Postfix) with SMTP id F3E3413C46F for ; Wed, 27 Dec 2006 01:24:28 +0000 (UTC) (envelope-from jan@digitaldaemon.com) Received: (qmail 2439 invoked by uid 98); 27 Dec 2006 01:24:19 -0000 Received: from 63.105.9.34 by digitaldaemon.com (envelope-from , uid 89) with qmail-scanner-1.25 (clamdscan: 0.87/1195. Clear:RC:1(63.105.9.34):. Processed in 0.07042 secs); 27 Dec 2006 01:24:19 -0000 X-Qmail-Scanner-Mail-From: jan@digitaldaemon.com via digitaldaemon.com X-Qmail-Scanner: 1.25 (Clear:RC:1(63.105.9.34):. Processed in 0.07042 secs) Received: from digitaldaemon.com (HELO ?16.81.102.2?) (63.105.9.34) by digitaldaemon.com with SMTP; 27 Dec 2006 01:24:19 -0000 Message-ID: <4591CB3C.1060902@digitaldaemon.com> Date: Tue, 26 Dec 2006 20:24:12 -0500 From: Jan Knepper User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Tim McCullagh , FreeBSD ISP , FreeBSD Hackers References: <45918F6E.90006@digitaldaemon.com> <004c01c7293b$d5e03b40$6500a8c0@laptopt> In-Reply-To: <004c01c7293b$d5e03b40$6500a8c0@laptopt> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: 6.1-RELEASE / 6.2 Kernel Crash... X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Dec 2006 01:24:31 -0000 Tried that and started dd if=/dev/ad4 if=/dev/ad6 bs=1m Kernel went in panic and automatic reboot in about an hour... It gets worse... when it does reboot the disk drive will not show in the BIOS, nor does FreeBSD recognize it during boot. The system actually has to be turned off to reset the drive... This is bad... Any other suggestions? Thanks! Jan Tim McCullagh wrote: > Hi Jan > > try editing your loader.conf > > I had a similar sounding issue. As soon as I did the following the > system became stable immediately. It was also on a Tyan Mainboard, > although with dual Xeon's > > # vi /boot/loader.conf > hint.apic.0.disabled="1" > > > Regards > > Tim > ----- Original Message ----- From: "Jan Knepper" > To: "FreeBSD ISP" ; "FreeBSD Hackers" > > Sent: Wednesday, December 27, 2006 7:09 AM > Subject: 6.1-RELEASE / 6.2 Kernel Crash... > > >> All, (sorry for the cross post) >> >> Something goofy is going on with a 6.x kernel. >> >> Dual Opteron Server (Tyan motherboard). 2 GB RAM... 2 x 256 GB SATA >> HD's. >> Just upgraded this machine from FreeBSD 5.5-STABLE to 6.2RC# and than >> down to 6.1-RELEASE. >> For some reason FreeBSD 6.1 seems to be very unstable. I use a custom >> kernel, (most devices not present in the system have been removed). >> >> When I create an SMP kernel after an undefined about of time which I >> have seen varying from 5 minutes up to about 6 hours the kernel will >> just hang. Things that seem to accelerate/aggrevate this are running >> CVSup from a repository on the same system. >> Something else that seems to push it is dd if=/dev/ad4 if=/dev/ad6 >> bs=64m (copying the master disk to the supposed slave, however geom >> is not active and module geom_mirror is not loaded! >> >> When I take SMP out of the kernel config and rebuild and install >> instead of hanging, the system seems to crash and reboot when I >> perform the same action. >> >> Also... When I first upgraded I did get an error during boot: >> kernel: module_register_init: MOD_LOAD (amr_linux, >> 0xffffffff805db120, 0) error 6 >> I disabled device amr (under RAID controllers) in the kernel config >> which took care of this. >> >> Following the bootlog. If any of you had any idea what the problem >> might be I definitely would like to know. >> >> Thanks! >> Jan >> >> >> >> syslogd: kernel boot file is /boot/kernel/kernel >> kernel: Copyright (c) 1992-2006 The FreeBSD Project. >> kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, >> 1993, 1994 >> kernel: The Regents of the University of California. All rights >> reserved. >> kernel: FreeBSD 6.1-RELEASE #4: Tue Dec 26 12:03:35 EST 2006 >> kernel: root@digitaldaemon.com:/usr/src/sys/amd64/compile/digitaldaemon >> kernel: Timecounter "i8254" frequency 1193182 Hz quality 0 >> kernel: CPU: AMD Opteron(tm) Processor 246 (1993.53-MHz K8-class CPU) >> kernel: Origin = "AuthenticAMD" Id = 0xf5a Stepping = 10 >> kernel: >> Features=0x78bfbff >> >> kernel: AMD Features=0xe0500800 >> kernel: real memory = 2147418112 (2047 MB) >> kernel: avail memory = 2065596416 (1969 MB) >> kernel: ACPI APIC Table: >> kernel: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs >> kernel: cpu0 (BSP): APIC ID: 0 >> kernel: cpu1 (AP): APIC ID: 1 >> kernel: MADT: Forcing active-low polarity and level trigger for SCI >> kernel: ioapic0 irqs 0-23 on motherboard >> kernel: ioapic1 irqs 24-27 on motherboard >> kernel: ioapic2 irqs 28-31 on motherboard >> kernel: netsmb_dev: loaded >> kernel: acpi0: on motherboard >> kernel: acpi0: Power Button (fixed) >> kernel: Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 >> kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0x5008-0x500b >> on acpi0 >> kernel: cpu0: on acpi0 >> kernel: acpi_throttle0: on cpu0 >> kernel: cpu1: on acpi0 >> kernel: pcib0: port 0xcf8-0xcff on acpi0 >> kernel: pci0: on pcib0 >> kernel: pcib1: at device 6.0 on pci0 >> kernel: pci3: on pcib1 >> kernel: ohci0: mem >> 0xff3fd000-0xff3fdfff irq 19 at device 0.0 on pci3 >> kernel: ohci0: [GIANT-LOCKED] >> kernel: usb0: OHCI version 1.0, legacy support >> kernel: usb0: on ohci0 >> kernel: usb0: USB revision 1.0 >> kernel: uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 >> kernel: uhub0: 3 ports with 3 removable, self powered >> kernel: ohci1: mem >> 0xff3fe000-0xff3fefff irq 19 at device 0.1 on pci3 >> kernel: ohci1: [GIANT-LOCKED] >> kernel: usb1: OHCI version 1.0, legacy support >> kernel: usb1: on ohci1 >> kernel: usb1: USB revision 1.0 >> kernel: uhub1: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 >> kernel: uhub1: 3 ports with 3 removable, self powered >> kernel: xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0x8080-0x80ff >> mem 0xff3ff800-0xff3ff87f irq 16 at device 10.0 on pci3 >> kernel: miibus0: on xl0 >> kernel: ukphy0: on miibus0 >> kernel: ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto >> kernel: xl0: Ethernet address: 00:04:75:ad:ac:0a >> kernel: atapci0: port >> 0x8c00-0x8c07,0x8880-0x8883,0x8800-0x8807,0x8480-0x8483,0x8400-0x840f >> mem 0xff3ffc00-0xff3fffff irq 17 at device 11.0 on pci3 >> kernel: ata2: on atapci0 >> kernel: ata3: on atapci0 >> kernel: ata4: on atapci0 >> kernel: ata5: on atapci0 >> kernel: fwohci0: mem >> 0xff3ff000-0xff3ff7ff,0xff3f8000-0xff3fbfff irq 19 at device 12.0 on >> pci3 >> kernel: fwohci0: OHCI version 1.10 (ROM=1) >> kernel: fwohci0: No. of Isochronous channels is 4. >> kernel: fwohci0: EUI64 00:e0:81:00:00:30:4c:06 >> kernel: fwohci0: Phy 1394a available S400, 2 ports. >> kernel: fwohci0: Link S400, max_rec 2048 bytes. >> kernel: firewire0: on fwohci0 >> kernel: fwe0: on firewire0 >> kernel: if_fwe0: Fake Ethernet address: 02:e0:81:30:4c:06 >> kernel: fwe0: Ethernet address: 02:e0:81:30:4c:06 >> kernel: fwe0: if_start running deferred for Giant >> kernel: sbp0: on firewire0 >> kernel: fwohci0: Initiate bus reset >> kernel: fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode >> kernel: firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) >> kernel: firewire0: bus manager 0 (me) >> kernel: isab0: at device 7.0 on pci0 >> kernel: isa0: on isab0 >> kernel: atapci1: port >> 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 7.1 on pci0 >> kernel: ata0: on atapci1 >> kernel: ata1: on atapci1 >> kernel: pci0: at device 7.2 (no driver attached) >> kernel: pci0: at device 7.3 (no driver attached) >> kernel: pci0: at device 7.5 (no driver attached) >> kernel: pcib2: at device 10.0 on pci0 >> kernel: pci2: on pcib2 >> kernel: bge0: >> mem 0xff1f0000-0xff1fffff irq 24 at device 9.0 on pci2 >> kernel: miibus1: on bge0 >> kernel: brgphy0: on miibus1 >> kernel: brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, >> 1000baseTX, 1000baseTX-FDX, auto >> kernel: bge0: Ethernet address: 00:e0:81:2d:ee:f7 >> kernel: pci0: at device 10.1 >> (no driver attached) >> kernel: pcib3: at device 11.0 on pci0 >> kernel: pci1: on pcib3 >> kernel: pci0: at device 11.1 >> (no driver attached) >> kernel: pcib4: on acpi0 >> kernel: pci4: on pcib4 >> kernel: pcib5: at device 1.0 on pci4 >> kernel: pci5: on pcib5 >> kernel: pci5: at device 0.0 (no driver attached) >> kernel: pci5: at device 0.1 (no driver attached) >> kernel: acpi_button0: on acpi0 >> kernel: atkbdc0: port 0x60,0x64 irq 1 >> on acpi0 >> kernel: atkbd0: irq 1 on atkbdc0 >> kernel: kbd0 at atkbd0 >> kernel: atkbd0: [GIANT-LOCKED] >> kernel: psm0: irq 12 on atkbdc0 >> kernel: psm0: [GIANT-LOCKED] >> kernel: psm0: model IntelliMouse Explorer, device ID 4 >> kernel: sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 >> flags 0x10 on acpi0 >> kernel: sio0: type 16550A >> kernel: sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on >> acpi0 >> kernel: sio1: type 16550A >> kernel: fdc0: port 0x3f0-0x3f5,0x3f7 >> irq 6 drq 2 on acpi0 >> kernel: fdc0: [FAST] >> kernel: ppc0: port 0x378-0x37f irq 7 >> on acpi0 >> kernel: ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode >> kernel: ppbus0: on ppc0 >> kernel: orm0: at iomem >> 0xc0000-0xccfff,0xcd000-0xd17ff,0xd1800-0xd1fff,0 >> xd2000-0xd2fff on isa0 >> kernel: sc0: at flags 0x100 on isa0 >> kernel: sc0: VGA <16 virtual consoles, flags=0x300> >> kernel: vga0: at port 0x3c0-0x3df iomem >> 0xa0000-0xbffff on isa0 >> kernel: ugen0: American Power Conversion Back-UPS RS 1500 FW:8.g9 .D >> USB FW:g9, rev 1.10/1.06, addr 2 >> kernel: Timecounters tick every 1.000 msec >> kernel: ipfw2 (+ipv6) initialized, divert loadable, rule-based >> forwarding enabled, default to deny, logging limited to 100 >> packets/entry by default >> kernel: acd0: DVDR at ata0-master UDMA33 >> kernel: ad4: 238475MB at ata2-master SATA150 >> kernel: ad6: 238475MB at ata3-master SATA150 >> kernel: SMP: AP CPU #1 Launched! >> kernel: Trying to mount root from ufs:/dev/ad4s1a >> >> _______________________________________________ >> freebsd-isp@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-isp >> To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org" >> > > _______________________________________________ > freebsd-isp@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-isp > To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org" > > From owner-freebsd-isp@FreeBSD.ORG Wed Dec 27 02:34:52 2006 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 34D3D16A40F for ; Wed, 27 Dec 2006 02:34:52 +0000 (UTC) (envelope-from mario@schmut.com) Received: from mail.schmut.com (mail.schmut.com [66.92.49.2]) by mx1.freebsd.org (Postfix) with SMTP id 03AE913C47C for ; Wed, 27 Dec 2006 02:34:51 +0000 (UTC) (envelope-from mario@schmut.com) Received: (qmail 90325 invoked by uid 89); 27 Dec 2006 02:08:10 -0000 Received: from perkyw.schmut.com (192.168.223.4) by snoopy.schmut.com (tmda-ofmipd) with ESMTP; Tue, 26 Dec 2006 18:08:09 -0800 To: freebsd-isp@freebsd.org Date: Tue, 26 Dec 2006 18:08:08 -0800 User-Agent: KMail/1.8.3 References: <45918F6E.90006@digitaldaemon.com> <004c01c7293b$d5e03b40$6500a8c0@laptopt> <4591CB3C.1060902@digitaldaemon.com> In-Reply-To: <4591CB3C.1060902@digitaldaemon.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200612261808.08984.mario@schmut.com> X-Delivery-Agent: TMDA/1.1.5 (Fettercairn) From: Mario Theodoridis X-Primary-Address: mario@schmut.com Cc: Tim McCullagh , FreeBSD Hackers , Jan Knepper Subject: Re: 6.1-RELEASE / 6.2 Kernel Crash... X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Mario Theodoridis List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Dec 2006 02:34:52 -0000 is it just me, or is this beginning to sound like hardware problems? mario;> On Tuesday 26 December 2006 17:24, Jan Knepper wrote: > Tried that and started > > dd if=/dev/ad4 if=/dev/ad6 bs=1m > > Kernel went in panic and automatic reboot in about an hour... > > It gets worse... when it does reboot the disk drive will not show in the > BIOS, nor does FreeBSD recognize it during boot. The system actually has > to be turned off to reset the drive... > > This is bad... > > Any other suggestions? > > Thanks! > Jan > > Tim McCullagh wrote: > > Hi Jan > > > > try editing your loader.conf > > > > I had a similar sounding issue. As soon as I did the following the > > system became stable immediately. It was also on a Tyan Mainboard, > > although with dual Xeon's > > > > # vi /boot/loader.conf > > hint.apic.0.disabled="1" > > > > > > Regards > > > > Tim > > ----- Original Message ----- From: "Jan Knepper" > > To: "FreeBSD ISP" ; "FreeBSD Hackers" > > > > Sent: Wednesday, December 27, 2006 7:09 AM > > Subject: 6.1-RELEASE / 6.2 Kernel Crash... > > > >> All, (sorry for the cross post) > >> > >> Something goofy is going on with a 6.x kernel. > >> > >> Dual Opteron Server (Tyan motherboard). 2 GB RAM... 2 x 256 GB SATA > >> HD's. > >> Just upgraded this machine from FreeBSD 5.5-STABLE to 6.2RC# and than > >> down to 6.1-RELEASE. > >> For some reason FreeBSD 6.1 seems to be very unstable. I use a custom > >> kernel, (most devices not present in the system have been removed). > >> > >> When I create an SMP kernel after an undefined about of time which I > >> have seen varying from 5 minutes up to about 6 hours the kernel will > >> just hang. Things that seem to accelerate/aggrevate this are running > >> CVSup from a repository on the same system. > >> Something else that seems to push it is dd if=/dev/ad4 if=/dev/ad6 > >> bs=64m (copying the master disk to the supposed slave, however geom > >> is not active and module geom_mirror is not loaded! > >> > >> When I take SMP out of the kernel config and rebuild and install > >> instead of hanging, the system seems to crash and reboot when I > >> perform the same action. > >> > >> Also... When I first upgraded I did get an error during boot: > >> kernel: module_register_init: MOD_LOAD (amr_linux, > >> 0xffffffff805db120, 0) error 6 > >> I disabled device amr (under RAID controllers) in the kernel config > >> which took care of this. > >> > >> Following the bootlog. If any of you had any idea what the problem > >> might be I definitely would like to know. > >> > >> Thanks! > >> Jan > >> > >> > >> > >> syslogd: kernel boot file is /boot/kernel/kernel > >> kernel: Copyright (c) 1992-2006 The FreeBSD Project. > >> kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, > >> 1993, 1994 > >> kernel: The Regents of the University of California. All rights > >> reserved. > >> kernel: FreeBSD 6.1-RELEASE #4: Tue Dec 26 12:03:35 EST 2006 > >> kernel: root@digitaldaemon.com:/usr/src/sys/amd64/compile/digitaldaemon > >> kernel: Timecounter "i8254" frequency 1193182 Hz quality 0 > >> kernel: CPU: AMD Opteron(tm) Processor 246 (1993.53-MHz K8-class CPU) > >> kernel: Origin = "AuthenticAMD" Id = 0xf5a Stepping = 10 > >> kernel: > >> Features=0x78bfbff >>MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2> > >> > >> kernel: AMD Features=0xe0500800 > >> kernel: real memory = 2147418112 (2047 MB) > >> kernel: avail memory = 2065596416 (1969 MB) > >> kernel: ACPI APIC Table: > >> kernel: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > >> kernel: cpu0 (BSP): APIC ID: 0 > >> kernel: cpu1 (AP): APIC ID: 1 > >> kernel: MADT: Forcing active-low polarity and level trigger for SCI > >> kernel: ioapic0 irqs 0-23 on motherboard > >> kernel: ioapic1 irqs 24-27 on motherboard > >> kernel: ioapic2 irqs 28-31 on motherboard > >> kernel: netsmb_dev: loaded > >> kernel: acpi0: on motherboard > >> kernel: acpi0: Power Button (fixed) > >> kernel: Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > >> kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0x5008-0x500b > >> on acpi0 > >> kernel: cpu0: on acpi0 > >> kernel: acpi_throttle0: on cpu0 > >> kernel: cpu1: on acpi0 > >> kernel: pcib0: port 0xcf8-0xcff on acpi0 > >> kernel: pci0: on pcib0 > >> kernel: pcib1: at device 6.0 on pci0 > >> kernel: pci3: on pcib1 > >> kernel: ohci0: mem > >> 0xff3fd000-0xff3fdfff irq 19 at device 0.0 on pci3 > >> kernel: ohci0: [GIANT-LOCKED] > >> kernel: usb0: OHCI version 1.0, legacy support > >> kernel: usb0: on ohci0 > >> kernel: usb0: USB revision 1.0 > >> kernel: uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > >> kernel: uhub0: 3 ports with 3 removable, self powered > >> kernel: ohci1: mem > >> 0xff3fe000-0xff3fefff irq 19 at device 0.1 on pci3 > >> kernel: ohci1: [GIANT-LOCKED] > >> kernel: usb1: OHCI version 1.0, legacy support > >> kernel: usb1: on ohci1 > >> kernel: usb1: USB revision 1.0 > >> kernel: uhub1: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > >> kernel: uhub1: 3 ports with 3 removable, self powered > >> kernel: xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0x8080-0x80ff > >> mem 0xff3ff800-0xff3ff87f irq 16 at device 10.0 on pci3 > >> kernel: miibus0: on xl0 > >> kernel: ukphy0: on miibus0 > >> kernel: ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > >> kernel: xl0: Ethernet address: 00:04:75:ad:ac:0a > >> kernel: atapci0: port > >> 0x8c00-0x8c07,0x8880-0x8883,0x8800-0x8807,0x8480-0x8483,0x8400-0x840f > >> mem 0xff3ffc00-0xff3fffff irq 17 at device 11.0 on pci3 > >> kernel: ata2: on atapci0 > >> kernel: ata3: on atapci0 > >> kernel: ata4: on atapci0 > >> kernel: ata5: on atapci0 > >> kernel: fwohci0: mem > >> 0xff3ff000-0xff3ff7ff,0xff3f8000-0xff3fbfff irq 19 at device 12.0 on > >> pci3 > >> kernel: fwohci0: OHCI version 1.10 (ROM=1) > >> kernel: fwohci0: No. of Isochronous channels is 4. > >> kernel: fwohci0: EUI64 00:e0:81:00:00:30:4c:06 > >> kernel: fwohci0: Phy 1394a available S400, 2 ports. > >> kernel: fwohci0: Link S400, max_rec 2048 bytes. > >> kernel: firewire0: on fwohci0 > >> kernel: fwe0: on firewire0 > >> kernel: if_fwe0: Fake Ethernet address: 02:e0:81:30:4c:06 > >> kernel: fwe0: Ethernet address: 02:e0:81:30:4c:06 > >> kernel: fwe0: if_start running deferred for Giant > >> kernel: sbp0: on firewire0 > >> kernel: fwohci0: Initiate bus reset > >> kernel: fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode > >> kernel: firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) > >> kernel: firewire0: bus manager 0 (me) > >> kernel: isab0: at device 7.0 on pci0 > >> kernel: isa0: on isab0 > >> kernel: atapci1: port > >> 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 7.1 on pci0 > >> kernel: ata0: on atapci1 > >> kernel: ata1: on atapci1 > >> kernel: pci0: at device 7.2 (no driver attached) > >> kernel: pci0: at device 7.3 (no driver attached) > >> kernel: pci0: at device 7.5 (no driver attached) > >> kernel: pcib2: at device 10.0 on pci0 > >> kernel: pci2: on pcib2 > >> kernel: bge0: > >> mem 0xff1f0000-0xff1fffff irq 24 at device 9.0 on pci2 > >> kernel: miibus1: on bge0 > >> kernel: brgphy0: on miibus1 > >> kernel: brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, > >> 1000baseTX, 1000baseTX-FDX, auto > >> kernel: bge0: Ethernet address: 00:e0:81:2d:ee:f7 > >> kernel: pci0: at device 10.1 > >> (no driver attached) > >> kernel: pcib3: at device 11.0 on pci0 > >> kernel: pci1: on pcib3 > >> kernel: pci0: at device 11.1 > >> (no driver attached) > >> kernel: pcib4: on acpi0 > >> kernel: pci4: on pcib4 > >> kernel: pcib5: at device 1.0 on pci4 > >> kernel: pci5: on pcib5 > >> kernel: pci5: at device 0.0 (no driver attached) > >> kernel: pci5: at device 0.1 (no driver attached) > >> kernel: acpi_button0: on acpi0 > >> kernel: atkbdc0: port 0x60,0x64 irq 1 > >> on acpi0 > >> kernel: atkbd0: irq 1 on atkbdc0 > >> kernel: kbd0 at atkbd0 > >> kernel: atkbd0: [GIANT-LOCKED] > >> kernel: psm0: irq 12 on atkbdc0 > >> kernel: psm0: [GIANT-LOCKED] > >> kernel: psm0: model IntelliMouse Explorer, device ID 4 > >> kernel: sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 > >> flags 0x10 on acpi0 > >> kernel: sio0: type 16550A > >> kernel: sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on > >> acpi0 > >> kernel: sio1: type 16550A > >> kernel: fdc0: port 0x3f0-0x3f5,0x3f7 > >> irq 6 drq 2 on acpi0 > >> kernel: fdc0: [FAST] > >> kernel: ppc0: port 0x378-0x37f irq 7 > >> on acpi0 > >> kernel: ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode > >> kernel: ppbus0: on ppc0 > >> kernel: orm0: at iomem > >> 0xc0000-0xccfff,0xcd000-0xd17ff,0xd1800-0xd1fff,0 > >> xd2000-0xd2fff on isa0 > >> kernel: sc0: at flags 0x100 on isa0 > >> kernel: sc0: VGA <16 virtual consoles, flags=0x300> > >> kernel: vga0: at port 0x3c0-0x3df iomem > >> 0xa0000-0xbffff on isa0 > >> kernel: ugen0: American Power Conversion Back-UPS RS 1500 FW:8.g9 .D > >> USB FW:g9, rev 1.10/1.06, addr 2 > >> kernel: Timecounters tick every 1.000 msec > >> kernel: ipfw2 (+ipv6) initialized, divert loadable, rule-based > >> forwarding enabled, default to deny, logging limited to 100 > >> packets/entry by default > >> kernel: acd0: DVDR at ata0-master UDMA33 > >> kernel: ad4: 238475MB at ata2-master SATA150 > >> kernel: ad6: 238475MB at ata3-master SATA150 > >> kernel: SMP: AP CPU #1 Launched! > >> kernel: Trying to mount root from ufs:/dev/ad4s1a > >> > >> _______________________________________________ > >> freebsd-isp@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-isp > >> To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org" > > > > _______________________________________________ > > freebsd-isp@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-isp > > To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org" > > _______________________________________________ > freebsd-isp@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-isp > To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org" From owner-freebsd-isp@FreeBSD.ORG Wed Dec 27 03:37:43 2006 Return-Path: X-Original-To: FreeBSD-ISP@FreeBSD.org Delivered-To: FreeBSD-ISP@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1389516A407; Wed, 27 Dec 2006 03:37:43 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id F3EAC13C48A; Wed, 27 Dec 2006 03:37:42 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id CE9571A3C1C; Tue, 26 Dec 2006 19:37:42 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 3CE87513F2; Tue, 26 Dec 2006 22:37:42 -0500 (EST) Date: Tue, 26 Dec 2006 22:37:42 -0500 From: Kris Kennaway To: Jan Knepper Message-ID: <20061227033742.GA9706@xor.obsecurity.org> References: <45918F6E.90006@digitaldaemon.com> <004c01c7293b$d5e03b40$6500a8c0@laptopt> <4591CB3C.1060902@digitaldaemon.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="3MwIy2ne0vdjdPXF" Content-Disposition: inline In-Reply-To: <4591CB3C.1060902@digitaldaemon.com> User-Agent: Mutt/1.4.2.2i Cc: Tim McCullagh , FreeBSD ISP , FreeBSD Hackers Subject: Re: 6.1-RELEASE / 6.2 Kernel Crash... X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Dec 2006 03:37:43 -0000 --3MwIy2ne0vdjdPXF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Dec 26, 2006 at 08:24:12PM -0500, Jan Knepper wrote: > Tried that and started >=20 > dd if=3D/dev/ad4 if=3D/dev/ad6 bs=3D1m >=20 > Kernel went in panic and automatic reboot in about an hour... >=20 > It gets worse... when it does reboot the disk drive will not show in the= =20 > BIOS, nor does FreeBSD recognize it during boot. The system actually has= =20 > to be turned off to reset the drive... >=20 > This is bad... >=20 > Any other suggestions? Sounds like a bug in the support for your ATA hardware, or your hardware is broken. The very least you'll need to do is to obtain a crashdump and debugging backtrace (see the developers handbook) and CC it to sos@ Kris --3MwIy2ne0vdjdPXF Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFkeqFWry0BWjoQKURAqP9AKC5e35lRbzZFYXzEul7PHfaO+kpggCbBBar dCe1/AwKwvaRXB3DRWpbsVY= =UpcX -----END PGP SIGNATURE----- --3MwIy2ne0vdjdPXF-- From owner-freebsd-isp@FreeBSD.ORG Wed Dec 27 07:08:42 2006 Return-Path: X-Original-To: FreeBSD-ISP@FreeBSD.org Delivered-To: FreeBSD-ISP@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6648F16A403 for ; Wed, 27 Dec 2006 07:08:42 +0000 (UTC) (envelope-from john@day-light.com) Received: from joseph.day-light.net (gabriel.day-light.net [209.145.160.141]) by mx1.freebsd.org (Postfix) with ESMTP id 7C71F13C46F for ; Wed, 27 Dec 2006 07:08:41 +0000 (UTC) (envelope-from john@day-light.com) Received: from w1 (w1 [10.1.5.201]) by joseph.day-light.net (Postfix) with SMTP id 2910A4F3E2; Wed, 27 Dec 2006 00:37:52 -0600 (CST) From: "John Brooks" To: "Jan Knepper" , "FreeBSD ISP" Date: Wed, 27 Dec 2006 00:37:53 -0600 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: <4591CB3C.1060902@digitaldaemon.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Importance: Normal Cc: Subject: RE: 6.1-RELEASE / 6.2 Kernel Crash... X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: john@day-light.com List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Dec 2006 07:08:42 -0000 > dd if=/dev/ad4 if=/dev/ad6 bs=1m shouldn't that be: dd if=/dev/ad4 of=/dev/ad6 bs=1m ^ just curious... -- John Brooks john@day-light.com > -----Original Message----- > From: owner-freebsd-isp@freebsd.org > [mailto:owner-freebsd-isp@freebsd.org]On Behalf Of Jan Knepper > Sent: Tuesday, December 26, 2006 7:24 PM > To: Tim McCullagh; FreeBSD ISP; FreeBSD Hackers > Subject: Re: 6.1-RELEASE / 6.2 Kernel Crash... > > > Tried that and started > > dd if=/dev/ad4 if=/dev/ad6 bs=1m > > Kernel went in panic and automatic reboot in about an hour... > > It gets worse... when it does reboot the disk drive will not show in the > BIOS, nor does FreeBSD recognize it during boot. The system actually has > to be turned off to reset the drive... > > This is bad... > > Any other suggestions? > > Thanks! > Jan > > From owner-freebsd-isp@FreeBSD.ORG Wed Dec 27 07:21:11 2006 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 43FB016A403 for ; Wed, 27 Dec 2006 07:21:11 +0000 (UTC) (envelope-from tim@halenet.com.au) Received: from helen.halenet.com.au (helen.halenet.com.au [203.55.33.243]) by mx1.freebsd.org (Postfix) with ESMTP id E7E9A13C475 for ; Wed, 27 Dec 2006 07:21:10 +0000 (UTC) (envelope-from tim@halenet.com.au) Received: from localhost (localhost.halenet.com.au [127.0.0.1]) by helen.halenet.com.au (Postfix) with ESMTP id C130E11456; Wed, 27 Dec 2006 17:20:08 +1000 (EST) X-Virus-Scanned: amavisd-new at halenet.com.au Received: from helen.halenet.com.au ([127.0.0.1]) by localhost (helen.halenet.com.au [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2G40kwZrd1ud; Wed, 27 Dec 2006 17:20:04 +1000 (EST) Received: from laptopt (wireless-48-200.halenet.com.au [61.88.48.200]) by helen.halenet.com.au (Postfix) with SMTP id ED4641143F; Wed, 27 Dec 2006 17:19:59 +1000 (EST) Message-ID: <003601c72987$910cd6d0$6500a8c0@laptopt> From: "Tim McCullagh" To: "Jan Knepper" References: <45918F6E.90006@digitaldaemon.com><004c01c7293b$d5e03b40$6500a8c0@laptopt> <4591B834.2040200@digitaldaemon.com> Date: Wed, 27 Dec 2006 17:20:58 +1000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3028 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 Cc: freebsd-isp@freebsd.org Subject: Re: 6.1-RELEASE / 6.2 Kernel Crash... X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Dec 2006 07:21:11 -0000 Hi Jan I had to edit the loader.conf in all my newer Tyan MB based systems 6.0 6.1 releases 4.11 worked fine That didn't stop the SMP working as far as I know I suspect there is a hardware compatibility issue with the Tyan boards and FreeBSD 6.0 6.1 releases, I have been using Tyan boards for years without any trouble, however I will probably now move to Intel server boards. I will need to test one first of course Did it fix it for you.? I just checked an the last system I had trouble with and it has now been up for 36 days without any issues. Before I changed that, the system would not boot or if it did it would crash within an hour Regards Tim ----- Original Message ----- From: "Jan Knepper" To: "Tim McCullagh" Cc: "FreeBSD ISP" Sent: Wednesday, December 27, 2006 10:03 AM Subject: Re: 6.1-RELEASE / 6.2 Kernel Crash... > Hmmm... > I put that in for now... but does that not mean you basically disabled SMP > as well? > I thought (could be wrong) that SMP required APCI to be active? > When you run "top" does it display with process runs on CPU 0/1? > > Thanks! > Jan > From owner-freebsd-isp@FreeBSD.ORG Wed Dec 27 11:07:37 2006 Return-Path: X-Original-To: FreeBSD-ISP@freebsd.org Delivered-To: FreeBSD-ISP@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EA90216A407; Wed, 27 Dec 2006 11:07:37 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe07.swip.net [212.247.154.193]) by mx1.freebsd.org (Postfix) with ESMTP id 5D80513C466; Wed, 27 Dec 2006 11:07:37 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] Received: from [193.217.102.48] (account mc467741@c2i.net HELO [10.0.0.249]) by mailfe07.swip.net (CommuniGate Pro SMTP 5.0.12) with ESMTPA id 368938761; Wed, 27 Dec 2006 11:07:29 +0100 From: Hans Petter Selasky To: freebsd-hackers@freebsd.org Date: Wed, 27 Dec 2006 11:07:11 +0100 User-Agent: KMail/1.7 References: <45918F6E.90006@digitaldaemon.com> <004c01c7293b$d5e03b40$6500a8c0@laptopt> <4591CB3C.1060902@digitaldaemon.com> In-Reply-To: <4591CB3C.1060902@digitaldaemon.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200612271107.13124.hselasky@c2i.net> Cc: Tim McCullagh , FreeBSD ISP , Jan Knepper Subject: Re: 6.1-RELEASE / 6.2 Kernel Crash... X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Dec 2006 11:07:38 -0000 On Wednesday 27 December 2006 02:24, Jan Knepper wrote: > Tried that and started > > dd if=/dev/ad4 if=/dev/ad6 bs=1m > > Kernel went in panic and automatic reboot in about an hour... > > It gets worse... when it does reboot the disk drive will not show in the > BIOS, nor does FreeBSD recognize it during boot. The system actually has > to be turned off to reset the drive... > > This is bad... > > Any other suggestions? > Maybe you can setup a serial console to grab the panic message? http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/serialconsole-setup.html --HPS From owner-freebsd-isp@FreeBSD.ORG Wed Dec 27 12:37:48 2006 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4D48616A416 for ; Wed, 27 Dec 2006 12:37:48 +0000 (UTC) (envelope-from jan@digitaldaemon.com) Received: from digitaldaemon.com (digitaldaemon.com [63.105.9.34]) by mx1.freebsd.org (Postfix) with SMTP id C648013C481 for ; Wed, 27 Dec 2006 12:37:46 +0000 (UTC) (envelope-from jan@digitaldaemon.com) Received: (qmail 34647 invoked by uid 98); 27 Dec 2006 12:37:42 -0000 Received: from 63.105.9.34 by digitaldaemon.com (envelope-from , uid 89) with qmail-scanner-1.25 (clamdscan: 0.87/1195. Clear:RC:1(63.105.9.34):. Processed in 1.433789 secs); 27 Dec 2006 12:37:42 -0000 X-Qmail-Scanner-Mail-From: jan@digitaldaemon.com via digitaldaemon.com X-Qmail-Scanner: 1.25 (Clear:RC:1(63.105.9.34):. Processed in 1.433789 secs) Received: from digitaldaemon.com (HELO ?184.157.102.2?) (63.105.9.34) by digitaldaemon.com with SMTP; 27 Dec 2006 12:37:40 -0000 Message-ID: <4592690B.7080800@digitaldaemon.com> Date: Wed, 27 Dec 2006 07:37:31 -0500 From: Jan Knepper User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Mario Theodoridis References: <45918F6E.90006@digitaldaemon.com> <004c01c7293b$d5e03b40$6500a8c0@laptopt> <4591CB3C.1060902@digitaldaemon.com> <200612261808.08984.mario@schmut.com> In-Reply-To: <200612261808.08984.mario@schmut.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-isp@freebsd.org, Tim McCullagh , FreeBSD Hackers Subject: Re: 6.1-RELEASE / 6.2 Kernel Crash... X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Dec 2006 12:37:48 -0000 FreeBSD 5.x branch run on that machine for almost 2 years without a problem and magically the same time period in *hours* that I upgrade the machine I get hardware problems too? Not an impossible coincidence, but not very likely... Thanks! Jan Mario Theodoridis wrote: > is it just me, or is this beginning to sound like hardware problems? > > mario;> > > On Tuesday 26 December 2006 17:24, Jan Knepper wrote: > >> Tried that and started >> >> dd if=/dev/ad4 if=/dev/ad6 bs=1m >> >> Kernel went in panic and automatic reboot in about an hour... >> >> It gets worse... when it does reboot the disk drive will not show in the >> BIOS, nor does FreeBSD recognize it during boot. The system actually has >> to be turned off to reset the drive... >> >> This is bad... >> >> Any other suggestions? >> >> Thanks! >> Jan >> >> Tim McCullagh wrote: >> >>> Hi Jan >>> >>> try editing your loader.conf >>> >>> I had a similar sounding issue. As soon as I did the following the >>> system became stable immediately. It was also on a Tyan Mainboard, >>> although with dual Xeon's >>> >>> # vi /boot/loader.conf >>> hint.apic.0.disabled="1" >>> >>> >>> Regards >>> >>> Tim >>> ----- Original Message ----- From: "Jan Knepper" >>> To: "FreeBSD ISP" ; "FreeBSD Hackers" >>> >>> Sent: Wednesday, December 27, 2006 7:09 AM >>> Subject: 6.1-RELEASE / 6.2 Kernel Crash... >>> >>> >>>> All, (sorry for the cross post) >>>> >>>> Something goofy is going on with a 6.x kernel. >>>> >>>> Dual Opteron Server (Tyan motherboard). 2 GB RAM... 2 x 256 GB SATA >>>> HD's. >>>> Just upgraded this machine from FreeBSD 5.5-STABLE to 6.2RC# and than >>>> down to 6.1-RELEASE. >>>> For some reason FreeBSD 6.1 seems to be very unstable. I use a custom >>>> kernel, (most devices not present in the system have been removed). >>>> >>>> When I create an SMP kernel after an undefined about of time which I >>>> have seen varying from 5 minutes up to about 6 hours the kernel will >>>> just hang. Things that seem to accelerate/aggrevate this are running >>>> CVSup from a repository on the same system. >>>> Something else that seems to push it is dd if=/dev/ad4 if=/dev/ad6 >>>> bs=64m (copying the master disk to the supposed slave, however geom >>>> is not active and module geom_mirror is not loaded! >>>> >>>> When I take SMP out of the kernel config and rebuild and install >>>> instead of hanging, the system seems to crash and reboot when I >>>> perform the same action. >>>> >>>> Also... When I first upgraded I did get an error during boot: >>>> kernel: module_register_init: MOD_LOAD (amr_linux, >>>> 0xffffffff805db120, 0) error 6 >>>> I disabled device amr (under RAID controllers) in the kernel config >>>> which took care of this. >>>> >>>> Following the bootlog. If any of you had any idea what the problem >>>> might be I definitely would like to know. >>>> >>>> Thanks! >>>> Jan >>>> >>>> >>>> >>>> syslogd: kernel boot file is /boot/kernel/kernel >>>> kernel: Copyright (c) 1992-2006 The FreeBSD Project. >>>> kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, >>>> 1993, 1994 >>>> kernel: The Regents of the University of California. All rights >>>> reserved. >>>> kernel: FreeBSD 6.1-RELEASE #4: Tue Dec 26 12:03:35 EST 2006 >>>> kernel: root@digitaldaemon.com:/usr/src/sys/amd64/compile/digitaldaemon >>>> kernel: Timecounter "i8254" frequency 1193182 Hz quality 0 >>>> kernel: CPU: AMD Opteron(tm) Processor 246 (1993.53-MHz K8-class CPU) >>>> kernel: Origin = "AuthenticAMD" Id = 0xf5a Stepping = 10 >>>> kernel: >>>> Features=0x78bfbff>>> MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2> >>>> >>>> kernel: AMD Features=0xe0500800 >>>> kernel: real memory = 2147418112 (2047 MB) >>>> kernel: avail memory = 2065596416 (1969 MB) >>>> kernel: ACPI APIC Table: >>>> kernel: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs >>>> kernel: cpu0 (BSP): APIC ID: 0 >>>> kernel: cpu1 (AP): APIC ID: 1 >>>> kernel: MADT: Forcing active-low polarity and level trigger for SCI >>>> kernel: ioapic0 irqs 0-23 on motherboard >>>> kernel: ioapic1 irqs 24-27 on motherboard >>>> kernel: ioapic2 irqs 28-31 on motherboard >>>> kernel: netsmb_dev: loaded >>>> kernel: acpi0: on motherboard >>>> kernel: acpi0: Power Button (fixed) >>>> kernel: Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 >>>> kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0x5008-0x500b >>>> on acpi0 >>>> kernel: cpu0: on acpi0 >>>> kernel: acpi_throttle0: on cpu0 >>>> kernel: cpu1: on acpi0 >>>> kernel: pcib0: port 0xcf8-0xcff on acpi0 >>>> kernel: pci0: on pcib0 >>>> kernel: pcib1: at device 6.0 on pci0 >>>> kernel: pci3: on pcib1 >>>> kernel: ohci0: mem >>>> 0xff3fd000-0xff3fdfff irq 19 at device 0.0 on pci3 >>>> kernel: ohci0: [GIANT-LOCKED] >>>> kernel: usb0: OHCI version 1.0, legacy support >>>> kernel: usb0: on ohci0 >>>> kernel: usb0: USB revision 1.0 >>>> kernel: uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 >>>> kernel: uhub0: 3 ports with 3 removable, self powered >>>> kernel: ohci1: mem >>>> 0xff3fe000-0xff3fefff irq 19 at device 0.1 on pci3 >>>> kernel: ohci1: [GIANT-LOCKED] >>>> kernel: usb1: OHCI version 1.0, legacy support >>>> kernel: usb1: on ohci1 >>>> kernel: usb1: USB revision 1.0 >>>> kernel: uhub1: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 >>>> kernel: uhub1: 3 ports with 3 removable, self powered >>>> kernel: xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0x8080-0x80ff >>>> mem 0xff3ff800-0xff3ff87f irq 16 at device 10.0 on pci3 >>>> kernel: miibus0: on xl0 >>>> kernel: ukphy0: on miibus0 >>>> kernel: ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto >>>> kernel: xl0: Ethernet address: 00:04:75:ad:ac:0a >>>> kernel: atapci0: port >>>> 0x8c00-0x8c07,0x8880-0x8883,0x8800-0x8807,0x8480-0x8483,0x8400-0x840f >>>> mem 0xff3ffc00-0xff3fffff irq 17 at device 11.0 on pci3 >>>> kernel: ata2: on atapci0 >>>> kernel: ata3: on atapci0 >>>> kernel: ata4: on atapci0 >>>> kernel: ata5: on atapci0 >>>> kernel: fwohci0: mem >>>> 0xff3ff000-0xff3ff7ff,0xff3f8000-0xff3fbfff irq 19 at device 12.0 on >>>> pci3 >>>> kernel: fwohci0: OHCI version 1.10 (ROM=1) >>>> kernel: fwohci0: No. of Isochronous channels is 4. >>>> kernel: fwohci0: EUI64 00:e0:81:00:00:30:4c:06 >>>> kernel: fwohci0: Phy 1394a available S400, 2 ports. >>>> kernel: fwohci0: Link S400, max_rec 2048 bytes. >>>> kernel: firewire0: on fwohci0 >>>> kernel: fwe0: on firewire0 >>>> kernel: if_fwe0: Fake Ethernet address: 02:e0:81:30:4c:06 >>>> kernel: fwe0: Ethernet address: 02:e0:81:30:4c:06 >>>> kernel: fwe0: if_start running deferred for Giant >>>> kernel: sbp0: on firewire0 >>>> kernel: fwohci0: Initiate bus reset >>>> kernel: fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode >>>> kernel: firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) >>>> kernel: firewire0: bus manager 0 (me) >>>> kernel: isab0: at device 7.0 on pci0 >>>> kernel: isa0: on isab0 >>>> kernel: atapci1: port >>>> 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 7.1 on pci0 >>>> kernel: ata0: on atapci1 >>>> kernel: ata1: on atapci1 >>>> kernel: pci0: at device 7.2 (no driver attached) >>>> kernel: pci0: at device 7.3 (no driver attached) >>>> kernel: pci0: at device 7.5 (no driver attached) >>>> kernel: pcib2: at device 10.0 on pci0 >>>> kernel: pci2: on pcib2 >>>> kernel: bge0: >>>> mem 0xff1f0000-0xff1fffff irq 24 at device 9.0 on pci2 >>>> kernel: miibus1: on bge0 >>>> kernel: brgphy0: on miibus1 >>>> kernel: brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, >>>> 1000baseTX, 1000baseTX-FDX, auto >>>> kernel: bge0: Ethernet address: 00:e0:81:2d:ee:f7 >>>> kernel: pci0: at device 10.1 >>>> (no driver attached) >>>> kernel: pcib3: at device 11.0 on pci0 >>>> kernel: pci1: on pcib3 >>>> kernel: pci0: at device 11.1 >>>> (no driver attached) >>>> kernel: pcib4: on acpi0 >>>> kernel: pci4: on pcib4 >>>> kernel: pcib5: at device 1.0 on pci4 >>>> kernel: pci5: on pcib5 >>>> kernel: pci5: at device 0.0 (no driver attached) >>>> kernel: pci5: at device 0.1 (no driver attached) >>>> kernel: acpi_button0: on acpi0 >>>> kernel: atkbdc0: port 0x60,0x64 irq 1 >>>> on acpi0 >>>> kernel: atkbd0: irq 1 on atkbdc0 >>>> kernel: kbd0 at atkbd0 >>>> kernel: atkbd0: [GIANT-LOCKED] >>>> kernel: psm0: irq 12 on atkbdc0 >>>> kernel: psm0: [GIANT-LOCKED] >>>> kernel: psm0: model IntelliMouse Explorer, device ID 4 >>>> kernel: sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 >>>> flags 0x10 on acpi0 >>>> kernel: sio0: type 16550A >>>> kernel: sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on >>>> acpi0 >>>> kernel: sio1: type 16550A >>>> kernel: fdc0: port 0x3f0-0x3f5,0x3f7 >>>> irq 6 drq 2 on acpi0 >>>> kernel: fdc0: [FAST] >>>> kernel: ppc0: port 0x378-0x37f irq 7 >>>> on acpi0 >>>> kernel: ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode >>>> kernel: ppbus0: on ppc0 >>>> kernel: orm0: at iomem >>>> 0xc0000-0xccfff,0xcd000-0xd17ff,0xd1800-0xd1fff,0 >>>> xd2000-0xd2fff on isa0 >>>> kernel: sc0: at flags 0x100 on isa0 >>>> kernel: sc0: VGA <16 virtual consoles, flags=0x300> >>>> kernel: vga0: at port 0x3c0-0x3df iomem >>>> 0xa0000-0xbffff on isa0 >>>> kernel: ugen0: American Power Conversion Back-UPS RS 1500 FW:8.g9 .D >>>> USB FW:g9, rev 1.10/1.06, addr 2 >>>> kernel: Timecounters tick every 1.000 msec >>>> kernel: ipfw2 (+ipv6) initialized, divert loadable, rule-based >>>> forwarding enabled, default to deny, logging limited to 100 >>>> packets/entry by default >>>> kernel: acd0: DVDR at ata0-master UDMA33 >>>> kernel: ad4: 238475MB at ata2-master SATA150 >>>> kernel: ad6: 238475MB at ata3-master SATA150 >>>> kernel: SMP: AP CPU #1 Launched! >>>> kernel: Trying to mount root from ufs:/dev/ad4s1a >>>> >>>> _______________________________________________ >>>> freebsd-isp@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-isp >>>> To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org" >>>> >>> _______________________________________________ >>> freebsd-isp@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-isp >>> To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org" >>> >> _______________________________________________ >> freebsd-isp@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-isp >> To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org" >> > _______________________________________________ > freebsd-isp@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-isp > To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org" > > > From owner-freebsd-isp@FreeBSD.ORG Wed Dec 27 12:40:02 2006 Return-Path: X-Original-To: FreeBSD-ISP@FreeBSD.org Delivered-To: FreeBSD-ISP@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A5BDB16A415 for ; Wed, 27 Dec 2006 12:40:02 +0000 (UTC) (envelope-from jan@digitaldaemon.com) Received: from digitaldaemon.com (digitaldaemon.com [63.105.9.34]) by mx1.freebsd.org (Postfix) with SMTP id C891613C493 for ; Wed, 27 Dec 2006 12:39:59 +0000 (UTC) (envelope-from jan@digitaldaemon.com) Received: (qmail 34764 invoked by uid 98); 27 Dec 2006 12:39:58 -0000 Received: from 63.105.9.34 by digitaldaemon.com (envelope-from , uid 89) with qmail-scanner-1.25 (clamdscan: 0.87/1195. Clear:RC:1(63.105.9.34):. Processed in 0.293546 secs); 27 Dec 2006 12:39:58 -0000 X-Qmail-Scanner-Mail-From: jan@digitaldaemon.com via digitaldaemon.com X-Qmail-Scanner: 1.25 (Clear:RC:1(63.105.9.34):. Processed in 0.293546 secs) Received: from digitaldaemon.com (HELO ?184.157.102.2?) (63.105.9.34) by digitaldaemon.com with SMTP; 27 Dec 2006 12:39:57 -0000 Message-ID: <45926996.2070603@digitaldaemon.com> Date: Wed, 27 Dec 2006 07:39:50 -0500 From: Jan Knepper User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Kris Kennaway References: <45918F6E.90006@digitaldaemon.com> <004c01c7293b$d5e03b40$6500a8c0@laptopt> <4591CB3C.1060902@digitaldaemon.com> <20061227033742.GA9706@xor.obsecurity.org> In-Reply-To: <20061227033742.GA9706@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Tim McCullagh , FreeBSD ISP , FreeBSD Hackers Subject: Re: 6.1-RELEASE / 6.2 Kernel Crash... X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Dec 2006 12:40:02 -0000 Kris Kennaway wrote: > On Tue, Dec 26, 2006 at 08:24:12PM -0500, Jan Knepper wrote: > >> Tried that and started >> >> dd if=/dev/ad4 if=/dev/ad6 bs=1m >> >> Kernel went in panic and automatic reboot in about an hour... >> >> It gets worse... when it does reboot the disk drive will not show in the >> BIOS, nor does FreeBSD recognize it during boot. The system actually has >> to be turned off to reset the drive... >> >> This is bad... >> >> Any other suggestions? >> > > Sounds like a bug in the support for your ATA hardware, or your > hardware is broken. The very least you'll need to do is to obtain a > crashdump and debugging backtrace (see the developers handbook) and CC > it to sos@ > Will start working on that (or downgrade to 5.5)... I am testing that and I think although I have not found a documented way of doing that it can be done. Thanks! Jan From owner-freebsd-isp@FreeBSD.ORG Wed Dec 27 12:40:26 2006 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6C1FB16A505 for ; Wed, 27 Dec 2006 12:40:26 +0000 (UTC) (envelope-from "") Received: from marova.hst.terra.com.br (marova.hst.terra.com.br [200.176.10.215]) by mx1.freebsd.org (Postfix) with ESMTP id 27FEE13C49A for ; Wed, 27 Dec 2006 12:40:26 +0000 (UTC) (envelope-from "") Received: from bundure.hst.terra.com.br (bundure.hst.terra.com.br [200.176.10.195]) by marova.hst.terra.com.br (Postfix) with ESMTP id 66A8811AAD41 for ; Wed, 27 Dec 2006 10:19:26 -0200 (BRST) Received: from baladonia.hst.terra.com.br (baladonia.hst.terra.com.br [200.176.10.78]) by bundure.hst.terra.com.br (Postfix) with ESMTP id 76F969A00DD for ; Wed, 27 Dec 2006 10:19:24 -0200 (BRST) Received: by baladonia.hst.terra.com.br (Postfix) id 5F1FF1AA0535; Wed, 27 Dec 2006 10:19:24 -0200 (BRST) Auto-Submitted: auto-replied Precedence: junk Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable In-Reply-To: <20061227121921.B45581AA01EF@baladonia.hst.terra.com.br> References: <20061227121921.B45581AA01EF@baladonia.hst.terra.com.br> X-Terra-Delivered-To: 4628131#perm!terra From: moemaprint@sao.terra.com.br To: freebsd-isp@freebsd.org Message-Id: <20061227121924.5F1FF1AA0535@baladonia.hst.terra.com.br> Date: Wed, 27 Dec 2006 10:19:24 -0200 (BRST) Subject: [Mensagem Automatica] X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Dec 2006 12:40:26 -0000 This message is an automatic response. Mensagem [[Spam] Grana] recebida. From owner-freebsd-isp@FreeBSD.ORG Wed Dec 27 12:41:13 2006 Return-Path: X-Original-To: FreeBSD-ISP@FreeBSD.org Delivered-To: FreeBSD-ISP@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 91B7116A403 for ; Wed, 27 Dec 2006 12:41:13 +0000 (UTC) (envelope-from jan@digitaldaemon.com) Received: from digitaldaemon.com (digitaldaemon.com [63.105.9.34]) by mx1.freebsd.org (Postfix) with SMTP id D985613C47E for ; Wed, 27 Dec 2006 12:41:12 +0000 (UTC) (envelope-from jan@digitaldaemon.com) Received: (qmail 34861 invoked by uid 98); 27 Dec 2006 12:41:08 -0000 Received: from 63.105.9.34 by digitaldaemon.com (envelope-from , uid 89) with qmail-scanner-1.25 (clamdscan: 0.87/1195. Clear:RC:1(63.105.9.34):. Processed in 0.346779 secs); 27 Dec 2006 12:41:08 -0000 X-Qmail-Scanner-Mail-From: jan@digitaldaemon.com via digitaldaemon.com X-Qmail-Scanner: 1.25 (Clear:RC:1(63.105.9.34):. Processed in 0.346779 secs) Received: from digitaldaemon.com (HELO ?184.157.102.2?) (63.105.9.34) by digitaldaemon.com with SMTP; 27 Dec 2006 12:41:08 -0000 Message-ID: <459269DD.3010606@digitaldaemon.com> Date: Wed, 27 Dec 2006 07:41:01 -0500 From: Jan Knepper User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: john@day-light.com References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: FreeBSD ISP Subject: Re: 6.1-RELEASE / 6.2 Kernel Crash... X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Dec 2006 12:41:13 -0000 John Brooks wrote: >> dd if=/dev/ad4 if=/dev/ad6 bs=1m >> > > shouldn't that be: > > dd if=/dev/ad4 of=/dev/ad6 bs=1m > ^ > > just curious... > Yes... typo... :-( Thanks! Jan From owner-freebsd-isp@FreeBSD.ORG Wed Dec 27 12:42:14 2006 Return-Path: X-Original-To: FreeBSD-ISP@freebsd.org Delivered-To: FreeBSD-ISP@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 289E216A4FF for ; Wed, 27 Dec 2006 12:42:14 +0000 (UTC) (envelope-from jan@digitaldaemon.com) Received: from digitaldaemon.com (digitaldaemon.com [63.105.9.34]) by mx1.freebsd.org (Postfix) with SMTP id 545B613C497 for ; Wed, 27 Dec 2006 12:42:13 +0000 (UTC) (envelope-from jan@digitaldaemon.com) Received: (qmail 34929 invoked by uid 98); 27 Dec 2006 12:42:12 -0000 Received: from 63.105.9.34 by digitaldaemon.com (envelope-from , uid 89) with qmail-scanner-1.25 (clamdscan: 0.87/1195. Clear:RC:1(63.105.9.34):. Processed in 0.225964 secs); 27 Dec 2006 12:42:12 -0000 X-Qmail-Scanner-Mail-From: jan@digitaldaemon.com via digitaldaemon.com X-Qmail-Scanner: 1.25 (Clear:RC:1(63.105.9.34):. Processed in 0.225964 secs) Received: from digitaldaemon.com (HELO ?184.157.102.2?) (63.105.9.34) by digitaldaemon.com with SMTP; 27 Dec 2006 12:42:12 -0000 Message-ID: <45926A1D.8040009@digitaldaemon.com> Date: Wed, 27 Dec 2006 07:42:05 -0500 From: Jan Knepper User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Hans Petter Selasky References: <45918F6E.90006@digitaldaemon.com> <004c01c7293b$d5e03b40$6500a8c0@laptopt> <4591CB3C.1060902@digitaldaemon.com> <200612271107.13124.hselasky@c2i.net> In-Reply-To: <200612271107.13124.hselasky@c2i.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Tim McCullagh , freebsd-hackers@freebsd.org, FreeBSD ISP Subject: Re: 6.1-RELEASE / 6.2 Kernel Crash... X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Dec 2006 12:42:14 -0000 Hans Petter Selasky wrote: > On Wednesday 27 December 2006 02:24, Jan Knepper wrote: > >> Tried that and started >> >> dd if=/dev/ad4 if=/dev/ad6 bs=1m >> >> Kernel went in panic and automatic reboot in about an hour... >> >> It gets worse... when it does reboot the disk drive will not show in the >> BIOS, nor does FreeBSD recognize it during boot. The system actually has >> to be turned off to reset the drive... >> >> This is bad... >> >> Any other suggestions? >> >> > > Maybe you can setup a serial console to grab the panic message? > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/serialconsole-setup.html > > Good idea... I might just try that... Thanks! Jan From owner-freebsd-isp@FreeBSD.ORG Wed Dec 27 20:40:27 2006 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3232C16A494 for ; Wed, 27 Dec 2006 20:40:27 +0000 (UTC) (envelope-from mwm-dated-1168114452.020dbf@mired.org) Received: from mired.org (vpn.mired.org [66.92.153.74]) by mx1.freebsd.org (Postfix) with SMTP id C998613C47E for ; Wed, 27 Dec 2006 20:40:26 +0000 (UTC) (envelope-from mwm-dated-1168114452.020dbf@mired.org) Received: (qmail 76058 invoked by uid 1001); 27 Dec 2006 20:14:12 -0000 Received: by bhuda.mired.org (tmda-sendmail, from uid 1001); Wed, 27 Dec 2006 15:14:12 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17810.54292.139339.466850@bhuda.mired.org> Date: Wed, 27 Dec 2006 15:14:12 -0500 To: Jan Knepper In-Reply-To: <4592690B.7080800@digitaldaemon.com> References: <45918F6E.90006@digitaldaemon.com> <004c01c7293b$d5e03b40$6500a8c0@laptopt> <4591CB3C.1060902@digitaldaemon.com> <200612261808.08984.mario@schmut.com> <4592690B.7080800@digitaldaemon.com> X-Mailer: VM 7.17 under 21.4 (patch 19) "Constant Variable" XEmacs Lucid X-Primary-Address: mwm@mired.org X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ X-Delivery-Agent: TMDA/1.1.5 (Fettercairn) From: Mike Meyer Cc: freebsd-isp@freebsd.org, Tim McCullagh , Mario Theodoridis , FreeBSD Hackers Subject: Re: 6.1-RELEASE / 6.2 Kernel Crash... X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Dec 2006 20:40:27 -0000 In <4592690B.7080800@digitaldaemon.com>, Jan Knepper typed: > FreeBSD 5.x branch run on that machine for almost 2 years without a > problem and magically the same time period in *hours* that I upgrade the > machine I get hardware problems too? Not an impossible coincidence, but > not very likely... Or it could be that you have a hardware problem in hardware that wasn't used by 5.x but is by 6.x. I had an 11/750 that ran BSD 4.2 for years with no problems. When I tried to upgrade it to BSD 4.3, it would reliably panic in namei during the boot process. We had about a dozen 750s, and this was our test machine - so none of them were going to be upgraded until this got fixed, deadline or no. Stepping through namei in the debugger showed that one of the instructions in the function prelude was changing a high bit in a register it wasn't supposed to touch at all. In 4.2, the register was unused, because namei got passed a handful of arguments. In 4.3, it got passed a pointer to a struct with some of that information in it, and the pointer wound up in said register. Dereferencing the pointer caused the panic. A motherboard replacement solved the problem. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-isp@FreeBSD.ORG Wed Dec 27 20:50:28 2006 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 17E8716A403 for ; Wed, 27 Dec 2006 20:50:28 +0000 (UTC) (envelope-from jan@digitaldaemon.com) Received: from digitaldaemon.com (digitaldaemon.com [63.105.9.34]) by mx1.freebsd.org (Postfix) with SMTP id EB26513C463 for ; Wed, 27 Dec 2006 20:50:26 +0000 (UTC) (envelope-from jan@digitaldaemon.com) Received: (qmail 67330 invoked by uid 98); 27 Dec 2006 20:50:25 -0000 Received: from 63.105.9.34 by digitaldaemon.com (envelope-from , uid 89) with qmail-scanner-1.25 (clamdscan: 0.87/1195. Clear:RC:1(63.105.9.34):. Processed in 0.340147 secs); 27 Dec 2006 20:50:25 -0000 X-Qmail-Scanner-Mail-From: jan@digitaldaemon.com via digitaldaemon.com X-Qmail-Scanner: 1.25 (Clear:RC:1(63.105.9.34):. Processed in 0.340147 secs) Received: from digitaldaemon.com (HELO ?16.81.102.2?) (63.105.9.34) by digitaldaemon.com with SMTP; 27 Dec 2006 20:50:25 -0000 Message-ID: <4592DC8C.4040704@digitaldaemon.com> Date: Wed, 27 Dec 2006 15:50:20 -0500 From: Jan Knepper User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Mike Meyer References: <45918F6E.90006@digitaldaemon.com> <004c01c7293b$d5e03b40$6500a8c0@laptopt> <4591CB3C.1060902@digitaldaemon.com> <200612261808.08984.mario@schmut.com> <4592690B.7080800@digitaldaemon.com> <17810.54292.139339.466850@bhuda.mired.org> In-Reply-To: <17810.54292.139339.466850@bhuda.mired.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-isp@freebsd.org, Tim McCullagh , Mario Theodoridis , FreeBSD Hackers Subject: Re: 6.1-RELEASE / 6.2 Kernel Crash... X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Dec 2006 20:50:28 -0000 Understood... and exactly as I wrote... Not impossible, but not that likely... Thanks! Jan Mike Meyer wrote: > In <4592690B.7080800@digitaldaemon.com>, Jan Knepper typed: > >> FreeBSD 5.x branch run on that machine for almost 2 years without a >> problem and magically the same time period in *hours* that I upgrade the >> machine I get hardware problems too? Not an impossible coincidence, but >> not very likely... >> > > Or it could be that you have a hardware problem in hardware that > wasn't used by 5.x but is by 6.x. > > > I had an 11/750 that ran BSD 4.2 for years with no problems. When I > tried to upgrade it to BSD 4.3, it would reliably panic in namei > during the boot process. We had about a dozen 750s, and this was our > test machine - so none of them were going to be upgraded until this > got fixed, deadline or no. > > Stepping through namei in the debugger showed that one of the > instructions in the function prelude was changing a high bit in a > register it wasn't supposed to touch at all. In 4.2, the register was > unused, because namei got passed a handful of arguments. In 4.3, it > got passed a pointer to a struct with some of that information in it, > and the pointer wound up in said register. Dereferencing the pointer > caused the panic. > > A motherboard replacement solved the problem. > > > > From owner-freebsd-isp@FreeBSD.ORG Thu Dec 28 00:52:05 2006 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 72F9E16A403 for ; Thu, 28 Dec 2006 00:52:05 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with SMTP id 0C43313C473 for ; Thu, 28 Dec 2006 00:52:04 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 17252 invoked by uid 399); 28 Dec 2006 00:25:23 -0000 Received: from localhost (HELO ?192.168.0.5?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 28 Dec 2006 00:25:23 -0000 X-Originating-IP: 127.0.0.1 Message-ID: <45930EF1.2040105@FreeBSD.org> Date: Wed, 27 Dec 2006 16:25:21 -0800 From: Doug Barton Organization: http://www.freebsd.org/ User-Agent: Thunderbird 1.5.0.8 (X11/20061215) MIME-Version: 1.0 To: Jan Knepper References: <45918F6E.90006@digitaldaemon.com> <004c01c7293b$d5e03b40$6500a8c0@laptopt> <4591CB3C.1060902@digitaldaemon.com> <200612261808.08984.mario@schmut.com> <4592690B.7080800@digitaldaemon.com> In-Reply-To: <4592690B.7080800@digitaldaemon.com> X-Enigmail-Version: 0.94.1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-isp@freebsd.org, Tim McCullagh , Mario Theodoridis , FreeBSD Hackers Subject: Re: 6.1-RELEASE / 6.2 Kernel Crash... X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: FreeBSD-stable@freebsd.org List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Dec 2006 00:52:05 -0000 [Attempting to redirect this to -stable, where it's more appropriate.] Jan Knepper wrote: > FreeBSD 5.x branch run on that machine for almost 2 years without a > problem and magically the same time period in *hours* that I upgrade the > machine I get hardware problems too? Not an impossible coincidence, but > not very likely... Depends on how you did the upgrade. Was the machine running continuously for 2 years, then you turned it off, then you did the upgrade? I had a box die that way because (we found out later) that the system drive's spindle had "issues" that were not apparent until it had been turned off, cooled down, then spun (sort of) back up. IOW, you're probably right, but "magical" hardware problems that develop during upgrade periods are more common than a lot of people realize. Meanwhile, back at the ranch, if you can't easily get a serial console up and running, your earlier suggestion of putting the box back to the last known good 5.x release is a good one. At least that can help rule out hardware _failure_, as opposed to hardware-used-differently issues. hth, Doug -- This .signature sanitized for your protection From owner-freebsd-isp@FreeBSD.ORG Thu Dec 28 05:25:08 2006 Return-Path: X-Original-To: FreeBSD-ISP@FreeBSD.org Delivered-To: FreeBSD-ISP@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3FE6016A403 for ; Thu, 28 Dec 2006 05:25:08 +0000 (UTC) (envelope-from jan@digitaldaemon.com) Received: from digitaldaemon.com (digitaldaemon.com [63.105.9.34]) by mx1.freebsd.org (Postfix) with SMTP id 556F213C478 for ; Thu, 28 Dec 2006 05:25:06 +0000 (UTC) (envelope-from jan@digitaldaemon.com) Received: (qmail 2680 invoked by uid 98); 28 Dec 2006 05:25:04 -0000 Received: from 63.105.9.34 by digitaldaemon.com (envelope-from , uid 89) with qmail-scanner-1.25 (clamdscan: 0.87/1195. Clear:RC:1(63.105.9.34):. Processed in 0.136763 secs); 28 Dec 2006 05:25:04 -0000 X-Qmail-Scanner-Mail-From: jan@digitaldaemon.com via digitaldaemon.com X-Qmail-Scanner: 1.25 (Clear:RC:1(63.105.9.34):. Processed in 0.136763 secs) Received: from digitaldaemon.com (HELO ?160.63.102.2?) (63.105.9.34) by digitaldaemon.com with SMTP; 28 Dec 2006 05:25:03 -0000 Message-ID: <4593552E.80400@digitaldaemon.com> Date: Thu, 28 Dec 2006 00:25:02 -0500 From: Jan Knepper User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Kris Kennaway References: <45918F6E.90006@digitaldaemon.com> <004c01c7293b$d5e03b40$6500a8c0@laptopt> <4591CB3C.1060902@digitaldaemon.com> <20061227033742.GA9706@xor.obsecurity.org> In-Reply-To: <20061227033742.GA9706@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Tim McCullagh , FreeBSD ISP , FreeBSD Hackers Subject: Re: 6.1-RELEASE / 6.2 Kernel Crash... X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Dec 2006 05:25:08 -0000 Kris Kennaway wrote: > On Tue, Dec 26, 2006 at 08:24:12PM -0500, Jan Knepper wrote: > >> Tried that and started >> >> dd if=/dev/ad4 if=/dev/ad6 bs=1m >> >> Kernel went in panic and automatic reboot in about an hour... >> >> It gets worse... when it does reboot the disk drive will not show in the >> BIOS, nor does FreeBSD recognize it during boot. The system actually has >> to be turned off to reset the drive... >> >> This is bad... >> >> Any other suggestions? >> > > Sounds like a bug in the support for your ATA hardware, or your > hardware is broken. The very least you'll need to do is to obtain a > crashdump and debugging backtrace (see the developers handbook) and CC > it to sos@ > > This is getting funnier... I added: dumpdev="AUTO" to: rc.conf Rebooted the system and tried to get it to crash again... And indeed it does in process 9: taskq Then it starts dumping which takes a couple of seconds as the machine has 2 GB Ram... Than it reboots... and the next thing you know... savecore does NOT recognize a dump on the swap file system. If does not save anything to /var/crash... Tried this about 10 times... No luck... Any other idea's? Thanks! Jan From owner-freebsd-isp@FreeBSD.ORG Thu Dec 28 22:24:16 2006 Return-Path: X-Original-To: FreeBSD-ISP@FreeBSD.org Delivered-To: FreeBSD-ISP@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A4B1616A403 for ; Thu, 28 Dec 2006 22:24:16 +0000 (UTC) (envelope-from jan@digitaldaemon.com) Received: from digitaldaemon.com (digitaldaemon.com [63.105.9.34]) by mx1.freebsd.org (Postfix) with SMTP id 6310B13C479 for ; Thu, 28 Dec 2006 22:24:12 +0000 (UTC) (envelope-from jan@digitaldaemon.com) Received: (qmail 2432 invoked by uid 98); 28 Dec 2006 22:24:07 -0000 Received: from 63.105.9.34 by digitaldaemon.com (envelope-from , uid 89) with qmail-scanner-1.25 (clamdscan: 0.87/1195. Clear:RC:1(63.105.9.34):. Processed in 0.138927 secs); 28 Dec 2006 22:24:07 -0000 X-Qmail-Scanner-Mail-From: jan@digitaldaemon.com via digitaldaemon.com X-Qmail-Scanner: 1.25 (Clear:RC:1(63.105.9.34):. Processed in 0.138927 secs) Received: from digitaldaemon.com (HELO ?160.63.102.2?) (63.105.9.34) by digitaldaemon.com with SMTP; 28 Dec 2006 22:24:06 -0000 Message-ID: <45944404.8050301@digitaldaemon.com> Date: Thu, 28 Dec 2006 17:24:04 -0500 From: Jan Knepper User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Jan Knepper References: <45918F6E.90006@digitaldaemon.com> <004c01c7293b$d5e03b40$6500a8c0@laptopt> <4591CB3C.1060902@digitaldaemon.com> <20061227033742.GA9706@xor.obsecurity.org> <4593552E.80400@digitaldaemon.com> In-Reply-To: <4593552E.80400@digitaldaemon.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Tim McCullagh , FreeBSD ISP , FreeBSD Hackers , Kris Kennaway Subject: Re: 6.1-RELEASE / 6.2 Kernel Crash... X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Dec 2006 22:24:16 -0000 Jan Knepper wrote: > Kris Kennaway wrote: >> On Tue, Dec 26, 2006 at 08:24:12PM -0500, Jan Knepper wrote: >> >>> Tried that and started >>> >>> dd if=/dev/ad4 if=/dev/ad6 bs=1m >>> >>> Kernel went in panic and automatic reboot in about an hour... >>> >>> It gets worse... when it does reboot the disk drive will not show in >>> the BIOS, nor does FreeBSD recognize it during boot. The system >>> actually has to be turned off to reset the drive... >>> >>> This is bad... >>> >>> Any other suggestions? >>> >> >> Sounds like a bug in the support for your ATA hardware, or your >> hardware is broken. The very least you'll need to do is to obtain a >> crashdump and debugging backtrace (see the developers handbook) and CC >> it to sos@ >> >> > This is getting funnier... > I added: > dumpdev="AUTO" > to: rc.conf > Rebooted the system and tried to get it to crash again... > And indeed it does in process 9: taskq > > Then it starts dumping which takes a couple of seconds as the machine > has 2 GB Ram... > > Than it reboots... and the next thing you know... savecore does NOT > recognize a dump on the swap file system. If does not save anything to > /var/crash... > Tried this about 10 times... No luck... > > Any other idea's? > Well... since capturing a kernel debug dump does not seem to be working I had an other crash (is not that difficult to reproduce) and copied the console screen with the information... Here it is, for whatever this is worth... Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x50 fault code = supervisor read, page not present instruction pointer = 0x8:0xffffffff80289d6d stack pointer = 0x10:0xffffffffb1b06af0 frame pointer = 0x10:0xffffff00468d9400 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current processor = 9 (thread taskq) trap number = 12 panic: page fault cpuid = 0 Uptime: 16h56m17s Dumping 2047 MB (2 chunks) chunk 0: 1MB (156 pages) .. ok chunk 1: 2047MB (524016 pages) 2031 2015 1999 1983 1967 1951 1935 1919 1903 18 87 ... ... 47 31 15 ... ok Dump complete Automatic reboot in 15 seconds - press a key on console ot abort From owner-freebsd-isp@FreeBSD.ORG Fri Dec 29 22:02:05 2006 Return-Path: X-Original-To: FreeBSD-ISP@FreeBSD.org Delivered-To: FreeBSD-ISP@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1F07416A407 for ; Fri, 29 Dec 2006 22:02:05 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id DC77513C428 for ; Fri, 29 Dec 2006 22:02:04 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 403EB46DE0; Fri, 29 Dec 2006 16:33:25 -0500 (EST) Date: Fri, 29 Dec 2006 21:33:25 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Jan Knepper In-Reply-To: <4593552E.80400@digitaldaemon.com> Message-ID: <20061229213013.E86685@fledge.watson.org> References: <45918F6E.90006@digitaldaemon.com> <004c01c7293b$d5e03b40$6500a8c0@laptopt> <4591CB3C.1060902@digitaldaemon.com> <20061227033742.GA9706@xor.obsecurity.org> <4593552E.80400@digitaldaemon.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Tim McCullagh , FreeBSD ISP , FreeBSD Hackers , Kris Kennaway Subject: Re: 6.1-RELEASE / 6.2 Kernel Crash... X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Dec 2006 22:02:05 -0000 On Thu, 28 Dec 2006, Jan Knepper wrote: >> Sounds like a bug in the support for your ATA hardware, or your hardware is >> broken. The very least you'll need to do is to obtain a crashdump and >> debugging backtrace (see the developers handbook) and CC it to sos@ >> > This is getting funnier... > I added: > dumpdev="AUTO" > to: rc.conf > Rebooted the system and tried to get it to crash again... > And indeed it does in process 9: taskq > > Then it starts dumping which takes a couple of seconds as the machine has 2 > GB Ram... > > Than it reboots... and the next thing you know... savecore does NOT > recognize a dump on the swap file system. If does not save anything to > /var/crash... Tried this about 10 times... No luck... > > Any other idea's? Yeah, unfortunately if some combination of storage driver and hardware aren't working, it's hard to get a dump... The usual fallback here is to use a serial console to capture debugging information from DDB and to skip the dump side of things. In fact, I prefer debugging that way most of the time. The reason for using a serial console (or firewire) is to avoid having to hand-copy trap and debugging information, which gets very painful very quickly. Compile DDB and KDB into your kernel, and configure a serial console, and a panic should lead to the system entering the debugger. The usual first command to type is "trace" to generate a backtrace; it's often useful also to do "show pcpu", "show allpcpu", "alltrace", and "ps", although for the problem you're seeing the last two may be less useful. The 0x50 trap address in your post suggests this is a NULL pointer dereference. What we now need to do is work out what piece of code is dereferencing the pointer improperly, which is where the backtrace comes in. If you could copy and paste all that DDB/KDB output into an e-mail (or, perhaps more ideally, a PR), that would be great. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-isp@FreeBSD.ORG Fri Dec 29 22:33:07 2006 Return-Path: X-Original-To: FreeBSD-ISP@FreeBSD.org Delivered-To: FreeBSD-ISP@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 19ADD16A403 for ; Fri, 29 Dec 2006 22:33:07 +0000 (UTC) (envelope-from jan@digitaldaemon.com) Received: from digitaldaemon.com (digitaldaemon.com [63.105.9.34]) by mx1.freebsd.org (Postfix) with SMTP id 61A9E13C448 for ; Fri, 29 Dec 2006 22:33:06 +0000 (UTC) (envelope-from jan@digitaldaemon.com) Received: (qmail 79498 invoked by uid 98); 29 Dec 2006 22:33:04 -0000 Received: from 63.105.9.34 by digitaldaemon.com (envelope-from , uid 89) with qmail-scanner-1.25 (clamdscan: 0.87/1195. Clear:RC:1(63.105.9.34):. Processed in 0.243414 secs); 29 Dec 2006 22:33:04 -0000 X-Qmail-Scanner-Mail-From: jan@digitaldaemon.com via digitaldaemon.com X-Qmail-Scanner: 1.25 (Clear:RC:1(63.105.9.34):. Processed in 0.243414 secs) Received: from digitaldaemon.com (HELO ?16.81.102.2?) (63.105.9.34) by digitaldaemon.com with SMTP; 29 Dec 2006 22:33:04 -0000 Message-ID: <4595979B.1030104@digitaldaemon.com> Date: Fri, 29 Dec 2006 17:32:59 -0500 From: Jan Knepper User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Robert Watson References: <45918F6E.90006@digitaldaemon.com> <004c01c7293b$d5e03b40$6500a8c0@laptopt> <4591CB3C.1060902@digitaldaemon.com> <20061227033742.GA9706@xor.obsecurity.org> <4593552E.80400@digitaldaemon.com> <20061229213013.E86685@fledge.watson.org> In-Reply-To: <20061229213013.E86685@fledge.watson.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Tim McCullagh , FreeBSD ISP , Kris Kennaway , FreeBSD Hackers Subject: Re: 6.1-RELEASE / 6.2 Kernel Crash... X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Dec 2006 22:33:07 -0000 Robert Watson wrote: > On Thu, 28 Dec 2006, Jan Knepper wrote: > >>> Sounds like a bug in the support for your ATA hardware, or your >>> hardware is broken. The very least you'll need to do is to obtain a >>> crashdump and debugging backtrace (see the developers handbook) and >>> CC it to sos@ >>> >> This is getting funnier... >> I added: >> dumpdev="AUTO" >> to: rc.conf >> Rebooted the system and tried to get it to crash again... >> And indeed it does in process 9: taskq >> >> Then it starts dumping which takes a couple of seconds as the machine >> has 2 GB Ram... >> >> Than it reboots... and the next thing you know... savecore does NOT >> recognize a dump on the swap file system. If does not save anything >> to /var/crash... Tried this about 10 times... No luck... >> >> Any other idea's? > > Yeah, unfortunately if some combination of storage driver and hardware > aren't working, it's hard to get a dump... No kidding! > The usual fallback here is to use a serial console to capture > debugging information from DDB and to skip the dump side of things. > In fact, I prefer debugging that way most of the time. The reason for > using a serial console (or firewire) is to avoid having to hand-copy > trap and debugging information, which gets very painful very quickly. > Compile DDB and KDB into your kernel, and configure a serial console, > and a panic should lead to the system entering the debugger. The > usual first command to type is "trace" to generate a backtrace; it's > often useful also to do "show pcpu", "show allpcpu", "alltrace", and > "ps", although for the problem you're seeing the last two may be less > useful. > > The 0x50 trap address in your post suggests this is a NULL pointer > dereference. What we now need to do is work out what piece of code is > dereferencing the pointer improperly, which is where the backtrace > comes in. > > If you could copy and paste all that DDB/KDB output into an e-mail > (or, perhaps more ideally, a PR), that would be great. Thanks for the reply Robert. Since this machine runs at my house I hope to get to this over the weekend. I will definitely try to get this information out as soon as I decently can. Thanks! Jan Knepper