From owner-freebsd-stable@FreeBSD.ORG Sun May 11 10:45:30 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B87931065671; Sun, 11 May 2008 10:45:30 +0000 (UTC) (envelope-from joe@tao.org.uk) Received: from mailhost.tao.org.uk (tao.uscs.susx.ac.uk [139.184.131.101]) by mx1.freebsd.org (Postfix) with ESMTP id 7FAFE8FC1A; Sun, 11 May 2008 10:45:30 +0000 (UTC) (envelope-from joe@tao.org.uk) Received: from [10.48.48.149] (nat65.mia.three.co.uk [217.171.129.65]) (Authenticated sender: joemail@transwarp.tao.org.uk) by mailhost.tao.org.uk (Postfix) with ESMTP id DBD0A600F; Sun, 11 May 2008 11:27:30 +0100 (BST) Date: Sun, 11 May 2008 00:43:24 +0100 From: "Dr Joe Karthauser" To: roberto@keltia.freenix.fr MIME-Version: 1.0 X-Mailer: Lonely Cat Games ProfiMail In-Reply-To: <20080508073540.GA95771@keltia.freenix.fr> Content-Type: text/plain; charset=iso-8859-1 Message-Id: <20080511102730.DBD0A600F@mailhost.tao.org.uk> X-Mailman-Approved-At: Sun, 11 May 2008 11:16:13 +0000 Cc: freebsd-hubs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: cvsup.uk.FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 May 2008 10:45:30 -0000 ------- Original message ------- From: Ollivier Robert Cc: freebsd-hubs@freebsd.org Sent: 8.5.'08, 8:35 > Stefan Lambrev disait : > > cvsup.uk.FreeBSD.org is outdated. > > I know this is not the proper list, but which one is? > > freebsd-hubs is, redirected. > > I've noticed that recently but I should have send a mail about it, sorry. > -- > Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr > Darwin sidhe.keltia.net Version 9.2.0: Tue Feb 5 16:13:22 PST 2008; i386 > Hey guys. I have reclassified this faulty mirror as cvsup1 and made cvsup a cname to cvsup3, which is the most recent addition and best hardware available. In the future we will always point to the most available machine in this way. Joe From owner-freebsd-stable@FreeBSD.ORG Sun May 11 12:51:01 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 654DC106567E for ; Sun, 11 May 2008 12:51:01 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by mx1.freebsd.org (Postfix) with ESMTP id 3B2428FC18 for ; Sun, 11 May 2008 12:51:01 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 4649C109000 for ; Sun, 11 May 2008 08:34:19 -0400 (EDT) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Sun, 11 May 2008 08:34:19 -0400 X-Sasl-enc: X3aGeAn1UwcJ+RLWhFZa7wwP+Foov+pUPtav2lEx/pkq 1210509258 Received: from empiric.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTPSA id 97C8C2A4A6 for ; Sun, 11 May 2008 08:34:18 -0400 (EDT) Message-ID: <4826E7C9.9030407@incunabulum.net> Date: Sun, 11 May 2008 13:34:17 +0100 From: Bruce M Simpson User-Agent: Thunderbird 2.0.0.12 (X11/20080423) MIME-Version: 1.0 To: FreeBSD stable X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Automounting USB sticks - questions X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 May 2008 12:51:01 -0000 I got this working quite easily with the amd daemon. Thanks to Alfred for your excellent work on this. I wonder what the status of autofs is? It would be great if we could ship FreeBSD out of the box, ready to automount removable media. This would be useful to all users, but particularly for novices and people who just wanna get on and use the beast. Since the move to /media for a place to put removable mount points I'd imagine all of this gets a lot easier. However I can understand there are real issues with this: * /etc/amd.conf. We don't ship one in /etc by default. Maybe we should? * /etc/amd.map. We ship one which contains defaults and nothing more. Perhaps commented out examples? * There doesn't appear to be a tool to tell amd about new maps at runtime. Is there such a beast? UPDATE: I just read code, and it seems SIGHUP can be sent, but this isn't in the man page and I haven't tried it. * devd doesn't have any hooks into GEOM, which makes it difficult to generate mount lines without retroactively parsing dmesg output. devd as I understand it sits on top of NEWBUS. Is there any way I can get a list of the disk devices, from userland, in the default install, which correspond to a given NEWBUS device? * I wonder if there's any way we can get a notification about media being inserted into a CDROM drive, without polling it? I had a brief discussion online with phk@ about doing dynamic mounts, and it seems that there are still problems dealing with blowing away mounts when the device goes away. From owner-freebsd-stable@FreeBSD.ORG Sun May 11 12:56:08 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5B6B61065676 for ; Sun, 11 May 2008 12:56:08 +0000 (UTC) (envelope-from ericlin@tamama.org) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.234]) by mx1.freebsd.org (Postfix) with ESMTP id 3EC9B8FC0A for ; Sun, 11 May 2008 12:56:08 +0000 (UTC) (envelope-from ericlin@tamama.org) Received: by rv-out-0506.google.com with SMTP id b25so3209237rvf.43 for ; Sun, 11 May 2008 05:56:08 -0700 (PDT) Received: by 10.141.15.19 with SMTP id s19mr3156632rvi.75.1210508916805; Sun, 11 May 2008 05:28:36 -0700 (PDT) Received: by 10.141.152.4 with HTTP; Sun, 11 May 2008 05:28:36 -0700 (PDT) Message-ID: <47713ee10805110528s1d2152cby3099d4ceda15864a@mail.gmail.com> Date: Sun, 11 May 2008 20:28:36 +0800 From: "Lin Jui-Nan Eric" To: stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: TMPFS does not support unix socket file? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 May 2008 12:56:08 -0000 Hi, I am trying to replace my /tmp to TMPFS. Everything is fine, but I found that MySQL does not run. The error log shows that it cannot bind /tmp/mysql.sock. Does TMPFS support unix socket file? From owner-freebsd-stable@FreeBSD.ORG Sun May 11 14:28:39 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9172F1065678 for ; Sun, 11 May 2008 14:28:39 +0000 (UTC) (envelope-from aragon@phat.za.net) Received: from mail.geek.sh (decoder.geek.sh [196.36.198.81]) by mx1.freebsd.org (Postfix) with ESMTP id 360708FC16 for ; Sun, 11 May 2008 14:28:39 +0000 (UTC) (envelope-from aragon@phat.za.net) Received: by mail.geek.sh (Postfix, from userid 1000) id 1D70624D26; Sun, 11 May 2008 16:00:22 +0200 (SAST) Date: Sun, 11 May 2008 16:00:22 +0200 From: Aragon Gouveia To: freebsd-stable@freebsd.org Message-ID: <20080511140022.GA6067@phat.za.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i X-Operating-System: FreeBSD 4.10-RELEASE-p2 i386 Subject: sound hosed on 7.0-STABLE/amd64 ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 May 2008 14:28:39 -0000 Hi, I'm running an amd64 install of 7.0-STABLE. Sound is behaving strangely. I'm trying to get either uaudio or snd_hda working, but am not having joy with either. The kernel detects the devices, but /dev/dsp* entries aren't created or take a long time to appear. And, of course, sound playback doesn't work either. Kernel output attached. Anyone know what could be up? Thanks, Aragon May 11 15:31:49 igor kernel: uaudio0: on uhub4 May 11 15:31:49 igor kernel: uaudio0: audio rev 1.00 May 11 15:31:49 igor kernel: pcm0: on uaudio0 May 11 15:49:09 igor kernel: pcm1: mem 0xe0320000-0xe0323fff irq 22 at device 27.0 on pci0 May 11 15:49:09 igor kernel: pcm1: [ITHREAD] May 11 15:49:09 igor kernel: pcm1: May 11 15:49:09 igor kernel: pcm1: May 11 15:49:09 igor kernel: pcm2: mem 0xe0210000-0xe0213fff irq 17 at device 0.1 on pci1 May 11 15:49:09 igor kernel: pcm2: [ITHREAD] May 11 15:49:09 igor kernel: pcm2: May 11 15:49:09 igor kernel: pcm2: From owner-freebsd-stable@FreeBSD.ORG Sun May 11 17:18:20 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 443981065671 for ; Sun, 11 May 2008 17:18:20 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.156]) by mx1.freebsd.org (Postfix) with ESMTP id C7AC48FC18 for ; Sun, 11 May 2008 17:18:19 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: by fg-out-1718.google.com with SMTP id l26so3798534fgb.35 for ; Sun, 11 May 2008 10:18:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=XX/USc1j7Zz1ihAQqLfSnblpVX1mJ2lsGYxDSFhZvqc=; b=tzzudfS65zzRZLzJp6dPdkft0OaN7lVKOW1iuPQxmONflThA+zO/xBFAKr1Mqi1RcTpyhX/q1/XBrunxWtE+TL9NQKM7lOZo7WnGBLZRXyRik0o2EhEQ+6E+LR/EpJG93uIgSn4bcHSkQINJ/CcRkYgz/DyTFshSXou4Le+rQkc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ZSzeTW6KN7hW/v7vg9RINX0vGtjs1Gz0OIwIvJjMFDszWup1YYOe5Ih9GrN1mBqadOer3Llz5KDpCg/4Lf57hWWSIeudwrCJ+Y7f/2p8DOvWSGRIeP6G4QWjt4j4yU4VumeXev4BDxsb3MRIcwVxpRL9AjZHCh+tYn0cCloziIA= Received: by 10.78.150.7 with SMTP id x7mr1705639hud.107.1210526297999; Sun, 11 May 2008 10:18:17 -0700 (PDT) Received: by 10.78.16.10 with HTTP; Sun, 11 May 2008 10:18:17 -0700 (PDT) Message-ID: Date: Sun, 11 May 2008 21:18:17 +0400 From: pluknet To: "Lin Jui-Nan Eric" In-Reply-To: <47713ee10805110528s1d2152cby3099d4ceda15864a@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <47713ee10805110528s1d2152cby3099d4ceda15864a@mail.gmail.com> Cc: stable@freebsd.org Subject: Re: TMPFS does not support unix socket file? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 May 2008 17:18:20 -0000 2008/5/11 Lin Jui-Nan Eric : > Hi, > > I am trying to replace my /tmp to TMPFS. > Everything is fine, but I found that MySQL does not run. The error log > shows that it cannot bind /tmp/mysql.sock. > Does TMPFS support unix socket file? I've just checked tmpfs with unix with simple test case on my stable and it works. maybe permissions issue? wbr, pluknet From owner-freebsd-stable@FreeBSD.ORG Sun May 11 17:27:05 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 47CEB106564A for ; Sun, 11 May 2008 17:27:05 +0000 (UTC) (envelope-from ericlin@tamama.org) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.233]) by mx1.freebsd.org (Postfix) with ESMTP id 2AE6C8FC0C for ; Sun, 11 May 2008 17:27:04 +0000 (UTC) (envelope-from ericlin@tamama.org) Received: by rv-out-0506.google.com with SMTP id b25so3267689rvf.43 for ; Sun, 11 May 2008 10:27:04 -0700 (PDT) Received: by 10.140.126.10 with SMTP id y10mr3251113rvc.214.1210526824542; Sun, 11 May 2008 10:27:04 -0700 (PDT) Received: by 10.141.152.4 with HTTP; Sun, 11 May 2008 10:27:04 -0700 (PDT) Message-ID: <47713ee10805111027h256286det6d20efcf78bf6e0c@mail.gmail.com> Date: Mon, 12 May 2008 01:27:04 +0800 From: "Lin Jui-Nan Eric" To: stable@freebsd.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <47713ee10805110528s1d2152cby3099d4ceda15864a@mail.gmail.com> Cc: Subject: Re: TMPFS does not support unix socket file? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 May 2008 17:27:05 -0000 On Mon, May 12, 2008 at 1:18 AM, pluknet wrote: > 2008/5/11 Lin Jui-Nan Eric : >> Hi, >> >> I am trying to replace my /tmp to TMPFS. >> Everything is fine, but I found that MySQL does not run. The error log >> shows that it cannot bind /tmp/mysql.sock. >> Does TMPFS support unix socket file? > > I've just checked tmpfs with unix with simple test case on my stable > and it works. > maybe permissions issue? It's a permission issue! Thank you very much. From owner-freebsd-stable@FreeBSD.ORG Sun May 11 18:30:29 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DD1B3106564A for ; Sun, 11 May 2008 18:30:29 +0000 (UTC) (envelope-from aragon@phat.za.net) Received: from mail.geek.sh (decoder.geek.sh [196.36.198.81]) by mx1.freebsd.org (Postfix) with ESMTP id 77E9F8FC13 for ; Sun, 11 May 2008 18:30:29 +0000 (UTC) (envelope-from aragon@phat.za.net) Received: by mail.geek.sh (Postfix, from userid 1000) id 3191E24D22; Sun, 11 May 2008 20:30:28 +0200 (SAST) Date: Sun, 11 May 2008 20:30:28 +0200 From: Aragon Gouveia To: freebsd-stable@freebsd.org Message-ID: <20080511183028.GA24596@phat.za.net> References: <20080511140022.GA6067@phat.za.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080511140022.GA6067@phat.za.net> User-Agent: Mutt/1.4i X-Operating-System: FreeBSD 4.10-RELEASE-p2 i386 Subject: Re: sound hosed on 7.0-STABLE/amd64 ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 May 2008 18:30:30 -0000 Hi again, I guess I should have spent more time troubleshooting. Sound is working now. I spent the last 30 minutes testing it with 6.3-RELEASE and 7.0-RELEASE livecds on two different machines. Ended up tracing my uaudio dysfunctionality to a dodgy USB hub! Onboard HDA was just a matter of setting the right options in the BIOS. All's good on both fronts. Sorry for the false alarm. Regards, Aragon | By Aragon Gouveia | [ 2008-05-11 16:29 +0200 ] > Hi, > > I'm running an amd64 install of 7.0-STABLE. Sound is behaving strangely. > I'm trying to get either uaudio or snd_hda working, but am not having joy > with either. The kernel detects the devices, but /dev/dsp* entries aren't > created or take a long time to appear. And, of course, sound playback > doesn't work either. > > Kernel output attached. Anyone know what could be up? > > > Thanks, > Aragon > > > May 11 15:31:49 igor kernel: uaudio0: on uhub4 > May 11 15:31:49 igor kernel: uaudio0: audio rev 1.00 > May 11 15:31:49 igor kernel: pcm0: on uaudio0 > May 11 15:49:09 igor kernel: pcm1: mem 0xe0320000-0xe0323fff irq 22 at device 27.0 on pci0 > May 11 15:49:09 igor kernel: pcm1: [ITHREAD] > May 11 15:49:09 igor kernel: pcm1: > May 11 15:49:09 igor kernel: pcm1: > May 11 15:49:09 igor kernel: pcm2: mem 0xe0210000-0xe0213fff irq 17 at device 0.1 on pci1 > May 11 15:49:09 igor kernel: pcm2: [ITHREAD] > May 11 15:49:09 igor kernel: pcm2: > May 11 15:49:09 igor kernel: pcm2: > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Sun May 11 20:10:43 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 19437106566C for ; Sun, 11 May 2008 20:10:43 +0000 (UTC) (envelope-from jhary@unsane.co.uk) Received: from unsane.co.uk (unsane-pt.tunnel.tserv5.lon1.ipv6.he.net [IPv6:2001:470:1f08:110::2]) by mx1.freebsd.org (Postfix) with ESMTP id 760DC8FC16 for ; Sun, 11 May 2008 20:10:42 +0000 (UTC) (envelope-from jhary@unsane.co.uk) Received: from crab.unsane.co.uk (crab.unsane.co.uk [10.0.0.111]) (authenticated bits=0) by unsane.co.uk (8.14.0/8.14.0) with ESMTP id m4BKAdko021891 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 11 May 2008 21:10:39 +0100 (BST) (envelope-from jhary@unsane.co.uk) Message-ID: <482752C0.8040401@unsane.co.uk> Date: Sun, 11 May 2008 21:10:40 +0100 From: Vince Hoffman User-Agent: Thunderbird 2.0.0.14 (X11/20080507) MIME-Version: 1.0 To: Bruce M Simpson References: <4826E7C9.9030407@incunabulum.net> In-Reply-To: <4826E7C9.9030407@incunabulum.net> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD stable Subject: Re: Automounting USB sticks - questions X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 May 2008 20:10:43 -0000 Bruce M Simpson wrote: > I got this working quite easily with the amd daemon. > Thanks to Alfred for your excellent work on this. I wonder what the > status of autofs is? > > It would be great if we could ship FreeBSD out of the box, ready to > automount removable media. This would be useful to all users, but > particularly for novices and people who just wanna get on and use the > beast. > > Since the move to /media for a place to put removable mount points I'd > imagine all of this gets a lot easier. > > However I can understand there are real issues with this: > > * /etc/amd.conf. We don't ship one in /etc by default. Maybe we should? > Speaking as someone who's never looked at amd before last week, this would be great, or at least in /usr/share/examples/etc. > * /etc/amd.map. We ship one which contains defaults and nothing more. > Perhaps commented out examples? > Again I'd find that helpful. I spent 5 or 10 minutes looking into setting up amd (Hardly indepth I know) and gave up because at the moment its easier to manually mount my devices ;) > * There doesn't appear to be a tool to tell amd about new maps at > runtime. Is there such a beast? > UPDATE: I just read code, and it seems SIGHUP can be sent, but this > isn't in the man page and I haven't tried it. > > * devd doesn't have any hooks into GEOM, which makes it difficult to > generate mount lines without retroactively parsing dmesg output. devd as > I understand it sits on top of NEWBUS. > Is there any way I can get a list of the disk devices, from userland, > in the default install, which correspond to a given NEWBUS device? > > * I wonder if there's any way we can get a notification about media > being inserted into a CDROM drive, without polling it? > > I had a brief discussion online with phk@ about doing dynamic mounts, > and it seems that there are still problems dealing with blowing away > mounts when the device goes away. > > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Mon May 12 01:23:53 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BB6321065675 for ; Mon, 12 May 2008 01:23:53 +0000 (UTC) (envelope-from jonathan@kc8onw.net) Received: from mail-out2.fuse.net (mail-out2.fuse.net [216.68.8.171]) by mx1.freebsd.org (Postfix) with ESMTP id 854708FC1B for ; Mon, 12 May 2008 01:23:53 +0000 (UTC) (envelope-from jonathan@kc8onw.net) X-CNFS-Analysis: v=1.0 c=1 a=qqrJ4_xcy9sA:15 a=dNULd-1nqGgA:10 a=xUvkYoQocQKi/8Los98NoQ==:17 a=6I5d2MoRAAAA:8 a=TnVG3v8EnmgfZSURnnEA:9 a=BdkqC3hdzIfyBDrT54kA:7 a=90tnaLcJUA7RBrQDEt27uzren2UA:4 a=2uiCRmbCp6AA:10 X-CM-Score: 0 X-Scanned-by: Cloudmark Authority Engine Received: from [208.102.162.227] ([208.102.162.227:50284] helo=mail.kc8onw.net) by mail-out2.fuse.net (ecelerity 2.1.1.22 r(17669)) with ESMTP id 7F/DA-01376-3A897284 for ; Sun, 11 May 2008 21:08:51 -0400 Received: from www.kc8onw.net (localhost [127.0.0.1]) by mail.kc8onw.net (Postfix) with ESMTP id 8F83E2842A; Sun, 11 May 2008 21:08:51 -0400 (EDT) Received: from 214.13.212.30 (SquirrelMail authenticated user jonathan) by www.kc8onw.net with HTTP; Sun, 11 May 2008 21:08:51 -0400 (EDT) Message-ID: <29626.214.13.212.30.1210554531.squirrel@www.kc8onw.net> Date: Sun, 11 May 2008 21:08:51 -0400 (EDT) From: jonathan@kc8onw.net To: stable@freebsd.org User-Agent: SquirrelMail/1.5.1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: sos@FreeBSD.org Subject: ATA APM and NCQ support in FreeBSD atacontrol X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2008 01:23:53 -0000 Has any work been done recently towards adding SATA Native Command Queueing as well as ATA APM and acoustic management to FreeBSD? I found this PR (with patch) to add APM and acoustic management control to atacontrol. The PR was opened in May 2005 has not been changed since December 2006 and is still open. http://www.freebsd.org/cgi/query-pr.cgi?pr=81692&cat= I have not been able to find much of anything on SATA NCQ in FreeBSD newer than 2005 or 2006 does anyone know anything newer? Thanks, Jonathan Stewart From owner-freebsd-stable@FreeBSD.ORG Mon May 12 03:06:47 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7B3351065670 for ; Mon, 12 May 2008 03:06:47 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 65C8D8FC21 for ; Mon, 12 May 2008 03:06:47 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 531641CC033; Sun, 11 May 2008 20:06:47 -0700 (PDT) Date: Sun, 11 May 2008 20:06:47 -0700 From: Jeremy Chadwick To: jonathan@kc8onw.net Message-ID: <20080512030647.GA93725@eos.sc1.parodius.com> References: <29626.214.13.212.30.1210554531.squirrel@www.kc8onw.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <29626.214.13.212.30.1210554531.squirrel@www.kc8onw.net> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: stable@freebsd.org, sos@FreeBSD.org Subject: Re: ATA APM and NCQ support in FreeBSD atacontrol X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2008 03:06:47 -0000 On Sun, May 11, 2008 at 09:08:51PM -0400, jonathan@kc8onw.net wrote: > Has any work been done recently towards adding SATA Native Command > Queueing as well as ATA APM and acoustic management to FreeBSD? > > I found this PR (with patch) to add APM and acoustic management control to > atacontrol. The PR was opened in May 2005 has not been changed since > December 2006 and is still open. > http://www.freebsd.org/cgi/query-pr.cgi?pr=81692&cat= > > I have not been able to find much of anything on SATA NCQ in FreeBSD newer > than 2005 or 2006 does anyone know anything newer? I believe NCQ is supported, assuming that your controller is operating in AHCI mode and your disk supports NCQ. This mainly applies to Intel ICHx controllers, but there are others which support it as well. There's also NCQ support in non-AHCI drivers like hptmv(4), rr232x(4), hptrr(4), and mpt(4) with SATA disks. I do see some code that explicitly disables NCQ on some nVidia chipsets, and I believe that's because the NCQ details for the nF4 chipset are unavailable; possibly Linux has them. atacontrol, on the other hand, I believe always spits out "-" as to whether or not it's enabled. I'd have to go look at the code to be sure, but I'm guessing it just says "-" no matter what. An example: Feature Support Enable Value Vendor write cache yes yes read ahead yes yes Native Command Queuing (NCQ) yes - 31/0x1F Tagged Command Queuing (TCQ) no no 31/0x1F SMART yes yes microcode download yes yes security yes no power management yes yes advanced power management no no 0/0x00 automatic acoustic management yes no 254/0xFE 128/0x80 Finally, I read a while back that NCQ on SATA does not provide a substantial improvement in overall disk I/O or under heavy load. It's not entirely marketing hype, but the benefits are like 3-4%, with added CPU utilisation. SATA TCQ is a different matter. SCSI uses TCQ, and as we all know, it works beautifully. SATA TCQ has a significantly larger queue depth than SATA NCQ (2^64 vs. 31). -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Mon May 12 04:46:25 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C88EE1065676 for ; Mon, 12 May 2008 04:46:25 +0000 (UTC) (envelope-from dikshie@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.170]) by mx1.freebsd.org (Postfix) with ESMTP id 9CF128FC0A for ; Mon, 12 May 2008 04:46:25 +0000 (UTC) (envelope-from dikshie@gmail.com) Received: by wf-out-1314.google.com with SMTP id 28so2082988wfa.7 for ; Sun, 11 May 2008 21:46:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; bh=GZqCU71n7dwaGOIWHT4cwIRxJJAq36b1bL8evqs9km8=; b=FsIP958gp3uXvv0NFjOa6PHeMlPNI2z5EvFEb98VmBZ/l916QNVzISYJo67b56oZROA7HxoZUvJIsAif5VQBySjaim6cR9C4t6oGjZOVf6Bpl0Lwv9f+DRsn5auEETkkS7TKDHm+7H19WXGHO0VyPBV607qXzn7KYZCNmSz1hJI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=uYJUgj59T2fNt8L9T0blUZLZj2m7s43FH9tERQO2RUZtJav8X64oPWkTXqB3fxQWN5nuJ3LUQRLALwugBI9C/AmPhDldYKxCmag0qoqOMU1S5/PyjldanGa7+6d2K3wMx0hQToRKuyzjcARNlZZPw+iF5sdyvvXjg41v2CRBg+4= Received: by 10.142.178.13 with SMTP id a13mr3067114wff.146.1210565836489; Sun, 11 May 2008 21:17:16 -0700 (PDT) Received: by 10.143.123.5 with HTTP; Sun, 11 May 2008 21:17:16 -0700 (PDT) Message-ID: <910e60e80805112117j1ecb83b4s4cdb62eafbdf748f@mail.gmail.com> Date: Mon, 12 May 2008 13:17:16 +0900 From: dikshie To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: any available patches for sata: "ad4: warning - setfeatures set transfer mode taskqueue timeout - completing request directly" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2008 04:46:25 -0000 Hi, I got : -------------------------------- ad4: warning - setfeatures set transfer mode taskqueue timeout - completing request directly ad4: warning - setfeatures enable rcache taskqueue timeout - completing request directly ad4: warning - setfeatures enable wcache taskqueue timeout - completing request directly ad4: timeout - flushcache retrying (0 retries left) geom_journal: flush cache of ad4s1d: error=5 ad4: timeout - write_dma retrying (1 retry left) LBA=4139103 ------------------------------- I read: http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues and strange output from dmesg: ad4: 305245MB at ata2-master UDMA33 ^^^^^^^^^^^ any available patches ? best regards, -dikshie- -------------------------------- Copyright (c) 1992-2008 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.0-STABLE #19: Sat May 10 15:41:00 JST 2008 dikshie@dhcp-143-221.sfc.wide.ad.jp:/usr/obj/usr/src/sys/BARU Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz (2333.34-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x6fb Stepping = 11 Features=0xbfebfbff Features2=0xe3fd AMD Features=0x20100800 AMD Features2=0x1 Cores per package: 2 usable memory = 2000646144 (1907 MB) avail memory = 1926553600 (1837 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ACPI Warning (tbfadt-0505): Optional field "Pm2ControlBlock" has zero address or length: 0 0/1 [20070320] ioapic0: Changing APIC ID to 4 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 cryptosoft0: on motherboard acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 100000, 7fdf0000 (3) failed acpi0: reservation of 0, a0000 (3) failed Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 acpi_hpet0: iomem 0xfeff0000-0xfeff03ff on acpi0 Timecounter "HPET" frequency 25000000 Hz quality 900 cpu0: on acpi0 est0: on cpu0 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 72a072a0600072a device_attach: est0 attach returned 6 p4tcc0: on cpu0 cpu1: on acpi0 est1: on cpu1 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 72a072a0600072a device_attach: est1 attach returned 6 p4tcc1: on cpu1 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: at device 0.1 (no driver attached) pci0: at device 1.0 (no driver attached) pci0: at device 1.1 (no driver attached) pci0: at device 1.2 (no driver attached) pci0: at device 1.3 (no driver attached) pci0: at device 1.4 (no driver attached) pci0: at device 1.5 (no driver attached) pci0: at device 1.6 (no driver attached) pci0: at device 2.0 (no driver attached) isab0: at device 3.0 on pci0 isa0: on isab0 pci0: at device 3.1 (no driver attached) pci0: at device 3.2 (no driver attached) pci0: at device 3.4 (no driver attached) ohci0: mem 0xeffff000-0xefffffff irq 21 at device 4.0 on pci0 ohci0: [GIANT-LOCKED] ohci0: [ITHREAD] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 10 ports with 10 removable, self powered ehci0: mem 0xefffe000-0xefffe0ff irq 22 at device 4.1 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb1: EHCI version 1.0 usb1: companion controller, 10 ports each: usb0 usb1: on ehci0 usb1: USB revision 2.0 uhub1: on usb1 uhub1: 10 ports with 10 removable, self powered umass0: on uhub1 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 8.0 on pci0 ata0: on atapci0 ata0: [ITHREAD] ata1: on atapci0 ata1: [ITHREAD] pci0: at device 9.0 (no driver attached) pcib1: at device 10.0 on pci0 pci1: on pcib1 pcib2: at device 11.0 on pci0 pci2: on pcib2 pcib3: at device 12.0 on pci0 pci3: on pcib3 pcib4: at device 13.0 on pci0 pci4: on pcib4 re0: port 0xde00-0xdeff mem 0xefdff000-0xefdfffff irq 16 at device 0.0 on pci4 miibus0: on re0 rgephy0: PHY 1 on miibus0 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto re0: Ethernet address: 00:e0:4d:66:7a:72 re0: [FILTER] atapci1: port 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xf700-0xf70f mem 0xefff8000-0xefff9fff irq 20 at device 14.0 on pci0 atapci1: [ITHREAD] ata2: on atapci1 ata2: [ITHREAD] ata3: on atapci1 ata3: [ITHREAD] vgapci0: mem 0xed000000-0xedffffff,0xd0000000-0xdfffffff,0xee000000-0xeeffffff irq 21 at device 16.0 on pci0 acpi_tz0: on acpi0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio0: [FILTER] ppc0: port 0x378-0x37f,0x778-0x77b irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold ppbus0: on ppc0 ppbus0: [ITHREAD] plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppc0: [GIANT-LOCKED] ppc0: [ITHREAD] atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] orm0: at iomem 0xd0000-0xd3fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] orm0: at iomem 0xd0000-0xd3fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ums0: on uhub0 ums0: 3 buttons and Z dir. Timecounters tick every 1.000 msec IPsec: Initialized Security Association Processing. ad4: 305245MB at ata2-master UDMA33 acd0: DVDR at ata3-slave UDMA33 GEOM_JOURNAL: Journal 3398879317: ad4s1d contains data. GEOM_JOURNAL: Journal 3398879317: ad4s1d contains journal. GEOM_JOURNAL: Journal ad4s1d clean. GEOM_JOURNAL: Journal 2420032810: ad4s1e contains data. GEOM_JOURNAL: Journal 2420032810: ad4s1e contains journal. GEOM_JOURNAL: Journal ad4s1e clean. GEOM_JOURNAL: Journal 2035336235: ad4s1f contains data. GEOM_JOURNAL: Journal 2035336235: ad4s1f contains journal. GEOM_JOURNAL: Journal ad4s1f clean. GEOM_JOURNAL: Journal 811662893: ad4s1g contains data. GEOM_JOURNAL: Journal 811662893: ad4s1g contains journal. GEOM_JOURNAL: Journal ad4s1g clean. SMP: AP CPU #1 Launched! da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present da1 at umass-sim0 bus 0 target 0 lun 1 da1: Removable Direct Access SCSI-0 device da1: 40.000MB/s transfers da1: Attempt to query device size failed: NOT READY, Medium not present da2 at umass-sim0 bus 0 target 0 lun 2 da2: Removable Direct Access SCSI-0 device da2: 40.000MB/s transfers da2: Attempt to query device size failed: NOT READY, Medium not present da3 at umass-sim0 bus 0 target 0 lun 3 da3: Removable Direct Access SCSI-0 device da3: 40.000MB/s transfers da3: Attempt to query device size failed: NOT READY, Medium not present Trying to mount root from ufs:/dev/ad4s1a ----------------------------------------------------------- From owner-freebsd-stable@FreeBSD.ORG Mon May 12 05:01:29 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8F859106567B for ; Mon, 12 May 2008 05:01:29 +0000 (UTC) (envelope-from daniels_intrepid@yahoo.ie) Received: from web26912.mail.ukl.yahoo.com (web26912.mail.ukl.yahoo.com [217.146.177.79]) by mx1.freebsd.org (Postfix) with SMTP id 05A598FC0A for ; Mon, 12 May 2008 05:01:28 +0000 (UTC) (envelope-from daniels_intrepid@yahoo.ie) Received: (qmail 80672 invoked by uid 60001); 12 May 2008 04:34:47 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.ie; h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=tKNzDhyURMl2VtLoIhluexW5NOB8Z3zbBcIPA1bnpMYelDXPmE4K+JoqFl24UElwkXpctZ7iq5XKWUvi3WCr3b5huzdi6CLUYo4JS83ymigJZ1tRdDd3wj7c+YLbKI9xBGPNjKZDgeBo9rmT1kPvwfeT1k23SSEtk+ikrOHNKGk=; X-YMail-OSG: r1AxoLAVM1klAkeXF4QnFWNiRfj5ItPBo28TEdqgWkS29Io5Ta4jqGYi6MNT3_Nqe.AamRBp6lK3X6UA2duI.bOa57OJLJT5Iwl_AGzaOUjrA4SetfbnVu6MSMA- Received: from [66.108.116.40] by web26912.mail.ukl.yahoo.com via HTTP; Mon, 12 May 2008 05:34:47 BST Date: Mon, 12 May 2008 05:34:47 +0100 (BST) From: John Daniels To: freebsd-stable@freebsd.org MIME-Version: 1.0 Message-ID: <339469.80542.qm@web26912.mail.ukl.yahoo.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: 7.0 issues fixed? upgrade timing? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2008 05:01:29 -0000 1. I have a realtek network card and am using a cable modem router. Does anyone know if fixes for problems with these (see below) have been backported from HEAD to RELENG_7? 2. Is this a good time to upgrade to RELENG_7? 3. I read a post last week that advised that 7.1 is a long way off. Appreciate any advice on use of ULE 3.0 and ZFS prior to 7.1 and a comment on what is holding up 7.1. Thanks >From FreeBSD 7.0 errata notes: [20080229] Instances of packet corruption and instability have been observed with the re(4) network driver. Some users have reported that using a newer version of this driver (on HEAD) has solved their problems, or at least mitigated them. [20080229] A change in the way that FreeBSD sends TCP options has been reported to cause odd interactions with some cable modem routers. While this issue is still under investigation, a change has been committed to HEAD that returns the option processing to that of FreeBSD 6. So far, this change has shown some promising results. Send instant messages to your online friends http://uk.messenger.yahoo.com From owner-freebsd-stable@FreeBSD.ORG Mon May 12 05:11:42 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DEF11106564A for ; Mon, 12 May 2008 05:11:42 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id CC4BB8FC17 for ; Mon, 12 May 2008 05:11:42 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id C29281CC033; Sun, 11 May 2008 22:11:42 -0700 (PDT) Date: Sun, 11 May 2008 22:11:42 -0700 From: Jeremy Chadwick To: dikshie Message-ID: <20080512051142.GA99535@eos.sc1.parodius.com> References: <910e60e80805112117j1ecb83b4s4cdb62eafbdf748f@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <910e60e80805112117j1ecb83b4s4cdb62eafbdf748f@mail.gmail.com> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-stable@freebsd.org Subject: Re: any available patches for sata: "ad4: warning - setfeatures set transfer mode taskqueue timeout - completing request directly" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2008 05:11:43 -0000 On Mon, May 12, 2008 at 01:17:16PM +0900, dikshie wrote: > and strange output from dmesg: > ad4: 305245MB at ata2-master UDMA33 > ^^^^^^^^^^^ > any available patches ? What's strange about this? -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Mon May 12 05:26:51 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 850A51065678; Mon, 12 May 2008 05:26:51 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from gaia.nimnet.asn.au (nimbin.lnk.telstra.net [139.130.45.143]) by mx1.freebsd.org (Postfix) with ESMTP id D69A88FC38; Mon, 12 May 2008 05:26:49 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from localhost (smithi@localhost) by gaia.nimnet.asn.au (8.8.8/8.8.8R1.5) with SMTP id OAA08982; Mon, 12 May 2008 14:52:57 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Mon, 12 May 2008 14:52:56 +1000 (EST) From: Ian Smith To: jonathan@kc8onw.net In-Reply-To: <29626.214.13.212.30.1210554531.squirrel@www.kc8onw.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: bruce@cran.org.uk, stable@freebsd.org, sos@freebsd.org Subject: Re: ATA APM and NCQ support in FreeBSD atacontrol X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2008 05:26:51 -0000 On Sun, 11 May 2008 jonathan@kc8onw.net wrote: > Has any work been done recently towards adding SATA Native Command > Queueing as well as ATA APM and acoustic management to FreeBSD? > > I found this PR (with patch) to add APM and acoustic management control to > atacontrol. The PR was opened in May 2005 has not been changed since > December 2006 and is still open. > http://www.freebsd.org/cgi/query-pr.cgi?pr=81692&cat= > > I have not been able to find much of anything on SATA NCQ in FreeBSD newer > than 2005 or 2006 does anyone know anything newer? Jeremy has addressed the NCQ issue, about which I know nothing. As for APM and AAM, that functionality is handled by sysutils/ataidle, which that PR appears - on a quick glance - to pretty well duplicate. I see phk@ recently added an 'atacontrol spindown' command to HEAD and RELENG_7 that appears to offer similar functionality to 'ataidle -S standby_mins' or 'ataidle -I idle_mins', though specified in seconds instead. However this doesn't address acoustic management. Or is ataidle broken for SATA disks? cheers, Ian From owner-freebsd-stable@FreeBSD.ORG Mon May 12 05:30:17 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 55C861065676 for ; Mon, 12 May 2008 05:30:17 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.freebsd.org (Postfix) with ESMTP id 2739B8FC29 for ; Mon, 12 May 2008 05:30:16 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id 48E4D5CDF; Mon, 12 May 2008 01:11:47 -0400 (EDT) X-Virus-Scanned: amavisd-new at codefab.com Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HlCzqpZAOaXC; Mon, 12 May 2008 01:11:45 -0400 (EDT) Received: from [10.152.145.176] (72-165-115-225.dia.static.qwest.net [72.165.115.225]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by pi.codefab.com (Postfix) with ESMTPSA id 494725C4B; Mon, 12 May 2008 01:11:45 -0400 (EDT) Message-Id: <42C08C65-F0F6-42E5-B20C-D76035F111D7@mac.com> From: Chuck Swiger To: John Daniels In-Reply-To: <339469.80542.qm@web26912.mail.ukl.yahoo.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v919.2) Date: Sun, 11 May 2008 22:11:40 -0700 References: <339469.80542.qm@web26912.mail.ukl.yahoo.com> X-Mailer: Apple Mail (2.919.2) Cc: freebsd-stable@freebsd.org Subject: Re: 7.0 issues fixed? upgrade timing? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2008 05:30:17 -0000 On May 11, 2008, at 9:34 PM, John Daniels wrote: > 1. I have a realtek network card and am using a cable modem > router. Does anyone know if fixes for problems with these (see > below) have been backported from HEAD to RELENG_7? The most useful thing to do would be to test the fixes out yourself and report back whether they help, assuming you encounter problems. > 2. Is this a good time to upgrade to RELENG_7? On a test machine, sure. It's been a long time since I've run a production environment off of a .0 release at all, much less without testing it first. :-) > 3. I read a post last week that advised that 7.1 is a long way off. > Appreciate any advice on use of ULE 3.0 and ZFS prior to 7.1 and a > comment on what is holding up 7.1. Respectively: ULE seems to be a solid improvement. ZFS is still beta. Nothing...be patient, or make more active contributions to help move things forwards. -- -Chuck From owner-freebsd-stable@FreeBSD.ORG Mon May 12 05:31:01 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5EC68106564A for ; Mon, 12 May 2008 05:31:01 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from smtp8.yandex.ru (smtp8.yandex.ru [213.180.200.213]) by mx1.freebsd.org (Postfix) with ESMTP id A87148FC1E for ; Mon, 12 May 2008 05:31:00 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from ns.kirov.so-cdu.ru ([77.72.136.145]:9203 "EHLO [127.0.0.1]" smtp-auth: "bu7cher" TLS-CIPHER: "DHE-RSA-AES256-SHA keybits 256/256 version TLSv1/SSLv3" TLS-PEER-CN1: ) by mail.yandex.ru with ESMTP id S7455914AbYELFaw (ORCPT ); Mon, 12 May 2008 09:30:52 +0400 X-Yandex-Spam: 1 X-Yandex-Front: smtp8 X-Yandex-TimeMark: 1210570252 X-MsgDayCount: 11 X-Comment: RFC 2476 MSA function at smtp8.yandex.ru logged sender identity as: bu7cher Message-ID: <4827D60A.6040200@yandex.ru> Date: Mon, 12 May 2008 09:30:50 +0400 From: "Andrey V. Elsukov" User-Agent: Mozilla Thunderbird 1.5 (FreeBSD/20051231) MIME-Version: 1.0 To: dikshie References: <910e60e80805112117j1ecb83b4s4cdb62eafbdf748f@mail.gmail.com> In-Reply-To: <910e60e80805112117j1ecb83b4s4cdb62eafbdf748f@mail.gmail.com> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: any available patches for sata: "ad4: warning - setfeatures set transfer mode taskqueue timeout - completing request directly" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2008 05:31:01 -0000 dikshie wrote: > atapci1: port > 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xf700-0xf70f mem > 0xefff8000-0xefff9fff irq 20 at device 14.0 on pci0 It seems your controller detected as generic ATA. Can you show `pciconf -l` output from your system? -- WBR, Andrey V. Elsukov From owner-freebsd-stable@FreeBSD.ORG Mon May 12 05:43:59 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6A948106564A for ; Mon, 12 May 2008 05:43:59 +0000 (UTC) (envelope-from unixmania@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.174]) by mx1.freebsd.org (Postfix) with ESMTP id A26318FC16 for ; Mon, 12 May 2008 05:43:58 +0000 (UTC) (envelope-from unixmania@gmail.com) Received: by ug-out-1314.google.com with SMTP id q2so635176uge.37 for ; Sun, 11 May 2008 22:43:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; bh=8iSihGLv1aguPViBR8fYdUN3qfiOAGpQ/r4bqPk3Low=; b=u3cCsaIDuGggP62vcnMLqD7Yxn8XhS9bvSvQwvT50l8zUVLT9L6wtVGtu7qWHxeZbpWdHWKOFMxfmixu4nANyfXJGlKqEp5XGee13L5Nr8gu/FFsF5pWdmfkqb/A9CzOAtX+/vUxJYk8rZfxvAHijfdif/CwQNGFdoCiSoUrpII= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=q0VSzlVrLRy0PBzJVrA3YTpEBmZX0w6bHQOnRrs02uW8RwkJJuYNpeplH4jfLbYhYrWfG/QaELTqBO9g7ls4t3QV+7Xr7zauVijJJoW1ef513iJNFxeuNObM82aJ3dW+lO4nqhUuTsdErnnTLDcWOt6P4qZgewa/Q2Zl2j9x+Fk= Received: by 10.66.217.20 with SMTP id p20mr5075433ugg.51.1210569544564; Sun, 11 May 2008 22:19:04 -0700 (PDT) Received: by 10.67.98.5 with HTTP; Sun, 11 May 2008 22:19:04 -0700 (PDT) Message-ID: Date: Mon, 12 May 2008 02:19:04 -0300 From: "Carlos A. M. dos Santos" To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_1689_32867670.1210569544557" Subject: burncd: ioctl(CDIOCEJECT): Input/output error X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2008 05:43:59 -0000 ------=_Part_1689_32867670.1210569544557 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hello, I get "burncd: ioctl(CDIOCEJECT): Input/output error" each time I attempt to blank a CDRW with burncd -f /dev/acd0 blank eject I noticed that this does not happen when I write a data cd with burncd -f /dev/acd0 data cd-image.iso fixate eject I have seen the same bahavior on 4 different computers that have DVD-RW units. Applying the attached patch to /usr/src/usr.sbin/burncd/burncd.c solves the problem. It make burncd attempt to eject the CD five times, sleeping for one second after each unccessful try. I'd like to get some opinions on this before submitting a PR. Thanks in advance. -- Carlos A. M. dos Santos ------=_Part_1689_32867670.1210569544557 Content-Type: application/octet-stream; name=burncd_eject.patch Content-Transfer-Encoding: base64 X-Attachment-Id: f_fg4ltas60 Content-Disposition: attachment; filename=burncd_eject.patch LS0tIGJ1cm5jZC5jLm9yaWcJMjAwNS0wNS0xMyAxNzowNjo0NC4wMDAwMDAwMDAgLTAzMDAKKysr IGJ1cm5jZC5jCTIwMDgtMDUtMTIgMDE6NDQ6MzAuMDAwMDAwMDAwIC0wMzAwCkBAIC00Niw2ICs0 Niw3IEBACiAjaW5jbHVkZSA8YXJwYS9pbmV0Lmg+CiAKICNkZWZpbmUgQkxPQ0tTCTE2CisjZGVm aW5lIEVKRUNUX1RSSUVTIDUKIAogc3RydWN0IHRyYWNrX2luZm8gewogCWludAlmaWxlOwpAQCAt MzE2LDkgKzMxNywxMyBAQAogCQllcnIoRVhfSU9FUlIsICJpb2N0bChDRFJJT0NTRVRCTE9DS1NJ WkUpIik7CiAJfQogCi0JaWYgKGVqZWN0KQotCQlpZiAoaW9jdGwoZmQsIENESU9DRUpFQ1QpIDwg MCkKKwlpZiAoZWplY3QpIHsKKwkJaW50IHN0YXR1cywgaSA9IDA7CisJCXdoaWxlICgoc3RhdHVz ID0gaW9jdGwoZmQsIENESU9DRUpFQ1QpKSA8IDAgJiYgKytpIDw9IEVKRUNUX1RSSUVTKQorCQkJ c2xlZXAoMSk7CisJCWlmIChzdGF0dXMgPCAwKQogCQkJZXJyKEVYX0lPRVJSLCAiaW9jdGwoQ0RJ T0NFSkVDVCkiKTsKKwl9CiAJY2xvc2UoZmQpOwogCWV4aXQoRVhfT0spOwogfQo= ------=_Part_1689_32867670.1210569544557-- From owner-freebsd-stable@FreeBSD.ORG Mon May 12 05:46:24 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 521FF106568B for ; Mon, 12 May 2008 05:46:24 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 404CB8FC1F for ; Mon, 12 May 2008 05:46:24 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 0CA151CC033; Sun, 11 May 2008 22:46:24 -0700 (PDT) Date: Sun, 11 May 2008 22:46:24 -0700 From: Jeremy Chadwick To: John Daniels Message-ID: <20080512054624.GA660@eos.sc1.parodius.com> References: <339469.80542.qm@web26912.mail.ukl.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <339469.80542.qm@web26912.mail.ukl.yahoo.com> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-stable@freebsd.org Subject: Re: 7.0 issues fixed? upgrade timing? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2008 05:46:24 -0000 On Mon, May 12, 2008 at 05:34:47AM +0100, John Daniels wrote: > 1. I have a realtek network card and am using a cable modem router. > Does anyone know if fixes for problems with these (see below) have > been backported from HEAD to RELENG_7? I'd recommend downloading a RELENG_7 bootonly image, or possibly the livefs image (which will give you utilities and a working read-only filesystem), and see how your hardware looks on that. Meaning, if you have a test scenario which can be easily reproduced and can be done from livefs, give that a try. RELENG_7 snapshots (meaning 7.0-STABLE vs. 7.0-RELEASE) are here: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200804 > 2. Is this a good time to upgrade to RELENG_7? That's entirely up to you. RELENG_6 will be decomissioned quicker than RELENG_5 was, from what I've read, so testing compatibility now would be a good idea. > 3. I read a post last week that advised that 7.1 is a long way off. > Appreciate any advice on use of ULE 3.0 and ZFS prior to 7.1 and a > comment on what is holding up 7.1. Regarding ULE 3.0, I think you're referring to the ULE that's actually in RELENG_7 presently, which actually works (compared to the ULE that was in RELENG_5 and RELENG_6, which had major bugs). Or are you referring to an even newer scheduler (something -CURRENT might have)? ZFS is in a state of... well... my opinion is: use it at your own risk. The "experimental!" warning is very applicable. There are known problems with ZFS when performing lots of I/O between a ZFS pool and a UFS fs. > [20080229] Instances of packet corruption and instability have been observed with the re(4) network driver. Some users have reported that using a newer version of this driver (on HEAD) has solved their problems, or at least mitigated them. I believe this has been fixed, based on commits I've seen to the driver. Pyun YongHyeon would be able to confirm/deny this. > [20080229] A change in the way that FreeBSD sends TCP options has been reported to cause odd interactions with some cable modem routers. While this issue is still under investigation, a change has been committed to HEAD that returns the option processing to that of FreeBSD 6. So far, this change has shown some promising results. Do you have more details on this? Open PR, or a thread I can read? I'm thinking it might be related to the net.inet.tcp.rfc1323 sysctl, but I'm not sure. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Mon May 12 05:54:07 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1FB22106566C for ; Mon, 12 May 2008 05:54:07 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 0B2768FC0C for ; Mon, 12 May 2008 05:54:06 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id EAE9B1CC033; Sun, 11 May 2008 22:54:06 -0700 (PDT) Date: Sun, 11 May 2008 22:54:06 -0700 From: Jeremy Chadwick To: dikshie Message-ID: <20080512055406.GA1333@eos.sc1.parodius.com> References: <910e60e80805112117j1ecb83b4s4cdb62eafbdf748f@mail.gmail.com> <20080512051142.GA99535@eos.sc1.parodius.com> <910e60e80805112214p5a03b6fcn73ea1c5ebf70baab@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <910e60e80805112214p5a03b6fcn73ea1c5ebf70baab@mail.gmail.com> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-stable@freebsd.org Subject: Re: any available patches for sata: "ad4: warning - setfeatures set transfer mode taskqueue timeout - completing request directly" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2008 05:54:07 -0000 On Mon, May 12, 2008 at 02:14:37PM +0900, dikshie wrote: > On Mon, May 12, 2008 at 2:11 PM, Jeremy Chadwick wrote: > > On Mon, May 12, 2008 at 01:17:16PM +0900, dikshie wrote: > >> and strange output from dmesg: > >> ad4: 305245MB at ata2-master UDMA33 > >> ^^^^^^^^^^^ > >> any available patches ? > > > > What's strange about this? > > i mean for "UDMA33" it should be SATA300 > do have to upgrade BIOS? Your carets are pointing to the drive firmware revision, which is why I was confused. :-) Yes, it should say either SATA150 or SATA300 (more on that in a moment), but based on your dmesg output, it appears your SATA controller does not have an attached driver, thus is operating generically. Andrey recommended showing pciconf -lv output; please do. Your drive is *probably* operating in SATA150/300 mode, despite UDMA33 being printed, however. Assuming you know your disk can push >33MB/sec, you could try some simple read I/O and use gstat to watch the speed. dd if=/dev/ad4 of=/dev/null bs=1m should suffice. Regarding SATA150 vs. SATA300: your drive has a physical jumper, labelled OPT1 in the below photo, which limits the drive to SATA150 capability. You can remove this jumper and get SATA300. This doesn't explain the UDMA33 issue, though. http://wdc.custhelp.com/cgi-bin/wdc.cfg/php/enduser/std_adp.php?p_faqid=1400&p_created=1134597011 Also, please don't remove the mailing list from the CC; others need to know what information you've provided, and future users may find this thread useful. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Mon May 12 05:57:35 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 973D91065673 for ; Mon, 12 May 2008 05:57:35 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from smtp8.yandex.ru (smtp8.yandex.ru [213.180.200.213]) by mx1.freebsd.org (Postfix) with ESMTP id DD6648FC18 for ; Mon, 12 May 2008 05:57:34 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from ns.kirov.so-cdu.ru ([77.72.136.145]:15056 "EHLO [127.0.0.1]" smtp-auth: "bu7cher" TLS-CIPHER: "DHE-RSA-AES256-SHA keybits 256/256 version TLSv1/SSLv3" TLS-PEER-CN1: ) by mail.yandex.ru with ESMTP id S7455966AbYELF1R (ORCPT ); Mon, 12 May 2008 09:27:17 +0400 X-Yandex-Spam: 1 X-Yandex-Front: smtp8 X-Yandex-TimeMark: 1210570037 X-MsgDayCount: 9 X-Comment: RFC 2476 MSA function at smtp8.yandex.ru logged sender identity as: bu7cher Message-ID: <4827D531.7000603@yandex.ru> Date: Mon, 12 May 2008 09:27:13 +0400 From: "Andrey V. Elsukov" User-Agent: Mozilla Thunderbird 1.5 (FreeBSD/20051231) MIME-Version: 1.0 To: Jeremy Chadwick References: <29626.214.13.212.30.1210554531.squirrel@www.kc8onw.net> <20080512030647.GA93725@eos.sc1.parodius.com> In-Reply-To: <20080512030647.GA93725@eos.sc1.parodius.com> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org, jonathan@kc8onw.net, sos@FreeBSD.org Subject: Re: ATA APM and NCQ support in FreeBSD atacontrol X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2008 05:57:35 -0000 Jeremy Chadwick wrote: > I believe NCQ is supported, assuming that your controller is operating > in AHCI mode and your disk supports NCQ. This mainly applies to Intel > ICHx controllers, but there are others which support it as well. > There's also NCQ support in non-AHCI drivers like hptmv(4), rr232x(4), > hptrr(4), and mpt(4) with SATA disks. No. ata(4) driver currently doesn't support/use NCQ. -- WBR, Andrey V. Elsukov From owner-freebsd-stable@FreeBSD.ORG Mon May 12 06:00:17 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 917D4106564A for ; Mon, 12 May 2008 06:00:17 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 7BC238FC2E for ; Mon, 12 May 2008 06:00:17 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 6ED051CC033; Sun, 11 May 2008 23:00:17 -0700 (PDT) Date: Sun, 11 May 2008 23:00:17 -0700 From: Jeremy Chadwick To: dikshie Message-ID: <20080512060017.GB1333@eos.sc1.parodius.com> References: <910e60e80805112117j1ecb83b4s4cdb62eafbdf748f@mail.gmail.com> <4827D60A.6040200@yandex.ru> <910e60e80805112236r105b5894r285b68f0d28105b1@mail.gmail.com> <910e60e80805112242w57a6e932tbf48e482d96dc452@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <910e60e80805112242w57a6e932tbf48e482d96dc452@mail.gmail.com> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: "Andrey V. Elsukov" , freebsd-stable@freebsd.org Subject: Re: any available patches for sata: "ad4: warning - setfeatures set transfer mode taskqueue timeout - completing request directly" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2008 06:00:17 -0000 On Mon, May 12, 2008 at 02:42:40PM +0900, dikshie wrote: > i just phone computer store and check together the BIOS. > it seems my computer store put the disk on IDE mode NOT on AHCI mode. > after change to AHCI now FreeBSD can detect SATA 300 (for WDC) and > SATA 150 (for DVD-R). Great, there you go. :-) > BUT sometimes I still getting: > ad4: warning - setfeatures set transfer mode taskqueue timeout -completing request directly > ad4: warning - setfeatures enable rcache taskqueue timeout - completing request directly > ad4: warning - setfeatures enable wcache taskqueue timeout - completing request directly > ad4: timeout - flushcache retrying (0 retries left) > geom_journal: flush cache of ad4s1d: error=5 > ad4: timeout - write_dma retrying (1 retry left) LBA=4139103 1) Have you checked SMART statistics of the drive, or run SMART tests? Install ports/sysutils/smartmontools and use smartctl -a /dev/ad4, and provide the output. 2) Is the error always on ad4? If so, is the error always at LBA 4139103, or "around there" (give or take a few thousand addressing blocks)? If so, the ad4 disk may be going bad. Otherwise, I would say this is probably the issue I've documented on my Common Issues page. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Mon May 12 06:09:38 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 906FF106566C; Mon, 12 May 2008 06:09:38 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 7C6E08FC1B; Mon, 12 May 2008 06:09:38 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 68E721CC033; Sun, 11 May 2008 23:09:38 -0700 (PDT) Date: Sun, 11 May 2008 23:09:38 -0700 From: Jeremy Chadwick To: "Andrey V. Elsukov" Message-ID: <20080512060938.GA2007@eos.sc1.parodius.com> References: <29626.214.13.212.30.1210554531.squirrel@www.kc8onw.net> <20080512030647.GA93725@eos.sc1.parodius.com> <4827D531.7000603@yandex.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4827D531.7000603@yandex.ru> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: stable@freebsd.org, jonathan@kc8onw.net, sos@FreeBSD.org Subject: Re: ATA APM and NCQ support in FreeBSD atacontrol X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2008 06:09:38 -0000 On Mon, May 12, 2008 at 09:27:13AM +0400, Andrey V. Elsukov wrote: > Jeremy Chadwick wrote: >> I believe NCQ is supported, assuming that your controller is operating >> in AHCI mode and your disk supports NCQ. This mainly applies to Intel >> ICHx controllers, but there are others which support it as well. >> There's also NCQ support in non-AHCI drivers like hptmv(4), rr232x(4), >> hptrr(4), and mpt(4) with SATA disks. > > No. ata(4) driver currently doesn't support/use NCQ. Thanks for this information -- I had no idea! I'll add this to my Common Issues page, although it's not so much an "issue" but more so a feature. I was always under the impression that AHCI included automatic support for negotiation and use of extensions like NCQ and TCQ: http://en.wikipedia.org/wiki/Native_Command_Queuing http://www.seagate.com/content/docs/pdf/whitepaper/D2c_tech_paper_intc-stx_sata_ncq.pdf -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Mon May 12 06:14:42 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 034C1106564A; Mon, 12 May 2008 06:14:42 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from smtp7.yandex.ru (smtp7.yandex.ru [213.180.200.45]) by mx1.freebsd.org (Postfix) with ESMTP id D75D38FC0A; Mon, 12 May 2008 06:14:40 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from mail.kirov.so-cdu.ru ([77.72.136.145]:31461 "EHLO [127.0.0.1]" smtp-auth: "bu7cher" TLS-CIPHER: "DHE-RSA-AES256-SHA keybits 256/256 version TLSv1/SSLv3" TLS-PEER-CN1: ) by mail.yandex.ru with ESMTP id S738515AbYELGOh (ORCPT + 2 others); Mon, 12 May 2008 10:14:37 +0400 X-Yandex-Spam: 1 X-Yandex-Front: smtp7 X-Yandex-TimeMark: 1210572877 X-MsgDayCount: 20 X-Comment: RFC 2476 MSA function at smtp7.yandex.ru logged sender identity as: bu7cher Message-ID: <4827E049.4030500@yandex.ru> Date: Mon, 12 May 2008 10:14:33 +0400 From: "Andrey V. Elsukov" User-Agent: Mozilla Thunderbird 1.5 (FreeBSD/20051231) MIME-Version: 1.0 To: Jeremy Chadwick References: <29626.214.13.212.30.1210554531.squirrel@www.kc8onw.net> <20080512030647.GA93725@eos.sc1.parodius.com> <4827D531.7000603@yandex.ru> <20080512060938.GA2007@eos.sc1.parodius.com> In-Reply-To: <20080512060938.GA2007@eos.sc1.parodius.com> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org, jonathan@kc8onw.net, sos@FreeBSD.org Subject: Re: ATA APM and NCQ support in FreeBSD atacontrol X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2008 06:14:42 -0000 Jeremy Chadwick wrote: >> No. ata(4) driver currently doesn't support/use NCQ. > > Thanks for this information -- I had no idea! I'll add this to my > Common Issues page, although it's not so much an "issue" but more so a > feature. > > I was always under the impression that AHCI included automatic support > for negotiation and use of extensions like NCQ and TCQ: > > http://en.wikipedia.org/wiki/Native_Command_Queuing > http://www.seagate.com/content/docs/pdf/whitepaper/D2c_tech_paper_intc-stx_sata_ncq.pdf AHCI has standart method to determine presence of NCQ support. But FreeBSD's driver needs some code to work with NCQ. Soren said to me that he is going to work with NCQ support after merging PM support, but I don't know about current status. -- WBR, Andrey V. Elsukov From owner-freebsd-stable@FreeBSD.ORG Mon May 12 06:38:47 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AB88D1065671 for ; Mon, 12 May 2008 06:38:47 +0000 (UTC) (envelope-from dikshie@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.169]) by mx1.freebsd.org (Postfix) with ESMTP id 792648FC20 for ; Mon, 12 May 2008 06:38:47 +0000 (UTC) (envelope-from dikshie@gmail.com) Received: by wf-out-1314.google.com with SMTP id 28so2115119wfa.7 for ; Sun, 11 May 2008 23:38:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=V99fEfRE3vIY6FtXpigB/vW1qPMfcmV7AfRYZ7ZXx0w=; b=u21LG4BKF9RCo559CfjAoCE5jIeKR2DMu3Mw7HJzwbBLDnb2rIENaV13X9qUzvlG7tmJoh7p2a0GcT4sIWL7Qzm5MKZYPhjdmX+NFmbzqFPmViPR6Wx1Cmhvm4PCclpuppqPHlaQU6wvPMWE+1AgZ7tU0k9lgc+wudIEbZpJkQ8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=YRy8ICLN43NDWuns3WQqPwaD43hBtKZJnSuL076B2Df+A8TnsDffYilFfouIb8eqiV/4OTyowTVFe4tgVqdK2I6UTo13YtqKUxMFJnLI1hikAGbKSe1fZDtuGtDsbk++mA7zsEgCi9RFSK2X3BKG6JXdVicggVKXUgQ02BnYibI= Received: by 10.142.226.2 with SMTP id y2mr3118278wfg.64.1210574327181; Sun, 11 May 2008 23:38:47 -0700 (PDT) Received: by 10.143.123.5 with HTTP; Sun, 11 May 2008 23:38:47 -0700 (PDT) Message-ID: <910e60e80805112338m6edf555fr3b7693f2c81bac5f@mail.gmail.com> Date: Mon, 12 May 2008 15:38:47 +0900 From: dikshie To: "Jeremy Chadwick" In-Reply-To: <20080512060017.GB1333@eos.sc1.parodius.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <910e60e80805112117j1ecb83b4s4cdb62eafbdf748f@mail.gmail.com> <4827D60A.6040200@yandex.ru> <910e60e80805112236r105b5894r285b68f0d28105b1@mail.gmail.com> <910e60e80805112242w57a6e932tbf48e482d96dc452@mail.gmail.com> <20080512060017.GB1333@eos.sc1.parodius.com> Cc: "Andrey V. Elsukov" , freebsd-stable@freebsd.org Subject: Re: any available patches for sata: "ad4: warning - setfeatures set transfer mode taskqueue timeout - completing request directly" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2008 06:38:47 -0000 On Mon, May 12, 2008 at 3:00 PM, Jeremy Chadwick wrote: > 1) Have you checked SMART statistics of the drive, or run SMART tests? > Install ports/sysutils/smartmontools and use smartctl -a /dev/ad4, and > provide the output. > > 2) Is the error always on ad4? If so, is the error always at LBA > 4139103, or "around there" (give or take a few thousand addressing > blocks)? If so, the ad4 disk may be going bad. Otherwise, I would say > this is probably the issue I've documented on my Common Issues page. dhcp-143-221# smartctl -a /dev/ad4 smartctl version 5.38 [amd64-portbld-freebsd7.0] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Model Family: Western Digital Caviar Second Generation Serial ATA family Device Model: WDC WD3200AAKS-00VYA0 Serial Number: WD-WCARW2314765 Firmware Version: 12.01B02 User Capacity: 320,072,933,376 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Mon May 12 15:27:24 2008 JST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x84) Offline data collection activity was suspended by an interrupting command from host. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (8760) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 104) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x303f) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0003 155 155 021 Pre-fail Always - 5233 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 11 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x000e 200 200 051 Old_age Always - 0 9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 940 10 Spin_Retry_Count 0x0012 100 253 051 Old_age Always - 0 11 Calibration_Retry_Count 0x0012 100 253 051 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 11 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 8 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 11 194 Temperature_Celsius 0x0022 114 108 000 Old_age Always - 33 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0012 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 051 Old_age Offline - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. errors always on ad4 with random LBA blocks numbers. with best regards, -dikshie- From owner-freebsd-stable@FreeBSD.ORG Mon May 12 07:16:12 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 308D2106566C for ; Mon, 12 May 2008 07:16:12 +0000 (UTC) (envelope-from jonathan@kc8onw.net) Received: from mail-out1.fuse.net (mail-out1.fuse.net [216.68.8.175]) by mx1.freebsd.org (Postfix) with ESMTP id E8E078FC0A for ; Mon, 12 May 2008 07:16:11 +0000 (UTC) (envelope-from jonathan@kc8onw.net) X-CNFS-Analysis: v=1.0 c=1 a=hgotusUyA10A:15 a=SBX5CgiQuncA:10 a=EkqlnXz0YW0A:10 a=xUvkYoQocQKi/8Los98NoQ==:17 a=6I5d2MoRAAAA:8 a=0aaThRKhvmoaeY0gSl4A:9 a=PiGEKJGV_Qd824_0cykA:7 a=VqXZvYeDKvurqx0jIoPeE_dRj6AA:4 a=jtOyKYpszwUA:10 a=LY0hPdMaydYA:10 X-CM-Score: 0 X-Scanned-by: Cloudmark Authority Engine Received: from [208.102.162.227] ([208.102.162.227:50474] helo=mail.kc8onw.net) by mail-out1.fuse.net (ecelerity 2.1.1.22 r(17669)) with ESMTP id 53/30-00443-ABEE7284 for ; Mon, 12 May 2008 03:16:11 -0400 Received: from www.kc8onw.net (localhost [127.0.0.1]) by mail.kc8onw.net (Postfix) with ESMTP id 0ABEE2842A; Mon, 12 May 2008 03:16:10 -0400 (EDT) Received: from 80.91.220.50 (SquirrelMail authenticated user jonathan) by www.kc8onw.net with HTTP; Mon, 12 May 2008 03:16:10 -0400 (EDT) Message-ID: <53004.80.91.220.50.1210576570.squirrel@www.kc8onw.net> In-Reply-To: References: <29626.214.13.212.30.1210554531.squirrel@www.kc8onw.net> Date: Mon, 12 May 2008 03:16:10 -0400 (EDT) From: jonathan@kc8onw.net To: "Ian Smith" User-Agent: SquirrelMail/1.5.1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: stable@freebsd.org, sos@freebsd.org Subject: Re: ATA APM and NCQ support in FreeBSD atacontrol X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2008 07:16:12 -0000 On Mon, May 12, 2008 00:52, Ian Smith wrote: > On Sun, 11 May 2008 jonathan@kc8onw.net wrote: > >> I found this PR (with patch) to add APM and acoustic management control >> to atacontrol. The PR was opened in May 2005 has not been changed since >> December 2006 and is still open. >> http://www.freebsd.org/cgi/query-pr.cgi?pr=81692&cat= >> >> I have not been able to find much of anything on SATA NCQ in FreeBSD >> newer than 2005 or 2006 does anyone know anything newer? > > As for APM and AAM, that functionality is handled by sysutils/ataidle, > which that PR appears - on a quick glance - to pretty well duplicate. > > I see phk@ recently added an 'atacontrol spindown' command to HEAD and > RELENG_7 that appears to offer similar functionality to 'ataidle -S > standby_mins' or 'ataidle -I idle_mins', though specified in seconds > instead. However this doesn't address acoustic management. > > Or is ataidle broken for SATA disks? I think the idea was to put the ability to control it where people see it first. I expected to be able to control NCQ, APM, and acoustic management from atacontrol considering it listed whether they were enabled or not. ataidle is easy enough to find, I won't deny, but why make users do the google search and install a port when there is (what looks to me) a fairly simple patch that can be added to the base system. Either way it would be good to get the PR closed one way or the other considering the backlog... Jonathan Stewart From owner-freebsd-stable@FreeBSD.ORG Mon May 12 07:23:16 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F15F1106566B; Mon, 12 May 2008 07:23:16 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id DBD298FC28; Mon, 12 May 2008 07:23:16 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 755701CC033; Mon, 12 May 2008 00:23:16 -0700 (PDT) Date: Mon, 12 May 2008 00:23:16 -0700 From: Jeremy Chadwick To: jonathan@kc8onw.net Message-ID: <20080512072316.GA3845@eos.sc1.parodius.com> References: <29626.214.13.212.30.1210554531.squirrel@www.kc8onw.net> <53004.80.91.220.50.1210576570.squirrel@www.kc8onw.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <53004.80.91.220.50.1210576570.squirrel@www.kc8onw.net> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: stable@freebsd.org, Ian Smith , sos@freebsd.org Subject: Re: ATA APM and NCQ support in FreeBSD atacontrol X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2008 07:23:17 -0000 On Mon, May 12, 2008 at 03:16:10AM -0400, jonathan@kc8onw.net wrote: > On Mon, May 12, 2008 00:52, Ian Smith wrote: > > On Sun, 11 May 2008 jonathan@kc8onw.net wrote: > > > >> I found this PR (with patch) to add APM and acoustic management control > >> to atacontrol. The PR was opened in May 2005 has not been changed since > >> December 2006 and is still open. > >> http://www.freebsd.org/cgi/query-pr.cgi?pr=81692&cat= > >> > >> I have not been able to find much of anything on SATA NCQ in FreeBSD > >> newer than 2005 or 2006 does anyone know anything newer? > > > > As for APM and AAM, that functionality is handled by sysutils/ataidle, > > which that PR appears - on a quick glance - to pretty well duplicate. > > > > I see phk@ recently added an 'atacontrol spindown' command to HEAD and > > RELENG_7 that appears to offer similar functionality to 'ataidle -S > > standby_mins' or 'ataidle -I idle_mins', though specified in seconds > > instead. However this doesn't address acoustic management. > > > > Or is ataidle broken for SATA disks? > > I think the idea was to put the ability to control it where people see it > first. I expected to be able to control NCQ, APM, and acoustic management > from atacontrol considering it listed whether they were enabled or not. Well, atacontrol(8) does let you control many things, but most pertain to ataraid(4). Otherwise, it acts purely as an ATA/SATA information utility; maybe it should be renamed atainfo(8)? The expectation that the tool should be able to control those things is legitimate, but if this is something you absolutely *need*, then I would recommend going with Linux instead. Their libata has support for all of the above, and has userland applications to control said features. > ataidle is easy enough to find, I won't deny, but why make users do the > google search and install a port when there is (what looks to me) a fairly > simple patch that can be added to the base system. Either way it would be > good to get the PR closed one way or the other considering the backlog... There are a "decent" number of PRs pertaining to ATA/SATA stuff in FreeBSD, some going back over 2 years which fix very severe bugs in RAID (see my Common Issues list for examples). Your cries are heard by some, but I'm left believing Soren is just super busy with real life. I consider this even more justification that the ATA layer in FreeBSD needs additional eyes familiar with it, and not just a single person. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Mon May 12 07:36:52 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 969EE1065673 for ; Mon, 12 May 2008 07:36:52 +0000 (UTC) (envelope-from jonathan@kc8onw.net) Received: from mail-out1.fuse.net (mail-out1.fuse.net [216.68.8.175]) by mx1.freebsd.org (Postfix) with ESMTP id 593408FC14 for ; Mon, 12 May 2008 07:36:52 +0000 (UTC) (envelope-from jonathan@kc8onw.net) X-CNFS-Analysis: v=1.0 c=1 a=QbhQkq5H3j4A:15 a=SBX5CgiQuncA:10 a=EkqlnXz0YW0A:10 a=xUvkYoQocQKi/8Los98NoQ==:17 a=6I5d2MoRAAAA:8 a=9M2REOSS36gancw60IYA:9 a=exKcGCQvsPc38TbpNAIA:7 a=rkcJ-wX26Xq6r0wRAbsGfm_4fhoA:4 a=jtOyKYpszwUA:10 a=LY0hPdMaydYA:10 X-CM-Score: 0 X-Scanned-by: Cloudmark Authority Engine Received: from [208.102.162.227] ([208.102.162.227:50809] helo=mail.kc8onw.net) by mail-out1.fuse.net (ecelerity 2.1.1.22 r(17669)) with ESMTP id C9/E0-00443-393F7284 for ; Mon, 12 May 2008 03:36:51 -0400 Received: from www.kc8onw.net (localhost [127.0.0.1]) by mail.kc8onw.net (Postfix) with ESMTP id E2B4D2846A; Mon, 12 May 2008 03:36:50 -0400 (EDT) Received: from 80.91.220.50 (SquirrelMail authenticated user jonathan) by www.kc8onw.net with HTTP; Mon, 12 May 2008 03:36:50 -0400 (EDT) Message-ID: <58131.80.91.220.50.1210577810.squirrel@www.kc8onw.net> In-Reply-To: <20080512072316.GA3845@eos.sc1.parodius.com> References: <29626.214.13.212.30.1210554531.squirrel@www.kc8onw.net> <53004.80.91.220.50.1210576570.squirrel@www.kc8onw.net> <20080512072316.GA3845@eos.sc1.parodius.com> Date: Mon, 12 May 2008 03:36:50 -0400 (EDT) From: jonathan@kc8onw.net To: "Jeremy Chadwick" User-Agent: SquirrelMail/1.5.1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: stable@freebsd.org Subject: Re: ATA APM and NCQ support in FreeBSD atacontrol X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2008 07:36:52 -0000 On Mon, May 12, 2008 03:23, Jeremy Chadwick wrote: > On Mon, May 12, 2008 at 03:16:10AM -0400, jonathan@kc8onw.net wrote: > >> On Mon, May 12, 2008 00:52, Ian Smith wrote: >> >>> On Sun, 11 May 2008 jonathan@kc8onw.net wrote: >>> >>>> I found this PR (with patch) to add APM and acoustic management >>>> control to atacontrol. The PR was opened in May 2005 has not been >>>> changed since December 2006 and is still open. >>>> http://www.freebsd.org/cgi/query-pr.cgi?pr=81692&cat= >>> >>> As for APM and AAM, that functionality is handled by >>> sysutils/ataidle, which that PR appears - on a quick glance - to >>> pretty well duplicate. >>> >>> I see phk@ recently added an 'atacontrol spindown' command to HEAD >>> and RELENG_7 that appears to offer similar functionality to 'ataidle >>> -S >>> standby_mins' or 'ataidle -I idle_mins', though specified in seconds >>> instead. However this doesn't address acoustic management. >>> >>> Or is ataidle broken for SATA disks? >>> >> >> I think the idea was to put the ability to control it where people see >> it first. I expected to be able to control NCQ, APM, and acoustic >> management from atacontrol considering it listed whether they were >> enabled or not. > > Well, atacontrol(8) does let you control many things, but most pertain > to ataraid(4). Otherwise, it acts purely as an ATA/SATA information > utility; maybe it should be renamed atainfo(8)? That would probably confuse more existing users than it would help new ones. I don't think it would be worth renaming it unless the raid functionality was moved to a separate command, which would be a pointless bunch of work. > The expectation that the tool should be able to control those things is > legitimate, but if this is something you absolutely *need*, then I would > recommend going with Linux instead. Their libata has support for all of > the above, and has userland applications to control said features. Nope, I'm happy with FreeBSD. This is more of a minor quirk than anything else for me. I figured I would see if anything had changed since the last mailing list messages I found where well over a year old. >> ataidle is easy enough to find, I won't deny, but why make users do the >> google search and install a port when there is (what looks to me) a >> fairly simple patch that can be added to the base system. Either way it >> would be good to get the PR closed one way or the other considering the >> backlog... > > There are a "decent" number of PRs pertaining to ATA/SATA stuff in > FreeBSD, some going back over 2 years which fix very severe bugs in RAID > (see my Common Issues list for examples). Where is this list? I did a quick search but couldn't find it. > Your cries are heard by some, but I'm left believing Soren is just super > busy with real life. I consider this even more justification that the ATA > layer in FreeBSD needs additional eyes familiar with it, and not just a > single person. No argument here. Soren does an incredible job maintaining ATA as it is and I am very grateful that he has put as much of his time into the project as he has. (Thanks Soren!) Jonathan Stewart From owner-freebsd-stable@FreeBSD.ORG Mon May 12 07:45:41 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3CC341065676 for ; Mon, 12 May 2008 07:45:41 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 279F68FC1C for ; Mon, 12 May 2008 07:45:41 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 1E3151CC033; Mon, 12 May 2008 00:45:41 -0700 (PDT) Date: Mon, 12 May 2008 00:45:41 -0700 From: Jeremy Chadwick To: jonathan@kc8onw.net Message-ID: <20080512074541.GA4667@eos.sc1.parodius.com> References: <29626.214.13.212.30.1210554531.squirrel@www.kc8onw.net> <53004.80.91.220.50.1210576570.squirrel@www.kc8onw.net> <20080512072316.GA3845@eos.sc1.parodius.com> <58131.80.91.220.50.1210577810.squirrel@www.kc8onw.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <58131.80.91.220.50.1210577810.squirrel@www.kc8onw.net> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: stable@freebsd.org Subject: Re: ATA APM and NCQ support in FreeBSD atacontrol X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2008 07:45:41 -0000 On Mon, May 12, 2008 at 03:36:50AM -0400, jonathan@kc8onw.net wrote: > On Mon, May 12, 2008 03:23, Jeremy Chadwick wrote: > > On Mon, May 12, 2008 at 03:16:10AM -0400, jonathan@kc8onw.net wrote: > >> ataidle is easy enough to find, I won't deny, but why make users do the > >> google search and install a port when there is (what looks to me) a > >> fairly simple patch that can be added to the base system. Either way it > >> would be good to get the PR closed one way or the other considering the > >> backlog... > > > > There are a "decent" number of PRs pertaining to ATA/SATA stuff in > > FreeBSD, some going back over 2 years which fix very severe bugs in RAID > > (see my Common Issues list for examples). > > Where is this list? I did a quick search but couldn't find it. http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues > > Your cries are heard by some, but I'm left believing Soren is just super > > busy with real life. I consider this even more justification that the ATA > > layer in FreeBSD needs additional eyes familiar with it, and not just a > > single person. > > No argument here. Soren does an incredible job maintaining ATA as it is > and I am very grateful that he has put as much of his time into the > project as he has. (Thanks Soren!) I am too, but PRs that are 2 years old which include patches for severe bugs that affect reliability of RAID is (in my opinion) not acceptable. I've been spanked over saying this before ("you don't understand how open source works"), but necessity easily supercedes idealism. Linux's libata has evolved very quickly and very well, and has multiple eyes familiar with the code (in the case the author takes vacation, etc.). It has the upper hand here. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Mon May 12 08:16:04 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DF2641065676; Mon, 12 May 2008 08:16:04 +0000 (UTC) (envelope-from markir@paradise.net.nz) Received: from smtp5.clear.net.nz (smtp5.clear.net.nz [203.97.33.68]) by mx1.freebsd.org (Postfix) with ESMTP id A4A348FC0A; Mon, 12 May 2008 08:16:04 +0000 (UTC) (envelope-from markir@paradise.net.nz) Received: from zmori.markir.net (121-73-161-238.dsl.telstraclear.net [121.73.161.238]) by smtp5.clear.net.nz (CLEAR Net Mail) with ESMTP id <0K0Q00ADLWWVRO00@smtp5.clear.net.nz>; Mon, 12 May 2008 20:00:33 +1200 (NZST) Date: Mon, 12 May 2008 20:00:30 +1200 From: Mark Kirkwood In-reply-to: <20080512074541.GA4667@eos.sc1.parodius.com> To: Jeremy Chadwick Message-id: <4827F91E.60102@paradise.net.nz> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7bit References: <29626.214.13.212.30.1210554531.squirrel@www.kc8onw.net> <53004.80.91.220.50.1210576570.squirrel@www.kc8onw.net> <20080512072316.GA3845@eos.sc1.parodius.com> <58131.80.91.220.50.1210577810.squirrel@www.kc8onw.net> <20080512074541.GA4667@eos.sc1.parodius.com> User-Agent: Thunderbird 2.0.0.9 (X11/20080419) Cc: stable@freebsd.org, jonathan@kc8onw.net Subject: Re: ATA APM and NCQ support in FreeBSD atacontrol X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2008 08:16:05 -0000 Jeremy Chadwick wrote: > > I am too, but PRs that are 2 years old which include patches for severe > bugs that affect reliability of RAID is (in my opinion) not acceptable. > I've been spanked over saying this before ("you don't understand how > open source works"), but necessity easily supercedes idealism. > > Linux's libata has evolved very quickly and very well, and has multiple > eyes familiar with the code (in the case the author takes vacation, > etc.). It has the upper hand here. > > Linux has more eyes period, which helps a lot. In addition Linux has more commercial sponsorship - having said that, I've no idea if libdata development has had any such sponsorship... However. I do agree that we (that is FreeBSD) need more folks brave enough to help Soren out with the (S)ATA layer - that means people like you or me deciding to get our hands dirty with this code... best wishes Mark From owner-freebsd-stable@FreeBSD.ORG Mon May 12 08:37:11 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1172C106567C; Mon, 12 May 2008 08:37:11 +0000 (UTC) (envelope-from fbsd-stable@mawer.org) Received: from outbound.icp-qv1-irony-out1.iinet.net.au (outbound.icp-qv1-irony-out1.iinet.net.au [203.59.1.108]) by mx1.freebsd.org (Postfix) with ESMTP id 4FB728FC16; Mon, 12 May 2008 08:37:09 +0000 (UTC) (envelope-from fbsd-stable@mawer.org) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AjEBAFuXJ0jLzq3r/2dsb2JhbAAIqV4 X-IronPort-AV: E=Sophos;i="4.27,472,1204470000"; d="scan'208";a="327956563" Received: from unknown (HELO [10.24.1.1]) ([203.206.173.235]) by outbound.icp-qv1-irony-out1.iinet.net.au with ESMTP; 12 May 2008 16:07:02 +0800 Message-ID: <4827FA43.1050006@mawer.org> Date: Mon, 12 May 2008 18:05:23 +1000 From: Antony Mawer User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) MIME-Version: 1.0 To: Jeremy Chadwick References: <339469.80542.qm@web26912.mail.ukl.yahoo.com> <20080512054624.GA660@eos.sc1.parodius.com> In-Reply-To: <20080512054624.GA660@eos.sc1.parodius.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, John Daniels Subject: Re: 7.0 issues fixed? upgrade timing? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2008 08:37:11 -0000 Jeremy Chadwick wrote: ... >> [20080229] A change in the way that FreeBSD sends TCP options has been reported to cause odd interactions with some cable modem routers. While this issue is still under investigation, a change has been committed to HEAD that returns the option processing to that of FreeBSD 6. So far, this change has shown some promising results. > > Do you have more details on this? Open PR, or a thread I can read? I'm > thinking it might be related to the net.inet.tcp.rfc1323 sysctl, but I'm > not sure. See here: http://groups.google.com/group/mailing.freebsd.net/browse_thread/thread/03e3965192fbc64c/48e037ab2717c7dd?lnk=raot It's fixed in RELENG_7 as far as I'm aware: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netinet/tcp_output.c#rev1.141.2.5 but there was talk of it being an errata candidate for RELENG_7_0, which doesn't look like has happened just yet. --Antony From owner-freebsd-stable@FreeBSD.ORG Mon May 12 08:52:33 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 439CE1065674; Mon, 12 May 2008 08:52:33 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from smtp6.yandex.ru (smtp6.yandex.ru [213.180.200.197]) by mx1.freebsd.org (Postfix) with ESMTP id 4EF8E8FC17; Mon, 12 May 2008 08:52:32 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from ns.kirov.so-cdu.ru ([77.72.136.145]:40135 "EHLO [127.0.0.1]" smtp-auth: "bu7cher" TLS-CIPHER: "DHE-RSA-AES256-SHA keybits 256/256 version TLSv1/SSLv3" TLS-PEER-CN1: ) by mail.yandex.ru with ESMTP id S5472302AbYELIwW (ORCPT + 1 other); Mon, 12 May 2008 12:52:22 +0400 X-Yandex-Spam: 1 X-Yandex-Front: smtp6 X-Yandex-TimeMark: 1210582342 X-MsgDayCount: 28 X-Comment: RFC 2476 MSA function at smtp6.yandex.ru logged sender identity as: bu7cher Message-ID: <4828053E.9080301@yandex.ru> Date: Mon, 12 May 2008 12:52:14 +0400 From: "Andrey V. Elsukov" User-Agent: Mozilla Thunderbird 1.5 (FreeBSD/20051231) MIME-Version: 1.0 To: Mark Kirkwood References: <29626.214.13.212.30.1210554531.squirrel@www.kc8onw.net> <53004.80.91.220.50.1210576570.squirrel@www.kc8onw.net> <20080512072316.GA3845@eos.sc1.parodius.com> <58131.80.91.220.50.1210577810.squirrel@www.kc8onw.net> <20080512074541.GA4667@eos.sc1.parodius.com> <4827F91E.60102@paradise.net.nz> In-Reply-To: <4827F91E.60102@paradise.net.nz> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: Jeremy Chadwick , stable@freebsd.org, jonathan@kc8onw.net Subject: Re: ATA APM and NCQ support in FreeBSD atacontrol X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2008 08:52:33 -0000 Mark Kirkwood wrote: > Linux has more eyes period, which helps a lot. In addition Linux has > more commercial sponsorship - having said that, I've no idea if libdata > development has had any such sponsorship... As I know the most of active libata developers have full-time job in Linux companies, e.g. in Red Hat. -- WBR, Andrey V. Elsukov From owner-freebsd-stable@FreeBSD.ORG Mon May 12 09:38:22 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5C0911065670 for ; Mon, 12 May 2008 09:38:22 +0000 (UTC) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1smout1.broadpark.no (osl1smout1.broadpark.no [80.202.4.58]) by mx1.freebsd.org (Postfix) with ESMTP id 133828FC12 for ; Mon, 12 May 2008 09:38:22 +0000 (UTC) (envelope-from torfinn.ingolfsen@broadpark.no) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=US-ASCII Received: from osl1sminn1.broadpark.no ([80.202.4.59]) by osl1smout1.broadpark.no (Sun Java(tm) System Messaging Server 6.3-3.01 (built Jul 12 2007; 32bit)) with ESMTP id <0K0R001I61F6VX80@osl1smout1.broadpark.no> for freebsd-stable@freebsd.org; Mon, 12 May 2008 11:37:54 +0200 (CEST) Received: from kg-work.kg4.no ([80.202.173.59]) by osl1sminn1.broadpark.no (Sun Java(tm) System Messaging Server 6.3-3.01 (built Jul 12 2007; 32bit)) with SMTP id <0K0R00MI81F6B8B0@osl1sminn1.broadpark.no> for freebsd-stable@freebsd.org; Mon, 12 May 2008 11:37:54 +0200 (CEST) Date: Mon, 12 May 2008 11:37:53 +0200 From: Torfinn Ingolfsen To: freebsd-stable@freebsd.org Message-id: <20080512113753.67295481.torfinn.ingolfsen@broadpark.no> In-reply-to: <339469.80542.qm@web26912.mail.ukl.yahoo.com> References: <339469.80542.qm@web26912.mail.ukl.yahoo.com> X-Mailer: Sylpheed 2.4.8 (GTK+ 2.12.9; i386-portbld-freebsd6.3) X-Face: "t9w2,-X@O^I`jVW\sonI3.,36KBLZE*AL[y9lL[PyFD*r_S:dIL9c[8Y>V42R0"!"yb_zN,f#%.[PYYNq; m"_0v; ~rUM2Yy!zmkh)3&U|u!=T(zyv,MHJv"nDH>OJ`t(@mil461d_B'Uo|'nMwlKe0Mv=kvV?Nh@>Hb<3s_z2jYgZhPb@?Wi^x1a~Hplz1.zH Subject: Re: 7.0 issues fixed? upgrade timing? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2008 09:38:22 -0000 On Mon, 12 May 2008 05:34:47 +0100 (BST) John Daniels wrote: > 1. I have a realtek network card and am using a cable modem > router. Does anyone know if fixes for problems with these (see > below) have been backported from HEAD to RELENG_7? FWIW, I had major troubles with re(4) around 7.0-release, and a while later (I had to use patches). After upgrading to 7-stable on 2008-04-12, re(4) is working for me without patches. HTH -- Regards, Torfinn Ingolfsen From owner-freebsd-stable@FreeBSD.ORG Mon May 12 11:06:00 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2D8311065672 for ; Mon, 12 May 2008 11:06:00 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from angel.ticketswitch.com (angel.ticketswitch.com [IPv6:2002:57e0:1d4e::1]) by mx1.freebsd.org (Postfix) with ESMTP id DF9A78FC26 for ; Mon, 12 May 2008 11:05:59 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from [10.50.50.2] (helo=smaug.rattatosk) by angel.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1JvVqv-000FMC-Ko; Mon, 12 May 2008 12:05:57 +0100 Received: from dilbert.rattatosk ([10.50.50.6] helo=dilbert.ticketswitch.com) by smaug.rattatosk with esmtp (Exim 4.69 (FreeBSD)) (envelope-from ) id 1JvVqv-000GWp-5V; Mon, 12 May 2008 12:05:57 +0100 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1JvVqv-000N1W-4S; Mon, 12 May 2008 12:05:57 +0100 To: freebsd-stable@freebsd.org, torfinn.ingolfsen@broadpark.no In-Reply-To: <20080512113753.67295481.torfinn.ingolfsen@broadpark.no> Message-Id: From: Pete French Date: Mon, 12 May 2008 12:05:57 +0100 Cc: Subject: Re: 7.0 issues fixed? upgrade timing? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2008 11:06:00 -0000 > FWIW, I had major troubles with re(4) around 7.0-release, and a while > later (I had to use patches). After upgrading to 7-stable on > 2008-04-12, re(4) is working for me without patches. I havent tried a recent 'sup, but I also had problems which were fixed by turning off some stuff using "-tso -lro -vlanhwtag -txcsum -rxcsum" in the ifconfig line. I would liek to test a recent patch, but political problems with ohysiucal access to the machine means I am pretty much scared to reboot it :-( Having said that, I;ve tried the patches on a test setup and they seem to work very nicely. -pete. From owner-freebsd-stable@FreeBSD.ORG Mon May 12 11:44:25 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 076241065675 for ; Mon, 12 May 2008 11:44:25 +0000 (UTC) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1smout1.broadpark.no (osl1smout1.broadpark.no [80.202.4.58]) by mx1.freebsd.org (Postfix) with ESMTP id B3E5C8FC0A for ; Mon, 12 May 2008 11:44:24 +0000 (UTC) (envelope-from torfinn.ingolfsen@broadpark.no) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=US-ASCII Received: from osl1sminn1.broadpark.no ([80.202.4.59]) by osl1smout1.broadpark.no (Sun Java(tm) System Messaging Server 6.3-3.01 (built Jul 12 2007; 32bit)) with ESMTP id <0K0R0026779ZQK80@osl1smout1.broadpark.no> for freebsd-stable@freebsd.org; Mon, 12 May 2008 13:44:23 +0200 (CEST) Received: from kg-work.kg4.no ([80.202.173.59]) by osl1sminn1.broadpark.no (Sun Java(tm) System Messaging Server 6.3-3.01 (built Jul 12 2007; 32bit)) with SMTP id <0K0R00BS679YVE42@osl1sminn1.broadpark.no> for freebsd-stable@freebsd.org; Mon, 12 May 2008 13:44:23 +0200 (CEST) Date: Mon, 12 May 2008 13:44:22 +0200 From: Torfinn Ingolfsen To: freebsd-stable@freebsd.org Message-id: <20080512134422.6dbe127c.torfinn.ingolfsen@broadpark.no> In-reply-to: <20080512113753.67295481.torfinn.ingolfsen@broadpark.no> References: <339469.80542.qm@web26912.mail.ukl.yahoo.com> <20080512113753.67295481.torfinn.ingolfsen@broadpark.no> X-Mailer: Sylpheed 2.4.8 (GTK+ 2.12.9; i386-portbld-freebsd6.3) X-Face: "t9w2,-X@O^I`jVW\sonI3.,36KBLZE*AL[y9lL[PyFD*r_S:dIL9c[8Y>V42R0"!"yb_zN,f#%.[PYYNq; m"_0v; ~rUM2Yy!zmkh)3&U|u!=T(zyv,MHJv"nDH>OJ`t(@mil461d_B'Uo|'nMwlKe0Mv=kvV?Nh@>Hb<3s_z2jYgZhPb@?Wi^x1a~Hplz1.zH Subject: Re: 7.0 issues fixed? upgrade timing? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2008 11:44:25 -0000 On Mon, 12 May 2008 11:37:53 +0200 Torfinn Ingolfsen wrote: > FWIW, I had major troubles with re(4) around 7.0-release, and a while > later (I had to use patches). After upgrading to 7-stable on > 2008-04-12, re(4) is working for me without patches. (sigh).. it seems that I spoke to soon. Murphy just showed up. I still get ssh disconnects (see below) on connections _to_ the machine when transferring largish amounts of data (like when upgrading a port). Here is one example (portupgrading the jdk port): /usr/bin/gcc -fno-strict-aliasing -fPIC -W -Wall -Wno-unused -Wno-parentheses -pipe -Damd64 -DARCH='"amd64"' -DRELEASE='"1.6.0_03-p4"' -DFULL_VERSION='"1.6.0_03-p4-root_12_may_2008_13_25-b00"' -D_GNU_SOURCE -D_REENTRANT -D_THREAD_SAFE -D_ALLBSD_SOURCE -D_LP64=1 -I. -I/usr/ports/java/jdk16/work/control/build/bsd-amd64/tmp/java/java.lang.management/management/CClassHeaders -I../../../src/solaris/javavm/export -I../../../src/share/javavm/export -I../../../src/share/javavm/include -I../../../src/solaris/javavm/include -I../../../src/share/native/sun/management -I../../../src/solaris/hpi/include -I../../../src/share/native/common -I../../../src/solaris/native/common -I../../../src/share/native/java/lang/management -I../../../src/solaris/native/java/lang/management -c -o /usr/ports/java/jdk16/work/control/build/bsd-amd64/tmp/java/java.lang.management/management/obj64/ClassLoadingImpl.o ../../../src/share/native/sun/management/ClassLoadingImpl.c Disconnecting: Bad packet length 3601161525. The machine is running: tingo@kg-vm$ uname -a FreeBSD kg-vm.kg4.no 7.0-STABLE FreeBSD 7.0-STABLE #10: Sat Apr 12 21:42:55 CEST 2008 root@kg-vm.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 and has been up for about 14 days: tingo@kg-vm$ uptime 1:36PM up 14 days, 17:42, 7 users, load averages: 2.15, 1.85, 1.34 I see that if_re.c for RELENG_7 has been updated on April 22nd, so I'll upgrade the machine to latest -stable and see if that works better. -- Regards, Torfinn Ingolfsen From owner-freebsd-stable@FreeBSD.ORG Mon May 12 12:32:07 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C63711065684 for ; Mon, 12 May 2008 12:32:07 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id B50D18FC0A for ; Mon, 12 May 2008 12:32:07 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 9E8CA1CC033; Mon, 12 May 2008 05:32:07 -0700 (PDT) Date: Mon, 12 May 2008 05:32:07 -0700 From: Jeremy Chadwick To: Torfinn Ingolfsen Message-ID: <20080512123207.GA12255@eos.sc1.parodius.com> References: <339469.80542.qm@web26912.mail.ukl.yahoo.com> <20080512113753.67295481.torfinn.ingolfsen@broadpark.no> <20080512134422.6dbe127c.torfinn.ingolfsen@broadpark.no> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080512134422.6dbe127c.torfinn.ingolfsen@broadpark.no> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-stable@freebsd.org Subject: Re: 7.0 issues fixed? upgrade timing? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2008 12:32:07 -0000 On Mon, May 12, 2008 at 01:44:22PM +0200, Torfinn Ingolfsen wrote: > On Mon, 12 May 2008 11:37:53 +0200 > Torfinn Ingolfsen wrote: > > > FWIW, I had major troubles with re(4) around 7.0-release, and a while > > later (I had to use patches). After upgrading to 7-stable on > > 2008-04-12, re(4) is working for me without patches. > > (sigh).. it seems that I spoke to soon. Murphy just showed up. I still > get ssh disconnects (see below) on connections _to_ the machine when > transferring largish amounts of data (like when upgrading a port). > Here is one example (portupgrading the jdk port): > /usr/bin/gcc -fno-strict-aliasing -fPIC -W -Wall -Wno-unused -Wno-parentheses -pipe -Damd64 -DARCH='"amd64"' -DRELEASE='"1.6.0_03-p4"' -DFULL_VERSION='"1.6.0_03-p4-root_12_may_2008_13_25-b00"' -D_GNU_SOURCE -D_REENTRANT -D_THREAD_SAFE -D_ALLBSD_SOURCE -D_LP64=1 -I. -I/usr/ports/java/jdk16/work/control/build/bsd-amd64/tmp/java/java.lang.management/management/CClassHeaders -I../../../src/solaris/javavm/export -I../../../src/share/javavm/export -I../../../src/share/javavm/include -I../../../src/solaris/javavm/include -I../../../src/share/native/sun/management -I../../../src/solaris/hpi/include -I../../../src/share/native/common -I../../../src/solaris/native/common -I../../../src/share/native/java/lang/management -I../../../src/solaris/native/java/lang/management -c -o /usr/ports/java/jdk16/work/control/build/bsd-amd64/tmp/java/java.lang.management/management/obj64/ClassLoadingImpl.o ../../../src/share/native/sun/management/ClassLoadingImpl.c > Disconnecting: Bad packet length 3601161525. > > The machine is running: > tingo@kg-vm$ uname -a > FreeBSD kg-vm.kg4.no 7.0-STABLE FreeBSD 7.0-STABLE #10: Sat Apr 12 > 21:42:55 CEST 2008 root@kg-vm.kg4.no:/usr/obj/usr/src/sys/GENERIC > amd64 > > and has been up for about 14 days: > tingo@kg-vm$ uptime > 1:36PM up 14 days, 17:42, 7 users, load averages: 2.15, 1.85, 1.34 > > I see that if_re.c for RELENG_7 has been updated on April 22nd, so I'll upgrade the machine to latest -stable and see if that works better. Is this machine using pf(4) at all? -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Mon May 12 14:11:26 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EF2BE1065672; Mon, 12 May 2008 14:11:26 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id A0C1D8FC0C; Mon, 12 May 2008 14:11:26 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.samsco.home (phobos.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.8/8.13.8) with ESMTP id m4CDswmM037572; Mon, 12 May 2008 07:54:58 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <48284C32.5060707@samsco.org> Date: Mon, 12 May 2008 07:54:58 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.13) Gecko/20080313 SeaMonkey/1.1.9 MIME-Version: 1.0 To: Mark Kirkwood References: <29626.214.13.212.30.1210554531.squirrel@www.kc8onw.net> <53004.80.91.220.50.1210576570.squirrel@www.kc8onw.net> <20080512072316.GA3845@eos.sc1.parodius.com> <58131.80.91.220.50.1210577810.squirrel@www.kc8onw.net> <20080512074541.GA4667@eos.sc1.parodius.com> <4827F91E.60102@paradise.net.nz> In-Reply-To: <4827F91E.60102@paradise.net.nz> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.4 required=3.8 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: Jeremy Chadwick , stable@freebsd.org, jonathan@kc8onw.net Subject: Re: ATA APM and NCQ support in FreeBSD atacontrol X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2008 14:11:27 -0000 Mark Kirkwood wrote: > Jeremy Chadwick wrote: >> >> I am too, but PRs that are 2 years old which include patches for severe >> bugs that affect reliability of RAID is (in my opinion) not acceptable. >> I've been spanked over saying this before ("you don't understand how >> open source works"), but necessity easily supercedes idealism. >> >> Linux's libata has evolved very quickly and very well, and has multiple >> eyes familiar with the code (in the case the author takes vacation, >> etc.). It has the upper hand here. >> >> > Linux has more eyes period, which helps a lot. In addition Linux has > more commercial sponsorship - having said that, I've no idea if libdata > development has had any such sponsorship... > > However. I do agree that we (that is FreeBSD) need more folks brave > enough to help Soren out with the (S)ATA layer - that means people like > you or me deciding to get our hands dirty with this code... > I'm working on adding ATA/SATA support to CAM. Scott From owner-freebsd-stable@FreeBSD.ORG Mon May 12 14:15:52 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AD2C4106566C for ; Mon, 12 May 2008 14:15:52 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 998788FC23 for ; Mon, 12 May 2008 14:15:52 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 57A261CC033; Mon, 12 May 2008 07:15:52 -0700 (PDT) Date: Mon, 12 May 2008 07:15:52 -0700 From: Jeremy Chadwick To: Scott Long Message-ID: <20080512141552.GA14963@eos.sc1.parodius.com> References: <29626.214.13.212.30.1210554531.squirrel@www.kc8onw.net> <53004.80.91.220.50.1210576570.squirrel@www.kc8onw.net> <20080512072316.GA3845@eos.sc1.parodius.com> <58131.80.91.220.50.1210577810.squirrel@www.kc8onw.net> <20080512074541.GA4667@eos.sc1.parodius.com> <4827F91E.60102@paradise.net.nz> <48284C32.5060707@samsco.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48284C32.5060707@samsco.org> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: stable@freebsd.org, jonathan@kc8onw.net, Mark Kirkwood Subject: Re: ATA APM and NCQ support in FreeBSD atacontrol X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2008 14:15:52 -0000 On Mon, May 12, 2008 at 07:54:58AM -0600, Scott Long wrote: > Mark Kirkwood wrote: >> Jeremy Chadwick wrote: >>> >>> I am too, but PRs that are 2 years old which include patches for severe >>> bugs that affect reliability of RAID is (in my opinion) not acceptable. >>> I've been spanked over saying this before ("you don't understand how >>> open source works"), but necessity easily supercedes idealism. >>> >>> Linux's libata has evolved very quickly and very well, and has multiple >>> eyes familiar with the code (in the case the author takes vacation, >>> etc.). It has the upper hand here. >>> >>> >> Linux has more eyes period, which helps a lot. In addition Linux has more >> commercial sponsorship - having said that, I've no idea if libdata >> development has had any such sponsorship... >> >> However. I do agree that we (that is FreeBSD) need more folks brave enough >> to help Soren out with the (S)ATA layer - that means people like you or me >> deciding to get our hands dirty with this code... >> > > I'm working on adding ATA/SATA support to CAM. ! Wow... I had no idea you were working on such! Ideally that'd be the best implementation. Thanks a ton for working on it! If you need someone to test patches (I figure they'll be for -CURRENT, but our test boxes run RELENG_7), let me know and I'll be more than happy to give them a shot. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Mon May 12 16:38:28 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8C09A106566C; Mon, 12 May 2008 16:38:28 +0000 (UTC) (envelope-from fanf2@hermes.cam.ac.uk) Received: from ppsw-6.csi.cam.ac.uk (ppsw-6.csi.cam.ac.uk [131.111.8.136]) by mx1.freebsd.org (Postfix) with ESMTP id 4EF668FC17; Mon, 12 May 2008 16:38:28 +0000 (UTC) (envelope-from fanf2@hermes.cam.ac.uk) X-Cam-SpamDetails: Not scanned X-Cam-AntiVirus: No virus found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from hermes-1.csi.cam.ac.uk ([131.111.8.51]:51383) by ppsw-6.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.156]:25) with esmtpa (EXTERNAL:fanf2) id 1JvaWy-000382-Ku (Exim 4.67) (return-path ); Mon, 12 May 2008 17:05:40 +0100 Received: from fanf2 (helo=localhost) by hermes-1.csi.cam.ac.uk (hermes.cam.ac.uk) with local-esmtp id 1JvaWy-00078L-Ex (Exim 4.67) (return-path ); Mon, 12 May 2008 17:05:40 +0100 Date: Mon, 12 May 2008 17:05:40 +0100 From: Tony Finch X-X-Sender: fanf2@hermes-1.csi.cam.ac.uk To: Dr Joe Karthauser In-Reply-To: <20080511102730.DBD0A600F@mailhost.tao.org.uk> Message-ID: References: <20080511102730.DBD0A600F@mailhost.tao.org.uk> User-Agent: Alpine 1.00 (LSU 882 2007-12-20) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Tony Finch Cc: freebsd-hubs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: cvsup.uk.FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2008 16:38:28 -0000 On Sun, 11 May 2008, Dr Joe Karthauser wrote: > > I have reclassified this faulty mirror as cvsup1 and made cvsup a cname to > cvsup3, which is the most recent addition and best hardware available. In > the future we will always point to the most available machine in this way. Looks like I'm getting a bit more traffic than before - peaking at over 100 logins an hour. Tony. -- f.anthony.n.finch http://dotat.at/ FORTIES CROMARTY FORTH TYNE DOGGER: NORTHEAST 4 OR 5, OCCASIONALLY 6 AT FIRST IN CROMARTY. MODERATE. EXTENSIVE FOG AT FIRST IN TYNE, OTHERWISE FOG PATCHES, THEN FAIR. MODERATE OR GOOD, OCCASIONALLY VERY POOR. From owner-freebsd-stable@FreeBSD.ORG Mon May 12 18:43:54 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 88B96106566B for ; Mon, 12 May 2008 18:43:54 +0000 (UTC) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1smout1.broadpark.no (osl1smout1.broadpark.no [80.202.4.58]) by mx1.freebsd.org (Postfix) with ESMTP id 433F38FC15 for ; Mon, 12 May 2008 18:43:54 +0000 (UTC) (envelope-from torfinn.ingolfsen@broadpark.no) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=US-ASCII Received: from osl1sminn1.broadpark.no ([80.202.4.59]) by osl1smout1.broadpark.no (Sun Java(tm) System Messaging Server 6.3-3.01 (built Jul 12 2007; 32bit)) with ESMTP id <0K0R005Y8QP5P510@osl1smout1.broadpark.no> for freebsd-stable@freebsd.org; Mon, 12 May 2008 20:43:53 +0200 (CEST) Received: from kg-work.kg4.no ([80.202.173.59]) by osl1sminn1.broadpark.no (Sun Java(tm) System Messaging Server 6.3-3.01 (built Jul 12 2007; 32bit)) with SMTP id <0K0R007UZQP4GF81@osl1sminn1.broadpark.no> for freebsd-stable@freebsd.org; Mon, 12 May 2008 20:43:52 +0200 (CEST) Date: Mon, 12 May 2008 20:43:52 +0200 From: Torfinn Ingolfsen To: freebsd-stable@freebsd.org Message-id: <20080512204352.e889411e.torfinn.ingolfsen@broadpark.no> In-reply-to: <20080512123207.GA12255@eos.sc1.parodius.com> References: <339469.80542.qm@web26912.mail.ukl.yahoo.com> <20080512113753.67295481.torfinn.ingolfsen@broadpark.no> <20080512134422.6dbe127c.torfinn.ingolfsen@broadpark.no> <20080512123207.GA12255@eos.sc1.parodius.com> X-Mailer: Sylpheed 2.4.8 (GTK+ 2.12.9; i386-portbld-freebsd6.3) X-Face: "t9w2,-X@O^I`jVW\sonI3.,36KBLZE*AL[y9lL[PyFD*r_S:dIL9c[8Y>V42R0"!"yb_zN,f#%.[PYYNq; m"_0v; ~rUM2Yy!zmkh)3&U|u!=T(zyv,MHJv"nDH>OJ`t(@mil461d_B'Uo|'nMwlKe0Mv=kvV?Nh@>Hb<3s_z2jYgZhPb@?Wi^x1a~Hplz1.zH Subject: Re: 7.0 issues fixed? upgrade timing? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2008 18:43:54 -0000 On Mon, 12 May 2008 05:32:07 -0700 Jeremy Chadwick wrote: > Is this machine using pf(4) at all? No. Not intentionally, and not in any way that I can tell: root@kg-vm# uname -a FreeBSD kg-vm.kg4.no 7.0-STABLE FreeBSD 7.0-STABLE #11: Mon May 12 16:39:19 CEST 2008 root@kg-vm.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 root@kg-vm# ls -l /dev/pf ls: /dev/pf: No such file or directory root@kg-vm# kldstat Id Refs Address Size Name 1 18 0xffffffff80100000 b09578 kernel 2 1 0xffffffff80c0a000 1a070 snd_hda.ko 3 2 0xffffffff80c25000 68a40 sound.ko 4 1 0xffffffff80c8e000 5100 atapicam.ko 5 1 0xffffffffb1a0f000 1256a ng_btsocket.ko 6 5 0xffffffffb1a22000 92b4 netgraph.ko 7 3 0xffffffffb1a2c000 89a ng_bluetooth.ko 8 1 0xffffffffb1a32000 35e2 vkbd.ko 9 1 0xffffffffb1a36000 aefa fuse.ko 10 1 0xffffffffb1aa5000 56b2 aio.ko 11 1 0xffffffffb1c4b000 268dc kqemu.ko 12 1 0xffffffffb1af0000 4266 ng_ubt.ko 13 1 0xffffffffb1cc7000 8e1a ng_hci.ko 14 1 0xffffffffb1cd0000 ba78 ng_l2cap.ko 15 1 0xffffffffb1ace000 1a9a ng_socket.ko (as you can see, the machine is now updated to latest 7-stable) -- Regards, Torfinn Ingolfsen From owner-freebsd-stable@FreeBSD.ORG Mon May 12 20:38:53 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2A87F1065685 for ; Mon, 12 May 2008 20:38:53 +0000 (UTC) (envelope-from bahamasfranks@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.244]) by mx1.freebsd.org (Postfix) with ESMTP id CF2408FC28 for ; Mon, 12 May 2008 20:38:52 +0000 (UTC) (envelope-from bahamasfranks@gmail.com) Received: by an-out-0708.google.com with SMTP id b33so586370ana.13 for ; Mon, 12 May 2008 13:38:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=/72uUoiyz4BAViuHa7uxhdvjM4v3iTYj1M13Z1bnL1g=; b=nuMQEQcj+IvrZE//hiBEWtYUO92lYZQXLsHSNm3i+s66BrQyHxNXkF7wTvH7QeqEt2bcY+cLUmhTlXjrhLr3UGQaWOEgd7SjdcqBu2ciCNo/A6ht1bZJsKFzgP3Xo87OTwHgrpbWgt09GcQLvdH40nZd4h8xvfCzUUxhs/iuKH0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=OFse9apOn4rWC3eKGVgJRSManIVWebZDk3ZIsvAPvHIHSe/lykD+cFZ8AZLsGjZEb6eO46KdGk4HDKQsIBAT9qnBJNTK+mop1NL5p88/zYK4PutPvqwoEN6x45V3bFzZNDrdUV4DfIFuHGeI9UKaBfLnFJJdSKppuJa9QGoG4no= Received: by 10.100.33.4 with SMTP id g4mr8870580ang.111.1210624731983; Mon, 12 May 2008 13:38:51 -0700 (PDT) Received: by 10.100.239.17 with HTTP; Mon, 12 May 2008 13:38:51 -0700 (PDT) Message-ID: <539c60b90805121338n439c1a62sab5be6f6ea9485ff@mail.gmail.com> Date: Mon, 12 May 2008 13:38:51 -0700 From: "Steve Franks" Sender: bahamasfranks@gmail.com To: "Roland Smith" , freebsd-stable@freebsd.org In-Reply-To: <20080429214640.GA85715@slackbox.xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <539c60b90804111420kcb73e6do8a20dce574d13864@mail.gmail.com> <20080412213225.GB24224@slackbox.xs4all.nl> <539c60b90804141549u6a138ad9u9c77bbfcbbad0ff3@mail.gmail.com> <20080415175347.GA29045@slackbox.xs4all.nl> <539c60b90804291032v4a7e80d0w205354d4bf1be842@mail.gmail.com> <20080429214640.GA85715@slackbox.xs4all.nl> X-Google-Sender-Auth: 73432ffa04f47900 Cc: Subject: Re: umass causes panic on 7 amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: stevefranks@ieee.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2008 20:38:53 -0000 I have added options USB DEBUG to my kernconf file ("DYSTANT"). Here is the backtrace: Steve [steve@dystant /usr/obj/usr/src/sys/DYSTANT]$ sudo kgdb kernel.debug /var/crash/vmcore.6 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd". Unread portion of the kernel message buffer: umass0: on uhub2 umass0: SCSI over (unknown 0x00); quirks = 0x0100 panic: /usr/src/sys/dev/usb/umass.c:1453: Unknown proto 0x100 cpuid = 0 Uptime: 3m1s Physical memory: 1002 MB Dumping 97 MB: 82 66 50 34 18 2 #0 doadump () at pcpu.h:194 194 __asm __volatile("movq %%gs:0,%0" : "=r" (td)); (kgdb) bt #0 doadump () at pcpu.h:194 #1 0x0000000000000004 in ?? () #2 0xffffffff8049d169 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409 #3 0xffffffff8049d56d in panic (fmt=0x104
) at /usr/src/sys/kern/kern_shutdown.c:563 #4 0xffffffff80412ee7 in umass_attach (self=0xffffff00014ae300) at /usr/src/sys/dev/usb/umass.c:1452 #5 0xffffffff804bf9c4 in device_attach (dev=0xffffff00014ae300) at device_if.h:178 #6 0xffffffff8041b8e1 in usbd_new_device (parent=0xffffff0001246000, bus=0xffffffff80e49000, depth=Variable "depth" is not available. ) at /usr/src/sys/dev/usb/usb_subr.c:932 #7 0xffffffff8040ebb2 in uhub_explore (dev=0xffffff0001245c00) at /usr/src/sys/dev/usb/uhub.c:523 #8 0xffffffff804177da in usb_discover (v=0xffffff000126e680) at /usr/src/sys/dev/usb/usb.c:724 #9 0xffffffff80418990 in usb_event_thread (arg=Variable "arg" is not available. ) at /usr/src/sys/dev/usb/usb.c:440 #10 0xffffffff8047e883 in fork_exit (callout=0xffffffff80418880 , arg=0xffffff000126e680, frame=0xffffffffa035ac80) at /usr/src/sys/kern/kern_fork.c:781 #11 0xffffffff8073b4ae in fork_trampoline () at /usr/src/sys/amd64/amd64/exception.S:415 #12 0x0000000000000000 in ?? () #13 0x0000000000000000 in ?? () #14 0x0000000000000001 in ?? () #15 0x0000000000000000 in ?? () #16 0x0000000000000000 in ?? () #17 0x0000000000000000 in ?? () #18 0x0000000000000000 in ?? () #19 0x0000000000000000 in ?? () #20 0x0000000000000000 in ?? () #21 0x0000000000000000 in ?? () #22 0x0000000000000000 in ?? () #23 0x0000000000000000 in ?? () #24 0x0000000000000000 in ?? () #25 0x0000000000000000 in ?? () #26 0x0000000000000000 in ?? () #27 0x0000000000000000 in ?? () #28 0x0000000000000000 in ?? () #29 0x0000000000000000 in ?? () #30 0x0000000000000000 in ?? () #31 0x0000000000000000 in ?? () #32 0x0000000000000000 in ?? () #33 0x0000000000000000 in ?? () #34 0x0000000000000000 in ?? () #35 0x0000000000000000 in ?? () #36 0x0000000000dd8000 in ?? () #37 0x0000000000000000 in ?? () #38 0x0000000000000004 in ?? () #39 0xffffff00012788d0 in ?? () #40 0xffffff0001087340 in ?? () #41 0xffffff0001258680 in ?? () #42 0xffffffffa0359c48 in ?? () #43 0xffffff0001258680 in ?? () #44 0xffffffff804bae29 in sched_switch (td=0xffffff000126e680, newtd=0xffffffff80418880, flags=0) at /usr/src/sys/kern/sched_4bsd.c:905 #45 0x0000000000000000 in ?? () #46 0x0000000000000000 in ?? () #47 0x0000000000000000 in ?? () #48 0x0000000000000000 in ?? () #49 0x0000000000000000 in ?? () #50 0x0000000000000000 in ?? () #51 0x0000000000000000 in ?? () #52 0x0000000000000000 in ?? () #53 0x0000000000000000 in ?? () #54 0x0000000000000000 in ?? () #55 0x0000000000000000 in ?? () #56 0x0000000000000000 in ?? () #57 0x0000000000000000 in ?? () #58 0x0000000000000000 in ?? () #59 0x0000000000000000 in ?? () #60 0x0000000000000000 in ?? () #61 0x0000000000000000 in ?? () #62 0x0000000000000000 in ?? () #63 0x0000000000000000 in ?? () #64 0x0000000000000000 in ?? () #65 0x0000000000000000 in ?? () #66 0x0000000000000000 in ?? () #67 0x0000000000000000 in ?? () #68 0x0000000000000000 in ?? () #69 0x0000000000000000 in ?? () #70 0x0000000000000000 in ?? () #71 0x0000000000000000 in ?? () ---Type to continue, or q to quit--- #72 0x0000000000000000 in ?? () #73 0x0000000000000000 in ?? () #74 0x0000000000000000 in ?? () #75 0x0000000000000000 in ?? () #76 0x0000000000000000 in ?? () #77 0x0000000000000000 in ?? () #78 0x0000000000000000 in ?? () #79 0x0000000000000000 in ?? () #80 0x0000000000000000 in ?? () #81 0x0000000000000000 in ?? () #82 0x0000000000000000 in ?? () #83 0x0000000000000000 in ?? () #84 0x0000000000000000 in ?? () #85 0x0000000000000000 in ?? () #86 0x0000000000000000 in ?? () #87 0x0000000000000000 in ?? () #88 0x0000000000000000 in ?? () #89 0x0000000000000000 in ?? () #90 0x0000000000000000 in ?? () #91 0x0000000000000000 in ?? () #92 0x0000000000000000 in ?? () #93 0x0000000000000000 in ?? () #94 0x0000000000000000 in ?? () #95 0x0000000000000000 in ?? () #96 0x0000000000000000 in ?? () #97 0x0000000000000000 in ?? () #98 0x0000000000000000 in ?? () #99 0x0000000000000000 in ?? () #100 0x0000000000000000 in ?? () #101 0x0000000000000000 in ?? () #102 0x0000000000000000 in ?? () #103 0x0000000000000000 in ?? () #104 0x0000000000000000 in ?? () #105 0x0000000000000000 in ?? () #106 0x0000000000000000 in ?? () #107 0x0000000000000000 in ?? () #108 0x0000000000000000 in ?? () #109 0x0000000000000000 in ?? () #110 0x0000000000000000 in ?? () #111 0x0000000000000000 in ?? () #112 0x0000000000000000 in ?? () #113 0x0000000000000000 in ?? () #114 0x0000000000000000 in ?? () #115 0x0000000000000000 in ?? () #116 0x0000000000000000 in ?? () #117 0x01263f4001263f80 in ?? () #118 0x01263ec001263f00 in ?? () #119 0x01263e4001263e80 in ?? () #120 0x01263dc001263e00 in ?? () #121 0x01263d4001263d80 in ?? () #122 0x01263cc001263d00 in ?? () #123 0x01263c4001263c80 in ?? () #124 0x01263bc001263c00 in ?? () #125 0x01263b4001263b80 in ?? () #126 0x01263ac001263b00 in ?? () #127 0x01263a4001263a80 in ?? () #128 0x012639c001263a00 in ?? () #129 0x0126394001263980 in ?? () #130 0x012638c001263900 in ?? () #131 0x0126384001263880 in ?? () #132 0x012637c001263800 in ?? () #133 0x0126374001263780 in ?? () #134 0x012636c001263700 in ?? () #135 0x0126364001263680 in ?? () #136 0x012635c001263600 in ?? () #137 0x0126354001263580 in ?? () #138 0x012634c001263500 in ?? () #139 0x0126344001263480 in ?? () #140 0x012633c001263400 in ?? () #141 0x0126334001263380 in ?? () #142 0x012632c001263300 in ?? () #143 0x0126324001263280 in ?? () #144 0x012631c001263200 in ?? () #145 0x0126314001263180 in ?? () #146 0x012630c001263100 in ?? () ---Type to continue, or q to quit--- #147 0x0126304001263080 in ?? () #148 0x01265fc001263000 in ?? () #149 0x01265f4001265f80 in ?? () #150 0x01265ec001265f00 in ?? () #151 0x01265e4001265e80 in ?? () #152 0x01265dc001265e00 in ?? () #153 0x01265d4001265d80 in ?? () #154 0x01265cc001265d00 in ?? () #155 0x01265c4001265c80 in ?? () #156 0x01265bc001265c00 in ?? () #157 0x01265b4001265b80 in ?? () #158 0x01265ac001265b00 in ?? () #159 0x01265a4001265a80 in ?? () #160 0x012659c001265a00 in ?? () #161 0x0126594001265980 in ?? () #162 0x012658c001265900 in ?? () #163 0x0126584001265880 in ?? () #164 0x012657c001265800 in ?? () #165 0x0126574001265780 in ?? () #166 0x012656c001265700 in ?? () #167 0x0126564001265680 in ?? () #168 0x012655c001265600 in ?? () #169 0x0126554001265580 in ?? () #170 0x012654c001265500 in ?? () #171 0x0126544001265480 in ?? () #172 0x012653c001265400 in ?? () #173 0x0126534001265380 in ?? () #174 0x012652c001265300 in ?? () #175 0x0126524001265280 in ?? () #176 0x012651c001265200 in ?? () #177 0x0126514001265180 in ?? () #178 0x012650c001265100 in ?? () #179 0x0126504001265080 in ?? () #180 0x01267fc001265000 in ?? () #181 0x01263f4001263f80 in ?? () #182 0x01263ec001263f00 in ?? () #183 0x01263e4001263e80 in ?? () #184 0x01263dc001263e00 in ?? () #185 0x01263d4001263d80 in ?? () #186 0x01263cc001263d00 in ?? () #187 0x01263c4001263c80 in ?? () #188 0x01263bc001263c00 in ?? () #189 0x01263b4001263b80 in ?? () #190 0x01263ac001263b00 in ?? () #191 0x01263a4001263a80 in ?? () #192 0x012639c001263a00 in ?? () #193 0x0126394001263980 in ?? () #194 0x012638c001263900 in ?? () #195 0x0126384001263880 in ?? () #196 0x012637c001263800 in ?? () #197 0x0126374001263780 in ?? () #198 0x012636c001263700 in ?? () #199 0x0126364001263680 in ?? () #200 0x012635c001263600 in ?? () #201 0x0126354001263580 in ?? () #202 0x012634c001263500 in ?? () #203 0x0126344001263480 in ?? () #204 0x012633c001263400 in ?? () #205 0x0126334001263380 in ?? () #206 0x012632c001263300 in ?? () #207 0x0126324001263280 in ?? () #208 0x012631c001263200 in ?? () #209 0x0126314001263180 in ?? () #210 0x012630c001263100 in ?? () #211 0x0126304001263080 in ?? () #212 0x01265fc001263000 in ?? () #213 0x01265f4001265f80 in ?? () #214 0x01265ec001265f00 in ?? () #215 0x01265e4001265e80 in ?? () #216 0x01265dc001265e00 in ?? () From owner-freebsd-stable@FreeBSD.ORG Mon May 12 22:50:52 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B1C4C1065675 for ; Mon, 12 May 2008 22:50:52 +0000 (UTC) (envelope-from rsmith@xs4all.nl) Received: from smtp-vbr17.xs4all.nl (smtp-vbr17.xs4all.nl [194.109.24.37]) by mx1.freebsd.org (Postfix) with ESMTP id 286DC8FC0C for ; Mon, 12 May 2008 22:50:51 +0000 (UTC) (envelope-from rsmith@xs4all.nl) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr17.xs4all.nl (8.13.8/8.13.8) with ESMTP id m4CMonFS044277; Tue, 13 May 2008 00:50:50 +0200 (CEST) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id 3FE9AB854; Tue, 13 May 2008 00:50:49 +0200 (CEST) Date: Tue, 13 May 2008 00:50:49 +0200 From: Roland Smith To: Steve Franks Message-ID: <20080512225049.GA35802@slackbox.xs4all.nl> Mail-Followup-To: Steve Franks , freebsd-stable@freebsd.org References: <539c60b90804111420kcb73e6do8a20dce574d13864@mail.gmail.com> <20080412213225.GB24224@slackbox.xs4all.nl> <539c60b90804141549u6a138ad9u9c77bbfcbbad0ff3@mail.gmail.com> <20080415175347.GA29045@slackbox.xs4all.nl> <539c60b90804291032v4a7e80d0w205354d4bf1be842@mail.gmail.com> <20080429214640.GA85715@slackbox.xs4all.nl> <539c60b90805121338n439c1a62sab5be6f6ea9485ff@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="OgqxwSJOaUobr8KG" Content-Disposition: inline In-Reply-To: <539c60b90805121338n439c1a62sab5be6f6ea9485ff@mail.gmail.com> X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 X-GPG-Key: http://www.xs4all.nl/~rsmith/pubkey.txt X-GPG-Notice: If this message is not signed, don't assume I sent it! User-Agent: Mutt/1.5.17 (2007-11-01) X-Virus-Scanned: by XS4ALL Virus Scanner Cc: freebsd-stable@freebsd.org Subject: Re: umass causes panic on 7 amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2008 22:50:52 -0000 --OgqxwSJOaUobr8KG Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, May 12, 2008 at 01:38:51PM -0700, Steve Franks wrote: > I have added options USB DEBUG to my kernconf file ("DYSTANT"). Here > is the backtrace: >=20 > Steve >=20 > [steve@dystant /usr/obj/usr/src/sys/DYSTANT]$ sudo kgdb kernel.debug > /var/crash/vmcore.6 > [GDB will not be able to debug user-mode threads: > /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] > GNU gdb 6.1.1 [FreeBSD] > Copyright 2004 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you = are > welcome to change it and/or distribute copies of it under certain conditi= ons. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for detail= s. > This GDB was configured as "amd64-marcel-freebsd". >=20 > Unread portion of the kernel message buffer: > umass0: on u= hub2 > umass0: SCSI over (unknown 0x00); quirks =3D 0x0100 > panic: /usr/src/sys/dev/usb/umass.c:1453: Unknown proto 0x100 It looks like the camera is not returning a wire protocol. You definitely need to take this to the -usb list. Roland --=20 R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) --OgqxwSJOaUobr8KG Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkgoyckACgkQEnfvsMMhpyUfMQCfRv46Qsnf/kkd+H+6GokD8pAc 03gAoKcJo7m6TgRSY+sQMUU7rFL7+U3D =x6oa -----END PGP SIGNATURE----- --OgqxwSJOaUobr8KG-- From owner-freebsd-stable@FreeBSD.ORG Mon May 12 23:19:28 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A530E106567C for ; Mon, 12 May 2008 23:19:28 +0000 (UTC) (envelope-from bahamasfranks@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.243]) by mx1.freebsd.org (Postfix) with ESMTP id 520FF8FC1D for ; Mon, 12 May 2008 23:19:28 +0000 (UTC) (envelope-from bahamasfranks@gmail.com) Received: by an-out-0708.google.com with SMTP id b33so601648ana.13 for ; Mon, 12 May 2008 16:19:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=MIqMyjMbBL18qOpIMz4TW3Ad6+uolrLPUS4trPYPsTM=; b=Z5YJsG+nkIvL8qAQ9VoJiNyX6XaAazJeOHJKAX9tfpOetFFUYSnRtiFBNsq8b601+GZh+4wTxxaaW8tzK0i/k+gx840ypPevNO2v8kFlXdru4yTc38eJEKR5AgQrBbRmXy+znzSGBXU7M6HNObqK/OEuOfiIi5vHFBE/Pm4LD3s= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=sBy4La4lmcHoxpAjLA4GfW9mQSw8//wMXB53/GquxeHyNpePhml7QT7n+hGNcRCSpohL5v+YjD57jYuQisSt9tEqJNhvJJ18g/Y/l1hGYovTs0fkH8s6bNyvFTRNcye2N5h9zKjrcPYI2udYVMp43OqU7MVSnFscXclimcaDYwM= Received: by 10.100.91.17 with SMTP id o17mr9068652anb.145.1210634367590; Mon, 12 May 2008 16:19:27 -0700 (PDT) Received: by 10.100.239.17 with HTTP; Mon, 12 May 2008 16:19:27 -0700 (PDT) Message-ID: <539c60b90805121619g3d7afe70yd7e733fea012ae9d@mail.gmail.com> Date: Mon, 12 May 2008 16:19:27 -0700 From: "Steve Franks" Sender: bahamasfranks@gmail.com To: "Roland Smith" , freebsd-stable@freebsd.org, freebsd-usb@freebsd.org In-Reply-To: <20080512225049.GA35802@slackbox.xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <539c60b90804111420kcb73e6do8a20dce574d13864@mail.gmail.com> <20080412213225.GB24224@slackbox.xs4all.nl> <539c60b90804141549u6a138ad9u9c77bbfcbbad0ff3@mail.gmail.com> <20080415175347.GA29045@slackbox.xs4all.nl> <539c60b90804291032v4a7e80d0w205354d4bf1be842@mail.gmail.com> <20080429214640.GA85715@slackbox.xs4all.nl> <539c60b90805121338n439c1a62sab5be6f6ea9485ff@mail.gmail.com> <20080512225049.GA35802@slackbox.xs4all.nl> X-Google-Sender-Auth: c37163105590529a Cc: Subject: Re: umass causes panic on 7 amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: stevefranks@ieee.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2008 23:19:28 -0000 On Mon, May 12, 2008 at 3:50 PM, Roland Smith wrote: > On Mon, May 12, 2008 at 01:38:51PM -0700, Steve Franks wrote: > > I have added options USB DEBUG to my kernconf file ("DYSTANT"). Here > > is the backtrace: > > > > Steve > > > > [steve@dystant /usr/obj/usr/src/sys/DYSTANT]$ sudo kgdb kernel.debug > > /var/crash/vmcore.6 > > [GDB will not be able to debug user-mode threads: > > /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] > > GNU gdb 6.1.1 [FreeBSD] > > Copyright 2004 Free Software Foundation, Inc. > > GDB is free software, covered by the GNU General Public License, and you are > > welcome to change it and/or distribute copies of it under certain conditions. > > Type "show copying" to see the conditions. > > There is absolutely no warranty for GDB. Type "show warranty" for details. > > This GDB was configured as "amd64-marcel-freebsd". > > > > Unread portion of the kernel message buffer: > > umass0: on uhub2 > > umass0: SCSI over (unknown 0x00); quirks = 0x0100 > > panic: /usr/src/sys/dev/usb/umass.c:1453: Unknown proto 0x100 > > It looks like the camera is not returning a wire protocol. > You definitely need to take this to the -usb list. > > > > Roland > -- > R.F.Smith http://www.xs4all.nl/~rsmith/ > [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] > pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) > Still shouldn't cause a panic, should it? Steve From owner-freebsd-stable@FreeBSD.ORG Tue May 13 01:22:38 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E88D01065679 for ; Tue, 13 May 2008 01:22:38 +0000 (UTC) (envelope-from bazzoola@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.176]) by mx1.freebsd.org (Postfix) with ESMTP id 9D2E98FC17 for ; Tue, 13 May 2008 01:22:38 +0000 (UTC) (envelope-from bazzoola@gmail.com) Received: by py-out-1112.google.com with SMTP id u52so2732027pyb.10 for ; Mon, 12 May 2008 18:22:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:from:to:content-type:content-transfer-encoding:mime-version:subject:date:x-mailer; bh=DUJfmpr0n/Nwe2QjKljlwcYQRV4Upspxs8zxFFO/vXc=; b=q/JemqBxQW6IFXIAgn//K1Ebm9wFki/QIyHnPriAGjalevFMsp3W8Xer0YOGewk7p+cil0DJWtW+KNBbq047wUXv1CIDpkEoQDVhkqwuoSabR1LttwrQVBCiYb/UZ5WqsGm/z0wa06zWZLw+5AQumjGJz/ZKLmulprTjCf8LBVg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:content-type:content-transfer-encoding:mime-version:subject:date:x-mailer; b=gESIkYLAjBEMvYfJrwISFyARvLozBAp/BCymx5SfoG/FaIXEmHzYX+8wrWPbd/OP8hCBBMmxbSpjJ7aakp9Mk8kHhcY52h0f9f/j1dv5DpayZJEUVSDfKA6F2JZy0JbZ4dlDmo0wrJmfLqWbZC9fBE3FPtQlNh6yFo9viDZ6ph4= Received: by 10.35.50.5 with SMTP id c5mr14831089pyk.26.1210640183956; Mon, 12 May 2008 17:56:23 -0700 (PDT) Received: from ?10.0.1.111? ( [99.147.176.243]) by mx.google.com with ESMTPS id f57sm25810442pyh.31.2008.05.12.17.56.23 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 12 May 2008 17:56:23 -0700 (PDT) Message-Id: From: bazzoola To: freebsd-stable Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v919.2) Date: Mon, 12 May 2008 20:56:20 -0400 X-Mailer: Apple Mail (2.919.2) Subject: kqemu support: not compiled X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2008 01:22:39 -0000 Greetings, I just cant get kqemu to work on my AMD64 SMP! I setenv WITH_KQEMU I compiled the port with make -DWITH_KQEMU I edited src.conf and added WITH_KQEMU=yes I make config and checked KQEMU ALPHA support I am running #uname -a FreeBSD Aa.bsd 7.0-STABLE FreeBSD 7.0-STABLE #3: Mon Apr 21 05:56:16 CDT 2008 root@Aa.bsd:/usr/obj/usr/src/sys/GENERIC amd64 #pkg_info | grep qemu kqemu-kmod-1.3.0.p11_6 qemu-devel-0.9.1s.20080302_6 latest as you as see ^^^ any ideas? From owner-freebsd-stable@FreeBSD.ORG Tue May 13 02:03:44 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 013FD106564A for ; Tue, 13 May 2008 02:03:44 +0000 (UTC) (envelope-from alex.kovalenko@verizon.net) Received: from vms173003pub.verizon.net (vms173003pub.verizon.net [206.46.173.3]) by mx1.freebsd.org (Postfix) with ESMTP id D00A18FC0C for ; Tue, 13 May 2008 02:03:43 +0000 (UTC) (envelope-from alex.kovalenko@verizon.net) Received: from [10.0.3.231] ([70.111.2.75]) by vms173003.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0K0S0022584HWCN0@vms173003.mailsrvcs.net> for stable@freebsd.org; Mon, 12 May 2008 20:00:19 -0500 (CDT) Date: Mon, 12 May 2008 21:02:22 -0400 From: "Alexandre \"Sunny\" Kovalenko" To: stable@freebsd.org Message-id: <1210640542.1008.33.camel@RabbitsDen> MIME-version: 1.0 X-Mailer: Evolution 2.22.1.1 FreeBSD GNOME Team Port Content-type: multipart/mixed; boundary="Boundary_(ID_UsNYKDm2UnlTuceC8ZYJfQ)" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Hard(?) lock when reassociating ath with wpa_supplicant on RELENG_7 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2008 02:03:44 -0000 --Boundary_(ID_UsNYKDm2UnlTuceC8ZYJfQ) Content-type: text/plain; charset=UTF-8 Content-transfer-encoding: 8BIT I seem to be able to lock my machine by going into wpa_cli and asking it to 'reassoc'. The reason for question mark after "hard" is that debug information (caused by wlandebug and athdebug) is being printed on the console. The only way to get machine's attention is to hold power button for 8 seconds. Note: manual reassociation is just the handy way to reproduce the problem -- I have had machine locking up on me the whole day long completely on its own. Below are, what I think, relevant pieces of information. If anything is missing, please, chastise me appropriately and will do my best to provide. I have rigged firewire console, but am unable to break into the debugger locally or remotely. While I am on the subject, I would appreciate couple of the troubleshooting suggestions: * is there any way to get sysctl dev.ath.0.debug to appear, other then defining ATH_DEBUG in something like /usr/src/sys/dev/ath/ah_osdep.h? * is there minimal, but still usable mask for athdebug and wlandebug? I have started with 0xFFFFFFFF and kept trimming likely high-volume settings until output slowed down to the reasonable pace. * what facility does wpa_supplicant use, when forced to syslog by -s switch? ======================================================================= * OS: RELENG_7 cvsup'ed on May 11th @ 15:30EST, if_ath is loaded as the module * HW: ath0@pci0:3:0:0: class=0x020000 card=0x058a1014 chip=0x1014168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = 'AR5212 Atheros AR5212 802.11abg wireless' class = network subclass = ethernet ath0: mem 0xedf00000-0xedf0ffff irq 17 at device 0.0 on pci3 ath0: [ITHREAD] ath0: using obsoleted if_watchdog interface ath0: Ethernet address: xx:xx:xx:xx:xx:xx ath0: mac 10.3 phy 6.1 radio 10.2 * Debug settings: net.wlan.0.debug: 0xdfffffff<11n,debug,crypto,input,xrate,elemid,node,assoc,auth,scan,output,state,power,dot1x,dot1xsm,radius,raddump,radkeys,wpa,acl,wme,superg,doth,inact,roam,rate> dev.ath.0.debug: 0xffef8ff0 * Console output (somewhat trimmed) is attached -- last group of messages keeps repeating until I power down the machine. * Output of 'wpa_supplicant -Dbsd -iath0 -d -d -K -c/etc/wpa_supplicant.conf' (hand transcribed) is: Starting AP scan (specific SSID) Scan SSID = hexdump_ascii (len = NN) xx xx xx xx xx xx * /etc/wpa_supplicant.conf is attached * Setup: two stations with the identical SSID: Linksys WRT54Gv8 (running dd-wrt micro) at about 50' and Zyxel P-330W at about 20'. -- Alexandre "Sunny" Kovalenko (ОлекÑандр Коваленко) --Boundary_(ID_UsNYKDm2UnlTuceC8ZYJfQ) Content-type: text/plain; name=wpa_supplicant.conf; charset=UTF-8 Content-transfer-encoding: 7BIT Content-disposition: attachment; filename=wpa_supplicant.conf # # $Log$ # ctrl_interface=/var/run/wpa_supplicant ctrl_interface_group=wheel network={ ssid="xxxxxxxxxxx" scan_ssid=1 priority=1 key_mgmt=WPA-PSK psk="xxxxxxxxxxxxxxxxxxxxxxxxxx" } --Boundary_(ID_UsNYKDm2UnlTuceC8ZYJfQ)-- From owner-freebsd-stable@FreeBSD.ORG Tue May 13 02:33:10 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 68E641065670 for ; Tue, 13 May 2008 02:33:10 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 2490F8FC1C for ; Tue, 13 May 2008 02:33:10 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from Macintosh-2.local ([10.0.0.194]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id m4D2X94J056193 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 May 2008 19:33:09 -0700 (PDT) (envelope-from sam@freebsd.org) Message-ID: <4828FDE5.8090409@freebsd.org> Date: Mon, 12 May 2008 19:33:09 -0700 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: "Alexandre \"Sunny\" Kovalenko" References: <1210640542.1008.33.camel@RabbitsDen> In-Reply-To: <1210640542.1008.33.camel@RabbitsDen> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC-Rhyolite-Metrics: ebb.errno.com; whitelist Cc: stable@freebsd.org Subject: Re: Hard(?) lock when reassociating ath with wpa_supplicant on RELENG_7 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2008 02:33:10 -0000 Alexandre "Sunny" Kovalenko wrote: > I seem to be able to lock my machine by going into wpa_cli and asking it > to 'reassoc'. The reason for question mark after "hard" is that debug > information (caused by wlandebug and athdebug) is being printed on the > console. The only way to get machine's attention is to hold power button > for 8 seconds. So this is just livelock due to console debug msgs. > > Note: manual reassociation is just the handy way to reproduce the > problem -- I have had machine locking up on me the whole day long > completely on its own. > > Below are, what I think, relevant pieces of information. If anything is > missing, please, chastise me appropriately and will do my best to > provide. I have rigged firewire console, but am unable to break into the > debugger locally or remotely. I see no log msgs. > > While I am on the subject, I would appreciate couple of the > troubleshooting suggestions: > * is there any way to get sysctl dev.ath.0.debug to appear, other then > defining ATH_DEBUG in something like /usr/src/sys/dev/ath/ah_osdep.h? options ATH_DEBUG > * is there minimal, but still usable mask for athdebug and wlandebug? I > have started with 0xFFFFFFFF and kept trimming likely high-volume > settings until output slowed down to the reasonable pace. Why do you want debug msgs from ath? The debug msgs from wlandebug depend on what you're trying to debug. I suggest that when debugging you start from the highest layer and move downward. If you can't find what you need in a wpa_supplicant log then turn on msgs in net80211 with wlandebug. If that doesn't tell you what you need then move to the driver. Blindly turning everything on can easily livelock your system. For high volume msgs I often do something like: athdebug +intr; sleep 1; athdebug -intr or athdebug +intr; read x; athdebug -intr so a carriage return will disable msgs. > * what facility does wpa_supplicant use, when forced to syslog by -s > switch? trouble% cd /data/freebsd/head/contrib/wpa_supplicant/ trouble% grep openlog *.c common.c: openlog("wpa_supplicant", LOG_PID | LOG_NDELAY, LOG_DAEMON); > > ======================================================================= > > * OS: > RELENG_7 cvsup'ed on May 11th @ 15:30EST, if_ath is loaded as the module > > * HW: > ath0@pci0:3:0:0: class=0x020000 card=0x058a1014 chip=0x1014168c rev=0x01 > hdr=0x00 > vendor = 'Atheros Communications Inc.' > device = 'AR5212 Atheros AR5212 802.11abg wireless' > class = network > subclass = ethernet > ath0: mem 0xedf00000-0xedf0ffff irq 17 at device 0.0 on > pci3 > ath0: [ITHREAD] > ath0: using obsoleted if_watchdog interface > ath0: Ethernet address: xx:xx:xx:xx:xx:xx > ath0: mac 10.3 phy 6.1 radio 10.2 > > * Debug settings: > net.wlan.0.debug: > 0xdfffffff<11n,debug,crypto,input,xrate,elemid,node,assoc,auth,scan,output,state,power,dot1x,dot1xsm,radius,raddump,radkeys,wpa,acl,wme,superg,doth,inact,roam,rate> > dev.ath.0.debug: > 0xffef8ff0 > > * Console output (somewhat trimmed) is attached -- last group of > messages keeps repeating until I power down the machine. > > * Output of 'wpa_supplicant -Dbsd -iath0 -d -d -K > -c/etc/wpa_supplicant.conf' (hand transcribed) is: > > Starting AP scan (specific SSID) > Scan SSID = hexdump_ascii (len = NN) > xx xx xx xx xx xx > > * /etc/wpa_supplicant.conf is attached > > * Setup: two stations with the identical SSID: Linksys WRT54Gv8 (running > dd-wrt micro) at about 50' and Zyxel P-330W at about 20'. > > > > ------------------------------------------------------------------------ > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Tue May 13 03:34:32 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BE57C1065675 for ; Tue, 13 May 2008 03:34:32 +0000 (UTC) (envelope-from bazzoola@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.176]) by mx1.freebsd.org (Postfix) with ESMTP id 727E08FC1C for ; Tue, 13 May 2008 03:34:32 +0000 (UTC) (envelope-from bazzoola@gmail.com) Received: by py-out-1112.google.com with SMTP id u52so2757577pyb.10 for ; Mon, 12 May 2008 20:34:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:cc:message-id:from:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer; bh=Hlf7fDIDOxqZgbxexdXkQbkNKK8/pgVPnUlTo6DVCCo=; b=NF5Id0WREwy4nbBHD2eZcFYXdeFt1Z1MqQreoEZVFOMxQzM+fGS69ZA+fkripuUsC81cpBVOorYmnrI95jPWxfnsGK15wSItgrZlK6Uu+eSAe3E1PhqAPfn25FVkzwAdi4McRNk1t57ErcomvMeQ90BFwbazRIKzU+n4INrctzY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=cc:message-id:from:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer; b=K/v5z/bcmNjOyDHWb0NDfCmGYvrr2jyagAvp381yJAt2I337rPbVJD6Ca4syNGE2NpXQaxNytFQJG6kowD3QCrWLEYIa/GNZTorcLm5Xgn9d+6/4noQG5NaV/S7du/esmojGtBVoI7cq18Tcnwo66fTW9sCMlX3oDMcCtaE/UMo= Received: by 10.35.50.5 with SMTP id c5mr15003415pyk.26.1210649671870; Mon, 12 May 2008 20:34:31 -0700 (PDT) Received: from ?10.0.1.111? ( [99.147.176.243]) by mx.google.com with ESMTPS id n63sm26076626pyh.8.2008.05.12.20.34.30 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 12 May 2008 20:34:30 -0700 (PDT) Message-Id: <86C46F8C-0F2F-4E80-8737-BF5BFF324C93@gmail.com> From: bazzoola To: Bakul Shah In-Reply-To: <20080513022054.5607C5B4B@mail.bitblocks.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v919.2) Date: Mon, 12 May 2008 23:34:27 -0400 References: <20080513022054.5607C5B4B@mail.bitblocks.com> X-Mailer: Apple Mail (2.919.2) Cc: freebsd-stable Subject: Re: kqemu support: not compiled X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2008 03:34:32 -0000 On May 12, 2008, at 10:20 PM, Bakul Shah wrote: >> I just cant get kqemu to work on my AMD64 SMP! > > echo kqemu_enable=YES >> /etc/rc.conf > /usr/local/etc/rc.d/kqemu start Is this documented anywhere? Also, I volunteered to update the wiki and the author was grateful for that but I didn't get access. If anyone cares. I can just send the updates here via email. Thanks! From owner-freebsd-stable@FreeBSD.ORG Tue May 13 04:18:37 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E8004106567C for ; Tue, 13 May 2008 04:18:37 +0000 (UTC) (envelope-from bazzoola@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.177]) by mx1.freebsd.org (Postfix) with ESMTP id 9B18D8FC13 for ; Tue, 13 May 2008 04:18:37 +0000 (UTC) (envelope-from bazzoola@gmail.com) Received: by py-out-1112.google.com with SMTP id u52so2763793pyb.10 for ; Mon, 12 May 2008 21:18:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:cc:message-id:from:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer; bh=M0bG4lBmFM29c4FJibGxjf5cn7fSa4W1ZynN9rmSh/Y=; b=INyfustRjDwhW9BEV4vD1JAQNR/rfMBaDHqgJe4ZoW814u5U7cgS3bEC5XczWhg1xSd9vSW676kWrLqQQBRFSPj5Qn7kjiag23vTkplPcXd6jIyYm6Wla9IFJrwlVAo2xqVPSQD5RZ2CJF9fVAZvy3GZ958FK/utRw1HIDpHbeM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=cc:message-id:from:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer; b=clh311Tt+BaQ0l51zGpTgyu12A2/oxHaqI0gg6bSioovbNpMj++jC8DBrL3HCPv9IshmnG8nudwZ/Jz/Ollnu88ACLmd23gBBojYKPG1b8ltfEXTlynAlaR7P1+ejhkNVWHU+5QvxLezt5GMwIeSnXXLQ9mO2YH3VDG1SCRjtXY= Received: by 10.35.77.18 with SMTP id e18mr15298854pyl.46.1210652316816; Mon, 12 May 2008 21:18:36 -0700 (PDT) Received: from ?10.0.1.111? ( [99.147.176.243]) by mx.google.com with ESMTPS id f51sm11448015pyh.10.2008.05.12.21.18.35 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 12 May 2008 21:18:36 -0700 (PDT) Message-Id: From: bazzoola To: freebsd-stable In-Reply-To: <20080513022054.5607C5B4B@mail.bitblocks.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v919.2) Date: Tue, 13 May 2008 00:18:32 -0400 References: <20080513022054.5607C5B4B@mail.bitblocks.com> X-Mailer: Apple Mail (2.919.2) Cc: Subject: Re: kqemu support: not compiled X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2008 04:18:38 -0000 On May 12, 2008, at 10:20 PM, Bakul Shah wrote: >> I just cant get kqemu to work on my AMD64 SMP! > > echo kqemu_enable=YES >> /etc/rc.conf > /usr/local/etc/rc.d/kqemu start I looked at the rc script and all it does is kldload aio and kqemu. I already have them loaded by default. This still does not help me with my problem. I press Ctrl + Alt + 2 then I type info kqemu I get "kqemu support: not compiled" From owner-freebsd-stable@FreeBSD.ORG Tue May 13 04:42:20 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C0562106566B for ; Tue, 13 May 2008 04:42:20 +0000 (UTC) (envelope-from pldrouin@pldrouin.net) Received: from smtp.cyberfingers.net (smtp.cyberfingers.net [198.177.254.227]) by mx1.freebsd.org (Postfix) with ESMTP id 9AC7B8FC0A for ; Tue, 13 May 2008 04:42:20 +0000 (UTC) (envelope-from pldrouin@pldrouin.net) Received: from ldaemon.pldrouin.net (modemcable090.40-56-74.mc.videotron.ca [74.56.40.90]) by smtp.cyberfingers.net (Postfix) with ESMTP id DC1D7AB6C20 for ; Tue, 13 May 2008 00:26:58 -0400 (EDT) Message-ID: <48291889.8030406@pldrouin.net> Date: Tue, 13 May 2008 00:26:49 -0400 From: Pierre-Luc Drouin User-Agent: Thunderbird 2.0.0.14 (X11/20080503) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Status of ZFS in -stable? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2008 04:42:20 -0000 Hi, I would like to know if the memory allocation problem with zfs has been fixed in -stable? Is zfs considered to be more "stable" now? Thanks! Pierre-Luc Drouin From owner-freebsd-stable@FreeBSD.ORG Tue May 13 04:43:23 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7EDB5106564A for ; Tue, 13 May 2008 04:43:23 +0000 (UTC) (envelope-from bazzoola@gmail.com) Received: from hs-out-0708.google.com (hs-out-0708.google.com [64.233.178.249]) by mx1.freebsd.org (Postfix) with ESMTP id 2F4668FC23 for ; Tue, 13 May 2008 04:43:23 +0000 (UTC) (envelope-from bazzoola@gmail.com) Received: by hs-out-0708.google.com with SMTP id m63so2307473hsc.11 for ; Mon, 12 May 2008 21:43:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:cc:message-id:from:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer; bh=qikSSrYe2fNErHyyGKjHCVVlVKTjZiyUtYyItMQKcR8=; b=LzEbqSSuw6jO58mdIY8UpTwCx9YacOzrzWrvZ3QzpRcEhWJID/cTl0BfGnIuaEQ37286Qf2TW9o3U7j2kIKZrMTbHt06gMnc/6YhVJm+Qn1WoHPT9I3h7rK7RnGp+6QG+Ou4MBcg2bnu+CfZiGuPI3OpxBsRnKIGKfd57qScWOA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=cc:message-id:from:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer; b=fjJjhUWParKKLx7y8tmI9mngBBlCWK1/FAY166Sbph6lcueLDZh5VYx0mWn3oiyb8a5vK74yy3VkX56yBYLN8pFkKHqnTlqdo27FxavsXDrxpDkkm85QNh/kJJRmb6oVb6ITJY/7oRXV/jXXKMoSUb9NhFyIZf6b828eio8ZgxY= Received: by 10.90.97.20 with SMTP id u20mr4135263agb.46.1210653802199; Mon, 12 May 2008 21:43:22 -0700 (PDT) Received: from ?10.0.1.111? ( [99.147.176.243]) by mx.google.com with ESMTPS id 38sm7507532aga.38.2008.05.12.21.43.21 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 12 May 2008 21:43:21 -0700 (PDT) Message-Id: <4FCC3D24-8F38-420E-A251-182C50E08476@gmail.com> From: bazzoola To: Brandon S. Allbery KF8NH In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v919.2) Date: Tue, 13 May 2008 00:43:17 -0400 References: <20080513022054.5607C5B4B@mail.bitblocks.com> X-Mailer: Apple Mail (2.919.2) Cc: freebsd-stable Subject: Re: kqemu support: not compiled X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2008 04:43:23 -0000 On May 13, 2008, at 12:24 AM, Brandon S. Allbery KF8NH wrote: > > On 2008 May 13, at 0:18, bazzoola wrote: > >> I press Ctrl + Alt + 2 >> then I type info kqemu >> I get "kqemu support: not compiled" > > > Without looking, I'd guess this means the qemu binary was built > without kqemu support enabled. > as I stated before (which u omitted) I DID enabled kqemu everywhere and then built qemu but still I get that error not compiled. setenv WITH_KQEMU edited src.conf and added WITH_KQEMU=yes did make config and checked KQEMU ALPHA support compiled the port with make -DWITH_KQEMU how do you compile qemu binary with kqemu? other than the 4 things above? > -- > brandon s. allbery [solaris,freebsd,perl,pugs,haskell] allbery@kf8nh.com > system administrator [openafs,heimdal,too many hats] allbery@ece.cmu.edu > electrical and computer engineering, carnegie mellon university > KF8NH > > From owner-freebsd-stable@FreeBSD.ORG Tue May 13 04:52:35 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 11201106564A for ; Tue, 13 May 2008 04:52:35 +0000 (UTC) (envelope-from allbery@ece.cmu.edu) Received: from bache.ece.cmu.edu (BACHE.ECE.CMU.EDU [128.2.129.23]) by mx1.freebsd.org (Postfix) with ESMTP id C97C68FC1A for ; Tue, 13 May 2008 04:52:34 +0000 (UTC) (envelope-from allbery@ece.cmu.edu) Received: from mress.kf8nh.com (dsl093-061-215.pit1.dsl.speakeasy.net [66.93.61.215]) by bache.ece.cmu.edu (Postfix) with ESMTP id E25A689; Tue, 13 May 2008 00:24:29 -0400 (EDT) Message-Id: From: "Brandon S. Allbery KF8NH" To: bazzoola In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v919.2) Date: Tue, 13 May 2008 00:24:29 -0400 References: <20080513022054.5607C5B4B@mail.bitblocks.com> X-Mailer: Apple Mail (2.919.2) Cc: freebsd-stable Subject: Re: kqemu support: not compiled X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2008 04:52:35 -0000 On 2008 May 13, at 0:18, bazzoola wrote: > I press Ctrl + Alt + 2 > then I type info kqemu > I get "kqemu support: not compiled" Without looking, I'd guess this means the qemu binary was built without kqemu support enabled. -- brandon s. allbery [solaris,freebsd,perl,pugs,haskell] allbery@kf8nh.com system administrator [openafs,heimdal,too many hats] allbery@ece.cmu.edu electrical and computer engineering, carnegie mellon university KF8NH From owner-freebsd-stable@FreeBSD.ORG Tue May 13 05:11:13 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2373A10656D5 for ; Tue, 13 May 2008 05:11:13 +0000 (UTC) (envelope-from bakul@bitblocks.com) Received: from mail.bitblocks.com (ns1.bitblocks.com [64.142.15.60]) by mx1.freebsd.org (Postfix) with ESMTP id 06DA78FC22 for ; Tue, 13 May 2008 05:11:12 +0000 (UTC) (envelope-from bakul@bitblocks.com) Received: from bitblocks.com (localhost.bitblocks.com [127.0.0.1]) by mail.bitblocks.com (Postfix) with ESMTP id 1563C5B4B; Mon, 12 May 2008 21:51:59 -0700 (PDT) To: bazzoola In-reply-to: Your message of "Tue, 13 May 2008 00:18:32 EDT." Date: Mon, 12 May 2008 21:51:58 -0700 From: Bakul Shah Message-Id: <20080513045159.1563C5B4B@mail.bitblocks.com> Cc: freebsd-stable Subject: Re: kqemu support: not compiled X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2008 05:11:13 -0000 On Tue, 13 May 2008 00:18:32 EDT bazzoola wrote: > > On May 12, 2008, at 10:20 PM, Bakul Shah wrote: > > >> I just cant get kqemu to work on my AMD64 SMP! > > > > echo kqemu_enable=YES >> /etc/rc.conf > > /usr/local/etc/rc.d/kqemu start This should probably be described in pkg-message. > I looked at the rc script and all it does is kldload aio and kqemu. I > already have them loaded by default. You didn't provide information so I had to guess. > This still does not help me with my problem. > > I press Ctrl + Alt + 2 > then I type info kqemu > I get "kqemu support: not compiled" Are you running qemu? It is an i386 emulator and won't use kqemu on amd64. You need to run qemu-system-x86_64. I know, this is a bit confusing. If you are still having problems provide the *exact sequence* of commands you used to build and run qemu. BTW, to build you don't need to muck with environ. var. or -DWITH_KQEMU. Just do make config && make From owner-freebsd-stable@FreeBSD.ORG Tue May 13 05:32:37 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 57A5A1065671 for ; Tue, 13 May 2008 05:32:37 +0000 (UTC) (envelope-from pldrouin@pldrouin.net) Received: from smtp.cyberfingers.net (smtp.cyberfingers.net [198.177.254.227]) by mx1.freebsd.org (Postfix) with ESMTP id 30F328FC18 for ; Tue, 13 May 2008 05:32:37 +0000 (UTC) (envelope-from pldrouin@pldrouin.net) Received: from ldaemon.pldrouin.net (modemcable090.40-56-74.mc.videotron.ca [74.56.40.90]) by smtp.cyberfingers.net (Postfix) with ESMTP id B2B8CAB6C1B for ; Tue, 13 May 2008 01:32:44 -0400 (EDT) Message-ID: <482927F3.20409@pldrouin.net> Date: Tue, 13 May 2008 01:32:35 -0400 From: Pierre-Luc Drouin User-Agent: Thunderbird 2.0.0.14 (X11/20080503) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Status of ZFS in -stable? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2008 05:32:37 -0000 Hi, I would like to know if the memory allocation problem with zfs has been fixed in -stable? Is zfs considered to be more "stable" now? Thanks! Pierre-Luc Drouin From owner-freebsd-stable@FreeBSD.ORG Tue May 13 05:33:36 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C5E831065677 for ; Tue, 13 May 2008 05:33:36 +0000 (UTC) (envelope-from bazzoola@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.176]) by mx1.freebsd.org (Postfix) with ESMTP id 77DED8FC0A for ; Tue, 13 May 2008 05:33:36 +0000 (UTC) (envelope-from bazzoola@gmail.com) Received: by py-out-1112.google.com with SMTP id u52so2773367pyb.10 for ; Mon, 12 May 2008 22:33:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:cc:message-id:from:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer; bh=oqRU5YOoSElnlNhjObfoboXJ9hXvPoiB7K/EfWF6DRQ=; b=UXUdFTjvhrboJ7bxf3UyQRDVz4TJWL+FYvcK0fhzybVNjRynKwLP/eXea1+3I5USTZXf8wewUY4RWPq/bqq+gU0jIZMDaSiNrYGDAWVI9FG1YitRFBBB2seEMLD1wJW1QLu3cFk7SRuJtez/tt42HtuWmaiv2j4h3wODyCSIkKc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=cc:message-id:from:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer; b=vV4lJD/6qMA19YxBrwminvU4h5z+13lXONpzK0b1+P/BK4cQz/L977ZKUvUGHlr9R8vGiJYJnKKmdUbkprmkTR8oOdE8RYHs3z4KnXJ4xJlKv1y/Yh0TF6T7SbqDQYWogi7Hx3j0B9BqVtP548A8Uv3sAfE3zvs5mRbqNphcBF4= Received: by 10.35.88.16 with SMTP id q16mr15377700pyl.66.1210656815714; Mon, 12 May 2008 22:33:35 -0700 (PDT) Received: from ?10.0.1.111? ( [99.147.176.243]) by mx.google.com with ESMTPS id f51sm11520141pyh.10.2008.05.12.22.33.33 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 12 May 2008 22:33:34 -0700 (PDT) Message-Id: From: bazzoola To: Bakul Shah In-Reply-To: <20080513045159.1563C5B4B@mail.bitblocks.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v919.2) Date: Tue, 13 May 2008 01:33:30 -0400 References: <20080513045159.1563C5B4B@mail.bitblocks.com> X-Mailer: Apple Mail (2.919.2) Cc: freebsd-stable Subject: Re: kqemu support: not compiled X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2008 05:33:36 -0000 Thanks for your quick reply I appreciate that! Please see below: On May 13, 2008, at 12:51 AM, Bakul Shah wrote: > On Tue, 13 May 2008 00:18:32 EDT bazzoola wrote: >> >> On May 12, 2008, at 10:20 PM, Bakul Shah wrote: >> >>>> I just cant get kqemu to work on my AMD64 SMP! >>> >>> echo kqemu_enable=YES >> /etc/rc.conf >>> /usr/local/etc/rc.d/kqemu start > > This should probably be described in pkg-message. It is not there. > > >> I looked at the rc script and all it does is kldload aio and kqemu. I >> already have them loaded by default. > > You didn't provide information so I had to guess. My problem lies in qemu not being compiled with kqemu > > >> This still does not help me with my problem. >> >> I press Ctrl + Alt + 2 >> then I type info kqemu >> I get "kqemu support: not compiled" > > Are you running qemu? It is an i386 emulator and won't use > kqemu on amd64. You need to run qemu-system-x86_64. I know, > this is a bit confusing. I thought qemu on x64 runs that directly. My bad.. Note I had to run qemu-system-x86_64 -kernel-kqemu to get kernel mode virtz to work otherwise it will just load it in user mode. Thanks again for your help! > > > If you are still having problems provide the *exact sequence* > of commands you used to build and run qemu. BTW, to build > you don't need to muck with environ. var. or -DWITH_KQEMU. > Just do > > make config && make From owner-freebsd-stable@FreeBSD.ORG Tue May 13 06:18:19 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4EC511065670 for ; Tue, 13 May 2008 06:18:19 +0000 (UTC) (envelope-from rsmith@xs4all.nl) Received: from smtp-vbr16.xs4all.nl (smtp-vbr16.xs4all.nl [194.109.24.36]) by mx1.freebsd.org (Postfix) with ESMTP id 8CA838FC0C for ; Tue, 13 May 2008 06:18:18 +0000 (UTC) (envelope-from rsmith@xs4all.nl) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr16.xs4all.nl (8.13.8/8.13.8) with ESMTP id m4D5gUEg074812; Tue, 13 May 2008 07:42:30 +0200 (CEST) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id 4D6DCB854; Tue, 13 May 2008 07:42:30 +0200 (CEST) Date: Tue, 13 May 2008 07:42:30 +0200 From: Roland Smith To: Steve Franks Message-ID: <20080513054230.GA47218@slackbox.xs4all.nl> Mail-Followup-To: Steve Franks , freebsd-stable@freebsd.org, freebsd-usb@freebsd.org References: <539c60b90804111420kcb73e6do8a20dce574d13864@mail.gmail.com> <20080412213225.GB24224@slackbox.xs4all.nl> <539c60b90804141549u6a138ad9u9c77bbfcbbad0ff3@mail.gmail.com> <20080415175347.GA29045@slackbox.xs4all.nl> <539c60b90804291032v4a7e80d0w205354d4bf1be842@mail.gmail.com> <20080429214640.GA85715@slackbox.xs4all.nl> <539c60b90805121338n439c1a62sab5be6f6ea9485ff@mail.gmail.com> <20080512225049.GA35802@slackbox.xs4all.nl> <539c60b90805121619g3d7afe70yd7e733fea012ae9d@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="6c2NcOVqGQ03X4Wi" Content-Disposition: inline In-Reply-To: <539c60b90805121619g3d7afe70yd7e733fea012ae9d@mail.gmail.com> X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 X-GPG-Key: http://www.xs4all.nl/~rsmith/pubkey.txt X-GPG-Notice: If this message is not signed, don't assume I sent it! User-Agent: Mutt/1.5.17 (2007-11-01) X-Virus-Scanned: by XS4ALL Virus Scanner Cc: freebsd-stable@freebsd.org, freebsd-usb@freebsd.org Subject: Re: umass causes panic on 7 amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2008 06:18:19 -0000 --6c2NcOVqGQ03X4Wi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, May 12, 2008 at 04:19:27PM -0700, Steve Franks wrote: > On Mon, May 12, 2008 at 3:50 PM, Roland Smith wrote: > > On Mon, May 12, 2008 at 01:38:51PM -0700, Steve Franks wrote: > > > I have added options USB DEBUG to my kernconf file ("DYSTANT"). Here > > > is the backtrace: > > > > > > Steve > > > > > > [steve@dystant /usr/obj/usr/src/sys/DYSTANT]$ sudo kgdb kernel.debug > > > /var/crash/vmcore.6 > > > [GDB will not be able to debug user-mode threads: > > > /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] > > > GNU gdb 6.1.1 [FreeBSD] > > > Copyright 2004 Free Software Foundation, Inc. > > > GDB is free software, covered by the GNU General Public License, and= you are > > > welcome to change it and/or distribute copies of it under certain co= nditions. > > > Type "show copying" to see the conditions. > > > There is absolutely no warranty for GDB. Type "show warranty" for d= etails. > > > This GDB was configured as "amd64-marcel-freebsd". > > > > > > Unread portion of the kernel message buffer: > > > umass0: = on uhub2 > > > umass0: SCSI over (unknown 0x00); quirks =3D 0x0100 > > > panic: /usr/src/sys/dev/usb/umass.c:1453: Unknown proto 0x100 > > > > It looks like the camera is not returning a wire protocol. > > You definitely need to take this to the -usb list. >=20 > Still shouldn't cause a panic, should it? Yes it should. It calls the 'panic' function. Roland --=20 R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) --6c2NcOVqGQ03X4Wi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkgpKkYACgkQEnfvsMMhpyU9ygCfZG8fjRkSGTZcNqR0osD3l4Qp JqUAn24SBoeKdUSn2Udjn1Hn4/Ov5apJ =6qSA -----END PGP SIGNATURE----- --6c2NcOVqGQ03X4Wi-- From owner-freebsd-stable@FreeBSD.ORG Tue May 13 08:42:16 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BC43E106567D for ; Tue, 13 May 2008 08:42:16 +0000 (UTC) (envelope-from danger@FreeBSD.org) Received: from mailhub.rulez.sk (mailhub.rulez.sk [IPv6:2001:15c0:6672::2]) by mx1.freebsd.org (Postfix) with ESMTP id 6A58D8FC29 for ; Tue, 13 May 2008 08:42:16 +0000 (UTC) (envelope-from danger@FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by mailhub.rulez.sk (Postfix) with ESMTP id A09E15C027; Tue, 13 May 2008 10:42:15 +0200 (CEST) X-Virus-Scanned: amavisd-new at rulez.sk Received: from mailhub.rulez.sk ([78.47.53.106]) by localhost (genesis.rulez.sk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GJcBTn2xEfVw; Tue, 13 May 2008 10:42:15 +0200 (CEST) Received: from DANGER-PC (danger.mcrn.sk [84.16.37.254]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: danger@rulez.sk) by mailhub.rulez.sk (Postfix) with ESMTPSA id 024D75C020; Tue, 13 May 2008 10:42:14 +0200 (CEST) Date: Tue, 13 May 2008 10:42:05 +0200 From: Daniel Gerzo X-Mailer: The Bat! (v3.99.3) Professional Organization: The FreeBSD Project X-Priority: 3 (Normal) Message-ID: <1618815695.20080513104205@rulez.sk> To: Pierre-Luc Drouin In-Reply-To: <48291889.8030406@pldrouin.net> References: <48291889.8030406@pldrouin.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: Status of ZFS in -stable? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Gerzo List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2008 08:42:16 -0000 Hello Pierre-Luc, Tuesday, May 13, 2008, 6:26:49 AM, you wrote: > Hi, > I would like to know if the memory allocation problem with zfs has been > fixed in -stable? Is zfs considered to be more "stable" now? It's still an experimental feature in FreeBSD, though the memory allocation issues might have been already fixed (I don't know personally). Many people have reported success stories when using ZFS on FreeBSD, however there's also plenty of them who are reporting substantial issues when using ZFS. It's up to your own decision whether ZFS will be feasible for you; you might want to test it before deploying it to the production environment. -- Best regards, Daniel mailto:danger@FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Tue May 13 12:08:57 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6C18D106567F; Tue, 13 May 2008 12:08:57 +0000 (UTC) (envelope-from hugo@barafranca.com) Received: from mail.barafranca.com (mail.barafranca.com [67.213.67.47]) by mx1.freebsd.org (Postfix) with ESMTP id 482F38FC31; Tue, 13 May 2008 12:08:57 +0000 (UTC) (envelope-from hugo@barafranca.com) Received: from localhost (unknown [172.16.100.24]) by mail.barafranca.com (Postfix) with ESMTP id A4B84A6A; Tue, 13 May 2008 11:54:51 +0000 (UTC) X-Virus-Scanned: amavisd-new at barafranca.com Received: from mail.barafranca.com ([172.16.100.24]) by localhost (mail.barafranca.com [172.16.100.24]) (amavisd-new, port 10024) with ESMTP id 41vrvwjvvtzv; Tue, 13 May 2008 11:54:12 +0000 (UTC) Received: from [192.168.200.26] (a213-22-25-165.cpe.netcabo.pt [213.22.25.165]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.barafranca.com (Postfix) with ESMTPSA id 865EAA5B; Tue, 13 May 2008 11:54:09 +0000 (UTC) Message-ID: <4829735A.6080103@barafranca.com> Date: Tue, 13 May 2008 12:54:18 +0200 From: Hugo Silva User-Agent: Thunderbird 2.0.0.9 (X11/20071213) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <48291889.8030406@pldrouin.net> <1618815695.20080513104205@rulez.sk> In-Reply-To: <1618815695.20080513104205@rulez.sk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Pierre-Luc Drouin , Daniel Gerzo Subject: Re: Status of ZFS in -stable? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2008 12:08:57 -0000 Daniel Gerzo wrote: > Hello Pierre-Luc, > > Tuesday, May 13, 2008, 6:26:49 AM, you wrote: > > >> Hi, >> > > >> I would like to know if the memory allocation problem with zfs has been >> fixed in -stable? Is zfs considered to be more "stable" now? >> > > It's still an experimental feature in FreeBSD, though the memory > allocation issues might have been already fixed (I don't know > personally). > > Many people have reported success stories when using ZFS on FreeBSD, > however there's also plenty of them who are reporting substantial issues > when using ZFS. It's up to your own decision whether ZFS will be > feasible for you; you might want to test it before deploying it to the > production environment. > > FWIW, I've been using ZFS on two "jail servers" for months without any visible issues. 7.0-RELEASE/amd64. Hugo From owner-freebsd-stable@FreeBSD.ORG Tue May 13 14:18:38 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 39C79106566B for ; Tue, 13 May 2008 14:18:38 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from angel.ticketswitch.com (angel.ticketswitch.com [IPv6:2002:57e0:1d4e::1]) by mx1.freebsd.org (Postfix) with ESMTP id 038568FC12 for ; Tue, 13 May 2008 14:18:37 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from [10.50.50.2] (helo=smaug.rattatosk) by angel.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1JvvKu-0003DM-CN for stable@freebsd.org; Tue, 13 May 2008 15:18:36 +0100 Received: from dilbert.rattatosk ([10.50.50.6] helo=dilbert.ticketswitch.com) by smaug.rattatosk with esmtp (Exim 4.69 (FreeBSD)) (envelope-from ) id 1JvvKu-0004Gd-9d for stable@freebsd.org; Tue, 13 May 2008 15:18:36 +0100 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1JvvKu-00051a-8q for stable@freebsd.org; Tue, 13 May 2008 15:18:36 +0100 To: stable@freebsd.org Message-Id: From: Pete French Date: Tue, 13 May 2008 15:18:36 +0100 Cc: Subject: Changing an installed system from i386 to amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2008 14:18:38 -0000 I have a box currently running i386 which I want to change over to run amd64. I have installed a second drive into the machine on which I have put a basic install of amd64, and have compiled up the world and kertnel from source. Can I simply switch the original partition over by mounting it up and doin a 'make installworld' with an approrpiate DESTDIR set ? I guess what I am asking is if anything else is different between the two versions aside from the actual binaries themselves (i.e. directory layout and the like). -pete. From owner-freebsd-stable@FreeBSD.ORG Tue May 13 14:29:24 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7C0B91065677 for ; Tue, 13 May 2008 14:29:24 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 0F0FF8FC0C for ; Tue, 13 May 2008 14:29:23 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1JvvVF-00033Z-AR for freebsd-stable@freebsd.org; Tue, 13 May 2008 14:29:17 +0000 Received: from 92.50.96.215 ([92.50.96.215]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 13 May 2008 14:29:17 +0000 Received: from saper by 92.50.96.215 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 13 May 2008 14:29:17 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Marcin Cieslak Date: Tue, 13 May 2008 16:29:03 +0200 Lines: 63 Message-ID: <4829A5AF.9070102@system.pl> References: <48291889.8030406@pldrouin.net> <1618815695.20080513104205@rulez.sk> <4829735A.6080103@barafranca.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-ripemd160; protocol="application/pgp-signature"; boundary="------------enigDD0B2132DDEB2201A3C64FFB" X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 92.50.96.215 User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.8.1.13) Gecko/20080405 SeaMonkey/1.1.9 Mnenhy/0.7.5.0 In-Reply-To: <4829735A.6080103@barafranca.com> X-Enigmail-Version: 0.95.6 Sender: news Cc: Pierre-Luc Drouin , Daniel Gerzo , freebsd-stable@freebsd.org Subject: Re: Status of ZFS in -stable? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2008 14:29:24 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigDD0B2132DDEB2201A3C64FFB Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: quoted-printable Hugo Silva wrote: > Daniel Gerzo wrote: >> Hello Pierre-Luc, >> >> Tuesday, May 13, 2008, 6:26:49 AM, you wrote: >> >> =20 >>> Hi, >>> =20 >> >> =20 >>> I would like to know if the memory allocation problem with zfs has be= en >>> fixed in -stable? Is zfs considered to be more "stable" now? I am using ZFS on my laptop as a typical, heavily used desktop system. I = experience some concurrency issues (the machine "locks up" for a moment=20 while the system is doing some work). I am doing some heavy tasks like=20 compiling OpenOffice in my free time. I experience very strange behaviour when running out of space (one of=20 the applications dumped a huge core file that could not be rm(1)'ed=20 because of.... "Not enough space"!). In my personal opinion, the stability of FreeBSD 7.0-stable with ZFS=20 (and maybe other features are at fault, e.g. wpi driver, my ACPI) is not = very good. I experience strange hangs and hick-ups, sometimes panics. The good thing about ZFS is that no matter how hard it dies it usually=20 comes up good (once I had to wait a while to let it recover after reboot = and reboot the system again cleanly since some files were missing and=20 just re-appeared later). I am bound to use ZFS because it saves me a lot of space (no need for=20 partition split), but as soon as I setup some more external disk space=20 for my laptop I may consider not using it anymore. --Marcin --------------enigDD0B2132DDEB2201A3C64FFB Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQCVAwUBSCmlsD2W2v2wY27ZAQOXxwP/RodTejWFN8jMOO9oGj50deBaEDnKmnNm 1Zvtp+8M2UAMtGdr3oVFdtFJ7ocfAoj3c4otxzDxf+MAGiAGr2i+Ks/XK3tQ/tZ3 2BotRtbpFC6H8Nsi1flnyWxFIol9S1HXfmND3FNSuxSSUHbarxmYi4czXKSXG8cm 0/J0sn0KDqY= =V72o -----END PGP SIGNATURE----- --------------enigDD0B2132DDEB2201A3C64FFB-- From owner-freebsd-stable@FreeBSD.ORG Tue May 13 14:56:49 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 63DE11065675 for ; Tue, 13 May 2008 14:56:49 +0000 (UTC) (envelope-from saper@system.pl) Received: from system.pl (ns356865.ovh.net [91.121.143.223]) by mx1.freebsd.org (Postfix) with ESMTP id D61E28FC29 for ; Tue, 13 May 2008 14:56:48 +0000 (UTC) (envelope-from saper@system.pl) Received: (qmail 29957 invoked by uid 10); 13 May 2008 16:30:08 +0200 Received: from radziecki.saper.info (localhost [127.0.0.1]) by radziecki.saper.info (8.14.2/8.14.2) with ESMTP id m4DET4lA044152 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 13 May 2008 16:29:05 +0200 (CEST) (envelope-from saper@system.pl) Message-ID: <4829A5AF.9070102@system.pl> Date: Tue, 13 May 2008 16:29:03 +0200 From: Marcin Cieslak User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.8.1.13) Gecko/20080405 SeaMonkey/1.1.9 Mnenhy/0.7.5.0 MIME-Version: 1.0 Newsgroups: gmane.os.freebsd.stable To: Hugo Silva References: <48291889.8030406@pldrouin.net> <1618815695.20080513104205@rulez.sk> <4829735A.6080103@barafranca.com> In-Reply-To: <4829735A.6080103@barafranca.com> X-Enigmail-Version: 0.95.6 Content-Type: multipart/signed; micalg=pgp-ripemd160; protocol="application/pgp-signature"; boundary="------------enigDD0B2132DDEB2201A3C64FFB" Cc: Pierre-Luc Drouin , Daniel Gerzo , freebsd-stable@freebsd.org Subject: Re: Status of ZFS in -stable? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2008 14:56:49 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigDD0B2132DDEB2201A3C64FFB Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: quoted-printable Hugo Silva wrote: > Daniel Gerzo wrote: >> Hello Pierre-Luc, >> >> Tuesday, May 13, 2008, 6:26:49 AM, you wrote: >> >> =20 >>> Hi, >>> =20 >> >> =20 >>> I would like to know if the memory allocation problem with zfs has be= en >>> fixed in -stable? Is zfs considered to be more "stable" now? I am using ZFS on my laptop as a typical, heavily used desktop system. I = experience some concurrency issues (the machine "locks up" for a moment=20 while the system is doing some work). I am doing some heavy tasks like=20 compiling OpenOffice in my free time. I experience very strange behaviour when running out of space (one of=20 the applications dumped a huge core file that could not be rm(1)'ed=20 because of.... "Not enough space"!). In my personal opinion, the stability of FreeBSD 7.0-stable with ZFS=20 (and maybe other features are at fault, e.g. wpi driver, my ACPI) is not = very good. I experience strange hangs and hick-ups, sometimes panics. The good thing about ZFS is that no matter how hard it dies it usually=20 comes up good (once I had to wait a while to let it recover after reboot = and reboot the system again cleanly since some files were missing and=20 just re-appeared later). I am bound to use ZFS because it saves me a lot of space (no need for=20 partition split), but as soon as I setup some more external disk space=20 for my laptop I may consider not using it anymore. --Marcin --------------enigDD0B2132DDEB2201A3C64FFB Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQCVAwUBSCmlsD2W2v2wY27ZAQOXxwP/RodTejWFN8jMOO9oGj50deBaEDnKmnNm 1Zvtp+8M2UAMtGdr3oVFdtFJ7ocfAoj3c4otxzDxf+MAGiAGr2i+Ks/XK3tQ/tZ3 2BotRtbpFC6H8Nsi1flnyWxFIol9S1HXfmND3FNSuxSSUHbarxmYi4czXKSXG8cm 0/J0sn0KDqY= =V72o -----END PGP SIGNATURE----- --------------enigDD0B2132DDEB2201A3C64FFB-- From owner-freebsd-stable@FreeBSD.ORG Tue May 13 15:28:05 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0A5BA106564A for ; Tue, 13 May 2008 15:28:05 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from angel.ticketswitch.com (angel.ticketswitch.com [IPv6:2002:57e0:1d4e::1]) by mx1.freebsd.org (Postfix) with ESMTP id C52508FC13 for ; Tue, 13 May 2008 15:28:04 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from [10.50.50.2] (helo=smaug.rattatosk) by angel.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1JvwQ5-0003nX-C2; Tue, 13 May 2008 16:28:01 +0100 Received: from dilbert.rattatosk ([10.50.50.6] helo=dilbert.ticketswitch.com) by smaug.rattatosk with esmtp (Exim 4.69 (FreeBSD)) (envelope-from ) id 1JvwQ5-0004v8-7s; Tue, 13 May 2008 16:28:01 +0100 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1JvwQ5-0009NK-72; Tue, 13 May 2008 16:28:01 +0100 To: aryeh.friedman@gmail.com In-Reply-To: <4829AEA6.9080306@gmail.com> Message-Id: From: Pete French Date: Tue, 13 May 2008 16:28:01 +0100 Cc: stable@freebsd.org Subject: Re: Changing an installed system from i386 to amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2008 15:28:05 -0000 > I did roughly the same but slightly different method: ah, and did it work o.k. ? -pete. From owner-freebsd-stable@FreeBSD.ORG Tue May 13 15:29:10 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E22F51065678 for ; Tue, 13 May 2008 15:29:10 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from mta1.srv.hcvlny.cv.net (mta1.srv.hcvlny.cv.net [167.206.4.196]) by mx1.freebsd.org (Postfix) with ESMTP id C017A8FC1A for ; Tue, 13 May 2008 15:29:10 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from ool-435559b8.dyn.optonline.net (ool-435559b8.dyn.optonline.net [67.85.89.184]) by mta1.srv.hcvlny.cv.net (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTP id <0K0T0021ZCCL9D01@mta1.srv.hcvlny.cv.net> for stable@freebsd.org; Tue, 13 May 2008 11:29:09 -0400 (EDT) Received: from ool-435559b8.dyn.optonline.net (localhost [127.0.0.1]) by ool-435559b8.dyn.optonline.net (8.14.2/8.14.2) with ESMTP id m4DFT8dI097199; Tue, 13 May 2008 11:29:09 -0400 Date: Tue, 13 May 2008 11:29:03 -0400 From: "Aryeh M. Friedman" In-reply-to: To: Pete French Message-id: <4829B3BF.6090201@gmail.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-Enigmail-Version: 0.95.6 References: User-Agent: Thunderbird 2.0.0.14 (X11/20080504) Cc: stable@freebsd.org Subject: Re: Changing an installed system from i386 to amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2008 15:29:11 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Pete French wrote: |> I did roughly the same but slightly different method: | | ah, and did it work o.k. ? | | -pete. | Yes and I have been using the system for almost 8 months now as my primary desktop -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkgps78ACgkQk8GFzCrQm4DjkwCgg6MUz2w73LZwKV2RorIyxeT7 sjAAn1Wh9NBQsBuR1Ftm2ashZEtc5SEk =W4Z2 -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Tue May 13 15:37:41 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 14345106564A for ; Tue, 13 May 2008 15:37:41 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from mta4.srv.hcvlny.cv.net (mta4.srv.hcvlny.cv.net [167.206.4.199]) by mx1.freebsd.org (Postfix) with ESMTP id E3DA28FC19 for ; Tue, 13 May 2008 15:37:40 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from ool-435559b8.dyn.optonline.net (ool-435559b8.dyn.optonline.net [67.85.89.184]) by mta4.srv.hcvlny.cv.net (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTP id <0K0T001LKBCCF2R0@mta4.srv.hcvlny.cv.net> for stable@freebsd.org; Tue, 13 May 2008 11:07:25 -0400 (EDT) Received: from ool-435559b8.dyn.optonline.net (localhost [127.0.0.1]) by ool-435559b8.dyn.optonline.net (8.14.2/8.14.2) with ESMTP id m4DF7NaV099197; Tue, 13 May 2008 11:07:23 -0400 Date: Tue, 13 May 2008 11:07:18 -0400 From: "Aryeh M. Friedman" In-reply-to: To: Pete French Message-id: <4829AEA6.9080306@gmail.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-Enigmail-Version: 0.95.6 References: User-Agent: Thunderbird 2.0.0.14 (X11/20080504) Cc: stable@freebsd.org Subject: Re: Changing an installed system from i386 to amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2008 15:37:41 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Pete French wrote: | I have a box currently running i386 which I want to change over to | run amd64. I have installed a second drive into the machine on which | I have put a basic install of amd64, and have compiled up the world | and kertnel from source. | | Can I simply switch the original partition over by mounting it up | and doin a 'make installworld' with an approrpiate DESTDIR set ? | I guess what I am asking is if anything else is different between | the two versions aside from the actual binaries themselves (i.e. | directory layout and the like). I did roughly the same but slightly different method: 0. Deinstall all ports but record what they are 1. FTP the enitre kernel and base system from what ever version you want 2. Install the kernel with (this assumes 7/8-current): ~ ./install.sh generic 3. Install the base system ~ ./install.sh 4. Reboot (optional) 4a. Get the most recent sources and remake the system with those (optional) 4b. Get and install any other sysinstall distfiles you wish (optional) 4c. Run make delete-old and make delete-old-libs 5. Reinstall all your ports Note: ./install.sh done from what ever dir you put the distfiles in (*DO NOT* intermix kernel and base) 4c is almost not optional -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkgprqUACgkQk8GFzCrQm4CtVACeJg9f0SnPG1I1nix/948kHJit GCkAoO8U2D/WCvPJ1Mz3icCCQaQD6180 =o5mP -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Tue May 13 15:51:13 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 805D4106564A for ; Tue, 13 May 2008 15:51:13 +0000 (UTC) (envelope-from bakul@bitblocks.com) Received: from mail.bitblocks.com (bitblocks.com [64.142.15.60]) by mx1.freebsd.org (Postfix) with ESMTP id 691068FC20 for ; Tue, 13 May 2008 15:51:13 +0000 (UTC) (envelope-from bakul@bitblocks.com) Received: from bitblocks.com (localhost.bitblocks.com [127.0.0.1]) by mail.bitblocks.com (Postfix) with ESMTP id 35BFA5B55; Tue, 13 May 2008 08:33:03 -0700 (PDT) To: Pete French In-reply-to: Your message of "Tue, 13 May 2008 15:18:36 BST." Date: Tue, 13 May 2008 08:33:03 -0700 From: Bakul Shah Message-Id: <20080513153303.35BFA5B55@mail.bitblocks.com> Cc: stable@freebsd.org Subject: Re: Changing an installed system from i386 to amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2008 15:51:13 -0000 On Tue, 13 May 2008 15:18:36 BST Pete French wrote: > I have a box currently running i386 which I want to change over to > run amd64. I have installed a second drive into the machine on which > I have put a basic install of amd64, and have compiled up the world > and kertnel from source. > > Can I simply switch the original partition over by mounting it up > and doin a 'make installworld' with an approrpiate DESTDIR set ? > I guess what I am asking is if anything else is different between > the two versions aside from the actual binaries themselves (i.e. > directory layout and the like). In the 64 bit FreeBSD world, /usr/lib32 contains libraries for the x86 binaries and /lib, /usr/lib contain 64 bit libraries so a straight install may mess things up. At the very least you should backup your 32 bit root partition -- but I have a feeling my advice is already too late :-) Ideally a simple perl script can automate most of this job. May be all you have to do is something like this: for a in lib usr/lib usr/local/lib do mv $DESTDIR/$a $DESTDIR/${a}32 done echo 'ldconfig32_paths="/usr/lib32 /usr/local/lib32"' >> $DESTIDIR/etc/rc.conf Most all old 32 bit ports should work but upgrading them can mess things up. All the new compiles will generate 64 bit binaries but any port dependencies on a shared library will be wrong. Also, not all 32 bit ports work on 64 bit. May be the trick is to save port directory names for all installed ports (e.g. shell/zsh), then blow them all away (after saving a copy somewhere) and then install them again. This really needs to be part of sysinstall. PS: the following may come in handy. Save it in ~/bin/ldd32. #!/bin/sh # ldd for i386 binaries for i in ${1+"$@"} do echo "$i": env LD_32_TRACE_LOADED_OBJECTS=1 "$i" done From owner-freebsd-stable@FreeBSD.ORG Tue May 13 15:59:12 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 698331065672 for ; Tue, 13 May 2008 15:59:12 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from angel.ticketswitch.com (angel.ticketswitch.com [IPv6:2002:57e0:1d4e::1]) by mx1.freebsd.org (Postfix) with ESMTP id 2484E8FC12 for ; Tue, 13 May 2008 15:59:12 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from [10.50.50.2] (helo=smaug.rattatosk) by angel.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1JvwuF-00043y-DJ; Tue, 13 May 2008 16:59:11 +0100 Received: from dilbert.rattatosk ([10.50.50.6] helo=dilbert.ticketswitch.com) by smaug.rattatosk with esmtp (Exim 4.69 (FreeBSD)) (envelope-from ) id 1JvwuF-0005FM-Aj; Tue, 13 May 2008 16:59:11 +0100 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1JvwuF-0009iQ-9v; Tue, 13 May 2008 16:59:11 +0100 To: bakul@bitblocks.com In-Reply-To: <20080513153303.35BFA5B55@mail.bitblocks.com> Message-Id: From: Pete French Date: Tue, 13 May 2008 16:59:11 +0100 Cc: stable@freebsd.org Subject: Re: Changing an installed system from i386 to amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2008 15:59:12 -0000 > In the 64 bit FreeBSD world, /usr/lib32 contains libraries > for the x86 binaries and /lib, /usr/lib contain 64 bit > libraries so a straight install may mess things up. At the > very least you should backup your 32 bit root partition -- > but I have a feeling my advice is already too late :-) heh, not too late, am not *that* impulsive - but I don't see why this will mess things up ? Surely thats exactly what I want to happen, for /usr/lib to become 64 bit to go with the binaries which will aalso become 64 bit. This isn't a running system bear in mind - it a disc from another system which is mounted on a separte machine running 64 bitA, so theres no issue with the binaries needing to run during the changeover. > Most all old 32 bit ports should work but upgrading them can > mess things up. All the new compiles will generate 64 bit > binaries but any port dependencies on a shared library will there are no ports on the amchine so this shouldnt be an issue. > PS: the following may come in handy. Save it in ~/bin/ldd32. thats useful, thanks! -pete. From owner-freebsd-stable@FreeBSD.ORG Tue May 13 16:30:16 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 68F091065677 for ; Tue, 13 May 2008 16:30:16 +0000 (UTC) (envelope-from bakul@bitblocks.com) Received: from mail.bitblocks.com (bitblocks.com [64.142.15.60]) by mx1.freebsd.org (Postfix) with ESMTP id 534E98FC1F for ; Tue, 13 May 2008 16:30:16 +0000 (UTC) (envelope-from bakul@bitblocks.com) Received: from bitblocks.com (localhost.bitblocks.com [127.0.0.1]) by mail.bitblocks.com (Postfix) with ESMTP id 153205B55; Tue, 13 May 2008 09:30:14 -0700 (PDT) To: Pete French In-reply-to: Your message of "Tue, 13 May 2008 16:59:11 BST." Date: Tue, 13 May 2008 09:30:14 -0700 From: Bakul Shah Message-Id: <20080513163015.153205B55@mail.bitblocks.com> Cc: stable@freebsd.org Subject: Re: Changing an installed system from i386 to amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2008 16:30:16 -0000 On Tue, 13 May 2008 16:59:11 BST Pete French wrote: > > In the 64 bit FreeBSD world, /usr/lib32 contains libraries > > for the x86 binaries and /lib, /usr/lib contain 64 bit > > libraries so a straight install may mess things up. At the > > very least you should backup your 32 bit root partition -- > > but I have a feeling my advice is already too late :-) > > heh, not too late, am not *that* impulsive - but I don't > see why this will mess things up ? Surely thats exactly what > I want to happen, for /usr/lib to become 64 bit to go > with the binaries which will aalso become 64 bit. If you run only the latest standard binaries you are right but typically one acquires useful things over time and it is not always possible to recompile them and also, why bother. From owner-freebsd-stable@FreeBSD.ORG Tue May 13 16:47:18 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 34DA8106564A for ; Tue, 13 May 2008 16:47:18 +0000 (UTC) (envelope-from hartzell@alerce.com) Received: from merlin.alerce.com (merlin.alerce.com [64.62.142.94]) by mx1.freebsd.org (Postfix) with ESMTP id 1DD368FC13 for ; Tue, 13 May 2008 16:47:17 +0000 (UTC) (envelope-from hartzell@alerce.com) Received: from merlin.alerce.com (localhost [127.0.0.1]) by merlin.alerce.com (Postfix) with ESMTP id 6F54533C62 for ; Tue, 13 May 2008 09:18:33 -0700 (PDT) Received: from postfix.alerce.com (w092.z064001164.sjc-ca.dsl.cnc.net [64.1.164.92]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by merlin.alerce.com (Postfix) with ESMTP id 1437733C5B for ; Tue, 13 May 2008 09:18:33 -0700 (PDT) Received: by postfix.alerce.com (Postfix, from userid 501) id 19E8B42BF57; Tue, 13 May 2008 09:18:32 -0700 (PDT) From: George Hartzell MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18473.48984.31132.91673@almost.alerce.com> Date: Tue, 13 May 2008 09:18:32 -0700 To: freebsd-stable@freebsd.org X-Mailer: VM 7.19 under Emacs 22.1.50.1 X-Virus-Scanned: ClamAV using ClamSMTP Subject: good/best practices for gmirror and gjournal on a pair of disks? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: hartzell@alerce.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2008 16:47:18 -0000 I've been running many of my systems for some time now using gmirror on a pair of identical disks, as described by Ralf at: http://people.freebsd.org/~rse/mirror/ Each disk has single slice that covers almost all of the disk. These slices are combined into the gmirror device (gm0), which is then carved up by bsdlabel into gm0a (/), gm0b (swap), gm0d (/var), gm0e (/tmp), and gm0f (/usr). My latest machine is using Seagate 1TB disks so I thought I should add gjournal to the mix to avoid ugly fsck's if/when the machine doesn't shut down cleanly. I ended up just creating a gm0f.journal and using it for /usr, which basically seems to be working. I'm left with a couple of questions though: - I've read in the gjournal man page that when it is "... configured on top of gmirror(8) or graid3(8) providers, it also keeps them in a consistent state..." I've been trying to figure out if this simply falls out of how gjournal works or if there's explicity collusion with gmirror/graid3 but can't come up with a satisfactory explanation. Can someone walk me through it? Since I'm only gjournal'ing a portion of the underlying gmirror device I assume that I don't get this benefit? - I've also read in the gjournal man page "... that sync(2) and fsync(2) system calls do not work as expected anymore." Does this invalidate any of the assumptions made by various database packages such as postgresql, sqlite, berkeley db, etc.... about if/when/whether their data is safely on the disk? - What's the cleanest gjournal adaptation of rse's two-disk-mirror-everything setup that would be able to avoid tedious gmirror sync's. The best I've come up with is to do two slices per disk, combine the slices into a pair of gmirror devices, bsdlabel the first into gm0a (/), gm0b (swap), gm0d (/var) and gm0e (/tmp) and bsdlabel the second into a gm1f which gets a gjournal device. Alternatively, would it work and/or make sense to give each disk a single slice, combine them into a gmirror, put a gjournal on top of that, then use bsdlabel to slice it up into partitions? Is anyone using gjournal and gmirror for all of the system on a pair of disks in some other configuration? Thanks, g. From owner-freebsd-stable@FreeBSD.ORG Tue May 13 16:50:09 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B0A361065673 for ; Tue, 13 May 2008 16:50:09 +0000 (UTC) (envelope-from minimarmot@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.30]) by mx1.freebsd.org (Postfix) with ESMTP id 6EDD98FC1C for ; Tue, 13 May 2008 16:50:09 +0000 (UTC) (envelope-from minimarmot@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so1581545ywe.13 for ; Tue, 13 May 2008 09:50:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; bh=foThX6HJ7uKUbj3+Rbu7fdWeW4SuMk/ioDB7yZRefrs=; b=rtWE7GPvFiM8WcCqSX/Sjbbk69jbX2gRnO5i+CF11gbBdFaf6da3MikOLB/Xzep6KToyZx9FtHpIXpenYlkVAlerlbbmMuxqpSQ14gW/57dkuthNJ7n8pbWmSIXm8adyY2FtxxYFelZ3hHCjmhdSjKQjHD/nuzFu82apUx5McEI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=WJNkbvEepePx4iIK9wNka95ydK6LOqMLS/QoeS6M3gaho1dkLH29y+EPuJoiXkAhWMwabji4BHoVKe/P91RDizPhCWO9NObWnIds/hn/7k6aOe4Lw4Fcz+MDK18MR4hsclWjEHGmXd6lzfMYMB5xEEHcZrJZusjfmtnUiBG+qE8= Received: by 10.150.206.21 with SMTP id d21mr3430447ybg.227.1210695730867; Tue, 13 May 2008 09:22:10 -0700 (PDT) Received: by 10.151.60.8 with HTTP; Tue, 13 May 2008 09:22:10 -0700 (PDT) Message-ID: <47d0403c0805130922x62fc479cs47b8a03f41598e00@mail.gmail.com> Date: Tue, 13 May 2008 12:22:10 -0400 From: "Ben Kaduk" To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Re: 7.0 issues fixed? upgrade timing? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2008 16:50:09 -0000 Hi all, I only just now subscribed, so my apologies if this has been covered and my cursory search missed it. I am seeing a similar issue to the one described in the email below (pasted from a web listing of this list). That is, my ssh connection will occasionally be dropped with the message Disconnecting: Bad packet length 3190815048. (the number is not always the same). I can reliably reproduce this with `cat < /dev/urandom | od -c` from a FreeBSD-current box (a few weeks old, actually, since the build was broken when I last tried to update) as well as from a mac running OS X 10.4 . The system that is killing my connections is: FreeBSD periphrasis.mit.edu 7.0-STABLE FreeBSD 7.0-STABLE #3: Tue Mar 25 14:53:51 EDT 2008 kaduk@periphrasis.mit.edu:/usr/obj/usr/src/sys/PERIPHRASIS amd64 Any thoughts would be appreciated. -Ben Kaduk ------------------ random message from this thread, for some context ------------- * From: Jeremy Chadwick * Date: Mon, 12 May 2008 05:32:07 -0700 On Mon, May 12, 2008 at 01:44:22PM +0200, Torfinn Ingolfsen wrote: On Mon, 12 May 2008 11:37:53 +0200 Torfinn Ingolfsen wrote: FWIW, I had major troubles with re(4) around 7.0-release, and a while later (I had to use patches). After upgrading to 7-stable on 2008-04-12, re(4) is working for me without patches. (sigh).. it seems that I spoke to soon. Murphy just showed up. I still get ssh disconnects (see below) on connections _to_ the machine when transferring largish amounts of data (like when upgrading a port). Here is one example (portupgrading the jdk port): /usr/bin/gcc -fno-strict-aliasing -fPIC -W -Wall -Wno-unused -Wno-parentheses -pipe -Damd64 -DARCH='"amd64"' -DRELEASE='"1.6.0_03-p4"' -DFULL_VERSION='"1.6.0_03-p4-root_12_may_2008_13_25-b00"' -D_GNU_SOURCE -D_REENTRANT -D_THREAD_SAFE -D_ALLBSD_SOURCE -D_LP64=1 -I. -I/usr/ports/java/jdk16/work/control/build/bsd-amd64/tmp/java/java.lang.management/management/CClassHeaders -I../../../src/solaris/javavm/export -I../../../src/share/javavm/export -I../../../src/share/javavm/include -I../../../src/solaris/javavm/include -I../../../src/share/native/sun/management -I../../../src/solaris/hpi/include -I../../../src/share/native/common -I../../../src/solaris/native/common -I../../../src/share/native/java/lang/management -I../../../src/solaris/native/java/lang/management -c -o /usr/ports/java/jdk16/work/control/build/bsd-amd64/tmp/java/java.lang.management/management/obj64/ClassLoadingImpl.o ../../../src/share/native/sun/management/ClassLoadingImpl.c Disconnecting: Bad packet length 3601161525. The machine is running: tingo@kg-vm$ uname -a FreeBSD kg-vm.kg4.no 7.0-STABLE FreeBSD 7.0-STABLE #10: Sat Apr 12 21:42:55 CEST 2008 root@xxxxxxxxxxxx:/usr/obj/usr/src/sys/GENERIC amd64 and has been up for about 14 days: tingo@kg-vm$ uptime 1:36PM up 14 days, 17:42, 7 users, load averages: 2.15, 1.85, 1.34 I see that if_re.c for RELENG_7 has been updated on April 22nd, so I'll upgrade the machine to latest -stable and see if that works better. Is this machine using pf(4) at all? From owner-freebsd-stable@FreeBSD.ORG Tue May 13 16:53:42 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CAF7C1065675; Tue, 13 May 2008 16:53:42 +0000 (UTC) (envelope-from alex.kovalenko@verizon.net) Received: from vms042pub.verizon.net (vms042pub.verizon.net [206.46.252.42]) by mx1.freebsd.org (Postfix) with ESMTP id ABE4C8FC21; Tue, 13 May 2008 16:53:42 +0000 (UTC) (envelope-from alex.kovalenko@verizon.net) Received: from [10.0.3.231] ([70.111.2.75]) by vms042.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0K0T00H4WG8VHEH9@vms042.mailsrvcs.net>; Tue, 13 May 2008 11:53:20 -0500 (CDT) Date: Tue, 13 May 2008 12:37:56 -0400 From: "Alexandre \"Sunny\" Kovalenko" In-reply-to: <4828FDE5.8090409@freebsd.org> To: Sam Leffler Message-id: <1210696676.985.18.camel@RabbitsDen> MIME-version: 1.0 X-Mailer: Evolution 2.22.1.1 FreeBSD GNOME Team Port Content-type: text/plain; charset=utf-8 Content-transfer-encoding: 8BIT References: <1210640542.1008.33.camel@RabbitsDen> <4828FDE5.8090409@freebsd.org> Cc: stable@freebsd.org Subject: Re: Hard(?) lock when reassociating ath with wpa_supplicant on RELENG_7 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2008 16:53:42 -0000 On Mon, 2008-05-12 at 19:33 -0700, Sam Leffler wrote: > Alexandre "Sunny" Kovalenko wrote: > > I seem to be able to lock my machine by going into wpa_cli and asking it > > to 'reassoc'. The reason for question mark after "hard" is that debug > > information (caused by wlandebug and athdebug) is being printed on the > > console. The only way to get machine's attention is to hold power button > > for 8 seconds. > > So this is just livelock due to console debug msgs. I am not sure, I have parsed this well enough, so I will try to clarify: machine becomes unresponsive *without* any debugging turned on, to an extent that pressing the power button twice *does not* generate ACPI console message (something to the tune of "going into S5 already -- gimme a break"). If I turn ath debugging on, I do see those messages, and only them, scrolling on the console. > > > > > Note: manual reassociation is just the handy way to reproduce the > > problem -- I have had machine locking up on me the whole day long > > completely on its own. > > > > Below are, what I think, relevant pieces of information. If anything is > > missing, please, chastise me appropriately and will do my best to > > provide. I have rigged firewire console, but am unable to break into the > > debugger locally or remotely. > > I see no log msgs. I am sorry -- mailman must have eaten it up -- I have posted them here now: http://members.verizon.net/~akovalenko/Misc/reassoc.log.gz > > > > > While I am on the subject, I would appreciate couple of the > > troubleshooting suggestions: > > * is there any way to get sysctl dev.ath.0.debug to appear, other then > > defining ATH_DEBUG in something like /usr/src/sys/dev/ath/ah_osdep.h? > > options ATH_DEBUG That does not seem to work for if_ath built as the module, sorry for not being clear in that respect. > > > * is there minimal, but still usable mask for athdebug and wlandebug? I > > have started with 0xFFFFFFFF and kept trimming likely high-volume > > settings until output slowed down to the reasonable pace. > > Why do you want debug msgs from ath? The debug msgs from wlandebug > depend on what you're trying to debug. Because neither wpa_supplicant (quoted below), nor wlandebug (in the URL above) gave me the answer -- it looks like we are going into the scan with the specific SSID in mind and never come back, so I went for the next level. However, could you, please, clarify that I understood you correctly -- you *do not* want to see mix of wlandebug and athdebug messages in the report, and I should turn wlandebug off before turning athdebug on, right? > > I suggest that when debugging you start from the highest layer and move > downward. If you can't find what you need in a wpa_supplicant log then > turn on msgs in net80211 with wlandebug. If that doesn't tell you what > you need then move to the driver. Blindly turning everything on can > easily livelock your system. That's what I did -- what I have posted is the end result of the walking down that chain, and I assumed, possibly incorrectly, that you would want result of all three to put things in context. I do apologize for the misunderstanding. > For high volume msgs I often do something > like: > > athdebug +intr; sleep 1; athdebug -intr > > or > > athdebug +intr; read x; athdebug -intr > > so a carriage return will disable msgs. Thank you for the suggestion. > > > > * what facility does wpa_supplicant use, when forced to syslog by -s > > switch? > > trouble% cd /data/freebsd/head/contrib/wpa_supplicant/ > trouble% grep openlog *.c > common.c: openlog("wpa_supplicant", LOG_PID | LOG_NDELAY, LOG_DAEMON); Thank you, should have done this myself, sorry. -- Alexandre "Sunny" Kovalenko (ОлекÑандр Коваленко) From owner-freebsd-stable@FreeBSD.ORG Tue May 13 16:59:39 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CBCAC1065672 for ; Tue, 13 May 2008 16:59:39 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from angel.ticketswitch.com (angel.ticketswitch.com [IPv6:2002:57e0:1d4e::1]) by mx1.freebsd.org (Postfix) with ESMTP id 891AF8FC13 for ; Tue, 13 May 2008 16:59:39 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from [10.50.50.2] (helo=smaug.rattatosk) by angel.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1Jvxqj-0004U0-Ot; Tue, 13 May 2008 17:59:37 +0100 Received: from dilbert.rattatosk ([10.50.50.6] helo=dilbert.ticketswitch.com) by smaug.rattatosk with esmtp (Exim 4.69 (FreeBSD)) (envelope-from ) id 1Jvxqj-0005hK-MI; Tue, 13 May 2008 17:59:37 +0100 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1Jvxqj-0000Vw-LI; Tue, 13 May 2008 17:59:37 +0100 To: bakul@bitblocks.com In-Reply-To: <20080513163015.153205B55@mail.bitblocks.com> Message-Id: From: Pete French Date: Tue, 13 May 2008 17:59:37 +0100 Cc: stable@freebsd.org Subject: Re: Changing an installed system from i386 to amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2008 16:59:39 -0000 > If you run only the latest standard binaries you are right > but typically one acquires useful things over time and it is > not always possible to recompile them and also, why bother. true, but in this case I want to change a more or less vanilla 7-STABLE/i386 to a more or less vanilla 7-STABLE/amd74, just preserving all my user data and config files. It sounds like it should work then, and I'll give it a shot, thanks. -pete. From owner-freebsd-stable@FreeBSD.ORG Tue May 13 17:45:56 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8FBA71065674 for ; Tue, 13 May 2008 17:45:56 +0000 (UTC) (envelope-from gaijin.k@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.246]) by mx1.freebsd.org (Postfix) with ESMTP id 45B228FC1B for ; Tue, 13 May 2008 17:45:56 +0000 (UTC) (envelope-from gaijin.k@gmail.com) Received: by an-out-0708.google.com with SMTP id b33so699217ana.13 for ; Tue, 13 May 2008 10:45:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:cc:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding; bh=uLr5rDqBjFgnsrOJQb1zvgkdT2pMLOm/Rv5LJf5IUuQ=; b=TX4znJZjvthF92VOntEYTdZMsYs+cxR8ES3PbFrVIUqdop7j0m0Kmu1mmRkjnCjCEimzU5mG/VuMrghrVbWh9y2GuXV5N9AcSahwDEGYP1ny4rVFfCPyRL6umtGzMigFA8A1F4fy4vkcMQFsJfOOYbC6rNMiN6ZFnN9zre6KsSs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding; b=W4i5/p6eCQD2QF4hcwA3Q6QoKcDZJ2u0JrIW105qxKG9GsR3IAl6aniUjHdyMfF+IdHdVnHwXLrieIpSvA1iC4YBGUs9+WzQID6WO0KYtntscyqZmgQW6Xa1yvA41HvG9N8w/rCzNSc441J0RxyTD6+rcopPlYC8dN4vli/Evgc= Received: by 10.100.173.9 with SMTP id v9mr10089452ane.39.1210699215373; Tue, 13 May 2008 10:20:15 -0700 (PDT) Received: from ?10.0.3.231? ( [70.111.2.75]) by mx.google.com with ESMTPS id 9sm178675wrl.31.2008.05.13.10.20.13 (version=SSLv3 cipher=RC4-MD5); Tue, 13 May 2008 10:20:14 -0700 (PDT) From: "Alexandre \"Sunny\" Kovalenko" To: Ian Smith In-Reply-To: References: Content-Type: text/plain; charset=utf-8 Date: Tue, 13 May 2008 13:19:25 -0400 Message-Id: <1210699165.2238.1.camel@RabbitsDen> Mime-Version: 1.0 X-Mailer: Evolution 2.22.1.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 8bit Cc: stable@freebsd.org Subject: Re: ATA APM and NCQ support in FreeBSD atacontrol X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2008 17:45:56 -0000 On Mon, 2008-05-12 at 14:52 +1000, Ian Smith wrote: > On Sun, 11 May 2008 jonathan@kc8onw.net wrote: > > Has any work been done recently towards adding SATA Native Command > > Queueing as well as ATA APM and acoustic management to FreeBSD? > > > > I found this PR (with patch) to add APM and acoustic management control to > > atacontrol. The PR was opened in May 2005 has not been changed since > > December 2006 and is still open. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=81692&cat= > > > > I have not been able to find much of anything on SATA NCQ in FreeBSD newer > > than 2005 or 2006 does anyone know anything newer? > > Jeremy has addressed the NCQ issue, about which I know nothing. > > As for APM and AAM, that functionality is handled by sysutils/ataidle, > which that PR appears - on a quick glance - to pretty well duplicate. > > I see phk@ recently added an 'atacontrol spindown' command to HEAD and > RELENG_7 that appears to offer similar functionality to 'ataidle -S > standby_mins' or 'ataidle -I idle_mins', though specified in seconds > instead. However this doesn't address acoustic management. > > Or is ataidle broken for SATA disks? Does not look broken here (RELENG_7): RabbitsDen# ataidle /dev/ad4 Device Info: Model: HTS541010G9SA00 Serial: MP2ZM4X0JWY6WH Firmware Rev: MBZIC60H ATA revision: ATA-7 LBA 48: yes Geometry: 16383 cyls, 16 heads, 63 spt Capacity: 93GB SMART Supported: yes SMART Enabled: yes APM Supported: yes APM Enabled: yes AAM Supported: yes AAM Enabled: yes Current AAM: 1 Vendor Recommends AAM: 1 APM Value: 16638 RabbitsDen# atacontrol list ATA channel 0: Master: no device present Slave: no device present ATA channel 1: Master: no device present Slave: no device present ATA channel 2: Master: ad4 Serial ATA v1.0 Slave: no device present ATA channel 3: Master: no device present Slave: no device present ATA channel 4: Master: no device present Slave: no device present ATA channel 5: Master: no device present Slave: no device present atacontrol: ioctl(IOCATADEVICES): Device not configured RabbitsDen# uname -a FreeBSD RabbitsDen.RabbitsLawn.verizon.net 7.0-STABLE FreeBSD 7.0-STABLE #1: Sun May 11 20:31:21 EDT 2008 root@RabbitsDen.RabbitsLawn.verizon.net:/usr/src/sys/i386/compile/TPX60 i386 RabbitsDen# > > cheers, Ian > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" -- Alexandre "Sunny" Kovalenko (ОлекÑандр Коваленко) From owner-freebsd-stable@FreeBSD.ORG Tue May 13 18:31:38 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CE5341065673 for ; Tue, 13 May 2008 18:31:38 +0000 (UTC) (envelope-from bsam@ipt.ru) Received: from services.ipt.ru (services.ipt.ru [194.62.233.110]) by mx1.freebsd.org (Postfix) with ESMTP id 826DD8FC1F for ; Tue, 13 May 2008 18:31:38 +0000 (UTC) (envelope-from bsam@ipt.ru) Received: from [85.173.17.7] (helo=localhost.my.domain) by services.ipt.ru with esmtpa (Exim 4.54 (FreeBSD)) id 1JvyxM-000Esy-EI; Tue, 13 May 2008 22:10:32 +0400 To: bazzoola References: From: Boris Samorodov Date: Tue, 13 May 2008 22:10:09 +0400 In-Reply-To: (bazzoola@gmail.com's message of "Mon\, 12 May 2008 20\:56\:20 -0400") Message-ID: <18780206@ipt.ru> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-stable Subject: Re: kqemu support: not compiled X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2008 18:31:38 -0000 On Mon, 12 May 2008 20:56:20 -0400 bazzoola wrote: > I just cant get kqemu to work on my AMD64 SMP! > I setenv WITH_KQEMU > I compiled the port with make -DWITH_KQEMU > I edited src.conf and added WITH_KQEMU=yes > I make config and checked KQEMU ALPHA support > I am running > #uname -a > FreeBSD Aa.bsd 7.0-STABLE FreeBSD 7.0-STABLE #3: Mon Apr 21 05:56:16 > CDT 2008 root@Aa.bsd:/usr/obj/usr/src/sys/GENERIC amd64 > #pkg_info | grep qemu > kqemu-kmod-1.3.0.p11_6 > qemu-devel-0.9.1s.20080302_6 > latest as you as see ^^^ > any ideas? You didn't show the actual command and an error message. -- WBR, bsam From owner-freebsd-stable@FreeBSD.ORG Tue May 13 19:00:49 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 282A11065675 for ; Tue, 13 May 2008 19:00:49 +0000 (UTC) (envelope-from nox@saturn.kn-bremen.de) Received: from gwyn.kn-bremen.de (gwyn.kn-bremen.de [212.63.36.242]) by mx1.freebsd.org (Postfix) with ESMTP id D49EF8FC0C for ; Tue, 13 May 2008 19:00:48 +0000 (UTC) (envelope-from nox@saturn.kn-bremen.de) Received: by gwyn.kn-bremen.de (Postfix, from userid 10) id 7D5B02D31F8; Tue, 13 May 2008 20:40:48 +0200 (CEST) Received: from saturn.kn-bremen.de (nox@localhost [127.0.0.1]) by saturn.kn-bremen.de (8.14.2/8.13.8) with ESMTP id m4DIZRcM010015; Tue, 13 May 2008 20:35:27 +0200 (CEST) (envelope-from nox@saturn.kn-bremen.de) Received: (from nox@localhost) by saturn.kn-bremen.de (8.14.2/8.13.6/Submit) id m4DIZQZq010014; Tue, 13 May 2008 20:35:26 +0200 (CEST) (envelope-from nox) Date: Tue, 13 May 2008 20:35:26 +0200 (CEST) From: Juergen Lock Message-Id: <200805131835.m4DIZQZq010014@saturn.kn-bremen.de> To: bakul@bitblocks.com X-Newsgroups: local.list.freebsd.stable In-Reply-To: <20080513045159.1563C5B4B@mail.bitblocks.com> References: Organization: home Cc: freebsd-stable@freebsd.org Subject: Re: kqemu support: not compiled X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2008 19:00:49 -0000 In article <20080513045159.1563C5B4B@mail.bitblocks.com> you write: >On Tue, 13 May 2008 00:18:32 EDT bazzoola wrote: >> >> On May 12, 2008, at 10:20 PM, Bakul Shah wrote: >> >> >> I just cant get kqemu to work on my AMD64 SMP! >> > >> > echo kqemu_enable=YES >> /etc/rc.conf >> > /usr/local/etc/rc.d/kqemu start > >This should probably be described in pkg-message. > >> I looked at the rc script and all it does is kldload aio and kqemu. I >> already have them loaded by default. > >You didn't provide information so I had to guess. > >> This still does not help me with my problem. >> >> I press Ctrl + Alt + 2 >> then I type info kqemu >> I get "kqemu support: not compiled" > >Are you running qemu? It is an i386 emulator and won't use >kqemu on amd64. You need to run qemu-system-x86_64. I know, >this is a bit confusing. I just added notes about these two things to the pkg-message(s)... Juergen From owner-freebsd-stable@FreeBSD.ORG Tue May 13 19:01:12 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AF6351065679 for ; Tue, 13 May 2008 19:01:12 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail09.syd.optusnet.com.au (mail09.syd.optusnet.com.au [211.29.132.190]) by mx1.freebsd.org (Postfix) with ESMTP id 3D4FA8FC16 for ; Tue, 13 May 2008 19:01:12 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c122-106-215-175.belrs3.nsw.optusnet.com.au [122.106.215.175]) by mail09.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m4DJ12Ds026302 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 14 May 2008 05:01:06 +1000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.2/8.14.2) with ESMTP id m4DJ128E062406; Wed, 14 May 2008 05:01:02 +1000 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.2/8.14.2/Submit) id m4DJ0vAF062402; Wed, 14 May 2008 05:00:57 +1000 (EST) (envelope-from peter) Date: Wed, 14 May 2008 05:00:57 +1000 From: Peter Jeremy To: Bakul Shah Message-ID: <20080513190057.GH64804@server.vk2pj.dyndns.org> References: <20080513153303.35BFA5B55@mail.bitblocks.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="u3/rZRmxL6MmkK24" Content-Disposition: inline In-Reply-To: <20080513153303.35BFA5B55@mail.bitblocks.com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.17 (2007-11-01) Cc: stable@freebsd.org, Pete French Subject: Re: Changing an installed system from i386 to amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2008 19:01:12 -0000 --u3/rZRmxL6MmkK24 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2008-May-13 08:33:03 -0700, Bakul Shah wrote: >Most all old 32 bit ports should work but upgrading them can >mess things up. All the new compiles will generate 64 bit >binaries but any port dependencies on a shared library will >be wrong. It's actually somewhat worse than this: When compiling a new port with dependencies, the internal foo_DEPENDS logic will detect the i386 .so but the port's own configuration tools or build process will normally die in interesting ways when they can't actually use that .so. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --u3/rZRmxL6MmkK24 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkgp5WkACgkQ/opHv/APuIczYgCgqDl1NlLLXi1qwflknOQGeqxW 4vAAoJYFAEk3/MFsdM1lrbeXHT9kd9oA =tUZW -----END PGP SIGNATURE----- --u3/rZRmxL6MmkK24-- From owner-freebsd-stable@FreeBSD.ORG Tue May 13 19:36:59 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 145E4106564A for ; Tue, 13 May 2008 19:36:59 +0000 (UTC) (envelope-from ben@altus-escon.com) Received: from altus-escon.com (altesco.xs4all.nl [82.95.106.39]) by mx1.freebsd.org (Postfix) with ESMTP id 661838FC1D for ; Tue, 13 May 2008 19:36:57 +0000 (UTC) (envelope-from ben@altus-escon.com) Received: from giskard.altus-escon.com (giskard.altus-escon.com [193.78.231.1]) by altus-escon.com (8.14.2/8.14.2) with ESMTP id m4DJL3Wg003129 for ; Tue, 13 May 2008 21:21:08 +0200 (CEST) (envelope-from ben@altus-escon.com) Message-Id: <7A0780B6-AD8E-440B-BFDB-EC2C4ACA1A70@altus-escon.com> From: Ben Stuyts To: stable@freebsd.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v919.2) Date: Tue, 13 May 2008 21:20:08 +0200 X-Mailer: Apple Mail (2.919.2) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (altus-escon.com [193.78.231.142]); Tue, 13 May 2008 21:21:08 +0200 (CEST) X-Virus-Scanned: ClamAV version 0.93, clamav-milter version 0.93 on mars.altus-escon.com X-Virus-Status: Clean X-Spam-Status: No, score=-2.3 required=3.5 tests=AWL,BAYES_00 autolearn=ham version=3.2.4 X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on mars.altus-escon.com Cc: Subject: Panic after hung rsync, probably zfs related X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2008 19:36:59 -0000 Hi, While doing an rsync from a zfs filesystem to an external usb hd (also zfs), the rsync processes hung in zfs state. I could not kill these processes, although the rest of the server seemingly continued to run fine. The reboot command did not work. Next I tried a shutdown now command. This caused a panic: ... Stopping dhcpd. Shutting down local daemons:. Stopping named. Waiting for PIDS: 106830 second watchdog timeout expired. Shutdown terminated. Tue May 13 21:02:50 CEST 2008 May 13 21:02:50 mars init: /bin/sh on /etc/rc.shutdown terminated abnormally, going to single user mode panic: vrele: negative ref cnt cpuid = 6 Uptime: 8d3h8m21s Physical memory: 8178 MB Dumping 3679 MB: 3664 3648 3632 3616 3600 3584 3568 3552 3536 3520 3504 3488 3472 3456 3440 3424 3408 3392 3376 3360 3344 3328 3312 3296 3280 3264 3248 atl trap 12: page fault while in kernel mode cpuid = 2; apic id = 02 fau =Fta tvailr tduoaulb laed dfraeuslst = r0ixp8 v f0axuflftf fcfofdfef 8 0=6 esbuap9e3r girssopr =r e0axdf fifnfsftfrfufcftbi5o4n8,f fp0a er bnpo t= p0rxe1s0e0n0t xipnusitdr u=c t0i;o na ppioci nitde r= =0 00 8:0x8 stack pointer = 0x10:0xfffffffff8c50a50 frame pointer = 0x10:0xfffffffffb54c450 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 44 (irq19: uhci1+) trap number = 12 Yes, it printed all that gibberish. ("double fault" I think it says?) At this point, the server completely hung, and I could not do a bt unfortunately. I had to reset the server. After reboot, savecore did not find a kernel dump. I ran the rsync again and could not reproduce the problem. Although I've had zfs related problems before, this one was new to me. Any idea what happened here? Other info on this machine follows below. Thanks, Ben [mars:~]133: uname -a FreeBSD mars.altus-escon.com 7.0-STABLE FreeBSD 7.0-STABLE #2: Mon Apr 21 08:45:56 CEST 2008 root@mars.altus-escon.com:/usr/obj/usr/src/ sys/MARS amd64 [mars:~]134: cat /boot/loader.conf console="comconsole" zfs_load="YES" vfs.root.mountfrom="zfs:tank" vfs.zfs.prefetch_disable=1 vm.kmem_size="1536M" vm.kmem_size_max="1536M" vfs.zfs.arc_max="768M" [mars:~]135: dmesg Copyright (c) 1992-2008 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.0-STABLE #2: Mon Apr 21 08:45:56 CEST 2008 root@mars.altus-escon.com:/usr/obj/usr/src/sys/MARS Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(R) CPU E5335 @ 2.00GHz (2000.08-MHz K8- class CPU) Origin = "GenuineIntel" Id = 0x6f7 Stepping = 7 Features = 0xbfebfbff < FPU ,VME ,DE ,PSE ,TSC ,MSR ,PAE ,MCE ,CX8 ,APIC ,SEP ,MTRR ,PGE ,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> Features2 =0x4e33d AMD Features=0x20100800 AMD Features2=0x1 Cores per package: 4 usable memory = 8575598592 (8178 MB) avail memory = 8285937664 (7902 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 cpu4 (AP): APIC ID: 4 cpu5 (AP): APIC ID: 5 cpu6 (AP): APIC ID: 6 cpu7 (AP): APIC ID: 7 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: on acpi0 p4tcc0: on cpu0 cpu1: on acpi0 p4tcc1: on cpu1 cpu2: on acpi0 p4tcc2: on cpu2 cpu3: on acpi0 p4tcc3: on cpu3 cpu4: on acpi0 p4tcc4: on cpu4 cpu5: on acpi0 p4tcc5: on cpu5 cpu6: on acpi0 p4tcc6: on cpu6 cpu7: on acpi0 p4tcc7: on cpu7 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 2.0 on pci0 pci1: on pcib1 pcib2: irq 16 at device 0.0 on pci1 pci2: on pcib2 pcib3: irq 16 at device 0.0 on pci2 pci3: on pcib3 pcib4: at device 0.0 on pci3 pci4: on pcib4 pcib5: irq 18 at device 2.0 on pci2 pci5: on pcib5 em0: port 0x2000-0x201f mem 0xd8000000-0xd801ffff irq 18 at device 0.0 on pci5 em0: Using MSI interrupt em0: Ethernet address: 00:30:48:7b:88:7e em0: [FILTER] em1: port 0x2020-0x203f mem 0xd8020000-0xd803ffff irq 19 at device 0.1 on pci5 em1: Using MSI interrupt em1: Ethernet address: 00:30:48:7b:88:7f em1: [FILTER] pcib6: at device 0.3 on pci1 pci6: on pcib6 puc0: port 0x3030-0x3037,0x3028-0x302f,0x3020-0x3027,0x3018-0x301f, 0x3010-0x3017,0x3000-0x300f irq 24 at device 1.0 on pci6 puc0: [FILTER] uart0: on puc0 uart0: [FILTER] uart1: on puc0 uart1: [FILTER] ppc0: on puc0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppbus0: on ppc0 plip0: cannot reserve interrupt, failed. lpt0: on ppbus0 lpt0: Polled port ppi0: on ppbus0 pcib7: at device 4.0 on pci0 pci7: on pcib7 pcib8: at device 6.0 on pci0 pci8: on pcib8 pci0: at device 8.0 (no driver attached) uhci0: port 0x1800-0x181f irq 17 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: on uhci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: port 0x1820-0x183f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: on uhci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0x1840-0x185f irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] uhci2: [ITHREAD] usb2: on uhci2 usb2: USB revision 1.0 uhub2: on usb2 uhub2: 2 ports with 2 removable, self powered ehci0: mem 0xd8500000-0xd85003ff irq 17 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb3: EHCI version 1.0 usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 uhub3: on usb3 uhub3: 6 ports with 6 removable, self powered umass0: on uhub3 ums0: on uhub3 ums0: X report 0x0022 not supported device_attach: ums0 attach returned 6 pcib9: at device 30.0 on pci0 pci9: on pcib9 vgapci0: port 0x4000-0x40ff mem 0xd0000000-0xd7ffffff,0xd8220000-0xd822ffff irq 18 at device 1.0 on pci9 em2: port 0x4400-0x443f mem 0xd8200000-0xd821ffff irq 16 at device 2.0 on pci9 em2: Ethernet address: 00:30:48:44:1a:ab em2: [FILTER] isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1860-0x186f at device 31.1 on pci0 ata0: on atapci0 ata0: [ITHREAD] ata1: on atapci0 ata1: [ITHREAD] atapci1: port 0x1890-0x1897,0x1884-0x1887,0x1888-0x188f,0x1880-0x1883,0x1870-0x187f mem 0xd8500400-0xd85007ff irq 19 at device 31.2 on pci0 atapci1: [ITHREAD] ata2: on atapci1 ata2: [ITHREAD] ata3: on atapci1 ata3: [ITHREAD] pci0: at device 31.3 (no driver attached) acpi_button0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio0: [FILTER] sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 flags 0x10 on acpi0 sio1: type 16550A, console sio1: [FILTER] fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FILTER] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 orm0: at iomem 0xc0000-0xcafff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 WARNING: ZFS is considered to be an experimental feature in FreeBSD. Timecounters tick every 1.000 msec ipfw2 (+ipv6) initialized, divert enabled, nat loadable, rule-based forwarding disabled, default to deny, logging limited to 50 packets/ entry by default ZFS filesystem version 6 ZFS storage pool version 6 acd0: DMA limited to UDMA33, controller found non-ATA66 cable acd0: DVDROM at ata0-slave UDMA33 ad4: 143089MB at ata2-master SATA150 ad6: 143089MB at ata3-master SATA150 SMP: AP CPU #2 Launched! SMP: AP CPU #1 Launched! SMP: AP CPU #3 Launched! SMP: AP CPU #4 Launched! SMP: AP CPU #5 Launched! SMP: AP CPU #6 Launched! SMP: AP CPU #7 Launched! da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-3 device da0: 40.000MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present Trying to mount root from zfs:tank em1: link state changed to UP em0: link state changed to UP em0: link state changed to DOWN em0: link state changed to UP umass1: on uhub3 da1 at umass-sim1 bus 1 target 0 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers da1: 238475MB (488397168 512 byte sectors: 255H 63S/T 30401C) From owner-freebsd-stable@FreeBSD.ORG Tue May 13 19:53:37 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C7C87106566C for ; Tue, 13 May 2008 19:53:37 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.delphij.net (delphij-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:2c9::2]) by mx1.freebsd.org (Postfix) with ESMTP id 6B40A8FC2F for ; Tue, 13 May 2008 19:53:37 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.geekcn.org (tarsier.geekcn.org [202.108.54.204]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tarsier.delphij.net (Postfix) with ESMTPS id 8D51928448 for ; Wed, 14 May 2008 03:53:36 +0800 (CST) Received: from localhost (tarsier.geekcn.org [202.108.54.204]) by tarsier.geekcn.org (Postfix) with ESMTP id 113D0EC3198; Wed, 14 May 2008 03:53:36 +0800 (CST) X-Virus-Scanned: amavisd-new at geekcn.org Received: from tarsier.geekcn.org ([202.108.54.204]) by localhost (mail.geekcn.org [202.108.54.204]) (amavisd-new, port 10024) with ESMTP id 1-dOP8b6d0T2; Wed, 14 May 2008 03:53:31 +0800 (CST) Received: from charlie.delphij.net (71.5.7.139.ptr.us.xo.net [71.5.7.139]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTPSA id 5D435EB0A75; Wed, 14 May 2008 03:53:30 +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=LAYmwrnKIhr6IBoDNJ0DTopn9Cfwf0OTNOSP1nY6OYhlCuHsLdtM/Y4bhx5fLz4nY P3j3WUfCzcCCo8aE7BOBA== Message-ID: <4829F1B8.1000707@delphij.net> Date: Tue, 13 May 2008 12:53:28 -0700 From: Xin LI Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.14 (X11/20080505) MIME-Version: 1.0 To: Ben Stuyts References: <7A0780B6-AD8E-440B-BFDB-EC2C4ACA1A70@altus-escon.com> In-Reply-To: <7A0780B6-AD8E-440B-BFDB-EC2C4ACA1A70@altus-escon.com> X-Enigmail-Version: 0.95.6 OpenPGP: id=18EDEBA0; url=http://www.delphij.net/delphij.asc Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org Subject: Re: Panic after hung rsync, probably zfs related X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: d@delphij.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2008 19:53:37 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ben Stuyts wrote: | Hi, | | While doing an rsync from a zfs filesystem to an external usb hd (also | zfs), the rsync processes hung in zfs state. I could not kill these | processes, although the rest of the server seemingly continued to run | fine. The reboot command did not work. Next I tried a shutdown now | command. This caused a panic: Sound like you somehow run out of memory, there is an known issue with ZFS which causes livelock when there is memory pressure. Which rsync version are you using? With rsync 3.x the memory usage would drop drastically which would help to prevent this from happening. Cheers, - -- ** Help China's quake relief at http://www.redcross.org.cn/ |>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkgp8bcACgkQi+vbBBjt66DQQgCfSObZqsQNCteT9SsjDTIqAa2E xfgAnAs9reRKfjaJdS9RAco0cnD7JZp0 =J4+1 -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Tue May 13 20:36:25 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2E24D1065673 for ; Tue, 13 May 2008 20:36:25 +0000 (UTC) (envelope-from mcdouga9@egr.msu.edu) Received: from mx.egr.msu.edu (surfnturf.egr.msu.edu [35.9.37.164]) by mx1.freebsd.org (Postfix) with ESMTP id EEE508FC1A for ; Tue, 13 May 2008 20:36:24 +0000 (UTC) (envelope-from mcdouga9@egr.msu.edu) Received: from localhost (localhost [127.0.0.1]) by mx.egr.msu.edu (Postfix) with ESMTP id 5E01971F0C8; Tue, 13 May 2008 16:36:24 -0400 (EDT) X-Virus-Scanned: amavisd-new at egr.msu.edu Received: from mx.egr.msu.edu ([127.0.0.1]) by localhost (surfnturf.egr.msu.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id noKpmnPKCXlg; Tue, 13 May 2008 16:36:24 -0400 (EDT) Received: from [35.9.44.65] (daemon.egr.msu.edu [35.9.44.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: mcdouga9) by mx.egr.msu.edu (Postfix) with ESMTPSA id 2085F71EF51; Tue, 13 May 2008 16:36:24 -0400 (EDT) Message-ID: <4829FBC8.5040101@egr.msu.edu> Date: Tue, 13 May 2008 16:36:24 -0400 From: Adam McDougall User-Agent: Thunderbird 2.0.0.14 (X11/20080503) MIME-Version: 1.0 To: hartzell@alerce.com References: <18473.48984.31132.91673@almost.alerce.com> In-Reply-To: <18473.48984.31132.91673@almost.alerce.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: good/best practices for gmirror and gjournal on a pair of disks? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2008 20:36:25 -0000 George Hartzell wrote: > I've been running many of my systems for some time now using gmirror > on a pair of identical disks, as described by Ralf at: > > http://people.freebsd.org/~rse/mirror/ > > Each disk has single slice that covers almost all of the disk. These > slices are combined into the gmirror device (gm0), which is then > carved up by bsdlabel into gm0a (/), gm0b (swap), gm0d (/var), gm0e > (/tmp), and gm0f (/usr). > > My latest machine is using Seagate 1TB disks so I thought I should add > gjournal to the mix to avoid ugly fsck's if/when the machine doesn't > shut down cleanly. I ended up just creating a gm0f.journal and using > it for /usr, which basically seems to be working. > > I'm left with a couple of questions though: > > - I've read in the gjournal man page that when it is "... configured > on top of gmirror(8) or graid3(8) providers, it also keeps them in > a consistent state..." I've been trying to figure out if this > simply falls out of how gjournal works or if there's explicity > collusion with gmirror/graid3 but can't come up with a > satisfactory explanation. Can someone walk me through it? > > Since I'm only gjournal'ing a portion of the underlying gmirror > device I assume that I don't get this benefit? > > - I've also read in the gjournal man page "... that sync(2) and > fsync(2) system calls do not work as expected anymore." Does this > invalidate any of the assumptions made by various database > packages such as postgresql, sqlite, berkeley db, etc.... about > if/when/whether their data is safely on the disk? > > - What's the cleanest gjournal adaptation of rse's > two-disk-mirror-everything setup that would be able to avoid > tedious gmirror sync's. The best I've come up with is to do two > slices per disk, combine the slices into a pair of gmirror > devices, bsdlabel the first into gm0a (/), gm0b (swap), gm0d > (/var) and gm0e (/tmp) and bsdlabel the second into a gm1f which > gets a gjournal device. > > Alternatively, would it work and/or make sense to give each disk a > single slice, combine them into a gmirror, put a gjournal on top > of that, then use bsdlabel to slice it up into partitions? > > Is anyone using gjournal and gmirror for all of the system on a pair > of disks in some other configuration? > > Thanks, > > g. > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > I am pasting below the instructions I would use to convert a recently installed system with only / (root) and swap to be using gmirror+gjournal. It is in mediawiki markup format so it could be pasted into one if desired. I based my gmirror steps on the instructions from http://people.freebsd.org/~rse/mirror/ so thats why some of the words sound familiar. I also have similar instructions for setting up a gmirrored da0s1a and da0s1b alongside a zfs mirror containing the rest. I decided to journal /usr /var /tmp and leave / as a standard UFS partition because it is so small, fsck doesn't take long anyway and hopefully doesn't get written to enough to cause damage by an abrupt reboot. Because I'm not journaling the root partition, I chose to ignore the possibility of gjournal marking the mirror clean. Sudden reboots don't happen enough on servers for me to care. And all my servers got abruptly rebooted this sunday and they all came up fine :) I believe gjournal uses 1G for journal (2x512) which seemed to be sufficient on all of the systems where I have used the default, but I quickly found that using a smaller journal is a bad idea and leads to panics that I was unable to avoid with tuning. Considering 1G was such a close value, I chose to go several times above the default journal size (disk is cheap and I want to be sure) but I ran into problems using gjournal label -s (size) rejecting my sizes or wrapping the value around to something too low. As a workaround I chose to use a separate partition for each journal. I quickly ran out of partitions in a bsd disklabel so I decided to partition each disk into two slices; the first for data and the second for journals. This also made it easier to line up disk devices so they made more sense as a pair, for example: gm0s1d(data) + gm0s2d(journal) = /usr. I will note that if you accidentally put a gjournal label in the 'wrong' spot on your disk, you might make a tough situation for yourself getting rid of it. I have had plenty of times where I applied a gjournal label, discovered something unideal with it, but every time I did 'gjournal stop foo' the label would automatically get detected as a child of a different part of the disk because it could be seen and I could not unload it. That is part of why I use -h for gjournal label, and use slices+partitions, and the first partition is at offset 16, some of which may have been for gmirror's sake too. ==Software raid on 72G disks with gjournal== 5 min to setup, around 30 min to sync ===Prepare=== *Clear any old mirror config including old gmirror labels sysctl kern.geom.debugflags=16 gmirror clear da0 gmirror clear da1 sysctl kern.geom.debugflags=0 dd if=/dev/zero of=/dev/da1 bs=512 count=79 *place a GEOM mirror label onto second disk gmirror label -v -n -b round-robin gm0 /dev/da1 *activate GEOM mirror kernel layer gmirror load ===Partition=== *place a PC MBR onto the second disk to make it bootable. Also partition it with the majority of space as partition 1, and enough for your journal partitions as partition 2. '''You might get an error, such as "fdisk: Geom not found". If the next steps work, ignore the error.''' fdisk -v -B -I /dev/mirror/gm0 *Partition it into two slices. I think there is an easier way but I cannot remember how. Maybe I used a different method of using fdisk and ignored the end cyl values since they dont seem to make much sense anyway. sysinstall or sade could be used as an alternative. fdisk -i /dev/mirror/gm0 Do you want to change our idea of what BIOS thinks ? '''[n]''' The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 143363997 (70001 Meg), flag 80 (active) '' ^^^^^^^^^ A = 143363997'' beg: cyl 0/ head 1/ sector 1; end: cyl 731/ head 254/ sector 63 Do you want to change it? [n] '''y'''
''We want to make partitions approx 60G(data) and 10G(journals).'' ''So take variable A, divide by 7 and multiply by 6 to get var B.'' ''B = 122883426''
Supply a decimal value for "sysid (165=FreeBSD)" '''[165]''' Supply a decimal value for "start" '''[63]''' Supply a decimal value for "size" [143363997] '''122883426''' ''^^^^^^^^^'' ''put B here'' fdisk: WARNING: partition does not end on a cylinder boundary fdisk: WARNING: this may confuse the BIOS or some operating systems Correct this automatically? [n] '''y''' fdisk: WARNING: adjusting size of partition to 122881122 Explicitly specify beg/end address ? '''[n]''' sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 122881122 (60000 Meg), flag 80 (active) ''^^^^^^^^^'' ''C = 122881122'' ''D = C + 63 = 122881122 + 63 = 122881185'' ''E = A - C = 143363997 - 122881185 = 20482812''
beg: cyl 0/ head 1/ sector 1; end: cyl 480/ head 254/ sector 63 Are we happy with this entry? [n] '''y''' The data for partition 2 is: Do you want to change it? [n] '''y''' Supply a decimal value for "sysid (165=FreeBSD)" [0] '''165''' Supply a decimal value for "start" [0] '''122881185''' ''^^^^^^^^^'' ''put D here '' Supply a decimal value for "size" [0] '''20482812''' ''^^^^^^^^'' ''put E here'' Explicitly specify beg/end address ? '''[n]''' Are we happy with this entry? [n] '''y''' The data for partition 3 is: Do you want to change it? '''[n]''' The data for partition 4 is: Do you want to change it? '''[n]''' Partition 1 is marked active Do you want to change the active partition? '''[n]''' Should we write new partition table? [n] '''y''' '''You might get an error, such as "fdisk: Geom not found". If the next steps work, ignore the error.''' ===Disklabel=== *place a BSD disklabel onto the mirrors bsdlabel -w -B /dev/mirror/gm0s1 bsdlabel -w /dev/mirror/gm0s2 NOTICE: figure out what partitions you want by referring to bsdlabel /dev/da0s1 and/or running bsdlabel /dev/mirror/gm0s1 on a different server that has already been mirrored and partition to your liking. Size can be specified with ##M, ##G or * for remainder, and offset should be * to make it calculate it. Paste the output into the editor and make whatever changes you want as long as it includes: start "a" partition at offset 16, "c" partition at offset 0) *Partition 1: bsdlabel -e /dev/mirror/gm0s1 Example: # size offset fstype [fsize bsize bps/cpg] a: 1G 16 4.2BSD b: 4G * swap c: * 0 unused # "raw" part, don't edit d: 10G * 4.2BSD e: * * 4.2BSD f: 4G * 4.2BSD *Partition 2: bsdlabel -e /dev/mirror/gm0s2 Example: # size offset fstype [fsize bsize bps/cpg] c: * 0 unused # "raw" part, don't edit d: 4G 16 4.2BSD e: 4G * 4.2BSD f: * * 4.2BSD ===Gjournal label=== *Label the data and journals so the journaled partition is available. gjournal label -f -h mirror/gm0s1d mirror/gm0s2d gjournal label -f -h mirror/gm0s1e mirror/gm0s2e gjournal label -f -h mirror/gm0s1f mirror/gm0s2f *Load the kernel module so the journaled partitions are detected: gjournal load ===Newfs=== *Format the devices with journaling support in UFS: newfs /dev/mirror/gm0s1a newfs -J /dev/mirror/gm0s1d.journal newfs -J /dev/mirror/gm0s1e.journal newfs -J /dev/mirror/gm0s1f.journal ===Mount=== *Mount them temporarily: mount /dev/mirror/gm0s1a /mnt mkdir -p /mnt/usr /mnt/var /mnt/tmp mount -o async /dev/mirror/gm0s1d.journal /mnt/usr mount -o async /dev/mirror/gm0s1e.journal /mnt/var mount -o async /dev/mirror/gm0s1f.journal /mnt/tmp ===Copy Data=== *Install rsync, if not already: pkg_add -r rsync *Copy the original boot drive to the new device: rehash rsync -avHSx --progress / /mnt/ (This will take about 1 minute.) ===Prepare mirror for booting=== *Edit '''/mnt/etc/fstab''' replacing the following mountpoints: vi /mnt/etc/fstab Old: # Device Mountpoint FStype Options Dump Pass# /dev/da0s1b none swap sw 0 0 /dev/da0s1a / ufs rw 1 1 /dev/cd0 /cdrom cd9660 ro,noauto 0 0 /dev/acd0 /cdrom1 cd9660 ro,noauto 0 0 New: # Device Mountpoint FStype Options Dump Pass# /dev/mirror/gm0s1b none swap sw 0 0 /dev/mirror/gm0s1a / ufs rw 1 1 /dev/mirror/gm0s1d.journal /usr ufs rw,async 2 2 /dev/mirror/gm0s1e.journal /var ufs rw,async 2 2 /dev/mirror/gm0s1f.journal /tmp ufs rw,async 2 2 /dev/cd0 /cdrom cd9660 ro,noauto 0 0 /dev/acd0 /cdrom1 cd9660 ro,noauto 0 0 *Load necessary kernel modules at boot: echo 'geom_journal_load="YES"' >> /mnt/boot/loader.conf echo 'geom_mirror_load="YES"' >> /mnt/boot/loader.conf *instruct boot stage 2 loader on first disk to boot with the boot stage 3 loader from the second disk (mainly because BIOS might not allow easy booting from second ATA disk or at least requires manual intervention on the console) echo "1:da(1,a)/boot/loader" >/boot.config *We're done with the first stage, reboot: reboot ===Check results=== *Login and run df. Should look like this: Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/mirror/gm0s1a 1012974 201898 730040 22% / devfs 1 1 0 100% /dev /dev/mirror/gm0s1d.journal 10154156 144920 9196904 2% /usr /dev/mirror/gm0s1e.journal 40209204 322 36992146 0% /var /dev/mirror/gm0s1f.journal 4058060 12 3733404 0% /tmp ===Configure second disk into mirror=== *Add the original boot disk to the mirror. Make sure the first disk is treated as a really fresh one dd if=/dev/zero of=/dev/da0 bs=512 count=79 *switch GEOM mirror to auto-synchronization and add first disk (first disk is now immediately synchronized with the second disk content) gmirror configure -a gm0 gmirror insert gm0 /dev/da0 *Wait for the GEOM mirror synchronization to complete, or check it manually with ''gmirror list'' sh -c 'while [ ".`gmirror list | grep SYNCHRONIZING`" != . ]; do sleep 1; done' *Reboot into the final two-disk GEOM mirror setup (now actually boots with the MBR and boot stages on first disk as it was synchronized from second disk) reboot ===Mirror check script=== *Enable daily_status_gmirror_enable in /etc/periodic.conf or write your own script to monitor gmirror status From owner-freebsd-stable@FreeBSD.ORG Tue May 13 21:17:56 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 75C671065670 for ; Tue, 13 May 2008 21:17:56 +0000 (UTC) (envelope-from hartzell@alerce.com) Received: from merlin.alerce.com (merlin.alerce.com [64.62.142.94]) by mx1.freebsd.org (Postfix) with ESMTP id 5E8B38FC21 for ; Tue, 13 May 2008 21:17:56 +0000 (UTC) (envelope-from hartzell@alerce.com) Received: from merlin.alerce.com (localhost [127.0.0.1]) by merlin.alerce.com (Postfix) with ESMTP id F23B633C62; Tue, 13 May 2008 14:17:55 -0700 (PDT) Received: from postfix.alerce.com (w092.z064001164.sjc-ca.dsl.cnc.net [64.1.164.92]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by merlin.alerce.com (Postfix) with ESMTP id BADA833C5B; Tue, 13 May 2008 14:17:55 -0700 (PDT) Received: by postfix.alerce.com (Postfix, from userid 501) id EFDBC42C649; Tue, 13 May 2008 14:17:54 -0700 (PDT) From: George Hartzell MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18474.1410.744898.778947@almost.alerce.com> Date: Tue, 13 May 2008 14:17:54 -0700 To: Adam McDougall In-Reply-To: <4829FBC8.5040101@egr.msu.edu> References: <18473.48984.31132.91673@almost.alerce.com> <4829FBC8.5040101@egr.msu.edu> X-Mailer: VM 7.19 under Emacs 22.1.50.1 X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-stable@freebsd.org Subject: Re: good/best practices for gmirror and gjournal on a pair of disks? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: hartzell@alerce.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2008 21:17:56 -0000 Adam McDougall writes: > [...] > I believe gjournal uses 1G for journal (2x512) which seemed to be > sufficient on all of the systems where I have used the default, but I > quickly found that using a smaller journal is a bad idea and leads to > panics that I was unable to avoid with tuning. Considering 1G was such > a close value, I chose to go several times above the default journal > size (disk is cheap and I want to be sure) but I ran into problems using > gjournal label -s (size) rejecting my sizes or wrapping the value around > to something too low. [...] I also stumbled on this and was unable to find any mention of it in the pr database. One of my todo items is to make sure I'm not messing up somehow, dig further into the PR db for an existing report, and file one if I can't find one? I tried -s 2147483648 and it was found to be "too small". A quick read of the source led me to find that jsize is an intmax_t and that gctl_get_intmax() should be returning an intmax_t and that intmax_ ought to be an __int64_t (I'm on amd64), which left me confused. Has anyone else seen/reported a problem with gjournal -s and values > 1G? g. From owner-freebsd-stable@FreeBSD.ORG Tue May 13 21:48:14 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 912611065670 for ; Tue, 13 May 2008 21:48:14 +0000 (UTC) (envelope-from hartzell@alerce.com) Received: from merlin.alerce.com (merlin.alerce.com [64.62.142.94]) by mx1.freebsd.org (Postfix) with ESMTP id 78B848FC13 for ; Tue, 13 May 2008 21:48:14 +0000 (UTC) (envelope-from hartzell@alerce.com) Received: from merlin.alerce.com (localhost [127.0.0.1]) by merlin.alerce.com (Postfix) with ESMTP id 3957333C62; Tue, 13 May 2008 14:48:14 -0700 (PDT) Received: from postfix.alerce.com (w092.z064001164.sjc-ca.dsl.cnc.net [64.1.164.92]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by merlin.alerce.com (Postfix) with ESMTP id 5411A33C5B; Tue, 13 May 2008 14:48:13 -0700 (PDT) Received: by postfix.alerce.com (Postfix, from userid 501) id 97C9042C6E6; Tue, 13 May 2008 14:48:02 -0700 (PDT) From: George Hartzell MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18474.3218.145536.664367@almost.alerce.com> Date: Tue, 13 May 2008 14:48:02 -0700 To: Adam McDougall In-Reply-To: <4829FBC8.5040101@egr.msu.edu> References: <18473.48984.31132.91673@almost.alerce.com> <4829FBC8.5040101@egr.msu.edu> X-Mailer: VM 7.19 under Emacs 22.1.50.1 X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-stable@freebsd.org, hartzell@alerce.com Subject: Re: good/best practices for gmirror and gjournal on a pair of disks? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: hartzell@alerce.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2008 21:48:14 -0000 Adam McDougall writes: > George Hartzell wrote: > >[...] > > - I've read in the gjournal man page that when it is "... configured > > on top of gmirror(8) or graid3(8) providers, it also keeps them in > > a consistent state..." I've been trying to figure out if this > > simply falls out of how gjournal works or if there's explicity > > collusion with gmirror/graid3 but can't come up with a > > satisfactory explanation. Can someone walk me through it? > > > > Since I'm only gjournal'ing a portion of the underlying gmirror > > device I assume that I don't get this benefit? > >[...] > [...] > I decided to journal /usr /var /tmp and leave / as a standard UFS > partition because it is so small, fsck doesn't take long anyway and > hopefully doesn't get written to enough to cause damage by an abrupt > reboot. Because I'm not journaling the root partition, I chose to > ignore the possibility of gjournal marking the mirror clean. Sudden > reboots don't happen enough on servers for me to care. And all my > servers got abruptly rebooted this sunday and they all came up fine :) > [...] So you're confirming my belief that setting up gjournal on a bsdlabel'ed partition of a gmirror does *not* provide the consistency guarantee and that I should leave autosynchronization enabled. Right? g. From owner-freebsd-stable@FreeBSD.ORG Tue May 13 23:29:54 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 412361065674 for ; Tue, 13 May 2008 23:29:54 +0000 (UTC) (envelope-from cjd.wong@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.225]) by mx1.freebsd.org (Postfix) with ESMTP id 175598FC0C for ; Tue, 13 May 2008 23:29:53 +0000 (UTC) (envelope-from cjd.wong@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so4555979rvf.43 for ; Tue, 13 May 2008 16:29:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; bh=Fr9r0xk/YhM7FPCHi72hZ0Y3D4duT/67mHE2r9CybYc=; b=OuZFdPjW18sw6DbLgicfQWoaLez90L+3LaXtbWLg8TSq8P5xG/bEd1B2vQTe2y5aBi+9jElBxwF/1RWmnwHEP8ap7SPzOmHXumzH/q0wu0rtC43YgVhRdi6RewwgAXghGc2JTvtY3/m7WHR8ZH2n5qTaDRtKIc49YkdnEqBqxJg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=pgUZxebl/O1aWtytutc9OAV1/j1K/Jx5ihXUq1yvOxv6zYP+e5N5vj2N52FEe4Fx7pb5qW7NMsX6M6+fU9AJeTZBtoTSZs2irRQl4zJQmIVK7D0j18to8bg5QMxEQcTh3j9D6wRxS+fj2zoaGsnlwogVS892irkBYVYhpCe/NN8= Received: by 10.141.1.2 with SMTP id d2mr131244rvi.129.1210719865334; Tue, 13 May 2008 16:04:25 -0700 (PDT) Received: by 10.141.123.2 with HTTP; Tue, 13 May 2008 16:04:25 -0700 (PDT) Message-ID: <5a054730805131604l73ae3623se6d5ad28eb5e40c1@mail.gmail.com> Date: Tue, 13 May 2008 18:04:25 -0500 From: "Christian J. Wong Cruz" To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: problems with ia64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2008 23:29:54 -0000 Hello, I'm trying to download the ia64 distribution CDs from ftp://ftp.freebsd.org/pub/FreeBSD/releases/ia64/ISO-IMAGES/7.0/ and the list is [FILE] 7.0-RELEASE-ia64-bootonly.iso. . Feb 25 18:10 62M [VIEW] [DOWNLOAD] [FILE] 7.0-RELEASE-ia64-disc1.iso . . . Feb 25 18:11 429M [VIEW] [DOWNLOAD] [FILE] 7.0-RELEASE-ia64-disc2.iso . . . Feb 25 18:11 364K [VIEW] [DOWNLOAD] [FILE] 7.0-RELEASE-ia64-disc3.iso . . . Feb 25 18:11 364K [VIEW] [DOWNLOAD] [FILE] 7.0-RELEASE-ia64-docs.iso. . . . Feb 25 18:11 238M [VIEW] [DOWNLOAD] [FILE] 7.0-RELEASE-ia64-livefs.iso. . . Feb 25 18:12 371M [VIEW] [DOWNLOAD] [FILE] CHECKSUM.MD5 . . . . . . . . . . Feb 25 18:10 411 [VIEW] [DOWNLOAD] [FILE] CHECKSUM.SHA256. . . . . . . . . Feb 25 18:10 621 [VIEW] [DOWNLOAD] if you look at the disc 2 and 3, the size is 364K is it ok?. I'd like to install freebsd in a intel core 2 duo. Should I instal this ia64? Thanks for your help. From owner-freebsd-stable@FreeBSD.ORG Tue May 13 23:47:50 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9011E106566C; Tue, 13 May 2008 23:47:50 +0000 (UTC) (envelope-from msaad@datapipe.com) Received: from exchfe01.datapipe-corp.net (exchfe01.datapipe-corp.net [64.106.130.69]) by mx1.freebsd.org (Postfix) with ESMTP id 59B588FC0A; Tue, 13 May 2008 23:47:50 +0000 (UTC) (envelope-from msaad@datapipe.com) Received: from divide.lan (192.168.128.20) by exchfe01.datapipe-corp.net (64.106.130.71) with Microsoft SMTP Server id 8.0.783.2; Tue, 13 May 2008 19:37:37 -0400 Message-ID: <482A2639.7000401@datapipe.com> Date: Tue, 13 May 2008 19:37:29 -0400 From: Mark Saad User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: "freebsd-stable@freebsd.org" , Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: : Re: Socket leak (Was: Re: What triggers "No BufferSpace), ?Available" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: msaad@datapipe.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2008 23:47:50 -0000 Hello All This issue goes back some time, but I do not see a solution. Sorry about the cross post not sure where this belongs. Here is an overview of my issue which is similar and I hope someone can point me in the direction of a solution. I have experiencing an odd socket related issue on a few servers i manage. They are fairly large ftp servers for popular north american news agency. They handle 1000's of ftp transactions per hour. Currently they are running FreeBSD 6.3-Release-p1 . I have verified this happened on FreeBSD 6.1-Release 6.1-Stable 6.2-Release 6.2-Stable and 7.0-Release all 32bit installs and in both SMP an UP kernels. Oddly this issue did not happen on FreeBSD 4.x . I have a similar setup that has a 1400+ Day uptime running FreeBSD 4.x-Release. The issue is after 7 to 14 days the servers lock up and will not create any new tcp sockets. The system used proftp with mysql for authentication of the ftp accounts. The system is also running Apache 2.2.x , Postfix, Cyrus, clam-av, Diablo JDK 1.5 for Resin Appserver and daemontools . The only sysctls that seem to help are kern.ipc.maxsockets and kern.maxusers . Currently they are set to 65535 and 1024 . Changing kern.ipc.maxsockbuf did not have any effect I tried bumping this up to 2Meg, In any case I started work on logging everything we could think of to see what was happening. I started logging the values of kern.ipc.numopensockets and I noticed that something is leaking sockets. Here is a sample of the log 2008-04-29--15:04.10 ____ kern.ipc.numopensockets: 1501 2008-04-29--16:04.01 ____ kern.ipc.numopensockets: 1535 2008-04-29--17:04.00 ____ kern.ipc.numopensockets: 1617 2008-04-29--18:04.00 ____ kern.ipc.numopensockets: 1710 This continues until kern.ipc.maxsockets its reached or the box is rebooted. The other thing we looked at was the output from vmstat -z The first thing was the high amount of malloc 128 bucket failures 128 Bucket: 524, 0, 2489, 80, 8364, 23055239 I also logged the mbuf clusters, we never reached the max mbuf clusters Its almost like there are stale sockets. Here is a snapshot of the server now ewr# sockstat -4u |wc -l 139 ewr# sysctl kern.ipc.numopensockets kern.ipc.numopensockets: 13935 ewr# uptime 7:30PM up 6 days, 26 mins, 3 users, load averages: 0.18, 0.25, 0.17 My questions. 1. If I can not identify who / what is consuming all my tcp sockets what will happen if I double or triple the value of kern.ipc.maxsockets ? 2. Could this be an issue with a low kern.maxusers . Its currently set to 1024 . Also at times when I can not create a new socket I am not pinned on mbuf clusters . I was able to verify this in the past. 3. I installed a debugging kernel, which I built on the server. I was able to get a coredump of the server at the point in time we last had an issue. But I am not sure what I can do with this, kernel debugging is way beyond what I am capable of doing . Do I want to even pursue this ? 4. Does anyone have any system tunings you could recommend for a high volume ftp site ? What does ftp.freebsd.org have ? -- Mark Saad msaad@datapipe.com From owner-freebsd-stable@FreeBSD.ORG Tue May 13 23:48:26 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 077AF1065674; Tue, 13 May 2008 23:48:26 +0000 (UTC) (envelope-from msaad@datapipe.com) Received: from exchfe01.datapipe-corp.net (exchfe01.datapipe-corp.net [64.106.130.69]) by mx1.freebsd.org (Postfix) with ESMTP id C50EC8FC16; Tue, 13 May 2008 23:48:25 +0000 (UTC) (envelope-from msaad@datapipe.com) Received: from divide.lan (192.168.128.20) by exchfe01.datapipe-corp.net (64.106.130.71) with Microsoft SMTP Server id 8.0.783.2; Tue, 13 May 2008 19:38:16 -0400 Message-ID: <482A2668.8070209@datapipe.com> Date: Tue, 13 May 2008 19:38:16 -0400 From: Mark Saad User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: "freebsd-stable@freebsd.org" , Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: : Re: Socket leak (Was: Re: What triggers "No BufferSpace), ?Available" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: msaad@datapipe.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2008 23:48:26 -0000 Hello All This issue goes back some time, but I do not see a solution. Sorry about the cross post not sure where this belongs. Here is an overview of my issue which is similar and I hope someone can point me in the direction of a solution. I have experiencing an odd socket related issue on a few servers i manage. They are fairly large ftp servers for popular north american news agency. They handle 1000's of ftp transactions per hour. Currently they are running FreeBSD 6.3-Release-p1 . I have verified this happened on FreeBSD 6.1-Release 6.1-Stable 6.2-Release 6.2-Stable and 7.0-Release all 32bit installs and in both SMP an UP kernels. Oddly this issue did not happen on FreeBSD 4.x . I have a similar setup that has a 1400+ Day uptime running FreeBSD 4.x-Release. The issue is after 7 to 14 days the servers lock up and will not create any new tcp sockets. The system used proftp with mysql for authentication of the ftp accounts. The system is also running Apache 2.2.x , Postfix, Cyrus, clam-av, Diablo JDK 1.5 for Resin Appserver and daemontools . The only sysctls that seem to help are kern.ipc.maxsockets and kern.maxusers . Currently they are set to 65535 and 1024 . Changing kern.ipc.maxsockbuf did not have any effect I tried bumping this up to 2Meg, In any case I started work on logging everything we could think of to see what was happening. I started logging the values of kern.ipc.numopensockets and I noticed that something is leaking sockets. Here is a sample of the log 2008-04-29--15:04.10 ____ kern.ipc.numopensockets: 1501 2008-04-29--16:04.01 ____ kern.ipc.numopensockets: 1535 2008-04-29--17:04.00 ____ kern.ipc.numopensockets: 1617 2008-04-29--18:04.00 ____ kern.ipc.numopensockets: 1710 This continues until kern.ipc.maxsockets its reached or the box is rebooted. The other thing we looked at was the output from vmstat -z The first thing was the high amount of malloc 128 bucket failures 128 Bucket: 524, 0, 2489, 80, 8364, 23055239 I also logged the mbuf clusters, we never reached the max mbuf clusters Its almost like there are stale sockets. Here is a snapshot of the server now ewr# sockstat -4u |wc -l 139 ewr# sysctl kern.ipc.numopensockets kern.ipc.numopensockets: 13935 ewr# uptime 7:30PM up 6 days, 26 mins, 3 users, load averages: 0.18, 0.25, 0.17 My questions. 1. If I can not identify who / what is consuming all my tcp sockets what will happen if I double or triple the value of kern.ipc.maxsockets ? 2. Could this be an issue with a low kern.maxusers . Its currently set to 1024 . Also at times when I can not create a new socket I am not pinned on mbuf clusters . I was able to verify this in the past. 3. I installed a debugging kernel, which I built on the server. I was able to get a coredump of the server at the point in time we last had an issue. But I am not sure what I can do with this, kernel debugging is way beyond what I am capable of doing . Do I want to even pursue this ? 4. Does anyone have any system tunings you could recommend for a high volume ftp site ? What does ftp.freebsd.org have ? -- Mark Saad msaad@datapipe.com From owner-freebsd-stable@FreeBSD.ORG Wed May 14 00:17:43 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F0A331065677 for ; Wed, 14 May 2008 00:17:42 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.235]) by mx1.freebsd.org (Postfix) with ESMTP id B98308FC18 for ; Wed, 14 May 2008 00:17:42 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so4579188rvf.43 for ; Tue, 13 May 2008 17:17:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; bh=//9zk9/o+3ZpWPkf2G/8WFLsjS9ysoT8eoHACdK08ZI=; b=VZFibQh9SzeocUmaXoqTcCEcfFm5jmCtL+S1G4sYpVl6c2oRydEcH1oOgFrj36KPXFRNqCMMf2ltf+yKRq1N/bluXyjyGQP0Ej8SHAR4NvQ013yp7SiZctLZ48FfdZI0D41JQlgC/m6z4MkjRmz+bnQa9BrJ8EZDzmDYWUJO8mY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=A+C310A5esEVTbmwrzNg7rNIEfCjhqVaQh9klKPx3lJ6wEE4xOa8zdNtZz+VpvQGuaCPxDPrP/YKCWBj8xeaohDUFe4pc4LU9IpRPtkkx79j9iVobMK23tisdd3jnES2bP4zj5OtHtD8+M8UKoB/4tCpZBF96ECQyD7964FNLs0= Received: by 10.140.226.14 with SMTP id y14mr156206rvg.164.1210724262384; Tue, 13 May 2008 17:17:42 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id l31sm621624rvb.6.2008.05.13.17.17.39 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 13 May 2008 17:17:40 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id m4E0HZHf003768 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 14 May 2008 09:17:35 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id m4E0HYSN003767; Wed, 14 May 2008 09:17:34 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Wed, 14 May 2008 09:17:34 +0900 From: Pyun YongHyeon To: Ben Kaduk Message-ID: <20080514001734.GA3634@cdnetworks.co.kr> References: <47d0403c0805130922x62fc479cs47b8a03f41598e00@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <47d0403c0805130922x62fc479cs47b8a03f41598e00@mail.gmail.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: 7.0 issues fixed? upgrade timing? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 May 2008 00:17:43 -0000 On Tue, May 13, 2008 at 12:22:10PM -0400, Ben Kaduk wrote: > Hi all, > > I only just now subscribed, so my apologies if this has been covered > and my cursory search missed it. > > I am seeing a similar issue to the one described in the email below > (pasted from a web listing of this list). > > That is, my ssh connection will occasionally be dropped with the > message > Disconnecting: Bad packet length 3190815048. > (the number is not always the same). > > I can reliably reproduce this with `cat < /dev/urandom | od -c` > from a FreeBSD-current box (a few weeks old, actually, since > the build was broken when I last tried to update) as well > as from a mac running OS X 10.4 . > > The system that is killing my connections is: > FreeBSD periphrasis.mit.edu 7.0-STABLE FreeBSD 7.0-STABLE #3: Tue Mar > 25 14:53:51 EDT 2008 > kaduk@periphrasis.mit.edu:/usr/obj/usr/src/sys/PERIPHRASIS amd64 > > > Any thoughts would be appreciated. > There had been large changes to enhance re(4) stablility and many users reported positive results. But it still seems to have issues for certain models. See kern/123202, kern/123563. If you encounter issues on latest re(4), please try patch in kern/123563 and let me know how it goes. > -Ben Kaduk > > > > > > > > ------------------ random message from this thread, for some context > ------------- > > * From: Jeremy Chadwick > * Date: Mon, 12 May 2008 05:32:07 -0700 > > On Mon, May 12, 2008 at 01:44:22PM +0200, Torfinn Ingolfsen wrote: > > On Mon, 12 May 2008 11:37:53 +0200 > Torfinn Ingolfsen wrote: > > FWIW, I had major troubles with re(4) around 7.0-release, and a while > later (I had to use patches). After upgrading to 7-stable on > 2008-04-12, re(4) is working for me without patches. > > > (sigh).. it seems that I spoke to soon. Murphy just showed up. I still > get ssh disconnects (see below) on connections _to_ the machine when > transferring largish amounts of data (like when upgrading a port). > Here is one example (portupgrading the jdk port): > /usr/bin/gcc -fno-strict-aliasing -fPIC -W -Wall -Wno-unused > -Wno-parentheses -pipe -Damd64 -DARCH='"amd64"' > -DRELEASE='"1.6.0_03-p4"' > -DFULL_VERSION='"1.6.0_03-p4-root_12_may_2008_13_25-b00"' > -D_GNU_SOURCE -D_REENTRANT -D_THREAD_SAFE -D_ALLBSD_SOURCE -D_LP64=1 > -I. -I/usr/ports/java/jdk16/work/control/build/bsd-amd64/tmp/java/java.lang.management/management/CClassHeaders > -I../../../src/solaris/javavm/export > -I../../../src/share/javavm/export -I../../../src/share/javavm/include > -I../../../src/solaris/javavm/include > -I../../../src/share/native/sun/management > -I../../../src/solaris/hpi/include -I../../../src/share/native/common > -I../../../src/solaris/native/common > -I../../../src/share/native/java/lang/management > -I../../../src/solaris/native/java/lang/management -c -o > /usr/ports/java/jdk16/work/control/build/bsd-amd64/tmp/java/java.lang.management/management/obj64/ClassLoadingImpl.o > ../../../src/share/native/sun/management/ClassLoadingImpl.c > Disconnecting: Bad packet length 3601161525. > > The machine is running: > tingo@kg-vm$ uname -a > FreeBSD kg-vm.kg4.no 7.0-STABLE FreeBSD 7.0-STABLE #10: Sat Apr 12 > 21:42:55 CEST 2008 root@xxxxxxxxxxxx:/usr/obj/usr/src/sys/GENERIC > amd64 > > and has been up for about 14 days: > tingo@kg-vm$ uptime > 1:36PM up 14 days, 17:42, 7 users, load averages: 2.15, 1.85, 1.34 > > I see that if_re.c for RELENG_7 has been updated on April 22nd, so > I'll upgrade the machine to latest -stable and see if that works > better. > > > Is this machine using pf(4) at all? -- Regards, Pyun YongHyeon From owner-freebsd-stable@FreeBSD.ORG Wed May 14 00:18:59 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 918021065670 for ; Wed, 14 May 2008 00:18:59 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from mail-out4.apple.com (mail-out4.apple.com [17.254.13.23]) by mx1.freebsd.org (Postfix) with ESMTP id 788588FC13 for ; Wed, 14 May 2008 00:18:59 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from relay13.apple.com (relay13.apple.com [17.128.113.29]) by mail-out4.apple.com (Postfix) with ESMTP id 3A1E02CD397D; Tue, 13 May 2008 17:18:59 -0700 (PDT) Received: from relay13.apple.com (unknown [127.0.0.1]) by relay13.apple.com (Symantec Mail Security) with ESMTP id 208C328085; Tue, 13 May 2008 17:18:59 -0700 (PDT) X-AuditID: 1180711d-a9b93bb000000ed7-ff-482a2ff22436 Received: from cswiger1.apple.com (cswiger1.apple.com [17.214.13.96]) by relay13.apple.com (Apple SCV relay) with ESMTP id 009A428050; Tue, 13 May 2008 17:18:59 -0700 (PDT) Message-Id: From: Chuck Swiger To: Christian J. Wong Cruz In-Reply-To: <5a054730805131604l73ae3623se6d5ad28eb5e40c1@mail.gmail.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v919.2) Date: Tue, 13 May 2008 17:18:58 -0700 References: <5a054730805131604l73ae3623se6d5ad28eb5e40c1@mail.gmail.com> X-Mailer: Apple Mail (2.919.2) X-Brightmail-Tracker: AAAAAA== Cc: freebsd-stable@freebsd.org Subject: Re: problems with ia64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 May 2008 00:18:59 -0000 On May 13, 2008, at 4:04 PM, Christian J. Wong Cruz wrote: > Hello, I'm trying to download the ia64 distribution CDs from > ftp://ftp.freebsd.org/pub/FreeBSD/releases/ia64/ISO-IMAGES/7.0/ and > the list > is > [ ... ] > if you look at the disc 2 and 3, the size is 364K is it ok?. I'd > like to > install freebsd in a intel core 2 duo. Should I instal this ia64? Why, no. ia64 is for the Itanium processor line which uses a different architecture and is not compatible with the standard x86 32- bit or 64-bit platforms. What you want instead is the amd64 platform, which is known as "EM64T" for the Intel Xeon/P4/Core/Core2 chips: http://www.FreeBSD.org/releases/7.0R/hardware.html#PROC-AMD64 ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/amd64/ISO-IMAGES/7.0/ Regards, -- -Chuck From owner-freebsd-stable@FreeBSD.ORG Wed May 14 00:37:03 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AF8E31065670 for ; Wed, 14 May 2008 00:37:03 +0000 (UTC) (envelope-from mcdouga9@egr.msu.edu) Received: from mx.egr.msu.edu (surfnturf.egr.msu.edu [35.9.37.164]) by mx1.freebsd.org (Postfix) with ESMTP id 84B568FC0A for ; Wed, 14 May 2008 00:37:03 +0000 (UTC) (envelope-from mcdouga9@egr.msu.edu) Received: from localhost (localhost [127.0.0.1]) by mx.egr.msu.edu (Postfix) with ESMTP id 0B5F271F12D; Tue, 13 May 2008 20:37:03 -0400 (EDT) X-Virus-Scanned: amavisd-new at egr.msu.edu Received: from mx.egr.msu.edu ([127.0.0.1]) by localhost (surfnturf.egr.msu.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zht3A92NdNC3; Tue, 13 May 2008 20:37:02 -0400 (EDT) Received: from [35.9.40.72] (eb2314p12.egr.msu.edu [35.9.40.72]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: mcdouga9) by mx.egr.msu.edu (Postfix) with ESMTPSA id C60BF71F121; Tue, 13 May 2008 20:37:02 -0400 (EDT) Message-ID: <482A342B.1020606@egr.msu.edu> Date: Tue, 13 May 2008 20:36:59 -0400 From: mcdouga9 User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: hartzell@alerce.com References: <18473.48984.31132.91673@almost.alerce.com> <4829FBC8.5040101@egr.msu.edu> <18474.3218.145536.664367@almost.alerce.com> In-Reply-To: <18474.3218.145536.664367@almost.alerce.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: good/best practices for gmirror and gjournal on a pair of disks? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 May 2008 00:37:03 -0000 George Hartzell wrote: > Adam McDougall writes: > > George Hartzell wrote: > > >[...] > > > - I've read in the gjournal man page that when it is "... configured > > > on top of gmirror(8) or graid3(8) providers, it also keeps them in > > > a consistent state..." I've been trying to figure out if this > > > simply falls out of how gjournal works or if there's explicity > > > collusion with gmirror/graid3 but can't come up with a > > > satisfactory explanation. Can someone walk me through it? > > > > > > Since I'm only gjournal'ing a portion of the underlying gmirror > > > device I assume that I don't get this benefit? > > >[...] > > [...] > > I decided to journal /usr /var /tmp and leave / as a standard UFS > > partition because it is so small, fsck doesn't take long anyway and > > hopefully doesn't get written to enough to cause damage by an abrupt > > reboot. Because I'm not journaling the root partition, I chose to > > ignore the possibility of gjournal marking the mirror clean. Sudden > > reboots don't happen enough on servers for me to care. And all my > > servers got abruptly rebooted this sunday and they all came up fine :) > > [...] > > So you're confirming my belief that setting up gjournal on a > bsdlabel'ed partition of a gmirror does *not* provide the consistency > guarantee and that I should leave autosynchronization enabled. Right? > > g. > I forgot to address that. I think to gain that, you have to (re)label the mirror using -F (see man gmirror). I believe without using -F, the mirrors will still be synced (but probably don't need to). Otherwise, look for initial mail list announcements (freebsd-current?) of gjournal which may explain. From owner-freebsd-stable@FreeBSD.ORG Wed May 14 05:12:30 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 82B2E106566C for ; Wed, 14 May 2008 05:12:30 +0000 (UTC) (envelope-from minimarmot@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.28]) by mx1.freebsd.org (Postfix) with ESMTP id 3C9698FC1B for ; Wed, 14 May 2008 05:12:30 +0000 (UTC) (envelope-from minimarmot@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so1732396ywe.13 for ; Tue, 13 May 2008 22:12:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=ZzzcyosteYnHYD+33vtksyZrz0Yu9wk6YnFyZF7BiMM=; b=xUyej2T6P95PRI8IHWaWekgzkVdlkQo4gw38qFoUAR6+bc9v9vu+romwfngLod43VGyerzLRLXPCtJo/+lvQi+T10kMdr7RHjI1SxxJ2ImkPmiMsDXH4jfeuJoWz4wDdSlR6yo6rbdVLJ6Zql3WYuRQC+3zNW/NY7QkUhiTRm6g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=S03ms8xdCTFfavNnCaqG782eSycdlb6rvYEao5+tr1gU/oEmOno35GfcqGVrKHuQnOPCQ02fs+wg8mJ5mdrxUfMIYon7c4TXB9ap9BQdO5ZDQzhlZbkBDf6jB/RglcZBBefOfLdpTfbw90JlGyFewE7fJBxI7UkdvOqtF1VEu5w= Received: by 10.150.73.41 with SMTP id v41mr612024yba.183.1210741949575; Tue, 13 May 2008 22:12:29 -0700 (PDT) Received: by 10.151.60.8 with HTTP; Tue, 13 May 2008 22:12:29 -0700 (PDT) Message-ID: <47d0403c0805132212i72c63776t1bca3d2e77be4bf3@mail.gmail.com> Date: Wed, 14 May 2008 01:12:29 -0400 From: "Ben Kaduk" To: pyunyh@gmail.com In-Reply-To: <20080514001734.GA3634@cdnetworks.co.kr> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <47d0403c0805130922x62fc479cs47b8a03f41598e00@mail.gmail.com> <20080514001734.GA3634@cdnetworks.co.kr> Cc: freebsd-stable@freebsd.org Subject: Re: 7.0 issues fixed? upgrade timing? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 May 2008 05:12:30 -0000 On 5/13/08, Pyun YongHyeon wrote: > > > There had been large changes to enhance re(4) stablility and many > users reported positive results. But it still seems to have issues > for certain models. See kern/123202, kern/123563. > If you encounter issues on latest re(4), please try patch in > kern/123563 and let me know how it goes. > > > > -Ben Kaduk > > Pyun, Thanks for the reminder -- I saw the changes go in, but forgot that this box was using re(4). Attempting to csup while running the March 25 driver made me sad, but a kernel.old from February worked well. I'm now running with if_re.c v 1.95.2.18 and I'm not seeing any packet loss or terminated ssh sessions. Thanks for all the good work! -Ben Kaduk From owner-freebsd-stable@FreeBSD.ORG Wed May 14 05:36:48 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 918F0106567C for ; Wed, 14 May 2008 05:36:48 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from gaia.nimnet.asn.au (nimbin.lnk.telstra.net [139.130.45.143]) by mx1.freebsd.org (Postfix) with ESMTP id 09A3E8FC34 for ; Wed, 14 May 2008 05:36:46 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from localhost (smithi@localhost) by gaia.nimnet.asn.au (8.8.8/8.8.8R1.5) with SMTP id PAA29663; Wed, 14 May 2008 15:36:35 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Wed, 14 May 2008 15:36:34 +1000 (EST) From: Ian Smith To: "Alexandre \"Sunny\" Kovalenko" In-Reply-To: <1210699165.2238.1.camel@RabbitsDen> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: bruce@cran.org.uk, stable@freebsd.org, jonathan@kc8onw.net Subject: Re: ATA APM and NCQ support in FreeBSD atacontrol X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 May 2008 05:36:48 -0000 On Tue, 13 May 2008, Alexandre "Sunny" Kovalenko wrote: > On Mon, 2008-05-12 at 14:52 +1000, Ian Smith wrote: > > On Sun, 11 May 2008 jonathan@kc8onw.net wrote: > > > Has any work been done recently towards adding SATA Native Command > > > Queueing as well as ATA APM and acoustic management to FreeBSD? > > > > > > I found this PR (with patch) to add APM and acoustic management control to > > > atacontrol. The PR was opened in May 2005 has not been changed since > > > December 2006 and is still open. > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=81692&cat= > > > > > > I have not been able to find much of anything on SATA NCQ in FreeBSD newer > > > than 2005 or 2006 does anyone know anything newer? > > > > Jeremy has addressed the NCQ issue, about which I know nothing. > > > > As for APM and AAM, that functionality is handled by sysutils/ataidle, > > which that PR appears - on a quick glance - to pretty well duplicate. > > > > I see phk@ recently added an 'atacontrol spindown' command to HEAD and > > RELENG_7 that appears to offer similar functionality to 'ataidle -S > > standby_mins' or 'ataidle -I idle_mins', though specified in seconds > > instead. However this doesn't address acoustic management. > > > > Or is ataidle broken for SATA disks? > Does not look broken here (RELENG_7): > > RabbitsDen# ataidle /dev/ad4 > Device Info: > > Model: HTS541010G9SA00 > Serial: MP2ZM4X0JWY6WH > Firmware Rev: MBZIC60H > ATA revision: ATA-7 > LBA 48: yes > Geometry: 16383 cyls, 16 heads, 63 spt > Capacity: 93GB > SMART Supported: yes > SMART Enabled: yes > APM Supported: yes > APM Enabled: yes > AAM Supported: yes > AAM Enabled: yes > Current AAM: 1 > Vendor Recommends AAM: 1 > APM Value: 16638 Thanks for the confirmation Alexandre. I take Jonathan's point that it would be nice to have this functionality in atacontrol, though perhaps the BUGS section in ataidle(8) precludes merging that? cc'ing Bruce Cran in case he wants to add something .. > RabbitsDen# atacontrol list [..] > ATA channel 2: > Master: ad4 Serial ATA v1.0 > Slave: no device present Regarding the spindown thing, I always used to use APM (set in BIOS) to do that on this old laptop, until I found that I'd already consumed 25% of a new 40GB drive's 2 million Load_Cycle_Count in a year, following a thread warning about that last year, so now I run ataidle from rc.conf: ataidle_enable="YES" ataidle_device="ad0" ataidle_ad0="-P 0 0 0" but then found it necessary to again disable disk APM in rc.resume: /usr/local/sbin/ataidle -P 0 0 0 cheers, Ian From owner-freebsd-stable@FreeBSD.ORG Wed May 14 06:37:54 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 663311065678 for ; Wed, 14 May 2008 06:37:54 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.bluestop.org (unknown [IPv6:2001:41c8:1:548a::2]) by mx1.freebsd.org (Postfix) with ESMTP id 0B3158FC2A for ; Wed, 14 May 2008 06:37:54 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from tau.draftnet (unknown [IPv6:2a01:348:10f:0:219:b9ff:fe54:f04a]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTP id 61DD9301B5; Wed, 14 May 2008 07:37:52 +0100 (BST) Message-ID: <482A88A5.4060108@cran.org.uk> Date: Wed, 14 May 2008 07:37:25 +0100 From: Bruce Cran User-Agent: Thunderbird 2.0.0.14 (X11/20080505) MIME-Version: 1.0 To: Ian Smith References: In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org, "Alexandre \"Sunny\" Kovalenko" , jonathan@kc8onw.net Subject: Re: ATA APM and NCQ support in FreeBSD atacontrol X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 May 2008 06:37:54 -0000 Ian Smith wrote: > I take Jonathan's point that it would be nice to have this functionality > in atacontrol, though perhaps the BUGS section in ataidle(8) precludes > merging that? cc'ing Bruce Cran in case he wants to add something .. ataidle is at the moment quite dumb about sending commands: it doesn't check that the drive actually supports APM/AAM before sending the commands, and that's an easy check to do. If this was being added to atacontrol I think I'd want to do quite a bit of work first to make it more robust. However I don't think the code from ataidle could ever just be merged in to atacontrol because the code styles are quite different; however since the interface to the ATA driver is quite straightforward it should be trivial to re-implement or copy the bits needed. -- Bruce From owner-freebsd-stable@FreeBSD.ORG Wed May 14 08:15:19 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8307F1065672 for ; Wed, 14 May 2008 08:15:19 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id AC8938FC0C; Wed, 14 May 2008 08:15:18 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <482A9F99.4040500@FreeBSD.org> Date: Wed, 14 May 2008 10:15:21 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: d@delphij.net References: <7A0780B6-AD8E-440B-BFDB-EC2C4ACA1A70@altus-escon.com> <4829F1B8.1000707@delphij.net> In-Reply-To: <4829F1B8.1000707@delphij.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org, Ben Stuyts Subject: Re: Panic after hung rsync, probably zfs related X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 May 2008 08:15:19 -0000 Xin LI wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Ben Stuyts wrote: > | Hi, > | > | While doing an rsync from a zfs filesystem to an external usb hd (also > | zfs), the rsync processes hung in zfs state. I could not kill these > | processes, although the rest of the server seemingly continued to run > | fine. The reboot command did not work. Next I tried a shutdown now > | command. This caused a panic: > > Sound like you somehow run out of memory, there is an known issue with > ZFS which causes livelock when there is memory pressure. Which rsync > version are you using? With rsync 3.x the memory usage would drop > drastically which would help to prevent this from happening. This isn't known to cause a double fault though. Unfortunately we probably need more information than was available in order to proceed. Kris From owner-freebsd-stable@FreeBSD.ORG Wed May 14 08:40:58 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C3A17106564A for ; Wed, 14 May 2008 08:40:58 +0000 (UTC) (envelope-from ben@altus-escon.com) Received: from altus-escon.com (altesco.xs4all.nl [82.95.106.39]) by mx1.freebsd.org (Postfix) with ESMTP id 51ED68FC1F for ; Wed, 14 May 2008 08:40:58 +0000 (UTC) (envelope-from ben@altus-escon.com) Received: from giskard.stuyts.nl (stuyts.xs4all.nl [82.95.106.42]) by altus-escon.com (8.14.2/8.14.2) with ESMTP id m4E8eawG016962; Wed, 14 May 2008 10:40:41 +0200 (CEST) (envelope-from ben@altus-escon.com) Message-Id: <11D2E346-752B-4F61-979E-1D64FB34ED34@altus-escon.com> From: Ben Stuyts To: d@delphij.net In-Reply-To: <4829F1B8.1000707@delphij.net> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v919.2) Date: Wed, 14 May 2008 10:39:36 +0200 References: <7A0780B6-AD8E-440B-BFDB-EC2C4ACA1A70@altus-escon.com> <4829F1B8.1000707@delphij.net> X-Mailer: Apple Mail (2.919.2) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (altus-escon.com [10.0.0.150]); Wed, 14 May 2008 10:40:41 +0200 (CEST) X-Virus-Scanned: ClamAV 0.93/6809/Thu Apr 17 11:33:01 2008 on mars.altus-escon.com X-Virus-Status: Clean X-Spam-Status: No, score=-2.2 required=3.5 tests=AWL,BAYES_00 autolearn=ham version=3.2.4 X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on mars.altus-escon.com Cc: stable@freebsd.org Subject: Re: Panic after hung rsync, probably zfs related X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 May 2008 08:40:58 -0000 On 13 mei 2008, at 21:53, Xin LI wrote: > | While doing an rsync from a zfs filesystem to an external usb hd > (also > | zfs), the rsync processes hung in zfs state. I could not kill these > | processes, although the rest of the server seemingly continued to > run > | fine. The reboot command did not work. Next I tried a shutdown now > | command. This caused a panic: > > Sound like you somehow run out of memory, there is an known issue with > ZFS which causes livelock when there is memory pressure. Which rsync > version are you using? With rsync 3.x the memory usage would drop > drastically which would help to prevent this from happening. I'm running rsync 3.0.0. Two weeks ago I already increased the memory in this machine from 4 to 8 GB, but I did not change any loader.conf variables. BTW, The wired memory goes all over the place in this machine: even when it's mostly idle it varies between 300 MB and 3.5 GB. That's why I added 4 more GB. Ben From owner-freebsd-stable@FreeBSD.ORG Wed May 14 08:50:56 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EABE31065679 for ; Wed, 14 May 2008 08:50:56 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from relay03.kiev.sovam.com (relay03.kiev.sovam.com [62.64.120.201]) by mx1.freebsd.org (Postfix) with ESMTP id 8A9768FC20 for ; Wed, 14 May 2008 08:50:56 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from [212.82.216.226] (helo=skuns.kiev.zoral.com.ua) by relay03.kiev.sovam.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1JwChK-000OTi-Ho for stable@freebsd.org; Wed, 14 May 2008 11:50:54 +0300 Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by skuns.kiev.zoral.com.ua (8.14.2/8.14.2) with ESMTP id m4E8oRAU016128 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 14 May 2008 11:50:28 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.2/8.14.2) with ESMTP id m4E8oPPb042309; Wed, 14 May 2008 11:50:25 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.2/8.14.2/Submit) id m4E8oPNd042308; Wed, 14 May 2008 11:50:25 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 14 May 2008 11:50:25 +0300 From: Kostik Belousov To: Ben Stuyts Message-ID: <20080514085025.GL18958@deviant.kiev.zoral.com.ua> References: <7A0780B6-AD8E-440B-BFDB-EC2C4ACA1A70@altus-escon.com> <4829F1B8.1000707@delphij.net> <11D2E346-752B-4F61-979E-1D64FB34ED34@altus-escon.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="QIAmslimH5K9Znqb" Content-Disposition: inline In-Reply-To: <11D2E346-752B-4F61-979E-1D64FB34ED34@altus-escon.com> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: ClamAV version 0.91.2, clamav-milter version 0.91.2 on skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.4 X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on skuns.kiev.zoral.com.ua X-Scanner-Signature: 4fe2b897d4d72954524b6b73d18f8617 X-DrWeb-checked: yes X-SpamTest-Envelope-From: kostikbel@gmail.com X-SpamTest-Group-ID: 00000000 X-SpamTest-Header: Not Detected X-SpamTest-Info: Profiles 2810 [May 13 2008] X-SpamTest-Info: helo_type=3 X-SpamTest-Method: none X-SpamTest-Rate: 0 X-SpamTest-Status: Not detected X-SpamTest-Status-Extended: not_detected X-SpamTest-Version: SMTP-Filter Version 3.0.0 [0278], KAS30/Release Cc: stable@freebsd.org, d@delphij.net Subject: Re: Panic after hung rsync, probably zfs related X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 May 2008 08:50:57 -0000 --QIAmslimH5K9Znqb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, May 14, 2008 at 10:39:36AM +0200, Ben Stuyts wrote: >=20 > On 13 mei 2008, at 21:53, Xin LI wrote: >=20 > >| While doing an rsync from a zfs filesystem to an external usb hd =20 > >(also > >| zfs), the rsync processes hung in zfs state. I could not kill these > >| processes, although the rest of the server seemingly continued to =20 > >run > >| fine. The reboot command did not work. Next I tried a shutdown now > >| command. This caused a panic: > > > >Sound like you somehow run out of memory, there is an known issue with > >ZFS which causes livelock when there is memory pressure. Which rsync > >version are you using? With rsync 3.x the memory usage would drop > >drastically which would help to prevent this from happening. >=20 > I'm running rsync 3.0.0. Two weeks ago I already increased the memory =20 > in this machine from 4 to 8 GB, but I did not change any loader.conf =20 > variables. >=20 > BTW, The wired memory goes all over the place in this machine: even =20 > when it's mostly idle it varies between 300 MB and 3.5 GB. That's why =20 > I added 4 more GB. 3.5Gb wired ? Do you run amd64 ? Does wired memory drops lower after you change the load ? --QIAmslimH5K9Znqb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkgqp9AACgkQC3+MBN1Mb4jlrgCffex2lnSLoSUMWgZdvRoF2vqK o18AoMiofyVjN8ZXGu1c+UeoQsL0ZHXE =hbGB -----END PGP SIGNATURE----- --QIAmslimH5K9Znqb-- From owner-freebsd-stable@FreeBSD.ORG Wed May 14 10:15:09 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 902E0106571E for ; Wed, 14 May 2008 10:15:09 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 49F308FC18 for ; Wed, 14 May 2008 10:15:08 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1JwE0p-0008HC-7O for freebsd-stable@freebsd.org; Wed, 14 May 2008 10:15:07 +0000 Received: from sub87-230-112-4.he-dsl.de ([87.230.112.4]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 14 May 2008 10:15:07 +0000 Received: from christian.baer by sub87-230-112-4.he-dsl.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 14 May 2008 10:15:07 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Christian Baer Date: Wed, 14 May 2008 12:14:28 +0200 Organization: Convenimus Projekt Lines: 13 Message-ID: References: <7A0780B6-AD8E-440B-BFDB-EC2C4ACA1A70@altus-escon.com> <4829F1B8.1000707@delphij.net> <11D2E346-752B-4F61-979E-1D64FB34ED34@altus-escon.com> <20080514085025.GL18958@deviant.kiev.zoral.com.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: sub87-230-112-4.he-dsl.de User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.1.14) Gecko/20080421 Thunderbird/2.0.0.14 Mnenhy/0.7.5.0 In-Reply-To: <20080514085025.GL18958@deviant.kiev.zoral.com.ua> Sender: news Subject: Re: Panic after hung rsync, probably zfs related X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 May 2008 10:15:09 -0000 Kostik Belousov wrote: >> BTW, The wired memory goes all over the place in this machine: even >> when it's mostly idle it varies between 300 MB and 3.5 GB. That's why >> I added 4 more GB. > 3.5Gb wired ? Do you run amd64 ? > Does wired memory drops lower after you change the load ? Either that or some other 64bit Plattform (alpha, sparc64 etc.). Regards Chris From owner-freebsd-stable@FreeBSD.ORG Wed May 14 11:48:57 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A0CC0106564A for ; Wed, 14 May 2008 11:48:57 +0000 (UTC) (envelope-from ben@altus-escon.com) Received: from altus-escon.com (altesco.xs4all.nl [82.95.106.39]) by mx1.freebsd.org (Postfix) with ESMTP id 2CF228FC2F for ; Wed, 14 May 2008 11:48:56 +0000 (UTC) (envelope-from ben@altus-escon.com) Received: from giskard.altus-escon.com (giskard.altus-escon.com [193.78.231.1]) by altus-escon.com (8.14.2/8.14.2) with ESMTP id m4EBmeNV022583; Wed, 14 May 2008 13:48:45 +0200 (CEST) (envelope-from ben@altus-escon.com) Message-Id: From: Ben Stuyts To: Kostik Belousov In-Reply-To: <20080514085025.GL18958@deviant.kiev.zoral.com.ua> Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v919.2) Date: Wed, 14 May 2008 13:47:46 +0200 References: <7A0780B6-AD8E-440B-BFDB-EC2C4ACA1A70@altus-escon.com> <4829F1B8.1000707@delphij.net> <11D2E346-752B-4F61-979E-1D64FB34ED34@altus-escon.com> <20080514085025.GL18958@deviant.kiev.zoral.com.ua> X-Mailer: Apple Mail (2.919.2) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (altus-escon.com [193.78.231.142]); Wed, 14 May 2008 13:48:45 +0200 (CEST) X-Virus-Scanned: ClamAV 0.93/6809/Thu Apr 17 11:33:01 2008 on mars.altus-escon.com X-Virus-Status: Clean X-Spam-Status: No, score=-2.3 required=3.5 tests=AWL,BAYES_00 autolearn=ham version=3.2.4 X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on mars.altus-escon.com Cc: stable@freebsd.org, d@delphij.net Subject: Re: Panic after hung rsync, probably zfs related X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 May 2008 11:48:57 -0000 On 14 mei 2008, at 10:50, Kostik Belousov wrote: >> BTW, The wired memory goes all over the place in this machine: even >> when it's mostly idle it varies between 300 MB and 3.5 GB. That's why >> I added 4 more GB. > 3.5Gb wired ? Do you run amd64 ? > > Does wired memory drops lower after you change the load ? Yes, it was in my original message. Ben From owner-freebsd-stable@FreeBSD.ORG Wed May 14 11:49:54 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 295C7106568D for ; Wed, 14 May 2008 11:49:54 +0000 (UTC) (envelope-from ben@altus-escon.com) Received: from altus-escon.com (altesco.xs4all.nl [82.95.106.39]) by mx1.freebsd.org (Postfix) with ESMTP id A94F18FC16 for ; Wed, 14 May 2008 11:49:53 +0000 (UTC) (envelope-from ben@altus-escon.com) Received: from giskard.altus-escon.com (giskard.altus-escon.com [193.78.231.1]) by altus-escon.com (8.14.2/8.14.2) with ESMTP id m4EBmeNW022583; Wed, 14 May 2008 13:49:43 +0200 (CEST) (envelope-from ben@altus-escon.com) Message-Id: <6E930383-27FE-470A-96D8-3E61DD21B2BC@altus-escon.com> From: Ben Stuyts To: Kris Kennaway In-Reply-To: <482A9F99.4040500@FreeBSD.org> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v919.2) Date: Wed, 14 May 2008 13:48:49 +0200 References: <7A0780B6-AD8E-440B-BFDB-EC2C4ACA1A70@altus-escon.com> <4829F1B8.1000707@delphij.net> <482A9F99.4040500@FreeBSD.org> X-Mailer: Apple Mail (2.919.2) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (altus-escon.com [193.78.231.142]); Wed, 14 May 2008 13:49:43 +0200 (CEST) X-Virus-Scanned: ClamAV 0.93/6809/Thu Apr 17 11:33:01 2008 on mars.altus-escon.com X-Virus-Status: Clean X-Spam-Status: No, score=-2.3 required=3.5 tests=AWL,BAYES_00 autolearn=ham version=3.2.4 X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on mars.altus-escon.com Cc: stable@freebsd.org, d@delphij.net Subject: Re: Panic after hung rsync, probably zfs related X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 May 2008 11:49:54 -0000 On 14 mei 2008, at 10:15, Kris Kennaway wrote: >> | While doing an rsync from a zfs filesystem to an external usb hd >> (also >> | zfs), the rsync processes hung in zfs state. I could not kill these >> | processes, although the rest of the server seemingly continued to >> run >> | fine. The reboot command did not work. Next I tried a shutdown now >> | command. This caused a panic: >> Sound like you somehow run out of memory, there is an known issue >> with >> ZFS which causes livelock when there is memory pressure. Which rsync >> version are you using? With rsync 3.x the memory usage would drop >> drastically which would help to prevent this from happening. > > This isn't known to cause a double fault though. Unfortunately we > probably need more information than was available in order to proceed. Yes, I agree. But I don't know what to do in this sort of case where the machine is completely wedged. Ben From owner-freebsd-stable@FreeBSD.ORG Wed May 14 11:52:49 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 65B82106566B for ; Wed, 14 May 2008 11:52:49 +0000 (UTC) (envelope-from ben@altus-escon.com) Received: from altus-escon.com (altesco.xs4all.nl [82.95.106.39]) by mx1.freebsd.org (Postfix) with ESMTP id E58FB8FC21 for ; Wed, 14 May 2008 11:52:48 +0000 (UTC) (envelope-from ben@altus-escon.com) Received: from giskard.altus-escon.com (giskard.altus-escon.com [193.78.231.1]) by altus-escon.com (8.14.2/8.14.2) with ESMTP id m4EBqZb4022698; Wed, 14 May 2008 13:52:40 +0200 (CEST) (envelope-from ben@altus-escon.com) Message-Id: <6BFEEFEA-46AD-46F6-9485-0A9105593B04@altus-escon.com> From: Ben Stuyts To: Kostik Belousov In-Reply-To: <20080514085025.GL18958@deviant.kiev.zoral.com.ua> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v919.2) Date: Wed, 14 May 2008 13:51:41 +0200 References: <7A0780B6-AD8E-440B-BFDB-EC2C4ACA1A70@altus-escon.com> <4829F1B8.1000707@delphij.net> <11D2E346-752B-4F61-979E-1D64FB34ED34@altus-escon.com> <20080514085025.GL18958@deviant.kiev.zoral.com.ua> X-Mailer: Apple Mail (2.919.2) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (altus-escon.com [193.78.231.142]); Wed, 14 May 2008 13:52:40 +0200 (CEST) X-Virus-Scanned: ClamAV 0.93/6809/Thu Apr 17 11:33:01 2008 on mars.altus-escon.com X-Virus-Status: Clean X-Spam-Status: No, score=-2.4 required=3.5 tests=AWL,BAYES_00 autolearn=ham version=3.2.4 X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on mars.altus-escon.com Cc: stable@freebsd.org, d@delphij.net Subject: Re: Panic after hung rsync, probably zfs related X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 May 2008 11:52:49 -0000 On 14 mei 2008, at 10:50, Kostik Belousov wrote: > 3.5Gb wired ? Do you run amd64 ? Yes. > Does wired memory drops lower after you change the load ? Sorry, forgot to answer this in my previous msg. It is very unpredictable, and I have not found a pattern. It is a small business server, and both during non-office and regular office hours the wired memory varies between the numbers above. Ben From owner-freebsd-stable@FreeBSD.ORG Wed May 14 13:25:03 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D3DDE106564A for ; Wed, 14 May 2008 13:25:03 +0000 (UTC) (envelope-from mvoorhis@eressea.wpi.edu) Received: from mail1.wpi.edu (MAIL1.WPI.EDU [130.215.36.91]) by mx1.freebsd.org (Postfix) with ESMTP id 8E3EE8FC1F for ; Wed, 14 May 2008 13:25:03 +0000 (UTC) (envelope-from mvoorhis@eressea.wpi.edu) Received: from mcafee.wpi.edu (MCAFEE.WPI.EDU [130.215.36.86]) by mail1.wpi.edu (8.14.3.Gamma0/8.14.3.Gamma0) with SMTP id m4ECx8Cm000852; Wed, 14 May 2008 08:59:08 -0400 Received: from (130.215.36.186) by mcafee.wpi.edu via smtp id 6b46_8a5a30ee_21b5_11dd_93d4_0013725b2d50; Wed, 14 May 2008 09:59:07 -0300 Received: from eressea.wpi.edu (ERESSEA.WPI.EDU [130.215.29.46]) by SMTP.WPI.EDU (8.13.8/8.13.8) with ESMTP id m4ECx8wH011525; Wed, 14 May 2008 08:59:08 -0400 (envelope-from mvoorhis@eressea.wpi.edu) Received: from eressea.wpi.edu (localhost [127.0.0.1]) by eressea.wpi.edu (8.14.2/8.14.2) with ESMTP id m4ECx421029601 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 14 May 2008 08:59:07 -0400 (EDT) (envelope-from mvoorhis@eressea.wpi.edu) Received: (from mvoorhis@localhost) by eressea.wpi.edu (8.14.2/8.14.2/Submit) id m4EBY40v095276; Wed, 14 May 2008 07:34:04 -0400 (EDT) (envelope-from mvoorhis) From: Michael Voorhis MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18474.52780.461861.985895@eressea.wpi.edu> Date: Wed, 14 May 2008 07:34:04 -0400 To: Bruce M Simpson In-Reply-To: <4826E7C9.9030407@incunabulum.net> References: <4826E7C9.9030407@incunabulum.net> X-Mailer: VM 7.19 under Emacs 22.1.1 X-Virus-Scanned: ClamAV version 0.93, clamav-milter version 0.93 on eressea.wpi.edu X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.2.4 X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on eressea.wpi.edu Cc: FreeBSD stable Subject: Automounting USB sticks - questions X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mvoorhis@cs.wpi.edu List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 May 2008 13:25:03 -0000 >>>>> "bms" == Bruce M Simpson writes: bms> It would be great if we could ship FreeBSD out of the box, ready bms> to automount removable media. This would be useful to all users, bms> but particularly for novices and people who just wanna get on bms> and use the beast. I think this would be nice, so long as it isn't enabled by default. I've always enjoyed how FreeBSD shuns the feature-creep that infects other operating systems. Wouldn't it also be nice to have automatic printer discovery, automatic WEP/WPA network setup via a nice GUI, etc etc. FreeBSD's documentation is really wonderful, and newbies should be encouraged to read the rich documentation to find out how to (among other things) enable automounting. They'll find out many other great things on the way. Mike V. From owner-freebsd-stable@FreeBSD.ORG Wed May 14 14:38:27 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EF0731065676 for ; Wed, 14 May 2008 14:38:27 +0000 (UTC) (envelope-from lists@lozenetz.org) Received: from mail.webreality.org (mailserver.webreality.org [217.75.141.5]) by mx1.freebsd.org (Postfix) with ESMTP id 9A0758FC1C for ; Wed, 14 May 2008 14:38:26 +0000 (UTC) (envelope-from lists@lozenetz.org) Received: from [10.0.1.101] (unknown [87.121.18.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.webreality.org (Postfix) with ESMTP id 22604FFE80B for ; Wed, 14 May 2008 17:38:25 +0300 (EEST) Message-ID: <482AF959.1000800@lozenetz.org> Date: Wed, 14 May 2008 17:38:17 +0300 From: Anton - Valqk User-Agent: Mozilla-Thunderbird 2.0.0.9 (X11/20080110) MIME-Version: 1.0 To: stable@freebsd.org Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-HostIT-MailScanner-Information: Please contact the ISP for more information X-HostIT-MailScanner: Found to be clean X-HostIT-MailScanner-From: lists@lozenetz.org Cc: Subject: nscd strange behaviour X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 May 2008 14:38:28 -0000 Hi there group, I have nscd running on 6.3 with backports patches, but maybe this will apply to the 7.0? What's the problem: i have nss setup with nss_pg module and authenticates passing through pam pg module. I have nscd running so I can make fewer queries to the pg server when system retrieves uid<->userid. But when I change the password in pg database, I can't get authenticated on the machine running nscd. When I restart it, the new password is retrieved as it should be and authentication goes ok. my config is: moser# cat /etc/nscd.conf # # Default caching daemon configuration file # $FreeBSD: src/etc/nscd.conf,v 1.2.2.1 2007/10/19 00:09:54 bushman Exp $ # enable-cache passwd yes enable-cache group yes enable-cache hosts no enable-cache services no enable-cache protocols no enable-cache rpc no enable-cache networks no #custom threads 25 So my question: Is this a suggested behaviour and shouldn't nscd cache all in passwd struct but password itself? any suggestions, opinions and comments are welcome! cheers, valqk. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From owner-freebsd-stable@FreeBSD.ORG Wed May 14 15:17:47 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1202F1065675; Wed, 14 May 2008 15:17:47 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from falcon.cybervisiontech.com (falcon.cybervisiontech.com [217.20.163.9]) by mx1.freebsd.org (Postfix) with ESMTP id 803DA8FC0C; Wed, 14 May 2008 15:17:46 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from localhost (localhost [127.0.0.1]) by falcon.cybervisiontech.com (Postfix) with ESMTP id 6D149744002; Wed, 14 May 2008 18:17:44 +0300 (EEST) X-Virus-Scanned: Debian amavisd-new at falcon.cybervisiontech.com Received: from falcon.cybervisiontech.com ([127.0.0.1]) by localhost (falcon.cybervisiontech.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yEZM-GKnsmf5; Wed, 14 May 2008 18:17:44 +0300 (EEST) Received: from [10.2.1.87] (gateway.cybervisiontech.com.ua [88.81.251.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by falcon.cybervisiontech.com (Postfix) with ESMTP id 13AE2744001; Wed, 14 May 2008 18:17:43 +0300 (EEST) Message-ID: <482B0297.2050300@icyb.net.ua> Date: Wed, 14 May 2008 18:17:43 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.12 (X11/20080311) MIME-Version: 1.0 To: freebsd-threads@freebsd.org, freebsd-stable@freebsd.org Content-Type: multipart/mixed; boundary="------------070900000602090808030708" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: thread scheduling at mutex unlock X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 May 2008 15:17:47 -0000 This is a multi-part message in MIME format. --------------070900000602090808030708 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I am trying the small attached program on FreeBSD 6.3 (amd64, SCHED_4BSD) and 7-STABLE (i386, SCHED_ULE), both with libthr as threads library and on both it produces "BROKEN" message. I compile this program as follows: cc sched_test.c -o sched_test -pthread I believe that the behavior I observe is broken because: if thread #1 releases a mutex and then tries to re-acquire it while thread #2 was already blocked waiting on that mutex, then thread #1 should be "queued" after thread #2 in mutex waiter's list. Is there any option (thread scheduler, etc) that I could try to achieve "good" behavior? P.S. I understand that all this is subject to (thread) scheduler policy, but I think that what I expect is more reasonable, at least it is more reasonable for my application. -- Andriy Gapon --------------070900000602090808030708-- From owner-freebsd-stable@FreeBSD.ORG Wed May 14 15:25:44 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 302E81065679 for ; Wed, 14 May 2008 15:25:44 +0000 (UTC) (envelope-from vivek@khera.org) Received: from yertle.kcilink.com (thingy.kcilink.com [74.92.149.59]) by mx1.freebsd.org (Postfix) with ESMTP id 0D4748FC15 for ; Wed, 14 May 2008 15:25:44 +0000 (UTC) (envelope-from vivek@khera.org) Received: from host-121.int.kcilink.com (host-121.int.kcilink.com [192.168.7.121]) by yertle.kcilink.com (Postfix) with ESMTP id 90BD58A0B6 for ; Wed, 14 May 2008 11:25:43 -0400 (EDT) Message-Id: <04EA1C34-AB7D-4A85-8A91-DED03E987706@khera.org> From: Vivek Khera To: FreeBSD Stable Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v919.2) Date: Wed, 14 May 2008 11:25:43 -0400 X-Mailer: Apple Mail (2.919.2) Subject: how much memory does increasing max rules for IPFW take up? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 May 2008 15:25:44 -0000 I had a box run out of dynamic state space yesterday. I found I can increase the number of dynamic rules by increasing the sysctl parameter net.inet.ip.fw.dyn_max. I can't find, however, how this affects memory usage on the system. Is it dyanamically allocated and de-allocated, or is it a static memory buffer? Thanks! From owner-freebsd-stable@FreeBSD.ORG Wed May 14 15:44:31 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 94C551065670 for ; Wed, 14 May 2008 15:44:31 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.156]) by mx1.freebsd.org (Postfix) with ESMTP id D23AF8FC16 for ; Wed, 14 May 2008 15:44:30 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: by fg-out-1718.google.com with SMTP id l26so5070843fgb.35 for ; Wed, 14 May 2008 08:44:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; bh=7IYs+uU9YCYzH3d7ati6nRVQqenmIerzVTpEwJltRzk=; b=VIODb4i62CgP6fmUuV/LcrVzN9WE6V9NIw2Ukyr5jIm06sRZGtitk6njOcWeB99dPCejwgRD95/BukEl/+QL9tETsK5MYJ9uVEWEXILtjGAiWkzUDhuQ6lIa3mx+JXylblrqA00eH3Oldk0ID8Zbjzqf8ANkzv94wYa8HthJziw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=wd9zn6ufyICLQV6aFu1H9NmTpun3WRofcrUO3g0GcShnk5iGCqJBavHddpEeESIXNfOKx+K6yVs/rQWQpF3By58ntw2jxe7VwLzvwNxtfVVYGihOBJ5ODMEeF4ydaFtJB0b4XrkePcvn7tDXaHReDtOBfagFNQlOyEdoa1nCFw0= Received: by 10.82.152.9 with SMTP id z9mr163379bud.57.1210779869346; Wed, 14 May 2008 08:44:29 -0700 (PDT) Received: by 10.82.180.3 with HTTP; Wed, 14 May 2008 08:44:29 -0700 (PDT) Message-ID: <7ad7ddd90805140844p9950dc8yf9f24c966a996fbc@mail.gmail.com> Date: Wed, 14 May 2008 17:44:29 +0200 From: "Ulrich Spoerlein" To: stable@freebsd.org MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_2304_4406913.1210779869343" Cc: Subject: RELENG_6 regression: ums0: X report 0x0002 not supported X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 May 2008 15:44:31 -0000 ------=_Part_2304_4406913.1210779869343 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi, after updating an Intel S5000PAL system from 6.2 to 6.3, ums(4) is no longer attaching correctly. Here's an dmesg diff between 6.2 and 6.3 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered ehci0: mem 0xe8d00000-0xe8d003ff irq 23 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: on ehci0 usb4: USB revision 2.0 uhub4: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub4: 8 ports with 8 removable, self powered ukbd0: Avocent Avocent Embedded DVC 1.0, rev 2.00/0.00, addr 2, iclass 3/1 kbd2 at ukbd0 ums0: Avocent Avocent Embedded DVC 1.0, rev 2.00/0.00, addr 2, iclass 3/1 -ums0: 3 buttons and Z dir. -uhid0: Avocent Avocent Embedded DVC 1.0, rev 2.00/0.00, addr 2, iclass 3/1 -uhid0: could not read endpoint descriptor -device_attach: uhid0 attach returned 6 +ums0: X report 0x0002 not supported +device_attach: ums0 attach returned 6 Attached is the full 6.3 dmesg. Looks weird to me, anything I can try on this hardware? Uli ------=_Part_2304_4406913.1210779869343 Content-Type: application/octet-stream; name=dmesg.boot Content-Transfer-Encoding: base64 X-Attachment-Id: f_fg832cux0 Content-Disposition: attachment; filename=dmesg.boot Q29weXJpZ2h0IChjKSAxOTkyLTIwMDggVGhlIEZyZWVCU0QgUHJvamVjdC4KQ29weXJpZ2h0IChj KSAxOTc5LCAxOTgwLCAxOTgzLCAxOTg2LCAxOTg4LCAxOTg5LCAxOTkxLCAxOTkyLCAxOTkzLCAx OTk0CglUaGUgUmVnZW50cyBvZiB0aGUgVW5pdmVyc2l0eSBvZiBDYWxpZm9ybmlhLiBBbGwgcmln aHRzIHJlc2VydmVkLgpGcmVlQlNEIGlzIGEgcmVnaXN0ZXJlZCB0cmFkZW1hcmsgb2YgVGhlIEZy ZWVCU0QgRm91bmRhdGlvbi4KRnJlZUJTRCA2LjMtMjAwODA1MDUtU05BUCAjMDogTW9uIE1heSAg NSAxMToxMzo1OSBVVEMgMjAwOAogICAgcm9vdEBmYnNkYnVpbGQuMTgyMmRpcmVrdC5jb206L3Vz ci9vYmovdXNyL3NyYy9zeXMvU0VSVkVSClRpbWVjb3VudGVyICJpODI1NCIgZnJlcXVlbmN5IDEx OTMxODIgSHogcXVhbGl0eSAwCkNQVTogSW50ZWwoUikgWGVvbihSKSBDUFUgICAgICAgICAgICA1 MTQwICBAIDIuMzNHSHogKDIzMzYuODItTUh6IDY4Ni1jbGFzcyBDUFUpCiAgT3JpZ2luID0gIkdl bnVpbmVJbnRlbCIgIElkID0gMHg2ZjYgIFN0ZXBwaW5nID0gNgogIEZlYXR1cmVzPTB4YmZlYmZi ZmY8RlBVLFZNRSxERSxQU0UsVFNDLE1TUixQQUUsTUNFLENYOCxBUElDLFNFUCxNVFJSLFBHRSxN Q0EsQ01PVixQQVQsUFNFMzYsQ0xGTFVTSCxEVFMsQUNQSSxNTVgsRlhTUixTU0UsU1NFMixTUyxI VFQsVE0sUEJFPgogIEZlYXR1cmVzMj0weDRlM2JkPFNTRTMsUlNWRDIsTU9OLERTX0NQTCxWTVgs RVNULFRNMixTU1NFMyxDWDE2LHhUUFIsUERDTSxEQ0E+CiAgQU1EIEZlYXR1cmVzPTB4MjAxMDAw MDA8TlgsTE0+CiAgQU1EIEZlYXR1cmVzMj0weDE8TEFIRj4KICBDb3JlcyBwZXIgcGFja2FnZTog MgpyZWFsIG1lbW9yeSAgPSAzNDg1NDY2NjI0ICgzMzI0IE1CKQphdmFpbCBtZW1vcnkgPSAzNDA5 MjE5NTg0ICgzMjUxIE1CKQpBQ1BJIEFQSUMgVGFibGU6IDxJTlRFTCAgUzUwMDBQQUw+CkZyZWVC U0QvU01QOiBNdWx0aXByb2Nlc3NvciBTeXN0ZW0gRGV0ZWN0ZWQ6IDIgQ1BVcwogY3B1MCAoQlNQ KTogQVBJQyBJRDogIDAKIGNwdTEgKEFQKTogQVBJQyBJRDogIDEKaW9hcGljMCA8VmVyc2lvbiAy LjA+IGlycXMgMC0yMyBvbiBtb3RoZXJib2FyZAppb2FwaWMxIDxWZXJzaW9uIDIuMD4gaXJxcyAy NC00NyBvbiBtb3RoZXJib2FyZApsYXBpYzA6IEZvcmNpbmcgTElOVDEgdG8gZWRnZSB0cmlnZ2Vy CmtiZDEgYXQga2JkbXV4MAphY3BpMDogPElOVEVMIFM1MDAwUEFMPiBvbiBtb3RoZXJib2FyZAph Y3BpMDogUG93ZXIgQnV0dG9uIChmaXhlZCkKVGltZWNvdW50ZXIgIkFDUEktZmFzdCIgZnJlcXVl bmN5IDM1Nzk1NDUgSHogcXVhbGl0eSAxMDAwCmFjcGlfdGltZXIwOiA8MjQtYml0IHRpbWVyIGF0 IDMuNTc5NTQ1TUh6PiBwb3J0IDB4NDA4LTB4NDBiIG9uIGFjcGkwCmFjcGlfaHBldDA6IDxIaWdo IFByZWNpc2lvbiBFdmVudCBUaW1lcj4gaW9tZW0gMHhmZWQwMDAwMC0weGZlZDAwM2ZmIG9uIGFj cGkwClRpbWVjb3VudGVyICJIUEVUIiBmcmVxdWVuY3kgMTQzMTgxODAgSHogcXVhbGl0eSA5MDAK Y3B1MDogPEFDUEkgQ1BVPiBvbiBhY3BpMAphY3BpX3Rocm90dGxlMDogPEFDUEkgQ1BVIFRocm90 dGxpbmc+IG9uIGNwdTAKY3B1MTogPEFDUEkgQ1BVPiBvbiBhY3BpMAphY3BpX3Rocm90dGxlMTog PEFDUEkgQ1BVIFRocm90dGxpbmc+IG9uIGNwdTEKYWNwaV90aHJvdHRsZTE6IGZhaWxlZCB0byBh dHRhY2ggUF9DTlQKZGV2aWNlX2F0dGFjaDogYWNwaV90aHJvdHRsZTEgYXR0YWNoIHJldHVybmVk IDYKYWNwaV9idXR0b24wOiA8UG93ZXIgQnV0dG9uPiBvbiBhY3BpMApwY2liMDogPEFDUEkgSG9z dC1QQ0kgYnJpZGdlPiBwb3J0IDB4Y2EyLDB4Y2EzLDB4Y2Y4LTB4Y2ZmIG9uIGFjcGkwCnBjaTA6 IDxBQ1BJIFBDSSBidXM+IG9uIHBjaWIwCnBjaWIxOiA8QUNQSSBQQ0ktUENJIGJyaWRnZT4gYXQg ZGV2aWNlIDIuMCBvbiBwY2kwCnBjaTE6IDxBQ1BJIFBDSSBidXM+IG9uIHBjaWIxCnBjaWIyOiA8 QUNQSSBQQ0ktUENJIGJyaWRnZT4gaXJxIDE2IGF0IGRldmljZSAwLjAgb24gcGNpMQpwY2kyOiA8 QUNQSSBQQ0kgYnVzPiBvbiBwY2liMgpwY2liMzogPEFDUEkgUENJLVBDSSBicmlkZ2U+IGlycSAx NiBhdCBkZXZpY2UgMC4wIG9uIHBjaTIKcGNpMzogPEFDUEkgUENJIGJ1cz4gb24gcGNpYjMKcGNp YjQ6IDxBQ1BJIFBDSS1QQ0kgYnJpZGdlPiBhdCBkZXZpY2UgMC4wIG9uIHBjaTMKcGNpNDogPEFD UEkgUENJIGJ1cz4gb24gcGNpYjQKbWZpMDogPExTSSBNZWdhU0FTIDEwNjRSPiBtZW0gMHhlOGIw MDAwMC0weGU4YjBmZmZmLDB4ZTg5MDAwMDAtMHhlODkxZmZmZiBpcnEgMTggYXQgZGV2aWNlIDE0 LjAgb24gcGNpNAptZmkwOiBNZWdhcmFpZCBTQVMgZHJpdmVyIFZlciAyLjAwIAptZmkwOiAxNDkz ICgyNjQwODgxODNzLzB4MDAyMC8wKSAtIFNodXRkb3duIGNvbW1hbmQgcmVjZWl2ZWQgZnJvbSBo b3N0Cm1maTA6IDE0OTQgKDQyNzgxOTAwODBzLzB4MDAyMC8wKSAtIFBDSSAweDA0MTAwMCAweDA0 NDExIDB4MDQ4MDg2IDB4MDQzNTAxOiBGaXJtd2FyZSBpbml0aWFsaXphdGlvbiBzdGFydGVkIChQ Q0kgSUQgMDQxMS8xMDAwLzM1MDEvODA4NikKbWZpMDogMTQ5NSAoNDI3ODE5MDA4MHMvMHgwMDIw LzApIC0gVHlwZSAxODogRmlybXdhcmUgdmVyc2lvbiAxLjAzLjAwLTAyMTEKbWZpMDogMTQ5NiAo NDI3ODE5MDEwMHMvMHgwMDA4LzApIC0gQmF0dGVyeSB0ZW1wZXJhdHVyZSBpcyBub3JtYWwKbWZp MDogMTQ5NyAoNDI3ODE5MDEwMHMvMHgwMDA4LzApIC0gQmF0dGVyeSBQcmVzZW50Cm1maTA6IDE0 OTggKDQyNzgxOTAxNDRzLzB4MDAwNC8wKSAtIFBEIDEwKGUxL3MyNTUpIGV2ZW50OiBFbmNsb3N1 cmUgKFNFUykgZGlzY292ZXJlZCBvbiBQRCAwYShlMS9zMjU1KQptZmkwOiAxNDk5ICg0Mjc4MTkw MTQ0cy8weDAwMDIvMCkgLSBQRCAxMChlMS9zMjU1KSBldmVudDogSW5zZXJ0ZWQ6IFBEIDBhKGUx L3MyNTUpCm1maTA6IDE1MDAgKDQyNzgxOTAxNDRzLzB4MDAwMi8wKSAtIFR5cGUgMjk6IEluc2Vy dGVkOiBQRCAwYShlMS9zMjU1KSBJbmZvOiBlbmNsUGQ9MGEsIHNjc2lUeXBlPWQsIHBvcnRNYXA9 MDAsIHNhc0FkZHI9NTAwMDQwM2RlY2VjMjAwMCwwMDAwMDAwMDAwMDAwMDAwCm1maTA6IDE1MDEg KDQyNzgxOTAxNDRzLzB4MDAwMi8wKSAtIFBEIDA4KGUxL3MwKSBldmVudDogSW5zZXJ0ZWQ6IFBE IDA4KGUxL3MwKQptZmkwOiAxNTAyICg0Mjc4MTkwMTQ0cy8weDAwMDIvMCkgLSBUeXBlIDI5OiBJ bnNlcnRlZDogUEQgMDgoZTEvczApIEluZm86IGVuY2xQZD0wYSwgc2NzaVR5cGU9MCwgcG9ydE1h cD0wMSwgc2FzQWRkcj01MDAwYzUwMDA1ODE5OTc5LDAwMDAwMDAwMDAwMDAwMDAKbWZpMDogMTUw MyAoNDI3ODE5MDE0NHMvMHgwMDAyLzApIC0gUEQgMDkoZTEvczEpIGV2ZW50OiBJbnNlcnRlZDog UEQgMDkoZTEvczEpCm1maTA6IDE1MDQgKDQyNzgxOTAxNDRzLzB4MDAwMi8wKSAtIFR5cGUgMjk6 IEluc2VydGVkOiBQRCAwOShlMS9zMSkgSW5mbzogZW5jbFBkPTBhLCBzY3NpVHlwZT0wLCBwb3J0 TWFwPTAyLCBzYXNBZGRyPTUwMDBjNTAwMDU4MmI2YTksMDAwMDAwMDAwMDAwMDAwMAptZmkwOiAx NTA1ICgyNjQwODgzMDJzLzB4MDAyMC8wKSAtIEFkYXB0ZXIgdGlja3MgMjY0MDg4MzAyIGVsYXBz ZWQgNjVzOiBUaW1lIGVzdGFibGlzaGVkIGFzIDA1LzE0LzA4IDEzOjUxOjQyOyAoNjUgc2Vjb25k cyBzaW5jZSBwb3dlciBvbikKcGNpYjU6IDxQQ0ktUENJIGJyaWRnZT4gYXQgZGV2aWNlIDAuMiBv biBwY2kzCnBjaTU6IDxQQ0kgYnVzPiBvbiBwY2liNQpwY2liNjogPEFDUEkgUENJLVBDSSBicmlk Z2U+IGlycSAxNiBhdCBkZXZpY2UgMS4wIG9uIHBjaTIKcGNpNjogPEFDUEkgUENJIGJ1cz4gb24g cGNpYjYKcGNpYjc6IDxBQ1BJIFBDSS1QQ0kgYnJpZGdlPiBpcnEgMTYgYXQgZGV2aWNlIDIuMCBv biBwY2kyCnBjaTc6IDxBQ1BJIFBDSSBidXM+IG9uIHBjaWI3CmVtMDogPEludGVsKFIpIFBSTy8x MDAwIE5ldHdvcmsgQ29ubmVjdGlvbiBWZXJzaW9uIC0gNi43LjM+IHBvcnQgMHgyMDIwLTB4MjAz ZiBtZW0gMHhlODgyMDAwMC0weGU4ODNmZmZmLDB4ZTg0MDAwMDAtMHhlODdmZmZmZiBpcnEgMTgg YXQgZGV2aWNlIDAuMCBvbiBwY2k3CmVtMDogVXNpbmcgTVNJIGludGVycnVwdAplbTA6IEV0aGVy bmV0IGFkZHJlc3M6IDAwOjA0OjIzOmRlOmNlOmMyCmVtMTogPEludGVsKFIpIFBSTy8xMDAwIE5l dHdvcmsgQ29ubmVjdGlvbiBWZXJzaW9uIC0gNi43LjM+IHBvcnQgMHgyMDAwLTB4MjAxZiBtZW0g MHhlODgwMDAwMC0weGU4ODFmZmZmLDB4ZTgwMDAwMDAtMHhlODNmZmZmZiBpcnEgMTkgYXQgZGV2 aWNlIDAuMSBvbiBwY2k3CmVtMTogVXNpbmcgTVNJIGludGVycnVwdAplbTE6IEV0aGVybmV0IGFk ZHJlc3M6IDAwOjA0OjIzOmRlOmNlOmMzCnBjaWI4OiA8QUNQSSBQQ0ktUENJIGJyaWRnZT4gYXQg ZGV2aWNlIDAuMyBvbiBwY2kxCnBjaTg6IDxBQ1BJIFBDSSBidXM+IG9uIHBjaWI4CnBjaWI5OiA8 UENJLVBDSSBicmlkZ2U+IGF0IGRldmljZSAzLjAgb24gcGNpMApwY2k5OiA8UENJIGJ1cz4gb24g cGNpYjkKcGNpYjEwOiA8QUNQSSBQQ0ktUENJIGJyaWRnZT4gYXQgZGV2aWNlIDQuMCBvbiBwY2kw CnBjaTEwOiA8QUNQSSBQQ0kgYnVzPiBvbiBwY2liMTAKcGNpYjExOiA8QUNQSSBQQ0ktUENJIGJy aWRnZT4gYXQgZGV2aWNlIDUuMCBvbiBwY2kwCnBjaTExOiA8QUNQSSBQQ0kgYnVzPiBvbiBwY2li MTEKcGNpYjEyOiA8QUNQSSBQQ0ktUENJIGJyaWRnZT4gYXQgZGV2aWNlIDYuMCBvbiBwY2kwCnBj aTEyOiA8QUNQSSBQQ0kgYnVzPiBvbiBwY2liMTIKcGNpYjEzOiA8QUNQSSBQQ0ktUENJIGJyaWRn ZT4gYXQgZGV2aWNlIDcuMCBvbiBwY2kwCnBjaTEzOiA8QUNQSSBQQ0kgYnVzPiBvbiBwY2liMTMK cGNpMDogPGJhc2UgcGVyaXBoZXJhbD4gYXQgZGV2aWNlIDguMCAobm8gZHJpdmVyIGF0dGFjaGVk KQp1aGNpMDogPFVIQ0kgKGdlbmVyaWMpIFVTQiBjb250cm9sbGVyPiBwb3J0IDB4MzA4MC0weDMw OWYgaXJxIDIzIGF0IGRldmljZSAyOS4wIG9uIHBjaTAKdWhjaTA6IFtHSUFOVC1MT0NLRURdCnVz YjA6IDxVSENJIChnZW5lcmljKSBVU0IgY29udHJvbGxlcj4gb24gdWhjaTAKdXNiMDogVVNCIHJl dmlzaW9uIDEuMAp1aHViMDogSW50ZWwgVUhDSSByb290IGh1YiwgY2xhc3MgOS8wLCByZXYgMS4w MC8xLjAwLCBhZGRyIDEKdWh1YjA6IDIgcG9ydHMgd2l0aCAyIHJlbW92YWJsZSwgc2VsZiBwb3dl cmVkCnVoY2kxOiA8VUhDSSAoZ2VuZXJpYykgVVNCIGNvbnRyb2xsZXI+IHBvcnQgMHgzMDYwLTB4 MzA3ZiBpcnEgMjIgYXQgZGV2aWNlIDI5LjEgb24gcGNpMAp1aGNpMTogW0dJQU5ULUxPQ0tFRF0K dXNiMTogPFVIQ0kgKGdlbmVyaWMpIFVTQiBjb250cm9sbGVyPiBvbiB1aGNpMQp1c2IxOiBVU0Ig cmV2aXNpb24gMS4wCnVodWIxOiBJbnRlbCBVSENJIHJvb3QgaHViLCBjbGFzcyA5LzAsIHJldiAx LjAwLzEuMDAsIGFkZHIgMQp1aHViMTogMiBwb3J0cyB3aXRoIDIgcmVtb3ZhYmxlLCBzZWxmIHBv d2VyZWQKdWhjaTI6IDxVSENJIChnZW5lcmljKSBVU0IgY29udHJvbGxlcj4gcG9ydCAweDMwNDAt MHgzMDVmIGlycSAyMyBhdCBkZXZpY2UgMjkuMiBvbiBwY2kwCnVoY2kyOiBbR0lBTlQtTE9DS0VE XQp1c2IyOiA8VUhDSSAoZ2VuZXJpYykgVVNCIGNvbnRyb2xsZXI+IG9uIHVoY2kyCnVzYjI6IFVT QiByZXZpc2lvbiAxLjAKdWh1YjI6IEludGVsIFVIQ0kgcm9vdCBodWIsIGNsYXNzIDkvMCwgcmV2 IDEuMDAvMS4wMCwgYWRkciAxCnVodWIyOiAyIHBvcnRzIHdpdGggMiByZW1vdmFibGUsIHNlbGYg cG93ZXJlZAp1aGNpMzogPFVIQ0kgKGdlbmVyaWMpIFVTQiBjb250cm9sbGVyPiBwb3J0IDB4MzAy MC0weDMwM2YgaXJxIDIyIGF0IGRldmljZSAyOS4zIG9uIHBjaTAKdWhjaTM6IFtHSUFOVC1MT0NL RURdCnVzYjM6IDxVSENJIChnZW5lcmljKSBVU0IgY29udHJvbGxlcj4gb24gdWhjaTMKdXNiMzog VVNCIHJldmlzaW9uIDEuMAp1aHViMzogSW50ZWwgVUhDSSByb290IGh1YiwgY2xhc3MgOS8wLCBy ZXYgMS4wMC8xLjAwLCBhZGRyIDEKdWh1YjM6IDIgcG9ydHMgd2l0aCAyIHJlbW92YWJsZSwgc2Vs ZiBwb3dlcmVkCmVoY2kwOiA8RUhDSSAoZ2VuZXJpYykgVVNCIDIuMCBjb250cm9sbGVyPiBtZW0g MHhlOGQwMDAwMC0weGU4ZDAwM2ZmIGlycSAyMyBhdCBkZXZpY2UgMjkuNyBvbiBwY2kwCmVoY2kw OiBbR0lBTlQtTE9DS0VEXQp1c2I0OiBFSENJIHZlcnNpb24gMS4wCnVzYjQ6IGNvbXBhbmlvbiBj b250cm9sbGVycywgMiBwb3J0cyBlYWNoOiB1c2IwIHVzYjEgdXNiMiB1c2IzCnVzYjQ6IDxFSENJ IChnZW5lcmljKSBVU0IgMi4wIGNvbnRyb2xsZXI+IG9uIGVoY2kwCnVzYjQ6IFVTQiByZXZpc2lv biAyLjAKdWh1YjQ6IEludGVsIEVIQ0kgcm9vdCBodWIsIGNsYXNzIDkvMCwgcmV2IDIuMDAvMS4w MCwgYWRkciAxCnVodWI0OiA4IHBvcnRzIHdpdGggOCByZW1vdmFibGUsIHNlbGYgcG93ZXJlZAp1 a2JkMDogQXZvY2VudCBBdm9jZW50IEVtYmVkZGVkIERWQyAxLjAsIHJldiAyLjAwLzAuMDAsIGFk ZHIgMiwgaWNsYXNzIDMvMQprYmQyIGF0IHVrYmQwCnVtczA6IEF2b2NlbnQgQXZvY2VudCBFbWJl ZGRlZCBEVkMgMS4wLCByZXYgMi4wMC8wLjAwLCBhZGRyIDIsIGljbGFzcyAzLzEKdW1zMDogWCBy ZXBvcnQgMHgwMDAyIG5vdCBzdXBwb3J0ZWQKZGV2aWNlX2F0dGFjaDogdW1zMCBhdHRhY2ggcmV0 dXJuZWQgNgpwY2liMTQ6IDxBQ1BJIFBDSS1QQ0kgYnJpZGdlPiBhdCBkZXZpY2UgMzAuMCBvbiBw Y2kwCnBjaTE0OiA8QUNQSSBQQ0kgYnVzPiBvbiBwY2liMTQKcGNpMTQ6IDxkaXNwbGF5LCBWR0E+ IGF0IGRldmljZSAxMi4wIChubyBkcml2ZXIgYXR0YWNoZWQpCmlzYWIwOiA8UENJLUlTQSBicmlk Z2U+IGF0IGRldmljZSAzMS4wIG9uIHBjaTAKaXNhMDogPElTQSBidXM+IG9uIGlzYWIwCmF0YXBj aTA6IDxJbnRlbCA2M1hYRVNCMiBVRE1BMTAwIGNvbnRyb2xsZXI+IHBvcnQgMHgxZjAtMHgxZjcs MHgzZjYsMHgxNzAtMHgxNzcsMHgzNzYsMHgzMGEwLTB4MzBhZiBpcnEgMjAgYXQgZGV2aWNlIDMx LjEgb24gcGNpMAphdGEwOiA8QVRBIGNoYW5uZWwgMD4gb24gYXRhcGNpMAphdGExOiA8QVRBIGNo YW5uZWwgMT4gb24gYXRhcGNpMAppY2hzbWIwOiA8U01CdXMgY29udHJvbGxlcj4gcG9ydCAweDMw MDAtMHgzMDFmIGlycSAyMCBhdCBkZXZpY2UgMzEuMyBvbiBwY2kwCmljaHNtYjA6IFtHSUFOVC1M T0NLRURdCnNtYnVzMDogPFN5c3RlbSBNYW5hZ2VtZW50IEJ1cz4gb24gaWNoc21iMApzbWIwOiA8 U01CdXMgZ2VuZXJpYyBJL08+IG9uIHNtYnVzMApzaW8wOiA8MTY1NTBBLWNvbXBhdGlibGUgQ09N IHBvcnQ+IHBvcnQgMHgzZjgtMHgzZmYgaXJxIDQgZmxhZ3MgMHgxMCBvbiBhY3BpMApzaW8wOiB0 eXBlIDE2NTUwQQpzaW8xOiA8MTY1NTBBLWNvbXBhdGlibGUgQ09NIHBvcnQ+IHBvcnQgMHgyZjgt MHgyZmYgaXJxIDMgb24gYWNwaTAKc2lvMTogdHlwZSAxNjU1MEEKYXRrYmRjMDogPEtleWJvYXJk IGNvbnRyb2xsZXIgKGk4MDQyKT4gcG9ydCAweDYwLDB4NjQgaXJxIDEgb24gYWNwaTAKYXRrYmQw OiA8QVQgS2V5Ym9hcmQ+IGlycSAxIG9uIGF0a2JkYzAKa2JkMCBhdCBhdGtiZDAKYXRrYmQwOiBb R0lBTlQtTE9DS0VEXQpwbXRpbWVyMCBvbiBpc2EwCm9ybTA6IDxJU0EgT3B0aW9uIFJPTXM+IGF0 IGlvbWVtIDB4YzAwMDAtMHhjOGZmZiwweGM5MDAwLTB4Y2RmZmYgb24gaXNhMApwcGMwOiBwYXJh bGxlbCBwb3J0IG5vdCBmb3VuZC4Kc2MwOiA8U3lzdGVtIGNvbnNvbGU+IGF0IGZsYWdzIDB4MTAw IG9uIGlzYTAKc2MwOiBWR0EgPDE2IHZpcnR1YWwgY29uc29sZXMsIGZsYWdzPTB4MzAwPgp2Z2Ew OiA8R2VuZXJpYyBJU0EgVkdBPiBhdCBwb3J0IDB4M2MwLTB4M2RmIGlvbWVtIDB4YTAwMDAtMHhi ZmZmZiBvbiBpc2EwCnVrYmQxOiB2ZW5kb3IgMHgwNDZhIHByb2R1Y3QgMHgwMDIzLCByZXYgMi4w MC8wLjMyLCBhZGRyIDIsIGljbGFzcyAzLzEKa2JkMyBhdCB1a2JkMQp1aGlkMDogdmVuZG9yIDB4 MDQ2YSBwcm9kdWN0IDB4MDAyMywgcmV2IDIuMDAvMC4zMiwgYWRkciAyLCBpY2xhc3MgMy8xClRp bWVjb3VudGVycyB0aWNrIGV2ZXJ5IDEuMDAwIG1zZWMKYWNkMDogQ0RSVyA8T3B0aWFyYyBDRC1S VyBDUlg4ODBBL0tYMTA+IGF0IGF0YTAtc2xhdmUgVURNQTMzCm1maWQwOiA8TUZJIExvZ2ljYWwg RGlzaz4gb24gbWZpMAptZmlkMDogNjg2NjRNQiAoMTQwNjIzODcyIHNlY3RvcnMpIFJBSUQgdm9s dW1lICcnIGlzIG9wdGltYWwKbGFwaWMxOiBGb3JjaW5nIExJTlQxIHRvIGVkZ2UgdHJpZ2dlcgpT TVA6IEFQIENQVSAjMSBMYXVuY2hlZCEKVHJ5aW5nIHRvIG1vdW50IHJvb3QgZnJvbSB1ZnM6L2Rl di9tZmlkMHMxYQo= ------=_Part_2304_4406913.1210779869343-- From owner-freebsd-stable@FreeBSD.ORG Wed May 14 15:58:49 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9DD7B1065672 for ; Wed, 14 May 2008 15:58:49 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.154]) by mx1.freebsd.org (Postfix) with ESMTP id DB5008FC0A for ; Wed, 14 May 2008 15:58:48 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: by fg-out-1718.google.com with SMTP id l26so5077520fgb.35 for ; Wed, 14 May 2008 08:58:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; bh=r/m7ydjxAxCYZKdTHardrG9uduE+D+ZPrgFuuX+7kjg=; b=o2LdIQ+XyrdiOhHA74gI+XncMSLdW/ceTwBjE73hml+SJyltWNgGbE7nDec2OqcAf+kWfiZYSgj4KZK6PS2KNxOEGCbzSutUSzJIvDA7m6KVB4Sls70EzykQrs7aIK+mWHgVvVEFYUui8v3GmaS9spmIeG3IJmQSjxr10255Xu4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=TxHztnOQqNEieE/zf+LcIsg7RN5mdU3aHMA8R4SPRrTwPgFAuLBJWJ50u2113sNmQIEwxjJxMgOB+uZuFcgkNCCCjzmP0W8gWqdBsPmpylh8Rp3PNpSH5+V3o8xku3R1Lvxd8bMhKyLxFnp+PS/wCAt2U3iEDFE+rtC//ReeHzA= Received: by 10.82.151.9 with SMTP id y9mr160652bud.8.1210779172758; Wed, 14 May 2008 08:32:52 -0700 (PDT) Received: by 10.82.180.3 with HTTP; Wed, 14 May 2008 08:32:52 -0700 (PDT) Message-ID: <7ad7ddd90805140832p23b70cb6s731e5d5bf907114b@mail.gmail.com> Date: Wed, 14 May 2008 17:32:52 +0200 From: "Ulrich Spoerlein" To: stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: RELENG_6 regression: panic: vm_fault on nofault entry, addr: c8000000 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 May 2008 15:58:49 -0000 Hi, there's a regression going from 6.2 to 6.3, where it will panic upon booting the kernel within vm_fault. This problem has been discussed before, but I'm seeing it reliably on a RELENG_6 checkout from 5th of May. It affects multiple (but identical) systems, here's an verbose boot leading to the panic. Please note that 6.2 was running fine on these machines, they also boot "normally" if I disable ACPI (but this is not really an option). SMAP type=01 base=0000000000000000 len=000000000009d800 SMAP type=02 base=000000000009d800 len=0000000000002800 SMAP type=02 base=00000000000ce000 len=0000000000002000 SMAP type=02 base=00000000000e4000 len=000000000001c000 SMAP type=01 base=0000000000100000 len=00000000cfe60000 SMAP type=03 base=00000000cff60000 len=0000000000009000 SMAP type=04 base=00000000cff69000 len=0000000000017000 SMAP type=02 base=00000000cff80000 len=0000000000080000 SMAP type=02 base=00000000e0000000 len=0000000010000000 SMAP type=02 base=00000000fec00000 len=0000000000010000 SMAP type=02 base=00000000fee00000 len=0000000000001000 SMAP type=02 base=00000000ff000000 len=0000000001000000 SMAP type=01 base=0000000100000000 len=0000000030000000 786432K of memory above 4GB ignored Copyright (c) 1992-2008 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 6.3-20080505-SNAP #0: Mon May 5 11:42:32 UTC 2008 root@fbsdbuild.1822direkt.com:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel "/boot/kernel/kernel" at 0xc1051000. Preloaded mfs_root "/boot/mfsroot" at 0xc10511e8. Preloaded elf module "/boot/modules/acpi.ko" at 0xc105122c. MP Configuration Table version 1.4 found at 0xc009dd71 Table 'FACP' at 0xcff68e48 Table 'APIC' at 0xcff68ebc MADT: Found table at 0xcff68ebc APIC: Using the MADT enumerator. MADT: Found CPU APIC ID 0 ACPI ID 0: enabled MADT: Found CPU APIC ID 4 ACPI ID 1: enabled MADT: Found CPU APIC ID 2 ACPI ID 2: enabled MADT: Found CPU APIC ID 6 ACPI ID 3: enabled ACPI APIC Table: Calibrating clock(s) ... i8254 clock: 1193204 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 3000122064 Hz CPU: Intel(R) Xeon(TM) CPU 3.00GHz (3000.12-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf64 Stepping = 4 Features=0xbfebfbff Features2=0xe4bd AMD Features=0x20100000 AMD Features2=0x1 Cores per package: 2 Logical CPUs per core: 2 real memory = 3489005568 (3327 MB) Physical memory chunk(s): 0x0000000000001000 - 0x000000000009cfff, 638976 bytes (156 pages) 0x0000000000100000 - 0x00000000003fffff, 3145728 bytes (768 pages) 0x0000000001425000 - 0x00000000cc488fff, 3406184448 bytes (831588 pages) avail memory = 3405979648 (3248 MB) bios32: Found BIOS32 Service Directory header at 0xc00f5960 bios32: Entry = 0xfd520 (c00fd520) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xfd520+0x247 pnpbios: Found PnP BIOS data at 0xc00f59e0 pnpbios: Entry = f0000:af28 Rev = 1.0 Other BIOS signatures found: APIC: CPU 0 has ACPI ID 0 MADT: Found IO APIC ID 8, Interrupt 0 at 0xfec00000 ioapic0: Routing external 8259A's -> intpin 0 MADT: Found IO APIC ID 9, Interrupt 24 at 0xfec80000 lapic0: Routing NMI -> LINT1 lapic0: LINT1 trigger: edge lapic0: LINT1 polarity: high lapic4: Routing NMI -> LINT1 lapic4: LINT1 trigger: edge lapic4: LINT1 polarity: high lapic2: Routing NMI -> LINT1 lapic2: LINT1 trigger: edge lapic2: LINT1 polarity: high lapic6: Routing NMI -> LINT1 lapic6: LINT1 trigger: edge lapic6: LINT1 polarity: high MADT: Interrupt override: source 0, irq 2 ioapic0: Routing IRQ 0 -> intpin 2 MADT: Interrupt override: source 9, irq 9 ioapic0: intpin 9 trigger: level ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard cpu0 BSP: ID: 0x00000000 VER: 0x00050014 LDR: 0xff000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00000200 err: 0x00010000 pcm: 0x00010000 ath_rate: version 1.2 wlan: <802.11 Link Layer> null: random: nfslock: pseudo-device io: kbd: new array size 4 kbd1 at kbdmux0 mem: Pentium Pro MTRR support enabled ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) rr232x: RocketRAID 232x controller driver v1.02 (May 5 2008 11:42:16) hptrr: HPT RocketRAID controller driver v1.1 (May 5 2008 11:42:14) npx0: INT 16 interface acpi0: on motherboard ioapic0: routing intpin 9 (ISA IRQ 9) to vector 48 acpi0: [MPSAFE] pci_open(1): mode 1 addr port (0x0cf8) is 0x80008058 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=25d88086) pcibios: BIOS version 2.10 AcpiOsDerivePciId: \_SB_.PCI0.LPC0.PIRX -> bus 0 dev 31 func 0 AcpiOsDerivePciId: \_SB_.PCI0.LPC0.PIRY -> bus 0 dev 31 func 0 acpi0: Power Button (fixed) acpi0: wakeup code va 0xdca93000 pa 0x9c000 AcpiOsDerivePciId: \_SB_.PCI0.LPC0.REGS -> bus 0 dev 31 func 0 ACPI timer: 1/0 1/0 1/0 1/0 1/0 1/0 1/0 1/0 1/0 1/0 -> 10 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 pci_link0: Index IRQ Rtd Ref IRQs Initial Probe 0 7 N 0 3 4 5 6 7 10 11 14 15 Validation 0 7 N 0 3 4 5 6 7 10 11 14 15 After Disable 0 255 N 0 3 4 5 6 7 10 11 14 15 pci_link1: Index IRQ Rtd Ref IRQs Initial Probe 0 5 N 0 3 4 5 6 7 10 11 14 15 Validation 0 5 N 0 3 4 5 6 7 10 11 14 15 After Disable 0 255 N 0 3 4 5 6 7 10 11 14 15 pci_link2: Index IRQ Rtd Ref IRQs Initial Probe 0 11 N 0 3 4 5 6 7 10 11 14 15 Validation 0 11 N 0 3 4 5 6 7 10 11 14 15 After Disable 0 255 N 0 3 4 5 6 7 10 11 14 15 pci_link3: Index IRQ Rtd Ref IRQs Initial Probe 0 10 N 0 3 4 5 6 7 10 11 14 15 Validation 0 10 N 0 3 4 5 6 7 10 11 14 15 After Disable 0 255 N 0 3 4 5 6 7 10 11 14 15 pci_link4: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 3 4 5 6 7 10 11 14 15 Validation 0 255 N 0 3 4 5 6 7 10 11 14 15 After Disable 0 255 N 0 3 4 5 6 7 10 11 14 15 pci_link5: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 4 5 6 7 10 11 14 15 Validation 0 255 N 0 4 5 6 7 10 11 14 15 After Disable 0 255 N 0 4 5 6 7 10 11 14 15 pci_link6: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 3 4 5 6 7 10 11 14 15 Validation 0 255 N 0 3 4 5 6 7 10 11 14 15 After Disable 0 255 N 0 3 4 5 6 7 10 11 14 15 pci_link7: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 4 5 6 7 10 11 14 15 Validation 0 255 N 0 4 5 6 7 10 11 14 15 After Disable 0 255 N 0 4 5 6 7 10 11 14 15 cpu0: on acpi0 panic: vm_fault: fault on nofault entry, addr: c8000000 Uptime: 1s Automatic reboot in 15 seconds - press a key on the console to abort --> Press a key on the console to reboot, --> or switch off the system now. Rebooting... What to do? Uli From owner-freebsd-stable@FreeBSD.ORG Wed May 14 18:21:08 2008 Return-Path: Delivered-To: stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 930E610656A8 for ; Wed, 14 May 2008 18:21:08 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from mail-gw1.york.ac.uk (mail-gw1.york.ac.uk [144.32.128.246]) by mx1.freebsd.org (Postfix) with ESMTP id 2933C8FC16 for ; Wed, 14 May 2008 18:21:07 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from mail-gw7.york.ac.uk (mail-gw7.york.ac.uk [144.32.129.30]) by mail-gw1.york.ac.uk (8.13.6/8.13.6) with ESMTP id m4EHnUw8016667; Wed, 14 May 2008 18:49:30 +0100 (BST) Received: from buffy-128.york.ac.uk ([144.32.128.160] helo=buffy.york.ac.uk) by mail-gw7.york.ac.uk with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1JwL6Y-0002eh-3F; Wed, 14 May 2008 18:49:30 +0100 Received: from buffy.york.ac.uk (localhost [127.0.0.1]) by buffy.york.ac.uk (8.14.2/8.14.2) with ESMTP id m4EHnTvh036387; Wed, 14 May 2008 18:49:29 +0100 (BST) (envelope-from gavin@FreeBSD.org) Received: (from ga9@localhost) by buffy.york.ac.uk (8.14.2/8.14.2/Submit) id m4EHnS46036386; Wed, 14 May 2008 18:49:28 +0100 (BST) (envelope-from gavin@FreeBSD.org) X-Authentication-Warning: buffy.york.ac.uk: ga9 set sender to gavin@FreeBSD.org using -f From: Gavin Atkinson To: Ulrich Spoerlein In-Reply-To: <7ad7ddd90805140832p23b70cb6s731e5d5bf907114b@mail.gmail.com> References: <7ad7ddd90805140832p23b70cb6s731e5d5bf907114b@mail.gmail.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Wed, 14 May 2008 18:49:27 +0100 Message-Id: <1210787367.29891.80.camel@buffy.york.ac.uk> Mime-Version: 1.0 X-Mailer: Evolution 2.10.1 FreeBSD GNOME Team Port X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin@freebsd.org Cc: stable@FreeBSD.org Subject: Re: RELENG_6 regression: panic: vm_fault on nofault entry, addr: c8000000 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 May 2008 18:21:08 -0000 On Wed, 2008-05-14 at 17:32 +0200, Ulrich Spoerlein wrote: > Hi, > > there's a regression going from 6.2 to 6.3, where it will panic upon > booting the kernel within vm_fault. This problem has been discussed > before, but I'm seeing it reliably on a RELENG_6 checkout from 5th of > May. > > It affects multiple (but identical) systems, here's an verbose boot > leading to the panic. Please note that 6.2 was running fine on these > machines, they also boot "normally" if I disable ACPI (but this is not > really an option). [snip dmesg output] > What to do? If you don't get any suggestions from people as to what it may be, and you have a system you can afford to reboot a few times, the easiest thing to do is to take the system back to 6.2, and then update your source to a date midway between 6.2 and 6.3 and see if that crashes. Use this in your supfile: *default tag=RELENG_6 *default date=2007.07.01.00.00.00 (For reference, 6.2 was released on 2007.01.15, with 6.3 on 2008.01.18) >From then, go half way again either forwards or backwards, to narrow down the window when the problem was introduced - with only eight kernel recompiles you should be able to narrow it down to a one-day window, and looking at the spec of the machine you should be able to do that in a morning :). Once you've got it down to a window of a couple of days or less, give csup the "-L 2" option, and it'll give you a list of files changed between dates. Obviously this is dependant on you being able to take one of the affected machines down for a few hours, but if you can, this may well be the quickest way of establishing when the problem was introduced. Out of interest, what type of hardware is this? Gavin From owner-freebsd-stable@FreeBSD.ORG Wed May 14 18:50:31 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2E516106567F for ; Wed, 14 May 2008 18:50:31 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from hosted.kievnet.com (hosted.kievnet.com [193.138.144.10]) by mx1.freebsd.org (Postfix) with ESMTP id D73558FC22 for ; Wed, 14 May 2008 18:50:30 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from localhost ([127.0.0.1] helo=edge.pp.kiev.ua) by hosted.kievnet.com with esmtpa (Exim 4.62) (envelope-from ) id 1JwM3Z-000KjA-Mq; Wed, 14 May 2008 21:50:29 +0300 Message-ID: <482B3475.6060803@icyb.net.ua> Date: Wed, 14 May 2008 21:50:29 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.12 (X11/20080320) MIME-Version: 1.0 To: freebsd-threads@freebsd.org, freebsd-stable@freebsd.org References: <482B0297.2050300@icyb.net.ua> In-Reply-To: <482B0297.2050300@icyb.net.ua> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: thread scheduling at mutex unlock X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 May 2008 18:50:31 -0000 on 14/05/2008 18:17 Andriy Gapon said the following: > I am trying the small attached program on FreeBSD 6.3 (amd64, > SCHED_4BSD) and 7-STABLE (i386, SCHED_ULE), both with libthr as threads > library and on both it produces "BROKEN" message. > > I compile this program as follows: > cc sched_test.c -o sched_test -pthread > > I believe that the behavior I observe is broken because: if thread #1 > releases a mutex and then tries to re-acquire it while thread #2 was > already blocked waiting on that mutex, then thread #1 should be "queued" > after thread #2 in mutex waiter's list. > > Is there any option (thread scheduler, etc) that I could try to achieve > "good" behavior? > > P.S. I understand that all this is subject to (thread) scheduler policy, > but I think that what I expect is more reasonable, at least it is more > reasonable for my application. > > Daniel Eischen has just kindly notified me that the code (as an attachment) didn't make it to the list, so here it is inline. #include #include #include #include pthread_mutex_t mutex; int count = 0; static void * thrfunc(void * arg) { while (1) { pthread_mutex_lock(&mutex); count++; if (count > 10) { fprintf(stderr, "you have a BROKEN thread scheduler!!!\n"); exit(1); } sleep(1); pthread_mutex_unlock(&mutex); } } int main(void) { pthread_t thr; #if 0 pthread_mutexattr_t attr; pthread_mutexattr_init(&attr); pthread_mutexattr_settype(&attr, PTHREAD_MUTEX_RECURSIVE_NP); pthread_mutex_init(&mutex, &attr); #else pthread_mutex_init(&mutex, NULL); #endif pthread_create(&thr, NULL, thrfunc, NULL); sleep(2); pthread_mutex_lock(&mutex); count = 0; printf("you have good thread scheduler\n"); pthread_mutex_unlock(&mutex); return 0; } -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Wed May 14 20:20:44 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3140E1065670 for ; Wed, 14 May 2008 20:20:44 +0000 (UTC) (envelope-from aragon@phat.za.net) Received: from mail.geek.sh (decoder.geek.sh [196.36.198.81]) by mx1.freebsd.org (Postfix) with ESMTP id D18078FC1B for ; Wed, 14 May 2008 20:20:43 +0000 (UTC) (envelope-from aragon@phat.za.net) Received: by mail.geek.sh (Postfix, from userid 1000) id 77C3C24D26; Wed, 14 May 2008 22:20:42 +0200 (SAST) Date: Wed, 14 May 2008 22:20:42 +0200 From: Aragon Gouveia To: freebsd-stable@freebsd.org Message-ID: <20080514202042.GA23704@phat.za.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i X-Operating-System: FreeBSD 4.10-RELEASE-p2 i386 Subject: instability with gmirror and atacontrol spindown X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 May 2008 20:20:44 -0000 Hi, I eagerly started using atacontrol's new spindown command the other day. There's a gmirror volume running on top of the two disks that get spundown. I find that often when the drives are spun back up to serve a disk request, one of the ata devices times out and my system goes into a never ending loop of retrying. At that point I'm lucky if I'm able to shutdown gracefully. This is what is logged on the console after the disk spin up message: ad8: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly ad8: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly ad8: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly ad8: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly ad8: WARNING - SET_MULTI taskqueue timeout - completing request directly ad8: TIMEOUT - READ_DMA retrying (1 retry left) LBA=20047817 ad8: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly ad8: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly ad8: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly ad8: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly ad8: WARNING - SET_MULTI taskqueue timeout - completing request directly ad8: TIMEOUT - READ_DMA retrying (0 retries left) LBA=20047817 I can only reproduce it when my gmirror volume is running. Any ideas? Thanks, Aragon From owner-freebsd-stable@FreeBSD.ORG Wed May 14 20:35:23 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B78EE1065670 for ; Wed, 14 May 2008 20:35:23 +0000 (UTC) (envelope-from ubm@u-boot-man.de) Received: from mail.upper.net (mail.upper.net [62.75.224.33]) by mx1.freebsd.org (Postfix) with ESMTP id 592EE8FC13 for ; Wed, 14 May 2008 20:35:22 +0000 (UTC) (envelope-from ubm@u-boot-man.de) Received: from ubm.mine.nu (e181035105.adsl.alicedsl.de [85.181.35.105]) (authenticated bits=0) by mail.upper.net (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id m4EKZFAi028998 for ; Wed, 14 May 2008 22:35:17 +0200 Date: Wed, 14 May 2008 22:35:15 +0200 From: Marc "UBM" Bocklet To: freebsd-stable@freebsd.org Message-Id: <20080514223515.84553317.ubm@u-boot-man.de> In-Reply-To: <48291889.8030406@pldrouin.net> References: <48291889.8030406@pldrouin.net> X-Mailer: Sylpheed 2.4.8 (GTK+ 2.12.8; i386-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: Status of ZFS in -stable? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 May 2008 20:35:23 -0000 On Tue, 13 May 2008 00:26:49 -0400 Pierre-Luc Drouin wrote: > Hi, > > I would like to know if the memory allocation problem with zfs has > been fixed in -stable? Is zfs considered to be more "stable" now? > > Thanks! > Pierre-Luc Drouin We just set up a zfs based fileserver in our home. It's accessed via samba and ftp, connected via an em 1gb card. FreeBSD is installed on an 80GB ufs2 disk, the zpool consists of two 750GB disks, set up as raidz (my mistake, mirror would probably have been the better choice). We've been using it for about 2 weeks now and there have been no problems (transferred lots of big and small files off/on it, maxing out disk speed). System is amd64, 4gb of ram. FreeBSD blah 7.0-STABLE-200804 FreeBSD 7.0-STABLE-200804 #0: Thu Apr 10 16:32:11 UTC 2008 root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 Bye Marc -- "A sudden blow: the great wings beating still Above the staggering girl, her thighs caressed By the dark webs, her nape caught in his bill, He holds her helpless breast upon his breast." W.B. Yeats, Leda and the Swan From owner-freebsd-stable@FreeBSD.ORG Wed May 14 21:05:41 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C3273106564A for ; Wed, 14 May 2008 21:05:41 +0000 (UTC) (envelope-from yurtesen@ispro.net) Received: from mail.ispro.net (mail.ispro.net [87.251.0.19]) by mx1.freebsd.org (Postfix) with ESMTP id B16798FC1F for ; Wed, 14 May 2008 21:05:39 +0000 (UTC) (envelope-from yurtesen@ispro.net) Received: (qmail 72311 invoked by uid 399); 14 May 2008 23:36:57 +0300 Received: from dsl-tkubrasgw1-fed0de00-174.dhcp.inet.fi (HELO ?80.222.208.174?) (yurtesen@ispro.net@80.222.208.174) by mail.ispro.net with ESMTPAM; 14 May 2008 23:36:57 +0300 X-Originating-IP: 80.222.208.174 Message-ID: <482B4DEE.3050705@ispro.net> Date: Wed, 14 May 2008 23:39:10 +0300 From: Evren Yurtesen User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Approaching the limit on PV entries, consider increasing either the vm.pmap.shpgperproc or the vm.pmap.pv_entry_max sysctl. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 May 2008 21:05:41 -0000 Hello, I have a FreeBSD 7.0-STABLE amd64 box which gives this message with apache 2.2 very often. Previously the contents of the box was on 6.3-STABLE x86 and I had no such problems. This started right away when we moved to 7, 64bit. FreeBSD web.XXXXX.com 7.0-STABLE FreeBSD 7.0-STABLE #0: Tue Apr 22 02:13:30 UTC 2008 yurtesen@web.XXXXX.com:/usr/obj/usr/src/sys/WEB amd64 Approaching the limit on PV entries, consider increasing either the vm.pmap.shpgperproc or the vm.pmap.pv_entry_max sysctl. Approaching the limit on PV entries, consider increasing either the vm.pmap.shpgperproc or the vm.pmap.pv_entry_max sysctl. I have increased vm.pmap.shpgperproc to 2000 and this seemed to stop complaints for a little while but they occur again... ipcs -a return nothing web:/root#ipcs -a Message Queues: T ID KEY MODE OWNER GROUP CREATOR CGROUP CBYTES QNUM QBYTES LSPID LRPID STIME RTIME CTIME Shared Memory: T ID KEY MODE OWNER GROUP CREATOR CGROUP NATTCH SEGSZ CPID LPID ATIME DTIME CTIME Semaphores: T ID KEY MODE OWNER GROUP CREATOR CGROUP NSEMS OTIME CTIME web:/root# Here are the active sysctl values: vm.pmap.pmap_collect_active: 0 vm.pmap.pmap_collect_inactive: 0 vm.pmap.pv_entry_spare: 7366 vm.pmap.pv_entry_allocs: 93953399357 vm.pmap.pv_entry_frees: 93953160939 vm.pmap.pc_chunk_tryfail: 0 vm.pmap.pc_chunk_frees: 559631374 vm.pmap.pc_chunk_allocs: 559632837 vm.pmap.pc_chunk_count: 1463 vm.pmap.pv_entry_count: 238418 vm.pmap.shpgperproc: 2000 vm.pmap.pv_entry_max: 13338058 The box is lightly loaded, it is an 8 core box with load average about 0.2-0.4 Any ideas about what to check/do next? I only could find a post which suggests using: kern.ipc.shm_use_phys: 1 But I already set it and it has no effect...box has 4gb of memory: CPU: 0.1% user, 0.0% nice, 0.0% system, 0.0% interrupt, 99.9% idle Mem: 180M Active, 1584M Inact, 467M Wired, 131M Cache, 214M Buf, 1578M Free Swap: 8192M Total, 8548K Used, 8184M Free I have the following in make.conf CPUTYPE?=core2 CFLAGS= -O2 -fno-strict-aliasing -pipe CXXFLAGS+= -fconserve-space COPTFLAGS= -O -pipe NO_GAMES=true NO_PROFILE=true WITHOUT_X11=true below is the kernel config file: cpu HAMMER ident WEB options SCHED_ULE # ULE scheduler options PREEMPTION # Enable kernel thread preemption options INET # InterNETworking #options INET6 # IPv6 communications protocols #options SCTP # Stream Control Transmission Protocol options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_DIRHASH # Improve performance on big directories options UFS_GJOURNAL # Enable gjournal-based UFS journaling options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS # Pseudo-filesystem framework options GEOM_PART_GPT # GUID Partition Tables. options GEOM_LABEL # Provides labelization options COMPAT_43TTY # BSD 4.3 TTY compat [KEEP THIS!] options COMPAT_IA32 # Compatible with i386 binaries options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options COMPAT_FREEBSD5 # Compatible with FreeBSD5 options COMPAT_FREEBSD6 # Compatible with FreeBSD6 options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options STACK # stack(9) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV # install a CDEV entry in /dev options ADAPTIVE_GIANT # Giant mutex is adaptive. options STOP_NMI # Stop CPUS using NMI instead of IPI #options AUDIT # Security event auditing # Make an SMP-capable kernel by default options SMP # Symmetric MultiProcessor Kernel # CPU frequency control device cpufreq # Bus support. device acpi device pci # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives options ATA_STATIC_ID # Static device numbering # SCSI peripherals device scbus # SCSI bus (required for SCSI) device da # Direct Access (disks) device cd # CD device pass # Passthrough device (direct SCSI access) #device ses # SCSI Environmental Services (and SAF-TE) # RAID controllers interfaced to the SCSI subsystem device twa # 3ware 9000 series PATA/SATA RAID # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device kbdmux # keyboard multiplexer device vga # VGA video card driver device splash # Splash screen and screen saver support # syscons is the default console driver, resembling an SCO console device sc device agp # support several AGP chipsets # PCI Ethernet NICs. device em # Intel PRO/1000 adapter Gigabit Ethernet Card device ixgb # Intel PRO/10GbE Ethernet Card # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support device dc # DEC/Intel 21143 and various workalikes device fxp # Intel EtherExpress PRO/100B (82557, 82558) device re # RealTek 8139C+/8169/8169S/8110S device rl # RealTek 8129/8139 device sk # SysKonnect SK-984x & SK-982x gigabit Ethernet device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') # Pseudo devices. device loop # Network loopback device random # Entropy device device ether # Ethernet support device pty # Pseudo-ttys (telnet etc) device firmware # firmware assist module # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! # Note that 'bpf' is required for DHCP. device bpf # Berkeley packet filter # USB support device uhci # UHCI PCI->USB interface device ohci # OHCI PCI->USB interface device ehci # EHCI PCI->USB interface (USB 2.0) device usb # USB Bus (required) device ugen # Generic device uhid # "Human Interface Devices" device ukbd # Keyboard device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse # My Additions # Statically Link in accept filters options ACCEPT_FILTER_DATA options ACCEPT_FILTER_HTTP # Other Devices & Options device snp #Snoop device - to look at pty/vty/etc.. Any ideas on what might be going on? Thanks, Evren From owner-freebsd-stable@FreeBSD.ORG Thu May 15 00:40:37 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0BD65106568A; Thu, 15 May 2008 00:40:37 +0000 (UTC) (envelope-from davids@webmaster.com) Received: from mail1.webmaster.com (mail1.webmaster.com [216.152.64.169]) by mx1.freebsd.org (Postfix) with ESMTP id EC26A8FC0C; Thu, 15 May 2008 00:40:36 +0000 (UTC) (envelope-from davids@webmaster.com) Received: from however by webmaster.com (MDaemon.PRO.v8.1.3.R) with ESMTP id md50002051997.msg; Wed, 14 May 2008 17:30:53 -0700 From: "David Schwartz" To: , Date: Wed, 14 May 2008 17:29:30 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) Importance: Normal In-Reply-To: <482B0297.2050300@icyb.net.ua> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 X-Authenticated-Sender: joelkatz@webmaster.com X-Spam-Processed: mail1.webmaster.com, Wed, 14 May 2008 17:30:53 -0700 (not processed: message from trusted or authenticated source) X-MDRemoteIP: 206.171.168.138 X-Return-Path: davids@webmaster.com X-MDAV-Processed: mail1.webmaster.com, Wed, 14 May 2008 17:30:54 -0700 Cc: Subject: RE: thread scheduling at mutex unlock X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: davids@webmaster.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2008 00:40:37 -0000 > I am trying the small attached program on FreeBSD 6.3 (amd64, > SCHED_4BSD) and 7-STABLE (i386, SCHED_ULE), both with libthr as = threads > library and on both it produces "BROKEN" message. >=20 > I compile this program as follows: > cc sched_test.c -o sched_test -pthread >=20 > I believe that the behavior I observe is broken because: if thread #1 > releases a mutex and then tries to re-acquire it while thread #2 was > already blocked waiting on that mutex, then thread #1 should be = "queued" > after thread #2 in mutex waiter's list. >=20 > Is there any option (thread scheduler, etc) that I could try to = achieve > "good" behavior? >=20 > P.S. I understand that all this is subject to (thread) scheduler = policy, > but I think that what I expect is more reasonable, at least it is more > reasonable for my application. >=20 > --=20 > Andriy Gapon Are you out of your mind?! You are specifically asking for the absolute = worst possible behavior! If you have fifty tiny things to do on one side of the room and fifty = tiny things to do on the other side, do you cross the room after each = one? Of course not. That would be *ludicrous*. If you want/need strict alternation, feel free to code it. But it's the = maximally inefficient scheduler behavior, and it sure as hell had better = not be the default. DS From owner-freebsd-stable@FreeBSD.ORG Thu May 15 01:00:28 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A45491065680 for ; Thu, 15 May 2008 01:00:28 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 9A3B68FC24 for ; Thu, 15 May 2008 01:00:28 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 806EF1CC038; Wed, 14 May 2008 18:00:28 -0700 (PDT) Date: Wed, 14 May 2008 18:00:28 -0700 From: Jeremy Chadwick To: Aragon Gouveia Message-ID: <20080515010028.GA84942@eos.sc1.parodius.com> References: <20080514202042.GA23704@phat.za.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080514202042.GA23704@phat.za.net> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-stable@freebsd.org Subject: Re: instability with gmirror and atacontrol spindown X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2008 01:00:28 -0000 On Wed, May 14, 2008 at 10:20:42PM +0200, Aragon Gouveia wrote: > This is what is logged on the console after the disk spin up message: > > ad8: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing > request directly > ad8: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing > request directly > ad8: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing > request directly > ad8: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing > request directly > ad8: WARNING - SET_MULTI taskqueue timeout - completing request directly > ad8: TIMEOUT - READ_DMA retrying (1 retry left) LBA=20047817 > ad8: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing > request directly > ad8: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing > request directly > ad8: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing > request directly > ad8: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing > request directly > ad8: WARNING - SET_MULTI taskqueue timeout - completing request directly > ad8: TIMEOUT - READ_DMA retrying (0 retries left) LBA=20047817 > > > I can only reproduce it when my gmirror volume is running. > > Any ideas? http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Thu May 15 01:03:47 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D79691065673 for ; Thu, 15 May 2008 01:03:47 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id CC5B98FC15 for ; Thu, 15 May 2008 01:03:47 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id C161C1CC038; Wed, 14 May 2008 18:03:47 -0700 (PDT) Date: Wed, 14 May 2008 18:03:47 -0700 From: Jeremy Chadwick To: Evren Yurtesen Message-ID: <20080515010347.GA85202@eos.sc1.parodius.com> References: <482B4DEE.3050705@ispro.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <482B4DEE.3050705@ispro.net> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-stable@freebsd.org Subject: Re: Approaching the limit on PV entries, consider increasing either the vm.pmap.shpgperproc or the vm.pmap.pv_entry_max sysctl. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2008 01:03:47 -0000 On Wed, May 14, 2008 at 11:39:10PM +0300, Evren Yurtesen wrote: > Approaching the limit on PV entries, consider increasing either the > vm.pmap.shpgperproc or the vm.pmap.pv_entry_max sysctl. > Approaching the limit on PV entries, consider increasing either the > vm.pmap.shpgperproc or the vm.pmap.pv_entry_max sysctl. I've seen this message on one of our i386 RELENG_7 boxes, which has a medium load (webserver with PHP) and 2GB RAM. Our counters, for comparison: vm.pmap.pmap_collect_active: 0 vm.pmap.pmap_collect_inactive: 0 vm.pmap.pv_entry_spare: 7991 vm.pmap.pv_entry_allocs: 807863761 vm.pmap.pv_entry_frees: 807708792 vm.pmap.pc_chunk_tryfail: 0 vm.pmap.pc_chunk_frees: 2580082 vm.pmap.pc_chunk_allocs: 2580567 vm.pmap.pc_chunk_count: 485 vm.pmap.pv_entry_count: 154969 vm.pmap.shpgperproc: 200 vm.pmap.pv_entry_max: 1745520 -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Thu May 15 04:20:46 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5BB081065670; Thu, 15 May 2008 04:20:46 +0000 (UTC) (envelope-from davidxu@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 4D7668FC12; Thu, 15 May 2008 04:20:46 +0000 (UTC) (envelope-from davidxu@freebsd.org) Received: from apple.my.domain (root@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m4F4Kgel097586; Thu, 15 May 2008 04:20:43 GMT (envelope-from davidxu@freebsd.org) Message-ID: <482BBA77.8000704@freebsd.org> Date: Thu, 15 May 2008 12:22:15 +0800 From: David Xu User-Agent: Thunderbird 2.0.0.9 (X11/20071211) MIME-Version: 1.0 To: Andriy Gapon References: <482B0297.2050300@icyb.net.ua> In-Reply-To: <482B0297.2050300@icyb.net.ua> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, freebsd-threads@freebsd.org Subject: Re: thread scheduling at mutex unlock X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2008 04:20:46 -0000 Andriy Gapon wrote: > I am trying the small attached program on FreeBSD 6.3 (amd64, > SCHED_4BSD) and 7-STABLE (i386, SCHED_ULE), both with libthr as threads > library and on both it produces "BROKEN" message. > > I compile this program as follows: > cc sched_test.c -o sched_test -pthread > > I believe that the behavior I observe is broken because: if thread #1 > releases a mutex and then tries to re-acquire it while thread #2 was > already blocked waiting on that mutex, then thread #1 should be "queued" > after thread #2 in mutex waiter's list. > > Is there any option (thread scheduler, etc) that I could try to achieve > "good" behavior? > > P.S. I understand that all this is subject to (thread) scheduler policy, > but I think that what I expect is more reasonable, at least it is more > reasonable for my application. > In fact, libthr is trying to avoid this conveying, if thread #1 hands off the ownership to thread #2, it will cause lots of context switch, in the idea world, I would let thread #1 to run until it exhausts its time slice, and at the end of its time slices, thread #2 will get the mutex ownership, of course it is difficult to make this work on SMP, but on UP, I would expect the result will be close enough if thread scheduler is sane, so we don't raise priority in kernel umtx code if a thread is blocked, this gives thread #1 some times to re-acquire the mutex without context switches, increases throughput. Regards, David Xu From owner-freebsd-stable@FreeBSD.ORG Thu May 15 05:56:59 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1EEA81065673; Thu, 15 May 2008 05:56:59 +0000 (UTC) (envelope-from b.j.casavant@ieee.org) Received: from yeppers.tdkt.org (skyline.tdkt.org [209.98.211.67]) by mx1.freebsd.org (Postfix) with ESMTP id BBA2A8FC1B; Thu, 15 May 2008 05:56:58 +0000 (UTC) (envelope-from b.j.casavant@ieee.org) Received: from [192.168.0.29] (c-98-240-155-201.hsd1.mn.comcast.net [98.240.155.201]) (authenticated bits=0) by yeppers.tdkt.org (8.12.11/8.12.11/erikj-OpenBSD) with ESMTP id m4F5GKo8015883; Thu, 15 May 2008 00:16:21 -0500 (CDT) Date: Thu, 15 May 2008 00:16:14 -0500 (CDT) From: Brent Casavant X-X-Sender: bcasavan@ella.local To: Andriy Gapon In-Reply-To: <482B0297.2050300@icyb.net.ua> Message-ID: References: <482B0297.2050300@icyb.net.ua> User-Agent: Alpine 1.10 (OSX 962 2008-03-14) Organization: "Angeltread Software Organization" MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-stable@freebsd.org, freebsd-threads@freebsd.org Subject: Re: thread scheduling at mutex unlock X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Brent Casavant List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2008 05:56:59 -0000 On Wed, 14 May 2008, Andriy Gapon wrote: > I believe that the behavior I observe is broken because: if thread #1 > releases a mutex and then tries to re-acquire it while thread #2 was > already blocked waiting on that mutex, then thread #1 should be "queued" > after thread #2 in mutex waiter's list. The behavior of scheduling with respect to mutex contention (apart from pthread_mutexattr_setprotocol()) is not specified by POSIX, to the best of my knowledge, and thus is left to the discretion of the implementation. > Is there any option (thread scheduler, etc) that I could try to achieve > "good" behavior? No portable mechanism, and not any mechanism in the operating systems with which I am familiar. That said, as the behavior is not specified by POSIX, there would be nothing preventing an implementation from providing this as an optional behavior through a custom pthread_mutexattr_???_np() interface. > P.S. I understand that all this is subject to (thread) scheduler policy, > but I think that what I expect is more reasonable, at least it is more > reasonable for my application. As other responders have indicated, the behavior you desire is as unoptimal as possible for the general case. If your application would truly benefit from this sort of queuing behavior, I'd suggest that either you need to implement your own mechanism to accomplish the queueing (probably the easier fix), or that the threading architecture of your application could be designed in a different manner that avoids this problem (probably the more difficult fix). Brent -- Brent Casavant Dance like everybody should be watching. www.angeltread.org KD5EMB, EN34lv From owner-freebsd-stable@FreeBSD.ORG Thu May 15 07:06:30 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 718301065682 for ; Thu, 15 May 2008 07:06:30 +0000 (UTC) (envelope-from bazzoola@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.176]) by mx1.freebsd.org (Postfix) with ESMTP id 281268FC1A for ; Thu, 15 May 2008 07:06:29 +0000 (UTC) (envelope-from bazzoola@gmail.com) Received: by py-out-1112.google.com with SMTP id u52so226631pyb.10 for ; Thu, 15 May 2008 00:06:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:cc:message-id:from:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer; bh=G4sfzhUd5hkiybeypaT1W7ihF5lioncpHNhzUwqY1W8=; b=teSconE4h3zWWwq761Jp71Dp5mrKLO9mwcHOMhUlT/OAfMnEckaxaYTTxdrdY8sL8Xta31ZE8gehXTCeVJOy8UgvcxLoXRfCgPzOuAqvAHw/d8Xp1nYOKcg13UJfS/xwHjPHWOEY8FdoVMXevN973Jterr+hpqdw0nnr61cpqMI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=cc:message-id:from:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer; b=ZrFFPTA4kiWUdLhEgVDAeZc/HTc/AQ7RFip6TGOJFi8c9jEIG238US22ODdD3ovc0bjlUDD0btV//9mg5/n1kRvZWOT460wHKXK3SpDZMoDUCACQQcNp3K7BxIUAalsddP0oypMMY4BfCsCEzfiLNkIQPr2F9gz5nRuoshmF4DU= Received: by 10.64.232.16 with SMTP id e16mr2727557qbh.86.1210835189278; Thu, 15 May 2008 00:06:29 -0700 (PDT) Received: from ?10.0.1.111? ( [99.147.176.243]) by mx.google.com with ESMTPS id f13sm2964919qba.1.2008.05.15.00.06.28 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 15 May 2008 00:06:28 -0700 (PDT) Message-Id: <6601D6DC-AD09-4028-A25A-59899C9A57E4@gmail.com> From: bazzoola To: freebsd-stable In-Reply-To: <20080513054223.2CAC95B4B@mail.bitblocks.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v919.2) Date: Thu, 15 May 2008 03:06:25 -0400 References: <20080513054223.2CAC95B4B@mail.bitblocks.com> X-Mailer: Apple Mail (2.919.2) Cc: maho@freebsd.org Subject: Auto bridge for qemu network [was: kqemu support: not compiled] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2008 07:06:30 -0000 Thanks for updating the port! I have few suggestions: #cat /etc/rc.conf [...] #KQEMU for qemu kqemu_enable="YES" #Bridge for qemu cloned_interfaces="bridge0" ifconfig_bridge0="up addm sk0" autobridge_interfaces="bridge0" autobridge_bridge0="tap*" This should take care of the network connection between qemu virtual host and the host instead of doing it manually. Assuming that qemu is using tap and the default "if" on the host is sk0. Also, is it possible to update this page, it has some outdated info: http://people.freebsd.org/~maho/qemu/qemu.html *It is the 1st answer from google when asked "freebsd qemu" From owner-freebsd-stable@FreeBSD.ORG Thu May 15 07:17:04 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EED48106566B for ; Thu, 15 May 2008 07:17:04 +0000 (UTC) (envelope-from yurtesen@ispro.net) Received: from mail.ispro.net (mail.ispro.net [87.251.0.19]) by mx1.freebsd.org (Postfix) with ESMTP id 0644A8FC19 for ; Thu, 15 May 2008 07:17:02 +0000 (UTC) (envelope-from yurtesen@ispro.net) Received: (qmail 88745 invoked by uid 399); 15 May 2008 10:14:15 +0300 Received: from dsl-tkubrasgw1-fed0de00-174.dhcp.inet.fi (HELO ?80.222.208.174?) (yurtesen@ispro.net@80.222.208.174) by mail.ispro.net with ESMTPAM; 15 May 2008 10:14:15 +0300 X-Originating-IP: 80.222.208.174 Message-ID: <482BE398.8010203@ispro.net> Date: Thu, 15 May 2008 10:17:44 +0300 From: Evren Yurtesen User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: Jeremy Chadwick References: <482B4DEE.3050705@ispro.net> <20080515010347.GA85202@eos.sc1.parodius.com> In-Reply-To: <20080515010347.GA85202@eos.sc1.parodius.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: Approaching the limit on PV entries, consider increasing either the vm.pmap.shpgperproc or the vm.pmap.pv_entry_max sysctl. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2008 07:17:05 -0000 Jeremy Chadwick wrote: > On Wed, May 14, 2008 at 11:39:10PM +0300, Evren Yurtesen wrote: >> Approaching the limit on PV entries, consider increasing either the >> vm.pmap.shpgperproc or the vm.pmap.pv_entry_max sysctl. >> Approaching the limit on PV entries, consider increasing either the >> vm.pmap.shpgperproc or the vm.pmap.pv_entry_max sysctl. > > I've seen this message on one of our i386 RELENG_7 boxes, which has a > medium load (webserver with PHP) and 2GB RAM. Our counters, for > comparison: > > vm.pmap.pmap_collect_active: 0 > vm.pmap.pmap_collect_inactive: 0 > vm.pmap.pv_entry_spare: 7991 > vm.pmap.pv_entry_allocs: 807863761 > vm.pmap.pv_entry_frees: 807708792 > vm.pmap.pc_chunk_tryfail: 0 > vm.pmap.pc_chunk_frees: 2580082 > vm.pmap.pc_chunk_allocs: 2580567 > vm.pmap.pc_chunk_count: 485 > vm.pmap.pv_entry_count: 154969 > vm.pmap.shpgperproc: 200 > vm.pmap.pv_entry_max: 1745520 > I guess one good question is, how can one see the number of PV entries used by a process? shouldnt these appear in the output of ipcs -a command? Another good question is, in many places there is references to rebooting after putting a new vm.pmap.shpgperproc value to loader.conf. However I just changed this on a running system, has it really been changed or was I suppose to reboot? In either case, I already increased vm.pmap.shpgperproc to 2000 (from 200) and still the error occurs, there is not so much load on this box, maybe there is a leak somewhere? Thanks, Evren From owner-freebsd-stable@FreeBSD.ORG Thu May 15 08:36:02 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3676B1065671; Thu, 15 May 2008 08:36:02 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from hosted.kievnet.com (hosted.kievnet.com [193.138.144.10]) by mx1.freebsd.org (Postfix) with ESMTP id E3CA38FC21; Thu, 15 May 2008 08:36:01 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from localhost ([127.0.0.1] helo=edge.pp.kiev.ua) by hosted.kievnet.com with esmtpa (Exim 4.62) (envelope-from ) id 1JwYwR-0000Oz-IH; Thu, 15 May 2008 11:35:59 +0300 Message-ID: <482BF5EA.5010806@icyb.net.ua> Date: Thu, 15 May 2008 11:35:54 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.12 (X11/20080320) MIME-Version: 1.0 To: David Xu , Brent Casavant References: <482B0297.2050300@icyb.net.ua> <482BBA77.8000704@freebsd.org> In-Reply-To: <482BBA77.8000704@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, freebsd-threads@freebsd.org Subject: Re: thread scheduling at mutex unlock X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2008 08:36:02 -0000 on 15/05/2008 07:22 David Xu said the following: > In fact, libthr is trying to avoid this conveying, if thread #1 > hands off the ownership to thread #2, it will cause lots of context > switch, in the idea world, I would let thread #1 to run until it > exhausts its time slice, and at the end of its time slices, > thread #2 will get the mutex ownership, of course it is difficult to > make this work on SMP, but on UP, I would expect the result will > be close enough if thread scheduler is sane, so we don't raise > priority in kernel umtx code if a thread is blocked, this gives > thread #1 some times to re-acquire the mutex without context switches, > increases throughput. Brent, David, thank you for the responses. I think I incorrectly formulated my original concern. It is not about behavior at mutex unlock but about behavior at mutex re-lock. You are right that waking waiters at unlock would hurt performance. But I think that it is not "fair" that at re-lock former owner gets the lock immediately and the thread that waited on it for longer time doesn't get a chance. Here's a more realistic example than the mock up code. Say you have a worker thread that processes queued requests and the load is such that there is always something on the queue. Thus the worker thread doesn't ever have to block waiting on it. And let's say that there is a GUI thread that wants to convey some information to the worker thread. And for that it needs to acquire some mutex and "do something". With current libthr behavior the GUI thread would never have a chance to get the mutex as worker thread would always be a winner (as my small program shows). Or even more realistic: there should be a feeder thread that puts things on the queue, it would never be able to enqueue new items until the queue becomes empty if worker thread's code looks like the following: while(1) { pthread_mutex_lock(&work_mutex); while(queue.is_empty()) pthread_cond_wait(...); //dequeue item ... pthread_mutex_unlock(&work mutex); //perform some short and non-blocking processing of the item ... } Because the worker thread (while the queue is not empty) would never enter cond_wait and would always re-lock the mutex shortly after unlocking it. So while improving performance on small scale this mutex re-acquire-ing unfairness may be hurting interactivity and thread concurrency and thus performance in general. E.g. in the above example queue would always be effectively of depth 1. Something about "lock starvation" comes to mind. So, yes, this is not about standards, this is about reasonable expectations about thread concurrency behavior in a particular implementation (libthr). I see now that performance advantage of libthr over libkse came with a price. I think that something like queued locks is needed. They would clearly reduce raw throughput performance, so maybe that should be a new (non-portable?) mutex attribute. -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Thu May 15 08:51:55 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AD2C4106564A; Thu, 15 May 2008 08:51:55 +0000 (UTC) (envelope-from marcolz@stack.nl) Received: from mx1.stack.nl (meestal-mk5.stack.nl [IPv6:2001:610:1108:5010::149]) by mx1.freebsd.org (Postfix) with ESMTP id 705D48FC12; Thu, 15 May 2008 08:51:55 +0000 (UTC) (envelope-from marcolz@stack.nl) Received: from toad.stack.nl (toad.stack.nl [IPv6:2001:610:1108:5010::135]) by mx1.stack.nl (Postfix) with ESMTP id 4CE093F6FD; Thu, 15 May 2008 10:51:54 +0200 (CEST) Received: by toad.stack.nl (Postfix, from userid 333) id 495FF4117; Thu, 15 May 2008 10:51:54 +0200 (CEST) Date: Thu, 15 May 2008 10:51:54 +0200 From: Marc Olzheim To: bug-followup@FreeBSD.org, martin@bnc.ch Message-ID: <20080515085154.GA72314@stack.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: FreeBSD toad.stack.nl 6.3-PRERELEASE FreeBSD 6.3-PRERELEASE User-Agent: Mutt/1.5.13 (2006-08-11) Cc: freebsd-stable@freebsd.org Subject: Re: bin/40278: mktime returns -1 for certain dates/timezones when it should normalize X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2008 08:51:55 -0000 With the testcode I put on http://www.stack.nl/~marcolz/FreeBSD/pr-bin-40278/40278.c I can reproduce it on FreeBSD 4.11: output on 4.11-STABLE ------ Init: mktime: 1014944400 Fri Mar 1 02:00:00 CET 2002 1: mktime: 4294967295 Fri Apr 0 02:00:00 CET 2002 Init: mktime: 1014944400 Fri Mar 1 02:00:00 CET 2002 2a: mktime: 1017622800 Mon Apr 1 03:00:00 CEST 2002 2b: mktime: 1017536400 Sun Mar 31 03:00:00 CEST 2002 Init: mktime: 1014944400 Fri Mar 1 02:00:00 CET 2002 3a: mktime: 1014858000 Thu Feb 28 02:00:00 CET 2002 3b: mktime: 1017277200 Thu Mar 28 02:00:00 CET 2002 ------ But it is fixed on my FreeBSD 6.x and up systems: output on 6.3-PRERELEASE: ------ Init: mktime: 1014944400 Fri Mar 1 02:00:00 CET 2002 1: mktime: 1017536400 Sun Mar 31 03:00:00 CEST 2002 Init: mktime: 1014944400 Fri Mar 1 02:00:00 CET 2002 2a: mktime: 1017622800 Mon Apr 1 03:00:00 CEST 2002 2b: mktime: 1017536400 Sun Mar 31 03:00:00 CEST 2002 Init: mktime: 1014944400 Fri Mar 1 02:00:00 CET 2002 3a: mktime: 1014858000 Thu Feb 28 02:00:00 CET 2002 3b: mktime: 1017277200 Thu Mar 28 02:00:00 CET 2002 ------ So it looks like it has been fixed in the mean time and that this PR can be closed. Marc From owner-freebsd-stable@FreeBSD.ORG Thu May 15 09:01:17 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A669D1065676; Thu, 15 May 2008 09:01:17 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from hosted.kievnet.com (hosted.kievnet.com [193.138.144.10]) by mx1.freebsd.org (Postfix) with ESMTP id 605CC8FC20; Thu, 15 May 2008 09:01:17 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from localhost ([127.0.0.1] helo=edge.pp.kiev.ua) by hosted.kievnet.com with esmtpa (Exim 4.62) (envelope-from ) id 1JwZKt-0001RV-8H; Thu, 15 May 2008 12:01:15 +0300 Message-ID: <482BFBDA.6060705@icyb.net.ua> Date: Thu, 15 May 2008 12:01:14 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.12 (X11/20080320) MIME-Version: 1.0 To: "David Schwartz" References: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, freebsd-threads@freebsd.org Subject: Re: thread scheduling at mutex unlock X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2008 09:01:17 -0000 David Schwartz wrote: > Are you out of your mind?! You are specifically asking for the absolute = > worst possible behavior! > > If you have fifty tiny things to do on one side of the room and fifty = > tiny things to do on the other side, do you cross the room after each = > one? Of course not. That would be *ludicrous*. > > If you want/need strict alternation, feel free to code it. But it's the = > maximally inefficient scheduler behavior, and it sure as hell had better = > not be the default. David, what if you have an infinite number of items on one side and finite number on the other, and you want to process them all (in infinite time, of course). Would you still try to finish everything on one side (the infinite one) or would you try to look at what you have on the other side? I am sorry about fuzzy wording of my original report, I should have mentioned "starvation" somewhere in it. -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Thu May 15 09:04:09 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C18F61065677; Thu, 15 May 2008 09:04:09 +0000 (UTC) (envelope-from davidxu@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id AE6408FC22; Thu, 15 May 2008 09:04:09 +0000 (UTC) (envelope-from davidxu@freebsd.org) Received: from apple.my.domain (root@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m4F945Jv048860; Thu, 15 May 2008 09:04:07 GMT (envelope-from davidxu@freebsd.org) Message-ID: <482BFCE3.7080704@freebsd.org> Date: Thu, 15 May 2008 17:05:39 +0800 From: David Xu User-Agent: Thunderbird 2.0.0.9 (X11/20071211) MIME-Version: 1.0 To: Andriy Gapon References: <482B0297.2050300@icyb.net.ua> <482BBA77.8000704@freebsd.org> <482BF5EA.5010806@icyb.net.ua> In-Reply-To: <482BF5EA.5010806@icyb.net.ua> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Brent Casavant , freebsd-threads@freebsd.org Subject: Re: thread scheduling at mutex unlock X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2008 09:04:09 -0000 Andriy Gapon wrote: > Brent, David, > > thank you for the responses. > I think I incorrectly formulated my original concern. > It is not about behavior at mutex unlock but about behavior at mutex > re-lock. You are right that waking waiters at unlock would hurt > performance. But I think that it is not "fair" that at re-lock former > owner gets the lock immediately and the thread that waited on it for > longer time doesn't get a chance. > > Here's a more realistic example than the mock up code. > Say you have a worker thread that processes queued requests and the load > is such that there is always something on the queue. Thus the worker > thread doesn't ever have to block waiting on it. > And let's say that there is a GUI thread that wants to convey some > information to the worker thread. And for that it needs to acquire some > mutex and "do something". > With current libthr behavior the GUI thread would never have a chance to > get the mutex as worker thread would always be a winner (as my small > program shows). > Or even more realistic: there should be a feeder thread that puts things > on the queue, it would never be able to enqueue new items until the > queue becomes empty if worker thread's code looks like the following: > > while(1) > { > pthread_mutex_lock(&work_mutex); > while(queue.is_empty()) > pthread_cond_wait(...); > //dequeue item > ... > pthread_mutex_unlock(&work mutex); > //perform some short and non-blocking processing of the item > ... > } > > Because the worker thread (while the queue is not empty) would never > enter cond_wait and would always re-lock the mutex shortly after > unlocking it. > > So while improving performance on small scale this mutex re-acquire-ing > unfairness may be hurting interactivity and thread concurrency and thus > performance in general. E.g. in the above example queue would always be > effectively of depth 1. > Something about "lock starvation" comes to mind. > > So, yes, this is not about standards, this is about reasonable > expectations about thread concurrency behavior in a particular > implementation (libthr). > I see now that performance advantage of libthr over libkse came with a > price. I think that something like queued locks is needed. They would > clearly reduce raw throughput performance, so maybe that should be a new > (non-portable?) mutex attribute. > You forgot that default scheduling policy is time-sharing, after thread #2 has blocked on the mutex for a while, when thread #1 unlocks the mutex and unblocks thread #1, the thread #2's priority will be raised and it preempts thread #1, the thread #2 then acquires the mutex, that's how it balances between fairness and performance. Regards, David Xu From owner-freebsd-stable@FreeBSD.ORG Thu May 15 09:27:36 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2568B106567D; Thu, 15 May 2008 09:27:36 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from hosted.kievnet.com (hosted.kievnet.com [193.138.144.10]) by mx1.freebsd.org (Postfix) with ESMTP id CF9818FC12; Thu, 15 May 2008 09:27:35 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from localhost ([127.0.0.1] helo=edge.pp.kiev.ua) by hosted.kievnet.com with esmtpa (Exim 4.62) (envelope-from ) id 1JwZkM-0003Fi-NM; Thu, 15 May 2008 12:27:34 +0300 Message-ID: <482C0206.1050206@icyb.net.ua> Date: Thu, 15 May 2008 12:27:34 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.12 (X11/20080320) MIME-Version: 1.0 To: David Xu References: <482B0297.2050300@icyb.net.ua> <482BBA77.8000704@freebsd.org> <482BF5EA.5010806@icyb.net.ua> <482BFCE3.7080704@freebsd.org> In-Reply-To: <482BFCE3.7080704@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Brent Casavant , freebsd-threads@freebsd.org Subject: Re: thread scheduling at mutex unlock X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2008 09:27:36 -0000 on 15/05/2008 12:05 David Xu said the following: > Andriy Gapon wrote: > >> Brent, David, >> >> thank you for the responses. >> I think I incorrectly formulated my original concern. >> It is not about behavior at mutex unlock but about behavior at mutex >> re-lock. You are right that waking waiters at unlock would hurt >> performance. But I think that it is not "fair" that at re-lock former >> owner gets the lock immediately and the thread that waited on it for >> longer time doesn't get a chance. >> >> Here's a more realistic example than the mock up code. >> Say you have a worker thread that processes queued requests and the >> load is such that there is always something on the queue. Thus the >> worker thread doesn't ever have to block waiting on it. >> And let's say that there is a GUI thread that wants to convey some >> information to the worker thread. And for that it needs to acquire >> some mutex and "do something". >> With current libthr behavior the GUI thread would never have a chance >> to get the mutex as worker thread would always be a winner (as my >> small program shows). >> Or even more realistic: there should be a feeder thread that puts >> things on the queue, it would never be able to enqueue new items until >> the queue becomes empty if worker thread's code looks like the following: >> >> while(1) >> { >> pthread_mutex_lock(&work_mutex); >> while(queue.is_empty()) >> pthread_cond_wait(...); >> //dequeue item >> ... >> pthread_mutex_unlock(&work mutex); >> //perform some short and non-blocking processing of the item >> ... >> } >> >> Because the worker thread (while the queue is not empty) would never >> enter cond_wait and would always re-lock the mutex shortly after >> unlocking it. >> >> So while improving performance on small scale this mutex >> re-acquire-ing unfairness may be hurting interactivity and thread >> concurrency and thus performance in general. E.g. in the above example >> queue would always be effectively of depth 1. >> Something about "lock starvation" comes to mind. >> >> So, yes, this is not about standards, this is about reasonable >> expectations about thread concurrency behavior in a particular >> implementation (libthr). >> I see now that performance advantage of libthr over libkse came with a >> price. I think that something like queued locks is needed. They would >> clearly reduce raw throughput performance, so maybe that should be a >> new (non-portable?) mutex attribute. >> > > You forgot that default scheduling policy is time-sharing, after thread > #2 has blocked on the mutex for a while, when thread #1 unlocks the > mutex and unblocks thread #1, the thread #2's priority will be raised > and it preempts thread #1, the thread #2 then acquires the mutex, > that's how it balances between fairness and performance. Maybe. But that's not what I see with my small example program. One thread releases and re-acquires a mutex 10 times in a row while the other doesn't get it a single time. I think that there is a very slim chance of a blocked thread preempting a running thread in this circumstances. Especially if execution time between unlock and re-lock is very small. I'd rather prefer to have an option to have FIFO fairness in mutex lock rather than always avoiding context switch at all costs and depending on scheduler to eventually do priority magic. -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Thu May 15 09:29:45 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 13F29106564A for ; Thu, 15 May 2008 09:29:45 +0000 (UTC) (envelope-from nb@ravenbrook.com) Received: from raven.ravenbrook.com (raven.ravenbrook.com [193.164.110.8]) by mx1.freebsd.org (Postfix) with ESMTP id 6F49F8FC1C for ; Thu, 15 May 2008 09:29:44 +0000 (UTC) (envelope-from nb@ravenbrook.com) Received: from thrush.ravenbrook.com (thrush.ravenbrook.com [193.164.110.145]) by raven.ravenbrook.com (8.13.8/8.13.8) with ESMTP id m4F9E1cB080108 for ; Thu, 15 May 2008 10:14:01 +0100 (BST) (envelope-from nb@ravenbrook.com) Received: from thrush.ravenbrook.com (localhost [127.0.0.1]) by thrush.ravenbrook.com (8.13.4/8.13.4) with ESMTP id m4F9E1CA060282 for ; Thu, 15 May 2008 10:14:01 +0100 (BST) (envelope-from nb@thrush.ravenbrook.com) From: Nick Barnes To: freebsd-stable@freebsd.org Date: Thu, 15 May 2008 10:14:01 +0100 Message-ID: <60281.1210842841@thrush.ravenbrook.com> Sender: nb@ravenbrook.com X-Virus-Scanned: ClamAV 0.92.1/6882/Tue Apr 22 18:33:01 2008 on raven.ravenbrook.com X-Virus-Status: Clean X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on raven.ravenbrook.com X-Spam-Level: X-Spam-Status: No, score=-2.7 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, URIBL_BLACK autolearn=no version=3.2.3 Subject: syslog console log not logging SCSI problems X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2008 09:29:45 -0000 One of our FreeBSD boxes has a SCSI controller and disk, which showed problems earlier this week. There was a lot of of chatter from the SCSI driver in /var/log/messages and to the console. However, the console is unattended and we only discovered the problem subsequently because /var/log/console.log didn't show any of the chatter. console.log is otherwise working, and very helpful (e.g. it shows /etc/rc output at boot which lets us spot daemon failures). We've rebuilt the machine now (fan failure leading to boot disk failure), so I can't report the SCSI chatter in question, but here is the dmesg and syslog.conf. Any suggestions? (yes, I know this is 6.2-RELEASE; I'm partway through cvsupping; the failure was under 6.2p11). Thanks in advance, Nick Barnes dmesg: Copyright (c) 1992-2007 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 6.2-RELEASE #0: Fri Jan 12 11:05:30 UTC 2007 root@dessler.cse.buffalo.edu:/usr/obj/usr/src/sys/SMP Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 3.00GHz (3006.01-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf4a Stepping = 10 Features=0xbfebfbff Features2=0x649d> AMD Features=0x20100000 AMD Features2=0x1 Logical CPUs per core: 2 real memory = 2137440256 (2038 MB) avail memory = 2086498304 (1989 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 2 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 cpu0: on acpi0 acpi_perf0: on cpu0 acpi_perf0: failed in PERF_STATUS attach device_attach: acpi_perf0 attach returned 6 acpi_perf0: on cpu0 acpi_perf0: failed in PERF_STATUS attach device_attach: acpi_perf0 attach returned 6 cpu1: on acpi0 acpi_perf1: on cpu1 acpi_perf1: failed in PERF_STATUS attach device_attach: acpi_perf1 attach returned 6 acpi_perf1: on cpu1 acpi_perf1: failed in PERF_STATUS attach device_attach: acpi_perf1 attach returned 6 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: at device 2.0 (no driver attached) pci0: at device 27.0 (no driver attached) pcib1: at device 28.0 on pci0 pci1: on pcib1 pcib2: at device 28.2 on pci0 pci2: on pcib2 pcib3: at device 28.3 on pci0 pci3: on pcib3 uhci0: port 0x2080-0x209f irq 23 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0x2060-0x207f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0x2040-0x205f irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhci3: port 0x2020-0x203f irq 16 at device 29.3 on pci0 uhci3: [GIANT-LOCKED] usb3: on uhci3 usb3: USB revision 1.0 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered ehci0: mem 0x901c4000-0x901c43ff irq 23 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: on ehci0 usb4: USB revision 2.0 uhub4: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub4: 8 ports with 8 removable, self powered pcib4: at device 30.0 on pci0 pci4: on pcib4 ahc0: port 0x1000-0x10ff mem 0x90000000-0x90000fff irq 21 at device 0.0 on pci4 ahc0: [GIANT-LOCKED] aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs fxp0: port 0x1100-0x113f mem 0x90001000-0x90001fff irq 20 at device 8.0 on pci4 miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:16:76:1c:01:2f isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x20b0-0x20bf irq 18 at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 atapci1: port 0x20c8-0x20cf,0x20ec-0x20ef,0x20c0-0x20c7,0x20e8-0x20eb,0x20a0-0x20af irq 19 at device 31.2 on pci0 ata2: on atapci1 ata3: on atapci1 pci0: at device 31.3 (no driver attached) ppc0: port 0x378-0x37f,0x778-0x77f irq 7 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A pmtimer0 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec acd0: CDROM at ata0-master UDMA33 ad4: 238475MB at ata2-master SATA150 Waiting 5 seconds for SCSI devices to settle da0 at ahc0 bus 0 target 6 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 160.000MB/s transfers (80.000MHz, offset 127, 16bit), Tagged Queueing Enabled da0: 35074MB (71833096 512 byte sectors: 255H 63S/T 4471C) SMP: AP CPU #1 Launched! Trying to mount root from ufs:/dev/ad4s1a syslog.conf: # $FreeBSD: src/etc/syslog.conf,v 1.28 2005/03/12 12:31:16 glebius Exp $ # # Spaces ARE valid field separators in this file. However, # other *nix-like systems still insist on using tabs as field # separators. If you are sharing this file between systems, you # may want to use only tabs as field separators here. # Consult the syslog.conf(5) manpage. *.err;kern.warning;auth.notice;mail.crit /dev/console *.notice;authpriv.none;kern.debug;lpr.info;mail.crit;news.err /var/log/messages security.*;auth.* /var/log/security auth.info;authpriv.info /var/log/auth.log mail.info /var/log/maillog lpr.info /var/log/lpd-errs ftp.info /var/log/xferlog cron.* /var/log/cron *.=debug /var/log/debug.log *.emerg * console.* /var/log/console.log # uncomment this to enable logging of all log messages to /var/log/all.log # touch /var/log/all.log and chmod it to mode 600 before it will work #*.* /var/log/all.log # uncomment this to enable logging to a remote loghost named loghost #*.* @loghost # uncomment these if you're running inn # news.crit /var/log/news/news.crit # news.err /var/log/news/news.err # news.notice /var/log/news/news.notice !startslip *.* /var/log/slip.log !ppp *.* /var/log/ppp.log From owner-freebsd-stable@FreeBSD.ORG Thu May 15 09:46:33 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 27F701065673 for ; Thu, 15 May 2008 09:46:33 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 17BFB8FC16 for ; Thu, 15 May 2008 09:46:32 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id E55411CC038; Thu, 15 May 2008 02:46:32 -0700 (PDT) Date: Thu, 15 May 2008 02:46:32 -0700 From: Jeremy Chadwick To: Nick Barnes Message-ID: <20080515094632.GA2738@eos.sc1.parodius.com> References: <60281.1210842841@thrush.ravenbrook.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <60281.1210842841@thrush.ravenbrook.com> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-stable@freebsd.org Subject: Re: syslog console log not logging SCSI problems X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2008 09:46:33 -0000 On Thu, May 15, 2008 at 10:14:01AM +0100, Nick Barnes wrote: > One of our FreeBSD boxes has a SCSI controller and disk, which showed > problems earlier this week. There was a lot of of chatter from the > SCSI driver in /var/log/messages and to the console. However, the > console is unattended and we only discovered the problem subsequently > because /var/log/console.log didn't show any of the chatter. > > console.log is otherwise working, and very helpful (e.g. it shows > /etc/rc output at boot which lets us spot daemon failures). > > We've rebuilt the machine now (fan failure leading to boot disk > failure), so I can't report the SCSI chatter in question, but here is > the dmesg and syslog.conf. Any suggestions? /boot/loader.conf, /boot.config, and /etc/make.conf would also be useful. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Thu May 15 09:52:40 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2916B1065670; Thu, 15 May 2008 09:52:40 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from smtp8.yandex.ru (smtp8.yandex.ru [213.180.200.213]) by mx1.freebsd.org (Postfix) with ESMTP id 473AD8FC38; Thu, 15 May 2008 09:52:39 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from ns.kirov.so-cdu.ru ([77.72.136.145]:19184 "EHLO [127.0.0.1]" smtp-auth: "bu7cher" TLS-CIPHER: "DHE-RSA-AES256-SHA keybits 256/256 version TLSv1/SSLv3" TLS-PEER-CN1: ) by mail.yandex.ru with ESMTP id S7455954AbYEOJwd (ORCPT + 1 other); Thu, 15 May 2008 13:52:33 +0400 X-Yandex-Spam: 1 X-Yandex-Front: smtp8 X-Yandex-TimeMark: 1210845153 X-MsgDayCount: 3 X-Comment: RFC 2476 MSA function at smtp8.yandex.ru logged sender identity as: bu7cher Message-ID: <482C07DE.3090504@yandex.ru> Date: Thu, 15 May 2008 13:52:30 +0400 From: "Andrey V. Elsukov" User-Agent: Mozilla Thunderbird 1.5 (FreeBSD/20051231) MIME-Version: 1.0 To: Vivek Khera References: <04EA1C34-AB7D-4A85-8A91-DED03E987706@khera.org> In-Reply-To: <04EA1C34-AB7D-4A85-8A91-DED03E987706@khera.org> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-ipfw@freebsd.org, FreeBSD Stable Subject: Re: how much memory does increasing max rules for IPFW take up? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2008 09:52:40 -0000 Vivek Khera wrote: > I had a box run out of dynamic state space yesterday. I found I can > increase the number of dynamic rules by increasing the sysctl parameter > net.inet.ip.fw.dyn_max. I can't find, however, how this affects memory > usage on the system. Is it dyanamically allocated and de-allocated, or > is it a static memory buffer? Each dynamic rule allocated dynamically. Be careful, too many dynamic rules will work very slow. -- WBR, Andrey V. Elsukov From owner-freebsd-stable@FreeBSD.ORG Thu May 15 09:55:53 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 45312106564A for ; Thu, 15 May 2008 09:55:53 +0000 (UTC) (envelope-from nb@ravenbrook.com) Received: from raven.ravenbrook.com (raven.ravenbrook.com [193.164.110.8]) by mx1.freebsd.org (Postfix) with ESMTP id CBA958FC12 for ; Thu, 15 May 2008 09:55:52 +0000 (UTC) (envelope-from nb@ravenbrook.com) Received: from thrush.ravenbrook.com (thrush.ravenbrook.com [193.164.110.145]) by raven.ravenbrook.com (8.13.8/8.13.8) with ESMTP id m4F9toJh081211; Thu, 15 May 2008 10:55:50 +0100 (BST) (envelope-from nb@ravenbrook.com) Received: from thrush.ravenbrook.com (localhost [127.0.0.1]) by thrush.ravenbrook.com (8.13.4/8.13.4) with ESMTP id m4F9toOe060462; Thu, 15 May 2008 10:55:50 +0100 (BST) (envelope-from nb@thrush.ravenbrook.com) From: Nick Barnes To: Jeremy Chadwick In-Reply-To: <20080515094632.GA2738@eos.sc1.parodius.com> from Jeremy Chadwick of "Thu, 15 May 2008 02:46:32 -0700" Date: Thu, 15 May 2008 10:55:50 +0100 Message-ID: <60461.1210845350@thrush.ravenbrook.com> Sender: nb@ravenbrook.com X-Virus-Scanned: ClamAV 0.92.1/6882/Tue Apr 22 18:33:01 2008 on raven.ravenbrook.com X-Virus-Status: Clean X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on raven.ravenbrook.com X-Spam-Level: X-Spam-Status: No, score=-3.7 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.3 Cc: freebsd-stable@FreeBSD.org Subject: Re: syslog console log not logging SCSI problems X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2008 09:55:53 -0000 At 2008-05-15 09:46:32+0000, Jeremy Chadwick writes: > On Thu, May 15, 2008 at 10:14:01AM +0100, Nick Barnes wrote: > > One of our FreeBSD boxes has a SCSI controller and disk, which showed > > problems earlier this week. There was a lot of of chatter from the > > SCSI driver in /var/log/messages and to the console. However, the > > console is unattended and we only discovered the problem subsequently > > because /var/log/console.log didn't show any of the chatter. > > > > console.log is otherwise working, and very helpful (e.g. it shows > > /etc/rc output at boot which lets us spot daemon failures). > > > > We've rebuilt the machine now (fan failure leading to boot disk > > failure), so I can't report the SCSI chatter in question, but here is > > the dmesg and syslog.conf. Any suggestions? > > /boot/loader.conf, /boot.config, and /etc/make.conf would also be > useful. All empty, except setting kern.maxdsiz in /boot/loader.conf. Running GENERIC. If this happens again, I will retain a copy of /var/log/messages so I can report the SCSI messages in question, but they aren't as interesting to me as the fact that they didn't appear in console.log. Nick B From owner-freebsd-stable@FreeBSD.ORG Thu May 15 10:02:03 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CF133106564A for ; Thu, 15 May 2008 10:02:03 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id BDA1F8FC15 for ; Thu, 15 May 2008 10:02:03 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id AE6571CC05B; Thu, 15 May 2008 03:02:03 -0700 (PDT) Date: Thu, 15 May 2008 03:02:03 -0700 From: Jeremy Chadwick To: Nick Barnes Message-ID: <20080515100203.GA3303@eos.sc1.parodius.com> References: <20080515094632.GA2738@eos.sc1.parodius.com> <60461.1210845350@thrush.ravenbrook.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <60461.1210845350@thrush.ravenbrook.com> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-stable@FreeBSD.org Subject: Re: syslog console log not logging SCSI problems X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2008 10:02:03 -0000 On Thu, May 15, 2008 at 10:55:50AM +0100, Nick Barnes wrote: > At 2008-05-15 09:46:32+0000, Jeremy Chadwick writes: > > On Thu, May 15, 2008 at 10:14:01AM +0100, Nick Barnes wrote: > > > One of our FreeBSD boxes has a SCSI controller and disk, which showed > > > problems earlier this week. There was a lot of of chatter from the > > > SCSI driver in /var/log/messages and to the console. However, the > > > console is unattended and we only discovered the problem subsequently > > > because /var/log/console.log didn't show any of the chatter. > > > > > > console.log is otherwise working, and very helpful (e.g. it shows > > > /etc/rc output at boot which lets us spot daemon failures). > > > > > > We've rebuilt the machine now (fan failure leading to boot disk > > > failure), so I can't report the SCSI chatter in question, but here is > > > the dmesg and syslog.conf. Any suggestions? > > > > /boot/loader.conf, /boot.config, and /etc/make.conf would also be > > useful. > > All empty, except setting kern.maxdsiz in /boot/loader.conf. Running > GENERIC. > > If this happens again, I will retain a copy of /var/log/messages so I > can report the SCSI messages in question, but they aren't as > interesting to me as the fact that they didn't appear in console.log. I've seen odd behaviour with syslog before, but it's hard to explain. I don't use the console.info entry in /etc/syslog.conf, so I can't tell you what's going on there. Another thing I can think of would be your kernel configuration. Can you provide it? -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Thu May 15 10:03:56 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 48CE91065674 for ; Thu, 15 May 2008 10:03:56 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id 1AF278FC20 for ; Thu, 15 May 2008 10:03:56 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 781C71095EE; Thu, 15 May 2008 06:03:55 -0400 (EDT) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Thu, 15 May 2008 06:03:55 -0400 X-Sasl-enc: z0HN/iHOGaYXEwZU8WdSfCOJsTWNs5VfURBdU0IO4qd8 1210845835 Received: from empiric.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTPSA id BA0F224E61; Thu, 15 May 2008 06:03:54 -0400 (EDT) Message-ID: <482C0A89.104@FreeBSD.org> Date: Thu, 15 May 2008 11:03:53 +0100 From: "Bruce M. Simpson" User-Agent: Thunderbird 2.0.0.14 (X11/20080514) MIME-Version: 1.0 To: "Andrey V. Elsukov" References: <04EA1C34-AB7D-4A85-8A91-DED03E987706@khera.org> <482C07DE.3090504@yandex.ru> In-Reply-To: <482C07DE.3090504@yandex.ru> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Vivek Khera , FreeBSD Stable , freebsd-ipfw@freebsd.org Subject: Re: how much memory does increasing max rules for IPFW take up? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2008 10:03:56 -0000 Andrey V. Elsukov wrote: > Vivek Khera wrote: >> I had a box run out of dynamic state space yesterday. I found I can >> increase the number of dynamic rules by increasing the sysctl >> parameter net.inet.ip.fw.dyn_max. I can't find, however, how this >> affects memory usage on the system. Is it dyanamically allocated and >> de-allocated, or is it a static memory buffer? > > Each dynamic rule allocated dynamically. Be careful, too many dynamic > rules will work very slow. Got any figures for this? I took a quick glance and it looks like it just uses a hash over dst/src/dport/sport. If there are a lot of raw IP or ICMP flows then that's going to result in hash collisions. It might be a good project for someone to optimize if it isn't scaling for folk. "Bloomier" filters are probably worth a look -- bloom filters are a class of probabilistic hash which may return a false positive, "bloomier" filters are a refinement which tries to limit the false positives. Having said that the default tunable of 256 state entries is probably quite low for use cases other than "home/small office NAT gateway". cheers BMS From owner-freebsd-stable@FreeBSD.ORG Thu May 15 10:21:54 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6D5F51065673; Thu, 15 May 2008 10:21:54 +0000 (UTC) (envelope-from nb@ravenbrook.com) Received: from raven.ravenbrook.com (raven.ravenbrook.com [193.164.110.8]) by mx1.freebsd.org (Postfix) with ESMTP id 8A5458FC0A; Thu, 15 May 2008 10:21:53 +0000 (UTC) (envelope-from nb@ravenbrook.com) Received: from thrush.ravenbrook.com (thrush.ravenbrook.com [193.164.110.145]) by raven.ravenbrook.com (8.13.8/8.13.8) with ESMTP id m4FALpUZ081883; Thu, 15 May 2008 11:21:51 +0100 (BST) (envelope-from nb@ravenbrook.com) Received: from thrush.ravenbrook.com (localhost [127.0.0.1]) by thrush.ravenbrook.com (8.13.4/8.13.4) with ESMTP id m4FALpoK060575; Thu, 15 May 2008 11:21:51 +0100 (BST) (envelope-from nb@thrush.ravenbrook.com) From: Nick Barnes To: Jeremy Chadwick In-Reply-To: <20080515100203.GA3303@eos.sc1.parodius.com> from Jeremy Chadwick of "Thu, 15 May 2008 03:02:03 -0700" Date: Thu, 15 May 2008 11:21:51 +0100 Message-ID: <60574.1210846911@thrush.ravenbrook.com> Sender: nb@ravenbrook.com X-Virus-Scanned: ClamAV 0.92.1/6882/Tue Apr 22 18:33:01 2008 on raven.ravenbrook.com X-Virus-Status: Clean X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on raven.ravenbrook.com X-Spam-Level: X-Spam-Status: No, score=-3.7 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.3 Cc: freebsd-stable@FreeBSD.org Subject: Re: syslog console log not logging SCSI problems X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2008 10:21:54 -0000 At 2008-05-15 10:02:03+0000, Jeremy Chadwick writes: > Another thing I can think of would be your kernel configuration. Can > you provide it? Just GENERIC. By the way, the need to set kern.maxdsiz - for really big processes - doesn't seem to be documented anywhere. I could have sworn it used to be in the Handbook, but I don't see it there. I guess it should be both there and in tuning(7). Rediscovering this switch took me 30 minutes yesterday. Nick B From owner-freebsd-stable@FreeBSD.ORG Thu May 15 12:57:21 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from alona.my.domain (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id DCBE7106566C; Thu, 15 May 2008 12:57:17 +0000 (UTC) (envelope-from davidxu@freebsd.org) Message-ID: <482C3333.1070205@freebsd.org> Date: Thu, 15 May 2008 20:57:23 +0800 From: David Xu User-Agent: Thunderbird 2.0.0.9 (X11/20080323) MIME-Version: 1.0 To: Andriy Gapon References: <482B0297.2050300@icyb.net.ua> <482BBA77.8000704@freebsd.org> <482BF5EA.5010806@icyb.net.ua> <482BFCE3.7080704@freebsd.org> <482C0206.1050206@icyb.net.ua> In-Reply-To: <482C0206.1050206@icyb.net.ua> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Brent Casavant , freebsd-threads@freebsd.org Subject: Re: thread scheduling at mutex unlock X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2008 12:57:21 -0000 Andriy Gapon wrote: > > Maybe. But that's not what I see with my small example program. One > thread releases and re-acquires a mutex 10 times in a row while the > other doesn't get it a single time. > I think that there is a very slim chance of a blocked thread > preempting a running thread in this circumstances. Especially if > execution time between unlock and re-lock is very small. It does not depends on how many times your thread acquires or re-acquires mutex, or how small the region the mutex is protecting. as long as current thread runs too long, other threads will have higher priorities and the ownership definitely will be transfered, though there will be some extra context switchings. > I'd rather prefer to have an option to have FIFO fairness in mutex > lock rather than always avoiding context switch at all costs and > depending on scheduler to eventually do priority magic. > It is better to implement this behavior in your application code, if it is implemented in thread library, you still can not control how many times acquiring and re-acquiring can be allowed for a thread without context switching, a simple FIFO as you said here will cause dreadful performance problem. From owner-freebsd-stable@FreeBSD.ORG Thu May 15 13:45:50 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E57C31065671; Thu, 15 May 2008 13:45:50 +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 97A198FC13; Thu, 15 May 2008 13:45:50 +0000 (UTC) (envelope-from deischen@freebsd.org) 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 m4FDOu6r018326; Thu, 15 May 2008 09:24:56 -0400 (EDT) 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.0 (mail.netplex.net [204.213.176.10]); Thu, 15 May 2008 09:24:56 -0400 (EDT) Date: Thu, 15 May 2008 09:24:56 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Andriy Gapon In-Reply-To: <482BF5EA.5010806@icyb.net.ua> Message-ID: References: <482B0297.2050300@icyb.net.ua> <482BBA77.8000704@freebsd.org> <482BF5EA.5010806@icyb.net.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org, David Xu , Brent Casavant , freebsd-threads@freebsd.org Subject: Re: thread scheduling at mutex unlock X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2008 13:45:51 -0000 On Thu, 15 May 2008, Andriy Gapon wrote: > Or even more realistic: there should be a feeder thread that puts things on > the queue, it would never be able to enqueue new items until the queue > becomes empty if worker thread's code looks like the following: > > while(1) > { > pthread_mutex_lock(&work_mutex); > while(queue.is_empty()) > pthread_cond_wait(...); > //dequeue item > ... > pthread_mutex_unlock(&work mutex); > //perform some short and non-blocking processing of the item > ... > } > > Because the worker thread (while the queue is not empty) would never enter > cond_wait and would always re-lock the mutex shortly after unlocking it. Well in theory, the kernel scheduler will let both threads run fairly with regards to their cpu usage, so this should even out the enqueueing and dequeueing threads. You could also optimize the above a little bit by dequeueing everything in the queue instead of one at a time. > So while improving performance on small scale this mutex re-acquire-ing > unfairness may be hurting interactivity and thread concurrency and thus > performance in general. E.g. in the above example queue would always be > effectively of depth 1. > Something about "lock starvation" comes to mind. > > So, yes, this is not about standards, this is about reasonable expectations > about thread concurrency behavior in a particular implementation (libthr). > I see now that performance advantage of libthr over libkse came with a price. > I think that something like queued locks is needed. They would clearly reduce > raw throughput performance, so maybe that should be a new (non-portable?) > mutex attribute. -- DE From owner-freebsd-stable@FreeBSD.ORG Thu May 15 14:59:06 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EC8ED106564A for ; Thu, 15 May 2008 14:59:06 +0000 (UTC) (envelope-from lightguard.jp@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.31]) by mx1.freebsd.org (Postfix) with ESMTP id A5F688FC12 for ; Thu, 15 May 2008 14:59:06 +0000 (UTC) (envelope-from lightguard.jp@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so258677ywe.13 for ; Thu, 15 May 2008 07:58:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; bh=XOtpxhWaZ7YowKqOQlKeRpAX10MZDml3FJdvw1Y1aKY=; b=d6sR0SZbxWGwlmQb9CTT3bfEkgy9bOyiqgkZGqyZwyt0xmt6DBqO88c6SMrpRSDP2hbXhvHo3L3ww+nHZoHUvRzCTrSebu2eHIo4MrzLDfMWA7Ad1uICFqAEEqVoy4P/yifpVcS5XnvKrGabekB0jsJRB9eWI9tvBAxKgUG1b7Y= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=mw4Oz6QeRxmNWoaggC5lj4UJjHPwL1DQCcxTdmSQcWXGaj5deljXIcKOGhq9UYkV7/THgHxKBgEc2nyFJ6eqfwxi4q4js9oVuADn/iYc6E/rQBpq58z8GUHU14k54N/ocq9knRZzKGmRgk8jF/twUsOsCfRa+jUMu8ffNUsU37Q= Received: by 10.150.197.9 with SMTP id u9mr2329169ybf.83.1210861866760; Thu, 15 May 2008 07:31:06 -0700 (PDT) Received: by 10.150.198.8 with HTTP; Thu, 15 May 2008 07:31:06 -0700 (PDT) Message-ID: <699477f60805150731p1f396bbaj27fc9ed49e69a916@mail.gmail.com> Date: Thu, 15 May 2008 08:31:06 -0600 From: "Jason Porter" To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Upgrade path from 5.5? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2008 14:59:07 -0000 I have an old sandbox (obviously if it's 5.5) that I was thinking of upgrading. Is there an upgrade path I should think about taking, or would it be best to backup my /home directory and install from scratch? Note, I'm currently not subscribed to the list. -- --Jason Porter Real Programmers think better when playing Adventure or Rogue. PGP key id: 926CCFF5 PGP fingerprint: 64C2 C078 13A9 5B23 7738 F7E5 1046 C39B 926C CFF5 PGP key available at: keyserver.net, pgp.mit.edu From owner-freebsd-stable@FreeBSD.ORG Thu May 15 15:10:49 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 93E961065670 for ; Thu, 15 May 2008 15:10:49 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from mail-gw0.york.ac.uk (mail-gw0.york.ac.uk [144.32.128.245]) by mx1.freebsd.org (Postfix) with ESMTP id 242128FC21 for ; Thu, 15 May 2008 15:10:48 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from mail-gw6.york.ac.uk (mail-gw6.york.ac.uk [144.32.129.26]) by mail-gw0.york.ac.uk (8.13.6/8.13.6) with ESMTP id m4FFAkDA007037; Thu, 15 May 2008 16:10:46 +0100 (BST) Received: from buffy-128.york.ac.uk ([144.32.128.160] helo=buffy.york.ac.uk) by mail-gw6.york.ac.uk with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1Jwf6U-000399-Fv; Thu, 15 May 2008 16:10:46 +0100 Received: from buffy.york.ac.uk (localhost [127.0.0.1]) by buffy.york.ac.uk (8.14.2/8.14.2) with ESMTP id m4FFAkrs041020; Thu, 15 May 2008 16:10:46 +0100 (BST) (envelope-from gavin@FreeBSD.org) Received: (from ga9@localhost) by buffy.york.ac.uk (8.14.2/8.14.2/Submit) id m4FFAjkh041019; Thu, 15 May 2008 16:10:45 +0100 (BST) (envelope-from gavin@FreeBSD.org) X-Authentication-Warning: buffy.york.ac.uk: ga9 set sender to gavin@FreeBSD.org using -f From: Gavin Atkinson To: Marc Olzheim In-Reply-To: <20080515085154.GA72314@stack.nl> References: <20080515085154.GA72314@stack.nl> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Thu, 15 May 2008 16:10:45 +0100 Message-Id: <1210864245.29891.93.camel@buffy.york.ac.uk> Mime-Version: 1.0 X-Mailer: Evolution 2.10.1 FreeBSD GNOME Team Port X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin@freebsd.org Cc: freebsd-stable@FreeBSD.org Subject: Re: bin/40278: mktime returns -1 for certain dates/timezones when it should normalize X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2008 15:10:49 -0000 On Thu, 2008-05-15 at 10:51 +0200, Marc Olzheim wrote: > With the testcode I put on > http://www.stack.nl/~marcolz/FreeBSD/pr-bin-40278/40278.c I can > reproduce it on FreeBSD 4.11: [snip] > But it is fixed on my FreeBSD 6.x and up systems: [snip] Many thanks for going to the effort of testing this. I've closed the PR. Gavin From owner-freebsd-stable@FreeBSD.ORG Thu May 15 16:09:40 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DC7EF1065670 for ; Thu, 15 May 2008 16:09:40 +0000 (UTC) (envelope-from vivek@khera.org) Received: from yertle.kcilink.com (thingy.kcilink.com [74.92.149.59]) by mx1.freebsd.org (Postfix) with ESMTP id 967EE8FC12 for ; Thu, 15 May 2008 16:09:40 +0000 (UTC) (envelope-from vivek@khera.org) Received: from host-121.int.kcilink.com (host-121.int.kcilink.com [192.168.7.121]) by yertle.kcilink.com (Postfix) with ESMTP id BA0DB8A0AD; Thu, 15 May 2008 12:09:39 -0400 (EDT) Message-Id: <6ADAB997-FAA4-43B8-AB57-3CC4A04F3700@khera.org> From: Vivek Khera To: FreeBSD Stable In-Reply-To: <482C0A89.104@FreeBSD.org> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v919.2) Date: Thu, 15 May 2008 12:09:39 -0400 References: <04EA1C34-AB7D-4A85-8A91-DED03E987706@khera.org> <482C07DE.3090504@yandex.ru> <482C0A89.104@FreeBSD.org> X-Mailer: Apple Mail (2.919.2) Cc: freebsd-ipfw@freebsd.org Subject: Re: how much memory does increasing max rules for IPFW take up? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2008 16:09:40 -0000 On May 15, 2008, at 6:03 AM, Bruce M. Simpson wrote: > Having said that the default tunable of 256 state entries is > probably quite low for use cases other than "home/small office NAT > gateway". The deafult on my systems seems to be 4096. My steady state on a pretty popular web server is about 400, on a busy inbound mail server, around 800 states. I need to account for peaks much higher, though. Luckily most of my connections are short-lived. Thanks for the answers! From owner-freebsd-stable@FreeBSD.ORG Thu May 15 16:20:56 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7D0751065670 for ; Thu, 15 May 2008 16:20:56 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 6791D8FC23 for ; Thu, 15 May 2008 16:20:56 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 567891CC038; Thu, 15 May 2008 09:20:56 -0700 (PDT) Date: Thu, 15 May 2008 09:20:56 -0700 From: Jeremy Chadwick To: "Bruce M. Simpson" Message-ID: <20080515162056.GA17187@eos.sc1.parodius.com> References: <04EA1C34-AB7D-4A85-8A91-DED03E987706@khera.org> <482C07DE.3090504@yandex.ru> <482C0A89.104@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <482C0A89.104@FreeBSD.org> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: Vivek Khera , "Andrey V. Elsukov" , FreeBSD Stable , freebsd-ipfw@freebsd.org Subject: Re: how much memory does increasing max rules for IPFW take up? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2008 16:20:56 -0000 On Thu, May 15, 2008 at 11:03:53AM +0100, Bruce M. Simpson wrote: > Andrey V. Elsukov wrote: >> Vivek Khera wrote: >>> I had a box run out of dynamic state space yesterday. I found I can >>> increase the number of dynamic rules by increasing the sysctl parameter >>> net.inet.ip.fw.dyn_max. I can't find, however, how this affects memory >>> usage on the system. Is it dyanamically allocated and de-allocated, or >>> is it a static memory buffer? >> >> Each dynamic rule allocated dynamically. Be careful, too many dynamic >> rules will work very slow. > > Got any figures for this? I took a quick glance and it looks like it just > uses a hash over dst/src/dport/sport. If there are a lot of raw IP or ICMP > flows then that's going to result in hash collisions. > > It might be a good project for someone to optimize if it isn't scaling for > folk. "Bloomier" filters are probably worth a look -- bloom filters are a > class of probabilistic hash which may return a false positive, "bloomier" > filters are a refinement which tries to limit the false positives. > > Having said that the default tunable of 256 state entries is probably quite > low for use cases other than "home/small office NAT gateway". It's far too low for home/small office. Standard Linux NAT routers, such as the Linksys WRT54G/GL, come with a default state table count of 2048, and often is increased by third-party firmwares to 8192 based on justified necessity. Search for "conntrack" below: http://www.polarcloud.com/firmware 256 can easily be exhausted by more than one user loading multiple HTTP 1.0 web pages at one time (such is the case with many users now have browsers that load 7-8 web pages into separate tabs during startup). And if that's not enough reason, consider torrents, which is quite often what results in a home or office router exhausting its state table. Bottom line: the 256 default is too low. It needs to be increased to at least 2048. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Thu May 15 16:33:25 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B5FF1106564A for ; Thu, 15 May 2008 16:33:25 +0000 (UTC) (envelope-from serg@tmn.ru) Received: from sbtx.tmn.ru (relay.tmn.ru [212.76.160.49]) by mx1.freebsd.org (Postfix) with ESMTP id 0DE7B8FC1A for ; Thu, 15 May 2008 16:33:24 +0000 (UTC) (envelope-from serg@tmn.ru) X-Bogosity: Ham, spamicity=0.000000 Received: from sv.tech.sibitex.tmn.ru (sv.tech.sibitex.tmn.ru [10.76.160.59]) by sbtx.tmn.ru (8.13.8/8.13.8) with ESMTP id m4FGEa5b012189; Thu, 15 May 2008 22:14:40 +0600 (YEKST) (envelope-from serg@tmn.ru) Received: from sv.tech.sibitex.tmn.ru (localhost.tech.sibitex.tmn.ru [127.0.0.1]) by sv.tech.sibitex.tmn.ru (8.14.2/8.14.2) with ESMTP id m4FGEaXT052757; Thu, 15 May 2008 22:14:36 +0600 (YEKST) (envelope-from serg@sv.tech.sibitex.tmn.ru) Received: (from serg@localhost) by sv.tech.sibitex.tmn.ru (8.14.2/8.14.2/Submit) id m4FGEaOQ052756; Thu, 15 May 2008 22:14:36 +0600 (YEKST) (envelope-from serg) Date: Thu, 15 May 2008 22:14:36 +0600 From: "Sergey N. Voronkov" To: Jason Porter Message-ID: <20080515161436.GA52741@tmn.ru> References: <699477f60805150731p1f396bbaj27fc9ed49e69a916@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <699477f60805150731p1f396bbaj27fc9ed49e69a916@mail.gmail.com> User-Agent: Mutt/1.4.2.3i X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (sbtx.tmn.ru [10.0.160.49]); Thu, 15 May 2008 22:14:40 +0600 (YEKST) X-Virus-Scanned: ClamAV version 0.93, clamav-milter version 0.93 on sbtx.tmn.ru X-Virus-Status: Clean Cc: freebsd-stable@freebsd.org Subject: Re: Upgrade path from 5.5? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2008 16:33:25 -0000 On Thu, May 15, 2008 at 08:31:06AM -0600, Jason Porter wrote: > I have an old sandbox (obviously if it's 5.5) that I was thinking of > upgrading. Is there an upgrade path I should think about taking, or would > it be best to backup my /home directory and install from scratch? Note, I'm > currently not subscribed to the list. Source upgrade 5.5 -> 6.2 -> 6.3 works fine for me. Serg N. Voronkov, Sibitex JSC. From owner-freebsd-stable@FreeBSD.ORG Thu May 15 17:39:38 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AF5501065677 for ; Thu, 15 May 2008 17:39:38 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from angel.ticketswitch.com (angel.ticketswitch.com [IPv6:2002:57e0:1d4e::1]) by mx1.freebsd.org (Postfix) with ESMTP id 6C7A48FC19 for ; Thu, 15 May 2008 17:39:38 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from [10.50.50.2] (helo=smaug.rattatosk) by angel.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1JwhQW-0007YX-So for stable@freebsd.org; Thu, 15 May 2008 18:39:36 +0100 Received: from dilbert.rattatosk ([10.50.50.6] helo=dilbert.ticketswitch.com) by smaug.rattatosk with esmtp (Exim 4.69 (FreeBSD)) (envelope-from ) id 1JwhQW-0003h5-JA for stable@freebsd.org; Thu, 15 May 2008 18:39:36 +0100 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1JwhQW-000L1H-IE for stable@freebsd.org; Thu, 15 May 2008 18:39:36 +0100 To: stable@freebsd.org Message-Id: From: Pete French Date: Thu, 15 May 2008 18:39:36 +0100 Cc: Subject: cron hanging on to child processes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2008 17:39:38 -0000 I have a process which is run daily from cron that stops mysql, does some stuff, and starts it again. The scriput outputs a number of lines which are emailed to me in the output of the cron job. What I have noticed is that my emials actually lag by a day - it turns out that the cron job appears to not send the email until mysql is sut down the following day. I can only assume that when mysql is restarted, cron sees it as a child process, and thus does not terminate until that process does. Which happens when a new cron job shuts it down again 24 hours later. Any suggestions on fixing this ? I wouldn't have thought that stopping and starting a daemon was a particularly unusual thing to want to do from a cron job. -pete. From owner-freebsd-stable@FreeBSD.ORG Thu May 15 17:54:12 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C715E1065675; Thu, 15 May 2008 17:54:12 +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 315A58FC13; Thu, 15 May 2008 17:54:12 +0000 (UTC) (envelope-from deischen@freebsd.org) 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 m4FHs9OF006254; Thu, 15 May 2008 13:54:10 -0400 (EDT) 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.0 (mail.netplex.net [204.213.176.10]); Thu, 15 May 2008 13:54:11 -0400 (EDT) Date: Thu, 15 May 2008 13:54:09 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Andriy Gapon In-Reply-To: Message-ID: References: <482B0297.2050300@icyb.net.ua> <482BBA77.8000704@freebsd.org> <482BF5EA.5010806@icyb.net.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org, David Xu , Brent Casavant , freebsd-threads@freebsd.org Subject: Re: thread scheduling at mutex unlock X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2008 17:54:12 -0000 On Thu, 15 May 2008, Daniel Eischen wrote: > On Thu, 15 May 2008, Andriy Gapon wrote: > >> Or even more realistic: there should be a feeder thread that puts things on >> the queue, it would never be able to enqueue new items until the queue >> becomes empty if worker thread's code looks like the following: >> >> while(1) >> { >> pthread_mutex_lock(&work_mutex); >> while(queue.is_empty()) >> pthread_cond_wait(...); >> //dequeue item >> ... >> pthread_mutex_unlock(&work mutex); >> //perform some short and non-blocking processing of the item >> ... >> } >> >> Because the worker thread (while the queue is not empty) would never enter >> cond_wait and would always re-lock the mutex shortly after unlocking it. > > Well in theory, the kernel scheduler will let both threads run fairly > with regards to their cpu usage, so this should even out the enqueueing > and dequeueing threads. > > You could also optimize the above a little bit by dequeueing everything > in the queue instead of one at a time. I suppose you could also enforce your own scheduling with something like the following: pthread_cond_t writer_cv; pthread_cond_t reader_cv; pthread_mutex_t q_mutex; ... thingy_q_t thingy_q; int writers_waiting = 0; int readers_waiting = 0; ... void enqueue(thingy_t *thingy) { pthread_mutex_lock(q_mutex); /* Insert into thingy q */ ... if (readers_waiting > 0) { pthread_cond_broadcast(&reader_cv, &q_mutex); readers_waiting = 0; } while (thingy_q.size > ENQUEUE_THRESHOLD_HIGH) { writers_waiting++; pthread_cond_wait(&writer_cv, &q_mutex); } pthread_mutex_unlock(&q_mutex); } thingy_t * dequeue(void) { thingy_t *thingy; pthread_mutex_lock(&q_mutex); while (thingy_q.size == 0) { readers_waiting++; pthread_cond_wait(&reader_cv, &q_mutex); } /* Dequeue thingy */ ... if ((writers_waiting > 0) && thingy_q.size < ENQUEUE_THRESHOLD_LOW)) { /* Wakeup the writers. */ pthread_cond_broadcast(&writer_cv, &q_mutex); writers_waiting = 0; } pthread_mutex_unlock(&q_mutex); return (thingy); } The above is completely untested and probably contains some bugs ;-) You probably shouldn't need anything like that if the kernel scheduler is scheduling your threads fairly. -- DE From owner-freebsd-stable@FreeBSD.ORG Thu May 15 19:30:18 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 08F541065674; Thu, 15 May 2008 19:30:18 +0000 (UTC) (envelope-from davids@webmaster.com) Received: from mail1.webmaster.com (mail1.webmaster.com [216.152.64.169]) by mx1.freebsd.org (Postfix) with ESMTP id E30928FC12; Thu, 15 May 2008 19:30:17 +0000 (UTC) (envelope-from davids@webmaster.com) Received: from however by webmaster.com (MDaemon.PRO.v8.1.3.R) with ESMTP id md50002053351.msg; Thu, 15 May 2008 12:30:37 -0700 From: "David Schwartz" To: Date: Thu, 15 May 2008 12:29:13 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: <482BFBDA.6060705@icyb.net.ua> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 X-Authenticated-Sender: joelkatz@webmaster.com X-Spam-Processed: mail1.webmaster.com, Thu, 15 May 2008 12:30:37 -0700 (not processed: message from trusted or authenticated source) X-MDRemoteIP: 206.171.168.138 X-Return-Path: davids@webmaster.com X-MDAV-Processed: mail1.webmaster.com, Thu, 15 May 2008 12:30:38 -0700 Cc: freebsd-stable@freebsd.org, freebsd-threads@freebsd.org Subject: RE: thread scheduling at mutex unlock X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: davids@webmaster.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2008 19:30:18 -0000 > what if you have an infinite number of items on one side and finite=20 > number on the other, and you want to process them all (in infinite = time,=20 > of course). Would you still try to finish everything on one side (the=20 > infinite one) or would you try to look at what you have on the other = side? >=20 > I am sorry about fuzzy wording of my original report, I should have=20 > mentioned "starvation" somewhere in it. There is no such thing as a "fair share" when comparing an infinite = quantity to a finite quantity. It is just as sensible to do 1 then 1 as = 10 then 10 or a billion then 1. What I would do in this case is work on one side for one timeslice then = the other side for one timeslice, continuuing until either side was = finished, then I'd work exclusively on the other side. This is precisely = the purpose for having timeslices in a scheduler. The timeslice is carefully chosen so that it's not so long that you = ignore a side for too long. It's also carefully chosen so that it's not = so short that you spend all your time switching swides. What sane schedulers do is assume that you want to make as much forward = progress as quickly as possible. This means getting as many work units = done per unit time as possible. This means as few context switches as = possible. A scheduler that switches significantly more often than once per = timeslice with a load like this is *broken*. The purpose of the = timeslice is to place an upper bound on the number of context switches = in cases where forward progress can be made on more than one process. An = ideal scheduler would not switch more often than once per timeslice = unless it could not make further forward progress. Real-world schedulers actually may allow one side to pre-empt the other, = and may switch a bit more often than a scheduler that's "ideal" in the = sense described above. This is done in an attempt to boost interactive = performance. But your basic assumption that strict alternation is desirable is = massively wrong. That's the *worst* *possible* outcome. DS From owner-freebsd-stable@FreeBSD.ORG Thu May 15 19:51:27 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2BB9E1065675; Thu, 15 May 2008 19:51:27 +0000 (UTC) (envelope-from b.j.casavant@ieee.org) Received: from yeppers.tdkt.org (skyline.tdkt.org [209.98.211.67]) by mx1.freebsd.org (Postfix) with ESMTP id A7C588FC13; Thu, 15 May 2008 19:51:26 +0000 (UTC) (envelope-from b.j.casavant@ieee.org) Received: from pkunk.americas.sgi.com (cfcafwp.sgi.com [192.48.179.6]) (authenticated bits=0) by yeppers.tdkt.org (8.12.11/8.12.11/erikj-OpenBSD) with ESMTP id m4FJpKq2014745; Thu, 15 May 2008 14:51:23 -0500 (CDT) Date: Thu, 15 May 2008 14:51:08 -0500 (CDT) From: Brent Casavant X-X-Sender: bcasavan@pkunk.americas.sgi.com To: Andriy Gapon In-Reply-To: <482BF5EA.5010806@icyb.net.ua> Message-ID: References: <482B0297.2050300@icyb.net.ua> <482BBA77.8000704@freebsd.org> <482BF5EA.5010806@icyb.net.ua> User-Agent: Alpine 1.10 (BSF 962 2008-03-14) Organization: "Angeltread Software Organization" MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-stable@freebsd.org, David Xu , freebsd-threads@freebsd.org Subject: Re: thread scheduling at mutex unlock X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Brent Casavant List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2008 19:51:27 -0000 On Thu, 15 May 2008, Andriy Gapon wrote: > With current libthr behavior the GUI thread would never have a chance to get > the mutex as worker thread would always be a winner (as my small program > shows). The example you gave indicates an incorrect mechanism being used for the GUI to communicate with this worker thread. For the behavior you desire, you need a common condition that lets both the GUI and the work item generator indicate that there is something for the worker to do, *and* you need seperate mechanisms for the GUI and work item generator to add to their respective queues. Something like this (could be made even better with a little effor): struct worker_queues_s { pthread_mutex_t work_mutex; struct work_queue_s work_queue; pthread_mutex_t gui_mutex; struct gui_queue_s gui_queue; pthread_mutex_t stuff_mutex; int stuff_todo; pthread_cond_t stuff_cond; }; struct worker_queue_s wq; int main(int argc, char *argv[]) { // blah blah init_worker_queue(&wq); // blah blah } void gui_callback(...) { // blah blah // Set up GUI message pthread_mutex_lock(&wq.gui_mutex); // Add GUI message to queue pthread_mutex_unlock(&wq.gui_mutex); pthread_mutex_lock(&wq.stuff_mutex); wq.stuff_todo++; pthread_cond_signal(&wq.stuff_cond); pthread_mutex_unlock(&wq.stuff_mutex); // blah blah } void* work_generator_thread(void*) { // blah blah while (1) { // Set up work to do pthread_mutex_lock(&wq.work_mutex); // Add work item to queue pthread_mutex_unlock(&wq.work_mutex); pthread_mutex_lock(&wq.stuff_mutex); wq.stuff_todo++; pthread_cond_signal(&wq.stuff_cond); pthread_mutex_unlock(&wq.stuff_mutex); } // blah blah } void* worker_thread(void* arg) { // blah blah while (1) { // Wait for there to be something to do pthread_mutex_lock(&wq.stuff_mutex); while (wq.stuff_todo < 1) { pthread_cond_wait(&wq.stuff_cond, &wq.stuff_mutex); } pthread_mutex_unlock(&wq.stuff_mutex); // Handle GUI messages pthread_mutex_lock(&wq.gui_mutex); while (!gui_queue_empty(&wq.gui_queue) { // dequeue and process GUI messages pthread_mutex_lock(&wq.stuff_mutex); wq.stuff_todo--; pthread_mutex_unlock(&wq.stuff_mutex); } pthread_mutex_unlock(&wq.gui_mutex); // Handle work items pthread_mutex_lock(&wq.work_mutex); while (!work_queue_empty(&wq.work_queue)) { // dequeue and process work item pthread_mutex_lock(&wq.stuff_mutex); wq.stuff_todo--; pthread_mutex_unlock(&wq.stuff_mutex); } pthread_mutex_unlock(&wq.work_mutex); } // blah blah } This should accomplish what you desire. Caution that I haven't compiled, run, or tested it, but I'm pretty sure it's a solid solution. The key here is unifying the two input sources (the GUI and work queues) without blocking on either one of them individually. The value of (wq.stuff_todo < 1) becomes a proxy for the value of (gui_queue_empty(...) && work_queue_empty(...)). I hope that helps, Brent -- Brent Casavant Dance like everybody should be watching. www.angeltread.org KD5EMB, EN34lv From owner-freebsd-stable@FreeBSD.ORG Thu May 15 20:26:38 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8A3AC1065674; Thu, 15 May 2008 20:26:38 +0000 (UTC) (envelope-from davids@webmaster.com) Received: from mail1.webmaster.com (mail1.webmaster.com [216.152.64.169]) by mx1.freebsd.org (Postfix) with ESMTP id 6EF218FC12; Thu, 15 May 2008 20:26:37 +0000 (UTC) (envelope-from davids@webmaster.com) Received: from however by webmaster.com (MDaemon.PRO.v8.1.3.R) with ESMTP id md50002053397.msg; Thu, 15 May 2008 13:27:23 -0700 From: "David Schwartz" To: "David Xu" , "Brent Casavant" Date: Thu, 15 May 2008 13:25:59 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: <482BF5EA.5010806@icyb.net.ua> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 X-Authenticated-Sender: joelkatz@webmaster.com X-Spam-Processed: mail1.webmaster.com, Thu, 15 May 2008 13:27:23 -0700 (not processed: message from trusted or authenticated source) X-MDRemoteIP: 206.171.168.138 X-Return-Path: davids@webmaster.com X-MDAV-Processed: mail1.webmaster.com, Thu, 15 May 2008 13:27:25 -0700 Cc: freebsd-stable@freebsd.org, freebsd-threads@freebsd.org Subject: RE: thread scheduling at mutex unlock X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: davids@webmaster.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2008 20:26:38 -0000 > Brent, David, > > thank you for the responses. > I think I incorrectly formulated my original concern. > It is not about behavior at mutex unlock but about behavior at mutex > re-lock. You are right that waking waiters at unlock would hurt > performance. But I think that it is not "fair" that at re-lock former > owner gets the lock immediately and the thread that waited on it for > longer time doesn't get a chance. You are correct, but fairness is not the goal, performance is. If you want fairness, you are welcome to code it. But threads don't file union grievances, and it would be absolute foolishness for a scheduler to sacrifice performance to make threads happier. The scheduler decides which thread runs, you decide what the running thread does. You are expected to use your control over that latter part to exercise whatever your application notion of "fairness" is. Your test program is a classic example of a case where the use of a mutex is inappropriate. > Here's a more realistic example than the mock up code. > Say you have a worker thread that processes queued requests and the load > is such that there is always something on the queue. Thus the worker > thread doesn't ever have to block waiting on it. > And let's say that there is a GUI thread that wants to convey some > information to the worker thread. And for that it needs to acquire some > mutex and "do something". > With current libthr behavior the GUI thread would never have a chance to > get the mutex as worker thread would always be a winner (as my small > program shows). Nonsense. The worker thread would be doing work most of the time and wouldn't be holding the mutex. > Or even more realistic: there should be a feeder thread that puts things > on the queue, it would never be able to enqueue new items until the > queue becomes empty if worker thread's code looks like the following: > > while(1) > { > pthread_mutex_lock(&work_mutex); > while(queue.is_empty()) > pthread_cond_wait(...); > //dequeue item > ... > pthread_mutex_unlock(&work mutex); > //perform some short and non-blocking processing of the item > ... > } > > Because the worker thread (while the queue is not empty) would never > enter cond_wait and would always re-lock the mutex shortly after > unlocking it. So what? The feeder thread could get the mutex after the mutex is unlocked before the worker thread goes to do work. The only reason your test code encountered a "problem" was because you yielded the CPU while you held the mutex and never used up a timeslice. > So while improving performance on small scale this mutex re-acquire-ing > unfairness may be hurting interactivity and thread concurrency and thus > performance in general. E.g. in the above example queue would always be > effectively of depth 1. > Something about "lock starvation" comes to mind. Nope. You have to create a situation where the mutex is held much more often than not held to get this behavior. That's a pathological case where the use of a mutex is known to be inappropriate. > So, yes, this is not about standards, this is about reasonable > expectations about thread concurrency behavior in a particular > implementation (libthr). > I see now that performance advantage of libthr over libkse came with a > price. I think that something like queued locks is needed. They would > clearly reduce raw throughput performance, so maybe that should be a new > (non-portable?) mutex attribute. If you want queued locks, feel free to code them and use them. But you have to work very hard to create a case where they are useful. If you find you're holding the mutex more often than not, you're doing something *very* wrong. DS From owner-freebsd-stable@FreeBSD.ORG Thu May 15 20:48:34 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 611F1106564A; Thu, 15 May 2008 20:48:34 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from hosted.kievnet.com (hosted.kievnet.com [193.138.144.10]) by mx1.freebsd.org (Postfix) with ESMTP id 16F398FC20; Thu, 15 May 2008 20:48:33 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from localhost ([127.0.0.1] helo=edge.pp.kiev.ua) by hosted.kievnet.com with esmtpa (Exim 4.62) (envelope-from ) id 1JwkNJ-000C2s-PY; Thu, 15 May 2008 23:48:29 +0300 Message-ID: <482CA191.1030004@icyb.net.ua> Date: Thu, 15 May 2008 23:48:17 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.12 (X11/20080320) MIME-Version: 1.0 To: David Xu References: <482B0297.2050300@icyb.net.ua> <482BBA77.8000704@freebsd.org> <482BF5EA.5010806@icyb.net.ua> <482BFCE3.7080704@freebsd.org> <482C0206.1050206@icyb.net.ua> <482C3333.1070205@freebsd.org> In-Reply-To: <482C3333.1070205@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Brent Casavant , freebsd-threads@freebsd.org Subject: Re: thread scheduling at mutex unlock X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2008 20:48:34 -0000 on 15/05/2008 15:57 David Xu said the following: > Andriy Gapon wrote: >> >> Maybe. But that's not what I see with my small example program. One >> thread releases and re-acquires a mutex 10 times in a row while the >> other doesn't get it a single time. >> I think that there is a very slim chance of a blocked thread >> preempting a running thread in this circumstances. Especially if >> execution time between unlock and re-lock is very small. > It does not depends on how many times your thread acquires or > re-acquires mutex, or > how small the region the mutex is protecting. as long as current thread > runs too long, > other threads will have higher priorities and the ownership definitely > will be transfered, > though there will be some extra context switchings. David, did you examine or try the small program that I sent before? The "lucky" thread slept for 1 second each time it held mutex. So in total it spent about 8 seconds sleeping and holding the mutex. And the "unlucky" thread, consequently, spent 8 seconds blocked waiting for that mutex. And it didn't get "lucky". Yes, technically the "lucky" thread was not running while holding the mutex, so probably this is why scheduling algorithm didn't immediately work. I did more testing and see that the "unlucky" thread eventually gets a chance (eventually means after very many lock/unlock cycles), but I think that it is penalized too much still. I wonder if with current code it is possible and easy to make this behavior more deterministic. Maybe something like the following: if (oldest_waiter.wait_time < X) do what we do now... else go into kernel for possible switch I have very little idea about unit and value of X. >> I'd rather prefer to have an option to have FIFO fairness in mutex >> lock rather than always avoiding context switch at all costs and >> depending on scheduler to eventually do priority magic. >> > It is better to implement this behavior in your application code, if it > is implemented in thread library, you still can not control how many > times acquiring and re-acquiring can be allowed for a thread without > context switching, a simple FIFO as you said here will cause dreadful > performance problem. I almost agree. But I still wouldn't take your last statement for a fact. "Dreadful performance" - on micro-scale maybe, not necessarily on macro scale. After all, never switching context would be the best performance for a single CPU-bound task, but you wouldn't think that this is the best performance for the whole system. As a data point: it seems that current Linux threading library is not significantly worse than libthr, but my small test program on Fedora 7 works to my expectations. -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Thu May 15 20:51:14 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4B453106567C for ; Thu, 15 May 2008 20:51:14 +0000 (UTC) (envelope-from andrew@modulus.org) Received: from email.octopus.com.au (host-122-100-2-232.octopus.com.au [122.100.2.232]) by mx1.freebsd.org (Postfix) with ESMTP id 0C2998FC16 for ; Thu, 15 May 2008 20:51:13 +0000 (UTC) (envelope-from andrew@modulus.org) Received: by email.octopus.com.au (Postfix, from userid 1002) id 2558617236; Fri, 16 May 2008 06:51:12 +1000 (EST) X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on email.octopus.com.au X-Spam-Level: X-Spam-Status: No, score=-1.4 required=10.0 tests=ALL_TRUSTED autolearn=failed version=3.2.3 Received: from [119.11.32.76] (unknown [119.11.32.76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: admin@email.octopus.com.au) by email.octopus.com.au (Postfix) with ESMTP id AB8611721F for ; Fri, 16 May 2008 06:51:07 +1000 (EST) Message-ID: <482CA235.6090400@modulus.org> Date: Fri, 16 May 2008 06:51:01 +1000 From: Andrew Snow User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: thread scheduling at mutex unlock X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2008 20:51:14 -0000 > But I think that it is not "fair" that at re-lock former > owner gets the lock immediately and the thread that waited on it for > longer time doesn't get a chance. I believe this is what yield() is for. Before attempting a re-lock you should call yield() to allow other threads a chance to run. (Side note: On FreeBSD, I believe only high priority threads will run when you yield(). As a workaround, I think you have to lower the thread's priority before yield() and then raise it again afterwards.) - Andrew From owner-freebsd-stable@FreeBSD.ORG Thu May 15 20:56:20 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E922B1065670; Thu, 15 May 2008 20:56:20 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from hosted.kievnet.com (hosted.kievnet.com [193.138.144.10]) by mx1.freebsd.org (Postfix) with ESMTP id A32158FC1A; Thu, 15 May 2008 20:56:20 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from localhost ([127.0.0.1] helo=edge.pp.kiev.ua) by hosted.kievnet.com with esmtpa (Exim 4.62) (envelope-from ) id 1JwkUt-000C9t-Aw; Thu, 15 May 2008 23:56:19 +0300 Message-ID: <482CA372.3000400@icyb.net.ua> Date: Thu, 15 May 2008 23:56:18 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.12 (X11/20080320) MIME-Version: 1.0 To: davids@webmaster.com References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, freebsd-threads@freebsd.org Subject: Re: thread scheduling at mutex unlock X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2008 20:56:21 -0000 on 15/05/2008 22:29 David Schwartz said the following: >> what if you have an infinite number of items on one side and finite >> number on the other, and you want to process them all (in infinite >> time, of course). Would you still try to finish everything on one >> side (the infinite one) or would you try to look at what you have >> on the other side? >> >> I am sorry about fuzzy wording of my original report, I should have >> mentioned "starvation" somewhere in it. > > There is no such thing as a "fair share" when comparing an infinite > quantity to a finite quantity. It is just as sensible to do 1 then 1 > as 10 then 10 or a billion then 1. > > What I would do in this case is work on one side for one timeslice > then the other side for one timeslice, continuuing until either side > was finished, then I'd work exclusively on the other side. This is > precisely the purpose for having timeslices in a scheduler. > > The timeslice is carefully chosen so that it's not so long that you > ignore a side for too long. It's also carefully chosen so that it's > not so short that you spend all your time switching swides. > > What sane schedulers do is assume that you want to make as much > forward progress as quickly as possible. This means getting as many > work units done per unit time as possible. This means as few context > switches as possible. > > A scheduler that switches significantly more often than once per > timeslice with a load like this is *broken*. The purpose of the > timeslice is to place an upper bound on the number of context > switches in cases where forward progress can be made on more than one > process. An ideal scheduler would not switch more often than once per > timeslice unless it could not make further forward progress. > > Real-world schedulers actually may allow one side to pre-empt the > other, and may switch a bit more often than a scheduler that's > "ideal" in the sense described above. This is done in an attempt to > boost interactive performance. > > But your basic assumption that strict alternation is desirable is > massively wrong. That's the *worst* *possible* outcome. David, thank you for the tutorial, it is quite enlightening. But first of all, did you take a look at my small test program? There are 1 second sleeps in it, this is not about timeslices and scheduling at that level at all. This is about basic expectation about fairness of acquiring a lock at macro level. I know that when one thread acquires and releases and reacquires a mutex during 10 seconds while the other thread is blocked on that mutex for 10 seconds, then this is not about timeslices. -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Thu May 15 21:02:45 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D82F4106564A; Thu, 15 May 2008 21:02:45 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from hosted.kievnet.com (hosted.kievnet.com [193.138.144.10]) by mx1.freebsd.org (Postfix) with ESMTP id 67EC78FC16; Thu, 15 May 2008 21:02:45 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from localhost ([127.0.0.1] helo=edge.pp.kiev.ua) by hosted.kievnet.com with esmtpa (Exim 4.62) (envelope-from ) id 1Jwkb6-000EGD-6b; Fri, 16 May 2008 00:02:44 +0300 Message-ID: <482CA4F3.6090501@icyb.net.ua> Date: Fri, 16 May 2008 00:02:43 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.12 (X11/20080320) MIME-Version: 1.0 To: Brent Casavant References: <482B0297.2050300@icyb.net.ua> <482BBA77.8000704@freebsd.org> <482BF5EA.5010806@icyb.net.ua> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, David Xu , freebsd-threads@freebsd.org Subject: Re: thread scheduling at mutex unlock X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2008 21:02:46 -0000 on 15/05/2008 22:51 Brent Casavant said the following: > On Thu, 15 May 2008, Andriy Gapon wrote: > >> With current libthr behavior the GUI thread would never have a chance to get >> the mutex as worker thread would always be a winner (as my small program >> shows). > > The example you gave indicates an incorrect mechanism being used for the > GUI to communicate with this worker thread. For the behavior you desire, > you need a common condition that lets both the GUI and the work item > generator indicate that there is something for the worker to do, *and* > you need seperate mechanisms for the GUI and work item generator to add > to their respective queues. Brent, that was just an example. Probably a quite bad example. I should only limit myself to the program that I sent and I should repeat that the result that it produces is not what I would call reasonably expected. And I will repeat that I understand that the behavior is not prohibited by standards (well, never letting other threads to run is probably not prohibited either). > Something like this (could be made even better with a little effor): > > struct worker_queues_s { > pthread_mutex_t work_mutex; > struct work_queue_s work_queue; > > pthread_mutex_t gui_mutex; > struct gui_queue_s gui_queue; > > pthread_mutex_t stuff_mutex; > int stuff_todo; > pthread_cond_t stuff_cond; > }; > struct worker_queue_s wq; > > int > main(int argc, char *argv[]) { > // blah blah > init_worker_queue(&wq); > // blah blah > } > > void > gui_callback(...) { > // blah blah > > // Set up GUI message > > pthread_mutex_lock(&wq.gui_mutex); > // Add GUI message to queue > pthread_mutex_unlock(&wq.gui_mutex); > > pthread_mutex_lock(&wq.stuff_mutex); > wq.stuff_todo++; > pthread_cond_signal(&wq.stuff_cond); > pthread_mutex_unlock(&wq.stuff_mutex); > > // blah blah > } > > void* > work_generator_thread(void*) { > // blah blah > > while (1) { > // Set up work to do > > pthread_mutex_lock(&wq.work_mutex); > // Add work item to queue > pthread_mutex_unlock(&wq.work_mutex); > > pthread_mutex_lock(&wq.stuff_mutex); > wq.stuff_todo++; > pthread_cond_signal(&wq.stuff_cond); > pthread_mutex_unlock(&wq.stuff_mutex); > } > > // blah blah > } > > void* > worker_thread(void* arg) { > // blah blah > > while (1) { > // Wait for there to be something to do > pthread_mutex_lock(&wq.stuff_mutex); > while (wq.stuff_todo < 1) { > pthread_cond_wait(&wq.stuff_cond, > &wq.stuff_mutex); > } > pthread_mutex_unlock(&wq.stuff_mutex); > > // Handle GUI messages > pthread_mutex_lock(&wq.gui_mutex); > while (!gui_queue_empty(&wq.gui_queue) { > // dequeue and process GUI messages > pthread_mutex_lock(&wq.stuff_mutex); > wq.stuff_todo--; > pthread_mutex_unlock(&wq.stuff_mutex); > } > pthread_mutex_unlock(&wq.gui_mutex); > > // Handle work items > pthread_mutex_lock(&wq.work_mutex); > while (!work_queue_empty(&wq.work_queue)) { > // dequeue and process work item > pthread_mutex_lock(&wq.stuff_mutex); > wq.stuff_todo--; > pthread_mutex_unlock(&wq.stuff_mutex); > } > pthread_mutex_unlock(&wq.work_mutex); > } > > // blah blah > } > > This should accomplish what you desire. Caution that I haven't > compiled, run, or tested it, but I'm pretty sure it's a solid > solution. > > The key here is unifying the two input sources (the GUI and work queues) > without blocking on either one of them individually. The value of > (wq.stuff_todo < 1) becomes a proxy for the value of > (gui_queue_empty(...) && work_queue_empty(...)). > > I hope that helps, > Brent > -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Thu May 15 22:23:55 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A5DF7106566B; Thu, 15 May 2008 22:23:55 +0000 (UTC) (envelope-from b.j.casavant@ieee.org) Received: from yeppers.tdkt.org (skyline.tdkt.org [209.98.211.67]) by mx1.freebsd.org (Postfix) with ESMTP id 029878FC26; Thu, 15 May 2008 22:23:54 +0000 (UTC) (envelope-from b.j.casavant@ieee.org) Received: from pkunk.americas.sgi.com (cfcafwp.sgi.com [192.48.179.6]) (authenticated bits=0) by yeppers.tdkt.org (8.12.11/8.12.11/erikj-OpenBSD) with ESMTP id m4FMNpLt018645; Thu, 15 May 2008 17:23:52 -0500 (CDT) Date: Thu, 15 May 2008 17:23:45 -0500 (CDT) From: Brent Casavant X-X-Sender: bcasavan@pkunk.americas.sgi.com To: Andriy Gapon In-Reply-To: <482CA4F3.6090501@icyb.net.ua> Message-ID: References: <482B0297.2050300@icyb.net.ua> <482BBA77.8000704@freebsd.org> <482BF5EA.5010806@icyb.net.ua> <482CA4F3.6090501@icyb.net.ua> User-Agent: Alpine 1.10 (BSF 962 2008-03-14) Organization: "Angeltread Software Organization" MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-stable@freebsd.org, freebsd-threads@freebsd.org Subject: Re: thread scheduling at mutex unlock X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Brent Casavant List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2008 22:23:55 -0000 On Fri, 16 May 2008, Andriy Gapon wrote: > that was just an example. Probably a quite bad example. > I should only limit myself to the program that I sent and I should repeat that > the result that it produces is not what I would call reasonably expected. And > I will repeat that I understand that the behavior is not prohibited by > standards (well, never letting other threads to run is probably not prohibited > either). Well, I don't know what to tell you at this point. I believe I understand the nature of the problem you're encountering, and I believe there are perfectly workable mechanisms in Pthreads to allow you to accomplish what you desire without depending on implementation-specific details. Yes, it's more work on your part, but if done well it's one-time work. The behavior you desire is useful only in limited situations, and can be implemented at the application level through the use of Pthreads primitives. If Pthreads behaved as you apparently expect, it would be impossible to implement the current behavior at the application level. Queueing mutexes are innappropriate in the majority of code designs. I'll take your word that it is appropriate in your particular case, but that does not make it appropriate for more typical designs. Several solutions have been presented, including one from me. If you choose not to implement such solutions, then best of luck to you. OK, I'm a sucker for punishment. So use this instead of Pthreads mutexes. This should work on both FreeBSD and Linux (FreeBSD has some convenience routines in the sys/queue.h package that Linux doesn't): #include #include struct thread_queue_entry_s { TAILQ_ENTRY(thread_queue_entry_s) tqe_list; pthread_cond_t tqe_cond; pthread_mutex_t tqe_mutex; int tqe_wakeup; }; TAILQ_HEAD(thread_queue_s, thread_queue_entry_s); typedef struct { struct thread_queue_s qm_queue; pthread_mutex_t qm_queue_lock; unsigned int qm_users; } queued_mutex_t; int queued_mutex_init(queued_mutex_t *qm) { TAILQ_INIT(&qm->qm_queue); qm->qm_users = 0; return pthread_mutex_init(&qm->qm_queue_lock, NULL); } int queued_mutex_lock(queued_mutex_t *qm) { struct thread_queue_entry_s waiter; pthread_mutex_lock(&qm->qm_queue_lock); qm->qm_users++; if (1 == qm->qm_users) { /* Nobody was waiting for mutex, we own it. * Fast path out. */ pthread_mutex_unlock(&qm->qm_queue_lock); return 0; } /* There are others waiting for the mutex. Slow path. */ /* Initialize this thread's wait structure */ pthread_cond_init(&waiter->tqe_cond, NULL); pthread_mutex_init(&waiter->tqe_mutex, NULL); pthread_mutex_lock(&waiter->tqe_mutex); waiter->tqe_wakeup = 0; /* Add this thread's wait structure to queue */ TAILQ_INSERT_TAIL(&qm->qm_queue, &waiter, tqe_list); pthread_mutex_unlock(&qm->qm_queue_lock); /* Wait for somebody to hand the mutex to us */ while (!waiter->tqe_wakeup) { pthread_cond_wait(&waiter->tqe_cond, &waiter->tqe_mutex); } /* Destroy this thread's wait structure */ pthread_mutex_unlock(&waiter->tqe_mutex); pthread_mutex_destroy(&waiter->tqe_mutex); pthread_cond_destroy(&waiter->tqe_cond); /* We own the queued mutex (handed to us by unlock) */ return 0; } int queued_mutex_unlock(queued_mutex_t *qm) { struct thread_queue_entry_s *waiter; pthread_mutex_lock(&qm->qm_queue_lock); qm->qm_users--; if (0 == qm->qm_users) { /* No waiters to wake up. Fast path out. */ pthread_mutex_unlock(&qm->qm_queue_lock); return 0; } /* Wake up first waiter. Slow path. */ /* Remove the first waiting thread. */ waiter = qm->qm_queue.tqh_first; TAILQ_REMOVE(&qm->qm_queue, waiter, tqe_list); pthread_mutex_unlock(&qm->qm_queue_lock); /* Wake up the thread. */ pthread_mutex_lock(&waiter->tqe_mutex); waiter->tqe_wakeup = 1; pthread_cond_signal(&waiter->tqe_cond); pthread_mutex_unlock(&waiter->tqe_mutex); return 0; } int queued_mutex_destroy(queued_mutex_t *qm) { pthread_mutex_lock(&qm->qm_queue_lock); if (qm->qm_users > 1) { pthread_mutex_unlock(&qm->qm_queue_lock); return EBUSY; } return pthread_mutex_destroy(&qm->qm_queue_lock); } These queued_mutex_t mutexes should have the behavior you're looking for, and will be portable to any platform with Pthreads and sys/queue.h. Be warned that I haven't compiled, run, or debugged this, but the code should be pretty solid (typos aside). Of course, in production code I'd check a bunch of return values, but those would just get in the way of this illustration. So use something this or change the application's threading model (like my previous post showed). There's no use complaining about the Pthreads implementation in this regard because your application's use of mutexes is the exception, not the rule. The fact that Linux behaves as you expect is irrelevant, as POSIX doesn't speak to this facet of implementation, so both Linux and BSD are correct. Relying on this behavior in Linux is ill-advised as it is non-portable, and likely to break in future releases. Brent -- Brent Casavant Dance like everybody should be watching. www.angeltread.org KD5EMB, EN34lv From owner-freebsd-stable@FreeBSD.ORG Thu May 15 22:37:43 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2C07A1065671; Thu, 15 May 2008 22:37:43 +0000 (UTC) (envelope-from davids@webmaster.com) Received: from mail1.webmaster.com (mail1.webmaster.com [216.152.64.169]) by mx1.freebsd.org (Postfix) with ESMTP id 128EF8FC1C; Thu, 15 May 2008 22:37:42 +0000 (UTC) (envelope-from davids@webmaster.com) Received: from however by webmaster.com (MDaemon.PRO.v8.1.3.R) with ESMTP id md50002053693.msg; Thu, 15 May 2008 15:38:23 -0700 From: "David Schwartz" To: Date: Thu, 15 May 2008 15:37:00 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: <482CA372.3000400@icyb.net.ua> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 X-Authenticated-Sender: joelkatz@webmaster.com X-Spam-Processed: mail1.webmaster.com, Thu, 15 May 2008 15:38:23 -0700 (not processed: message from trusted or authenticated source) X-MDRemoteIP: 206.171.168.138 X-Return-Path: davids@webmaster.com X-MDAV-Processed: mail1.webmaster.com, Thu, 15 May 2008 15:38:24 -0700 Cc: freebsd-stable@freebsd.org, freebsd-threads@freebsd.org Subject: RE: thread scheduling at mutex unlock X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: davids@webmaster.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2008 22:37:43 -0000 > David, =20 > thank you for the tutorial, it is quite enlightening. > But first of all, did you take a look at my small test program? Yes. It demonstrates the classic example of mutex abuse. A mutex is not = an appropriate synchronization mechanism when it's going to be held most = of the time and released briefly. > There are 1 second sleeps in it, this is not about timeslices and=20 > scheduling at that level at all. This is about basic expectation about = > fairness of acquiring a lock at macro level. I know that when one = thread=20 > acquires and releases and reacquires a mutex during 10 seconds while = the=20 > other thread is blocked on that mutex for 10 seconds, then this is not = > about timeslices. I guess it comes down to what your test program is supposed to test. = Threading primitives can always be made to look bad in toy test programs = that don't even remotely reflect real-world use cases. No sane person = optimizes for such toys. The reason your program behaves the way it does is because the thread = that holds the mutex relinquishes the CPU while it holds it. As such, it = appears to be very nice and is its dynamic priority level rises. In a = real-world case, the threads waiting for the mutex will have their = priorities rise while the thread holding the mutex will use up its = timeslice working. This is simply not appropriate use of a mutex. It would be absolute = foolishness to encumber the platform's default mutex implementation with = any attempt to make such abuses do more what you happen to expect them = to do. In fact, the behavior I expect is the behavior seen. So the defect is in = your unreasonable expectations. The scheduler's goal is to allow the = running thread to make forward progress, and it does this perfectly. DS From owner-freebsd-stable@FreeBSD.ORG Thu May 15 23:25:29 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9AFEC1065678; Thu, 15 May 2008 23:25:29 +0000 (UTC) (envelope-from joe@tao.org.uk) Received: from mailhost.tao.org.uk (tao.uscs.susx.ac.uk [139.184.131.101]) by mx1.freebsd.org (Postfix) with ESMTP id 5F3748FC1C; Thu, 15 May 2008 23:25:29 +0000 (UTC) (envelope-from joe@tao.org.uk) Received: from genius (wireless59.dhcp.tao.org.uk [82.153.225.59]) (Authenticated sender: joemail@transwarp.tao.org.uk) by mailhost.tao.org.uk (Postfix) with ESMTP id 6CB2C81C6; Fri, 16 May 2008 00:25:26 +0100 (BST) From: "Dr Josef Karthauser" To: "'Tony Finch'" References: <20080511102730.DBD0A600F@mailhost.tao.org.uk> In-Reply-To: Date: Fri, 16 May 2008 00:25:26 +0100 Organization: Tao Research Message-ID: <07f101c8b6e2$f4b13f20$de13bd60$@org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Aci0T1To4GbZ6Q7dTnmaAknGu4EvVACk5EyQ Content-Language: en-gb Cc: freebsd-hubs@freebsd.org, freebsd-stable@freebsd.org Subject: RE: cvsup.uk.FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: joe@tao.org.uk List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2008 23:25:29 -0000 > -----Original Message----- > From: owner-freebsd-hubs@freebsd.org [mailto:owner-freebsd- > hubs@freebsd.org] On Behalf Of Tony Finch > Sent: 12 May 2008 17:06 > To: Dr Joe Karthauser > Cc: freebsd-hubs@freebsd.org; freebsd-stable@freebsd.org > Subject: Re: cvsup.uk.FreeBSD.org > > On Sun, 11 May 2008, Dr Joe Karthauser wrote: > > > > I have reclassified this faulty mirror as cvsup1 and made cvsup a > cname to > > cvsup3, which is the most recent addition and best hardware > available. In > > the future we will always point to the most available machine in this > way. > > Looks like I'm getting a bit more traffic than before - peaking at over > 100 logins an hour. As a matter of interest, do you know what the peak bandwidth usage is? Joe From owner-freebsd-stable@FreeBSD.ORG Fri May 16 00:12:36 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CC0B91065679 for ; Fri, 16 May 2008 00:12:36 +0000 (UTC) (envelope-from jan6146@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.227]) by mx1.freebsd.org (Postfix) with ESMTP id A27C18FC1B for ; Fri, 16 May 2008 00:12:36 +0000 (UTC) (envelope-from jan6146@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so842544rvf.43 for ; Thu, 15 May 2008 17:12:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; bh=MQBnBJ80dQL3dfYCEW+I2nQDAD7CnpF6CQwSR2izZn4=; b=riQacPOFat2hahWdviHaICIZ5pXPYj8gok25qB9l3YNtttB1UiSTKv+dmrDXmwSUSGSeXXkw+9jXy3nkYWixww1U4snC1gYCUfQW2t0ZToNSIIS5Od6vNninokAmZBHFr5xJ9d9RFT2ZtnFbwfBuO6ICiMJAzMUXHpGhrPC20d0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=SxYUhjGEi+Fo3rKKU4stgZhM0PwqZRTWI23UsizJCqN/w9yLauWwYPssHJtC7Pl7hJM1rT8kRf/TJ6N1ZyOeU3KbqYUK9IX5RhNEKl0Y+OGs4Cl82n7Y5nwdPqCYSrji2O5D+wksNydjVhdTu4wF6la1J0qFW2BNQz//THzYPBU= Received: by 10.141.171.6 with SMTP id y6mr1426808rvo.85.1210895097139; Thu, 15 May 2008 16:44:57 -0700 (PDT) Received: by 10.141.114.7 with HTTP; Thu, 15 May 2008 16:44:57 -0700 (PDT) Message-ID: <784966050805151644m43b9a5e1qe8a4568576fc081f@mail.gmail.com> Date: Thu, 15 May 2008 16:44:57 -0700 From: "Rob Lytle" To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: today's build is causing errors for me X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2008 00:12:37 -0000 First I am running 7.0-Stable and just cvsup'd today. Then I built the system, new kernel, and installed them. Second I am using the GENERIC KERNEL. Sysctl.conf is empty. I will put my /etc/rc.conf at the end. I tried to do a very careful job of merging /usr/src/etc with /etc. I didn't touch any files that I or the computer configured. But I am getting these errors upon bootup: 1. eval: /etc/rc.d/cleanvar: Permission Denied 2. syslogd: bind: Can't assign requested address. (repeated twice) 3. syslogd: child pid 134 exited with return code 1 4. /etc/rc: Warning: Dump device does not exist. Savecore will not run. (this always worked before) 5. /etc/rc.d/securelevel: /etc/rc.d/sysctl: Permission denied. 6. My computer says "Amnesiac" yet the host name is clearly in rc.conf 7. My WiFi no longer starts up by myself. I have to do it all manually using ifconfig and dhclient. Any help would be appreciated. I'm kind of lost as some of it makes no sense to me, esp #6 and 7. Has the default rc.conf format changed??? Thanks, Sincerely, Rob ------------------------------------------ My rc.conf file # -- sysinstall generated deltas -- # Sun Oct 28 11:36:26 2007 # Created: Sun Oct 28 11:36:26 2007 # Enable network daemons for user convenience. # Please make all changes to this file, not to /etc/defaults/rc.conf. # This file now contains just the overrides from /etc/defaults/rc.conf. hostname="xenon" # "" for DHCP linux_enable="YES" #moused_enable="YES" sshd_enable="YES" usbd_enable="YES" lpd_enable="YES" kern_securelevel_enable="NO" dumpdev="AUTO" dumpdir="/var/crash" cron_enable="YES" performance_cx_lowest="LOW" performance_cpu_freq="HIGH" economy_cx_lowest="LOW" economy_cpu_freq="LOW" ipfilter_enable="YES" ipfilter_rules="/etc/ipfw.rules" ipmon_enable="YES" ipmon_flags="-Ds" watchdogd_enable="YES" powerd_enable="YES" mixer_enable="YES" #ifconfig_ath0="WPA DHCP channel 3" #ifconfig_msk0="DHCP" ifconfig_ath0="DHCP ssid leighmorlock channel 6" # added by mergebase.sh local_startup="/usr/local/etc/rc.d" From owner-freebsd-stable@FreeBSD.ORG Fri May 16 04:20:40 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 26E591065675; Fri, 16 May 2008 04:20:40 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from gaia.nimnet.asn.au (nimbin.lnk.telstra.net [139.130.45.143]) by mx1.freebsd.org (Postfix) with ESMTP id 9B4168FC19; Fri, 16 May 2008 04:20:37 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from localhost (smithi@localhost) by gaia.nimnet.asn.au (8.8.8/8.8.8R1.5) with SMTP id NAA15526; Fri, 16 May 2008 13:56:50 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Fri, 16 May 2008 13:56:49 +1000 (EST) From: Ian Smith To: Jeremy Chadwick In-Reply-To: <20080515162056.GA17187@eos.sc1.parodius.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Vivek Khera , "Andrey V. Elsukov" , "Bruce M. Simpson" , freebsd-stable@freebsd.org, freebsd-ipfw@freebsd.org Subject: Re: how much memory does increasing max rules for IPFW take up? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2008 04:20:40 -0000 On Thu, 15 May 2008, Jeremy Chadwick wrote: > On Thu, May 15, 2008 at 11:03:53AM +0100, Bruce M. Simpson wrote: > > Andrey V. Elsukov wrote: > >> Vivek Khera wrote: > >>> I had a box run out of dynamic state space yesterday. I found I can > >>> increase the number of dynamic rules by increasing the sysctl parameter > >>> net.inet.ip.fw.dyn_max. I can't find, however, how this affects memory > >>> usage on the system. Is it dyanamically allocated and de-allocated, or > >>> is it a static memory buffer? > >> > >> Each dynamic rule allocated dynamically. Be careful, too many dynamic > >> rules will work very slow. > > > > Got any figures for this? I took a quick glance and it looks like it just > > uses a hash over dst/src/dport/sport. If there are a lot of raw IP or ICMP > > flows then that's going to result in hash collisions. > > > > It might be a good project for someone to optimize if it isn't scaling for > > folk. "Bloomier" filters are probably worth a look -- bloom filters are a > > class of probabilistic hash which may return a false positive, "bloomier" > > filters are a refinement which tries to limit the false positives. > > > > Having said that the default tunable of 256 state entries is probably quite > > low for use cases other than "home/small office NAT gateway". > > It's far too low for home/small office. Standard Linux NAT routers, > such as the Linksys WRT54G/GL, come with a default state table count of > 2048, and often is increased by third-party firmwares to 8192 based on > justified necessity. Search for "conntrack" below: > > http://www.polarcloud.com/firmware > > 256 can easily be exhausted by more than one user loading multiple HTTP > 1.0 web pages at one time (such is the case with many users now have > browsers that load 7-8 web pages into separate tabs during startup). > > And if that's not enough reason, consider torrents, which is quite often > what results in a home or office router exhausting its state table. > > Bottom line: the 256 default is too low. It needs to be increased to at > least 2048. I think there may be some confusion in terms. Looking at defaults on my older 5.5 system - sure, call it a "home/small office NAT gateway": net.inet.ip.fw.dyn_buckets: 256 net.inet.ip.fw.curr_dyn_buckets: 256 net.inet.ip.fw.dyn_count: 212 net.inet.ip.fw.dyn_max: 4096 net.inet.ip.fw.static_count: 153 What defaults to 256 is the number of hash table buckets, not the max number of dynamic rules, here 4096 (though the 5.5 manual says 8192). On hash collisions, a linked list is used for duplicate hashes of: i = (id->dst_ip) ^ (id->src_ip) ^ (id->dst_port) ^ (id->src_port); i &= (curr_dyn_buckets - 1); So while 256 may well be too few buckets for many systems, and like Bruce I wonder about the effectiveness of the xor hash for raw IP & ICMP and wouldn't mind seeing some stats on bucket use vs linked list lengths for various workloads, it doesn't determine the max no. of dynamic rules available, which is adjustable up without any apparent static memory allocation, and is moderated by the various expiry timeout sysctls. For reference, I admin a 4.8 filtering bridge with up to 20 boxes behind it, that has only very rarely reported exceeding the max no. of dynamic rules with the (4.8) default net.inet.ip.fw.dyn_max of 1000 .. however it only keeps state for UDP connections (and yes, it only ever hits that limit on torrents or skype, which are generally admin. prohib. :) cheers, Ian (not subscribed to -ipfw) From owner-freebsd-stable@FreeBSD.ORG Fri May 16 04:33:18 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 54CFF1065670; Fri, 16 May 2008 04:33:18 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from smtp6.yandex.ru (smtp6.yandex.ru [213.180.200.197]) by mx1.freebsd.org (Postfix) with ESMTP id 30F468FC2E; Fri, 16 May 2008 04:33:16 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from ns.kirov.so-cdu.ru ([77.72.136.145]:47811 "EHLO [127.0.0.1]" smtp-auth: "bu7cher" TLS-CIPHER: "DHE-RSA-AES256-SHA keybits 256/256 version TLSv1/SSLv3" TLS-PEER-CN1: ) by mail.yandex.ru with ESMTP id S5473464AbYEPEdO (ORCPT + 2 others); Fri, 16 May 2008 08:33:14 +0400 X-Yandex-Spam: 1 X-Yandex-Front: smtp6 X-Yandex-TimeMark: 1210912394 X-MsgDayCount: 5 X-Comment: RFC 2476 MSA function at smtp6.yandex.ru logged sender identity as: bu7cher Message-ID: <482D0E87.6000003@yandex.ru> Date: Fri, 16 May 2008 08:33:11 +0400 From: "Andrey V. Elsukov" User-Agent: Mozilla Thunderbird 1.5 (FreeBSD/20051231) MIME-Version: 1.0 To: "Bruce M. Simpson" References: <04EA1C34-AB7D-4A85-8A91-DED03E987706@khera.org> <482C07DE.3090504@yandex.ru> <482C0A89.104@FreeBSD.org> In-Reply-To: <482C0A89.104@FreeBSD.org> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: Vadim Goncharov , Vivek Khera , FreeBSD Stable , freebsd-ipfw@freebsd.org Subject: Re: how much memory does increasing max rules for IPFW take up? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2008 04:33:18 -0000 Bruce M. Simpson wrote: > Got any figures for this? I took a quick glance and it looks like it > just uses a hash over dst/src/dport/sport. If there are a lot of raw IP > or ICMP flows then that's going to result in hash collisions. It's my guess, i haven't any figures.. Yes, hash collisions will trigger many searching in buckets lists. And increasing only dyn_max without increasing dyn_buckets will grow collisions. > It might be a good project for someone to optimize if it isn't scaling > for folk. "Bloomier" filters are probably worth a look -- bloom filters > are a class of probabilistic hash which may return a false positive, > "bloomier" filters are a refinement which tries to limit the false > positives. There were some ideas from Vadim Goncharov about rewriting dynamic rules implementation.. -- WBR, Andrey V. Elsukov From owner-freebsd-stable@FreeBSD.ORG Fri May 16 04:34:12 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 30C1A106567D for ; Fri, 16 May 2008 04:34:12 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 212188FC19 for ; Fri, 16 May 2008 04:34:12 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 02E601CC05F; Thu, 15 May 2008 21:34:12 -0700 (PDT) Date: Thu, 15 May 2008 21:34:12 -0700 From: Jeremy Chadwick To: Rob Lytle Message-ID: <20080516043411.GA44491@eos.sc1.parodius.com> References: <784966050805151644m43b9a5e1qe8a4568576fc081f@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <784966050805151644m43b9a5e1qe8a4568576fc081f@mail.gmail.com> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-stable@freebsd.org Subject: Re: today's build is causing errors for me X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2008 04:34:12 -0000 On Thu, May 15, 2008 at 04:44:57PM -0700, Rob Lytle wrote: > First I am running 7.0-Stable and just cvsup'd today. Then I built the > system, new kernel, and installed them. Second I am using the GENERIC > KERNEL. Sysctl.conf is empty. I will put my /etc/rc.conf at the end. I > tried to do a very careful job of merging /usr/src/etc with /etc. I didn't > touch any files that I or the computer configured. > > But I am getting these errors upon bootup: > > 1. eval: /etc/rc.d/cleanvar: Permission Denied > 2. syslogd: bind: Can't assign requested address. (repeated twice) > 3. syslogd: child pid 134 exited with return code 1 > 4. /etc/rc: Warning: Dump device does not exist. Savecore will not > run. (this always worked before) > 5. /etc/rc.d/securelevel: /etc/rc.d/sysctl: Permission denied. > 6. My computer says "Amnesiac" yet the host name is clearly in rc.conf > 7. My WiFi no longer starts up by myself. I have to do it all manually > using ifconfig and dhclient. You should have followed the instructions in /usr/src/Makefile. You don't "merge things by hand". You can use mergemaster for that. Please use it, as I'm willing to bet there's a portion of your rc framework which is broken in some way. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Fri May 16 06:04:35 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DC534106566C for ; Fri, 16 May 2008 06:04:34 +0000 (UTC) (envelope-from jan6146@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.236]) by mx1.freebsd.org (Postfix) with ESMTP id A7C768FC1A for ; Fri, 16 May 2008 06:04:34 +0000 (UTC) (envelope-from jan6146@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so3073rvf.43 for ; Thu, 15 May 2008 23:04:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=OqD5BywVL9+6N5XbPk0RNEB3c14CT5Stmt9xWjnkH7w=; b=INAyFe+Dr+oRX7qf97Od4Weyx+S8jXilo89CH/1mte68PEM/qndU09T7goalImZlntp+OI9kVcXjhVwNObbj5qekZRjJccpSO8fJmMrZp1yayZxXFUoFy3wNwXFV0Sk+/Nc1vlc0hzFd2Dxx+8wmP7LPoaCSkRcAZios2kZxX+g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Ae8ho0ttR9w3Vt4RSOKrVmemFNSRx2hPgh2MmMMj+slY96KSE2FXs5jIPBMxTTVoDszbnrFtt/q7dU9JdiW27I5wFqZy6CrC3Cv9qwybkFBh9wRn4KmM6FyrT1aqklN4lsEtP09siWIqIURBC755wMD6uhuV502Dmk1qOmcxhJ8= Received: by 10.141.43.5 with SMTP id v5mr1579050rvj.49.1210917874316; Thu, 15 May 2008 23:04:34 -0700 (PDT) Received: by 10.141.114.7 with HTTP; Thu, 15 May 2008 23:04:34 -0700 (PDT) Message-ID: <784966050805152304t1827c53bi6988ae9c8f837f32@mail.gmail.com> Date: Thu, 15 May 2008 23:04:34 -0700 From: "Rob Lytle" To: "Jeremy Chadwick" In-Reply-To: <20080516043411.GA44491@eos.sc1.parodius.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <784966050805151644m43b9a5e1qe8a4568576fc081f@mail.gmail.com> <20080516043411.GA44491@eos.sc1.parodius.com> Cc: freebsd-stable@freebsd.org Subject: Re: today's build is causing errors for me X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2008 06:04:35 -0000 Hi Jeremy, I used Mergemaster. Thats what I mean't when I said that I carefully "merged" /usr/src/etc/ with /etc. But like I said, no files were replaced that contained my own configuration, e.g. group. I will say this- that I have always considered Mergemaster a confusing mess, despite the dogma on the lists. I have been running FreeBSD and installing it since 1998, so I have some experience- but this is new behavior beyond my previous experiences. Sincerely, Rob. On 5/15/08, Jeremy Chadwick wrote: > On Thu, May 15, 2008 at 04:44:57PM -0700, Rob Lytle wrote: >> First I am running 7.0-Stable and just cvsup'd today. Then I built the >> system, new kernel, and installed them. Second I am using the GENERIC >> KERNEL. Sysctl.conf is empty. I will put my /etc/rc.conf at the end. I >> tried to do a very careful job of merging /usr/src/etc with /etc. I >> didn't >> touch any files that I or the computer configured. >> >> But I am getting these errors upon bootup: >> >> 1. eval: /etc/rc.d/cleanvar: Permission Denied >> 2. syslogd: bind: Can't assign requested address. (repeated twice) >> 3. syslogd: child pid 134 exited with return code 1 >> 4. /etc/rc: Warning: Dump device does not exist. Savecore will not >> run. (this always worked before) >> 5. /etc/rc.d/securelevel: /etc/rc.d/sysctl: Permission denied. >> 6. My computer says "Amnesiac" yet the host name is clearly in rc.conf >> 7. My WiFi no longer starts up by myself. I have to do it all manually >> using ifconfig and dhclient. > > You should have followed the instructions in /usr/src/Makefile. You > don't "merge things by hand". You can use mergemaster for that. Please > use it, as I'm willing to bet there's a portion of your rc framework > which is broken in some way. > > -- > | Jeremy Chadwick jdc at parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > From owner-freebsd-stable@FreeBSD.ORG Fri May 16 06:17:24 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E0E961065677 for ; Fri, 16 May 2008 06:17:24 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id CF8668FC28 for ; Fri, 16 May 2008 06:17:24 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id C774B1CC038; Thu, 15 May 2008 23:17:24 -0700 (PDT) Date: Thu, 15 May 2008 23:17:24 -0700 From: Jeremy Chadwick To: Rob Lytle Message-ID: <20080516061724.GA47953@eos.sc1.parodius.com> References: <784966050805151644m43b9a5e1qe8a4568576fc081f@mail.gmail.com> <20080516043411.GA44491@eos.sc1.parodius.com> <784966050805152304t1827c53bi6988ae9c8f837f32@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <784966050805152304t1827c53bi6988ae9c8f837f32@mail.gmail.com> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-stable@freebsd.org Subject: Re: today's build is causing errors for me X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2008 06:17:25 -0000 On Thu, May 15, 2008 at 11:04:34PM -0700, Rob Lytle wrote: > Hi Jeremy, > > I used Mergemaster. Thats what I mean't when I said that I carefully > "merged" /usr/src/etc/ with /etc. But like I said, no files were > replaced that contained my own configuration, e.g. group. I will say > this- that I have always considered Mergemaster a confusing mess, > despite the dogma on the lists. I have been running FreeBSD and > installing it since 1998, so I have some experience- but this is new > behavior beyond my previous experiences. "Permission denied" could imply that the rc scripts aren't set to executable. Possibly a umask problem? Additionally, mergemaster isn't a confusing mess. If anything, it's one of the most simple tools there is for managing /etc. The part you probably find "confusing", which is the same part I did when I started using it, is the side-by-side interactive diff. It's very easy to use; "r" means use the text shown on the right, and "l" means use the text shown on the left. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Fri May 16 06:22:31 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 80A3F1065672 for ; Fri, 16 May 2008 06:22:31 +0000 (UTC) (envelope-from jan6146@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.227]) by mx1.freebsd.org (Postfix) with ESMTP id 384AC8FC19 for ; Fri, 16 May 2008 06:22:30 +0000 (UTC) (envelope-from jan6146@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so11550rvf.43 for ; Thu, 15 May 2008 23:22:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:mime-version:content-type; bh=BE4uhmUCRpWeBuYloQgjglZDx9O8jRf+MJF58lXZvMw=; b=Ubh+rfWhtcLxBVPIKvc8jFPUPV09Qxorzh+yTNT2a28C59wW1+TlYgsaejruQcS+1rBdT06vV/GX9yoaxZ8iUHhK8BlGDTXjL0KlOdXcF0sS2INSTCHrmX5pxd4t7XGeE+CGVIPIKrJTC5pJztp7drXldW+2Hz3hFOoYUiA0zIQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:mime-version:content-type; b=EHCJ8uPKvXFsq0CUr9RVepr74Z84VmdgRQCjV/9mLhPfnJGCny5gdRB6lAKuHF6CqIRhThzSM5mlDyFajm2wDsi6/UttdoJ3qJN3H2ilJ3cPT12qjKYzB/yCbDCMHJrCkoJhGjWrwby/osr7xK0XKe+NOIF5ueKGXwYY84fuqVg= Received: by 10.141.20.7 with SMTP id x7mr1578251rvi.82.1210918949652; Thu, 15 May 2008 23:22:29 -0700 (PDT) Received: by 10.141.114.7 with HTTP; Thu, 15 May 2008 23:22:29 -0700 (PDT) Message-ID: <784966050805152322n5e03b67bhc29d912860c0c3c3@mail.gmail.com> Date: Thu, 15 May 2008 23:22:29 -0700 From: "Rob Lytle" To: "Jeremy Chadwick" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: today's build is causing errors for me / Fixed for now X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2008 06:22:31 -0000 Hi Jeremy, I always back up /etc before I upgrade the system. The old /etc works just fine. I will eventually go back in and check out the new /etc to see what is wrong. Sincerely, Rob. On Thu, May 15, 2008 at 11:17 PM, Jeremy Chadwick wrote: > On Thu, May 15, 2008 at 11:04:34PM -0700, Rob Lytle wrote: > > Hi Jeremy, > > > > I used Mergemaster. Thats what I mean't when I said that I carefully > > "merged" /usr/src/etc/ with /etc. But like I said, no files were > > replaced that contained my own configuration, e.g. group. I will say > > this- that I have always considered Mergemaster a confusing mess, > > despite the dogma on the lists. I have been running FreeBSD and > > installing it since 1998, so I have some experience- but this is new > > behavior beyond my previous experiences. > > "Permission denied" could imply that the rc scripts aren't set to > executable. Possibly a umask problem? > > Additionally, mergemaster isn't a confusing mess. If anything, it's one > of the most simple tools there is for managing /etc. The part you > probably find "confusing", which is the same part I did when I started > using it, is the side-by-side interactive diff. It's very easy to use; > "r" means use the text shown on the right, and "l" means use the text > shown on the left. > > -- > | Jeremy Chadwick jdc at parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > From owner-freebsd-stable@FreeBSD.ORG Fri May 16 07:02:47 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C3BC41065678 for ; Fri, 16 May 2008 07:02:47 +0000 (UTC) (envelope-from jan6146@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.238]) by mx1.freebsd.org (Postfix) with ESMTP id 798AA8FC16 for ; Fri, 16 May 2008 07:02:47 +0000 (UTC) (envelope-from jan6146@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so32223rvf.43 for ; Fri, 16 May 2008 00:02:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=f7DiAcwH5UssqODcxkw8TUX33pwRsSyUvs/ybGTnnY4=; b=qe7ba0kmzPTwV25ICiu5t4EZuHRMDQCxz2hrPdBuJ/rZ8aYtTlgZFm7kBe1l+rM3pscOJJlXfe1q5zg0nR2LuB9OGYzzPtTTr85p8FzQGnS/kMAYJXew/FaHkhhg7Vjuw2hO1GOJ1ATbeEU3yDToMYGgQeKuOg9iNBgenOeFa18= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=Y2/Es1FxSLOok5XEB2OccavMa5ZIWRhAafRx6wgnwOXnlKopbp9dfpeOXboPmnSi5tN1nvHT+SRZUIiKKOiIEsON5DcBmmcCprQwXZr4AtNvxZUowEtAPWI7iFRsSJJ0zU03WzlZdxtL+KK93EgQAWKlVQRKVAmLzvM3c2MWS7c= Received: by 10.140.249.20 with SMTP id w20mr1591206rvh.189.1210921367272; Fri, 16 May 2008 00:02:47 -0700 (PDT) Received: by 10.141.114.7 with HTTP; Fri, 16 May 2008 00:02:47 -0700 (PDT) Message-ID: <784966050805160002g63defc51j11465f0d51025a0d@mail.gmail.com> Date: Fri, 16 May 2008 00:02:47 -0700 From: "Rob Lytle" To: "Jeremy Chadwick" In-Reply-To: <20080516061724.GA47953@eos.sc1.parodius.com> MIME-Version: 1.0 References: <784966050805151644m43b9a5e1qe8a4568576fc081f@mail.gmail.com> <20080516043411.GA44491@eos.sc1.parodius.com> <784966050805152304t1827c53bi6988ae9c8f837f32@mail.gmail.com> <20080516061724.GA47953@eos.sc1.parodius.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: today's build is causing errors for me X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2008 07:02:47 -0000 Hi Jeremy, You were correct. Somehow some files in /etc/rc.d had permissions of 644. Setting the new permissions to that of the old fixed the problem. Thanks. Rob. On Thu, May 15, 2008 at 11:17 PM, Jeremy Chadwick wrote: > On Thu, May 15, 2008 at 11:04:34PM -0700, Rob Lytle wrote: > > Hi Jeremy, > > > > I used Mergemaster. Thats what I mean't when I said that I carefully > > "merged" /usr/src/etc/ with /etc. But like I said, no files were > > replaced that contained my own configuration, e.g. group. I will say > > this- that I have always considered Mergemaster a confusing mess, > > despite the dogma on the lists. I have been running FreeBSD and > > installing it since 1998, so I have some experience- but this is new > > behavior beyond my previous experiences. > > "Permission denied" could imply that the rc scripts aren't set to > executable. Possibly a umask problem? > > Additionally, mergemaster isn't a confusing mess. If anything, it's one > of the most simple tools there is for managing /etc. The part you > probably find "confusing", which is the same part I did when I started > using it, is the side-by-side interactive diff. It's very easy to use; > "r" means use the text shown on the right, and "l" means use the text > shown on the left. > > -- > | Jeremy Chadwick jdc at parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > From owner-freebsd-stable@FreeBSD.ORG Fri May 16 07:13:24 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EDC42106566B for ; Fri, 16 May 2008 07:13:24 +0000 (UTC) (envelope-from jan6146@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.224]) by mx1.freebsd.org (Postfix) with ESMTP id 305738FC28 for ; Fri, 16 May 2008 07:13:24 +0000 (UTC) (envelope-from jan6146@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so39286rvf.43 for ; Fri, 16 May 2008 00:13:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition; bh=dA5YDCQ4+20785kQR0H9MR2RTOpbqI5I5PDQ2iJ/qHY=; b=rktjfaL5Ej669NKDydHe7EoEll146CFCvwAQfKE0yuyAx3JixfrJLjQaJhkcdfMT43Q0wkDoqG/np11FXYFiN3bkFSArtpRJsqWKwwZpBAzD7VNoux86+fs7A9pM+yR2HmbeYZfKfXJY/tn/EYeKPVqQMtsIRn0xt7uqVifYXhY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition; b=CdMlqp8GUVYh4C6o5qnVI6Vo/dDUQzJHGJaeKqtFvFdBdmUFOOIyEyeu85MV6JDfuJtoQQoChx6Pqbqxahj8YEwG0FbOh56170gzm4FbbcavrOIbfeXb/SuTP5xe4vfULN75D1CU9KR4CgNHl089ImwPWoFDkOR0W3ffKrWWfHo= Received: by 10.140.207.2 with SMTP id e2mr1599611rvg.144.1210921999628; Fri, 16 May 2008 00:13:19 -0700 (PDT) Received: by 10.141.114.7 with HTTP; Fri, 16 May 2008 00:13:19 -0700 (PDT) Message-ID: <784966050805160013w7d3ec31euc95be9e4a0a68fa9@mail.gmail.com> Date: Fri, 16 May 2008 00:13:19 -0700 From: "Rob Lytle" To: "Jeremy Chadwick" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: freebsd-stable@freebsd.org Subject: just one last question about /etc/rc.d file permissions X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2008 07:13:25 -0000 Hi Jeremy, I noticed that most all of the files in my old /etc/rc.d had 555 permissions. There were 4 or 5 that had 644 permissions in my old /etc/rc.d. What I am wondering is if all the files in rc.d should be 555? So far I am not experiencing any problems with anything with a very few 644 files. Thanks, Rob. On 5/16/08, Rob Lytle wrote: > Hi Jeremy, > > You were correct. Somehow some files in /etc/rc.d had permissions of 644. > Setting the new permissions to that of the old fixed the problem. Thanks. > > Rob. > From owner-freebsd-stable@FreeBSD.ORG Fri May 16 07:39:35 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B1AB21065678 for ; Fri, 16 May 2008 07:39:35 +0000 (UTC) (envelope-from emikulic@gmail.com) Received: from ipmail01.adl6.internode.on.net (ipmail01.adl6.internode.on.net [203.16.214.146]) by mx1.freebsd.org (Postfix) with ESMTP id 44E048FC20 for ; Fri, 16 May 2008 07:39:34 +0000 (UTC) (envelope-from emikulic@gmail.com) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApsEANbULEiWZaK6/2dsb2JhbACLAqNf X-IronPort-AV: E=Sophos;i="4.27,496,1204464600"; d="scan'208";a="103712506" Received: from ppp162-186.static.internode.on.net ([150.101.162.186]) by ipmail01.adl6.internode.on.net with ESMTP; 16 May 2008 17:09:33 +0930 Received: by ppp162-186.static.internode.on.net (Poofix, from userid 1001) id 9C35E409F; Fri, 16 May 2008 17:39:32 +1000 (EST) Date: Fri, 16 May 2008 17:39:32 +1000 From: Emil Mikulic To: freebsd-stable@freebsd.org Message-ID: <20080516073932.GA39803@dmr.ath.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.17 (2007-11-01) Subject: ciss(4) not coping with large arrays? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2008 07:39:35 -0000 Hi all, Running today's RELENG_7 (although 7.0-RELEASE has the same problem), GENERIC kernel on an amd64 and I can't seem to get a da(4) device for any arrays bigger than 2TB. dmesg: <...> ciss0: port 0x4000-0x40ff mem 0xfdf00000-0xfdffffff,0xfdef 0000-0xfdef0fff irq 16 at device 0.0 on pci10 ciss0: [ITHREAD] <...> da0 at ciss0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-5 device da0: 135.168MB/s transfers da0: 953837MB (1953459632 512 byte sectors: 255H 32S/T 65535C) da1 at ciss0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-5 device da1: 135.168MB/s transfers da1: 953837MB (1953459632 512 byte sectors: 255H 32S/T 65535C) da2 at ciss0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-5 device da2: 135.168MB/s transfers da2: 1907675MB (3906918832 512 byte sectors: 255H 32S/T 65535C) (da3:ciss0:0:3:0): got CAM status 0x4 (da3:ciss0:0:3:0): fatal error, failed to attach to device (da3:ciss0:0:3:0): lost device (da3:ciss0:0:3:0): removing device entry (da4:ciss0:0:4:0): got CAM status 0x4 (da4:ciss0:0:4:0): fatal error, failed to attach to device (da4:ciss0:0:4:0): lost device (da4:ciss0:0:4:0): removing device entry <...> The arrays I'm testing with: da1 = 1 x 1TB da2 = 2 x 1TB da3 = 3 x 1TB da4 = 4 x 1TB Also: # camcontrol devlist at scbus0 target 0 lun 0 (pass0,da0) at scbus0 target 1 lun 0 (pass1,da1) at scbus0 target 2 lun 0 (pass2,da2) at scbus0 target 3 lun 0 (pass3) at scbus0 target 4 lun 0 (pass4) # camcontrol readcap pass2 Last Block: 3906918831, Block Length: 512 bytes # camcontrol readcap pass3 (pass3:ciss0:0:3:0): SERVICE ACTION IN(16). CDB: 9e 10 0 0 0 0 0 0 0 0 0 0 0 c 0 0 (pass3:ciss0:0:3:0): CAM Status: CCB request completed with an error Is it possible to get FreeBSD to recognize arrays > 2TB? Are there any further diagnostics I can provide? --Emil From owner-freebsd-stable@FreeBSD.ORG Fri May 16 07:50:13 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7BA18106564A for ; Fri, 16 May 2008 07:50:13 +0000 (UTC) (envelope-from kometen@gmail.com) Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.186]) by mx1.freebsd.org (Postfix) with ESMTP id F32F28FC16 for ; Fri, 16 May 2008 07:50:12 +0000 (UTC) (envelope-from kometen@gmail.com) Received: by fk-out-0910.google.com with SMTP id k31so656826fkk.11 for ; Fri, 16 May 2008 00:50:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=Tvf4fbs60MB1XIv4Y3VsYgpGcK3FVKwwIn+roINkHIg=; b=KUB0Bf4wTNezPRtXD+a1DPgBOjEYzIQ/jf9PS3TkkAVed4kacEXwPOigQl0G4xo/NOghjuo+4p1cx1dSeSQinyoDC21FPTeejq7g7uAf+RPUtLOQ5SPPXD2EYqcpobfv56CoJFJKpeK8KulC15rwLvRGKicoUxUsrRfqPSpEt38= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=AZNSdTVRm6ky9wi7qzqW9WNDFJyTvZMQ2RYRKT5Qx+7hZm5eomeImYy22wPgktI22aOLqibZBGE76a11mA+rTpmd/PLXWEdCd5DZ00V9yTGvG/YP40Nn9hRGiNaTuZyaQV3muHuZEGLVOGXgb415IBiOluyuGiIE6sTG0VCWfFc= Received: by 10.125.93.13 with SMTP id v13mr2222717mkl.75.1210924210988; Fri, 16 May 2008 00:50:10 -0700 (PDT) Received: by 10.86.81.6 with HTTP; Fri, 16 May 2008 00:50:10 -0700 (PDT) Message-ID: Date: Fri, 16 May 2008 09:50:10 +0200 From: "Claus Guttesen" To: "Emil Mikulic" In-Reply-To: <20080516073932.GA39803@dmr.ath.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080516073932.GA39803@dmr.ath.cx> Cc: freebsd-stable@freebsd.org Subject: Re: ciss(4) not coping with large arrays? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2008 07:50:13 -0000 > Running today's RELENG_7 (although 7.0-RELEASE has the same problem), > GENERIC kernel on an amd64 and I can't seem to get a da(4) device for > any arrays bigger than 2TB. In earlier releases (5 and 6 at least) you couldn't create partitions larger than 2 TB. I don't know whether work has been to circumvent this in 7 but tools like fsck has to be changed as well. Have you tried zfs? > dmesg: > <...> > ciss0: port 0x4000-0x40ff mem 0xfdf00000-0xfdffffff,0xfdef > 0000-0xfdef0fff irq 16 at device 0.0 on pci10 > ciss0: [ITHREAD] > <...> > da0 at ciss0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-5 device > da0: 135.168MB/s transfers > da0: 953837MB (1953459632 512 byte sectors: 255H 32S/T 65535C) > da1 at ciss0 bus 0 target 1 lun 0 > da1: Fixed Direct Access SCSI-5 device > da1: 135.168MB/s transfers > da1: 953837MB (1953459632 512 byte sectors: 255H 32S/T 65535C) > da2 at ciss0 bus 0 target 2 lun 0 > da2: Fixed Direct Access SCSI-5 device > da2: 135.168MB/s transfers > da2: 1907675MB (3906918832 512 byte sectors: 255H 32S/T 65535C) > (da3:ciss0:0:3:0): got CAM status 0x4 > (da3:ciss0:0:3:0): fatal error, failed to attach to device > (da3:ciss0:0:3:0): lost device > (da3:ciss0:0:3:0): removing device entry > (da4:ciss0:0:4:0): got CAM status 0x4 > (da4:ciss0:0:4:0): fatal error, failed to attach to device > (da4:ciss0:0:4:0): lost device > (da4:ciss0:0:4:0): removing device entry > <...> > > The arrays I'm testing with: > da1 = 1 x 1TB > da2 = 2 x 1TB > da3 = 3 x 1TB > da4 = 4 x 1TB > > Also: > # camcontrol devlist > at scbus0 target 0 lun 0 (pass0,da0) > at scbus0 target 1 lun 0 (pass1,da1) > at scbus0 target 2 lun 0 (pass2,da2) > at scbus0 target 3 lun 0 (pass3) > at scbus0 target 4 lun 0 (pass4) > # camcontrol readcap pass2 > Last Block: 3906918831, Block Length: 512 bytes > # camcontrol readcap pass3 > (pass3:ciss0:0:3:0): SERVICE ACTION IN(16). CDB: 9e 10 0 0 0 0 0 0 0 0 0 0 0 c 0 0 > (pass3:ciss0:0:3:0): CAM Status: CCB request completed with an error > > Is it possible to get FreeBSD to recognize arrays > 2TB? > Are there any further diagnostics I can provide? > > --Emil > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > -- regards Claus When lenity and cruelty play for a kingdom, the gentlest gamester is the soonest winner. Shakespeare From owner-freebsd-stable@FreeBSD.ORG Fri May 16 08:19:34 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D4424106567E for ; Fri, 16 May 2008 08:19:34 +0000 (UTC) (envelope-from paul.m.saab@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.230]) by mx1.freebsd.org (Postfix) with ESMTP id A3A308FC2B for ; Fri, 16 May 2008 08:19:34 +0000 (UTC) (envelope-from paul.m.saab@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so74317rvf.43 for ; Fri, 16 May 2008 01:19:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:references:x-google-sender-auth; bh=UNq/U8fR9h76+RexJWF2V+G95CeFNcXpl3m3NVHSGfQ=; b=hdybIRIA7xg9Z6vQns5JXn7U46mV8USYTt0kkAWoNx1KuX+oFt9Nb/h9r5JUVMS/o3SqdrThORIxbdmBaRjCI89HwBMXRy14GoPr66p0f8VDf95NHZFMybhkh4o9/OjMiL5rjt0r6KtW0M2rAmDKGR2DbTHkQuR6LCBfoUPt5vs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=iWBq6nY9fwLTonBYpXrrecvd5he/c6UJu6YJEkZJB+HES/XRGsdBXzaSNKntWOVz4MtzAI0B/2zrT08M4kSxYjsWhJJjbGuv0dQxPvCsrIW+Ig+NgVKKA4JZSJYFEj6K6uRQ6Zhxm9pFj4CZFB+crdlpSMpa5jX5/s33ug4Unbs= Received: by 10.141.43.19 with SMTP id v19mr1631156rvj.154.1210925973323; Fri, 16 May 2008 01:19:33 -0700 (PDT) Received: by 10.140.141.12 with HTTP; Fri, 16 May 2008 01:19:33 -0700 (PDT) Message-ID: <5c0ff6a70805160119n2f8361c4y7b3c1451f36d3c6e@mail.gmail.com> Date: Fri, 16 May 2008 01:19:33 -0700 From: "Paul Saab" Sender: paul.m.saab@gmail.com To: "Claus Guttesen" In-Reply-To: <5c0ff6a70805160103o75461976wce04f697975a176c@mail.gmail.com> MIME-Version: 1.0 References: <20080516073932.GA39803@dmr.ath.cx> <5c0ff6a70805160103o75461976wce04f697975a176c@mail.gmail.com> X-Google-Sender-Auth: aac3554f8be974e6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org, Emil Mikulic Subject: Re: ciss(4) not coping with large arrays? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2008 08:19:34 -0000 On Fri, May 16, 2008 at 1:03 AM, Paul Saab wrote: > On Fri, May 16, 2008 at 12:50 AM, Claus Guttesen > wrote: > >> > Running today's RELENG_7 (although 7.0-RELEASE has the same problem), >> > GENERIC kernel on an amd64 and I can't seem to get a da(4) device for >> > any arrays bigger than 2TB. >> >> In earlier releases (5 and 6 at least) you couldn't create partitions >> larger than 2 TB. I don't know whether work has been to circumvent >> this in 7 but tools like fsck has to be changed as well. Have you >> tried zfs? > > > zfs has nothing to do with this. The driver is not properly dealing with > the large volume. > > set the kernel tunable in loader.conf > > kern.cam.da.3.minimum_cmd_size=16 > kern.cam.da.4.minimum_cmd_size=16 > > Actually, this has nothing to do with it either.. Please try the following patch: http://yogurt.org/FreeBSD/ciss_large.diff From owner-freebsd-stable@FreeBSD.ORG Fri May 16 08:27:22 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EE056106567A for ; Fri, 16 May 2008 08:27:22 +0000 (UTC) (envelope-from paul.m.saab@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.233]) by mx1.freebsd.org (Postfix) with ESMTP id BDDA18FC29 for ; Fri, 16 May 2008 08:27:22 +0000 (UTC) (envelope-from paul.m.saab@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so77763rvf.43 for ; Fri, 16 May 2008 01:27:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:references:x-google-sender-auth; bh=q2RM05wneK0iEM5hiGL5Yguzv/tyMgfivBUm5zKbo/E=; b=kqXmcgQxCAqoYtWP6iWyeazuEwAtNppYg0N5dYHXHOw9CIRZltAdVcMXlRo2janSrNlA4+uKPCIfs/abgmLl8w0aylnDVkFD3+ey4TQWBww8MZ0/b8cb/Fshfe33bJnDp4CZ7IpEDfDE3eRNfBT9CVkiVIt8MXfh++/MXV4wEXk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=kux9ZGBu3txBcEs3K7N5uX7al7zKDNDMapy2ittCamikup7lxC/ueew0+vZI0eIC6f9hD1XmvcBuKSTQhqpHF8eOnPNuFQDQJIwd1gukaXpvHlJ6yB0ccMfbvGrbPUqJuo5BeKb5IKcUUquSycBbZpXbo5dBfagNXJNXX8Tk+Ck= Received: by 10.141.193.1 with SMTP id v1mr1630201rvp.73.1210924994470; Fri, 16 May 2008 01:03:14 -0700 (PDT) Received: by 10.140.141.12 with HTTP; Fri, 16 May 2008 01:03:14 -0700 (PDT) Message-ID: <5c0ff6a70805160103o75461976wce04f697975a176c@mail.gmail.com> Date: Fri, 16 May 2008 01:03:14 -0700 From: "Paul Saab" Sender: paul.m.saab@gmail.com To: "Claus Guttesen" In-Reply-To: MIME-Version: 1.0 References: <20080516073932.GA39803@dmr.ath.cx> X-Google-Sender-Auth: 622c88e7b67355b5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org, Emil Mikulic Subject: Re: ciss(4) not coping with large arrays? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2008 08:27:23 -0000 On Fri, May 16, 2008 at 12:50 AM, Claus Guttesen wrote: > > Running today's RELENG_7 (although 7.0-RELEASE has the same problem), > > GENERIC kernel on an amd64 and I can't seem to get a da(4) device for > > any arrays bigger than 2TB. > > In earlier releases (5 and 6 at least) you couldn't create partitions > larger than 2 TB. I don't know whether work has been to circumvent > this in 7 but tools like fsck has to be changed as well. Have you > tried zfs? zfs has nothing to do with this. The driver is not properly dealing with the large volume. set the kernel tunable in loader.conf kern.cam.da.3.minimum_cmd_size=16 kern.cam.da.4.minimum_cmd_size=16 From owner-freebsd-stable@FreeBSD.ORG Fri May 16 08:34:00 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6AD5B1065677 for ; Fri, 16 May 2008 08:34:00 +0000 (UTC) (envelope-from freebsdlists@bsdunix.ch) Received: from conversation.bsdunix.ch (ns1.bsdunix.ch [82.220.1.90]) by mx1.freebsd.org (Postfix) with ESMTP id 9B8A28FC1C for ; Fri, 16 May 2008 08:33:59 +0000 (UTC) (envelope-from freebsdlists@bsdunix.ch) Received: from localhost (localhost.bsdunix.ch [127.0.0.1]) by conversation.bsdunix.ch (Postfix) with ESMTP id 977255E04 for ; Fri, 16 May 2008 10:17:38 +0200 (CEST) X-Virus-Scanned: by amavisd-new at mail.bsdunix.ch Received: from conversation.bsdunix.ch ([127.0.0.1]) by localhost (conversation.bsdunix.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id aMkMTSVYEtRd for ; Fri, 16 May 2008 10:17:38 +0200 (CEST) Received: from [192.168.1.105] (home.bsdunix.ch [82.220.17.23]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by conversation.bsdunix.ch (Postfix) with ESMTP id 03D3D5D8B for ; Fri, 16 May 2008 10:17:37 +0200 (CEST) Message-Id: <65DED12A-0263-4281-ADAC-CBF2A7857D5E@bsdunix.ch> From: Thomas Vogt To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v919.2) Date: Fri, 16 May 2008 10:17:37 +0200 X-Mailer: Apple Mail (2.919.2) Subject: Timedia 8 port serial pci card problem X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2008 08:34:00 -0000 Hello I run FreeBSD 7-Stable on my soekris net 5501 with a "8 Port Timedia Serial PCI Card". It's also know as SUNIX 4066 card. My Kernel Config is like Generic exept this two added options: options CPU_SOEKRIS device puc FreeBSD detects it with: "puc0: port 0xe500-0xe51f,0xe520-0xe52f,0xe530-0xe537,0xe538-0xe53f, 0xe540-0xe547,0xe548-0xe54f irq 10 at device 14.0 on pci0" . But it only adds 3 uart ports instead of 8. Any idea what i can do? Maybe useful informations: FreeBSD a2.test.lan 7.0-STABLE FreeBSD 7.0-STABLE #4: Thu May 15 16:27:54 CEST 2008 pciconf: puc0@pci0:0:14:0: class=0x070002 card=0x50661409 chip=0x71681409 rev=0x01 hdr=0x00 vendor = 'Timedia Technology Co Ltd' device = '40371409 PCI / ISA Asynchronous UART Signal Chips Solution' class = simple comms subclass = UART puc/uart: puc0: port 0xe500-0xe51f, 0xe520-0xe52f,0xe530-0xe537,0xe538-0xe53f,0xe540-0xe547,0xe548-0xe54f irq 10 at device 14.0 on pci0 puc0: Reserved 0x20 bytes for rid 0x10 type 4 at 0xe500 puc0: Lazy allocation of 0x4 bytes rid 0x11 type 4 at 0x1000 puc0: Lazy allocation of 0x4 bytes rid 0x12 type 4 at 0x1004 puc0: Lazy allocation of 0x4 bytes rid 0x13 type 4 at 0x1008 puc0: Reserved 0x10 bytes for rid 0x14 type 4 at 0xe520 puc0: Lazy allocation of 0x4 bytes rid 0x15 type 4 at 0x100c puc0: [FILTER] uart0: on puc0 uart0: [FILTER] uart0: fast interrupt uart1: <16550 or compatible> on puc0 uart1: [FILTER] uart1: fast interrupt uart2: on puc0 uart2: [FILTER] uart2: fast interrupt Complete dmesg: Copyright (c) 1992-2008 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.0-STABLE #4: Thu May 15 16:27:54 CEST 2008 root@bert.mlan.solnet.ch:/usr/obj/usr/src/sys/ULL Preloaded elf kernel "/boot/kernel/kernel" at 0xc0905000. Calibrating clock(s) ... i8254 clock: 1193155 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 499904707 Hz CPU: Geode(TM) Integrated Processor by AMD PCS (499.90-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x5a2 Stepping = 2 Features=0x88a93d AMD Features=0xc0400000 Data TLB: 16 entries, fully associative Instruction TLB: 16 entries, fully associative L1 data cache: 64 kbytes, 32 bytes/line, 1 lines/tag, 16-way associative L1 instruction cache: 64 kbytes, 32 bytes/line, 1 lines/tag, 16-way associative L2 internal cache: 128 kbytes, 32 bytes/line, 1 lines/tag, 4-way associative Write Allocate Disable real memory = 536870912 (512 MB) Physical memory chunk(s): 0x0000000000001000 - 0x000000000009efff, 647168 bytes (158 pages) 0x0000000000100000 - 0x00000000003fffff, 3145728 bytes (768 pages) 0x0000000000c25000 - 0x000000001f6bbfff, 514420736 bytes (125591 pages) avail memory = 515969024 (492 MB) bios32: Found BIOS32 Service Directory header at 0xc00fac00 bios32: Entry = 0xfac40 (c00fac40) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf0000+0xac61 Other BIOS signatures found: ULE: setup cpu 0 kbd: new array size 4 kbd1 at kbdmux0 nfslock: pseudo-device random: mem: K6-family MTRR support enabled (2 registers) io: null: npx0: INT 16 interface cpu0 on motherboard pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 1 [class=060000] [hdr=80] is there (id=20801022) pcibios: BIOS version 2.01 pcib0: pcibus 0 on motherboard pci0: on pcib0 pci0: domain=0, physical bus=0 found-> vendor=0x1022, dev=0x2080, revid=0x31 domain=0, bus=0, slot=1, func=0 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0005, statreg=0x0220, cachelnsz=8 (dwords) lattimer=0xf8 (7440 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x2082, revid=0x00 domain=0, bus=0, slot=1, func=2 class=10-10-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x0220, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=10 map[10]: type Memory, range 32, base 0xa0000000, size 14, enabled found-> vendor=0x1106, dev=0x3053, revid=0x96 domain=0, bus=0, slot=6, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0117, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0x40 (1920 ns), mingnt=0x03 (750 ns), maxlat=0x08 (2000 ns) intpin=a, irq=11 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type I/O Port, range 32, base 0xe100, size 8, enabled map[14]: type Memory, range 32, base 0xa0004000, size 8, enabled found-> vendor=0x1106, dev=0x3053, revid=0x96 domain=0, bus=0, slot=7, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0117, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0x40 (1920 ns), mingnt=0x03 (750 ns), maxlat=0x08 (2000 ns) intpin=a, irq=5 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type I/O Port, range 32, base 0xe200, size 8, enabled map[14]: type Memory, range 32, base 0xa0004100, size 8, enabled found-> vendor=0x1106, dev=0x3053, revid=0x96 domain=0, bus=0, slot=8, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0117, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0x40 (1920 ns), mingnt=0x03 (750 ns), maxlat=0x08 (2000 ns) intpin=a, irq=9 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type I/O Port, range 32, base 0xe300, size 8, enabled map[14]: type Memory, range 32, base 0xa0004200, size 8, enabled found-> vendor=0x1106, dev=0x3053, revid=0x96 domain=0, bus=0, slot=9, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0117, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0x40 (1920 ns), mingnt=0x03 (750 ns), maxlat=0x08 (2000 ns) intpin=a, irq=12 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type I/O Port, range 32, base 0xe400, size 8, enabled map[14]: type Memory, range 32, base 0xa0004300, size 8, enabled found-> vendor=0x1409, dev=0x7168, revid=0x01 domain=0, bus=0, slot=14, func=0 class=07-00-02, hdrtype=0x00, mfdev=0 cmdreg=0x0181, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=10 map[10]: type I/O Port, range 32, base 0xe500, size 5, enabled map[14]: type I/O Port, range 32, base 0xe520, size 4, enabled map[18]: type I/O Port, range 32, base 0xe530, size 3, enabled map[1c]: type I/O Port, range 32, base 0xe538, size 3, enabled map[20]: type I/O Port, range 32, base 0xe540, size 3, enabled map[24]: type I/O Port, range 32, base 0xe548, size 3, enabled found-> vendor=0x1022, dev=0x2090, revid=0x03 domain=0, bus=0, slot=20, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x0009, statreg=0x02a0, cachelnsz=8 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[10]: type I/O Port, range 32, base 0x6000, size 13, enabled map[14]: type I/O Port, range 32, base 0x6100, size 8, enabled map[18]: type I/O Port, range 32, base 0x6200, size 9, enabled found-> vendor=0x1022, dev=0x209a, revid=0x01 domain=0, bus=0, slot=20, func=2 class=01-01-80, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x02a0, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[20]: type I/O Port, range 32, base 0xe000, size 4, enabled found-> vendor=0x1022, dev=0x2094, revid=0x02 domain=0, bus=0, slot=21, func=0 class=0c-03-10, hdrtype=0x00, mfdev=1 cmdreg=0x0006, statreg=0x0230, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=15 map[10]: type Memory, range 32, base 0xa0005000, size 12, enabled found-> vendor=0x1022, dev=0x2095, revid=0x02 domain=0, bus=0, slot=21, func=1 class=0c-03-20, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x0230, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=15 map[10]: type Memory, range 32, base 0xa0006000, size 12, enabled pci0: at device 1.2 (no driver attached) vr0: port 0xe100-0xe1ff mem 0xa0004000-0xa00040ff irq 11 at device 6.0 on pci0 vr0: Quirks: 0x6 vr0: Revision: 0x96 vr0: Reserved 0x100 bytes for rid 0x10 type 4 at 0xe100 miibus0: on vr0 ukphy0: PHY 1 on miibus0 ukphy0: OUI 0x004063, model 0x0034, rev. 3 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto vr0: bpf attached vr0: Ethernet address: 00:00:24:ca:0a:d8 vr0: [MPSAFE] vr0: [ITHREAD] vr1: port 0xe200-0xe2ff mem 0xa0004100-0xa00041ff irq 5 at device 7.0 on pci0 vr1: Quirks: 0x6 vr1: Revision: 0x96 vr1: Reserved 0x100 bytes for rid 0x10 type 4 at 0xe200 miibus1: on vr1 ukphy1: PHY 1 on miibus1 ukphy1: OUI 0x004063, model 0x0034, rev. 3 ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto vr1: bpf attached vr1: Ethernet address: 00:00:24:ca:0a:d9 vr1: [MPSAFE] vr1: [ITHREAD] vr2: port 0xe300-0xe3ff mem 0xa0004200-0xa00042ff irq 9 at device 8.0 on pci0 vr2: Quirks: 0x6 vr2: Revision: 0x96 vr2: Reserved 0x100 bytes for rid 0x10 type 4 at 0xe300 miibus2: on vr2 ukphy2: PHY 1 on miibus2 ukphy2: OUI 0x004063, model 0x0034, rev. 3 ukphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto vr2: bpf attached vr2: Ethernet address: 00:00:24:ca:0a:da vr2: [MPSAFE] vr2: [ITHREAD] vr3: port 0xe400-0xe4ff mem 0xa0004300-0xa00043ff irq 12 at device 9.0 on pci0 vr3: Quirks: 0x6 vr3: Revision: 0x96 vr3: Reserved 0x100 bytes for rid 0x10 type 4 at 0xe400 miibus3: on vr3 ukphy3: PHY 1 on miibus3 ukphy3: OUI 0x004063, model 0x0034, rev. 3 ukphy3: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto vr3: bpf attached vr3: Ethernet address: 00:00:24:ca:0a:db vr3: [MPSAFE] vr3: [ITHREAD] puc0: port 0xe500-0xe51f, 0xe520-0xe52f,0xe530-0xe537,0xe538-0xe53f,0xe540-0xe547,0xe548-0xe54f irq 10 at device 14.0 on pci0 puc0: Reserved 0x20 bytes for rid 0x10 type 4 at 0xe500 puc0: Lazy allocation of 0x4 bytes rid 0x11 type 4 at 0x1000 puc0: Lazy allocation of 0x4 bytes rid 0x12 type 4 at 0x1004 puc0: Lazy allocation of 0x4 bytes rid 0x13 type 4 at 0x1008 puc0: Reserved 0x10 bytes for rid 0x14 type 4 at 0xe520 puc0: Lazy allocation of 0x4 bytes rid 0x15 type 4 at 0x100c puc0: [FILTER] uart0: on puc0 uart0: [FILTER] uart0: fast interrupt uart1: <16550 or compatible> on puc0 uart1: [FILTER] uart1: fast interrupt uart2: on puc0 uart2: [FILTER] uart2: fast interrupt isab0: at device 20.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xe000-0xe00f at device 20.2 on pci0 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xe000 ata0: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 atapci0: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 ata0: reset tp1 mask=03 ostat0=50 ostat1=00 ata0: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata0: stat1=0x00 err=0x01 lsb=0x00 msb=0x00 ata0: reset tp2 stat0=50 stat1=00 devices=0x1 ata0: [MPSAFE] ata0: [ITHREAD] ata1: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170 atapci0: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376 ata1: reset tp1 mask=00 ostat0=ff ostat1=ff ata1: [MPSAFE] ata1: [ITHREAD] ohci0: mem 0xa0005000-0xa0005fff irq 15 at device 21.0 on pci0 ohci0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xa0005000 ohci0: [GIANT-LOCKED] ohci0: [ITHREAD] usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 4 ports with 4 removable, self powered ehci0: mem 0xa0006000-0xa0006fff irq 15 at device 21.1 on pci0 ehci0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xa0006000 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb1: EHCI version 1.0 usb1: companion controller, 4 ports each: usb0 usb1: on ehci0 usb1: USB revision 2.0 uhub1: on usb1 uhub1: 4 ports with 4 removable, self powered ata: ata0 already exists; skipping it ata: ata1 already exists; skipping it pnp_identify: Trying Read_Port at 203 pnp_identify: Trying Read_Port at 243 pnp_identify: Trying Read_Port at 283 pnp_identify: Trying Read_Port at 2c3 pnp_identify: Trying Read_Port at 303 pnp_identify: Trying Read_Port at 343 pnp_identify: Trying Read_Port at 383 pnp_identify: Trying Read_Port at 3c3 PNP Identify complete sc: sc0 already exists; skipping it vga: vga0 already exists; skipping it isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices pmtimer0 on isa0 orm0: at iomem 0xc8000-0xd27ff pnpid ORM0000 on isa0 adv0: not probed (disabled) aha0: not probed (disabled) aic0: not probed (disabled) atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 kbd0: atkbd0, generic (0), config:0x0, flags:0x1f0000 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: current command byte:004d psm0: failed to reset the aux device. bt0: not probed (disabled) cs0: not probed (disabled) ed0: not probed (disabled) fdc0 failed to probe at port 0x3f0 irq 6 drq 2 on isa0 fe0: not probed (disabled) ie0: not probed (disabled) le0: not probed (disabled) ppc0 failed to probe at irq 7 on isa0 sc0: no video adapter found. sc0: failed to probe on isa0 sio0: irq maps: 0x8001 0x8011 0x8001 0x8001 sio0: irq maps: 0x8001 0x8011 0x8001 0x8001 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A, console sio0: [FILTER] sio1: irq maps: 0x8001 0x8009 0x8001 0x8001 sio1: irq maps: 0x8001 0x8009 0x8001 0x8001 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio1: [FILTER] sio2: not probed (disabled) sio3: not probed (disabled) sn0: not probed (disabled) vga0: failed to probe on isa0 vt0: not probed (disabled) isa_probe_children: probing PnP devices Device configuration finished. procfs registered Timecounter "TSC" frequency 499904707 Hz quality 800 Timecounters tick every 6.666 msec ipfw2 (+ipv6) initialized, divert loadable, nat loadable, rule-based forwarding enabled, default to accept, logging limited to 100 packets/ entry by default lo0: bpf attached ata0-master: pio=PIO4 wdma=WDMA2 udma=UNSUPPORTED cable=40 wire atapicam: atapicam0 already exists; skipping it ad0: setting PIO4 on CS5536 chip ad0: setting WDMA2 on CS5536 chip ad0: 1953MB at ata0-master WDMA2 ad0: 4001760 sectors [3970C/16H/63S] 4 sectors/interrupt 1 depth queue GEOM: new disk ad0 Trying to mount root from ufs:/dev/ad0s1a Invalid time in clock: check and reset the date! start_init: trying /sbin/init 15.fe8155ebfe6e5152 too short 15.fe8168502ce320aa too short Regards, Thomas Vogt From owner-freebsd-stable@FreeBSD.ORG Fri May 16 08:46:51 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 306E61065670 for ; Fri, 16 May 2008 08:46:51 +0000 (UTC) (envelope-from kometen@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.158]) by mx1.freebsd.org (Postfix) with ESMTP id B564F8FC0C for ; Fri, 16 May 2008 08:46:50 +0000 (UTC) (envelope-from kometen@gmail.com) Received: by fg-out-1718.google.com with SMTP id l26so819367fgb.35 for ; Fri, 16 May 2008 01:46:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=FK9/Kx+E1MDiS2daHQPdd8XypsaXLOzKz2XsyqlvUZ4=; b=Xp+ZYrhXhSHkFy0yWDfBZMlOJSlX7vlEfOeKUhUPJdaXxaXrPtGvVqZ+ILv6lFsXmUAklTRh+WHG0uu/yjZ2KPiciBpH+tmqdXvpOAsLdCcq7q6B9p6KrUBaQmUP3/nUP5E9WhN8xTrHxY0Eoy/iV6qPzRW1MWay4o3JQdb6Of4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=haJwDGOdOZVrPWEWLwf/Ya1pETlSvwsprDWCv7bDQJhTgdOzJLT8fm4S8Wwf0hdPHDfb0UcB7MkqL9/R2MklGZiDoklIdwc2A+iaS8Z1sq0hRKYNZSXTvQQxOVWZWrNAbEKY2gGr+2Ysi5vpfPGgwWgqo0ZLJyWsBoVqOP5sxQE= Received: by 10.124.66.14 with SMTP id o14mr2282082mka.176.1210927609625; Fri, 16 May 2008 01:46:49 -0700 (PDT) Received: by 10.86.81.6 with HTTP; Fri, 16 May 2008 01:46:49 -0700 (PDT) Message-ID: Date: Fri, 16 May 2008 10:46:49 +0200 From: "Claus Guttesen" To: "Paul Saab" In-Reply-To: <5c0ff6a70805160103o75461976wce04f697975a176c@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080516073932.GA39803@dmr.ath.cx> <5c0ff6a70805160103o75461976wce04f697975a176c@mail.gmail.com> Cc: freebsd-stable@freebsd.org, Emil Mikulic Subject: Re: ciss(4) not coping with large arrays? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2008 08:46:51 -0000 >> In earlier releases (5 and 6 at least) you couldn't create partitions >> larger than 2 TB. I don't know whether work has been to circumvent >> this in 7 but tools like fsck has to be changed as well. Have you >> tried zfs? > > zfs has nothing to do with this. The driver is not properly dealing with > the large volume. > set the kernel tunable in loader.conf > kern.cam.da.3.minimum_cmd_size=16 > kern.cam.da.4.minimum_cmd_size=16 Yes, of course. I was off-course. :-) -- regards Claus When lenity and cruelty play for a kingdom, the gentlest gamester is the soonest winner. Shakespeare From owner-freebsd-stable@FreeBSD.ORG Fri May 16 09:37:11 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4F0EF1065678 for ; Fri, 16 May 2008 09:37:11 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 3F3788FC12 for ; Fri, 16 May 2008 09:37:11 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 319AB1CC05B; Fri, 16 May 2008 02:37:11 -0700 (PDT) Date: Fri, 16 May 2008 02:37:11 -0700 From: Jeremy Chadwick To: Rob Lytle Message-ID: <20080516093711.GA55422@eos.sc1.parodius.com> References: <784966050805160013w7d3ec31euc95be9e4a0a68fa9@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <784966050805160013w7d3ec31euc95be9e4a0a68fa9@mail.gmail.com> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-stable@freebsd.org Subject: Re: just one last question about /etc/rc.d file permissions X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2008 09:37:11 -0000 On Fri, May 16, 2008 at 12:13:19AM -0700, Rob Lytle wrote: > Hi Jeremy, > > I noticed that most all of the files in my old /etc/rc.d had 555 > permissions. There were 4 or 5 that had 644 permissions in my old > /etc/rc.d. What I am wondering is if all the files in rc.d should be > 555? So far I am not experiencing any problems with anything with a > very few 644 files. Yes, they all should be. On our RELENG_6 and RELENG_7 systems they are. I wonder if part of the problem is that your umask was set oddly before running mergemaster, or possibly even when doing your csup. It should be 022. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Fri May 16 10:53:27 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 460DC106566B for ; Fri, 16 May 2008 10:53:27 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from smtpoutm.mac.com (smtpoutm.mac.com [17.148.16.77]) by mx1.freebsd.org (Postfix) with ESMTP id 0ACBD8FC18 for ; Fri, 16 May 2008 10:53:27 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from smtpin125.mac.com (smtpin125-bge351000 [10.150.68.125]) by smtpoutm.mac.com (Xserve/smtpout014/MantshX 4.0) with ESMTP id m4GArQkM022771 for ; Fri, 16 May 2008 03:53:26 -0700 (PDT) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Received: from [192.168.2.70] ([24.114.252.230]) by smtpin125.mac.com (Sun Java(tm) System Messaging Server 6.3-6.03 (built Mar 14 2008; 32bit)) with ESMTPSA id <0K0Y00G0RJL1YG30@smtpin125.mac.com> for freebsd-stable@freebsd.org; Fri, 16 May 2008 03:53:26 -0700 (PDT) Message-id: <7C738CA6-9F66-44B4-A1AF-9CC3F80DB6BC@mac.com> From: Marcel Moolenaar To: Thomas Vogt In-reply-to: <65DED12A-0263-4281-ADAC-CBF2A7857D5E@bsdunix.ch> Date: Fri, 16 May 2008 03:53:24 -0700 References: <65DED12A-0263-4281-ADAC-CBF2A7857D5E@bsdunix.ch> X-Mailer: Apple Mail (2.919.2) Cc: freebsd-stable@freebsd.org Subject: Re: Timedia 8 port serial pci card problem X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2008 10:53:27 -0000 On May 16, 2008, at 1:17 AM, Thomas Vogt wrote: > FreeBSD detects it with: "puc0: > port 0xe500-0xe51f,0xe520-0xe52f,0xe530-0xe537,0xe538-0xe53f, > 0xe540-0xe547,0xe548-0xe54f irq 10 at device 14.0 on pci0" . But it > only adds 3 uart ports instead of 8. Any idea what i can do? Can you try the following (white-space corrupted) patch: Index: pucdata.c =================================================================== RCS file: /home/ncvs/src/sys/dev/puc/pucdata.c,v retrieving revision 1.59.2.1 diff -u -r1.59.2.1 pucdata.c --- pucdata.c 26 Feb 2008 09:33:57 -0000 1.59.2.1 +++ pucdata.c 16 May 2008 10:48:25 -0000 @@ -1116,7 +1116,7 @@ *res = (port == 1 || port == 3) ? 8 : 0; return (0); case PUC_CFG_GET_RID: - *res = 0x10 + ((port > 3) ? port - 2 : port >> 1); + *res = 0x10 + ((port > 3) ? port - 2 : port >> 1) * 4; return (0); case PUC_CFG_GET_TYPE: *res = PUC_TYPE_SERIAL; -- Marcel Moolenaar xcllnt@mac.com From owner-freebsd-stable@FreeBSD.ORG Fri May 16 10:59:00 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AE3A1106566B for ; Fri, 16 May 2008 10:59:00 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from ftp.translate.ru (ftp.translate.ru [195.131.4.140]) by mx1.freebsd.org (Postfix) with ESMTP id 6828D8FC18 for ; Fri, 16 May 2008 10:59:00 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from [192.18.98.62] (brmea-proxy-1.Sun.COM [192.18.98.62]) (Authenticated sender: lev@serebryakov.spb.ru) by ftp.translate.ru (Postfix) with ESMTPA id EABBA13DF53 for ; Fri, 16 May 2008 14:40:36 +0400 (MSD) Message-ID: <482D6492.8080209@FreeBSD.org> Date: Fri, 16 May 2008 14:40:18 +0400 From: Lev Serebryakov Organization: FreeBSD Project User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.14) Gecko/20071210 Thunderbird/1.5.0.14 Mnenhy/0.7.4.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Subject: FreeBSD 7.0-STABLE: "mount_nfs" vs "mount -t nfs": problems with second one, UDP timeouts and ICMP ports unreach?! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2008 10:59:00 -0000 I have two hosts: host A (FreeBSD 6.3-S) and host B (FreeBSD 7.0-S, freshly installed). Host A exports "/usr/ports" to host B via NFS. Mount with "mount_nfs" works well: b# mount_nfs a:/usr/ports /usr/ports b# ls /usr/ports [---SKIPPED---= b# But mount with "mount -t nfs" FAILS: b# mount -t nfs a:/usr/ports /usr/ports [udp] a:/usr/ports: NFSPROC_NULL: RPC: Timed out [udp] a:/usr/ports: NFSPROC_NULL: RPC: Timed out ^C b# tcpdump on A shows VERY strange picture: b.960 > a.sunrpc: UDP, length 56 a.sunrpc > b.960: UDP, length 28 b.820 > a.nfs: 40 null a.nfs > b.820: reply ok 24 b > a: ICMP b udp port 820 unreachable, length 36 b.912 > a.sunrpc: UDP, length 56 a.sunrpc > b.912: UDP, length 28 b.973 > a.nfs: 40 null a.nfs > b.973: reply ok 24 b > a: ICMP b udp port 973 unreachable, length 36 You see? b answer with "UDP port unreachable" on each RPC reply! There is NO any firewalls on B. And, I repeat, it WORKS when I call mount_nfs directly in a moment! Main problem is, that "/etc/fstab" is processed by mount, and NFS mount hangs up on boot, as shown above :( -- // Lev Serebryakov From owner-freebsd-stable@FreeBSD.ORG Fri May 16 12:12:02 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 88DCA106564A for ; Fri, 16 May 2008 12:12:02 +0000 (UTC) (envelope-from willy@Offermans.Rompen.nl) Received: from hpsmtp-eml14.kpnxchange.com (hpsmtp-eml14.kpnxchange.com [213.75.38.114]) by mx1.freebsd.org (Postfix) with ESMTP id 177A98FC1B for ; Fri, 16 May 2008 12:12:01 +0000 (UTC) (envelope-from willy@Offermans.Rompen.nl) Received: from cpsmtp-eml107.kpnxchange.com ([213.75.84.107]) by hpsmtp-eml14.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 16 May 2008 14:12:00 +0200 Received: from koko.offrom.nl ([86.82.183.148]) by cpsmtp-eml107.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 16 May 2008 14:11:59 +0200 Received: from wiz.vpn.offrom.nl (Debian-exim@wiz.vpn.offrom.nl [10.168.0.18]) by koko.offrom.nl (8.13.8/8.13.8) with ESMTP id m4GCBnXU082202; Fri, 16 May 2008 14:11:51 +0200 (CEST) (envelope-from willy@wiz.vpn.offrom.nl) Received: from willy by wiz.vpn.offrom.nl with local (Exim 4.63) (envelope-from ) id 1JwypC-0002Ku-RB; Fri, 16 May 2008 14:14:14 +0200 Date: Fri, 16 May 2008 14:14:14 +0200 From: Willy Offermans To: Roland Smith Message-ID: <20080516121414.GD4618@wiz.vpn.offrom.nl> References: <20080421190403.GA4625@wiz.vpn.offrom.nl> <20080421201047.GB6884@slackbox.xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080421201047.GB6884@slackbox.xs4all.nl> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: ClamAV 0.92.1/7133/Fri May 16 11:20:38 2008 on koko.offrom.nl X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.2.4 X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on koko.offrom.nl X-OriginalArrivalTime: 16 May 2008 12:12:00.0092 (UTC) FILETIME=[0B0EF1C0:01C8B74E] Cc: freebsd-stable@FreeBSD.ORG Subject: Re: g_vfs_done error third part--PLEASE HELP! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Willy@Offermans.Rompen.nl List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2008 12:12:02 -0000 Hello Roland and FreeBSD friends, I'm sorry to be so quite for a while, but I went away for a vacation. But now I'm back, I like to solve this issue. On Mon, Apr 21, 2008 at 10:10:47PM +0200, Roland Smith wrote: > On Mon, Apr 21, 2008 at 09:04:03PM +0200, Willy Offermans wrote: > > Dear FreeBSD friends, > > > > It is already the third time that I report this error. Can someone help > > me in solving this issue? > > Probably the reason that you hear so little is that you provide so > little information. Most of us are not clairvoyant. > > > Over and over again and always after heavy disk I/O I see the following > > errors in the log files. If I force ar0s1g to unmount the machine > > spontaneously reboots. Nothing seriously seems to be damaged by this > > act, but anyway I cannot afford something bad happening to this > > production machine. > > Why would you force an unmount? Otherwise the device keeps on reporting to be unavailable and cannot be unmounted: sun# umount /share/ umount: unmount of /share failed: Resource temporarily unavailable > > > Apr 18 20:02:19 sun kernel: g_vfs_done():ar0s1g[WRITE(offset=290725068800, length=4096)]error = 5 > > > > I have no clue what the errors mean, since offsets of 290725068800, > > 290725072896, and 290725074944 seem to be ridiculous. Does anybody > > have a clue what is going on? > > For starters, how big is ar0s1g? If the offset is in bytes, it is around > 270 GB, which is not that unusual in this day and age. I have to admit that I was a bit confused by an offset value of 290725068800. There is no indication of a unit, so I assumed that it was sector but probably it is simply bytes and then indeed the number does make sense. > > > I'm using FreeBSD 7.0, but found the error being reported before with > > previous versions of FreeBSD. I can and will provide more details on > > demand. > > What does 'df' say? Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ar0s1a 20308398 230438 18453290 1% / devfs 1 1 0 100% /dev /dev/ar0s1d 21321454 3814482 15801256 19% /usr /dev/ar0s1e 50777034 5331686 41383186 11% /var /dev/ar0s1f 101554150 18813760 74616058 20% /home /dev/ar0s1g 274977824 34564876 218414724 14% /share pretty normal I would say. > > Did you notice any file corruption in the filesystem on ar0s1g? No the two disks are brand new and I did not encounter any noticeable file corruption. However I assume that nowadays bad sectors on HD are handled by the hardware and do not need any user interaction to correct this. But maybe I'm totally wrong. > > Unmount the filesystem and run fsck(8) on it. Does it report any errors? sun# fsck /dev/ar0s1g ** /dev/ar0s1g ** Last Mounted on /share ** Phase 1 - Check Blocks and Sizes INCORRECT BLOCK COUNT I=34788357 (272 should be 264) CORRECT? [yn] y INCORRECT BLOCK COUNT I=34789217 (296 should be 288) CORRECT? [yn] y ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups FREE BLK COUNT(S) WRONG IN SUPERBLK SALVAGE? [yn] y SUMMARY INFORMATION BAD SALVAGE? [yn] y BLK(S) MISSING IN BIT MAPS SALVAGE? [yn] y 182863 files, 17282440 used, 120206472 free (12448 frags, 15024253 blocks, 0.0% fragmentation) ***** FILE SYSTEM MARKED CLEAN ***** ***** FILE SYSTEM WAS MODIFIED ***** The usual stuff I would say. > > > Any hints are very much appreciated. > > Did you manage to create a partition larger than the disk is (using > newfs's -s switch)? In that case it could be that you're trying to write > past the end of the device. No, look to the following output: sun# bsdlabel -A /dev/ar0s1 # /dev/ar0s1: type: unknown disk: amnesiac label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 60799 sectors/unit: 976751937 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 41943040 0 4.2BSD 0 0 0 b: 8388608 41943040 swap c: 976751937 0 unused 0 0 # "raw" part, don't edit d: 44040192 50331648 4.2BSD 2048 16384 28552 e: 104857600 94371840 4.2BSD 2048 16384 28552 f: 209715200 199229440 4.2BSD 2048 16384 28552 g: 567807297 408944640 4.2BSD 2048 16384 28552 /dev/ar0s1g starts after 408944640*512/1024/1024=199680MB So I have to conclude that the write error message does make sense and that something seems to be wrong with the disks. The next question is what can I do about it? Should I return the disks to the shop and ask for new ones? However other people that I have contacted and who had a similar problem before have solved it by using software raid setup instead of a hardware raid setup. This seems to indicate that there is some bug in the FreeBSD code. Another peculiarity that I have to mention is the following. If I use sysinstall and if I try to ``Label allocated disk partitions'', I cannot see the partitions on ar0. However the partitions can be visualised by bsdlabel as shown above. What is going on and what should I do? > > Roland > -- > R.F.Smith http://www.xs4all.nl/~rsmith/ > [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] > pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, De jrus wah, Willy ************************************* W.K. Offermans Home: +31 45 544 49 44 Mobile: +31 653 27 16 23 e-mail: Willy@Offermans.Rompen.nl Powered by .... (__) \\\'',) \/ \ ^ .\._/_) www.FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Fri May 16 12:27:59 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5CA7C1065731 for ; Fri, 16 May 2008 12:27:59 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4BA908FC1E for ; Fri, 16 May 2008 12:27:59 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 2D7581CC033; Fri, 16 May 2008 05:27:59 -0700 (PDT) Date: Fri, 16 May 2008 05:27:59 -0700 From: Jeremy Chadwick To: Willy Offermans Message-ID: <20080516122759.GA61346@eos.sc1.parodius.com> References: <20080421190403.GA4625@wiz.vpn.offrom.nl> <20080421201047.GB6884@slackbox.xs4all.nl> <20080516121414.GD4618@wiz.vpn.offrom.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080516121414.GD4618@wiz.vpn.offrom.nl> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: Roland Smith , freebsd-stable@FreeBSD.ORG Subject: Re: g_vfs_done error third part--PLEASE HELP! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2008 12:27:59 -0000 On Fri, May 16, 2008 at 02:14:14PM +0200, Willy Offermans wrote: > On Mon, Apr 21, 2008 at 10:10:47PM +0200, Roland Smith wrote: > > Did you notice any file corruption in the filesystem on ar0s1g? > > No the two disks are brand new and I did not encounter any noticeable > file corruption. However I assume that nowadays bad sectors on HD are > handled by the hardware and do not need any user interaction to correct > this. But maybe I'm totally wrong. You're right, but it depends on the type of disk. SCSI disks will report bad blocks to the OS regardless if it is about to mark the block as a grown defect or not. PATA and SATA disks, on the other hand, will report bad blocks to the OS only if the internal bad block list (which it manages itself -- this is what you're thinking of) is full. There are still many conditions where PATA and SATA disks can induce errors in the OS. If the disk is attempting to work around a bad block, and there's a physical error (servo problem, head crash, repetitive re-reads of the block due to dust, whatever -- something that "ties up" the disk for long periods of time), ATA subsystem timeouts may be seen, DMA errors, or whatever else. SMART stats will show this kind of problem. > > Unmount the filesystem and run fsck(8) on it. Does it report any errors? > > sun# fsck /dev/ar0s1g > ** /dev/ar0s1g > ** Last Mounted on /share > ** Phase 1 - Check Blocks and Sizes > INCORRECT BLOCK COUNT I=34788357 (272 should be 264) > CORRECT? [yn] y > > INCORRECT BLOCK COUNT I=34789217 (296 should be 288) > CORRECT? [yn] y > > ** Phase 2 - Check Pathnames > ** Phase 3 - Check Connectivity > ** Phase 4 - Check Reference Counts > ** Phase 5 - Check Cyl groups > FREE BLK COUNT(S) WRONG IN SUPERBLK > SALVAGE? [yn] y > > SUMMARY INFORMATION BAD > SALVAGE? [yn] y > > BLK(S) MISSING IN BIT MAPS > SALVAGE? [yn] y > > 182863 files, 17282440 used, 120206472 free (12448 frags, 15024253 > blocks, 0.0% fragmentation) > > ***** FILE SYSTEM MARKED CLEAN ***** > > ***** FILE SYSTEM WAS MODIFIED ***** > > The usual stuff I would say. How is this usual?. It appears to me you did have some filesystem corruption. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Fri May 16 12:38:06 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 42CB91065679 for ; Fri, 16 May 2008 12:38:06 +0000 (UTC) (envelope-from pldrouin@pldrouin.net) Received: from smtp.cyberfingers.net (smtp.cyberfingers.net [198.177.254.227]) by mx1.freebsd.org (Postfix) with ESMTP id 21E808FC33 for ; Fri, 16 May 2008 12:38:05 +0000 (UTC) (envelope-from pldrouin@pldrouin.net) Received: from ldaemon.pldrouin.net (modemcable090.40-56-74.mc.videotron.ca [74.56.40.90]) by smtp.cyberfingers.net (Postfix) with ESMTP id 17C52AB6C10 for ; Fri, 16 May 2008 08:38:13 -0400 (EDT) Message-ID: <482917B0.9040302@pldrouin.net> Date: Tue, 13 May 2008 00:23:12 -0400 From: Pierre-Luc Drouin User-Agent: Thunderbird 2.0.0.14 (X11/20080503) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Status of ZFS in -stable? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2008 12:38:06 -0000 Hi, I would like to know memory allocation problem eith zfs has been fixed in -stable since the release of 7.0? Is zfs more "stable From owner-freebsd-stable@FreeBSD.ORG Fri May 16 12:43:23 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 02AC81065672 for ; Fri, 16 May 2008 12:43:23 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E52268FC14; Fri, 16 May 2008 12:43:21 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <482D816C.4060402@FreeBSD.org> Date: Fri, 16 May 2008 14:43:24 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Willy@Offermans.Rompen.nl References: <20080421190403.GA4625@wiz.vpn.offrom.nl> <20080421201047.GB6884@slackbox.xs4all.nl> <20080516121414.GD4618@wiz.vpn.offrom.nl> In-Reply-To: <20080516121414.GD4618@wiz.vpn.offrom.nl> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Cc: Roland Smith , freebsd-stable@FreeBSD.ORG Subject: Re: g_vfs_done error third part--PLEASE HELP! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2008 12:43:23 -0000 Willy Offermans wrote: > Hello Roland and FreeBSD friends, > > I'm sorry to be so quite for a while, but I went away for a vacation. > But now I'm back, I like to solve this issue. > > > On Mon, Apr 21, 2008 at 10:10:47PM +0200, Roland Smith wrote: >> On Mon, Apr 21, 2008 at 09:04:03PM +0200, Willy Offermans wrote: >>> Dear FreeBSD friends, >>> >>> It is already the third time that I report this error. Can someone help >>> me in solving this issue? >> Probably the reason that you hear so little is that you provide so >> little information. Most of us are not clairvoyant. >> >>> Over and over again and always after heavy disk I/O I see the following >>> errors in the log files. If I force ar0s1g to unmount the machine >>> spontaneously reboots. Nothing seriously seems to be damaged by this >>> act, but anyway I cannot afford something bad happening to this >>> production machine. >> Why would you force an unmount? > > Otherwise the device keeps on reporting to be unavailable and cannot be > unmounted: > > sun# umount /share/ > umount: unmount of /share failed: Resource temporarily unavailable > >>> Apr 18 20:02:19 sun kernel: g_vfs_done():ar0s1g[WRITE(offset=290725068800, length=4096)]error = 5 >>> >>> I have no clue what the errors mean, since offsets of 290725068800, >>> 290725072896, and 290725074944 seem to be ridiculous. Does anybody >>> have a clue what is going on? >> For starters, how big is ar0s1g? If the offset is in bytes, it is around >> 270 GB, which is not that unusual in this day and age. > > I have to admit that I was a bit confused by an offset value of > 290725068800. There is no indication of a unit, so I assumed that it > was sector but probably it is simply bytes and then indeed the number > does make sense. >>> I'm using FreeBSD 7.0, but found the error being reported before with >>> previous versions of FreeBSD. I can and will provide more details on >>> demand. >> What does 'df' say? > > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/ar0s1a 20308398 230438 18453290 1% / > devfs 1 1 0 100% /dev > /dev/ar0s1d 21321454 3814482 15801256 19% /usr > /dev/ar0s1e 50777034 5331686 41383186 11% /var > /dev/ar0s1f 101554150 18813760 74616058 20% /home > /dev/ar0s1g 274977824 34564876 218414724 14% /share > > pretty normal I would say. > >> Did you notice any file corruption in the filesystem on ar0s1g? > > No the two disks are brand new and I did not encounter any noticeable > file corruption. However I assume that nowadays bad sectors on HD are > handled by the hardware and do not need any user interaction to correct > this. But maybe I'm totally wrong. > >> Unmount the filesystem and run fsck(8) on it. Does it report any errors? > > sun# fsck /dev/ar0s1g > ** /dev/ar0s1g > ** Last Mounted on /share > ** Phase 1 - Check Blocks and Sizes > INCORRECT BLOCK COUNT I=34788357 (272 should be 264) > CORRECT? [yn] y > > INCORRECT BLOCK COUNT I=34789217 (296 should be 288) > CORRECT? [yn] y > > ** Phase 2 - Check Pathnames > ** Phase 3 - Check Connectivity > ** Phase 4 - Check Reference Counts > ** Phase 5 - Check Cyl groups > FREE BLK COUNT(S) WRONG IN SUPERBLK > SALVAGE? [yn] y > > SUMMARY INFORMATION BAD > SALVAGE? [yn] y > > BLK(S) MISSING IN BIT MAPS > SALVAGE? [yn] y > > 182863 files, 17282440 used, 120206472 free (12448 frags, 15024253 > blocks, 0.0% fragmentation) > > ***** FILE SYSTEM MARKED CLEAN ***** > > ***** FILE SYSTEM WAS MODIFIED ***** > > The usual stuff I would say. No, any form of filesystem corruption is not usual. > >>> Any hints are very much appreciated. >> Did you manage to create a partition larger than the disk is (using >> newfs's -s switch)? In that case it could be that you're trying to write >> past the end of the device. > > No, look to the following output: > > sun# bsdlabel -A /dev/ar0s1 > # /dev/ar0s1: > type: unknown > disk: amnesiac > label: > flags: > bytes/sector: 512 > sectors/track: 63 > tracks/cylinder: 255 > sectors/cylinder: 16065 > cylinders: 60799 > sectors/unit: 976751937 > rpm: 3600 > interleave: 1 > trackskew: 0 > cylinderskew: 0 > headswitch: 0 # milliseconds > track-to-track seek: 0 # milliseconds > drivedata: 0 > > 8 partitions: > # size offset fstype [fsize bsize bps/cpg] > a: 41943040 0 4.2BSD 0 0 0 > b: 8388608 41943040 swap > c: 976751937 0 unused 0 0 # "raw" > part, don't edit > d: 44040192 50331648 4.2BSD 2048 16384 28552 > e: 104857600 94371840 4.2BSD 2048 16384 28552 > f: 209715200 199229440 4.2BSD 2048 16384 28552 > g: 567807297 408944640 4.2BSD 2048 16384 28552 > > /dev/ar0s1g starts after 408944640*512/1024/1024=199680MB > > > So I have to conclude that the write error message does make sense and > that something seems to be wrong with the disks. The next question is > what can I do about it? Should I return the disks to the shop and ask > for new ones? #define EIO 5 /* Input/output error */ At least one of your disks is toast. Kris From owner-freebsd-stable@FreeBSD.ORG Fri May 16 13:36:27 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ADD071065675 for ; Fri, 16 May 2008 13:36:27 +0000 (UTC) (envelope-from freebsdlists@bsdunix.ch) Received: from conversation.bsdunix.ch (ns1.bsdunix.ch [82.220.1.90]) by mx1.freebsd.org (Postfix) with ESMTP id 68EB08FC39 for ; Fri, 16 May 2008 13:36:27 +0000 (UTC) (envelope-from freebsdlists@bsdunix.ch) Received: from localhost (localhost.bsdunix.ch [127.0.0.1]) by conversation.bsdunix.ch (Postfix) with ESMTP id 733265DBF; Fri, 16 May 2008 15:36:26 +0200 (CEST) X-Virus-Scanned: by amavisd-new at mail.bsdunix.ch Received: from conversation.bsdunix.ch ([127.0.0.1]) by localhost (conversation.bsdunix.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id C0fhvpYjEyb3; Fri, 16 May 2008 15:36:26 +0200 (CEST) Received: from 192.168.1.105.local.home (3.noc.solnet.ch [212.101.0.3]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by conversation.bsdunix.ch (Postfix) with ESMTP id E0DEF5D45; Fri, 16 May 2008 15:36:25 +0200 (CEST) Message-Id: <81B25D8A-5EE6-4C18-A170-15ADACA8B3C7@bsdunix.ch> From: Thomas Vogt To: Marcel Moolenaar In-Reply-To: <7C738CA6-9F66-44B4-A1AF-9CC3F80DB6BC@mac.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v919.2) Date: Fri, 16 May 2008 15:36:25 +0200 References: <65DED12A-0263-4281-ADAC-CBF2A7857D5E@bsdunix.ch> <7C738CA6-9F66-44B4-A1AF-9CC3F80DB6BC@mac.com> X-Mailer: Apple Mail (2.919.2) Cc: freebsd-stable@freebsd.org Subject: Re: Timedia 8 port serial pci card problem X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2008 13:36:27 -0000 Hi Marcel Am 16.05.2008 um 12:53 schrieb Marcel Moolenaar: > > On May 16, 2008, at 1:17 AM, Thomas Vogt wrote: > >> FreeBSD detects it with: "puc0: >> port 0xe500-0xe51f,0xe520-0xe52f,0xe530-0xe537,0xe538-0xe53f, >> 0xe540-0xe547,0xe548-0xe54f irq 10 at device 14.0 on pci0" . But it >> only adds 3 uart ports instead of 8. Any idea what i can do? > > Can you try the following (white-space corrupted) patch: > > Index: pucdata.c > =================================================================== > RCS file: /home/ncvs/src/sys/dev/puc/pucdata.c,v > retrieving revision 1.59.2.1 > diff -u -r1.59.2.1 pucdata.c > --- pucdata.c 26 Feb 2008 09:33:57 -0000 1.59.2.1 > +++ pucdata.c 16 May 2008 10:48:25 -0000 > @@ -1116,7 +1116,7 @@ > *res = (port == 1 || port == 3) ? 8 : 0; > return (0); > case PUC_CFG_GET_RID: > - *res = 0x10 + ((port > 3) ? port - 2 : port >> 1); > + *res = 0x10 + ((port > 3) ? port - 2 : port >> 1) * 4; > return (0); > case PUC_CFG_GET_TYPE: > *res = PUC_TYPE_SERIAL; Thats it. It works with your patch dmesg: puc0: port 0xe500-0xe51f, 0xe520-0xe52f,0xe530-0xe537,0xe538-0xe53f,0xe540-0xe547,0xe548-0xe54f irq 10 at device 14.0 on pci0 puc0: Reserved 0x20 bytes for rid 0x10 type 4 at 0xe500 puc0: Reserved 0x10 bytes for rid 0x14 type 4 at 0xe520 puc0: Reserved 0x8 bytes for rid 0x18 type 4 at 0xe530 puc0: Reserved 0x8 bytes for rid 0x1c type 4 at 0xe538 puc0: Reserved 0x8 bytes for rid 0x20 type 4 at 0xe540 puc0: Reserved 0x8 bytes for rid 0x24 type 4 at 0xe548 puc0: [FILTER] uart0: on puc0 uart0: [FILTER] uart0: fast interrupt uart1: on puc0 uart1: [FILTER] uart1: fast interrupt uart2: on puc0 uart2: [FILTER] uart2: fast interrupt uart3: on puc0 uart3: [FILTER] uart3: fast interrupt uart4: on puc0 uart4: [FILTER] uart4: fast interrupt uart5: on puc0 uart5: [FILTER] uart5: fast interrupt uart6: on puc0 uart6: [FILTER] uart6: fast interrupt uart7: on puc0 uart7: [FILTER] uart7: fast interrupt Thank you, Thomas From owner-freebsd-stable@FreeBSD.ORG Fri May 16 13:43:51 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 07B7B1065671; Fri, 16 May 2008 13:43:51 +0000 (UTC) (envelope-from so14k@valentine.liquidneon.com) Received: from valentine.liquidneon.com (unknown [IPv6:2001:4830:2407:8000:230:48ff:fe71:c2a2]) by mx1.freebsd.org (Postfix) with ESMTP id 21F118FC1E; Fri, 16 May 2008 13:43:49 +0000 (UTC) (envelope-from so14k@valentine.liquidneon.com) Received: by valentine.liquidneon.com (Postfix, from userid 1018) id B8D478FD8B; Fri, 16 May 2008 07:43:46 -0600 (MDT) Date: Fri, 16 May 2008 07:43:46 -0600 From: Brad Davis To: hackers@FreeBSD.org Message-ID: <20080516134346.GB1844@valentine.liquidneon.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: FreeBSD Status Reports for the First Quarter of 2008 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2008 13:43:51 -0000 Hi Everyone, The FreeBSD Status Reports for the First Quarter of 2008 are now available at: http://www.freebsd.org/news/status/report-2008-01-2008-03.html Regards, Brad Davis From owner-freebsd-stable@FreeBSD.ORG Fri May 16 13:54:00 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B1FEC106567D for ; Fri, 16 May 2008 13:54:00 +0000 (UTC) (envelope-from steve@mouf.net) Received: from stevenwills.com (cpe-024-163-080-004.nc.res.rr.com [24.163.80.4]) by mx1.freebsd.org (Postfix) with ESMTP id 635248FC1B for ; Fri, 16 May 2008 13:54:00 +0000 (UTC) (envelope-from steve@mouf.net) Received: from [192.168.1.19] (adsl-065-015-231-202.sip.rmo.bellsouth.net [65.15.231.202]) (authenticated bits=0) by stevenwills.com (8.13.8/8.13.8) with ESMTP id m4GDghRS020467 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for ; Fri, 16 May 2008 09:42:44 -0400 (EDT) (envelope-from steve@mouf.net) Message-Id: <9A673D2F-8758-44D9-A41A-382610B377BA@mouf.net> From: Steve Wills To: stable@freebsd.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v919.2) Date: Fri, 16 May 2008 09:42:35 -0400 X-Mailer: Apple Mail (2.919.2) X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-3.0 (stevenwills.com [24.163.80.4]); Fri, 16 May 2008 09:42:45 -0400 (EDT) X-Spam-Status: No, score=0.1 required=5.0 tests=RDNS_DYNAMIC autolearn=disabled version=3.2.3 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on mastershake.mouf.net X-Virus-Scanned: ClamAV 0.91.2/7112/Tue May 13 14:50:35 2008 on mastershake.mouf.net X-Virus-Status: Clean Cc: Subject: cfservd crashing on 7.0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2008 13:54:00 -0000 Hi, I just moved my cfservd (a part of sysutils/cfengine) from a 6.2 server to a 7.0 server. Ever since, cfservd crashes regularly. The backtrace is below, although obviously it is missing a lot. If anyone has clues or suggestions, I'd really appreciate it. # gdb /usr/local/sbin/cfservd cfservd.core GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd"...(no debugging symbols found)... Core was generated by `cfservd'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/local/lib/libdb-4.6.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libdb-4.6.so.0 Reading symbols from /lib/libthr.so.3...(no debugging symbols found)...done. Loaded symbols for /lib/libthr.so.3 Reading symbols from /lib/libcrypto.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libcrypto.so.5 Reading symbols from /usr/lib/librt.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/librt.so.1 Reading symbols from /lib/libm.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libm.so.5 Reading symbols from /lib/libc.so.7...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols found)...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x283214e0 in sha1_block_data_order () from /lib/libcrypto.so.5 [New Thread 0x28501600 (LWP 100725)] [New Thread 0x28501500 (LWP 100723)] [New Thread 0x28501c00 (LWP 100289)] [New Thread 0x28501a00 (LWP 100722)] [New Thread 0x28501900 (LWP 100505)] [New Thread 0x28501400 (LWP 100726)] [New Thread 0x28501100 (LWP 100614)] (gdb) bt #0 0x283214e0 in sha1_block_data_order () from /lib/libcrypto.so.5 #1 0x28323112 in SHA1_Update () from /lib/libcrypto.so.5 #2 0x283114fe in EVP_sha512 () from /lib/libcrypto.so.5 #3 0x2952e080 in ?? () #4 0x28391cf4 in ?? () from /lib/libcrypto.so.5 #5 0xffffff6b in ?? () #6 0x28311b65 in EVP_DigestInit_ex () from /lib/libcrypto.so.5 #7 0x2831161f in EVP_DigestUpdate () from /lib/libcrypto.so.5 #8 0x282f38ef in RAND_SSLeay () from /lib/libcrypto.so.5 #9 0xbf8f5d20 in ?? () #10 0x28391cf4 in ?? () from /lib/libcrypto.so.5 #11 0xffffff6b in ?? () #12 0x000001c2 in ?? () #13 0x00000100 in ?? () #14 0xbf8f5d38 in ?? () #15 0x2836aad0 in RSA_version () from /lib/libcrypto.so.5 #16 0xbf8f5d0c in ?? () #17 0xbf8f5d30 in ?? () #18 0x0000000a in ?? () #19 0x000003ff in ?? () #20 0x00000001 in ?? () #21 0xfffffc0b in ?? () #22 0x9479e4c0 in ?? () #23 0x907484c9 in ?? () ---Type to continue, or q to quit--- #24 0x99437746 in ?? () #25 0xde61d2b4 in ?? () #26 0xaab0b47e in ?? () #27 0x2838cc20 in ASN1_OCTET_STRING_NDEF_it () from /lib/libcrypto.so.5 #28 0x00000000 in ?? () #29 0x00000000 in ?? () #30 0x2952e080 in ?? () #31 0x0000952a in ?? () #32 0x000036ea in ?? () #33 0x00000000 in ?? () #34 0x2838f08c in ?? () from /lib/libcrypto.so.5 #35 0x29512080 in ?? () #36 0x2952a102 in ?? () #37 0xbf8f5d68 in ?? () #38 0x282f2eac in RAND_bytes () from /lib/libcrypto.so.5 Previous frame identical to this frame (corrupt stack?) (gdb) Thanks, Steve From owner-freebsd-stable@FreeBSD.ORG Fri May 16 13:58:30 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 810B81065675 for ; Fri, 16 May 2008 13:58:30 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from ftp.translate.ru (ftp.translate.ru [195.131.4.140]) by mx1.freebsd.org (Postfix) with ESMTP id 3B88C8FC17 for ; Fri, 16 May 2008 13:58:30 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from [192.18.98.62] (brmea-proxy-1.Sun.COM [192.18.98.62]) (Authenticated sender: lev@serebryakov.spb.ru) by ftp.translate.ru (Postfix) with ESMTPA id 440C013DF5B for ; Fri, 16 May 2008 17:58:27 +0400 (MSD) Message-ID: <482D92D4.20908@FreeBSD.org> Date: Fri, 16 May 2008 17:57:40 +0400 From: Lev Serebryakov Organization: FreeBSD Project User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.14) Gecko/20071210 Thunderbird/1.5.0.14 Mnenhy/0.7.4.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <482D6492.8080209@FreeBSD.org> In-Reply-To: <482D6492.8080209@FreeBSD.org> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: FreeBSD 7.0-STABLE: "mount_nfs" vs "mount -t nfs": problems with second one, UDP timeouts and ICMP ports unreach?! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2008 13:58:30 -0000 Lev Serebryakov wrote: > You see? b answer with "UDP port unreachable" on each RPC reply! Additional info. ktrace from "mount -t nfs": ============================================================= 65962 mount_nfs 0.006679 RET sendto 40/0x28 65962 mount_nfs 0.006682 CALL kevent(0x4,0x638110,0x1,0x7fffffffe2d0,0x1,0x7fffffffe310) 65962 mount_nfs 10.218001 GIO fd 4 wrote 32 bytes 65962 mount_nfs 10.218018 GIO fd 4 read 0 bytes "" 65962 mount_nfs 10.218023 RET kevent 0 65962 mount_nfs 10.218029 CALL gettimeofday(0x7fffffffe320,0) 65962 mount_nfs 10.218035 RET gettimeofday 0 65962 mount_nfs 10.218040 CALL close(0x4) 65962 mount_nfs 10.218049 RET close 0 65962 mount_nfs 10.218077 CALL close(0x3) 65962 mount_nfs 10.218087 RET close 0 65962 mount_nfs 10.218101 CALL write(0x2,0x7fffffffdd40,0x37) 65962 mount_nfs 10.218117 GIO fd 2 wrote 55 bytes "[udp] gateway:/usr/ports: NFSPROC_NULL: RPC: Timed out " ============================================================= ktrace (same piece) from "mount_nfs": ============================================================= 93109 mount_nfs 0.005458 RET sendto 40/0x28 93109 mount_nfs 0.005462 CALL kevent(0x4,0x638110,0x1,0x7fffffffe2a0,0x1,0x7fffffffe2e0) 93109 mount_nfs 0.005724 GIO fd 4 wrote 32 bytes 93109 mount_nfs 0.005738 GIO fd 4 read 32 bytes 93109 mount_nfs 0.005743 RET kevent 1 93109 mount_nfs 0.005748 CALL recvfrom(0x3,0x638134,0x2260,0,0,0) 93109 mount_nfs 0.005756 GIO fd 3 read 24 bytes 93109 mount_nfs 0.005761 RET recvfrom 24/0x18 93109 mount_nfs 0.005767 CALL close(0x4) 93109 mount_nfs 0.005775 RET close 0 93109 mount_nfs 0.005781 CALL close(0x3) 93109 mount_nfs 0.005788 RET close 0 ============================================================= From owner-freebsd-stable@FreeBSD.ORG Fri May 16 14:26:30 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CAA97106567A; Fri, 16 May 2008 14:26:30 +0000 (UTC) (envelope-from fanf2@hermes.cam.ac.uk) Received: from ppsw-1.csi.cam.ac.uk (ppsw-1.csi.cam.ac.uk [131.111.8.131]) by mx1.freebsd.org (Postfix) with ESMTP id 88ED88FC22; Fri, 16 May 2008 14:26:30 +0000 (UTC) (envelope-from fanf2@hermes.cam.ac.uk) X-Cam-SpamDetails: Not scanned X-Cam-AntiVirus: No virus found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from hermes-1.csi.cam.ac.uk ([131.111.8.51]:41659) by ppsw-1.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.151]:25) with esmtpa (EXTERNAL:fanf2) id 1Jx0t8-00037Q-3G (Exim 4.67) (return-path ); Fri, 16 May 2008 15:26:26 +0100 Received: from fanf2 (helo=localhost) by hermes-1.csi.cam.ac.uk (hermes.cam.ac.uk) with local-esmtp id 1Jx0t7-0002Dt-W0 (Exim 4.67) (return-path ); Fri, 16 May 2008 15:26:25 +0100 Date: Fri, 16 May 2008 15:26:25 +0100 From: Tony Finch X-X-Sender: fanf2@hermes-1.csi.cam.ac.uk To: Dr Josef Karthauser In-Reply-To: <07f101c8b6e2$f4b13f20$de13bd60$@org.uk> Message-ID: References: <20080511102730.DBD0A600F@mailhost.tao.org.uk> <07f101c8b6e2$f4b13f20$de13bd60$@org.uk> User-Agent: Alpine 1.00 (LSU 882 2007-12-20) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Tony Finch Cc: freebsd-hubs@freebsd.org, freebsd-stable@freebsd.org Subject: RE: cvsup.uk.FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2008 14:26:30 -0000 On Fri, 16 May 2008, Dr Josef Karthauser wrote: > > As a matter of interest, do you know what the peak bandwidth usage is? Based on the cvsupd log the peak is around 600KB/sec in and 360KB/sec out at about 2am. The university's bandwidth accounting system says: date host in (MB) out (MB) total 2008-05-09 131.111.008.041 1902.863 2890.291 4793.155 2008-05-10 131.111.008.041 9278.231 5287.797 14566.028 2008-05-11 131.111.008.041 9214.064 4059.799 13273.863 2008-05-12 131.111.008.041 9248.677 4458.978 13707.655 2008-05-13 131.111.008.041 8818.575 4651.896 13470.471 2008-05-14 131.111.008.041 9254.688 5833.494 15088.182 2008-05-15 131.111.008.041 9116.638 4715.182 13831.820 Tony. -- f.anthony.n.finch http://dotat.at/ VIKING: NORTHERLY 4 OR 5 INCREASING 6 OR 7, PERHAPS GALE 8 LATER. MODERATE BECOMING ROUGH. SHOWERS. MODERATE OR GOOD. From owner-freebsd-stable@FreeBSD.ORG Fri May 16 14:53:08 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6BBB11065672; Fri, 16 May 2008 14:53:08 +0000 (UTC) (envelope-from vivek@khera.org) Received: from yertle.kcilink.com (thingy.kcilink.com [74.92.149.59]) by mx1.freebsd.org (Postfix) with ESMTP id 404C18FC2A; Fri, 16 May 2008 14:53:08 +0000 (UTC) (envelope-from vivek@khera.org) Received: from host-121.int.kcilink.com (host-121.int.kcilink.com [192.168.7.121]) by yertle.kcilink.com (Postfix) with ESMTP id 7AB048A0AD; Fri, 16 May 2008 10:53:07 -0400 (EDT) Message-Id: From: Vivek Khera To: FreeBSD Stable In-Reply-To: <6ADAB997-FAA4-43B8-AB57-3CC4A04F3700@khera.org> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v919.2) Date: Fri, 16 May 2008 10:53:07 -0400 References: <04EA1C34-AB7D-4A85-8A91-DED03E987706@khera.org> <482C07DE.3090504@yandex.ru> <482C0A89.104@FreeBSD.org> <6ADAB997-FAA4-43B8-AB57-3CC4A04F3700@khera.org> X-Mailer: Apple Mail (2.919.2) Cc: freebsd-ipfw@freebsd.org Subject: Re: how much memory does increasing max rules for IPFW take up? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2008 14:53:08 -0000 How are the buckets used? Are they hashed per rule number or some other mechanism? Nearly all of my states are from the same rule (eg, on a mail server for the SMTP port rule). How should I scale the buckets with the max rules? The default seems to be 4096 rules and 256 buckets. Should I maintain that ratio? From owner-freebsd-stable@FreeBSD.ORG Fri May 16 15:11:02 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4D27A10656C9 for ; Fri, 16 May 2008 15:11:02 +0000 (UTC) (envelope-from lists-fbsdstable@shadypond.com) Received: from mx-outbound01.easydns.com (mailout1.easydns.com [205.210.42.66]) by mx1.freebsd.org (Postfix) with ESMTP id 26A758FC23 for ; Fri, 16 May 2008 15:11:01 +0000 (UTC) (envelope-from lists-fbsdstable@shadypond.com) Received: from lilypad.shadypond.com (69-12-173-117.static.humboldt1.com [69.12.173.117]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx-outbound01.easydns.com (Postfix) with ESMTP id E0B7148966 for ; Fri, 16 May 2008 10:40:19 -0400 (EDT) Received: from slider.shadypond.com (slider.shadypond.com [192.168.1.11]) by lilypad.shadypond.com (Postfix) with ESMTPS id 6CF1DB87D for ; Fri, 16 May 2008 14:42:52 +0000 (UTC) From: Pollywog To: freebsd-stable@freebsd.org Date: Fri, 16 May 2008 14:42:49 +0000 References: <784966050805151644m43b9a5e1qe8a4568576fc081f@mail.gmail.com> <784966050805152304t1827c53bi6988ae9c8f837f32@mail.gmail.com> <20080516061724.GA47953@eos.sc1.parodius.com> In-Reply-To: <20080516061724.GA47953@eos.sc1.parodius.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200805161442.51667.lists-fbsdstable@shadypond.com> Subject: Re: today's build is causing errors for me X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2008 15:11:02 -0000 On Friday 16 May 2008 06:17:24 Jeremy Chadwick wrote: > > Additionally, mergemaster isn't a confusing mess. If anything, it's one > of the most simple tools there is for managing /etc. The part you > probably find "confusing", which is the same part I did when I started > using it, is the side-by-side interactive diff. It's very easy to use; > "r" means use the text shown on the right, and "l" means use the text > shown on the left. That is certainly the part that confused me until I referred to the "Absolute FreeBSD" book. From owner-freebsd-stable@FreeBSD.ORG Fri May 16 15:11:02 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4D44810656CA for ; Fri, 16 May 2008 15:11:02 +0000 (UTC) (envelope-from lists-fbsdstable@shadypond.com) Received: from mx-outbound01.easydns.com (mailout1.easydns.com [205.210.42.66]) by mx1.freebsd.org (Postfix) with ESMTP id 26BA78FC24 for ; Fri, 16 May 2008 15:11:01 +0000 (UTC) (envelope-from lists-fbsdstable@shadypond.com) Received: from lilypad.shadypond.com (69-12-173-117.static.humboldt1.com [69.12.173.117]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx-outbound01.easydns.com (Postfix) with ESMTP id 250FE4820C for ; Fri, 16 May 2008 10:38:53 -0400 (EDT) Received: from slider.shadypond.com (slider.shadypond.com [192.168.1.11]) by lilypad.shadypond.com (Postfix) with ESMTPS id 4CF15B87D for ; Fri, 16 May 2008 14:41:25 +0000 (UTC) From: Pollywog To: freebsd-stable@freebsd.org Date: Fri, 16 May 2008 14:41:22 +0000 References: <784966050805151644m43b9a5e1qe8a4568576fc081f@mail.gmail.com> <20080516043411.GA44491@eos.sc1.parodius.com> <784966050805152304t1827c53bi6988ae9c8f837f32@mail.gmail.com> In-Reply-To: <784966050805152304t1827c53bi6988ae9c8f837f32@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200805161441.24237.lists-fbsdstable@shadypond.com> Subject: Re: today's build is causing errors for me X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2008 15:11:02 -0000 On Friday 16 May 2008 06:04:34 Rob Lytle wrote: > Hi Jeremy, > > I used Mergemaster. Thats what I mean't when I said that I carefully > "merged" /usr/src/etc/ with /etc. But like I said, no files were > replaced that contained my own configuration, e.g. group. I will say > this- that I have always considered Mergemaster a confusing mess, > despite the dogma on the lists. I have been running FreeBSD and > installing it since 1998, so I have some experience- but this is new > behavior beyond my previous experiences. I have only been using FreeBSD for almost one year and I am still a little confused by Mergemaster, but what helped me with it was the book "Absolute FreeBSD". I would not have been able to deal with it without the book. From owner-freebsd-stable@FreeBSD.ORG Fri May 16 15:23:15 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A3FE31065673 for ; Fri, 16 May 2008 15:23:15 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from ftp.translate.ru (ftp.translate.ru [195.131.4.140]) by mx1.freebsd.org (Postfix) with ESMTP id 624B48FC15 for ; Fri, 16 May 2008 15:23:15 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from [192.18.98.62] (brmea-proxy-1.Sun.COM [192.18.98.62]) (Authenticated sender: lev@serebryakov.spb.ru) by ftp.translate.ru (Postfix) with ESMTPA id ADAC813DF9B for ; Fri, 16 May 2008 19:23:13 +0400 (MSD) Message-ID: <482DA6A5.4060103@FreeBSD.org> Date: Fri, 16 May 2008 19:22:13 +0400 From: Lev Serebryakov Organization: FreeBSD Project User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.14) Gecko/20071210 Thunderbird/1.5.0.14 Mnenhy/0.7.4.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <482D6492.8080209@FreeBSD.org> In-Reply-To: <482D6492.8080209@FreeBSD.org> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: FreeBSD 7.0-STABLE: "mount_nfs" vs "mount -t nfs": problems with second one, UDP timeouts and ICMP ports unreach?! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2008 15:23:15 -0000 Lev Serebryakov wrote: > Main problem is, that "/etc/fstab" is processed by mount, and NFS > mount hangs up on boot, as shown above :( Mounting with "mount -t nfs" with 7.0 server (host B) and 6.3 client (host A) works... -- // Lev Serebryakov From owner-freebsd-stable@FreeBSD.ORG Fri May 16 15:35:34 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B39E11065670 for ; Fri, 16 May 2008 15:35:34 +0000 (UTC) (envelope-from willy@Offermans.Rompen.nl) Received: from hpsmtp-eml11.kpnxchange.com (hpsmtp-eml11.kpnxchange.com [213.75.38.111]) by mx1.freebsd.org (Postfix) with ESMTP id 3F83D8FC21 for ; Fri, 16 May 2008 15:35:33 +0000 (UTC) (envelope-from willy@Offermans.Rompen.nl) Received: from cpsmtp-eml101.kpnxchange.com ([213.75.84.101]) by hpsmtp-eml11.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 16 May 2008 17:35:32 +0200 Received: from koko.offrom.nl ([86.82.183.148]) by cpsmtp-eml101.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 16 May 2008 17:35:31 +0200 Received: from wiz.vpn.offrom.nl (Debian-exim@wiz.vpn.offrom.nl [10.168.0.18]) by koko.offrom.nl (8.13.8/8.13.8) with ESMTP id m4GFZTjq083692; Fri, 16 May 2008 17:35:29 +0200 (CEST) (envelope-from willy@wiz.vpn.offrom.nl) Received: from willy by wiz.vpn.offrom.nl with local (Exim 4.63) (envelope-from ) id 1Jx20K-0002YR-2G; Fri, 16 May 2008 17:37:56 +0200 Date: Fri, 16 May 2008 17:37:56 +0200 From: Willy Offermans To: Jeremy Chadwick Message-ID: <20080516153755.GA9388@wiz.vpn.offrom.nl> References: <20080421190403.GA4625@wiz.vpn.offrom.nl> <20080421201047.GB6884@slackbox.xs4all.nl> <20080516121414.GD4618@wiz.vpn.offrom.nl> <20080516122759.GA61346@eos.sc1.parodius.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080516122759.GA61346@eos.sc1.parodius.com> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: ClamAV 0.92.1/7136/Fri May 16 14:56:53 2008 on koko.offrom.nl X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.2.4 X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on koko.offrom.nl X-OriginalArrivalTime: 16 May 2008 15:35:32.0083 (UTC) FILETIME=[79F8E430:01C8B76A] Cc: freebsd-stable@FreeBSD.org Subject: Re: g_vfs_done error third part--PLEASE HELP! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Willy@Offermans.Rompen.nl List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2008 15:35:34 -0000 Hello Jeremy and FreeBSD friends, On Fri, May 16, 2008 at 05:27:59AM -0700, Jeremy Chadwick wrote: > On Fri, May 16, 2008 at 02:14:14PM +0200, Willy Offermans wrote: > > On Mon, Apr 21, 2008 at 10:10:47PM +0200, Roland Smith wrote: > > > Did you notice any file corruption in the filesystem on ar0s1g? > > > > No the two disks are brand new and I did not encounter any noticeable > > file corruption. However I assume that nowadays bad sectors on HD are > > handled by the hardware and do not need any user interaction to correct > > this. But maybe I'm totally wrong. > > You're right, but it depends on the type of disk. SCSI disks will > report bad blocks to the OS regardless if it is about to mark the block > as a grown defect or not. PATA and SATA disks, on the other hand, will > report bad blocks to the OS only if the internal bad block list (which > it manages itself -- this is what you're thinking of) is full. > > There are still many conditions where PATA and SATA disks can induce > errors in the OS. If the disk is attempting to work around a bad block, > and there's a physical error (servo problem, head crash, repetitive > re-reads of the block due to dust, whatever -- something that "ties up" > the disk for long periods of time), ATA subsystem timeouts may be seen, > DMA errors, or whatever else. SMART stats will show this kind of > problem. > > > > Unmount the filesystem and run fsck(8) on it. Does it report any errors? > > > > sun# fsck /dev/ar0s1g > > ** /dev/ar0s1g > > ** Last Mounted on /share > > ** Phase 1 - Check Blocks and Sizes > > INCORRECT BLOCK COUNT I=34788357 (272 should be 264) > > CORRECT? [yn] y > > > > INCORRECT BLOCK COUNT I=34789217 (296 should be 288) > > CORRECT? [yn] y > > > > ** Phase 2 - Check Pathnames > > ** Phase 3 - Check Connectivity > > ** Phase 4 - Check Reference Counts > > ** Phase 5 - Check Cyl groups > > FREE BLK COUNT(S) WRONG IN SUPERBLK > > SALVAGE? [yn] y > > > > SUMMARY INFORMATION BAD > > SALVAGE? [yn] y > > > > BLK(S) MISSING IN BIT MAPS > > SALVAGE? [yn] y > > > > 182863 files, 17282440 used, 120206472 free (12448 frags, 15024253 > > blocks, 0.0% fragmentation) > > > > ***** FILE SYSTEM MARKED CLEAN ***** > > > > ***** FILE SYSTEM WAS MODIFIED ***** > > > > The usual stuff I would say. > > How is this usual?. It appears to me you did have some filesystem > corruption. > What kind of filesystem corruption and how to solve that? I see these messages frequently if a FreeBSD machine unexpectedly reboots. Not only on this system but also on others. I never worried about it. -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, De jrus wah, Willy ************************************* W.K. Offermans Home: +31 45 544 49 44 Mobile: +31 653 27 16 23 e-mail: Willy@Offermans.Rompen.nl Powered by .... (__) \\\'',) \/ \ ^ .\._/_) www.FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Fri May 16 15:39:46 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0F1051065678 for ; Fri, 16 May 2008 15:39:46 +0000 (UTC) (envelope-from willy@Offermans.Rompen.nl) Received: from hpsmtp-eml20.kpnxchange.com (hpsmtp-eml20.kpnxchange.com [213.75.38.85]) by mx1.freebsd.org (Postfix) with ESMTP id 92B7E8FC1B for ; Fri, 16 May 2008 15:39:45 +0000 (UTC) (envelope-from willy@Offermans.Rompen.nl) Received: from cpsmtp-eml111.kpnxchange.com ([213.75.84.111]) by hpsmtp-eml20.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 16 May 2008 17:39:44 +0200 Received: from koko.offrom.nl ([86.82.183.148]) by cpsmtp-eml111.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 16 May 2008 17:39:43 +0200 Received: from wiz.vpn.offrom.nl (Debian-exim@wiz.vpn.offrom.nl [10.168.0.18]) by koko.offrom.nl (8.13.8/8.13.8) with ESMTP id m4GFdejP083725; Fri, 16 May 2008 17:39:40 +0200 (CEST) (envelope-from willy@wiz.vpn.offrom.nl) Received: from willy by wiz.vpn.offrom.nl with local (Exim 4.63) (envelope-from ) id 1Jx24M-0002fL-RO; Fri, 16 May 2008 17:42:06 +0200 Date: Fri, 16 May 2008 17:42:06 +0200 From: Willy Offermans To: Kris Kennaway Message-ID: <20080516154206.GB9388@wiz.vpn.offrom.nl> References: <20080421190403.GA4625@wiz.vpn.offrom.nl> <20080421201047.GB6884@slackbox.xs4all.nl> <20080516121414.GD4618@wiz.vpn.offrom.nl> <482D816C.4060402@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <482D816C.4060402@FreeBSD.org> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: ClamAV 0.92.1/7136/Fri May 16 14:56:53 2008 on koko.offrom.nl X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.2.4 X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on koko.offrom.nl X-OriginalArrivalTime: 16 May 2008 15:39:43.0794 (UTC) FILETIME=[1000F120:01C8B76B] Cc: freebsd-stable@FreeBSD.org Subject: Re: g_vfs_done error third part--PLEASE HELP! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Willy@Offermans.Rompen.nl List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2008 15:39:46 -0000 Hello Kris, On Fri, May 16, 2008 at 02:43:24PM +0200, Kris Kennaway wrote: > Willy Offermans wrote: > >Hello Roland and FreeBSD friends, > > > >I'm sorry to be so quite for a while, but I went away for a vacation. > >But now I'm back, I like to solve this issue. > > > > > >On Mon, Apr 21, 2008 at 10:10:47PM +0200, Roland Smith wrote: > >>On Mon, Apr 21, 2008 at 09:04:03PM +0200, Willy Offermans wrote: > >>>Dear FreeBSD friends, > >>> > >>>It is already the third time that I report this error. Can someone help > >>>me in solving this issue? > >>Probably the reason that you hear so little is that you provide so > >>little information. Most of us are not clairvoyant. > >> > >>>Over and over again and always after heavy disk I/O I see the following > >>>errors in the log files. If I force ar0s1g to unmount the machine > >>>spontaneously reboots. Nothing seriously seems to be damaged by this > >>>act, but anyway I cannot afford something bad happening to this > >>>production machine. > >>Why would you force an unmount? > > > >Otherwise the device keeps on reporting to be unavailable and cannot be > >unmounted: > > > >sun# umount /share/ > >umount: unmount of /share failed: Resource temporarily unavailable > > > >>>Apr 18 20:02:19 sun kernel: > >>>g_vfs_done():ar0s1g[WRITE(offset=290725068800, length=4096)]error = 5 > >>> > >>>I have no clue what the errors mean, since offsets of 290725068800, > >>>290725072896, and 290725074944 seem to be ridiculous. Does anybody > >>>have a clue what is going on? > >>For starters, how big is ar0s1g? If the offset is in bytes, it is around > >>270 GB, which is not that unusual in this day and age. > > > >I have to admit that I was a bit confused by an offset value of > >290725068800. There is no indication of a unit, so I assumed that it > >was sector but probably it is simply bytes and then indeed the number > >does make sense. > >>>I'm using FreeBSD 7.0, but found the error being reported before with > >>>previous versions of FreeBSD. I can and will provide more details on > >>>demand. > >>What does 'df' say? > > > >Filesystem 1K-blocks Used Avail Capacity Mounted on > >/dev/ar0s1a 20308398 230438 18453290 1% / > >devfs 1 1 0 100% /dev > >/dev/ar0s1d 21321454 3814482 15801256 19% /usr > >/dev/ar0s1e 50777034 5331686 41383186 11% /var > >/dev/ar0s1f 101554150 18813760 74616058 20% /home > >/dev/ar0s1g 274977824 34564876 218414724 14% /share > > > >pretty normal I would say. > > > >>Did you notice any file corruption in the filesystem on ar0s1g? > > > >No the two disks are brand new and I did not encounter any noticeable > >file corruption. However I assume that nowadays bad sectors on HD are > >handled by the hardware and do not need any user interaction to correct > >this. But maybe I'm totally wrong. > > > >>Unmount the filesystem and run fsck(8) on it. Does it report any errors? > > > >sun# fsck /dev/ar0s1g > >** /dev/ar0s1g > >** Last Mounted on /share > >** Phase 1 - Check Blocks and Sizes > >INCORRECT BLOCK COUNT I=34788357 (272 should be 264) > >CORRECT? [yn] y > > > >INCORRECT BLOCK COUNT I=34789217 (296 should be 288) > >CORRECT? [yn] y > > > >** Phase 2 - Check Pathnames > >** Phase 3 - Check Connectivity > >** Phase 4 - Check Reference Counts > >** Phase 5 - Check Cyl groups > >FREE BLK COUNT(S) WRONG IN SUPERBLK > >SALVAGE? [yn] y > > > >SUMMARY INFORMATION BAD > >SALVAGE? [yn] y > > > >BLK(S) MISSING IN BIT MAPS > >SALVAGE? [yn] y > > > >182863 files, 17282440 used, 120206472 free (12448 frags, 15024253 > >blocks, 0.0% fragmentation) > > > >***** FILE SYSTEM MARKED CLEAN ***** > > > >***** FILE SYSTEM WAS MODIFIED ***** > > > >The usual stuff I would say. > > No, any form of filesystem corruption is not usual. > > > > >>>Any hints are very much appreciated. > >>Did you manage to create a partition larger than the disk is (using > >>newfs's -s switch)? In that case it could be that you're trying to write > >>past the end of the device. > > > >No, look to the following output: > > > >sun# bsdlabel -A /dev/ar0s1 > ># /dev/ar0s1: > >type: unknown > >disk: amnesiac > >label: > >flags: > >bytes/sector: 512 > >sectors/track: 63 > >tracks/cylinder: 255 > >sectors/cylinder: 16065 > >cylinders: 60799 > >sectors/unit: 976751937 > >rpm: 3600 > >interleave: 1 > >trackskew: 0 > >cylinderskew: 0 > >headswitch: 0 # milliseconds > >track-to-track seek: 0 # milliseconds > >drivedata: 0 > > > >8 partitions: > ># size offset fstype [fsize bsize bps/cpg] > > a: 41943040 0 4.2BSD 0 0 0 > > b: 8388608 41943040 swap > > c: 976751937 0 unused 0 0 # "raw" > >part, don't edit > > d: 44040192 50331648 4.2BSD 2048 16384 28552 > > e: 104857600 94371840 4.2BSD 2048 16384 28552 > > f: 209715200 199229440 4.2BSD 2048 16384 28552 > > g: 567807297 408944640 4.2BSD 2048 16384 28552 > > > >/dev/ar0s1g starts after 408944640*512/1024/1024=199680MB > > > > > >So I have to conclude that the write error message does make sense and > >that something seems to be wrong with the disks. The next question is > >what can I do about it? Should I return the disks to the shop and ask > >for new ones? > > #define EIO 5 /* Input/output error */ > > At least one of your disks is toast. > > Kris > I doubt it, but you could be right. Do you have any suggestions to investigate any further? Since this is a production machine I have to operate extremely carefully. I will transfer the data to other disks and will reboot and run the system from the other disks. Then I will reformat the disks again and restore the data. Lets see what happens. -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, De jrus wah, Willy ************************************* W.K. Offermans Home: +31 45 544 49 44 Mobile: +31 653 27 16 23 e-mail: Willy@Offermans.Rompen.nl Powered by .... (__) \\\'',) \/ \ ^ .\._/_) www.FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Fri May 16 15:59:38 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 973941065670 for ; Fri, 16 May 2008 15:59:38 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 85D798FC26 for ; Fri, 16 May 2008 15:59:38 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 76C931CC05B; Fri, 16 May 2008 08:59:38 -0700 (PDT) Date: Fri, 16 May 2008 08:59:38 -0700 From: Jeremy Chadwick To: Willy Offermans Message-ID: <20080516155938.GA71548@eos.sc1.parodius.com> References: <20080421190403.GA4625@wiz.vpn.offrom.nl> <20080421201047.GB6884@slackbox.xs4all.nl> <20080516121414.GD4618@wiz.vpn.offrom.nl> <20080516122759.GA61346@eos.sc1.parodius.com> <20080516153755.GA9388@wiz.vpn.offrom.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080516153755.GA9388@wiz.vpn.offrom.nl> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-stable@FreeBSD.org Subject: Re: g_vfs_done error third part--PLEASE HELP! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2008 15:59:38 -0000 On Fri, May 16, 2008 at 05:37:56PM +0200, Willy Offermans wrote: > > > sun# fsck /dev/ar0s1g > > > ** /dev/ar0s1g > > > ** Last Mounted on /share > > > ** Phase 1 - Check Blocks and Sizes > > > INCORRECT BLOCK COUNT I=34788357 (272 should be 264) > > > CORRECT? [yn] y > > > > > > INCORRECT BLOCK COUNT I=34789217 (296 should be 288) > > > CORRECT? [yn] y > > > > > > ** Phase 2 - Check Pathnames > > > ** Phase 3 - Check Connectivity > > > ** Phase 4 - Check Reference Counts > > > ** Phase 5 - Check Cyl groups > > > FREE BLK COUNT(S) WRONG IN SUPERBLK > > > SALVAGE? [yn] y > > > > > > SUMMARY INFORMATION BAD > > > SALVAGE? [yn] y > > > > > > BLK(S) MISSING IN BIT MAPS > > > SALVAGE? [yn] y > > > > > > 182863 files, 17282440 used, 120206472 free (12448 frags, 15024253 > > > blocks, 0.0% fragmentation) > > > > > > ***** FILE SYSTEM MARKED CLEAN ***** > > > > > > ***** FILE SYSTEM WAS MODIFIED ***** > > > > > > The usual stuff I would say. > > > > How is this usual?. It appears to me you did have some filesystem > > corruption. > > What kind of filesystem corruption and how to solve that? That's difficult to answer, for a lot of reasons. Your original post stated that you were seeing g_vfs_done errors on the console, and you were worried about what they implied. Then someone asked you "have you fsck'd the filesystem?", and you hadn't. Then you did fsck it, and as can be seen above, the filesystem had errors. When combined with your below comment, it's very difficult to figure out what's going on with your system over there, or what information you're not disclosing. Additionally, kris@ has stated that it looks like you may have a hard disk that's gone bad, and that's a strong possibility as well. SMART statistics of the drives in your RAID array would be useful. > I see these messages frequently if a FreeBSD machine unexpectedly reboots. Not only on this > system but also on others. I never worried about it. Are you saying the above errors experienced were caused by an unexpected crash or reboot? If so, the filesystem should have been automatically fsck'd shortly (60-120 seconds) after getting a "login:" prompt on the console. Is your filesystem UFS2 with softupdates enabled? If so, and the automatic fsck didn't happen, then that's something separate to look into -- it should happen automatically with softupdates enabled. More importantly, though, would be the explanation for why your system is crashing/rebooting/power-cycling. Data corruption can happen in those situations, especially the latter, but any form of non-clean shutdown should induce a fsck on UFS2+softupdate filesystems. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Fri May 16 16:03:17 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9BC49106564A for ; Fri, 16 May 2008 16:03:17 +0000 (UTC) (envelope-from zkolic@sbb.co.yu) Received: from smtp4.sbb.co.yu (smtp4.sbb.co.yu [82.117.194.24]) by mx1.freebsd.org (Postfix) with ESMTP id 10F0E8FC0C for ; Fri, 16 May 2008 16:03:16 +0000 (UTC) (envelope-from zkolic@sbb.co.yu) Received: from faust.net (cable-89-216-167-178.dynamic.sbb.rs [89.216.167.178]) by smtp4.sbb.co.yu (8.14.0/8.14.0) with ESMTP id m4GFmVJx006678 for ; Fri, 16 May 2008 17:48:31 +0200 Received: by faust.net (Postfix, from userid 1001) id 7C4381CC2F; Fri, 16 May 2008 17:48:48 +0200 (CEST) Date: Fri, 16 May 2008 17:48:48 +0200 From: Zoran Kolic To: freebsd-stable@freebsd.org Message-ID: <20080516154848.GA1127@faust.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-SMTP-Vilter-Version: 1.3.2 X-SBB-Virus-Status: clean X-SBB-Spam-Score: 1.9 X-SBB-Spam-Level: XXXX Subject: udf X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2008 16:03:17 -0000 Howdy! What is the experience regarding udf on cd/dvd on 7.0? I saw netbsd mail few days ago having those steps: newfs_udf and mount_udf. Best regards Zoran From owner-freebsd-stable@FreeBSD.ORG Fri May 16 16:08:16 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 18A241065675 for ; Fri, 16 May 2008 16:08:16 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: from blah.sun-fish.com (blah.sun-fish.com [217.18.249.150]) by mx1.freebsd.org (Postfix) with ESMTP id C42738FC19 for ; Fri, 16 May 2008 16:08:15 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: by blah.sun-fish.com (Postfix, from userid 1002) id 6CEB51B10EFB; Fri, 16 May 2008 18:08:14 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on malcho.cmotd.com X-Spam-Level: X-Spam-Status: No, score=-10.6 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.2.4 Received: from hater.haters.org (hater.cmotd.com [192.168.3.125]) by blah.sun-fish.com (Postfix) with ESMTP id 0D6BA1B10EF8; Fri, 16 May 2008 18:08:12 +0200 (CEST) Message-ID: <482DB16B.2070402@moneybookers.com> Date: Fri, 16 May 2008 19:08:11 +0300 From: Stefan Lambrev User-Agent: Thunderbird 2.0.0.14 (X11/20080503) MIME-Version: 1.0 To: Zoran Kolic References: <20080516154848.GA1127@faust.net> In-Reply-To: <20080516154848.GA1127@faust.net> Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.93, clamav-milter version 0.93 on blah.cmotd.com X-Virus-Status: Clean Cc: freebsd-stable@freebsd.org Subject: Re: udf X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2008 16:08:16 -0000 Zoran Kolic wrote: > Howdy! > What is the experience regarding udf on cd/dvd on 7.0? > I saw netbsd mail few days ago having those steps: > newfs_udf and mount_udf. > Best regards > From man mount_udf (FreeBSD7) HISTORY The mount_udf utility first appeared in FreeBSD 5.0. FreeBSD 7.0 March 23, 2002 FreeBSD 7.0 I have no idea for newfs_udf , and what is supposed this to do :) > Zoran > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > -- Best Wishes, Stefan Lambrev ICQ# 24134177 From owner-freebsd-stable@FreeBSD.ORG Fri May 16 16:10:17 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 70BE31065684 for ; Fri, 16 May 2008 16:10:17 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 617FD8FC26 for ; Fri, 16 May 2008 16:10:17 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 565A41CC05F; Fri, 16 May 2008 09:10:17 -0700 (PDT) Date: Fri, 16 May 2008 09:10:17 -0700 From: Jeremy Chadwick To: Stefan Lambrev Message-ID: <20080516161017.GA72242@eos.sc1.parodius.com> References: <20080516154848.GA1127@faust.net> <482DB16B.2070402@moneybookers.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <482DB16B.2070402@moneybookers.com> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-stable@freebsd.org, Zoran Kolic Subject: Re: udf X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2008 16:10:17 -0000 On Fri, May 16, 2008 at 07:08:11PM +0300, Stefan Lambrev wrote: > From man mount_udf (FreeBSD7) > > HISTORY > The mount_udf utility first appeared in FreeBSD 5.0. > > FreeBSD 7.0 March 23, 2002 FreeBSD > 7.0 > > I have no idea for newfs_udf , and what is supposed this to do :) It creates a UDF (commonly DVD/DVD Audio) filesystem. NetBSD and Solaris 10 both have this. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Fri May 16 16:23:29 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 761AB1065671 for ; Fri, 16 May 2008 16:23:29 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 32C778FC20 for ; Fri, 16 May 2008 16:23:29 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from Macintosh-4.local ([137.122.73.36]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id m4GGNRxp086221 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 16 May 2008 09:23:28 -0700 (PDT) (envelope-from sam@freebsd.org) Message-ID: <482DB4FE.3010300@freebsd.org> Date: Fri, 16 May 2008 12:23:26 -0400 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: "Alexandre \"Sunny\" Kovalenko" References: <1210640542.1008.33.camel@RabbitsDen> <4828FDE5.8090409@freebsd.org> <1210696676.985.18.camel@RabbitsDen> In-Reply-To: <1210696676.985.18.camel@RabbitsDen> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC-sonic.net-Metrics: ebb.errno.com; whitelist Cc: stable@freebsd.org Subject: Re: Hard(?) lock when reassociating ath with wpa_supplicant on RELENG_7 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2008 16:23:29 -0000 Alexandre "Sunny" Kovalenko wrote: > On Mon, 2008-05-12 at 19:33 -0700, Sam Leffler wrote: >> Alexandre "Sunny" Kovalenko wrote: >>> I seem to be able to lock my machine by going into wpa_cli and asking it >>> to 'reassoc'. The reason for question mark after "hard" is that debug >>> information (caused by wlandebug and athdebug) is being printed on the >>> console. The only way to get machine's attention is to hold power button >>> for 8 seconds. >> So this is just livelock due to console debug msgs. > I am not sure, I have parsed this well enough, so I will try to clarify: > machine becomes unresponsive *without* any debugging turned on, to an > extent that pressing the power button twice *does not* generate ACPI > console message (something to the tune of "going into S5 already -- > gimme a break"). If I turn ath debugging on, I do see those messages, > and only them, scrolling on the console. Guess I misunderstood you. >>> Note: manual reassociation is just the handy way to reproduce the >>> problem -- I have had machine locking up on me the whole day long >>> completely on its own. >>> >>> Below are, what I think, relevant pieces of information. If anything is >>> missing, please, chastise me appropriately and will do my best to >>> provide. I have rigged firewire console, but am unable to break into the >>> debugger locally or remotely. >> I see no log msgs. > I am sorry -- mailman must have eaten it up -- I have posted them here > now: > > http://members.verizon.net/~akovalenko/Misc/reassoc.log.gz All I see in the log is normal scanning. > >>> While I am on the subject, I would appreciate couple of the >>> troubleshooting suggestions: >>> * is there any way to get sysctl dev.ath.0.debug to appear, other then >>> defining ATH_DEBUG in something like /usr/src/sys/dev/ath/ah_osdep.h? >> options ATH_DEBUG > That does not seem to work for if_ath built as the module, sorry for not > being clear in that respect. If you are build a module then you must edit the Makefile to add the option. Feel free to provide a patch to improve this situation. > >>> * is there minimal, but still usable mask for athdebug and wlandebug? I >>> have started with 0xFFFFFFFF and kept trimming likely high-volume >>> settings until output slowed down to the reasonable pace. >> Why do you want debug msgs from ath? The debug msgs from wlandebug >> depend on what you're trying to debug. > Because neither wpa_supplicant (quoted below), nor wlandebug (in the URL > above) gave me the answer -- it looks like we are going into the scan > with the specific SSID in mind and never come back, so I went for the > next level. However, could you, please, clarify that I understood you > correctly -- you *do not* want to see mix of wlandebug and athdebug > messages in the report, and I should turn wlandebug off before turning > athdebug on, right? wlandebug msgs are typically low duty and can be left enabled when you add driver-level debug msgs. But I can't see from the log you sent what is going on. Try reducing the noise by eliminating all the ath debug msgs; maybe provide one log w/ only wlan msgs and one w/ wlan+ath. > >> I suggest that when debugging you start from the highest layer and move >> downward. If you can't find what you need in a wpa_supplicant log then >> turn on msgs in net80211 with wlandebug. If that doesn't tell you what >> you need then move to the driver. Blindly turning everything on can >> easily livelock your system. > That's what I did -- what I have posted is the end result of the walking > down that chain, and I assumed, possibly incorrectly, that you would > want result of all three to put things in context. I do apologize for > the misunderstanding. > >> For high volume msgs I often do something >> like: >> >> athdebug +intr; sleep 1; athdebug -intr >> >> or >> >> athdebug +intr; read x; athdebug -intr >> >> so a carriage return will disable msgs. > Thank you for the suggestion. > >> >>> * what facility does wpa_supplicant use, when forced to syslog by -s >>> switch? >> trouble% cd /data/freebsd/head/contrib/wpa_supplicant/ >> trouble% grep openlog *.c >> common.c: openlog("wpa_supplicant", LOG_PID | LOG_NDELAY, LOG_DAEMON); > Thank you, should have done this myself, sorry. > From owner-freebsd-stable@FreeBSD.ORG Fri May 16 16:48:11 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C69AA106564A; Fri, 16 May 2008 16:48:11 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id 7B7AB8FC0C; Fri, 16 May 2008 16:48:11 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from joshua-aunes-macbook-pro.local ([192.168.254.200]) (authenticated bits=0) by pooker.samsco.org (8.13.8/8.13.8) with ESMTP id m4GGm4Je076855; Fri, 16 May 2008 10:48:04 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <482DBAC4.30101@samsco.org> Date: Fri, 16 May 2008 10:48:04 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.13) Gecko/20080313 SeaMonkey/1.1.9 MIME-Version: 1.0 To: Jeremy Chadwick References: <20080516154848.GA1127@faust.net> <482DB16B.2070402@moneybookers.com> <20080516161017.GA72242@eos.sc1.parodius.com> In-Reply-To: <20080516161017.GA72242@eos.sc1.parodius.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.4 required=3.8 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: Zoran Kolic , freebsd-stable@freebsd.org, Stefan Lambrev Subject: Re: udf X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2008 16:48:11 -0000 Jeremy Chadwick wrote: > On Fri, May 16, 2008 at 07:08:11PM +0300, Stefan Lambrev wrote: >> From man mount_udf (FreeBSD7) >> >> HISTORY >> The mount_udf utility first appeared in FreeBSD 5.0. >> >> FreeBSD 7.0 March 23, 2002 FreeBSD >> 7.0 >> >> I have no idea for newfs_udf , and what is supposed this to do :) > > It creates a UDF (commonly DVD/DVD Audio) filesystem. NetBSD and > Solaris 10 both have this. > There is no write support in UDF in FreeBSD. When I wrote the fs code, packet writing was the only way to do discrete writes, and it's very hard to make that work with a traditional VM system. Now with DVD+R, it's probably worth someone's time to look at it (though the append-only nature of +R means that there are still some nasty VM complications to deal with). Until that happens, mkisofs can be used to create a static UDF filesystem. Scott From owner-freebsd-stable@FreeBSD.ORG Fri May 16 18:20:47 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3C5B61065672; Fri, 16 May 2008 18:20:47 +0000 (UTC) (envelope-from tom.hurst@clara.net) Received: from spork.qfe3.net (spork.qfe3.net [212.13.207.101]) by mx1.freebsd.org (Postfix) with ESMTP id F1B168FC16; Fri, 16 May 2008 18:20:46 +0000 (UTC) (envelope-from tom.hurst@clara.net) Received: from [81.104.123.28] (helo=voi.aagh.net) by spork.qfe3.net with esmtp (Exim 4.66 (FreeBSD)) (envelope-from ) id 1Jx4Xt-0006m1-6Y; Fri, 16 May 2008 19:20:45 +0100 Received: from freaky by voi.aagh.net with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1Jx4Xs-0002jx-VY; Fri, 16 May 2008 19:20:44 +0100 Date: Fri, 16 May 2008 19:20:44 +0100 From: Thomas Hurst To: Evren Yurtesen Message-ID: <20080516182044.GA5921@voi.aagh.net> Mail-Followup-To: Evren Yurtesen , Jeremy Chadwick , freebsd-stable@freebsd.org References: <482B4DEE.3050705@ispro.net> <20080515010347.GA85202@eos.sc1.parodius.com> <482BE398.8010203@ispro.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <482BE398.8010203@ispro.net> Organization: Not much. User-Agent: Mutt/1.5.17 (2007-11-01) Sender: Thomas Hurst Cc: Jeremy Chadwick , freebsd-stable@freebsd.org Subject: Re: Approaching the limit on PV entries, consider increasing either the vm.pmap.shpgperproc or the vm.pmap.pv_entry_max sysctl. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2008 18:20:47 -0000 * Evren Yurtesen (yurtesen@ispro.net) wrote: > I guess one good question is, how can one see the number of PV entries > used by a process? shouldnt these appear in the output of ipcs -a > command? No, PV entries are a VM thing, not limited to SysV IPC. > Another good question is, in many places there is references to > rebooting after putting a new vm.pmap.shpgperproc value to > loader.conf. However I just changed this on a running system, has it > really been changed or was I suppose to reboot? Looking at the code it should be fine, the limit's just a couple of integers. > In either case, I already increased vm.pmap.shpgperproc to 2000 (from > 200) and still the error occurs, there is not so much load on this > box, maybe there is a leak somewhere? What sort of load is there? Do you have a bunch of big processes sharing significant chunks of memory in any way? -- Thomas 'Freaky' Hurst http://hur.st/ From owner-freebsd-stable@FreeBSD.ORG Fri May 16 18:35:25 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6CBA51065672 for ; Fri, 16 May 2008 18:35:25 +0000 (UTC) (envelope-from yurtesen@ispro.net) Received: from mail.ispro.net (mail.ispro.net [87.251.0.19]) by mx1.freebsd.org (Postfix) with ESMTP id B37918FC18 for ; Fri, 16 May 2008 18:35:21 +0000 (UTC) (envelope-from yurtesen@ispro.net) Received: (qmail 38660 invoked by uid 399); 16 May 2008 21:32:39 +0300 Received: from dsl-tkubrasgw1-fed0de00-174.dhcp.inet.fi (HELO ?80.222.208.174?) (yurtesen@ispro.net@80.222.208.174) by mail.ispro.net with ESMTPAM; 16 May 2008 21:32:39 +0300 X-Originating-IP: 80.222.208.174 Message-ID: <482DD410.6090102@ispro.net> Date: Fri, 16 May 2008 21:36:00 +0300 From: Evren Yurtesen User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: Evren Yurtesen , Jeremy Chadwick , freebsd-stable@freebsd.org References: <482B4DEE.3050705@ispro.net> <20080515010347.GA85202@eos.sc1.parodius.com> <482BE398.8010203@ispro.net> <20080516182044.GA5921@voi.aagh.net> In-Reply-To: <20080516182044.GA5921@voi.aagh.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: Approaching the limit on PV entries, consider increasing either the vm.pmap.shpgperproc or the vm.pmap.pv_entry_max sysctl. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2008 18:35:25 -0000 Thomas Hurst wrote: >> In either case, I already increased vm.pmap.shpgperproc to 2000 (from >> 200) and still the error occurs, there is not so much load on this >> box, maybe there is a leak somewhere? > > What sort of load is there? Do you have a bunch of big processes > sharing significant chunks of memory in any way? > How do I see what process is sharing memory and how much memory? There are a bunch of apache 2.2 processes working normally about 20-30 processes. This box doesnt do much more than that... I just checked the machine and here is what it looks like: 2:32PM up 18 days, 5:40, 3 users, load averages: 0.41, 0.36, 0.27 web:/root#ps ax |grep http 21429 ?? Ss 0:18.08 /usr/local/sbin/httpd 86473 ?? S 0:00.09 /usr/local/sbin/httpd 86659 ?? S 0:00.09 /usr/local/sbin/httpd 86851 ?? S 0:00.07 /usr/local/sbin/httpd 86857 ?? S 0:00.04 /usr/local/sbin/httpd 86912 ?? S 0:00.04 /usr/local/sbin/httpd 86918 ?? S 0:00.03 /usr/local/sbin/httpd 86919 ?? S 0:00.03 /usr/local/sbin/httpd 86996 ?? S 0:00.04 /usr/local/sbin/httpd 87023 ?? S 0:00.02 /usr/local/sbin/httpd 87028 ?? S 0:00.03 /usr/local/sbin/httpd 87059 ?? S 0:00.01 /usr/local/sbin/httpd 87060 ?? S 0:00.01 /usr/local/sbin/httpd 87062 ?? S 0:00.02 /usr/local/sbin/httpd 87065 ?? S 0:00.03 /usr/local/sbin/httpd 87074 ?? S 0:00.01 /usr/local/sbin/httpd 87076 ?? S 0:00.02 /usr/local/sbin/httpd 87077 ?? S 0:00.03 /usr/local/sbin/httpd 87079 ?? S 0:00.04 /usr/local/sbin/httpd 87081 ?? S 0:00.03 /usr/local/sbin/httpd 87083 ?? S 0:00.03 /usr/local/sbin/httpd 87085 ?? S 0:00.04 /usr/local/sbin/httpd 87090 ?? S 0:00.02 /usr/local/sbin/httpd 87190 p1 R+ 0:00.00 grep http web:/root# Although I see now that for 2 days the PV entries error did not appear. I wonder if it is spooling up somehow... There is a cron job restarting apache everyday at midnight so it cant be apache leaking perhaps. Thanks, Evren From owner-freebsd-stable@FreeBSD.ORG Fri May 16 19:07:20 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AB4591065670 for ; Fri, 16 May 2008 19:07:20 +0000 (UTC) (envelope-from rsmith@xs4all.nl) Received: from smtp-vbr10.xs4all.nl (smtp-vbr10.xs4all.nl [194.109.24.30]) by mx1.freebsd.org (Postfix) with ESMTP id 3D2CB8FC13 for ; Fri, 16 May 2008 19:07:20 +0000 (UTC) (envelope-from rsmith@xs4all.nl) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr10.xs4all.nl (8.13.8/8.13.8) with ESMTP id m4GJ7I60075427; Fri, 16 May 2008 21:07:19 +0200 (CEST) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id 2FF0BB82A; Fri, 16 May 2008 21:07:18 +0200 (CEST) Date: Fri, 16 May 2008 21:07:18 +0200 From: Roland Smith To: Willy Offermans Message-ID: <20080516190718.GA73178@slackbox.xs4all.nl> Mail-Followup-To: Willy Offermans , freebsd-stable@freebsd.org References: <20080421190403.GA4625@wiz.vpn.offrom.nl> <20080421201047.GB6884@slackbox.xs4all.nl> <20080516121414.GD4618@wiz.vpn.offrom.nl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="CE+1k2dSO48ffgeK" Content-Disposition: inline In-Reply-To: <20080516121414.GD4618@wiz.vpn.offrom.nl> X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 X-GPG-Key: http://www.xs4all.nl/~rsmith/pubkey.txt X-GPG-Notice: If this message is not signed, don't assume I sent it! User-Agent: Mutt/1.5.17 (2007-11-01) X-Virus-Scanned: by XS4ALL Virus Scanner Cc: freebsd-stable@freebsd.org Subject: Re: g_vfs_done error third part--PLEASE HELP! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2008 19:07:20 -0000 --CE+1k2dSO48ffgeK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, May 16, 2008 at 02:14:14PM +0200, Willy Offermans wrote: > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/ar0s1a 20308398 230438 18453290 1% / > devfs 1 1 0 100% /dev > /dev/ar0s1d 21321454 3814482 15801256 19% /usr > /dev/ar0s1e 50777034 5331686 41383186 11% /var > /dev/ar0s1f 101554150 18813760 74616058 20% /home > /dev/ar0s1g 274977824 34564876 218414724 14% /share >=20 > pretty normal I would say. Yes. > > Did you notice any file corruption in the filesystem on ar0s1g? >=20 > No the two disks are brand new and I did not encounter any noticeable > file corruption. However I assume that nowadays bad sectors on HD are > handled by the hardware and do not need any user interaction to correct > this. But maybe I'm totally wrong. Every ATA disk has spare sectors, and they usually don't report bad blocks untill the spares are exhausted. In which case it is prudent to replace the disk. > > Unmount the filesystem and run fsck(8) on it. Does it report any errors? >=20 > sun# fsck /dev/ar0s1g=20 > ** /dev/ar0s1g > ** Last Mounted on /share > ** Phase 1 - Check Blocks and Sizes > INCORRECT BLOCK COUNT I=3D34788357 (272 should be 264) > CORRECT? [yn] y >=20 > INCORRECT BLOCK COUNT I=3D34789217 (296 should be 288) > CORRECT? [yn] y >=20 > ** Phase 2 - Check Pathnames > ** Phase 3 - Check Connectivity > ** Phase 4 - Check Reference Counts > ** Phase 5 - Check Cyl groups > FREE BLK COUNT(S) WRONG IN SUPERBLK > SALVAGE? [yn] y >=20 > SUMMARY INFORMATION BAD > SALVAGE? [yn] y >=20 > BLK(S) MISSING IN BIT MAPS > SALVAGE? [yn] y >=20 > 182863 files, 17282440 used, 120206472 free (12448 frags, 15024253 > blocks, 0.0% fragmentation) >=20 > ***** FILE SYSTEM MARKED CLEAN ***** >=20 > ***** FILE SYSTEM WAS MODIFIED ***** >=20 > The usual stuff I would say. Disk corruption is never normal. It can be explained by if the machine crashed or was power-cycles before the disks were unmounted, but it can also indicate hardware troubles. > > > Any hints are very much appreciated. > So I have to conclude that the write error message does make sense and > that something seems to be wrong with the disks. The next question is > what can I do about it? Should I return the disks to the shop and ask > for new ones? Install sysutils/smartmontools, and run 'smartctl -A /dev/adX|less', where X are the numbers of the drives in the RAID array. In the output, look at the values for Reallocated_Sector_Ct, Current_Pending_Sector, Offline_Uncorrectable, which is the last number that you see on each line. A small number for Reallocated_Sector_Ct is allowable. But non-zero counts for Current_Pending_Sector or Offline_Uncorrectable means it's time to get a new disk. > However other people that I have contacted and who had a similar > problem before have solved it by using software raid setup instead of a > hardware raid setup. This seems to indicate that there is some bug in > the FreeBSD code. The RAID support that you find on most desktop motherboards _is_ software RAID. See ataraid(4). Roland --=20 R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) --CE+1k2dSO48ffgeK Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkgt22UACgkQEnfvsMMhpyVvxACdElN6UcWmej8KV+H2iZZgUrhK z1cAoIQh+c5yptPN58KAPhVlGVTw4exp =Eeol -----END PGP SIGNATURE----- --CE+1k2dSO48ffgeK-- From owner-freebsd-stable@FreeBSD.ORG Fri May 16 19:11:10 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D4EE71065676 for ; Fri, 16 May 2008 19:11:10 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from ftp.translate.ru (ftp.translate.ru [195.131.4.140]) by mx1.freebsd.org (Postfix) with ESMTP id 8E6118FC14 for ; Fri, 16 May 2008 19:11:10 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from desktop.home.serebryakov.spb.ru (unknown [89.163.10.141]) (Authenticated sender: lev@serebryakov.spb.ru) by ftp.translate.ru (Postfix) with ESMTPA id 6A54E13DF53 for ; Fri, 16 May 2008 23:11:09 +0400 (MSD) Date: Fri, 16 May 2008 23:11:16 +0400 From: Lev Serebryakov X-Mailer: The Bat! (v3.99.3) Professional Organization: FreeBSD X-Priority: 3 (Normal) Message-ID: <625532066.20080516231116@serebryakov.spb.ru> To: freebsd-stable@freebsd.org In-Reply-To: <482D6492.8080209@FreeBSD.org> References: <482D6492.8080209@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: quoted-printable Subject: Re: FreeBSD 7.0-STABLE: "mount_nfs" vs "mount -t nfs": problems with second one, UDP timeouts and ICMP ports unreach?! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lev@FreeBSD.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2008 19:11:10 -0000 Hello, freebsd-stable. You wrote 16 =CD=C1=D1 2008 =C7., 14:40:18: > There is NO any firewalls on B. And, I repeat, it WORKS when I call > mount_nfs directly in a moment! Adding `-o -c' to mount (to pass `-c' to mount_nfs) helps. But I'm very curious WHY mount_nfs, called directly, work WITHOUT `-c'... --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-stable@FreeBSD.ORG Sat May 17 00:53:07 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 01986106566B; Sat, 17 May 2008 00:53:07 +0000 (UTC) (envelope-from tom.hurst@clara.net) Received: from spork.qfe3.net (spork.qfe3.net [212.13.207.101]) by mx1.freebsd.org (Postfix) with ESMTP id B291E8FC14; Sat, 17 May 2008 00:53:06 +0000 (UTC) (envelope-from tom.hurst@clara.net) Received: from [81.104.123.28] (helo=voi.aagh.net) by spork.qfe3.net with esmtp (Exim 4.66 (FreeBSD)) (envelope-from ) id 1JxAfY-0009i6-LU; Sat, 17 May 2008 01:53:04 +0100 Received: from freaky by voi.aagh.net with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1JxAfY-000Gxf-At; Sat, 17 May 2008 01:53:04 +0100 Date: Sat, 17 May 2008 01:53:04 +0100 From: Thomas Hurst To: Evren Yurtesen Message-ID: <20080517005304.GA63122@voi.aagh.net> Mail-Followup-To: Evren Yurtesen , Jeremy Chadwick , freebsd-stable@freebsd.org References: <482B4DEE.3050705@ispro.net> <20080515010347.GA85202@eos.sc1.parodius.com> <482BE398.8010203@ispro.net> <20080516182044.GA5921@voi.aagh.net> <482DD410.6090102@ispro.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <482DD410.6090102@ispro.net> Organization: Not much. User-Agent: Mutt/1.5.17 (2007-11-01) Sender: Thomas Hurst Cc: Jeremy Chadwick , freebsd-stable@freebsd.org Subject: Re: Approaching the limit on PV entries, consider increasing either the vm.pmap.shpgperproc or the vm.pmap.pv_entry_max sysctl. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 May 2008 00:53:07 -0000 * Evren Yurtesen (yurtesen@ispro.net) wrote: > How do I see what process is sharing memory and how much memory? Guessing is normally sufficient; typically it's processes with the same name and similar size/res. On 7-STABLE you can use procstat -v to look at the VM mappings for a process, but typically that'll be overkill. > There are a bunch of apache 2.2 processes working normally about 20-30 > processes. This box doesnt do much more than that... > > I just checked the machine and here is what it looks like: > 2:32PM up 18 days, 5:40, 3 users, load averages: 0.41, 0.36, 0.27 > > web:/root#ps ax |grep http > 21429 ?? Ss 0:18.08 /usr/local/sbin/httpd > 86473 ?? S 0:00.09 /usr/local/sbin/httpd > 86659 ?? S 0:00.09 /usr/local/sbin/httpd > > Although I see now that for 2 days the PV entries error did not appear. I > wonder if it is spooling up somehow... They do look a bit small to be triggering it; assuming they're sharing most of that, that's still only about 400k pv entries; 5MB or so (12 bytes per entry). The systems I've seen pv entries run out on run to a couple of orders of magnitude more than that. > There is a cron job restarting apache everyday at midnight so it cant > be apache leaking perhaps. Load spikes maybe? Child count running into the stratosphere? Big PHP opcode cache? -- Thomas 'Freaky' Hurst http://hur.st/ From owner-freebsd-stable@FreeBSD.ORG Sat May 17 05:38:33 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 05C54106564A for ; Sat, 17 May 2008 05:38:33 +0000 (UTC) (envelope-from emikulic@gmail.com) Received: from ipmail01.adl6.internode.on.net (ipmail01.adl6.internode.on.net [203.16.214.146]) by mx1.freebsd.org (Postfix) with ESMTP id 88EC38FC1F for ; Sat, 17 May 2008 05:38:32 +0000 (UTC) (envelope-from emikulic@gmail.com) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApsEADcKLkiWZaK6/2dsb2JhbACLCaIC X-IronPort-AV: E=Sophos;i="4.27,500,1204464600"; d="scan'208";a="104307131" Received: from ppp162-186.static.internode.on.net ([150.101.162.186]) by ipmail01.adl6.internode.on.net with ESMTP; 17 May 2008 15:08:30 +0930 Received: by ppp162-186.static.internode.on.net (Poofix, from userid 1001) id 4A3FE409F; Sat, 17 May 2008 15:38:29 +1000 (EST) Date: Sat, 17 May 2008 15:38:29 +1000 From: Emil Mikulic To: Paul Saab Message-ID: <20080517053829.GA73251@dmr.ath.cx> References: <20080516073932.GA39803@dmr.ath.cx> <5c0ff6a70805160103o75461976wce04f697975a176c@mail.gmail.com> <5c0ff6a70805160119n2f8361c4y7b3c1451f36d3c6e@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5c0ff6a70805160119n2f8361c4y7b3c1451f36d3c6e@mail.gmail.com> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-stable@freebsd.org, Claus Guttesen Subject: Re: ciss(4) not coping with large arrays? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 May 2008 05:38:33 -0000 On Fri, May 16, 2008 at 01:19:33AM -0700, Paul Saab wrote: > Emil: > > Running today's RELENG_7 (although 7.0-RELEASE has the same problem), > > GENERIC kernel on an amd64 and I can't seem to get a da(4) device for > > any arrays bigger than 2TB. > > Please try the following patch: > > http://yogurt.org/FreeBSD/ciss_large.diff This works a treat! da4 at ciss0 bus 0 target 4 lun 0 da4: Fixed Direct Access SCSI-5 device da4: 135.168MB/s transfers da4: 3815350MB (7813837232 512 byte sectors: 255H 32S/T 65535C) Double thanks for committing it, and for merging to RELENG_7! --Emil From owner-freebsd-stable@FreeBSD.ORG Sat May 17 07:50:01 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6156F106564A for ; Sat, 17 May 2008 07:50:01 +0000 (UTC) (envelope-from willy@Offermans.Rompen.nl) Received: from cpsmtpo-eml03.kpnxchange.com (cpsmtpo-eml03.kpnxchange.com [213.75.38.152]) by mx1.freebsd.org (Postfix) with ESMTP id DC2378FC18 for ; Sat, 17 May 2008 07:50:00 +0000 (UTC) (envelope-from willy@Offermans.Rompen.nl) Received: from cpsmtp-eml107.kpnxchange.com ([213.75.84.107]) by cpsmtpo-eml03.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.1830); Sat, 17 May 2008 09:49:59 +0200 Received: from koko.offrom.nl ([86.82.183.148]) by cpsmtp-eml107.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.1830); Sat, 17 May 2008 09:49:58 +0200 Received: from wiz.vpn.offrom.nl (Debian-exim@wiz.vpn.offrom.nl [10.168.0.18]) by koko.offrom.nl (8.13.8/8.13.8) with ESMTP id m4H7nr0e015281; Sat, 17 May 2008 09:49:53 +0200 (CEST) (envelope-from willy@wiz.vpn.offrom.nl) Received: from willy by wiz.vpn.offrom.nl with local (Exim 4.63) (envelope-from ) id 1JxHDL-0001qD-3K; Sat, 17 May 2008 09:52:23 +0200 Date: Sat, 17 May 2008 09:52:23 +0200 From: Willy Offermans To: Roland Smith Message-ID: <20080517075222.GA4250@wiz.vpn.offrom.nl> References: <20080421190403.GA4625@wiz.vpn.offrom.nl> <20080421201047.GB6884@slackbox.xs4all.nl> <20080516121414.GD4618@wiz.vpn.offrom.nl> <20080516190718.GA73178@slackbox.xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080516190718.GA73178@slackbox.xs4all.nl> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: ClamAV 0.92.1/7141/Sat May 17 03:12:19 2008 on koko.offrom.nl X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.2.4 X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on koko.offrom.nl X-OriginalArrivalTime: 17 May 2008 07:49:58.0923 (UTC) FILETIME=[9AECADB0:01C8B7F2] Cc: freebsd-stable@FreeBSD.ORG Subject: Re: g_vfs_done error third part--PLEASE HELP! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Willy@Offermans.Rompen.nl List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 May 2008 07:50:01 -0000 Hello Roland and FreeBSD friends, On Fri, May 16, 2008 at 09:07:18PM +0200, Roland Smith wrote: > On Fri, May 16, 2008 at 02:14:14PM +0200, Willy Offermans wrote: > > > Filesystem 1K-blocks Used Avail Capacity Mounted on > > /dev/ar0s1a 20308398 230438 18453290 1% / > > devfs 1 1 0 100% /dev > > /dev/ar0s1d 21321454 3814482 15801256 19% /usr > > /dev/ar0s1e 50777034 5331686 41383186 11% /var > > /dev/ar0s1f 101554150 18813760 74616058 20% /home > > /dev/ar0s1g 274977824 34564876 218414724 14% /share > > > > pretty normal I would say. > > Yes. > > > > Did you notice any file corruption in the filesystem on ar0s1g? > > > > No the two disks are brand new and I did not encounter any noticeable > > file corruption. However I assume that nowadays bad sectors on HD are > > handled by the hardware and do not need any user interaction to correct > > this. But maybe I'm totally wrong. > > Every ATA disk has spare sectors, and they usually don't report bad > blocks untill the spares are exhausted. In which case it is prudent to > replace the disk. > > > > Unmount the filesystem and run fsck(8) on it. Does it report any errors? > > > > sun# fsck /dev/ar0s1g > > ** /dev/ar0s1g > > ** Last Mounted on /share > > ** Phase 1 - Check Blocks and Sizes > > INCORRECT BLOCK COUNT I=34788357 (272 should be 264) > > CORRECT? [yn] y > > > > INCORRECT BLOCK COUNT I=34789217 (296 should be 288) > > CORRECT? [yn] y > > > > ** Phase 2 - Check Pathnames > > ** Phase 3 - Check Connectivity > > ** Phase 4 - Check Reference Counts > > ** Phase 5 - Check Cyl groups > > FREE BLK COUNT(S) WRONG IN SUPERBLK > > SALVAGE? [yn] y > > > > SUMMARY INFORMATION BAD > > SALVAGE? [yn] y > > > > BLK(S) MISSING IN BIT MAPS > > SALVAGE? [yn] y > > > > 182863 files, 17282440 used, 120206472 free (12448 frags, 15024253 > > blocks, 0.0% fragmentation) > > > > ***** FILE SYSTEM MARKED CLEAN ***** > > > > ***** FILE SYSTEM WAS MODIFIED ***** > > > > The usual stuff I would say. > > Disk corruption is never normal. It can be explained by if the machine > crashed or was power-cycles before the disks were unmounted, but it can > also indicate hardware troubles. > > > > > Any hints are very much appreciated. > > > So I have to conclude that the write error message does make sense and > > that something seems to be wrong with the disks. The next question is > > what can I do about it? Should I return the disks to the shop and ask > > for new ones? > > Install sysutils/smartmontools, and run 'smartctl -A /dev/adX|less', where X > are the numbers of the drives in the RAID array. > > In the output, look at the values for Reallocated_Sector_Ct, > Current_Pending_Sector, Offline_Uncorrectable, which is the last number > that you see on each line. > > A small number for Reallocated_Sector_Ct is allowable. But non-zero counts > for Current_Pending_Sector or Offline_Uncorrectable means it's time to > get a new disk. sun# atacontrol status ar0 ar0: ATA RAID1 status: READY subdisks: 0 ad4 ONLINE 1 ad6 ONLINE So ad4 and ad6 are the HDs of the array. sun# smartctl -A /dev/ad6 smartctl version 5.38 [i386-portbld-freebsd7.0] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF READ SMART DATA SECTION === SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 100 100 051 Pre-fail Always - 3 3 Spin_Up_Time 0x0007 100 100 015 Pre-fail Always - 7232 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 31 5 Reallocated_Sector_Ct 0x0033 253 253 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 253 253 051 Pre-fail Always - 0 8 Seek_Time_Performance 0x0025 253 253 015 Pre-fail Offline - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 1478 10 Spin_Retry_Count 0x0033 253 253 051 Pre-fail Always - 0 11 Calibration_Retry_Count 0x0012 253 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 31 13 Read_Soft_Error_Rate 0x000e 100 100 000 Old_age Always - 439070649 187 Reported_Uncorrect 0x0032 253 253 000 Old_age Always - 0 188 Unknown_Attribute 0x0032 253 253 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 062 060 000 Old_age Always - 38 194 Temperature_Celsius 0x0022 124 115 000 Old_age Always - 38 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 439070649 196 Reallocated_Event_Count 0x0032 253 253 000 Old_age Always - 0 197 Current_Pending_Sector 0x0012 253 253 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 253 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x000a 100 100 000 Old_age Always - 0 201 Soft_Read_Error_Rate 0x000a 100 100 000 Old_age Always - 0 202 TA_Increase_Count 0x0032 253 253 000 Old_age Always - 0 un# smartctl -A /dev/ad4 smartctl version 5.38 [i386-portbld-freebsd7.0] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF READ SMART DATA SECTION === SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 100 100 051 Pre-fail Always - 109 3 Spin_Up_Time 0x0007 100 100 015 Pre-fail Always - 7360 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 32 5 Reallocated_Sector_Ct 0x0033 253 253 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 253 253 051 Pre-fail Always - 0 8 Seek_Time_Performance 0x0025 253 253 015 Pre-fail Offline - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 1478 10 Spin_Retry_Count 0x0033 253 253 051 Pre-fail Always - 0 11 Calibration_Retry_Count 0x0012 253 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 31 13 Read_Soft_Error_Rate 0x000e 100 100 000 Old_age Always - 835531250 187 Reported_Uncorrect 0x0032 253 253 000 Old_age Always - 0 188 Unknown_Attribute 0x0032 253 253 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 062 060 000 Old_age Always - 38 194 Temperature_Celsius 0x0022 124 118 000 Old_age Always - 38 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 835531250 196 Reallocated_Event_Count 0x0032 253 253 000 Old_age Always - 0 197 Current_Pending_Sector 0x0012 253 253 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 253 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x000a 100 100 000 Old_age Always - 0 201 Soft_Read_Error_Rate 0x000a 100 100 000 Old_age Always - 0 202 TA_Increase_Count 0x0032 253 253 000 Old_age Always - 0 The critical values you have mentioned are all zero, but maybe you notice some other oddities. > > > However other people that I have contacted and who had a similar > > problem before have solved it by using software raid setup instead of a > > hardware raid setup. This seems to indicate that there is some bug in > > the FreeBSD code. > > The RAID support that you find on most desktop motherboards _is_ > software RAID. See ataraid(4). Well then read motherboard supported raid instead of hardware raid! What I meant was that Toomas noticed a similar problem and turned to gmirror to ``solve'' the issue. But somewhere is something weird going on. I'm not the first one to discover this and would be nice to nail it down, so that in the future no one has to suffer anymore from this. > > Roland > -- > R.F.Smith http://www.xs4all.nl/~rsmith/ > [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] > pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, De jrus wah, Willy ************************************* W.K. Offermans Home: +31 45 544 49 44 Mobile: +31 653 27 16 23 e-mail: Willy@Offermans.Rompen.nl Powered by .... (__) \\\'',) \/ \ ^ .\._/_) www.FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Sat May 17 10:16:28 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 403AD1065670 for ; Sat, 17 May 2008 10:16:28 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 2CAB38FC35 for ; Sat, 17 May 2008 10:16:27 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id DA9221CC033; Sat, 17 May 2008 03:16:27 -0700 (PDT) Date: Sat, 17 May 2008 03:16:27 -0700 From: Jeremy Chadwick To: Willy Offermans Message-ID: <20080517101627.GA42928@eos.sc1.parodius.com> References: <20080421190403.GA4625@wiz.vpn.offrom.nl> <20080421201047.GB6884@slackbox.xs4all.nl> <20080516121414.GD4618@wiz.vpn.offrom.nl> <20080516190718.GA73178@slackbox.xs4all.nl> <20080517075222.GA4250@wiz.vpn.offrom.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080517075222.GA4250@wiz.vpn.offrom.nl> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: Roland Smith , freebsd-stable@FreeBSD.ORG Subject: Re: g_vfs_done error third part--PLEASE HELP! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 May 2008 10:16:28 -0000 On Sat, May 17, 2008 at 09:52:23AM +0200, Willy Offermans wrote: > sun# atacontrol status ar0 > ar0: ATA RAID1 status: READY > subdisks: > 0 ad4 ONLINE > 1 ad6 ONLINE What ataraid(4) method are you using? Promise FastTrak? Adaptec HostRAID? Intel MatrixRAID? Please let us know, as there are some known long-standing bugs with ataraid(4) that could (no guarantee) explain what's going on. > So ad4 and ad6 are the HDs of the array. > > sun# smartctl -A /dev/ad6 This excludes the brand/model of hard disks you have. Can you please tell us this? Different hard disk manufacturers do different things with SMART statistics. Your SMART statistics look okay, but depending upon what drive model and manufacturer is being used, they could be indicative of a problem. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Sat May 17 12:43:25 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D9726106567A for ; Sat, 17 May 2008 12:43:25 +0000 (UTC) (envelope-from yurtesen@ispro.net) Received: from mail.ispro.net (mail.ispro.net [87.251.0.19]) by mx1.freebsd.org (Postfix) with ESMTP id 1C77B8FC13 for ; Sat, 17 May 2008 12:43:23 +0000 (UTC) (envelope-from yurtesen@ispro.net) Received: (qmail 48124 invoked by uid 399); 17 May 2008 15:40:38 +0300 Received: from dsl-tkubrasgw1-fed0de00-174.dhcp.inet.fi (HELO ?80.222.208.174?) (yurtesen@ispro.net@80.222.208.174) by mail.ispro.net with ESMTPAM; 17 May 2008 15:40:38 +0300 X-Originating-IP: 80.222.208.174 Message-ID: <482ED30C.3030802@ispro.net> Date: Sat, 17 May 2008 15:43:56 +0300 From: Evren Yurtesen User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: Evren Yurtesen , Jeremy Chadwick , freebsd-stable@freebsd.org References: <482B4DEE.3050705@ispro.net> <20080515010347.GA85202@eos.sc1.parodius.com> <482BE398.8010203@ispro.net> <20080516182044.GA5921@voi.aagh.net> <482DD410.6090102@ispro.net> <20080517005304.GA63122@voi.aagh.net> In-Reply-To: <20080517005304.GA63122@voi.aagh.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: Approaching the limit on PV entries, consider increasing either the vm.pmap.shpgperproc or the vm.pmap.pv_entry_max sysctl. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 May 2008 12:43:25 -0000 Thomas Hurst wrote: > * Evren Yurtesen (yurtesen@ispro.net) wrote: > >> How do I see what process is sharing memory and how much memory? > > Guessing is normally sufficient; typically it's processes with the same > name and similar size/res. On 7-STABLE you can use procstat -v to look > at the VM mappings for a process, but typically that'll be overkill. Thanks, I will try to check procstat -v when I start seeing the error message coming. When the system is showing "Approaching the limit on PV entries" is it related to number of allocations I see in procstat -v output? Is each line an PV entry? How can one obtain same information from 6.x i386? (just asking to compare similar systems) >> There are a bunch of apache 2.2 processes working normally about 20-30 >> processes. This box doesnt do much more than that... >> >> I just checked the machine and here is what it looks like: >> 2:32PM up 18 days, 5:40, 3 users, load averages: 0.41, 0.36, 0.27 >> >> web:/root#ps ax |grep http >> 21429 ?? Ss 0:18.08 /usr/local/sbin/httpd >> 86473 ?? S 0:00.09 /usr/local/sbin/httpd >> 86659 ?? S 0:00.09 /usr/local/sbin/httpd >> >> Although I see now that for 2 days the PV entries error did not appear. I >> wonder if it is spooling up somehow... > > They do look a bit small to be triggering it; assuming they're sharing > most of that, that's still only about 400k pv entries; 5MB or so (12 > bytes per entry). The systems I've seen pv entries run out on run to a > couple of orders of magnitude more than that. >> There is a cron job restarting apache everyday at midnight so it cant >> be apache leaking perhaps. > > Load spikes maybe? Child count running into the stratosphere? Big PHP > opcode cache? The machine is primarily serving perl pages through mod_perl2 and there are a few PHP sites too but they are negligible. It is just that I never saw this kind of message coming out on 6.3-stable i386 with the same sites which is kind of weird. However a load spike might be the cause of course, I will try to catch this when PV entry warning appear. Now that I know that procstat can show me more info, I can try to collect some info to see if something looks weird. I will let you guys know of my findings. Thanks for the great help! This information was very useful. Thanks, Evren From owner-freebsd-stable@FreeBSD.ORG Sat May 17 14:48:56 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 43D491065672; Sat, 17 May 2008 14:48:56 +0000 (UTC) (envelope-from johan@stromnet.se) Received: from core.stromnet.se (core.stromnet.se [83.218.84.131]) by mx1.freebsd.org (Postfix) with ESMTP id ED7BF8FC24; Sat, 17 May 2008 14:48:55 +0000 (UTC) (envelope-from johan@stromnet.se) Received: from localhost (core.stromnet.se [83.218.84.131]) by core.stromnet.se (Postfix) with ESMTP id AAC5CF58CF1; Sat, 17 May 2008 16:33:25 +0200 (CEST) X-Virus-Scanned: amavisd-new at stromnet.se X-Spam-Flag: NO X-Spam-Score: 0.375 X-Spam-Level: X-Spam-Status: No, score=0.375 tagged_above=0 required=6.2 tests=[AWL=2.181, BAYES_00=-2.599, RDNS_DYNAMIC=0.1, SPF_FAIL=0.693] Received: from core.stromnet.se ([83.218.84.131]) by localhost (core.stromnet.se [83.218.84.131]) (amavisd-new, port 10024) with ESMTP id 09knv3Onvj+d; Sat, 17 May 2008 16:33:23 +0200 (CEST) Received: from johan-mp.stromnet.se (90-224-172-102-no129.tbcn.telia.com [90.224.172.102]) by core.stromnet.se (Postfix) with ESMTP id 92DD4F58BC1; Sat, 17 May 2008 16:33:22 +0200 (CEST) Message-Id: <678A03F5-5E8A-4CF6-90DF-AA9A4F30FBE1@stromnet.se> From: =?ISO-8859-1?Q?Johan_Str=F6m?= To: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Apple Message framework v919.2) Date: Sat, 17 May 2008 16:33:20 +0200 X-Mailer: Apple Mail (2.919.2) Cc: Subject: connect(): Operation not permitted X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 May 2008 14:48:56 -0000 Hello I got a FreeBSD 7 machine running mail services (among other things). =20= This machine recently replaced a FreeBSD 6.2 machine doing the same =20 tasks. Now and then I need to send alot of mail to customers (mailing list), =20= and one thing i've noticed now after the change is that when I use a =20 lot of connections subsequently (high connection rate, even if they =20 are very shortlived) inside a jail (dunno if that has anything to do =20 with it though), I start to get Operation not permitted in return to =20 connect(). I've seen this in the PHP app that sends mail, when it tried to =20 connect to localhost, as well as from postfix when it have been trying =20= to connect to amavisd on localhost, but also from postfix when it has =20= tried to connect to remote SMTP servers. I do have PF for filtering, but there are no max-src-conn-rate limits =20= enabled for any rules that is used for this. However, from one of the =20= jail I do have a hfsc queue limiting the outgoing mail traffic from =20 one jailed IP. But I'm not sure that this would be the problem, since =20= I've also seen the problem when doing localhost connects in the jail, =20= and also in other jails on an entierly different IP that is not =20 affected. Does anyone have any clues about what I can look at and tune to fix =20 this? Thanks! -- Johan Str=F6m Stromnet johan@stromnet.se http://www.stromnet.se/ From owner-freebsd-stable@FreeBSD.ORG Sat May 17 15:23:48 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 73D981065678 for ; Sat, 17 May 2008 15:23:48 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 5F2918FC16 for ; Sat, 17 May 2008 15:23:48 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 28AF21CC033; Sat, 17 May 2008 08:23:48 -0700 (PDT) Date: Sat, 17 May 2008 08:23:48 -0700 From: Jeremy Chadwick To: Johan =?iso-8859-1?Q?Str=F6m?= Message-ID: <20080517152348.GA64850@eos.sc1.parodius.com> References: <678A03F5-5E8A-4CF6-90DF-AA9A4F30FBE1@stromnet.se> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <678A03F5-5E8A-4CF6-90DF-AA9A4F30FBE1@stromnet.se> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Subject: Re: connect(): Operation not permitted X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 May 2008 15:23:48 -0000 On Sat, May 17, 2008 at 04:33:20PM +0200, Johan Ström wrote: > Hello > > I got a FreeBSD 7 machine running mail services (among other things). This > machine recently replaced a FreeBSD 6.2 machine doing the same tasks. > Now and then I need to send alot of mail to customers (mailing list), and > one thing i've noticed now after the change is that when I use a lot of > connections subsequently (high connection rate, even if they are very > shortlived) inside a jail (dunno if that has anything to do with it > though), I start to get Operation not permitted in return to connect(). > I've seen this in the PHP app that sends mail, when it tried to connect to > localhost, as well as from postfix when it have been trying to connect to > amavisd on localhost, but also from postfix when it has tried to connect to > remote SMTP servers. > > I do have PF for filtering, but there are no max-src-conn-rate limits > enabled for any rules that is used for this. However, from one of the jail > I do have a hfsc queue limiting the outgoing mail traffic from one jailed > IP. But I'm not sure that this would be the problem, since I've also seen > the problem when doing localhost connects in the jail, and also in other > jails on an entierly different IP that is not affected. > > Does anyone have any clues about what I can look at and tune to fix this? Operation not permitted is most commonly seen on machines using pf(4), where there are rules blocking certain outbound traffic. I believe this has nothing to do with max-src-conn-rate. Chances are some of your pf(4) rules are wrong. There is also the possibility that jails are causing your problem. I have no experience with jails, so I cannot comment on that. I'd consider re-posting your problem to freebsd-pf@freebsd.org, and include your entire pf ruleset, so people could analyse it. Output from "pfctl -s info" would also be benefitial. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Sat May 17 15:36:54 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 763061065673; Sat, 17 May 2008 15:36:54 +0000 (UTC) (envelope-from alex@trull.org) Received: from mail.internationalconspiracy.org (mail.internationalconspiracy.org [85.234.142.62]) by mx1.freebsd.org (Postfix) with ESMTP id 09EE18FC19; Sat, 17 May 2008 15:36:53 +0000 (UTC) (envelope-from alex@trull.org) Received: from localhost (mail.internationalconspiracy.org [85.234.142.62]) by mail.internationalconspiracy.org (Postfix) with ESMTP id 19770646F5; Sat, 17 May 2008 16:19:50 +0100 (BST) X-Virus-Scanned: amavisd-new at mail.internationalconspiracy.org Received: from mail.internationalconspiracy.org ([85.234.142.62]) by localhost (mail.internationalconspiracy.org [85.234.142.62]) (amavisd-new, port 10024) with LMTP id vpQpBUVHZVOI; Sat, 17 May 2008 16:19:29 +0100 (BST) Received: from [192.168.124.200] (77-96-69-222.cable.ubr09.croy.blueyonder.co.uk [77.96.69.222]) by mail.internationalconspiracy.org (Postfix) with ESMTPSA id 1C2BB646DD; Sat, 17 May 2008 16:19:29 +0100 (BST) From: Alex Trull To: Johan =?ISO-8859-1?Q?Str=F6m?= , freebsd-net@freebsd.org, freebsd-stable In-Reply-To: <678A03F5-5E8A-4CF6-90DF-AA9A4F30FBE1@stromnet.se> References: <678A03F5-5E8A-4CF6-90DF-AA9A4F30FBE1@stromnet.se> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-4WU6AqCfRhU+2u6n9jki" Date: Sat, 17 May 2008 16:19:23 +0100 Message-Id: <1211037564.6326.27.camel@porksoda> Mime-Version: 1.0 X-Mailer: Evolution 2.22.1 Cc: Subject: Re: connect(): Operation not permitted X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 May 2008 15:36:54 -0000 --=-4WU6AqCfRhU+2u6n9jki Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Johan and List, In my case a few months ago it was pahu. Don't give that fine fellow an account on your precious system ! But seriously, I had a pf-firewalled jail being being used for DNS testing, with large numbers of udp "connections" hanging around in pf state. While the default udp timeout settings in PF are lower than those of the tcp timeouts, it is was still too high for it to to remove the states in time before hitting the default 10k state limit! If this is the case with you - run 'pfctl -s state | wc -l' - when there is traffic load you may see that hitting 10k states if you've not tuned that variable. What to do next - up the state limit or lower the state timeouts. I did both, to be safe. in /etc/pf.conf these must be at the very top of the file: # options # 10k is insanely low, lets raise it.. set limit { frags 16384, states 32768 } # timeouts - see 'pfctl -s timeouts' for options - you will want to=20 # change the tcp ones rather than the udp ones for your smtp setup.=20 # but these are mine, I set them for the dns traffic. set timeout { udp.first 15, udp.single 5, udp.multiple 30 } don't forget to: $ /etc/rc.d/pf check && =EF=BB=BF/etc/rc.d/pf reload HTH, Alex On Sat, 2008-05-17 at 16:33 +0200, Johan Str=C3=B6m wrote: > Hello >=20 > I got a FreeBSD 7 machine running mail services (among other things). =20 > This machine recently replaced a FreeBSD 6.2 machine doing the same =20 > tasks. > Now and then I need to send alot of mail to customers (mailing list), =20 > and one thing i've noticed now after the change is that when I use a =20 > lot of connections subsequently (high connection rate, even if they =20 > are very shortlived) inside a jail (dunno if that has anything to do =20 > with it though), I start to get Operation not permitted in return to =20 > connect(). > I've seen this in the PHP app that sends mail, when it tried to =20 > connect to localhost, as well as from postfix when it have been trying =20 > to connect to amavisd on localhost, but also from postfix when it has =20 > tried to connect to remote SMTP servers. >=20 > I do have PF for filtering, but there are no max-src-conn-rate limits =20 > enabled for any rules that is used for this. However, from one of the =20 > jail I do have a hfsc queue limiting the outgoing mail traffic from =20 > one jailed IP. But I'm not sure that this would be the problem, since =20 > I've also seen the problem when doing localhost connects in the jail, =20 > and also in other jails on an entierly different IP that is not =20 > affected. >=20 > Does anyone have any clues about what I can look at and tune to fix =20 > this? >=20 > Thanks! >=20 > -- > Johan Str=C3=B6m > Stromnet > johan@stromnet.se > http://www.stromnet.se/ >=20 >=20 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" --=-4WU6AqCfRhU+2u6n9jki Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQBILvd7ey4m6/eWxTQRAhuWAJ9MaVHRQkza3Hdb25CtQhHiz09KMwCfQzVw dSLK+Ik5TadrYUpngZeyQS4= =7Fyq -----END PGP SIGNATURE----- --=-4WU6AqCfRhU+2u6n9jki-- From owner-freebsd-stable@FreeBSD.ORG Sat May 17 15:41:45 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4B4CF1065676; Sat, 17 May 2008 15:41:45 +0000 (UTC) (envelope-from willy@Offermans.Rompen.nl) Received: from hpsmtp-eml13.kpnxchange.com (hpsmtp-eml13.kpnxchange.com [213.75.38.113]) by mx1.freebsd.org (Postfix) with ESMTP id C7C248FC15; Sat, 17 May 2008 15:41:44 +0000 (UTC) (envelope-from willy@Offermans.Rompen.nl) Received: from cpsmtp-eml106.kpnxchange.com ([213.75.84.106]) by hpsmtp-eml13.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.1830); Sat, 17 May 2008 17:41:43 +0200 Received: from koko.offrom.nl ([86.82.183.148]) by cpsmtp-eml106.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.1830); Sat, 17 May 2008 17:41:43 +0200 Received: from wiz.vpn.offrom.nl (Debian-exim@wiz.vpn.offrom.nl [10.168.0.18]) by koko.offrom.nl (8.13.8/8.13.8) with ESMTP id m4HFfeHa017917; Sat, 17 May 2008 17:41:40 +0200 (CEST) (envelope-from willy@wiz.vpn.offrom.nl) Received: from willy by wiz.vpn.offrom.nl with local (Exim 4.63) (envelope-from ) id 1JxOZv-0002W8-K1; Sat, 17 May 2008 17:44:11 +0200 Date: Sat, 17 May 2008 17:44:11 +0200 From: Willy Offermans To: Jeremy Chadwick Message-ID: <20080517154411.GA9504@wiz.vpn.offrom.nl> References: <20080421190403.GA4625@wiz.vpn.offrom.nl> <20080421201047.GB6884@slackbox.xs4all.nl> <20080516121414.GD4618@wiz.vpn.offrom.nl> <20080516190718.GA73178@slackbox.xs4all.nl> <20080517075222.GA4250@wiz.vpn.offrom.nl> <20080517101627.GA42928@eos.sc1.parodius.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080517101627.GA42928@eos.sc1.parodius.com> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: ClamAV 0.92.1/7141/Sat May 17 03:12:19 2008 on koko.offrom.nl X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.2.4 X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on koko.offrom.nl X-OriginalArrivalTime: 17 May 2008 15:41:43.0176 (UTC) FILETIME=[8192F080:01C8B834] Cc: freebsd-stable@FreeBSD.org Subject: Re: g_vfs_done error third part--PLEASE HELP! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Willy@Offermans.Rompen.nl List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 May 2008 15:41:45 -0000 Hello Jeremy and FreeBSD friends, On Sat, May 17, 2008 at 03:16:27AM -0700, Jeremy Chadwick wrote: > On Sat, May 17, 2008 at 09:52:23AM +0200, Willy Offermans wrote: > > sun# atacontrol status ar0 > > ar0: ATA RAID1 status: READY > > subdisks: > > 0 ad4 ONLINE > > 1 ad6 ONLINE > > What ataraid(4) method are you using? Promise FastTrak? Adaptec > HostRAID? Intel MatrixRAID? Please let us know, as there are some > known long-standing bugs with ataraid(4) that could (no guarantee) > explain what's going on. > > > So ad4 and ad6 are the HDs of the array. > > > > sun# smartctl -A /dev/ad6 > > This excludes the brand/model of hard disks you have. Can you please > tell us this? Different hard disk manufacturers do different things > with SMART statistics. > > Your SMART statistics look okay, but depending upon what drive model and > manufacturer is being used, they could be indicative of a problem. > > -- >From /var/run/dmesg.boot: ar0: 476837MB status: READY ad4: 476940MB at ata2-master SATA150 ad6: 476940MB at ata3-master SATA150 I hope this is the information you are asking for. -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, De jrus wah, Willy ************************************* W.K. Offermans Home: +31 45 544 49 44 Mobile: +31 653 27 16 23 e-mail: Willy@Offermans.Rompen.nl Powered by .... (__) \\\'',) \/ \ ^ .\._/_) www.FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Sat May 17 16:01:19 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B1A3E106564A; Sat, 17 May 2008 16:01:19 +0000 (UTC) (envelope-from johan@stromnet.se) Received: from core.stromnet.se (core.stromnet.se [83.218.84.131]) by mx1.freebsd.org (Postfix) with ESMTP id 30C848FC0A; Sat, 17 May 2008 16:01:18 +0000 (UTC) (envelope-from johan@stromnet.se) Received: from localhost (core.stromnet.se [83.218.84.131]) by core.stromnet.se (Postfix) with ESMTP id BBDCEF59403; Sat, 17 May 2008 18:01:16 +0200 (CEST) X-Virus-Scanned: amavisd-new at stromnet.se X-Spam-Flag: NO X-Spam-Score: 0.294 X-Spam-Level: X-Spam-Status: No, score=0.294 tagged_above=0 required=6.2 tests=[AWL=2.100, BAYES_00=-2.599, RDNS_DYNAMIC=0.1, SPF_FAIL=0.693] Received: from core.stromnet.se ([83.218.84.131]) by localhost (core.stromnet.se [83.218.84.131]) (amavisd-new, port 10024) with ESMTP id Y9G3KTO53EEo; Sat, 17 May 2008 18:01:14 +0200 (CEST) Received: from johan-mp.stromnet.se (90-224-172-102-no129.tbcn.telia.com [90.224.172.102]) by core.stromnet.se (Postfix) with ESMTP id BAEE3F58D78; Sat, 17 May 2008 18:01:12 +0200 (CEST) Message-Id: <679DB462-75D6-45CC-949C-1BE8E12C22CD@stromnet.se> From: =?ISO-8859-1?Q?Johan_Str=F6m?= To: Alex Trull In-Reply-To: <1211037564.6326.27.camel@porksoda> Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Apple Message framework v919.2) Date: Sat, 17 May 2008 18:01:10 +0200 References: <678A03F5-5E8A-4CF6-90DF-AA9A4F30FBE1@stromnet.se> <1211037564.6326.27.camel@porksoda> X-Mailer: Apple Mail (2.919.2) Cc: freebsd-net@freebsd.org, freebsd-stable , freebsd-pf@freebsd.org Subject: Re: connect(): Operation not permitted X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 May 2008 16:01:19 -0000 First of all, for freebsd-pf subscribers, I posted my original problem =20= (in the bottom) to freebsd-net earlier, but replies seems to point to =20= PF so I'll CC there too.. On May 17, 2008, at 5:19 PM, Alex Trull wrote: > Hi Johan and List, > > In my case a few months ago it was pahu. Don't give that fine fellow =20= > an > account on your precious system ! > > > But seriously, I had a pf-firewalled jail being being used for DNS > testing, with large numbers of udp "connections" hanging around in pf > state. While the default udp timeout settings in PF are lower than =20 > those > of the tcp timeouts, it is was still too high for it to to remove the > states in time before hitting the default 10k state limit! > > If this is the case with you - run 'pfctl -s state | wc -l' - when =20 > there > is traffic load you may see that hitting 10k states if you've not =20 > tuned > that variable. > > What to do next - up the state limit or lower the state timeouts. I =20= > did > both, to be safe. > > in /etc/pf.conf these must be at the very top of the file: > > # options > # 10k is insanely low, lets raise it.. > set limit { frags 16384, states 32768 } > # timeouts - see 'pfctl -s timeouts' for options - you will want to > # change the tcp ones rather than the udp ones for your smtp setup. > # but these are mine, I set them for the dns traffic. > set timeout { udp.first 15, udp.single 5, udp.multiple 30 } > > > don't forget to: > > $ /etc/rc.d/pf check && /etc/rc.d/pf reload Ok, looked over the PF states now, but I'm not quite sure thats what =20 causing it. I have default limit on 10k states, normally I seem to =20 have around ~800 states, and when I start my test script that tries to =20= send as many mails as possible (using PHP's Pear::Mail, creating a =20 connection, sending, disconnecting, creating new connection.. and so =20 on), I can clearly see the PF state counter (pfctl -vsi) increase, but =20= the script aborts with Operation not permitted way before I hit 10k, =20 its rather around 3-4k.. If I then wait a few seconds and run the script again, I can see the =20 number of states increase even more, and if I do this enough times I =20 finally hit around 9700 states. But at this point (states exhausted), =20= I don't get Operation not permitted, instead it just seems that the =20 script blocks up a few seconds while states clear up, then continues =20 running until it gets a Operation not permitted. So, from the above results, I cant say that it looks like its the =20 states? Just tried to disable the altq rule now too, no changes (not that I =20 expected one, since its on bce0 not lo0). Another thing, which might be more approriate in freebsd-pf though.. =20 Why would it create states at all for this traffic, when my pf.conf =20 rule is "pass on lo0 inet from $jail to $jail" (i have a block drop in =20= rule to drop all traffic)? A check with pfctl -vsr reveals that the =20 actual rule inserted is "pass on lo0 inet from 123.123.123.123 to =20 123.123.123.123 flags S/SA keep state". Where did that "keep state" =20 come from? Thanks for ideas :) > > > HTH, > > Alex > > On Sat, 2008-05-17 at 16:33 +0200, Johan Str=F6m wrote: >> Hello >> >> I got a FreeBSD 7 machine running mail services (among other things). >> This machine recently replaced a FreeBSD 6.2 machine doing the same >> tasks. >> Now and then I need to send alot of mail to customers (mailing list), >> and one thing i've noticed now after the change is that when I use a >> lot of connections subsequently (high connection rate, even if they >> are very shortlived) inside a jail (dunno if that has anything to do >> with it though), I start to get Operation not permitted in return to >> connect(). >> I've seen this in the PHP app that sends mail, when it tried to >> connect to localhost, as well as from postfix when it have been =20 >> trying >> to connect to amavisd on localhost, but also from postfix when it has >> tried to connect to remote SMTP servers. >> >> I do have PF for filtering, but there are no max-src-conn-rate limits >> enabled for any rules that is used for this. However, from one of the >> jail I do have a hfsc queue limiting the outgoing mail traffic from >> one jailed IP. But I'm not sure that this would be the problem, since >> I've also seen the problem when doing localhost connects in the jail, >> and also in other jails on an entierly different IP that is not >> affected. >> >> Does anyone have any clues about what I can look at and tune to fix >> this? >> >> Thanks! >> >> -- >> Johan Str=F6m >> Stromnet >> johan@stromnet.se >> http://www.stromnet.se/ >> >> >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org=20 >> " From owner-freebsd-stable@FreeBSD.ORG Sat May 17 19:18:19 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 834AF106564A for ; Sat, 17 May 2008 19:18:19 +0000 (UTC) (envelope-from fbsd-ml@scrapper.ca) Received: from pd2mo2so.prod.shaw.ca (idcmail-mo1so.shaw.ca [24.71.223.10]) by mx1.freebsd.org (Postfix) with ESMTP id 598888FC13 for ; Sat, 17 May 2008 19:18:19 +0000 (UTC) (envelope-from fbsd-ml@scrapper.ca) Received: from pd2mr6so.prod.shaw.ca (pd2mr6so-qfe3.prod.shaw.ca [10.0.141.9]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0K1000LZKYUJC880@l-daemon> for freebsd-stable@freebsd.org; Sat, 17 May 2008 12:18:19 -0600 (MDT) Received: from pn2ml4so.prod.shaw.ca ([10.0.121.148]) by pd2mr6so.prod.shaw.ca (Sun Java System Messaging Server 6.2-7.05 (built Sep 5 2006)) with ESMTP id <0K1000G2FYUHF280@pd2mr6so.prod.shaw.ca> for freebsd-stable@freebsd.org; Sat, 17 May 2008 12:18:19 -0600 (MDT) Received: from proven.lan ([24.85.241.34]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0K1000ESXYUHJ200@l-daemon> for freebsd-stable@freebsd.org; Sat, 17 May 2008 12:18:17 -0600 (MDT) Received: from proven.lan (localhost [127.0.0.1]) by proven.lan (8.14.2/8.14.2) with ESMTP id m4HIIGSO046203 for ; Sat, 17 May 2008 11:18:16 -0700 (PDT envelope-from fbsd-ml@scrapper.ca) Received: from localhost (localhost [[UNIX: localhost]]) by proven.lan (8.14.2/8.14.2/Submit) id m4HIIGuG046202 for freebsd-stable@freebsd.org; Sat, 17 May 2008 11:18:16 -0700 (PDT envelope-from fbsd-ml@scrapper.ca) Date: Sat, 17 May 2008 11:18:16 -0700 From: Norbert Papke To: freebsd-stable@freebsd.org Message-id: <200805171118.16482.fbsd-ml@scrapper.ca> Organization: Archaeological Filing MIME-version: 1.0 Content-type: text/plain; charset=utf-8 Content-transfer-encoding: 7bit Content-disposition: inline X-Authentication-warning: proven.lan: npapke set sender to fbsd-ml@scrapper.ca using -f User-Agent: KMail/1.9.7 Subject: Apache seg faults -- Possible problem with libc? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 May 2008 19:18:19 -0000 Environment: FreeBSD 7.0 Stable (as of Apr 30), apache-2.0.63 I am experiencing Apache crashes on a fairly consistent and frequent basis. The crash occurs in strncmp(). To help with the diagnosis, I have rebuilt libc with debug symbols. Here is a typical stack dump: #0 strncmp () at /usr/src/lib/libc/i386/string/strncmp.S:69 #1 0x2832558c in getenv (name=0x28338648 "TZ") at /usr/src/lib/libc/stdlib/getenv.c:144 #2 0x2830ce3a in tzset_basic (rdlocked=0) at /usr/src/lib/libc/stdtime/localtime.c:1013 #3 0x2830d42f in localtime (timep=0xbfbfc1d4) at /usr/src/lib/libc/stdtime/localtime.c:1158 #4 0x28220e6c in explode_time () from /usr/local/lib/apache2/libapr-0.so.9 #5 0x28220f13 in apr_time_exp_lt () from /usr/local/lib/apache2/libapr-0.so.9 #6 0x08070227 in cached_explode () #7 0x28374519 in log_request_time () from /usr/local/libexec/apache2/mod_log_config.so #8 0x2837358d in config_log_transaction () from /usr/local/libexec/apache2/mod_log_config.so #9 0x28373654 in multi_log_transaction () from /usr/local/libexec/apache2/mod_log_config.so #10 0x08074519 in ap_run_log_transaction () #11 0x08063d62 in ap_process_request () #12 0x0805e718 in ap_process_http_connection () #13 0x08070817 in ap_run_process_connection () #14 0x08064fde in child_main () #15 0x08065283 in make_child () #16 0x08065a51 in ap_mpm_run () #17 0x0806bfb8 in main () Frames 0 - 4 are present in all crash scenarios. However, similar crashes occur with different paths into explode_time(). (gdb) frame 0 #0 strncmp () at /usr/src/lib/libc/i386/string/strncmp.S:69 69 movb (%eax),%bl (gdb) p/x $eax $70 = 0x883a4bc (gdb) p/x *$eax Cannot access memory at address 0x883a4bc eax contains the first string to be compared. This is an invalid memory location. (gdb) frame 1 #1 0x2832558c in getenv (name=0x28338648 "TZ") at /usr/src/lib/libc/stdlib/getenv.c:144 144 if (strncmp(nameValue, name, nameLen) == 0 && nameValue[nameLen] == '=') Current language: auto; currently c (gdb) p envVarsTotal $71 = 57 (gdb) p envVars[56] $72 = {nameLen = 4294967295, valueSize = 4294967295, name = 0x883a4bc
, value = 0x0, active = true, putenv = true} (gdb) p envVars[55] $73 = {nameLen = 16, valueSize = 4, name = 0x8303f20 "KDE_FULL_SESSION=true", value = 0x8303f31 "true", active = true, putenv = false} Because of the inline functions used in getenv(), gdb's location information is somewhat incomplete. However, I believe that line 144 was called by __findenv(), The fault occurs when __findenv() tries to access what appears to be an invalid environment variable. Most likely, envVarsTotal is too big by one. For reference, here is the code for __findenv(). The calling line is marked. static inline char * __findenv(const char *name, size_t nameLen, int *envNdx, bool onlyActive) { int ndx; /* * Find environment variable from end of array (more likely to be * active). A variable created by putenv is always active or it is not * tracked in the array. */ for (ndx = *envNdx; ndx >= 0; ndx--) if (envVars[ndx].putenv) { /* ==> */ if (strncmpeq(envVars[ndx].name, name, nameLen)) { *envNdx = ndx; return (envVars[ndx].name + nameLen + sizeof ("=") - 1); } } else if ((!onlyActive || envVars[ndx].active) && (envVars[ndx].nameLen == nameLen && strncmpeq(envVars[ndx].name, name, nameLen))) { *envNdx = ndx; return (envVars[ndx].value); } return (NULL); } which is called by char * getenv(const char *name) { int envNdx; size_t nameLen; /* Check for malformed name. */ if (name == NULL || (nameLen = __strleneq(name)) == 0) { errno = EINVAL; return (NULL); } /* * Find environment variable via environ if no changes have been made * via a *env() call or environ has been replaced by a running program, * otherwise, use the rebuilt environment. */ if (envVars == NULL || environ != intEnviron) return (__findenv_environ(name, nameLen)); else { envNdx = envVarsTotal - 1; /* ==> */ return (__findenv(name, nameLen, &envNdx, true)); } } Any suggestions on how I could nail down the cause? Cheers, -- Norbert.