From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 6 00:56:55 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2169816A41A for ; Sun, 6 Jan 2008 00:56:55 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.183]) by mx1.freebsd.org (Postfix) with ESMTP id 0013F13C458 for ; Sun, 6 Jan 2008 00:56:54 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so11986142waf.3 for ; Sat, 05 Jan 2008 16:56: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:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=/FvXv7GvLBgERDbd4tBFe4BWOG3i2vD9N9bhDcbicdA=; b=aL8/DJb7T4PpY58WRnkJ/Yzp1ios0sIUrVRf+sf0W/9kEIKcaEQBl0N+T7VjagetfcSi40xmCVFfYcdF9F4iLPOeWlC+5hEgjNmY0VrrU4pc8jw8SzhEfeh45LpLGyXFw66XEoF9FDKEWZKOAaNw7tNrf+EUvFRj6C96XhY51tA= 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=d7ngN3Ax3KFuRx0V6xNRRCJ0tpwgGWPObJon/OBE4B3JPZ56Ng50XvWMKtj/oTDDNzSAvrK9rM44AA2niyTT9B8pLWVEGFKOx8nF/hFi01i54fyuHpGf2wZdS5leUj12b/Gqgl1uer55Zi1YueolQaS9n1sfRGpjXAMgB5ylM+w= Received: by 10.114.80.4 with SMTP id d4mr1788531wab.44.1199581014605; Sat, 05 Jan 2008 16:56:54 -0800 (PST) Received: by 10.114.255.11 with HTTP; Sat, 5 Jan 2008 16:56:54 -0800 (PST) Message-ID: Date: Sat, 5 Jan 2008 16:56:54 -0800 From: "Kip Macy" To: "Ray Mihm" In-Reply-To: <1aa142960801051655s64cacd78td97a20da41f0994a@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1aa142960801051655s64cacd78td97a20da41f0994a@mail.gmail.com> Cc: freebsd-hackers@freebsd.org, Ivan Voras Subject: Re: IRQ-CPU binding? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Jan 2008 00:56:55 -0000 http://perforce.freebsd.org/changeView.cgi?CH=124874 HTH On Jan 5, 2008 4:55 PM, Ray Mihm wrote: > On Jan 5, 2008 12:16 PM, Kip Macy wrote: > > It can easily be done, there is no API for it in CVS. > > I have a situation where this is needed. I would appreciate if you > tell me how to do it. > > Ray. > From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 6 01:08:25 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 82E8416A420 for ; Sun, 6 Jan 2008 01:08:25 +0000 (UTC) (envelope-from ray.mihm@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.158]) by mx1.freebsd.org (Postfix) with ESMTP id 1BC2513C46B for ; Sun, 6 Jan 2008 01:08:24 +0000 (UTC) (envelope-from ray.mihm@gmail.com) Received: by fg-out-1718.google.com with SMTP id 16so4689350fgg.35 for ; Sat, 05 Jan 2008 17:08:24 -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=K2UAO/EBEIKhga+Jd3O5XM2t+UuQ5nU7UR+4VmgKDX8=; b=S4jOee2gU1v3AzzTy0PVJLoOFJgp/EBRTbKpnbpR4SqUhNaxa7V2UagPgEqppBxsJ2pOEhFcury4NlkJ/rc2q2PKbOnbqg4+9G0GJCZzXsLYAyEPAn45ime3eA/RhReLqXE6TYCErOkbjLqtmGKmJgbairEz+Zj13rNlW5GEvUM= 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=LKBTCUmIm2noCNgacbNik0egwXg3fOm9LqrQrT7aqf5GvtyRMOsOavp0k7dgl73b4AR97Qdm5dD+eGInuSUBzWy1WE5uLb9QcqmsnNgydfbXqZ/j+WN+FglPuU0QCRkf4RVHB5qUfOyX3AuhxrXPDiKtg8VUoYJez49Ej+Y9B0w= Received: by 10.86.78.4 with SMTP id a4mr18457729fgb.3.1199581278043; Sat, 05 Jan 2008 17:01:18 -0800 (PST) Received: by 10.86.91.5 with HTTP; Sat, 5 Jan 2008 17:01:18 -0800 (PST) Message-ID: <1aa142960801051701m2e44873aia860f72f4dcb418d@mail.gmail.com> Date: Sat, 5 Jan 2008 17:01:18 -0800 From: "Ray Mihm" To: "Kip Macy" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1aa142960801051655s64cacd78td97a20da41f0994a@mail.gmail.com> Cc: freebsd-hackers@freebsd.org, Ivan Voras Subject: Re: IRQ-CPU binding? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Jan 2008 01:08:25 -0000 On Jan 5, 2008 4:56 PM, Kip Macy wrote: > http://perforce.freebsd.org/changeView.cgi?CH=124874 Yes, that's it. Thanks very much. Ray. From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 6 01:22:57 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D936F16A417 for ; Sun, 6 Jan 2008 01:22:57 +0000 (UTC) (envelope-from ray.mihm@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.159]) by mx1.freebsd.org (Postfix) with ESMTP id 71DCF13C447 for ; Sun, 6 Jan 2008 01:22:57 +0000 (UTC) (envelope-from ray.mihm@gmail.com) Received: by fg-out-1718.google.com with SMTP id 16so4691094fgg.35 for ; Sat, 05 Jan 2008 17:22: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:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=vacCJQqUqBU2JvdnWA6dB4AadKchmF0zp/MPR5h+ZjU=; b=wqrFxwgsVx1g7lF6qRPXldAhaEdKBrmRmW90no7mxUJ++PVQ/KqfQq2yz0rNXaLZkvALQDxgRozK0MKnwsFy+kTO9bFRKxB81OSBCs5gPpzbSX2qxI6xTJeRHh3uGxJctRip9UzfI4OE4va6YxofczIqAsby6eC3F4dziyKhYdA= 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=OUq8XS92aXRyyC83n62LfgY4l0BRxIg1wZaNq9+l4+gjebzorUXBzOvoAT+z61BWb6sIYGz+xwmQk3TXQT2YsRGoSp1zdTaXpCxjXkOHwRvhyrplH3sz71Bd4aD0alKgnrxVi7TAoJS+HR1pHHxM8q8XpcmDi26/sz5oz1oKUbI= Received: by 10.86.28.5 with SMTP id b5mr9703012fgb.76.1199580915552; Sat, 05 Jan 2008 16:55:15 -0800 (PST) Received: by 10.86.91.5 with HTTP; Sat, 5 Jan 2008 16:55:15 -0800 (PST) Message-ID: <1aa142960801051655s64cacd78td97a20da41f0994a@mail.gmail.com> Date: Sat, 5 Jan 2008 16:55:15 -0800 From: "Ray Mihm" To: "Kip Macy" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Cc: freebsd-hackers@freebsd.org, Ivan Voras Subject: Re: IRQ-CPU binding? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Jan 2008 01:22:57 -0000 On Jan 5, 2008 12:16 PM, Kip Macy wrote: > It can easily be done, there is no API for it in CVS. I have a situation where this is needed. I would appreciate if you tell me how to do it. Ray. From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 6 22:57:13 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9EA6816A41B for ; Sun, 6 Jan 2008 22:57:13 +0000 (UTC) (envelope-from stefan.aeschbacher@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.243]) by mx1.freebsd.org (Postfix) with ESMTP id 686D813C478 for ; Sun, 6 Jan 2008 22:57:13 +0000 (UTC) (envelope-from stefan.aeschbacher@gmail.com) Received: by an-out-0708.google.com with SMTP id c14so1557435anc.13 for ; Sun, 06 Jan 2008 14:57:12 -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:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth; bh=tyqfatro7+WJ2OxWaIHZuLHRYUIUQD1PkZDgJ7S3ogU=; b=NwzAaZz6wwaFHKF1Gy2/yqYHagtftRuqQaZ8Fcu5kUZGxnTtp+630FxiX4m9LU1RY+3o1U37gKdC9C2Xu6U3VwsVPrFf3L8Zvl7BBdSEXDvWt+IVeJhFirrmSxX1pNpoz6aJwPJ9IBnrkWDyfVg93kPoMg971Hlo1YaJa8wKc9g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth; b=sKJV2yZKT1JbsBND6yZZqhOjAtbNtWd9zVLAAdL2e/KylT0LN8CCOlxa3604+lgXNwD5cUUHey46qvqE7oH6yahxLkaPQP6lM+Pbs5vqeS6HH97jgtzPoumToot1agvjxIsALdNkI/OLifit8dAmwTezaH58asHeKzSOWKTY4HY= Received: by 10.100.34.16 with SMTP id h16mr41015963anh.114.1199658479040; Sun, 06 Jan 2008 14:27:59 -0800 (PST) Received: by 10.70.126.4 with HTTP; Sun, 6 Jan 2008 14:27:58 -0800 (PST) Message-ID: <207060770801061427o2dc99d76y7f85fa527c29125c@mail.gmail.com> Date: Sun, 6 Jan 2008 23:27:58 +0100 From: "Stefan Aeschbacher" Sender: stefan.aeschbacher@gmail.com To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Google-Sender-Auth: 546dc5f1df6f5c3f Subject: SATA RAID Problems X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Jan 2008 22:57:13 -0000 Hi I just bought a new Server (a Fujitsu Siemens PRIMERGY Econel 100) with 2 x 160GB disks (ad4 and ad6) and added a 1TB disk (ad8). Configuring the two 160GB disks ar a RAID1 in the LSI MegaRAID utility works without problems, but when I boot FreeBSD (FreeSBIE 2.0.1 or a bootable 7.0 RC1), the RAID consist of ad4 and ad8 (see dmesg below). I tried to delete the RAID configuration from the disks (I never configured the 1TB disk into the RAID in the first place) via LSI utility, atacontrol delte and dd'ing the head of the disk from /dev/zero but nothing worked. When I unplug ad8, the RAID is displayed as consisting of ad4 and ad6 as expected. When I change the SATA Controller from RAID to Native, atacontrol displays the correct drives (ad4 and ad6) to belong to ar0. Furthermore, the througput rate of the disks is very meager, ad4 and ad6 make around 5MB/s, ad8 only 0.5MB/s. any ideas? thanks Stefan dmesg from FreeSBIE with all 3 disks attached. Copyright (c) 1992-2007 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 6.2-RELEASE #11: Wed Feb 7 16:52:42 UTC 2007 root@kaiser.sig11.org:/usr/obj.gmv-i386/usr/src/sys/FREESBIE ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) D CPU 3.40GHz (3400.15-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf65 Stepping = 5 Features=0xbfebfbff Features2=0xe49d,> AMD Features=0x20100000 AMD Features2=0x1 Cores per package: 2 real memory = 1072562176 (1022 MB) avail memory = 1040560128 (992 MB) ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: on motherboard acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi0: Power Button (fixed) acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0xf008-0xf00b on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: irq 17 at device 28.0 on pci0 pci4: on pcib1 pcib2: irq 17 at device 28.4 on pci0 pci7: on pcib2 bge0: mem 0xfc100000-0xfc10ffff irq 16 at device 0.0 on pci7 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:19:99:1b:02:e7 pcib3: irq 16 at device 28.5 on pci0 pci8: on pcib3 uhci0: port 0x2000-0x201f irq 23 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0x2400-0x241f irq 22 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0x2800-0x281f irq 21 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhci3: port 0x2c00-0x2c1f irq 20 at device 29.3 on pci0 uhci3: [GIANT-LOCKED] usb3: on uhci3 usb3: USB revision 1.0 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered ehci0: mem 0xfc000000-0xfc0003ff irq 23 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: on ehci0 usb4: USB revision 2.0 uhub4: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub4: 8 ports with 8 removable, self powered pcib4: at device 30.0 on pci0 pci11: on pcib4 pci11: at device 3.0 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x3420-0x342f at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 atapci1: port 0x3440-0x3447,0x3434-0x3437,0x3438-0x343f,0x3430-0x3433,0x3400-0x341f mem 0xfc000400-0xfc0007ff irq 19 at device 31.2 on pci0 atapci1: AHCI Version 01.10 controller with 4 ports detected ata2: on atapci1 ata3: on atapci1 ata4: on atapci1 ata5: on atapci1 pci0: at device 31.3 (no driver attached) atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] ppc0: port 0x378-0x37b irq 7 on acpi0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A pmtimer0 on isa0 orm0: at iomem 0xc0000-0xc8fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ums0: Logitech USB Mouse, rev 1.10/29.00, addr 2, iclass 3/1 ums0: 3 buttons and Z dir. umass0: LEXAR MEDIA JUMPDRIVE, rev 1.10/0.01, addr 3 Timecounter "TSC" frequency 3400145537 Hz quality 800 Timecounters tick every 1.000 msec ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding disabled, default to accept, logging unlimited acd0: DVDROM at ata0-master UDMA33 ad4: 152627MB at ata2-master SATA300 ad6: 152627MB at ata3-master SATA300 ad8: 953869MB at ata4-master SATA150 GEOM_LABEL: Label for provider acd0 is iso9660/FreeSBIE. cd0 at ata0 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: cd present [343720 x 2048 byte records] ar0: 152520MB status: READY ar0: disk0 READY (master) using ad4 at ata2-master ar0: disk1 READY (mirror) using ad8 at ata4-master From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 7 08:34:53 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 175B016A41B for ; Mon, 7 Jan 2008 08:34:53 +0000 (UTC) (envelope-from samflanker@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.157]) by mx1.freebsd.org (Postfix) with ESMTP id A692813C4E3 for ; Mon, 7 Jan 2008 08:34:52 +0000 (UTC) (envelope-from samflanker@gmail.com) Received: by fg-out-1718.google.com with SMTP id 16so4995293fgg.35 for ; Mon, 07 Jan 2008 00:34:51 -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=LFypkccx2jMfsvLYC2tA8UiBhQcBU9D2xWH6aVbDUlU=; b=HIElwOwplKhww8RsuiJJv74j/sWuMS9vU3YikmQ1SkEywYUinx7UXWY4LvfYsmhCzinqYWJpucVHOiPaIc/OSGhuqUVPy2yubWECyMfLFQkOutRvdgVptpG+C43i49rW8IGQcQmFv1Mv5AiLr0py0JPMtOWlqJFWeba3R4PPkDw= 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=DnhyUks9R+Rt3pw73v5tRM8iaOQ5V7vQmCbP15enIupV0PljYFnsQNzslT4WY2rO9k9KP4/M1IyQruXOGvcZ3gQnsyvwVgoW4SofZzqqumkDbpujSF59SpwQCY/71W5L4lVeZnWJJHyxTEO7f3eQduQDedNlw6UDEIsFQIfSNEQ= Received: by 10.86.91.12 with SMTP id o12mr19887789fgb.62.1199694891219; Mon, 07 Jan 2008 00:34:51 -0800 (PST) Received: from ?192.168.12.92? ( [213.152.137.38]) by mx.google.com with ESMTPS id l19sm22504548fgb.3.2008.01.07.00.34.49 (version=SSLv3 cipher=RC4-MD5); Mon, 07 Jan 2008 00:34:50 -0800 (PST) Message-ID: <4781E42B.701@gmail.com> Date: Mon, 07 Jan 2008 11:34:51 +0300 From: sam User-Agent: Thunderbird 2.0.0.4 (Windows/20070604) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: syscall linux_getdents() trouble X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jan 2008 08:34:53 -0000 program-test (experimental) for testing syscall linux_getdents() http://cs.udmvt.ru/files/temp/linux_dbg.tar.bz2 includes: * temp/ - test_dir with files (special for crash situation) * linux_getdents.c - source of program-test * linux_getdents_static - binary exec file, staticaly compiled on Linux Debian 4.0 Etch * linux_getdents_dynamic - binary exec file, dynamicaly compiled on Linux Debian 4.0 Etch - test failed on systems: FreeBSD 6.3-PRERELEASE with port linux_base-fc4, FreeBSD 8.0-CURRENT with port linux_base-fc4; - test passed on Linux Debian 4.0 Etch Trouble: syscall linux_getdents() don`t stable work Trouble Description: http://lists.freebsd.org/pipermail/freebsd-emulation/2007-September/thread.html topic subject: linuxolator problem on i386 http://www.freebsd.org/cgi/query-pr.cgi?pr=117010 please help, any solution? /Vladimir Ermakov From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 7 09:12:47 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AF1E616A418 for ; Mon, 7 Jan 2008 09:12:47 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from vlakno.cz (vlk.vlakno.cz [62.168.28.247]) by mx1.freebsd.org (Postfix) with ESMTP id 70FCA13C447 for ; Mon, 7 Jan 2008 09:12:47 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from localhost (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id 82B4566B899; Mon, 7 Jan 2008 09:56:19 +0100 (CET) X-Virus-Scanned: amavisd-new at vlakno.cz Received: from vlakno.cz ([127.0.0.1]) by localhost (vlk.vlakno.cz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3GGW7A-8E1QR; Mon, 7 Jan 2008 09:56:06 +0100 (CET) Received: from vlk.vlakno.cz (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id EC50166B86F; Mon, 7 Jan 2008 09:56:05 +0100 (CET) Received: (from rdivacky@localhost) by vlk.vlakno.cz (8.13.8/8.13.8/Submit) id m078u5A9067987; Mon, 7 Jan 2008 09:56:05 +0100 (CET) (envelope-from rdivacky) Date: Mon, 7 Jan 2008 09:56:05 +0100 From: Roman Divacky To: sam Message-ID: <20080107085605.GA67904@freebsd.org> References: <4781E42B.701@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4781E42B.701@gmail.com> User-Agent: Mutt/1.4.2.3i Cc: freebsd-hackers@freebsd.org Subject: Re: syscall linux_getdents() trouble X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jan 2008 09:12:47 -0000 On Mon, Jan 07, 2008 at 11:34:51AM +0300, sam wrote: > program-test (experimental) for testing syscall linux_getdents() > http://cs.udmvt.ru/files/temp/linux_dbg.tar.bz2 > includes: > * temp/ - test_dir with files (special for crash situation) > * linux_getdents.c - source of program-test > * linux_getdents_static - binary exec file, staticaly compiled on Linux > Debian 4.0 Etch > * linux_getdents_dynamic - binary exec file, dynamicaly compiled on > Linux Debian 4.0 Etch > > - test failed on systems: FreeBSD 6.3-PRERELEASE with port > linux_base-fc4, FreeBSD 8.0-CURRENT with port linux_base-fc4; > - test passed on Linux Debian 4.0 Etch > > Trouble: syscall linux_getdents() don`t stable work > > Trouble Description: > http://lists.freebsd.org/pipermail/freebsd-emulation/2007-September/thread.html > topic subject: linuxolator problem on i386 > http://www.freebsd.org/cgi/query-pr.cgi?pr=117010 > > please help, any solution? unless someone else looks at it it wont be done anytime soon as I dont have much time. I'll try to find some but I cant promise anything. some other volunteer? (so I can focus on other things) From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 8 19:27:34 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0E6C016A469 for ; Tue, 8 Jan 2008 19:27:34 +0000 (UTC) (envelope-from aduane@juniper.net) Received: from exprod7og105.obsmtp.com (exprod7og105.obsmtp.com [64.18.2.163]) by mx1.freebsd.org (Postfix) with ESMTP id C736513C44B for ; Tue, 8 Jan 2008 19:27:33 +0000 (UTC) (envelope-from aduane@juniper.net) Received: from source ([66.129.224.36]) by exprod7ob105.postini.com ([64.18.6.12]) with SMTP; Tue, 08 Jan 2008 11:25:12 PST Received: from proton.jnpr.net ([10.10.2.37]) by emailsmtp56.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Fri, 28 Dec 2007 06:08:58 -0800 Received: from antipi.jnpr.net ([10.10.2.34]) by proton.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Fri, 28 Dec 2007 09:09:07 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Fri, 28 Dec 2007 09:09:08 -0500 Message-ID: <0FCFCF6165E968449991746EB91D614DD48EF6@antipi.jnpr.net> In-Reply-To: <200712281127.53084.sharadc@in.niksun.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: trap 12 with interrupts disabled, need help Thread-Index: AchJGwl547VCBQkcR9aMIFx29WD3GwAP/16g References: <200712281127.53084.sharadc@in.niksun.com> From: "Andrew Duane" To: "Sharad Chandra" , X-OriginalArrivalTime: 28 Dec 2007 14:09:07.0217 (UTC) FILETIME=[35B82010:01C8495B] Cc: chandrabhagat@gmail.com Subject: RE: trap 12 with interrupts disabled, need help X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jan 2008 19:27:34 -0000 Obvious question: is your stack set up properly, and is it big enough? It could be that you haven't set up a bigger kernel stack yet, and have overrun the small boot stack that the processor was running on. Do you know what the stack pointer is? If it is a few bytes below a page boundary, then overrunning the stack is a good guess. /Andrew =20 > -----Original Message----- > From: owner-freebsd-hackers@freebsd.org [mailto:owner-freebsd- > hackers@freebsd.org] On Behalf Of Sharad Chandra > Sent: Friday, December 28, 2007 12:58 AM > To: freebsd-hackers@freebsd.org > Cc: chandrabhagat@gmail.com > Subject: trap 12 with interrupts disabled, need help >=20 > Hi, >=20 > I got a message on first boot "pid (): trap 12 with > interrupts > disabled", then it hanged and hard boot is required. > It does not appears all the time. >=20 > I tried to figure out the problem, trap 12 is stack exception, find at the > last > http://www.acm.uiuc.edu/sigops/roll_your_own/i386/idt.html > and is coming from kernel, > The location of this message is /usr/src/ > sys/amd64/amd64/trap.c: "pid %ld (%s): trap %d with > interrupts disabled\n", >=20 > What does this exception mean, and what could be possible reason that my > program is doing wrong? How to handle it >=20 > Platform: freebsd 6.1 on amd64 >=20 > -- >=20 > Thanks > Sharad Chandra > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 9 00:23:00 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5838216A421 for ; Wed, 9 Jan 2008 00:23:00 +0000 (UTC) (envelope-from bharmaji@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.154]) by mx1.freebsd.org (Postfix) with ESMTP id EAD8513C44B for ; Wed, 9 Jan 2008 00:22:59 +0000 (UTC) (envelope-from bharmaji@gmail.com) Received: by fg-out-1718.google.com with SMTP id 16so28255fgg.35 for ; Tue, 08 Jan 2008 16:22:58 -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=Z45RPgi3a4ufy0A/XtilyDkTgGxun1ldLk52IU5Vwfs=; b=uzb0hG7Tgj+JckzHa7qIzEyDpHI6ldI+WkEP0ShU+AUqGPq/5hF11s51z1LtYF8h89ksjvjBVhYOMeyvmNrq1HUyQL5tKD4VMIJHd9c/vF8hPgx3RNsBQsY3PbSZKuEbVTKtqdv5uiiJKRBu+8OrR/H63co7sJEDioSXo8GrBXE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=c7TF+sOTI6fo0YgV37ILTLOmLl/oH/f1tSlh6Hw0HTH0HRRySXMIgfKgBTW8uABefQzNvCVkZgfWCMWt6TwY95ffdilmFVmkvtksfjZzSA9nUVzoLorPB3VTtbNGHtvWCWRP4vrR4AJ0jNSWExo7Colz4d+ckVBEFrK8mQgF6d0= Received: by 10.78.201.10 with SMTP id y10mr33847huf.11.1199836558881; Tue, 08 Jan 2008 15:55:58 -0800 (PST) Received: by 10.78.130.18 with HTTP; Tue, 8 Jan 2008 15:55:58 -0800 (PST) Message-ID: <67beabb0801081555v4ca3b729x294322fa724afa09@mail.gmail.com> Date: Tue, 8 Jan 2008 15:55:58 -0800 From: "Bharma Ji" To: freebsd-hackers@freebsd.org 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: Graceful failure instead of panicking in kmem_malloc X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jan 2008 00:23:00 -0000 In FreeBSD 6_2, if kmem_malloc is unable to find space it panics. The relevant code is in vm_kern.c if ((flags & M_NOWAIT) == 0) panic("kmem_malloc(%ld): kmem_map too small: %ld total allocated", (long)size, (long)map->size); Is there any way to make the system log and then gracefully shut off instead of panicking? From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 9 00:30:25 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1AD6516A420 for ; Wed, 9 Jan 2008 00:30:25 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 72C1713C467; Wed, 9 Jan 2008 00:30:24 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <4784159E.9040905@FreeBSD.org> Date: Wed, 09 Jan 2008 01:30:22 +0100 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: Bharma Ji References: <67beabb0801081555v4ca3b729x294322fa724afa09@mail.gmail.com> In-Reply-To: <67beabb0801081555v4ca3b729x294322fa724afa09@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: Graceful failure instead of panicking in kmem_malloc X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jan 2008 00:30:25 -0000 Bharma Ji wrote: > In FreeBSD 6_2, if kmem_malloc is unable to find space it panics. The > relevant code is in vm_kern.c > if ((flags & M_NOWAIT) == 0) > panic("kmem_malloc(%ld): kmem_map too small: %ld > total allocated", > (long)size, (long)map->size); > > Is there any way to make the system log and then gracefully shut off instead > of panicking? Not really, because those actions require memory allocation. The real fix is to either a) avoid running out of memory in the first place by tuning vm.kmem_size b) perhaps trying harder to avoid panicking by first trying to more aggressively reclaim memory. You can try http://www.freebsd.org/~pjd/patches/vm_kern.c.2.patch which implements b) (patch against 7.0, but might apply to 6.2 unchanged). Kris From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 9 03:25:21 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2A3A616A417 for ; Wed, 9 Jan 2008 03:25:20 +0000 (UTC) (envelope-from bharmaji@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.155]) by mx1.freebsd.org (Postfix) with ESMTP id 5D6D413C447 for ; Wed, 9 Jan 2008 03:25:19 +0000 (UTC) (envelope-from bharmaji@gmail.com) Received: by fg-out-1718.google.com with SMTP id 16so81769fgg.35 for ; Tue, 08 Jan 2008 19:25:18 -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:references; bh=wA+EBlI6BdRSTq/5gERSMOSe1kks+5EzvI5UQtHY7Y8=; b=hpMG+jbnAEoMzpIIgqbKRqWya9wQt2K67922zNobDV5LuGYZfB0VMxjqkc8nVyXAKFQztR2rPCuKegaDK+rz0BVc5fkXWrRTvJmgzwnNiXO4WMq+fJrasnFpd7aQ3kZJ7smJUlXPG9GcdT5wPmszs86hEbfEA3RXeKFwvfLoq6k= 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:references; b=E4bC9qnA9QitIOlOwgrgECTvbGSeOXwfM8/6NcMW0dRMKXSXrsXv5XJ/Ps3JeATIbPDhItli+IxbvpqI8WeQ4JSCqLSxI4SIt0Loe3N3qL8lXtnWuUP04bFA3X2xqb+Dgp6NwtT82Qh5tppfkwL8sGnelFNeidt7tGHWZdUh8D4= Received: by 10.78.81.20 with SMTP id e20mr51178hub.60.1199849117928; Tue, 08 Jan 2008 19:25:17 -0800 (PST) Received: by 10.78.130.18 with HTTP; Tue, 8 Jan 2008 19:25:17 -0800 (PST) Message-ID: <67beabb0801081925t67f995b8hc4cc779f88c2ba@mail.gmail.com> Date: Tue, 8 Jan 2008 19:25:17 -0800 From: "Bharma Ji" To: "Kris Kennaway" In-Reply-To: <4784159E.9040905@FreeBSD.org> MIME-Version: 1.0 References: <67beabb0801081555v4ca3b729x294322fa724afa09@mail.gmail.com> <4784159E.9040905@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers@freebsd.org Subject: Re: Graceful failure instead of panicking in kmem_malloc X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jan 2008 03:25:21 -0000 Thanks for the response. I am hoping to keep some memory aside specifically for handling out of memory allocation situations. Yes the real fix is to avoid out of memory allocation. Thanks for the patch. Will try that. As a first cut I am just trying to handle failure gracefully. So asking again - if there is any way already discussed or standardized to make the system handle failures gracefully On Jan 8, 2008 4:30 PM, Kris Kennaway wrote: > Bharma Ji wrote: > > In FreeBSD 6_2, if kmem_malloc is unable to find space it panics. The > > relevant code is in vm_kern.c > > if ((flags & M_NOWAIT) == 0) > > panic("kmem_malloc(%ld): kmem_map too small: > %ld > > total allocated", > > (long)size, (long)map->size); > > > > Is there any way to make the system log and then gracefully shut off > instead > > of panicking? > > Not really, because those actions require memory allocation. The real > fix is to either > > a) avoid running out of memory in the first place by tuning vm.kmem_size > > b) perhaps trying harder to avoid panicking by first trying to more > aggressively reclaim memory. > > You can try > > http://www.freebsd.org/~pjd/patches/vm_kern.c.2.patch > > which implements b) (patch against 7.0, but might apply to 6.2 unchanged). > > Kris > From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 9 09:53:09 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5F19316A41A for ; Wed, 9 Jan 2008 09:53:09 +0000 (UTC) (envelope-from jrisom@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.179]) by mx1.freebsd.org (Postfix) with ESMTP id 14F3A13C461 for ; Wed, 9 Jan 2008 09:53:08 +0000 (UTC) (envelope-from jrisom@gmail.com) Received: by py-out-1112.google.com with SMTP id u52so296513pyb.10 for ; Wed, 09 Jan 2008 01:53:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:in-reply-to:references:mime-version:content-type:message-id:content-transfer-encoding:cc:from:subject:date:to:x-mailer; bh=l1GCgg+eMHFiWMCf6lg1mtWTka3JdNlWamhTqdpRNyo=; b=qvGH2OL9V1PPkWLMrjyYWYrUB2SIUshT2fPo7naeoZD8Y80zImXETAW6zGanQOmrY6MMrX+KEG4w42tcOYtESDIh+5v0fQ6umU85J5kbwEsXf2J4vnfDVMLY+tcvhDHTqH7mc99kFVk7U2FfJ851BkNF0UmW7nVYKDJY0l6sR+A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=in-reply-to:references:mime-version:content-type:message-id:content-transfer-encoding:cc:from:subject:date:to:x-mailer; b=SQXitBCIPYnw9J/W7cDFO3pka+FAIZciucieWhAaMAswuGDu+x8WSOxG7qUor9rVjzSo4seat9BHBMU9QbZpV77uliafb6d70OZf5b8Tx2EImRBhc9O6P0tTWdyGDaNF8Ap/WLL4vJg3OW6ZUaRLIV07Ii0NBDdyMSTAmo6PeQ0= Received: by 10.35.33.5 with SMTP id l5mr572561pyj.30.1199870925885; Wed, 09 Jan 2008 01:28:45 -0800 (PST) Received: from ?192.168.1.4? ( [74.134.230.123]) by mx.google.com with ESMTPS id f45sm1639141pyh.6.2008.01.09.01.28.44 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 09 Jan 2008 01:28:45 -0800 (PST) In-Reply-To: <67beabb0801081925t67f995b8hc4cc779f88c2ba@mail.gmail.com> References: <67beabb0801081555v4ca3b729x294322fa724afa09@mail.gmail.com> <4784159E.9040905@FreeBSD.org> <67beabb0801081925t67f995b8hc4cc779f88c2ba@mail.gmail.com> Mime-Version: 1.0 (Apple Message framework v624) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <66462bcb31fb347796200bd5260d7cdc@gmail.com> Content-Transfer-Encoding: 7bit From: Joshua Isom Date: Wed, 9 Jan 2008 03:29:43 -0600 To: "Bharma Ji" X-Mailer: Apple Mail (2.624) Cc: freebsd-hackers@freebsd.org Subject: Re: Graceful failure instead of panicking in kmem_malloc X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jan 2008 09:53:09 -0000 On Jan 8, 2008, at 9:25 PM, Bharma Ji wrote: > Thanks for the response. I am hoping to keep some memory aside > specifically > for handling out of memory allocation situations. Yes the real fix is > to > avoid out of memory allocation. Thanks for the patch. Will try that. > As a > first cut I am just trying to handle failure gracefully. > > So asking again - if there is any way already discussed or > standardized to > make the system handle failures gracefully > > On Jan 8, 2008 4:30 PM, Kris Kennaway wrote: > >> Bharma Ji wrote: >>> In FreeBSD 6_2, if kmem_malloc is unable to find space it panics. The >>> relevant code is in vm_kern.c >>> if ((flags & M_NOWAIT) == 0) >>> panic("kmem_malloc(%ld): kmem_map too small: >> %ld >>> total allocated", >>> (long)size, (long)map->size); >>> >>> Is there any way to make the system log and then gracefully shut off >> instead >>> of panicking? >> >> Not really, because those actions require memory allocation. The real >> fix is to either >> >> a) avoid running out of memory in the first place by tuning >> vm.kmem_size >> >> b) perhaps trying harder to avoid panicking by first trying to more >> aggressively reclaim memory. >> >> You can try >> >> >> http://www.freebsd.org/~pjd/patches/vm_kern.c.2.patch> www.freebsd.org/%7Epjd/patches/vm_kern.c.2.patch> >> >> which implements b) (patch against 7.0, but might apply to 6.2 >> unchanged). >> >> Kris >> > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to > "freebsd-hackers-unsubscribe@freebsd.org" Why not try to take out some user processes? Going with a combination of process priority and memory usage, it should at least be more tolerable than a panic. From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 9 10:10:34 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DA41A16A41A for ; Wed, 9 Jan 2008 10:10:34 +0000 (UTC) (envelope-from wundram@beenic.net) Received: from mail.beenic.net (mail.beenic.net [83.246.72.40]) by mx1.freebsd.org (Postfix) with ESMTP id 99B0F13C467 for ; Wed, 9 Jan 2008 10:10:34 +0000 (UTC) (envelope-from wundram@beenic.net) Received: from [192.168.1.32] (a89-182-145-140.net-htp.de [89.182.145.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.beenic.net (Postfix) with ESMTP id D9722A44529 for ; Wed, 9 Jan 2008 11:03:36 +0100 (CET) From: "Heiko Wundram (Beenic)" Organization: Beenic Networks GmbH To: freebsd-hackers@freebsd.org Date: Wed, 9 Jan 2008 11:11:05 +0100 User-Agent: KMail/1.9.7 References: <67beabb0801081555v4ca3b729x294322fa724afa09@mail.gmail.com> <67beabb0801081925t67f995b8hc4cc779f88c2ba@mail.gmail.com> <66462bcb31fb347796200bd5260d7cdc@gmail.com> In-Reply-To: <66462bcb31fb347796200bd5260d7cdc@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200801091111.06050.wundram@beenic.net> Subject: Re: Graceful failure instead of panicking in kmem_malloc X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jan 2008 10:10:34 -0000 Am Mittwoch, 9. Januar 2008 10:29:43 schrieb Joshua Isom: > Why not try to take out some user processes? Going with a combination > of process priority and memory usage, it should at least be more > tolerable than a panic. Ahemm. No. That's not tolerable in real world conditions. Have you ever had the OOM-killer strike on Linux (which is known for this, and has been criticized at other times for its braindead default behavior of overcommiting virtual memory space almost two-fold)? That's a major, major PITA. I'd rather have the system reboot and come back up to a clean and initialized state than to "randomly" kill user processes and leave it crippled but (somewhat) running (with sshd possibly killed off, which is especially bad on remote boxes), as basically to recover cleanly from the OOM-killer striking, you're going to have to reboot the box anyway. -- Heiko Wundram Product & Application Development From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 9 10:13:24 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AEF9116A418 for ; Wed, 9 Jan 2008 10:13:24 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id C9FC213C4DB; Wed, 9 Jan 2008 10:13:23 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <47849E42.7090201@FreeBSD.org> Date: Wed, 09 Jan 2008 11:13:22 +0100 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: Joshua Isom References: <67beabb0801081555v4ca3b729x294322fa724afa09@mail.gmail.com> <4784159E.9040905@FreeBSD.org> <67beabb0801081925t67f995b8hc4cc779f88c2ba@mail.gmail.com> <66462bcb31fb347796200bd5260d7cdc@gmail.com> In-Reply-To: <66462bcb31fb347796200bd5260d7cdc@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, Bharma Ji Subject: Re: Graceful failure instead of panicking in kmem_malloc X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jan 2008 10:13:24 -0000 Joshua Isom wrote: > > On Jan 8, 2008, at 9:25 PM, Bharma Ji wrote: > >> Thanks for the response. I am hoping to keep some memory aside >> specifically >> for handling out of memory allocation situations. Yes the real fix is to >> avoid out of memory allocation. Thanks for the patch. Will try that. As a >> first cut I am just trying to handle failure gracefully. >> >> So asking again - if there is any way already discussed or >> standardized to >> make the system handle failures gracefully >> >> On Jan 8, 2008 4:30 PM, Kris Kennaway wrote: >> >>> Bharma Ji wrote: >>>> In FreeBSD 6_2, if kmem_malloc is unable to find space it panics. The >>>> relevant code is in vm_kern.c >>>> if ((flags & M_NOWAIT) == 0) >>>> panic("kmem_malloc(%ld): kmem_map too small: >>> %ld >>>> total allocated", >>>> (long)size, (long)map->size); >>>> >>>> Is there any way to make the system log and then gracefully shut off >>> instead >>>> of panicking? >>> >>> Not really, because those actions require memory allocation. The real >>> fix is to either >>> >>> a) avoid running out of memory in the first place by tuning vm.kmem_size >>> >>> b) perhaps trying harder to avoid panicking by first trying to more >>> aggressively reclaim memory. >>> >>> You can try >>> >>> >>> http://www.freebsd.org/~pjd/patches/vm_kern.c.2.patch >>> >>> >>> which implements b) (patch against 7.0, but might apply to 6.2 >>> unchanged). >>> >>> Kris >>> >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to >> "freebsd-hackers-unsubscribe@freebsd.org" > > Why not try to take out some user processes? Going with a combination > of process priority and memory usage, it should at least be more > tolerable than a panic. This is kernel memory, not user memory. There is a fixed-size arena for mallocs in the kernel, and the panic happens when it fills up and no free space can be immediately reclaimed. Kris From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 9 11:16:43 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0C29016A419 for ; Wed, 9 Jan 2008 11:16:43 +0000 (UTC) (envelope-from greycd@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.181]) by mx1.freebsd.org (Postfix) with ESMTP id D332413C43E for ; Wed, 9 Jan 2008 11:16:41 +0000 (UTC) (envelope-from greycd@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so390818waf.3 for ; Wed, 09 Jan 2008 03:16:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:subject:message-id:x-mailer:mime-version:content-type; bh=XRfy1fdzc7i6qLLEblLKm4k51ND7mAVZviedCxdMTLo=; b=vGHxTOv+2DTOgxRuOUky1xrM3PDVHPqryvEpEl1snQJSzBK6RwoX+lWado4HE+OaO0GAQPb5qOA2DsEB7BKMneJdOrApG4g2HURXAhxGgTP9TPRME+14l9MVsq7tC//3yX30T9JBLhHR2qlkWFZXLKQ8VbTpcKfjEyLNo3vEGVk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:subject:message-id:x-mailer:mime-version:content-type; b=knnYrE9dftZ87YZgKrXqY/Wwy/H0B/sfGL+p0/wrqV+xPJrhNsEB4aKuz7KfBAIHlaWJ1tL7gWnv37pE0DL3eftNNZqLxt/lVWu/295J7JzF8ZIqhEPUhLgkAwfZ608jCd9EY9U/fccNz7woSuDsUEDvpP3plZJb3p18VLj7TYY= Received: by 10.114.181.1 with SMTP id d1mr676934waf.10.1199875905198; Wed, 09 Jan 2008 02:51:45 -0800 (PST) Received: from microsof-ad06c9 ( [210.13.108.116]) by mx.google.com with ESMTPS id k24sm1805055waf.22.2008.01.09.02.51.43 (version=SSLv3 cipher=OTHER); Wed, 09 Jan 2008 02:51:44 -0800 (PST) Date: Wed, 9 Jan 2008 18:51:45 +0800 From: "timo" To: "freebsd-hackers" Message-ID: <200801091851425005991@gmail.com> X-mailer: Foxmail 6, 10, 201, 20 [cn] Mime-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: kernel time sync enabled X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jan 2008 11:16:43 -0000 hi, I'am running freebsd6.2 with apache now in /var/log/message has follow info. anyone can tell me what's the meaning? Jan 9 01:01:02 server1 sshd[4345]: error: channel 0: chan_read_failed for istate 3 Jan 9 01:01:02 server1 sshd[4345]: error: channel 0: chan_read_failed for istate 3 Jan 9 01:01:03 server1 sshd[4396]: error: channel 0: chan_read_failed for istate 3 Jan 9 01:01:03 server1 sshd[4396]: error: channel 0: chan_read_failed for istate 3 Jan 9 01:01:03 server1 sshd[4387]: error: channel 0: chan_read_failed for istate 3 Jan 9 01:01:03 server1 sshd[4387]: error: channel 0: chan_read_failed for istate 3 Jan 9 01:02:20 server1 ntpd[46085]: kernel time sync enabled 6001 Jan 9 01:19:23 server1 ntpd[46085]: kernel time sync enabled 2001 Jan 9 01:53:34 server1 ntpd[46085]: kernel time sync enabled 6001 Jan 9 02:10:40 server1 ntpd[46085]: kernel time sync enabled 2001 Jan 9 04:27:20 server1 ntpd[46085]: kernel time sync enabled 6001 Jan 9 05:52:45 server1 ntpd[46085]: kernel time sync enabled 2001 Jan 9 10:08:50 server1 ntpd[46085]: kernel time sync enabled 6001 Jan 9 10:25:54 server1 ntpd[46085]: kernel time sync enabled 2001 Jan 9 11:26:35 server1 sshd[90201]: error: accept: Software caused connection abort 2008-01-09 _____________________________________________________________________________________________________________________________________ Best Regard Timo msn: timo@live.cn web: https://stand.eicp.net From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 9 11:47:01 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5CF7116A417 for ; Wed, 9 Jan 2008 11:47:01 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4A3F513C4CE for ; Wed, 9 Jan 2008 11:47:01 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 2A6C51CC079; Wed, 9 Jan 2008 03:47:01 -0800 (PST) Date: Wed, 9 Jan 2008 03:47:01 -0800 From: Jeremy Chadwick To: timo Message-ID: <20080109114701.GA55407@eos.sc1.parodius.com> References: <200801091851425005991@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200801091851425005991@gmail.com> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-hackers Subject: Re: kernel time sync enabled X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jan 2008 11:47:01 -0000 On Wed, Jan 09, 2008 at 06:51:45PM +0800, timo wrote: > anyone can tell me what's the meaning? > > Jan 9 01:02:20 server1 ntpd[46085]: kernel time sync enabled 6001 > Jan 9 01:19:23 server1 ntpd[46085]: kernel time sync enabled 2001 > Jan 9 01:53:34 server1 ntpd[46085]: kernel time sync enabled 6001 > Jan 9 02:10:40 server1 ntpd[46085]: kernel time sync enabled 2001 > Jan 9 04:27:20 server1 ntpd[46085]: kernel time sync enabled 6001 > Jan 9 05:52:45 server1 ntpd[46085]: kernel time sync enabled 2001 > Jan 9 10:08:50 server1 ntpd[46085]: kernel time sync enabled 6001 > Jan 9 10:25:54 server1 ntpd[46085]: kernel time sync enabled 2001 Taken from our ntp.conf (used across all our production machines): # maxpoll 9 is used to work around PLL/FLL flipping, which # happens at exactly 1024 seconds (the default maxpoll value). # Another FreeBSD member recommended using 9 instead. # http://lists.freebsd.org/pipermail/freebsd-stable/2006-December/031512.html # server 0.north-america.pool.ntp.org maxpoll 9 iburst server 1.north-america.pool.ntp.org maxpoll 9 server 2.north-america.pool.ntp.org maxpoll 9 -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 9 13:08:43 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AC90D16A41A for ; Wed, 9 Jan 2008 13:08:43 +0000 (UTC) (envelope-from greycd@gmail.com) Received: from po-out-1718.google.com (po-out-1718.google.com [72.14.252.153]) by mx1.freebsd.org (Postfix) with ESMTP id 7D85913C4EE for ; Wed, 9 Jan 2008 13:08:43 +0000 (UTC) (envelope-from greycd@gmail.com) Received: by po-out-1718.google.com with SMTP id a23so198872poh.3 for ; Wed, 09 Jan 2008 05:08:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:cc:references:subject:message-id:x-mailer:mime-version:content-type; bh=AGOPvThtQJ6uVuICgwtUa2fapk1khgtW+vogU3PuUTo=; b=H8Bim2pXA0eIetzJ9SlJlO9C0EFOfIDu7IHR8tHGjMIb046WegPO1Xo3QgmBV6yLpBTWCd7bX2Y/e0dXOeT2skSCriJuLNtdbqK1i8xzpv8KzulqDmvQLl5EYi2z1s+LCp1EW31uBYwYsiLL6pJCtB3TFkAjKPcodRp77QI+Xo4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:references:subject:message-id:x-mailer:mime-version:content-type; b=uwxFqaQaQJNG/sLpvgHOFm0L4WsdUNGINBZI2cN+YYwiy3jr5OZ14KKcgUujn50wXvt5MvkQRLrV+Zx3S2yxpgJo8WhspyvVnbsrr3j8GuzvkxHpS9cMcIB85e5y5m2qB5uNXMTaH3z6LtmRKEj78QEs1KkExv5sMX/tJJdTCm0= Received: by 10.140.82.38 with SMTP id f38mr399514rvb.27.1199884121960; Wed, 09 Jan 2008 05:08:41 -0800 (PST) Received: from microsof-ad06c9 ( [58.40.77.20]) by mx.google.com with ESMTPS id k2sm2221286rvb.36.2008.01.09.05.08.37 (version=SSLv3 cipher=OTHER); Wed, 09 Jan 2008 05:08:40 -0800 (PST) Date: Wed, 9 Jan 2008 21:08:40 +0800 From: "timo" To: "Jeremy Chadwick" References: <200801091851425005991@gmail.com>, <20080109114701.GA55407@eos.sc1.parodius.com> Message-ID: <200801092108369689533@gmail.com> X-mailer: Foxmail 6, 10, 201, 20 [cn] Mime-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers Subject: Re: Re: kernel time sync enabled X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jan 2008 13:08:43 -0000 dGhhbmtzLCBJIGhhdmUgcmVwYWlsIGl0DQoNCg0KMjAwOC0wMS0wOSANCg0KDQoNCiAgDQpfX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fDQpCZXN0ICBSZWdhcmQNClRpbW8gDQptc246IHRpbW9AbGl2ZS5jbg0K DQoNCndlYjogaHR0cHM6Ly9zdGFuZC5laWNwLm5ldA0KDQoNCg0Kt6K8/sjLo7ogSmVyZW15IENo YWR3aWNrIA0Kt6LLzcqxvOSjuiAyMDA4LTAxLTA5ICAxOTo0NzowMyANCsrVvP7Iy6O6IHRpbW8g DQqzrcvNo7ogZnJlZWJzZC1oYWNrZXJzIA0K1vfM4qO6IFJlOiBrZXJuZWwgdGltZSBzeW5jIGVu YWJsZWQgDQogDQpPbiBXZWQsIEphbiAwOSwgMjAwOCBhdCAwNjo1MTo0NVBNICswODAwLCB0aW1v IHdyb3RlOg0KPiBhbnlvbmUgY2FuIHRlbGwgbWUgd2hhdCdzIHRoZSBtZWFuaW5nPw0KPiANCj4g SmFuICA5IDAxOjAyOjIwIHNlcnZlcjEgbnRwZFs0NjA4NV06IGtlcm5lbCB0aW1lIHN5bmMgZW5h YmxlZCA2MDAxDQo+IEphbiAgOSAwMToxOToyMyBzZXJ2ZXIxIG50cGRbNDYwODVdOiBrZXJuZWwg dGltZSBzeW5jIGVuYWJsZWQgMjAwMQ0KPiBKYW4gIDkgMDE6NTM6MzQgc2VydmVyMSBudHBkWzQ2 MDg1XToga2VybmVsIHRpbWUgc3luYyBlbmFibGVkIDYwMDENCj4gSmFuICA5IDAyOjEwOjQwIHNl cnZlcjEgbnRwZFs0NjA4NV06IGtlcm5lbCB0aW1lIHN5bmMgZW5hYmxlZCAyMDAxDQo+IEphbiAg OSAwNDoyNzoyMCBzZXJ2ZXIxIG50cGRbNDYwODVdOiBrZXJuZWwgdGltZSBzeW5jIGVuYWJsZWQg NjAwMQ0KPiBKYW4gIDkgMDU6NTI6NDUgc2VydmVyMSBudHBkWzQ2MDg1XToga2VybmVsIHRpbWUg c3luYyBlbmFibGVkIDIwMDENCj4gSmFuICA5IDEwOjA4OjUwIHNlcnZlcjEgbnRwZFs0NjA4NV06 IGtlcm5lbCB0aW1lIHN5bmMgZW5hYmxlZCA2MDAxDQo+IEphbiAgOSAxMDoyNTo1NCBzZXJ2ZXIx IG50cGRbNDYwODVdOiBrZXJuZWwgdGltZSBzeW5jIGVuYWJsZWQgMjAwMQ0KDQpUYWtlbiBmcm9t IG91ciBudHAuY29uZiAodXNlZCBhY3Jvc3MgYWxsIG91ciBwcm9kdWN0aW9uIG1hY2hpbmVzKToN Cg0KIyBtYXhwb2xsIDkgaXMgdXNlZCB0byB3b3JrIGFyb3VuZCBQTEwvRkxMIGZsaXBwaW5nLCB3 aGljaA0KIyBoYXBwZW5zIGF0IGV4YWN0bHkgMTAyNCBzZWNvbmRzICh0aGUgZGVmYXVsdCBtYXhw b2xsIHZhbHVlKS4NCiMgQW5vdGhlciBGcmVlQlNEIG1lbWJlciByZWNvbW1lbmRlZCB1c2luZyA5 IGluc3RlYWQuDQojIGh0dHA6Ly9saXN0cy5mcmVlYnNkLm9yZy9waXBlcm1haWwvZnJlZWJzZC1z dGFibGUvMjAwNi1EZWNlbWJlci8wMzE1MTIuaHRtbA0KIw0Kc2VydmVyIDAubm9ydGgtYW1lcmlj YS5wb29sLm50cC5vcmcgbWF4cG9sbCA5IGlidXJzdA0Kc2VydmVyIDEubm9ydGgtYW1lcmljYS5w b29sLm50cC5vcmcgbWF4cG9sbCA5DQpzZXJ2ZXIgMi5ub3J0aC1hbWVyaWNhLnBvb2wubnRwLm9y ZyBtYXhwb2xsIDkNCg0KLS0gDQp8IEplcmVteSBDaGFkd2ljayAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgIGpkYyBhdCBwYXJvZGl1cy5jb20gfA0KfCBQYXJvZGl1cyBOZXR3b3Jr aW5nICAgICAgICAgICAgICAgICAgICAgICAgICAgaHR0cDovL3d3dy5wYXJvZGl1cy5jb20vIHwN CnwgVU5JWCBTeXN0ZW1zIEFkbWluaXN0cmF0b3IgICAgICAgICAgICAgICAgICAgICAgTW91bnRh aW4gVmlldywgQ0EsIFVTQSB8DQp8IE1ha2luZyBsaWZlIGhhcmQgZm9yIG90aGVycyBzaW5jZSAx OTc3LiAgICAgICAgICAgICAgICAgIFBHUDogNEJENkMwQ0IgfA0K From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 9 17:58:47 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0AFF316A41A for ; Wed, 9 Jan 2008 17:58:47 +0000 (UTC) (envelope-from deathjestr@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.224]) by mx1.freebsd.org (Postfix) with ESMTP id B954C13C442 for ; Wed, 9 Jan 2008 17:58:45 +0000 (UTC) (envelope-from deathjestr@gmail.com) Received: by wx-out-0506.google.com with SMTP id i29so168039wxd.7 for ; Wed, 09 Jan 2008 09:58:44 -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=hP2k75GgVtInyxeu5t5UcnUTTVjspuHDpjsR7EEaP6s=; b=q75tzoFS8mxyl1IKMF9XpjoFsOQt53ERDe5YPWCuhyTqHttRG6IfexJ695uLZGipBvfFKQDEyxOnyVa2DPYru0kxizMGAsbCKmHKCzBney+psJz1WvB3HVD4Kn3W2jyl9RukQc1qTnPbr7ZSijALRSovAh0d3zG34bUvPLaHu6U= 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=wkgKZ6YCfMuOj1YcbZOhShHU1CL2wMTmLZkRytNEq7g82fHXV5u8JRwkzNjYC1pyv5DenUtah2FMw+EqpEr7Rbu1cIcv7noqcSbUy7AWpsQ2/10DgPbkbb3K/erKkvKmBPS+lDub1HFrHwYDcNZ/Gq8wIaxwfe9/3yQGS2HO5OM= Received: by 10.151.12.1 with SMTP id p1mr366778ybi.83.1199899836475; Wed, 09 Jan 2008 09:30:36 -0800 (PST) Received: by 10.35.41.11 with HTTP; Wed, 9 Jan 2008 09:30:36 -0800 (PST) Message-ID: <44b564930801090930y3ce2014bldaa7e97402683ef7@mail.gmail.com> Date: Wed, 9 Jan 2008 12:30:36 -0500 From: Mike To: "Bharma Ji" In-Reply-To: <47849E42.7090201@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <67beabb0801081555v4ca3b729x294322fa724afa09@mail.gmail.com> <4784159E.9040905@FreeBSD.org> <67beabb0801081925t67f995b8hc4cc779f88c2ba@mail.gmail.com> <66462bcb31fb347796200bd5260d7cdc@gmail.com> <47849E42.7090201@FreeBSD.org> Cc: freebsd-hackers@freebsd.org Subject: Re: Graceful failure instead of panicking in kmem_malloc X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jan 2008 17:58:47 -0000 Bharma Ji wrote: > Is there any way to make the system log and then gracefully shut off instead > of panicking? Is there any way to make the system log and then gracefully shut off while guaranteeing that the logging/shutdown procedure won't also run out memory somewhere? From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 9 23:48:04 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3BF5116A41A for ; Wed, 9 Jan 2008 23:48:04 +0000 (UTC) (envelope-from bharmaji@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.155]) by mx1.freebsd.org (Postfix) with ESMTP id B765C13C44B for ; Wed, 9 Jan 2008 23:48:03 +0000 (UTC) (envelope-from bharmaji@gmail.com) Received: by fg-out-1718.google.com with SMTP id 16so465263fgg.35 for ; Wed, 09 Jan 2008 15:48:02 -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:references; bh=p52KF3Qq51R2fmFRMEhvdUi+pWcfi81fd/TWzjVbki0=; b=KhEhu80BQmnur6PNeuh7ku3P01eTB6rnm2tfYncEK4TfXYafEuJfBcFeXxswvk0DEXXmXAF6h29hyzlcSLKYqIo5NR0t94xb6OIMl0Y7R9LCZLQG+Ny33fE4dWYZM9k3kEID9MxFvojgV3cwKDY0HhK/RwED+4xMWMNCmJ7kwHU= 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:references; b=SbdiSlD3WLLa1tS2IkKphKtuCD+cAmWbbFcEqoGqqKuQXOBFr3OJq6rII3BBvYKkunoHjV4nUz+J62AokalfcTXysNfGsjK/z1XpPd/2fPAlaCEW+kyy+GxOQg29IIUdrNhMImIhbjjnkc/ONkPz+2IYxtV77YmHBEwRH0/+WCA= Received: by 10.78.132.2 with SMTP id f2mr1627199hud.44.1199922481964; Wed, 09 Jan 2008 15:48:01 -0800 (PST) Received: by 10.78.130.18 with HTTP; Wed, 9 Jan 2008 15:48:01 -0800 (PST) Message-ID: <67beabb0801091548p2b0bdf41m193a7a22c95411c4@mail.gmail.com> Date: Wed, 9 Jan 2008 15:48:01 -0800 From: "Bharma Ji" To: Mike , kris@freebsd.org In-Reply-To: <44b564930801090930y3ce2014bldaa7e97402683ef7@mail.gmail.com> MIME-Version: 1.0 References: <67beabb0801081555v4ca3b729x294322fa724afa09@mail.gmail.com> <4784159E.9040905@FreeBSD.org> <67beabb0801081925t67f995b8hc4cc779f88c2ba@mail.gmail.com> <66462bcb31fb347796200bd5260d7cdc@gmail.com> <47849E42.7090201@FreeBSD.org> <44b564930801090930y3ce2014bldaa7e97402683ef7@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers@freebsd.org Subject: Re: Graceful failure instead of panicking in kmem_malloc X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jan 2008 23:48:04 -0000 >Is there any way to make the system log and then gracefully shut off while >guaranteeing that the logging/shutdown procedure won't also run out memory >somewhere? For logging procedure, I am hoping that by keeping some memory aside, I should be able to guarantee that the procedure will not run out of memory. For shutdown, I don't know. I am not sure if doing the usual shutdown is even required. To me this appears to be a generic requirement of any system i.e. a) Set aside some memory to handle out of memory conditions. Establish a low threshold b) When the system reaches the low threshold, 1) stop all processing (not sure right now if this translates to shutdown) 2) record the error. Kris Thanks for sending the patch. The patch essentially will try to reclaim memory 8 times before panicking. Is the understanding correct? If so, how did you arrive at the number 8? On Jan 9, 2008 9:30 AM, Mike wrote: > Bharma Ji wrote: > > Is there any way to make the system log and then gracefully shut off > instead > > of panicking? > > Is there any way to make the system log and then gracefully shut off while > guaranteeing that the logging/shutdown procedure won't also run out memory > somewhere? > From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 11 03:40:11 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8487C16A41A for ; Fri, 11 Jan 2008 03:40:11 +0000 (UTC) (envelope-from john.giacomoni@colorado.edu) Received: from suburban.colorado.edu (suburban.colorado.edu [128.138.189.14]) by mx1.freebsd.org (Postfix) with ESMTP id 5E08F13C469 for ; Fri, 11 Jan 2008 03:40:11 +0000 (UTC) (envelope-from john.giacomoni@colorado.edu) Received: from localhost (suburban.colorado.edu [127.0.0.1]) by suburban.colorado.edu (8.13.1/8.13.1) with ESMTP id m0ANmTOr004538 for ; Thu, 10 Jan 2008 18:48:29 -0500 Message-Id: From: John Giacomoni To: freebsd-hackers@freebsd.org Content-Type: multipart/mixed; boundary=Apple-Mail-347-521328921 Mime-Version: 1.0 (Apple Message framework v915) Date: Thu, 10 Jan 2008 19:42:24 -0700 X-Mailer: Apple Mail (2.915) X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Running without clock interrupts? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jan 2008 03:40:11 -0000 --Apple-Mail-347-521328921 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit I'd like to run a long loop with a minimum of interrupts, specifically without any scheduler or timer interrupts, the introduced jitter is noticeable. Is this possible in FreeBSD 7? If so how should I proceed? I can take as long as I need after the loop has completed to restore/ reinitialize any necessary state. I do want to be able to process other interrupts to handle page faults and the like. I'm working on dual core dual processor amd opteron setups right now and would like to support the intel family processors as well. It seems that what I want to do is to disable/mask acpi timer interrupts for the processor but trying to read the 0xfee00320 register (lvt_timer) causes a panic. Alternatively, I could hook in the timer handler to return immediately when a flag is set, though this still might introduce more jitter than I'd like. Thanks, John Giacomoni -- John.Giacomoni@colorado.edu University of Colorado at Boulder Department of Computer Science Engineering Center, ECCR 1B50 430 UCB Boulder, CO 80303-0430 USA --Apple-Mail-347-521328921 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit --Apple-Mail-347-521328921-- From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 11 16:08:09 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 97BAF16A419 for ; Fri, 11 Jan 2008 16:08:09 +0000 (UTC) (envelope-from gizmen@blurp.pl) Received: from albion.azs.pwr.wroc.pl (albion.azs.pwr.wroc.pl [156.17.17.145]) by mx1.freebsd.org (Postfix) with ESMTP id 4E69713C46A for ; Fri, 11 Jan 2008 16:08:09 +0000 (UTC) (envelope-from gizmen@blurp.pl) Received: from [10.8.1.58] (unknown [213.172.177.22]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by albion.azs.pwr.wroc.pl (Postfix) with ESMTP id 72727115E6 for ; Fri, 11 Jan 2008 16:52:52 +0100 (CET) From: Bartosz Giza Organization: BLURP.pl To: freebsd-hackers@freebsd.org Date: Fri, 11 Jan 2008 16:52:50 +0100 User-Agent: KMail/1.9.7 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200801111652.50612.gizmen@blurp.pl> Subject: kernel panic while using tcpdump X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jan 2008 16:08:09 -0000 Hi, We are using a lot of i386 computers as routers for out network. All of those routers are using FreeBSD from 4.x to 7.x (exept 5.x) We are having problem with kernel panic on routers based on 6.x and 7.x while using tcpdump or trafshow. It is not that always we got kernel panics. We got them in random occurence. Some time i can tcpdump for a minute and turn it off and again while i am testing packets comming thru iface for an hour, and nothin happens. But sometime i run tcpdump and after few second i got kernel panic. It happens mostly when i am trying to close tcpdump with ctrl-c. It happens also with trafshow3 which we are using to track transfers. It happens on 6.x series and i thought that maybe there is bug in this line and i have tryied 7.x line i got kernel panics also. The problem is that i can't really get message when it happens because those routers are in remote places and after 15 second they are rebooting (and that is great:) Is there any way to save this message to a file that i could paste over here ? Could some one help me to diagnoze this behaviour ? We are using i386 arch on all routers. The hardware is totally different from quite old parts to quite new dell. What is strange on 4.x we never hit such a kernel panic. We are using mostly fxp NIC on all routers with some exeptions and i have started wondering that maybe fxp driver has some bug or bpf code. Thanks for any help in diagnosing this panics. From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 11 16:21:29 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6104016A469 for ; Fri, 11 Jan 2008 16:21:29 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 8305813C455; Fri, 11 Jan 2008 16:21:27 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <47879785.9010806@FreeBSD.org> Date: Fri, 11 Jan 2008 17:21:25 +0100 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: Bartosz Giza References: <200801111652.50612.gizmen@blurp.pl> In-Reply-To: <200801111652.50612.gizmen@blurp.pl> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: kernel panic while using tcpdump X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jan 2008 16:21:29 -0000 Bartosz Giza wrote: > Hi, > > We are using a lot of i386 computers as routers for out network. All of those > routers are using FreeBSD from 4.x to 7.x (exept 5.x) > > We are having problem with kernel panic on routers based on 6.x and 7.x while > using tcpdump or trafshow. It is not that always we got kernel panics. We got > them in random occurence. Some time i can tcpdump for a minute and turn it > off and again while i am testing packets comming thru iface for an hour, and > nothin happens. But sometime i run tcpdump and after few second i got kernel > panic. It happens mostly when i am trying to close tcpdump with ctrl-c. > It happens also with trafshow3 which we are using to track transfers. > > It happens on 6.x series and i thought that maybe there is bug in this line > and i have tryied 7.x line i got kernel panics also. > > The problem is that i can't really get message when it happens because those > routers are in remote places and after 15 second they are rebooting (and that > is great:) > > Is there any way to save this message to a file that i could paste over here ? > > Could some one help me to diagnoze this behaviour ? > > We are using i386 arch on all routers. The hardware is totally different from > quite old parts to quite new dell. > What is strange on 4.x we never hit such a kernel panic. > > We are using mostly fxp NIC on all routers with some exeptions and i have > started wondering that maybe fxp driver has some bug or bpf code. > > Thanks for any help in diagnosing this panics. > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html Kris From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 11 20:12:41 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B1C2C16A41B for ; Fri, 11 Jan 2008 20:12:41 +0000 (UTC) (envelope-from freebsd-hackers@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 3B5AC13C45D for ; Fri, 11 Jan 2008 20:12:40 +0000 (UTC) (envelope-from freebsd-hackers@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1JDQF2-0004GK-6P for freebsd-hackers@freebsd.org; Fri, 11 Jan 2008 20:12:36 +0000 Received: from 78-1-116-131.adsl.net.t-com.hr ([78.1.116.131]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 11 Jan 2008 20:12:36 +0000 Received: from ivoras by 78-1-116-131.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 11 Jan 2008 20:12:36 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-hackers@freebsd.org From: Ivan Voras Date: Fri, 11 Jan 2008 21:12:27 +0100 Lines: 46 Message-ID: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig14A246A22C6231A0328C3E14" X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 78-1-116-131.adsl.net.t-com.hr User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) X-Enigmail-Version: 0.95.6 Sender: news Subject: Coverity problems? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jan 2008 20:12:41 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig14A246A22C6231A0328C3E14 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Hi, I got a link to this article via ACM TechNews:=20 http://www.informationweek.com/story/showArticle.jhtml?articleID=3D205600= 229&%0Acid=3DRSSfeed_IWK_All """ Linux came in with far fewer defects than average as did a number of=20 other open source projects. The version 2.6 of the Linux kernel had a=20 security bug rate of .127 per thousand lines of code. The kernel scan=20 covered 3,639,322 lines of code. As exposures were identified by=20 repeated scans, 452 defects have been fixed by kernel developers; 48=20 have been verified but not yet fixed; another 413 remain to be verified=20 and fixed, according to code scanning results posted on the Coverity Web = site. FreeBSD, sometimes posed as an alternative to Linux, has been slower to=20 respond to the Coverity scans. In 1,582,166 lines of code, it has fixed=20 zero defects, verified six and has another 605 to go. """ These numbers seem strange and out of proportion. I know there has been=20 prior cooperation with Coverity - is this just old data? --------------enig14A246A22C6231A0328C3E14 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.2.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHh82rldnAQVacBcgRAuI6AJ9Oz82EwzDaqUqF+Vc5nYSIvhRKUQCfaroR rRuXNtbbtX9nS6mctk0yGGU= =MiZF -----END PGP SIGNATURE----- --------------enig14A246A22C6231A0328C3E14-- From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 11 21:23:31 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2128116A419; Fri, 11 Jan 2008 21:23:31 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (lefty.soaustin.net [66.135.55.46]) by mx1.freebsd.org (Postfix) with ESMTP id 0969A13C47E; Fri, 11 Jan 2008 21:23:30 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id 0F5B38C0F8; Fri, 11 Jan 2008 14:57:04 -0600 (CST) Date: Fri, 11 Jan 2008 14:57:04 -0600 To: Ivan Voras Message-ID: <20080111205704.GE4787@soaustin.net> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.13 (2006-08-11) From: linimon@lonesome.com (Mark Linimon) X-Mailman-Approved-At: Fri, 11 Jan 2008 22:04:50 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: Coverity problems? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jan 2008 21:23:31 -0000 On Fri, Jan 11, 2008 at 09:12:27PM +0100, Ivan Voras wrote: > These numbers seem strange and out of proportion. I know there has been > prior cooperation with Coverity - is this just old data? IIRC Coverity is not tracking our use of their software, at least in those statistics. Someone was telling me yesterday that was because we have our own copy of the Coverity server which we use, rather than accessing the one on their site that generates the statistics. Someone, please correct me if I'm wrong. mcl From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 11 22:55:07 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B4E8716A418; Fri, 11 Jan 2008 22:55:07 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 7B00813C448; Fri, 11 Jan 2008 22:55:07 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.2/8.14.2) with ESMTP id m0BMRRte011493; Fri, 11 Jan 2008 15:27:27 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.2/8.14.2/Submit) with ESMTP id m0BMRRoH011490; Fri, 11 Jan 2008 15:27:27 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Fri, 11 Jan 2008 15:27:27 -0700 (MST) From: Warren Block To: Mark Linimon In-Reply-To: <20080111205704.GE4787@soaustin.net> Message-ID: <20080111152611.J11483@wonkity.com> References: <20080111205704.GE4787@soaustin.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (wonkity.com [127.0.0.1]); Fri, 11 Jan 2008 15:27:27 -0700 (MST) Cc: freebsd-hackers@freebsd.org, Ivan Voras Subject: Re: Coverity problems? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jan 2008 22:55:07 -0000 On Fri, 11 Jan 2008, Mark Linimon wrote: > On Fri, Jan 11, 2008 at 09:12:27PM +0100, Ivan Voras wrote: >> These numbers seem strange and out of proportion. I know there has been >> prior cooperation with Coverity - is this just old data? > > IIRC Coverity is not tracking our use of their software, at least in > those statistics. Someone was telling me yesterday that was because > we have our own copy of the Coverity server which we use, rather than > accessing the one on their site that generates the statistics. > > Someone, please correct me if I'm wrong. You're right. See the January 11, 2008 note here: http://scan.coverity.com/ -Warren Block * Rapid City, South Dakota USA From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 11 23:06:11 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 40FE216A419; Fri, 11 Jan 2008 23:06:11 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 22A2E13C45B; Fri, 11 Jan 2008 23:06:10 +0000 (UTC) (envelope-from sam@errno.com) Received: from Macintosh-2.local ([10.0.0.196]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id m0BMdCIC012897 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 11 Jan 2008 14:39:12 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <4787F00F.6070405@errno.com> Date: Fri, 11 Jan 2008 14:39:11 -0800 From: Sam Leffler Organization: Errno Consulting User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: Mark Linimon References: <20080111205704.GE4787@soaustin.net> In-Reply-To: <20080111205704.GE4787@soaustin.net> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC--Metrics: ebb.errno.com; whitelist Cc: freebsd-hackers@freebsd.org, Ivan Voras Subject: Re: Coverity problems? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jan 2008 23:06:11 -0000 Mark Linimon wrote: > On Fri, Jan 11, 2008 at 09:12:27PM +0100, Ivan Voras wrote: >> These numbers seem strange and out of proportion. I know there has been >> prior cooperation with Coverity - is this just old data? > > IIRC Coverity is not tracking our use of their software, at least in > those statistics. Someone was telling me yesterday that was because > we have our own copy of the Coverity server which we use, rather than > accessing the one on their site that generates the statistics. > > Someone, please correct me if I'm wrong. You are correct; we've had a private coverity server doing nightly runs long before coverity setup this service (the project has their own license through the FreeBSD Foundation). I have no idea why coverity continues to do freebsd runs as the results are also not meaningful because their default models generate false positives that we've long since filtered out. Sam From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 11 23:21:44 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3E46316A420; Fri, 11 Jan 2008 23:21:44 +0000 (UTC) (envelope-from chris@hitnet.RWTH-Aachen.DE) Received: from mta-1.ms.rz.rwth-aachen.de (mta-1.ms.rz.RWTH-Aachen.DE [134.130.7.72]) by mx1.freebsd.org (Postfix) with ESMTP id F0CC613C455; Fri, 11 Jan 2008 23:21:43 +0000 (UTC) (envelope-from chris@hitnet.RWTH-Aachen.DE) Received: from ironport-out-1.rz.rwth-aachen.de ([134.130.3.58]) by mta-1.ms.rz.RWTH-Aachen.de (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTP id <0JUI00BMA4U6EWA0@mta-1.ms.rz.RWTH-Aachen.de>; Fri, 11 Jan 2008 23:51:42 +0100 (CET) Received: from smarthost-1.ms.rz.rwth-aachen.de (HELO smarthost.rwth-aachen.de) ([134.130.7.89]) by ironport-in-1.rz.rwth-aachen.de with ESMTP; Fri, 11 Jan 2008 23:51:42 +0100 Received: from bigboss.hitnet.rwth-aachen.de (bigspace.hitnet.RWTH-Aachen.DE [137.226.181.2]) by smarthost.rwth-aachen.de (8.13.8+Sun/8.13.8/1) with ESMTP id m0BMpfkr024523; Fri, 11 Jan 2008 23:51:42 +0100 (CET) Received: from haakonia.hitnet.rwth-aachen.de ([137.226.181.92]) by bigboss.hitnet.rwth-aachen.de with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from ) id 1JDSiz-000359-Ut; Fri, 11 Jan 2008 23:51:41 +0100 Received: by haakonia.hitnet.rwth-aachen.de (Postfix, from userid 1001) id A868A3F421; Fri, 11 Jan 2008 23:51:41 +0100 (CET) Date: Fri, 11 Jan 2008 23:51:41 +0100 From: Christian Brueffer In-reply-to: <20080111205704.GE4787@soaustin.net> To: Mark Linimon Message-id: <20080111225141.GC3593@haakonia.hitnet.RWTH-Aachen.DE> MIME-version: 1.0 Content-type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary=WplhKdTI2c8ulnbP Content-disposition: inline X-IronPort-AV: E=Sophos;i="4.24,273,1196636400"; d="scan'208";a="43863485" X-Operating-System: FreeBSD 6.3-PRERELEASE X-PGP-Key: http://people.FreeBSD.org/~brueffer/brueffer.key.asc X-PGP-Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D References: <20080111205704.GE4787@soaustin.net> User-Agent: Mutt/1.5.11 Cc: freebsd-hackers@freebsd.org, Ivan Voras Subject: Re: Coverity problems? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jan 2008 23:21:44 -0000 --WplhKdTI2c8ulnbP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 11, 2008 at 02:57:04PM -0600, Mark Linimon wrote: > On Fri, Jan 11, 2008 at 09:12:27PM +0100, Ivan Voras wrote: > > These numbers seem strange and out of proportion. I know there has been= =20 > > prior cooperation with Coverity - is this just old data? >=20 > IIRC Coverity is not tracking our use of their software, at least in > those statistics. Someone was telling me yesterday that was because > we have our own copy of the Coverity server which we use, rather than > accessing the one on their site that generates the statistics. >=20 > Someone, please correct me if I'm wrong. >=20 Yes, also take a look at http://www.informationweek.com/blog/main/archives/2008/01/oops_look_at_th.h= tml Corrections to the article by the same author. - Christian --=20 Christian Brueffer chris@unixpages.org brueffer@FreeBSD.org GPG Key: http://people.freebsd.org/~brueffer/brueffer.key.asc GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D --WplhKdTI2c8ulnbP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFHh/L9bHYXjKDtmC0RAi00AKCkZFUFGjtd23+PTW6BwRNAxezCwgCdH36S oB27QpEaVOquOjQfJfxP3gk= =tUxE -----END PGP SIGNATURE----- --WplhKdTI2c8ulnbP-- From owner-freebsd-hackers@FreeBSD.ORG Sat Jan 12 04:26:27 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4C3DA16A420 for ; Sat, 12 Jan 2008 04:26:27 +0000 (UTC) (envelope-from subhashg.unix@gmail.com) Received: from hu-out-0506.google.com (hu-out-0506.google.com [72.14.214.239]) by mx1.freebsd.org (Postfix) with ESMTP id D763313C467 for ; Sat, 12 Jan 2008 04:26:26 +0000 (UTC) (envelope-from subhashg.unix@gmail.com) Received: by hu-out-0506.google.com with SMTP id 28so539353hub.8 for ; Fri, 11 Jan 2008 20:26:25 -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=fL3MgB+0J8blBu1b3qBtXoJElvsbrDWGMu5iB05gz9I=; b=RfCqqeB5d1zPoqs7KbgDTRfBW0gNhbMENiIh4d494wLGBWwPed65VD6LjI+SeIusuUMGEPxzgeh8IuEbDsBLYDAPfNRJ88sEh7BDfwCqMai99XTX6j6tKuH1gi+9R+A6dheQLACA41g8fJ+bqwxgfr73Fw3+eVWcQhce2LNT+wI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=d95iaIV+9F/ftw2bVMYQ9jbUuAKOI1/BhnnpjmTmFYoKHMjYr3Gim1faNyFOeudVDc5oteAzWtOU1JlBGJAN31nYXEZ4pQ+y5yIAJV9b4V+uQmER4m/S0eCS8yOiaWlJ4oR6NH5u3RYituPT4jY9PyxM5kiWYNqcXSWRDWCpCG4= Received: by 10.78.132.2 with SMTP id f2mr4816481hud.19.1200111034750; Fri, 11 Jan 2008 20:10:34 -0800 (PST) Received: by 10.78.187.8 with HTTP; Fri, 11 Jan 2008 20:10:34 -0800 (PST) Message-ID: <5db9d2e0801112010s55812b20p6a43f0fbb5cddd17@mail.gmail.com> Date: Fri, 11 Jan 2008 20:10:34 -0800 From: "Subhash Gopinath" To: freebsd-hackers@freebsd.org 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: netgraph question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Jan 2008 04:26:27 -0000 Hello folks, I am looking at writing an application program to tap certain ipv6 packets (say icmpv6) using netgraph. The application has to do some processing, before kernel can proceed with those packets. I have vaguely understood netgraph, and I see that I need a ng_socket node in the application, an ng_bpf node, and an ng_ether or ng_iface node in the kernel. My question is. would I need to create such nodes for each interface. Then it becomes unscalable.. Can I have just one socket, bpf, iface node that can tap icmpv6 packets on all interfaces? I'll reiterate if this question was not clear. Any help would be greatly appreciated... Otherwise I'll have to end up using raw sockets.. Thanks, Subhash From owner-freebsd-hackers@FreeBSD.ORG Sat Jan 12 07:02:18 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3223B16A417 for ; Sat, 12 Jan 2008 07:02:18 +0000 (UTC) (envelope-from lstewart@freebsd.org) Received: from outbound.icp-qv1-irony-out1.iinet.net.au (outbound.icp-qv1-irony-out1.iinet.net.au [203.59.1.108]) by mx1.freebsd.org (Postfix) with ESMTP id B286713C455 for ; Sat, 12 Jan 2008 07:02:17 +0000 (UTC) (envelope-from lstewart@freebsd.org) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ao8CADbth0d8qBDq/2dsb2JhbACqCA X-IronPort-AV: E=Sophos;i="4.24,275,1196607600"; d="scan'208";a="274062850" Received: from unknown (HELO newbox.caia.swin.edu.au) ([124.168.16.234]) by outbound.icp-qv1-irony-out1.iinet.net.au with ESMTP; 12 Jan 2008 15:32:17 +0900 Message-ID: <47885EF3.8070104@freebsd.org> Date: Sat, 12 Jan 2008 17:32:19 +1100 From: Lawrence Stewart User-Agent: Thunderbird 2.0.0.4 (X11/20070625) MIME-Version: 1.0 To: Subhash Gopinath References: <5db9d2e0801112010s55812b20p6a43f0fbb5cddd17@mail.gmail.com> In-Reply-To: <5db9d2e0801112010s55812b20p6a43f0fbb5cddd17@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: netgraph question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Jan 2008 07:02:18 -0000 Hi Subhash, Subhash Gopinath wrote: > Hello folks, > > I am looking at writing an application program to tap certain ipv6 packets > (say icmpv6) > using netgraph. The application has to do some processing, before kernel can > proceed > with those packets. > > I have vaguely understood netgraph, and I see that I need a ng_socket node > in the application, an ng_bpf node, and an ng_ether or ng_iface node in the > kernel. > > My question is. would I need to create such nodes for each interface. Then > it becomes unscalable.. > Can I have just one socket, bpf, iface node that can tap icmpv6 packets on > all interfaces? The PFIL(9) interface might also be of interest to you. If all you need to do is packet interception and then allow/deny packets based on the results of some processing, PFIL might be the way to go. We wrote some code (SIFTR [1]) which uses PFIL in a similar capacity and you may want to refer to it as an example. Cheers, Lawrence [1] http://caia.swin.edu.au/urp/newtcp/tools.html From owner-freebsd-hackers@FreeBSD.ORG Sat Jan 12 19:40:08 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C71CB16A419 for ; Sat, 12 Jan 2008 19:40:08 +0000 (UTC) (envelope-from subhashg.unix@gmail.com) Received: from hu-out-0506.google.com (hu-out-0506.google.com [72.14.214.228]) by mx1.freebsd.org (Postfix) with ESMTP id 33FEA13C459 for ; Sat, 12 Jan 2008 19:40:07 +0000 (UTC) (envelope-from subhashg.unix@gmail.com) Received: by hu-out-0506.google.com with SMTP id 28so615349hub.8 for ; Sat, 12 Jan 2008 11:40:06 -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=hcZDKdnK6eGSqVSvCMbm9OTWapTfyUEymRS7MI6ggR0=; b=hHg2CpgOePEbGqxRSW62p+EB7DV6B+wuTBwZi/IYH9tmnHub1MC+qH7sD7x5jaQknv6/yUZUwA5t7CdnK5bVNbw5CMYA91TUP6HjRxRIUj7BzpHijsnzkSTMe0M0kpE3YOo2//kv5EbRg+NR9o7baoOFaCUuycG9fzblwBCAq9A= 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=o8SXbfltOa8++0wI4z6jKj0KljlYO6l/7NEBbFgRWHLi4Jdee4thsNraPJ8HLej7VaS2zNAqO86aP7PtDgiVEvdB6ryTJ9X4yq63CqEBgEbKkTRfllh5JqJx6YcYJOOnsF++bmKnmlc2VunzYBFF16Nc55s4RIW/NoWdUKYhL5M= Received: by 10.78.129.16 with SMTP id b16mr5479260hud.39.1200166805934; Sat, 12 Jan 2008 11:40:05 -0800 (PST) Received: by 10.78.187.8 with HTTP; Sat, 12 Jan 2008 11:40:05 -0800 (PST) Message-ID: <5db9d2e0801121140x76c26a6k20e12a21db4cf0ae@mail.gmail.com> Date: Sat, 12 Jan 2008 11:40:05 -0800 From: "Subhash Gopinath" To: "Lawrence Stewart" In-Reply-To: <47885EF3.8070104@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <5db9d2e0801112010s55812b20p6a43f0fbb5cddd17@mail.gmail.com> <47885EF3.8070104@freebsd.org> Cc: freebsd-hackers@freebsd.org Subject: Re: netgraph question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Jan 2008 19:40:08 -0000 Thanks, looks interesting. But I was looking at processing the packets in userspace. Sorry I didn't mention it clearly. Thanks, -Subhash On Jan 11, 2008 10:32 PM, Lawrence Stewart wrote: > Hi Subhash, > > Subhash Gopinath wrote: > > Hello folks, > > > > I am looking at writing an application program to tap certain ipv6 packets > > (say icmpv6) > > using netgraph. The application has to do some processing, before kernel can > > proceed > > with those packets. > > > > I have vaguely understood netgraph, and I see that I need a ng_socket node > > in the application, an ng_bpf node, and an ng_ether or ng_iface node in the > > kernel. > > > > My question is. would I need to create such nodes for each interface. Then > > it becomes unscalable.. > > Can I have just one socket, bpf, iface node that can tap icmpv6 packets on > > all interfaces? > > The PFIL(9) interface might also be of interest to you. If all you need > to do is packet interception and then allow/deny packets based on the > results of some processing, PFIL might be the way to go. We wrote some > code (SIFTR [1]) which uses PFIL in a similar capacity and you may want > to refer to it as an example. > > Cheers, > Lawrence > > [1] http://caia.swin.edu.au/urp/newtcp/tools.html >