From owner-freebsd-hackers@FreeBSD.ORG Sun Jun 4 04:38:32 2006 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 3E4A216A475; Sun, 4 Jun 2006 04:38:32 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 52C7143D46; Sun, 4 Jun 2006 04:38:27 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from gothmog.pc (host5.bedc.ondsl.gr [62.103.39.229]) (authenticated bits=128) by igloo.linux.gr (8.13.6/8.13.6/Debian-1) with ESMTP id k544b5ac002104 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 4 Jun 2006 07:37:13 +0300 Received: from gothmog.pc (gothmog [127.0.0.1]) by gothmog.pc (8.13.6/8.13.6) with ESMTP id k52NouD3048467; Sat, 3 Jun 2006 02:50:56 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from giorgos@localhost) by gothmog.pc (8.13.6/8.13.6/Submit) id k52NouSV048466; Sat, 3 Jun 2006 02:50:56 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Sat, 3 Jun 2006 02:50:56 +0300 From: Giorgos Keramidas To: Jason Evans Message-ID: <20060602235056.GA48432@gothmog.pc> References: <20060601150924.98192.qmail@web32701.mail.mud.yahoo.com> <4480CD78.4070602@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4480CD78.4070602@FreeBSD.org> X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (score=-3.408, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.79, BAYES_00 -2.60, DNS_FROM_RFC_ABUSE 0.20) X-Hellug-MailScanner-From: keramida@ceid.upatras.gr X-Spam-Status: No Cc: freebsd-hackers@FreeBSD.org, pfgshield-freebsd@yahoo.com Subject: Re: Porting libumem (was Re: Is anyone working on a port of ZFS to 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: Sun, 04 Jun 2006 04:38:32 -0000 On 2006-06-02 16:44, Jason Evans wrote: >pfgshield-freebsd@yahoo.com wrote: >> IMHO, and purely as constructive criticism, Jason's article >> would've been much more interesting if he had tested ptmalloc (in >> the ports tree) and we had had libumem. > > Yes, that would have been nice, but when I tried to use ptmalloc, it > failed to work correctly. I don't remember the details anymore, but > ISTR there was something wrong with the ptmalloc port that I didn't > have the time to fix. It may still be worth trying. I only started looking at `umem' from sourceforge this week, but if there is more interest in ptmalloc, maybe it is better if I focused on why ptmalloc fails to work on FreeBSD. - Giorgos From owner-freebsd-hackers@FreeBSD.ORG Sun Jun 4 06:47:01 2006 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 ADFDF16A473 for ; Sun, 4 Jun 2006 06:47:01 +0000 (UTC) (envelope-from pfgshield-freebsd@yahoo.com) Received: from web32713.mail.mud.yahoo.com (web32713.mail.mud.yahoo.com [68.142.206.26]) by mx1.FreeBSD.org (Postfix) with SMTP id 34BF243D49 for ; Sun, 4 Jun 2006 06:47:00 +0000 (GMT) (envelope-from pfgshield-freebsd@yahoo.com) Received: (qmail 6596 invoked by uid 60001); 4 Jun 2006 06:47:00 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=491Cr7YuCH7Rt4UV7GgC5lmY5bOw5Sxwha6AIqn1jUEJkqfBruDIUx1uOtYN9WLcMl9a9/mmMV0T4OIsfmVArJ33TJAJGEK9N4vJWaewxm5iDhx3jaKu0xtX3zxfxMgVicaEWZb0CV6zxBZSPS0BWftTRwAErsdbpzafFd5LVxo= ; Message-ID: <20060604064700.6590.qmail@web32713.mail.mud.yahoo.com> Received: from [200.118.56.50] by web32713.mail.mud.yahoo.com via HTTP; Sun, 04 Jun 2006 08:47:00 CEST Date: Sun, 4 Jun 2006 08:47:00 +0200 (CEST) From: To: Giorgos Keramidas In-Reply-To: <20060602235056.GA48432@gothmog.pc> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Mailman-Approved-At: Sun, 04 Jun 2006 06:51:52 +0000 Cc: freebsd-hackers@FreeBSD.org Subject: Re: Porting libumem (was Re: Is anyone working on a port of ZFS to FreeBSD) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pfgshield-freebsd@yahoo.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Jun 2006 06:47:01 -0000 --- Giorgos Keramidas ha scritto: ... > > It may still be worth trying. I only started looking at `umem' from > sourceforge this week, but if there is more interest in ptmalloc, > maybe it is better if I focused on why ptmalloc fails to work on > FreeBSD. > FWIW, I just submitted an update to ptmalloc as a followup to ports/95179. I'm still more interested in libumem though :). Pedro. Chiacchiera con i tuoi amici in tempo reale! http://it.yahoo.com/mail_it/foot/*http://it.messenger.yahoo.com From owner-freebsd-hackers@FreeBSD.ORG Sun Jun 4 07:29:34 2006 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 8C7BF16A473 for ; Sun, 4 Jun 2006 07:29:34 +0000 (UTC) (envelope-from fierykylin@gmail.com) Received: from wx-out-0102.google.com (wx-out-0102.google.com [66.249.82.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA1C543D4C for ; Sun, 4 Jun 2006 07:29:33 +0000 (GMT) (envelope-from fierykylin@gmail.com) Received: by wx-out-0102.google.com with SMTP id i31so568897wxd for ; Sun, 04 Jun 2006 00:29:31 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=QqrsppV4zjHwPOzL0h2Nsb5Gi1Y7jmoBa96ipPIOYy88MPrLm2Vsg/Pw9HevqDyVk20DAGBvLMuGKIpxQRphKq5icF7JG3RsBdnWDqUQ7AD3U6jLJyejiyJfcQRHaKj2o6/sPwS5Hi0xh0Zkmb9htaTW6bIEYKkCqUiDVatxRXM= Received: by 10.70.8.2 with SMTP id 2mr1456467wxh; Sun, 04 Jun 2006 00:29:31 -0700 (PDT) Received: by 10.70.43.11 with HTTP; Sun, 4 Jun 2006 00:29:31 -0700 (PDT) Message-ID: <87ab37ab0606040029u67edc35ende0b34e39e80bd37@mail.gmail.com> Date: Sun, 4 Jun 2006 15:29:31 +0800 From: "william wallace" Sender: fierykylin@gmail.com To: "Warner Losh" In-Reply-To: <20060520.013546.104050983.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-2022-JP; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <87ab37ab0605192015h363ef74aw23dcc2d97721dea9@mail.gmail.com> <20060519.232002.71106210.imp@bsdimp.com> <87ab37ab0605192239n73b7fcdbtbdd5dbd3f1099fc3@mail.gmail.com> <20060520.013546.104050983.imp@bsdimp.com> X-Google-Sender-Auth: 916a99c1dc7c7660 Cc: freebsd-hackers@freebsd.org Subject: Re: misc questions about the device&driver arch 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, 04 Jun 2006 07:29:34 -0000 On 5/20/06, Warner Losh wrote: > From: "william wallace" > Subject: Re: misc questions about the device&driver arch > Date: Sat, 20 May 2006 13:39:08 +0800 > > > comparing the method array of pci_pci and cardbusbridge: > > what losts in pci bridge but exist in cardbusbridge: > > 1 card interface > > 2 power interface > > 3 some functions : > > 3ain bus interface > > (bus_driver_added, cbb_driver_added), > > (bus_child_detached, cbb_child_detached), > > (bus_child_present, cbb_child_present), > > 3b in device interface > > (device_detach, cbb_detach), > > what exists in pci bridge but losts in cardbusbridge: > > (pcib_route_interrupt, pcib_route_interrupt), > > > > not only that ,functions r very different eventhough they realize the > > same interface function template > > wooo，so long to go to hotplug pci > > Yes. The hardest part would be to create a pci hot swap bridge > driver. The interface for them tend to be underdocumented. > > The bus_child_present is important for detaching. > > Also, I think that we may need to start implementing a quiess method > to tell the drivers they are about to be removed. For hot plug PCI, > the model is that you quess the driver, the os tells you somehow it is > safe, and then you remove the card. The details vary (some system are > all in software, while others have a complicated interlock and LEDs), > but they are similar. Cardbus is harder in some ways because cards > leave unannounced (in fact, there's not a good way to announce a card > leaving, but there should be). > > Warner > > > On 5/20/06, Warner Losh wrote: > > > > > Busses create devices to represent hardware in the system. The bus > > > then causes these devices to be probed and attached. This latter > > > usage is for those cases. As drivers are loaded these devices are > > > offered to the new (and old) drivers in the system. > > > > > > FreeBSD inherently dynamic in its device system. The hardest part of > > > adding hotplug support is programming the bridge. Adding new devices > > > to the tree is easy, but knowing when to add them is hard since you > > > have to write a bridge driver... > > > > > > Warner Prior to removing a card from the system, two things must occur: The device's driver must cease accessing the card. The card must cease generation transaction and interrupts. How this is accomplished is OS-specific, but the following must take place: The OS must stop issuing new requests to the device's driver or must instruct the driver to stop accepting new requests. The driver must terminate or complete all outstanding requests. The card must be disabled from generating interrupts or transactions. When the OS commands the driver to quiesce itself and its device, the OS must not expect the device to remain in the system (in other words, it could be removed and not replaced with a similar card). How to design and implement quiescing in freebsd? -- we who r about to die,salute u! From owner-freebsd-hackers@FreeBSD.ORG Sun Jun 4 09:30:01 2006 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 343DE16A492 for ; Sun, 4 Jun 2006 09:30:01 +0000 (UTC) (envelope-from unledev@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 467F943D49 for ; Sun, 4 Jun 2006 09:30:00 +0000 (GMT) (envelope-from unledev@gmail.com) Received: by nz-out-0102.google.com with SMTP id 13so796733nzn for ; Sun, 04 Jun 2006 02:29:59 -0700 (PDT) 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=CA8taQFkW1r+AkapP/YMerivMMl1Oe2dkbgC1QLKNNZ2BqucWGguxqTz+eTrN6r/wuaHm0kqyiyeH5S9hjL+x8699Ru8GshVoAVQtIxX4NJ+g9tFLH+eP43x0tRHhVPMANReX3kvE6XYE0wpLsJqaUmY2m35IH0uMwzxkPjWef0= Received: by 10.64.83.17 with SMTP id g17mr2836287qbb; Sun, 04 Jun 2006 02:29:59 -0700 (PDT) Received: by 10.65.181.5 with HTTP; Sun, 4 Jun 2006 02:29:59 -0700 (PDT) Message-ID: <5e4707340606040229s1689fa5cl758d8d7df1ce2b60@mail.gmail.com> Date: Sun, 4 Jun 2006 11:29:59 +0200 From: "=?ISO-8859-1?Q?Alex_Mart=EDnez?=" To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: __getcwd() 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: Sun, 04 Jun 2006 09:30:01 -0000 Hi guys, I've come across some problems while porting to FreeBSD a wrapper library which protects the filesystem from unauthorized accesses by overriding potentially dangerous functions and making some checks before calling the real thing. Turns out that overriding getcwd() resulted in segfaults because the library wrapped both getcwd() and __getcwd(), so that libc's getcwd() would call my wrapped __getcwd() instead of its own version, and my version would call libc's getcwd() again (which is wrong anyways), effectively building an infinite recursion loop. This stems from the fact that __getcwd() is exported by FreeBSD's libc (as a weak alias to __sys___getcwd(), along with ___getcwd()), while the libc this library ran originally on (GNU) does not export it. So here come my questions: is there any legal use of __getcwd() (and the other two functions for that matter) outside the libc? Any reason explaining why it should be exported? I guess backwards compatibility can be one such reason, but I'd like to know what you people think about it, specially if they were initially exported on purpose. TIA, Alex From owner-freebsd-hackers@FreeBSD.ORG Sun Jun 4 10:37:38 2006 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 3E92516A474 for ; Sun, 4 Jun 2006 10:37:38 +0000 (UTC) (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 D6A2343D48 for ; Sun, 4 Jun 2006 10:37:37 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [IPv6:::1] (may be forged)) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id k54AbHMB035954; Sun, 4 Jun 2006 04:37:17 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sun, 04 Jun 2006 04:37:25 -0600 (MDT) Message-Id: <20060604.043725.778152499.imp@bsdimp.com> To: avalonwallace@gmail.com From: "M. Warner Losh" In-Reply-To: <87ab37ab0606040029u67edc35ende0b34e39e80bd37@mail.gmail.com> References: <87ab37ab0605192239n73b7fcdbtbdd5dbd3f1099fc3@mail.gmail.com> <20060520.013546.104050983.imp@bsdimp.com> <87ab37ab0606040029u67edc35ende0b34e39e80bd37@mail.gmail.com> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: misc questions about the device&driver arch 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, 04 Jun 2006 10:37:39 -0000 In message: <87ab37ab0606040029u67edc35ende0b34e39e80bd37@mail.gmail.com> "william wallace" writes: : On 5/20/06, Warner Losh wrote: : > From: "william wallace" : > Subject: Re: misc questions about the device&driver arch : > Date: Sat, 20 May 2006 13:39:08 +0800 : > : > > comparing the method array of pci_pci and cardbusbridge: : > > what losts in pci bridge but exist in cardbusbridge: : > > 1 card interface : > > 2 power interface : > > 3 some functions : : > > 3ain bus interface : > > (bus_driver_added, cbb_driver_added), : > > (bus_child_detached, cbb_child_detached), : > > (bus_child_present, cbb_child_present), : > > 3b in device interface : > > (device_detach, cbb_detach), : > > what exists in pci bridge but losts in cardbusbridge: : > > (pcib_route_interrupt, pcib_route_interrupt), : > > : > > not only that ,functions r very different eventhough they realize the : > > same interface function template : > > wooo，so long to go to hotplug pci : > : > Yes. The hardest part would be to create a pci hot swap bridge : > driver. The interface for them tend to be underdocumented. : > : > The bus_child_present is important for detaching. : > : > Also, I think that we may need to start implementing a quiess method : > to tell the drivers they are about to be removed. For hot plug PCI, : > the model is that you quess the driver, the os tells you somehow it is : > safe, and then you remove the card. The details vary (some system are : > all in software, while others have a complicated interlock and LEDs), : > but they are similar. Cardbus is harder in some ways because cards : > leave unannounced (in fact, there's not a good way to announce a card : > leaving, but there should be). : > : > Warner : > : > > On 5/20/06, Warner Losh wrote: : > > : > > > Busses create devices to represent hardware in the system. The bus : > > > then causes these devices to be probed and attached. This latter : > > > usage is for those cases. As drivers are loaded these devices are : > > > offered to the new (and old) drivers in the system. : > > > : > > > FreeBSD inherently dynamic in its device system. The hardest part of : > > > adding hotplug support is programming the bridge. Adding new devices : > > > to the tree is easy, but knowing when to add them is hard since you : > > > have to write a bridge driver... : > > > : > > > Warner : Prior to removing a card from the system, two things must occur: : : The device's driver must cease accessing the card. : : The card must cease generation transaction and interrupts. : : How this is accomplished is OS-specific, but the following must take place: : : The OS must stop issuing new requests to the device's driver or must : instruct the driver to stop accepting new requests. : : The driver must terminate or complete all outstanding requests. : : The card must be disabled from generating interrupts or transactions. : : When the OS commands the driver to quiesce itself and its device, the : OS must not expect the device to remain in the system (in other words, : it could be removed and not replaced with a similar card). : : How to design and implement quiescing in freebsd? device_quiesce? I have it in a p4 tree right now. Specifically, it hooks up to the MOD_UNLOAD with a QUIESCE flag. The driver's device_quiesce routine gets called, the driver sleeps there until it knows that it is good, then returns to the caller. Then the driver's detach routine can be called. Warner From owner-freebsd-hackers@FreeBSD.ORG Sun Jun 4 10:42:22 2006 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 B343516A420 for ; Sun, 4 Jun 2006 10:42:22 +0000 (UTC) (envelope-from fierykylin@gmail.com) Received: from wx-out-0102.google.com (wx-out-0102.google.com [66.249.82.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 35C1943D60 for ; Sun, 4 Jun 2006 10:42:21 +0000 (GMT) (envelope-from fierykylin@gmail.com) Received: by wx-out-0102.google.com with SMTP id i31so577840wxd for ; Sun, 04 Jun 2006 03:42:20 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=RFIToweJELwXupPTREiWiCkIMfbu08035cMGw+czfqcGsKJWrk1JF32C3vIs5AwLrGQqBoYGVPqfNVBBfq7HvEV/3yBfelbcASv6GSKdH3mxKl94a1EhB/EIAz9fvZzmT6a0qhgYYkBYsoxfNwo5VdWOl2f8vQPVJ6vRb/nsdxk= Received: by 10.70.102.11 with SMTP id z11mr4722357wxb; Sun, 04 Jun 2006 03:42:20 -0700 (PDT) Received: by 10.70.43.11 with HTTP; Sun, 4 Jun 2006 03:42:20 -0700 (PDT) Message-ID: <87ab37ab0606040342y55ef91baje8f07d68e1a70464@mail.gmail.com> Date: Sun, 4 Jun 2006 18:42:20 +0800 From: "william wallace" Sender: fierykylin@gmail.com To: "M. Warner Losh" In-Reply-To: <20060604.043725.778152499.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <87ab37ab0605192239n73b7fcdbtbdd5dbd3f1099fc3@mail.gmail.com> <20060520.013546.104050983.imp@bsdimp.com> <87ab37ab0606040029u67edc35ende0b34e39e80bd37@mail.gmail.com> <20060604.043725.778152499.imp@bsdimp.com> X-Google-Sender-Auth: 3624d08cee681785 Cc: freebsd-hackers@freebsd.org Subject: Re: misc questions about the device&driver arch 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, 04 Jun 2006 10:42:22 -0000 On 6/4/06, M. Warner Losh wrote: > In message: <87ab37ab0606040029u67edc35ende0b34e39e80bd37@mail.gmail.com> > : > > > Warner > : Prior to removing a card from the system, two things must occur: > : > : The device's driver must cease accessing the card. > : > : The card must cease generation transaction and interrupts. > : > : How this is accomplished is OS-specific, but the following must take place: > : > : The OS must stop issuing new requests to the device's driver or must > : instruct the driver to stop accepting new requests. > : > : The driver must terminate or complete all outstanding requests. > : > : The card must be disabled from generating interrupts or transactions. > : > : When the OS commands the driver to quiesce itself and its device, the > : OS must not expect the device to remain in the system (in other words, > : it could be removed and not replaced with a similar card). > : > : How to design and implement quiescing in freebsd? > > device_quiesce? I have it in a p4 tree right now. Specifically, it > hooks up to the MOD_UNLOAD with a QUIESCE flag. The driver's > device_quiesce routine gets called, the driver sleeps there until it > knows that it is good, then returns to the caller. Then the driver's > detach routine can be called. > > Warner > where can i get the p4 tree read ,sir -- we who r about to die,salute u! From owner-freebsd-hackers@FreeBSD.ORG Sun Jun 4 11:01:14 2006 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 27A4516A477 for ; Sun, 4 Jun 2006 11:01:14 +0000 (UTC) (envelope-from maxim@macomnet.ru) Received: from mp2.macomnet.net (mp2.macomnet.net [195.128.64.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2FCE143D55 for ; Sun, 4 Jun 2006 11:01:12 +0000 (GMT) (envelope-from maxim@macomnet.ru) Received: from localhost (localhost [127.0.0.1]) by mp2.macomnet.net (8.13.4/8.13.3) with ESMTP id k54B1AYO064264; Sun, 4 Jun 2006 15:01:10 +0400 (MSD) (envelope-from maxim@macomnet.ru) Date: Sun, 4 Jun 2006 15:01:10 +0400 (MSD) From: Maxim Konovalov To: Matt Emmerton In-Reply-To: <20060523000227.M81386@mp2.macomnet.net> Message-ID: <20060604145844.Q63310@mp2.macomnet.net> References: <002a01c5db7c$6817e030$1200a8c0@gsicomp.on.ca> <20060523000227.M81386@mp2.macomnet.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-hackers@freebsd.org Subject: Re: RFC: porting NetBSD fsdb enhancements to 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: Sun, 04 Jun 2006 11:01:14 -0000 On Tue, 23 May 2006, 00:19+0400, Maxim Konovalov wrote: > Hi Matt, > > On Fri, 28 Oct 2005, 00:59-0400, Matt Emmerton wrote: > > > Recently I've had to do some low-level surgery on some disks that > > have gone bad in order to recover some of the data. This has > > required me to zero out blocks on disk, patch up the affected > > files, and pull the data off the disks. > > > > I was toying around the with fsdb tool, but couldn't figure out a > > way to map blocks to inodes (although the 'blocks' command does > > the mapping in the other direction quite nicely.) > > > > Poking around I found that someone has added this functionality > > (via a "findblk" command) to NetBSD's fsdb (back in 2003!), which > > I have grafted onto a 4.x box here with relative ease. > > > > NetBSD Mailing List Posting: > > http://groups.google.com/group/mailing.netbsd.tech.userlevel/browse_thread/thread/18acceb04cf5aadb/2a891d67edf9279%232a891d67edf9279?sa=X&oi=groupsr&start=0&num=3) > > NetBSD CVS: > > http://cvsweb.netbsd.org/bsdweb.cgi/src/sbin/fsdb/fsdb.c.diff?r1=1.24&r2=1.25&f=h > > > > Is this something that folks would like to see on FreeBSD? I've > > got RELENG_5_4 and RELENG_6_0 boxes here in my office so I can > > whip up the patches and do some testing in short order. > > I think it is a useful functionality. Here is a patch based on NetBSD > code for HEAD, should work for RELENG_5 and RELENG_6 also. [ patch skipped ] For the record: I committed this code to HEAD. Here is another cookie for fsdb(8): show and set inode birth time. http://people.freebsd.org/~maxim/diff/fsdb-btime.diff -- Maxim Konovalov From owner-freebsd-hackers@FreeBSD.ORG Sun Jun 4 12:07:16 2006 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 34B2416A537 for ; Sun, 4 Jun 2006 12:07:16 +0000 (UTC) (envelope-from lists-freebsd@silverwraith.com) Received: from pear.silverwraith.com (pear.silverwraith.com [69.12.167.160]) by mx1.FreeBSD.org (Postfix) with ESMTP id DC2A743D5A for ; Sun, 4 Jun 2006 12:07:13 +0000 (GMT) (envelope-from lists-freebsd@silverwraith.com) Received: from avleen by pear.silverwraith.com with local (Exim 4.61 (FreeBSD)) (envelope-from ) id 1FmrNx-0002Hh-Mi for freebsd-hackers@freebsd.org; Sun, 04 Jun 2006 05:07:13 -0700 Date: Sun, 4 Jun 2006 05:07:13 -0700 From: Avleen Vig To: freebsd-hackers@freebsd.org Message-ID: <20060604120713.GP3685@silverwraith.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.11 Subject: Snapshot's causing access problems X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Jun 2006 12:07:28 -0000 Is anyone else experiencing this? I'm finding that during times when a snapshot is being created for a partition, all access of that partition hangs until the snapshot is completed. On a large partition (180Gb, 66% used), this takes over 10 minutes for me. I've found that any time the partition (which is NFS mounted) is being accessed when the snapshot creation starts, the creation seems to take an even longer amount of time and sometimes isn't complete after 30 mins when I reboot the box. The problem is also really bad when the background fsck is starting and makes a snapshot first, which takes a lot of production time out a server which just crashed that I'm trying to restore. -- Avleen Vig Systems Administrator Personal: www.silverwraith.com "Wickedness is a myth invented by good people to account for the curious attractiveness of others." - Oscar Wilde From owner-freebsd-hackers@FreeBSD.ORG Sun Jun 4 15:23:48 2006 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 4F83D16A830 for ; Sun, 4 Jun 2006 15:23:48 +0000 (UTC) (envelope-from fierykylin@gmail.com) Received: from wx-out-0102.google.com (wx-out-0102.google.com [66.249.82.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9007843D5E for ; Sun, 4 Jun 2006 15:23:39 +0000 (GMT) (envelope-from fierykylin@gmail.com) Received: by wx-out-0102.google.com with SMTP id i31so603904wxd for ; Sun, 04 Jun 2006 08:23:36 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=d3CdtlY/kUe8zCnW6TphofUE9+wq1tH3vWpmNzkRkiZg5oGwDZ/ql+rS9TmVl9pp388JWXEpPhKYmoiKB0F7p12HAz1ZYcaFQgEP9t9XUqfOnF7E8RvhE8cAaNsKM3jEd2TjIZf04wvTWfAcxNli+Uc9GlvCXhh9yUqle1Xaj2I= Received: by 10.70.49.6 with SMTP id w6mr4994701wxw; Sun, 04 Jun 2006 08:23:36 -0700 (PDT) Received: by 10.70.43.11 with HTTP; Sun, 4 Jun 2006 08:23:36 -0700 (PDT) Message-ID: <87ab37ab0606040823k73cf27b1q787d544ce19a9687@mail.gmail.com> Date: Sun, 4 Jun 2006 23:23:36 +0800 From: "william wallace" Sender: fierykylin@gmail.com To: "M. Warner Losh" In-Reply-To: <20060604.043725.778152499.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-2022-JP; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <87ab37ab0605192239n73b7fcdbtbdd5dbd3f1099fc3@mail.gmail.com> <20060520.013546.104050983.imp@bsdimp.com> <87ab37ab0606040029u67edc35ende0b34e39e80bd37@mail.gmail.com> <20060604.043725.778152499.imp@bsdimp.com> X-Google-Sender-Auth: 4e21d33b5c77d68d Cc: freebsd-hackers@freebsd.org Subject: Re: misc questions about the device&driver arch 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, 04 Jun 2006 15:23:54 -0000 Sir: now i am dealing with the pciexpress resource release and allocation i found it hard to distinguish between the bus_alloc_resource familiy(type rid and flag) and the rman_get/set_***** family(struct rman and resource ) ,i have heard that memory resource which alloc by the bus_alloc_resource should not be refer to by rid , " SYS_RES_MEMORY Memory-access is done with the bus_space_(read,write)_(1,2,3,4) functions (depends on how many bytes you want to read/write). u_int8_t old; old = bus_space_read_1(sc->bst, sc->bsh, 0); bus_space_write_1(sc->bst, sc->bsh, 0, old); " is that true? the second question ,if i do hot swap and donot release the hot remove card 's resource ,how can i attach it to the newly add-in card ? shall i do a pci_write_config(child, rle->rid, rle->start, 4);to pin the resource to the pci space ? i wonder if there 's a find document for the freebsd resource topology, thank you ,sir . On 6/4/06, M. Warner Losh wrote: > In message: <87ab37ab0606040029u67edc35ende0b34e39e80bd37@mail.gmail.com> > "william wallace" writes: > : On 5/20/06, Warner Losh wrote: > : > From: "william wallace" > : > Subject: Re: misc questions about the device&driver arch > : > Date: Sat, 20 May 2006 13:39:08 +0800 > : > > : > > comparing the method array of pci_pci and cardbusbridge: > : > > what losts in pci bridge but exist in cardbusbridge: > : > > 1 card interface > : > > 2 power interface > : > > 3 some functions : > : > > 3ain bus interface > : > > (bus_driver_added, cbb_driver_added), > : > > (bus_child_detached, cbb_child_detached), > : > > (bus_child_present, cbb_child_present), > : > > 3b in device interface > : > > (device_detach, cbb_detach), > : > > what exists in pci bridge but losts in cardbusbridge: > : > > (pcib_route_interrupt, pcib_route_interrupt), > : > > > : > > not only that ,functions r very different eventhough they realize the > : > > same interface function template > : > > wooo，so long to go to hotplug pci > : > > : > Yes. The hardest part would be to create a pci hot swap bridge > : > driver. The interface for them tend to be underdocumented. > : > > : > The bus_child_present is important for detaching. > : > > : > Also, I think that we may need to start implementing a quiess method > : > to tell the drivers they are about to be removed. For hot plug PCI, > : > the model is that you quess the driver, the os tells you somehow it is > : > safe, and then you remove the card. The details vary (some system are > : > all in software, while others have a complicated interlock and LEDs), > : > but they are similar. Cardbus is harder in some ways because cards > : > leave unannounced (in fact, there's not a good way to announce a card > : > leaving, but there should be). > : > > : > Warner > : > > : > > On 5/20/06, Warner Losh wrote: > : > > > : > > > Busses create devices to represent hardware in the system. The bus > : > > > then causes these devices to be probed and attached. This latter > : > > > usage is for those cases. As drivers are loaded these devices are > : > > > offered to the new (and old) drivers in the system. > : > > > > : > > > FreeBSD inherently dynamic in its device system. The hardest part of > : > > > adding hotplug support is programming the bridge. Adding new devices > : > > > to the tree is easy, but knowing when to add them is hard since you > : > > > have to write a bridge driver... > : > > > > : > > > Warner > : Prior to removing a card from the system, two things must occur: > : > : The device's driver must cease accessing the card. > : > : The card must cease generation transaction and interrupts. > : > : How this is accomplished is OS-specific, but the following must take place: > : > : The OS must stop issuing new requests to the device's driver or must > : instruct the driver to stop accepting new requests. > : > : The driver must terminate or complete all outstanding requests. > : > : The card must be disabled from generating interrupts or transactions. > : > : When the OS commands the driver to quiesce itself and its device, the > : OS must not expect the device to remain in the system (in other words, > : it could be removed and not replaced with a similar card). > : > : How to design and implement quiescing in freebsd? > > device_quiesce? I have it in a p4 tree right now. Specifically, it > hooks up to the MOD_UNLOAD with a QUIESCE flag. The driver's > device_quiesce routine gets called, the driver sleeps there until it > knows that it is good, then returns to the caller. Then the driver's > detach routine can be called. > > Warner > -- we who r about to die,salute u! From owner-freebsd-hackers@FreeBSD.ORG Sun Jun 4 16:07:46 2006 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 E83C716A506 for ; Sun, 4 Jun 2006 16:07:46 +0000 (UTC) (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 853A043D45 for ; Sun, 4 Jun 2006 16:07:46 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [IPv6:::1] (may be forged)) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id k54G74jU038816; Sun, 4 Jun 2006 10:07:05 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sun, 04 Jun 2006 10:07:13 -0600 (MDT) Message-Id: <20060604.100713.-552478981.imp@bsdimp.com> To: avalonwallace@gmail.com From: "M. Warner Losh" In-Reply-To: <87ab37ab0606040823k73cf27b1q787d544ce19a9687@mail.gmail.com> References: <87ab37ab0606040029u67edc35ende0b34e39e80bd37@mail.gmail.com> <20060604.043725.778152499.imp@bsdimp.com> <87ab37ab0606040823k73cf27b1q787d544ce19a9687@mail.gmail.com> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: misc questions about the device&driver arch 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, 04 Jun 2006 16:07:51 -0000 In message: <87ab37ab0606040823k73cf27b1q787d544ce19a9687@mail.gmail.com> "william wallace" writes: : now i am dealing with the pciexpress resource release and allocation : i found it hard to distinguish between the bus_alloc_resource : familiy(type rid and flag) and the rman_get/set_***** family(struct : rman and resource ) ,i have heard that memory resource which alloc by : the bus_alloc_resource should not be refer to by rid , : " SYS_RES_MEMORY : Memory-access is done with the bus_space_(read,write)_(1,2,3,4) : functions (depends on how many bytes you want to read/write). : u_int8_t old; : old = bus_space_read_1(sc->bst, sc->bsh, 0); : bus_space_write_1(sc->bst, sc->bsh, 0, old); " : is that true? bus_alloc_resources is how you get resources from your parent device. It will return a struct resource * that the rman* rouintes can access the insides of (let's call it r). bus_space_read_1(rman_get_bustag(r), rman_get_bushandle(r), 0); or the newer bus_read_1(r, 0); : the second question ,if i do hot swap and donot release the hot remove : card 's resource ,how can i attach it to the newly add-in card ? You must release the resource whent he card exits the system. : shall i do a : pci_write_config(child, rle->rid, rle->start, 4);to pin the resource : to the pci space ? No. The pci code should already handle things correctly. : i wonder if there 's a find document for the freebsd resource topology, There's not a centralized document outside of the source. Warner : thank you ,sir . : On 6/4/06, M. Warner Losh wrote: : > In message: <87ab37ab0606040029u67edc35ende0b34e39e80bd37@mail.gmail.com> : > "william wallace" writes: : > : On 5/20/06, Warner Losh wrote: : > : > From: "william wallace" : > : > Subject: Re: misc questions about the device&driver arch : > : > Date: Sat, 20 May 2006 13:39:08 +0800 : > : > : > : > > comparing the method array of pci_pci and cardbusbridge: : > : > > what losts in pci bridge but exist in cardbusbridge: : > : > > 1 card interface : > : > > 2 power interface : > : > > 3 some functions : : > : > > 3ain bus interface : > : > > (bus_driver_added, cbb_driver_added), : > : > > (bus_child_detached, cbb_child_detached), : > : > > (bus_child_present, cbb_child_present), : > : > > 3b in device interface : > : > > (device_detach, cbb_detach), : > : > > what exists in pci bridge but losts in cardbusbridge: : > : > > (pcib_route_interrupt, pcib_route_interrupt), : > : > > : > : > > not only that ,functions r very different eventhough they realize the : > : > > same interface function template : > : > > wooo，so long to go to hotplug pci : > : > : > : > Yes. The hardest part would be to create a pci hot swap bridge : > : > driver. The interface for them tend to be underdocumented. : > : > : > : > The bus_child_present is important for detaching. : > : > : > : > Also, I think that we may need to start implementing a quiess method : > : > to tell the drivers they are about to be removed. For hot plug PCI, : > : > the model is that you quess the driver, the os tells you somehow it is : > : > safe, and then you remove the card. The details vary (some system are : > : > all in software, while others have a complicated interlock and LEDs), : > : > but they are similar. Cardbus is harder in some ways because cards : > : > leave unannounced (in fact, there's not a good way to announce a card : > : > leaving, but there should be). : > : > : > : > Warner : > : > : > : > > On 5/20/06, Warner Losh wrote: : > : > > : > : > > > Busses create devices to represent hardware in the system. The bus : > : > > > then causes these devices to be probed and attached. This latter : > : > > > usage is for those cases. As drivers are loaded these devices are : > : > > > offered to the new (and old) drivers in the system. : > : > > > : > : > > > FreeBSD inherently dynamic in its device system. The hardest part of : > : > > > adding hotplug support is programming the bridge. Adding new devices : > : > > > to the tree is easy, but knowing when to add them is hard since you : > : > > > have to write a bridge driver... : > : > > > : > : > > > Warner : > : Prior to removing a card from the system, two things must occur: : > : : > : The device's driver must cease accessing the card. : > : : > : The card must cease generation transaction and interrupts. : > : : > : How this is accomplished is OS-specific, but the following must take place: : > : : > : The OS must stop issuing new requests to the device's driver or must : > : instruct the driver to stop accepting new requests. : > : : > : The driver must terminate or complete all outstanding requests. : > : : > : The card must be disabled from generating interrupts or transactions. : > : : > : When the OS commands the driver to quiesce itself and its device, the : > : OS must not expect the device to remain in the system (in other words, : > : it could be removed and not replaced with a similar card). : > : : > : How to design and implement quiescing in freebsd? : > : > device_quiesce? I have it in a p4 tree right now. Specifically, it : > hooks up to the MOD_UNLOAD with a QUIESCE flag. The driver's : > device_quiesce routine gets called, the driver sleeps there until it : > knows that it is good, then returns to the caller. Then the driver's : > detach routine can be called. : > : > Warner : > : : : -- : we who r about to die,salute u! : : From owner-freebsd-hackers@FreeBSD.ORG Sun Jun 4 18:48:56 2006 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 11E5B16A567 for ; Sun, 4 Jun 2006 18:48:56 +0000 (UTC) (envelope-from artifact.one@googlemail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id A128043D45 for ; Sun, 4 Jun 2006 18:48:55 +0000 (GMT) (envelope-from artifact.one@googlemail.com) Received: by py-out-1112.google.com with SMTP id m51so1183880pye for ; Sun, 04 Jun 2006 11:48:52 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=googlemail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=hWC0apRUO5w64OPWVE0JeZ1Z63RyOlw+T3Uqor5i1sN0iALaDG+sj4CI5rh9Rg2cnfCjhJzbtC13DVSSm+vsgcKheL9rg2fZv6xK00adlaZOla5X3D27QRP5gnwNuyFxAiyUb/S5H8KTWrqxVbBFAObjzpvwcnjXk/0/0qIGucQ= Received: by 10.35.131.10 with SMTP id i10mr5193858pyn; Sun, 04 Jun 2006 11:48:52 -0700 (PDT) Received: by 10.35.121.7 with HTTP; Sun, 4 Jun 2006 11:48:52 -0700 (PDT) Message-ID: <8e96a0b90606041148g5674ca31r74be2e1f9c79b640@mail.gmail.com> Date: Sun, 4 Jun 2006 19:48:52 +0100 From: "mal content" To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Strange behaviour from mkdir()? 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, 04 Jun 2006 18:48:56 -0000 Is this expected behaviour (I'm using the mkdir utility for the example, but the problem occurs using the system call directly): # mkdir . mkdir: .: File exists # mkdir .. mkdir: ..: File exists Now, the unusual one: # mkdir / mkdir: /: Is a directory Shouldn't it say 'file exists'? The mkdir() man page doesn't say that the function can set errno to EISDIR and yet that's what's happening here. FreeBSD 6.0-RELEASE-p7 MC From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 5 03:04:35 2006 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 9A26516A588 for ; Mon, 5 Jun 2006 03:04:35 +0000 (UTC) (envelope-from betogigi@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id EECC043D5A for ; Mon, 5 Jun 2006 03:04:33 +0000 (GMT) (envelope-from betogigi@gmail.com) Received: by nz-out-0102.google.com with SMTP id m7so933499nzf for ; Sun, 04 Jun 2006 20:04:33 -0700 (PDT) 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=W6tF7oWu9sKrCuLiBl824M8LTNsFqudQZETiX9iRiWtScNcLrCEPSWulq92q8RFJhr9w90InaypbaaL3x2GR2CXK1Fgl1fwd5vqlHSc5+4TOKYkX4PlRUS/3wLVIDhK2NLt615Dh+aMS9QSOLvdDLl8jJY5wZHQF9HhT7UN0zeE= Received: by 10.37.21.52 with SMTP id y52mr5528236nzi; Sun, 04 Jun 2006 20:04:33 -0700 (PDT) Received: by 10.36.134.11 with HTTP; Sun, 4 Jun 2006 20:04:33 -0700 (PDT) Message-ID: Date: Mon, 5 Jun 2006 00:04:33 -0300 From: "Roberto Lima" To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: D-Link DSL210 USB in FreeBSD 6.x ? 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, 05 Jun 2006 03:04:35 -0000 Hi all, How do I make to runs the DLINK DSL210 USB in my freebsd? I tried this with Linux, and I not have success .. Anyone can help me? Thanks and sorry for my bad english. Roberto. From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 5 03:22:43 2006 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 E409316A4AC for ; Mon, 5 Jun 2006 03:22:43 +0000 (UTC) (envelope-from root@solink.ru) Received: from ns.itam.nsc.ru (ns.itam.nsc.ru [194.226.179.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id 22C9C43D48 for ; Mon, 5 Jun 2006 03:22:42 +0000 (GMT) (envelope-from root@solink.ru) Received: from site.lan (itut.itam.nsc.ru [194.226.179.2]) by ns.itam.nsc.ru (8.13.1/8.13.1) with ESMTP id k553MWdP019596 for ; Mon, 5 Jun 2006 10:22:35 +0700 Received: from bocha.solink.office ([192.168.66.166]) (authenticated bits=0) by site.lan (8.12.11.20060308/8.12.11) with ESMTP id k553MVk2030311 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 5 Jun 2006 10:22:31 +0700 From: Bachilo Dmitry Organization: Solink Ltd To: freebsd-hackers@freebsd.org Date: Mon, 5 Jun 2006 10:22:34 +0700 User-Agent: KMail/1.9.1 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200606051022.35686.root@solink.ru> Subject: Re: D-Link DSL210 USB in FreeBSD 6.x ? 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, 05 Jun 2006 03:22:44 -0000 =F7 =D3=CF=CF=C2=DD=C5=CE=C9=C9 =CF=D4 =F0=CF=CE=C5=C4=C5=CC=D8=CE=C9=CB 05= =C9=C0=CE=D1 2006 10:04 Roberto Lima =CE=C1=D0=C9=D3=C1=CC(a): > Hi all, > How do I make to runs the DLINK DSL210 USB in my freebsd? I tried this > with Linux, and I not have success .. > > Anyone can help me? > > Thanks and sorry for my bad english. > > Roberto. Is sat a wireless network USB adapter? If so, then there is no way to run U= SB=20 Wi_Fi in FreeBSD nor in Linux, only PCI or PCMCIA adapters are supported fo= r=20 now as far as I know. Even with Windows native drivers. But no USB... > _______________________________________________ > 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" =2D-=20 =2D----------------------- =F3 =D5=D7=C1=D6=C5=CE=C9=C5=CD, =E2=C1=DE=C9=CC=CF =E4=CD=C9=D4=D2=C9=CA =F2=D5=CB=CF=D7=CF=C4=C9=D4=C5=CC=D8 =CF=D4=C4=C5=CC=C1 =D3=C9=D3=D4=C5=CD= =CE=CF=CA =C9=CE=D4=C5=C7=D2=C1=C3=C9=C9 =EF=EF=EF "=EB=CF=CD=D0=C1=CE=C9=D1 =F3=CF=EC=C9=CE=CB" From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 5 03:42:24 2006 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 0830D16A54F for ; Mon, 5 Jun 2006 03:42:24 +0000 (UTC) (envelope-from sangwoos@gmail.com) Received: from wx-out-0102.google.com (wx-out-0102.google.com [66.249.82.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 64EDB43D68 for ; Mon, 5 Jun 2006 03:42:18 +0000 (GMT) (envelope-from sangwoos@gmail.com) Received: by wx-out-0102.google.com with SMTP id i31so664547wxd for ; Sun, 04 Jun 2006 20:42:16 -0700 (PDT) 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=PrfaRbLiAsDMflm+4KK9futbHOaZ4Qvs/wUAV+6appKZkryuEvCxIXIAAByyMi6Sq00h6XFb2roPFnt60MzXrmH7A/52tq++uLniUb9VGWxL41KMfHd554nIkiETzhNhLieCNXLIqFwX39pVudcBARi0WhmERo/cTLlSw4GNK1s= Received: by 10.70.113.20 with SMTP id l20mr5608924wxc; Sun, 04 Jun 2006 20:42:16 -0700 (PDT) Received: by 10.70.14.5 with HTTP; Sun, 4 Jun 2006 20:42:16 -0700 (PDT) Message-ID: <4cbd01f40606042042m4f8633h73d737b676d820cd@mail.gmail.com> Date: Mon, 5 Jun 2006 12:42:16 +0900 From: "Sangwoo Shim" To: "Bachilo Dmitry" In-Reply-To: <200606051022.35686.root@solink.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-2022-JP; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200606051022.35686.root@solink.ru> Cc: freebsd-hackers@freebsd.org Subject: Re: D-Link DSL210 USB in FreeBSD 6.x ? 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, 05 Jun 2006 03:42:28 -0000 2006/6/5, Bachilo Dmitry : > В сообщении от Понедельник 05 июня 2006 10:04 Roberto Lima написал(a): > > Hi all, > > How do I make to runs the DLINK DSL210 USB in my freebsd? I tried this > > with Linux, and I not have success .. > > > > Anyone can help me? > > > > Thanks and sorry for my bad english. > > > > Roberto. > > Is sat a wireless network USB adapter? If so, then there is no way to run USB > Wi_Fi in FreeBSD nor in Linux, only PCI or PCMCIA adapters are supported for > now as far as I know. Even with Windows native drivers. But no USB... > Actually, some USB wireless adapters are supported via ural(4). If the adapter is made of Ralink USB chipset, it might just work by kldloading if_ural.ko. However, I've experienced frequent loss of connection during cvsup with if_ural, on modest-heavy traffic. > > _______________________________________________ > > 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" > > -- > ------------------------ > С уважением, Бачило Дмитрий > Руководитель отдела системной интеграции > ООО "Компания СоЛинк" > _______________________________________________ > 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" > -- Regards, Sangwoo Shim From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 5 11:01:40 2006 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 03B4F16A474 for ; Mon, 5 Jun 2006 11:01:40 +0000 (UTC) (envelope-from simon@comsys.ntu-kpi.kiev.ua) Received: from comsys.ntu-kpi.kiev.ua (comsys.ntu-kpi.kiev.ua [195.245.194.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id 36DBB43D45 for ; Mon, 5 Jun 2006 11:01:37 +0000 (GMT) (envelope-from simon@comsys.ntu-kpi.kiev.ua) Received: from pm513-1.comsys.ntu-kpi.kiev.ua (pm513-1.comsys.ntu-kpi.kiev.ua [10.18.52.101]) (authenticated bits=0) by comsys.ntu-kpi.kiev.ua (8.13.6/8.13.6) with ESMTP id k55B2egu052075 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Mon, 5 Jun 2006 14:02:40 +0300 (EEST) Received: by pm513-1.comsys.ntu-kpi.kiev.ua (Postfix, from userid 1001) id AD0025C023; Mon, 5 Jun 2006 14:01:36 +0300 (EEST) Date: Mon, 5 Jun 2006 14:01:36 +0300 From: Andrey Simonenko To: freebsd-hackers@freebsd.org Message-ID: <20060605110136.GA1348@pm513-1.comsys.ntu-kpi.kiev.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=unavailable version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on comsys.ntu-kpi.kiev.ua X-Virus-Scanned: ClamAV 0.82/1456/Thu May 11 08:57:31 2006 on comsys.ntu-kpi.kiev.ua X-Virus-Status: Clean Subject: Question about synchronization (nfssvc, vfs_busy) 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, 05 Jun 2006 11:01:40 -0000 Greetings, Can somebody comment following questions? I want to know where I'm wrong (I checked CURRENT). 1. If the nfsserver is a KLD, then it can be unloaded. There is the nfssvc(2) which is implemented in nfsserver and it is called without Giant. Suppose nfsrv_numnfsd is equal to 0 and some process calls nfssvc(NFSSVC_ADDSOCK), as the result copyin() is called, which can sleep due to possible vm fault, I do not even mention thread preemption. Now nfsserver is unloaded, since nfsrv_numnfsd is equal to zero; when blocked process in copyin() wakes up, it will be continue execution in non-existent KVM address space. 2. If vfs_busy() is called without LK_NOWAIT flag, then it can sleep if a filesystem is being unmounted. At some point unmount() will reach vfs_mount_destroy() and since there is one ref from vfs_busy() it will sleep 3 seconds and will notice MNTK_MWAIT flag and wake up a process, which is sleeping in vfs_busy(). How woken up process can work with mount structure in vfs_busy() after wakeup(), which could be already deallocated in vfs_mount_destroy()? From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 5 08:45:13 2006 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 B845316A420 for ; Mon, 5 Jun 2006 08:45:13 +0000 (UTC) (envelope-from tofik@oxygen.az) Received: from mail.azerin.com (mail.azerin.com [212.47.128.23]) by mx1.FreeBSD.org (Postfix) with SMTP id 9873F43D46 for ; Mon, 5 Jun 2006 08:45:10 +0000 (GMT) (envelope-from tofik@oxygen.az) Received: (qmail 35054 invoked from network); 5 Jun 2006 08:45:29 -0000 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on ml350.azerin.com X-Spam-Level: X-Spam-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00, UNPARSEABLE_RELAY autolearn=ham version=3.1.1 Received: from qmail by qscan (mail filter); 5 Jun 2006 08:45:29 +0000 Received: from unknown (HELO ?212.47.129.5?) (212.47.129.5) by mail.azerin.com with SMTP; 5 Jun 2006 08:45:29 -0000 Message-ID: <4483EF11.7010503@oxygen.az> Date: Mon, 05 Jun 2006 11:45:05 +0300 From: Tofik Suleymanov User-Agent: Thunderbird 1.5.0.2 (X11/20060425) MIME-Version: 1.0 To: viktor@rbg.informatik.tu-darmstadt.de Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Mon, 05 Jun 2006 11:38:24 +0000 Cc: freebsd-hackers@freebsd.org Subject: port of NetBSD IrDA frame level driver to 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: Mon, 05 Jun 2006 08:45:13 -0000 Hello, after patching my FREEBSD-6.1-RC with your irda patchset - i've loaded two produced kernel modules and reattached my usb-irda device and got following in system log: --- start --- Jun 5 11:30:48 paranoia kernel: ustir_match: uaa->iface = 0, uaa->vendor = 0x9710, uaa->product = 0x7780 Jun 5 11:30:48 paranoia kernel: ustir_match: uaa->iface = 0xc312bcc0, uaa->vendor = 0x9710, uaa->product = 0x7780 Jun 5 11:30:48 paranoia kernel: ustir_match: uaa->iface = 0, uaa->vendor = 0x9710, uaa->product = 0x7780 --- end --- Seems like my irda-device is not supported by your driver ? Additionally, no ustirX and no irframeX devices appear in /dev . i am ready to contribute any possible help in order to make this work. Tofik Suleymanov From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 5 11:58:42 2006 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 3B0C816A55C for ; Mon, 5 Jun 2006 11:58:42 +0000 (UTC) (envelope-from viktor.vasilev@stud.tu-darmstadt.de) Received: from lnx130.hrz.tu-darmstadt.de (lnx130.hrz.tu-darmstadt.de [130.83.174.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A28043D46 for ; Mon, 5 Jun 2006 11:58:40 +0000 (GMT) (envelope-from viktor.vasilev@stud.tu-darmstadt.de) Received: from mailserver3.hrz.tu-darmstadt.de (lnx116.hrz.tu-darmstadt.de [130.83.174.28]) by lnx130.hrz.tu-darmstadt.de (8.13.4/8.12.10) with ESMTP id k55BwdUY031258 for ; Mon, 5 Jun 2006 13:58:39 +0200 Received: from [130.83.20.203] (helo=ABC216.ram1st.wh.tu-darmstadt.de) by mailserver3.hrz.tu-darmstadt.de with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1FnDjD-0002X8-IU for freebsd-hackers@freebsd.org; Mon, 05 Jun 2006 13:58:39 +0200 From: Viktor Vasilev To: freebsd-hackers@freebsd.org Date: Mon, 5 Jun 2006 13:58:35 +0200 User-Agent: KMail/1.9.1 References: <4483EF11.7010503@oxygen.az> In-Reply-To: <4483EF11.7010503@oxygen.az> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1234919.TekzCyRaiU"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200606051358.38847.viktor.vasilev@stud.tu-darmstadt.de> Subject: Re: port of NetBSD IrDA frame level driver to 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: Mon, 05 Jun 2006 11:58:43 -0000 --nextPart1234919.TekzCyRaiU Content-Type: text/plain; charset="windows-1251" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Monday 05 June 2006 10:45 Tofik Suleymanov wrote: > Hello, > after patching my FREEBSD-6.1-RC with your irda patchset - i've loaded > two produced kernel modules and reattached my usb-irda device and got > following in system log: > --- start --- > Jun 5 11:30:48 paranoia kernel: ustir_match: uaa->iface =3D 0, > uaa->vendor =3D 0x9710, uaa->product =3D 0x7780 > Jun 5 11:30:48 paranoia kernel: ustir_match: uaa->iface =3D 0xc312bcc0, > uaa->vendor =3D 0x9710, uaa->product =3D 0x7780 > Jun 5 11:30:48 paranoia kernel: ustir_match: uaa->iface =3D 0, > uaa->vendor =3D 0x9710, uaa->product =3D 0x7780 > --- end --- > > Seems like my irda-device is not supported by your driver ? > Additionally, no ustirX and no irframeX devices appear in /dev . > i am ready to contribute any possible help in order to make this work. No it's not. Google says that's a dongle with a MosChip MCS7780, and not a= =20 SigmaTel STIR 4200: http://www.qbik.ch/usb/devices/showdev.php?id=3D2881 There appears to be a linux driver for the MCS7780: http://web.cecs.pdx.edu/~bpugh/mcs7780.html I don't actively work on the USB IrDA support on FreeBSD. This is mainly=20 because I'm lacking the hardware. Also bluetooth dongles are supported by=20 the netgraph bluetooth stack, and are cheaper than USB IrDA. Cheers, Vik =2D-=20 PGP Key: 0xE09DC8D8/6799 4011 EBDE 6412 05A1 090C DBDF 5887 E09D C8D8 Signed/encrypted mail welcome! --nextPart1234919.TekzCyRaiU Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQBEhBxu299Yh+CdyNgRAqflAJ43S6Yr8lnh3kTV2TnbCYBhf/dcpQCff0ro M6O6yWre8iFtKK6TRvJ/QC8= =bzCH -----END PGP SIGNATURE----- --nextPart1234919.TekzCyRaiU-- From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 5 12:24:06 2006 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 8429416A47F for ; Mon, 5 Jun 2006 12:24:06 +0000 (UTC) (envelope-from betogigi@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id 15AC943D48 for ; Mon, 5 Jun 2006 12:24:05 +0000 (GMT) (envelope-from betogigi@gmail.com) Received: by nz-out-0102.google.com with SMTP id m7so1010435nzf for ; Mon, 05 Jun 2006 05:24:05 -0700 (PDT) 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:content-transfer-encoding:content-disposition:references; b=uciMKyGoOl2Kbu0sKdSEh85Y66Nfrdp/AH6hhMcL9FS15hIyyI1hQVPRhoKNw+cWTbyVQfzaoiNEedDAEe0bfzoNfrQElryI63AkNEXC2lEL3qOr6neh1n1uh1FCUeRc++cQBUN3rgeOX5v+7XHAf+kc3jx/p3/fCKjpuV35o1k= Received: by 10.36.68.4 with SMTP id q4mr5473290nza; Mon, 05 Jun 2006 05:24:05 -0700 (PDT) Received: by 10.36.134.11 with HTTP; Mon, 5 Jun 2006 05:24:05 -0700 (PDT) Message-ID: Date: Mon, 5 Jun 2006 09:24:05 -0300 From: "Roberto Lima" To: freebsd-hackers@freebsd.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Subject: Re: D-Link DSL210 USB in FreeBSD 6.x ? 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, 05 Jun 2006 12:24:10 -0000 Mmm, Im sorry.. my problem is with D-Link DSL210 USB ADSL. its not wireless device. Thanks, Roberto. From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 5 13:13:57 2006 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 87B6016A41F for ; Mon, 5 Jun 2006 13:13:57 +0000 (UTC) (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 2F4E943D46 for ; Mon, 5 Jun 2006 13:13:56 +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 k55DDt8H070660; Mon, 5 Jun 2006 08:13:55 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <44842E19.8020307@centtech.com> Date: Mon, 05 Jun 2006 08:14:01 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5.0.2 (X11/20060506) MIME-Version: 1.0 To: Avleen Vig References: <20060604120713.GP3685@silverwraith.com> In-Reply-To: <20060604120713.GP3685@silverwraith.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1512/Sun Jun 4 04:58:49 2006 on mh2.centtech.com X-Virus-Status: Clean Cc: freebsd-hackers@freebsd.org Subject: Re: Snapshot's causing access problems X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Jun 2006 13:14:09 -0000 Avleen Vig wrote: > Is anyone else experiencing this? > > I'm finding that during times when a snapshot is being created for a > partition, all access of that partition hangs until the snapshot is > completed. > > On a large partition (180Gb, 66% used), this takes over 10 minutes for > me. > I've found that any time the partition (which is NFS mounted) is being > accessed when the snapshot creation starts, the creation seems to take > an even longer amount of time and sometimes isn't complete after 30 mins > when I reboot the box. > > The problem is also really bad when the background fsck is starting and > makes a snapshot first, which takes a lot of production time out a > server which just crashed that I'm trying to restore. > This is probably a known issue. I say probably because it sounds like the regular fs suspended state that the filesystem goes into when doing the snapshot. You didn't mention which FreeBSD version you were using, but many fixes have been made to recent 6-STABLE branches regarding filesystems, but none that will alleviate your problems. Have you tried burying your snapshot file down deeper in the directory tree, and changing the mode on the parent(s) to something only root could love? For instance: /.snap/2006/snapshotfile Where /.snap and /.snap/2006 are chmod 0700. I think that you might only see the locking/hanging if a process attempts to stat the snapshot file while it's being created. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 5 17:09:09 2006 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 4488816B310 for ; Mon, 5 Jun 2006 17:09:09 +0000 (UTC) (envelope-from pollo.es.pollo@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.171]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3927643D4C for ; Mon, 5 Jun 2006 17:09:07 +0000 (GMT) (envelope-from pollo.es.pollo@gmail.com) Received: by ug-out-1314.google.com with SMTP id m3so1497845uge for ; Mon, 05 Jun 2006 10:09:07 -0700 (PDT) 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=k+Q5qX6d0rDj5xWZUeGlL1siWHxG+m3Ueas+cPBOFeWqjip/gr2ZOpzsWFTSVlkiO6kpTgSFnmd9+K4qC/cMeu4ZLMUs3Cpr625Fw+SW6S1/D83TPtFSF2EX8vElqGgPMMbWN+5OrWNXFxGcOCArSX8wdwUxYyccTOOXOdglKZI= Received: by 10.67.105.19 with SMTP id h19mr3568044ugm; Mon, 05 Jun 2006 10:01:53 -0700 (PDT) Received: by 10.66.250.5 with HTTP; Mon, 5 Jun 2006 10:01:53 -0700 (PDT) Message-ID: <98c02f5f0606051001q655ee8d5o40ad19fe81fc1cea@mail.gmail.com> Date: Mon, 5 Jun 2006 19:01:53 +0200 From: "Omar Lopez Limonta" To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Old a.out binary files 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, 05 Jun 2006 17:09:14 -0000 Hi i have an old aplication that runs on red hat 6.0/8.0, it use very old Microsoft Xenix a.out format are there any way to run it on modern FreeBSD? -- http://www.tuactualidad.com IM: pollo.es.pollo en gmail.com Te lo traigo fresco. From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 5 17:31:00 2006 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 C66A816B3DA for ; Mon, 5 Jun 2006 17:31:00 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from fw.zoral.com.ua (ll-227.216.82.212.sovam.net.ua [212.82.216.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id A9EC043D46 for ; Mon, 5 Jun 2006 17:30:59 +0000 (GMT) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by fw.zoral.com.ua (8.13.4/8.13.4) with ESMTP id k55HUkC3092997 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 5 Jun 2006 20:30:46 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6) with ESMTP id k55HUk0P056290; Mon, 5 Jun 2006 20:30:46 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6/Submit) id k55HUjxU056289; Mon, 5 Jun 2006 20:30:45 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 5 Jun 2006 20:30:45 +0300 From: Konstantin Belousov To: Andrey Simonenko Message-ID: <20060605173045.GA45380@deviant.kiev.zoral.com.ua> References: <20060605110136.GA1348@pm513-1.comsys.ntu-kpi.kiev.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="sm4nu43k4a2Rpi4c" Content-Disposition: inline In-Reply-To: <20060605110136.GA1348@pm513-1.comsys.ntu-kpi.kiev.ua> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: ClamAV version 0.88.2, clamav-milter version 0.88.2 on fw.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on fw.zoral.com.ua Cc: freebsd-hackers@freebsd.org Subject: Re: Question about synchronization (nfssvc, vfs_busy) 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, 05 Jun 2006 17:31:05 -0000 --sm4nu43k4a2Rpi4c Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jun 05, 2006 at 02:01:36PM +0300, Andrey Simonenko wrote: > 2. >=20 > If vfs_busy() is called without LK_NOWAIT flag, then it can sleep > if a filesystem is being unmounted. At some point unmount() will If vfs_busy() is called without LK_NOWAIT and fs is being unmounted, then vfs_busy returns with ENOENT error, isn't it ? > reach vfs_mount_destroy() and since there is one ref from vfs_busy() > it will sleep 3 seconds and will notice MNTK_MWAIT flag and wake up > a process, which is sleeping in vfs_busy(). How woken up process > can work with mount structure in vfs_busy() after wakeup(), which > could be already deallocated in vfs_mount_destroy()? vfs_busy() internally increases the ref count for mount point, so, it cannot be taken from under it (look for MNT_REF/MNT_REL). Simultameous entrance into the code in question in vfs_busy/vfs_mount_destroy is protected by mnt_mtx (MNT_ILOCK/MNT_IUNLOCK). --sm4nu43k4a2Rpi4c Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEhGpEC3+MBN1Mb4gRAhKLAKCzcwZcg0H7mlo5gt/FoSya8+HZMgCdGRBM QS+AKE9KhokSOoPDSb7Cxo8= =GDxq -----END PGP SIGNATURE----- --sm4nu43k4a2Rpi4c-- From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 5 18:27:11 2006 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 C4EFC16A704 for ; Mon, 5 Jun 2006 18:27:11 +0000 (UTC) (envelope-from dgilbert@daveg.ca) Received: from ox.eicat.ca (ox.eicat.ca [66.96.30.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D60043D49 for ; Mon, 5 Jun 2006 18:27:11 +0000 (GMT) (envelope-from dgilbert@daveg.ca) Received: by ox.eicat.ca (Postfix, from userid 66) id 574631D2DB; Mon, 5 Jun 2006 14:27:10 -0400 (EDT) Received: by canoe.dclg.ca (Postfix, from userid 101) id 15EFB4AC3B; Mon, 5 Jun 2006 14:27:02 -0400 (EDT) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17540.30581.541897.566515@canoe.dclg.ca> Date: Mon, 5 Jun 2006 14:27:01 -0400 To: freebsd-hackers@freebsd.org X-Mailer: VM 7.17 under 21.4 (patch 19) "Constant Variable" XEmacs Lucid Subject: tun and SIOCSIFADDR 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, 05 Jun 2006 18:27:18 -0000 I read in the if_tun manpage that it supports SIOCSIFADDR (such that it works with ifconfig). I like examples, so I search the ifconfig source code for SIOCSIFADDR. None. Then I search the entire source tree. ppp uses it to set the IPX address. Obviously SIOCSIFADDR is not the preferred way to do this anymore. Hints? Dave. -- ============================================================================ |David Gilbert, Independent Contractor. | Two things can be | |Mail: dave@daveg.ca | equal if and only if they | |http://daveg.ca | are precisely opposite. | =========================================================GLO================ From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 5 19:40:11 2006 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 A8F6616B611 for ; Mon, 5 Jun 2006 19:40:11 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 21E3E43D76 for ; Mon, 5 Jun 2006 19:40:10 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id D54A31FFACC; Mon, 5 Jun 2006 21:40:08 +0200 (CEST) Received: by transport.cksoft.de (Postfix, from userid 66) id 661D71FFACB; Mon, 5 Jun 2006 21:40:05 +0200 (CEST) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id CB9E64448D6; Mon, 5 Jun 2006 19:36:20 +0000 (UTC) Date: Mon, 5 Jun 2006 19:36:20 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: David Gilbert In-Reply-To: <17540.30581.541897.566515@canoe.dclg.ca> Message-ID: <20060605193051.B79180@maildrop.int.zabbadoz.net> References: <17540.30581.541897.566515@canoe.dclg.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Cc: freebsd-hackers@freebsd.org Subject: Re: tun and SIOCSIFADDR 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, 05 Jun 2006 19:40:20 -0000 On Mon, 5 Jun 2006, David Gilbert wrote: > I read in the if_tun manpage that it supports SIOCSIFADDR (such that > it works with ifconfig). I like examples, so I search the ifconfig > source code for SIOCSIFADDR. None. Then I search the entire source > tree. ppp uses it to set the IPX address. Obviously SIOCSIFADDR is > not the preferred way to do this anymore. Hints? SIOCSIFADDR/SIOCSIFDSTADDR was deprecated about 10 years ago. See man 4 netintro /Calls which are now deprecated are . If you want SIOCSIFADDR/SIOCSIFDSTADDR for tun you need a patch I have in my tree. SIOCAIFADDR is what you really want. Look at ppp sources for examples for example. -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 5 20:00:46 2006 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 A89FF16C848 for ; Mon, 5 Jun 2006 20:00:45 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 19B6943D73 for ; Mon, 5 Jun 2006 20:00:10 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 9321A1FFACB; Mon, 5 Jun 2006 22:00:09 +0200 (CEST) Received: by transport.cksoft.de (Postfix, from userid 66) id D179D1FFACE; Mon, 5 Jun 2006 22:00:05 +0200 (CEST) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id 2F1724448D6; Mon, 5 Jun 2006 19:55:27 +0000 (UTC) Date: Mon, 5 Jun 2006 19:55:27 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: David Gilbert In-Reply-To: <20060605193051.B79180@maildrop.int.zabbadoz.net> Message-ID: <20060605195307.L79180@maildrop.int.zabbadoz.net> References: <17540.30581.541897.566515@canoe.dclg.ca> <20060605193051.B79180@maildrop.int.zabbadoz.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Cc: freebsd-hackers@freebsd.org Subject: Re: tun and SIOCSIFADDR 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, 05 Jun 2006 20:00:57 -0000 On Mon, 5 Jun 2006, Bjoern A. Zeeb wrote: > On Mon, 5 Jun 2006, David Gilbert wrote: > >> I read in the if_tun manpage that it supports SIOCSIFADDR (such that >> it works with ifconfig). I like examples, so I search the ifconfig >> source code for SIOCSIFADDR. None. Then I search the entire source >> tree. ppp uses it to set the IPX address. Obviously SIOCSIFADDR is >> not the preferred way to do this anymore. Hints? > > SIOCSIFADDR/SIOCSIFDSTADDR was deprecated about 10 years ago. See > man 4 netintro /Calls which are now deprecated are . > If you want SIOCSIFADDR/SIOCSIFDSTADDR for tun you need a patch I > have in my tree. > SIOCAIFADDR is what you really want. Look at ppp sources for examples > for example. oops. I misread IPX for IP but it should apply equally (though I don't have a patch for that). -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 6 01:00:57 2006 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 DD1FD16E587 for ; Tue, 6 Jun 2006 00:08:35 +0000 (UTC) (envelope-from pieter@degoeje.nl) Received: from smtp.utwente.nl (smtp1.utsp.utwente.nl [130.89.2.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id D5F0643D58 for ; Tue, 6 Jun 2006 00:08:34 +0000 (GMT) (envelope-from pieter@degoeje.nl) Received: from nox.student.utwente.nl (nox.student.utwente.nl [130.89.165.91]) by smtp.utwente.nl (8.12.10/SuSE Linux 0.7) with ESMTP id k5608Txt013860; Tue, 6 Jun 2006 02:08:29 +0200 From: Pieter de Goeje To: freebsd-hackers@freebsd.org Date: Tue, 6 Jun 2006 02:08:28 +0200 User-Agent: KMail/1.9.1 References: <8e96a0b90606041148g5674ca31r74be2e1f9c79b640@mail.gmail.com> In-Reply-To: <8e96a0b90606041148g5674ca31r74be2e1f9c79b640@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200606060208.28838.pieter@degoeje.nl> X-UTwente-MailScanner-Information: Scanned by MailScanner. Contact helpdesk@ITBE.utwente.nl for more information. X-UTwente-MailScanner: Found to be clean X-UTwente-MailScanner-From: pieter@degoeje.nl X-Spam-Status: No Cc: mal content Subject: Re: Strange behaviour from mkdir()? 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, 06 Jun 2006 01:01:08 -0000 Hi MC, On Sunday 04 June 2006 20:48, mal content wrote: > Is this expected behaviour (I'm using the mkdir utility > for the example, but the problem occurs using the system > call directly): > > # mkdir . > mkdir: .: File exists > # mkdir .. > mkdir: ..: File exists > > Now, the unusual one: > > # mkdir / > mkdir: /: Is a directory > > Shouldn't it say 'file exists'? In fact, the _only_ directory that I could find that shows this behaviour is /. (I am using 6-stable) > > The mkdir() man page doesn't say that the function can set > errno to EISDIR and yet that's what's happening here. > I did some research on it, and it seems the mkdir utility is aware of the EISDIR error. Kinda weird if you ask me, since it isn't documented. Pieter de Goeje From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 6 02:14:03 2006 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 5437916AE20 for ; Tue, 6 Jun 2006 01:35:24 +0000 (UTC) (envelope-from artifact.one@googlemail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id C437443D5D for ; Tue, 6 Jun 2006 01:35:20 +0000 (GMT) (envelope-from artifact.one@googlemail.com) Received: by py-out-1112.google.com with SMTP id m51so1563295pye for ; Mon, 05 Jun 2006 18:35:20 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=googlemail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ALZqJmQx9TZLdXSJB5x0gD5RuHX1YNpQ9TDr13BcAM9TEP3yObpYznlchtQJzQqxRuJTSpMt/0xXF1cLLsIDDMOODpQrTnpUxLChhHZdnmnVH/WoMbAhoX/pR9sSAq1AljvvSkxFAGZoWdfz4ipfvyWqu0GVBtkJxoyMwdMJJJ4= Received: by 10.35.53.18 with SMTP id f18mr7429468pyk; Mon, 05 Jun 2006 18:35:20 -0700 (PDT) Received: by 10.35.121.7 with HTTP; Mon, 5 Jun 2006 18:35:20 -0700 (PDT) Message-ID: <8e96a0b90606051835j363547e0q4d8a549837c27b74@mail.gmail.com> Date: Tue, 6 Jun 2006 02:35:20 +0100 From: "mal content" To: "Pieter de Goeje" In-Reply-To: <200606060208.28838.pieter@degoeje.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <8e96a0b90606041148g5674ca31r74be2e1f9c79b640@mail.gmail.com> <200606060208.28838.pieter@degoeje.nl> Cc: freebsd-hackers@freebsd.org Subject: Re: Strange behaviour from mkdir()? 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, 06 Jun 2006 02:14:06 -0000 On 06/06/06, Pieter de Goeje wrote: > Hi MC, > > On Sunday 04 June 2006 20:48, mal content wrote: > > Is this expected behaviour (I'm using the mkdir utility > > for the example, but the problem occurs using the system > > call directly): > > > > # mkdir . > > mkdir: .: File exists > > # mkdir .. > > mkdir: ..: File exists > > > > Now, the unusual one: > > > > # mkdir / > > mkdir: /: Is a directory > > > > Shouldn't it say 'file exists'? > In fact, the _only_ directory that I could find that shows this behaviour > is /. (I am using 6-stable) > > > > > The mkdir() man page doesn't say that the function can set > > errno to EISDIR and yet that's what's happening here. > > > > I did some research on it, and it seems the mkdir utility is aware of the > EISDIR error. Kinda weird if you ask me, since it isn't documented. I followed the kern_mkdir() function and ended up in /src/sys/kern/vfs_lookup.c where this bit of code appears: 785: /* 786: * Check for degenerate name (e.g. / or "") 787: * which is a way of talking about a directory, 788: * e.g. like "/." or ".". 789: */ 790: if (cnp->cn_nameptr[0] == '\0') { 791: if (cnp->cn_nameiop != LOOKUP || wantparent) { 792: error = EISDIR; 793: goto bad; 794: } 795: if (dp->v_type != VDIR) { 796: error = ENOTDIR; 797: goto bad; 798: } Not sure if that code is completely correct, but what do I know... MC From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 6 03:39:42 2006 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 27CA316C102 for ; Tue, 6 Jun 2006 02:59:18 +0000 (UTC) (envelope-from jbaggs@san.rr.com) Received: from ms-smtp-01.socal.rr.com (ms-smtp-01.socal.rr.com [66.75.162.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9CDAC43D49 for ; Tue, 6 Jun 2006 02:59:17 +0000 (GMT) (envelope-from jbaggs@san.rr.com) Received: from [10.0.10.5] (cpe-24-165-11-242.san.res.rr.com [24.165.11.242]) by ms-smtp-01.socal.rr.com (8.13.6/8.13.6) with ESMTP id k562xGbr008511 for ; Mon, 5 Jun 2006 19:59:16 -0700 (PDT) Message-ID: <4484EF84.80808@san.rr.com> Date: Mon, 05 Jun 2006 19:59:16 -0700 From: Jeremy Baggs User-Agent: Thunderbird 1.5.0.2 (X11/20060510) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org X-Enigmail-Version: 0.94.0.0 Content-Type: multipart/mixed; boundary="------------030901050703070709090303" X-Virus-Scanned: Symantec AntiVirus Scan Engine Subject: kernel panic 6.1 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, 06 Jun 2006 03:39:43 -0000 This is a multi-part message in MIME format. --------------030901050703070709090303 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Got a panic today. following are output from uname -a and kgdb,with my kernel config as an attachment. FreeBSD shiva.home.lan 6.1-STABLE FreeBSD 6.1-STABLE #8: Thu Jun 1 23:42:46 PDT 2006 jbaggs@shiva.home.lan:/usr/obj/usr/src/sys/SHIVA i386 - ---------------------------------------------------------------------------------------------------------------------------------- This GDB was configured as "i386-marcel-freebsd". Unread portion of the kernel message buffer: panic: softdep_write_inodeblock: lost dep2 Uptime: 59s Dumping 511 MB (2 chunks) chunk 0: 1MB (159 pages) ... ok chunk 1: 511MB (130800 pages) 495 479 463 447 431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 191 175 159 143 1 27 111 95 79 63 47 31 15 #0 doadump () at pcpu.h:165 165 pcpu.h: No such file or directory. in pcpu.h (kgdb) where #0 doadump () at pcpu.h:165 #1 0xc0521afe in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409 #2 0xc0521d94 in panic (fmt=0xc06d5e94 "softdep_write_inodeblock: lost dep2") at /usr/src/sys/kern/kern_shutdown.c:565 #3 0xc062cde5 in initiate_write_inodeblock_ufs2 (inodedep=0xc3671380, bp=0x0) at /usr/src/sys/ufs/ffs/ffs_softdep.c:4151 #4 0xc062bfd7 in softdep_disk_io_initiation (bp=0xcd7d7160) at /usr/src/sys/ufs/ffs/ffs_softdep.c:3748 #5 0xc0634795 in ffs_geom_strategy (bo=0xc3554940, bp=0xcd7d7160) at buf.h:422 #6 0xc0566794 in bufwrite (bp=0xcd7d7160) at buf.h:415 #7 0xc0634656 in ffs_bufwrite (bp=0xcd7d7160) at /usr/src/sys/ufs/ffs/ffs_vfsops.c:1710 #8 0xc05681c3 in vfs_bio_awrite (bp=0xcd7d7160) at buf.h:399 #9 0xc056f1f4 in vop_stdfsync (ap=0xd5690cc0) at /usr/src/sys/kern/vfs_default.c:412 #10 0xc04d6473 in devfs_fsync (ap=0xd5690cc0) at /usr/src/sys/fs/devfs/devfs_vnops.c:307 #11 0xc06a45e4 in VOP_FSYNC_APV (vop=0x0, a=0x0) at vnode_if.c:1020 #12 0xc0577af8 in sync_vnode (bo=0xc3554940, td=0xc335ac00) at vnode_if.h:537 #13 0xc0577e11 in sched_sync () at /usr/src/sys/kern/vfs_subr.c:1679 #14 0xc050bffc in fork_exit (callout=0xc0577bbc , arg=0x0, frame=0xd5690d38) at /usr/src/sys/kern/kern_fork.c:805 #15 0xc0682d9c in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:208 (kgdb) up 4 #4 0xc062bfd7 in softdep_disk_io_initiation (bp=0xcd7d7160) at /usr/src/sys/ufs/ffs/ffs_softdep.c:3748 3748 initiate_write_inodeblock_ufs2(inodedep, bp); (kgdb) Quit - --------------------------------------------------------------------------------------------------------------------------------------------- Thanks to anyone who can help. Jeremy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEhO+DErogemV/I6ERAsuCAJ9Bj+AEQpXRqy7pT11Ukf2jpPoaLwCgwOcc B8yCJNPy2P2I832fZc95mI4= =wZOW -----END PGP SIGNATURE----- --------------030901050703070709090303 Content-Type: text/plain; name="SHIVA" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="SHIVA" # # SHIVA--kernel configuration file for FreeBSD/i386 # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # # http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ../../conf/NOTES and NOTES files. # If you are in doubt as to the purpose or necessity of a line, check first # in NOTES. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.429.2.3.2.1 2005/10/28 19:22:41 jhb Exp $ machine i386 #cpu I486_CPU #cpu I586_CPU cpu I686_CPU ident SHIVA maxusers 0 # To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" # Default places to look for devices. makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols #options SCHED_ULE # ULE scheduler options SCHED_4BSD # 4BSD scheduler options PREEMPTION # Enable kernel thread preemption options INET # InterNETworking options INET6 # IPv6 communications protocols options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories options MD_ROOT # MD is a potential root device options NFSCLIENT # Network Filesystem Client options NFSSERVER # Network Filesystem Server options NFS_ROOT # NFS usable as /, requires NFSCLIENT options MSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS # Pseudo-filesystem framework options GEOM_GPT # GUID Partition Tables. options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options COMPAT_FREEBSD5 # Compatible with FreeBSD5 options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV # install a CDEV entry in /dev options AHC_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~128k to driver. options AHD_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~215k to driver. options ADAPTIVE_GIANT # Giant mutex is adaptive. device apic # I/O APIC (do I need this?) # Bus support. device eisa device pci # Floppy drives device fdc # ATA and ATAPI devices device ata #device atadisk # ATA disk drives #device ataraid # ATA RAID drives #device atapicd # ATAPI CDROM drives #device atapifd # ATAPI floppy drives #device atapist # ATAPI tape drives #options ATA_STATIC_ID # Static device numbering #SCSI on ATAPI device atapicam # SCSI Controllers #device ahb # EISA AHA1742 family device ahc # AHA2940 and onboard AIC7xxx devices #device ahd # AHA39320/29320 and onboard AIC79xx devices #device amd # AMD 53C974 (Tekram DC-390(T)) #device isp # Qlogic family #device ispfw # Firmware for QLogic HBAs- normally a module #device mpt # LSI-Logic MPT-Fusion #device ncr # NCR/Symbios Logic #device sym # NCR/Symbios Logic (newer chipsets + those of `ncr') #device trm # Tekram DC395U/UW/F DC315U adapters #device adv # Advansys SCSI adapters #device adw # Advansys wide SCSI adapters #device aha # Adaptec 154x SCSI adapters #device aic # Adaptec 15[012]x SCSI adapters, AIC-6[23]60. #device bt # Buslogic/Mylex MultiMaster SCSI adapters #device ncv # NCR 53C500 #device nsp # Workbit Ninja SCSI-3 #device stg # TMC 18C30/18C50 # SCSI peripherals device scbus # SCSI bus (required for SCSI) device ch # SCSI media changers device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass # Passthrough device (direct SCSI access) device ses # SCSI Environmental Services (and SAF-TE) # RAID controllers interfaced to the SCSI subsystem #device amr # AMI MegaRAID #device arcmsr # Areca SATA II RAID #device asr # DPT SmartRAID V, VI and Adaptec SCSI RAID #device ciss # Compaq Smart RAID 5* #device dpt # DPT Smartcache III, IV - See NOTES for options #device hptmv # Highpoint RocketRAID 182x #device iir # Intel Integrated RAID #device ips # IBM (Adaptec) ServeRAID #device mly # Mylex AcceleRAID/eXtremeRAID #device twa # 3ware 9000 series PATA/SATA RAID # RAID controllers #device aac # Adaptec FSA RAID #device aacp # SCSI passthrough for aac (requires CAM) #device ida # Compaq Smart RAID #device mlx # Mylex DAC960 family #device pst # Promise Supertrak SX6000 #device twe # 3ware ATA RAID # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device vga # VGA video card driver device splash # Splash screen and screen saver support # syscons is the default console driver, resembling an SCO console device sc # Enable this for the pcvt (VT220 compatible) console driver #device vt #options XSERVER # support for X server on a vt console #options FAT_CURSOR # start with block cursor device agp # support several AGP chipsets # Power management support (see NOTES for more options) #device apm # Add suspend/resume support for the i8254. device pmtimer # PCCARD (PCMCIA) support # PCMCIA and cardbus bridge support device cbb # cardbus (yenta) bridge #device pcic # ExCA ISA and PCI bridges device pccard # PC Card (16-bit) bus device cardbus # CardBus (32-bit) bus # Serial (COM) ports device sio # 8250, 16[45]50 based serial ports # Parallel port device ppc device ppbus # Parallel port bus (required) device lpt # Printer device plip # TCP/IP over parallel device ppi # Parallel port interface device #device vpo # Requires scbus and da # If you've got a "dumb" serial or parallel PCI card that is # supported by the puc(4) glue driver, uncomment the following # line to enable it (connects to the sio and/or ppc drivers): #device puc # PCI Ethernet NICs. #device de # DEC/Intel DC21x4x (``Tulip'') #device em # Intel PRO/1000 adapter Gigabit Ethernet Card #device ixgb # Intel PRO/10GbE Ethernet Card #device txp # 3Com 3cR990 (``Typhoon'') #device vx # 3Com 3c590, 3c595 (``Vortex'') # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support #device bfe # Broadcom BCM440x 10/100 Ethernet #device bge # Broadcom BCM570xx Gigabit Ethernet #device dc # DEC/Intel 21143 and various workalikes #device fxp # Intel EtherExpress PRO/100B (82557, 82558) #device lge # Level 1 LXT1001 gigabit Ethernet #device nge # NatSemi DP83820 gigabit Ethernet #device nve # nVidia nForce MCP on-board Ethernet Networking #device pcn # AMD Am79C97x PCI 10/100(precedence over 'lnc') #device re # RealTek 8139C+/8169/8169S/8110S device rl # RealTek 8129/8139 #device sf # Adaptec AIC-6915 (``Starfire'') #device sis # Silicon Integrated Systems SiS 900/SiS 7016 #device sk # SysKonnect SK-984x & SK-982x gigabit Ethernet #device ste # Sundance ST201 (D-Link DFE-550TX) #device ti # Alteon Networks Tigon I/II gigabit Ethernet #device tl # Texas Instruments ThunderLAN #device tx # SMC EtherPower II (83c170 ``EPIC'') #device vge # VIA VT612x gigabit Ethernet #device vr # VIA Rhine, Rhine II #device wb # Winbond W89C840F #device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') # ISA Ethernet NICs. pccard NICs included. #device cs # Crystal Semiconductor CS89x0 NIC # 'device ed' requires 'device miibus' #device ed # NE[12]000, SMC Ultra, 3c503, DS8390 cards #device ex # Intel EtherExpress Pro/10 and Pro/10+ #device ep # Etherlink III based cards #device fe # Fujitsu MB8696x based cards #device ie # EtherExpress 8/16, 3C507, StarLAN 10 etc. #device lnc # NE2100, NE32-VL Lance Ethernet cards #device sn # SMC's 9000 series of Ethernet chips #device xe # Xircom pccard Ethernet # ISA devices that use the old ISA shims #device le # Wireless NIC cards #device wlan # 802.11 support #device an # Aironet 4500/4800 802.11 wireless NICs. #device awi # BayStack 660 and others #device ral # Ralink Technology RT2500 wireless NICs. #device wi # WaveLAN/Intersil/Symbol 802.11 wireless NICs. #device wl # Older non 802.11 Wavelan wireless NIC. # Pseudo devices. device loop # Network loopback device random # Entropy device device ether # Ethernet support device sl # Kernel SLIP device ppp # Kernel PPP device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" device gif # IPv6 and IPv4 tunneling device faith # IPv6-to-IPv4 relaying (translation) # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! # Note that 'bpf' is required for DHCP. device bpf # Berkeley packet filter # USB support device uhci # UHCI PCI->USB interface device ohci # OHCI PCI->USB interface device ehci # EHCI PCI->USB interface (USB 2.0) device usb # USB Bus (required) #device udbp # USB Double Bulk Pipe devices device ugen # Generic device uhid # "Human Interface Devices" device ukbd # Keyboard device ulpt # Printer device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse #device ural # Ralink Technology RT2500USB wireless NICs device urio # Diamond Rio 500 MP3 player device uscanner # Scanners # USB Ethernet, requires miibus #device aue # ADMtek USB Ethernet #device axe # ASIX Electronics USB Ethernet #device cdce # Generic USB over Ethernet #device cue # CATC USB Ethernet #device kue # Kawasaki LSI USB Ethernet #device rue # RealTek RTL8150 USB Ethernet # FireWire support #device firewire # FireWire bus code #device sbp # SCSI over FireWire (Requires scbus and da) #device fwe # Ethernet over FireWire (non-standard!) #Sound support #device pcm #PnP Sound card support (old) device sound --------------030901050703070709090303-- From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 6 06:58:08 2006 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 0A6D216B73B; Tue, 6 Jun 2006 06:48:13 +0000 (UTC) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9576B43D45; Tue, 6 Jun 2006 06:48:12 +0000 (GMT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.13.4.20060308/8.13.4) with ESMTP id k566mB88046045; Mon, 5 Jun 2006 23:48:11 -0700 (PDT) Received: (from dillon@localhost) by apollo.backplane.com (8.13.4.20060308/8.13.4/Submit) id k566m0df046035; Mon, 5 Jun 2006 23:48:00 -0700 (PDT) Date: Mon, 5 Jun 2006 23:48:00 -0700 (PDT) From: Matthew Dillon Message-Id: <200606060648.k566m0df046035@apollo.backplane.com> To: Alexander Leidinger References: <3bbf2fe10605311156p7e629283r34d22b368877582d@mail.gmail.com> <447DFA0C.20207@FreeBSD.org> <3bbf2fe10605311329h7adc1722j9088253515e0265b@mail.gmail.com> <20060601084052.D32549@delplex.bde.org> <3bbf2fe10605311632w58c2949buc072e58ac103d7d@mail.gmail.com> <20060601093016.ygeptkv80840gkww@netchild.homeip.net> Cc: Attilio Rao , freebsd-hackers@freebsd.org, Suleiman Souhlal , Bruce Evans , freebsd-arch@freebsd.org Subject: Re: [patch] Adding optimized kernel copying support - Part III 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, 06 Jun 2006 06:58:08 -0000 :AFAIR the DFly FPU rework allows to use FPU/XMM instructions in their :kernel without the need to do some manual state preserving (it's done :... : :Bye, :Alexander. That actually isn't quite how it works. If the userland had active FP state then the kernel still has to save it before it can use the FP registers. The kernel does not have to restore it, however (that is, it can just let userland take a fault to restore its FP state). However, the kernel still has to mess around with CR0_TS when pushing and popping an FP context / save area. The FP state reworking in DragonFly had the following effects: * We now have a save area pointer instead of a fixed, static save area. This allows FP state to be 'stacked' without having to play weird games with a static save area. * The standard FP restoration fault is no longer limited to userland. The kernel can push its own state, switch away to another thread, switch back, and take a fault to restore it, independant of the user FP state. -- It would be possible to simplify matters and actually implement what you say... the ability to use FP registers without any manual state preserving. That is, to be able to treat the FP registers just like normal registers. It would require saving and restoring a great deal more state in the interrupt/exception frame push code and the thread switch code, though. It could be conditionalized based CR0_TS or it could just be done unconditionally. I'm not sure it would yield any improvement in performance, though. There is also the problem of the storage required to manage multiple save areas. It's something like, what, 512 bytes on the stack? Because of that DragonFly still implements an FPU interlock so the kernel doesn't stack more then one additional save area due to FAST interrupts, stacked exceptions, etc. -Matt From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 6 07:23:04 2006 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 A810216B6E7 for ; Tue, 6 Jun 2006 07:18:36 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from wx-out-0102.google.com (wx-out-0102.google.com [66.249.82.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 025B843D55 for ; Tue, 6 Jun 2006 07:18:34 +0000 (GMT) (envelope-from asmrookie@gmail.com) Received: by wx-out-0102.google.com with SMTP id i31so880660wxd for ; Tue, 06 Jun 2006 00:18:34 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=nv9DzTiuhbMsYO0/0AMHqhjwL1I9m3cPCNd1YQlt/b1V5OslIB0ALn1sCsLEdtjHB7gCipNJcpJTfSvOBlMS8a5Qb3hIvmI0h5+CpmpE5uVzCTmfr8uD6yMYUX1XQI3SWUqt2vJ1++zPTdLsTH33fCJMeWgmWeAqKP20VOuqv/8= Received: by 10.70.130.14 with SMTP id c14mr7180871wxd; Tue, 06 Jun 2006 00:18:34 -0700 (PDT) Received: by 10.70.37.15 with HTTP; Tue, 6 Jun 2006 00:18:34 -0700 (PDT) Message-ID: <3bbf2fe10606060018k7d9052eck672277079144ca10@mail.gmail.com> Date: Tue, 6 Jun 2006 09:18:34 +0200 From: "Attilio Rao" Sender: asmrookie@gmail.com To: "Matthew Dillon" , "Alexander Leidinger" , "Bruce Evans" , "Suleiman Souhlal" , freebsd-arch@freebsd.org, freebsd-hackers@freebsd.org In-Reply-To: <200606060648.k566m0df046035@apollo.backplane.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <3bbf2fe10605311156p7e629283r34d22b368877582d@mail.gmail.com> <447DFA0C.20207@FreeBSD.org> <3bbf2fe10605311329h7adc1722j9088253515e0265b@mail.gmail.com> <20060601084052.D32549@delplex.bde.org> <3bbf2fe10605311632w58c2949buc072e58ac103d7d@mail.gmail.com> <20060601093016.ygeptkv80840gkww@netchild.homeip.net> <200606060648.k566m0df046035@apollo.backplane.com> X-Google-Sender-Auth: b97437906e0b7dea Cc: Subject: Re: [patch] Adding optimized kernel copying support - Part III 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, 06 Jun 2006 07:23:04 -0000 2006/6/6, Matthew Dillon : > :AFAIR the DFly FPU rework allows to use FPU/XMM instructions in their > :kernel without the need to do some manual state preserving (it's done > :... > : > :Bye, > :Alexander. > > That actually isn't quite how it works. If the userland had active > FP state then the kernel still has to save it before it can use the > FP registers. The kernel does not have to restore it, however (that is, > it can just let userland take a fault to restore its FP state). > However, the kernel still has to mess around with CR0_TS when pushing > and popping an FP context / save area. > > The FP state reworking in DragonFly had the following effects: > > * We now have a save area pointer instead of a fixed, static save area. > This allows FP state to be 'stacked' without having to play weird > games with a static save area. > > * The standard FP restoration fault is no longer limited to userland. > The kernel can push its own state, switch away to another thread, > switch back, and take a fault to restore it, independant of the > user FP state. > > -- > > It would be possible to simplify matters and actually implement what > you say... the ability to use FP registers without any manual state > preserving. That is, to be able to treat the FP registers just like > normal registers. It would require saving and restoring a great deal > more state in the interrupt/exception frame push code and the > thread switch code, though. It could be conditionalized based CR0_TS > or it could just be done unconditionally. I'm not sure it would yield > any improvement in performance, though. I tend to agree with you beacause it would be too much work/storage savings which will loose all the improvements gave to xmm registers. The point about using xmm registers is just performance improvements. I think that having an interlock into the kernel (and so just one kernel saving-state) is the better thing for performances, even if it doesn't provide a real unconditional usage. Attilio PS: Please consider too that xmm registers seem increasing performances just if used with aligned with aligned datas (movaps, movdqa), so not in the general case. MMXs, instead, seem giving very poor improvement, in particular on evolved architectures (>= P3) -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 6 08:25:20 2006 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 2671B16B750 for ; Tue, 6 Jun 2006 08:15:15 +0000 (UTC) (envelope-from soralx@cydem.org) Received: from pd3mo2so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id C06D043D5D for ; Tue, 6 Jun 2006 08:15:14 +0000 (GMT) (envelope-from soralx@cydem.org) Received: from pd5mr5so.prod.shaw.ca (pd5mr5so-qfe3.prod.shaw.ca [10.0.141.181]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J0F00J1AIXE7M60@l-daemon> for freebsd-hackers@freebsd.org; Tue, 06 Jun 2006 02:15:14 -0600 (MDT) Received: from pn2ml7so.prod.shaw.ca ([10.0.121.151]) by pd5mr5so.prod.shaw.ca (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J0F000AHIXEWNG0@pd5mr5so.prod.shaw.ca> for freebsd-hackers@freebsd.org; Tue, 06 Jun 2006 02:15:14 -0600 (MDT) Received: from soralx.cydem.org ([24.87.27.3]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J0F00K11IXDS4B1@l-daemon> for freebsd-hackers@freebsd.org; Tue, 06 Jun 2006 02:15:14 -0600 (MDT) Date: Tue, 06 Jun 2006 01:15:13 -0700 From: soralx@cydem.org In-reply-to: <4cbd01f40606042042m4f8633h73d737b676d820cd@mail.gmail.com> To: freebsd-hackers@freebsd.org Message-id: <200606060115.13285.soralx@cydem.org> MIME-version: 1.0 Content-type: text/plain; charset=iso-2022-jp Content-transfer-encoding: 7bit Content-disposition: inline References: <200606051022.35686.root@solink.ru> <4cbd01f40606042042m4f8633h73d737b676d820cd@mail.gmail.com> User-Agent: KMail/1.9.1 Subject: Re: D-Link DSL210 USB in FreeBSD 6.x ? 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, 06 Jun 2006 08:25:25 -0000 > Is sat a wireless network USB adapter? If so, then there is no way to run USB > Wi_Fi in FreeBSD nor in Linux, only PCI or PCMCIA adapters are supported for > now as far as I know. Even with Windows native drivers. But no USB... I used NetGear 'WG111' USB successfully (without encryption, though). [SorAlx] ridin' VN1500-B2 From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 6 08:43:18 2006 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 1B6B116A6FB for ; Tue, 6 Jun 2006 08:25:38 +0000 (UTC) (envelope-from simon@comsys.ntu-kpi.kiev.ua) Received: from comsys.ntu-kpi.kiev.ua (comsys.ntu-kpi.kiev.ua [195.245.194.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id 016E743D49 for ; Tue, 6 Jun 2006 08:25:32 +0000 (GMT) (envelope-from simon@comsys.ntu-kpi.kiev.ua) Received: from pm513-1.comsys.ntu-kpi.kiev.ua (pm513-1.comsys.ntu-kpi.kiev.ua [10.18.52.101]) (authenticated bits=0) by comsys.ntu-kpi.kiev.ua (8.13.6/8.13.6) with ESMTP id k568QYvk058152 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 6 Jun 2006 11:26:34 +0300 (EEST) Received: by pm513-1.comsys.ntu-kpi.kiev.ua (Postfix, from userid 1001) id 0EC165C024; Tue, 6 Jun 2006 11:25:30 +0300 (EEST) Date: Tue, 6 Jun 2006 11:25:29 +0300 From: Andrey Simonenko To: Konstantin Belousov Message-ID: <20060606082529.GA767@pm513-1.comsys.ntu-kpi.kiev.ua> References: <20060605110136.GA1348@pm513-1.comsys.ntu-kpi.kiev.ua> <20060605173045.GA45380@deviant.kiev.zoral.com.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060605173045.GA45380@deviant.kiev.zoral.com.ua> User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-0.9 required=5.0 tests=ALL_TRUSTED,AWL autolearn=unavailable version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on comsys.ntu-kpi.kiev.ua X-Virus-Scanned: ClamAV 0.82/1456/Thu May 11 08:57:31 2006 on comsys.ntu-kpi.kiev.ua X-Virus-Status: Clean Cc: freebsd-hackers@freebsd.org Subject: Re: Question about synchronization (nfssvc, vfs_busy) 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, 06 Jun 2006 08:43:20 -0000 On Mon, Jun 05, 2006 at 08:30:45PM +0300, Konstantin Belousov wrote: > On Mon, Jun 05, 2006 at 02:01:36PM +0300, Andrey Simonenko wrote: > > 2. > > > > If vfs_busy() is called without LK_NOWAIT flag, then it can sleep > > if a filesystem is being unmounted. At some point unmount() will > If vfs_busy() is called without LK_NOWAIT and fs is being unmounted, > then vfs_busy returns with ENOENT error, isn't it ? > Yes, it returns ENOENT, but before this event vfs_busy() sets MNTK_MWAIT flag and sleeps on mount point address. When vfs_mount_destroy() sees MNTK_MWAIT, it wakes up a thread which sleeps in vfs_busy(). Since vfs_busy() and vfs_mount_destroy() are active only if MNT_MTX(mp) is acquired, vfs_mount_destroy() continues own execution, deallocating mount point, so mutex address passed to msleep() in vfs_busy() is not valid any more. > > reach vfs_mount_destroy() and since there is one ref from vfs_busy() > > it will sleep 3 seconds and will notice MNTK_MWAIT flag and wake up > > a process, which is sleeping in vfs_busy(). How woken up process > > can work with mount structure in vfs_busy() after wakeup(), which > > could be already deallocated in vfs_mount_destroy()? > vfs_busy() internally increases the ref count for mount point, so, it cannot > be taken from under it (look for MNT_REF/MNT_REL). Simultameous entrance > into the code in question in vfs_busy/vfs_mount_destroy is protected > by mnt_mtx (MNT_ILOCK/MNT_IUNLOCK). > > A reference counter is increased, but in vfs_mount_destroy() in first for() (mnt_ref != 0) is checked only 3 seconds, then debug message is outputted. Let me ask in other words, how vfs_ref() guarantees that unmount() in vfs_mount_destroy() will not deallocate a mount point (see checks in first for() loop, also assume that mnt_holdcnt, mnt_writeopcount and mnt_secondary_writes are equal to zero)? I also wanted to ask similar question about vfs_getvfs(), but as I understand in CURRENT it was corrected. From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 6 09:07:15 2006 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 AD56716BFF3 for ; Tue, 6 Jun 2006 09:03:14 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96D9B43D69 for ; Tue, 6 Jun 2006 09:03:09 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1FnXSs-0005qX-3f; Tue, 06 Jun 2006 12:03:06 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: Scott Long In-reply-to: <447EB9C0.9010402@samsco.org> References: <447EB9C0.9010402@samsco.org> Comments: In-reply-to Scott Long message dated "Thu, 01 Jun 2006 03:56:16 -0600." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 06 Jun 2006 12:03:06 +0300 From: Danny Braniss Message-ID: Cc: freebsd-hackers@freebsd.org Subject: iSCSI/sosend(...), was iSCSI/sendto(...) 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, 06 Jun 2006 09:07:22 -0000 > Danny Braniss wrote: > > > Hi, > > on a fairly new 6.1-stable, and probably before, once in a > > blue moon, sendto return error 64 (EHOSTDOWN?). but the packet seems to have > > been received by the target, since i get a response, and further more, > > everything keeps on working. > > > > what is error 64? > > > > danny > > > > > > EHOSTDOWN comes from the ARP layer of the IP stack, and would be > consistent with the host either getting no arp response or rejected > responses from the target. It would be useful to run tcpdump+ethereal > on your connection to see what is really going on. > > Scott > If someone can shed some light, in ftp://ftp.cs.huji.ac.il/users/danny/freebsd/snif8 around No. 28051, there is the ARP request, which seems a bit odd. danny From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 6 09:25:57 2006 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 ED24C16B803 for ; Tue, 6 Jun 2006 09:22:26 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from fw.zoral.com.ua (ll-227.216.82.212.sovam.net.ua [212.82.216.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id D53C843D45 for ; Tue, 6 Jun 2006 09:22:25 +0000 (GMT) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by fw.zoral.com.ua (8.13.4/8.13.4) with ESMTP id k569N3eG005822 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 6 Jun 2006 12:23:03 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6) with ESMTP id k569MD2R071737; Tue, 6 Jun 2006 12:22:13 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6/Submit) id k569MCdq071736; Tue, 6 Jun 2006 12:22:12 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 6 Jun 2006 12:22:12 +0300 From: Konstantin Belousov To: Andrey Simonenko Message-ID: <20060606092212.GB45380@deviant.kiev.zoral.com.ua> References: <20060605110136.GA1348@pm513-1.comsys.ntu-kpi.kiev.ua> <20060605173045.GA45380@deviant.kiev.zoral.com.ua> <20060606082529.GA767@pm513-1.comsys.ntu-kpi.kiev.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Bn2rw/3z4jIqBvZU" Content-Disposition: inline In-Reply-To: <20060606082529.GA767@pm513-1.comsys.ntu-kpi.kiev.ua> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: ClamAV version 0.88.2, clamav-milter version 0.88.2 on fw.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on fw.zoral.com.ua Cc: freebsd-hackers@freebsd.org Subject: Re: Question about synchronization (nfssvc, vfs_busy) 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, 06 Jun 2006 09:25:59 -0000 --Bn2rw/3z4jIqBvZU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jun 06, 2006 at 11:25:29AM +0300, Andrey Simonenko wrote: > On Mon, Jun 05, 2006 at 08:30:45PM +0300, Konstantin Belousov wrote: > > On Mon, Jun 05, 2006 at 02:01:36PM +0300, Andrey Simonenko wrote: > > > 2. > > >=20 > > > If vfs_busy() is called without LK_NOWAIT flag, then it can sleep > > > if a filesystem is being unmounted. At some point unmount() will > > If vfs_busy() is called without LK_NOWAIT and fs is being unmounted, > > then vfs_busy returns with ENOENT error, isn't it ? > >=20 >=20 > Yes, it returns ENOENT, but before this event vfs_busy() sets MNTK_MWAIT > flag and sleeps on mount point address. When vfs_mount_destroy() sees > MNTK_MWAIT, it wakes up a thread which sleeps in vfs_busy(). Since > vfs_busy() and vfs_mount_destroy() are active only if MNT_MTX(mp) is > acquired, vfs_mount_destroy() continues own execution, deallocating > mount point, so mutex address passed to msleep() in vfs_busy() is not > valid any more. Are you concerned about invocation of vfs_mount_destroy() at line 1224 of vfs_mount.c, in dounmount ?=20 Do you experience problems (panics, etc) caused by this issue ? It seems that this scenario is impossible for some reasons that are external to vfs_busy, because dounmount() aquires exclusive lock on the vnode covered by mount point. As far as I see, all invocations of vfs_busy() without LK_NOWAIT flag are done while holding at least shared lock on that vnode. See, for instance, fchdir() from vfs_syscalls.c. --Bn2rw/3z4jIqBvZU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEhUlDC3+MBN1Mb4gRAuGbAKCOc65xHM6O8ae7ovh7r+moQJI4cwCgglMg cwK4VUKBGqbIZiabcx2WHVg= =aGaX -----END PGP SIGNATURE----- --Bn2rw/3z4jIqBvZU-- From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 6 10:03:56 2006 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 7AD2A16A4F0 for ; Tue, 6 Jun 2006 10:03:56 +0000 (UTC) (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 CE9A443D48 for ; Tue, 6 Jun 2006 10:03:55 +0000 (GMT) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 5E45451307; Tue, 6 Jun 2006 12:03:54 +0200 (CEST) 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 95B8850EA7; Tue, 6 Jun 2006 12:03:49 +0200 (CEST) Date: Tue, 6 Jun 2006 12:01:34 +0200 From: Pawel Jakub Dawidek To: sara lidgey Message-ID: <20060606100134.GE74562@garage.freebsd.pl> References: <20060529214404.14374.qmail@web35710.mail.mud.yahoo.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ey/N+yb7u/X9mFhi" Content-Disposition: inline In-Reply-To: <20060529214404.14374.qmail@web35710.mail.mud.yahoo.com> 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 Subject: Re: freebsd 5.3, gmirror raid 1, 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: Tue, 06 Jun 2006 10:04:02 -0000 --ey/N+yb7u/X9mFhi Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, May 29, 2006 at 05:44:04PM -0400, sara lidgey wrote: +> Hi All, +> =20 +> I've been running a server using FreeBSD 5.3 and gmirror to mirror two = identical IDE hard drives. Its been running great for over a year. But re= cently everything went down and when I reboot and put a monitor on it I get= the following errors on screen: +> =20 +> GEOM_MIRROR: Device gm0: provider ad1 disconnected +> GEOM_MIRROR: Device gm0: provider mirror/gm0 destroyed +> GEOM_MIRROR: Device gm0: rebuilding provider ad0 stopped +> =20 +> Fatal trap 12: page fault while in kernel mode... (this is followed by= details about the fault) +> =20 +> These errors are preceded by other related error information that flys = by on the screen and I have no way of seeing them again. +> =20 +> Does anyone now what steps I should take to figure what is going on and= try to recover data or get the machine to boot? Can you provide more info? There should be more interesting informations before those you pasted. There was a lot of fixes to gmirror in 6.1, so you may consider an upgrade. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --ey/N+yb7u/X9mFhi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFEhVJ+ForvXbEpPzQRAiW1AKDkaC723Upv0tCPmcU6uJ2S3t2JZACfaqQU 34+Wr4O4Bp8rPzDJdqBYkxs= =TG7d -----END PGP SIGNATURE----- --ey/N+yb7u/X9mFhi-- From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 6 09:01:16 2006 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 77C3316AA1A for ; Tue, 6 Jun 2006 08:40:38 +0000 (UTC) (envelope-from killa@ebash.it) Received: from mx1.caravan.ru (mx1.caravan.ru [217.23.130.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id E287943D49 for ; Tue, 6 Jun 2006 08:40:37 +0000 (GMT) (envelope-from killa@ebash.it) Received: from [217.23.131.8] (helo=[10.0.0.70]) by mx1.caravan.ru with esmtp (Exim 4.60) (envelope-from ) id 1FnX76-000KNL-4T for freebsd-hackers@freebsd.org; Tue, 06 Jun 2006 12:40:36 +0400 Message-ID: <4485416C.5080309@ebash.it> Date: Tue, 06 Jun 2006 12:48:44 +0400 From: "Oleg D." User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050517) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Tue, 06 Jun 2006 11:55:26 +0000 Subject: problem with SCSI 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, 06 Jun 2006 09:01:27 -0000 Sorry for some offtopic. Experiencing some troubles with SCSI disks on FBSD 4.8 and looking for advice/solution how to fix/diagnose-more... What (maybe not) causes troubles: okey# make clean ===> Cleaning for m4-1.4_1 rm: /usr/ports/devel/m4/work: Directory not empty *** Error code 1 Stop in /usr/ports/devel/m4. *** Error code 1 Stop in /usr/ports/devel/m4. okey# Message from syslogd@okey at Tue Jun 6 10:50:12 2006 ... okey /kernel: <<<<<<<<<<<<<<<< Dump Card State Ends >>>>>>>>>>>>>>>>>> and machine went stuck... That error report happenned twice after what machine was rebooted (just `reset`ing). After reboot with turning off power and so on: `camcontrol' tells that all is OK, but I think it's not... Was using `iostat' to have some additional traces, but it showed that's all ok even. Also used `dd' to make some huge loads on disks, but it even told me nothing, except "OK". System: Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.8-RELEASE-p22 #3: Thu May 27 16:53:05 MSD 2004 root@okey.caravan.ru:/usr/obj/usr/src/sys/OKEY Timecounter "i8254" frequency 1193182 Hz CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2791.01-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 Features=0xbfebfbff Hyperthreading: 2 logical CPUs real memory = 2147418112 (2097088K bytes) avail memory = 2087776256 (2038844K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 Programming 24 pins in IOAPIC #1 Programming 24 pins in IOAPIC #2 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00050014, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00050014, at 0xfee00000 cpu2 (AP): apic id: 6, version: 0x00050014, at 0xfee00000 cpu3 (AP): apic id: 7, version: 0x00050014, at 0xfee00000 io0 (APIC): apic id: 8, version: 0x00178020, at 0xfec00000 io1 (APIC): apic id: 9, version: 0x00178020, at 0xfec81000 io2 (APIC): apic id: 10, version: 0x00178020, at 0xfec81400 Preloaded elf kernel "kernel" at 0xc03ce000. ccd0-1: Concatenated disk drivers Pentium Pro MTRR support enabled Using $PIR table, 19 entries at 0xc00f3630 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard IOAPIC #0 intpin 17 -> irq 2 pci0: on pcib0 pci0: (vendor=0x8086, dev=0x2541) at 0.1 pcib1: at device 3.0 on pci0 pci2: on pcib1 pci2: (vendor=0x8086, dev=0x1461) at 28.0 pcib2: at device 29.0 on pci2 IOAPIC #2 intpin 2 -> irq 16 IOAPIC #2 intpin 1 -> irq 17 pci4: on pcib2 ahd0: port 0x4000-0x40ff,0x3800-0x38ff mem 0xfe9e0000-0xfe9e1fff irq 16 at device 7.0 on pci4 aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs ahd1: port 0x3400-0x34ff,0x3000-0x30ff mem 0xfe9f0000-0xfe9f1fff irq 17 at device 7.1 on pci4 aic7902: Ultra320 Wide Channel B, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs pci2: (vendor=0x8086, dev=0x1461) at 30.0 pcib3: at device 31.0 on pci2 IOAPIC #1 intpin 6 -> irq 18 IOAPIC #1 intpin 7 -> irq 19 pci3: on pcib3 em0: port 0x2040-0x207f mem 0xfe6c0000-0xfe6dffff irq 18 at device 7.0 on pci3 em0: Speed:100 Mbps Duplex:Half em1: port 0x2000-0x203f mem 0xfe6e0000-0xfe6fffff irq 19 at device 7.1 on pci3 em1: Speed:N/A Duplex:N/A pci0: (vendor=0x8086, dev=0x2546) at 3.1 pcib4: at device 30.0 on pci0 pci1: on pcib4 pci1: at 12.0 irq 2 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x3a0-0x3af,0-0x3,0-0x7,0-0x3,0-0x7 irq 0 at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: (vendor=0x8086, dev=0x2483) at 31.3 irq 2 orm0: