From owner-freebsd-hackers@FreeBSD.ORG Sun May 21 01:10:37 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 D9AA816A425 for ; Sun, 21 May 2006 01:10:37 +0000 (UTC) (envelope-from ederbs.hackers@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6AAE843D46 for ; Sun, 21 May 2006 01:10:37 +0000 (GMT) (envelope-from ederbs.hackers@gmail.com) Received: by nz-out-0102.google.com with SMTP id 13so964300nzn for ; Sat, 20 May 2006 18:10:36 -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=Zg/EhTx9HnSnEU93DGSfRTskIJQ9l41TTDvCY6gDV2TOyw6T33gH1CZC6ORRYEm3M2Y+qWVJbNvg1kzyUG0LbILp/AOboyjZndOau3miggjYm4St+yuc46+oiCxc8DRL74+IHaFdIABpLMQZjZaBVLOP1YMYfkOymbjsZmS7RSI= Received: by 10.64.180.14 with SMTP id c14mr2212926qbf; Sat, 20 May 2006 18:10:36 -0700 (PDT) Received: by 10.64.178.4 with HTTP; Sat, 20 May 2006 18:10:36 -0700 (PDT) Message-ID: <2699850605201810g377964edlbffd6928c9fbcdef@mail.gmail.com> Date: Sat, 20 May 2006 22:10:36 -0300 From: Eder To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Source Screensaver 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, 21 May 2006 01:10:42 -0000 Hi all, Doubts ! I created to screensaver for console. The code would like to know as sending, to be enclosed in src of the FreeBSD. Thanks, Eder. From owner-freebsd-hackers@FreeBSD.ORG Sun May 21 02:42:39 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 1863816A422 for ; Sun, 21 May 2006 02:42:39 +0000 (UTC) (envelope-from fierykylin@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 8512A43D45 for ; Sun, 21 May 2006 02:42:38 +0000 (GMT) (envelope-from fierykylin@gmail.com) Received: by wx-out-0102.google.com with SMTP id i30so430820wxd for ; Sat, 20 May 2006 19:42:37 -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=ZWJ2q1QgxxBqFEEP77a8E1ZA9X6C3mzccuWfgPoVqSS8HYeYw3mK7utb9x8jIjs1/v7I5fWYpl4DMEOX5KX0Rlwedmzy5ixpaqe2QnbjLrMPvMTaLpyDWlDkAM+NOg0cq45p1sHED6/NhjmhDhinUEhjeo526e5u4sBlhUZv5s0= Received: by 10.70.17.10 with SMTP id 10mr3786303wxq; Sat, 20 May 2006 19:42:37 -0700 (PDT) Received: by 10.70.43.11 with HTTP; Sat, 20 May 2006 19:42:37 -0700 (PDT) Message-ID: <87ab37ab0605201942o3e27c46w2ac57261e02a2890@mail.gmail.com> Date: Sun, 21 May 2006 10:42:37 +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: e4d6f3251da06aa5 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, 21 May 2006 02:42:39 -0000 still a question about newbus 's BUS interface : usage of DEVICE_IDENTIFY AND BUS_ADD_CHILD I know these bus interface func r called accessor functions ,that call the appropriate function by checking the parameter.just like the polymorphism technic in OOP . that's really a magic :) my first QUESTION is what if the calling device do not realize the corresponding interface ? taking bus_add_child interface as example. only a few device-drivers have implement it ,but more r called for it .what will happen when BUS_ADD_CHILD(device_t bus, int order, const char *name, int unit) 's bus do not implement it ? my second is :a driver's DEVICE_IDENTIFY always call its device 's parent's BUS_ADD_CHILD ,what is the semantic of them:) thank u the drivers who have registered the bus_add_child (not too many) Acpi.c (dev\acpica): DEVMETHOD(bus_add_child, acpi_add_child), Atkbdc_isa.c (isa): DEVMETHOD(bus_add_child, atkbdc_add_child), Canbus.c (pc98\pc98): DEVMETHOD(bus_add_child, canbus_add_child), Firewire.c (dev\firewire): DEVMETHOD(bus_add_child, firewire_add_child), Fwohci_pci.c (dev\firewire): DEVMETHOD(bus_add_child, fwohci_pci_add_child), Iicbus.c (dev\iicbus): DEVMETHOD(bus_add_child, iicbus_add_child), Isa_common.c (isa): DEVMETHOD(bus_add_child, isa_add_child), Legacy.c (amd64\amd64): DEVMETHOD(bus_add_child, legacy_add_child), Legacy.c (i386\i386): DEVMETHOD(bus_add_child, legacy_add_child), Nexus.c (amd64\amd64): DEVMETHOD(bus_add_child, nexus_add_child), Nexus.c (i386\i386): DEVMETHOD(bus_add_child, nexus_add_child), Nexus.c (ia64\ia64): DEVMETHOD(bus_add_child, nexus_add_child), Ppbconf.c (dev\ppbus): DEVMETHOD(bus_add_child, ppbus_add_child), Smbus.c (dev\smbus): DEVMETHOD(bus_add_child, smbus_add_child), 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$B!$(Bso 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 > > > > > > > > > -- > > we who r about to die,salute u! > > > > > -- we who r about to die,salute u! From owner-freebsd-hackers@FreeBSD.ORG Sun May 21 03:07:30 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 AC56016A421 for ; Sun, 21 May 2006 03:07:30 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id D574943D5A for ; Sun, 21 May 2006 03:07:28 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (a068taw3zoaq075b@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.4/8.13.3) with ESMTP id k4L37PTQ055901; Sat, 20 May 2006 20:07:25 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.4/8.13.3/Submit) id k4L37PIB055900; Sat, 20 May 2006 20:07:25 -0700 (PDT) (envelope-from jmg) Date: Sat, 20 May 2006 20:07:25 -0700 From: John-Mark Gurney To: william wallace Message-ID: <20060521030725.GD770@funkthat.com> Mail-Followup-To: william wallace , Warner Losh , "freebsd-hackers@freebsd.org" References: <87ab37ab0605192015h363ef74aw23dcc2d97721dea9@mail.gmail.com> <20060519.232002.71106210.imp@bsdimp.com> <87ab37ab0605192239n73b7fcdbtbdd5dbd3f1099fc3@mail.gmail.com> <20060520.013546.104050983.imp@bsdimp.com> <87ab37ab0605201942o3e27c46w2ac57261e02a2890@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87ab37ab0605201942o3e27c46w2ac57261e02a2890@mail.gmail.com> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: "freebsd-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 Reply-To: John-Mark Gurney List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 May 2006 03:07:30 -0000 william wallace wrote this message on Sun, May 21, 2006 at 10:42 +0800: > still a question about newbus 's BUS interface : > usage of DEVICE_IDENTIFY AND BUS_ADD_CHILD > I know these bus interface func r called accessor functions ,that call > the appropriate function by checking the parameter.just like the > polymorphism technic in OOP . that's really a magic :) > my first QUESTION is what if the calling device do not realize the > corresponding interface ? taking bus_add_child interface as example. > only a few device-drivers have implement it ,but more r called for it > .what will happen when BUS_ADD_CHILD(device_t bus, int order, const > char *name, int unit) 's bus do not implement it ? If there isn't one implemented, it just falls back to kobj_error_method, which simply returns ENXIO... > my second is :a driver's DEVICE_IDENTIFY always call its device 's > parent's BUS_ADD_CHILD ,what is the semantic of them:) > thank u > > the drivers who have registered the bus_add_child (not too many) > Acpi.c (dev\acpica): DEVMETHOD(bus_add_child, acpi_add_child), > Atkbdc_isa.c (isa): DEVMETHOD(bus_add_child, atkbdc_add_child), > Canbus.c (pc98\pc98): DEVMETHOD(bus_add_child, canbus_add_child), > Firewire.c (dev\firewire): DEVMETHOD(bus_add_child, firewire_add_child), > Fwohci_pci.c (dev\firewire): DEVMETHOD(bus_add_child, > fwohci_pci_add_child), > Iicbus.c (dev\iicbus): DEVMETHOD(bus_add_child, iicbus_add_child), > Isa_common.c (isa): DEVMETHOD(bus_add_child, isa_add_child), > Legacy.c (amd64\amd64): DEVMETHOD(bus_add_child, legacy_add_child), > Legacy.c (i386\i386): DEVMETHOD(bus_add_child, legacy_add_child), > Nexus.c (amd64\amd64): DEVMETHOD(bus_add_child, nexus_add_child), > Nexus.c (i386\i386): DEVMETHOD(bus_add_child, nexus_add_child), > Nexus.c (ia64\ia64): DEVMETHOD(bus_add_child, nexus_add_child), > Ppbconf.c (dev\ppbus): DEVMETHOD(bus_add_child, ppbus_add_child), > Smbus.c (dev\smbus): DEVMETHOD(bus_add_child, smbus_add_child), Look at how it's called: nclaptop,ttyp5,~/FreeBSD/HEAD/src/sys/isa,557$grep BUS_ADD_CHILD * isahint.c: child = BUS_ADD_CHILD(parent, order, name, unit); orm.c: child = BUS_ADD_CHILD(parent, ISA_ORDER_SENSITIVE, "orm", -1); as you can see, you just provide the probe order, the name and unit of the device you're adding... The call to BUS_ADD_CHILD is necessary for busses that use identify methods... this ensures that things like ivars are setup properly by the bus for the device.. > 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?$B!$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). > > > >> 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... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-hackers@FreeBSD.ORG Sun May 21 06:10: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 1939516A434 for ; Sun, 21 May 2006 06:10:13 +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 933F343D46 for ; Sun, 21 May 2006 06:10:12 +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 k4L67TGo039311; Sun, 21 May 2006 00:07:29 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sun, 21 May 2006 00:07:29 -0600 (MDT) Message-Id: <20060521.000729.41671970.imp@bsdimp.com> To: avalonwallace@gmail.com From: Warner Losh In-Reply-To: <87ab37ab0605201942o3e27c46w2ac57261e02a2890@mail.gmail.com> References: <87ab37ab0605192239n73b7fcdbtbdd5dbd3f1099fc3@mail.gmail.com> <20060520.013546.104050983.imp@bsdimp.com> <87ab37ab0605201942o3e27c46w2ac57261e02a2890@mail.gmail.com> X-Mailer: Mew version 3.3 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, 21 May 2006 06:10:13 -0000 > still a question about newbus 's BUS interface : > usage of DEVICE_IDENTIFY AND BUS_ADD_CHILD > I know these bus interface func r called accessor functions ,that call > the appropriate function by checking the parameter.just like the > polymorphism technic in OOP . that's really a magic :) > my first QUESTION is what if the calling device do not realize the > corresponding interface ? taking bus_add_child interface as example. > only a few device-drivers have implement it ,but more r called for it > .what will happen when BUS_ADD_CHILD(device_t bus, int order, const > char *name, int unit) 's bus do not implement it ? The BUS_ADD_CHILD interface is called by the bus. Children drivers don't need to know/care about it. They aren't always needed, however. You'll likely find that only busses that are not self-enumerating have these registered. This is so that when the identiy routines are called to enumerate the children otherwise unknown to the parent bus, the parent bus gets notification of the addition of these new chilren. > my second is :a driver's DEVICE_IDENTIFY always call its device 's > parent's BUS_ADD_CHILD ,what is the semantic of them:) > thank u nope. It may be called once per bus instance per driver, if the bus is not self-identifying. If the bus is self-idntiying, chances are that it will not be called. pci never calls its children drivers' identify routine because it already knows all the children on the bus and doesn't need the leaf drivers to go find instances of themselves. the isa bus driver, on the other hand, does call the identify routine so that pre-plug and play standard device enumeration can happen. Warner > the drivers who have registered the bus_add_child (not too many) > Acpi.c (dev\acpica): DEVMETHOD(bus_add_child, acpi_add_child), > Atkbdc_isa.c (isa): DEVMETHOD(bus_add_child, atkbdc_add_child), > Canbus.c (pc98\pc98): DEVMETHOD(bus_add_child, canbus_add_child), > Firewire.c (dev\firewire): DEVMETHOD(bus_add_child, firewire_add_child), > Fwohci_pci.c (dev\firewire): DEVMETHOD(bus_add_child, fwohci_pci_add_child), > Iicbus.c (dev\iicbus): DEVMETHOD(bus_add_child, iicbus_add_child), > Isa_common.c (isa): DEVMETHOD(bus_add_child, isa_add_child), > Legacy.c (amd64\amd64): DEVMETHOD(bus_add_child, legacy_add_child), > Legacy.c (i386\i386): DEVMETHOD(bus_add_child, legacy_add_child), > Nexus.c (amd64\amd64): DEVMETHOD(bus_add_child, nexus_add_child), > Nexus.c (i386\i386): DEVMETHOD(bus_add_child, nexus_add_child), > Nexus.c (ia64\ia64): DEVMETHOD(bus_add_child, nexus_add_child), > Ppbconf.c (dev\ppbus): DEVMETHOD(bus_add_child, ppbus_add_child), > Smbus.c (dev\smbus): DEVMETHOD(bus_add_child, smbus_add_child), > > > 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$B!$(Bso 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 > > > > > > > > > > > > > -- > > > we who r about to die,salute u! > > > > > > > > > > > -- > we who r about to die,salute u! > > From owner-freebsd-hackers@FreeBSD.ORG Sun May 21 08:08: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 B11E716A470 for ; Sun, 21 May 2006 08:08:03 +0000 (UTC) (envelope-from fierykylin@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 0F6AF43D5E for ; Sun, 21 May 2006 08:08:00 +0000 (GMT) (envelope-from fierykylin@gmail.com) Received: by wx-out-0102.google.com with SMTP id i31so742718wxd for ; Sun, 21 May 2006 01:08:00 -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=oF2n5XK2rd3bCcAq6sgaBj51O1XYSP+l+Wci60hGgaPkcvNoIDhZ+dBwUVV2LEaCKCXjrRgwmHjb9/QCINX5rho+SM+ygdupw/syjFjl42X6pTDAgr1AsQ8ajZFhOzwO16050r1SL0tXgig0lhNFC/EjNWYioOZnnJLe5MvLXGk= Received: by 10.70.47.11 with SMTP id u11mr3950185wxu; Sun, 21 May 2006 01:08:00 -0700 (PDT) Received: by 10.70.43.11 with HTTP; Sun, 21 May 2006 01:08:00 -0700 (PDT) Message-ID: <87ab37ab0605210108w127a235bue281428f52bbc784@mail.gmail.com> Date: Sun, 21 May 2006 16:08:00 +0800 From: "william wallace" Sender: fierykylin@gmail.com To: "Warner Losh" In-Reply-To: <20060521.000729.41671970.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <87ab37ab0605192239n73b7fcdbtbdd5dbd3f1099fc3@mail.gmail.com> <20060520.013546.104050983.imp@bsdimp.com> <87ab37ab0605201942o3e27c46w2ac57261e02a2890@mail.gmail.com> <20060521.000729.41671970.imp@bsdimp.com> X-Google-Sender-Auth: 782d1d438831a1ef 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, 21 May 2006 08:08:03 -0000 On 5/21/06, Warner Losh wrote: > nope. It may be called once per bus instance per driver, if the bus > is not self-identifying. If the bus is self-idntiying, chances are > that it will not be called. pci never calls its children drivers' > identify routine because it already knows all the children on the bus > and doesn't need the leaf drivers to go find instances of themselves. > the isa bus driver, on the other hand, does call the identify routine > so that pre-plug and play standard device enumeration can happen. > > Warner the defination of self-enumerating 1 what does self-enumerating mean ? 2 does that mean the pci way of looping through configuration space ? 3 does that happen in start time and hotplug time ? 4 pci doesn't need the leaf drivers to go find instances of themselves. does that mean that self-enumerating device system use the top down w= ay , and the non- self-enumerating device system use the down -top way 5 i guest pci hot plug need some magic to identify or emulae(loop pci sons ) BTW There r so many hot plug specifications ,SHPC hotplug ,PCIE hotplug and compaq hotplug and so on , in linux ,they use different driver for different pci bridge so i think for us to implement in freeBSD ,just do 1 by 1:) --=20 we who r about to die,salute u! From owner-freebsd-hackers@FreeBSD.ORG Sun May 21 17:28:54 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 E37D216A703 for ; Sun, 21 May 2006 17:28:54 +0000 (UTC) (envelope-from ricardo_bsd@yahoo.com.br) Received: from smtp107.mail.mud.yahoo.com (smtp107.mail.mud.yahoo.com [209.191.85.217]) by mx1.FreeBSD.org (Postfix) with SMTP id 7CF1F43D48 for ; Sun, 21 May 2006 17:28:54 +0000 (GMT) (envelope-from ricardo_bsd@yahoo.com.br) Received: (qmail 3963 invoked from network); 21 May 2006 17:28:53 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com.br; h=Received:Date:To:Subject:From:Organization:Content-Type:MIME-Version:Content-Transfer-Encoding:Message-ID:User-Agent; b=IbtBEJc8ptcoNawRcVhuqAQPGXdVCL8oxZNeFmcy+KmmD5HHU0EQxJ7fXZAAKfVcq6ansVuwWOOOgodLTlxsQJUQIPEcmFZj7vji2C+htnlpsed8eOFvB80p3WhJ50Ns6O3ON9BhOh0AX49Upkxw2fUH5q2ZL7UmaR5IfRQYYTM= ; Received: from unknown (HELO myfreebsd) (ricardo?bsd@201.1.77.188 with login) by smtp107.mail.mud.yahoo.com with SMTP; 21 May 2006 17:28:52 -0000 Date: Sun, 21 May 2006 14:28:29 -0300 To: "freebsd-hackers@freebsd.org" From: "Ricardo A. Reis" Organization: UNIFESP Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1 MIME-Version: 1.0 Content-Transfer-Encoding: Quoted-Printable Message-ID: User-Agent: Opera Mail/9.00 (FreeBSD) Subject: kldfind, updated for version 0.56 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, 21 May 2006 17:28:59 -0000 Hi all, I corrected option implementation, now kldfind accept options in = any = order Changelog: 0.56: Corrected use of getopts, Mupdated man with option and examples (is necessary re-view optio= n = in pod2man for pre-formate string) I've two questions, First about exit codes, when program is executed without options,= = how this must return ? kldunload and kldload not return the same exit codes, [ricardo@myfreebsd:~/kldfind] # kldload usage: kldload [-v] file ... zsh: 48524 exit 1 kldload [ricardo@myfreebsd:~/kldfind] # kldunload usage: kldunload [-fv] -i id ... kldunload [-fv] [-n] name ... zsh: 48539 exit 64 kldunload [ricardo@myfreebsd:~/kldfind] # ./kldfind-v056 usage: kldfind-v056 [-chqsv] ... In kldfind i return 0 The last question is about short description in -v (verbose = output), i use this line for capture from man line after NAME section, man acpi |col -b|awk '/^NAME/,/-/ { gsub(/^.* [-]+ |^.* -- |( = )+|^[ ]+|--$/,"") ; print }'|\ tail -n1 |tr '\n' ' ' 2>&1 This work for severals man, it acceptable ? Thanks for any comments. http://ricardo.epm.br/freebsd/script/kldfind/kldfind-v056 Ricardo A. Reis UNIFESP Unix and Network Admin _______________________________________________________ Abra sua conta no Yahoo! Mail: 1GB de espaço, alertas de e-mail no celular e anti-spam realmente eficaz. http://br.info.mail.yahoo.com/ From owner-freebsd-hackers@FreeBSD.ORG Sun May 21 17:49: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 D57D516A4DB for ; Sun, 21 May 2006 17:49:04 +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 7B99843D45 for ; Sun, 21 May 2006 17:49:04 +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 k4LHm732050514; Sun, 21 May 2006 11:48:07 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sun, 21 May 2006 11:48:07 -0600 (MDT) Message-Id: <20060521.114807.74702188.imp@bsdimp.com> To: avalonwallace@gmail.com From: Warner Losh In-Reply-To: <87ab37ab0605210108w127a235bue281428f52bbc784@mail.gmail.com> References: <87ab37ab0605201942o3e27c46w2ac57261e02a2890@mail.gmail.com> <20060521.000729.41671970.imp@bsdimp.com> <87ab37ab0605210108w127a235bue281428f52bbc784@mail.gmail.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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, 21 May 2006 17:49:12 -0000 From: "william wallace" Subject: Re: misc questions about the device&driver arch Date: Sun, 21 May 2006 16:08:00 +0800 > On 5/21/06, Warner Losh wrote: > > nope. It may be called once per bus instance per driver, if the bus > > is not self-identifying. If the bus is self-idntiying, chances are > > that it will not be called. pci never calls its children drivers' > > identify routine because it already knows all the children on the bus > > and doesn't need the leaf drivers to go find instances of themselves. > > the isa bus driver, on the other hand, does call the identify routine > > so that pre-plug and play standard device enumeration can happen. > > > > Warner > the defination of self-enumerating > 1 > what does self-enumerating mean ? self-enumerating or self-identifying mean the same thing. The bus driver is able to know all of its children. This may be because there's a method to finding them, or the bus may have perfect knowledge of what is there by other means. PCI, CardBus, PC Card, USB, Firewire, and EISA are all examples of self enumerating busses. You can know that you have a device, and the device can provide information about its existance. ISA is the odd-man out. It isn't possible to know when you have an ISA card in a given slot. There are some add-on hacks to be able to discover the devices. ISAPNP is one such hack. Really old Realtek adapters have another. 3Com cards have yet another. It was for these old, pre-plug and play enumeration techniques that the identify routine was invented. > 2 > does that mean the pci way of looping through configuration space ? Yes. > 3 > does that happen in start time and hotplug time ? That happens at attach time. Cardbus right now has a private protocol between the card bus bridge (cbb) and the bus to know when there's a new card in a slot and to enumerate that bus. > 4 > pci doesn't need the leaf drivers to go find instances of themselves. > does that mean that self-enumerating device system use the top down way , > and the non- self-enumerating device system use the down -top way Right. FreeBSD's device enumeration model is top down. > 5 > i guest pci hot plug need some magic to identify or emulae(loop pci sons ) Yes. The hot plug bridge would need to tell its child bus about changes to the bus. This might mean the child bus does a full enumeration, or a partial one. Cardbus does a full enueration, but each card bus slot is its own bus. > BTW > There r so many hot plug specifications ,SHPC hotplug ,PCIE hotplug > and compaq hotplug and so on , in linux ,they use different driver for > different pci > bridge > so i think for us to implement in freeBSD ,just do 1 by 1:) Yes. We'd need todo something similar in FreeBSD. Chances are that the best way to approach this would be to add hotplug functionality directly to the pci bus, and teach cardbus the new protocol. Warner From owner-freebsd-hackers@FreeBSD.ORG Mon May 22 06:29: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 4E1D016A463 for ; Mon, 22 May 2006 06:29:08 +0000 (UTC) (envelope-from fierykylin@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 BDB8B43D5E for ; Mon, 22 May 2006 06:28:59 +0000 (GMT) (envelope-from fierykylin@gmail.com) Received: by wx-out-0102.google.com with SMTP id i30so552687wxd for ; Sun, 21 May 2006 23:28:58 -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=YVmijvfrnEjzuLPnlONLtsnOoVSkNvbL5T73C2FRThsbIxzLPikuUDTESCFUqDKvx38civzwdHZZmZfhdjao23Qv2kDyLs5yn6yKqI0OEWNNStvMT2HoP6ele6K+WRQgNT81RKkV4NBGzA3OCtvuJzH50g4DhXEegDZiuRRwFRk= Received: by 10.70.65.14 with SMTP id n14mr4821935wxa; Sun, 21 May 2006 23:28:58 -0700 (PDT) Received: by 10.70.43.11 with HTTP; Sun, 21 May 2006 23:28:58 -0700 (PDT) Message-ID: <87ab37ab0605212328ue7c70fcu49c5fec8921ae229@mail.gmail.com> Date: Mon, 22 May 2006 14:28:58 +0800 From: "william wallace" Sender: fierykylin@gmail.com To: "Warner Losh" In-Reply-To: <20060521.114807.74702188.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <87ab37ab0605201942o3e27c46w2ac57261e02a2890@mail.gmail.com> <20060521.000729.41671970.imp@bsdimp.com> <87ab37ab0605210108w127a235bue281428f52bbc784@mail.gmail.com> <20060521.114807.74702188.imp@bsdimp.com> X-Google-Sender-Auth: aaf5a687283f7723 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: Mon, 22 May 2006 06:29:12 -0000 On 5/22/06, Warner Losh wrote: > From: "william wallace" > Subject: Re: misc questions about the device&driver arch > Date: Sun, 21 May 2006 16:08:00 +0800 > > > On 5/21/06, Warner Losh wrote: > > > nope. It may be called once per bus instance per driver, if the bus > > > is not self-identifying. If the bus is self-idntiying, chances are > > > that it will not be called. pci never calls its children drivers' > > > identify routine because it already knows all the children on the bus > > > and doesn't need the leaf drivers to go find instances of themselves. > > > the isa bus driver, on the other hand, does call the identify routine > > > so that pre-plug and play standard device enumeration can happen. > > > > > > Warner > > the defination of self-enumerating > > 1 > > what does self-enumerating mean ? > > self-enumerating or self-identifying mean the same thing. The bus > driver is able to know all of its children. This may be because > there's a method to finding them, or the bus may have perfect > knowledge of what is there by other means. > PCI, CardBus, PC Card, USB, Firewire, and EISA are all examples of > self enumerating busses. You can know that you have a device, and the > device can provide information about its existance. ISA is the > odd-man out. It isn't possible to know when you have an ISA card in a > given slot. There are some add-on hacks to be able to discover the > devices. ISAPNP is one such hack. Really old Realtek adapters have > another. 3Com cards have yet another. It was for these old, pre-plug > and play enumeration techniques that the identify routine was > invented. o ,really thanx,first time to identity the meaning of IDENTIFY > > 2 > > does that mean the pci way of looping through configuration space ? > > Yes. > > > 3 > > does that happen in start time and hotplug time ? > > That happens at attach time. Cardbus right now has a private protocol > between the card bus bridge (cbb) and the bus to know when there's a > new card in a slot and to enumerate that bus. i think that 's because in cardbus protocol ,one bus only have one device ,so does pci express port (port :device =3D1:1) > > 4 > > pci doesn't need the leaf drivers to go find instances of themselves. > > does that mean that self-enumerating device system use the top do= wn way , > > and the non- self-enumerating device system use the down -top way > > Right. FreeBSD's device enumeration model is top down. > > > 5 > > i guest pci hot plug need some magic to identify or emulae(loop pci son= s ) > > Yes. The hot plug bridge would need to tell its child bus about > changes to the bus. This might mean the child bus does a full > enumeration, or a partial one. Cardbus does a full enueration, but > each card bus slot is its own bus. > > > BTW > > There r so many hot plug specifications ,SHPC hotplug ,PCIE hotplug > > and compaq hotplug and so on , in linux ,they use different driver for > > different pci > > bridge > > so i think for us to implement in freeBSD ,just do 1 by 1:) > > Yes. We'd need todo something similar in FreeBSD. Chances are that > the best way to approach this would be to add hotplug functionality > directly to the pci bus, and teach cardbus the new protocol. > > Warner > so there will be a long list of methods in the future hotplug pci driver and pcib driver SHPC interface .. ....... PCIE interface ....... compaq interface ....... IBM interface .... ....... poer interface ....... - thanks ,sir ! we who r about to die,salute u! From owner-freebsd-hackers@FreeBSD.ORG Mon May 22 06:52:26 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 8CCCD16A432 for ; Mon, 22 May 2006 06:52:26 +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 CD72A43D4C for ; Mon, 22 May 2006 06:52:21 +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 k4M6oB2e059313; Mon, 22 May 2006 00:50:11 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 22 May 2006 00:50:10 -0600 (MDT) Message-Id: <20060522.005010.104089663.imp@bsdimp.com> To: avalonwallace@gmail.com From: Warner Losh In-Reply-To: <87ab37ab0605212328ue7c70fcu49c5fec8921ae229@mail.gmail.com> References: <87ab37ab0605210108w127a235bue281428f52bbc784@mail.gmail.com> <20060521.114807.74702188.imp@bsdimp.com> <87ab37ab0605212328ue7c70fcu49c5fec8921ae229@mail.gmail.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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: Mon, 22 May 2006 06:52:26 -0000 > > That happens at attach time. Cardbus right now has a private protocol > > between the card bus bridge (cbb) and the bus to know when there's a > > new card in a slot and to enumerate that bus. > i think that 's because in cardbus protocol ,one bus only have one > device ,so does pci express port (port :device =1:1) Cool. I just bought a new laptop yesterday. It has an expresscard slot, which I think is handled as a PCI Express port (or USB 2.0 port, depending on the card that's inserted). > so there will be a long list of methods in the future hotplug pci > driver and pcib driver > SHPC interface .. > ....... > PCIE interface > ....... > compaq interface > ....... > IBM interface .... > ....... > poer interface > ....... Yes. If ExpressCard isn't handled by the PCIe interface, then we'd want to add it to the list as well. Warner From owner-freebsd-hackers@FreeBSD.ORG Mon May 22 20:19:28 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 F12B416B041 for ; Mon, 22 May 2006 20:19:27 +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 5CD2C43D45 for ; Mon, 22 May 2006 20:19:26 +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 k4MKJLq7081745; Tue, 23 May 2006 00:19:25 +0400 (MSD) (envelope-from maxim@macomnet.ru) Date: Tue, 23 May 2006 00:19:21 +0400 (MSD) From: Maxim Konovalov To: Matt Emmerton In-Reply-To: <002a01c5db7c$6817e030$1200a8c0@gsicomp.on.ca> Message-ID: <20060523000227.M81386@mp2.macomnet.net> References: <002a01c5db7c$6817e030$1200a8c0@gsicomp.on.ca> 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: Mon, 22 May 2006 20:19:38 -0000 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. For those who is unfamiliar: findblk command gets up to 32 _disk_ blocks as parameters and tries to find the inode(s) owning these blocks. You need to differentiate disk and file system blocks. To a find a disk block number from the given file system block you need to obtain fs_fsbtodb constant for the specific file system. E.g. for my /home: # dumpfs /dev/ad0s1 | head | grep fsbtodb frag 8 shift 3 fsbtodb 2 fsbtodb is 2. This is a power of 2. So disk block = file system block * 2^2 = file system block * 4 Here is a real life example: # ls -i ~/fsdb/fsdb 1961933 /home/maxim/fsdb/fsdb ^^^^^^^- ------------- - ----- inode number # ./fsdb/fsdb -r /dev/ad0s1e ** /dev/ad0s1e (NO WRITE) Examining file system `/dev/ad0s1e' Last Mounted on /home current inode: directory I=2 MODE=40755 SIZE=512 MTIME=Apr 14 02:10:21 2006 [0 nsec] CTIME=Apr 14 02:11:12 2006 [0 nsec] ATIME=May 22 00:15:46 2006 [0 nsec] OWNER=maxim GRP=wheel LINKCNT=9 FLAGS=0 BLKCNT=4 GEN=3d75e23a fsdb (inum: 2)> inode 1961933 current inode: regular file I=1961933 MODE=100755 SIZE=1063137 MTIME=May 22 23:51:35 2006 [0 nsec] CTIME=May 22 23:51:35 2006 [0 nsec] ATIME=May 22 23:51:34 2006 [0 nsec] OWNER=maxim GRP=maxim LINKCNT=1 FLAGS=0 BLKCNT=840 GEN=bb75d52 fsdb (inum: 1961933)> blocks Blocks for inode 1961933: Direct blocks: 7857760, 7857976, 7858016, 7858120, 7858152, 7858168, 7858176, 7858288, 7858376, 7858392, 7858408, 7858416 Indirect blocks: 7858480, 7858568, 7858584, 7858616, 7858672, 7858824, 7858832, 7859128, 7859144, 7859152, 7859168, 7859176, 7859184, 7859200, 7859352, 7859368, 7859376, 7859384, 7859456, 7859464, 7859472, 7859616, 7859624, 7859632, 7859640, 7857840, 7858136, 7858368, 7858384, 7858400, 7858592, 7859360, 7857912, 7858032, 7858840, 7857920, 7857944, 7857952, 7857992, 7858024, 7858040, 7858128, 7857928, 7857960, 7857968, 7858144, 7858848, 7860456, 7860464, 7860472, 7860480, 7860488, 7860504, fsdb (inum: 1961933)> findblk 31431680 # 7857920 file system block 31431680: data block of inode 1961933 Testers are welcome! Index: fsdb.8 =================================================================== RCS file: /home/ncvs/src/sbin/fsdb/fsdb.8,v retrieving revision 1.28 diff -u -p -r1.28 fsdb.8 --- fsdb.8 12 Feb 2005 23:23:53 -0000 1.28 +++ fsdb.8 22 May 2006 19:31:44 -0000 @@ -28,7 +28,7 @@ .\" .\" $FreeBSD: src/sbin/fsdb/fsdb.8,v 1.28 2005/02/12 23:23:53 trhodes Exp $ .\" -.Dd September 14, 1995 +.Dd May 22, 2006 .Dt FSDB 8 .Os .Sh NAME @@ -117,6 +117,12 @@ Print out the active inode. Print out the block list of the active inode. Note that the printout can become long for large files, since all indirect block pointers will also be printed. +.Pp +.It Cm findblk Ar disk block number ... +Find the inode(s) owning the specified disk block(s) number(s). +Note that these are not absolute disk blocks numbers, but offsets from the +start of the partition. +.Pp .It Cm uplink Increment the active inode's link count. .Pp Index: fsdb.c =================================================================== RCS file: /home/ncvs/src/sbin/fsdb/fsdb.c,v retrieving revision 1.32 diff -u -p -r1.32 fsdb.c --- fsdb.c 21 Apr 2006 20:33:16 -0000 1.32 +++ fsdb.c 22 May 2006 19:51:42 -0000 @@ -52,6 +52,13 @@ static const char rcsid[] = static void usage(void) __dead2; int cmdloop(void); +static int compare_blk32(uint32_t *wantedblk, uint32_t curblk); +static int compare_blk64(uint64_t *wantedblk, uint64_t curblk); +static int founddatablk(uint64_t blk); +static int find_blks32(uint32_t *buf, int size, uint32_t *blknum); +static int find_blks64(uint64_t *buf, int size, uint64_t *blknum); +static int find_indirblks32(uint32_t blk, int ind_level, uint32_t *blknum); +static int find_indirblks64(uint64_t blk, int ind_level, uint64_t *blknum); static void usage(void) @@ -129,6 +136,7 @@ CMDFUNC(uplink); /* incr link */ CMDFUNC(downlink); /* decr link */ CMDFUNC(linkcount); /* set link count */ CMDFUNC(quit); /* quit */ +CMDFUNC(findblk); /* find block */ CMDFUNC(ls); /* list directory */ CMDFUNC(rm); /* remove name */ CMDFUNC(ln); /* add name */ @@ -160,6 +168,7 @@ struct cmdtable cmds[] = { { "uplink", "Increment link count", 1, 1, FL_WR, uplink }, { "downlink", "Decrement link count", 1, 1, FL_WR, downlink }, { "linkcount", "Set link count to COUNT", 2, 2, FL_WR, linkcount }, + { "findblk", "Find inode owning disk block(s)", 2, 33, FL_RO, findblk}, { "ls", "List current inode as directory", 1, 1, FL_RO, ls }, { "rm", "Remove NAME from current inode directory", 2, 2, FL_WR | FL_ST, rm }, { "del", "Remove NAME from current inode directory", 2, 2, FL_WR | FL_ST, rm }, @@ -415,6 +424,262 @@ CMDFUNCSTART(ls) return 0; } +static int findblk_numtofind; +static int wantedblksize; + +CMDFUNCSTART(findblk) +{ + ino_t inum, inosused; + uint32_t *wantedblk32; + uint64_t *wantedblk64; + struct cg *cgp = &cgrp; + int c, i, is_ufs2; + + wantedblksize = (argc - 1); + is_ufs2 = sblock.fs_magic == FS_UFS2_MAGIC; + ocurrent = curinum; + + if (is_ufs2) { + wantedblk64 = calloc(wantedblksize, sizeof(uint64_t)); + if (wantedblk64 == NULL) + err(1, "malloc"); + for (i = 1; i < argc; i++) + wantedblk64[i - 1] = dbtofsb(&sblock, strtoull(argv[i], NULL, 0)); + } else { + wantedblk32 = calloc(wantedblksize, sizeof(uint32_t)); + if (wantedblk32 == NULL) + err(1, "malloc"); + for (i = 1; i < argc; i++) + wantedblk32[i - 1] = dbtofsb(&sblock, strtoull(argv[i], NULL, 0)); + } + findblk_numtofind = wantedblksize; + /* + * sblock.fs_ncg holds a number of cylinder groups. + * Iterate over all cylinder groups. + */ + for (c = 0; c < sblock.fs_ncg; c++) { + /* + * sblock.fs_ipg holds a number of inodes per cylinder group. + * Calculate a highest inode number for a given cylinder group. + */ + inum = c * sblock.fs_ipg; + /* Read cylinder group. */ + getblk(&cgblk, cgtod(&sblock, c), sblock.fs_cgsize); + memcpy(cgp, cgblk.b_un.b_cg, sblock.fs_cgsize); + /* + * Get a highest used inode number for a given cylinder group. + * For UFS1 all inodes initialized at the newfs stage. + */ + if (is_ufs2) + inosused = cgp->cg_initediblk; + else + inosused = sblock.fs_ipg; + + for (; inosused > 0; inum++, inosused--) { + /* Skip magic inodes: 0, WINO, ROOTINO. */ + if (inum < ROOTINO) + continue; + /* + * Check if the block we are looking for is just an inode block. + * + * ino_to_fsba() - get block containing inode from its number. + * INOPB() - get a number of inodes in one disk block. + */ + if (is_ufs2 ? + compare_blk64(wantedblk64, ino_to_fsba(&sblock, inum)) : + compare_blk32(wantedblk32, ino_to_fsba(&sblock, inum))) { + printf("block %llu: inode block (%d-%d)\n", + (unsigned long long)fsbtodb(&sblock, + ino_to_fsba(&sblock, inum)), + (inum / INOPB(&sblock)) * INOPB(&sblock), + (inum / INOPB(&sblock) + 1) * INOPB(&sblock)); + findblk_numtofind--; + if (findblk_numtofind == 0) + goto end; + } + /* Get on-disk inode aka dinode. */ + curinum = inum; + curinode = ginode(inum); + /* Find IFLNK dinode with allocated data blocks. */ + switch (DIP(curinode, di_mode) & IFMT) { + case IFDIR: + case IFREG: + if (DIP(curinode, di_blocks) == 0) + continue; + break; + case IFLNK: + { + uint64_t size = DIP(curinode, di_size); + if (size > 0 && size < sblock.fs_maxsymlinklen && + DIP(curinode, di_blocks) == 0) + continue; + else + break; + } + default: + continue; + } + /* Look through direct data blocks. */ + if (is_ufs2 ? + find_blks64(curinode->dp2.di_db, NDADDR, wantedblk64) : + find_blks32(curinode->dp1.di_db, NDADDR, wantedblk32)) + goto end; + for (i = 0; i < NIADDR; i++) { + /* + * Does the block we are looking for belongs to the + * indirect blocks? + */ + if (is_ufs2 ? + compare_blk64(wantedblk64, curinode->dp2.di_ib[i]) : + compare_blk32(wantedblk32, curinode->dp1.di_ib[i])) + if (founddatablk(is_ufs2 ? curinode->dp2.di_ib[i] : + curinode->dp1.di_ib[i])) + goto end; + /* + * Search through indirect, double and triple indirect + * data blocks. + */ + if (is_ufs2 ? (curinode->dp2.di_ib[i] != 0) : + (curinode->dp1.di_ib[i] != 0)) + if (is_ufs2 ? + find_indirblks64(curinode->dp2.di_ib[i], i, + wantedblk64) : + find_indirblks32(curinode->dp1.di_ib[i], i, + wantedblk32)) + goto end; + } + } + } +end: + curinum = ocurrent; + curinode = ginode(curinum); + return 0; +} + +static int +compare_blk32(uint32_t *wantedblk, uint32_t curblk) +{ + int i; + + for (i = 0; i < wantedblksize; i++) { + if (wantedblk[i] != 0 && wantedblk[i] == curblk) { + wantedblk[i] = 0; + return 1; + } + } + return 0; +} + +static int +compare_blk64(uint64_t *wantedblk, uint64_t curblk) +{ + int i; + + for (i = 0; i < wantedblksize; i++) { + if (wantedblk[i] != 0 && wantedblk[i] == curblk) { + wantedblk[i] = 0; + return 1; + } + } + return 0; +} + +static int +founddatablk(uint64_t blk) +{ + + printf("%llu: data block of inode %d\n", + (unsigned long long)fsbtodb(&sblock, blk), curinum); + findblk_numtofind--; + if (findblk_numtofind == 0) + return 1; + return 0; +} + +static int +find_blks32(uint32_t *buf, int size, uint32_t *wantedblk) +{ + int blk; + for (blk = 0; blk < size; blk++) { + if (buf[blk] == 0) + continue; + if (compare_blk32(wantedblk, buf[blk])) { + if (founddatablk(buf[blk])) + return 1; + } + } + return 0; +} + +static int +find_indirblks32(uint32_t blk, int ind_level, uint32_t *wantedblk) +{ +#define MAXNINDIR (MAXBSIZE / sizeof(uint32_t)) + uint32_t idblk[MAXNINDIR]; + int i; + + bread(fsreadfd, (char *)idblk, fsbtodb(&sblock, blk), (int)sblock.fs_bsize); + if (ind_level <= 0) { + if (find_blks32(idblk, sblock.fs_bsize / sizeof(uint32_t), wantedblk)) + return 1; + } else { + ind_level--; + for (i = 0; i < sblock.fs_bsize / sizeof(uint32_t); i++) { + if (compare_blk32(wantedblk, idblk[i])) { + if (founddatablk(idblk[i])) + return 1; + } + if (idblk[i] != 0) + if (find_indirblks32(idblk[i], ind_level, wantedblk)) + return 1; + } + } +#undef MAXNINDIR + return 0; +} + +static int +find_blks64(uint64_t *buf, int size, uint64_t *wantedblk) +{ + int blk; + for (blk = 0; blk < size; blk++) { + if (buf[blk] == 0) + continue; + if (compare_blk64(wantedblk, buf[blk])) { + if (founddatablk(buf[blk])) + return 1; + } + } + return 0; +} + +static int +find_indirblks64(uint64_t blk, int ind_level, uint64_t *wantedblk) +{ +#define MAXNINDIR (MAXBSIZE / sizeof(uint64_t)) + uint64_t idblk[MAXNINDIR]; + int i; + + bread(fsreadfd, (char *)idblk, fsbtodb(&sblock, blk), (int)sblock.fs_bsize); + if (ind_level <= 0) { + if (find_blks64(idblk, sblock.fs_bsize / sizeof(uint64_t), wantedblk)) + return 1; + } else { + ind_level--; + for (i = 0; i < sblock.fs_bsize / sizeof(uint64_t); i++) { + if (compare_blk64(wantedblk, idblk[i])) { + if (founddatablk(idblk[i])) + return 1; + } + if (idblk[i] != 0) + if (find_indirblks64(idblk[i], ind_level, wantedblk)) + return 1; + } + } +#undef MAXNINDIR + return 0; +} + int findino(struct inodesc *idesc); /* from fsck */ static int dolookup(char *name); %%% -- Maxim Konovalov From owner-freebsd-hackers@FreeBSD.ORG Mon May 22 23:19:12 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 A20EF16AFE3 for ; Mon, 22 May 2006 23:19:12 +0000 (UTC) (envelope-from ederbs.hackers@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA35843D6E for ; Mon, 22 May 2006 23:19:07 +0000 (GMT) (envelope-from ederbs.hackers@gmail.com) Received: by nz-out-0102.google.com with SMTP id 13so1309786nzn for ; Mon, 22 May 2006 16:19: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; b=Q7GTgBo5iGDtlN0X9+nWt/SQHeOjmPlthCwnVovsiEcYWDcsdIM4Smthh8+NHryYV5h1AIb+tQri72XRtJ04PQqFkCA9U3qCxu233ObbmCK90vs+OLSibR8J2Gk+yaLmNUVfz/d1NI/hdS2CWOYTyb6XfBYtAR+ZfIFQ/0XWhuU= Received: by 10.64.152.6 with SMTP id z6mr1379815qbd; Mon, 22 May 2006 16:19:07 -0700 (PDT) Received: by 10.64.178.4 with HTTP; Mon, 22 May 2006 16:19:07 -0700 (PDT) Message-ID: <2699850605221619u24b39e18kcff20b953ab2d93a@mail.gmail.com> Date: Mon, 22 May 2006 20:19:07 -0300 From: Eder To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Source ScreenSaver 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, 22 May 2006 23:19:12 -0000 Hi all, It follows link of the code and the procedures http://200.193.29.195/saver/index.html Thanks, Eder. From owner-freebsd-hackers@FreeBSD.ORG Tue May 23 01:16:30 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 A085A16A44D for ; Tue, 23 May 2006 01:16:30 +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 A4F4743D58 for ; Tue, 23 May 2006 01:16:29 +0000 (GMT) (envelope-from fierykylin@gmail.com) Received: by wx-out-0102.google.com with SMTP id i31so991346wxd for ; Mon, 22 May 2006 18:16:29 -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=QEpFA6lVc4gwaEx73BqcjoMmEDEovcYwDzHP0hV0fcmBR2SBJNnQwP3rSLaExwegcGLR8m5akIJM28HlzIfQHXVXTr3aciXHknACWBwS1aGiUnqpkWOEvavgWI1J5nihWtpMbRaZ4TSKFz1WjrrKOyGliubcZjLmpmEPyNAjXD0= Received: by 10.70.109.19 with SMTP id h19mr5334949wxc; Mon, 22 May 2006 18:16:29 -0700 (PDT) Received: by 10.70.43.11 with HTTP; Mon, 22 May 2006 18:16:29 -0700 (PDT) Message-ID: <87ab37ab0605221816y6cca5387sc43fa1e1116f55cc@mail.gmail.com> Date: Tue, 23 May 2006 09:16:29 +0800 From: "william wallace" Sender: fierykylin@gmail.com To: "Warner Losh" In-Reply-To: <20060522.005010.104089663.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <87ab37ab0605210108w127a235bue281428f52bbc784@mail.gmail.com> <20060521.114807.74702188.imp@bsdimp.com> <87ab37ab0605212328ue7c70fcu49c5fec8921ae229@mail.gmail.com> <20060522.005010.104089663.imp@bsdimp.com> X-Google-Sender-Auth: 748306afa86e69c9 Cc: "freebsd-hackers@freebsd.org" , freebsd-arch@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: Tue, 23 May 2006 01:16:30 -0000 I just have fossicked some idea from scottl@samsco.org "PCI-Express support= " PCI-Express support All, I've emailed before about supporting various aspects of PCI-Express and especially MSI, but haven't really gotten too far with it due to lack of resources. I now how access to a system that can do PCI-Express (PCI-E) so I'd like to revisit it and see what can be added for 5-STABLE. There are three general areas that need to be addressed in some form or another: Enhanced Configuration Space: PCI-E introduces an enhanced PCI Configuration space that allows for each function to have 4096 bytes of space instead of just 256. The Intel Lindenhurst chipset exposes this space via a memory-mapped window instead of the old slow type 1/2 ioport configuration methods. It appears that if the northbridge supports the enhanced config space then all PCI, PCI-X, and PCI-E devices will show up in it as well as in the legacy space. Proper support likely entails splitting up the pci host-bridge drivers so that a given ACPI or legacy front-end can plug into a given enhanced or legacy configuration layer. This definitely is not going to happen in time for 5.3, though. A hack that could work for 5-STABLE would be to provide pcie_[read|write]_config() methods that would compliment the existing pci methods and be available for drivers that want to access the >255 configuration addresses. Devices are already showing up that want to use these registers, btw. The mechanics of doing this would involve using pmap_mapdev() to map in the range that is specific to each function, and then hang this information off of the pcicfg structure. It's a bit hackish, yes, but it does seem to work in tests that a colleague of mine has done. MSI: I've bantered around different suggestions for an API that will support this. The basic thing that a driver needs from this is to know exactly how many message interrupt vectors are available to it. It can't just register vectors and handlers blindly since the purpose of MSI is to assign special meanings to each vector and allow the driver to handle each one in specifically. In order to keep the API as consistent as possible between classic interrupt sources and MSI sources, I'd like to add a new bus method: int bus_reserve_resource(device_t, int *start, int *end, int *count, int flags)= ; start, end, and count would be passed is as the desired range and would map to the per-function interrupt index in MSI. On return, the range supported and negotiated by the OS, bus, and function would be filled into these values. flags would be something like SYS_RES_MESSAGE. Internal failure of the function would be given in the return value. Whether failure to support MSI should be given as an error code return value can be debated. This function will also program the MSI configuration registers on the device to use the correct message cookie and number of messages. Interrupt registration would then proceed as normal with paired calls to bus_alloc_resource() and bus_setup_intr() for each desired interrupt index. The individual function interrupt index would be used as the start and end parameters to bus_alloc_resource(), and the type parameter would be SYS_RES_MESSAGE instead of SYS_RES_IRQ. bus_setup_intr() would unmask the source in the MSI APIC just like normal. Adding this for 5.3 is feasible, I think, and doesn't add a whole lot of risk. PCI-E provides a legacy mde for interrupts that simulates PCI interrupt lines, so drivers can choose whether to use MSI or the legacy interrupt methods. Hot-Plug, lane status, lane bonding: We don't have the infrastructure to support PCI or PCI-E hot-plug. It's also debatable whether this information will actually be available in a standard form. The PCI-E spec defines a new extended capabilities structure in the config space that can provide some of this information, but these kinds of things have a history of the vendors choosing their own proprietary methods and ignoring the standard. In short, we can't deal with this in the short term at all, and likely not in the long term without significant work to the bus and device infrastructure. On 5/22/06, Warner Losh wrote: > > > That happens at attach time. Cardbus right now has a private protoco= l > > > between the card bus bridge (cbb) and the bus to know when there's a > > > new card in a slot and to enumerate that bus. > > i think that 's because in cardbus protocol ,one bus only have one > > device ,so does pci express port (port :device =3D1:1) > > Cool. I just bought a new laptop yesterday. It has an expresscard > slot, which I think is handled as a PCI Express port (or USB 2.0 port, > depending on the card that's inserted). > > > so there will be a long list of methods in the future hotplug pci > > driver and pcib driver > > SHPC interface .. > > ....... > > PCIE interface > > ....... > > compaq interface > > ....... > > IBM interface .... > > ....... > > poer interface > > ....... > > Yes. If ExpressCard isn't handled by the PCIe interface, then we'd > want to add it to the list as well. > > Warner > --=20 we who r about to die,salute u! From owner-freebsd-hackers@FreeBSD.ORG Tue May 23 02:07: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 4533516A426; Tue, 23 May 2006 02:07:32 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id B20E343D48; Tue, 23 May 2006 02:07:31 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (yuojqcq06jdeuipr@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.4/8.13.3) with ESMTP id k4N27RRp027040; Mon, 22 May 2006 19:07:27 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.4/8.13.3/Submit) id k4N27QqC027039; Mon, 22 May 2006 19:07:26 -0700 (PDT) (envelope-from jmg) Date: Mon, 22 May 2006 19:07:26 -0700 From: John-Mark Gurney To: william wallace Message-ID: <20060523020726.GP770@funkthat.com> Mail-Followup-To: william wallace , Warner Losh , "freebsd-hackers@freebsd.org" , freebsd-arch@freebsd.org References: <87ab37ab0605210108w127a235bue281428f52bbc784@mail.gmail.com> <20060521.114807.74702188.imp@bsdimp.com> <87ab37ab0605212328ue7c70fcu49c5fec8921ae229@mail.gmail.com> <20060522.005010.104089663.imp@bsdimp.com> <87ab37ab0605221816y6cca5387sc43fa1e1116f55cc@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87ab37ab0605221816y6cca5387sc43fa1e1116f55cc@mail.gmail.com> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: "freebsd-hackers@freebsd.org" , freebsd-arch@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 Reply-To: John-Mark Gurney List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 May 2006 02:07:32 -0000 william wallace wrote this message on Tue, May 23, 2006 at 09:16 +0800: > In order to keep the API as consistent as possible between classic > interrupt sources and MSI sources, I'd like to add a new bus method: > > int > bus_reserve_resource(device_t, int *start, int *end, int *count, int flags); > > start, end, and count would be passed is as the desired range and would > map to the per-function interrupt index in MSI. On return, the range > supported and negotiated by the OS, bus, and function would be filled > into these values. flags would be something like SYS_RES_MESSAGE. > Internal failure of the function would be given in the return value. > Whether failure to support MSI should be given as an error code return > value can be debated. This function will also program the MSI > configuration registers on the device to use the correct message cookie > and number of messages. Why not create a wrapper, and start at the highest requested, and slowly work your way down as the requests are rejected.. since the number of messages must be a power of two, it isn't than many rounds.. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-hackers@FreeBSD.ORG Tue May 23 05:20: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 65E9C16A420; Tue, 23 May 2006 05:20:34 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E41C43D46; Tue, 23 May 2006 05:20:31 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k4N5K1c8004598; Mon, 22 May 2006 23:20:06 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <44729B81.8010909@samsco.org> Date: Mon, 22 May 2006 23:20:01 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: william wallace References: <87ab37ab0605210108w127a235bue281428f52bbc784@mail.gmail.com> <20060521.114807.74702188.imp@bsdimp.com> <87ab37ab0605212328ue7c70fcu49c5fec8921ae229@mail.gmail.com> <20060522.005010.104089663.imp@bsdimp.com> <87ab37ab0605221816y6cca5387sc43fa1e1116f55cc@mail.gmail.com> In-Reply-To: <87ab37ab0605221816y6cca5387sc43fa1e1116f55cc@mail.gmail.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: "freebsd-hackers@freebsd.org" , freebsd-arch@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: Tue, 23 May 2006 05:20:34 -0000 william wallace wrote: [...] > MSI: > I've bantered around different suggestions for an API that will support > this. The basic thing that a driver needs from this is to know > exactly how many message interrupt vectors are available to it. It > can't just register vectors and handlers blindly since the purpose of > MSI is to assign special meanings to each vector and allow the driver to > handle each one in specifically. [...] I just wanted to briefly say that an MSI implementation has been done recently, and that it should start getting wider circulation and review soon. That's not to say that more work and design can't be done in this area, but we should probably wait a bit and see what has been done already. Scott From owner-freebsd-hackers@FreeBSD.ORG Tue May 23 21:28: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 C1F0116B331 for ; Tue, 23 May 2006 21:28:09 +0000 (UTC) (envelope-from kim@tinker.com) Received: from tinker.com (tinker2-3.august.net [66.228.55.4]) by mx1.FreeBSD.org (Postfix) with SMTP id 2B41743D76 for ; Tue, 23 May 2006 21:28:08 +0000 (GMT) (envelope-from kim@tinker.com) Received: (qmail 73713 invoked by uid 27); 23 May 2006 21:28:08 -0000 Received: from 204.10.126.26.tinker.com(204.10.126.26), claiming to be "[192.42.172.22]" via SMTP by pop.tinker.com, id smtpd2NQZmT; Tue May 23 16:28:07 2006 Mime-Version: 1.0 (Apple Message framework v750) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: FreeBSD Hackers From: Kim Shrier Date: Tue, 23 May 2006 15:28:05 -0600 X-Mailer: Apple Mail (2.750) Subject: 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: Tue, 23 May 2006 21:28:16 -0000 Is there a port already in progress? If so, who would I contact to see if I could help. If not, is there any interest (besides myself) in having ZFS ported? Thanks, Kim -- Kim Shrier - principal, Shrier and Deihl - mailto:kim@tinker.com Remote Unix Network Admin, Security, Internet Software Development Tinker Internet Services - Superior FreeBSD-based Web Hosting http://www.tinker.com/ From owner-freebsd-hackers@FreeBSD.ORG Wed May 24 01:24: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 28D7A16A833 for ; Wed, 24 May 2006 01:24:04 +0000 (UTC) (envelope-from gs_stoller@juno.com) Received: from outbound-mail.nyc.untd.com (outbound-mail.nyc.untd.com [64.136.20.164]) by mx1.FreeBSD.org (Postfix) with SMTP id 676DE43D93 for ; Wed, 24 May 2006 01:23:44 +0000 (GMT) (envelope-from gs_stoller@juno.com) Received: from webmail29.nyc.untd.com (webmail29.nyc.untd.com [10.141.27.169]) by smtpout01.nyc.untd.com with SMTP id AABCHHPMJA5EFYW2 for (sender ); Tue, 23 May 2006 18:22:48 -0700 (PDT) Received: (from gs_stoller@juno.com) by webmail29.nyc.untd.com (jqueuemail) id LQ4NTPV8; Tue, 23 May 2006 18:22:18 PDT Received: from [67.84.52.37] by webmail29.nyc.untd.com with HTTP: Wed, 24 May 2006 01:21:59 GMT X-Originating-IP: [67.84.52.37] Mime-Version: 1.0 From: "gs_stoller@juno.com" Date: Wed, 24 May 2006 01:21:59 GMT To: freebsd-hackers@freebsd.org X-Mailer: Webmail Version 4.0 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Content-Type: text/plain Message-Id: <20060523.182218.19235.1026225@webmail29.nyc.untd.com> X-ContentStamp: 2:1:4110914514 X-UNTD-OriginStamp: /s5f1SIGSI3+WdnoYQ8yRDHgdxEl0vaJNbpvw2hkEIH/PaEbN0BQlg== X-UNTD-Peer-Info: 10.141.27.169|webmail29.nyc.untd.com|webmail29.nyc.untd.com|gs_stoller@juno.com Subject: The 'ln -s' command X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 01:24:10 -0000 I tried the 'ln -s' command in bothe 4.3 & 4.7 in a situation where i= t should fail and it did, but it still had a return/exit code of 0 , I = think it should have been nonzero. I tried 'ln -s a b' where the file= b existed (and was a directory) and I wanted to create the file named= a also pointing to it. The correct form was 'ln -s b a'. FreeBSD 4.3-RELEASE FreeBSD 4.3-RELEASE #0: Sat Apr 21 10:54:49 GMT 200= 1 jkh@narf.osd.bsdi.com:/usr/src/sys/compile/GENERIC i386 FreeBSD 4.7-RELEASE FreeBSD 4.7-RELEASE #0: Wed Oct 9 15:08:34 GMT 200= 2 root@builder.freebsdmall.com:/usr/obj/usr/src/sys/GENERIC i386 From owner-freebsd-hackers@FreeBSD.ORG Wed May 24 01:27:53 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 0628716A592 for ; Wed, 24 May 2006 01:27:52 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id C6BBD43D4C for ; Wed, 24 May 2006 01:27:51 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (ndq43a9fc27y8gtw@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.4/8.13.3) with ESMTP id k4O1RmJJ061122; Tue, 23 May 2006 18:27:48 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.4/8.13.3/Submit) id k4O1RlVF061121; Tue, 23 May 2006 18:27:47 -0700 (PDT) (envelope-from jmg) Date: Tue, 23 May 2006 18:27:47 -0700 From: John-Mark Gurney To: "gs_stoller@juno.com" Message-ID: <20060524012747.GB49081@funkthat.com> Mail-Followup-To: "gs_stoller@juno.com" , freebsd-hackers@freebsd.org References: <20060523.182218.19235.1026225@webmail29.nyc.untd.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060523.182218.19235.1026225@webmail29.nyc.untd.com> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: freebsd-hackers@freebsd.org Subject: Re: The 'ln -s' command X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 01:27:57 -0000 gs_stoller@juno.com wrote this message on Wed, May 24, 2006 at 01:21 +0000: > I tried the 'ln -s' command in bothe 4.3 & 4.7 in a situation where it should fail and it did, but it still had a return/exit code of 0 , I think it should have been nonzero. I tried 'ln -s a b' where the file b existed (and was a directory) and I wanted to create the file named a also pointing to it. The correct form was 'ln -s b a'. > > FreeBSD 4.3-RELEASE FreeBSD 4.3-RELEASE #0: Sat Apr 21 10:54:49 GMT 2001 jkh@narf.osd.bsdi.com:/usr/src/sys/compile/GENERIC i386 > > FreeBSD 4.7-RELEASE FreeBSD 4.7-RELEASE #0: Wed Oct 9 15:08:34 GMT 2002 root@builder.freebsdmall.com:/usr/obj/usr/src/sys/GENERIC i386 Hmm... I just tried this and I didn't see this behavior on 4.7-R: -bash-2.05b$ ln -s a z ln: z: File exists -bash-2.05b$ echo $? 1 -bash-2.05b$ ln -s z a -bash-2.05b$ echo $? 0 -bash-2.05b$ uname -a FreeBSD gate.funkthat.com 4.7-RELEASE FreeBSD 4.7-RELEASE #5: Tue Sep 9 02:05:39 PDT 2003 jmg@gate.funkthat.com:/usr/src/sys/compile/gate i386 Looks like the EEXIST is returning non-zero... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-hackers@FreeBSD.ORG Wed May 24 01:42: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 CF79216AB7E for ; Wed, 24 May 2006 01:42:20 +0000 (UTC) (envelope-from joseph.koshy@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F45B43D45 for ; Wed, 24 May 2006 01:42:20 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: by ug-out-1314.google.com with SMTP id m3so1951377uge for ; Tue, 23 May 2006 18:42:19 -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=VUQ4KCl9by74UvBYg7UI0041eC/Qjm7Os8M0BEnmkoZAcUzLBAgELJHpze20dmjahElxrMEZ4YWwC1eEa0hlrEnfP0A00d4BcFWDw04f5t47dH59p7u0HdWYRmMrR6HJtYzJl7wEWlKlACeAdo7T/ptVnPemPaKzi+59EfWPu0k= Received: by 10.78.47.9 with SMTP id u9mr1577477huu; Tue, 23 May 2006 18:42:18 -0700 (PDT) Received: by 10.78.71.19 with HTTP; Tue, 23 May 2006 18:42:18 -0700 (PDT) Message-ID: <84dead720605231842y4fc8f1c9x69bdce897fb470f7@mail.gmail.com> Date: Wed, 24 May 2006 07:12:18 +0530 From: "Joseph Koshy" To: "gs_stoller@juno.com" In-Reply-To: <20060523.182218.19235.1026225@webmail29.nyc.untd.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20060523.182218.19235.1026225@webmail29.nyc.untd.com> Cc: freebsd-hackers@freebsd.org Subject: Re: The 'ln -s' command X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 01:42:21 -0000 > I tried the 'ln -s' command in bothe 4.3 & 4.7 in a > situation where it should fail and it did, but it still had > a return/exit code of 0 , I think it should have been > nonzero. I tried 'ln -s a b' where the file b existed > (and was a directory) and I wanted to create the file named > a also pointing to it. The correct form was 'ln -s b a'. > FreeBSD 4.3-RELEASE FreeBSD 4.3-RELEASE #0: Sat Apr 21 \ 10:54:49 GMT 2001 \ jkh@narf.osd.bsdi.com:/usr/src/sys/compile/GENERIC i386 > FreeBSD 4.7-RELEASE FreeBSD 4.7-RELEASE #0: Wed Oct 9 \ 15:08:34 GMT 2002 \ root@builder.freebsdmall.com:/usr/obj/usr/src/sys/GENERIC \ i386 I don't have a 4.3 or 4.7 box, but on 4.11 I see: $ ls a.out a.out $ ln -s foo a.out ln: a.out: File exists $ echo $? 1 Are you really running /bin/ln? Do you run other programs at the time of displaying your PS1 prompt? -- FreeBSD Developer, http://people.freebsd.org/~jkoshy From owner-freebsd-hackers@FreeBSD.ORG Wed May 24 01:42:59 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 2A93216A6C2 for ; Wed, 24 May 2006 01:42:59 +0000 (UTC) (envelope-from boris@brooknet.com.au) Received: from jay.exetel.com.au (jay.exetel.com.au [220.233.0.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4DE0A43D5A for ; Wed, 24 May 2006 01:42:56 +0000 (GMT) (envelope-from boris@brooknet.com.au) Received: (qmail 25700 invoked by uid 507); 24 May 2006 11:42:55 +1000 Received: from 180.205.233.220.exetel.com.au (HELO ?192.168.0.157?) (220.233.205.180) by jay.exetel.com.au with SMTP; 24 May 2006 11:42:55 +1000 In-Reply-To: <20060523.182218.19235.1026225@webmail29.nyc.untd.com> References: <20060523.182218.19235.1026225@webmail29.nyc.untd.com> Mime-Version: 1.0 (Apple Message framework v750) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <61DC5A82-3742-4FB0-9B7E-9655F4E4FC60@brooknet.com.au> Content-Transfer-Encoding: 7bit From: Sam Lawrance Date: Wed, 24 May 2006 11:42:51 +1000 To: gs_stoller@juno.com X-Mailer: Apple Mail (2.750) Cc: freebsd-hackers@freebsd.org Subject: Re: The 'ln -s' command X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 01:42:59 -0000 On 24/05/2006, at 1:21 AM, gs_stoller@juno.com wrote: > I tried the 'ln -s' command in bothe 4.3 & 4.7 in a situation > where it should fail and it did, but it still had a return/exit > code of 0 , I think it should have been nonzero. I tried 'ln -s > a b' where the file b existed (and was a directory) and I wanted > to create the file named a also pointing to it. The correct form > was 'ln -s b a'. See the synopsis in the manpage for 'ln'. It exited nonzero because you successfully put a symlink under the directory 'b', pointing to 'a'. oddie:~ sam$ mkdir b oddie:~ sam$ ln -s a b oddie:~ sam$ ls -l b total 8 lrwxr-xr-x 1 sam sam 1 May 24 11:42 a -> a From owner-freebsd-hackers@FreeBSD.ORG Wed May 24 01:47: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 521A616A9CB for ; Wed, 24 May 2006 01:47:06 +0000 (UTC) (envelope-from boris@brooknet.com.au) Received: from jay.exetel.com.au (jay.exetel.com.au [220.233.0.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB0F543D46 for ; Wed, 24 May 2006 01:47:04 +0000 (GMT) (envelope-from boris@brooknet.com.au) Received: (qmail 27434 invoked by uid 507); 24 May 2006 11:47:04 +1000 Received: from 180.205.233.220.exetel.com.au (HELO ?192.168.0.157?) (220.233.205.180) by jay.exetel.com.au with SMTP; 24 May 2006 11:47:04 +1000 Mime-Version: 1.0 (Apple Message framework v750) In-Reply-To: <61DC5A82-3742-4FB0-9B7E-9655F4E4FC60@brooknet.com.au> References: <20060523.182218.19235.1026225@webmail29.nyc.untd.com> <61DC5A82-3742-4FB0-9B7E-9655F4E4FC60@brooknet.com.au> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <3E55A43D-7017-4897-9D10-758F8F393404@brooknet.com.au> Content-Transfer-Encoding: 7bit From: Sam Lawrance Date: Wed, 24 May 2006 11:47:02 +1000 To: gs_stoller@juno.com, freebsd-hackers@freebsd.org X-Mailer: Apple Mail (2.750) Cc: Subject: Re: The 'ln -s' command X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 01:47:07 -0000 On 24/05/2006, at 11:42 AM, Sam Lawrance wrote: > > On 24/05/2006, at 1:21 AM, gs_stoller@juno.com wrote: > >> I tried the 'ln -s' command in bothe 4.3 & 4.7 in a situation >> where it should fail and it did, but it still had a return/exit >> code of 0 , I think it should have been nonzero. I tried 'ln -s >> a b' where the file b existed (and was a directory) and I >> wanted to create the file named a also pointing to it. The >> correct form was 'ln -s b a'. > > See the synopsis in the manpage for 'ln'. It exited nonzero > because you successfully put a symlink under the directory 'b', > pointing to 'a'. > > oddie:~ sam$ mkdir b > oddie:~ sam$ ln -s a b > oddie:~ sam$ ls -l b > total 8 > lrwxr-xr-x 1 sam sam 1 May 24 11:42 a -> a Oops, I meant: "it exited with zero status because ..." From owner-freebsd-hackers@FreeBSD.ORG Wed May 24 02:22:52 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 2B87716AE26 for ; Wed, 24 May 2006 02:22:52 +0000 (UTC) (envelope-from pfgshield-freebsd@yahoo.com) Received: from web32702.mail.mud.yahoo.com (web32702.mail.mud.yahoo.com [68.142.207.246]) by mx1.FreeBSD.org (Postfix) with SMTP id B180643D5D for ; Wed, 24 May 2006 02:22:45 +0000 (GMT) (envelope-from pfgshield-freebsd@yahoo.com) Received: (qmail 68703 invoked by uid 60001); 24 May 2006 02:22:45 -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:MIME-Version:Content-Type; b=gWV1I8DOZ8/iFY+QL5XKqUvbNsvamlg2g3hrSo5SZqsHFV7svUXM40J6hN8Z3it8oCbgXDpxYGThVumKU/vzEYzAl70cAt8+zfLv5Y6e5LkCM9W5OLKL1SvT+5x7cjusEl+g0qZpFF54dPulpvPbpDtaeTSoMVV0N3lNHRqm++k= ; Message-ID: <20060524022245.68701.qmail@web32702.mail.mud.yahoo.com> Received: from [200.118.175.203] by web32702.mail.mud.yahoo.com via HTTP; Wed, 24 May 2006 04:22:45 CEST Date: Wed, 24 May 2006 04:22:45 +0200 (CEST) From: To: Kim Shrier , FreeBSD Hackers MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Mailman-Approved-At: Wed, 24 May 2006 02:48:23 +0000 Cc: Subject: 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: Wed, 24 May 2006 02:22:58 -0000 Hello; DragonFly and NetBSD are interested, I'm sure there's interest in FreeBSD too, but AFAICT no one has started. Here is an interesting link: http://www.opensolaris.org/os/community/zfs/porting/ cheers, Pedro. --- Pedro F. Giffuni M. Sc. Industrial Eng. University of Pittsburgh Mech. Eng. Universidad Nacional de Colombia --- Yahoo is powered by FreeBSD http://www.FreeBSD.org/ 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 Wed May 24 04:26:26 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 61A5016A43A for ; Wed, 24 May 2006 04:26:26 +0000 (UTC) (envelope-from spork@fasttrackmonkey.com) Received: from angryfist.fasttrackmonkey.com (angryfist.fasttrackmonkey.com [216.220.107.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id CACE143D46 for ; Wed, 24 May 2006 04:26:25 +0000 (GMT) (envelope-from spork@fasttrackmonkey.com) Received: (qmail 58851 invoked by uid 2003); 24 May 2006 04:26:06 -0000 Received: from spork@fasttrackmonkey.com by angryfist.fasttrackmonkey.com by uid 1001 with qmail-scanner-1.20 (clamscan: 0.65. Clear:RC:1(216.220.116.154):. Processed in 0.049464 secs); 24 May 2006 04:26:06 -0000 Received: from unknown (HELO white.nat.fasttrackmonkey.com) (216.220.116.154) by 0 with (DHE-RSA-AES256-SHA encrypted) SMTP; 24 May 2006 04:26:06 -0000 Date: Wed, 24 May 2006 00:26:23 -0400 (EDT) From: Charles Sprickman X-X-Sender: spork@white.nat.fasttrackmonkey.com To: hackers@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Subject: state of growfs? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 04:26:26 -0000 Hi all, I've gotten somewhat fed up with the SCSI hardware RAID stuff out there, so I'm jumping ship and going with 3Ware SATA for a new PGSQL server. It's fairly important to me to be able to "grow" the filesystem. We'll be starting with 6 or 8 250GB drives and going up to the max of 12 we can hang off of that controller. Aside from all the problems with 2TB+ filesystems, this kind of looks possible. 3Ware claims they can expand a volume, and they also mention that it should work with FreeBSD (but stop short of explaining how). growfs seems to be the thing to use, but I'm seeing very little about it in the archives. Is it reliable? Can it deal with large filesystems? Anyone here have personal experience with it? Thanks, Charles From owner-freebsd-hackers@FreeBSD.ORG Wed May 24 04:55:36 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0632D16A41F for ; Wed, 24 May 2006 04:55:36 +0000 (UTC) (envelope-from stephen@bartlettsoftware.biz) Received: from n120.sc0.cp.net (smtpout1117.sc0.cp.net [64.97.144.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB7F543D46 for ; Wed, 24 May 2006 04:55:35 +0000 (GMT) (envelope-from stephen@bartlettsoftware.biz) Received: from daemon.hawaiiantel.net (72.235.34.7) by n120.sc0.cp.net (7.2.069.1) (authenticated as stephen_bartlett@hawaiiantel.net) id 447149CB0006A626; Wed, 24 May 2006 04:55:24 +0000 Received: by daemon.hawaiiantel.net (Postfix, from userid 1001) id CD6E528A70; Tue, 23 May 2006 18:55:22 -1000 (HST) Date: Tue, 23 May 2006 18:55:22 -1000 From: Stephen Bartlett To: Charles Sprickman Message-ID: <20060524045522.GA842@daemon.localdomain.local> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0F1p//8PRICkK4MW" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: hackers@freebsd.org Subject: Re: state of growfs? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 04:55:36 -0000 --0F1p//8PRICkK4MW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Thus spake Charles Sprickman on Wed, May 24, 2006 at 12:26:23AM -0400: [snip] > growfs seems to be the thing to use, but I'm seeing very little about it = in=20 > the archives. Is it reliable? Can it deal with large filesystems? Anyon= e=20 > here have personal experience with it? Funny you should ask -- I just got bitten by growfs. Was running out of room and decided to delete a partition and grow FreeBSD into that space. Am running 6.1-RELEASE on i386, no RAID, no SCSI. =20 I used these tools: parted fdisk -u ... bsdlabel -e ... growfs -s ... I followed all tips/instructions I could find and was very careful, I thought. All seemed well until the final reboot, when FreeBSD would only mount all the partitions in the slice as *read-only*. Nothing I could try fixed it. It was also complaining about bad fs blocks, and fsck couldn't help. I had to start *all over* and install 6.1 from scratch. That's just my tale.... - Stephen --=20 Stephen Bartlett President, Bartlett Software, Inc. http://www.bartlettsoftware.biz/ --0F1p//8PRICkK4MW Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEc+c6R7d3GIt7UjgRApBPAJ9/shQ1k7hb6DobXY9RP/sa30TAtACfXglE wio0BhOjJv+zWu58riuT/EM= =lyCv -----END PGP SIGNATURE----- --0F1p//8PRICkK4MW-- From owner-freebsd-hackers@FreeBSD.ORG Wed May 24 05:32: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 EAECD16A41F for ; Wed, 24 May 2006 05:32:00 +0000 (UTC) (envelope-from kazakov@gmail.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 80BE543D45 for ; Wed, 24 May 2006 05:32:00 +0000 (GMT) (envelope-from kazakov@gmail.com) Received: by py-out-1112.google.com with SMTP id f28so1970882pyf for ; Tue, 23 May 2006 22:31:59 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:subject:from:to:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding; b=CP+ErK9kN84sxXufCSMzR8SSgQP1BBVDUKjIMkmHarwBxUynzVKjcIOjFdpXD9bkoR0+KgafEMD3MDh1DmNVxNb7aWROzdtiRrra38/5Dtbxjh9u5axEqjxM54WV5W05pVla3qDVaJxIqAkozdDzXeCiQkQInStH20DvXNpLhlI= Received: by 10.35.34.20 with SMTP id m20mr819663pyj; Tue, 23 May 2006 22:31:59 -0700 (PDT) Received: from tyoma.kek.jp ( [130.87.161.100]) by mx.gmail.com with ESMTP id n40sm1110495pyg.2006.05.23.22.31.58; Tue, 23 May 2006 22:31:59 -0700 (PDT) From: Artem Kazakov To: FreeBSD Hackers Content-Type: text/plain Date: Wed, 24 May 2006 14:32:03 +0900 Message-Id: <1148448723.1639.102.camel@tyoma.linac.kek.jp> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Subject: process descriptor table X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 05:32:01 -0000 Dear All, please give me a hint, how to see process descriptor table? I'm debugging in gdb. Tyoma. From owner-freebsd-hackers@FreeBSD.ORG Wed May 24 07:06:12 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 5F61816A423 for ; Wed, 24 May 2006 07:06:12 +0000 (UTC) (envelope-from tyler@tamu.edu) Received: from smtp-relay.tamu.edu (smtp-relay.tamu.edu [165.91.22.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A27243D4C for ; Wed, 24 May 2006 07:06:02 +0000 (GMT) (envelope-from tyler@tamu.edu) Received: from [192.168.250.100] (24-240-208-83.dhcp.sprn.tx.charter.com [24.240.208.83]) (authenticated bits=0) by smtp-relay.tamu.edu (8.13.6/8.13.3/oc) with ESMTP id k4O76EfY096542 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO) for ; Wed, 24 May 2006 02:06:27 -0500 (CDT) (envelope-from tyler@tamu.edu) Mime-Version: 1.0 (Apple Message framework v750) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: FreeBSD Hackers From: "R. Tyler Ballance" Date: Wed, 24 May 2006 02:05:33 -0500 X-Pgp-Agent: GPGMail 1.1.2 (Tiger) X-Mailer: Apple Mail (2.750) Received-SPF: pass (smtp-relay.tamu.edu: 24.240.208.83 is authenticated by a trusted mechanism) Subject: Kernel call stack for dummies. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 07:06:19 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've started the uphill battle to port FreeBSD's kernel to run "paravirtualized" (<--note the smart sounding vocabulary) on top of the L4/Iguana OS (Iguana is a very barebones OS developed by NICTA: http://www.ertos.nicta.com.au/software/kenge/iguana-project/latest/) On of the first steps is basically porting the lowest of low kernel calls such as those in sys/i386 sys/arm and sys/amd64 for example into sys/iguana to talk to iguana instead of actual hardware. One of the things I need to figure out is the order in which kernel calls are made on boot, so I can go through and reimplement them one by one (in order to spend as little time as possible going back and fixing other problems of mine), as suggested by Ben Leslie at NICTA. Is there a good overview of what's happening directly after boot in terms of the procedure in which functions are called right after the bootloader finishes it business? Cheers, - -R. Tyler Ballance -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (Darwin) iD8DBQFEdAW/qO6nEJfroRsRAgMUAJ93K5wwRRXljCkgx8SaU0fdgN3l3gCgkuqA S/BC67a7O1KuQzvnsvZUAvc= =PQtC -----END PGP SIGNATURE----- From owner-freebsd-hackers@FreeBSD.ORG Wed May 24 07:26: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 DB1E616A421 for ; Wed, 24 May 2006 07:26:24 +0000 (UTC) (envelope-from julian@elischer.org) Received: from a50.ironport.com (a50.ironport.com [63.251.108.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id A3E6743D45 for ; Wed, 24 May 2006 07:26:24 +0000 (GMT) (envelope-from julian@elischer.org) Received: from unknown (HELO [192.168.2.4]) ([10.251.60.97]) by a50.ironport.com with ESMTP; 24 May 2006 00:26:24 -0700 Message-ID: <44740A9F.9080202@elischer.org> Date: Wed, 24 May 2006 00:26:23 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.13) Gecko/20060414 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Artem Kazakov References: <1148448723.1639.102.camel@tyoma.linac.kek.jp> In-Reply-To: <1148448723.1639.102.camel@tyoma.linac.kek.jp> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Hackers Subject: Re: process descriptor table X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 07:26:25 -0000 Artem Kazakov wrote: >Dear All, >please give me a hint, how to see process descriptor table? >I'm debugging in gdb. > > > what is a process descriptor table? process FILE descriptor table? process table? >Tyoma. > >_______________________________________________ >freebsd-hackers@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > > From owner-freebsd-hackers@FreeBSD.ORG Wed May 24 07:41: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 45D6A16A48B for ; Wed, 24 May 2006 07:41:34 +0000 (UTC) (envelope-from kazakov@gmail.com) Received: from wx-out-0102.google.com (wx-out-0102.google.com [66.249.82.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id E24F443D55 for ; Wed, 24 May 2006 07:41:28 +0000 (GMT) (envelope-from kazakov@gmail.com) Received: by wx-out-0102.google.com with SMTP id i31so1207368wxd for ; Wed, 24 May 2006 00:41:27 -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=WKMHKXrEhUGGU52xH6YQsCp200UHPHYi9vh+ZFbb05vxaZRYrwJtbRqLlTBdGAcaqzstuRCJngeU0Wrhzgsd7kszaltEBhrE/hmhXx3/Y6eaJTisCscs2fk97LF4Y2iYLTjCZucpZXJvJuk0AzekRIz4bqxI5QmZvFOXDnYwgMM= Received: by 10.70.31.19 with SMTP id e19mr7399440wxe; Wed, 24 May 2006 00:41:27 -0700 (PDT) Received: by 10.70.126.17 with HTTP; Wed, 24 May 2006 00:41:27 -0700 (PDT) Message-ID: Date: Wed, 24 May 2006 16:41:27 +0900 From: "Artem Kazakov" To: "Julian Elischer" In-Reply-To: <44740A9F.9080202@elischer.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <1148448723.1639.102.camel@tyoma.linac.kek.jp> <44740A9F.9080202@elischer.org> Cc: FreeBSD Hackers Subject: Re: process descriptor table X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 07:41:34 -0000 > what is a process descriptor table? > process FILE descriptor table? > process table? process file descriptor table I suppose. The problem is that at some point a socket() function is called. And it returns descriptor =3D 1, which is a standart ouput. So when write() is done, everything goes to terminal,instead of socket. I want to see descriptor table, to see why this can happen. From owner-freebsd-hackers@FreeBSD.ORG Wed May 24 07:48:47 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 695C516A425 for ; Wed, 24 May 2006 07:48:47 +0000 (UTC) (envelope-from fierykylin@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 C5EC343D49 for ; Wed, 24 May 2006 07:48:46 +0000 (GMT) (envelope-from fierykylin@gmail.com) Received: by wx-out-0102.google.com with SMTP id i31so1208062wxd for ; Wed, 24 May 2006 00:48:46 -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=eAyR6ccIw3GleM8CcLAA50VjGx5+Bb7jQ6+J1FAMwLZIc1gBAhPDNMXmfJANVQu6lAwhBwvunHzbKABUJn1LAEiNC4pguauTiAKv+XxyDYpUYopL7tsMZ+QLh4//eZTuTtDNS8o0sSHcfNHsTgS3r89U4vH6mXidyP/frLmKRFg= Received: by 10.70.116.10 with SMTP id o10mr7398859wxc; Wed, 24 May 2006 00:48:46 -0700 (PDT) Received: by 10.70.43.11 with HTTP; Wed, 24 May 2006 00:48:46 -0700 (PDT) Message-ID: <87ab37ab0605240048g224218a5s87cfe1b1ed5cc8c9@mail.gmail.com> Date: Wed, 24 May 2006 15:48:46 +0800 From: "william wallace" Sender: fierykylin@gmail.com To: "Scott Long" , imp@bsdimp.com In-Reply-To: <44729B81.8010909@samsco.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <87ab37ab0605210108w127a235bue281428f52bbc784@mail.gmail.com> <20060521.114807.74702188.imp@bsdimp.com> <87ab37ab0605212328ue7c70fcu49c5fec8921ae229@mail.gmail.com> <20060522.005010.104089663.imp@bsdimp.com> <87ab37ab0605221816y6cca5387sc43fa1e1116f55cc@mail.gmail.com> <44729B81.8010909@samsco.org> X-Google-Sender-Auth: ee0f50cfeb6d7863 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: Wed, 24 May 2006 07:48:49 -0000 IN static device_method_t pci_methods[] =3D { what is the freeBSD's magic to connect pci_read_config_method wtih PCI_READ_CONFIG? awk script?and so on? which DEVMETHOD(pci_read_config,=09pci_read_config_method), in pci.c command =3D PCI_READ_CONFIG(dev, child, PCIR_COMMAND, 2); in pci_enable_io_method in pci.c and what if i create a new method in pci method interface ? such as DEVMETHOD(pci_have_rest ,=09pci_have_rest_method) what else should i do when i want to use PCI_HAVE_REST(dev ) point to pci_have_rest_method On 5/23/06, Scott Long wrote: > william wallace wrote: > > [...] > > > MSI: > > I've bantered around different suggestions for an API that will support > > this. The basic thing that a driver needs from this is to know > > exactly how many message interrupt vectors are available to it. It > > can't just register vectors and handlers blindly since the purpose of > > MSI is to assign special meanings to each vector and allow the driver t= o > > handle each one in specifically. > > [...] > > I just wanted to briefly say that an MSI implementation has been done > recently, and that it should start getting wider circulation and review > soon. That's not to say that more work and design can't be done in this > area, but we should probably wait a bit and see what has been done > already. > > Scott > > --=20 we who r about to die,salute u! From owner-freebsd-hackers@FreeBSD.ORG Wed May 24 07:59:53 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 1BC3516A451 for ; Wed, 24 May 2006 07:59:53 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 976B743D46 for ; Wed, 24 May 2006 07:59:52 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (glidy82uko4njbl0@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.4/8.13.3) with ESMTP id k4O7xnqm070062; Wed, 24 May 2006 00:59:49 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.4/8.13.3/Submit) id k4O7xkBg070061; Wed, 24 May 2006 00:59:46 -0700 (PDT) (envelope-from jmg) Date: Wed, 24 May 2006 00:59:46 -0700 From: John-Mark Gurney To: william wallace Message-ID: <20060524075946.GE49081@funkthat.com> Mail-Followup-To: william wallace , Scott Long , imp@bsdimp.com, "freebsd-hackers@freebsd.org" References: <87ab37ab0605210108w127a235bue281428f52bbc784@mail.gmail.com> <20060521.114807.74702188.imp@bsdimp.com> <87ab37ab0605212328ue7c70fcu49c5fec8921ae229@mail.gmail.com> <20060522.005010.104089663.imp@bsdimp.com> <87ab37ab0605221816y6cca5387sc43fa1e1116f55cc@mail.gmail.com> <44729B81.8010909@samsco.org> <87ab37ab0605240048g224218a5s87cfe1b1ed5cc8c9@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87ab37ab0605240048g224218a5s87cfe1b1ed5cc8c9@mail.gmail.com> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: "freebsd-hackers@freebsd.org" , Scott Long Subject: Re: misc questions about the device&driver arch X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 07:59:54 -0000 william wallace wrote this message on Wed, May 24, 2006 at 15:48 +0800: > IN static device_method_t pci_methods[] = { > what is the freeBSD's magic to connect pci_read_config_method wtih > PCI_READ_CONFIG? awk script?and so on? > which > DEVMETHOD(pci_read_config, pci_read_config_method), in pci.c > command = PCI_READ_CONFIG(dev, child, PCIR_COMMAND, 2); in > pci_enable_io_method in pci.c > > and what if i create a new method in pci method interface ? > such as DEVMETHOD(pci_have_rest , pci_have_rest_method) > what else should i do when i want to use PCI_HAVE_REST(dev ) point to > pci_have_rest_method These are handled by the _if.m files... look at sys/dev/pci/pci_if.m... There is an awk script in sys/tools/makeobjops.awk that converts the _if.m to the appropriate .h and .c files... Please read: http://www.freebsd.org/doc/en_US.ISO8859-1/books/arch-handbook/kernel-objects-using.html http://www.freebsd.org/doc/en_US.ISO8859-1/books/arch-handbook/newbus-overview.html The device methods are implemented using kobj... > On 5/23/06, Scott Long wrote: > >william wallace wrote: > > > >[...] > > > >> MSI: > >> I've bantered around different suggestions for an API that will support > >> this. The basic thing that a driver needs from this is to know > >> exactly how many message interrupt vectors are available to it. It > >> can't just register vectors and handlers blindly since the purpose of > >> MSI is to assign special meanings to each vector and allow the driver to > >> handle each one in specifically. > > > >[...] > > > >I just wanted to briefly say that an MSI implementation has been done > >recently, and that it should start getting wider circulation and review > >soon. That's not to say that more work and design can't be done in this > >area, but we should probably wait a bit and see what has been done > >already. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-hackers@FreeBSD.ORG Wed May 24 09:31:02 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 2865716A453 for ; Wed, 24 May 2006 09:31:02 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D0C843D46 for ; Wed, 24 May 2006 09:31:01 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id B539F2089; Wed, 24 May 2006 11:30:56 +0200 (CEST) X-Spam-Tests: none X-Spam-Learn: disabled X-Spam-Score: 0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on tim.des.no Received: from xps.des.no (des.no [80.203.243.180]) by tim.des.no (Postfix) with ESMTP id 41EEF2087; Wed, 24 May 2006 11:30:56 +0200 (CEST) Received: by xps.des.no (Postfix, from userid 1001) id 2093633CAD; Wed, 24 May 2006 11:30:56 +0200 (CEST) From: des@des.no (Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?=) To: "Artem Kazakov" References: <1148448723.1639.102.camel@tyoma.linac.kek.jp> <44740A9F.9080202@elischer.org> Date: Wed, 24 May 2006 11:30:55 +0200 In-Reply-To: (Artem Kazakov's message of "Wed, 24 May 2006 16:41:27 +0900") Message-ID: <86hd3fixbk.fsf@xps.des.no> User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD Hackers , Julian Elischer Subject: Re: process descriptor table X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 09:31:02 -0000 "Artem Kazakov" writes: > The problem is that at some point a socket() function is called. And > it returns descriptor =3D 1, which is a standart ouput. socket() will not return 1 unless you previously closed descriptor 1, either directly with close(1) or indirectly with fclose(stdout). You probably did something like this: if (sd =3D socket(AF_INET, SOCK_STREAM, 0) !=3D -1) { /* foo */ } which assigns either 1 or 0 to sd depending on whether socket() returned -1. You need to parenthesize the assignment: if ((sd =3D socket(AF_INET, SOCK_STREAM, 0)) !=3D -1) { /* foo */ } You also need to check the return value from either bind() or connect() (they should have failed and set errno to ENOTSOCK), and enable compiler warnings (gcc should have warned you about the dodgy assignment / comparison). DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-hackers@FreeBSD.ORG Wed May 24 11:01:52 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 D97FD16A41F for ; Wed, 24 May 2006 11:01:52 +0000 (UTC) (envelope-from kazakov@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.178]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6CAA843D49 for ; Wed, 24 May 2006 11:01:52 +0000 (GMT) (envelope-from kazakov@gmail.com) Received: by py-out-1112.google.com with SMTP id f28so2031970pyf for ; Wed, 24 May 2006 04:01:51 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:subject:from:to:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding; b=Jz6Ag62SKLYpFJ//0Eh7KQjRSg8ka5c6U2hyYd1Hrf37iAuU3c7IJy03mEFPKi+UZpGsWuMzPkBjbSSTtWZfqmWYTiYxzKfFIwQOSBJaMW2c0qmpFkBqP9VnEqjMDg3FmPvp3yqCOQiUIVYAIPsGfRDvmmEz2sxOnYv90AH0/rk= Received: by 10.35.81.10 with SMTP id i10mr919018pyl; Wed, 24 May 2006 04:01:42 -0700 (PDT) Received: from tyoma.kek.jp ( [130.87.161.100]) by mx.gmail.com with ESMTP id w66sm1553094pyw.2006.05.24.04.01.40; Wed, 24 May 2006 04:01:41 -0700 (PDT) From: Artem Kazakov To: FreeBSD Hackers Content-Type: text/plain Date: Wed, 24 May 2006 20:00:49 +0900 Message-Id: <1148468449.1745.27.camel@tyoma.linac.kek.jp> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Subject: tcsh & nss_ldap problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 11:01:52 -0000 Dear All, I don't know if this should go here, point me to the right place. But it looks like a problem (bug?) in tcsh. The story started from this pr: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/77574 While debugging I realized that the problem is because of the way tcsh manages descriptors. So, the problem is: when you use nss_ldap, and it has persistent connections enabled. You type somthing like : $ cd ~ab[tab] At this point a lookup through nss_ldap is made. At the moment descriptors 0,1,2 are free. So when nss_ldap makes a call to socket() it returns 1 (0 is used for logging if I get it right, and 2 is used too then). And as connection stays open the descriptor is still held and descriptor id = 1; So then you issue a command: $ cd ~abc[enter] at this point, tcsh makes call to doio() - as I understand this function should set proper descriptors for pipe, io-redirection etc. And here is the code: doio(t, pipein, pipeout) struct command *t; int *pipein, *pipeout; { .... (void) close(0); (void) dup(OLDSTD); .... (void) close(1); (void) dup(SHOUT); .... (void) close(2); if (flags & F_STDERR) { (void) dup(1); is2atty = is1atty; } else { (void) dup(SHDIAG); is2atty = isdiagatty; .... So, descriptors 1,2,3 were closed and then dup()ed. And after that a lookup through nss_ldap is done again (we issued a command cd ~abc) But it thinks that connection is still alive, and when it calls write() all the data goes to terminal, instead of socket. Which is definitely is not the result we wanted to get. Also shell error output goes to syslog instead of terminal, because descriptor no 2 was dup()ed against SHDIAG which is 0; and 0 descriptor was previosly used by nss_ldap for logging. Ok, what next? Current workaround exists, you just have not to use persistent connections with nss_ldap. But tcsh should be fixed, I suppose. I'm not familiar with tcsh code, so can't do that. Cheers, Artem Kazakov. From owner-freebsd-hackers@FreeBSD.ORG Wed May 24 12:27:02 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 E7DB416A44A for ; Wed, 24 May 2006 12:27:02 +0000 (UTC) (envelope-from dwmalone@maths.tcd.ie) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by mx1.FreeBSD.org (Postfix) with SMTP id 2E1C643D5A for ; Wed, 24 May 2006 12:27:00 +0000 (GMT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie ([134.226.81.10] helo=walton.maths.tcd.ie) by salmon.maths.tcd.ie with SMTP id ; 24 May 2006 13:26:59 +0100 (BST) Date: Wed, 24 May 2006 13:26:59 +0100 From: David Malone To: "gs_stoller@juno.com" Message-ID: <20060524122659.GA64453@walton.maths.tcd.ie> References: <20060523.182218.19235.1026225@webmail29.nyc.untd.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060523.182218.19235.1026225@webmail29.nyc.untd.com> User-Agent: Mutt/1.5.6i Sender: dwmalone@maths.tcd.ie Cc: freebsd-hackers@freebsd.org Subject: Re: The 'ln -s' command X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 12:27:03 -0000 On Wed, May 24, 2006 at 01:21:59AM +0000, gs_stoller@juno.com wrote: > I tried the 'ln -s' command in bothe 4.3 & 4.7 in a situation > where it should fail and it did, but it still had a return/exit > code of 0 , I think it should have been nonzero. I tried 'ln -s > a b' where the file b existed (and was a directory) In this case, ln should make a link called b/a pointing to a. ln probably successfully did this and returned 0. The behaviour is documented in the ln man page I think. David. From owner-freebsd-hackers@FreeBSD.ORG Wed May 24 12:51:54 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 A3DFA16A498 for ; Wed, 24 May 2006 12:51:54 +0000 (UTC) (envelope-from jhein@timing.com) Received: from Daffy.timing.com (w.timing.com [206.168.13.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 37B8743D6E for ; Wed, 24 May 2006 12:51:46 +0000 (GMT) (envelope-from jhein@timing.com) Received: from gromit.timing.com (gromit.timing.com [206.168.13.209]) by Daffy.timing.com (8.13.1/8.12.8) with ESMTP id k4OCpjEV012982; Wed, 24 May 2006 06:51:45 -0600 (MDT) (envelope-from jhein@timing.com) Received: from gromit.timing.com (localhost [127.0.0.1]) by gromit.timing.com (8.13.6/8.13.4) with ESMTP id k4OCpjDJ024602; Wed, 24 May 2006 06:51:45 -0600 (MDT) (envelope-from jhein@gromit.timing.com) Received: (from jhein@localhost) by gromit.timing.com (8.13.6/8.13.6/Submit) id k4OCpjHm024599; Wed, 24 May 2006 06:51:45 -0600 (MDT) (envelope-from jhein) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17524.22241.137972.599803@gromit.timing.com> Date: Wed, 24 May 2006 06:51:45 -0600 From: John E Hein To: Artem Kazakov In-Reply-To: <1148468449.1745.27.camel@tyoma.linac.kek.jp> References: <1148468449.1745.27.camel@tyoma.linac.kek.jp> X-Mailer: VM 7.19 under Emacs 21.3.1 X-Virus-Scanned: ClamAV version 0.87.1, clamav-milter version 0.87 on Daffy.timing.com X-Virus-Status: Clean Cc: FreeBSD Hackers Subject: Re: tcsh & nss_ldap problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 12:52:04 -0000 Artem Kazakov wrote at 20:00 +0900 on May 24, 2006: > I don't know if this should go here, point me to the right place. > But it looks like a problem (bug?) in tcsh. That report and the link to the PR should be plenty of information to ship off to: Tcsh-Bugs@mx.gw.com (see also http://mx.gw.com/mailman/listinfo/tcsh-bugs) From owner-freebsd-hackers@FreeBSD.ORG Wed May 24 13:13: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 C26CE16A428 for ; Wed, 24 May 2006 13:13:15 +0000 (UTC) (envelope-from fierykylin@gmail.com) Received: from wx-out-0102.google.com (wx-out-0102.google.com [66.249.82.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3BF9C43D4C for ; Wed, 24 May 2006 13:13:13 +0000 (GMT) (envelope-from fierykylin@gmail.com) Received: by wx-out-0102.google.com with SMTP id i30so977098wxd for ; Wed, 24 May 2006 06:13:13 -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=twgwMoFaIqwwTLcQjCISYJA6IncvDWSRdKI4KynPp7IFQ7vJ/MzKJ1TTI2mpESTAJ2BFy8kUfOvWZrSbfnw4jaqx+wm6NrKNPrYRQMJdBxbs9UbIeMzhc3k4pNeKYuZJ48bQsDO0Q7aoDJIZVlkMe/s7T5v+GpjXRr1MI0pgjJA= Received: by 10.70.126.6 with SMTP id y6mr7694478wxc; Wed, 24 May 2006 06:13:13 -0700 (PDT) Received: by 10.70.43.11 with HTTP; Wed, 24 May 2006 06:13:13 -0700 (PDT) Message-ID: <87ab37ab0605240613n594c566q844b754043c2c10@mail.gmail.com> Date: Wed, 24 May 2006 21:13:13 +0800 From: "william wallace" Sender: fierykylin@gmail.com To: "John-Mark Gurney" , "william wallace" , "Scott Long" , imp@bsdimp.com, "freebsd-hackers@freebsd.org" In-Reply-To: <20060524075946.GE49081@funkthat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <87ab37ab0605210108w127a235bue281428f52bbc784@mail.gmail.com> <20060521.114807.74702188.imp@bsdimp.com> <87ab37ab0605212328ue7c70fcu49c5fec8921ae229@mail.gmail.com> <20060522.005010.104089663.imp@bsdimp.com> <87ab37ab0605221816y6cca5387sc43fa1e1116f55cc@mail.gmail.com> <44729B81.8010909@samsco.org> <87ab37ab0605240048g224218a5s87cfe1b1ed5cc8c9@mail.gmail.com> <20060524075946.GE49081@funkthat.com> X-Google-Sender-Auth: 2f4e6681307e6257 Cc: 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: Wed, 24 May 2006 13:13:15 -0000 roger really good tips :) and so far as i know , the PCI configure space is accessed by pci_read_config,and so on the PCI IO space is accessed by the PCI memory space is accessed by bus_space_read_1 and so on am i right sir? On 5/24/06, John-Mark Gurney wrote: > william wallace wrote this message on Wed, May 24, 2006 at 15:48 +0800: > > IN static device_method_t pci_methods[] =3D { > > what is the freeBSD's magic to connect pci_read_config_method wtih > > PCI_READ_CONFIG? awk script?and so on? > > which > > DEVMETHOD(pci_read_config, pci_read_config_method), in pci.c > > command =3D PCI_READ_CONFIG(dev, child, PCIR_COMMAND, 2); in > > pci_enable_io_method in pci.c > > > > and what if i create a new method in pci method interface ? > > such as DEVMETHOD(pci_have_rest , pci_have_rest_method) > > what else should i do when i want to use PCI_HAVE_REST(dev ) point to > > pci_have_rest_method > > These are handled by the _if.m files... look at sys/dev/pci/pci_if.m... > There is an awk script in sys/tools/makeobjops.awk that converts the > _if.m to the appropriate .h and .c files... > > Please read: > http://www.freebsd.org/doc/en_US.ISO8859-1/books/arch-handbook/kernel-obj= ects-using.html > http://www.freebsd.org/doc/en_US.ISO8859-1/books/arch-handbook/newbus-ove= rview.html > > The device methods are implemented using kobj... > > > On 5/23/06, Scott Long wrote: > > >william wallace wrote: > > > > > >[...] > > > > > >> MSI: > > >> I've bantered around different suggestions for an API that will supp= ort > > >> this. The basic thing that a driver needs from this is to know > > >> exactly how many message interrupt vectors are available to it. It > > >> can't just register vectors and handlers blindly since the purpose o= f > > >> MSI is to assign special meanings to each vector and allow the drive= r to > > >> handle each one in specifically. > > > > > >[...] > > > > > >I just wanted to briefly say that an MSI implementation has been done > > >recently, and that it should start getting wider circulation and revie= w > > >soon. That's not to say that more work and design can't be done in th= is > > >area, but we should probably wait a bit and see what has been done > > >already. > > -- > John-Mark Gurney Voice: +1 415 225 5579 > > "All that I will do, has been done, All that I have, has not." > --=20 we who r about to die,salute u! From owner-freebsd-hackers@FreeBSD.ORG Wed May 24 14:14: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 5A7C116A43D for ; Wed, 24 May 2006 14:14:32 +0000 (UTC) (envelope-from listas@itm.net.br) Received: from venom.itm.net.br (venom.itm.net.br [201.30.187.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id F0E5543D76 for ; Wed, 24 May 2006 14:14:23 +0000 (GMT) (envelope-from listas@itm.net.br) Received: (qmail 81550 invoked by uid 89); 24 May 2006 14:13:01 -0000 Received: by simscan 1.2.0 ppid: 81535, pid: 81536, t: 2.4146s scanners: attach: 1.2.0 clamav: 0.88/m:38/d:1425 spam: 3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on venom.itm.net.br X-Spam-Level: X-Spam-Status: No, score=-2.6 required=6.0 tests=BAYES_00 autolearn=ham version=3.1.0 Received: from unknown (HELO ironman) (200.223.172.71) by venom.itm.net.br with SMTP; 24 May 2006 14:12:58 -0000 Message-ID: <009401c67f3c$57e5ef90$47acdfc8@ironman> From: "Cesar" To: Date: Wed, 24 May 2006 11:14:17 -0300 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 Subject: USB Flash disk on FreeBSD 6 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 14:14:32 -0000 Hi, Anyone know if FreeBSD 6.x have problems with usb flash disks? I have a mini-freebsd build running on some flash disks with FreeBSD 5.3, last week I changed to FreeBSD 6.0 and my flash disks started to show a lot of errors. I tried the 6.1 STABLE too, but no lucky. Flash Disk Info: da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-2 device da0: 40.000MB/s transfers da0: 246MB (504832 512 byte sectors: 64H 32S/T 246C) Errors on FreeBSD 6.x g_vfs_done():da0a[WRITE(offset=65536, length=2048)]error = 5 g_vfs_done():da0a[WRITE(offset=147456, length=8192)]error = 5 g_vfs_done():da0a[WRITE(offset=3055616, length=1024)]error = 5 g_vfs_done():da0a[WRITE(offset=3576832, length=1024)]error = 5 g_vfs_done():da0a[WRITE(offset=94797824, length=8192)]error = 5 g_vfs_done():da0a[WRITE(offset=94806016, length=8192)]error = 5 [...] Any idea? PS. I have more then 20 flash disks running fbsd 5.3 without problems. I installed like 5 flash disks with fbsd 6x and all 5 show those errors. Thanks in advance. From owner-freebsd-hackers@FreeBSD.ORG Wed May 24 14:20: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 7C0E616A4E4 for ; Wed, 24 May 2006 14:20:40 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8042743D91 for ; Wed, 24 May 2006 14:20:39 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k4OEKWgD091853; Wed, 24 May 2006 10:20:32 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Wed, 24 May 2006 09:55:19 -0400 User-Agent: KMail/1.9.1 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200605240955.19370.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1479/Wed May 24 01:17:23 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: "R. Tyler Ballance" Subject: Re: Kernel call stack for dummies. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 14:20:40 -0000 On Wednesday 24 May 2006 03:05, R. Tyler Ballance wrote: > I've started the uphill battle to port FreeBSD's kernel to run > "paravirtualized" (<--note the smart sounding vocabulary) on top of > the L4/Iguana OS (Iguana is a very barebones OS developed by NICTA: > http://www.ertos.nicta.com.au/software/kenge/iguana-project/latest/) >=20 > On of the first steps is basically porting the lowest of low kernel > calls such as those in sys/i386 sys/arm and sys/amd64 for example > into sys/iguana to talk to iguana instead of actual hardware. >=20 > One of the things I need to figure out is the order in which kernel > calls are made on boot, so I can go through and reimplement them one > by one (in order to spend as little time as possible going back and > fixing other problems of mine), as suggested by Ben Leslie at NICTA. > Is there a good overview of what's happening directly after boot in > terms of the procedure in which functions are called right after the > bootloader finishes it business? The boot loader hands off execution to locore.S. The entry point in there sets up various things and then calls init_() (such as init_i386() in sys/i386/i386/machdep.c). When init_i386() returns, locore then calls mi_startup() which runs through all of the SYSINITs and never returns (the last SYSINIT kicks off the swapper kthread using the boot stack). =2D-=20 John Baldwin =A0<>< =A0http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =A0=3D =A0http://www.FreeBSD.org From owner-freebsd-hackers@FreeBSD.ORG Wed May 24 15:31:29 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 AE14A16A95A for ; Wed, 24 May 2006 15:31:29 +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 585BF43D55 for ; Wed, 24 May 2006 15:31:25 +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 k4OFSHpL011277; Wed, 24 May 2006 09:28:17 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Wed, 24 May 2006 09:28:16 -0600 (MDT) Message-Id: <20060524.092816.85403996.imp@bsdimp.com> To: avalonwallace@gmail.com From: Warner Losh In-Reply-To: <87ab37ab0605240613n594c566q844b754043c2c10@mail.gmail.com> References: <87ab37ab0605240048g224218a5s87cfe1b1ed5cc8c9@mail.gmail.com> <20060524075946.GE49081@funkthat.com> <87ab37ab0605240613n594c566q844b754043c2c10@mail.gmail.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, gurney_j@resnet.uoregon.edu, scottl@samsco.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: Wed, 24 May 2006 15:31:33 -0000 > the PCI configure space is accessed by pci_read_config,and so on > the PCI IO space is accessed by > the PCI memory space is accessed by bus_space_read_1 and so on > am i right sir? Yes. Warner From owner-freebsd-hackers@FreeBSD.ORG Wed May 24 15:32: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 784A016A9B4 for ; Wed, 24 May 2006 15:32:04 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 36D8643D55 for ; Wed, 24 May 2006 15:32:01 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (5qj2ooavyzj7q3j5@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.4/8.13.3) with ESMTP id k4OFVucC081124; Wed, 24 May 2006 08:31:56 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.4/8.13.3/Submit) id k4OFVrTU081112; Wed, 24 May 2006 08:31:53 -0700 (PDT) (envelope-from jmg) Date: Wed, 24 May 2006 08:31:53 -0700 From: John-Mark Gurney To: william wallace Message-ID: <20060524153153.GF49081@funkthat.com> Mail-Followup-To: william wallace , Scott Long , imp@bsdimp.com, "freebsd-hackers@freebsd.org" References: <87ab37ab0605210108w127a235bue281428f52bbc784@mail.gmail.com> <20060521.114807.74702188.imp@bsdimp.com> <87ab37ab0605212328ue7c70fcu49c5fec8921ae229@mail.gmail.com> <20060522.005010.104089663.imp@bsdimp.com> <87ab37ab0605221816y6cca5387sc43fa1e1116f55cc@mail.gmail.com> <44729B81.8010909@samsco.org> <87ab37ab0605240048g224218a5s87cfe1b1ed5cc8c9@mail.gmail.com> <20060524075946.GE49081@funkthat.com> <87ab37ab0605240613n594c566q844b754043c2c10@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87ab37ab0605240613n594c566q844b754043c2c10@mail.gmail.com> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: "freebsd-hackers@freebsd.org" , Scott Long Subject: Re: misc questions about the device&driver arch X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 15:32:08 -0000 william wallace wrote this message on Wed, May 24, 2006 at 21:13 +0800: > roger really good tips :) > and so far as i know , > the PCI configure space is accessed by pci_read_config,and so on > the PCI IO space is accessed by bus_space_read_1 and friends... > the PCI memory space is accessed by bus_space_read_1 and so on > am i right sir? Yep... > On 5/24/06, John-Mark Gurney wrote: > >william wallace wrote this message on Wed, May 24, 2006 at 15:48 +0800: > >> IN static device_method_t pci_methods[] = { > >> what is the freeBSD's magic to connect pci_read_config_method wtih > >> PCI_READ_CONFIG? awk script?and so on? > >> which > >> DEVMETHOD(pci_read_config, pci_read_config_method), in pci.c > >> command = PCI_READ_CONFIG(dev, child, PCIR_COMMAND, 2); in > >> pci_enable_io_method in pci.c > >> > >> and what if i create a new method in pci method interface ? > >> such as DEVMETHOD(pci_have_rest , pci_have_rest_method) > >> what else should i do when i want to use PCI_HAVE_REST(dev ) point to > >> pci_have_rest_method > > > >These are handled by the _if.m files... look at sys/dev/pci/pci_if.m... > >There is an awk script in sys/tools/makeobjops.awk that converts the > >_if.m to the appropriate .h and .c files... > > > >Please read: > >http://www.freebsd.org/doc/en_US.ISO8859-1/books/arch-handbook/kernel-objects-using.html > >http://www.freebsd.org/doc/en_US.ISO8859-1/books/arch-handbook/newbus-overview.html > > > >The device methods are implemented using kobj... > > > >> On 5/23/06, Scott Long wrote: > >> >william wallace wrote: > >> > > >> >[...] > >> > > >> >> MSI: > >> >> I've bantered around different suggestions for an API that will > >support > >> >> this. The basic thing that a driver needs from this is to know > >> >> exactly how many message interrupt vectors are available to it. It > >> >> can't just register vectors and handlers blindly since the purpose of > >> >> MSI is to assign special meanings to each vector and allow the driver > >to > >> >> handle each one in specifically. > >> > > >> >[...] > >> > > >> >I just wanted to briefly say that an MSI implementation has been done > >> >recently, and that it should start getting wider circulation and review > >> >soon. That's not to say that more work and design can't be done in this > >> >area, but we should probably wait a bit and see what has been done > >> >already. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-hackers@FreeBSD.ORG Wed May 24 16:55:05 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 CACF316A7A1 for ; Wed, 24 May 2006 16:55:05 +0000 (UTC) (envelope-from mehmetpala@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 EF00C43D53 for ; Wed, 24 May 2006 16:55:04 +0000 (GMT) (envelope-from mehmetpala@gmail.com) Received: by nz-out-0102.google.com with SMTP id n1so74254nzf for ; Wed, 24 May 2006 09:55:04 -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:references; b=jgnjZqfaHZ5caVGy6o2nPJhMDwBwqtl4kFb4kcJ7KpkE2WrmAIcGrQtkmwdIC+WXf+YOW0nMxahPtIxUNWCufFvbHk72RXbLVpGxmNpCOsaR/6KvZEaW49QR9HnhlgN8VQffITCfuN9eqsshyTFnhYnGReghGGa06ygidiGY98U= Received: by 10.65.20.9 with SMTP id x9mr3218459qbi; Wed, 24 May 2006 09:55:04 -0700 (PDT) Received: by 10.65.220.12 with HTTP; Wed, 24 May 2006 09:55:04 -0700 (PDT) Message-ID: <412ec2a30605240955gdc0d65alf4f3b0e94b3a13d6@mail.gmail.com> Date: Wed, 24 May 2006 19:55:04 +0300 From: "Mehmet Pala" To: freebsd-hackers@freebsd.org In-Reply-To: <20060524120039.B07ED16A4A0@hub.freebsd.org> MIME-Version: 1.0 References: <20060524120039.B07ED16A4A0@hub.freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: freebsd-hackers Digest, Vol 166, Issue 3 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 16:55:05 -0000 *reebsd-hackers-unsubscribe@freebsd.org* From owner-freebsd-hackers@FreeBSD.ORG Wed May 24 17:29:34 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 57C5E16A912 for ; Wed, 24 May 2006 17:29:34 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id DBDD543D70 for ; Wed, 24 May 2006 17:29:29 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id k4OHTPBO041489; Wed, 24 May 2006 12:29:27 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <447497F8.10009@centtech.com> Date: Wed, 24 May 2006 12:29:28 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5.0.2 (X11/20060506) MIME-Version: 1.0 To: Coleman Kane References: <20060424131508.GB23163@pint.candc.home> <444CD48A.4060501@centtech.com> <444CE475.30104@centtech.com> <20060430231621.GA551@pint.candc.home> <44557F34.3020906@centtech.com> <20060501190645.GB4315@odin.ac.hmc.edu> <44565DD2.1020604@centtech.com> <20060501191447.GD4315@odin.ac.hmc.edu> <44565E74.3060801@centtech.com> <20060501192920.GE4315@odin.ac.hmc.edu> <20060501212801.GA2254@pint.candc.home> <44577B56.70704@centtech.com> In-Reply-To: <44577B56.70704@centtech.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1480/Wed May 24 11:45:51 2006 on mh1.centtech.com X-Virus-Status: Clean Cc: hackers@freebsd.org Subject: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 17:29:36 -0000 Eric Anderson wrote: > Coleman Kane wrote: >> On Mon, May 01, 2006 at 12:29:20PM -0700, Brooks Davis wrote: >>> On Mon, May 01, 2006 at 02:16:04PM -0500, Eric Anderson wrote: >>>> Brooks Davis wrote: >>>>> On Mon, May 01, 2006 at 02:13:22PM -0500, Eric Anderson wrote: >>>>>> Brooks Davis wrote: >>>>>>> On Sun, Apr 30, 2006 at 10:23:32PM -0500, Eric Anderson wrote: >>>>>>>> Coleman Kane wrote: >>>>>>>>> On Mon, Apr 24, 2006 at 09:45:09AM -0500, Eric Anderson wrote: >>>>>>>>>> Eric Anderson wrote: >>>>>>>>>> >>>>>>>>>> Actually, some other things got changed somewhere in the >>>>>>>>>> history, that broke some things and assumptions I was making. >>>>>>>>>> This patch has them fixed, and I've tested it with all the >>>>>>>>>> different options: >>>>>>>>>> >>>>>>>>>> http://www.googlebit.com/freebsd/patches/rc_fancy.patch-9 >>>>>>>>>> >>>>>>>>>> It's missing the defaults/rc.conf diffs, but you should >>>>>>>>>> already know those. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Eric >>>>>>>>>> >>>>>>>>> I have a new patch (to 7-CURRENT) of the "fancy_rc" updates. >>>>>>>>> >>>>>>>>> This allows the use of: >>>>>>>>> rc_fancy="YES" ---> Turns on fancy reporting (w/o color) >>>>>>>>> rc_fancy_color="YES" ---> Turns on fancy reporting (w/ >>>>>>>>> color), needs >>>>>>>>> rc_fancy="YES" >>>>>>>>> rc_fancy_colour="YES" ---> Same as above for you on the other >>>>>>>>> side of >>>>>>>>> the pond. >>>>>>>>> rc_fancy_verbose="YES" --> Turn on more verbose activity >>>>>>>>> messages. >>>>>>>>> This will cause what appear to be "false >>>>>>>>> positives", where an unused service is >>>>>>>>> "OK" instead of "SKIP". >>>>>>>>> >>>>>>>>> You can also customize the colors, the widths of the message >>>>>>>>> brackets (e.g. [ OK ] vs. [ OK ]), the screen width, and >>>>>>>>> the contents of the message (OK versus GOOD versus BUENO). >>>>>>>>> >>>>>>>>> Also, we have the following message combinations: >>>>>>>>> OK ---> Universal good message >>>>>>>>> SKIP,SKIPPED ---> Two methods for conveying the same idea? >>>>>>>>> ERROR,FAILED ---> Ditto above, for failure cases >>>>>>>>> >>>>>>>>> Should we just have 3 different messages, rather than 5 messages >>>>>>>>> in 3 categories? >>>>>>>> Yes, that's something that started with my first patch, and >>>>>>>> never got ironed out. I think it should be: >>>>>>>> OK >>>>>>>> SKIPPED >>>>>>>> FAILED >>>>>>>> and possibly also: >>>>>>>> ERROR >>>>>>>> >>>>>>>> The difference between FAILED and ERROR would be that FAILED >>>>>>>> means the service did not start at all, and ERROR means it >>>>>>>> started but had some kind of error response. >>>>>>> FAILED vs ERROR seems confusing. I'd be inclined toward WARNING vs >>>>>>> FAILED or ERROR. >>>>>> True, however I still see a difference between FAILED and WARNING. >>>>>> For instance, as an example: a FAILED RAID is different than a >>>>>> RAID with a WARNING. >>>>> For that level of detail, the ability to provide additional output >>>>> seems >>>>> like the appropriate solution. >>>> Yes, true, but you'd still want to show something (I would think) in >>>> the [ ]'s to keep it consistent. >>> My feeling is that anything short of complete success should report >>> WARNING and a message unless it actually totally failed in which case >>> FAILED or ERROR (I slightly perfer ERROR) should be used. >>> >>> -- Brooks >> >> What situations are we determining get flagged as ERROR versus FAILED? >> Is FAILED considered to be 'I was able to run the command, but it >> returned an error code', versus ERROR being 'I could not even run the >> command!' like bad path, file not found, etc... >> >> This point still kind of confuses me (and needs to be well defined). I >> am an advocate of having three distinct messages: OK, SKIPPED, ERROR. >> And not even bothering with the different types of ERROR/FAILED other >> than having extra reporting output. > > I'm ok with just OK, SKIPPED, ERROR.. If there's ever a need for more, > it's easy to add it. > > Eric > > > Is this still planned to make it into -CURRENT? Thanks, Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-hackers@FreeBSD.ORG Wed May 24 18:17:53 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 8A3AB16AAE9 for ; Wed, 24 May 2006 18:17:53 +0000 (UTC) (envelope-from rick@kiwi-computer.com) Received: from kiwi-computer.com (megan.kiwi-computer.com [63.224.10.3]) by mx1.FreeBSD.org (Postfix) with SMTP id B9DF443D58 for ; Wed, 24 May 2006 18:17:52 +0000 (GMT) (envelope-from rick@kiwi-computer.com) Received: (qmail 93744 invoked by uid 2001); 24 May 2006 18:17:51 -0000 Date: Wed, 24 May 2006 13:17:51 -0500 From: "Rick C. Petty" To: "Ricardo A. Reis" Message-ID: <20060524181751.GA92607@megan.kiwi-computer.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: "freebsd-hackers@freebsd.org" Subject: Re: kldfind, updated for version 0.56 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 18:17:55 -0000 On Sun, May 21, 2006 at 02:28:29PM -0300, Ricardo A. Reis wrote: > > First about exit codes, when program is executed without options, > how this must return ? > kldunload and kldload not return the same exit codes, > > [ricardo@myfreebsd:~/kldfind] # kldload > usage: kldload [-v] file ... > zsh: 48524 exit 1 kldload > > [ricardo@myfreebsd:~/kldfind] # kldunload > usage: kldunload [-fv] -i id ... > kldunload [-fv] [-n] name ... > zsh: 48539 exit 64 kldunload > > [ricardo@myfreebsd:~/kldfind] # ./kldfind-v056 > usage: kldfind-v056 [-chqsv] ... > > In kldfind i return 0 See the manpage for sysexits(3). Both should return EX_USAGE (64) in this case. You should only return EX_OK (0) if the command was successful. If you're spitting out usage text, return EX_USAGE. Also by glancing at your usage string, it's not apparent that specifying no options is an invalid usage. Without reading through your script, I'm not sure which options are optional or which are required. I read "[-chqsv]" meaning use any of those options in any combination, or no options whatsoever. Consider something like either: kldfind -c | -s | -h [-qv] modulename ... or a multi-line usage (e.g. something like bsdlabel(1)): kldfind [-qv] -c category ... kldfind [-qv] -s string ... kldfind [-qv] -h Personally, I'd prefer clarity over brevity. Just my 3 cents, -- Rick C. Petty From owner-freebsd-hackers@FreeBSD.ORG Wed May 24 19:53: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 2D56616AA1E for ; Wed, 24 May 2006 19:53:40 +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 7881B43D49 for ; Wed, 24 May 2006 19:53:39 +0000 (GMT) (envelope-from asmrookie@gmail.com) Received: by wx-out-0102.google.com with SMTP id i31so1312752wxd for ; Wed, 24 May 2006 12:53:38 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=hQsLzGz31knReA7saadsTJ4aBlAU9qz/WHdJ5jF50P76b0mvwP0VNIG8SGIO1H3g7tCerFqm0O3nwlTK5mT3aY7hRLuVDf3j8tySqLCns4s8U+dZDCiNEWo4tWgYnwqMOXRl5UsIWpvcq/m3MmDNsPyN4tUGrtsUxYXsvf9XQPc= Received: by 10.70.97.12 with SMTP id u12mr8174522wxb; Wed, 24 May 2006 12:53:38 -0700 (PDT) Received: by 10.70.38.10 with HTTP; Wed, 24 May 2006 12:53:38 -0700 (PDT) Message-ID: <3bbf2fe10605241253v6cb36c1fr8e20a09405606898@mail.gmail.com> Date: Wed, 24 May 2006 21:53:38 +0200 From: "Attilio Rao" To: "R. Tyler Ballance" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64 Content-Disposition: inline References: Cc: freebsd-hackers@freebsd.org Subject: Re: Kernel call stack for dummies. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rookie@gufi.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 19:53:45 -0000 MjAwNi81LzI0LCBSLiBUeWxlciBCYWxsYW5jZSA8dHlsZXJAdGFtdS5lZHU+Ogo+IC0tLS0tQkVH SU4gUEdQIFNJR05FRCBNRVNTQUdFLS0tLS0KPiBIYXNoOiBTSEExCj4KPiBJJ3ZlIHN0YXJ0ZWQg dGhlIHVwaGlsbCBiYXR0bGUgdG8gcG9ydCBGcmVlQlNEJ3Mga2VybmVsIHRvIHJ1bgo+ICJwYXJh dmlydHVhbGl6ZWQiICg8LS1ub3RlIHRoZSBzbWFydCBzb3VuZGluZyB2b2NhYnVsYXJ5KSBvbiB0 b3Agb2YKPiB0aGUgTDQvSWd1YW5hIE9TIChJZ3VhbmEgaXMgYSB2ZXJ5IGJhcmVib25lcyBPUyBk ZXZlbG9wZWQgYnkgTklDVEE6Cj4gaHR0cDovL3d3dy5lcnRvcy5uaWN0YS5jb20uYXUvc29mdHdh cmUva2VuZ2UvaWd1YW5hLXByb2plY3QvbGF0ZXN0LykKPgo+IE9uIG9mIHRoZSBmaXJzdCBzdGVw cyBpcyBiYXNpY2FsbHkgcG9ydGluZyB0aGUgbG93ZXN0IG9mIGxvdyBrZXJuZWwKPiBjYWxscyBz dWNoIGFzIHRob3NlIGluIHN5cy9pMzg2IHN5cy9hcm0gYW5kIHN5cy9hbWQ2NCBmb3IgZXhhbXBs ZQo+IGludG8gc3lzL2lndWFuYSB0byB0YWxrIHRvIGlndWFuYSBpbnN0ZWFkIG9mIGFjdHVhbCBo YXJkd2FyZS4KPgo+IE9uZSBvZiB0aGUgdGhpbmdzIEkgbmVlZCB0byBmaWd1cmUgb3V0IGlzIHRo ZSBvcmRlciBpbiB3aGljaCBrZXJuZWwKPiBjYWxscyBhcmUgbWFkZSBvbiBib290LCBzbyBJIGNh biBnbyB0aHJvdWdoIGFuZCByZWltcGxlbWVudCB0aGVtIG9uZQo+IGJ5IG9uZSAoaW4gb3JkZXIg dG8gc3BlbmQgYXMgbGl0dGxlIHRpbWUgYXMgcG9zc2libGUgZ29pbmcgYmFjayBhbmQKPiBmaXhp bmcgb3RoZXIgcHJvYmxlbXMgb2YgbWluZSksIGFzIHN1Z2dlc3RlZCBieSBCZW4gTGVzbGllIGF0 IE5JQ1RBLgo+IElzIHRoZXJlIGEgZ29vZCBvdmVydmlldyBvZiB3aGF0J3MgaGFwcGVuaW5nIGRp cmVjdGx5IGFmdGVyIGJvb3QgaW4KPiB0ZXJtcyBvZiB0aGUgcHJvY2VkdXJlIGluIHdoaWNoIGZ1 bmN0aW9ucyBhcmUgY2FsbGVkIHJpZ2h0IGFmdGVyIHRoZQo+IGJvb3Rsb2FkZXIgZmluaXNoZXMg aXQgYnVzaW5lc3M/CgpJIHRoaW5rIHRoYXQgRnJlZUJTRCBiZWhhdmlvdXIgYWJvdXQgdGhpcyBp cyBub3QgcmVhbGx5IHN1aXRhYmxlIGZvciBhCkw0IGtlcm5lbCBzaW5jZSBpbiB0aGUgZW5kIGFs bCBTWVNJTklUIGZ1bmN0aW9ucyBhcmUgY2FsbGVkIGFuZCBtYXliZQppbXBsZW1lbnRpbmcgYSB3 b3JrcXVldWUgbGlrZSB0aGlzIGlzIG5vdCB0aGUgYmV0dGVyIHNvbHV0aW9uIGZvciB5b3UKYWN0 dWFsbHkuCgpBdHRpbGlvCgotLSAKUGVhY2UgY2FuIG9ubHkgYmUgYWNoaWV2ZWQgYnkgdW5kZXJz dGFuZGluZyAtIEEuIEVpbnN0ZWluCg== From owner-freebsd-hackers@FreeBSD.ORG Thu May 25 02:18:19 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 5AA0C16A421 for ; Thu, 25 May 2006 02:18:19 +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 2F1A043D45 for ; Thu, 25 May 2006 02:18:17 +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 k4P2IAH0012093 for ; Thu, 25 May 2006 09:18:10 +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 k4P2I8FC015606 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 25 May 2006 09:18:09 +0700 From: Bachilo Dmitry Organization: Solink Ltd To: freebsd-hackers@freebsd.org Date: Thu, 25 May 2006 09:18:08 +0700 User-Agent: KMail/1.9.1 References: <009401c67f3c$57e5ef90$47acdfc8@ironman> In-Reply-To: <009401c67f3c$57e5ef90$47acdfc8@ironman> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200605250918.09324.root@solink.ru> Subject: Re: USB Flash disk on FreeBSD 6 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 May 2006 02:18:19 -0000 =F7 =D3=CF=CF=C2=DD=C5=CE=C9=C9 =CF=D4 =F3=D2=C5=C4=C1 24 =CD=C1=D1 2006 21= :14 Cesar =CE=C1=D0=C9=D3=C1=CC(a): > Hi, > > Anyone know if FreeBSD 6.x have problems with usb flash disks? > I have a mini-freebsd build running on some flash disks with FreeBSD > 5.3, last week I changed to FreeBSD 6.0 and my flash disks started to show > a lot of errors. I tried the 6.1 STABLE too, but no lucky. > > Flash Disk Info: > > da0 at umass-sim0 bus 0 target 0 lun 0 > da0: Removable Direct Access SCSI-2 device > da0: 40.000MB/s transfers > da0: 246MB (504832 512 byte sectors: 64H 32S/T 246C) > > Errors on FreeBSD 6.x > g_vfs_done():da0a[WRITE(offset=3D65536, length=3D2048)]error =3D 5 > g_vfs_done():da0a[WRITE(offset=3D147456, length=3D8192)]error =3D 5 > g_vfs_done():da0a[WRITE(offset=3D3055616, length=3D1024)]error =3D 5 > g_vfs_done():da0a[WRITE(offset=3D3576832, length=3D1024)]error =3D 5 > g_vfs_done():da0a[WRITE(offset=3D94797824, length=3D8192)]error =3D 5 > g_vfs_done():da0a[WRITE(offset=3D94806016, length=3D8192)]error =3D 5 > [...] > > Any idea? > > PS. I have more then 20 flash disks running fbsd 5.3 without problems. > I installed like 5 flash disks with fbsd 6x and all 5 show those errors. > > > Thanks in advance. No I've 6.1 and had 6.0 - there were and are no problems. Maybe something = has=20 happened to your USB controller or something? > _______________________________________________ > 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 Thu May 25 01:11:29 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DC29616A423 for ; Thu, 25 May 2006 01:11:29 +0000 (UTC) (envelope-from cokane@ramen.cokane.org) Received: from smtp1.fuse.net (mail-out1.fuse.net [216.68.8.174]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6078743D48 for ; Thu, 25 May 2006 01:11:29 +0000 (GMT) (envelope-from cokane@ramen.cokane.org) Received: from gx5.fuse.net ([66.117.224.249]) by smtp1.fuse.net (InterMail vM.6.01.04.04 201-2131-118-104-20050224) with ESMTP id <20060525011128.ZUWR3018.smtp1.fuse.net@gx5.fuse.net> for ; Wed, 24 May 2006 21:11:28 -0400 Received: from ramen.cokane.org ([66.117.224.249]) by gx5.fuse.net (InterMail vG.1.02.00.02 201-2136-104-102-20041210) with SMTP id <20060525011128.OEZ28402.gx5.fuse.net@ramen.cokane.org> for ; Wed, 24 May 2006 21:11:28 -0400 Received: (qmail 14281 invoked by uid 1001); 25 May 2006 01:12:32 -0000 Date: Thu, 25 May 2006 01:12:32 +0000 From: Coleman Kane To: Eric Anderson Message-ID: <20060525011232.GA14233@ramen.coleyandcheryl> References: <20060430231621.GA551@pint.candc.home> <44557F34.3020906@centtech.com> <20060501190645.GB4315@odin.ac.hmc.edu> <44565DD2.1020604@centtech.com> <20060501191447.GD4315@odin.ac.hmc.edu> <44565E74.3060801@centtech.com> <20060501192920.GE4315@odin.ac.hmc.edu> <20060501212801.GA2254@pint.candc.home> <44577B56.70704@centtech.com> <447497F8.10009@centtech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <447497F8.10009@centtech.com> User-Agent: Mutt/1.4.1i X-Mailman-Approved-At: Thu, 25 May 2006 02:28:48 +0000 Cc: hackers@freebsd.org Subject: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 May 2006 01:11:30 -0000 On Wed, May 24, 2006 at 12:29:28PM -0500, Eric Anderson wrote, and it was proclaimed: > Eric Anderson wrote: > >Coleman Kane wrote: > >>On Mon, May 01, 2006 at 12:29:20PM -0700, Brooks Davis wrote: > >>>On Mon, May 01, 2006 at 02:16:04PM -0500, Eric Anderson wrote: > >>>>Brooks Davis wrote: > >>>>>On Mon, May 01, 2006 at 02:13:22PM -0500, Eric Anderson wrote: > >>>>>>Brooks Davis wrote: > >>>>>>>On Sun, Apr 30, 2006 at 10:23:32PM -0500, Eric Anderson wrote: > >>>>>>>>Coleman Kane wrote: > >>>>>>>>>On Mon, Apr 24, 2006 at 09:45:09AM -0500, Eric Anderson wrote: > >>>>>>>>>>Eric Anderson wrote: > >>>>>>>>>> > >>>>>>>>>>Actually, some other things got changed somewhere in the > >>>>>>>>>>history, that broke some things and assumptions I was making. > >>>>>>>>>>This patch has them fixed, and I've tested it with all the > >>>>>>>>>>different options: > >>>>>>>>>> > >>>>>>>>>>http://www.googlebit.com/freebsd/patches/rc_fancy.patch-9 > >>>>>>>>>> > >>>>>>>>>>It's missing the defaults/rc.conf diffs, but you should > >>>>>>>>>>already know those. > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>>Eric > >>>>>>>>>> > >>>>>>>>>I have a new patch (to 7-CURRENT) of the "fancy_rc" updates. > >>>>>>>>> > >>>>>>>>>This allows the use of: > >>>>>>>>>rc_fancy="YES" ---> Turns on fancy reporting (w/o color) > >>>>>>>>>rc_fancy_color="YES" ---> Turns on fancy reporting (w/ > >>>>>>>>>color), needs > >>>>>>>>> rc_fancy="YES" > >>>>>>>>>rc_fancy_colour="YES" ---> Same as above for you on the other > >>>>>>>>>side of > >>>>>>>>> the pond. > >>>>>>>>>rc_fancy_verbose="YES" --> Turn on more verbose activity > >>>>>>>>>messages. > >>>>>>>>> This will cause what appear to be "false > >>>>>>>>> positives", where an unused service is > >>>>>>>>> "OK" instead of "SKIP". > >>>>>>>>> > >>>>>>>>>You can also customize the colors, the widths of the message > >>>>>>>>>brackets (e.g. [ OK ] vs. [ OK ]), the screen width, and > >>>>>>>>>the contents of the message (OK versus GOOD versus BUENO). > >>>>>>>>> > >>>>>>>>>Also, we have the following message combinations: > >>>>>>>>>OK ---> Universal good message > >>>>>>>>>SKIP,SKIPPED ---> Two methods for conveying the same idea? > >>>>>>>>>ERROR,FAILED ---> Ditto above, for failure cases > >>>>>>>>> > >>>>>>>>>Should we just have 3 different messages, rather than 5 messages > >>>>>>>>>in 3 categories? > >>>>>>>>Yes, that's something that started with my first patch, and > >>>>>>>>never got ironed out. I think it should be: > >>>>>>>>OK > >>>>>>>>SKIPPED > >>>>>>>>FAILED > >>>>>>>>and possibly also: > >>>>>>>>ERROR > >>>>>>>> > >>>>>>>>The difference between FAILED and ERROR would be that FAILED > >>>>>>>>means the service did not start at all, and ERROR means it > >>>>>>>>started but had some kind of error response. > >>>>>>>FAILED vs ERROR seems confusing. I'd be inclined toward WARNING vs > >>>>>>>FAILED or ERROR. > >>>>>>True, however I still see a difference between FAILED and WARNING. > >>>>>>For instance, as an example: a FAILED RAID is different than a > >>>>>>RAID with a WARNING. > >>>>>For that level of detail, the ability to provide additional output > >>>>>seems > >>>>>like the appropriate solution. > >>>>Yes, true, but you'd still want to show something (I would think) in > >>>>the [ ]'s to keep it consistent. > >>>My feeling is that anything short of complete success should report > >>>WARNING and a message unless it actually totally failed in which case > >>>FAILED or ERROR (I slightly perfer ERROR) should be used. > >>> > >>>-- Brooks > >> > >>What situations are we determining get flagged as ERROR versus FAILED? > >>Is FAILED considered to be 'I was able to run the command, but it > >>returned an error code', versus ERROR being 'I could not even run the > >>command!' like bad path, file not found, etc... > >> > >>This point still kind of confuses me (and needs to be well defined). I > >>am an advocate of having three distinct messages: OK, SKIPPED, ERROR. > >>And not even bothering with the different types of ERROR/FAILED other > >>than having extra reporting output. > > > >I'm ok with just OK, SKIPPED, ERROR.. If there's ever a need for more, > >it's easy to add it. > > > >Eric > > > > > > > > > Is this still planned to make it into -CURRENT? > > Thanks, > Eric > > > -- > ------------------------------------------------------------------------ > Eric Anderson Sr. Systems Administrator Centaur Technology > Anything that works is better than anything that doesn't. > ------------------------------------------------------------------------ Yeah, I've been working on it in my spare time. I am investigating some avenues regarding status reporting from the rc scripts to the console. Also been slow getting some hardware together to put cokane.org back up and online. Mostly real-life just got in the way of freebsd for a little while. -- coleman kane From owner-freebsd-hackers@FreeBSD.ORG Thu May 25 12:51:02 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 0CAA716A422 for ; Thu, 25 May 2006 12:51:02 +0000 (UTC) (envelope-from ricardo_bsd@yahoo.com.br) Received: from maritaca.epm.br (mail.dis.epm.br [200.17.25.235]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6F47743D48 for ; Thu, 25 May 2006 12:51:01 +0000 (GMT) (envelope-from ricardo_bsd@yahoo.com.br) Received: from localhost (localhost.localdomain [127.0.0.1]) by maritaca.epm.br (Postfix) with ESMTP id D11EC3B25; Thu, 25 May 2006 09:50:58 -0300 (BRST) Received: from localhost (ricardo.epm.br [172.22.1.166]) by maritaca.epm.br (Postfix) with ESMTP id 1F3283A6C; Thu, 25 May 2006 09:50:53 -0300 (BRST) Date: Thu, 25 May 2006 09:50:53 -0300 To: "Rick C. Petty" From: "Ricardo A. Reis" Organization: UNIFESP Content-Type: text/plain; format=flowed; delsp=yes; charset=utf-8 MIME-Version: 1.0 References: <20060524181751.GA92607@megan.kiwi-computer.com> Content-Transfer-Encoding: Quoted-Printable Message-ID: In-Reply-To: <20060524181751.GA92607@megan.kiwi-computer.com> User-Agent: Opera Mail/9.00 (FreeBSD) UNIFESP-Virus-Scanned: by amavisd-new at dis.epm.br Cc: "freebsd-hackers@freebsd.org" Subject: NOW: version 0.58 (Re: kldfind, updated for version 0.56 ) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 May 2006 12:51:02 -0000 > See the manpage for sysexits(3). Both should return EX_USAGE (64) in = = > this > case. You should only return EX_OK (0) if the command was successful.= = > If > you're spitting out usage text, return EX_USAGE. > or a multi-line usage (e.g. something like bsdlabel(1)): > kldfind [-qv] -c category ... > kldfind [-qv] -s string ... > kldfind -h Hi Rick, Greats for your feedback, i accept your sugestion and update kldfind = and = man for version v058, http://ricardo.epm.br/freebsd/script/kldfind/kldfind-v058. One questions !! What is necessary for include kldfind in HEAD ? -- = Atenciosamente Ricardo A. Reis UNIFESP Unix and Network Adm From owner-freebsd-hackers@FreeBSD.ORG Thu May 25 14:37:27 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 D0B9516A6C0; Thu, 25 May 2006 14:37:27 +0000 (UTC) (envelope-from daichi@freebsd.org) Received: from natial.ongs.co.jp (natial.ongs.co.jp [202.216.232.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E08243D8A; Thu, 25 May 2006 14:37:16 +0000 (GMT) (envelope-from daichi@freebsd.org) Received: from [192.168.1.101] (dullmdaler.ongs.co.jp [202.216.232.62]) by natial.ongs.co.jp (Postfix) with ESMTP id 2355F244C3A; Thu, 25 May 2006 23:37:15 +0900 (JST) Message-ID: <4475C119.1020305@freebsd.org> Date: Thu, 25 May 2006 23:37:13 +0900 From: Daichi GOTO User-Agent: Thunderbird 1.5.0.2 (X11/20060424) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org, freebsd-fs@freebsd.org References: <43E5D052.3020207@freebsd.org> <43E656C7.8040302@freesbie.org> <43E6D5C8.4050405@freebsd.org> <43E71485.5040901@freesbie.org> <43E73330.8070101@freebsd.org> <43EB4C00.2030101@freebsd.org> <4417DD8D.3050201@freebsd.org> <4433CA53.5050000@freebsd.org> <444E13BA.8050902@freebsd.org> In-Reply-To: <444E13BA.8050902@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Thu, 25 May 2006 15:09:21 +0000 Cc: ozawa@ongs.co.jp, dkirhlarov@oilspace.com, Daichi GOTO , freebsd-listen@fabiankeil.de, meianoite@gmail.com, kris@obsecurity.org, Alexander@Leidinger.net, Dario Freni Subject: [ANN] unionfs patchset-12 release X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 May 2006 14:37:32 -0000 Hi Guys! It is my pleasure and honor to announce the availability of the unionfs patchset-12. Patchset-12: For 7-current http://people.freebsd.org/~daichi/unionfs/unionfs-p12.diff For 6.x http://people.freebsd.org/~daichi/unionfs/unionfs6-p12.diff Changes in unionfs-p12.diff - Fixed a bug that responses without lock when share lock is requested with VOP_LOOKUP. - Fixed a bug that leads lock-around panic on FreeBSD 6.x. - others, misc bug fixes The documents of those unionfs patches: http://people.freebsd.org/~daichi/unionfs/ (English) http://people.freebsd.org/~daichi/unionfs/index-ja.html (Japanese) Guys taking some panic troubles with p11, please try the p12 :) We think that p12 is better stable than p11. Thanks -- Daichi GOTO, http://people.freebsd.org/~daichi From owner-freebsd-hackers@FreeBSD.ORG Thu May 25 15:17: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 3373116A716 for ; Thu, 25 May 2006 15:17:00 +0000 (UTC) (envelope-from oxy@field.hu) Received: from green.field.hu (green.field.hu [217.20.130.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8AD1143D6A for ; Thu, 25 May 2006 15:16:59 +0000 (GMT) (envelope-from oxy@field.hu) Received: from localhost (green.field.hu [217.20.130.28]) by green.field.hu (Postfix) with ESMTP id 05258575C1 for ; Thu, 25 May 2006 17:16:52 +0200 (CEST) X-Virus-Scanned: by Amavisd-new (Spamassassin+Razor2+Pyzor+DCC+Bayes db, Clamd Antivirus) at field.hu Received: from green.field.hu ([217.20.130.28]) by localhost (green.field.hu [217.20.130.28]) (amavisd-new, port 10024) with ESMTP id ENhCeKF5mARY for ; Thu, 25 May 2006 17:16:51 +0200 (CEST) Received: from oxy (dsl195-38-115-248.pool.tvnet.hu [195.38.115.248]) by green.field.hu (Postfix) with ESMTP id BF866564A4 for ; Thu, 25 May 2006 17:16:51 +0200 (CEST) Message-ID: <001401c6800e$4376e280$0201a8c0@oxy> From: "OxY" To: Date: Thu, 25 May 2006 17:16:57 +0200 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: setting up a serial console.. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 May 2006 15:17:04 -0000 hi! i have a simple question, but i didn't found the answer. after i set console=3Dcomconsole in the /boot/loader.conf and rebooted every output has been sent to the serial console, it's normal... but! what if anything goes wrong, serial console not working, box cannot = boot up.. how can i change the comconsole setting back to vidconsole? is it possible? thx! From owner-freebsd-hackers@FreeBSD.ORG Thu May 25 18: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 460B616A994 for ; Thu, 25 May 2006 18:39:42 +0000 (UTC) (envelope-from thierry@herbelot.com) Received: from smtp1-g19.free.fr (smtp1-g19.free.fr [212.27.42.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9EBB243D5C for ; Thu, 25 May 2006 18:39:41 +0000 (GMT) (envelope-from thierry@herbelot.com) Received: from herbelot.dyndns.org (bne75-4-82-227-159-103.fbx.proxad.net [82.227.159.103]) by smtp1-g19.free.fr (Postfix) with ESMTP id AB6A99AD3D for ; Thu, 25 May 2006 20:39:40 +0200 (CEST) Received: from diversion.herbelot.nom (diversion.herbelot.nom [192.168.2.6]) by herbelot.dyndns.org (8.13.3/8.13.3) with ESMTP id k4PIdSJw030742; Thu, 25 May 2006 20:39:29 +0200 (CEST) From: Thierry Herbelot To: freebsd-hackers@freebsd.org Date: Thu, 25 May 2006 20:39:21 +0200 User-Agent: KMail/1.9.1 References: <001401c6800e$4376e280$0201a8c0@oxy> In-Reply-To: <001401c6800e$4376e280$0201a8c0@oxy> X-Warning: Windows can lose your files X-Op-Sys: Le FriBi de la mort qui tue X-Org: TfH&Co X-MailScanner: Found to be clean MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 8bit Content-Disposition: inline Message-Id: <200605252039.22658.thierry@herbelot.com> X-Mailman-Approved-At: Thu, 25 May 2006 18:44:13 +0000 Cc: OxY Subject: Re: setting up a serial console.. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: thierry@herbelot.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 May 2006 18:39:51 -0000 Le Thursday 25 May 2006 17:16, OxY a écrit : > hi! > > i have a simple question, but i didn't found the answer. > > after i set console=comconsole in the /boot/loader.conf > and rebooted every output has been sent to the serial console, > it's normal... in /boot/defaults/loader.conf you will find the following line : #console="vidconsole" # A comma separated list of console(s) you can have both a serial console and a video console by setting : console="vidconsole,comconsole" TfH From owner-freebsd-hackers@FreeBSD.ORG Thu May 25 19:05:19 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 A3A5B16ABFA for ; Thu, 25 May 2006 19:05:19 +0000 (UTC) (envelope-from danger@rulez.sk) Received: from virtual.micronet.sk (smtp.micronet.sk [84.16.32.237]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D52C43D5A for ; Thu, 25 May 2006 19:05:18 +0000 (GMT) (envelope-from danger@rulez.sk) Received: from localhost (localhost [127.0.0.1]) by virtual.micronet.sk (Postfix) with ESMTP id A085910E68C; Thu, 25 May 2006 21:06:08 +0200 (CEST) Received: from virtual.micronet.sk ([127.0.0.1]) by localhost (virtual.micronet.sk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 72262-06; Thu, 25 May 2006 21:06:08 +0200 (CEST) Received: from danger.mcrn.sk (danger.mcrn.sk [84.16.37.254]) by virtual.micronet.sk (Postfix) with ESMTP id F2F0D10E678; Thu, 25 May 2006 21:06:07 +0200 (CEST) Date: Thu, 25 May 2006 21:02:01 +0200 From: Daniel Gerzo X-Mailer: The Bat! (v3.62.14) Professional X-Priority: 3 (Normal) Message-ID: <1686462422.20060525210201@rulez.sk> To: "OxY" In-Reply-To: <001401c6800e$4376e280$0201a8c0@oxy> References: <001401c6800e$4376e280$0201a8c0@oxy> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at virtual.micronet.sk Cc: freebsd-hackers@freebsd.org Subject: Re: setting up a serial console.. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Gerzo List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 May 2006 19:05:26 -0000 Hello OxY, Thursday, May 25, 2006, 5:16:57 PM, you wrote: > hi! > i have a simple question, but i didn't found the answer. > after i set console=comconsole in the /boot/loader.conf > and rebooted every output has been sent to the serial console, > it's normal... > but! what if anything goes wrong, serial console not working, box cannot boot up.. > how can i change the comconsole setting back to vidconsole? > is it possible? You should read more Handbook, it's a gread source of information: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/serialconsole-setup.html -- Sincerely, Daniel Gerzo From owner-freebsd-hackers@FreeBSD.ORG Thu May 25 19:19: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 7F32716B642 for ; Thu, 25 May 2006 19:19:35 +0000 (UTC) (envelope-from oxy@field.hu) Received: from green.field.hu (green.field.hu [217.20.130.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0981343D6D for ; Thu, 25 May 2006 19:19:34 +0000 (GMT) (envelope-from oxy@field.hu) Received: from localhost (green.field.hu [217.20.130.28]) by green.field.hu (Postfix) with ESMTP id 9D2CF57571; Thu, 25 May 2006 21:19:34 +0200 (CEST) X-Virus-Scanned: by Amavisd-new (Spamassassin+Razor2+Pyzor+DCC+Bayes db, Clamd Antivirus) at field.hu Received: from green.field.hu ([217.20.130.28]) by localhost (green.field.hu [217.20.130.28]) (amavisd-new, port 10024) with ESMTP id 2Tu+BM-0HTTn; Thu, 25 May 2006 21:19:34 +0200 (CEST) Received: from oxy (dsl195-38-115-248.pool.tvnet.hu [195.38.115.248]) by green.field.hu (Postfix) with ESMTP id 66573564A4; Thu, 25 May 2006 21:19:34 +0200 (CEST) Message-ID: <000c01c68030$2769f9c0$0201a8c0@oxy> From: "OxY" To: , References: <001401c6800e$4376e280$0201a8c0@oxy> <200605252039.22658.thierry@herbelot.com> Date: Thu, 25 May 2006 21:19:33 +0200 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-2"; reply-type=original Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 Cc: Subject: Re: setting up a serial console.. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 May 2006 19:19:45 -0000 ----- Original Message ----- From: "Thierry Herbelot" To: Cc: "OxY" Sent: Thursday, May 25, 2006 8:39 PM Subject: Re: setting up a serial console.. > Le Thursday 25 May 2006 17:16, OxY a écrit : >> hi! >> >> i have a simple question, but i didn't found the answer. >> >> after i set console=comconsole in the /boot/loader.conf >> and rebooted every output has been sent to the serial console, >> it's normal... > > in /boot/defaults/loader.conf you will find the following line : > #console="vidconsole" # A comma separated list of console(s) > > you can have both a serial console and a video console by setting : > console="vidconsole,comconsole" awesome, thx! > > TfH > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@FreeBSD.ORG Thu May 25 20:15:58 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BA94416B094 for ; Thu, 25 May 2006 20:15:58 +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 0D4D943D6A for ; Thu, 25 May 2006 20:15:51 +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 k4PKFo3u004334; Thu, 25 May 2006 15:15:50 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <44761079.4080801@centtech.com> Date: Thu, 25 May 2006 15:15:53 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5.0.2 (X11/20060506) MIME-Version: 1.0 To: Coleman Kane References: <20060430231621.GA551@pint.candc.home> <44557F34.3020906@centtech.com> <20060501190645.GB4315@odin.ac.hmc.edu> <44565DD2.1020604@centtech.com> <20060501191447.GD4315@odin.ac.hmc.edu> <44565E74.3060801@centtech.com> <20060501192920.GE4315@odin.ac.hmc.edu> <20060501212801.GA2254@pint.candc.home> <44577B56.70704@centtech.com> <447497F8.10009@centtech.com> <20060525011232.GA14233@ramen.coleyandcheryl> In-Reply-To: <20060525011232.GA14233@ramen.coleyandcheryl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1484/Thu May 25 10:19:23 2006 on mh2.centtech.com X-Virus-Status: Clean Cc: hackers@freebsd.org Subject: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 May 2006 20:16:10 -0000 Coleman Kane wrote: > On Wed, May 24, 2006 at 12:29:28PM -0500, Eric Anderson wrote, and it was proclaimed: >> Eric Anderson wrote: >>> Coleman Kane wrote: >>>> On Mon, May 01, 2006 at 12:29:20PM -0700, Brooks Davis wrote: >>>>> On Mon, May 01, 2006 at 02:16:04PM -0500, Eric Anderson wrote: >>>>>> Brooks Davis wrote: >>>>>>> On Mon, May 01, 2006 at 02:13:22PM -0500, Eric Anderson wrote: >>>>>>>> Brooks Davis wrote: >>>>>>>>> On Sun, Apr 30, 2006 at 10:23:32PM -0500, Eric Anderson wrote: >>>>>>>>>> Coleman Kane wrote: >>>>>>>>>>> On Mon, Apr 24, 2006 at 09:45:09AM -0500, Eric Anderson wrote: >>>>>>>>>>>> Eric Anderson wrote: >>>>>>>>>>>> >>>>>>>>>>>> Actually, some other things got changed somewhere in the >>>>>>>>>>>> history, that broke some things and assumptions I was making. >>>>>>>>>>>> This patch has them fixed, and I've tested it with all the >>>>>>>>>>>> different options: >>>>>>>>>>>> >>>>>>>>>>>> http://www.googlebit.com/freebsd/patches/rc_fancy.patch-9 >>>>>>>>>>>> >>>>>>>>>>>> It's missing the defaults/rc.conf diffs, but you should >>>>>>>>>>>> already know those. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Eric >>>>>>>>>>>> >>>>>>>>>>> I have a new patch (to 7-CURRENT) of the "fancy_rc" updates. >>>>>>>>>>> >>>>>>>>>>> This allows the use of: >>>>>>>>>>> rc_fancy="YES" ---> Turns on fancy reporting (w/o color) >>>>>>>>>>> rc_fancy_color="YES" ---> Turns on fancy reporting (w/ >>>>>>>>>>> color), needs >>>>>>>>>>> rc_fancy="YES" >>>>>>>>>>> rc_fancy_colour="YES" ---> Same as above for you on the other >>>>>>>>>>> side of >>>>>>>>>>> the pond. >>>>>>>>>>> rc_fancy_verbose="YES" --> Turn on more verbose activity >>>>>>>>>>> messages. >>>>>>>>>>> This will cause what appear to be "false >>>>>>>>>>> positives", where an unused service is >>>>>>>>>>> "OK" instead of "SKIP". >>>>>>>>>>> >>>>>>>>>>> You can also customize the colors, the widths of the message >>>>>>>>>>> brackets (e.g. [ OK ] vs. [ OK ]), the screen width, and >>>>>>>>>>> the contents of the message (OK versus GOOD versus BUENO). >>>>>>>>>>> >>>>>>>>>>> Also, we have the following message combinations: >>>>>>>>>>> OK ---> Universal good message >>>>>>>>>>> SKIP,SKIPPED ---> Two methods for conveying the same idea? >>>>>>>>>>> ERROR,FAILED ---> Ditto above, for failure cases >>>>>>>>>>> >>>>>>>>>>> Should we just have 3 different messages, rather than 5 messages >>>>>>>>>>> in 3 categories? >>>>>>>>>> Yes, that's something that started with my first patch, and >>>>>>>>>> never got ironed out. I think it should be: >>>>>>>>>> OK >>>>>>>>>> SKIPPED >>>>>>>>>> FAILED >>>>>>>>>> and possibly also: >>>>>>>>>> ERROR >>>>>>>>>> >>>>>>>>>> The difference between FAILED and ERROR would be that FAILED >>>>>>>>>> means the service did not start at all, and ERROR means it >>>>>>>>>> started but had some kind of error response. >>>>>>>>> FAILED vs ERROR seems confusing. I'd be inclined toward WARNING vs >>>>>>>>> FAILED or ERROR. >>>>>>>> True, however I still see a difference between FAILED and WARNING. >>>>>>>> For instance, as an example: a FAILED RAID is different than a >>>>>>>> RAID with a WARNING. >>>>>>> For that level of detail, the ability to provide additional output >>>>>>> seems >>>>>>> like the appropriate solution. >>>>>> Yes, true, but you'd still want to show something (I would think) in >>>>>> the [ ]'s to keep it consistent. >>>>> My feeling is that anything short of complete success should report >>>>> WARNING and a message unless it actually totally failed in which case >>>>> FAILED or ERROR (I slightly perfer ERROR) should be used. >>>>> >>>>> -- Brooks >>>> What situations are we determining get flagged as ERROR versus FAILED? >>>> Is FAILED considered to be 'I was able to run the command, but it >>>> returned an error code', versus ERROR being 'I could not even run the >>>> command!' like bad path, file not found, etc... >>>> >>>> This point still kind of confuses me (and needs to be well defined). I >>>> am an advocate of having three distinct messages: OK, SKIPPED, ERROR. >>>> And not even bothering with the different types of ERROR/FAILED other >>>> than having extra reporting output. >>> I'm ok with just OK, SKIPPED, ERROR.. If there's ever a need for more, >>> it's easy to add it. >>> >>> Eric >>> >>> >>> >> >> Is this still planned to make it into -CURRENT? >> >> Thanks, >> Eric >> >> >> -- >> ------------------------------------------------------------------------ >> Eric Anderson Sr. Systems Administrator Centaur Technology >> Anything that works is better than anything that doesn't. >> ------------------------------------------------------------------------ > > Yeah, I've been working on it in my spare time. I am investigating some > avenues regarding status reporting from the rc scripts to the console. > Also been slow getting some hardware together to put cokane.org back up > and online. > > Mostly real-life just got in the way of freebsd for a little while. > > -- > coleman kane Ok - just making sure it had not been forgotten. :) Thanks Coleman! Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-hackers@FreeBSD.ORG Fri May 26 08:51:37 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C6DEC16A433 for ; Fri, 26 May 2006 08:51:37 +0000 (UTC) (envelope-from joseph@randomnetworks.com) Received: from rhyll.com (rhyll.com [70.84.96.250]) by mx1.FreeBSD.org (Postfix) with ESMTP id 763BA43D46 for ; Fri, 26 May 2006 08:51:37 +0000 (GMT) (envelope-from joseph@randomnetworks.com) Received: from localhost (localhost [127.0.0.1]) by rhyll.com (Postfix) with ESMTP id 08DBD2E078 for ; Fri, 26 May 2006 01:51:37 -0700 (PDT) Received: from rhyll.com ([127.0.0.1]) by localhost (sm01.rhyll.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 71524-01 for ; Fri, 26 May 2006 01:51:36 -0700 (PDT) Received: from [192.168.1.100] (adsl-71-142-212-154.dsl.scrm01.pacbell.net [71.142.212.154]) by rhyll.com (Postfix) with ESMTP id E39C42E077 for ; Fri, 26 May 2006 01:51:35 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v750) Content-Transfer-Encoding: 7bit Message-Id: <2079304F-4A16-48A2-A690-CFAB25CC3EA3@randomnetworks.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: hackers@freebsd.org From: Joseph Scott Date: Fri, 26 May 2006 01:51:32 -0700 X-Mailer: Apple Mail (2.750) X-Virus-Scanned: amavisd-new at rhyll.com Cc: Subject: ZFS on FUSE/Linux X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 May 2006 08:51:42 -0000 One of the Google Summer of Code projects is ZFS for FUSE/Linux. More info: Google SoC app: http://code.google.com/soc/opsol/appinfo.html? csaid=1EEF6B271FE5408B Blog: http://zfs-on-fuse.blogspot.com/2006/05/announcing-zfs-on- fuselinux.html Since there is FUSE for FreeBSD now, any chance this can be leveraged to make ZFS work on FreeBSD? -- Joseph Scott http://joseph.randomnetworks.com joseph@randomnetworks.com From owner-freebsd-hackers@FreeBSD.ORG Fri May 26 15:19:54 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 AD2FD16A432 for ; Fri, 26 May 2006 15:19:54 +0000 (UTC) (envelope-from mistry.7@osu.edu) Received: from mail.united-ware.com (am-productions.biz [69.61.164.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0BCFC43D48 for ; Fri, 26 May 2006 15:19:53 +0000 (GMT) (envelope-from mistry.7@osu.edu) Received: from [192.168.1.100] (am-productions.biz [69.61.164.22]) (authenticated bits=0) by mail.united-ware.com (8.13.4/8.13.6) with ESMTP id k4QFLXOc058409 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 26 May 2006 11:21:39 -0400 (EDT) (envelope-from mistry.7@osu.edu) From: Anish Mistry To: freebsd-hackers@freebsd.org Date: Fri, 26 May 2006 11:20:03 -0400 User-Agent: KMail/1.9.1 References: <2079304F-4A16-48A2-A690-CFAB25CC3EA3@randomnetworks.com> In-Reply-To: <2079304F-4A16-48A2-A690-CFAB25CC3EA3@randomnetworks.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3717329.c745cqmgZd"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200605261120.13966.mistry.7@osu.edu> X-Spam-Status: No, score=-5.5 required=5.0 tests=ALL_TRUSTED,BAYES_50, MYFREEBSD2 autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on mail.united-ware.com X-Virus-Scanned: ClamAV 0.88.2/1485/Thu May 25 15:29:05 2006 on mail.united-ware.com X-Virus-Status: Clean Cc: Joseph Scott Subject: Re: ZFS on FUSE/Linux X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 May 2006 15:19:54 -0000 --nextPart3717329.c745cqmgZd Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Friday 26 May 2006 04:51, Joseph Scott wrote: > One of the Google Summer of Code projects is ZFS for FUSE/Linux. > More info: > > Google SoC app: http://code.google.com/soc/opsol/appinfo.html? > csaid=3D1EEF6B271FE5408B > Blog: http://zfs-on-fuse.blogspot.com/2006/05/announcing-zfs-on- > fuselinux.html > > Since there is FUSE for FreeBSD now, any chance this can be > leveraged to make ZFS work on FreeBSD? Probably with some small changes. Some one will just need to step up=20 and port it and create a port skeleton for the ports system. If you=20 need help with the port skeleton, let me know. If you need help with=20 =46USE specific stuff contact Csaba Henk. I'd suggest getting involved=20 early to avoid any annoying Linuxisms creeping in the project. =2D-=20 Anish Mistry --nextPart3717329.c745cqmgZd Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQBEdxytxqA5ziudZT0RAjN/AJ0Z3X3aW4T2JtM4nqFGLjRfFu07DwCgp3zC rfDMhsFs6FlLcc61Kqs4gBc= =Isio -----END PGP SIGNATURE----- --nextPart3717329.c745cqmgZd-- From owner-freebsd-hackers@FreeBSD.ORG Fri May 26 16:00:41 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 C2AAF16A6B2 for ; Fri, 26 May 2006 16:00:41 +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 7F65043D6E for ; Fri, 26 May 2006 16:00:41 +0000 (GMT) (envelope-from dgilbert@daveg.ca) Received: by ox.eicat.ca (Postfix, from userid 66) id 713CB16EC1; Fri, 26 May 2006 12:00:40 -0400 (EDT) Received: by canoe.dclg.ca (Postfix, from userid 101) id B744A4AC2D; Fri, 26 May 2006 12:00:41 -0400 (EDT) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17527.9769.709495.372721@canoe.dclg.ca> Date: Fri, 26 May 2006 12:00:41 -0400 To: freebsd-hackers@freebsd.org X-Mailer: VM 7.17 under 21.4 (patch 19) "Constant Variable" XEmacs Lucid Subject: A2DP (stereo bluetooth) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 May 2006 16:00:46 -0000 Has anyone considered A2DP support on FreeBSD? I did a quick search --- and it would appear that we havn't mastered bluetooth headsets yet, but I thought I'd ask. For the uninitated, A2DP is the "Advanced Audio Distribution Profile" for bluetooth. An example device would be the iPhono (420 and 450) from Bluetake. They are stereo cordless headphones. They also suport the AVRCP (Audio/Video Remote Control Profile) which allows track up/down and play/pause. The same unit also supports headset and handsfree profiles --- and includs a mic --- so they're generally useful. Anyways... The audio quality coming from my Treo is excellent, and I'd like to use them with my laptop, too. 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 Fri May 26 17:57: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 E4B1116A8ED for ; Fri, 26 May 2006 17:57:11 +0000 (UTC) (envelope-from matt@frii.com) Received: from mail.frii.com (phobos02.frii.net [216.17.128.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id DBA5D43D55 for ; Fri, 26 May 2006 17:57:10 +0000 (GMT) (envelope-from matt@frii.com) Received: from elara.frii.com (elara.frii.com [216.17.128.39]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.frii.com (FRII) with ESMTP id 886C0A4A2C for ; Fri, 26 May 2006 11:57:10 -0600 (MDT) Date: Fri, 26 May 2006 11:57:09 -0600 (MDT) From: Matt Ruzicka X-X-Sender: mattr@elara.frii.com To: freebsd-hackers@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: FreeBSD 6.1, crashes and a lack of vmcores X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 May 2006 17:57:15 -0000 For some time now we have been having a lot of trouble with one particular server which is part of a farm of six other largely identical servers. These servers run under extremely high load through a majority of the day and run a mix of postfix, MySQL (running as replication slaves) and custom filter software using MFS partitions. All seven servers are running on identical SuperMicro 6013E-i SuperServers with dual hyper-threading Xeon 2.80GHz CPU's with 2G of RAM. It is not all together uncommon for these machines to crash under extremely high load, but this one server in particular crashes much more frequently. We started with memtest and CPU tests with no errors. As part of our troubleshooting we have replaced (or swapped out with the other servers) every piece of hardware in this box, replaced every cable and cord and moved to different switch and power ports. We've even changed physical locations in our data center. We have so far been unable resolve the more frequent crashes or move the increased instability to another server in an effort to find the cause. We've also disable hyper-threading in the bios and in FreeBSD on this machine since it sounds as if we might see other benefits from this. Also, as a stretch I've moved this box to using the ULE scheduler instead of the standard 4BSD. Really I'm starting to suspect it is haunted (or that I'm sleepdriving into work at night to foil my own progress). These boxes traditionally run FreeBSD 4.11, but in a move of desperation we decided to take this particular machine up to FreeBSD 6.1 in an effort to rule out problems related to OS improvements and to ensure we are running the latest stable version of the different software pieces (and because it seems like the right move in the long term). (We install service software manually by the way, not from ports. MySQL we've installed from their binary distribution for 6.x.) With the upgrade we are still receiving crashes at the same frequency and although the errors appear to report a bit differently they appear to be the same errors. Mostly a combination of "Fatal Trap 12" and "vm_page_fault" errors, though we have seen a couple "Sleeping thread owns a non-sleepable lock" errors. The biggest frustration in this is that of the few dozen crashes we've had I've only been able to get one successful dump. All the other times I get the savecore error message: kernel: kernel dumps on /dev/ad0s1b kernel: Checking for core dump on /dev/ad0s1b... kernel: unable to open bounds file, using 0 kernel: checking for kernel dump on device /dev/ad0s1b kernel: mediasize = 4294967296 kernel: sectorsize = 512 kernel: magic mismatch on last dump header on /dev/ad0s1b kernel: savecore: no dumps found savecore: no dumps found Is there something I am missing to more reliably receive successful dumps? I have plenty of space on /var (22G) and my swap partition is 4G (with 2G of RAM). The one successful dump returned the below gdb information. I've also included the non-commented bits of our kernel config at the very bottom. If anyone has any suggestions on what this dump information indicates I would be very appreciative. Please let me know what other information I can furnish. If I can determine how to get another vmcore I'd be happy to send along another debug as well. Thank you very much in advance. Matt Ruzicka - Senior Systems Administrator Front Range Internet, Inc. matt@frii.net - (970) 212-0728 ---- [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd". Unread portion of the kernel message buffer: vm_page_free: pindex(3255307648), busy(194), PG_BUSY(1), hold(-10260) panic: vm_page_free: freeing busy page cpuid = 0 Uptime: 18h43m26s Dumping 2047 MB (2 chunks) chunk 0: 1MB (159 pages) ... ok chunk 1: 2047MB (524016 pages) 2031 2015 1999 1983 1967 1951 1935 1919 1903 1887 1871 1855 1839 1823 1807 1791 1775 1759 1743 1727 1711 1695 1679 1663 1647 1631 1615 1599 1583 1567 1551 1535 1519 1503 1487 1471 1455 1439 1423 1407 1391 1375 1359 1343 1327 1311 1295 1279 1263 1247 1231 1215 1199 1183 1167 1151 1135 1119 1103 1087 1071 1055 1039 1023 1007 991 975 959 943 927 911 895 879 863 847 831 815 799 783 767 751 735 719 703 687 671 655 639 623 607 591 575 559 543 527 511 495 479 463 447 431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 191 175 159 143 127 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 0xc04b029d in boot (howto=260) at /u/frii/src/FreeBSD-6.1-RELEASE/sys/kern/kern_shutdown.c:402 #2 0xc04b05c5 in panic (fmt=0xc0600359 "vm_page_free: freeing busy page") at /u/frii/src/FreeBSD-6.1-RELEASE/sys/kern/kern_shutdown.c:558 #3 0xc05a2f45 in vm_page_free_toq (m=0xc207d7b0) at /u/frii/src/FreeBSD-6.1-RELEASE/sys/vm/vm_page.c:1025 #4 0xc05a256d in vm_page_free (m=0xc207d7b0) at /u/frii/src/FreeBSD-6.1-RELEASE/sys/vm/vm_page.c:403 #5 0xc059ff39 in vm_object_terminate (object=0xc878b4a4) at /u/frii/src/FreeBSD-6.1-RELEASE/sys/vm/vm_object.c:631 #6 0xc059fe13 in vm_object_deallocate (object=0xc878b4a4) at /u/frii/src/FreeBSD-6.1-RELEASE/sys/vm/vm_object.c:564 #7 0xc059c8fa in vm_map_entry_delete (map=0xc9f7e12c, entry=0xca3e2c38) at /u/frii/src/FreeBSD-6.1-RELEASE/sys/vm/vm_map.c:2207 #8 0xc059cac7 in vm_map_delete (map=0xc9f7e12c, start=3335031932, end=3217031168) at /u/frii/src/FreeBSD-6.1-RELEASE/sys/vm/vm_map.c:2300 #9 0xc059cb28 in vm_map_remove (map=0xc9f7e12c, start=0, end=3217031168) at /u/frii/src/FreeBSD-6.1-RELEASE/sys/vm/vm_map.c:2319 #10 0xc0496fcd in exit1 (td=0xc9d93190, rv=0) at vm_map.h:211 #11 0xc04969b8 in sys_exit (td=0xc9d93190, uap=0x0) at /u/frii/src/FreeBSD-6.1-RELEASE/sys/kern/kern_exit.c:97 #12 0xc05d8917 in syscall (frame= {tf_fs = 59, tf_es = 59, tf_ds = -1079115717, tf_edi = -1077942712, tf_esi = -1077942820, tf_ebp = -1077942876, tf_isp = -387965596, tf_ebx = 672734248, tf_edx = 10, tf_ecx = 672733680, tf_eax = 1, tf_trapno = 12, tf_err = 2, tf_eip = 672673571, tf_cs = 51, tf_eflags = 646, tf_esp = -1077942904, tf_ss = 59}) at /u/frii/src/FreeBSD-6.1-RELEASE/sys/i386/i386/trap.c:981 #13 0xc05c58bf in Xint0x80_syscall () at /u/frii/src/FreeBSD-6.1-RELEASE/sys/i386/i386/exception.s:200 #14 0x00000033 in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb) up 2 #2 0xc04b05c5 in panic (fmt=0xc0600359 "vm_page_free: freeing busy page") at /u/frii/src/FreeBSD-6.1-RELEASE/sys/kern/kern_shutdown.c:558 558 boot(bootopt); (kgdb) p bootopt $1 = 260 (kgdb) p *bootopt Cannot access memory at address 0x104 (kgdb) ---- machine i386 cpu I686_CPU ident MAFILTER-NEW makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols options SCHED_ULE # ULE scheduler options PREEMPTION # Enable kernel thread preemption options INET # InterNETworking 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 NFSCLIENT # Network Filesystem Client options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS # Pseudo-filesystem framework options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options COMPAT_FREEBSD5 # Compatible with FreeBSD5 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. options SMP # Symmetric MultiProcessor Kernel device apic # I/O APIC device eisa device pci device ata device atadisk # ATA disk drives device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device kbdmux # keyboard multiplexer device vga # VGA video card driver device sc device em # Intel PRO/1000 adapter Gigabit Ethernet Card device miibus # MII bus support device fxp # Intel EtherExpress PRO/100B (82557, 82558) device loop # Network loopback device random # Entropy device device ether # Ethernet support device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" From owner-freebsd-hackers@FreeBSD.ORG Fri May 26 18:45: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 59FF816A54A for ; Fri, 26 May 2006 18:45:57 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 56B2043D90 for ; Fri, 26 May 2006 18:45:40 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id BD5DB1A4DB1; Fri, 26 May 2006 11:45:40 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id CAC1651203; Fri, 26 May 2006 14:45:39 -0400 (EDT) Date: Fri, 26 May 2006 14:45:39 -0400 From: Kris Kennaway To: Matt Ruzicka Message-ID: <20060526184539.GA69742@xor.obsecurity.org> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="EeQfGwPcQSOJBaQU" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD 6.1, crashes and a lack of vmcores X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 May 2006 18:46:06 -0000 --EeQfGwPcQSOJBaQU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, May 26, 2006 at 11:57:09AM -0600, Matt Ruzicka wrote: > options SCHED_ULE # ULE scheduler Try with 4BSD; ULE is known to be broken, and it's also usually a performance loss except under minor load. Kris --EeQfGwPcQSOJBaQU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEd0zSWry0BWjoQKURAnFLAKDBQa0+vAEzDt6SBFiMADA/lqKfQQCfRo1S nsCP+/cw5aiP3p5Od/eMDNU= =y8by -----END PGP SIGNATURE----- --EeQfGwPcQSOJBaQU-- From owner-freebsd-hackers@FreeBSD.ORG Fri May 26 18:56:39 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 8340816B2A6 for ; Fri, 26 May 2006 18:56:39 +0000 (UTC) (envelope-from matt@frii.com) Received: from mail.frii.com (phobos02.frii.net [216.17.128.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id CC05943D60 for ; Fri, 26 May 2006 18:56:35 +0000 (GMT) (envelope-from matt@frii.com) Received: from elara.frii.com (elara.frii.com [216.17.128.39]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.frii.com (FRII) with ESMTP id 95BA8A44C0; Fri, 26 May 2006 12:56:35 -0600 (MDT) Date: Fri, 26 May 2006 12:56:35 -0600 (MDT) From: Matt Ruzicka X-X-Sender: mattr@elara.frii.com To: Kris Kennaway In-Reply-To: <20060526184539.GA69742@xor.obsecurity.org> Message-ID: References: <20060526184539.GA69742@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD 6.1, crashes and a lack of vmcores X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 May 2006 18:56:48 -0000 On Fri, 26 May 2006, Kris Kennaway wrote: > Try with 4BSD; ULE is known to be broken, and it's also usually a > performance loss except under minor load. Cool, I'll jump back to 4BSD for completeness, though we were seeing the same behavior for a while before I tried ULE. Thanks for the input. Matt Ruzicka - Senior Systems Administrator Front Range Internet, Inc. matt@frii.net - (970) 212-0728 From owner-freebsd-hackers@FreeBSD.ORG Fri May 26 19:17:29 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 EC2D316A7EE for ; Fri, 26 May 2006 19:17:29 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id A7EBC43D5F for ; Fri, 26 May 2006 19:17:29 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 8CD101A4DAE; Fri, 26 May 2006 12:17:29 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id CDFF851238; Fri, 26 May 2006 15:17:28 -0400 (EDT) Date: Fri, 26 May 2006 15:17:28 -0400 From: Kris Kennaway To: Matt Ruzicka Message-ID: <20060526191728.GA70614@xor.obsecurity.org> References: <20060526184539.GA69742@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="envbJBWh7q8WU6mo" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: freebsd-hackers@freebsd.org, Kris Kennaway Subject: Re: FreeBSD 6.1, crashes and a lack of vmcores X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 May 2006 19:17:31 -0000 --envbJBWh7q8WU6mo Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, May 26, 2006 at 12:56:35PM -0600, Matt Ruzicka wrote: > On Fri, 26 May 2006, Kris Kennaway wrote: >=20 > >Try with 4BSD; ULE is known to be broken, and it's also usually a > >performance loss except under minor load. >=20 > Cool, I'll jump back to 4BSD for completeness, though we were seeing the= =20 > same behavior for a while before I tried ULE. OK, might be unrelated but we need to baseline it. Thanks. Kris --envbJBWh7q8WU6mo Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEd1RIWry0BWjoQKURAhN2AJ0R2S/GoYE8EUSgJP/m5c9TUhjG9wCg2BUa 4H+71ZlD4K0D6YcBhFMVspg= =Js0A -----END PGP SIGNATURE----- --envbJBWh7q8WU6mo-- From owner-freebsd-hackers@FreeBSD.ORG Fri May 26 20:58:54 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 679D516A559 for ; Fri, 26 May 2006 20:58:54 +0000 (UTC) (envelope-from lulf@stud.ntnu.no) Received: from fri.itea.ntnu.no (fri.itea.ntnu.no [129.241.7.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id F30B943D55 for ; Fri, 26 May 2006 20:58:53 +0000 (GMT) (envelope-from lulf@stud.ntnu.no) Received: from localhost (localhost [127.0.0.1]) by fri.itea.ntnu.no (Postfix) with ESMTP id 3963C7F04 for ; Fri, 26 May 2006 22:58:53 +0200 (CEST) Received: from gaupe.stud.ntnu.no (gaupe.stud.ntnu.no [129.241.56.184]) by fri.itea.ntnu.no (Postfix) with ESMTP for ; Fri, 26 May 2006 22:58:53 +0200 (CEST) Received: by gaupe.stud.ntnu.no (Postfix, from userid 2312) id 1560BCFFFA; Fri, 26 May 2006 22:59:18 +0200 (CEST) Date: Fri, 26 May 2006 22:59:18 +0200 From: Ulf Lilleengen To: freebsd-hackers@freebsd.org Message-ID: <20060526205917.GA12965@stud.ntnu.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.9i X-Content-Scanned: with sophos and spamassassin at mailgw.ntnu.no. Subject: Formatting time in kernel X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 May 2006 20:58:55 -0000 Hi, I've been looking through the kernel code the past few days, but I have not found what I'm looking for, which is a way to format "struct timeval" for output in the same matter as the ctime(3) in the standard libc. I keep thinking how this part of the code should not be in kernel because of this, but things will be vastly more complicated if not because of the whole gvinum structure. (This is for use in the gvinum dumpconfig option I'm working on, and I'm not sure if it's really that important showing the creation time, but that's a different discussion). I could ofcourse write my own, but I thought I'd just ask here. Thanks in advance -- Mvh Ulf Lilleengen From owner-freebsd-hackers@FreeBSD.ORG Sat May 27 02:55:21 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 388C216A6DB for ; Sat, 27 May 2006 02:55:21 +0000 (UTC) (envelope-from soralx@cydem.org) Received: from pd3mo1so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id D23DE43D48 for ; Sat, 27 May 2006 02:55:20 +0000 (GMT) (envelope-from soralx@cydem.org) Received: from pd2mr4so.prod.shaw.ca (pd2mr4so-qfe3.prod.shaw.ca [10.0.141.107]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0IZW00CMFLG7LSF0@l-daemon> for freebsd-hackers@freebsd.org; Fri, 26 May 2006 20:55:20 -0600 (MDT) Received: from pn2ml6so.prod.shaw.ca ([10.0.121.150]) by pd2mr4so.prod.shaw.ca (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0IZW00LHXLG791J0@pd2mr4so.prod.shaw.ca> for freebsd-hackers@freebsd.org; Fri, 26 May 2006 20:55:19 -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 <0IZW00BRALG7MM21@l-daemon> for freebsd-hackers@freebsd.org; Fri, 26 May 2006 20:55:19 -0600 (MDT) Date: Fri, 26 May 2006 19:55:19 -0700 From: soralx@cydem.org In-reply-to: To: freebsd-hackers@freebsd.org Message-id: <200605261955.19720.soralx@cydem.org> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7bit Content-disposition: inline References: User-Agent: KMail/1.9.1 Subject: Re: FreeBSD 6.1, crashes and a lack of vmcores X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 May 2006 02:55:23 -0000 > We started with memtest and CPU tests with no errors. As part of our > troubleshooting we have replaced (or swapped out with the other servers) > every piece of hardware in this box, replaced every cable and cord and > moved to different switch and power ports. We've even changed physical > locations in our data center. We have so far been unable resolve the more 0. how many hours did you run memtest86 for? 1. did you try to swap the mainboard? 2. do you suspect any corelation between net traffic intensity,type,etc, and crashes? 3. disabling ACPI made no change? [SorAlx] ridin' VN1500-B2 From owner-freebsd-hackers@FreeBSD.ORG Sat May 27 10:59: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 AB7CF16A8BD for ; Sat, 27 May 2006 10:59:22 +0000 (UTC) (envelope-from joost@jodocus.org) Received: from bps.jodocus.org (a198193.upc-a.chello.nl [62.163.198.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id E538B43D4C for ; Sat, 27 May 2006 10:59:21 +0000 (GMT) (envelope-from joost@jodocus.org) Received: from jodocus.org (localhost [127.0.0.1]) by bps.jodocus.org (8.13.6/8.13.6) with ESMTP id k4RAxJjo034525 for ; Sat, 27 May 2006 12:59:19 +0200 (CEST) (envelope-from joost@jodocus.org) Received: (from joost@localhost) by jodocus.org (8.13.6/8.13.6/Submit) id k4RAxJKQ034524 for freebsd-hackers@freebsd.org; Sat, 27 May 2006 12:59:19 +0200 (CEST) (envelope-from joost) Date: Sat, 27 May 2006 12:59:19 +0200 From: Joost Bekkers To: freebsd-hackers@freebsd.org Message-ID: <20060527105919.GA33939@bps.jodocus.org> Mail-Followup-To: Joost Bekkers , freebsd-hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Greylist: Sender is SPF-compliant, not delayed by milter-greylist-2.0.2 (bps.jodocus.org [127.0.0.1]); Sat, 27 May 2006 12:59:19 +0200 (CEST) X-Virus-Scanned: ClamAV 0.88.1/1488/Sat May 27 10:30:18 2006 on bps.jodocus.org X-Virus-Status: Clean Subject: Trouble debugging a kernel dump (kgdb: kvm_read: invalid address) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 May 2006 10:59:35 -0000 Hi The problem is probably in front of the keyboard, but I don't know what I'm doing wrong. A pc of a friend of mine has been crashing lately after installing 6.0R on it. It has ran 4.10R rock solid ever since it was released. Whenever I try to open the dump I get the following: # kgdb -d /usr/crash/ -n 0 /usr/src/sys/i386/compile/SAPPHIRE/kernel.debug kgdb: kvm_read: invalid address (0x50012) kgdb: kvm_read: invalid address (0x7) kgdb: kvm_read: invalid address (0x50) kgdb: kvm_read: invalid address (0x50) kgdb: kvm_read: invalid address (0x50) kgdb: kvm_read: invalid address (0x50) kgdb: kvm_read: invalid address (0x50) kgdb: kvm_read: invalid address (0x50) kgdb: kvm_read: invalid address (0x50) kgdb: kvm_read: invalid address (0x50) kgdb: kvm_read: invalid address (0x50) kgdb: kvm_read: invalid address (0x50) 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 8F1ED16D07A for ; Sat, 27 May 2006 22:22:15 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E11743D55 for ; Sat, 27 May 2006 22:22:15 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id F3E4E1A3C32; Sat, 27 May 2006 15:22:14 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id F3D7D5164F; Sat, 27 May 2006 18:22:13 -0400 (EDT) Date: Sat, 27 May 2006 18:22:13 -0400 From: Kris Kennaway To: Joost Bekkers , freebsd-hackers@freebsd.org Message-ID: <20060527222213.GA13879@xor.obsecurity.org> References: <20060527105919.GA33939@bps.jodocus.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="RnlQjJ0d97Da+TV1" Content-Disposition: inline In-Reply-To: <20060527105919.GA33939@bps.jodocus.org> User-Agent: Mutt/1.4.2.1i Cc: Subject: Re: Trouble debugging a kernel dump (kgdb: kvm_read: invalid address) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 May 2006 22:34:24 -0000 --RnlQjJ0d97Da+TV1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, May 27, 2006 at 12:59:19PM +0200, Joost Bekkers wrote: > Hi >=20 > The problem is probably in front of the keyboard, but I don't know what I= 'm > doing wrong. >=20 > A pc of a friend of mine has been crashing lately after installing 6.0R o= n it. > It has ran 4.10R rock solid ever since it was released. >=20 > Whenever I try to open the dump I get the following: >=20 > # kgdb -d /usr/crash/ -n 0 /usr/src/sys/i386/compile/SAPPHIRE/kernel.debu= g=20 > kgdb: kvm_read: invalid address (0x50012) > kgdb: kvm_read: invalid address (0x7) > kgdb: kvm_read: invalid address (0x50) > kgdb: kvm_read: invalid address (0x50) > kgdb: kvm_read: invalid address (0x50) > kgdb: kvm_read: invalid address (0x50) > kgdb: kvm_read: invalid address (0x50) > kgdb: kvm_read: invalid address (0x50) > kgdb: kvm_read: invalid address (0x50) > kgdb: kvm_read: invalid address (0x50) > kgdb: kvm_read: invalid address (0x50) > kgdb: kvm_read: invalid address (0x50) > =20 > Thank for any help you can give. Wrong kernel, usually. Kris --RnlQjJ0d97Da+TV1 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEeNEUWry0BWjoQKURAgJwAKDrnKKH20qKA/bUEJIFkeRxjlEjrwCbBp9O j1HRQxW8jGjdUaM9yw73Hro= =f9qF -----END PGP SIGNATURE----- --RnlQjJ0d97Da+TV1--