From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 13 03:33:17 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 1385A16A41F for ; Sun, 13 Nov 2005 03:33:17 +0000 (GMT) (envelope-from sebastien.bourdeauducq@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A12243D45 for ; Sun, 13 Nov 2005 03:33:16 +0000 (GMT) (envelope-from sebastien.bourdeauducq@gmail.com) Received: by xproxy.gmail.com with SMTP id t10so1379556wxc for ; Sat, 12 Nov 2005 19:33:16 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:to:subject:date:user-agent:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=JdNGI2LpJiU1Z2maHYvIMoQDTW6SRXHNpSpRL+d4RBMf19pKojfGHHfunAcD8FjR0+IRyQTrLWYwVXdw7/smXNv/yriyyigcyoW7wstH+sFZmGBlrIhrlJb2wizedk8eO/Uu8DSmj1W8wDXp532Dc/lHCGXCyF5VoNRwekBrcxA= Received: by 10.64.193.9 with SMTP id q9mr675596qbf; Sat, 12 Nov 2005 04:55:49 -0800 (PST) Received: from 192.168.1.12 ( [83.198.45.72]) by mx.gmail.com with ESMTP id q18sm464993qbq.2005.11.12.04.55.48; Sat, 12 Nov 2005 04:55:49 -0800 (PST) From: Sebastien To: freebsd-hackers@freebsd.org Date: Sat, 12 Nov 2005 14:00:01 +0100 User-Agent: KMail/1.8.2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511121400.02075.sebastien.bourdeauducq@gmail.com> Subject: Trigerring a taskqueue from the if_start routine crashes FreeBSD6 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Nov 2005 03:33:17 -0000 Hello, My 802.11 driver queues frames to send to the device in a tailq and then triggers a taskqueue to actually send them. The taskqueue is required because I need to do two USB transfers, and wait for the first one to complete before I start the second : doing this asynchronously would be a pain. This used to work fine under FreeBSD 5, but with 6, the system randomly freezes without any error message, and doesn't respond to anything else than the big red button. The crash seems more likely to happen when there are 3 or more frames in the tailq when the taskqueue runs. My code is online at http://svnweb.tuxfamily.org/listing.php?repname=p54u+%28prism54%29&path=%2F&sc=0 The taskqueue-related code is all in output_layer.c, and the interface with the 802.11 and network stack, from which the taskqueue is triggered, is in netif.c. The taskqueue is also trigerred from the thread created to bring the device up when it's detected, but it doesn't crash there (but the frames are queued one by one there). Any ideas ? Thanks, Sebastien From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 13 05:25:03 2005 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.org 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 8268316A420 for ; Sun, 13 Nov 2005 05:25:03 +0000 (GMT) (envelope-from dinesh@alphaque.com) Received: from ns2.alphaque.com (ns2.alphaque.com [202.75.47.153]) by mx1.FreeBSD.org (Postfix) with SMTP id 27EA043D4C for ; Sun, 13 Nov 2005 05:25:01 +0000 (GMT) (envelope-from dinesh@alphaque.com) Received: (qmail 39043 invoked by uid 0); 13 Nov 2005 05:25:00 -0000 Received: from lucifer.net-gw.com (HELO prophet.alphaque.com) (202.75.47.153) by lucifer.net-gw.com with SMTP; 13 Nov 2005 05:25:00 -0000 Received: from [127.0.0.1] (localhost [127.0.0.1]) by prophet.alphaque.com (8.13.4/8.13.4) with ESMTP id jAD5Lpsi001579; Sun, 13 Nov 2005 13:21:51 +0800 (MYT) (envelope-from dinesh@alphaque.com) Message-ID: <4376CD6E.4050803@alphaque.com> Date: Sun, 13 Nov 2005 13:21:50 +0800 From: Dinesh Nair User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8b) Gecko/20051026 MIME-Version: 1.0 To: Dinesh Nair References: <4375E7DA.1090204@alphaque.com> In-Reply-To: <4375E7DA.1090204@alphaque.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@FreeBSD.org, freebsd-questions@FreeBSD.org Subject: [patch] Re: Loading mfsroot read-write on FreeBSD 6.0-RELEASE X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Nov 2005 05:25:03 -0000 On 11/12/05 21:02 Dinesh Nair said the following: > how does one specify a read/write mount of mfsroot in 6.0 in the > bootloader ? apparently, the behaviour of vfs_mountroot_try() has changed in 6.0. previously, if the root filesystem was mounted from a memory disk, as would be the case with an mfsroot.gz, it would be mounted R/W while other fs types would be mounted R/O before /etc/rc scripts upgraded the mount to R/W. however, in 6.0, all root filesystems are mounted R/O. the following patch mounts all root filesystems R/W. it's a quick and dirty fix however, for a cleaner fix would be to duplicate 5.x behaviour of only mounting memory disks R/W and other disks R/O. the kernel needs to be rebuilt for this patch to take effect. is there enough interest in having memory root file systems mounted R/W at boot ? if there is, i could put in a little bit more effort into duplicating 5.x behaviour on this and submitting it as a PR to 6.0. --- CUT HERE --- --- sys/kern/vfs_mount.c.orig Sat Nov 12 23:22:07 2005 +++ sys/kern/vfs_mount.c Sat Nov 12 23:59:50 2005 @@ -1297,7 +1297,7 @@ strcpy(path, ROOTNAME); error = kernel_vmount( - MNT_RDONLY | MNT_ROOTFS, + MNT_ROOTFS, "fstype", vfsname, "fspath", "/", "from", path, --- CUT HERE --- -- Regards, /\_/\ "All dogs go to heaven." dinesh@alphaque.com (0 0) http://www.alphaque.com/ +==========================----oOO--(_)--OOo----==========================+ | for a in past present future; do | | for b in clients employers associates relatives neighbours pets; do | | echo "The opinions here in no way reflect the opinions of my $a $b." | | done; done | +=========================================================================+ From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 13 07:42:05 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 0405816A41F for ; Sun, 13 Nov 2005 07:42:05 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B84243D49 for ; Sun, 13 Nov 2005 07:42:04 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: by xproxy.gmail.com with SMTP id t13so993363wxc for ; Sat, 12 Nov 2005 23:42:03 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=qkmoL2xnQZXiFtG0ewT1qk1sXO+mWVpzN50KwOik3Oudnxk6A5+JVA9qyHpFZXaUpkZQbhvOH2OgaW1j0Sju+eUPiA+KVwjIkp7rkwxwHAlLLdC1Jm1wNuJ+dJ80oieR0nHBudXPa8q9lrXzuLVYsY+l/4dqi+XqtCyR6UVqCkg= Received: by 10.70.100.17 with SMTP id x17mr2656512wxb; Fri, 11 Nov 2005 21:35:20 -0800 (PST) Received: by 10.70.105.13 with HTTP; Fri, 11 Nov 2005 21:35:20 -0800 (PST) Message-ID: <84dead720511112135j435a3723ld15a9d993bbae9cc@mail.gmail.com> Date: Sat, 12 Nov 2005 11:05:20 +0530 From: Joseph Koshy To: freebsd MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: UFS2 max limits? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Nov 2005 07:42:05 -0000 The Wikipedia page referenced below says that UFS2 supports a filesystem size of 2^80 Bytes (1YiB) with the limit on a given file being 2^55 bytes (32 PiB). Are these numbers correct? I somehow remember the limits as being much lower (of the order of 16TB or so). http://en.wikipedia.org/wiki/Comparison_of_file_systems -- FreeBSD Volunteer, http://people.freebsd.org/~jkoshy From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 13 15:46:12 2005 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.org 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 4C1CC16A41F for ; Sun, 13 Nov 2005 15:46:12 +0000 (GMT) (envelope-from bland@FreeBSD.org) Received: from mvs3.plala.or.jp (c158131.vh.plala.or.jp [210.150.158.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id B12A543D55 for ; Sun, 13 Nov 2005 15:46:11 +0000 (GMT) (envelope-from bland@FreeBSD.org) Received: from hub.bbnest.net ([58.89.186.214]) by mvs3.plala.or.jp with ESMTP id <20051113154609.DBIX15688.mvs3.plala.or.jp@hub.bbnest.net>; Mon, 14 Nov 2005 00:46:09 +0900 Received: from [10.0.1.2] (egg.bbnest.net [10.0.1.2]) by hub.bbnest.net (8.13.4/8.13.4) with ESMTP id jADFk6vX001357 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 14 Nov 2005 00:46:09 +0900 (JST) (envelope-from bland@FreeBSD.org) Message-ID: <43775FBF.9050306@FreeBSD.org> Date: Mon, 14 Nov 2005 00:46:07 +0900 From: Alexander Nedotsukov User-Agent: Thunderbird 1.5 (Windows/20051025) MIME-Version: 1.0 To: "M. Warner Losh" References: <437309BD.7010704@FreeBSD.org> <20051111.093141.122160674.imp@bsdimp.com> In-Reply-To: <20051111.093141.122160674.imp@bsdimp.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@FreeBSD.org Subject: Re: No interrupts coming to device driver. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Nov 2005 15:46:12 -0000 Warner, Unfortunately my BIOS do not allow IRQ reservation for ISA devices. But in I noticed Interrupt Mode menu with PIC/APIC options. This pushed me to go through another round of tests. First with PIC mode and back again with APIC but now with "device apic" added to kernel config. After few attempts to use different IRQs I finally got interrupts on IRQ9. Well. This is good and I can move forward with driver. Though I still confused the way it done. I will be really appreciated if some good will explain me what is behind all this woodoo I did. Is it necessary to have "device apic" today? And still what is the nature of those ?lost in hardware? interrupts? BTW. Here is a quote from dmesg which may be connected to the case. ACPI APIC Table: ioapic0 irqs 0-23 on motherboard acpi0: Overriding SCI Interrupt from IRQ 9 to IRQ 20 Another bits of info. Windows automagically assigns IRQ7 to device and works fine. But I can not use IRQ7 on FreeBSD even with "device apic" in kernel. I do have hardware which is not in use ATM (PCI TV card). But I do not have any driver installed on Windows too. So if this is the case Windows somehow makes better guess of what driver can use. Anyway thanks everyone who tried to help! All the best, Alexander. M. Warner Losh wrote: > In message: <437309BD.7010704@FreeBSD.org> > Alexander Nedotsukov writes: > : I trying to create small lirc (www.lirc.org) compatible CIR driver for > : it8705 chip (sits on ISA bus). My problem is I can not get interrupts > : coming to driver. I believe I configured chip (carrier freq. + baudrate > : divisor) and enabled interrupt mode the same way it windows driver does. > : It also seems to be correct according to chip specs. But nothing. vmstat > : -i shows zeros for assigned irq. And my IRS stay cold. I wrote small > : userland program which polls CIRs IIR (interrupt identefication > : register) and it shows interrupt pending bit set on right after I press > : key on remote control. Looks like I missed something fundamental. Does > : anyone can give me a hint where to look? > > If it is on the ISA bus, then you can look at the IRQ line that you > are using for this card on the scope. Set it to trigger on an edge > (either falling if the signal is high or rising if the signal is low, > usually it is high). > > Make sure that the IRQ that you are using is not shared with anything > else, even hardware you aren't using. That's forbidden in the ISA > world (although some hacks exist to do interrupt sharing with two > devices on the ISA bus, (a) almost nobody does them and (b) they don't > work when sharing with pci). > > Make sure that the IRQ is set in the BIOS as Legacy/ISA rather than > ISAPNP/PCI (or some variants of those phrases). > > See if there's a way to force an interrupt on the chip by writing to a > register of some sort. It doesn't matter if you are going to use > this, but it will be good for testing. > > It almost certainly isn't an unacknowledged interrupt (unless it is > left over from before your chip reset). In my experience, those cause > vmstat of 1. It might be worth checking the chip initialization > sequence to make sure that you clear any possible interrupts AFTER > you've done the bus_setup_inter() call to register your interrupt > handler. > > That's all I can think of at the moment, but it should keep you busy > for a few hours :-) > > Warner > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 13 18:18:01 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 37DD416A41F for ; Sun, 13 Nov 2005 18:18:01 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id B0E7843D46 for ; Sun, 13 Nov 2005 18:18:00 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.3/8.13.3) with ESMTP id jADII0dr037345; Sun, 13 Nov 2005 10:18:00 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.3/8.13.3/Submit) id jADIHx9U037344; Sun, 13 Nov 2005 10:17:59 -0800 (PST) (envelope-from jmg) Date: Sun, 13 Nov 2005 10:17:59 -0800 From: John-Mark Gurney To: Joseph Koshy Message-ID: <20051113181759.GM775@funkthat.com> Mail-Followup-To: Joseph Koshy , freebsd References: <84dead720511112135j435a3723ld15a9d993bbae9cc@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <84dead720511112135j435a3723ld15a9d993bbae9cc@mail.gmail.com> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 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 Subject: Re: UFS2 max limits? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 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: Sun, 13 Nov 2005 18:18:01 -0000 Joseph Koshy wrote this message on Sat, Nov 12, 2005 at 11:05 +0530: > The Wikipedia page referenced below says that UFS2 supports a > filesystem size of 2^80 Bytes (1YiB) with the limit on a given > file being 2^55 bytes (32 PiB). Those sound correct, as UFS2 uses 64bit frag addresses, which when combined with a frag size of 16 (for 65536 bytes per frag) gives you 2^80 for total file system size.... as for the file size, The approximate max can be calculated by (blocksize / sizeof(ufs2_daddr_t)) ^ 3 * blocksize the real max would add in addition: (blocksize / sizeof(ufs2_daddr_t)) ^ 2 * blocksize + (blocksize / sizeof(ufs2_daddr_t)) * blocksize + 9 * blocksize so, with a blocksize of 65536, and ufs2_daddr_t's size being 8 bytes, you end up with: (2^16 / 2^3) ^ 3 * 2^16 (2^13)^3 * 2^16 2^(13*3) * 2^16 2^39 * 2^16 2^(39 + 16) 2^55 but if you add the additional blocks, you'll end up with larger, but not enough to go to 2^56 for file sizes... > Are these numbers correct? I somehow remember the limits as > being much lower (of the order of 16TB or so). You might be thinking of UFS1... Now there is a funny thing that I found out about UFS2 and UFS1... UFS1 supports larger file sizes (not file system sizes) due to the fact that the ufs_daddr_t is smaller (32bits), means it can get more out of the indirect blocks than UFS2 can... UFS1 can have files of 2^58 compared to UFS2's 2^55... -- 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 Sun Nov 13 18:25:02 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 ADC3416A41F for ; Sun, 13 Nov 2005 18:25:02 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 44D5C43D46 for ; Sun, 13 Nov 2005 18:25:02 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.3/8.13.3) with ESMTP id jADIP17r037616; Sun, 13 Nov 2005 10:25:01 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.3/8.13.3/Submit) id jADIP1uJ037615; Sun, 13 Nov 2005 10:25:01 -0800 (PST) (envelope-from jmg) Date: Sun, 13 Nov 2005 10:25:01 -0800 From: John-Mark Gurney To: Joseph Koshy , freebsd Message-ID: <20051113182501.GN775@funkthat.com> Mail-Followup-To: Joseph Koshy , freebsd References: <84dead720511112135j435a3723ld15a9d993bbae9cc@mail.gmail.com> <20051113181759.GM775@funkthat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051113181759.GM775@funkthat.com> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 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: Subject: Re: UFS2 max limits? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 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: Sun, 13 Nov 2005 18:25:02 -0000 John-Mark Gurney wrote this message on Sun, Nov 13, 2005 at 10:17 -0800: > as for the file size, The approximate max can be calculated by > (blocksize / sizeof(ufs2_daddr_t)) ^ 3 * blocksize > the real max would add in addition: > (blocksize / sizeof(ufs2_daddr_t)) ^ 2 * blocksize + > (blocksize / sizeof(ufs2_daddr_t)) * blocksize + > 9 * blocksize ^ ack, I miss remebered, I knew I needed to check this before I sent the email: !!grep define.*N[DI]ADDR /usr/include/ufs/ufs/dinode.h #define NDADDR 12 /* Direct addresses in inode. */ #define NIADDR 3 /* Indirect addresses in inode. */ The 9 above should be 12... -- 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 Sun Nov 13 20:25:56 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 EA6E316A41F for ; Sun, 13 Nov 2005 20:25:56 +0000 (GMT) (envelope-from SRS0=pW+Q+mi7=ZM=metro.cx=fbsd@sonologic.nl) Received: from mx1.sonologic.nl (mx1.sonologic.nl [82.94.245.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 38FE943D4C for ; Sun, 13 Nov 2005 20:25:55 +0000 (GMT) (envelope-from SRS0=pW+Q+mi7=ZM=metro.cx=fbsd@sonologic.nl) Received: from [10.1.4.2] (sonolo.xs4all.nl [80.126.206.91]) (authenticated bits=0) by mx1.sonologic.nl (8.13.3/8.13.3) with ESMTP id jADKPnhk062011; Sun, 13 Nov 2005 20:25:50 GMT Message-ID: <4377A15D.7060100@metro.cx> Date: Sun, 13 Nov 2005 21:26:05 +0100 From: Koen Martens Organization: Sonologic User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050317 Thunderbird/1.0.2 Mnenhy/0.7.2.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Koen Martens References: <20051112121343.94908.qmail@web60322.mail.yahoo.com> <43766A0A.9060105@metro.cx> In-Reply-To: <43766A0A.9060105@metro.cx> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Helo-Milter-Authen: gmc@sonologic.nl, fbsd@metro.cx, mx1 Received-SPF: pass (mx1.sonologic.nl: 80.126.206.91 is authenticated by a trusted mechanism) Cc: freebsd-hackers@freebsd.org, d c Subject: Re: SSH From within a Jail X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Nov 2005 20:25:57 -0000 Koen Martens wrote: > d c wrote: > >>Greetings: >> >>I currently am running Freebsd 6.0 Release. >> >>I am experimenting with jails and have run into a >>problem. I need to ssh from within my jail to another >>server. Actually I need to use scp. WHen I try it I >>get the error: "Host key verification failed." > > > This could also be something related to permissions on the .ssh > directory, but you cleared that out of the way if i understand the > rest of this thread correctly. I remember having this problem once, > but can't remember right now what i did to solve it.. I usually > compile openssh from source anyway, so you might try that. If that > works, it would probably be interesting to see what is the > difference between your own hand-rolled openssh and the one that > came with your world. Just remembered something else: do you jexec into the jail, or do you do a proper logon (eg. ssh into the jail). I think that if you jexec into the jail and then try to ssh, you might have a problem because you aren't really logged in to the jail and thus have no (psuedo) tty associated with your session.. Koen -- K.F.J. Martens, Sonologic, http://www.sonologic.nl/ Networking, hosting, embedded systems, unix, artificial intelligence. Public PGP key: http://www.metro.cx/pubkey-gmc.asc Wondering about the funny attachment your mail program can't read? Visit http://www.openpgp.org/ From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 13 23:14:12 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 0033B16A41F; Sun, 13 Nov 2005 23:14:11 +0000 (GMT) (envelope-from MTaylor@bytecraft.com.au) Received: from wolf.bytecraft.au.com (wolf.bytecraft.au.com [203.39.118.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id C0D0543D46; Sun, 13 Nov 2005 23:14:09 +0000 (GMT) (envelope-from MTaylor@bytecraft.com.au) Received: from localhost (localhost [127.0.0.1]) by wolf.bytecraft.au.com (8.12.11/8.12.11) with ESMTP id jADNE5nE002033; Mon, 14 Nov 2005 10:14:05 +1100 (EST) (envelope-from MTaylor@bytecraft.com.au) Received: from wolf.bytecraft.au.com ([127.0.0.1]) by localhost (wolf.bytecraft.au.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 01154-05-5; Mon, 14 Nov 2005 10:14:04 +1100 (EST) Received: from svmarshal.bytecraft.au.com ([10.0.0.4]) by wolf.bytecraft.au.com (8.12.11/8.12.11) with ESMTP id jADNDqC1001986; Mon, 14 Nov 2005 10:13:53 +1100 (EST) (envelope-from MTaylor@bytecraft.com.au) Received: from svmailmel.bytecraft.internal (Not Verified[10.0.0.24]) by svmarshal.bytecraft.au.com with MailMarshal (v5, 0, 3, 78) id ; Mon, 14 Nov 2005 10:13:52 +1100 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.5.7226.0 Date: Mon, 14 Nov 2005 10:13:51 +1100 Message-ID: <04E232FDCD9FBE43857F7066CAD3C0F1053F5E@svmailmel.bytecraft.internal> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Help: Asus P5WD2 mobo and ITE IDE controller problem Thread-Index: AcXop+jL30c+O3thTrC24ne6IWUdDw== From: "Murray Taylor" To: Cc: freebsd-hackers@freebsd.org Subject: Help: Asus P5WD2 mobo and ITE IDE controller problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Nov 2005 23:14:12 -0000 Hi all, I have had a system configured using this mobo and have hit a showstopper. The HDD (a seagate 330GB IDE) have been connected to the ITE IDE controller while the DVDrom has been connected to the primary IDE controller.=20 It seems that the ITE device is a RAID controller, and the BIOS and the 5.4 FreeBSD installer dont see the HDD at all. Which is not very useful! The mobo has a SATA port as well, and the question is Does 5.4 support SATA drives for install?=20 I think I can tell the BIOS to make a SATA drive 'look like' an IDE=20 drive. (sent to hackers also for this followup question) As a followup - Does anyone know of any support re the ITE device? CPU Intel Pentium 4 640 3.2Ghz 2MB 775 M/B Asus P5WD2 - Premium M/B Ram 2.048GB (2x-1.024GB) CL3.0 DDR2 533 HDD Seagate 300GB 7200RPM 8MB Optical Drive Pioneer 110-D 16 x DVD/RW Black w/NERO FDD 1.44MB Floppy Drive Black Tape Certance DDS5 Tape Drive SCSI Card Adaptec 19160 SCSI Card PSU 600Watt --=20 A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? Murray Taylor Bytecraft Systems P: +61 3 8710 2555 F: +61 3 8710 2599 D: +61 3 9238 4275 E: mtaylor@bytecraft.com.au --------------------------------------------------------------- The information transmitted in this e-mail is for the exclusive use of the intended addressee and may contain confidential and/or privileged material. Any review, re-transmission, dissemination or other use of it, or the taking of any action in reliance upon this information by persons and/or entities other than the intended recipient is prohibited. If you received this in error, please inform the sender and/or addressee immediately and delete the material.=20 E-mails may not be secure, may contain computer viruses and may be corrupted in transmission. Please carefully check this e-mail (and any attachment) accordingly. No warranties are given and no liability is accepted for any loss or damage caused by such matters. --------------------------------------------------------------- ***This Email has been scanned for Viruses by MailMarshal.*** From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 13 23:37:42 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 E4BD416A41F; Sun, 13 Nov 2005 23:37:42 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from smtp-vbr4.xs4all.nl (smtp-vbr4.xs4all.nl [194.109.24.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 420E343D45; Sun, 13 Nov 2005 23:37:42 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr4.xs4all.nl (8.13.3/8.13.3) with ESMTP id jADNbZ6f059912; Mon, 14 Nov 2005 00:37:36 +0100 (CET) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id A236CB822; Mon, 14 Nov 2005 00:37:35 +0100 (CET) Date: Mon, 14 Nov 2005 00:37:35 +0100 From: Roland Smith To: Murray Taylor Message-ID: <20051113233735.GC18557@slackbox.xs4all.nl> Mail-Followup-To: Murray Taylor , freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org References: <04E232FDCD9FBE43857F7066CAD3C0F1053F5E@svmailmel.bytecraft.internal> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="TYecfFk8j8mZq+dy" Content-Disposition: inline In-Reply-To: <04E232FDCD9FBE43857F7066CAD3C0F1053F5E@svmailmel.bytecraft.internal> User-Agent: Mutt/1.4.2.1i X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 X-GPG-Key: http://www.xs4all.nl/~rsmith/pubkey.txt X-GPG-Notice: If this message is not signed, don't assume I sent it! X-Virus-Scanned: by XS4ALL Virus Scanner X-Mailman-Approved-At: Sun, 13 Nov 2005 23:56:36 +0000 Cc: freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Help: Asus P5WD2 mobo and ITE IDE controller problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Nov 2005 23:37:43 -0000 --TYecfFk8j8mZq+dy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Nov 14, 2005 at 10:13:51AM +1100, Murray Taylor wrote: > Hi all, >=20 > I have had a system configured using this mobo and have hit a > showstopper. >=20 > The HDD (a seagate 330GB IDE) have been connected to the ITE IDE > controller > while the DVDrom has been connected to the primary IDE controller.=20 >=20 > It seems that the ITE device is a RAID controller, and the BIOS and > the 5.4 FreeBSD installer dont see the HDD at all. Which is not very > useful! The ASUS site doesn't mention what type the ITE controller is. According to the ata(4) manual page, only the IT8211F and IT8212F are supported. But according to the motherboard layout drawing in the manual, it is indeed a IT8211F, so it should be supported. Are you sure it is enabled? > The mobo has a SATA port as well, and the question is >=20 > Does 5.4 support SATA drives for install?=20 Yes. Roland --=20 R.F.Smith (http://www.xs4all.nl/~rsmith/) Please send e-mail as plain text. public key: http://www.xs4all.nl/~rsmith/pubkey.txt --TYecfFk8j8mZq+dy Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDd84/EnfvsMMhpyURAlcHAJ9ZnzjD2iNBNJfh9xBagUS+K80lHACggq9w xkpaMWQnItYFpk1PS+mci3g= =ZlPs -----END PGP SIGNATURE----- --TYecfFk8j8mZq+dy-- From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 13 23:59:18 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 80F8816A41F; Sun, 13 Nov 2005 23:59:18 +0000 (GMT) (envelope-from MTaylor@bytecraft.com.au) Received: from wolf.bytecraft.au.com (wolf.bytecraft.au.com [203.39.118.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id F29FB43D72; Sun, 13 Nov 2005 23:59:09 +0000 (GMT) (envelope-from MTaylor@bytecraft.com.au) Received: from localhost (localhost [127.0.0.1]) by wolf.bytecraft.au.com (8.12.11/8.12.11) with ESMTP id jADNx4Zn004203; Mon, 14 Nov 2005 10:59:04 +1100 (EST) (envelope-from MTaylor@bytecraft.com.au) Received: from wolf.bytecraft.au.com ([127.0.0.1]) by localhost (wolf.bytecraft.au.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 03708-02-5; Mon, 14 Nov 2005 10:59:03 +1100 (EST) Received: from svmarshal.bytecraft.au.com ([10.0.0.4]) by wolf.bytecraft.au.com (8.12.11/8.12.11) with ESMTP id jADNwqfW004159; Mon, 14 Nov 2005 10:58:52 +1100 (EST) (envelope-from MTaylor@bytecraft.com.au) Received: from svmailmel.bytecraft.internal (Not Verified[10.0.0.24]) by svmarshal.bytecraft.au.com with MailMarshal (v5, 0, 3, 78) id ; Mon, 14 Nov 2005 10:58:52 +1100 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.5.7226.0 Date: Mon, 14 Nov 2005 10:58:51 +1100 Message-ID: <04E232FDCD9FBE43857F7066CAD3C0F1053F6C@svmailmel.bytecraft.internal> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Help: Asus P5WD2 mobo and ITE IDE controller problem Thread-Index: AcXoq0oHGyVNqtCyS7esw66NKtqSmgAAiZ7g From: "Murray Taylor" To: "Roland Smith" Cc: freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org Subject: RE: Help: Asus P5WD2 mobo and ITE IDE controller problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Nov 2005 23:59:18 -0000 > -----Original Message----- > From: Roland Smith [mailto:rsmith@xs4all.nl]=20 >=20 > On Mon, Nov 14, 2005 at 10:13:51AM +1100, Murray Taylor wrote: > > Hi all, > >=20 > > I have had a system configured using this mobo and have hit a > > showstopper. > >=20 > > The HDD (a seagate 330GB IDE) have been connected to the ITE IDE > > controller > > while the DVDrom has been connected to the primary IDE controller.=20 > >=20 > > It seems that the ITE device is a RAID controller, and the BIOS and > > the 5.4 FreeBSD installer dont see the HDD at all. Which=20 > > is not very useful! >=20 > The ASUS site doesn't mention what type the ITE controller=20 > is. According > to the ata(4) manual page, only the IT8211F and IT8212F are supported. >=20 > But according to the motherboard layout drawing in the manual, it is > indeed a IT8211F, so it should be supported. Are you sure it=20 > is enabled? >=20 I believe that it is 'enabled' in that there is a momentary flash of the ITE scanning and I think the disk is found as I reckon I can catch something like this ??? 0: ST3300???? UDMA? ??? 1: ??? 2: ??? 3: where the ? are characters I havent caught. But it never appears in the BIOS report. And the installer certainly=20 doesnt talk to it at all. > > The mobo has a SATA port as well, and the question is > >=20 > > Does 5.4 support SATA drives for install?=20 >=20 > Yes. >=20 > Roland > --=20 mjt --------------------------------------------------------------- The information transmitted in this e-mail is for the exclusive use of the intended addressee and may contain confidential and/or privileged material. Any review, re-transmission, dissemination or other use of it, or the taking of any action in reliance upon this information by persons and/or entities other than the intended recipient is prohibited. If you received this in error, please inform the sender and/or addressee immediately and delete the material.=20 E-mails may not be secure, may contain computer viruses and may be corrupted in transmission. Please carefully check this e-mail (and any attachment) accordingly. No warranties are given and no liability is accepted for any loss or damage caused by such matters. --------------------------------------------------------------- ***This Email has been scanned for Viruses by MailMarshal.*** From owner-freebsd-hackers@FreeBSD.ORG Mon Nov 14 02:32:17 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 2C32A16A41F for ; Mon, 14 Nov 2005 02:32:17 +0000 (GMT) (envelope-from pyunyh@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 39D6E43D45 for ; Mon, 14 Nov 2005 02:32:16 +0000 (GMT) (envelope-from pyunyh@gmail.com) Received: by zproxy.gmail.com with SMTP id 9so608795nzo for ; Sun, 13 Nov 2005 18:32:15 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=nu0fVQU7j2q0K7VMBD8yyOnF3fCau6HBqtIbNtnk1NNL2HQTAiAfg/4aqh9f/ITUpavOGblJUWJjlIKXFMT8+q66JsHZkfIQ5rinDx2BPSQm+BPaQuXok++O+f7B5dXay4ih20b/Gt+xDXYmMEChD/jqT2ae+AplyD/SNVd6zAU= Received: by 10.36.109.16 with SMTP id h16mr1446928nzc; Sun, 13 Nov 2005 18:32:15 -0800 (PST) Received: from michelle.rndsoft.co.kr ( [211.32.202.217]) by mx.gmail.com with ESMTP id 18sm1817002nzo.2005.11.13.18.32.11; Sun, 13 Nov 2005 18:32:15 -0800 (PST) Received: from michelle.rndsoft.co.kr (localhost.rndsoft.co.kr [127.0.0.1]) by michelle.rndsoft.co.kr (8.13.1/8.13.1) with ESMTP id jAE2U3v5001605 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 14 Nov 2005 11:30:03 +0900 (KST) (envelope-from yongari@gmail.com) Received: (from yongari@localhost) by michelle.rndsoft.co.kr (8.13.1/8.13.1/Submit) id jAE2U0LZ001604; Mon, 14 Nov 2005 11:30:00 +0900 (KST) (envelope-from yongari@gmail.com) Date: Mon, 14 Nov 2005 11:30:00 +0900 From: Pyun YongHyeon To: "Matthew D. Fuller" Message-ID: <20051114023000.GB800@rndsoft.co.kr> References: <20051112071815.GD18405@rndsoft.co.kr> <20051112073711.GE39882@cirb503493.alcatel.com.au> <20051112074418.GE18405@rndsoft.co.kr> <20051112161422.GB1485@over-yonder.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051112161422.GB1485@over-yonder.net> User-Agent: Mutt/1.4.2.1i Cc: Peter Jeremy , freebsd-hackers@freebsd.org Subject: Re: poor fdc(4) performance X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2005 02:32:17 -0000 On Sat, Nov 12, 2005 at 10:14:22AM -0600, Matthew D. Fuller wrote: > On Sat, Nov 12, 2005 at 04:44:18PM +0900 I heard the voice of > Pyun YongHyeon, and lo! it spake thus: > > > > Yes, it could be. But I think the machine is fast enough to read > > sequential blocks. > > Try running it without SMP. There may be enough happening in the MP > locking bit that you end up falling behind. I remember noticing crap > fdc performance (without larger block sizes) on my dual PPro a little > while back. > Hmm, I think this is not the case as interrupt handler on fdc was registered with FAST handler. In addition, the handler just invokes wakeup(9), without any lock operations, to wake up kernel floppy worker thread. Note, I see the same issue on UP sparc64 too. -- Regards, Pyun YongHyeon From owner-freebsd-hackers@FreeBSD.ORG Mon Nov 14 12:31:51 2005 Return-Path: X-Original-To: hackers@freebsd.org 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 794FD16A41F; Mon, 14 Nov 2005 12:31:51 +0000 (GMT) (envelope-from stijn@pcwin002.win.tue.nl) Received: from kweetal.tue.nl (kweetal.tue.nl [131.155.3.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD2EE43D4C; Mon, 14 Nov 2005 12:31:50 +0000 (GMT) (envelope-from stijn@pcwin002.win.tue.nl) Received: from localhost (localhost [127.0.0.1]) by kweetal.tue.nl (Postfix) with ESMTP id D78BB13B6F8; Mon, 14 Nov 2005 13:31:49 +0100 (CET) Received: from kweetal.tue.nl ([127.0.0.1]) by localhost (kweetal.tue.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 75557-01-8; Mon, 14 Nov 2005 13:31:31 +0100 (CET) Received: from umta.win.tue.nl (umta.win.tue.nl [131.155.71.100]) by kweetal.tue.nl (Postfix) with ESMTP id 297CA13B788; Mon, 14 Nov 2005 13:30:53 +0100 (CET) Received: from pcwin002.win.tue.nl (pcwin002 [131.155.71.72]) by umta.win.tue.nl (Postfix) with ESMTP id 2445431401C; Mon, 14 Nov 2005 13:30:53 +0100 (CET) Received: by pcwin002.win.tue.nl (Postfix, from userid 1001) id 0EC9140BE; Mon, 14 Nov 2005 13:30:53 +0100 (CET) Date: Mon, 14 Nov 2005 13:30:53 +0100 From: Stijn Hoop To: Harti Brandt Message-ID: <20051114123052.GG69544@pcwin002.win.tue.nl> References: <20051021160017.D4007@beagle.kn.op.dlr.de> <20051021141752.GQ6916@pcwin002.win.tue.nl> <20051021170843.A6955@beagle.kn.op.dlr.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="MdJ3p2aQbVp3YFXz" Content-Disposition: inline In-Reply-To: <20051021170843.A6955@beagle.kn.op.dlr.de> User-Agent: Mutt/1.4.2.1i X-Bright-Idea: Let's abolish HTML mail! X-Virus-Scanned: amavisd-new at tue.nl Cc: hackers@freebsd.org Subject: Re: telnetd/sshd and Kerberos tickets (PAM) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2005 12:31:51 -0000 --MdJ3p2aQbVp3YFXz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Oct 21, 2005 at 05:10:39PM +0200, Harti Brandt wrote: > On Fri, 21 Oct 2005, Stijn Hoop wrote: > SH>On Fri, Oct 21, 2005 at 04:08:14PM +0200, Harti Brandt wrote: > SH>> I have enabled the pam_krb5 module in pam.d/{login,telnetd,sshd}. Wh= en=20 > SH>> login in locally I get a Kerberos ticket as I would expect. When log= ging=20 > SH>> in via ssh or telnet I don't get one. I have digged around in the so= urces=20 > SH>> and it locks like telnetd never calls pam_setcred() which would do t= his=20 > SH>> work. My PAM-foo is rather limited so my question is: shouldn't sshd= and=20 > SH>> telnetd call pam_setcred() somewhere? > SH> > SH>WRT sshd I bugged des@ about this but did not receive an answer :( See > SH>the attached mail. >=20 > Hmm. I digged around a little bit and found something: >=20 > http://bugzilla.mindrot.org/show_bug.cgi?id=3D789 >=20 > From a first glance it seems that this bug was introduced by fixing=20 > another bug. I see. If I understand correctly, disabling privsep will fix it? Still, I would really like to get an answer to my PAM question: "Is it allowed for an application to only call pam_setcred with the PAM_REINITIALIZE_FLAG, while never having called it with PAM_ESTABLISH_CRED= ?" Did you find out yet? --Stijn --=20 "An adult is a child who has more ethics and morals, that's all." -- Shigeru Miyamoto --MdJ3p2aQbVp3YFXz Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDeIN8Y3r/tLQmfWcRAkWUAJ9LsJ+u3XeV3seJVfbXAMPnpIQN0gCgqL82 XYJpEeMsGKTCuKrzYt9Gtmc= =xpSz -----END PGP SIGNATURE----- --MdJ3p2aQbVp3YFXz-- From owner-freebsd-hackers@FreeBSD.ORG Mon Nov 14 13:35:51 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 3A81616A41F for ; Mon, 14 Nov 2005 13:35:51 +0000 (GMT) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6C41C43D46 for ; Mon, 14 Nov 2005 13:35:48 +0000 (GMT) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 4E49952D5E; Mon, 14 Nov 2005 14:35:45 +0100 (CET) Received: from localhost (pjd.wheel.pl [10.0.1.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 9A9B652D60; Mon, 14 Nov 2005 14:35:35 +0100 (CET) Date: Mon, 14 Nov 2005 14:35:20 +0100 From: Pawel Jakub Dawidek To: Koen Martens Message-ID: <20051114133520.GA42544@garage.freebsd.pl> References: <20051112121343.94908.qmail@web60322.mail.yahoo.com> <43766A0A.9060105@metro.cx> <4377A15D.7060100@metro.cx> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="tKW2IUtsqtDRztdT" Content-Disposition: inline In-Reply-To: <4377A15D.7060100@metro.cx> X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r535 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-5.9 required=3.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-hackers@freebsd.org, d c Subject: Re: SSH From within a Jail X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2005 13:35:51 -0000 --tKW2IUtsqtDRztdT Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Nov 13, 2005 at 09:26:05PM +0100, Koen Martens wrote: +> Just remembered something else: do you jexec into the jail, or do +> you do a proper logon (eg. ssh into the jail). I think that if you +> jexec into the jail and then try to ssh, you might have a problem +> because you aren't really logged in to the jail and thus have no +> (psuedo) tty associated with your session.. I just saw this thread. Yes, you are right, I can confirm this. To be able to ssh to another server from within a jail, you need to log in to the jail properly (have access to your terminal), so jexec won't work here. Try to ssh into the jail and then ssh to another box. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --tKW2IUtsqtDRztdT Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDeJKYForvXbEpPzQRAlwhAKCpl19T6GIGqC44Ks1ZIr5lLNYmpQCgzVu6 DjQa4y7DeqqnitYu8g2RaEo= =kym1 -----END PGP SIGNATURE----- --tKW2IUtsqtDRztdT-- From owner-freebsd-hackers@FreeBSD.ORG Mon Nov 14 16:11:54 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 6860A16A41F for ; Mon, 14 Nov 2005 16:11:54 +0000 (GMT) (envelope-from matthew@digitalstratum.com) Received: from mail.mundomateo.com (static-24-56-193-117.chrlmi.cablespeed.com [24.56.193.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id D8F2F43D55 for ; Mon, 14 Nov 2005 16:11:53 +0000 (GMT) (envelope-from matthew@digitalstratum.com) Received: from [10.0.81.12] (ws12.mundomateo.com [10.0.81.12]) by mail.mundomateo.com (Postfix) with ESMTP id 1AEED5CA1 for ; Mon, 14 Nov 2005 11:11:52 -0500 (EST) Message-ID: <4378B743.7070702@digitalstratum.com> Date: Mon, 14 Nov 2005 11:11:47 -0500 From: Matthew Hagerty Organization: Digital Stratum User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) 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 Subject: Modifying code using ata_cmd to FBSD 6.0-Release X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: matthew@digitalstratum.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2005 16:11:54 -0000 Greetings, I'm trying to use a AoE (ata over ethernet) EtherDrive (from coraid.com), but their "FreeBSD 6.0" kernel patch seems to have been developed against 6.0 early on, or they just renamed the 5.x patch and hoped no one would notice. Needless to say, the patch fails to compile because they are using the ata_cmd struct, which seems to have been totally rewritten in 6.0. I don't know very much about kernel hacking (yet) and I'm hoping to be able to just replace some structure references and a few defines and get things working. My initial problems are trying to find references to tie all this together. I cannot seem to find much documentation on GEOM or how to add new 'services' (correct term?) to the kernel, hence my post here for help. I have isolated the parts of the patch that seem to reference the old struct, listed below. I looked at the old ata_cmd struct (from a 5.4 install) and found a new ata_ioc_request struct that seems to contain almost all the members (that I need) that were used from the old ata_cmd struct, so is it feasible that I can simply re-cast against ata_ioc_request and change the references? Here are the members that are currently used: struct ata_cmd *iocmd; iocmd->cmd iocmd->u.request.count iocmd->u.request.data iocmd->u.request.u.ata.count iocmd->u.request.u.ata.command iocmd->u.request.u.ata.feature iocmd->u.request.timeout iocmd->u.request.u.ata.lba The only reference that is not in ata_ioc_request is the 'cmd' member, which is used in the code like this: if (iocmd->cmd != ATAREQUEST) { Which leads me to the other problem I'm having. Two defines are used that I cannot reliably find a replacement for: IOCATA ATAREQUEST I did find a IOCATAREQUEST that could maybe be the replacement for ATAREQUEST? But as for IOCATA, I can find nothing that seem cut and dry. Last, the function that uses the ata_cmd struct the most (there is one other, but it does nothing new) seems to be called by GEOM? The only reference to the function call is while creating a new disk with disk_create(), like this: struct disk *disk; ... disk = disk_alloc(); ... disk->d_ioctl = aoeblk_ioctl; ... disk_create(disk, DISK_VERSION_00); What I can't find is where GEOM defines the prototypes for the functions it can call (d_open, d_close, d_strategy, d_ioctl, d_dump), but the prototype for the aoeblk_ioctl() function has the ata_cmd struct passed in as a void pointer and casts it to ata_cmd... So how do I know what kind of data the GEOM system is passing the function for any given call? I see there is a 'cmd' parameter (unrelated to the above ioctl->cmd), but without docs for each of the the disk_create() support functions, I can't really tell how to use it. I've included (for reference) the two main functions below that I need to modify. Any insight would be greatly appreciated as to how I can proceed with the modifications, or where I can get more documentation about the ata.h changes, disk_create() function prototypes, etc.. Thank you, Matthew /* * Ioctl only for select smartmontools ata commands. * We fake out the ATAREQUEST ata ioctl -- ugly, but effective. */ static int aoeblk_ioctl(struct disk *disk, ulong cmd, void *vp, int flag, struct thread *td) { struct ata_cmd *iocmd; Aoedev *d; int n; if (cmd != IOCATA) { log(LOG_INFO, "aoe: aoeblk_ioctl: cmd %ld not IOCATA.\n", cmd); return ENOTTY; } iocmd = (struct ata_cmd *) vp; if (iocmd == NULL) { log(LOG_INFO, "aoe: aoeblk_ioctl: NULL arg ptr.\n"); return EINVAL; } if (iocmd->cmd != ATAREQUEST) { log(LOG_INFO, "aoe: aoeblk_ioctl: unknown iocmd->cmd=%d\n", iocmd->cmd); return ENOTTY; } if (iocmd->u.request.count) { if (iocmd->u.request.data == NULL) { log(LOG_INFO, "aoe: aoeblk_ioctl: null return data pointer\n"); return EINVAL; } iocmd->u.request.count = 512; iocmd->u.request.u.ata.count = 1; } d = disk->d_drv1; mtx_lock(&d->mtx); if ((d->flags & DEVFL_UP) == 0) { log(LOG_INFO, "aoe: aoeblk_ioctl: device for unit %ld is not up.\n", d->unit); mtx_unlock(&d->mtx); return ENXIO; } switch (iocmd->u.request.u.ata.command) { case ATA_ATA_IDENTIFY: copyout(d->ident, iocmd->u.request.data, sizeof d->ident); mtx_unlock(&d->mtx); return 0; case ATA_SMART: if (iocmd->u.request.u.ata.feature != ATA_SMART_ATTR_AUTOSAVE) { n = aoecmd_ata_smart(d, iocmd); mtx_unlock(&d->mtx); return n; } default: mtx_unlock(&d->mtx); log(LOG_INFO, "aoe: aoeblk_ioctl: unallowed ata command; " "cmd=%2.2X feat=%2.2X.\n", iocmd->u.request.u.ata.command, iocmd->u.request.u.ata.feature); return EINVAL; } } static void disk_create_task(void *ctx, int useless) { struct disk *disk; Aoedev *d; d = (Aoedev *) ctx; disk = disk_alloc(); /* Disk_destroy triggers freeing the allocated disk. */ if (disk == NULL) { log(LOG_INFO, "aoe: disk_create_task: cannot alloc disk structure.\n"); mtx_lock(&d->mtx); d->flags &= ~DEVFL_TASKON; mtx_unlock(&d->mtx); return; } d->disk = disk; disk->d_drv1 = d; disk->d_maxsize = DFLTPHYS; disk->d_sectorsize = DEV_BSIZE; disk->d_mediasize = DEV_BSIZE * d->nsectors; disk->d_unit = d->unit; disk->d_name = "aoed"; disk->d_open = aoeblk_open; disk->d_close = aoeblk_close; disk->d_ioctl = aoeblk_ioctl; disk->d_strategy = aoeblk_strategy; disk_create(disk, DISK_VERSION_00); mtx_lock(&d->mtx); d->flags &= ~DEVFL_TASKON; d->flags |= DEVFL_UP; mtx_unlock(&d->mtx); } From owner-freebsd-hackers@FreeBSD.ORG Mon Nov 14 17:04:11 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 51C8A16A41F; Mon, 14 Nov 2005 17:04:11 +0000 (GMT) (envelope-from babkin@verizon.net) Received: from vms042pub.verizon.net (vms042pub.verizon.net [206.46.252.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 17D9C43D53; Mon, 14 Nov 2005 17:04:11 +0000 (GMT) (envelope-from babkin@verizon.net) Received: from vms070.mailsrvcs.net ([192.168.1.3]) by vms042.mailsrvcs.net (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPA id <0IPY005YCFEYN8J0@vms042.mailsrvcs.net>; Mon, 14 Nov 2005 11:04:10 -0600 (CST) Date: Mon, 14 Nov 2005 11:04:10 -0600 (CST) From: Sergey Babkin To: Pawel Jakub Dawidek , Koen Martens Message-id: <14758607.1131987850677.JavaMail.root@vms070.mailsrvcs.net> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Mailman-Approved-At: Mon, 14 Nov 2005 17:09:34 +0000 Cc: freebsd-hackers@freebsd.org, d c Subject: Re: Re: SSH From within a Jail X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: babkin@users.sf.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2005 17:04:11 -0000 >From: Pawel Jakub Dawidek >On Sun, Nov 13, 2005 at 09:26:05PM +0100, Koen Martens wrote: >+> Just remembered something else: do you jexec into the jail, or do >+> you do a proper logon (eg. ssh into the jail). I think that if you >+> jexec into the jail and then try to ssh, you might have a problem >+> because you aren't really logged in to the jail and thus have no >+> (psuedo) tty associated with your session.. > >I just saw this thread. Yes, you are right, I can confirm this. >To be able to ssh to another server from within a jail, you need to >log in to the jail properly (have access to your terminal), so >jexec won't work here. >Try to ssh into the jail and then ssh to another box. "ssh -n" can work without a tty. Though I'm not sure what was the question, I did not watch this thread from the start. -SB From owner-freebsd-hackers@FreeBSD.ORG Mon Nov 14 17:23:16 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 7881216A41F for ; Mon, 14 Nov 2005 17:23:16 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (66-23-216-219.clients.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id F186643D46 for ; Mon, 14 Nov 2005 17:23:15 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 1948898 for multiple; Mon, 14 Nov 2005 12:23:02 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jAEHMmcn079034; Mon, 14 Nov 2005 12:22:50 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Mon, 14 Nov 2005 12:19:48 -0500 User-Agent: KMail/1.8.2 References: <200511121400.02075.sebastien.bourdeauducq@gmail.com> In-Reply-To: <200511121400.02075.sebastien.bourdeauducq@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511141219.49573.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: Sebastien Subject: Re: Trigerring a taskqueue from the if_start routine crashes FreeBSD6 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2005 17:23:16 -0000 On Saturday 12 November 2005 08:00 am, Sebastien wrote: > Hello, > > My 802.11 driver queues frames to send to the device in a tailq and then > triggers a taskqueue to actually send them. The taskqueue is required > because I need to do two USB transfers, and wait for the first one to > complete before I start the second : doing this asynchronously would be a > pain. > > This used to work fine under FreeBSD 5, but with 6, the system randomly > freezes without any error message, and doesn't respond to anything else > than the big red button. The crash seems more likely to happen when there > are 3 or more frames in the tailq when the taskqueue runs. > > My code is online at > http://svnweb.tuxfamily.org/listing.php?repname=p54u+%28prism54%29&path=%2F >&sc=0 > > The taskqueue-related code is all in output_layer.c, and the interface with > the 802.11 and network stack, from which the taskqueue is triggered, is in > netif.c. > > The taskqueue is also trigerred from the thread created to bring the device > up when it's detected, but it doesn't crash there (but the frames are > queued one by one there). > > Any ideas ? I don't see anything in output_layer.c Note that it's ok to hold locks over a call to free() so that your output_free() routine could be simplified somewhat: mtx_lock(&sc->output_lock); while (!TAILQ_EMPTY(&sc->output_queue) { bf = TAILQ_FIRST(&sc->output_queue); TAILQ_REMOVE(&sc->output_queue, bf, bf_list); m_freem(bf->m); free(bf, M_USBDEV); } mtx_destroy(&sc->output_lock); but that is just a suggestion, I don't think it would affect your problem. Are you able to add KDB into your kernel and break into the debugger when the machine hangs (either via Ctrl-Alt-Esc or via a serial break over a serial console)? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-hackers@FreeBSD.ORG Mon Nov 14 20:39:23 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 320DB16A41F for ; Mon, 14 Nov 2005 20:39:23 +0000 (GMT) (envelope-from John.Giacomoni@colorado.edu) Received: from serl.cs.colorado.edu (serl.cs.colorado.edu [128.138.207.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id BDA0743D49 for ; Mon, 14 Nov 2005 20:39:22 +0000 (GMT) (envelope-from John.Giacomoni@colorado.edu) Received: from [IPv6???1] (localhost [127.0.0.1]) by serl.cs.colorado.edu (Postfix) with ESMTP id 922907B0B22 for ; Mon, 14 Nov 2005 13:40:12 -0700 (MST) Mime-Version: 1.0 (Apple Message framework v746.2) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; format=flowed To: freebsd-hackers@freebsd.org From: John Giacomoni Date: Mon, 14 Nov 2005 13:39:19 -0700 X-Mailer: Apple Mail (2.746.2) Subject: Sharing the same VM address space between Kernel and UserSpace X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2005 20:39:23 -0000 I am in need of a way to share memory between kernel space and possibly multiple different user-space processes for an extended period of time. This memory would need to be a single unpageable region. I am using the vm routines as cribbed from mmap, however I'd like the address spaces to be viewed as the same regardless of which process I'm in to avoid swizzling pointers as I'm storing data structures in the shared memory region. I imagine I'd need to find a way to expose part of the kernel address space to user space to accomplish this. Is there a way to do this? thanks John G -- John.Giacomoni@colorado.edu University of Colorado at Boulder Department of Computer Science Engineering Center, ECCR 1B05 430 UCB Boulder, CO 80303-0430 USA From owner-freebsd-hackers@FreeBSD.ORG Mon Nov 14 20:57:15 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 D728316A420 for ; Mon, 14 Nov 2005 20:57:15 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 337E943D46 for ; Mon, 14 Nov 2005 20:57:15 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jAEKvAeC061924; Mon, 14 Nov 2005 13:57:10 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <4378FA26.8040604@samsco.org> Date: Mon, 14 Nov 2005 13:57:10 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Giacomoni References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: freebsd-hackers@freebsd.org Subject: Re: Sharing the same VM address space between Kernel and UserSpace X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2005 20:57:16 -0000 John Giacomoni wrote: > I am in need of a way to share memory between kernel space and possibly > multiple different user-space processes for an extended period of time. > This memory would need to be a single unpageable region. > > I am using the vm routines as cribbed from mmap, however I'd like the > address spaces to be viewed as the same regardless of which process I'm > in to avoid swizzling pointers as I'm storing data structures in the > shared memory region. > > I imagine I'd need to find a way to expose part of the kernel address > space to user space to accomplish this. > > Is there a way to do this? > > thanks > > John G > If you get this working then it'll be very useful for the syspage support that was talked about recently. The kernel can access addresses in the user space so long as they are wired and won't cause a fault. Thus I imagine that you only need to allocate the memory, wire it, mark it with the appropriate page permissions, and reserve a user address range for it in the process map. I'd look at the process exec path in the kernel for places to hook in. The only other trick then is how to let the user process know the address for this magic region. An easy way would be to store it in a sysctl that can be read at runtime. A harder way would be to have the kernel dummy up an elf segment in the image activator code that the dynamic linker could read and put into a global variable for the program to access. Scott From owner-freebsd-hackers@FreeBSD.ORG Mon Nov 14 22:28:52 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 52C1416A420 for ; Mon, 14 Nov 2005 22:28:52 +0000 (GMT) (envelope-from John.Giacomoni@colorado.edu) Received: from serl.cs.colorado.edu (serl.cs.colorado.edu [128.138.207.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id A448B43D46 for ; Mon, 14 Nov 2005 22:28:51 +0000 (GMT) (envelope-from John.Giacomoni@colorado.edu) Received: from [IPv6???1] (localhost [127.0.0.1]) by serl.cs.colorado.edu (Postfix) with ESMTP id 4D0BA7B0B21 for ; Mon, 14 Nov 2005 15:29:42 -0700 (MST) Mime-Version: 1.0 (Apple Message framework v746.2) In-Reply-To: <4378FA26.8040604@samsco.org> References: <4378FA26.8040604@samsco.org> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: John Giacomoni Date: Mon, 14 Nov 2005 15:28:47 -0700 To: freebsd-hackers@freebsd.org X-Mailer: Apple Mail (2.746.2) Subject: Re: Sharing the same VM address space between Kernel and UserSpace X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2005 22:28:52 -0000 On Nov 14, 2005, at 1:57 PM, Scott Long wrote: > John Giacomoni wrote: > >> I am in need of a way to share memory between kernel space and >> possibly >> multiple different user-space processes for an extended period of >> time. >> This memory would need to be a single unpageable region. >> I am using the vm routines as cribbed from mmap, however I'd like the >> address spaces to be viewed as the same regardless of which >> process I'm >> in to avoid swizzling pointers as I'm storing data structures in the >> shared memory region. >> I imagine I'd need to find a way to expose part of the kernel address >> space to user space to accomplish this. >> Is there a way to do this? >> thanks >> John G > > If you get this working then it'll be very useful for the syspage > support that was talked about recently. > > The kernel can access addresses in the user space so long as they > are wired and won't cause a fault. Thus I imagine that you > only need to allocate the memory, wire it, mark it with the > appropriate > page permissions, and reserve a user address range for it in the > process map. I'd look at the process exec path in the kernel for > places to hook in. The only other trick then is how to let the user > process know the address for this magic region. An easy way would be > to store it in a sysctl that can be read at runtime. A harder way > would > be to have the kernel dummy up an elf segment in the image activator > code that the dynamic linker could read and put into a global variable > for the program to access. > > Scott > Which thread/list was the syspage support discussed? (I did a quick search in my freebsd-hackers mailbox and didn't find it) As for my problem I'm not sure that the kernel being able to access userpages is quite what is needed. The first reason is that if there are two processes trying to map the same region it would be problematic if one of them had allocated something in the same area of the heap as the shared memory region resides. This suggests that to avoid swizzling the region needs to be in an address region where the user-space processes will never allocate in (kernel). The other reason is that the kernel code needs to be able to function using the shared memory without a user-space process being attached at all times. So the question is, is it possible to mark wired kernel pages as being accessible to a user-space process without triggering a context switch? John G -- John.Giacomoni@colorado.edu University of Colorado at Boulder Department of Computer Science Engineering Center, ECCR 1B05 430 UCB Boulder, CO 80303-0430 USA From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 15 00:06:07 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 EB5DE16A41F for ; Tue, 15 Nov 2005 00:06:07 +0000 (GMT) (envelope-from bra@fsn.hu) Received: from people.fsn.hu (people.fsn.hu [195.228.252.137]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE46943D4C for ; Tue, 15 Nov 2005 00:06:06 +0000 (GMT) (envelope-from bra@fsn.hu) Received: from localhost (localhost [127.0.0.1]) by people.fsn.hu (Postfix) with ESMTP id 5719584420; Sun, 13 Nov 2005 18:52:11 +0100 (CET) Received: from people.fsn.hu ([127.0.0.1]) by localhost (people.fsn.hu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 85210-01-9; Sun, 13 Nov 2005 18:51:36 +0100 (CET) Received: from [172.16.164.1] (fw.axelero.hu [195.228.243.120]) by people.fsn.hu (Postfix) with ESMTP id 6AACD8441F; Sun, 13 Nov 2005 18:51:36 +0100 (CET) Message-ID: <43777D24.2060606@fsn.hu> Date: Sun, 13 Nov 2005 18:51:32 +0100 From: Attila Nagy User-Agent: Debian Thunderbird 1.0.2 (X11/20050602) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Joseph Koshy References: <84dead720511112135j435a3723ld15a9d993bbae9cc@mail.gmail.com> In-Reply-To: <84dead720511112135j435a3723ld15a9d993bbae9cc@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at fsn.hu Cc: freebsd Subject: Re: UFS2 max limits? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Nov 2005 00:06:08 -0000 Joseph Koshy wrote: > The Wikipedia page referenced below says that UFS2 supports a > filesystem size of 2^80 Bytes (1YiB) with the limit on a given > file being 2^55 bytes (32 PiB). > Are these numbers correct? I somehow remember the limits as > being much lower (of the order of 16TB or so). I could only create a 128TB sparse file on an UFS2 partition, so I guess 32 PB is a little bith high. -- Attila Nagy e-mail: Attila.Nagy@fsn.hu Free Software Network (FSN.HU) phone: +3630 306 6758 ISOs: http://www.fsn.hu/?f=download From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 15 00:12:55 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 E2FAB16A423 for ; Tue, 15 Nov 2005 00:12:55 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 79E9243D46 for ; Tue, 15 Nov 2005 00:12:55 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.3/8.13.3) with ESMTP id jAF0CnKl084130; Mon, 14 Nov 2005 16:12:49 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.3/8.13.3/Submit) id jAF0CnG2084129; Mon, 14 Nov 2005 16:12:49 -0800 (PST) (envelope-from jmg) Date: Mon, 14 Nov 2005 16:12:49 -0800 From: John-Mark Gurney To: John Giacomoni Message-ID: <20051115001249.GA79020@funkthat.com> Mail-Followup-To: John Giacomoni , freebsd-hackers@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 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 Subject: Re: Sharing the same VM address space between Kernel and UserSpace X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 15 Nov 2005 00:12:56 -0000 John Giacomoni wrote this message on Mon, Nov 14, 2005 at 13:39 -0700: > I am in need of a way to share memory between kernel space and possibly > multiple different user-space processes for an extended period of time. > This memory would need to be a single unpageable region. > > I am using the vm routines as cribbed from mmap, however I'd like the > address spaces to be viewed as the same regardless of which process I'm > in to avoid swizzling pointers as I'm storing data structures in the > shared memory region. > > I imagine I'd need to find a way to expose part of the kernel address > space to user space to accomplish this. > > Is there a way to do this? Getting a common address between userland processes is easy, as you can always just use fixed mappings using the MAP_FIXED flag to mmap.. Getting the same address will take some kernel vm magic, and also not be very portable across platforms, since each platform may/can have a different code address (though we try to keep them the same)... -- 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 15 00:22:57 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 23CA616A41F for ; Tue, 15 Nov 2005 00:22:57 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2042C43D4C for ; Tue, 15 Nov 2005 00:22:56 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.3/8.13.3) with ESMTP id jAF0MtWq084516; Mon, 14 Nov 2005 16:22:55 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.3/8.13.3/Submit) id jAF0MqDP084515; Mon, 14 Nov 2005 16:22:52 -0800 (PST) (envelope-from jmg) Date: Mon, 14 Nov 2005 16:22:52 -0800 From: John-Mark Gurney To: Attila Nagy Message-ID: <20051115002252.GB79020@funkthat.com> Mail-Followup-To: Attila Nagy , Joseph Koshy , freebsd References: <84dead720511112135j435a3723ld15a9d993bbae9cc@mail.gmail.com> <43777D24.2060606@fsn.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43777D24.2060606@fsn.hu> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 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 Subject: Re: UFS2 max limits? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 15 Nov 2005 00:22:57 -0000 Attila Nagy wrote this message on Sun, Nov 13, 2005 at 18:51 +0100: > Joseph Koshy wrote: > >The Wikipedia page referenced below says that UFS2 supports a > >filesystem size of 2^80 Bytes (1YiB) with the limit on a given > >file being 2^55 bytes (32 PiB). > >Are these numbers correct? I somehow remember the limits as > >being much lower (of the order of 16TB or so). > I could only create a 128TB sparse file on an UFS2 partition, so I guess > 32 PB is a little bith high. No, it is not... The reason you were limited to 128TB is that you did not create your filesystem with -f 65536 -b 65536... If you look at my equation that I posted earlier, if you have a blocksize of 16384, you end up with ~128TB as the max file size... K M G T (16384/8)^3*16384 / 1024 / 1024 / 1024 / 1024 == 128 -- 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 15 04:25:46 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 5D97116A41F for ; Tue, 15 Nov 2005 04:25:46 +0000 (GMT) (envelope-from kamalpr@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 905EA43D4C for ; Tue, 15 Nov 2005 04:25:43 +0000 (GMT) (envelope-from kamalpr@gmail.com) Received: by wproxy.gmail.com with SMTP id i5so858620wra for ; Mon, 14 Nov 2005 20:25:42 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:in-reply-to:references:mime-version:content-type:message-id:cc:content-transfer-encoding:from:subject:date:to:x-mailer:sender; b=eAfpwC+SF6Wr6g5sX900ey+xU76iewzZaRNRsKxXcsV1MnGE5z4j0N75vH9Ys07HDXdZEb3vmSPvy3zDD5Czvo4dMWQQpRc0onZ+y8j8c7hT5dI4XRtp5J/TcujlqXiss+zwhXs9+7aXkPREtdbVAdtHl6169XcT89wCeboN4bo= Received: by 10.54.109.9 with SMTP id h9mr3347601wrc; Mon, 14 Nov 2005 20:25:42 -0800 (PST) Received: from ?192.168.2.20? ( [59.92.153.10]) by mx.gmail.com with ESMTP id 33sm1743571wra.2005.11.14.20.25.40; Mon, 14 Nov 2005 20:25:42 -0800 (PST) In-Reply-To: References: <4378FA26.8040604@samsco.org> Mime-Version: 1.0 (Apple Message framework v734) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <53B48211-614A-43F9-89B0-C0A2DE7F168B@acm.org> Content-Transfer-Encoding: 7bit From: "Kamal R. Prasad" Date: Tue, 15 Nov 2005 09:59:57 +0530 To: John Giacomoni X-Mailer: Apple Mail (2.734) Sender: "Kamal R. Prasad" Cc: freebsd-hackers@freebsd.org Subject: Re: Sharing the same VM address space between Kernel and UserSpace X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Nov 2005 04:25:46 -0000 On 15-Nov-05, at 3:58 AM, John Giacomoni wrote: > > On Nov 14, 2005, at 1:57 PM, Scott Long wrote: > > >> John Giacomoni wrote: >> >> >>> I am in need of a way to share memory between kernel space and >>> possibly >>> multiple different user-space processes for an extended period of >>> time. >>> This memory would need to be a single unpageable region. >>> I am using the vm routines as cribbed from mmap, however I'd like >>> the >>> address spaces to be viewed as the same regardless of which >>> process I'm >>> in to avoid swizzling pointers as I'm storing data structures in the >>> shared memory region. >>> I imagine I'd need to find a way to expose part of the kernel >>> address >>> space to user space to accomplish this. >>> Is there a way to do this? >>> thanks >>> John G >>> >> >> If you get this working then it'll be very useful for the syspage >> support that was talked about recently. >> >> The kernel can access addresses in the user space so long as they >> are wired and won't cause a fault. Thus I imagine that you >> only need to allocate the memory, wire it, mark it with the >> appropriate >> page permissions, and reserve a user address range for it in the >> process map. I'd look at the process exec path in the kernel for >> places to hook in. The only other trick then is how to let the user >> process know the address for this magic region. An easy way would be >> to store it in a sysctl that can be read at runtime. A harder way >> would >> be to have the kernel dummy up an elf segment in the image activator >> code that the dynamic linker could read and put into a global >> variable >> for the program to access. >> >> Scott >> >> > > Which thread/list was the syspage support discussed? > (I did a quick search in my freebsd-hackers mailbox and didn't find > it) > > As for my problem I'm not sure that the kernel being able to access > userpages > is quite what is needed. The first reason is that if there are two > processes > trying to map the same region it would be problematic if one of > them had > allocated something in the same area of the heap as the shared > memory region Typically, the address range for heap is different from that of shared memory segment. Im not sure of freebsd -but for AIX what Im saying is true. So, unless you have allocated another shared memory object, MAP_FIXED should suffice to get the same address across user processes. > resides. This suggests that to avoid swizzling the region needs to > be in an > address region where the user-space processes will never allocate > in (kernel). > The other reason is that the kernel code needs to be able to > function using > the shared memory without a user-space process being attached at > all times. > > So the question is, is it possible to mark wired kernel pages as > being accessible > to a user-space process without triggering a context switch? > How about you bring in a kernel process to access the mmap'ed file/ shmid? regards -kamal > John G > > -- > > John.Giacomoni@colorado.edu > University of Colorado at Boulder > Department of Computer Science > Engineering Center, ECCR 1B05 > 430 UCB > Boulder, CO 80303-0430 > USA > > > _______________________________________________ > 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" > Kamal R. Prasad UNIX systems consultant http://www.kamalprasad.com/ kamalp@acm.org From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 15 08:00:28 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 7C12016A41F for ; Tue, 15 Nov 2005 08:00:28 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail16.syd.optusnet.com.au (mail16.syd.optusnet.com.au [211.29.132.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA85F43D49 for ; Tue, 15 Nov 2005 08:00:27 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail16.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id jAF80Nb5003424 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 15 Nov 2005 19:00:23 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1]) by cirb503493.alcatel.com.au (8.12.10/8.12.10) with ESMTP id jAF80NHh091777; Tue, 15 Nov 2005 19:00:23 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id jAF80MCs091776; Tue, 15 Nov 2005 19:00:23 +1100 (EST) (envelope-from pjeremy) Date: Tue, 15 Nov 2005 19:00:22 +1100 From: Peter Jeremy To: John Giacomoni Message-ID: <20051115080022.GI39882@cirb503493.alcatel.com.au> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc Cc: freebsd-hackers@freebsd.org Subject: Re: Sharing the same VM address space between Kernel and UserSpace X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Nov 2005 08:00:28 -0000 On Mon, 2005-Nov-14 13:39:19 -0700, John Giacomoni wrote: >I am in need of a way to share memory between kernel space and possibly >multiple different user-space processes for an extended period of time. >This memory would need to be a single unpageable region. Does the region have to have the same address in both kernel and user space? Based on some of your later comments, I suspect you only need the same address is all userland processes. If this is true, then I think all you need to do is malloc(9) the space, vm_map_wire(9) it and arrange for all userland processes to mmap(2) it at the same address - by having them pass MAP_FIXED. (The malloc() and vm_map_wire() are only needed once because the memory will remain wired until the kernel releases it). Avoiding other mappings isn't that difficult, though it's not totally trivial. You need to avoid KVA, stack, text, heap, shared libraries, SysV SHM and other random mmap()'s. If this is a fairly custom application, you can get a fairly good idea of what other mappings exist and just ensure that you pick an unused address and mmap it fairly early. If you need to allocate a very large region (getting towards the GB region) or this is part of a library that is supposed to be linked into arbitrary applications then things may be more difficult. -- Peter Jeremy From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 15 11:27:27 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 A0BC416A41F for ; Tue, 15 Nov 2005 11:27:27 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5BA4343D46 for ; Tue, 15 Nov 2005 11:27:27 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 3DE7D46B3E; Tue, 15 Nov 2005 06:27:26 -0500 (EST) Date: Tue, 15 Nov 2005 11:27:26 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Peter Jeremy In-Reply-To: <20051115080022.GI39882@cirb503493.alcatel.com.au> Message-ID: <20051115112118.D63879@fledge.watson.org> References: <20051115080022.GI39882@cirb503493.alcatel.com.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org, John Giacomoni Subject: Re: Sharing the same VM address space between Kernel and UserSpace X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Nov 2005 11:27:27 -0000 On Tue, 15 Nov 2005, Peter Jeremy wrote: > Avoiding other mappings isn't that difficult, though it's not totally > trivial. You need to avoid KVA, stack, text, heap, shared libraries, > SysV SHM and other random mmap()'s. If this is a fairly custom > application, you can get a fairly good idea of what other mappings exist > and just ensure that you pick an unused address and mmap it fairly > early. If you need to allocate a very large region (getting towards the > GB region) or this is part of a library that is supposed to be linked > into arbitrary applications then things may be more difficult. This used to be something of a problem in Coda, because we used RVM (Recoverable Virtual Memory) to provide transactional persistent virtual memory. We required a large memory region (generally >128mb) that we could use at the same virtual address base over long runtimes and across reboots -- potentially years or more, since rewriting the memory region was a very expensive and complex process. The VM space would get perturbed every few years due to migrations to ELF, etc, requiring conversion to new addresses. The RVM code had to run early in process execution to prevent VM space fragmentation from becoming a problem also. I imagine that on 64-bit address space systems, life is much easier, but on 32-bit systems even in 1998 we had significant problems with this across many operating systems. So not that it can't be done, but it can be a problem. It might well be worth looking at the address usage in Coda to find some reference use, though, as Coda runs on a number of systems quite successfully, and uses RVM in both the client and server. Robert N M Watson From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 15 12:01:49 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 E77B016A41F for ; Tue, 15 Nov 2005 12:01:48 +0000 (GMT) (envelope-from dirkx@webweaving.org) Received: from skutsje.san.webweaving.org (skutsje.san.webweaving.org [209.132.96.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5CC1E43D55 for ; Tue, 15 Nov 2005 12:01:46 +0000 (GMT) (envelope-from dirkx@webweaving.org) Received: from skutsje.san.webweaving.org (skutsje.san.webweaving.org [209.132.96.45] (may be forged)) by skutsje.san.webweaving.org (8.12.9/8.12.9) with ESMTP id jAFC1j9H046449 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 15 Nov 2005 04:01:45 -0800 (PST) (envelope-from dirkx@webweaving.org) Received: from localhost (dirkx@localhost) by skutsje.san.webweaving.org (8.12.9/8.12.9/Submit) with ESMTP id jAFC1jQu046446 for ; Tue, 15 Nov 2005 04:01:45 -0800 (PST) (envelope-from dirkx@webweaving.org) X-Authentication-Warning: skutsje.san.webweaving.org: dirkx owned process doing -bs Date: Tue, 15 Nov 2005 04:01:45 -0800 (PST) From: Dirk-Willem van Gulik X-X-Sender: dirkx@skutsje.san.webweaving.org To: freebsd-hackers@freebsd.org In-Reply-To: <20051112072658.Q14448@skutsje.san.webweaving.org> Message-ID: <20051115034742.Q40829@skutsje.san.webweaving.org> References: <20051112072658.Q14448@skutsje.san.webweaving.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: Sierra Wireless / AC775 / Loading an external cisfile as a 'quirck' X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Nov 2005 12:01:49 -0000 After a hint from Warner - with the quirck from OpenBSD, see below; I am getting the AC775 nicely detected and showing sensible values; but the attaching of the expected sio(4) driver failes with a: pccard0: check_cis_quirks pccard0: using CIS quirks for Sierra Wireless, AC775, EDGE Network Adapter, R1 pccard0: CIS version PC Card Standard 7.0 pccard0: CIS info: Sierra Wireless, AC775, EDGE Network Adapter, R1 pccard0: Manufacturer code 0x192, product 0x710 pccard0: function 1: serial port, ccr addr 700 mask 73 pccard0: function 1, config table entry 32: I/O card; irq mask 3fbc; iomask 0, iospace 3f8-3ff; io8 irqlevel pccard0: functions scanning pccard0: Card has 1 functions. pccard_mfc is 0 pccard0: (dirkx) values on Mac/Windows: index 0x20 Vcc 5.0 irq 255 io 0x03f8-3ff pccard0: I/O rid 0 start 3f8 end 3ff pccard0: (dirkx) bus_alloc_resource on 452 failed for SYS_RES_IOPORT pccard0: Allocation failed for cfe 32 pccard0: No config entry could be allocated. (complete verbose dmesg on http://people.apache.org/~dirkx/ac775/) on a Soekris, a normal PC and a Sony VAIO. Can anyone give me a hint as to where to start debugging this ? Is there a subtle netbsd quirck difference biting me ? Does any of the above values look suspicious ? Thanks, Dw diff pccard_cis_quirks.c.org pccard_cis_quirks.c > static struct pccard_function pcmcia_sierra_a555_func1 = { > 1, /* function number */ > PCCARD_FUNCTION_SERIAL, > 0x24, /* last cfe number */ > 0x700, /* ccr_base */ > 0x73, /* ccr_mask */ > }; > > static struct pccard_config_entry pcmcia_sierra_a555_func1_cfe0 = { > 0x20, /* cfe number */ > PCCARD_CFE_IO8 | PCCARD_CFE_IRQLEVEL, PCCARD_IFTYPE_IO, > 1, /* num_iospace */ > 0, /* iomask */ > { { 0x0008, 0x3f8 } }, /* iospace */ > 0x3fbc, /* irqmask */ > 0, /* num_memspace */ > { }, /* memspace */ > 0, /* maxtwins */ > }; > /* Sierra */ > #define PCMCIA_VENDOR_SIERRA 0x0192 > #define PCMCIA_CIS_SIERRA_AC710 { NULL, NULL, NULL, NULL } > #define PCMCIA_PRODUCT_SIERRA_AC710 0x0710 > #define PCMCIA_CIS_SIERRA_A550 { NULL, NULL, NULL, NULL } > #define PCMCIA_PRODUCT_SIERRA_A550 0xa550 > #define PCMCIA_CIS_SIERRA_A555 { NULL, NULL, NULL, NULL } > #define PCMCIA_PRODUCT_SIERRA_A555 0xa555 > #define PCMCIA_CIS_SIERRA_A710 { NULL, NULL, NULL, NULL } > #define PCMCIA_PRODUCT_SIERRA_A710 0xa710 > 183a214,225 > { PCMCIA_VENDOR_SIERRA, PCMCIA_PRODUCT_SIERRA_A550, > PCMCIA_CIS_INVALID, > &pcmcia_sierra_a555_func1, &pcmcia_sierra_a555_func1_cfe0 }, > { PCMCIA_VENDOR_SIERRA, PCMCIA_PRODUCT_SIERRA_A555, > PCMCIA_CIS_INVALID, > &pcmcia_sierra_a555_func1, &pcmcia_sierra_a555_func1_cfe0 }, > { PCMCIA_VENDOR_SIERRA, PCMCIA_PRODUCT_SIERRA_A710, > PCMCIA_CIS_INVALID, > &pcmcia_sierra_a555_func1, &pcmcia_sierra_a555_func1_cfe0 }, > { PCMCIA_VENDOR_SIERRA, PCMCIA_PRODUCT_SIERRA_AC710, > PCMCIA_CIS_INVALID, > &pcmcia_sierra_a555_func1, &pcmcia_sierra_a555_func1_cfe0 }, From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 15 13:57:26 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 3FB7E16A41F for ; Tue, 15 Nov 2005 13:57:26 +0000 (GMT) (envelope-from casteld73@yahoo.com) Received: from web60316.mail.yahoo.com (web60316.mail.yahoo.com [209.73.178.124]) by mx1.FreeBSD.org (Postfix) with SMTP id B32D643D45 for ; Tue, 15 Nov 2005 13:57:25 +0000 (GMT) (envelope-from casteld73@yahoo.com) Received: (qmail 94333 invoked by uid 60001); 15 Nov 2005 13:57:24 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=I3uz6ygLwbscGhHZ60Yp1yKn9O7NC8dPhqMioMLFr5H20hIGXgAmoseMpQ674mk7W5kpXdvmjfTQwOAl6UQMzJtGwzJT4sXUvMeOJb5Qxokd+uC80JJyCAr5uBugmH0yskCATruwPDRPI9i/iJil+w3NU67r5g//DNxn9gutbPg= ; Message-ID: <20051115135724.94331.qmail@web60316.mail.yahoo.com> Received: from [66.95.160.2] by web60316.mail.yahoo.com via HTTP; Tue, 15 Nov 2005 05:57:24 PST Date: Tue, 15 Nov 2005 05:57:24 -0800 (PST) From: d c To: Koen Martens In-Reply-To: <4377A15D.7060100@metro.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers@freebsd.org, d c Subject: Re: SSH From within a Jail X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Nov 2005 13:57:26 -0000 Koen Martens wrote: Koen Martens wrote: > d c wrote: > >>Greetings: >> >>I currently am running Freebsd 6.0 Release. >> >>I am experimenting with jails and have run into a >>problem. I need to ssh from within my jail to another >>server. Actually I need to use scp. WHen I try it I >>get the error: "Host key verification failed." > > > This could also be something related to permissions on the .ssh > directory, but you cleared that out of the way if i understand the > rest of this thread correctly. I remember having this problem once, > but can't remember right now what i did to solve it.. I usually > compile openssh from source anyway, so you might try that. If that > works, it would probably be interesting to see what is the > difference between your own hand-rolled openssh and the one that > came with your world. Just remembered something else: do you jexec into the jail, or do you do a proper logon (eg. ssh into the jail). I think that if you jexec into the jail and then try to ssh, you might have a problem because you aren't really logged in to the jail and thus have no (psuedo) tty associated with your session.. Koen -- K.F.J. Martens, Sonologic, http://www.sonologic.nl/ Networking, hosting, embedded systems, unix, artificial intelligence. Public PGP key: http://www.metro.cx/pubkey-gmc.asc Wondering about the funny attachment your mail program can't read? Visit http://www.openpgp.org/ _______________________________________________ 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 Yes- Koen you hit the nail on the head. If I use jexec I cannot use ssh to connect to other servers. I also ran into problems with make in ports tree and using screen. However- If I ssh in I can perform all functions (ssh and make) as if it were it own system...aka- jail. The man page should reflect this. That is...all compiling and management of the jail should be done through ssh. Only use jexec for intial configuration and emergency related work. Thanks everyone for their response and ideas. --------------------------------- Yahoo! FareChase - Search multiple travel sites in one click. From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 15 20:13:25 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 CE74F16A41F for ; Tue, 15 Nov 2005 20:13:25 +0000 (GMT) (envelope-from maslanbsd@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id E9B5343D58 for ; Tue, 15 Nov 2005 20:13:24 +0000 (GMT) (envelope-from maslanbsd@gmail.com) Received: by wproxy.gmail.com with SMTP id i31so1270594wra for ; Tue, 15 Nov 2005 12:13:23 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=OBIFtPdSOaeviD7mtdiwWk3xGGt0Pw8Pfyzqnc7xKgNoLgSkmOW/VprqKBCZgvOeGsX/e488q3bs399rcTdIP+Mbr+KxL/SwfZTbS7J1+xSIMdw5aaVn0wvChfe7htK2YSutMVGswwbAsaHYdeyDn/UxX67Ba4j/OrgVAUAqAxk= Received: by 10.54.93.18 with SMTP id q18mr4367656wrb; Tue, 15 Nov 2005 12:13:23 -0800 (PST) Received: by 10.54.102.3 with HTTP; Tue, 15 Nov 2005 12:13:23 -0800 (PST) Message-ID: <319cceca0511151213p39f84427y55cff6d49742a90f@mail.gmail.com> Date: Tue, 15 Nov 2005 22:13:23 +0200 From: Maslan To: FreeBSD Hackers , netbsd-techkern@netbsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Cc: Subject: Config options X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Nov 2005 20:13:25 -0000 hi hackers, i would appreciate if any one told me how to : 1- add a new option for config. 2- disable an option without removing it. 3- re-enable a disabled option. thanks alot -- I'm Searching For Perfection, So Even If U Need Portability U've To Use Assembly ;-) http://libosdk.berlios.de http://www.maslanlab.org From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 15 22:27:53 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 47DE916A41F for ; Tue, 15 Nov 2005 22:27:53 +0000 (GMT) (envelope-from dirkx@webweaving.org) Received: from skutsje.san.webweaving.org (skutsje.san.webweaving.org [209.132.96.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id 15F3D43D77 for ; Tue, 15 Nov 2005 22:27:45 +0000 (GMT) (envelope-from dirkx@webweaving.org) Received: from skutsje.san.webweaving.org (skutsje.san.webweaving.org [209.132.96.45] (may be forged)) by skutsje.san.webweaving.org (8.12.9/8.12.9) with ESMTP id jAFMRj9H070572 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 15 Nov 2005 14:27:45 -0800 (PST) (envelope-from dirkx@webweaving.org) Received: from localhost (dirkx@localhost) by skutsje.san.webweaving.org (8.12.9/8.12.9/Submit) with ESMTP id jAFMRjCf070569 for ; Tue, 15 Nov 2005 14:27:45 -0800 (PST) (envelope-from dirkx@webweaving.org) X-Authentication-Warning: skutsje.san.webweaving.org: dirkx owned process doing -bs Date: Tue, 15 Nov 2005 14:27:45 -0800 (PST) From: Dirk-Willem van Gulik X-X-Sender: dirkx@skutsje.san.webweaving.org To: freebsd-hackers@freebsd.org In-Reply-To: <20051112072658.Q14448@skutsje.san.webweaving.org> Message-ID: <20051115142431.I40829@skutsje.san.webweaving.org> References: <20051112072658.Q14448@skutsje.san.webweaving.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Works: Sierra Wireless / AC775 / Loading an external cisfile as a 'quick' X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Nov 2005 22:27:53 -0000 For reasons unclear to me; the standard sio0 address 0x3f8 gets in the way even if there is absolutely nothing on that address. It is almost as if the BIOS wispers it in the ear of the kernel even when disabled. Not sure where the kernel gets this from. But in any case; moving it up to the COM3 address solves that issue completely. With the patch below (and increasing the cp4ticks by at least a 10 fold) makes the Sierra Wireless 775 AirConnect card work; in EDGE and in GPRS mode with decent speed (Telfort, the Netherlands) Thanks for all the help ! Dw. root@builld-jv# diff /sys/dev/pccard/pccard_cis_quirks.c.org /sys/dev/pccard/pccard_cis_quirks.c 4c4 < __FBSDID("$FreeBSD: /repoman/r/ncvs/src/sys/dev/pccard/pccard_cis_quirks.c,v 1.15.2.1 2005/09/27 18:42:20 imp Exp $"); --- > __FBSDID("$FreeBSD: src/sys/dev/pccard/pccard_cis_quirks.c,v 1.16 2005/09/20 10:25:51 glebius Exp $"); 182a183,214 > static struct pccard_function pcmcia_sierra_a555_func1 = { > 1, /* function number */ > PCCARD_FUNCTION_SERIAL, > 0x24, /* last cfe number */ > 0x700, /* ccr_base */ > 0x73, /* ccr_mask */ > }; > > static struct pccard_config_entry pcmcia_sierra_a555_func1_cfe0 = { > // 0x20, /* cfe number */ > 0x22, /* cfe number */ > PCCARD_CFE_IO8 | PCCARD_CFE_IRQLEVEL, PCCARD_IFTYPE_IO, > 1, /* num_iospace */ > 0, /* iomask */ > // { { 0x0008, 0x3f8 } }, /* iospace */ > { { 0x0008, 0x3e8 } }, /* iospace */ > 0x3fbc, /* irqmask */ > 0, /* num_memspace */ > { }, /* memspace */ > 0, /* maxtwins */ > }; > /* Sierra */ > #define PCMCIA_VENDOR_SIERRA 0x0192 > #define PCMCIA_CIS_SIERRA_AC710 { NULL, NULL, NULL, NULL } > #define PCMCIA_PRODUCT_SIERRA_AC710 0x0710 > #define PCMCIA_CIS_SIERRA_A550 { NULL, NULL, NULL, NULL } > #define PCMCIA_PRODUCT_SIERRA_A550 0xa550 > #define PCMCIA_CIS_SIERRA_A555 { NULL, NULL, NULL, NULL } > #define PCMCIA_PRODUCT_SIERRA_A555 0xa555 > #define PCMCIA_CIS_SIERRA_A710 { NULL, NULL, NULL, NULL } > #define PCMCIA_PRODUCT_SIERRA_A710 0xa710 > 183a216,227 > { PCMCIA_VENDOR_SIERRA, PCMCIA_PRODUCT_SIERRA_A550, > PCMCIA_CIS_INVALID, > &pcmcia_sierra_a555_func1, &pcmcia_sierra_a555_func1_cfe0 }, > { PCMCIA_VENDOR_SIERRA, PCMCIA_PRODUCT_SIERRA_A555, > PCMCIA_CIS_INVALID, > &pcmcia_sierra_a555_func1, &pcmcia_sierra_a555_func1_cfe0 }, > { PCMCIA_VENDOR_SIERRA, PCMCIA_PRODUCT_SIERRA_A710, > PCMCIA_CIS_INVALID, > &pcmcia_sierra_a555_func1, &pcmcia_sierra_a555_func1_cfe0 }, > { PCMCIA_VENDOR_SIERRA, PCMCIA_PRODUCT_SIERRA_AC710, > PCMCIA_CIS_INVALID, > &pcmcia_sierra_a555_func1, &pcmcia_sierra_a555_func1_cfe0 }, From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 16 10:12:49 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 D7B9416A41F for ; Wed, 16 Nov 2005 10:12:49 +0000 (GMT) (envelope-from orspap@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 69FAD43D45 for ; Wed, 16 Nov 2005 10:12:49 +0000 (GMT) (envelope-from orspap@gmail.com) Received: by wproxy.gmail.com with SMTP id i34so1501402wra for ; Wed, 16 Nov 2005 02:12:48 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=glxhmLmjH/33FBkItKUZbPgKgdDhiGkI3IHMJ5O1VTMdRrjzsuKUNqxBC40taRz0EFurMDf6EpIna+PtkOeAN138/eEAN4LGKvvowZG1EbHysoWQl2BOhTQ7FSkgKo8npVg21ksNW1Wzs9cm2ngAcw3CNzT/nqTVEmFPFtG0NIE= Received: by 10.65.244.6 with SMTP id w6mr537372qbr; Wed, 16 Nov 2005 02:12:48 -0800 (PST) Received: by 10.65.107.12 with HTTP; Wed, 16 Nov 2005 02:12:48 -0800 (PST) Message-ID: <697d7ae00511160212r2adc621bv241d7e929f9ec111@mail.gmail.com> Date: Wed, 16 Nov 2005 12:12:48 +0200 From: Orestis Papakonstantinou To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: VIA RAID controller problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2005 10:12:50 -0000 Hello everyone, I recently purchased a laptop (Amilo M3438G) that uses VIA's VT6421 RAID controller. I have problem installing FreeBSD (6.0) on that laptop because FreeBSD does not support this hardware and after the installation it loses all the mount points, got several core dumps too etc etc. VIA has released drivers for Linux (both SuSE and Redhat) and I would like to ask if there i= s a way to integrate these drivers to FreeBSD at boot time (not through Linux compatibility layer after the install). Has anyone with similar hardware found a solution? Thanks for your time! From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 16 10:45:12 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 8C3F516A41F for ; Wed, 16 Nov 2005 10:45:12 +0000 (GMT) (envelope-from marcin@studio4plus.com) Received: from pe78.opole.sdi.tpnet.pl (pe78.opole.sdi.tpnet.pl [217.96.240.78]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0305643D46 for ; Wed, 16 Nov 2005 10:45:11 +0000 (GMT) (envelope-from marcin@studio4plus.com) Received: from [81.219.217.131] (helo=[192.168.0.101]) by pe78.opole.sdi.tpnet.pl with esmtpa (Exim 4.52 (FreeBSD)) id 1EcKms-000P7K-1f; Wed, 16 Nov 2005 11:45:10 +0100 Message-ID: <437B0DB0.8040002@studio4plus.com> Date: Wed, 16 Nov 2005 11:45:04 +0100 From: Marcin Simonides User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051111) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Orestis Papakonstantinou References: <697d7ae00511160212r2adc621bv241d7e929f9ec111@mail.gmail.com> In-Reply-To: <697d7ae00511160212r2adc621bv241d7e929f9ec111@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: VIA RAID controller problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2005 10:45:12 -0000 Orestis Papakonstantinou wrote: > I recently purchased a laptop (Amilo M3438G) that uses VIA's VT6421 RAID > controller. I have problem installing FreeBSD (6.0) on that laptop because [...] > compatibility layer after the install). Has anyone with similar hardware > found a solution? Thanks for your time! I'm using a similar VIA VT6420 with FreeBSD 6.0 though the system is installed on a single IDE disk and only uses VIA's RAID for /usr. I've had problems with RAID0 (I'm going to post more information soon, I need to make a few tests), but I think RAID1 should work fine (I haven't tried). -- Marcin Simonides From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 16 10:48:29 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 17F1016A41F for ; Wed, 16 Nov 2005 10:48:29 +0000 (GMT) (envelope-from ntarmos@diogenis.ceid.upatras.gr) Received: from poseidon.ceid.upatras.gr (poseidon.ceid.upatras.gr [150.140.141.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id D9DEE43D6E for ; Wed, 16 Nov 2005 10:48:23 +0000 (GMT) (envelope-from ntarmos@diogenis.ceid.upatras.gr) Received: from rhea.ceid.upatras.gr (rhea.ceid.upatras.gr [150.140.141.171]) by poseidon.ceid.upatras.gr (Postfix) with ESMTP id AC7175C13C1 for ; Wed, 16 Nov 2005 12:48:21 +0200 (EET) Received: from localhost (localhost [127.0.0.1]) by rhea.ceid.upatras.gr (Postfix) with ESMTP id 1F5ED80003 for ; Wed, 16 Nov 2005 12:48:20 +0200 (EET) Received: from rhea.ceid.upatras.gr ([127.0.0.1]) by localhost (rhea [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 08421-09 for ; Wed, 16 Nov 2005 12:48:20 +0200 (EET) Received: from diogenis.ceid.upatras.gr (diogenis.ceid.upatras.gr [150.140.141.181]) by rhea.ceid.upatras.gr (Postfix) with ESMTP id 4255580002 for ; Wed, 16 Nov 2005 12:48:19 +0200 (EET) Received: by diogenis.ceid.upatras.gr (Postfix, from userid 21001) id E542FB013A; Wed, 16 Nov 2005 12:48:18 +0200 (EET) Date: Wed, 16 Nov 2005 12:48:19 +0200 From: Nikos Ntarmos To: freebsd-hackers@freebsd.org Message-ID: <20051116104819.GA10128@diogenis.ceid.upatras.gr> Mail-Followup-To: Nikos Ntarmos , freebsd-hackers@freebsd.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="gatW/ieO32f1wygP" Content-Disposition: inline Organization: NetCInS Lab., C.E.I.D., U. of Patras, Greece WWW-Homepage: http://noth.ceid.upatras.gr/ X-PGP-Fingerprint: 9680 60A7 DE60 0298 B1F0 9B22 9BA2 7569 CF95 160A Office-Phone: +30-2610-996919 Office-Fax: +30-2610-969011 GPS-Info: 38.2594N, 21.7428E User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new at ceid.upatras.gr Subject: Bogus ioapic entry X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2005 10:48:29 -0000 --gatW/ieO32f1wygP Content-Type: multipart/mixed; boundary="LZvS9be/3tNcYl/X" Content-Disposition: inline --LZvS9be/3tNcYl/X Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi all. I spent a couple of hours last night trying to get ACPI to function correctly on my new Acer Aspire 1692WLMi. I found out that with apic enabled, the system hangs when returning from S3, while with apic disabled it suffers from interrupt storms on irq9 and the screen is not reinitialized on return from S3 (with hw.acpi.reset_video set to both "0" and "1"). While trying to hunt this thing down, I noticed that the GENERIC kernel of 6.0-STABLE (and probably of other branches as well) incorrectly discovers two ioapic devices: ioapic1: Changing APIC ID to 2 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-23 on motherboard There is something obviously wrong with ioapic1. The cause seems to be the handling of value and numintr in ioapic_create(...). value is a uint32_t, while numintr is a u_int, both of which are 32-bits long (per and at least on my i386). The code in ioapic_create(...), after the call to ioapic_read(apic, IOAPIC_VER), uses the latter's return value to compute the number of interrupts assigned to the current ioapic. This return value is checked against 0xffffff (that's 24 1-bits) to detect an error and bail out. This code chunk is also in -current (so perhaps I'm missing something here...) The (buggy?) BIOS implementation of my laptop returns a value of 0xffffffff (32 1-bits) in ioapic_read(...). This, however, doesn't trigger the current if-clause, so the code proceeds and creates ioapic1 with -1(!) assigned IRQs (due to the and-and-shift-plus-one formula of computing numintr). The attached diff fixes this situation and seems more correct to me than the current code, given that io_numintr is 8 bits and u_int is 32 bits per C standard. The problems with resuming from S3 still haunt me though. I guess I should have a look at acpi@ later today... Cheers. \n\n --LZvS9be/3tNcYl/X Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="io_apic.c.diff" Content-Transfer-Encoding: quoted-printable --- io_apic.c.orig Fri Aug 5 22:08:25 2005 +++ io_apic.c Wed Nov 16 12:26:47 2005 @@ -478,14 +478,21 @@ value =3D ioapic_read(apic, IOAPIC_VER); mtx_unlock_spin(&icu_lock); =20 - /* If it's version register doesn't seem to work, punt. */ - if (value =3D=3D 0xffffff) { + /* Determine the number of vectors and set the APIC ID. */ + numintr =3D ((value & IOART_VER_MAXREDIR) >> MAXREDIRSHIFT) + 1; + + /* numintr is a uint32_t but io_numintr is only 8 bits long. On my + * Acer Aspire 1692WLMi, two ioapic's are discovered. However, the + * second one is bogus, since ioapic_read(apic, IOAPIC_VER) returns + * 0xffffffff, which doesn't trigger the old if-clause (value =3D=3D + * 0xffffff). Keeping around an ioapic with -1 assigned IRQs doesn't + * make much sense, so: + */ + if ((numintr & 0x000000ff) =3D=3D 0) { pmap_unmapdev((vm_offset_t)apic, IOAPIC_MEM_REGION); return (NULL); } =20 - /* Determine the number of vectors and set the APIC ID. */ - numintr =3D ((value & IOART_VER_MAXREDIR) >> MAXREDIRSHIFT) + 1; io =3D malloc(sizeof(struct ioapic) + numintr * sizeof(struct ioapic_intsrc), M_IOAPIC, M_WAITOK); io->io_pic =3D ioapic_template; --LZvS9be/3tNcYl/X-- --gatW/ieO32f1wygP Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Nikos Ntarmos iD8DBQFDew5zm6J1ac+VFgoRAihHAKCGEl+nzwUPqEJsg8menyuoE4RPZwCgkGjZ U/2bmem5pLsLug6YKVKmpYU= =KfKL -----END PGP SIGNATURE----- --gatW/ieO32f1wygP-- From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 16 11:14:00 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 1931E16A420 for ; Wed, 16 Nov 2005 11:14:00 +0000 (GMT) (envelope-from orspap@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F02A43D46 for ; Wed, 16 Nov 2005 11:13:58 +0000 (GMT) (envelope-from orspap@gmail.com) Received: by zproxy.gmail.com with SMTP id 40so1597820nzk for ; Wed, 16 Nov 2005 03:13:58 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=hXhi8ri49MI15TnPXcoR2yfnoGHzunX8hJxewnHPazL6wolNDbgqqCQnoRYkCPXZHu+a/cWM8lRLGNF0AZkSeapYTgW/5e4TrBcYY2yRDB49uDrrypVOjTVdQ1D3f442FoTAdtiVaqYM+gnh9CTO/53AhQ3EPpLkTyFjMBUKyv4= Received: by 10.65.75.16 with SMTP id c16mr3213525qbl; Wed, 16 Nov 2005 03:13:58 -0800 (PST) Received: by 10.65.107.12 with HTTP; Wed, 16 Nov 2005 03:13:58 -0800 (PST) Message-ID: <697d7ae00511160313nbc7f45dh4b458ea6b0fffd5d@mail.gmail.com> Date: Wed, 16 Nov 2005 13:13:58 +0200 From: Orestis Papakonstantinou To: freebsd-hackers@freebsd.org In-Reply-To: <697d7ae00511160311u269eda1dw44c24b4f3a85e001@mail.gmail.com> MIME-Version: 1.0 References: <697d7ae00511160212r2adc621bv241d7e929f9ec111@mail.gmail.com> <437B0DB0.8040002@studio4plus.com> <697d7ae00511160311u269eda1dw44c24b4f3a85e001@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: VIA RAID controller problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2005 11:14:00 -0000 ---------- Forwarded message ---------- From: Orestis Papakonstantinou Date: Nov 16, 2005 1:11 PM Subject: Re: VIA RAID controller problem To: Marcin Simonides The problem in my situation is that I am using a laptop. That means that whether I use RAID 0/1 or just JBOD is the same thing because everything passes through that RAID controller. It is completely embedded to the system. My BIOS does not even know that I am using RAID or if it does, it hasn't got any configuration settings, so that FreeBSD could "look" through the BIOS. Things get even more complicated if you consider that my laptop hasn't got a floppy drive. Because even the existing VIA RAID drivers for Linux are released as an iso for a floppy to be booted from the kernel. So on a second thought I really cant use FreeBSD on that laptop unless these drivers are supported in a future release version (embedded to the kernel o= n boot-time). So if any FreeBSD developers are reading this, I would be grateful if they could embed this RAID controller driver in a future release. Thanks for replying. On 11/16/05, Marcin Simonides wrote: > > Orestis Papakonstantinou wrote: > > > I recently purchased a laptop (Amilo M3438G) that uses VIA's VT6421 RAI= D > > controller. I have problem installing FreeBSD (6.0) on that laptop > because > [...] > > compatibility layer after the install). Has anyone with similar hardwar= e > > > found a solution? Thanks for your time! > > I'm using a similar VIA VT6420 with FreeBSD 6.0 though the system is > installed on a single IDE disk and only uses VIA's RAID for /usr. > > I've had problems with RAID0 (I'm going to post more information soon, I > need to make a few tests), but I think RAID1 should work fine (I haven't > tried). > -- > Marcin Simonides > From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 16 16:03:41 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 C743016A41F for ; Wed, 16 Nov 2005 16:03:41 +0000 (GMT) (envelope-from mayong@mail.com) Received: from webmail-outgoing.us4.outblaze.com (webmail-outgoing2.us4.outblaze.com [205.158.62.67]) by mx1.FreeBSD.org (Postfix) with ESMTP id 17EDE43D45 for ; Wed, 16 Nov 2005 16:03:41 +0000 (GMT) (envelope-from mayong@mail.com) Received: from unknown (unknown [192.168.9.180]) by webmail-outgoing.us4.outblaze.com (Postfix) with QMQP id B09AA1800232 for ; Wed, 16 Nov 2005 16:03:40 +0000 (GMT) X-OB-Received: from unknown (205.158.62.50) by wfilter.us4.outblaze.com; 16 Nov 2005 10:33:10 -0000 Received: by ws1-4.us4.outblaze.com (Postfix, from userid 1001) id 20B9A164A49; Wed, 16 Nov 2005 10:33:10 +0000 (GMT) Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 From: "Yong Ma" To: freebsd-drivers@freebsd.org Date: Wed, 16 Nov 2005 05:33:09 -0500 Received: from [159.226.5.225] by ws1-4.us4.outblaze.com with http for mayong@mail.com; Wed, 16 Nov 2005 05:33:09 -0500 X-Originating-Ip: 159.226.5.225 X-Originating-Server: ws1-4.us4.outblaze.com Message-Id: <20051116103310.20B9A164A49@ws1-4.us4.outblaze.com> Cc: freebsd-hackers@freebsd.org Subject: Re: How to make my new driver be configurable in the kernel configuration file? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2005 16:03:42 -0000 ----- Original Message ----- From: "Warner Losh" To: jhb@freebsd.org Subject: Re: How to make my new driver be configurable in the kernel config= uration file? Date: Tue, 15 Nov 2005 09:19:09 -0700 (MST) >=20 > From: John Baldwin > Subject: Re: How to make my new driver be configurable in the=20 > kernel configuration file? > Date: Tue, 15 Nov 2005 10:21:59 -0500 >=20 > > On Tuesday 15 November 2005 03:59 am, Yong Ma wrote: > > > Hi all, > > > I wrote and debuged my driver for a new device in KLD mode,now I want= to > > > plug it into the kernel,so that it can be loaded when the system boo= ts,and > > > make it be configurable in the kernel configuration file like other d= evice > > > driver as "device XXX",I don't know what to do,could anyone be kind t= o help > > > me? > > > > To add your driver you update the src/sys/conf/files* files. If=20 > > your driver is machine independent, you can add it to=20 > > src/sys/conf/files. For example, here are the lines in=20 > > sys/conf/files for the cy(4) driver: > > > > dev/cy/cy.c optional cy > > dev/cy/cy_isa.c optional cy isa > > dev/cy/cy_pci.c optional cy pci > > > > If your driver only works on a single architecture (such as i386)=20 > > then add it to the architecture file sys/conf/files. (e.g.=20 > > sys/conf/files.i386). The device names after 'optional' specify=20 > > which devices must be enabled in the kernel config for that file=20 > > to be included. Thus, in the example above, src/sys/dev/cy/cy.c=20 > > is included as long as 'device cy' is in the kernel, but=20 > > src/sys/dev/cy/cy_isa.c is only included if both 'device cy' and=20 > > 'device isa' are in the kernel config file. >=20 > You can augment the system files with the files directive if you don't > want to edit sys/conf/files.foo: >=20 > files "/foo/bar/baz" >=20 > and put something like the above in that. >=20 > Warner >=20 > _______________________________________________ > freebsd-drivers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-drivers > To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@freebsd.org" Thank you! I did as that but came across some problems,these are the=20 jobs and the errors: 1) I copyed the files to the sys/dev/mydevice and added=20 "dev/mydevice/mydevice.c optinonal mydevice" in the file=20 /usr/src/sys/conf/files.i386,and added a line "device mydevice" in=20 the sys/i386/conf/MYKERNEL(a copy of GENERIC),but met a error when=20 config MYKERNEL:syntax error (the line I just added). 2) Then,I modified line in files.i386 as "dev/mydevice/mydevice.c=20=20= =20 standard",configed successfully,but another error occured when make=20 depend(make buildkernel KERNCONF=3DMYKERNEL the same): ... ../../../dev/mydevice/mydevice.c:27:20: mydevice.h: No such=20 file or directory ../../../dev/mydevice/mydevice.c:28:44: mydevicekern.h: No such=20 file or directory ../../../dev/mydevice/mydevice.c:29:49: mydeviceioctl.h: No=20 such file or directory mkdep: compile failed *** Error code 1 ... and the source code of mydevice.c is as follows: ... #include "sjy22b.h" #include "sjy22bkern.h" #include "sjy22bioctl.h" ... the three headers are just in the sys/dev/mydevice directory,I don't=20 know why this happened. Need your suggestion! Thanks Yong --=20 ___________________________________________________ Play 100s of games for FREE! http://games.mail.com/ From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 16 16:10:29 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 756E916A41F for ; Wed, 16 Nov 2005 16:10:29 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 318AD43D49 for ; Wed, 16 Nov 2005 16:10:27 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 2066458 for multiple; Wed, 16 Nov 2005 11:10:03 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jAGG9tVV001642; Wed, 16 Nov 2005 11:09:55 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Wed, 16 Nov 2005 11:10:02 -0500 User-Agent: KMail/1.8.2 References: <20051116104819.GA10128@diogenis.ceid.upatras.gr> In-Reply-To: <20051116104819.GA10128@diogenis.ceid.upatras.gr> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511161110.02750.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: Nikos Ntarmos Subject: Re: Bogus ioapic entry X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2005 16:10:29 -0000 On Wednesday 16 November 2005 05:48 am, Nikos Ntarmos wrote: > Hi all. > > I spent a couple of hours last night trying to get ACPI to function > correctly on my new Acer Aspire 1692WLMi. I found out that with apic > enabled, the system hangs when returning from S3, while with apic > disabled it suffers from interrupt storms on irq9 and the screen is not > reinitialized on return from S3 (with hw.acpi.reset_video set to both > "0" and "1"). While trying to hunt this thing down, I noticed that the > GENERIC kernel of 6.0-STABLE (and probably of other branches as well) > incorrectly discovers two ioapic devices: > > ioapic1: Changing APIC ID to 2 > ioapic0 irqs 0-23 on motherboard > ioapic1 irqs 24-23 on motherboard > > There is something obviously wrong with ioapic1. The cause seems to be > the handling of value and numintr in ioapic_create(...). value is a > uint32_t, while numintr is a u_int, both of which are 32-bits long (per > and at least on my i386). The code in > ioapic_create(...), after the call to ioapic_read(apic, IOAPIC_VER), > uses the latter's return value to compute the number of interrupts > assigned to the current ioapic. This return value is checked against > 0xffffff (that's 24 1-bits) to detect an error and bail out. This code > chunk is also in -current (so perhaps I'm missing something here...) > > The (buggy?) BIOS implementation of my laptop returns a value of > 0xffffffff (32 1-bits) in ioapic_read(...). This, however, doesn't > trigger the current if-clause, so the code proceeds and creates ioapic1 > with -1(!) assigned IRQs (due to the and-and-shift-plus-one formula of > computing numintr). > > The attached diff fixes this situation and seems more correct to me than > the current code, given that io_numintr is 8 bits and u_int is 32 bits > per C standard. The problems with resuming from S3 > still haunt me though. I guess I should have a look at acpi@ later > today... > > Cheers. > > \n\n How about this diff instead. It is supposed to be explicitly checking for -1 since a read of an invalid memory or device location returns -1. I just typo'd and didn't put the right value in for the check. Index: io_apic.c =================================================================== RCS file: /usr/cvs/src/sys/i386/i386/io_apic.c,v retrieving revision 1.23 diff -u -r1.23 io_apic.c --- io_apic.c 2 Nov 2005 20:11:47 -0000 1.23 +++ io_apic.c 16 Nov 2005 16:09:19 -0000 @@ -502,7 +502,7 @@ mtx_unlock_spin(&icu_lock); /* If it's version register doesn't seem to work, punt. */ - if (value == 0xffffff) { + if (value == 0xffffffff) { pmap_unmapdev((vm_offset_t)apic, IOAPIC_MEM_REGION); return (NULL); } -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 16 16:29:18 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 1194A16A41F; Wed, 16 Nov 2005 16:29:18 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id A4CBC43D66; Wed, 16 Nov 2005 16:29:15 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 2067365 for multiple; Wed, 16 Nov 2005 11:28:37 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jAGGSRul001754; Wed, 16 Nov 2005 11:28:29 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-drivers@freebsd.org Date: Wed, 16 Nov 2005 11:28:25 -0500 User-Agent: KMail/1.8.2 References: <20051116103310.20B9A164A49@ws1-4.us4.outblaze.com> In-Reply-To: <20051116103310.20B9A164A49@ws1-4.us4.outblaze.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511161128.26191.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: freebsd-hackers@freebsd.org, Yong Ma Subject: Re: How to make my new driver be configurable in the kernel configuration file? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2005 16:29:18 -0000 On Wednesday 16 November 2005 05:33 am, Yong Ma wrote: > ----- Original Message ----- > From: "Warner Losh" > To: jhb@freebsd.org > Subject: Re: How to make my new driver be configurable in the kernel > configuration file? Date: Tue, 15 Nov 2005 09:19:09 -0700 (MST) > > > From: John Baldwin > > Subject: Re: How to make my new driver be configurable in the > > kernel configuration file? > > Date: Tue, 15 Nov 2005 10:21:59 -0500 > > > > > On Tuesday 15 November 2005 03:59 am, Yong Ma wrote: > > > > Hi all, > > > > I wrote and debuged my driver for a new device in KLD mode,now I want > > > > to plug it into the kernel,so that it can be loaded when the system > > > > boots,and make it be configurable in the kernel configuration file > > > > like other device driver as "device XXX",I don't know what to > > > > do,could anyone be kind to help me? > > > > > > To add your driver you update the src/sys/conf/files* files. If > > > your driver is machine independent, you can add it to > > > src/sys/conf/files. For example, here are the lines in > > > sys/conf/files for the cy(4) driver: > > > > > > dev/cy/cy.c optional cy > > > dev/cy/cy_isa.c optional cy isa > > > dev/cy/cy_pci.c optional cy pci > > > > > > If your driver only works on a single architecture (such as i386) > > > then add it to the architecture file sys/conf/files. (e.g. > > > sys/conf/files.i386). The device names after 'optional' specify > > > which devices must be enabled in the kernel config for that file > > > to be included. Thus, in the example above, src/sys/dev/cy/cy.c > > > is included as long as 'device cy' is in the kernel, but > > > src/sys/dev/cy/cy_isa.c is only included if both 'device cy' and > > > 'device isa' are in the kernel config file. > > > > You can augment the system files with the files directive if you don't > > want to edit sys/conf/files.foo: > > > > files "/foo/bar/baz" > > > > and put something like the above in that. > > > > Warner > > > > _______________________________________________ > > freebsd-drivers@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-drivers > > To unsubscribe, send any mail to > > "freebsd-drivers-unsubscribe@freebsd.org" > > Thank you! I did as that but came across some problems,these are the > jobs and the errors: > > 1) I copyed the files to the sys/dev/mydevice and added > "dev/mydevice/mydevice.c optinonal mydevice" in the file > /usr/src/sys/conf/files.i386,and added a line "device mydevice" in > the sys/i386/conf/MYKERNEL(a copy of GENERIC),but met a error when > config MYKERNEL:syntax error (the line I just added). > > 2) Then,I modified line in files.i386 as "dev/mydevice/mydevice.c > standard",configed successfully,but another error occured when make > depend(make buildkernel KERNCONF=MYKERNEL the same): > ... > ../../../dev/mydevice/mydevice.c:27:20: mydevice.h: No such > file or directory > ../../../dev/mydevice/mydevice.c:28:44: mydevicekern.h: No such > file or directory > ../../../dev/mydevice/mydevice.c:29:49: mydeviceioctl.h: No > such file or directory > mkdep: compile failed > *** Error code 1 > ... > and the source code of mydevice.c is as follows: > ... > #include "sjy22b.h" > #include "sjy22bkern.h" > #include "sjy22bioctl.h" > ... > the three headers are just in the sys/dev/mydevice directory,I don't > know why this happened. > Need your suggestion! You'll need to include them as "dev/mydevice/mydevice.h" rather than "mydevice.h" -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 16 16:38:08 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 B3AAD16A41F; Wed, 16 Nov 2005 16:38:08 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A40343D4C; Wed, 16 Nov 2005 16:38:08 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id jAGGa8rb053516; Wed, 16 Nov 2005 09:36:08 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Wed, 16 Nov 2005 09:36:11 -0700 (MST) Message-Id: <20051116.093611.06948893.imp@bsdimp.com> To: jhb@freebsd.org From: "M. Warner Losh" In-Reply-To: <200511161128.26191.jhb@freebsd.org> References: <20051116103310.20B9A164A49@ws1-4.us4.outblaze.com> <200511161128.26191.jhb@freebsd.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Wed, 16 Nov 2005 09:36:08 -0700 (MST) Cc: freebsd-hackers@freebsd.org, freebsd-drivers@freebsd.org Subject: Re: How to make my new driver be configurable in the kernel configuration file? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2005 16:38:09 -0000 In message: <200511161128.26191.jhb@freebsd.org> John Baldwin writes: : On Wednesday 16 November 2005 05:33 am, Yong Ma wrote: : > ----- Original Message ----- : > From: "Warner Losh" : > To: jhb@freebsd.org : > Subject: Re: How to make my new driver be configurable in the kernel : > configuration file? Date: Tue, 15 Nov 2005 09:19:09 -0700 (MST) : > : > > From: John Baldwin : > > Subject: Re: How to make my new driver be configurable in the : > > kernel configuration file? : > > Date: Tue, 15 Nov 2005 10:21:59 -0500 : > > : > > > On Tuesday 15 November 2005 03:59 am, Yong Ma wrote: : > > > > Hi all, : > > > > I wrote and debuged my driver for a new device in KLD mode,now I want : > > > > to plug it into the kernel,so that it can be loaded when the system : > > > > boots,and make it be configurable in the kernel configuration file : > > > > like other device driver as "device XXX",I don't know what to : > > > > do,could anyone be kind to help me? : > > > : > > > To add your driver you update the src/sys/conf/files* files. If : > > > your driver is machine independent, you can add it to : > > > src/sys/conf/files. For example, here are the lines in : > > > sys/conf/files for the cy(4) driver: : > > > : > > > dev/cy/cy.c optional cy : > > > dev/cy/cy_isa.c optional cy isa : > > > dev/cy/cy_pci.c optional cy pci : > > > : > > > If your driver only works on a single architecture (such as i386) : > > > then add it to the architecture file sys/conf/files. (e.g. : > > > sys/conf/files.i386). The device names after 'optional' specify : > > > which devices must be enabled in the kernel config for that file : > > > to be included. Thus, in the example above, src/sys/dev/cy/cy.c : > > > is included as long as 'device cy' is in the kernel, but : > > > src/sys/dev/cy/cy_isa.c is only included if both 'device cy' and : > > > 'device isa' are in the kernel config file. : > > : > > You can augment the system files with the files directive if you don't : > > want to edit sys/conf/files.foo: : > > : > > files "/foo/bar/baz" : > > : > > and put something like the above in that. : > > : > > Warner : > > : > > _______________________________________________ : > > freebsd-drivers@freebsd.org mailing list : > > http://lists.freebsd.org/mailman/listinfo/freebsd-drivers : > > To unsubscribe, send any mail to : > > "freebsd-drivers-unsubscribe@freebsd.org" : > : > Thank you! I did as that but came across some problems,these are the : > jobs and the errors: : > : > 1) I copyed the files to the sys/dev/mydevice and added : > "dev/mydevice/mydevice.c optinonal mydevice" in the file : > /usr/src/sys/conf/files.i386,and added a line "device mydevice" in : > the sys/i386/conf/MYKERNEL(a copy of GENERIC),but met a error when : > config MYKERNEL:syntax error (the line I just added). : > : > 2) Then,I modified line in files.i386 as "dev/mydevice/mydevice.c : > standard",configed successfully,but another error occured when make : > depend(make buildkernel KERNCONF=MYKERNEL the same): : > ... : > ../../../dev/mydevice/mydevice.c:27:20: mydevice.h: No such : > file or directory : > ../../../dev/mydevice/mydevice.c:28:44: mydevicekern.h: No such : > file or directory : > ../../../dev/mydevice/mydevice.c:29:49: mydeviceioctl.h: No : > such file or directory : > mkdep: compile failed : > *** Error code 1 : > ... : > and the source code of mydevice.c is as follows: : > ... : > #include "sjy22b.h" : > #include "sjy22bkern.h" : > #include "sjy22bioctl.h" : > ... : > the three headers are just in the sys/dev/mydevice directory,I don't : > know why this happened. : > Need your suggestion! : : You'll need to include them as "dev/mydevice/mydevice.h" rather than : "mydevice.h" Usually that's spelled '#include ' since it is relative to one of the -I paths. In practice, however, it rarely makes a difference. Warner From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 16 17:56:46 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 AE9B316A41F for ; Wed, 16 Nov 2005 17:56:46 +0000 (GMT) (envelope-from mayong@mail.com) Received: from webmail-outgoing.us4.outblaze.com (webmail-outgoing2.us4.outblaze.com [205.158.62.67]) by mx1.FreeBSD.org (Postfix) with ESMTP id BABB743D49 for ; Wed, 16 Nov 2005 17:56:45 +0000 (GMT) (envelope-from mayong@mail.com) Received: from unknown (unknown [192.168.9.180]) by webmail-outgoing.us4.outblaze.com (Postfix) with QMQP id 1FDFD180022E for ; Wed, 16 Nov 2005 17:56:45 +0000 (GMT) X-OB-Received: from unknown (205.158.62.182) by wfilter.us4.outblaze.com; 16 Nov 2005 03:20:01 -0000 Received: by ws1-6.us4.outblaze.com (Postfix, from userid 1001) id 7C66D1CE30A; Wed, 16 Nov 2005 03:20:01 +0000 (GMT) Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 From: "Yong Ma" To: freebsd-drivers@freebsd.org Date: Tue, 15 Nov 2005 22:20:01 -0500 Received: from [159.226.5.225] by ws1-6.us4.outblaze.com with http for mayong@mail.com; Tue, 15 Nov 2005 22:20:01 -0500 X-Originating-Ip: 159.226.5.225 X-Originating-Server: ws1-6.us4.outblaze.com Message-Id: <20051116032001.7C66D1CE30A@ws1-6.us4.outblaze.com> Cc: freebsd-hackers@freebsd.org Subject: Re: How to make my new driver be configurable in the kernel configuration file? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2005 17:56:46 -0000 ----- Original Message ----- From: "John Baldwin" To: freebsd-drivers@freebsd.org Subject: Re: How to make my new driver be configurable in the kernel config= uration file? Date: Tue, 15 Nov 2005 10:21:59 -0500 >=20 > On Tuesday 15 November 2005 03:59 am, Yong Ma wrote: > > Hi all, > > I wrote and debuged my driver for a new device in KLD mode,now I want to > > plug it into the kernel,so that it can be loaded when the system boots= ,and > > make it be configurable in the kernel configuration file like other dev= ice > > driver as "device XXX",I don't know what to do,could anyone be kind to = help > > me? >=20 > To add your driver you update the src/sys/conf/files* files. If your dri= ver > is machine independent, you can add it to src/sys/conf/files. For exampl= e, > here are the lines in sys/conf/files for the cy(4) driver: >=20 > dev/cy/cy.c optional cy > dev/cy/cy_isa.c optional cy isa > dev/cy/cy_pci.c optional cy pci >=20 > If your driver only works on a single architecture (such as i386) then ad= d it > to the architecture file sys/conf/files. (e.g. sys/conf/files.i386). > The device names after 'optional' specify which devices must be enabled in > the kernel config for that file to be included. Thus, in the example abo= ve, > src/sys/dev/cy/cy.c is included as long as 'device cy' is in the kernel, = but > src/sys/dev/cy/cy_isa.c is only included if both 'device cy' and 'device = isa' > are in the kernel config file. >=20 > -- > John Baldwin <>< http://www.FreeBSD.org/~jhb/ > "Power Users Use the Power to Serve" =3D http://www.FreeBSD.org Thank you! I did as that but came across some problems,these are the jobs a= nd the errors: 1) I copyed the files to the sys/dev/mydevice and added "dev/mydevice/myde= vice.c optinonal mydevice" in the file /usr/src/sys/conf/files.i386,and a= dded a line "device mydevice" in the sys/i386/conf/MYKERNEL(a copy of GENER= IC),but met a error when config MYKERNEL:syntax error (the line I just adde= d). 2) Then,I modified line in files.i386 as "dev/mydevice/mydevice.c standa= rd",configed successfully,but another error occured when make depend(make b= uildkernel KERNCONF=3DMYKERNEL the same): ... ../../../dev/mydevice/mydevice.c:27:20: mydevice.h: No such file or di= rectory ../../../dev/mydevice/mydevice.c:28:44: mydevicekern.h: No such file o= r directory ../../../dev/mydevice/mydevice.c:29:49: mydeviceioctl.h: No such file = or directory mkdep: compile failed *** Error code 1 ... and the source code of mydevice.c is as follows: ... #include "sjy22b.h" #include "sjy22bkern.h"=20=20 #include "sjy22bioctl.h"=20 ... the three headers are just in the sys/dev/mydevice directory,I don't know w= hy this happened. Need your suggestion! Thanks Yong --=20 ___________________________________________________ Play 100s of games for FREE! http://games.mail.com/ From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 16 20:14:22 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 583BF16A41F; Wed, 16 Nov 2005 20:14:22 +0000 (GMT) (envelope-from julian@elischer.org) Received: from a50.ironport.com (a50.ironport.com [63.251.108.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E5BA43D45; Wed, 16 Nov 2005 20:14:21 +0000 (GMT) (envelope-from julian@elischer.org) Received: from unknown (HELO [10.251.19.149]) ([10.251.19.149]) by a50.ironport.com with ESMTP; 16 Nov 2005 12:14:21 -0800 X-IronPort-Anti-Spam-Filtered: true Message-ID: <437B931C.9080107@elischer.org> Date: Wed, 16 Nov 2005 12:14:20 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.11) Gecko/20050727 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Yong Ma References: <20051116032001.7C66D1CE30A@ws1-6.us4.outblaze.com> In-Reply-To: <20051116032001.7C66D1CE30A@ws1-6.us4.outblaze.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, freebsd-drivers@freebsd.org Subject: Re: How to make my new driver be configurable in the kernel configuration file? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2005 20:14:22 -0000 Yong Ma wrote: > >Thank you! I did as that but came across some problems,these are the jobs and the errors: > > 1) I copyed the files to the sys/dev/mydevice and added "dev/mydevice/mydevice.c optinonal mydevice" in the file /usr/src/sys/conf/files.i386, > At one stage you could add your own file called "files.MYKERNEL", where MYKERNEL is in the name given in the 'ident' line of the "MYKERNEL" file. I have not checked if this still works, but it stops you frm having to edit the supplied "files" and "files.i386" files. From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 16 21:40:48 2005 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.ORG 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 69BEC16A41F for ; Wed, 16 Nov 2005 21:40:48 +0000 (GMT) (envelope-from dirkx@webweaving.org) Received: from skutsje.san.webweaving.org (skutsje.san.webweaving.org [209.132.96.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id 10B0443D46 for ; Wed, 16 Nov 2005 21:40:45 +0000 (GMT) (envelope-from dirkx@webweaving.org) Received: from dyn-217.leiden.webweaving.org (53551666.cable.casema.nl [83.85.22.102]) by skutsje.san.webweaving.org (8.12.9/8.12.9) with ESMTP id jAGLeg9H025914 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 16 Nov 2005 13:40:45 -0800 (PST) (envelope-from dirkx@webweaving.org) Received: from localhost (localhost [127.0.0.1]) by dyn-217.leiden.webweaving.org (Postfix) with ESMTP id 361F640F07E for ; Wed, 16 Nov 2005 22:40:52 +0100 (CET) Date: Wed, 16 Nov 2005 22:40:51 +0100 (CET) From: Dirk-Willem van Gulik X-X-Sender: dirkx@gprs133.anywi.koole.com To: freebsd-hackers@FreeBSD.ORG Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Subject: "Sierra Wireless" "AC710/AC750" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2005 21:40:48 -0000 Besides the AC775 card tested earlier ( "Sierra Wireless" "AC755") both the AC710 and the AC750 card have now also been tested with the previous quirckset from OpenBSD. They both work (but do add somethign to cp4ticks in sio(4) to get enough buffer). Dw From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 16 22:06:06 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 594B416A420 for ; Wed, 16 Nov 2005 22:06:06 +0000 (GMT) (envelope-from dirkx@webweaving.org) Received: from skutsje.san.webweaving.org (skutsje.san.webweaving.org [209.132.96.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0013443D46 for ; Wed, 16 Nov 2005 22:06:05 +0000 (GMT) (envelope-from dirkx@webweaving.org) Received: from skutsje.san.webweaving.org (skutsje.san.webweaving.org [209.132.96.45] (may be forged)) by skutsje.san.webweaving.org (8.12.9/8.12.9) with ESMTP id jAGM659H026791 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 16 Nov 2005 14:06:05 -0800 (PST) (envelope-from dirkx@webweaving.org) Received: from localhost (dirkx@localhost) by skutsje.san.webweaving.org (8.12.9/8.12.9/Submit) with ESMTP id jAGM6517026788 for ; Wed, 16 Nov 2005 14:06:05 -0800 (PST) (envelope-from dirkx@webweaving.org) X-Authentication-Warning: skutsje.san.webweaving.org: dirkx owned process doing -bs Date: Wed, 16 Nov 2005 14:06:05 -0800 (PST) From: Dirk-Willem van Gulik X-X-Sender: dirkx@skutsje.san.webweaving.org To: freebsd-hackers@freebsd.org In-Reply-To: Message-ID: <20051116140145.V22890@skutsje.san.webweaving.org> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Dealing with silo overflow and interrupt-level buffer overflow in sio(4) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2005 22:06:06 -0000 I found that for virtually all GPRS and UMTS cards I tried that I get so many interopt and silo overflow errors as to virtually make the card unusable. Attached patch below allows one to increase the buffer a bit; relative to the speed of the connection. Thanks, Dw. *** sio.c.orig Wed Nov 16 21:49:23 2005 --- sio.c Wed Nov 16 21:57:46 2005 *************** *** 1906,1911 **** --- 1907,1915 ---- return (0); } + + static int cp4tick_rate = 4; + TUNABLE_INT("machdep.sio.cp4tick_rate", &cp4tick_rate); /* * This function must be called with the sio_lock mutex released and will * return with it obtained. *************** *** 1926,1932 **** * (about 3 ticks if input flow control is not used or not honoured, * but a bit less for CS5-CS7 modes). */ ! cp4ticks = 40 * speed / 10 / hz * 4; for (ibufsize = 128; ibufsize < cp4ticks;) ibufsize <<= 1; if (ibufsize == com->ibufsize) { --- 1930,1936 ---- * (about 3 ticks if input flow control is not used or not honoured, * but a bit less for CS5-CS7 modes). */ ! cp4ticks = (cp4tick_rate ? cp4tick_rate : 4) * speed / 10 / hz; for (ibufsize = 128; ibufsize < cp4ticks;) ibufsize <<= 1; if (ibufsize == com->ibufsize) {root@builld-jv# diff -c sio.4.orig sio.4 *** sio.4.orig Wed Nov 16 21:57:33 2005 --- sio.4 Wed Nov 16 22:02:04 2005 *************** *** 363,368 **** --- 363,381 ---- .Pp The device numbers are made from the set [0-9a-v] so that more than 10 ports can be supported. + .Sh TUNABLES + The driver supports the following tunable parameters, which may be + added to + .Pa /boot/loader.conf + or set via the + .Xr sysctl 8 + command: + .Bl -tag -width ".Cm machdep.sio.cp4tick_rate " -compact + .It Cm machdep.sio.cp4tick_rate + Rate by which to increase the buffer ti handle softtty interrupt + latency. Default value is 4; to deal with about 2-3 ticks without + loss of throughput or data. + .El .Sh DIAGNOSTICS .Bl -diag .It sio%d: silo overflow. *************** *** 370,382 **** .El .Bl -diag .It sio%d: interrupt-level buffer overflow. ! Problem in the bottom half of the driver. .El .Bl -diag .It sio%d: tty-level buffer overflow. Problem in the application. Input has arrived faster than the given module could process it ! and some has been lost. .El .\" .Bl -diag .\" .It sio%d: reduced fifo trigger level to %d. --- 383,395 ---- .El .Bl -diag .It sio%d: interrupt-level buffer overflow. ! Problem in the bottom half of the driver. Try increasing machdep.sio.cp4tick_rate. .El .Bl -diag .It sio%d: tty-level buffer overflow. Problem in the application. Input has arrived faster than the given module could process it ! and some has been lost. Try increasing machdep.sio.cp4tick_rate. .El .\" .Bl -diag .\" .It sio%d: reduced fifo trigger level to %d. From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 17 02:34:15 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 2163E16A41F; Thu, 17 Nov 2005 02:34:15 +0000 (GMT) (envelope-from mayong@mail.com) Received: from ws1-4.us4.outblaze.com (ws1-4.us4.outblaze.com [205.158.62.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id D82F543D49; Thu, 17 Nov 2005 02:34:14 +0000 (GMT) (envelope-from mayong@mail.com) Received: by ws1-4.us4.outblaze.com (Postfix, from userid 1001) id 8A2C21642FE; Thu, 17 Nov 2005 02:34:14 +0000 (GMT) Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 From: "Yong Ma" To: "M. Warner Losh" , jhb@freebsd.org Date: Wed, 16 Nov 2005 21:34:14 -0500 Received: from [159.226.5.225] by ws1-4.us4.outblaze.com with http for mayong@mail.com; Wed, 16 Nov 2005 21:34:14 -0500 X-Originating-Ip: 159.226.5.225 X-Originating-Server: ws1-4.us4.outblaze.com Message-Id: <20051117023414.8A2C21642FE@ws1-4.us4.outblaze.com> Cc: freebsd-hackers@freebsd.org, freebsd-drivers@freebsd.org Subject: Re: How to make my new driver be configurable in the kernel configuration file? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2005 02:34:15 -0000 >=20 > Usually that's spelled '#include ' since it > is relative to one of the -I paths. In practice, however, it rarely > makes a difference. >=20 > Warner Yes,it works.I made it as a "standard".but I want to make it as a "optional= " so I can config it in the kernel configuration file(MYKERNEL) as "device= mydevice" to decide whether it will be load when system boots. It seemed not enough only add a line "dev/mydevice/mycevice.c optional= device" in sys/conf/files.i386 .There will be a syntax error when c= onfig MYKERNEL. Something else needed? Thanks a lot! Yong Ma --=20 ___________________________________________________ Play 100s of games for FREE! http://games.mail.com/ From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 17 14:17:44 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 6704A16A41F for ; Thu, 17 Nov 2005 14:17:44 +0000 (GMT) (envelope-from Jose-Marcio.Martins@ensmp.fr) Received: from mar92-6-82-226-38-60.fbx.proxad.net (mar92-6-82-226-38-60.fbx.proxad.net [82.226.38.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id 793D043D49 for ; Thu, 17 Nov 2005 14:17:37 +0000 (GMT) (envelope-from Jose-Marcio.Martins@ensmp.fr) Received: from [127.0.0.1] (localhost. [127.0.0.1]) by joe.j-chkmail.org (sendmail X.0.0.0.0) with ESMTP id S000000000000149D01; Thu, 17 Nov 2005 15:17:39 +0100 Message-ID: <437C9102.7070909@ensmp.fr> Date: Thu, 17 Nov 2005 15:17:38 +0100 From: Jose Marcio Martins da Cruz User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050511 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org X-Enigmail-Version: 0.92.0.0 Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms090909000900000902000309" Subject: res_nXXX function X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jose-Marcio.Martins@ensmp.fr List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2005 14:17:44 -0000 This is a cryptographically signed message in MIME format. --------------ms090909000900000902000309 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hello, It seems that FreeBSD doesn't have reentrant versions of DNS query functions (res_nXXX, ...). What's the best and easiest way to be able to use these functions on a FreeBSD application ? Thanks for the replies Jose --------------ms090909000900000902000309 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJwDCC BNwwggLEoAMCAQICAwD1ZzANBgkqhkiG9w0BAQQFADB5MRAwDgYDVQQKEwdSb290IENBMR4w HAYDVQQLExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNVBAMTGUNBIENlcnQgU2lnbmlu ZyBBdXRob3JpdHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2FjZXJ0Lm9yZzAeFw0wNTAz MDIyMTQ3MjlaFw0wNjAzMDIyMTQ3MjlaMFMxJDAiBgNVBAMTG0pvc2UtTWFyY2lvIE1hcnRp bnMgZGEgQ3J1ejErMCkGCSqGSIb3DQEJARYcSm9zZS1NYXJjaW8uTWFydGluc0BlbnNtcC5m cjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMyu8K6aUJMX2ZJP69UGRaB/gZ2W FzSXUpLmA+1lNGlc40X8D6N9mTwWX/IpI1Ppcxd9QYOBLm2M2Atc7IjV78MXj75dGYbOT0Dz YUovwoTGhKOYg18VIuxQ4rinGEI8eIqX6gMJ/Ftzox3H/og04AiIZxyMClAjuV5QFN7FRRtI uYGYgLaT+Hq5Q2LXizthF0ewXBfqH1GmJFyErhjkxWQTH4Dq8oFZuRnWA4V2Y30Ss6dn1mjx ySA3AsMaMNQTAZssa6R0BOqAFui3vm58zghLL23Mp5De2bpM83Y2mA8yqMEsF0DWr8Hi40a8 6xCYZHqKtTVxjeXqVRv5OxF8J/sCAwEAAaOBkjCBjzAMBgNVHRMBAf8EAjAAMFYGCWCGSAGG +EIBDQRJFkdUbyBnZXQgeW91ciBvd24gY2VydGlmaWNhdGUgZm9yIEZSRUUgaGVhZCBvdmVy IHRvIGh0dHA6Ly93d3cuQ0FjZXJ0Lm9yZzAnBgNVHREEIDAegRxKb3NlLU1hcmNpby5NYXJ0 aW5zQGVuc21wLmZyMA0GCSqGSIb3DQEBBAUAA4ICAQAicgOjgV0t6WLPCVJUgLGmcrUdtHPI Ee0zJ2DX/44WKngsaEXMrMMLvE93rFW77BgusUraW/uOF/phFoVBSgrTm/Iy10ixaSlWYad3 S+SqDjkDFOuK1LQwuQxQNj8Rjn+mTAi1EUTcM0xm0hBRQQueFjNOgu6wDoCKLSniHyjUtokY radIb4TGgoE0fmOQQz0n8ehysoerdIjaqmFK0pd8zEC914f7uhhdKCnzESuKg3Q9HxzjdcJD HCC+oNgWf504029HsnjnOkg7GS/jSqWxxWmHhAfJjKlLEM2BEPM7I7h/TEYqgbRGzFIba/RT 0HUYYKpVxTaUBp8XaupVBYzr3eHOxwKIsAtIW8N8qmbjAlRVSS+5wx5bjL04mVKUdq3kOVDx ESuTo086buVJ2+ntJ7sF6s1bynenOzDDOi5t4itkOKyZr7+MqSJQrqMX2J9TawP75KiN1uz7 llc8ShDm2kZijKmOAbUC8TeecoU9w+9H9aT1jbUYp2Q4hMmkVKZrbAlox67isPEZlgT4NCqY w2yJOz7tPXhNcIRFaQ50AZGaF0VJTKyDpyLiqAyOxJ1Smaa2ZhvI2w1b0JQcu7QCz4x/EI3r 4Uq8q+I8s5ghOq25NtdeJXQgS563S0eH1FHcgIC6B7l8QV5z9mWmWnUs9w7wxMiIMI6OQX7q gu3oKzCCBNwwggLEoAMCAQICAwD1ZzANBgkqhkiG9w0BAQQFADB5MRAwDgYDVQQKEwdSb290 IENBMR4wHAYDVQQLExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNVBAMTGUNBIENlcnQg U2lnbmluZyBBdXRob3JpdHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2FjZXJ0Lm9yZzAe Fw0wNTAzMDIyMTQ3MjlaFw0wNjAzMDIyMTQ3MjlaMFMxJDAiBgNVBAMTG0pvc2UtTWFyY2lv IE1hcnRpbnMgZGEgQ3J1ejErMCkGCSqGSIb3DQEJARYcSm9zZS1NYXJjaW8uTWFydGluc0Bl bnNtcC5mcjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMyu8K6aUJMX2ZJP69UG RaB/gZ2WFzSXUpLmA+1lNGlc40X8D6N9mTwWX/IpI1Ppcxd9QYOBLm2M2Atc7IjV78MXj75d GYbOT0DzYUovwoTGhKOYg18VIuxQ4rinGEI8eIqX6gMJ/Ftzox3H/og04AiIZxyMClAjuV5Q FN7FRRtIuYGYgLaT+Hq5Q2LXizthF0ewXBfqH1GmJFyErhjkxWQTH4Dq8oFZuRnWA4V2Y30S s6dn1mjxySA3AsMaMNQTAZssa6R0BOqAFui3vm58zghLL23Mp5De2bpM83Y2mA8yqMEsF0DW r8Hi40a86xCYZHqKtTVxjeXqVRv5OxF8J/sCAwEAAaOBkjCBjzAMBgNVHRMBAf8EAjAAMFYG CWCGSAGG+EIBDQRJFkdUbyBnZXQgeW91ciBvd24gY2VydGlmaWNhdGUgZm9yIEZSRUUgaGVh ZCBvdmVyIHRvIGh0dHA6Ly93d3cuQ0FjZXJ0Lm9yZzAnBgNVHREEIDAegRxKb3NlLU1hcmNp by5NYXJ0aW5zQGVuc21wLmZyMA0GCSqGSIb3DQEBBAUAA4ICAQAicgOjgV0t6WLPCVJUgLGm crUdtHPIEe0zJ2DX/44WKngsaEXMrMMLvE93rFW77BgusUraW/uOF/phFoVBSgrTm/Iy10ix aSlWYad3S+SqDjkDFOuK1LQwuQxQNj8Rjn+mTAi1EUTcM0xm0hBRQQueFjNOgu6wDoCKLSni HyjUtokYradIb4TGgoE0fmOQQz0n8ehysoerdIjaqmFK0pd8zEC914f7uhhdKCnzESuKg3Q9 HxzjdcJDHCC+oNgWf504029HsnjnOkg7GS/jSqWxxWmHhAfJjKlLEM2BEPM7I7h/TEYqgbRG zFIba/RT0HUYYKpVxTaUBp8XaupVBYzr3eHOxwKIsAtIW8N8qmbjAlRVSS+5wx5bjL04mVKU dq3kOVDxESuTo086buVJ2+ntJ7sF6s1bynenOzDDOi5t4itkOKyZr7+MqSJQrqMX2J9TawP7 5KiN1uz7llc8ShDm2kZijKmOAbUC8TeecoU9w+9H9aT1jbUYp2Q4hMmkVKZrbAlox67isPEZ lgT4NCqYw2yJOz7tPXhNcIRFaQ50AZGaF0VJTKyDpyLiqAyOxJ1Smaa2ZhvI2w1b0JQcu7QC z4x/EI3r4Uq8q+I8s5ghOq25NtdeJXQgS563S0eH1FHcgIC6B7l8QV5z9mWmWnUs9w7wxMiI MI6OQX7qgu3oKzGCA4cwggODAgEBMIGAMHkxEDAOBgNVBAoTB1Jvb3QgQ0ExHjAcBgNVBAsT FWh0dHA6Ly93d3cuY2FjZXJ0Lm9yZzEiMCAGA1UEAxMZQ0EgQ2VydCBTaWduaW5nIEF1dGhv cml0eTEhMB8GCSqGSIb3DQEJARYSc3VwcG9ydEBjYWNlcnQub3JnAgMA9WcwCQYFKw4DAhoF AKCCAdswGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMDUxMTE3 MTQxNzM4WjAjBgkqhkiG9w0BCQQxFgQUythgSG+cbgIUuE1/eqfT7f92r9gwUgYJKoZIhvcN AQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYF Kw4DAgcwDQYIKoZIhvcNAwICASgwgZEGCSsGAQQBgjcQBDGBgzCBgDB5MRAwDgYDVQQKEwdS b290IENBMR4wHAYDVQQLExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNVBAMTGUNBIENl cnQgU2lnbmluZyBBdXRob3JpdHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2FjZXJ0Lm9y ZwIDAPVnMIGTBgsqhkiG9w0BCRACCzGBg6CBgDB5MRAwDgYDVQQKEwdSb290IENBMR4wHAYD VQQLExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNVBAMTGUNBIENlcnQgU2lnbmluZyBB dXRob3JpdHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2FjZXJ0Lm9yZwIDAPVnMA0GCSqG SIb3DQEBAQUABIIBALqsiNht64mRB/fyoJ3X3fTrWaUjEvp3qLI6FdrpRUMrjS3I0uh0dsAc UJ5iEJRPzi5QjTVM+dN+Gvz/kY6yaYDHQEN3npvycjmvKX6/xHbnzqjvTd8ZWOfWKn3J8Vs+ ISORGbGj8UFkNx0fdxm3Fy0hcN3iEfsAwkjX9Re+ajOR13IL/1pwRXyvNJmSwygOroKZYI91 tGYEOxgD/rk65j94trzSLPNtwfgtr3M7agaNlz4znv21/PKDGCo2r5WdaFqbXmvW78t9XidG zu79xkye6DTNEtE7d35rIDlwxK8etPRBED1354RamR+L4E+dSFkgL3VSk3NUdjLr4tT8HccA AAAAAAA= --------------ms090909000900000902000309-- From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 17 15:07:50 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 009B916A41F for ; Thu, 17 Nov 2005 15:07:50 +0000 (GMT) (envelope-from rools.ster@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D18243D49 for ; Thu, 17 Nov 2005 15:07:48 +0000 (GMT) (envelope-from rools.ster@gmail.com) Received: by xproxy.gmail.com with SMTP id t15so1778194wxc for ; Thu, 17 Nov 2005 07:07:48 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=KO4giKTmWdCsB9oDzwF+Rhk27+UTJ/4kXzpFd3salHxX7IInSo79pK9IWhjMOCJXWpx0kmi4C6+BrHcrnxf/GNL5d1Mi/fvjfZXYyFdD14zwm1F/HGsUsYqW6gmPgny4SDBCFfDJHMdEa5rg7zJJpdaz+ShnhdheYqt+qy1bI7M= Received: by 10.65.126.9 with SMTP id d9mr4037396qbn; Thu, 17 Nov 2005 07:07:48 -0800 (PST) Received: by 10.64.76.16 with HTTP; Thu, 17 Nov 2005 07:07:48 -0800 (PST) Message-ID: Date: Thu, 17 Nov 2005 15:07:48 +0000 From: Cornelis Swanepoel To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Filesystem monitoring question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2005 15:07:50 -0000 I have a FreeBSD 6.0 box with a partition that is accessible to a number of clients via SMB and NFS. I would like to monitor activity on this partition so that every time a write to it is completed, my C program is run (which stats the file and stores some info about it in a database amongst other things) My question is: What do I need to learn in order to construct a trigger for my code? If anyone can point me in the right direction I would greatly appreciate it= . Thanks Cornelis From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 17 16:05:04 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 3BEEE16A428; Thu, 17 Nov 2005 16:05:04 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 84CB143D46; Thu, 17 Nov 2005 16:05:03 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 2123115 for multiple; Thu, 17 Nov 2005 11:04:46 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jAHG4YTe022588; Thu, 17 Nov 2005 11:04:40 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: "Yong Ma" Date: Thu, 17 Nov 2005 10:55:46 -0500 User-Agent: KMail/1.8.2 References: <20051117023414.8A2C21642FE@ws1-4.us4.outblaze.com> In-Reply-To: <20051117023414.8A2C21642FE@ws1-4.us4.outblaze.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511171055.47539.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: freebsd-hackers@freebsd.org, freebsd-drivers@freebsd.org Subject: Re: How to make my new driver be configurable in the kernel configuration file? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2005 16:05:04 -0000 On Wednesday 16 November 2005 09:34 pm, Yong Ma wrote: > > Usually that's spelled '#include ' since it > > is relative to one of the -I paths. In practice, however, it rarely > > makes a difference. > > > > Warner > > Yes,it works.I made it as a "standard".but I want to make it as a > "optional" so I can config it in the kernel configuration file(MYKERNEL) > as "device mydevice" to decide whether it will be load when system boots. > > It seemed not enough only add a line "dev/mydevice/mycevice.c optional > device" in sys/conf/files.i386 .There will be a syntax error when > config MYKERNEL. Something else needed? No, that's all that's needed. Perhaps you can post your diff against files.i386 and the line from MYKERNEL that is causing the error? -- 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 17 16:18:01 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 4048B16A41F for ; Thu, 17 Nov 2005 16:18:01 +0000 (GMT) (envelope-from xride@x12.dk) Received: from swip.net (mailfe08.swip.net [212.247.154.225]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9636643D4C for ; Thu, 17 Nov 2005 16:18:00 +0000 (GMT) (envelope-from xride@x12.dk) X-T2-Posting-ID: lkM/Dn7LTUP9vUt2XCoVCw== Received: from x12.dk ([83.72.97.237] verified) by mailfe08.swip.net (CommuniGate Pro SMTP 5.0.1) with ESMTP id 13470929; Thu, 17 Nov 2005 17:17:59 +0100 Received: from localhost (unknown [127.0.0.1]) by x12.dk (Postfix) with ESMTP id 936DD50818; Thu, 17 Nov 2005 17:17:58 +0100 (CET) Received: from x12.dk ([127.0.0.1]) by localhost (x12.dk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 00167-04; Thu, 17 Nov 2005 17:16:36 +0100 (CET) Received: from x12.dk (localhost [127.0.0.1]) by x12.dk (Postfix) with ESMTP; Thu, 17 Nov 2005 17:16:36 +0100 (CET) Received: from localhost (xride@localhost) by x12.dk (8.13.3/8.13.3/Submit) with ESMTP id jAHGGZEd000359; Thu, 17 Nov 2005 17:16:35 +0100 (CET) (envelope-from xride@x12.dk) Date: Thu, 17 Nov 2005 17:16:35 +0100 (CET) From: Soeren Straarup To: Cornelis Swanepoel In-Reply-To: Message-ID: <20051117171543.A39634@x12.dk> References: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-600370571-1132244195=:39634" X-Virus-Scanned: amavisd-new at x12.dk Cc: freebsd-hackers@freebsd.org Subject: Re: Filesystem monitoring question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2005 16:18:01 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-600370571-1132244195=:39634 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Thu, 17 Nov 2005, Cornelis Swanepoel wrote: > I have a FreeBSD 6.0 box with a partition that is accessible to a number = of > clients via SMB and NFS. > > I would like to monitor activity on this partition so that every time a > write to it is completed, my C program is run (which stats the file and > stores some info about it in a database amongst other things) > > My question is: What do I need to learn in order to construct a trigger f= or > my code? > > If anyone can point me in the right direction I would greatly appreciate = it. > > Thanks > > Cornelis I don't know if this is what your looking for: /usr/src/usr.sbin/gstat \S=F8ren Soeren Straarup | aka OZ2DAK aka Xride FreeBSD wannabe | FreeBSD since 2.2.6-R 'We wanted to believe. But the tools had been taken away..' Mulder --0-600370571-1132244195=:39634-- From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 17 16:30:20 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 69F8516A41F for ; Thu, 17 Nov 2005 16:30:20 +0000 (GMT) (envelope-from gpt@tirloni.org) Received: from srv-03.bs2.com.br (srv-03.bs2.com.br [200.203.183.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D8B943D96 for ; Thu, 17 Nov 2005 16:30:08 +0000 (GMT) (envelope-from gpt@tirloni.org) Received: from localhost (localhost.bs2.com.br [127.0.0.1]) by srv-03.bs2.com.br (Postfix) with ESMTP id A217C4AEC5; Thu, 17 Nov 2005 14:32:02 -0200 (BRST) Received: from [172.16.12.101] (unknown [201.15.215.182]) by srv-03.bs2.com.br (Postfix) with ESMTP id 097A14B1DC; Thu, 17 Nov 2005 14:31:49 -0200 (BRST) Message-ID: <437CB004.2000401@tirloni.org> Date: Thu, 17 Nov 2005 14:29:56 -0200 From: "Giovanni P. Tirloni" User-Agent: Mozilla Thunderbird 1.0.7-1.1.fc4 (X11/20050929) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Cornelis Swanepoel References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: Filesystem monitoring question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2005 16:30:20 -0000 Cornelis Swanepoel wrote: > I have a FreeBSD 6.0 box with a partition that is accessible to a number of > clients via SMB and NFS. > > I would like to monitor activity on this partition so that every time a > write to it is completed, my C program is run (which stats the file and > stores some info about it in a database amongst other things) > > My question is: What do I need to learn in order to construct a trigger for > my code? > > If anyone can point me in the right direction I would greatly appreciate it. Using kqueue you can monitor a file/directory for changes and have it trigger something when that event happens. But you want to monitor you whole partition.. perhaps intercept some syscalls ? -- Giovanni P. Tirloni http://blog.tirloni.org From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 17 17:15:14 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 00A5816A420 for ; Thu, 17 Nov 2005 17:15:13 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id B174143D49 for ; Thu, 17 Nov 2005 17:15:13 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id DAD4B46BCA; Thu, 17 Nov 2005 12:15:12 -0500 (EST) Date: Thu, 17 Nov 2005 17:15:12 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: "Giovanni P. Tirloni" In-Reply-To: <437CB004.2000401@tirloni.org> Message-ID: <20051117171414.L77687@fledge.watson.org> References: <437CB004.2000401@tirloni.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org, Cornelis Swanepoel Subject: Re: Filesystem monitoring question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2005 17:15:14 -0000 On Thu, 17 Nov 2005, Giovanni P. Tirloni wrote: > Using kqueue you can monitor a file/directory for changes and have it > trigger something when that event happens. But you want to monitor you > whole partition.. perhaps intercept some syscalls ? Depending on your requirements, you may be able to use ktrace(1) to monitor the path lookups of all processes on the system by logging them to a file and tracking the file. With Audit support, shortly to be imported into the tree, you'll be able to do similar things, although in a more configurable way. Robert N M Watson From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 17 17:24:09 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 5613216A41F; Thu, 17 Nov 2005 17:24:09 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D58A43D45; Thu, 17 Nov 2005 17:24:07 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id jAHHO6GC022081; Thu, 17 Nov 2005 11:24:06 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <437CBCAD.3080600@centtech.com> Date: Thu, 17 Nov 2005 11:23:57 -0600 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051021 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Robert Watson References: <437CB004.2000401@tirloni.org> <20051117171414.L77687@fledge.watson.org> In-Reply-To: <20051117171414.L77687@fledge.watson.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.82/1177/Thu Nov 17 02:35:37 2005 on mh2.centtech.com X-Virus-Status: Clean Cc: freebsd-hackers@freebsd.org Subject: Re: Filesystem monitoring question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2005 17:24:09 -0000 Robert Watson wrote: > > On Thu, 17 Nov 2005, Giovanni P. Tirloni wrote: > >> Using kqueue you can monitor a file/directory for changes and have it >> trigger something when that event happens. But you want to monitor you >> whole partition.. perhaps intercept some syscalls ? > > > Depending on your requirements, you may be able to use ktrace(1) to > monitor the path lookups of all processes on the system by logging them > to a file and tracking the file. > > With Audit support, shortly to be imported into the tree, you'll be able > to do similar things, although in a more configurable way. This got me thinking - what would be the appropriate way for someone to have the kernel dump filesystem info to a userland process? What I'm wondering, is if one could wedge in some parts to the vfs code, that spits out things like vnode, vnop, etc, to a place where a userland app could listen and do something with that info. It would have to be a path that would cause the least delay in dumping the data of course, perhaps a /dev/ device entry, or unix domain socket? Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 17 18:30:08 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 4B23E16A41F for ; Thu, 17 Nov 2005 18:30:08 +0000 (GMT) (envelope-from rools.ster@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0DD7F43D75 for ; Thu, 17 Nov 2005 18:30:00 +0000 (GMT) (envelope-from rools.ster@gmail.com) Received: by wproxy.gmail.com with SMTP id i32so1859844wra for ; Thu, 17 Nov 2005 10:30:00 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=BndoL2oL4CInmv7nfgzPxxYh0A2bkrXcsrWgWxouQe5hB44Vuknu7vMUsp4a1SDliKM5HOhmlQC3rpraJJDzLpvTW9n7yglVfNUty/koXl4BVedHOBtZykLawtA6T0GU1FAEYRVIwrEM0L77T+F4+8JMYeS67kYhrcxFmaN3+VQ= Received: by 10.65.196.17 with SMTP id y17mr165551qbp; Thu, 17 Nov 2005 10:29:59 -0800 (PST) Received: by 10.64.76.16 with HTTP; Thu, 17 Nov 2005 10:29:59 -0800 (PST) Message-ID: Date: Thu, 17 Nov 2005 18:29:59 +0000 From: Cornelis Swanepoel To: "Giovanni P. Tirloni" In-Reply-To: <437CB004.2000401@tirloni.org> MIME-Version: 1.0 References: <437CB004.2000401@tirloni.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers@freebsd.org Subject: Re: Filesystem monitoring question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2005 18:30:08 -0000 > > > Using kqueue you can monitor a file/directory for changes and have it > trigger something when that event happens. But you want to monitor you > whole partition.. perhaps intercept some syscalls ? > > Thanks a bunch for the replies, I'll do some more homework on all 3 options= . At least I know where to start now. Thanks again Cornelis From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 17 18:40:32 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 9378116A41F for ; Thu, 17 Nov 2005 18:40:32 +0000 (GMT) (envelope-from sebastien.bourdeauducq@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id D980E43D46 for ; Thu, 17 Nov 2005 18:40:31 +0000 (GMT) (envelope-from sebastien.bourdeauducq@gmail.com) Received: by zproxy.gmail.com with SMTP id j2so2031777nzf for ; Thu, 17 Nov 2005 10:40:31 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:to:subject:date:user-agent:cc:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=Wkm3u7LcPB0TJ6IrXgUU4hBLDmAFJm+7NgcPrqdr7pX6tkkdJIJQFNm6Z7TisxwMrgOnpgJCN56i/rqcwohpN5qNTvSxxwRu79a10cvI1THhz5VJU/iar2ck1fHahx4J7XtoMAtKahNNJ7GZGw1G1d07DX9f0kGJg/8udN4czB4= Received: by 10.64.250.1 with SMTP id x1mr2110605qbh; Thu, 17 Nov 2005 10:40:26 -0800 (PST) Received: from oasis ( [82.231.252.157]) by mx.gmail.com with ESMTP id q16sm3483719qbq.2005.11.17.10.40.24; Thu, 17 Nov 2005 10:40:25 -0800 (PST) From: Sebastien To: John Baldwin Date: Thu, 17 Nov 2005 19:44:54 +0100 User-Agent: KMail/1.8.2 References: <200511121400.02075.sebastien.bourdeauducq@gmail.com> <200511141219.49573.jhb@freebsd.org> In-Reply-To: <200511141219.49573.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511171944.55256.sebastien.bourdeauducq@gmail.com> Cc: freebsd-hackers@freebsd.org Subject: Re: Trigerring a taskqueue from the if_start routine crashes FreeBSD6 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2005 18:40:32 -0000 > I don't see anything in output_layer.c output_layer was OK. I finally managed to track down this bug : it is not in the taskqueue system, but sending the incrimined frames enables the device to receive packets, and the bug was in the RX path. Its randomness was because the crash depended on wireless APs around... > Note that it's ok to hold locks > over a call to free() so that your output_free() routine could be > simplified somewhat: Ok, applied. Thanks. Sebastien From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 17 19:56:07 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 915E016A41F for ; Thu, 17 Nov 2005 19:56:07 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 22D8543D46 for ; Thu, 17 Nov 2005 19:56:07 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id jAHJrcSS071175; Thu, 17 Nov 2005 12:53:40 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Thu, 17 Nov 2005 12:53:43 -0700 (MST) Message-Id: <20051117.125343.88816998.imp@bsdimp.com> To: dirkx@webweaving.org From: "M. Warner Losh" In-Reply-To: <20051116140145.V22890@skutsje.san.webweaving.org> References: <20051116140145.V22890@skutsje.san.webweaving.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Thu, 17 Nov 2005 12:53:40 -0700 (MST) Cc: freebsd-hackers@freebsd.org Subject: Re: Dealing with silo overflow and interrupt-level buffer overflow in sio(4) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2005 19:56:07 -0000 How does this help with interrupt level overflows? Warner From owner-freebsd-hackers@FreeBSD.ORG Fri Nov 18 01:34:39 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 BD51916A420 for ; Fri, 18 Nov 2005 01:34:39 +0000 (GMT) (envelope-from mayong@mail.com) Received: from webmail-outgoing.us4.outblaze.com (webmail-outgoing2.us4.outblaze.com [205.158.62.67]) by mx1.FreeBSD.org (Postfix) with ESMTP id 189A343D49 for ; Fri, 18 Nov 2005 01:34:39 +0000 (GMT) (envelope-from mayong@mail.com) Received: from unknown (unknown [192.168.9.180]) by webmail-outgoing.us4.outblaze.com (Postfix) with QMQP id 4B6B8180013F for ; Fri, 18 Nov 2005 01:34:38 +0000 (GMT) X-OB-Received: from unknown (205.158.62.55) by wfilter.us4.outblaze.com; 18 Nov 2005 01:34:38 -0000 Received: by ws1-3.us4.outblaze.com (Postfix, from userid 1001) id 3ACAE101E6; Fri, 18 Nov 2005 01:34:38 +0000 (GMT) Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 From: "Yong Ma" To: "John Baldwin" Date: Thu, 17 Nov 2005 20:34:37 -0500 Received: from [159.226.5.225] by ws1-3.us4.outblaze.com with http for mayong@mail.com; Thu, 17 Nov 2005 20:34:37 -0500 X-Originating-Ip: 159.226.5.225 X-Originating-Server: ws1-3.us4.outblaze.com Message-Id: <20051118013438.3ACAE101E6@ws1-3.us4.outblaze.com> Cc: freebsd-hackers@freebsd.org, freebsd-drivers@freebsd.org Subject: Re: How to make my new driver be configurable in the kernel configuration file? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2005 01:34:39 -0000 ----- Original Message ----- From: "John Baldwin" To: "Yong Ma" Subject: Re: How to make my new driver be configurable in the kernel config= uration file? Date: Thu, 17 Nov 2005 10:55:46 -0500 >=20 > On Wednesday 16 November 2005 09:34 pm, Yong Ma wrote: > > > Usually that's spelled '#include ' since it > > > is relative to one of the -I paths. In practice, however, it rarely > > > makes a difference. > > > > > > Warner > > > > Yes,it works.I made it as a "standard".but I want to make it as a > > "optional" so I can config it in the kernel configuration file(MYKERNE= L) > > as "device mydevice" to decide whether it will be load when system boot= s. > > > > It seemed not enough only add a line "dev/mydevice/mycevice.c opti= onal > > device" in sys/conf/files.i386 .There will be a syntax error when > > config MYKERNEL. Something else needed? >=20 > No, that's all that's needed. Perhaps you can post your diff against > files.i386 and the line from MYKERNEL that is causing the error? >=20 > -- > John Baldwin <>< http://www.FreeBSD.org/~jhb/ > "Power Users Use the Power to Serve" =3D http://www.FreeBSD.org > _______________________________________________ > 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" Yes,and I got the reason:There wiil be a syntax error if the name behind 'd= evice' in MYKERNEL contains numbers(in the middle). so "device cryptcard" p= assed but "device sjy22b" caused error.=20 Thanks Yong --=20 ___________________________________________________ Play 100s of games for FREE! http://games.mail.com/ From owner-freebsd-hackers@FreeBSD.ORG Fri Nov 18 01:45:20 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 AFF7916A41F for ; Fri, 18 Nov 2005 01:45:20 +0000 (GMT) (envelope-from freebsdenthu@yahoo.com) Received: from web36415.mail.mud.yahoo.com (web36415.mail.mud.yahoo.com [209.191.85.150]) by mx1.FreeBSD.org (Postfix) with SMTP id 4069443D45 for ; Fri, 18 Nov 2005 01:45:20 +0000 (GMT) (envelope-from freebsdenthu@yahoo.com) Received: (qmail 21085 invoked by uid 60001); 18 Nov 2005 01:45:19 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=cqw5UkVw575kq4XulyAGb9CtRwCn1yaLy/rqoymmlkZaT616FgkdlE9hsedIvzf9Ufo9U4LvFmPSZh+YwXeIvJk1JQ2tnPFPGJOlgEFWcfMzWmg7LlC16b2b1IhKqlUgv1DOFX9s1C+eRUbMvBuFlJxG1QNT6Q5cOIME6TgedWo= ; Message-ID: <20051118014519.21083.qmail@web36415.mail.mud.yahoo.com> Received: from [216.240.27.23] by web36415.mail.mud.yahoo.com via HTTP; Thu, 17 Nov 2005 17:45:19 PST Date: Thu, 17 Nov 2005 17:45:19 -0800 (PST) From: Freebsd Enthu To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: How do I control the load address in Elf header X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2005 01:45:20 -0000 Hi, I am one of the firmware guys that is writing a Secondary Boot Loader that boots FreeBSD kernel. From what I see in the ELF header for FreeBSD kernel, the load address seems to have a value of 0x80200000 which seems to be a Virtual address for me. If I want to put the Physical address where I want the FreeBSD to go, what are the FreeeBSD files I need to change? Any help will be appreciated. Thanks --------------------------------- Yahoo! FareChase - Search multiple travel sites in one click. From owner-freebsd-hackers@FreeBSD.ORG Fri Nov 18 06:02:32 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 484B816A41F for ; Fri, 18 Nov 2005 06:02:32 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id B654C43D46 for ; Fri, 18 Nov 2005 06:02:31 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: by xproxy.gmail.com with SMTP id s9so106302wxc for ; Thu, 17 Nov 2005 22:02:31 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=TBfQH1oUN9SRigf0Fi3PUS9chXN/Z0omc3sJS9dscWSxZ6EzFjVhqcsSfxPzEnrd/TgNcmSX8bOpZViZNBK+1VL0Am/Bn/ftZk4H3/tHKX6GpNXJE9CficWfDS2Z7kqc4iFSsYpzDTqhmOsFMO21zioiODysUKSjnhS9+9XJk3M= Received: by 10.70.74.20 with SMTP id w20mr3955742wxa; Thu, 17 Nov 2005 22:02:30 -0800 (PST) Received: by 10.70.105.13 with HTTP; Thu, 17 Nov 2005 22:02:30 -0800 (PST) Message-ID: <84dead720511172202x3f45b7f3j64273dac7f64f211@mail.gmail.com> Date: Fri, 18 Nov 2005 11:32:30 +0530 From: Joseph Koshy To: Freebsd Enthu In-Reply-To: <20051118014519.21083.qmail@web36415.mail.mud.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20051118014519.21083.qmail@web36415.mail.mud.yahoo.com> Cc: freebsd-hackers@freebsd.org Subject: Re: How do I control the load address in Elf header X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2005 06:02:32 -0000 > I am one of the firmware guys that is writing a Secondary Boot Loader th= at boots > FreeBSD kernel. From what I see in the ELF header for FreeBSD kernel, the= load > address seems to have a value of 0x80200000 which seems to be a Virtual = address > for me. If I want to put the Physical address where I want the FreeBSD to= go, > what are the FreeeBSD files I need to change? See loader(8) ... /usr/src/sys/boot/* AFAIR we switch to protected mode in the loader itself. -- FreeBSD Volunteer, http://people.freebsd.org/~jkoshy From owner-freebsd-hackers@FreeBSD.ORG Fri Nov 18 09:52:50 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 7AE5A16A460 for ; Fri, 18 Nov 2005 09:52:50 +0000 (GMT) (envelope-from ume@mahoroba.org) Received: from ameno.mahoroba.org (gw4.mahoroba.org [218.45.22.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9350E44244 for ; Fri, 18 Nov 2005 09:26:15 +0000 (GMT) (envelope-from ume@mahoroba.org) Received: from localhost (IDENT:DkwlyHsQjElp2O/+gU7zbqGlHYyY6NWywg5MOGQOLVvuh/42H3RWiHcupzYQkgN4@localhost [IPv6:::1]) (user=ume mech=CRAM-MD5 bits=0) by ameno.mahoroba.org (8.13.4/8.13.4) with ESMTP/inet6 id jAI9Ox43005525 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 18 Nov 2005 18:25:00 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Fri, 18 Nov 2005 18:24:59 +0900 Message-ID: From: Hajimu UMEMOTO To: Jose-Marcio.Martins@ensmp.fr In-Reply-To: <437C9102.7070909@ensmp.fr> References: <437C9102.7070909@ensmp.fr> User-Agent: xcite1.38> Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 Emacs/21.3 (i386--freebsd) MULE/5.0 (SAKAKI) X-Operating-System: FreeBSD 5.4-STABLE X-PGP-Key: http://www.imasy.or.jp/~ume/publickey.asc X-PGP-Fingerprint: 1F00 0B9E 2164 70FC 6DC5 BF5F 04E9 F086 BF90 71FE Organization: Internet Mutual Aid Society, YOKOHAMA MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (ameno.mahoroba.org [IPv6:::1]); Fri, 18 Nov 2005 18:25:00 +0900 (JST) X-Virus-Scanned: by amavisd-new X-Virus-Status: Clean X-Spam-Status: No, score=-3.7 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on ameno.mahoroba.org Cc: freebsd-hackers@freebsd.org Subject: Re: res_nXXX function X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2005 09:52:52 -0000 Hi, >>>>> On Thu, 17 Nov 2005 15:17:38 +0100 >>>>> Jose Marcio Martins da Cruz said: Jose-Marcio> It seems that FreeBSD doesn't have reentrant versions of DNS query functions Jose-Marcio> (res_nXXX, ...). Our recent resolver is thread-safe. So we don't need to use res_n*(), basically. Sincerely, -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ From owner-freebsd-hackers@FreeBSD.ORG Fri Nov 18 12:37:06 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 8D68416A432; Fri, 18 Nov 2005 12:37:06 +0000 (GMT) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.171]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3916F43D46; Fri, 18 Nov 2005 12:37:05 +0000 (GMT) (envelope-from max@love2party.net) Received: from [84.163.238.171] (helo=donor.laier.local) by mrelayeu.kundenserver.de (node=mrelayeu3) with ESMTP (Nemesis), id 0MKxQS-1Ed5UC0xMK-0002RL; Fri, 18 Nov 2005 13:37:04 +0100 From: Max Laier To: freebsd-hackers@freebsd.org Date: Fri, 18 Nov 2005 13:36:52 +0100 User-Agent: KMail/1.8.2 MIME-Version: 1.0 Content-Type: Multipart/Mixed; boundary="Boundary-00=_rrcfDt62MW+sypK" Message-Id: <200511181336.59361.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de login:61c499deaeeba3ba5be80f48ecc83056 Cc: freebsd-current@freebsd.org Subject: FreeBSD Status Report Third Quarter 2005 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2005 12:37:06 -0000 --Boundary-00=_rrcfDt62MW+sypK Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline --Boundary-00=_rrcfDt62MW+sypK Content-Type: text/plain; charset="us-ascii"; name="report-july-2005-oct-2005.txt" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline; filename="report-july-2005-oct-2005.txt" July-October 2005 Status Report Introduction After a long, exhausting, yet very productive third quarter of 2005 FreeBSD 6.0 has been released. Many activities were put into the background in order to make this release the success it has become. Nontheless, we received a tremendous amount of reports covering various projects that either found their way into FreeBSD 6.0 already or have started to develop in, what is now known as 7-CURRENT. The EuroBSDCon and the Developer Summit in Basel next week will be a good opportunity to help some of the ideas herein to take off. Last round we had the pleasure to introduce our accepted Google Summer of Code projects. Now, that the summer is over, we are even more pleased to include reports about the outcome of these projects. Some already found their way into the tree or the general public otherwise - most ocularly the new webdesign. Unfortunately, this publication has been delayed for various reasons - the before mentioned release of 6.0 being one of them. Thus, some of the reports might no longer be as up to date as they were when we received them and we encourage you - even more this time - to also visit the weblinks to get more recent information. Thanks again to everyone who submitted reports, and our sincere apologies for running late this time. __________________________________________________________________ Google summer of code * BSD Installer * csup: cvs mode support * FreeBSD Web Site Redesign * Fuse for FreeBSD * gjournal * gvinum 'move', 'rename' support * Improve Libalias * Integrated SNMP monitoring * Interface Cleanup * launchd(8) for FreeBSD * Nsswitch / Caching daemon * SNMP Monitoring * UFS Journaling Projects * ggtrace * iSCSI Initiator * pfSense * Realtime POSIX signal Documentation * bridge.c retired * TODO list for volunteers Kernel * Low-overhead performance monitoring for FreeBSD * NEWCARD * Sound subsystem improvements * The Kernel Stress Test Suite Network infrastructure * OpenBSD dhclient import * Removable interface improvements * TCP & IP Routing Optimization Fundraise Architectures * Porting FreeBSD to the Xbox * PowerPC Port Ports * FreeBSD GNOME Project * FreshPorts * Ports Collection * Ports Tinderbox Vendor / 3rd Party Software * Cronyx/Asterisk * OpenBSD packet filter - pf Miscellaneous * BSDCan * EuroBSDCon 2005 - Basel * Problem Report Database __________________________________________________________________ bridge.c retired Contact: Max Laier Contact: Andrew Thompson As of September 27, the old bridge(4) implementation has been removed from HEAD and will not be part of FreeBSD 7 and later. FreeBSD 6 will serve as transition period. The full functional replacement if_bridge(4) is now available in FreeBSD 5 (not yet part of 5.4 however), FreeBSD 6 and -CURRENT. Any problems should be reported to Andrew Thompson, who is maintaining if_bridge in FreeBSD. Open tasks: 1. Document the change in the handbook and other reference material. __________________________________________________________________ BSD Installer URL: http://www.bsdinstaller.org/ URL: http://wikitest.freebsd.org/moin.cgi/BSDInstaller Contact: Andrew Turner By the end of August I managed to modify the release building process to build a live CD that loads the front and backends. It could install all the distfiles, install the ports tree and had minimal support to install and uninstall packages. Since the end of the Summer of Code I have worked to integrate the new Lua backend. This has been successful, with it now past the point of the BSDINSTALLER-BETA-1 release. It can install the distfiles but not the ports tree or packages yet. __________________________________________________________________ BSDCan URL: http://www.bsdcan.org/ Contact: Dan Langille We are in the process of recruiting new members for the program committee. If you would like to volunteer before you are recruited, please contact me. The dates for 2006 have been announced: May 12-13, 2006. The venue will be the same as previous events: University of Ottawa. The prices will not increase from 2005. Please start thinking about your papers. The call for papers will go out soon. __________________________________________________________________ Cronyx/Asterisk URL: http://www.cronyx.ru/hardware/wan.html URL: http://www.freebsd.org/~rik Contact: Roman Kurakin A new netgraph-to-zaptel module that allows to use E1(ISDN PRI) WAN adapters as an interface card for open source PBX - Asterisk. All you need is an adapter that able to work in raw phone mode (like Cronyx Tau-PCI/2E1), eq. without HDLC-like framing and that has support of Netgraph. __________________________________________________________________ csup: cvs mode support URL: http://wikitest.freebsd.org/moin.cgi/ChristophMathys URL: http://mu.org/~mux/csup.html Contact: Christoph Mathys During the "Summer of Code" I worked on csup (a rewrite of CVSup in C). It already supported checkout-mode, so my task was to implement support for cvs-mode. The biggest part of the project was to implement support for rcs-files. As "byproducts" I also wrote the necessary code to create nodes/hardlinks and to update files using the rsync-algorithm. For what I know, the code works fine, but errorhandling is practically inexistent. Open tasks: 1. Errors should be properly handled 2. Support to get fixups 3. The hard part to support rcs file updates is done, but there is no checksum, some options are not honored and the performance could be improved __________________________________________________________________ EuroBSDCon 2005 - Basel URL: http://www.eurobsdcon.org/ Contact: Information The fourth European BSD conference in Basel, Switzerland is a great opportunity to present new ideas to the community and to meet some of the developers behind the different BSDs. The two day conference program (Nov 26 and 27) will be complemented by a tutorial day preceeding the conference (Nov 25). The FreeBSD developers will hold a DevSummit on Nov 24 and 25, so several developers will be at the conference. The program is available for Saturday and Sunday providing very interesting FreeBSD talks and topics. Today more than 160 people from 25 countries have registered for the conference. __________________________________________________________________ =46reeBSD GNOME Project URL: http://www.FreeBSD.org/gnome/ Contact: Joe Marcus Clarke Contact: FreeBSD GNOME Team Since our last status report, we have added a new member to the team: Jean-Yves Lefort (jylefort). We have even spiced up our contact page with pictures of ourselves and in some cases, a cute hippo. And our very own Adam Weinberger (adamw) has been made a GNOME Project committer heading up the Canadian English translation project. We have finished the port GNOME 2.12 to FreeBSD. However, due to the ports slush in preparation for 6.0-RELEASE, the update has not been merged into the official ports tree. If people are eager to try out GNOME 2.12 while waiting for the ports tree to fully thaw, we have instructions on our website. GNOME 2.12 will be the first FreeBSD GNOME release not to include support for FreeBSD 4.X. While 4.X is still a very viable release for servers, it lacks many of the features needed for a Desktop Environment such as GNOME. We do plan to continue support of the GNOME development platform on 4.X, however. This includes Glib, GTK+, libgnome, etc. A new porting component will be introduced with GNOME 2.12 called, ``ltverhack''. This will help with future upgrades by keeping shared library versions from needlessly changing. The FreeBSD GNOME Project is also committed to providing our users with a solid package experience. To that end, we have extended our Tinderbox to build amd64 packages for all supported versions of FreeBSD for both the production and development releases of the GNOME Desktop. The development packages are even built with debugging symbols to better help with reporting problems. Open tasks: 1. FreeBSD needs a HAL port. HAL will be vital for both GNOME and KDE in providing FreeBSD users with a smooth, elegant desktop experience. Once GNOME 2.12 has been merged into the ports tree, work will begin on making HAL on FreeBSD a reality. Contact gnome@FreeBSD.org if you are interested in helping. 2. We need help with project documentation. In particular, we need help auditing the FAQ to make sure the content is still relevant, and we are not missing any key items. If you're interested, please contact gnome@FreeBSD.org . __________________________________________________________________ =46reeBSD Web Site Redesign URL: http://www.FreeBSD.org URL: http://www.FreeBSD.org/old Contact: Emily Boyd Contact: Murray Stokely Contact: Web Team The new website has gone live! Thanks to Emily Boyd for all her hard work. We still have a lot of work to do to integrate suggestions that have been made by users since we went live. The new CSS design makes it much easier to rapidly change the look and feel of the site, so it is easy to experiment. We're still looking for more HTML/CSS designers to help us improve the site. __________________________________________________________________ =46reshPorts URL: http://www.freshports.org/ Contact: Dan Langille I'm in the process of adding personalized newsfeeds to the website. For each of your Watch Lists, you will also have a news feed just for that watch list. Any commit to any port in your watch list will turn up on your newsfeed. This fantastic new feature is available now for your RSS pleasure at the BETA site . I've also been doing some work in the area of supporting multiple platforms and architectures. This will allow FreshPorts to correctly report that a port is broken, for example, on i386, but not the other platforms. This feature will take note of BROKEN, FORBIDDEN, and IGNORE for the following architectures: * alpha * amd64 * i386 * ia64 * sparc64 And the following OSVERSIONS (subject to upgrade as new releases come along): * 492100 * 504102 * 600033 * 700001 Upcoming changes, in addition to the above, include: 1. NOT_FOR_ARCHS 2. ONLY_FOR_ARCHS 3. IS_INTERACTIVE I've been getting useful help from those on IRC. Thanks. Open tasks: 1. Complete the above. __________________________________________________________________ =46use for FreeBSD URL: http://fuse4bsd.creo.hu/ URL: http://wikitest.freebsd.org/moin.cgi/FuseFilesystem URL: http://creo.hu/~csaba/projects/fuse4bsd/downloads/ Contact: Csaba Henk Fuse for FreeBSD is the outcome of my "ssh based networking filesystem for FreeBSD" SoC project. The kernel interface for the comprehensive userspace filesystem API provided by the ( Fuse project ) has been implemented for FreeBSD (6.x and 7.x), under the BSD license. This has the benefit of opening up the possibility of porting the rich collection of Fuse based filesystems to FreeBSD. Now it's ready for consumption by a broader audience. The sysutils/fusefs-kmod , sysutils/fusefs-libs , sysutils/fusefs-sshfs ports can be expected to be integrated into the FreeBSD ports tree in the next few days (the ports were created and are maintained by Anish Mistry, and Simon Barner's careful review also helps a lot). Open tasks: 1. Implement missing features like extended attributes and attribute/name caching (with timeout). 2. Resolve problems with autotools and integrate userspace modifications into the Fuse codebase. 3. Port Fuse based filesystems and language bindings to FreeBSD. 4. Create sysfs (Fuse based filesystem interface to sysctl). 5. Test, test, test among a broad variety of circumstances. __________________________________________________________________ ggtrace URL: http://ivoras.sharanet.org/projects/ggtrace.html Contact: Ivan Voras Ggtrace is "GEOM gate tracer", utility to track I/O requests on a storage device on FreeBSD. It uses the ggate facility of FreeBSD to attach to a file or device and produces a device that can be used for any I/O, including hosting filesystems. I/O requests are presented in the form of a moving histogram that can be used to discern which parts of the storage device are used most often. One use of ggtrace is to analyze how filesystems arrange and access data on storage devices. The project is working and usable only on the RELENG_6 branch. __________________________________________________________________ gjournal URL: http://wikitest.freebsd.org/moin.cgi/gjournal Contact: Ivan Voras Gjournal provides GEOM-level journaling and COW capabilities to storage devices. Unfortunately, it cannot be used as a substitute for filesystem journaling (fsck is still needed when gjournal device is used to host filesystems). Development has slowed down, and the existing code needs much more testing. If there is continued interest in it, I'll probably split the functionalities into two projects, one handling COW and one handling the journaling, in order to make the code cleaner. Open tasks: 1. More testing is needed. __________________________________________________________________ gvinum 'move', 'rename' support URL: http://wikitest.freebsd.org/moin.cgi/GvinumMoveRename Contact: Chris Jones Support for moving and renaming objects in gvinum was completed at the end of August 2005. All gvinum objects (drives, subdisks, plexes, and volumes) can be renamed, and subdisks can be moved from drive to drive. Also, a man page for gvinum was created. Open tasks: 1. Update FreeBSD Handbook chapter on vinum to reflect gvinum. Slowly in progress, but hopefully done by the end of the year, workload permitting. __________________________________________________________________ Improve Libalias URL: http://wikitest.freebsd.org/moin.cgi/PaoloPisati URL: http://wikitest.freebsd.org/moin.cgi/PaoloPisati Contact: Paolo Pisati The project met all the scheduled goals, and following are the new features implemented in libalias: * integration with IPFW in kernel land * support for 4.x and 5.x as kld * converted from a monolithic to a modular architecture, added the ability to load/unload at runtime support for new protocols (modules work both in kernel and user land) * added logging support in kernel land Fell free to suggest other improvements. Open tasks: 1. Test and feedback are welcome __________________________________________________________________ Integrated SNMP monitoring URL: http://people.freebsd.org/~harti/bsnmp/index.html URL: http://wikitest.freebsd.org/moin.cgi/ShteryanaShopova URL: http://wikitest.freebsd.org/moin.cgi/SnmpMonitoringModulesStatus Contact: Philip Paeps Contact: Shteryana Shopova This summer, we've had the pleasure of having two Google Summer of Code students hacking on our SNMP monitoring machinery. Victor worked on implementing the Host Resources, TCP and UDP MIBs in bsnmpd while Shteryana started on client-side SNMP tools. With these modules and tools, a FreeBSD installation can be monitored without having to install any (heavy!) third-party tools. Open tasks: 1. While the modules and the tools currently in Perforce are generally functional, they still need some tidying up (style(9)) and testing before they can be committed to CVS. At the time of this writing, the Hostres MIB is pretty much commit-ready in Perforce (//depot/user/philip/bsnmp/...), the other modules and tools live in //depot/projects/soc2005/bsnmp/... They'll be branched for tidying up and committing "Real Soon Now"[tm] 2. Testers are very welcome. :-) Please let us know about any bugs! __________________________________________________________________ Interface Cleanup URL: http://wikitest.freebsd.org/moin.cgi/CleanupOfNetworkInterfaceApisProp osal Contact: Anders Persson The dependencies to kernel-only datastructures in netstat (ifnet, etc.) have been removed almost completely (AppleTalk and IPX still needs work). In order to remove the dependencies, the debugging features of netstat had to be removed. However, a project to create a generic, modular 'data structure' examination tool is ongoing, and the debugging features factor out of netstat have been migrated to this tool. Open tasks: 1. Refactoring of the netstat code, create a modular version in the spirit of ifconfig. 2. Data structure examination tool needs to be completed, current state is more that of a prototype. __________________________________________________________________ iSCSI Initiator URL: ftp://ftp.cs.huji.ac.il/users/danny/freebsd/iscsi-12.tar.bz2 Contact: Daniel Braniss This iSCSI kernel module and its companion control program, are still under development, but the main parts seem to be working. A second round of public tests has started. Open tasks: 1. login chap authentication 2. digest 3. network disconnect recovery __________________________________________________________________ launchd(8) for FreeBSD URL: http://wikitest.freebsd.org/moin.cgi/launchd Contact: R. Tyler Ballance In short, launchd can run perfectly fine on FreeBSD, and combined with launchctl, it can be used to manage daemons through the launchctl(1) interface. Jobs can be added and managed two ways as of yet from launchctl(1). Using zarzycki@'s experimental "submit" command within launchctl(1) or by using my lame/rudimentary/etc "launcher" format (launchd/launchers/*.launch) which uses property(3) to parse out three simple, and important details. The program label, path, and any program flags. Using the "load" command, one can load the data into launchctl(1) and then start the processes with the..."start" command. Jobs can be removed/stopped with the "remove" command. The "limit" command still throws launchctl(1) into an infinite loop, and yes, I plan on fixing this. There are some things that need to be fixed, first off, some sort of boot time integration, whether as an init-replacement (i.e. PID 1, a la Mac OS X) or as the first thing started from init, that kicks all rcng things off. Along with, more importantly, a plist parser, so we can have full compatibility with Mac OS X's launchd via Core Foundation. I'm also trying to get launchd(8) relicensed with the BSD license, as opposed to the APSL, anybody with tips, or methods for achieving this goal, contact me at tyler@tamu.edu Open tasks: 1. Writing a light-weight plist (non-XML) parser with lex and yacc. __________________________________________________________________ Low-overhead performance monitoring for FreeBSD URL: http://people.freebsd.org/~jkoshy/projects/perf-measurement Contact: Joseph Koshy This projects implements a kernel module (hwpmc(4)), an application programming interface (pmc(3)) and a few simple applications (pmcstat(8) and pmccontrol(8)) for measuring system performance using event monitoring hardware in modern CPUs. The last three months have been spent in bug fixing and in tweaking the code. A few more minor features and loose ends remain to be taken care of. Once these are done, I hope to get started on a graphical performance analyser. __________________________________________________________________ NEWCARD Contact: Warner Losh Due to an email snafu, the June report was not submitted, so this report covers since the last 6 months. Summary: The 16-bit part of NEWCARD has been greatly enhanced. In addition, power control has become interrupt driven. Some drivers make use of the new functionality. The pccard layer now exports the CIS for each device that is present, even if there's no driver for the card or parts of the card. The power up and reset sequence is now interrupt driven. This has eliminated many of the long pauses that the system used to experience after a card insertion. We can not play glitch-free audio while inserting or removing a card. A number of additional cards are recognized by PC Card. In addition, drivers now can read the CIS for more information about the card. Drivers have been enhanced to read the CIS for MAC addresses and the like where appropriate. The ed driver now attaches the mii bus of the AX88190 and AX88790 fast ethernet PC Card chips. This allows better status reporting and increased functionality for PHY chips that need some help. The ed driver also supports the Tamarack TC5299J chipset (including attaching its MII bus) now, the only open source OS that does so (TC5299J cards will work with other open source OS, but they won't report their status or attach a mii bus). A number of bugs have been fixed in the pccard or cardbus drivers. Most of these changes have been merged into the forthcoming 6.0. Others will be merged after the release. Open tasks: 1. ExpressCard laptops have arrived with ExpressCard/54 and ExpressCard/34 slots. It is unknown the extent of the work necessary to support them. 2. The ISA attachment of cbb needs work to make it fully functional. 3. A CIS parser in userland needs to be written. The pccardc based CIS parser is OK, but it doesn't handle MFC cards too well. Ideally the parser would produce output that is compatible with the linux tool. 4. A mechanism for CIS override is needed. We need a tool that will take an ascii representation of the CIS and produce a binary. We need a tool that will install the binary into the kernel and kernel modifications to switch from the CIS that's in the card to the faked up CIS. 5. We need a mechanism for creating pseudo multi-function cards. Initially, it seems that all we really need is the ability for an arbitrary driver to add a sio companion, since that covers all the cases I'm aware of. Resources would need to be 'donated' from the creating driver to the sio card. 6. It would be nice if we could move to a more common CIS parsing and dispatch. The CardBus side is wide open at the moment since none of the pci drivers use the CIS information outside of a few that get their MAC address via a standard interface. 7. The ep driver needs work to make the newer ep cards that have mii bus on them actually probe and attach it. It needs to gain media support for the non-mii based cards. The 3C1 still needs work. 8. The sn driver needs work to support many of the SMC91Cxxx PC Card devices. These are typically combination cards that need special, non-standard initialization. 9. Power savings for 16-bit cards can be realized if we power them up at 3.3V rather than at 5.0V. Not all cards can support this, but many can and indicate this support in the CIS. Windows tries the 3.3V configuration entries before the 5.0V ones. We should do the same. 10. Most of the changes that have been made to the pccard and cardbus layers can be merged back into RELENG_5. __________________________________________________________________ Nsswitch / Caching daemon URL: http://wikitest.freebsd.org/moin.cgi/NsswitchAndCachingFinalReport URL: http://wikitest.freebsd.org/moin.cgi/MichaelBushkov Contact: Michael Bushkov <> The nsswitch / caching daemon project was developed within the Google's Summer Of Code program. Almost all goals of the project were achieved. Thanks to Brooks Davis and Jacques Vidrine, who were my mentors and greatly helped me. Nsswitch subsystem was extended to support new sources (services, protocols, rpc, openssh and GT4). The testing of the Globus Grid Toolkit 4 patch (which adds support for nsswitch to GT4) is still to be done. For nsswitch to support caching, the caching daemon was implemented on top of the caching library, which was also developed during the SoC. The current version of the daemon uses simple nscd-like configuration file and seems to be stable. To complete the SoC project, the experimental version of libc with in-process caching enabled was made. It's benchmarking will be done in the nearest future. There were some requests for caching daemon to be able to act like NSCD (to perform the actual nsswitch lookups by itself), so it was modified to support this feature. But current implementation has some restrictions and requires a lot of testing. Right now the final polishing is being made to the project's sources, so that they could be added to the CURRENT Open tasks: 1. Extend caching daemon to support NSCD functionality 2. Test Globus Grid Toolkit 4 patch 3. Add support for MAC and audit related configuration files to the nsswitch __________________________________________________________________ OpenBSD dhclient import Contact: Brooks Davis Contact: Sam Leffler The OpenBSD rewrite of dhclient has been imported, replacing the ISC dhclient. The OpenBSD client provides better support for roaming on wireless networks and a simpler model of operation. Instead of a single dhclient process per system, there is on per network interface. This instance automatically goes away in the even of link loss and is restarted via devd when link is reacquired. To support this change, many aspects of the network interface configuration process were overhauled. The current code works well in most circumstances, but more testing and polishing is needed. A few bug are being tracked, but most of them are edge cases. Work on further interface configuration enhancements is underway for FreeBSD 7.0. __________________________________________________________________ OpenBSD packet filter - pf Contact: Max Laier Futher improvements have been made to pfsync to make it behave well in SMP scenarios. All bug fixes have been MFCed to RELENG_5 where applicable. A couple of bugfixes and feature improvements have been imported via OpenBSD (originally suggested by FreeBSD users). As described in the last report, FreeBSD 6.0 and future RELENG_6 releases will be based on OpenBSD 3.7. Newer code will be imported as soon as 6.0 has settled down a bit. __________________________________________________________________ pfSense URL: http://www.pfsense.com Contact: Scott Ullrich pfSense is a m0n0wall derived operating system platform with radically different goals such as using Packet Filter, FreeBSD 6, ALTQ for excellent packet queueing and finally an integrated package management system for extending the environment with new features. Work continues to stabilize pfSense in preparation for the FreeBSD 6 release. Once FreeBSD 6 is released pfSense will enter the final beta and release candidate phases in preparation for the 1.0 release. Open tasks: 1. Stabilize installer (cannot load kernel errors after install) 2. Finish outgoing load balancing monitoring 3. Fix last minute bugs that turn up __________________________________________________________________ Porting FreeBSD to the Xbox URL: http://www.xbox-bsd.nl Contact: Rink Springer Contact: Ed Schouten As of 26th July 2005, it is possible to run FreeBSD on your Xbox with minor patching effort. The framebuffer has initial support; The USB ports, IDE- and audio controllers are fully supported; the only part severely lacking now is the lack of support for the NForce Ethernet controller. Currently, efforts are focussing on eliminating the XBOX kernel option and make the port self-detecting; this means the x86 and xbox kernels will be identical. The goal is to provide native xbox support in 7-CURRENT. Futhermore, a porting effort is planned from Linux' GPL-ed forcedeth.c; not only the Xbox port will benefit from this but also all NForce motherboard owners. The resulting driver could be kldload-ed to keep the kernel GPL-free. Open tasks: 1. The xbox framebuffer driver should be merged in the VESA framework, so it can use syscons(4). Assistance on this would be very welcome! __________________________________________________________________ Ports Collection URL: http://www.freebsd.org/ports/ URL: http://people.freebsd.org/~fenner/portsurvey/ URL: http://edwin.adsl.barnet.com.au/~edwin/ports/ URL: http://portsmon.FreeBSD.org/index.html URL: http://www.freebsd.org/portmgr/index.html Contact: Mark Linimon A great deal of work has gone into the Ports Collection since the last report in April, much of it behind-the-scenes. As this report was being written, the 6.0 release was ongoing. Due to the amount of time that it has taken to get 6.0 through the beta process and into RC, we have been in ports freeze or slush for more than two months. Unfortunately this has held back needed work on the ports infrastructure. The last major update to bsd.port.mk, in early May, was coordinated by Kirill Ponomarew added a number of new features and closed 15 PRs. Another similar set of changes has been tested and is ready for commit after release. portmgr welcomed two new members to its team: Erwin Lansing (who had previously served as secretary, a role in which he is continuing) and Clement Laforet. Clement is interested in speeding up the adoption of new changes into the infrastructure, an item I'm sure that that everyone can support. He promises to bring some fresh ideas to bear on this, including the revitalization of devel/portmk as a testing ground for new changes to bsd.port.mk in which the larger community can help test changes. The unfetchable distfile survey, which had been non-functional for quite some time, was revitalized by Bill Fenner, with many new pages of analysis added to it. Work is still ongoing. As a result of this analysis, Bill and Mark Linimon eliminated nearly 100 lines of bogus or outdated sites from bsd.sites.mk alone. They are continuing to work through many other sites and ports as successive iterations of the survey reveal more dimensions to the problem. We still need more help from the larger community (see below). Edwin Groothius has instituted a similar but slightly different survey. His program attempts to visit each listed mastersite for each distfile and determine whether or not a newer version might be available. The results are stored in a database. This is helping to automate a function that had been left up to individual maintainers to look through numerous websites to try to find these updates. The survey has been hugely (if not universally) popular. Already, dozens of port updates have been committed as a direct result of this service. In addition, portsmon, which had been down due to a machine change, was moved to portsmon.FreeBSD.org and updated during this time. Many thanks to Erwin Lansing for providing the loan of this machine, and Will Andrews for having provided the loan of the previous incarnation. Both of the above surveys are now generating periodic email to ports maintainers advising them of problems. This is in addition to recurring email from portsmon. The surveys allow individual maintainers to ask to receive no further email. portsmon does not currently have this but it needs to be added. Although we have no doubt the mail can in some cases be annoying (especially given the fact that there will inevitably be some false positives), the fact is that these emails have had a direct impact on the quality on the ports. We ask for patience from the community while each of us continues to fine-tune the algorithms controlling what email is generated. (Because of the number of emails these systems generate, it is impossible to go over every one individually for a sanity check). As a result of bounces from the above email, we have also been resetting maintainers who have become unreachable. Pav Lucistnik has done a great deal of work on the Porter's Handbook, including some much needed reshuffling and cleanup. Expanded sections include Apache and PHP; Configure Scripts; Dealing With Shared Libraries; Dealing With User Configuration Files; Handling Empty Directories; Python; and Ruby. In addition, Edwin Groothius has contributed a section on OPTIONS, and numerous other sections have been improved by good suggestions from various other contributors. A new article, "Maintaining and contributing to the FreeBSD Ports Collection", has been prepared by Sam Lawrance and has been reviewed and is ready for commit. This document attempts to codify the rights and responsibilities of ports maintainers, which until now had merely been "community lore" as discussed on various mailing lists. We continue to add new committers regularly, 8 since the last report. The ports collection now contains over 13,500 ports. This is an increase of over 750 since the last report in April. Open tasks: 1. portmgr would like to ask maintainers and committers alike to go through the status of their ports on the two distfile surveys, both the one that shows unfetchable current distfiles and the one that shows possibly updated distfiles. This is an effective way to quickly help improve our user's perception of the state of the ports. 2. A great deal of progress has been made in cracking down on ports that install files outside the approved directories and/or do not deinstall cleanly (see "Extra files not listed in PLIST" on pointyhat ). These ports are now a small minority thanks to the dedicated efforts of a large number of individuals. 3. We still have a large number of PRs that have been assigned to committers for some time (in fact, they constitute the majority). portmgr members are now going through this list and asking each committer to either commit them or release them to the general pool so that someone else may work on them. In addition, the existing policies for inactive maintainers (two weeks for maintainer- timeout on PRs; three months for maintainer reset if no activity) are going to be much more actively pursued than in the past, where the policies were more honored in the breach than in the observance. The goal is to try to bring the Ports Collection as up-to-date as possible. (While there has been progress on many fronts, there are still areas where ports are suffering from bit-rot.) __________________________________________________________________ Ports Tinderbox URL: http://tinderbox.marcuscom.com Contact: Joe Marcus Clarke Contact: Tinderbox List The Ports Tinderbox is a packaged system for building FreeBSD ports in a clean environment. It can be used to test new ports, updates to existing ports, or simply as a package building engine. Tinderbox uses the same underlying code that the official FreeBSD package build cluster, pointyhat, uses. So if a port builds under Tinderbox, it is guaranteed to build on pointyhat. More an more FreeBSD committers and ports maintainers are starting to use Tinderbox. We just released version 2.1.0 which added much-requested PostgreSQL support as well as fixed many bugs. We expect a 2.1.1 release soon with some additional bug fixes. With the 2.1.0 release of Tinderbox, we have branched the code base so that we can focus on larger features in our HEAD branch while still producing stable releases on a more frequent basis. The biggest new feature planned for Tinderbox 3.0 is clustering support which is being spearheaded by Ade Lovett (ade). Open tasks: 1. At this point, we really need help with documentation. Work has begun on creating man pages for the various Tinderbox commands, but we need help to churn them out at as faster rate. If you have strong mdoc fu, and interested in helping us out, please contact marcus@marcuscom.com . __________________________________________________________________ PowerPC Port URL: http://www.freebsd.org/platforms/ppc.html Contact: Peter Grehan The project has been following the 6.0 release schedule by producing BETA-* builds and is now up to the RC1 build. Dario Freni successfully built a FreeSBIE/ppc iso for his Summer-of-code project. __________________________________________________________________ Problem Report Database URL: http://www.freebsd.org/support.html#gnats Contact: Mark Linimon Due to some good recent commit and cleanup work by both Alexander Leidinger and Craig Rodrigues, the number of base-system PRs has stabilized somewhat. The number of incoming ports PRs continues to accelerate but except during freezes the ports committers have been battling to commit them as quickly as they come in. (The graphs very clearly show where the freezes are.) The net result is that we are holding our own but it takes a great deal of (mostly unheralded) effort to do so. Thanks are due to a large number of individuals who are doing this ongoing work. There is ongoing work to ask committers who have had PRs assigned to them for a significant period of time, whether they are still interested in pursuing them or whether they should instead be reassigned to the pool. This is being done to try to get as many PRs 'unstuck' as possible to try to help improve our users' perceptions of the project. As an experiment, Mark Linimon has been adding 'tags' to many of the kern and bin PRs, including such things as '[nfs]', '[if_em]', and so forth. The idea is to try allow searching and browsing based on these terms so that committers will find it easier to work with our current PR database. At the moment this is in the experimental stage, although it is possible for committers to work with them from the command line on systems with a database installed via query-pr(1). __________________________________________________________________ Realtime POSIX signal Contact: David Xu The FreeBSD kernel is powerful, but it still lacks some realtime POSIX facilities, for example, sigqueue, current I am working on it, most code is ready, and being tested. Open tasks: 1. POSIX timer, timer_xxx syscalls __________________________________________________________________ Removable interface improvements URL: http://people.freebsd.org/~brooks/pubs/eurobsdcon2004/ URL: http://www.freebsd.org/projects/dingo/ Contact: Brooks Davis This project is an attempt to clean up handling of network interfaces in order to allow interfaces to be removed reliably. Current problems include panics if Dummynet is delaying packets to an interface when it is removed. I have removed struct ifnet's and layer two common structures from device driver structures. This will eventually allow them to be managed properly upon device removal. This code has been committed and will appear in 6.0. Popular drivers have continued to be fixed. jhb's locking work has identified and corrected many issues. rwatson has also committed cleanups to the multicast code which fix some issues in this area. __________________________________________________________________ SNMP Monitoring URL: http://wikitest.freebsd.org/moin.cgi/VictorCruceru Contact: Harti Brandt Contact: Philip Paeps Contact: Victor Cruceru New MIBs are implmented for the BSNMP agent: 1. HOST-RESOURCES-MIB ( http://www.ietf.org/rfc/rfc2790.txt ). Philip is going to submit the code into the CVS repository. 2. TCP-MIB with combined IPv4 & IPv6 support ( http://www.ietf.org/rfc/rfc4022.txt ). This new TCP-MIB is 100% backward compatible with the old one (v4 only). It adds a clear distinction between active and passive tcp endpoints and for each endpoint info about the process it belongs to. 3. UDP-MIB with combined IPv4 & IPv6 support ( http://www.ietf.org/rfc/rfc4113.txt ). This new UDP-MIB is 100% backward compatible with the old one (v4 only) and it adds multiple instances support for the UDP endpoints and for each endpoint info about the processes using it. Open tasks: 1. For HOST-RESOURCES-MIB we are going to add support for more detailed memory stats based of libmemstat(3) 2. The rest of the IPv6 MIBs. 3. FreeBSD enterprise MIBs for supporting SNMP configuration (via SNMP SETs) for FreeBSD. __________________________________________________________________ Sound subsystem improvements Contact: Multimedia Mailinglist Contact: Ariff Abdullah Contact: Alexander Leidinger Recently a lot of fixes, specially in handling format / rate conversion and general stability got committed to -current. This include fixes for most LOR's and new features (software volume handling for soundcards without volume handling in hardware and the possibility to switch to spdif). A lot of effort was spend by Ariff (and other people) to come up with those improvements. For this reason Ariff is "punished" with a commit bit, so he is able to commit further improvements on his own. This work is not integrated into 6.0-RELEASE because of some lose ends (see 'sndctl' below). You can help by looking at sound related PR's in GNATS and making follow-up's which tell us if a problem still persists or if a PR can be closed because the bug is fixed. Also feel free to submit patches for anything on the TODO list below. Open tasks: 1. Update manpages to reflect current features. 2. Fix driver specific issue (via, t4dwave, maestro). 3. Make all drivers MPSAFE. 4. Rewrite some parts (e.g. a new mixer subsystem with OSS compatibility). 5. sndctl(1): tool to control non-mixer parts of the sound system (e.g. spdif switching, virtual-3D effects) by an user (instead of the sysctl approach in -current); pcmplay(1), pcmrec(1), pcmutil(1). 6. Plugable FEEDER infrastructure. For ease of debugging various feeder stuff and/or as userland library and test suite. 7. Support for new hardware (envy24, Intel HDA). 8. Performance enhancement (via 'slave'-channels, changes are under review)? 9. Closer compatibility with OSS, especially for the upcoming OSS v4. 10. Close a lot of PR's. 11. Document the sound system in the FreeBSD Architecture Handbook . __________________________________________________________________ TCP & IP Routing Optimization Fundraise URL: http://people.freebsd.org/~andre/tcpoptimization.html URL: http://www.freebsd.org/news/status/report-mar-2005-june-2005.html#Fund raising---TCP-&-IP-Routing-Optimization Contact: Andre Oppermann The fundraise has been very successful and I want to thank everyone who has pledged their support and tipped the jar. The full amount plus a little bit more has been raised in a very short timeframe. More information on the exact amounts and their sponsors can be found at the first link. Due to the extended (and unexpected long) code freeze for the release process of FreeBSD 6.0 (which is very high quality btw.) I've decided to push back on working full time until the freeze is lifted. So far I've done some work in the mbuf handling area and some other netinet cleanups in my local repository. Once FreeBSD 6.0 is released I resume my work on this project and many changes and optimizations, as described in the first and second link, will go into into FreeBSD-current. __________________________________________________________________ The Kernel Stress Test Suite URL: http://people.freebsd.org/~pho/stress/ Contact: Peter Holm The current version of the test suite took form in the beginning of this year after discussions with Jeff Roberson, during a long period of testing Jeff's VFS SMP work. At that time Daniel Seuffert donated a Tyan Thunder 7500 M/B with CPUs, RAM and coolers so I was able to do some serious SMP testing. Mid July Murray Stokely suggested adding a link from the 6.0 todo web page to the Stress Test Status Page. At that time there were a few reoccurring panics that made it hard to test the kernel for other problems. Numerous people put a lot of hard work in fixing the panics and livelocks found during the next months. At the same time others stepped in and ran the test suite on their own hardware, thus increasing the focus on kernel stability. The status for 6.0 is that I do not any longer get panics with the test suite. __________________________________________________________________ TODO list for volunteers Contact: Alexander Leidinger The TODO list for volunteers (see the last report for more) is now under review by some doc@ people. __________________________________________________________________ UFS Journaling Contact: Brian Wilson Contact: Scott Long Scott has been working on inserting journalling hooks into the ufs and ffs filesystem code. Brian has been balancing school and redesigning various things that were deemed necessary to update during the end of the actual SoC project. Open tasks: 1. Finish the redesign of the internal block management code. 2. Integration and test of the ffs/ufs hooks and the journaling code. 3. Updating userland tools to be aware of and use the journal. 4. Journal buffer management wiring to VM subsystem a la XFS. __________________________________________________________________ Legal Notices | =A9 1995-2005 The FreeBSD Project. All rights reserved. --Boundary-00=_rrcfDt62MW+sypK-- From owner-freebsd-hackers@FreeBSD.ORG Fri Nov 18 11:51:38 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 D81F916A41F for ; Fri, 18 Nov 2005 11:51:38 +0000 (GMT) (envelope-from dmitry@atlantis.dp.ua) Received: from postman.atlantis.dp.ua (postman.atlantis.dp.ua [193.108.47.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id E2BE943D46 for ; Fri, 18 Nov 2005 11:51:37 +0000 (GMT) (envelope-from dmitry@atlantis.dp.ua) Received: from smtp.atlantis.dp.ua (smtp.atlantis.dp.ua [193.108.46.231]) by postman.atlantis.dp.ua (8.13.1/8.13.1) with ESMTP id jAIBpPDP031903 for ; Fri, 18 Nov 2005 13:51:25 +0200 (EET) (envelope-from dmitry@atlantis.dp.ua) Date: Fri, 18 Nov 2005 13:51:25 +0200 (EET) From: Dmitry Pryanishnikov To: freebsd-hackers@freebsd.org Message-ID: <20051118124856.F199@atlantis.atlantis.dp.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Mailman-Approved-At: Fri, 18 Nov 2005 12:44:56 +0000 Subject: Physical memory access from kld X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2005 11:51:39 -0000 Hello! I'm trying to add Intel 875P chipset support for ecc.ko module. Basically this module outputs whether chipset supports and utilizes ECC, how much memory does it have, and whether there were memory errors. Well, this chipset has a very confusing architecture. Instead of having all relevant bits in PCI device configuration space, Intel has moved part of important DRAM controller registers into memory-mapped region, which is in turn controlled by the Overflow device 6, which isn't (in turn) even available by default. Many thanks to the author of http://www.x86-secret.com/articles/tweak/pat/patsecrets-2.htm for making it possible to access it at all - Intel's pdf doesn't even mention special register 0xF4 of Device 0! Very confusing desing, much worse than previous Intel chips ;( So, what tricks should I do in order to access memory-mapped registers of this "hidden" device 6? I wrote the code (currently under FreeBSD-4, but I want to port it then to RELENG_6) that enables device 6. Luckily BAR6 (starting address of memory-mapped registers) has been set up correctly by the mobo's (D875PBZ) BIOS. I can even "dd if=/dev/mem skip=xxx" and read those registers. But obviously I can't just dereference the pointer read from BAR6 since this physical address isn't mapped in kernel's virtual address space. What API should I use in order to map it in RELENG_4? In RELENG_6? And how to construct 'pcicfgregs' object for this "shadow" Overflow device under RELENG_6? During boot this device is invisible, so OS doesn't create 'pcicfgregs' for it. Under RELENG_4 all is simple: static pcicfgregs pci_cfg,pci_cfg2; ... bzero(cfgp, sizeof pci_cfg); pci_cfg.slot = 0; pci_cfg.func = 0; ... pci_cfg2 = pci_cfg; pci_cfg2.slot = 6 ; pci_cfg2.func = 0; and voila - pci_cfgread() / pci_cfgwrite() are happy. But under RELENG_6 there is no such API, and pci_read_config() / pci_write_config() do require valid (pcicfgregs *)->dev. So for Device 0 I'm just using OS-created objects: STAILQ_FOREACH(dinfo,&pci_devq,pci_links) { cfgp = &dinfo->cfg; if (cfgp->baseclass != PCIC_BRIDGE) continue; if (cfgp->subclass != PCIS_BRIDGE_HOST) continue; /* Here I have valid "pcicfgregs *cfgp" */ How to create valid *cfgp for Device 6? Sincerely, Dmitry -- Atlantis ISP, System Administrator e-mail: dmitry@atlantis.dp.ua nic-hdl: LYNX-RIPE From owner-freebsd-hackers@FreeBSD.ORG Fri Nov 18 14:55:42 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 11D9216A420 for ; Fri, 18 Nov 2005 14:55:42 +0000 (GMT) (envelope-from ellard@eecs.harvard.edu) Received: from mail.eecs.harvard.edu (bowser.eecs.harvard.edu [140.247.60.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0CC7943D5D for ; Fri, 18 Nov 2005 14:55:35 +0000 (GMT) (envelope-from ellard@eecs.harvard.edu) Received: from localhost (localhost.eecs.harvard.edu [127.0.0.1]) by mail.eecs.harvard.edu (Postfix) with ESMTP id CE58036EB0 for ; Fri, 18 Nov 2005 09:55:34 -0500 (EST) Received: from mail.eecs.harvard.edu ([127.0.0.1]) by localhost (bowser.eecs.harvard.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 75758-01 for ; Fri, 18 Nov 2005 09:55:34 -0500 (EST) Received: by mail.eecs.harvard.edu (Postfix, from userid 465) id 9E23A36EAA; Fri, 18 Nov 2005 09:55:34 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by mail.eecs.harvard.edu (Postfix) with ESMTP id 9AE9836EA6 for ; Fri, 18 Nov 2005 09:55:34 -0500 (EST) Date: Fri, 18 Nov 2005 09:55:34 -0500 (EST) From: Daniel Ellard To: freebsd-hackers@freebsd.org In-Reply-To: <20051118120039.BB3EE16A421@hub.freebsd.org> Message-ID: <20051118094225.E72964@bowser.eecs.harvard.edu> References: <20051118120039.BB3EE16A421@hub.freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by EECS Amavis at eecs.harvard.edu Subject: Re: Filesystem monitoring question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2005 14:55:42 -0000 There are many possible answers to this question. Can you explain more about exactly what you need? Depending on what you can and cannot access, one method is to sniff the network or the network interface. This will tell you when write requests come to the server, but can require a great deal of careful bookkeeping to know which write was to what file, etc. And it also doesn't tell you what the file system is doing, because these writes might be delayed/clustered/die in the cache. But it's a technique you can do on a machine for which you don't even have a login. If you were on Solaris, the answer is DTrace. But then you wouldn't be posting to this group... IIRC some of folks at SUNY Stony Brook (Erez Zadok's students, I think) have a VFS shim that traces calls through the VFS layer. If everything you're doing goes through VFS, that would work. But if it's a production server, you might not be able to get permission to fiddle with the kernel. ktrace might do everything you need, but I understand that it has an impact on system performance under load. I don't know if that matters to you at all. It also might be awkward if the SMB and NFS servers are kernel processes. (I just don't know; I've only used ktrace on ordinary user-land processes, and not even much of that.) -Dan From owner-freebsd-hackers@FreeBSD.ORG Fri Nov 18 15:29:43 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 602CA16A420 for ; Fri, 18 Nov 2005 15:29:43 +0000 (GMT) (envelope-from rools.ster@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5970943D62 for ; Fri, 18 Nov 2005 15:29:31 +0000 (GMT) (envelope-from rools.ster@gmail.com) Received: by zproxy.gmail.com with SMTP id r28so215972nza for ; Fri, 18 Nov 2005 07:29:31 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=b3Cd8PWSoHeU+np7FP22LNDEHNP8uESgaWRA/3Un1sE2EMovW63vPfj4SssKXXgsCC/90hUqNLY6BwVcjtBX2bUx/CKuA/xnV/zTtnZxWQ/W4M/Ue4o9p5ANhHlFm18cxR78UY1JHMZsUO7v/6BltAin2n3Dxva7NsDOPJbrZEo= Received: by 10.65.244.6 with SMTP id w6mr3817948qbr; Fri, 18 Nov 2005 07:29:30 -0800 (PST) Received: by 10.64.76.16 with HTTP; Fri, 18 Nov 2005 07:29:30 -0800 (PST) Message-ID: Date: Fri, 18 Nov 2005 15:29:30 +0000 From: Cornelis Swanepoel To: Daniel Ellard In-Reply-To: <20051118094225.E72964@bowser.eecs.harvard.edu> MIME-Version: 1.0 References: <20051118120039.BB3EE16A421@hub.freebsd.org> <20051118094225.E72964@bowser.eecs.harvard.edu> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers@freebsd.org Subject: Re: Filesystem monitoring question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2005 15:29:43 -0000 Before all else let me just say that my programming experience is confined to userland but I am very eager to learn about interaction with the FreeBSD kernel. There are many possible answers to this question. Can you explain > more about exactly what you need? This will be a server setup from scratch to accomodate the requirements. Currently the share is a full partition but it can be setup on the new server as a directory. A number of SMB and NFS clients, around 30, will need to write to this directory. Writing to the directory is 24/7 since some clients VPN into the network from different time zones. When they have completed a write operation I need to trigger some code that will act upon the file just written. This code generates a unique id for the file, stats the file, compresses th= e file(if over set limit), generates a preview of the file and stores some info about the file and its owner in a MySQL db and a log on a seperate machine. It then moves the file to a different location on the same machine (which i= s inaccesible to the NFS and SMB clients) and renames it as its unique identifier. At this point it is out of my hands. Depending on what you can and cannot access ... If everything .. goes > through VFS, that would work. But if > it's a production server, you might not be able to get permission to > fiddle with the kernel. This machine will be built from scratch and any kernel fiddling is possible= . ktrace might do everything you need, but I understand that it has an > impact on system performance under load. I don't know if that matters > to you at all. It also might be awkward if the SMB and NFS servers > are kernel processes. (I just don't know; I've only used ktrace on > ordinary user-land processes, and not even much of that.) >From the limited research I've done it seems that ktrace might not be the answer and I've been looking more into kqueue. I will definitely look into the VFS option. As I said at the start, this is all new to me and I greatly appreciate the feedback so far. If my explaination of the requirements is lacking please let me know specifically and I can elaborate. Thanks again and any further suggestions would be much appreciated. Cornelis From owner-freebsd-hackers@FreeBSD.ORG Fri Nov 18 15:48:51 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 5459016A41F for ; Fri, 18 Nov 2005 15:48:51 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C62D43D6E for ; Fri, 18 Nov 2005 15:48:46 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id jAIFmjsE042134; Fri, 18 Nov 2005 09:48:45 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <437DF7D3.9020902@centtech.com> Date: Fri, 18 Nov 2005 09:48:35 -0600 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051021 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Cornelis Swanepoel References: <20051118120039.BB3EE16A421@hub.freebsd.org> <20051118094225.E72964@bowser.eecs.harvard.edu> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.82/1178/Thu Nov 17 23:27:25 2005 on mh2.centtech.com X-Virus-Status: Clean Cc: freebsd-hackers@freebsd.org Subject: Re: Filesystem monitoring question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2005 15:48:51 -0000 Cornelis Swanepoel wrote: > Before all else let me just say that my programming experience is confined > to userland but I am very eager to learn about interaction with the FreeBSD > kernel. > > There are many possible answers to this question. Can you explain > >>more about exactly what you need? > > > > > This will be a server setup from scratch to accomodate the requirements. > Currently the share is a full partition but it can be setup on the new > server as a directory. > A number of SMB and NFS clients, around 30, will need to write to this > directory. > Writing to the directory is 24/7 since some clients VPN into the network > from different time zones. > > When they have completed a write operation I need to trigger some code that > will act upon the file just written. > This code generates a unique id for the file, stats the file, compresses the > file(if over set limit), generates a preview of the file and stores some > info about the file and its owner in a MySQL db and a log on a seperate > machine. > It then moves the file to a different location on the same machine (which is > inaccesible to the NFS and SMB clients) and renames it as its unique > identifier. > > At this point it is out of my hands. > > > Depending on what you can and cannot access ... If everything .. goes > >>through VFS, that would work. But if >> > > it's a production server, you might not be able to get permission to > >>fiddle with the kernel. > > > > > This machine will be built from scratch and any kernel fiddling is possible. > > ktrace might do everything you need, but I understand that it has an > >>impact on system performance under load. I don't know if that matters >>to you at all. It also might be awkward if the SMB and NFS servers >>are kernel processes. (I just don't know; I've only used ktrace on >>ordinary user-land processes, and not even much of that.) > > > > >>From the limited research I've done it seems that ktrace might not be the > answer and I've been looking more into kqueue. > I will definitely look into the VFS option. > > As I said at the start, this is all new to me and I greatly appreciate the > feedback so far. > > If my explaination of the requirements is lacking please let me know > specifically and I can elaborate. > > Thanks again and any further suggestions would be much appreciated. Here's a non-optimal way, but just tossing it in anyway: make a clone of nullfs (call it monitorfs say), modify it so that it outputs the write's using a printf (or any other more efficient method). Then you kldload your monitorfs module, and your tool watches the output. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-hackers@FreeBSD.ORG Fri Nov 18 15:56:38 2005 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.org 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 9A4E216A41F; Fri, 18 Nov 2005 15:56:38 +0000 (GMT) (envelope-from Jose-Marcio.Martins@ensmp.fr) Received: from mar92-6-82-226-38-60.fbx.proxad.net (mar92-6-82-226-38-60.fbx.proxad.net [82.226.38.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA61343D45; Fri, 18 Nov 2005 15:56:37 +0000 (GMT) (envelope-from Jose-Marcio.Martins@ensmp.fr) Received: from [127.0.0.1] (localhost. [127.0.0.1]) by joe.j-chkmail.org (sendmail X.0.0.0.0) with ESMTP id S00000000000014D701; Fri, 18 Nov 2005 16:56:39 +0100 Message-ID: <437DF9B7.8090206@ensmp.fr> Date: Fri, 18 Nov 2005 16:56:39 +0100 From: Jose Marcio Martins da Cruz User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050511 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Hajimu UMEMOTO References: <437C9102.7070909@ensmp.fr> In-Reply-To: X-Enigmail-Version: 0.92.0.0 Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms080300050707050503000702" Cc: freebsd-hackers@FreeBSD.org Subject: Re: res_nXXX function X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jose-Marcio.Martins@ensmp.fr List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2005 15:56:38 -0000 This is a cryptographically signed message in MIME format. --------------ms080300050707050503000702 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hello Hajimu, Hajimu UMEMOTO wrote: > Hi, > > Jose-Marcio> It seems that FreeBSD doesn't have reentrant versions of DNS query functions > Jose-Marcio> (res_nXXX, ...). > > Our recent resolver is thread-safe. So we don't need to use res_n*(), > basically. Nice. Since which version I can consider the resolver is thread-safe ? -- --------------------------------------------------------------- Jose Marcio MARTINS DA CRUZ Tel. :(33) 01.40.51.93.41 Ecole des Mines de Paris http://j-chkmail.ensmp.fr 60, bd Saint Michel http://www.ensmp.fr/~martins 75272 - PARIS CEDEX 06 mailto:Jose-Marcio.Martins@ensmp.fr --------------ms080300050707050503000702 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJwDCC BNwwggLEoAMCAQICAwD1ZzANBgkqhkiG9w0BAQQFADB5MRAwDgYDVQQKEwdSb290IENBMR4w HAYDVQQLExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNVBAMTGUNBIENlcnQgU2lnbmlu ZyBBdXRob3JpdHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2FjZXJ0Lm9yZzAeFw0wNTAz MDIyMTQ3MjlaFw0wNjAzMDIyMTQ3MjlaMFMxJDAiBgNVBAMTG0pvc2UtTWFyY2lvIE1hcnRp bnMgZGEgQ3J1ejErMCkGCSqGSIb3DQEJARYcSm9zZS1NYXJjaW8uTWFydGluc0BlbnNtcC5m cjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMyu8K6aUJMX2ZJP69UGRaB/gZ2W FzSXUpLmA+1lNGlc40X8D6N9mTwWX/IpI1Ppcxd9QYOBLm2M2Atc7IjV78MXj75dGYbOT0Dz YUovwoTGhKOYg18VIuxQ4rinGEI8eIqX6gMJ/Ftzox3H/og04AiIZxyMClAjuV5QFN7FRRtI uYGYgLaT+Hq5Q2LXizthF0ewXBfqH1GmJFyErhjkxWQTH4Dq8oFZuRnWA4V2Y30Ss6dn1mjx ySA3AsMaMNQTAZssa6R0BOqAFui3vm58zghLL23Mp5De2bpM83Y2mA8yqMEsF0DWr8Hi40a8 6xCYZHqKtTVxjeXqVRv5OxF8J/sCAwEAAaOBkjCBjzAMBgNVHRMBAf8EAjAAMFYGCWCGSAGG +EIBDQRJFkdUbyBnZXQgeW91ciBvd24gY2VydGlmaWNhdGUgZm9yIEZSRUUgaGVhZCBvdmVy IHRvIGh0dHA6Ly93d3cuQ0FjZXJ0Lm9yZzAnBgNVHREEIDAegRxKb3NlLU1hcmNpby5NYXJ0 aW5zQGVuc21wLmZyMA0GCSqGSIb3DQEBBAUAA4ICAQAicgOjgV0t6WLPCVJUgLGmcrUdtHPI Ee0zJ2DX/44WKngsaEXMrMMLvE93rFW77BgusUraW/uOF/phFoVBSgrTm/Iy10ixaSlWYad3 S+SqDjkDFOuK1LQwuQxQNj8Rjn+mTAi1EUTcM0xm0hBRQQueFjNOgu6wDoCKLSniHyjUtokY radIb4TGgoE0fmOQQz0n8ehysoerdIjaqmFK0pd8zEC914f7uhhdKCnzESuKg3Q9HxzjdcJD HCC+oNgWf504029HsnjnOkg7GS/jSqWxxWmHhAfJjKlLEM2BEPM7I7h/TEYqgbRGzFIba/RT 0HUYYKpVxTaUBp8XaupVBYzr3eHOxwKIsAtIW8N8qmbjAlRVSS+5wx5bjL04mVKUdq3kOVDx ESuTo086buVJ2+ntJ7sF6s1bynenOzDDOi5t4itkOKyZr7+MqSJQrqMX2J9TawP75KiN1uz7 llc8ShDm2kZijKmOAbUC8TeecoU9w+9H9aT1jbUYp2Q4hMmkVKZrbAlox67isPEZlgT4NCqY w2yJOz7tPXhNcIRFaQ50AZGaF0VJTKyDpyLiqAyOxJ1Smaa2ZhvI2w1b0JQcu7QCz4x/EI3r 4Uq8q+I8s5ghOq25NtdeJXQgS563S0eH1FHcgIC6B7l8QV5z9mWmWnUs9w7wxMiIMI6OQX7q gu3oKzCCBNwwggLEoAMCAQICAwD1ZzANBgkqhkiG9w0BAQQFADB5MRAwDgYDVQQKEwdSb290 IENBMR4wHAYDVQQLExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNVBAMTGUNBIENlcnQg U2lnbmluZyBBdXRob3JpdHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2FjZXJ0Lm9yZzAe Fw0wNTAzMDIyMTQ3MjlaFw0wNjAzMDIyMTQ3MjlaMFMxJDAiBgNVBAMTG0pvc2UtTWFyY2lv IE1hcnRpbnMgZGEgQ3J1ejErMCkGCSqGSIb3DQEJARYcSm9zZS1NYXJjaW8uTWFydGluc0Bl bnNtcC5mcjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMyu8K6aUJMX2ZJP69UG RaB/gZ2WFzSXUpLmA+1lNGlc40X8D6N9mTwWX/IpI1Ppcxd9QYOBLm2M2Atc7IjV78MXj75d GYbOT0DzYUovwoTGhKOYg18VIuxQ4rinGEI8eIqX6gMJ/Ftzox3H/og04AiIZxyMClAjuV5Q FN7FRRtIuYGYgLaT+Hq5Q2LXizthF0ewXBfqH1GmJFyErhjkxWQTH4Dq8oFZuRnWA4V2Y30S s6dn1mjxySA3AsMaMNQTAZssa6R0BOqAFui3vm58zghLL23Mp5De2bpM83Y2mA8yqMEsF0DW r8Hi40a86xCYZHqKtTVxjeXqVRv5OxF8J/sCAwEAAaOBkjCBjzAMBgNVHRMBAf8EAjAAMFYG CWCGSAGG+EIBDQRJFkdUbyBnZXQgeW91ciBvd24gY2VydGlmaWNhdGUgZm9yIEZSRUUgaGVh ZCBvdmVyIHRvIGh0dHA6Ly93d3cuQ0FjZXJ0Lm9yZzAnBgNVHREEIDAegRxKb3NlLU1hcmNp by5NYXJ0aW5zQGVuc21wLmZyMA0GCSqGSIb3DQEBBAUAA4ICAQAicgOjgV0t6WLPCVJUgLGm crUdtHPIEe0zJ2DX/44WKngsaEXMrMMLvE93rFW77BgusUraW/uOF/phFoVBSgrTm/Iy10ix aSlWYad3S+SqDjkDFOuK1LQwuQxQNj8Rjn+mTAi1EUTcM0xm0hBRQQueFjNOgu6wDoCKLSni HyjUtokYradIb4TGgoE0fmOQQz0n8ehysoerdIjaqmFK0pd8zEC914f7uhhdKCnzESuKg3Q9 HxzjdcJDHCC+oNgWf504029HsnjnOkg7GS/jSqWxxWmHhAfJjKlLEM2BEPM7I7h/TEYqgbRG zFIba/RT0HUYYKpVxTaUBp8XaupVBYzr3eHOxwKIsAtIW8N8qmbjAlRVSS+5wx5bjL04mVKU dq3kOVDxESuTo086buVJ2+ntJ7sF6s1bynenOzDDOi5t4itkOKyZr7+MqSJQrqMX2J9TawP7 5KiN1uz7llc8ShDm2kZijKmOAbUC8TeecoU9w+9H9aT1jbUYp2Q4hMmkVKZrbAlox67isPEZ lgT4NCqYw2yJOz7tPXhNcIRFaQ50AZGaF0VJTKyDpyLiqAyOxJ1Smaa2ZhvI2w1b0JQcu7QC z4x/EI3r4Uq8q+I8s5ghOq25NtdeJXQgS563S0eH1FHcgIC6B7l8QV5z9mWmWnUs9w7wxMiI MI6OQX7qgu3oKzGCA4cwggODAgEBMIGAMHkxEDAOBgNVBAoTB1Jvb3QgQ0ExHjAcBgNVBAsT FWh0dHA6Ly93d3cuY2FjZXJ0Lm9yZzEiMCAGA1UEAxMZQ0EgQ2VydCBTaWduaW5nIEF1dGhv cml0eTEhMB8GCSqGSIb3DQEJARYSc3VwcG9ydEBjYWNlcnQub3JnAgMA9WcwCQYFKw4DAhoF AKCCAdswGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMDUxMTE4 MTU1NjM5WjAjBgkqhkiG9w0BCQQxFgQU4i7RKwLeHf8BTtRLBQ35+ZDmGlEwUgYJKoZIhvcN AQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYF Kw4DAgcwDQYIKoZIhvcNAwICASgwgZEGCSsGAQQBgjcQBDGBgzCBgDB5MRAwDgYDVQQKEwdS b290IENBMR4wHAYDVQQLExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNVBAMTGUNBIENl cnQgU2lnbmluZyBBdXRob3JpdHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2FjZXJ0Lm9y ZwIDAPVnMIGTBgsqhkiG9w0BCRACCzGBg6CBgDB5MRAwDgYDVQQKEwdSb290IENBMR4wHAYD VQQLExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNVBAMTGUNBIENlcnQgU2lnbmluZyBB dXRob3JpdHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2FjZXJ0Lm9yZwIDAPVnMA0GCSqG SIb3DQEBAQUABIIBAE+0UGlj00QnxnrIFaJ2IcCtZacv0PjWR9qvGXlgtDlMVcpaINW9hLkb z1F1xAkSGDgHeSd47Jyhf++xnUvAUF3BW6oZV8LfHhubD4UJ3xB3MBP8L/9W1ehRU97pNH3M iaba15Sl43jppUmOwunjn0oHnZfygQyOedgiAHb9S8ectD/5AKcQhOX6/N3PkDAFq/pKRcsw goAn5K/4ZK8y/KoRqTowYeNUEQJSnpLTiZvXcjm7pkJlHjsjsuY+1rUXXRb96s2mMyt4wHxm aCiUV9Bq2X8qJmDXTADUT5yiboC/OST/T3MXTrL3ujc/S8lvaSZ9Q6nHTz4u8PJL0SGZB00A AAAAAAA= --------------ms080300050707050503000702-- From owner-freebsd-hackers@FreeBSD.ORG Fri Nov 18 16:55:54 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 072EF16A41F for ; Fri, 18 Nov 2005 16:55:54 +0000 (GMT) (envelope-from bv@bilver.wjv.com) Received: from wjv.com (fl-65-40-24-38.sta.sprint-hsd.net [65.40.24.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A23D43D46 for ; Fri, 18 Nov 2005 16:55:53 +0000 (GMT) (envelope-from bv@bilver.wjv.com) Received: from bilver.wjv.com (localhost.wjv.com [127.0.0.1]) by wjv.com (8.13.5/8.13.1) with ESMTP id jAIGtp8U054690 for ; Fri, 18 Nov 2005 11:55:51 -0500 (EST) (envelope-from bv@bilver.wjv.com) Received: (from bv@localhost) by bilver.wjv.com (8.13.5/8.13.1/Submit) id jAIGtkmB054689 for freebsd-hackers@freebsd.org; Fri, 18 Nov 2005 11:55:46 -0500 (EST) (envelope-from bv) Date: Fri, 18 Nov 2005 11:55:46 -0500 From: Bill Vermillion To: freebsd-hackers@freebsd.org Message-ID: <20051118165546.GM53311@wjv.com> References: <20051118120040.5B6B616A423@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051118120040.5B6B616A423@hub.freebsd.org> Organization: W.J.Vermillion / Orlando - Winter Park ReplyTo: bv@wjv.com User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on bilver.wjv.com Subject: Re: Filesystem monitoring question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bv@wjv.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2005 16:55:54 -0000 On Fri, Nov 18, 2005 at 12:00 , freebsd-hackers-request@freebsd.org showing utter disregard for spell-checkers gave us this: > Date: Thu, 17 Nov 2005 15:07:48 +0000 > From: Cornelis Swanepoel > Subject: Filesystem monitoring question > I have a FreeBSD 6.0 box with a partition that is accessible to > a number of clients via SMB and NFS. > I would like to monitor activity on this partition so that every > time a write to it is completed, my C program is run (which > stats the file and stores some info about it in a database > amongst other things) > My question is: What do I need to learn in order to construct a > trigger for my code? > If anyone can point me in the right direction I would greatly > appreciate it. What is that you need that fam won't do. See man 1m fam. Bill -- Bill Vermillion - bv @ wjv . com From owner-freebsd-hackers@FreeBSD.ORG Fri Nov 18 17:03:07 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 2157116A41F for ; Fri, 18 Nov 2005 17:03:07 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id B4BF043D76 for ; Fri, 18 Nov 2005 17:03:06 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.3) id jAIH35W4059783; Fri, 18 Nov 2005 11:03:05 -0600 (CST) (envelope-from dan) Date: Fri, 18 Nov 2005 11:03:05 -0600 From: Dan Nelson To: Cornelis Swanepoel Message-ID: <20051118170304.GI62141@dan.emsphone.com> References: <20051118120039.BB3EE16A421@hub.freebsd.org> <20051118094225.E72964@bowser.eecs.harvard.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-OS: FreeBSD 5.4-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.11 Cc: freebsd-hackers@freebsd.org, Daniel Ellard Subject: Re: Filesystem monitoring question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2005 17:03:07 -0000 In the last episode (Nov 18), Cornelis Swanepoel said: > When they have completed a write operation I need to trigger some > code that will act upon the file just written. This code generates a > unique id for the file, stats the file, compresses the file(if over > set limit), generates a preview of the file and stores some info > about the file and its owner in a MySQL db and a log on a seperate > machine. It then moves the file to a different location on the same > machine (which is inaccesible to the NFS and SMB clients) and renames > it as its unique identifier. Are you sure you need to hook into the kernel? Why not just have a userland process scan the directory every 10 seconds or so for new files? Note that NFS has no concept of "file close", just reads and writes, so you will need to be able to determine whether a file has completed. This could be either timestamp based (file not modified in 60 seconds == done), or if you know the file format, you may be able to validate the contents (check for zipfile end-of-file marker, etc). -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-hackers@FreeBSD.ORG Fri Nov 18 17:12:11 2005 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.org 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 129C016A41F; Fri, 18 Nov 2005 17:12:11 +0000 (GMT) (envelope-from ume@mahoroba.org) Received: from ameno.mahoroba.org (gw4.mahoroba.org [218.45.22.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id 83DB843D76; Fri, 18 Nov 2005 17:11:53 +0000 (GMT) (envelope-from ume@mahoroba.org) Received: from kasuga.mahoroba.org (IDENT:1qY+L5fQdbRgQIxa7DiDU/mwVNs2fN+hk2pVBSoGa1oKfpybossCKfSMwGnmXoGB@kasuga.mahoroba.org [IPv6:3ffe:501:185b:8010:20b:97ff:fe2e:b521]) (user=ume mech=CRAM-MD5 bits=0) by ameno.mahoroba.org (8.13.4/8.13.4) with ESMTP/inet6 id jAIHBX5W084433 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 19 Nov 2005 02:11:36 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Sat, 19 Nov 2005 02:11:32 +0900 Message-ID: From: Hajimu UMEMOTO To: Jose-Marcio.Martins@ensmp.fr In-Reply-To: <437DF9B7.8090206@ensmp.fr> References: <437C9102.7070909@ensmp.fr> <437DF9B7.8090206@ensmp.fr> User-Agent: xcite1.38> Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 Emacs/22.0.50 (i386-unknown-freebsd6.0) MULE/5.0 (SAKAKI) X-Operating-System: FreeBSD 6.0-STABLE X-PGP-Key: http://www.imasy.or.jp/~ume/publickey.asc X-PGP-Fingerprint: 1F00 0B9E 2164 70FC 6DC5 BF5F 04E9 F086 BF90 71FE Organization: Internet Mutual Aid Society, YOKOHAMA MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (ameno.mahoroba.org [IPv6:3ffe:501:185b:8010::1]); Sat, 19 Nov 2005 02:11:37 +0900 (JST) X-Virus-Scanned: by amavisd-new X-Virus-Status: Clean X-Spam-Status: No, score=-4.0 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on ameno.mahoroba.org Cc: freebsd-hackers@FreeBSD.org, Hajimu UMEMOTO Subject: Re: res_nXXX function X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2005 17:12:11 -0000 Hi, >>>>> On Fri, 18 Nov 2005 16:56:39 +0100 >>>>> Jose Marcio Martins da Cruz said: Jose-Marcio> Since which version I can consider the resolver is thread-safe ? The resolver itself (res_* functions) is thread-safe since 5.3-RELEASE. The netdb functions such as gethostbyname(3) and gethostbyaddr(3) are since 5.4-STABLE as of May 19 2005 and 6.0-RELEASE. Sincerely, -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ From owner-freebsd-hackers@FreeBSD.ORG Fri Nov 18 23:34:33 2005 Return-Path: X-Original-To: hackers@freebsd.org 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 E717116A420 for ; Fri, 18 Nov 2005 23:34:33 +0000 (GMT) (envelope-from saturnero@freesbie.org) Received: from jail1-fbsd4.consiagnet.it (jail1-fbsd4.consiagnet.it [83.149.128.151]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7651943D45 for ; Fri, 18 Nov 2005 23:34:28 +0000 (GMT) (envelope-from saturnero@freesbie.org) Received: from jail1-fbsd4.consiagnet.it (jail1-fbsd4.consiagnet.it [83.149.128.151]) by jail1-fbsd4.consiagnet.it (Postfix) with ESMTP id 0923D579A for ; Sat, 19 Nov 2005 00:39:22 +0100 (CET) X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on cvs.freesbie.org X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=ham version=3.1.0 Received: from [192.168.99.16] (host2-169.pool872.interbusiness.it [87.2.169.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by jail1-fbsd4.consiagnet.it (Postfix) with ESMTP for ; Sat, 19 Nov 2005 00:39:21 +0100 (CET) Message-ID: <437E64F8.6050402@freesbie.org> Date: Sat, 19 Nov 2005 00:34:16 +0100 From: Dario Freni User-Agent: Mozilla Thunderbird 1.0.7 (Macintosh/20050923) X-Accept-Language: it, it-it, en-us, en MIME-Version: 1.0 To: hackers@freebsd.org X-Enigmail-Version: 0.92.0.0 OpenPGP: url=http://www.saturnero.net/saturnero.asc Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig67FABC9A70153BACC20A20B6" X-Virus-Scanned: ClamAV using ClamSMTP Cc: Subject: Date set to epoch when root filesystem is cd9660 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2005 23:34:34 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig67FABC9A70153BACC20A20B6 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Hi guys, I encountered this problem during the summer, asked on current@ but didn't receive response. When root filesystem is cd9660, the date of the system is set to epoch. I made some empiric debugging, discovering that the problem strongly depends on the mountroot setting and not on the different loader used for cd-boot. Have taken a look at the code and discovered what it seems to me the responsible of the bug. kern/vfs_mount.c:1313: /* * We mount devfs prior to mounting the / FS, so the first * entry will typically be devfs. */ mp = TAILQ_FIRST(&mountlist); KASSERT(mp != NULL, ("%s: mountlist is empty", __func__)); /* * Iterate over all currently mounted file systems and * the time stamp found to check and/or initialize the RTC. * Typically devfs has no time stamp and the only other FS * is the actual / FS. */ do { if (mp->mnt_time != 0) inittodr(mp->mnt_time); mp = TAILQ_NEXT(mp, mnt_list); } while (mp != NULL); Haven't investigate further, but I think that when the root is cd9660, mp->mnt_time is 0 and inittodr isn't initialised. Any idea on how to resolve this? Bye and thanks in advance, Dario -- Dario Freni (saturnero@freesbie.org) FreeSBIE developer (http://www.freesbie.org) GPG Public key at http://www.saturnero.net/saturnero.asc --------------enig67FABC9A70153BACC20A20B6 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDfmT+ymi72IiShysRAr/7AKC3xhyf0KoOSYG7SApPaUqLtHXwGQCgwcqD NifsrWsFjjmEfOOpEEzOHFs= =5hlu -----END PGP SIGNATURE----- --------------enig67FABC9A70153BACC20A20B6-- From owner-freebsd-hackers@FreeBSD.ORG Fri Nov 18 23:58:31 2005 Return-Path: X-Original-To: hackers@freebsd.org 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 188AA16A41F for ; Fri, 18 Nov 2005 23:58:31 +0000 (GMT) (envelope-from vkushnir@i.kiev.ua) Received: from horse.iptelecom.net.ua (horse.iptelecom.net.ua [212.9.224.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F2C143D45 for ; Fri, 18 Nov 2005 23:58:29 +0000 (GMT) (envelope-from vkushnir@i.kiev.ua) Received: from h191.242.159.dialup.iptcom.net ([213.159.242.191]:10961 "EHLO kushnir1.kiev.ua" ident: "SOCKFAULT1" whoson: "vkushnir") by horse.iptelecom.net.ua with ESMTP id S1219527AbVKRX61 (INRCPT ); Sat, 19 Nov 2005 01:58:27 +0200 Received: from kushnir1.kiev.ua (kushnir1.kiev.ua [10.0.0.1]) by kushnir1.kiev.ua (8.13.4/8.13.3) with ESMTP id jAINwPRm033360 for ; Sat, 19 Nov 2005 01:58:25 +0200 (EET) (envelope-from vkushnir@i.kiev.ua) Date: Sat, 19 Nov 2005 01:58:25 +0200 (EET) From: Vladimir Kushnir X-X-Sender: vkushnir@kushnir1.kiev.ua To: hackers@freebsd.org Message-ID: <20051119015322.S27789@kushnir1.kiev.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Subject: ATI drivers for FreeBSD - anything? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2005 23:58:31 -0000 Hi all, Is there any project on FreeBSD wrapper for ATI Linux drivers (like nVidia's used to be)? If so - I'd be more than happy to test (sorry I can hardly write it myself). Regards, Vladimir From owner-freebsd-hackers@FreeBSD.ORG Sat Nov 19 00:02:47 2005 Return-Path: X-Original-To: hackers@freebsd.org 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 82AF416A41F for ; Sat, 19 Nov 2005 00:02:47 +0000 (GMT) (envelope-from saturnero@freesbie.org) Received: from jail1-fbsd4.consiagnet.it (jail1-fbsd4.consiagnet.it [83.149.128.151]) by mx1.FreeBSD.org (Postfix) with ESMTP id 05A3643D45 for ; Sat, 19 Nov 2005 00:02:46 +0000 (GMT) (envelope-from saturnero@freesbie.org) Received: from jail1-fbsd4.consiagnet.it (jail1-fbsd4.consiagnet.it [83.149.128.151]) by jail1-fbsd4.consiagnet.it (Postfix) with ESMTP id 12F6657FD for ; Sat, 19 Nov 2005 01:07:39 +0100 (CET) X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on cvs.freesbie.org X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=ham version=3.1.0 Received: from [192.168.99.16] (host2-169.pool872.interbusiness.it [87.2.169.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by jail1-fbsd4.consiagnet.it (Postfix) with ESMTP for ; Sat, 19 Nov 2005 01:07:38 +0100 (CET) Message-ID: <437E6B9F.6030006@freesbie.org> Date: Sat, 19 Nov 2005 01:02:39 +0100 From: Dario Freni User-Agent: Mozilla Thunderbird 1.0.7 (Macintosh/20050923) X-Accept-Language: it, it-it, en-us, en MIME-Version: 1.0 To: hackers@freebsd.org References: <437E64F8.6050402@freesbie.org> In-Reply-To: <437E64F8.6050402@freesbie.org> X-Enigmail-Version: 0.92.0.0 OpenPGP: url=http://www.saturnero.net/saturnero.asc Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig5CB09D2E9E5AADB7E593E035" X-Virus-Scanned: ClamAV using ClamSMTP Cc: Subject: Re: Date set to epoch when root filesystem is cd9660 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Nov 2005 00:02:47 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig5CB09D2E9E5AADB7E593E035 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Dario Freni wrote: > kern/vfs_mount.c:1313: > > /* > * We mount devfs prior to mounting the / FS, so the first > * entry will typically be devfs. > */ > mp = TAILQ_FIRST(&mountlist); > KASSERT(mp != NULL, ("%s: mountlist is empty", __func__)); > /* > * Iterate over all currently mounted file systems and > * the time stamp found to check and/or initialize the RTC. > * Typically devfs has no time stamp and the only other FS > * is the actual / FS. > */ > do { > if (mp->mnt_time != 0) > inittodr(mp->mnt_time); > mp = TAILQ_NEXT(mp, mnt_list); > } while (mp != NULL); Found when this code was introduced: ======= Revision 1.186 / (download) - annotate - [select for diffs], Fri Mar 25 01:56:12 2005 UTC (7 months, 3 weeks ago) by marcel Branch: MAIN Fix inittodr() invocation. Now that devfs is mounted before the actual root file system is mounted, the first entry on the mountlist is not the root file system and the timestamp for that entry is typically 0. Passing that to inittodr() caused annoying errors on alpha and ia64. So, call inittodr() for all file systems on mountlist, but only when the timestamp (mnt_time) is non-zero. ======= -- Dario Freni (saturnero@freesbie.org) FreeSBIE developer (http://www.freesbie.org) GPG Public key at http://www.saturnero.net/saturnero.asc --------------enig5CB09D2E9E5AADB7E593E035 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDfmufymi72IiShysRAqjqAKCDX0wlaPnYuoNxku8tUkUaM7yvLACgsgNq 3eZxSiN0gMN7ZRz4qCurXdk= =tLZ9 -----END PGP SIGNATURE----- --------------enig5CB09D2E9E5AADB7E593E035-- From owner-freebsd-hackers@FreeBSD.ORG Sat Nov 19 03:05:47 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 B761016A420 for ; Sat, 19 Nov 2005 03:05:47 +0000 (GMT) (envelope-from spork@fasttrackmonkey.com) Received: from angryfist.fasttrackmonkey.com (angryfist.fasttrackmonkey.com [216.220.107.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3DE9143D46 for ; Sat, 19 Nov 2005 03:05:44 +0000 (GMT) (envelope-from spork@fasttrackmonkey.com) Received: (qmail 14648 invoked by uid 2003); 19 Nov 2005 02:59:10 -0000 Received: from spork@fasttrackmonkey.com by angryfist.fasttrackmonkey.com by uid 1001 with qmail-scanner-1.20 (clamscan: 0.65. Clear:RC:1(216.220.116.154):. Processed in 0.048972 secs); 19 Nov 2005 02:59:10 -0000 Received: from unknown (HELO gee5.nat.fasttrackmonkey.com) (216.220.116.154) by 0 with (DHE-RSA-AES256-SHA encrypted) SMTP; 19 Nov 2005 02:59:10 -0000 Date: Fri, 18 Nov 2005 22:05:42 -0500 (EST) From: Charles Sprickman X-X-Sender: spork@gee5.nat.fasttrackmonkey.com To: freebsd-hackers@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: 4.8 "Alternate system clock has died" error X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Nov 2005 03:05:47 -0000 Hello, I tried this query on -stable, hoping someone here can help me further understand and troubleshoot this. Reference: http://thread.gmane.org/gmane.os.freebsd.stable/32837 In short, top, ps report 0% CPU on all processes as of a few weeks ago. "systat -vmstat" hands out the "Alternate system clock has died" error. Box is running 4.8-p24 and has been up 425 days. Nothing out of the ordinary except for the above symptoms. In searching the various lists/newsgroups, it seems that the other folks with this problem have fixed it in various ways: -early 4.x users referenced a PR that was committed before 4.8 -some 5.3 users reported this with unknown resolution/cause -sending init a HUP was suggested (tried it, no luck) -setting kern.timecounter.method: 1 (tried it, no luck) -one user seemed to actually have a dead timer In the stable thread one person answered, and they were the sole example I could find of a true hardware failure. The odds are in my favor that it's a software issue I think... My hardware that I was given is probably a bit uncommon; it's an SMP Athlon box (Tyan S2462 THUNDER K7), probably not the most widely-tested platform. The -stable poster had a warning that if the RTC is bad, the machine likely won't come back up if I boot it. That has me very worried as this box is very important (mail server). Can anyone help me determine if this is a hardware problem? If it is, I really need to stretch the budget and dig up some new hardware to transplant everything into. Dmesg is in the linked thread. If there's any other info I can provide, let me know. Thanks, Charles From owner-freebsd-hackers@FreeBSD.ORG Sat Nov 19 03:16:04 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 0D3EC16A41F for ; Sat, 19 Nov 2005 03:16:04 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6DDD243D49 for ; Sat, 19 Nov 2005 03:16:03 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 2259185 for multiple; Fri, 18 Nov 2005 22:16:07 -0500 Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jAJ3FwEp042539; Fri, 18 Nov 2005 22:15:58 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Fri, 18 Nov 2005 22:15:03 -0500 User-Agent: KMail/1.8.3 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200511182215.04399.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: Charles Sprickman Subject: Re: 4.8 "Alternate system clock has died" error X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Nov 2005 03:16:04 -0000 On Friday 18 November 2005 10:05 pm, Charles Sprickman wrote: > Hello, > > I tried this query on -stable, hoping someone here can help me further > understand and troubleshoot this. > > Reference: > http://thread.gmane.org/gmane.os.freebsd.stable/32837 > > In short, top, ps report 0% CPU on all processes as of a few weeks ago. > "systat -vmstat" hands out the "Alternate system clock has died" error. > > Box is running 4.8-p24 and has been up 425 days. Nothing out of the > ordinary except for the above symptoms. In searching the various > lists/newsgroups, it seems that the other folks with this problem have > fixed it in various ways: > > -early 4.x users referenced a PR that was committed before 4.8 > -some 5.3 users reported this with unknown resolution/cause > -sending init a HUP was suggested (tried it, no luck) > -setting kern.timecounter.method: 1 (tried it, no luck) > -one user seemed to actually have a dead timer Actually, there was a patch that was committed in 5.4 and 6.0 for this issu= e. =20 You can see the diff here: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/i386/isa/clock.c.diff?r1=3D1.= 213&r2=3D1.214&f=3Dh That patch would probably backport to 4.x fairly easily. > The -stable poster had a warning that if the RTC is bad, the machine > likely won't come back up if I boot it. That has me very worried as this > box is very important (mail server). If it's a software glitch such as the ones fixed in the patch above, your b= ox=20 will come up after a reboot without a problem. > Can anyone help me determine if this is a hardware problem? If it is, I > really need to stretch the budget and dig up some new hardware to > transplant everything into. That is not very easy to tell. It's doubtful that it is a hardware problem= ,=20 but if it is, it would require a new motherboard to fix as the RTC is part = of=20 the southbridge which is rather firmly attached to your motherboard. :) =2D-=20 John Baldwin =A0<>< =A0http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =A0=3D =A0http://www.FreeBSD.org From owner-freebsd-hackers@FreeBSD.ORG Sat Nov 19 13:52:08 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 389E716A41F for ; Sat, 19 Nov 2005 13:52:08 +0000 (GMT) (envelope-from gzh@net.pku.edu.cn) Received: from net.pku.edu.cn (net.pku.edu.cn [162.105.203.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 52BCB43D46 for ; Sat, 19 Nov 2005 13:52:05 +0000 (GMT) (envelope-from gzh@net.pku.edu.cn) Received: from pku10ecd4f5e75 ([162.105.146.218]) (authenticated bits=0) by net.pku.edu.cn (8.12.11/8.12.8) with ESMTP id jAJE8KGl024009 for ; Sat, 19 Nov 2005 22:08:21 +0800 Message-Id: <200511191408.jAJE8KGl024009@net.pku.edu.cn> From: =?gb2312?B?ufnV8buq?= To: Date: Sat, 19 Nov 2005 21:51:58 +0800 MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcXtEGi77WF93nUyR1uoxe+nCkM6FQ== X-Mailman-Approved-At: Sat, 19 Nov 2005 15:13:54 +0000 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: a puzzle about FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Nov 2005 13:52:08 -0000 I am very interested in FreeBSD but it is difficult to master it. There = is little resource related to the most basic and fundamental problems. I read the source code of a project. I don=A1=AFt understand SYSCTL_IN = macro and SYSCTL_PROC macro. I want to know when my function registered in = SYSCTL_PROC is called. In addition, can you give me some advanced reference books or websites = which are useful? =20 Best wishes Jenvor From owner-freebsd-hackers@FreeBSD.ORG Sat Nov 19 15:18:57 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 1414D16A41F for ; Sat, 19 Nov 2005 15:18:57 +0000 (GMT) (envelope-from delphij@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F14C43D45 for ; Sat, 19 Nov 2005 15:18:56 +0000 (GMT) (envelope-from delphij@gmail.com) Received: by xproxy.gmail.com with SMTP id t14so416355wxc for ; Sat, 19 Nov 2005 07:18:55 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Qd3FeVavH18X2UWIwGcQjIrwPAARgmjVcwPutQsKaFKBn6xU2U2ST3/2+viMCR6O/AXOTxRdB4ZTf64s+E3kVxnQOk4LQu/pihXuruMLo2o2UsOY3Jwrw1GriokXGRftHIYn5lSXTL3IkeYO6Vy6+j+/lSBvHQ5owAOr96sffFw= Received: by 10.64.251.9 with SMTP id y9mr992712qbh; Sat, 19 Nov 2005 07:18:55 -0800 (PST) Received: by 10.64.21.5 with HTTP; Sat, 19 Nov 2005 07:18:55 -0800 (PST) Message-ID: Date: Sat, 19 Nov 2005 23:18:55 +0800 From: Xin LI To: =?UTF-8?B?6YOt5oyv5Y2O?= In-Reply-To: <200511191408.jAJE8KGl024009@net.pku.edu.cn> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 Content-Disposition: inline References: <200511191408.jAJE8KGl024009@net.pku.edu.cn> Cc: freebsd-hackers@freebsd.org Subject: Re: a puzzle about FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: delphij@delphij.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Nov 2005 15:18:57 -0000 SGksCgpPbiAxMS8xOS8wNSwg6YOt5oyv5Y2OIDxnemhAbmV0LnBrdS5lZHUuY24+IHdyb3RlOgo+ IEkgYW0gdmVyeSBpbnRlcmVzdGVkIGluIEZyZWVCU0QgYnV0IGl0IGlzIGRpZmZpY3VsdCB0byBt YXN0ZXIgaXQuIFRoZXJlIGlzCj4gbGl0dGxlIHJlc291cmNlIHJlbGF0ZWQgdG8gdGhlIG1vc3Qg YmFzaWMgYW5kIGZ1bmRhbWVudGFsIHByb2JsZW1zLgo+Cj4gSSByZWFkIHRoZSBzb3VyY2UgY29k ZSBvZiBhIHByb2plY3QuIEkgZG9uJ3QgdW5kZXJzdGFuZCBTWVNDVExfSU4gbWFjcm8gYW5kCj4g U1lTQ1RMX1BST0MgbWFjcm8uIEkgd2FudCB0byBrbm93IHdoZW4gbXkgZnVuY3Rpb24gcmVnaXN0 ZXJlZCBpbiBTWVNDVExfUFJPQwo+IGlzIGNhbGxlZC4KPgo+IEluIGFkZGl0aW9uLCBjYW4geW91 IGdpdmUgbWUgc29tZSBhZHZhbmNlZCByZWZlcmVuY2UgYm9va3Mgb3Igd2Vic2l0ZXMgd2hpY2gK PiBhcmUgdXNlZnVsPwoKSWYgeW91IGFyZSByZWFkaW5nIHRoZSBrZXJuZWwgdGhlbiB5b3Ugd291 bGQgZmluZCB0aGUgIkFyY2hpdGVjdHVyZQpIYW5kYm9vayIgdXNlZnVsLiAgVGhlIEZyZWVCU0Qg U2ltcGxpZmllZCBDaGluZXNlIFByb2plY3QgaXMKdHJhbnNsYXRpbmcgdGhlIGJvb2sgaW50byBD aGluZXNlLCBhbmQgeW91IGNhbiBsb29rIGF0IHRoZSBXSVAKc25hcHNob3QgaGVyZToKCmh0dHA6 Ly93d3cuZnJlZWJzZC5vcmcuY24vc25hcC9kb2MvemhfQ04uR0IyMzEyL2Jvb2tzL2FyY2gtaGFu ZGJvb2sKClRoZSBFbmdsaXNoIHZlcnNpb24gaXMgYXQ6CgpodHRwOi8vd3d3LmZyZWVic2Qub3Jn L2RvYy9lbl9VUy5JU084ODU5LTEvYm9va3MvYXJjaC1oYW5kYm9vawoKV2Ugd291bGQgYXBwcmVj aWF0ZSBpZiB5b3Ugd291bGQgcHJvdmlkZSBzb21lIGZlZWRiYWNrIGFib3V0IG91ciB0cmFuc2xh dGlvbiA6LSkKCkNoZWVycywKLS0KWGluIExJIDxkZWxwaGlqQGRlbHBoaWoubmV0PiBodHRwOi8v d3d3LmRlbHBoaWoubmV0Cg== From owner-freebsd-hackers@FreeBSD.ORG Sat Nov 19 15:18:32 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 E4D8116A41F for ; Sat, 19 Nov 2005 15:18:32 +0000 (GMT) (envelope-from bwzhou@hotmail.com) Received: from hotmail.com (bay111-f10.bay111.hotmail.com [64.4.17.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id A905E43D45 for ; Sat, 19 Nov 2005 15:18:32 +0000 (GMT) (envelope-from bwzhou@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sat, 19 Nov 2005 07:18:32 -0800 Message-ID: Received: from 64.4.17.200 by by111fd.bay111.hotmail.msn.com with HTTP; Sat, 19 Nov 2005 15:18:32 GMT X-Originating-IP: [210.77.2.92] X-Originating-Email: [bwzhou@hotmail.com] X-Sender: bwzhou@hotmail.com In-Reply-To: <200511191408.jAJE8KGl024009@net.pku.edu.cn> From: =?gb2312?B?1twg1tw=?= To: gzh@net.pku.edu.cn, freebsd-hackers@freebsd.org Date: Sat, 19 Nov 2005 15:18:32 +0000 Mime-Version: 1.0 Content-Type: text/plain; charset=gb2312; format=flowed X-OriginalArrivalTime: 19 Nov 2005 15:18:32.0475 (UTC) FILETIME=[80BE4EB0:01C5ED1C] X-Mailman-Approved-At: Sat, 19 Nov 2005 15:38:33 +0000 Cc: Subject: RE: a puzzle about FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Nov 2005 15:18:33 -0000 You'd better read "the design and implementation of the freebsd operating system" written by McKusick himself. >From: 郭振华 >To: >Subject: a puzzle about FreeBSD >Date: Sat, 19 Nov 2005 21:51:58 +0800 > >I am very interested in FreeBSD but it is difficult to master it. There is >little resource related to the most basic and fundamental problems. > >I read the source code of a project. I don’t understand SYSCTL_IN macro and >SYSCTL_PROC macro. I want to know when my function registered in SYSCTL_PROC >is called. > >In addition, can you give me some advanced reference books or websites which >are useful? > > > >Best wishes > >Jenvor > >_______________________________________________ >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" _________________________________________________________________ 与联机的朋友进行交流，请使用 MSN Messenger: http://messenger.msn.com/cn From owner-freebsd-hackers@FreeBSD.ORG Sat Nov 19 19:16:05 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 6059016A41F; Sat, 19 Nov 2005 19:16:05 +0000 (GMT) (envelope-from gemini@geminix.org) Received: from gen129.n001.c02.escapebox.net (gen129.n001.c02.escapebox.net [213.73.91.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id E587643D45; Sat, 19 Nov 2005 19:16:04 +0000 (GMT) (envelope-from gemini@geminix.org) Message-ID: <437F79F1.5040706@geminix.org> Date: Sat, 19 Nov 2005 20:16:01 +0100 From: Uwe Doering Organization: Private UNIX Site User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051117 X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <200511182215.04399.jhb@freebsd.org> In-Reply-To: <200511182215.04399.jhb@freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Received: from gemini by geminix.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.54 (FreeBSD)) id 1EdYBu-0008EP-IS; Sat, 19 Nov 2005 20:16:02 +0100 Cc: freebsd-hackers@freebsd.org, Charles Sprickman Subject: Re: 4.8 "Alternate system clock has died" error X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Nov 2005 19:16:05 -0000 John Baldwin wrote: > On Friday 18 November 2005 10:05 pm, Charles Sprickman wrote: > >>I tried this query on -stable, hoping someone here can help me further >>understand and troubleshoot this. >> >>Reference: >>http://thread.gmane.org/gmane.os.freebsd.stable/32837 >> >>In short, top, ps report 0% CPU on all processes as of a few weeks ago. >>"systat -vmstat" hands out the "Alternate system clock has died" error. >> >>Box is running 4.8-p24 and has been up 425 days. Nothing out of the >>ordinary except for the above symptoms. In searching the various >>lists/newsgroups, it seems that the other folks with this problem have >>fixed it in various ways: >> >>-early 4.x users referenced a PR that was committed before 4.8 >>-some 5.3 users reported this with unknown resolution/cause >>-sending init a HUP was suggested (tried it, no luck) >>-setting kern.timecounter.method: 1 (tried it, no luck) >>-one user seemed to actually have a dead timer > > Actually, there was a patch that was committed in 5.4 and 6.0 for this issue. > You can see the diff here: > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/i386/isa/clock.c.diff?r1=1.213&r2=1.214&f=h > > That patch would probably backport to 4.x fairly easily. I just looked at RELENG_4, and yes, backporting should be easy. Though I haven't tried it yet on our machines. I wonder, however, what's writing to the RTC on a running server. Could this event perhaps have been triggered by the recent Daylight Saving Time switch? Uwe -- Uwe Doering | EscapeBox - Managed On-Demand UNIX Servers gemini@geminix.org | http://www.escapebox.net