From owner-freebsd-stable@FreeBSD.ORG Sun Nov 30 00:01:04 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DE4F2106567B for ; Sun, 30 Nov 2008 00:01:04 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (chello087206045082.chello.pl [87.206.45.82]) by mx1.freebsd.org (Postfix) with ESMTP id 36CC98FC13 for ; Sun, 30 Nov 2008 00:01:03 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 9DE5245C9B; Sun, 30 Nov 2008 01:01:02 +0100 (CET) Received: from localhost (chello087206045082.chello.pl [87.206.45.82]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 77F3445B36; Sun, 30 Nov 2008 01:00:56 +0100 (CET) Date: Sun, 30 Nov 2008 01:00:59 +0100 From: Pawel Jakub Dawidek To: Pete French Message-ID: <20081130000059.GC1494@garage.freebsd.pl> References: <20081129104640.GB1494@garage.freebsd.pl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="4ZLFUWh1odzi/v6L" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 8.0-CURRENT i386 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-stable@freebsd.org Subject: Re: Curious failure of ZFS snapshots 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: Sun, 30 Nov 2008 00:01:04 -0000 --4ZLFUWh1odzi/v6L Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Nov 29, 2008 at 01:01:18PM +0000, Pete French wrote: > > Is there a way for me to reproduce that? >=20 > I am not sure how to reproduce it, as I am unclear as to what > causes is. I have two machines making regular snapshots, one of which > ends up in this state, and one which doesnt. The only difference is > that the one which goes wwrong is actually trying to access the snapshots, > whereas the other is a backup machine where they just sit there. >=20 > What I can try and do is to setup a small system to try and reproduce the > bug on a small file backed zfs system, aandd then maybe email you the > failed image if I can get it to fail. Would that be of any use ? > The current failed image is about 50GB, so I dont have an easy way to > send you that. Is an image of a filesystem with the problem actualll of > any use to you anywway ? It's not file system on-disk structure fault, as far as I understand, because reboot fixes it. I belive it's how you access the snapshots. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --4ZLFUWh1odzi/v6L Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFJMde6ForvXbEpPzQRAq/NAJ9AmrQ5AnbswYgfdCGX1FmO9eR0cgCeL+4z 4tBGvAwXdPtQcTScda2aRGo= =rG3H -----END PGP SIGNATURE----- --4ZLFUWh1odzi/v6L-- From owner-freebsd-stable@FreeBSD.ORG Sun Nov 30 01:05:50 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C3C2C1065673; Sun, 30 Nov 2008 01:05:50 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from constantine.ticketswitch.com (constantine.ticketswitch.com [IPv6:2002:57e0:1d4e:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id 8993C8FC1C; Sun, 30 Nov 2008 01:05:50 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from dilbert.rattatosk ([10.64.50.6] helo=dilbert.ticketswitch.com) by constantine.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1L6aku-0000ZR-Rc; Sun, 30 Nov 2008 01:05:48 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1L6aku-000NAk-Q1; Sun, 30 Nov 2008 01:05:48 +0000 To: pjd@FreeBSD.org In-Reply-To: <20081130000059.GC1494@garage.freebsd.pl> Message-Id: From: Pete French Date: Sun, 30 Nov 2008 01:05:48 +0000 Cc: freebsd-stable@freebsd.org Subject: Re: Curious failure of ZFS snapshots 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: Sun, 30 Nov 2008 01:05:50 -0000 > It's not file system on-disk structure fault, as far as I understand, > because reboot fixes it. I belive it's how you access the snapshots. I was about to say "a reboot doesnt fix it for me" - as I swear i tried that before, but I have discovered you are right, as I just rebooted the server and it is fine. Here is what I am doing - this script is run with an argument '7am' or '7pm' once per day. the mysql database is a slave replication from a master, so there is a continuous trickle of data into it. The symbolic links are there so you can connect to the mysql server and access 'xxx-7am' or 'xxx-7pm' to get a previous version of database 'xxx'. In case its not obvious, the filesystem 'tank/zfs' is mounted on the director '/var/db/mysql'. If you run this for a few cycles it should preseumably break for you too. -pete. ------------------------------------------------------------------- #!/bin/sh SUFFIX=$1 FS_NAME=tank/mysql DB_DIR=/var/db/mysql # First we should make sure we are root if test `/usr/bin/whoami` != "root" then /bin/echo You must be root to run this script exit fi # Check that we have a suffix if test "${SUFFIX}" = "" then /bin/echo "usage: $0 " exit fi # Stop mysql, unlink the links and destroy the snapshot /usr/local/etc/rc.d/mysql-server stop > /dev/null /bin/rm -f ${DB_DIR}/*-${SUFFIX} /sbin/zfs destroy ${FS_NAME}@${SUFFIX} # Create the new (dated) snapshot /bin/date > ${DB_DIR}/SNAPSHOT_DATE /sbin/zfs snapshot ${FS_NAME}@${SUFFIX} /bin/rm -f ${DB_DIR}/SNAPSHOT_DATE # Find all mysql subdirectories and link them /usr/bin/find ${DB_DIR}/ -name '[a-z]*' -type d -maxdepth 1 -print | while read DIR do BASE_DIR=`/usr/bin/basename ${DIR}` /bin/ln -s ${DB_DIR}/.zfs/snapshot/${SUFFIX}/${BASE_DIR} ${DIR}-${SUFFIX} done # Restart mysql /usr/local/etc/rc.d/mysql-server start > /dev/null From owner-freebsd-stable@FreeBSD.ORG Sun Nov 30 13:07:30 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D2460106564A for ; Sun, 30 Nov 2008 13:07:30 +0000 (UTC) (envelope-from hk@alogis.com) Received: from alogis.com (firewall.solit-ag.de [212.184.102.1]) by mx1.freebsd.org (Postfix) with ESMTP id 355128FC18 for ; Sun, 30 Nov 2008 13:07:30 +0000 (UTC) (envelope-from hk@alogis.com) Received: from alogis.com (localhost [127.0.0.1]) by alogis.com (8.13.4/8.13.1) with ESMTP id mAUCnc1G044780; Sun, 30 Nov 2008 13:49:38 +0100 (CET) (envelope-from hk@alogis.com) Received: (from hk@localhost) by alogis.com (8.13.4/8.13.1/Submit) id mAUCncbJ044779; Sun, 30 Nov 2008 13:49:38 +0100 (CET) (envelope-from hk) Date: Sun, 30 Nov 2008 13:49:38 +0100 From: Holger Kipp To: stable@freebsd.org Message-ID: <20081130124938.GA44403@intserv.int1.b.intern> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Cc: Subject: panic: spin lock held too long on 7.1-PRERELEASE (sio) 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: Sun, 30 Nov 2008 13:07:31 -0000 Hi, I currently encounter spin lock 0xc0c83ba8 (sio) held by 0xc6337460 (tid 100005) too long panic: spin lock held too long cpuid=3 on hp server with two dual-core intel xeon (3.8GHz) and 3GB RAM. System is 7.1-PRELEASE last fetched 29.11.2008, 17:58 UTC. This happens with VSCom Card that was previously in use in a 5.3-STABLE system (also hp server, but older hardware) without problems. The card is a 8-port serial card using puc0 and puc1 with 4 ports each. Interestingly, problem seems to occur only if sendfax is using devices attache to puc1. Works without problems at the moment with sendfax only using puc0-sios. See dmesg below. Any ideas what might be causing this, or is this even related to kern/121322, 118044 or 117913? Best regards, Holger Dmesg: Copyright (c) 1992-2008 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 7.1-PRERELEASE #9: Sat Nov 29 18:58:40 CET 2008 root@fax02.dmz-43.intern:/usr/obj/usr/src/sys/FAX Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.80GHz (3800.16-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf4a Stepping = 10 Features=0xbfebfbff Features2=0x659d AMD Features=0x20000000 AMD Features2=0x1 Logical CPUs per core: 2 real memory = 3221172224 (3071 MB) avail memory = 3146608640 (3000 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 6 cpu3 (AP): APIC ID: 7 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard ioapic2 irqs 48-71 on motherboard ioapic3 irqs 72-95 on motherboard ioapic4 irqs 96-119 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x908-0x90b on acpi0 pcib0: on acpi0 pci0: on pcib0 pcib1: at device 2.0 on pci0 pci2: on pcib1 pcib2: at device 0.0 on pci2 pci3: on pcib2 bge0: mem 0xfddf0000-0xfddfffff irq 25 at device 1.0 on pci3 miibus0: on bge0 brgphy0: PHY 1 on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto bge0: Ethernet address: 00:16:35:05:b6:dd bge0: [ITHREAD] bge1: mem 0xfdde0000-0xfddeffff irq 26 at device 1.1 on pci3 miibus1: on bge1 brgphy1: PHY 1 on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto bge1: Ethernet address: 00:16:35:05:b6:dc bge1: [ITHREAD] pcib3: at device 0.2 on pci2 pci4: on pcib3 ciss0: port 0x4000-0x40ff mem 0xfdef0000-0xfdef1fff,0xfde80000-0xfdebffff irq 51 at device 3.0 on pci4 ciss0: [ITHREAD] pcib4: at device 6.0 on pci0 pci5: on pcib4 pcib5: at device 0.0 on pci5 pci6: on pcib5 puc0: port 0x5000-0x501f,0x5020-0x503f mem 0xfdff0000-0xfdff0fff,0xfdfe0000-0xfdfe0fff irq 78 at device 2.0 on pci6 puc0: [FILTER] sio0 on puc0 sio0: type 16550A (multiport master) sio0: [FILTER] sio1 on puc0 sio1: type 16550A (multiport) sio1: [FILTER] sio2 on puc0 sio2: type 16550A (multiport) sio2: [FILTER] sio3 on puc0 sio3: type 16550A (multiport) sio3: [FILTER] puc1: port 0x5040-0x505f,0x5060-0x507f mem 0xfdfd0000-0xfdfd0fff,0xfdfc0000-0xfdfc0fff irq 78 at device 2.1 on pci6 puc1: [FILTER] sio4 on puc1 sio4: type 16550A (multiport) sio4: [FILTER] sio5 on puc1 sio5: type 16550A (multiport) sio5: [FILTER] sio6 on puc1 sio6: type 16550A (multiport) sio6: [FILTER] sio7 on puc1 sio7: type 16550A (multiport) sio7: [FILTER] pcib6: at device 0.2 on pci5 pci10: on pcib6 uhci0: port 0x2000-0x201f irq 16 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: on uhci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: port 0x2020-0x203f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: on uhci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0x2040-0x205f irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] uhci2: [ITHREAD] usb2: on uhci2 usb2: USB revision 1.0 uhub2: on usb2 uhub2: 2 ports with 2 removable, self powered uhci3: port 0x2060-0x207f irq 16 at device 29.3 on pci0 uhci3: [GIANT-LOCKED] uhci3: [ITHREAD] usb3: on uhci3 usb3: USB revision 1.0 uhub3: on usb3 uhub3: 2 ports with 2 removable, self powered ehci0: mem 0xfbef0000-0xfbef03ff irq 23 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: on ehci0 usb4: USB revision 2.0 uhub4: on usb4 uhub4: 8 ports with 8 removable, self powered pcib7: at device 30.0 on pci0 pci1: on pcib7 vgapci0: port 0x3000-0x30ff mem 0xfc000000-0xfcffffff,0xfbff0000-0xfbff0fff at device 3.0 on pci1 pci1: at device 4.0 (no driver attached) pci1: at device 4.2 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x500-0x50f at device 31.1 on pci0 ata0: on atapci0 ata0: [ITHREAD] ata1: on atapci0 ata1: [ITHREAD] acpi_tz0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model Generic PS/2 mouse, device ID 0 sio8: port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio8: type 16550A sio8: [FILTER] fdc0: port 0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FILTER] cpu0: on acpi0 acpi_perf0: on cpu0 p4tcc0: on cpu0 cpu1: on acpi0 est1: on cpu1 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 132d0000132d device_attach: est1 attach returned 6 p4tcc1: on cpu1 cpu2: on acpi0 est2: on cpu2 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 132d0000132d device_attach: est2 attach returned 6 p4tcc2: on cpu2 cpu3: on acpi0 est3: on cpu3 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 132d0000132d device_attach: est3 attach returned 6 p4tcc3: on cpu3 pmtimer0 on isa0 orm0: at iomem 0xc0000-0xc7fff,0xc8000-0xcbfff,0xee000-0xeffff pnpid ORM0000 on isa0 ppc0: parallel port not found. sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ums0: on uhub0 ums0: X report 0x0002 not supported device_attach: ums0 attach returned 6 Timecounters tick every 1.000 msec acd0: CDROM at ata0-master UDMA33 da0 at ciss0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-0 device da0: 135.168MB/s transfers da0: 69459MB (142253280 512 byte sectors: 255H 32S/T 17433C) da1 at ciss0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-0 device da1: 135.168MB/s transfers da1: 138919MB (284506560 512 byte sectors: 255H 32S/T 34866C) SMP: AP CPU #3 Launched! SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! Trying to mount root from ufs:/dev/da0s1a From owner-freebsd-stable@FreeBSD.ORG Sun Nov 30 20:28:09 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 84B921065670 for ; Sun, 30 Nov 2008 20:28:09 +0000 (UTC) (envelope-from cliftonr@lava.net) Received: from outgoing01.lava.net (cake.lava.net [IPv6:2001:1888:0:1:230:48ff:fe5b:3b50]) by mx1.freebsd.org (Postfix) with ESMTP id CCA908FC14 for ; Sun, 30 Nov 2008 20:28:08 +0000 (UTC) (envelope-from cliftonr@lava.net) Received: from malasada.lava.net (malasada.lava.net [64.65.64.17]) by outgoing01.lava.net (Postfix) with ESMTP id B596CD006D for ; Sun, 30 Nov 2008 10:27:57 -1000 (HST) Received: by malasada.lava.net (Postfix, from userid 102) id 646C8153882; Sun, 30 Nov 2008 10:27:57 -1000 (HST) Date: Sun, 30 Nov 2008 10:27:57 -1000 From: Clifton Royston To: FreeBSD-STABLE Message-ID: <20081130202756.GA4036@lava.net> Mail-Followup-To: FreeBSD-STABLE References: <20081125043124.GA18518@sysmon.tcworks.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081125043124.GA18518@sysmon.tcworks.net> User-Agent: Mutt/1.4.2.2i Subject: Re: FreeBSD 7.0-STABLE Jul 23: panic: ffs_blkfree: freeing free frag 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: Sun, 30 Nov 2008 20:28:09 -0000 On Mon, Nov 24, 2008 at 10:31:24PM -0600, Scott Lambert wrote: ... > According to Nagios, it took about 25 minutes to panic, reboot, fsck and > come back up. Funny, it felt a lot longer. > > The gmirror is currently degraded and 'systat -vm 1' is showing 98% > utilization on da0 and 23% utilization on da1 with 35 to 50MB/s on both > da0 and da1. I hadn't looked at the mirror status before the crash. > > 21:42:09 Mon Nov 24 $ gmirror status > Name Status Components > mirror/gm0 DEGRADED da0 (84%) > da1 Just so you know, if you don't shut down normally, the mirror is not marked into a synchronized state, so it usually has to rebuild after a panic or other crash. That's probably unrelated to the crash. -- Clifton -- Clifton Royston -- cliftonr@iandicomputing.com / cliftonr@lava.net President - I and I Computing * http://www.iandicomputing.com/ Custom programming, network design, systems and network consulting services From owner-freebsd-stable@FreeBSD.ORG Sun Nov 30 20:46:59 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 720E8106567B for ; Sun, 30 Nov 2008 20:46:59 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from kennaway-macbookpro.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 4077D8FC19; Sun, 30 Nov 2008 20:46:59 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <4932FBC2.5060807@FreeBSD.org> Date: Sun, 30 Nov 2008 12:46:58 -0800 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.18 (Macintosh/20081105) MIME-Version: 1.0 To: Holger Kipp References: <20081130124938.GA44403@intserv.int1.b.intern> In-Reply-To: <20081130124938.GA44403@intserv.int1.b.intern> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org Subject: Re: panic: spin lock held too long on 7.1-PRERELEASE (sio) 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: Sun, 30 Nov 2008 20:46:59 -0000 Holger Kipp wrote: > Hi, > > I currently encounter > > spin lock 0xc0c83ba8 (sio) held by 0xc6337460 (tid 100005) too long > panic: spin lock held too long > cpuid=3 > > on hp server with two dual-core intel xeon (3.8GHz) and 3GB RAM. > System is 7.1-PRELEASE last fetched 29.11.2008, 17:58 UTC. > > This happens with VSCom Card that was previously in use in a > 5.3-STABLE system (also hp server, but older hardware) without > problems. The card is a 8-port serial card using puc0 and puc1 > with 4 ports each. > > Interestingly, problem seems to occur only if sendfax is using > devices attache to puc1. Works without problems at the moment > with sendfax only using puc0-sios. See dmesg below. > > Any ideas what might be causing this, or is this even related > to kern/121322, 118044 or 117913? Enable WITNESS in your kernel and try to reproduce the problem. It should give additional information about the condition leading to the deadlock. Kris From owner-freebsd-stable@FreeBSD.ORG Mon Dec 1 08:26:08 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4AA23106564A; Mon, 1 Dec 2008 08:26:08 +0000 (UTC) (envelope-from gerrit@pmp.uni-hannover.de) Received: from mrelay1.uni-hannover.de (mrelay1.uni-hannover.de [130.75.2.106]) by mx1.freebsd.org (Postfix) with ESMTP id 7F4C18FC1F; Mon, 1 Dec 2008 08:26:07 +0000 (UTC) (envelope-from gerrit@pmp.uni-hannover.de) Received: from www.pmp.uni-hannover.de (www.pmp.uni-hannover.de [130.75.117.2]) by mrelay1.uni-hannover.de (8.14.2/8.14.2) with ESMTP id mB18Q4S9029746; Mon, 1 Dec 2008 09:26:05 +0100 Received: from pmp.uni-hannover.de (arc.pmp.uni-hannover.de [130.75.117.1]) by www.pmp.uni-hannover.de (Postfix) with SMTP id 389AE4F; Mon, 1 Dec 2008 09:26:04 +0100 (CET) Date: Mon, 1 Dec 2008 09:26:04 +0100 From: Gerrit =?ISO-8859-1?Q?K=FChn?= To: Pawel Jakub Dawidek Message-Id: <20081201092604.da46d948.gerrit@pmp.uni-hannover.de> In-Reply-To: <20081129104640.GB1494@garage.freebsd.pl> References: <20081121151518.9f4f6af8.gerrit@pmp.uni-hannover.de> <20081121154153.a741e391.gerrit@pmp.uni-hannover.de> <200811210816.35573.fjwcash@gmail.com> <20081129104640.GB1494@garage.freebsd.pl> Organization: Albert-Einstein-Institut (MPI =?ISO-8859-1?Q?f=FCr?= Gravitationsphysik & IGP =?ISO-8859-1?Q?Universit=E4t?= Hannover) X-Mailer: Sylpheed 2.4.8 (GTK+ 2.12.11; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-PMX-Version: 5.4.1.325704, Antispam-Engine: 2.6.0.325393, Antispam-Data: 2008.12.1.81339 Cc: freebsd-stable@freebsd.org Subject: Re: Curious failure of ZFS snapshots 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: Mon, 01 Dec 2008 08:26:08 -0000 On Sat, 29 Nov 2008 11:46:40 +0100 Pawel Jakub Dawidek wrote about Re: Curious failure of ZFS snapshots: PJD> > > GK> mclane# ll /tank/home/pt/.zfs/ PJD> > > GK> ls: snapshot: Bad file descriptor PJD> > > GK> total 0 PJD> Is there a way for me to reproduce that? None that I could tell you right now. This was on a machine which uses zfs send/receive to backup its zfs filesystem to a backup server. Only one out of 6 or 7 zfs filesystems showed this problem. After rebooting it went away and did not appear again since then. cu Gerrit From owner-freebsd-stable@FreeBSD.ORG Mon Dec 1 08:32:35 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EA667106564A; Mon, 1 Dec 2008 08:32:35 +0000 (UTC) (envelope-from gerrit@pmp.uni-hannover.de) Received: from mrelay1.uni-hannover.de (mrelay1.uni-hannover.de [130.75.2.106]) by mx1.freebsd.org (Postfix) with ESMTP id 4CC068FC0C; Mon, 1 Dec 2008 08:32:35 +0000 (UTC) (envelope-from gerrit@pmp.uni-hannover.de) Received: from www.pmp.uni-hannover.de (www.pmp.uni-hannover.de [130.75.117.2]) by mrelay1.uni-hannover.de (8.14.2/8.14.2) with ESMTP id mB18WWWX030114; Mon, 1 Dec 2008 09:32:33 +0100 Received: from pmp.uni-hannover.de (arc.pmp.uni-hannover.de [130.75.117.1]) by www.pmp.uni-hannover.de (Postfix) with SMTP id 1568672; Mon, 1 Dec 2008 09:32:32 +0100 (CET) Date: Mon, 1 Dec 2008 09:32:32 +0100 From: Gerrit =?ISO-8859-1?Q?K=FChn?= To: pjd@freebsd.org Message-Id: <20081201093232.59394eec.gerrit@pmp.uni-hannover.de> In-Reply-To: References: <20081130000059.GC1494@garage.freebsd.pl> Organization: Albert-Einstein-Institut (MPI =?ISO-8859-1?Q?f=FCr?= Gravitationsphysik & IGP =?ISO-8859-1?Q?Universit=E4t?= Hannover) X-Mailer: Sylpheed 2.4.8 (GTK+ 2.12.11; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-PMX-Version: 5.4.1.325704, Antispam-Engine: 2.6.0.325393, Antispam-Data: 2008.12.1.82242 Cc: freebsd-stable@freebsd.org, Pete French Subject: Re: Curious failure of ZFS snapshots 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: Mon, 01 Dec 2008 08:32:36 -0000 On Sun, 30 Nov 2008 01:05:48 +0000 Pete French wrote about Re: Curious failure of ZFS snapshots: PF> Here is what I am doing - this script is run with an argument '7am' or PF> '7pm' once per day. the mysql database is a slave replication from a PF> master, so there is a continuous trickle of data into it. The symbolic PF> links are there so you can connect to the mysql server and access PF> 'xxx-7am' or 'xxx-7pm' to get a previous version of database 'xxx'. PF> In case its not obvious, the filesystem 'tank/zfs' is mounted on the PF> director '/var/db/mysql'. If you run this for a few cycles it should PF> preseumably break for you too. If you think it will be useful I can also post my scripts. However, as I did not see the problem again so far, it might be the case that I messed something up manually while developing the scripts one or two weeks ago. As mentioned, even the unaccessible zfs snapshots did send/receive fine, so internally zfs seems to be happy (only unmounting them was a bad idea :-). cu Gerrit From owner-freebsd-stable@FreeBSD.ORG Mon Dec 1 08:46:50 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 604FD1065670; Mon, 1 Dec 2008 08:46:50 +0000 (UTC) (envelope-from vulture@netvulture.com) Received: from mail.consult-scs.com (MAIL.CONSULT-SCS.COM [208.81.60.67]) by mx1.freebsd.org (Postfix) with ESMTP id 4613F8FC14; Mon, 1 Dec 2008 08:46:50 +0000 (UTC) (envelope-from vulture@netvulture.com) Received: from [127.0.0.1] (host72.netvulture.com [208.201.244.72]) (Authenticated sender: vulture@netvulture.com) by mail.consult-scs.com (Postfix) with ESMTPA id 05A241642486; Mon, 1 Dec 2008 00:28:00 -0800 (PST) Message-ID: <4933A00E.7080201@netvulture.com> Date: Mon, 01 Dec 2008 00:27:58 -0800 From: Jonathan Feally User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: freebsd-stable@freebsd.org, freebsd-net@freebsd.org Content-Type: multipart/mixed; boundary="------------010705070407050807080507" X-SCS-MailScanner-Information: Please contact the ISP for more information X-MailScanner-ID: 05A241642486.49AC2 X-SCS-MailScanner: Found to be clean X-SCS-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-204.399, required 4, autolearn=not spam, ALL_TRUSTED -1.80, BAYES_00 -2.60, INIT_RECVD_OUR_AUTH -200.00) X-SCS-MailScanner-From: vulture@netvulture.com Cc: Subject: dhclient doing DISCOVER with bad IP checksum - bge 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: Mon, 01 Dec 2008 08:46:50 -0000 This is a multi-part message in MIME format. --------------010705070407050807080507 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sorry for the cross-post, but this could be either lists problem. I have 2 boxes running 7-STABLE as of 20081130, both i386 SMP. One is running ISC DHCPD 3.0.x from recent ports, and the other dhclient from make world. The server is refusing to answer the DISCOVER request, as it thinks the IP checksum is wrong, which tcpdump also confirms. Other DHCP clients are working fine on this network, so I do not believe it to be the network, server or dhcpd. Server is running a 2 Port Intel card - em driver. Client is a Dell PE1750 with 2 onboard NIC's - bge driver. I have tried turning off both RXCSUM and TXCSUM on both the client and server machines with no luck. I also tried the second NIC on the server with the same result. This setup was working just a couple of weeks ago, and the only thing that has changed is updating the src for a make world. PXE booting this server does result in an IP being issued, so it is pointing towards something new/changed in 7-STABLE. I have attached a 3 packet dump of the DISCOVER requests. Can anybody shed some light on this for me? Thanks, -Jon -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --------------010705070407050807080507 Content-Type: application/octet-stream; name="dhclient_badcsum.cap" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="dhclient_badcsum.cap" 1MOyoQIABAAAAAAAAAAAAP//AAABAAAAuFgzSURyCgBWAQAAVgEAAP////// /wAPH2mL5QgARRABSAAAAAAQEV6WAAAAAP////8ARABDATSkzwEBBgC1qjdA AAAAAAAAAAAAAAAAAAAAAAAAAAAADx9pi+UAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAY4JTYzUBATIEwKgC8z0HAQAPH2mL5QwHZGF0YW1hbjcIARwCeQMPBgz/ AAAAAAAAAAAAAAAAAAAAAAAAAAAAAL9YM0lmdAoAVgEAAFYBAAD///////8A Dx9pi+UIAEUQAUgAAAAAEBHulgAAAAD/////AEQAQwE0pMgBAQYAtao3QAAH AAAAAAAAAAAAAAAAAAAAAAAAAA8faYvlAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AGOCU2M1AQEyBMCoAvM9BwEADx9pi+UMB2RhdGFtYW43CAEcAnkDDwYM/wAA AAAAAAAAAAAAAAAAAAAAAAAAAADOWDNJWXYKAFYBAABWAQAA////////AA8f aYvlCABFEAFIAAAAABAR7pYAAAAA/////wBEAEMBNKS5AQEGALWqN0AAFgAA AAAAAAAAAAAAAAAAAAAAAAAPH2mL5QAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABj glNjNQEBMgTAqALzPQcBAA8faYvlDAdkYXRhbWFuNwgBHAJ5Aw8GDP8AAAAA AAAAAAAAAAAAAAAAAAAAAAAA --------------010705070407050807080507-- From owner-freebsd-stable@FreeBSD.ORG Mon Dec 1 11:13:44 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 875631065679 for ; Mon, 1 Dec 2008 11:13:44 +0000 (UTC) (envelope-from dewayne_freebsd@yahoo.com) Received: from n24.bullet.mail.mud.yahoo.com (n24.bullet.mail.mud.yahoo.com [68.142.206.163]) by mx1.freebsd.org (Postfix) with SMTP id 4E7658FC24 for ; Mon, 1 Dec 2008 11:13:44 +0000 (UTC) (envelope-from dewayne_freebsd@yahoo.com) Received: from [68.142.200.226] by n24.bullet.mail.mud.yahoo.com with NNFMP; 01 Dec 2008 11:00:05 -0000 Received: from [68.142.201.243] by t7.bullet.mud.yahoo.com with NNFMP; 01 Dec 2008 11:00:05 -0000 Received: from [127.0.0.1] by omp404.mail.mud.yahoo.com with NNFMP; 01 Dec 2008 11:00:05 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 295557.32093.bm@omp404.mail.mud.yahoo.com Received: (qmail 95394 invoked by uid 60001); 1 Dec 2008 11:00:04 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=VVRqdzYnEY319xUAOFNJQUKFrxxu2vdAb0aYunKU+y8tPC0AP11hE/o+TSFMVeb8CHszmOEgTvLc8SeZEwMQV6GfSQss6V2WwkTD7qG+Lo4uGmVJGIXgGIimaKKaBWn1FEngI3UUUuC7+rLSSud7u2uk4IxLvEkwwHtQ3Omnlao=; X-YMail-OSG: ltexrvgVM1k4xSC0wsCl8G7Igi0xijm.KBPCSBdOOKLRCc4oaKF3Npq1OFmVSY4lvF8sTm7qAEuQFJO8NGIdsaBKioPKur3R2fTd2vf7LlExXLHiE0wKGKJ_uaCGHvAcOaZPakhnFSKtCrOPOXyUSu0bXZ8- Received: from [58.172.113.127] by web46412.mail.sp1.yahoo.com via HTTP; Mon, 01 Dec 2008 03:00:03 PST X-Mailer: YahooMailWebService/0.7.260.1 Date: Mon, 1 Dec 2008 03:00:03 -0800 (PST) From: Dewayne Geraghty To: freebsd-stable@freebsd.org In-Reply-To: <20081201092604.da46d948.gerrit@pmp.uni-hannover.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Message-ID: <478434.94854.qm@web46412.mail.sp1.yahoo.com> Subject: make distribution halts during install (7.1Prerelease today) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dewayne_freebsd@yahoo.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Dec 2008 11:13:44 -0000 The "make distribution" phase of a full build of 7.1 Prerelease, sourced to= day (Mon Dec 1 10:34:45 UTC 2008), unfortunately failed. make distribution DESTDIR=3D/differentplace=20 failed (see below), however the following worked ok: buildkernel, installke= rnerl, buildworld, installworld. Two systems (a Uni and Dual processor) wer= e used and both failed at the same point. Both building systems were succe= ssful in building/installing kernel and world for themselves and for a diff= erent DESTDIR (per the Handbook). Only the make distribution failed (a clu= e?) The repeated attempts to make distribution DESTDIR=3DX failed at the same l= ocation (see below). The error message suggestions incorrect parameters to = "install". Advise/guidance welcome. #cd /usr/src && make DESTDIR=3D/usr/k_brfw-d distribution cd /usr/src/etc; MAKEOBJDIRPREFIX=3D/usr/obj MACHINE_ARCH=3Di386 MACHINE= =3Di386 CPUTYPE=3D GROFF_BIN_PATH=3D/usr/obj/usr/src/tmp/legacy/usr/bin = GROFF_FONT_PATH=3D/usr/obj/usr/src/tmp/legacy/usr/share/groff_font GROFF_T= MAC_PATH=3D/usr/obj/usr/src/tmp/legacy/usr/share/tmac PATH=3D/usr/obj/usr/s= rc/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src= /tmp/legacy/usr/games:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/us= r/bin:/usr/obj/usr/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin make dis= tribution cd /usr/src/etc; install -o root -g wheel -m 644 amd.map apmd.conf auth.c= onf crontab csh.cshrc csh.login csh.logout devd.conf devfs.conf ddb.conf = dhclient.conf disktab fbtab freebsd-update.conf ftpusers gettytab group h= osts hosts.allow hosts.equiv hosts.lpd inetd.conf libalias.conf login.acce= ss login.conf mac.conf motd netconfig network.subr networks newsyslog.conf= nsswitch.conf portsnap.conf pf.os phones profile protocols rc rc.bsdexte= nded rc.firewall rc.firewall6 rc.initdiskless rc.sendmail rc.shutdown rc.= subr remote rpc services shells snmpd.config sysctl.conf syslog.conf etc.= i386/ttys /usr/src/etc/../gnu/usr.bin/man/manpath/manpath.config /usr/src= /etc/../usr.bin/mail/misc/mail.rc /usr/src/etc/../usr.bin/locate/locate/lo= cate.rc nscd.conf /usr/k_brfw-d/etc; cap_mkdb -l /usr/k_brfw-d/etc/login.c= onf; install -o root -g wheel -m 755 netstart pccard_ether rc.suspend rc.= resume /usr/k_brfw-d/etc; install -o root -g wheel -m 600=20 master.passwd nsmb.conf opieaccess /usr/k_brfw-d/etc; pwd_mkdb -L -i -p -= d /usr/k_brfw-d/etc /usr/k_brfw-d/etc/master.passwd install: wrong number or types of arguments usage: install [-bCcpSsv] [-B suffix] [-f flags] [-g group] [-m mode] [-o owner] file1 file2 install [-bCcpSsv] [-B suffix] [-f flags] [-g group] [-m mode] [-o owner] file1 ... fileN directory install -d [-v] [-g group] [-m mode] [-o owner] directory ... *** Error code 64 Stop in /usr/src/etc. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. I also tried various CPUTYPES to ensure that all parameters to make, were p= opulated. Having spent most of the day building kernels/worlds and gstripp= ing, gjournalling and building a lot of ports, the package is looking prett= y good. I hope that my explanation is concise it's been a long day and I'm= stuck. Regards, Dewayne.=0A=0A=0A Start your day with Yahoo!7 and win a Sony = Bravia TV. Enter now http://au.docs.yahoo.com/homepageset/?p1=3Dother&p2=3D= au&p3=3Dtagline From owner-freebsd-stable@FreeBSD.ORG Mon Dec 1 14:17:44 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 841AA10656D8 for ; Mon, 1 Dec 2008 14:17:44 +0000 (UTC) (envelope-from janm@transactionware.com) Received: from mail.transactionware.com (mail.transactionware.com [203.14.245.7]) by mx1.freebsd.org (Postfix) with SMTP id 7C6DB8FC27 for ; Mon, 1 Dec 2008 14:17:43 +0000 (UTC) (envelope-from janm@transactionware.com) Received: (qmail 39639 invoked from network); 1 Dec 2008 14:00:52 -0000 Received: from midgard.transactionware.com (192.168.1.55) by dm.transactionware.com with SMTP; 1 Dec 2008 14:00:52 -0000 Received: (qmail 2644 invoked by uid 907); 1 Dec 2008 14:00:29 -0000 Received: from midgard.transactionware.com (HELO jmlaptop) (192.168.1.55) by midgard.transactionware.com (qpsmtpd/0.40) with SMTP; Tue, 02 Dec 2008 01:00:29 +1100 Message-ID: <2515BCEE3A2F4CBA8FFB9F1C052924AA@jmlaptop> From: "Jan Mikkelsen" To: Date: Tue, 2 Dec 2008 01:00:23 +1100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5512 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 Subject: 7.1-PRERELEASE: arcmsr write performance problem 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: Mon, 01 Dec 2008 14:17:44 -0000 Hi, I am seeing extremely poor performance (~100kB/s) when untaring large tar files into fresh ufs filesystems. I see the problem with softupdates and without softupdates but with an async mount. This is a Supermicro X7DB8 board, 4GB, 2 x Xeon 5140. Sample gstat output: dT: 1.033s w: 1.000s L(q) ops/s r/s kBps ms/r w/s kBps ms/w %busy Name 585 61 0 0 0.0 61 170 13812.0 100.1| da2 I see ms/w start at about 200ms with a ~3MB/s throughput, and then I see ms/w rise and kBps drop. ms/w goes as high as 16-20s, and then suddenly drops back down to about 200ms. Using iostat, while the performance is high(er), kb/t is 64kB, as the problem starts it drops towards 2kB. Copying a single large file doesn't exhibit this problem, although throughput isn't great (~3-5MB/s). However, that's better that 100kB/s. arcmsr0: mem 0xd8900000-0xd8900fff,0xd8000000-0xd83fffff irq 16 at device 14.0 > on pci10 ARECA RAID ADAPTER0: Driver Version 1.20.00.15 2007-10-07 ARECA RAID ADAPTER0: FIRMWARE VERSION V1.46 2008-08-06 arcmsr0: [ITHREAD] There are eight disks connected in a RAID-6 configuration. The controller's cache is write-through and the disks' write caches are disabled. NCQ is enabled on the drives. The same hardware when it ran 6.3-p1 didn't have this problem. However, the system BIOS was updated at the same time as the operating system (in an attempt to solve a recent em problem), so it is possible that it is a BIOS related problem. The same build on an entirely different machine with an aac controller and SAS disks also doesn't show this problem. Running 'devinfo -r' doesn't list arcmsr as having an interrupt at all. (see below). That strikes me as odd; checking another machine that is still running 6.2 with an arcmsr controller, I can see the interrupt just fine. So: - Does anyone have any suggestions? - Is it normal for arcmsr to not show an interrupt in the output from devinfo in 7.1? Full dmesg, devinfo below. Thanks, Jan Mikkelsen Copyright (c) 1992-2008 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 7.1-PRERELEASE #0: Mon Dec 1 14:53:12 EST 2008 root@valhalla.transactionware.com:/home/janm/p4/freebsd-image-std-2008.2/work/base-freebsd/home/janm/p4/freebsd-image-std-2008.2/FreeBSD/src/sys/TW-SMP Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(R) CPU 5140 @ 2.33GHz (2333.35-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x6f6 Stepping = 6 Features=0xbfebfbff Features2=0x4e3bd AMD Features=0x20100800 AMD Features2=0x1 Cores per package: 2 usable memory = 4280651776 (4082 MB) avail memory = 4117843968 (3927 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 6 cpu3 (AP): APIC ID: 7 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 2.0 on pci0 pci1: on pcib1 pcib2: irq 16 at device 0.0 on pci1 pci2: on pcib2 pcib3: irq 16 at device 0.0 on pci2 pci3: on pcib3 pcib4: at device 0.0 on pci3 pci4: on pcib4 ahd0: port 0x2400-0x24ff,0x2000-0x20ff mem 0xd8500000-0xd8501fff irq 16 at device 2.0 on pci4 ahd0: [ITHREAD] aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs ahd1: port 0x2c00-0x2cff,0x2800-0x28ff mem 0xd8502000-0xd8503fff irq 17 at device 2.1 on pci4 ahd1: [ITHREAD] aic7902: Ultra320 Wide Channel B, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs pcib5: at device 0.2 on pci3 pci5: on pcib5 bge0: mem 0xd8600000-0xd860ffff irq 16 at device 1.0 on pci5 miibus0: on bge0 brgphy0: PHY 1 on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto bge0: Ethernet address: 00:40:f4:66:b1:56 bge0: [ITHREAD] pcib6: irq 18 at device 2.0 on pci2 pci6: on pcib6 em0: port 0x3000-0x301f mem 0xd8400000-0xd841ffff irq 18 at device 0.0 on pci6 em0: Using MSI interrupt em0: [FILTER] em0: Ethernet address: 00:30:48:31:67:86 em1: port 0x3020-0x303f mem 0xd8420000-0xd843ffff irq 19 at device 0.1 on pci6 em1: Using MSI interrupt em1: [FILTER] em1: Ethernet address: 00:30:48:31:67:87 pcib7: at device 0.3 on pci1 pci7: on pcib7 pcib8: at device 4.0 on pci0 pci8: on pcib8 pcib9: at device 6.0 on pci0 pci9: on pcib9 pcib10: at device 0.0 on pci9 pci10: on pcib10 arcmsr0: mem 0xd8900000-0xd8900fff,0xd8000000-0xd83fffff irq 16 at device 14.0 > on pci10 ARECA RAID ADAPTER0: Driver Version 1.20.00.15 2007-10-07 ARECA RAID ADAPTER0: FIRMWARE VERSION V1.46 2008-08-06 arcmsr0: [ITHREAD] pcib11: at device 0.2 on pci9 pci11: on pcib11 pci0: at device 8.0 (no driver attached) pcib12: irq 17 at device 28.0 on pci0 pci12: on pcib12 uhci0: port 0x1800-0x181f irq 17 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: on uhci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: port 0x1820-0x183f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: on uhci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0x1840-0x185f irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] uhci2: [ITHREAD] usb2: on uhci2 usb2: USB revision 1.0 uhub2: on usb2 uhub2: 2 ports with 2 removable, self powered ehci0: mem 0xd8c00400-0xd8c007ff irq 17 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb3: EHCI version 1.0 usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 uhub3: on usb3 uhub3: 6 ports with 6 removable, self powered pcib13: at device 30.0 on pci0 pci13: on pcib13 vgapci0: port 0x4000-0x40ff mem 0xd0000000-0xd7ffffff,0xd8800000-0xd880ffff irq 18 at device 1.0 on pci13 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1860-0x186f at device 31.1 on pci0 ata0: on atapci0 ata0: [ITHREAD] pci0: at device 31.3 (no driver attached) acpi_button0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model Generic PS/2 mouse, device ID 0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio0: [FILTER] sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A sio1: [FILTER] fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FILTER] ppc0: port 0x378-0x37f,0x778-0x77f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppbus0: on ppc0 ppbus0: [ITHREAD] plip0: on ppbus0 plip0: WARNING: using obsoleted IFF_NEEDSGIANT flag lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 ppc0: [GIANT-LOCKED] ppc0: [ITHREAD] cpu0: on acpi0 est0: on cpu0 p4tcc0: on cpu0 cpu1: on acpi0 est1: on cpu1 p4tcc1: on cpu1 cpu2: on acpi0 est2: on cpu2 p4tcc2: on cpu2 cpu3: on acpi0 est3: on cpu3 p4tcc3: on cpu3 orm0: at iomem 0xc0000-0xcafff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec acd0: DVDR at ata0-master UDMA66 Waiting 5 seconds for SCSI devices to settle (probe46:arcmsr0:0:16:0): inquiry data fails comparison at DV1 step da0 at arcmsr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-5 device da0: 166.666MB/s transfers (83.333MHz DT, offset 32, 16bit) da0: 77247MB (158201856 512 byte sectors: 255H 63S/T 9847C) da1 at arcmsr0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-5 device da1: 166.666MB/s transfers (83.333MHz DT, offset 32, 16bit) da1: 953673MB (1953122304 512 byte sectors: 255H 63S/T 121576C) da2 at arcmsr0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-5 device da2: 166.666MB/s transfers (83.333MHz DT, offset 32, 16bit) da2: 800131MB (1638669312 512 byte sectors: 255H 63S/T 102002C) sa0 at ahd1 bus 0 target 6 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 10.000MB/s transfers (10.000MHz, offset 15) SMP: AP CPU #1 Launched! SMP: AP CPU #3 Launched! SMP: AP CPU #2 Launched! Trying to mount root from ufs:/dev/da0s2a This module (opensolaris) contains code covered by the Common Development and Distribution License (CDDL) see http://opensolaris.org/os/licensing/opensolaris_license/ WARNING: ZFS is considered to be an experimental feature in FreeBSD. ZFS filesystem version 6 ZFS storage pool version 6 bge0: link state changed to UP em0: link state changed to UP em1: link state changed to UP nexus0 acpi0 Interrupt request lines: 9 I/O ports: 0x10-0x1f 0x24-0x25 0x28-0x29 0x2c-0x2d 0x2e-0x2f 0x30-0x31 0x34-0x35 0x38-0x39 0x3c-0x3d 0x4e-0x4f 0x50-0x53 0x63 0x65 0x67 0x72-0x77 0x80 0x90-0x9f 0xa4-0xa5 0xa8-0xa9 0xac-0xad 0xb0-0xb5 0xb8-0xb9 0xbc-0xbd 0x295-0x296 0x4d0-0x4d1 0x800-0x80f 0xca2-0xca3 0xca8-0xcaf 0x1000-0x107f 0x1180-0x11bf 0xfe00 I/O memory addresses: 0xe0000000-0xefffffff 0xfe000000-0xfe01ffff 0xfe600000-0xfe6fffff 0xfec80000-0xfec80fff 0xfed1c000-0xfed1ffff 0xfee00000-0xfee0ffff cpu0 acpi_perf0 est0 p4tcc0 cpufreq0 cpu1 acpi_perf1 est1 p4tcc1 cpufreq1 cpu2 acpi_perf2 est2 p4tcc2 cpufreq2 cpu3 acpi_perf3 est3 p4tcc3 cpufreq3 pcib0 pci0 hostb0 pcib1 pci1 pcib2 pci2 pcib3 pci3 pcib4 pci4 ahd0 Interrupt request lines: 16 I/O ports: 0x2000-0x20ff 0x2400-0x24ff I/O memory addresses: 0xd8500000-0xd8501fff ahd1 Interrupt request lines: 17 I/O ports: 0x2800-0x28ff 0x2c00-0x2cff I/O memory addresses: 0xd8502000-0xd8503fff pcib5 pci5 bge0 I/O memory addresses: 0xd8600000-0xd860ffff miibus0 brgphy0 pcib6 pci6 em0 Interrupt request lines: 256 I/O ports: 0x3000-0x301f I/O memory addresses: 0xd8400000-0xd841ffff em1 Interrupt request lines: 257 I/O ports: 0x3020-0x303f I/O memory addresses: 0xd8420000-0xd843ffff pcib7 pci7 pcib8 pci8 pcib9 pci9 pcib10 pci10 arcmsr0 I/O memory addresses: 0xd8000000-0xd83fffff 0xd8900000-0xd8900fff pcib11 pci11 hostb1 hostb2 hostb3 hostb4 hostb5 hostb6 hostb7 pcib12 pci12 uhci0 I/O ports: 0x1800-0x181f usb0 uhub0 uhci1 Interrupt request lines: 19 I/O ports: 0x1820-0x183f usb1 uhub1 uhci2 Interrupt request lines: 18 I/O ports: 0x1840-0x185f usb2 uhub2 ehci0 I/O memory addresses: 0xd8c00400-0xd8c007ff usb3 uhub3 pcib13 pci13 vgapci0 I/O ports: 0x4000-0x40ff I/O memory addresses: 0xd0000000-0xd7ffffff 0xd8800000-0xd880ffff isab0 isa0 sc0 vga0 I/O ports: 0x3c0-0x3df I/O memory addresses: 0xa0000-0xbffff orm0 I/O memory addresses: 0xc0000-0xcafff atapci0 I/O ports: 0x170-0x177 0x1f0-0x1f7 0x376 0x3f6 0x1860-0x186f ata0 Interrupt request lines: 14 acd0 acpi_sysresource0 atdma0 fpupnp0 attimer0 attimer1 pci_link0 pci_link1 pci_link2 pci_link3 pci_link4 pci_link5 pci_link6 pci_link7 atkbdc0 I/O ports: 0x60 0x64 atkbd0 Interrupt request lines: 1 psm0 Interrupt request lines: 12 psmcpnp0 sio0 Interrupt request lines: 4 I/O ports: 0x3f8-0x3ff sio1 Interrupt request lines: 3 I/O ports: 0x2f8-0x2ff fdc0 Interrupt request lines: 6 DMA request lines: 2 I/O ports: 0x3f0-0x3f5 0x3f7 ppc0 Interrupt request lines: 7 DMA request lines: 3 I/O ports: 0x378-0x37f ppbus0 plip0 lpt0 ppi0 acpi_button0 acpi_timer0 ACPI I/O ports: 0x1008-0x100b apic0 I/O memory addresses: 0xfec00000-0xfec0001f ram0 I/O memory addresses: 0x0-0x9dfff 0x100000-0xcff4ffff 0x100000000-0x12fffffff From owner-freebsd-stable@FreeBSD.ORG Mon Dec 1 18:20:39 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6335D1065676 for ; Mon, 1 Dec 2008 18:20:39 +0000 (UTC) (envelope-from jrhett@netconsonance.com) Received: from mail.netconsonance.com (mail.netconsonance.com [198.207.204.4]) by mx1.freebsd.org (Postfix) with ESMTP id 283B18FC1D for ; Mon, 1 Dec 2008 18:20:39 +0000 (UTC) (envelope-from jrhett@netconsonance.com) Received: from [10.66.240.106] (public-wireless.sv.svcolo.com [64.13.135.30]) (authenticated bits=0) by mail.netconsonance.com (8.14.1/8.14.2) with ESMTP id mB1IKTnC087627; Mon, 1 Dec 2008 10:20:29 -0800 (PST) (envelope-from jrhett@netconsonance.com) X-Virus-Scanned: amavisd-new at netconsonance.com X-Spam-Flag: NO X-Spam-Score: -1.059 X-Spam-Level: X-Spam-Status: No, score=-1.059 tagged_above=-999 required=3.5 tests=[ALL_TRUSTED=-1.44, AWL=0.381] Message-Id: From: Jo Rhett To: Ken Smith In-Reply-To: <1227733967.83059.1.camel@neo.cse.buffalo.edu> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Date: Mon, 1 Dec 2008 10:20:23 -0800 References: <84E1EC10-5323-4A8C-AD60-31142621DB32@netconsonance.com> <200810271151.47366.jhb@freebsd.org> <280616DD-A58F-4AE5-AB03-92C5F2C244EC@netconsonance.com> <1227733967.83059.1.camel@neo.cse.buffalo.edu> X-Mailer: Apple Mail (2.929.2) Cc: freebsd-stable Stable Subject: Re: Can I get a committer to mark this bug as blocking 6.4-RELEASE ? 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: Mon, 01 Dec 2008 18:20:39 -0000 On Nov 26, 2008, at 1:12 PM, Ken Smith wrote: > Unfortunately no. As John indicated in the earlier thread BIOS > issues tend to be extremely hard to diagnose and so far it seems > like its specific to this one motherboard. > > Given this problem does cause issues with installs I'd be willing > to provide ISOs built at the point we've done the Errata Notice that > fixes the problem. But its too nebulous an issue to hold up the > release itself for. It does *not* cause an issue with installs. Installs work fine. It prevents booting an installed operating system. This appears to affect *ALL* of the Intel multi-cpu motherboards, including 3 generations of Rackable systems. The only reason it is nebulous is because absolutely nobody bothered to investigate the issue. I've been asking for what information would help. I've offered to setup serial consoles, or even ship systems, to anyone who would work on this problem. This is very big problem that will affect thousands of freebsd servers. Ken, the complete lack of action taken by FreeBSD to even CONSIDER investigating a significant bug reported during the testing process is shocking. And it truly puts a lie to those who continue to claim that we should be more active in the testing process. Every time I have done this, I'd found significant issues that affect a significant portion of the user base and COMPLETELY prevent deployment of a given release, and absolutely nothing has been done to even investigate the reports, nevermind address them. Congradulations. Good Job. If you aren't going to accept bug reports, why exactly do you release testing candidates at all? -- Jo Rhett Net Consonance : consonant endings by net philanthropy, open source and other randomness From owner-freebsd-stable@FreeBSD.ORG Mon Dec 1 18:22:39 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8F6E51065677 for ; Mon, 1 Dec 2008 18:22:39 +0000 (UTC) (envelope-from jrhett@netconsonance.com) Received: from mail.netconsonance.com (mail.netconsonance.com [198.207.204.4]) by mx1.freebsd.org (Postfix) with ESMTP id 71C388FC20 for ; Mon, 1 Dec 2008 18:22:39 +0000 (UTC) (envelope-from jrhett@netconsonance.com) Received: from [10.66.240.106] (public-wireless.sv.svcolo.com [64.13.135.30]) (authenticated bits=0) by mail.netconsonance.com (8.14.1/8.14.2) with ESMTP id mB1IMa9O087722; Mon, 1 Dec 2008 10:22:36 -0800 (PST) (envelope-from jrhett@netconsonance.com) X-Virus-Scanned: amavisd-new at netconsonance.com X-Spam-Flag: NO X-Spam-Score: -1.06 X-Spam-Level: X-Spam-Status: No, score=-1.06 tagged_above=-999 required=3.5 tests=[ALL_TRUSTED=-1.44, AWL=0.380] Message-Id: <31DE68A5-D3CB-4C33-86E6-515581B425E1@netconsonance.com> From: Jo Rhett To: Andriy Gapon In-Reply-To: <492FF127.807@icyb.net.ua> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Date: Mon, 1 Dec 2008 10:22:31 -0800 References: <4912E462.4090608@icyb.net.ua> <491586B9.2020303@vwsoft.com> <4919851B.7050800@icyb.net.ua> <492FF127.807@icyb.net.ua> X-Mailer: Apple Mail (2.929.2) Cc: FreeBSD Stable , freebsd-usb@freebsd.org Subject: Re: usb keyboard dying at loader prompt 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: Mon, 01 Dec 2008 18:22:39 -0000 Just FYI we are seeing the exact same problem with PS/2 keyboards and the 6.4 loader, so this may not be a USB-only issue. The complete lack of response to serious bug reports about 6.4-REL is fairly shocking. On Nov 28, 2008, at 5:24 AM, Andriy Gapon wrote: > I did more testing and it seems that our loader does have something to > do with the problem. > > If I boot to memtest86 the keyboard keeps working. > If I pause boot menu, wait for many minutes, the keyboard still works. > If I escape to loader prompt, this when the keyboard stops working > after > a few seconds. > > Not sure how to explain this. > I think I've seen some changes to reduce memory usage of loader, I > will > try them to see if that would make any difference for my situation. > > > -- > Andriy Gapon > _______________________________________________ > 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 > " -- Jo Rhett Net Consonance : consonant endings by net philanthropy, open source and other randomness From owner-freebsd-stable@FreeBSD.ORG Mon Dec 1 19:30:30 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C6046106568C for ; Mon, 1 Dec 2008 19:30:30 +0000 (UTC) (envelope-from kensmith@cse.Buffalo.EDU) Received: from phoebe.cse.buffalo.edu (phoebe.cse.buffalo.edu [128.205.32.89]) by mx1.freebsd.org (Postfix) with ESMTP id 7EF8A8FC27 for ; Mon, 1 Dec 2008 19:30:30 +0000 (UTC) (envelope-from kensmith@cse.Buffalo.EDU) Received: from [128.205.32.76] (bauer.cse.buffalo.edu [128.205.32.76]) (authenticated bits=0) by phoebe.cse.buffalo.edu (8.14.1/8.13.7) with ESMTP id mB1JUM03061859 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 1 Dec 2008 14:30:22 -0500 (EST) (envelope-from kensmith@cse.buffalo.edu) From: Ken Smith To: Jo Rhett In-Reply-To: References: <84E1EC10-5323-4A8C-AD60-31142621DB32@netconsonance.com> <200810271151.47366.jhb@freebsd.org> <280616DD-A58F-4AE5-AB03-92C5F2C244EC@netconsonance.com> <1227733967.83059.1.camel@neo.cse.buffalo.edu> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-vh/iv9y6o2sXMCNjByrG" Organization: U. Buffalo CSE Department Date: Mon, 01 Dec 2008 14:30:22 -0500 Message-Id: <1228159822.15856.45.camel@bauer.cse.buffalo.edu> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 FreeBSD GNOME Team Port X-DCC-Buffalo.EDU-Metrics: phoebe.cse.buffalo.edu 1029; Body=0 Fuz1=0 Fuz2=0 X-Spam-Status: No, score=-4.0 required=5.0 tests=RCVD_IN_DNSWL_MED autolearn=failed version=3.2.3 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on phoebe.cse.buffalo.edu Cc: freebsd-stable Stable Subject: Re: Can I get a committer to mark this bug as blocking 6.4-RELEASE ? 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: Mon, 01 Dec 2008 19:30:30 -0000 --=-vh/iv9y6o2sXMCNjByrG Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Mon, 2008-12-01 at 10:20 -0800, Jo Rhett wrote: > On Nov 26, 2008, at 1:12 PM, Ken Smith wrote: > > Unfortunately no. As John indicated in the earlier thread BIOS > > issues tend to be extremely hard to diagnose and so far it seems > > like its specific to this one motherboard. > > > > Given this problem does cause issues with installs I'd be willing > > to provide ISOs built at the point we've done the Errata Notice that > > fixes the problem. But its too nebulous an issue to hold up the > > release itself for. >=20 > It does *not* cause an issue with installs. Installs work fine. It =20 > prevents booting an installed operating system. This appears to =20 > affect *ALL* of the Intel multi-cpu motherboards, including 3 =20 > generations of Rackable systems. Understood, I guess I wasn't quite specific enough. The machine not being able to boot what got installed on its disk I consider an install problem. To date this is the first mention I've seen of it affecting more than one specific machine type. I might have missed it but I can't recall you mentioning this affected more than one particular machine. And it does not seem to affect *ALL* of the Intel multi-cpu motherboards. > The only reason it is nebulous is because absolutely nobody bothered =20 > to investigate the issue. I've been asking for what information would =20 > help. I've offered to setup serial consoles, or even ship systems, to =20 > anyone who would work on this problem. Both John and Xin Li have chimed in on the two threads I've seen that are related to this specific topic. John diagnosed it as a issue with the BIOS. That's what makes it a nebulous problem. When working on those sorts of things most people liken it to "Whack-a-mole". > This is very big problem that will affect thousands of freebsd servers. Its still not clear it will affect thousands of servers. The same set of changes got made to stable/7 as were done to stable/6, and the test builds for the 7.1 release have been seeing much more testing than the test builds for the 6.4 release. If the problem was as wide-spread as you're suggesting we'd likely have seen a lot more reports and that factored into the decision about whether to go ahead or not. This all left me with a decision. My choices were to back out the BTX changes that were known to fix boot issues with certain motherboards and enabled booting from USB devices or leave things as they are. The motherboards that didn't boot with the older code had no work-around. The motherboards that did boot with the older code but not the newer code do have a work-around (use the old loader). Decisions like that suck, no matter which choice I make it's wrong. Holding the release until all bios issues get resolved isn't a viable option because of the "Whack-a-mole" thing mentioned above. Fix it for one and two break. It takes a lot of time/work to settle into what seems to work for the widest set of machines. > Ken, the complete lack of action taken by FreeBSD to even CONSIDER =20 > investigating a significant bug reported during the testing process is =20 > shocking. And it truly puts a lie to those who continue to claim that =20 > we should be more active in the testing process. Every time I have =20 > done this, I'd found significant issues that affect a significant =20 > portion of the user base and COMPLETELY prevent deployment of a given =20 > release, and absolutely nothing has been done to even investigate the =20 > reports, nevermind address them. >=20 > Congradulations. Good Job. If you aren't going to accept bug =20 > reports, why exactly do you release testing candidates at all? So you're saying John and Xin Li's responses (Xin Li's questions still un-answered) to you show a complete lack to even consider investigating it? I know from past email threads your preference is for 6.X right now but as a test point if you aren't totally fried over this whole thing it would still be useful to know for sure if the issue exists with 7.1 test builds. If yes it eliminates a variety of possibilities and helps focus on the exact problem. --=20 Ken Smith - From there to here, from here to | kensmith@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | --=-vh/iv9y6o2sXMCNjByrG Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEABECAAYFAkk0O04ACgkQ/G14VSmup/bHUACbB2lpUaUPgbUTFxAZBBFtJwVT eXgAniLrWRlhr3J/D0ZmfT9znqkho4/2 =+YW9 -----END PGP SIGNATURE----- --=-vh/iv9y6o2sXMCNjByrG-- From owner-freebsd-stable@FreeBSD.ORG Mon Dec 1 20:12:06 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 359371065670 for ; Mon, 1 Dec 2008 20:12:06 +0000 (UTC) (envelope-from jrhett@netconsonance.com) Received: from mail.netconsonance.com (mail.netconsonance.com [198.207.204.4]) by mx1.freebsd.org (Postfix) with ESMTP id 104478FC0A for ; Mon, 1 Dec 2008 20:12:06 +0000 (UTC) (envelope-from jrhett@netconsonance.com) Received: from [10.66.240.106] (public-wireless.sv.svcolo.com [64.13.135.30]) (authenticated bits=0) by mail.netconsonance.com (8.14.1/8.14.2) with ESMTP id mB1KBupW092033; Mon, 1 Dec 2008 12:11:56 -0800 (PST) (envelope-from jrhett@netconsonance.com) X-Virus-Scanned: amavisd-new at netconsonance.com X-Spam-Flag: NO X-Spam-Score: -0.442 X-Spam-Level: X-Spam-Status: No, score=-0.442 tagged_above=-999 required=3.5 tests=[ALL_TRUSTED=-1.44, AWL=-0.242, SARE_LWSHORTT=1.24] Message-Id: From: Jo Rhett To: Ken Smith In-Reply-To: <1228159822.15856.45.camel@bauer.cse.buffalo.edu> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Date: Mon, 1 Dec 2008 12:11:50 -0800 References: <84E1EC10-5323-4A8C-AD60-31142621DB32@netconsonance.com> <200810271151.47366.jhb@freebsd.org> <280616DD-A58F-4AE5-AB03-92C5F2C244EC@netconsonance.com> <1227733967.83059.1.camel@neo.cse.buffalo.edu> <1228159822.15856.45.camel@bauer.cse.buffalo.edu> X-Mailer: Apple Mail (2.929.2) Cc: freebsd-stable Stable Subject: Re: Can I get a committer to mark this bug as blocking 6.4-RELEASE ? 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: Mon, 01 Dec 2008 20:12:06 -0000 On Dec 1, 2008, at 11:30 AM, Ken Smith wrote: > Both John and Xin Li have chimed in on the two threads I've seen that > are related to this specific topic. John diagnosed it as a issue with > the BIOS. That's what makes it a nebulous problem. When working on > those sorts of things most people liken it to "Whack-a-mole". Diagnosed without testing. John never asked for any more information than the page fault description from me. When I asked what else to test and offered to supply systems for testing he stopped responding. Xin Li proposed a work-around that would have castrated the systems. It might work, but it wasn't a useful workaround so I deferred testing and focused on trying to get someone to address the real problem. >> This is very big problem that will affect thousands of freebsd >> servers. > > Its still not clear it will affect thousands of servers. Um... Rackable. Rackable ships cabinets full of systems to people that run FreeBSD. They don't sell to home or small corporate users, period. Any problem that affects a standard Rackable build will by definition affect thousands of systems. (much like any standard Dell or HP server build) > This all left me with a decision. My choices were to back out the BTX > changes that were known to fix boot issues with certain motherboards > and > enabled booting from USB devices or leave things as they are. Or do some more testing and determine the problem and fix it. I had a stack of systems demonstrating the problem. I could have shipped one to each freebsd developer you wanted to work on it. If you were willing to identify the affect source code and relevant gdb traps I would have happily worked on the source directly if that is what it took. I would test. I would supply console access and build systems. I would ship them to anyone who wanted one in their hot little hands. I would investigate the source code myself with a mere hour of "here's the relevant bits you need to consider" training. You could have done *anything* that suited your needs for testing. Instead you did nothing. > The > motherboards that didn't boot with the older code had no work-around. > The motherboards that did boot with the older code but not the newer > code do have a work-around (use the old loader). Not true. I tested this, installing the old loader and it did not change the problem. As reported. > Decisions like that > suck, no matter which choice I make it's wrong. Holding the release > until all bios issues get resolved isn't a viable option because of > the > "Whack-a-mole" thing mentioned above. Fix it for one and two > break. It > takes a lot of time/work to settle into what seems to work for the > widest set of machines. Break the boot loader for a very wide variety of systems rather than spend EVEN A SINGLE HOUR trying to diagnose the boot problem? Ken, your diagnosis here would make sense if ANY diagnosis had been attempted. This could be a trivial problem. It could be solved with 5 minutes of actually looking at it. What happened here is that you proceeded WITHOUT EVEN TRYING. > So you're saying John and Xin Li's responses (Xin Li's questions still > un-answered) to you show a complete lack to even consider > investigating > it? No actual diagnosis was done. I'm sorry, but if I pull my car up to my mechanic's garage and he makes a diagnosis of "no idea what's wrong" without even popping the hood, yeah that counts as "didn't even consider investigating" Worse yet, I would happily have done all of the grunt work for the investigation. But I'm not going to start by reading the source tree and making guesses where to look. If someone had given me some useful tests to do, I would have done them. > I know from past email threads your preference is for 6.X right now Not my preference, my ability to justify the evaluation and testing costs based on the support available for a given release. 7.0 doesn't work on this hardware at all. No, I haven't tested 7.1 because 6.4 was the easier testing target and I had thought that the security team was working on fixing the support model. So now we have the brilliance strategy of a long-term support -REL that we will never be able to use. The same stupid stunt that gave us 6.1 which was unusable and 6.2 which worked great but expired at the same time as 6.1. Etc and such forth. 6.5 will likely be short term support again, but the first release we can consider for deployment. > but as a test point if you aren't totally fried over this whole > thing it > would still be useful to know for sure if the issue exists with 7.1 > test > builds. If yes it eliminates a variety of possibilities and helps > focus > on the exact problem. I'm not burnt, but testing 7.1 has no meaningful relevance to my day job until we have a reasonable and working support mechanism. And given that I really pulled out the stops to make sure we had hardware for testing 6.4 (I went a bought a whole stack of systems *JUST FOR THIS*) and filed PRs and followed up, and couldn't get much more than "it sounds like this" kind of response ... seriously, would you invest a lot of time testing a very unstable release under those conditions? I mean jesus, 6.4 is supposed to be truly stable and yet you're willing to ship it not working with dozens of nearly identical reports of the same symptoms for both 6.4 and 7.1? Think seriously about what happened here, and how exactly I'm supposed to convince any executive of the logic of trying to test 7.1, when we're stuck on 6.3 until/if 6.5, which will be screwed for support? I mean seriously? The problem BTW is *EXACTLY* why I proposed the revisions to the support policy I did. Now you're stuck supporting 6.4 for 2 years, and you won't want to release 6.5 because you'll end up supporting three 6.x releases at the same time. Which would suck. Which is exactly what my proposed change to the policy would have fixed. FreeBSD has usually been a solid product on the more stable releases. It's really unfortunate that the release management is so willing to ignore the evidence which leads to major releases with serious flaws, and on top of that seems to take delight in marking the known flawed releases as the long support releases. Brilliance. Just plain brilliant, top to bottom. -- Jo Rhett Net Consonance : consonant endings by net philanthropy, open source and other randomness From owner-freebsd-stable@FreeBSD.ORG Mon Dec 1 20:26:00 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5C0CC106564A for ; Mon, 1 Dec 2008 20:26:00 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.delphij.net (delphij-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:2c9::2]) by mx1.freebsd.org (Postfix) with ESMTP id E8A208FC08 for ; Mon, 1 Dec 2008 20:25:59 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.geekcn.org (tarsier.geekcn.org [211.166.10.233]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tarsier.delphij.net (Postfix) with ESMTPS id E761928448 for ; Tue, 2 Dec 2008 04:25:58 +0800 (CST) Received: from localhost (tarsier.geekcn.org [211.166.10.233]) by tarsier.geekcn.org (Postfix) with ESMTP id A5AF2ED9F23; Tue, 2 Dec 2008 04:25:58 +0800 (CST) X-Virus-Scanned: amavisd-new at geekcn.org Received: from tarsier.geekcn.org ([211.166.10.233]) by localhost (mail.geekcn.org [211.166.10.233]) (amavisd-new, port 10024) with ESMTP id FDgQt7JbH62e; Tue, 2 Dec 2008 04:25:53 +0800 (CST) Received: from charlie.delphij.net (adsl-76-237-33-62.dsl.pltn13.sbcglobal.net [76.237.33.62]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTPSA id CB6F4ED9E9C; Tue, 2 Dec 2008 04:25:51 +0800 (CST) DomainKey-Signature: a=rsa-sha1; s=default; d=delphij.net; c=nofws; q=dns; h=message-id:date:from:reply-to:organization:user-agent: mime-version:to:cc:subject:references:in-reply-to: x-enigmail-version:openpgp:content-type:content-transfer-encoding; b=dWCmyuGocqFIM9jT3F3IyhjqzfqUFYGoJ2776YErydyw7Xm4DXPis+ucEk9TDBcpS sElFtIfxgCuKufNWLkE4g== Message-ID: <4934484C.7060106@delphij.net> Date: Mon, 01 Dec 2008 12:25:48 -0800 From: Xin LI Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.18 (X11/20081125) MIME-Version: 1.0 To: Jo Rhett References: <84E1EC10-5323-4A8C-AD60-31142621DB32@netconsonance.com> <200810271151.47366.jhb@freebsd.org> <280616DD-A58F-4AE5-AB03-92C5F2C244EC@netconsonance.com> <1227733967.83059.1.camel@neo.cse.buffalo.edu> <1228159822.15856.45.camel@bauer.cse.buffalo.edu> In-Reply-To: X-Enigmail-Version: 0.95.7 OpenPGP: id=18EDEBA0; url=http://www.delphij.net/delphij.asc Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Ken Smith , freebsd-stable Stable Subject: Re: Can I get a committer to mark this bug as blocking 6.4-RELEASE ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: d@delphij.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Dec 2008 20:26:00 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jo Rhett wrote: > On Dec 1, 2008, at 11:30 AM, Ken Smith wrote: >> Both John and Xin Li have chimed in on the two threads I've seen that >> are related to this specific topic. John diagnosed it as a issue with >> the BIOS. That's what makes it a nebulous problem. When working on >> those sorts of things most people liken it to "Whack-a-mole". > > Diagnosed without testing. John never asked for any more information > than the page fault description from me. When I asked what else to test > and offered to supply systems for testing he stopped responding. Xin Li > proposed a work-around that would have castrated the systems. It might > work, but it wasn't a useful workaround so I deferred testing and > focused on trying to get someone to address the real problem. What I proposed is, to *narrow down* the problem so we can diagnose further, since nobody has idea at the moment about how the problem was, we do need to have further information, or, to get the whole 6.3->6.4 diff reviewed, which is (in my opinion) not an optimal use of developers' time. Cheers, - -- Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkk0SEwACgkQi+vbBBjt66AbmACeLJgUrf3fp9yNyUXV/T/YvCxT WDkAoL745HKpJw0CogTcZDdvbkMck3uG =0Fg4 -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Mon Dec 1 20:28:05 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D8DD41065679 for ; Mon, 1 Dec 2008 20:28:05 +0000 (UTC) (envelope-from jrhett@netconsonance.com) Received: from mail.netconsonance.com (mail.netconsonance.com [198.207.204.4]) by mx1.freebsd.org (Postfix) with ESMTP id A076C8FC3D for ; Mon, 1 Dec 2008 20:28:05 +0000 (UTC) (envelope-from jrhett@netconsonance.com) Received: from [10.66.240.106] (public-wireless.sv.svcolo.com [64.13.135.30]) (authenticated bits=0) by mail.netconsonance.com (8.14.1/8.14.2) with ESMTP id mB1KS27N092425; Mon, 1 Dec 2008 12:28:03 -0800 (PST) (envelope-from jrhett@netconsonance.com) X-Virus-Scanned: amavisd-new at netconsonance.com X-Spam-Flag: NO X-Spam-Score: -1.063 X-Spam-Level: X-Spam-Status: No, score=-1.063 tagged_above=-999 required=3.5 tests=[ALL_TRUSTED=-1.44, AWL=0.377] From: Jo Rhett To: "George V. Neville-Neil" In-Reply-To: References: <4912E462.4090608@icyb.net.ua> <491586B9.2020303@vwsoft.com> <4919851B.7050800@icyb.net.ua> <492FF127.807@icyb.net.ua> <31DE68A5-D3CB-4C33-86E6-515581B425E1@netconsonance.com> Message-Id: <7A8CC4E4-D59A-4841-8800-A3509C9DB68E@netconsonance.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Date: Mon, 1 Dec 2008 12:27:57 -0800 X-Mailer: Apple Mail (2.929.2) Cc: FreeBSD Stable Subject: confirming bugs is bad behavior, etc. 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: Mon, 01 Dec 2008 20:28:05 -0000 On Dec 1, 2008, at 11:59 AM, George V. Neville-Neil wrote: > I have mostly stayed away from these threads because they've often > devolved into unproductive finger pointing. > > Please leave the hyperbole out of your posts, or at least attempt to > cut it back. People on these lists are working quite hard to solve > problems for the whole of the FreeBSD community and your posts, such > as this one, are not helping us to move forward. My posts have always been directed at solving very real, operational problems with using FreeBSD on server platforms, which is exactly the stated goal for freebsd. I have always offered not only problems, but resources to help test or evaluate the issues, and serious considerations for ways to improve the process. Yes, you're right. Threads I start about real problems always devolve into unproductive finger pointing. That would be the freebsd developers attacking the reporter for identifying a real, operational problem. Take a look at the posts of the FreeBSD developers, and view for yourself the unprofessional attacks and personal insults hurled by them at people who are simply trying to get real problems resolved. And yet, instead of asking your developers to stop violating the posted rules of the mailing list, you are asking a bug reporter who simply informed another bug reporter that their problem was both widespread and not limited to USB devices to stop posting to the list. Because god knows that "yes we saw it too and it's widely reported" is bad behavior. Much worse that personal attacks which are strictly against the list rules. Yes, I'm sure that the personal attacks really do help drive freebsd development forward. Much more so than me bringing resources and actually testing things does. Now that Core has clearly spoken their mind on this issue, by refusing to ask freebsd developers to avoid violating the list charter and then publicly calling out someone for just saying "yeah, it's a widely reported problem" ... leaves any doubt that positive change is going to happen here. Your request is accepted. I'm unsubscribing now. -- Jo Rhett Net Consonance : consonant endings by net philanthropy, open source and other randomness From owner-freebsd-stable@FreeBSD.ORG Mon Dec 1 20:34:07 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3808B1065678 for ; Mon, 1 Dec 2008 20:34:07 +0000 (UTC) (envelope-from jrhett@netconsonance.com) Received: from mail.netconsonance.com (mail.netconsonance.com [198.207.204.4]) by mx1.freebsd.org (Postfix) with ESMTP id EDEB08FC13 for ; Mon, 1 Dec 2008 20:34:06 +0000 (UTC) (envelope-from jrhett@netconsonance.com) Received: from [10.66.240.106] (public-wireless.sv.svcolo.com [64.13.135.30]) (authenticated bits=0) by mail.netconsonance.com (8.14.1/8.14.2) with ESMTP id mB1KXiNN092577; Mon, 1 Dec 2008 12:33:44 -0800 (PST) (envelope-from jrhett@netconsonance.com) X-Virus-Scanned: amavisd-new at netconsonance.com X-Spam-Flag: NO X-Spam-Score: -1.064 X-Spam-Level: X-Spam-Status: No, score=-1.064 tagged_above=-999 required=3.5 tests=[ALL_TRUSTED=-1.44, AWL=0.376] Message-Id: From: Jo Rhett To: d@delphij.net In-Reply-To: <4934484C.7060106@delphij.net> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Date: Mon, 1 Dec 2008 12:33:38 -0800 References: <84E1EC10-5323-4A8C-AD60-31142621DB32@netconsonance.com> <200810271151.47366.jhb@freebsd.org> <280616DD-A58F-4AE5-AB03-92C5F2C244EC@netconsonance.com> <1227733967.83059.1.camel@neo.cse.buffalo.edu> <1228159822.15856.45.camel@bauer.cse.buffalo.edu> <4934484C.7060106@delphij.net> X-Mailer: Apple Mail (2.929.2) Cc: Ken Smith , freebsd-stable Stable Subject: Re: Can I get a committer to mark this bug as blocking 6.4-RELEASE ? 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: Mon, 01 Dec 2008 20:34:07 -0000 On Dec 1, 2008, at 12:25 PM, Xin LI wrote: > What I proposed is, to *narrow down* the problem so we can diagnose > further, since nobody has idea at the moment about how the problem > was, > we do need to have further information, or, to get the whole 6.3->6.4 > diff reviewed, which is (in my opinion) not an optimal use of > developers' time. I got your request at the beginning of a vacation period where I was out of town. I had explicitly requested that 6.4 be blocked for this issue. I didn't think that "just my problem" would be enough to hold it up, but I apparently never even considered that -REL would happen without even responding to my request. Since nobody had responded to my request, and several posts had gone out about more testing for 7.1 (which had the same loader and the same problems) I assumed that 6.4 was similarly delayed. Had anyone said you needed this information pronto I would have canceled my Thanksgiving plans and spent the day in the lab testing this for you. For that matter, I had already pulled a diff of 6.3 to 6.4 and was working my way through it trying to find the relevant parts. If you would have identified the relevant portions, I would have happily tried backing out some of the changes on a per-component basis to figure it out. In short, tell me what you wanted/needed, and I would have done it ASAP. It's apparently irrelevant now. -- Jo Rhett Net Consonance : consonant endings by net philanthropy, open source and other randomness From owner-freebsd-stable@FreeBSD.ORG Mon Dec 1 20:40:47 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C2FFC1065672; Mon, 1 Dec 2008 20:40:47 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from proxy.meer.net (proxy.meer.net [64.13.141.13]) by mx1.freebsd.org (Postfix) with ESMTP id 4E54A8FC1D; Mon, 1 Dec 2008 20:40:47 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from mail.meer.net (mail.meer.net [64.13.141.3]) by proxy.meer.net (8.14.2/8.14.2) with ESMTP id mB1K01uC064161; Mon, 1 Dec 2008 12:00:21 -0800 (PST) (envelope-from gnn@neville-neil.com) Received: from mail2.meer.net (mail2.meer.net [64.13.141.16]) by mail.meer.net (8.13.3/8.13.3/meer) with ESMTP id mB1JxD1Q083632; Mon, 1 Dec 2008 11:59:13 -0800 (PST) (envelope-from gnn@neville-neil.com) Received: from minion.local.neville-neil.com (209.249.190.254.available.above.net [209.249.190.254] (may be forged)) (authenticated bits=0) by mail2.meer.net (8.14.1/8.14.1) with ESMTP id mB1JxDFu029335; Mon, 1 Dec 2008 11:59:13 -0800 (PST) (envelope-from gnn@neville-neil.com) Date: Mon, 01 Dec 2008 14:59:12 -0500 Message-ID: From: "George V. Neville-Neil" To: Jo Rhett In-Reply-To: <31DE68A5-D3CB-4C33-86E6-515581B425E1@netconsonance.com> References: <4912E462.4090608@icyb.net.ua> <491586B9.2020303@vwsoft.com> <4919851B.7050800@icyb.net.ua> <492FF127.807@icyb.net.ua> <31DE68A5-D3CB-4C33-86E6-515581B425E1@netconsonance.com> User-Agent: Wanderlust/2.15.5 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.7 Emacs/22.3 (i386-apple-darwin9.5.0) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Canit-CHI2: 0.50 X-Bayes-Prob: 0.5 (Score 0, tokens from: ) X-Spam-Score: 0.80 () [Tag at 5.00] PORN_RP_SHOCKING X-CanItPRO-Stream: default X-Canit-Stats-ID: 2462937 - b7fd3f763812 X-Scanned-By: CanIt (www . roaringpenguin . com) on 64.13.141.13 Cc: FreeBSD Stable , Andriy Gapon , freebsd-usb@freebsd.org Subject: Re: usb keyboard dying at loader prompt 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: Mon, 01 Dec 2008 20:40:47 -0000 At Mon, 1 Dec 2008 10:22:31 -0800, Jo Rhett wrote: > > Just FYI we are seeing the exact same problem with PS/2 keyboards and > the 6.4 loader, so this may not be a USB-only issue. > > The complete lack of response to serious bug reports about 6.4-REL is > fairly shocking. > Jo, I have mostly stayed away from these threads because they've often devolved into unproductive finger pointing. Please leave the hyperbole out of your posts, or at least attempt to cut it back. People on these lists are working quite hard to solve problems for the whole of the FreeBSD community and your posts, such as this one, are not helping us to move forward. Thanks, George Neville-Neil From owner-freebsd-stable@FreeBSD.ORG Mon Dec 1 20:46:09 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EBD101065672 for ; Mon, 1 Dec 2008 20:46:09 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from proxy.meer.net (proxy.meer.net [64.13.141.13]) by mx1.freebsd.org (Postfix) with ESMTP id C3FEA8FC18 for ; Mon, 1 Dec 2008 20:46:09 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from mail.meer.net (mail.meer.net [64.13.141.3]) by proxy.meer.net (8.14.2/8.14.2) with ESMTP id mB1Kk1UF067750 for ; Mon, 1 Dec 2008 12:46:09 -0800 (PST) (envelope-from gnn@neville-neil.com) Received: from mail2.meer.net (mail2.meer.net [64.13.141.16]) by mail.meer.net (8.13.3/8.13.3/meer) with ESMTP id mB1KiPWw000703 for ; Mon, 1 Dec 2008 12:44:25 -0800 (PST) (envelope-from gnn@neville-neil.com) Received: from minion.local.neville-neil.com (209.249.190.254.available.above.net [209.249.190.254] (may be forged)) (authenticated bits=0) by mail2.meer.net (8.14.1/8.14.1) with ESMTP id mB1KiP8V037647 for ; Mon, 1 Dec 2008 12:44:25 -0800 (PST) (envelope-from gnn@neville-neil.com) Date: Mon, 01 Dec 2008 15:44:24 -0500 Message-ID: From: gnn@freebsd.org To: FreeBSD Stable In-Reply-To: <7A8CC4E4-D59A-4841-8800-A3509C9DB68E@netconsonance.com> References: <4912E462.4090608@icyb.net.ua> <491586B9.2020303@vwsoft.com> <4919851B.7050800@icyb.net.ua> <492FF127.807@icyb.net.ua> <31DE68A5-D3CB-4C33-86E6-515581B425E1@netconsonance.com> <7A8CC4E4-D59A-4841-8800-A3509C9DB68E@netconsonance.com> User-Agent: Wanderlust/2.15.5 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.7 Emacs/22.3 (i386-apple-darwin9.5.0) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Canit-CHI2: 0.50 X-Bayes-Prob: 0.5 (Score 0, tokens from: ) X-Spam-Score: 0.10 () [Tag at 5.00] COMBINED_FROM X-CanItPRO-Stream: default X-Canit-Stats-ID: 2463682 - 6e0490d7bfe2 X-Scanned-By: CanIt (www . roaringpenguin . com) on 64.13.141.13 Subject: Re: confirming bugs is bad behavior, etc. 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: Mon, 01 Dec 2008 20:46:10 -0000 At Mon, 1 Dec 2008 12:27:57 -0800, Jo Rhett wrote: > > Now that Core has clearly spoken their mind on this issue, by refusing > to ask freebsd developers to avoid violating the list charter and then > publicly calling out someone for just saying "yeah, it's a widely > reported problem" ... leaves any doubt that positive change is going > to happen here. > Note that my mail was not marked in any way "From core" but was merely as a list participant. I've always been all for people finding and helping to work through bugs. What I object to is hyperbole and passive aggressiveness. For more on this see here: http://video.google.com/videoplay?docid=-4216011961522818645 If we can identify the issue let's fix it, but let's do it without lots of emotional stuff. Best, George From owner-freebsd-stable@FreeBSD.ORG Mon Dec 1 22:27:15 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5F4D7106564A for ; Mon, 1 Dec 2008 22:27:15 +0000 (UTC) (envelope-from janm@transactionware.com) Received: from mail.transactionware.com (mail.transactionware.com [203.14.245.7]) by mx1.freebsd.org (Postfix) with SMTP id 9E4458FC19 for ; Mon, 1 Dec 2008 22:27:14 +0000 (UTC) (envelope-from janm@transactionware.com) Received: (qmail 53677 invoked from network); 1 Dec 2008 22:27:34 -0000 Received: from midgard.transactionware.com (192.168.1.55) by dm.transactionware.com with SMTP; 1 Dec 2008 22:27:34 -0000 Received: (qmail 14051 invoked by uid 907); 1 Dec 2008 22:27:12 -0000 Received: from midgard.transactionware.com (HELO STUDYPC) (192.168.1.55) by midgard.transactionware.com (qpsmtpd/0.40) with ESMTP; Tue, 02 Dec 2008 09:27:12 +1100 From: "Jan Mikkelsen" To: "'Jo Rhett'" , "'Andriy Gapon'" Date: Tue, 2 Dec 2008 09:27:03 +1100 Message-ID: <459EF5063D85400CB8D57DE9529A4D04@STUDYPC> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6838 Importance: Normal In-Reply-To: <31DE68A5-D3CB-4C33-86E6-515581B425E1@netconsonance.com> Thread-Index: AclT4eTpFdXnCmVfT1a5vocktTfRRQAIUOMg X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 Cc: 'FreeBSD Stable' , freebsd-usb@freebsd.org Subject: RE: usb keyboard dying at loader prompt 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: Mon, 01 Dec 2008 22:27:15 -0000 Hi, > Just FYI we are seeing the exact same problem with PS/2 > keyboards and > the 6.4 loader, so this may not be a USB-only issue. > > [ ... ] > > On Nov 28, 2008, at 5:24 AM, Andriy Gapon wrote: > > I did more testing and it seems that our loader does have > something to > > do with the problem. > > > > If I boot to memtest86 the keyboard keeps working. > > If I pause boot menu, wait for many minutes, the keyboard > still works. > > If I escape to loader prompt, this when the keyboard stops working > > after > > a few seconds. > > > > Not sure how to explain this. > > I think I've seen some changes to reduce memory usage of loader, I > > will > > try them to see if that would make any difference for my situation. I have seen a similar problem on a Sun X4240 with 7.1-PRE. Using the ILOM remote keyboard works at the loader prompt but fails at the root filesystem prompt. I could work around the problem by attaching a different keyboard to the front USB port. Have you tried different keyboards? Regards, Jan. From owner-freebsd-stable@FreeBSD.ORG Mon Dec 1 22:41:34 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 665A91065676 for ; Mon, 1 Dec 2008 22:41:33 +0000 (UTC) (envelope-from janm@transactionware.com) Received: from mail.transactionware.com (mail.transactionware.com [203.14.245.7]) by mx1.freebsd.org (Postfix) with SMTP id A80148FC12 for ; Mon, 1 Dec 2008 22:41:32 +0000 (UTC) (envelope-from janm@transactionware.com) Received: (qmail 54054 invoked from network); 1 Dec 2008 22:41:52 -0000 Received: from midgard.transactionware.com (192.168.1.55) by dm.transactionware.com with SMTP; 1 Dec 2008 22:41:52 -0000 Received: (qmail 14228 invoked by uid 907); 1 Dec 2008 22:41:30 -0000 Received: from midgard.transactionware.com (HELO STUDYPC) (192.168.1.55) by midgard.transactionware.com (qpsmtpd/0.40) with ESMTP; Tue, 02 Dec 2008 09:41:30 +1100 From: "Jan Mikkelsen" To: , "'FreeBSD Stable'" Date: Tue, 2 Dec 2008 09:41:22 +1100 Message-ID: <1A7634CAC3E147CB8B5CDA853E4856D7@STUDYPC> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6838 Importance: Normal Thread-Index: AclUBe9HTTQHEcgLQ5WPl5twJaurjA== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 Cc: Subject: Re: no priority on the console? 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: Mon, 01 Dec 2008 22:41:34 -0000 Hi, > As per my previous message, I've spent about 3 months trying to debug = > a problem that was causing all disk I/O to go very slowly. A first glance this sounds similar to the problem I am having with very = slow I/O on the Areca controller. (see: "7.1-PRERELEASE: arcmsr write performance problem") What controller are you using? Is the write = cache enabled? > One of the things which made this nearly impossible to diagnose was =20 > the absolute lack of priority given to the console. Logging in on the = =20 > console would take 12-15 minutes. Hitting enter on the console would = > usually take between 3 and 5 minutes. Yes, I see this when I get the slow I/O problem. I think this has been = a problem for some time; I have also seen "console freezes" (ssh, console, etc.) on 6.0 and 6.1 systems under SATA load. That was a while ago now (2006?). I also recall others reporting have seen the same problem intermittently. > This doesn't seem right to me. Can someone explain why the console =20 > isn't given a very high priority? Why not? What other mechanism does = =20 > the sysadmin have for debugging, at a time when SSH logins either =20 > fail, or take up to an hour to complete? In my case I could log into the system and start things like iostat and gstat and they kept running while the problem occurred so that I could = see some of what was going on. I could also have what seemed like a = reasonable ssh session with a jail on the same machine. This indicates to me that = it is not the console that is the issue, but rather that the process of = logging into the main machine touches some file that causes it to get caught up = in the slow I/O quagmire. If the problem I am seeing now is the same as the one I saw a few years = ago then I think the nature might have changed. My recollection is that utilities like iostat would also freeze back then, but I can't be sure. I'd like to resolve this problem too. Regards, Jan. From owner-freebsd-stable@FreeBSD.ORG Tue Dec 2 02:34:24 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ECD0E1065676 for ; Tue, 2 Dec 2008 02:34:24 +0000 (UTC) (envelope-from dewayne_freebsd@yahoo.com) Received: from n21.bullet.mail.mud.yahoo.com (n21.bullet.mail.mud.yahoo.com [68.142.206.160]) by mx1.freebsd.org (Postfix) with SMTP id B4C138FC18 for ; Tue, 2 Dec 2008 02:34:24 +0000 (UTC) (envelope-from dewayne_freebsd@yahoo.com) Received: from [68.142.194.244] by n21.bullet.mail.mud.yahoo.com with NNFMP; 02 Dec 2008 02:34:15 -0000 Received: from [68.142.201.241] by t2.bullet.mud.yahoo.com with NNFMP; 02 Dec 2008 02:34:24 -0000 Received: from [127.0.0.1] by omp402.mail.mud.yahoo.com with NNFMP; 02 Dec 2008 02:34:24 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 265740.51947.bm@omp402.mail.mud.yahoo.com Received: (qmail 25461 invoked by uid 60001); 2 Dec 2008 02:34:23 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=28PHmgGt4zevWp5uJ3L0KMtMMY7jvbohUzdyYY6AcMDmRIBIRTm37me7nxMSKXeMuKywcFRCBZMm0V+jUqxG/oG7FmEEf7+ywLRkdNW+dLsymQx61rQpcwOUMkX02iHmefsOE645XNFSyplUm6BEWKXLWh8V/DbaRl7ynk5KFu4=; X-YMail-OSG: 8.FSHWkVM1keLwfmQ2DWDPjtH.AErCVU0c3WCiQ_Unr5hiFG56nsjaPQM0aMu3mkxv_iK_kXJWVTyBK7IWkWyH.5U0vP6xDoNUpCj__uwMfKi8.BI0x2hdfLar.aPZlhWKDdZ00usQYoMbcp7uHY55KFp44- Received: from [58.172.113.127] by web46409.mail.sp1.yahoo.com via HTTP; Mon, 01 Dec 2008 18:34:20 PST X-Mailer: YahooMailWebService/0.7.260.1 Date: Mon, 1 Dec 2008 18:34:20 -0800 (PST) From: Dewayne Geraghty To: freebsd-stable@freebsd.org In-Reply-To: <478434.94854.qm@web46412.mail.sp1.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Message-ID: <798506.9689.qm@web46409.mail.sp1.yahoo.com> Subject: Re: make distribution halts during install (7.1Prerelease today) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dewayne_freebsd@yahoo.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Dec 2008 02:34:25 -0000 My earlier post falls into the embarrassing, wish that I hadn't category. T= o prevent anyone wasting effort, I'm replying. make distribution DESTDIR=3D/newplace requires a=20 make world DESTDIR=3D/newplace as a prerequisite. =20 The earlier post, caused me to believe that there was an error in /usr/bin/= install, when using: make distribution DESTDIR=3D/differentplace The granularity of my testing was inappropriate. Apologies for the distract= ion. =20 Dewayne=0A=0A=0A Start your day with Yahoo!7 and win a Sony Bravia TV.= Enter now http://au.docs.yahoo.com/homepageset/?p1=3Dother&p2=3Dau&p3=3Dta= gline From owner-freebsd-stable@FreeBSD.ORG Tue Dec 2 05:27:12 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 980B81065673; Tue, 2 Dec 2008 05:27:12 +0000 (UTC) (envelope-from vulture@netvulture.com) Received: from mail.consult-scs.com (MAIL.CONSULT-SCS.COM [208.81.60.67]) by mx1.freebsd.org (Postfix) with ESMTP id 8C1B18FC08; Tue, 2 Dec 2008 05:27:12 +0000 (UTC) (envelope-from vulture@netvulture.com) Received: from [127.0.0.1] (host77.netvulture.com [208.201.244.77]) (Authenticated sender: vulture@netvulture.com) by mail.consult-scs.com (Postfix) with ESMTPA id 4F72F1642489; Mon, 1 Dec 2008 21:27:41 -0800 (PST) Message-ID: <4934C733.4020506@netvulture.com> Date: Mon, 01 Dec 2008 21:27:15 -0800 From: Jonathan Feally User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: freebsd-stable@freebsd.org, freebsd-net@freebsd.org References: <4933A00E.7080201@netvulture.com> In-Reply-To: <4933A00E.7080201@netvulture.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SCS-MailScanner-Information: Please contact the ISP for more information X-MailScanner-ID: 4F72F1642489.DAC6B X-SCS-MailScanner: Found to be clean X-SCS-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-204.399, required 4, autolearn=not spam, ALL_TRUSTED -1.80, BAYES_00 -2.60, INIT_RECVD_OUR_AUTH -200.00) X-SCS-MailScanner-From: vulture@netvulture.com Cc: Subject: Re: dhclient doing DISCOVER with bad IP checksum - bge (7.1 show stopper??) 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, 02 Dec 2008 05:27:12 -0000 Can someone please confirm or rule out my issue with dhclient sending bad IP checksum packets. It would really suck if 7.1 was released with a broken DHCP client. Jonathan Feally wrote: > Sorry for the cross-post, but this could be either lists problem. > > I have 2 boxes running 7-STABLE as of 20081130, both i386 SMP. One is > running ISC DHCPD 3.0.x from recent ports, and the other dhclient from > make world. > > The server is refusing to answer the DISCOVER request, as it thinks > the IP checksum is wrong, which tcpdump also confirms. Other DHCP > clients are working fine on this network, so I do not believe it to be > the network, server or dhcpd. > > Server is running a 2 Port Intel card - em driver. > > Client is a Dell PE1750 with 2 onboard NIC's - bge driver. > > I have tried turning off both RXCSUM and TXCSUM on both the client and > server machines with no luck. I also tried the second NIC on the > server with the same result. > > This setup was working just a couple of weeks ago, and the only thing > that has changed is updating the src for a make world. PXE booting > this server does result in an IP being issued, so it is pointing > towards something new/changed in 7-STABLE. > > I have attached a 3 packet dump of the DISCOVER requests. > > Can anybody shed some light on this for me? > > Thanks, -Jon > > ------------------------------------------------------------------------ > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From owner-freebsd-stable@FreeBSD.ORG Tue Dec 2 05:45:31 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B26361065673 for ; Tue, 2 Dec 2008 05:45:31 +0000 (UTC) (envelope-from janm@transactionware.com) Received: from mail.transactionware.com (mail.transactionware.com [203.14.245.7]) by mx1.freebsd.org (Postfix) with SMTP id A31398FC22 for ; Tue, 2 Dec 2008 05:45:30 +0000 (UTC) (envelope-from janm@transactionware.com) Received: (qmail 80933 invoked from network); 2 Dec 2008 05:45:50 -0000 Received: from midgard.transactionware.com (192.168.1.55) by dm.transactionware.com with SMTP; 2 Dec 2008 05:45:50 -0000 Received: (qmail 9538 invoked by uid 907); 2 Dec 2008 05:45:27 -0000 Received: from [192.168.1.32] (HELO [192.168.1.32]) (192.168.1.32) by midgard.transactionware.com (qpsmtpd/0.32) with ESMTP; Tue, 02 Dec 2008 16:45:27 +1100 Message-ID: <4934CB77.30906@transactionware.com> Date: Tue, 02 Dec 2008 16:45:27 +1100 From: Jan Mikkelsen User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <2515BCEE3A2F4CBA8FFB9F1C052924AA@jmlaptop> In-Reply-To: <2515BCEE3A2F4CBA8FFB9F1C052924AA@jmlaptop> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: 7.1-PRERELEASE: arcmsr write performance problem 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, 02 Dec 2008 05:45:31 -0000 Replying to my own post ... I have done a test on the same machine comparing 6.3-p1 to 7.1-PRE. The performance is the expected ~6MB/s (because of the lack of cache) on 6.3-p1, so the BIOS change doesn't seem to be at fault. This seems to be a regression somewhere between 6.3 to 7.1. The Areca driver is the same in 6.3 and 7.1, so the problem seems to be elsewhere. I think this is more than just a "performance" problem. The observations with gstat showing extremely high ms/w values (I have seen them as high as 22000) makes it look like IO completion interrupts are being lost. Any suggestions on where to look next? Are there obvious candidates? Jan Mikkelsen wrote: > Hi, > > I am seeing extremely poor performance (~100kB/s) when untaring large > tar files into fresh ufs filesystems. I see the problem with > softupdates and without softupdates but with an async mount. This is a > Supermicro X7DB8 board, 4GB, 2 x Xeon 5140. > > Sample gstat output: > > dT: 1.033s w: 1.000s > L(q) ops/s r/s kBps ms/r w/s kBps ms/w %busy Name > 585 61 0 0 0.0 61 170 13812.0 100.1| da2 > > I see ms/w start at about 200ms with a ~3MB/s throughput, and then I see > ms/w rise and kBps drop. ms/w goes as high as 16-20s, and then suddenly > drops back down to about 200ms. Using iostat, while the performance is > high(er), kb/t is 64kB, as the problem starts it drops towards 2kB. > > Copying a single large file doesn't exhibit this problem, although > throughput isn't great (~3-5MB/s). However, that's better that 100kB/s. > > arcmsr0: > mem 0xd8900000-0xd8900fff,0xd8000000-0xd83fffff irq 16 at device 14.0 >> on pci10 > ARECA RAID ADAPTER0: Driver Version 1.20.00.15 2007-10-07 > ARECA RAID ADAPTER0: FIRMWARE VERSION V1.46 2008-08-06 > arcmsr0: [ITHREAD] > > There are eight disks connected in a RAID-6 configuration. The > controller's cache is write-through and the disks' write caches are > disabled. NCQ is enabled on the drives. > > The same hardware when it ran 6.3-p1 didn't have this problem. However, > the system BIOS was updated at the same time as the operating system (in > an attempt to solve a recent em problem), so it is possible that it is a > BIOS related problem. The same build on an entirely different machine > with an aac controller and SAS disks also doesn't show this problem. > > Running 'devinfo -r' doesn't list arcmsr as having an interrupt at all. > (see below). That strikes me as odd; checking another machine that is > still running 6.2 with an arcmsr controller, I can see the interrupt > just fine. > > So: > > - Does anyone have any suggestions? > > - Is it normal for arcmsr to not show an interrupt in the output from > devinfo in 7.1? > > Full dmesg, devinfo below. > > Thanks, > > Jan Mikkelsen > > > Copyright (c) 1992-2008 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 is a registered trademark of The FreeBSD Foundation. > FreeBSD 7.1-PRERELEASE #0: Mon Dec 1 14:53:12 EST 2008 > > root@valhalla.transactionware.com:/home/janm/p4/freebsd-image-std-2008.2/work/base-freebsd/home/janm/p4/freebsd-image-std-2008.2/FreeBSD/src/sys/TW-SMP > > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Xeon(R) CPU 5140 @ 2.33GHz (2333.35-MHz > K8-class CPU) > Origin = "GenuineIntel" Id = 0x6f6 Stepping = 6 > Features=0xbfebfbff > > Features2=0x4e3bd > > AMD Features=0x20100800 > AMD Features2=0x1 > Cores per package: 2 > usable memory = 4280651776 (4082 MB) > avail memory = 4117843968 (3927 MB) > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > cpu2 (AP): APIC ID: 6 > cpu3 (AP): APIC ID: 7 > ioapic0 irqs 0-23 on motherboard > ioapic1 irqs 24-47 on motherboard > kbd1 at kbdmux0 > ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) > acpi0: on motherboard > acpi0: [ITHREAD] > acpi0: Power Button (fixed) > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > pcib1: at device 2.0 on pci0 > pci1: on pcib1 > pcib2: irq 16 at device 0.0 on pci1 > pci2: on pcib2 > pcib3: irq 16 at device 0.0 on pci2 > pci3: on pcib3 > pcib4: at device 0.0 on pci3 > pci4: on pcib4 > ahd0: port > 0x2400-0x24ff,0x2000-0x20ff mem 0xd8500000-0xd8501fff irq 16 at device > 2.0 on pci4 > ahd0: [ITHREAD] > aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs > ahd1: port > 0x2c00-0x2cff,0x2800-0x28ff mem 0xd8502000-0xd8503fff irq 17 at device > 2.1 on pci4 > ahd1: [ITHREAD] > aic7902: Ultra320 Wide Channel B, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs > pcib5: at device 0.2 on pci3 > pci5: on pcib5 > bge0: mem > 0xd8600000-0xd860ffff irq 16 at device 1.0 on pci5 > miibus0: on bge0 > brgphy0: PHY 1 on miibus0 > brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > 1000baseT-FDX, auto > bge0: Ethernet address: 00:40:f4:66:b1:56 > bge0: [ITHREAD] > pcib6: irq 18 at device 2.0 on pci2 > pci6: on pcib6 > em0: port 0x3000-0x301f mem > 0xd8400000-0xd841ffff irq 18 at device 0.0 on pci6 > em0: Using MSI interrupt > em0: [FILTER] > em0: Ethernet address: 00:30:48:31:67:86 > em1: port 0x3020-0x303f mem > 0xd8420000-0xd843ffff irq 19 at device 0.1 on pci6 > em1: Using MSI interrupt > em1: [FILTER] > em1: Ethernet address: 00:30:48:31:67:87 > pcib7: at device 0.3 on pci1 > pci7: on pcib7 > pcib8: at device 4.0 on pci0 > pci8: on pcib8 > pcib9: at device 6.0 on pci0 > pci9: on pcib9 > pcib10: at device 0.0 on pci9 > pci10: on pcib10 > arcmsr0: > mem 0xd8900000-0xd8900fff,0xd8000000-0xd83fffff irq 16 at device 14.0 >> on pci10 > ARECA RAID ADAPTER0: Driver Version 1.20.00.15 2007-10-07 > ARECA RAID ADAPTER0: FIRMWARE VERSION V1.46 2008-08-06 > arcmsr0: [ITHREAD] > pcib11: at device 0.2 on pci9 > pci11: on pcib11 > pci0: at device 8.0 (no driver attached) > pcib12: irq 17 at device 28.0 on pci0 > pci12: on pcib12 > uhci0: port > 0x1800-0x181f irq 17 at device 29.0 on pci0 > uhci0: [GIANT-LOCKED] > uhci0: [ITHREAD] > usb0: on uhci0 > usb0: USB revision 1.0 > uhub0: on usb0 > uhub0: 2 ports with 2 removable, self powered > uhci1: port > 0x1820-0x183f irq 19 at device 29.1 on pci0 > uhci1: [GIANT-LOCKED] > uhci1: [ITHREAD] > usb1: on uhci1 > usb1: USB revision 1.0 > uhub1: on usb1 > uhub1: 2 ports with 2 removable, self powered > uhci2: port > 0x1840-0x185f irq 18 at device 29.2 on pci0 > uhci2: [GIANT-LOCKED] > uhci2: [ITHREAD] > usb2: on uhci2 > usb2: USB revision 1.0 > uhub2: on usb2 > uhub2: 2 ports with 2 removable, self powered > ehci0: mem 0xd8c00400-0xd8c007ff irq > 17 at device 29.7 on pci0 > ehci0: [GIANT-LOCKED] > ehci0: [ITHREAD] > usb3: EHCI version 1.0 > usb3: companion controllers, 2 ports each: usb0 usb1 usb2 > usb3: on ehci0 > usb3: USB revision 2.0 > uhub3: on usb3 > uhub3: 6 ports with 6 removable, self powered > pcib13: at device 30.0 on pci0 > pci13: on pcib13 > vgapci0: port 0x4000-0x40ff mem > 0xd0000000-0xd7ffffff,0xd8800000-0xd880ffff irq 18 at device 1.0 on pci13 > isab0: at device 31.0 on pci0 > isa0: on isab0 > atapci0: port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1860-0x186f at device 31.1 on pci0 > ata0: on atapci0 > ata0: [ITHREAD] > pci0: at device 31.3 (no driver attached) > acpi_button0: on acpi0 > atkbdc0: port 0x60,0x64 irq 1 on acpi0 > atkbd0: irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > atkbd0: [ITHREAD] > psm0: irq 12 on atkbdc0 > psm0: [GIANT-LOCKED] > psm0: [ITHREAD] > psm0: model Generic PS/2 mouse, device ID 0 > sio0: configured irq 4 not in bitmap of probed irqs 0 > sio0: port may not be enabled > sio0: configured irq 4 not in bitmap of probed irqs 0 > sio0: port may not be enabled > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on > acpi0 > sio0: type 16550A > sio0: [FILTER] > sio1: configured irq 3 not in bitmap of probed irqs 0 > sio1: port may not be enabled > sio1: configured irq 3 not in bitmap of probed irqs 0 > sio1: port may not be enabled > sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 > sio1: type 16550A > sio1: [FILTER] > fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 > fdc0: [FILTER] > ppc0: port 0x378-0x37f,0x778-0x77f irq 7 drq 3 on acpi0 > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > ppc0: FIFO with 16/16/9 bytes threshold > ppbus0: on ppc0 > ppbus0: [ITHREAD] > plip0: on ppbus0 > plip0: WARNING: using obsoleted IFF_NEEDSGIANT flag > lpt0: on ppbus0 > lpt0: Interrupt-driven port > ppi0: on ppbus0 > ppc0: [GIANT-LOCKED] > ppc0: [ITHREAD] > cpu0: on acpi0 > est0: on cpu0 > p4tcc0: on cpu0 > cpu1: on acpi0 > est1: on cpu1 > p4tcc1: on cpu1 > cpu2: on acpi0 > est2: on cpu2 > p4tcc2: on cpu2 > cpu3: on acpi0 > est3: on cpu3 > p4tcc3: on cpu3 > orm0: at iomem 0xc0000-0xcafff on isa0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > Timecounters tick every 1.000 msec > acd0: DVDR at ata0-master UDMA66 > Waiting 5 seconds for SCSI devices to settle > (probe46:arcmsr0:0:16:0): inquiry data fails comparison at DV1 step > da0 at arcmsr0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-5 device > da0: 166.666MB/s transfers (83.333MHz DT, offset 32, 16bit) > da0: 77247MB (158201856 512 byte sectors: 255H 63S/T 9847C) > da1 at arcmsr0 bus 0 target 1 lun 0 > da1: Fixed Direct Access SCSI-5 device > da1: 166.666MB/s transfers (83.333MHz DT, offset 32, 16bit) > da1: 953673MB (1953122304 512 byte sectors: 255H 63S/T 121576C) > da2 at arcmsr0 bus 0 target 2 lun 0 > da2: Fixed Direct Access SCSI-5 device > da2: 166.666MB/s transfers (83.333MHz DT, offset 32, 16bit) > da2: 800131MB (1638669312 512 byte sectors: 255H 63S/T 102002C) > sa0 at ahd1 bus 0 target 6 lun 0 > sa0: Removable Sequential Access SCSI-2 > device > sa0: 10.000MB/s transfers (10.000MHz, offset 15) > SMP: AP CPU #1 Launched! > SMP: AP CPU #3 Launched! > SMP: AP CPU #2 Launched! > Trying to mount root from ufs:/dev/da0s2a > This module (opensolaris) contains code covered by the > Common Development and Distribution License (CDDL) > see http://opensolaris.org/os/licensing/opensolaris_license/ > WARNING: ZFS is considered to be an experimental feature in FreeBSD. > ZFS filesystem version 6 > ZFS storage pool version 6 > bge0: link state changed to UP > em0: link state changed to UP > em1: link state changed to UP > > > nexus0 > acpi0 > Interrupt request lines: > 9 > I/O ports: > 0x10-0x1f > 0x24-0x25 > 0x28-0x29 > 0x2c-0x2d > 0x2e-0x2f > 0x30-0x31 > 0x34-0x35 > 0x38-0x39 > 0x3c-0x3d > 0x4e-0x4f > 0x50-0x53 > 0x63 > 0x65 > 0x67 > 0x72-0x77 > 0x80 > 0x90-0x9f > 0xa4-0xa5 > 0xa8-0xa9 > 0xac-0xad > 0xb0-0xb5 > 0xb8-0xb9 > 0xbc-0xbd > 0x295-0x296 > 0x4d0-0x4d1 > 0x800-0x80f > 0xca2-0xca3 > 0xca8-0xcaf > 0x1000-0x107f > 0x1180-0x11bf > 0xfe00 > I/O memory addresses: > 0xe0000000-0xefffffff > 0xfe000000-0xfe01ffff > 0xfe600000-0xfe6fffff > 0xfec80000-0xfec80fff > 0xfed1c000-0xfed1ffff > 0xfee00000-0xfee0ffff > cpu0 > acpi_perf0 > est0 > p4tcc0 > cpufreq0 > cpu1 > acpi_perf1 > est1 > p4tcc1 > cpufreq1 > cpu2 > acpi_perf2 > est2 > p4tcc2 > cpufreq2 > cpu3 > acpi_perf3 > est3 > p4tcc3 > cpufreq3 > pcib0 > pci0 > hostb0 > pcib1 > pci1 > pcib2 > pci2 > pcib3 > pci3 > pcib4 > pci4 > ahd0 > Interrupt request lines: > 16 > I/O ports: > 0x2000-0x20ff > 0x2400-0x24ff > I/O memory addresses: > 0xd8500000-0xd8501fff > ahd1 > Interrupt request lines: > 17 > I/O ports: > 0x2800-0x28ff > 0x2c00-0x2cff > I/O memory addresses: > 0xd8502000-0xd8503fff > pcib5 > pci5 > bge0 > I/O memory addresses: > 0xd8600000-0xd860ffff > miibus0 > brgphy0 > pcib6 > pci6 > em0 > Interrupt request lines: > 256 > I/O ports: > 0x3000-0x301f > I/O memory addresses: > 0xd8400000-0xd841ffff > em1 > Interrupt request lines: > 257 > I/O ports: > 0x3020-0x303f > I/O memory addresses: > 0xd8420000-0xd843ffff > pcib7 > pci7 > pcib8 > pci8 > pcib9 > pci9 > pcib10 > pci10 > arcmsr0 > I/O memory addresses: > 0xd8000000-0xd83fffff > 0xd8900000-0xd8900fff > pcib11 > pci11 > hostb1 > hostb2 > hostb3 > hostb4 > hostb5 > hostb6 > hostb7 > pcib12 > pci12 > uhci0 > I/O ports: > 0x1800-0x181f > usb0 > uhub0 > uhci1 > Interrupt request lines: > 19 > I/O ports: > 0x1820-0x183f > usb1 > uhub1 > uhci2 > Interrupt request lines: > 18 > I/O ports: > 0x1840-0x185f > usb2 > uhub2 > ehci0 > I/O memory addresses: > 0xd8c00400-0xd8c007ff > usb3 > uhub3 > pcib13 > pci13 > vgapci0 > I/O ports: > 0x4000-0x40ff > I/O memory addresses: > 0xd0000000-0xd7ffffff > 0xd8800000-0xd880ffff > isab0 > isa0 > sc0 > vga0 > I/O ports: > 0x3c0-0x3df > I/O memory addresses: > 0xa0000-0xbffff > orm0 > I/O memory addresses: > 0xc0000-0xcafff > atapci0 > I/O ports: > 0x170-0x177 > 0x1f0-0x1f7 > 0x376 > 0x3f6 > 0x1860-0x186f > ata0 > Interrupt request lines: > 14 > acd0 > acpi_sysresource0 > atdma0 > fpupnp0 > attimer0 > attimer1 > pci_link0 > pci_link1 > pci_link2 > pci_link3 > pci_link4 > pci_link5 > pci_link6 > pci_link7 > atkbdc0 > I/O ports: > 0x60 > 0x64 > atkbd0 > Interrupt request lines: > 1 > psm0 > Interrupt request lines: > 12 > psmcpnp0 > sio0 > Interrupt request lines: > 4 > I/O ports: > 0x3f8-0x3ff > sio1 > Interrupt request lines: > 3 > I/O ports: > 0x2f8-0x2ff > fdc0 > Interrupt request lines: > 6 > DMA request lines: > 2 > I/O ports: > 0x3f0-0x3f5 > 0x3f7 > ppc0 > Interrupt request lines: > 7 > DMA request lines: > 3 > I/O ports: > 0x378-0x37f > ppbus0 > plip0 > lpt0 > ppi0 > acpi_button0 > acpi_timer0 > ACPI I/O ports: > 0x1008-0x100b > apic0 > I/O memory addresses: > 0xfec00000-0xfec0001f > ram0 > I/O memory addresses: > 0x0-0x9dfff > 0x100000-0xcff4ffff > 0x100000000-0x12fffffff > > _______________________________________________ > 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" From owner-freebsd-stable@FreeBSD.ORG Tue Dec 2 06:50:54 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D5646106568A for ; Tue, 2 Dec 2008 06:50:54 +0000 (UTC) (envelope-from awd@awdcomp.net) Received: from home.awdcomp.net (ppp121-45-10-50.lns10.adl2.internode.on.net [121.45.10.50]) by mx1.freebsd.org (Postfix) with ESMTP id 96D718FC12 for ; Tue, 2 Dec 2008 06:50:54 +0000 (UTC) (envelope-from awd@awdcomp.net) Received: from getafix.abdulla ([192.168.202.99]) by home.awdcomp.net with esmtp (Exim 4.69 (FreeBSD)) (envelope-from ) id 1L7OlV-000JMb-MT for freebsd-stable@freebsd.org; Tue, 02 Dec 2008 16:59:45 +1030 Message-ID: <4934D5C5.4030302@awdcomp.net> Date: Tue, 02 Dec 2008 16:59:25 +1030 From: Andrew User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: 'FreeBSD Stable' Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: exim 4.69 freebsd 7.0 locking issues 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, 02 Dec 2008 06:50:54 -0000 Hi all, Running Exim 4.69 on 7.0-RELEASE-p6 FreeBSD. The box has been recently upgraded from 6.3 (like 24 hours ago). Currently Exim is sending the following lines to the log files. 2008-12-01 19:02:35 Failed to get write lock for /var/spool/exim/db/callout.lockfile: Invalid argument 2008-12-01 19:02:35 Failed to get write lock for /var/spool/exim/db/callout.lockfile: Invalid argument 2008-12-01 19:02:35 1L74Cp-000GRN-3R Cannot lock /var/spool/exim/input//1L74Cp-000GRN-3R-D (22): Invalid argument The permissions are all correct for the spool directories and for Exim itself. It is creating stacks and stacks of 0 byte files in the message spool directory. I have recompiled all the ports but to no avail. I've upgraded 2 other machines with 99.0% the same setup with no issues. The only difference is hostnames/ips and that this machine is running mysql on it. Everything else on the machine (spam-assassin, clamav, mysql) is working fine. Has anybody got any ideas, other than downgrade back to fbsd 6.3? Cheers cya Andrew From owner-freebsd-stable@FreeBSD.ORG Tue Dec 2 06:53:41 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7DC321065679; Tue, 2 Dec 2008 06:53:41 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id 0EF568FC08; Tue, 2 Dec 2008 06:53:40 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (Inchoate.gsoft.com.au [203.31.81.30]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id mB26XjIm060326 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Dec 2008 17:03:45 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-stable@freebsd.org Date: Tue, 2 Dec 2008 17:03:37 +1030 User-Agent: KMail/1.9.10 References: <4933A00E.7080201@netvulture.com> <4934C733.4020506@netvulture.com> In-Reply-To: <4934C733.4020506@netvulture.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart4748134.Xn4Dr6lWPW"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200812021703.44935.doconnor@gsoft.com.au> X-Spam-Score: -3.977 () ALL_TRUSTED,BAYES_00 X-Scanned-By: MIMEDefang 2.63 on 203.31.81.10 Cc: freebsd-net@freebsd.org, Jonathan Feally Subject: Re: dhclient doing DISCOVER with bad IP checksum - bge (7.1 show stopper??) 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, 02 Dec 2008 06:53:41 -0000 --nextPart4748134.Xn4Dr6lWPW Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 02 December 2008 15:57:15 Jonathan Feally wrote: > Can someone please confirm or rule out my issue with dhclient sending > bad IP checksum packets. It would really suck if 7.1 was released with a > broken DHCP client. I had 7.1-PRE (early Octover) send out DHCP requests without issue, althoug= h I=20 don't have that system available now. It was using em card. I have a 7.0-STABLE system with an sk card from July that does DHCP request= s=20 just fine too.. I don't have any bge systems running 7 to test with though sorry.. Does it= =20 always give dud packets or just DHCP? Can you try another card in the clien= t? =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart4748134.Xn4Dr6lWPW Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQBJNNbI5ZPcIHs/zowRAktgAJ407dx5bAwTyUNnfIGV0P6jEPPFkwCfQZWh CBeBrwgKBwnVY4FGljkCP2w= =87ln -----END PGP SIGNATURE----- --nextPart4748134.Xn4Dr6lWPW-- From owner-freebsd-stable@FreeBSD.ORG Tue Dec 2 10:13:30 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4EB071065670 for ; Tue, 2 Dec 2008 10:13:30 +0000 (UTC) (envelope-from dgeo@ec-marseille.fr) Received: from melo.ec-marseille.fr (melo.ec-marseille.fr [147.94.19.139]) by mx1.freebsd.org (Postfix) with ESMTP id F2BE28FC1C for ; Tue, 2 Dec 2008 10:13:29 +0000 (UTC) (envelope-from dgeo@ec-marseille.fr) Received: from localhost (amavis4.serv.int [10.3.0.48]) by melo.ec-marseille.fr (GrosseBox 1743 XXL) with ESMTP id 9F53FACB59 for ; Tue, 2 Dec 2008 10:57:53 +0100 (CET) X-Virus-Scanned: amavisd-new at ec-marseille.fr Received: from melo.ec-marseille.fr ([10.3.0.13]) by localhost (amavis4.serv.int [10.3.0.48]) (amavisd-new, port 10024) with LMTP id wE9QAND6Z1WH for ; Tue, 2 Dec 2008 10:57:53 +0100 (CET) Received: from dgeo.egim-mrs.fr (dgeo.egim-mrs.fr [147.94.19.169]) (Authenticated sender: dgeo) by melo.ec-marseille.fr (GrosseBox 1743 XXL) with ESMTPSA id 401B7ACB57 for ; Tue, 2 Dec 2008 10:57:53 +0100 (CET) Message-ID: <4935069A.8060209@ec-marseille.fr> Date: Tue, 02 Dec 2008 10:57:46 +0100 From: Geoffroy Desvernay User-Agent: Thunderbird 2.0.0.18 (X11/20081123) MIME-Version: 1.0 To: freebsd-stable@freebsd.org X-Enigmail-Version: 0.95.7 OpenPGP: id=017C80AA Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigCD3A6D7F746A74CEB43CA721" Subject: RELENG_7_1: bce driver change generating too much interrupts ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Geoffroy Desvernay , freebsd-stable@freebsd.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Dec 2008 10:13:30 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigCD3A6D7F746A74CEB43CA721 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Since last upgrade, I see much more CPU time "eated" by interrupts (at least 10% cpu in top) (see http://dgeo.perso.ec-marseille.fr/cpu-week.png) The server behave correctly (Or seems to=E2=80=A6), and high interrupt nu= mber seems to come from bce cards (source: systat -vmstat) I just upgraded from "RELENG_7 Mon Sep 8 12:33:06 CEST 2008" to "RELENG_7_1 Sat Nov 29 16:20:35 CET 2008" We have the same machine (dell PE 1950) which have not been upgraded (production use - the two machine are carp(4)-redundant) I don't know if it is related to "SVN rev 184826 on 2008-11-10 22:40:16Z by delphij" patch to sys/dev/bce/if_bce.c If I can help debugging something=E2=80=A6 These are production machines,= but I may test patches or ? on the faulty system. Some clues: Under the very same load (carp interfaces down on other machine), vmstat shows: for newer system: procs memory page disk faults cpu r b w avm fre flt re pi po fr sr mf0 in sy cs us sy id 0 1 1 4806M 460M 649 0 0 0 582 2 0 21770 1270 13653 1 15 85 and for older: procs memory page disk faults cpu r b w avm fre flt re pi po fr sr mf0 in sy cs us sy id 0 1 0 3694M 414M 236 0 0 0 199 17 0 286 317 386 1 1 97 bce-related part of dmesg for the newer system: bce0: mem 0xf4000000-0xf5ffffff irq 16 at device 0.0 on pci9 miibus0: on bce0 bce0: Ethernet address: 00:15:c5:f1:56:f4 bce0: [ITHREAD] bce0: ASIC (0x57081020); Rev (B2); Bus (PCI-X, 64-bit, 133MHz); F/W (0x02090105); Flags( SPLT MFW MSI ) bce1: mem 0xf8000000-0xf9ffffff irq 16 at device 0.0 on pci5 miibus1: on bce1 bce1: Ethernet address: 00:15:c5:f1:56:f2 bce1: [ITHREAD] bce1: ASIC (0x57081020); Rev (B2); Bus (PCI-X, 64-bit, 133MHz); F/W (0x02090105); Flags( SPLT MFW MSI ) And on the older system: bce0: mem 0xf4000000-0xf5ffffff irq 16 at device 0.0 on pci9 miibus0: on bce0 bce0: Ethernet address: 00:15:c5:f1:6a:47 bce0: [ITHREAD] bce0: ASIC (0x57081020); Rev (B2); Bus (PCI-X, 64-bit, 133MHz); F/W (0x02090105); Flags( MFW MSI ) bce1: mem 0xf8000000-0xf9ffffff irq 16 at device 0.0 on pci5 miibus1: on bce1 bce1: Ethernet address: 00:15:c5:f1:6a:45 bce1: [ITHREAD] bce1: ASIC (0x57081020); Rev (B2); Bus (PCI-X, 64-bit, 133MHz); F/W (0x02090105); Flags( MFW MSI ) --=20 Geoffroy Desvernay Ecole Centrale de Marseille --------------enigCD3A6D7F746A74CEB43CA721 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkk1BqAACgkQGbFYzwF8gKpr8wCePV+QlUMCTLLsXDkXUbloma/j 9XEAnjSlSox0B1leCuGRuX8lsb8EyDtU =ulkO -----END PGP SIGNATURE----- --------------enigCD3A6D7F746A74CEB43CA721-- From owner-freebsd-stable@FreeBSD.ORG Tue Dec 2 11:47:57 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 871C4106564A for ; Tue, 2 Dec 2008 11:47:57 +0000 (UTC) (envelope-from rajkumars@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.29]) by mx1.freebsd.org (Postfix) with ESMTP id 409F78FC08 for ; Tue, 2 Dec 2008 11:47:56 +0000 (UTC) (envelope-from rajkumars@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so1174175ywe.13 for ; Tue, 02 Dec 2008 03:47:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=mtO56eGkqBhXzUY72mIhFb9LxLXDaWSzlvuNOmwoRUs=; b=O9/UIRt0lwP+zAQFnan05+EzlLPUHEbXHNAkUtdFbDwwXKQdpJeCIt8v610291HQ2g yWtTbstj0ijhEPvy4LccAVYErilXVhZ2BtZFBVSXDOo4u9wXuDY6/7BN8DT4Oz1f/wU/ 5pCbst/TiJWrs+3uk4irRgWSESXVGx6EC8CR8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=XMOKlfkcX2jQCD6PbESaH8WOaW6l8U8GFentdc4T/eLjuopcCVtA+GtB4F04B8QbfQ F8Dmr/qSUvHDZ8A9pnjNXNJR6eYYmlboq/PNzSCfPvWw+U5pLO3cUNj+eaZmmXxxSrs6 nNj5VkiPx0H0gXwoWbZfD5FG07AOFWFEnPW4Q= Received: by 10.143.16.9 with SMTP id t9mr4863098wfi.329.1228218475954; Tue, 02 Dec 2008 03:47:55 -0800 (PST) Received: by 10.143.167.2 with HTTP; Tue, 2 Dec 2008 03:47:55 -0800 (PST) Message-ID: <64de5c8b0812020347v2c8eb928q48de999292681378@mail.gmail.com> Date: Tue, 2 Dec 2008 17:17:55 +0530 From: "Rajkumar S" To: dev@pfsense.com, freebsd-stable@freebsd.org In-Reply-To: <64de5c8b0811242310l14932467kdcef55ab48322b23@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <64de5c8b0811242310l14932467kdcef55ab48322b23@mail.gmail.com> Cc: Subject: Re: ioctl DIOCSMBR: Inappropriate ioctl for device 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, 02 Dec 2008 11:47:57 -0000 On Tue, Nov 25, 2008 at 12:40 PM, Rajkumar S wrote: > boot0cfg: /dev/ad2: Class not found > boot0cfg: /dev/ad2: ioctl DIOCSMBR: Inappropriate ioctl for device I found the reason for this error: I need to set kern.geom.debugflags=16 before executing this command. raj From owner-freebsd-stable@FreeBSD.ORG Tue Dec 2 12:27:40 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CCE971065672; Tue, 2 Dec 2008 12:27:40 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.16.84]) by mx1.freebsd.org (Postfix) with ESMTP id 869E68FC17; Tue, 2 Dec 2008 12:27:40 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by kabab.cs.huji.ac.il with esmtp id 1L7Tjl-000Ert-J6; Tue, 02 Dec 2008 13:48:17 +0200 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 02 Dec 2008 13:48:17 +0200 From: Danny Braniss Message-ID: Cc: freebsd-hackers@freebsd.org Subject: btx/pxeboot problem 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, 02 Dec 2008 12:27:40 -0000 latest pxeboot (7.1): mother-board NIC/LOM CPU ------------- ------- --- Intel SWV25 em xeon works fine SUN X2200 bge amd works fine DELL PE 2950 bce xeon failes 95% of the times hangs or goes into btx dump regs. mode :-) Intel SE7320VP21 msk xeon failes 50% of the times - hangs pxeboot with btx.S 1.45 2008/02/27 23:35:39, works fine. so it seems that changes since 1.45 have fixed it for some, but it brakes for others :-). I can help testing, but btx is way out of my league. danny From owner-freebsd-stable@FreeBSD.ORG Tue Dec 2 12:41:05 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 31368106564A for ; Tue, 2 Dec 2008 12:41:05 +0000 (UTC) (envelope-from dkelly@hiwaay.net) Received: from smtp.knology.net (smtp.knology.net [24.214.63.101]) by mx1.freebsd.org (Postfix) with ESMTP id BDE588FC17 for ; Tue, 2 Dec 2008 12:41:04 +0000 (UTC) (envelope-from dkelly@hiwaay.net) Received: (qmail 26689 invoked by uid 0); 2 Dec 2008 12:14:21 -0000 Received: from unknown (HELO ?10.0.0.187?) (75.76.211.79) by smtp5.knology.net with SMTP; 2 Dec 2008 12:14:21 -0000 In-Reply-To: <4934CB77.30906@transactionware.com> References: <2515BCEE3A2F4CBA8FFB9F1C052924AA@jmlaptop> <4934CB77.30906@transactionware.com> Mime-Version: 1.0 (Apple Message framework v753.1) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <34C71E28-F128-4F83-80EF-75768172A59D@hiwaay.net> Content-Transfer-Encoding: 7bit From: David Kelly Date: Tue, 2 Dec 2008 06:14:20 -0600 To: Jan Mikkelsen X-Mailer: Apple Mail (2.753.1) Cc: freebsd-stable@freebsd.org Subject: Re: 7.1-PRERELEASE: arcmsr write performance problem X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@freebsd.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Dec 2008 12:41:05 -0000 On Dec 1, 2008, at 11:45 PM, Jan Mikkelsen wrote: > Replying to my own post ... > > I have done a test on the same machine comparing 6.3-p1 to 7.1- > PRE. The performance is the expected ~6MB/s (because of the lack > of cache) on 6.3-p1, so the BIOS change doesn't seem to be at fault. > > This seems to be a regression somewhere between 6.3 to 7.1. The > Areca driver is the same in 6.3 and 7.1, so the problem seems to be > elsewhere. > > I think this is more than just a "performance" problem. The > observations with gstat showing extremely high ms/w values (I have > seen them as high as 22000) makes it look like IO completion > interrupts are being lost. > > Any suggestions on where to look next? Are there obvious candidates? ATA maximum block transfer has dropped from 128k to 64k in 7.x. Am not sure where the handle is to tweak it back up but has slowed peak thruput on my Dell PE400SC. Can watch with "systat -v" Worse, I have a stripped array of 2 drives that won't transfer more than 43k at a chunk because apparently the stripe metadata didn't align nicely on 64k multiples. -- David Kelly N4HHE, dkelly@HiWAAY.net ======================================================================== Whom computers would destroy, they must first drive mad. From owner-freebsd-stable@FreeBSD.ORG Tue Dec 2 13:19:20 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2B0371065670 for ; Tue, 2 Dec 2008 13:19:20 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id DE97F8FC1D for ; Tue, 2 Dec 2008 13:19:19 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost1.sentex.ca (8.14.3/8.14.3) with ESMTP id mB2DJHFe035946 for ; Tue, 2 Dec 2008 08:19:17 -0500 (EST) (envelope-from mike@sentex.net) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.8/8.13.3) with ESMTP id mB2DJGJx003807 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 2 Dec 2008 08:19:16 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <200812021319.mB2DJGJx003807@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Tue, 02 Dec 2008 08:19:17 -0500 To: freebsd-stable@freebsd.org From: Mike Tancsa Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18 Subject: repeatable crash on RELENG7 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, 02 Dec 2008 13:19:20 -0000 While trying to speed up nanobsd builds, I mounted /usr/obj on a ramdisk and found my box crashing. Thinking it might be hardware, I tried a separate machine, but with the same results. I have 4G of ram (i386). Am I just running out of some kernel memory ? If so, is there anything I can adjust to prevent this, yet still use mfs in this way ? mdconfig -a -t malloc -s 1800M newfs /dev/md0 mount /dev/md0 /usr/obj/ time make -j4 buildworld > /var/log/build.out in the middle of the buildworld on the serial console (after adding witness etc) g_vfs_done():md0[WRITE(offset=1752924160, length=6144)]error = 28 g_vfs_done():md0[WRITE(offset=1752952832, length=4096)]error = 28 g_vfs_done():md0[WRITE(offset=1753006080, length=14336)]error = 28 g_vfs_done():md0[WRITE(offset=1753020416, length=2048)]error = 28 g_vfs_done():md0[WRITE(offset=1753202688, length=81920)]error = 28 g_vfs_done():md0[WRITE(offset=1191755776, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=1191886848, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=1192017920, length=131072)]error = 28 panic: kmem_malloc(4096): kmem_map too small: 335544320 total allocated cpuid = 1 KDB: enter: panic [thread pid 15139 tid 100160 ] Stopped at kdb_enter_why+0x3a: movl $0,kdb_why db> db> bt Tracing pid 15139 tid 100160 td 0xc7a85af0 kdb_enter_why(3231417278,3231417278,3231555983,3911968708,1,...) at kdb_enter_why+58 panic(3231555983,4096,335544320,3231555977,2000,...) at panic+310 kmem_malloc(3242659980,4096,258,3911968860,3230390816,...) at kmem_malloc+640 page_alloc(3242544416,4096,3911968847,258,3242544416,...) at page_alloc+39 slab_zalloc(3228209884,3242551688,8,3231552877,1878,...) at slab_zalloc+192 uma_zone_slab(3242551688,0,3231552877,1878,4,...) at uma_zone_slab+324 uma_zalloc_arg(3242544416,0,258,3349699312,3911969228,...) at uma_zalloc_arg+1395 ffs_vget(3333761124,922776,2,3911969228,3911969240,...) at ffs_vget+168 ufs_lookup(3911969308,3343471972,3911969744,3343471972,3911969340,...) at ufs_lookup+2555 VOP_CACHEDLOOKUP_APV(3232100544,3911969308,3911969744,3911969724,3335025920,...) at VOP_CACHEDLOOKUP_APV+165 vfs_cache_lookup(3911969440,3911969440,3911969704,3343471972,2,...) at vfs_cache_lookup+208 VOP_LOOKUP_APV(3232100544,3911969440,3349699312,3231462256,681,...) at VOP_LOOKUP_APV+165 lookup(3911969704,3231462256,198,191,3343637548,...) at lookup+1422 namei(3911969704,3911969608,96,0,3349699312,...) at namei+843 kern_stat(3349699312,672272928,0,3911969816,93,...) at kern_stat+61 stat(3349699312,3911970044,8,3231440732,3231973120,...) at stat+47 syscall(3911970104) at syscall+691 Xint0x80_syscall() at Xint0x80_syscall+32 --- syscall (188, FreeBSD ELF32, stat), eip = 134726611, esp = 3217021740, ebp = 3217021864 --- db> -------------------------------------------------------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet since 1994 www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike From owner-freebsd-stable@FreeBSD.ORG Tue Dec 2 13:38:32 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6DDBA1065675 for ; Tue, 2 Dec 2008 13:38:32 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.terabit.net.ua (mail.terabit.net.ua [195.137.202.147]) by mx1.freebsd.org (Postfix) with ESMTP id 0185E8FC18 for ; Tue, 2 Dec 2008 13:38:31 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from skuns.zoral.com.ua ([91.193.166.194] helo=mail.zoral.com.ua) by mail.terabit.net.ua with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1L7VSN-000Nq6-HX; Tue, 02 Dec 2008 15:38:27 +0200 Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id mB2DcD4T082963 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Dec 2008 15:38:13 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id mB2DcDUx013125; Tue, 2 Dec 2008 15:38:13 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id mB2DcDu9013123; Tue, 2 Dec 2008 15:38:13 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 2 Dec 2008 15:38:13 +0200 From: Kostik Belousov To: Mike Tancsa Message-ID: <20081202133812.GY3045@deviant.kiev.zoral.com.ua> References: <200812021319.mB2DJGJx003807@lava.sentex.ca> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="8bLSEqNM5P+Jqlqx" Content-Disposition: inline In-Reply-To: <200812021319.mB2DJGJx003807@lava.sentex.ca> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: ClamAV version 0.93.3, clamav-milter version 0.93.3 on skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua X-Virus-Scanned: mail.terabit.net.ua 1L7VSN-000Nq6-HX 23b5f7b131429a68a2467ee09ffa8b48 X-Terabit: YES Cc: freebsd-stable@freebsd.org Subject: Re: repeatable crash on RELENG7 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, 02 Dec 2008 13:38:32 -0000 --8bLSEqNM5P+Jqlqx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Dec 02, 2008 at 08:19:17AM -0500, Mike Tancsa wrote: > While trying to speed up nanobsd builds, I mounted /usr/obj on a=20 > ramdisk and found my box crashing. Thinking it might be hardware, I=20 > tried a separate machine, but with the same results. I have 4G of=20 > ram (i386). Am I just running out of some kernel memory ? If so, is=20 > there anything I can adjust to prevent this, yet still use mfs in this wa= y ? >=20 > mdconfig -a -t malloc -s 1800M You cannot have ~ 2Gb of kernel memory allocated for md, at least not on i386. > newfs /dev/md0 > mount /dev/md0 /usr/obj/ > time make -j4 buildworld > /var/log/build.out >=20 >=20 > in the middle of the buildworld on the serial console (after adding=20 > witness etc) >=20 > g_vfs_done():md0[WRITE(offset=3D1752924160, length=3D6144)]error =3D 28 > g_vfs_done():md0[WRITE(offset=3D1752952832, length=3D4096)]error =3D 28 > g_vfs_done():md0[WRITE(offset=3D1753006080, length=3D14336)]error =3D 28 > g_vfs_done():md0[WRITE(offset=3D1753020416, length=3D2048)]error =3D 28 > g_vfs_done():md0[WRITE(offset=3D1753202688, length=3D81920)]error =3D 28 > g_vfs_done():md0[WRITE(offset=3D1191755776, length=3D131072)]error =3D 28 > g_vfs_done():md0[WRITE(offset=3D1191886848, length=3D131072)]error =3D 28 > g_vfs_done():md0[WRITE(offset=3D1192017920, length=3D131072)]error =3D 28 > panic: kmem_malloc(4096): kmem_map too small: 335544320 total allocated > cpuid =3D 1 > KDB: enter: panic > [thread pid 15139 tid 100160 ] > Stopped at kdb_enter_why+0x3a: movl $0,kdb_why > db> > db> bt > Tracing pid 15139 tid 100160 td 0xc7a85af0 > kdb_enter_why(3231417278,3231417278,3231555983,3911968708,1,...) at=20 > kdb_enter_why+58 > panic(3231555983,4096,335544320,3231555977,2000,...) at panic+310 > kmem_malloc(3242659980,4096,258,3911968860,3230390816,...) at=20 > kmem_malloc+640 > page_alloc(3242544416,4096,3911968847,258,3242544416,...) at page_alloc+39 > slab_zalloc(3228209884,3242551688,8,3231552877,1878,...) at slab_zalloc+1= 92 > uma_zone_slab(3242551688,0,3231552877,1878,4,...) at uma_zone_slab+324 > uma_zalloc_arg(3242544416,0,258,3349699312,3911969228,...) at=20 > uma_zalloc_arg+1395 > ffs_vget(3333761124,922776,2,3911969228,3911969240,...) at ffs_vget+168 > ufs_lookup(3911969308,3343471972,3911969744,3343471972,3911969340,...)=20 > at ufs_lookup+2555 > VOP_CACHEDLOOKUP_APV(3232100544,3911969308,3911969744,3911969724,33350259= 20,...)=20 > at VOP_CACHEDLOOKUP_APV+165 > vfs_cache_lookup(3911969440,3911969440,3911969704,3343471972,2,...)=20 > at vfs_cache_lookup+208 > VOP_LOOKUP_APV(3232100544,3911969440,3349699312,3231462256,681,...)=20 > at VOP_LOOKUP_APV+165 > lookup(3911969704,3231462256,198,191,3343637548,...) at lookup+1422 > namei(3911969704,3911969608,96,0,3349699312,...) at namei+843 > kern_stat(3349699312,672272928,0,3911969816,93,...) at kern_stat+61 > stat(3349699312,3911970044,8,3231440732,3231973120,...) at stat+47 > syscall(3911970104) at syscall+691 > Xint0x80_syscall() at Xint0x80_syscall+32 > --- syscall (188, FreeBSD ELF32, stat), eip =3D 134726611, esp =3D=20 > 3217021740, ebp =3D 3217021864 --- > db> >=20 >=20 > -------------------------------------------------------------------- > Mike Tancsa, tel +1 519 651 3400 > Sentex Communications, mike@sentex.net > Providing Internet since 1994 www.sentex.net > Cambridge, Ontario Canada www.sentex.net/mike >=20 > _______________________________________________ > 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" --8bLSEqNM5P+Jqlqx Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkk1OkQACgkQC3+MBN1Mb4ihJQCgt3cTuPKUIud/cbrcc8vqGczn SaUAoNRMr+MdpeNfeqXIzd198eg7IpaU =dUfW -----END PGP SIGNATURE----- --8bLSEqNM5P+Jqlqx-- From owner-freebsd-stable@FreeBSD.ORG Tue Dec 2 14:12:59 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C80561065672 for ; Tue, 2 Dec 2008 14:12:59 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id 723568FC17 for ; Tue, 2 Dec 2008 14:12:59 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost1.sentex.ca (8.14.3/8.14.3) with ESMTP id mB2ECsH0046056; Tue, 2 Dec 2008 09:12:54 -0500 (EST) (envelope-from mike@sentex.net) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.8/8.13.3) with ESMTP id mB2ECsEp004018 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Dec 2008 09:12:54 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <200812021412.mB2ECsEp004018@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Tue, 02 Dec 2008 09:12:54 -0500 To: Kostik Belousov From: Mike Tancsa In-Reply-To: <20081202133812.GY3045@deviant.kiev.zoral.com.ua> References: <200812021319.mB2DJGJx003807@lava.sentex.ca> <20081202133812.GY3045@deviant.kiev.zoral.com.ua> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18 Cc: freebsd-stable@freebsd.org Subject: Re: repeatable crash on RELENG7 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, 02 Dec 2008 14:12:59 -0000 At 08:38 AM 12/2/2008, Kostik Belousov wrote: > > > > mdconfig -a -t malloc -s 1800M >You cannot have ~ 2Gb of kernel memory allocated for md, at least not on >i386. Thanks, how do I find out what the limit is on a machine ? Is it vm.kvm_size ? ---Mike From owner-freebsd-stable@FreeBSD.ORG Tue Dec 2 14:20:59 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D682D1065687 for ; Tue, 2 Dec 2008 14:20:59 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.terabit.net.ua (mail.terabit.net.ua [195.137.202.147]) by mx1.freebsd.org (Postfix) with ESMTP id 7572C8FC0C for ; Tue, 2 Dec 2008 14:20:59 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from skuns.zoral.com.ua ([91.193.166.194] helo=mail.zoral.com.ua) by mail.terabit.net.ua with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1L7W7W-0003wt-A6; Tue, 02 Dec 2008 16:20:58 +0200 Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id mB2EKjAg086462 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Dec 2008 16:20:45 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id mB2EKjLZ017552; Tue, 2 Dec 2008 16:20:45 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id mB2EKjF1017550; Tue, 2 Dec 2008 16:20:45 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 2 Dec 2008 16:20:45 +0200 From: Kostik Belousov To: Mike Tancsa Message-ID: <20081202142045.GA3045@deviant.kiev.zoral.com.ua> References: <200812021319.mB2DJGJx003807@lava.sentex.ca> <20081202133812.GY3045@deviant.kiev.zoral.com.ua> <200812021412.mB2ECsEp004018@lava.sentex.ca> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="21/Vc5rId7THQcsT" Content-Disposition: inline In-Reply-To: <200812021412.mB2ECsEp004018@lava.sentex.ca> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: ClamAV version 0.93.3, clamav-milter version 0.93.3 on skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua X-Virus-Scanned: mail.terabit.net.ua 1L7W7W-0003wt-A6 b1d73a251c745e741fd1bd877547760d X-Terabit: YES Cc: freebsd-stable@freebsd.org Subject: Re: repeatable crash on RELENG7 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, 02 Dec 2008 14:20:59 -0000 --21/Vc5rId7THQcsT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Dec 02, 2008 at 09:12:54AM -0500, Mike Tancsa wrote: > At 08:38 AM 12/2/2008, Kostik Belousov wrote: > >> > >> mdconfig -a -t malloc -s 1800M > >You cannot have ~ 2Gb of kernel memory allocated for md, at least not on > >i386. >=20 > Thanks, how do I find out what the limit is on a machine ? Is it=20 > vm.kvm_size ? It is much less, and highly depends on your load, since KVA is used for all kind of allocations made by kernel. I think either md(4) or mdconfig(8) have a warning about malloc backing for md. --21/Vc5rId7THQcsT Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkk1RDwACgkQC3+MBN1Mb4i5RwCgl3eE3pgWKUJTlTKhnXoP9Pvg ZgwAn2M+2Uv2U2Ct0v7ZLUlidO9McK0E =AQAj -----END PGP SIGNATURE----- --21/Vc5rId7THQcsT-- From owner-freebsd-stable@FreeBSD.ORG Tue Dec 2 15:02:18 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 83FAF1065670 for ; Tue, 2 Dec 2008 15:02:18 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.26]) by mx1.freebsd.org (Postfix) with ESMTP id 0FB318FC13 for ; Tue, 2 Dec 2008 15:02:17 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: by ey-out-2122.google.com with SMTP id 6so1267079eyi.7 for ; Tue, 02 Dec 2008 07:02:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=yTEVFqPtAsoOdzWbGiVMi6OwwANSLWotKjThpokTXp8=; b=tci4Lw5JfxDFz/TPzGgF5zs95hvi1RW/xX6NWtsBC6Kh55snJcDUinJDk360xd0rmG /dt5oe6Ry1UsCba4QnkrjHI+5kF8vf1K8w/5+4RmUYltohsn3qYC/lok4N5IpmolVUtv ptVpIAX10Ql2mvhr9eRBa98W2HHii8ml7XmgQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=qCTyGvhoqc2Im/ZLA2e7ZTYi6wm7UbMiBnA5NRzcngWcZ7xkoCXf/9TIqCr6hdPw5L pphsh259tuth78oaI7CWA4CrOqBnVpKhliX+TjK2FCnPw1BanSKpCzjEdCSqqIoSbHnB i8Mk0k3ye4Ra70LHX6Q/XHrlh/tGSwEuJyGFc= Received: by 10.210.143.11 with SMTP id q11mr14096303ebd.146.1228230136881; Tue, 02 Dec 2008 07:02:16 -0800 (PST) Received: by 10.210.34.12 with HTTP; Tue, 2 Dec 2008 07:02:16 -0800 (PST) Message-ID: Date: Tue, 2 Dec 2008 18:02:16 +0300 From: pluknet To: Stable MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: ipfw2.c,v 1.76.2.17 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, 02 Dec 2008 15:02:18 -0000 Hi. Since this revision (appeared in 6.3) I think ipfw violates POLA. I mean "ipfw table N list" shows values of table in Internet '.' notation. A friend of mine was surprised to found Internet representation of this "optional 32-bit unsigned value". For example security/bruteblock stores unix timestamps here and AFAICS there is no possibility to come back to the previous output format (other than reverting this revision). -- wbr, pluknet From owner-freebsd-stable@FreeBSD.ORG Tue Dec 2 15:41:38 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4642F1065672 for ; Tue, 2 Dec 2008 15:41:38 +0000 (UTC) (envelope-from eugen@kuzbass.ru) Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su [213.184.65.80]) by mx1.freebsd.org (Postfix) with ESMTP id 8D1C78FC26 for ; Tue, 2 Dec 2008 15:41:37 +0000 (UTC) (envelope-from eugen@kuzbass.ru) Received: from www.svzserv.kemerovo.su (eugen@localhost [127.0.0.1]) by www.svzserv.kemerovo.su (8.13.8/8.13.8) with ESMTP id mB2FfYbu073356; Tue, 2 Dec 2008 22:41:34 +0700 (KRAT) (envelope-from eugen@www.svzserv.kemerovo.su) Received: (from eugen@localhost) by www.svzserv.kemerovo.su (8.13.8/8.13.8/Submit) id mB2FfYmC073355; Tue, 2 Dec 2008 22:41:34 +0700 (KRAT) (envelope-from eugen) Date: Tue, 2 Dec 2008 22:41:34 +0700 From: Eugene Grosbein To: pluknet Message-ID: <20081202154134.GA73002@svzserv.kemerovo.su> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: Stable Subject: Re: ipfw2.c,v 1.76.2.17 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, 02 Dec 2008 15:41:38 -0000 On Tue, Dec 02, 2008 at 06:02:16PM +0300, pluknet wrote: > Since this revision (appeared in 6.3) I think ipfw violates POLA. > I mean "ipfw table N list" shows values of table in Internet '.' notation. > > A friend of mine was surprised to found Internet representation > of this "optional 32-bit unsigned value". > > For example security/bruteblock stores unix timestamps here > and AFAICS there is no possibility to come back to the previous > output format (other than reverting this revision). That was fixed 8 months ago. Just upgrade to 6.4. Eugene Grosbein From owner-freebsd-stable@FreeBSD.ORG Tue Dec 2 15:45:06 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 918481065670; Tue, 2 Dec 2008 15:45:06 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (cl-162.ewr-01.us.sixxs.net [IPv6:2001:4830:1200:a1::2]) by mx1.freebsd.org (Postfix) with ESMTP id 0E6EC8FC22; Tue, 2 Dec 2008 15:45:05 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.14.3/8.14.2) with ESMTP id mB2FjpAA091303; Tue, 2 Dec 2008 09:45:51 -0600 (CST) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.14.3/8.14.3/Submit) id mB2Fjod3091302; Tue, 2 Dec 2008 09:45:50 -0600 (CST) (envelope-from brooks) Date: Tue, 2 Dec 2008 09:45:50 -0600 From: Brooks Davis To: Jonathan Feally Message-ID: <20081202154550.GA91152@lor.one-eyed-alien.net> References: <4933A00E.7080201@netvulture.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="azLHFNyN32YCQGCU" Content-Disposition: inline In-Reply-To: <4933A00E.7080201@netvulture.com> User-Agent: Mutt/1.5.17 (2007-11-01) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (lor.one-eyed-alien.net [127.0.0.1]); Tue, 02 Dec 2008 09:45:51 -0600 (CST) Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Subject: Re: dhclient doing DISCOVER with bad IP checksum - bge 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, 02 Dec 2008 15:45:06 -0000 --azLHFNyN32YCQGCU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Dec 01, 2008 at 12:27:58AM -0800, Jonathan Feally wrote: > Sorry for the cross-post, but this could be either lists problem. >=20 > I have 2 boxes running 7-STABLE as of 20081130, both i386 SMP. One is=20 > running ISC DHCPD 3.0.x from recent ports, and the other dhclient from ma= ke=20 > world. >=20 > The server is refusing to answer the DISCOVER request, as it thinks the I= P=20 > checksum is wrong, which tcpdump also confirms. Other DHCP clients are=20 > working fine on this network, so I do not believe it to be the network,= =20 > server or dhcpd. >=20 > Server is running a 2 Port Intel card - em driver. >=20 > Client is a Dell PE1750 with 2 onboard NIC's - bge driver. >=20 > I have tried turning off both RXCSUM and TXCSUM on both the client and=20 > server machines with no luck. I also tried the second NIC on the server= =20 > with the same result. >=20 > This setup was working just a couple of weeks ago, and the only thing tha= t=20 > has changed is updating the src for a make world. PXE booting this server= =20 > does result in an IP being issued, so it is pointing towards something=20 > new/changed in 7-STABLE. >=20 > I have attached a 3 packet dump of the DISCOVER requests. >=20 > Can anybody shed some light on this for me? Where are you running tcpdump? If on the host with the bge0 device, the checksums are probably useless due to checksum offloading. They should be valid on the server end of things. You might try disabling checksum offloading on the nic and see if that changes the results. It's possible the change to bpf.c to send packets through a socket when reassociateing isn't working correctly in that case. You might try backing out this change and seeing if the problem goes away (this will cause problems on some networks). http://svn.freebsd.org/viewvc/base/stable/7/sbin/dhclient/bpf.c?revision=3D= 178675&view=3Dmarkup -- Brooks --azLHFNyN32YCQGCU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) iD8DBQFJNVguXY6L6fI4GtQRAi4dAJ4sdSSSL5KGyZ6VM24RFE7K8FoMiQCgyZus hBp6O01NOWY36pHpDfQ2Dg4= =IUhd -----END PGP SIGNATURE----- --azLHFNyN32YCQGCU-- From owner-freebsd-stable@FreeBSD.ORG Tue Dec 2 15:45:12 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E18E81065673; Tue, 2 Dec 2008 15:45:12 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.9.129]) by mx1.freebsd.org (Postfix) with ESMTP id 9DA238FC18; Tue, 2 Dec 2008 15:45:12 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 8D9D17309E; Tue, 2 Dec 2008 16:34:08 +0100 (CET) Date: Tue, 2 Dec 2008 16:34:08 +0100 From: Luigi Rizzo To: Danny Braniss Message-ID: <20081202153408.GC54445@onelab2.iet.unipi.it> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org Subject: Re: btx/pxeboot problem 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, 02 Dec 2008 15:45:13 -0000 On Tue, Dec 02, 2008 at 01:48:17PM +0200, Danny Braniss wrote: > latest pxeboot (7.1): > mother-board NIC/LOM CPU > ------------- ------- --- > Intel SWV25 em xeon works fine > SUN X2200 bge amd works fine > DELL PE 2950 bce xeon failes 95% of the times > hangs or goes into btx dump regs. mode :-) > Intel SE7320VP21 msk xeon failes 50% of the times - hangs > > pxeboot with btx.S 1.45 2008/02/27 23:35:39, works fine. > so it seems that changes since 1.45 have fixed it for some, but it > brakes for others :-). I can help testing, but btx is way out of > my league. interesting, so this is the same problem i was seeing on the Asus/amd machines here... the commit log for 1.47 mention interrupt issues which are consistent with the random hangs or errors that I see while booting over the network. http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/boot/i386/btx/btx/btx.S.diff?r1=1.46;r2=1.47 I wonder if the hangs are related to interrupts coming in at the wrong time. I also wonder whether the same symptoms might also affect the standard loader and not just pxeloader, in which case the problem would be slightly more serious. I am afraid my ability to debug the problem isn't going much beyond this... cheers luigi From owner-freebsd-stable@FreeBSD.ORG Tue Dec 2 15:58:28 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 193C4106564A for ; Tue, 2 Dec 2008 15:58:28 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.173]) by mx1.freebsd.org (Postfix) with ESMTP id 950238FC08 for ; Tue, 2 Dec 2008 15:58:27 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: by ug-out-1314.google.com with SMTP id 30so2972286ugs.39 for ; Tue, 02 Dec 2008 07:58:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=XOBA6cgA5SVto7TXx9M8Qg/FiZYKlbmoKvpw/6RljX0=; b=GBglmsXxLI3Z0x/xhqvRsT3/4MWii3iBoi5xpMl4zEmbPgnff3drCa2QlgBentXrs7 /fyzBfix1UlhmatNI6UtT6zJDV1t1EM22dL0tS6wKZ3VCeM0Kn7gEGvUFBGYomMQaK6g J0/8Jow+7rAaXUO56J/BcWNek4VI//asl4th8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=H/G3etTyVZGTVCVtwO/pC2894WRzO9KLFqFIcOk9MyRN7qoFm83ZLqePpyor8AF+Gj kY173oO075gqufhWn8HjvL1fDpTY3ob1vyPrguwdJU2+zPwkRW3R3tXTOxa8l06FIgKG XdVXuDlJTrtZk8WyBUAR78Twsm+KtbxHW5zTA= Received: by 10.210.59.14 with SMTP id h14mr14171321eba.182.1228233506048; Tue, 02 Dec 2008 07:58:26 -0800 (PST) Received: by 10.210.34.12 with HTTP; Tue, 2 Dec 2008 07:58:26 -0800 (PST) Message-ID: Date: Tue, 2 Dec 2008 18:58:26 +0300 From: pluknet To: "Andrey V. Elsukov" , "Eugene Grosbein" In-Reply-To: <427101228232910@webmail19.yandex.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <427101228232910@webmail19.yandex.ru> Cc: Stable Subject: Re: ipfw2.c,v 1.76.2.17 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, 02 Dec 2008 15:58:28 -0000 2008/12/2 Andrey V. Elsukov : > 02.12.08, 18:02, "pluknet" : >> Since this revision (appeared in 6.3) I think ipfw violates POLA. >> I mean "ipfw table N list" shows values of table in Internet '.' notation. >> A friend of mine was surprised to found Internet representation >> of this "optional 32-bit unsigned value". >> For example security/bruteblock stores unix timestamps here >> and AFAICS there is no possibility to come back to the previous >> output format (other than reverting this revision). > > It fixed in 1.76.2.21. > > -- > WBR, Andrey V. Elsukov > Andrey, Eugene. Thank you all! And please forgive me my laziness, not allowed to check up last revisions of ipfw2.c. -- wbr, pluknet From owner-freebsd-stable@FreeBSD.ORG Tue Dec 2 16:01:00 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7B4651065676 for ; Tue, 2 Dec 2008 16:01:00 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from smtp132.rog.mail.re2.yahoo.com (smtp132.rog.mail.re2.yahoo.com [206.190.53.37]) by mx1.freebsd.org (Postfix) with SMTP id 1BAB88FC1D for ; Tue, 2 Dec 2008 16:00:59 +0000 (UTC) (envelope-from mikej@rogers.com) Received: (qmail 34087 invoked from network); 2 Dec 2008 15:34:19 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:Received:Message-ID:In-Reply-To:References:Date:Subject:From:To:Cc:User-Agent:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:Importance; b=aQzxpHQLzwgzVbBBYHXmhLtlT6etsWa8QSqmvVLH+ii0t08V/zoErQeL9kCahLmt9Rfvv3cokrQV405fxsvs4yKiZrg7Sn/RFIhi2RhUnGYExbfLWEwR8sgNVIqIjLe1HiMwXtFBHrSd4ucfPcEQGH9vweHqNTZB7xbhwjyOyrQ= ; Received: from unknown (HELO wettoast.dyndns.org) (mikej@99.227.98.203 with login) by smtp132.rog.mail.re2.yahoo.com with SMTP; 2 Dec 2008 15:34:16 -0000 X-YMail-OSG: HClk1NIVM1lud1ME5qGWY1z3PMfp8aFkXtWqFA1Y5y9nd5YIkriU6W.C2VDAV7SYKg-- X-Yahoo-Newman-Property: ymail-3 Received: from 38.99.187.34 (SquirrelMail authenticated user mikej) by wettoast.dyndns.org with HTTP; Tue, 2 Dec 2008 10:34:31 -0500 (EST) Message-ID: In-Reply-To: <4935069A.8060209@ec-marseille.fr> References: <4935069A.8060209@ec-marseille.fr> Date: Tue, 2 Dec 2008 10:34:31 -0500 (EST) From: "Mike Jakubik" To: "Geoffroy Desvernay" , freebsd-stable@freebsd.org User-Agent: SquirrelMail/1.4.15 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: delphij@delphij.net Subject: Re: RELENG_7_1: bce driver change generating too much interrupts ? 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, 02 Dec 2008 16:01:00 -0000 On Tue, December 2, 2008 4:57 am, Geoffroy Desvernay wrote: > Since last upgrade, I see much more CPU time "eated" by interrupts (at > least 10% cpu in top) > (see http://dgeo.perso.ec-marseille.fr/cpu-week.png) I am also seeing the same behavior on a farm of Dell servers. root@web.local:~# vmstat -i interrupt total rate irq1: atkbd0 18 0 irq14: ata0 176 0 irq16: mfi0 67924 1 irq20: uhci1 uhci3 1 0 irq21: uhci0 uhci+ 5 0 cpu0: timer 132244117 1997 irq257: bce1 3366039632 50853 cpu1: timer 132244053 1997 cpu2: timer 132244053 1997 cpu3: timer 132244053 1997 Total 3895084032 58846 Not only this, but i have also noticed that there are a number of errors reported by netstat now. before the drivers update, i would not get these errors. root@web.local:~# netstat -i Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll 0 bce1 1500 00:1e:c9:b5:cc:b6 1848959 2197 1357031 0 0 From owner-freebsd-stable@FreeBSD.ORG Tue Dec 2 16:01:51 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E8F261065678 for ; Tue, 2 Dec 2008 16:01:51 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forwards4.yandex.ru (forwards4.yandex.ru [77.88.32.20]) by mx1.freebsd.org (Postfix) with ESMTP id 993938FC1A for ; Tue, 2 Dec 2008 16:01:51 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from webmail19.yandex.ru (webmail19.yandex.ru [77.88.32.123]) by forwards4.yandex.ru (Yandex) with ESMTP id E05F24C55C0; Tue, 2 Dec 2008 18:48:33 +0300 (MSK) Received: from YAMAIL (webmail19) by mail.yandex.ru id S1163267AbYLBPsa for (+ 1 other); Tue, 2 Dec 2008 18:48:30 +0300 X-Yandex-Spam: 1 Received: from [77.72.138.58] ([77.72.138.58]) by mail.yandex.ru with HTTP; Tue, 02 Dec 2008 18:48:30 +0300 From: "Andrey V. Elsukov" To: "pluknet" In-Reply-To: References: MIME-Version: 1.0 Message-Id: <427101228232910@webmail19.yandex.ru> Date: Tue, 02 Dec 2008 18:48:30 +0300 X-Mailer: Yamail [ http://yandex.ru ] 5.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain Cc: Stable Subject: Re: ipfw2.c,v 1.76.2.17 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, 02 Dec 2008 16:01:52 -0000 02.12.08, 18:02, "pluknet" : > Since this revision (appeared in 6.3) I think ipfw violates POLA. > I mean "ipfw table N list" shows values of table in Internet '.' notation. > A friend of mine was surprised to found Internet representation > of this "optional 32-bit unsigned value". > For example security/bruteblock stores unix timestamps here > and AFAICS there is no possibility to come back to the previous > output format (other than reverting this revision). It fixed in 1.76.2.21. -- WBR, Andrey V. Elsukov From owner-freebsd-stable@FreeBSD.ORG Tue Dec 2 16:03:43 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 170411065678 for ; Tue, 2 Dec 2008 16:03:43 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id CB04C8FC1B for ; Tue, 2 Dec 2008 16:03:42 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost1.sentex.ca (8.14.3/8.14.3) with ESMTP id mB2G3eGi077809; Tue, 2 Dec 2008 11:03:40 -0500 (EST) (envelope-from mike@sentex.net) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.8/8.13.3) with ESMTP id mB2G3eb9004481 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Dec 2008 11:03:40 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <200812021603.mB2G3eb9004481@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Tue, 02 Dec 2008 11:03:40 -0500 To: Kostik Belousov From: Mike Tancsa In-Reply-To: <20081202142045.GA3045@deviant.kiev.zoral.com.ua> References: <200812021319.mB2DJGJx003807@lava.sentex.ca> <20081202133812.GY3045@deviant.kiev.zoral.com.ua> <200812021412.mB2ECsEp004018@lava.sentex.ca> <20081202142045.GA3045@deviant.kiev.zoral.com.ua> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18 Cc: freebsd-stable@freebsd.org Subject: Re: repeatable crash on RELENG7 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, 02 Dec 2008 16:03:43 -0000 At 09:20 AM 12/2/2008, Kostik Belousov wrote: >On Tue, Dec 02, 2008 at 09:12:54AM -0500, Mike Tancsa wrote: > > At 08:38 AM 12/2/2008, Kostik Belousov wrote: > > >> > > >> mdconfig -a -t malloc -s 1800M > > >You cannot have ~ 2Gb of kernel memory allocated for md, at least not on > > >i386. > > > > Thanks, how do I find out what the limit is on a machine ? Is it > > vm.kvm_size ? > >It is much less, and highly depends on your load, since KVA is used for all >kind of allocations made by kernel. I think either md(4) or mdconfig(8) have >a warning about malloc backing for md. Thanks! A warning might be helpful to prevent such foot shooting :) ---Mike From owner-freebsd-stable@FreeBSD.ORG Tue Dec 2 16:08:24 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6DB6C1065670 for ; Tue, 2 Dec 2008 16:08:24 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.16.84]) by mx1.freebsd.org (Postfix) with ESMTP id 1B0EF8FC14 for ; Tue, 2 Dec 2008 16:08:23 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by kabab.cs.huji.ac.il with esmtp id 1L7XnR-000Hmn-JA; Tue, 02 Dec 2008 18:08:21 +0200 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: Jonathan Feally In-reply-to: <4934C733.4020506@netvulture.com> References: <4933A00E.7080201@netvulture.com> <4934C733.4020506@netvulture.com> Comments: In-reply-to Jonathan Feally message dated "Mon, 01 Dec 2008 21:27:15 -0800." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 02 Dec 2008 18:08:21 +0200 From: Danny Braniss Message-ID: Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Subject: Re: dhclient doing DISCOVER with bad IP checksum - bge (7.1 show stopper??) 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, 02 Dec 2008 16:08:24 -0000 > Can someone please confirm or rule out my issue with dhclient sending > bad IP checksum packets. It would really suck if 7.1 was released with a > broken DHCP client. > I've had many problems lately, but none involved checksum nor the dhcpd (btw, I assume that you are seeing bad checksum on the receiving server) could you add a nic to your PE1750? danny > Jonathan Feally wrote: > > Sorry for the cross-post, but this could be either lists problem. > > > > I have 2 boxes running 7-STABLE as of 20081130, both i386 SMP. One is > > running ISC DHCPD 3.0.x from recent ports, and the other dhclient from > > make world. > > > > The server is refusing to answer the DISCOVER request, as it thinks > > the IP checksum is wrong, which tcpdump also confirms. Other DHCP > > clients are working fine on this network, so I do not believe it to be > > the network, server or dhcpd. > > > > Server is running a 2 Port Intel card - em driver. > > > > Client is a Dell PE1750 with 2 onboard NIC's - bge driver. > > > > I have tried turning off both RXCSUM and TXCSUM on both the client and > > server machines with no luck. I also tried the second NIC on the > > server with the same result. > > > > This setup was working just a couple of weeks ago, and the only thing > > that has changed is updating the src for a make world. PXE booting > > this server does result in an IP being issued, so it is pointing > > towards something new/changed in 7-STABLE. > > > > I have attached a 3 packet dump of the DISCOVER requests. > > > > Can anybody shed some light on this for me? > > > > Thanks, -Jon > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > freebsd-net@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-net > > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > _______________________________________________ > 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" > From owner-freebsd-stable@FreeBSD.ORG Tue Dec 2 16:51:23 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BF5251065670 for ; Tue, 2 Dec 2008 16:51:23 +0000 (UTC) (envelope-from samflanker@gmail.com) Received: from ik-out-1112.google.com (ik-out-1112.google.com [66.249.90.180]) by mx1.freebsd.org (Postfix) with ESMTP id 4C3868FC0A for ; Tue, 2 Dec 2008 16:51:22 +0000 (UTC) (envelope-from samflanker@gmail.com) Received: by ik-out-1112.google.com with SMTP id c21so2835784ika.3 for ; Tue, 02 Dec 2008 08:51:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:content-type :content-transfer-encoding; bh=0dmdE0gmrG9OmfzzLUKgOKN+KuMUTwkcyCtAka0K40w=; b=NvWKz7cMrDk+nQvi6ol4XL4I5Gr31W7nuitATRBNVfIwc8kaH12oz5vyj4GebTO33F /G1FbaVqfdTyihTPPGSWE5QC/DN2aBEzdLClZEgBie4XlAbJ8VHJ3lECQJqckVPDkuAt l58W93n3TiSgV2kO4+hk6X15i/7arMtahurhI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; b=ur6tMTYHavYHPg8I86rZ358zIPBge1HPyNWhTuRX0EYjcRblwFmpSSoKt0ohF/w5ym IfdMmQcCjjCocR04j/c6KFH4dy+gadkEwLTzysXh83wpqTh7ptQah+R03QzPfDpnfybX R8aSFX1rfjlqnxTwzRYQC9urWfQNpECBHJ2h0= Received: by 10.210.51.10 with SMTP id y10mr14220432eby.98.1228235092984; Tue, 02 Dec 2008 08:24:52 -0800 (PST) Received: from localhost.localdomain ([213.152.137.42]) by mx.google.com with ESMTPS id 10sm6084833eyd.43.2008.12.02.08.24.51 (version=SSLv3 cipher=RC4-MD5); Tue, 02 Dec 2008 08:24:52 -0800 (PST) Message-ID: <49356162.8070609@gmail.com> Date: Tue, 02 Dec 2008 19:25:06 +0300 From: Vladimir Ermakov User-Agent: Thunderbird 2.0.0.18 (X11/20081119) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: synproxy state does not work on FreeBSD 7.1-PRERELEASE 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, 02 Dec 2008 16:51:23 -0000 crossmessage http://lists.freebsd.org/pipermail/freebsd-pf/2008-November/004881.html hello I tried to rule with `synproxy state` uname FreeBSD 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Wed Oct 29 12:47:36 UTC 2008 (amd64 & i386 arch) the `synproxy state` is not working (web-browser does not receive the html-page) uname FreeBSD 7.0-RELEASE GENERIC (amd64 & i386 arch) the `synproxy state` is working # cat /etc/pf.conf pass on em0 proto tcp from any to 192.168.0.1 port 80 synproxy state to all, please check and confirm or deny /Vladimir Ermakov From owner-freebsd-stable@FreeBSD.ORG Tue Dec 2 16:55:55 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8BC3F1065673 for ; Tue, 2 Dec 2008 16:55:55 +0000 (UTC) (envelope-from pahom.rt@gmail.com) Received: from rn-out-0910.google.com (rn-out-0910.google.com [64.233.170.189]) by mx1.freebsd.org (Postfix) with ESMTP id 2E3F08FC2E for ; Tue, 2 Dec 2008 16:55:54 +0000 (UTC) (envelope-from pahom.rt@gmail.com) Received: by rn-out-0910.google.com with SMTP id j71so2617285rne.12 for ; Tue, 02 Dec 2008 08:55:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type:references; bh=R1QOjuqkb34Z4gr5Gcbd+uYhMTWMfnYUpuzIoMf4r4E=; b=jBbjReQtNhj4L/MxzRGqdukpGeY4M/AA03ljnF+7o4YKdEjGpEnmtPw5PAm6+UVucU G/7ZWD7NvbdYP/+9Jtb173ysyFMumKfIV6b8guVE4TEME9r62v+7sTgBv2skdhYMj3gX phsJ1x2L8aPv89mbFFa4+9LvdK+Ep9gmLyHvg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=CWPb1hM9nJ+TX9UuN/rMgTnTFWaSyCStTDwGqacS0rkBNJdN787p9xG4yRXvDDuKPw m8ILxqxVvEMnxY7sOuCfOSE6ATKxojaC7NnAuFGWekGwqKAv9fFgWHXsxtvSS3nYtG7a fC2C3Qpp6ggTJG2Lsiv6FZTPXmFSQXWmypy10= Received: by 10.103.179.16 with SMTP id g16mr523383mup.130.1228235580781; Tue, 02 Dec 2008 08:33:00 -0800 (PST) Received: by 10.103.217.2 with HTTP; Tue, 2 Dec 2008 08:33:00 -0800 (PST) Message-ID: Date: Tue, 2 Dec 2008 19:33:00 +0300 From: "Alexandr Pakhomov" To: "Mike Tancsa" In-Reply-To: <200812021412.mB2ECsEp004018@lava.sentex.ca> MIME-Version: 1.0 References: <200812021319.mB2DJGJx003807@lava.sentex.ca> <20081202133812.GY3045@deviant.kiev.zoral.com.ua> <200812021412.mB2ECsEp004018@lava.sentex.ca> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: repeatable crash on RELENG7 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, 02 Dec 2008 16:55:55 -0000 On Tue, Dec 2, 2008 at 5:12 PM, Mike Tancsa wrote: > At 08:38 AM 12/2/2008, Kostik Belousov wrote: > >> > >> > mdconfig -a -t malloc -s 1800M >> You cannot have ~ 2Gb of kernel memory allocated for md, at least not on >> i386. >> > > Thanks, how do I find out what the limit is on a machine ? Is it > vm.kvm_size ? > > > ---Mike > _______________________________________________ > 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" > Try tune both vm.kmem_size and vm.kmem_size_max via /boot/loader.conf. They are equal to 330M by default. From owner-freebsd-stable@FreeBSD.ORG Tue Dec 2 17:08:12 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9554C10656D6 for ; Tue, 2 Dec 2008 17:08:12 +0000 (UTC) (envelope-from samflanker@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.168]) by mx1.freebsd.org (Postfix) with ESMTP id 193308FC1C for ; Tue, 2 Dec 2008 17:08:11 +0000 (UTC) (envelope-from samflanker@gmail.com) Received: by ug-out-1314.google.com with SMTP id 30so2992835ugs.39 for ; Tue, 02 Dec 2008 09:08:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=nD7nZYUmxCY0MH0gtfYE3L4tegIyYOFouIZeItsLVws=; b=jVrVF5wb5vG7e9i8c2bSabVtwlv31pmyH/kbn6Hoboo2q1TbsV4xzdVkRQjtj7M6sA ALDAdtgzh+CdNHGbVxyiMUpXOHpG+6JcO//vhWntVTPFqFylqGeAvNBPANTNoBvPxzOo MmMcN26BRkA6mt183JBhdSy4D0DggoOQsWu+o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=Xc4irI/nxtNwFqLdq5KdwxMn7ZmS9e4ou7SrO6x5njhOoMfWfpDk83W/8VIJxkCayB tlOjVRmBryhGexICqxdsI7h231nJu3Rk0c+RTVYpiAg7eJB4tzsBnjt7GsONqzUy7cRv TOfEv2Zi92e3xt5nd3+W1zAE+E7GpoIUj3xho= Received: by 10.210.109.10 with SMTP id h10mr14253822ebc.110.1228237690361; Tue, 02 Dec 2008 09:08:10 -0800 (PST) Received: from localhost.localdomain ([213.152.137.42]) by mx.google.com with ESMTPS id 10sm6090904eyd.43.2008.12.02.09.08.07 (version=SSLv3 cipher=RC4-MD5); Tue, 02 Dec 2008 09:08:08 -0800 (PST) Message-ID: <49356B87.6020201@gmail.com> Date: Tue, 02 Dec 2008 20:08:23 +0300 From: Vladimir Ermakov User-Agent: Thunderbird 2.0.0.18 (X11/20081119) MIME-Version: 1.0 To: Jesper Wallin References: <49356162.8070609@gmail.com> <20081202165601.GA55067@zero.nohack.se> In-Reply-To: <20081202165601.GA55067@zero.nohack.se> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: synproxy state does not work on FreeBSD 7.1-PRERELEASE 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, 02 Dec 2008 17:08:12 -0000 Jesper Wallin wrote: > think this is because you also do filtering on the loopback interface and therefore block the initial handshake. Try with "set skip on lo0". :-) > > > Regards, > Jesper > > > Thank you, but I did not use blocking rules. /Vladimir Ermakov From owner-freebsd-stable@FreeBSD.ORG Tue Dec 2 17:40:53 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 881BE1065676; Tue, 2 Dec 2008 17:40:53 +0000 (UTC) (envelope-from vulture@netvulture.com) Received: from mail.consult-scs.com (MAIL.CONSULT-SCS.COM [208.81.60.67]) by mx1.freebsd.org (Postfix) with ESMTP id 669E28FC20; Tue, 2 Dec 2008 17:40:53 +0000 (UTC) (envelope-from vulture@netvulture.com) Received: from [127.0.0.1] (host77.netvulture.com [208.201.244.77]) (Authenticated sender: vulture@netvulture.com) by mail.consult-scs.com (Postfix) with ESMTPA id F3B8F1642485; Tue, 2 Dec 2008 09:41:25 -0800 (PST) Message-ID: <49357329.9000107@netvulture.com> Date: Tue, 02 Dec 2008 09:40:57 -0800 From: Jonathan Feally User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 References: <4933A00E.7080201@netvulture.com> <4934C733.4020506@netvulture.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SCS-MailScanner-Information: Please contact the ISP for more information X-MailScanner-ID: F3B8F1642485.6C299 X-SCS-MailScanner: Found to be clean X-SCS-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-203.107, required 4, autolearn=not spam, ALL_TRUSTED -1.80, BAYES_00 -2.60, INIT_RECVD_OUR_AUTH -200.00, MISSING_HEADERS 1.29) X-SCS-MailScanner-From: vulture@netvulture.com Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Subject: Re: dhclient doing DISCOVER with bad IP checksum - bge (7.1 show stopper??) 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, 02 Dec 2008 17:40:53 -0000 I will try another em card in that server to confirm/rule out the nic driver. I am seeing the same checksum number on both the source machine, the dhcp server machine, and a 3rd windows xp machine sniffing the traffic with etherreal/wireshark. The windows xp box is running an intel nic as well, and those 0.0.0.0.67 -> 255.255.255.255.68 packets as seen by the server do have the correct checksum. After the nic test, if no change from one driver to the other, then I'll try to un-patch the bpf.c change. At this point it is acting like the checksum offloading (which I did disable on both the client and server) just isn't working. Will let you know. -Jon Danny Braniss wrote: >> Can someone please confirm or rule out my issue with dhclient sending >> bad IP checksum packets. It would really suck if 7.1 was released with a >> broken DHCP client. >> >> > I've had many problems lately, but none involved checksum nor the dhcpd > (btw, I assume that you are seeing bad checksum on the receiving server) > could you add a nic to your PE1750? > > danny > > > >> Jonathan Feally wrote: >> >>> Sorry for the cross-post, but this could be either lists problem. >>> >>> I have 2 boxes running 7-STABLE as of 20081130, both i386 SMP. One is >>> running ISC DHCPD 3.0.x from recent ports, and the other dhclient from >>> make world. >>> >>> The server is refusing to answer the DISCOVER request, as it thinks >>> the IP checksum is wrong, which tcpdump also confirms. Other DHCP >>> clients are working fine on this network, so I do not believe it to be >>> the network, server or dhcpd. >>> >>> Server is running a 2 Port Intel card - em driver. >>> >>> Client is a Dell PE1750 with 2 onboard NIC's - bge driver. >>> >>> I have tried turning off both RXCSUM and TXCSUM on both the client and >>> server machines with no luck. I also tried the second NIC on the >>> server with the same result. >>> >>> This setup was working just a couple of weeks ago, and the only thing >>> that has changed is updating the src for a make world. PXE booting >>> this server does result in an IP being issued, so it is pointing >>> towards something new/changed in 7-STABLE. >>> >>> I have attached a 3 packet dump of the DISCOVER requests. >>> >>> Can anybody shed some light on this for me? >>> >>> Thanks, -Jon >>> >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> freebsd-net@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-net >>> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >>> >> -- >> This message has been scanned for viruses and >> dangerous content by MailScanner, and is >> believed to be clean. >> >> _______________________________________________ >> 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" >> >> > > > _______________________________________________ > 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" > > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From owner-freebsd-stable@FreeBSD.ORG Tue Dec 2 18:18:08 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 99EA11065670 for ; Tue, 2 Dec 2008 18:18:08 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.delphij.net (delphij-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:2c9::2]) by mx1.freebsd.org (Postfix) with ESMTP id 04A7C8FC14 for ; Tue, 2 Dec 2008 18:18:07 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.geekcn.org (tarsier.geekcn.org [211.166.10.233]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tarsier.delphij.net (Postfix) with ESMTPS id 313C928449 for ; Wed, 3 Dec 2008 02:18:06 +0800 (CST) Received: from localhost (tarsier.geekcn.org [211.166.10.233]) by tarsier.geekcn.org (Postfix) with ESMTP id A49F6EB4A2F; Wed, 3 Dec 2008 02:18:05 +0800 (CST) X-Virus-Scanned: amavisd-new at geekcn.org Received: from tarsier.geekcn.org ([211.166.10.233]) by localhost (mail.geekcn.org [211.166.10.233]) (amavisd-new, port 10024) with ESMTP id KqCqcmVRjcgx; Wed, 3 Dec 2008 02:18:00 +0800 (CST) Received: from charlie.delphij.net (adsl-76-237-33-62.dsl.pltn13.sbcglobal.net [76.237.33.62]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTPSA id CA272EB0C00; Wed, 3 Dec 2008 02:17:55 +0800 (CST) DomainKey-Signature: a=rsa-sha1; s=default; d=delphij.net; c=nofws; q=dns; h=message-id:date:from:reply-to:organization:user-agent: mime-version:to:cc:subject:references:in-reply-to: x-enigmail-version:openpgp:content-type:content-transfer-encoding; b=WZzjyM1R5KOkVWZ+6BnRgs1UNXaf+tHH14PRtHo3qAXWIh3IbS9Ens0vS3gZzvAuI lvxqYNmHJvqc8LEyuz4Jw== Message-ID: <49357BD0.4000008@delphij.net> Date: Tue, 02 Dec 2008 10:17:52 -0800 From: Xin LI Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.18 (X11/20081125) MIME-Version: 1.0 To: Mike Jakubik References: <4935069A.8060209@ec-marseille.fr> In-Reply-To: X-Enigmail-Version: 0.95.7 OpenPGP: id=18EDEBA0; url=http://www.delphij.net/delphij.asc Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Geoffroy Desvernay Subject: Re: RELENG_7_1: bce driver change generating too much interrupts ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: d@delphij.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Dec 2008 18:18:08 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Can anyone try reverting the changeset itself? There are two recent changesets: http://www.delphij.net/bce-185161.diff.bz2 http://www.delphij.net/bce-184826.diff.bz2 You can revert the change by doing this: cd /usr/src fetch http://www.delphij.net/bce-185161.diff.bz2 fetch http://www.delphij.net/bce-184826.diff.bz2 bzcat bce-185161.diff.bz2 | patch -R bzcat bce-184826.diff.bz2 | patch -R I'll check what's happening ASAP. Cheers, - -- Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkk1e88ACgkQi+vbBBjt66AsYACfXPwMnWtUsCeae/pBDOIav1Hd JN8AoL5cm8ZHYY0dKutRljtxRsiVYco0 =v1VF -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Tue Dec 2 18:47:18 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5C4CF1065672 for ; Tue, 2 Dec 2008 18:47:18 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from smtp130.rog.mail.re2.yahoo.com (smtp130.rog.mail.re2.yahoo.com [206.190.53.35]) by mx1.freebsd.org (Postfix) with SMTP id DEE6B8FC1B for ; Tue, 2 Dec 2008 18:47:17 +0000 (UTC) (envelope-from mikej@rogers.com) Received: (qmail 59704 invoked from network); 2 Dec 2008 18:47:17 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:Received:Message-ID:In-Reply-To:References:Date:Subject:From:To:Cc:User-Agent:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:Importance; b=gIVJdxKjOOTsLX4nCzT46Nv3zH9bgUvenUzZOkL7PZ3O9r2LrLocrC/iJxxfoWlgmFfjmSzgdx/KPEb+k5sewOwkW62zq4DC2E1DqYJuvBKlUGiZG4Zo7DMQLPeOcikTmyn/bqVtZpRtpsv9VvUb8x1W+t7Xu6PyuA6pEFhI5m4= ; Received: from unknown (HELO wettoast.dyndns.org) (mikej@99.227.98.203 with login) by smtp130.rog.mail.re2.yahoo.com with SMTP; 2 Dec 2008 18:47:17 -0000 X-YMail-OSG: BKeqpKgVM1l4uJYeUOwS9gpKxleBYnd7m7Q80yfYtcAjkaW_AH6RTWLtEWxPiI.Afw-- X-Yahoo-Newman-Property: ymail-3 Received: from 38.99.187.34 (SquirrelMail authenticated user mikej) by wettoast.dyndns.org with HTTP; Tue, 2 Dec 2008 13:47:31 -0500 (EST) Message-ID: <577b277aabfaf99e2d0e33f3d8572cf7.squirrel@wettoast.dyndns.org> In-Reply-To: <49357BD0.4000008@delphij.net> References: <4935069A.8060209@ec-marseille.fr> <49357BD0.4000008@delphij.net> Date: Tue, 2 Dec 2008 13:47:31 -0500 (EST) From: "Mike Jakubik" To: d@delphij.net User-Agent: SquirrelMail/1.4.15 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: freebsd-stable@freebsd.org Subject: Re: RELENG_7_1: bce driver change generating too much interrupts ? 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, 02 Dec 2008 18:47:18 -0000 On Tue, December 2, 2008 1:17 pm, Xin LI wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Can anyone try reverting the changeset itself? There are two recent > changesets: > > http://www.delphij.net/bce-185161.diff.bz2 > http://www.delphij.net/bce-184826.diff.bz2 Thanks for the info, the exact card that i use is the following, it is shipped with Dell servers. --- bce1@pci0:3:0:0: class=0x020000 card=0x01b31028 chip=0x164c14e4 rev=0x12 hdr=0x00 vendor = 'Broadcom Corporation' device = '5708C Broadcom NetXtreme II Gigabit Ethernet Adapter' class = network subclass = ethernet --- From owner-freebsd-stable@FreeBSD.ORG Tue Dec 2 19:09:04 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CEAC91065677; Tue, 2 Dec 2008 19:09:04 +0000 (UTC) (envelope-from vulture@netvulture.com) Received: from mail.consult-scs.com (MAIL.CONSULT-SCS.COM [208.81.60.67]) by mx1.freebsd.org (Postfix) with ESMTP id B3D9F8FC1A; Tue, 2 Dec 2008 19:09:04 +0000 (UTC) (envelope-from vulture@netvulture.com) Received: from [127.0.0.1] (host77.netvulture.com [208.201.244.77]) (Authenticated sender: vulture@netvulture.com) by mail.consult-scs.com (Postfix) with ESMTPA id 5BE5D164248E; Tue, 2 Dec 2008 11:09:37 -0800 (PST) Message-ID: <493587D4.5000400@netvulture.com> Date: Tue, 02 Dec 2008 11:09:08 -0800 From: Jonathan Feally User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: freebsd-net@freebsd.org, freebsd-stable@freebsd.org References: <4933A00E.7080201@netvulture.com> <4934C733.4020506@netvulture.com> <49357329.9000107@netvulture.com> In-Reply-To: <49357329.9000107@netvulture.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SCS-MailScanner-Information: Please contact the ISP for more information X-MailScanner-ID: 5BE5D164248E.4F48C X-SCS-MailScanner: Found to be clean X-SCS-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-204.399, required 4, autolearn=not spam, ALL_TRUSTED -1.80, BAYES_00 -2.60, INIT_RECVD_OUR_AUTH -200.00) X-SCS-MailScanner-From: vulture@netvulture.com Cc: Subject: Re: dhclient doing DISCOVER with bad IP checksum - bge (7.1 show stopper??) 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, 02 Dec 2008 19:09:04 -0000 Jonathan Feally wrote: > I will try another em card in that server to confirm/rule out the nic > driver. I am seeing the same checksum number on both the source > machine, the dhcp server machine, and a 3rd windows xp machine > sniffing the traffic with etherreal/wireshark. The windows xp box is > running an intel nic as well, and those 0.0.0.0.67 -> > 255.255.255.255.68 packets as seen by the server do have the correct > checksum. After the nic test, if no change from one driver to the > other, then I'll try to un-patch the bpf.c change. > > At this point it is acting like the checksum offloading (which I did > disable on both the client and server) just isn't working. > > Will let you know. > > -Jon > > Danny Braniss wrote: Tried a add-in em0 card - intel pro/1000 XT server card - 82544E chip - no change. also tried with ifconfig em0 -rxcsum ifconfig em0 -txcsum dhclient em0 No change. Packets still received with bad IP checksum. Went back to bge0 now and reversed rev 178675 back to 172506 care of patch via http://svn.freebsd.org/viewvc/base/stable/7/sbin/dhclient/bpf.c?r1=172506&r2=178675&view=patch Also no change. So this change to dhclient doesn't seem to be the issue. >From looking at http://svn.freebsd.org/viewvc/base/stable/7/sbin/dhclient/ this patch I took out is 7 months old, and I had this system running on 7-STABLE just fine about as of about 2-3 weeks ago. So it must have been something else in the sys/net or sys/netinet. I do seem some changes that are 3 weeks old, 4 weeks, and 6 days for these directories on files that would effect the packet assembly. Authors are julian, rwatson, and bz. I'm going to look through these recent changes to try to find some that has to do with the checksum process. -Jon -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From owner-freebsd-stable@FreeBSD.ORG Tue Dec 2 20:02:27 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 268C41065679 for ; Tue, 2 Dec 2008 20:02:27 +0000 (UTC) (envelope-from dgeo@ec-marseille.fr) Received: from melo.ec-marseille.fr (melo.ec-marseille.fr [147.94.19.139]) by mx1.freebsd.org (Postfix) with ESMTP id C2A468FC29 for ; Tue, 2 Dec 2008 20:02:26 +0000 (UTC) (envelope-from dgeo@ec-marseille.fr) Received: from localhost (amavis3.serv.int [10.3.0.47]) by melo.ec-marseille.fr (GrosseBox 1743 XXL) with ESMTP id E7EDAACB6C; Tue, 2 Dec 2008 21:02:25 +0100 (CET) X-Virus-Scanned: amavisd-new at ec-marseille.fr Received: from melo.ec-marseille.fr ([10.3.0.13]) by localhost (amavis3.serv.int [10.3.0.47]) (amavisd-new, port 10024) with LMTP id eYyMlxAjBEJr; Tue, 2 Dec 2008 21:02:25 +0100 (CET) Received: from [10.0.3.6] (schizo.ec-marseille.fr [147.94.19.137]) (Authenticated sender: dgeo) by melo.ec-marseille.fr (GrosseBox 1743 XXL) with ESMTPSA id 5D43FACB69; Tue, 2 Dec 2008 21:02:25 +0100 (CET) Message-ID: <4935944A.9090509@ec-marseille.fr> Date: Tue, 02 Dec 2008 21:02:18 +0100 From: geoffroy desvernay User-Agent: Thunderbird 2.0.0.18 (X11/20081125) MIME-Version: 1.0 To: d@delphij.net References: <4935069A.8060209@ec-marseille.fr> <49357BD0.4000008@delphij.net> In-Reply-To: <49357BD0.4000008@delphij.net> X-Enigmail-Version: 0.95.0 OpenPGP: id=017C80AA Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig1B8843D2BAE32A023C133105" Cc: Mike Jakubik , freebsd-stable@freebsd.org Subject: Re: RELENG_7_1: bce driver change generating too much interrupts ? 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, 02 Dec 2008 20:02:27 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig1B8843D2BAE32A023C133105 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Xin LI a =E9crit : > Can anyone try reverting the changeset itself? There are two recent > changesets: >=20 > http://www.delphij.net/bce-185161.diff.bz2 > http://www.delphij.net/bce-184826.diff.bz2 >=20 > You can revert the change by doing this: >=20 > cd /usr/src > fetch http://www.delphij.net/bce-185161.diff.bz2 > fetch http://www.delphij.net/bce-184826.diff.bz2 > bzcat bce-185161.diff.bz2 | patch -R > bzcat bce-184826.diff.bz2 | patch -R >=20 > I'll check what's happening ASAP. >=20 Done: I'd say it seems to be related... Before applying your patches: # vmstat -i interrupt total rate irq1: atkbd0 18 0 irq14: ata0 58 0 irq20: uhci1 96 0 irq21: uhci0 uhci+ 5 0 irq78: mfi0 539747 3 cpu0: timer 350029937 1999 irq256: bce0 6757905080 38611 irq259: bce1 8296789513 47403 cpu1: timer 350029945 1999 cpu2: timer 350030010 1999 cpu3: timer 350030025 1999 Total 16455354434 94018 After patch, make buildkernel && make reinstallkernel and reboot interrupt total rate irq1: atkbd0 18 0 irq14: ata0 58 0 irq20: uhci1 2 0 irq21: uhci0 uhci+ 5 0 irq78: mfi0 3947 24 cpu0: timer 320361 1989 irq256: bce0 6658 41 irq259: bce1 1428 8 cpu1: timer 320320 1989 cpu2: timer 320380 1989 cpu3: timer 320507 1990 Total 1293684 8035 --=20 geoffroy desvernay --------------enig1B8843D2BAE32A023C133105 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJNZRNGbFYzwF8gKoRAldLAJsHfSbRs9tb+0BHEnp+pPpF26TQsACcCBi/ wLZfYel8FyJUHY+VAnwGRlw= =dUSU -----END PGP SIGNATURE----- --------------enig1B8843D2BAE32A023C133105-- From owner-freebsd-stable@FreeBSD.ORG Tue Dec 2 23:21:35 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 31C0F1065678 for ; Tue, 2 Dec 2008 23:21:35 +0000 (UTC) (envelope-from peters@netreconsys.com) Received: from guttless.creativelogic.ca (guttless.creativelogic.ca [76.10.129.163]) by mx1.freebsd.org (Postfix) with ESMTP id F0E298FC20 for ; Tue, 2 Dec 2008 23:21:34 +0000 (UTC) (envelope-from peters@netreconsys.com) Received: by guttless.creativelogic.ca (Postfix, from userid 1002) id ECACB1146D; Tue, 2 Dec 2008 18:07:01 -0500 (EST) X-Original-To: freebsd-stable@freebsd.org Received: from [10.11.12.206] (76-10-166-51.dsl.teksavvy.com [76.10.166.51]) by guttless.creativelogic.ca (Postfix) with ESMTPA id 8987611469 for ; Tue, 2 Dec 2008 18:07:01 -0500 (EST) Message-Id: <11EA14E6-BF73-4D67-B287-45B76208BE11@netreconsys.com> From: Peter Sprokkelenburg To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Date: Tue, 2 Dec 2008 18:05:19 -0500 X-Mailer: Apple Mail (2.929.2) Subject: Freebsd 7 STABLE 200807 amd64 - Realtek 8168 not working 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, 02 Dec 2008 23:21:35 -0000 I have an Asus P5Q-WS running FreeBSD 7 and the onboard Realtek NIC's are not being detected. No Kernel modifications as this is a fresh install. pciconf -lv : re0@pci0:3:0:0: class=0x020000 card=0x82c61043 chip=0x816810ec rev=0x02 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' class = network subclass = ethernet re1@pci0:2:0:0: class=0x020000 card=0x82c61043 chip=0x816810ec rev=0x02 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' class = network subclass = ethernet /var/log/messages: pci3: on pcib6 Dec 2 17:37:21 nas kernel: re0: port 0xc800-0xc8ff mem 0xfe5ff000-0xfe5fffff,0xfdef 0000-0xfdefffff irq 16 at device 0.0 on pci3 Dec 2 17:37:21 nas kernel: re0: Unknown H/W revision: 3c400000 Dec 2 17:37:21 nas kernel: device_attach: re0 attach returned 6 Dec 2 17:37:21 nas kernel: pcib7: irq 18 at device 28.5 on pci0 Dec 2 17:37:21 nas kernel: pci2: on pcib7 Dec 2 17:37:21 nas kernel: re1: port 0xb800-0xb8ff mem 0xfe4ff000-0xfe4fffff,0xfddf 0000-0xfddfffff irq 17 at device 0.0 on pci2 Dec 2 17:37:21 nas kernel: re1: Unknown H/W revision: 3c400000 Dec 2 17:37:21 nas kernel: device_attach: re1 attach returned 6 Is anymore info need to generate a patch? let me know. ------------------ Peter Sprokkelenburg mailto:peters@netreconsys.com From owner-freebsd-stable@FreeBSD.ORG Tue Dec 2 23:27:29 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D40161065676; Tue, 2 Dec 2008 23:27:29 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.delphij.net (delphij-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:2c9::2]) by mx1.freebsd.org (Postfix) with ESMTP id 185958FC13; Tue, 2 Dec 2008 23:27:29 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.geekcn.org (tarsier.geekcn.org [211.166.10.233]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tarsier.delphij.net (Postfix) with ESMTPS id 300CA28450; Wed, 3 Dec 2008 07:27:28 +0800 (CST) Received: from localhost (tarsier.geekcn.org [211.166.10.233]) by tarsier.geekcn.org (Postfix) with ESMTP id B52D7EB89C0; Wed, 3 Dec 2008 07:27:27 +0800 (CST) X-Virus-Scanned: amavisd-new at geekcn.org Received: from tarsier.geekcn.org ([211.166.10.233]) by localhost (mail.geekcn.org [211.166.10.233]) (amavisd-new, port 10024) with ESMTP id pkCIhbtswQdk; Wed, 3 Dec 2008 07:27:21 +0800 (CST) Received: from charlie.delphij.net (adsl-76-237-33-62.dsl.pltn13.sbcglobal.net [76.237.33.62]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTPSA id ADE93EB4D29; Wed, 3 Dec 2008 07:27:18 +0800 (CST) DomainKey-Signature: a=rsa-sha1; s=default; d=delphij.net; c=nofws; q=dns; h=message-id:date:from:reply-to:organization:user-agent: mime-version:to:cc:subject:references:in-reply-to: x-enigmail-version:openpgp:content-type; b=K3gdpmNp3rNVEy+Ak/Fcsp1lhjtg802EcG7auzYARasg+1HD1NkTMx6wefpjtn3Qn 21kAqQuWMeTeijdvlotdA== Message-ID: <4935C453.8070301@delphij.net> Date: Tue, 02 Dec 2008 15:27:15 -0800 From: Xin LI Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.18 (X11/20081125) MIME-Version: 1.0 To: geoffroy desvernay References: <4935069A.8060209@ec-marseille.fr> <49357BD0.4000008@delphij.net> <4935944A.9090509@ec-marseille.fr> In-Reply-To: <4935944A.9090509@ec-marseille.fr> X-Enigmail-Version: 0.95.7 OpenPGP: id=18EDEBA0; url=http://www.delphij.net/delphij.asc Content-Type: multipart/mixed; boundary="------------010001060603010607030506" Cc: Mike Jakubik , d@delphij.net, freebsd-stable@freebsd.org, demon@FreeBSD.ORG Subject: Re: RELENG_7_1: bce driver change generating too much interrupts ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: d@delphij.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Dec 2008 23:27:29 -0000 This is a multi-part message in MIME format. --------------010001060603010607030506 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Here is a patch that adjusts parameters of the interrupt handler, which reduces interrupts. These parameters are obtained from DragonFly, FYI. Note that this does not restore previous behavior, say, few interrupt if no traffic. I'm still looking into the real cause. geoffroy desvernay wrote: > Xin LI a écrit : >> Can anyone try reverting the changeset itself? There are two recent >> changesets: >> >> http://www.delphij.net/bce-185161.diff.bz2 >> http://www.delphij.net/bce-184826.diff.bz2 >> >> You can revert the change by doing this: >> >> cd /usr/src >> fetch http://www.delphij.net/bce-185161.diff.bz2 >> fetch http://www.delphij.net/bce-184826.diff.bz2 >> bzcat bce-185161.diff.bz2 | patch -R >> bzcat bce-184826.diff.bz2 | patch -R >> >> I'll check what's happening ASAP. >> > Done: > > I'd say it seems to be related... > > Before applying your patches: > # vmstat -i > interrupt total rate > irq1: atkbd0 18 0 > irq14: ata0 58 0 > irq20: uhci1 96 0 > irq21: uhci0 uhci+ 5 0 > irq78: mfi0 539747 3 > cpu0: timer 350029937 1999 > irq256: bce0 6757905080 38611 > irq259: bce1 8296789513 47403 > cpu1: timer 350029945 1999 > cpu2: timer 350030010 1999 > cpu3: timer 350030025 1999 > Total 16455354434 94018 > > > After patch, make buildkernel && make reinstallkernel and reboot > interrupt total rate > irq1: atkbd0 18 0 > irq14: ata0 58 0 > irq20: uhci1 2 0 > irq21: uhci0 uhci+ 5 0 > irq78: mfi0 3947 24 > cpu0: timer 320361 1989 > irq256: bce0 6658 41 > irq259: bce1 1428 8 > cpu1: timer 320320 1989 > cpu2: timer 320380 1989 > cpu3: timer 320507 1990 > Total 1293684 8035 > - -- Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkk1xFMACgkQi+vbBBjt66DgRwCfRTItoRYMYtyWywXfa4arKl8n +usAoLUBSnifVZhK5wmENCpOAngI10WB =tLQJ -----END PGP SIGNATURE----- --------------010001060603010607030506 Content-Type: text/plain; name="bce-intrcoll-parameters.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="bce-intrcoll-parameters.diff" --- if_bce.c 2008-12-02 14:02:30.078918595 -0800 +++ .#if_bce.c.1.34.2.3.2.1 2008-12-02 13:49:07.000000000 -0800 @@ -925,15 +925,15 @@ sc->bce_rx_ticks = 0; #else /* Improve throughput at the expense of increased latency. */ - sc->bce_tx_quick_cons_trip_int = 20; - sc->bce_tx_quick_cons_trip = 20; - sc->bce_tx_ticks_int = 80; - sc->bce_tx_ticks = 80; - - sc->bce_rx_quick_cons_trip_int = 6; - sc->bce_rx_quick_cons_trip = 6; - sc->bce_rx_ticks_int = 18; - sc->bce_rx_ticks = 18; + sc->bce_tx_quick_cons_trip_int = 255; + sc->bce_tx_quick_cons_trip = 255; + sc->bce_tx_ticks_int = 1022; + sc->bce_tx_ticks = 1022; + + sc->bce_rx_quick_cons_trip_int = 128; + sc->bce_rx_quick_cons_trip = 128; + sc->bce_rx_ticks_int = 125; + sc->bce_rx_ticks = 125; #endif /* Update statistics once every second. */ @@ -2555,7 +2555,7 @@ } else if (BCE_CHIP_BOND_ID(sc) & BCE_CHIP_BOND_ID_SERDES_BIT) sc->bce_phy_flags |= BCE_PHY_SERDES_FLAG; - if (sc->bce_phy_flags && BCE_PHY_SERDES_FLAG) { + if (sc->bce_phy_flags & BCE_PHY_SERDES_FLAG) { sc->bce_flags |= BCE_NO_WOL_FLAG; if (BCE_CHIP_NUM(sc) != BCE_CHIP_NUM_5706) { sc->bce_phy_addr = 2; --------------010001060603010607030506-- From owner-freebsd-stable@FreeBSD.ORG Tue Dec 2 23:30:56 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 060C41065777 for ; Tue, 2 Dec 2008 23:30:56 +0000 (UTC) (envelope-from jason.chambers@earthlink.net) Received: from elasmtp-scoter.atl.sa.earthlink.net (elasmtp-scoter.atl.sa.earthlink.net [209.86.89.67]) by mx1.freebsd.org (Postfix) with ESMTP id CD0048FC16 for ; Tue, 2 Dec 2008 23:30:55 +0000 (UTC) (envelope-from jason.chambers@earthlink.net) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=hsU1IF2KpWlhq+/6M5AFRqQKXutYxVWWDwTbKDxcilj8R+bCeiivJiuOptvQwven; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; Received: from [149.142.36.207] (helo=computer.local) by elasmtp-scoter.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1L7eNe-00078u-Kx for freebsd-stable@freebsd.org; Tue, 02 Dec 2008 18:10:10 -0500 Message-ID: <4935C051.4060400@earthlink.net> Date: Tue, 02 Dec 2008 23:10:09 +0000 From: Jason Chambers User-Agent: Thunderbird 2.0.0.18 (Macintosh/20081105) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-ELNK-Trace: 93537cc8dcc13ee2691d87aecaa30ad294f5150ab1c16ac0eafd45f126befae220222d1bfc83f7775dad75a4eb94df8b350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 149.142.36.207 Subject: Re: [FreeBSD] Fix for ServerWorks HT1000 in upcoming 7.1? 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, 02 Dec 2008 23:30:56 -0000 Hello, There is already a PR for this issue. #122572 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=kern/122572 Regards, --Jason ######################################### Fernan Aguero fernan at iib.unsam.edu.ar Fri Oct 17 13:37:16 UTC 2008 Previous message: [FreeBSD] Fix for ServerWorks HT1000 in upcoming 7.1? Next message: [FreeBSD] Fix for ServerWorks HT1000 in upcoming 7.1? Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] > > On Friday 10 October 2008 01:11:17 pm Fernan Aguero wrote: > > > John, > > > > > > thanks for the tip. I have now successfully gone through > > > the process of making a new bootable CD using the ATA_HT1000 > > > patched kernel. [snipped] > So far everything seems to be working OK ... compiled and > installed a couple of ports (vim, screen, apache, > portupgrade), and everything looks fine. > > I can run more thourough tests if you want. Just let me know > what those are and guide me through them ... are we still on > time for including this patch in the upcoming 7.1? Will > there be a new beta or RC? > > Fernan I have already built world + kernel and installed some more ports. Again, everything works fine. Should I submit a PR asking for inclusion of this patch? This platform (ServerWorks HT1000, and the Dell PowerEdge SC1435) would not boot 7.0 nor 7.1-BETA. If the patch does not affect other chipsets, it would be good to include it in 7.1-RELEASE. Fernan From owner-freebsd-stable@FreeBSD.ORG Wed Dec 3 00:30:35 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DDEF01065672 for ; Wed, 3 Dec 2008 00:30:34 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.228]) by mx1.freebsd.org (Postfix) with ESMTP id A78018FC18 for ; Wed, 3 Dec 2008 00:30:34 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so3136049rvf.43 for ; Tue, 02 Dec 2008 16:30:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=vy3HcGTmduZ2d8PMIBF6T4enq5R1m5uqGiDhTfmLnl0=; b=UMjVrp90DXs9yy/ybTAWDqIWFioBDCYnaglIuZcHRm60Dk6R/tYPUx/AFWsw9Zk0ZZ i6k/28OgxjM1RRFgv5Q0tMD0TksZ4MqC90D5kLtfom/So/SLxTFvgjR5UiHAU4ZUWugZ TmynPT73XIY+xCjGPoTtV7QtWYfqRX6TEm5n4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=sX0TwdSBllZCA7Ad0oNlmdu1sCljwMCUXjegGi7RvXGSf8koJbkX0Wnfx06KXDeJ67 bY9IvbSjbUdeRaKsnKudztVrHiX3EWFNJfSv4ZWrUhm9rdTYjtvTVdlY1689ntg7PcQB bvXxuuxjzN/zfCSUGqqkeWqnu8srJJw0ha1jo= Received: by 10.141.48.6 with SMTP id a6mr6029570rvk.36.1228264233809; Tue, 02 Dec 2008 16:30:33 -0800 (PST) Received: from michelle.cdnetworks.co.kr ([211.53.35.84]) by mx.google.com with ESMTPS id k37sm15460498rvb.1.2008.12.02.16.30.31 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 02 Dec 2008 16:30:32 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id mB30URa9009816 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 3 Dec 2008 09:30:27 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id mB30UQFu009815; Wed, 3 Dec 2008 09:30:26 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Wed, 3 Dec 2008 09:30:26 +0900 From: Pyun YongHyeon To: Peter Sprokkelenburg Message-ID: <20081203003026.GA9639@cdnetworks.co.kr> References: <11EA14E6-BF73-4D67-B287-45B76208BE11@netreconsys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <11EA14E6-BF73-4D67-B287-45B76208BE11@netreconsys.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: Freebsd 7 STABLE 200807 amd64 - Realtek 8168 not working X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Dec 2008 00:30:35 -0000 On Tue, Dec 02, 2008 at 06:05:19PM -0500, Peter Sprokkelenburg wrote: > I have an Asus P5Q-WS running FreeBSD 7 and the onboard Realtek NIC's > are not being detected. > > No Kernel modifications as this is a fresh install. > > pciconf -lv : > > re0@pci0:3:0:0: class=0x020000 card=0x82c61043 chip=0x816810ec > rev=0x02 hdr=0x00 > vendor = 'Realtek Semiconductor' > device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' > class = network > subclass = ethernet > re1@pci0:2:0:0: class=0x020000 card=0x82c61043 chip=0x816810ec > rev=0x02 hdr=0x00 > vendor = 'Realtek Semiconductor' > device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' > class = network > subclass = ethernet > > /var/log/messages: > > pci3: on pcib6 > Dec 2 17:37:21 nas kernel: re0: Ethernet> port 0xc800-0xc8ff mem 0xfe5ff000-0xfe5fffff,0xfdef > 0000-0xfdefffff irq 16 at device 0.0 on pci3 > Dec 2 17:37:21 nas kernel: re0: Unknown H/W revision: 3c400000 > Dec 2 17:37:21 nas kernel: device_attach: re0 attach returned 6 > Dec 2 17:37:21 nas kernel: pcib7: irq 18 at > device 28.5 on pci0 > Dec 2 17:37:21 nas kernel: pci2: on pcib7 > Dec 2 17:37:21 nas kernel: re1: Ethernet> port 0xb800-0xb8ff mem 0xfe4ff000-0xfe4fffff,0xfddf > 0000-0xfddfffff irq 17 at device 0.0 on pci2 > Dec 2 17:37:21 nas kernel: re1: Unknown H/W revision: 3c400000 > Dec 2 17:37:21 nas kernel: device_attach: re1 attach returned 6 > > Is anymore info need to generate a patch? > Please use latest stable/7 or 7.1-BETA2. re(4) will recognize your 8168C controller. -- Regards, Pyun YongHyeon From owner-freebsd-stable@FreeBSD.ORG Wed Dec 3 00:30:41 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8DB3F1065670 for ; Wed, 3 Dec 2008 00:30:41 +0000 (UTC) (envelope-from peter@simons-rock.edu) Received: from hedwig.simons-rock.edu (hedwig.simons-rock.edu [208.81.88.14]) by mx1.freebsd.org (Postfix) with ESMTP id 4C21D8FC17 for ; Wed, 3 Dec 2008 00:30:41 +0000 (UTC) (envelope-from peter@simons-rock.edu) Received: from cesium.hyperfine.info (c2.8d.5646.static.theplanet.com [70.86.141.194]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by hedwig.simons-rock.edu (Postfix) with ESMTP id 12059ED027; Tue, 2 Dec 2008 19:30:40 -0500 (EST) Date: Tue, 2 Dec 2008 19:27:05 -0500 From: "Peter C. Lai" To: Peter Sprokkelenburg Message-ID: <20081203002705.GO27780@cesium.hyperfine.info> References: <11EA14E6-BF73-4D67-B287-45B76208BE11@netreconsys.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <11EA14E6-BF73-4D67-B287-45B76208BE11@netreconsys.com> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-stable@freebsd.org Subject: Re: Freebsd 7 STABLE 200807 amd64 - Realtek 8168 not working 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: Wed, 03 Dec 2008 00:30:41 -0000 You need to move up to at least 20080716... On 2008-12-02 06:05:19PM -0500, Peter Sprokkelenburg wrote: > I have an Asus P5Q-WS running FreeBSD 7 and the onboard Realtek NIC's are > not being detected. > > No Kernel modifications as this is a fresh install. > > pciconf -lv : > > re0@pci0:3:0:0: class=0x020000 card=0x82c61043 chip=0x816810ec rev=0x02 > hdr=0x00 > vendor = 'Realtek Semiconductor' > device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' > class = network > subclass = ethernet > re1@pci0:2:0:0: class=0x020000 card=0x82c61043 chip=0x816810ec rev=0x02 > hdr=0x00 > vendor = 'Realtek Semiconductor' > device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' > class = network > subclass = ethernet > > /var/log/messages: > > pci3: on pcib6 > Dec 2 17:37:21 nas kernel: re0: > port 0xc800-0xc8ff mem 0xfe5ff000-0xfe5fffff,0xfdef > 0000-0xfdefffff irq 16 at device 0.0 on pci3 > Dec 2 17:37:21 nas kernel: re0: Unknown H/W revision: 3c400000 > Dec 2 17:37:21 nas kernel: device_attach: re0 attach returned 6 > Dec 2 17:37:21 nas kernel: pcib7: irq 18 at device > 28.5 on pci0 > Dec 2 17:37:21 nas kernel: pci2: on pcib7 > Dec 2 17:37:21 nas kernel: re1: > port 0xb800-0xb8ff mem 0xfe4ff000-0xfe4fffff,0xfddf > 0000-0xfddfffff irq 17 at device 0.0 on pci2 > Dec 2 17:37:21 nas kernel: re1: Unknown H/W revision: 3c400000 > Dec 2 17:37:21 nas kernel: device_attach: re1 attach returned 6 > > Is anymore info need to generate a patch? > > let me know. > > > ------------------ > Peter Sprokkelenburg > mailto:peters@netreconsys.com > > > > _______________________________________________ > 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" -- =========================================================== Peter C. Lai | Bard College at Simon's Rock Systems Administrator | 84 Alford Rd. Information Technology Svcs. | Gt. Barrington, MA 01230 USA peter AT simons-rock.edu | (413) 528-7428 =========================================================== From owner-freebsd-stable@FreeBSD.ORG Wed Dec 3 00:44:58 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 73E941065670; Wed, 3 Dec 2008 00:44:58 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.delphij.net (delphij-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:2c9::2]) by mx1.freebsd.org (Postfix) with ESMTP id 14ED48FC0C; Wed, 3 Dec 2008 00:44:58 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.geekcn.org (tarsier.geekcn.org [211.166.10.233]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tarsier.delphij.net (Postfix) with ESMTPS id 7855228448; Wed, 3 Dec 2008 08:44:56 +0800 (CST) Received: from localhost (tarsier.geekcn.org [211.166.10.233]) by tarsier.geekcn.org (Postfix) with ESMTP id F24CBEB8A3A; Wed, 3 Dec 2008 08:44:55 +0800 (CST) X-Virus-Scanned: amavisd-new at geekcn.org Received: from tarsier.geekcn.org ([211.166.10.233]) by localhost (mail.geekcn.org [211.166.10.233]) (amavisd-new, port 10024) with ESMTP id XdxUTVKXq5o6; Wed, 3 Dec 2008 08:44:51 +0800 (CST) Received: from charlie.delphij.net (adsl-76-237-33-62.dsl.pltn13.sbcglobal.net [76.237.33.62]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTPSA id 25F51EB89E4; Wed, 3 Dec 2008 08:44:48 +0800 (CST) DomainKey-Signature: a=rsa-sha1; s=default; d=delphij.net; c=nofws; q=dns; h=message-id:date:from:reply-to:organization:user-agent: mime-version:to:cc:subject:references:in-reply-to: x-enigmail-version:openpgp:content-type; b=WnK28Non0vw4bUeVNjrrw0Rk44VerQbu7WEE4b9xzn/LRlwQa8vga/B7Do6lDWBC5 j6zSnUmB+bKltw6ZuoeVg== Message-ID: <4935D67E.4070204@delphij.net> Date: Tue, 02 Dec 2008 16:44:46 -0800 From: Xin LI Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.18 (X11/20081125) MIME-Version: 1.0 To: d@delphij.net References: <4935069A.8060209@ec-marseille.fr> <49357BD0.4000008@delphij.net> <4935944A.9090509@ec-marseille.fr> <4935C453.8070301@delphij.net> In-Reply-To: <4935C453.8070301@delphij.net> X-Enigmail-Version: 0.95.7 OpenPGP: id=18EDEBA0; url=http://www.delphij.net/delphij.asc Content-Type: multipart/mixed; boundary="------------030401080201050805010300" Cc: Mike Jakubik , freebsd-stable@freebsd.org, geoffroy desvernay , demon@FreeBSD.ORG Subject: Re: RELENG_7_1: bce driver change generating too much interrupts ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: d@delphij.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Dec 2008 00:44:58 -0000 This is a multi-part message in MIME format. --------------030401080201050805010300 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi guys, I think I got a real fix. Cheers, - -- Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkk11n0ACgkQi+vbBBjt66Dy6wCfSl3eLRhj5TVs24Q+8ao5Mcz0 FNQAoK8KvziiXFoanhSlWv636o+HfYIj =AixC -----END PGP SIGNATURE----- --------------030401080201050805010300 Content-Type: text/plain; name="patch-bce.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="patch-bce.diff" Index: if_bce.c =================================================================== --- if_bce.c (revision 185565) +++ if_bce.c (working copy) @@ -7030,13 +7030,14 @@ /* Was it a link change interrupt? */ if ((status_attn_bits & STATUS_ATTN_BITS_LINK_STATE) != - (sc->status_block->status_attn_bits_ack & STATUS_ATTN_BITS_LINK_STATE)) + (sc->status_block->status_attn_bits_ack & STATUS_ATTN_BITS_LINK_STATE)) { bce_phy_intr(sc); - /* Clear any transient status updates during link state change. */ - REG_WR(sc, BCE_HC_COMMAND, - sc->hc_command | BCE_HC_COMMAND_COAL_NOW_WO_INT); - REG_RD(sc, BCE_HC_COMMAND); + /* Clear any transient status updates during link state change. */ + REG_WR(sc, BCE_HC_COMMAND, + sc->hc_command | BCE_HC_COMMAND_COAL_NOW_WO_INT); + REG_RD(sc, BCE_HC_COMMAND); + } /* If any other attention is asserted then the chip is toast. */ if (((status_attn_bits & ~STATUS_ATTN_BITS_LINK_STATE) != --------------030401080201050805010300-- From owner-freebsd-stable@FreeBSD.ORG Wed Dec 3 02:52:49 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 57ADC1065672 for ; Wed, 3 Dec 2008 02:52:49 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from dhcp-172-29-11-40.kir.corp.google.com (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 2D1BC8FC08; Wed, 3 Dec 2008 02:52:49 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <4935F481.6060407@FreeBSD.org> Date: Tue, 02 Dec 2008 18:52:49 -0800 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.18 (Macintosh/20081105) MIME-Version: 1.0 To: Mike Tancsa References: <200812021319.mB2DJGJx003807@lava.sentex.ca> <20081202133812.GY3045@deviant.kiev.zoral.com.ua> <200812021412.mB2ECsEp004018@lava.sentex.ca> <20081202142045.GA3045@deviant.kiev.zoral.com.ua> <200812021603.mB2G3eb9004481@lava.sentex.ca> In-Reply-To: <200812021603.mB2G3eb9004481@lava.sentex.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Kostik Belousov , freebsd-stable@freebsd.org Subject: Re: repeatable crash on RELENG7 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: Wed, 03 Dec 2008 02:52:49 -0000 Mike Tancsa wrote: > At 09:20 AM 12/2/2008, Kostik Belousov wrote: >> On Tue, Dec 02, 2008 at 09:12:54AM -0500, Mike Tancsa wrote: >> > At 08:38 AM 12/2/2008, Kostik Belousov wrote: >> > >> >> > >> mdconfig -a -t malloc -s 1800M >> > >You cannot have ~ 2Gb of kernel memory allocated for md, at least >> not on >> > >i386. >> > >> > Thanks, how do I find out what the limit is on a machine ? Is it >> > vm.kvm_size ? >> >> It is much less, and highly depends on your load, since KVA is used >> for all >> kind of allocations made by kernel. I think either md(4) or >> mdconfig(8) have >> a warning about malloc backing for md. > > Thanks! A warning might be helpful to prevent such foot shooting :) malloc Storage for this type of memory disk is allocated with malloc(9). This limits the size to the malloc bucket limit in the kernel. If the -o reserve option is not set, creating and filling a large malloc-backed memory disk is a very easy way to panic a system. You almost never want to use malloc backing for a md, in favour of swap backing. Kris From owner-freebsd-stable@FreeBSD.ORG Wed Dec 3 03:17:40 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0975B106564A; Wed, 3 Dec 2008 03:17:40 +0000 (UTC) (envelope-from vulture@netvulture.com) Received: from mail.consult-scs.com (MAIL.CONSULT-SCS.COM [208.81.60.67]) by mx1.freebsd.org (Postfix) with ESMTP id E382A8FC0A; Wed, 3 Dec 2008 03:17:39 +0000 (UTC) (envelope-from vulture@netvulture.com) Received: from [127.0.0.1] (host77.netvulture.com [208.201.244.77]) (Authenticated sender: vulture@netvulture.com) by mail.consult-scs.com (Postfix) with ESMTPA id 7D9971642486; Tue, 2 Dec 2008 19:18:15 -0800 (PST) Message-ID: <4935FA57.6080106@netvulture.com> Date: Tue, 02 Dec 2008 19:17:43 -0800 From: Jonathan Feally User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: freebsd-net@freebsd.org, freebsd-stable@freebsd.org References: <4933A00E.7080201@netvulture.com> <4934C733.4020506@netvulture.com> <49357329.9000107@netvulture.com> <493587D4.5000400@netvulture.com> In-Reply-To: <493587D4.5000400@netvulture.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SCS-MailScanner-Information: Please contact the ISP for more information X-MailScanner-ID: 7D9971642486.8272C X-SCS-MailScanner: Found to be clean X-SCS-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-204.399, required 4, autolearn=not spam, ALL_TRUSTED -1.80, BAYES_00 -2.60, INIT_RECVD_OUR_AUTH -200.00) X-SCS-MailScanner-From: vulture@netvulture.com Cc: Subject: Re: dhclient doing DISCOVER with bad IP checksum - bge (7.1 show stopper?? NOPE - We're OK) 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: Wed, 03 Dec 2008 03:17:40 -0000 OK, so I installed a different PE1750 with BETA2 and then updated the source via cvsup RELENG_7 from cvsup3 and all is ok now on that box. Went back the first box and cvsup'ed the src again into an empty directory and it compiled and worked fine. Looks like my updating of the source along the way missed http://svn.freebsd.org/viewvc/base?view=revision&revision=182924 as that is the only diff between the 2 local source trees. Sorry for the confusion. I've never had this issue before with cvsup, but guess there's always a first time. Thanks to all for checking my own bad testing work. -Jon -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From owner-freebsd-stable@FreeBSD.ORG Wed Dec 3 04:05:55 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C49F61065670 for ; Wed, 3 Dec 2008 04:05:55 +0000 (UTC) (envelope-from janm@transactionware.com) Received: from mail.transactionware.com (mail.transactionware.com [203.14.245.7]) by mx1.freebsd.org (Postfix) with SMTP id 255B28FC08 for ; Wed, 3 Dec 2008 04:05:54 +0000 (UTC) (envelope-from janm@transactionware.com) Received: (qmail 37677 invoked from network); 3 Dec 2008 04:06:14 -0000 Received: from midgard.transactionware.com (192.168.1.55) by dm.transactionware.com with SMTP; 3 Dec 2008 04:06:14 -0000 Received: (qmail 3282 invoked by uid 907); 3 Dec 2008 04:05:50 -0000 Received: from [192.168.1.32] (HELO [192.168.1.32]) (192.168.1.32) by midgard.transactionware.com (qpsmtpd/0.40) with ESMTP; Wed, 03 Dec 2008 15:05:50 +1100 Message-ID: <4936059E.4050905@transactionware.com> Date: Wed, 03 Dec 2008 15:05:50 +1100 From: Jan Mikkelsen User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <2515BCEE3A2F4CBA8FFB9F1C052924AA@jmlaptop> <4934CB77.30906@transactionware.com> <34C71E28-F128-4F83-80EF-75768172A59D@hiwaay.net> In-Reply-To: <34C71E28-F128-4F83-80EF-75768172A59D@hiwaay.net> Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: 7.1-PRERELEASE: arcmsr write performance problem 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: Wed, 03 Dec 2008 04:05:55 -0000 David Kelly wrote: > > On Dec 1, 2008, at 11:45 PM, Jan Mikkelsen wrote: > >> Replying to my own post ... >> >> I have done a test on the same machine comparing 6.3-p1 to 7.1-PRE. >> The performance is the expected ~6MB/s (because of the lack of cache) >> on 6.3-p1, so the BIOS change doesn't seem to be at fault. >> >> This seems to be a regression somewhere between 6.3 to 7.1. The Areca >> driver is the same in 6.3 and 7.1, so the problem seems to be elsewhere. >> >> I think this is more than just a "performance" problem. The >> observations with gstat showing extremely high ms/w values (I have >> seen them as high as 22000) makes it look like IO completion >> interrupts are being lost. >> >> Any suggestions on where to look next? Are there obvious candidates? > > > ATA maximum block transfer has dropped from 128k to 64k in 7.x. Am not > sure where the handle is to tweak it back up but has slowed peak thruput > on my Dell PE400SC. Can watch with "systat -v" Interesting, thanks. > Worse, I have a stripped array of 2 drives that won't transfer more than > 43k at a chunk because apparently the stripe metadata didn't align > nicely on 64k multiples. I know the partitions start at 64kB multiples in my case. I did, however, reduce the RAID-6 stripe size to 4kB (from 64kB) and that improved things slightly, but the throughput on 7.1 is still slower by about a factor of a about 6 (measured by untaring ~3GB across ~167k files into a fresh filesystem). And on 7.1 the machine is unusable during much of the time. > -- > David Kelly N4HHE, dkelly@HiWAAY.net > ======================================================================== > Whom computers would destroy, they must first drive mad. From owner-freebsd-stable@FreeBSD.ORG Wed Dec 3 06:56:54 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 34D831065670 for ; Wed, 3 Dec 2008 06:56:54 +0000 (UTC) (envelope-from n-butcher=freebsd-stable=freebsd.org=mmporwnv@fusiongol.com) Received: from smtp12.dentaku.gol.com (smtp12.dentaku.gol.com [203.216.5.74]) by mx1.freebsd.org (Postfix) with ESMTP id 098358FC13 for ; Wed, 3 Dec 2008 06:56:53 +0000 (UTC) (envelope-from n-butcher=freebsd-stable=freebsd.org=mmporwnv@fusiongol.com) Received: from nat-166.gol.co.jp ([203.216.1.166] helo=[127.0.0.1]) by smtp12.dentaku.gol.com with esmtpa (Dentaku) id 1L7lQz-0004BG-9U for ; Wed, 03 Dec 2008 15:42:05 +0900 Message-ID: <49362A3C.7060204@fusiongol.com> Date: Wed, 03 Dec 2008 15:42:04 +0900 From: Nathan Butcher User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: freebsd-stable@freebsd.org X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV GOL (outbound) X-Abuse-Complaints: abuse@gol.com Subject: sysinstall automatic partition labelling/sizing problem 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: Wed, 03 Dec 2008 06:56:54 -0000 Automatic labelling on 7.0 created about 360MB for my root partition on a 8GB disk. After a buildkernel into 7.1-PRERELEASE, the root partition was exhausted during the installkernel. Maybe automatic labelling in sysinstall needs to allocate more than 360MB in the root (/) partition if it's going to stay big enough to accomodate a buildkernel and installkernel from source. From owner-freebsd-stable@FreeBSD.ORG Wed Dec 3 07:09:08 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 785DC1065672; Wed, 3 Dec 2008 07:09:08 +0000 (UTC) (envelope-from vulture@netvulture.com) Received: from mail.consult-scs.com (MAIL.CONSULT-SCS.COM [208.81.60.67]) by mx1.freebsd.org (Postfix) with ESMTP id 5EEC18FC0A; Wed, 3 Dec 2008 07:09:08 +0000 (UTC) (envelope-from vulture@netvulture.com) Received: from [127.0.0.1] (host77.netvulture.com [208.201.244.77]) (Authenticated sender: vulture@netvulture.com) by mail.consult-scs.com (Postfix) with ESMTPA id 4F2DE1642485; Tue, 2 Dec 2008 23:09:46 -0800 (PST) Message-ID: <49363099.5040701@netvulture.com> Date: Tue, 02 Dec 2008 23:09:13 -0800 From: Jonathan Feally User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: freebsd-net@freebsd.org, freebsd-stable@freebsd.org References: <4933A00E.7080201@netvulture.com> <4934C733.4020506@netvulture.com> <49357329.9000107@netvulture.com> <493587D4.5000400@netvulture.com> <4935FA57.6080106@netvulture.com> In-Reply-To: <4935FA57.6080106@netvulture.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SCS-MailScanner-Information: Please contact the ISP for more information X-MailScanner-ID: 4F2DE1642485.30571 X-SCS-MailScanner: Found to be clean X-SCS-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-204.399, required 4, autolearn=not spam, ALL_TRUSTED -1.80, BAYES_00 -2.60, INIT_RECVD_OUR_AUTH -200.00) X-SCS-MailScanner-From: vulture@netvulture.com Cc: Subject: Re: dhclient doing DISCOVER with bad IP checksum - compile optimization issue 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: Wed, 03 Dec 2008 07:09:08 -0000 Ok, I managed to cause it again. dhclient was the problem. My source tree was fine. Turns out that it is my make.conf CFLAGS=-O3 setting. When compiled with -O3 it will generate packets with bad checksums. Simply recompiling it with -O2 did not cause this issue and dhclient works fine. So the question becomes, what is happening with -O3 that is breaking it? So far I am not having any other issues with -O3 on the rest of the system. -Jon -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From owner-freebsd-stable@FreeBSD.ORG Wed Dec 3 09:02:30 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E5CA01065688 for ; Wed, 3 Dec 2008 09:02:30 +0000 (UTC) (envelope-from mitya@m4-new.master-telecom.ru) Received: from m4-new.master-telecom.ru (m4-new.master-telecom.ru [85.193.64.114]) by mx1.freebsd.org (Postfix) with ESMTP id 5F2398FC16 for ; Wed, 3 Dec 2008 09:02:29 +0000 (UTC) (envelope-from mitya@m4-new.master-telecom.ru) Received: from m4-new.master-telecom.ru (localhost [127.0.0.1]) by m4-new.master-telecom.ru (8.13.8/8.13.8) with ESMTP id mB38RY2l048270; Wed, 3 Dec 2008 11:27:34 +0300 (MSK) (envelope-from mitya@m4-new.master-telecom.ru) Received: (from mitya@localhost) by m4-new.master-telecom.ru (8.13.8/8.13.8/Submit) id mB38RXfF048269; Wed, 3 Dec 2008 11:27:33 +0300 (MSK) (envelope-from mitya) Date: Wed, 3 Dec 2008 11:27:33 +0300 From: Dmitry Sivachenko To: d@delphij.net Message-ID: <20081203082733.GA48143@m4-new.master-telecom.ru> References: <4935069A.8060209@ec-marseille.fr> <49357BD0.4000008@delphij.net> <4935944A.9090509@ec-marseille.fr> <4935C453.8070301@delphij.net> <4935D67E.4070204@delphij.net> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <4935D67E.4070204@delphij.net> WWW-Home-Page: http://mitya.pp.ru/ X-PGP-Key: http://mitya.pp.ru/mitya.asc User-Agent: Mutt/1.5.18 (2008-05-17) Cc: Mike Jakubik , freebsd-stable@freebsd.org, geoffroy desvernay Subject: Re: RELENG_7_1: bce driver change generating too much interrupts ? 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: Wed, 03 Dec 2008 09:02:31 -0000 On Tue, Dec 02, 2008 at 04:44:46PM -0800, Xin LI wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi guys, > > I think I got a real fix. > I tried that patch with very recent 7-STABLE. I does fix the problem for me. Thanks a lot! > Cheers, > - -- > Xin LI http://www.delphij.net/ > FreeBSD - The Power to Serve! > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.9 (FreeBSD) > > iEYEARECAAYFAkk11n0ACgkQi+vbBBjt66Dy6wCfSl3eLRhj5TVs24Q+8ao5Mcz0 > FNQAoK8KvziiXFoanhSlWv636o+HfYIj > =AixC > -----END PGP SIGNATURE----- > Index: if_bce.c > =================================================================== > --- if_bce.c (revision 185565) > +++ if_bce.c (working copy) > @@ -7030,13 +7030,14 @@ > > /* Was it a link change interrupt? */ > if ((status_attn_bits & STATUS_ATTN_BITS_LINK_STATE) != > - (sc->status_block->status_attn_bits_ack & STATUS_ATTN_BITS_LINK_STATE)) > + (sc->status_block->status_attn_bits_ack & STATUS_ATTN_BITS_LINK_STATE)) { > bce_phy_intr(sc); > > - /* Clear any transient status updates during link state change. */ > - REG_WR(sc, BCE_HC_COMMAND, > - sc->hc_command | BCE_HC_COMMAND_COAL_NOW_WO_INT); > - REG_RD(sc, BCE_HC_COMMAND); > + /* Clear any transient status updates during link state change. */ > + REG_WR(sc, BCE_HC_COMMAND, > + sc->hc_command | BCE_HC_COMMAND_COAL_NOW_WO_INT); > + REG_RD(sc, BCE_HC_COMMAND); > + } > > /* If any other attention is asserted then the chip is toast. */ > if (((status_attn_bits & ~STATUS_ATTN_BITS_LINK_STATE) != From owner-freebsd-stable@FreeBSD.ORG Wed Dec 3 09:28:22 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 929651065672 for ; Wed, 3 Dec 2008 09:28:22 +0000 (UTC) (envelope-from richardtector@thekeelecentre.com) Received: from mx0.thekeelecentre.com (mx0.thekeelecentre.com [IPv6:2001:470:1f09:16f:2::3]) by mx1.freebsd.org (Postfix) with ESMTP id 15CEE8FC12 for ; Wed, 3 Dec 2008 09:28:21 +0000 (UTC) (envelope-from richardtector@thekeelecentre.com) Received: from localhost (filter.mx0.thekeelecentre.com [217.206.238.165]) by mx0.thekeelecentre.com (Postfix) with ESMTP id DF642451AD; Wed, 3 Dec 2008 09:28:20 +0000 (GMT) X-Virus-Scanned: amavisd-new at thekeelecentre.com Received: from mx0.thekeelecentre.com ([217.206.238.167]) by localhost (filter.mx0.thekeelecentre.com [217.206.238.165]) (amavisd-new, port 10024) with ESMTP id cw-VUPiiYxf4; Wed, 3 Dec 2008 09:28:18 +0000 (UTC) Received: from [10.0.2.11] (82-71-32-9.dsl.in-addr.zen.co.uk [82.71.32.9]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx0.thekeelecentre.com (Postfix) with ESMTPSA id 96501451B4; Wed, 3 Dec 2008 09:28:17 +0000 (GMT) Message-ID: <4936512F.5060406@thekeelecentre.com> Date: Wed, 03 Dec 2008 09:28:15 +0000 From: Richard Tector User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <2515BCEE3A2F4CBA8FFB9F1C052924AA@jmlaptop> <4934CB77.30906@transactionware.com> <34C71E28-F128-4F83-80EF-75768172A59D@hiwaay.net> In-Reply-To: <34C71E28-F128-4F83-80EF-75768172A59D@hiwaay.net> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms060406050005000009020100" Cc: Jan Mikkelsen Subject: Re: 7.1-PRERELEASE: arcmsr write performance problem 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: Wed, 03 Dec 2008 09:28:22 -0000 This is a cryptographically signed message in MIME format. --------------ms060406050005000009020100 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit David Kelly wrote: > > On Dec 1, 2008, at 11:45 PM, Jan Mikkelsen wrote: > >> Replying to my own post ... >> >> I have done a test on the same machine comparing 6.3-p1 to 7.1-PRE. >> The performance is the expected ~6MB/s (because of the lack of cache) >> on 6.3-p1, so the BIOS change doesn't seem to be at fault. >> >> This seems to be a regression somewhere between 6.3 to 7.1. The Areca >> driver is the same in 6.3 and 7.1, so the problem seems to be elsewhere. >> >> I think this is more than just a "performance" problem. The >> observations with gstat showing extremely high ms/w values (I have >> seen them as high as 22000) makes it look like IO completion >> interrupts are being lost. >> >> Any suggestions on where to look next? Are there obvious candidates? > > > ATA maximum block transfer has dropped from 128k to 64k in 7.x. Am not > sure where the handle is to tweak it back up but has slowed peak thruput > on my Dell PE400SC. Can watch with "systat -v" > > Worse, I have a stripped array of 2 drives that won't transfer more than > 43k at a chunk because apparently the stripe metadata didn't align > nicely on 64k multiples. Would changes to ATA have affected arcmsr? As far as I know it is not linked to the ATA subsystem at all, though it would explain some odd instances of one of my machines becoming unresponsive a couple of times a day. Richard --------------ms060406050005000009020100 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIHPDCC A5owggMDoAMCAQICAQcwDQYJKoZIhvcNAQEEBQAwgYExCzAJBgNVBAYTAlVLMRYwFAYDVQQI Ew1TdGFmZm9yZHNoaXJlMQ4wDAYDVQQHEwVLZWVsZTEZMBcGA1UEChMQVGhlIEtlZWxlIENl bnRyZTEvMC0GA1UEAxMmVGhlIEtlZWxlIENlbnRyZSBDZXJ0aWZpY2F0ZSBBdXRob3JpdHkw HhcNMDYwOTI5MTQyNTM4WhcNMTAwOTI5MTQyNTM4WjCBijELMAkGA1UEBhMCVUsxFjAUBgNV BAgTDVN0YWZmb3Jkc2hpcmUxGTAXBgNVBAoTEFRoZSBLZWVsZSBDZW50cmUxFzAVBgNVBAMT DlJpY2hhcmQgVGVjdG9yMS8wLQYJKoZIhvcNAQkBFiByaWNoYXJkdGVjdG9yQHRoZWtlZWxl Y2VudHJlLmNvbTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxAE7t9Z0xg5iVOnqE2q7 UhaRoPrygXPXnZ4bHM8P2E4VKfpCP9tmU5rqP/zDwOKwUAFZsv1yHvzMj2d4S8nTP3eC75YY pztd1tiGIUyi2O1vtQuVrcogCC0Xe8TovubsjeosoEN6kujkTLhgWKj+/jDtb0ELiSwh7NnN CoStDvcCAwEAAaOCARUwggERMAkGA1UdEwQCMAAwLAYJYIZIAYb4QgENBB8WHU9wZW5TU0wg R2VuZXJhdGVkIENlcnRpZmljYXRlMB0GA1UdDgQWBBR5NRc2TrF8Qfj9ZMKvq5m5Lh9IFTCB tgYDVR0jBIGuMIGrgBSNCaM0QC1N5Hiyb/MPAVd/ouQEEqGBh6SBhDCBgTELMAkGA1UEBhMC VUsxFjAUBgNVBAgTDVN0YWZmb3Jkc2hpcmUxDjAMBgNVBAcTBUtlZWxlMRkwFwYDVQQKExBU aGUgS2VlbGUgQ2VudHJlMS8wLQYDVQQDEyZUaGUgS2VlbGUgQ2VudHJlIENlcnRpZmljYXRl IEF1dGhvcml0eYIJAJZYbH4e6XXnMA0GCSqGSIb3DQEBBAUAA4GBABy7Pq1hPDwR2vUs9Jlh LHXE1xLe/COWwTjmZ95mnvsX6XL6eVEzuc0xE66Mf1pyFxDKXxTCBj+G/ialE9AYiXTJAAVJ uvhvkm/u1vXdlNlfQJDRnZKFxrZsIT03LIysq+Hb4qZDpQvgWUUyGib4Ze7pNXPp8HOtlTgB ICafws5LMIIDmjCCAwOgAwIBAgIBBzANBgkqhkiG9w0BAQQFADCBgTELMAkGA1UEBhMCVUsx FjAUBgNVBAgTDVN0YWZmb3Jkc2hpcmUxDjAMBgNVBAcTBUtlZWxlMRkwFwYDVQQKExBUaGUg S2VlbGUgQ2VudHJlMS8wLQYDVQQDEyZUaGUgS2VlbGUgQ2VudHJlIENlcnRpZmljYXRlIEF1 dGhvcml0eTAeFw0wNjA5MjkxNDI1MzhaFw0xMDA5MjkxNDI1MzhaMIGKMQswCQYDVQQGEwJV SzEWMBQGA1UECBMNU3RhZmZvcmRzaGlyZTEZMBcGA1UEChMQVGhlIEtlZWxlIENlbnRyZTEX MBUGA1UEAxMOUmljaGFyZCBUZWN0b3IxLzAtBgkqhkiG9w0BCQEWIHJpY2hhcmR0ZWN0b3JA dGhla2VlbGVjZW50cmUuY29tMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDEATu31nTG DmJU6eoTartSFpGg+vKBc9ednhsczw/YThUp+kI/22ZTmuo//MPA4rBQAVmy/XIe/MyPZ3hL ydM/d4LvlhinO13W2IYhTKLY7W+1C5WtyiAILRd7xOi+5uyN6iygQ3qS6ORMuGBYqP7+MO1v QQuJLCHs2c0KhK0O9wIDAQABo4IBFTCCAREwCQYDVR0TBAIwADAsBglghkgBhvhCAQ0EHxYd T3BlblNTTCBHZW5lcmF0ZWQgQ2VydGlmaWNhdGUwHQYDVR0OBBYEFHk1FzZOsXxB+P1kwq+r mbkuH0gVMIG2BgNVHSMEga4wgauAFI0JozRALU3keLJv8w8BV3+i5AQSoYGHpIGEMIGBMQsw CQYDVQQGEwJVSzEWMBQGA1UECBMNU3RhZmZvcmRzaGlyZTEOMAwGA1UEBxMFS2VlbGUxGTAX BgNVBAoTEFRoZSBLZWVsZSBDZW50cmUxLzAtBgNVBAMTJlRoZSBLZWVsZSBDZW50cmUgQ2Vy dGlmaWNhdGUgQXV0aG9yaXR5ggkAllhsfh7pdecwDQYJKoZIhvcNAQEEBQADgYEAHLs+rWE8 PBHa9Sz0mWEsdcTXEt78I5bBOOZn3mae+xfpcvp5UTO5zTETrox/WnIXEMpfFMIGP4b+JqUT 0BiJdMkABUm6+G+Sb+7W9d2U2V9AkNGdkoXGtmwhPTcsjKyr4dvipkOlC+BZRTIaJvhl7uk1 c+nwc62VOAEgJp/CzksxggMbMIIDFwIBATCBhzCBgTELMAkGA1UEBhMCVUsxFjAUBgNVBAgT DVN0YWZmb3Jkc2hpcmUxDjAMBgNVBAcTBUtlZWxlMRkwFwYDVQQKExBUaGUgS2VlbGUgQ2Vu dHJlMS8wLQYDVQQDEyZUaGUgS2VlbGUgQ2VudHJlIENlcnRpZmljYXRlIEF1dGhvcml0eQIB BzAJBgUrDgMCGgUAoIIB6TAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJ BTEPFw0wODEyMDMwOTI4MTVaMCMGCSqGSIb3DQEJBDEWBBTSZr3USJicoMaf0Mf4MXHDt7ii zDBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG 9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBmAYJKwYBBAGCNxAEMYGKMIGHMIGB MQswCQYDVQQGEwJVSzEWMBQGA1UECBMNU3RhZmZvcmRzaGlyZTEOMAwGA1UEBxMFS2VlbGUx GTAXBgNVBAoTEFRoZSBLZWVsZSBDZW50cmUxLzAtBgNVBAMTJlRoZSBLZWVsZSBDZW50cmUg Q2VydGlmaWNhdGUgQXV0aG9yaXR5AgEHMIGaBgsqhkiG9w0BCRACCzGBiqCBhzCBgTELMAkG A1UEBhMCVUsxFjAUBgNVBAgTDVN0YWZmb3Jkc2hpcmUxDjAMBgNVBAcTBUtlZWxlMRkwFwYD VQQKExBUaGUgS2VlbGUgQ2VudHJlMS8wLQYDVQQDEyZUaGUgS2VlbGUgQ2VudHJlIENlcnRp ZmljYXRlIEF1dGhvcml0eQIBBzANBgkqhkiG9w0BAQEFAASBgGXDa+Lq/Ar4/MTxD1JJQMtd rBoR8oGsry50WFZAN7+SeVtwdtShgGGWvV3bK7aiudamHFkjzHVXz+P3IY2tFnNSL3WVqrc6 HdbZCKgbQEXEUqOmLbibfX3paBdbJCN+WQSSF2Oe10kUT6WPLaLwRmXsjfj2hMOLdO9r/Gbp cda+AAAAAAAA --------------ms060406050005000009020100-- From owner-freebsd-stable@FreeBSD.ORG Wed Dec 3 10:08:42 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B46D51065673 for ; Wed, 3 Dec 2008 10:08:42 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.29]) by mx1.freebsd.org (Postfix) with ESMTP id 7C31B8FC12 for ; Wed, 3 Dec 2008 10:08:42 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: by yx-out-2324.google.com with SMTP id 8so1423216yxb.13 for ; Wed, 03 Dec 2008 02:08:41 -0800 (PST) Received: by 10.151.106.4 with SMTP id i4mr12997113ybm.97.1228297664156; Wed, 03 Dec 2008 01:47:44 -0800 (PST) Received: by 10.151.137.13 with HTTP; Wed, 3 Dec 2008 01:47:44 -0800 (PST) Message-ID: Date: Wed, 3 Dec 2008 11:47:44 +0200 From: "Vlad GALU" To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Weird truss output 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: Wed, 03 Dec 2008 10:08:42 -0000 Hello, I'm running a statically linked binary, which I've built inside a jail. The jail's libc & co are in sync with the host's. Truss then shows this: -- cut here -- -- UNKNOWN SYSCALL 1048532 -- -- UNKNOWN SYSCALL 1048532 -- -- UNKNOWN SYSCALL 1048524 -- -- UNKNOWN SYSCALL 1048516 -- -- UNKNOWN SYSCALL 1048572 -- -- UNKNOWN SYSCALL 1048532 -- -- UNKNOWN SYSCALL 1048556 -- -- UNKNOWN SYSCALL 1048532 -- -- UNKNOWN SYSCALL 1048524 -- -- UNKNOWN SYSCALL 1048564 -- -- UNKNOWN SYSCALL 1048548 -- -- UNKNOWN SYSCALL 1048532 -- -- UNKNOWN SYSCALL 1048532 -- -- UNKNOWN SYSCALL 1048532 -- -- UNKNOWN SYSCALL 1048564 -- -- and here -- Is this a bug or a feature? -- ~/.signature: no such file or directory From owner-freebsd-stable@FreeBSD.ORG Wed Dec 3 14:48:08 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8925F1065670 for ; Wed, 3 Dec 2008 14:48:08 +0000 (UTC) (envelope-from spry@anarchy.in.the.ph) Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.186]) by mx1.freebsd.org (Postfix) with ESMTP id 282B78FC12 for ; Wed, 3 Dec 2008 14:48:07 +0000 (UTC) (envelope-from spry@anarchy.in.the.ph) Received: by fk-out-0910.google.com with SMTP id k31so3164182fkk.11 for ; Wed, 03 Dec 2008 06:48:06 -0800 (PST) Received: by 10.181.135.12 with SMTP id m12mr4671621bkn.88.1228313963237; Wed, 03 Dec 2008 06:19:23 -0800 (PST) Received: by 10.181.193.8 with HTTP; Wed, 3 Dec 2008 06:19:23 -0800 (PST) Message-ID: Date: Wed, 3 Dec 2008 22:19:23 +0800 From: "Mars G Miro" To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: GIF parallel tunnels 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: Wed, 03 Dec 2008 14:48:08 -0000 Hi, I have a GIF tunnel w/c has a v4 RFC1918 and v6 on it (both over public IPv4). In 7.0, even if I haven't set to 1 net.link.gif.parallel_tunnels, it would seem okay. But recent 7.1 just csup'd a few hours ago, if this sysctl is not set, recreating the GIF will crash the box (it will only crash upon re-creating). This is now the behavior? I'll try to do more tests tomorrow. Thanks. -- cheers mars From owner-freebsd-stable@FreeBSD.ORG Wed Dec 3 15:45:34 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 568D51065670 for ; Wed, 3 Dec 2008 15:45:34 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.28]) by mx1.freebsd.org (Postfix) with ESMTP id 164A38FC17 for ; Wed, 3 Dec 2008 15:45:33 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: by yx-out-2324.google.com with SMTP id 8so1487435yxb.13 for ; Wed, 03 Dec 2008 07:45:33 -0800 (PST) Received: by 10.151.150.20 with SMTP id c20mr26254995ybo.139.1228319133334; Wed, 03 Dec 2008 07:45:33 -0800 (PST) Received: by 10.151.137.13 with HTTP; Wed, 3 Dec 2008 07:45:33 -0800 (PST) Message-ID: Date: Wed, 3 Dec 2008 17:45:33 +0200 From: "Vlad GALU" To: "Dan Nelson" In-Reply-To: <20081203152330.GD22076@dan.emsphone.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20081203152330.GD22076@dan.emsphone.com> Cc: freebsd-stable@freebsd.org Subject: Re: Weird truss output 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: Wed, 03 Dec 2008 15:45:34 -0000 On Wed, Dec 3, 2008 at 5:23 PM, Dan Nelson wrote: > In the last episode (Dec 03), Vlad GALU said: >> I'm running a statically linked binary, which I've built inside a >> jail. The jail's libc & co are in sync with the host's. Truss then >> shows this: >> >> -- cut here -- >> -- UNKNOWN SYSCALL 1048532 -- >> -- UNKNOWN SYSCALL 1048532 -- > > Is this a threaded app that you attached truss to after it was started? > The method that truss uses to catch syscall enter/exit events doesn't > indicate whether the event is an enter or an exit, so if you attach > while a syscall is active, truss handles the exit event as if it were a > syscall entry event, and never gets back in synch. It gets worse with > threaded apps because each thread is another chance to get out of > synch. Try this patch: > > Index: i386-fbsd.c > =================================================================== > RCS file: /home/ncvs/src/usr.bin/truss/i386-fbsd.c,v > retrieving revision 1.29 > diff -u -p -r1.29 i386-fbsd.c > --- i386-fbsd.c 28 Jul 2007 23:15:04 -0000 1.29 > +++ i386-fbsd.c 3 Dec 2008 15:20:09 -0000 > @@ -149,7 +149,14 @@ i386_syscall_entry(struct trussinfo *tru > fsc.name = > (syscall_num < 0 || syscall_num > nsyscalls) ? NULL : syscallnames[syscall_num]; > if (!fsc.name) { > - fprintf(trussinfo->outfile, "-- UNKNOWN SYSCALL %d --\n", syscall_num); > + fprintf(trussinfo->outfile, "-- UNKNOWN SYSCALL %u (0x%08x) --\n", syscall_num, syscall_num); > + if ((unsigned int)syscall_num > 0x1000) { > + /* When attaching to a running process, we have a 50-50 chance > + of attaching to a process waiting in a syscall, which means > + our first trap is an exit instead of an entry and we're out > + of synch. Reset our flag */ > + trussinfo->curthread->in_syscall = 0; > + } > } > > if (fsc.name && (trussinfo->flags & FOLLOWFORKS) > > > -- > Dan Nelson > dnelson@allantgroup.com > Hi Dan, You were right, this application was indeed threaded. The messages still occur, although at a slightly lower rate. One other thing that's not particularly helpful is this: -- cut here-- read(1074283119,"\M-Ry\^A\0",7356800) = 4 (0x4) -- and here -- I obviously don't have that many descriptors in my process. I can live with the malformed message, but it's a PITA not to know which fd the read was actually made from :( -- ~/.signature: no such file or directory From owner-freebsd-stable@FreeBSD.ORG Wed Dec 3 15:48:13 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E9A9B106564A for ; Wed, 3 Dec 2008 15:48:13 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from smtp132.rog.mail.re2.yahoo.com (smtp132.rog.mail.re2.yahoo.com [206.190.53.37]) by mx1.freebsd.org (Postfix) with SMTP id 744CA8FC0A for ; Wed, 3 Dec 2008 15:48:13 +0000 (UTC) (envelope-from mikej@rogers.com) Received: (qmail 76968 invoked from network); 3 Dec 2008 15:48:12 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:Received:Message-ID:In-Reply-To:References:Date:Subject:From:To:Cc:User-Agent:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:Importance; b=LQUyiTQDR976pYqUiJhHu9QVMmC9e8J8tvFGm6V6pmxstEw3Ad9tdxVWX3zcz6B0ypkoBn48FDHhie6c1hbk9GMiCBt8ZgnR9+gJXDx3NC2uG2PAC6chqIbJGSBC5tDfSA2IeGOCk1JKWamBc/zFoHHJVUYPppgF8vY2nxDmpqU= ; Received: from unknown (HELO wettoast.dyndns.org) (mikej@99.227.98.203 with login) by smtp132.rog.mail.re2.yahoo.com with SMTP; 3 Dec 2008 15:48:12 -0000 X-YMail-OSG: Wg5ZGTYVM1mi7jcm3uuWmfnNEeL_uDOrMy32b2G1Q84nM2as_pWmTCwz7awJAQ0LWQ-- X-Yahoo-Newman-Property: ymail-3 Received: from 38.99.187.34 (SquirrelMail authenticated user mikej) by wettoast.dyndns.org with HTTP; Wed, 3 Dec 2008 10:48:35 -0500 (EST) Message-ID: <8746e280e0118383ab37e9454199d06b.squirrel@wettoast.dyndns.org> In-Reply-To: <20081203082733.GA48143@m4-new.master-telecom.ru> References: <4935069A.8060209@ec-marseille.fr> <49357BD0.4000008@delphij.net> <4935944A.9090509@ec-marseille.fr> <4935C453.8070301@delphij.net> <4935D67E.4070204@delphij.net> <20081203082733.GA48143@m4-new.master-telecom.ru> Date: Wed, 3 Dec 2008 10:48:35 -0500 (EST) From: "Mike Jakubik" To: "Dmitry Sivachenko" User-Agent: SquirrelMail/1.4.15 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: freebsd-stable@freebsd.org, d@delphij.net, geoffroy desvernay Subject: Re: RELENG_7_1: bce driver change generating too much interrupts ? 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: Wed, 03 Dec 2008 15:48:14 -0000 On Wed, December 3, 2008 3:27 am, Dmitry Sivachenko wrote: > On Tue, Dec 02, 2008 at 04:44:46PM -0800, Xin LI wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Hi guys, >> >> I think I got a real fix. >> > > > I tried that patch with very recent 7-STABLE. > I does fix the problem for me. Good to hear. I will have to wait a few days before i update the code as these systems are in production. Thanks guys. From owner-freebsd-stable@FreeBSD.ORG Wed Dec 3 16:00:42 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 115FE1065673 for ; Wed, 3 Dec 2008 16:00:42 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.freebsd.org (Postfix) with ESMTP id C79C98FC0C for ; Wed, 3 Dec 2008 16:00:41 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (smmsp@localhost [127.0.0.1]) by dan.emsphone.com (8.14.3/8.14.3) with ESMTP id mB3FNXHo021672 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 3 Dec 2008 09:23:33 -0600 (CST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.14.3/8.14.3/Submit) id mB3FNWfE021667; Wed, 3 Dec 2008 09:23:32 -0600 (CST) (envelope-from dan) Date: Wed, 3 Dec 2008 09:23:32 -0600 From: Dan Nelson To: Vlad GALU Message-ID: <20081203152330.GD22076@dan.emsphone.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-OS: FreeBSD 7.1-PRERELEASE User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-stable@freebsd.org Subject: Re: Weird truss output 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: Wed, 03 Dec 2008 16:00:42 -0000 In the last episode (Dec 03), Vlad GALU said: > I'm running a statically linked binary, which I've built inside a > jail. The jail's libc & co are in sync with the host's. Truss then > shows this: > > -- cut here -- > -- UNKNOWN SYSCALL 1048532 -- > -- UNKNOWN SYSCALL 1048532 -- Is this a threaded app that you attached truss to after it was started? The method that truss uses to catch syscall enter/exit events doesn't indicate whether the event is an enter or an exit, so if you attach while a syscall is active, truss handles the exit event as if it were a syscall entry event, and never gets back in synch. It gets worse with threaded apps because each thread is another chance to get out of synch. Try this patch: Index: i386-fbsd.c =================================================================== RCS file: /home/ncvs/src/usr.bin/truss/i386-fbsd.c,v retrieving revision 1.29 diff -u -p -r1.29 i386-fbsd.c --- i386-fbsd.c 28 Jul 2007 23:15:04 -0000 1.29 +++ i386-fbsd.c 3 Dec 2008 15:20:09 -0000 @@ -149,7 +149,14 @@ i386_syscall_entry(struct trussinfo *tru fsc.name = (syscall_num < 0 || syscall_num > nsyscalls) ? NULL : syscallnames[syscall_num]; if (!fsc.name) { - fprintf(trussinfo->outfile, "-- UNKNOWN SYSCALL %d --\n", syscall_num); + fprintf(trussinfo->outfile, "-- UNKNOWN SYSCALL %u (0x%08x) --\n", syscall_num, syscall_num); + if ((unsigned int)syscall_num > 0x1000) { + /* When attaching to a running process, we have a 50-50 chance + of attaching to a process waiting in a syscall, which means + our first trap is an exit instead of an entry and we're out + of synch. Reset our flag */ + trussinfo->curthread->in_syscall = 0; + } } if (fsc.name && (trussinfo->flags & FOLLOWFORKS) -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-stable@FreeBSD.ORG Wed Dec 3 16:23:28 2008 Return-Path: Delivered-To: stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 997EE1065672; Wed, 3 Dec 2008 16:23:28 +0000 (UTC) (envelope-from webmaster@kibab.com) Received: from mr0.ht-systems.ru (mr0.ht-systems.ru [78.110.50.55]) by mx1.freebsd.org (Postfix) with ESMTP id 465B98FC0A; Wed, 3 Dec 2008 16:23:28 +0000 (UTC) (envelope-from webmaster@kibab.com) Received: from [83.237.168.189] (helo=kibab-nb.kibab.com) by smtp.ht-systems.ru with esmtpa (Exim 4.62) (envelope-from ) id 1L7uVY-0000XS-65; Wed, 03 Dec 2008 19:23:24 +0300 Date: Wed, 3 Dec 2008 19:23:35 +0300 From: Ilya Bakulin To: pyunyh@gmail.com Message-Id: <20081203192335.1da94c73.webmaster@kibab.com> In-Reply-To: <20081030051017.GB78796@cdnetworks.co.kr> References: <755632516.20081018001504@rulez.sk> <20081018020248.GB31303@cdnetworks.co.kr> <20081020012504.95adc0ca.nork@FreeBSD.org> <20081020071155.GH38923@cdnetworks.co.kr> <20081020132827.edbb2c53.webmaster@kibab.com> <20081021043152.GE43039@cdnetworks.co.kr> <20081030001123.cb1ebd9c.webmaster@kibab.com> <20081030051017.GB78796@cdnetworks.co.kr> Organization: HT-Systems X-Mailer: Sylpheed 2.5.0 (GTK+ 2.12.11; i386-portbld-freebsd7.1) Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="PGP-SHA1"; boundary="Signature=_Wed__3_Dec_2008_19_23_35_+0300_fiwHd7NnN0xy/EQ2" Cc: Daniel Gerzo , Norikatsu Shigemura , stable@FreeBSD.org, yongari@FreeBSD.org Subject: Re: re0 problem 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: Wed, 03 Dec 2008 16:23:28 -0000 --Signature=_Wed__3_Dec_2008_19_23_35_+0300_fiwHd7NnN0xy/EQ2 Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, 30 Oct 2008 14:10:17 +0900 Pyun YongHyeon wrote: >=20 > Please make sure you've (cold/warm) rebooted several times with > this patch. Just applying the patch and using it without reboots > doesn't necessary mean a working fix. Since it's hard to reproduce > the issue even on a system with problematic controllers I'd like to > have confidence in the patch. >=20 > --=20 > Regards, > Pyun YongHyeon I've been using patched driver for a month, without any problems. Cold/warm= reboots, panics, shutdowns occured regularly, but - no problems. Yesterday= I've updated kernel to latest 7-STABLE & forgot to apply patch, and errors= are here :-) Applying patch once more fixed problems. I think that perfect working of patched driver during past month definitely= proves that your patch corrects incorrect behavior of re(4). Thank you ver= y much! =20 --=20 Ilya Bakulin --Signature=_Wed__3_Dec_2008_19_23_35_+0300_fiwHd7NnN0xy/EQ2 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkk2sosACgkQo9vlj1oadwhSagCdFPYKGRVT1RV7WBbMaNT4YIWh NA0AoLC1srh2MPuxiDfs2F11C5gA1dLl =E8jH -----END PGP SIGNATURE----- --Signature=_Wed__3_Dec_2008_19_23_35_+0300_fiwHd7NnN0xy/EQ2-- From owner-freebsd-stable@FreeBSD.ORG Wed Dec 3 17:08:39 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F0484106564A for ; Wed, 3 Dec 2008 17:08:39 +0000 (UTC) (envelope-from henrik@50hz.ws) Received: from dsp.50hz.ws (50hz.ws [208.86.227.9]) by mx1.freebsd.org (Postfix) with ESMTP id B3FDB8FC14 for ; Wed, 3 Dec 2008 17:08:39 +0000 (UTC) (envelope-from henrik@50hz.ws) Received: from dsp.50hz.ws (localhost [127.0.0.1]) by dsp.50hz.ws (8.14.2/8.14.2) with ESMTP id mB3Gpv1I091362 for ; Wed, 3 Dec 2008 17:51:57 +0100 (CET) (envelope-from henrik@dsp.50hz.ws) Received: (from henrik@localhost) by dsp.50hz.ws (8.14.2/8.14.2/Submit) id mB3GpvkG091361 for stable@freebsd.org; Wed, 3 Dec 2008 17:51:57 +0100 (CET) (envelope-from henrik@dsp.50hz.ws) Date: Wed, 3 Dec 2008 17:51:56 +0100 From: Henrik Friedrichsen To: stable@freebsd.org Message-ID: <20081203165156.GA91351@dsp.50hz.ws> Mail-Followup-To: stable@freebsd.org References: <755632516.20081018001504@rulez.sk> <20081018020248.GB31303@cdnetworks.co.kr> <20081020012504.95adc0ca.nork@FreeBSD.org> <20081020071155.GH38923@cdnetworks.co.kr> <20081020132827.edbb2c53.webmaster@kibab.com> <20081021043152.GE43039@cdnetworks.co.kr> <20081030001123.cb1ebd9c.webmaster@kibab.com> <20081030051017.GB78796@cdnetworks.co.kr> <20081203192335.1da94c73.webmaster@kibab.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081203192335.1da94c73.webmaster@kibab.com> User-Agent: Mutt/1.4.2.3i Cc: Subject: Re: re0 problem 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: Wed, 03 Dec 2008 17:08:40 -0000 On Wed, Dec 03, 2008 at 07:23:35PM +0300, Ilya Bakulin wrote: > On Thu, 30 Oct 2008 14:10:17 +0900 > Pyun YongHyeon wrote: > > > > Please make sure you've (cold/warm) rebooted several times with > > this patch. Just applying the patch and using it without reboots > > doesn't necessary mean a working fix. Since it's hard to reproduce > > the issue even on a system with problematic controllers I'd like to > > have confidence in the patch. > > > > -- > > Regards, > > Pyun YongHyeon > > I've been using patched driver for a month, without any problems. Cold/warm reboots, panics, shutdowns occured regularly, but - no problems. Yesterday I've updated kernel to latest 7-STABLE & forgot to apply patch, and errors are here :-) > Applying patch once more fixed problems. > I think that perfect working of patched driver during past month definitely proves that your patch corrects incorrect behavior of re(4). Thank you very much! > > -- > Ilya Bakulin Here's another proof: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/125805 From owner-freebsd-stable@FreeBSD.ORG Wed Dec 3 17:09:00 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BD1D5106568A for ; Wed, 3 Dec 2008 17:09:00 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.freebsd.org (Postfix) with ESMTP id 7B3788FC0C for ; Wed, 3 Dec 2008 17:08:59 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (smmsp@localhost [127.0.0.1]) by dan.emsphone.com (8.14.3/8.14.3) with ESMTP id mB3H8ww0068988 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 3 Dec 2008 11:08:58 -0600 (CST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.14.3/8.14.3/Submit) id mB3H8voe068987; Wed, 3 Dec 2008 11:08:57 -0600 (CST) (envelope-from dan) Date: Wed, 3 Dec 2008 11:08:57 -0600 From: Dan Nelson To: Vlad GALU Message-ID: <20081203170857.GE22076@dan.emsphone.com> References: <20081203152330.GD22076@dan.emsphone.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-OS: FreeBSD 7.1-PRERELEASE User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-stable@freebsd.org Subject: Re: Weird truss output 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: Wed, 03 Dec 2008 17:09:00 -0000 In the last episode (Dec 03), Vlad GALU said: > On Wed, Dec 3, 2008 at 5:23 PM, Dan Nelson wrote: > > In the last episode (Dec 03), Vlad GALU said: > >> I'm running a statically linked binary, which I've built inside a > >> jail. The jail's libc & co are in sync with the host's. Truss then > >> shows this: > >> > >> -- cut here -- > >> -- UNKNOWN SYSCALL 1048532 -- > >> -- UNKNOWN SYSCALL 1048532 -- > > > > Is this a threaded app that you attached truss to after it was > > started? The method that truss uses to catch syscall enter/exit > > events doesn't indicate whether the event is an enter or an exit, > > so if you attach while a syscall is active, truss handles the exit > > event as if it were a syscall entry event, and never gets back in > > synch. It gets worse with threaded apps because each thread is > > another chance to get out of synch. Try this patch: > > You were right, this application was indeed threaded. The messages > still occur, although at a slightly lower rate. One other thing > that's not particularly helpful is this: > > -- cut here-- > read(1074283119,"\M-Ry\^A\0",7356800) = 4 (0x4) > -- and here -- > > I obviously don't have that many descriptors in my process. I can > live with the malformed message, but it's a PITA not to know which fd > the read was actually made from :( It looks like there's some other problem where truss either drops a syscall event, or puts some status fields into the wrong thread's structure. It seems to happen when two threads call blocking syscalls, and when they return, truss gets confused as to which thread called which syscall. The read syscall is probably still pending, and you're getting the arguments of the syscall that returned, printed as if it was the read syscall. When the read call completes, you'll probably get an --UNKNOWN SYSCALL-- line, or another mismatched syscall output line. An alternative it to use ktrace/kdump to trace the process; it's more cumbersome to use, but doesn't have problems with threaded processes. -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-stable@FreeBSD.ORG Wed Dec 3 17:29:27 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E0B901065679 for ; Wed, 3 Dec 2008 17:29:27 +0000 (UTC) (envelope-from wearabnet@yahoo.ca) Received: from n2.bullet.mail.gq1.yahoo.com (n2.bullet.mail.gq1.yahoo.com [67.195.9.85]) by mx1.freebsd.org (Postfix) with SMTP id 96B9E8FC21 for ; Wed, 3 Dec 2008 17:29:27 +0000 (UTC) (envelope-from wearabnet@yahoo.ca) Received: from [67.195.9.81] by n2.bullet.mail.gq1.yahoo.com with NNFMP; 03 Dec 2008 17:16:33 -0000 Received: from [67.195.9.102] by t1.bullet.mail.gq1.yahoo.com with NNFMP; 03 Dec 2008 17:16:33 -0000 Received: from [127.0.0.1] by omp106.mail.gq1.yahoo.com with NNFMP; 03 Dec 2008 17:16:33 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 6698.78608.bm@omp106.mail.gq1.yahoo.com Received: (qmail 39669 invoked by uid 60001); 3 Dec 2008 17:16:32 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.ca; h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID; b=6VdEUzYDzr63ULmPk1RxKq1FL1vk9PitplUd8lwKyjeTQYakRCVCAuRrrK6Xh6ABfRaUuVS7MuP0YGywvK394t+bghrMp5/PBVKwSkv8XLrMHkFBUxNKriXDzF4zE4KrkLzyspWH3wm3blg1XVlKDSOQG5d3KJJpdrguTsH3FZk=; X-YMail-OSG: pDUVzhEVM1monUSWSHcMzPtw_fdEtoN9NLstW0Kkj7klUlDh7g3MvyR1gQV08cIJZ7NsKG5SSmouzt0j0qCvFJTlY6rr5f.r9hSd.opd_ysyQeNyJOjE3uJWGccOPhfnnsKD_I8cFyKgfDkYbXy1k7KgIRXG2ydyk2r.ufAVJwwvfJDb5K9tsYRRPDh6JA-- Received: from [78.101.88.37] by web111308.mail.gq1.yahoo.com via HTTP; Wed, 03 Dec 2008 09:16:32 PST X-Mailer: YahooMailRC/1155.32 YahooMailWebService/0.7.260.1 Date: Wed, 3 Dec 2008 09:16:32 -0800 (PST) From: Abdullah Ibn Hamad Al-Marri To: FreeBSD STABLE MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <755219.38504.qm@web111308.mail.gq1.yahoo.com> Subject: Can't installworld for latest RELENG_7 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: Wed, 03 Dec 2008 17:29:28 -0000 Hello, install -o root -g wheel -m 444 la_LN.ISO8859-1.out /usr/share/locale/la_LN.ISO8859-1/LC_TIME install -o root -g wheel -m 444 lt_LT.ISO8859-4.out /usr/share/locale/lt_LT.ISO8859-4/LC_TIME install -o root -g wheel -m 444 lt_LT.ISO8859-13.out /usr/share/locale/lt_LT.ISO8859-13/LC_TIME install -o root -g wheel -m 444 lt_LT.UTF-8.out /usr/share/locale/lt_LT.UTF-8/LC_TIME install -o root -g wheel -m 444 mn_MN.UTF-8.out /usr/share/locale/mn_MN.UTF-8/LC_TIME install -o root -g wheel -m 444 nb_NO.ISO8859-1.out /usr/share/locale/nb_NO.ISO8859-1/LC_TIME install: /usr/share/locale/nb_NO.ISO8859-1/LC_TIME: Too many levels of symbolic links *** Error code 71 Stop in /usr/src/share/timedef. *** Error code 1 Stop in /usr/src/share. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Regards, -Abdullah Ibn Hamad Al-Marri Arab Portal http://www.WeArab.Net/ From owner-freebsd-stable@FreeBSD.ORG Wed Dec 3 18:06:25 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 11D891065673 for ; Wed, 3 Dec 2008 18:06:25 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.31]) by mx1.freebsd.org (Postfix) with ESMTP id C88C88FC18 for ; Wed, 3 Dec 2008 18:06:24 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: by yw-out-2324.google.com with SMTP id 9so1521806ywe.13 for ; Wed, 03 Dec 2008 10:06:24 -0800 (PST) Received: by 10.151.39.2 with SMTP id r2mr8864201ybj.193.1228327584115; Wed, 03 Dec 2008 10:06:24 -0800 (PST) Received: by 10.151.137.13 with HTTP; Wed, 3 Dec 2008 10:06:24 -0800 (PST) Message-ID: Date: Wed, 3 Dec 2008 20:06:24 +0200 From: "Vlad GALU" To: "Dan Nelson" In-Reply-To: <20081203170857.GE22076@dan.emsphone.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20081203152330.GD22076@dan.emsphone.com> <20081203170857.GE22076@dan.emsphone.com> Cc: freebsd-stable@freebsd.org Subject: Re: Weird truss output 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: Wed, 03 Dec 2008 18:06:25 -0000 On Wed, Dec 3, 2008 at 7:08 PM, Dan Nelson wrote: > In the last episode (Dec 03), Vlad GALU said: >> On Wed, Dec 3, 2008 at 5:23 PM, Dan Nelson wrote: >> > In the last episode (Dec 03), Vlad GALU said: >> >> I'm running a statically linked binary, which I've built inside a >> >> jail. The jail's libc & co are in sync with the host's. Truss then >> >> shows this: >> >> >> >> -- cut here -- >> >> -- UNKNOWN SYSCALL 1048532 -- >> >> -- UNKNOWN SYSCALL 1048532 -- >> > >> > Is this a threaded app that you attached truss to after it was >> > started? The method that truss uses to catch syscall enter/exit >> > events doesn't indicate whether the event is an enter or an exit, >> > so if you attach while a syscall is active, truss handles the exit >> > event as if it were a syscall entry event, and never gets back in >> > synch. It gets worse with threaded apps because each thread is >> > another chance to get out of synch. Try this patch: >> >> You were right, this application was indeed threaded. The messages >> still occur, although at a slightly lower rate. One other thing >> that's not particularly helpful is this: >> >> -- cut here-- >> read(1074283119,"\M-Ry\^A\0",7356800) = 4 (0x4) >> -- and here -- >> >> I obviously don't have that many descriptors in my process. I can >> live with the malformed message, but it's a PITA not to know which fd >> the read was actually made from :( > > It looks like there's some other problem where truss either drops a > syscall event, or puts some status fields into the wrong thread's > structure. It seems to happen when two threads call blocking syscalls, > and when they return, truss gets confused as to which thread called > which syscall. The read syscall is probably still pending, and you're > getting the arguments of the syscall that returned, printed as if it > was the read syscall. When the read call completes, you'll probably > get an --UNKNOWN SYSCALL-- line, or another mismatched syscall output > line. > > An alternative it to use ktrace/kdump to trace the process; it's more > cumbersome to use, but doesn't have problems with threaded processes. Now why didn't I think of that? :/ Thanks for the suggestion! -- ~/.signature: no such file or directory From owner-freebsd-stable@FreeBSD.ORG Wed Dec 3 18:36:50 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D3A281065677 for ; Wed, 3 Dec 2008 18:36:50 +0000 (UTC) (envelope-from marius@nuenneri.ch) Received: from el-out-1112.google.com (el-out-1112.google.com [209.85.162.178]) by mx1.freebsd.org (Postfix) with ESMTP id 91F5C8FC0A for ; Wed, 3 Dec 2008 18:36:50 +0000 (UTC) (envelope-from marius@nuenneri.ch) Received: by el-out-1112.google.com with SMTP id v27so1033750ele.17 for ; Wed, 03 Dec 2008 10:36:49 -0800 (PST) Received: by 10.90.92.16 with SMTP id p16mr2068753agb.91.1228327417729; Wed, 03 Dec 2008 10:03:37 -0800 (PST) Received: by 10.90.73.15 with HTTP; Wed, 3 Dec 2008 10:03:37 -0800 (PST) Message-ID: Date: Wed, 3 Dec 2008 19:03:37 +0100 From: "=?ISO-8859-1?Q?Marius_N=FCnnerich?=" To: "Dan Nelson" In-Reply-To: <20081203170857.GE22076@dan.emsphone.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20081203152330.GD22076@dan.emsphone.com> <20081203170857.GE22076@dan.emsphone.com> Cc: Vlad GALU , freebsd-stable@freebsd.org Subject: Re: Weird truss output 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: Wed, 03 Dec 2008 18:36:50 -0000 On Wed, Dec 3, 2008 at 6:08 PM, Dan Nelson wrote: > In the last episode (Dec 03), Vlad GALU said: >> On Wed, Dec 3, 2008 at 5:23 PM, Dan Nelson wrote: >> > In the last episode (Dec 03), Vlad GALU said: >> >> I'm running a statically linked binary, which I've built inside a >> >> jail. The jail's libc & co are in sync with the host's. Truss then >> >> shows this: >> >> >> >> -- cut here -- >> >> -- UNKNOWN SYSCALL 1048532 -- >> >> -- UNKNOWN SYSCALL 1048532 -- >> > >> > Is this a threaded app that you attached truss to after it was >> > started? The method that truss uses to catch syscall enter/exit >> > events doesn't indicate whether the event is an enter or an exit, >> > so if you attach while a syscall is active, truss handles the exit >> > event as if it were a syscall entry event, and never gets back in >> > synch. It gets worse with threaded apps because each thread is >> > another chance to get out of synch. Try this patch: >> >> You were right, this application was indeed threaded. The messages >> still occur, although at a slightly lower rate. One other thing >> that's not particularly helpful is this: >> >> -- cut here-- >> read(1074283119,"\M-Ry\^A\0",7356800) = 4 (0x4) >> -- and here -- >> >> I obviously don't have that many descriptors in my process. I can >> live with the malformed message, but it's a PITA not to know which fd >> the read was actually made from :( > > It looks like there's some other problem where truss either drops a > syscall event, or puts some status fields into the wrong thread's > structure. It seems to happen when two threads call blocking syscalls, > and when they return, truss gets confused as to which thread called > which syscall. The read syscall is probably still pending, and you're > getting the arguments of the syscall that returned, printed as if it > was the read syscall. When the read call completes, you'll probably > get an --UNKNOWN SYSCALL-- line, or another mismatched syscall output > line. > > An alternative it to use ktrace/kdump to trace the process; it's more > cumbersome to use, but doesn't have problems with threaded processes. Maybe DTrace will help you but I don't know if there is enough ported yet. From owner-freebsd-stable@FreeBSD.ORG Wed Dec 3 18:56:25 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B9D0E1065677 for ; Wed, 3 Dec 2008 18:56:25 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.freebsd.org (Postfix) with ESMTP id CFBC38FC14 for ; Wed, 3 Dec 2008 18:56:24 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (smmsp@localhost [127.0.0.1]) by dan.emsphone.com (8.14.3/8.14.3) with ESMTP id mB3IuNFO026962 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 3 Dec 2008 12:56:24 -0600 (CST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.14.3/8.14.3/Submit) id mB3IuMqp026961; Wed, 3 Dec 2008 12:56:22 -0600 (CST) (envelope-from dan) Date: Wed, 3 Dec 2008 12:56:22 -0600 From: Dan Nelson To: Vlad GALU Message-ID: <20081203185622.GF22076@dan.emsphone.com> References: <20081203152330.GD22076@dan.emsphone.com> <20081203170857.GE22076@dan.emsphone.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081203170857.GE22076@dan.emsphone.com> X-OS: FreeBSD 7.1-PRERELEASE User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-stable@freebsd.org Subject: Re: Weird truss output 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: Wed, 03 Dec 2008 18:56:25 -0000 In the last episode (Dec 03), Dan Nelson said: > It looks like there's some other problem where truss either drops a > syscall event, or puts some status fields into the wrong thread's > structure. It seems to happen when two threads call blocking > syscalls, and when they return, truss gets confused as to which > thread called which syscall. The read syscall is probably still > pending, and you're getting the arguments of the syscall that > returned, printed as if it was the read syscall. When the read call > completes, you'll probably get an --UNKNOWN SYSCALL-- line, or > another mismatched syscall output line. It turns out that was the problem. There was a global structure that held syscall information. Converting it to a per-thread structure makes it work much better :) If you're adventurous, try applying the patch at http://www.evoy.net/FreeBSD/truss.diff , which fixes that problem plus a bunch of other stuff. If you're not adventurous, try the following instead, which just fixes the per-thread problem. Index: i386-fbsd.c =================================================================== RCS file: /home/ncvs/src/usr.bin/truss/i386-fbsd.c,v retrieving revision 1.29 diff -u -r1.29 i386-fbsd.c --- i386-fbsd.c 28 Jul 2007 23:15:04 -0000 1.29 +++ i386-fbsd.c 3 Dec 2008 18:48:23 -0000 @@ -49,6 +49,7 @@ #include #include +#include #include #include #include @@ -77,29 +78,29 @@ * 'struct syscall' describes the system call; it may be NULL, however, * if we don't know about this particular system call yet. */ -static struct freebsd_syscall { +struct freebsd_syscall { struct syscall *sc; const char *name; int number; unsigned long *args; int nargs; /* number of arguments -- *not* number of words! */ char **s_args; /* the printable arguments */ -} fsc; +}; /* Clear up and free parts of the fsc structure. */ static __inline void -clear_fsc(void) { - if (fsc.args) { - free(fsc.args); +clear_fsc(struct freebsd_syscall *fsc) { + if (fsc->args) { + free(fsc->args); } - if (fsc.s_args) { + if (fsc->s_args) { int i; - for (i = 0; i < fsc.nargs; i++) - if (fsc.s_args[i]) - free(fsc.s_args[i]); - free(fsc.s_args); + for (i = 0; i < fsc->nargs; i++) + if (fsc->s_args[i]) + free(fsc->s_args[i]); + free(fsc->s_args); } - memset(&fsc, 0, sizeof(fsc)); + memset(fsc, 0, sizeof(*fsc)); } /* @@ -117,9 +118,20 @@ unsigned int parm_offset; struct syscall *sc = NULL; struct ptrace_io_desc iorequest; + struct freebsd_syscall *fsc; + cpid = trussinfo->curthread->tid; - clear_fsc(); + fsc = trussinfo->curthread->fsc; + if (fsc == NULL) + { + fsc = malloc(sizeof(*fsc)); + if (fsc == NULL) + errx(1, "cannot allocate syscall struct"); + memset(fsc, 0, sizeof(*fsc)); + trussinfo->curthread->fsc = fsc; + } else + clear_fsc(fsc); if (ptrace(PT_GETREGS, cpid, (caddr_t)®s, 0) < 0) { @@ -145,17 +157,24 @@ break; } - fsc.number = syscall_num; - fsc.name = + fsc->number = syscall_num; + fsc->name = (syscall_num < 0 || syscall_num > nsyscalls) ? NULL : syscallnames[syscall_num]; - if (!fsc.name) { - fprintf(trussinfo->outfile, "-- UNKNOWN SYSCALL %d --\n", syscall_num); + if (!fsc->name) { + fprintf(trussinfo->outfile, "-- UNKNOWN SYSCALL %u (0x%08x) --\n", syscall_num, syscall_num); + if ((unsigned int)syscall_num > 0x1000) { + /* When attaching to a running process, we have a 50-50 chance + of attaching to a process waiting in a syscall, which means + our first trap is an exit instead of an entry and we're out + of synch. Reset our flag */ + trussinfo->curthread->in_syscall = 0; + } } - if (fsc.name && (trussinfo->flags & FOLLOWFORKS) - && ((!strcmp(fsc.name, "fork") - || !strcmp(fsc.name, "rfork") - || !strcmp(fsc.name, "vfork")))) + if (fsc->name && (trussinfo->flags & FOLLOWFORKS) + && ((!strcmp(fsc->name, "fork") + || !strcmp(fsc->name, "rfork") + || !strcmp(fsc->name, "vfork")))) { trussinfo->curthread->in_fork = 1; } @@ -163,30 +182,30 @@ if (nargs == 0) return; - fsc.args = malloc((1+nargs) * sizeof(unsigned long)); + fsc->args = malloc((1+nargs) * sizeof(unsigned long)); iorequest.piod_op = PIOD_READ_D; iorequest.piod_offs = (void *)parm_offset; - iorequest.piod_addr = fsc.args; + iorequest.piod_addr = fsc->args; iorequest.piod_len = (1+nargs) * sizeof(unsigned long); ptrace(PT_IO, cpid, (caddr_t)&iorequest, 0); if (iorequest.piod_len == 0) return; - if (fsc.name) - sc = get_syscall(fsc.name); + if (fsc->name) + sc = get_syscall(fsc->name); if (sc) { - fsc.nargs = sc->nargs; + fsc->nargs = sc->nargs; } else { #if DEBUG fprintf(trussinfo->outfile, "unknown syscall %s -- setting args to %d\n", - fsc.name, nargs); + fsc->name, nargs); #endif - fsc.nargs = nargs; + fsc->nargs = nargs; } - fsc.s_args = malloc((1+fsc.nargs) * sizeof(char*)); - memset(fsc.s_args, 0, fsc.nargs * sizeof(char*)); - fsc.sc = sc; + fsc->s_args = malloc((1+fsc->nargs) * sizeof(char*)); + memset(fsc->s_args, 0, fsc->nargs * sizeof(char*)); + fsc->sc = sc; /* * At this point, we set up the system call arguments. @@ -196,21 +215,21 @@ * passed in *and* out, however. */ - if (fsc.name) { + if (fsc->name) { #if DEBUG - fprintf(stderr, "syscall %s(", fsc.name); + fprintf(stderr, "syscall %s(", fsc->name); #endif - for (i = 0; i < fsc.nargs; i++) { + for (i = 0; i < fsc->nargs; i++) { #if DEBUG fprintf(stderr, "0x%x%s", sc - ? fsc.args[sc->args[i].offset] - : fsc.args[i], - i < (fsc.nargs - 1) ? "," : ""); + ? fsc->args[sc->args[i].offset] + : fsc->args[i], + i < (fsc->nargs - 1) ? "," : ""); #endif if (sc && !(sc->args[i].type & OUT)) { - fsc.s_args[i] = print_arg(&sc->args[i], fsc.args, 0, trussinfo); + fsc->s_args[i] = print_arg(&sc->args[i], fsc->args, 0, trussinfo); } } #if DEBUG @@ -222,23 +241,23 @@ fprintf(trussinfo->outfile, "\n"); #endif - if (fsc.name != NULL && - (!strcmp(fsc.name, "execve") || !strcmp(fsc.name, "exit"))) { + if (fsc->name != NULL && + (!strcmp(fsc->name, "execve") || !strcmp(fsc->name, "exit"))) { /* XXX * This could be done in a more general * manner but it still wouldn't be very pretty. */ - if (!strcmp(fsc.name, "execve")) { + if (!strcmp(fsc->name, "execve")) { if ((trussinfo->flags & EXECVEARGS) == 0) - if (fsc.s_args[1]) { - free(fsc.s_args[1]); - fsc.s_args[1] = NULL; + if (fsc->s_args[1]) { + free(fsc->s_args[1]); + fsc->s_args[1] = NULL; } if ((trussinfo->flags & EXECVEENVS) == 0) - if (fsc.s_args[2]) { - free(fsc.s_args[2]); - fsc.s_args[2] = NULL; + if (fsc->s_args[2]) { + free(fsc->s_args[2]); + fsc->s_args[2] = NULL; } } @@ -262,9 +281,14 @@ int i; int errorp; struct syscall *sc; + struct freebsd_syscall *fsc; - if (fsc.name == NULL) + fsc = trussinfo->curthread->fsc; + if (fsc == NULL || fsc->name == NULL) { + fprintf(trussinfo->outfile, "No syscall?\n"); + fflush(trussinfo->outfile); return (-1); + } cpid = trussinfo->curthread->tid; if (ptrace(PT_GETREGS, cpid, (caddr_t)®s, 0) < 0) @@ -281,10 +305,10 @@ * stand some significant cleaning. */ - sc = fsc.sc; + sc = fsc->sc; if (!sc) { - for (i = 0; i < fsc.nargs; i++) - asprintf(&fsc.s_args[i], "0x%lx", fsc.args[i]); + for (i = 0; i < fsc->nargs; i++) + asprintf(&fsc->s_args[i], "0x%lx", fsc->args[i]); } else { /* * Here, we only look for arguments that have OUT masked in -- @@ -298,10 +322,10 @@ * it may not be valid. */ if (errorp) - asprintf(&temp, "0x%lx", fsc.args[sc->args[i].offset]); + asprintf(&temp, "0x%lx", fsc->args[sc->args[i].offset]); else - temp = print_arg(&sc->args[i], fsc.args, retval, trussinfo); - fsc.s_args[i] = temp; + temp = print_arg(&sc->args[i], fsc->args, retval, trussinfo); + fsc->s_args[i] = temp; } } } @@ -312,15 +336,15 @@ * The nargs check is so we don't have to do yet another strcmp on every * syscall. */ - if (!errorp && fsc.nargs == 0 && fsc.name && strcmp(fsc.name, "pipe") == 0) { - fsc.nargs = 1; - fsc.s_args = malloc((1+fsc.nargs) * sizeof(char*)); - asprintf(&fsc.s_args[0], "[%d,%d]", (int)retval, regs.r_edx); + if (!errorp && fsc->nargs == 0 && fsc->name && strcmp(fsc->name, "pipe") == 0) { + fsc->nargs = 1; + fsc->s_args = malloc((1+fsc->nargs) * sizeof(char*)); + asprintf(&fsc->s_args[0], "[%d,%d]", (int)retval, regs.r_edx); retval = 0; } - if (fsc.name != NULL && - (!strcmp(fsc.name, "execve") || !strcmp(fsc.name, "exit"))) { + if (fsc->name != NULL && + (!strcmp(fsc->name, "execve") || !strcmp(fsc->name, "exit"))) { trussinfo->curthread->in_syscall = 1; } @@ -329,8 +353,8 @@ * but that complicates things considerably. */ - print_syscall_ret(trussinfo, fsc.name, fsc.nargs, fsc.s_args, errorp, retval); - clear_fsc(); + print_syscall_ret(trussinfo, fsc->name, fsc->nargs, fsc->s_args, errorp, retval); + clear_fsc(fsc); return (retval); } Index: setup.c =================================================================== RCS file: /home/ncvs/src/usr.bin/truss/setup.c,v retrieving revision 1.24 diff -u -r1.24 setup.c --- setup.c 26 Jun 2007 22:42:37 -0000 1.24 +++ setup.c 3 Dec 2008 18:49:06 -0000 @@ -166,6 +166,7 @@ np->tid = lwpid; np->in_fork = 0; np->in_syscall = 0; + np->fsc = NULL; SLIST_INSERT_HEAD(&info->threadlist, np, entries); info->curthread = np; } Index: truss.h =================================================================== RCS file: /home/ncvs/src/usr.bin/truss/truss.h,v retrieving revision 1.8 diff -u -r1.8 truss.h --- truss.h 10 Apr 2007 04:03:34 -0000 1.8 +++ truss.h 3 Dec 2008 18:42:54 -0000 @@ -38,6 +38,7 @@ { SLIST_ENTRY(threadinfo) entries; lwpid_t tid; + void *fsc; int in_syscall; int in_fork; }; -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-stable@FreeBSD.ORG Wed Dec 3 19:01:21 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 334731065673 for ; Wed, 3 Dec 2008 19:01:21 +0000 (UTC) (envelope-from dimitry@andric.com) Received: from tensor.andric.com (cl-327.ede-01.nl.sixxs.net [IPv6:2001:7b8:2ff:146::2]) by mx1.freebsd.org (Postfix) with ESMTP id BBDF28FC1C for ; Wed, 3 Dec 2008 19:01:20 +0000 (UTC) (envelope-from dimitry@andric.com) Received: from [IPv6:2001:7b8:3a7:0:e14b:ad63:e472:d6fb] (unknown [IPv6:2001:7b8:3a7:0:e14b:ad63:e472:d6fb]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 1740284438 for ; Wed, 3 Dec 2008 20:01:19 +0100 (CET) Message-ID: <4936D781.8090907@andric.com> Date: Wed, 03 Dec 2008 20:01:21 +0100 From: Dimitry Andric User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.1b2pre) Gecko/20081125 Shredder/3.0b1pre MIME-Version: 1.0 To: FreeBSD STABLE Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: device_attach: acpi_hpet0 attach returned 12 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: Wed, 03 Dec 2008 19:01:21 -0000 Hi, Apparently there's a HPET on one of my 7.1-ALMOST-STABLE machines, and it's enabled in the BIOS too, but it fails to attach: Copyright (c) 1992-2008 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 7.1-PRERELEASE #0: Fri Nov 28 16:04:48 CET 2008 dim@vfbsd7.home.andric.com:/usr/obj/usr/src/sys/TENSOR Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: VIA Esther processor 1200MHz (1200.01-MHz 686-class CPU) Origin = "CentaurHauls" Id = 0x6a9 Stepping = 9 Features=0xa7c9baff Features2=0x181 VIA Padlock Features=0x3fcc real memory = 518914048 (494 MB) avail memory = 498270208 (475 MB) ACPI APIC Table: ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 cryptosoft0: on motherboard padlock0: on motherboard acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, 1ede0000 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 acpi_hpet0: iomem 0xfe800000-0xfe8003ff on acpi0 device_attach: acpi_hpet0 attach returned 12 [...] It looks like the HPET should be at address 0xfe800000-0xfe8003ff, but if I look in the output of "devinfo -rv", I see the following: nexus0 cryptosoft0 padlock0 apic0 acpi0 Interrupt request lines: 9 I/O ports: 0x10-0x1f 0x22-0x3f 0x44-0x5f 0x62-0x63 0x65-0x6f 0x74-0x7f 0x91-0x93 0xa2-0xbf 0xe0-0xef 0x290-0x297 0x400-0x47f 0x4d0-0x4d1 0x500-0x50f 0x800-0x805 I/O memory addresses: 0xf0000-0xfffff 0x1eee0000-0x1eefffff 0xfe800000-0xfe8000ff [...] So apparently the ACPI memory range information says the HPET only uses 256 bytes of iomem, while FreeBSD assumes 1024. The latter is correct, at least according to the Intel HPET spec I dug up somewhere. When I dump ACPI info using acpidump -dt, I see: [...] /* HPET: Length=56, Revision=1, Checksum=196, OEMID=CN700, OEM Table ID=AWRDACPI, OEM Revision=0x42302e31, Creator ID=AWRD, Creator Revision=0x98 HPET Number=0 ADDR=0xfe800000:0[0] (Memory) HW Rev=0x1 Comparitors=2 Counter Size=0 Legacy IRQ routing capable={TRUE} PCI Vendor ID=0x1106 Minimal Tick=144 */ [...] Device (MEM) { Name (_HID, EisaId ("PNP0C01")) Method (_CRS, 0, NotSerialized) { Name (BUF0, ResourceTemplate () { Memory32Fixed (ReadOnly, 0x000F0000, // Address Base 0x00010000, // Address Length ) Memory32Fixed (ReadWrite, 0xFE800000, // Address Base 0x00000100, // Address Length ) [...] Device (HPET) { Name (_HID, EisaId ("PNP0103")) Name (ATT3, ResourceTemplate () { IRQNoFlags () {0} IRQNoFlags () {8} Memory32Fixed (ReadWrite, 0xFE800000, // Address Base 0x00000400, // Address Length ) }) [...] So apparently the devinfo information is gotten from ACPI's "Device (MEM)" declaration, which seems to be inconsistent with the "Device (HPET)" declaration later on. My question is therefore: is this just buggy ACPI information in the BIOS, and can I override it with a custom DSDT file in the boot loader? Or is there some other workaround? From owner-freebsd-stable@FreeBSD.ORG Wed Dec 3 19:36:35 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E17001065677 for ; Wed, 3 Dec 2008 19:36:35 +0000 (UTC) (envelope-from frode@nordahl.net) Received: from smtp3.powertech.no (smtp3.powertech.no [195.159.0.178]) by mx1.freebsd.org (Postfix) with ESMTP id A1FE88FC22 for ; Wed, 3 Dec 2008 19:36:35 +0000 (UTC) (envelope-from frode@nordahl.net) Received: from dhcp1.xu.nordahl.net (dhcp1.xu.nordahl.net [195.159.148.120]) by smtp3.powertech.no (Postfix) with ESMTP id EF293C5C93; Wed, 3 Dec 2008 20:12:22 +0100 (CET) Message-Id: From: Frode Nordahl To: Kostik Belousov In-Reply-To: <20081203173939.GA2401@deviant.kiev.zoral.com.ua> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Date: Wed, 3 Dec 2008 20:12:22 +0100 References: <3B675385-956D-4A26-8E09-E338DF7D7244@nordahl.net> <20081203173939.GA2401@deviant.kiev.zoral.com.ua> X-Mailer: Apple Mail (2.929.2) Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 7.1-PRERELEASE-p1, panic: dqget: free dquot isn't 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: Wed, 03 Dec 2008 19:36:36 -0000 (moved to freebsd-stable) On 3. des.. 2008, at 18.39, Kostik Belousov wrote: >> db> where >> Tracing pid 41111 tid 100199 td 0xffffff0056f1f370 >> kdb_enter_why() at kdb_enter_why+0x3d >> panic() at panic+0x17b >> dqget() at dqget+0xaa4 >> getinoquota() at getinoquota+0x5b >> ufs_access() at ufs_access+0x28c >> ufs_lookup() at ufs_lookup+0x9fe >> vfs_cache_lookup() at vfs_cache_lookup+0xf8 >> VOP_LOOKUP_APV() at VOP_LOOKUP_APV+0x40 >> lookup() at lookup+0x531 >> namei() at namei+0x35d >> kern_rmdir() at kern_rmdir+0xbd >> syscall() at syscall+0x256 >> Xfast_syscall() at Xfast_syscall+0xab > > For the start, I want to see the content of the *dq in the dqget() > frame. I am unable to get to *dq :-( (kgdb) frame 10 #10 0xffffffff806dbc54 in dqget (vp=0xffffff011e0767e0, id=419444, ump=0xffffff00038a9000, type=0, dqp=0xffffff0122e47268) at /usr/src/sys/ufs/ufs/ufs_quota.c:1210 1210 panic("dqget: free dquot isn't"); (kgdb) print dq Variable "dq" is not available. I will try to provoke the panic again and see if I can get more info from DDB. (Any hints as to what to ask ddb to get the information you requested?) (I'll put my kernel.debug and vmcore.0 in an archve somewhere and mail you the URL privately if you are up to download 126MB) -- Frode Nordahl From owner-freebsd-stable@FreeBSD.ORG Wed Dec 3 19:43:54 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 26957106564A for ; Wed, 3 Dec 2008 19:43:54 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.terabit.net.ua (mail.terabit.net.ua [195.137.202.147]) by mx1.freebsd.org (Postfix) with ESMTP id BE6D68FC08 for ; Wed, 3 Dec 2008 19:43:53 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from skuns.zoral.com.ua ([91.193.166.194] helo=mail.zoral.com.ua) by mail.terabit.net.ua with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1L7xdX-000O4D-GJ; Wed, 03 Dec 2008 21:43:51 +0200 Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id mB3Jhmpx008749 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 3 Dec 2008 21:43:48 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id mB3Jhmix015674; Wed, 3 Dec 2008 21:43:48 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id mB3Jhmxe015673; Wed, 3 Dec 2008 21:43:48 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 3 Dec 2008 21:43:48 +0200 From: Kostik Belousov To: Frode Nordahl Message-ID: <20081203194348.GB2401@deviant.kiev.zoral.com.ua> References: <3B675385-956D-4A26-8E09-E338DF7D7244@nordahl.net> <20081203173939.GA2401@deviant.kiev.zoral.com.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="yNb1oOkm5a9FJOVX" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: ClamAV version 0.93.3, clamav-milter version 0.93.3 on skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua X-Virus-Scanned: mail.terabit.net.ua 1L7xdX-000O4D-GJ 765fdd06359df0fa028f66d7e2ef1451 X-Terabit: YES Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 7.1-PRERELEASE-p1, panic: dqget: free dquot isn't 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: Wed, 03 Dec 2008 19:43:54 -0000 --yNb1oOkm5a9FJOVX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Dec 03, 2008 at 08:12:22PM +0100, Frode Nordahl wrote: > (moved to freebsd-stable) >=20 > On 3. des.. 2008, at 18.39, Kostik Belousov wrote: >=20 > >>db> where > >>Tracing pid 41111 tid 100199 td 0xffffff0056f1f370 > >>kdb_enter_why() at kdb_enter_why+0x3d > >>panic() at panic+0x17b > >>dqget() at dqget+0xaa4 > >>getinoquota() at getinoquota+0x5b > >>ufs_access() at ufs_access+0x28c > >>ufs_lookup() at ufs_lookup+0x9fe > >>vfs_cache_lookup() at vfs_cache_lookup+0xf8 > >>VOP_LOOKUP_APV() at VOP_LOOKUP_APV+0x40 > >>lookup() at lookup+0x531 > >>namei() at namei+0x35d > >>kern_rmdir() at kern_rmdir+0xbd > >>syscall() at syscall+0x256 > >>Xfast_syscall() at Xfast_syscall+0xab > > > >For the start, I want to see the content of the *dq in the dqget() > >frame. >=20 >=20 > I am unable to get to *dq :-( >=20 > (kgdb) frame 10 > #10 0xffffffff806dbc54 in dqget (vp=3D0xffffff011e0767e0, id=3D419444, > ump=3D0xffffff00038a9000, type=3D0, dqp=3D0xffffff0122e47268) > at /usr/src/sys/ufs/ufs/ufs_quota.c:1210 > 1210 panic("dqget: free dquot isn't"); If this is repeatable, change panic to panic("dqget: free dquot isn't %p", dq); and then in kgdb p/x *(struct dquot *) > (kgdb) print dq > Variable "dq" is not available. >=20 > I will try to provoke the panic again and see if I can get more info =20 > from DDB. (Any hints as to what to ask ddb to get the information you =20 > requested?) >=20 > (I'll put my kernel.debug and vmcore.0 in an archve somewhere and mail = =20 > you the URL privately if you are up to download 126MB) >=20 > -- > Frode Nordahl >=20 >=20 --yNb1oOkm5a9FJOVX Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkk24XMACgkQC3+MBN1Mb4jtRgCeOi159RfIPG5fdb+YgHsAFK9g QdwAnj8BnuSj3FsmZlIlHtwrJjkt6LkV =GgbU -----END PGP SIGNATURE----- --yNb1oOkm5a9FJOVX-- From owner-freebsd-stable@FreeBSD.ORG Wed Dec 3 19:48:11 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1CE581065689 for ; Wed, 3 Dec 2008 19:48:11 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: from mail-gx0-f19.google.com (mail-gx0-f19.google.com [209.85.217.19]) by mx1.freebsd.org (Postfix) with ESMTP id B5EB88FC16 for ; Wed, 3 Dec 2008 19:48:09 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: by gxk12 with SMTP id 12so2563174gxk.19 for ; Wed, 03 Dec 2008 11:48:08 -0800 (PST) Received: by 10.151.107.8 with SMTP id j8mr1999877ybm.28.1228333342462; Wed, 03 Dec 2008 11:42:22 -0800 (PST) Received: by 10.151.137.13 with HTTP; Wed, 3 Dec 2008 11:42:22 -0800 (PST) Message-ID: Date: Wed, 3 Dec 2008 21:42:22 +0200 From: "Vlad GALU" To: "Dan Nelson" In-Reply-To: <20081203185622.GF22076@dan.emsphone.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20081203152330.GD22076@dan.emsphone.com> <20081203170857.GE22076@dan.emsphone.com> <20081203185622.GF22076@dan.emsphone.com> Cc: freebsd-stable@freebsd.org Subject: Re: Weird truss output 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: Wed, 03 Dec 2008 19:48:11 -0000 On Wed, Dec 3, 2008 at 8:56 PM, Dan Nelson wrote: [...] Am I doing something wrong? I've applied the full diff, rebuilt truss, now I get this: -- cut here -- root@goofy / # truss -p 52731 SIGNAL 17 (SIGSTOP) -- UNKNOWN SYSCALL 1048535 -- -- UNKNOWN SYSCALL 1048496 -- -- UNKNOWN SYSCALL 1048559 -- -- UNKNOWN SYSCALL 1048559 -- -- UNKNOWN SYSCALL -8464 -- -- UNKNOWN SYSCALL -8464 -- -- UNKNOWN SYSCALL 527 -- -- UNKNOWN SYSCALL 527 -- /100084: read(1074283119,"\M-|\M^WP\^A",7356800) = 4 (0x4) -- UNKNOWN SYSCALL 527 -- -- UNKNOWN SYSCALL 7385248 -- -- and here -- Perhaps I should mention that I block all signals from all threads, except for one, where I do all the handling/cleanup. -- ~/.signature: no such file or directory From owner-freebsd-stable@FreeBSD.ORG Wed Dec 3 20:18:15 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A68E91065689; Wed, 3 Dec 2008 20:18:15 +0000 (UTC) (envelope-from fernan@iib.unsam.edu.ar) Received: from unsam.edu.ar (mx.unsam.edu.ar [200.45.170.30]) by mx1.freebsd.org (Postfix) with ESMTP id 683438FC17; Wed, 3 Dec 2008 20:18:11 +0000 (UTC) (envelope-from fernan@iib.unsam.edu.ar) Received: from gama.iib.unsam.edu.ar by unsam.edu.ar (MDaemon.PRO.v8.1.1.R) with ESMTP id md50011554379.msg; Wed, 03 Dec 2008 18:17:50 -0200 Received: from gama.iib.unsam.edu.ar (localhost [127.0.0.1]) by gama.iib.unsam.edu.ar (8.14.2/8.14.2) with ESMTP id mB3KHuXN060951; Wed, 3 Dec 2008 17:17:56 -0300 (ART) (envelope-from fernan@iib.unsam.edu.ar) Received: (from fernan@localhost) by gama.iib.unsam.edu.ar (8.14.2/8.14.2/Submit) id mB3KHZRZ060950; Wed, 3 Dec 2008 17:17:35 -0300 (ART) (envelope-from fernan@iib.unsam.edu.ar) X-Authentication-Warning: gama.iib.unsam.edu.ar: fernan set sender to fernan@iib.unsam.edu.ar using -f Date: Wed, 3 Dec 2008 17:17:35 -0300 From: Fernan Aguero To: Kirk Strauser Message-ID: <20081203201735.GJ59053@iib.unsam.edu.ar> References: <520894aa0809301434h68b94628x54ec08fd48785feb@mail.gmail.com> <200810011134.49795.jhb@freebsd.org> <48EBDE69.1030609@delphij.net> <200810271251.28411.kirk@strauser.com> <20081029170522.GH47829@iib.unsam.edu.ar> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081029170522.GH47829@iib.unsam.edu.ar> User-Agent: Mutt/1.5.18 (2008-05-17) X-Spam-Processed: unsam-mail.unsam.edu.ar, Wed, 03 Dec 2008 18:17:50 -0200 (not processed: spam filter disabled) X-Return-Path: fernan@iib.unsam.edu.ar X-MDAV-Processed: unsam-mail.unsam.edu.ar, Wed, 03 Dec 2008 18:17:55 -0200 Cc: d@delphij.net, freebsd-stable@freebsd.org, re@freebsd.org, John Baldwin Subject: Re: [FreeBSD] Fix for ServerWorks HT1000 in upcoming 7.1? 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: Wed, 03 Dec 2008 20:18:15 -0000 +----[ To Kirk Strauser (29.Oct.2008 14:05): | | > On Tuesday 07 October 2008 17:10:49 Xin LI wrote: | > > Did anyone who can trigger the data corruption has tried John's patch | > > and let us know if it worked? | > > | > > Cheers, | > | > I can confirm that it works on my PowerEdge SC1435. With both controllers | > running in SATA150 mode, I have an uptime of 101 days with moderately heavy | > load. | > -- | > Kirk Strauser | | Same here. The ata_ht1000.patch referenced in this thread | works, in my case at least with 1 controller running in | SATA150 mode (I have only 1 disk). | | However, the recent 7.1-BETA2 does not work for me, contrary | to reports saying that this BETA contains the patch. Looking | at the sources, it seems evident that the patch applied is | not identical to the ata_ht1000.patch in this thread. | | This patch: | http://people.freebsd.org/~jhb/patches/ata_ht1000.patch | is the only requirement to turn a broken 7.1-BETA1 into a | working 7.1 for a Dell PowerEdge SC1435. | | The recent 7.1-BETA2, does not work! | | Fernan | +----] Hi, I've been tracking the 7.1 release page but so far I haven't seen any update lately ... any news on when a new BETA/RC will be out for testing? Fernan From owner-freebsd-stable@FreeBSD.ORG Wed Dec 3 21:23:28 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F1AE31065670 for ; Wed, 3 Dec 2008 21:23:28 +0000 (UTC) (envelope-from dgeo@ec-marseille.fr) Received: from meli.ec-marseille.fr (meli.ec-marseille.fr [147.94.19.138]) by mx1.freebsd.org (Postfix) with ESMTP id A7C4B8FC17 for ; Wed, 3 Dec 2008 21:23:28 +0000 (UTC) (envelope-from dgeo@ec-marseille.fr) Received: from localhost (amavis4.serv.int [10.3.0.48]) by meli.ec-marseille.fr (GrosseBox 1743 XXL) with ESMTP id AE1AC27882A; Wed, 3 Dec 2008 22:23:26 +0100 (CET) X-Virus-Scanned: amavisd-new at ec-marseille.fr Received: from meli.ec-marseille.fr ([10.3.0.12]) by localhost (amavis4.serv.int [10.3.0.48]) (amavisd-new, port 10024) with LMTP id BIqySuIn6wcY; Wed, 3 Dec 2008 22:23:26 +0100 (CET) Received: from [10.0.3.6] (schizo.ec-marseille.fr [147.94.19.137]) (Authenticated sender: dgeo) by meli.ec-marseille.fr (GrosseBox 1743 XXL) with ESMTPSA id 0DBFF27881B; Wed, 3 Dec 2008 22:23:25 +0100 (CET) Message-ID: <4936F8C4.6090006@ec-marseille.fr> Date: Wed, 03 Dec 2008 22:23:16 +0100 From: geoffroy desvernay User-Agent: Thunderbird 2.0.0.18 (X11/20081125) MIME-Version: 1.0 To: d@delphij.net References: <4935069A.8060209@ec-marseille.fr> <49357BD0.4000008@delphij.net> <4935944A.9090509@ec-marseille.fr> <4935C453.8070301@delphij.net> <4935D67E.4070204@delphij.net> In-Reply-To: <4935D67E.4070204@delphij.net> X-Enigmail-Version: 0.95.0 OpenPGP: id=017C80AA Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigB4640E7D0D919B7E8C17FD5C" Cc: freebsd-stable@freebsd.org Subject: Re: RELENG_7_1: bce driver change generating too much interrupts ? 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: Wed, 03 Dec 2008 21:23:29 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigB4640E7D0D919B7E8C17FD5C Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Xin LI a =E9crit : > Hi guys, >=20 > I think I got a real fix. >=20 It seems to "work for me=AE" too Server under normal charge (smtp/imap/Maildir for ~1000 users, NFS filer), everything seems ok... (1h uptime for now) Thank you ! --=20 geoffroy desvernay --------------enigB4640E7D0D919B7E8C17FD5C Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJNvjIGbFYzwF8gKoRAkZdAKCHY/wCe1WJEwH+whOw0VgihMDb+wCdH608 /yrr2sf2qhBEvt1P8TwTOk4= =DIN1 -----END PGP SIGNATURE----- --------------enigB4640E7D0D919B7E8C17FD5C-- From owner-freebsd-stable@FreeBSD.ORG Wed Dec 3 21:55:10 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9C5501065686; Wed, 3 Dec 2008 21:55:06 +0000 (UTC) (envelope-from kensmith@cse.Buffalo.EDU) Received: from phoebe.cse.buffalo.edu (phoebe.cse.buffalo.edu [128.205.32.89]) by mx1.freebsd.org (Postfix) with ESMTP id 2CDA88FC17; Wed, 3 Dec 2008 21:55:06 +0000 (UTC) (envelope-from kensmith@cse.Buffalo.EDU) Received: from [192.168.1.101] (cpe-74-77-179-53.buffalo.res.rr.com [74.77.179.53]) (authenticated bits=0) by phoebe.cse.buffalo.edu (8.14.1/8.13.7) with ESMTP id mB3Lsltn075507 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 3 Dec 2008 16:54:51 -0500 (EST) (envelope-from kensmith@cse.buffalo.edu) From: Ken Smith To: Fernan Aguero In-Reply-To: <20081203201735.GJ59053@iib.unsam.edu.ar> References: <520894aa0809301434h68b94628x54ec08fd48785feb@mail.gmail.com> <200810011134.49795.jhb@freebsd.org> <48EBDE69.1030609@delphij.net> <200810271251.28411.kirk@strauser.com> <20081029170522.GH47829@iib.unsam.edu.ar> <20081203201735.GJ59053@iib.unsam.edu.ar> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-dxVUjc5gSLw1HJU9PcOa" Date: Wed, 03 Dec 2008 16:54:42 -0500 Message-Id: <1228341282.23618.3.camel@neo.cse.buffalo.edu> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 FreeBSD GNOME Team Port X-DCC-Buffalo.EDU-Metrics: phoebe.cse.buffalo.edu 1336; Body=0 Fuz1=0 Fuz2=0 X-Spam-Status: No, score=1.7 required=5.0 tests=RCVD_IN_SORBS_DUL, RDNS_DYNAMIC autolearn=no version=3.2.3 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on phoebe.cse.buffalo.edu Cc: d@delphij.net, freebsd-stable@freebsd.org, re@freebsd.org, John Baldwin Subject: Re: [FreeBSD] Fix for ServerWorks HT1000 in upcoming 7.1? 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: Wed, 03 Dec 2008 21:55:10 -0000 --=-dxVUjc5gSLw1HJU9PcOa Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Wed, 2008-12-03 at 17:17 -0300, Fernan Aguero wrote: > I've been tracking the 7.1 release page but so far I haven't > seen any update lately ... any news on when a new BETA/RC > will be out for testing? A couple of days. Problems with an interface that was added after 7.0 were found. Since a release hasn't been done with that interface its being fixed so we can avoid needing to provide some ugly compatibility goo down the road. The code is in head now, hopefully it can be moved into stable/7 and releng/7.1 within the next day or two. Between 7.1-BETA2 and now we've had two show-stoppers that have been addressed and one security advisory that we needed to hold for, followed by this nit that's being worked on now. Hopefully that's the last big nit. --=20 Ken Smith - From there to here, from here to | kensmith@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | --=-dxVUjc5gSLw1HJU9PcOa Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEABECAAYFAkk3ABkACgkQ/G14VSmup/Z0eACfRcEX4pB1eCA66OoRvPUFn3Rr +PkAn3qUki994PzsnP8vbMYglTzzz2Rq =P4Zg -----END PGP SIGNATURE----- --=-dxVUjc5gSLw1HJU9PcOa-- From owner-freebsd-stable@FreeBSD.ORG Wed Dec 3 22:53:46 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2E2F41065679 for ; Wed, 3 Dec 2008 22:53:46 +0000 (UTC) (envelope-from josh.carroll@gmail.com) Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.29]) by mx1.freebsd.org (Postfix) with ESMTP id C70F28FC1C for ; Wed, 3 Dec 2008 22:53:45 +0000 (UTC) (envelope-from josh.carroll@gmail.com) Received: by yx-out-2324.google.com with SMTP id 8so1598778yxb.13 for ; Wed, 03 Dec 2008 14:53:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=CKmFJiglEyYkVnUsBUrNi5JrrmvcjWprUKCwjrAMMq4=; b=sKzOGJ3zYns0AE75S+X6ZQsAkvaIYC0rgq6X96iz1fRBrtnsBSGHhMMnVl1QrC6eTD YI6uy0mVntkCG0jQtH8p8yQTwYBimuHEvH5mr3wmbWf++TH/w1Z7q1nQdgk+v3GVLGkY a14JG3U0ZOHw+CJdrrsQruI/w6Qeckn0plkFQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:cc:in-reply-to :mime-version:content-type:content-transfer-encoding :content-disposition:references; b=vWoqPd9IKRLO6hfksmxgTXFJ6nYrzUR4egmvmo/pxhZCGcd+g6k/lmv0+odT/XwzqV EVH7hRm/cyKsEYcmgZ3N+mtTcGWOzW8RYAGlT4bPcPkZ2LP5WyIw+wrXLrIn89G07dtu naxtVZ5C6f8Hjpex34K6BkNqi7OfPtA+B8Tdg= Received: by 10.151.142.2 with SMTP id u2mr26950388ybn.4.1228344823942; Wed, 03 Dec 2008 14:53:43 -0800 (PST) Received: by 10.150.123.1 with HTTP; Wed, 3 Dec 2008 14:53:43 -0800 (PST) Message-ID: <8cb6106e0812031453j6dc2f2f4i374145823c084eaa@mail.gmail.com> Date: Wed, 3 Dec 2008 17:53:43 -0500 From: "Josh Carroll" To: "Kostik Belousov" In-Reply-To: <20081125150342.GL2042@deviant.kiev.zoral.com.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <8cb6106e0811241129o642dcf28re4ae177c8ccbaa25@mail.gmail.com> <20081125140601.GH2042@deviant.kiev.zoral.com.ua> <8cb6106e0811250617q5fffb41exe20dfb8314fc4a9d@mail.gmail.com> <20081125142827.GI2042@deviant.kiev.zoral.com.ua> <8cb6106e0811250657q6fdf08b0x1e94f35fd0a7ed4f@mail.gmail.com> <20081125150342.GL2042@deviant.kiev.zoral.com.ua> Cc: freebsd-fs@freebsd.org, FreeBSD Stable Subject: Re: ext2 inode size patch - RE: PR kern/124621 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: josh.carroll@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Dec 2008 22:53:46 -0000 > Ok, I describe my concern once more. I do not object against the checking > of the inode size. But, if inode size is changed, then some data is added > to the inode, that could (and usually does, otherwise why extend it ?) > change intrerpetation of the inode. Thus, we need a verification of the > fact that simply ignoring added fields does not damage filesystem or > cause user data corruption. Verification != testing. Let me take another crack at explaining why I think this patch is not dangerous. The inode size is determined by reading the following member: __u16 s_inode_size; of the ext2_super_block structure. I took a look at the Linux 2.6.27.7 kernel source, and indeed they do something very similar if not the same: #define EXT2_INODE_SIZE(s) (EXT2_SB(s)->s_inode_size) If you compare to what I did: #define EXT2_INODE_SIZE(s) ((s)->u.ext2_sb.s_inode_size) This is really the same thing, since EXT2_SB is defined (in the Linux kernel src as): #ifdef __KERNEL__ #include static inline struct ext2_sb_info *EXT2_SB(struct super_block *sb) { return sb->s_fs_info; } And struct ext2_sb_info has the following member: int s_inode_size; Essentially, the changes I made simply query the existing information from the filesystem, which is what the Linux kernel does as well. The inode size, blocks per group, etc are all defined at filesystem creation time by mke2fs and it ensures the sanity of the relationship between the inodes/blocks/block groups. The first diagram here: http://sunsite.nus.sg/LDP/LDP/tlk/node95.html Makes it clear that as long as the number of inodes per block and the blocks per group is is sane during fs creation, looking up the inode size as my patch does is fine, since the creation of the filesystem is ensures a correct by construction situation. We're simply reading the size of the inode based on the filesystem. I hope this is sufficient to convince some further thought about committing this. For those interested in the relevant Linux kernel source, you can have a look at line 105 of include/linux/ext2_fs.h from the linux-2.6.27.7 kernel source. Thanks, Josh From owner-freebsd-stable@FreeBSD.ORG Wed Dec 3 22:55:45 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2CE92106564A for ; Wed, 3 Dec 2008 22:55:45 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.freebsd.org (Postfix) with ESMTP id DE3478FC1B for ; Wed, 3 Dec 2008 22:55:44 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (smmsp@localhost [127.0.0.1]) by dan.emsphone.com (8.14.3/8.14.3) with ESMTP id mB3MtipS090944 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 3 Dec 2008 16:55:44 -0600 (CST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.14.3/8.14.3/Submit) id mB3Mtgb6090929; Wed, 3 Dec 2008 16:55:42 -0600 (CST) (envelope-from dan) Date: Wed, 3 Dec 2008 16:55:42 -0600 From: Dan Nelson To: Vlad GALU Message-ID: <20081203225542.GG22076@dan.emsphone.com> References: <20081203152330.GD22076@dan.emsphone.com> <20081203170857.GE22076@dan.emsphone.com> <20081203185622.GF22076@dan.emsphone.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-OS: FreeBSD 7.1-PRERELEASE User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-stable@freebsd.org Subject: Re: Weird truss output 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: Wed, 03 Dec 2008 22:55:45 -0000 In the last episode (Dec 03), Vlad GALU said: > On Wed, Dec 3, 2008 at 8:56 PM, Dan Nelson wrote: > [...] > > Am I doing something wrong? I've applied the full diff, rebuilt > truss, now I get this: > -- cut here -- > root@goofy / # truss -p 52731 > SIGNAL 17 (SIGSTOP) > > -- UNKNOWN SYSCALL 1048535 -- > -- UNKNOWN SYSCALL 1048496 -- > -- UNKNOWN SYSCALL 1048559 -- > -- UNKNOWN SYSCALL 1048559 -- > -- UNKNOWN SYSCALL -8464 -- > -- UNKNOWN SYSCALL -8464 -- > -- UNKNOWN SYSCALL 527 -- > -- UNKNOWN SYSCALL 527 -- > /100084: read(1074283119,"\M-|\M^WP\^A",7356800) = 4 (0x4) > -- UNKNOWN SYSCALL 527 -- > -- UNKNOWN SYSCALL 7385248 -- > -- and here -- > > Perhaps I should mention that I block all signals from all threads, > except for one, where I do all the handling/cleanup. So you're back to your original behaviour basically? Not sure what's wrong; it all works great on my machine... Are you on a 64-bit system? I only have a Pentium-III here, so the big patch isn't guaranteed to work on anything except i386. The little patch inlined in my previous email is for i386-fbsd.c, but you should be able to make similar changes to amd64-fbsd.c (most of the diff just replaces "fsc." with "fsc->" ). -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 07:12:48 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 66B701065679 for ; Thu, 4 Dec 2008 07:12:48 +0000 (UTC) (envelope-from frode@nordahl.net) Received: from smtp3.powertech.no (smtp3.powertech.no [195.159.0.178]) by mx1.freebsd.org (Postfix) with ESMTP id EBC458FC1E for ; Thu, 4 Dec 2008 07:12:47 +0000 (UTC) (envelope-from frode@nordahl.net) Received: from dhcp1.xu.nordahl.net (dhcp1.xu.nordahl.net [195.159.148.120]) by smtp3.powertech.no (Postfix) with ESMTP id 6819BC59F3; Thu, 4 Dec 2008 08:12:46 +0100 (CET) Message-Id: <8A6A8FA5-07A6-4A12-B9AD-6E77E534CED7@nordahl.net> From: Frode Nordahl To: Kostik Belousov In-Reply-To: <20081203194348.GB2401@deviant.kiev.zoral.com.ua> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Date: Thu, 4 Dec 2008 08:12:45 +0100 References: <3B675385-956D-4A26-8E09-E338DF7D7244@nordahl.net> <20081203173939.GA2401@deviant.kiev.zoral.com.ua> <20081203194348.GB2401@deviant.kiev.zoral.com.ua> X-Mailer: Apple Mail (2.929.2) Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 7.1-PRERELEASE-p1, panic: dqget: free dquot isn't 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: Thu, 04 Dec 2008 07:12:48 -0000 On 3. des.. 2008, at 20.43, Kostik Belousov wrote: > On Wed, Dec 03, 2008 at 08:12:22PM +0100, Frode Nordahl wrote: >> (moved to freebsd-stable) >> >> On 3. des.. 2008, at 18.39, Kostik Belousov wrote: >> >>>> db> where >>>> Tracing pid 41111 tid 100199 td 0xffffff0056f1f370 >>>> kdb_enter_why() at kdb_enter_why+0x3d >>>> panic() at panic+0x17b >>>> dqget() at dqget+0xaa4 >>>> getinoquota() at getinoquota+0x5b >>>> ufs_access() at ufs_access+0x28c >>>> ufs_lookup() at ufs_lookup+0x9fe >>>> vfs_cache_lookup() at vfs_cache_lookup+0xf8 >>>> VOP_LOOKUP_APV() at VOP_LOOKUP_APV+0x40 >>>> lookup() at lookup+0x531 >>>> namei() at namei+0x35d >>>> kern_rmdir() at kern_rmdir+0xbd >>>> syscall() at syscall+0x256 >>>> Xfast_syscall() at Xfast_syscall+0xab >>> >>> For the start, I want to see the content of the *dq in the dqget() >>> frame. >> >> >> I am unable to get to *dq :-( >> >> (kgdb) frame 10 >> #10 0xffffffff806dbc54 in dqget (vp=0xffffff011e0767e0, id=419444, >> ump=0xffffff00038a9000, type=0, dqp=0xffffff0122e47268) >> at /usr/src/sys/ufs/ufs/ufs_quota.c:1210 >> 1210 panic("dqget: free dquot isn't"); > If this is repeatable, change panic to > panic("dqget: free dquot isn't %p", dq); > > and then in kgdb p/x *(struct dquot *) Got it! panic: dqget: free dquot isn't dq=0xffffff00b3d27000 (kgdb) p/x *(struct dquot *)0xffffff00b3d27000 $1 = {dq_hash = {le_next = 0x0, le_prev = 0xffffff010b9da700}, dq_freelist = { tqe_next = 0xffffff0055e2de00, tqe_prev = 0xffffffff80b03710}, dq_lock = { lock_object = {lo_name = 0xffffffff8088c21c, lo_type = 0xffffffff8088c21c, lo_flags = 0x1030000, lo_witness_data = {lod_list = {stqe_next = 0x0}, lod_witness = 0x0}}, mtx_lock = 0x4, mtx_recurse = 0x0}, dq_flags = 0xc, dq_type = 0x0, dq_cnt = 0x0, dq_id = 0x16a37d, dq_ump = 0xffffff00038e1600, dq_dqb = {dqb_bhardlimit = 0x0, dqb_bsoftlimit = 0x0, dqb_curblocks = 0x0, dqb_ihardlimit = 0x0, dqb_isoftlimit = 0x0, dqb_curinodes = 0x1, dqb_btime = 0x493ef2b5, dqb_itime = 0x493ef2b5}} Let me know if I can provide any more information! Updated the crashinfo archive you got an URL to yesterday if you want to poke around yourself. -- Frode Nordahl From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 07:31:04 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 96C661065676; Thu, 4 Dec 2008 07:31:04 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id 666D38FC13; Thu, 4 Dec 2008 07:31:04 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from compute2.internal (compute2.internal [10.202.2.42]) by out1.messagingengine.com (Postfix) with ESMTP id D38451CCF09; Thu, 4 Dec 2008 02:15:07 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute2.internal (MEProxy); Thu, 04 Dec 2008 02:15:07 -0500 X-Sasl-enc: EQDauYBCrxW/pU5OuZOqHdtKdL86qR9yYZfh2Ygwt3vM 1228374907 Received: from empiric.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTPSA id 1BD5F24DF8; Thu, 4 Dec 2008 02:15:07 -0500 (EST) Message-ID: <49378379.5050900@FreeBSD.org> Date: Thu, 04 Dec 2008 07:15:05 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 2.0.0.14 (X11/20080514) MIME-Version: 1.0 To: Kostik Belousov References: <8cb6106e0811241129o642dcf28re4ae177c8ccbaa25@mail.gmail.com> <20081125140601.GH2042@deviant.kiev.zoral.com.ua> <8cb6106e0811250617q5fffb41exe20dfb8314fc4a9d@mail.gmail.com> <20081125142827.GI2042@deviant.kiev.zoral.com.ua> <8cb6106e0811250657q6fdf08b0x1e94f35fd0a7ed4f@mail.gmail.com> <20081125150342.GL2042@deviant.kiev.zoral.com.ua> <8cb6106e0812031453j6dc2f2f4i374145823c084eaa@mail.gmail.com> In-Reply-To: <8cb6106e0812031453j6dc2f2f4i374145823c084eaa@mail.gmail.com> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: josh.carroll@gmail.com, freebsd-fs@freebsd.org, FreeBSD Stable Subject: Re: ext2 inode size patch - RE: PR kern/124621 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: Thu, 04 Dec 2008 07:31:04 -0000 Hi, The inode size for the ext3 filesystem which Gentoo created for my last install defaulted to 256 bytes, so I got bit by this problem. I can't speak for the write path. but the read path looks just fine to me, and the patch should go in ASAP. Josh Carroll wrote: >> Ok, I describe my concern once more. I do not object against the checking >> of the inode size. But, if inode size is changed, then some data is added >> to the inode, that could (and usually does, otherwise why extend it ?) >> change intrerpetation of the inode. Thus, we need a verification of the >> fact that simply ignoring added fields does not damage filesystem or >> cause user data corruption. Verification != testing. >> If folk are paranoid, then add a check for dynamic inode size and disable ext2fs writes by downgrading the mount in that case (We can do that, right? Can someone make sure Josh gets the help he needs here?) As Josh points out, the ext2 inode size is stored in the superblock. Whilst it may vary between ext2 filesystems, *the inode size itself does not appear to be something which one can modify in an existing ext2/3 filesystem*. Older ext2 filesystems may not contain the inode size field in the superblock, and the patch appears to default to 128 for that case. The double indirection thus introduced doesn't concern me, our ext2fs is not performance critical code, and the superblock is likely to sit in L2/L3 cache anyway (note: content free argument). Thanks to Josh for fixing this problem. cheers BMS From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 08:29:14 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EA01F1065676 for ; Thu, 4 Dec 2008 08:29:14 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.28]) by mx1.freebsd.org (Postfix) with ESMTP id AE5248FC20 for ; Thu, 4 Dec 2008 08:29:14 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: by yw-out-2324.google.com with SMTP id 9so1669425ywe.13 for ; Thu, 04 Dec 2008 00:29:13 -0800 (PST) Received: by 10.150.212.14 with SMTP id k14mr3910971ybg.148.1228379353681; Thu, 04 Dec 2008 00:29:13 -0800 (PST) Received: by 10.151.137.13 with HTTP; Thu, 4 Dec 2008 00:29:13 -0800 (PST) Message-ID: Date: Thu, 4 Dec 2008 10:29:13 +0200 From: "Vlad GALU" To: "Dan Nelson" In-Reply-To: <20081203225542.GG22076@dan.emsphone.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20081203152330.GD22076@dan.emsphone.com> <20081203170857.GE22076@dan.emsphone.com> <20081203185622.GF22076@dan.emsphone.com> <20081203225542.GG22076@dan.emsphone.com> Cc: freebsd-stable@freebsd.org Subject: Re: Weird truss output 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: Thu, 04 Dec 2008 08:29:15 -0000 On Thu, Dec 4, 2008 at 12:55 AM, Dan Nelson wrote: > In the last episode (Dec 03), Vlad GALU said: >> On Wed, Dec 3, 2008 at 8:56 PM, Dan Nelson wrote: >> [...] >> >> Am I doing something wrong? I've applied the full diff, rebuilt >> truss, now I get this: >> -- cut here -- >> root@goofy / # truss -p 52731 >> SIGNAL 17 (SIGSTOP) >> >> -- UNKNOWN SYSCALL 1048535 -- >> -- UNKNOWN SYSCALL 1048496 -- >> -- UNKNOWN SYSCALL 1048559 -- >> -- UNKNOWN SYSCALL 1048559 -- >> -- UNKNOWN SYSCALL -8464 -- >> -- UNKNOWN SYSCALL -8464 -- >> -- UNKNOWN SYSCALL 527 -- >> -- UNKNOWN SYSCALL 527 -- >> /100084: read(1074283119,"\M-|\M^WP\^A",7356800) = 4 (0x4) >> -- UNKNOWN SYSCALL 527 -- >> -- UNKNOWN SYSCALL 7385248 -- >> -- and here -- >> >> Perhaps I should mention that I block all signals from all threads, >> except for one, where I do all the handling/cleanup. > > So you're back to your original behaviour basically? Not sure what's > wrong; it all works great on my machine... Are you on a 64-bit system? > I only have a Pentium-III here, so the big patch isn't guaranteed to > work on anything except i386. The little patch inlined in my previous > email is for i386-fbsd.c, but you should be able to make similar > changes to amd64-fbsd.c (most of the diff just replaces "fsc." with > "fsc->" ). > Duh, I'm dumb, I didn't take a moment to check whether there was a 64-bit specific implementation. My initial thought was that the "i386" in the i386-fbsd.c referred to the CPU arch :) I'll try patching the other file today and get back with the results. And next time I'll make sure I've had my daily coffee before posting to the list :) > -- > Dan Nelson > dnelson@allantgroup.com > _______________________________________________ > 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" > -- ~/.signature: no such file or directory From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 09:09:06 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 246EB106564A for ; Thu, 4 Dec 2008 09:09:06 +0000 (UTC) (envelope-from mail25@bzerk.org) Received: from ei.bzerk.org (tunnel490.ipv6.xs4all.nl [IPv6:2001:888:10:1ea::2]) by mx1.freebsd.org (Postfix) with ESMTP id A1E898FC12 for ; Thu, 4 Dec 2008 09:09:05 +0000 (UTC) (envelope-from mail25@bzerk.org) Received: from ei.bzerk.org (BOFH@localhost [127.0.0.1]) by ei.bzerk.org (8.14.2/8.14.2) with ESMTP id mB4991hL016585; Thu, 4 Dec 2008 10:09:01 +0100 (CET) (envelope-from mail25@bzerk.org) Received: (from bulk@localhost) by ei.bzerk.org (8.14.2/8.14.2/Submit) id mB4990YK016584; Thu, 4 Dec 2008 10:09:00 +0100 (CET) (envelope-from mail25@bzerk.org) Date: Thu, 4 Dec 2008 10:08:59 +0100 From: Ruben de Groot To: Nathan Butcher Message-ID: <20081204090859.GA16512@ei.bzerk.org> Mail-Followup-To: Ruben de Groot , Nathan Butcher , freebsd-stable@freebsd.org References: <49362A3C.7060204@fusiongol.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49362A3C.7060204@fusiongol.com> User-Agent: Mutt/1.4.2.3i X-Spam-Status: No, score=-4.2 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, SUBJECT_FUZZY_TION autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on ei.bzerk.org X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (ei.bzerk.org [127.0.0.1]); Thu, 04 Dec 2008 10:09:04 +0100 (CET) Cc: freebsd-stable@freebsd.org Subject: Re: sysinstall automatic partition labelling/sizing problem 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: Thu, 04 Dec 2008 09:09:06 -0000 /boot/kernel is ~118 MB on my system (including debugging symbols). Default size of the root partition created by sysinstall is 512 MB, in your case downsized to 360 to accomodate other partitions on your 8GB disk. Should still be enough though. Do you have any other big files hanging around in your root partition? Ruben On Wed, Dec 03, 2008 at 03:42:04PM +0900, Nathan Butcher typed: > Automatic labelling on 7.0 created about 360MB for my root partition on > a 8GB disk. After a buildkernel into 7.1-PRERELEASE, the root partition > was exhausted during the installkernel. > > Maybe automatic labelling in sysinstall needs to allocate more than > 360MB in the root (/) partition if it's going to stay big enough to > accomodate a buildkernel and installkernel from source. > > _______________________________________________ > 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" From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 09:24:08 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 640281065675 for ; Thu, 4 Dec 2008 09:24:08 +0000 (UTC) (envelope-from peter@simons-rock.edu) Received: from hedwig.simons-rock.edu (hedwig.simons-rock.edu [208.81.88.14]) by mx1.freebsd.org (Postfix) with ESMTP id 23EE28FC0A for ; Thu, 4 Dec 2008 09:24:07 +0000 (UTC) (envelope-from peter@simons-rock.edu) Received: from cesium.hyperfine.info (c2.8d.5646.static.theplanet.com [70.86.141.194]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by hedwig.simons-rock.edu (Postfix) with ESMTP id E97EDED0DC; Thu, 4 Dec 2008 04:24:06 -0500 (EST) Date: Thu, 4 Dec 2008 04:20:24 -0500 From: "Peter C. Lai" To: Ruben de Groot , Nathan Butcher , freebsd-stable@freebsd.org Message-ID: <20081204092024.GW27780@cesium.hyperfine.info> References: <49362A3C.7060204@fusiongol.com> <1660_1228381770_49379E4A_1660_278_1_20081204090859.GA16512@ei.bzerk.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1660_1228381770_49379E4A_1660_278_1_20081204090859.GA16512@ei.bzerk.org> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: Subject: Re: sysinstall automatic partition labelling/sizing problem 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: Thu, 04 Dec 2008 09:24:08 -0000 Might be helpful to remember that /root is on /, so if you're in the habit of leaving stuff in /root for doing sysadmin tasks, it can kill / pretty quickly... On 2008-12-04 10:08:59AM +0100, Ruben de Groot wrote: > > /boot/kernel is ~118 MB on my system (including debugging symbols). > Default size of the root partition created by sysinstall is 512 MB, in your > case downsized to 360 to accomodate other partitions on your 8GB disk. > Should still be enough though. Do you have any other big files hanging > around in your root partition? > > Ruben > > On Wed, Dec 03, 2008 at 03:42:04PM +0900, Nathan Butcher typed: > > Automatic labelling on 7.0 created about 360MB for my root partition on > > a 8GB disk. After a buildkernel into 7.1-PRERELEASE, the root partition > > was exhausted during the installkernel. > > > > Maybe automatic labelling in sysinstall needs to allocate more than > > 360MB in the root (/) partition if it's going to stay big enough to > > accomodate a buildkernel and installkernel from source. > > > > _______________________________________________ > > 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" > _______________________________________________ > 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" -- =========================================================== Peter C. Lai | Bard College at Simon's Rock Systems Administrator | 84 Alford Rd. Information Technology Svcs. | Gt. Barrington, MA 01230 USA peter AT simons-rock.edu | (413) 528-7428 =========================================================== From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 09:48:57 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C1DA11065673 for ; Thu, 4 Dec 2008 09:48:57 +0000 (UTC) (envelope-from admin@kkip.pl) Received: from mainframe.kkip.pl (kkip.pl [87.105.164.78]) by mx1.freebsd.org (Postfix) with ESMTP id 728E88FC19 for ; Thu, 4 Dec 2008 09:48:57 +0000 (UTC) (envelope-from admin@kkip.pl) Received: from admin.admin.lan.kkip.pl ([10.66.3.254]) by mainframe.kkip.pl with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1L8ApJ-000NQP-EX for freebsd-stable@freebsd.org; Thu, 04 Dec 2008 10:48:56 +0100 Message-ID: <4937A786.9080403@kkip.pl> Date: Thu, 04 Dec 2008 10:48:54 +0100 From: Bartosz Stec User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: FreeBSD Stable Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated-User: admin@kkip.pl X-Authenticator: plain X-Sender-Verify: SUCCEEDED (sender exists & accepts mail) X-Spam-Score: -8.9 X-Spam-Score-Int: -88 X-Exim-Version: 4.69 (build at 01-Nov-2008 10:39:57) X-Date: 2008-12-04 10:48:56 X-Connected-IP: 10.66.3.254:1543 X-Message-Linecount: 28 X-Body-Linecount: 17 X-Message-Size: 1080 X-Body-Size: 650 X-Received-Count: 1 X-Recipient-Count: 1 X-Local-Recipient-Count: 1 X-Local-Recipient-Defer-Count: 0 X-Local-Recipient-Fail-Count: 0 Subject: Burning DVD with files>4GB from console 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: Thu, 04 Dec 2008 09:48:57 -0000 My backup script split filesystem dumps to files with size of 4,37 GB (4 588 544 kB). It's just an optimal size to fill out DVDs. At this moment I have to burn them from windows via smb-link becuase I didn't manage to do this task from FreeBSD console due to 2GB/4GB filesize restrictions (growisofs). I'm using freeware CDBurnerXP to burn my backups (ISO9660/UDF/Joliet), and they mount without problems on my FreeBSD BOX, files are fully readable too. However, burning gigabytes of data via slow (about 3.5MB/s) SMB network is just annoing. Is there *any* way to burn DVDs with files>4GB from FreeBSD console? cheers! -- Bartosz Stec From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 10:31:53 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5EF8E1065675 for ; Thu, 4 Dec 2008 10:31:53 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 764EF8FC24 for ; Thu, 4 Dec 2008 10:31:51 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id MAA16335 for ; Thu, 04 Dec 2008 12:31:49 +0200 (EET) (envelope-from avg@icyb.net.ua) Message-ID: <4937B194.1020606@icyb.net.ua> Date: Thu, 04 Dec 2008 12:31:48 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.18 (X11/20081124) MIME-Version: 1.0 To: FreeBSD Stable Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: rc.firewall: default loopback rules are set up even for custom file 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: Thu, 04 Dec 2008 10:31:53 -0000 I've just realized that I see in releng/7 something that I did not see in releng/6 - even if I use a file with custom rules in firewall_type I still get default loopback rules installed. I think that this is not correct, I am using custom rules exactly because I want to control *everything* (e.g. all deny rules come with log logamount xxx). -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 10:50:30 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2197C106567C for ; Thu, 4 Dec 2008 10:50:30 +0000 (UTC) (envelope-from gandalf@shopzeus.com) Received: from viefep28-int.chello.at (viefep28-int.chello.at [62.179.121.48]) by mx1.freebsd.org (Postfix) with ESMTP id 68DC18FC22 for ; Thu, 4 Dec 2008 10:50:29 +0000 (UTC) (envelope-from gandalf@shopzeus.com) Received: from edge01.upc.biz ([192.168.13.236]) by viefep17-int.chello.at (InterMail vM.7.09.01.00 201-2219-108-20080618) with ESMTP id <20081204103441.GVYT17413.viefep17-int.chello.at@edge01.upc.biz> for ; Thu, 4 Dec 2008 11:34:41 +0100 Received: from [192.168.1.104] ([89.134.230.11]) by edge01.upc.biz with edge id myaa1a03c0FQLHV01yab43; Thu, 04 Dec 2008 11:34:41 +0100 X-SourceIP: 89.134.230.11 Message-ID: <4937B23A.5060507@shopzeus.com> Date: Thu, 04 Dec 2008 11:34:34 +0100 From: Laszlo Nagy User-Agent: Thunderbird 2.0.0.17 (X11/20080925) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Kernel panic, Trap 12, page fault while in kernel mode and freeing free frag on 7.0 p5 amd64 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: Thu, 04 Dec 2008 10:50:30 -0000 We have a production server which keeps crashing. Hardware: two Quad Core Xeons (5420), 8GB ECC ram, Intel S5000 motherboard, Areca 1680-ix12 RAID card. The memory have been replaced three times. Memtest runs OK. The motherboard was replaced, all firmwares updated to the latest version (last time an Intel engineer did this for us.) Machine is running postgresql, postfix, apache, mod_php, dovecot. Kernel was compiled with debug symbols. Machine configuration can be found here: http://195.228.74.135/info Core dumps are here (not all of them): http://195.228.74.135/crash In most cases, the error message is "page fault" but there is also a "freeing free frag". When there is no big load (weekends) then it runs for two or three days. It crashes only when there is bigger load on the server. On very busy days, it can crash three times a day. I have installed exactly the same software on a desktop computer with amd X2 BE2350 processor and 3GB non-ecc RAM, and it ran for 6 days without crashing. (Unfortunately, I cannot use that computer in production because it is incredibly slow...) I have found some other posts about a similar problem, but that issue was closed. Unfortunately, I'm not familiar with kernel debugging. Is this the right place to ask for help? Thanks, Laszlo From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 10:51:34 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 503BA1065678; Thu, 4 Dec 2008 10:51:34 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.terabit.net.ua (mail.terabit.net.ua [195.137.202.147]) by mx1.freebsd.org (Postfix) with ESMTP id E062B8FC16; Thu, 4 Dec 2008 10:51:33 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from skuns.zoral.com.ua ([91.193.166.194] helo=mail.zoral.com.ua) by mail.terabit.net.ua with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1L8Bnw-0005Kj-NG; Thu, 04 Dec 2008 12:51:32 +0200 Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id mB4ApTZa061830 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 4 Dec 2008 12:51:30 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id mB4ApTum025259; Thu, 4 Dec 2008 12:51:29 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id mB4ApTom025258; Thu, 4 Dec 2008 12:51:29 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 4 Dec 2008 12:51:29 +0200 From: Kostik Belousov To: "Bruce M. Simpson" Message-ID: <20081204105129.GA2246@deviant.kiev.zoral.com.ua> References: <8cb6106e0811241129o642dcf28re4ae177c8ccbaa25@mail.gmail.com> <20081125140601.GH2042@deviant.kiev.zoral.com.ua> <8cb6106e0811250617q5fffb41exe20dfb8314fc4a9d@mail.gmail.com> <20081125142827.GI2042@deviant.kiev.zoral.com.ua> <8cb6106e0811250657q6fdf08b0x1e94f35fd0a7ed4f@mail.gmail.com> <20081125150342.GL2042@deviant.kiev.zoral.com.ua> <8cb6106e0812031453j6dc2f2f4i374145823c084eaa@mail.gmail.com> <49378379.5050900@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="17pEHd4RhPHOinZp" Content-Disposition: inline In-Reply-To: <49378379.5050900@FreeBSD.org> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: ClamAV version 0.93.3, clamav-milter version 0.93.3 on skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua X-Virus-Scanned: mail.terabit.net.ua 1L8Bnw-0005Kj-NG 247ecf99707698ec13432c25c35defde X-Terabit: YES Cc: josh.carroll@gmail.com, freebsd-fs@freebsd.org, FreeBSD Stable Subject: Re: ext2 inode size patch - RE: PR kern/124621 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: Thu, 04 Dec 2008 10:51:34 -0000 --17pEHd4RhPHOinZp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Dec 04, 2008 at 07:15:05AM +0000, Bruce M. Simpson wrote: > Hi, >=20 > The inode size for the ext3 filesystem which Gentoo created for my last= =20 > install defaulted to 256 bytes, so I got bit by this problem. >=20 > I can't speak for the write path. but the read path looks just fine to=20 > me, and the patch should go in ASAP. >=20 > Josh Carroll wrote: > >>Ok, I describe my concern once more. I do not object against the checki= ng > >>of the inode size. But, if inode size is changed, then some data is add= ed > >>to the inode, that could (and usually does, otherwise why extend it ?) > >>change intrerpetation of the inode. Thus, we need a verification of the > >>fact that simply ignoring added fields does not damage filesystem or > >>cause user data corruption. Verification !=3D testing. > >> =20 >=20 > If folk are paranoid, then add a check for dynamic inode size and=20 > disable ext2fs writes by downgrading the mount in that case (We can do=20 > that, right? Can someone make sure Josh gets the help he needs here?) >=20 > As Josh points out, the ext2 inode size is stored in the superblock.=20 > Whilst it may vary between ext2 filesystems, *the inode size itself does= =20 > not appear to be something which one can modify in an existing ext2/3=20 > filesystem*. >=20 > Older ext2 filesystems may not contain the inode size field in the=20 > superblock, and the patch appears to default to 128 for that case. The=20 > double indirection thus introduced doesn't concern me, our ext2fs is not= =20 > performance critical code, and the superblock is likely to sit in L2/L3= =20 > cache anyway (note: content free argument). >=20 > Thanks to Josh for fixing this problem. Bruce, feel free to commit the patch. I do not want to spend time on ext2 in any form, and due to our (only partly jokingly) rule of the "last committer is the owner", I do not want to analyze ext2 bug reports after. --17pEHd4RhPHOinZp Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkk3tjEACgkQC3+MBN1Mb4gsMACfdZOmzO3B2qwkehgi1lWJWB+s anMAoNKxfWj1QQ6gOIYnXXIRE6bPZeWs =8ohK -----END PGP SIGNATURE----- --17pEHd4RhPHOinZp-- From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 12:07:42 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8637B1065673 for ; Thu, 4 Dec 2008 12:07:42 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.terabit.net.ua (mail.terabit.net.ua [195.137.202.147]) by mx1.freebsd.org (Postfix) with ESMTP id 160658FC21 for ; Thu, 4 Dec 2008 12:07:41 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from skuns.zoral.com.ua ([91.193.166.194] helo=mail.zoral.com.ua) by mail.terabit.net.ua with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1L8Czc-000Dcx-K0; Thu, 04 Dec 2008 14:07:40 +0200 Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id mB4C7a3x067207 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 4 Dec 2008 14:07:37 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id mB4C7aZC019291; Thu, 4 Dec 2008 14:07:36 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id mB4C7ahK019281; Thu, 4 Dec 2008 14:07:36 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 4 Dec 2008 14:07:36 +0200 From: Kostik Belousov To: Frode Nordahl Message-ID: <20081204120736.GC2038@deviant.kiev.zoral.com.ua> References: <3B675385-956D-4A26-8E09-E338DF7D7244@nordahl.net> <20081203173939.GA2401@deviant.kiev.zoral.com.ua> <20081203194348.GB2401@deviant.kiev.zoral.com.ua> <8A6A8FA5-07A6-4A12-B9AD-6E77E534CED7@nordahl.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="qtZFehHsKgwS5rPz" Content-Disposition: inline In-Reply-To: <8A6A8FA5-07A6-4A12-B9AD-6E77E534CED7@nordahl.net> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: ClamAV version 0.93.3, clamav-milter version 0.93.3 on skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua X-Virus-Scanned: mail.terabit.net.ua 1L8Czc-000Dcx-K0 2ffa936a1f695a30d25c4546a77f36a4 X-Terabit: YES Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 7.1-PRERELEASE-p1, panic: dqget: free dquot isn't 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: Thu, 04 Dec 2008 12:07:42 -0000 --qtZFehHsKgwS5rPz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Dec 04, 2008 at 08:12:45AM +0100, Frode Nordahl wrote: > On 3. des.. 2008, at 20.43, Kostik Belousov wrote: >=20 > >On Wed, Dec 03, 2008 at 08:12:22PM +0100, Frode Nordahl wrote: > >>(moved to freebsd-stable) > >> > >>On 3. des.. 2008, at 18.39, Kostik Belousov wrote: > >> > >>>>db> where > >>>>Tracing pid 41111 tid 100199 td 0xffffff0056f1f370 > >>>>kdb_enter_why() at kdb_enter_why+0x3d > >>>>panic() at panic+0x17b > >>>>dqget() at dqget+0xaa4 > >>>>getinoquota() at getinoquota+0x5b > >>>>ufs_access() at ufs_access+0x28c > >>>>ufs_lookup() at ufs_lookup+0x9fe > >>>>vfs_cache_lookup() at vfs_cache_lookup+0xf8 > >>>>VOP_LOOKUP_APV() at VOP_LOOKUP_APV+0x40 > >>>>lookup() at lookup+0x531 > >>>>namei() at namei+0x35d > >>>>kern_rmdir() at kern_rmdir+0xbd > >>>>syscall() at syscall+0x256 > >>>>Xfast_syscall() at Xfast_syscall+0xab > >>> > >>>For the start, I want to see the content of the *dq in the dqget() > >>>frame. > >> > >> > >>I am unable to get to *dq :-( > >> > >>(kgdb) frame 10 > >>#10 0xffffffff806dbc54 in dqget (vp=3D0xffffff011e0767e0, id=3D419444, > >> ump=3D0xffffff00038a9000, type=3D0, dqp=3D0xffffff0122e47268) > >> at /usr/src/sys/ufs/ufs/ufs_quota.c:1210 > >>1210 panic("dqget: free dquot isn't"); > >If this is repeatable, change panic to > > panic("dqget: free dquot isn't %p", dq); > > > >and then in kgdb p/x *(struct dquot *) >=20 > Got it! >=20 > panic: dqget: free dquot isn't dq=3D0xffffff00b3d27000 > (kgdb) p/x *(struct dquot *)0xffffff00b3d27000 > $1 =3D {dq_hash =3D {le_next =3D 0x0, le_prev =3D 0xffffff010b9da700}, = =20 > dq_freelist =3D { > tqe_next =3D 0xffffff0055e2de00, tqe_prev =3D 0xffffffff80b03710}, = =20 > dq_lock =3D { > lock_object =3D {lo_name =3D 0xffffffff8088c21c, lo_type =3D =20 > 0xffffffff8088c21c, > lo_flags =3D 0x1030000, lo_witness_data =3D {lod_list =3D {stqe_nex= t =20 > =3D 0x0}, > lod_witness =3D 0x0}}, mtx_lock =3D 0x4, mtx_recurse =3D 0x0}, > dq_flags =3D 0xc, dq_type =3D 0x0, dq_cnt =3D 0x0, dq_id =3D 0x16a37d, > dq_ump =3D 0xffffff00038e1600, dq_dqb =3D {dqb_bhardlimit =3D 0x0, > dqb_bsoftlimit =3D 0x0, dqb_curblocks =3D 0x0, dqb_ihardlimit =3D 0x0, > dqb_isoftlimit =3D 0x0, dqb_curinodes =3D 0x1, dqb_btime =3D 0x493ef2= b5, > dqb_itime =3D 0x493ef2b5}} >=20 > Let me know if I can provide any more information! >=20 > Updated the crashinfo archive you got an URL to yesterday if you want =20 > to poke around yourself. Please, try the patch below, it should fix a race I see. Quite possible, this is what you tripped over. On the other hand, dq_id =3D=3D 1483645 looks very suspicious. Do you actually have such large uid in the system ? Could it be that you have file on fs owned by such uid ? diff --git a/sys/ufs/ufs/ufs_quota.c b/sys/ufs/ufs/ufs_quota.c index e5cb956..0c8209a 100644 --- a/sys/ufs/ufs/ufs_quota.c +++ b/sys/ufs/ufs/ufs_quota.c @@ -1262,7 +1262,7 @@ dqrele(struct vnode *vp, struct dquot *dq) return; } DQH_UNLOCK(); - +sync: (void) dqsync(vp, dq); =20 DQH_LOCK(); @@ -1271,6 +1271,18 @@ dqrele(struct vnode *vp, struct dquot *dq) DQH_UNLOCK(); return; } + + /* + * The dq may become dirty after it is synced but before it is + * put to the free list. Checking the DQ_MOD there without + * locking dq should be safe since no other references to the + * dq exist. + */ + if ((dq->dq_flags & DQ_MOD) !=3D 0) { + dq->dq_cnt++; + DQH_UNLOCK(); + goto sync; + } TAILQ_INSERT_TAIL(&dqfreelist, dq, dq_freelist); DQH_UNLOCK(); } --qtZFehHsKgwS5rPz Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkk3yAgACgkQC3+MBN1Mb4jZ+ACgq+QZ3rjGVNNqFCXYuAsE4lt7 LpYAoPYyQl+nCrKWLd0myqKa97NXddG5 =foB/ -----END PGP SIGNATURE----- --qtZFehHsKgwS5rPz-- From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 12:20:38 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5714D106564A for ; Thu, 4 Dec 2008 12:20:38 +0000 (UTC) (envelope-from frode@nordahl.net) Received: from smtp3.powertech.no (smtp3.powertech.no [195.159.0.178]) by mx1.freebsd.org (Postfix) with ESMTP id 148BD8FC1E for ; Thu, 4 Dec 2008 12:20:38 +0000 (UTC) (envelope-from frode@nordahl.net) Received: from ws24.ns5.powertech.no (ws24.ns5.powertech.no [195.159.6.24]) by smtp3.powertech.no (Postfix) with ESMTP id C7371C6082; Thu, 4 Dec 2008 13:20:36 +0100 (CET) Message-Id: <576BB990-78D8-4CE8-9660-55EB989EE3BA@nordahl.net> From: Frode Nordahl To: Kostik Belousov In-Reply-To: <20081204120736.GC2038@deviant.kiev.zoral.com.ua> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Date: Thu, 4 Dec 2008 13:20:19 +0100 References: <3B675385-956D-4A26-8E09-E338DF7D7244@nordahl.net> <20081203173939.GA2401@deviant.kiev.zoral.com.ua> <20081203194348.GB2401@deviant.kiev.zoral.com.ua> <8A6A8FA5-07A6-4A12-B9AD-6E77E534CED7@nordahl.net> <20081204120736.GC2038@deviant.kiev.zoral.com.ua> X-Mailer: Apple Mail (2.929.2) Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 7.1-PRERELEASE-p1, panic: dqget: free dquot isn't 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: Thu, 04 Dec 2008 12:20:38 -0000 On 4. des.. 2008, at 13.07, Kostik Belousov wrote: > On Thu, Dec 04, 2008 at 08:12:45AM +0100, Frode Nordahl wrote: >> Got it! >> >> panic: dqget: free dquot isn't dq=0xffffff00b3d27000 >> (kgdb) p/x *(struct dquot *)0xffffff00b3d27000 >> $1 = {dq_hash = {le_next = 0x0, le_prev = 0xffffff010b9da700}, >> dq_freelist = { >> tqe_next = 0xffffff0055e2de00, tqe_prev = 0xffffffff80b03710}, >> dq_lock = { >> lock_object = {lo_name = 0xffffffff8088c21c, lo_type = >> 0xffffffff8088c21c, >> lo_flags = 0x1030000, lo_witness_data = {lod_list = {stqe_next >> = 0x0}, >> lod_witness = 0x0}}, mtx_lock = 0x4, mtx_recurse = 0x0}, >> dq_flags = 0xc, dq_type = 0x0, dq_cnt = 0x0, dq_id = 0x16a37d, >> dq_ump = 0xffffff00038e1600, dq_dqb = {dqb_bhardlimit = 0x0, >> dqb_bsoftlimit = 0x0, dqb_curblocks = 0x0, dqb_ihardlimit = 0x0, >> dqb_isoftlimit = 0x0, dqb_curinodes = 0x1, dqb_btime = 0x493ef2b5, >> dqb_itime = 0x493ef2b5}} >> >> Let me know if I can provide any more information! >> >> Updated the crashinfo archive you got an URL to yesterday if you want >> to poke around yourself. > > Please, try the patch below, it should fix a race I see. Quite > possible, > this is what you tripped over. Thanks! I will apply the patch and retry the steps that lead to the panic! > On the other hand, dq_id == 1483645 looks very suspicious. Do you > actually have such large uid in the system ? Could it be that you have > file on fs owned by such uid ? Yes. The system has uids ranging from 0 to 3152039 :-) -- Frode Nordahl From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 12:36:25 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 46D671065673 for ; Thu, 4 Dec 2008 12:36:25 +0000 (UTC) (envelope-from "cyb."@gmx.net) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id A3C268FC14 for ; Thu, 4 Dec 2008 12:36:24 +0000 (UTC) (envelope-from "cyb."@gmx.net) Received: (qmail invoked by alias); 04 Dec 2008 12:09:43 -0000 Received: from pD952E449.dip0.t-ipconnect.de (EHLO core2duo.local) [217.82.228.73] by mail.gmx.net (mp060) with SMTP; 04 Dec 2008 13:09:43 +0100 X-Authenticated: #4870692 X-Provags-ID: V01U2FsdGVkX1+jMDc0UhOjzDIyEitqivOi1o81hNYEt+Ty8zmYpj BSlcDAEL6UINwU Date: Thu, 4 Dec 2008 13:09:40 +0100 From: Andreas Rudisch To: Bartosz Stec Message-Id: <20081204130940.b8a4acf8.cyb.@gmx.net> In-Reply-To: <4937A786.9080403@kkip.pl> References: <4937A786.9080403@kkip.pl> X-Mailer: Sylpheed 2.5.0 (GTK+ 2.12.11; i386-portbld-freebsd6.3) Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="PGP-SHA1"; boundary="Signature=_Thu__4_Dec_2008_13_09_40_+0100_bN3+B3RbcdfSsKhK" X-Y-GMX-Trusted: 0 X-FuHaFi: 0.6 Cc: FreeBSD Stable Subject: Re: Burning DVD with files>4GB from console 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: Thu, 04 Dec 2008 12:36:25 -0000 --Signature=_Thu__4_Dec_2008_13_09_40_+0100_bN3+B3RbcdfSsKhK Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, 04 Dec 2008 10:48:54 +0100 Bartosz Stec wrote: > My backup script split filesystem dumps to files with size of 4,37 GB (4= =20 > 588 544 kB). It's just an optimal size to fill out DVDs. At this moment=20 > I have to burn them from windows via smb-link becuase I didn't manage to= =20 > do this task from FreeBSD console due to 2GB/4GB filesize restrictions=20 > (growisofs). I'm using freeware CDBurnerXP to burn my backups=20 > (ISO9660/UDF/Joliet), and they mount without problems on my FreeBSD BOX,= =20 > files are fully readable too. However, burning gigabytes of data via=20 > slow (about 3.5MB/s) SMB network is just annoing. Is there *any* way to=20 > burn DVDs with files>4GB from FreeBSD console? As a work around you could simply tell your backup script to spilt the data= at about 1GB and burn 4 files to one DVD. Andreas -- GnuPG key : 0x2A573565 | http://www.gnupg.org/howtos/de/ Fingerprint: 925D 2089 0BF9 8DE5 9166 33BB F0FD CD37 2A57 3565 --Signature=_Thu__4_Dec_2008_13_09_40_+0100_bN3+B3RbcdfSsKhK Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkk3yIYACgkQ8P3NNypXNWW/VQCfTA18etgTirCQBRTxaLrJytnI hAMAn21j1/R4Fc0izHbX53OCCqLTuwp+ =fl5z -----END PGP SIGNATURE----- --Signature=_Thu__4_Dec_2008_13_09_40_+0100_bN3+B3RbcdfSsKhK-- From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 12:52:01 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A3DA3106567A for ; Thu, 4 Dec 2008 12:52:01 +0000 (UTC) (envelope-from admin@kkip.pl) Received: from mainframe.kkip.pl (kkip.pl [87.105.164.78]) by mx1.freebsd.org (Postfix) with ESMTP id 540428FC13 for ; Thu, 4 Dec 2008 12:52:01 +0000 (UTC) (envelope-from admin@kkip.pl) Received: from admin.admin.lan.kkip.pl ([10.66.3.254]) by mainframe.kkip.pl with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1L8DgT-000OOl-15; Thu, 04 Dec 2008 13:51:59 +0100 Message-ID: <4937D26D.60408@kkip.pl> Date: Thu, 04 Dec 2008 13:51:57 +0100 From: Bartosz Stec User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: Philipp Ost References: <4937A786.9080403@kkip.pl> <4937CBBC.1020406@smo.de> In-Reply-To: <4937CBBC.1020406@smo.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated-User: admin@kkip.pl X-Authenticator: plain X-Sender-Verify: SUCCEEDED (sender exists & accepts mail) X-Spam-Score: -8.9 X-Spam-Score-Int: -88 X-Exim-Version: 4.69 (build at 01-Nov-2008 10:39:57) X-Date: 2008-12-04 13:51:59 X-Connected-IP: 10.66.3.254:3524 X-Message-Linecount: 40 X-Body-Linecount: 26 X-Message-Size: 1169 X-Body-Size: 605 X-Received-Count: 1 X-Recipient-Count: 2 X-Local-Recipient-Count: 2 X-Local-Recipient-Defer-Count: 0 X-Local-Recipient-Fail-Count: 0 Cc: FreeBSD Stable Subject: Re: Burning DVD with files>4GB from console 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: Thu, 04 Dec 2008 12:52:01 -0000 Philipp Ost pisze: > Hi, > > Bartosz Stec wrote: >> [...] Is there *any* way to burn DVDs with files>4GB from FreeBSD >> console? > > I succesfully used growisofs for exactly this task ;-) > > What I did is (for DL-DVDs): > # growisofs -dvd-compat -Z /dev/cd0=$file.iso -speed=2 > > I had to limit the speed, else it wouldn't do anything. If I burn > "normal" DVDs I don't need the speed limit. > > HTH, > Philipp But doesn't that command expecting file.iso being already premastered ISO image? OK, that's *some* way, but to be clear - I want to avoid preparing ISO images too ;) -- Bartosz Stec From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 13:16:19 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4F560106564A; Thu, 4 Dec 2008 13:16:19 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id 1ED1F8FC19; Thu, 4 Dec 2008 13:16:19 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 820781CD17B; Thu, 4 Dec 2008 08:16:18 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Thu, 04 Dec 2008 08:16:18 -0500 X-Sasl-enc: rXF7KLAAqFGOMAFJIgwgyXV29LtEJzB+W0cOm9z9lnAU 1228396578 Received: from empiric.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTPSA id AEA733A2C1; Thu, 4 Dec 2008 08:16:17 -0500 (EST) Message-ID: <4937D820.8080803@FreeBSD.org> Date: Thu, 04 Dec 2008 13:16:16 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 2.0.0.14 (X11/20080514) MIME-Version: 1.0 To: Kostik Belousov References: <8cb6106e0811241129o642dcf28re4ae177c8ccbaa25@mail.gmail.com> <20081125140601.GH2042@deviant.kiev.zoral.com.ua> <8cb6106e0811250617q5fffb41exe20dfb8314fc4a9d@mail.gmail.com> <20081125142827.GI2042@deviant.kiev.zoral.com.ua> <8cb6106e0811250657q6fdf08b0x1e94f35fd0a7ed4f@mail.gmail.com> <20081125150342.GL2042@deviant.kiev.zoral.com.ua> <8cb6106e0812031453j6dc2f2f4i374145823c084eaa@mail.gmail.com> <49378379.5050900@FreeBSD.org> <20081204105129.GA2246@deviant.kiev.zoral.com.ua> In-Reply-To: <20081204105129.GA2246@deviant.kiev.zoral.com.ua> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: josh.carroll@gmail.com, freebsd-fs@freebsd.org, FreeBSD Stable Subject: Re: ext2 inode size patch - RE: PR kern/124621 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: Thu, 04 Dec 2008 13:16:19 -0000 Kostik Belousov wrote: > ... > Bruce, feel free to commit the patch. > > I do not want to spend time on ext2 in any form, and due to our (only > partly jokingly) rule of the "last committer is the owner", I do not > want to analyze ext2 bug reports after. > Yes, development resource is limited here too, and any involvement on my part here DOES NOT constitute any commitment, express or implied, to maintaining the ext2fs module beyond the change being considered right now. I find that this often has to be reiterated as people are prone to confusing the concepts "open source" and "free", basic economics dictates infinite demand for free goods, and we've all got lives to live. As per our off-list discussion: It's a damned if we do and damned if we don't situation. Take the patch and it eats someone's lunch, and our reptuation suffers. Don't take the patch and look like patriarchal killjoys, and our reputation siffers. Your specific objection is that the testing is insufficient to exercise the patch, and there could be an area of ext2 which this patch doesn't address. That can never be said with 100% certainty, but I agree with you. Content free argument: Based on my reading of the code, the patch must be considered experimental. Whilst the scope of the patch appears to be small, the symbol space of ext2 is bigger -- a case of feeping creaturism due to ext2 itself, but hey, that's evolution for you. If folk are happy with it going in, let it go in, but remember, you get the system you apply effort to. I myself consider the patch experimental -- but HEAD is an experiment, is it not? Reality is what you can get away with. cheers BMS From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 13:40:54 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0E0791065677 for ; Thu, 4 Dec 2008 13:40:54 +0000 (UTC) (envelope-from pj@smo.de) Received: from ilk.de (mx-out14.ilk.de [194.121.104.14]) by mx1.freebsd.org (Postfix) with ESMTP id 58ED68FC08 for ; Thu, 4 Dec 2008 13:40:52 +0000 (UTC) (envelope-from pj@smo.de) Received: from bologna.intern.smo.de (pool56.ka.ilk.net [212.86.194.56]) by ilk.de (8.13.4/8.13.4/ilk-relay) with ESMTP id mB4CNYRQ021490; Thu, 4 Dec 2008 13:23:34 +0100 Received: from [192.168.153.208] (herdubreid.intern.smo.de [192.168.153.208]) by bologna.intern.smo.de (8.13.8+Sun/8.13.8) with ESMTP id mB4CFbmH012100; Thu, 4 Dec 2008 13:15:41 +0100 (CET) Message-ID: <4937CBBC.1020406@smo.de> Date: Thu, 04 Dec 2008 13:23:24 +0100 From: Philipp Ost User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.13) Gecko/20080701 X-Accept-Language: de, en-us, en MIME-Version: 1.0 To: Bartosz Stec References: <4937A786.9080403@kkip.pl> In-Reply-To: <4937A786.9080403@kkip.pl> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Stable Subject: Re: Burning DVD with files>4GB from console 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: Thu, 04 Dec 2008 13:40:54 -0000 Hi, Bartosz Stec wrote: > [...] Is there *any* way to > burn DVDs with files>4GB from FreeBSD console? I succesfully used growisofs for exactly this task ;-) What I did is (for DL-DVDs): # growisofs -dvd-compat -Z /dev/cd0=$file.iso -speed=2 I had to limit the speed, else it wouldn't do anything. If I burn "normal" DVDs I don't need the speed limit. HTH, Philipp From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 15:24:12 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 026F010656B5 for ; Thu, 4 Dec 2008 15:24:12 +0000 (UTC) (envelope-from samflanker@gmail.com) Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.26]) by mx1.freebsd.org (Postfix) with ESMTP id 870488FC0A for ; Thu, 4 Dec 2008 15:24:11 +0000 (UTC) (envelope-from samflanker@gmail.com) Received: by ey-out-2122.google.com with SMTP id 6so1725877eyi.7 for ; Thu, 04 Dec 2008 07:24:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:content-type :content-transfer-encoding; bh=rd4hmRDQnwH41dhDuSjk20ex0Z8rnDABCY2urs2WmA8=; b=JSCbN8oFkXbXDeJVGBSw/TKLOY/6FPdY1OmvjBGHsyq/PuALbwD4ND04VuhHvU/jjk WZZM9Lmy8YOhd19MdpteUeX6+mkcabuUYy2kaxWigC3uL6eGb7FPkd3NYp7yddVHlade u98hMpCUo/SDGNl4xahatswRjrZafBLALL1X8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :content-type:content-transfer-encoding; b=e8mvnGIMcudW5KB0cxi472hnNLmgSafpA3c0TVzUYMEcRwpQm2RYFMvfbeBocwpPiH AjluokwumHR7WUQuTFP3K9Ffz/OxEvABYd4f6oyNQ/ROcXbQMZyYcw7sbFMZu3plMZNY +CSXiYUT4T7SAKYDmLtgfRoqb0YtJsBA5CwRg= Received: by 10.210.86.10 with SMTP id j10mr16571067ebb.181.1228404250186; Thu, 04 Dec 2008 07:24:10 -0800 (PST) Received: from localhost.localdomain ([213.152.137.42]) by mx.google.com with ESMTPS id 7sm6295568eyg.42.2008.12.04.07.24.06 (version=SSLv3 cipher=RC4-MD5); Thu, 04 Dec 2008 07:24:07 -0800 (PST) Message-ID: <4937F627.8080602@gmail.com> Date: Thu, 04 Dec 2008 18:24:23 +0300 From: Vladimir Ermakov User-Agent: Thunderbird 2.0.0.18 (X11/20081119) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-pf@freebsd.org Subject: Re: synproxy state does not work on FreeBSD 7.1-PRERELEASE 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: Thu, 04 Dec 2008 15:24:12 -0000 problem is fixed in OpenBSD 4.4 http://www.openbsd.org/plus44.html /Vladimir Ermakov From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 15:47:16 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4615010656D4 for ; Thu, 4 Dec 2008 15:47:16 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.9]) by mx1.freebsd.org (Postfix) with ESMTP id CBD798FC2C for ; Thu, 4 Dec 2008 15:47:15 +0000 (UTC) (envelope-from max@love2party.net) Received: from vampire.homelinux.org (dslb-088-066-028-001.pools.arcor-ip.net [88.66.28.1]) by mrelayeu.kundenserver.de (node=mrelayeu1) with ESMTP (Nemesis) id 0MKwpI-1L8GQ61o2M-0003va; Thu, 04 Dec 2008 16:47:14 +0100 Received: (qmail 83387 invoked from network); 4 Dec 2008 15:47:14 -0000 Received: from unknown (HELO fbsd8.laiers.local) (192.168.4.151) by laiers.local with SMTP; 4 Dec 2008 15:47:14 -0000 From: Max Laier Organization: FreeBSD To: freebsd-pf@freebsd.org Date: Thu, 4 Dec 2008 16:47:13 +0100 User-Agent: KMail/1.10.1 (FreeBSD/8.0-CURRENT; KDE/4.1.1; i386; ; ) References: <4937F627.8080602@gmail.com> In-Reply-To: <4937F627.8080602@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200812041647.14049.max@love2party.net> X-Provags-ID: V01U2FsdGVkX19op4gidrQnLgcRVnNKjQeBHX/NGCXSm72/L1b lK9MaBLUOqAKyv0GkOGk2YdzaonM2XRbQX/qzQP3d6ReWzWv6u jMF6mHHycag0tI9CSL/FQ== Cc: freebsd-stable@freebsd.org, Vladimir Ermakov Subject: Re: synproxy state does not work on FreeBSD 7.1-PRERELEASE 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: Thu, 04 Dec 2008 15:47:16 -0000 On Thursday 04 December 2008 16:24:23 Vladimir Ermakov wrote: > problem is fixed in OpenBSD 4.4 > http://www.openbsd.org/plus44.html The bug this note refers to was introduced after OpenBSD 4.1 (our last import) and should not be present in the FreeBSD code. I'll double check in a bit to make sure synproxy is working, but I don't think it was broken after my last import ... do you have a particular test case that I could reproduce? -- /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 16:11:49 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 90666106564A for ; Thu, 4 Dec 2008 16:11:49 +0000 (UTC) (envelope-from dkelly@Grumpy.DynDNS.org) Received: from smtp.knology.net (smtp.knology.net [24.214.63.101]) by mx1.freebsd.org (Postfix) with ESMTP id 2C7EF8FC17 for ; Thu, 4 Dec 2008 16:11:48 +0000 (UTC) (envelope-from dkelly@Grumpy.DynDNS.org) Received: (qmail 27294 invoked by uid 0); 4 Dec 2008 15:45:07 -0000 Received: from unknown (HELO Grumpy.DynDNS.org) (75.76.211.79) by smtp7.knology.net with SMTP; 4 Dec 2008 15:45:07 -0000 Received: by Grumpy.DynDNS.org (Postfix, from userid 928) id 9725828422; Thu, 4 Dec 2008 09:45:07 -0600 (CST) Date: Thu, 4 Dec 2008 09:45:07 -0600 From: David Kelly To: Bartosz Stec Message-ID: <20081204154507.GA18645@Grumpy.DynDNS.org> References: <4937A786.9080403@kkip.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4937A786.9080403@kkip.pl> User-Agent: Mutt/1.4.2.3i Cc: FreeBSD Stable Subject: Re: Burning DVD with files>4GB from console X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@freebsd.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Dec 2008 16:11:49 -0000 On Thu, Dec 04, 2008 at 10:48:54AM +0100, Bartosz Stec wrote: > My backup script split filesystem dumps to files with size of 4,37 GB (4 > 588 544 kB). It's just an optimal size to fill out DVDs. At this moment > I have to burn them from windows via smb-link becuase I didn't manage to > do this task from FreeBSD console due to 2GB/4GB filesize restrictions > (growisofs). Since when did FreeBSD (or growisofs) have a 2GB/4GB filesize limit? I have burned 4.3GB DVDs several times. -- David Kelly N4HHE, dkelly@HiWAAY.net ======================================================================== Whom computers would destroy, they must first drive mad. From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 16:27:08 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 395DB1065670 for ; Thu, 4 Dec 2008 16:27:08 +0000 (UTC) (envelope-from stephen@math.missouri.edu) Received: from cauchy.math.missouri.edu (cauchy.math.missouri.edu [128.206.184.213]) by mx1.freebsd.org (Postfix) with ESMTP id 0A5A88FC1F for ; Thu, 4 Dec 2008 16:27:07 +0000 (UTC) (envelope-from stephen@math.missouri.edu) Received: from laptop3.gateway.2wire.net (cauchy.math.missouri.edu [128.206.184.213]) by cauchy.math.missouri.edu (8.14.3/8.14.3) with ESMTP id mB4GEAkK056024; Thu, 4 Dec 2008 10:14:11 -0600 (CST) (envelope-from stephen@math.missouri.edu) Message-ID: <493801F5.2050009@math.missouri.edu> Date: Thu, 04 Dec 2008 10:14:45 -0600 From: Stephen Montgomery-Smith User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.8.1.18) Gecko/20081125 SeaMonkey/1.1.13 MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <4937A786.9080403@kkip.pl> <20081204154507.GA18645@Grumpy.DynDNS.org> In-Reply-To: <20081204154507.GA18645@Grumpy.DynDNS.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Bartosz Stec Subject: Re: Burning DVD with files>4GB from console 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: Thu, 04 Dec 2008 16:27:08 -0000 David Kelly wrote: > On Thu, Dec 04, 2008 at 10:48:54AM +0100, Bartosz Stec wrote: >> My backup script split filesystem dumps to files with size of 4,37 GB (4 >> 588 544 kB). It's just an optimal size to fill out DVDs. At this moment >> I have to burn them from windows via smb-link becuase I didn't manage to >> do this task from FreeBSD console due to 2GB/4GB filesize restrictions >> (growisofs). > > Since when did FreeBSD (or growisofs) have a 2GB/4GB filesize limit? I > have burned 4.3GB DVDs several times. I never had a problem writing huge files. But I did have a problem subsequently reading it with Windows XP. Maybe the file size restriction is a Windows thing. From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 17:06:49 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D6D4C1065672 for ; Thu, 4 Dec 2008 17:06:49 +0000 (UTC) (envelope-from josh.carroll@gmail.com) Received: from mail-gx0-f19.google.com (mail-gx0-f19.google.com [209.85.217.19]) by mx1.freebsd.org (Postfix) with ESMTP id 72F548FC12 for ; Thu, 4 Dec 2008 17:06:49 +0000 (UTC) (envelope-from josh.carroll@gmail.com) Received: by gxk12 with SMTP id 12so3019101gxk.19 for ; Thu, 04 Dec 2008 09:06:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=Li2Y+DxJbqcg0TZ82JW5/oGyyFyprpt9aKKztSAm7IM=; b=K5UDgJeNf6OTehVoKlKgwT7Abg/PBDejDEGiqubwWZlzs7hYDL89ldxZRpQLzyf5l0 D9CiNPg9JU6qFE/ZHsJoNJcSQcdIJALJybaIv489fxQtsrdU8TADxl77Q733aFWqYFsU 2QTI7a+UFo4BvDZ1KlHOo2tFI/sRF8QDNUigI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:cc:in-reply-to :mime-version:content-type:content-transfer-encoding :content-disposition:references; b=mEjMXYfctV4p0WRG0Rxn9aD6tr2B46tqf9N9ZjCrpwqi94cJnSyAk6TlcWPhZOu0Tt 2nPtzOlmsvP+1EGyYQ6DBh3mIvAtdSApPEC88zkIPMnRn8at1slPKVFqkI2dHwb89onw jQwDHQEtkvt6Crb5YxSsa5/kI40y88Crq5c3o= Received: by 10.151.103.11 with SMTP id f11mr10696708ybm.32.1228410164206; Thu, 04 Dec 2008 09:02:44 -0800 (PST) Received: by 10.150.123.1 with HTTP; Thu, 4 Dec 2008 09:02:44 -0800 (PST) Message-ID: <8cb6106e0812040902g69ec2f84t814c2f2b5cdb33f6@mail.gmail.com> Date: Thu, 4 Dec 2008 12:02:44 -0500 From: "Josh Carroll" To: "Gonzalo Nemmi" In-Reply-To: <200812041747.09040.gnemmi@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <8cb6106e0811241129o642dcf28re4ae177c8ccbaa25@mail.gmail.com> <20081125150342.GL2042@deviant.kiev.zoral.com.ua> <8cb6106e0812031453j6dc2f2f4i374145823c084eaa@mail.gmail.com> <200812041747.09040.gnemmi@gmail.com> Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: ext2 inode size patch - RE: PR kern/124621 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: josh.carroll@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Dec 2008 17:06:49 -0000 > Could you please point me to your patch and an explanation on how to apply it > and test it? You can grab the patch here: http://pflog.net/~floyd/ext2fs.diff To apply it: cd /usr/src/sys/gnu/fs patch < /path/to/ext2fs.diff cd /usr/src/sys/modules/ext2fs make clean && make kldload ./ext2fs.ko Then umount and mount again your ext2 file systems. This should apply cleanly to RELENG_7_0, RELENG_7_1 and RELENG_7 source. I'm not sure if it'll apply cleanly to -CURRENT or not (I can provide an updated patch if you need it). Note: if you have ext2fs built into your kernel, you'll have to build and install your kernel as usual after patching, instead of building the module separately. Also, if you already have ext2fs loaded, you'll need to kldunload it first of course. If you want to update the ext2fs.ko in your installed kernel in /boot/kernel, after a make in .../modules/ext2fs, you can "make install". Thanks, Josh From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 17:09:12 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9F3511065673 for ; Thu, 4 Dec 2008 17:09:12 +0000 (UTC) (envelope-from gnemmi@gmail.com) Received: from mail-qy0-f18.google.com (mail-qy0-f18.google.com [209.85.221.18]) by mx1.freebsd.org (Postfix) with ESMTP id 3B5D28FC16 for ; Thu, 4 Dec 2008 17:09:12 +0000 (UTC) (envelope-from gnemmi@gmail.com) Received: by qyk11 with SMTP id 11so5099891qyk.19 for ; Thu, 04 Dec 2008 09:09:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :user-agent:cc:references:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:message-id; bh=D/IZxoDBsYC9MtrwgJrfMVshXjkMMSbPZ3AW1LzXp2A=; b=Yps3iF3Kj7ZAEgb23jfCPacFTJ4HCenNfuI5GBfQip/BYzr4Zg0YsEPQYd580Kbtej mrKn/NEkd0Ok/hoZycgV4VejJGNSHql3uO6t8TbnSmB+sQ/ASFWTVQ4SUj5KMIhPhc93 ZJKte0GLemcyAvacAkHObn5p+s/E+Zj68Y/ho= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:cc:references:in-reply-to :mime-version:content-type:content-transfer-encoding :content-disposition:message-id; b=xTEmDXo2mFOqMlcC7+N8qEcWZRye9gOKp5StffNkHD3qs1CiYdgSsjKH7WWbq9EehR SkaaqyLY9cQvckRi0o49JeSczM5zQ2Raz7KHHioPcbMKpVQMqrr5nMiE3rpd2nL7KBJi zNSAQZP5CAFo5Bj5Ahl4svkkMXqgzI6NPIK1M= Received: by 10.214.149.3 with SMTP id w3mr15054314qad.111.1228409234693; Thu, 04 Dec 2008 08:47:14 -0800 (PST) Received: from ?192.168.1.2? ([190.177.205.95]) by mx.google.com with ESMTPS id 6sm8871917qwk.52.2008.12.04.08.47.12 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 04 Dec 2008 08:47:14 -0800 (PST) From: Gonzalo Nemmi To: freebsd-stable@freebsd.org, josh.carroll@gmail.com Date: Thu, 4 Dec 2008 17:47:08 -0200 User-Agent: KMail/1.9.10 References: <8cb6106e0811241129o642dcf28re4ae177c8ccbaa25@mail.gmail.com> <20081125150342.GL2042@deviant.kiev.zoral.com.ua> <8cb6106e0812031453j6dc2f2f4i374145823c084eaa@mail.gmail.com> In-Reply-To: <8cb6106e0812031453j6dc2f2f4i374145823c084eaa@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200812041747.09040.gnemmi@gmail.com> Cc: freebsd-fs@freebsd.org Subject: Re: ext2 inode size patch - RE: PR kern/124621 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: Thu, 04 Dec 2008 17:09:12 -0000 On Wednesday 03 December 2008 8:53:43 pm Josh Carroll wrote: > > Ok, I describe my concern once more. I do not object against the checking > > of the inode size. But, if inode size is changed, then some data is added > > to the inode, that could (and usually does, otherwise why extend it ?) > > change intrerpetation of the inode. Thus, we need a verification of the > > fact that simply ignoring added fields does not damage filesystem or > > cause user data corruption. Verification != testing. > > Let me take another crack at explaining why I think this patch is not > dangerous. > > The inode size is determined by reading the following member: > > __u16 s_inode_size; > > of the ext2_super_block structure. > > I took a look at the Linux 2.6.27.7 kernel source, and indeed they do > something very similar if not the same: > > #define EXT2_INODE_SIZE(s) (EXT2_SB(s)->s_inode_size) > > If you compare to what I did: > > #define EXT2_INODE_SIZE(s) ((s)->u.ext2_sb.s_inode_size) > > This is really the same thing, since EXT2_SB is defined (in the Linux > kernel src as): > > #ifdef __KERNEL__ > #include > static inline struct ext2_sb_info *EXT2_SB(struct super_block *sb) > { > return sb->s_fs_info; > } > > And struct ext2_sb_info has the following member: > > int s_inode_size; > > Essentially, the changes I made simply query the existing information > from the filesystem, which is what the Linux kernel does as well. > > The inode size, blocks per group, etc are all defined at filesystem > creation time by mke2fs and it ensures the sanity of the relationship > between the inodes/blocks/block groups. > > The first diagram here: > > http://sunsite.nus.sg/LDP/LDP/tlk/node95.html > > Makes it clear that as long as the number of inodes per block and the > blocks per group is is sane during fs creation, looking up the inode > size as my patch does is fine, since the creation of the filesystem is > ensures a correct by construction situation. We're simply reading the > size of the inode based on the filesystem. > > I hope this is sufficient to convince some further thought about > committing this. > > For those interested in the relevant Linux kernel source, you can have > a look at line 105 of include/linux/ext2_fs.h from the linux-2.6.27.7 > kernel source. > > Thanks, > Josh Could you please point me to your patch and an explanation on how to apply it and test it? I've been following your las emails referencing it ( on @questions and @hackers or current i think it was ... ) and I'd like to give it a spin in here ... I've followed the "can't mount ext2/3" problem for a time (since I have that problem) and would like to know to what extent for patch solves the problem. Here are some of the references: mounting linux partitions Fri May 9 18:05:26 UTC 2008 http://lists.freebsd.org/pipermail/freebsd-questions/2008-May/174588.html bad file descriptor when mounting an ext2fs. Tue Jun 10 11:08:46 UTC 2008 http://lists.freebsd.org/pipermail/freebsd-questions/2008-June/176506.html mounting ext2fs partitions on FBSD7 ( third time a charm?) Fri Jul 4 23:33:53 UTC 2008 http://lists.freebsd.org/pipermail/freebsd-questions/2008-July/178219.html My case: root@inferna:~ # ls -l /dev/ad4s ad4s1% ad4s2% ad4s3% ad4s3a% ad4s3b% ad4s3c% ad4s3d% ad4s3e% ad4s3f% ad4s4% ad4s5% ad4s6% ad4s7% ad4s8% root@inferna:~ # ls -l /dev/ad4s root@inferna:~ # tune2fs -l /dev/ad4s1 | grep "Inode size" Inode size: 256 root@inferna:~ # tune2fs -l /dev/ad4s6 | grep "Inode size" Inode size: 256 root@inferna:~ # tune2fs -l /dev/ad4s7 | grep "Inode size" Inode size: 256 root@inferna:~ # tune2fs -l /dev/ad4s8 | grep "Inode size" Inode size: 256 root@inferna:~ # tune2fs -l /dev/ad4s9 | grep "Inode size" BTW: I'm willing to run any tests you need me too, even if they imply a serious risk of loosing data on the 256 inode partitions. Regards -- Blessings Gonzalo Nemmi From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 17:28:37 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 08C94106568E for ; Thu, 4 Dec 2008 17:28:36 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.10]) by mx1.freebsd.org (Postfix) with ESMTP id 8369E8FC1A for ; Thu, 4 Dec 2008 17:28:35 +0000 (UTC) (envelope-from max@love2party.net) Received: from vampire.homelinux.org (dslb-088-066-028-001.pools.arcor-ip.net [88.66.28.1]) by mrelayeu.kundenserver.de (node=mrelayeu7) with ESMTP (Nemesis) id 0ML2xA-1L8I0A48Ua-0007ga; Thu, 04 Dec 2008 18:28:35 +0100 Received: (qmail 84823 invoked from network); 4 Dec 2008 17:28:34 -0000 Received: from unknown (HELO fbsd8.laiers.local) (192.168.4.151) by laiers.local with SMTP; 4 Dec 2008 17:28:34 -0000 From: Max Laier Organization: FreeBSD To: freebsd-pf@freebsd.org Date: Thu, 4 Dec 2008 18:28:33 +0100 User-Agent: KMail/1.10.1 (FreeBSD/8.0-CURRENT; KDE/4.1.1; i386; ; ) References: <4937F627.8080602@gmail.com> <200812041647.14049.max@love2party.net> In-Reply-To: <200812041647.14049.max@love2party.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200812041828.34033.max@love2party.net> X-Provags-ID: V01U2FsdGVkX1/FoR9aygmiP3MjvIaCQU50liCriuBCcdyLFHG 3RZRGNtO1rKMoMS2S7iaimHuxYctcY/Tqd4DphvME3t+TSVtiu kIj0kUlzuKsgAR/ojdSfw== Cc: freebsd-stable@freebsd.org, Vladimir Ermakov Subject: Re: synproxy state does not work on FreeBSD 7.1-PRERELEASE 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: Thu, 04 Dec 2008 17:28:37 -0000 On Thursday 04 December 2008 16:47:13 Max Laier wrote: > On Thursday 04 December 2008 16:24:23 Vladimir Ermakov wrote: > > problem is fixed in OpenBSD 4.4 > > http://www.openbsd.org/plus44.html > > The bug this note refers to was introduced after OpenBSD 4.1 (our last > import) and should not be present in the FreeBSD code. I'll double check > in a bit to make sure synproxy is working, but I don't think it was broken > after my last import ... do you have a particular test case that I could > reproduce? Okay ... here is the story: First off, "synproxy state" is *NOT* broken! But you need to be careful how you use it. If you - like the OP - intend to use it to protect a service running on the same box as your pf, you must make sure to "set skip on lo0" or it will not work. If you are protecting a box behind the pf box, there is no need for that. -- /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 17:54:36 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8A5C11065670 for ; Thu, 4 Dec 2008 17:54:36 +0000 (UTC) (envelope-from korvus@comcast.net) Received: from QMTA08.emeryville.ca.mail.comcast.net (qmta08.emeryville.ca.mail.comcast.net [76.96.30.80]) by mx1.freebsd.org (Postfix) with ESMTP id 6C5C98FC13 for ; Thu, 4 Dec 2008 17:54:36 +0000 (UTC) (envelope-from korvus@comcast.net) Received: from OMTA02.emeryville.ca.mail.comcast.net ([76.96.30.19]) by QMTA08.emeryville.ca.mail.comcast.net with comcast id n4de1a00v0QkzPwA85kRBV; Thu, 04 Dec 2008 17:44:28 +0000 Received: from [192.168.2.164] ([206.210.89.202]) by OMTA02.emeryville.ca.mail.comcast.net with comcast id n5kE1a00F4Mx3R28N5kHxB; Thu, 04 Dec 2008 17:44:21 +0000 X-Authority-Analysis: v=1.0 c=1 a=9etTIFggkaEA:10 a=KeKWfgY5SXgA:10 a=6I5d2MoRAAAA:8 a=eciaTVS0hRXHoakKmeQA:9 a=0z2G_RAHjWLCVpNLqZAA:7 a=UcdITMjmpbDC6zG-yqBnqhet3p8A:4 a=SV7veod9ZcQA:10 a=6-x43y6uxGMA:10 Message-ID: <493816EE.8010408@comcast.net> Date: Thu, 04 Dec 2008 12:44:14 -0500 From: Steve Polyack User-Agent: Thunderbird 2.0.0.18 (X11/20081124) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <4937A786.9080403@kkip.pl> <20081204154507.GA18645@Grumpy.DynDNS.org> <493801F5.2050009@math.missouri.edu> In-Reply-To: <493801F5.2050009@math.missouri.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Burning DVD with files>4GB from console 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: Thu, 04 Dec 2008 17:54:36 -0000 Not too say you're .iso images can't be >2GB/4GB, but I'm pretty sure the ISO9660 standard is limited to a 2GB maximum file size (for files within the .iso). You must use UDF to burn files of greater size. mkisofs(8) seems to support this, if only in alpha/hybrid stage: -udf Include UDF support in the generated filesystem image. UDF sup- port is currently in alpha status and for this reason, it is not possible to create UDF only images. Stephen Montgomery-Smith wrote: > David Kelly wrote: >> On Thu, Dec 04, 2008 at 10:48:54AM +0100, Bartosz Stec wrote: >>> My backup script split filesystem dumps to files with size of 4,37 >>> GB (4 588 544 kB). It's just an optimal size to fill out DVDs. At >>> this moment I have to burn them from windows via smb-link becuase I >>> didn't manage to do this task from FreeBSD console due to 2GB/4GB >>> filesize restrictions (growisofs). >> >> Since when did FreeBSD (or growisofs) have a 2GB/4GB filesize limit? I >> have burned 4.3GB DVDs several times. > > I never had a problem writing huge files. But I did have a problem > subsequently reading it with Windows XP. Maybe the file size > restriction is a Windows thing. > _______________________________________________ > 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" > From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 18:41:18 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0CD831065670; Thu, 4 Dec 2008 18:41:18 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 00BF28FC0A; Thu, 4 Dec 2008 18:41:16 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id UAA03603; Thu, 04 Dec 2008 20:41:14 +0200 (EET) (envelope-from avg@icyb.net.ua) Message-ID: <49382449.80002@icyb.net.ua> Date: Thu, 04 Dec 2008 20:41:13 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.18 (X11/20081124) MIME-Version: 1.0 To: FreeBSD Stable , freebsd-hackers@freebsd.org References: <49300020.6060603@icyb.net.ua> In-Reply-To: <49300020.6060603@icyb.net.ua> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Subject: Re: ichwd problem: watchdog doesn't "bark" 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: Thu, 04 Dec 2008 18:41:18 -0000 on 28/11/2008 16:28 Andriy Gapon said the following: > uname: > FreeBSD 7.1-PRERELEASE r185311 amd64 > > dmesg: > ichwd0: on isa0 > ichwd0: Intel ICH9R watchdog timer (ICH9 or equivalent) > ichwd0: timer disabled > > pciconf: > isab0@pci0:0:31:0: class=0x060100 card=0x50448086 chip=0x29168086 > rev=0x02 hdr=0x00 > vendor = 'Intel Corporation' > device = '82801IR (ICH9R) LPC Interface Controller' > class = bridge > subclass = PCI-ISA > > > When I start watchdogd I see the following messages: > timer enabled > timeout set to 28 ticks > and then a flow of messages: > timer reloaded > > Then I kill -9 watchdogd. > "timer reloded" messages are no longer produced. > And there are no other messages. > > But nothing happens for many minutes that I waited. > BTW, can someone knowledgeable tell me if watchdog better be firing SMI or NMI when it runs down? My bet is on NMI, but who knows. Thanks! Or maybe I am trying to ask a different question. I see that NMI2SMI_EN bit of TCO1_CNT is set 1 on my machine and our watchdog driver is careful to preserve this bit unmodified. This means that watchdog would try to cause SMI instead of NMI. On the other hand I see that bit GBL_SMI_EN of SMI_EN is set to zero, which means that chipset would never generate an SMI. So I think this is why I don't see anything happening. Now, would should try first - reset NMI2SMI_EN to zero or set GBL_SMI_EN to 1? As additional data points: I see that TCO_EN bit of SMI_EN is 1 and it is locked to that value because TCO_LOCK bit of TCO1_CNT is 1. SMI_LOCK in PCI config register GEN_PMCON_1 is not set. -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 19:16:48 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 446121065672 for ; Thu, 4 Dec 2008 19:16:48 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail15.syd.optusnet.com.au (mail15.syd.optusnet.com.au [211.29.132.196]) by mx1.freebsd.org (Postfix) with ESMTP id CD50D8FC1B for ; Thu, 4 Dec 2008 19:16:47 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c122-106-215-175.belrs3.nsw.optusnet.com.au [122.106.215.175]) by mail15.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id mB4JGgP0022695 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 5 Dec 2008 06:16:45 +1100 X-Bogosity: Ham, spamicity=0.000000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.3/8.14.3) with ESMTP id mB4JGgHU098703; Fri, 5 Dec 2008 06:16:42 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.3/8.14.3/Submit) id mB4JGeox098702; Fri, 5 Dec 2008 06:16:40 +1100 (EST) (envelope-from peter) Date: Fri, 5 Dec 2008 06:16:40 +1100 From: Peter Jeremy To: Nathan Butcher Message-ID: <20081204191640.GH58682@server.vk2pj.dyndns.org> References: <49362A3C.7060204@fusiongol.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="FCF9ydJxlAJsfRTu" Content-Disposition: inline In-Reply-To: <49362A3C.7060204@fusiongol.com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-stable@freebsd.org Subject: Re: sysinstall automatic partition labelling/sizing problem 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: Thu, 04 Dec 2008 19:16:48 -0000 --FCF9ydJxlAJsfRTu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2008-Dec-03 15:42:04 +0900, Nathan Butcher wro= te: >Automatic labelling on 7.0 created about 360MB for my root partition on >a 8GB disk. After a buildkernel into 7.1-PRERELEASE, the root partition >was exhausted during the installkernel. Are you running i386 or amd64? 360MB _is_ a very tight fit for amd64 but you should make it unless you have some large, unexpected files lying around in your root partition. As a workaround, you could remove *.symbols from the old kernel files. >Maybe automatic labelling in sysinstall needs to allocate more than >360MB in the root (/) partition if it's going to stay big enough to >accomodate a buildkernel and installkernel from source. Looking at sysinstall, the default size is currently 512MB unless you have less than ~20GB, when it will start scaling down. Your options are: 1) Expand root (maybe use growfs and eat into your swap) 2) Avoid building unwanted modules via MODULES_OVERRIDE. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --FCF9ydJxlAJsfRTu Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkk4LJgACgkQ/opHv/APuId7LACeNHWvj78oA60ZCJmr/MjnVsEH I3UAn2JOYZvHxS7btPbtjoeRtH8N3+R5 =h2jt -----END PGP SIGNATURE----- --FCF9ydJxlAJsfRTu-- From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 19:20:00 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3D28B1065673 for ; Thu, 4 Dec 2008 19:20:00 +0000 (UTC) (envelope-from dkelly@Grumpy.DynDNS.org) Received: from smtp.knology.net (smtp.knology.net [24.214.63.101]) by mx1.freebsd.org (Postfix) with ESMTP id 6C8AD8FC19 for ; Thu, 4 Dec 2008 19:19:59 +0000 (UTC) (envelope-from dkelly@Grumpy.DynDNS.org) Received: (qmail 13590 invoked by uid 0); 4 Dec 2008 19:19:58 -0000 Received: from unknown (HELO Grumpy.DynDNS.org) (75.76.211.79) by smtp5.knology.net with SMTP; 4 Dec 2008 19:19:58 -0000 Received: by Grumpy.DynDNS.org (Postfix, from userid 928) id DC16228422; Thu, 4 Dec 2008 13:19:57 -0600 (CST) Date: Thu, 4 Dec 2008 13:19:57 -0600 From: David Kelly To: Steve Polyack Message-ID: <20081204191957.GA32007@Grumpy.DynDNS.org> References: <4937A786.9080403@kkip.pl> <20081204154507.GA18645@Grumpy.DynDNS.org> <493801F5.2050009@math.missouri.edu> <493816EE.8010408@comcast.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <493816EE.8010408@comcast.net> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org Subject: Re: Burning DVD with files>4GB from console X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@freebsd.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Dec 2008 19:20:00 -0000 On Thu, Dec 04, 2008 at 12:44:14PM -0500, Steve Polyack wrote: > Not too say you're .iso images can't be >2GB/4GB, but I'm pretty sure > the ISO9660 standard is limited to a 2GB maximum file size (for files > within the .iso). You must use UDF to burn files of greater size. > mkisofs(8) seems to support this, if only in alpha/hybrid stage: > > -udf Include UDF support in the generated filesystem image. UDF sup- > port is currently in alpha status and for this reason, it is not > possible to create UDF only images. It would seem then that the O.P. who is already splitting his backup into 4.3GB chunks should split backups into sub-2GB chunks. 4,700,000,000 is the standard DVD size, I'd shoot for chunks of 4.5E9/3 so as to have about 200MB of headroom per DVD. growisofs will write 3 files to the DVD just as easily as one. The magic of growisofs is that it invokes mkisofs on the fly. And also that cdrecord had obnoxious (and broken) licensing in years past when I last tried it. -- David Kelly N4HHE, dkelly@HiWAAY.net ======================================================================== Whom computers would destroy, they must first drive mad. From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 20:48:04 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8D4761065679 for ; Thu, 4 Dec 2008 20:48:04 +0000 (UTC) (envelope-from oberman@es.net) Received: from postal1.es.net (postal1.es.net [198.128.3.205]) by mx1.freebsd.org (Postfix) with ESMTP id 7163A8FC13 for ; Thu, 4 Dec 2008 20:48:04 +0000 (UTC) (envelope-from oberman@es.net) Received: from ptavv.es.net by postal1.es.net (Postal Node 1) with ESMTP (SSL) id KGA22504; Thu, 04 Dec 2008 12:48:04 -0800 Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id EB8D34500F; Thu, 4 Dec 2008 12:48:03 -0800 (PST) To: "Alexandr Pakhomov" In-Reply-To: Your message of "Tue, 02 Dec 2008 19:33:00 +0300." Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1228423683_68706P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Thu, 04 Dec 2008 12:48:03 -0800 From: "Kevin Oberman" Message-Id: <20081204204803.EB8D34500F@ptavv.es.net> X-Sender-IP: 198.128.4.29 X-Sender-Domain: es.net X-Recipent: ;; X-Sender: X-To_Name: Alexandr Pakhomov X-To_Domain: gmail.com X-To: "Alexandr Pakhomov" X-To_Email: pahom.rt@gmail.com X-To_Alias: pahom.rt Cc: Mike Tancsa Subject: Re: repeatable crash on RELENG7 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: Thu, 04 Dec 2008 20:48:04 -0000 --==_Exmh_1228423683_68706P Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > Date: Tue, 2 Dec 2008 19:33:00 +0300 > From: "Alexandr Pakhomov" > Sender: owner-freebsd-stable@freebsd.org > > On Tue, Dec 2, 2008 at 5:12 PM, Mike Tancsa wrote: > > > At 08:38 AM 12/2/2008, Kostik Belousov wrote: > > > >> > > >> > mdconfig -a -t malloc -s 1800M > >> You cannot have ~ 2Gb of kernel memory allocated for md, at least not on > >> i386. > >> > > > > Thanks, how do I find out what the limit is on a machine ? Is it > > vm.kvm_size ? > > > > > > ---Mike > > _______________________________________________ > > 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" > > > > Try tune both vm.kmem_size and vm.kmem_size_max via /boot/loader.conf. They > are equal to 330M by default. Mike, Let me second Kris's suggestion. I can think of very few cases where malloc backed is in any way better than swap backed. Many people assume that swap-backed performance is better, but this is only the case if you run out of memory (and that is full memory, not kvm). md is still RAM based and very fast. The current mdconfig should be defaulting to swap-backed devices, but I don't see any indication of that in the man page, so I may be wrong. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 --==_Exmh_1228423683_68706P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) Comment: Exmh version 2.5 06/03/2002 iD8DBQFJOEIDkn3rs5h7N1ERArVwAKCNPJ++Z0HiimFwgFuxrYluBvkzyACgmYaD 9Fp3CL23o9lKGSjugafJ0zM= =Wnyn -----END PGP SIGNATURE----- --==_Exmh_1228423683_68706P-- From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 21:28:43 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BE6DB1065677 for ; Thu, 4 Dec 2008 21:28:43 +0000 (UTC) (envelope-from korvus@comcast.net) Received: from QMTA01.westchester.pa.mail.comcast.net (qmta01.westchester.pa.mail.comcast.net [76.96.62.16]) by mx1.freebsd.org (Postfix) with ESMTP id 6A4F98FC22 for ; Thu, 4 Dec 2008 21:28:43 +0000 (UTC) (envelope-from korvus@comcast.net) Received: from OMTA05.westchester.pa.mail.comcast.net ([76.96.62.43]) by QMTA01.westchester.pa.mail.comcast.net with comcast id n7ge1a0310vyq2s519FUKL; Thu, 04 Dec 2008 21:15:28 +0000 Received: from [192.168.2.164] ([206.210.89.202]) by OMTA05.westchester.pa.mail.comcast.net with comcast id n9FF1a00c4Mx3R23R9FJrg; Thu, 04 Dec 2008 21:15:26 +0000 X-Authority-Analysis: v=1.0 c=1 a=6I5d2MoRAAAA:8 a=d_4LvegynDpHsueOYS0A:9 a=FaA_p-e2MH80nz0pW00A:7 a=znMLVyXIlFKoWgWtbaPD9sZbD0kA:4 a=MSl-tDqOz04A:10 a=SV7veod9ZcQA:10 a=qm7f-9QL9LsA:10 a=ZKlmZI38X7UA:10 Message-ID: <49384863.9040807@comcast.net> Date: Thu, 04 Dec 2008 16:15:15 -0500 From: Steve Polyack User-Agent: Thunderbird 2.0.0.18 (X11/20081124) MIME-Version: 1.0 To: Kevin Oberman References: <20081204204803.EB8D34500F@ptavv.es.net> In-Reply-To: <20081204204803.EB8D34500F@ptavv.es.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Mike Tancsa , Alexandr Pakhomov Subject: Re: repeatable crash on RELENG7 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: Thu, 04 Dec 2008 21:28:43 -0000 Kevin Oberman wrote: >> Date: Tue, 2 Dec 2008 19:33:00 +0300 >> From: "Alexandr Pakhomov" >> Sender: owner-freebsd-stable@freebsd.org >> >> On Tue, Dec 2, 2008 at 5:12 PM, Mike Tancsa wrote: >> >> >>> At 08:38 AM 12/2/2008, Kostik Belousov wrote: >>> >>> >>>>> mdconfig -a -t malloc -s 1800M >>>>> >>>> You cannot have ~ 2Gb of kernel memory allocated for md, at least not on >>>> i386. >>>> >>>> >>> Thanks, how do I find out what the limit is on a machine ? Is it >>> vm.kvm_size ? >>> >>> >>> ---Mike >>> _______________________________________________ >>> 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" >>> >>> >> Try tune both vm.kmem_size and vm.kmem_size_max via /boot/loader.conf. They >> are equal to 330M by default. >> > > Mike, > > Let me second Kris's suggestion. I can think of very few cases where > malloc backed is in any way better than swap backed. Many people assume > that swap-backed performance is better, but this is only the case if you > run out of memory (and that is full memory, not kvm). > > md is still RAM based and very fast. The current mdconfig should be > defaulting to swap-backed devices, but I don't see any indication of > that in the man page, so I may be wrong. > I agree here. Using mdconfig(8) in malloc-backed mode may lead to unpredictable results when attempting to use large amounts of memory. mdconfig(8) seems to allow you to "reserve" more kernel memory than may be appropriate, and as in Mike's experience, causes a kernel panic upon writing enough data to the malloc'd md(4) device. It seems that the term "swap-backed" is misleading for some people. It does NOT mean your md(4) device will be constantly swapping to disk (and the man page does an alright job of relaying this). It simply means that generally available memory will be used, and so will swap iff available memory happens to drop low enough. The bottom line in my experience with md(4) devices greater than ~100MB is that "swap-backed" is always reliable, while malloc'd md(4) devices will cause unpredictable kernel panics. From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 22:11:48 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0495B1065672 for ; Thu, 4 Dec 2008 22:11:48 +0000 (UTC) (envelope-from josh.carroll@gmail.com) Received: from rn-out-0910.google.com (rn-out-0910.google.com [64.233.170.188]) by mx1.freebsd.org (Postfix) with ESMTP id A95718FC29 for ; Thu, 4 Dec 2008 22:11:47 +0000 (UTC) (envelope-from josh.carroll@gmail.com) Received: by rn-out-0910.google.com with SMTP id j71so3971034rne.12 for ; Thu, 04 Dec 2008 14:11:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=VTgGECwKuluVbGO6mbzmVb0lpMy6Djfh2NAmVDYcoi4=; b=gVO/Z3+/6I98+2KB71E6MPu/57DffPe/0oZcO9ioovLysQlRb7bqtoxjp5oolqjoeX ZXGrIjdmvZEIjQZvcYePPlHF3uwI8l2366uUrrWTRJonaAz3YZysF2bIVwkSWAENX5lc jrHRaWtawvTVomMf0ajjArDSHD/PfCWOXO+SY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:cc:in-reply-to :mime-version:content-type:content-transfer-encoding :content-disposition:references; b=AKnhCzptIRRknQpyyW/XjcDjJVQkhoFZRGD33oM8iuMSFHPXTd6GAkLbm8YZ+x1CO+ Yf0wN383Kj+xYU5JITVShv7ByRXE56NDPPfAqUiNVLC4GgGTmbDpNCWyfjH98zXxpt5O 2KGoRMLiqa4ufSiNiuwssnTNP4kJvg2wMSFRo= Received: by 10.151.110.14 with SMTP id n14mr335580ybm.141.1228428706872; Thu, 04 Dec 2008 14:11:46 -0800 (PST) Received: by 10.150.123.1 with HTTP; Thu, 4 Dec 2008 14:11:46 -0800 (PST) Message-ID: <8cb6106e0812041411t13ca9ffcjc4cc66a33ef43133@mail.gmail.com> Date: Thu, 4 Dec 2008 17:11:46 -0500 From: "Josh Carroll" To: "Steve Polyack" In-Reply-To: <49384863.9040807@comcast.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20081204204803.EB8D34500F@ptavv.es.net> <49384863.9040807@comcast.net> Cc: Alexandr Pakhomov , Mike Tancsa Subject: Re: repeatable crash on RELENG7 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: josh.carroll@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Dec 2008 22:11:48 -0000 > It seems that the term "swap-backed" is misleading for some people. It does > NOT mean your md(4) device will be constantly swapping to disk (and the man > page does an alright job of relaying this). It simply means that generally > available memory will be used, and so will swap iff available memory happens > to drop low enough. > > The bottom line in my experience with md(4) devices greater than ~100MB is > that "swap-backed" is always reliable, while malloc'd md(4) devices will > cause unpredictable kernel panics. Using -t swap instead of -t malloc will prevent a panic, but creating an md greater than the size of the VM available and filling it will cause resource exhaustion and OOM will kick in and start killing processes, right? So while it won't panic the box, I still wouldn't consider it safe to use unless the size of the md is chosen carefully. Someone please correct me if I'm wrong, but I think that'd be the behavior if an md with -t swap is used, right? Regards, Josh From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 22:34:43 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5A31E106564A for ; Thu, 4 Dec 2008 22:34:43 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from mail-gx0-f19.google.com (mail-gx0-f19.google.com [209.85.217.19]) by mx1.freebsd.org (Postfix) with ESMTP id 143278FC12 for ; Thu, 4 Dec 2008 22:34:42 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: by gxk12 with SMTP id 12so3168048gxk.19 for ; Thu, 04 Dec 2008 14:34:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=kqqtNCR6wpFVXw1f6ZMHynDE2ZL7331sADXFyEe+vEo=; b=q4M6mhKm0zsdVlrmVXbWMxd4q/+QEG4Q/2/fqEqAos7dn21CybEmyT6UqdWLYtHulU Eyh964KcLSEYaXIh+Bh5QIsZ+zN3Z3T0UuYHK47vkEre9/cdyUmsWIxmDjSxydErMtXX HLv/DvXA1bEOuJihyMUad1f6+Mer6GXLU6LMY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=Xy6eo41eZEI96BP1W9lb9iGpQhR1y0cSuy0hPrkTXjlj9jlw7sFDcLoiFzYCXH/RRr 7MGXmaOv22euesKDGDGuktP1wXJqkOsp+aIt5nprQbpvRJK31bt8CLbGI1XquSduCz4A Xv9t9VuIICf98F7eN1R0do7j3Nrv+lsRmuGe4= Received: by 10.150.140.6 with SMTP id n6mr396647ybd.75.1228429929023; Thu, 04 Dec 2008 14:32:09 -0800 (PST) Received: by 10.151.128.6 with HTTP; Thu, 4 Dec 2008 14:32:08 -0800 (PST) Message-ID: <5f67a8c40812041432y13793ee5k1d2526c9829dc16f@mail.gmail.com> Date: Thu, 4 Dec 2008 17:32:08 -0500 From: "Zaphod Beeblebrox" To: "FreeBSD Stable Mailing List" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: SATA CD fail. 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: Thu, 04 Dec 2008 22:34:43 -0000 I've got an HP DL-360 1U here that has a slim SATA CDROM. I've (so far) tried booting FreeBSD-7.0-RELEASE and FreeBSD-7.1-BETA2. I've tried both rewritable media (my first choice) and write-once media. The kernel loads fine, but multiuser fails with "acd0: TIMEOUT - READ_BIG retrying" ... twice, followed by "timed out". From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 23:20:22 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DA5611065676 for ; Thu, 4 Dec 2008 23:20:22 +0000 (UTC) (envelope-from oberman@es.net) Received: from postal1.es.net (postal4.es.net [198.124.252.66]) by mx1.freebsd.org (Postfix) with ESMTP id 862878FC1D for ; Thu, 4 Dec 2008 23:20:22 +0000 (UTC) (envelope-from oberman@es.net) Received: from postal1.es.net (postal3.es.net [198.128.3.207]) by postal4.es.net (Postal Node 4) with ESMTP (SSL) id KJY84121; Thu, 04 Dec 2008 15:20:21 -0800 Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by postal3.es.net (Postal Node 3) with ESMTP (SSL) id KJY72420; Thu, 04 Dec 2008 15:20:20 -0800 Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 7289A45019; Thu, 4 Dec 2008 15:20:20 -0800 (PST) To: josh.carroll@gmail.com In-Reply-To: Your message of "Thu, 04 Dec 2008 17:11:46 EST." <8cb6106e0812041411t13ca9ffcjc4cc66a33ef43133@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1228432820_12904P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Thu, 04 Dec 2008 15:20:20 -0800 From: "Kevin Oberman" Message-Id: <20081204232020.7289A45019@ptavv.es.net> X-Sender-IP: 198.128.3.207 X-Sender-Domain: es.net X-Recipent: ; ; ; ; X-Sender: X-To_Name: X-To_Domain: gmail.com X-To: josh.carroll@gmail.com X-To_Email: josh.carroll@gmail.com X-To_Alias: josh.carroll Cc: Alexandr Pakhomov , Mike Tancsa , Steve Polyack Subject: Re: repeatable crash on RELENG7 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: Thu, 04 Dec 2008 23:20:22 -0000 --==_Exmh_1228432820_12904P Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > Date: Thu, 4 Dec 2008 17:11:46 -0500 > From: "Josh Carroll" > > > It seems that the term "swap-backed" is misleading for some people. It does > > NOT mean your md(4) device will be constantly swapping to disk (and the man > > page does an alright job of relaying this). It simply means that generally > > available memory will be used, and so will swap iff available memory happens > > to drop low enough. > > > > The bottom line in my experience with md(4) devices greater than ~100MB is > > that "swap-backed" is always reliable, while malloc'd md(4) devices will > > cause unpredictable kernel panics. > > Using -t swap instead of -t malloc will prevent a panic, but creating > an md greater than the size of the VM available and filling it will > cause resource exhaustion and OOM will kick in and start killing > processes, right? So while it won't panic the box, I still wouldn't > consider it safe to use unless the size of the md is chosen carefully. > Someone please correct me if I'm wrong, but I think that'd be the > behavior if an md with -t swap is used, right? Yes, but the VM available is just a bit larger than the amount of KVM. you still need at least a bit of sanity when you create (and fill) an MD device. For performance reasons, I suggest keeping the size of an MD so that it will fit in RAM. Paging in and out is rather painfully slow. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 --==_Exmh_1228432820_12904P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) Comment: Exmh version 2.5 06/03/2002 iD8DBQFJOGW0kn3rs5h7N1ERAh9jAJoDr0hX/7rTzLodd6wF8gm0MsfdLACfebHl FSfNU/zkkOoIxPN91Owe/V0= =hyxw -----END PGP SIGNATURE----- --==_Exmh_1228432820_12904P-- From owner-freebsd-stable@FreeBSD.ORG Fri Dec 5 00:41:30 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6A0151065673 for ; Fri, 5 Dec 2008 00:41:30 +0000 (UTC) (envelope-from fbsdlists@gmail.com) Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.28]) by mx1.freebsd.org (Postfix) with ESMTP id 1B7288FC1F for ; Fri, 5 Dec 2008 00:41:29 +0000 (UTC) (envelope-from fbsdlists@gmail.com) Received: by yx-out-2324.google.com with SMTP id 8so1883006yxb.13 for ; Thu, 04 Dec 2008 16:41:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=DMuLRPYV/MAEn3DKicSgLuNCT3L/oOkEgGZpr90Og98=; b=H4SuKeWKCiAFU3wuUkaInB+wHPR5Rpcdxquo4kyFG0veLjeaClwQyeqiMoBu69l9F/ iA92QTR5ywheowLivxIjtZ9dDd+l1BFo4hmY5BXjh1FVVbslA5WgHm2ArEDeXkB7SYxe AiZBd5LJH2pCN/4PScpL+bIP6qsgHQPrlU5YE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=pd94aM/Okt9NGoL7d/0jUb5l3xT0rLEjHFe5lYRTjuuAgil5q7WZrELmbLWFQKBd3T 5zMqyKSoBAJm9/4RD1vXcm0Q7AJkmohfFC0aH177shrkqnzJ59hh+J7jRuZfZD3UnIc2 pBAij+9RIEGLDEAMqdbyxiwIyvVMLG1kh8PEM= Received: by 10.150.97.19 with SMTP id u19mr496492ybb.206.1228436069938; Thu, 04 Dec 2008 16:14:29 -0800 (PST) Received: by 10.151.123.3 with HTTP; Thu, 4 Dec 2008 16:14:29 -0800 (PST) Message-ID: <54db43990812041614h62f2608bua8462341a59c8626@mail.gmail.com> Date: Thu, 4 Dec 2008 19:14:29 -0500 From: "Bob Johnson" To: "Bartosz Stec" In-Reply-To: <4937D26D.60408@kkip.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4937A786.9080403@kkip.pl> <4937CBBC.1020406@smo.de> <4937D26D.60408@kkip.pl> Cc: FreeBSD Stable Subject: Re: Burning DVD with files>4GB from console 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: Fri, 05 Dec 2008 00:41:30 -0000 On 12/4/08, Bartosz Stec wrote: > Philipp Ost pisze: >> Hi, >> >> Bartosz Stec wrote: >>> [...] Is there *any* way to burn DVDs with files>4GB from FreeBSD >>> console? >> >> I succesfully used growisofs for exactly this task ;-) >> >> What I did is (for DL-DVDs): >> # growisofs -dvd-compat -Z /dev/cd0=$file.iso -speed=2 >> >> I had to limit the speed, else it wouldn't do anything. If I burn >> "normal" DVDs I don't need the speed limit. >> >> HTH, >> Philipp > But doesn't that command expecting file.iso being already premastered > ISO image? OK, that's *some* way, but to be clear - I want to avoid > preparing ISO images too ;) > Some thoughts that might be useful: 1) I expect the problem is with mkisofs version 2.01 that is used in FreeBSD (at least in 7.0), but I haven't attempted to confirm this. Growisofs is supposed to handle large files, and so are recent versions of mkisofs. The author of mkisofs considers 2.01 to be obsolete. Perhaps installing a newer mkisofs is the solution (e.g. sysutils/cdrtools-devel appears to be fairly recent)? 2) Perhaps you could do what I do and write tar files directly to DVD with no filesystem. I use burncd to write the file to the DVD, but I don't remember if I've tried to exceed 4 GiB per file. You might need growisofs in premastered image mode instead of burncd. To read the file later use something like 'tar -xf /dev/cd0'. Might have a problem with this in Windows, but maybe that's not really a problem? 3) You could modify your script to use mkisofs to create the ISO image as part of the process of splitting your files into (smaller) chunks. Then use growisofs in premastered image mode, as already suggested. If you want to do this, look at the -stream-media-size option in mkisofs. 4) The 4 GiB limit on file size is built into the ISO 9660 filesystem prior to Level 3. Level 3 allows larger files by allowing files to have multiple extents (each extent must still be < 4 GiB). You may need to explicitly specify ISO Level 3 to get the correct behavior (i.e. use the '-iso-level 3' option with growisofs or mkisofs). -- Bob Johnson fbsdlists@gmail.com From owner-freebsd-stable@FreeBSD.ORG Fri Dec 5 01:42:16 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 019B11065687 for ; Fri, 5 Dec 2008 01:42:16 +0000 (UTC) (envelope-from lists-freebsd-stable@biaix.org) Received: from grummit.biaix.org (86.Red-213-97-212.staticIP.rima-tde.net [213.97.212.86]) by mx1.freebsd.org (Postfix) with SMTP id 8668D8FC17 for ; Fri, 5 Dec 2008 01:42:15 +0000 (UTC) (envelope-from lists-freebsd-stable@biaix.org) Received: (qmail 3872 invoked by uid 1012); 5 Dec 2008 01:14:12 -0000 Date: Fri, 5 Dec 2008 02:14:12 +0100 From: Joan Picanyol i Puig To: freebsd-stable@freebsd.org Message-ID: <20081205011412.GA3515@grummit.biaix.org> Mail-Followup-To: freebsd-stable@freebsd.org, cperciva@freebsd.org, simon@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.11 Cc: simon@freebsd.org, cperciva@freebsd.org Subject: can't freebsd-update from 7.1-PRERELEASE 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: Fri, 05 Dec 2008 01:42:16 -0000 Hi, Apparently 7.1-PRERELEASE has been pulled from freebsd-update's server while I was being lazy: calvin% sudo freebsd-update --debug upgrade -r 7.1-BETA2 Looking up update.FreeBSD.org mirrors... 1 mirrors found. Fetching metadata signature for 7.1-PRERELEASE from update1.FreeBSD.org... fetch: http://update1.FreeBSD.org/7.1-PRERELEASE/i386/latest.ssl: Not Found failed. No mirrors remaining, giving up. Any workarounds? -- pica From owner-freebsd-stable@FreeBSD.ORG Fri Dec 5 02:53:48 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F2EB01065675 for ; Fri, 5 Dec 2008 02:53:48 +0000 (UTC) (envelope-from ari@ish.com.au) Received: from fish.ish.com.au (eth5921.nsw.adsl.internode.on.net [59.167.240.32]) by mx1.freebsd.org (Postfix) with ESMTP id AF1308FC0A for ; Fri, 5 Dec 2008 02:53:48 +0000 (UTC) (envelope-from ari@ish.com.au) Received: from ip-132.ish.com.au ([203.29.62.132]:63478) by fish.ish.com.au with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from ) id 1L8RKH-00070w-08; Fri, 05 Dec 2008 14:25:57 +1100 Message-Id: From: Aristedes Maniatis To: freebsd-stable Stable In-Reply-To: <20081205011412.GA3515@grummit.biaix.org> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Date: Fri, 5 Dec 2008 13:53:43 +1100 References: <20081205011412.GA3515@grummit.biaix.org> X-Mailer: Apple Mail (2.929.2) Cc: cperciva@freebsd.org Subject: Re: can't freebsd-update from 7.1-PRERELEASE 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: Fri, 05 Dec 2008 02:53:49 -0000 On 05/12/2008, at 12:14 PM, Joan Picanyol i Puig wrote: > Hi, > > Apparently 7.1-PRERELEASE has been pulled from freebsd-update's server > while I was being lazy: > > calvin% sudo freebsd-update --debug upgrade -r 7.1-BETA2 > Looking up update.FreeBSD.org mirrors... 1 mirrors found. > Fetching metadata signature for 7.1-PRERELEASE from > update1.FreeBSD.org... > fetch: http://update1.FreeBSD.org/7.1-PRERELEASE/i386/latest.ssl: > Not Found > failed. > No mirrors remaining, giving up. Yeah, this seems to be a problem in freebsd-update. You can workaround like this: # env UNAME_r=7.1-BETA freebsd-update upgrade -r 7.1-BETA2 Something got mixed up in the naming of the releases and freebsd- update gets confused. Ari Maniatis --------------------------> ish http://www.ish.com.au Level 1, 30 Wilson Street Newtown 2042 Australia phone +61 2 9550 5001 fax +61 2 9550 4001 GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A From owner-freebsd-stable@FreeBSD.ORG Fri Dec 5 03:04:11 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CDD94106564A for ; Fri, 5 Dec 2008 03:04:11 +0000 (UTC) (envelope-from n-butcher=freebsd-stable=freebsd.org=mmporwnv@fusiongol.com) Received: from smtp12.dentaku.gol.com (smtp12.dentaku.gol.com [203.216.5.74]) by mx1.freebsd.org (Postfix) with ESMTP id 9E1A08FC17 for ; Fri, 5 Dec 2008 03:04:11 +0000 (UTC) (envelope-from n-butcher=freebsd-stable=freebsd.org=mmporwnv@fusiongol.com) Received: from nat-166.gol.co.jp ([203.216.1.166] helo=[127.0.0.1]) by smtp12.dentaku.gol.com with esmtpa (Dentaku) id 1L8QzC-0000Z7-8I; Fri, 05 Dec 2008 12:04:10 +0900 Message-ID: <49389A27.8040704@fusiongol.com> Date: Fri, 05 Dec 2008 12:04:07 +0900 From: Nathan Butcher User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: Peter Jeremy References: <49362A3C.7060204@fusiongol.com> <20081204191640.GH58682@server.vk2pj.dyndns.org> In-Reply-To: <20081204191640.GH58682@server.vk2pj.dyndns.org> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV GOL (outbound) X-Abuse-Complaints: abuse@gol.com Cc: freebsd-stable@freebsd.org Subject: Re: sysinstall automatic partition labelling/sizing problem 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: Fri, 05 Dec 2008 03:04:11 -0000 > Are you running i386 or amd64? 360MB _is_ a very tight fit for amd64 > but you should make it unless you have some large, unexpected files > lying around in your root partition. As a workaround, you could > remove *.symbols from the old kernel files. Running amd64. The install was fresh so there were no extra files in / > Looking at sysinstall, the default size is currently 512MB unless you > have less than ~20GB, when it will start scaling down. maybe it needs to scale down just a little bit less than it already does.... although granted, not every install is going to experience a kernal recompile from source - well, ones that expect to be maintained anyway. > Your options are: > 1) Expand root (maybe use growfs and eat into your swap) > 2) Avoid building unwanted modules via MODULES_OVERRIDE. Fair enough. This issue just bit me in the behind because I was expecting the 7.1 kernal and modules to take up about as much space as 7.0 ... but then I remember that dtrace found it's way into 7.1 plus a whole lotta code.... From owner-freebsd-stable@FreeBSD.ORG Fri Dec 5 04:34:06 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EB515106564A for ; Fri, 5 Dec 2008 04:34:06 +0000 (UTC) (envelope-from jesper@nohack.se) Received: from proxy3.bredband.net (proxy3.bredband.net [195.54.101.73]) by mx1.freebsd.org (Postfix) with ESMTP id A7B838FC14 for ; Fri, 5 Dec 2008 04:34:06 +0000 (UTC) (envelope-from jesper@nohack.se) Received: from ironport.bredband.com (195.54.101.120) by proxy3.bredband.net (7.3.127) id 492A9CFF0041F911 for freebsd-stable@freebsd.org; Fri, 5 Dec 2008 05:13:51 +0100 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AkA4ABs5OElV4vm9PGdsb2JhbACBbZFYAQEBATW7a4F5GQRv Received: from c-bdf9e255.06-33-6f72652.cust.bredbandsbolaget.se (HELO zero.nohack.se) ([85.226.249.189]) by ironport1.bredband.com with ESMTP; 05 Dec 2008 05:13:55 +0100 Received: by zero.nohack.se (Postfix, from userid 1000) id 715C011570; Fri, 5 Dec 2008 05:14:33 +0100 (CET) Date: Fri, 5 Dec 2008 05:14:33 +0100 From: Jesper Wallin To: freebsd-stable@freebsd.org Message-ID: <20081205041433.GA35652@zero.nohack.se> Mail-Followup-To: freebsd-stable@freebsd.org References: <4937F627.8080602@gmail.com> <200812041647.14049.max@love2party.net> <200812041828.34033.max@love2party.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <200812041828.34033.max@love2party.net> User-Agent: Mutt/1.4.2.3i Subject: Re: synproxy state does not work on FreeBSD 7.1-PRERELEASE 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: Fri, 05 Dec 2008 04:34:07 -0000 * Max Laier [2008-12-04 18:28:33 +0100]: > On Thursday 04 December 2008 16:47:13 Max Laier wrote: > > On Thursday 04 December 2008 16:24:23 Vladimir Ermakov wrote: > > > problem is fixed in OpenBSD 4.4 > > > http://www.openbsd.org/plus44.html > > > > The bug this note refers to was introduced after OpenBSD 4.1 (our last > > import) and should not be present in the FreeBSD code. I'll double check > > in a bit to make sure synproxy is working, but I don't think it was broken > > after my last import ... do you have a particular test case that I could > > reproduce? > > Okay ... here is the story: First off, "synproxy state" is *NOT* broken! But > you need to be careful how you use it. If you - like the OP - intend to use > it to protect a service running on the same box as your pf, you must make sure > to "set skip on lo0" or it will not work. If you are protecting a box behind > the pf box, there is no need for that. Without getting too far off-topic here. I personally find synproxy (or any stateful firewall for that matter) useless. The idea behind synproxy is to protect the actual server from a SYN-flood, which would cause all sockets to be filled up and the service would be unavailable. With this "protection" enabled, you simply limit the amount of SYN packets to respond to, to the amount of what your state-table allow. When the state-table is full, you're service will still be unavailable. During my personal testing, I could easily make a service hosted on a machine with a gigabit connection unavailable with approximenty 250kb/s of SYN-packets with random source addresses, using some lines of simple perl code. I would rather suggest using the "no state" option and use syncookies, as it's *way* more effective against this kind of attack. You can easily limit the outbound traffic using altq if needed. Using synstate will only make the real users fight against the attacker for an open spot in the states-table, where an attacker easily can create ~200k states a sec, using very little bandwidth. (note that pf's default size of the states-table is 10000) I would love if someone (I would do it myself if I had the knowledge of C/C++) could add some sort of "syn-cookies + pf" support, where pf took advantage of the syn-cookie feature when deciding if the states-table is full or not. Making it responding with SYN/ACK's even if the states-table is full, and use the syn-cookies algorithm when an ACK is recieved, and re-add the SYN-state into the table if the syn-cookie is valid. Regards, Jesper Wallin ps, seems like I forgot to forward this to the list. ;-) From owner-freebsd-stable@FreeBSD.ORG Fri Dec 5 05:53:46 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4B2C31065672 for ; Fri, 5 Dec 2008 05:53:46 +0000 (UTC) (envelope-from david@esn.org.za) Received: from serendipity.wcape.school.za (seren.esn.org.za [196.211.28.252]) by mx1.freebsd.org (Postfix) with ESMTP id 472038FC13 for ; Fri, 5 Dec 2008 05:53:42 +0000 (UTC) (envelope-from david@esn.org.za) Received: from intsika.ct.esn.org.za ([196.211.28.250] helo=ct.esn.org.za) by serendipity.wcape.school.za with esmtp (Exim 4.30) id 1L8TdD-000C1X-Fh for freebsd-stable@freebsd.org; Fri, 05 Dec 2008 07:53:39 +0200 Received: from ct.esn.org.za ([192.168.0.32]) by ct.esn.org.za with Microsoft SMTPSVC(6.0.3790.3959); Fri, 5 Dec 2008 07:53:39 +0200 Received: from exchange.ct.esn.org.za ([fe80::3c71:5518:de45:c66c]) by exchange.ct.esn.org.za ([fe80::3c71:5518:de45:c66c%10]) with mapi; Fri, 5 Dec 2008 07:53:38 +0200 From: David Peall To: "'freebsd-stable@freebsd.org'" Date: Fri, 5 Dec 2008 07:53:37 +0200 Thread-Topic: rtfree: 0xffffff00013797c0 has 1 refs Thread-Index: AclWndD0yXEjhcd9Qyu3f4rzdMPHMw== Message-ID: <0807767D2D53E649827BC55A3A53B06709C6C04BFE@exchange.ct.esn.org.za> Accept-Language: en-US, en-ZA Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-ZA MIME-Version: 1.0 X-OriginalArrivalTime: 05 Dec 2008 05:53:39.0319 (UTC) FILETIME=[D2332070:01C9569D] X-Antivirus-Scanned: Clean by seren.wcsn.org.za Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: rtfree: 0xffffff00013797c0 has 1 refs 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: Fri, 05 Dec 2008 05:53:46 -0000 Hi I'm getting some strange messages: Dec 5 07:49:19 jonny kernel: rtfree: 0xffffff0001379d90 has 1 refs Dec 5 07:49:19 jonny kernel: rtfree: 0xffffff000a1784d8 has 1 refs Dec 5 07:49:28 jonny kernel: rtfree: 0xffffff000198a7c0 has 1 refs Dec 5 07:49:31 jonny kernel: rtfree: 0xffffff00013797c0 has 1 refs Dec 5 07:49:35 jonny kernel: rtfree: 0xffffff00013797c0 has 1 refs Dec 5 07:49:37 jonny kernel: rtfree: 0xffffff0001c233e0 has 1 refs Dec 5 07:49:43 jonny kernel: rtfree: 0xffffff00013797c0 has 1 refs Dec 5 07:49:47 jonny kernel: rtfree: 0xffffff0001b3bc98 has 1 refs I've tried google but couldn't find anything usefull. Uname -a FreeBSD jonny.esn.org.za 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Wed Nov = 26 08:03:32 UTC 2008 root@:/usr/obj/usr/src/sys/GENERIC amd64 Is there some other output that would be useful please let me know. -- David Peall :: IT Manager e-Schools' Network :: http://www.esn.org.za/ Phone +27 (021) 674-9140 From owner-freebsd-stable@FreeBSD.ORG Fri Dec 5 07:16:03 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1BE4F1065672 for ; Fri, 5 Dec 2008 07:16:03 +0000 (UTC) (envelope-from samflanker@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.189]) by mx1.freebsd.org (Postfix) with ESMTP id 9B66D8FC18 for ; Fri, 5 Dec 2008 07:16:02 +0000 (UTC) (envelope-from samflanker@gmail.com) Received: by nf-out-0910.google.com with SMTP id h3so2362390nfh.33 for ; Thu, 04 Dec 2008 23:16:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=Tk6Xc7gqJBYg/JvnoDoV9CPLcqTZgS8gzxb1jcn6AwA=; b=oLuNhrXYRZejXsgQFWSDU70XKgqCLZl9qwRDzHQyCzmiL3madM/voF/7if/VYaG2CU cOiaG2iRk9QGnlD0ZXtLo4srYYhi8MFOMgBTl2lj+XkcZinfxCrkbIqXxRtj4cp/YsaP lI6NNeo9X0r7f5QIcdC1vbQJWYd+6QltkYW4o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=C+WNgiUsfz/3XesO14ePbYV4kmrHD6JTS7HfrpTmVe3HagEkTdO1J/fCic9gzpFu84 luruUmzfvFuasIZBW4A73m2lc8t5SZHa1U5bIKycnvGAxtW12GmeexT/xesUGYnK0d+a kXufbNktJ35heBaXgf6gnzTGtzLUwmknHUVN4= Received: by 10.210.76.19 with SMTP id y19mr17121801eba.52.1228461361181; Thu, 04 Dec 2008 23:16:01 -0800 (PST) Received: from localhost.localdomain ([213.152.137.42]) by mx.google.com with ESMTPS id 3sm6543998eyj.41.2008.12.04.23.15.58 (version=SSLv3 cipher=RC4-MD5); Thu, 04 Dec 2008 23:15:59 -0800 (PST) Message-ID: <4938D540.4080304@gmail.com> Date: Fri, 05 Dec 2008 10:16:16 +0300 From: Vladimir Ermakov User-Agent: Thunderbird 2.0.0.18 (X11/20081119) MIME-Version: 1.0 To: Max Laier References: <4937F627.8080602@gmail.com> <200812041647.14049.max@love2party.net> <200812041828.34033.max@love2party.net> In-Reply-To: <200812041828.34033.max@love2party.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, freebsd-pf@freebsd.org Subject: Re: synproxy state does not work on FreeBSD 7.1-PRERELEASE 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: Fri, 05 Dec 2008 07:16:03 -0000 Max Laier wrote: > > > Okay ... here is the story: First off, "synproxy state" is *NOT* broken! But > you need to be careful how you use it. If you - like the OP - intend to use > it to protect a service running on the same box as your pf, you must make sure > to "set skip on lo0" or it will not work. If you are protecting a box behind > the pf box, there is no need for that. > > Max, sorry for your time. Thanks, i solved the problem. /Vladimir Ermakov From owner-freebsd-stable@FreeBSD.ORG Fri Dec 5 08:00:51 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4B3781065670 for ; Fri, 5 Dec 2008 08:00:51 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.25]) by mx1.freebsd.org (Postfix) with ESMTP id D11928FC08 for ; Fri, 5 Dec 2008 08:00:50 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: by ey-out-2122.google.com with SMTP id 6so1879224eyi.7 for ; Fri, 05 Dec 2008 00:00:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=MLIuWKCaQYI8CKJAtGAkTd4dhqrbzWU5C5609IgXmUk=; b=VrFtd91UZbWBd4TQs6978OOO6B1Q+vP7xc+C6SuBLItCWvSzKemLajqsadzKqrd5Ar Ssnhrh+LKhIxVGIHktlE1QXOhl4UoXQNNEm0RfixqSPdk7BS2akIUPnki/gkLjL0NSkV 38C6c8COmqgsNaziF7mKtos/1uywnvEb6taqw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=nZ3kVpudLdiVnq2C8/OQDRQEmPOzJ47Ue6iJBTaxuyCViYWBl6u8JQVaEkytijLAyV nOrpko05knRcQoeYv8nNyP6qo2L18Aenm1KIku1UdgRwpeidwXVJ7ovXgZgA3xM3TGT5 Kxl547CInK3VfN1DpDFUgHdS1QIOz8s5mg+hc= Received: by 10.210.21.6 with SMTP id 6mr17160289ebu.18.1228464049609; Fri, 05 Dec 2008 00:00:49 -0800 (PST) Received: by 10.210.34.12 with HTTP; Fri, 5 Dec 2008 00:00:49 -0800 (PST) Message-ID: Date: Fri, 5 Dec 2008 11:00:49 +0300 From: pluknet To: "Zaphod Beeblebrox" In-Reply-To: <5f67a8c40812041432y13793ee5k1d2526c9829dc16f@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <5f67a8c40812041432y13793ee5k1d2526c9829dc16f@mail.gmail.com> Cc: FreeBSD Stable Mailing List Subject: Re: SATA CD fail. 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: Fri, 05 Dec 2008 08:00:51 -0000 2008/12/5 Zaphod Beeblebrox : > I've got an HP DL-360 1U here that has a slim SATA CDROM. I've (so far) > tried booting FreeBSD-7.0-RELEASE and FreeBSD-7.1-BETA2. I've tried both > rewritable media (my first choice) and write-once media. The kernel loads > fine, but multiuser fails with "acd0: TIMEOUT - READ_BIG retrying" ... > twice, followed by "timed out". I workarounded this by ejecting CD after kernel is loaded but before probing media, then installing from sysinstall via NFS from this CD inserted on nearby with IDE CDROM computer. -- wbr, pluknet From owner-freebsd-stable@FreeBSD.ORG Fri Dec 5 08:33:02 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 634F31065675 for ; Fri, 5 Dec 2008 08:33:02 +0000 (UTC) (envelope-from admin@kkip.pl) Received: from mainframe.kkip.pl (kkip.pl [87.105.164.78]) by mx1.freebsd.org (Postfix) with ESMTP id 117AF8FC21 for ; Fri, 5 Dec 2008 08:33:02 +0000 (UTC) (envelope-from admin@kkip.pl) Received: from admin.admin.lan.kkip.pl ([10.66.3.254]) by mainframe.kkip.pl with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1L8W7N-0006gy-Gj for freebsd-stable@freebsd.org; Fri, 05 Dec 2008 09:33:01 +0100 Message-ID: <4938E73A.5070304@kkip.pl> Date: Fri, 05 Dec 2008 09:32:58 +0100 From: Bartosz Stec User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <4937A786.9080403@kkip.pl> <20081204154507.GA18645@Grumpy.DynDNS.org> In-Reply-To: <20081204154507.GA18645@Grumpy.DynDNS.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated-User: admin@kkip.pl X-Authenticator: plain X-Sender-Verify: SUCCEEDED (sender exists & accepts mail) X-Spam-Score: -8.9 X-Spam-Score-Int: -88 X-Exim-Version: 4.69 (build at 01-Nov-2008 10:39:57) X-Date: 2008-12-05 09:33:01 X-Connected-IP: 10.66.3.254:1846 X-Message-Linecount: 72 X-Body-Linecount: 59 X-Message-Size: 3106 X-Body-Size: 2551 X-Received-Count: 1 X-Recipient-Count: 1 X-Local-Recipient-Count: 1 X-Local-Recipient-Defer-Count: 0 X-Local-Recipient-Fail-Count: 0 Subject: Re: Burning DVD with files>4GB from console 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: Fri, 05 Dec 2008 08:33:02 -0000 David Kelly pisze: > On Thu, Dec 04, 2008 at 10:48:54AM +0100, Bartosz Stec wrote: > >> My backup script split filesystem dumps to files with size of 4,37 GB (4 >> 588 544 kB). It's just an optimal size to fill out DVDs. At this moment >> I have to burn them from windows via smb-link becuase I didn't manage to >> do this task from FreeBSD console due to 2GB/4GB filesize restrictions >> (growisofs). >> > > Since when did FreeBSD (or growisofs) have a 2GB/4GB filesize limit? I > have burned 4.3GB DVDs several times. > > Just look, here is example: fbsd# growisofs -Z /dev/cd0 -R -J -udf -iso-level 3 -dry-run somefile Executing 'mkisofs -R -J -udf -iso-level 3 somefile | builtin_dd of=/dev/pass0 obs=32k seek=0' mkisofs: Value too large to be stored in data type. File somefile is too large - ignoring I'm not talking about restriction of DVD size, but restriction to filesize wchich I want to place on DVD: fbsd# cat somefile | split -b 2G fbsd# rm somefile fbsd# ls -lh total 4590848 -rw-r--r-- 1 root operator 2,0G 5 gru 09:18 xaa -rw-r--r-- 1 root operator 2,0G 5 gru 09:24 xab -rw-r--r-- 1 root operator 385M 5 gru 09:26 xac fbsd# growisofs -v -Z /dev/cd0 -R -J -udf -dry-run ./ Executing 'mkisofs -v -R -J -udf ./ | builtin_dd of=/dev/pass0 obs=32k seek=0' mkisofs 2.01 (i386-unknown-freebsd7.0) Scanning ./ Writing: Initial Padblock Start Block 0 Done with: Initial Padblock Block(s) 16 Writing: Primary Volume Descriptor Start Block 16 Done with: Primary Volume Descriptor Block(s) 1 Writing: Joliet Volume Descriptor Start Block 17 Done with: Joliet Volume Descriptor Block(s) 1 Writing: End Volume Descriptor Start Block 18 Done with: End Volume Descriptor Block(s) 1 Writing: UDF volume recognition area Start Block 19 Done with: UDF volume recognition area Block(s) 3 Writing: Version block Start Block 22 Done with: Version block Block(s) 1 Writing: UDF pad to sector 32 Start Block 23 Done with: UDF pad to sector 32 Block(s) 9 Writing: UDF main seq Start Block 32 When I split that file there are no errors and DVD is 4,3GB size. -- Bartosz Stec From owner-freebsd-stable@FreeBSD.ORG Fri Dec 5 09:00:30 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F27961065676 for ; Fri, 5 Dec 2008 09:00:30 +0000 (UTC) (envelope-from admin@kkip.pl) Received: from mainframe.kkip.pl (kkip.pl [87.105.164.78]) by mx1.freebsd.org (Postfix) with ESMTP id 9F9F58FC1E for ; Fri, 5 Dec 2008 09:00:30 +0000 (UTC) (envelope-from admin@kkip.pl) Received: from admin.admin.lan.kkip.pl ([10.66.3.254]) by mainframe.kkip.pl with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1L8WXy-0006n1-RX for freebsd-stable@freebsd.org; Fri, 05 Dec 2008 10:00:29 +0100 Message-ID: <4938EDAB.70809@kkip.pl> Date: Fri, 05 Dec 2008 10:00:27 +0100 From: Bartosz Stec User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <4937A786.9080403@kkip.pl> <20081204154507.GA18645@Grumpy.DynDNS.org> <493801F5.2050009@math.missouri.edu> <493816EE.8010408@comcast.net> <20081204191957.GA32007@Grumpy.DynDNS.org> In-Reply-To: <20081204191957.GA32007@Grumpy.DynDNS.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated-User: admin@kkip.pl X-Authenticator: plain X-Sender-Verify: SUCCEEDED (sender exists & accepts mail) X-Spam-Score: -8.9 X-Spam-Score-Int: -88 X-Exim-Version: 4.69 (build at 01-Nov-2008 10:39:57) X-Date: 2008-12-05 10:00:29 X-Connected-IP: 10.66.3.254:1870 X-Message-Linecount: 58 X-Body-Linecount: 45 X-Message-Size: 2533 X-Body-Size: 1869 X-Received-Count: 1 X-Recipient-Count: 1 X-Local-Recipient-Count: 1 X-Local-Recipient-Defer-Count: 0 X-Local-Recipient-Fail-Count: 0 Subject: Re: Burning DVD with files>4GB from console 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: Fri, 05 Dec 2008 09:00:31 -0000 David Kelly pisze: > On Thu, Dec 04, 2008 at 12:44:14PM -0500, Steve Polyack wrote: > >> Not too say you're .iso images can't be >2GB/4GB, but I'm pretty sure >> the ISO9660 standard is limited to a 2GB maximum file size (for files >> within the .iso). You must use UDF to burn files of greater size. >> mkisofs(8) seems to support this, if only in alpha/hybrid stage: >> >> -udf Include UDF support in the generated filesystem image. UDF sup- >> port is currently in alpha status and for this reason, it is not >> possible to create UDF only images. >> > > It would seem then that the O.P. who is already splitting his backup > into 4.3GB chunks should split backups into sub-2GB chunks. > 4,700,000,000 is the standard DVD size, I'd shoot for chunks of 4.5E9/3 > so as to have about 200MB of headroom per DVD. > > growisofs will write 3 files to the DVD just as easily as one. The magic > of growisofs is that it invokes mkisofs on the fly. And also that > cdrecord had obnoxious (and broken) licensing in years past when I last > tried it. > > Yes, I know that. My reasons for keeping one file on DVD are just for making my life easier. If I want to restore some files from filesystem backup (they are made via pipeline dump | gunzip | split) I have to copy all files from DVDs wchich includes needed filesystem and then I type: cat file1 file2 file3 ... fileN | gunzip | restore -if - And yes, I know that tapes are much better for tasks like this but for now I just have to use DVDs :) Now imagine backup placed on 10 DVDs. With single file on DVD I have 10 files to manage, not 30. I know there're workarounds but with more files I probably will need some script to restore files rather than do it manually. That's the reason I asked if there's a possibility to burn it this way from FreeBSD. -- Bartosz Stec From owner-freebsd-stable@FreeBSD.ORG Fri Dec 5 09:02:13 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6EF6C106564A for ; Fri, 5 Dec 2008 09:02:13 +0000 (UTC) (envelope-from admin@kkip.pl) Received: from mainframe.kkip.pl (kkip.pl [87.105.164.78]) by mx1.freebsd.org (Postfix) with ESMTP id 1E2E78FC19 for ; Fri, 5 Dec 2008 09:02:13 +0000 (UTC) (envelope-from admin@kkip.pl) Received: from admin.admin.lan.kkip.pl ([10.66.3.254]) by mainframe.kkip.pl with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1L8WZd-0006nL-Bv for freebsd-stable@freebsd.org; Fri, 05 Dec 2008 10:02:12 +0100 Message-ID: <4938EE12.4060609@kkip.pl> Date: Fri, 05 Dec 2008 10:02:10 +0100 From: Bartosz Stec User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: FreeBSD Stable References: <4937A786.9080403@kkip.pl> <20081204154507.GA18645@Grumpy.DynDNS.org> <493801F5.2050009@math.missouri.edu> In-Reply-To: <493801F5.2050009@math.missouri.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated-User: admin@kkip.pl X-Authenticator: plain X-Sender-Verify: SUCCEEDED (sender exists & accepts mail) X-Spam-Score: -8.9 X-Spam-Score-Int: -88 X-Exim-Version: 4.69 (build at 01-Nov-2008 10:39:57) X-Date: 2008-12-05 10:02:12 X-Connected-IP: 10.66.3.254:1871 X-Message-Linecount: 37 X-Body-Linecount: 24 X-Message-Size: 1505 X-Body-Size: 902 X-Received-Count: 1 X-Recipient-Count: 1 X-Local-Recipient-Count: 1 X-Local-Recipient-Defer-Count: 0 X-Local-Recipient-Fail-Count: 0 Subject: Re: Burning DVD with files>4GB from console 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: Fri, 05 Dec 2008 09:02:13 -0000 Stephen Montgomery-Smith pisze: > David Kelly wrote: >> On Thu, Dec 04, 2008 at 10:48:54AM +0100, Bartosz Stec wrote: >>> My backup script split filesystem dumps to files with size of 4,37 >>> GB (4 588 544 kB). It's just an optimal size to fill out DVDs. At >>> this moment I have to burn them from windows via smb-link becuase I >>> didn't manage to do this task from FreeBSD console due to 2GB/4GB >>> filesize restrictions (growisofs). >> >> Since when did FreeBSD (or growisofs) have a 2GB/4GB filesize limit? I >> have burned 4.3GB DVDs several times. > > I never had a problem writing huge files. But I did have a problem > subsequently reading it with Windows XP. Maybe the file size > restriction is a Windows thing. Nope. I am burning my backups from Windows, and they're readable both from Windows and FreeBSD. FreeBSD just doesn't let me burn them directly :) -- Bartosz Stec From owner-freebsd-stable@FreeBSD.ORG Fri Dec 5 09:02:51 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B77C7106567C for ; Fri, 5 Dec 2008 09:02:51 +0000 (UTC) (envelope-from admin@kkip.pl) Received: from mainframe.kkip.pl (kkip.pl [87.105.164.78]) by mx1.freebsd.org (Postfix) with ESMTP id 664C38FC25 for ; Fri, 5 Dec 2008 09:02:51 +0000 (UTC) (envelope-from admin@kkip.pl) Received: from admin.admin.lan.kkip.pl ([10.66.3.254]) by mainframe.kkip.pl with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1L8WaG-0006nd-94 for freebsd-stable@freebsd.org; Fri, 05 Dec 2008 10:02:50 +0100 Message-ID: <4938EE38.2000504@kkip.pl> Date: Fri, 05 Dec 2008 10:02:48 +0100 From: Bartosz Stec User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: FreeBSD Stable References: <4937A786.9080403@kkip.pl> <20081204154507.GA18645@Grumpy.DynDNS.org> <493801F5.2050009@math.missouri.edu> <493816EE.8010408@comcast.net> In-Reply-To: <493816EE.8010408@comcast.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated-User: admin@kkip.pl X-Authenticator: plain X-Sender-Verify: SUCCEEDED (sender exists & accepts mail) X-Spam-Score: -8.9 X-Spam-Score-Int: -88 X-Exim-Version: 4.69 (build at 01-Nov-2008 10:39:57) X-Date: 2008-12-05 10:02:50 X-Connected-IP: 10.66.3.254:1872 X-Message-Linecount: 33 X-Body-Linecount: 20 X-Message-Size: 1219 X-Body-Size: 591 X-Received-Count: 1 X-Recipient-Count: 1 X-Local-Recipient-Count: 1 X-Local-Recipient-Defer-Count: 0 X-Local-Recipient-Fail-Count: 0 Subject: Re: Burning DVD with files>4GB from console 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: Fri, 05 Dec 2008 09:02:51 -0000 Steve Polyack pisze: > Not too say you're .iso images can't be >2GB/4GB, but I'm pretty sure > the ISO9660 standard is limited to a 2GB maximum file size (for files > within the .iso). You must use UDF to burn files of greater size. > mkisofs(8) seems to support this, if only in alpha/hybrid stage: > > -udf Include UDF support in the generated filesystem image. > UDF sup- > port is currently in alpha status and for this reason, it > is not > possible to create UDF only images. > Indeed. I'm using -udf switch, no success. -- Bartosz Stec From owner-freebsd-stable@FreeBSD.ORG Fri Dec 5 09:23:37 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A52CD1065673 for ; Fri, 5 Dec 2008 09:23:37 +0000 (UTC) (envelope-from admin@kkip.pl) Received: from mainframe.kkip.pl (kkip.pl [87.105.164.78]) by mx1.freebsd.org (Postfix) with ESMTP id 4EBAE8FC1E for ; Fri, 5 Dec 2008 09:23:37 +0000 (UTC) (envelope-from admin@kkip.pl) Received: from admin.admin.lan.kkip.pl ([10.66.3.254]) by mainframe.kkip.pl with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1L8WuL-0006tQ-CP; Fri, 05 Dec 2008 10:23:36 +0100 Message-ID: <4938F316.9010403@kkip.pl> Date: Fri, 05 Dec 2008 10:23:34 +0100 From: Bartosz Stec User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: Bob Johnson References: <4937A786.9080403@kkip.pl> <4937CBBC.1020406@smo.de> <4937D26D.60408@kkip.pl> <54db43990812041614h62f2608bua8462341a59c8626@mail.gmail.com> In-Reply-To: <54db43990812041614h62f2608bua8462341a59c8626@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated-User: admin@kkip.pl X-Authenticator: plain X-Sender-Verify: SUCCEEDED (sender exists & accepts mail) X-Spam-Score: -8.9 X-Spam-Score-Int: -88 X-Exim-Version: 4.69 (build at 01-Nov-2008 10:39:57) X-Date: 2008-12-05 10:23:36 X-Connected-IP: 10.66.3.254:1925 X-Message-Linecount: 84 X-Body-Linecount: 70 X-Message-Size: 3320 X-Body-Size: 2621 X-Received-Count: 1 X-Recipient-Count: 2 X-Local-Recipient-Count: 2 X-Local-Recipient-Defer-Count: 0 X-Local-Recipient-Fail-Count: 0 Cc: FreeBSD Stable Subject: Re: Burning DVD with files>4GB from console 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: Fri, 05 Dec 2008 09:23:37 -0000 Bob Johnson pisze: > On 12/4/08, Bartosz Stec wrote: > >> Philipp Ost pisze: >> >>> Hi, >>> >>> Bartosz Stec wrote: >>> >>>> [...] Is there *any* way to burn DVDs with files>4GB from FreeBSD >>>> console? >>>> >>> I succesfully used growisofs for exactly this task ;-) >>> >>> What I did is (for DL-DVDs): >>> # growisofs -dvd-compat -Z /dev/cd0=$file.iso -speed=2 >>> >>> I had to limit the speed, else it wouldn't do anything. If I burn >>> "normal" DVDs I don't need the speed limit. >>> >>> HTH, >>> Philipp >>> >> But doesn't that command expecting file.iso being already premastered >> ISO image? OK, that's *some* way, but to be clear - I want to avoid >> preparing ISO images too ;) >> >> > > Some thoughts that might be useful: > > 1) I expect the problem is with mkisofs version 2.01 that is used in > FreeBSD (at least in 7.0), but I haven't attempted to confirm this. > Growisofs is supposed to handle large files, and so are recent > versions of mkisofs. The author of mkisofs considers 2.01 to be > obsolete. Perhaps installing a newer mkisofs is the solution (e.g. > sysutils/cdrtools-devel appears to be fairly recent)? > > 2) Perhaps you could do what I do and write tar files directly to DVD > with no filesystem. I use burncd to write the file to the DVD, but I > don't remember if I've tried to exceed 4 GiB per file. You might need > growisofs in premastered image mode instead of burncd. To read the > file later use something like 'tar -xf /dev/cd0'. Might have a > problem with this in Windows, but maybe that's not really a problem? > > 3) You could modify your script to use mkisofs to create the ISO image > as part of the process of splitting your files into (smaller) chunks. > Then use growisofs in premastered image mode, as already suggested. If > you want to do this, look at the -stream-media-size option in mkisofs. > > 4) The 4 GiB limit on file size is built into the ISO 9660 filesystem > prior to Level 3. Level 3 allows larger files by allowing files to > have multiple extents (each extent must still be < 4 GiB). You may > need to explicitly specify ISO Level 3 to get the correct behavior > (i.e. use the '-iso-level 3' option with growisofs or mkisofs). > > > -- Bob Johnson > fbsdlists@gmail.com > _______________________________________________ > 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" > Thanks a lot! Upgrading to sysutils/cdrtools-devel solves my problem! :) -- Bartosz Stec From owner-freebsd-stable@FreeBSD.ORG Fri Dec 5 10:04:57 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ABB001065672; Fri, 5 Dec 2008 10:04:57 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 6D8828FC1A; Fri, 5 Dec 2008 10:04:57 +0000 (UTC) (envelope-from des@des.no) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id B8EC56D44E; Fri, 5 Dec 2008 10:04:56 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id 9D6648448C; Fri, 5 Dec 2008 11:04:56 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Andriy Gapon References: <49300020.6060603@icyb.net.ua> <49382449.80002@icyb.net.ua> Date: Fri, 05 Dec 2008 11:04:56 +0100 In-Reply-To: <49382449.80002@icyb.net.ua> (Andriy Gapon's message of "Thu, 04 Dec 2008 20:41:13 +0200") Message-ID: <86wsefgcon.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org, FreeBSD Stable Subject: Re: ichwd problem: watchdog doesn't "bark" 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: Fri, 05 Dec 2008 10:04:57 -0000 Andriy Gapon writes: > When I start watchdogd I see the following messages: > timer enabled > timeout set to 28 ticks > and then a flow of messages: > timer reloaded >=20 > Then I kill -9 watchdogd. > "timer reloded" messages are no longer produced. > And there are no other messages. >=20 > But nothing happens for many minutes that I waited. The watchdog may be disabled, either in hardware or by the BIOS at boot time, but the driver should have detected that. It is also possible that the BIOS catches the SMI but ignores it. > BTW, can someone knowledgeable tell me if watchdog better be firing SMI > or NMI when it runs down? It should fire SMI, IIRC. Read the comments at the top of the code for references to the relevant Intel documentation, which you can download for free. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-stable@FreeBSD.ORG Fri Dec 5 10:11:19 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 425791065670; Fri, 5 Dec 2008 10:11:19 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id D75068FC1A; Fri, 5 Dec 2008 10:11:18 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 306B11CC6B8; Fri, 5 Dec 2008 05:11:18 -0500 (EST) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Fri, 05 Dec 2008 05:11:18 -0500 X-Sasl-enc: uxwnbMegg1OLlKySK7psLPt+G9idZ3/wtHdW0QEucwc7 1228471877 Received: from empiric.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTPSA id 8157BC311; Fri, 5 Dec 2008 05:11:17 -0500 (EST) Message-ID: <4938FE44.9090608@FreeBSD.org> Date: Fri, 05 Dec 2008 10:11:16 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 2.0.0.14 (X11/20080514) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <8cb6106e0811241129o642dcf28re4ae177c8ccbaa25@mail.gmail.com> <20081125150342.GL2042@deviant.kiev.zoral.com.ua> <8cb6106e0812031453j6dc2f2f4i374145823c084eaa@mail.gmail.com> <200812041747.09040.gnemmi@gmail.com> In-Reply-To: <200812041747.09040.gnemmi@gmail.com> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: josh.carroll@gmail.com, freebsd-fs@freebsd.org Subject: ext2fuse: user-space ext2 implementation 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: Fri, 05 Dec 2008 10:11:19 -0000 Hi, I just tested the ext2fuse project on FreeBSD 7.1-PRERELEASE as of today and found that it works for read/write on an ext3 filesystem. The inode size was 128 -- I haven't exercised dynamic inode sizes. ext2fuse project: http://sourceforge.net/projects/ext2fuse Required FreeBSD patches: http://people.freebsd.org/~bms/dump/ext2fuse-freebsd.patch Steps: 1. fetch http://ovh.dl.sourceforge.net/sourceforge/ext2fuse/ext2fuse-src-0.8.1.tar.gz 2. tar xvf ext2fuse-src-0.8.1.tar.gz 3. patch -i ext2fuse-0.8.1-freebsd.patch 4. cd ext2fuse-src-0.8.1 5. aclocal ; automake ; autoconf 6. ./configure && gmake Performance seems quite slow, it could probably benefit from being ported to use UBLIO as ntfs-3g for FreeBSD has. I'm going to leave this thing for others to play with, this was a 20 minute bunk-off from other work. It shouldn't take much effort to create a port around it. cheers BMS From owner-freebsd-stable@FreeBSD.ORG Fri Dec 5 10:35:58 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D8FA81065676 for ; Fri, 5 Dec 2008 10:35:58 +0000 (UTC) (envelope-from Joerg.Schilling@fokus.fraunhofer.de) Received: from iron02.fraunhofer.de (iron02.fraunhofer.de [153.96.1.56]) by mx1.freebsd.org (Postfix) with ESMTP id 6FE7B8FC14 for ; Fri, 5 Dec 2008 10:35:58 +0000 (UTC) (envelope-from Joerg.Schilling@fokus.fraunhofer.de) Received: from pluto.fokus.fraunhofer.de ([195.37.77.164]) by iron02.fraunhofer.de with ESMTP/TLS/DHE-RSA-AES256-SHA; 05 Dec 2008 11:06:07 +0100 Received: from EXCHSRV.fokus.fraunhofer.de (bohr [10.147.9.231]) by pluto.fokus.fraunhofer.de (8.13.7/8.13.7) with SMTP id mB5A67Jp000353 for ; Fri, 5 Dec 2008 11:06:07 +0100 (MET) Received: from rigel ([10.147.65.195]) by EXCHSRV.fokus.fraunhofer.de with Microsoft SMTPSVC(6.0.3790.3959); Fri, 5 Dec 2008 11:06:07 +0100 Date: Fri, 05 Dec 2008 11:06:03 +0100 From: Joerg.Schilling@fokus.fraunhofer.de (Joerg Schilling) To: freebsd-stable@freebsd.org Message-ID: <4938fd0b.OhN+VuuHXZBfyAPp%Joerg.Schilling@fokus.fraunhofer.de> User-Agent: nail 11.22 3/20/05 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-OriginalArrivalTime: 05 Dec 2008 10:06:07.0213 (UTC) FILETIME=[170C51D0:01C956C1] Subject: Re: Burning DVD with files>4GB from console 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: Fri, 05 Dec 2008 10:35:59 -0000 >My backup script split filesystem dumps to files with size of 4,37 GB (4 >588 544 kB). It's just an optimal size to fill out DVDs. At this moment >I have to burn them from windows via smb-link becuase I didn't manage to >do this task from FreeBSD console due to 2GB/4GB filesize restrictions >(growisofs). I'm using freeware CDBurnerXP to burn my backups What "limitations" are you thinking of? Growisofs is based on mkisofs which is part of cdrtools. Mkisofs supports large files since a long time (~ 8 years). >I never had a problem writing huge files. But I did have a problem >subsequently reading it with Windows XP. Maybe the file size >restriction is a Windows thing. >From the information I have, MS-WIN handles large files correctly. What problems do you have? >Not too say you're .iso images can't be >2GB/4GB, but I'm pretty sure >the ISO9660 standard is limited to a 2GB maximum file size (for files >within the .iso). You must use UDF to burn files of greater size. >mkisofs(8) seems to support this, if only in alpha/hybrid stage: The ISO-9660 standard is limited to 8 TB for the max. filesystem size as well as for the size of a single file. Mkisofs supports single files up to 4 GB since ~ Y2000 and it suppports files up to 8 TB since 2 years. >growisofs will write 3 files to the DVD just as easily as one. The magic >of growisofs is that it invokes mkisofs on the fly. And also that >cdrecord had obnoxious (and broken) licensing in years past when I last >tried it. Cdrecord alwas had and still has a free license. There is nothing broken with cdrtools/cdrecord. There is however a big social problem with the anti-social habbit and propaganda from Debian. Fortunately, cdrtools is not related to Debian, so where is your problem? Growisofs depends on mkisofs and mkisofs is part of cdrtools, so you need cdrtools anyway. >1) I expect the problem is with mkisofs version 2.01 that is used in >FreeBSD (at least in 7.0), but I haven't attempted to confirm this. >Growisofs is supposed to handle large files, and so are recent >versions of mkisofs. The author of mkisofs considers 2.01 to be >obsolete. Perhaps installing a newer mkisofs is the solution (e.g. >sysutils/cdrtools-devel appears to be fairly recent)? mkisofs-2.01 is more than 4 years old. It is not just obsolete but extremely outdated. Since mkisofs-2.01 30-50% of the code has been replaced or added. Cdrtools is only a few weeks from the next major release and it would be silly not to use a recent version. Jörg -- EMail:joerg@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin js@cs.tu-berlin.de (uni) schilling@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily From owner-freebsd-stable@FreeBSD.ORG Fri Dec 5 11:40:49 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F3ADB1065677; Fri, 5 Dec 2008 11:40:48 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id C806D8FC0C; Fri, 5 Dec 2008 11:40:48 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from compute2.internal (compute2.internal [10.202.2.42]) by out1.messagingengine.com (Postfix) with ESMTP id 1D0CB1CDBB4; Fri, 5 Dec 2008 06:40:48 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute2.internal (MEProxy); Fri, 05 Dec 2008 06:40:48 -0500 X-Sasl-enc: qlQqapjSLEkhsayyjDNOojkbOD9Qnp5XB4JCwfnh5gJ9 1228477247 Received: from empiric.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTPSA id 8048830C5F; Fri, 5 Dec 2008 06:40:47 -0500 (EST) Message-ID: <4939133E.2000701@FreeBSD.org> Date: Fri, 05 Dec 2008 11:40:46 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 2.0.0.14 (X11/20080514) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <8cb6106e0811241129o642dcf28re4ae177c8ccbaa25@mail.gmail.com> <20081125150342.GL2042@deviant.kiev.zoral.com.ua> <8cb6106e0812031453j6dc2f2f4i374145823c084eaa@mail.gmail.com> <200812041747.09040.gnemmi@gmail.com> <4938FE44.9090608@FreeBSD.org> In-Reply-To: <4938FE44.9090608@FreeBSD.org> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: josh.carroll@gmail.com, freebsd-fs@freebsd.org Subject: Re: ext2fuse: user-space ext2 implementation 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: Fri, 05 Dec 2008 11:40:49 -0000 Bruce M. Simpson wrote: > ... > Performance seems quite slow, it could probably benefit from being > ported to use UBLIO as ntfs-3g for FreeBSD has. > > I'm going to leave this thing for others to play with, this was a 20 > minute bunk-off from other work. It shouldn't take much effort to > create a port around it. P.S. Ale's patch to use libublio for fusefs-ntfs is here, if anyone picks up on ext2fuse before I do: http://people.freebsd.org/~alepulver/fusefs-ntfs.diff This contains the necessary diffs for UBLIO. cheers BMS From owner-freebsd-stable@FreeBSD.ORG Fri Dec 5 11:41:34 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C5E23106567D for ; Fri, 5 Dec 2008 11:41:34 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id 979C28FC19 for ; Fri, 5 Dec 2008 11:41:34 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 42A061CAA85; Fri, 5 Dec 2008 06:41:34 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Fri, 05 Dec 2008 06:41:34 -0500 X-Sasl-enc: 090N2utzmGgNHcTNCVjFvI+Nk52L038WV9uD3R+eT3a3 1228477293 Received: from empiric.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTPSA id 7F35135418; Fri, 5 Dec 2008 06:41:33 -0500 (EST) Message-ID: <4939136C.3000500@incunabulum.net> Date: Fri, 05 Dec 2008 11:41:32 +0000 From: Bruce M Simpson User-Agent: Thunderbird 2.0.0.14 (X11/20080514) MIME-Version: 1.0 To: FreeBSD stable X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Matteo Riondato , Konstantin Belousov Subject: Issues with mount(8) and FUSE in 7.1-PRERELEASE 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: Fri, 05 Dec 2008 11:41:34 -0000 Hi all, I noticed when porting ext2fuse to run on 7.1-PRERELEASE, that the port sysutils/fusefs-ntfs needs some additional steps in order to mount user-space FUSE filesystems on startup. These steps weren't necessary in 6.x. It seems mount(8) can't deal with new mount binaries unless it has been explicitly built with support for them; please see /usr/local/share/doc/ntfs-3g/README.FreeBSD for more info where the problem is described in more detail. There is a comment which reads as follows in the mount.c code: /* XXX: We need to get away from implementing external mount * programs for every filesystem, and move towards having * each filesystem properly implement the nmount() system call. */ Unfortunately, this assumption seems to be grounded in a very restricted picture of the filesystem world. FUSE is clearly something which doesn't fit a limited use case of "let's only mount stuff which the FreeBSD base system supports", and, to my mind, is applicable to the vast majority of FreeBSD desktop users. This seems like an inflexible approach, and I'm curious why this design choice persists. I understand the technical arguments for nmount() and I do support them, but not at the expense of functional utility. How can we make this work for users out-of-the-box? thanks, BMS P.S. There is a patch by Ale Pulver to change some of this hardcoded logic, however it doesn't seem complete: http://people.freebsd.org/~alepulver/current-7.0-mount.diff From owner-freebsd-stable@FreeBSD.ORG Fri Dec 5 12:34:23 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 67AB21065677 for ; Fri, 5 Dec 2008 12:34:23 +0000 (UTC) (envelope-from bseklecki@collaborativefusion.com) Received: from collaborativefusion.com (mx01.pub.collaborativefusion.com [206.210.89.201]) by mx1.freebsd.org (Postfix) with ESMTP id 141858FC1A for ; Fri, 5 Dec 2008 12:34:22 +0000 (UTC) (envelope-from bseklecki@collaborativefusion.com) Received: from Internal Mail-Server by mx01 (envelope-from bseklecki@collaborativefusion.com) with SMTP; 5 Dec 2008 07:34:21 -0500 From: "Brian A. Seklecki" To: Peter Jeremy In-Reply-To: <20080812120307.GD64458@server.vk2pj.dyndns.org> References: <20080812120307.GD64458@server.vk2pj.dyndns.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-7zVPQTw3Vkq94LWlaKHr" Organization: Collaborative Fusion, Inc. Date: Fri, 05 Dec 2008 07:34:21 -0500 Message-Id: <1228480461.2805.469.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 (2.22.3.1-1.fc9) Cc: stable@freebsd.org, eugen@kuzbass.ru, Pete French , Marian Hettwer Subject: Re: lagg(4) and failover X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bseklecki@collaborativefusion.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Dec 2008 12:34:23 -0000 --=-7zVPQTw3Vkq94LWlaKHr Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Tue, 2008-08-12 at 22:03 +1000, Peter Jeremy wrote: > >Thats unfortunate... >=20 > I tend to agree. >=20 > >bonding in Linux is capable of doing this and solaris too. >=20 Well ... name a price for the development; HA L1/L2 is a feature the community would gladly sponsor the development of. Also, Peter, you should put a page up on the FreeBSD wiki with some of those multi-catalyst LACP IOS config examples. =20 Maybe write an article for BSDMag. I always just counted that idea out (LACP against two switches) since LACP doesn't have any inter-component transport protocol a la pfsync(4). But if the backplanes of Cat 37xx`s can be merged at a lower level, then then yea, fuck. Lets have it. ~BAS=20 P.S., in my experience, system level redundancy/HA with a load balancer is almost always less expensive then excessive component-level redundancy/ha (RAID Disk, RAID RAM, Dual Power Supplies, Dual Backplanes...) > It shouldn't be too difficult to create something that behaves > functionally similarly to Slowaris ipmpd (and with marginally more > effort, you could create something that could be configured to behave > sensibly). --=20 Brian A. Seklecki Collaborative Fusion, Inc. --=-7zVPQTw3Vkq94LWlaKHr Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEABECAAYFAkk5H80ACgkQCne6BNDQ+R9sWwCdEs4oicCy15n+VrJ+uFEqbIYz xXMAmwTAUPy6BTLDWKi73gi3fzbDWYQm =SypL -----END PGP SIGNATURE----- --=-7zVPQTw3Vkq94LWlaKHr-- From owner-freebsd-stable@FreeBSD.ORG Fri Dec 5 19:11:06 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6A4391065673 for ; Fri, 5 Dec 2008 19:11:06 +0000 (UTC) (envelope-from frode@nordahl.net) Received: from smtp3.powertech.no (smtp3.powertech.no [195.159.0.178]) by mx1.freebsd.org (Postfix) with ESMTP id B82408FC16 for ; Fri, 5 Dec 2008 19:11:05 +0000 (UTC) (envelope-from frode@nordahl.net) Received: from dhcp3.xu.nordahl.net (dhcp3.xu.nordahl.net [195.159.148.122]) by smtp3.powertech.no (Postfix) with ESMTP id 2A286C6179; Fri, 5 Dec 2008 20:11:04 +0100 (CET) Message-Id: From: Frode Nordahl To: Kostik Belousov In-Reply-To: <576BB990-78D8-4CE8-9660-55EB989EE3BA@nordahl.net> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Date: Fri, 5 Dec 2008 20:11:02 +0100 References: <3B675385-956D-4A26-8E09-E338DF7D7244@nordahl.net> <20081203173939.GA2401@deviant.kiev.zoral.com.ua> <20081203194348.GB2401@deviant.kiev.zoral.com.ua> <8A6A8FA5-07A6-4A12-B9AD-6E77E534CED7@nordahl.net> <20081204120736.GC2038@deviant.kiev.zoral.com.ua> <576BB990-78D8-4CE8-9660-55EB989EE3BA@nordahl.net> X-Mailer: Apple Mail (2.929.2) Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 7.1-PRERELEASE-p1, panic: dqget: free dquot isn't 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: Fri, 05 Dec 2008 19:11:06 -0000 On 4. des.. 2008, at 13.20, Frode Nordahl wrote: > On 4. des.. 2008, at 13.07, Kostik Belousov wrote: > >> On Thu, Dec 04, 2008 at 08:12:45AM +0100, Frode Nordahl wrote: >>> Got it! >>> >>> panic: dqget: free dquot isn't dq=0xffffff00b3d27000 >>> (kgdb) p/x *(struct dquot *)0xffffff00b3d27000 >>> $1 = {dq_hash = {le_next = 0x0, le_prev = 0xffffff010b9da700}, >>> dq_freelist = { >>> tqe_next = 0xffffff0055e2de00, tqe_prev = 0xffffffff80b03710}, >>> dq_lock = { >>> lock_object = {lo_name = 0xffffffff8088c21c, lo_type = >>> 0xffffffff8088c21c, >>> lo_flags = 0x1030000, lo_witness_data = {lod_list = {stqe_next >>> = 0x0}, >>> lod_witness = 0x0}}, mtx_lock = 0x4, mtx_recurse = 0x0}, >>> dq_flags = 0xc, dq_type = 0x0, dq_cnt = 0x0, dq_id = 0x16a37d, >>> dq_ump = 0xffffff00038e1600, dq_dqb = {dqb_bhardlimit = 0x0, >>> dqb_bsoftlimit = 0x0, dqb_curblocks = 0x0, dqb_ihardlimit = 0x0, >>> dqb_isoftlimit = 0x0, dqb_curinodes = 0x1, dqb_btime = 0x493ef2b5, >>> dqb_itime = 0x493ef2b5}} >>> >>> Let me know if I can provide any more information! >>> >>> Updated the crashinfo archive you got an URL to yesterday if you >>> want >>> to poke around yourself. >> >> Please, try the patch below, it should fix a race I see. Quite >> possible, >> this is what you tripped over. > > Thanks! I will apply the patch and retry the steps that lead to the > panic! Good news! I have run through two and have started on the third iteration of the test that lead to the panic without your patch, and no panic so far! I will let it run through the weekend, it prooves usefull as a burn-in- test as well :-) Will this patch make it into 7.1-RELEASE? -- Frode Nordahl From owner-freebsd-stable@FreeBSD.ORG Fri Dec 5 19:59:32 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9767F1065670 for ; Fri, 5 Dec 2008 19:59:32 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.terabit.net.ua (mail.terabit.net.ua [195.137.202.147]) by mx1.freebsd.org (Postfix) with ESMTP id 37E378FC13 for ; Fri, 5 Dec 2008 19:59:32 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from skuns.zoral.com.ua ([91.193.166.194] helo=mail.zoral.com.ua) by mail.terabit.net.ua with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1L8gpm-0000Rv-DZ; Fri, 05 Dec 2008 21:59:30 +0200 Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id mB5JxMDx090888 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 5 Dec 2008 21:59:23 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id mB5JxMUk039843; Fri, 5 Dec 2008 21:59:22 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id mB5JxMG1039841; Fri, 5 Dec 2008 21:59:22 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Fri, 5 Dec 2008 21:59:22 +0200 From: Kostik Belousov To: Frode Nordahl Message-ID: <20081205195922.GP2038@deviant.kiev.zoral.com.ua> References: <3B675385-956D-4A26-8E09-E338DF7D7244@nordahl.net> <20081203173939.GA2401@deviant.kiev.zoral.com.ua> <20081203194348.GB2401@deviant.kiev.zoral.com.ua> <8A6A8FA5-07A6-4A12-B9AD-6E77E534CED7@nordahl.net> <20081204120736.GC2038@deviant.kiev.zoral.com.ua> <576BB990-78D8-4CE8-9660-55EB989EE3BA@nordahl.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="MM5RgFPKyuP3gDcV" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: ClamAV version 0.93.3, clamav-milter version 0.93.3 on skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua X-Virus-Scanned: mail.terabit.net.ua 1L8gpm-0000Rv-DZ 0ed6f0a30ab670d6eff3dd605d84f5ff X-Terabit: YES Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 7.1-PRERELEASE-p1, panic: dqget: free dquot isn't 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: Fri, 05 Dec 2008 19:59:32 -0000 --MM5RgFPKyuP3gDcV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Dec 05, 2008 at 08:11:02PM +0100, Frode Nordahl wrote: >=20 > On 4. des.. 2008, at 13.20, Frode Nordahl wrote: >=20 > >On 4. des.. 2008, at 13.07, Kostik Belousov wrote: > > > >>On Thu, Dec 04, 2008 at 08:12:45AM +0100, Frode Nordahl wrote: > >>>Got it! > >>> > >>>panic: dqget: free dquot isn't dq=3D0xffffff00b3d27000 > >>>(kgdb) p/x *(struct dquot *)0xffffff00b3d27000 > >>>$1 =3D {dq_hash =3D {le_next =3D 0x0, le_prev =3D 0xffffff010b9da700}, > >>>dq_freelist =3D { > >>> tqe_next =3D 0xffffff0055e2de00, tqe_prev =3D 0xffffffff80b03710}, > >>>dq_lock =3D { > >>> lock_object =3D {lo_name =3D 0xffffffff8088c21c, lo_type =3D > >>>0xffffffff8088c21c, > >>> lo_flags =3D 0x1030000, lo_witness_data =3D {lod_list =3D {stqe_ne= xt > >>>=3D 0x0}, > >>> lod_witness =3D 0x0}}, mtx_lock =3D 0x4, mtx_recurse =3D 0x0}, > >>>dq_flags =3D 0xc, dq_type =3D 0x0, dq_cnt =3D 0x0, dq_id =3D 0x16a37d, > >>>dq_ump =3D 0xffffff00038e1600, dq_dqb =3D {dqb_bhardlimit =3D 0x0, > >>> dqb_bsoftlimit =3D 0x0, dqb_curblocks =3D 0x0, dqb_ihardlimit =3D 0x= 0, > >>> dqb_isoftlimit =3D 0x0, dqb_curinodes =3D 0x1, dqb_btime =3D 0x493ef= 2b5, > >>> dqb_itime =3D 0x493ef2b5}} > >>> > >>>Let me know if I can provide any more information! > >>> > >>>Updated the crashinfo archive you got an URL to yesterday if you =20 > >>>want > >>>to poke around yourself. > >> > >>Please, try the patch below, it should fix a race I see. Quite =20 > >>possible, > >>this is what you tripped over. > > > >Thanks! I will apply the patch and retry the steps that lead to the =20 > >panic! >=20 >=20 > Good news! I have run through two and have started on the third =20 > iteration of the test that lead to the panic without your patch, and =20 > no panic so far! >=20 > I will let it run through the weekend, it prooves usefull as a burn-in-= =20 > test as well :-) >=20 > Will this patch make it into 7.1-RELEASE? There is a possibility. Please inform me about the weekend burn-test results. If results are encouranging, I am almost sure that I can squeeze it into the release. --MM5RgFPKyuP3gDcV Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkk5iBoACgkQC3+MBN1Mb4gVwwCg6mybvxLIKz3IBXyY4zuuNiqw nnIAnj+reE2q7nH883k/nch2+sBVJ97Q =NOYf -----END PGP SIGNATURE----- --MM5RgFPKyuP3gDcV-- From owner-freebsd-stable@FreeBSD.ORG Fri Dec 5 21:40:01 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3A6B6106567D for ; Fri, 5 Dec 2008 21:40:01 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.delphij.net (delphij-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:2c9::2]) by mx1.freebsd.org (Postfix) with ESMTP id D2BD58FC08 for ; Fri, 5 Dec 2008 21:40:00 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.geekcn.org (tarsier.geekcn.org [211.166.10.233]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tarsier.delphij.net (Postfix) with ESMTPS id 6EF2E28448 for ; Sat, 6 Dec 2008 05:39:59 +0800 (CST) Received: from localhost (tarsier.geekcn.org [211.166.10.233]) by tarsier.geekcn.org (Postfix) with ESMTP id A6240EBAA5D; Sat, 6 Dec 2008 05:39:58 +0800 (CST) X-Virus-Scanned: amavisd-new at geekcn.org Received: from tarsier.geekcn.org ([211.166.10.233]) by localhost (mail.geekcn.org [211.166.10.233]) (amavisd-new, port 10024) with ESMTP id EBGaacpuZFsT; Sat, 6 Dec 2008 05:39:54 +0800 (CST) Received: from charlie.delphij.net (adsl-76-237-33-62.dsl.pltn13.sbcglobal.net [76.237.33.62]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTPSA id 4DA90EBA464; Sat, 6 Dec 2008 05:39:53 +0800 (CST) DomainKey-Signature: a=rsa-sha1; s=default; d=delphij.net; c=nofws; q=dns; h=message-id:date:from:reply-to:organization:user-agent: mime-version:cc:subject:references:in-reply-to:x-enigmail-version:openpgp: content-type:content-transfer-encoding; b=epC6lPRFOzF0pATeiOg9IQ3HPa2i9NbI4vTDKeuvBAxfGbpsyeWVRlpEl6UWEXum7 7OSU5lzSP6XcHQsdx7kUA== Message-ID: <49399FA6.3060108@delphij.net> Date: Fri, 05 Dec 2008 13:39:50 -0800 From: Xin LI Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.18 (X11/20081125) MIME-Version: 1.0 References: <4935069A.8060209@ec-marseille.fr> <49357BD0.4000008@delphij.net> <4935944A.9090509@ec-marseille.fr> <4935C453.8070301@delphij.net> <4935D67E.4070204@delphij.net> <4936F8C4.6090006@ec-marseille.fr> In-Reply-To: <4936F8C4.6090006@ec-marseille.fr> X-Enigmail-Version: 0.95.7 OpenPGP: id=18EDEBA0; url=http://www.delphij.net/delphij.asc Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, d@delphij.net Subject: Re: RELENG_7_1: bce driver change generating too much interrupts ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: d@delphij.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Dec 2008 21:40:01 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 FYI, I have committed the patch as r185653 (stable/7) and r185654 (releng/7.1) so new build would get this issue fixed. Thanks goes to David who gave review for the changes and all who tested the earlier patches. Cheers, - -- Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkk5n6YACgkQi+vbBBjt66BToACfTp+1hqno30HTpNfcvMn7SpAF 6XoAn1St590CMK2Lz9jLwlnTLDKGW8cV =/FVN -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Sat Dec 6 15:42:34 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B9688106570D for ; Sat, 6 Dec 2008 15:42:34 +0000 (UTC) (envelope-from healthy-wealthy-tea@freemail.lt) Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by mx1.freebsd.org (Postfix) with ESMTP id 84F038FC1E for ; Sat, 6 Dec 2008 15:42:34 +0000 (UTC) (envelope-from healthy-wealthy-tea@freemail.lt) Received: from infong660.perfora.net (infong660.lxa.perfora.net [74.208.16.166]) by mrelay.perfora.net (node=mrus0) with ESMTP (Nemesis) id 0MKp8S-1L8z6X2xOK-0006QU; Sat, 06 Dec 2008 10:30:02 -0500 Received: from 121.97.158.125 (IP may be forged by CGI script) by infong660.perfora.net with HTTP id 3oUmtk-1L8z6X2yfm-0005VX; Sat, 06 Dec 2008 10:30:01 -0500 X-Sender-Info: <155977404@infong660.perfora.net> Date: Sat, 06 Dec 2008 10:30:01 -0500 Message-Id: <3oUmtk-1L8z6X2yfm-0005VX@infong660.perfora.net> Precedence: bulk To: "freebsd-stable" From: "healthy-wealthy-tea freebsd-stable" MIME-Version: 1.0 X-Mailer: Zen Cart Mailer Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX19D4YFolydCqYNDRZS7g4oUj7ZdQ/qOOYSCcrj 6rMo9QT9LC4hPxHSrxEFc3VhW3eyIEMkylgJtY/thzOvnvFcKn qYxRWJom/s= Subject: Your friend healthy-wealthy-tea freebsd-stable has recommended this great product from Green Tea & Me X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Dec 2008 15:42:34 -0000 Hi freebsd-stable! Your friend, healthy-wealthy-tea freebsd-stable, thought that you would be interested in Matcha from Green Tea & Me. healthy-wealthy-tea freebsd-stable sent a note saying: Amazing News, Get Paid, Look Smart And Stay Healthy! Hi Friend, Here's how it works... First, we detoxifies your body. Second, we burn your unwanted fats. Thus, we make all your friends jealous because you will actually lose weight the first day. And Third, you'll be paid the moment you start spreading the good news for others to try themselves with this extraordinary product. Visit this very important link below now!. http://123redirect.com/healthy-and-wealthy-tea So Goodluck, Look Good And Be Healthy, Associates http://123redirect.com/healthy-and-wealthy-tea Online Promoter P.S. Dr. Miller's Iaso Tea - formulated by Dr. Bill Miller (Bs.Ms.Ph.D. Nutritional Science) of Tennessee, USA - is a unique herbal blend of safe, all-natural ingredients designed to gently cleanse the digestive tract and detoxify the whole body. Iaso Tea is like a white tea, a green tea, a weight loss tea, and a great-tasting herbal tea - all wrapped up in each unbleached tea bag. But, most of all, Dr. Miller's Iaso Tea is a healing tea. Remarkable things happen when you drink Iaso Tea every day. It is gentle, yet surprisingly powerful as a colon cleanse, parasite cleanse, Candida cleanse, blood purifier, and whole body detoxifier. It acts like a general health tonic and a home remedy for many ailments like the ones mentioned below. Some want to call it a "miracle tea", but this cleansing and slimming tea is really just a special blend of high-quality herbs, tested and refined over time, which produce fast and effective results that no imitator has been able to copy. ------------------------------ Email here: healthy-wealthy-tea@freemail.lt and add "Not interested" ---------------------------------------------------------------------------------------- To view the product, click on the link below or copy and paste the link into your web browser: http://www.greenteame.com/store/index.php?main_page=product_info&products_id=1 Regards, Green Tea & Me http://www.greenteame.com/store/ ----- IMPORTANT: For your protection and to prevent malicious use, all emails sent via this web site are logged and the contents recorded and available to the store owner. If you feel that you have received this email in error, please send an email to customersupport@greenteame.com From owner-freebsd-stable@FreeBSD.ORG Sat Dec 6 21:03:42 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A63AD1065670 for ; Sat, 6 Dec 2008 21:03:42 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail14.syd.optusnet.com.au (mail14.syd.optusnet.com.au [211.29.132.195]) by mx1.freebsd.org (Postfix) with ESMTP id 341CE8FC08 for ; Sat, 6 Dec 2008 21:03:41 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c122-106-215-175.belrs3.nsw.optusnet.com.au [122.106.215.175]) by mail14.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id mB6L3KG9007556 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 7 Dec 2008 08:03:22 +1100 X-Bogosity: Ham, spamicity=0.000000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.3/8.14.3) with ESMTP id mB6L3KlL046237; Sun, 7 Dec 2008 08:03:20 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.3/8.14.3/Submit) id mB6L3H9Z046236; Sun, 7 Dec 2008 08:03:17 +1100 (EST) (envelope-from peter) Date: Sun, 7 Dec 2008 08:03:17 +1100 From: Peter Jeremy To: "Brian A. Seklecki" Message-ID: <20081206210316.GP58682@server.vk2pj.dyndns.org> References: <20080812120307.GD64458@server.vk2pj.dyndns.org> <1228480461.2805.469.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="gXx2FYK2AghGE4Yq" Content-Disposition: inline In-Reply-To: <1228480461.2805.469.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.18 (2008-05-17) Cc: stable@freebsd.org, eugen@kuzbass.ru, Pete French , Marian Hettwer Subject: Re: lagg(4) and failover 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: Sat, 06 Dec 2008 21:03:42 -0000 --gXx2FYK2AghGE4Yq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2008-Dec-05 07:34:21 -0500, "Brian A. Seklecki" wrote: >Well ... name a price for the development; HA L1/L2 is a feature the >community would gladly sponsor the development of. net/ifstated covers at least some of this. >Also, Peter, you should put a page up on the FreeBSD wiki with some of >those multi-catalyst LACP IOS config examples. =20 This appears to be aimed at Pete French - I'm using stacked Alcatel-Lucent OS6850's which appear as single switches to LACP. >P.S., in my experience, system level redundancy/HA with a load balancer >is almost always less expensive then excessive component-level >redundancy/ha (RAID Disk, RAID RAM, Dual Power Supplies, Dual >Backplanes...) That's a different topic, but yes, you should evaluate your requirements at a system level, rather than just making every component HA. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --gXx2FYK2AghGE4Yq Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkk66JQACgkQ/opHv/APuIcLvQCfdXg+eENrnDwlpxRCInASiBPe a+EAnA0jTQJljTZma4HShZVA5Zfw/xHn =WJvO -----END PGP SIGNATURE----- --gXx2FYK2AghGE4Yq-- From owner-freebsd-stable@FreeBSD.ORG Sat Dec 6 21:41:10 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F38DC1065672 for ; Sat, 6 Dec 2008 21:41:09 +0000 (UTC) (envelope-from csjp@freebsd.org) Received: from mx-02queue01.mts.net (mx-02queue01.mts.net [142.161.131.10]) by mx1.freebsd.org (Postfix) with ESMTP id A02278FC12 for ; Sat, 6 Dec 2008 21:41:09 +0000 (UTC) (envelope-from csjp@freebsd.org) Received: from wnpgmb013qw-sp03.mts.net ([10.205.128.23]) by mx-01mtaout02.mts.net with ESMTP id <20081206211347.XPWS12442.mx-01mtaout02.mts.net@wnpgmb013qw-sp03.mts.net> for ; Sat, 6 Dec 2008 15:13:47 -0600 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Aq8EACN6OkmOoT/O/2dsb2JhbACBbcBNCYpJAYIAgQQ X-IronPort-AV: E=Sophos;i="4.33,725,1220245200"; d="scan'208";a="48654613" Received: from wnpgmb1309w-ad05-63-206.dynamic.mts.net (HELO jnz.my.domain) ([142.161.63.206]) by wnpgmb013qw-sp03.mts.net with ESMTP; 06 Dec 2008 15:13:46 -0600 Received: from jnz.my.domain (localhost [127.0.0.1]) by jnz.my.domain (8.14.2/8.14.2) with ESMTP id mB6LDkhn060872; Sat, 6 Dec 2008 15:13:46 -0600 (CST) (envelope-from csjp@jnz.my.domain) Received: (from csjp@localhost) by jnz.my.domain (8.14.2/8.14.2/Submit) id mB6LDjol060871; Sat, 6 Dec 2008 15:13:45 -0600 (CST) (envelope-from csjp) Date: Sat, 6 Dec 2008 15:13:44 -0600 From: Christian Peron To: David Peall Message-ID: <20081206211344.GA60861@jnz.sqrt.ca> References: <0807767D2D53E649827BC55A3A53B06709C6C04BFE@exchange.ct.esn.org.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0807767D2D53E649827BC55A3A53B06709C6C04BFE@exchange.ct.esn.org.za> User-Agent: Mutt/1.4.2.3i Cc: "'freebsd-stable@freebsd.org'" Subject: Re: rtfree: 0xffffff00013797c0 has 1 refs 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: Sat, 06 Dec 2008 21:41:10 -0000 I have just fixed a similar (possibly the same) issue in -CURRENT. Please try the patch at: http://people.freebsd.org/~csjp/if_ether.1228494489.diff (Fetch it into /usr/src/sys/netinet and apply there). Let me know if this solves your problem, if it does I will try to get it in for the release. Thanks! On Fri, Dec 05, 2008 at 07:53:37AM +0200, David Peall wrote: > Hi > > I'm getting some strange messages: > > Dec 5 07:49:19 jonny kernel: rtfree: 0xffffff0001379d90 has 1 refs > Dec 5 07:49:19 jonny kernel: rtfree: 0xffffff000a1784d8 has 1 refs > Dec 5 07:49:28 jonny kernel: rtfree: 0xffffff000198a7c0 has 1 refs > Dec 5 07:49:31 jonny kernel: rtfree: 0xffffff00013797c0 has 1 refs > Dec 5 07:49:35 jonny kernel: rtfree: 0xffffff00013797c0 has 1 refs > Dec 5 07:49:37 jonny kernel: rtfree: 0xffffff0001c233e0 has 1 refs > Dec 5 07:49:43 jonny kernel: rtfree: 0xffffff00013797c0 has 1 refs > Dec 5 07:49:47 jonny kernel: rtfree: 0xffffff0001b3bc98 has 1 refs > > I've tried google but couldn't find anything usefull. > > Uname -a > FreeBSD jonny.esn.org.za 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Wed Nov 26 08:03:32 UTC 2008 root@:/usr/obj/usr/src/sys/GENERIC amd64 > > Is there some other output that would be useful please let me know. > > -- > David Peall :: IT Manager > e-Schools' Network :: http://www.esn.org.za/ > Phone +27 (021) 674-9140 > > _______________________________________________ > 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"