From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 2 04:53:20 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8982216A4CE; Sun, 2 Nov 2003 04:53:20 -0800 (PST) Received: from smtpzilla2.xs4all.nl (smtpzilla2.xs4all.nl [194.109.127.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 35F9043FAF; Sun, 2 Nov 2003 04:53:19 -0800 (PST) (envelope-from wkb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtpzilla2.xs4all.nl (8.12.9/8.12.9) with ESMTP id hA2CrFN9082106; Sun, 2 Nov 2003 13:53:16 +0100 (CET) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.12.9p2/8.12.9) with ESMTP id hA2CrFf1000280; Sun, 2 Nov 2003 13:53:15 +0100 (CET) (envelope-from wkb@freebie.xs4all.nl) Received: (from wkb@localhost) by freebie.xs4all.nl (8.12.9p2/8.12.9/Submit) id hA2CrF2r000279; Sun, 2 Nov 2003 13:53:15 +0100 (CET) (envelope-from wkb) Date: Sun, 2 Nov 2003 13:53:14 +0100 From: Wilko Bulte To: Orion Hodson Message-ID: <20031102125314.GA241@freebie.xs4all.nl> References: <20030819230111.GA239@freebie.xs4all.nl> <200308192332.h7JNWUTU028766@puma.icir.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200308192332.h7JNWUTU028766@puma.icir.org> User-Agent: Mutt/1.4.1i X-OS: FreeBSD 4.9-STABLE X-PGP: finger wilko@freebsd.org cc: Rudolf Cejka cc: hackers@freebsd.org Subject: Re: ASUS P4P800-VM + AD1980 (Was Re: VIA8235 + AD1980) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2003 12:53:20 -0000 On Tue, Aug 19, 2003 at 04:32:30PM -0700, Orion Hodson wrote: > /-- Wilko Bulte wrote: > | > | hi, sorry for jumping in late: what is/is not now in 4.8-stable > | as far as the patches go to make the Asus P4P800 work? > | > | I get as far as: > | > | wkb@freebie ~: dmesg| grep pcm > | pcm0: port 0xee80-0xeebf,0xe800-0xe8ff mem > | 0xfebff400-0xfebff4ff,0xfebff800-0xfebff9ff irq 10 at device 31.5 on pci0 > | pcm0: > | wkb@freebie ~: cat /dev/sndstat > | FreeBSD Audio Driver (newpcm) > | Installed devices: > | pcm0: at io 0xfebff800, 0xfebff400 irq 10 bufsz 16384 > | (1p/1r/0v channels duplex) > | wkb@freebie ~: > > Okay, I've not looked at the specs for the AD1985 at all or looked into what other folks are doing regarding custom initialization patches for it. We don't have any code in the tree at present that is likely to help. A similar patch to Oleg's submission for the AD1980 might be applicable, but that's not in the tree today (still thinking about some general issues arising relating to this). Just for the record: 4.9R / 4.9-stable still have the 'no sound' problem on the P4P800. Rudolf's patches apply cleanly, and then sound is working. -- | / o / /_ _ wilko@FreeBSD.org |/|/ / / /( (_) Bulte From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 2 07:59:35 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0A2A316A4CE for ; Sun, 2 Nov 2003 07:59:35 -0800 (PST) Received: from www.kukulies.org (www.kukulies.org [213.146.112.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 870FD43F75 for ; Sun, 2 Nov 2003 07:59:33 -0800 (PST) (envelope-from kuku@www.kukulies.org) Received: from www.kukulies.org (localhost [127.0.0.1]) by www.kukulies.org (8.12.10/8.12.6) with ESMTP id hA2FxUoR003916 for ; Sun, 2 Nov 2003 16:59:30 +0100 (CET) (envelope-from kuku@www.kukulies.org) Received: (from kuku@localhost) by www.kukulies.org (8.12.10/8.12.6/Submit) id hA2FxTjn003915 for hackers@freebsd.org; Sun, 2 Nov 2003 16:59:29 +0100 (CET) Date: Sun, 2 Nov 2003 16:59:29 +0100 (CET) From: "C. Kukulies" Message-Id: <200311021559.hA2FxTjn003915@www.kukulies.org> To: hackers@freebsd.org Subject: spambouncer tags much freebsd list mail as spam X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2003 15:59:35 -0000 I installed the spambouncer.org procmail script and before I was switching the behaviour from SILENT to COMPLAIN I took a look at my spam.incoming folder and found a lot of messages from freebsd-bugs and freebsd-mobile in there. Both lists are not directed to folders prior to spambouncer coming into effect so they are trapped by spambouncer and I suspect that other freebsd lists would be trapped as well. Anyone experienced similar? -- Chris Christoph P. U. Kukulies kuku_at_physik.rwth-aachen.de From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 2 10:06:15 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2D2F016A4CF for ; Sun, 2 Nov 2003 10:06:15 -0800 (PST) Received: from smtp.inode.at (smtp-04.inode.at [62.99.194.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5241643F85 for ; Sun, 2 Nov 2003 10:06:14 -0800 (PST) (envelope-from mranner@inode.at) Received: from line-m-40.adsl-dynamic.inode.at ([81.223.113.40]:1749) by smtp.inode.at with esmtp (Exim 4.10) id 1AGMc3-0001M7-00; Sun, 02 Nov 2003 19:06:07 +0100 From: Michael Ranner To: "C. Kukulies" , hackers@freebsd.org Date: Sun, 2 Nov 2003 19:05:58 +0100 User-Agent: KMail/1.5 References: <200311021559.hA2FxTjn003915@www.kukulies.org> In-Reply-To: <200311021559.hA2FxTjn003915@www.kukulies.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200311021905.58534.mranner@inode.at> Subject: Re: spambouncer tags much freebsd list mail as spam X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2003 18:06:15 -0000 Am Sonntag, 2. November 2003 16:59 schrieb C. Kukulies: > I installed the spambouncer.org procmail script and before I was switching > the behaviour from SILENT to COMPLAIN I took a look at my spam.incoming > folder and found a lot of messages from freebsd-bugs and freebsd-mobile in > there. > > Both lists are not directed to folders prior to spambouncer coming into > effect so they are trapped by spambouncer and I suspect that other freebsd > lists would be trapped as well. Filter mails from FreeBSD mailing lists with List-Id: header in procmail before spam checking or filter by an different header like Sender. This works well under kmail with spamassassin. Regards, -- /\/\ichael Ranner mranner@inode.at - mranner@jawa.at - mranner@bugat.at ----------------------------------------------------- BSD Usergroup Austria - http://www.bugat.at/ -----BEGIN GEEK CODE BLOCK----- GIT/CS/AT dx(-) s+:(++:) a- C++ UBLVS++++$ P++>+++$ L-(+)$ E--- W+++$ N+(++) o-- K- w--()$ O-(--) M@ V-(--) PS+>++ PE(-) Y+ PGP(-) t+ 5+ X+++(++++) R* tv++ b+(++) DI++ D-(--) G- e h--(*) r++ y? ------END GEEK CODE BLOCK------ From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 2 10:19:57 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0F68416A4CE for ; Sun, 2 Nov 2003 10:19:57 -0800 (PST) Received: from gatekeeper.syskonnect.de (gatekeeper.syskonnect.de [213.144.13.149]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0322943FE0 for ; Sun, 2 Nov 2003 10:19:55 -0800 (PST) (envelope-from gheinig@syskonnect.de) Received: from syskonnect.de (spock [10.9.15.1])h9VI3E69026726 for ; Fri, 31 Oct 2003 19:03:18 +0100 (MET) Received: from syskonnect.de (localhost [127.0.0.1]) by syskonnect.de (8.12.9/8.12.9) with ESMTP id h9VI2o8q003726 for ; Fri, 31 Oct 2003 19:02:50 +0100 (MET) X-Authentication-Warning: spock.skd.de: iscan owned process doing -bs Sender: gheinig@syskonnect.de Message-ID: <3FA29FF2.F0F3C009@syskonnect.de> Date: Fri, 31 Oct 2003 18:46:26 +0100 From: Gerald Heinig Organization: SysKonnect GmbH X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.18 i686) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: kernel malloc usage X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2003 18:19:57 -0000 Hi all, I have a question concerning the use of malloc to allocate small amounts of memory for packet wrappers for certain packets. Basically, I'm using malloc in much the same way as one would use it in a standard userland program: allocating small chunks and freeing them again a short(ish) time later. A colleague said this was a bad idea, since malloc should only really be used to allocate larger chunks (PAGE_SIZE and over) at driver initialisation. Management and partition of the allocated space should be done by the driver. His reason was that over time, the kernel heap memory gets progressively more fragmented until it becomes difficult to get larger blocks. Is this true? I seem to remember that FreeBSD has a slab allocator, which IIRC is particularly good at allocating small chunks. Is it a better idea to write my own allocators which use a larger block of memory allocated by malloc at driver start-time, or can I use malloc as in userland? Cheers, Gerald -- S y s K o n n e c t G m b H A Marvell Company Siemensstr. 23 D-76275 Ettlingen, Germany --------------------------------- Gerald Heinig Software Engineer ------------------------------------- phone: + 49 (0) 7243 502 354 fax: +49 (0) 7243 502 364 email: gheinig@syskonnect.de http://www.syskonnect.com From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 2 10:46:57 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B077616A4CF for ; Sun, 2 Nov 2003 10:46:57 -0800 (PST) Received: from smtp5.hy.skanova.net (smtp5.hy.skanova.net [195.67.199.134]) by mx1.FreeBSD.org (Postfix) with ESMTP id 80D7A43FCB for ; Sun, 2 Nov 2003 10:46:56 -0800 (PST) (envelope-from pawh_thm@swipnet.se) Received: from ultrix.homeunix.net (h102n2fls32o846.telia.com [213.67.16.102]) by smtp5.hy.skanova.net (8.12.10/8.12.10) with SMTP id hA2IktIf022591 for ; Sun, 2 Nov 2003 19:46:55 +0100 (CET) Date: Sun, 2 Nov 2003 19:46:55 +0100 From: Peter =?ISO-8859-1?Q?Hagstr=F6m?= To: hackers@freebsd.org Message-Id: <20031102194655.765a61ef.pawh_thm@swipnet.se> X-Mailer: Sylpheed version 0.9.3claws (GTK+ 1.2.10; i386-portbld-freebsd5.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Wierd problems with 5.1Current X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2003 18:46:57 -0000 After fsck background check, the system ends up with dev = ad1s1, block = 1, fs = /mnt/mellan panic: ffs_blkfree: freeing free block irq 1 at atkbd0 panic page fault And the official Nvidia driver doesnt seems to work.. Cvsuped the tree earlier this day and just wonders if any one know whats wrong or how i can get it working? /Peter From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 2 12:13:39 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5935416A4CE for ; Sun, 2 Nov 2003 12:13:39 -0800 (PST) Received: from mail.numachi.com (meisai.numachi.com [198.175.254.6]) by mx1.FreeBSD.org (Postfix) with SMTP id E4D4E43FBF for ; Sun, 2 Nov 2003 12:13:37 -0800 (PST) (envelope-from reichert@numachi.com) Received: (qmail 22843 invoked from network); 2 Nov 2003 20:13:36 -0000 Received: from natto.numachi.com (198.175.254.216) by meisai.numachi.com with SMTP; 2 Nov 2003 20:13:36 -0000 Received: (qmail 13321 invoked by uid 1001); 2 Nov 2003 20:13:36 -0000 Date: Sun, 2 Nov 2003 15:13:36 -0500 From: Brian Reichert To: freebsd-hackers@freebsd.org Message-ID: <20031102201336.GF7119@numachi.com> References: <20031101233412.GA33988@ussenterprise.ufp.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031101233412.GA33988@ussenterprise.ufp.org> User-Agent: Mutt/1.5.4i Subject: Re: dhclient & dynamic DNS updates X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2003 20:13:39 -0000 On Sat, Nov 01, 2003 at 06:34:12PM -0500, Leo Bicknell wrote: > Best I can tell from the config this should make dhclient send a > dynamic DNS update to the server listed as "primary" in the zone > section adding hostname.my.example.com. However, tcpdump shows no > DNS update packets of any kind coming from the machine running > dhclient. I've never tried to make use of this feature. The manpage for dhclient.conf(5) says: "The fqdn.encoded option may need to be set to on or off, depending on the DHCP server you are using." Which tells me that your client isn't sending the updates, but is asking the DHCP server to send the updates, which obviously depends on who's DHCP server you're talking to. The dhclient.conf(5) does go on the describe a method of doing DNS updates in the DHCP client script. Myself, I've configured my DHCP server to honor 'send host-name' directives, and update my nameservers. That way, even the most unsophisticated DHCP clients (re: Windows boxes) can make use of my infrastructure... > -- > Leo Bicknell - bicknell@ufp.org - CCIE 3440 > PGP keys at http://www.ufp.org/~bicknell/ > Read TMBG List - tmbg-list-request@tmbg.org, www.tmbg.org -- Brian 'you Bastard' Reichert 37 Crystal Ave. #303 Daytime number: (603) 434-6842 Derry NH 03038-1713 USA BSD admin/developer at large From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 2 13:28:13 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D4E8B16A4CE for ; Sun, 2 Nov 2003 13:28:13 -0800 (PST) Received: from obsecurity.dyndns.org (adsl-63-207-60-234.dsl.lsan03.pacbell.net [63.207.60.234]) by mx1.FreeBSD.org (Postfix) with ESMTP id 15BC643FE0 for ; Sun, 2 Nov 2003 13:28:13 -0800 (PST) (envelope-from kris@obsecurity.org) Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id EB04C66DD2; Sun, 2 Nov 2003 13:28:12 -0800 (PST) Received: by rot13.obsecurity.org (Postfix, from userid 1000) id A6770BD7; Sun, 2 Nov 2003 13:28:12 -0800 (PST) Date: Sun, 2 Nov 2003 13:28:12 -0800 From: Kris Kennaway To: "C. Kukulies" Message-ID: <20031102212812.GA51732@rot13.obsecurity.org> References: <200311021559.hA2FxTjn003915@www.kukulies.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cWoXeonUoKmBZSoM" Content-Disposition: inline In-Reply-To: <200311021559.hA2FxTjn003915@www.kukulies.org> User-Agent: Mutt/1.4.1i cc: hackers@freebsd.org Subject: Re: spambouncer tags much freebsd list mail as spam X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2003 21:28:13 -0000 --cWoXeonUoKmBZSoM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Nov 02, 2003 at 04:59:29PM +0100, C. Kukulies wrote: > I installed the spambouncer.org procmail script and before I was switching > the behaviour from SILENT to COMPLAIN I took a look at my spam.incoming f= older > and found a lot of messages from freebsd-bugs and freebsd-mobile in there. >=20 > Both lists are not directed to folders prior to spambouncer coming into e= ffect > so they are trapped by spambouncer and I suspect that other freebsd lists > would be trapped as well. >=20 > Anyone experienced similar? Many anti-spam packages need to be tuned to avoid classifying non-spam messages as spam. Depending on the software, sometimes it isn't possible to avoid a significant false positive rate, but a good spam filter (e.g. bogofilter) is one that doesn't have this characteristic. Kris --cWoXeonUoKmBZSoM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/pXbsWry0BWjoQKURAvL0AKCKyTv3As21HB0nrYlH1lKh39+E8wCeLSop UzTY4jwXw2HywYrTzkLDIAo= =SlSC -----END PGP SIGNATURE----- --cWoXeonUoKmBZSoM-- From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 2 13:40:56 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 29B4716A4CE for ; Sun, 2 Nov 2003 13:40:56 -0800 (PST) Received: from w2xo.jcdurham.com (18.gibs5.xdsl.nauticom.net [209.195.184.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 36C0643FA3 for ; Sun, 2 Nov 2003 13:40:55 -0800 (PST) (envelope-from durham@jcdurham.com) Received: from jimslaptop.home.jcdurham.com (jimslaptop.jcdurham.com [192.168.5.14]) by w2xo.jcdurham.com (8.11.6/8.11.6) with ESMTP id hA2Lesx50363 for ; Sun, 2 Nov 2003 16:40:54 -0500 (EST) (envelope-from durham@jcdurham.com) From: Jim Durham Organization: JC Durham Consulting To: freebsd-hackers@freebsd.org Date: Sun, 2 Nov 2003 16:40:46 -0500 User-Agent: KMail/1.5.3 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200311021640.46969.durham@jcdurham.com> Subject: Parallel Port in 5.1-RELEASE X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: durham@jcdurham.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2003 21:40:56 -0000 I have a computer running 5.1-RELEASE and another running 4.9-RELEASE.. Both have the same motherboard with onboard ports/nic, etc, so conditions should be equal. They both have a printer plugged in the parallel port. One printer is an HP 5L, the other is an HP 6L, so that is almost identical also. On the 5.1 system, boot messages show: ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold ppbus0: on ppc0 ppbus0: IEEE1284 device found /NIBBLE Probing for PnP devices on ppbus0: ppbus0: plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 On the 4.9-RELEASE system, I get: ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold ppbus0: IEEE1284 device found /NIBBLE Probing for PnP devices on ppbus0: ppbus0: PRINTER HP ENHANCED PCL5,PJL plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 The 4.9 system identifies the printer, the 5.1 system does not, it calls it an "IEEE1284 device". I run CUPS printing on both. On the 4.9 system, the parallel port is available in the cups setup. On the 5.1 system, it is not. The utility 'lpinfo' that comes with CUPS shows a parallel port on the 4.9 System, but not on the 5.1-SYSTEM. The device 'lpt0' shows up in the devfs at /dev on the 5.1 box. However, the permissions always some up as 600 after a bootup, even though I have: perm pass0 0666 perm acd0c 0666 perm lpt0 0666 in /etc/devfs.conf. The first two rules work. The rule for lpt0 does not. BTW, I have a laptop running 5.1 and it does not show a parallel port in CUPS either. Any Ideas? Thanks, -- Jim Durham From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 2 16:12:41 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 46EC916A4CE for ; Sun, 2 Nov 2003 16:12:41 -0800 (PST) Received: from ussenterprise.ufp.org (ussenterprise.ufp.org [208.185.30.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5157043F75 for ; Sun, 2 Nov 2003 16:12:40 -0800 (PST) (envelope-from bicknell@ussenterprise.ufp.org) Received: from ussenterprise.ufp.org (bicknell@localhost [127.0.0.1]) by ussenterprise.ufp.org (8.12.9/8.12.9) with ESMTP id hA30Cd8i084256 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 2 Nov 2003 19:12:39 -0500 (EST) Received: (from bicknell@localhost) by ussenterprise.ufp.org (8.12.9/8.12.9/Submit) id hA30CdfJ084255 for freebsd-hackers@freebsd.org; Sun, 2 Nov 2003 19:12:39 -0500 (EST) Date: Sun, 2 Nov 2003 19:12:39 -0500 From: Leo Bicknell To: freebsd-hackers@freebsd.org Message-ID: <20031103001239.GB83823@ussenterprise.ufp.org> Mail-Followup-To: freebsd-hackers@freebsd.org References: <20031101233412.GA33988@ussenterprise.ufp.org> <20031102201336.GF7119@numachi.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="H8ygTp4AXg6deix2" Content-Disposition: inline In-Reply-To: <20031102201336.GF7119@numachi.com> Organization: United Federation of Planets X-PGP-Key: http://www.ufp.org/~bicknell/ Subject: Re: dhclient & dynamic DNS updates X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2003 00:12:41 -0000 --H8ygTp4AXg6deix2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In a message written on Sun, Nov 02, 2003 at 03:13:36PM -0500, Brian Reiche= rt wrote: > I've never tried to make use of this feature. The manpage for > dhclient.conf(5) says: >=20 > "The fqdn.encoded option may need to be set to on or off, depending > on the DHCP server you are using." >=20 > Which tells me that your client isn't sending the updates, but is > asking the DHCP server to send the updates, which obviously depends > on who's DHCP server you're talking to. Actually, I believe the fqdn.server-update variable controls if the server does the update or not, the fqdn.encoded just needs to be set the same as the server. I'm working on two test cases. 1) dhcpd does the forward and reverse updates for the client. This works fine, and works great with dhclient (with fqdn.server-update on). This proves a couple of things, including that my DDNS nameserver config is ok. 2) dhclient does a forward update only (basically same config with the key and zone sections added to dhclient.conf, and server-update set to off). Under no set of flipping options have I been able to get dhclient to generate a DNS packet of any sort, much less a valid DDNS update. > The dhclient.conf(5) does go on the describe a method of doing DNS > updates in the DHCP client script. I'm afraid I'm going to have to fall back to an external script, which seems silly since dhclient is supposed to be able to do the update itself. > Myself, I've configured my DHCP server to honor 'send host-name' > directives, and update my nameservers. That way, even the most > unsophisticated DHCP clients (re: Windows boxes) can make use of > my infrastructure... Agreed. The end goal for config #2 though is boxes on the end of cable modem or DSL lines using dhcp. In that case I don't control the DHCP server, I just want the client to add it's address to a nameserver I do control so there is a way to get to it remotely. --=20 Leo Bicknell - bicknell@ufp.org - CCIE 3440 PGP keys at http://www.ufp.org/~bicknell/ Read TMBG List - tmbg-list-request@tmbg.org, www.tmbg.org --H8ygTp4AXg6deix2 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE/pZ13Nh6mMG5yMTYRArg6AJ9yl0OmXQCdkJH2J1g3VBwQ6yGD9ACcCBD9 aqfYoKHvEEquJ9kTwQC/8k0= =G8Uv -----END PGP SIGNATURE----- --H8ygTp4AXg6deix2-- From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 2 16:35:20 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 10D7B16A4CE for ; Sun, 2 Nov 2003 16:35:20 -0800 (PST) Received: from webmail.tiscali.de (relay1.tiscali.de [62.26.116.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A44643FB1 for ; Sun, 2 Nov 2003 16:35:14 -0800 (PST) (envelope-from walter@pelissero.de) Received: from daemon.home.loc (62.246.53.170) by webmail.tiscali.de (6.7.019) id 3F9D28A800311079 for hackers@freebsd.org; Mon, 3 Nov 2003 01:35:13 +0100 Received: from hyde.home.loc (hyde.home.loc [10.0.0.2]) by daemon.home.loc (8.12.9/8.12.8) with ESMTP id hA30X13V000387 for ; Mon, 3 Nov 2003 01:33:01 +0100 (CET) (envelope-from wcp@hyde.home.loc) Received: from hyde.home.loc (localhost [127.0.0.1]) by hyde.home.loc (8.12.9/8.12.8) with ESMTP id hA30XKKv064393 for ; Mon, 3 Nov 2003 01:33:20 +0100 (CET) (envelope-from wcp@hyde.home.loc) Received: (from wcp@localhost) by hyde.home.loc (8.12.9/8.12.6/Submit) id hA30XJpj064390; Mon, 3 Nov 2003 01:33:19 +0100 (CET) (envelope-from wcp) From: "Walter C. Pelissero" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16293.41551.103901.897025@hyde.home.loc> Date: Mon, 3 Nov 2003 01:33:19 +0100 To: hackers@freebsd.org X-Mailer: VM 7.16 under Emacs 21.3.50.1 X-Attribution: WP Subject: SCSI spin down on suspend (patch) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: walter@pelissero.de List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2003 00:35:20 -0000 I eventually got around to hack scsi_da.c to implement spin down/up on suspend/resume events of APM or ACPI. Actually the ACPI stuff is untested and the APM once didn't work properly on my system: one of the disks, after resume, was misbehaving (hardware errors). A power toggle fixed the problem, though. I suspect this code could be improved introducing a delay after the spin up of each HD (I've got 6 HD hooked to a 350W power supply, this might explain the hardware error), but not being a kernel hacker myself, I don't know how to proceed. Suggestions are welcome. Please note you need to define CAM_APM_COOP or CAM_ACPI_COOP. --- scsi_da.c.orig Mon Nov 3 00:15:55 2003 +++ scsi_da.c Mon Nov 3 00:18:04 2003 @@ -72,6 +72,15 @@ #include #endif /* !_KERNEL */ +#ifdef CAM_ACPI_COOP +# include +# include +# include +#endif /* CAM_ACPI_COOP */ +#ifdef CAM_APM_COOP +# include +#endif + #ifdef _KERNEL typedef enum { DA_STATE_PROBE, @@ -142,6 +151,40 @@ da_quirks quirks; }; +#ifdef CAM_APM_COOP +static void da_start_stop_all(int start); + +static int +da_apm_suspend (void *junk) +{ + da_start_stop_all (0); + return 0; +} + +static int +da_apm_resume (void *junk) +{ + da_start_stop_all (1); + return 0; +} + +struct apmhook da_suspend_hook = { + 0, /* next */ + da_apm_suspend, /* fun */ + 0, /* arg */ + "da_suspend", /* name */ + 0 /* order */ +}; + +struct apmhook da_resume_hook = { + 0, /* next */ + da_apm_resume, /* fun */ + 0, /* arg */ + "da_resume", /* name */ + 0 /* order */ +}; +#endif /* CAM_APM_COOP */ + static const char quantum[] = "QUANTUM"; static const char microp[] = "MICROP"; @@ -213,6 +256,12 @@ {T_DIRECT, SIP_MEDIA_FIXED, quantum, "LPS525S", "*"}, /*quirks*/ DA_Q_NO_SYNC_CACHE }, + { {T_DIRECT, SIP_MEDIA_FIXED, quantum, "LPS540S", "*"}, + DA_Q_NO_SYNC_CACHE }, + { {T_DIRECT, SIP_MEDIA_FIXED, "CONNER", "CP3500*", "*"}, + DA_Q_NO_SYNC_CACHE }, + { {T_DIRECT, SIP_MEDIA_REMOVABLE, "DataFab*", "*", "*"}, + DA_Q_NO_6_BYTE | DA_Q_NO_SYNC_CACHE }, { /* * Doesn't work correctly with 6 byte reads/writes. @@ -935,6 +984,71 @@ return (0); } +/* + * Step through all DA peripheral drivers and spin them up/down. + */ +static void +da_start_stop_all(int start) +{ + struct cam_periph *periph; + struct da_softc *softc; + + for (periph = TAILQ_FIRST(&dadriver.units); periph != NULL; + periph = TAILQ_NEXT(periph, unit_links)) { + union ccb ccb; + softc = (struct da_softc *)periph->softc; + + xpt_setup_ccb(&ccb.ccb_h, periph->path, /*priority*/1); + + ccb.ccb_h.ccb_state = DA_CCB_DUMP; + scsi_start_stop(&ccb.csio, + /*retries*/1, + /*cbfcnp*/dadone, + MSG_SIMPLE_Q_TAG, + start, + /*load_eject*/ 0, + /*immediate*/ FALSE, + /*sense_len*/ SSD_FULL_SIZE, + /*timeout*/ 50000); + + xpt_polled_action(&ccb); + + if ((ccb.ccb_h.status & CAM_STATUS_MASK) != CAM_REQ_CMP) { + if (((ccb.ccb_h.status & CAM_STATUS_MASK) == + CAM_SCSI_STATUS_ERROR) + && (ccb.csio.scsi_status == SCSI_STATUS_CHECK_COND)){ + int error_code, sense_key, asc, ascq; + + scsi_extract_sense(&ccb.csio.sense_data, + &error_code, &sense_key, + &asc, &ascq); + + if (sense_key != SSD_KEY_ILLEGAL_REQUEST) + scsi_sense_print(&ccb.csio); + } else { + xpt_print_path(periph->path); + printf("Suspend disk failed, status " + "== 0x%x, scsi status == 0x%x\n", + ccb.ccb_h.status, ccb.csio.scsi_status); + } + } + } +} + +#ifdef CAM_ACPI_COOP +static void +da_start_all(void *arg, int state) +{ + da_start_stop_all(1); +} + +static void +da_stop_all(void *arg, int state) +{ + da_start_stop_all(0); +} +#endif /* CAM_ACPI_COOP */ + static void dainit(void) { @@ -987,6 +1101,14 @@ if ((EVENTHANDLER_REGISTER(shutdown_post_sync, dashutdown, NULL, SHUTDOWN_PRI_DEFAULT)) == NULL) printf("dainit: shutdown event registration failed!\n"); +#ifdef CAM_ACPI_COOP + EVENTHANDLER_REGISTER(acpi_sleep_event, da_stop_all, NULL, ACPI_EVENT_PRI_DEFAULT); + EVENTHANDLER_REGISTER(acpi_wakeup_event, da_start_all, NULL, ACPI_EVENT_PRI_DEFAULT); +#endif +#ifdef CAM_APM_COOP + apm_hook_establish (APM_HOOK_SUSPEND, &da_suspend_hook); + apm_hook_establish (APM_HOOK_RESUME, &da_resume_hook); +#endif } } -- walter pelissero http://www.pelissero.de From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 2 17:59:00 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5DE0816A4CE for ; Sun, 2 Nov 2003 17:59:00 -0800 (PST) Received: from ms-smtp-01-eri0.southeast.rr.com (ms-smtp-01-lbl.southeast.rr.com [24.25.9.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id 49C3E43FBF for ; Sun, 2 Nov 2003 17:58:59 -0800 (PST) (envelope-from jason@ec.rr.com) Received: from ec.rr.com (cpe-024-211-231-149.ec.rr.com [24.211.231.149]) hA31wsQT027482 for ; Sun, 2 Nov 2003 20:58:56 -0500 (EST) Message-ID: <3FCD4390.2030408@ec.rr.com> From: jason User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.5b) Gecko/20030901 Thunderbird/0.2 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Symantec AntiVirus Scan Engine Subject: I need help fixing the agp_nvidia.c driver X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Date: Mon, 03 Nov 2003 01:59:00 -0000 X-Original-Date: Tue, 02 Dec 2003 20:59:44 -0500 X-List-Received-Date: Mon, 03 Nov 2003 01:59:00 -0000 Hello everyone, I have a problem loading agp. Every time I do load it at boot from rc.conf and do a startx the machine hard locks. So I decided to check the source code and maybe make some modifications. I have an epox 8rda with the nforce 2 chipset, and a radeon 8500. I am running 5.1. I noticed in the driver for my chipset(agp_nvidia.c) "wbc_mask" was coming up, and it was only in 1 driver, mine. I checked for it in all related files and have found: "#define AGP_NVIDIA_1_WBC 0xf0" in agpreg.h, "#define PCIM_BRIO_MASK 0xf" in pcireg.h. Would anyone know if BRIO_MASK = Base Register In Out_MASK, and what does PCIM and WBC mean? This is the first driver I have worked on or with and I am seeing allot of stuff that must be standard in linux(that is where agp_nvidia.c comes from) because it just does not look like other bsd code in the other agp drivers I have compared it too. Although I have also heard that the drivers nvidia writes for linux are pretty bad, I think they were referring to the style not the quality if I remember correctly. Thanks, Jason From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 2 20:46:35 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1F52216A4CF for ; Sun, 2 Nov 2003 20:46:35 -0800 (PST) Received: from relay.pair.com (relay.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 07DDF43F75 for ; Sun, 2 Nov 2003 20:46:34 -0800 (PST) (envelope-from silby@silby.com) Received: (qmail 75121 invoked from network); 3 Nov 2003 04:46:32 -0000 Received: from niwun.pair.com (HELO localhost) (209.68.2.70) by relay.pair.com with SMTP; 3 Nov 2003 04:46:32 -0000 X-pair-Authenticated: 209.68.2.70 Date: Sun, 2 Nov 2003 22:46:31 -0600 (CST) From: Mike Silbersack To: Vivek Pai In-Reply-To: <3FA2C43E.3030204@cs.princeton.edu> Message-ID: <20031102223625.T90665@odysseus.silby.com> References: <1066789354.21430.39.camel@boxster.onthenet.com.au> <20031022082953.GA69506@rot13.obsecurity.org> <1066816287.25609.34.camel@boxster.onthenet.com.au> <20031022095754.GA70026@rot13.obsecurity.org> <1067183332.3f9bece4c0cf4@webmail.cs.princeton.edu> <3FA2C43E.3030204@cs.princeton.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= cc: Kris Kennaway cc: Q cc: freebsd-hackers@freebsd.org Subject: Re: Some mmap observations compared to Linux 2.6/OpenBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2003 04:46:35 -0000 On Fri, 31 Oct 2003, Vivek Pai wrote: > Before we proceed on this, I'd like to ask is there actuall a committer > ready to follow up on this? We currently make our patches available on > Ping's homepage, and they're relatively clean. He spent a fair bit of > time getting it from a relatively ugly set of changes to something more > elegant and better integrated with the rest of the kernel. However, even > with the benchmark success that we've gotten (which Aniruddha Bohra > mentioned in a different e-mail), we haven't had a single nibble from a > committer. FreeBSD lags Linux badly on the SpecWeb99 benchmarks, and > those are probably more representative than some arbitrary > microbenchmark. It would be nice to get some respectable numbers on it, > especially if we could do it with a stable user-space server. > > -Vivek My main concern is that your patches may no longer cleanly apply to -current, which could make integration more difficult. If integration is easy, and if we can show some improvement with webservers other than Flash, I'll help with integration. However, with the 5.2 code freeze starting in mid-November, I can't guarantee that we could have it integrated by then. However, that doesn't preclude us from doing work on it during that time. Does the version of flash available for download (.1 alpha) have the changes which take advantage of your enhanced sendfile integrated? Mike "Silby" Silbersack From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 2 21:03:32 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AA1C716A4CE; Sun, 2 Nov 2003 21:03:32 -0800 (PST) Received: from ms-smtp-01-eri0.southeast.rr.com (ms-smtp-01-lbl.southeast.rr.com [24.25.9.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D02943FDD; Sun, 2 Nov 2003 21:03:31 -0800 (PST) (envelope-from jason@ec.rr.com) Received: from ec.rr.com (cpe-024-211-231-149.ec.rr.com [24.211.231.149]) hA353SQT028893; Mon, 3 Nov 2003 00:03:29 -0500 (EST) Message-ID: <3FCD6ED4.2090005@ec.rr.com> From: jason User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.5b) Gecko/20030901 Thunderbird/0.2 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Symantec AntiVirus Scan Engine Subject: pci registers for nforce2 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Date: Mon, 03 Nov 2003 05:03:32 -0000 X-Original-Date: Wed, 03 Dec 2003 00:04:20 -0500 X-List-Received-Date: Mon, 03 Nov 2003 05:03:32 -0000 #define AGP_NVIDIA_3_APBASE 0x50 #define AGP_NVIDIA_3_APLIMIT 0x54 These are only listed in agpreg.h and agp_nvidia.c, where as all other register information(as far as I can tell) is also listed in pcireg.h. Is it necessary to have it listed in both places or is it fine as is? If it is a custom register for the nforce2, I guess it would be ok but I don't know. Thanks, Jason From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 2 21:12:21 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9BEFE16A4CE; Sun, 2 Nov 2003 21:12:21 -0800 (PST) Received: from sasami.jurai.net (sasami.jurai.net [66.92.160.223]) by mx1.FreeBSD.org (Postfix) with ESMTP id B833F43F3F; Sun, 2 Nov 2003 21:12:20 -0800 (PST) (envelope-from mdodd@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [66.92.160.223]) by sasami.jurai.net (8.12.9/8.12.9) with ESMTP id hA35CGkL044446; Mon, 3 Nov 2003 00:12:16 -0500 (EST) (envelope-from mdodd@FreeBSD.ORG) Date: Mon, 3 Nov 2003 00:12:16 -0500 (EST) From: "Matthew N. Dodd" X-X-Sender: winter@sasami.jurai.net To: jason In-Reply-To: <3FCD6ED4.2090005@ec.rr.com> Message-ID: <20031103000957.N25925@sasami.jurai.net> References: <3FCD6ED4.2090005@ec.rr.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hackers@FreeBSD.ORG cc: freebsd-questions@FreeBSD.ORG Subject: Re: pci registers for nforce2 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2003 05:12:21 -0000 On Wed, 3 Dec 2003, jason wrote: > #define AGP_NVIDIA_3_APBASE 0x50 > #define AGP_NVIDIA_3_APLIMIT 0x54 > These are only listed in agpreg.h and agp_nvidia.c, where as all other > register information(as far as I can tell) is also listed in pcireg.h. > Is it necessary to have it listed in both places or is it fine as is? > If it is a custom register for the nforce2, I guess it would be ok but I > don't know. These definitions are fine; if they weren't defined the driver wouldn't compile. I wish I could provide more help in getting this driver to work but I've gone as far as I can without having physical access to the hardware. Good luck. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 2 21:21:12 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CE15F16A4CE; Sun, 2 Nov 2003 21:21:12 -0800 (PST) Received: from VARK.homeunix.com (adsl-68-123-40-77.dsl.pltn13.pacbell.net [68.123.40.77]) by mx1.FreeBSD.org (Postfix) with ESMTP id C18CA43F75; Sun, 2 Nov 2003 21:21:11 -0800 (PST) (envelope-from das@FreeBSD.ORG) Received: from VARK.homeunix.com (localhost [127.0.0.1]) by VARK.homeunix.com (8.12.9/8.12.9) with ESMTP id hA35KBen071644; Sun, 2 Nov 2003 21:20:11 -0800 (PST) (envelope-from das@FreeBSD.ORG) Received: (from das@localhost) by VARK.homeunix.com (8.12.9/8.12.9/Submit) id hA35KA9e071643; Sun, 2 Nov 2003 21:20:10 -0800 (PST) (envelope-from das@FreeBSD.ORG) Date: Sun, 2 Nov 2003 21:20:10 -0800 From: David Schultz To: Vivek Pai Message-ID: <20031103052010.GA71583@VARK.homeunix.com> Mail-Followup-To: Vivek Pai , Dag-Erling@FreeBSD.ORG,, freebsd-hackers@FreeBSD.ORG, Q , Kris Kennaway References: <1066789354.21430.39.camel@boxster.onthenet.com.au> <20031022082953.GA69506@rot13.obsecurity.org> <1066816287.25609.34.camel@boxster.onthenet.com.au> <20031022095754.GA70026@rot13.obsecurity.org> <1066820436.25609.93.camel@boxster.onthenet.com.au> <20031026052854.GA20701@VARK.homeunix.com> <3FA2C63C.5000900@cs.princeton.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3FA2C63C.5000900@cs.princeton.edu> cc: Q cc: freebsd-hackers@FreeBSD.ORG cc: Kris Kennaway cc: iso-8859-1?Q?Sm=F8rgrav?= cc: Dag-Erling@FreeBSD.ORG cc: "=?us-ascii@FreeBSD.ORG"@FreeBSD.ORG Subject: Re: Some mmap observations compared to Linux 2.6/OpenBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2003 05:21:12 -0000 On Fri, Oct 31, 2003, Vivek Pai wrote: > Take a look at Figure 6, page 9 in the following: > http://www.cs.princeton.edu/~yruan/DeBox/debox.pdf > > On a 1GHz box with 1GB of memory, we were spending > 4-5 milliseconds per mmap call, and that was limiting > the throughput of our server on SpecWeb99. > > Figure 9 on page 11 shows that just getting rid of the > mmap/munmap/mincore calls in this server got us a 50% > performance boost on a fairly complicated workload. The > SpecWeb99 workload was modeled after several web sites, > so this might actually be a performance problem in the > real world. > > If you look at figure 11, page 12, you'll see that with > various improvements, our server's median latency dropped to > less than 1ms. An mmap time of several milliseconds would > kill that benefit. Okay, I guess SpecWeb99 is ``real world'' enough for me to justify the assertion that there is an mmap() performance problem. Just out of curiosity, how many regions did SpecWeb99 map? (i.e. what does 'dd if=/proc/$pid/map bs=64k count=1 | wc -l' give?) From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 2 21:27:33 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D68D516A4CE; Sun, 2 Nov 2003 21:27:33 -0800 (PST) Received: from bluebox.CS.Princeton.EDU (bluebox.CS.Princeton.EDU [128.112.136.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id B43F843FB1; Sun, 2 Nov 2003 21:27:32 -0800 (PST) (envelope-from vivek@CS.Princeton.EDU) Received: from cs.princeton.edu (oakley [128.112.139.27]) (authenticated bits=0)hA35RSFU025673 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 3 Nov 2003 00:27:29 -0500 (EST) Message-ID: <3FA5E740.6050704@cs.princeton.edu> Date: Mon, 03 Nov 2003 00:27:28 -0500 From: Vivek Pai User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.0.1) Gecko/20020920 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: David Schultz References: <1066789354.21430.39.camel@boxster.onthenet.com.au> <20031022082953.GA69506@rot13.obsecurity.org> <1066816287.25609.34.camel@boxster.onthenet.com.au> <20031022095754.GA70026@rot13.obsecurity.org> <1066820436.25609.93.camel@boxster.onthenet.com.au> <20031026052854.GA20701@VARK.homeunix.com> <3FA2C63C.5000900@cs.princeton.edu> <20031103052010.GA71583@VARK.homeunix.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: "=?us-ascii@FreeBSD.ORG: iso-8859-1?Q?Sm=F8rgrav?=" cc: Kris Kennaway cc: Q cc: freebsd-hackers@FreeBSD.ORG cc: Dag-Erling@FreeBSD.ORG Subject: Re: Some mmap observations compared to Linux 2.6/OpenBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2003 05:27:34 -0000 David Schultz wrote: > > Okay, I guess SpecWeb99 is ``real world'' enough for me to justify > the assertion that there is an mmap() performance problem. Just > out of curiosity, how many regions did SpecWeb99 map? > (i.e. what does 'dd if=/proc/$pid/map bs=64k count=1 | wc -l' give?) The SpecWeb99 benchmark is self-scaling - the higher request rate you try to achieve, the more files are included in the data set. It's entirely up to the server to decide how to go about dealing with the data, and the Flash server used to keep a cache of mmap'd regions. Files smaller than 64KB were mapped as a single region, while larger files were broken into 64KB pieces, basically to avoid exhausting the address space. For the kinds of throughputs that we achieve, we're dealing with about 13,000 files. We probably had a number of regions somewhere in that ballpark, but I don't have a free machine at the moment to give you an exact number. Our new server basically gave up on using mapped files entirely due to the problems with scaling to larger memory sizes - that's why I'm pushing for the sendfile changes I mentioned in a different mail. -Vivek From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 2 22:11:07 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EEA9B16A4CF for ; Sun, 2 Nov 2003 22:11:07 -0800 (PST) Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [204.127.202.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id 46DEC43FB1 for ; Sun, 2 Nov 2003 22:11:07 -0800 (PST) (envelope-from DougB@freebsd.org) Received: from master.dougb.net (12-234-18-52.client.attbi.com[12.234.18.52]) by comcast.net (sccrmhc11) with SMTP id <2003110306110601100enslge>; Mon, 3 Nov 2003 06:11:06 +0000 Date: Sun, 2 Nov 2003 22:11:05 -0800 (PST) From: Doug Barton To: jason In-Reply-To: <3FCD4390.2030408@ec.rr.com> Message-ID: <20031102220825.I9025@znfgre.qbhto.arg> References: <3FCD4390.2030408@ec.rr.com> Organization: http://www.FreeBSD.org/ X-message-flag: Outlook -- Not just for spreading viruses anymore! MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hackers@freebsd.org Subject: Re: I need help fixing the agp_nvidia.c driver X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2003 06:11:08 -0000 On Tue, 2 Dec 2003, jason wrote: > Hello everyone, > I have a problem loading agp. Every time I do load it at boot from > rc.conf and do a startx the machine hard locks. One definition of sanity is doing the same thing over and over, and expecting a different result. :) You should load it in /boot/loader.conf[.local]: agp_load="YES" Actually, I do better with nvidia's driver without agp loaded, FWIW. Doug -- This .signature sanitized for your protection From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 2 22:45:03 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BDF9616A4CE; Sun, 2 Nov 2003 22:45:03 -0800 (PST) Received: from mail.ryu16.org (YahooBB219005044050.bbtec.net [219.5.44.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A97043F3F; Sun, 2 Nov 2003 22:45:02 -0800 (PST) (envelope-from imura@ryu16.org) Received: from redeye.xt.ryu16.org (localhost [127.0.0.1]) by mail.ryu16.org (8.12.9p1/8.12.9) with ESMTP id hA36j1uD034237; Mon, 3 Nov 2003 15:45:01 +0900 (JST) (envelope-from imura@redeye.xt.ryu16.org) Received: (from imura@localhost) by redeye.xt.ryu16.org (8.12.9p1/8.12.9/Submit) id hA36j10r034236; Mon, 3 Nov 2003 15:45:01 +0900 (JST) (envelope-from imura) Date: Mon, 3 Nov 2003 15:45:00 +0900 From: "R. Imura" To: current@freebsd.org, hackers@freebsd.org Message-ID: <20031103064500.GD606%imura@ryu16.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i-ja.1 Subject: Fw: [patch] combine mount_udf(8) with kiconv(3) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2003 06:45:03 -0000 Hi, I was adviced to forward here, so that more poeple can see it. It was originally posted to fs@ and i18n@. Regards, ----- Forwarded message from "R. Imura" ----- Date: Mon, 3 Nov 2003 01:42:18 +0900 From: "R. Imura" Subject: [patch] combine mount_udf(8) with kiconv(3) To: fs@freebsd.org, i18n@freebsd.org Hi all, I now added -C option to mount_udf(8) as well as mount_cd9660(8) and mount_ntfs(8) with UDF_ICONV kernel module in order to handle multibyte characters. Since I'm new to nmount(), please correct me if I'm wrong with how to write udf specific options/flags. The patch is here: http://www.ryu16.org/FreeBSD/kiconv/udf_5_current_20031101.diff It is grateful if this will be applied to the FreeBSD src tree. Regards, - R. Imura ----- End forwarded message ----- From owner-freebsd-hackers@FreeBSD.ORG Mon Nov 3 01:04:28 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 00BAF16A4D6; Mon, 3 Nov 2003 01:04:28 -0800 (PST) Received: from turtle.freedns.us (netblock-66-159-221-76.dslextreme.com [66.159.221.76]) by mx1.FreeBSD.org (Postfix) with ESMTP id C581B43FAF; Mon, 3 Nov 2003 01:04:26 -0800 (PST) (envelope-from bt@turtle.freedns.us) Received: from turtle.freedns.us (localhost [127.0.0.1]) by turtle.freedns.us (8.12.3/8.12.3) with ESMTP id hA394NNB001025; Mon, 3 Nov 2003 01:04:23 -0800 (PST) (envelope-from bt@turtle.freedns.us) Message-ID: <3FA61A17.70605@turtle.freedns.us> Date: Mon, 03 Nov 2003 01:04:23 -0800 From: Igor Serikov Organization: Private Person User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.0.1) Gecko/20030209 X-Accept-Language: ru, en MIME-Version: 1.0 To: FreeBSD Bugs , FreeBSD Hackers Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Subject: rfork problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2003 09:04:28 -0000 Hello, Combining flags RFNOWAIT and RFPPWAIT in rfork(2) under 4.6-RELEASE makes the parent process sleeping on channel "ppwait" forever. Regards, Igor. From owner-freebsd-hackers@FreeBSD.ORG Mon Nov 3 02:08:35 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8AA7C16A4CE for ; Mon, 3 Nov 2003 02:08:35 -0800 (PST) Received: from gatekeeper.syskonnect.de (gatekeeper.syskonnect.de [213.144.13.149]) by mx1.FreeBSD.org (Postfix) with ESMTP id 328C043FE1 for ; Mon, 3 Nov 2003 02:08:34 -0800 (PST) (envelope-from gheinig@syskonnect.de) Received: from syskonnect.de (spock [10.9.15.1])hA3A8u69011993 for ; Mon, 3 Nov 2003 11:08:57 +0100 (MET) Received: from syskonnect.de (localhost [127.0.0.1]) by syskonnect.de (8.12.9/8.12.9) with ESMTP id hA3KfNKl029079 for ; Mon, 3 Nov 2003 21:41:28 +0100 (MET) X-Authentication-Warning: spock.skd.de: iscan owned process doing -bs Sender: gheinig@syskonnect.de Message-ID: <3FA6253E.9D727094@syskonnect.de> Date: Mon, 03 Nov 2003 10:51:58 +0100 From: Gerald Heinig Organization: SysKonnect GmbH X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.18 i686) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: kernel malloc usage X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2003 10:08:35 -0000 Hi all, I have a question concerning the use of malloc to allocate small amounts of memory for packet wrappers for certain packets. Basically, I'm using malloc in much the same way as one would use it in a standard userland program: allocating small chunks and freeing them again a short(ish) time later. A colleague said this was a bad idea, since malloc should only really be used to allocate larger chunks (PAGE_SIZE and over) at driver initialisation. Management and partition of the allocated space should be done by the driver. His reason was that over time, the kernel heap memory gets progressively more fragmented until it becomes difficult to get larger blocks. Is this true? I seem to remember that FreeBSD has a slab allocator, which IIRC is particularly good at allocating small chunks. Is it a better idea to write my own allocators which use a larger block of memory allocated by malloc at driver start-time, or can I use malloc as in userland? Cheers, Gerald -- S y s K o n n e c t G m b H A Marvell Company Siemensstr. 23 D-76275 Ettlingen, Germany --------------------------------- Gerald Heinig Software Engineer ------------------------------------- phone: + 49 (0) 7243 502 354 fax: +49 (0) 7243 502 364 email: gheinig@syskonnect.de http://www.syskonnect.com From owner-freebsd-hackers@FreeBSD.ORG Mon Nov 3 02:59:34 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1F36316A4CE for ; Mon, 3 Nov 2003 02:59:34 -0800 (PST) Received: from arginine.spc.org (arginine.spc.org [195.206.69.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB76F43FAF for ; Mon, 3 Nov 2003 02:59:32 -0800 (PST) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id B8F836542D; Mon, 3 Nov 2003 10:59:31 +0000 (GMT) Received: from arginine.spc.org ([127.0.0.1]) by localhost (arginine.spc.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 56731-01; Mon, 3 Nov 2003 10:59:31 +0000 (GMT) Received: from saboteur.dek.spc.org (unknown [82.147.19.91]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by arginine.spc.org (Postfix) with ESMTP id A03166542C; Mon, 3 Nov 2003 10:59:30 +0000 (GMT) Received: by saboteur.dek.spc.org (Postfix, from userid 1001) id A42BD40; Mon, 3 Nov 2003 10:59:29 +0000 (GMT) Date: Mon, 3 Nov 2003 10:59:29 +0000 From: Bruce M Simpson To: Gerald Heinig Message-ID: <20031103105929.GB17479@saboteur.dek.spc.org> References: <3FA6253E.9D727094@syskonnect.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3FA6253E.9D727094@syskonnect.de> cc: hackers@freebsd.org Subject: Re: kernel malloc usage X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2003 10:59:34 -0000 On Mon, Nov 03, 2003 at 10:51:58AM +0100, Gerald Heinig wrote: > Is this true? I seem to remember that FreeBSD has a slab allocator, > which IIRC is particularly good at allocating small chunks. You don't specify which version of the kernel you're programming to; so I'll assume 5.x. If your allocations are of similar size, then consider using the zone allocator; I believe this implements a slab-like algorithm. BMS From owner-freebsd-hackers@FreeBSD.ORG Mon Nov 3 05:55:02 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 305BD16A4CE; Mon, 3 Nov 2003 05:55:02 -0800 (PST) Received: from frost.ath.cx (BSN-95-242-77.dsl.siol.net [193.95.242.77]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB38643F85; Mon, 3 Nov 2003 05:55:00 -0800 (PST) (envelope-from bfg@noviforum.si) Received: from noviforum.si (mordor.lucky.si [192.168.200.250]) by frost.ath.cx (ESMTP) with ESMTP id 5009375; Mon, 3 Nov 2003 14:54:56 +0100 (CET) Message-ID: <3FA65BF4.7080604@noviforum.si> Date: Mon, 03 Nov 2003 14:45:24 +0100 From: =?ISO-8859-2?Q?=22Branko_F=2E_Gra=E8nar=22?= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031013 Thunderbird/0.3 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kris Kennaway References: <3F9F9884.3020309@noviforum.si> <20031030050540.GA25906@rot13.obsecurity.org> In-Reply-To: <20031030050540.GA25906@rot13.obsecurity.org> X-Enigmail-Version: 0.81.7.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-hackers@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: FreeBSD 5.1-p10 reproducible crash with Apache2 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2003 13:55:02 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi. Today i added the following lines in my kernel config and i recompiled kernel: makeoptions DEBUG=-g options DDB options INVARIANTS options INVARIANT_SUPPORT options WITNESS I reran apache2 ssl test with jmeter. Machine stopped responding after 3-4 seconds (keyboard and console are unresponsible, machine doesn't respond to ping, sshd stops responding...) after reboot machine does not save core (panic didn't happen), so i'm unable to give you any kernel dump. # savecore /var/crash /dev/ar0s1b savecore: no dumps found /etc/rc.conf: dumpdev="/dev/ar0s1b" # Device name to crashdump to (or NO). dumpdir="/var/crash" # Directory where crash dumps are to be stored savecore_flags="" # Used if dumpdev is enabled above, and present. Brane -----BEGIN PGP SIGNATURE----- iD8DBQE/plv0fiC/E+t8hPcRAovOAJ47Yv9qk0/7E43dZFtMf7vAJ694agCfUtm8 xWCjwkSpilNcTUW3cvs1330= =EmbK -----END PGP SIGNATURE----- From owner-freebsd-hackers@FreeBSD.ORG Mon Nov 3 06:04:17 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C1BDD16A4CF for ; Mon, 3 Nov 2003 06:04:17 -0800 (PST) Received: from pixies.tirloni.org (pixies.tirloni.org [200.203.183.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id D112643FCB for ; Mon, 3 Nov 2003 06:04:16 -0800 (PST) (envelope-from tirloni@tirloni.org) Received: by pixies.tirloni.org (Postfix, from userid 1000) id 02A9B1E1411; Mon, 3 Nov 2003 12:04:14 -0200 (BRST) Date: Mon, 3 Nov 2003 12:04:13 -0200 From: "Giovanni P. Tirloni" To: "Branko F. Gra?nar" Message-ID: <20031103140413.GG18358@pixies.tirloni.org> Mail-Followup-To: "Branko F. Gra?nar" , freebsd-hackers@freebsd.org References: <3F9F9884.3020309@noviforum.si> <20031030050540.GA25906@rot13.obsecurity.org> <3FA65BF4.7080604@noviforum.si> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <3FA65BF4.7080604@noviforum.si> X-Info: http://www.tirloni.org User-Agent: Mutt/1.5.4i cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD 5.1-p10 reproducible crash with Apache2 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2003 14:04:17 -0000 * "Branko F. Gra?nar" (bfg@noviforum.si) wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi. > > Today i added the following lines in my kernel config and i recompiled > kernel: > > makeoptions DEBUG=-g > options DDB > options INVARIANTS > options INVARIANT_SUPPORT > options WITNESS > > > I reran apache2 ssl test with jmeter. Machine stopped responding after > 3-4 seconds (keyboard and console are unresponsible, machine doesn't > respond to ping, sshd stops responding...) [ I couldn't find this thread on the archives so I'm jumping in blind. ] Perhaps you're being livelocked by so many interrupts hitting the system that it doesn't do anything productive and only stays there handling interrupts. Can you try polling (http://info.iet.unipi.it/~luigi/polling/) ? -- Giovanni P. Tirloni Fingerprint: 8C3F BEC5 79BD 3E9B EDB8 72F4 16E8 BA5E D031 5C26 From owner-freebsd-hackers@FreeBSD.ORG Mon Nov 3 06:46:12 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1067716A4CE; Mon, 3 Nov 2003 06:46:12 -0800 (PST) Received: from frost.ath.cx (BSN-95-242-77.dsl.siol.net [193.95.242.77]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2119343FE3; Mon, 3 Nov 2003 06:46:11 -0800 (PST) (envelope-from bfg@noviforum.si) Received: from noviforum.si (mordor.lucky.si [192.168.200.250]) by frost.ath.cx (ESMTP) with ESMTP id C43A175; Mon, 3 Nov 2003 15:46:08 +0100 (CET) Message-ID: <3FA667F4.7060003@noviforum.si> Date: Mon, 03 Nov 2003 15:36:36 +0100 From: =?ISO-8859-1?Q?=22Branko_F=2E_Grac=28nar=22?= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031013 Thunderbird/0.3 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Giovanni P. Tirloni" References: <3F9F9884.3020309@noviforum.si> <20031030050540.GA25906@rot13.obsecurity.org> <3FA65BF4.7080604@noviforum.si> <20031103140413.GG18358@pixies.tirloni.org> In-Reply-To: <20031103140413.GG18358@pixies.tirloni.org> X-Enigmail-Version: 0.81.7.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-hackers@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: FreeBSD 5.1-p10 reproducible crash with Apache2 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2003 14:46:12 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 | | Can you try polling (http://info.iet.unipi.it/~luigi/polling/) ? Hi. I just disabled SMP support, enabled polling (i've also set sysctl variable to 1) and reran the test. Machine locked up in about 5 seconds (this is 1u p4 xeon 2.4 GHz, 2GB of ~ ram). This only accours if Apache2 SSLMutex is set to 'sem' and SSLSessionCache is set to 'shm:/path(size)'. So... there are possible problems with shared memory implementation in 5.1-RELEASE Brane -----BEGIN PGP SIGNATURE----- iD8DBQE/pmfzfiC/E+t8hPcRAqGzAJ4vTHkq/CH9Z/t9JzoQmyrra7kGkQCgkNNY /ymFJanS5jNGBkypPc6t4Ts= =cxx4 -----END PGP SIGNATURE----- From owner-freebsd-hackers@FreeBSD.ORG Mon Nov 3 07:39:34 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3ACFB16A4CE for ; Mon, 3 Nov 2003 07:39:34 -0800 (PST) Received: from pixies.tirloni.org (pixies.tirloni.org [200.203.183.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id B5DA443FE5 for ; Mon, 3 Nov 2003 07:39:32 -0800 (PST) (envelope-from tirloni@tirloni.org) Received: by pixies.tirloni.org (Postfix, from userid 1000) id D21951E140B; Mon, 3 Nov 2003 13:39:30 -0200 (BRST) Date: Mon, 3 Nov 2003 13:39:30 -0200 From: "Giovanni P. Tirloni" To: freebsd-hackers@freebsd.org Message-ID: <20031103153930.GH18358@pixies.tirloni.org> Mail-Followup-To: freebsd-hackers@freebsd.org References: <3F9F9884.3020309@noviforum.si> <20031030050540.GA25906@rot13.obsecurity.org> <3FA65BF4.7080604@noviforum.si> <20031103140413.GG18358@pixies.tirloni.org> <3FA66083.1020609@noviforum.si> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <3FA66083.1020609@noviforum.si> X-Info: http://www.tirloni.org User-Agent: Mutt/1.5.4i Subject: Re: FreeBSD 5.1-p10 reproducible crash with Apache2 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2003 15:39:34 -0000 * "Branko F. Grac(nar" (bfg@noviforum.si) wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > | > | [ I couldn't find this thread on the archives so I'm jumping in blind. ] > | > | Perhaps you're being livelocked by so many interrupts hitting the > | system that it doesn't do anything productive and only stays there > | handling interrupts. > | > | Can you try polling (http://info.iet.unipi.it/~luigi/polling/) ? > > This is SMP machine... So polling shouldn't even work. That's true. Although I remember someone here got it working but I can't remember his name. -- Giovanni P. Tirloni Fingerprint: 8C3F BEC5 79BD 3E9B EDB8 72F4 16E8 BA5E D031 5C26 From owner-freebsd-hackers@FreeBSD.ORG Mon Nov 3 11:36:58 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0EB2716A4CF for ; Mon, 3 Nov 2003 11:36:58 -0800 (PST) Received: from razorbill.mail.pas.earthlink.net (razorbill.mail.pas.earthlink.net [207.217.121.248]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1850E43FBD for ; Mon, 3 Nov 2003 11:36:57 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from user-38ldvdb.dialup.mindspring.com ([209.86.253.171] helo=mindspring.com) by razorbill.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 1AGkVR-00017Z-00; Mon, 03 Nov 2003 11:36:54 -0800 Message-ID: <3FA6AE69.3BB03ACD@mindspring.com> Date: Mon, 03 Nov 2003 11:37:13 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "C. Kukulies" References: <200311021559.hA2FxTjn003915@www.kukulies.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a458b1036e115974f055e08b64745391b6350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c cc: hackers@freebsd.org Subject: Re: spambouncer tags much freebsd list mail as spam X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2003 19:36:58 -0000 "C. Kukulies" wrote: > I installed the spambouncer.org procmail script and before I was switching > the behaviour from SILENT to COMPLAIN I took a look at my spam.incoming folder > and found a lot of messages from freebsd-bugs and freebsd-mobile in there. > > Both lists are not directed to folders prior to spambouncer coming into effect > so they are trapped by spambouncer and I suspect that other freebsd lists > would be trapped as well. > > Anyone experienced similar? The "spambouncer" script makes the same incorrect assumption that the EarthLink SPAM stuff makes, which is that any mail not explicitly addressed to you is SPAM. In other words, they expect mailing lists to violate the draft RFC that prohibits header rewriting by mailing lists, and they expect all mailing list servers to eat the overhead of expanding each message to a single recipient message, instead of sending the messages in bulk if the destination domain is identical. At least the "spambouncer" script can be modified to respect the "Sender:" header, which EarthLink fails to respect in their list of "allowed senders". This is pretty much how you should modify the "spambouncer" code to handle mailing lists (and how EarthLink should modify their anti-SPAM system, as well, but probably won't). -- Terry From owner-freebsd-hackers@FreeBSD.ORG Mon Nov 3 21:02:41 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E811C16A4CF for ; Mon, 3 Nov 2003 21:02:41 -0800 (PST) Received: from relay.pair.com (relay.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 3AF3643FD7 for ; Mon, 3 Nov 2003 21:02:40 -0800 (PST) (envelope-from silby@silby.com) Received: (qmail 34124 invoked from network); 4 Nov 2003 05:02:38 -0000 Received: from niwun.pair.com (HELO localhost) (209.68.2.70) by relay.pair.com with SMTP; 4 Nov 2003 05:02:38 -0000 X-pair-Authenticated: 209.68.2.70 Date: Mon, 3 Nov 2003 23:02:36 -0600 (CST) From: Mike Silbersack To: =?ISO-8859-1?Q?=22Branko_F=2E_Grac=28nar=22?= In-Reply-To: <3FA667F4.7060003@noviforum.si> Message-ID: <20031103230152.F99573@odysseus.silby.com> References: <3F9F9884.3020309@noviforum.si> <20031030050540.GA25906@rot13.obsecurity.org> <20031103140413.GG18358@pixies.tirloni.org> <3FA667F4.7060003@noviforum.si> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hackers@freebsd.org cc: freebsd-current@freebsd.org cc: "Giovanni P. Tirloni" Subject: Re: FreeBSD 5.1-p10 reproducible crash with Apache2 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Nov 2003 05:02:42 -0000 On Mon, 3 Nov 2003, [ISO-8859-1] "Branko F. Grac(nar" wrote: > Machine locked up in about 5 seconds (this is 1u p4 xeon 2.4 GHz, 2GB of > ~ ram). > > This only accours if Apache2 SSLMutex is set to 'sem' and > SSLSessionCache is set to 'shm:/path(size)'. > > So... there are possible problems with shared memory implementation in > 5.1-RELEASE > > > Brane Can you try updating to 5.1-current and see if the situation changes at all? A lot has changed since 5.1-release. If it's still broken in 5.1-current, we can take a look into it. Thanks, Mike "Silby" Silbersack From owner-freebsd-hackers@FreeBSD.ORG Mon Nov 3 22:04:51 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6552616A4CE for ; Mon, 3 Nov 2003 22:04:51 -0800 (PST) Received: from gunjin.wccnet.org (gunjin.wccnet.org [198.111.176.99]) by mx1.FreeBSD.org (Postfix) with ESMTP id 665F943FE3 for ; Mon, 3 Nov 2003 22:04:50 -0800 (PST) (envelope-from anthony@gunjin.wccnet.org) Received: from gunjin.wccnet.org (localhost.rexroof.com [127.0.0.1]) by gunjin.wccnet.org (8.12.3/8.12.2) with ESMTP id hA468q2m039934 for ; Tue, 4 Nov 2003 01:08:52 -0500 (EST) Received: (from anthony@localhost) by gunjin.wccnet.org (8.12.3/8.12.3/Submit) id hA468qgs039933 for freebsd-hackers@freebsd.org; Tue, 4 Nov 2003 01:08:52 -0500 (EST) Date: Tue, 4 Nov 2003 01:08:51 -0500 From: Anthony Schneider To: freebsd-hackers@freebsd.org Message-ID: <20031104060851.GA39619@x-anthony.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="EeQfGwPcQSOJBaQU" Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: Sound Blaster Audigy LS problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Nov 2003 06:04:51 -0000 --EeQfGwPcQSOJBaQU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Dear @hackers, i recently bought a soundblaster audigy ls card hoping that it would "just work" with freebsd, but sadly this is not the case. at boot, i see that we recognize that there is a sound card, but that's not adequate. pciconf -l -v: none@pci2:7:0: class=0x040100 card=0x10021102 chip=0x00071102 rev=0x00 hdr=0x00 vendor = 'Creative Labs' class = multimedia subclass = audio /sys/dev/sound/pci/emu10k1.c defines the following: #define EMU10K1_PCI_ID 0x00021102 #define EMU10K2_PCI_ID 0x00041102 from this, i've concluded that either a) this card has an "audigy-compatible" chipset and the freebsd driver just doesn't recognize it, b) this card has an audigy-compatible chipset and the freebsd driver not only doesn't recognize it, biut it might even be slightly different, or c) this "audigy ls" card really isn't that similar at all to other audigy cards. so, i tried just changing the PCI_ID defines above to match my card's id, but writes to the device through mpg123 and xmms give me: pcm0:play:0: play interrupt timeout, channel dead so the question afer all of this is: has anyone been able to push sound out of an audigy ls card? does anyone know what the chipset is (emu10k1, emu10k2...)? would it be trivial for me to hack emu10k1 into compatibility? thank you in advance. -Anthony. P.S. FreeBSD pickle 5.1-RELEASE-p10 FreeBSD 5.1-RELEASE-p10 #0: Mon Nov 3 19:10:54 EST 2003 anthony@pickle:/usr/src/sys/i386/compile/PICKLE i386 P.P.S. also, someone may want to look at sys/dev/sound/pcm/channel.c (lines 279-282): timeout = (hz * sndbuf_getblksz(bs)) / (sndbuf_getspd(bs) * sndbuf_getbps(bs)); if (timeout < 1) timeout = 1; timeout = 1; seems like overkill... --EeQfGwPcQSOJBaQU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE/p0JyKUeW47UGY2kRAraCAJ9aIgRzVPrm+n5GXRIqrNA5HbnBSACdF3lj agiBtssaCRMWKLZD4TjFA5c= =rRGW -----END PGP SIGNATURE----- --EeQfGwPcQSOJBaQU-- From owner-freebsd-hackers@FreeBSD.ORG Mon Nov 3 23:27:06 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4192516A4CE for ; Mon, 3 Nov 2003 23:27:06 -0800 (PST) Received: from md.gfk.ru (md.gfk.ru [62.205.179.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5AB9643FBD for ; Mon, 3 Nov 2003 23:27:04 -0800 (PST) (envelope-from Yuriy.Tsibizov@gfk.ru) Received: from mx.gfk.ru ([10.0.0.30]) by md.gfk.ru ([62.205.179.201]) with SMTP (MDaemon.PRO.v6.5.2.R) for ; Tue, 04 Nov 2003 10:26:39 +0300 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Date: Tue, 4 Nov 2003 10:26:53 +0300 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Sound Blaster Audigy LS problem Thread-Index: AcOimcLU3w7v0jx/Ss2PmcBSE2fh0gAB2zNA From: "Yuriy Tsibizov" To: "Anthony Schneider" , X-MDRemoteIP: 10.0.0.30 X-Return-Path: Yuriy.Tsibizov@gfk.ru X-MDaemon-Deliver-To: freebsd-hackers@freebsd.org Subject: RE: Sound Blaster Audigy LS problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Nov 2003 07:27:06 -0000 > Dear @hackers, > i recently bought a soundblaster audigy ls card hoping that it > would "just work" with freebsd, but sadly this is not the=20 > case.=20 Anthony, Audigy is not supported in -CURRENT kernel, but there are some patches to make it work under FreeBSD. I know about five of them:=20 1) http://www.freebsd.org/cgi/getmsg.cgi?fetch=3D664373+686499+/usr/local/ww= w /db/text/2003/freebsd-hackers/20030216.freebsd-hackers+raw old patch by Orlando Bassotto 2) http://mad.ieo-research.it/ also by Orlando=20 3) http://docs.freebsd.org/cgi/getmsg.cgi?fetch=3D2034341+0+archive/2003/fre= e bsd-current/20030608.freebsd-current+raw mail from David O'Brien with patches he use.=20 4) http://chibis.persons.gfk.ru/audigy/ mine 5) http://chibis.persons.gfk.ru/audigy/alexander/audigy_pack.tgz old patches for 4.x and early 5.0 kernels by Alexander Kurilovich=20 > /sys/dev/sound/pci/emu10k1.c defines the following: >=20 > #define EMU10K1_PCI_ID 0x00021102 > #define EMU10K2_PCI_ID 0x00041102 >=20 It only knows about PCI IDs. In-kernel driver cannot initialize and control Audigy cards. > P.S. FreeBSD pickle 5.1-RELEASE-p10 FreeBSD 5.1-RELEASE-p10=20 > #0: Mon Nov 3 19:10:54 EST 2003 =20 > anthony@pickle:/usr/src/sys/i386/compile/PICKLE i386 >=20 Yuriy Tsibizov, http://chibis.persons.gfk.ru From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 4 00:19:00 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F3DA016A4CE; Tue, 4 Nov 2003 00:18:59 -0800 (PST) Received: from VARK.homeunix.com (adsl-68-123-40-77.dsl.pltn13.pacbell.net [68.123.40.77]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3965C43F75; Tue, 4 Nov 2003 00:18:59 -0800 (PST) (envelope-from das@FreeBSD.ORG) Received: from VARK.homeunix.com (localhost [127.0.0.1]) by VARK.homeunix.com (8.12.9/8.12.9) with ESMTP id hA48I1en078708; Tue, 4 Nov 2003 00:18:01 -0800 (PST) (envelope-from das@FreeBSD.ORG) Received: (from das@localhost) by VARK.homeunix.com (8.12.9/8.12.9/Submit) id hA48I1Hr078707; Tue, 4 Nov 2003 00:18:01 -0800 (PST) (envelope-from das@FreeBSD.ORG) Date: Tue, 4 Nov 2003 00:18:00 -0800 From: David Schultz To: Igor Serikov Message-ID: <20031104081800.GA78439@VARK.homeunix.com> Mail-Followup-To: Igor Serikov , FreeBSD Bugs , FreeBSD Hackers References: <3FA61A17.70605@turtle.freedns.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3FA61A17.70605@turtle.freedns.us> cc: FreeBSD Hackers cc: FreeBSD Bugs Subject: Re: rfork problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Nov 2003 08:19:00 -0000 On Mon, Nov 03, 2003, Igor Serikov wrote: > > Hello, > > Combining flags RFNOWAIT and RFPPWAIT in rfork(2) under 4.6-RELEASE > makes the parent process sleeping on channel "ppwait" forever. RFPPWAIT tells rfork() to wait for the child to exit, and RFNOWAIT tells rfork() to detach the child such that it never tells the parent when it exits. So you're getting exactly what you asked for, as silly as it may be. From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 4 01:11:34 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DEDD016A4CF; Tue, 4 Nov 2003 01:11:34 -0800 (PST) Received: from turtle.freedns.us (netblock-66-159-221-76.dslextreme.com [66.159.221.76]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5498943FE5; Tue, 4 Nov 2003 01:11:33 -0800 (PST) (envelope-from bt@turtle.freedns.us) Received: from turtle.freedns.us (localhost [127.0.0.1]) by turtle.freedns.us (8.12.9p2/8.12.3) with ESMTP id hA49BVq3000289; Tue, 4 Nov 2003 01:11:31 -0800 (PST) (envelope-from bt@turtle.freedns.us) Message-ID: <3FA76D43.1040508@turtle.freedns.us> Date: Tue, 04 Nov 2003 01:11:31 -0800 From: Igor Serikov Organization: Private Person User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.0.1) Gecko/20030209 X-Accept-Language: ru, en MIME-Version: 1.0 To: David Schultz References: <3FA61A17.70605@turtle.freedns.us> <20031104081800.GA78439@VARK.homeunix.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: FreeBSD Hackers cc: FreeBSD Bugs Subject: Re: rfork problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Nov 2003 09:11:35 -0000 David, Is it okay to have a condition that can be created by a mortal user and then cannot be changed by the root? The waiting process cannot be killed and would keep "waiting" till system reboot. I do not think it is a good idea to make ppwait state uninterruptible in any case. As to RFNOWAIT, I believe that the correct behavior is to detach after leaving ppwait. David Schultz wrote: > On Mon, Nov 03, 2003, Igor Serikov wrote: > >> Hello, >> >>Combining flags RFNOWAIT and RFPPWAIT in rfork(2) under 4.6-RELEASE >>makes the parent process sleeping on channel "ppwait" forever. > > > RFPPWAIT tells rfork() to wait for the child to exit, and RFNOWAIT > tells rfork() to detach the child such that it never tells the > parent when it exits. So you're getting exactly what you asked > for, as silly as it may be. > > From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 4 08:36:57 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5124B16A4CE for ; Tue, 4 Nov 2003 08:36:57 -0800 (PST) Received: from gunjin.wccnet.org (gunjin.wccnet.org [198.111.176.99]) by mx1.FreeBSD.org (Postfix) with ESMTP id A444943F75 for ; Tue, 4 Nov 2003 08:36:55 -0800 (PST) (envelope-from anthony@gunjin.wccnet.org) Received: from gunjin.wccnet.org (localhost.rexroof.com [127.0.0.1]) by gunjin.wccnet.org (8.12.3/8.12.2) with ESMTP id hA4Gex2m047375; Tue, 4 Nov 2003 11:40:59 -0500 (EST) Received: (from anthony@localhost) by gunjin.wccnet.org (8.12.3/8.12.3/Submit) id hA4GesbG047372; Tue, 4 Nov 2003 11:40:54 -0500 (EST) Date: Tue, 4 Nov 2003 11:40:54 -0500 From: Anthony Schneider To: Yuriy Tsibizov Message-ID: <20031104164054.GA47060@x-anthony.com> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="uAKRQypu60I7Lcqm" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i cc: freebsd-hackers@freebsd.org Subject: Re: Sound Blaster Audigy LS problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Nov 2003 16:36:57 -0000 --uAKRQypu60I7Lcqm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Well, it appears from your page that this driver will not work on 5.1-RELEASE (as stated from i guess 2003-10-19). I tried building your driver (on 5.1-RELEASE-p10), and it seemed that i just needed to add #define PCIR_BARS 0x10 #define PCIR_BAR(x)(PCIR_BARS + (x) * 4) and also strip (yes, bad) some arguments from busdma_tag_create() to=20 successfully build. are these differences (addition of PCIR_BAR and=20 PCI_BARS macros and altered prototype of busdma_tag_create()) ones that we can expect to be moving *towards* in -CURRENT, or are they ones we=20 have moved away from with -RELEASE? also, do you think that by just redefining the PCI id to match my card's PCI id for EMU10K2 would fix my problem if the lockfunc and lockarg were returned back to to busdma_tag_create() (assuming i moved to -CURRENT where I expect they currently reside)? do you perhaps know if the audigy ls card uses an audigy 2 chipset? after much searching i could not find any datasheet-style information on the audigy ls beyond the usual frequency and decibel measurements on creative's specification link on the product page for this card. thank you very much for your response. -Anthony. On Tue, Nov 04, 2003 at 10:26:53AM +0300, Yuriy Tsibizov wrote: > > Dear @hackers, > > i recently bought a soundblaster audigy ls card hoping that it > > would "just work" with freebsd, but sadly this is not the=20 > > case.=20 >=20 > Anthony, >=20 > Audigy is not supported in -CURRENT kernel, but there are some patches > to make it work under FreeBSD. I know about five of them:=20 > 1) > http://www.freebsd.org/cgi/getmsg.cgi?fetch=3D664373+686499+/usr/local/www > /db/text/2003/freebsd-hackers/20030216.freebsd-hackers+raw old patch by > Orlando Bassotto > 2) http://mad.ieo-research.it/ also by Orlando=20 > 3) > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=3D2034341+0+archive/2003/free > bsd-current/20030608.freebsd-current+raw mail from David O'Brien with > patches he use.=20 > 4) http://chibis.persons.gfk.ru/audigy/ mine > 5) http://chibis.persons.gfk.ru/audigy/alexander/audigy_pack.tgz old > patches for 4.x and early 5.0 kernels by Alexander Kurilovich=20 >=20 > > /sys/dev/sound/pci/emu10k1.c defines the following: > >=20 > > #define EMU10K1_PCI_ID 0x00021102 > > #define EMU10K2_PCI_ID 0x00041102 > >=20 > It only knows about PCI IDs. In-kernel driver cannot initialize and > control Audigy cards. >=20 > > P.S. FreeBSD pickle 5.1-RELEASE-p10 FreeBSD 5.1-RELEASE-p10=20 > > #0: Mon Nov 3 19:10:54 EST 2003 =20 > > anthony@pickle:/usr/src/sys/i386/compile/PICKLE i386 > >=20 >=20 >=20 > Yuriy Tsibizov, > http://chibis.persons.gfk.ru >=20 --uAKRQypu60I7Lcqm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE/p9aVKUeW47UGY2kRAnV2AJ9l72MWhqx9uhEDYdtbghHncJGSTwCeO49z sLbjuOyvTMm5w85q7tKO3Rw= =kuV8 -----END PGP SIGNATURE----- --uAKRQypu60I7Lcqm-- From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 4 08:52:27 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D2E4616A4CE for ; Tue, 4 Nov 2003 08:52:27 -0800 (PST) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id C33CC43FBF for ; Tue, 4 Nov 2003 08:52:26 -0800 (PST) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id hA4GqQ1G005998 for ; Tue, 4 Nov 2003 11:52:26 -0500 (EST) Date: Tue, 4 Nov 2003 11:52:26 -0500 (EST) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: hackers@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: ANN: New UNIX Internationalization Guide Book (fwd) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: hackers@freebsd.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Nov 2003 16:52:27 -0000 FYI ---------- Forwarded message ---------- Date: Tue, 4 Nov 2003 16:37:40 GMT From: Andrew Josey To: austin-group-l@opengroup.org Subject: ANN: New UNIX Internationalization Guide Book Resent-Date: 4 Nov 2003 16:37:58 -0000 Resent-From: austin-group-l@opengroup.org Resent-To: austin-group-l@opengroup.org The Open Group, in association with Sun Microsystems, is pleased to announce availability of a new Guide Book covering the Internationalization features of Version 3 of the Single UNIX Specification and IEEE Std 1003.1-2001 (POSIX); The book costs GBP 19, US$ 31.50, EUR 27.50 and includes the complete Single UNIX Specification, Versions 1, 2 and 3 on the accompanying CD-ROM in HTML and PDF formats. For more information on The UNIX Internationalization Guide including ordering information see http://www.opengroup.org/pubs/catalog/g032.htm ----- Andrew Josey The Open Group Austin Group Chair Apex Plaza,Forbury Road, Email: a.josey@opengroup.org Reading,Berks.RG1 1AX,England Tel: +44 118 9508311 ext 2250 Fax: +44 118 9500110 From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 4 09:02:39 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8071916A4CE for ; Tue, 4 Nov 2003 09:02:39 -0800 (PST) Received: from relay.pair.com (relay.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 385D743FDF for ; Tue, 4 Nov 2003 09:02:38 -0800 (PST) (envelope-from silby@silby.com) Received: (qmail 71171 invoked from network); 4 Nov 2003 17:02:36 -0000 Received: from niwun.pair.com (HELO localhost) (209.68.2.70) by relay.pair.com with SMTP; 4 Nov 2003 17:02:36 -0000 X-pair-Authenticated: 209.68.2.70 Date: Tue, 4 Nov 2003 11:02:35 -0600 (CST) From: Mike Silbersack To: Vivek Pai In-Reply-To: <3FA2C43E.3030204@cs.princeton.edu> Message-ID: <20031104104729.S1684@odysseus.silby.com> References: <1066789354.21430.39.camel@boxster.onthenet.com.au> <20031022082953.GA69506@rot13.obsecurity.org> <1066816287.25609.34.camel@boxster.onthenet.com.au> <20031022095754.GA70026@rot13.obsecurity.org> <1067183332.3f9bece4c0cf4@webmail.cs.princeton.edu> <3FA2C43E.3030204@cs.princeton.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hackers@freebsd.org cc: Alan Cox Subject: Update: Debox sendfile modifications X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Nov 2003 17:02:39 -0000 Ok, I've reread the debox paper, looked over the patch, and talked to Alan Cox about his present and upcoming work on the vm system. The debox patch does three basic things (if I'm understanding everything correctly.): 1. It ensures that the header is sent in the same packet as the first part of the data, fixing performance with small files. - This part of the patch needs a little cleanup, but that's easy enough. I will try to integrate it next week. 2. The patch merges sendfile buffers so that when the same page is sent to multiple connections, kernel address space is not wasted. - While this is the part of the patch with the widest benefit, it will be the most difficult to integrate. In order to support 64-bit architectures better, Alan has refactored the sendfile code, meaning that the patch would have to be rewritten to fit this new layout. 3. The patch returns a new error when sendfile realizes that it will have to block on disk I/O, thereby allowing Flash to have a helper do the blocking call. - While this change could be made easily enough, I'm not sure that it would benefit anything other than Flash, so I'm not certain if we should do it. However, based on what you learned with Flash, I have an alternate idea: --- Suppose that sendfile is called to send to a non-blocking socket, and that it detects that the page(s) required are not in memory, and that disk I/O will be necessary. Instead of blocking, sendfile would call a sendfile helper kernel thread (either by calling kthread_create, or by having a preexisting pool.) After dispatching this thread, sendfile would return EWOULDBLOCK to the caller. Note that only a limited number of threads would exist (perhaps 8?), so, if all threads were busy, sendfile would have to block like it does at present. Once the I/O was complete, the thread would call sowakeup (or whatever is called typically when a thread is now ready for writing) for the socket in question. The application would call sendfile, like normal, but this time everything would succeed because the page would be in memory. --- If such a feature were implemented, it might have the same increased performance effect that your new return value does, except that it would require no modification for a non-blocking sendfile based application to take advantage of it. Alan, would this be possible from the VM system's perspective? Is it safe to assume that once the page in question was in the page cache that it would hang around long enough for the second sendfile call to access it before it is paged back out again? Thanks, Mike "Silby" Silbersack From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 4 10:27:07 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BA18416A4CE for ; Tue, 4 Nov 2003 10:27:07 -0800 (PST) Received: from bluebox.CS.Princeton.EDU (bluebox.CS.Princeton.EDU [128.112.136.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA76A43FDD for ; Tue, 4 Nov 2003 10:27:06 -0800 (PST) (envelope-from vivek@CS.Princeton.EDU) Received: from cs.princeton.edu (oakley [128.112.139.27]) (authenticated bits=0)hA4IR3DF024626 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 4 Nov 2003 13:27:04 -0500 (EST) Message-ID: <3FA7EF77.5010808@cs.princeton.edu> Date: Tue, 04 Nov 2003 13:27:03 -0500 From: Vivek Pai User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.0.1) Gecko/20020920 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mike Silbersack References: <1066789354.21430.39.camel@boxster.onthenet.com.au> <20031022082953.GA69506@rot13.obsecurity.org> <1066816287.25609.34.camel@boxster.onthenet.com.au> <20031022095754.GA70026@rot13.obsecurity.org> <1066820436.25609.93.camel@boxster.onthenet.com.au> <1067183332.3f9bece4c0cf4@webmail.cs.princeton.edu> <20031026121527.K2023@odysseus.silby.com> <3FA2C43E.3030204@cs.princeton.edu> <20031104104729.S1684@odysseus.silby.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-hackers@freebsd.org cc: Alan Cox Subject: Re: Update: Debox sendfile modifications X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Nov 2003 18:27:07 -0000 Sorry for not replying sooner - under deadline pressure right now. Mike Silbersack wrote: > Ok, I've reread the debox paper, looked over the patch, and talked to Alan > Cox about his present and upcoming work on the vm system. > > The debox patch does three basic things (if I'm understanding everything > correctly.): > > 1. It ensures that the header is sent in the same packet as the first > part of the data, fixing performance with small files. > > - This part of the patch needs a little cleanup, but that's easy enough. > I will try to integrate it next week. ok, that sounds good > 2. The patch merges sendfile buffers so that when the same page is sent > to multiple connections, kernel address space is not wasted. > > - While this is the part of the patch with the widest benefit, it will be > the most difficult to integrate. In order to support 64-bit architectures > better, Alan has refactored the sendfile code, meaning that the patch > would have to be rewritten to fit this new layout. The one other aspect of this is that sf_bufs mappings are maintained for a configurable amount of time, reducing the number of TLB ops. You can specify the parameter for how long, ranging from -1 (no coalescing at all), 0 (coalesce, but free immediately after last holder release), to any other time. Obviously, any value above 0 will increase the amount of wired memory at any given point in time, but it's configurable. > 3. The patch returns a new error when sendfile realizes that it will have > to block on disk I/O, thereby allowing Flash to have a helper do the > blocking call. > > - While this change could be made easily enough, I'm not sure that it > would benefit anything other than Flash, so I'm not certain if we should > do it. However, based on what you learned with Flash, I have an alternate > idea: > > --- > > Suppose that sendfile is called to send to a non-blocking socket, and that > it detects that the page(s) required are not in memory, and that disk I/O > will be necessary. Instead of blocking, sendfile would call a sendfile > helper kernel thread (either by calling kthread_create, or by having a > preexisting pool.) After dispatching this thread, sendfile would return > EWOULDBLOCK to the caller. Note that only a limited number of threads > would exist (perhaps 8?), so, if all threads were busy, sendfile would > have to block like it does at present. > > Once the I/O was complete, the thread would call sowakeup (or whatever is > called typically when a thread is now ready for writing) for the socket in > question. The application would call sendfile, like normal, but this time > everything would succeed because the page would be in memory. > > --- > > If such a feature were implemented, it might have the same increased > performance effect that your new return value does, except that it would > require no modification for a non-blocking sendfile based application to > take advantage of it. > > Alan, would this be possible from the VM system's perspective? Is it safe > to assume that once the page in question was in the page cache that it > would hang around long enough for the second sendfile call to access it > before it is paged back out again? There are two problems to this approach that I see a) you'd have to return a value back to sendfile while this async operation is in progress, because you don't have any other non-intrusive way of giving back the return value at any other time b) once that small number of kernel threads gets exhausted, you lose the opportunity to serve requests out of main memory part (a) means that this change can't be made completely without application re-coding, and part (b) means that more sophisticated applications could lose performance. How about something that lets you choose what happens - we've got a flag field anyway, so why not have options to control the behavior on missing pages? Applications like Flash might just want the error message so that they can handle it themselves, while other applications may be happy with the default that you're suggesting. -Vivek From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 4 11:16:27 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7C9A416A4CE; Tue, 4 Nov 2003 11:16:27 -0800 (PST) Received: from VARK.homeunix.com (adsl-68-123-40-77.dsl.pltn13.pacbell.net [68.123.40.77]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9DD7343F93; Tue, 4 Nov 2003 11:16:26 -0800 (PST) (envelope-from das@FreeBSD.ORG) Received: from VARK.homeunix.com (localhost [127.0.0.1]) by VARK.homeunix.com (8.12.9/8.12.9) with ESMTP id hA4JFRen081923; Tue, 4 Nov 2003 11:15:27 -0800 (PST) (envelope-from das@FreeBSD.ORG) Received: (from das@localhost) by VARK.homeunix.com (8.12.9/8.12.9/Submit) id hA4JFRl8081922; Tue, 4 Nov 2003 11:15:27 -0800 (PST) (envelope-from das@FreeBSD.ORG) Date: Tue, 4 Nov 2003 11:15:26 -0800 From: David Schultz To: Igor Serikov Message-ID: <20031104191526.GA79079@VARK.homeunix.com> Mail-Followup-To: Igor Serikov , FreeBSD Bugs , FreeBSD Hackers References: <3FA61A17.70605@turtle.freedns.us> <20031104081800.GA78439@VARK.homeunix.com> <3FA76D43.1040508@turtle.freedns.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3FA76D43.1040508@turtle.freedns.us> cc: FreeBSD Hackers cc: FreeBSD Bugs Subject: Re: rfork problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Nov 2003 19:16:27 -0000 On Tue, Nov 04, 2003, Igor Serikov wrote: > > David, > > Is it okay to have a condition that can be created by a mortal user and > then cannot be changed by the root? The waiting process cannot be killed > and would keep "waiting" till system reboot. Aah, I see. No, it's not okay that a non-root user can create an unkillable process. -CURRENT doesn't have this problem because it rightly fails when a userland program tries to use RFPPWAIT. (It isn't supposed to be available to userland, which is why it isn't documented.) The problem could be fixed by backporting the relevant bits from -CURRENT. > I do not think it is a good idea to make ppwait state uninterruptible in > any case. I do not think it would be safe to deliver a signal to a parent process while a vforked child is borrowing its address space. Here's a patch against -STABLE: Index: kern_fork.c =================================================================== RCS file: /cvs/src/sys/kern/kern_fork.c,v retrieving revision 1.72.2.15 diff -u -r1.72.2.15 kern_fork.c --- kern_fork.c 28 Sep 2003 11:08:31 -0000 1.72.2.15 +++ kern_fork.c 4 Nov 2003 19:13:33 -0000 @@ -130,6 +130,9 @@ int error; struct proc *p2; + /* Don't allow kernel only flags. */ + if ((uap->flags & RFKERNELONLY) != 0) + return (EINVAL); error = fork1(p, uap->flags, &p2); if (error == 0) { p->p_retval[0] = p2 ? p2->p_pid : 0; From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 4 11:49:13 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D92816A4CE; Tue, 4 Nov 2003 11:49:13 -0800 (PST) Received: from sweeper.openet-telecom.com (mail.openet-telecom.com [62.17.151.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id 19D9B43FD7; Tue, 4 Nov 2003 11:49:11 -0800 (PST) (envelope-from peter.edwards@openet-telecom.com) Received: from mail.openet-telecom.com (unverified) by sweeper.openet-telecom.com ; Tue, 4 Nov 2003 19:50:12 +0000 Received: from openet-telecom.com (10.0.0.40) by mail.openet-telecom.com (NPlex 6.5.027) (authenticated as peter.edwards@openet-telecom.com) id 3FA62F9800001E8F; Tue, 4 Nov 2003 19:44:35 +0000 Message-ID: <3FA802AF.4030107@openet-telecom.com> Date: Tue, 04 Nov 2003 19:49:03 +0000 From: Peter Edwards User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20031104 X-Accept-Language: en-us, en MIME-Version: 1.0 To: David Schultz References: <3FA61A17.70605@turtle.freedns.us> <20031104081800.GA78439@VARK.homeunix.com> <3FA76D43.1040508@turtle.freedns.us> <20031104191526.GA79079@VARK.homeunix.com> In-Reply-To: <20031104191526.GA79079@VARK.homeunix.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: FreeBSD Hackers cc: FreeBSD Bugs cc: Igor Serikov Subject: Re: rfork problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Nov 2003 19:49:13 -0000 David Schultz wrote: >On Tue, Nov 04, 2003, Igor Serikov wrote: > > >> David, >> >>Is it okay to have a condition that can be created by a mortal user and >>then cannot be changed by the root? The waiting process cannot be killed >>and would keep "waiting" till system reboot. >> >> > >Aah, I see. No, it's not okay that a non-root user can create an >unkillable process. -CURRENT doesn't have this problem because it >rightly fails when a userland program tries to use RFPPWAIT. (It >isn't supposed to be available to userland, which is why it isn't >documented.) The problem could be fixed by backporting the >relevant bits from -CURRENT. > > > >>I do not think it is a good idea to make ppwait state uninterruptible in >>any case. >> >> > >I do not think it would be safe to deliver a signal to a parent >process while a vforked child is borrowing its address space. > >Here's a patch against -STABLE: > >Index: kern_fork.c >=================================================================== >RCS file: /cvs/src/sys/kern/kern_fork.c,v >retrieving revision 1.72.2.15 >diff -u -r1.72.2.15 kern_fork.c >--- kern_fork.c 28 Sep 2003 11:08:31 -0000 1.72.2.15 >+++ kern_fork.c 4 Nov 2003 19:13:33 -0000 >@@ -130,6 +130,9 @@ > int error; > struct proc *p2; > >+ /* Don't allow kernel only flags. */ >+ if ((uap->flags & RFKERNELONLY) != 0) >+ return (EINVAL); > error = fork1(p, uap->flags, &p2); > if (error == 0) { > p->p_retval[0] = p2 ? p2->p_pid : 0; >_______________________________________________ >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" > > I don't think -STABLE defines RFKERNELONLY (or some of the other rfork flags), so you need to add Index: unistd.h =================================================================== RCS file: /pub/FreeBSD/development/FreeBSD-CVS/src/sys/sys/unistd.h,v retrieving revision 1.22.2.2 diff -u -r1.22.2.2 unistd.h --- unistd.h 22 Aug 2000 01:46:30 -0000 1.22.2.2 +++ unistd.h 4 Nov 2003 19:46:03 -0000 @@ -218,6 +218,7 @@ #define RFSIGSHARE (1<<14) /* share signal handlers */ #define RFLINUXTHPN (1<<16) /* do linux clone exit parent notification */ #define RFPPWAIT (1<<31) /* parent sleeps until child exits (vfork) */ +#define RFKERNELONLY RFPPWAIT #endif /* !_POSIX_SOURCE */ From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 4 15:10:10 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CE22D16A4CE for ; Tue, 4 Nov 2003 15:10:10 -0800 (PST) Received: from webmail.tiscali.de (relay1.tiscali.de [62.26.116.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B08543FDF for ; Tue, 4 Nov 2003 15:10:09 -0800 (PST) (envelope-from walter@pelissero.de) Received: from daemon.home.loc (62.246.37.32) by webmail.tiscali.de (6.7.019) id 3F9D2AE2003FDD06 for hackers@freebsd.org; Wed, 5 Nov 2003 00:10:07 +0100 Received: from hyde.home.loc (hyde.home.loc [10.0.0.2]) by daemon.home.loc (8.12.9/8.12.8) with ESMTP id hA4N8oQH000800 for ; Wed, 5 Nov 2003 00:08:51 +0100 (CET) (envelope-from wcp@hyde.home.loc) Received: from hyde.home.loc (localhost [127.0.0.1]) by hyde.home.loc (8.12.9/8.12.8) with ESMTP id hA4N8ogV000549 for ; Wed, 5 Nov 2003 00:08:50 +0100 (CET) (envelope-from wcp@hyde.home.loc) Received: (from wcp@localhost) by hyde.home.loc (8.12.9/8.12.6/Submit) id hA4N8nM0000546; Wed, 5 Nov 2003 00:08:49 +0100 (CET) (envelope-from wcp) From: "Walter C. Pelissero" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16296.12673.686825.358250@hyde.home.loc> Date: Wed, 5 Nov 2003 00:08:49 +0100 To: hackers@freebsd.org In-Reply-To: <16293.41551.103901.897025@hyde.home.loc> References: <16293.41551.103901.897025@hyde.home.loc> X-Mailer: VM 7.16 under Emacs 21.3.50.2 X-Attribution: WP Subject: SCSI spin down on suspend (patch) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: walter@pelissero.de List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Nov 2003 23:10:11 -0000 I amended the patch. Now: - the behaviour is controlled by a sysctl (off by default) . - a 1s delay is done after each drive spin up, making things easier for the system power supply - no need to define anything; APM or ACPI methods are chosen according to what has been made available in the kernel configuration file; if neither APM or ACPI is selcted the code is (mostly) removed I tried to introduce a cache flush before the spin down, but it didn't work (system panic), so the code is there but ifdef-ed out. Maybe somebody with a deeper knowledge of the CAM layer could shed a light. Once I get some confidence about the stability of the patch, and if anybody is interested, I could submit a pr. One thing I forgot to mention in my former message: the patch has been tested on 4.9-STABLE only. Enjoy. -- walter pelissero http://www.pelissero.de --- scsi_da.c.orig Mon Nov 3 00:15:55 2003 +++ scsi_da.c Tue Nov 4 20:20:54 2003 @@ -72,6 +72,21 @@ #include #endif /* !_KERNEL */ +#include +#include +/* to get DELAY declaration */ +#include + +#if NAPM > 0 +# include +#endif + +#if NACPICA > 0 +# include +# include +# include +#endif + #ifdef _KERNEL typedef enum { DA_STATE_PROBE, @@ -414,6 +435,8 @@ struct scsi_read_capacity_data * rdcap); static timeout_t dasendorderedtag; static void dashutdown(void *arg, int howto); +static void dasync(struct cam_periph *periph); +static void daspin(struct cam_periph *periph, int up); #ifndef DA_DEFAULT_TIMEOUT #define DA_DEFAULT_TIMEOUT 60 /* Timeout in seconds */ @@ -435,6 +458,11 @@ SYSCTL_INT(_kern_cam_da, OID_AUTO, default_timeout, CTLFLAG_RW, &da_default_timeout, 0, "Normal I/O timeout (in seconds)"); TUNABLE_INT("kern.cam.da.default_timeout", &da_default_timeout); +#if NAPM > 0 || NACPICA > 0 +static int da_spindown_on_suspend = 0; +SYSCTL_INT(_kern_cam_da, OID_AUTO, spindown_on_suspend, CTLFLAG_RW, + &da_spindown_on_suspend, 0, "Spindown hard disks on system suspend"); +#endif /* * DA_ORDEREDTAG_INTERVAL determines how often, relative @@ -490,6 +518,95 @@ static SLIST_HEAD(,da_softc) softc_list; static struct extend_array *daperiphs; +#if NAPM > 0 || NACPICA > 0 +/* Step through all DA peripheral drivers and spin them up/down. */ +static void +da_spin_all(int up) +{ + struct cam_periph *periph; + + for (periph = TAILQ_FIRST(&dadriver.units); periph != NULL; + periph = TAILQ_NEXT(periph, unit_links)) { +#if 0 /* this panics the system -wcp4/11/03. */ + /* if spinning down, it might be safer to synchronise + * the cache before */ + if (!up) + dasync(periph); +#endif + daspin(periph, up); + /* If spinning up, wait a moment to avoid overloading + * the power supply. A better solution would be to + * check until the device is ready. I don't know how + * to do it, though. */ + if (up) + DELAY(1000 * 1000); + } +} + +static void +da_suspend(void) +{ + if (da_spindown_on_suspend) + da_spin_all(0); +} + +static void +da_resume(void) +{ + if (da_spindown_on_suspend) + da_spin_all(1); +} +#endif /* NAPM > 0 || NACPICA > 0 */ + +/* The mechanism to hook functions to certain events in the APM and + * ACPI code are different for no apparent reason. */ + +#if NAPM > 0 +static int +da_apm_suspend (void *junk) +{ + da_suspend(); + return 0; +} + +static int +da_apm_resume (void *junk) +{ + da_resume(); + return 0; +} + +struct apmhook da_apm_suspend_hook = { + 0, /* next */ + da_apm_suspend, /* fun */ + 0, /* arg */ + "da_suspend", /* name */ + 0 /* order */ +}; + +struct apmhook da_apm_resume_hook = { + 0, /* next */ + da_apm_resume, /* fun */ + 0, /* arg */ + "da_resume", /* name */ + 0 /* order */ +}; +#endif /* NAPM > 0 */ + +#if NACPICA > 0 +static void +da_acpi_resume(void *arg, int state) +{ + da_resume(); +} + +static void +da_acpi_suspend(void *arg, int state) +{ + da_suspend(); +} +#endif /* NACPICA > 0 */ + static int daopen(dev_t dev, int flags, int fmt, struct proc *p) { @@ -987,6 +1104,14 @@ if ((EVENTHANDLER_REGISTER(shutdown_post_sync, dashutdown, NULL, SHUTDOWN_PRI_DEFAULT)) == NULL) printf("dainit: shutdown event registration failed!\n"); +#if NACPICA > 0 + EVENTHANDLER_REGISTER(acpi_sleep_event, da_acpi_suspend, NULL, ACPI_EVENT_PRI_DEFAULT); + EVENTHANDLER_REGISTER(acpi_wakeup_event, da_acpi_resume, NULL, ACPI_EVENT_PRI_DEFAULT); +#endif +#if NAPM > 0 + apm_hook_establish (APM_HOOK_SUSPEND, &da_apm_suspend_hook); + apm_hook_establish (APM_HOOK_RESUME, &da_apm_resume_hook); +#endif } } @@ -1888,6 +2013,109 @@ timeout(dasendorderedtag, NULL, (da_default_timeout * hz) / DA_ORDEREDTAG_INTERVAL); } + +static void +daspin(struct cam_periph *periph, int up) +{ + struct da_softc *softc; + union ccb ccb; + + softc = (struct da_softc *)periph->softc; + + xpt_setup_ccb(&ccb.ccb_h, periph->path, /*priority*/1); + + ccb.ccb_h.ccb_state = DA_CCB_DUMP; + scsi_start_stop(&ccb.csio, + /*retries*/ 1, + /*cbfcnp*/ dadone, + MSG_SIMPLE_Q_TAG, + /*up/down*/ up, + /*load_eject*/ 0, + /*immediate*/ FALSE, + /*sense_len*/ SSD_FULL_SIZE, + /*timeout*/ 50000); + xpt_polled_action(&ccb); + + if ((ccb.ccb_h.status & CAM_STATUS_MASK) != CAM_REQ_CMP) { + if (((ccb.ccb_h.status & CAM_STATUS_MASK) == + CAM_SCSI_STATUS_ERROR) + && (ccb.csio.scsi_status == SCSI_STATUS_CHECK_COND)){ + int error_code, sense_key, asc, ascq; + + scsi_extract_sense(&ccb.csio.sense_data, + &error_code, &sense_key, + &asc, &ascq); + + if (sense_key != SSD_KEY_ILLEGAL_REQUEST) + scsi_sense_print(&ccb.csio); + } else { + xpt_print_path(periph->path); + printf("Spin %s disk failed, status " + "== 0x%x, scsi status == 0x%x\n", + (up ? "up" : "down"), + ccb.ccb_h.status, ccb.csio.scsi_status); + } + } + CAM_DEBUG(periph->path, CAM_DEBUG_TRACE, + ("daspin: spinned ~A\n", (up ? "up" : "down"))); +} + +/* This would be used only in da_spin_all and it panics the system + -wcp4/11/03.*/ +#if 0 +static void +dasync(struct cam_periph *periph) +{ + struct da_softc *softc; + union ccb ccb; + + softc = (struct da_softc *)periph->softc; + + /* We only sync the cache if the drive is open, and if the + * drive is capable of it. */ + if (((softc->flags & DA_FLAG_OPEN) == 0) + || (softc->quirks & DA_Q_NO_SYNC_CACHE)) + return; + + xpt_setup_ccb(&ccb.ccb_h, periph->path, /*priority*/1); + ccb.ccb_h.ccb_state = DA_CCB_DUMP; + scsi_synchronize_cache(&ccb.csio, + /*retries*/1, + /*cbfcnp*/dadone, + MSG_SIMPLE_Q_TAG, + /*begin_lba*/0, /* whole disk */ + /*lb_count*/0, + SSD_FULL_SIZE, + 5 * 60 * 1000); + xpt_polled_action(&ccb); + + if ((ccb.ccb_h.status & CAM_STATUS_MASK) != CAM_REQ_CMP) { + if (((ccb.ccb_h.status & CAM_STATUS_MASK) == + CAM_SCSI_STATUS_ERROR) + && (ccb.csio.scsi_status == SCSI_STATUS_CHECK_COND)){ + int error_code, sense_key, asc, ascq; + + scsi_extract_sense(&ccb.csio.sense_data, + &error_code, &sense_key, + &asc, &ascq); + + if (sense_key != SSD_KEY_ILLEGAL_REQUEST) + scsi_sense_print(&ccb.csio); + } else { + xpt_print_path(periph->path); + printf("Synchronize cache failed, status " + "== 0x%x, scsi status == 0x%x\n", + ccb.ccb_h.status, ccb.csio.scsi_status); + } + } + if ((ccb.ccb_h.status & CAM_DEV_QFRZN) != 0) + cam_release_devq(ccb.ccb_h.path, + /*relsim_flags*/0, + /*reduction*/0, + /*timeout*/0, + /*getcount_only*/0); +} +#endif /* 0 */ /* * Step through all DA peripheral drivers, and if the device is still open, From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 4 17:20:49 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 94D9C16A4CE for ; Tue, 4 Nov 2003 17:20:49 -0800 (PST) Received: from mail.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1664C43FAF for ; Tue, 4 Nov 2003 17:20:48 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (qmail 21536 invoked from network); 5 Nov 2003 01:20:47 -0000 Received: from unknown (HELO hydrogen.funkthat.com) ([69.17.45.168]) (envelope-sender ) by mail6.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 5 Nov 2003 01:20:47 -0000 Received: from hydrogen.funkthat.com (wluzyr@localhost.funkthat.com [127.0.0.1])hA51KkgP037693; Tue, 4 Nov 2003 17:20:46 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.12.10/8.12.10/Submit) id hA51Kjwt037692; Tue, 4 Nov 2003 17:20:45 -0800 (PST) Date: Tue, 4 Nov 2003 17:20:45 -0800 From: John-Mark Gurney To: Mike Silbersack Message-ID: <20031105012044.GY558@funkthat.com> Mail-Followup-To: Mike Silbersack , Vivek Pai , freebsd-hackers@freebsd.org, Alan Cox References: <1066789354.21430.39.camel@boxster.onthenet.com.au> <20031022082953.GA69506@rot13.obsecurity.org> <1066816287.25609.34.camel@boxster.onthenet.com.au> <20031022095754.GA70026@rot13.obsecurity.org> <1067183332.3f9bece4c0cf4@webmail.cs.princeton.edu> <3FA2C43E.3030204@cs.princeton.edu> <20031104104729.S1684@odysseus.silby.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031104104729.S1684@odysseus.silby.com> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.2-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html cc: freebsd-hackers@freebsd.org cc: Vivek Pai cc: Alan Cox Subject: Re: Update: Debox sendfile modifications X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: John-Mark Gurney List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Nov 2003 01:20:49 -0000 Mike Silbersack wrote this message on Tue, Nov 04, 2003 at 11:02 -0600: > Suppose that sendfile is called to send to a non-blocking socket, and that > it detects that the page(s) required are not in memory, and that disk I/O > will be necessary. Instead of blocking, sendfile would call a sendfile > helper kernel thread (either by calling kthread_create, or by having a > preexisting pool.) After dispatching this thread, sendfile would return > EWOULDBLOCK to the caller. Note that only a limited number of threads > would exist (perhaps 8?), so, if all threads were busy, sendfile would > have to block like it does at present. > > Once the I/O was complete, the thread would call sowakeup (or whatever is > called typically when a thread is now ready for writing) for the socket in > question. The application would call sendfile, like normal, but this time > everything would succeed because the page would be in memory. > > --- > > If such a feature were implemented, it might have the same increased > performance effect that your new return value does, except that it would > require no modification for a non-blocking sendfile based application to > take advantage of it. This would not work with kqueues as kevents are level triggered, not edge... so, this idea is bad/broken. I don't even think it would work with select since when you call select, it will check the availabilty of writing at the select call time.. You'd have to add a flag to the fd so mark it as delayed for another reason.. I don't think this feature can be cleanly added w/o somehow tieing fd's together. One call that I would like to see is a fd to fd copy. You pass in both fd's with maybe a length, and then a kernel helper thread does the copy or something. This would have other uses in that you can then "plumb" pipes between programs in a more effecient manner... This would also possibly fix/replace sendfile as sendfile isn't more different. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 4 20:56:08 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2631616A4CE for ; Tue, 4 Nov 2003 20:56:08 -0800 (PST) Received: from dastardly.newsbastards.org.72.27.172.IN-addr.ARPA.NOSPAM.dyndns.dk (B7774.b.pppool.de [213.7.119.116]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC94C43FB1 for ; Tue, 4 Nov 2003 20:55:22 -0800 (PST) (envelope-from bounce@NOSPAM.dyndns.dk) Received: from NOSPAM.spam.NOSPAM.spam.NOSPAM.dyndns.dk (NOSPAM.spam.NOSPAM.spam.NOSPAM.dyndns.dk [2002:d507:7774:0:200:c0ff:fefc:19aa]) (8.11.6/8.11.6-SPAMMERS-DeLiGHt) with ESMTP id hA54sgg89220 verified NO) for ; Wed, 5 Nov 2003 05:54:44 +0100 (CET) (envelope-from bounce@NOSPAM.dyndns.dk) Received: (from beer@localhost)hA54sfw55036; Wed, 5 Nov 2003 05:54:41 +0100 (CET) (envelope-from bounce@NOSPAM.dyndns.dk) Date: Wed, 5 Nov 2003 05:54:41 +0100 (CET) Message-Id: <200311050454.hA54sfw55036@NOSPAM.spam.NOSPAM.spam.NOSPAM.dyndns.dk> X-Authentication-Warning: NOSPAM.spam.NOSPAM.spam.NOSPAM.dyndns.dk: beer set sender to bounce@NOSPAM.dyndns.dk using -f From: Barry Bouwsma References: <200309300326.h8U3QXx12997@Mail.NOSPAM.DynDNS.dK> <20030930103337.GL18891@cicely12.cicely.de> To: FreeBSD Hacking Group Subject: Re: USB2.0 external hub and ehci question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Nov 2003 04:56:08 -0000 [heh, got this reply over IPv6, sorry about the other bounce, at least some mail passes some ISPs, but drop me anyway and I'll catch the archives] [sorry for the delay, you know, offline, real-life, laziness, etc] > > namely, that I can't attach an external hub, supposedly with USB2.0 > > capability, and have it be recognized. > > When I connect the external hub in its place, I get the error that the > > port was disabled, STALLED -- just as I saw under old NetBSD. > cypress hubs stall the controll endpoint without a reason when running > high speed - even if it had one the specs say that the control endpoint > shouldn't stall at all. Oh wonderful. So I have a shiny USB1.x hub with a USB2.0 label. Heck, it was fun anyway, though it does sometimes work as USB1.x too... > I have a workaround for the probing problem, but USB2 hubs won't work > anyway, because at ehci is missing support for interrupt endpoints. Oh joy. I assume you mean that the current ehci.c codebase is missing the support for this, and that some time in the future it may be added or imported, rather than that it's not at all possible? In other words, if the USB2-labelled hubs I see frequently nowadays in grocery stores and the like might work later, I should still consider them, and/or trying to hack the codebase? In any case, maybe I need to disable the probing for a hub of this type, as a Long Time Ago, with NetBSD, the EHCI probe failed (that stalled error), and no USB1 attach was done. Admittedly, I don't know if this is also the case under FreeBSD, since I haven't properly updated my machine to -current. > Maybe there are other show stopppers too. Erk. Thanks for your informative replies! Barry Bouwsma From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 4 21:02:40 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0CC6416A4CE for ; Tue, 4 Nov 2003 21:02:40 -0800 (PST) Received: from dastardly.newsbastards.org.72.27.172.IN-addr.ARPA.NOSPAM.dyndns.dk (B7774.b.pppool.de [213.7.119.116]) by mx1.FreeBSD.org (Postfix) with ESMTP id 73FFB43FB1 for ; Tue, 4 Nov 2003 21:02:06 -0800 (PST) (envelope-from bounce@NOSPAM.dyndns.dk) Received: from NOSPAM.spam.NOSPAM.spam.NOSPAM.dyndns.dk (NOSPAM.spam.NOSPAM.spam.NOSPAM.dyndns.dk [2002:d507:7774:0:200:c0ff:fefc:19aa]) (8.11.6/8.11.6-SPAMMERS-DeLiGHt) with ESMTP id hA551Ng89236 verified NO) for ; Wed, 5 Nov 2003 06:01:26 +0100 (CET) (envelope-from bounce@NOSPAM.dyndns.dk) Received: (from beer@localhost)hA551MK55087; Wed, 5 Nov 2003 06:01:22 +0100 (CET) (envelope-from bounce@NOSPAM.dyndns.dk) Date: Wed, 5 Nov 2003 06:01:22 +0100 (CET) Message-Id: <200311050501.hA551MK55087@NOSPAM.spam.NOSPAM.spam.NOSPAM.dyndns.dk> X-Authentication-Warning: NOSPAM.spam.NOSPAM.spam.NOSPAM.dyndns.dk: beer set sender to bounce@NOSPAM.dyndns.dk using -f From: Barry Bouwsma References: <200309241632.h8OGWgs02770@Mail.NOSPAM.DynDNS.dK> <20030924191217.GZ21665@cicely12.cicely.de> To: FreeBSD Hacking Group Subject: Re: USB card overcurrent problems... X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Nov 2003 05:02:40 -0000 [Drop my (IPv6-only) address when replying -- I'm offline too much, and I'm not even sure if all the ISPs I use let IPv4 mail through either] [Sorry for being offline so long, and the delay in this reply...] > > fine, but the other one, an OHCI card, out-of-the-box exhibits problems. > > Chipset is identified in dmesg as NEC uPD 9210 USB controller. > Current protection and limiting is completely up to the card designer. > The best that FreeBSD can do is getting informed if the card design > allows it, but I almost never saw a card doing this. The source has the following comment: /* Fiddle the No OverCurrent Protection bit to avoid chip bug. */ desca = OREAD4(sc, OHCI_RH_DESCRIPTOR_A); OWRITE4(sc, OHCI_RH_DESCRIPTOR_A, desca | OHCI_NOCP); OWRITE4(sc, OHCI_RH_STATUS, OHCI_LPSC); /* Enable port power */ usb_delay_ms(&sc->sc_bus, OHCI_ENABLE_POWER_DELAY); OWRITE4(sc, OHCI_RH_DESCRIPTOR_A, desca); (Somehow that didn't make it into my hacked code; hmmm, I wonder if I really hacked what I thought I was hacking -- I did try it alone once, which wasn't enough to reliably power the external hub) Since this doesn't seem to be in the RELENG_4 branch, or else I've really botched my cvs tags, and the commit comment mentions that it afflicts some OHCI controllers, I wonder if I have an even buggier chip. Nonetheless, I've apparently managed to make it work, somehow, after boot, in spite of the overcurrent. During boot (or when auto-loaded at boot by usbd), though, it seems to hang with a timeout during the port reset. I need to make more sense of my hacks... More hacking has allowed me to also sometimes power it up at boot, although with a painful delay, unlike my after-boot hack which powers it on cleanly. > Either your hubs really use more power then it is allowed to or you I wondered, but there were several things that made me suspicious that this was not the case. Then, some other things make me suspect that it could be the case too: = favoring the idea that the hub does not take too much power: * the external hub works without any problems with a built-in UHCI USB, * it also works fine with a different UHCI PCI card, * I can connect an external power supply to the hub, also with current- drawing devices attached to the USB ports, then disconnect this power supply after everything is detected and the bus-power takes over with no overcurrent problems, * my hacks of repeatedly applying power a few times are enough to power up the external hub, also with bus-powered devices attached... = favoring the idea that the hub does take too much power: * connecting a bus-powered USB mouse dongle to this same card does not trigger any overcurrent warnings. (I have no other USB devices now) Does `usbctl' or any similar utility give the aktuell current being supplied on a particular port? All I see is for the internal OHCI hub, (some snippage) iManufacturer=1(NEC) iProduct=2(OHCI root hub) iSerialNumber=0() bNumConfigurations=1 CONFIGURATION descriptor 0: bLength=9 bDescriptorType=config(2) wTotalLength=25 bNumInterface=1 bConfigurationValue=1 iConfiguration=0() bmAttributes=40 bMaxPower=0 mA HUB descriptor: bDescLength=10 bDescriptorType=41 bNbrPorts=2 wHubCharacteristics=00 bPwrOn2PwrGood=255 bHubContrCurrent=0 DeviceRemovable=0 and for the external (Cypress) hub, bDeviceProtocol=0 bMaxPacketSize=64 idVendor=0x04b4 idProduct=0x6560 bcdDevice=7 iManufacturer=0() iProduct=0() iSerialNumber=0() bNumConfigurations=1 CONFIGURATION descriptor 0: bLength=9 bDescriptorType=config(2) wTotalLength=25 bNumInterface=1 bConfigurationValue=1 iConfiguration=0() bmAttributes=e0 bMaxPower=100 mA HUB descriptor: bDescLength=9 bDescriptorType=41 bNbrPorts=4 wHubCharacteristics=89 bPwrOn2PwrGood=50 bHubContrCurrent=100 DeviceRemovable=0 This is comparable to the mouse dongle bMaxPower=100 mA so I'm sure I'm not seeing the actual current the device is sucking down. Another Interesting Thing is that `usbdevs' reports this external hub always as self-powered, even when it takes its power from the bus... port 1 addr 2: self powered, config 1, product 0x6560(0x6560), Cypress Semicond uctor(0x04b4), rev 0.07 If that makes any difference. > have a broken controller card. This is possible, for it was in a opened package marked a few Euro less than normal, and I figured I'd take a chance, what with some 95% of the junk I pick up at a discount or being discarded working fine for me, and someone might have only been dissatisfied with it (or had an IRQ problem, as I seemed to have earlier). I'll either keep my present hacks, and continue to hack on the at-boot case to see if I can arrive at a clean power-on, or keep the external hub attached to its power supply cord, or try yet another card, or some combination of the above, or something different. Or maybe even cut open a USB cable to measure the actual current inline... Thanks, Barry Bouwsma From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 4 21:08:46 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1932816A4CE for ; Tue, 4 Nov 2003 21:08:46 -0800 (PST) Received: from relay.pair.com (relay.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 8095E43FA3 for ; Tue, 4 Nov 2003 21:08:44 -0800 (PST) (envelope-from silby@silby.com) Received: (qmail 83813 invoked from network); 5 Nov 2003 05:08:42 -0000 Received: from niwun.pair.com (HELO localhost) (209.68.2.70) by relay.pair.com with SMTP; 5 Nov 2003 05:08:42 -0000 X-pair-Authenticated: 209.68.2.70 Date: Tue, 4 Nov 2003 23:08:38 -0600 (CST) From: Mike Silbersack To: Vivek Pai In-Reply-To: <3FA7EF77.5010808@cs.princeton.edu> Message-ID: <20031104221455.I9997@odysseus.silby.com> References: <1066789354.21430.39.camel@boxster.onthenet.com.au> <20031022082953.GA69506@rot13.obsecurity.org> <1066816287.25609.34.camel@boxster.onthenet.com.au> <20031022095754.GA70026@rot13.obsecurity.org> <1067183332.3f9bece4c0cf4@webmail.cs.princeton.edu> <3FA2C43E.3030204@cs.princeton.edu> <3FA7EF77.5010808@cs.princeton.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hackers@freebsd.org cc: Alan Cox Subject: Re: Update: Debox sendfile modifications X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Nov 2003 05:08:46 -0000 On Tue, 4 Nov 2003, Vivek Pai wrote: > The one other aspect of this is that sf_bufs mappings are maintained for > a configurable amount of time, reducing the number of TLB ops. You can > specify the parameter for how long, ranging from -1 (no coalescing at > all), 0 (coalesce, but free immediately after last holder release), to > any other time. Obviously, any value above 0 will increase the amount of > wired memory at any given point in time, but it's configurable. Ah, I missed that point. Did your testing show the caching part of the functionality to be significant? > There are two problems to this approach that I see > a) you'd have to return a value back to sendfile while this async > operation is in progress, because you don't have any other > non-intrusive way of giving back the return value at any other time > b) once that small number of kernel threads gets exhausted, you lose > the opportunity to serve requests out of main memory > > part (a) means that this change can't be made completely without > application re-coding, and part (b) means that more sophisticated > applications could lose performance. > > How about something that lets you choose what happens - we've got a > flag field anyway, so why not have options to control the behavior on > missing pages? Applications like Flash might just want the error > message so that they can handle it themselves, while other applications > may be happy with the default that you're suggesting. > > -Vivek Yeah, I guess you're right; as John-Mark Gurney also pointed out, it would be extremely difficult to hide the asychronous implementation. Assuming that we came up with an extra flag which told sendfile to use asynchronous mode (and raised the maximum number of such threads), wouldn't it be even more efficient than Flash's helper threads? Mike "Silby" Silbersack From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 4 22:25:48 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3833616A4CE for ; Tue, 4 Nov 2003 22:25:48 -0800 (PST) Received: from bluebox.CS.Princeton.EDU (bluebox.CS.Princeton.EDU [128.112.136.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1432543FCB for ; Tue, 4 Nov 2003 22:25:47 -0800 (PST) (envelope-from vivek@CS.Princeton.EDU) Received: from cs.princeton.edu (oakley [128.112.139.27]) (authenticated bits=0)hA56PhNt005171 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 5 Nov 2003 01:25:44 -0500 (EST) Message-ID: <3FA897E7.5020103@cs.princeton.edu> Date: Wed, 05 Nov 2003 01:25:43 -0500 From: Vivek Pai User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.0.1) Gecko/20020920 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mike Silbersack References: <1066789354.21430.39.camel@boxster.onthenet.com.au> <20031022082953.GA69506@rot13.obsecurity.org> <1066816287.25609.34.camel@boxster.onthenet.com.au> <20031022095754.GA70026@rot13.obsecurity.org> <1067183332.3f9bece4c0cf4@webmail.cs.princeton.edu> <3FA2C43E.3030204@cs.princeton.edu> <3FA7EF77.5010808@cs.princeton.edu> <20031104221455.I9997@odysseus.silby.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-hackers@freebsd.org cc: Alan Cox Subject: Re: Update: Debox sendfile modifications X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Nov 2003 06:25:48 -0000 Mike Silbersack wrote: > On Tue, 4 Nov 2003, Vivek Pai wrote: >>The one other aspect of this is that sf_bufs mappings are maintained for >>a configurable amount of time, reducing the number of TLB ops. You can >>specify the parameter for how long, ranging from -1 (no coalescing at >>all), 0 (coalesce, but free immediately after last holder release), to >>any other time. Obviously, any value above 0 will increase the amount of >>wired memory at any given point in time, but it's configurable. > > Ah, I missed that point. Did your testing show the caching part of the > functionality to be significant? I think it buys us a small gain (a few percent) under static-content workloads, and a little less under SpecWeb99, where more time is spent in dynamic content. However, it's almost free - the additional complexity beyond just coalescing is hooking into the timer to free unused mappings. >>How about something that lets you choose what happens - we've got a >>flag field anyway, so why not have options to control the behavior on >>missing pages? Applications like Flash might just want the error >>message so that they can handle it themselves, while other applications >>may be happy with the default that you're suggesting. > > > Yeah, I guess you're right; as John-Mark Gurney also pointed out, it would > be extremely difficult to hide the asychronous implementation. Assuming > that we came up with an extra flag which told sendfile to use asynchronous > mode (and raised the maximum number of such threads), wouldn't it be even > more efficient than Flash's helper threads? We use the helper processes for mostly historical portability reasons, and if we wanted to really customize Flash for FreeBSD, we'd issue some async disk ops and get their completion status via kevent. So, it's just a tradeoff of where the additional complexity goes - kernel or application. I don't know that we'll be breaking away from our helper approach just yet, mostly because we're still interested in some level of portability. If you were to have sendfile issue the disk reads, how would you signal completion? I guess one approach is to make the socket buffer appear to have no space while the sendfile-initiated read is in progress, but it seems to me that such an approach would be considered too ugly. It would cause the least modification to applications, because otherwise apps need to disable interest on the socket having space, and re-enable it after getting notified that the sendfile-initiated read (and transfer) completed. Am I missing something? -Vivek From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 5 00:09:44 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3D7A716A4CE for ; Wed, 5 Nov 2003 00:09:44 -0800 (PST) Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id AEA1F44005 for ; Wed, 5 Nov 2003 00:09:42 -0800 (PST) (envelope-from alc@cs.rice.edu) Received: from localhost (localhost [127.0.0.1]) by cs.rice.edu (Postfix) with ESMTP id CCADD4AA56; Wed, 5 Nov 2003 02:09:41 -0600 (CST) Received: from cs.rice.edu ([127.0.0.1]) by localhost (cs.rice.edu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 10033-01-91; Wed, 5 Nov 2003 02:09:37 -0600 (CST) Received: by cs.rice.edu (Postfix, from userid 19572) id C70154AA89; Wed, 5 Nov 2003 02:09:37 -0600 (CST) Date: Wed, 5 Nov 2003 02:09:37 -0600 From: Alan Cox To: Vivek Pai Message-ID: <20031105080937.GA9687@cs.rice.edu> References: <1066789354.21430.39.camel@boxster.onthenet.com.au> <20031022082953.GA69506@rot13.obsecurity.org> <1066816287.25609.34.camel@boxster.onthenet.com.au> <20031022095754.GA70026@rot13.obsecurity.org> <1067183332.3f9bece4c0cf4@webmail.cs.princeton.edu> <3FA2C43E.3030204@cs.princeton.edu> <3FA7EF77.5010808@cs.princeton.edu> <20031104221455.I9997@odysseus.silby.com> <3FA897E7.5020103@cs.princeton.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3FA897E7.5020103@cs.princeton.edu> User-Agent: Mutt/1.3.28i X-Virus-Scanned: by amavis-20030616-p5 at rice.edu cc: freebsd-hackers@freebsd.org Subject: Re: Update: Debox sendfile modifications X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Nov 2003 08:09:44 -0000 On Wed, Nov 05, 2003 at 01:25:43AM -0500, Vivek Pai wrote: > Mike Silbersack wrote: > >On Tue, 4 Nov 2003, Vivek Pai wrote: > >>The one other aspect of this is that sf_bufs mappings are maintained for > >>a configurable amount of time, reducing the number of TLB ops. You can > >>specify the parameter for how long, ranging from -1 (no coalescing at > >>all), 0 (coalesce, but free immediately after last holder release), to > >>any other time. Obviously, any value above 0 will increase the amount of > >>wired memory at any given point in time, but it's configurable. > > > >Ah, I missed that point. Did your testing show the caching part of the > >functionality to be significant? > > I think it buys us a small gain (a few percent) under static-content > workloads, and a little less under SpecWeb99, where more time is spent > in dynamic content. However, it's almost free - the additional > complexity beyond just coalescing is hooking into the timer to free > unused mappings. I think it's reasonable to expect a more pronounced effect on i386 SMP. In order to maintain TLB coherence, we issue two interprocessor interrupts _per_page_ transmitted by sendfile(2). Alan From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 5 00:29:56 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A79F16A4CE for ; Wed, 5 Nov 2003 00:29:56 -0800 (PST) Received: from relay.pair.com (relay.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id F1D0043FBF for ; Wed, 5 Nov 2003 00:29:54 -0800 (PST) (envelope-from silby@silby.com) Received: (qmail 26229 invoked from network); 5 Nov 2003 08:29:53 -0000 Received: from niwun.pair.com (HELO localhost) (209.68.2.70) by relay.pair.com with SMTP; 5 Nov 2003 08:29:53 -0000 X-pair-Authenticated: 209.68.2.70 Date: Wed, 5 Nov 2003 02:29:47 -0600 (CST) From: Mike Silbersack To: Vivek Pai In-Reply-To: <3FA897E7.5020103@cs.princeton.edu> Message-ID: <20031105022737.J1370@odysseus.silby.com> References: <1066789354.21430.39.camel@boxster.onthenet.com.au> <20031022082953.GA69506@rot13.obsecurity.org> <1066816287.25609.34.camel@boxster.onthenet.com.au> <20031022095754.GA70026@rot13.obsecurity.org> <1067183332.3f9bece4c0cf4@webmail.cs.princeton.edu> <3FA2C43E.3030204@cs.princeton.edu> <3FA7EF77.5010808@cs.princeton.edu> <20031104221455.I9997@odysseus.silby.com> <3FA897E7.5020103@cs.princeton.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hackers@freebsd.org cc: Alan Cox Subject: Re: Update: Debox sendfile modifications X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Nov 2003 08:29:56 -0000 On Wed, 5 Nov 2003, Vivek Pai wrote: > If you were to have sendfile issue the disk reads, how would you signal > completion? I guess one approach is to make the socket buffer appear to > have no space while the sendfile-initiated read is in progress, but > it seems to me that such an approach would be considered too ugly. It > would cause the least modification to applications, because otherwise > apps need to disable interest on the socket having space, and re-enable > it after getting notified that the sendfile-initiated read (and > transfer) completed. Am I missing something? > > -Vivek I'm not quite certain how I would do it yet. At this point in time I'm just brainstorming. I have some other things I'd like to work on in the next few weeks, I'll sit down and think about this more in late November / early December if I'm still in the right mindset. Mike "Silby" Silbersack From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 5 01:31:25 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8894016A4CE for ; Wed, 5 Nov 2003 01:31:25 -0800 (PST) Received: from park.rambler.ru (park.rambler.ru [81.19.64.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF64D43FEC for ; Wed, 5 Nov 2003 01:31:23 -0800 (PST) (envelope-from is@rambler-co.ru) Received: from is.park.rambler.ru (is.park.rambler.ru [81.19.64.102]) by park.rambler.ru (8.12.6/8.12.6) with ESMTP id hA59VEJ6095448; Wed, 5 Nov 2003 12:31:14 +0300 (MSK) (envelope-from is@rambler-co.ru) Date: Wed, 5 Nov 2003 12:31:14 +0300 (MSK) From: Igor Sysoev X-Sender: is@is.park.rambler.ru To: Mike Silbersack In-Reply-To: <20031105022737.J1370@odysseus.silby.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hackers@freebsd.org cc: Vivek Pai cc: Alan Cox Subject: Re: Update: Debox sendfile modifications X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Nov 2003 09:31:25 -0000 On Wed, 5 Nov 2003, Mike Silbersack wrote: > On Wed, 5 Nov 2003, Vivek Pai wrote: > > > If you were to have sendfile issue the disk reads, how would you signal > > completion? I guess one approach is to make the socket buffer appear to > > have no space while the sendfile-initiated read is in progress, but > > it seems to me that such an approach would be considered too ugly. It > > would cause the least modification to applications, because otherwise > > apps need to disable interest on the socket having space, and re-enable > > it after getting notified that the sendfile-initiated read (and > > transfer) completed. Am I missing something? > > > > -Vivek > > I'm not quite certain how I would do it yet. At this point in time I'm > just brainstorming. I have some other things I'd like to work on in the > next few weeks, I'll sit down and think about this more in late November / > early December if I'm still in the right mindset. I think it can done in the following way - a socket should have flag that says that sendfile() had started the reading a page. select()/poll()/kevent() should check this flag before the checking a socket buffer space. When the page had been read this flag is reset. If there was error while a reading a page then second flag should be set and the first one should be reset. sendfile() should check the error flag before processing. If it set then sendfile() should do a blocking read() to learn errno. I think that this blocking read() would not occur under normal conditions and would not decrease perfomance. And if we have file errors we should think not about perfomance but about correctness of a whole server. I think it would be transparent to the existent user applications that uses select()/etc. As to worker kthreads I think it's better to queue aio operation as it was made in src/sys/kern/vfs_aio.c:aio_qphysio(). Igor Sysoev http://sysoev.ru/en/ From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 5 07:30:23 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BDE9916A4CE for ; Wed, 5 Nov 2003 07:30:23 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id C6BF243FEC for ; Wed, 5 Nov 2003 07:30:22 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.9p2/8.12.9) with ESMTP id hA5FSiMg084268; Wed, 5 Nov 2003 10:28:44 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)hA5FSccp084261; Wed, 5 Nov 2003 10:28:44 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Wed, 5 Nov 2003 10:28:38 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Igor Sysoev In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hackers@freebsd.org cc: Vivek Pai cc: Alan Cox Subject: Re: Update: Debox sendfile modifications X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Nov 2003 15:30:23 -0000 On Wed, 5 Nov 2003, Igor Sysoev wrote: > As to worker kthreads I think it's better to queue aio operation as it > was made in src/sys/kern/vfs_aio.c:aio_qphysio(). One of the things that worries me about the proposal to use kernel worker threads to perform the I/O is that this can place a fairly low upper bound on effective parallelism, unless the kernel threads themselves can issue the I/O's asynchronously. In the network stack itself, we are event and queue driven without blocking--if we can maintain the apparent semantics to the application, it would be very nice to be able to handle that at the socket layer itself. I.e., not waste a thread + stack per "in-progress" operation, and instead have a worker or two that simply propel operations up and down the stack (similar to geom_up and geom_down). Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 5 07:54:17 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4DB8C16A4CE; Wed, 5 Nov 2003 07:54:17 -0800 (PST) Received: from park.rambler.ru (park.rambler.ru [81.19.64.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B73143FF7; Wed, 5 Nov 2003 07:54:15 -0800 (PST) (envelope-from is@rambler-co.ru) Received: from is.park.rambler.ru (is.park.rambler.ru [81.19.64.102]) by park.rambler.ru (8.12.6/8.12.6) with ESMTP id hA5Fs4J6007014; Wed, 5 Nov 2003 18:54:04 +0300 (MSK) (envelope-from is@rambler-co.ru) Date: Wed, 5 Nov 2003 18:54:04 +0300 (MSK) From: Igor Sysoev X-Sender: is@is.park.rambler.ru To: Robert Watson In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hackers@freebsd.org cc: Vivek Pai cc: Alan Cox Subject: Re: Update: Debox sendfile modifications X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Nov 2003 15:54:17 -0000 On Wed, 5 Nov 2003, Robert Watson wrote: > On Wed, 5 Nov 2003, Igor Sysoev wrote: > > > As to worker kthreads I think it's better to queue aio operation as it > > was made in src/sys/kern/vfs_aio.c:aio_qphysio(). > > One of the things that worries me about the proposal to use kernel worker > threads to perform the I/O is that this can place a fairly low upper bound > on effective parallelism, unless the kernel threads themselves can issue > the I/O's asynchronously. In the network stack itself, we are event and > queue driven without blocking--if we can maintain the apparent semantics > to the application, it would be very nice to be able to handle that at the > socket layer itself. I.e., not waste a thread + stack per "in-progress" > operation, and instead have a worker or two that simply propel operations > up and down the stack (similar to geom_up and geom_down). As far as I understand src/sys/kern/vfs_aio.c:aio_qphysio() (that handles AIO on raw disks) does not use kthreads and simply queues operations. Igor Sysoev http://sysoev.ru/en/ From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 5 08:40:55 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C13B116A4CF for ; Wed, 5 Nov 2003 08:40:55 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 818B043F93 for ; Wed, 5 Nov 2003 08:40:54 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.9p2/8.12.9) with ESMTP id hA5GdKMg085496; Wed, 5 Nov 2003 11:39:20 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)hA5GdJ1E085493; Wed, 5 Nov 2003 11:39:20 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Wed, 5 Nov 2003 11:39:19 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Igor Sysoev In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hackers@freebsd.org cc: Vivek Pai cc: Alan Cox Subject: Re: Update: Debox sendfile modifications X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Nov 2003 16:40:55 -0000 On Wed, 5 Nov 2003, Igor Sysoev wrote: > On Wed, 5 Nov 2003, Robert Watson wrote: > > > On Wed, 5 Nov 2003, Igor Sysoev wrote: > > > > > As to worker kthreads I think it's better to queue aio operation as it > > > was made in src/sys/kern/vfs_aio.c:aio_qphysio(). > > > > One of the things that worries me about the proposal to use kernel worker > > threads to perform the I/O is that this can place a fairly low upper bound > > on effective parallelism, unless the kernel threads themselves can issue > > the I/O's asynchronously. In the network stack itself, we are event and > > queue driven without blocking--if we can maintain the apparent semantics > > to the application, it would be very nice to be able to handle that at the > > socket layer itself. I.e., not waste a thread + stack per "in-progress" > > operation, and instead have a worker or two that simply propel operations > > up and down the stack (similar to geom_up and geom_down). > > As far as I understand src/sys/kern/vfs_aio.c:aio_qphysio() (that > handles AIO on raw disks) does not use kthreads and simply queues > operations. I think it sounds like we're actually agreeing with each other. Currently, AIO does use threads for non-character devices, so in the socket case it will be using a worker thread. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 5 09:01:25 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D34E116A4CE; Wed, 5 Nov 2003 09:01:25 -0800 (PST) Received: from park.rambler.ru (park.rambler.ru [81.19.64.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA58B43FFD; Wed, 5 Nov 2003 09:01:23 -0800 (PST) (envelope-from is@rambler-co.ru) Received: from is.park.rambler.ru (is.park.rambler.ru [81.19.64.102]) by park.rambler.ru (8.12.6/8.12.6) with ESMTP id hA5H1CJ6008893; Wed, 5 Nov 2003 20:01:12 +0300 (MSK) (envelope-from is@rambler-co.ru) Date: Wed, 5 Nov 2003 20:01:11 +0300 (MSK) From: Igor Sysoev X-Sender: is@is.park.rambler.ru To: Robert Watson In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hackers@freebsd.org cc: Vivek Pai cc: Alan Cox Subject: Re: Update: Debox sendfile modifications X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Nov 2003 17:01:26 -0000 On Wed, 5 Nov 2003, Robert Watson wrote: > On Wed, 5 Nov 2003, Igor Sysoev wrote: > > > On Wed, 5 Nov 2003, Robert Watson wrote: > > > > > On Wed, 5 Nov 2003, Igor Sysoev wrote: > > > > > > > As to worker kthreads I think it's better to queue aio operation as it > > > > was made in src/sys/kern/vfs_aio.c:aio_qphysio(). > > > > > > One of the things that worries me about the proposal to use kernel worker > > > threads to perform the I/O is that this can place a fairly low upper bound > > > on effective parallelism, unless the kernel threads themselves can issue > > > the I/O's asynchronously. In the network stack itself, we are event and > > > queue driven without blocking--if we can maintain the apparent semantics > > > to the application, it would be very nice to be able to handle that at the > > > socket layer itself. I.e., not waste a thread + stack per "in-progress" > > > operation, and instead have a worker or two that simply propel operations > > > up and down the stack (similar to geom_up and geom_down). > > > > As far as I understand src/sys/kern/vfs_aio.c:aio_qphysio() (that > > handles AIO on raw disks) does not use kthreads and simply queues > > operations. > > I think it sounds like we're actually agreeing with each other. Yes. > Currently, AIO does use threads for non-character devices, so in the > socket case it will be using a worker thread. Yes, current AIO implementation uses worker threads for regular files. But I suggest not to use AIO code for sendfile() to read a file page. I suggest to use BUF_STRATEGY() like aio_qphysio() does. Is it possible to read a regular file page using BUF_STRATEGY() ? Igor Sysoev http://sysoev.ru/en/ From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 5 10:30:39 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2451C16A4CE for ; Wed, 5 Nov 2003 10:30:39 -0800 (PST) Received: from smtp-relay1.barrysworld.com (ns1.barrysworld.com [213.221.172.238]) by mx1.FreeBSD.org (Postfix) with ESMTP id 02B9B43F75 for ; Wed, 5 Nov 2003 10:30:38 -0800 (PST) (envelope-from killing@barrysworld.com) Received: from [213.221.181.50] (helo=barrysworld.com) by smtp-relay1.barrysworld.com with esmtp (Exim 4.24) id 1AHSPg-0008FA-9n for freebsd-hackers@freebsd.org; Wed, 05 Nov 2003 18:29:52 +0000 Received: from vader [212.135.219.179] by barrysworld.com with ESMTP (SMTPD32-7.15) id A1B12F19008E; Wed, 05 Nov 2003 18:30:09 +0000 Message-ID: <01d501c3a3ca$caa925b0$b3db87d4@multiplay.co.uk> From: "Steven Hartland" To: References: Date: Wed, 5 Nov 2003 18:29:45 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Subject: 5.1-CURRENT (today), ath(4) + Dlink DWL-AG650 = no joy X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Steven Hartland List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Nov 2003 18:30:39 -0000 Is anyone using this atm. Just got the card today as it was in the hardware compat list for the ath driver but I not having any joy with it. On insert or boot it identifies as: ath0: ... ... . But when using ifconfig I get: No support for the 5112 yet! ath0: unable to reset hardware; hal status 3 Any ideas? Steve From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 5 12:07:53 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1F35E16A4CF; Wed, 5 Nov 2003 12:07:53 -0800 (PST) Received: from frost.ath.cx (BSN-95-242-77.dsl.siol.net [193.95.242.77]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F44543FBF; Wed, 5 Nov 2003 12:07:51 -0800 (PST) (envelope-from bfg@noviforum.si) Received: from noviforum.si (mordor.lucky.si [192.168.200.250]) by frost.ath.cx (ESMTP) with ESMTP id 3BB3278; Wed, 5 Nov 2003 21:07:48 +0100 (CET) Message-ID: <3FA95893.1060208@noviforum.si> Date: Wed, 05 Nov 2003 21:07:47 +0100 From: =?ISO-8859-1?Q?=22Branko_F=2E_Grac=28nar=22?= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031013 Thunderbird/0.3 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mike Silbersack References: <3F9F9884.3020309@noviforum.si> <20031030050540.GA25906@rot13.obsecurity.org> <20031103140413.GG18358@pixies.tirloni.org> <3FA667F4.7060003@noviforum.si> <20031103230152.F99573@odysseus.silby.com> In-Reply-To: <20031103230152.F99573@odysseus.silby.com> X-Enigmail-Version: 0.81.7.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-hackers@freebsd.org cc: freebsd-current@freebsd.org cc: "Giovanni P. Tirloni" Subject: Re: FreeBSD 5.1-p10 reproducible crash with Apache2 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Nov 2003 20:07:53 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mike Silbersack wrote: | Can you try updating to 5.1-current and see if the situation changes at | all? A lot has changed since 5.1-release. If it's still broken in | 5.1-current, we can take a look into it. | | Thanks, I tried today with yesterday's -CURRENT. Same symptoms. No kernel panic, just lockup. Brane -----BEGIN PGP SIGNATURE----- iD8DBQE/qViTfiC/E+t8hPcRAs5BAJ4po+J7FpIkPHtYjypSI1BeC3snugCfbfJa o7jO2699XTtnauPrjNxGOd8= =qdph -----END PGP SIGNATURE----- From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 5 22:52:56 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 513FF16A4CF for ; Wed, 5 Nov 2003 22:52:56 -0800 (PST) Received: from relay.pair.com (relay.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 1243E43FAF for ; Wed, 5 Nov 2003 22:52:54 -0800 (PST) (envelope-from silby@silby.com) Received: (qmail 63835 invoked from network); 6 Nov 2003 06:52:52 -0000 Received: from niwun.pair.com (HELO localhost) (209.68.2.70) by relay.pair.com with SMTP; 6 Nov 2003 06:52:52 -0000 X-pair-Authenticated: 209.68.2.70 Date: Thu, 6 Nov 2003 00:52:46 -0600 (CST) From: Mike Silbersack To: =?ISO-8859-1?Q?=22Branko_F=2E_Grac=28nar=22?= In-Reply-To: <3FA95893.1060208@noviforum.si> Message-ID: <20031106005009.D1561@odysseus.silby.com> References: <3F9F9884.3020309@noviforum.si> <20031030050540.GA25906@rot13.obsecurity.org> <3FA667F4.7060003@noviforum.si><3FA95893.1060208@noviforum.si> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hackers@freebsd.org cc: freebsd-current@freebsd.org cc: "Giovanni P. Tirloni" Subject: Re: FreeBSD 5.1-p10 reproducible crash with Apache2 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Nov 2003 06:52:56 -0000 On Wed, 5 Nov 2003, [ISO-8859-1] "Branko F. Grac(nar" wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Mike Silbersack wrote: > > | Can you try updating to 5.1-current and see if the situation changes at > | all? A lot has changed since 5.1-release. If it's still broken in > | 5.1-current, we can take a look into it. > | > | Thanks, > > I tried today with yesterday's -CURRENT. Same symptoms. No kernel panic, > just lockup. > > Brane Ok, submit a PR with clear details on how to recreate the problem, and we'll see if someone can take a look into it. I'm too busy to look at it, but at least putting it in a PR will ensure that it doesn't get too lost. Once the PR is filed, you might want to try asking on the freebsd-threads list; it sounds like the issue might be thread-related. (Note that your original e-mail might contain enough detail, I'm not certain; I just skimmed it. Filing a good PR is important either way, mailing list messages get easily lost.) Thanks, Mike "Silby" Silbersack From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 6 02:31:51 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0EC4A16A4CE for ; Thu, 6 Nov 2003 02:31:51 -0800 (PST) Received: from park.rambler.ru (park.rambler.ru [81.19.64.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C60743FDD for ; Thu, 6 Nov 2003 02:31:49 -0800 (PST) (envelope-from is@rambler-co.ru) Received: from is.park.rambler.ru (is.park.rambler.ru [81.19.64.102]) by park.rambler.ru (8.12.6/8.12.6) with ESMTP id hA6AVcJ6029458; Thu, 6 Nov 2003 13:31:38 +0300 (MSK) (envelope-from is@rambler-co.ru) Date: Thu, 6 Nov 2003 13:31:38 +0300 (MSK) From: Igor Sysoev X-Sender: is@is.park.rambler.ru To: Mike Silbersack In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hackers@freebsd.org cc: Vivek Pai cc: Alan Cox Subject: Re: Update: Debox sendfile modifications X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Nov 2003 10:31:51 -0000 On Wed, 5 Nov 2003, Igor Sysoev wrote: > On Wed, 5 Nov 2003, Mike Silbersack wrote: > > > On Wed, 5 Nov 2003, Vivek Pai wrote: > > > > > If you were to have sendfile issue the disk reads, how would you signal > > > completion? I guess one approach is to make the socket buffer appear to > > > have no space while the sendfile-initiated read is in progress, but > > > it seems to me that such an approach would be considered too ugly. It > > > would cause the least modification to applications, because otherwise > > > apps need to disable interest on the socket having space, and re-enable > > > it after getting notified that the sendfile-initiated read (and > > > transfer) completed. Am I missing something? > > > > > > -Vivek > > > > I'm not quite certain how I would do it yet. At this point in time I'm > > just brainstorming. I have some other things I'd like to work on in the > > next few weeks, I'll sit down and think about this more in late November / > > early December if I'm still in the right mindset. > > I think it can done in the following way - a socket should have flag > that says that sendfile() had started the reading a page. > select()/poll()/kevent() should check this flag before the checking > a socket buffer space. When the page had been read this flag is reset. > If there was error while a reading a page then second flag should be set and > the first one should be reset. sendfile() should check the error flag > before processing. If it set then sendfile() should do a blocking read() > to learn errno. I think that this blocking read() would not occur under > normal conditions and would not decrease perfomance. And if we have file > errors we should think not about perfomance but about correctness of a whole > server. > > I think it would be transparent to the existent user applications > that uses select()/etc. Here is more clear (I hope) description of the above method. Each socket buffer has two flags - SB_SFBUSY and SB_SFERR. When sendfile() needs to read a file page it sets SB_SFBUSY in so->so_snd.sb_flags and initiates the reading by starting kthread (probably easy to program but non-optimal method) or by queueing async disk operation. Then sendfile() returns EWOULDBLOCK. An application calls select()/poll()/kevent() to learn when the socket would be ready to write. select()/etc sees SB_SFBUSY set and decides that the socket is not ready. I think it's correct behaviour because I do not think that there is an application that wants to writev() after sendfile() returns EWOULDBLOCK. When a reading has completed kthread or aio completion procedure clear SB_SFBUSY flags. If there was an error while a reading then it sets SB_SFERR. And then it calls wakeup. select()/etc sees that SB_SFBUSY is clear, checks the buffer space and reports readiness to an application. An application calls sendfile() again. If sendfile() sees the SB_SFERR it does a blocking read to learn error code. Although we can save the error code before but I do not see a place where to save it. It certainly should not be an addition to the socket structures because it increases their size. Or we can save it to so->so_error (I think it would be rather EIO so it can not be mixed with other socket errors). Then kevent() can report about it and sendfile() can see it too. In this case we do not need SB_SFERR flag. Igor Sysoev http://sysoev/ru/en/ From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 6 03:52:08 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6356716A4CE; Thu, 6 Nov 2003 03:52:08 -0800 (PST) Received: from frost.ath.cx (BSN-95-242-77.dsl.siol.net [193.95.242.77]) by mx1.FreeBSD.org (Postfix) with ESMTP id 951A643FE5; Thu, 6 Nov 2003 03:52:06 -0800 (PST) (envelope-from bfg@noviforum.si) Received: from noviforum.si (mordor.lucky.si [192.168.200.250]) by frost.ath.cx (ESMTP) with ESMTP id E53677B; Thu, 6 Nov 2003 12:52:01 +0100 (CET) Message-ID: <3FAA35E2.1090703@noviforum.si> Date: Thu, 06 Nov 2003 12:52:02 +0100 From: =?ISO-8859-1?Q?=22Branko_F=2E_Grac=28nar=22?= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031013 Thunderbird/0.3 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mike Silbersack References: <3F9F9884.3020309@noviforum.si> <20031030050540.GA25906@rot13.obsecurity.org> <20031103140413.GG18358@pixies.tirloni.org> <3FA667F4.7060003@noviforum.si> <20031103230152.F99573@odysseus.silby.com> <3FA95893.1060208@noviforum.si> <20031106005009.D1561@odysseus.silby.com> In-Reply-To: <20031106005009.D1561@odysseus.silby.com> X-Enigmail-Version: 0.81.7.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-hackers@freebsd.org cc: freebsd-current@freebsd.org cc: "Giovanni P. Tirloni" cc: freebsd-threads@freebsd.org Subject: Re: FreeBSD 5.1-p10 reproducible crash with Apache2 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Nov 2003 11:52:08 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mike Silbersack wrote: | On Wed, 5 Nov 2003, [ISO-8859-1] "Branko F. Grac(nar" wrote: | | |>-----BEGIN PGP SIGNED MESSAGE----- |>Hash: SHA1 |> |>Mike Silbersack wrote: |> |>| Can you try updating to 5.1-current and see if the situation changes at |>| all? A lot has changed since 5.1-release. If it's still broken in |>| 5.1-current, we can take a look into it. |>| |>| Thanks, |> |>I tried today with yesterday's -CURRENT. Same symptoms. No kernel panic, |>just lockup. |> |>Brane | | | Ok, submit a PR with clear details on how to recreate the problem, and | we'll see if someone can take a look into it. I'm too busy to look at it, | but at least putting it in a PR will ensure that it doesn't get too lost. | Once the PR is filed, you might want to try asking on the freebsd-threads | list; it sounds like the issue might be thread-related. | | (Note that your original e-mail might contain enough detail, I'm not | certain; I just skimmed it. Filing a good PR is important either way, | mailing list messages get easily lost.) | Thanks. I already sent pr at 29.10.2003, which is identified by id 'kern/58677'. PR can be viewed at the following url address: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/58677 I think, that this really serious issue, concerning operating system stability. best regards, Brane -----BEGIN PGP SIGNATURE----- iD8DBQE/qjXifiC/E+t8hPcRAlUUAJ9PsqYXoh6lty2USRISPRyilOJIxwCcCyLr J//Y0OU7K0ODV4n99sMPfzE= =LByr -----END PGP SIGNATURE----- From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 6 04:24:34 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7B54816A4CE for ; Thu, 6 Nov 2003 04:24:34 -0800 (PST) Received: from brolloks.trispen.com (brolloks.trispen.com [196.7.146.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 26DE643FBD for ; Thu, 6 Nov 2003 04:24:32 -0800 (PST) (envelope-from jacques@trispen.com) Received: from localhost (unknown [127.0.0.1]) by brolloks.trispen.com (Postfix) with ESMTP id 2B3B322E45 for ; Thu, 6 Nov 2003 12:24:27 +0000 (GMT) Received: from brolloks.trispen.com ([127.0.0.1]) by localhost (brolloks [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 99346-09 for ; Thu, 6 Nov 2003 14:24:19 +0200 (SAST) Received: by brolloks.trispen.com (Postfix, from userid 1000) id 2FFA822E44; Thu, 6 Nov 2003 14:24:17 +0200 (SAST) Date: Thu, 6 Nov 2003 14:24:16 +0200 From: Jacques Fourie To: freebsd-hackers@freebsd.org Message-ID: <20031106142416.A99843@trispen.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Subject: ar interface issues X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jf@trispen.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Nov 2003 12:24:34 -0000 Hi, I'm using a Digi SYNC/570i-PCI 2 port adapter on a system running FreeBSD 4.9-RELEASE as one end of a point-to-point link. If I change between ports on the adapter, I need to reboot the FreeBSD box to get everything working. Here is the sequence of events that leads to this scenario : 1.) ifconfig ar0 10.0.0.1 10.0.0.2 netmask 255.255.255.252 link2 2.) ping 10.0.0.2 - OK 3.) ifconfig ar0 down 4.) ifconfig ar0 delete 5.) swap cable to ar1 6.) ifconfig ar1 10.0.0.1 10.0.0.2 netmask 255.255.255.252 link2 7.) ping 10.0.0.2 - not OK, reboot required. I've also noticed a lot of 'ar1: transmit failed, ST0 0, ST1 50, ST3 f, DSR3 3.' after step 6 above. After a reboot ar1 is working but the same happens when I try to switch to ar0. I have also verified that the same condition occurs when using netgraph. Any ideas on how I can go about trying to fix this would be greatly appreciated. regards, jacques From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 6 04:28:53 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB51A16A4CE; Thu, 6 Nov 2003 04:28:53 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 19BEA43FA3; Thu, 6 Nov 2003 04:28:53 -0800 (PST) (envelope-from davidxu@freebsd.org) Received: from freebsd.org (davidxu@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id hA6CSnFY023632; Thu, 6 Nov 2003 04:28:50 -0800 (PST) (envelope-from davidxu@freebsd.org) Message-ID: <3FAA411C.6050209@freebsd.org> Date: Thu, 06 Nov 2003 20:39:56 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20031025 Thunderbird/0.3 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Branko@FreeBSD.org, "F."@FreeBSD.org, Grac@FreeBSD.org References: <3F9F9884.3020309@noviforum.si> <20031030050540.GA25906@rot13.obsecurity.org> <20031103140413.GG18358@pixies.tirloni.org> <3FA667F4.7060003@noviforum.si> <20031103230152.F99573@odysseus.silby.com> <3FA95893.1060208@noviforum.si> <20031106005009.D1561@odysseus.silby.com> <3FAA35E2.1090703@noviforum.si> In-Reply-To: <3FAA35E2.1090703@noviforum.si> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-hackers@freebsd.org cc: freebsd-current@freebsd.org cc: "Giovanni P. Tirloni" cc: freebsd-threads@freebsd.org Subject: Re: FreeBSD 5.1-p10 reproducible crash with Apache2 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Nov 2003 12:28:54 -0000 Branko F. Grac(nar wrote: > > Thanks. I already sent pr at 29.10.2003, which is identified by id > 'kern/58677'. > > PR can be viewed at the following url address: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/58677 > > I think, that this really serious issue, concerning operating system > stability. > > best regards, Brane > > Please tell us your Apache configuration, are you using prefork or worker or perchild mode ? If you are using worker mode, which thread library are you using ? this would help us to narrow down problem scope. --- David Xu From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 6 05:19:24 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 70D0E16A4CE for ; Thu, 6 Nov 2003 05:19:24 -0800 (PST) Received: from c1-2-6.rz.ruhr-uni-bochum.de (c1-2-6.rz.ruhr-uni-bochum.de [134.147.32.86]) by mx1.FreeBSD.org (Postfix) with SMTP id 28D0C43FE5 for ; Thu, 6 Nov 2003 05:19:22 -0800 (PST) (envelope-from gandalf@nm.ruhr-uni-bochum.de) Received: (qmail 28674 invoked by uid 82); 6 Nov 2003 13:19:21 -0000 Received: from gandalf@nm.ruhr-uni-bochum.de by c1-2-6.rz.ruhr-uni-bochum.de by uid 80 with qmail-scanner-1.16 (sophie: 2.17/3.75. Clear:. Processed in 0.035838 secs); 06 Nov 2003 13:19:21 -0000 Received: from sunu450.rz.ruhr-uni-bochum.de (134.147.32.69) by c1-2-6.rz.ruhr-uni-bochum.de with SMTP; 6 Nov 2003 13:19:20 -0000 Received: (qmail 7860 invoked from network); 6 Nov 2003 13:19:20 -0000 Received: from server.nm.ruhr-uni-bochum.de (HELO mailhost.nm.ruhr-uni-bochum.de) (134.147.252.40) by sunu450.rz.ruhr-uni-bochum.de with SMTP; 6 Nov 2003 13:19:20 -0000 Received: (qmail 93957 invoked by uid 101); 6 Nov 2003 13:19:18 -0000 Received: from pc-o.nm.ruhr-uni-bochum.de (134.147.252.55) by server.nm.ruhr-uni-bochum.de with SMTP; 6 Nov 2003 13:19:18 -0000 Received: from pc-o.nm.ruhr-uni-bochum.de (localhost [127.0.0.1]) hA6DJIXB059788 for ; Thu, 6 Nov 2003 14:19:18 +0100 (CET) (envelope-from gandalf@pc-o.nm.ruhr-uni-bochum.de) Received: (from gandalf@localhost)hA6DJIGx059787 for freebsd-hackers@freebsd.org; Thu, 6 Nov 2003 14:19:18 +0100 (CET) Date: Thu, 6 Nov 2003 14:19:18 +0100 From: Andre Grosse Bley To: freebsd-hackers@freebsd.org Message-ID: <20031106131918.GA41660@nm.ruhr-uni-bochum.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: 4.9-RELEASE, ACPI and DELL Latitude D600 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Nov 2003 13:19:24 -0000 Hi all, i am trying to install FreeBSD 4.9-RELEASE on a Dell Latitude D600 notebook. "standard" Kernel without ACPI works fine (dmesg at http://www.nm.ruhr-uni-bochum.de/~gandalf/dell/dmesg.noacpi.txt) Since i need the batterystatus (and the Bios doesnt seem to support APM anymore) i activated acpi: The machine paniced after detecting the brgphy0. After removing pcic0/pcic1 from the kernel configuration, i was able to boot with ACPI (wow!;) But no batterystatus. Googling found a solution: http://sandcat.nl/~stijn/freebsd/dell.php I needed to add acpi_dsdt_load="YES" acpi_dsdt_name="/boot/acpi_dsdt.aml" acpi_dsdt_type="acpi_dsdt" to /boot/loader.conf dmesg is at http://www.nm.ruhr-uni-bochum.de/~gandalf/dell/dmesg.acpi.txt sysctl hw.acpi gives: hw.acpi.supported_sleep_state: S1 S3 S4 S5 hw.acpi.power_button_state: S5 hw.acpi.sleep_button_state: S1 hw.acpi.lid_switch_state: S1 hw.acpi.standby_state: S1 hw.acpi.suspend_state: S3 hw.acpi.sleep_delay: 0 hw.acpi.s4bios: 1 hw.acpi.verbose: 1 hw.acpi.disable_on_poweroff: 1 hw.acpi.cpu.max_speed: 8 hw.acpi.cpu.current_speed: 8 hw.acpi.cpu.performance_speed: 8 hw.acpi.cpu.economy_speed: 4 hw.acpi.thermal.min_runtime: 0 hw.acpi.thermal.polling_rate: 30 hw.acpi.thermal.tz0.temperature: 3127 hw.acpi.thermal.tz0.active: -1 hw.acpi.thermal.tz0.thermal_flags: 0 hw.acpi.thermal.tz0._PSV: -1 hw.acpi.thermal.tz0._HOT: -1 hw.acpi.thermal.tz0._CRT: 3752 hw.acpi.thermal.tz0._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.acline: 1 hw.acpi.battery.life: 46 hw.acpi.battery.time: -1 hw.acpi.battery.state: 2 hw.acpi.battery.units: 2 hw.acpi.battery.info_expire: 5 My problem: the machine panics when closing the lid, even after sysctl hw.acpi.lid_switch_state=NONE. Traceback without the sysctl is as follows: root@feap:~ $gdb -k /kernel.debug /var/crash/vmcore.1 IdlePTD at phsyical address 0x00470000 initial pcb at physical address 0x003b04e0 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x70 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01b5198 stack pointer = 0x10:0xc0367b70 frame pointer = 0x10:0xc0367b94 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = net tty bio cam trap number = 12 panic: page fault syncing disks... Fatal trap 12: page fault while in kernel mode fault virtual address = 0x30 fault code = supervisor read, page not present instruction pointer = 0x8:0xc02784d0 stack pointer = 0x10:0xc0367998 frame pointer = 0x10:0xc03679a0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = net tty bio cam trap number = 12 panic: page fault Uptime: 4m6s #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:487 #1 0xc01b20f7 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:316 #2 0xc01b2535 in panic (fmt=0xc035f76c "%s") at /usr/src/sys/kern/kern_shutdown.c:595 #3 0xc02fa003 in trap_fatal (frame=0xc0367958, eva=48) at /usr/src/sys/i386/i386/trap.c:974 #4 0xc02f9cb1 in trap_pfault (frame=0xc0367958, usermode=0, eva=48) at /usr/src/sys/i386/i386/trap.c:867 #5 0xc02f9857 in trap (frame={tf_fs = -1071841264, tf_es = -65520, tf_ds = -1070202864, tf_edi = 0, tf_esi = -1036472064, tf_ebp = -1070171744, tf_isp = -1070171772, tf_ebx = -1070075364, tf_edx = 6866944, tf_ecx = -614904832, tf_eax = 0, tf_trapno = 12, tf_err = 0, tf_eip = -1071151920, tf_cs = 8, tf_eflags = 66182, tf_esp = -1036472064, tf_ss = -1036472064}) at /usr/src/sys/i386/i386/trap.c:466 #6 0xc02784d0 in acquire_lock (lk=0xc037f21c) at /usr/src/sys/ufs/ffs/ffs_softdep.c:266 #7 0xc027c5d0 in softdep_update_inodeblock (ip=0xc238b100, bp=0xcc94a43c, waitfor=0) at /usr/src/sys/ufs/ffs/ffs_softdep.c:3813 #8 0xc0277605 in ffs_update (vp=0xdb594c00, waitfor=0) at /usr/src/sys/ufs/ffs/ffs_inode.c:106 #9 0xc027fa4e in ffs_sync (mp=0xc2318600, waitfor=2, cred=0xc1453680, p=0xc03caf20) at /usr/src/sys/ufs/ffs/ffs_vfsops.c:1025 #10 0xc01e2e7b in sync (p=0xc03caf20, uap=0x0) at /usr/src/sys/kern/vfs_syscalls.c:577 #11 0xc01b1e92 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:235 #12 0xc01b2535 in panic (fmt=0xc035f76c "%s") at /usr/src/sys/kern/kern_shutdown.c:595 #13 0xc02fa003 in trap_fatal (frame=0xc0367b30, eva=112) at /usr/src/sys/i386/i386/trap.c:974 #14 0xc02f9cb1 in trap_pfault (frame=0xc0367b30, usermode=0, eva=112) at /usr/src/sys/i386/i386/trap.c:867 #15 0xc02f9857 in trap (frame={tf_fs = -1070202864, tf_es = -1070465008, tf_ds = -1070465008, tf_edi = 0, tf_esi = -1069882148, tf_ebp = -1070171244, tf_isp = -1070171300, tf_ebx = 0, tf_edx = 0, tf_ecx = 200, tf_eax = 6291968, tf_trapno = 12, tf_err = 0, tf_eip = -1071951464, tf_cs = 8, tf_eflags = 66118, tf_esp = 0, tf_ss = 274877907}) at /usr/src/sys/i386/i386/trap.c:466 #16 0xc01b5198 in tsleep (ident=0xc03ae4dc, priority=0, wmesg=0xc0328583 "acpislp", timo=200) at /usr/src/sys/kern/kern_synch.c:436 #17 0xc017817e in AcpiOsSleep (Seconds=2, Milliseconds=0) at /usr/src/sys/dev/acpica/Osd/OsdSchedule.c:256 #18 0xc0157991 in AcpiExSystemDoSuspend (HowLong=2000) at /usr/src/sys/contrib/dev/acpica/exsystem.c:257 #19 0xc0153b1e in AcpiExOpcode_1A_0T_0R (WalkState=0xc21f4028) at /usr/src/sys/contrib/dev/acpica/exoparg1.c:202 20 0xc0149fc1 in AcpiDsExecEndOp (WalkState=0xc21f4028) at /usr/src/sys/contrib/dev/acpica/dswexec.c:516 #21 0xc015f904 in AcpiPsParseLoop (WalkState=0xc21f4028) at /usr/src/sys/contrib/dev/acpica/psparse.c:977 #22 0xc015fe01 in AcpiPsParseAml (WalkState=0xc24cd828) at /usr/src/sys/contrib/dev/acpica/psparse.c:1258 #23 0xc0160b9e in AcpiPsxExecute (MethodNode=0xc21da4a8, Params=0x0, ReturnObjDesc=0xc0367d94) at /usr/src/sys/contrib/dev/acpica/psxface.c:281 #24 0xc015b407 in AcpiNsExecuteControlMethod (MethodNode=0xc21da4a8, Params=0x0, ReturnObjDesc=0xc0367d94) at /usr/src/sys/contrib/dev/acpica/nseval.c:527 #25 0xc015b2eb in AcpiNsEvaluateByHandle (Handle=0xc21da4a8, Params=0x0, ReturnObject=0x0) at /usr/src/sys/contrib/dev/acpica/nseval.c:409 #26 0xc014c484 in AcpiEvAsynchExecuteGpeMethod (Context=0xc21b326c) at /usr/src/sys/contrib/dev/acpica/evgpe.c:334 #27 0xc01780ef in AcpiOsExecuteQueue (arg=0xc23d6dc0, pending=1) at /usr/src/sys/dev/acpica/Osd/OsdSchedule.c:234 #28 0xc01c0e41 in taskqueue_run (queue=0xc144c600) at /usr/src/sys/kern/subr_taskqueue.c:186 #29 0xc01c0e7a in taskqueue_swi_run () at /usr/src/sys/kern/subr_taskqueue.c:202 #30 0xc02ef0e0 in splz_swi () #31 0xc02f3b56 in cpu_idle () at /usr/src/sys/i386/i386/machdep.c:1000 Any ideas? Patches? Suggestions? Thanks, Andre From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 6 06:10:02 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 13A5216A4CE for ; Thu, 6 Nov 2003 06:10:02 -0800 (PST) Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id E6FD443F93 for ; Thu, 6 Nov 2003 06:10:00 -0800 (PST) (envelope-from marcov@stack.nl) Received: by mailhost.stack.nl (Postfix, from userid 65534) id 72A181F016; Thu, 6 Nov 2003 15:09:59 +0100 (CET) Received: from toad.stack.nl (toad.stack.nl [2001:610:1108:5010::135]) by mailhost.stack.nl (Postfix) with ESMTP id D5F931F012 for ; Thu, 6 Nov 2003 15:09:57 +0100 (CET) Received: by toad.stack.nl (Postfix, from userid 816) id B1B1E93; Thu, 6 Nov 2003 15:09:57 +0100 (CET) To: freebsd-hackers@freebsd.org Date: Thu, 6 Nov 2003 15:09:57 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL88 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Message-Id: <20031106140957.B1B1E93@toad.stack.nl> From: marcov@stack.nl (Marco van de Voort) X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on vaak.stack.nl X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Subject: Re: Kylix in FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Nov 2003 14:10:02 -0000 X-List-Received-Date: Thu, 06 Nov 2003 14:10:02 -0000 > * jasaorp [031031 04:59]: > > Somebody uses Kylix in FreeBSD? > > What is the performance? > > The IDE doesn't run under FreeBSD. I worked on it a bit over this > summer when the most recent Kylix came out, and it appears to rely on > too many Linux-isms. > > The command-line tools work just fine, and produce binaries that are on > par with the ones you get from Linux. If I remember from my testing, > the compiler produces Linux-style ELF binaries. > > Getting the Kylix IDE to function on FreeBSD has been one of the ongoing > hair-pulling tasks I undertake every few months. The installer alone is > a pain in the ass, since it performs "compatibility checks" in such > Linux-centric ways as hard-coding /bin/bash into the shell scripts, and > searching for shared libraries by name from hard-coded paths. (GTK > especially gives the installer fits because FreeBSD's gtk library has a > -x11 at the end of the name.) But once you work around those issues > with some creative symlinking and script editing, the console tools > install fairly painlessly. For some projects, using lang/fpc (get a newer version from the website, the 1.9beta supports nearly the entire D6 language set) and lazarus (lazarus.freepascal.org) as RAD might be of some use. It is native and open source. See also the next more elaborate message. Your mileage may vary depending on your skills and requirements, but it is definitely worth a look. If you futs with getting Kylix to run under FreeBSD, don't forget the special glibc requirements that some versions of Kylix have. Maybe you should probably simply replace the entire /compat userland with the userland of a distro that Kylix supprorts _with_ kylix extra patches installed? From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 6 06:10:29 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F2F0B16A4CE for ; Thu, 6 Nov 2003 06:10:28 -0800 (PST) Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id A151C43FCB for ; Thu, 6 Nov 2003 06:10:27 -0800 (PST) (envelope-from marcov@stack.nl) Received: by mailhost.stack.nl (Postfix, from userid 65534) id E955F1F012; Thu, 6 Nov 2003 15:10:26 +0100 (CET) Received: from toad.stack.nl (toad.stack.nl [2001:610:1108:5010::135]) by mailhost.stack.nl (Postfix) with ESMTP id 066CD1F006 for ; Thu, 6 Nov 2003 15:10:26 +0100 (CET) Received: by toad.stack.nl (Postfix, from userid 816) id C9C0493; Thu, 6 Nov 2003 15:10:25 +0100 (CET) To: freebsd-hackers@freebsd.org Date: Thu, 6 Nov 2003 15:10:25 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL88 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Message-Id: <20031106141025.C9C0493@toad.stack.nl> From: marcov@stack.nl (Marco van de Voort) X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on vaak.stack.nl X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Subject: Re: Kylix in FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Nov 2003 14:10:29 -0000 > I do not know about the C++ part of Kylix, but about the Delphi part, maybe > it could be replaced with FreePascal (http://www.freepascal.org/). There > are even some projects that try to produce an IDE similar to Delphi > (http://www.freepascal.org/links.html). > > Has anyone gived a try to FreePascal? I maintain it, the FPC on *BSD ports I mean. (but I'm not the FreeBSD ports tree entry maintainer). I just uploaded the first public beta from the future 2.0.x branch to the FTP FPC site last night. Bindings for several database types included. The GUI RAD project (Lazarus.freepascal.org) is gtk1.2 based and works with FreeBSD, however the conversion of lazarus to the future 2.0.x branch was only done a few days ago, so it might be wise to wait a month till the next version, or obtain a snapshot when lazarus is stabilized. (there is some minor problem in the pipe handling that connects the RAD to the compiler and debugger, which was fixed in the old branch, but not yet in the new one,) The new branch supports near the entire Delphi language set in principle (and is threadsafe), the one major exception I know of are dispinterfaces. Installation of the commandline compiler is very easy. Download the .tar, run sh install.sh, and answer yes on everything. (which will install most into /usr/local/lib/fpc, throw a few bins in /usr/local/bin, and some manpages and docs where it hopefully should be). Compiling and installing the RAD is somewhat more involved, but that is mainly because it is a moving target. Should be doable for a freebsd-hacker ( :-) ) People interested in FPC on *BSD can always contact me. P.s.1 German speakers: an article about installing lazarus + working (1.0.x) snapshots was published in the most recent FreeX (the one from oct 1th) http://www.cul.de/freex.html P.s.2 Matthew West added a compat_4 flag to the lang/fpc port. I would like to know what the reason for this is. (iow what do I have to change to make it FreeBSD native?) P.s.3 The new branch is multi architecture, though due to the preparing and debugging of the 1.9beta, all non-x86 archs (ARM,PPC,Sparc V8) are broken. However I did run Delphi code on NetBSD/macppc before it broke! From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 6 08:25:41 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E95B216A4CE for ; Thu, 6 Nov 2003 08:25:41 -0800 (PST) Received: from mail.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE40C43FEC for ; Thu, 6 Nov 2003 08:25:40 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 2506 invoked from network); 6 Nov 2003 16:25:39 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender )encrypted SMTP for ; 6 Nov 2003 16:25:39 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.9/8.12.9) with ESMTP id hA6GPEce081707; Thu, 6 Nov 2003 11:25:15 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20031106131918.GA41660@nm.ruhr-uni-bochum.de> Date: Thu, 06 Nov 2003 11:25:14 -0500 (EST) From: John Baldwin To: Andre Grosse Bley X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) cc: freebsd-hackers@freebsd.org Subject: RE: 4.9-RELEASE, ACPI and DELL Latitude D600 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Nov 2003 16:25:42 -0000 On 06-Nov-2003 Andre Grosse Bley wrote: > Hi all, > > i am trying to install FreeBSD 4.9-RELEASE on a Dell Latitude D600 > notebook. "standard" Kernel without ACPI works fine > (dmesg at http://www.nm.ruhr-uni-bochum.de/~gandalf/dell/dmesg.noacpi.txt) > > Since i need the batterystatus (and the Bios doesnt seem to support APM > anymore) i activated acpi: The machine paniced after detecting the brgphy0. > After removing pcic0/pcic1 from the kernel configuration, i was able to > boot with ACPI (wow!;) > But no batterystatus. Googling found a solution: > > http://sandcat.nl/~stijn/freebsd/dell.php > > I needed to add > acpi_dsdt_load="YES" > acpi_dsdt_name="/boot/acpi_dsdt.aml" > acpi_dsdt_type="acpi_dsdt" > > > to /boot/loader.conf > > dmesg is at http://www.nm.ruhr-uni-bochum.de/~gandalf/dell/dmesg.acpi.txt > > sysctl hw.acpi gives: > > hw.acpi.supported_sleep_state: S1 S3 S4 S5 > hw.acpi.power_button_state: S5 > hw.acpi.sleep_button_state: S1 > hw.acpi.lid_switch_state: S1 > hw.acpi.standby_state: S1 > hw.acpi.suspend_state: S3 > hw.acpi.sleep_delay: 0 > hw.acpi.s4bios: 1 > hw.acpi.verbose: 1 > hw.acpi.disable_on_poweroff: 1 > hw.acpi.cpu.max_speed: 8 > hw.acpi.cpu.current_speed: 8 > hw.acpi.cpu.performance_speed: 8 > hw.acpi.cpu.economy_speed: 4 > hw.acpi.thermal.min_runtime: 0 > hw.acpi.thermal.polling_rate: 30 > hw.acpi.thermal.tz0.temperature: 3127 > hw.acpi.thermal.tz0.active: -1 > hw.acpi.thermal.tz0.thermal_flags: 0 > hw.acpi.thermal.tz0._PSV: -1 > hw.acpi.thermal.tz0._HOT: -1 > hw.acpi.thermal.tz0._CRT: 3752 > hw.acpi.thermal.tz0._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 > hw.acpi.acline: 1 > hw.acpi.battery.life: 46 > hw.acpi.battery.time: -1 > hw.acpi.battery.state: 2 > hw.acpi.battery.units: 2 > hw.acpi.battery.info_expire: 5 > > My problem: the machine panics when closing the lid, even after > sysctl hw.acpi.lid_switch_state=NONE. > > Traceback without the sysctl is as follows: > > root@feap:~ $gdb -k /kernel.debug /var/crash/vmcore.1 > IdlePTD at phsyical address 0x00470000 > initial pcb at physical address 0x003b04e0 > panicstr: page fault > panic messages: > --- > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x70 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc01b5198 > stack pointer = 0x10:0xc0367b70 > frame pointer = 0x10:0xc0367b94 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = Idle > interrupt mask = net tty bio cam > trap number = 12 > panic: page fault > > syncing disks... > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x30 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc02784d0 > stack pointer = 0x10:0xc0367998 > frame pointer = 0x10:0xc03679a0 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = Idle > interrupt mask = net tty bio cam > trap number = 12 > panic: page fault > Uptime: 4m6s > >#0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:487 >#1 0xc01b20f7 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:316 >#2 0xc01b2535 in panic (fmt=0xc035f76c "%s") > at /usr/src/sys/kern/kern_shutdown.c:595 >#3 0xc02fa003 in trap_fatal (frame=0xc0367958, eva=48) > at /usr/src/sys/i386/i386/trap.c:974 >#4 0xc02f9cb1 in trap_pfault (frame=0xc0367958, usermode=0, eva=48) > at /usr/src/sys/i386/i386/trap.c:867 >#5 0xc02f9857 in trap (frame={tf_fs = -1071841264, tf_es = -65520, > tf_ds = -1070202864, tf_edi = 0, tf_esi = -1036472064, > tf_ebp = -1070171744, tf_isp = -1070171772, tf_ebx = -1070075364, > tf_edx = 6866944, tf_ecx = -614904832, tf_eax = 0, tf_trapno = 12, > tf_err = 0, tf_eip = -1071151920, tf_cs = 8, tf_eflags = 66182, > tf_esp = -1036472064, tf_ss = -1036472064}) > at /usr/src/sys/i386/i386/trap.c:466 >#6 0xc02784d0 in acquire_lock (lk=0xc037f21c) > at /usr/src/sys/ufs/ffs/ffs_softdep.c:266 >#7 0xc027c5d0 in softdep_update_inodeblock (ip=0xc238b100, bp=0xcc94a43c, > waitfor=0) at /usr/src/sys/ufs/ffs/ffs_softdep.c:3813 >#8 0xc0277605 in ffs_update (vp=0xdb594c00, waitfor=0) > at /usr/src/sys/ufs/ffs/ffs_inode.c:106 >#9 0xc027fa4e in ffs_sync (mp=0xc2318600, waitfor=2, cred=0xc1453680, > p=0xc03caf20) at /usr/src/sys/ufs/ffs/ffs_vfsops.c:1025 >#10 0xc01e2e7b in sync (p=0xc03caf20, uap=0x0) > at /usr/src/sys/kern/vfs_syscalls.c:577 >#11 0xc01b1e92 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:235 >#12 0xc01b2535 in panic (fmt=0xc035f76c "%s") > at /usr/src/sys/kern/kern_shutdown.c:595 >#13 0xc02fa003 in trap_fatal (frame=0xc0367b30, eva=112) > at /usr/src/sys/i386/i386/trap.c:974 >#14 0xc02f9cb1 in trap_pfault (frame=0xc0367b30, usermode=0, eva=112) > at /usr/src/sys/i386/i386/trap.c:867 >#15 0xc02f9857 in trap (frame={tf_fs = -1070202864, tf_es = -1070465008, > tf_ds = -1070465008, tf_edi = 0, tf_esi = -1069882148, > tf_ebp = -1070171244, tf_isp = -1070171300, tf_ebx = 0, tf_edx = 0, > tf_ecx = 200, tf_eax = 6291968, tf_trapno = 12, tf_err = 0, > tf_eip = -1071951464, tf_cs = 8, tf_eflags = 66118, tf_esp = 0, > tf_ss = 274877907}) at /usr/src/sys/i386/i386/trap.c:466 >#16 0xc01b5198 in tsleep (ident=0xc03ae4dc, priority=0, > wmesg=0xc0328583 "acpislp", timo=200) at /usr/src/sys/kern/kern_synch.c:436 Ah, the problem is that ACPI tries to sleep from a task, which is not safe to do. This is not easy to fix. :( -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 6 09:15:49 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E1CA616A4CE for ; Thu, 6 Nov 2003 09:15:49 -0800 (PST) Received: from serl.cs.colorado.edu (serl-fs.cs.colorado.edu [128.138.242.215]) by mx1.FreeBSD.org (Postfix) with ESMTP id 265B843FFD for ; Thu, 6 Nov 2003 09:15:45 -0800 (PST) (envelope-from John.Giacomoni@colorado.edu) Received: from [127.0.0.1] (localhost [127.0.0.1]) by serl.cs.colorado.edu (8.12.9/8.12.6) with ESMTP id hA6HFgiQ028653 for ; Thu, 6 Nov 2003 10:15:42 -0700 (MST) Mime-Version: 1.0 (Apple Message framework v606) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; format=flowed To: freebsd-hackers@freebsd.org From: John Giacomoni Date: Thu, 6 Nov 2003 10:15:44 -0700 X-Mailer: Apple Mail (2.606) Subject: locking ifpromisc (struct ifnet) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Nov 2003 17:15:50 -0000 Currently how should one lock a struct ifnet* so one can safely use ifpromisc on it? I'm writting a module similar to the bpf, however I am failing to follow the correct way to safely establish locking. Grabbing [Giant does not seem correct as Giant is being removed] my understanding is that one uses ifunit to convert if_name -> struct ifnet *ifp and then one uses the *ifp in the ifpromisc call. the safety I'm referring to would be: a) device deallocation in between ifunit and ifpromisc. b) simultaneous calls to ifpromisc d) a simultaneous ifpromisc call and the device being removed and deallocated. my guess would be to grab IFNET_RLOCK or IFNET_WLOCK, then do the ifunit name -> ifp translation, ifpromisc, then the IFNET_UN[RW]LOCK is this correct? for the present? for the future? is there a way to acquire a struct ifnet* and keep it around safely? [perhaps some kind of notification system for when an ifp is no longer valid?] thanks John G -- University of Colorado at Boulder John.Giacomoni@colorado.edu Department of Computer Science phone: 303.492.8115 Engineering Center, ECCS 121 303.492.7906 430 UCB fax: 303.492.2844 Boulder, CO 80303-0430 USA From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 6 10:48:30 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9504216A4CE for ; Thu, 6 Nov 2003 10:48:30 -0800 (PST) Received: from mail.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D3BE44005 for ; Thu, 6 Nov 2003 10:48:28 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 15871 invoked from network); 6 Nov 2003 18:48:26 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender )encrypted SMTP for ; 6 Nov 2003 18:48:26 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.9/8.12.9) with ESMTP id hA6Iluce082366; Thu, 6 Nov 2003 13:47:57 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 06 Nov 2003 13:47:55 -0500 (EST) From: John Baldwin To: John Baldwin X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) cc: freebsd-hackers@freebsd.org Subject: RE: 4.9-RELEASE, ACPI and DELL Latitude D600 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Nov 2003 18:48:30 -0000 On 06-Nov-2003 John Baldwin wrote: > > On 06-Nov-2003 Andre Grosse Bley wrote: >> Hi all, >> >> i am trying to install FreeBSD 4.9-RELEASE on a Dell Latitude D600 >> notebook. "standard" Kernel without ACPI works fine >> (dmesg at http://www.nm.ruhr-uni-bochum.de/~gandalf/dell/dmesg.noacpi.txt) >> >> Since i need the batterystatus (and the Bios doesnt seem to support APM >> anymore) i activated acpi: The machine paniced after detecting the brgphy0. >> After removing pcic0/pcic1 from the kernel configuration, i was able to >> boot with ACPI (wow!;) >> But no batterystatus. Googling found a solution: >> >> http://sandcat.nl/~stijn/freebsd/dell.php >> >> I needed to add >> acpi_dsdt_load="YES" >> acpi_dsdt_name="/boot/acpi_dsdt.aml" >> acpi_dsdt_type="acpi_dsdt" >> >> >> to /boot/loader.conf >> >> dmesg is at http://www.nm.ruhr-uni-bochum.de/~gandalf/dell/dmesg.acpi.txt >> >> My problem: the machine panics when closing the lid, even after >> sysctl hw.acpi.lid_switch_state=NONE. >> > > Ah, the problem is that ACPI tries to sleep from a task, which is not safe > to do. This is not easy to fix. :( Actually, it may not be too hard. In current, ACPI uses its own thread to run the tasks in, so stable would need the same sort of thing. Basically, ACPI needs to start up a kproc and needs to have its own taskqueue again that uses this kproc for its execution context. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 6 16:59:53 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9E69116A4CE for ; Thu, 6 Nov 2003 16:59:53 -0800 (PST) Received: from web11407.mail.yahoo.com (web11407.mail.yahoo.com [216.136.131.237]) by mx1.FreeBSD.org (Postfix) with SMTP id 0FBDD4400F for ; Thu, 6 Nov 2003 16:59:53 -0800 (PST) (envelope-from raysonlogin@yahoo.com) Message-ID: <20031107005951.2157.qmail@web11407.mail.yahoo.com> Received: from [65.49.80.122] by web11407.mail.yahoo.com via HTTP; Thu, 06 Nov 2003 16:59:51 PST Date: Thu, 6 Nov 2003 16:59:51 -0800 (PST) From: Rayson Ho To: bioclusters@bioinformatics.org, beowulf , Linux Cluster , List In-Reply-To: <20031106145623.GA5867@iib.unsam.edu.ar> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Linux vs FreeBSD clusters (was: how are the Redhat product changes affecting existing and future plans?) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Nov 2003 00:59:53 -0000 A very good paper about building HPC clusters with FreeBSD: "Building a High-performance Computing Cluster Using FreeBSD" http://people.freebsd.org/~brooks/papers/bsdcon2003/ The author talked about hardware issues: KVM, BIOS redirection, CPU choices; and then talked about why he chose FreeBSD instead of Linux... he also did the port of GridEngine (SGE) to FreeBSD. Anyone tried to setup HPC clusters with *BSD?? Rayson --- Fernan Aguero wrote: > Any FreeBSD users willing to share clustering experiences > out there? > > Fernan __________________________________ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 6 17:41:42 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D976516A4CE for ; Thu, 6 Nov 2003 17:41:42 -0800 (PST) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 23BA243F3F for ; Thu, 6 Nov 2003 17:41:42 -0800 (PST) (envelope-from sam@errno.com) Received: from 66.127.85.91 ([66.127.85.91]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.9) with ESMTP id hA71dl0x093227 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Thu, 6 Nov 2003 17:39:52 -0800 (PST) (envelope-from sam@errno.com) From: Sam Leffler Organization: Errno Consulting To: Steven Hartland , Date: Thu, 6 Nov 2003 17:41:45 -0800 User-Agent: KMail/1.5.3 References: <01d501c3a3ca$caa925b0$b3db87d4@multiplay.co.uk> In-Reply-To: <01d501c3a3ca$caa925b0$b3db87d4@multiplay.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200311061741.45354.sam@errno.com> Subject: Re: 5.1-CURRENT (today), ath(4) + Dlink DWL-AG650 = no joy X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Nov 2003 01:41:43 -0000 On Wednesday 05 November 2003 10:29 am, Steven Hartland wrote: > Is anyone using this atm. Just got the card today as it was in > the hardware compat list for the ath driver but I not having > any joy with it. > On insert or boot it identifies as: > ath0: ... > ... > . > But when using ifconfig I get: > No support for the 5112 yet! > ath0: unable to reset hardware; hal status 3 > > Any ideas? Wait for a HAL upgrade. It's coming. Sam From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 6 17:55:49 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1354616A4CE for ; Thu, 6 Nov 2003 17:55:49 -0800 (PST) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1F07243F93 for ; Thu, 6 Nov 2003 17:55:48 -0800 (PST) (envelope-from rodperson@comcast.net) Received: from roland.opensourcebeef.bsd.st (c-24-3-204-103.client.comcast.net[24.3.204.103]) by comcast.net (rwcrmhc12) with SMTP id <2003110701554601400hr24ve>; Fri, 7 Nov 2003 01:55:47 +0000 From: Rod Person Organization: Open Source Beef To: marcov@stack.nl (Marco van de Voort), freebsd-hackers@freebsd.org Date: Thu, 6 Nov 2003 20:54:49 -0500 User-Agent: KMail/1.5.2 References: <20031106140957.B1B1E93@toad.stack.nl> In-Reply-To: <20031106140957.B1B1E93@toad.stack.nl> X-OSB: This means that this is a real email from Roddie Rod, Not Spam MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200311062054.49682.rodperson@comcast.net> Subject: Re: Kylix in FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: rodperson@comcast.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Nov 2003 01:55:49 -0000 On Thursday 06 November 2003 09:09 am, It was written: > If you futs with getting Kylix to run under FreeBSD, don't forget the > special glibc requirements that some versions of Kylix have. Maybe you > should probably simply replace the entire /compat userland with the > userland of a distro that Kylix supprorts _with_ kylix extra patches > installed? Marco, Have you tried this? Since Kylix came out I have tried to get it to run on FreeBSD and various Linux distros. A few days ago I got kylix to run on SuSE 8.2 (from the kylix newsgroups this seems to be the best distro for it). NetBSDs Linux emulation is based on SuSE, isn't it? But, I found no postings related to Kylix on NetBSD. My next wondering is would NetBSD Linux emu run under FreeBSD and would this run kylix? -- Rod @ Home So No Cool Signature AIM: TheRealRoddieRod Yahoo:RoddieRod http://opensourcebeef.bsd.st From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 6 20:02:44 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 27F3016A4CE for ; Thu, 6 Nov 2003 20:02:44 -0800 (PST) Received: from h00609772adf0.ne.client2.attbi.com (h00609772adf0.ne.client2.attbi.com [66.31.45.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id B4BAE43FCB for ; Thu, 6 Nov 2003 20:02:42 -0800 (PST) (envelope-from rodrigc@crodrigues.org) Received: from h00609772adf0.ne.client2.attbi.com (localhost.crodrigues.org [127.0.0.1])hA744HdN006219; Thu, 6 Nov 2003 23:04:17 -0500 (EST) (envelope-from rodrigc@h00609772adf0.ne.client2.attbi.com) Received: (from rodrigc@localhost)hA744FKN006218; Thu, 6 Nov 2003 23:04:15 -0500 (EST) (envelope-from rodrigc) Date: Thu, 6 Nov 2003 23:04:15 -0500 From: Craig Rodrigues To: Rayson Ho Message-ID: <20031107040415.GA5711@crodrigues.org> References: <20031106145623.GA5867@iib.unsam.edu.ar> <20031107005951.2157.qmail@web11407.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031107005951.2157.qmail@web11407.mail.yahoo.com> User-Agent: Mutt/1.4i cc: List cc: bioclusters@bioinformatics.org cc: beowulf cc: Linux Cluster Subject: Re: Linux vs FreeBSD clusters (was: how are the Redhat product changes affecting existing and future plans?) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Nov 2003 04:02:44 -0000 On Thu, Nov 06, 2003 at 04:59:51PM -0800, Rayson Ho wrote: > A very good paper about building HPC clusters with FreeBSD: > > "Building a High-performance Computing Cluster Using FreeBSD" > > http://people.freebsd.org/~brooks/papers/bsdcon2003/ > > The author talked about hardware issues: KVM, BIOS redirection, CPU > choices; and then talked about why he chose FreeBSD instead of Linux... > he also did the port of GridEngine (SGE) to FreeBSD. > > Anyone tried to setup HPC clusters with *BSD?? Hi, Not quite the same as an HPC cluster, but take a look at the University of Utah's Emulab: http://www.emulab.net It is heavily based on FreeBSD (i.e. makes use of FreeBSD routing, Dummynet, etc.). The Emulab is a remotely accessible testbed that researchers can use to conduct network experiments. It consists of about 200 PC nodes. The same company that Brooks works for (Aerospace), has apparently set up an internal testbed based on the Emulab software developed at Utah. I use the Emulab every day as party of my research work at BBN, and it is an excellent facility. -- Craig Rodrigues http://crodrigues.org rodrigc@crodrigues.org From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 6 20:20:58 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1789D16A4CE for ; Thu, 6 Nov 2003 20:20:58 -0800 (PST) Received: from netmeister.org (netmeister.org [64.81.200.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id D8C3B43FB1 for ; Thu, 6 Nov 2003 20:20:56 -0800 (PST) (envelope-from jschauma@netmeister.org) Received: by netmeister.org (Postfix, from userid 1000) id 9B99B2DC624; Thu, 6 Nov 2003 23:22:50 -0500 (EST) Date: Thu, 6 Nov 2003 23:22:50 -0500 From: Jan Schaumann To: Rayson Ho Message-ID: <20031107042250.GB3913@netmeister.org> Mail-Followup-To: Rayson Ho , bioclusters@bioinformatics.org, beowulf , Linux Cluster , List , tech-cluster@netbsd.org References: <20031106145623.GA5867@iib.unsam.edu.ar> <20031107005951.2157.qmail@web11407.mail.yahoo.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="XF85m9dhOBO43t/C" Content-Disposition: inline In-Reply-To: <20031107005951.2157.qmail@web11407.mail.yahoo.com> User-Agent: Mutt/1.4i cc: List cc: bioclusters@bioinformatics.org cc: beowulf cc: tech-cluster@netbsd.org cc: Linux Cluster Subject: Re: Linux vs FreeBSD clusters (was: how are the Redhat product changes affecting existing and future plans?) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Nov 2003 04:20:58 -0000 --XF85m9dhOBO43t/C Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Rayson Ho wrote: > A very good paper about building HPC clusters with FreeBSD: >=20 > "Building a High-performance Computing Cluster Using FreeBSD" >=20 > http://people.freebsd.org/~brooks/papers/bsdcon2003/ >=20 > The author talked about hardware issues: KVM, BIOS redirection, CPU > choices; and then talked about why he chose FreeBSD instead of Linux... > he also did the port of GridEngine (SGE) to FreeBSD. >=20 > Anyone tried to setup HPC clusters with *BSD?? I have a 30 node NetBSD/i386 cluster, and just recently created the tech-cluster@netbsd.org mailing list. Some people are working on a port of SGE to NetBSD, too. I hope to expand the awareness of NetBSD in particular for cluster usage in the near future. Some URLs of relevance: http://guinness.cs.stevens-tech.edu/~jschauma/hpcf/ http://www.netbsd.org/MailingLists/#tech-cluster http://www.netbsd.org/ http://eurobsdcon.org/papers/#souvatzis http://bsd.slashdot.org/article.pl?sid=3D03/10/20/1523252&mode=3Dthread&tid= =3D122&tid=3D185&tid=3D190 http://bsd.slashdot.org/bsd/03/11/05/1536226.shtml?tid=3D122&tid=3D185&tid= =3D190 -Jan --=20 Life," said Marvin, "don't talk to me about life." --XF85m9dhOBO43t/C Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (NetBSD) iD8DBQE/qx4afFtkr68iakwRAlZaAKDNrRoIwtwjP9t4/eEfBEtpiv/p6ACgt5FR 9gGHhsjX+zJE9NeSwAwgLo8= =zUsX -----END PGP SIGNATURE----- --XF85m9dhOBO43t/C-- From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 6 20:43:57 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 385CF16A4CE for ; Thu, 6 Nov 2003 20:43:57 -0800 (PST) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 53B3F43FBD for ; Thu, 6 Nov 2003 20:43:56 -0800 (PST) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (IDENT:brdavis@localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.12.9/8.12.3) with ESMTP id hA74hVXU029131; Thu, 6 Nov 2003 20:43:31 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.12.9/8.12.3/Submit) id hA74hVql029121; Thu, 6 Nov 2003 20:43:31 -0800 Date: Thu, 6 Nov 2003 20:43:30 -0800 From: Brooks Davis To: Craig Rodrigues Message-ID: <20031107044322.GA23181@Odin.AC.HMC.Edu> References: <20031106145623.GA5867@iib.unsam.edu.ar> <20031107005951.2157.qmail@web11407.mail.yahoo.com> <20031107040415.GA5711@crodrigues.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="a8Wt8u1KmwUX3Y2C" Content-Disposition: inline In-Reply-To: <20031107040415.GA5711@crodrigues.org> User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-milter (http://amavis.org/) on odin.ac.hmc.edu cc: List cc: bioclusters@bioinformatics.org cc: beowulf cc: Linux Cluster cc: Rayson Ho Subject: Re: Linux vs FreeBSD clusters (was: how are the Redhat product changes affecting existing and future plans?) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Nov 2003 04:43:57 -0000 --a8Wt8u1KmwUX3Y2C Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Nov 06, 2003 at 11:04:15PM -0500, Craig Rodrigues wrote: > Not quite the same as an HPC cluster, but take > a look at the University of Utah's Emulab: >=20 > http://www.emulab.net >=20 > It is heavily based on FreeBSD (i.e. makes use of FreeBSD routing, > Dummynet, etc.). The Emulab is a remotely accessible testbed > that researchers can use to conduct network experiments. It > consists of about 200 PC nodes. The same company that=20 > Brooks works for (Aerospace), has apparently set up > an internal testbed based on the Emulab software developed at Utah. We (my department, but mostly different people then Fellowship) have a small 10-node setup (though each node does have 6 gigabit ports :-). I think we're aiming to upgrade to around 48 nodes in the next year. Our HPC cluster is currently pretty close to what's described in the paper, though we are up to 160 nodes and we're adding rack space for another 192 this year. The short version of my take on which OS to run on your cluster is that so long as it runs the apps you need, the best OS is one you know how to admin well since that's most of the work. I've spent a few weeks here and there porting applictions or improving their ports, but by and large, most key systems are already ported to the major UNIX platforms. The free MPI implemntations work on just about anything, the base Ganglia metrics work nearly everywhere (FreeBSD and Linux are at feature parity in the upcoming release), and SGE works on a wide range of platforms. On an amusing note, we were the launch customer for Grid Mathematica despite not running a supported OS because the Linux version runs just fine on FreeBSD. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --a8Wt8u1KmwUX3Y2C Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE/qyLlXY6L6fI4GtQRAgRdAKDL9Eh1RB4Q0eBBFhKNhizmT9+cbQCeIe0+ VNFsAkXmJmeO9w7ESxHEuvE= =yKvI -----END PGP SIGNATURE----- --a8Wt8u1KmwUX3Y2C-- From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 6 23:29:12 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4D42616A4CE; Thu, 6 Nov 2003 23:29:12 -0800 (PST) Received: from firecrest.mail.pas.earthlink.net (firecrest.mail.pas.earthlink.net [207.217.121.247]) by mx1.FreeBSD.org (Postfix) with ESMTP id 64C2343FE3; Thu, 6 Nov 2003 23:29:11 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from user-2ivfi0e.dialup.mindspring.com ([165.247.200.14] helo=mindspring.com) by firecrest.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 1AI13J-0005Lm-00; Thu, 06 Nov 2003 23:29:06 -0800 Message-ID: <3FAB49CF.931D1C48@mindspring.com> Date: Thu, 06 Nov 2003 23:29:19 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Mike Silbersack References: <3F9F9884.3020309@noviforum.si> <20031030050540.GA25906@rot13.obsecurity.org> <20031106005009.D1561@odysseus.silby.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a46dca913c26aa10fdf732af28134a5bff666fa475841a1c7a350badd9bab72f9c350badd9bab72f9c cc: "Branko F. Grac\(nar" cc: freebsd-hackers@freebsd.org cc: freebsd-current@freebsd.org cc: "Giovanni P. Tirloni" Subject: Re: FreeBSD 5.1-p10 reproducible crash with Apache2 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Nov 2003 07:29:12 -0000 Mike Silbersack wrote: > On Wed, 5 Nov 2003, [ISO-8859-1] "Branko F. Grac(nar" wrote: > > I tried today with yesterday's -CURRENT. Same symptoms. No kernel panic, > > just lockup. > > Ok, submit a PR with clear details on how to recreate the problem, and > we'll see if someone can take a look into it. I'm too busy to look at it, > but at least putting it in a PR will ensure that it doesn't get too lost. > Once the PR is filed, you might want to try asking on the freebsd-threads > list; it sounds like the issue might be thread-related. > > (Note that your original e-mail might contain enough detail, I'm not > certain; I just skimmed it. Filing a good PR is important either way, > mailing list messages get easily lost.) Is gdb good enough in FreeBSD that you can break to the kernel debugger with GDB enabled, and dump out the stacks for all threads currently in the kernel for all processes? The way to find this, if it's a threads related issue, is to do exactly that, and then look to se if there's something like a close in one thread of an fd being used in a blocking operation in another thread. -- Terry From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 6 23:59:07 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D7E5616A4CF for ; Thu, 6 Nov 2003 23:59:07 -0800 (PST) Received: from razorbill.mail.pas.earthlink.net (razorbill.mail.pas.earthlink.net [207.217.121.248]) by mx1.FreeBSD.org (Postfix) with ESMTP id 19BCA43FFB for ; Thu, 6 Nov 2003 23:59:07 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from user-2ivfi0e.dialup.mindspring.com ([165.247.200.14] helo=mindspring.com) by razorbill.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 1AI1WG-0001WY-00; Thu, 06 Nov 2003 23:59:01 -0800 Message-ID: <3FAB50D6.39BDF991@mindspring.com> Date: Thu, 06 Nov 2003 23:59:18 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: rodperson@comcast.net References: <20031106140957.B1B1E93@toad.stack.nl> <200311062054.49682.rodperson@comcast.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4de023130d0ef96a870cd5ef43258e206350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c cc: freebsd-hackers@freebsd.org Subject: Re: Kylix in FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Nov 2003 07:59:08 -0000 Rod Person wrote: > On Thursday 06 November 2003 09:09 am, It was written: > > If you futs with getting Kylix to run under FreeBSD, don't forget the > > special glibc requirements that some versions of Kylix have. Maybe you > > should probably simply replace the entire /compat userland with the > > userland of a distro that Kylix supprorts _with_ kylix extra patches > > installed? > > Have you tried this? Since Kylix came out I have tried to get it to run on > FreeBSD and various Linux distros. A few days ago I got kylix to run on SuSE > 8.2 (from the kylix newsgroups this seems to be the best distro for it). > NetBSDs Linux emulation is based on SuSE, isn't it? But, I found no postings > related to Kylix on NetBSD. My next wondering is would NetBSD Linux emu run > under FreeBSD and would this run kylix? Since all new developement in Kylix is apparently officially stalled, now would be a good time to do the porting work, since it's no longer a moving target... http://www.linuxworld.com.au/nindex.php?id=122384005&eid=-50 -- Terry From owner-freebsd-hackers@FreeBSD.ORG Fri Nov 7 01:49:02 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B118116A4CE for ; Fri, 7 Nov 2003 01:49:02 -0800 (PST) Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F86143FBF for ; Fri, 7 Nov 2003 01:49:00 -0800 (PST) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32] ident=danny) by cs.huji.ac.il with esmtp id 1AI3Eg-000MxI-QB for freebsd-hackers@freebsd.org; Fri, 07 Nov 2003 11:48:58 +0200 X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4 To: freebsd-hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 07 Nov 2003 11:48:58 +0200 From: Danny Braniss Message-Id: Subject: iSCSI X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Nov 2003 09:49:02 -0000 hi all, is there any interest/progress with SCSI over IP? I am asking because our NetApp is supposed to support it, and the other approach, FiberChannel/EMC seems 'slightly' expensive. thanks, danny PS: all our servers are running Freebsd 4.[8-9] with great success From owner-freebsd-hackers@FreeBSD.ORG Fri Nov 7 01:57:42 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BEC2716A4CE for ; Fri, 7 Nov 2003 01:57:42 -0800 (PST) Received: from mailhub.fokus.fraunhofer.de (mailhub.fokus.fraunhofer.de [193.174.154.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E8EB43FE1 for ; Fri, 7 Nov 2003 01:57:41 -0800 (PST) (envelope-from brandt@fokus.fraunhofer.de) Received: from beagle (beagle [193.175.132.100])hA79ud628194; Fri, 7 Nov 2003 10:56:39 +0100 (MET) Date: Fri, 7 Nov 2003 10:56:39 +0100 (CET) From: Harti Brandt To: Danny Braniss In-Reply-To: Message-ID: <20031107105434.J11960@beagle.fokus.fraunhofer.de> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hackers@freebsd.org Subject: Re: iSCSI X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Nov 2003 09:57:42 -0000 On Fri, 7 Nov 2003, Danny Braniss wrote: DB>hi all, DB> is there any interest/progress with SCSI over IP? DB>I am asking because our NetApp is supposed to support it, and the other DB>approach, FiberChannel/EMC seems 'slightly' expensive. DB> DB>thanks, DB> danny DB>PS: all our servers are running Freebsd 4.[8-9] with great success Did you look into Joerg Schillings SCSI library? As far as I know it allows transport of SCSI over whatever connection you have. It should be included in the cdrecord sources (don't know whether there is a standalone port). You may also contact schilling@fokus.fraunhofer.de. harti -- harti brandt, http://www.fokus.fraunhofer.de/research/cc/cats/employees/hartmut.brandt/private brandt@fokus.fraunhofer.de, harti@freebsd.org From owner-freebsd-hackers@FreeBSD.ORG Fri Nov 7 02:00:46 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2BF0416A4CE for ; Fri, 7 Nov 2003 02:00:46 -0800 (PST) Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D68F43FE1 for ; Fri, 7 Nov 2003 02:00:45 -0800 (PST) (envelope-from marcov@stack.nl) Received: by mailhost.stack.nl (Postfix, from userid 65534) id 961601F003; Fri, 7 Nov 2003 11:00:44 +0100 (CET) Received: from toad.stack.nl (toad.stack.nl [2001:610:1108:5010::135]) by mailhost.stack.nl (Postfix) with ESMTP id AF7E51F00E for ; Fri, 7 Nov 2003 11:00:43 +0100 (CET) Received: by toad.stack.nl (Postfix, from userid 816) id 9651F89; Fri, 7 Nov 2003 11:00:43 +0100 (CET) To: freebsd-hackers@freebsd.org Date: Fri, 7 Nov 2003 11:00:43 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL88 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Message-Id: <20031107100043.9651F89@toad.stack.nl> From: marcov@stack.nl (Marco van de Voort) X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on vaak.stack.nl X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Subject: Re: Kylix in FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Nov 2003 10:00:46 -0000 Hmm, and to the list :) > Rod Person + Terry Lamber wrote: > > On Thursday 06 November 2003 09:09 am, It was written: > > > If you futs with getting Kylix to run under FreeBSD, don't forget the > > > special glibc requirements that some versions of Kylix have. Maybe you > > > should probably simply replace the entire /compat userland with the > > > userland of a distro that Kylix supprorts _with_ kylix extra patches > > > installed? RP: > > Have you tried this? No, I only needed the commandline compiler at the time. It is also only a suggestion for something to look into. I don't have Kylix anymore (it was my employers) > > Since Kylix came out I have tried to get it to run on FreeBSD and > > various Linux distros. A few days ago I got kylix to run on SuSE 8.2 > > (from the kylix newsgroups this seems to be the best distro for it). > > NetBSDs Linux emulation is based on SuSE, isn't it? But, I found no > > postings related to Kylix on NetBSD. My next wondering is would NetBSD > > Linux emu run under FreeBSD and would this run kylix? No idea. > Since all new developement in Kylix is apparently officially > stalled, now would be a good time to do the porting work, since > it's no longer a moving target... Not me, IMHO the fpc (+lazarus) port is more important atm. It generates much simpler apps, but it is native on every 4.x and 5.x with gtk12, and connects to the free dbs without much fuzz :-) Moreover it is not dead. Kylix is dead. Probably both because Borland got in bed with Microsoft because of .NET, and because it was no commercial success. Kylix is a bastard child compared to Delphi, but not _that_ bad, and being the only similar tool in the market should have made up for that. Productivity is apparantly not appreciated under Linux yet, or the demand for small/medium custom client-server apps on linux is still too low. From owner-freebsd-hackers@FreeBSD.ORG Fri Nov 7 05:38:59 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A1A6E16A4CE; Fri, 7 Nov 2003 05:38:59 -0800 (PST) Received: from sana.init-main.com (104.194.138.210.bn.2iij.net [210.138.194.104]) by mx1.FreeBSD.org (Postfix) with ESMTP id 00B0C43FF7; Fri, 7 Nov 2003 05:38:58 -0800 (PST) (envelope-from takawata@init-main.com) Received: from init-main.com (localhost [127.0.0.1]) by sana.init-main.com (8.12.10/8.12.9) with ESMTP id hA7DVfkf026399; Fri, 7 Nov 2003 22:31:41 +0900 (JST) (envelope-from takawata@init-main.com) Message-Id: <200311071331.hA7DVfkf026399@sana.init-main.com> To: jhb@freebsd.org Date: Fri, 07 Nov 2003 22:31:41 +0900 From: Takanori Watanabe cc: hackers@freebsd.org cc: acpi-jp@jp.freebsd.org Subject: Re-enabling ACPI module. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Nov 2003 13:38:59 -0000 Hi, I looked in the new APIC code you commit. The thing that prevent ACPI subsystem from moduler is the way we aquire ACPI root pointer, I think. Right? If so, we can took this in way. 1. Move u_long i386_acpi_root; to machdep.c and madt.c use i386_acpi_root variable, instead of calling AcpiOsGetRootPointer. If Boot loader failed to detect ACPI root pointer, the MADT table is not used, even if the OS can detect it. 2. Re-imprement AcpiOsGetRootPointer so that it does not use AcpiFindRootPointer(). Which do you think better? From owner-freebsd-hackers@FreeBSD.ORG Fri Nov 7 07:50:35 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F0B8616A4CE for ; Fri, 7 Nov 2003 07:50:35 -0800 (PST) Received: from www.premsoft.co.za (www.rune.za.net [196.37.142.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7490E4400D for ; Fri, 7 Nov 2003 07:50:28 -0800 (PST) (envelope-from freebsd-questions@premsoft.co.za) Received: from jaco[196.33.196.21] by www.premsoft.co.za; Fri, 07 Nov 2003 18:12:24 +0200 Message-ID: <070401c3a546$d7e92360$3635a8c0@jaco> From: "Jaco H. van Tonder" To: "FreeBSD-Hackers" Date: Fri, 7 Nov 2003 17:49:35 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 cc: freebsd-current@freebsd.org Subject: [CURRENT] Panic in -CURRENT of 20031105 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Nov 2003 15:50:36 -0000 Hi All, I get panics at random times of the day with -CURRENT from 20031105, with absolutely no load on the machine. The machine acts as a dial-up server/gateway/firewall for my local lan. I managed to get a coredump. The contents of the rt pointer passed to RTFREE() does really not look right to me. These in particular: rt_llinfo = 0xc0f95880 "\220ǼÁ\200qùÀ" rn_Key = 0xc1bcc7a0 "0AùÀ8AùÀ" Anyone got any ideas? Thanks Jaco firewall# uname -a FreeBSD firewall.symphiano 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Fri Nov 7 15:31:34 SAST 2003 jacovt@firewall.symphiano:/usr/src/sys/i386/compile/FIREWALL i386 firewall# dmesg Copyright (c) 1992-2003 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 5.1-CURRENT #0: Fri Nov 7 15:31:34 SAST 2003 jacovt@firewall.symphiano:/usr/src/sys/i386/compile/FIREWALL Preloaded elf kernel "/boot/kernel/kernel" at 0xc06cf000. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Pentium II/Pentium II Xeon/Celeron (501.14-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x665 Stepping = 5 Features=0x183f9ff real memory = 134217728 (128 MB) avail memory = 124952576 (119 MB) Pentium Pro MTRR support enabled npx0: [FAST] npx0: on motherboard npx0: INT 16 interface pcibios: BIOS version 2.10 Using $PIR table, 7 entries at 0xc00fded0 pcib0: at pcibus 0 on motherboard pci0: on pcib0 pci_cfgintr: 0:8 INTA BIOS irq 11 pci_cfgintr: 0:10 INTA BIOS irq 10 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci_cfgintr: 0:1 INTA routed to irq 11 pcib1: slot 0 INTA is routed to irq 11 pci1: at device 0.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xe000-0xe00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] pci0: at device 7.2 (no driver attached) pci0: at device 7.3 (no driver attached) xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xe800-0xe87f mem 0xdf800000-0xdf80007f irq 11 at device 8.0 on pci0 xl0: Ethernet address: 00:50:da:45:92:81 miibus0: on xl0 xlphy0: <3c905C 10/100 internal PHY> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci0: at device 10.0 (no driver attached) orm0: