From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 25 00:47:09 2012 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 587F1264 for ; Sun, 25 Nov 2012 00:47:09 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from monday.kientzle.com (99-115-135-74.uvs.sntcca.sbcglobal.net [99.115.135.74]) by mx1.freebsd.org (Postfix) with ESMTP id 2942C8FC12 for ; Sun, 25 Nov 2012 00:47:08 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id qAP0l1XV028979; Sun, 25 Nov 2012 00:47:01 GMT (envelope-from kientzle@freebsd.org) Received: from [192.168.2.143] (CiscoE3000 [192.168.1.65]) by kientzle.com with SMTP id 6s34cm565ydaarznjgf48vfngs; Sun, 25 Nov 2012 00:47:01 +0000 (UTC) (envelope-from kientzle@freebsd.org) Subject: Re: FreeBSD on RaspberryPi Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=windows-1252 From: Tim Kientzle In-Reply-To: Date: Sat, 24 Nov 2012 16:47:00 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: References: <31C904E6-F230-4187-AE32-F9A7B1A7C38E@freebsd.org> <4A5E03E5-3295-4FD4-9A06-7D1C4E9E0C12@freebsd.org> To: Alexander Yerenkow X-Mailer: Apple Mail (2.1283) Cc: FreeBSD Hackers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Nov 2012 00:47:09 -0000 On Nov 24, 2012, at 11:13 AM, Alexander Yerenkow wrote: >=20 >=20 > 2012/11/24 Tim Kientzle > On Nov 7, 2012, at 8:09 AM, Alexander Yerenkow wrote: >=20 > > > Such experiments was tried by me and others in August; I got = framebuffer worked in rca/hdmi; =85 >=20 > On Nov 8, 2012, at 11:12 PM, Alexander Yerenkow wrote: >=20 > > It was plain current with plain RPIB kernel config, and for graphic = you should uncomment there partition about sysconsole; serial then = disabled; > > Also, if you want ethernet - it's ue device, which also worked, but = produced hangs for me in past (Hans IIRC already fixed.this). > > I'll have some time this weekend, feel free to contact me by gtalk = or else, I will play around with my rpi with both serials and vide = modes. >=20 > Alexander, >=20 > I tried uncommenting the 'sc' entries in the RPI-B kernel > config that's in -CURRENT right now. >=20 > All entries, right? Yes, I uncommented all entries. > And how do you booting, via usb-flash, or via SD card? Via SD-card. I'm using the image from here: = http://people.freebsd.org/~kientzle/FreeBSD-RPI-B-r242362-2012-10-30.img.x= z and swapping out the kernel. > I'll build now CURRENT, will look if I got same.=20 Thanks. I'd appreciate knowing whether it works for you. If you can get it to work, I'd appreciate any details you can give. Cheers, Tim From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 25 04:02:01 2012 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CFFAAA85; Sun, 25 Nov 2012 04:02:01 +0000 (UTC) (envelope-from gonzo@id.bluezbox.com) Received: from id.bluezbox.com (id.bluezbox.com [88.198.91.248]) by mx1.freebsd.org (Postfix) with ESMTP id 5B3928FC08; Sun, 25 Nov 2012 04:02:00 +0000 (UTC) Received: from [207.6.254.8] (helo=[192.168.1.67]) by id.bluezbox.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from ) id 1TcTPi-000Nyq-SA; Sat, 24 Nov 2012 20:01:52 -0800 Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: FreeBSD on RaspberryPi From: Oleksandr Tymoshenko In-Reply-To: Date: Sat, 24 Nov 2012 20:01:33 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <9E4DA920-BE72-4AA0-8159-43205CDEF5CD@bluezbox.com> References: <31C904E6-F230-4187-AE32-F9A7B1A7C38E@freebsd.org> <4A5E03E5-3295-4FD4-9A06-7D1C4E9E0C12@freebsd.org> To: Tim Kientzle X-Mailer: Apple Mail (2.1499) Sender: gonzo@id.bluezbox.com X-Spam-Level: -- X-Spam-Report: Spam detection software, running on the system "id.bluezbox.com", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: On 2012-11-24, at 4:47 PM, Tim Kientzle wrote: > > On Nov 24, 2012, at 11:13 AM, Alexander Yerenkow wrote: > >> >> >> 2012/11/24 Tim Kientzle >> On Nov 7, 2012, at 8:09 AM, Alexander Yerenkow wrote: >> >>>> Such experiments was tried by me and others in August; I got framebuffer worked in rca/hdmi; … >> >> On Nov 8, 2012, at 11:12 PM, Alexander Yerenkow wrote: >> >>> It was plain current with plain RPIB kernel config, and for graphic you should uncomment there partition about sysconsole; serial then disabled; >>> Also, if you want ethernet - it's ue device, which also worked, but produced hangs for me in past (Hans IIRC already fixed.this). >>> I'll have some time this weekend, feel free to contact me by gtalk or else, I will play around with my rpi with both serials and vide modes. >> >> Alexander, >> >> I tried uncommenting the 'sc' entries in the RPI-B kernel >> config that's in -CURRENT right now. >> >> All entries, right? > > Yes, I uncommented all entries. > >> And how do you booting, via usb-flash, or via SD card? > > Via SD-card. I'm using the image from here: > http://people.freebsd.org/~kientzle/FreeBSD-RPI-B-r242362-2012-10-30.img.xz > and swapping out the kernel. > >> I'll build now CURRENT, will look if I got same. > > Thanks. I'd appreciate knowing whether it works for you. > > If you can get it to work, I'd appreciate any details you can give. [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] Cc: FreeBSD Hackers , Alexander Yerenkow X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Nov 2012 04:02:01 -0000 On 2012-11-24, at 4:47 PM, Tim Kientzle wrote: >=20 > On Nov 24, 2012, at 11:13 AM, Alexander Yerenkow wrote: >=20 >>=20 >>=20 >> 2012/11/24 Tim Kientzle >> On Nov 7, 2012, at 8:09 AM, Alexander Yerenkow wrote: >>=20 >>>> Such experiments was tried by me and others in August; I got = framebuffer worked in rca/hdmi; =85 >>=20 >> On Nov 8, 2012, at 11:12 PM, Alexander Yerenkow wrote: >>=20 >>> It was plain current with plain RPIB kernel config, and for graphic = you should uncomment there partition about sysconsole; serial then = disabled; >>> Also, if you want ethernet - it's ue device, which also worked, but = produced hangs for me in past (Hans IIRC already fixed.this). >>> I'll have some time this weekend, feel free to contact me by gtalk = or else, I will play around with my rpi with both serials and vide = modes. >>=20 >> Alexander, >>=20 >> I tried uncommenting the 'sc' entries in the RPI-B kernel >> config that's in -CURRENT right now. >>=20 >> All entries, right? >=20 > Yes, I uncommented all entries. >=20 >> And how do you booting, via usb-flash, or via SD card? >=20 > Via SD-card. I'm using the image from here: > = http://people.freebsd.org/~kientzle/FreeBSD-RPI-B-r242362-2012-10-30.img.x= z > and swapping out the kernel. >=20 >> I'll build now CURRENT, will look if I got same.=20 >=20 > Thanks. I'd appreciate knowing whether it works for you. >=20 > If you can get it to work, I'd appreciate any details you can give. Tim, I'm almost done with getting kernel working with latest raspberry Pi = firmware. Just need to figure out how to make ubldr pass FDT pointer from u-boot to kernel = and handle=20 /reserve/ information in ARM machdep code.=20 Meanwhile I suggest editing .dts file manually. Fill out "display" node = properties with proper display resolution and depth. Also add ukbd driver. That should get you = working console.=20= From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 25 10:29:00 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 07237312; Sun, 25 Nov 2012 10:29:00 +0000 (UTC) (envelope-from jlh@FreeBSD.org) Received: from smtp5-g21.free.fr (smtp5-g21.free.fr [IPv6:2a01:e0c:1:1599::14]) by mx1.freebsd.org (Postfix) with ESMTP id A8A618FC08; Sun, 25 Nov 2012 10:28:57 +0000 (UTC) Received: from endor.tataz.chchile.org (unknown [82.233.239.98]) by smtp5-g21.free.fr (Postfix) with ESMTP id BAE02D48132; Sun, 25 Nov 2012 11:28:49 +0100 (CET) Received: from felucia.tataz.chchile.org (felucia.tataz.chchile.org [192.168.1.9]) by endor.tataz.chchile.org (Postfix) with ESMTP id 8E1817C3; Sun, 25 Nov 2012 11:28:48 +0100 (CET) Received: by felucia.tataz.chchile.org (Postfix, from userid 1000) id 6721B10199; Sun, 25 Nov 2012 10:28:48 +0000 (UTC) Date: Sun, 25 Nov 2012 11:28:48 +0100 From: Jeremie Le Hen To: Mateusz Guzik , Zaphod Beeblebrox , Eitan Adler , FreeBSD Hackers , Benjamin Kaduk Subject: Re: old style kernel configuration Message-ID: <20121125102848.GA75048@felucia.tataz.chchile.org> Mail-Followup-To: Mateusz Guzik , Zaphod Beeblebrox , Eitan Adler , FreeBSD Hackers , Benjamin Kaduk References: <20121122163857.GA25225@dft-labs.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20121122163857.GA25225@dft-labs.eu> User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Nov 2012 10:29:00 -0000 Hi! On Thu, Nov 22, 2012 at 05:38:58PM +0100, Mateusz Guzik wrote: > > # make buildkernel ... KERNFAST=1 Is it documented somewhere? I was using NO_CLEAN=1. -- Jeremie Le Hen Scientists say the world is made up of Protons, Neutrons and Electrons. They forgot to mention Morons. From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 25 11:10:19 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6D72FC76; Sun, 25 Nov 2012 11:10:19 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id C2AE48FC17; Sun, 25 Nov 2012 11:10:18 +0000 (UTC) Received: by mail-we0-f182.google.com with SMTP id u54so4052687wey.13 for ; Sun, 25 Nov 2012 03:10:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:subject:message-id:mail-followup-to:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=Zz0hU8iUDH8RSshyj7MELTICxsEUVQ24GOC9ns+D+qg=; b=OO2f4KsMtY8c09Xt7NgPsHlUdUyyYgDjXVwD1MEzbjfXpCUTS/2GyZ8ZhWBpqOZZHd H9dBXKntpTa2ZoxqKO8I2aDL5GiopAeFtaIKMCAUqY7Jbgt7cMhtWrjrzsWsREPyAC6/ o/MpbWZefUbujNPBz5DtvucEyFVUWc96EtaIqF0xKM+MhnqzHAgMOmt2OFBZS0EMVv5y tysg9I7vMDsKQ6WEbdGvQ00k2Dtq3aL/LZIEFwAn8/SNNihHybkq2xS5v1nB2l6uksOA jkWH9S3bBAoc+fquKl/7DaSU+r//3bH4U1l5hgvcTYOzmv2qvIfQ3C0WhKHvS1fJqLT9 cEZg== Received: by 10.216.30.16 with SMTP id j16mr3062709wea.42.1353841811735; Sun, 25 Nov 2012 03:10:11 -0800 (PST) Received: from dft-labs.eu (n1x0n-1-pt.tunnel.tserv5.lon1.ipv6.he.net. [2001:470:1f08:1f7::2]) by mx.google.com with ESMTPS id gk9sm16361153wib.4.2012.11.25.03.10.10 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 25 Nov 2012 03:10:10 -0800 (PST) Date: Sun, 25 Nov 2012 12:10:04 +0100 From: Mateusz Guzik To: Zaphod Beeblebrox , Eitan Adler , FreeBSD Hackers , Benjamin Kaduk Subject: Re: old style kernel configuration Message-ID: <20121125111004.GA25556@dft-labs.eu> Mail-Followup-To: Mateusz Guzik , Zaphod Beeblebrox , Eitan Adler , FreeBSD Hackers , Benjamin Kaduk References: <20121122163857.GA25225@dft-labs.eu> <20121125102848.GA75048@felucia.tataz.chchile.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20121125102848.GA75048@felucia.tataz.chchile.org> User-Agent: Mutt/1.5.20 (2009-06-14) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Nov 2012 11:10:19 -0000 On Sun, Nov 25, 2012 at 11:28:48AM +0100, Jeremie Le Hen wrote: > Hi! > > On Thu, Nov 22, 2012 at 05:38:58PM +0100, Mateusz Guzik wrote: > > > > # make buildkernel ... KERNFAST=1 > > Is it documented somewhere? I was using NO_CLEAN=1. > Yep, build(7). -- Mateusz Guzik From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 25 12:29:51 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7F57559C; Sun, 25 Nov 2012 12:29:51 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id BAC458FC18; Sun, 25 Nov 2012 12:29:50 +0000 (UTC) Received: by mail-lb0-f182.google.com with SMTP id go10so7221318lbb.13 for ; Sun, 25 Nov 2012 04:29:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=hma5uL1zHZll4LoapOeK69ONhmauYi1RcFsnEzJj+3k=; b=uLyc6wVvHc9vqDTjB8cWAMXE3wqq4WIKbrhfiPoeIxJJxLO0L6VLueh++ZGVtimyPG qKRQM2Iuv05BUCQFNP3isy81eluMQiKeqLOc0c03CscmgBHgFir3FpCmgmhIJyiQhAvV LrJ7kxP7Rq+0AgIKkDVRzYUUvOb3VSXsXdHc0aeOOs6ISTbWITrfEuIXE71l0+B9k7Zk X/LuFSghQYCj7UeTzkL9KUY7fITh2Skdj+otZaNgJPgmKacSupTLtufna3gyovA2DRnl nWn4KPijG4c94+lVffI4Ig/jl3m0jZPkMS9MGz/jR6VfmGwdeE0dlBkyoWawwXGcaGeH ZWvA== MIME-Version: 1.0 Received: by 10.112.87.40 with SMTP id u8mr3836929lbz.50.1353846589263; Sun, 25 Nov 2012 04:29:49 -0800 (PST) Sender: asmrookie@gmail.com Received: by 10.112.134.5 with HTTP; Sun, 25 Nov 2012 04:29:49 -0800 (PST) In-Reply-To: <50A65208.4050804@FreeBSD.org> References: <50A5F12C.1050902@FreeBSD.org> <50A63D1D.9090500@FreeBSD.org> <50A65208.4050804@FreeBSD.org> Date: Sun, 25 Nov 2012 12:29:49 +0000 X-Google-Sender-Auth: VtqKUqAX-ZXIFmAJ1516UZ69QnI Message-ID: Subject: Re: stop_cpus_hard when multiple CPUs are panicking from an NMI From: Attilio Rao To: Andriy Gapon Content-Type: text/plain; charset=UTF-8 Cc: freebsd-hackers@freebsd.org, Ryan Stone X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: attilio@FreeBSD.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Nov 2012 12:29:51 -0000 On Fri, Nov 16, 2012 at 2:47 PM, Andriy Gapon wrote: > on 16/11/2012 16:41 Attilio Rao said the following: >> On Fri, Nov 16, 2012 at 1:18 PM, Andriy Gapon wrote: >>> on 16/11/2012 14:30 Attilio Rao said the following: >>>> On Fri, Nov 16, 2012 at 7:54 AM, Andriy Gapon wrote: >>>>> on 16/11/2012 00:58 Ryan Stone said the following: >>>>>> At work we have some custom watchdog hardware that sends an NMI upon >>>>>> expiry. We've modified the kernel to panic when it receives the watchdog >>>>>> NMI. I've been trying the "stop_scheduler_on_panic" mode, and I've >>>>>> discovered that when my watchdog expires, the system gets completely >>>>>> wedged. After some digging, I've discovered is that I have multiple CPUs >>>>>> getting the watchdog NMI and trying to panic concurrently. One of the CPUs >>>>>> wins, and the rest spin forever in this code: >>>>>> >>>>>> /* >>>>>> * We don't want multiple CPU's to panic at the same time, so we >>>>>> * use panic_cpu as a simple spinlock. We have to keep checking >>>>>> * panic_cpu if we are spinning in case the panic on the first >>>>>> * CPU is canceled. >>>>>> */ >>>>>> if (panic_cpu != PCPU_GET(cpuid)) >>>>>> while (atomic_cmpset_int(&panic_cpu, NOCPU, >>>>>> PCPU_GET(cpuid)) == 0) >>>>>> while (panic_cpu != NOCPU) >>>>>> ; /* nothing */ >>>>>> >>>>>> The system wedges when stop_cpus_hard() is called, which sends NMIs to all >>>>>> of the other CPUs and waits for them to acknowledge that they are stopped >>>>>> before returning. However the CPU will not deliver an NMI to a CPU that is >>>>>> already handling an NMI, so the other CPUs that got a watchdog NMI and are >>>>>> spinning will never go into the NMI handler and acknowledge that they are >>>>>> stopped. >>>>> >>>>> I thought about this issue and fixed (in my tree) in a different way: >>>>> http://people.freebsd.org/~avg/cpu_stop-race.diff >>>>> >>>>> The need for spinlock_enter in the patch in not entirely clear. >>>>> The main idea is that a CPU which calls cpu_stop and loses a race should >>>>> voluntary enter cpustop_handler. >>>>> I am also not sure about MI-cleanness of this patch. >>>> >>>> It is similar to what I propose but with some differences: >>>> - It is not clean from MI perspective >>> >>> OK. >>> >>>> - I don't think we need to treact it specially, I would just >>>> unconditionally stop all the CPUs entering in the "spinlock zone", >>>> making the patch simpler. >>> >>> I couldn't understand this part. >> >> I'm sorry, I think I misread your patch. >> >> I was basically suggesting to fix Ryan case by calling >> cpustop_handler() (or the new MI interface) into the panic() function, >> in the case the CPU don't win the race for panic_cpu. >> Basically doing: >> Index: sys/kern/kern_shutdown.c >> =================================================================== >> --- sys/kern/kern_shutdown.c (revision 243154) >> +++ sys/kern/kern_shutdown.c (working copy) >> @@ -568,15 +568,11 @@ panic(const char *fmt, ...) >> #ifdef SMP >> /* >> * We don't want multiple CPU's to panic at the same time, so we >> - * use panic_cpu as a simple spinlock. We have to keep checking >> - * panic_cpu if we are spinning in case the panic on the first >> - * CPU is canceled. >> + * use panic_cpu as a simple lock. >> */ >> if (panic_cpu != PCPU_GET(cpuid)) >> - while (atomic_cmpset_int(&panic_cpu, NOCPU, >> - PCPU_GET(cpuid)) == 0) >> - while (panic_cpu != NOCPU) >> - ; /* nothing */ >> + if (atomic_cmpset_int(&panic_cpu, NOCPU, PCPU_GET(cpuid)) == 0) >> + cpustop_handler(); >> >> if (stop_scheduler_on_panic) { >> if (panicstr == NULL && !kdb_active) { >> >> >> Infact it seems to me that the comment is outdated and no longer >> represent truth. > > Ah, I see. Thank you. > > My older plan was to get rid of stop_scheduler_on_panic, that is to make the > behavior unconditional. And then to use stop_cpus_hard instead of the hand-rolled > 'panic_cpu' spinlock. This way the whichever CPU wins stop_cpus_hard would be the > only CPU to enter panic. So, assuming we are not yet defaulting to stop cpus behaviour for panic, I think we have 2 things to take care: 1) Handling the simultaneous panics 2) Handling deadlocks/starvation among simultaneous cpu_stops In particular, case 2 is more tricky than it seems, it is not only related to NMI but also to the case where you send an IPI_STOP via a normal IPI and interrupts are disabled on one of the channels. Infact, I think the patch you propose makes such effects even worse, because it disables interrupts in generic_stop_cpus(). What I suggest to do, is the following: - The CPU which wins the race for generic_stop_cpus also signals the CPUs it is willing to stop on a global mask - Another CPU entering generic_stop_cpus() and loosing the race, checks the mask of cpus which might be stopped and stops itself if necessary (ie. not yet done). We must be careful with races here, but I'm confindent this can be done easily enough. About the case 1 I think that my patch should be good enough, if you agree. We can worry about making the stop_cpu default case later on (I don't recall if we had any real objection to it or we just wanted to be protective). I've also recently thought about the suspended_cpus mask. I know I'm the one who pushed for it and you are the one who didn't like it, but I'm caming to think that you may have been right with this. I want to review some code and eventually we can merge suspended_cpus with stopped_cpus eventually. What do you think? Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 25 12:31:44 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 90C5DAA8; Sun, 25 Nov 2012 12:31:44 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id CA88C8FC08; Sun, 25 Nov 2012 12:31:43 +0000 (UTC) Received: by mail-lb0-f182.google.com with SMTP id go10so7221972lbb.13 for ; Sun, 25 Nov 2012 04:31:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=vzBEDAiKuch/DWCqYTiKTAePuI9Q1kbrsGdWeGGc94Y=; b=vkATVCwe9vr1Tu95wiyMKel1/N/CfzAh3vtDuDEsmwa2sZ2EQ4RCzF2tXEIW5bnkbM i1enY7ke2whpTp2+WiCKZpihdOiK4NAOBa16TQxaWKGjT6aSXXR2faK6coj+XjDek6Of jHqwshULy3Bg+oDrDNXvoEgeHL3nGOdQnqsPuAD7UUez51UstlQJFbD0Z3P64Voi+BbX wv+/APprBwFnlqY3xZ/HIfNro+p/MLmMa0fF0PKgTZffvyHe4T9/iems22dnB3KqwWDD JcZ8WDChGMkJTfLOaBPn7blIKgK2sIiDkxKqLsdGzgiT4+hirk+nmQD/4FONWJQopL9L Mblw== MIME-Version: 1.0 Received: by 10.152.104.50 with SMTP id gb18mr8304404lab.9.1353846702535; Sun, 25 Nov 2012 04:31:42 -0800 (PST) Sender: asmrookie@gmail.com Received: by 10.112.134.5 with HTTP; Sun, 25 Nov 2012 04:31:42 -0800 (PST) In-Reply-To: References: <50A5F12C.1050902@FreeBSD.org> <50A63D1D.9090500@FreeBSD.org> <50A65208.4050804@FreeBSD.org> Date: Sun, 25 Nov 2012 12:31:42 +0000 X-Google-Sender-Auth: RoDkbfyVsG3cSImyS_LaZLDvzjk Message-ID: Subject: Re: stop_cpus_hard when multiple CPUs are panicking from an NMI From: Attilio Rao To: Andriy Gapon Content-Type: text/plain; charset=UTF-8 Cc: freebsd-hackers@freebsd.org, Ryan Stone X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: attilio@FreeBSD.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Nov 2012 12:31:44 -0000 On Sun, Nov 25, 2012 at 12:29 PM, Attilio Rao wrote: > On Fri, Nov 16, 2012 at 2:47 PM, Andriy Gapon wrote: >> on 16/11/2012 16:41 Attilio Rao said the following: >>> On Fri, Nov 16, 2012 at 1:18 PM, Andriy Gapon wrote: >>>> on 16/11/2012 14:30 Attilio Rao said the following: >>>>> On Fri, Nov 16, 2012 at 7:54 AM, Andriy Gapon wrote: >>>>>> on 16/11/2012 00:58 Ryan Stone said the following: >>>>>>> At work we have some custom watchdog hardware that sends an NMI upon >>>>>>> expiry. We've modified the kernel to panic when it receives the watchdog >>>>>>> NMI. I've been trying the "stop_scheduler_on_panic" mode, and I've >>>>>>> discovered that when my watchdog expires, the system gets completely >>>>>>> wedged. After some digging, I've discovered is that I have multiple CPUs >>>>>>> getting the watchdog NMI and trying to panic concurrently. One of the CPUs >>>>>>> wins, and the rest spin forever in this code: >>>>>>> >>>>>>> /* >>>>>>> * We don't want multiple CPU's to panic at the same time, so we >>>>>>> * use panic_cpu as a simple spinlock. We have to keep checking >>>>>>> * panic_cpu if we are spinning in case the panic on the first >>>>>>> * CPU is canceled. >>>>>>> */ >>>>>>> if (panic_cpu != PCPU_GET(cpuid)) >>>>>>> while (atomic_cmpset_int(&panic_cpu, NOCPU, >>>>>>> PCPU_GET(cpuid)) == 0) >>>>>>> while (panic_cpu != NOCPU) >>>>>>> ; /* nothing */ >>>>>>> >>>>>>> The system wedges when stop_cpus_hard() is called, which sends NMIs to all >>>>>>> of the other CPUs and waits for them to acknowledge that they are stopped >>>>>>> before returning. However the CPU will not deliver an NMI to a CPU that is >>>>>>> already handling an NMI, so the other CPUs that got a watchdog NMI and are >>>>>>> spinning will never go into the NMI handler and acknowledge that they are >>>>>>> stopped. >>>>>> >>>>>> I thought about this issue and fixed (in my tree) in a different way: >>>>>> http://people.freebsd.org/~avg/cpu_stop-race.diff >>>>>> >>>>>> The need for spinlock_enter in the patch in not entirely clear. >>>>>> The main idea is that a CPU which calls cpu_stop and loses a race should >>>>>> voluntary enter cpustop_handler. >>>>>> I am also not sure about MI-cleanness of this patch. >>>>> >>>>> It is similar to what I propose but with some differences: >>>>> - It is not clean from MI perspective >>>> >>>> OK. >>>> >>>>> - I don't think we need to treact it specially, I would just >>>>> unconditionally stop all the CPUs entering in the "spinlock zone", >>>>> making the patch simpler. >>>> >>>> I couldn't understand this part. >>> >>> I'm sorry, I think I misread your patch. >>> >>> I was basically suggesting to fix Ryan case by calling >>> cpustop_handler() (or the new MI interface) into the panic() function, >>> in the case the CPU don't win the race for panic_cpu. >>> Basically doing: >>> Index: sys/kern/kern_shutdown.c >>> =================================================================== >>> --- sys/kern/kern_shutdown.c (revision 243154) >>> +++ sys/kern/kern_shutdown.c (working copy) >>> @@ -568,15 +568,11 @@ panic(const char *fmt, ...) >>> #ifdef SMP >>> /* >>> * We don't want multiple CPU's to panic at the same time, so we >>> - * use panic_cpu as a simple spinlock. We have to keep checking >>> - * panic_cpu if we are spinning in case the panic on the first >>> - * CPU is canceled. >>> + * use panic_cpu as a simple lock. >>> */ >>> if (panic_cpu != PCPU_GET(cpuid)) >>> - while (atomic_cmpset_int(&panic_cpu, NOCPU, >>> - PCPU_GET(cpuid)) == 0) >>> - while (panic_cpu != NOCPU) >>> - ; /* nothing */ >>> + if (atomic_cmpset_int(&panic_cpu, NOCPU, PCPU_GET(cpuid)) == 0) >>> + cpustop_handler(); >>> >>> if (stop_scheduler_on_panic) { >>> if (panicstr == NULL && !kdb_active) { >>> >>> >>> Infact it seems to me that the comment is outdated and no longer >>> represent truth. >> >> Ah, I see. Thank you. >> >> My older plan was to get rid of stop_scheduler_on_panic, that is to make the >> behavior unconditional. And then to use stop_cpus_hard instead of the hand-rolled >> 'panic_cpu' spinlock. This way the whichever CPU wins stop_cpus_hard would be the >> only CPU to enter panic. > > So, assuming we are not yet defaulting to stop cpus behaviour for > panic, I think we have 2 things to take care: > 1) Handling the simultaneous panics > 2) Handling deadlocks/starvation among simultaneous cpu_stops > > In particular, case 2 is more tricky than it seems, it is not only > related to NMI but also to the case where you send an IPI_STOP via a > normal IPI and interrupts are disabled on one of the channels. Infact, > I think the patch you propose makes such effects even worse, because > it disables interrupts in generic_stop_cpus(). > What I suggest to do, is the following: > - The CPU which wins the race for generic_stop_cpus also signals the > CPUs it is willing to stop on a global mask > - Another CPU entering generic_stop_cpus() and loosing the race, > checks the mask of cpus which might be stopped and stops itself if > necessary (ie. not yet done). We must be careful with races here, but > I'm confindent this can be done easily enough. BTW; I'm aware such case is not fatal because of the safety belt, but I think it would be too easy to get wrong code if we get simultaneous generic_stop_cpus() to race in the "wrong way" (race loser with interrupts/NMI disabled). Thanks, Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 25 12:38:10 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A3272E3B; Sun, 25 Nov 2012 12:38:10 +0000 (UTC) (envelope-from pawel@dawidek.net) Received: from mail.dawidek.net (garage.dawidek.net [91.121.88.72]) by mx1.freebsd.org (Postfix) with ESMTP id 5CB6F8FC19; Sun, 25 Nov 2012 12:38:09 +0000 (UTC) Received: from localhost (89-73-195-149.dynamic.chello.pl [89.73.195.149]) by mail.dawidek.net (Postfix) with ESMTPSA id 19DBAC33; Sun, 25 Nov 2012 13:36:21 +0100 (CET) Date: Sun, 25 Nov 2012 13:39:21 +0100 From: Pawel Jakub Dawidek To: Attilio Rao Subject: Re: [RFQ] make witness panic an option Message-ID: <20121125123920.GI1460@garage.freebsd.pl> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="EdRE1UL8d3mMOE6m" Content-Disposition: inline In-Reply-To: X-OS: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "freebsd-hackers@freebsd.org" , Adrian Chadd , Giovanni Trematerra , freebsd-arch@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Nov 2012 12:38:10 -0000 --EdRE1UL8d3mMOE6m Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Nov 15, 2012 at 04:39:55PM +0000, Attilio Rao wrote: > On 11/15/12, Adrian Chadd wrote: > > On 15 November 2012 05:27, Giovanni Trematerra > > wrote: > > > >> I really do think that is a very bad idea. > >> When a locking assertion fails you have just to stop your mind and > >> think what's wrong, > >> no way to postpone on this. > > > > Not all witness panics are actually fatal. For a developer who is > > sufficiently cluey in their area, they are quite likely able to just > > stare at the code paths for a while to figure out why the > > incorrectness occured. >=20 > The problem is that such mechanism can be abused, just like the > BLESSING one and that's why this is disabled by default. WITNESS is a development tool. We don't ship production kernels with WITNESS even compiled in. What is more efficient use of developer time: going through full reboot cycle every time or reading the warning from console, unloading a module, fixing the bug and loading it again? And if this option is turned off by default what is the problem? --=20 Pawel Jakub Dawidek http://www.wheelsystems.com FreeBSD committer http://www.FreeBSD.org Am I Evil? Yes, I Am! http://tupytaj.pl --EdRE1UL8d3mMOE6m Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlCyEXgACgkQForvXbEpPzRdpwCbBmzAAu4KdDaHCcDdEr/xq5SE HDwAoMpyO7TPU8jPupmwrg1EgSJXLljn =gpTY -----END PGP SIGNATURE----- --EdRE1UL8d3mMOE6m-- From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 25 12:42:19 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 78F30180; Sun, 25 Nov 2012 12:42:19 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id 5BEBF8FC0C; Sun, 25 Nov 2012 12:42:17 +0000 (UTC) Received: by mail-lb0-f182.google.com with SMTP id go10so7225582lbb.13 for ; Sun, 25 Nov 2012 04:42:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=/ZgxWTcmy7bW4zmJmA9hpWjmPo8HwffJiEFY4Zl3HMw=; b=dWCkF44fYD/BMhGodD7WygNvt0/CKcOSuZipXG8UTj6sZmAyX9m3GdpvTbw9fop/wZ lkaSUUOE0O5gLbm4QLv5URLMAgFSfIlJPfXf4Vog0oT4v4OrmFbNSRgydG0iZmK6SwQG WtoPu7gcI4gW+0/z+AaQNgjj+Ix0iFzumN3Xyu6IdNJQ0cFaSG6B9OLeltYLuw1DSyoN AH0DlxZny3WuCU59W/xI5Ml7hUD76hOdp7aGpvAV68scK6yuCNaPFMg6PhAtFn++Qa5f phXfLa7Czu6QxuT1Jud6SUe8vs0CejWKI8hj+jXyK8owH9tByfVGjwpQ1OtNtWApYX+4 uEVA== MIME-Version: 1.0 Received: by 10.112.28.98 with SMTP id a2mr3800413lbh.110.1353847337007; Sun, 25 Nov 2012 04:42:17 -0800 (PST) Sender: asmrookie@gmail.com Received: by 10.112.134.5 with HTTP; Sun, 25 Nov 2012 04:42:16 -0800 (PST) In-Reply-To: <20121125123920.GI1460@garage.freebsd.pl> References: <20121125123920.GI1460@garage.freebsd.pl> Date: Sun, 25 Nov 2012 12:42:16 +0000 X-Google-Sender-Auth: A_uJPsdkWDmbZj44H85r7_DJHmg Message-ID: Subject: Re: [RFQ] make witness panic an option From: Attilio Rao To: Pawel Jakub Dawidek Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-hackers@freebsd.org" , Adrian Chadd , Giovanni Trematerra , freebsd-arch@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: attilio@FreeBSD.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Nov 2012 12:42:19 -0000 On Sun, Nov 25, 2012 at 12:39 PM, Pawel Jakub Dawidek wrote: > On Thu, Nov 15, 2012 at 04:39:55PM +0000, Attilio Rao wrote: >> On 11/15/12, Adrian Chadd wrote: >> > On 15 November 2012 05:27, Giovanni Trematerra >> > wrote: >> > >> >> I really do think that is a very bad idea. >> >> When a locking assertion fails you have just to stop your mind and >> >> think what's wrong, >> >> no way to postpone on this. >> > >> > Not all witness panics are actually fatal. For a developer who is >> > sufficiently cluey in their area, they are quite likely able to just >> > stare at the code paths for a while to figure out why the >> > incorrectness occured. >> >> The problem is that such mechanism can be abused, just like the >> BLESSING one and that's why this is disabled by default. > > WITNESS is a development tool. We don't ship production kernels with > WITNESS even compiled in. What is more efficient use of developer time: > going through full reboot cycle every time or reading the warning from > console, unloading a module, fixing the bug and loading it again? > > And if this option is turned off by default what is the problem? Yes, so, why do you write here? Go ahead and fix BLESSED, make it the default, etc. I have enough of your (not referred to you particulary but to the people which contributed to this and other thread) to not be able to respect others opinion. As I said I cannot forbid you guys from doing anything, just go ahead, write the code and commit it, albeit completely bypassing other people's opinion. Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 25 12:55:37 2012 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 87FB5616; Sun, 25 Nov 2012 12:55:37 +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 995E38FC12; Sun, 25 Nov 2012 12:55:36 +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 OAA18339; Sun, 25 Nov 2012 14:55:34 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1TcbkE-000Kw8-KS; Sun, 25 Nov 2012 14:55:34 +0200 Message-ID: <50B21545.5060807@FreeBSD.org> Date: Sun, 25 Nov 2012 14:55:33 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: attilio@FreeBSD.org Subject: Re: stop_cpus_hard when multiple CPUs are panicking from an NMI References: <50A5F12C.1050902@FreeBSD.org> <50A63D1D.9090500@FreeBSD.org> <50A65208.4050804@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@FreeBSD.org, Ryan Stone X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Nov 2012 12:55:37 -0000 on 25/11/2012 14:29 Attilio Rao said the following: > I think the patch you propose makes such effects even worse, because > it disables interrupts in generic_stop_cpus(). > What I suggest to do, is the following: > - The CPU which wins the race for generic_stop_cpus also signals the > CPUs it is willing to stop on a global mask > - Another CPU entering generic_stop_cpus() and loosing the race, > checks the mask of cpus which might be stopped and stops itself if > necessary (ie. not yet done). We must be careful with races here, but > I'm confindent this can be done easily enough. I think that you either misunderstood my patch or I misunderstand your suggestion, because my patch does exactly what you wrote above. -- Andriy Gapon From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 25 13:11:41 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C8AA6916; Sun, 25 Nov 2012 13:11:41 +0000 (UTC) (envelope-from pawel@dawidek.net) Received: from mail.dawidek.net (garage.dawidek.net [91.121.88.72]) by mx1.freebsd.org (Postfix) with ESMTP id 758F08FC08; Sun, 25 Nov 2012 13:11:40 +0000 (UTC) Received: from localhost (89-73-195-149.dynamic.chello.pl [89.73.195.149]) by mail.dawidek.net (Postfix) with ESMTPSA id 85F8CC48; Sun, 25 Nov 2012 14:09:52 +0100 (CET) Date: Sun, 25 Nov 2012 14:12:52 +0100 From: Pawel Jakub Dawidek To: Attilio Rao Subject: Re: [RFQ] make witness panic an option Message-ID: <20121125131252.GJ1460@garage.freebsd.pl> References: <20121125123920.GI1460@garage.freebsd.pl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="/0U0QBNx7JIUZLHm" Content-Disposition: inline In-Reply-To: X-OS: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "freebsd-hackers@freebsd.org" , Adrian Chadd , Giovanni Trematerra , freebsd-arch@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Nov 2012 13:11:42 -0000 --/0U0QBNx7JIUZLHm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Nov 25, 2012 at 12:42:16PM +0000, Attilio Rao wrote: > On Sun, Nov 25, 2012 at 12:39 PM, Pawel Jakub Dawidek w= rote: > > WITNESS is a development tool. We don't ship production kernels with > > WITNESS even compiled in. What is more efficient use of developer time: > > going through full reboot cycle every time or reading the warning from > > console, unloading a module, fixing the bug and loading it again? > > > > And if this option is turned off by default what is the problem? >=20 > Yes, so, why do you write here? I'm trying to understand why do you object. Until now the only concern you have that I found is that you are afraid of it being abused. I don't see how this can be abused if it is turned off by default. If someone will commit a change that will turn it on by default, believe me, I'll unleash hell personally. As I said, WITNESS is development tool, a very handy one. This doesn't mean we can't make it even more handy. It is there to help find bugs faster, right? Adrian is proposing a change that will make it help to find and fix bugs maybe even faster. > Go ahead and fix BLESSED, make it the default, etc. This is another story, but BLESSED is much less controversial to me. It is turned off by default in assumption that all the code that runs in our kernel is developed for FreeBSD, which is not true. For example ZFS is, I think, the biggest locking consumer in our kernel (around 120 locks), which wasn't originally developed for FreeBSD and locking order was verified using different tools. Now on FreeBSD it triggers massive LOR warnings from WITNESS, eventhough those are not bugs. At some point I verified many of them and they were all false-positives, so I simply turned off WITNESS warnings for ZFS locks. Why? Because BLESSED is turned off in fear of abuse, and this is turn is the cause of mentioned hack in ZFS. > I have enough of your (not referred to you particulary but to the > people which contributed to this and other thread) to not be able to > respect others opinion. > As I said I cannot forbid you guys from doing anything, just go ahead, > write the code and commit it, albeit completely bypassing other > people's opinion. I'm sorry, I wasn't aware that your opinions are set in stone. I hoped that with some new arguments you may want to reconsider:) --=20 Pawel Jakub Dawidek http://www.wheelsystems.com FreeBSD committer http://www.FreeBSD.org Am I Evil? Yes, I Am! http://tupytaj.pl --/0U0QBNx7JIUZLHm Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlCyGVQACgkQForvXbEpPzTD7wCghovfDQb54c7N9qdn+GkhKYZH 4PkAoOK2W1rVxX032BdbCFvgrE1u8Zwv =tTdM -----END PGP SIGNATURE----- --/0U0QBNx7JIUZLHm-- From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 25 10:43:11 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 442DA5D8 for ; Sun, 25 Nov 2012 10:43:11 +0000 (UTC) (envelope-from w8hdkim@gmail.com) Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id E998D8FC08 for ; Sun, 25 Nov 2012 10:43:10 +0000 (UTC) Received: by mail-vb0-f54.google.com with SMTP id l1so2352881vba.13 for ; Sun, 25 Nov 2012 02:43:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=L6f82iXS3hnoh6macm8525k4vb91UpBEK5wvSizInBA=; b=qxlLvhOSTsCw0Td5yZ78UhxeSRezNVPBYylygq4GF+yK5GU6ErhJwYDTl6RERvqCnH he3yyPsfqorTI/nOMIy5bVreMeLBJCND1ZSazwtzAFdN8a15rBePJKVxis/4D0CGtl4z 2Nw+m3+yqEynnyAMAC02mwU6v5PlRTGdngLhZokVjcEykd3fhY3zp6A/wMsHdpMRf6Q3 M+PPJnTlYwvejVurMWRgWcoPbxxMxKm+yoh1iavHQ9fljohy0Ib8tQ/5p27gwjE0LfLB gqjW/Mlb/jxoChPII2oSHKj8kXRs12zcHBs2/sSixhsdXknZvx9YWu+YJUrlOmpQf3iX 5Hsw== MIME-Version: 1.0 Received: by 10.58.15.72 with SMTP id v8mr14161953vec.55.1353840190176; Sun, 25 Nov 2012 02:43:10 -0800 (PST) Received: by 10.58.226.163 with HTTP; Sun, 25 Nov 2012 02:43:10 -0800 (PST) Date: Sun, 25 Nov 2012 05:43:10 -0500 Message-ID: Subject: Re: postfix mail server infected ? From: Kim Culhan To: trafdev X-Mailman-Approved-At: Sun, 25 Nov 2012 13:36:23 +0000 Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Nov 2012 10:43:11 -0000 On Sat, November 24, 2012 1:08 pm, trafdev wrote: > Hi. I've a dedicated stand-alone FreeBSD server: > > uname -a > FreeBSD trafd-website-freebsd 9.0-RELEASE-p3 FreeBSD 9.0-RELEASE-p3 #0: > Tue Jun 12 02:52:29 UTC 2012 > root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 > > Server has one external interface (re0) with IP 206.239.112.241 and > postfix service installed on 25 port. > > Yesterday I've noticed huge amount of emails sending out: > > Nov 24 00:00:37 trafd-website-freebsd postfix/smtpd[37230]: connect from > f116.sd.com[206.239.112.241] > Nov 24 00:00:37 trafd-website-freebsd postfix/qmgr[40324]: 73F7D1365D: > from=, size=1211, nrcpt=10 (queue active) > Nov 24 00:00:37 trafd-website-freebsd postfix/error[37366]: 75ECA134F2: > to=, relay=none, delay=25715, > delays=25715/0.02/0/0.12, dsn=4.7.0, status=deferred (delivery > temporarily suspended: host mta7.am0.yahoodns.net[66.94.236.34] refused > to talk to me: 421 4.7.0 [TS01] Messages from 206.239.112.241 > temporarily deferred due to user complaints - 4.16.55.1; see > http://postmaster.yahoo.com/421-ts01.html) > Nov 24 00:00:37 trafd-website-freebsd postfix/error[37368]: 794A911711: > to=, relay=none, delay=29716, > delays=29716/0.05/0/0.05, dsn=4.7.0, status=deferred (delivery > temporarily suspended: host mta7.am0.yahoodns.net[66.94.236.34] refused > to talk to me: 421 4.7.0 [TS01] Messages from 206.239.112.241 > temporarily deferred due to user complaints - 4.16.55.1; see > http://postmaster.yahoo.com/421-ts01.html) > Nov 24 00:00:37 trafd-website-freebsd postfix/smtp[36699]: E559512F49: > to=, > relay=vip-us-br-mx.terra.com[208.84.244.133]:25, delay=26077, > delays=26075/1/0.59/0.31, dsn=4.7.1, status=deferred (host > vip-us-br-mx.terra.com[208.84.244.133] said: 450 4.7.1 You've exceeded > your sending limit to this domain. (in reply to end of DATA command)) > Nov 24 00:00:37 trafd-website-freebsd postfix/error[37370]: 7C45D18E5D: > to=, relay=none, delay=6984, > delays=6984/0.02/0/0.04, dsn=4.7.0, status=deferred (delivery > temporarily suspended: host mta7.am0.yahoodns.net[66.94.236.34] refused > to talk to me: 421 4.7.0 [TS01] Messages from 206.239.112.241 > temporarily deferred due to user complaints - 4.16.55.1; see > http://postmaster.yahoo.com/421-ts01.html) > Nov 24 00:00:37 trafd-website-freebsd postfix/qmgr[40324]: 73E8118E53: > from=, size=1143, nrcpt=10 (queue active) > Nov 24 00:00:37 trafd-website-freebsd postfix/smtpd[37153]: 93E1020413: > client=f116.sd.com[206.239.112.241] > Nov 24 00:00:37 trafd-website-freebsd postfix/error[37367]: 74A511A5BF: > to=, relay=none, delay=5587, > delays=5587/0/0/0.18, dsn=4.7.0, status=deferred (delivery temporarily > suspended: host mta7.am0.yahoodns.net[66.94.236.34] refused to talk to > me: 421 4.7.0 [TS01] Messages from 206.239.112.241 temporarily deferred > due to user complaints - 4.16.55.1; see > http://postmaster.yahoo.com/421-ts01.html) > Nov 24 00:00:37 trafd-website-freebsd postfix/smtp[36698]: E7898134D0: > to=, relay=vip-us-br-mx.terra.com[208.84.244.133]:25, > conn_use=4, delay=25728, delays=25726/1.1/0.06/0.4, dsn=4.7.1, > status=deferred (host vip-us-br-mx.terra.com[208.84.244.133] said: 450 > 4.7.1 You've exceeded your sending limit to this domain. (in reply to > end of DATA command)) > Nov 24 00:00:37 trafd-website-freebsd postfix/smtp[36226]: 7BE421F989: > to=, relay=mx3.bol.com.br[200.147.36.13]:25, > delay=339, delays=339/0/0.49/0.24, dsn=4.7.1, status=deferred (host > mx3.bol.com.br[200.147.36.13] said: 450 4.7.1 : > Recipient address rejected: MX-BOL-04 - Too many messages, try again > later. (in reply to RCPT TO command)) > > Where f116.sd.com[206.239.112.241] is an IP and host assigned for > external interface (re0). > > Due to "permit_mynetworks" policy enabled in postfix conf mail was > sending out without authentication. However all externally connected > clients were rejected which is proper and expected behavior: > > Nov 24 19:31:04 trafd-website-freebsd postfix/smtpd[65618]: connect from > a2-starfury4.uol.com.br[200.147.33.227] > Nov 24 19:31:05 trafd-website-freebsd postfix/smtpd[65618]: NOQUEUE: > reject: RCPT from a2-starfury4.uol.com.br[200.147.33.227]: 550 5.1.1 > : Recipient address rejected: User unknown in virtual > mailbox table; from=<> to= proto=ESMTP > helo= > Nov 24 19:31:05 trafd-website-freebsd postfix/smtpd[65618]: disconnect > from a2-starfury4.uol.com.br[200.147.33.227] > > Then, I've tried: > > $cmd 001 deny all from any to me dst-port 25 in via re0 > $cmd 002 deny all from any to me dst-port 25 out via re0 > > and cleaned local mail queue with > postsuper -d ALL > > This didn't changed anything - server continued to send huge amount of > emails. > > However restrictions on lo0: > $cmd 001 deny all from any to me dst-port 25 in via lo0 > $cmd 002 deny all from any to me dst-port 25 out via lo0 > > did the trick - emailing had stopped. So by fact - problem solved, but > the real reason wasn't not found. > > I've launched clamav and f-prot scans - nothing suspicious found. > > The main question I have - how it's possible on stand-alone dedicated > server - who and how is connecting on behalf of it's own ext ip and uses > local interface to send emails? Is this possible to do from outside, or > server was infected from inside? It appears the delivery failures are failed attempts to deliver bounce messages which likely are generated in response to receiving emails with a Delivered-To: header with the address the same as the delivery address. The email has a forged sender address where postfix tries to send the bounce message. This activity seems to be increasing and we can guess at what the motivation might be.. Though its not a FreeBSD problem, there is very little discussion on the 'net about this and it probably causes a lot of grief for those on the receiving end of the bounce messages. Would be good if users of postfix on FreeBSD were aware of this and took some action. Google searching will find a few possibilities for that action, none I found were without some potential negative effects. Hope this helps.. -kim From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 25 13:37:22 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 30972506; Sun, 25 Nov 2012 13:37:22 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id 0D7448FC17; Sun, 25 Nov 2012 13:37:20 +0000 (UTC) Received: by mail-lb0-f182.google.com with SMTP id go10so7247376lbb.13 for ; Sun, 25 Nov 2012 05:37:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=sOy3O2jzaHqSDtvrM8xlzBIK1ymFObmKgtpUb9/hY+M=; b=sHChh4l4gqmqbjKEBXM5LtzNGYoIAa4r5h6Ii0+kbZJnHy+EwWRnXZETcnADaZh25R DCsxoPMvTfTkkfcySMiExWXx4FvOCwzZcyjrcCXQlZRfanc5/p8a7QsSPSgwuLJBV8W2 h1W/b7HYPWmdl3ew4XexZcOfSC5mhanS8EUJ/3hqPtTyABXO+LakdtiONeN3WnDKT/FV OCXbudjlYcoFWixMBrtJdUrA9LNWcw4oIyTZzsP/hCRw6zukliEzHkkpkraH6QLhulG5 2KVGEhtWI/l3v5oTffrchiI2oMKOYOPbfU1K7Ohy7ZEh42Ru10sThHf5q8BAyisxfVwN ndoA== MIME-Version: 1.0 Received: by 10.112.26.67 with SMTP id j3mr3979866lbg.39.1353850639777; Sun, 25 Nov 2012 05:37:19 -0800 (PST) Sender: asmrookie@gmail.com Received: by 10.112.134.5 with HTTP; Sun, 25 Nov 2012 05:37:19 -0800 (PST) In-Reply-To: <20121125131252.GJ1460@garage.freebsd.pl> References: <20121125123920.GI1460@garage.freebsd.pl> <20121125131252.GJ1460@garage.freebsd.pl> Date: Sun, 25 Nov 2012 13:37:19 +0000 X-Google-Sender-Auth: N8EJXNjtOLmV3R7ZWDhW0Zp7oV0 Message-ID: Subject: Re: [RFQ] make witness panic an option From: Attilio Rao To: Pawel Jakub Dawidek Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-hackers@freebsd.org" , Adrian Chadd , Giovanni Trematerra , freebsd-arch@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: attilio@FreeBSD.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Nov 2012 13:37:22 -0000 On Sun, Nov 25, 2012 at 1:12 PM, Pawel Jakub Dawidek wrote: > On Sun, Nov 25, 2012 at 12:42:16PM +0000, Attilio Rao wrote: >> On Sun, Nov 25, 2012 at 12:39 PM, Pawel Jakub Dawidek wrote: >> > WITNESS is a development tool. We don't ship production kernels with >> > WITNESS even compiled in. What is more efficient use of developer time: >> > going through full reboot cycle every time or reading the warning from >> > console, unloading a module, fixing the bug and loading it again? >> > >> > And if this option is turned off by default what is the problem? >> >> Yes, so, why do you write here? > > I'm trying to understand why do you object. Until now the only concern > you have that I found is that you are afraid of it being abused. I don't > see how this can be abused if it is turned off by default. If someone > will commit a change that will turn it on by default, believe me, I'll > unleash hell personally. So I don't understand what are you proposing. You are not proposing to switch BLESSING on and you are not proposing to import Adrian's patches in, if I get it correctly. I don't understand then. Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 25 13:46:33 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B5B4D795; Sun, 25 Nov 2012 13:46:33 +0000 (UTC) (envelope-from pawel@dawidek.net) Received: from mail.dawidek.net (garage.dawidek.net [91.121.88.72]) by mx1.freebsd.org (Postfix) with ESMTP id 6BBF98FC12; Sun, 25 Nov 2012 13:46:32 +0000 (UTC) Received: from localhost (89-73-195-149.dynamic.chello.pl [89.73.195.149]) by mail.dawidek.net (Postfix) with ESMTPSA id C074EC5C; Sun, 25 Nov 2012 14:44:43 +0100 (CET) Date: Sun, 25 Nov 2012 14:47:43 +0100 From: Pawel Jakub Dawidek To: Attilio Rao Subject: Re: [RFQ] make witness panic an option Message-ID: <20121125134743.GK1460@garage.freebsd.pl> References: <20121125123920.GI1460@garage.freebsd.pl> <20121125131252.GJ1460@garage.freebsd.pl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="OOq1TgGhe8eTwFBO" Content-Disposition: inline In-Reply-To: X-OS: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "freebsd-hackers@freebsd.org" , Adrian Chadd , Giovanni Trematerra , freebsd-arch@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Nov 2012 13:46:33 -0000 --OOq1TgGhe8eTwFBO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Nov 25, 2012 at 01:37:19PM +0000, Attilio Rao wrote: > On Sun, Nov 25, 2012 at 1:12 PM, Pawel Jakub Dawidek wr= ote: > > On Sun, Nov 25, 2012 at 12:42:16PM +0000, Attilio Rao wrote: > >> On Sun, Nov 25, 2012 at 12:39 PM, Pawel Jakub Dawidek wrote: > >> > WITNESS is a development tool. We don't ship production kernels with > >> > WITNESS even compiled in. What is more efficient use of developer ti= me: > >> > going through full reboot cycle every time or reading the warning fr= om > >> > console, unloading a module, fixing the bug and loading it again? > >> > > >> > And if this option is turned off by default what is the problem? > >> > >> Yes, so, why do you write here? > > > > I'm trying to understand why do you object. Until now the only concern > > you have that I found is that you are afraid of it being abused. I don't > > see how this can be abused if it is turned off by default. If someone > > will commit a change that will turn it on by default, believe me, I'll > > unleash hell personally. >=20 > So I don't understand what are you proposing. > You are not proposing to switch BLESSING on and you are not proposing > to import Adrian's patches in, if I get it correctly. I don't > understand then. I propose to get Adrian's patches in, just leave current behaviour as the default. --=20 Pawel Jakub Dawidek http://www.wheelsystems.com FreeBSD committer http://www.FreeBSD.org Am I Evil? Yes, I Am! http://tupytaj.pl --OOq1TgGhe8eTwFBO Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlCyIX8ACgkQForvXbEpPzQlJQCeIlqNSY/OZwVQHNSHjq1nQxsl c50AoJRjD25nFJxD+fAuVT4q0EJZXVBQ =ReUf -----END PGP SIGNATURE----- --OOq1TgGhe8eTwFBO-- From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 25 13:48:26 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0330F92F; Sun, 25 Nov 2012 13:48:26 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from mail-la0-f54.google.com (mail-la0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id C3D448FC08; Sun, 25 Nov 2012 13:48:24 +0000 (UTC) Received: by mail-la0-f54.google.com with SMTP id j13so9846135lah.13 for ; Sun, 25 Nov 2012 05:48:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=pYYhZu8E2pPTj413sT1sGPEGOm84VyS5rufs5O1XPn8=; b=UX7kXfFTT4sFMjqUZX8qjMW8NW1MalkBhuHdL87B5ViDJ1VXAG1oQc/XwHcy/RYZKj c1JhJEY/n0kGEPbYQZTmDvdcFSXOVSNBKus3m99/1iwoO6V78mqC0fYDQWVbTgtD9DXT XyrQ1Ni4x2MNoa/Vok7LgeMeDhefZkbCCz6pLQ5Re09qoMgc6KZDqh73vpSSaPtPKNo6 q6FDl2jKmLC8crxwttXDAb70YZN0npOFNldijBrlGxpmNqyQsXHnB0KNju3ipH4ROyt8 AautPe6bmxbxxdvjmNGERyzyECa0t9sknmrF9SOm/o8nFywwuI+BK/cgsARfQX7Dyx3w sstg== MIME-Version: 1.0 Received: by 10.112.87.40 with SMTP id u8mr3892069lbz.50.1353851303661; Sun, 25 Nov 2012 05:48:23 -0800 (PST) Sender: asmrookie@gmail.com Received: by 10.112.134.5 with HTTP; Sun, 25 Nov 2012 05:48:23 -0800 (PST) In-Reply-To: <20121125134743.GK1460@garage.freebsd.pl> References: <20121125123920.GI1460@garage.freebsd.pl> <20121125131252.GJ1460@garage.freebsd.pl> <20121125134743.GK1460@garage.freebsd.pl> Date: Sun, 25 Nov 2012 13:48:23 +0000 X-Google-Sender-Auth: uMTFE7q4eFLBVQYRQO5gz28i9oo Message-ID: Subject: Re: [RFQ] make witness panic an option From: Attilio Rao To: Pawel Jakub Dawidek Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-hackers@freebsd.org" , Adrian Chadd , Giovanni Trematerra , freebsd-arch@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: attilio@FreeBSD.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Nov 2012 13:48:26 -0000 On Sun, Nov 25, 2012 at 1:47 PM, Pawel Jakub Dawidek wrote: > On Sun, Nov 25, 2012 at 01:37:19PM +0000, Attilio Rao wrote: >> On Sun, Nov 25, 2012 at 1:12 PM, Pawel Jakub Dawidek wrote: >> > On Sun, Nov 25, 2012 at 12:42:16PM +0000, Attilio Rao wrote: >> >> On Sun, Nov 25, 2012 at 12:39 PM, Pawel Jakub Dawidek wrote: >> >> > WITNESS is a development tool. We don't ship production kernels with >> >> > WITNESS even compiled in. What is more efficient use of developer time: >> >> > going through full reboot cycle every time or reading the warning from >> >> > console, unloading a module, fixing the bug and loading it again? >> >> > >> >> > And if this option is turned off by default what is the problem? >> >> >> >> Yes, so, why do you write here? >> > >> > I'm trying to understand why do you object. Until now the only concern >> > you have that I found is that you are afraid of it being abused. I don't >> > see how this can be abused if it is turned off by default. If someone >> > will commit a change that will turn it on by default, believe me, I'll >> > unleash hell personally. >> >> So I don't understand what are you proposing. >> You are not proposing to switch BLESSING on and you are not proposing >> to import Adrian's patches in, if I get it correctly. I don't >> understand then. > > I propose to get Adrian's patches in, just leave current behaviour as > the default. So if I tell that I'm afraid this mechanism will be abused (and believe me, I really wanted to trimm out BLESSING stuff also for the same reason) and you say "you can't see how" there is not much we can discuss. You know how I think, there is no need to wait for me to reconsider, because I don't believe this will happen with arguments like "I don't think", "I don't agree", etc. Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 25 13:53:57 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 90B7CBDF; Sun, 25 Nov 2012 13:53:57 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (wojtek.tensor.gdynia.pl [89.206.35.99]) by mx1.freebsd.org (Postfix) with ESMTP id E426F8FC14; Sun, 25 Nov 2012 13:53:56 +0000 (UTC) Received: from wojtek.tensor.gdynia.pl (localhost [127.0.0.1]) by wojtek.tensor.gdynia.pl (8.14.5/8.14.5) with ESMTP id qAPDrgaF008470; Sun, 25 Nov 2012 14:53:42 +0100 (CET) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from localhost (wojtek@localhost) by wojtek.tensor.gdynia.pl (8.14.5/8.14.5/Submit) with ESMTP id qAPDrg5A008467; Sun, 25 Nov 2012 14:53:42 +0100 (CET) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Date: Sun, 25 Nov 2012 14:53:42 +0100 (CET) From: Wojciech Puchar To: Eitan Adler Subject: Re: old style kernel configuration 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 X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (wojtek.tensor.gdynia.pl [127.0.0.1]); Sun, 25 Nov 2012 14:53:43 +0100 (CET) Cc: Garrett Cooper , FreeBSD Hackers , Benjamin Kaduk X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Nov 2012 13:53:57 -0000 > and > - what are the man differences between the old and new ways. > > and it is starting to turn into a flame/bikeshed. i just don't see what's wrong in SIMPLE procedure that just use existing C compiler and just sys sources > > Thanks for the information. I'll restore the documentation with > updated information shortly. > > > -- > Eitan Adler > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 25 14:01:19 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7DC9EEE7; Sun, 25 Nov 2012 14:01:19 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from mail-la0-f54.google.com (mail-la0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id A67EC8FC12; Sun, 25 Nov 2012 14:01:18 +0000 (UTC) Received: by mail-la0-f54.google.com with SMTP id j13so9850830lah.13 for ; Sun, 25 Nov 2012 06:01:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=pHhZLCx3MEByWkSqgclgU6JxDW6v9mXvSmB/uxx6iis=; b=XNIvC83IBPsrJGZZsAvx21/DiB21efzLR9+WPgNkZhHRjUrkShMEznCkTHdDKHIs5d rQWUBZHLEhGFBncqej+759e+bwYN3hHHd7y6MZch7MRBDr+tFE2wIxU8OQrQX3i0ST6v coFIhJHPUhy1U1Ul/NDPe1MjvcJ+TFL0ISKoQg2AV0zFMPyqvLhl+SScatfWyF6v475b mkM0jMBqG1KuUnB07RQLD8xqkWhR5udaexcl1GJ/ywFLuUMTcwVYeuuxRvG4LC3lY32D I80C1guFrPDAvx2nEIc0HpVEEhT4IvQNSHnB+xMnkts8IyD6HdmwmsV2baW9wWkL2NN0 3ubw== MIME-Version: 1.0 Received: by 10.152.104.50 with SMTP id gb18mr8453539lab.9.1353852076629; Sun, 25 Nov 2012 06:01:16 -0800 (PST) Sender: asmrookie@gmail.com Received: by 10.112.134.5 with HTTP; Sun, 25 Nov 2012 06:01:16 -0800 (PST) In-Reply-To: <50B21545.5060807@FreeBSD.org> References: <50A5F12C.1050902@FreeBSD.org> <50A63D1D.9090500@FreeBSD.org> <50A65208.4050804@FreeBSD.org> <50B21545.5060807@FreeBSD.org> Date: Sun, 25 Nov 2012 14:01:16 +0000 X-Google-Sender-Auth: a06cDD71dlzgDx1OZ8UBbxKRbmY Message-ID: Subject: Re: stop_cpus_hard when multiple CPUs are panicking from an NMI From: Attilio Rao To: Andriy Gapon Content-Type: text/plain; charset=UTF-8 Cc: freebsd-hackers@freebsd.org, Ryan Stone X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: attilio@FreeBSD.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Nov 2012 14:01:19 -0000 On Sun, Nov 25, 2012 at 12:55 PM, Andriy Gapon wrote: > on 25/11/2012 14:29 Attilio Rao said the following: >> I think the patch you propose makes such effects even worse, because >> it disables interrupts in generic_stop_cpus(). >> What I suggest to do, is the following: >> - The CPU which wins the race for generic_stop_cpus also signals the >> CPUs it is willing to stop on a global mask >> - Another CPU entering generic_stop_cpus() and loosing the race, >> checks the mask of cpus which might be stopped and stops itself if >> necessary (ie. not yet done). We must be careful with races here, but >> I'm confindent this can be done easily enough. > > I think that you either misunderstood my patch or I misunderstand your > suggestion, because my patch does exactly what you wrote above. The patch is someway incomplete: - I don't think that we need specific checks in cpustop_handler() (and if you have added them to prevent races, I don't think they are enough, see below) - setting of "stopping_cpus" map must happen atomically/before the stopper_cpu cpuid setting, otherwise some CPUs may end up using a NULL mask in the check - Did you consider the races about when a stop and restart request happen just after the CPU_ISSET() check? I think CPUs can deadlock there. - I'm very doubious about the spinlock_enter() stuff, I think I can just make the problem worse atm. However you are right, the concept of your patch is the same I really wanted to get, we maybe need to just lift it up a bit. In the while I also double-checked suspended_cpus and I don't think there are real showstoppers to have it in stopped_cpus map. Thanks, Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 25 14:05:10 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E0E85138; Sun, 25 Nov 2012 14:05:09 +0000 (UTC) (envelope-from pawel@dawidek.net) Received: from mail.dawidek.net (garage.dawidek.net [91.121.88.72]) by mx1.freebsd.org (Postfix) with ESMTP id 8EDC88FC08; Sun, 25 Nov 2012 14:05:09 +0000 (UTC) Received: from localhost (89-73-195-149.dynamic.chello.pl [89.73.195.149]) by mail.dawidek.net (Postfix) with ESMTPSA id 1AEC3C67; Sun, 25 Nov 2012 15:03:21 +0100 (CET) Date: Sun, 25 Nov 2012 15:06:21 +0100 From: Pawel Jakub Dawidek To: Attilio Rao Subject: Re: [RFQ] make witness panic an option Message-ID: <20121125140620.GL1460@garage.freebsd.pl> References: <20121125123920.GI1460@garage.freebsd.pl> <20121125131252.GJ1460@garage.freebsd.pl> <20121125134743.GK1460@garage.freebsd.pl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="7vAdt9JsdkkzRPKN" Content-Disposition: inline In-Reply-To: X-OS: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "freebsd-hackers@freebsd.org" , Adrian Chadd , Giovanni Trematerra , freebsd-arch@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Nov 2012 14:05:10 -0000 --7vAdt9JsdkkzRPKN Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Nov 25, 2012 at 01:48:23PM +0000, Attilio Rao wrote: > On Sun, Nov 25, 2012 at 1:47 PM, Pawel Jakub Dawidek wr= ote: > > On Sun, Nov 25, 2012 at 01:37:19PM +0000, Attilio Rao wrote: > >> On Sun, Nov 25, 2012 at 1:12 PM, Pawel Jakub Dawidek = wrote: > >> > On Sun, Nov 25, 2012 at 12:42:16PM +0000, Attilio Rao wrote: > >> >> On Sun, Nov 25, 2012 at 12:39 PM, Pawel Jakub Dawidek wrote: > >> >> > WITNESS is a development tool. We don't ship production kernels w= ith > >> >> > WITNESS even compiled in. What is more efficient use of developer= time: > >> >> > going through full reboot cycle every time or reading the warning= from > >> >> > console, unloading a module, fixing the bug and loading it again? > >> >> > > >> >> > And if this option is turned off by default what is the problem? > >> >> > >> >> Yes, so, why do you write here? > >> > > >> > I'm trying to understand why do you object. Until now the only conce= rn > >> > you have that I found is that you are afraid of it being abused. I d= on't > >> > see how this can be abused if it is turned off by default. If someone > >> > will commit a change that will turn it on by default, believe me, I'= ll > >> > unleash hell personally. > >> > >> So I don't understand what are you proposing. > >> You are not proposing to switch BLESSING on and you are not proposing > >> to import Adrian's patches in, if I get it correctly. I don't > >> understand then. > > > > I propose to get Adrian's patches in, just leave current behaviour as > > the default. >=20 > So if I tell that I'm afraid this mechanism will be abused (and > believe me, I really wanted to trimm out BLESSING stuff also for the > same reason) and you say "you can't see how" there is not much we can > discuss. This is not what I said. I would see it as abuse if someone will suddenly decided to turn off locking assertions by default in FreeBSD base. If he will turn that off on his private machine be it to speed up his development (a good thing) or to shut up important lock assertion (a bad thing) this is entirely his decision. He can already do that having all the source code, its just more complex. Make tools, not policies. BLESSING is totally different subject. You were afraid that people will start to silence LORs they don't understand by committing blessed pairs to FreeBSD base. And this situation is abuse and I fully agree, but I also still think BLESSING is useful, although I recognize it might be hard to prevent mentioned abuse. In case of Adrian's patch nothing will change in how we enforce locking assertions in FreeBSD base. > You know how I think, there is no need to wait for me to reconsider, > because I don't believe this will happen with arguments like "I don't > think", "I don't agree", etc. I provide valid arguments with I hope proper explanation, you choose not to address them or ignore them and I hope this will change:) --=20 Pawel Jakub Dawidek http://www.wheelsystems.com FreeBSD committer http://www.FreeBSD.org Am I Evil? Yes, I Am! http://tupytaj.pl --7vAdt9JsdkkzRPKN Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlCyJdwACgkQForvXbEpPzTHCACeMiM0zXHueZ1aJcdEX56NOsXP VskAoLbBLZH742DdygjBFTZYOpxAbHrz =Hya/ -----END PGP SIGNATURE----- --7vAdt9JsdkkzRPKN-- From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 25 14:09:02 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D2C222EE; Sun, 25 Nov 2012 14:09:02 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id A45478FC08; Sun, 25 Nov 2012 14:09:01 +0000 (UTC) Received: by mail-lb0-f182.google.com with SMTP id go10so7260452lbb.13 for ; Sun, 25 Nov 2012 06:09:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=qZykcAZoW0RKyTdsvWkmXfPC1+4mvsyvaDFlNLBCB4k=; b=ixSSh9UNyvjl/RKLnTltCE+Ci5V7LczsCeFF6wEPt6YksJ8iE0dFOc4cZykoVj1meu TNBVkTwS7EGmnSeLBWBO1kr36e2Q5lPneE6KqZyFQnOuOoMpZf361xe6HhBSbbp4a96r t18i00lxJRSpjGhOIOAx1sKBosZ3n8+kFK+zd6WMpSt546pRpE0LBI+U3I3G8GofQnoT gQmhYiptEaOP84zHI3zZiHOZjqqM6qXVffro/VtmRlGa+DpOt/3pZaeoPQnOJem1WMfx F0DA2LLU1304HdbwsUDDHgR3aPWFfZv8AAslygYnz8AHKy6Ou/ZrC9E8IG003yCTgmfY qvAg== MIME-Version: 1.0 Received: by 10.152.132.3 with SMTP id oq3mr8189422lab.18.1353852540239; Sun, 25 Nov 2012 06:09:00 -0800 (PST) Sender: asmrookie@gmail.com Received: by 10.112.134.5 with HTTP; Sun, 25 Nov 2012 06:09:00 -0800 (PST) In-Reply-To: <20121125140620.GL1460@garage.freebsd.pl> References: <20121125123920.GI1460@garage.freebsd.pl> <20121125131252.GJ1460@garage.freebsd.pl> <20121125134743.GK1460@garage.freebsd.pl> <20121125140620.GL1460@garage.freebsd.pl> Date: Sun, 25 Nov 2012 14:09:00 +0000 X-Google-Sender-Auth: NgLPQcbFg0D9VZQzanBEbdILWZA Message-ID: Subject: Re: [RFQ] make witness panic an option From: Attilio Rao To: Pawel Jakub Dawidek Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-hackers@freebsd.org" , Adrian Chadd , Giovanni Trematerra , freebsd-arch@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: attilio@FreeBSD.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Nov 2012 14:09:03 -0000 On Sun, Nov 25, 2012 at 2:06 PM, Pawel Jakub Dawidek wrote: > On Sun, Nov 25, 2012 at 01:48:23PM +0000, Attilio Rao wrote: >> On Sun, Nov 25, 2012 at 1:47 PM, Pawel Jakub Dawidek wrote: >> > On Sun, Nov 25, 2012 at 01:37:19PM +0000, Attilio Rao wrote: >> >> On Sun, Nov 25, 2012 at 1:12 PM, Pawel Jakub Dawidek wrote: >> >> > On Sun, Nov 25, 2012 at 12:42:16PM +0000, Attilio Rao wrote: >> >> >> On Sun, Nov 25, 2012 at 12:39 PM, Pawel Jakub Dawidek wrote: >> >> >> > WITNESS is a development tool. We don't ship production kernels with >> >> >> > WITNESS even compiled in. What is more efficient use of developer time: >> >> >> > going through full reboot cycle every time or reading the warning from >> >> >> > console, unloading a module, fixing the bug and loading it again? >> >> >> > >> >> >> > And if this option is turned off by default what is the problem? >> >> >> >> >> >> Yes, so, why do you write here? >> >> > >> >> > I'm trying to understand why do you object. Until now the only concern >> >> > you have that I found is that you are afraid of it being abused. I don't >> >> > see how this can be abused if it is turned off by default. If someone >> >> > will commit a change that will turn it on by default, believe me, I'll >> >> > unleash hell personally. >> >> >> >> So I don't understand what are you proposing. >> >> You are not proposing to switch BLESSING on and you are not proposing >> >> to import Adrian's patches in, if I get it correctly. I don't >> >> understand then. >> > >> > I propose to get Adrian's patches in, just leave current behaviour as >> > the default. >> >> So if I tell that I'm afraid this mechanism will be abused (and >> believe me, I really wanted to trimm out BLESSING stuff also for the >> same reason) and you say "you can't see how" there is not much we can >> discuss. > > This is not what I said. I would see it as abuse if someone will > suddenly decided to turn off locking assertions by default in FreeBSD > base. > > If he will turn that off on his private machine be it to speed up his > development (a good thing) or to shut up important lock assertion (a bad > thing) this is entirely his decision. He can already do that having all > the source code, its just more complex. Make tools, not policies. > > BLESSING is totally different subject. You were afraid that people will > start to silence LORs they don't understand by committing blessed pairs > to FreeBSD base. And this situation is abuse and I fully agree, but I > also still think BLESSING is useful, although I recognize it might be > hard to prevent mentioned abuse. > > In case of Adrian's patch nothing will change in how we enforce locking > assertions in FreeBSD base. > >> You know how I think, there is no need to wait for me to reconsider, >> because I don't believe this will happen with arguments like "I don't >> think", "I don't agree", etc. > > I provide valid arguments with I hope proper explanation, you choose not > to address them or ignore them and I hope this will change:) I'm not ignoring them, I'm saying that your arguments are not enough convincing to me. And really, giving the possibility to turn off assertions in witness is already a dangerous tool I want to avoid (not only related to BLESSING). If there are some cases that deserve a panic, we might just get it, not matter how sysctls are setup. However it seems to me I'm just saying the same thing since 20 e-mails, please drop me from CC in your next follow up. As I said, you can commit all the changes you want (assuming they are technically correct) even if I would appreciate my disagreement is expressed in the commit message. Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 25 14:20:14 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C37FD60A; Sun, 25 Nov 2012 14:20:14 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from mail-la0-f54.google.com (mail-la0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 911C58FC08; Sun, 25 Nov 2012 14:20:13 +0000 (UTC) Received: by mail-la0-f54.google.com with SMTP id j13so9859159lah.13 for ; Sun, 25 Nov 2012 06:20:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=cnNqoQPukRmNldxMx9UofAenoA3cai5nayBCAeWjFvo=; b=E0KfcDGGr+KQEZ/nPVcPELLb8AqrZn/f7EhpeQkoccD6FCqrJwsQXJ0i/UjkdMVTzx rG4xBoqzxPpTl2xp/+tQvr0H+nP/430Ti8oGVilHRO79oDvecUfax0ddv9bjIWx3dyjj rnvqU4fFeiK/ZNh++/3/3D04wAHCKOUEa0kydl8Lj0YqljIZ/UBHYT6UglKMSO08yN43 pti+hCgwBjZHTK3x00P9ToaHRnzx6VzFmCdji6ZqEg4Lz2QAHb3X7beRusWdcmDoUgy3 1yse8QlqaesAIC/dMisCeFnRYIpKF3Rr0vNK1hJ9CgQIn3xptssrxosX06hA9vk2Jgyq cA1Q== MIME-Version: 1.0 Received: by 10.152.123.103 with SMTP id lz7mr8223554lab.21.1353853212272; Sun, 25 Nov 2012 06:20:12 -0800 (PST) Sender: asmrookie@gmail.com Received: by 10.112.134.5 with HTTP; Sun, 25 Nov 2012 06:20:12 -0800 (PST) In-Reply-To: <20121125131252.GJ1460@garage.freebsd.pl> References: <20121125123920.GI1460@garage.freebsd.pl> <20121125131252.GJ1460@garage.freebsd.pl> Date: Sun, 25 Nov 2012 14:20:12 +0000 X-Google-Sender-Auth: VIDSUp_4vKS6zzsIoSf3vrNnqRY Message-ID: Subject: Re: [RFQ] make witness panic an option From: Attilio Rao To: Pawel Jakub Dawidek Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-hackers@freebsd.org" , Adrian Chadd , Giovanni Trematerra , freebsd-arch@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: attilio@FreeBSD.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Nov 2012 14:20:14 -0000 On Sun, Nov 25, 2012 at 1:12 PM, Pawel Jakub Dawidek wrote: > On Sun, Nov 25, 2012 at 12:42:16PM +0000, Attilio Rao wrote: >> On Sun, Nov 25, 2012 at 12:39 PM, Pawel Jakub Dawidek wrote: >> > WITNESS is a development tool. We don't ship production kernels with >> > WITNESS even compiled in. What is more efficient use of developer time: >> > going through full reboot cycle every time or reading the warning from >> > console, unloading a module, fixing the bug and loading it again? >> > >> > And if this option is turned off by default what is the problem? >> >> Yes, so, why do you write here? > > I'm trying to understand why do you object. Until now the only concern > you have that I found is that you are afraid of it being abused. I don't > see how this can be abused if it is turned off by default. If someone > will commit a change that will turn it on by default, believe me, I'll > unleash hell personally. > > As I said, WITNESS is development tool, a very handy one. This doesn't > mean we can't make it even more handy. It is there to help find bugs > faster, right? Adrian is proposing a change that will make it help to > find and fix bugs maybe even faster. > >> Go ahead and fix BLESSED, make it the default, etc. > > This is another story, but BLESSED is much less controversial to me. > It is turned off by default in assumption that all the code that runs in > our kernel is developed for FreeBSD, which is not true. For example ZFS > is, I think, the biggest locking consumer in our kernel (around 120 > locks), which wasn't originally developed for FreeBSD and locking order > was verified using different tools. Now on FreeBSD it triggers massive > LOR warnings from WITNESS, eventhough those are not bugs. At some point > I verified many of them and they were all false-positives, so I simply > turned off WITNESS warnings for ZFS locks. Why? Because BLESSED is > turned off in fear of abuse, and this is turn is the cause of mentioned > hack in ZFS. Just a few notes about this: to my knowledge you never discussed publically this. WITNESS is not a perfect tool and it has several issues (I tried to summarize them a bit at the beginning of this thread), where the biggest problem is that its file/line approach doesn't help when willing to shutdown specific LOR without shutting down all of them involving the lock pair, etc. I have no idea what are the problems you are facing here with WITNESS and ZFS but if you could summarize them we can work on getting something which is useful also with ZFS. Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 25 14:39:34 2012 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2CFFFDF0; Sun, 25 Nov 2012 14:39:34 +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 402848FC13; Sun, 25 Nov 2012 14:39:32 +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 QAA19065; Sun, 25 Nov 2012 16:39:31 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1TcdMp-000KzT-7e; Sun, 25 Nov 2012 16:39:31 +0200 Message-ID: <50B22DA0.9080207@FreeBSD.org> Date: Sun, 25 Nov 2012 16:39:28 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: attilio@FreeBSD.org Subject: Re: stop_cpus_hard when multiple CPUs are panicking from an NMI References: <50A5F12C.1050902@FreeBSD.org> <50A63D1D.9090500@FreeBSD.org> <50A65208.4050804@FreeBSD.org> <50B21545.5060807@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@FreeBSD.org, Ryan Stone X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Nov 2012 14:39:34 -0000 on 25/11/2012 16:01 Attilio Rao said the following: > On Sun, Nov 25, 2012 at 12:55 PM, Andriy Gapon wrote: >> on 25/11/2012 14:29 Attilio Rao said the following: >>> I think the patch you propose makes such effects even worse, because >>> it disables interrupts in generic_stop_cpus(). >>> What I suggest to do, is the following: >>> - The CPU which wins the race for generic_stop_cpus also signals the >>> CPUs it is willing to stop on a global mask >>> - Another CPU entering generic_stop_cpus() and loosing the race, >>> checks the mask of cpus which might be stopped and stops itself if >>> necessary (ie. not yet done). We must be careful with races here, but >>> I'm confindent this can be done easily enough. >> >> I think that you either misunderstood my patch or I misunderstand your >> suggestion, because my patch does exactly what you wrote above. > > The patch is someway incomplete: > - I don't think that we need specific checks in cpustop_handler() (and > if you have added them to prevent races, I don't think they are > enough, see below) The check is to cover the following scenario: - two CPUs race in hard-stop scenario, and both are in NMI contexts - one CPU wins and the other does spinning right in generic_stop_cpus - NMI for the spinning CPU is blocked and remains pending - the winning CPU releases all other CPUs - the spinning CPU exits the NMI context and get the NMI which was pending > - setting of "stopping_cpus" map must happen atomically/before the > stopper_cpu cpuid setting, otherwise some CPUs may end up using a NULL > mask in the check Not NULL, but empty or stale. But a very good point, I agree. The logic must be redone. > - Did you consider the races about when a stop and restart request > happen just after the CPU_ISSET() check? I think CPUs can deadlock > there. Yeah, good point again. This seems to be a different side of the issue above. stopping_cpus is probably a bad idea. > - I'm very doubious about the spinlock_enter() stuff, I think I can > just make the problem worse atm. Well, this is where I disagree. I think that cpu_stop must already be called in context which effectively disable pre-emption and interrupts. The added spinlock_enter() stuff is kind of a safety belt to make things more explicit, but it could be changed into some sort of an assert if that's possible. > However you are right, the concept of your patch is the same I really > wanted to get, we maybe need to just lift it up a bit. I agree. To add some gas to the fire. Do you recall my wish to drop the mask parameter from the stop calls? If that was done then it would be simpler to handle these things. In that case only "stopper_cpu" ID (master/winner) would be needed. > In the while I also double-checked suspended_cpus and I don't think > there are real showstoppers to have it in stopped_cpus map. -- Andriy Gapon From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 25 17:32:44 2012 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8121BF4E for ; Sun, 25 Nov 2012 17:32:44 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from monday.kientzle.com (99-115-135-74.uvs.sntcca.sbcglobal.net [99.115.135.74]) by mx1.freebsd.org (Postfix) with ESMTP id 304DD8FC08 for ; Sun, 25 Nov 2012 17:32:43 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id qAPHW84G033168; Sun, 25 Nov 2012 17:32:08 GMT (envelope-from kientzle@freebsd.org) Received: from [192.168.2.143] (CiscoE3000 [192.168.1.65]) by kientzle.com with SMTP id hia3fata5tdehrpjxkv4rb62ci; Sun, 25 Nov 2012 17:32:08 +0000 (UTC) (envelope-from kientzle@freebsd.org) Subject: Re: FreeBSD on RaspberryPi Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=windows-1252 From: Tim Kientzle In-Reply-To: <9E4DA920-BE72-4AA0-8159-43205CDEF5CD@bluezbox.com> Date: Sun, 25 Nov 2012 09:32:08 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: References: <31C904E6-F230-4187-AE32-F9A7B1A7C38E@freebsd.org> <4A5E03E5-3295-4FD4-9A06-7D1C4E9E0C12@freebsd.org> <9E4DA920-BE72-4AA0-8159-43205CDEF5CD@bluezbox.com> To: Oleksandr Tymoshenko X-Mailer: Apple Mail (2.1283) Cc: FreeBSD Hackers , Alexander Yerenkow X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Nov 2012 17:32:44 -0000 On Nov 24, 2012, at 8:01 PM, Oleksandr Tymoshenko wrote: >=20 > On 2012-11-24, at 4:47 PM, Tim Kientzle wrote: >=20 >>=20 >> On Nov 24, 2012, at 11:13 AM, Alexander Yerenkow wrote: >>=20 >>>=20 >>>=20 >>> 2012/11/24 Tim Kientzle >>> On Nov 7, 2012, at 8:09 AM, Alexander Yerenkow wrote: >>>=20 >>>>> Such experiments was tried by me and others in August; I got = framebuffer worked in rca/hdmi; =85 >>>=20 >>> On Nov 8, 2012, at 11:12 PM, Alexander Yerenkow wrote: >>>=20 >>>> It was plain current with plain RPIB kernel config, and for graphic = you should uncomment there partition about sysconsole; serial then = disabled; >>>> Also, if you want ethernet - it's ue device, which also worked, but = produced hangs for me in past (Hans IIRC already fixed.this). >>>> I'll have some time this weekend, feel free to contact me by gtalk = or else, I will play around with my rpi with both serials and vide = modes. >>>=20 >>> Alexander, >>>=20 >>> I tried uncommenting the 'sc' entries in the RPI-B kernel >>> config that's in -CURRENT right now. >>>=20 >>> All entries, right? >>=20 >> Yes, I uncommented all entries. >>=20 >>> And how do you booting, via usb-flash, or via SD card? >>=20 >> Via SD-card. I'm using the image from here: >> = http://people.freebsd.org/~kientzle/FreeBSD-RPI-B-r242362-2012-10-30.img.x= z >> and swapping out the kernel. >>=20 >>> I'll build now CURRENT, will look if I got same.=20 >>=20 >> Thanks. I'd appreciate knowing whether it works for you. >>=20 >> If you can get it to work, I'd appreciate any details you can give. >=20 > Tim, >=20 > I'm almost done with getting kernel working with latest raspberry Pi = firmware. Just need > to figure out how to make ubldr pass FDT pointer from u-boot to kernel = and handle=20 > /reserve/ information in ARM machdep code.=20 Let me know if you need help with this. I've worked with the ubldr FDT code recently. > Meanwhile I suggest editing .dts file manually. Fill out "display" = node properties with proper > display resolution and depth. Also add ukbd driver. That should get = you working console. I'll try that. I'm curious: why is this information coming from the DTS? That seems pretty complex; I thought that the console code would query this information via the mailbox interface. Tim =20= From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 25 18:05:45 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 48A7A6E0; Sun, 25 Nov 2012 18:05:45 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id 8651E8FC12; Sun, 25 Nov 2012 18:05:44 +0000 (UTC) Received: by mail-lb0-f182.google.com with SMTP id go10so7357866lbb.13 for ; Sun, 25 Nov 2012 10:05:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=fj/Ch2vYBmUbefjW5oxM0i5CoeuVR1BNzv1sevGFXrw=; b=xSIRYqoV319H0kS43aAdS0XXOefGb2+148b+qJtqEa8ihr2UtvlYW3a34g8AaCX7oI HrYmVGxZHty8oG0u5SbTmBZynv4iCc9vMmawu/IE2pVXv8G1CsQiv8rDaYsuOuCdfI21 5mPuoF9bHQFWR8brVjd47D+ptdlf1ZGfVtIkv5geBjsXVkvbfqCUArbNAJSpJ7LQ2siI 9PEusjckaGIbSfQ8BfXZnZHfCJfm+p7uSm5ckExtiwWkdSmb+X4KpOsFfaZX1+0DnUC4 YpnrdRhqjNlTrMbLcjJ87bEU13YJoT8IB484G2oZwExeu83hlWQRg/KGb/jp4DasntLM s5Hg== MIME-Version: 1.0 Received: by 10.112.24.41 with SMTP id r9mr4032080lbf.115.1353866743281; Sun, 25 Nov 2012 10:05:43 -0800 (PST) Sender: asmrookie@gmail.com Received: by 10.112.134.5 with HTTP; Sun, 25 Nov 2012 10:05:43 -0800 (PST) In-Reply-To: <50B22DA0.9080207@FreeBSD.org> References: <50A5F12C.1050902@FreeBSD.org> <50A63D1D.9090500@FreeBSD.org> <50A65208.4050804@FreeBSD.org> <50B21545.5060807@FreeBSD.org> <50B22DA0.9080207@FreeBSD.org> Date: Sun, 25 Nov 2012 19:05:43 +0100 X-Google-Sender-Auth: J17eA8mJLy5cFfHpa9pQu1SOthE Message-ID: Subject: Re: stop_cpus_hard when multiple CPUs are panicking from an NMI From: Attilio Rao To: Andriy Gapon Content-Type: text/plain; charset=UTF-8 Cc: freebsd-hackers@freebsd.org, Ryan Stone X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: attilio@FreeBSD.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Nov 2012 18:05:45 -0000 On Sun, Nov 25, 2012 at 3:39 PM, Andriy Gapon wrote: > on 25/11/2012 16:01 Attilio Rao said the following: >> On Sun, Nov 25, 2012 at 12:55 PM, Andriy Gapon wrote: >>> on 25/11/2012 14:29 Attilio Rao said the following: >>>> I think the patch you propose makes such effects even worse, because >>>> it disables interrupts in generic_stop_cpus(). >>>> What I suggest to do, is the following: >>>> - The CPU which wins the race for generic_stop_cpus also signals the >>>> CPUs it is willing to stop on a global mask >>>> - Another CPU entering generic_stop_cpus() and loosing the race, >>>> checks the mask of cpus which might be stopped and stops itself if >>>> necessary (ie. not yet done). We must be careful with races here, but >>>> I'm confindent this can be done easily enough. >>> >>> I think that you either misunderstood my patch or I misunderstand your >>> suggestion, because my patch does exactly what you wrote above. >> >> The patch is someway incomplete: >> - I don't think that we need specific checks in cpustop_handler() (and >> if you have added them to prevent races, I don't think they are >> enough, see below) > > The check is to cover the following scenario: > - two CPUs race in hard-stop scenario, and both are in NMI contexts Please consider also another type of (similar race): two CPUs race in (normal) stop scenario and the loser is with interrupt disabled. I don't this will be completely fatal, but I'm sure it can lead to issues (double stop, etc.). > - one CPU wins and the other does spinning right in generic_stop_cpus > - NMI for the spinning CPU is blocked and remains pending > - the winning CPU releases all other CPUs > - the spinning CPU exits the NMI context and get the NMI which was pending > >> - setting of "stopping_cpus" map must happen atomically/before the >> stopper_cpu cpuid setting, otherwise some CPUs may end up using a NULL >> mask in the check > > Not NULL, but empty or stale. But a very good point, I agree. > The logic must be redone. > >> - Did you consider the races about when a stop and restart request >> happen just after the CPU_ISSET() check? I think CPUs can deadlock >> there. > > Yeah, good point again. This seems to be a different side of the issue above. > stopping_cpus is probably a bad idea. > >> - I'm very doubious about the spinlock_enter() stuff, I think I can >> just make the problem worse atm. > > Well, this is where I disagree. I think that cpu_stop must already be called in > context which effectively disable pre-emption and interrupts. > The added spinlock_enter() stuff is kind of a safety belt to make things more > explicit, but it could be changed into some sort of an assert if that's possible. Maybe it can be come really safe once we take care of all the races involved and reported above. I reserve to suspend my judgement until we don't care of the other races. > >> However you are right, the concept of your patch is the same I really >> wanted to get, we maybe need to just lift it up a bit. > > I agree. > > To add some gas to the fire. Do you recall my wish to drop the mask parameter > from the stop calls? If that was done then it would be simpler to handle these > things. In that case only "stopper_cpu" ID (master/winner) would be needed. If you really want to do something like that please rename s/generic_stop_cpus/generic_stop_butself() or similar convention and I may be not opposed to it. Thanks, Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 25 18:20:45 2012 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1E9A1C4B; Sun, 25 Nov 2012 18:20:45 +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 32ACC8FC16; Sun, 25 Nov 2012 18:20:43 +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 UAA20654; Sun, 25 Nov 2012 20:20:42 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1Tcgos-000L7U-Lc; Sun, 25 Nov 2012 20:20:42 +0200 Message-ID: <50B26179.4040205@FreeBSD.org> Date: Sun, 25 Nov 2012 20:20:41 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: attilio@FreeBSD.org Subject: Re: stop_cpus_hard when multiple CPUs are panicking from an NMI References: <50A5F12C.1050902@FreeBSD.org> <50A63D1D.9090500@FreeBSD.org> <50A65208.4050804@FreeBSD.org> <50B21545.5060807@FreeBSD.org> <50B22DA0.9080207@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@FreeBSD.org, Ryan Stone X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Nov 2012 18:20:45 -0000 on 25/11/2012 20:05 Attilio Rao said the following: > If you really want to do something like that please rename > s/generic_stop_cpus/generic_stop_butself() or similar convention and I > may be not opposed to it. As we discussed before, anything else besides "all but self" does not make sense. So I am not sure what's the point of being that verbose in the naming. -- Andriy Gapon From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 25 18:28:02 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9DF2EF0A for ; Sun, 25 Nov 2012 18:28:02 +0000 (UTC) (envelope-from trafdev@mail.ru) Received: from smtp44.i.mail.ru (smtp44.i.mail.ru [94.100.177.104]) by mx1.freebsd.org (Postfix) with ESMTP id E2CE08FC13 for ; Sun, 25 Nov 2012 18:28:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mail.ru; s=mail; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=DApGwUbR+CXQfo3/9HDbjbIJwwqVqeXOekTfHvT6EuI=; b=VU5iZt7K46dRn9zZ+TtRE9Av85YoGD4LmaWVZRf+MWhP74CcpemLFONNZMvwED2gIr/Aa5ZAL+hZEic3dcO/vxQy2oIrQCFo0624sMZRrpa9mtdDIB2eQRkX+wUccUv6; Received: from [76.126.253.89] (port=16603 helo=[192.168.1.117]) by smtp44.i.mail.ru with esmtpa (envelope-from ) id 1Tcgvp-0002Ez-6m; Sun, 25 Nov 2012 22:27:53 +0400 Message-ID: <50B26326.3070008@mail.ru> Date: Sun, 25 Nov 2012 10:27:50 -0800 From: trafdev User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121110 Thunderbird/16.0.2 MIME-Version: 1.0 To: Kim Culhan Subject: Re: postfix mail server infected ? References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam: Not detected X-Mras: Ok Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Nov 2012 18:28:02 -0000 Hi. Can you please point me to some discussions and solutions related to this problem? Thanks. On Sun Nov 25 02:43:10 2012, Kim Culhan wrote: > On Sat, November 24, 2012 1:08 pm, trafdev wrote: > > Hi. I've a dedicated stand-alone FreeBSD server: > > > uname -a > > FreeBSD trafd-website-freebsd 9.0-RELEASE-p3 FreeBSD 9.0-RELEASE-p3 #0: > > Tue Jun 12 02:52:29 UTC 2012 > > root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC > > amd64 > > > > Server has one external interface (re0) with IP 206.239.112.241 and > > postfix service installed on 25 port. > > > > Yesterday I've noticed huge amount of emails sending out: > > > > Nov 24 00:00:37 trafd-website-freebsd postfix/smtpd[37230]: connect from > > f116.sd.com [206.239.112.241] > > Nov 24 00:00:37 trafd-website-freebsd postfix/qmgr[40324]: 73F7D1365D: > > from=>, size=1211, > nrcpt=10 (queue active) > > Nov 24 00:00:37 trafd-website-freebsd postfix/error[37366]: 75ECA134F2: > > to=>, > relay=none, delay=25715, > > delays=25715/0.02/0/0.12, dsn=4.7.0, status=deferred (delivery > > temporarily suspended: host mta7.am0.yahoodns.net > [66.94.236.34] refused > > to talk to me: 421 4.7.0 [TS01] Messages from 206.239.112.241 > > temporarily deferred due to user complaints - 4.16.55.1; see > > http://postmaster.yahoo.com/421-ts01.html) > > Nov 24 00:00:37 trafd-website-freebsd postfix/error[37368]: 794A911711: > > to=>, relay=none, > delay=29716, > > delays=29716/0.05/0/0.05, dsn=4.7.0, status=deferred (delivery > > temporarily suspended: host mta7.am0.yahoodns.net > [66.94.236.34] refused > > to talk to me: 421 4.7.0 [TS01] Messages from 206.239.112.241 > > temporarily deferred due to user complaints - 4.16.55.1; see > > http://postmaster.yahoo.com/421-ts01.html) > > Nov 24 00:00:37 trafd-website-freebsd postfix/smtp[36699]: E559512F49: > > to= >, > > relay=vip-us-br-mx.terra.com > [208.84.244.133]:25, delay=26077, > > delays=26075/1/0.59/0.31, dsn=4.7.1, status=deferred (host > > vip-us-br-mx.terra.com > [208.84.244.133] said: 450 4.7.1 You've > exceeded > > your sending limit to this domain. (in reply to end of DATA command)) > > Nov 24 00:00:37 trafd-website-freebsd postfix/error[37370]: 7C45D18E5D: > > to=>, relay=none, > delay=6984, > > delays=6984/0.02/0/0.04, dsn=4.7.0, status=deferred (delivery > > temporarily suspended: host mta7.am0.yahoodns.net > [66.94.236.34] refused > > to talk to me: 421 4.7.0 [TS01] Messages from 206.239.112.241 > > temporarily deferred due to user complaints - 4.16.55.1; see > > http://postmaster.yahoo.com/421-ts01.html) > > Nov 24 00:00:37 trafd-website-freebsd postfix/qmgr[40324]: 73E8118E53: > > from=>, size=1143, > nrcpt=10 (queue active) > > Nov 24 00:00:37 trafd-website-freebsd postfix/smtpd[37153]: 93E1020413: > > client=f116.sd.com [206.239.112.241] > > Nov 24 00:00:37 trafd-website-freebsd postfix/error[37367]: 74A511A5BF: > > to=>, > relay=none, delay=5587, > > delays=5587/0/0/0.18, dsn=4.7.0, status=deferred (delivery temporarily > > suspended: host mta7.am0.yahoodns.net > [66.94.236.34] refused to talk to > > me: 421 4.7.0 [TS01] Messages from 206.239.112.241 temporarily deferred > > due to user complaints - 4.16.55.1; see > > http://postmaster.yahoo.com/421-ts01.html) > > Nov 24 00:00:37 trafd-website-freebsd postfix/smtp[36698]: E7898134D0: > > to=>, > relay=vip-us-br-mx.terra.com > [208.84.244.133]:25, > > conn_use=4, delay=25728, delays=25726/1.1/0.06/0.4, dsn=4.7.1, > > status=deferred (host vip-us-br-mx.terra.com > [208.84.244.133] said: 450 > > 4.7.1 You've exceeded your sending limit to this domain. (in reply to > > end of DATA command)) > > Nov 24 00:00:37 trafd-website-freebsd postfix/smtp[36226]: 7BE421F989: > > to=>, > relay=mx3.bol.com.br [200.147.36.13]:25, > > delay=339, delays=339/0/0.49/0.24, dsn=4.7.1, status=deferred (host > > mx3.bol.com.br [200.147.36.13] said: 450 > 4.7.1 >: > > Recipient address rejected: MX-BOL-04 - Too many messages, try again > > later. (in reply to RCPT TO command)) > > > > Where f116.sd.com [206.239.112.241] is an IP and > host assigned for > > external interface (re0). > > > > Due to "permit_mynetworks" policy enabled in postfix conf mail was > > sending out without authentication. However all externally connected > > clients were rejected which is proper and expected behavior: > > > > Nov 24 19:31:04 trafd-website-freebsd postfix/smtpd[65618]: connect from > > a2-starfury4.uol.com.br [200.147.33.227] > > Nov 24 19:31:05 trafd-website-freebsd postfix/smtpd[65618]: NOQUEUE: > > reject: RCPT from a2-starfury4.uol.com.br > [200.147.33.227]: 550 5.1.1 > > >: Recipient address > rejected: User unknown in virtual > > mailbox table; from=<> to= > proto=ESMTP > > helo=> > > Nov 24 19:31:05 trafd-website-freebsd postfix/smtpd[65618]: disconnect > > from a2-starfury4.uol.com.br > [200.147.33.227] > > > > Then, I've tried: > > > > $cmd 001 deny all from any to me dst-port 25 in via re0 > > $cmd 002 deny all from any to me dst-port 25 out via re0 > > > > and cleaned local mail queue with > > postsuper -d ALL > > > > This didn't changed anything - server continued to send huge amount of > > emails. > > > > However restrictions on lo0: > > $cmd 001 deny all from any to me dst-port 25 in via lo0 > > $cmd 002 deny all from any to me dst-port 25 out via lo0 > > > > did the trick - emailing had stopped. So by fact - problem solved, but > > the real reason wasn't not found. > > > > I've launched clamav and f-prot scans - nothing suspicious found. > > > > The main question I have - how it's possible on stand-alone dedicated > > server - who and how is connecting on behalf of it's own ext ip and uses > > local interface to send emails? Is this possible to do from outside, or > > server was infected from inside? > It appears the delivery failures are failed attempts to deliver bounce > messages which likely are generated in response to receiving emails > with a Delivered-To: header with the address the same as the delivery > address. > The email has a forged sender address where postfix tries to send the > bounce message. > This activity seems to be increasing and we can guess at what the > motivation might be.. > Though its not a FreeBSD problem, there is very little discussion on > the 'net about this and it probably causes a lot of grief for those on > the receiving end of the bounce messages. > Would be good if users of postfix on FreeBSD were aware of this and > took some action. > Google searching will find a few possibilities for that action, none I > found were without some potential negative effects. > Hope this helps.. > -kim From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 25 19:06:03 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 558F3CCE; Sun, 25 Nov 2012 19:06:03 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from monday.kientzle.com (99-115-135-74.uvs.sntcca.sbcglobal.net [99.115.135.74]) by mx1.freebsd.org (Postfix) with ESMTP id 25CA98FC08; Sun, 25 Nov 2012 19:06:02 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id qAPJ61St033561; Sun, 25 Nov 2012 19:06:01 GMT (envelope-from kientzle@freebsd.org) Received: from [192.168.2.143] (CiscoE3000 [192.168.1.65]) by kientzle.com with SMTP id 5iiten4di27buz9n9d4zuxhy5w; Sun, 25 Nov 2012 19:06:01 +0000 (UTC) (envelope-from kientzle@freebsd.org) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1283) Subject: Re: FreeBSD on RaspberryPi From: Tim Kientzle In-Reply-To: Date: Sun, 25 Nov 2012 11:05:59 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: References: <31C904E6-F230-4187-AE32-F9A7B1A7C38E@freebsd.org> <509CC1F6.1010308@freebsd.org> <1B7CD3EC-6F99-43A3-BAAA-EC6EA25D90A9@bluezbox.com> To: Adrian Chadd , freebsd-hackers X-Mailer: Apple Mail (2.1283) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Nov 2012 19:06:03 -0000 On Nov 11, 2012, at 12:46 PM, Adrian Chadd wrote: > On 11 November 2012 12:39, Oleksandr Tymoshenko = wrote: >=20 >> At the moment HDMI output works only in a sense of video output for = simple >> frame buffer. I'm trying to get GPU support ported but not sure how = much time >> it will take. Eventually we'd like to get audio support too. >=20 > How's the general, non-video support working out? Are there any random > crashes or panics that people are seeing on R-PI right now? So far, I haven't done very much, but it is stable enough to natively build a bootable kernel; note the build machine on my RPi boot message: FreeBSD 10.0-CURRENT #2: Sun Nov 25 14:23:57 UTC 2012 root@raspberry-pi:/usr/src/sys/arm/compile/RPI-B arm The two biggest obstacles right now are: * Memory. There's a missing piece in the current boot sequence that causes it to always default to 128MB memory. That makes it hard to do much on a generic -CURRENT build. (The native kernel above took a long time; swapping to SDHC is a little slow. ;-) Related: Shipping RPis now have 512MB RAM; I'm pretty excited about = that. * Video console. You've probably noticed the exchanges on the list. Apart from that, it's pretty promising. I'm optimistic that we're no more than a couple of weeks from having a FreeBSD image that a lot of folks can just download and use. Tim From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 25 19:11:26 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3A6CD190; Sun, 25 Nov 2012 19:11:26 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 3B72E8FC12; Sun, 25 Nov 2012 19:11:25 +0000 (UTC) Received: by mail-we0-f182.google.com with SMTP id u54so4206905wey.13 for ; Sun, 25 Nov 2012 11:11:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=jaWOUp1Jdih+C+0Q7IDmBiXQWbMd6Z387A5eZQsdeMg=; b=NAWZ9a90zYjLN6OQXwyfx408WlA5ybzHdtTCnzmONMxC/Uvdyn7KQbsnsAyZFix9fl DnEjQCF2o9IBMciq4L8OgLRzfncuPf7OorJ90HfGRdPYh3f381UxzXi6noXI0Yh0zwTw TNMxGlqj5FPb5olH/XoJ+zJzzV4DZLArEynyi5xxgqafSb6DKL9vzOE2kJRtVQfNsiUm Rs5bzxnA1kz22GYzQ8Jjjn1dnBwUaaP8Ja2N7djt+JcwJIQpW6QrIczHj64h2+KmnoGO KzkI4EjdqjXzblEiQj4Qw9u+oeUnYDTIonQ7diH5xGy1VlUYIAbQi6YZiKwE2N6Xm7ls hasQ== MIME-Version: 1.0 Received: by 10.180.103.106 with SMTP id fv10mr14050185wib.19.1353870684166; Sun, 25 Nov 2012 11:11:24 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.217.57.9 with HTTP; Sun, 25 Nov 2012 11:11:24 -0800 (PST) In-Reply-To: References: <20121125123920.GI1460@garage.freebsd.pl> <20121125131252.GJ1460@garage.freebsd.pl> Date: Sun, 25 Nov 2012 11:11:24 -0800 X-Google-Sender-Auth: QleFQo76D6QpOTABeAxrWCaf1Fs Message-ID: Subject: Re: [RFQ] make witness panic an option From: Adrian Chadd To: attilio@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-hackers@freebsd.org" , Giovanni Trematerra , freebsd-arch@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Nov 2012 19:11:26 -0000 The reason I haven't yet committed it is I'd like to sit down with Attilio one-on-one and figure out the _right_ way to do this. There's a time for shit-stirring and a time for getting stuff done; this is neither of those times. I don't mind taking my time on this one. Adrian From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 25 19:29:13 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8BC81BBA; Sun, 25 Nov 2012 19:29:13 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from mail-la0-f54.google.com (mail-la0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id C37C88FC13; Sun, 25 Nov 2012 19:29:12 +0000 (UTC) Received: by mail-la0-f54.google.com with SMTP id j13so9985500lah.13 for ; Sun, 25 Nov 2012 11:29:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=iBQJyyysg7i+d7gyJUf6QxeuNonTWvOuxhr8EbVExhw=; b=Zm3F3r479lWgUuFBvwHLx1CaUPeNp0Azo5gTB3/zICvwox4Htou8DOhX0J+hkmmSz/ yJ5N7IV6yt3CZuZ3OvMNA8qx/u5gizVkm84f/TFkoTT+U+6yl8ppgSNsX1lGfdlaQrYN 1xr35606ulmA2mRBGuvKiukyV6vbPuW9TTJ5C5gqoVHiytX/6db6g30e8K9FtOMjt/+v 06S6NyL37eIfkrrIRWlexHTpKrTGDmu72Ji0SXUeZ2Bl7j+eiQGjvZ3HcznwExSL2QuU MPkmuuJ5vMzsB/GzBz4UxSPoYCmyQWjCJav4MR63Y45KEsvINE9JTVV73snJVbRt75gj tR2w== MIME-Version: 1.0 Received: by 10.152.129.197 with SMTP id ny5mr8861417lab.43.1353871751433; Sun, 25 Nov 2012 11:29:11 -0800 (PST) Sender: asmrookie@gmail.com Received: by 10.112.134.5 with HTTP; Sun, 25 Nov 2012 11:29:11 -0800 (PST) In-Reply-To: <50B26179.4040205@FreeBSD.org> References: <50A5F12C.1050902@FreeBSD.org> <50A63D1D.9090500@FreeBSD.org> <50A65208.4050804@FreeBSD.org> <50B21545.5060807@FreeBSD.org> <50B22DA0.9080207@FreeBSD.org> <50B26179.4040205@FreeBSD.org> Date: Sun, 25 Nov 2012 20:29:11 +0100 X-Google-Sender-Auth: MOzvdOA-yMhiOXKj_-Blc24vQIs Message-ID: Subject: Re: stop_cpus_hard when multiple CPUs are panicking from an NMI From: Attilio Rao To: Andriy Gapon Content-Type: text/plain; charset=UTF-8 Cc: freebsd-hackers@freebsd.org, Ryan Stone X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: attilio@FreeBSD.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Nov 2012 19:29:13 -0000 On Sun, Nov 25, 2012 at 7:20 PM, Andriy Gapon wrote: > on 25/11/2012 20:05 Attilio Rao said the following: >> If you really want to do something like that please rename >> s/generic_stop_cpus/generic_stop_butself() or similar convention and I >> may be not opposed to it. > > As we discussed before, anything else besides "all but self" does not make > sense. So I am not sure what's the point of being that verbose in the naming. Avoid POLA violation and show there is a change in the KPI? I'd personally prefer a new name, but I'm open on not getting it. Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 25 21:13:27 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 58F746E1; Sun, 25 Nov 2012 21:13:27 +0000 (UTC) (envelope-from des@des.no) Received: from smtp.des.no (smtp.des.no [194.63.250.102]) by mx1.freebsd.org (Postfix) with ESMTP id 0BCE58FC14; Sun, 25 Nov 2012 21:13:26 +0000 (UTC) Received: from ds4.des.no (smtp.des.no [194.63.250.102]) by smtp.des.no (Postfix) with ESMTP id 0F3FC69B3; Sun, 25 Nov 2012 22:13:26 +0100 (CET) Received: by ds4.des.no (Postfix, from userid 1001) id CC1BB9547; Sun, 25 Nov 2012 22:13:25 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: grarpamp Subject: Re: FreeBSD needs Git to ensure repo integrity References: Date: Sun, 25 Nov 2012 22:13:25 +0100 In-Reply-To: (grarpamp@gmail.com's message of "Sat, 17 Nov 2012 15:00:06 -0500") Message-ID: <864nkdtmh6.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org, freebsd-hubs@freebsd.org, freebsd-questions@freebsd.org, freebsd-security@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Nov 2012 21:13:27 -0000 grarpamp writes: > Any of hundreds of committer and admin accounts could be compromised > with the attacker silently editing the repo. FUD. Committer accounts don't have direct access to the repo. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 25 21:53:53 2012 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C14C9432; Sun, 25 Nov 2012 21:53:53 +0000 (UTC) (envelope-from jilles@stack.nl) Received: from mx1.stack.nl (unknown [IPv6:2001:610:1108:5012::107]) by mx1.freebsd.org (Postfix) with ESMTP id 5C2F78FC12; Sun, 25 Nov 2012 21:53:53 +0000 (UTC) Received: from snail.stack.nl (snail.stack.nl [IPv6:2001:610:1108:5010::131]) by mx1.stack.nl (Postfix) with ESMTP id 595111200BA; Sun, 25 Nov 2012 22:53:48 +0100 (CET) Received: by snail.stack.nl (Postfix, from userid 1677) id 426302848C; Sun, 25 Nov 2012 22:53:48 +0100 (CET) Date: Sun, 25 Nov 2012 22:53:48 +0100 From: Jilles Tjoelker To: freebsd-hackers@FreeBSD.org Subject: Incorrect use of posix_memalign() (was: Re: svn commit: r243405 - in stable/9: include lib/libc/stdlib) Message-ID: <20121125215348.GB65833@stack.nl> References: <201211221519.qAMFJroe007462@svn.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201211221519.qAMFJroe007462@svn.freebsd.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Ed Schouten X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Nov 2012 21:53:53 -0000 On Thu, Nov 22, 2012 at 03:19:53PM +0000, Ed Schouten wrote: > Author: ed > Date: Thu Nov 22 15:19:53 2012 > New Revision: 243405 > URL: http://svnweb.freebsd.org/changeset/base/243405 > Log: > MFC r229848: > Add aligned_alloc(3). > The C11 folks reinvented the wheel by introducing an aligned version of > malloc(3) called aligned_alloc(3), instead of posix_memalign(3). Instead > of returning the allocation by reference, it returns the address, just > like malloc(3). > I'm MFCing this now, as it seems aligned_alloc(3) is needed to make the > new version of libc++ work, which was merged back to FreeBSD 9 in r243376. The C11 committee knew about posix_memalign() and had several reasons for creating a new function; see for example http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1397.htm . In particular, posix_memalign() is a little annoying to use correctly, often requiring a temporary variable of type void *. It is tempting to do something like error = posix_memalign((void **)&some_ptr, aln, sz); and some FreeBSD code does this, but it violates strict-aliasing. A further mostly theoretical objection is that assumes that the representation of some_ptr and void * are compatible which C does not guarantee. The problem can be fixed by adding the temporary pointer variable like void *tmp_ptr; error = posix_memalign(&tmp_ptr, aln, sz); some_ptr = tmp_ptr; or by using aligned_alloc() instead of posix_memalign() some_ptr = aligned_alloc(aln, sz); with error checking against some_ptr instead of error. -- Jilles Tjoelker From owner-freebsd-hackers@FreeBSD.ORG Mon Nov 26 00:06:38 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4AA64B16 for ; Mon, 26 Nov 2012 00:06:38 +0000 (UTC) (envelope-from nvass@gmx.com) Received: from mailout-eu.gmx.com (mailout-eu.gmx.com [213.165.64.44]) by mx1.freebsd.org (Postfix) with SMTP id BAA0D8FC08 for ; Mon, 26 Nov 2012 00:06:37 +0000 (UTC) Received: (qmail invoked by alias); 26 Nov 2012 00:06:36 -0000 Received: from 178.128.120.133.dsl.dyn.forthnet.gr (EHLO [192.168.1.77]) [178.128.120.133] by mail.gmx.com (mp-eu001) with SMTP; 26 Nov 2012 01:06:36 +0100 X-Authenticated: #46156728 X-Provags-ID: V01U2FsdGVkX1/XnkQs2zTXHnWR2rtxhguuReQFfQDKI9iOs6Stwq 23M3Y4R6sE6mSb Message-ID: <50B2B285.2020008@gmx.com> Date: Mon, 26 Nov 2012 02:06:29 +0200 From: Nikos Vassiliadis User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120604 Thunderbird/13.0 MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: "not" user display in top Content-Type: multipart/mixed; boundary="------------020603090909080604080608" X-Y-GMX-Trusted: 0 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Nov 2012 00:06:38 -0000 This is a multi-part message in MIME format. --------------020603090909080604080608 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi, The attached patch adds 'not' functionality to the interactive u command in top so one can select all processes not owned by a user. This happens when the username is prefixed with a minus. Example display for -root: > CPU: 0.0% user, 0.0% nice, 0.1% system, 0.0% interrupt, 99.9% idle > Mem: 16M Active, 108M Inact, 150M Wired, 3760K Cache, 112M Buf, 1210M Free > Swap: 288M Total, 288M Free > > PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND > 794 smmsp 1 20 0 12812K 4284K pause 1 0:00 0.00% sendmail > 566 _dhcp 1 39 0 10136K 1848K select 0 0:00 0.00% dhclient > Thanks, Nikos --------------020603090909080604080608 Content-Type: text/plain; charset=windows-1252; name="top.diff.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="top.diff.txt" Index: contrib/top/machine.h =================================================================== --- contrib/top/machine.h (revision 243514) +++ contrib/top/machine.h (working copy) @@ -65,6 +65,7 @@ int system; /* show system processes */ int thread; /* show threads */ int uid; /* only this uid (unless uid == -1) */ + int buid; /* all but this uid (unless buid == -1) */ int wcpu; /* show weighted cpu */ int jail; /* show jail ID */ int kidle; /* show per-CPU idle threads */ Index: contrib/top/top.X =================================================================== --- contrib/top/top.X (revision 243514) +++ contrib/top/top.X (working copy) @@ -286,8 +286,10 @@ .TP .B u Display only processes owned by a specific username (prompt for username). -If the username specified is simply \*(lq+\*(rq, then processes belonging -to all users will be displayed. +If the username specified is simply \*(lq+\*(rq or \*(lq-\*(rq, then processes +belonging to all users will be displayed. +If the username is prefixed by a \*(lq-\*(rq, then only processes not owned +by the username will be displayed. .TP .B o Change the order in which the display is sorted. This command is not Index: contrib/top/top.c =================================================================== --- contrib/top/top.c (revision 243514) +++ contrib/top/top.c (working copy) @@ -259,6 +259,7 @@ ps.self = -1; ps.system = No; ps.uid = -1; + ps.buid = -1; ps.thread = No; ps.wcpu = 1; ps.jail = No; @@ -997,20 +998,32 @@ "Username to show: "); if (readline(tempbuf2, sizeof(tempbuf2), No) > 0) { - if (tempbuf2[0] == '+' && + if ((tempbuf2[0] == '+' || tempbuf2[0] == '-') && tempbuf2[1] == '\0') { ps.uid = -1; + ps.buid = -1; } + else if (tempbuf2[0] == '-') + { + if ((i = userid(tempbuf2 + 1)) == -1) + { + new_message(MT_standout, + " %s: unknown user", tempbuf2 + 1); + no_command = Yes; + } else { + ps.uid = -1; + ps.buid = i; + } + } else if ((i = userid(tempbuf2)) == -1) { new_message(MT_standout, " %s: unknown user", tempbuf2); no_command = Yes; - } - else - { + } else { ps.uid = i; + ps.buid = -1; } putchar('\r'); } Index: usr.bin/top/machine.c =================================================================== --- usr.bin/top/machine.c (revision 243514) +++ usr.bin/top/machine.c (working copy) @@ -671,6 +671,7 @@ int show_self; int show_system; int show_uid; + int show_buid; int show_command; int show_kidle; @@ -713,6 +714,7 @@ show_self = sel->self == -1; show_system = sel->system; show_uid = sel->uid != -1; + show_buid = sel->buid != -1; show_command = sel->command != NULL; show_kidle = sel->kidle; @@ -768,6 +770,10 @@ /* skip proc. that don't belong to the selected UID */ continue; + if (show_buid && pp->ki_ruid == (uid_t)sel->buid) + /* skip proc. that belong to the selected UID */ + continue; + *prefp++ = pp; active_procs++; } --------------020603090909080604080608-- From owner-freebsd-hackers@FreeBSD.ORG Mon Nov 26 06:21:38 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D0D2B89B for ; Mon, 26 Nov 2012 06:21:38 +0000 (UTC) (envelope-from sushanth_rai@yahoo.com) Received: from nm5-vm1.bullet.mail.ne1.yahoo.com (nm5-vm1.bullet.mail.ne1.yahoo.com [98.138.91.32]) by mx1.freebsd.org (Postfix) with ESMTP id 6403C8FC0C for ; Mon, 26 Nov 2012 06:21:38 +0000 (UTC) Received: from [98.138.90.55] by nm5.bullet.mail.ne1.yahoo.com with NNFMP; 26 Nov 2012 06:21:32 -0000 Received: from [66.94.237.125] by tm8.bullet.mail.ne1.yahoo.com with NNFMP; 26 Nov 2012 06:21:32 -0000 Received: from [127.0.0.1] by omp1030.access.mail.mud.yahoo.com with NNFMP; 26 Nov 2012 06:21:32 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 661780.75570.bm@omp1030.access.mail.mud.yahoo.com Received: (qmail 70867 invoked by uid 60001); 26 Nov 2012 06:21:32 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1353910892; bh=fbQCrMsNgQK4lm50yz7mFHlEpmO/1ICxFgfAUgX1+o0=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Subject:To:MIME-Version:Content-Type; b=gb863Uqx7FyE5ztOU0W9gKE+DlpiLm0j/Q+ZK8lrDoRIZp8lmw8zNYO3OSYbuXs0TA0Cs1mlLxClT0+4Hn2TYuWLPp7e/mZJRSX7dzMz+TkSr1CkAIptXZQMRxcPPDd4HV+xpF76vGQeiy18YQfguSAfMFUJ5+Es5hiiUwdKip0= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Subject:To:MIME-Version:Content-Type; b=rjs+NL+Ep8YUWq+9RLX4jbOGtvQYTiRrCX8njFAtSC1EZBiAPnbmJwg6gX/MLFofphzBb0bAzRIbvWwf6qJ8Efq6eXYq7Ybi96Bh1Hobin2ori7oNv2HITuftRjxXD7Dg9sNa7H8Cnf+5AeJrqCgu3R0HNdYTARB4MG9JrHneAM=; X-YMail-OSG: JSm_oW0VM1mD12ycrwYwK3EDfNV_YG8DclXJsqHiALHChTt ckzd5jGhepuz3QCe5QnMTP.6r7S0n83x3z8Du5bqn4NwAf7NPtFV2qGf9mT5 kKQnnjuzazbWaOvrZGtw2UnK5mmTfzmFFDr2U2VR7hpJlstxwU14jZO5zA4D DFoI_nQbOugvum9u7C6JVA0KghZ5Ql9J1RBPgrS3Dmscrq8vSDcVIpWTwWv9 gU_ICBPRCHnruQGpb6m3u5YrLbYpwDXTdowSXd5dvXrB0GIQNDiAEJvtuuVI pu3ZJoZ7iwu1966Iic5mBkTatT438F6.WaRngUGVzTWYd3PSVucEVfCOjJKY bPcpKZANwWnSlrQTkvwoCrp8TJs7MSoEcGzSDQpV.AtGXsFDCvl91lnM9hBK owVP8iyL7L5MNFgz6CS7FXMCfi_zzigdg.E8WfqXAZn0kjGpktGfRc.KIkT. daobyj.bgR2m2Jw7rCznKTDo9EhaAlbzzua9LBEfb.sSYRjaTPkUJ Received: from [76.211.239.121] by web181702.mail.ne1.yahoo.com via HTTP; Sun, 25 Nov 2012 22:21:32 PST X-Rocket-MIMEInfo: 001.001, QmFzaWNhbGx5IEkgd291bGQgbGlrZSB0byBnZXQga2VybmVsIGJhY2t0cmFjZSBvZiBhIGJ1bmNoIG9mIHRocmVhZHMgZnJvbSB0aGUgbGl2ZSBrZXJuZWwgdW5kZXIgc29tZSBjb25kaXRpb25zLiBXaGVuIHRoZSBjb25kaXRpb24gaXMgc2VlbiBJIHdvdWxkIGxpa2UgdG8gcnVuIGtnZGIsIGNvbGxlY3Qga2VybmVsIGJhY2t0cmFjZSBvZiBzcGVjaWZpYyB0aHJlYWRzIGFuZCBleGl0LiBJcyB0aGVyZSBhIHdheSBydW4ga2dkYiBpbiBiYXRjaCBtb2RlID8gT3IgYW55IG90aGVyIHdheSB0byBnZXQgdGhlIHMBMAEBAQE- X-Mailer: YahooMailClassic/15.0.8 YahooMailWebService/0.8.123.460 Message-ID: <1353910892.62730.YahooMailClassic@web181702.mail.ne1.yahoo.com> Date: Sun, 25 Nov 2012 22:21:32 -0800 (PST) From: Sushanth Rai Subject: Running kgdb in batch mode. To: freebsd-hackers@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Nov 2012 06:21:39 -0000 Basically I would like to get kernel backtrace of a bunch of threads from the live kernel under some conditions. When the condition is seen I would like to run kgdb, collect kernel backtrace of specific threads and exit. Is there a way run kgdb in batch mode ? Or any other way to get the stack trace. Thanks, Sushanth From owner-freebsd-hackers@FreeBSD.ORG Mon Nov 26 07:46:58 2012 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7ECAF5FA; Mon, 26 Nov 2012 07:46:58 +0000 (UTC) (envelope-from gonzo@id.bluezbox.com) Received: from id.bluezbox.com (id.bluezbox.com [88.198.91.248]) by mx1.freebsd.org (Postfix) with ESMTP id 212648FC13; Mon, 26 Nov 2012 07:46:57 +0000 (UTC) Received: from [207.6.254.8] (helo=[192.168.1.67]) by id.bluezbox.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from ) id 1TctOw-000N1z-1I; Sun, 25 Nov 2012 23:46:51 -0800 Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: FreeBSD on RaspberryPi From: Oleksandr Tymoshenko In-Reply-To: Date: Sun, 25 Nov 2012 23:46:27 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: References: <31C904E6-F230-4187-AE32-F9A7B1A7C38E@freebsd.org> <4A5E03E5-3295-4FD4-9A06-7D1C4E9E0C12@freebsd.org> <9E4DA920-BE72-4AA0-8159-43205CDEF5CD@bluezbox.com> To: Tim Kientzle X-Mailer: Apple Mail (2.1499) Sender: gonzo@id.bluezbox.com X-Spam-Level: -- X-Spam-Report: Spam detection software, running on the system "id.bluezbox.com", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: On 2012-11-25, at 9:32 AM, Tim Kientzle wrote: > > On Nov 24, 2012, at 8:01 PM, Oleksandr Tymoshenko wrote: > >> >> On 2012-11-24, at 4:47 PM, Tim Kientzle wrote: >> >> [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] Cc: FreeBSD Hackers , Alexander Yerenkow X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Nov 2012 07:46:58 -0000 On 2012-11-25, at 9:32 AM, Tim Kientzle wrote: >=20 > On Nov 24, 2012, at 8:01 PM, Oleksandr Tymoshenko wrote: >=20 >>=20 >> On 2012-11-24, at 4:47 PM, Tim Kientzle wrote: >>=20 >>=20 .. skipped .. >> Tim, >>=20 >> I'm almost done with getting kernel working with latest raspberry Pi = firmware. Just need >> to figure out how to make ubldr pass FDT pointer from u-boot to = kernel and handle=20 >> /reserve/ information in ARM machdep code.=20 >=20 > Let me know if you need help with this. I've worked with > the ubldr FDT code recently. >=20 >> Meanwhile I suggest editing .dts file manually. Fill out "display" = node properties with proper >> display resolution and depth. Also add ukbd driver. That should get = you working console. >=20 > I'll try that. >=20 > I'm curious: why is this information coming from the DTS? > That seems pretty complex; I thought that the > console code would query this information via the mailbox > interface. It's either FDT blob or message box interface. Implementation complexity = is about the same. But since we're getting other variables (like MAC address, memory size) = from FDT I decided to be consistent and get all of them from there. The issue I'm facing is = that ubldr gets FDT blob either from file directly or from ELF kernel itself. While on Raspberry = Pi to works as follows: - Firmware loads .dtb file from SD card to specified address - Fixes up values like amount of memory, reserved regions, UART and = clock frequencies,=20 MAC address, display resolution. - Passes control to next link in boot chain (e.g. U-Boot) I'm thinking about adding compile-time constant FDT_BLOB_ADDRESS and = arrange possible FDT sources in following priority: - Check FDT_BLOB_ADDRESS (if defined) - Check dtb file - Check ELF kernel Does it sound sane enough?=20= From owner-freebsd-hackers@FreeBSD.ORG Mon Nov 26 14:55:41 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 13B4E1F5 for ; Mon, 26 Nov 2012 14:55:41 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-ie0-f182.google.com (mail-ie0-f182.google.com [209.85.223.182]) by mx1.freebsd.org (Postfix) with ESMTP id C8F708FC12 for ; Mon, 26 Nov 2012 14:55:40 +0000 (UTC) Received: by mail-ie0-f182.google.com with SMTP id s9so12609417iec.13 for ; Mon, 26 Nov 2012 06:55:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=m4i7/jAH8dvrKfCNA1lB/fI5S3Y6rkJEJLUefDqy978=; b=XZY5LpCLsBmpcuLgUmsUqH4/YUqCcwzVb7TN7YrLwXQU9TIdhw034Q3A4/dHxjKmg4 umSPBFFJCYMx/sGRUX217vWxunLnP/6ACsQ/s+EF+mskp6zucYpwv2q+tu6fUPKWl0uB OafRHuKjM53Af0fRfENKyuQqQYWSVJQ4fEX1elTRHw1tIlLVT+HwVFHCoTe5fKBzjpJk vzqXjAivygyK+/p/G1vCOtDWasr5F9G1ZUBAiULmT8uiVY7VzJmgiUR5440kmxLZ5lc2 w55H/9lPuM8++IXK6cu73l6xO+S9AxrFPyloqMWaS79elnN/biRSbLE2tHwb75sjz9RM 3noQ== MIME-Version: 1.0 Received: by 10.50.95.161 with SMTP id dl1mr14919875igb.0.1353941740235; Mon, 26 Nov 2012 06:55:40 -0800 (PST) Sender: carpeddiem@gmail.com Received: by 10.50.151.135 with HTTP; Mon, 26 Nov 2012 06:55:40 -0800 (PST) In-Reply-To: <1353910892.62730.YahooMailClassic@web181702.mail.ne1.yahoo.com> References: <1353910892.62730.YahooMailClassic@web181702.mail.ne1.yahoo.com> Date: Mon, 26 Nov 2012 09:55:40 -0500 X-Google-Sender-Auth: T66q_OdtSFOg3-NF8zGm4yh3ty4 Message-ID: Subject: Re: Running kgdb in batch mode. From: Ed Maste To: Sushanth Rai Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Nov 2012 14:55:41 -0000 On 26 November 2012 01:21, Sushanth Rai wrote: > Basically I would like to get kernel backtrace of a bunch of threads from= the live kernel under some conditions. When the condition is seen I would = like to run kgdb, collect kernel backtrace of specific threads and exit. Is= there a way run kgdb in batch mode ? Or any other way to get the stack tra= ce. Have a look at /usr/sbin/crashinfo for an example of how to do so - basically just run kgdb $KERNEL $VMCORE < commands_file. -Ed From owner-freebsd-hackers@FreeBSD.ORG Mon Nov 26 15:06:23 2012 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2726A786 for ; Mon, 26 Nov 2012 15:06:23 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from monday.kientzle.com (99-115-135-74.uvs.sntcca.sbcglobal.net [99.115.135.74]) by mx1.freebsd.org (Postfix) with ESMTP id EA1A38FC14 for ; Mon, 26 Nov 2012 15:06:22 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id qAQF5drf038915; Mon, 26 Nov 2012 15:05:39 GMT (envelope-from kientzle@freebsd.org) Received: from [192.168.2.143] (CiscoE3000 [192.168.1.65]) by kientzle.com with SMTP id m25h4wdmkh8yx6h4ywna4qp6de; Mon, 26 Nov 2012 15:05:39 +0000 (UTC) (envelope-from kientzle@freebsd.org) Subject: Re: FreeBSD on RaspberryPi Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=us-ascii From: Tim Kientzle In-Reply-To: Date: Mon, 26 Nov 2012 07:05:37 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <1E75CEAC-32E8-4048-A1FB-DD59F996E22F@freebsd.org> References: <31C904E6-F230-4187-AE32-F9A7B1A7C38E@freebsd.org> <4A5E03E5-3295-4FD4-9A06-7D1C4E9E0C12@freebsd.org> <9E4DA920-BE72-4AA0-8159-43205CDEF5CD@bluezbox.com> To: Oleksandr Tymoshenko X-Mailer: Apple Mail (2.1283) Cc: FreeBSD Hackers , Alexander Yerenkow X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Nov 2012 15:06:23 -0000 On Nov 25, 2012, at 11:46 PM, Oleksandr Tymoshenko wrote: >=20 > On 2012-11-25, at 9:32 AM, Tim Kientzle wrote: >=20 >>=20 >> On Nov 24, 2012, at 8:01 PM, Oleksandr Tymoshenko wrote: >>=20 >>>=20 >>> On 2012-11-24, at 4:47 PM, Tim Kientzle = wrote: >>>=20 >>>=20 >=20 > .. skipped .. >=20 >>> Tim, >>>=20 >>> I'm almost done with getting kernel working with latest raspberry Pi = firmware. Just need >>> to figure out how to make ubldr pass FDT pointer from u-boot to = kernel and handle=20 >>> /reserve/ information in ARM machdep code.=20 >>=20 >> Let me know if you need help with this. I've worked with >> the ubldr FDT code recently. >>=20 >>> Meanwhile I suggest editing .dts file manually. Fill out "display" = node properties with proper >>> display resolution and depth. Also add ukbd driver. That should get = you working console. >>=20 >> I'll try that. >>=20 >> I'm curious: why is this information coming from the DTS? >> That seems pretty complex; I thought that the >> console code would query this information via the mailbox >> interface. >=20 >=20 > It's either FDT blob or message box interface. Implementation = complexity is about the same. My thinking: * Display resolution used by kernel has to match what the firmware = uses. So the kernel should either get the information from the firmware = or from the same place the firmware gets it from. * We want ubldr to remain generic, so I'm reluctant to put things into = it that are RaspberryPi-specific. If the firmware is putting the values into the FDT, then having the = kernel get it from the FDT is another way for the kernel to get it from = the firmware, so that sounds okay. > But since we're getting other variables (like MAC address, memory = size) from FDT I decided > to be consistent and get all of them from there. I don't know about MAC address. Memory size is handled generically by = ubldr using a standard interface to U-Boot, so it's not special to = RaspberryPi. The FDT editing is just a standard way for ubldr to pass = this to the kernel. > The issue I'm facing is that ubldr gets FDT blob > either from file directly or from ELF kernel itself. While on = Raspberry Pi to works as follows: >=20 > - Firmware loads .dtb file from SD card to specified address Does RaspberryPi firmware now load an FDT? Does the firmware now read the FDT to get its values for display = resolution, etc? (I don't really like this because a lot of people need to tweak the = display settings and it's hard to tell a 6-year-old how to edit and = recompile an FDT.) > - Fixes up values like amount of memory, reserved regions, UART and = clock frequencies,=20 > MAC address, display resolution. > - Passes control to next link in boot chain (e.g. U-Boot) To be clear: You say the RPi firmware is already doing this editing? So the ubldr just has to pass the RPi FDT to the kernel? If so, that's = a lot simpler. > I'm thinking about adding compile-time constant FDT_BLOB_ADDRESS and = arrange possible > FDT sources in following priority: >=20 > - Check FDT_BLOB_ADDRESS (if defined) > - Check dtb file > - Check ELF kernel >=20 > Does it sound sane enough?=20 If the RPi firmware always loads the FDT at a fixed address and the RPi firmware is using the FDT to configure itself, then it makes a lot of sense. It would be nice to do this without adding RPi-specific code to ubldr. > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to = "freebsd-hackers-unsubscribe@freebsd.org" >=20 From owner-freebsd-hackers@FreeBSD.ORG Mon Nov 26 15:17:51 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A1F5BC73 for ; Mon, 26 Nov 2012 15:17:51 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-5.mit.edu (DMZ-MAILSEC-SCANNER-5.MIT.EDU [18.7.68.34]) by mx1.freebsd.org (Postfix) with ESMTP id 39D6D8FC0C for ; Mon, 26 Nov 2012 15:17:50 +0000 (UTC) X-AuditID: 12074422-b7f196d00000398d-38-50b388183225 Received: from mailhub-auth-3.mit.edu ( [18.9.21.43]) by dmz-mailsec-scanner-5.mit.edu (Symantec Messaging Gateway) with SMTP id 17.96.14733.81883B05; Mon, 26 Nov 2012 10:17:44 -0500 (EST) Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-3.mit.edu (8.13.8/8.9.2) with ESMTP id qAQFHifw032541; Mon, 26 Nov 2012 10:17:44 -0500 Received: from multics.mit.edu (SYSTEM-LOW-SIPB.MIT.EDU [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id qAQFHf0L026872 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 26 Nov 2012 10:17:43 -0500 (EST) Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id qAQFHfqP026951; Mon, 26 Nov 2012 10:17:41 -0500 (EST) Date: Mon, 26 Nov 2012 10:17:40 -0500 (EST) From: Benjamin Kaduk To: Sushanth Rai Subject: Re: Running kgdb in batch mode. In-Reply-To: Message-ID: References: <1353910892.62730.YahooMailClassic@web181702.mail.ne1.yahoo.com> User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrNIsWRmVeSWpSXmKPExsUixCmqrSvRsTnAYM99SYvtm/8xWtyeepnZ gcljxqf5LB6zZh1mCmCK4rJJSc3JLEst0rdL4MrY3LuerWASa8X75atZGxhbWboYOTkkBEwk /n+Yyg5hi0lcuLeerYuRi0NIYB+jxIXVM5kgnA2MEjdvbmSBcE4wScy/uoQRwmlglDiy/Twj SD+LgLbEhu07WEFsNgEViZlvNrKB2CICmhJPHl0D28csIC9xYfMhsHphAQ2J7+9awOo5BQIl Zr4DWcfJwSvgILGy/QgzxIKJjBKTL8wBS4gK6Eis3j+FBaJIUOLkzCdQQy0lzv25zjaBUXAW ktQsJKkFjEyrGGVTcqt0cxMzc4pTk3WLkxPz8lKLdE31cjNL9FJTSjcxgsKV3UVpB+PPg0qH GAU4GJV4eCWObQoQYk0sK67MPcQoycGkJMp7rHVzgBBfUn5KZUZicUZ8UWlOavEhRgkOZiUR 3u+NQDnelMTKqtSifJiUNAeLkjjvtZSb/kIC6YklqdmpqQWpRTBZGQ4OJQlennagRsGi1PTU irTMnBKENBMHJ8hwHqDhOm0gw4sLEnOLM9Mh8qcYdTl6/3U9YRRiycvPS5US57UDGSQAUpRR mgc3B5ZmXjGKA70lzPsXZBQPMEXBTXoFtIQJaEny9Y0gS0oSEVJSDYwuD3IkllzrdmwMFem9 wxHm810uerPs64i+CIvLO9XTHNaEfpz9nfPKykvHps8IypNRmXQu8MkMo4b8ea9jzu75Jddv bb7+xXpnht0pBkZlp0sfX5EW/lc2P65gsvfsHd73F3IFL1tSG3RONlJURa/+j0gm/78fEWJP JsUpdIhvlZx+kflA3GYlluKMREMt5qLiRAATnNSqDgMAAA== Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Nov 2012 15:17:51 -0000 On Mon, 26 Nov 2012, Ed Maste wrote: > On 26 November 2012 01:21, Sushanth Rai wrote: >> Basically I would like to get kernel backtrace of a bunch of threads >> from the live kernel under some conditions. When the condition is seen >> I would like to run kgdb, collect kernel backtrace of specific threads >> and exit. Is there a way run kgdb in batch mode ? Or any other way to >> get the stack trace. > > Have a look at /usr/sbin/crashinfo for an example of how to do so - > basically just run kgdb $KERNEL $VMCORE < commands_file. procstat -kk [pid] will give a kernel stack trace from userspace. -Ben Kaduk From owner-freebsd-hackers@FreeBSD.ORG Mon Nov 26 18:43:58 2012 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A7CCC70F; Mon, 26 Nov 2012 18:43:58 +0000 (UTC) (envelope-from gonzo@id.bluezbox.com) Received: from id.bluezbox.com (id.bluezbox.com [88.198.91.248]) by mx1.freebsd.org (Postfix) with ESMTP id 09CEA8FC14; Mon, 26 Nov 2012 18:43:57 +0000 (UTC) Received: from [207.6.254.8] (helo=[192.168.1.67]) by id.bluezbox.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from ) id 1Td3es-0004TI-K3; Mon, 26 Nov 2012 10:43:56 -0800 Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: FreeBSD on RaspberryPi From: Oleksandr Tymoshenko In-Reply-To: <1E75CEAC-32E8-4048-A1FB-DD59F996E22F@freebsd.org> Date: Mon, 26 Nov 2012 10:43:36 -0800 Message-Id: <3CE258BC-0A80-428A-8535-D589C50ADA86@bluezbox.com> References: <31C904E6-F230-4187-AE32-F9A7B1A7C38E@freebsd.org> <4A5E03E5-3295-4FD4-9A06-7D1C4E9E0C12@freebsd.org> <9E4DA920-BE72-4AA0-8159-43205CDEF5CD@bluezbox.com> <1E75CEAC-32E8-4048-A1FB-DD59F996E22F@freebsd.org> To: Tim Kientzle X-Mailer: Apple Mail (2.1499) Sender: gonzo@id.bluezbox.com X-Spam-Level: -- X-Spam-Report: Spam detection software, running on the system "id.bluezbox.com", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: On 2012-11-26, at 7:05 AM, Tim Kientzle wrote: > > On Nov 25, 2012, at 11:46 PM, Oleksandr Tymoshenko wrote: > >> >> On 2012-11-25, at 9:32 AM, Tim Kientzle wrote: >> >>> >>> On Nov 24, 2012, at 8:01 PM, Oleksandr Tymoshenko wrote: >>> >>>> >>>> On 2012-11-24, at 4:47 PM, Tim Kientzle wrote: >>>> >>>> >> >> .. skipped .. >> >>>> Tim, >>>> >>>> I'm almost done with getting kernel working with latest raspberry Pi firmware. Just need >>>> to figure out how to make ubldr pass FDT pointer from u-boot to kernel and handle >>>> /reserve/ information in ARM machdep code. >>> >>> Let me know if you need help with this. I've worked with >>> the ubldr FDT code recently. >>> >>>> Meanwhile I suggest editing .dts file manually. Fill out "display" node properties with proper >>>> display resolution and depth. Also add ukbd driver. That should get you working console. >>> >>> I'll try that. >>> >>> I'm curious: why is this information coming from the DTS? >>> That seems pretty complex; I thought that the >>> console code would query this information via the mailbox >>> interface. >> >> >> It's either FDT blob or message box interface. Implementation complexity is about the same. > > My thinking: > * Display resolution used by kernel has to match what the firmware uses. So the kernel should either get the information from the firmware or from the same place the firmware gets it from. > * We want ubldr to remain generic, so I'm reluctant to put things into it that are RaspberryPi-specific. > > If the firmware is putting the values into the FDT, then having the kernel get it from the FDT is another way for the kernel to get it from the firmware, so that sounds okay. > > >> But since we're getting other variables (like MAC address, memory size) from FDT I decided >> to be consistent and get all of them from there. > > I don't know about MAC address. Memory size is handled generically by ubldr using a standard interface to U-Boot, so it's not special to RaspberryPi. The FDT editing is just a standard way for ubldr to pass this to the [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] 0.0 HTML_MESSAGE BODY: HTML included in message Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Hackers , Alexander Yerenkow X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Nov 2012 18:43:58 -0000 On 2012-11-26, at 7:05 AM, Tim Kientzle wrote: >=20 > On Nov 25, 2012, at 11:46 PM, Oleksandr Tymoshenko wrote: >=20 >>=20 >> On 2012-11-25, at 9:32 AM, Tim Kientzle wrote: >>=20 >>>=20 >>> On Nov 24, 2012, at 8:01 PM, Oleksandr Tymoshenko wrote: >>>=20 >>>>=20 >>>> On 2012-11-24, at 4:47 PM, Tim Kientzle = wrote: >>>>=20 >>>>=20 >>=20 >> .. skipped .. >>=20 >>>> Tim, >>>>=20 >>>> I'm almost done with getting kernel working with latest raspberry = Pi firmware. Just need >>>> to figure out how to make ubldr pass FDT pointer from u-boot to = kernel and handle=20 >>>> /reserve/ information in ARM machdep code.=20 >>>=20 >>> Let me know if you need help with this. I've worked with >>> the ubldr FDT code recently. >>>=20 >>>> Meanwhile I suggest editing .dts file manually. Fill out "display" = node properties with proper >>>> display resolution and depth. Also add ukbd driver. That should get = you working console. >>>=20 >>> I'll try that. >>>=20 >>> I'm curious: why is this information coming from the DTS? >>> That seems pretty complex; I thought that the >>> console code would query this information via the mailbox >>> interface. >>=20 >>=20 >> It's either FDT blob or message box interface. Implementation = complexity is about the same. >=20 > My thinking: > * Display resolution used by kernel has to match what the firmware = uses. So the kernel should either get the information from the firmware = or from the same place the firmware gets it from. > * We want ubldr to remain generic, so I'm reluctant to put things = into it that are RaspberryPi-specific. >=20 > If the firmware is putting the values into the FDT, then having the = kernel get it from the FDT is another way for the kernel to get it from = the firmware, so that sounds okay. >=20 >=20 >> But since we're getting other variables (like MAC address, memory = size) from FDT I decided >> to be consistent and get all of them from there. >=20 > I don't know about MAC address. Memory size is handled generically by = ubldr using a standard interface to U-Boot, so it's not special to = RaspberryPi. The FDT editing is just a standard way for ubldr to pass = this to the kernel. >=20 >> The issue I'm facing is that ubldr gets FDT blob >> either from file directly or from ELF kernel itself. While on = Raspberry Pi to works as follows: >>=20 >> - Firmware loads .dtb file from SD card to specified address >=20 > Does RaspberryPi firmware now load an FDT? Yes, when requested by device_tree_address and device_tree = parameters in config.txt >=20 > Does the firmware now read the FDT to get its values for display = resolution, etc? > (I don't really like this because a lot of people need to tweak the = display settings and it's hard to tell a 6-year-old how to edit and = recompile an FDT.) No. firmware writes to .dtb display's native resolution (or the one = requested in config.txt) to it. Not vice versa.=20 That's the way to pass this information to kernel.=20 >=20 >> - Fixes up values like amount of memory, reserved regions, UART and = clock frequencies,=20 >> MAC address, display resolution. >> - Passes control to next link in boot chain (e.g. U-Boot) >=20 > To be clear: You say the RPi firmware is already doing this editing? >=20 > So the ubldr just has to pass the RPi FDT to the kernel? If so, = that's a lot simpler. Yes >=20 >> I'm thinking about adding compile-time constant FDT_BLOB_ADDRESS and = arrange possible >> FDT sources in following priority: >>=20 >> - Check FDT_BLOB_ADDRESS (if defined) >> - Check dtb file >> - Check ELF kernel >>=20 >> Does it sound sane enough?=20 >=20 > If the RPi firmware always loads the FDT at a fixed address > and the RPi firmware is using the FDT to configure itself, > then it makes a lot of sense. >=20 > It would be nice to do this without adding RPi-specific > code to ubldr. There will be no RPi-specific code. Just one more way to specify = location of generic FDT blob.=20= From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 27 02:54:11 2012 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 335ADAB0 for ; Tue, 27 Nov 2012 02:54:11 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from monday.kientzle.com (99-115-135-74.uvs.sntcca.sbcglobal.net [99.115.135.74]) by mx1.freebsd.org (Postfix) with ESMTP id DEB838FC12 for ; Tue, 27 Nov 2012 02:54:09 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id qAR2rZlh042768; Tue, 27 Nov 2012 02:53:35 GMT (envelope-from kientzle@freebsd.org) Received: from [192.168.2.143] (CiscoE3000 [192.168.1.65]) by kientzle.com with SMTP id d6dwi4qya4bpjumxbqph6hcibs; Tue, 27 Nov 2012 02:53:34 +0000 (UTC) (envelope-from kientzle@freebsd.org) Subject: Re: FreeBSD on RaspberryPi Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=us-ascii From: Tim Kientzle In-Reply-To: <3CE258BC-0A80-428A-8535-D589C50ADA86@bluezbox.com> Date: Mon, 26 Nov 2012 18:53:33 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <5020FB83-6EAA-49D5-A533-ED127AF956AB@freebsd.org> References: <31C904E6-F230-4187-AE32-F9A7B1A7C38E@freebsd.org> <4A5E03E5-3295-4FD4-9A06-7D1C4E9E0C12@freebsd.org> <9E4DA920-BE72-4AA0-8159-43205CDEF5CD@bluezbox.com> <1E75CEAC-32E8-4048-A1FB-DD59F996E22F@freebsd.org> <3CE258BC-0A80-428A-8535-D589C50ADA86@bluezbox.com> To: Oleksandr Tymoshenko X-Mailer: Apple Mail (2.1283) Cc: FreeBSD Hackers , Alexander Yerenkow X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Nov 2012 02:54:11 -0000 On Nov 26, 2012, at 10:43 AM, Oleksandr Tymoshenko wrote: >=20 > On 2012-11-26, at 7:05 AM, Tim Kientzle wrote: >=20 >>=20 >> On Nov 25, 2012, at 11:46 PM, Oleksandr Tymoshenko wrote: >>=20 >>>=20 >>> On 2012-11-25, at 9:32 AM, Tim Kientzle = wrote: >>>=20 >>>>=20 >>>> On Nov 24, 2012, at 8:01 PM, Oleksandr Tymoshenko wrote: >>>>=20 >>>>>=20 >>>>> On 2012-11-24, at 4:47 PM, Tim Kientzle = wrote: >>>>>=20 >>>>>=20 >>>=20 >>> .. skipped .. >>>=20 >>>>> Tim, >>>>>=20 >>>>> I'm almost done with getting kernel working with latest raspberry = Pi firmware. Just need >>>>> to figure out how to make ubldr pass FDT pointer from u-boot to = kernel and handle=20 >>>>> /reserve/ information in ARM machdep code.=20 >>>>=20 >>>> Let me know if you need help with this. I've worked with >>>> the ubldr FDT code recently. >>>>=20 >>>>> Meanwhile I suggest editing .dts file manually. Fill out "display" = node properties with proper >>>>> display resolution and depth. Also add ukbd driver. That should = get you working console. >>>>=20 >>>> I'll try that. >>>>=20 >>>> I'm curious: why is this information coming from the DTS? >>>> That seems pretty complex; I thought that the >>>> console code would query this information via the mailbox >>>> interface. >>>=20 >>>=20 >>> It's either FDT blob or message box interface. Implementation = complexity is about the same. >>=20 >> My thinking: >> * Display resolution used by kernel has to match what the firmware = uses. So the kernel should either get the information from the firmware = or from the same place the firmware gets it from. >> * We want ubldr to remain generic, so I'm reluctant to put things = into it that are RaspberryPi-specific. >>=20 >> If the firmware is putting the values into the FDT, then having the = kernel get it from the FDT is another way for the kernel to get it from = the firmware, so that sounds okay. >>=20 >>=20 >>> But since we're getting other variables (like MAC address, memory = size) from FDT I decided >>> to be consistent and get all of them from there. >>=20 >> I don't know about MAC address. Memory size is handled generically = by ubldr using a standard interface to U-Boot, so it's not special to = RaspberryPi. The FDT editing is just a standard way for ubldr to pass = this to the kernel. >>=20 >>> The issue I'm facing is that ubldr gets FDT blob >>> either from file directly or from ELF kernel itself. While on = Raspberry Pi to works as follows: >>>=20 >>> - Firmware loads .dtb file from SD card to specified address >>=20 >> Does RaspberryPi firmware now load an FDT? > Yes, when requested by device_tree_address and device_tree = parameters in config.txt >=20 >>=20 >> Does the firmware now read the FDT to get its values for display = resolution, etc? >> (I don't really like this because a lot of people need to tweak the = display settings and it's hard to tell a 6-year-old how to edit and = recompile an FDT.) > No. firmware writes to .dtb display's native resolution (or the = one requested in config.txt) to it. Not vice versa.=20 > That's the way to pass this information to kernel.=20 >=20 >>=20 >>> - Fixes up values like amount of memory, reserved regions, UART and = clock frequencies,=20 >>> MAC address, display resolution. >>> - Passes control to next link in boot chain (e.g. U-Boot) >>=20 >> To be clear: You say the RPi firmware is already doing this editing? >>=20 >> So the ubldr just has to pass the RPi FDT to the kernel? If so, = that's a lot simpler. > Yes >=20 >>=20 >>> I'm thinking about adding compile-time constant FDT_BLOB_ADDRESS and = arrange possible >>> FDT sources in following priority: >>>=20 >>> - Check FDT_BLOB_ADDRESS (if defined) >>> - Check dtb file >>> - Check ELF kernel >>>=20 >>> Does it sound sane enough?=20 >>=20 >> If the RPi firmware always loads the FDT at a fixed address >> and the RPi firmware is using the FDT to configure itself, >> then it makes a lot of sense. >>=20 >> It would be nice to do this without adding RPi-specific >> code to ubldr. >=20 > There will be no RPi-specific code. Just one more way to specify = location of generic FDT blob.=20 This all sounds good then. So we can put the FreeBSD .dts file on the MSDOS Boot partition, then: * Firmware will load it into memory and add display information. * ? ubldr will access the FDT and add memory information and MAC = address info ? * Kernel will then load it and use it to initialize. Maybe another possibility would be to script ubldr and have it load the = FDT from the correct location in memory. ubldr already knows how to = load an FDT and how to pass that FDT to the kernel. Tim From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 27 03:44:13 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 49F28D5F for ; Tue, 27 Nov 2012 03:44:13 +0000 (UTC) (envelope-from gonzo@id.bluezbox.com) Received: from id.bluezbox.com (id.bluezbox.com [88.198.91.248]) by mx1.freebsd.org (Postfix) with ESMTP id DDC128FC0C for ; Tue, 27 Nov 2012 03:44:12 +0000 (UTC) Received: from [88.198.91.248] (helo=[IPv6:::1]) by id.bluezbox.com with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from ) id 1TdC5h-0009SK-Ut for freebsd-hackers@freebsd.org; Mon, 26 Nov 2012 19:44:11 -0800 Message-ID: <50B43708.2000902@bluezbox.com> Date: Mon, 26 Nov 2012 19:44:08 -0800 From: Oleksandr Tymoshenko User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2 MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Re: FreeBSD on RaspberryPi References: <31C904E6-F230-4187-AE32-F9A7B1A7C38E@freebsd.org> <4A5E03E5-3295-4FD4-9A06-7D1C4E9E0C12@freebsd.org> <9E4DA920-BE72-4AA0-8159-43205CDEF5CD@bluezbox.com> <1E75CEAC-32E8-4048-A1FB-DD59F996E22F@freebsd.org> <3CE258BC-0A80-428A-8535-D589C50ADA86@bluezbox.com> <5020FB83-6EAA-49D5-A533-ED127AF956AB@freebsd.org> In-Reply-To: <5020FB83-6EAA-49D5-A533-ED127AF956AB@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: gonzo@id.bluezbox.com X-Spam-Level: -- X-Spam-Report: Spam detection software, running on the system "id.bluezbox.com", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: On 11/26/2012 6:53 PM, Tim Kientzle wrote: > > This all sounds good then. > > So we can put the FreeBSD .dts file on the MSDOS Boot partition, then: > * Firmware will load it into memory and add display information. > * ? ubldr will access the FDT and add memory information and MAC address info ? [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Nov 2012 03:44:13 -0000 On 11/26/2012 6:53 PM, Tim Kientzle wrote: > > This all sounds good then. > > So we can put the FreeBSD .dts file on the MSDOS Boot partition, then: > * Firmware will load it into memory and add display information. > * ? ubldr will access the FDT and add memory information and MAC address info ? Memory is somewhat complicated. memory node contains whole range of memory 256 or 512 Mb The VideoCore part is passed as memreserve table. memreserve is not real property. It's got own API calls in libfdt and does not fit nicely with generic OF framework we have in FreeBSD. So I'm kind of on a fence here: either we need merge memory regions and memreserve in FDT fixup procedure in ubldr. Or convert memreserve data to valid property in ubldr again. Or add hack to arm/arm/machdep.c, which is not really good. > * Kernel will then load it and use it to initialize. > > Maybe another possibility would be to script ubldr and have it load the FDT from the correct location in memory. ubldr already knows how to load an FDT and how to pass that FDT to the kernel. ubldr loads FDT only from raw file or ELF kernel. We'll need "fdt addr" subcommand.But now you mentioned it, I think it might be worth adding it instead of compile-time option. From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 27 09:48:39 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7B20BE23 for ; Tue, 27 Nov 2012 09:48:39 +0000 (UTC) (envelope-from white.heron@yahoo.com) Received: from nm3-vm5.bullet.mail.gq1.yahoo.com (nm3-vm5.bullet.mail.gq1.yahoo.com [98.136.218.148]) by mx1.freebsd.org (Postfix) with ESMTP id 281288FC0C for ; Tue, 27 Nov 2012 09:48:38 +0000 (UTC) Received: from [98.137.12.191] by nm3.bullet.mail.gq1.yahoo.com with NNFMP; 27 Nov 2012 09:46:42 -0000 Received: from [98.137.12.204] by tm12.bullet.mail.gq1.yahoo.com with NNFMP; 27 Nov 2012 09:46:42 -0000 Received: from [127.0.0.1] by omp1012.mail.gq1.yahoo.com with NNFMP; 27 Nov 2012 09:46:42 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 955723.82129.bm@omp1012.mail.gq1.yahoo.com Received: (qmail 27910 invoked by uid 60001); 27 Nov 2012 09:46:42 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1354009602; bh=DOn6J5iot4aQDPUnY5CfVM85aPDBjVtzR5ba6kNh84Y=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=P2B7PZ4ZYy/49TiVYBplz7i0tbnqtuJFzWOgMPIobXNLHThVjtCnsGuVnZAhlpp+UJhg+8DQAOqW1j7c//TXwF05p9QhBDmCGGD+v1CUGpznLbjlaqxyslXAXF+eIJq6V9ZZdpaFXt8/hhxymRGthw8lJeNw0vYVdQXAFtME9Ro= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=6SJb7eVDsEnXp+ROpPrke+1x9O+ELGg7AMbeufhDyaZif2Dmkm7wfnYK64B/bKoC23e6l+xZrSlt5LKrp3X7BG5spO7wrSFPXvCKd54cTuI8TcMrsh76jfNDgt80/UwnRJsOmptqeQRWCUO+zzF4L90OAS0Se3CZmn8bQbUlziU=; X-YMail-OSG: .SfmU9MVM1mwPwy9YAyXb1thNHURijfBCp1k1d3q_BQpItO TqXqBP.ZudCiUVMQNaqEl2scRdGEu0EuqZyIVxLraG20.vf12BZFo8_vZfyR qOosn7tbzPj76RwKkzUVYCXIRkdnANPhNGnJnIrgP_h6.RkNwa5SKpXCoxlj o8cfrPt5.pFFF9wjil0JRIUU6ZfLZ.l5fSAmmhpwDQf6cJ7j8_HMvYmdh4Cm 70hYm48NWR32.Z0Ayy_8VZnUQrQRnqgdOj6pITbSTA9Xs6A7N9046xVKCels zkm2V8chlKM.L1ZLQvSpsCBCpqUtSZtQXmgQ5NmQxAXVKqXXwpQQ5Dd_w_DR clmoKRBR60VGuNOtCyxVkg3cR_wM1IiUNpSjbEVFbl0atYYXsFIGZxgPtddX yPvMfjEz5RK5LfyBz_VMvEI2l3hVgbP_OpPdMoVti2TUYhkiUO_.4VR_oJez r16Jim2hXCd_CRSZkZ6S8ZpfRerjviCmSllfTw8SVXo52kC4YzV1kMCHWn.R _ Received: from [58.26.23.98] by web163503.mail.gq1.yahoo.com via HTTP; Tue, 27 Nov 2012 01:46:42 PST X-Rocket-MIMEInfo: 001.001, RGVhciBBbGwsCgpJIGFtIGtlZW4gdG8ga25vdyBpZiB5b3UgaGF2ZSBhbnkgZ3VpZGVsaW5lIGZvciBCdWlsZCBhbmQgUmVsZWFzZSBBdXRvbWF0aW9uIHdpdGggUGVybCBMYW5ndWFnZS4KSSBhbSBpbnRlcmVzdGVkIHRvIGRyaWxsIGRvd24gZnVydGhlciB0byBleHBsb3JlIHRoaXMgZmllbGQuIEkgYW0gZXhwZWN0aW5nIHRoYXQgSSBjb3VsZCBjb21lIG91dCBhIHNoZWxsIHNjcmlwdCB0aGF0IGFsbG93IHRoZSBlbmQtdXNlcnMgdG8gY2xpY2sgYW5kIGluc3RhbGwgdGhlIExpbnV4LCBNeVNRTCBhbmQgQ3IBMAEBAQE- X-Mailer: YahooMailWebService/0.8.127.475 References: <20121120030445.GA38037@zjl.local> Message-ID: <1354009602.20693.YahooMailNeo@web163503.mail.gq1.yahoo.com> Date: Tue, 27 Nov 2012 01:46:42 -0800 (PST) From: "white.heron white" Subject: Build and Release Automation with Perl Language for *.nix. To: "freebsd-questions@freebsd.org" In-Reply-To: <20121120030445.GA38037@zjl.local> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-questions@freebsd.org" , "freebsd-security@freebsd.org" , "freebsd-hubs@freebsd.org" , grarpamp , "freebsd-hackers@freebsd.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: "white.heron white" List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Nov 2012 09:48:39 -0000 Dear All,=0A=0AI am keen to know if you have any guideline for Build and Re= lease Automation with Perl Language.=0AI am interested to drill down furthe= r to explore this field. I am expecting that I could come out a shell scrip= t that allow the end-users to click and install the Linux, MySQL and Creati= ng necessary account information within that script.=0AKindly advised. Than= ks.=0A=A0=0ARegards,=0A=0AKAMARUDIN=0A=0A=0A=0A=0AH/p number: =A0(017) 362 = 3661=0AEmail:=A0white.heron@yahoo.com=0A=0A________________________________= =0A From: Zach Leslie =0ATo: Adrian Chadd =0ACc: freebsd-security@freebsd.org; freebsd-hackers@freebsd.org; f= reebsd-hubs@freebsd.org; grarpamp ; freebsd-questions@f= reebsd.org =0ASent: Tuesday, November 20, 2012 11:04 AM=0ASubject: Re: Free= BSD needs Git to ensure repo integrity [was: 2012 incident]=0A =0A> There's= a git repository. It's public. You can look at what goes into=0A> the Free= BSD git clone to get your assurance that things aren't being=0A> snuck in. = People are using it, right now.=0A=0AI've always been confused by this.=A0 = Which source repo is the true source=0Aof truth?=0A=0ATo obtain the FreeBSD= source, you can use CVS, SVN, or Git?=A0 Do all have=0Athe same level of s= upport?=A0 Are they all up to date?=0A=0A> Honestly, I'd rather see subvers= ion grow this kind of cryptographic=0A> signing of each commit in the short= term then migrate everyone over to=0A> git.=0A=0AHow much effor would thei= r really be involved, considering your link to=0Athe FreeBSD source repo on= github.=A0 Converting the repos to me seems=0Alike it would be the bulk of= it, and that work is already done.=A0 Help me=0Aunderstand please.=0A=0AAl= so, local branching and merging is amazing.=0A=0A-- =0AZach=0A_____________= __________________________________=0Afreebsd-hackers@freebsd.org mailing li= st=0Ahttp://lists.freebsd.org/mailman/listinfo/freebsd-hackers=0ATo unsubsc= ribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 27 22:27:21 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A3E2D142; Tue, 27 Nov 2012 22:27:21 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id BB0168FC1B; Tue, 27 Nov 2012 22:27:20 +0000 (UTC) Received: by mail-lb0-f182.google.com with SMTP id go10so9830175lbb.13 for ; Tue, 27 Nov 2012 14:27:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=6x4rTu2nHbaSWlFbT7SDCryzG8A5fxpamr9ZK/c2TYk=; b=PFBqzXk7ApITqsBuvpFOBDVx+t5Se7rFA72iaIqx107KcA553PLz5vg+0CfkcNwje+ jx5VFSDvLmbETVG9OYx5PLKujw7UremtAAGPGNzdvaZ0fy3bDbPxbqNE3MI1Z3rYh4aJ vbFjCd0YML3XOx/OlKnfOMq4+WagBoXphrdyVrP4BSVWNgAEsSm1NZbpOWSawP1krqsV +nliSaDYPQEDDDJU649m5juHo9IbkF8yIDD3+8RSFUP/7qAQiy+euZxUnYr90KrUufE8 qBMlSPFoIshG3WIAw3tVv+bI7wIkNqMnzd6MSnBHiZly4FtWY8KXTztsR6EOTHrDXh9H if+A== MIME-Version: 1.0 Received: by 10.152.105.44 with SMTP id gj12mr16234840lab.19.1354055239725; Tue, 27 Nov 2012 14:27:19 -0800 (PST) Received: by 10.112.61.33 with HTTP; Tue, 27 Nov 2012 14:27:19 -0800 (PST) Date: Tue, 27 Nov 2012 17:27:19 -0500 Message-ID: Subject: 9.1-RC3 IGB dropping connections. From: Zaphod Beeblebrox To: FreeBSD Stable , FreeBSD Hackers , FreeBSD Net Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Nov 2012 22:27:21 -0000 I've got an Intel server motherboard with 4x igb (and 1x em) on it. The motherboard in question is the S3420GPRX and the IGB's show up as: igb0: port 0x3020-0x303f mem 0xb1b20000-0xb1b3ffff,0xb1bc4000-0xb1bc7fff irq 19 at device 0.0 on pci3 igb0: Using MSIX interrupts with 9 vectors igb0: Ethernet address: 00:1e:67:3a:d5:40 igb0: Bound queue 0 to cpu 0 igb0: Bound queue 1 to cpu 1 igb0: Bound queue 2 to cpu 2 igb0: Bound queue 3 to cpu 3 igb0: Bound queue 4 to cpu 4 igb0: Bound queue 5 to cpu 5 igb0: Bound queue 6 to cpu 6 igb0: Bound queue 7 to cpu 7 ... now... I have this machine (right now) on the local lan with my windows 7 workstation and putty sees the ssh connection as dropped often. I say often --- in that it can happen in a minute or two... it often seems to happen when there is active output going to the window (like a download counter running), but I also say "often" in that... it seems slightly random... but it _is_ incessant... as in very "often." This seems like something that we should ship with 9.1... From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 27 23:08:00 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 48C3C8D6; Tue, 27 Nov 2012 23:08:00 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from mail-la0-f54.google.com (mail-la0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 625738FC14; Tue, 27 Nov 2012 23:07:59 +0000 (UTC) Received: by mail-la0-f54.google.com with SMTP id j13so12431342lah.13 for ; Tue, 27 Nov 2012 15:07:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=/+dEsfSBwi9Ec6ZJUK1KL01whzSyaWktFaaIVnSqnyg=; b=iq4txiyF/DKrQVsDII+bBvyvJBvEOCg1xLUGaoSXZ/CtnY7cJ54fil9gWzzWS7xMro /vurX0lye6HVsrKKFDSPFf7U43hvvv0PdPVddozu25lbBnW3uvgK10529ghI7HnQ3uiH ZvDS+gCzR1rKUQ/Dy7WyLsjvTxwHAOtTOObEGtIVLych06je2szQojKoOCwto5ix7Oc6 S0X7BO3WRaMKdypD5+t0bIvA9sGiG7oFz6QeaUEg1wWI65CpHuvh1B1//+724awuWGoY gqzw+54GHivLL9ujHxr/u9+z4ZBWSO2woj0T3IhoBQzqdGMWGj3KQM4VKJ4BbSS7Oa3P 1+tw== MIME-Version: 1.0 Received: by 10.112.103.5 with SMTP id fs5mr7400465lbb.23.1354057676946; Tue, 27 Nov 2012 15:07:56 -0800 (PST) Received: by 10.112.61.33 with HTTP; Tue, 27 Nov 2012 15:07:56 -0800 (PST) In-Reply-To: References: Date: Tue, 27 Nov 2012 18:07:56 -0500 Message-ID: Subject: Re: 9.1-RC3 IGB dropping connections. From: Zaphod Beeblebrox To: FreeBSD Stable , FreeBSD Hackers , FreeBSD Net Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Nov 2012 23:08:00 -0000 A further update to my problem: it only seems to occur when there is largely traffic "out" ie: the window is active with ... but typing in the window seems to prevent the effect. From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 27 23:19:43 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1559A362 for ; Tue, 27 Nov 2012 23:19:43 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.freebsd.org (Postfix) with ESMTP id 72BCB8FC12 for ; Tue, 27 Nov 2012 23:19:42 +0000 (UTC) Received: (qmail 37440 invoked from network); 28 Nov 2012 00:51:15 -0000 Received: from unknown (HELO [62.48.0.94]) ([62.48.0.94]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 28 Nov 2012 00:51:15 -0000 Message-ID: <50B54AE7.3040901@freebsd.org> Date: Wed, 28 Nov 2012 00:21:11 +0100 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2 MIME-Version: 1.0 To: Zaphod Beeblebrox Subject: Re: 9.1-RC3 IGB dropping connections. References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Hackers , FreeBSD Stable , FreeBSD Net X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Nov 2012 23:19:43 -0000 On 27.11.2012 23:27, Zaphod Beeblebrox wrote: > I've got an Intel server motherboard with 4x igb (and 1x em) on it. > The motherboard in question is the S3420GPRX and the IGB's show up as: > > igb0: port > 0x3020-0x303f mem 0xb1b20000-0xb1b3ffff,0xb1bc4000-0xb1bc7fff irq 19 > at device 0.0 on pci3 > igb0: Using MSIX interrupts with 9 vectors > igb0: Ethernet address: 00:1e:67:3a:d5:40 > igb0: Bound queue 0 to cpu 0 > igb0: Bound queue 1 to cpu 1 > igb0: Bound queue 2 to cpu 2 > igb0: Bound queue 3 to cpu 3 > igb0: Bound queue 4 to cpu 4 > igb0: Bound queue 5 to cpu 5 > igb0: Bound queue 6 to cpu 6 > igb0: Bound queue 7 to cpu 7 > > ... now... I have this machine (right now) on the local lan with my > windows 7 workstation and putty sees the ssh connection as dropped > often. I say often --- in that it can happen in a minute or two... it > often seems to happen when there is active output going to the window > (like a download counter running), but I also say "often" in that... > it seems slightly random... but it _is_ incessant... as in very > "often." r243570 in CURRENT should likely fix this issue. It's only 27 hours old and hasn't been MFC'd yet. > This seems like something that we should ship with 9.1... -- Andre From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 27 23:15:13 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 282EFE2D; Tue, 27 Nov 2012 23:15:13 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-vc0-f182.google.com (mail-vc0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 93E928FC08; Tue, 27 Nov 2012 23:15:12 +0000 (UTC) Received: by mail-vc0-f182.google.com with SMTP id fo13so17614106vcb.13 for ; Tue, 27 Nov 2012 15:15:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=d5S50J9057WUI3BvtZmoHtGMbN+ZQQGbwgDv687Z5Ws=; b=S4vdGVOrB00Lr1ni3ktlvze9gqJZDGVnAuu1031ogrkgydafNJ4NZkhwlz8/AI/RT+ Xi7dF2QMQxN2PY6VVGO4KHXCUM+DerpyGmHqJ55nFvf3TxEz9+Pdilqrme1ipTDoLjtG pbRN41Iqoq6fXYcVR+aeIVfiZsfW7C2ZpKd62OCtRLpdwc/IPku0UV6w509UUNuzNJa2 qrCehHFkrssHyOYOda6cRjkiMThRyk3REWefChYCjXI6cQOldJ6aU5ea5fZ4NzVeuH8P 02PiZJGj4VnQs6J8c8scsAR+ZLVU9Fy8ovRuYZoGggsXysmAgPGswvRZ3P3VQT4TVO1l FBAQ== MIME-Version: 1.0 Received: by 10.58.55.198 with SMTP id u6mr27555378vep.35.1354058111603; Tue, 27 Nov 2012 15:15:11 -0800 (PST) Received: by 10.59.3.165 with HTTP; Tue, 27 Nov 2012 15:15:11 -0800 (PST) In-Reply-To: References: Date: Tue, 27 Nov 2012 15:15:11 -0800 Message-ID: Subject: Re: 9.1-RC3 IGB dropping connections. From: Jack Vogel To: Zaphod Beeblebrox X-Mailman-Approved-At: Tue, 27 Nov 2012 23:25:57 +0000 Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Hackers , FreeBSD Stable , FreeBSD Net X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Nov 2012 23:15:13 -0000 Something in your environment, have lots of users with this driver in very demanding environments and I have not been seeing reports of this sort. Jack On Tue, Nov 27, 2012 at 2:27 PM, Zaphod Beeblebrox wrote: > I've got an Intel server motherboard with 4x igb (and 1x em) on it. > The motherboard in question is the S3420GPRX and the IGB's show up as: > > igb0: port > 0x3020-0x303f mem 0xb1b20000-0xb1b3ffff,0xb1bc4000-0xb1bc7fff irq 19 > at device 0.0 on pci3 > igb0: Using MSIX interrupts with 9 vectors > igb0: Ethernet address: 00:1e:67:3a:d5:40 > igb0: Bound queue 0 to cpu 0 > igb0: Bound queue 1 to cpu 1 > igb0: Bound queue 2 to cpu 2 > igb0: Bound queue 3 to cpu 3 > igb0: Bound queue 4 to cpu 4 > igb0: Bound queue 5 to cpu 5 > igb0: Bound queue 6 to cpu 6 > igb0: Bound queue 7 to cpu 7 > > ... now... I have this machine (right now) on the local lan with my > windows 7 workstation and putty sees the ssh connection as dropped > often. I say often --- in that it can happen in a minute or two... it > often seems to happen when there is active output going to the window > (like a download counter running), but I also say "often" in that... > it seems slightly random... but it _is_ incessant... as in very > "often." > > This seems like something that we should ship with 9.1... > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 28 00:04:37 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 04FFC14E; Wed, 28 Nov 2012 00:04:37 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id E3B5A8FC12; Wed, 28 Nov 2012 00:04:35 +0000 (UTC) Received: by mail-lb0-f182.google.com with SMTP id go10so9890367lbb.13 for ; Tue, 27 Nov 2012 16:04:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=jApgb7ZMT+nFwY7qUJ1IHjdJUtoyhK5DnSZD4rrknjQ=; b=UzH8D2smXYyEFQhppmULBaWmeCkfaTYwqfyL6/IsT64i+CsGn0pL8O3n6ba7zYER3J Zf3wCvpWatfaUS5CJxIt6Ezr2TiSVEOC58LYGFppHtQ9ZTLVWoHM9BrzGgep1vX19ytH 50an8YN/CL/nEalDvwiyX7/BvZ9C/ntSugtiYaFjgpVf+4+Jtb8KyjWXVMEg82dlUpGa 3Mo8DD0UFDo4BF9PVik1/2fF2IP2x1z5IwXKcF0wYjkt6ikVM5uB9MyrSQptNIVPCL9P zI9o2HJXged/ioqepMVj3CAhk5lsRePXdY1tFj3o6+N30h9l9AHuYgrHovUxrAyTwiH0 X0tw== MIME-Version: 1.0 Received: by 10.112.101.232 with SMTP id fj8mr3665447lbb.83.1354061074686; Tue, 27 Nov 2012 16:04:34 -0800 (PST) Received: by 10.112.61.33 with HTTP; Tue, 27 Nov 2012 16:04:34 -0800 (PST) In-Reply-To: <50B54AE7.3040901@freebsd.org> References: <50B54AE7.3040901@freebsd.org> Date: Tue, 27 Nov 2012 19:04:34 -0500 Message-ID: Subject: Re: 9.1-RC3 IGB dropping connections. From: Zaphod Beeblebrox To: Andre Oppermann Content-Type: text/plain; charset=ISO-8859-1 Cc: FreeBSD Hackers , FreeBSD Stable , FreeBSD Net X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Nov 2012 00:04:37 -0000 To Jack Vogel's comment, this problem only seems to occur on systems that are exceedingly lightly loaded (in this case, not yet in production and I'm the only one using it). On Tue, Nov 27, 2012 at 6:21 PM, Andre Oppermann wrote: > r243570 in CURRENT should likely fix this issue. It's only 27 hours old > and hasn't been MFC'd yet. I'm not sure this addresses what I'm seeing. It's a pause the the traffic in the shell that is "fixed" by causing some traffic on the return channel (watching for the pause --- and then hitting enter a few times seems to fix it). I'd expect that TCP retransmission should take care of this regularly ... but in this case, it doesn't... for whatever reason ... From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 28 02:26:14 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B115D2A3; Wed, 28 Nov 2012 02:26:14 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1-6.sentex.ca [IPv6:2607:f3e0:0:1::12]) by mx1.freebsd.org (Postfix) with ESMTP id 6E5368FC08; Wed, 28 Nov 2012 02:26:14 +0000 (UTC) Received: from [192.168.43.26] (pyroxene.sentex.ca [199.212.134.18]) by smarthost1.sentex.ca (8.14.5/8.14.5) with ESMTP id qAS2Q9j1090272; Tue, 27 Nov 2012 21:26:09 -0500 (EST) (envelope-from mike@sentex.net) Message-ID: <50B57632.6050004@sentex.net> Date: Tue, 27 Nov 2012 21:25:54 -0500 From: Mike Tancsa Organization: Sentex Communications User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: Zaphod Beeblebrox Subject: Re: 9.1-RC3 IGB dropping connections. References: In-Reply-To: X-Enigmail-Version: 1.4.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.72 on 64.7.153.18 Cc: FreeBSD Hackers , FreeBSD Stable , FreeBSD Net X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Nov 2012 02:26:14 -0000 On 11/27/2012 5:27 PM, Zaphod Beeblebrox wrote: > I've got an Intel server motherboard with 4x igb (and 1x em) on it. > The motherboard in question is the S3420GPRX and the IGB's show up as: > > igb0: port > 0x3020-0x303f mem 0xb1b20000-0xb1b3ffff,0xb1bc4000-0xb1bc7fff irq 19 > at device 0.0 on pci3 > igb0: Using MSIX interrupts with 9 vectors > igb0: Ethernet address: 00:1e:67:3a:d5:40 > igb0: Bound queue 0 to cpu 0 > > ... now... I have this machine (right now) on the local lan with my > windows 7 workstation and putty sees the ssh connection as dropped > often. I say often --- in that it can happen in a minute or two... it > often seems to happen when there is active output going to the window > (like a download counter running), but I also say "often" in that... > it seems slightly random... but it _is_ incessant... as in very > "often." > Are you using pf ? Also, did you confirm it is the igb nic and not something more general ? e.g. if you put in a different nic, does the problem go away ? If you are using pf, lets see the rules. ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 28 01:18:43 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0DDDDDFB; Wed, 28 Nov 2012 01:18:43 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-vc0-f182.google.com (mail-vc0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 6B83F8FC16; Wed, 28 Nov 2012 01:18:42 +0000 (UTC) Received: by mail-vc0-f182.google.com with SMTP id fo13so17722779vcb.13 for ; Tue, 27 Nov 2012 17:18:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=G7uEvtoyRtwp/N4FeZkS59lK1Bj+ms2J+BE9pK0JmmI=; b=mfqyr/XnK04dNgV0PHd6t7uK9GXaeVoDZfaArqGHR3Bn0wp7VUq1MFLlVTe1h2lXD3 eXUNsN1CYbK7XPSmJju0Pkw0H+LTUwRhrl44pbtm/Kfpn3d2xY/f2izoaqx/IEjgbb/v o4a/lPLXjUJogHIWsgk3M07M1lFTZ4DnNHFDSFKHarCmkRkqBIg9pqBIeUv3oR8Pn3SK gW5aTtDghPLb4hCqZaelafVcdG65wM+JMxOUT+8WKY1GD7slr90cNAFJmF3hFsgy+5Xp D7KZTuu+28BhWlMxDEn8rA15TH0m70rnHIPm2InzFa/TWW9Kzj1VvJPQSVcAbVnd6qzl djxA== MIME-Version: 1.0 Received: by 10.52.32.229 with SMTP id m5mr23930818vdi.5.1354065521599; Tue, 27 Nov 2012 17:18:41 -0800 (PST) Received: by 10.59.3.165 with HTTP; Tue, 27 Nov 2012 17:18:41 -0800 (PST) In-Reply-To: References: <50B54AE7.3040901@freebsd.org> Date: Tue, 27 Nov 2012 17:18:41 -0800 Message-ID: Subject: Re: 9.1-RC3 IGB dropping connections. From: Jack Vogel To: Zaphod Beeblebrox X-Mailman-Approved-At: Wed, 28 Nov 2012 02:38:47 +0000 Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Hackers , Andre Oppermann , FreeBSD Stable , FreeBSD Net X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Nov 2012 01:18:43 -0000 On Tue, Nov 27, 2012 at 4:04 PM, Zaphod Beeblebrox wrote: > To Jack Vogel's comment, this problem only seems to occur on systems > that are exceedingly lightly loaded (in this case, not yet in > production and I'm the only one using it). > > On Tue, Nov 27, 2012 at 6:21 PM, Andre Oppermann > wrote: > > > r243570 in CURRENT should likely fix this issue. It's only 27 hours old > > and hasn't been MFC'd yet. > > I'm not sure this addresses what I'm seeing. It's a pause the the > traffic in the shell that is "fixed" by causing some traffic on the > return channel (watching for the pause --- and then hitting enter a > few times seems to fix it). I'd expect that TCP retransmission should > take care of this regularly ... but in this case, it doesn't... for > whatever reason ... > > You say it drops the connection but show no specifics, may I see the system message file from boot til it happens. Also how about a pciconf -lv while you're at it. Jack From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 28 02:36:18 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8859C5A9 for ; Wed, 28 Nov 2012 02:36:18 +0000 (UTC) (envelope-from barney_cordoba@yahoo.com) Received: from nm6-vm0.bullet.mail.ne1.yahoo.com (nm6-vm0.bullet.mail.ne1.yahoo.com [98.138.91.54]) by mx1.freebsd.org (Postfix) with ESMTP id 3EF538FC0C for ; Wed, 28 Nov 2012 02:36:17 +0000 (UTC) Received: from [98.138.90.48] by nm6.bullet.mail.ne1.yahoo.com with NNFMP; 28 Nov 2012 02:36:11 -0000 Received: from [98.138.226.166] by tm1.bullet.mail.ne1.yahoo.com with NNFMP; 28 Nov 2012 02:36:11 -0000 Received: from [127.0.0.1] by omp1067.mail.ne1.yahoo.com with NNFMP; 28 Nov 2012 02:36:11 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 894575.50440.bm@omp1067.mail.ne1.yahoo.com Received: (qmail 66141 invoked by uid 60001); 28 Nov 2012 02:36:11 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1354070171; bh=yWJ0q6LRo4+Mj1EZHNqY+2MIgUnP/Hz1kWT3fQdIYzQ=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=tPUTM9PU3SUhMuJFHS6ZyU/TOqtv7UBlw7kAHs2dGtBBuTcM/WYHwtAJAcB+8Oy46ehwlmOdj6Hvk6dDWQcHlya9wMA6eFuH/6YT5SHhT3tCgDsn4m7ob0OupAjPi3V/ALIvjEqzWAd90Nte/FIZQN3e/z0C7quXYBmGb1Wyusw= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=dZQ2Kvk7od7dMuWIh5tdHjcr4vR5iMV9yPR09+R0zNPn+AhHRG9b6BOVvei6SBF6DVvKv1QHMlWhjuawk/51O6zXsEP373AMflwI1NR8ZiKZxOPcREGdW4ZLUbaCrIF6Xex83JsdBms5klTd2pB1jiubGmj/i1hX4eoq2GDpIBQ=; X-YMail-OSG: HMid_9YVM1mAsVo0g8ut3mj5pWob12YwQc1RIh8mhE.svZ1 OLs_V9MT4e9WBPaSDb6DEkMpzAWWXz94bB2eCBD7iAghcyp_JfrmgALrMS3Z C0Ap1Gjx1sfsrQqyjd4hya1ufXbBm.y3JVBKv5q.a9pGRbz6X5bef8b8hQe2 rClQtf8IKB8VTua6vQ0x8VViMd7f3TSIovFMsVltnqp5UipTOrGcf_JLuOrX NrkDeeH4ErT7sl5q2Brr3JW_D1MOVfLsGhivWf8v2gyrhx6kzacqTmVnvqW2 DzLc2nA1QjoCDrNElvoDU0bS.T3osNxzqAAzbLdhxyqILfsxxwURcWheKZ2z wHcfu6qX05x8bXmMQp5.7vk6Q00zK.MDY.ATO66a1yPYRbDYTaEjqxT_GKL4 fKBJ2LqMH5PWsNKkwN45DuvlxkHE.vvzKis3cLIeUFneTRmHqmrWEE1Tc9k_ xG_7m5wP5e2fr0L1fpxpPMx2EjuSeDgkJAXGcvcNDVC8lERU.Kn_F2P_uBk6 uDAoZd3Gf7cFX4KczlN9IAEMs5QkWYGhgDd7TRzeOnWgcIGmNfhx.EL0xEAv gD0aTbQON0TA7OuICm_OA5jO4 Received: from [174.48.128.27] by web121603.mail.ne1.yahoo.com via HTTP; Tue, 27 Nov 2012 18:36:11 PST X-Rocket-MIMEInfo: 001.001, CgotLS0gT24gVHVlLCAxMS8yNy8xMiwgWmFwaG9kIEJlZWJsZWJyb3ggPHpiZWVibGVAZ21haWwuY29tPiB3cm90ZToKCj4gRnJvbTogWmFwaG9kIEJlZWJsZWJyb3ggPHpiZWVibGVAZ21haWwuY29tPgo.IFN1YmplY3Q6IFJlOiA5LjEtUkMzIElHQiBkcm9wcGluZyBjb25uZWN0aW9ucy4KPiBUbzogIkFuZHJlIE9wcGVybWFubiIgPGFuZHJlQGZyZWVic2Qub3JnPgo.IENjOiAiRnJlZUJTRCBIYWNrZXJzIiA8ZnJlZWJzZC1oYWNrZXJzQGZyZWVic2Qub3JnPiwgIkZyZWVCU0QgU3RhYmxlIiA8ZnJlZWJzZC0BMAEBAQE- X-Mailer: YahooMailClassic/15.0.8 YahooMailWebService/0.8.127.475 Message-ID: <1354070171.39734.YahooMailClassic@web121603.mail.ne1.yahoo.com> Date: Tue, 27 Nov 2012 18:36:11 -0800 (PST) From: Barney Cordoba Subject: Re: 9.1-RC3 IGB dropping connections. To: Andre Oppermann , Zaphod Beeblebrox In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Wed, 28 Nov 2012 02:59:29 +0000 Cc: FreeBSD Hackers , FreeBSD Stable , FreeBSD Net X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Nov 2012 02:36:18 -0000 =0A=0A--- On Tue, 11/27/12, Zaphod Beeblebrox wrote:=0A= =0A> From: Zaphod Beeblebrox =0A> Subject: Re: 9.1-RC3 I= GB dropping connections.=0A> To: "Andre Oppermann" =0A> = Cc: "FreeBSD Hackers" , "FreeBSD Stable" , "FreeBSD Net" =0A> Date: = Tuesday, November 27, 2012, 7:04 PM=0A> To Jack Vogel's comment, this probl= em=0A> only seems to occur on systems=0A> that are exceedingly lightly load= ed (in this case, not yet=0A> in=0A> production and I'm the only one using = it).=0A> =0A> On Tue, Nov 27, 2012 at 6:21 PM, Andre Oppermann =0A> wrote:=0A> =0A> > r243570 in CURRENT should likely fix this iss= ue.=A0=0A> It's only 27 hours old=0A> > and hasn't been MFC'd yet.=0A> =0A>= I'm not sure this addresses what I'm seeing.=A0 It's a=0A> pause the the= =0A> traffic in the shell that is "fixed" by causing some traffic=0A> on th= e=0A> return channel (watching for the pause --- and then hitting=0A> enter= a=0A> few times seems to fix it).=A0 I'd expect that TCP=0A> retransmissio= n should=0A> take care of this regularly=A0 ... but in this case, it=0A> do= esn't... for=0A> whatever reason ...=0A=0AThe symptoms point to something h= aving to do with kicking=0Athe start/xmit queue. You might want to check th= e if_snd queues in=0Athe timer routine.=0A=0A=0A From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 28 03:26:58 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DA4506AB; Wed, 28 Nov 2012 03:26:57 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from mail-la0-f54.google.com (mail-la0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id CBF598FC13; Wed, 28 Nov 2012 03:26:56 +0000 (UTC) Received: by mail-la0-f54.google.com with SMTP id j13so12568167lah.13 for ; Tue, 27 Nov 2012 19:26:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=FQGyVxOs8Js2WVpAXEm04sxfqILqpAWtaB8YazpaSP4=; b=n+FCqogHGlLNlZ4UDRKtYTi5I1h2lP3NJZeo/EMjDsuamSmfuNRSeu/jHeARqUJ0tE ODqaH81nemelBdgPlwmBcoLnVR3VUWWCS7d55KlSnfp68hZbOkDEa3PVDQHHQwEUjLjk t7DV1XP/avlzELYlQTbF2UmsHotALIgGSO7eNbIfFuTtCULH8xVXW3N/nwsFPU+acrw6 W5MDN2PARQQ4YUIav5M2W+HjkwlQySrwjAiTwE5VpU/DnNrWc+f5hKtZ7Oo7Ww29MC5O TjpT2mSbGfS035WhLSW5k7FAXtr3lGpt5F5GHI8IH5KfYn1qckPa907h+Y6OOp6Ugw9t yECQ== MIME-Version: 1.0 Received: by 10.152.104.50 with SMTP id gb18mr17005798lab.9.1354073215441; Tue, 27 Nov 2012 19:26:55 -0800 (PST) Received: by 10.112.61.33 with HTTP; Tue, 27 Nov 2012 19:26:55 -0800 (PST) In-Reply-To: <50B57632.6050004@sentex.net> References: <50B57632.6050004@sentex.net> Date: Tue, 27 Nov 2012 22:26:55 -0500 Message-ID: Subject: Re: 9.1-RC3 IGB dropping connections. From: Zaphod Beeblebrox To: Mike Tancsa Content-Type: text/plain; charset=ISO-8859-1 Cc: FreeBSD Hackers , FreeBSD Stable , FreeBSD Net X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Nov 2012 03:26:58 -0000 On Tue, Nov 27, 2012 at 9:25 PM, Mike Tancsa wrote: > Are you using pf ? Also, did you confirm it is the igb nic and not > something more general ? e.g. if you put in a different nic, does the > problem go away ? No pf, the motherboard em-driver NIC does not have this problem. In reply to another message, igb1@pci0:3:0:1: class=0x020000 card=0x34f28086 chip=0x10c98086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82576 Gigabit Network Connection' class = network subclass = ethernet Here is /var/log/messages. The IPv6 chatter is something that everything on the network has problems with --- duplicate IPv6 addresses that are not duplicate. Nov 26 12:53:49 ccsw1 newsyslog[1419]: logfile first created Nov 26 12:53:49 ccsw1 syslogd: kernel boot file is /boot/kernel/kernel Nov 26 12:53:49 ccsw1 kernel: Copyright (c) 1992-2012 The FreeBSD Project. Nov 26 12:53:49 ccsw1 kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Nov 26 12:53:49 ccsw1 kernel: The Regents of the University of California. All rights reserved. Nov 26 12:53:49 ccsw1 kernel: FreeBSD is a registered trademark of The FreeBSD Foundation. Nov 26 12:53:49 ccsw1 kernel: FreeBSD 9.1-RC3 #0 r242324: Tue Oct 30 00:58:57 UTC 2012 Nov 26 12:53:49 ccsw1 kernel: root@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 Nov 26 12:53:49 ccsw1 kernel: CPU: Intel(R) Xeon(R) CPU X3440 @ 2.53GHz (2533.35-MHz K8-class CPU) Nov 26 12:53:49 ccsw1 kernel: Origin = "GenuineIntel" Id = 0x106e5 Family = 6 Model = 1e Stepping = 5 Nov 26 12:53:49 ccsw1 kernel: Features=0xbfebfbff Nov 26 12:53:49 ccsw1 kernel: Features2=0x98e3fd Nov 26 12:53:49 ccsw1 kernel: AMD Features=0x28100800 Nov 26 12:53:49 ccsw1 kernel: AMD Features2=0x1 Nov 26 12:53:49 ccsw1 kernel: TSC: P-state invariant, performance statistics Nov 26 12:53:49 ccsw1 kernel: real memory = 17179869184 (16384 MB) Nov 26 12:53:49 ccsw1 kernel: avail memory = 16458309632 (15695 MB) Nov 26 12:53:49 ccsw1 kernel: Event timer "LAPIC" quality 400 Nov 26 12:53:49 ccsw1 kernel: ACPI APIC Table: Nov 26 12:53:49 ccsw1 kernel: FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs Nov 26 12:53:49 ccsw1 kernel: FreeBSD/SMP: 1 package(s) x 4 core(s) x 2 SMT threads Nov 26 12:53:49 ccsw1 kernel: cpu0 (BSP): APIC ID: 0 Nov 26 12:53:49 ccsw1 kernel: cpu1 (AP): APIC ID: 1 Nov 26 12:53:49 ccsw1 kernel: cpu2 (AP): APIC ID: 2 Nov 26 12:53:49 ccsw1 kernel: cpu3 (AP): APIC ID: 3 Nov 26 12:53:49 ccsw1 kernel: cpu4 (AP): APIC ID: 4 Nov 26 12:53:49 ccsw1 kernel: cpu5 (AP): APIC ID: 5 Nov 26 12:53:49 ccsw1 kernel: cpu6 (AP): APIC ID: 6 Nov 26 12:53:49 ccsw1 kernel: cpu7 (AP): APIC ID: 7 Nov 26 12:53:49 ccsw1 kernel: ioapic0 irqs 0-23 on motherboard Nov 26 12:53:49 ccsw1 kernel: lapic0: Forcing LINT1 to edge trigger Nov 26 12:53:49 ccsw1 kernel: kbd1 at kbdmux0 Nov 26 12:53:49 ccsw1 kernel: acpi0: on motherboard Nov 26 12:53:49 ccsw1 kernel: acpi0: Power Button (fixed) Nov 26 12:53:49 ccsw1 kernel: cpu0: on acpi0 Nov 26 12:53:49 ccsw1 kernel: cpu1: on acpi0 Nov 26 12:53:49 ccsw1 kernel: cpu2: on acpi0 Nov 26 12:53:49 ccsw1 kernel: cpu3: on acpi0 Nov 26 12:53:49 ccsw1 kernel: cpu4: on acpi0 Nov 26 12:53:49 ccsw1 kernel: cpu5: on acpi0 Nov 26 12:53:49 ccsw1 kernel: cpu6: on acpi0 Nov 26 12:53:49 ccsw1 kernel: cpu7: on acpi0 Nov 26 12:53:49 ccsw1 kernel: atrtc0: port 0x70-0x71,0x74-0x77 irq 8 on acpi0 Nov 26 12:53:49 ccsw1 kernel: Event timer "RTC" frequency 32768 Hz quality 0 Nov 26 12:53:49 ccsw1 kernel: attimer0: port 0x40-0x43,0x50-0x53 irq 0 on acpi0 Nov 26 12:53:49 ccsw1 kernel: Timecounter "i8254" frequency 1193182 Hz quality 0 Nov 26 12:53:49 ccsw1 kernel: Event timer "i8254" frequency 1193182 Hz quality 100 Nov 26 12:53:49 ccsw1 kernel: hpet0: iomem 0xfed00000-0xfed003ff on acpi0 Nov 26 12:53:49 ccsw1 kernel: Timecounter "HPET" frequency 14318180 Hz quality 950 Nov 26 12:53:49 ccsw1 kernel: Event timer "HPET" frequency 14318180 Hz quality 550 Nov 26 12:53:49 ccsw1 kernel: Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 Nov 26 12:53:49 ccsw1 kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 Nov 26 12:53:49 ccsw1 kernel: pcib0: port 0xcf8-0xcff on acpi0 Nov 26 12:53:49 ccsw1 kernel: pci0: on pcib0 Nov 26 12:53:49 ccsw1 kernel: pcib1: irq 16 at device 3.0 on pci0 Nov 26 12:53:49 ccsw1 kernel: pci1: on pcib1 Nov 26 12:53:49 ccsw1 kernel: pcib2: at device 0.0 on pci1 Nov 26 12:53:49 ccsw1 kernel: pci2: on pcib2 Nov 26 12:53:49 ccsw1 kernel: pcib3: at device 2.0 on pci2 Nov 26 12:53:49 ccsw1 kernel: pci3: on pcib3 Nov 26 12:53:49 ccsw1 kernel: igb0: port 0x3020-0x303f mem 0xb1b20000-0xb1b3ffff,0xb1bc4000-0xb1bc7fff irq 19 at device 0.0 on pci3 Nov 26 12:53:49 ccsw1 kernel: igb0: Using MSIX interrupts with 9 vectors Nov 26 12:53:49 ccsw1 kernel: igb0: Ethernet address: 00:1e:67:3a:d5:40 Nov 26 12:53:49 ccsw1 kernel: igb0: Bound queue 0 to cpu 0 Nov 26 12:53:49 ccsw1 kernel: igb0: Bound queue 1 to cpu 1 Nov 26 12:53:49 ccsw1 kernel: igb0: Bound queue 2 to cpu 2 Nov 26 12:53:49 ccsw1 kernel: igb0: Bound queue 3 to cpu 3 Nov 26 12:53:49 ccsw1 kernel: igb0: Bound queue 4 to cpu 4 Nov 26 12:53:49 ccsw1 kernel: igb0: Bound queue 5 to cpu 5 Nov 26 12:53:49 ccsw1 kernel: igb0: Bound queue 6 to cpu 6 Nov 26 12:53:49 ccsw1 kernel: igb0: Bound queue 7 to cpu 7 Nov 26 12:53:49 ccsw1 kernel: igb1: port 0x3000-0x301f mem 0xb1b00000-0xb1b1ffff,0xb1bc0000-0xb1bc3fff irq 18 at device 0.1 on pci3 Nov 26 12:53:49 ccsw1 kernel: igb1: Using MSIX interrupts with 9 vectors Nov 26 12:53:49 ccsw1 kernel: igb1: Ethernet address: 00:1e:67:3a:d5:41 Nov 26 12:53:49 ccsw1 kernel: igb1: Bound queue 0 to cpu 0 Nov 26 12:53:49 ccsw1 kernel: igb1: Bound queue 1 to cpu 1 Nov 26 12:53:49 ccsw1 kernel: igb1: Bound queue 2 to cpu 2 Nov 26 12:53:49 ccsw1 kernel: igb1: Bound queue 3 to cpu 3 Nov 26 12:53:49 ccsw1 kernel: igb1: Bound queue 4 to cpu 4 Nov 26 12:53:49 ccsw1 kernel: igb1: Bound queue 5 to cpu 5 Nov 26 12:53:49 ccsw1 kernel: igb1: Bound queue 6 to cpu 6 Nov 26 12:53:49 ccsw1 kernel: igb1: Bound queue 7 to cpu 7 Nov 26 12:53:49 ccsw1 kernel: pcib4: at device 3.0 on pci2 Nov 26 12:53:49 ccsw1 kernel: pci6: on pcib4 Nov 26 12:53:49 ccsw1 kernel: igb2: port 0x2020-0x203f mem 0xb1a20000-0xb1a3ffff,0xb1ac4000-0xb1ac7fff irq 16 at device 0.0 on pci6 Nov 26 12:53:49 ccsw1 kernel: igb2: Using MSIX interrupts with 9 vectors Nov 26 12:53:49 ccsw1 kernel: igb2: Ethernet address: 00:1e:67:3a:d5:42 Nov 26 12:53:49 ccsw1 kernel: igb2: Bound queue 0 to cpu 0 Nov 26 12:53:49 ccsw1 kernel: igb2: Bound queue 1 to cpu 1 Nov 26 12:53:49 ccsw1 kernel: igb2: Bound queue 2 to cpu 2 Nov 26 12:53:49 ccsw1 kernel: igb2: Bound queue 3 to cpu 3 Nov 26 12:53:49 ccsw1 kernel: igb2: Bound queue 4 to cpu 4 Nov 26 12:53:49 ccsw1 kernel: igb2: Bound queue 5 to cpu 5 Nov 26 12:53:49 ccsw1 kernel: igb2: Bound queue 6 to cpu 6 Nov 26 12:53:49 ccsw1 kernel: igb2: Bound queue 7 to cpu 7 Nov 26 12:53:49 ccsw1 kernel: igb3: port 0x2000-0x201f mem 0xb1a00000-0xb1a1ffff,0xb1ac0000-0xb1ac3fff irq 19 at device 0.1 on pci6 Nov 26 12:53:49 ccsw1 kernel: igb3: Using MSIX interrupts with 9 vectors Nov 26 12:53:49 ccsw1 kernel: igb3: Ethernet address: 00:1e:67:3a:d5:43 Nov 26 12:53:49 ccsw1 kernel: igb3: Bound queue 0 to cpu 0 Nov 26 12:53:49 ccsw1 kernel: igb3: Bound queue 1 to cpu 1 Nov 26 12:53:49 ccsw1 kernel: igb3: Bound queue 2 to cpu 2 Nov 26 12:53:49 ccsw1 kernel: igb3: Bound queue 3 to cpu 3 Nov 26 12:53:49 ccsw1 kernel: igb3: Bound queue 4 to cpu 4 Nov 26 12:53:49 ccsw1 kernel: igb3: Bound queue 5 to cpu 5 Nov 26 12:53:49 ccsw1 kernel: igb3: Bound queue 6 to cpu 6 Nov 26 12:53:49 ccsw1 kernel: igb3: Bound queue 7 to cpu 7 Nov 26 12:53:49 ccsw1 kernel: pcib5: at device 4.0 on pci2 Nov 26 12:53:49 ccsw1 kernel: pci9: on pcib5 Nov 26 12:53:49 ccsw1 kernel: pcib6: at device 5.0 on pci2 Nov 26 12:53:49 ccsw1 kernel: pci10: on pcib6 Nov 26 12:53:49 ccsw1 kernel: pci0: at device 8.0 (no driver attached) Nov 26 12:53:49 ccsw1 kernel: pci0: at device 8.1 (no driver attached) Nov 26 12:53:49 ccsw1 kernel: pci0: at device 8.2 (no driver attached) Nov 26 12:53:49 ccsw1 kernel: pci0: at device 8.3 (no driver a ttached) Nov 26 12:53:49 ccsw1 kernel: pci0: at device 16.0 (no driver attached) Nov 26 12:53:49 ccsw1 kernel: pci0: at device 16.1 (no driver attached) Nov 26 12:53:49 ccsw1 kernel: ehci0: mem 0xb1c02000-0xb1c023ff irq 21 at device 26.0 on pci0 Nov 26 12:53:49 ccsw1 kernel: usbus0: EHCI version 1.0 Nov 26 12:53:49 ccsw1 kernel: usbus0 on ehci0 Nov 26 12:53:49 ccsw1 kernel: pcib7: irq 16 at device 28.0 on pci0 Nov 26 12:53:49 ccsw1 kernel: pci11: on pcib7 Nov 26 12:53:49 ccsw1 kernel: pcib8: irq 16 at device 28.4 on pci0 Nov 26 12:53:49 ccsw1 kernel: pci12: on pcib8 Nov 26 12:53:49 ccsw1 kernel: em0: port 0x1000-0x101f mem 0xb1900000-0xb191ffff,0xb1920000-0xb1923fff irq 16 at device 0.0 on pci12 Nov 26 12:53:49 ccsw1 kernel: em0: Using MSIX interrupts with 3 vectors Nov 26 12:53:49 ccsw1 kernel: em0: Ethernet address: 00:1e:67:3a:d5:44 Nov 26 12:53:49 ccsw1 kernel: pcib9: irq 18 at device 28.6 on pci0 Nov 26 12:53:49 ccsw1 kernel: pci13: on pcib9 Nov 26 12:53:49 ccsw1 kernel: vgapci0: mem 0xb0000000-0xb0ffffff,0xb1800000-0xb1803fff,0xb1000000-0xb17fffff irq 17 at device 0.0 on pci13 Nov 26 12:53:49 ccsw1 kernel: ehci1: mem 0xb1c01000-0xb1c013ff irq 23 at device 29.0 on pci0 Nov 26 12:53:49 ccsw1 kernel: usbus1: EHCI version 1.0 Nov 26 12:53:49 ccsw1 kernel: usbus1 on ehci1 Nov 26 12:53:49 ccsw1 kernel: pcib10: at device 30.0 on pci0 Nov 26 12:53:49 ccsw1 kernel: pci14: on pcib10 Nov 26 12:53:49 ccsw1 kernel: isab0: at device 31.0 on pci0 Nov 26 12:53:49 ccsw1 kernel: isa0: on isab0 Nov 26 12:53:49 ccsw1 kernel: ahci0: port 0x4048-0x404f,0x4054-0x4057,0x4040-0x4047,0x4050-0x4053,0x4020-0x403f mem 0xb1c00000-0xb1c007ff irq 18 at device 31.2 on pci0 Nov 26 12:53:49 ccsw1 kernel: ahci0: AHCI v1.30 with 6 3Gbps ports, Port Multiplier not supported Nov 26 12:53:49 ccsw1 kernel: ahcich0: at channel 0 on ahci0 Nov 26 12:53:49 ccsw1 kernel: ahcich1: at channel 1 on ahci0 Nov 26 12:53:49 ccsw1 kernel: ahcich2: at channel 2 on ahci0 Nov 26 12:53:49 ccsw1 kernel: ahcich3: at channel 3 on ahci0 Nov 26 12:53:49 ccsw1 kernel: ahcich4: at channel 4 on ahci0 Nov 26 12:53:49 ccsw1 kernel: ahcich5: at channel 5 on ahci0 Nov 26 12:53:49 ccsw1 kernel: pci0: at device 31.3 (no driver attached) Nov 26 12:53:49 ccsw1 kernel: acpi_button0: on acpi0 Nov 26 12:53:49 ccsw1 kernel: uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 Nov 26 12:53:49 ccsw1 kernel: uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0 Nov 26 12:53:49 ccsw1 kernel: orm0: at iomem 0xc0000-0xc7fff on isa0 Nov 26 12:53:49 ccsw1 kernel: sc0: at flags 0x100 on isa0 Nov 26 12:53:49 ccsw1 kernel: sc0: VGA <16 virtual consoles, flags=0x300> Nov 26 12:53:49 ccsw1 kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Nov 26 12:53:49 ccsw1 kernel: ppc0: cannot reserve I/O port range Nov 26 12:53:49 ccsw1 kernel: ctl: CAM Target Layer loaded Nov 26 12:53:49 ccsw1 kernel: est0: on cpu0 Nov 26 12:53:49 ccsw1 kernel: p4tcc0: on cpu0 Nov 26 12:53:49 ccsw1 kernel: est1: on cpu1 Nov 26 12:53:49 ccsw1 kernel: p4tcc1: on cpu1 Nov 26 12:53:49 ccsw1 kernel: est2: on cpu2 Nov 26 12:53:49 ccsw1 kernel: p4tcc2: on cpu2 Nov 26 12:53:49 ccsw1 kernel: est3: on cpu3 Nov 26 12:53:49 ccsw1 kernel: p4tcc3: on cpu3 Nov 26 12:53:49 ccsw1 kernel: est4: on cpu4 Nov 26 12:53:49 ccsw1 kernel: p4tcc4: on cpu4 Nov 26 12:53:49 ccsw1 kernel: est5: on cpu5 Nov 26 12:53:49 ccsw1 kernel: p4tcc5: on cpu5 Nov 26 12:53:49 ccsw1 kernel: est6: on cpu6 Nov 26 12:53:49 ccsw1 kernel: p4tcc6: on cpu6 Nov 26 12:53:49 ccsw1 kernel: est7: on cpu7 Nov 26 12:53:49 ccsw1 kernel: p4tcc7: on cpu7 Nov 26 12:53:49 ccsw1 kernel: ZFS filesystem version 5 Nov 26 12:53:49 ccsw1 kernel: ZFS storage pool version 28 Nov 26 12:53:49 ccsw1 kernel: Timecounters tick every 1.000 msec Nov 26 12:53:49 ccsw1 kernel: usbus0: 480Mbps High Speed USB v2.0 Nov 26 12:53:49 ccsw1 kernel: usbus1: 480Mbps High Speed USB v2.0 Nov 26 12:53:49 ccsw1 kernel: ugen0.1: at usbus0 Nov 26 12:53:49 ccsw1 kernel: uhub0: on usbus0 Nov 26 12:53:49 ccsw1 kernel: ugen1.1: at usbus1 Nov 26 12:53:49 ccsw1 kernel: uhub1: on usbus1 Nov 26 12:53:49 ccsw1 kernel: uhub0: 2 ports with 2 removable, self powered Nov 26 12:53:49 ccsw1 kernel: uhub1: 2 ports with 2 removable, self powered Nov 26 12:53:49 ccsw1 kernel: ugen0.2: at usbus0 Nov 26 12:53:49 ccsw1 kernel: uhub2: on usbus0 Nov 26 12:53:49 ccsw1 kernel: ugen1.2: at usbus1 Nov 26 12:53:49 ccsw1 kernel: uhub3: on usbus1 Nov 26 12:53:49 ccsw1 kernel: uhub2: 6 ports with 6 removable, self powered Nov 26 12:53:49 ccsw1 kernel: uhub3: 8 ports with 8 removable, self powered Nov 26 12:53:49 ccsw1 kernel: ugen0.3: at usbus0 Nov 26 12:53:49 ccsw1 kernel: ukbd0: on usbus0 Nov 26 12:53:49 ccsw1 kernel: kbd0 at ukbd0 Nov 26 12:53:49 ccsw1 kernel: uhid0: <12032003> on usbus0 Nov 26 12:53:49 ccsw1 kernel: ugen1.3: at usbus1 Nov 26 12:53:49 ccsw1 kernel: ukbd1: on usbus1 Nov 26 12:53:49 ccsw1 kernel: kbd2 at ukbd1 Nov 26 12:53:49 ccsw1 kernel: ums0: on usbus1 Nov 26 12:53:49 ccsw1 kernel: ums0: 3 buttons and [Z] coordinates ID=0 Nov 26 12:53:49 ccsw1 kernel: ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 Nov 26 12:53:49 ccsw1 kernel: ada0: ATA-8 SATA 3.x device Nov 26 12:53:49 ccsw1 kernel: ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) Nov 26 12:53:49 ccsw1 kernel: ada0: Command Queueing enabled Nov 26 12:53:49 ccsw1 kernel: ada0: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C) Nov 26 12:53:49 ccsw1 kernel: ada0: Previously was known as ad4 Nov 26 12:53:49 ccsw1 kernel: ada1 at ahcich1 bus 0 scbus1 target 0 lun 0 Nov 26 12:53:49 ccsw1 kernel: ada1: ATA-8 SATA 3.x device Nov 26 12:53:49 ccsw1 kernel: ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) Nov 26 12:53:49 ccsw1 kernel: ada1: Command Queueing enabled Nov 26 12:53:49 ccsw1 kernel: ada1: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C) Nov 26 12:53:49 ccsw1 kernel: ada1: Previously was known as ad6 Nov 26 12:53:49 ccsw1 kernel: lapic1: Forcing LINT1 to edge trigger Nov 26 12:53:49 ccsw1 kernel: SMP: AP CPU #1 Launched! Nov 26 12:53:49 ccsw1 kernel: lapic2: Forcing LINT1 to edge trigger Nov 26 12:53:49 ccsw1 kernel: SMP: AP CPU #2 Launched! Nov 26 12:53:49 ccsw1 kernel: lapic7: Forcing LINT1 to edge trigger Nov 26 12:53:49 ccsw1 kernel: SMP: AP CPU #7 Launched! Nov 26 12:53:49 ccsw1 kernel: lapic5: Forcing LINT1 to edge trigger Nov 26 12:53:49 ccsw1 kernel: SMP: AP CPU #5 Launched! Nov 26 12:53:49 ccsw1 kernel: lapic6: Forcing LINT1 to edge trigger Nov 26 12:53:49 ccsw1 kernel: SMP: AP CPU #6 Launched! Nov 26 12:53:49 ccsw1 kernel: lapic3: Forcing LINT1 to edge trigger Nov 26 12:53:49 ccsw1 kernel: SMP: AP CPU #3 Launched! Nov 26 12:53:49 ccsw1 kernel: lapic4: Forcing LINT1 to edge trigger Nov 26 12:53:49 ccsw1 kernel: SMP: AP CPU #4 Launched! Nov 26 12:53:49 ccsw1 kernel: Timecounter "TSC-low" frequency 9895914 Hz quality 1000 Nov 26 12:58:01 ccsw1 kernel: Trying to mount root from zfs:pool/r1 []... Nov 26 12:58:01 ccsw1 root: /etc/rc: WARNING: Dump device does not exist. Savecore not run. Nov 26 12:58:01 ccsw1 ntpd[1511]: ntpd 4.2.4p5-a (1) Nov 26 12:58:01 ccsw1 ntpd[1512]: bind() fd 22, family AF_INET6, port 123, scope 2, addr fe80::21e:67ff:fe3a:d541, mcast=0 flags=0x11 fails: Can't assign requested address Nov 26 12:58:01 ccsw1 ntpd[1512]: unable to create socket on igb1 (2) for fe80::21e:67ff:fe3a:d541#123 Nov 26 12:58:12 ccsw1 ntpd[1512]: bind() fd 27, family AF_INET6, port 123, scope 2, addr fe80::21e:67ff:fe3a:d541, mcast=0 flags=0x11 fails: Can't assign requested address Nov 26 12:58:12 ccsw1 ntpd[1512]: unable to create socket on igb1 (7) for fe80::21e:67ff:fe3a:d541#123 Nov 26 12:58:18 ccsw1 ntpd[1512]: time reset +0.261195 s Nov 26 12:58:23 ccsw1 sshd[1575]: error: PAM: authentication error for root from 192.168.221.84 Nov 26 13:03:12 ccsw1 ntpd[1512]: bind() fd 27, family AF_INET6, port 123, scope 2, addr fe80::21e:67ff:fe3a:d541, mcast=0 flags=0x11 fails: Can't assign requested address ntpd keeps chattering about the link-local ipv6... but no other messages occur in the log during the exercise. From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 28 14:20:30 2012 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 937E3390 for ; Wed, 28 Nov 2012 14:20:30 +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 B0D1B8FC08 for ; Wed, 28 Nov 2012 14:20:29 +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 QAA27208 for ; Wed, 28 Nov 2012 16:20:28 +0200 (EET) (envelope-from avg@FreeBSD.org) Message-ID: <50B61DAC.7050102@FreeBSD.org> Date: Wed, 28 Nov 2012 16:20:28 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: FreeBSD Hackers Subject: lib for working with graphs X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Nov 2012 14:20:30 -0000 Does anyone know a light-weight BSD-licensed (or analogous) library / piece of code for doing useful things with graphs? Thank you. -- Andriy Gapon From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 28 14:31:16 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 43D2C5A8; Wed, 28 Nov 2012 14:31:16 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (m209-73.dsl.rawbw.com [198.144.209.73]) by mx1.freebsd.org (Postfix) with ESMTP id 14E898FC0C; Wed, 28 Nov 2012 14:31:15 +0000 (UTC) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.14.5/8.14.5) with ESMTP id qASEVFum038177; Wed, 28 Nov 2012 06:31:15 -0800 (PST) (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.14.5/8.14.5/Submit) id qASEVFDp038176; Wed, 28 Nov 2012 06:31:15 -0800 (PST) (envelope-from david) Date: Wed, 28 Nov 2012 06:31:15 -0800 From: David Wolfskill To: Andriy Gapon Subject: Re: lib for working with graphs Message-ID: <20121128143115.GJ2617@albert.catwhisker.org> References: <50B61DAC.7050102@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="8Ll2WeG2L2s3+nMg" Content-Disposition: inline In-Reply-To: <50B61DAC.7050102@FreeBSD.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: FreeBSD Hackers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Nov 2012 14:31:16 -0000 --8Ll2WeG2L2s3+nMg Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 28, 2012 at 04:20:28PM +0200, Andriy Gapon wrote: >=20 > Does anyone know a light-weight BSD-licensed (or analogous) library / pie= ce of > code for doing useful things with graphs? > Thank you. > .... Errr.... "graphs" is fairly ambiguous, and "things with graphs" covers a very wide range of activities. ports/math/R may be useful for this -- I use it to generate graphs (and perform statistical analyses). ports/graphics/plotmtv is possibly of some interest, as well, as it allows a certain level of interactivity (though the code hasn't been updated in quite some time -- but it still works). If neither of those suits your intent, perhaps you could expand a bit on what that intent is? Peace, david --=20 David H. Wolfskill david@catwhisker.org Taliban: Evil men with guns afraid of truth from a 14-year old girl. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --8Ll2WeG2L2s3+nMg Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlC2IDIACgkQmprOCmdXAD0L3QCfdUD/OeGIqhA3JmPm+plMXMqU IwkAnRZTEt5sZ7EMV3bNxFTM4ClCJ/fB =DoK9 -----END PGP SIGNATURE----- --8Ll2WeG2L2s3+nMg-- From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 28 14:37:54 2012 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5C3EF805 for ; Wed, 28 Nov 2012 14:37:54 +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 A4C2F8FC16 for ; Wed, 28 Nov 2012 14:37:53 +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 QAA27343; Wed, 28 Nov 2012 16:37:46 +0200 (EET) (envelope-from avg@FreeBSD.org) Message-ID: <50B621BA.1080407@FreeBSD.org> Date: Wed, 28 Nov 2012 16:37:46 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: David Wolfskill Subject: Re: lib for working with graphs References: <50B61DAC.7050102@FreeBSD.org> <20121128143115.GJ2617@albert.catwhisker.org> In-Reply-To: <20121128143115.GJ2617@albert.catwhisker.org> X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: FreeBSD Hackers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Nov 2012 14:37:54 -0000 on 28/11/2012 16:31 David Wolfskill said the following: > On Wed, Nov 28, 2012 at 04:20:28PM +0200, Andriy Gapon wrote: >> >> Does anyone know a light-weight BSD-licensed (or analogous) library / piece of >> code for doing useful things with graphs? >> Thank you. >> .... > > Errr.... "graphs" is fairly ambiguous, and "things with graphs" covers a > very wide range of activities. Graphs as in vertices, edges, etc :) And things like graph basics: BFS, DFS, connected components, topological sort, etc > ports/math/R may be useful for this -- I use it to generate graphs (and > perform statistical analyses). > > ports/graphics/plotmtv is possibly of some interest, as well, as it > allows a certain level of interactivity (though the code hasn't been > updated in quite some time -- but it still works). > > If neither of those suits your intent, perhaps you could expand a bit on > what that intent is? And, big oops sorry, forgot one very important detail - it has to be C. -- Andriy Gapon From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 28 15:02:42 2012 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 22AF6DB3; Wed, 28 Nov 2012 15:02:42 +0000 (UTC) (envelope-from jonathan@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 06B8A8FC08; Wed, 28 Nov 2012 15:02:42 +0000 (UTC) Received: from [::8097:d111:100:0] (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id qASF2e77044929; Wed, 28 Nov 2012 15:02:41 GMT (envelope-from jonathan@FreeBSD.org) Date: Wed, 28 Nov 2012 15:02:40 +0000 From: Jonathan Anderson To: Andriy Gapon Message-ID: In-Reply-To: <50B621BA.1080407@FreeBSD.org> References: <50B61DAC.7050102@FreeBSD.org> <20121128143115.GJ2617@albert.catwhisker.org> <50B621BA.1080407@FreeBSD.org> Subject: Re: lib for working with graphs X-Mailer: sparrow 1.6.4 (build 1176) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: FreeBSD Hackers , David Wolfskill X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Nov 2012 15:02:42 -0000 On Wednesday, 28 November 2012 at 14:37, Andriy Gapon wrote: > Graphs as in vertices, edges, etc :) > And things like graph basics: BFS, DFS, connected components, topological sort, etc > I've used igraph in my research: http://igraph.sourceforge.net/. It's very full-featured, with attention to efficiency and sensible choices for (at least some) algorithms, but it is GPL'ed rather than BSD-licenced. > And, big oops sorry, forgot one very important detail - it has to be C. Does it have to *be* C, or does it have to be *interoperable with* C? For instance, igraph has a core C library to do the heavy lifting, but I'd never want to use it directly when exploring data sets because the Python wrapper API is so very convenient (and I can pop the resulting data into matplotlib). Jon -- Jonathan Anderson jonathan@FreeBSD.org (mailto:jonathan@FreeBSD.org) From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 28 15:17:17 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 877685B5; Wed, 28 Nov 2012 15:17:17 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from email2.allantgroup.com (email2.emsphone.com [199.67.51.116]) by mx1.freebsd.org (Postfix) with ESMTP id 262BA8FC19; Wed, 28 Nov 2012 15:17:15 +0000 (UTC) Received: from dan.emsphone.com (dan.emsphone.com [172.17.17.101]) by email2.allantgroup.com (8.14.5/8.14.5) with ESMTP id qASF9xvC066822 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 28 Nov 2012 09:09:59 -0600 (CST) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (smmsp@localhost [127.0.0.1]) by dan.emsphone.com (8.14.5/8.14.5) with ESMTP id qASF9xr1036586 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 28 Nov 2012 09:09:59 -0600 (CST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.14.5/8.14.5/Submit) id qASF9xOp036585; Wed, 28 Nov 2012 09:09:59 -0600 (CST) (envelope-from dan) Date: Wed, 28 Nov 2012 09:09:59 -0600 From: Dan Nelson To: Andriy Gapon Subject: Re: lib for working with graphs Message-ID: <20121128150959.GB91597@dan.emsphone.com> References: <50B61DAC.7050102@FreeBSD.org> <20121128143115.GJ2617@albert.catwhisker.org> <50B621BA.1080407@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <50B621BA.1080407@FreeBSD.org> X-OS: FreeBSD 8.3-STABLE User-Agent: Mutt/1.5.21 (2010-09-15) X-Virus-Scanned: clamav-milter 0.97.6 at email2.allantgroup.com X-Virus-Status: Clean X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (email2.allantgroup.com [172.17.19.78]); Wed, 28 Nov 2012 09:10:00 -0600 (CST) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on email2.allantgroup.com X-Scanned-By: MIMEDefang 2.73 Cc: FreeBSD Hackers , David Wolfskill X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Nov 2012 15:17:17 -0000 In the last episode (Nov 28), Andriy Gapon said: > on 28/11/2012 16:31 David Wolfskill said the following: > > On Wed, Nov 28, 2012 at 04:20:28PM +0200, Andriy Gapon wrote: > >> > >> Does anyone know a light-weight BSD-licensed (or analogous) library / > >> piece of code for doing useful things with graphs? Thank you. > >> .... > > > > Errr.... "graphs" is fairly ambiguous, and "things with graphs" covers a > > very wide range of activities. > > Graphs as in vertices, edges, etc :) And things like graph basics: BFS, > DFS, connected components, topological sort, etc Graphviz would be the most popular package for stuff like this, I think, and it includes a C API. It's licensed under the Eclipse Public License. http://www.graphviz.org/ http://www.graphviz.org/Gallery.php http://www.graphviz.org/doc/libguide/libguide.pdf -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 28 16:36:57 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 54BDD1AF; Wed, 28 Nov 2012 16:36:57 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-vc0-f182.google.com (mail-vc0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id E0CDF8FC0C; Wed, 28 Nov 2012 16:36:56 +0000 (UTC) Received: by mail-vc0-f182.google.com with SMTP id fo13so18661042vcb.13 for ; Wed, 28 Nov 2012 08:36:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=xk/7l41zzmQXxMyrcxblYKOdpsytkP/2dDx7lwM4A50=; b=S7RhL/TJip/VB4UooN6TGkOzcWjcqQcHNqxPJriPcvvfpJdlFTwgUaJtZanM8B1/kC ZB6zGelhdvd6aPAwZ0J2zpmR4lLFXitTCRpEJGXEJDC2jQDNK7KXULzUBpQb1ilSts/y 4iGGTdgpT6DreOJpLIabtmnCy3zEPLpVJC4GcZ6WgGAckeD/Yt+e/IjHos5AQIeVI8UI hzM6v88brdnrUA1q/okFBTNFjxNv1yRbflbd/GfC2YmcQwi9JAE9pfaynKi72oULSwBi IzOpDFCvIR7SYVhQJ8ThsxhMVRT7BR8Q0b0ApV9/9jnpoYXtyklHwibnfcKn0oUOD+jR nLNA== MIME-Version: 1.0 Received: by 10.52.36.40 with SMTP id n8mr24943612vdj.52.1354120616138; Wed, 28 Nov 2012 08:36:56 -0800 (PST) Received: by 10.58.218.35 with HTTP; Wed, 28 Nov 2012 08:36:55 -0800 (PST) In-Reply-To: <50B621BA.1080407@FreeBSD.org> References: <50B61DAC.7050102@FreeBSD.org> <20121128143115.GJ2617@albert.catwhisker.org> <50B621BA.1080407@FreeBSD.org> Date: Wed, 28 Nov 2012 08:36:55 -0800 Message-ID: Subject: Re: lib for working with graphs From: Mehmet Erol Sanliturk To: Andriy Gapon Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Hackers , David Wolfskill X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Nov 2012 16:36:57 -0000 On Wed, Nov 28, 2012 at 6:37 AM, Andriy Gapon wrote: > on 28/11/2012 16:31 David Wolfskill said the following: > > On Wed, Nov 28, 2012 at 04:20:28PM +0200, Andriy Gapon wrote: > >> > >> Does anyone know a light-weight BSD-licensed (or analogous) library / > piece of > >> code for doing useful things with graphs? > >> Thank you. > >> .... > > > > Errr.... "graphs" is fairly ambiguous, and "things with graphs" covers a > > very wide range of activities. > > Graphs as in vertices, edges, etc :) > And things like graph basics: BFS, DFS, connected components, topological > sort, etc > > > ports/math/R may be useful for this -- I use it to generate graphs (and > > perform statistical analyses). > > > > ports/graphics/plotmtv is possibly of some interest, as well, as it > > allows a certain level of interactivity (though the code hasn't been > > updated in quite some time -- but it still works). > > > > If neither of those suits your intent, perhaps you could expand a bit on > > what that intent is? > > And, big oops sorry, forgot one very important detail - it has to be C. > > -- > Andriy Gapon > http://en.wikipedia.org/wiki/JUNG http://en.wikipedia.org/wiki/Xfig http://en.wikipedia.org/wiki/SVG-edit http://en.wikipedia.org/wiki/Category:Graph_drawing_software http://en.wikipedia.org/wiki/Comparison_of_vector_graphics_editors http://en.wikipedia.org/wiki/Category:Free_diagramming_software Thank you very much . Mehmet Erol Sanliturk From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 28 17:32:28 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 98731733 for ; Wed, 28 Nov 2012 17:32:28 +0000 (UTC) (envelope-from otacilio.neto@bsd.com.br) Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 306158FC0C for ; Wed, 28 Nov 2012 17:32:27 +0000 (UTC) Received: by mail-vb0-f54.google.com with SMTP id l1so7065187vba.13 for ; Wed, 28 Nov 2012 09:32:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsd.com.br; s=capeta; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=63qwDmc9hzETMyr0P8OS08pfmipy8dHoHag8OX6LhY8=; b=Mac3fKM4LgzMOgljzKNQJysoKOSQejUgF2wjjWjFvobXsf7rJzzDiwesEzApp7jfPY W0iQA6BS8Rtpnv2ctNciaK2hOiiIeZdooRaoXrxn4e/MVKTf4Vtu4sjflbDgDjhaSLCs CJvVc1tSi8eGn1abaVpkSU4S975WdqrplS2go= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:x-enigmail-version:content-type :content-transfer-encoding:x-gm-message-state; bh=63qwDmc9hzETMyr0P8OS08pfmipy8dHoHag8OX6LhY8=; b=MZFz+2WrLS6Z16axyoRLLkNqY3zG4KIz9zU2XYcTl5VPHYMAp0/T2XdG/6wBOafvrM JLs+AyWwaxd+8rh1ICImtrNWh+2mnlEJZW86zEbRGF5/8iN7Da+OjHtgDWQ0IZuLfxgn 6VoGGVimnwFIS6UtmFXNHErcsvxX2SVbS4IKKVKb6qCWMZJ3TXqtvphWUzThd0X8jIcq g7gdS/N5Bisj8XJBu8znOeHRc3TD1SCL4g+F8khYfshjlYofzz4MrCt3S3i7Qn+EoKs6 iPtW1ppLFA6IedhtVFy5l537l/litLDzd2gkf2AuPPtL86fktSQsMwAmk5w/CuysVu8A H2lA== Received: by 10.220.153.201 with SMTP id l9mr16234375vcw.33.1354123947264; Wed, 28 Nov 2012 09:32:27 -0800 (PST) Received: from [192.168.1.101] ([150.165.130.201]) by mx.google.com with ESMTPS id cd19sm4882552vdb.20.2012.11.28.09.32.25 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 28 Nov 2012 09:32:26 -0800 (PST) Message-ID: <50B64A9C.6000004@bsd.com.br> Date: Wed, 28 Nov 2012 14:32:12 -0300 From: =?ISO-8859-1?Q?Otac=EDlio?= User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:15.0) Gecko/20120919 Thunderbird/15.0.1 MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Re: lib for working with graphs References: <50B61DAC.7050102@FreeBSD.org> <20121128143115.GJ2617@albert.catwhisker.org> <50B621BA.1080407@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.4.3 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Gm-Message-State: ALoCoQnz6kDnVjpKeEOeFLIo30B42JM3zLw7ULOeE5DmJ3UP58ZxNOkUzsm1EiZk78FSMr5v/xQn X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Nov 2012 17:32:28 -0000 On 28/11/2012 13:36, Mehmet Erol Sanliturk wrote: > On Wed, Nov 28, 2012 at 6:37 AM, Andriy Gapon > wrote: > >> on 28/11/2012 16:31 David Wolfskill said the following: >>> On Wed, Nov 28, 2012 at 04:20:28PM +0200, Andriy Gapon wrote: >>>> >>>> Does anyone know a light-weight BSD-licensed (or analogous) >>>> library / >> piece of >>>> code for doing useful things with graphs? Thank you. .... >>> >>> Errr.... "graphs" is fairly ambiguous, and "things with graphs" >>> covers a very wide range of activities. >> >> Graphs as in vertices, edges, etc :) And things like graph >> basics: BFS, DFS, connected components, topological sort, etc >> >>> ports/math/R may be useful for this -- I use it to generate >>> graphs (and perform statistical analyses). >>> >>> ports/graphics/plotmtv is possibly of some interest, as well, >>> as it allows a certain level of interactivity (though the code >>> hasn't been updated in quite some time -- but it still works). >>> >>> If neither of those suits your intent, perhaps you could expand >>> a bit on what that intent is? >> >> And, big oops sorry, forgot one very important detail - it has to >> be C. >> >> -- Andriy Gapon >> > > > > > http://en.wikipedia.org/wiki/JUNG > http://en.wikipedia.org/wiki/Xfig > http://en.wikipedia.org/wiki/SVG-edit > > > http://en.wikipedia.org/wiki/Category:Graph_drawing_software > http://en.wikipedia.org/wiki/Comparison_of_vector_graphics_editors > http://en.wikipedia.org/wiki/Category:Free_diagramming_software > > > Thank you very much . > > Mehmet Erol Sanliturk Err, someone knows a library that implements the hmetis algorithm and run on FreeBSD? From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 29 09:22:12 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E5609C3C for ; Thu, 29 Nov 2012 09:22:12 +0000 (UTC) (envelope-from nkoch@demig.de) Received: from h949823.serverkompetenz.net (demig.de [85.214.63.38]) by mx1.freebsd.org (Postfix) with ESMTP id 2A4BF8FC17 for ; Thu, 29 Nov 2012 09:22:11 +0000 (UTC) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=demig.de; b=j+hRXzYnsnisNm3t6fVE1PV+qQ42rjSyhdPst9t+QgW4cbsI8V4u6rTO4nbB6L4t3lUD8W40WnY+Hx5tIQZjhH7uCyjo05NRpBpqsJ+aNMgfpGF4aO5JmBcLEF9RZAcL; h=Received:Received:Received:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:X-Enigmail-Version:Content-Type:Content-Transfer-Encoding:X-Scanned-By; Received: (qmail 25691 invoked from network); 29 Nov 2012 10:15:28 +0100 Received: from ip-78-94-60-110.unitymediagroup.de (HELO firewall.demig.intra) (78.94.60.110) by demig.de with (DHE-RSA-AES256-SHA encrypted) SMTP; 29 Nov 2012 10:15:28 +0100 Received: from entw-pr.demig.intra (srv-pr-1 [192.168.148.236]) by firewall.demig.intra (8.14.4/8.14.4) with ESMTP id qAT9F0Sn084291 for ; Thu, 29 Nov 2012 10:15:00 +0100 (CET) (envelope-from nkoch@demig.de) Received: from [192.168.148.83] ([192.168.148.83]) by entw-pr.demig.intra (8.14.2/8.13.4) with ESMTP id qAT9F04T089695 for ; Thu, 29 Nov 2012 10:15:00 +0100 (CET) (envelope-from nkoch@demig.de) Message-ID: <50B72794.6050609@demig.de> Date: Thu, 29 Nov 2012 10:15:00 +0100 From: Norbert Koch User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.org Subject: uart device numbering X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.73 on 192.168.148.235 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Nov 2012 09:22:13 -0000 Hello, I have an embedded system which is equipped with uart hardware controlled by the puc driver. There are no standard uarts at 0x3f8/0x2f8. When I boot FreeBSD 8.2 I see my uarts as devices 0..3. FreeBSD 9 shows them as 2..5. The kernel configurations are more or less identical and disabling uarts 0 & 1 through /boot/device.hints seems not to change anything. Is this behaviour expected/wanted? Thank you, Norbert Koch From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 29 12:05:52 2012 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0342E808; Thu, 29 Nov 2012 12:05:52 +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 E4FBE8FC13; Thu, 29 Nov 2012 12:05:50 +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 OAA10285; Thu, 29 Nov 2012 14:05:48 +0200 (EET) (envelope-from avg@FreeBSD.org) Message-ID: <50B74F9C.40106@FreeBSD.org> Date: Thu, 29 Nov 2012 14:05:48 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: attilio@FreeBSD.org Subject: Re: LK_SHARED/LK_DOWNGRADE adjustments to lock.9 manual page References: <50A4E8C0.5030608@FreeBSD.org> <50A552C5.5060703@FreeBSD.org> <50A650C2.7060407@FreeBSD.org> In-Reply-To: <50A650C2.7060407@FreeBSD.org> X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@FreeBSD.org, freebsd-current@FreeBSD.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Nov 2012 12:05:52 -0000 on 16/11/2012 16:42 Andriy Gapon said the following: > on 15/11/2012 23:44 Attilio Rao said the following: >> Do you think you can test this patch?: >> http://www.freebsd.org/~attilio/lockmgr_forcerec.patch > > I will use this patch in my tree, but I think that it is effectively already quite > well tested by using INVARIANTS+WITNESS. > I've been using this patch in both debug and non-debug environments and I have not run into any issues. Please commit when you get a chance. Thank you. -- Andriy Gapon From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 29 12:53:45 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AD9EFA39 for ; Thu, 29 Nov 2012 12:53:45 +0000 (UTC) (envelope-from freebsd-hackers@m.gmane.org) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) by mx1.freebsd.org (Postfix) with ESMTP id 566838FC08 for ; Thu, 29 Nov 2012 12:53:44 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Te3cF-0000Qs-8X for freebsd-hackers@freebsd.org; Thu, 29 Nov 2012 13:53:19 +0100 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, 29 Nov 2012 13:53:19 +0100 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 29 Nov 2012 13:53:19 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-hackers@freebsd.org From: Ivan Voras Subject: Re: postfix mail server infected ? Date: Thu, 29 Nov 2012 13:52:44 +0100 Lines: 30 Message-ID: References: <50B26326.3070008@mail.ru> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig613F3EB7D83F2AFFCEB88340" X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:14.0) Gecko/20120812 Thunderbird/14.0 In-Reply-To: <50B26326.3070008@mail.ru> X-Enigmail-Version: 1.4.3 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Nov 2012 12:53:45 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig613F3EB7D83F2AFFCEB88340 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 25/11/2012 19:27, trafdev wrote: > Hi. Can you please point me to some discussions and solutions related t= o > this problem? Thanks. Since this is a developers-mostly mailing list, I think you could get a better response at the freebsd-security@freebsd.org list. --------------enig613F3EB7D83F2AFFCEB88340 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.19 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlC3WpwACgkQ/QjVBj3/HSzQmQCfR3xZ+CJYXj4/kfyh8z69SQVo l08Anj7JHW/GhhDAgcIXTJNa6qRZwsYq =Tv/r -----END PGP SIGNATURE----- --------------enig613F3EB7D83F2AFFCEB88340-- From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 29 15:10:15 2012 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EC8924FA; Thu, 29 Nov 2012 15:10:15 +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 0CA878FC13; Thu, 29 Nov 2012 15:10:14 +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 RAA11964; Thu, 29 Nov 2012 17:10:13 +0200 (EET) (envelope-from avg@FreeBSD.org) Message-ID: <50B77AD5.7030703@FreeBSD.org> Date: Thu, 29 Nov 2012 17:10:13 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Jonathan Anderson Subject: Re: lib for working with graphs References: <50B61DAC.7050102@FreeBSD.org> <20121128143115.GJ2617@albert.catwhisker.org> <50B621BA.1080407@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: FreeBSD Hackers , David Wolfskill X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Nov 2012 15:10:16 -0000 on 28/11/2012 17:02 Jonathan Anderson said the following: > On Wednesday, 28 November 2012 at 14:37, Andriy Gapon wrote: >> Graphs as in vertices, edges, etc :) And things like graph basics: BFS, DFS, >> connected components, topological sort, etc >> > > I've used igraph in my research: http://igraph.sourceforge.net/. It's very > full-featured, with attention to efficiency and sensible choices for (at least > some) algorithms, but it is GPL'ed rather than BSD-licenced. Yeah, a bummer for me. >> And, big oops sorry, forgot one very important detail - it has to be C. > > > > Does it have to *be* C, or does it have to be *interoperable with* C? For > instance, igraph has a core C library to do the heavy lifting, but I'd never > want to use it directly when exploring data sets because the Python wrapper API > is so very convenient (and I can pop the resulting data into matplotlib). It has to be C because I need to use it from C code in a "C runtime". -- Andriy Gapon From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 29 15:12:04 2012 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E32005F3 for ; Thu, 29 Nov 2012 15:12:04 +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 3629C8FC0C for ; Thu, 29 Nov 2012 15:12:03 +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 RAA11980; Thu, 29 Nov 2012 17:12:01 +0200 (EET) (envelope-from avg@FreeBSD.org) Message-ID: <50B77B41.7040008@FreeBSD.org> Date: Thu, 29 Nov 2012 17:12:01 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Mehmet Erol Sanliturk Subject: Re: lib for working with graphs References: <50B61DAC.7050102@FreeBSD.org> <20121128143115.GJ2617@albert.catwhisker.org> <50B621BA.1080407@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: FreeBSD Hackers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Nov 2012 15:12:05 -0000 on 28/11/2012 18:36 Mehmet Erol Sanliturk said the following: > > > On Wed, Nov 28, 2012 at 6:37 AM, Andriy Gapon > wrote: > > on 28/11/2012 16:31 David Wolfskill said the following: > > On Wed, Nov 28, 2012 at 04:20:28PM +0200, Andriy Gapon wrote: > >> > >> Does anyone know a light-weight BSD-licensed (or analogous) library / piece of > >> code for doing useful things with graphs? > >> Thank you. > >> .... > > > > Errr.... "graphs" is fairly ambiguous, and "things with graphs" covers a > > very wide range of activities. > > Graphs as in vertices, edges, etc :) > And things like graph basics: BFS, DFS, connected components, topological > sort, etc > > > ports/math/R may be useful for this -- I use it to generate graphs (and > > perform statistical analyses). > > > > ports/graphics/plotmtv is possibly of some interest, as well, as it > > allows a certain level of interactivity (though the code hasn't been > > updated in quite some time -- but it still works). > > > > If neither of those suits your intent, perhaps you could expand a bit on > > what that intent is? > > And, big oops sorry, forgot one very important detail - it has to be C. > > http://en.wikipedia.org/wiki/JUNG > http://en.wikipedia.org/wiki/Xfig > http://en.wikipedia.org/wiki/SVG-edit > > > http://en.wikipedia.org/wiki/Category:Graph_drawing_software > http://en.wikipedia.org/wiki/Comparison_of_vector_graphics_editors > http://en.wikipedia.org/wiki/Category:Free_diagramming_software > > > Thank you very much . Thank you, but all of these appear to be off-mark. They all are end-user oriented applications for drawing/editing graphs, etc. While I need a light-weight library for "embedding" graph analysis. -- Andriy Gapon From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 29 15:20:11 2012 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1A4FDCD1 for ; Thu, 29 Nov 2012 15:20:11 +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 64DA38FC12 for ; Thu, 29 Nov 2012 15:20:10 +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 RAA12062; Thu, 29 Nov 2012 17:20:07 +0200 (EET) (envelope-from avg@FreeBSD.org) Message-ID: <50B77D26.7050300@FreeBSD.org> Date: Thu, 29 Nov 2012 17:20:06 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Dan Nelson Subject: Re: lib for working with graphs References: <50B61DAC.7050102@FreeBSD.org> <20121128143115.GJ2617@albert.catwhisker.org> <50B621BA.1080407@FreeBSD.org> <20121128150959.GB91597@dan.emsphone.com> In-Reply-To: <20121128150959.GB91597@dan.emsphone.com> X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: FreeBSD Hackers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Nov 2012 15:20:11 -0000 on 28/11/2012 17:09 Dan Nelson said the following: > In the last episode (Nov 28), Andriy Gapon said: >> on 28/11/2012 16:31 David Wolfskill said the following: >>> On Wed, Nov 28, 2012 at 04:20:28PM +0200, Andriy Gapon wrote: >>>> >>>> Does anyone know a light-weight BSD-licensed (or analogous) library / >>>> piece of code for doing useful things with graphs? Thank you. >>>> .... >>> >>> Errr.... "graphs" is fairly ambiguous, and "things with graphs" covers a >>> very wide range of activities. >> >> Graphs as in vertices, edges, etc :) And things like graph basics: BFS, >> DFS, connected components, topological sort, etc > > Graphviz would be the most popular package for stuff like this, I think, and > it includes a C API. It's licensed under the Eclipse Public License. > > http://www.graphviz.org/ > http://www.graphviz.org/Gallery.php > http://www.graphviz.org/doc/libguide/libguide.pdf The library sounds interesting, but I need to evaluate the license and light-weight-ness of it. EPL is not as long as GPL, but is not as short as BSDL unfortunately. Thank you! -- Andriy Gapon From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 29 16:01:17 2012 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 83E8ED7A; Thu, 29 Nov 2012 16:01:17 +0000 (UTC) (envelope-from bakul@bitblocks.com) Received: from mail.bitblocks.com (ns1.bitblocks.com [173.228.5.8]) by mx1.freebsd.org (Postfix) with ESMTP id 5B51F8FC0C; Thu, 29 Nov 2012 16:01:17 +0000 (UTC) Received: from [192.168.125.13] (ipad.bitblocks.com [192.168.125.13]) by mail.bitblocks.com (Postfix) with ESMTP id D0C70B827; Thu, 29 Nov 2012 07:55:00 -0800 (PST) References: <50B61DAC.7050102@FreeBSD.org> <20121128143115.GJ2617@albert.catwhisker.org> <50B621BA.1080407@FreeBSD.org> <50B77B41.7040008@FreeBSD.org> In-Reply-To: <50B77B41.7040008@FreeBSD.org> Mime-Version: 1.0 (1.0) Content-Type: text/plain; charset=us-ascii Message-Id: Content-Transfer-Encoding: quoted-printable X-Mailer: iPad Mail (9B206) From: Bakul Shah Subject: Re: lib for working with graphs Date: Thu, 29 Nov 2012 07:55:00 -0800 To: Andriy Gapon Cc: FreeBSD Hackers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Nov 2012 16:01:17 -0000 On Nov 29, 2012, at 7:12 AM, Andriy Gapon wrote: > on 28/11/2012 18:36 Mehmet Erol Sanliturk said the following: >>=20 >>=20 >> On Wed, Nov 28, 2012 at 6:37 AM, Andriy Gapon > > wrote: >>=20 >> on 28/11/2012 16:31 David Wolfskill said the following: >>> On Wed, Nov 28, 2012 at 04:20:28PM +0200, Andriy Gapon wrote: >>>>=20 >>>> Does anyone know a light-weight BSD-licensed (or analogous) library / p= iece of >>>> code for doing useful things with graphs? >>>> Thank you. >>>> .... >>>=20 >>> Errr.... "graphs" is fairly ambiguous, and "things with graphs" covers a= >>> very wide range of activities. >>=20 >> Graphs as in vertices, edges, etc :) >> And things like graph basics: BFS, DFS, connected components, topologi= cal >> sort, etc >>=20 >>> ports/math/R may be useful for this -- I use it to generate graphs (and >>> perform statistical analyses). >>>=20 >>> ports/graphics/plotmtv is possibly of some interest, as well, as it >>> allows a certain level of interactivity (though the code hasn't been >>> updated in quite some time -- but it still works). >>>=20 >>> If neither of those suits your intent, perhaps you could expand a bit on= >>> what that intent is? >>=20 >> And, big oops sorry, forgot one very important detail - it has to be C= . >>=20 >> http://en.wikipedia.org/wiki/JUNG >> http://en.wikipedia.org/wiki/Xfig >> http://en.wikipedia.org/wiki/SVG-edit >>=20 >>=20 >> http://en.wikipedia.org/wiki/Category:Graph_drawing_software >> http://en.wikipedia.org/wiki/Comparison_of_vector_graphics_editors >> http://en.wikipedia.org/wiki/Category:Free_diagramming_software >>=20 >>=20 >> Thank you very much . >=20 > Thank you, but all of these appear to be off-mark. > They all are end-user oriented applications for drawing/editing graphs, et= c. > While I need a light-weight library for "embedding" graph analysis. What about Prof. Knuth's Stanford GraphBase library? It is in public domain.= And there is a whole book about it!=20= From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 29 16:35:01 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 89FA2852; Thu, 29 Nov 2012 16:35:01 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-vc0-f182.google.com (mail-vc0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 1516A8FC1B; Thu, 29 Nov 2012 16:35:00 +0000 (UTC) Received: by mail-vc0-f182.google.com with SMTP id fo13so20207838vcb.13 for ; Thu, 29 Nov 2012 08:35:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=9Kl2g5so9i8JODEK+52NmJjdNZ2BubRVPEl7PJz5Uzc=; b=T9rEMC6H2Kb3D0k9zGX/gB9RmNrzM1WDtK4bU5YfobLuB+i64Ap6MpmvjXxnOKK4PI HxvtZF/uBVhm7Vjp9ToQedSXyX70OQnMsuyHi+v1qieJQVrFv7NIT34kH1ZsKo9SiVZl O7Wc0SpprA4yzTGRm7agukb0bjINsoEfu1fQ/dOjXBma/FQq0TPf04L4M0h2opQP5hxO w32gKEtmtyYnBJh9FNZtDSOaf/PuuJdXNNnKL5VAAXC06yeW8v9/k/NFYLADCyUFsiLy tgPpGiB39mUCVIXhaNDNQx4b5bFEWZP+c8MtYjGTOOyS3vwKzr7TxsTCFNZ5EqBEHark or5Q== MIME-Version: 1.0 Received: by 10.58.168.135 with SMTP id zw7mr32885185veb.4.1354206900408; Thu, 29 Nov 2012 08:35:00 -0800 (PST) Received: by 10.58.218.35 with HTTP; Thu, 29 Nov 2012 08:35:00 -0800 (PST) In-Reply-To: <50B77B41.7040008@FreeBSD.org> References: <50B61DAC.7050102@FreeBSD.org> <20121128143115.GJ2617@albert.catwhisker.org> <50B621BA.1080407@FreeBSD.org> <50B77B41.7040008@FreeBSD.org> Date: Thu, 29 Nov 2012 08:35:00 -0800 Message-ID: Subject: Re: lib for working with graphs From: Mehmet Erol Sanliturk To: Andriy Gapon Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Hackers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Nov 2012 16:35:01 -0000 On Thu, Nov 29, 2012 at 7:12 AM, Andriy Gapon wrote: > on 28/11/2012 18:36 Mehmet Erol Sanliturk said the following: > > > > > > On Wed, Nov 28, 2012 at 6:37 AM, Andriy Gapon > > wrote: > > > > on 28/11/2012 16:31 David Wolfskill said the following: > > > On Wed, Nov 28, 2012 at 04:20:28PM +0200, Andriy Gapon wrote: > > >> > > >> Does anyone know a light-weight BSD-licensed (or analogous) > library / piece of > > >> code for doing useful things with graphs? > > >> Thank you. > > >> .... > > > > > > Errr.... "graphs" is fairly ambiguous, and "things with graphs" > covers a > > > very wide range of activities. > > > > Graphs as in vertices, edges, etc :) > > And things like graph basics: BFS, DFS, connected components, > topological > > sort, etc > > > > > ports/math/R may be useful for this -- I use it to generate graphs > (and > > > perform statistical analyses). > > > > > > ports/graphics/plotmtv is possibly of some interest, as well, as it > > > allows a certain level of interactivity (though the code hasn't > been > > > updated in quite some time -- but it still works). > > > > > > If neither of those suits your intent, perhaps you could expand a > bit on > > > what that intent is? > > > > And, big oops sorry, forgot one very important detail - it has to be > C. > > > > http://en.wikipedia.org/wiki/JUNG > > http://en.wikipedia.org/wiki/Xfig > > http://en.wikipedia.org/wiki/SVG-edit > > > > > > http://en.wikipedia.org/wiki/Category:Graph_drawing_software > > http://en.wikipedia.org/wiki/Comparison_of_vector_graphics_editors > > http://en.wikipedia.org/wiki/Category:Free_diagramming_software > > > > > > Thank you very much . > > Thank you, but all of these appear to be off-mark. > They all are end-user oriented applications for drawing/editing graphs, > etc. > While I need a light-weight library for "embedding" graph analysis. > > -- > Andriy Gapon > Graph Theory is vast subject area : http://en.wikipedia.org/wiki/Category:Graph_theory http://en.wikipedia.org/wiki/Graph_theory http://en.wikipedia.org/wiki/Graph_%28mathematics%29 http://en.wikipedia.org/wiki/Power_graph_analysis http://www.cs.sunysb.edu/~algorith/implement/graphbase/implement.shtml If a subject with a selected title is specified , it may be possible to find more detailed information about it . Thank you very much . Mehmet Erol Sanliturk From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 29 16:36:36 2012 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 40AE5A50; Thu, 29 Nov 2012 16:36:36 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebius.int.ru (glebius.int.ru [81.19.69.10]) by mx1.freebsd.org (Postfix) with ESMTP id AF62C8FC17; Thu, 29 Nov 2012 16:36:34 +0000 (UTC) Received: from cell.glebius.int.ru (localhost [127.0.0.1]) by cell.glebius.int.ru (8.14.5/8.14.5) with ESMTP id qATGaX7N020766; Thu, 29 Nov 2012 20:36:33 +0400 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebius.int.ru (8.14.5/8.14.5/Submit) id qATGaXks020765; Thu, 29 Nov 2012 20:36:33 +0400 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebius.int.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Thu, 29 Nov 2012 20:36:33 +0400 From: Gleb Smirnoff To: Zaphod Beeblebrox Subject: Re: 9.1-RC3 IGB dropping connections. Message-ID: <20121129163633.GM14202@FreeBSD.org> References: <50B57632.6050004@sentex.net> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: FreeBSD Hackers , FreeBSD Net , FreeBSD Stable , Mike Tancsa X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Nov 2012 16:36:36 -0000 On Tue, Nov 27, 2012 at 10:26:55PM -0500, Zaphod Beeblebrox wrote: Z> > Are you using pf ? Also, did you confirm it is the igb nic and not Z> > something more general ? e.g. if you put in a different nic, does the Z> > problem go away ? Z> Z> No pf, the motherboard em-driver NIC does not have this problem. I'd suggest to do some traffic sniffing when connection is dropped. May be some other host on network takes your IP address and resets connection? -- Totus tuus, Glebius. From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 1 00:01:19 2012 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A1DB9BBF for ; Sat, 1 Dec 2012 00:01:19 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell0.rawbw.com (shell0.rawbw.com [198.144.192.45]) by mx1.freebsd.org (Postfix) with ESMTP id 710818FC08 for ; Sat, 1 Dec 2012 00:01:19 +0000 (UTC) Received: from eagle.yuri.org (stunnel@localhost [127.0.0.1]) (authenticated bits=0) by shell0.rawbw.com (8.14.4/8.14.4) with ESMTP id qB101IKH094574 for ; Fri, 30 Nov 2012 16:01:18 -0800 (PST) (envelope-from yuri@rawbw.com) Message-ID: <50B948CE.5080304@rawbw.com> Date: Fri, 30 Nov 2012 16:01:18 -0800 From: Yuri User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: hackers@freebsd.org Subject: How to overload the system call in the userland program? Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Dec 2012 00:01:19 -0000 I am looking into one library (google-perftools) that attempts to overload sbrk(2). In Linux libc translates calls, ex. sbrk -> __sbrk (in libc), so one can define their own version, call extern __sbrk and it works. FreeBSD programs connect to the symbol sbrk@@FBSD_1.0 So what is the way to overload the system call like this would be in linux?: extern "C" void* __sbrk(ptrdiff_t increment); extern "C" void* sbrk(intptr_t increment) { return__sbrk(increment); } Yuri