From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 02:21:54 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B5ED416A41F for ; Tue, 13 Dec 2005 02:21:54 +0000 (GMT) (envelope-from fredthetree@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id D367643D58 for ; Tue, 13 Dec 2005 02:21:53 +0000 (GMT) (envelope-from fredthetree@gmail.com) Received: by wproxy.gmail.com with SMTP id i4so25440wra for ; Mon, 12 Dec 2005 18:21:53 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=U23QuWwx0/3XB3LsUkzjSlZSQVJmfqpNdiDiBDmqYDMknEZYsGhbBjJdyLKbp8xf7Pn89lacx/67E+3AtN5EdxZusoTCue183Fvu3GBtgqo36HDkEms23MedtfCaXAtMKKoKQyc13omZ/mMnblRZD+EKH5pew0WQ/BR01hlmvFQ= Received: by 10.54.159.5 with SMTP id h5mr204446wre; Mon, 12 Dec 2005 18:21:52 -0800 (PST) Received: by 10.54.146.19 with HTTP; Mon, 12 Dec 2005 18:21:52 -0800 (PST) Message-ID: Date: Mon, 12 Dec 2005 22:21:52 -0400 From: fredthetree To: freebsd-stable@freebsd.org In-Reply-To: <439E0B23.3060304@asd.aplus.net> MIME-Version: 1.0 References: <439DE88B.1090407@asd.aplus.net> <439E0B23.3060304@asd.aplus.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: 6.0 random freezes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 02:21:54 -0000 I just wanted to chime in and say I've had my 6.0-RELEASE #0 freeze up twic= e in the past few days. never once had it happen with 5.x. everything locks= , no keyboard response, no mouse, and after several minutes it reboots itself= , and savecore starts up during boot.. and again, it's not during heavy load= , both times i was running X, just browsing ye olde internet with firefox, some other apps running as per usual.. FreeBSD atlan.ns.ca 6.0-RELEASE FreeBSD 6.0-RELEASE #0: Thu Nov 3 09:36:13 UTC 2005 root@x64.samsco.home:/usr/obj/usr/src/sys/GENERIC i386 Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.0-RELEASE #0: Thu Nov 3 09:36:13 UTC 2005 root@x64.samsco.home:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel Pentium III (701.59-MHz 686-class CPU) Origin =3D "GenuineIntel" Id =3D 0x683 Stepping =3D 3 Features=3D0x387f9ff real memory =3D 536805376 (511 MB) avail memory =3D 515956736 (492 MB) ath_hal: 0.9.14.9 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413) npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) pci_link0: irq 11 on acpi0 pci_link1: irq 5 on acpi0 pci_link2: irq 9 on acpi0 pci_link3: irq 10 on acpi0 Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 cpu0: on acpi0 acpi_throttle0: on cpu0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff,0x4000-0x4041,0x5000-0x500f on acpi0 pci0: on pcib0 agp0: mem 0xe0000000-0xe3ffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 7.1 on pci0 ata0: on atapci0 ata1: on atapci0 uhci0: port 0x9000-0x901f irq 10 at device 7.2 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: at device 7.3 (no driver attached) pcm0: port 0x9400-0x941f irq 9 at device 10.0 on pci0 pcm0: ath0: mem 0xe8000000-0xe800ffff irq 5 at device 11.0 on pci0 ath0: Ethernet address: 00:0f:3d:50:13:5c ath0: mac 5.9 phy 4.3 radio 4.6 fdc0: port 0x3f2-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0: port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3 pmtimer0 on isa0 orm0: at iomem 0xc0000-0xcffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=3D0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 umass0: Cowon Systems, Inc. iAUDIO M3 Digital Audio Player, rev 2.00/1.00, addr 2 ugen0: EPSON EPSON Scanner, rev 2.00/1.10, addr 3 Timecounter "TSC" frequency 701594095 Hz quality 800 Timecounters tick every 1.000 msec ad0: 8063MB at ata0-master UDMA33 ad1: 57241MB at ata0-slave UDMA33 acd0: CDRW at ata1-master UDMA33 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-0 device da0: 1.000MB/s transfers da0: 19073MB (39063024 512 byte sectors: 255H 63S/T 2431C) Trying to mount root from ufs:/dev/ad0s1a On 12/12/05, Atanas wrote: > > Ronald Klop said the following on 12/12/05 13:27: > > > > What happens if you set one of these sysctl values to 0? (This disables > > SMP changes from 5.4 to 6.0.) > > debug.mpsafevfs: 1 > > debug.mpsafenet : 1 > > debug.mpsafevm: 1 > > > Thanks for the suggestion! > I just did so and rebooted both machines, so we'll see. > > I remember unseting debug.mpsafenet before 5.4 due to some ipfw > limitations, but didn't know about the other two. > > > And is there a possibility (performance-wise) to build a kernel with > > WITNESS and/or INVARIANTS options compiled in. This will give more info > > about possible locking problems. Your system will run slower. And > > because of this the problem may not occur anymore, but it is worth the > > try. > > > Both machines are not much loaded, so I could afford slowing them down a > bit for a while (I hope it won't be several times slower). I will do > that at some point later if the problem still persists. > > I hope I won't be forced to downgrade to 5.4, though I'm already working > on that (just in case). > > Regards, > Atanas > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >