From owner-freebsd-current@FreeBSD.ORG Sun May 29 00:16:38 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C03FE1065672 for ; Sun, 29 May 2011 00:16:38 +0000 (UTC) (envelope-from DStaal@usa.net) Received: from mail.magehandbook.com (173-8-4-45-WashingtonDC.hfc.comcastbusiness.net [173.8.4.45]) by mx1.freebsd.org (Postfix) with ESMTP id 9AA2A8FC16 for ; Sun, 29 May 2011 00:16:38 +0000 (UTC) Received: from [192.168.1.50] (Mac-Pro.magehandbook.com [192.168.1.50]) by mail.magehandbook.com (Postfix) with ESMTP id 8832FCD2 for ; Sat, 28 May 2011 20:16:37 -0400 (EDT) Date: Sat, 28 May 2011 20:16:37 -0400 From: Daniel Staal To: freebsd-current@freebsd.org Message-ID: X-Mailer: Mulberry/4.0.8 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: ZFS install from -CURRENT snapshot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 May 2011 00:16:38 -0000 Ok, I think I've figured this out, but I want some confirmation before I start playing with actual hardware... The install steps on no longer appear to apply. The /dist/ directory doesn't exist on any of the current snapshots, so the actual install process given in that page can't work. Am I correct in guessing that the /usr/freebsd_dist/ directory has replaced it in some form? Also, instead of sub-folders with install scripts, there are tarballs, which I assume are extracted over the new filesystem? Then any necessary pre-boot configuration would be done. (Anything special need mention beyond what is on the page above?) If there's a doc someplace on this, feel free to point me to it. I just want a sanity-check before I dive in headfirst... Daniel T. Staal --------------------------------------------------------------- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. --------------------------------------------------------------- From owner-freebsd-current@FreeBSD.ORG Sun May 29 01:45:49 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4285C1065673 for ; Sun, 29 May 2011 01:45:49 +0000 (UTC) (envelope-from deeptech71@gmail.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id F42188FC17 for ; Sun, 29 May 2011 01:45:48 +0000 (UTC) Received: by gwb15 with SMTP id 15so1486349gwb.13 for ; Sat, 28 May 2011 18:45:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=d5ygujzJsHgxzuRflY028TH2BXr+mFvgeu3YEtfrhA8=; b=ZfrQzzOYgzJKkVV6zSJjU4c9XKbpFzpz2D56BxkaGC19cqhNXTugjpTpbfUBnJjCwQ kQF9mKJ2J9EBxk4bWNSJgrMYcohoepGr3Loh8ipj9R22/cgNCf+azyUfC8NK3uheSoW9 LhDxFcJqfMvmaxuwQx5NnyOTzmdNrbXQcoyxQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=W5dY1WhnXpkkZskmTDZHf3hf2pUBl9vG8roYC+wkKQ9v4QMYCNmg9WM8LxZ/TP32SL Kh36ecJKHcpcCz0dpoTcG3/9/QnsSKDVyGharc0h3urDoDZ+yg8fRaXGw9lmjhorR/Cm yNkOIh6IPxhDJtQoG9ChCoocOE+xTLva+FiTc= MIME-Version: 1.0 Received: by 10.236.92.116 with SMTP id i80mr4565571yhf.348.1306633548122; Sat, 28 May 2011 18:45:48 -0700 (PDT) Received: by 10.236.107.197 with HTTP; Sat, 28 May 2011 18:45:48 -0700 (PDT) In-Reply-To: <201105260940.37035.jhb@freebsd.org> References: <201105260940.37035.jhb@freebsd.org> Date: Sun, 29 May 2011 03:45:48 +0200 Message-ID: From: "deeptech71@gmail.com" To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: pcib allocation failure X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 May 2011 01:45:49 -0000 On Thu, May 26, 2011 at 3:40 PM, John Baldwin wrote: > Ohh, you have two devices behind this bridge that have prefetch ranges. > > As a hack, can you try this: > > Index: pci_pci.c > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- pci_pci.c =A0 (revision 222285) > +++ pci_pci.c =A0 (working copy) > @@ -162,8 +162,13 @@ pcib_write_windows(struct pcib_softc *sc, int mask > =A0{ > =A0 =A0 =A0 =A0device_t dev; > =A0 =A0 =A0 =A0uint32_t val; > + =A0 =A0 =A0 uint16_t cmd; > > =A0 =A0 =A0 =A0dev =3D sc->dev; > + =A0 =A0 =A0 cmd =3D pci_read_config(dev, PCIR_COMMAND, 2); > + =A0 =A0 =A0 if (cmd & (PCIM_CMD_PORTEN | PCIM_CMD_MEMEN)) > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 pci_write_config(dev, PCIR_COMMAND, > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 cmd & ~(PCIM_CMD_PORTEN | PCIM_CMD_= MEMEN), 2); > =A0 =A0 =A0 =A0if (sc->io.valid && mask & WIN_IO) { > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0val =3D pci_read_config(dev, PCIR_IOBASEL_= 1, 1); > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0if ((val & PCIM_BRIO_MASK) =3D=3D PCIM_BRI= O_32) { > @@ -192,6 +197,8 @@ pcib_write_windows(struct pcib_softc *sc, int mask > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0pci_write_config(dev, PCIR_PMBASEL_1, sc->= pmem.base >> 16, 2); > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0pci_write_config(dev, PCIR_PMLIMITL_1, sc-= >pmem.limit >> 16, 2); > =A0 =A0 =A0 =A0} > + =A0 =A0 =A0 if (cmd & (PCIM_CMD_PORTEN | PCIM_CMD_MEMEN)) > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 pci_write_config(dev, PCIR_COMMAND, cmd, 2)= ; > =A0} > > =A0static void > @@ -337,6 +344,9 @@ pcib_probe_windows(struct pcib_softc *sc) > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0pci_read_config(de= v, PCIR_PMLIMITL_1, 2)); > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0max =3D 0xffffffff; > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0} > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 /* XXX: Testing hack */ > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 if (device_get_unit(sc->sc_dev) =3D=3D 1) i'm assuming that "sc->sc_dev" should be "dev" (this fixes a compilation er= ror). > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 sc->pmem.limit =3D 0xefffff= ff; > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0pcib_alloc_window(sc, &sc->pmem, SYS_RES_M= EMORY, > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0RF_PREFETCHABLE, max); > =A0 =A0 =A0 =A0} that seems to work! btw, is my machine a test-pig for an upcoming change to the PCI bus driver? From owner-freebsd-current@FreeBSD.ORG Sun May 29 02:48:53 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BF165106564A; Sun, 29 May 2011 02:48:53 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from mail-yi0-f54.google.com (mail-yi0-f54.google.com [209.85.218.54]) by mx1.freebsd.org (Postfix) with ESMTP id 507248FC0C; Sun, 29 May 2011 02:48:52 +0000 (UTC) Received: by yie12 with SMTP id 12so1505070yie.13 for ; Sat, 28 May 2011 19:48:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=0eTAUQgQho0KpjQcgkjSA1pNkan8lLU+mZeSQZ4lZj8=; b=nHdH+jvqd97nQwklgCAnNcGhKz1hsm1pymRILlVaks/ccL5qi1aka+Z9NuxVYM0SXa Tx4KRnWEDq1zljTLjJjtfP/AVF4JA/HT+hn46eCeTylEYATbPacAtLoT8xM3TY7jVZHS YSc5FfsEnPCCl6DB24pYkhOQGclnaPqQljrWs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=QJ3l1VmxEB6KdICxSpamHZD0HvJhzrUs5wHVQ4kIRR4fnqwZ29PAhvY6OjpkfRaUEs eJmlBGvUjjOJEMQGLxTaUNWe7dXsM3G5sk5+DX/VQJ9l7Z16+acNJgXmOfS26WF7IyqX EP3xhcuyMdHqmOv3HPjvAr0etLIDkw34QKGSw= MIME-Version: 1.0 Received: by 10.236.175.38 with SMTP id y26mr4577500yhl.304.1306637332392; Sat, 28 May 2011 19:48:52 -0700 (PDT) Sender: asmrookie@gmail.com Received: by 10.236.103.136 with HTTP; Sat, 28 May 2011 19:48:52 -0700 (PDT) In-Reply-To: <4DDD2B34.5070702@FreeBSD.org> References: <4DD3F662.9040603@FreeBSD.org> <4DD54C18.8050305@FreeBSD.org> <4DDA8B2A.6010500@FreeBSD.org> <4DDD2B34.5070702@FreeBSD.org> Date: Sat, 28 May 2011 22:48:52 -0400 X-Google-Sender-Auth: hyYqyUUVDjH52ldX2USa0amNndI Message-ID: From: Attilio Rao To: Andriy Gapon Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-current@freebsd.org" , "freebsd-arch@freebsd.org" Subject: Re: [rfc] remove hlt_cpus et al sysctls and related code X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 May 2011 02:48:53 -0000 2011/5/25 Andriy Gapon : > on 23/05/2011 19:28 Andriy Gapon said the following: >> I propose the following path for moving forward. >> - use hint.lapic.X.disabled to disable individual CPUs by their APIC ID >> - use machdep.hyperthreading_allowed tunable to disable second logical C= PU on each >> real core >> >> The above should already work as expected. =C2=A0One thing is that curre= ntly we have >> handling of machdep.hyperthreading_allowed tunable under SCHED_ULE. =C2= =A0I plan to >> make it unconditional. >> >> Things to remove: >> - all the related sysctls for dynamic onlining/offlining >> - machdep.hlt_logical_cpus tunable (it duplicates hint.lapic.X.disabled) >> >> It's possible to keep machdep.hlt_logical_cpus and just add some code to= convert >> hlt_logical_cpus mask to a set of individual hint.lapic.X.disabled, but = I don't >> see very much value in that. =C2=A0But if there is a good reason to keep= that tunable, >> I am prepared to jump through this hoop. >> >> If no one objects to this proposal, I will provide a patch soon. > > The patch is here: > http://people.freebsd.org/~avg/cpu-offline-sysctl.diff > It should implement the strategy described above. > I don't see the point in keeping alive mp_grab_cpu_hlt() and supporting, actually. On the top of your patch I made some modifies that use directly ap_watchdog() in cpu_idle() which I think is better for the time being: http://www.freebsd.org/~attilio/avg_rem_cpuhlt.diff If you are happy with it, just commit as long as Garrett tests that. On a second round of changes we can discuss mp_watchdog and eventual removal / improvements to it. Attilio --=20 Peace can only be achieved by understanding - A. Einstein From owner-freebsd-current@FreeBSD.ORG Sun May 29 03:06:33 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E3EBB1065672; Sun, 29 May 2011 03:06:32 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from mail-yi0-f54.google.com (mail-yi0-f54.google.com [209.85.218.54]) by mx1.freebsd.org (Postfix) with ESMTP id 724C18FC15; Sun, 29 May 2011 03:06:32 +0000 (UTC) Received: by yie12 with SMTP id 12so1508013yie.13 for ; Sat, 28 May 2011 20:06:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=ln1aS4EpWu2Ff3myz6p94p4tr36E1rJ0kO7si9kf/io=; b=pO2k4XNYTSwU5VB5OUYGJ4zXs/Z9WYRge8TgmYa8ySwazkcI+Yq5G8B/76PyvTht2u Sf0csGc+hpca8hsToqg1VhMV0bdsegR5aAa+uPA6tf2ErEXycurq8YGfIc/hkt1XjNWF /MJK467pDgZTHopZ9IB/GSHZWUZy9hlt3Ms3I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=Wc0RaJa6AQwL5ZZMmVZSD5zyla9+r8dEF1bxSVaHKIH8d2kB9Gzah240xBDeL8gqHT 6B7g9yJFLIC/rPfgp26FB2QRtRamb0bbBPq9FSpijm8w0tqMRnNlUsN5DSjc0i0hi6gC Zpv85zb1+XJm+TM638V04eLgeousK23QTXdLk= MIME-Version: 1.0 Received: by 10.236.184.67 with SMTP id r43mr1456317yhm.103.1306638391582; Sat, 28 May 2011 20:06:31 -0700 (PDT) Sender: asmrookie@gmail.com Received: by 10.236.103.136 with HTTP; Sat, 28 May 2011 20:06:31 -0700 (PDT) In-Reply-To: References: <4DD3F662.9040603@FreeBSD.org> <4DD54C18.8050305@FreeBSD.org> <4DDA8B2A.6010500@FreeBSD.org> <4DDD2B34.5070702@FreeBSD.org> Date: Sat, 28 May 2011 23:06:31 -0400 X-Google-Sender-Auth: IIc0Uygr-f8wMAEEUsr1T_8RmV0 Message-ID: From: Attilio Rao To: Andriy Gapon Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-current@freebsd.org" , "freebsd-arch@freebsd.org" Subject: Re: [rfc] remove hlt_cpus et al sysctls and related code X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 May 2011 03:06:33 -0000 2011/5/28 Attilio Rao : > 2011/5/25 Andriy Gapon : >> on 23/05/2011 19:28 Andriy Gapon said the following: >>> I propose the following path for moving forward. >>> - use hint.lapic.X.disabled to disable individual CPUs by their APIC ID >>> - use machdep.hyperthreading_allowed tunable to disable second logical = CPU on each >>> real core >>> >>> The above should already work as expected. =C2=A0One thing is that curr= ently we have >>> handling of machdep.hyperthreading_allowed tunable under SCHED_ULE. =C2= =A0I plan to >>> make it unconditional. >>> >>> Things to remove: >>> - all the related sysctls for dynamic onlining/offlining >>> - machdep.hlt_logical_cpus tunable (it duplicates hint.lapic.X.disabled= ) >>> >>> It's possible to keep machdep.hlt_logical_cpus and just add some code t= o convert >>> hlt_logical_cpus mask to a set of individual hint.lapic.X.disabled, but= I don't >>> see very much value in that. =C2=A0But if there is a good reason to kee= p that tunable, >>> I am prepared to jump through this hoop. >>> >>> If no one objects to this proposal, I will provide a patch soon. >> >> The patch is here: >> http://people.freebsd.org/~avg/cpu-offline-sysctl.diff >> It should implement the strategy described above. >> > > I don't see the point in keeping alive mp_grab_cpu_hlt() and > supporting, actually. > > On the top of your patch I made some modifies that use directly > ap_watchdog() in cpu_idle() which I think is better for the time > being: > http://www.freebsd.org/~attilio/avg_rem_cpuhlt.diff > > If you are happy with it, just commit as long as Garrett tests that. > > On a second round of changes we can discuss mp_watchdog and eventual > removal / improvements to it. I almost forgot: this change would also require an UPDATE entry, where you explicitly mention the "new" way to deal with CPUs. Use your prefer wording. Attilio --=20 Peace can only be achieved by understanding - A. Einstein From owner-freebsd-current@FreeBSD.ORG Sun May 29 04:38:06 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2900C1065674 for ; Sun, 29 May 2011 04:38:06 +0000 (UTC) (envelope-from lambert@lambertfam.org) Received: from sysmon.tcworks.net (sysmon.tcworks.net [65.66.76.4]) by mx1.freebsd.org (Postfix) with ESMTP id CECC48FC14 for ; Sun, 29 May 2011 04:38:05 +0000 (UTC) Received: from sysmon.tcworks.net (localhost [127.0.0.1]) by sysmon.tcworks.net (8.13.1/8.13.1) with ESMTP id p4T480hZ049774; Sat, 28 May 2011 23:08:00 -0500 (CDT) (envelope-from lambert@lambertfam.org) Received: (from lambert@localhost) by sysmon.tcworks.net (8.13.1/8.13.1/Submit) id p4T480Br049773; Sat, 28 May 2011 23:08:00 -0500 (CDT) (envelope-from lambert@lambertfam.org) X-Authentication-Warning: sysmon.tcworks.net: lambert set sender to lambert@lambertfam.org using -f Date: Sat, 28 May 2011 23:08:00 -0500 From: Scott Lambert To: Daniel Staal Message-ID: <20110529040800.GA44286@sysmon.tcworks.net> Mail-Followup-To: Daniel Staal , freebsd-current@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i Cc: freebsd-current@freebsd.org Subject: Re: ZFS install from -CURRENT snapshot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 May 2011 04:38:06 -0000 On Sat, May 28, 2011 at 08:16:37PM -0400, Daniel Staal wrote: > > Ok, I think I've figured this out, but I want some confirmation before I > start playing with actual hardware... > > The install steps on no > longer appear to apply. The /dist/ directory doesn't exist on any of the > current snapshots, so the actual install process given in that page can't > work. > If there's a doc someplace on this, feel free to point me to it. > > I just want a sanity-check before I dive in headfirst... If you want to end up with a mirrored ZFS only setup, have you seen ? http://blogs.freebsdish.org/pjd/2010/08/06/from-sysinstall-to-zfs-only-configuration/ That one was pretty straight-forward for me. You get to use sysinstall and don't have to manually install the OS. -- Scott Lambert KC5MLE Unix SysAdmin lambert@lambertfam.org From owner-freebsd-current@FreeBSD.ORG Sun May 29 06:55:24 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 084DC10657A9 for ; Sun, 29 May 2011 06:55:24 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 527668FC0A for ; Sun, 29 May 2011 06:55:22 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id JAA27914; Sun, 29 May 2011 09:55:21 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1QQZuC-000AYo-M3; Sun, 29 May 2011 09:55:20 +0300 Message-ID: <4DE1EDD8.5050003@FreeBSD.org> Date: Sun, 29 May 2011 09:55:20 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.17) Gecko/20110503 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: freebsd-current@FreeBSD.org References: <20110529040800.GA44286@sysmon.tcworks.net> In-Reply-To: <20110529040800.GA44286@sysmon.tcworks.net> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Daniel Staal Subject: Re: ZFS install from -CURRENT snapshot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 May 2011 06:55:24 -0000 on 29/05/2011 07:08 Scott Lambert said the following: > If you want to end up with a mirrored ZFS only setup, have you seen ? > > http://blogs.freebsdish.org/pjd/2010/08/06/from-sysinstall-to-zfs-only-configuration/ > > That one was pretty straight-forward for me. You get to use > sysinstall and don't have to manually install the OS. There is no sysinstall :-) [in the latest CURRENT] -- Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Sun May 29 09:36:36 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D4D281065672; Sun, 29 May 2011 09:36:36 +0000 (UTC) (envelope-from gkontos.mail@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 8DCCD8FC13; Sun, 29 May 2011 09:36:36 +0000 (UTC) Received: by iwn33 with SMTP id 33so3434290iwn.13 for ; Sun, 29 May 2011 02:36:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=dveTKR2Fb8o6t7C7+p2ENoum1iFLLXAUTfAz4NkFF+o=; b=vnxQOiXMiHz5yz/bbCDPwVtEp5TsTeHz8PKYual4BsA3ZwpnHkbrAh11bWImIY9HXP atTtkZNBZqbY7B7dFsgqrpKgd13gFKOzGPlZqGuWV18T7SWgHmEgTsyfketPisHQvi0Z JYw85jwHNwKZAaV6pVst1EQIse2Dp5lBz8k6g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=qx4h2ySMhXWUpt+C/MTD5wWaIqUd5zncP9XEKY5UWirQOr/SAMSWjI0IrKEtgLfd5t 7uCfgiAV5bhSDNfC6WD2zDhxQNLgsOAjc5C/KPdOEyDO6iZZcXCH5gYakAC9UHMlDi2e lXQUbOXdWhEvDSrZigyOQ24zSlEVvBEJXdIU0= MIME-Version: 1.0 Received: by 10.231.24.70 with SMTP id u6mr4747929ibb.108.1306659990648; Sun, 29 May 2011 02:06:30 -0700 (PDT) Received: by 10.231.30.77 with HTTP; Sun, 29 May 2011 02:06:30 -0700 (PDT) In-Reply-To: <4DE1EDD8.5050003@FreeBSD.org> References: <20110529040800.GA44286@sysmon.tcworks.net> <4DE1EDD8.5050003@FreeBSD.org> Date: Sun, 29 May 2011 12:06:30 +0300 Message-ID: From: George Kontostanos To: Daniel Staal Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-current@freebsd.org, Andriy Gapon Subject: Re: ZFS install from -CURRENT snapshot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 May 2011 09:36:37 -0000 The new bsdinstall has a different layout so the previous guides don't work. I have prepared one that works for recent 9-Current at : "http://www.aisecure.net/?p=132" Regards On Sun, May 29, 2011 at 9:55 AM, Andriy Gapon wrote: > on 29/05/2011 07:08 Scott Lambert said the following: > > If you want to end up with a mirrored ZFS only setup, have you seen ? > > > > > http://blogs.freebsdish.org/pjd/2010/08/06/from-sysinstall-to-zfs-only-configuration/ > > > > That one was pretty straight-forward for me. You get to use > > sysinstall and don't have to manually install the OS. > > There is no sysinstall :-) [in the latest CURRENT] > > -- > Andriy Gapon > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > -- George Kontostanos aisecure.net From owner-freebsd-current@FreeBSD.ORG Sun May 29 11:38:16 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DCBF8106566C; Sun, 29 May 2011 11:38:16 +0000 (UTC) (envelope-from to.my.trociny@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 360EA8FC0A; Sun, 29 May 2011 11:38:15 +0000 (UTC) Received: by bwz12 with SMTP id 12so3350938bwz.13 for ; Sun, 29 May 2011 04:38:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:to:cc:subject:references:x-comment-to :sender:date:in-reply-to:message-id:user-agent:mime-version :content-type; bh=Ja5VrxGVOYDjTZtsjrUVGKtmWJv/9fSrB+y4R0Kzz7s=; b=In6S6L4ohKGA+ZAbTF5Zu1P1YPfJovdv+npgy4abG6hU7cYZLijJujBn8ZimzCW8og onUq7uQcW6BJBiNyw0vqU5BaN9Tpzmjme6UdNMDamOZUWbZIWUC+vKFAH0dX1BIthTb2 MuowSl//LMz3iIdIfhSLBRhxmJR7s8CRx+LrE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:subject:references:x-comment-to:sender:date:in-reply-to :message-id:user-agent:mime-version:content-type; b=ulGyijCG2nOEE/22MK0X9lnLo53+w1DNiTOhtSlFIpttAa+EUXSfzVWIvca5QTf0jq 1ZW23ihGV8ecStPCohUQMLcnpXlC3znZKSI1fpHbMz5BKdPZGSXBQoTWzSh+0JK7Eom2 xC5TgPZjnZvxP1AS077Bh+jWcTPlHOa+2Krag= Received: by 10.204.76.83 with SMTP id b19mr3349796bkk.126.1306667519865; Sun, 29 May 2011 04:11:59 -0700 (PDT) Received: from localhost ([95.69.172.154]) by mx.google.com with ESMTPS id t23sm2608392bkf.16.2011.05.29.04.11.56 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 29 May 2011 04:11:57 -0700 (PDT) From: Mikolaj Golub To: Maxim Sobolev References: <4DDD4890.70604@FreeBSD.org> X-Comment-To: Maxim Sobolev Sender: Mikolaj Golub Date: Sun, 29 May 2011 14:11:55 +0300 In-Reply-To: <4DDD4890.70604@FreeBSD.org> (Maxim Sobolev's message of "Wed, 25 May 2011 11:21:04 -0700") Message-ID: <86hb8du5fo.fsf@kopusha.home.net> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Pawel Jakub Dawidek , "current@freebsd.org" Subject: Re: Weird issue with hastd(8) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 May 2011 11:38:16 -0000 On Wed, 25 May 2011 11:21:04 -0700 Maxim Sobolev wrote: MS> Hi Pawel, MS> I am observing strange errors while synchronizing the data between MS> primary and secondary. I keep getting the following error messages: MS> May 25 11:09:19 eights hastd[10113]: [test] (secondary) Unable to MS> receive request header: Socket is not connected. MS> May 25 11:09:24 eights hastd[37571]: [test] (secondary) Worker process MS> exited ungracefully (pid=10113, exitcode=75). MS> May 25 11:10:17 eights hastd[12109]: [test] (secondary) Unable to MS> receive request header: Socket is not connected. MS> May 25 11:10:18 eights hastd[37571]: [test] (secondary) Worker process MS> exited ungracefully (pid=12109, exitcode=75). MS> May 25 11:10:39 eights hastd[14685]: [test] (secondary) Unable to MS> receive request header: Socket is not connected. MS> May 25 11:10:44 eights hastd[37571]: [test] (secondary) Worker process MS> exited ungracefully (pid=14685, exitcode=75). MS> The synchronization steel proceeds, but it's slow due to the need to MS> re-negotiate and re-spawn the secondary worker. I have tried to ktrace MS> both server and client at the same time. For some reason the primary MS> keeps sending data, while client gets 0-read from the recvfrom at some MS> point, while the primary keeps sending more data. This is 8-STABLE MS> code on both ends. MS> Any ideas of what could be wrong here are appreciated. This might be MSG_WAITALL issue I described on net@ (look for the thread "recv() with MSG_WAITALL might stuck when receiving more than rcvbuf", and also kern/154504). Could you please try the patch? http://people.freebsd.org/~trociny/uipc_socket.c.patch -- Mikolaj Golub From owner-freebsd-current@FreeBSD.ORG Sun May 29 13:10:58 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7A8651065674 for ; Sun, 29 May 2011 13:10:58 +0000 (UTC) (envelope-from DStaal@usa.net) Received: from mail.magehandbook.com (173-8-4-45-WashingtonDC.hfc.comcastbusiness.net [173.8.4.45]) by mx1.freebsd.org (Postfix) with ESMTP id 507498FC0C for ; Sun, 29 May 2011 13:10:58 +0000 (UTC) Received: from [192.168.1.50] (Mac-Pro.magehandbook.com [192.168.1.50]) by mail.magehandbook.com (Postfix) with ESMTP id 8CA01D85; Sun, 29 May 2011 09:10:57 -0400 (EDT) Date: Sun, 29 May 2011 09:10:57 -0400 From: Daniel Staal To: George Kontostanos , freebsd-current@freebsd.org Message-ID: <3E1EB5E79BD1A6B775EB8387@mac-pro.magehandbook.com> In-Reply-To: References: <20110529040800.GA44286@sysmon.tcworks.net> <4DE1EDD8.5050003@FreeBSD.org> X-Mailer: Mulberry/4.0.8 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: Re: ZFS install from -CURRENT snapshot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 May 2011 13:10:58 -0000 --As of May 29, 2011 12:06:30 PM +0300, George Kontostanos is alleged to have said: > The new bsdinstall has a different layout so the previous guides don't > work. I have prepared one that works for recent 9-Current at : > > "http://www.aisecure.net/?p=132" --As for the rest, it is mine. Thanks, that's about what I expected the install procedure to be at this point. Nice to have the reminder about the zpool.cache. (Do I have to use the Live CD mode? Can I use shell mode instead?) Daniel T. Staal --------------------------------------------------------------- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. --------------------------------------------------------------- From owner-freebsd-current@FreeBSD.ORG Sun May 29 13:54:34 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1FD7A106566B for ; Sun, 29 May 2011 13:54:34 +0000 (UTC) (envelope-from gkontos.mail@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id D94C38FC18 for ; Sun, 29 May 2011 13:54:33 +0000 (UTC) Received: by iwn33 with SMTP id 33so3567939iwn.13 for ; Sun, 29 May 2011 06:54:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=gOJZ1l/xjacVxN0X4K/MfLfAPp1nR0y+YXRjCCfon9Y=; b=wc5HpjlFVKA3PhFSr1JcnDsE+b9ew09ux1/O1JaRwzlOLDMBI7kunF6sSlPWZosACc T9vJrZHkLsWrzbrU+CF2Q4EZlni5BRXJFmkqx8rEV279xZEwB84OI93AuiIBOsl1qHh5 ySZpcw+wLTnw+3+6MiwcMAHlrgjo1aFaGnDgQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=AL0kQsQJ2KDC4vP9NDtjGg1AAHzkTW2zkXvoK9npW+k7rIkSRBxYwLEa/4dq7LxAfp Bx+v2YZ5Gikcbc4/qJfNhIrJFAQus/BfLZWgURlxccq4HWh53DUuI3v6AKN1/uFMxLgM lQC8KTF4nrDb6XNLvdhvomvLVKNTOHgWkutWE= MIME-Version: 1.0 Received: by 10.231.24.70 with SMTP id u6mr5040751ibb.108.1306677272928; Sun, 29 May 2011 06:54:32 -0700 (PDT) Received: by 10.231.30.77 with HTTP; Sun, 29 May 2011 06:54:32 -0700 (PDT) In-Reply-To: <3E1EB5E79BD1A6B775EB8387@mac-pro.magehandbook.com> References: <20110529040800.GA44286@sysmon.tcworks.net> <4DE1EDD8.5050003@FreeBSD.org> <3E1EB5E79BD1A6B775EB8387@mac-pro.magehandbook.com> Date: Sun, 29 May 2011 16:54:32 +0300 Message-ID: From: George Kontostanos To: Daniel Staal Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-current@freebsd.org Subject: Re: ZFS install from -CURRENT snapshot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 May 2011 13:54:34 -0000 Last time I checked it was practically the same. On Sun, May 29, 2011 at 4:10 PM, Daniel Staal wrote: > --As of May 29, 2011 12:06:30 PM +0300, George Kontostanos is alleged to > have said: > > The new bsdinstall has a different layout so the previous guides don't >> work. I have prepared one that works for recent 9-Current at : >> >> "http://www.aisecure.net/?p=132" >> > > --As for the rest, it is mine. > > Thanks, that's about what I expected the install procedure to be at this > point. Nice to have the reminder about the zpool.cache. (Do I have to use > the Live CD mode? Can I use shell mode instead?) > > > Daniel T. Staal > > --------------------------------------------------------------- > This email copyright the author. Unless otherwise noted, you > are expressly allowed to retransmit, quote, or otherwise use > the contents for non-commercial purposes. This copyright will > expire 5 years after the author's death, or in 30 years, > whichever is longer, unless such a period is in excess of > local copyright law. > --------------------------------------------------------------- > -- George Kontostanos aisecure.net From owner-freebsd-current@FreeBSD.ORG Sun May 29 22:04:57 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4C3041065672 for ; Sun, 29 May 2011 22:04:57 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id 084B68FC17 for ; Sun, 29 May 2011 22:04:56 +0000 (UTC) Received: by yxl31 with SMTP id 31so1750029yxl.13 for ; Sun, 29 May 2011 15:04:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:from:to:content-type :content-transfer-encoding:mime-version:subject:date:x-mailer; bh=vP7vTWqBxqczNlgum38/9nkgDY22bld+OsMk6gd13iw=; b=NG4WyyoTA9SgdBVS7osVw4dDPM3w2WHmOZNtsu4+nEK1XvTM2tAzoS6rJeD7zuHksw g+qqJHZ8rbvV10nFQUMsf7G2Bk5/9gwpU35jZ5pyHBmaFf/AjJIccv0eLWUVeCGhp503 1RMPpl8vgED2Qc/lKIbvGDn61u9WC8yz6n7zo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:content-type:content-transfer-encoding :mime-version:subject:date:x-mailer; b=D80zasY0Mx1cuoiJQY2+Re+JHcA1/dxJFcVtNkFbW2rUK/cb1xZbBpWUh4H1yW93uM iIPAPsSx0Rui96ctvIg8NrMo3G5LmrLsjXHvB70PP16DwVbyNg77PDbhYfwnjRHEkMVM sqe+2iVkGj3GwB1opZfBpJR5XCdIV3En250wk= Received: by 10.236.193.73 with SMTP id j49mr4750114yhn.332.1306705279819; Sun, 29 May 2011 14:41:19 -0700 (PDT) Received: from triad.knownspace (216-15-41-8.c3-0.gth-ubr1.lnh-gth.md.cable.rcn.com [216.15.41.8]) by mx.google.com with ESMTPS id i46sm2052161yhk.62.2011.05.29.14.41.18 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 29 May 2011 14:41:18 -0700 (PDT) Message-Id: <0448A52E-0AEB-430F-87D0-532C1AB94CB0@gmail.com> From: Justin Hibbits To: FreeBSD Current Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Date: Sun, 29 May 2011 17:41:17 -0400 X-Mailer: Apple Mail (2.936) Subject: Bootloader broken on ppc X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 May 2011 22:04:57 -0000 As of r222417 the bootloader is broken on PowerPC port, due to screen. 4th not being installed into /boot. - Justin From owner-freebsd-current@FreeBSD.ORG Sun May 29 22:18:06 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 41921106564A for ; Sun, 29 May 2011 22:18:06 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id EDB388FC17 for ; Sun, 29 May 2011 22:18:05 +0000 (UTC) Received: by vxc34 with SMTP id 34so3275786vxc.13 for ; Sun, 29 May 2011 15:18:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=wad1e9ZT/Fn1F9sEsZqSoS4r9aRX3wAxR783ye999UM=; b=nuItFuubHijI9h/iZLG6zr8q/y70nefJvaGgl2yH2IHNJp5DlmK0xHnbbxMX9ZJ20B 09jL2YM8CciATUxV/B+L5SQ/NyqvGwL7LTL7v4DXDbCv6KqjJ/xfrNE/OdybTD/LMjzs Gkf9rTJ4mxhXH3Qro/L8g/8bUX8YL08+FSIs0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=QkYIDj4tMqebkhJMQSA0yV7ZYhaNdBnjaZsePZQ5N0rPaanzR5i+poasvDbkZ0bcoe lPytv3+ObIGZUMFch8KzppVBC6XyCJzx/LIHeBYEppC70lYh8oorSBQtJqJryEO1mHYP bPZuDuofYi8o5Hr+HP6jL8T5NjugYGNCDG1k8= MIME-Version: 1.0 Received: by 10.220.124.71 with SMTP id t7mr1632437vcr.38.1306707485026; Sun, 29 May 2011 15:18:05 -0700 (PDT) Received: by 10.220.183.11 with HTTP; Sun, 29 May 2011 15:18:05 -0700 (PDT) In-Reply-To: <0448A52E-0AEB-430F-87D0-532C1AB94CB0@gmail.com> References: <0448A52E-0AEB-430F-87D0-532C1AB94CB0@gmail.com> Date: Sun, 29 May 2011 15:18:05 -0700 Message-ID: From: Garrett Cooper To: Justin Hibbits Content-Type: text/plain; charset=ISO-8859-1 Cc: FreeBSD Current Subject: Re: Bootloader broken on ppc X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 May 2011 22:18:06 -0000 On Sun, May 29, 2011 at 2:41 PM, Justin Hibbits wrote: > As of r222417 the bootloader is broken on PowerPC port, due to screen.4th > not being installed into /boot. It was fixed in r222450. Cheers, -Garrett From owner-freebsd-current@FreeBSD.ORG Sun May 29 22:20:24 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CCB26106566B for ; Sun, 29 May 2011 22:20:24 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id 8364E8FC08 for ; Sun, 29 May 2011 22:20:24 +0000 (UTC) Received: by yxl31 with SMTP id 31so1753613yxl.13 for ; Sun, 29 May 2011 15:20:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:cc:message-id:from:to:in-reply-to:content-type :content-transfer-encoding:mime-version:subject:date:references :x-mailer; bh=tNPOJKJKvwahTMu3SNc0qKGRww7NJ/5elcFQsrfq1Ck=; b=EatHWubwgzQLrZVLCaI5XNHlWWhWicbH9kw3t2/4dLl7MKbw/lrx3Yr7ExoXMBBdrn pkq2NxY6YQ7CxK5DelITZMxqorRkuqT9ri1yBY3BLm3sivl3aRioJmwX4EzdZAPt1uiL R/+JEipxqmEJX5vMiL/Y3KZWnBewrjgr3Rq8o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=cc:message-id:from:to:in-reply-to:content-type :content-transfer-encoding:mime-version:subject:date:references :x-mailer; b=PvC+WzXvBfq/go0i303ODyL4URruRNzC68mCPOhIZ9WyExPa0RtCJOyRQ3fRVopz9E O+03QXBL3U5DwbQYzgwT4D+OicsUmGB0NwidOkrKbOuKBkpDbxCT8A5qh9bjIqTExg6s awBHFf4TnX2QXr1UqpQhzdNSF8rZGYdA3M2+E= Received: by 10.236.184.71 with SMTP id r47mr4735668yhm.190.1306707623739; Sun, 29 May 2011 15:20:23 -0700 (PDT) Received: from triad.knownspace (216-15-41-8.c3-0.gth-ubr1.lnh-gth.md.cable.rcn.com [216.15.41.8]) by mx.google.com with ESMTPS id v50sm2073304yhi.16.2011.05.29.15.20.22 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 29 May 2011 15:20:23 -0700 (PDT) Message-Id: <91AE5980-0DA2-469E-B556-9523BA4E6518@gmail.com> From: Justin Hibbits To: Garrett Cooper In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Date: Sun, 29 May 2011 18:20:21 -0400 References: <0448A52E-0AEB-430F-87D0-532C1AB94CB0@gmail.com> X-Mailer: Apple Mail (2.936) Cc: FreeBSD Current Subject: Re: Bootloader broken on ppc X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 May 2011 22:20:24 -0000 On May 29, 2011, at 6:18 PM, Garrett Cooper wrote: > On Sun, May 29, 2011 at 2:41 PM, Justin Hibbits > wrote: >> As of r222417 the bootloader is broken on PowerPC port, due to >> screen.4th >> not being installed into /boot. > > It was fixed in r222450. > Cheers, > -Garrett Shows me for not checking very latest svn before posting. - Justin From owner-freebsd-current@FreeBSD.ORG Mon May 30 01:05:55 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 242BA106564A for ; Mon, 30 May 2011 01:05:54 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) by mx1.freebsd.org (Postfix) with ESMTP id 9C45A8FC0A for ; Mon, 30 May 2011 01:05:54 +0000 (UTC) Received: from julian-mac.elischer.org (home-nat.elischer.org [67.100.89.137]) (authenticated bits=0) by vps1.elischer.org (8.14.4/8.14.4) with ESMTP id p4U15pi9074474 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sun, 29 May 2011 18:05:52 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <4DE2ED78.4020901@freebsd.org> Date: Sun, 29 May 2011 18:06:00 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 To: Justin Hibbits References: <0448A52E-0AEB-430F-87D0-532C1AB94CB0@gmail.com> In-Reply-To: <0448A52E-0AEB-430F-87D0-532C1AB94CB0@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Current Subject: Re: Bootloader broken on ppc X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 May 2011 01:05:55 -0000 On 5/29/11 2:41 PM, Justin Hibbits wrote: > As of r222417 the bootloader is broken on PowerPC port, due to > screen.4th not being installed into /boot. I think it was fixed in 222450 > > - Justin > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Mon May 30 09:53:23 2011 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4FB2F1065675 for ; Mon, 30 May 2011 09:53:23 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 27BC48FC1A for ; Mon, 30 May 2011 09:53:23 +0000 (UTC) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id C811246B2D for ; Mon, 30 May 2011 05:53:22 -0400 (EDT) Date: Mon, 30 May 2011 10:53:22 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: current@FreeBSD.org In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Subject: Re: FYI: merging TCP, UDP, netisr locking changes X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 May 2011 09:53:23 -0000 On Tue, 24 May 2011, Robert Watson wrote: > Over the next few days, I will be merging a number of TCP-related locking > changes, as well as changes to various network stack infrastructure bits, > such as the netisr implementation. The goal, generally, has been to move us > in the direction of supporting more clear CPU affinity for network flows, > the ability to program filters in network cards to support those affinities > explicitly, and elimination of cache line contention (whether by locks, > stats, etc) during high-volume parallel steady-state TCP load, with > ancillary benefits (hopefully) for UDP and other protocols. This has > implied non-trivial changes to our inpcb locking model, netisr code, etc. > Detailed information will appear in commit messages as I go; some elements, > such a programming of card filters based on setting TCP socket options, are > very much a work in progress. > > Obviously, there are no bugs in this code at all. However, if they are, > they might manifest as network problems, new WITNESS warnings, etc, and > network stack exercise + reports would be greatly appreciated! > > This work has been sponsored by Juniper Networks. Thanks also to Bjoern > Zeeb, who has been reviewing changes! After a series of smaller commits, I've just merged some initial decomposition of the pcbinfo lock into an additional pcbhash lock, which changes lock ordering and lookup with respect to inpcbs significantly (r222488; commit message below). I expect there to be some initial instability as people shake out edge cases I didn't bump into in my testing. Please report bugs to current@, and I'll pick them up there! Robert N. M. Watson University of Cambridge Computer Laboratory Decompose the current single inpcbinfo lock into two locks: - The existing ipi_lock continues to protect the global inpcb list and inpcb counter. This lock is now relegated to a small number of allocation and free operations, and occasional operations that walk all connections (including, awkwardly, certain UDP multicast receive operations -- something to revisit). - A new ipi_hash_lock protects the two inpcbinfo hash tables for looking up connections and bound sockets, manipulated using new INP_HASH_*() macros. This lock, combined with inpcb locks, protects the 4-tuple address space. Unlike the current ipi_lock, ipi_hash_lock follows the individual inpcb connection locks, so may be acquired while manipulating a connection on which a lock is already held, avoiding the need to acquire the inpcbinfo lock preemptively when a binding change might later be required. As a result, however, lookup operations necessarily go through a reference acquire while holding the lookup lock, later acquiring an inpcb lock -- if required. A new function in_pcblookup() looks up connections, and accepts flags indicating how to return the inpcb. Due to lock order changes, callers no longer need acquire locks before performing a lookup: the lookup routine will acquire the ipi_hash_lock as needed. In the future, it will also be able to use alternative lookup and locking strategies transparently to callers, such as pcbgroup lookup. New lookup flags are, supplementing the existing INPLOOKUP_WILDCARD flag: INPLOOKUP_RLOCKPCB - Acquire a read lock on the returned inpcb Decompose the current single inpcbinfo lock into two locks: - The existing ipi_lock continues to protect the global inpcb list and inpcb counter. This lock is now relegated to a small number of allocation and free operations, and occasional operations that walk all connections (including, awkwardly, certain UDP multicast receive operations -- something to revisit). - A new ipi_hash_lock protects the two inpcbinfo hash tables for looking up connections and bound sockets, manipulated using new INP_HASH_*() macros. This lock, combined with inpcb locks, protects the 4-tuple address space. Unlike the current ipi_lock, ipi_hash_lock follows the individual inpcb connection locks, so may be acquired while manipulating a connection on which a lock is already held, avoiding the need to acquire the inpcbinfo lock preemptively when a binding change might later be required. As a result, however, lookup operations necessarily go through a reference acquire while holding the lookup lock, later acquiring an inpcb lock -- if required. A new function in_pcblookup() looks up connections, and accepts flags indicating how to return the inpcb. Due to lock order changes, callers no longer need acquire locks before performing a lookup: the lookup routine will acquire the ipi_hash_lock as needed. In the future, it will also be able to use alternative lookup and locking strategies transparently to callers, such as pcbgroup lookup. New lookup flags are, supplementing the existing INPLOOKUP_WILDCARD flag: INPLOOKUP_RLOCKPCB - Acquire a read lock on the returned inpcb INPLOOKUP_WLOCKPCB - Acquire a write lock on the returned inpcb Callers must pass exactly one of these flags (for the time being). Some notes: - All protocols are updated to work within the new regime; especially, TCP, UDPv4, and UDPv6. pcbinfo ipi_lock acquisitions are largely eliminated, and global hash lock hold times are dramatically reduced compared to previous locking. - The TCP syncache still relies on the pcbinfo lock, something that we may want to revisit. - Support for reverting to the FreeBSD 7.x locking strategy in TCP input is no longer available -- hash lookup locks are now held only very briefly during inpcb lookup, rather than for potentially extended periods. However, the pcbinfo ipi_lock will still be acquired if a connection state might change such that a connection is added or removed. - Raw IP sockets continue to use the pcbinfo ipi_lock for protection, due to maintaining their own hash tables. - The interface in6_pcblookup_hash_locked() is maintained, which allows callers to acquire hash locks and perform one or more lookups atomically with 4-tuple allocation: this is required only for TCPv6, as there is no in6_pcbconnect_setup(), which there should be. - UDPv6 locking remains significantly more conservative than UDPv4 locking, which relates to source address selection. This needs attention, as it likely significantly reduces parallelism in this code for multithreaded socket use (such as in BIND). - In the UDPv4 and UDPv6 multicast cases, we need to revisit locking somewhat, as they relied on ipi_lock to stablise 4-tuple matches, which is no longer sufficient. A second check once the inpcb lock is held should do the trick, keeping the general case from requiring the inpcb lock for every inpcb visited. - This work reminds us that we need to revisit locking of the v4/v6 flags, which may be accessed lock-free both before and after this change. - Right now, a single lock name is used for the pcbhash lock -- this is undesirable, and probably another argument is required to take care of this (or a char array name field in the pcbinfo?). This is not an MFC candidate for 8.x due to its impact on lookup and locking semantics. It's possible some of these issues could be worked around with compatibility wrappers, if necessary. Reviewed by: bz Sponsored by: Juniper Networks, Inc. From owner-freebsd-current@FreeBSD.ORG Mon May 30 15:01:16 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CB683106566C for ; Mon, 30 May 2011 15:01:16 +0000 (UTC) (envelope-from DStaal@usa.net) Received: from mail.magehandbook.com (173-8-4-45-WashingtonDC.hfc.comcastbusiness.net [173.8.4.45]) by mx1.freebsd.org (Postfix) with ESMTP id 629E48FC16 for ; Mon, 30 May 2011 15:01:15 +0000 (UTC) Received: from [192.168.1.50] (Mac-Pro.magehandbook.com [192.168.1.50]) by mail.magehandbook.com (Postfix) with ESMTP id B4F5BFEC; Mon, 30 May 2011 11:01:05 -0400 (EDT) Date: Mon, 30 May 2011 11:01:06 -0400 From: Daniel Staal To: George Kontostanos , freebsd-current@freebsd.org Message-ID: In-Reply-To: <3E1EB5E79BD1A6B775EB8387@mac-pro.magehandbook.com> References: <20110529040800.GA44286@sysmon.tcworks.net> <4DE1EDD8.5050003@FreeBSD.org> <3E1EB5E79BD1A6B775EB8387@mac-pro.magehandbook.com> X-Mailer: Mulberry/4.0.8 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: Re: ZFS install from -CURRENT snapshot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 May 2011 15:01:16 -0000 --As of May 29, 2011 9:10:57 AM -0400, George Kontostanos, freebsd-current@freebsd.org is alleged to have said: > --As of May 29, 2011 12:06:30 PM +0300, George Kontostanos is alleged to > have said: > >> The new bsdinstall has a different layout so the previous guides don't >> work. I have prepared one that works for recent 9-Current at : >> >> "http://www.aisecure.net/?p=132" > > --As for the rest, it is mine. > > Thanks, that's about what I expected the install procedure to be at this > point. Nice to have the reminder about the zpool.cache. (Do I have to > use the Live CD mode? Can I use shell mode instead?) --As for the rest, it is mine. Ok, I've tried shell mode and live CD mode. I've re-partitioned my disks several different ways. Nothing gets me a system that will actually boot. Or even recognize that there is an OS loaded anywhere. Help? (My preferred partitioning: ada1: 1 freebsd-boot 2 freebsd-swap 8G 3 freebsd-zfs 4G (zil) 4 freebsd-zfs 17G (cache) ada0: Managed by ZFS, ~250G Main filesystem. This takes advantage of the mSATA SSD in ada1.) Daniel T. Staal --------------------------------------------------------------- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. --------------------------------------------------------------- From owner-freebsd-current@FreeBSD.ORG Mon May 30 15:11:20 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 945AF106564A for ; Mon, 30 May 2011 15:11:20 +0000 (UTC) (envelope-from gkontos.mail@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 568F18FC0C for ; Mon, 30 May 2011 15:11:20 +0000 (UTC) Received: by iwn33 with SMTP id 33so4492049iwn.13 for ; Mon, 30 May 2011 08:11:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=+pzG8GF7r26xSBaj78Ci99PyZVf/Nxr5A9d/GPPPdiI=; b=x3F+HdP4ylOymfCKANvoD77cLDFWytx/nHrOZ5HBz0fnLf7delwzjZ5uwwmvorZscV 4kmbr404iu8V2/4oY6MZZgwAkQd4PP/v8AV1Nq11OBSVPZK79V/eNmed8vv6vIj5mjjI ouxHGWE8T/llUi9NAOpWhpLfDYXUbY6nDwP0o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=ivzE1P2wnvgJ657rMqNSdwruNLNrrhfc+ULPp4Rp5trbTGVpYgwlIIFDBpEV8CJes7 7LApWhZM6oFIUbwYo7k03G6HNFna9zB8nFnDbQxXAav5k44ghnRl/IsjL8k3jVKrarmz Hh03xB/wmB5Q9A+mX4712zFsI3GsjeFeUOhGA= MIME-Version: 1.0 Received: by 10.231.117.35 with SMTP id o35mr6306459ibq.149.1306768279874; Mon, 30 May 2011 08:11:19 -0700 (PDT) Received: by 10.231.215.42 with HTTP; Mon, 30 May 2011 08:11:19 -0700 (PDT) In-Reply-To: References: <20110529040800.GA44286@sysmon.tcworks.net> <4DE1EDD8.5050003@FreeBSD.org> <3E1EB5E79BD1A6B775EB8387@mac-pro.magehandbook.com> Date: Mon, 30 May 2011 18:11:19 +0300 Message-ID: From: George Kontostanos To: Daniel Staal Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-current@freebsd.org Subject: Re: ZFS install from -CURRENT snapshot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 May 2011 15:11:20 -0000 Could you please explain where did you actually got stacked ? Have you installed the OS by : for file in base.txz lib32.txz kernel.txz doc.txz ports.txz src.txz; do (cat $file | tar --unlink -xpJf - -C ${DESTDIR:-/}); done Did you copy zpool.cache ? On Mon, May 30, 2011 at 6:01 PM, Daniel Staal wrote: > --As of May 29, 2011 9:10:57 AM -0400, George Kontostanos, > freebsd-current@freebsd.org is alleged to have said: > > --As of May 29, 2011 12:06:30 PM +0300, George Kontostanos is alleged to >> have said: >> >> The new bsdinstall has a different layout so the previous guides don't >>> work. I have prepared one that works for recent 9-Current at : >>> >>> "http://www.aisecure.net/?p=132" >>> >> >> --As for the rest, it is mine. >> >> Thanks, that's about what I expected the install procedure to be at this >> point. Nice to have the reminder about the zpool.cache. (Do I have to >> use the Live CD mode? Can I use shell mode instead?) >> > > --As for the rest, it is mine. > > Ok, I've tried shell mode and live CD mode. I've re-partitioned my disks > several different ways. > > Nothing gets me a system that will actually boot. Or even recognize that > there is an OS loaded anywhere. Help? > > (My preferred partitioning: > > ada1: > 1 freebsd-boot > 2 freebsd-swap 8G > 3 freebsd-zfs 4G (zil) > 4 freebsd-zfs 17G (cache) > > ada0: Managed by ZFS, ~250G Main filesystem. > > This takes advantage of the mSATA SSD in ada1.) > > > Daniel T. Staal > > --------------------------------------------------------------- > This email copyright the author. Unless otherwise noted, you > are expressly allowed to retransmit, quote, or otherwise use > the contents for non-commercial purposes. This copyright will > expire 5 years after the author's death, or in 30 years, > whichever is longer, unless such a period is in excess of > local copyright law. > --------------------------------------------------------------- > -- George Kontostanos aisecure.net From owner-freebsd-current@FreeBSD.ORG Mon May 30 15:25:45 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EA64C1065672 for ; Mon, 30 May 2011 15:25:45 +0000 (UTC) (envelope-from DStaal@usa.net) Received: from mail.magehandbook.com (173-8-4-45-WashingtonDC.hfc.comcastbusiness.net [173.8.4.45]) by mx1.freebsd.org (Postfix) with ESMTP id BD9D78FC14 for ; Mon, 30 May 2011 15:25:45 +0000 (UTC) Received: from [192.168.1.50] (Mac-Pro.magehandbook.com [192.168.1.50]) by mail.magehandbook.com (Postfix) with ESMTP id 014F3FF9; Mon, 30 May 2011 11:25:44 -0400 (EDT) Date: Mon, 30 May 2011 11:25:45 -0400 From: Daniel Staal To: George Kontostanos , freebsd-current@freebsd.org Message-ID: <1D3AFD591C1E756AFAE43572@mac-pro.magehandbook.com> In-Reply-To: References: <20110529040800.GA44286@sysmon.tcworks.net> <4DE1EDD8.5050003@FreeBSD.org> <3E1EB5E79BD1A6B775EB8387@mac-pro.magehandbook.com> X-Mailer: Mulberry/4.0.8 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: Re: ZFS install from -CURRENT snapshot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 May 2011 15:25:46 -0000 --As of May 30, 2011 6:11:19 PM +0300, George Kontostanos is alleged to have said: > Could you please explain where did you actually got stacked ? > > Have you installed the OS by : > > for file in base.txz lib32.txz kernel.txz doc.txz ports.txz src.txz; > do (cat $file | tar --unlink -xpJf - -C ${DESTDIR:-/}); done > > Did you copy zpool.cache ? --As for the rest, it is mine. Did both of those. A half-dozen times. ;) The machine fails to find a bootable drive. It searches, tries PXE booting a couple of times, then dumps me into the BIOS's boot drive chooser. I can try selecting either of the internal drives at that point if I wish, and it will just loop back to there. Daniel T. Staal --------------------------------------------------------------- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. --------------------------------------------------------------- From owner-freebsd-current@FreeBSD.ORG Mon May 30 15:29:08 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8FE5D1065670 for ; Mon, 30 May 2011 15:29:08 +0000 (UTC) (envelope-from gkontos.mail@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 525698FC14 for ; Mon, 30 May 2011 15:29:08 +0000 (UTC) Received: by iwn33 with SMTP id 33so4506932iwn.13 for ; Mon, 30 May 2011 08:29:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=gESXepZrdgak0z1OIGFhfk2slEFMu7zm1AFDTK+tgjI=; b=OL2iJmIo/KwcumSN2fust5zA/InUS8mJsmmZHMzrvBnHkLHdo3w4zU12Cs0hZN6AQ/ wjlFIzwPCSuGzvZAQ/NEQ4sg6poz4Cb/Zu4OmsTt/GSBw7MoJYR8SEB1EBD6rNCrSE/g pce4MwAWtg8/a7tzPUTa2qrbNtMBfk/7OP0bQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Fikd37fpA7vZepRvDMwcqZXV3XadnueOlOZdgm1S1LZMgaf/lW+qj4lEGyb/7BR7AM DAjFh5QgYC5MU9t5HDf3sT4SMDCpOkgYArbG9K1CDzDK5oDvkmxOK0QVqrmWEpH4tLHI yNSyFgtQe+rujC+5wuCCUNSMQReBqHGdSO950= MIME-Version: 1.0 Received: by 10.231.91.16 with SMTP id k16mr6328938ibm.124.1306769346948; Mon, 30 May 2011 08:29:06 -0700 (PDT) Received: by 10.231.215.42 with HTTP; Mon, 30 May 2011 08:29:06 -0700 (PDT) In-Reply-To: <1D3AFD591C1E756AFAE43572@mac-pro.magehandbook.com> References: <20110529040800.GA44286@sysmon.tcworks.net> <4DE1EDD8.5050003@FreeBSD.org> <3E1EB5E79BD1A6B775EB8387@mac-pro.magehandbook.com> <1D3AFD591C1E756AFAE43572@mac-pro.magehandbook.com> Date: Mon, 30 May 2011 18:29:06 +0300 Message-ID: From: George Kontostanos To: Daniel Staal Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-current@freebsd.org Subject: Re: ZFS install from -CURRENT snapshot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 May 2011 15:29:08 -0000 I suppose that you didn't forget to add a boot code to your boot disk(s) ? gpart bootcode -b boot/pmbr -p boot/gptzfsboot -i 1 ada0 On Mon, May 30, 2011 at 6:25 PM, Daniel Staal wrote: > --As of May 30, 2011 6:11:19 PM +0300, George Kontostanos is alleged to > have said: > > Could you please explain where did you actually got stacked ? >> >> Have you installed the OS by : >> >> for file in base.txz lib32.txz kernel.txz doc.txz ports.txz src.txz; >> do (cat $file | tar --unlink -xpJf - -C ${DESTDIR:-/}); done >> >> Did you copy zpool.cache ? >> > > --As for the rest, it is mine. > > Did both of those. A half-dozen times. ;) > > The machine fails to find a bootable drive. It searches, tries PXE booting > a couple of times, then dumps me into the BIOS's boot drive chooser. I can > try selecting either of the internal drives at that point if I wish, and it > will just loop back to there. > > > Daniel T. Staal > > --------------------------------------------------------------- > This email copyright the author. Unless otherwise noted, you > are expressly allowed to retransmit, quote, or otherwise use > the contents for non-commercial purposes. This copyright will > expire 5 years after the author's death, or in 30 years, > whichever is longer, unless such a period is in excess of > local copyright law. > --------------------------------------------------------------- > -- George Kontostanos aisecure.net From owner-freebsd-current@FreeBSD.ORG Mon May 30 15:33:31 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6612A106564A for ; Mon, 30 May 2011 15:33:31 +0000 (UTC) (envelope-from DStaal@usa.net) Received: from mail.magehandbook.com (173-8-4-45-WashingtonDC.hfc.comcastbusiness.net [173.8.4.45]) by mx1.freebsd.org (Postfix) with ESMTP id 37E4A8FC12 for ; Mon, 30 May 2011 15:33:31 +0000 (UTC) Received: from [192.168.1.50] (Mac-Pro.magehandbook.com [192.168.1.50]) by mail.magehandbook.com (Postfix) with ESMTP id 63C3F1000 for ; Mon, 30 May 2011 11:33:30 -0400 (EDT) Date: Mon, 30 May 2011 11:33:30 -0400 From: Daniel Staal To: freebsd-current@freebsd.org Message-ID: <0D1F1853C6DE2ECF75C7ED26@mac-pro.magehandbook.com> In-Reply-To: References: <20110529040800.GA44286@sysmon.tcworks.net> <4DE1EDD8.5050003@FreeBSD.org> <3E1EB5E79BD1A6B775EB8387@mac-pro.magehandbook.com> <1D3AFD591C1E756AFAE43572@mac-pro.magehandbook.com> X-Mailer: Mulberry/4.0.8 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Re: ZFS install from -CURRENT snapshot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 May 2011 15:33:31 -0000 --As of May 30, 2011 6:29:06 PM +0300, George Kontostanos is alleged to have said: > I suppose that you didn't forget to add a boot code to your boot disk(s) ? > > gpart bootcode -b boot/pmbr -p boot/gptzfsboot -i 1 ada0 --As for the rest, it is mine. Nope, I got that. Although that line as written threw errors. I used: gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada1 (Normally I was installing the boot code to the mSATA drive, as it was the one I was partitioning.) Daniel T. Staal --------------------------------------------------------------- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. --------------------------------------------------------------- From owner-freebsd-current@FreeBSD.ORG Mon May 30 15:47:33 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BEA1A106564A for ; Mon, 30 May 2011 15:47:33 +0000 (UTC) (envelope-from gkontos.mail@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 7EDF78FC13 for ; Mon, 30 May 2011 15:47:33 +0000 (UTC) Received: by iwn33 with SMTP id 33so4522048iwn.13 for ; Mon, 30 May 2011 08:47:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=a8TPFPfW8z2AcbxSf+GuN6nTV30O4MRFZRtanfV/5aI=; b=Htny60CSrz3FI+e1Oz561twNAHDrg+HzV8bjf32xJlOloQqThOKq8mricdxFPaKEmk K0KyDXk5JNaJGt0dvBgloBVTAQVeJ9TEP188KQo3xeVVW37in7f4bXbYjpwRLk4YFW4q VmP0Bz81Xlb8HWlHc0ee+pEZ6FRZLD9Dddeyc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=LivtCFdLeBYNO0FEKsRqGxNnC++nIJhMyD09+CQW7PWQGx49NxAWHWyTMeeAbslm7V PZ6kcRIj9S9gZQJkyKltt8mjGqNkFnWVGf4u7T6q86TH7G+9aFbnGVP+EMvEwGVODarX Mf8zQhBYbRGYwCLnGP86fqChFHiB/nrc6prtA= MIME-Version: 1.0 Received: by 10.42.130.72 with SMTP id u8mr9644708ics.379.1306770452647; Mon, 30 May 2011 08:47:32 -0700 (PDT) Received: by 10.231.215.42 with HTTP; Mon, 30 May 2011 08:47:32 -0700 (PDT) In-Reply-To: <0D1F1853C6DE2ECF75C7ED26@mac-pro.magehandbook.com> References: <20110529040800.GA44286@sysmon.tcworks.net> <4DE1EDD8.5050003@FreeBSD.org> <3E1EB5E79BD1A6B775EB8387@mac-pro.magehandbook.com> <1D3AFD591C1E756AFAE43572@mac-pro.magehandbook.com> <0D1F1853C6DE2ECF75C7ED26@mac-pro.magehandbook.com> Date: Mon, 30 May 2011 18:47:32 +0300 Message-ID: From: George Kontostanos To: Daniel Staal Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-current@freebsd.org Subject: Re: ZFS install from -CURRENT snapshot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 May 2011 15:47:33 -0000 Sorry about the typos. The bootcode should be installed to the drive that you are booting from. I see that you have: ada1: 1 freebsd-boot 2 freebsd-swap 8G 3 freebsd-zfs 4G (zil) 4 freebsd-zfs 17G (cache) ada0: Managed by ZFS, ~250G Main filesystem. I don't think that ada1 holds any OS files therefore you will need to boot from ada0 gpart create -s gpt ada0 gpart add -b 34 -s 64k -t freebsd-boot ada0 gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0 On Mon, May 30, 2011 at 6:33 PM, Daniel Staal wrote: > --As of May 30, 2011 6:29:06 PM +0300, George Kontostanos is alleged to > have said: > > I suppose that you didn't forget to add a boot code to your boot disk(s) ? >> >> gpart bootcode -b boot/pmbr -p boot/gptzfsboot -i 1 ada0 >> > > --As for the rest, it is mine. > > Nope, I got that. Although that line as written threw errors. I used: > > gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada1 > > (Normally I was installing the boot code to the mSATA drive, as it was the > one I was partitioning.) > > > Daniel T. Staal > > --------------------------------------------------------------- > This email copyright the author. Unless otherwise noted, you > are expressly allowed to retransmit, quote, or otherwise use > the contents for non-commercial purposes. This copyright will > expire 5 years after the author's death, or in 30 years, > whichever is longer, unless such a period is in excess of > local copyright law. > --------------------------------------------------------------- > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > -- George Kontostanos aisecure.net From owner-freebsd-current@FreeBSD.ORG Mon May 30 15:59:23 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 67F03106564A for ; Mon, 30 May 2011 15:59:23 +0000 (UTC) (envelope-from daniel@digsys.bg) Received: from smtp-sofia.digsys.bg (smtp-sofia.digsys.bg [193.68.3.230]) by mx1.freebsd.org (Postfix) with ESMTP id E2D328FC12 for ; Mon, 30 May 2011 15:59:20 +0000 (UTC) Received: from dcave.digsys.bg (dcave.digsys.bg [192.92.129.5]) (authenticated bits=0) by smtp-sofia.digsys.bg (8.14.4/8.14.4) with ESMTP id p4UFQewY050495 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Mon, 30 May 2011 18:26:45 +0300 (EEST) (envelope-from daniel@digsys.bg) Message-ID: <4DE3B72F.8030203@digsys.bg> Date: Mon, 30 May 2011 18:26:39 +0300 From: Daniel Kalchev User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.17) Gecko/20110519 Thunderbird/3.1.10 MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <20110529040800.GA44286@sysmon.tcworks.net> <4DE1EDD8.5050003@FreeBSD.org> <3E1EB5E79BD1A6B775EB8387@mac-pro.magehandbook.com> In-Reply-To: <3E1EB5E79BD1A6B775EB8387@mac-pro.magehandbook.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: ZFS install from -CURRENT snapshot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 May 2011 15:59:23 -0000 On 29.05.11 16:10, Daniel Staal wrote: > --As of May 29, 2011 12:06:30 PM +0300, George Kontostanos is alleged > to have said: >> "http://www.aisecure.net/?p=132" > > Thanks, that's about what I expected the install procedure to be at > this point. Nice to have the reminder about the zpool.cache. (Do I > have to use the Live CD mode? Can I use shell mode instead?) > Actually, you don't need to go via the trouble to make /boot writable. You can obtain zpool.cache by using zpool import -c /tmp/zpool.cache zroot Then copy that file to the mounted root filesystem of the zpool. Daniel From owner-freebsd-current@FreeBSD.ORG Mon May 30 16:09:06 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BEB6A1065672 for ; Mon, 30 May 2011 16:09:06 +0000 (UTC) (envelope-from gkontos.mail@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 830E18FC15 for ; Mon, 30 May 2011 16:09:06 +0000 (UTC) Received: by iyj12 with SMTP id 12so4617268iyj.13 for ; Mon, 30 May 2011 09:09:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=kOKehN2lwex3GYVzin/N516s5/vuPeg59L81dN7XYWA=; b=jy2ja3avOP0NaHqMmv5kmR3Sq6HX+PvXu5JkfwP6Xri7LoKkK34xGtJ8VpNKlft+LG nF8lXevh6phuDvzCRCSoZ/V80vAuv3Kdv57XRth1TNwk3/y0ot/wc8BpCNOM3zo24DYt 3iA5O7eOzl99hIS7jpisSxeDAqZnRYizTfGAQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=TtIrd/xrhXi93g19HTKUZXRzNRw6g+X2M3NHT3BvcZQjkWRdf4u5aKoxN4ImxGHf37 ZiS8ZrR+j4hfYZpMFgSpZqj+UoxbOrVRhVOyq5g+Z5McRTrQ1O2dSRlO1Ck/gGCQoLak G1cptlaBrHeHjHiVdJ5jHEfpMijMUGfy8GAfw= MIME-Version: 1.0 Received: by 10.231.127.198 with SMTP id h6mr6577238ibs.199.1306771745838; Mon, 30 May 2011 09:09:05 -0700 (PDT) Received: by 10.231.215.42 with HTTP; Mon, 30 May 2011 09:09:05 -0700 (PDT) In-Reply-To: <4DE3B72F.8030203@digsys.bg> References: <20110529040800.GA44286@sysmon.tcworks.net> <4DE1EDD8.5050003@FreeBSD.org> <3E1EB5E79BD1A6B775EB8387@mac-pro.magehandbook.com> <4DE3B72F.8030203@digsys.bg> Date: Mon, 30 May 2011 19:09:05 +0300 Message-ID: From: George Kontostanos To: Daniel Kalchev Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-current@freebsd.org Subject: Re: ZFS install from -CURRENT snapshot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 May 2011 16:09:06 -0000 Thanks, I will reproduce it and update the guide. On Mon, May 30, 2011 at 6:26 PM, Daniel Kalchev wrote: > > > On 29.05.11 16:10, Daniel Staal wrote: > >> --As of May 29, 2011 12:06:30 PM +0300, George Kontostanos is alleged to >> have said: >> >>> "http://www.aisecure.net/?p=132" >>> >> >> Thanks, that's about what I expected the install procedure to be at this >> point. Nice to have the reminder about the zpool.cache. (Do I have to use >> the Live CD mode? Can I use shell mode instead?) >> >> Actually, you don't need to go via the trouble to make /boot writable. > You can obtain zpool.cache by using > > zpool import -c /tmp/zpool.cache zroot > > Then copy that file to the mounted root filesystem of the zpool. > > Daniel > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > -- George Kontostanos aisecure.net From owner-freebsd-current@FreeBSD.ORG Mon May 30 17:04:22 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B5BD91065670 for ; Mon, 30 May 2011 17:04:22 +0000 (UTC) (envelope-from DStaal@usa.net) Received: from mail.magehandbook.com (173-8-4-45-WashingtonDC.hfc.comcastbusiness.net [173.8.4.45]) by mx1.freebsd.org (Postfix) with ESMTP id 851B08FC0A for ; Mon, 30 May 2011 17:04:22 +0000 (UTC) Received: from [192.168.1.50] (Mac-Pro.magehandbook.com [192.168.1.50]) by mail.magehandbook.com (Postfix) with ESMTP id 58E5C73 for ; Mon, 30 May 2011 13:04:21 -0400 (EDT) Date: Mon, 30 May 2011 13:04:20 -0400 From: Daniel Staal To: freebsd-current@freebsd.org Message-ID: <23E3DA9AC3C53247AB75359E@mac-pro.magehandbook.com> In-Reply-To: References: <20110529040800.GA44286@sysmon.tcworks.net> <4DE1EDD8.5050003@FreeBSD.org> <3E1EB5E79BD1A6B775EB8387@mac-pro.magehandbook.com> <1D3AFD591C1E756AFAE43572@mac-pro.magehandbook.com> <0D1F1853C6DE2ECF75C7ED26@mac-pro.magehandbook.com> X-Mailer: Mulberry/4.0.8 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Re: ZFS install from -CURRENT snapshot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 May 2011 17:04:22 -0000 --As of May 30, 2011 6:47:32 PM +0300, George Kontostanos is alleged to have said: > The bootcode should be installed to the drive that you are booting from. > > I see that you have: > >> ada1: >> 1 freebsd-boot >> 2 freebsd-swap 8G >> 3 freebsd-zfs 4G (zil) >> 4 freebsd-zfs 17G (cache) >> >> ada0: Managed by ZFS, ~250G Main filesystem. > > I don't think that ada1 holds any OS files therefore you will need to boot > from ada0 > > gpart create -s gpt ada0 > gpart add -b 34 -s 64k -t freebsd-boot ada0 > gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0 --As for the rest, it is mine. I said that was my preferred partitioning. I had tried others. ;) I just double-checked putting the bootcode on ada0. It doesn't help. (Note that if it did that'd be an interesting regression from 8.2. My home server is running with *only* the bootcode on one drive, and the OS loaded from a ZFS RAIDZ array.) Daniel T. Staal --------------------------------------------------------------- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. --------------------------------------------------------------- From owner-freebsd-current@FreeBSD.ORG Mon May 30 17:04:31 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B26E81065746 for ; Mon, 30 May 2011 17:04:31 +0000 (UTC) (envelope-from mike@reifenberger.com) Received: from mail-out.m-online.net (mail-out.m-online.net [212.18.0.10]) by mx1.freebsd.org (Postfix) with ESMTP id 6A0838FC12 for ; Mon, 30 May 2011 17:04:31 +0000 (UTC) Received: from frontend1.mail.m-online.net (frontend1.mail.intern.m-online.net [192.168.8.180]) by mail-out.m-online.net (Postfix) with ESMTP id E56431853BA3 for ; Mon, 30 May 2011 18:48:23 +0200 (CEST) Received: from localhost (dynscan1.mnet-online.de [192.168.8.164]) by mail.m-online.net (Postfix) with ESMTP id 0BB1C1C000B5 for ; Mon, 30 May 2011 18:48:24 +0200 (CEST) X-Virus-Scanned: amavisd-new at mnet-online.de Received: from mail.mnet-online.de ([192.168.8.180]) by localhost (dynscan1.mail.m-online.net [192.168.8.164]) (amavisd-new, port 10024) with ESMTP id seKfQxfL+8S6 for ; Mon, 30 May 2011 18:48:23 +0200 (CEST) Received: from mail.reifenberger.com (ppp-93-104-96-13.dynamic.mnet-online.de [93.104.96.13]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.mnet-online.de (Postfix) with ESMTPS for ; Mon, 30 May 2011 18:48:23 +0200 (CEST) Received: by mail.reifenberger.com (Postfix, from userid 1001) id 9BCC031097; Mon, 30 May 2011 18:48:22 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mail.reifenberger.com (Postfix) with ESMTP id 7468931094 for ; Mon, 30 May 2011 18:48:22 +0200 (CEST) Date: Mon, 30 May 2011 18:48:22 +0200 (CEST) From: Michael Reifenberger To: FreeBSD-Current Message-ID: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Cc: Subject: mount root from zfs fails under current with "error 6" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 May 2011 17:04:31 -0000 Hi, I get the following error with recent -current (r222417) during boot: ... Trying to mount root from zfs:boot/ROOT/root []... Mounting from zfs:boot/ROOT/root failed with error 6. ... What does "error 6" mean? The strange thing is, that I could boot with r222417 a few times but after applying a (here unrelated) one-liner from rmacklem@ to nfs_clkdtrace.c, recompile the module and reinstall, I could'n load either kernel nor kernel.old. I didn't even use the patched module. Only loading a kernel r221381 let me boot again. So may it be a race condition of some form? Anyone else sees this? Any further infos are available on request. Bye/2 --- Michael Reifenberger Michael@Reifenberger.com http://www.Reifenberger.com From owner-freebsd-current@FreeBSD.ORG Mon May 30 17:25:19 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 843B6106566C for ; Mon, 30 May 2011 17:25:19 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 3C3068FC19 for ; Mon, 30 May 2011 17:25:18 +0000 (UTC) Received: by vxc34 with SMTP id 34so3860218vxc.13 for ; Mon, 30 May 2011 10:25:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=fRBXqqdDZqKOzm//qvStU0zq072MrZL+E4gbZxQvMNM=; b=pm0VU0AL0+qXzZ4RsEi/I18IddBpGRtMhSVhRAJTy072qZteGi1oKCY7RsFccX2sJ1 OP1xjLOtEObfpgJ6EMeBTraOJGjVXKVLBiRIWPIfH9UhEIG4Yp7j3FTi0uQw4PDFT6ig fGjYZW4ZPSbkW7iMWIKpSA9X3McO/Vd4rtB0I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=TiZjKFCERTbGsFtTIBjKgaoLnfFbQGAfqP78Okk5gVG4PfAdHkbDtCPtIoIlFcDhqd gHGxiGdJtw0YIfTmzk002QMdYodFdhr3e9a/eBtHjutL1TjTzmCZ71sq91TC2Wflo8pM kIvq9z/Y1fOMVjSPlEF5TrYax3YAfSO2YfC6E= MIME-Version: 1.0 Received: by 10.220.124.71 with SMTP id t7mr1940188vcr.38.1306776318398; Mon, 30 May 2011 10:25:18 -0700 (PDT) Received: by 10.220.183.11 with HTTP; Mon, 30 May 2011 10:25:18 -0700 (PDT) In-Reply-To: References: Date: Mon, 30 May 2011 10:25:18 -0700 Message-ID: From: Garrett Cooper To: Michael Reifenberger Content-Type: text/plain; charset=ISO-8859-1 Cc: FreeBSD-Current Subject: Re: mount root from zfs fails under current with "error 6" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 May 2011 17:25:19 -0000 On Mon, May 30, 2011 at 9:48 AM, Michael Reifenberger wrote: > Hi, > I get the following error with recent -current (r222417) during boot: > ... > Trying to mount root from zfs:boot/ROOT/root []... > Mounting from zfs:boot/ROOT/root failed with error 6. > ... > > What does "error 6" mean? See ENXIO under errno(2). > The strange thing is, that I could boot with r222417 a few times > but after applying a (here unrelated) one-liner from rmacklem@ to > nfs_clkdtrace.c, recompile the module and reinstall, I could'n load either > kernel nor kernel.old. > I didn't even use the patched module. > > Only loading a kernel r221381 let me boot again. > > So may it be a race condition of some form? > > Anyone else sees this? > > Any further infos are available on request. dmesg for starters (boot -v if possible) would be extremely helpful. More details like your disk subsystem that you're booting off of, whether you're using GPT/MBR when booting via ZFS, etc would be helpful. Also being able to better trace down the root cause would be nice (not being able to boot a recent kernel, but being able to boot a kernel from almost a month ago is unfortunately a bit of a non-starter for tracking down the actual issue because that's such a long span of time). Thanks, -Garrett From owner-freebsd-current@FreeBSD.ORG Mon May 30 18:13:22 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CD91C106564A for ; Mon, 30 May 2011 18:13:22 +0000 (UTC) (envelope-from gkontos.mail@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 79CA38FC0A for ; Mon, 30 May 2011 18:13:22 +0000 (UTC) Received: by iyj12 with SMTP id 12so4712490iyj.13 for ; Mon, 30 May 2011 11:13:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=pTkJ2VhN2WqlF6HJamDnmkKUyJEwju0r8GEFnoOp1LU=; b=fwG07CXXaAuhbJYjOe9saMh5bIVoXzswQSPybBwXeiQkUHgn5NiBp2fu2+3Dar+t0C o2TtNFBoDoK9za3uxOOTeYpi/w+EBFL9pnmOVA5Udw+Higg0n7ewAOq1HpViPQzaBj5U EVDEb4S7gJAxDi4YW8bWhBgjiZH+k/cXkit9E= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=p7FDcdwCO/+gabTqRFNWTDPpMFvIqkCgZI++44Hm25Uv66hgAf+S6HcRqL37tAzod9 2H9jlyAc7gu2sj9V0jKrCHXNt9dU26+/soGyRpYW17fWYeYBoOntfqAEn686ykfSOEfA jrIn/qolpwLeeiQPMgnX6OSEQc6LCOiXQiknQ= MIME-Version: 1.0 Received: by 10.231.127.198 with SMTP id h6mr6716677ibs.199.1306779201826; Mon, 30 May 2011 11:13:21 -0700 (PDT) Received: by 10.231.215.42 with HTTP; Mon, 30 May 2011 11:13:21 -0700 (PDT) In-Reply-To: <23E3DA9AC3C53247AB75359E@mac-pro.magehandbook.com> References: <20110529040800.GA44286@sysmon.tcworks.net> <4DE1EDD8.5050003@FreeBSD.org> <3E1EB5E79BD1A6B775EB8387@mac-pro.magehandbook.com> <1D3AFD591C1E756AFAE43572@mac-pro.magehandbook.com> <0D1F1853C6DE2ECF75C7ED26@mac-pro.magehandbook.com> <23E3DA9AC3C53247AB75359E@mac-pro.magehandbook.com> Date: Mon, 30 May 2011 21:13:21 +0300 Message-ID: From: George Kontostanos To: Daniel Staal Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-current@freebsd.org Subject: Re: ZFS install from -CURRENT snapshot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 May 2011 18:13:22 -0000 Could you please post the output of: gpart show On Mon, May 30, 2011 at 8:04 PM, Daniel Staal wrote: > --As of May 30, 2011 6:47:32 PM +0300, George Kontostanos is alleged to > have said: > > The bootcode should be installed to the drive that you are booting from. >> >> I see that you have: >> >> ada1: >>> 1 freebsd-boot >>> 2 freebsd-swap 8G >>> 3 freebsd-zfs 4G (zil) >>> 4 freebsd-zfs 17G (cache) >>> >>> ada0: Managed by ZFS, ~250G Main filesystem. >>> >> >> I don't think that ada1 holds any OS files therefore you will need to boot >> from ada0 >> >> gpart create -s gpt ada0 >> gpart add -b 34 -s 64k -t freebsd-boot ada0 >> gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0 >> > > --As for the rest, it is mine. > > I said that was my preferred partitioning. I had tried others. ;) I just > double-checked putting the bootcode on ada0. It doesn't help. > > (Note that if it did that'd be an interesting regression from 8.2. My home > server is running with *only* the bootcode on one drive, and the OS loaded > from a ZFS RAIDZ array.) > > > Daniel T. Staal > > --------------------------------------------------------------- > This email copyright the author. Unless otherwise noted, you > are expressly allowed to retransmit, quote, or otherwise use > the contents for non-commercial purposes. This copyright will > expire 5 years after the author's death, or in 30 years, > whichever is longer, unless such a period is in excess of > local copyright law. > --------------------------------------------------------------- > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > -- George Kontostanos aisecure.net From owner-freebsd-current@FreeBSD.ORG Mon May 30 18:54:52 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 446FE1065675 for ; Mon, 30 May 2011 18:54:52 +0000 (UTC) (envelope-from gkontos.mail@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 0718F8FC0C for ; Mon, 30 May 2011 18:54:51 +0000 (UTC) Received: by iyj12 with SMTP id 12so4742303iyj.13 for ; Mon, 30 May 2011 11:54:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=Xgb7Rtm09EHho0Usc2OkCr1dMW2HCgP5vMbdpJExTzg=; b=aPZAE+PnzVHgW7+2/INFLEMz9VKlT4bcCy7QhZ/bX4QG48y+X8CyDrzfBCRfIL2zuj vI8ar67IXTfsF4acW/k4PUqVbVd5+OjsqZGW7RdRPT14MfirXFcNHFzBnwuyhlTxpoja K5Dgqg8ShfbeeUuvqrfSzpIuziOunOvtVbDyk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=jStEOh/SpmPLkxwCq1cRvm9XYf46HvSZwEHX8YNjUI71u+KZn6/OQyCD2DDyYVGYxP aldT1goFMiPri0XDGLLZZh4WCCZXtzon8WqJkuU1wXrDAW3cPzh//jMdZBpF1TCu0SDi QSz3ZOGdndAez6+RVsx51zqBY0rzVIvYQUMH4= MIME-Version: 1.0 Received: by 10.231.91.16 with SMTP id k16mr6546331ibm.124.1306781691050; Mon, 30 May 2011 11:54:51 -0700 (PDT) Received: by 10.231.215.42 with HTTP; Mon, 30 May 2011 11:54:51 -0700 (PDT) In-Reply-To: <4DE3B72F.8030203@digsys.bg> References: <20110529040800.GA44286@sysmon.tcworks.net> <4DE1EDD8.5050003@FreeBSD.org> <3E1EB5E79BD1A6B775EB8387@mac-pro.magehandbook.com> <4DE3B72F.8030203@digsys.bg> Date: Mon, 30 May 2011 21:54:51 +0300 Message-ID: From: George Kontostanos To: Daniel Kalchev Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: FreeBSD-Current Subject: Re: ZFS install from -CURRENT snapshot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 May 2011 18:54:52 -0000 *zpool import -c /tmp/zpool.cache zroot can not import /tmp/zpool.cache no such pool available * Well, it seems that -c switch is for specifying where to read from and not where to write. I haven't been able to import the pool and find a way to store zpool.cache in a diffrent place other than /boot/zfs On Mon, May 30, 2011 at 6:26 PM, Daniel Kalchev wrote: > > > On 29.05.11 16:10, Daniel Staal wrote: > >> --As of May 29, 2011 12:06:30 PM +0300, George Kontostanos is alleged to >> have said: >> >>> "http://www.aisecure.net/?p=132" >>> >> >> Thanks, that's about what I expected the install procedure to be at this >> point. Nice to have the reminder about the zpool.cache. (Do I have to use >> the Live CD mode? Can I use shell mode instead?) >> >> Actually, you don't need to go via the trouble to make /boot writable. > You can obtain zpool.cache by using > > zpool import -c /tmp/zpool.cache zroot > > Then copy that file to the mounted root filesystem of the zpool. > > Daniel > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > -- George Kontostanos aisecure.net From owner-freebsd-current@FreeBSD.ORG Mon May 30 20:56:03 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C3758106566B for ; Mon, 30 May 2011 20:56:03 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 7E10D8FC19 for ; Mon, 30 May 2011 20:56:03 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ap4EANgD5E2DaFvO/2dsb2JhbABVG4QuolilIo4kkDqBK4NsgQcEkE+PNg X-IronPort-AV: E=Sophos;i="4.65,293,1304308800"; d="scan'208";a="126303656" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 30 May 2011 16:56:02 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 9C3CAB3F3D for ; Mon, 30 May 2011 16:56:02 -0400 (EDT) Date: Mon, 30 May 2011 16:56:02 -0400 (EDT) From: Rick Macklem To: FreeBSD-Current Message-ID: <857698325.1023052.1306788962581.JavaMail.root@erie.cs.uoguelph.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.202] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - IE7 (Win)/6.0.10_GA_2692) Subject: mountd, rpc.lockd and rpc.statd patches for testing X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 May 2011 20:56:03 -0000 Hi, I have patches for the mountd, rpc.statd and rpc.lockd daemons that are meant to keep them from failing when a dynamically selected port# is not available for some combination of udp,tcp X ipv4,ipv6 If anyone would like to test these patches, they can be found at: http://people.freebsd.org/~rmacklem/mountd.patch statd.patch lockd.patch Although I think I got them correct, they are rather big and ugly. rick From owner-freebsd-current@FreeBSD.ORG Mon May 30 21:31:25 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 15491106564A for ; Mon, 30 May 2011 21:31:25 +0000 (UTC) (envelope-from inyaoo@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id BC6338FC13 for ; Mon, 30 May 2011 21:31:24 +0000 (UTC) Received: by gyg13 with SMTP id 13so2242503gyg.13 for ; Mon, 30 May 2011 14:31:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:to:cc:subject:references:date:in-reply-to :message-id:user-agent:mime-version:content-type; bh=OZVzxKFq7lH6jOhSDZfGe1wccp2K+o9dVGS1D6K1Ddo=; b=fiH0zWu2r4mG3Fwg4oZmugwR3VUVkP7D1ZeMNGUMdvpky6QO3ZRws6Ww3DpjV+XY1z GL7w/MFKnovQYOUSkfSabD/5iPTlTMdUx8TJfSSs/bbJ3vLcgFkXEd6WfbruPtrs+3lo ph5PpNYsLn4TcENHA2YdK8lkeZt3KoVIxZ0Q4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-type; b=avqaIitqZYucCqBPpswp5V/Tj2pJxz69fXE55m+CcQGEHz2vbMttHz0G2pwtiCyGtE mPt8SEj2okusY/wILXbizq99w6glfx0vZq169xG/YxwBAsmZCBdfru1nUoHuOTAG8fDP f4/KgYvEZyE3ca1pDnuTJtEUERaLFWtlTDG3Q= Received: by 10.236.161.228 with SMTP id w64mr5783020yhk.140.1306791083915; Mon, 30 May 2011 14:31:23 -0700 (PDT) Received: from localhost (chomsky.torservers.net [77.247.181.162]) by mx.google.com with ESMTPS id a45sm1338887yhm.7.2011.05.30.14.31.20 (version=SSLv3 cipher=OTHER); Mon, 30 May 2011 14:31:23 -0700 (PDT) From: Pan Tsu To: George Kontostanos References: <20110529040800.GA44286@sysmon.tcworks.net> <4DE1EDD8.5050003@FreeBSD.org> <3E1EB5E79BD1A6B775EB8387@mac-pro.magehandbook.com> <4DE3B72F.8030203@digsys.bg> Date: Tue, 31 May 2011 01:30:59 +0400 In-Reply-To: (George Kontostanos's message of "Mon, 30 May 2011 21:54:51 +0300") Message-ID: <868vtnub8s.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain Cc: FreeBSD-Current , Daniel Kalchev Subject: Re: ZFS install from -CURRENT snapshot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 May 2011 21:31:25 -0000 George Kontostanos writes: > *zpool import -c /tmp/zpool.cache zroot > can not import /tmp/zpool.cache no such pool available Try modifying pool's property: $ zpool import -o cachefile=/tmp/zpool.cache zroot > Well, it seems that -c switch is for specifying where to read from and not > where to write. I haven't been able to import the pool and find a way to > store zpool.cache in a diffrent place other than /boot/zfs From owner-freebsd-current@FreeBSD.ORG Mon May 30 22:21:50 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D53781065670 for ; Mon, 30 May 2011 22:21:50 +0000 (UTC) (envelope-from gkontos.mail@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 97A548FC14 for ; Mon, 30 May 2011 22:21:50 +0000 (UTC) Received: by iwn33 with SMTP id 33so4800334iwn.13 for ; Mon, 30 May 2011 15:21:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=XoyfEbhrCDAFPwJFzKM4/qtNGf8UDmHtjer7F4p54YU=; b=gn8QIf7wqHBSxRbfVbf6YFqrjbfnb8zNW5Av6JA8RO6TjELSEbVmosc5XriGgstzJV Fct5TN+JK+hzz0r+Ll8PzaDv91XmAm+eUDxlmrnR1dcmhMsi3nsFNbD8gXI71OTipTvk 0CPaDlXh9ujvJH8dOR1UbNxcv1JgIgIuQ52dY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=VeJnjOA14y/XUiD8b/hptL4O09X3izW6jpr0fUq94+BhV06teKPBX/1QtkCA2VCdGv 3EEXSmHExC9TNt/pNHao5LQ7IorWhNNe40fUtGqWifaeUB1JLL3+mqQbnHOtD0D5PmUt DdfbJxCiq2Aq49NttjtZm1tHyE4JuzYS7NOMU= MIME-Version: 1.0 Received: by 10.42.130.72 with SMTP id u8mr10259050ics.379.1306794109701; Mon, 30 May 2011 15:21:49 -0700 (PDT) Received: by 10.231.215.42 with HTTP; Mon, 30 May 2011 15:21:49 -0700 (PDT) In-Reply-To: <868vtnub8s.fsf@gmail.com> References: <20110529040800.GA44286@sysmon.tcworks.net> <4DE1EDD8.5050003@FreeBSD.org> <3E1EB5E79BD1A6B775EB8387@mac-pro.magehandbook.com> <4DE3B72F.8030203@digsys.bg> <868vtnub8s.fsf@gmail.com> Date: Tue, 31 May 2011 01:21:49 +0300 Message-ID: From: George Kontostanos To: Pan Tsu , Daniel Staal Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: FreeBSD-Current Subject: Re: ZFS install from -CURRENT snapshot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 May 2011 22:21:51 -0000 Bingo! That did it. I will update the guide soon. @Daniel my apologies it seems that another typo is preventing you from booting. You have to set the bootfs in the pool. zpool set bootfs=zroot zroot On Tue, May 31, 2011 at 12:30 AM, Pan Tsu wrote: > George Kontostanos writes: > > > *zpool import -c /tmp/zpool.cache zroot > > can not import /tmp/zpool.cache no such pool available > > Try modifying pool's property: > > $ zpool import -o cachefile=/tmp/zpool.cache zroot > > > Well, it seems that -c switch is for specifying where to read from and > not > > where to write. I haven't been able to import the pool and find a way to > > store zpool.cache in a diffrent place other than /boot/zfs > -- George Kontostanos aisecure.net From owner-freebsd-current@FreeBSD.ORG Mon May 30 22:48:06 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A1540106566B for ; Mon, 30 May 2011 22:48:06 +0000 (UTC) (envelope-from DStaal@usa.net) Received: from mail.magehandbook.com (173-8-4-45-WashingtonDC.hfc.comcastbusiness.net [173.8.4.45]) by mx1.freebsd.org (Postfix) with ESMTP id 5B6D68FC1B for ; Mon, 30 May 2011 22:48:06 +0000 (UTC) Received: from [192.168.1.50] (Mac-Pro.magehandbook.com [192.168.1.50]) by mail.magehandbook.com (Postfix) with ESMTP id 45C7310E; Mon, 30 May 2011 18:48:05 -0400 (EDT) Date: Mon, 30 May 2011 18:48:05 -0400 From: Daniel Staal To: George Kontostanos , FreeBSD-Current Message-ID: In-Reply-To: References: <20110529040800.GA44286@sysmon.tcworks.net> <4DE1EDD8.5050003@FreeBSD.org> <3E1EB5E79BD1A6B775EB8387@mac-pro.magehandbook.com> <4DE3B72F.8030203@digsys.bg> <868vtnub8s.fsf@gmail.com> X-Mailer: Mulberry/4.0.8 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: Re: ZFS install from -CURRENT snapshot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 May 2011 22:48:06 -0000 --As of May 31, 2011 1:21:49 AM +0300, George Kontostanos is alleged to have said: > Bingo! That did it. I will update the guide soon. > > @Daniel my apologies it seems that another typo is preventing you from > booting. You have to set the bootfs in the pool. > > zpool set bootfs=zroot zroot --As for the rest, it is mine. I'd actually caught that one... (Yesterday afternoon.) I was hoping this was something people had seen before. At this point, I've been trying to get a FreeBSD+ZFS install on this box for about a month - including spending much of my first vacation in two years on it - and I know that even if I do manage to do so I'll still have a problem with the screen resolution. (Sandy Bridge integrated graphics. It works in VERSA mode, but doesn't detect the native mode.) I've decided to call it quits for now. A current Linux runs fine. The power management isn't as good as FreeBSD, I'm loosing the ZFS coolness, and the other advantages of a FreeBSD box over Linux, but it means I've got a working laptop for the moment. I'll revisit putting FreeBSD on it sometime in the future, once the hardware isn't quite so current-edge. For now, I've invested too much time into just getting this running. George, a couple other notes on your walkthrough: (I'd decided to wait until I was done to go over all of these.) cd /tmp && copy -R * /boot # Needs to be cp. zpool create -O mountpoint=/mnt zroot /dev/gpt/disk0 # Will avoid the export/import later. And in theory it doesn't make *much* difference, but setting the checksum before creating usr, var, and tmp is slightly better practice. (The directory entries are checksummed as well, which would be the only difference. If any files were created in between they'd get the fletcher2 checksum.) Daniel T. Staal --------------------------------------------------------------- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. --------------------------------------------------------------- From owner-freebsd-current@FreeBSD.ORG Mon May 30 23:18:16 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 36B841065678 for ; Mon, 30 May 2011 23:18:16 +0000 (UTC) (envelope-from gkontos.mail@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id EB3C28FC1C for ; Mon, 30 May 2011 23:18:15 +0000 (UTC) Received: by iwn33 with SMTP id 33so4830981iwn.13 for ; Mon, 30 May 2011 16:18:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=ylWRVYOGjtCdr5jszUbR+US4tIbqoJ+qbO9km8taJao=; b=CUocWQ7y7Di1JQ6ehyLKhzO8G7dIZiHWZtvUCs79MfDt3KXTyjq6hy61SYkiNIClB2 OC/pHR34g7R9GCUksL1OTvhQgPdBqwAhAm20W1yzYRUH6QLNbRPWpXWbXpOvY7qCtP1m FqQzt/se/q1I7Lp/Z0st96skBRNzJSiWnSs74= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=tzz7GpGiBq5c/zNTcuaifdCjR60DMEI0h+ZCZUFQg/wOUS8tB+4UnZ+lLgqhCiKFcK U37O8hADbokOEqjL5iftyu2orpnfy9+iMO7geL+6cAZ8VuYOCbl/TbuekTfhB7mAstOq tFahyb9N4LRz18mwQsvTwljnTjDHGAF3+k4l8= MIME-Version: 1.0 Received: by 10.42.28.200 with SMTP id o8mr8263183icc.312.1306797493524; Mon, 30 May 2011 16:18:13 -0700 (PDT) Received: by 10.231.215.42 with HTTP; Mon, 30 May 2011 16:18:13 -0700 (PDT) In-Reply-To: References: <20110529040800.GA44286@sysmon.tcworks.net> <4DE1EDD8.5050003@FreeBSD.org> <3E1EB5E79BD1A6B775EB8387@mac-pro.magehandbook.com> <4DE3B72F.8030203@digsys.bg> <868vtnub8s.fsf@gmail.com> Date: Tue, 31 May 2011 02:18:13 +0300 Message-ID: From: George Kontostanos To: Daniel Staal Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: FreeBSD-Current Subject: Re: ZFS install from -CURRENT snapshot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 May 2011 23:18:16 -0000 oops typos, typos! That's one of the bad things that happens when you type without having the copy - paste functionality. On Tue, May 31, 2011 at 1:48 AM, Daniel Staal wrote: > --As of May 31, 2011 1:21:49 AM +0300, George Kontostanos is alleged to > have said: > > Bingo! That did it. I will update the guide soon. >> >> @Daniel my apologies it seems that another typo is preventing you from >> booting. You have to set the bootfs in the pool. >> >> zpool set bootfs=zroot zroot >> > > --As for the rest, it is mine. > > I'd actually caught that one... (Yesterday afternoon.) > > I was hoping this was something people had seen before. At this point, > I've been trying to get a FreeBSD+ZFS install on this box for about a month > - including spending much of my first vacation in two years on it - and I > know that even if I do manage to do so I'll still have a problem with the > screen resolution. (Sandy Bridge integrated graphics. It works in VERSA > mode, but doesn't detect the native mode.) > > I've decided to call it quits for now. A current Linux runs fine. The > power management isn't as good as FreeBSD, I'm loosing the ZFS coolness, and > the other advantages of a FreeBSD box over Linux, but it means I've got a > working laptop for the moment. I'll revisit putting FreeBSD on it sometime > in the future, once the hardware isn't quite so current-edge. For now, I've > invested too much time into just getting this running. > > George, a couple other notes on your walkthrough: (I'd decided to wait > until I was done to go over all of these.) > cd /tmp && copy -R * /boot # Needs to be cp. > zpool create -O mountpoint=/mnt zroot /dev/gpt/disk0 # Will avoid the > export/import later. > > And in theory it doesn't make *much* difference, but setting the checksum > before creating usr, var, and tmp is slightly better practice. (The > directory entries are checksummed as well, which would be the only > difference. If any files were created in between they'd get the fletcher2 > checksum.) > > > Daniel T. Staal > > --------------------------------------------------------------- > This email copyright the author. Unless otherwise noted, you > are expressly allowed to retransmit, quote, or otherwise use > the contents for non-commercial purposes. This copyright will > expire 5 years after the author's death, or in 30 years, > whichever is longer, unless such a period is in excess of > local copyright law. > --------------------------------------------------------------- > -- George Kontostanos aisecure.net From owner-freebsd-current@FreeBSD.ORG Tue May 31 08:10:50 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E1BFC106564A; Tue, 31 May 2011 08:10:49 +0000 (UTC) (envelope-from mike@reifenberger.com) Received: from mail-out.m-online.net (mail-out.m-online.net [212.18.0.9]) by mx1.freebsd.org (Postfix) with ESMTP id 7089B8FC16; Tue, 31 May 2011 08:10:48 +0000 (UTC) Received: from frontend1.mail.m-online.net (unknown [192.168.8.180]) by mail-out.m-online.net (Postfix) with ESMTP id C36A51C08E16; Tue, 31 May 2011 10:10:47 +0200 (CEST) Received: from localhost (dynscan1.mnet-online.de [192.168.8.164]) by mail.m-online.net (Postfix) with ESMTP id AD5E61C00062; Tue, 31 May 2011 10:10:47 +0200 (CEST) X-Virus-Scanned: amavisd-new at mnet-online.de Received: from mail.mnet-online.de ([192.168.8.180]) by localhost (dynscan1.mail.m-online.net [192.168.8.164]) (amavisd-new, port 10024) with ESMTP id KCXO7yqQWA6O; Tue, 31 May 2011 10:10:43 +0200 (CEST) Received: from mail.reifenberger.com (ppp-93-104-55-65.dynamic.mnet-online.de [93.104.55.65]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.mnet-online.de (Postfix) with ESMTPS; Tue, 31 May 2011 10:10:43 +0200 (CEST) Received: by mail.reifenberger.com (Postfix, from userid 1001) id 318C43108D; Tue, 31 May 2011 10:10:43 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mail.reifenberger.com (Postfix) with ESMTP id 267053108C; Tue, 31 May 2011 10:10:43 +0200 (CEST) Date: Tue, 31 May 2011 10:10:42 +0200 (CEST) From: Michael Reifenberger To: Garrett Cooper In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: pjd@freebsd.org, FreeBSD-Current Subject: Re: mount root from zfs fails under current with "error 6" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2011 08:10:50 -0000 On Mon, 30 May 2011, Garrett Cooper wrote: ... > dmesg for starters (boot -v if possible) would be extremely > helpful. More details like your disk subsystem that you're booting off > of, whether you're using GPT/MBR when booting via ZFS, etc would be > helpful. Also being able to better trace down the root cause would be > nice (not being able to boot a recent kernel, but being able to boot a > kernel from almost a month ago is unfortunately a bit of a non-starter > for tracking down the actual issue because that's such a long span of > time). Ok. Verbose boot output is available here: http://people.freebsd.org/~mr/boot_fail.txt http://people.freebsd.org/~mr/boot_success.txt Verbose pciconf output: http://people.freebsd.org/~mr/pciconf.txt Disksetup: Im booting from 4 equally GPT partitioned 3TiB Disks: (fs)(root) gpart show ada0 => 34 5860533101 ada0 GPT (2.7T) 34 990 1 freebsd-boot (495k) 1024 2098176 2 freebsd-swap (1.0G) 2099200 5858433928 3 freebsd-zfs (2.7T) 5860533128 7 - free - (3.5k) (fs)(root) zpool status boot pool: boot state: ONLINE scan: scrub repaired 0 in 5h2m with 0 errors on Mon May 30 08:03:43 2011 config: NAME STATE READ WRITE CKSUM boot ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 ada0p3 ONLINE 0 0 0 ada1p3 ONLINE 0 0 0 ada2p3 ONLINE 0 0 0 ada3p3 ONLINE 0 0 0 errors: No known data errors (fs)(root) zpool get bootfs boot NAME PROPERTY VALUE SOURCE boot bootfs boot/ROOT/root local # loader.conf: ... vfs.root.mountfrom="zfs:boot/ROOT/root" ... BTW: After suspecting the new ada alias code I set: kern.cam.ada.legacy_aliases=0 But without effect. @pjd: Could you tell why/when the ZFS mount code errors with ENXIO? Thanks all for investigating! Bye/2 --- Michael Reifenberger Michael@Reifenberger.com http://www.Reifenberger.com From owner-freebsd-current@FreeBSD.ORG Tue May 31 11:42:22 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 14125106566B; Tue, 31 May 2011 11:42:22 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id F0AAC8FC15; Tue, 31 May 2011 11:42:20 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id OAA08487; Tue, 31 May 2011 14:42:19 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <4DE4D41B.1000000@FreeBSD.org> Date: Tue, 31 May 2011 14:42:19 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.17) Gecko/20110504 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: Attilio Rao References: <4DD3F662.9040603@FreeBSD.org> <4DD54C18.8050305@FreeBSD.org> <4DDA8B2A.6010500@FreeBSD.org> <4DDD2B34.5070702@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: "freebsd-current@freebsd.org" , "freebsd-arch@freebsd.org" Subject: Re: [rfc] remove hlt_cpus et al sysctls and related code X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2011 11:42:22 -0000 on 29/05/2011 06:06 Attilio Rao said the following: > 2011/5/28 Attilio Rao : >> 2011/5/25 Andriy Gapon : >>> The patch is here: >>> http://people.freebsd.org/~avg/cpu-offline-sysctl.diff >>> It should implement the strategy described above. >>> >> >> I don't see the point in keeping alive mp_grab_cpu_hlt() and >> supporting, actually. >> >> On the top of your patch I made some modifies that use directly >> ap_watchdog() in cpu_idle() which I think is better for the time >> being: >> http://www.freebsd.org/~attilio/avg_rem_cpuhlt.diff Yes, I agree, thank you. >> If you are happy with it, just commit as long as Garrett tests that. OK. Waiting for test feedback. >> On a second round of changes we can discuss mp_watchdog and eventual >> removal / improvements to it. > > I almost forgot: this change would also require an UPDATE entry, where > you explicitly mention the "new" way to deal with CPUs. Use your > prefer wording. Sure. Thank you! BTW, I guess there would be no reason to MFC this change? -- Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Tue May 31 12:34:28 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EE468106564A for ; Tue, 31 May 2011 12:34:27 +0000 (UTC) (envelope-from glz@hidden-powers.com) Received: from mail.hidden-powers.com (mail.hidden-powers.com [213.242.135.162]) by mx1.freebsd.org (Postfix) with ESMTP id 667608FC14 for ; Tue, 31 May 2011 12:34:27 +0000 (UTC) Received: from mail.hidden-powers.com (localhost [127.0.0.1]) by dkim.hidden-powers.com (Postfix) with ESMTP id 240786F056; Tue, 31 May 2011 14:34:25 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=hidden-powers.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type; s=selector1; bh=Fntyc5V42x6MjUHf7LOo Eu4q6C4=; b=oU/U/8Q6yZJwqPqGi9l34qFcoKkhUkSbnVM3DjoBSnDMesMgQWXA /zhMb6cm1+eCcJvTcZeGtBEI9ZjN5JyAziYPNIvfAT9Zd030WtO6u7TzqGYBcoHL saLi6Y2EgP6JepM4LMPaobWuStkQJvN8WttK1EP7KjOIHOU4yQF3a/o= Received: from [172.16.2.57] (gw01.ismobile.com [212.73.186.202]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.hidden-powers.com (Postfix) with ESMTPSA id 4703C6F055; Tue, 31 May 2011 14:34:24 +0200 (CEST) Date: Tue, 31 May 2011 14:34:22 +0200 From: Goran Lowkrantz To: freebsd-current@freebsd.org Message-ID: <1DE98FADA8318788A5DD5505@[172.16.2.57]> In-Reply-To: <40413420.946642.1306625323806.JavaMail.root@erie.cs.uoguelph.ca> References: <40413420.946642.1306625323806.JavaMail.root@erie.cs.uoguelph.ca> X-Mailer: Mulberry/4.0.8 (Mac OS X) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="==========C4E6BEA5E50909674CDD==========" Cc: Rick Macklem Subject: Re: Testing new nfs and VIMAGE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2011 12:34:28 -0000 --==========C4E6BEA5E50909674CDD========== Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline For the list: Attached patch works. /glz --On May 28, 2011 19:28:43 -0400 Rick Macklem wrote: >> It worked when I added CURVNET_SET/CURVNET_RESTORE around the >> RTFREE_LOCKED >> macro too. Attached a complete patch. >> >> Thank you. >> > and thanks for finding/reporting/testing it. I've attached another > variant of the patch that maybe you could try? > (I don't think it's necessary to do twice, so I just moved the > CURVNET_RESTORE() to after the RTFREE_LOCKED() macro instead.) > > I don't know if you are a committer for this stuff or not? > If you are feel free to commit whichever variant of the patch you > find works and prefer. > > If not, maybe bz@ could either commit it or review it? > (or whoever is doing the VIMAGE stuff these days?) > > rick --==========C4E6BEA5E50909674CDD========== Content-Type: text/x-patch; name="curvnet.patch" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="curvnet.patch"; size=1145 LS0tIGZzL25mc2NsaWVudC9uZnNfY2xwb3J0LmMuc2F2CTIwMTEtMDUtMDQgMTk6MTI6MTAuMDAw MDAwMDAwIC0wNDAwCisrKyBmcy9uZnNjbGllbnQvbmZzX2NscG9ydC5jCTIwMTEtMDUtMjggMTk6 MTQ6MzAuMDAwMDAwMDAwIC0wNDAwCkBAIC05NDMsNiArOTQzLDcgQEAgbmZzY2xfZ2V0bXlpcChz dHJ1Y3QgbmZzbW91bnQgKm5tcCwgaW50IAogCQlzYWQuc2luX2ZhbWlseSA9IEFGX0lORVQ7CiAJ CXNhZC5zaW5fbGVuID0gc2l6ZW9mIChzdHJ1Y3Qgc29ja2FkZHJfaW4pOwogCQlzYWQuc2luX2Fk ZHIuc19hZGRyID0gc2luLT5zaW5fYWRkci5zX2FkZHI7CisJCUNVUlZORVRfU0VUKFREX1RPX1ZO RVQoY3VydGhyZWFkKSk7CiAJCXJ0ID0gcnRhbGxvYzEoKHN0cnVjdCBzb2NrYWRkciAqKSZzYWQs IDAsIDBVTCk7CiAJCWlmIChydCAhPSBOVUxMKSB7CiAJCQlpZiAocnQtPnJ0X2lmcCAhPSBOVUxM ICYmCkBAIC05NTYsNiArOTU3LDcgQEAgbmZzY2xfZ2V0bXlpcChzdHJ1Y3QgbmZzbW91bnQgKm5t cCwgaW50IAogCQkJfQogCQkJUlRGUkVFX0xPQ0tFRChydCk7CiAJCX0KKwkJQ1VSVk5FVF9SRVNU T1JFKCk7CiAjaWZkZWYgSU5FVDYKIAl9IGVsc2UgaWYgKG5tcC0+bm1fbmFtLT5zYV9mYW1pbHkg PT0gQUZfSU5FVDYpIHsKIAkJc3RydWN0IHNvY2thZGRyX2luNiBzYWQ2LCAqc2luNjsKQEAgLTk2 Niw2ICs5NjgsNyBAQCBuZnNjbF9nZXRteWlwKHN0cnVjdCBuZnNtb3VudCAqbm1wLCBpbnQgCiAJ CXNhZDYuc2luNl9mYW1pbHkgPSBBRl9JTkVUNjsKIAkJc2FkNi5zaW42X2xlbiA9IHNpemVvZiAo c3RydWN0IHNvY2thZGRyX2luNik7CiAJCXNhZDYuc2luNl9hZGRyID0gc2luNi0+c2luNl9hZGRy OworCQlDVVJWTkVUX1NFVChURF9UT19WTkVUKGN1cnRocmVhZCkpOwogCQlydCA9IHJ0YWxsb2Mx KChzdHJ1Y3Qgc29ja2FkZHIgKikmc2FkNiwgMCwgMFVMKTsKIAkJaWYgKHJ0ICE9IE5VTEwpIHsK IAkJCWlmIChydC0+cnRfaWZwICE9IE5VTEwgJiYKQEAgLTk4MCw2ICs5ODMsNyBAQCBuZnNjbF9n ZXRteWlwKHN0cnVjdCBuZnNtb3VudCAqbm1wLCBpbnQgCiAJCQl9CiAJCQlSVEZSRUVfTE9DS0VE KHJ0KTsKIAkJfQorCQlDVVJWTkVUX1JFU1RPUkUoKTsKICNlbmRpZgogCX0KIAlyZXR1cm4gKHJl dHApOwo= --==========C4E6BEA5E50909674CDD==========-- From owner-freebsd-current@FreeBSD.ORG Tue May 31 13:34:46 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5EFD21065670; Tue, 31 May 2011 13:34:46 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id DEB808FC08; Tue, 31 May 2011 13:34:45 +0000 (UTC) Received: by gyg13 with SMTP id 13so2604228gyg.13 for ; Tue, 31 May 2011 06:34:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=LVSmB85qYlHDaL3fZa8ZoC5JsBnOZaedd7+vTmFvHlU=; b=wZvG5a/CyefhwZEVJiRJSXCcbU1qhoq4r5qAHCSry+zQY8mmP2o8oUzsTySD0v58zK hYMSuRy9To5SJtHf3BMyJGqPN/6U0d/ho+LOHCvzZEd7XqyqjPbNdnRKK7kLL6iujbsD LgAlAb8UgQuzhuPjdY+8Aer+UjKuynFzEK8B8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=lKhSKv0dkbePOQdP6Qzp/Yql4T4SkMuXPSbFIKV4JauzlBe8DLFySBz+Y2H3YAIH1h JkdB9kaTbqnamB0LDbXkXjRMgGNDLs6GNK/hEshrJL41Kn7vjCayx1s5mJBAILfbDu6l mMUAVq19sCyEvPf9Jn+pFQ+g5G6ljRilEqWSI= MIME-Version: 1.0 Received: by 10.236.161.194 with SMTP id w42mr6771364yhk.237.1306848885146; Tue, 31 May 2011 06:34:45 -0700 (PDT) Sender: asmrookie@gmail.com Received: by 10.236.103.136 with HTTP; Tue, 31 May 2011 06:34:44 -0700 (PDT) In-Reply-To: <4DE4D41B.1000000@FreeBSD.org> References: <4DD3F662.9040603@FreeBSD.org> <4DD54C18.8050305@FreeBSD.org> <4DDA8B2A.6010500@FreeBSD.org> <4DDD2B34.5070702@FreeBSD.org> <4DE4D41B.1000000@FreeBSD.org> Date: Tue, 31 May 2011 09:34:44 -0400 X-Google-Sender-Auth: ArqOaQt3weQvcGly6vcpJn3F6AM Message-ID: From: Attilio Rao To: Andriy Gapon Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-current@freebsd.org" , "freebsd-arch@freebsd.org" Subject: Re: [rfc] remove hlt_cpus et al sysctls and related code X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2011 13:34:46 -0000 2011/5/31 Andriy Gapon : > on 29/05/2011 06:06 Attilio Rao said the following: >> 2011/5/28 Attilio Rao : >>> 2011/5/25 Andriy Gapon : >>>> The patch is here: >>>> http://people.freebsd.org/~avg/cpu-offline-sysctl.diff >>>> It should implement the strategy described above. >>>> >>> >>> I don't see the point in keeping alive mp_grab_cpu_hlt() and >>> supporting, actually. >>> >>> On the top of your patch I made some modifies that use directly >>> ap_watchdog() in cpu_idle() which I think is better for the time >>> being: >>> http://www.freebsd.org/~attilio/avg_rem_cpuhlt.diff > > Yes, I agree, thank you. > >>> If you are happy with it, just commit as long as Garrett tests that. > > > OK. =C2=A0Waiting for test feedback. > >>> On a second round of changes we can discuss mp_watchdog and eventual >>> removal / improvements to it. >> >> I almost forgot: this change would also require an UPDATE entry, where >> you explicitly mention the "new" way to deal with CPUs. Use your >> prefer wording. > > Sure. =C2=A0Thank you! > > BTW, I guess there would be no reason to MFC this change? You mean no reason to not MFC it? In general, I think that users may expect those sysctls to be alive (IMHO we should consider sysctls to be part of the userland API) so that we can add some more, but we should not axe them. So probabilly MFC is not the best option here. Attilio --=20 Peace can only be achieved by understanding - A. Einstein From owner-freebsd-current@FreeBSD.ORG Tue May 31 13:40:48 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BD939106564A; Tue, 31 May 2011 13:40:48 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id A56C18FC14; Tue, 31 May 2011 13:40:47 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id QAA11207; Tue, 31 May 2011 16:40:46 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <4DE4EFDD.8070803@FreeBSD.org> Date: Tue, 31 May 2011 16:40:45 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.17) Gecko/20110504 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: Attilio Rao References: <4DD3F662.9040603@FreeBSD.org> <4DD54C18.8050305@FreeBSD.org> <4DDA8B2A.6010500@FreeBSD.org> <4DDD2B34.5070702@FreeBSD.org> <4DE4D41B.1000000@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: "freebsd-current@freebsd.org" , "freebsd-arch@freebsd.org" Subject: Re: [rfc] remove hlt_cpus et al sysctls and related code X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2011 13:40:48 -0000 on 31/05/2011 16:34 Attilio Rao said the following: > 2011/5/31 Andriy Gapon : >> on 29/05/2011 06:06 Attilio Rao said the following: >>> 2011/5/28 Attilio Rao : >>>> 2011/5/25 Andriy Gapon : >>>>> The patch is here: >>>>> http://people.freebsd.org/~avg/cpu-offline-sysctl.diff >>>>> It should implement the strategy described above. >>>>> >>>> >>>> I don't see the point in keeping alive mp_grab_cpu_hlt() and >>>> supporting, actually. >>>> >>>> On the top of your patch I made some modifies that use directly >>>> ap_watchdog() in cpu_idle() which I think is better for the time >>>> being: >>>> http://www.freebsd.org/~attilio/avg_rem_cpuhlt.diff >> >> Yes, I agree, thank you. >> >>>> If you are happy with it, just commit as long as Garrett tests that. >> >> >> OK. Waiting for test feedback. >> >>>> On a second round of changes we can discuss mp_watchdog and eventual >>>> removal / improvements to it. >>> >>> I almost forgot: this change would also require an UPDATE entry, where >>> you explicitly mention the "new" way to deal with CPUs. Use your >>> prefer wording. >> >> Sure. Thank you! >> >> BTW, I guess there would be no reason to MFC this change? > > You mean no reason to not MFC it? I meant exactly what I asked :-) As in: I didn't see any reason for MFC. > In general, I think that users may expect those sysctls to be alive > (IMHO we should consider sysctls to be part of the userland API) so > that we can add some more, but we should not axe them. > So probabilly MFC is not the best option here. -- Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Tue May 31 14:05:08 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1E1F2106566B for ; Tue, 31 May 2011 14:05:08 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from mail.ebusiness-leidinger.de (mail.ebusiness-leidinger.de [217.11.53.44]) by mx1.freebsd.org (Postfix) with ESMTP id 9ED168FC16 for ; Tue, 31 May 2011 14:05:07 +0000 (UTC) Received: from outgoing.leidinger.net (p5B155924.dip.t-dialin.net [91.21.89.36]) by mail.ebusiness-leidinger.de (Postfix) with ESMTPSA id E141884401B; Tue, 31 May 2011 16:04:53 +0200 (CEST) Received: from webmail.leidinger.net (webmail.Leidinger.net [IPv6:fd73:10c7:2053:1::3:102]) by outgoing.leidinger.net (Postfix) with ESMTP id 3965E331D; Tue, 31 May 2011 16:04:51 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=Leidinger.net; s=outgoing-alex; t=1306850691; bh=COQdtVaI4GWZUD/OYVUyRyWYWUCFuS7xZ7hzLtJA1O8=; h=Message-ID:Date:From:To:Cc:Subject:References:In-Reply-To: MIME-Version:Content-Type:Content-Transfer-Encoding; b=EVBZinlX8sP6Ggr38yYYD3r5XAbs7jVwuWtq+gZEDJ0b+MzDxHOE12mQpqQjbqu1q Go/lLuM8zWOw4WlJ222H5qU+fZBToJQ03v5E+2sz4QKJYGeeazPm8Jr4bmjqQ/2Yu+ EKYuszRYf8z9IuL7vxJqlVhdBoNQVmpjVpqKHnt5KzCTpn/uCjumjSKgWLI3hOO3yc 6N0ApLgHYAM5FM9QVeXuZrH+N5hvrz3ovfsUJCmcec/nP0Gqmb1HmF2JYY7Mt7Mwgv ysOeeQU7R6/4RRq8PvG6pWgoG5uRWTcgO8NXamvsMPbwyG5RzOj1n60tYMFRRloOQU mpLEHz+q6hmOQ== Received: (from www@localhost) by webmail.leidinger.net (8.14.4/8.14.4/Submit) id p4VE4oSJ006987; Tue, 31 May 2011 16:04:50 +0200 (CEST) (envelope-from Alexander@Leidinger.net) X-Authentication-Warning: webmail.leidinger.net: www set sender to Alexander@Leidinger.net using -f Received: from pslux.ec.europa.eu (pslux.ec.europa.eu [158.169.9.14]) by webmail.leidinger.net (Horde Framework) with HTTP; Tue, 31 May 2011 16:04:49 +0200 Message-ID: <20110531160449.19667dub2cfejdkx@webmail.leidinger.net> Date: Tue, 31 May 2011 16:04:49 +0200 From: Alexander Leidinger To: Daniel Staal References: <20110529040800.GA44286@sysmon.tcworks.net> <4DE1EDD8.5050003@FreeBSD.org> <3E1EB5E79BD1A6B775EB8387@mac-pro.magehandbook.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Dynamic Internet Messaging Program (DIMP) H3 (1.1.6) X-EBL-MailScanner-Information: Please contact the ISP for more information X-EBL-MailScanner-ID: E141884401B.AEADF X-EBL-MailScanner: Found to be clean X-EBL-MailScanner-SpamCheck: not spam, spamhaus-ZEN, SpamAssassin (not cached, score=0.577, required 6, autolearn=disabled, DKIM_SIGNED 0.10, DKIM_VALID -0.10, DKIM_VALID_AU -0.10, J_CHICKENPOX_55 0.60, TW_ZF 0.08) X-EBL-MailScanner-From: alexander@leidinger.net X-EBL-MailScanner-Watermark: 1307455494.52541@mzfKyVJYBBDM+OEd4dGSqw X-EBL-Spam-Status: No Cc: freebsd-current@freebsd.org, George Kontostanos Subject: Re: ZFS install from -CURRENT snapshot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2011 14:05:08 -0000 Quoting Daniel Staal (from Mon, 30 May 2011 11:01:06 -0400): > --As of May 29, 2011 9:10:57 AM -0400, George Kontostanos, > freebsd-current@freebsd.org is alleged to have said: > >> --As of May 29, 2011 12:06:30 PM +0300, George Kontostanos is alleged to >> have said: >> >>> The new bsdinstall has a different layout so the previous guides don't >>> work. I have prepared one that works for recent 9-Current at : >>> >>> "http://www.aisecure.net/?p=132" >> >> --As for the rest, it is mine. >> >> Thanks, that's about what I expected the install procedure to be at this >> point. Nice to have the reminder about the zpool.cache. (Do I have to >> use the Live CD mode? Can I use shell mode instead?) > > --As for the rest, it is mine. > > Ok, I've tried shell mode and live CD mode. I've re-partitioned my > disks several different ways. > > Nothing gets me a system that will actually boot. Or even recognize > that there is an OS loaded anywhere. Help? I did it like this: http://www.leidinger.net/blog/2011/05/03/another-root-on-zfs-howto-optimized-for-4k-sector-drives/ > (My preferred partitioning: > > ada1: > 1 freebsd-boot > 2 freebsd-swap 8G > 3 freebsd-zfs 4G (zil) > 4 freebsd-zfs 17G (cache) > > ada0: Managed by ZFS, ~250G Main filesystem. You show the boot partition on ada1, but you do not tell if ada0 has a boot partition too or not. Did you try to have the boot partition on the same disk as the pool? I hope ada1 is a SSD. If not, it does not make much sense to have a cache there (a cache needs to have lower latency than the main pool, I do not expect that just another spindle gives a significant perf improvement). Bye, Alexander. -- Please don't put a strain on our friendship by asking me to do something for you. http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 From owner-freebsd-current@FreeBSD.ORG Tue May 31 15:01:29 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C66601065673 for ; Tue, 31 May 2011 15:01:29 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 9D75D8FC13 for ; Tue, 31 May 2011 15:01:29 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 52A8F46B3C; Tue, 31 May 2011 11:01:29 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 8A4A68A02B; Tue, 31 May 2011 11:01:28 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Date: Tue, 31 May 2011 10:39:37 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110325; KDE/4.5.5; amd64; ; ) References: <201105260940.37035.jhb@freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201105311039.37935.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Tue, 31 May 2011 11:01:29 -0400 (EDT) Cc: "deeptech71@gmail.com" Subject: Re: pcib allocation failure X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2011 15:01:29 -0000 On Saturday, May 28, 2011 9:45:48 pm deeptech71@gmail.com wrote: > On Thu, May 26, 2011 at 3:40 PM, John Baldwin wrote: > > Ohh, you have two devices behind this bridge that have prefetch ranges. > > > > As a hack, can you try this: > > > > Index: pci_pci.c > > =================================================================== > > --- pci_pci.c (revision 222285) > > +++ pci_pci.c (working copy) > > @@ -162,8 +162,13 @@ pcib_write_windows(struct pcib_softc *sc, int mask > > { > > device_t dev; > > uint32_t val; > > + uint16_t cmd; > > > > dev = sc->dev; > > + cmd = pci_read_config(dev, PCIR_COMMAND, 2); > > + if (cmd & (PCIM_CMD_PORTEN | PCIM_CMD_MEMEN)) > > + pci_write_config(dev, PCIR_COMMAND, > > + cmd & ~(PCIM_CMD_PORTEN | PCIM_CMD_MEMEN), 2); > > if (sc->io.valid && mask & WIN_IO) { > > val = pci_read_config(dev, PCIR_IOBASEL_1, 1); > > if ((val & PCIM_BRIO_MASK) == PCIM_BRIO_32) { > > @@ -192,6 +197,8 @@ pcib_write_windows(struct pcib_softc *sc, int mask > > pci_write_config(dev, PCIR_PMBASEL_1, sc->pmem.base >> 16, 2); > > pci_write_config(dev, PCIR_PMLIMITL_1, sc->pmem.limit >> 16, 2); > > } > > + if (cmd & (PCIM_CMD_PORTEN | PCIM_CMD_MEMEN)) > > + pci_write_config(dev, PCIR_COMMAND, cmd, 2); > > } > > > > static void > > @@ -337,6 +344,9 @@ pcib_probe_windows(struct pcib_softc *sc) > > pci_read_config(dev, PCIR_PMLIMITL_1, 2)); > > max = 0xffffffff; > > } > > + /* XXX: Testing hack */ > > + if (device_get_unit(sc->sc_dev) == 1) > > i'm assuming that "sc->sc_dev" should be "dev" (this fixes a compilation error). > > > + sc->pmem.limit = 0xefffffff; > > pcib_alloc_window(sc, &sc->pmem, SYS_RES_MEMORY, > > RF_PREFETCHABLE, max); > > } > > that seems to work! Hmmm, ok. This may not be easy to fix properly for the time being as it requires the PCI-PCI bridge to scan all the devices behind the bus to find what resource ranges are actually needed before programming its windows. Note that this is all to work around your BIOS being very broken. :( > btw, is my machine a test-pig for an upcoming change to the PCI bus driver? Well, it's been a good test thus far. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Tue May 31 15:42:16 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C4345106566C for ; Tue, 31 May 2011 15:42:16 +0000 (UTC) (envelope-from ken@kdm.org) Received: from nargothrond.kdm.org (nargothrond.kdm.org [70.56.43.81]) by mx1.freebsd.org (Postfix) with ESMTP id 875B08FC18 for ; Tue, 31 May 2011 15:42:16 +0000 (UTC) Received: from nargothrond.kdm.org (localhost [127.0.0.1]) by nargothrond.kdm.org (8.14.2/8.14.2) with ESMTP id p4VFgFhL046187; Tue, 31 May 2011 09:42:15 -0600 (MDT) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.14.2/8.14.2/Submit) id p4VFgFYh046186; Tue, 31 May 2011 09:42:15 -0600 (MDT) (envelope-from ken) Date: Tue, 31 May 2011 09:42:15 -0600 From: "Kenneth D. Merry" To: Julian Elischer Message-ID: <20110531154215.GA45877@nargothrond.kdm.org> References: <20110527224523.GA77922@nargothrond.kdm.org> <4DE13E6A.20202@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4DE13E6A.20202@freebsd.org> User-Agent: Mutt/1.4.2i Cc: current@freebsd.org Subject: Re: message buffer scrambling fix X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2011 15:42:16 -0000 On Sat, May 28, 2011 at 11:26:50 -0700, Julian Elischer wrote: > On 5/27/11 3:45 PM, Kenneth D. Merry wrote: > >Hey folks, > > > >I have attached some patches to the kernel message buffer code (this > >affects dmesg(8) output as well as kernel messages that go to the syslog) > >to address log scrambling. > > > >This fixes the same issue that 'options PRINTF_BUFR_SIZE=128' fixes for the > >console. > > > >The problem is that you can have multiple kernel threads writing to the > >message buffer at the same time, and so their characters will get > >interleaved. All of the characters will get in there, because they're > >written with atomic operations, but the output might looked scrambled. > > > >So the fix is to use the same stack buffer that is used for the console > >output (so the stack size doesn't increase), and use a spin lock instead of > >atomic operations to insert the string into the message buffer. > > > >The result is that dmesg and syslog output should look the same as the > >console output. As long as individual kernel prints fit in the printf > >buffer size, they will be put into the message buffer atomically. > > > >I also fixed a couple of other long-standing issues. putcons() (in > >subr_prf.c) was adding a carriage return before calling cnputs(). But > >cnputs() calls cnputc(), which adds a carriage return before every newline. > >So much of the console output (the part that came from putcons() at least) > >had two carriage returns at the end. > > > >The other issue was that log_console() was inserting a newline for any > >console write that didn't already have one at the end. The issue with that > >can be seen if you do a 'dmesg -a' and compare that to the console output. > > > >You'll see something like this on the console: > > > >Updating motd:. > > > >But this in dmesg -a: > > > >Updating motd: > >. > > > >That is because "Updating motd:" is written first, log_console() appends a > >newline, and then ".\n" is written. > > > >I added a loader tunable and sysctl to turn the old behavior back on > >(kern.log_console_add_linefeed) if you want the old behavior, but I think > >we should be able to safely remove it. > > > >Also, the new msgbuf_addstr() function allows the caller to optionally ask > >for carriage returns to be stripped out. However, in my testing I haven't > >seen any carriage returns to strip. > > > >Let me know if you have any comments. I'm planning to check this into head > >next week. > > looks good.. as long as we don't end up with the behaviour that I > think I see on > Linux (it's hard to tell sometimes) where the last message (the one > you really > want to see) doesn't make it out. Everything passed into the kernel printf() call should make it out to the console, message buffer, etc. before the printf call completes. The only way that wouldn't happen is if spin locks break for some reason. One thing I forgot to mention is that I think the PRINTF_BUFR_SIZE option should be made non-optional. Even on smaller embedded machines, I think we should be able to afford the 128 bytes of stack space to keep messages from getting scrambled. Ken -- Kenneth Merry ken@FreeBSD.ORG From owner-freebsd-current@FreeBSD.ORG Tue May 31 17:38:53 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E3E2D106566C; Tue, 31 May 2011 17:38:53 +0000 (UTC) (envelope-from mike@reifenberger.com) Received: from mail-out.m-online.net (mail-out.m-online.net [212.18.0.10]) by mx1.freebsd.org (Postfix) with ESMTP id 995FE8FC12; Tue, 31 May 2011 17:38:53 +0000 (UTC) Received: from frontend1.mail.m-online.net (frontend1.mail.intern.m-online.net [192.168.8.180]) by mail-out.m-online.net (Postfix) with ESMTP id 88ABC188B5BA; Tue, 31 May 2011 19:38:51 +0200 (CEST) Received: from localhost (dynscan1.mnet-online.de [192.168.8.164]) by mail.m-online.net (Postfix) with ESMTP id DAC7F1C0005B; Tue, 31 May 2011 19:38:51 +0200 (CEST) X-Virus-Scanned: amavisd-new at mnet-online.de Received: from mail.mnet-online.de ([192.168.8.180]) by localhost (dynscan1.mail.m-online.net [192.168.8.164]) (amavisd-new, port 10024) with ESMTP id kiMbL4oK4jew; Tue, 31 May 2011 19:38:51 +0200 (CEST) Received: from mail.reifenberger.com (ppp-93-104-55-65.dynamic.mnet-online.de [93.104.55.65]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.mnet-online.de (Postfix) with ESMTPS; Tue, 31 May 2011 19:38:51 +0200 (CEST) Received: by mail.reifenberger.com (Postfix, from userid 1001) id 7C085310B4; Tue, 31 May 2011 19:38:50 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mail.reifenberger.com (Postfix) with ESMTP id 6F73B310B3; Tue, 31 May 2011 19:38:50 +0200 (CEST) Date: Tue, 31 May 2011 19:38:50 +0200 (CEST) From: Michael Reifenberger To: pjd@freebsd.org In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Garrett Cooper , FreeBSD-Current Subject: Re: mount root from zfs fails under current with "error 6" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2011 17:38:54 -0000 Hi, On Tue, 31 May 2011, Michael Reifenberger wrote: ... > (fs)(root) gpart show ada0 > => 34 5860533101 ada0 GPT (2.7T) > 34 990 1 freebsd-boot (495k) > 1024 2098176 2 freebsd-swap (1.0G) > 2099200 5858433928 3 freebsd-zfs (2.7T) > 5860533128 7 - free - (3.5k) > ... maybe I found something: After setting vfs.zfs.debug=1 I got two new verbose bootlogs: http://people.freebsd.org/~mr/boot_fail2.txt http://people.freebsd.org/~mr/boot_success2.txt As you can see, in the failing case ZFS tries to attach to ada[0123] whereas in the succeeding case ZFS attaches to ada[0123]p3 (which are the correct devices) Bye/2 --- Michael Reifenberger Michael@Reifenberger.com http://www.Reifenberger.com From owner-freebsd-current@FreeBSD.ORG Tue May 31 19:29:03 2011 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 859841065672; Tue, 31 May 2011 19:29:03 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 9F4738FC15; Tue, 31 May 2011 19:29:02 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id WAA17354; Tue, 31 May 2011 22:28:55 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1QRUcY-000HVk-Sg; Tue, 31 May 2011 22:28:54 +0300 Message-ID: <4DE54176.3080702@FreeBSD.org> Date: Tue, 31 May 2011 22:28:54 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.17) Gecko/20110503 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: Michael Reifenberger References: In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Garrett Cooper , pjd@FreeBSD.org, FreeBSD-Current Subject: Re: mount root from zfs fails under current with "error 6" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2011 19:29:03 -0000 on 31/05/2011 20:38 Michael Reifenberger said the following: > Hi, > > On Tue, 31 May 2011, Michael Reifenberger wrote: > ... >> (fs)(root) gpart show ada0 >> => 34 5860533101 ada0 GPT (2.7T) >> 34 990 1 freebsd-boot (495k) >> 1024 2098176 2 freebsd-swap (1.0G) >> 2099200 5858433928 3 freebsd-zfs (2.7T) >> 5860533128 7 - free - (3.5k) >> > ... > > maybe I found something: > After setting vfs.zfs.debug=1 I got two new verbose bootlogs: > http://people.freebsd.org/~mr/boot_fail2.txt > http://people.freebsd.org/~mr/boot_success2.txt > > As you can see, in the failing case ZFS tries to attach to ada[0123] > whereas in the succeeding case ZFS attaches to ada[0123]p3 (which are the > correct devices) Maybe try to enable GEOM debug to see if/when tasting of the GPT partitions occurs. -- Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Tue May 31 20:24:23 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 166EC1065695 for ; Tue, 31 May 2011 20:24:22 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.59.238]) by mx1.freebsd.org (Postfix) with ESMTP id 8AF548FC0C for ; Tue, 31 May 2011 20:24:22 +0000 (UTC) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 81F587300B; Tue, 31 May 2011 22:21:42 +0200 (CEST) Date: Tue, 31 May 2011 22:21:42 +0200 From: Luigi Rizzo To: current@freebsd.org Message-ID: <20110531202142.GA7105@onelab2.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Cc: Subject: "lazy" mmap for a device driver ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2011 20:24:23 -0000 hi, i have a kernel module implementing a memory mapped special device which exports a large block of memory to the process. I see that when the process calls mmap(), my routine foo_mmap() is called immediately once per page, even though the process is not actually touching the pages. I believe this happens through dev_pager_alloc(). Right now i can live with that because all the memory is allocated at module load time, but i might want to have a sparse memory region which is populated dynamically, so i was wondering if there is a way to achieve this. I see there are two other device routines, d_mmap2 and d_mmap_single, any pointer to documentation or comments on how they differ ? thanks luigi From owner-freebsd-current@FreeBSD.ORG Tue May 31 20:45:25 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 95208106564A for ; Tue, 31 May 2011 20:45:25 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id EF3B48FC23 for ; Tue, 31 May 2011 20:45:24 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id p4VKjJSB095072 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 31 May 2011 23:45:19 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4) with ESMTP id p4VKjI03095022; Tue, 31 May 2011 23:45:18 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4/Submit) id p4VKjIVB095021; Tue, 31 May 2011 23:45:18 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 31 May 2011 23:45:18 +0300 From: Kostik Belousov To: Luigi Rizzo Message-ID: <20110531204518.GX48734@deviant.kiev.zoral.com.ua> References: <20110531202142.GA7105@onelab2.iet.unipi.it> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="OkGsJQGtcVL5ZVbY" Content-Disposition: inline In-Reply-To: <20110531202142.GA7105@onelab2.iet.unipi.it> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-3.3 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, DNS_FROM_OPENWHOIS autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: current@freebsd.org Subject: Re: "lazy" mmap for a device driver ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2011 20:45:25 -0000 --OkGsJQGtcVL5ZVbY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, May 31, 2011 at 10:21:42PM +0200, Luigi Rizzo wrote: > hi, > i have a kernel module implementing a memory mapped special device > which exports a large block of memory to the process. > I see that when the process calls mmap(), my routine foo_mmap() > is called immediately once per page, even though the process is > not actually touching the pages. I believe this happens > through dev_pager_alloc(). >=20 > Right now i can live with that because all the memory is allocated > at module load time, but i might want to have a sparse memory > region which is populated dynamically, so i was wondering if > there is a way to achieve this. I see there are two other > device routines, d_mmap2 and d_mmap_single, any pointer to > documentation or comments on how they differ ? During the porting of GEM to our kernel, I had to make a device pager interface more flexible. In particular, the updated pager allows the device to handle individual faults and return an explicit page to satisfy the fault, instead of the physical address. More, the driver can do any appropriate setup by ctr method. The new interface is supposed to be used with d_mmap_single(). http://people.freebsd.org/~kib/misc/device_pager.2.patch --OkGsJQGtcVL5ZVbY Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk3lU14ACgkQC3+MBN1Mb4hTmQCeIGrYXrb4zPG3zCucFqYg4l8/ 5KgAmwbc0cbg0vMlQqJ2r4yybRIcX5Su =tk7A -----END PGP SIGNATURE----- --OkGsJQGtcVL5ZVbY-- From owner-freebsd-current@FreeBSD.ORG Tue May 31 20:50:22 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 7C601106564A; Tue, 31 May 2011 20:50:22 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: Xin LI Date: Tue, 31 May 2011 16:50:14 -0400 User-Agent: KMail/1.6.2 References: In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201105311650.16164.jkim@FreeBSD.org> Cc: "George V. Neville-Neil" , freebsd-current@freebsd.org, Johannes Dieterich Subject: Re: Boot halts on Thinkpad X220 (Sandy Bridge) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2011 20:50:22 -0000 On Friday 27 May 2011 01:14 pm, Xin LI wrote: > On Thu, May 19, 2011 at 5:18 AM, Johannes Dieterich > > wrote: > > On Wed, May 18, 2011 at 7:40 PM, Xin LI wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- > >> Hash: SHA256 > >> > >> Try this patch? > > > > The attached patch makes 9-CURRENT-amd64 boot on the X220 w/o any > > hints or BIOS fixes needed. Thanks a lot! :-) > > > >> (I'm still opted to disable the typematic rate detection by > >> default at least for amd64, as we don't do it in the past for > >> amd64) > > > > What does this mean concerning getting the fix into CURRENT? > > Well, that's not a perfect fix and we do lose the ability of > detecting typematic rate (by default), so technically it's a > workaround (sufficient to make the kernel boot and work, though) > and doesn't fix anything. > > I have committed it anyway since we do not have better fix (yet), > and have updated atkbd(4) manual page so one can enable it again > when wanted. > > The problem we had was that it seems that running the BIOS in the > x86emu emulator on amd64 would cause problem. This doesn't seem to > be fixable without hands-on experiments on a system in question, > it's either a BIOS bug or an emulator bug. The strange part of the > problem is that the functionality is quite common in the Good Old > Days (TM). I got BIOS dump from gnn last week. I've been scratching my head cause it should just fail and exit gracefully unless I am totally missing something. :-( Are you guys sure that INT 15h is causing hangs? Maybe INT 16h is the real culprit (which is more probable, BTW)? Jung-uk Kim From owner-freebsd-current@FreeBSD.ORG Tue May 31 20:56:40 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 6460E106566B; Tue, 31 May 2011 20:56:33 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: Xin LI Date: Tue, 31 May 2011 16:56:25 -0400 User-Agent: KMail/1.6.2 References: <201105311650.16164.jkim@FreeBSD.org> In-Reply-To: <201105311650.16164.jkim@FreeBSD.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201105311656.27244.jkim@FreeBSD.org> Cc: "George V. Neville-Neil" , freebsd-current@freebsd.org, Johannes Dieterich Subject: Re: Boot halts on Thinkpad X220 (Sandy Bridge) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2011 20:56:40 -0000 On Tuesday 31 May 2011 04:50 pm, Jung-uk Kim wrote: > I got BIOS dump from gnn last week. I've been scratching my head > cause it should just fail and exit gracefully unless I am totally > missing something. :-( > > Are you guys sure that INT 15h is causing hangs? Maybe INT 16h is > the real culprit (which is more probable, BTW)? BTW, it shouldn't call INT 16h at all unless INT 15h succeeded somehow. So, I am totally lost. :-( Jung-uk Kim From owner-freebsd-current@FreeBSD.ORG Wed Jun 1 00:03:37 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 6EE78106564A; Wed, 1 Jun 2011 00:03:37 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: Xin LI Date: Tue, 31 May 2011 20:03:28 -0400 User-Agent: KMail/1.6.2 References: <201105311650.16164.jkim@FreeBSD.org> In-Reply-To: <201105311650.16164.jkim@FreeBSD.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201105312003.29931.jkim@FreeBSD.org> Cc: "George V. Neville-Neil" , freebsd-current@freebsd.org, Johannes Dieterich Subject: Re: Boot halts on Thinkpad X220 (Sandy Bridge) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2011 00:03:37 -0000 On Tuesday 31 May 2011 04:50 pm, Jung-uk Kim wrote: > On Friday 27 May 2011 01:14 pm, Xin LI wrote: > > On Thu, May 19, 2011 at 5:18 AM, Johannes Dieterich > > > > wrote: > > > On Wed, May 18, 2011 at 7:40 PM, Xin LI > > wrote: > > >> -----BEGIN PGP SIGNED MESSAGE----- > > >> Hash: SHA256 > > >> > > >> Try this patch? > > > > > > The attached patch makes 9-CURRENT-amd64 boot on the X220 w/o > > > any hints or BIOS fixes needed. Thanks a lot! :-) > > > > > >> (I'm still opted to disable the typematic rate detection by > > >> default at least for amd64, as we don't do it in the past for > > >> amd64) > > > > > > What does this mean concerning getting the fix into CURRENT? > > > > Well, that's not a perfect fix and we do lose the ability of > > detecting typematic rate (by default), so technically it's a > > workaround (sufficient to make the kernel boot and work, though) > > and doesn't fix anything. > > > > I have committed it anyway since we do not have better fix (yet), > > and have updated atkbd(4) manual page so one can enable it again > > when wanted. > > > > The problem we had was that it seems that running the BIOS in the > > x86emu emulator on amd64 would cause problem. This doesn't seem > > to be fixable without hands-on experiments on a system in > > question, it's either a BIOS bug or an emulator bug. The strange > > part of the problem is that the functionality is quite common in > > the Good Old Days (TM). > > I got BIOS dump from gnn last week. I've been scratching my head > cause it should just fail and exit gracefully unless I am totally > missing something. :-( > > Are you guys sure that INT 15h is causing hangs? Maybe INT 16h is > the real culprit (which is more probable, BTW)? I found something strange about this BIOS (well, if we can call it that). Please try this: Index: sys/dev/atkbdc/atkbd.c =================================================================== --- sys/dev/atkbdc/atkbd.c (revision 222550) +++ sys/dev/atkbdc/atkbd.c (working copy) @@ -1100,7 +1100,8 @@ get_typematic(keyboard_t *kbd) if (!(kbd->kb_config & KB_CONF_PROBE_TYPEMATIC)) return (ENODEV); - if (x86bios_get_intr(0x15) == 0 || x86bios_get_intr(0x16) == 0) + if (x86bios_get_intr(0x15) != 0xf000f859 || + x86bios_get_intr(0x16) != 0xf000e82e) return (ENODEV); /* Is BIOS system configuration table supported? */ You must re-enable typematic probing from loader to test it, of course. I think the following line should do: hint.atkbd.0.flags="0x10" Note: You may add printf() before and after the check to make sure it is being called (and it fails immediately). A long answer goes like this. INT 0x15 and 0x16 vectors have fixed entry points in *real* BIOS, i.e., 0xf000:0xf859 and 0xf000:0xe82e. For this BIOS (or CSM), INT 0x16 vector is correct but INT 0x15 vector is not (0xf000:0xb4f1). Funny thing is 0xf000:0xf859 actually points to a working INT 15h handler, it seems, which confused me totally. Probably it was done like this because (U)EFI CSM spec. mandated it to be located @ 0xf000:0xf859. If we follow the interrupt vector (0xf000:0xb4f1), it gets nowhere (or jumps to an unknown external interrupt handler). If we follow the fixed address, it will exit gracefully. So, actually there are two possible solutions, i.e., 1) check whether the interrupt vector is modified (the above patch), or 2) jump directly to the fixed interrupt entry point. I chose Option #1 because it is very hard to find BIOS typematic support these days (as you pointed out). Cheers, Jung-uk Kim From owner-freebsd-current@FreeBSD.ORG Wed Jun 1 14:35:44 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D568A1065670 for ; Wed, 1 Jun 2011 14:35:44 +0000 (UTC) (envelope-from thicks@averesystems.com) Received: from zimbra.averesystems.com (75-149-8-245-Pennsylvania.hfc.comcastbusiness.net [75.149.8.245]) by mx1.freebsd.org (Postfix) with ESMTP id 6AA4B8FC15 for ; Wed, 1 Jun 2011 14:35:44 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by zimbra.averesystems.com (Postfix) with ESMTP id A8412446003 for ; Wed, 1 Jun 2011 10:19:05 -0400 (EDT) X-Virus-Scanned: amavisd-new at averesystems.com Received: from zimbra.averesystems.com ([127.0.0.1]) by localhost (zimbra.averesystems.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uLtgkUpvYN+0; Wed, 1 Jun 2011 10:19:01 -0400 (EDT) Received: from zimbra.averesystems.com (zimbra.averesystems.com [10.0.0.42]) by zimbra.averesystems.com (Postfix) with ESMTP id 0691C8BC004; Wed, 1 Jun 2011 10:19:01 -0400 (EDT) References: <20110601120005.CEF1210656E6@hub.freebsd.org> From: Tom Hicks Content-Type: text/plain; charset=us-ascii In-Reply-To: <20110601120005.CEF1210656E6@hub.freebsd.org> Message-Id: <97920B9E-F6F3-47D0-8B37-E5D05D90D357@averesystems.com> Date: Wed, 1 Jun 2011 10:19:00 -0400 (EDT) To: "freebsd-current@freebsd.org" Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 X-Mailer: Zimbra 6.0.12_GA_2883 (MobileSync - Apple-iPhone3C1/810.2) Subject: Re: freebsd-current Digest, Vol 398, Issue 3 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2011 14:35:44 -0000 On Jun 1, 2011, at 8:03, freebsd-current-request@freebsd.org wrote: > Send freebsd-current mailing list submissions to > freebsd-current@freebsd.org >=20 > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.freebsd.org/mailman/listinfo/freebsd-current > or, via email, send a message with subject or body 'help' to > freebsd-current-request@freebsd.org >=20 > You can reach the person managing the list at > freebsd-current-owner@freebsd.org >=20 > When replying, please edit your Subject line so it is more specific > than "Re: Contents of freebsd-current digest..." >=20 >=20 > Today's Topics: >=20 > 1. Re: Testing new nfs and VIMAGE (Goran Lowkrantz) > 2. Re: [rfc] remove hlt_cpus et al sysctls and related code > (Attilio Rao) > 3. Re: [rfc] remove hlt_cpus et al sysctls and related code > (Andriy Gapon) > 4. Re: ZFS install from -CURRENT snapshot (Alexander Leidinger) > 5. Re: pcib allocation failure (John Baldwin) > 6. Re: message buffer scrambling fix (Kenneth D. Merry) > 7. Re: mount root from zfs fails under current with "error 6" > (Michael Reifenberger) > 8. Re: mount root from zfs fails under current with "error 6" > (Andriy Gapon) > 9. "lazy" mmap for a device driver ? (Luigi Rizzo) > 10. Re: "lazy" mmap for a device driver ? (Kostik Belousov) > 11. Re: Boot halts on Thinkpad X220 (Sandy Bridge) (Jung-uk Kim) > 12. Re: Boot halts on Thinkpad X220 (Sandy Bridge) (Jung-uk Kim) > 13. Re: Boot halts on Thinkpad X220 (Sandy Bridge) (Jung-uk Kim) >=20 >=20 > ---------------------------------------------------------------------- >=20 > Message: 1 > Date: Tue, 31 May 2011 14:34:22 +0200 > From: Goran Lowkrantz > Subject: Re: Testing new nfs and VIMAGE > To: freebsd-current@freebsd.org > Cc: Rick Macklem > Message-ID: <1DE98FADA8318788A5DD5505@[172.16.2.57]> > Content-Type: text/plain; charset=3D"us-ascii" >=20 > For the list: Attached patch works. >=20 > /glz >=20 > --On May 28, 2011 19:28:43 -0400 Rick Macklem wrot= e: >=20 >>> It worked when I added CURVNET_SET/CURVNET_RESTORE around the >>> RTFREE_LOCKED >>> macro too. Attached a complete patch. >>>=20 >>> Thank you. >>>=20 >> and thanks for finding/reporting/testing it. I've attached another >> variant of the patch that maybe you could try? >> (I don't think it's necessary to do twice, so I just moved the >> CURVNET_RESTORE() to after the RTFREE_LOCKED() macro instead.) >>=20 >> I don't know if you are a committer for this stuff or not? >> If you are feel free to commit whichever variant of the patch you >> find works and prefer. >>=20 >> If not, maybe bz@ could either commit it or review it? >> (or whoever is doing the VIMAGE stuff these days?) >>=20 >> rick >=20 > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: curvnet.patch > Type: text/x-patch > Size: 1144 bytes > Desc: not available > Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/2011= 0531/2c83e02d/curvnet-0001.bin >=20 > ------------------------------ >=20 > Message: 2 > Date: Tue, 31 May 2011 09:34:44 -0400 > From: Attilio Rao > Subject: Re: [rfc] remove hlt_cpus et al sysctls and related code > To: Andriy Gapon > Cc: "freebsd-current@freebsd.org" , > "freebsd-arch@freebsd.org" > Message-ID: > Content-Type: text/plain; charset=3DUTF-8 >=20 > 2011/5/31 Andriy Gapon : >> on 29/05/2011 06:06 Attilio Rao said the following: >>> 2011/5/28 Attilio Rao : >>>> 2011/5/25 Andriy Gapon : >>>>> The patch is here: >>>>> http://people.freebsd.org/~avg/cpu-offline-sysctl.diff >>>>> It should implement the strategy described above. >>>>>=20 >>>>=20 >>>> I don't see the point in keeping alive mp_grab_cpu_hlt() and >>>> supporting, actually. >>>>=20 >>>> On the top of your patch I made some modifies that use directly >>>> ap_watchdog() in cpu_idle() which I think is better for the time >>>> being: >>>> http://www.freebsd.org/~attilio/avg_rem_cpuhlt.diff >>=20 >> Yes, I agree, thank you. >>=20 >>>> If you are happy with it, just commit as long as Garrett tests that. >>=20 >>=20 >> OK. Waiting for test feedback. >>=20 >>>> On a second round of changes we can discuss mp_watchdog and eventual >>>> removal / improvements to it. >>>=20 >>> I almost forgot: this change would also require an UPDATE entry, where >>> you explicitly mention the "new" way to deal with CPUs. Use your >>> prefer wording. >>=20 >> Sure. Thank you! >>=20 >> BTW, I guess there would be no reason to MFC this change? >=20 > You mean no reason to not MFC it? >=20 > In general, I think that users may expect those sysctls to be alive > (IMHO we should consider sysctls to be part of the userland API) so > that we can add some more, but we should not axe them. > So probabilly MFC is not the best option here. >=20 > Attilio >=20 >=20 > --=20 > Peace can only be achieved by understanding - A. Einstein >=20 >=20 > ------------------------------ >=20 > Message: 3 > Date: Tue, 31 May 2011 16:40:45 +0300 > From: Andriy Gapon > Subject: Re: [rfc] remove hlt_cpus et al sysctls and related code > To: Attilio Rao > Cc: "freebsd-current@freebsd.org" , > "freebsd-arch@freebsd.org" > Message-ID: <4DE4EFDD.8070803@FreeBSD.org> > Content-Type: text/plain; charset=3Dus-ascii >=20 > on 31/05/2011 16:34 Attilio Rao said the following: >> 2011/5/31 Andriy Gapon : >>> on 29/05/2011 06:06 Attilio Rao said the following: >>>> 2011/5/28 Attilio Rao : >>>>> 2011/5/25 Andriy Gapon : >>>>>> The patch is here: >>>>>> http://people.freebsd.org/~avg/cpu-offline-sysctl.diff >>>>>> It should implement the strategy described above. >>>>>>=20 >>>>>=20 >>>>> I don't see the point in keeping alive mp_grab_cpu_hlt() and >>>>> supporting, actually. >>>>>=20 >>>>> On the top of your patch I made some modifies that use directly >>>>> ap_watchdog() in cpu_idle() which I think is better for the time >>>>> being: >>>>> http://www.freebsd.org/~attilio/avg_rem_cpuhlt.diff >>>=20 >>> Yes, I agree, thank you. >>>=20 >>>>> If you are happy with it, just commit as long as Garrett tests that. >>>=20 >>>=20 >>> OK. Waiting for test feedback. >>>=20 >>>>> On a second round of changes we can discuss mp_watchdog and eventual >>>>> removal / improvements to it. >>>>=20 >>>> I almost forgot: this change would also require an UPDATE entry, where >>>> you explicitly mention the "new" way to deal with CPUs. Use your >>>> prefer wording. >>>=20 >>> Sure. Thank you! >>>=20 >>> BTW, I guess there would be no reason to MFC this change? >>=20 >> You mean no reason to not MFC it? >=20 > I meant exactly what I asked :-) > As in: I didn't see any reason for MFC. >=20 >> In general, I think that users may expect those sysctls to be alive >> (IMHO we should consider sysctls to be part of the userland API) so >> that we can add some more, but we should not axe them. >> So probabilly MFC is not the best option here. >=20 > --=20 > Andriy Gapon >=20 >=20 > ------------------------------ >=20 > Message: 4 > Date: Tue, 31 May 2011 16:04:49 +0200 > From: Alexander Leidinger > Subject: Re: ZFS install from -CURRENT snapshot > To: Daniel Staal > Cc: freebsd-current@freebsd.org, George Kontostanos > > Message-ID: <20110531160449.19667dub2cfejdkx@webmail.leidinger.net> > Content-Type: text/plain; charset=3DUTF-8; DelSp=3D"Yes"; format=3D"flowe= d" >=20 > Quoting Daniel Staal (from Mon, 30 May 2011 11:01:06 -04= 00): >=20 >> --As of May 29, 2011 9:10:57 AM -0400, George Kontostanos, =20 >> freebsd-current@freebsd.org is alleged to have said: >>=20 >>> --As of May 29, 2011 12:06:30 PM +0300, George Kontostanos is alleged t= o >>> have said: >>>=20 >>>> The new bsdinstall has a different layout so the previous guides don't >>>> work. I have prepared one that works for recent 9-Current at : >>>>=20 >>>> "http://www.aisecure.net/?p=3D132" >>>=20 >>> --As for the rest, it is mine. >>>=20 >>> Thanks, that's about what I expected the install procedure to be at thi= s >>> point. Nice to have the reminder about the zpool.cache. (Do I have t= o >>> use the Live CD mode? Can I use shell mode instead?) >>=20 >> --As for the rest, it is mine. >>=20 >> Ok, I've tried shell mode and live CD mode. I've re-partitioned my =20 >> disks several different ways. >>=20 >> Nothing gets me a system that will actually boot. Or even recognize =20 >> that there is an OS loaded anywhere. Help? >=20 > I did it like this: > http://www.leidinger.net/blog/2011/05/03/another-root-on-zfs-howto-optimi= zed-for-4k-sector-drives/ >=20 >> (My preferred partitioning: >>=20 >> ada1: >> 1 freebsd-boot >> 2 freebsd-swap 8G >> 3 freebsd-zfs 4G (zil) >> 4 freebsd-zfs 17G (cache) >>=20 >> ada0: Managed by ZFS, ~250G Main filesystem. >=20 > You show the boot partition on ada1, but you do not tell if ada0 has a = =20 > boot partition too or not. Did you try to have the boot partition on =20 > the same disk as the pool? >=20 > I hope ada1 is a SSD. If not, it does not make much sense to have a =20 > cache there (a cache needs to have lower latency than the main pool, I = =20 > do not expect that just another spindle gives a significant perf =20 > improvement). >=20 > Bye, > Alexander. >=20 > --=20 > Please don't put a strain on our friendship > by asking me to do something for you. >=20 > http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID =3D B0063FE= 7 > http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID =3D 7207713= 7 >=20 >=20 > ------------------------------ >=20 > Message: 5 > Date: Tue, 31 May 2011 10:39:37 -0400 > From: John Baldwin > Subject: Re: pcib allocation failure > To: freebsd-current@freebsd.org > Cc: "deeptech71@gmail.com" > Message-ID: <201105311039.37935.jhb@freebsd.org> > Content-Type: Text/Plain; charset=3D"iso-8859-1" >=20 > On Saturday, May 28, 2011 9:45:48 pm deeptech71@gmail.com wrote: >> On Thu, May 26, 2011 at 3:40 PM, John Baldwin wrote: >>> Ohh, you have two devices behind this bridge that have prefetch ranges. >>>=20 >>> As a hack, can you try this: >>>=20 >>> Index: pci_pci.c >>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>> --- pci_pci.c (revision 222285) >>> +++ pci_pci.c (working copy) >>> @@ -162,8 +162,13 @@ pcib_write_windows(struct pcib_softc *sc, int mask >>> { >>> device_t dev; >>> uint32_t val; >>> + uint16_t cmd; >>>=20 >>> dev =3D sc->dev; >>> + cmd =3D pci_read_config(dev, PCIR_COMMAND, 2); >>> + if (cmd & (PCIM_CMD_PORTEN | PCIM_CMD_MEMEN)) >>> + pci_write_config(dev, PCIR_COMMAND, >>> + cmd & ~(PCIM_CMD_PORTEN | PCIM_CMD_MEMEN), 2); >>> if (sc->io.valid && mask & WIN_IO) { >>> val =3D pci_read_config(dev, PCIR_IOBASEL_1, 1); >>> if ((val & PCIM_BRIO_MASK) =3D=3D PCIM_BRIO_32) { >>> @@ -192,6 +197,8 @@ pcib_write_windows(struct pcib_softc *sc, int mask >>> pci_write_config(dev, PCIR_PMBASEL_1, sc->pmem.base >> 16= ,=20 > 2); >>> pci_write_config(dev, PCIR_PMLIMITL_1, sc->pmem.limit >>= =20 > 16, 2); >>> } >>> + if (cmd & (PCIM_CMD_PORTEN | PCIM_CMD_MEMEN)) >>> + pci_write_config(dev, PCIR_COMMAND, cmd, 2); >>> } >>>=20 >>> static void >>> @@ -337,6 +344,9 @@ pcib_probe_windows(struct pcib_softc *sc) >>> pci_read_config(dev, PCIR_PMLIMITL_1, 2)); >>> max =3D 0xffffffff; >>> } >>> + /* XXX: Testing hack */ >>> + if (device_get_unit(sc->sc_dev) =3D=3D 1) >>=20 >> i'm assuming that "sc->sc_dev" should be "dev" (this fixes a compilation= =20 > error). >>=20 >>> + sc->pmem.limit =3D 0xefffffff; >>> pcib_alloc_window(sc, &sc->pmem, SYS_RES_MEMORY, >>> RF_PREFETCHABLE, max); >>> } >>=20 >> that seems to work! >=20 > Hmmm, ok. This may not be easy to fix properly for the time being as it= =20 > requires the PCI-PCI bridge to scan all the devices behind the bus to fin= d=20 > what resource ranges are actually needed before programming its windows. = Note=20 > that this is all to work around your BIOS being very broken. :( >=20 >> btw, is my machine a test-pig for an upcoming change to the PCI bus driv= er? >=20 > Well, it's been a good test thus far. >=20 > --=20 > John Baldwin >=20 >=20 > ------------------------------ >=20 > Message: 6 > Date: Tue, 31 May 2011 09:42:15 -0600 > From: "Kenneth D. Merry" > Subject: Re: message buffer scrambling fix > To: Julian Elischer > Cc: current@freebsd.org > Message-ID: <20110531154215.GA45877@nargothrond.kdm.org> > Content-Type: text/plain; charset=3Dus-ascii >=20 > On Sat, May 28, 2011 at 11:26:50 -0700, Julian Elischer wrote: >> On 5/27/11 3:45 PM, Kenneth D. Merry wrote: >>> Hey folks, >>>=20 >>> I have attached some patches to the kernel message buffer code (this >>> affects dmesg(8) output as well as kernel messages that go to the syslo= g) >>> to address log scrambling. >>>=20 >>> This fixes the same issue that 'options PRINTF_BUFR_SIZE=3D128' fixes f= or the >>> console. >>>=20 >>> The problem is that you can have multiple kernel threads writing to the >>> message buffer at the same time, and so their characters will get >>> interleaved. All of the characters will get in there, because they're >>> written with atomic operations, but the output might looked scrambled. >>>=20 >>> So the fix is to use the same stack buffer that is used for the console >>> output (so the stack size doesn't increase), and use a spin lock instea= d of >>> atomic operations to insert the string into the message buffer. >>>=20 >>> The result is that dmesg and syslog output should look the same as the >>> console output. As long as individual kernel prints fit in the printf >>> buffer size, they will be put into the message buffer atomically. >>>=20 >>> I also fixed a couple of other long-standing issues. putcons() (in >>> subr_prf.c) was adding a carriage return before calling cnputs(). But >>> cnputs() calls cnputc(), which adds a carriage return before every newl= ine. >>> So much of the console output (the part that came from putcons() at lea= st) >>> had two carriage returns at the end. >>>=20 >>> The other issue was that log_console() was inserting a newline for any >>> console write that didn't already have one at the end. The issue with = that >>> can be seen if you do a 'dmesg -a' and compare that to the console outp= ut. >>>=20 >>> You'll see something like this on the console: >>>=20 >>> Updating motd:. >>>=20 >>> But this in dmesg -a: >>>=20 >>> Updating motd: >>> . >>>=20 >>> That is because "Updating motd:" is written first, log_console() append= s a >>> newline, and then ".\n" is written. >>>=20 >>> I added a loader tunable and sysctl to turn the old behavior back on >>> (kern.log_console_add_linefeed) if you want the old behavior, but I thi= nk >>> we should be able to safely remove it. >>>=20 >>> Also, the new msgbuf_addstr() function allows the caller to optionally = ask >>> for carriage returns to be stripped out. However, in my testing I have= n't >>> seen any carriage returns to strip. >>>=20 >>> Let me know if you have any comments. I'm planning to check this into = head >>> next week. >>=20 >> looks good.. as long as we don't end up with the behaviour that I=20 >> think I see on >> Linux (it's hard to tell sometimes) where the last message (the one=20 >> you really >> want to see) doesn't make it out. >=20 > Everything passed into the kernel printf() call should make it out to the > console, message buffer, etc. before the printf call completes. The only > way that wouldn't happen is if spin locks break for some reason. >=20 > One thing I forgot to mention is that I think the PRINTF_BUFR_SIZE option > should be made non-optional. Even on smaller embedded machines, I think = we > should be able to afford the 128 bytes of stack space to keep messages fr= om > getting scrambled. >=20 > Ken > --=20 > Kenneth Merry > ken@FreeBSD.ORG >=20 >=20 > ------------------------------ >=20 > Message: 7 > Date: Tue, 31 May 2011 19:38:50 +0200 (CEST) > From: Michael Reifenberger > Subject: Re: mount root from zfs fails under current with "error 6" > To: pjd@freebsd.org > Cc: Garrett Cooper , FreeBSD-Current > > Message-ID: > Content-Type: TEXT/PLAIN; charset=3DUS-ASCII; format=3Dflowed >=20 > Hi, >=20 > On Tue, 31 May 2011, Michael Reifenberger wrote: > ... >> (fs)(root) gpart show ada0 >> =3D> 34 5860533101 ada0 GPT (2.7T) >> 34 990 1 freebsd-boot (495k) >> 1024 2098176 2 freebsd-swap (1.0G) >> 2099200 5858433928 3 freebsd-zfs (2.7T) >> 5860533128 7 - free - (3.5k) >>=20 > ... >=20 > maybe I found something: > After setting vfs.zfs.debug=3D1 I got two new verbose bootlogs: > http://people.freebsd.org/~mr/boot_fail2.txt > http://people.freebsd.org/~mr/boot_success2.txt >=20 > As you can see, in the failing case ZFS tries to attach to ada[0123] > whereas in the succeeding case ZFS attaches to ada[0123]p3 (which are the= =20 > correct devices) >=20 > Bye/2 > --- > Michael Reifenberger > Michael@Reifenberger.com > http://www.Reifenberger.com >=20 >=20 >=20 > ------------------------------ >=20 > Message: 8 > Date: Tue, 31 May 2011 22:28:54 +0300 > From: Andriy Gapon > Subject: Re: mount root from zfs fails under current with "error 6" > To: Michael Reifenberger > Cc: Garrett Cooper , pjd@FreeBSD.org, > FreeBSD-Current > Message-ID: <4DE54176.3080702@FreeBSD.org> > Content-Type: text/plain; charset=3DISO-8859-1 >=20 > on 31/05/2011 20:38 Michael Reifenberger said the following: >> Hi, >>=20 >> On Tue, 31 May 2011, Michael Reifenberger wrote: >> ... >>> (fs)(root) gpart show ada0 >>> =3D> 34 5860533101 ada0 GPT (2.7T) >>> 34 990 1 freebsd-boot (495k) >>> 1024 2098176 2 freebsd-swap (1.0G) >>> 2099200 5858433928 3 freebsd-zfs (2.7T) >>> 5860533128 7 - free - (3.5k) >>>=20 >> ... >>=20 >> maybe I found something: >> After setting vfs.zfs.debug=3D1 I got two new verbose bootlogs: >> http://people.freebsd.org/~mr/boot_fail2.txt >> http://people.freebsd.org/~mr/boot_success2.txt >>=20 >> As you can see, in the failing case ZFS tries to attach to ada[0123] >> whereas in the succeeding case ZFS attaches to ada[0123]p3 (which are th= e >> correct devices) >=20 > Maybe try to enable GEOM debug to see if/when tasting of the GPT partitio= ns occurs. > --=20 > Andriy Gapon >=20 >=20 > ------------------------------ >=20 > Message: 9 > Date: Tue, 31 May 2011 22:21:42 +0200 > From: Luigi Rizzo > Subject: "lazy" mmap for a device driver ? > To: current@freebsd.org > Message-ID: <20110531202142.GA7105@onelab2.iet.unipi.it> > Content-Type: text/plain; charset=3Dus-ascii >=20 > hi, > i have a kernel module implementing a memory mapped special device > which exports a large block of memory to the process. > I see that when the process calls mmap(), my routine foo_mmap() > is called immediately once per page, even though the process is > not actually touching the pages. I believe this happens > through dev_pager_alloc(). >=20 > Right now i can live with that because all the memory is allocated > at module load time, but i might want to have a sparse memory > region which is populated dynamically, so i was wondering if > there is a way to achieve this. I see there are two other > device routines, d_mmap2 and d_mmap_single, any pointer to > documentation or comments on how they differ ? >=20 > thanks > luigi >=20 >=20 > ------------------------------ >=20 > Message: 10 > Date: Tue, 31 May 2011 23:45:18 +0300 > From: Kostik Belousov > Subject: Re: "lazy" mmap for a device driver ? > To: Luigi Rizzo > Cc: current@freebsd.org > Message-ID: <20110531204518.GX48734@deviant.kiev.zoral.com.ua> > Content-Type: text/plain; charset=3D"us-ascii" >=20 > On Tue, May 31, 2011 at 10:21:42PM +0200, Luigi Rizzo wrote: >> hi, >> i have a kernel module implementing a memory mapped special device >> which exports a large block of memory to the process. >> I see that when the process calls mmap(), my routine foo_mmap() >> is called immediately once per page, even though the process is >> not actually touching the pages. I believe this happens >> through dev_pager_alloc(). >>=20 >> Right now i can live with that because all the memory is allocated >> at module load time, but i might want to have a sparse memory >> region which is populated dynamically, so i was wondering if >> there is a way to achieve this. I see there are two other >> device routines, d_mmap2 and d_mmap_single, any pointer to >> documentation or comments on how they differ ? >=20 > During the porting of GEM to our kernel, I had to make a device > pager interface more flexible. In particular, the updated pager allows > the device to handle individual faults and return an explicit > page to satisfy the fault, instead of the physical address. >=20 > More, the driver can do any appropriate setup by ctr method. > The new interface is supposed to be used with d_mmap_single(). >=20 > http://people.freebsd.org/~kib/misc/device_pager.2.patch > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: not available > Type: application/pgp-signature > Size: 196 bytes > Desc: not available > Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/2011= 0531/6e617d43/attachment-0001.pgp >=20 > ------------------------------ >=20 > Message: 11 > Date: Tue, 31 May 2011 16:50:14 -0400 > From: Jung-uk Kim > Subject: Re: Boot halts on Thinkpad X220 (Sandy Bridge) > To: Xin LI > Cc: "George V. Neville-Neil" , > freebsd-current@freebsd.org, Johannes Dieterich > > Message-ID: <201105311650.16164.jkim@FreeBSD.org> > Content-Type: text/plain; charset=3D"iso-8859-1" >=20 > On Friday 27 May 2011 01:14 pm, Xin LI wrote: >> On Thu, May 19, 2011 at 5:18 AM, Johannes Dieterich >>=20 >> wrote: >>> On Wed, May 18, 2011 at 7:40 PM, Xin LI =20 > wrote: >>>> -----BEGIN PGP SIGNED MESSAGE----- >>>> Hash: SHA256 >>>>=20 >>>> Try this patch? >>>=20 >>> The attached patch makes 9-CURRENT-amd64 boot on the X220 w/o any >>> hints or BIOS fixes needed. Thanks a lot! :-) >>>=20 >>>> (I'm still opted to disable the typematic rate detection by >>>> default at least for amd64, as we don't do it in the past for >>>> amd64) >>>=20 >>> What does this mean concerning getting the fix into CURRENT? >>=20 >> Well, that's not a perfect fix and we do lose the ability of >> detecting typematic rate (by default), so technically it's a >> workaround (sufficient to make the kernel boot and work, though) >> and doesn't fix anything. >>=20 >> I have committed it anyway since we do not have better fix (yet), >> and have updated atkbd(4) manual page so one can enable it again >> when wanted. >>=20 >> The problem we had was that it seems that running the BIOS in the >> x86emu emulator on amd64 would cause problem. This doesn't seem to >> be fixable without hands-on experiments on a system in question, >> it's either a BIOS bug or an emulator bug. The strange part of the >> problem is that the functionality is quite common in the Good Old >> Days (TM). >=20 > I got BIOS dump from gnn last week. I've been scratching my head=20 > cause it should just fail and exit gracefully unless I am totally=20 > missing something. :-( >=20 > Are you guys sure that INT 15h is causing hangs? Maybe INT 16h is the=20 > real culprit (which is more probable, BTW)? >=20 > Jung-uk Kim >=20 >=20 > ------------------------------ >=20 > Message: 12 > Date: Tue, 31 May 2011 16:56:25 -0400 > From: Jung-uk Kim > Subject: Re: Boot halts on Thinkpad X220 (Sandy Bridge) > To: Xin LI > Cc: "George V. Neville-Neil" , > freebsd-current@freebsd.org, Johannes Dieterich > > Message-ID: <201105311656.27244.jkim@FreeBSD.org> > Content-Type: text/plain; charset=3D"iso-8859-1" >=20 > On Tuesday 31 May 2011 04:50 pm, Jung-uk Kim wrote: >> I got BIOS dump from gnn last week. I've been scratching my head >> cause it should just fail and exit gracefully unless I am totally >> missing something. :-( >>=20 >> Are you guys sure that INT 15h is causing hangs? Maybe INT 16h is >> the real culprit (which is more probable, BTW)? >=20 > BTW, it shouldn't call INT 16h at all unless INT 15h succeeded=20 > somehow. So, I am totally lost. :-( >=20 > Jung-uk Kim >=20 >=20 > ------------------------------ >=20 > Message: 13 > Date: Tue, 31 May 2011 20:03:28 -0400 > From: Jung-uk Kim > Subject: Re: Boot halts on Thinkpad X220 (Sandy Bridge) > To: Xin LI > Cc: "George V. Neville-Neil" , > freebsd-current@freebsd.org, Johannes Dieterich > > Message-ID: <201105312003.29931.jkim@FreeBSD.org> > Content-Type: text/plain; charset=3D"iso-8859-1" >=20 > On Tuesday 31 May 2011 04:50 pm, Jung-uk Kim wrote: >> On Friday 27 May 2011 01:14 pm, Xin LI wrote: >>> On Thu, May 19, 2011 at 5:18 AM, Johannes Dieterich >>>=20 >>> wrote: >>>> On Wed, May 18, 2011 at 7:40 PM, Xin LI >>=20 >> wrote: >>>>> -----BEGIN PGP SIGNED MESSAGE----- >>>>> Hash: SHA256 >>>>>=20 >>>>> Try this patch? >>>>=20 >>>> The attached patch makes 9-CURRENT-amd64 boot on the X220 w/o >>>> any hints or BIOS fixes needed. Thanks a lot! :-) >>>>=20 >>>>> (I'm still opted to disable the typematic rate detection by >>>>> default at least for amd64, as we don't do it in the past for >>>>> amd64) >>>>=20 >>>> What does this mean concerning getting the fix into CURRENT? >>>=20 >>> Well, that's not a perfect fix and we do lose the ability of >>> detecting typematic rate (by default), so technically it's a >>> workaround (sufficient to make the kernel boot and work, though) >>> and doesn't fix anything. >>>=20 >>> I have committed it anyway since we do not have better fix (yet), >>> and have updated atkbd(4) manual page so one can enable it again >>> when wanted. >>>=20 >>> The problem we had was that it seems that running the BIOS in the >>> x86emu emulator on amd64 would cause problem. This doesn't seem >>> to be fixable without hands-on experiments on a system in >>> question, it's either a BIOS bug or an emulator bug. The strange >>> part of the problem is that the functionality is quite common in >>> the Good Old Days (TM). >>=20 >> I got BIOS dump from gnn last week. I've been scratching my head >> cause it should just fail and exit gracefully unless I am totally >> missing something. :-( >>=20 >> Are you guys sure that INT 15h is causing hangs? Maybe INT 16h is >> the real culprit (which is more probable, BTW)? >=20 > I found something strange about this BIOS (well, if we can call it=20 > that). Please try this: >=20 > Index: sys/dev/atkbdc/atkbd.c > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- sys/dev/atkbdc/atkbd.c (revision 222550) > +++ sys/dev/atkbdc/atkbd.c (working copy) > @@ -1100,7 +1100,8 @@ get_typematic(keyboard_t *kbd) > if (!(kbd->kb_config & KB_CONF_PROBE_TYPEMATIC)) > return (ENODEV); >=20 > - if (x86bios_get_intr(0x15) =3D=3D 0 || x86bios_get_intr(0x16) =3D=3D= 0) > + if (x86bios_get_intr(0x15) !=3D 0xf000f859 || > + x86bios_get_intr(0x16) !=3D 0xf000e82e) > return (ENODEV); >=20 > /* Is BIOS system configuration table supported? */ >=20 > You must re-enable typematic probing from loader to test it, of=20 > course. I think the following line should do: >=20 > hint.atkbd.0.flags=3D"0x10" >=20 > Note: You may add printf() before and after the check to make sure it=20 > is being called (and it fails immediately). >=20 > A long answer goes like this. INT 0x15 and 0x16 vectors have fixed=20 > entry points in *real* BIOS, i.e., 0xf000:0xf859 and 0xf000:0xe82e. =20 > For this BIOS (or CSM), INT 0x16 vector is correct but INT 0x15=20 > vector is not (0xf000:0xb4f1). Funny thing is 0xf000:0xf859 actually=20 > points to a working INT 15h handler, it seems, which confused me=20 > totally. Probably it was done like this because (U)EFI CSM spec.=20 > mandated it to be located @ 0xf000:0xf859. If we follow the=20 > interrupt vector (0xf000:0xb4f1), it gets nowhere (or jumps to an=20 > unknown external interrupt handler). If we follow the fixed address,=20 > it will exit gracefully. So, actually there are two possible=20 > solutions, i.e., 1) check whether the interrupt vector is modified=20 > (the above patch), or 2) jump directly to the fixed interrupt entry=20 > point. I chose Option #1 because it is very hard to find BIOS=20 > typematic support these days (as you pointed out). >=20 > Cheers, >=20 > Jung-uk Kim >=20 >=20 > ------------------------------ >=20 > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " >=20 > End of freebsd-current Digest, Vol 398, Issue 3 > *********************************************** From owner-freebsd-current@FreeBSD.ORG Wed Jun 1 15:09:33 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 07DFD106564A for ; Wed, 1 Jun 2011 15:09:33 +0000 (UTC) (envelope-from uwe@grohnwaldt.eu) Received: from web01.lando.us (web01.lando.us [77.232.247.17]) by mx1.freebsd.org (Postfix) with ESMTP id C64DE8FC17 for ; Wed, 1 Jun 2011 15:09:32 +0000 (UTC) Received: from C3PO (bridge.aixit.com [82.149.224.60]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: uwe@grohnwaldt.eu) by web01.lando.us (Postfix) with ESMTPSA id CC5F87C933 for ; Wed, 1 Jun 2011 16:50:57 +0200 (CEST) From: "Uwe Grohnwaldt" To: Date: Wed, 1 Jun 2011 16:50:58 +0200 Message-ID: <006101cc206b$512599f0$f370cdd0$@grohnwaldt.eu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Thread-Index: Acwga1EGZFqqAri2TxqRKVktfFUVUQ== Content-Language: de Cc: Subject: AW: -CURRENT: mountroot failed X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2011 15:09:33 -0000 Hi, i have the same problem and setting kern.geom.part.check_integrity=3D0 = works. I installed my system using sysinstall from 8.2-amd64-CD1. Ciao, Uwe -- Uwe Grohnwaldt -----Urspr=FCngliche Nachricht----- Von: owner-freebsd-current@freebsd.org [mailto:owner-freebsd-current@freebsd.org] Im Auftrag von Andrey V. = Elsukov Gesendet: Montag, 16. Mai 2011 17:00 An: Michiel Boland Cc: FreeBSD Current Betreff: Re: -CURRENT: mountroot failed On 16.05.2011 16:13, Michiel Boland wrote: >> Can you send me a binary image of the first sector of ada0? >> Also, output of `gpart list ada0` would be helpful. > charlemagne# gpart list ada0 > Geom name: ada0 > modified: false > state: OK > fwheads: 16 > fwsectors: 63 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D> last: 1953525167 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D> first: 63 > entries: 4 > scheme: MBR > Providers: > 1. Name: ada0s1 > Mediasize: 1000204648448 (931G) > Sectorsize: 512 > Mode: r5w5e9 > attrib: active > rawtype: 165 > length: 1000204648448 > offset: 16384 > type: freebsd > index: 1 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D> end: 1953524735 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D> start: 32 Your partition has start offset below the first LBA. As temporary workaround you can set loader tunable kern.geom.part.check_integrity=3D0 (recently added to CURRENT) > (Note that I partitioned the disk so that partition 1 starts at a=20 > multiple of 4096 bytes; this is one of those 4kb-sector disks that=20 > performs extremely badly if access is not aligned on a 4k boundary.) What tool did you use for partitioning? -- WBR, Andrey V. Elsukov From owner-freebsd-current@FreeBSD.ORG Wed Jun 1 15:55:02 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E6F02106566B for ; Wed, 1 Jun 2011 15:55:02 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward13.mail.yandex.net (forward13.mail.yandex.net [95.108.130.120]) by mx1.freebsd.org (Postfix) with ESMTP id 5C13E8FC13 for ; Wed, 1 Jun 2011 15:55:01 +0000 (UTC) Received: from smtp11.mail.yandex.net (smtp11.mail.yandex.net [95.108.130.67]) by forward13.mail.yandex.net (Yandex) with ESMTP id 3CB5B142779; Wed, 1 Jun 2011 19:55:00 +0400 (MSD) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1306943700; bh=Unql841gDTYNczHSr/lpsIYcym1iZo4V1aqK8ErrV0E=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type; b=bL5oTIi2fblaTStbIHZCnXZZ89++z8kT9wm82ZillOrUF1dEN4dWDA5vFwwAwnopY lYYA4oFPZBKt5tCWzgrR+fOTBrbR9UxJdwLZOob6KXQRllTo71OtBVJeUOeu5vGdc+ oA3fttRql2y2hWTGSggDB3KBXrF9sgmek4xFrTMI= Received: from [178.141.6.33] (dynamic-178-141-6-33.kirov.comstar-r.ru [178.141.6.33]) by smtp11.mail.yandex.net (Yandex) with ESMTPSA id E94EA4CC005D; Wed, 1 Jun 2011 19:54:59 +0400 (MSD) Message-ID: <4DE660CB.4000508@yandex.ru> Date: Wed, 01 Jun 2011 19:54:51 +0400 From: "Andrey V. Elsukov" User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.17) Gecko/20110429 Thunderbird/3.1.10 MIME-Version: 1.0 To: Uwe Grohnwaldt References: <006101cc206b$512599f0$f370cdd0$@grohnwaldt.eu> In-Reply-To: <006101cc206b$512599f0$f370cdd0$@grohnwaldt.eu> X-Enigmail-Version: 1.1.2 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig4571358791D311527D9C1EC5" X-Yandex-Spam: 1 Cc: current@freebsd.org Subject: Re: AW: -CURRENT: mountroot failed X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2011 15:55:03 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig4571358791D311527D9C1EC5 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable On 01.06.2011 18:50, Uwe Grohnwaldt wrote: > i have the same problem and setting kern.geom.part.check_integrity=3D0 = works. I > installed my system using sysinstall from 8.2-amd64-CD1. Hi, i added a workaround for this issue in r222341. Which revision do you use? --=20 WBR, Andrey V. Elsukov --------------enig4571358791D311527D9C1EC5 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (FreeBSD) iQEcBAEBAgAGBQJN5mDLAAoJEAHF6gQQyKF68n4H/2IlVbKktdV2sddbWqNIQsMT wWYqW1q2GZ/kyTvRe0TENn3JsHE5BPjzP/6EGT9iGKDZCu6gsqeO/ZM3kd5pvfC0 zvolI4t2gbUNuZPGX21j0+DVRibD0DfrryLyRqKOrmStDjAoRG06Q3YqFwcfq3Dw gdiJbywyqqqFX2SeHSu0ulvBDE/zPQ66htldaOOWfNV9lPWE7+TfHutiBpqs+ntw 61CUuitIYPsVPBcagrn51A/Xc+RQ1In9yQLH9UnAC42k2d4Jvao4RjjFMf953f1X ik5wsOsbTdUlRUzpAJZ1U1UQSUCH5+Kw9vCZk5YKSjLCNrxlf1CjNBM7e0YbRUA= =+e5Y -----END PGP SIGNATURE----- --------------enig4571358791D311527D9C1EC5-- From owner-freebsd-current@FreeBSD.ORG Wed Jun 1 16:38:32 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A3B2A106566B for ; Wed, 1 Jun 2011 16:38:32 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.59.238]) by mx1.freebsd.org (Postfix) with ESMTP id 700508FC13 for ; Wed, 1 Jun 2011 16:38:31 +0000 (UTC) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id BB0C57300A; Wed, 1 Jun 2011 18:54:29 +0200 (CEST) Date: Wed, 1 Jun 2011 18:54:29 +0200 From: Luigi Rizzo To: current@freebsd.org Message-ID: <20110601165429.GA16569@onelab2.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Cc: Subject: warning: 'inline' is not at beginning of declaration ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2011 16:38:32 -0000 In an attempt to build a kernel with -Wextra gives a number of warnings for 'inline' is not at beginning of declaration (in tcp_input.c, as an example). Is there any interest in trying to fix these ? HEAD/sys/netinet/tcp_input.c:218: warning: 'inline' is not at beginning of declaration HEAD/sys/netinet/tcp_input.c:224: warning: 'inline' is not at beginning of declaration HEAD/sys/netinet/tcp_input.c:226: warning: 'inline' is not at beginning of declaration HEAD/sys/netinet/tcp_input.c:227: warning: 'inline' is not at beginning of declaration HEAD/sys/netinet/tcp_input.c:228: warning: 'inline' is not at beginning of declaration HEAD/sys/netinet/tcp_input.c:248: warning: 'inline' is not at beginning of declaration HEAD/sys/netinet/tcp_input.c:266: warning: 'inline' is not at beginning of declaration HEAD/sys/netinet/tcp_input.c:298: warning: 'inline' is not at beginning of declaration HEAD/sys/netinet/tcp_input.c:388: warning: 'inline' is not at beginning of declaration HEAD/sys/netinet/tcp_input.c:440: warning: 'inline' is not at beginning of declaration On a related topic, do we have any mechanism to provide per-subdir or per-file CFLAGS during kernel builds ? I tried to put a Makefile.inc in a subdirectory but it did not help. cheers luigi From owner-freebsd-current@FreeBSD.ORG Wed Jun 1 16:44:52 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5C3451065673 for ; Wed, 1 Jun 2011 16:44:52 +0000 (UTC) (envelope-from uwe@grohnwaldt.eu) Received: from web01.lando.us (web01.lando.us [77.232.247.17]) by mx1.freebsd.org (Postfix) with ESMTP id 2231F8FC1A for ; Wed, 1 Jun 2011 16:44:51 +0000 (UTC) Received: from C3PO (bridge.aixit.com [82.149.224.60]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: uwe@grohnwaldt.eu) by web01.lando.us (Postfix) with ESMTPSA id 276F17CB9C; Wed, 1 Jun 2011 18:44:51 +0200 (CEST) From: "Uwe Grohnwaldt" To: "'Andrey V. Elsukov'" References: <006101cc206b$512599f0$f370cdd0$@grohnwaldt.eu> <4DE660CB.4000508@yandex.ru> In-Reply-To: <4DE660CB.4000508@yandex.ru> Date: Wed, 1 Jun 2011 18:44:51 +0200 Message-ID: <009701cc207b$3a217840$ae6468c0$@grohnwaldt.eu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQEwzLU6L0g5gf83CPRvPK2tE0DiSgHv+gnZlc/dGSA= Content-Language: de Cc: current@freebsd.org Subject: AW: AW: -CURRENT: mountroot failed X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2011 16:44:52 -0000 Hi, i csuped src this morning, where do i find the information about the = exact revision? cu -- Uwe Grohnwaldt -----Urspr=FCngliche Nachricht----- Von: Andrey V. Elsukov [mailto:bu7cher@yandex.ru]=20 Gesendet: Mittwoch, 1. Juni 2011 17:55 An: Uwe Grohnwaldt Cc: current@freebsd.org Betreff: Re: AW: -CURRENT: mountroot failed On 01.06.2011 18:50, Uwe Grohnwaldt wrote: > i have the same problem and setting kern.geom.part.check_integrity=3D0 = > works. I installed my system using sysinstall from 8.2-amd64-CD1. Hi, i added a workaround for this issue in r222341. Which revision do you use? -- WBR, Andrey V. Elsukov From owner-freebsd-current@FreeBSD.ORG Wed Jun 1 17:00:58 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CDC0A1065674 for ; Wed, 1 Jun 2011 17:00:58 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id A63B88FC13 for ; Wed, 1 Jun 2011 17:00:58 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 4901946B0D; Wed, 1 Jun 2011 13:00:58 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id D08758A01F; Wed, 1 Jun 2011 13:00:57 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Date: Wed, 1 Jun 2011 12:59:45 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110325; KDE/4.5.5; amd64; ; ) References: <20110531202142.GA7105@onelab2.iet.unipi.it> In-Reply-To: <20110531202142.GA7105@onelab2.iet.unipi.it> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201106011259.45652.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Wed, 01 Jun 2011 13:00:57 -0400 (EDT) Cc: Luigi Rizzo Subject: Re: "lazy" mmap for a device driver ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2011 17:00:58 -0000 On Tuesday, May 31, 2011 4:21:42 pm Luigi Rizzo wrote: > hi, > i have a kernel module implementing a memory mapped special device > which exports a large block of memory to the process. > I see that when the process calls mmap(), my routine foo_mmap() > is called immediately once per page, even though the process is > not actually touching the pages. I believe this happens > through dev_pager_alloc(). Yes, this is to verify that all the pages in the mmap() request are permitted for access so that an error can be returned to userland if it maps an invalid region of the device's virtual address space. > Right now i can live with that because all the memory is allocated > at module load time, but i might want to have a sparse memory > region which is populated dynamically, so i was wondering if > there is a way to achieve this. I see there are two other > device routines, d_mmap2 and d_mmap_single, any pointer to > documentation or comments on how they differ ? d_mmap2 is an ABI hack in 7/8, it is identical to d_mmap in 9. d_mmap_single() allows a driver to "claim" an entire mmap() request and return an arbitrary VM object. If all you need is a random assortment of pages of a fixed size object that is shared between userland and the kernel, you can create an OBJT_DEFAULT VM object and let it fault in pages on demand perhaps. You would need to be careful to wire the pages if you are going to access them from the kernel. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Wed Jun 1 18:21:32 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2308F106566B; Wed, 1 Jun 2011 18:21:32 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 82BA28FC1F; Wed, 1 Jun 2011 18:21:31 +0000 (UTC) Received: by gwb15 with SMTP id 15so44955gwb.13 for ; Wed, 01 Jun 2011 11:21:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:date:x-google-sender-auth :message-id:subject:from:to:cc:content-type; bh=f7gEazXcXAjB5FWU2gwaRHmdWnQiRN1tt2kKqaGxwys=; b=QBgp9s4U+c0CwX2mAhNZY/jvrDrb5cc7NMIkAud+emI1uDUYDvjUUDf/fUwz8kbcMM agXztQ8iPUNmLsdlhUGANY3uYipYol+XoYFfd7ePjZxYgNBhclW2CofWsDwU005HQbQZ m1NC/nopHv+SEMQI3UpSvRIscOiw2BlUTIl+I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; b=MuNKV0ZSDRODWOI1vNC/NIOBi+R9MyWDltBNMrcoM7knJcNioxcpCKGtHdsnaq5YlC sg0XIjtgB6iDH9SItssVVN6QoywR5knwvuZu67izlmAhwbLvi571U1UWO3kGzESe3aYA dJ+/xZMhO6xcCuAIpg4df3EdEzNkONXHXLyBw= MIME-Version: 1.0 Received: by 10.236.112.199 with SMTP id y47mr8623899yhg.170.1306952490724; Wed, 01 Jun 2011 11:21:30 -0700 (PDT) Sender: asmrookie@gmail.com Received: by 10.236.103.136 with HTTP; Wed, 1 Jun 2011 11:21:30 -0700 (PDT) Date: Wed, 1 Jun 2011 14:21:30 -0400 X-Google-Sender-Auth: pRppI4Qiwmr3bLjmKS0DB1uH0FA Message-ID: From: Attilio Rao To: freebsd-current@freebsd.org Content-Type: text/plain; charset=UTF-8 Cc: Marius Strobl , Sergey Kandaurov , Nick Esborn , Sean Bruno Subject: [PATCH] Add the infrastructure for supporting an infinite number of CPUs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2011 18:21:32 -0000 Current maximum number of CPUs supported by the FreeBSD kernel is 32. That number cames from indirectly by the fact that we have a cpumask_t type, representing a mask of CPUs, which is an unsigned int right now. I then made a patch that removes the cpumask_t type and uses cpuset_t type for characterizing a generic mask of CPUs: http://www.freebsd.org/~attilio/largeSMP/largeSMP-patchset-beta-0.diff This is part of a bigger effort which brought to serveral smaller commits along the way, in order to fix some edge cases. Things to pay attention at: - Userland and kerneland cpuset_t size can be different, thus when accessing to a kernel cpuset_t object from userland (via kvm_read() for example) a pattern similar to what pmccontrol does, in this patch, should be followed - There are some cpuset_t object in pcpu representing curcpu mask and !curcpu mask. With transition from cpumask_t to cpuset_t they become inefficient and not really useful. The next weeks I'll focus on removing them and make a smarter usage of the cpuset_t interface. Additively, please note that right now I clobbered pcpu accesses under scheduler pinnings, because it is possible more than a single atomic operation is needed for accessing a cpuset_t. When the cleanup happens those pinnings will go away. - I had to introduce, among the other things, functions for representing cpuset_t object in "visual" way, thus cpusetobj_strprint() and cpusetobj_strscan(). I got the desired format from what Linux already does, so that someone may be already used to it. Anyway strings will be represented as a serie of long, hexadecimal long words, all separated by ", ". The left-most represents the higher word, following natural bits representation. - I used cpusetobj_strscan() for implementing KTR_CPUMASK in a way it supports cpuset_t. Change the kernel config appropriately. - No MAXCPU has been bumped in the patch, but I encourage you to do so with your own kernel configurations. I really need to commit this patch before code slush happens, thus I plan to commit it on June 7th, if no one reports bugs or can make good point on his reviews. Please note that the patch has been greatly tested and reviewed on all FreeBSD tier-1 and tier-2 architectures. Anyway more testing and reviews are welcome to happen. Thanks, Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-current@FreeBSD.ORG Wed Jun 1 20:18:09 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CAD31106564A; Wed, 1 Jun 2011 20:18:09 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 52B6C8FC13; Wed, 1 Jun 2011 20:18:08 +0000 (UTC) Received: by vxc34 with SMTP id 34so212260vxc.13 for ; Wed, 01 Jun 2011 13:18:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=lvCrJFGfoBD9IoC5ZJdV3lep3urc0TRqpaQZ8lUhQsk=; b=omnNBYVJL7E4y0xL0ohMP6PI2XxrF+u6lqBL4wThUyaz42ChWCFcGsTJE2AXCRy/ku cCJuYPNySQbnq9PWd01Qkzqdo4NAc6c4ZpGIsuvDj9UOgXpz467tTe6Eb8AR/G8jyuEx jjlx4QW1t+Of5OU8ptFzhro2XDPoplk6jUtlQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=p8zflTSr4NU7lgrxSduaVYPMOJV4BM5K8mt9FBQiqfYn+pxglsT4pMSM2oaUtep5p8 rnb+SeX1hSP9fdDgTEIUcbmYQ4aMs4m4hGWnlEAE6i9mEKA0rgX5sJbdj8I2V5kV59/4 2wsfBXpx3hWLre3U7EJReRYZgBUEjGBmDDM3k= MIME-Version: 1.0 Received: by 10.52.175.132 with SMTP id ca4mr2438323vdc.98.1306957605226; Wed, 01 Jun 2011 12:46:45 -0700 (PDT) Received: by 10.52.107.97 with HTTP; Wed, 1 Jun 2011 12:46:45 -0700 (PDT) In-Reply-To: References: Date: Wed, 1 Jun 2011 12:46:45 -0700 Message-ID: From: Jack Vogel To: Attilio Rao Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Nick Esborn , Marius Strobl , freebsd-current@freebsd.org, Sergey Kandaurov , Sean Bruno Subject: Re: [PATCH] Add the infrastructure for supporting an infinite number of CPUs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2011 20:18:09 -0000 Awesome, glad to see this happening :) Jack On Wed, Jun 1, 2011 at 11:21 AM, Attilio Rao wrote: > Current maximum number of CPUs supported by the FreeBSD kernel is 32. > That number cames from indirectly by the fact that we have a cpumask_t > type, representing a mask of CPUs, which is an unsigned int right now. > I then made a patch that removes the cpumask_t type and uses cpuset_t > type for characterizing a generic mask of CPUs: > http://www.freebsd.org/~attilio/largeSMP/largeSMP-patchset-beta-0.diff > > This is part of a bigger effort which brought to serveral smaller > commits along the way, in order to fix some edge cases. > > Things to pay attention at: > - Userland and kerneland cpuset_t size can be different, thus when > accessing to a kernel cpuset_t object from userland (via kvm_read() > for example) a pattern similar to what pmccontrol does, in this patch, > should be followed > - There are some cpuset_t object in pcpu representing curcpu mask and > !curcpu mask. With transition from cpumask_t to cpuset_t they become > inefficient and not really useful. The next weeks I'll focus on > removing them and make a smarter usage of the cpuset_t interface. > Additively, please note that right now I clobbered pcpu accesses > under scheduler pinnings, because it is possible more than a single > atomic operation is needed for accessing a cpuset_t. When the cleanup > happens those pinnings will go away. > - I had to introduce, among the other things, functions for > representing cpuset_t object in "visual" way, thus > cpusetobj_strprint() and cpusetobj_strscan(). I got the desired format > from what Linux already does, so that someone may be already used to > it. Anyway strings will be represented as a serie of long, hexadecimal > long words, all separated by ", ". The left-most represents the higher > word, following natural bits representation. > - I used cpusetobj_strscan() for implementing KTR_CPUMASK in a way it > supports cpuset_t. Change the kernel config appropriately. > - No MAXCPU has been bumped in the patch, but I encourage you to do so > with your own kernel configurations. > > I really need to commit this patch before code slush happens, thus I > plan to commit it on June 7th, if no one reports bugs or can make good > point on his reviews. Please note that the patch has been greatly > tested and reviewed on all FreeBSD tier-1 and tier-2 architectures. > Anyway more testing and reviews are welcome to happen. > > Thanks, > Attilio > > > -- > Peace can only be achieved by understanding - A. Einstein > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Wed Jun 1 22:17:53 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 44A021065678 for ; Wed, 1 Jun 2011 22:17:53 +0000 (UTC) (envelope-from uwe@grohnwaldt.eu) Received: from web01.lando.us (web01.lando.us [77.232.247.17]) by mx1.freebsd.org (Postfix) with ESMTP id 0C0988FC23 for ; Wed, 1 Jun 2011 22:17:52 +0000 (UTC) Received: from Jabba (p4FFD1F38.dip.t-dialin.net [79.253.31.56]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: uwe@grohnwaldt.eu) by web01.lando.us (Postfix) with ESMTPSA id 09CB47C055; Thu, 2 Jun 2011 00:17:52 +0200 (CEST) From: "Uwe Grohnwaldt" To: "'Andrey V. Elsukov'" References: <006101cc206b$512599f0$f370cdd0$@grohnwaldt.eu> <4DE660CB.4000508@yandex.ru> In-Reply-To: <4DE660CB.4000508@yandex.ru> Date: Thu, 2 Jun 2011 00:17:52 +0200 Message-ID: <00c801cc20a9$bff247f0$3fd6d7d0$@grohnwaldt.eu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQEwzLU6L0g5gf83CPRvPK2tE0DiSgHv+gnZldA51uA= Content-Language: de Cc: current@freebsd.org Subject: AW: AW: -CURRENT: mountroot failed X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2011 22:17:53 -0000 Hi, I build a kernel using src from svn. I have the same error. svn info shows Last Changed Rev: 222585 -- Uwe Grohnwaldt -----Urspr=FCngliche Nachricht----- Von: Andrey V. Elsukov [mailto:bu7cher@yandex.ru]=20 Gesendet: Mittwoch, 1. Juni 2011 17:55 An: Uwe Grohnwaldt Cc: current@freebsd.org Betreff: Re: AW: -CURRENT: mountroot failed On 01.06.2011 18:50, Uwe Grohnwaldt wrote: > i have the same problem and setting kern.geom.part.check_integrity=3D0 = > works. I installed my system using sysinstall from 8.2-amd64-CD1. Hi, i added a workaround for this issue in r222341. Which revision do you use? -- WBR, Andrey V. Elsukov From owner-freebsd-current@FreeBSD.ORG Thu Jun 2 04:23:30 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F027C106564A for ; Thu, 2 Jun 2011 04:23:30 +0000 (UTC) (envelope-from jhellenthal@gmail.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 7107C8FC0C for ; Thu, 2 Jun 2011 04:23:30 +0000 (UTC) Received: by gwb15 with SMTP id 15so316836gwb.13 for ; Wed, 01 Jun 2011 21:23:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:date:from:to:cc:subject:message-id :reply-to:references:mime-version:content-type:content-disposition :in-reply-to:x-openpgp-key-id:x-openpgp-key-fingerprint :x-openpgp-key-url; bh=UQQlZ6fKiyHVWf4ot8u9iWZIdiLlVx3L4qSNzT22ERg=; b=vcqCZq2EJhNAobhuG9Y0yeiI/j4iLAt7nS+jq/GXQKYu9OpPiD3dT9wvtloeMwODtJ jKr8G1nOiuJe4pa/bF0QPDusjUGKCJRzhgfWc0P+HeIxhQmqvWuCjvk/JSeqeNtnLH2B GnmRguX0REccdv0TSJdg+z++rYkZCLFz1sL64= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:date:from:to:cc:subject:message-id:reply-to:references :mime-version:content-type:content-disposition:in-reply-to :x-openpgp-key-id:x-openpgp-key-fingerprint:x-openpgp-key-url; b=pgIpV/r6eYfvheMQS5z9WRUSos5q2KA808LGLUng+pLuW9fHYD964vxUEfpndfDeSQ R1hZV4wWSqBWTolQL6jC4li7Vl/Dz0gKS1HIS8VbtslpYhPeAzMcEfZwszLlz2snIs7i JiAOFkDVo6wACykvAZkSMeYq1sSKEnkep+4Fs= Received: by 10.150.31.4 with SMTP id e4mr245561ybe.127.1306988609580; Wed, 01 Jun 2011 21:23:29 -0700 (PDT) Received: from DataIX.net (adsl-99-19-42-166.dsl.klmzmi.sbcglobal.net [99.19.42.166]) by mx.google.com with ESMTPS id d30sm128733ybd.24.2011.06.01.21.23.26 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 01 Jun 2011 21:23:27 -0700 (PDT) Sender: "J. Hellenthal" Received: from DataIX.net (localhost [127.0.0.1]) by DataIX.net (8.14.4/8.14.4) with ESMTP id p524NSxx005509 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 Jun 2011 00:23:28 -0400 (EDT) (envelope-from jhell@DataIX.net) Received: (from jhell@localhost) by DataIX.net (8.14.4/8.14.4/Submit) id p524NQdv005501; Thu, 2 Jun 2011 00:23:26 -0400 (EDT) (envelope-from jhell@DataIX.net) Date: Thu, 2 Jun 2011 00:23:26 -0400 From: Jason Hellenthal To: Attilio Rao Message-ID: <20110602042326.GA3103@DataIX.net> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="4Ckj6UjgE2iN1+kY" Content-Disposition: inline In-Reply-To: X-OpenPGP-Key-Id: 0x89D8547E X-OpenPGP-Key-Fingerprint: 85EF E26B 07BB 3777 76BE B12A 9057 8789 89D8 547E X-OpenPGP-Key-URL: http://bit.ly/0x89D8547E Cc: Nick Esborn , Marius Strobl , freebsd-current@freebsd.org, Sergey Kandaurov , Sean Bruno Subject: Re: [PATCH] Add the infrastructure for supporting an infinite number of CPUs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jhell@DataIX.net List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2011 04:23:31 -0000 --4Ckj6UjgE2iN1+kY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Attilio, AWESOME! to say the least, but I am sure there is a LOT more to be said. Thank YOU! On Wed, Jun 01, 2011 at 02:21:30PM -0400, Attilio Rao wrote: > Current maximum number of CPUs supported by the FreeBSD kernel is 32. > That number cames from indirectly by the fact that we have a cpumask_t > type, representing a mask of CPUs, which is an unsigned int right now. > I then made a patch that removes the cpumask_t type and uses cpuset_t > type for characterizing a generic mask of CPUs: > http://www.freebsd.org/~attilio/largeSMP/largeSMP-patchset-beta-0.diff >=20 > This is part of a bigger effort which brought to serveral smaller > commits along the way, in order to fix some edge cases. >=20 > Things to pay attention at: > - Userland and kerneland cpuset_t size can be different, thus when > accessing to a kernel cpuset_t object from userland (via kvm_read() > for example) a pattern similar to what pmccontrol does, in this patch, > should be followed > - There are some cpuset_t object in pcpu representing curcpu mask and > !curcpu mask. With transition from cpumask_t to cpuset_t they become > inefficient and not really useful. The next weeks I'll focus on > removing them and make a smarter usage of the cpuset_t interface. > Additively, please note that right now I clobbered pcpu accesses > under scheduler pinnings, because it is possible more than a single > atomic operation is needed for accessing a cpuset_t. When the cleanup > happens those pinnings will go away. > - I had to introduce, among the other things, functions for > representing cpuset_t object in "visual" way, thus > cpusetobj_strprint() and cpusetobj_strscan(). I got the desired format > from what Linux already does, so that someone may be already used to > it. Anyway strings will be represented as a serie of long, hexadecimal > long words, all separated by ", ". The left-most represents the higher > word, following natural bits representation. > - I used cpusetobj_strscan() for implementing KTR_CPUMASK in a way it > supports cpuset_t. Change the kernel config appropriately. > - No MAXCPU has been bumped in the patch, but I encourage you to do so > with your own kernel configurations. >=20 > I really need to commit this patch before code slush happens, thus I > plan to commit it on June 7th, if no one reports bugs or can make good > point on his reviews. Please note that the patch has been greatly > tested and reviewed on all FreeBSD tier-1 and tier-2 architectures. > Anyway more testing and reviews are welcome to happen. >=20 > Thanks, > Attilio >=20 >=20 > --=20 > Peace can only be achieved by understanding - A. Einstein > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" --=20 "Unity can only be manifested by the Binary. Unity itself and the idea of U= nity are already two." -- Buddha Regards, (jhell) Jason Hellenthal --4Ckj6UjgE2iN1+kY Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (FreeBSD) Comment: http://bit.ly/0x89D8547E iQEcBAEBAgAGBQJN5xA9AAoJEJBXh4mJ2FR+RLYIAJl7YVG8e8jB2BnzrGusvprj vHlv6n43XXV3/amnecnavhcS0tcTv4VrAwjOgCUmQj/OVDrt12TckSIwrrgCb1OC 3Ga8z/8Rd3sK1LBGsLZ67eVSc/eALGhuKpCCSwxMGeoBZ1cIStSmx6dskYYiXuTA wXz7aS6MKQCjwWK/7a1iEcN0nNHKENRnIeIAnvyR5LaMH6UePo7hI6vvTQym5aHK slkZc5voWRYPzYA6AUNGzMmk4uDk7+b4/8TbPL1vqQsDdYn+T9HB8YFCzK57kEcE egaHt1F12xf2aMhJgKvvymwlpWfTLeYjl+g+5SFpAuVmPOdks/LJh0RI23EcsN8= =DQtV -----END PGP SIGNATURE----- --4Ckj6UjgE2iN1+kY-- From owner-freebsd-current@FreeBSD.ORG Thu Jun 2 04:57:13 2011 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3AA6D106566B; Thu, 2 Jun 2011 04:57:13 +0000 (UTC) (envelope-from bz@FreeBSD.org) Received: from mx1.sbone.de (mx1.sbone.de [IPv6:2a01:4f8:130:3ffc::401:25]) by mx1.freebsd.org (Postfix) with ESMTP id E55528FC0C; Thu, 2 Jun 2011 04:57:12 +0000 (UTC) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id 2C0D825D385D; Thu, 2 Jun 2011 04:57:12 +0000 (UTC) Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id 63968159FE84; Thu, 2 Jun 2011 04:57:11 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id UZLayjTstG+7; Thu, 2 Jun 2011 04:57:10 +0000 (UTC) Received: from orange-en1.sbone.de (orange-en1.sbone.de [IPv6:fde9:577b:c1a9:31:cabc:c8ff:fecf:e8e3]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 29447159FE7C; Thu, 2 Jun 2011 04:57:10 +0000 (UTC) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: "Bjoern A. Zeeb" In-Reply-To: Date: Thu, 2 Jun 2011 04:57:09 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Robert Watson X-Mailer: Apple Mail (2.1084) Cc: current@FreeBSD.org Subject: Re: FYI: merging TCP, UDP, netisr locking changes X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2011 04:57:13 -0000 On May 30, 2011, at 9:53 AM, Robert Watson wrote: >> This work has been sponsored by Juniper Networks. Thanks also to = Bjoern Zeeb, who has been reviewing changes! And pointy hat to me for missing this one:( > After a series of smaller commits, I've just merged some initial = decomposition of the pcbinfo lock into an additional pcbhash lock, which = changes lock ordering and lookup with respect to inpcbs significantly = (r222488; commit message below). I expect there to be some initial = instability as people shake out edge cases I didn't bump into in my = testing. Please report bugs to current@, and I'll pick them up there! Can you review the following I found this morning on my IPv6 only snapshot VM. We need to make sure all the src/tools/regression test cases equally run IPv6. Patches certainly welcome from the community! ! ! Do not leak the pcbinfohash lock in case in6_pcbladdr() errors ! for a tcp connect on IPv6. ! ! Submitted by: bz ! Index: sys/netinet/tcp_usrreq.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- sys/netinet/tcp_usrreq.c (revision 222591) +++ sys/netinet/tcp_usrreq.c (working copy) @@ -1158,7 +1158,7 @@ tcp6_connect(struct tcpcb *tp, struct sockaddr *na */ error =3D in6_pcbladdr(inp, nam, &addr6); if (error) - return error; + goto out; oinp =3D in6_pcblookup_hash_locked(inp->inp_pcbinfo, &sin6->sin6_addr, sin6->sin6_port, = IN6_IS_ADDR_UNSPECIFIED(&inp->in6p_laddr) --=20 Bjoern A. Zeeb You have to have visions! Stop bit received. Insert coin for new address family. From owner-freebsd-current@FreeBSD.ORG Thu Jun 2 08:50:33 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 98493106564A for ; Thu, 2 Jun 2011 08:50:33 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward2.mail.yandex.net (forward2.mail.yandex.net [77.88.46.7]) by mx1.freebsd.org (Postfix) with ESMTP id 40C0B8FC13 for ; Thu, 2 Jun 2011 08:50:32 +0000 (UTC) Received: from smtp2.mail.yandex.net (smtp2.mail.yandex.net [77.88.46.102]) by forward2.mail.yandex.net (Yandex) with ESMTP id 6193512A6DD0; Thu, 2 Jun 2011 12:50:31 +0400 (MSD) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1307004631; bh=VYLtUorA8VYWkaL870rfTd2kZg/M1sGRo1NU39NIn/c=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type; b=wCRuy7iS4Rt6PhtzygzjJ0auiYwB0ckllHIqWXJWT/9Rm55fBTBEpmphEUvJIFty2 NPIsgd7HAr/qAVrXK019UXm8UD1yUZkc1seMz52sRRDRXouaE4dNlEAB4kwVSCIHEN v5q2Br8982s415avdJc3Ce9QSF4xKRjPcC2lBF5Y= Received: from [127.0.0.1] (ns.kirov.so-ups.ru [77.72.136.145]) by smtp2.mail.yandex.net (Yandex) with ESMTPSA id 269DD5D100C8; Thu, 2 Jun 2011 12:50:31 +0400 (MSD) Message-ID: <4DE74ED3.40006@yandex.ru> Date: Thu, 02 Jun 2011 12:50:27 +0400 From: "Andrey V. Elsukov" User-Agent: Mozilla Thunderbird 1.5 (FreeBSD/20051231) MIME-Version: 1.0 To: Uwe Grohnwaldt References: <006101cc206b$512599f0$f370cdd0$@grohnwaldt.eu> <4DE660CB.4000508@yandex.ru> <00c801cc20a9$bff247f0$3fd6d7d0$@grohnwaldt.eu> In-Reply-To: <00c801cc20a9$bff247f0$3fd6d7d0$@grohnwaldt.eu> X-Enigmail-Version: 1.1.1 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigE96A89B930AACE1EA985AF66" X-Yandex-Spam: 1 Cc: current@freebsd.org Subject: Re: AW: AW: -CURRENT: mountroot failed X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2011 08:50:33 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigE96A89B930AACE1EA985AF66 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable On 02.06.2011 2:17, Uwe Grohnwaldt wrote: > Hi, >=20 > I build a kernel using src from svn. I have the same error. > svn info shows Last Changed Rev: 222585 You should enable bootverbose mode and show all messages that begins from GEOM_PART. --=20 WBR, Andrey V. Elsukov --------------enigE96A89B930AACE1EA985AF66 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) iQEcBAEBAgAGBQJN507XAAoJEAHF6gQQyKF6llMH/jEgw9/iOC8m55Dq7hS7XKob dZ75SjmXOYs1mqj/ABO5gwct6dC38MNyrRnxh+6XMNfTD3y/OmjZdnZaf/v5eAqH zLV4l8BbxV2jgoB2j7JN4vU00Op9DdgRe0vvfx5XSWAEmBNVvXQEzbe2ebHvnFDm 1qwRqbN1fvcuGoVeWiwmUdPcA2yUiQHuzmv/vLAv0yJO0RcN3GJvxYVDXWdKLt7X /Qgbt1cDp5ZFEnjh6YdegGQnqH9DxoIymqnaREpD6HFvlW0W3pbXegS177Xkc6de PJrESZXNe903fn6AU1pYaSliElZM4uw+P0B5eq+yVgrL2WKb+XKvziqbMtjgJlQ= =Ugii -----END PGP SIGNATURE----- --------------enigE96A89B930AACE1EA985AF66-- From owner-freebsd-current@FreeBSD.ORG Thu Jun 2 10:16:09 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 29A5B106564A for ; Thu, 2 Jun 2011 10:16:09 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id DE3178FC08 for ; Thu, 2 Jun 2011 10:16:08 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) for freebsd-current@freebsd.org with esmtp (envelope-from ) id <1QS4wi-0002wa-1B>; Thu, 02 Jun 2011 12:16:08 +0200 Received: from e178016025.adsl.alicedsl.de ([85.178.16.25] helo=thor.walstatt.dyndns.org) by inpost2.zedat.fu-berlin.de (Exim 4.69) for freebsd-current@freebsd.org with esmtpsa (envelope-from ) id <1QS4wh-0002Qe-Uf>; Thu, 02 Jun 2011 12:16:08 +0200 Message-ID: <4DE762E7.10803@zedat.fu-berlin.de> Date: Thu, 02 Jun 2011 12:16:07 +0200 From: "Hartmann, O." User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.17) Gecko/20110601 Lightning/1.0b2 Thunderbird/3.1.10 To: FreeBSD Current Content-Transfer-Encoding: 7bit X-Originating-IP: 85.178.16.25 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: -O3 -mtune=native -march=native seems to heal problem when compiling with CLANG X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2011 10:16:09 -0000 Earlier last month I realized that some ports crashes on FreeBSD 9.0-CURRENT/smd64 (most recent sources), when compiled with CLANG. In particular astro/stellarium and editors/leibreoffice (3.3.2) crashed. Those crashes where recognized on all boxes with world compiled with CLANG and default optimizations or -O2 -march=native. All boxes in question do have Core2Duo (Core2) CPUs . I tried now "-O3 -march=native -mtune=native" on all those boxes while compiling with CLANG and now the crashing software in question is now working correct as expected. This is strange! Oliver P.S. I have a notebook with a Core-i5 based CPU (Clarkdale). This notebook completely fails installing FreeBSD 9.0-CURRENT/amd64 compiled with CLANG (I reported this). Compiling performed with the given defaults. I'll try to compile the OS with -O3 also and see ... From owner-freebsd-current@FreeBSD.ORG Thu Jun 2 12:23:18 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 855F0106566C for ; Thu, 2 Jun 2011 12:23:18 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 426328FC12 for ; Thu, 2 Jun 2011 12:23:18 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1QS6vl-0000gk-EY for freebsd-current@freebsd.org; Thu, 02 Jun 2011 14:23:17 +0200 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 02 Jun 2011 14:23:17 +0200 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 02 Jun 2011 14:23:17 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Ivan Voras Date: Thu, 02 Jun 2011 14:23:00 +0200 Lines: 15 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.12) Gecko/20101102 Thunderbird/3.1.6 In-Reply-To: X-Enigmail-Version: 1.1.2 Subject: Re: [PATCH] Add the infrastructure for supporting an infinite number of CPUs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2011 12:23:18 -0000 On 01/06/2011 20:21, Attilio Rao wrote: > Current maximum number of CPUs supported by the FreeBSD kernel is 32. > That number cames from indirectly by the fact that we have a cpumask_t > type, representing a mask of CPUs, which is an unsigned int right now. > I then made a patch that removes the cpumask_t type and uses cpuset_t > type for characterizing a generic mask of CPUs: > http://www.freebsd.org/~attilio/largeSMP/largeSMP-patchset-beta-0.diff Hi, I'm just wandering: what is the expected overhead of this, compared to using a simple atomic integer (32-bit on i386, 64-bit on amd64)? I assume that this will introduce more work, like locking, in performance-critical code like the scheduler, etc.? From owner-freebsd-current@FreeBSD.ORG Thu Jun 2 12:30:09 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6873F106566B for ; Thu, 2 Jun 2011 12:30:09 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 1E1F68FC13 for ; Thu, 2 Jun 2011 12:30:08 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1QS72J-0004MJ-Te for freebsd-current@freebsd.org; Thu, 02 Jun 2011 14:30:03 +0200 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 02 Jun 2011 14:30:03 +0200 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 02 Jun 2011 14:30:03 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Ivan Voras Date: Thu, 02 Jun 2011 14:29:51 +0200 Lines: 25 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.12) Gecko/20101102 Thunderbird/3.1.6 In-Reply-To: X-Enigmail-Version: 1.1.2 Subject: Re: [PATCH] Add the infrastructure for supporting an infinite number of CPUs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2011 12:30:09 -0000 On 02/06/2011 14:23, Ivan Voras wrote: > On 01/06/2011 20:21, Attilio Rao wrote: >> Current maximum number of CPUs supported by the FreeBSD kernel is 32. >> That number cames from indirectly by the fact that we have a cpumask_t >> type, representing a mask of CPUs, which is an unsigned int right now. >> I then made a patch that removes the cpumask_t type and uses cpuset_t >> type for characterizing a generic mask of CPUs: >> http://www.freebsd.org/~attilio/largeSMP/largeSMP-patchset-beta-0.diff > > Hi, > > I'm just wandering: what is the expected overhead of this, compared to > using a simple atomic integer (32-bit on i386, 64-bit on amd64)? I > assume that this will introduce more work, like locking, in > performance-critical code like the scheduler, etc.? The reason why I'm asking is this: http://msdn.microsoft.com/en-us/library/dd405503%28v=vs.85%29.aspx It's not necessarily a good approach, but it does have the benefit of keeping the CPU mask operations atomic... (I don't know if the benefits of this are big enough). From owner-freebsd-current@FreeBSD.ORG Thu Jun 2 13:02:46 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 874E0106566C for ; Thu, 2 Jun 2011 13:02:46 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 2516D8FC12 for ; Thu, 2 Jun 2011 13:02:45 +0000 (UTC) Received: by vws18 with SMTP id 18so839679vws.13 for ; Thu, 02 Jun 2011 06:02:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=//op7Z3e5E8EjSyDjsT6hHVmlMMLnnnBM1uzq+Ee3BA=; b=H6EHGXT7w1XvKfRNJ9CtE0uOlV1rW8eq94lW4S2EZeT7IXRREeiIlz1ROLClSUCkV6 m6IXhiMHMU23Bnoo90p1bhNEbx0qnnWqgm7jMGIUrgS1mxrFglKkpEAP3UPpSwdJKH+i DnbB49AtNQgd+XjEFYne30oUAJ2YxSP78NkW4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=jAKOFKK8d8dUe9kQfyMGnRtB0mPtEZnVjLTjHHwzRLHkQW767R7KQUEXtjRd2Ae2ov hsDcJPZcBTMDAYNIZxRt3mvhsN6sYgp4h8bFab3EbWsS1k1/0VfR/tTuzPqbxvgEzdJH JRZewLrDSDGu6r/s/CQ1v1qpTFvMiY7pN+6wg= MIME-Version: 1.0 Received: by 10.52.175.137 with SMTP id ca9mr264587vdc.194.1307019765300; Thu, 02 Jun 2011 06:02:45 -0700 (PDT) Sender: asmrookie@gmail.com Received: by 10.220.178.65 with HTTP; Thu, 2 Jun 2011 06:02:44 -0700 (PDT) In-Reply-To: References: Date: Thu, 2 Jun 2011 09:02:44 -0400 X-Google-Sender-Auth: xFbTYcwaNm9tOE-NY5sOV-a4ebo Message-ID: From: Attilio Rao To: Ivan Voras Content-Type: text/plain; charset=UTF-8 Cc: freebsd-current@freebsd.org Subject: Re: [PATCH] Add the infrastructure for supporting an infinite number of CPUs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2011 13:02:46 -0000 2011/6/2 Ivan Voras : > On 02/06/2011 14:23, Ivan Voras wrote: >> >> On 01/06/2011 20:21, Attilio Rao wrote: >>> >>> Current maximum number of CPUs supported by the FreeBSD kernel is 32. >>> That number cames from indirectly by the fact that we have a cpumask_t >>> type, representing a mask of CPUs, which is an unsigned int right now. >>> I then made a patch that removes the cpumask_t type and uses cpuset_t >>> type for characterizing a generic mask of CPUs: >>> http://www.freebsd.org/~attilio/largeSMP/largeSMP-patchset-beta-0.diff >> >> Hi, >> >> I'm just wandering: what is the expected overhead of this, compared to >> using a simple atomic integer (32-bit on i386, 64-bit on amd64)? I >> assume that this will introduce more work, like locking, in >> performance-critical code like the scheduler, etc.? Once the cleanup of this code is finished (read one of the point of my patches) only some global variables will still be needed to be used as cpuset_t whole operation (all_cpus, for example) and they are all used rarely enough that should be negligible. FreeBSD right now uses the cpuset_t mostly for these things: - pcpu masks (pc_cpumask, pc_other_cpus) - pmap pm_active - global masks for tracking online CPU, HTT, etc. The second type is just accessed on a bit basis, so it doesn't apply. The first one will be optimized in the next round of changes. As said, just the third type will remain and really is a minor factor in performance. > The reason why I'm asking is this: > > http://msdn.microsoft.com/en-us/library/dd405503%28v=vs.85%29.aspx > > It's not necessarily a good approach, but it does have the benefit of > keeping the CPU mask operations atomic... (I don't know if the benefits of > this are big enough). Well, it is just actually bypassing the problem and also I'm not entirely sure it is a great idea from other point of views. In particular, I've never seen so far a 64 cpus system offering homogeinity among them, I wonder how you can consider a single schedule entity something like 8 x 4 x 4(htt)? Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-current@FreeBSD.ORG Thu Jun 2 17:39:30 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2B8EB1065670 for ; Thu, 2 Jun 2011 17:39:30 +0000 (UTC) (envelope-from bartosz.stec@it4pro.pl) Received: from mainframe.kkip.pl (kkip.pl [87.105.164.78]) by mx1.freebsd.org (Postfix) with ESMTP id 4D31D8FC0A for ; Thu, 2 Jun 2011 17:39:29 +0000 (UTC) Received: from static-78-8-144-74.ssp.dialog.net.pl ([78.8.144.74]) by mainframe.kkip.pl with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.76 (FreeBSD)) (envelope-from ) id 1QSBZ7-0000eF-0P for freebsd-current@freebsd.org; Thu, 02 Jun 2011 19:20:25 +0200 Message-ID: <4DE7C63C.7010705@it4pro.pl> Date: Thu, 02 Jun 2011 19:19:56 +0200 From: Bartosz Stec Organization: IT4Pro User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; pl; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: freebsd-current@freebsd.org X-Authenticated-User: bartosz.stec@it4pro.pl X-Authenticator: plain X-Sender-Verify: SUCCEEDED (sender exists & accepts mail) X-Spam-Score: -8.0 X-Spam-Score-Int: -79 X-Exim-Version: 4.76 (build at 12-May-2011 10:41:54) X-Date: 2011-06-02 19:20:25 X-Connected-IP: 78.8.144.74:50192 X-Message-Linecount: 657 X-Body-Linecount: 646 X-Message-Size: 30814 X-Body-Size: 30338 X-Received-Count: 1 X-Recipient-Count: 1 X-Local-Recipient-Count: 1 X-Local-Recipient-Defer-Count: 0 X-Local-Recipient-Fail-Count: 0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: [ZFSv28] Loader hangs, import failes, zfs filesystem unavailable. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2011 17:39:30 -0000 Hi list, Today I needed to shut down my home server (FreeSBD9-CURRENT, 3 x 40GB ATA HDD in RADZ1, ZFS only, GPT, i386) for a moment. After power up, loader started to spin cursor indifinitely, and didn't load the kernel. No error messages, no hints, just spinning cursor. I tried booting from other HDDs in case that bootstrap area errors on single hdd but no luck. I wanted to play with latest current LiveFS snapshot (with ZFSv28 support), but apparently latest one is from february?? Finally I ended with mfsBSD from http://mfsbsd.vx.sk/ I've downloaded "8.2-RELEASE-i386 with ZFSv28 special edition " iso, burned it and booted machine. Here's what happened when i was trying to import zpool: mfsbsd# zpool status no pools available mfsbsd# zpool import pool: zroot id: 16074929158756467860 state: ONLINE status: The pool was last accessed by another system. action: The pool can be imported using its name or numeric identifier and the '-f' flag. see: http://www.sun.com/msg/ZFS-8000-EY config: zroot ONLINE raidz1-0 ONLINE gptid/2ea57c66-bc69-11df-8955-0050dad823cd ONLINE gptid/5bc92016-6852-11df-a16c-0050dad823cd ONLINE gptid/87d467cc-bc3b-11df-8066-0050dad823cd ONLINE mfsbsd# zpool import -f zroot cannot import 'zroot': one or more devices is currently unavailable There was also some kernel messages while running zpool commands, they are visible at the end of dmesg output: mfsbsd# dmesg Copyright (c) 1992-2011 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 8.2-RELEASE #2 r219081M: Wed Mar 2 10:29:25 CET 2011 root@www4:/usr/obj/i386/usr/src_v28/sys/GENERIC i386 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: mobile AMD Athlon(tm) XP 2200+ (1800.08-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x681 Family = 6 Model = 8 Stepping = 1 Features=0x383fbff AMD Features=0xc0480800 real memory = 2147483648 (2048 MB) avail memory = 2053263360 (1958 MB) ACPI APIC Table: ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: on hostb0 agp0: aperture size is 128M pcib1: at device 1.0 on pci0 pci1: on pcib1 vgapci0: mem 0xdfe80000-0xdfefffff,0xd0000000-0xd7ffffff irq 16 at device 0.0 on pci1 xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0xec00-0xec7f mem 0xdfffff80-0xdfffffff irq 17 at device 6.0 on pci0 miibus0: on xl0 xlphy0: <3Com internal media interface> PHY 24 on miibus0 xlphy0: 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, auto, auto-flow xl0: Ethernet address: 00:50:da:d8:23:cd xl0: [ITHREAD] rl0: port 0xe800-0xe8ff mem 0xdffffe00-0xdffffeff irq 18 at device 7.0 on pci0 miibus1: on rl0 rlphy0: PHY 0 on miibus1 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:40:f4:b4:e9:3c rl0: [ITHREAD] uhci0: port 0xdc00-0xdc1f irq 21 at device 16.0 on pci0 uhci0: [ITHREAD] usbus0: on uhci0 uhci1: port 0xe000-0xe01f irq 21 at device 16.1 on pci0 uhci1: [ITHREAD] usbus1: on uhci1 uhci2: port 0xe400-0xe41f irq 21 at device 16.2 on pci0 uhci2: [ITHREAD] usbus2: on uhci2 ehci0: mem 0xdffffd00-0xdffffdff irq 21 at device 16.3 on pci0 ehci0: [ITHREAD] usbus3: EHCI version 1.0 usbus3: on ehci0 isab0: at device 17.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 17.1 on pci0 ata0: on atapci0 ata0: [ITHREAD] ata1: on atapci0 ata1: [ITHREAD] pci0: at device 17.6 (no driver attached) acpi_button1: on acpi0 fdc0: port 0x3f2-0x3f3,0x3f4-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FILTER] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 uart0: [FILTER] uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0 uart1: [FILTER] ppc0: port 0x378-0x37f,0x778-0x77b irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppc0: [ITHREAD] ppbus0: on ppc0 plip0: on ppbus0 plip0: [ITHREAD] lpt0: on ppbus0 lpt0: [ITHREAD] lpt0: Interrupt-driven port ppi0: on ppbus0 atrtc0: port 0x70-0x71 irq 8 on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] pmtimer0 on isa0 orm0: at iomem 0xc0000-0xc9fff pnpid ORM0000 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 acpi_throttle0: on cpu0 powernow0: on cpu0 device_attach: powernow0 attach returned 6 Timecounter "TSC" frequency 1800078810 Hz quality 800 Timecounters tick every 1.000 msec md0: Preloaded image 33923072 bytes at 0xc0fd9834 usbus0: 12Mbps Full Speed USB v1.0 usbus1: 12Mbps Full Speed USB v1.0 usbus2: 12Mbps Full Speed USB v1.0 usbus3: 480Mbps High Speed USB v2.0 ad0: 39205MB at ata0-master UDMA133 ugen0.1: at usbus0 uhub0: on usbus0 ugen1.1: at usbus1 uhub1: on usbus1 ugen2.1: at usbus2 uhub2: on usbus2 ugen3.1: at usbus3 uhub3: on usbus3 ad1: 38166MB at ata0-slave UDMA100 ad2: 39205MB at ata1-master UDMA133 uhub0: 2 ports with 2 removable, self powered uhub1: 2 ports with 2 removable, self powered uhub2: 2 ports with 2 removable, self powered acd0: DVDROM at ata1-slave UDMA33 uhub3: 6 ports with 6 removable, self powered acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00 acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00 Trying to mount root from ufs:/dev/md0 ZFS NOTICE: Prefetch is disabled by default on i386 -- to enable, add "vfs.zfs.prefetch_disable=0" to /boot/loader.conf. ZFS WARNING: Recommended minimum kmem_size is 512MB; expect unstable behavior. Consider tuning vm.kmem_size and vm.kmem_size_max in /boot/loader.conf. ZFS filesystem version 5 ZFS storage pool version 28 log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented log_sysevent: type 19 is not implemented And here is gpart output: mfsbsd# gpart show => 34 80293181 ad0 GPT (38G) 34 128 1 freebsd-boot (64K) 162 2097152 2 freebsd-swap (1.0G) 2097314 76068013 3 freebsd-zfs (36G) 78165327 2127888 - free - (1.0G) => 34 78165293 ad1 GPT (37G) 34 128 1 freebsd-boot (64K) 162 2097152 2 freebsd-swap (1.0G) 2097314 76068013 3 freebsd-zfs (36G) => 34 80293181 ad2 GPT (38G) 34 128 1 freebsd-boot (64K) 162 2097152 2 freebsd-swap (1.0G) 2097314 76068013 3 freebsd-zfs (36G) 78165327 2127888 - free - (1.0G) Any idea what happened to the pool, why I am unable to boot and import it, and what can I do to investigate or fix this issue? -- Bartosz Stec From owner-freebsd-current@FreeBSD.ORG Thu Jun 2 22:15:42 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0A3321065672; Thu, 2 Jun 2011 22:15:42 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.59.238]) by mx1.freebsd.org (Postfix) with ESMTP id C8B778FC12; Thu, 2 Jun 2011 22:15:41 +0000 (UTC) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id E3C6F7300A; Fri, 3 Jun 2011 00:31:40 +0200 (CEST) Date: Fri, 3 Jun 2011 00:31:40 +0200 From: Luigi Rizzo To: net@freebsd.org Message-ID: <20110602223140.GA31285@onelab2.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Cc: current@freebsd.org Subject: Introducing netmap: line-rate packet send/receive at 10Gbit/s X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2011 22:15:42 -0000 Hi, we have recently worked on a project, called netmap, which lets FreeBSD send/receive packets at line rate even at 10 Gbit/s with very low CPU overhead: one core at 1.33 GHz does 14.88 Mpps with a modified ixgbe driver, which gives plenty of CPU cycles to handle multiple interface and/or do useful work (packet forwarding, analysis, etc.) You can find full documentation and source code and even a picobsd image at http://info.iet.unipi.it/~luigi/netmap/ The system uses memory mapped packet buffers to reduce the cost of data movements, but this would not be enough to make it useful or novel. Netmap uses many other small but important tricks to make the system fast, safe and easy to use, and support transmission, reception, and communication with the host stack. You can see full details in documentation at the above link. Feedback welcome. cheers luigi -----------------------------------------+------------------------------- Prof. Luigi RIZZO, rizzo@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL +39-050-2211611 . via Diotisalvi 2 Mobile +39-338-6809875 . 56122 PISA (Italy) -----------------------------------------+------------------------------- From owner-freebsd-current@FreeBSD.ORG Thu Jun 2 23:14:49 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0872C106564A for ; Thu, 2 Jun 2011 23:14:49 +0000 (UTC) (envelope-from lacombar@gmail.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id D272E8FC19 for ; Thu, 2 Jun 2011 23:14:48 +0000 (UTC) Received: by pzk27 with SMTP id 27so781101pzk.13 for ; Thu, 02 Jun 2011 16:14:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=fsqnDVEdMdeO2GP/cZZtTGU9jaS2CtUjC4WV9/7fMFA=; b=rRyucN+hGPPrDVCAAZj9mISO5/lRIMdUhLdwrbQQL4+YGULBFaI73I+/M/EK3GyAy4 KUsZrI3P8c1jmJaamEtrCvua/XnoNkX4fVfB3GM47vAr+BwjJyWHdtBETfQIKQxhAaE2 HP6JbmZo4FhVwZVzIdgr1t7oPIZmPwOoKXeXk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=sS/gCEXrq16XO0zizm/iljfqdYfq/ZYVrUsSa4qMr67W6iQaIsYKCvn33fh/PCqcAD DlTQWM3Plju0/B+Y9TE7cf4wyLNA8o4Kg1HOMaDl7FPat+ZsRVyqIl4YEZ3UVCdW/QvU Xdt1//c+iBzFgzAVfLmXEn/XcAVqARM0pDgMY= MIME-Version: 1.0 Received: by 10.68.31.137 with SMTP id a9mr534120pbi.202.1307056487528; Thu, 02 Jun 2011 16:14:47 -0700 (PDT) Received: by 10.68.52.164 with HTTP; Thu, 2 Jun 2011 16:14:47 -0700 (PDT) In-Reply-To: <20110601165429.GA16569@onelab2.iet.unipi.it> References: <20110601165429.GA16569@onelab2.iet.unipi.it> Date: Thu, 2 Jun 2011 19:14:47 -0400 Message-ID: From: Arnaud Lacombe To: Luigi Rizzo Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: current@freebsd.org Subject: Re: warning: 'inline' is not at beginning of declaration ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2011 23:14:49 -0000 Hi, On Wed, Jun 1, 2011 at 12:54 PM, Luigi Rizzo wrote: > In an attempt to build a kernel with -Wextra gives a number > of warnings for > > =A0 =A0 =A0 =A0'inline' is not at beginning of declaration > > (in tcp_input.c, as an example). > > Is there any interest in trying to fix these ? > > =A0 =A0 =A0 =A0HEAD/sys/netinet/tcp_input.c:218: warning: 'inline' is not= at beginning of declaration > =A0 =A0 =A0 =A0HEAD/sys/netinet/tcp_input.c:224: warning: 'inline' is not= at beginning of declaration > =A0 =A0 =A0 =A0HEAD/sys/netinet/tcp_input.c:226: warning: 'inline' is not= at beginning of declaration > =A0 =A0 =A0 =A0HEAD/sys/netinet/tcp_input.c:227: warning: 'inline' is not= at beginning of declaration > =A0 =A0 =A0 =A0HEAD/sys/netinet/tcp_input.c:228: warning: 'inline' is not= at beginning of declaration > =A0 =A0 =A0 =A0HEAD/sys/netinet/tcp_input.c:248: warning: 'inline' is not= at beginning of declaration > =A0 =A0 =A0 =A0HEAD/sys/netinet/tcp_input.c:266: warning: 'inline' is not= at beginning of declaration > =A0 =A0 =A0 =A0HEAD/sys/netinet/tcp_input.c:298: warning: 'inline' is not= at beginning of declaration > =A0 =A0 =A0 =A0HEAD/sys/netinet/tcp_input.c:388: warning: 'inline' is not= at beginning of declaration > =A0 =A0 =A0 =A0HEAD/sys/netinet/tcp_input.c:440: warning: 'inline' is not= at beginning of declaration > > On a related topic, do we have any mechanism to provide > per-subdir or per-file CFLAGS during kernel builds ? > I'd say no as the kernel per-se makes no use of , ooth, some modules do. > I tried to put a Makefile.inc in a subdirectory but it > did not help. > understandable, as Makefile.inc is sourced by , which is only used by `sys/conf/kmod.mk'. - Arnaud > cheers > luigi > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " > From owner-freebsd-current@FreeBSD.ORG Fri Jun 3 00:05:07 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E39391065673 for ; Fri, 3 Jun 2011 00:05:07 +0000 (UTC) (envelope-from jdneal@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 735938FC0C for ; Fri, 3 Jun 2011 00:05:07 +0000 (UTC) Received: by fxm11 with SMTP id 11so1487779fxm.13 for ; Thu, 02 Jun 2011 17:05:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=FNfP/ore/2MPrcFDl+ayzo/QFDdD4POCHd8KkfB3rr0=; b=fsRBoO7FDav67jumoBPUxfgqdvpLJGAc334wvRKi65SH+/oAbLbSJCAib6tDIpjuqT EI8MD452MmYjjT1zvwe1e1FfssrTAZs/X3jH6TZY+j/pu1LdYgA+9MTlwqy/AlEH0c8N la/MxSh8iZinctG9tzfXMBrLIBiwqJQuZkjQI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=Fs61SLJn9+virevm9DbUhzE13+7U8EETAT6InmVVnI+8c/jYOI9laTLSXjzE88cWlP uu7PW1fQLTOhEV92qp6TjdrG7MSB7cMeB4H1XbvtocXiuDVFGbSY6ZIXO/w03zgLtwM0 ir1lOfsV5nuHKI2s25zMv3wOU/fk6S/qXvWDY= MIME-Version: 1.0 Received: by 10.223.55.201 with SMTP id v9mr677531fag.76.1307058005778; Thu, 02 Jun 2011 16:40:05 -0700 (PDT) Received: by 10.223.120.17 with HTTP; Thu, 2 Jun 2011 16:40:05 -0700 (PDT) In-Reply-To: <20110601165429.GA16569@onelab2.iet.unipi.it> References: <20110601165429.GA16569@onelab2.iet.unipi.it> Date: Thu, 2 Jun 2011 16:40:05 -0700 Message-ID: From: Joshua Neal To: Luigi Rizzo Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: current@freebsd.org Subject: Re: warning: 'inline' is not at beginning of declaration ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2011 00:05:08 -0000 A compile-with clause in the sys/conf/files configuration file may work for what you want, e.g. picking a random example: dev/e1000/e1000_82542.c optional em | igb \ compile-with "${NORMAL_C} -I$S/dev/e1000" - Joshua On Wed, Jun 1, 2011 at 9:54 AM, Luigi Rizzo wrote: > In an attempt to build a kernel with -Wextra gives a number > of warnings for > > =A0 =A0 =A0 =A0'inline' is not at beginning of declaration > > (in tcp_input.c, as an example). > > Is there any interest in trying to fix these ? > > =A0 =A0 =A0 =A0HEAD/sys/netinet/tcp_input.c:218: warning: 'inline' is not= at beginning of declaration > =A0 =A0 =A0 =A0HEAD/sys/netinet/tcp_input.c:224: warning: 'inline' is not= at beginning of declaration > =A0 =A0 =A0 =A0HEAD/sys/netinet/tcp_input.c:226: warning: 'inline' is not= at beginning of declaration > =A0 =A0 =A0 =A0HEAD/sys/netinet/tcp_input.c:227: warning: 'inline' is not= at beginning of declaration > =A0 =A0 =A0 =A0HEAD/sys/netinet/tcp_input.c:228: warning: 'inline' is not= at beginning of declaration > =A0 =A0 =A0 =A0HEAD/sys/netinet/tcp_input.c:248: warning: 'inline' is not= at beginning of declaration > =A0 =A0 =A0 =A0HEAD/sys/netinet/tcp_input.c:266: warning: 'inline' is not= at beginning of declaration > =A0 =A0 =A0 =A0HEAD/sys/netinet/tcp_input.c:298: warning: 'inline' is not= at beginning of declaration > =A0 =A0 =A0 =A0HEAD/sys/netinet/tcp_input.c:388: warning: 'inline' is not= at beginning of declaration > =A0 =A0 =A0 =A0HEAD/sys/netinet/tcp_input.c:440: warning: 'inline' is not= at beginning of declaration > > On a related topic, do we have any mechanism to provide > per-subdir or per-file CFLAGS during kernel builds ? > I tried to put a Makefile.inc in a subdirectory but it > did not help. > > cheers > luigi > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " > From owner-freebsd-current@FreeBSD.ORG Fri Jun 3 00:06:56 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A91C1106564A for ; Fri, 3 Jun 2011 00:06:56 +0000 (UTC) (envelope-from ptyll@nitronet.pl) Received: from mail.nitronet.pl (smtp.nitronet.pl [195.90.106.27]) by mx1.freebsd.org (Postfix) with ESMTP id 61F388FC17 for ; Fri, 3 Jun 2011 00:06:56 +0000 (UTC) Received: from mailnull by mail.nitronet.pl with virscan (Exim 4.76 (FreeBSD)) (envelope-from ) id 1QSHWj-000DeL-TB for current@freebsd.org; Fri, 03 Jun 2011 01:42:09 +0200 Date: Fri, 3 Jun 2011 01:41:22 +0200 From: Pawel Tyll X-Priority: 3 (Normal) Message-ID: <174644677.20110603014122@nitronet.pl> To: Luigi Rizzo In-Reply-To: <20110602223140.GA31285@onelab2.iet.unipi.it> References: <20110602223140.GA31285@onelab2.iet.unipi.it> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: Nitronet.pl X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: ptyll@nitronet.pl X-SA-Exim-Scanned: No (on mail.nitronet.pl); SAEximRunCond expanded to false Cc: current@freebsd.org, net@freebsd.org Subject: Re: Introducing netmap: line-rate packet send/receive at 10Gbit/s X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2011 00:06:56 -0000 Hi Luigi, > we have recently worked on a project, called netmap, which lets > FreeBSD send/receive packets at line rate even at 10 Gbit/s with > very low CPU overhead: one core at 1.33 GHz does 14.88 Mpps with a > modified ixgbe driver, which gives plenty of CPU cycles to handle > multiple interface and/or do useful work (packet forwarding, analysis, etc.) Great to hear. Now all we need is a proper MPLS stack, and plans of moving on from FreeBSD are postponed for like, ever ;) Thanks for your ongoing work! From owner-freebsd-current@FreeBSD.ORG Fri Jun 3 05:33:49 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D979D106574C for ; Fri, 3 Jun 2011 05:33:49 +0000 (UTC) (envelope-from himali.patel@sibridgetech.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 97FAC8FC0A for ; Fri, 3 Jun 2011 05:33:49 +0000 (UTC) Received: by vws18 with SMTP id 18so1616705vws.13 for ; Thu, 02 Jun 2011 22:33:48 -0700 (PDT) Received: by 10.52.109.101 with SMTP id hr5mr2038589vdb.251.1307077523072; Thu, 02 Jun 2011 22:05:23 -0700 (PDT) Received: from HimaliPatel ([110.172.28.16]) by mx.google.com with ESMTPS id cr7sm472550vbb.14.2011.06.02.22.05.20 (version=SSLv3 cipher=OTHER); Thu, 02 Jun 2011 22:05:22 -0700 (PDT) From: "Himali Patel" To: Date: Fri, 3 Jun 2011 10:35:15 +0530 Message-ID: <7B777582034949C6A217E0852661FC1E@HimaliPatel> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 11 Thread-Index: Acwhq9Ny5q2a+rBoTcetHt9Bx6Cvuw== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: 802.11n support for athero's chipset X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2011 05:33:49 -0000 Hi, Current branch of FreeBSD 9.0 doesn't have full support of 802.11n functionality. Any clue on by when the 802.11n support in FreeBSD will be available for Athero's chipset? Thanks, Himali From owner-freebsd-current@FreeBSD.ORG Fri Jun 3 06:56:35 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B4F5C106566C for ; Fri, 3 Jun 2011 06:56:35 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id 7137F8FC0C for ; Fri, 3 Jun 2011 06:56:35 +0000 (UTC) Received: by gyg13 with SMTP id 13so1012618gyg.13 for ; Thu, 02 Jun 2011 23:56:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=H2dAOvm5qAFKUYTIOwy42uu+EvyDeI0u0YDvh7v1vrQ=; b=PdD4BiiOduxhR6EpkoA0t8XEqRvrAdKMdXOYuHvjx5ZTA24KDbS0rE7Q+4UbySxc4q yD4I4r9DdtqkUdQSY1iGYc8fBysrLICEYuD55Wvsl4Izr/+V9Z1CGAcn9Qs4wUOL4ez/ IBg0+RAy1T9YpHtcMIG8OP7FsFXj45IVMmr9w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=xBZws+T9/a2ZDB0rkjuGruqUjbm90i16JUBnI0feTIBUISgZVAGz0A4l/a+RrxD/HM eWVJw04mPHbkWk10NC1i3I6h407jqKrsdckzCN5HMXk/1tMRNFR5ETaBFcc63JiNil4L bvdMxn0FE0nMmd+JBkbUycmQ5TTmAk5UZPWrM= MIME-Version: 1.0 Received: by 10.151.58.8 with SMTP id l8mr1667879ybk.242.1307084194642; Thu, 02 Jun 2011 23:56:34 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.151.107.15 with HTTP; Thu, 2 Jun 2011 23:56:34 -0700 (PDT) In-Reply-To: <7B777582034949C6A217E0852661FC1E@HimaliPatel> References: <7B777582034949C6A217E0852661FC1E@HimaliPatel> Date: Fri, 3 Jun 2011 14:56:34 +0800 X-Google-Sender-Auth: 0twFDJ_yxAtuC5wIddLDuVSEdfU Message-ID: From: Adrian Chadd To: Himali Patel Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current@freebsd.org Subject: Re: 802.11n support for athero's chipset X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2011 06:56:35 -0000 On 3 June 2011 13:05, Himali Patel wrote: > Current branch of FreeBSD 9.0 doesn't have full support of 802.11n > functionality. Any clue on by when the 802.11n support in FreeBSD will be > available for Athero's chipset? Hi, The main thing that's left is TX aggregation. Everything else (especially surrounding powersave) isn't on my personal radar at the moment. The only answer I can give you for TX aggregation is "when someone's coded it." :-) I'm going to sit down now and try to fix the TX path a bit. A bunch of stuff is needed before TX aggregation is possible (mostly surrounding implementing per-TID software TX queues, handling hardware-filtered packets and software TX retries.) I've created a new branch in FreeBSD SVN for the initial tidying up I'm doing. If you'd like to help out then please contact me privately and we can discuss how to break down the work. :) Thanks, Adrian From owner-freebsd-current@FreeBSD.ORG Fri Jun 3 07:58:42 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 41ABA106564A; Fri, 3 Jun 2011 07:58:42 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id EB6A18FC13; Fri, 3 Jun 2011 07:58:41 +0000 (UTC) Received: by qwc9 with SMTP id 9so979816qwc.13 for ; Fri, 03 Jun 2011 00:58:41 -0700 (PDT) Received: by 10.224.112.195 with SMTP id x3mr864042qap.114.1307086514286; Fri, 03 Jun 2011 00:35:14 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.31.73 with HTTP; Fri, 3 Jun 2011 00:34:34 -0700 (PDT) In-Reply-To: <20110602223140.GA31285@onelab2.iet.unipi.it> References: <20110602223140.GA31285@onelab2.iet.unipi.it> From: Vlad Galu Date: Fri, 3 Jun 2011 09:34:34 +0200 Message-ID: To: Luigi Rizzo Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: current@freebsd.org, net@freebsd.org Subject: Re: Introducing netmap: line-rate packet send/receive at 10Gbit/s X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2011 07:58:42 -0000 On Fri, Jun 3, 2011 at 12:31 AM, Luigi Rizzo wrote: > Hi, > we have recently worked on a project, called netmap, which lets > FreeBSD send/receive packets at line rate even at 10 Gbit/s with > very low CPU overhead: one core at 1.33 GHz does 14.88 Mpps with a > modified ixgbe driver, which gives plenty of CPU cycles to handle > multiple interface and/or do useful work (packet forwarding, analysis, > etc.) > > You can find full documentation and source code and even a picobsd image at > > http://info.iet.unipi.it/~luigi/netmap/ > > The system uses memory mapped packet buffers to reduce the cost of > data movements, but this would not be enough to make it useful or > novel. Netmap uses many other small but important tricks to make > the system fast, safe and easy to use, and support transmission, > reception, and communication with the host stack. > > You can see full details in documentation at the above link. > > Feedback welcome. > > cheers > luigi > -----------------------------------------+------------------------------- > Prof. Luigi RIZZO, rizzo@iet.unipi.it . Dip. di Ing. dell'Informazione > http://www.iet.unipi.it/~luigi/ . Universita` di Pisa > TEL +39-050-2211611 . via Diotisalvi 2 > Mobile +39-338-6809875 . 56122 PISA (Italy) > -----------------------------------------+------------------------------- > This is great news, Luigi! Thank you for your work! -- Good, fast & cheap. Pick any two. From owner-freebsd-current@FreeBSD.ORG Fri Jun 3 08:26:23 2011 Return-Path: Delivered-To: current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 041DE106566C; Fri, 3 Jun 2011 08:26:23 +0000 (UTC) (envelope-from sobomax@sippysoft.com) Received: from mail.sippysoft.com (mail.sippysoft.com [4.59.13.245]) by mx1.freebsd.org (Postfix) with ESMTP id 4174B8FC12; Fri, 3 Jun 2011 08:26:22 +0000 (UTC) Received: from s0106005004e13421.vs.shawcable.net ([70.71.175.212] helo=[192.168.1.79]) by mail.sippysoft.com with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from ) id 1QSPi1-0007qz-CF; Fri, 03 Jun 2011 01:26:21 -0700 Message-ID: <4DE89AA3.908@FreeBSD.org> Date: Fri, 03 Jun 2011 01:26:11 -0700 From: Maxim Sobolev Organization: Sippy Software, Inc. User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: Mikolaj Golub References: <4DDD4890.70604@FreeBSD.org> <86hb8du5fo.fsf@kopusha.home.net> In-Reply-To: <86hb8du5fo.fsf@kopusha.home.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: sobomax@sippysoft.com X-ssp-trusted: yes Cc: Pawel Jakub Dawidek , "current@freebsd.org" Subject: Re: Weird issue with hastd(8) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2011 08:26:23 -0000 On 5/29/2011 4:11 AM, Mikolaj Golub wrote: > This might be MSG_WAITALL issue I described on net@ (look for the thread > "recv() with MSG_WAITALL might stuck when receiving more than rcvbuf", and > also kern/154504). > > Could you please try the patch? > > http://people.freebsd.org/~trociny/uipc_socket.c.patch Yes, installing this patch on both client and server has solved this issue. Synchronization now goes much faster. I would also like to get your input on my two other patches - randomization of the synchronization pattern and ad-hoc asynchronous more. Hastd appears extremely useful to synchronize large virtual disks over slow links without taking live virtual machine offline. -Maxim From owner-freebsd-current@FreeBSD.ORG Fri Jun 3 07:26:53 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 84935106564A; Fri, 3 Jun 2011 07:26:53 +0000 (UTC) (envelope-from nwf@cs.jhu.edu) Received: from blaze.cs.jhu.edu (blaze.cs.jhu.edu [128.220.13.50]) by mx1.freebsd.org (Postfix) with ESMTP id 5976A8FC08; Fri, 3 Jun 2011 07:26:53 +0000 (UTC) Received: from gradx.cs.jhu.edu (gradx.cs.jhu.edu [128.220.13.52]) by blaze.cs.jhu.edu (8.14.3/8.14.3) with ESMTP id p5373ucI020158 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 3 Jun 2011 03:03:56 -0400 (EDT) Received: from gradx.cs.jhu.edu (localhost [127.0.0.1]) by gradx.cs.jhu.edu (8.14.3/8.13.1) with ESMTP id p5373u38026976; Fri, 3 Jun 2011 03:03:56 -0400 Received: (from nwf@localhost) by gradx.cs.jhu.edu (8.14.3/8.13.8/Submit) id p5373uU0026975; Fri, 3 Jun 2011 03:03:56 -0400 Date: Fri, 3 Jun 2011 03:03:56 -0400 From: Nathaniel W Filardo To: freebsd-current@freebsd.org, freebsd-sparc64@freebsd.org Message-ID: <20110603070356.GJ7129@gradx.cs.jhu.edu> References: <20110406080043.GQ609@gradx.cs.jhu.edu> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Ev+J9+115SO9Z5Eo" Content-Disposition: inline In-Reply-To: <20110406080043.GQ609@gradx.cs.jhu.edu> User-Agent: Mutt/1.5.20 (2009-08-17) X-Mailman-Approved-At: Fri, 03 Jun 2011 11:29:34 +0000 Cc: Subject: Re: ZFS panic with concurrent recv and read-heavy workload X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2011 07:26:53 -0000 --Ev+J9+115SO9Z5Eo Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I just got this on another machine, no heavy workload needed, just booting and starting some jails. Of interest, perhaps, both this and the machine triggering the below panic are SMP V240s with 1.5GHz CPUs (though I will confess that the machine in the original report may have had bad RAM). I have run a UP 1.2GHz V240 for months and never seen this panic. This time the kernel is > FreeBSD 9.0-CURRENT #9: Fri Jun 3 02:32:13 EDT 2011 csup'd immediately before building. The full panic this time is > panic: Lock buf_hash_table.ht_locks[i].ht_lock not exclusively locked @ > /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/arc.c:4659 > > cpuid = 1 > KDB: stack backtrace: > panic() at panic+0x1c8 > _sx_assert() at _sx_assert+0xc4 > _sx_xunlock() at _sx_xunlock+0x98 > l2arc_feed_thread() at l2arc_feed_thread+0xeac > fork_exit() at fork_exit+0x9c > fork_trampoline() at fork_trampoline+0x8 > > SC Alert: SC Request to send Break to host. > KDB: enter: Line break on console > [ thread pid 27 tid 100121 ] > Stopped at kdb_enter+0x80: ta %xcc, 1 > db> reset > ttiimmeeoouutt sshhuuttttiinngg ddoowwnn CCPPUUss.. Half of the memory in this machine is new (well, came with the machine) and half is from the aforementioned UP V240 which seemed to work fine (I was attempting an upgrade when this happened); none of it (or indeed any of the hardware save the disk controller and disks) are common between this and the machine reporting below. Thoughts? Any help would be greatly appreciated. Thanks. --nwf; On Wed, Apr 06, 2011 at 04:00:43AM -0400, Nathaniel W Filardo wrote: >[...] > panic: Lock buf_hash_table.ht_locks[i].ht_lock not exclusively locked @ /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/arc.c:1869 > > cpuid = 1 > KDB: stack backtrace: > panic() at panic+0x1c8 > _sx_assert() at _sx_assert+0xc4 > _sx_xunlock() at _sx_xunlock+0x98 > arc_evict() at arc_evict+0x614 > arc_get_data_buf() at arc_get_data_buf+0x360 > arc_buf_alloc() at arc_buf_alloc+0x94 > dmu_buf_will_fill() at dmu_buf_will_fill+0xfc > dmu_write() at dmu_write+0xec > dmu_recv_stream() at dmu_recv_stream+0x8a8 > zfs_ioc_recv() at zfs_ioc_recv+0x354 > zfsdev_ioctl() at zfsdev_ioctl+0xe0 > devfs_ioctl_f() at devfs_ioctl_f+0xe8 > kern_ioctl() at kern_ioctl+0x294 > ioctl() at ioctl+0x198 > syscallenter() at syscallenter+0x270 > syscall() at syscall+0x74 > -- syscall (54, FreeBSD ELF64, ioctl) %o7=0x40c13e24 -- > userland() at 0x40e72cc8 > user trace: trap %o7=0x40c13e24 > pc 0x40e72cc8, sp 0x7fdffff4641 > pc 0x40c158f4, sp 0x7fdffff4721 > pc 0x40c1e878, sp 0x7fdffff47f1 > pc 0x40c1ce54, sp 0x7fdffff8b01 > pc 0x40c1dbe0, sp 0x7fdffff9431 > pc 0x40c1f718, sp 0x7fdffffd741 > pc 0x10731c, sp 0x7fdffffd831 > pc 0x10c90c, sp 0x7fdffffd8f1 > pc 0x103ef0, sp 0x7fdffffe1d1 > pc 0x4021aff4, sp 0x7fdffffe291 > done >[...] --Ev+J9+115SO9Z5Eo Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk3oh1wACgkQTeQabvr9Tc+FLACcCBa0wdug6xIFknSxPi9f4IaN SbMAn1jJ9GqKWVs0lSJDMQXvCyxjc9nQ =JDAt -----END PGP SIGNATURE----- --Ev+J9+115SO9Z5Eo-- From owner-freebsd-current@FreeBSD.ORG Fri Jun 3 13:42:28 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 79B28106566B for ; Fri, 3 Jun 2011 13:42:28 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.59.238]) by mx1.freebsd.org (Postfix) with ESMTP id 40A9F8FC13 for ; Fri, 3 Jun 2011 13:42:27 +0000 (UTC) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id D0C787300B; Fri, 3 Jun 2011 15:58:28 +0200 (CEST) Date: Fri, 3 Jun 2011 15:58:28 +0200 From: Luigi Rizzo To: Patrick Tracanelli Message-ID: <20110603135828.GA42615@onelab2.iet.unipi.it> References: <20110602223140.GA31285@onelab2.iet.unipi.it> <85C4C9B4-9413-4695-B625-BDAA00B97662@freebsdbrasil.com.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <85C4C9B4-9413-4695-B625-BDAA00B97662@freebsdbrasil.com.br> User-Agent: Mutt/1.4.2.3i Cc: current@freebsd.org Subject: Re: Introducing netmap: line-rate packet send/receive at 10Gbit/s X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2011 13:42:28 -0000 On Fri, Jun 03, 2011 at 10:20:50AM -0300, Patrick Tracanelli wrote: > > Em 02/06/2011, ?s 19:31, Luigi Rizzo escreveu: > > > Hi, > > we have recently worked on a project, called netmap, which lets > > FreeBSD send/receive packets at line rate even at 10 Gbit/s with > > very low CPU overhead: one core at 1.33 GHz does 14.88 Mpps with a > > modified ixgbe driver, which gives plenty of CPU cycles to handle > > multiple interface and/or do useful work (packet forwarding, analysis, etc.) > > > > You can find full documentation and source code and even a picobsd image at > > > > http://info.iet.unipi.it/~luigi/netmap/ > > > > The system uses memory mapped packet buffers to reduce the cost of > > data movements, but this would not be enough to make it useful or > > novel. Netmap uses many other small but important tricks to make > > the system fast, safe and easy to use, and support transmission, > > reception, and communication with the host stack. > > > > You can see full details in documentation at the above link. > > > > Feedback welcome. > > Dear Rizzo, > > Which packet len you transmitted at 14.8MPPS? According to figure 5 or the description I could not find it. Did you test TCP? The paper gives all details in sec.6, please read it carefully. The test is done with individual streams (either tx or rx) of packets, the protocol is irrelevant. In fig.5 of the paper, packet size is on the X axis, pps is on the Y axis. You get the maximum PPS rate with min-sized packets (60 bytes + 4 byte crc). If you want to do both send and receive and perhaps on multiple interfaces you should make sure there are enough resources (CPU cycles, bus bandwidth and transactions etc.) for the task. In my tests, CPU does not seem to be a problem (i can send about 27Mpps with just one core and two interfaces), but bus cycles perhaps are (e.g. receiving with some of the "bad" packet sizes also slows down the sender on the same bus, no matter how many cores i put in). cheers luigi > How did you perform this test? Multihomed with forwarding between NICs or you generated the data from userland to the wire and let it flow? If not tell me how you believe netmap may impact in our current forwarding rate (specially the pps limit) and FreeBSD should be changed to take advantage of netmap for pkt forwarding. > > Thank you for your time, code and all the stuff in between :) > > -- > Patrick Tracanelli > From owner-freebsd-current@FreeBSD.ORG Fri Jun 3 13:52:13 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6A833106566C for ; Fri, 3 Jun 2011 13:52:13 +0000 (UTC) (envelope-from eksffa@freebsdbrasil.com.br) Received: from capeta.freebsdbrasil.com.br (eudaemonian2.freebsdbrasil.com.br [201.48.151.8]) by mx1.freebsd.org (Postfix) with SMTP id A409A8FC08 for ; Fri, 3 Jun 2011 13:52:12 +0000 (UTC) Received: (qmail 88997 invoked from network); 3 Jun 2011 10:25:30 -0300 Received: by simscan 1.4.0 ppid: 88955, pid: 88994, t: 1.2168s scanners:none Received: from unknown (HELO ?172.20.10.8?) (eksffa@freebsdbrasil.com.br@187.1.226.98) by capeta.freebsdbrasil.com.br with ESMTPA; 3 Jun 2011 10:25:29 -0300 Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=iso-8859-1 From: Patrick Tracanelli In-Reply-To: <20110602223140.GA31285@onelab2.iet.unipi.it> Date: Fri, 3 Jun 2011 10:20:50 -0300 Content-Transfer-Encoding: quoted-printable Message-Id: <85C4C9B4-9413-4695-B625-BDAA00B97662@freebsdbrasil.com.br> References: <20110602223140.GA31285@onelab2.iet.unipi.it> To: Luigi Rizzo X-Mailer: Apple Mail (2.1084) Cc: current@freebsd.org Subject: Re: Introducing netmap: line-rate packet send/receive at 10Gbit/s X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2011 13:52:13 -0000 Em 02/06/2011, =E0s 19:31, Luigi Rizzo escreveu: > Hi, > we have recently worked on a project, called netmap, which lets > FreeBSD send/receive packets at line rate even at 10 Gbit/s with > very low CPU overhead: one core at 1.33 GHz does 14.88 Mpps with a > modified ixgbe driver, which gives plenty of CPU cycles to handle > multiple interface and/or do useful work (packet forwarding, analysis, = etc.) >=20 > You can find full documentation and source code and even a picobsd = image at >=20 > http://info.iet.unipi.it/~luigi/netmap/ >=20 > The system uses memory mapped packet buffers to reduce the cost of > data movements, but this would not be enough to make it useful or > novel. Netmap uses many other small but important tricks to make > the system fast, safe and easy to use, and support transmission, > reception, and communication with the host stack. >=20 > You can see full details in documentation at the above link. >=20 > Feedback welcome. Dear Rizzo, Which packet len you transmitted at 14.8MPPS? According to figure 5 or = the description I could not find it. Did you test TCP? How did you perform this test? Multihomed with forwarding between NICs = or you generated the data from userland to the wire and let it flow? If = not tell me how you believe netmap may impact in our current forwarding = rate (specially the pps limit) and FreeBSD should be changed to take = advantage of netmap for pkt forwarding. Thank you for your time, code and all the stuff in between :) -- Patrick Tracanelli From owner-freebsd-current@FreeBSD.ORG Fri Jun 3 14:46:59 2011 Return-Path: Delivered-To: current@FreeBSD.org Received: from lo0.su (repoman.freebsd.org [IPv6:2001:4f8:fff6::29]) by hub.freebsd.org (Postfix) with ESMTP id 915AE1065676 for ; Fri, 3 Jun 2011 14:46:58 +0000 (UTC) (envelope-from ru@FreeBSD.org) Date: Fri, 3 Jun 2011 14:48:59 +0000 From: Ruslan Ermilov To: current@FreeBSD.org Message-ID: <20110603144859.GA73084@lo0.su> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Cc: Subject: [HEADS UP] color and page width support in man(1) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2011 14:46:59 -0000 Hi there, On a freshly installed -CURRENT, to view a colorized manpage in color and in full terminal width, try this: env MANCOLOR=yes MANWIDTH=tty man grotty Both features are disabled by default for POLA reasons. Bikeshedding will be redirected to /dev/null. Cheers, -- Ruslan Ermilov ru@FreeBSD.org FreeBSD committer From owner-freebsd-current@FreeBSD.ORG Fri Jun 3 15:13:53 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 51A9E1065672; Fri, 3 Jun 2011 15:13:53 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 760A18FC13; Fri, 3 Jun 2011 15:13:51 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id SAA15788; Fri, 03 Jun 2011 18:13:50 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <4DE8FA2E.4030202@FreeBSD.org> Date: Fri, 03 Jun 2011 18:13:50 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.17) Gecko/20110504 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: freebsd-current@FreeBSD.org, freebsd-stable@FreeBSD.org X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Subject: [poll / rfc] kdb_stop_cpus X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2011 15:13:53 -0000 I wonder if anybody uses kdb_stop_cpus with non-default value. If, yes, I am very interested to learn about your usecase for it. I think that the default kdb behavior is the correct one, so it doesn't make sense to have a knob to turn on incorrect behavior. But I may be missing something obvious. The comment in the code doesn't really satisfy me: /* * Flag indicating whether or not to IPI the other CPUs to stop them on * entering the debugger. Sometimes, this will result in a deadlock as * stop_cpus() waits for the other cpus to stop, so we allow it to be * disabled. In order to maximize the chances of success, use a hard * stop for that. */ The hard stop should be sufficiently mighty. Yes, I am aware of supposedly extremely rare situations where a deadlock could happen even when using hard stop. But I'd rather fix that than have this switch. Oh, the commit message (from 2004) explains it: > Add a new sysctl, debug.kdb.stop_cpus, which controls whether or not we > attempt to IPI other cpus when entering the debugger in order to stop > them while in the debugger. The default remains to issue the stop; > however, that can result in a hang if another cpu has interrupts disabled > and is spinning, since the IPI won't be received and the KDB will wait > indefinitely. We probably need to add a timeout, but this is a useful > stopgap in the mean time. But that was before we started using hard stop in this context (in 2009). -- Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Fri Jun 3 15:54:22 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CE51D1065672; Fri, 3 Jun 2011 15:54:22 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from mail.icecube.wisc.edu (trout.icecube.wisc.edu [128.104.255.119]) by mx1.freebsd.org (Postfix) with ESMTP id 91D6F8FC12; Fri, 3 Jun 2011 15:54:22 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.icecube.wisc.edu (Postfix) with ESMTP id D3C7D58142; Fri, 3 Jun 2011 10:28:03 -0500 (CDT) X-Virus-Scanned: amavisd-new at icecube.wisc.edu Received: from mail.icecube.wisc.edu ([127.0.0.1]) by localhost (trout.icecube.wisc.edu [127.0.0.1]) (amavisd-new, port 10030) with ESMTP id csROGH26NRuy; Fri, 3 Jun 2011 10:28:03 -0500 (CDT) Received: from wanderer.tachypleus.net (i3-dhcp-172-16-223-128.icecube.wisc.edu [172.16.223.128]) by mail.icecube.wisc.edu (Postfix) with ESMTP id 9B78F5813A; Fri, 3 Jun 2011 10:28:03 -0500 (CDT) Message-ID: <4DE8FD83.6030503@freebsd.org> Date: Fri, 03 Jun 2011 10:28:03 -0500 From: Nathan Whitehorn User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.17) Gecko/20110516 Thunderbird/3.1.10 MIME-Version: 1.0 To: Andriy Gapon References: <4DE8FA2E.4030202@FreeBSD.org> In-Reply-To: <4DE8FA2E.4030202@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: Re: [poll / rfc] kdb_stop_cpus X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2011 15:54:22 -0000 On 06/03/11 10:13, Andriy Gapon wrote: > > I wonder if anybody uses kdb_stop_cpus with non-default value. > If, yes, I am very interested to learn about your usecase for it. > > I think that the default kdb behavior is the correct one, so it doesn't make sense > to have a knob to turn on incorrect behavior. > But I may be missing something obvious. > > The comment in the code doesn't really satisfy me: > /* > * Flag indicating whether or not to IPI the other CPUs to stop them on > * entering the debugger. Sometimes, this will result in a deadlock as > * stop_cpus() waits for the other cpus to stop, so we allow it to be > * disabled. In order to maximize the chances of success, use a hard > * stop for that. > */ > > The hard stop should be sufficiently mighty. > Yes, I am aware of supposedly extremely rare situations where a deadlock could > happen even when using hard stop. But I'd rather fix that than have this switch. > > Oh, the commit message (from 2004) explains it: >> Add a new sysctl, debug.kdb.stop_cpus, which controls whether or not we >> attempt to IPI other cpus when entering the debugger in order to stop >> them while in the debugger. The default remains to issue the stop; >> however, that can result in a hang if another cpu has interrupts disabled >> and is spinning, since the IPI won't be received and the KDB will wait >> indefinitely. We probably need to add a timeout, but this is a useful >> stopgap in the mean time. > > But that was before we started using hard stop in this context (in 2009). Some non-x86 platforms (e.g. PPC) don't support real NMIs, and so this still applies. -Nathan From owner-freebsd-current@FreeBSD.ORG Fri Jun 3 16:03:47 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 47B2E106566B; Fri, 3 Jun 2011 16:03:47 +0000 (UTC) (envelope-from daniel@digsys.bg) Received: from smtp-sofia.digsys.bg (smtp-sofia.digsys.bg [193.68.3.230]) by mx1.freebsd.org (Postfix) with ESMTP id C7B828FC12; Fri, 3 Jun 2011 16:03:46 +0000 (UTC) Received: from dcave.digsys.bg (dcave.digsys.bg [192.92.129.5]) (authenticated bits=0) by smtp-sofia.digsys.bg (8.14.4/8.14.4) with ESMTP id p53FXggN079120 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 3 Jun 2011 18:33:47 +0300 (EEST) (envelope-from daniel@digsys.bg) Message-ID: <4DE8FED5.6020308@digsys.bg> Date: Fri, 03 Jun 2011 18:33:41 +0300 From: Daniel Kalchev User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.17) Gecko/20110519 Thunderbird/3.1.10 MIME-Version: 1.0 To: Maxim Sobolev References: <4DDD4890.70604@FreeBSD.org> <86hb8du5fo.fsf@kopusha.home.net> <4DE89AA3.908@FreeBSD.org> In-Reply-To: <4DE89AA3.908@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Mikolaj Golub , Pawel Jakub Dawidek , "current@freebsd.org" Subject: Re: Weird issue with hastd(8) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2011 16:03:47 -0000 On 03.06.11 11:26, Maxim Sobolev wrote: > On 5/29/2011 4:11 AM, Mikolaj Golub wrote: >> This might be MSG_WAITALL issue I described on net@ (look for the thread >> "recv() with MSG_WAITALL might stuck when receiving more than >> rcvbuf", and >> also kern/154504). >> >> Could you please try the patch? >> >> http://people.freebsd.org/~trociny/uipc_socket.c.patch > > Yes, installing this patch on both client and server has solved this > issue. Synchronization now goes much faster. > This patch also apparently resolved the issue I had with HAST over 10Gbit Ethernet. It should probably be committed. Daniel From owner-freebsd-current@FreeBSD.ORG Fri Jun 3 16:06:21 2011 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F07C3106566C for ; Fri, 3 Jun 2011 16:06:21 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from gse-mta-27.emailfiltering.com (gse-mta-27-tx.emailfiltering.com [194.116.198.158]) by mx1.freebsd.org (Postfix) with ESMTP id 58A298FC14 for ; Fri, 3 Jun 2011 16:06:20 +0000 (UTC) Received: from mail-gw5.york.ac.uk ([144.32.129.29]) by gse-mta-27.emailfiltering.com with emfmta (version 4.8.1.33) by TLS id 1023873628 for mike@reifenberger.com; f1d6e82043ed96c9; Fri, 03 Jun 2011 16:55:14 +0100 Received: from buffy-128.york.ac.uk ([144.32.128.160]:14402 helo=buffy.york.ac.uk) by mail-gw5.york.ac.uk with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1QSWiP-0007sH-CA; Fri, 03 Jun 2011 16:55:13 +0100 Received: from buffy.york.ac.uk (localhost [127.0.0.1]) by buffy.york.ac.uk (8.14.4/8.14.4) with ESMTP id p53FtCCC071352; Fri, 3 Jun 2011 16:55:12 +0100 (BST) (envelope-from gavin@FreeBSD.org) Received: (from ga9@localhost) by buffy.york.ac.uk (8.14.4/8.14.4/Submit) id p53FtC4s071351; Fri, 3 Jun 2011 16:55:12 +0100 (BST) (envelope-from gavin@FreeBSD.org) X-Authentication-Warning: buffy.york.ac.uk: ga9 set sender to gavin@FreeBSD.org using -f From: Gavin Atkinson To: Michael Reifenberger In-Reply-To: References: Content-Type: text/plain; charset="ASCII" Content-Transfer-Encoding: quoted-printable Date: Fri, 03 Jun 2011 16:55:12 +0100 Message-ID: <1307116512.60345.8.camel@buffy.york.ac.uk> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Cc: Garrett Cooper , pjd@FreeBSD.org, FreeBSD-Current Subject: Re: mount root from zfs fails under current with "error 6" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2011 16:06:22 -0000 On Tue, 2011-05-31 at 19:38 +0200, Michael Reifenberger wrote: > Hi, >=20 > On Tue, 31 May 2011, Michael Reifenberger wrote: > ... > > (fs)(root) gpart show ada0 > > =3D> 34 5860533101 ada0 GPT (2.7T) > > 34 990 1 freebsd-boot (495k) > > 1024 2098176 2 freebsd-swap (1.0G) > > 2099200 5858433928 3 freebsd-zfs (2.7T) > > 5860533128 7 - free - (3.5k) > > > ... >=20 > maybe I found something: > After setting vfs.zfs.debug=3D1 I got two new verbose bootlogs: > http://people.freebsd.org/~mr/boot_fail2.txt > http://people.freebsd.org/~mr/boot_success2.txt >=20 > As you can see, in the failing case ZFS tries to attach to ada[0123] > whereas in the succeeding case ZFS attaches to ada[0123]p3 (which are the= =20 > correct devices) Can you try setting kern.geom.part.check_integrity=3D0 ? Thanks, Gavin --=20 Gavin Atkinson FreeBSD committer and bugmeister GPG: A093262B (313A A79F 697D 3A5C 216A EDF5 935D EF44 A093 262B) From owner-freebsd-current@FreeBSD.ORG Fri Jun 3 16:12:40 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D02771065670; Fri, 3 Jun 2011 16:12:40 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id BCF948FC16; Fri, 3 Jun 2011 16:12:39 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id TAA16277; Fri, 03 Jun 2011 19:12:38 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <4DE907F5.2070901@FreeBSD.org> Date: Fri, 03 Jun 2011 19:12:37 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.17) Gecko/20110504 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: Nathan Whitehorn References: <4DE8FA2E.4030202@FreeBSD.org> <4DE8FD83.6030503@freebsd.org> In-Reply-To: <4DE8FD83.6030503@freebsd.org> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: Re: [poll / rfc] kdb_stop_cpus X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2011 16:12:40 -0000 on 03/06/2011 18:28 Nathan Whitehorn said the following: > On 06/03/11 10:13, Andriy Gapon wrote: >> >> I wonder if anybody uses kdb_stop_cpus with non-default value. >> If, yes, I am very interested to learn about your usecase for it. >> >> I think that the default kdb behavior is the correct one, so it doesn't make sense >> to have a knob to turn on incorrect behavior. >> But I may be missing something obvious. >> >> The comment in the code doesn't really satisfy me: >> /* >> * Flag indicating whether or not to IPI the other CPUs to stop them on >> * entering the debugger. Sometimes, this will result in a deadlock as >> * stop_cpus() waits for the other cpus to stop, so we allow it to be >> * disabled. In order to maximize the chances of success, use a hard >> * stop for that. >> */ >> >> The hard stop should be sufficiently mighty. >> Yes, I am aware of supposedly extremely rare situations where a deadlock could >> happen even when using hard stop. But I'd rather fix that than have this switch. >> >> Oh, the commit message (from 2004) explains it: >>> Add a new sysctl, debug.kdb.stop_cpus, which controls whether or not we >>> attempt to IPI other cpus when entering the debugger in order to stop >>> them while in the debugger. The default remains to issue the stop; >>> however, that can result in a hang if another cpu has interrupts disabled >>> and is spinning, since the IPI won't be received and the KDB will wait >>> indefinitely. We probably need to add a timeout, but this is a useful >>> stopgap in the mean time. >> >> But that was before we started using hard stop in this context (in 2009). > > Some non-x86 platforms (e.g. PPC) don't support real NMIs, and so this still applies. Well, even if it does, there are two things that can be done about that (and, IMO, both are better than the manually controlled knob): - quick and dirty: just let stop_cpus[_hard] timeout; this way good CPUs are stopped and the bad ones are no worse than with kdb_stop_cpus=0. - have a special reserved high priority interrupt, change 'disabling of interrupts' to 'disabling of all interrupts except the special one' by employing various kinds of interrupt priority registers (like it was done for splX stuff); use the special interrupt like an IPI+NMI. What do you think? P.S. I think that the first "quick and dirty" thing should be done anyway, regardless of any other changes and plans. -- Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Fri Jun 3 17:48:50 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7ED13106566B for ; Fri, 3 Jun 2011 17:48:50 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id 3F18D8FC0C for ; Fri, 3 Jun 2011 17:48:50 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) for freebsd-current@freebsd.org with esmtp (envelope-from ) id <1QSYUL-0002sk-5T>; Fri, 03 Jun 2011 19:48:49 +0200 Received: from e178009113.adsl.alicedsl.de ([85.178.9.113] helo=thor.walstatt.dyndns.org) by inpost2.zedat.fu-berlin.de (Exim 4.69) for freebsd-current@freebsd.org with esmtpsa (envelope-from ) id <1QSYUL-0002WS-3G>; Fri, 03 Jun 2011 19:48:49 +0200 Message-ID: <4DE91E80.1080508@zedat.fu-berlin.de> Date: Fri, 03 Jun 2011 19:48:48 +0200 From: "Hartmann, O." User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.17) Gecko/20110601 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: FreeBSD Current Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: 85.178.9.113 Subject: Linuxulator64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2011 17:48:50 -0000 In the year 2008, there were some discussions about efforts going on in developing a 64Bit compliant Linuxulator64 for FreeBSD/amd64. What is the status of this project? Oliver From owner-freebsd-current@FreeBSD.ORG Fri Jun 3 17:57:25 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BBF4E106566B; Fri, 3 Jun 2011 17:57:25 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 958EB8FC0A; Fri, 3 Jun 2011 17:57:25 +0000 (UTC) Received: from lemongrass.sec.cl.cam.ac.uk (lemongrass.sec.cl.cam.ac.uk [128.232.18.47]) by cyrus.watson.org (Postfix) with ESMTPSA id 9CA1A46B03; Fri, 3 Jun 2011 13:57:24 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: "Robert N. M. Watson" In-Reply-To: <4DE8FA2E.4030202@FreeBSD.org> Date: Fri, 3 Jun 2011 18:57:23 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <5E4D0F56-4338-4157-8BC6-17EE2831725F@FreeBSD.org> References: <4DE8FA2E.4030202@FreeBSD.org> To: Andriy Gapon X-Mailer: Apple Mail (2.1084) Cc: freebsd-current@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: Re: [poll / rfc] kdb_stop_cpus X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2011 17:57:25 -0000 On 3 Jun 2011, at 16:13, Andriy Gapon wrote: > I wonder if anybody uses kdb_stop_cpus with non-default value. > If, yes, I am very interested to learn about your usecase for it. The issue that prompted the sysctl was non-NMI IPIs being used to enter = the debugger or reboot following a core hanging with interrupts = disabled. With the switch to NMI IPIs in some of those circumstances, = life is better -- at least, on hardware that supports non-maskable IPIs. = I seem to recall sparc64 doesn't, however? Not sure about MIPS, etc. = Attilio has since significantly improved our shutdown behaviour -- = initially, the switch to NMI IPIs broke other things (because certain = IPIs then improperly preempted threads holding spinlocks), but that = pretty much all seems worked out now. Robert >=20 > I think that the default kdb behavior is the correct one, so it = doesn't make sense > to have a knob to turn on incorrect behavior. > But I may be missing something obvious. >=20 > The comment in the code doesn't really satisfy me: > /* > * Flag indicating whether or not to IPI the other CPUs to stop them on > * entering the debugger. Sometimes, this will result in a deadlock as > * stop_cpus() waits for the other cpus to stop, so we allow it to be > * disabled. In order to maximize the chances of success, use a hard > * stop for that. > */ >=20 > The hard stop should be sufficiently mighty. > Yes, I am aware of supposedly extremely rare situations where a = deadlock could > happen even when using hard stop. But I'd rather fix that than have = this switch. >=20 > Oh, the commit message (from 2004) explains it: >> Add a new sysctl, debug.kdb.stop_cpus, which controls whether or not = we >> attempt to IPI other cpus when entering the debugger in order to stop >> them while in the debugger. The default remains to issue the stop; >> however, that can result in a hang if another cpu has interrupts = disabled >> and is spinning, since the IPI won't be received and the KDB will = wait >> indefinitely. We probably need to add a timeout, but this is a = useful >> stopgap in the mean time. >=20 > But that was before we started using hard stop in this context (in = 2009). >=20 > --=20 > Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Fri Jun 3 20:27:40 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 01DBC1065674 for ; Fri, 3 Jun 2011 20:27:40 +0000 (UTC) (envelope-from cforgeron@acsi.ca) Received: from mta03.eastlink.ca (mta03.eastlink.ca [24.224.136.9]) by mx1.freebsd.org (Postfix) with ESMTP id BBBC98FC08 for ; Fri, 3 Jun 2011 20:27:39 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from ip03.eastlink.ca ([24.222.39.36]) by mta03.eastlink.ca (Oracle Communications Messaging Exchange Server 7u4-21.01 64bit (built Feb 16 2011)) with ESMTP id <0LM800MTUCRKXA61@mta03.eastlink.ca> for freebsd-current@freebsd.org; Fri, 03 Jun 2011 16:57:20 -0300 (ADT) X-CMAE-Score: 0 X-CMAE-Analysis: v=1.1 cv=j7CbBf0UjVt5t8oMLzyQ2uTroMF2aq/TSONqDSZKfgE= c=1 sm=1 a=dZxA7agGZuUA:10 a=IkcTkHD0fZMA:10 a=ExYiJt9ujVh27xuznyQA:9 a=QEXdDO2ut3YA:10 a=k1w2ZutsjhWYawe+LO1aOw==:117 Received: from blk-222-10-85.eastlink.ca (HELO server7.acsi.ca) ([24.222.10.85]) by ip03.eastlink.ca with ESMTP; Fri, 03 Jun 2011 16:57:20 -0300 Received: from server7.acsi.ca ([192.168.9.7]) by server7.acsi.ca ([192.168.9.7]) with mapi; Fri, 03 Jun 2011 16:57:20 -0300 From: Chris Forgeron To: Rick Macklem , "freebsd-current@freebsd.org" Date: Fri, 03 Jun 2011 16:57:18 -0300 Thread-topic: Heads Up: default NFS server changing to the new one Thread-index: AcwCFq8oMXauxcDpQxyZ5lGkCtcgcggD9sHQ Message-id: References: <2075443640.480241.1303603218847.JavaMail.root@erie.cs.uoguelph.ca> In-reply-to: <2075443640.480241.1303603218847.JavaMail.root@erie.cs.uoguelph.ca> Accept-Language: en-US Content-language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US X-Mailman-Approved-At: Fri, 03 Jun 2011 20:36:18 +0000 Cc: Subject: RE: Heads Up: default NFS server changing to the new one X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2011 20:27:40 -0000 BTW, I've been pounding on the new NFS server with a few test VM's from my ESX cluster for the last 2 weeks, 24/7. Everything looks solid, no panics, no errors, no corruption. Memory usage is staying stable, so I haven't found any leaks. I'm using IOMETER to move a few TB of randomized data a day over the NFS link from each VM. However, ESX is only a NFS3 client, so my tests are not exercising any NFS4 based protocols. I hope to do a speed test comparison between new and old NFS servers this weekend - At this stage, my feeling is that the new NFS server is at least as fast. I suspect tests will show it to be faster (at least the code looks faster. :-) ). I'm going to expand testing by upgrading one of our non-critical SAN's to the latest code as well, so we'll see what it's like having 20 different workstations connecting daily and moving small files has on it. Good work on the new code. From owner-freebsd-current@FreeBSD.ORG Fri Jun 3 20:43:59 2011 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E05C61065680 for ; Fri, 3 Jun 2011 20:43:59 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from mx0.hoeg.nl (mx0.hoeg.nl [IPv6:2a01:4f8:101:5343::aa]) by mx1.freebsd.org (Postfix) with ESMTP id 828E08FC0A for ; Fri, 3 Jun 2011 20:43:59 +0000 (UTC) Received: by mx0.hoeg.nl (Postfix, from userid 1000) id B23F32A28CF3; Fri, 3 Jun 2011 22:43:58 +0200 (CEST) Date: Fri, 3 Jun 2011 22:43:58 +0200 From: Ed Schouten To: current@FreeBSD.org Message-ID: <20110603204358.GC50646@hoeg.nl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9hzSyicXuByfNYJd" Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Subject: llimport(8): Import lastlog into utmpx X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2011 20:44:00 -0000 --9hzSyicXuByfNYJd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi all, I think not long after I replaced utmp with utmpx, I got requests to add utilities to convert the old utmp databases to the new formats. I added wtmpcvt(1) for /var/log/wtmp*, but I didn't add any tools for the other databases. Even though it's a bit overdue (more than one year later?), I think it wouldn't be a bad idea to add a utility to import lastlog for people who are going to upgrade from 7.x/8.x to 9.0. I've written a utility called llimport(8), which imports entries from lastlog into utx.lastlogin for users which do not already have an entry in the latter. I've also added an rc-script, which executes llimport when /var/log/lastlog is present and renames the old database to /var/log/lastlog.old. Any objections if I commit the following patch to HEAD one of these days? I will remove it from HEAD not long after we release 9.0, since an upgrade from 8.x to 10.x should go through 9.x anyway. http://80386.nl/pub/llimport.txt It would be nice if someone could look at the rc script. I think it should be okay, but it's not a part of the tree I'm familiar with. --=20 Ed Schouten WWW: http://80386.nl/ --9hzSyicXuByfNYJd Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (FreeBSD) iQIcBAEBAgAGBQJN6UeOAAoJEG5e2P40kaK7z2oP/3RLsUpnnpY5P7bXVzRNnkwQ GZhW902MEBn0ea0G2iRFiVRysxu9oSf9UX/3rK2B+8ZR7GNviyShPMd5XqY8wDgW NlbKJztTj7yZxcXppIP6cz61iEXQp/fCK9X73wQd3JMloIM5uxEtLjub2HDcVg9p mVRBz+MqasR8QNLbQiXBo3eQEjhNuVggT4b27BFbby/DH+UAxjk2tcf5xbb2WXHB VArr8eWFzDS4pAbdj6htNEZdyIHkrN1/Htafd3QoRd69QWkMuOF+h49BteJmtii+ 1wEFZQZ9Lo4NDAiYKd1GcFC+k1J7IoYO58vqXkijxh/V7IG9uGKRW1+yk7bPo8QJ 0KxEXMyuUUVw3WNrpJLq2q5FtH46ezlX6/mhrDtDT+vsooBwidAIoDcphsOhdLQS uHpLLsYKtyPLpgu9sma9kcEbp9Oa2qXKLMveIsKn2xvqFZ8v1zJe0zfTtvtKwi1o d0yOSU9ved7ZHWPOoDdf0LAJdoRLWRw2L3mVw2aAzmAgvE7OLONGZTl4MggkLKBn Ru6qpkD2JL61xu8mz973T6t1lVOpM1/v2wIMSUWaUp5nEwPUP+a7cUMsgpA+g+p1 csWxHwWEW4qwfz+2oP9J+a8vxD+Zh6eTbTnw3qpOByvg7tcgyy3JmkN8XdChnt+g D2zGV/WX6EWXWT02M5UZ =KRL/ -----END PGP SIGNATURE----- --9hzSyicXuByfNYJd-- From owner-freebsd-current@FreeBSD.ORG Fri Jun 3 20:47:59 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2A073106567E for ; Fri, 3 Jun 2011 20:47:59 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id D41A28FC0C for ; Fri, 3 Jun 2011 20:47:58 +0000 (UTC) Received: by vxc34 with SMTP id 34so2322724vxc.13 for ; Fri, 03 Jun 2011 13:47:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=9m2J+CIt6642stIOWDDWH5wKOf582iq4nl5qM75CD2s=; b=Go8FL30JlOnquJcE0YKyclLOMrc0Ia82LbvUsn387+EZ0fnOQsNG8QU7jAg1vOLiFD CanLF4o4Q7LEQUZdEbIIgiEZtAczYbS6OW7QhYeHbInuqG0N/Ye8q5/minzdoVtw8VgD wWxuDM4gzpMSKmPXu+aBLOAh0lG7CE9C1nEqM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=rWYxot70pWnU5ZZXi++TpWI5YSj7Wjj6DtLHqpDVMnp/bd3GWyPPLSXRZ265ZbzyP6 lNEmYbIuOhUegXSHeZUXyZ6vkci7KdFPBwx6NS+6sZXTb003dRXrMpVTtO+irocgLyKa m4/bI0qJGOg6JR2VOSWfAcVAdKu6Oy5lYquQY= MIME-Version: 1.0 Received: by 10.220.213.195 with SMTP id gx3mr39146vcb.23.1307134077847; Fri, 03 Jun 2011 13:47:57 -0700 (PDT) Received: by 10.220.181.139 with HTTP; Fri, 3 Jun 2011 13:47:57 -0700 (PDT) In-Reply-To: <20110603204358.GC50646@hoeg.nl> References: <20110603204358.GC50646@hoeg.nl> Date: Fri, 3 Jun 2011 13:47:57 -0700 Message-ID: From: Garrett Cooper To: Ed Schouten Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: current@freebsd.org Subject: Re: llimport(8): Import lastlog into utmpx X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2011 20:47:59 -0000 On Fri, Jun 3, 2011 at 1:43 PM, Ed Schouten wrote: > Hi all, > > I think not long after I replaced utmp with utmpx, I got requests to add > utilities to convert the old utmp databases to the new formats. I added > wtmpcvt(1) for /var/log/wtmp*, but I didn't add any tools for the other > databases. Even though it's a bit overdue (more than one year later?), I > think it wouldn't be a bad idea to add a utility to import lastlog for > people who are going to upgrade from 7.x/8.x to 9.0. > > I've written a utility called llimport(8), which imports entries from > lastlog into utx.lastlogin for users which do not already have an entry > in the latter. I've also added an rc-script, which executes llimport > when /var/log/lastlog is present and renames the old database to > /var/log/lastlog.old. > > Any objections if I commit the following patch to HEAD one of these > days? I will remove it from HEAD not long after we release 9.0, since an > upgrade from 8.x to 10.x should go through 9.x anyway. > > =A0 =A0 =A0 =A0http://80386.nl/pub/llimport.txt > > It would be nice if someone could look at the rc script. I think it > should be okay, but it's not a part of the tree I'm familiar with. Is this a one time change? If so, wouldn't it make more sense to put this into mergemaster(8) instead of rc(5)? Thanks! -Garrett From owner-freebsd-current@FreeBSD.ORG Fri Jun 3 20:56:10 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CEADE106564A for ; Fri, 3 Jun 2011 20:56:10 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from mx0.hoeg.nl (mx0.hoeg.nl [IPv6:2a01:4f8:101:5343::aa]) by mx1.freebsd.org (Postfix) with ESMTP id 958B28FC14 for ; Fri, 3 Jun 2011 20:56:10 +0000 (UTC) Received: by mx0.hoeg.nl (Postfix, from userid 1000) id 0952B2A28CF3; Fri, 3 Jun 2011 22:56:10 +0200 (CEST) Date: Fri, 3 Jun 2011 22:56:10 +0200 From: Ed Schouten To: Garrett Cooper Message-ID: <20110603205610.GD50646@hoeg.nl> References: <20110603204358.GC50646@hoeg.nl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Wo0oCZYLrer5S3Oe" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: current@freebsd.org Subject: Re: llimport(8): Import lastlog into utmpx X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2011 20:56:10 -0000 --Wo0oCZYLrer5S3Oe Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Garrett, * Garrett Cooper , 20110603 22:47: > Is this a one time change? If so, wouldn't it make more sense to > put this into mergemaster(8) instead of rc(5)? Good point. I hadn't thought about that. I'll take a look. --=20 Ed Schouten WWW: http://80386.nl/ --Wo0oCZYLrer5S3Oe Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (FreeBSD) iQIcBAEBAgAGBQJN6UppAAoJEG5e2P40kaK71VMP/2ekqFCdS6likOEREK1TDdOU 3BNK3xQNrp/Fzpxh7lK+082S/dnXhdY9zU6gDGvX0KGuUAk015h/y1n2dGqiZ0fo Nx3cmibPMOsx4apA/qsP+O7tdR9/xSJ00v8gVb3jn0tXufNNmUQrejjvX/hnWSb2 yG5mb8t69CJX0FJjCo91dGEvA27TcKvZlxHBa7nmqwYdi3pMS5aSDD0KWxgwtrT7 Wv+Dx17v3eA2T0My6UsY7tOLkW8KevPhZcm/LTXLR4oFUSd4en5glSjouPTjDkGa 6k5WuPsAxVfQn4EgauOYXad3eQ0qfpRwnxhebwAbmEHos633nIgIF5/zSkbWIlwC D1h3jN/+FPVdg8YBL3nA90+2ex4TJvCUSZImyuGrALZn5SHgDQd5eHEOakr+vUx+ A5zjFE0+HFLLaDQwkXiqtg7gZeqStFg91oNIyG8vzhcr+m5hVgwC3s065oOnRf0p R7Fl3XLydVkrMcNgcfwsO5NdhJpyh0YLYfPC8zX+vbGnaSCLGgM679kjj4ackfp9 VbNRP8tdavUXYRs4+a3HLHlZqJCH74wQPyvV8F9tGzaE7eyfv8RlqMrW3d5tP7GT eXFXNr6oGLGgRrZlVXvpMKcBHPq1mqKa933MOMarBc2q7uliYGtrPgD9WW+KelPl KDojkGSvPILrsZPHjVkT =UP/j -----END PGP SIGNATURE----- --Wo0oCZYLrer5S3Oe-- From owner-freebsd-current@FreeBSD.ORG Fri Jun 3 20:58:01 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 335381065689 for ; Fri, 3 Jun 2011 20:58:01 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 65-241-43-5.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 6526D15F29D; Fri, 3 Jun 2011 20:58:00 +0000 (UTC) Message-ID: <4DE94AD7.6060007@FreeBSD.org> Date: Fri, 03 Jun 2011 13:57:59 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.17) Gecko/20110429 Thunderbird/3.1.10 MIME-Version: 1.0 To: Garrett Cooper References: <20110603204358.GC50646@hoeg.nl> In-Reply-To: X-Enigmail-Version: 1.1.2 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Ed Schouten , current@freebsd.org Subject: Re: llimport(8): Import lastlog into utmpx X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2011 20:58:01 -0000 On 06/03/2011 13:47, Garrett Cooper wrote: > On Fri, Jun 3, 2011 at 1:43 PM, Ed Schouten wrote: >> Hi all, >> >> I think not long after I replaced utmp with utmpx, I got requests to add >> utilities to convert the old utmp databases to the new formats. I added >> wtmpcvt(1) for /var/log/wtmp*, but I didn't add any tools for the other >> databases. Even though it's a bit overdue (more than one year later?), I >> think it wouldn't be a bad idea to add a utility to import lastlog for >> people who are going to upgrade from 7.x/8.x to 9.0. >> >> I've written a utility called llimport(8), which imports entries from >> lastlog into utx.lastlogin for users which do not already have an entry >> in the latter. I've also added an rc-script, which executes llimport >> when /var/log/lastlog is present and renames the old database to >> /var/log/lastlog.old. >> >> Any objections if I commit the following patch to HEAD one of these >> days? I will remove it from HEAD not long after we release 9.0, since an >> upgrade from 8.x to 10.x should go through 9.x anyway. >> >> http://80386.nl/pub/llimport.txt >> >> It would be nice if someone could look at the rc script. I think it >> should be okay, but it's not a part of the tree I'm familiar with. > > Is this a one time change? If so, wouldn't it make more sense to > put this into mergemaster(8) instead of rc(5)? FWIW I'm not enthusiastic about either option. I definitely don't think an rc.d script is desirable, since it would be run at every boot for what (if I understand it correctly) is a one-time thing. More or less the same argument applies to adding this to mergemaster. In my mind the best way to handle this would be to add it to tools/ and let users who need it access it that way. But perhaps I'm missing something? Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-current@FreeBSD.ORG Fri Jun 3 21:07:12 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0DA241065676; Fri, 3 Jun 2011 21:07:12 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from mx0.hoeg.nl (mx0.hoeg.nl [IPv6:2a01:4f8:101:5343::aa]) by mx1.freebsd.org (Postfix) with ESMTP id C7A1E8FC1C; Fri, 3 Jun 2011 21:07:11 +0000 (UTC) Received: by mx0.hoeg.nl (Postfix, from userid 1000) id 3B9BC2A28CF3; Fri, 3 Jun 2011 23:07:11 +0200 (CEST) Date: Fri, 3 Jun 2011 23:07:11 +0200 From: Ed Schouten To: Doug Barton Message-ID: <20110603210711.GE50646@hoeg.nl> References: <20110603204358.GC50646@hoeg.nl> <4DE94AD7.6060007@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="NQFQLHPkFLmdEfVA" Content-Disposition: inline In-Reply-To: <4DE94AD7.6060007@FreeBSD.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Garrett Cooper , current@freebsd.org Subject: Re: llimport(8): Import lastlog into utmpx X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2011 21:07:12 -0000 --NQFQLHPkFLmdEfVA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Doug, * Doug Barton , 20110603 22:57: > FWIW I'm not enthusiastic about either option. I definitely don't > think an rc.d script is desirable, since it would be run at every > boot for what (if I understand it correctly) is a one-time thing. > More or less the same argument applies to adding this to mergemaster. True. I just looked at mergemaster, but adding it to mergemaster could be unreliable. Say, you're running mergemaster on a different destdir, it would call llimport from the host system, meaning it uses the user database (and byte order) of the host, instead of the target. > In my mind the best way to handle this would be to add it to tools/ > and let users who need it access it that way. But perhaps I'm missing > something? I could do that as well, but the reason why I picked the current approach, is because I don't want to cause people to get confused when they upgrade to 9.0, to discover that their lastlog database is `missing'. Groetjes, --=20 Ed Schouten WWW: http://80386.nl/ --NQFQLHPkFLmdEfVA Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (FreeBSD) iQIcBAEBAgAGBQJN6Uz/AAoJEG5e2P40kaK76jIP/2+MD96eK5Mc0QQXUANK81oy ypIxQDycR1zU87Lo+86lQPFLGUSO/6h+p0XEdaymm3yh+k+Czr4pyZe0IGng7AZO AvttSXs5rlulXkUmwZP2IAqNdzJ1uvzuTaHMIPOnSoHPj8MJEWAaHtsCKzZ5+og4 GccKiLhEP9Exf6v5qnw+w2pmYqjxvns4DIpN/DHoLxFrm0hZPL37Wyz5Ez+BclEO EYmgmbuW5HhE6ccV7dQy4iLgvnRO3bVKkIPU/Rk4BbbRvG5P/Gatccr4mKoSuPih 59oMlwzPheAg1UkUImS518bF3d7wjBS3+mL2NTuohhGPVerQRaMRME2bWimR8HZz NDByBQM3x51vSTByCX2PH2JU6yjIW28Nl21rKXQUD19BRYs9RPWF2uQWsUEaru2v jpPT59bDw3DUYfbXIwzbm2L/kitGMXfJl/Bb0L0I5jVOnvuuuZlNPNHQE57HkfFP y+1lYZQn+2DNi7JKHOHr6dsU5UQ6HscWbsK2zlBHavWauvnss1ZkJNyW0NRs4wSo xjyQoBRC+eCCDIEFX8Suw3bBIBMEsxYESj7uMNGN23z08IPWeNCug/VFPlJvj81r J2qCec+a3cdcUc1dVmMvS61hVoPs9CyjGAslNEkM2fWuLPqdj6Y5BaCUpMiAGP+a gcYCMbocqknFNm64dev7 =W6L9 -----END PGP SIGNATURE----- --NQFQLHPkFLmdEfVA-- From owner-freebsd-current@FreeBSD.ORG Fri Jun 3 21:10:58 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 1BCF2106567B for ; Fri, 3 Jun 2011 21:10:58 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 65-241-43-5.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id BD7ED153DF2; Fri, 3 Jun 2011 21:10:45 +0000 (UTC) Message-ID: <4DE94DD5.1040607@FreeBSD.org> Date: Fri, 03 Jun 2011 14:10:45 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.17) Gecko/20110429 Thunderbird/3.1.10 MIME-Version: 1.0 To: Ed Schouten References: <20110603204358.GC50646@hoeg.nl> <4DE94AD7.6060007@FreeBSD.org> <20110603210711.GE50646@hoeg.nl> In-Reply-To: <20110603210711.GE50646@hoeg.nl> X-Enigmail-Version: 1.1.2 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Garrett Cooper , current@freebsd.org Subject: Re: llimport(8): Import lastlog into utmpx X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2011 21:10:58 -0000 On 06/03/2011 14:07, Ed Schouten wrote: > the reason why I picked the current > approach, is because I don't want to cause people to get confused when > they upgrade to 9.0, to discover that their lastlog database is > `missing'. Understood, but in my mind that's a release notes issue. -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-current@FreeBSD.ORG Fri Jun 3 21:26:14 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7732E106567A; Fri, 3 Jun 2011 21:26:14 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from mx0.hoeg.nl (mx0.hoeg.nl [IPv6:2a01:4f8:101:5343::aa]) by mx1.freebsd.org (Postfix) with ESMTP id 3C4A08FC12; Fri, 3 Jun 2011 21:26:14 +0000 (UTC) Received: by mx0.hoeg.nl (Postfix, from userid 1000) id A3A702A28CF3; Fri, 3 Jun 2011 23:26:13 +0200 (CEST) Date: Fri, 3 Jun 2011 23:26:13 +0200 From: Ed Schouten To: Doug Barton Message-ID: <20110603212613.GF50646@hoeg.nl> References: <20110603204358.GC50646@hoeg.nl> <4DE94AD7.6060007@FreeBSD.org> <20110603210711.GE50646@hoeg.nl> <4DE94DD5.1040607@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="J+xDcZ1j08+V/OfU" Content-Disposition: inline In-Reply-To: <4DE94DD5.1040607@FreeBSD.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Garrett Cooper , current@freebsd.org Subject: Re: llimport(8): Import lastlog into utmpx X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2011 21:26:14 -0000 --J+xDcZ1j08+V/OfU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Doug Barton , 20110603 23:10: > On 06/03/2011 14:07, Ed Schouten wrote: > >the reason why I picked the current > >approach, is because I don't want to cause people to get confused when > >they upgrade to 9.0, to discover that their lastlog database is > >`missing'. >=20 > Understood, but in my mind that's a release notes issue. That sounds like a good idea. I'll see what I can do. Thanks! --=20 Ed Schouten WWW: http://80386.nl/ --J+xDcZ1j08+V/OfU Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (FreeBSD) iQIcBAEBAgAGBQJN6VF1AAoJEG5e2P40kaK78jEP/3YDe6IRZjNa/D/c3/+20sQg Z6ui6KLwb/h8JlGe2FL/kE5a+Q+lwWQn5819+jG88gZjYW5K9hxSoRcfRD4oMITz daMYS2Dj5Qxk6/OQ28a7uhx3sFN/LoK/I1RGddZGV9EJF3n19d4Es/fZNDH/oZxH BFfdLzmsQ1Xn3EVwINobxWYu58g86/eujTMjB5zsXcvEBIMqkWWsTvzcl/0kKtEm 4pQvTu92oyH5AzY+BkK/u2EfL3/1xSNtzJSckQteVc2SapqNYehmp9zC7Ip3/LQq aProOtg00J8sziohk2VE1+9YcHVpOh2WfspzrOfX6nbJDeFm4843A9KjupBJckxZ 0diqCAnMqSffZngXcWMCEd/FQ+7Hr0oezusj/KxoiMghtBUqNowwqi2IifarGDfB jNSEX6YCt856G7MB63Fjr6IeOTwaiWdSEQ93lnEsyjvRVCdrDk0tUKTPyeedxHXM fyCwNwlgAmKMWAyuUWQBUy5vW6LGAzjfu4u7d2Dxrl0w/C+on8PoRTmTIw5m/5RS J/qduK+nG3dN0+EI8tlaFI2WDNxb7mo6YRgaA3WReBiyiXSRZqZanANLD3yk45+m 0iK7wCrmjBeqi83luZyyTmK3bd8JL/g5M+1JJW7cxq71H/tthk7XdAu6TLf2IO+9 SMq1VIPIZM5Jez8Efy4J =uE1C -----END PGP SIGNATURE----- --J+xDcZ1j08+V/OfU-- From owner-freebsd-current@FreeBSD.ORG Sat Jun 4 00:28:48 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 528AA106564A; Sat, 4 Jun 2011 00:28:48 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id BA5258FC17; Sat, 4 Jun 2011 00:28:47 +0000 (UTC) Received: by wyf23 with SMTP id 23so2410418wyf.13 for ; Fri, 03 Jun 2011 17:28:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=PlaS/QCpKrEfagTC8ffFXWy45yZpCW4b5iGUtVDjfGQ=; b=OE53znOHhW3/XnEJ/ZEvAVG5+uDa8o2AC6CGi684+VWnbNXrklnIvEb9djDXNhaGfh P9Kr8T+YjljLXPUXQ8/KYj6A8oHOSGT8DjeTdYD1q1lUB24BDuwAGnjZgDbcefz91bGq 487ePcSgvK4HPcO7Shs2cjjRYT37Lpa0Xz+U0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=oe0np7TT2r/wUTUjdGZOncyWc0ELTCsTdeSWHGJtWhCYiX7kkEETt6HfCGn4ZavxBG PGm8EQqUm0U+0LbXj9jEXR/c14jbZHuUBUdalI2Nr3rEOctSv1AulJJvxUMLmIZJzguq 9UTzkM0NXqxtBr6mp8BOWE3LSBBnb7VsRlOTY= MIME-Version: 1.0 Received: by 10.216.46.21 with SMTP id q21mr7706777web.113.1307145776826; Fri, 03 Jun 2011 17:02:56 -0700 (PDT) Received: by 10.216.35.5 with HTTP; Fri, 3 Jun 2011 17:02:56 -0700 (PDT) Date: Fri, 3 Jun 2011 20:02:56 -0400 Message-ID: From: Aryeh Friedman To: FreeBSD Current , FreeBSD Ports ML Content-Type: text/plain; charset=ISO-8859-1 Cc: Subject: 8-STABLE /usr/include/utmp.h and tmpx X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jun 2011 00:28:48 -0000 Some time in the last 2 weeks (I am sure when) a commit caused many ports that assume a "standard" utmp/utmp.x to break for example x11-toolkits/vte produces: gnome-pty-helper.c:497: warning: passing argument 4 of 'pty_add' discards qualifiers from pointer target type mv -f .deps/gnome-pty-helper.Tpo .deps/gnome-pty-helper.Po cc -DHAVE_CONFIG_H -I. -I/usr/local/include -O2 -pipe -march=prescott -fno-strict-aliasing -MT gnome-utmp.o -MD -MP -MF .deps/gnome-utmp.Tpo -c -o gnome-utmp.o gnome-utmp.c gnome-utmp.c: In function 'write_login_record': gnome-utmp.c:367: warning: passing argument 1 of 'login' from incompatible pointer type gnome-utmp.c:374: error: 'struct utmpx' has no member named 'ut_name' This is not the only port that has the issue but it is the only one I remember off the top of my head (I manually fixed a few others) From owner-freebsd-current@FreeBSD.ORG Sat Jun 4 01:11:08 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2290F106566C for ; Sat, 4 Jun 2011 01:11:08 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id AFC6C8FC12 for ; Sat, 4 Jun 2011 01:11:07 +0000 (UTC) Received: by vws18 with SMTP id 18so2445917vws.13 for ; Fri, 03 Jun 2011 18:11:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=uuBVHaIUnEVSlTMeX098QJQJhGluXdRUdjFYejsG/ms=; b=fn+jBBnlGn7RhdaimrssyO2vg3aGiiMgQ8rc/OQISDaYCuMeVLJ9p92eQoDlHLSxEF IOdp9VIY1LClzJw8wSLi/sAoPsUvk1IKmq9t/Db0C1ouf/6qPp+1hYJY+wLpAHw6h1wV 4h12OVkdDH7oxpY6daQR5GurP9brGEX3DWHDc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=TcR/Pe3WZtIzQHPvk/vE3tYLbMRLzryWkUWHdagQxz0nGaeAO+p7AN6ULDfiWl/pjt PPJUHXIqHohPygyKKyoBIb/MjOTVlf6c11Rf9ZscTvcgeAqQiJfe9GzVGNCXcoPYpTdv cjiwvf8y6on2bm4q0WhFkRW5f8CCJadAkvbu8= MIME-Version: 1.0 Received: by 10.220.187.76 with SMTP id cv12mr211714vcb.128.1307149766513; Fri, 03 Jun 2011 18:09:26 -0700 (PDT) Received: by 10.220.181.139 with HTTP; Fri, 3 Jun 2011 18:09:26 -0700 (PDT) In-Reply-To: References: Date: Fri, 3 Jun 2011 18:09:26 -0700 Message-ID: From: Garrett Cooper To: Aryeh Friedman Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD Current , FreeBSD Ports ML Subject: Re: 8-STABLE /usr/include/utmp.h and tmpx X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jun 2011 01:11:08 -0000 On Fri, Jun 3, 2011 at 5:02 PM, Aryeh Friedman w= rote: > Some time in the last 2 weeks (I am sure when) a commit caused many > ports that assume a "standard" utmp/utmp.x to break for example > x11-toolkits/vte produces: > > gnome-pty-helper.c:497: warning: passing argument 4 of 'pty_add' > discards qualifiers from pointer target type > mv -f .deps/gnome-pty-helper.Tpo .deps/gnome-pty-helper.Po > cc -DHAVE_CONFIG_H -I. =A0 -I/usr/local/include =A0-O2 -pipe > -march=3Dprescott -fno-strict-aliasing -MT gnome-utmp.o -MD -MP -MF > .deps/gnome-utmp.Tpo -c -o gnome-utmp.o gnome-utmp.c > gnome-utmp.c: In function 'write_login_record': > gnome-utmp.c:367: warning: passing argument 1 of 'login' from > incompatible pointer type > gnome-utmp.c:374: error: 'struct utmpx' has no member named 'ut_name' > > > This is not the only port that has the issue but it is the only one I > remember off the top of my head (I manually fixed a few others) Compiles just fine on CURRENT. Did you open a PR for this item? Thanks, -Garrett From owner-freebsd-current@FreeBSD.ORG Sat Jun 4 01:17:00 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6CE0D106564A; Sat, 4 Jun 2011 01:17:00 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id CD8098FC0C; Sat, 4 Jun 2011 01:16:59 +0000 (UTC) Received: by wyf23 with SMTP id 23so2427447wyf.13 for ; Fri, 03 Jun 2011 18:16:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=0BFF6gl48/Tnnr0ybyu10UTJwzoYj8v8kTfwnwoA2Eg=; b=bT75vBdydzyoNGKqhsT2+3tpIW5bVX15YqrDtq0wglz4jBrhIYGJ1DS/fe98lE4xzZ /sUyK/ssQMgnvjeNckDi4sa3o5MUIJ5LThTQRuD4b8mbBWQOmIvG0NkjuRpiQce1VnQK BQjv5UqL5jKTYc/kJPnJ7v6NACkFz2yKODCMU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=QWT2I4AMELx7SEz7KEbE0x9rgfM3szOeByG3dZ5TwUMfMvkOAWsDecR74wgto6NDgY zBI6tT0rGsB1RtPFpagss8qTw3OJHrLTgyRaqyoxVbNX/OOk70oQBuMziUhdDYGZGLSQ GQAtDAcWB2t1s6oxJ2w8M2VXLiwunEynFjuZA= MIME-Version: 1.0 Received: by 10.216.231.89 with SMTP id k67mr2379086weq.113.1307150218573; Fri, 03 Jun 2011 18:16:58 -0700 (PDT) Received: by 10.216.35.5 with HTTP; Fri, 3 Jun 2011 18:16:58 -0700 (PDT) In-Reply-To: References: Date: Fri, 3 Jun 2011 21:16:58 -0400 Message-ID: From: Aryeh Friedman To: Garrett Cooper Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD Current , FreeBSD Ports ML Subject: Re: 8-STABLE /usr/include/utmp.h and tmpx X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jun 2011 01:17:00 -0000 No will do even though I don't think I have a complete enough list of ports to make a proper report (if in fact it is a per port solution vs. fixing base) On Fri, Jun 3, 2011 at 9:09 PM, Garrett Cooper wrote: > On Fri, Jun 3, 2011 at 5:02 PM, Aryeh Friedman = wrote: >> Some time in the last 2 weeks (I am sure when) a commit caused many >> ports that assume a "standard" utmp/utmp.x to break for example >> x11-toolkits/vte produces: >> >> gnome-pty-helper.c:497: warning: passing argument 4 of 'pty_add' >> discards qualifiers from pointer target type >> mv -f .deps/gnome-pty-helper.Tpo .deps/gnome-pty-helper.Po >> cc -DHAVE_CONFIG_H -I. =A0 -I/usr/local/include =A0-O2 -pipe >> -march=3Dprescott -fno-strict-aliasing -MT gnome-utmp.o -MD -MP -MF >> .deps/gnome-utmp.Tpo -c -o gnome-utmp.o gnome-utmp.c >> gnome-utmp.c: In function 'write_login_record': >> gnome-utmp.c:367: warning: passing argument 1 of 'login' from >> incompatible pointer type >> gnome-utmp.c:374: error: 'struct utmpx' has no member named 'ut_name' >> >> >> This is not the only port that has the issue but it is the only one I >> remember off the top of my head (I manually fixed a few others) > > =A0 =A0Compiles just fine on CURRENT. Did you open a PR for this item? > Thanks, > -Garrett > From owner-freebsd-current@FreeBSD.ORG Sat Jun 4 01:23:18 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9790C1065670; Sat, 4 Jun 2011 01:23:18 +0000 (UTC) (envelope-from yuri.pankov@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id EA1458FC08; Sat, 4 Jun 2011 01:23:17 +0000 (UTC) Received: by fxm11 with SMTP id 11so2340140fxm.13 for ; Fri, 03 Jun 2011 18:23:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:x-authentication-warning:date:from:to:cc :subject:message-id:references:mime-version:content-type :content-disposition:in-reply-to:user-agent; bh=4VtLXepLK6TLlxo+KUdOgc7JeNgFxXGLj+qr3Hhy8Hg=; b=fsE0GhrAz3hRqddjFkW5JJxE27lsxTwIAKi78F3J2epQqLi5iHApPQOVxwwuKEeoIl KkS5BoMP6IeuEUop+DGve9ryAD9a9QB0qjqbWpUGkQ6xHuzOQkqtyEnUkRHNQokzvLPG 8uzPUvADQBPUqyKUmn3CSqruezT12/WDvr/xw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=x-authentication-warning:date:from:to:cc:subject:message-id :references:mime-version:content-type:content-disposition :in-reply-to:user-agent; b=ZJtEb2ga7j0M24WGRk+ELOlVSbjPd9INbU+AIkUM74cW8S8dmJukiO3Jms2x3RW6OO WNo1EZgarwAKtkyPCmNCXp2do6kw5/NEDVV7nE6Mt8DE8FU/Zr6jo60/U0S24IlGs6Ap qaRabWZeW4d5gb0/lI622kDqAizsQ8hQdxCow= Received: by 10.223.30.82 with SMTP id t18mr2809557fac.106.1307150596887; Fri, 03 Jun 2011 18:23:16 -0700 (PDT) Received: from procyon.xvoid.org ([213.132.76.142]) by mx.google.com with ESMTPS id b25sm641102fab.28.2011.06.03.18.23.15 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 03 Jun 2011 18:23:16 -0700 (PDT) Received: from procyon.xvoid.org (yuri@procyon.xvoid.org [IPv6:::1]) by procyon.xvoid.org (8.14.4/8.14.4) with ESMTP id p541NDDZ000621; Sat, 4 Jun 2011 05:23:13 +0400 (MSD) (envelope-from yuri.pankov@gmail.com) Received: (from yuri@localhost) by procyon.xvoid.org (8.14.4/8.14.4/Submit) id p541NDLQ000620; Sat, 4 Jun 2011 05:23:13 +0400 (MSD) (envelope-from yuri.pankov@gmail.com) X-Authentication-Warning: procyon.xvoid.org: yuri set sender to yuri.pankov@gmail.com using -f Date: Sat, 4 Jun 2011 05:23:13 +0400 From: Yuri Pankov To: Aryeh Friedman Message-ID: <20110604012313.GE1247@procyon.xvoid.org> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="48TaNjbzBVislYPb" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current@freebsd.org, freebsd-ports@freebsd.org Subject: Re: 8-STABLE /usr/include/utmp.h and tmpx X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jun 2011 01:23:18 -0000 --48TaNjbzBVislYPb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Jun 03, 2011 at 09:16:58PM -0400, Aryeh Friedman wrote: > No will do even though I don't think I have a complete enough list of > ports to make a proper report (if in fact it is a per port solution > vs. fixing base) I don't see any related commits to 8-STABLE, which commit are you reffering to (and guessing on previous thread, such change isn't going to be MFCed)? Yuri --48TaNjbzBVislYPb Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (FreeBSD) iQIcBAABAgAGBQJN6YkBAAoJEF9SuVmZPGsqp6AP/A8iewkIL6kn2l69h4Sg0PtK U+7vBWRRHv4Zo14z+Yn2n3D2KvGLFXi0dbf5LWJKuIRZuBiYRJUCOwSGT4wjlwHM On0P24gJZpxrs6l0jrQe2IxT+iKiPuFDCVThcc/r12wIpvmjLitxrOBeNcsZoVI7 DpwHPVHJ5P/IFsiy5PbJHRZM3zADI7c0MDaoQpsgd7WMzr9F2534aJ/B6dAWZdfH dZKLCZzkx1TB4cV/IAQMN2mwU0zOaCgpGRMhyra5GjVQuoEvnjtbpblNtcALrgBK +vp0ZqBKFxLwHhyDZ8XaEBM/JdpP1X4vJ3MuJ3aGJGtYm3G23wvvjIv+9+oahz2e m+jfDpWAlXjq51TKZIaBRSTAecG0hARuI29f7/Pw7rQkpCAc01fg92yQlK7QXNE4 bcXaPfqs3be4fLoRazL5IIthf4p2mIt3hYMzdQ6CltsxZ/ONzVEzR8YxhUjzbJgP QpB9bI4XPLgzniBCNTO/2XuwlxWmB1xrl3Td2PEKc9bwxY3TxNm6urLu2w1hVYqX clhSDU7cViYVcqXl97RJksXRpw0i9VZb8S6mnv2AMmHvviiXgY1mjDTnmD2EVoo8 X8g3wTFMK9IYVY11s2A7+DlhZ7KFnj60yGJSql5DFPKcc3Sn0D1x5ucIBrlXVCw9 Av1YDONDmu01NgBH5kF6 =knre -----END PGP SIGNATURE----- --48TaNjbzBVislYPb-- From owner-freebsd-current@FreeBSD.ORG Sat Jun 4 01:54:53 2011 Return-Path: Delivered-To: current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 983B9106564A for ; Sat, 4 Jun 2011 01:54:53 +0000 (UTC) (envelope-from ache@vniz.net) Received: from vniz.net (vniz.net [194.87.13.69]) by mx1.freebsd.org (Postfix) with ESMTP id 02C078FC13 for ; Sat, 4 Jun 2011 01:54:52 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by vniz.net (8.14.4/8.14.4) with ESMTP id p541so7a043465; Sat, 4 Jun 2011 05:54:50 +0400 (MSD) (envelope-from ache@vniz.net) Received: (from ache@localhost) by localhost (8.14.4/8.14.4/Submit) id p541soIs043464; Sat, 4 Jun 2011 05:54:50 +0400 (MSD) (envelope-from ache) Date: Sat, 4 Jun 2011 05:54:49 +0400 From: Andrey Chernov To: Ruslan Ermilov Message-ID: <20110604015449.GA43316@vniz.net> Mail-Followup-To: Andrey Chernov , Ruslan Ermilov , current@FreeBSD.ORG References: <20110603144859.GA73084@lo0.su> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110603144859.GA73084@lo0.su> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: current@FreeBSD.ORG Subject: Re: [HEADS UP] color and page width support in man(1) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jun 2011 01:54:53 -0000 On Fri, Jun 03, 2011 at 02:48:59PM +0000, Ruslan Ermilov wrote: > On a freshly installed -CURRENT, to view a colorized manpage in color > and in full terminal width, try this: > > env MANCOLOR=yes MANWIDTH=tty man grotty > SGR presence can be easily autodetected analyzing termcap capibilities (for isatty() case). -- http://ache.vniz.net/ From owner-freebsd-current@FreeBSD.ORG Sat Jun 4 08:23:01 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3D4EC1065675; Sat, 4 Jun 2011 08:23:01 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 253CF8FC16; Sat, 4 Jun 2011 08:22:59 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id LAA24873; Sat, 04 Jun 2011 11:22:58 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1QSm8I-0004eU-Du; Sat, 04 Jun 2011 11:22:58 +0300 Message-ID: <4DE9EB61.3000006@FreeBSD.org> Date: Sat, 04 Jun 2011 11:22:57 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.17) Gecko/20110503 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: "Robert N. M. Watson" References: <4DE8FA2E.4030202@FreeBSD.org> <5E4D0F56-4338-4157-8BC6-17EE2831725F@FreeBSD.org> In-Reply-To: <5E4D0F56-4338-4157-8BC6-17EE2831725F@FreeBSD.org> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: Re: [poll / rfc] kdb_stop_cpus X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jun 2011 08:23:01 -0000 on 03/06/2011 20:57 Robert N. M. Watson said the following: > > On 3 Jun 2011, at 16:13, Andriy Gapon wrote: > >> I wonder if anybody uses kdb_stop_cpus with non-default value. If, yes, I >> am very interested to learn about your usecase for it. > > The issue that prompted the sysctl was non-NMI IPIs being used to enter the > debugger or reboot following a core hanging with interrupts disabled. With > the switch to NMI IPIs in some of those circumstances, life is better -- at > least, on hardware that supports non-maskable IPIs. I seem to recall sparc64 > doesn't, however? Seems to be so as Nathan has also pointed out for PPC. For this I also plan the following change: commit 458ebd9aca7e91fc6e0825c727c7220ab9f61016 generic_stop_cpus: move timeout detection code from under DIAGNOSTIC ... and also increase it a bit. IMO it's better to detect and report the (rather serious) condition and allow a system to proceed somehow rather than be stuck in an endless loop. diff --git a/sys/kern/subr_smp.c b/sys/kern/subr_smp.c index ae52f4b..4bd766b 100644 --- a/sys/kern/subr_smp.c +++ b/sys/kern/subr_smp.c @@ -232,12 +232,10 @@ generic_stop_cpus(cpumask_t map, u_int type) /* spin */ cpu_spinwait(); i++; -#ifdef DIAGNOSTIC - if (i == 100000) { + if (i == 100000000) { printf("timeout stopping cpus\n"); break; } -#endif } stopping_cpu = NOCPU; > Not sure about MIPS, etc. Attilio has since significantly > improved our shutdown behaviour -- initially, the switch to NMI IPIs broke > other things (because certain IPIs then improperly preempted threads holding > spinlocks), but that pretty much all seems worked out now. -- Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Sat Jun 4 09:11:10 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 773D0106566C; Sat, 4 Jun 2011 09:11:10 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 532D68FC08; Sat, 4 Jun 2011 09:11:10 +0000 (UTC) Received: from [192.168.2.112] (host86-173-95-198.range86-173.btcentralplus.com [86.173.95.198]) by cyrus.watson.org (Postfix) with ESMTPSA id 7022346B2E; Sat, 4 Jun 2011 05:11:09 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: "Robert N. M. Watson" In-Reply-To: <4DE9EB61.3000006@FreeBSD.org> Date: Sat, 4 Jun 2011 10:11:07 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <8AA26086-DA05-4DDA-9973-AE57328E2C81@FreeBSD.org> References: <4DE8FA2E.4030202@FreeBSD.org> <5E4D0F56-4338-4157-8BC6-17EE2831725F@FreeBSD.org> <4DE9EB61.3000006@FreeBSD.org> To: Andriy Gapon X-Mailer: Apple Mail (2.1084) Cc: freebsd-current@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: Re: [poll / rfc] kdb_stop_cpus X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jun 2011 09:11:10 -0000 On 4 Jun 2011, at 09:22, Andriy Gapon wrote: > on 03/06/2011 20:57 Robert N. M. Watson said the following: >>=20 >> On 3 Jun 2011, at 16:13, Andriy Gapon wrote: >>=20 >>> I wonder if anybody uses kdb_stop_cpus with non-default value. If, = yes, I >>> am very interested to learn about your usecase for it. >>=20 >> The issue that prompted the sysctl was non-NMI IPIs being used to = enter the >> debugger or reboot following a core hanging with interrupts disabled. = With >> the switch to NMI IPIs in some of those circumstances, life is better = -- at >> least, on hardware that supports non-maskable IPIs. I seem to recall = sparc64 >> doesn't, however? >=20 > Seems to be so as Nathan has also pointed out for PPC. > For this I also plan the following change: >=20 > commit 458ebd9aca7e91fc6e0825c727c7220ab9f61016 >=20 > generic_stop_cpus: move timeout detection code from under = DIAGNOSTIC >=20 > ... and also increase it a bit. > IMO it's better to detect and report the (rather serious) condition = and > allow a system to proceed somehow rather than be stuck in an = endless > loop. Agreed on detecting and reporting. It would be good to confirm that it = works in practice, however, and also that there are no false positives. = I'm not sure what the best test scenarios are for that. Robert From owner-freebsd-current@FreeBSD.ORG Sat Jun 4 09:40:09 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 02320106566B; Sat, 4 Jun 2011 09:40:08 +0000 (UTC) (envelope-from buganini@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id B0BA28FC16; Sat, 4 Jun 2011 09:40:08 +0000 (UTC) Received: by iyj12 with SMTP id 12so3070998iyj.13 for ; Sat, 04 Jun 2011 02:40:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=NZ8BefQ5MN3KyIT7SERMxH0qLxu5uoxJnC20HfPhIbI=; b=rUCR4xdoCD/JTQRVLA+33Jt+poHIufte2jYn7REJIi3c1i0t40tuxCuBONZUaj04Iz yNgDFk+ZWMLWSHxy5oJZHs59lKy9wP6tKngE7u1qHQa0y15cSfGcjAcZpDnD1zQFrkgq aKT+FfjvT96cu9RaE9aj/ejptBQO8NQm+ngoM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=tp62KUVo1xLEnVRrS2ORYL9d5ImzdorToWknDrJXxDepZodGvXlaq0TnTs3SK7N/Gi kxSVJo7wbbOfEqkf6f7eWmQyl+GQMaOobNv9Te9YTJirupXxYlsEe39WA5q4j84Bbl59 05cSzsQ/+NfP65w/bEKocdqreV1mG5/rjXkPM= MIME-Version: 1.0 Received: by 10.231.67.74 with SMTP id q10mr3995408ibi.25.1307178614496; Sat, 04 Jun 2011 02:10:14 -0700 (PDT) Received: by 10.231.35.75 with HTTP; Sat, 4 Jun 2011 02:10:14 -0700 (PDT) Date: Sat, 4 Jun 2011 17:10:14 +0800 Message-ID: From: Buganini To: FreeBSD Current , freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 Cc: Subject: [RFC] rcexecr: rcorder in parallel X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jun 2011 09:40:09 -0000 https://github.com/buganini/rcexecr Currently it is able to determine the exec/wait order There are something I haven't digged in deeply in the "self modification" part. patches/ideas are welcome. Regards, Buganini From owner-freebsd-current@FreeBSD.ORG Sat Jun 4 11:23:08 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A33B91065673 for ; Sat, 4 Jun 2011 11:23:08 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay04.ispgateway.de (smtprelay04.ispgateway.de [80.67.31.31]) by mx1.freebsd.org (Postfix) with ESMTP id 636BF8FC0A for ; Sat, 4 Jun 2011 11:23:08 +0000 (UTC) Received: from [78.35.65.229] (helo=fabiankeil.de) by smtprelay04.ispgateway.de with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.68) (envelope-from ) id 1QSohr-0002Qc-HC for freebsd-current@freebsd.org; Sat, 04 Jun 2011 13:07:52 +0200 Date: Sat, 4 Jun 2011 13:07:56 +0200 From: Fabian Keil To: freebsd-current@freebsd.org Message-ID: <20110604130756.1d3b71ba@fabiankeil.de> In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/I44SqPU4/HIKzH2CTFHypNO"; protocol="application/pgp-signature" X-Df-Sender: 775067 Subject: Re: [PATCH] Add the infrastructure for supporting an infinite number of CPUs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jun 2011 11:23:08 -0000 --Sig_/I44SqPU4/HIKzH2CTFHypNO Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Attilio Rao wrote: > Current maximum number of CPUs supported by the FreeBSD kernel is 32. > That number cames from indirectly by the fact that we have a cpumask_t > type, representing a mask of CPUs, which is an unsigned int right now. > I then made a patch that removes the cpumask_t type and uses cpuset_t > type for characterizing a generic mask of CPUs: > http://www.freebsd.org/~attilio/largeSMP/largeSMP-patchset-beta-0.diff =20 > I really need to commit this patch before code slush happens, thus I > plan to commit it on June 7th, if no one reports bugs or can make good > point on his reviews. Please note that the patch has been greatly > tested and reviewed on all FreeBSD tier-1 and tier-2 architectures. > Anyway more testing and reviews are welcome to happen. In the few days I've been using the patch, I haven't experienced any problems on a dual core AMD64 system using SCHED_ULE. I'm aware that two isn't that close to infinity, though. Not sure if it matters, but I noticed two places where the CPU_ABSENT() macro could be used, but isn't. There may be more, but as someone unfamiliar with the code it wasn't obvious to me if there are places where "all_cpus" and "cpus" are equal. Of course there also might be a difference in semantics that I'm not gettin= g. Fabian --Sig_/I44SqPU4/HIKzH2CTFHypNO Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (FreeBSD) iEYEARECAAYFAk3qEg8ACgkQBYqIVf93VJ273ACdElM9wRQUM3tpoIFtRJ8kxB5a UFUAmgOMWymGdVTkWIq9jn0+BTR4XQK2 =nx8z -----END PGP SIGNATURE----- --Sig_/I44SqPU4/HIKzH2CTFHypNO-- From owner-freebsd-current@FreeBSD.ORG Sat Jun 4 12:07:28 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CBFF51065670; Sat, 4 Jun 2011 12:07:28 +0000 (UTC) (envelope-from julien.laffaye@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id 75A6B8FC17; Sat, 4 Jun 2011 12:07:28 +0000 (UTC) Received: by ywf7 with SMTP id 7so1618568ywf.13 for ; Sat, 04 Jun 2011 05:07:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=WinnB7iO3GHWBHYPTP9fto4INdwbKxyadCxq3FDN0dU=; b=KjLiYsmrm8VoeVKDaUGL4MYYvxLvh/s/KvfGroADdwl7jKKnbrSOWfIac7XB/FT4Kv 675ip+6rOUsNwW51kv30bzBFu4d6vuIfmintiTvQYCX38c+AoLRBIHbIjHR+Zmy+ttB3 E0P3XLfgok07JP9Aqs+Kprt3LKyD3irkbdibc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=S0XUBIngcq3k1I5uh8kHaY/YZPjIInV/orLH942JCfmwU1DvGWny4Btp7kHQFiTh8j MjWN4s9QYyP/96oBiTDKcXAbUyhw7+zoejuG+M67UTKcxA/GixMO0jJVl6MY+YBTEwKo f5BZdAZObI6bs0pwP9VVuMkpraONkTmMCdsMM= MIME-Version: 1.0 Received: by 10.236.77.34 with SMTP id c22mr3799763yhe.120.1307187938140; Sat, 04 Jun 2011 04:45:38 -0700 (PDT) Sender: julien.laffaye@gmail.com Received: by 10.236.108.171 with HTTP; Sat, 4 Jun 2011 04:45:37 -0700 (PDT) In-Reply-To: References: Date: Sat, 4 Jun 2011 12:45:37 +0100 X-Google-Sender-Auth: au0E_jqemx_eHg9qRHBz2VolgLA Message-ID: From: Julien Laffaye To: Buganini Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-hackers@freebsd.org, FreeBSD Current Subject: Re: [RFC] rcexecr: rcorder in parallel X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jun 2011 12:07:28 -0000 On Sat, Jun 4, 2011 at 10:10 AM, Buganini wrote: > https://github.com/buganini/rcexecr > > Currently it is able to determine the exec/wait order > > There are something I haven't digged in deeply in the "self modification" part. > > patches/ideas are welcome. Hello, Thanks for doing that! You should use kqueue(2) instead of waitpid(2) so that you can efficiently monitor a pool of processes. See pwait(1) for an example. Regards, Julien From owner-freebsd-current@FreeBSD.ORG Sat Jun 4 12:13:35 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C4003106564A; Sat, 4 Jun 2011 12:13:35 +0000 (UTC) (envelope-from dickey@saltmine.radix.net) Received: from saltmine.radix.net (saltmine.radix.net [207.192.128.40]) by mx1.freebsd.org (Postfix) with ESMTP id 8628B8FC0A; Sat, 4 Jun 2011 12:13:35 +0000 (UTC) Received: from saltmine.radix.net (localhost [127.0.0.1]) by saltmine.radix.net (8.12.2/8.12.2) with ESMTP id p54BqVuM023376; Sat, 4 Jun 2011 07:52:33 -0400 (EDT) Received: (from dickey@localhost) by saltmine.radix.net (8.12.2/8.12.2/Submit) id p54BqVj5023375; Sat, 4 Jun 2011 07:52:31 -0400 (EDT) Date: Sat, 4 Jun 2011 07:52:31 -0400 From: Thomas Dickey To: Andrey Chernov , Ruslan Ermilov , current@freebsd.org Message-ID: <20110604115231.GA22970@saltmine.radix.net> References: <20110603144859.GA73084@lo0.su> <20110604015449.GA43316@vniz.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="NzB8fVQJ5HfG6fxh" Content-Disposition: inline In-Reply-To: <20110604015449.GA43316@vniz.net> User-Agent: Mutt/1.3.27i Cc: Subject: Re: [HEADS UP] color and page width support in man(1) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jun 2011 12:13:35 -0000 --NzB8fVQJ5HfG6fxh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jun 04, 2011 at 05:54:49AM +0400, Andrey Chernov wrote: > On Fri, Jun 03, 2011 at 02:48:59PM +0000, Ruslan Ermilov wrote: > > On a freshly installed -CURRENT, to view a colorized manpage in color > > and in full terminal width, try this: > >=20 > > env MANCOLOR=3Dyes MANWIDTH=3Dtty man grotty > >=20 >=20 > SGR presence can be easily autodetected analyzing termcap capibilities=20 > (for isatty() case). true - but grotty doesn't pay any attention to the termcap or terminfo database. --=20 Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net --NzB8fVQJ5HfG6fxh Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (SunOS) Comment: For info see http://www.gnupg.org iD8DBQFN6hx9tIqByHxlDocRAiK4AKCUuYGd0tGVnzTCLe31psrFy1JyJgCfWTzY SScUOYt4XUoLPcriX4QA/f4= =odcY -----END PGP SIGNATURE----- --NzB8fVQJ5HfG6fxh-- From owner-freebsd-current@FreeBSD.ORG Sat Jun 4 12:27:04 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F088B1065674; Sat, 4 Jun 2011 12:27:04 +0000 (UTC) (envelope-from jilles@stack.nl) Received: from mx1.stack.nl (relay04.stack.nl [IPv6:2001:610:1108:5010::107]) by mx1.freebsd.org (Postfix) with ESMTP id 9109A8FC1A; Sat, 4 Jun 2011 12:27:04 +0000 (UTC) Received: from turtle.stack.nl (turtle.stack.nl [IPv6:2001:610:1108:5010::132]) by mx1.stack.nl (Postfix) with ESMTP id 853E71DD789; Sat, 4 Jun 2011 14:27:03 +0200 (CEST) Received: by turtle.stack.nl (Postfix, from userid 1677) id 796E6173E4; Sat, 4 Jun 2011 14:27:03 +0200 (CEST) Date: Sat, 4 Jun 2011 14:27:03 +0200 From: Jilles Tjoelker To: Julien Laffaye Message-ID: <20110604122703.GB33796@stack.nl> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-hackers@freebsd.org, Buganini , FreeBSD Current Subject: Re: [RFC] rcexecr: rcorder in parallel X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jun 2011 12:27:05 -0000 On Sat, Jun 04, 2011 at 12:45:37PM +0100, Julien Laffaye wrote: > On Sat, Jun 4, 2011 at 10:10 AM, Buganini wrote: > > https://github.com/buganini/rcexecr > > Currently it is able to determine the exec/wait order > > There are something I haven't digged in deeply in the "self > > modification" part. > > patches/ideas are welcome. > Thanks for doing that! Yes. > You should use kqueue(2) instead of waitpid(2) so that you can > efficiently monitor a pool of processes. > See pwait(1) for an example. Hmm, I don't think kqueue() should be used here. Its main advantage is that it works regardless of parent-child relationships, but that advantage is not relevant here. On the other hand, waitpid() is still necessary to get rid of the zombies. Furthermore, waitpid() is standard while kqueue() is not, and I think non-standard interfaces should only be used if they provide a real benefit above standard interfaces. The current approach with waitpid() for specific processes should be good enough for a proof of concept. It will keep zombies longer than necessary, particularly for things that are not explicitly depended on. To avoid this, use waitpid(-1, ...) and maintain more tracking for processes that have already terminated. -- Jilles Tjoelker From owner-freebsd-current@FreeBSD.ORG Sat Jun 4 12:46:18 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3EEFD106566C; Sat, 4 Jun 2011 12:46:18 +0000 (UTC) (envelope-from inyaoo@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 5F3138FC13; Sat, 4 Jun 2011 12:46:17 +0000 (UTC) Received: by wwc33 with SMTP id 33so2427392wwc.31 for ; Sat, 04 Jun 2011 05:46:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:to:cc:subject:references:date:in-reply-to :message-id:user-agent:mime-version:content-type; bh=IfPeXXgl0FglUVGmv9idgRjULI/cnZp8OfXGGoXvX20=; b=hnOjPXYJ6tUBOrmzMZA8XrzKNxPRLmLIksBoTGMSZxs8rMol8U05weZ6n+0yJzFCMW nQ5ltHce3aOTK89nX4ux8Iv3nNnONbnDMqUlZooJvNsrUm2IimBQvIQRSZh5yTS+kvV2 /op1hQZR0a5/dv8RYRB3G5g71L9/iKPVGS4ck= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-type; b=L9cajjUP8hrStX48t92+XZyLNhZRGRAu38EMAfGGHQXT9qELLZupNi+Z9cQgOKR2hY u3Rh6xPerxsYjx+dbTrd8QVz2TCeC8Nli9eDDAf2l77AHaspkSEfnLcJj3D2fKB5XUSG /WME2WnsU0pKO1Eoz2Eczefd21kua7pLq7PrQ= Received: by 10.216.61.77 with SMTP id v55mr476445wec.114.1307191575441; Sat, 04 Jun 2011 05:46:15 -0700 (PDT) Received: from localhost (lvps178-77-103-137.dedicated.hosteurope.de [178.77.103.137]) by mx.google.com with ESMTPS id y3sm1314833wec.10.2011.06.04.05.46.12 (version=SSLv3 cipher=OTHER); Sat, 04 Jun 2011 05:46:14 -0700 (PDT) From: Pan Tsu To: Aryeh Friedman References: Date: Sat, 04 Jun 2011 16:46:06 +0400 In-Reply-To: (Aryeh Friedman's message of "Fri, 3 Jun 2011 20:02:56 -0400") Message-ID: <867h91ojch.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain Cc: FreeBSD Current , FreeBSD Ports ML Subject: Re: 8-STABLE /usr/include/utmp.h and tmpx X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jun 2011 12:46:18 -0000 Aryeh Friedman writes: > Some time in the last 2 weeks (I am sure when) a commit caused many > ports that assume a "standard" utmp/utmp.x to break for example > x11-toolkits/vte produces: I guess it's a user error, utmpx.h and utmp.h shouldn't both be present. See similar issue http://lists.freebsd.org/pipermail/freebsd-ports/2010-September/063733.html > gnome-pty-helper.c:497: warning: passing argument 4 of 'pty_add' > discards qualifiers from pointer target type > mv -f .deps/gnome-pty-helper.Tpo .deps/gnome-pty-helper.Po > cc -DHAVE_CONFIG_H -I. -I/usr/local/include -O2 -pipe > -march=prescott -fno-strict-aliasing -MT gnome-utmp.o -MD -MP -MF > .deps/gnome-utmp.Tpo -c -o gnome-utmp.o gnome-utmp.c > gnome-utmp.c: In function 'write_login_record': > gnome-utmp.c:367: warning: passing argument 1 of 'login' from > incompatible pointer type > gnome-utmp.c:374: error: 'struct utmpx' has no member named 'ut_name' If you're on /stable/8 try removing leftover includes from /head by reinstalling /usr/include, e.g. $ mv /usr/include /usr/include.old $ make distrib-dirs installincludes -C/usr/src # a list of files that shouldn't be there $ mtree -klink -cinp /usr/include.old >old.mtree $ mtree -klink -cinp /usr/include >new.mtree $ diff -u old.mtree new.mtree struct utmpx shouldn't be used on /stable/8 as there is no utmpx.h. # from vte-0.26.2/gnome-pty-helper/acinclude.m4 AC_CHECK_HEADERS(sys/time.h utmp.h utmpx.h) if test "$ac_cv_header_utmpx_h" = "yes"; then AC_DEFINE(UTMP,[struct utmpx],[Define to the name of a structure which holds utmp data.]) else AC_DEFINE(UTMP,[struct utmp],[Define to the name of a structure which holds utmp data.]) fi And if you're on /head then stale utmp.h should be removed, e.g. $ make delete-old -C/usr/src making the port use ut_user instead of ut_name. > This is not the only port that has the issue but it is the only one I > remember off the top of my head (I manually fixed a few others) From owner-freebsd-current@FreeBSD.ORG Sat Jun 4 13:40:58 2011 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BC0F5106564A; Sat, 4 Jun 2011 13:40:58 +0000 (UTC) (envelope-from mike@reifenberger.com) Received: from mail-out.m-online.net (mail-out.m-online.net [212.18.0.10]) by mx1.freebsd.org (Postfix) with ESMTP id 45A808FC16; Sat, 4 Jun 2011 13:40:57 +0000 (UTC) Received: from frontend1.mail.m-online.net (frontend1.mail.intern.m-online.net [192.168.8.180]) by mail-out.m-online.net (Postfix) with ESMTP id 59519188A182; Sat, 4 Jun 2011 15:40:56 +0200 (CEST) Received: from localhost (dynscan1.mnet-online.de [192.168.8.164]) by mail.m-online.net (Postfix) with ESMTP id A43941C000AB; Sat, 4 Jun 2011 15:40:56 +0200 (CEST) X-Virus-Scanned: amavisd-new at mnet-online.de Received: from mail.mnet-online.de ([192.168.8.180]) by localhost (dynscan1.mail.m-online.net [192.168.8.164]) (amavisd-new, port 10024) with ESMTP id Ral+sQ-W+npA; Sat, 4 Jun 2011 15:40:54 +0200 (CEST) Received: from mail.reifenberger.com (ppp-93-104-32-7.dynamic.mnet-online.de [93.104.32.7]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.mnet-online.de (Postfix) with ESMTPS; Sat, 4 Jun 2011 15:40:53 +0200 (CEST) Received: by mail.reifenberger.com (Postfix, from userid 1001) id 3A12E3107D; Sat, 4 Jun 2011 15:40:53 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mail.reifenberger.com (Postfix) with ESMTP id 1468B3107A; Sat, 4 Jun 2011 15:40:52 +0200 (CEST) Date: Sat, 4 Jun 2011 15:40:52 +0200 (CEST) From: Michael Reifenberger To: Gavin Atkinson In-Reply-To: <1307116512.60345.8.camel@buffy.york.ac.uk> Message-ID: References: <1307116512.60345.8.camel@buffy.york.ac.uk> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=UTF-8; format=flowed Cc: Garrett Cooper , pjd@FreeBSD.org, FreeBSD-Current Subject: Re: mount root from zfs fails under current with "error 6" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jun 2011 13:40:58 -0000 On Fri, 3 Jun 2011, Gavin Atkinson wrote: ... >> maybe I found something: >> After setting vfs.zfs.debug=1 I got two new verbose bootlogs: >> http://people.freebsd.org/~mr/boot_fail2.txt >> http://people.freebsd.org/~mr/boot_success2.txt >> >> As you can see, in the failing case ZFS tries to attach to ada[0123] >> whereas in the succeeding case ZFS attaches to ada[0123]p3 (which are the >> correct devices) > > Can you try setting kern.geom.part.check_integrity=0 ? > Preparing a new r222654 kernel and booting with kern.geom.part.check_integrity=0 didn't cure anything. See http://people.freebsd.org/~mr/boot_3.txt for a "boot -v" using set kern.geom.label.debug=1 additionaly But reverting /sys/geom to r221381 allows to boot. See http://people.freebsd.org/~mr/boot_4.txt for a "boot -s" using set vfs.zfs.debug=1 set kern.geom.debugflags=4 set kern.geom.label.debug=1 additionaly. So the problem seems to be related to the recent geom changes... Bye/2 --- Michael Reifenberger Michael@Reifenberger.com http://www.Reifenberger.com From owner-freebsd-current@FreeBSD.ORG Sat Jun 4 14:54:32 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4A5481065672; Sat, 4 Jun 2011 14:54:32 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 217538FC17; Sat, 4 Jun 2011 14:54:32 +0000 (UTC) Received: from [192.168.2.112] (host86-173-95-198.range86-173.btcentralplus.com [86.173.95.198]) by cyrus.watson.org (Postfix) with ESMTPSA id D8CBA46B03; Sat, 4 Jun 2011 10:54:29 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: multipart/mixed; boundary=Apple-Mail-7-327068992 From: "Robert N. M. Watson" In-Reply-To: <20110604143043.GE17764@nereid> Date: Sat, 4 Jun 2011 15:54:26 +0100 Message-Id: <64903CD6-7AED-4BF6-9FDF-B6748690EA8A@FreeBSD.org> References: <201105300943.p4U9htjI070096@svn.freebsd.org> <20110604143043.GE17764@nereid> To: Kristof Provost X-Mailer: Apple Mail (2.1084) Cc: "freebsd-current@FreeBSD.org Current" Subject: Divert socket problem (was: Re: svn commit: r222488 - in head/sys: contrib/pf/net netinet netinet/ipfw netinet6) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jun 2011 14:54:32 -0000 --Apple-Mail-7-327068992 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 4 Jun 2011, at 15:30, Kristof Provost wrote: > div_bind probably also needs to surround the call to in_pcbbind with > INP_HASHW(UN)LOCK(...) >=20 > I'm currently running 222680. I've only now seen the issue, but I've = also > just now activated INVARIANTS. Hi Kristof: Thanks for the detailed report, and yes, it looks like that is exactly = what is required. Could you try the attached patch? Robert --Apple-Mail-7-327068992 Content-Disposition: attachment; filename=20110604-divert-fix.diff Content-Type: application/octet-stream; x-unix-mode=0644; name="20110604-divert-fix.diff" Content-Transfer-Encoding: 7bit IP divert sockets use their inpcbinfo for port reservation, although not for lookup. I missed its call to in_pcbbind() when preparing previous patches, which would lead to a lock assertion failure (although problem not an actual race condition due to global pcbinfo locks providing required synchronisation -- in this particular case only). This change adds the missing locking of the pcbhash lock. (Existing comments in the ipdivert code question the need for using the global hash to manage the namespace, as really it's a simple port namespace and not an address/port namespace. Also, although in_pcbbind is used to manage reservations, the hash tables aren't used for lookup. It might be a good idea to make them use hashed lookup, or to use a different reservation scheme.) Reviewed by: bz Reported by: Kristof Provost Sponsored by: Juniper Networks Index: ip_divert.c =================================================================== --- ip_divert.c (revision 222672) +++ ip_divert.c (working copy) @@ -530,7 +530,9 @@ ((struct sockaddr_in *)nam)->sin_addr.s_addr = INADDR_ANY; INP_INFO_WLOCK(&V_divcbinfo); INP_WLOCK(inp); + INP_HASH_WLOCK(&V_divcbinfo); error = in_pcbbind(inp, nam, td->td_ucred); + INP_HASH_WUNLOCK(&V_divcbinfo); INP_WUNLOCK(inp); INP_INFO_WUNLOCK(&V_divcbinfo); return error; --Apple-Mail-7-327068992-- From owner-freebsd-current@FreeBSD.ORG Sat Jun 4 16:06:40 2011 Return-Path: Delivered-To: current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 642F5106564A; Sat, 4 Jun 2011 16:06:40 +0000 (UTC) (envelope-from sobomax@sippysoft.com) Received: from mail.sippysoft.com (mail.sippysoft.com [4.59.13.245]) by mx1.freebsd.org (Postfix) with ESMTP id 0348B8FC08; Sat, 4 Jun 2011 16:06:40 +0000 (UTC) Received: from s0106005004e13421.vs.shawcable.net ([70.71.175.212] helo=[192.168.1.79]) by mail.sippysoft.com with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from ) id 1QStN0-000Bkf-PC; Sat, 04 Jun 2011 09:06:38 -0700 Message-ID: <4DEA5807.2020605@FreeBSD.org> Date: Sat, 04 Jun 2011 09:06:31 -0700 From: Maxim Sobolev Organization: Sippy Software, Inc. User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: Mikolaj Golub References: <4DDD4890.70604@FreeBSD.org> <86hb8du5fo.fsf@kopusha.home.net> In-Reply-To: <86hb8du5fo.fsf@kopusha.home.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: sobomax@sippysoft.com X-ssp-trusted: yes Cc: Pawel Jakub Dawidek , "current@freebsd.org" , daniel@digsys.bg Subject: Re: Weird issue with hastd(8) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jun 2011 16:06:40 -0000 Mikolaj, Upon further investigation it appears that there is a logic mistake in hastd's server/client buffering code. I've just applied a fix and it immediately solved the issue for me. Please see r222688 for details. I plan to MFC it ASAP, as otherwise hastd is not functional when compression is enabled. -Maxim From owner-freebsd-current@FreeBSD.ORG Sat Jun 4 22:34:00 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D5C781065672; Sat, 4 Jun 2011 22:34:00 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from mail-yi0-f54.google.com (mail-yi0-f54.google.com [209.85.218.54]) by mx1.freebsd.org (Postfix) with ESMTP id 5916D8FC12; Sat, 4 Jun 2011 22:34:00 +0000 (UTC) Received: by yie12 with SMTP id 12so1749246yie.13 for ; Sat, 04 Jun 2011 15:33:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=bVYvCO+7Urv6VxMt/s9qUDeLTZWwuPQrQ/43cfS5keA=; b=dwo0wj30xjiulUsgL9Hd4+ElELA2NSkyclSIwopt2XU7E7y53vwWiyhS4H1NipFPmY dk4XQ1gMrQEEp3VFKfuJR8TZYnrMFYrbUUmTxuErYYWfCm8j1f5z8hDVgHxkSbRba5rU ZCeaHRbrmYuJmF6Uw73lCxbF3ao+vn/7RXHaE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=XGl3akqaBHhaxLvjmxoWlI3ywuWEWyXVoOBI0ZxZeAqqRyDtc3FADcEGGLHjRF7IZV E05i6al0aRl0Wz+XYENa53AwHSeV4mCzV0pMAMdgW6jLz0j/pDaVghgU4/+kcWuFJrDj FqHgchsYNlRe4Wuj9AD2fQtpRIXxMRzv+disU= MIME-Version: 1.0 Received: by 10.236.154.105 with SMTP id g69mr4320048yhk.505.1307226839507; Sat, 04 Jun 2011 15:33:59 -0700 (PDT) Sender: asmrookie@gmail.com Received: by 10.236.103.136 with HTTP; Sat, 4 Jun 2011 15:33:59 -0700 (PDT) In-Reply-To: <4DE8FD83.6030503@freebsd.org> References: <4DE8FA2E.4030202@FreeBSD.org> <4DE8FD83.6030503@freebsd.org> Date: Sat, 4 Jun 2011 18:33:59 -0400 X-Google-Sender-Auth: ni--62nmh3sCfELNT79lJf4LNOA Message-ID: From: Attilio Rao To: Nathan Whitehorn Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org, Andriy Gapon Subject: Re: [poll / rfc] kdb_stop_cpus X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jun 2011 22:34:01 -0000 2011/6/3 Nathan Whitehorn : > On 06/03/11 10:13, Andriy Gapon wrote: >> >> I wonder if anybody uses kdb_stop_cpus with non-default value. >> If, yes, I am very interested to learn about your usecase for it. >> >> I think that the default kdb behavior is the correct one, so it doesn't >> make sense >> to have a knob to turn on incorrect behavior. >> But I may be missing something obvious. >> >> The comment in the code doesn't really satisfy me: >> /* >> =C2=A0* Flag indicating whether or not to IPI the other CPUs to stop the= m on >> =C2=A0* entering the debugger. =C2=A0Sometimes, this will result in a de= adlock as >> =C2=A0* stop_cpus() waits for the other cpus to stop, so we allow it to = be >> =C2=A0* disabled. =C2=A0In order to maximize the chances of success, use= a hard >> =C2=A0* stop for that. >> =C2=A0*/ >> >> The hard stop should be sufficiently mighty. >> Yes, I am aware of supposedly extremely rare situations where a deadlock >> could >> happen even when using hard stop. =C2=A0But I'd rather fix that than hav= e this >> switch. >> >> Oh, the commit message (from 2004) explains it: >>> >>> Add a new sysctl, debug.kdb.stop_cpus, which controls whether or not we >>> attempt to IPI other cpus when entering the debugger in order to stop >>> them while in the debugger. =C2=A0The default remains to issue the stop= ; >>> however, that can result in a hang if another cpu has interrupts disabl= ed >>> and is spinning, since the IPI won't be received and the KDB will wait >>> indefinitely. =C2=A0We probably need to add a timeout, but this is a us= eful >>> stopgap in the mean time. >> >> But that was before we started using hard stop in this context (in 2009)= . > > Some non-x86 platforms (e.g. PPC) don't support real NMIs, and so this st= ill > applies. Well, if I get Andriy's proposal right, he just wants to trim off the possibility to not stop the CPUs on entering KDB. I'm not entirely sure why there is a sysctl for disabling that and I really don't want it. Note that the missing of the NMI/privileged Interrupt is not going to be a factor on this request, unless you are worried a lot by the easy deadlock that a normal stop operation may lead. If that is the case, I think that the upcoming work on skipping locking during KDB/panic entering is going to help a lot for this case. At that point removing the possibility to turn off CPU stopping will be a good idea, IMHO. Attilio --=20 Peace can only be achieved by understanding - A. Einstein From owner-freebsd-current@FreeBSD.ORG Sat Jun 4 22:35:29 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6A086106564A; Sat, 4 Jun 2011 22:35:29 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id E01988FC14; Sat, 4 Jun 2011 22:35:28 +0000 (UTC) Received: by gyg13 with SMTP id 13so1746480gyg.13 for ; Sat, 04 Jun 2011 15:35:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=lrZ1edEjVtym7htofHoC62s2wKoryNttfZYqcVgCQNw=; b=Tfxzha2AtNzeJhIxQo/uUNqYdTbfCnTw+MGvgF/W7SnZJFiaV553jsCDxWMSmH6pV7 qdm0mXCvztMVlF1efoDkxU7AW7Qv5YVwMn/EeHJpIvClWNPaDpCifq98efdOETHxoVDe nfFEFphj0RDtd9TFb+DRWrzSBPsvTuJ40TT2Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=XuVKSZFEec+LDEls2jQeS8/ksUehKoEgpBDni2/pTp+oCR51EefijU7L36vexim0XR Hf3VX1U8WH38qpHtPqPuN2KNrv4vRksEqNmVlI5yJyf1KH6ZyxF5ExyjYqwVZvnG+Xc+ 622Ue8WwindmlktUNeCxLwUArSPwJVRpHyV4U= MIME-Version: 1.0 Received: by 10.236.161.194 with SMTP id w42mr4157724yhk.237.1307226928163; Sat, 04 Jun 2011 15:35:28 -0700 (PDT) Sender: asmrookie@gmail.com Received: by 10.236.103.136 with HTTP; Sat, 4 Jun 2011 15:35:28 -0700 (PDT) In-Reply-To: <4DE9EB61.3000006@FreeBSD.org> References: <4DE8FA2E.4030202@FreeBSD.org> <5E4D0F56-4338-4157-8BC6-17EE2831725F@FreeBSD.org> <4DE9EB61.3000006@FreeBSD.org> Date: Sat, 4 Jun 2011 18:35:28 -0400 X-Google-Sender-Auth: Iu3VIueuqAZNmZQIBs5oUET-vGQ Message-ID: From: Attilio Rao To: Andriy Gapon Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org, freebsd-current@freebsd.org, "Robert N. M. Watson" Subject: Re: [poll / rfc] kdb_stop_cpus X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jun 2011 22:35:29 -0000 2011/6/4 Andriy Gapon : > on 03/06/2011 20:57 Robert N. M. Watson said the following: >> >> On 3 Jun 2011, at 16:13, Andriy Gapon wrote: >> >>> I wonder if anybody uses kdb_stop_cpus with non-default value. If, yes,= I >>> am very interested to learn about your usecase for it. >> >> The issue that prompted the sysctl was non-NMI IPIs being used to enter = the >> debugger or reboot following a core hanging with interrupts disabled. Wi= th >> the switch to NMI IPIs in some of those circumstances, life is better --= at >> least, on hardware that supports non-maskable IPIs. I seem to recall spa= rc64 >> doesn't, however? > > Seems to be so as Nathan has also pointed out for PPC. > For this I also plan the following change: > > commit 458ebd9aca7e91fc6e0825c727c7220ab9f61016 > > =C2=A0 =C2=A0generic_stop_cpus: move timeout detection code from under DI= AGNOSTIC > > =C2=A0 =C2=A0... and also increase it a bit. > =C2=A0 =C2=A0IMO it's better to detect and report the (rather serious) co= ndition and > =C2=A0 =C2=A0allow a system to proceed somehow rather than be stuck in an= endless > =C2=A0 =C2=A0loop. > > diff --git a/sys/kern/subr_smp.c b/sys/kern/subr_smp.c > index ae52f4b..4bd766b 100644 > --- a/sys/kern/subr_smp.c > +++ b/sys/kern/subr_smp.c > @@ -232,12 +232,10 @@ generic_stop_cpus(cpumask_t map, u_int type) > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0/* spin */ > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0cpu_spinwait(); > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0i++; > -#ifdef DIAGNOSTIC > - =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 if (i =3D=3D 100000) { > + =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 if (i =3D=3D 100000000= ) { > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0printf("timeout stopping cpus\n"); > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0break; > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0} > -#endif > =C2=A0 =C2=A0 =C2=A0 =C2=A0} > > =C2=A0 =C2=A0 =C2=A0 =C2=A0stopping_cpu =3D NOCPU; I'd also add the ability, once the deadlock is detected, to break in KDB, and put that under DIAGNOSTIC. I had such a patch and I used it to debug some deadlocks on shutdown code, but now it seems I can't find it anymore. Attilio --=20 Peace can only be achieved by understanding - A. Einstein