From owner-freebsd-stable@FreeBSD.ORG Sun May 23 05:46:25 2004 Return-Path: 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 4509616A4CE for ; Sun, 23 May 2004 05:46:25 -0700 (PDT) Received: from postit.mail.adnap.net.au (postit.mail.adnap.net.au [203.6.132.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB0D343D1F for ; Sun, 23 May 2004 05:46:24 -0700 (PDT) (envelope-from bastill@adam.com.au) Received: from 192.168.1.11 (unknown [202.6.154.199]) by postit.mail.adnap.net.au (Postfix) with ESMTP id 630F51C961 for ; Sun, 23 May 2004 22:15:39 +0930 (CST) From: Brian Astill To: freebsd-stable@FreeBSD.ORG Date: Sun, 23 May 2004 22:13:22 +0930 User-Agent: KMail/1.5.4 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200405232213.22361.bastill@adam.com.au> Subject: is microuptime backwards solved? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 May 2004 12:46:25 -0000 I have the Athlon CPU - VIA chipset combination which suffers persistent runaway messages saying "microuptime going backwards" unless APM is removed from the kernel. However, a recent clean install of FBSD 4.9 Release hasn't shown any sign of the problem. Is it fixed or have I somehow been lucky not to produce the trigger? -- Regards, Brian From owner-freebsd-stable@FreeBSD.ORG Sun May 23 17:00:56 2004 Return-Path: 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 6E72F16A4CE for ; Sun, 23 May 2004 17:00:56 -0700 (PDT) Received: from auk2.snu.ac.kr (auk2.snu.ac.kr [147.46.100.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1CD3B43D1F for ; Sun, 23 May 2004 17:00:56 -0700 (PDT) (envelope-from stopspam@users.sourceforge.net) Received: from [147.46.44.181] (stopspam@users.sourceforge.net) by auk2.snu.ac.kr (Terrace Internet Messaging Server) with ESMTP id 2004052408:43:12:776891.13435.2626239408 for ; Mon, 24 May 2004 08:43:12 +0900 (KST) Message-ID: <40B13B26.10201@users.sourceforge.net> Date: Mon, 24 May 2004 09:00:38 +0900 From: Rob User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040507 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org, iedowse@maths.tcd.ie References: <200405232109.aa46210@salmon.maths.tcd.ie> In-Reply-To: <200405232109.aa46210@salmon.maths.tcd.ie> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-TERRACE-SPAMMARK: YES-__TRSYS_LV__3 (SR:-2.03) (SRN:SPAMROBOT) ----------------- Subject: Re: USB patch for better bus_dma and detachment support X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 May 2004 00:00:56 -0000 Ian Dowse wrote: > In case anybody is interested in testing or helping with this, > there's a patch at > > http://people.freebsd.org/~iedowse/usb.diff > > that attempts to begin addressing a number of problems with our > current USB code: > > o All data buffers were allocated using bus_dma as physically > contiguous memory. All transfers involve a memory copy to/from > these contiguous buffers, and the contiguous memory is never > freed. Use of these buffers is also inefficient, so low-memory > systems tend to quickly run out of usable physical memory. > > o USB host controllers cannot be detached, so for example, unplugging > a cardbus USB device will cause a crash. > > Neither of these issues is completely solved by the patch, but most > I/O now avoids the need for contiguous buffers by using bus_dmamap_load() > on the virtual buffer, and the system seems to survive the removal > of a cardbus OHCI/EHCI controller, though memory is probably leaked. Can I apply this patch safely to STABLE as well? If not, then, if you make a patch for STABLE, I would test it right away! My umass storage USB toy, crashes the system when I umount it. I blamed the USB chipset (VIA 83C572 USB controller), but am still not sure, since I did not get much response from the STABLE mailing list. It would be great if your patch would solve the crash! Regards, Rob. From owner-freebsd-stable@FreeBSD.ORG Mon May 24 01:40:33 2004 Return-Path: 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 7AA3316A4CE for ; Mon, 24 May 2004 01:40:33 -0700 (PDT) Received: from auk2.snu.ac.kr (auk2.snu.ac.kr [147.46.100.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 22F6E43D2F for ; Mon, 24 May 2004 01:40:33 -0700 (PDT) (envelope-from stopspam@users.sourceforge.net) Received: from [147.46.44.181] (stopspam@users.sourceforge.net) by auk2.snu.ac.kr (Terrace Internet Messaging Server) with ESMTP id 2004052417:22:45:930801.13435.2716855216 for ; Mon, 24 May 2004 17:22:45 +0900 (KST) Message-ID: <40B1B4F2.6050605@users.sourceforge.net> Date: Mon, 24 May 2004 17:40:18 +0900 From: Rob User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040507 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Cyril Guibourg , freebsd-stable@freebsd.org References: <40ABFB4A.9060508@users.sourceforge.net> <87ad037d5j.fsf@blackbox.babasse.net> In-Reply-To: <87ad037d5j.fsf@blackbox.babasse.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-TERRACE-SPAMMARK: NO (SR:11.82) (by Terrace) Subject: Re: USB/umass detach freezes system X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 May 2004 08:40:33 -0000 Cyril Guibourg wrote: > Rob writes: > > >>Mounting this device with "mount_msdos /dev/da0s1 /mnt" is okay. >>The umass filesystem is there. Problems start when unmounting it. >>The umount command will hang and eventually the whole system will hang. >>Power off/on is only what helps then. > > > Welcome on board. I have the same issue and sometimes the system reboots. > It seems it worked better with 4.10-RC1 and starting with RC2 I am back > to 4.9 behaviour. > > >>Any ideas how to deal with this? > > > I would be glad to have the answer to that question. I compiled a kernel > with debug code and tried to figure out what is wrong without any success. > I asked for some help here but got no answer, good luck. Today someone has posted a patch for USB on the CURRENT mailing list, which seems to address this problem. Only bad-luck: the patch applies to CURRENT. Rob. From owner-freebsd-stable@FreeBSD.ORG Mon May 24 05:17:38 2004 Return-Path: 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 1AA5D16A4CE for ; Mon, 24 May 2004 05:17:38 -0700 (PDT) Received: from mail.errors.firstcallgroup.co.uk (mail.errors.firstcallgroup.co.uk [213.167.69.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id B475743D2F for ; Mon, 24 May 2004 05:17:37 -0700 (PDT) (envelope-from petefrench@keithprowse.com) Received: from smaug.rattatosk ([172.16.1.8]) by mail.errors.firstcallgroup.co.uk with esmtp (Exim 4.22) id 1BSENx-000JmK-UH for stable@FreeBSD.ORG; Mon, 24 May 2004 13:16:55 +0100 Received: from [172.16.1.6] (helo=dilbert.firstcallgroup.co.uk) by smaug.rattatosk with esmtp (Exim 4.22) id 1BSE40-0009c6-27 for stable@FreeBSD.ORG; Mon, 24 May 2004 12:56:16 +0100 Received: from petefrench by dilbert.firstcallgroup.co.uk with local (Exim 4.32; FreeBSD) id 1BSE40-0009XZ-1X for stable@FreeBSD.ORG; Mon, 24 May 2004 12:56:16 +0100 To: stable@FreeBSD.ORG Message-Id: From: Pete French Date: Mon, 24 May 2004 12:56:16 +0100 Subject: Problems with 4.10 and mysql X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 May 2004 12:17:38 -0000 Unfortunately this is going to be a very indistinct bug report, but ever since upgrading to 4.10 from 4.9 I am having several problems with mysql. These manifest as programs occasionally failing to connect to the database. Unfortunately I have been unable to track this down as yet due to the fact it only happens once in every few hundred attempts, so trying to actually characterise it is proving almost impossible! Has anyone else seen this ? I am using the system on a test server and am loathe to upgrade the production machines just in case it *isnt* simply some quirk of this machine. -pcf. From owner-freebsd-stable@FreeBSD.ORG Mon May 24 06:54:06 2004 Return-Path: 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 66CF116A4CE for ; Mon, 24 May 2004 06:54:06 -0700 (PDT) Received: from veldy.net (fuggle.veldy.net [209.98.200.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2BC3F43D46 for ; Mon, 24 May 2004 06:54:06 -0700 (PDT) (envelope-from veldy@veldy.net) Received: from localhost (localhost.veldy.net [127.0.0.1]) by veldy.net (Postfix) with ESMTP id DEC216127; Mon, 24 May 2004 08:52:20 -0500 (CDT) Received: from veldy.net ([127.0.0.1]) by localhost (fuggle.veldy.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 92691-06; Mon, 24 May 2004 08:52:18 -0500 (CDT) Received: from 148L241 (localhost.veldy.net [127.0.0.1]) by veldy.net (Postfix) with SMTP id 9DB156113; Mon, 24 May 2004 08:52:18 -0500 (CDT) Message-ID: <001a01c44196$544870f0$321d590a@nic.target.com> From: "Thomas T. Veldhouse" To: , "Pete French" References: Date: Mon, 24 May 2004 08:52:18 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Virus-Scanned: by amavisd-new at veldy.net Subject: Re: Problems with 4.10 and mysql X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 May 2004 13:54:06 -0000 From: "Pete French" > Unfortunately this is going to be a very indistinct bug > report, but ever since upgrading to 4.10 from 4.9 I am > having several problems with mysql. These manifest as > programs occasionally failing to connect to the database. > Unfortunately I have been unable to track this down as yet > due to the fact it only happens once in every few hundred > attempts, so trying to actually characterise it is proving > almost impossible! > > Has anyone else seen this ? I am using the system on a test > server and am loathe to upgrade the production machines just in case > it *isnt* simply some quirk of this machine. > > -pcf. Do you run a firewall (ipfw) on that machine? Perhaps you are hitting stateful connection limits? I used to set this in /etc/sysctl.conf to avoid the issue for me: # increase the number of dynamic firewall rules allowed net.inet.ip.fw.dyn_max=3000 Tom Veldhouse From owner-freebsd-stable@FreeBSD.ORG Mon May 24 06:57:53 2004 Return-Path: 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 332E616A4CE for ; Mon, 24 May 2004 06:57:53 -0700 (PDT) Received: from mail.errors.firstcallgroup.co.uk (mail.errors.firstcallgroup.co.uk [213.167.69.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id E68B443D1F for ; Mon, 24 May 2004 06:57:52 -0700 (PDT) (envelope-from petefrench@keithprowse.com) Received: from smaug.rattatosk ([172.16.1.8]) by mail.errors.firstcallgroup.co.uk with esmtp (Exim 4.22) id 1BSFxA-000OwQ-8S; Mon, 24 May 2004 14:57:20 +0100 Received: from [172.16.1.6] (helo=dilbert.firstcallgroup.co.uk) by smaug.rattatosk with esmtp (Exim 4.22) id 1BSFx9-000AAx-Ve; Mon, 24 May 2004 14:57:19 +0100 Received: from petefrench by dilbert.firstcallgroup.co.uk with local (Exim 4.32; FreeBSD) id 1BSFx9-000LBv-V5; Mon, 24 May 2004 14:57:19 +0100 To: petefrench@keithprowse.com, stable@FreeBSD.ORG, veldy@veldy.net In-Reply-To: <001a01c44196$544870f0$321d590a@nic.target.com> Message-Id: From: Pete French Date: Mon, 24 May 2004 14:57:19 +0100 Subject: Re: Problems with 4.10 and mysql X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 May 2004 13:57:53 -0000 > Do you run a firewall (ipfw) on that machine? Perhaps you are hitting > stateful connection limits? Nope, its just straight out of the box with no firewall. Also the connections are local (the scripts run on the same machine). It worked fine under 4.9 - though someone else has said they have seen the same beahviout under 4.9 -pcf. From owner-freebsd-stable@FreeBSD.ORG Mon May 24 13:04:16 2004 Return-Path: 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 6FF4416A4CE for ; Mon, 24 May 2004 13:04:16 -0700 (PDT) Received: from alpha.lic1.vsi.ru (alpha.lic1.vsi.ru [80.82.34.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0289843D3F for ; Mon, 24 May 2004 13:04:15 -0700 (PDT) (envelope-from viaprog@lic1.vsi.ru) Received: from lic1.vsi.ru (dialup.lic1.vsi.ru [80.82.34.35]) by alpha.lic1.vsi.ru (8.12.10/8.12.10) with ESMTP id i4OK3ous036451 for ; Tue, 25 May 2004 00:03:50 +0400 (MSD) (envelope-from viaprog@lic1.vsi.ru) Message-ID: <40B25524.4070609@lic1.vsi.ru> Date: Tue, 25 May 2004 00:03:48 +0400 From: "Igor A. Valcov" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040429 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: FreeBSD-4.10-RC3 auto reboot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: viaprog@lic1.vsi.ru List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 May 2004 20:04:16 -0000 Hello! I'm have FreeBSD-4.10-RC3. Whem performing operations over the sound (hw.snd.pcm0.vchan=4) system was going down for reboot. Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.10-RC3 #0: Mon May 24 00:20:34 MSD 2004 root@:/usr/src/sys/compile/VIAPROG Timecounter "i8254" frequency 1193182 Hz CPU: Intel(R) Pentium(R) 4 CPU 1.80GHz (1817.91-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf24 Stepping = 4 Features=0x3febfbff real memory = 268369920 (262080K bytes) avail memory = 257769472 (251728K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 FreeBSD/SMP: Multiprocessor motherboard: 1 CPUs cpu0 (BSP): apic id: 0, version: 0x00050014, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00178020, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc0352000. Warning: Pentium 4 CPU: PSE disabled Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 9 entries at 0xc00fded0 apm0: on motherboard apm0: found APM BIOS v1.2, connected at v1.2 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard IOAPIC #0 intpin 16 -> irq 2 IOAPIC #0 intpin 19 -> irq 5 IOAPIC #0 intpin 18 -> irq 9 IOAPIC #0 intpin 23 -> irq 10 IOAPIC #0 intpin 17 -> irq 11 pci0: on pcib0 agp0: mem 0xd0000000-0xd7ffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 irq 2 pci0: at 29.0 irq 2 pci0: at 29.1 irq 5 pci0: at 29.2 irq 9 pci0: at 29.7 irq 10 pcib2: at device 30.0 on pci0 IOAPIC #0 intpin 21 -> irq 16 IOAPIC #0 intpin 22 -> irq 17 pci2: on pcib2 sio0: configured irq 9 not in bitmap of probed irqs 0x20 sio0: <3COM PCI FaxModem> port 0x9000-0x9007 irq 9 at device 0.0 on pci2 sio0: moving to sio2 sio2: type 16550A rl0: port 0x9400-0x94ff mem 0xeb004000-0xeb0040ff irq 16 at device 1.0 o n pci2 rl0: Ethernet address: 00:05:1c:18:5f:50 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto atapci0: port 0xa800-0xa80f,0xa400-0xa403,0xa000-0xa007,0x9c00-0x9c0 3,0x9800-0x9807 mem 0xeb000000-0xeb003fff irq 17 at device 2.0 on pci2 ata2: at 0x9800 on atapci0 ata3: at 0xa000 on atapci0 isab0: at device 31.0 on pci0 isa0: on isab0 atapci1: port 0xcc00-0xcc0f,0xc800-0xc803,0xc400-0xc407,0xc000-0xc003 ,0xbc00-0xbc07 irq 2 at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci1 ata1: at 0x170 irq 15 on atapci1 pci0: (vendor=0x8086, dev=0x24c3) at 31.3 irq 11 pcm0: port 0xd800-0xd83f,0xd400-0xd4ff mem 0xec003000-0xec0030ff,0xec002000-0 xec0021ff irq 11 at device 31.5 on pci0 pcm0: orm0: