From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 14 08:25:22 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B06AC1065694 for ; Mon, 14 Dec 2009 08:25:22 +0000 (UTC) (envelope-from ibrahim.harrani@gmail.com) Received: from mail-bw0-f213.google.com (mail-bw0-f213.google.com [209.85.218.213]) by mx1.freebsd.org (Postfix) with ESMTP id 472F08FC17 for ; Mon, 14 Dec 2009 08:25:21 +0000 (UTC) Received: by bwz5 with SMTP id 5so1922555bwz.3 for ; Mon, 14 Dec 2009 00:25:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=Y5WYI6zsxyOg6lrjdE5+WaRA+nG26aqwru9KwD6K65E=; b=LA62QsQJDf6cDiaIlMuxwXKMoSEl8BHNjzIROv8sGcdZWtXyhgbaDYM5be0ri6vrMB Xr1bQl4bEcQDAM9XqDsLZIOX6njCffjZP3CvlZ/EAeY4xsvcoqEZMfzMphQrtzNBpy3+ Zw5R2Sq2Dr3uUutigQRrBbxohTz7sVcVcxKtk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=fxh0DqMUZsEqqz1YWZdCtUOJIXbCiaqB6PanSLUcTRnh5ZBVM8Er/2Bg4yIdmPvUVY LIqmmk7FpsfklmCJktO2WHjvf43wxmSk5Bb2N03o9TeX1a7lBxieix3MVyLUdUiJo6r2 Jo9qADD9Qd36/grEucBDK8wqouoX8epQOChjA= MIME-Version: 1.0 Received: by 10.204.24.130 with SMTP id v2mr2568338bkb.33.1260777730894; Mon, 14 Dec 2009 00:02:10 -0800 (PST) Date: Mon, 14 Dec 2009 10:02:10 +0200 Message-ID: <530068a0912140002w10641022w57bc3f8129e8fde0@mail.gmail.com> From: Ibrahim Harrani To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: panic: semexit - semid not allocated in FreeBSD 6.3 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 08:25:22 -0000 Hi, I am using FreeBSD 6.3 amd64, I am getting the following crash semexit - semid not allocated cpuid = 7 Cannot dump. No dump device defined Sleeping thread (tid 101800, pid 4107) owns a non-sleepable lock It seems that this problem was reported and fixed in FreeBSD 7.1 http://lists.freebsd.org/pipermail/freebsd-hackers/2009-January/027317.html Is there any fix for FreeBSD 6.3? Thanks. Ibrahim From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 14 16:15:11 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 783091065676 for ; Mon, 14 Dec 2009 16:15:11 +0000 (UTC) (envelope-from hkunst@moneyfitness.com) Received: from mail.truebridge.com (mail.truebridge.com [216.75.192.44]) by mx1.freebsd.org (Postfix) with ESMTP id 0E8A68FC1E for ; Mon, 14 Dec 2009 16:15:10 +0000 (UTC) Received: (qmail 21964 invoked from network); 14 Dec 2009 10:48:29 -0500 Received: from static-71-243-118-33.bos.east.verizon.net (HELO ?192.168.199.40?) (hkunst@71.243.118.33) by mail.truebridge.com with SMTP; 14 Dec 2009 10:48:29 -0500 Message-ID: <4B265E27.8050906@moneyfitness.com> Date: Mon, 14 Dec 2009 10:47:51 -0500 From: Holger Kunst User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.5) Gecko/20091204 Lightning/1.0pre Thunderbird/3.0 MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Mon, 14 Dec 2009 17:11:36 +0000 Subject: Email sent from "at" command going to the wrong account X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 16:15:11 -0000 Hi, The "at" command sends an email with the output of the scheduled job. I've experienced inconsistent results when running jobs, receiving emails in accounts not associated with the user currently logged in. To reproduce in FreeBSD 7.2-RELEASE-p2 Case #1 login as user a (new shell through ssh) echo "echo 1" | at now --> user a will receive an email containing "1" - this is as expected Case #2 login as user a (new shell through ssh) login as user b exit echo "echo 1" | at now --> user b will receive an email containing "1" - this is not as expected, since I am user a again A look at the source for "at" reveals that "at" is getting the mailname from getlogin(). Running a small test program that outputs getlogin(), confirms the above behavior: A log-in and out of another account makes getlogin() return that account's name, even though the shell has been closed and we are back to the original shell and the original user a. Is this the intended behavior? Any hints would be appreciated. Best regards, Holger Kunst From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 14 17:20:34 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5E26C1065672 for ; Mon, 14 Dec 2009 17:20:34 +0000 (UTC) (envelope-from nate@thatsmathematics.com) Received: from euclid.ucsd.edu (euclid.ucsd.edu [132.239.145.52]) by mx1.freebsd.org (Postfix) with ESMTP id 3FE978FC08 for ; Mon, 14 Dec 2009 17:20:33 +0000 (UTC) Received: from zeno.ucsd.edu (zeno.ucsd.edu [132.239.145.22]) by euclid.ucsd.edu (8.11.7p3+Sun/8.11.7) with ESMTP id nBEHKXo20901; Mon, 14 Dec 2009 09:20:33 -0800 (PST) Received: from localhost (neldredg@localhost) by zeno.ucsd.edu (8.11.7p3+Sun/8.11.7) with ESMTP id nBEHKXU10966; Mon, 14 Dec 2009 09:20:33 -0800 (PST) X-Authentication-Warning: zeno.ucsd.edu: neldredg owned process doing -bs Date: Mon, 14 Dec 2009 09:20:33 -0800 (PST) From: Nate Eldredge X-X-Sender: neldredg@zeno.ucsd.edu To: Holger Kunst In-Reply-To: <4B265E27.8050906@moneyfitness.com> Message-ID: References: <4B265E27.8050906@moneyfitness.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org Subject: Re: Email sent from "at" command going to the wrong account X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 17:20:34 -0000 On Mon, 14 Dec 2009, Holger Kunst wrote: > Hi, > > The "at" command sends an email with the output of the scheduled job. I've > experienced inconsistent results when running jobs, receiving emails in > accounts not associated with the user currently logged in. > > To reproduce in FreeBSD 7.2-RELEASE-p2 > > Case #1 > login as user a (new shell through ssh) > echo "echo 1" | at now > --> user a will receive an email containing "1" - this is as expected > > Case #2 > login as user a (new shell through ssh) > login as user b How are you accomplishing this? > exit > echo "echo 1" | at now > --> user b will receive an email containing "1" - this is not as expected, > since I am user a again > > A look at the source for "at" reveals that "at" is getting the mailname from > getlogin(). Running a small test program that outputs getlogin(), confirms > the above behavior: A log-in and out of another account makes getlogin() > return that account's name, even though the shell has been closed and we are > back to the original shell and the original user a. > > Is this the intended behavior? Any hints would be appreciated. -- Nate Eldredge nate@thatsmathematics.com From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 14 19:19:10 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 64F2A106566C for ; Mon, 14 Dec 2009 19:19:10 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.geekcn.org (delphij-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:2c9::2]) by mx1.freebsd.org (Postfix) with ESMTP id 0DBD08FC15 for ; Mon, 14 Dec 2009 19:19:10 +0000 (UTC) Received: from localhost (tarsier.geekcn.org [211.166.10.233]) by tarsier.geekcn.org (Postfix) with ESMTP id 9899AA585F7; Tue, 15 Dec 2009 03:19:03 +0800 (CST) X-Virus-Scanned: amavisd-new at geekcn.org Received: from tarsier.geekcn.org ([211.166.10.233]) by localhost (mail.geekcn.org [211.166.10.233]) (amavisd-new, port 10024) with ESMTP id BNYb85ohZIL9; Tue, 15 Dec 2009 03:18:55 +0800 (CST) Received: from delta.delphij.net (drawbridge.ixsystems.com [206.40.55.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTPSA id 3859FA58594; Tue, 15 Dec 2009 03:18:54 +0800 (CST) DomainKey-Signature: a=rsa-sha1; s=default; d=delphij.net; c=nofws; q=dns; h=message-id:date:from:reply-to:organization:user-agent: mime-version:to:cc:subject:references:in-reply-to: x-enigmail-version:openpgp:content-type:content-transfer-encoding; b=kVgmN7cdDQP7r1Q2yzOkLF5T2antmijjsf3EkS7Qqa4LigYcVKhvSdHO3Qqm5OUoD IYAfiQpW5X26palze0RJA== Message-ID: <4B268F9B.1050108@delphij.net> Date: Mon, 14 Dec 2009 11:18:51 -0800 From: Xin LI Organization: The Geek China Organization User-Agent: Thunderbird 2.0.0.23 (X11/20091130) MIME-Version: 1.0 To: Ravi Shankar References: <734342.41538.qm@web33202.mail.mud.yahoo.com> In-Reply-To: <734342.41538.qm@web33202.mail.mud.yahoo.com> X-Enigmail-Version: 0.95.7 OpenPGP: id=18EDEBA0; url=http://www.delphij.net/delphij.asc Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: freebsd-hackers@freebsd.org Subject: Re: Regarding enabling IOAPIC on Intel Dual core processor based boards having Broadcom controller X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: d@delphij.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 19:19:10 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Ravi Shankar wrote: > Hi, > > We are using Freebsd6.2 bases OS on our LV 5200 Series Intel Dual Core Xeon bases processor(Wolfdale-DP-ULV). In the carrier board hosting the processor we have BCM5703 controller. > Currently we are using only one core in 32 bit mode and planning to use dual core where we need to enable IOAPIC. When IOAPIC is not enabled I see the bcm/bge driver is attached to IRQ10 and everything works fine, but when I enable IOAPIC I still see the boot msgs show that bge is attached to irq10 but the Broadcom controller does not come up. I found interrupt storm on irq17 ( remember without IOAPIC enable there are not IRQ assignments beyond IRQ16),looks like the controller is interrupting on 17 while driver waits on 10. > > When I stop and loader and assign it manually using config command "set hw.pci8.9.INTA.irq=”17”" , everything works fine. Would be great if some one can throw some light on this IRQ mapping when IOAPIC is enabled and possible fix ( Software or BIOS?) > > NOTE: Other devices ( Intel controller (em driver)) are working fine only this BCM5703 is having issues with IOAPIC Is it possible for you to use some newer FreeBSD release, i.e. 6.3 or 6.4, or 7.x even 8.x and see if that would solve your problem? Cheers, - -- Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.13 (FreeBSD) iEYEARECAAYFAksmj5sACgkQi+vbBBjt66AJvwCeJVlT301Ulu54C+UwvdNXjTxY KCkAn19OqPOpfeifzkRdf2zooRar9UrK =i1Dc -----END PGP SIGNATURE----- From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 15 19:40:08 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DEA66106566C for ; Tue, 15 Dec 2009 19:40:08 +0000 (UTC) (envelope-from linda.messerschmidt@gmail.com) Received: from mail-ew0-f226.google.com (mail-ew0-f226.google.com [209.85.219.226]) by mx1.freebsd.org (Postfix) with ESMTP id 7984B8FC12 for ; Tue, 15 Dec 2009 19:40:08 +0000 (UTC) Received: by ewy26 with SMTP id 26so233021ewy.3 for ; Tue, 15 Dec 2009 11:40:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=bVcgLrh9UoRkPuNA2YFI+TIthF83RZkmxgmhA0V23Kw=; b=CC4mLrL3Fm5vMTfs1zlG3V4te4TiW8MMKhNJilFD6Gd5lVnzT2PyrRQasPXHxy2/tR 9vKoGbuyLvO2wZFoXcg2RcJAqj+luWgd40uNBRHmREtzlJ7pmR5xZV+X6ILI/hmn7Q1q hozxI+5B/Su68SSh0THChROUral3+WOrc17F8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=GJEJAbLBVKUZeQc5ldfayzCtbDrRGKkO2Nvki91UTSy3junYLuXTzOTS6T3v7JaPn1 6C7AxBGB+LqvQqYHGsxYCZ2RRbfGnrhbFWe9N5B+/iQXS8P0La+yvDTEO+8fY0nzt9Bo DX6lxShOuvEgyZ1qs+hyrwTrBZV4jshmxq5UI= MIME-Version: 1.0 Received: by 10.216.88.80 with SMTP id z58mr298319wee.116.1260906007155; Tue, 15 Dec 2009 11:40:07 -0800 (PST) Date: Tue, 15 Dec 2009 14:40:07 -0500 Message-ID: <237c27100912151140o1b227bb1pdaa65f5aee13ab5b@mail.gmail.com> From: Linda Messerschmidt To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: 8.0-RELEASE-p1 Panic "panic: sbdrop" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 19:40:08 -0000 This is a new one on me: panic: sbdrop cpuid = 3 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a panic() at panic+0x182 sbdrop_internal() at sbdrop_internal+0x323 soisdisconnected() at soisdisconnected+0xbe tcp_close() at tcp_close+0x45 tcp_do_segment() at tcp_do_segment+0x122f tcp_input() at tcp_input+0xc92 ip_input() at ip_input+0xac netisr_dispatch_src() at netisr_dispatch_src+0x7e ether_demux() at ether_demux+0x15d ether_input() at ether_input+0x17b em_rxeof() at em_rxeof+0x287 em_handle_rxtx() at em_handle_rxtx+0x2f taskqueue_run() at taskqueue_run+0x93 taskqueue_thread_loop() at taskqueue_thread_loop+0x46 fork_exit() at fork_exit+0x118 fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xffffff8000117d30, rbp = 0 --- This machine runs squid as a reverse proxy, and this has happened a couple of times now in the past day. Unfortunately it's a production machine, so we'll have to go back to 7.2. I can probably leave it as-is for 24 hours or so if anybody wants me to check something, but it doesn't have a dump or a debug kernel and I unfortunately can't put it back in production to provoke another crash. :( But I wanted to at least report this before we did in case it's useful to anyone. From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 15 20:11:10 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E01DB1065693; Tue, 15 Dec 2009 20:11:09 +0000 (UTC) (envelope-from google@vink.pl) Received: from mail-fx0-f163.google.com (mail-fx0-f163.google.com [209.85.220.163]) by mx1.freebsd.org (Postfix) with ESMTP id 492298FC15; Tue, 15 Dec 2009 20:11:08 +0000 (UTC) Received: by fxm3 with SMTP id 3so87513fxm.3 for ; Tue, 15 Dec 2009 12:11:08 -0800 (PST) Received: by 10.223.98.19 with SMTP id o19mr370619fan.82.1260907025765; Tue, 15 Dec 2009 11:57:05 -0800 (PST) Received: from mail-fx0-f227.google.com (mail-fx0-f227.google.com [209.85.220.227]) by mx.google.com with ESMTPS id 13sm72027fxm.13.2009.12.15.11.57.03 (version=SSLv3 cipher=RC4-MD5); Tue, 15 Dec 2009 11:57:05 -0800 (PST) Received: by fxm27 with SMTP id 27so264939fxm.3 for ; Tue, 15 Dec 2009 11:57:03 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.5.8 with SMTP id 8mr8272925fat.48.1260907023184; Tue, 15 Dec 2009 11:57:03 -0800 (PST) In-Reply-To: References: Date: Tue, 15 Dec 2009 20:57:03 +0100 Message-ID: <2ae8edf30912151157t53267adek85af80b1e31fb4b@mail.gmail.com> From: Wiktor Niesiobedzki To: Ivan Voras Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Tue, 15 Dec 2009 20:59:04 +0000 Cc: freebsd-fs , freebsd-hackers Subject: Re: ZFS, compression, system load, pauses (livelocks?) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 20:11:10 -0000 2009/12/15 Ivan Voras : > The context of this post is file servers running FreeBSD 8 and ZFS with > compressed file systems on low-end hardware, or actually high-end hardwar= e > on VMWare ESX 3.5 and 4, which kind of makes it low-end as far as storage= is > concerned. The servers are standby backup mirrors of production servers - > thus many writes, few reads. > > Running this setup I notice two things: > > 1) load averages get very high, though the only usage these systems get i= s > file system usage: > 2) long pauses, in what looks like vfs.zfs.txg.timeout second intervals, > which seemengly block everything, or at least the entire userland. These > pauses are sometimes so long that file transfers fail, which must be > avoided. > > Looking at the list of processes it looks like a large number of kernel a= nd > userland processes are woken up at once. From the kernel side there are > regularily all g_* threads, but also unrelated threads like bufdaemon, > softdepflush, etc. and from the userland - top, syslog, cron, etc. It is > like ZFS livelocks everything else. > > Any ideas on the "pauses" issue? > Hi, I've a bit striped your post. It's kind of "me too" message (more details here: http://lists.freebsd.org/pipermail/freebsd-geom/2009-December= /003810.html). What I've figured out so far is, that lowering the kernel thread priority (as pjd@ suggested) gives quite promising results (no livelocks at all). Though my bottleneck were caused by GELI thread. The pattern there is like this: sched_prio(curthread, PRIBIO); [...] msleep(sc, &sc->sc_queue_mtx, PDROP | PRIBIO, "geli:w", 0); I'm running right now with changed wersion - where I have: msleep(sc, &sc->sc_queue_mtx, PDROP, "geli:w", 0); So I don't change initial thread priority. It doesn't give such result as using PUSER prio, but I fear, that using PUSER may cause livelocks in some other cases. This helps my case (geli encryption and periodic locks during ZFS transaction commits) with some performance penalty, but I have similar problems in other cases. When I run: # zfs scrub tank Then "kernel" system process/thread consumes most of CPU (>95% in system) and load rises to 20+ for the period of scrubbing. During scrub my top screen looks like: last pid: 87570; load averages: 8.26, 2.84, 1.68 199 processes: 3 running, 179 sleeping, 17 waiting CPU: 2.4% user, 0.0% nice, 97.0% system, 0.6% interrupt, 0.0% idle Mem: 66M Active, 6256K Inact, 1027M Wired, 104K Cache, 240K Buf, 839M Free Swap: 4096M Total, 4096M Free PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMMAND 0 root 69 -8 0 0K 544K - 104:40 67.19% kernel 24 root 1 -8 - 0K 8K geli:w 9:56 5.66% g_eli[0] ad= 6 26 root 1 -8 - 0K 8K geli:w 9:50 5.47% g_eli[0] ad= 10 25 root 1 -8 - 0K 8K geli:w 9:53 5.37% g_eli[0] ad= 8 8 root 12 -8 - 0K 104K vgeom: 61:35 3.27% zfskern 3 root 1 -8 - 0K 8K - 3:22 0.68% g_up 11 root 17 -60 - 0K 136K WAIT 31:21 0.29% intr Intresting thing, is that I have 17 processes waiting for CPU reported (though only intr is the only process that is reported as in WAIT state - at least for top40 processes). I just wonder, whether this might be a scheduler related issue. I'm thinking about giving a SCHED_4BSD a try. Cheers, Wiktor Niesiob=C4=99dzki From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 15 21:21:56 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1ED21106568B for ; Tue, 15 Dec 2009 21:21:56 +0000 (UTC) (envelope-from hkunst@moneyfitness.com) Received: from mail.truebridge.com (mail.truebridge.com [216.75.192.44]) by mx1.freebsd.org (Postfix) with ESMTP id AD25C8FC16 for ; Tue, 15 Dec 2009 21:21:55 +0000 (UTC) Received: (qmail 68753 invoked from network); 15 Dec 2009 16:21:54 -0500 Received: from static-71-243-118-33.bos.east.verizon.net (HELO ?192.168.199.40?) (hkunst@71.243.118.33) by mail.truebridge.com with SMTP; 15 Dec 2009 16:21:54 -0500 Message-ID: <4B27FDA7.3070100@moneyfitness.com> Date: Tue, 15 Dec 2009 16:20:39 -0500 From: Holger Kunst User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.5) Gecko/20091204 Lightning/1.0pre Thunderbird/3.0 MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: <4B265E27.8050906@moneyfitness.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Email sent from "at" command going to the wrong account X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 21:21:56 -0000 Nate, Thank you for your reply, On 12/14/2009 12:20 PM, Nate Eldredge wrote: > On Mon, 14 Dec 2009, Holger Kunst wrote: > >> The "at" command sends an email with the output of the scheduled job. >> I've experienced inconsistent results when running jobs, receiving >> emails in accounts not associated with the user currently logged in. >> >> To reproduce in FreeBSD 7.2-RELEASE-p2 >> >> Case #1 >> login as user a (new shell through ssh) >> echo "echo 1" | at now >> --> user a will receive an email containing "1" - this is as expected >> >> Case #2 >> login as user a (new shell through ssh) >> login as user b > > How are you accomplishing this? login command from the shell: "login b", enter password Best regards, Holger From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 15 21:43:27 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D6298106568F; Tue, 15 Dec 2009 21:43:27 +0000 (UTC) (envelope-from ivoras@gmail.com) Received: from mail-ew0-f226.google.com (mail-ew0-f226.google.com [209.85.219.226]) by mx1.freebsd.org (Postfix) with ESMTP id 41CBB8FC1B; Tue, 15 Dec 2009 21:43:26 +0000 (UTC) Received: by ewy26 with SMTP id 26so361499ewy.3 for ; Tue, 15 Dec 2009 13:43:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:from:date:x-google-sender-auth:message-id:subject:to:cc :content-type:content-transfer-encoding; bh=6Q1uzqzbAbd0UaV+xSljXe5UjfvVqgDaDcMCXGgPnug=; b=uejzTYatuFCfOPDMN35521z9RUMvyUq3pTRZYHpX1H1m+Hu2qP7b1u7v7u6GU37eBH /sgOaUunvxMdvMgTKclNCA1JWVcr4TCHDJVKfJn3X/DHH8A22X1TRxdNpfEyqb8dOGlB 4PAmGVfhJL12JDY6xPEHV7MW84Qe/tjXGbnlM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; b=pPmwthsDxf2fpAUuOyaQ2sj+NfacUG2pD5dnn6SWiS7Ou/5o12ZSBimKrqnVY1781s X5djZJvl84f0CwNqCc58DwnR1mv+FHQV0v5g7Ie555FdgEuw+stHafMRZBLy5RgEeXTE STTKkIWJ2SwRtSZ4BFsAGi6Zk4k2EAOtjfMW8= MIME-Version: 1.0 Sender: ivoras@gmail.com Received: by 10.216.90.11 with SMTP id d11mr37318wef.187.1260913406139; Tue, 15 Dec 2009 13:43:26 -0800 (PST) In-Reply-To: <2ae8edf30912151157t53267adek85af80b1e31fb4b@mail.gmail.com> References: <2ae8edf30912151157t53267adek85af80b1e31fb4b@mail.gmail.com> From: Ivan Voras Date: Tue, 15 Dec 2009 22:43:06 +0100 X-Google-Sender-Auth: 138eac8a0e663cc7 Message-ID: <9bbcef730912151343p729b6d29w97e56bab96f264f9@mail.gmail.com> To: Wiktor Niesiobedzki Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs , freebsd-hackers Subject: Re: ZFS, compression, system load, pauses (livelocks?) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 21:43:27 -0000 2009/12/15 Wiktor Niesiobedzki : > 2009/12/15 Ivan Voras : >> The context of this post is file servers running FreeBSD 8 and ZFS with >> compressed file systems on low-end hardware, or actually high-end hardwa= re >> on VMWare ESX 3.5 and 4, which kind of makes it low-end as far as storag= e is >> concerned. The servers are standby backup mirrors of production servers = - >> thus many writes, few reads. >> >> Running this setup I notice two things: >> >> 1) load averages get very high, though the only usage these systems get = is >> file system usage: >> 2) long pauses, in what looks like vfs.zfs.txg.timeout second intervals, >> which seemengly block everything, or at least the entire userland. These >> pauses are sometimes so long that file transfers fail, which must be >> avoided. >> >> Looking at the list of processes it looks like a large number of kernel = and >> userland processes are woken up at once. From the kernel side there are >> regularily all g_* threads, but also unrelated threads like bufdaemon, >> softdepflush, etc. and from the userland - top, syslog, cron, etc. It is >> like ZFS livelocks everything else. >> >> Any ideas on the "pauses" issue? >> > > Hi, > > I've a bit striped your post. It's kind of "me too" message (more > details here: http://lists.freebsd.org/pipermail/freebsd-geom/2009-Decemb= er/003810.html). > What I've figured out so far is, that lowering the kernel thread > priority (as pjd@ suggested) gives quite promising results (no > livelocks at all). Though my bottleneck were caused by GELI thread. > > The pattern there is like this: > > sched_prio(curthread, PRIBIO); > [...] > msleep(sc, &sc->sc_queue_mtx, PDROP | PRIBIO, =C2=A0"geli:w", 0); I have tried before reducing priority of ZFS taskqueues but only to PRIBIO, not below it - not much effect wrt "pauses". From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 15 22:39:19 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A448E1065692; Tue, 15 Dec 2009 22:39:19 +0000 (UTC) (envelope-from google@vink.pl) Received: from mail-fx0-f227.google.com (mail-fx0-f227.google.com [209.85.220.227]) by mx1.freebsd.org (Postfix) with ESMTP id E72208FC0A; Tue, 15 Dec 2009 22:39:18 +0000 (UTC) Received: by fxm27 with SMTP id 27so415732fxm.3 for ; Tue, 15 Dec 2009 14:39:17 -0800 (PST) Received: by 10.223.5.77 with SMTP id 13mr171987fau.86.1260916757560; Tue, 15 Dec 2009 14:39:17 -0800 (PST) Received: from mail-fx0-f227.google.com (mail-fx0-f227.google.com [209.85.220.227]) by mx.google.com with ESMTPS id 13sm116223fxm.9.2009.12.15.14.39.17 (version=SSLv3 cipher=RC4-MD5); Tue, 15 Dec 2009 14:39:17 -0800 (PST) Received: by fxm27 with SMTP id 27so415718fxm.3 for ; Tue, 15 Dec 2009 14:39:16 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.143.15 with SMTP id s15mr177897fau.77.1260916756585; Tue, 15 Dec 2009 14:39:16 -0800 (PST) In-Reply-To: <9bbcef730912151343p729b6d29w97e56bab96f264f9@mail.gmail.com> References: <2ae8edf30912151157t53267adek85af80b1e31fb4b@mail.gmail.com> <9bbcef730912151343p729b6d29w97e56bab96f264f9@mail.gmail.com> Date: Tue, 15 Dec 2009 23:39:16 +0100 Message-ID: <2ae8edf30912151439h799277a0ofee13f5aecc55f00@mail.gmail.com> From: Wiktor Niesiobedzki To: Ivan Voras Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Tue, 15 Dec 2009 22:45:59 +0000 Cc: freebsd-fs , freebsd-hackers Subject: Re: ZFS, compression, system load, pauses (livelocks?) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 22:39:19 -0000 2009/12/15 Ivan Voras : > I have tried before reducing priority of ZFS taskqueues but only to > PRIBIO, not below it - not much effect wrt "pauses". I was testing with getting the thread as low priority as PUSER (with original pjd@ patch) and it was actually performing better than the current solution, though I found that quite risky. Cheers, Wiktor Niesiob=C4=99dzki From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 16 11:52:38 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5CA321065670 for ; Wed, 16 Dec 2009 11:52:38 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 35A7F8FC15 for ; Wed, 16 Dec 2009 11:52:38 +0000 (UTC) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id C867946B23; Wed, 16 Dec 2009 06:52:37 -0500 (EST) Date: Wed, 16 Dec 2009 11:52:37 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Linda Messerschmidt In-Reply-To: <237c27100912151140o1b227bb1pdaa65f5aee13ab5b@mail.gmail.com> Message-ID: References: <237c27100912151140o1b227bb1pdaa65f5aee13ab5b@mail.gmail.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org Subject: Re: 8.0-RELEASE-p1 Panic "panic: sbdrop" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2009 11:52:38 -0000 On Tue, 15 Dec 2009, Linda Messerschmidt wrote: > This is a new one on me: Hi Linda-- Unfortunately, this has historically been a tricky panic to debug, as it's associated with a sanity check that picks up kernel memory corruption that may have occurred at a much earlier time. Without a crashdump, we won't get much further. However, let's see what we can do, perhaps trying to find some common configuration element with another past report of the same diagnostic. FYI, typically this panic occurs as a result of a concurrency bug in a device driver, although it can be a symptom of a more general network stack bug. Could you tell us a bit more about the network configuration -- especially, are you using any tunneling software (such as ipsec), netgraph, or other less commonly used network features? Are you using accept filters? Robert N M Watson Computer Laboratory University of Cambridge > > panic: sbdrop > cpuid = 3 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > panic() at panic+0x182 > sbdrop_internal() at sbdrop_internal+0x323 > soisdisconnected() at soisdisconnected+0xbe > tcp_close() at tcp_close+0x45 > tcp_do_segment() at tcp_do_segment+0x122f > tcp_input() at tcp_input+0xc92 > ip_input() at ip_input+0xac > netisr_dispatch_src() at netisr_dispatch_src+0x7e > ether_demux() at ether_demux+0x15d > ether_input() at ether_input+0x17b > em_rxeof() at em_rxeof+0x287 > em_handle_rxtx() at em_handle_rxtx+0x2f > taskqueue_run() at taskqueue_run+0x93 > taskqueue_thread_loop() at taskqueue_thread_loop+0x46 > fork_exit() at fork_exit+0x118 > fork_trampoline() at fork_trampoline+0xe > --- trap 0, rip = 0, rsp = 0xffffff8000117d30, rbp = 0 --- > > This machine runs squid as a reverse proxy, and this has happened a > couple of times now in the past day. > > Unfortunately it's a production machine, so we'll have to go back to > 7.2. I can probably leave it as-is for 24 hours or so if anybody > wants me to check something, but it doesn't have a dump or a debug > kernel and I unfortunately can't put it back in production to provoke > another crash. :( But I wanted to at least report this before we > did in case it's useful to anyone. > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 16 06:13:36 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5DD5F106566B for ; Wed, 16 Dec 2009 06:13:36 +0000 (UTC) (envelope-from eugen@eg.sd.rdtc.ru) Received: from eg.sd.rdtc.ru (eg.sd.rdtc.ru [62.231.161.221]) by mx1.freebsd.org (Postfix) with ESMTP id 258CC8FC08 for ; Wed, 16 Dec 2009 06:13:23 +0000 (UTC) Received: from eg.sd.rdtc.ru (localhost [127.0.0.1]) by eg.sd.rdtc.ru (8.14.3/8.14.3) with ESMTP id nBG6DD9K098821; Wed, 16 Dec 2009 13:13:14 +0700 (KRAT) (envelope-from eugen@eg.sd.rdtc.ru) Message-ID: <4B287A79.6090604@eg.sd.rdtc.ru> Date: Wed, 16 Dec 2009 13:13:13 +0700 From: Eugene Grosbein User-Agent: Thunderbird 2.0.0.23 (X11/20090918) MIME-Version: 1.0 To: Holger Kunst References: <4B265E27.8050906@moneyfitness.com> In-Reply-To: <4B265E27.8050906@moneyfitness.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Wed, 16 Dec 2009 12:30:29 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: Email sent from "at" command going to the wrong account X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2009 06:13:36 -0000 Holger Kunst wrote: > Hi, > > The "at" command sends an email with the output of the scheduled job. > I've experienced inconsistent results when running jobs, receiving > emails in accounts not associated with the user currently logged in. > > To reproduce in FreeBSD 7.2-RELEASE-p2 > > Case #1 > login as user a (new shell through ssh) > echo "echo 1" | at now > --> user a will receive an email containing "1" - this is as expected > > Case #2 > login as user a (new shell through ssh) > login as user b > exit > echo "echo 1" | at now > --> user b will receive an email containing "1" - this is not as > expected, since I am user a again > > A look at the source for "at" reveals that "at" is getting the mailname > from getlogin(). Running a small test program that outputs getlogin(), > confirms the above behavior: A log-in and out of another account makes > getlogin() return that account's name, even though the shell has been > closed and we are back to the original shell and the original user a. > > Is this the intended behavior? Any hints would be appreciated. This is known long-standing bug. FreeBSD-4.9 was affected (may be earlier) and all versions after it: http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/61355 The PR has some kind of patch in the Audit-Trail. Eugene Grosbein From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 17 09:15:40 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 82FA41065676 for ; Thu, 17 Dec 2009 09:15:40 +0000 (UTC) (envelope-from ltsampros@upnet.gr) Received: from kane.otenet.gr (kane.otenet.gr [83.235.67.31]) by mx1.freebsd.org (Postfix) with ESMTP id E44348FC1B for ; Thu, 17 Dec 2009 09:15:39 +0000 (UTC) Received: from bifteki.lan (ppp-94-66-42-105.home.otenet.gr [94.66.42.105]) by kane.otenet.gr (8.13.8/8.13.8/Debian-3) with ESMTP id nBH9Fckm025451 for ; Thu, 17 Dec 2009 11:15:38 +0200 Received: from bifteki.lan (localhost [127.0.0.1]) by bifteki.lan (8.14.3/8.14.3) with ESMTP id nBH9FVuW015620 for ; Thu, 17 Dec 2009 11:15:31 +0200 (EET) (envelope-from ltsampros@bifteki.lan) Received: (from ltsampros@localhost) by bifteki.lan (8.14.3/8.14.3/Submit) id nBH9FV0D015619; Thu, 17 Dec 2009 11:15:31 +0200 (EET) (envelope-from ltsampros@bifteki.lan) From: Leonidas Tsampros To: freebsd-hackers@freebsd.org Mail-Followup-To: freebsd-hackers@freebsd.org Date: Thu, 17 Dec 2009 11:15:30 +0200 Message-ID: <86zl5iufkd.fsf@bifteki.lan> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.95 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: pam_passwdqc update to latest vendor release X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Dec 2009 09:15:40 -0000 Hello, I read a mail on this list 3 or 4 weeks saying/stating that pam_passwdqc was out of date. To update the module I used the vendor release 1.0.5 which can be found here http://www.openwall.com/pam/modules/pam_passwdqc/pam_passwdqc-1.0.5.tar.gz The patch is available here: http://bifteki.podzone.org/~ltsampros/pam_passwdc.diff And a summary of the patch: M contrib/pam_modules/pam_passwdqc/INTERNALS M contrib/pam_modules/pam_passwdqc/LICENSE M contrib/pam_modules/pam_passwdqc/Makefile M contrib/pam_modules/pam_passwdqc/PLATFORMS M contrib/pam_modules/pam_passwdqc/README M contrib/pam_modules/pam_passwdqc/pam_macros.h M contrib/pam_modules/pam_passwdqc/pam_passwdqc.c A contrib/pam_modules/pam_passwdqc/pam_passwdqc.map M contrib/pam_modules/pam_passwdqc/pam_passwdqc.spec M contrib/pam_modules/pam_passwdqc/passwdqc.h M contrib/pam_modules/pam_passwdqc/passwdqc_check.c M contrib/pam_modules/pam_passwdqc/passwdqc_random.c M lib/libpam/modules/pam_passwdqc/pam_passwdqc.8 I built the updated module on my system. I did some testing with the default options in /etc/pam.d/passwd and it seems to work okey. Feedback is welcome. Regards Leonidas From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 17 11:23:06 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CAEAF1065670; Thu, 17 Dec 2009 11:23:06 +0000 (UTC) (envelope-from prvs=1602d8d4d9=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id 28FFD8FC0A; Thu, 17 Dec 2009 11:23:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=multiplay.co.uk; s=Multiplay; t=1261048331; x=1261653131; q=dns/txt; h=Received: Message-ID:From:To:Subject:Date:MIME-Version:Content-Type: Content-Transfer-Encoding; bh=+CLZAIp2e+Fxhf1rD1frFN4/32vYmcVbN4 QDXKJIiKQ=; b=hM9Y87KGoRJDiEk1Hwl6luLV+AbH6AQFE5mHQ/kb3r8Bt3zHRz lxx8u9eJAsKmRAQ6VZhJG8tlom2YrZTf6CEouJ9rlcKrfqBZtvTfkB9CNu1aD+7a dbtO+tkuJGLei/WoxBnk5AwXi+zIF+JDnMF8hBbqSR3LlZ8+3wzbID7pc= X-MDAV-Processed: mail1.multiplay.co.uk, Thu, 17 Dec 2009 11:12:11 +0000 Received: from r2d2 by mail1.multiplay.co.uk (MDaemon PRO v10.0.4) with ESMTP id md50008877441.msg; Thu, 17 Dec 2009 11:12:11 +0000 X-Spam-Processed: mail1.multiplay.co.uk, Thu, 17 Dec 2009 11:12:11 +0000 (not processed: message from trusted or authenticated source) X-Authenticated-Sender: Killing@multiplay.co.uk X-MDRemoteIP: 213.123.247.160 X-Return-Path: prvs=1602d8d4d9=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk Message-ID: From: "Steven Hartland" To: , Date: Thu, 17 Dec 2009 11:12:07 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5843 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 Cc: Subject: Passenger hangs on live and SEGV on tests possible threading / kernel bug? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Dec 2009 11:23:06 -0000 We're having an issue with Passenger on FreeBSD where it will hang and stop processing any more requests the details are attach to the following bug report: http://code.google.com/p/phusion-passenger/issues/detail?id=318#c14 In addition the test suite crashes in what seems to be a very basic test, which I'm at a loss with. http://code.google.com/p/phusion-passenger/issues/detail?id=441 I'm thinking this may be a bugs in the FreeBSD either kernel or thread library as the crashes don't make any sense from the application side. Any advise on debugging or feedback on the stack traces would be much appreciated. Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 17 15:45:42 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0FDC3106568F; Thu, 17 Dec 2009 15:45:42 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id D47FA8FC08; Thu, 17 Dec 2009 15:45:41 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 7006A46B2A; Thu, 17 Dec 2009 10:45:41 -0500 (EST) Received: from jhbbsd.localnet (unknown [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPA id C967D8A01D; Thu, 17 Dec 2009 10:45:40 -0500 (EST) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Thu, 17 Dec 2009 09:08:49 -0500 User-Agent: KMail/1.12.1 (FreeBSD/7.2-CBSD-20091103; KDE/4.3.1; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200912170908.49119.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Thu, 17 Dec 2009 10:45:40 -0500 (EST) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: freebsd-stable@freebsd.org, Steven Hartland Subject: Re: Passenger hangs on live and SEGV on tests possible threading / kernel bug? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Dec 2009 15:45:42 -0000 On Thursday 17 December 2009 6:12:07 am Steven Hartland wrote: > We're having an issue with Passenger on FreeBSD where it will hang > and stop processing any more requests the details are attach to > the following bug report: > http://code.google.com/p/phusion-passenger/issues/detail?id=318#c14 > > In addition the test suite crashes in what seems to be a very > basic test, which I'm at a loss with. > http://code.google.com/p/phusion-passenger/issues/detail?id=441 > > I'm thinking this may be a bugs in the FreeBSD either kernel or > thread library as the crashes don't make any sense from the > application side. > > Any advise on debugging or feedback on the stack traces would > be much appreciated. For the hang it seems you have a thread waiting in a blocking read(), a thread waiting in a blocking accept(), and lots of threads creating condition variables. However, the pthread_cond_init() in libpthread (libthr on FreeBSD) doesn't call pthread_cleanup_push(), so your stack trace doesn't make sense to me. However, that may be gdb getting confused. The pthread_cleanup_push() frame may be cond_init(). However, it doesn't call umtx_op() (the _thr_umutex_init() call it makes just initializes the structure, it doesn't make a _umtx_op() system call). You might try posting on threads@ to try to get more info on this, but your pthread_cond_init() stack traces don't really make sense. Can you rebuild libc and libthr with debug symbols? For example: # cd /usr/src/lib/libc # make clean # make DEBUG_FLAGS=-g # make DEBUG_FLAGS=-g install However, if you are hanging in read(), that usually means you have a socket that just doesn't have data. That might be an application bug of some sort. The segv trace doesn't include the first part of GDB messages which show which thread actually had a seg fault. It looks like it was the thread that was throwing an exception. However, nanosleep() doesn't throw exceptions, so that stack trace doesn't really make sense either. Perhaps that stack is hosed by the exception handling code? -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 17 15:52:37 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7A2DA106566B; Thu, 17 Dec 2009 15:52:37 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.10]) by mx1.freebsd.org (Postfix) with ESMTP id 34B838FC1A; Thu, 17 Dec 2009 15:52:36 +0000 (UTC) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.3/8.14.3/NETPLEX) with ESMTP id nBHFqZqM001350; Thu, 17 Dec 2009 10:52:35 -0500 (EST) X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.2.2 (mail.netplex.net [204.213.176.10]); Thu, 17 Dec 2009 10:52:35 -0500 (EST) Date: Thu, 17 Dec 2009 10:52:35 -0500 (EST) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: John Baldwin In-Reply-To: <200912170908.49119.jhb@freebsd.org> Message-ID: References: <200912170908.49119.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org, Steven Hartland Subject: Re: Passenger hangs on live and SEGV on tests possible threading / kernel bug? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Dec 2009 15:52:37 -0000 On Thu, 17 Dec 2009, John Baldwin wrote: > On Thursday 17 December 2009 6:12:07 am Steven Hartland wrote: >> We're having an issue with Passenger on FreeBSD where it will hang >> and stop processing any more requests the details are attach to >> the following bug report: >> http://code.google.com/p/phusion-passenger/issues/detail?id=318#c14 >> >> In addition the test suite crashes in what seems to be a very >> basic test, which I'm at a loss with. >> http://code.google.com/p/phusion-passenger/issues/detail?id=441 >> >> I'm thinking this may be a bugs in the FreeBSD either kernel or >> thread library as the crashes don't make any sense from the >> application side. >> >> Any advise on debugging or feedback on the stack traces would >> be much appreciated. > > For the hang it seems you have a thread waiting in a blocking read(), a thread > waiting in a blocking accept(), and lots of threads creating condition > variables. However, the pthread_cond_init() in libpthread (libthr on FreeBSD) > doesn't call pthread_cleanup_push(), so your stack trace doesn't make sense to > me. However, that may be gdb getting confused. The pthread_cleanup_push() > frame may be cond_init(). However, it doesn't call umtx_op() (the > _thr_umutex_init() call it makes just initializes the structure, it doesn't > make a _umtx_op() system call). You might try posting on threads@ to try to > get more info on this, but your pthread_cond_init() stack traces don't really > make sense. Can you rebuild libc and libthr with debug symbols? Yes, good advice, I have noticed that you can't trust GDB stack traces unless libc and libthr have been built with debug (-g) enabled. -- DE From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 17 17:27:23 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 31483106568F; Thu, 17 Dec 2009 17:27:23 +0000 (UTC) (envelope-from prvs=1602d8d4d9=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id 24FDB8FC0A; Thu, 17 Dec 2009 17:27:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=multiplay.co.uk; s=Multiplay; t=1261070842; x=1261675642; q=dns/txt; h=Received: Message-ID:From:To:Cc:References:Subject:Date:MIME-Version: Content-Type:Content-Transfer-Encoding; bh=snWfwQUl0zIE3KIw6t8wO YMnSFn/Pa1QaX6QoeZpkug=; b=HHB7nXQlzzSsrcCvOJIZpM+o7wbC5Zst04gix i2ekluhHO+DesU70MbnRYCBXEdh0qTUEUELU62btxaV9ue73VuCymGFkgwlfYzUr 99So9q/1FWdrV+vglbwWsm6Fstno+ZeZol5M5AaOn+kTsoGeOH/XfDgOub3JJZWI J1n0Mk= X-MDAV-Processed: mail1.multiplay.co.uk, Thu, 17 Dec 2009 17:27:22 +0000 Received: from r2d2 by mail1.multiplay.co.uk (MDaemon PRO v10.0.4) with ESMTP id md50008880113.msg; Thu, 17 Dec 2009 17:27:20 +0000 X-Spam-Processed: mail1.multiplay.co.uk, Thu, 17 Dec 2009 17:27:20 +0000 (not processed: message from trusted or authenticated source) X-Authenticated-Sender: Killing@multiplay.co.uk X-MDRemoteIP: 213.123.247.160 X-Return-Path: prvs=1602d8d4d9=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk Message-ID: <28F90357192743E085ABEE7CD4C9FDF9@multiplay.co.uk> From: "Steven Hartland" To: "John Baldwin" , References: <200912170908.49119.jhb@freebsd.org> Date: Thu, 17 Dec 2009 17:27:17 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5843 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 Cc: freebsd-stable@freebsd.org Subject: Re: Passenger hangs on live and SEGV on tests possible threading / kernel bug? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Dec 2009 17:27:23 -0000 ----- Original Message ----- From: "John Baldwin" > For the hang it seems you have a thread waiting in a blocking read(), a thread > waiting in a blocking accept(), and lots of threads creating condition > variables. However, the pthread_cond_init() in libpthread (libthr on FreeBSD) > doesn't call pthread_cleanup_push(), so your stack trace doesn't make sense to > me. However, that may be gdb getting confused. The pthread_cleanup_push() > frame may be cond_init(). However, it doesn't call umtx_op() (the > _thr_umutex_init() call it makes just initializes the structure, it doesn't > make a _umtx_op() system call). You might try posting on threads@ to try to > get more info on this, but your pthread_cond_init() stack traces don't really > make sense. Can you rebuild libc and libthr with debug symbols? > > For example: > > # cd /usr/src/lib/libc > # make clean > # make DEBUG_FLAGS=-g > # make DEBUG_FLAGS=-g install > > However, if you are hanging in read(), that usually means you have a socket > that just doesn't have data. That might be an application bug of some sort. > > The segv trace doesn't include the first part of GDB messages which show which > thread actually had a seg fault. It looks like it was the thread that was > throwing an exception. However, nanosleep() doesn't throw exceptions, so that > stack trace doesn't really make sense either. Perhaps that stack is hosed by > the exception handling code? I've uploaded a two more traces for the oxt test failure / segv. http://code.google.com/p/phusion-passenger/issues/detail?id=441#c1 >From looking at the test case it testing the capture of failures and its ability to create a stack trace output so that may give others some indication where the issue may be? I will look to do the same on for the hang issue but that's on a live site so will need to schedule some downtime before I can get those rebuilt and then wait for it to hang again, which could be quite some time :( Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 17 18:25:39 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B4C6E1065692 for ; Thu, 17 Dec 2009 18:25:39 +0000 (UTC) (envelope-from linda.messerschmidt@gmail.com) Received: from mail-ew0-f226.google.com (mail-ew0-f226.google.com [209.85.219.226]) by mx1.freebsd.org (Postfix) with ESMTP id 026EA8FC14 for ; Thu, 17 Dec 2009 18:25:38 +0000 (UTC) Received: by ewy26 with SMTP id 26so1540550ewy.3 for ; Thu, 17 Dec 2009 10:25:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=UlMepzuBAdNEto6H+xVszD+eCAVLRyDFbwKgtadWBRo=; b=AOG3z6udk3gTpTE54mHKxBy7x8kkW/lPOBKMQMsyAPOM2/H/NKCkt7x4KJ+0XLTrme aXgK7D30qATE8sW7KGmGsLDAwjAEZbVIEQHW8qkI8//uvbaCH+2lQjLCNleYBzcoIxBa h6JVxDWaAP2YC9D3FYrsngUvTMMcblJCawu9I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=DHGHKdAWU0naWMc4dAk3+1wa2oXJGmx1xKb18+6OKOStXL1IPiD0xRy8cD+x3Ghv1v asJfjl5hQQYOHyLMSXIJztjQabXIqJMjtzK0gsn4B9rRKr6KO6f7MjZVWql50UHBJdgw whTnam9Qw6PbsHSc5L5gvi7xhtaWclKp0wzu4= MIME-Version: 1.0 Received: by 10.216.87.68 with SMTP id x46mr1057311wee.2.1261074337129; Thu, 17 Dec 2009 10:25:37 -0800 (PST) In-Reply-To: References: <237c27100912151140o1b227bb1pdaa65f5aee13ab5b@mail.gmail.com> Date: Thu, 17 Dec 2009 13:25:37 -0500 Message-ID: <237c27100912171025l3525da40m4abb526dd31ef067@mail.gmail.com> From: Linda Messerschmidt To: Robert Watson Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org Subject: Re: 8.0-RELEASE-p1 Panic "panic: sbdrop" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Dec 2009 18:25:39 -0000 On Wed, Dec 16, 2009 at 6:52 AM, Robert Watson wrote: > Could you tell us a bit more about the network configuration -- especiall= y, > are you using any tunneling software (such as ipsec), netgraph, or other > less commonly used network features? =A0Are you using accept filters? Let's see, we are using a couple of simple PF rdr rules in conjunction with squid and yes, we are using accf_http with it as well. Other than that, nothing uncommon. The ethernet is Intel onboard, em0 and em1. Web traffic comes in on em0, gets redirected to squid, and origin server requests go out on e1. It crashed under relatively light traffic, about 3000 requests per minute. Thanks! From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 17 18:38:43 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 87629106566B for ; Thu, 17 Dec 2009 18:38:43 +0000 (UTC) (envelope-from lars@e.0x20.net) Received: from mail.0x20.net (mail.0x20.net [217.69.67.217]) by mx1.freebsd.org (Postfix) with ESMTP id 496AF8FC19 for ; Thu, 17 Dec 2009 18:38:43 +0000 (UTC) Received: by mail.0x20.net (Postfix, from userid 1002) id B04E0398B3; Thu, 17 Dec 2009 19:19:56 +0100 (CET) Date: Thu, 17 Dec 2009 19:19:56 +0100 From: Lars Engels To: freebsd-hackers@freebsd.org Message-ID: <20091217181956.GA38107@e.0x20.net> References: <86zl5iufkd.fsf@bifteki.lan> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="sm4nu43k4a2Rpi4c" Content-Disposition: inline In-Reply-To: <86zl5iufkd.fsf@bifteki.lan> X-Editor: VIM - Vi IMproved 7.2 X-Operation-System: FreeBSD 5.5-RELEASE-p19 User-Agent: Mutt/1.5.20 (2009-06-14) X-Mailman-Approved-At: Thu, 17 Dec 2009 18:58:50 +0000 Subject: Re: pam_passwdqc update to latest vendor release X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Dec 2009 18:38:43 -0000 --sm4nu43k4a2Rpi4c Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Dec 17, 2009 at 11:15:30AM +0200, Leonidas Tsampros wrote: > Hello, >=20 > I read a mail on this list 3 or 4 weeks saying/stating that pam_passwdqc > was out of date. To update the module I used the vendor release 1.0.5 > which can be found here >=20 > http://www.openwall.com/pam/modules/pam_passwdqc/pam_passwdqc-1.0.5.tar.gz >=20 > The patch is available here: >=20 > http://bifteki.podzone.org/~ltsampros/pam_passwdc.diff >=20 > And a summary of the patch: >=20 > M contrib/pam_modules/pam_passwdqc/INTERNALS > M contrib/pam_modules/pam_passwdqc/LICENSE > M contrib/pam_modules/pam_passwdqc/Makefile > M contrib/pam_modules/pam_passwdqc/PLATFORMS > M contrib/pam_modules/pam_passwdqc/README > M contrib/pam_modules/pam_passwdqc/pam_macros.h > M contrib/pam_modules/pam_passwdqc/pam_passwdqc.c > A contrib/pam_modules/pam_passwdqc/pam_passwdqc.map > M contrib/pam_modules/pam_passwdqc/pam_passwdqc.spec > M contrib/pam_modules/pam_passwdqc/passwdqc.h > M contrib/pam_modules/pam_passwdqc/passwdqc_check.c > M contrib/pam_modules/pam_passwdqc/passwdqc_random.c > M lib/libpam/modules/pam_passwdqc/pam_passwdqc.8 >=20 > I built the updated module on my system. I did some testing with the > default options in /etc/pam.d/passwd and it seems to work okey. >=20 > Feedback is welcome. Thanks for updating pam_passwdqc. I couldn't find the time to update it myself. It works for me, though the patch doesn't apply cleanly: Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |diff --git a/lib/libpam/modules/pam_passwdqc/pam_passwdqc.8 b/lib/libpam/m= odules/pam_passwdqc/pam_passwdqc.8 |index 408f77d..8247652 100644 |--- a/lib/libpam/modules/pam_passwdqc/pam_passwdqc.8 |+++ b/lib/libpam/modules/pam_passwdqc/pam_passwdqc.8 -------------------------- Patching file lib/libpam/modules/pam_passwdqc/pam_passwdqc.8 using Plan A... Hunk #1 succeeded at 1. Hunk #2 failed at 32. Hunk #3 succeeded at 53. Hunk #4 succeeded at 67. Hunk #5 succeeded at 80. Hunk #6 succeeded at 98. Hunk #7 succeeded at 128. Hunk #8 succeeded at 144. Hunk #9 succeeded at 173. Hunk #10 succeeded at 191. Hunk #11 succeeded at 233. Hunk #12 succeeded at 257. 1 out of 12 hunks failed--saving rejects to lib/libpam/modules/pam_passwdqc= /pam_passwdqc.8.rej done Could someone commit this, please? Lars --sm4nu43k4a2Rpi4c Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAksqdkwACgkQKc512sD3afiXjQCgifv47Amz0mDgoSX2b3Q9Wm3k 0okAn0PNFbdqWnQSMf28DxstytMyW6JM =RinA -----END PGP SIGNATURE----- --sm4nu43k4a2Rpi4c-- From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 17 22:53:02 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3CC621065670 for ; Thu, 17 Dec 2009 22:53:02 +0000 (UTC) (envelope-from ltsampros@upnet.gr) Received: from kane.otenet.gr (kane.otenet.gr [83.235.67.31]) by mx1.freebsd.org (Postfix) with ESMTP id B473C8FC0A for ; Thu, 17 Dec 2009 22:53:01 +0000 (UTC) Received: from bifteki.lan (ppp-94-66-42-105.home.otenet.gr [94.66.42.105]) by kane.otenet.gr (8.13.8/8.13.8/Debian-3) with ESMTP id nBHMqxFe031527 for ; Fri, 18 Dec 2009 00:52:59 +0200 Received: from bifteki.lan (localhost [127.0.0.1]) by bifteki.lan (8.14.3/8.14.3) with ESMTP id nBHMqnhC050327 for ; Fri, 18 Dec 2009 00:52:49 +0200 (EET) (envelope-from ltsampros@bifteki.lan) Received: (from ltsampros@localhost) by bifteki.lan (8.14.3/8.14.3/Submit) id nBHMqnY0050326; Fri, 18 Dec 2009 00:52:49 +0200 (EET) (envelope-from ltsampros@bifteki.lan) From: Leonidas Tsampros To: freebsd-hackers@freebsd.org References: <86zl5iufkd.fsf@bifteki.lan> <20091217181956.GA38107@e.0x20.net> Mail-Followup-To: freebsd-hackers@freebsd.org Date: Fri, 18 Dec 2009 00:52:49 +0200 In-Reply-To: <20091217181956.GA38107@e.0x20.net> (Lars Engels's message of "Thu, 17 Dec 2009 19:19:56 +0100") Message-ID: <86vdg5ciwu.fsf@bifteki.lan> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.95 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: pam_passwdqc update to latest vendor release X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Dec 2009 22:53:02 -0000 Lars Engels writes: > On Thu, Dec 17, 2009 at 11:15:30AM +0200, Leonidas Tsampros wrote: >> Hello, >> >> I read a mail on this list 3 or 4 weeks saying/stating that pam_passwdqc >> was out of date. To update the module I used the vendor release 1.0.5 >> which can be found here >> >> http://www.openwall.com/pam/modules/pam_passwdqc/pam_passwdqc-1.0.5.tar.gz >> >> The patch is available here: >> >> http://bifteki.podzone.org/~ltsampros/pam_passwdc.diff >> >> And a summary of the patch: >> >> M contrib/pam_modules/pam_passwdqc/INTERNALS >> M contrib/pam_modules/pam_passwdqc/LICENSE >> M contrib/pam_modules/pam_passwdqc/Makefile >> M contrib/pam_modules/pam_passwdqc/PLATFORMS >> M contrib/pam_modules/pam_passwdqc/README >> M contrib/pam_modules/pam_passwdqc/pam_macros.h >> M contrib/pam_modules/pam_passwdqc/pam_passwdqc.c >> A contrib/pam_modules/pam_passwdqc/pam_passwdqc.map >> M contrib/pam_modules/pam_passwdqc/pam_passwdqc.spec >> M contrib/pam_modules/pam_passwdqc/passwdqc.h >> M contrib/pam_modules/pam_passwdqc/passwdqc_check.c >> M contrib/pam_modules/pam_passwdqc/passwdqc_random.c >> M lib/libpam/modules/pam_passwdqc/pam_passwdqc.8 >> >> I built the updated module on my system. I did some testing with the >> default options in /etc/pam.d/passwd and it seems to work okey. >> >> Feedback is welcome. > > > Thanks for updating pam_passwdqc. I couldn't find the time to update it > myself. > > It works for me, though the patch doesn't apply cleanly: > > Hmm... The next patch looks like a unified diff to me... > The text leading up to this was: > -------------------------- > |diff --git a/lib/libpam/modules/pam_passwdqc/pam_passwdqc.8 b/lib/libpam/modules/pam_passwdqc/pam_passwdqc.8 > |index 408f77d..8247652 100644 > |--- a/lib/libpam/modules/pam_passwdqc/pam_passwdqc.8 > |+++ b/lib/libpam/modules/pam_passwdqc/pam_passwdqc.8 > -------------------------- > Patching file lib/libpam/modules/pam_passwdqc/pam_passwdqc.8 using Plan A... > Hunk #1 succeeded at 1. > Hunk #2 failed at 32. > Hunk #3 succeeded at 53. > Hunk #4 succeeded at 67. > Hunk #5 succeeded at 80. > Hunk #6 succeeded at 98. > Hunk #7 succeeded at 128. > Hunk #8 succeeded at 144. > Hunk #9 succeeded at 173. > Hunk #10 succeeded at 191. > Hunk #11 succeeded at 233. > Hunk #12 succeeded at 257. > 1 out of 12 hunks failed--saving rejects to lib/libpam/modules/pam_passwdqc/pam_passwdqc.8.rej > done > You are right! I did my testing using a local clone from git://gitorious.org/freebsd/freebsd.git and the patch applied cleanly there. I broke up the patch in two files. You can find them here: http://bifteki.podzone.org/~ltsampros/pam_passwdqc.8.diff This is the patch for the man page under lib/libpam/modules/pam_passwdqc. It should apply cleanly now. http://bifteki.podzone.org/~ltsampros/pam_passwdqc.diff This is the patch for the module itself under contrib/pam_modules/pam_passwdqc. It should apply cleanly too using patch -p1. > > Could someone commit this, please? > > > Lars From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 18 17:29:41 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C55FC106566B for ; Fri, 18 Dec 2009 17:29:41 +0000 (UTC) (envelope-from rwatson@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 9DCEE8FC15 for ; Fri, 18 Dec 2009 17:29:41 +0000 (UTC) Received: from [192.168.2.102] (host86-146-40-97.range86-146.btcentralplus.com [86.146.40.97]) by cyrus.watson.org (Postfix) with ESMTPSA id C0DE446B03; Fri, 18 Dec 2009 12:29:40 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v1077) Content-Type: text/plain; charset=us-ascii From: "Robert N. M. Watson" In-Reply-To: <237c27100912171025l3525da40m4abb526dd31ef067@mail.gmail.com> Date: Fri, 18 Dec 2009 17:29:38 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: <9BE780E7-4114-43DF-BA5E-3517F2E28D21@freebsd.org> References: <237c27100912151140o1b227bb1pdaa65f5aee13ab5b@mail.gmail.com> <237c27100912171025l3525da40m4abb526dd31ef067@mail.gmail.com> To: Linda Messerschmidt X-Mailer: Apple Mail (2.1077) Cc: freebsd-hackers@freebsd.org Subject: Re: 8.0-RELEASE-p1 Panic "panic: sbdrop" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Dec 2009 17:29:41 -0000 On 17 Dec 2009, at 18:25, Linda Messerschmidt wrote: > On Wed, Dec 16, 2009 at 6:52 AM, Robert Watson = wrote: >> Could you tell us a bit more about the network configuration -- = especially, >> are you using any tunneling software (such as ipsec), netgraph, or = other >> less commonly used network features? Are you using accept filters? >=20 > Let's see, we are using a couple of simple PF rdr rules in conjunction > with squid and yes, we are using accf_http with it as well. Other > than that, nothing uncommon. >=20 > The ethernet is Intel onboard, em0 and em1. Web traffic comes in on > em0, gets redirected to squid, and origin server requests go out on > e1. It crashed under relatively light traffic, about 3000 requests > per minute. Is this something you might be able to reproduce on a non-production = system? Might you be able to test on 8.0 whether, without accf_http, the = problem goes away? (I'm not sure it makes life easier for you, but -- you should be able to = use an 8.0 kernel with a 7.x userspace, making the cost of rolling = forward/back to test things a bit easier perhaps) Thanks, Robert= From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 19 05:47:57 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 88F89106566B for ; Sat, 19 Dec 2009 05:47:56 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from mail-ew0-f226.google.com (mail-ew0-f226.google.com [209.85.219.226]) by mx1.freebsd.org (Postfix) with ESMTP id E39068FC08 for ; Sat, 19 Dec 2009 05:47:55 +0000 (UTC) Received: by ewy26 with SMTP id 26so3128453ewy.3 for ; Fri, 18 Dec 2009 21:47:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=ISR4WzYdSzuA2rnVVa3c/aumXAqb6Iejj6SV8+5V7Js=; b=INBtk8rFsMsQd+IXtW60w+Ol3XXGAp8knY57IteYdwEWhQpZngHFlx9MFMsXoGjBtC nGpxJ4VN1+8zdwxPU4z1KtsZBHlHdGC9YUOt7Ushqez5WZJ0Au2QlpGJEuZC0hFeqph4 jfzpDPsVRxVxZx3uT5x8AX/M3Ng00R5blssSA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=JPNAcsornuWtbTHcEiTvmDKQ9BMpPPMOIjxRtNQhyJ9d3OSl4lBNY56gwc8rbE41CG +6e6PJe7KnLze5VvWwy9xXtX7/DrEqhq1zNLnH6YAzj9l6oQlRMAfNQ8uoDnA10K8amC pBhXawBbE/xHmTww9JW9cwnADszjHLOIiHTqo= MIME-Version: 1.0 Received: by 10.216.90.18 with SMTP id d18mr1787571wef.225.1261201673089; Fri, 18 Dec 2009 21:47:53 -0800 (PST) Date: Sat, 19 Dec 2009 00:47:53 -0500 Message-ID: <5f67a8c40912182147t1adc158ew9fd3d94c4c4c955f@mail.gmail.com> From: Zaphod Beeblebrox To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: scp more perfectly fills the pipe than NFS/TCP X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Dec 2009 05:47:57 -0000 Here's an interesting conundrum. I don't know what's different between the TCP that scp uses from the TCP that NFS uses, but given the same two FreeBSD machines, SCP fills the pipe with packets better. Examine the following graphic: http://www.eicat.ca/~dgilbert/example-mrtg.png The system doing the scp and the NFS server is FreeBSD-7.2-p1. The system receiving the scp and the NFS client is FreeBSD-8.0-p1 The scp transfer is the left hand side of the graph and the NFS transfer is on the right. The NFS is mounted with "-3 -T -b -l -i" and no other options. Files are being moved over NFS with the system "mv" command. The files in each case are large (50 to 500 meg files). The connection is a DSL that terminates on the local lan near the server (I own and run the DSL and the ISP) In either case, the connection is lightly used by only me --- and I'm fairly certain that this isn't another network factor at play. From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 19 07:29:16 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9C6FE106566B for ; Sat, 19 Dec 2009 07:29:16 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: from mail-fx0-f227.google.com (mail-fx0-f227.google.com [209.85.220.227]) by mx1.freebsd.org (Postfix) with ESMTP id 432F38FC08 for ; Sat, 19 Dec 2009 07:29:15 +0000 (UTC) Received: by fxm27 with SMTP id 27so3456773fxm.3 for ; Fri, 18 Dec 2009 23:29:15 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.5.25 with SMTP id 25mr6448312fat.38.1261207755110; Fri, 18 Dec 2009 23:29:15 -0800 (PST) From: Vlad Galu Date: Sat, 19 Dec 2009 09:28:55 +0200 Message-ID: To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Small libstdc++ change required X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Dec 2009 07:29:16 -0000 Hi, as per http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36612, could one please apply the following patch? -- cut here -- --- /usr/include/c++/4.2/ext/pb_ds/exception.hpp 2008-04-05 14:15:32.000000000 +0300 +++ /mnt/store/jails/dudu/usr/include/c++/4.2/ext/pb_ds/exception.hpp 2009-12-19 05:07:55.000000000 +0200 @@ -71,35 +71,35 @@ struct resize_error : public container_error { }; #if __EXCEPTIONS - void + inline void __throw_container_error(void) { throw container_error(); } - void + inline void __throw_insert_error(void) { throw insert_error(); } - void + inline void __throw_join_error(void) { throw join_error(); } - void + inline void __throw_resize_error(void) { throw resize_error(); } #else - void + inline void __throw_container_error(void) { std::abort(); } - void + inline void __throw_insert_error(void) { std::abort(); } - void + inline void __throw_join_error(void) { std::abort(); } - void + inline void __throw_resize_error(void) { std::abort(); } #endif -- and here -- Thanks, Vlad From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 19 08:43:07 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8B54D1065670 for ; Sat, 19 Dec 2009 08:43:07 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from vlakno.cz (77-93-215-190.static.masterinter.net [77.93.215.190]) by mx1.freebsd.org (Postfix) with ESMTP id 46F528FC19 for ; Sat, 19 Dec 2009 08:43:06 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id 75CD49CB0C7; Sat, 19 Dec 2009 09:40:55 +0100 (CET) X-Virus-Scanned: amavisd-new at vlakno.cz Received: from vlakno.cz ([127.0.0.1]) by localhost (lev.vlakno.cz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u7TxMiG7RiQQ; Sat, 19 Dec 2009 09:40:53 +0100 (CET) Received: from vlk.vlakno.cz (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id 084B59CB0F7; Sat, 19 Dec 2009 09:40:53 +0100 (CET) Received: (from rdivacky@localhost) by vlk.vlakno.cz (8.14.3/8.14.3/Submit) id nBJ8eqlq028929; Sat, 19 Dec 2009 09:40:52 +0100 (CET) (envelope-from rdivacky) Date: Sat, 19 Dec 2009 09:40:52 +0100 From: Roman Divacky To: Vlad Galu Message-ID: <20091219084052.GA28763@freebsd.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-hackers@freebsd.org Subject: Re: Small libstdc++ change required X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Dec 2009 08:43:07 -0000 On Sat, Dec 19, 2009 at 09:28:55AM +0200, Vlad Galu wrote: > Hi, > > as per http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36612, could one > please apply the following patch? the patch in question seems to be GPLv3, we cant apply it then... From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 19 08:47:07 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C77231065676 for ; Sat, 19 Dec 2009 08:47:07 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: from mail-fx0-f227.google.com (mail-fx0-f227.google.com [209.85.220.227]) by mx1.freebsd.org (Postfix) with ESMTP id 4485B8FC1B for ; Sat, 19 Dec 2009 08:47:06 +0000 (UTC) Received: by fxm27 with SMTP id 27so3478613fxm.3 for ; Sat, 19 Dec 2009 00:47:06 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.54.15 with SMTP id o15mr5995731fag.96.1261212426143; Sat, 19 Dec 2009 00:47:06 -0800 (PST) In-Reply-To: <20091219084052.GA28763@freebsd.org> References: <20091219084052.GA28763@freebsd.org> From: Vlad Galu Date: Sat, 19 Dec 2009 10:46:46 +0200 Message-ID: To: Roman Divacky Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-hackers@freebsd.org Subject: Re: Small libstdc++ change required X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Dec 2009 08:47:07 -0000 On Sat, Dec 19, 2009 at 10:40 AM, Roman Divacky wrote: > On Sat, Dec 19, 2009 at 09:28:55AM +0200, Vlad Galu wrote: >> Hi, >> >> as per http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36612, could one >> please apply the following patch? > > the patch in question seems to be GPLv3, we cant apply it then... > Actually, I only followed their suggestion and made the patch myself. Ofc, it most likely looks like their does. It's not theirs, though. Could this work out?