From owner-freebsd-stable@FreeBSD.ORG Sun Apr 24 16:39:11 2011 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 84C411065670 for ; Sun, 24 Apr 2011 16:39:11 +0000 (UTC) (envelope-from freebsd@chillt.de) Received: from dd16434.kasserver.com (dd16434.kasserver.com [85.13.137.111]) by mx1.freebsd.org (Postfix) with ESMTP id 481528FC0C for ; Sun, 24 Apr 2011 16:39:11 +0000 (UTC) Received: from taiko.lan (ppp-94-44.21-151.libero.it [151.21.44.94]) by dd16434.kasserver.com (Postfix) with ESMTPSA id 76BE4188603F; Sun, 24 Apr 2011 18:20:11 +0200 (CEST) Message-ID: <4DB44DA3.5060509@chillt.de> Date: Sun, 24 Apr 2011 18:19:47 +0200 From: Bartosz Fabianowski User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110309 Thunderbird/3.1.9 MIME-Version: 1.0 To: "illoai@gmail.com" References: <4DA596D3.1090803@chillt.de> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Ronald Klop Subject: Re: System extremely slow under light load 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, 24 Apr 2011 16:39:11 -0000 >> Just for an experiment, try to disable powerd and look if things improve. > > Or just bump it to "maximum", temporarily. I have tried both now. The results are as follows: * With powerd disabled and the CPU clocked down, the computer is responsive when almost nothing is going on but becomes very slow as soon as there is a light load. This is identical to the behavior I am seeing with powerd enabled and a reduced maximum frequency. * With powerd disabled and the CPU clocked to its full speed, the computer is running much hotter but responsiveness is not improved. It appears that powerd is not at fault. Something else is making this computer run unbelievably slow. My Atom netbook regularly outperforms this Core i7 when building ports. This just cannot be right :(. - Bartosz From owner-freebsd-stable@FreeBSD.ORG Sun Apr 24 17:23:49 2011 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 0CDFA106564A for ; Sun, 24 Apr 2011 17:23:49 +0000 (UTC) (envelope-from amarat@ksu.ru) Received: from webmail.hitv.ru (mail.hitv.ru [217.66.16.37]) by mx1.freebsd.org (Postfix) with ESMTP id 753118FC08 for ; Sun, 24 Apr 2011 17:23:48 +0000 (UTC) Received: from webmail.hitv.ru (localhost [127.0.0.1]) by webmail.hitv.ru (Postfix) with ESMTP id A74664AC5BC; Sun, 24 Apr 2011 21:06:28 +0400 (MSD) Received: from zealot.ksu.ru (zealot.hitv.ru [83.151.8.230]) by webmail.hitv.ru (Postfix) with ESMTP id 851A84AC59E; Sun, 24 Apr 2011 21:06:28 +0400 (MSD) Received: from zealot.ksu.ru (localhost.lnet [127.0.0.1]) by zealot.ksu.ru (8.14.4/8.14.4) with ESMTP id p3OH6ZN0064219; Sun, 24 Apr 2011 21:06:35 +0400 (MSD) (envelope-from amarat@ksu.ru) Message-ID: <4DB4589B.2020909@ksu.ru> Date: Sun, 24 Apr 2011 21:06:35 +0400 From: "Marat N.Afanasyev" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:2.0pre) Gecko/20110423 Firefox/4.0pre SeaMonkey/2.1b3pre MIME-Version: 1.0 To: Bartosz Fabianowski References: <4DA596D3.1090803@chillt.de> <4DB44DA3.5060509@chillt.de> In-Reply-To: <4DB44DA3.5060509@chillt.de> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-stable@freebsd.org, "illoai@gmail.com" , Ronald Klop Subject: Re: System extremely slow under light load 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, 24 Apr 2011 17:23:49 -0000 Bartosz Fabianowski wrote: >>> Just for an experiment, try to disable powerd and look if things >>> improve. >> >> Or just bump it to "maximum", temporarily. > > I have tried both now. The results are as follows: > > * With powerd disabled and the CPU clocked down, the computer is > responsive when almost nothing is going on but becomes very slow as soon > as there is a light load. This is identical to the behavior I am seeing > with powerd enabled and a reduced maximum frequency. > > * With powerd disabled and the CPU clocked to its full speed, the > computer is running much hotter but responsiveness is not improved. > > It appears that powerd is not at fault. Something else is making this > computer run unbelievably slow. My Atom netbook regularly outperforms > this Core i7 when building ports. This just cannot be right :(. > > - Bartosz > _______________________________________________ > 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" > did you test the caches? I've seen such a behavior when cpu cache was disabled. and it can be thermal throttle in case of bad contact between cpu and heatsink. try to reapply thermal compound -- SY, Marat From owner-freebsd-stable@FreeBSD.ORG Sun Apr 24 17:27:34 2011 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 5747A1065672 for ; Sun, 24 Apr 2011 17:27:34 +0000 (UTC) (envelope-from freebsd@chillt.de) Received: from dd16434.kasserver.com (dd16434.kasserver.com [85.13.137.111]) by mx1.freebsd.org (Postfix) with ESMTP id 178EA8FC08 for ; Sun, 24 Apr 2011 17:27:33 +0000 (UTC) Received: from taiko.lan (ppp-94-44.21-151.libero.it [151.21.44.94]) by dd16434.kasserver.com (Postfix) with ESMTPSA id D8ED2188603F; Sun, 24 Apr 2011 19:27:32 +0200 (CEST) Message-ID: <4DB45D6C.20203@chillt.de> Date: Sun, 24 Apr 2011 19:27:08 +0200 From: Bartosz Fabianowski User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110309 Thunderbird/3.1.9 MIME-Version: 1.0 To: "Marat N.Afanasyev" References: <4DA596D3.1090803@chillt.de> <4DB44DA3.5060509@chillt.de> <4DB4589B.2020909@ksu.ru> In-Reply-To: <4DB4589B.2020909@ksu.ru> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-stable@freebsd.org, "illoai@gmail.com" , Ronald Klop Subject: Re: System extremely slow under light load 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, 24 Apr 2011 17:27:34 -0000 > did you test the caches? I've seen such a behavior when cpu cache was > disabled. The Dell BIOS setup is very minimalistic and would not even allow me to turn off caches. So unless the FreeBSD boot loader somehow turned them off, the caches should be active. Is there some tool I can use to verify my caches are active? > and it can be thermal throttle in case of bad contact between > cpu and heatsink. try to reapply thermal compound The CPU temperature is about 60°C-70°C when idle, 80°-90°C under light load and exceeds 90°C under heavy load. All of these readings are obtained from sysctl dev.cpu as ACPI always reports a temperature of 0°C. If I fix the DSDT to correctly report temperatures, a medium to heavy load forces an emergency shutdown. To prevent this, I am running with the original broken DSDT and the CPU throttled from 1.8GHz to 1.3GHz where it never exceeds 90°C. Yes, the CPU is very warm. But it does not appear to be critically hot. The ACPI critical threshold is 95°C. It seems that this model (Dell Studio 15) always runs that hot. I have had several visits from a Dell technician who changed everything from heat pipe to complete motherboard. The temperatures never changed. Dell finally exchanged the entire laptop for a slightly newer model but the temperatures remained as they were. So reapplying thermal grease or even swapping components does not seem to change anything. Again, a tool would be useful that can tell me whether the CPU is throttling itself. Does such a thing exist? - Bartosz From owner-freebsd-stable@FreeBSD.ORG Sun Apr 24 17:52:01 2011 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 333021065670; Sun, 24 Apr 2011 17:52:01 +0000 (UTC) (envelope-from dnaeon@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id AD0448FC17; Sun, 24 Apr 2011 17:52:00 +0000 (UTC) Received: by vxc34 with SMTP id 34so1896814vxc.13 for ; Sun, 24 Apr 2011 10:51:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=kVlSMsOvsphl4b/zsR0mGX7ryWe3AGRTD8GAeh5jeTA=; b=oJjgUEwtlG+hcx/mddZALYZUCHBRpigpDyO3S/RKDJvPb18FkVHth3Dz6jrQu4DLd9 eDp5CGyYGF4CEY92MUtCx01JIovlOoxJ/YXOjvx1qgVmGwSIv+0S1E61l1M7wIZWo1Ys y7UUcVLGxhD+RUO01+qoo5JKYqvxyugeDbw/g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=hFRqtengf0nbdmnEphpi5f0ADMG4QYVPAsWYIzQFuhnLdBlOFsLqKARzBG4eWSdfL1 p3f3m2Qd0hWpfnc6bfqxue6G6BXXFpAtokeWW4hRyEV1SNW3isZon4InAmVJlK8J8y+A BTI/Tiumo7z5FR/ZhW+NXD3uCI7eiytOs7SaY= MIME-Version: 1.0 Received: by 10.52.98.39 with SMTP id ef7mr60342vdb.145.1303665779282; Sun, 24 Apr 2011 10:22:59 -0700 (PDT) Received: by 10.52.160.226 with HTTP; Sun, 24 Apr 2011 10:22:59 -0700 (PDT) Date: Sun, 24 Apr 2011 20:22:59 +0300 Message-ID: From: Marin Atanasov Nikolov To: freebsd-ports@freebsd.org, ml-freebsd-stable , freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: Subject: Configuration Management with Cfengine 3 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, 24 Apr 2011 17:52:01 -0000 Hello, Recently I've been working on automating my FreeBSD systems, as much as possible and the viable solution was to try out Cfengine 3. Currently I'm running most of my hosts and jails under Cfengine 3 control, and wanted to share this you, because I think some might find it useful. Therefore I've created a little documentation that explains how to setup Cfengine 3 on your systems and use it for managing your hosts and jails - starting from simple configuration deployments and daemon processes control, and package management with Cfengine 3. Anyway the document can be found here: - http://unix-heaven.org/node/50 Hope you find it useful. Regards, Marin -- Marin Atanasov Nikolov dnaeon AT gmail DOT com daemon AT unix-heaven DOT org http://www.unix-heaven.org/ From owner-freebsd-stable@FreeBSD.ORG Sun Apr 24 18:41:51 2011 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 0A7B6106564A for ; Sun, 24 Apr 2011 18:41:51 +0000 (UTC) (envelope-from freebsd@chillt.de) Received: from dd16434.kasserver.com (dd16434.kasserver.com [85.13.137.111]) by mx1.freebsd.org (Postfix) with ESMTP id C091F8FC12 for ; Sun, 24 Apr 2011 18:41:50 +0000 (UTC) Received: from taiko.lan (ppp-94-44.21-151.libero.it [151.21.44.94]) by dd16434.kasserver.com (Postfix) with ESMTPSA id 9CBE6188603F; Sun, 24 Apr 2011 20:41:48 +0200 (CEST) Message-ID: <4DB46ED4.2010500@chillt.de> Date: Sun, 24 Apr 2011 20:41:24 +0200 From: Bartosz Fabianowski User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110309 Thunderbird/3.1.9 MIME-Version: 1.0 To: John References: <4DA596D3.1090803@chillt.de> <4DB44DA3.5060509@chillt.de> <4DB4589B.2020909@ksu.ru> <4DB45D6C.20203@chillt.de> <20110424182456.9DD03589@server.theusgroup.com> In-Reply-To: <20110424182456.9DD03589@server.theusgroup.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-stable@freebsd.org Subject: Re: System extremely slow under light load 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, 24 Apr 2011 18:41:51 -0000 > I don't know which i7 you have, but the intel datasheet for the i7-870 states > that the maximum case temperature is 72.7C. I have a Core i7 Q740 with a native speed of 1.73GHz. My previous Dell had a Q730. Both were exhibiting the same problems. Since this is a laptop, I would expect temperatures to be higher than in a desktop box. So up to 50-60°C CPU temperature while idling and 90°C under load may be acceptable. But the behavior the computer is exhibiting definitely is not acceptable. - Bartosz From owner-freebsd-stable@FreeBSD.ORG Sun Apr 24 19:40:19 2011 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 46A7A1065670 for ; Sun, 24 Apr 2011 19:40:19 +0000 (UTC) (envelope-from john@theusgroup.com) Received: from theusgroup.com (theusgroup.com [64.122.243.222]) by mx1.freebsd.org (Postfix) with ESMTP id 1A0BC8FC17 for ; Sun, 24 Apr 2011 19:40:18 +0000 (UTC) To: Bartosz Fabianowski In-reply-to: <4DB45D6C.20203@chillt.de> References: <4DA596D3.1090803@chillt.de> <4DB44DA3.5060509@chillt.de> <4DB4589B.2020909@ksu.ru> <4DB45D6C.20203@chillt.de> Comments: In-reply-to Bartosz Fabianowski message dated "Sun, 24 Apr 2011 19:27:08 +0200." Date: Sun, 24 Apr 2011 11:24:56 -0700 From: John Message-Id: <20110424182456.9DD03589@server.theusgroup.com> Cc: freebsd-stable@freebsd.org Subject: Re: System extremely slow under light load 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, 24 Apr 2011 19:40:19 -0000 >The CPU temperature is about 60°C-70°C when idle, 80°-90°C under light >load and exceeds 90°C under heavy load. All of these readings are >obtained from sysctl dev.cpu > >Yes, the CPU is very warm. But it does not appear to be critically hot. >The ACPI critical threshold is 95°C. It seems that this model (Dell >Studio 15) always runs that hot. I don't know which i7 you have, but the intel datasheet for the i7-870 states that the maximum case temperature is 72.7C. The reported cpu temperatures will be a little higher at this case temperature, maybe a few degrees. How much higher I can't say without knowing the thermal resistance. The i7-870 motherboard I have with a large cooler idles at about 40C. Under heavy load it runs at about 65C. John Theus From owner-freebsd-stable@FreeBSD.ORG Sun Apr 24 22:52:41 2011 Return-Path: Delivered-To: stable@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 8A6A41065672 for ; Sun, 24 Apr 2011 22:52:41 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 65-241-43-5.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 6A79C150536; Sun, 24 Apr 2011 22:52:41 +0000 (UTC) Message-ID: <4DB4A9B9.4060101@FreeBSD.org> Date: Sun, 24 Apr 2011 15:52:41 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110319 Thunderbird/3.1.9 MIME-Version: 1.0 To: "Simon L. B. Nielsen" References: <50FB1524-4717-468A-8F8C-FD0586A36C68@nitro.dk> In-Reply-To: <50FB1524-4717-468A-8F8C-FD0586A36C68@nitro.dk> X-Enigmail-Version: 1.1.2 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org Subject: Re: svn.FreeBSD.org upgrade 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, 24 Apr 2011 22:52:41 -0000 This seems to have gone well, and the new viewvc seems faster (which fortunately wasn't hard). :) I did notice one problem, I didn't see a commit e-mail for r220972, which was a commit you did to add a user directory: http://svnweb.freebsd.org/base?view=revision&revision=220972 It's happened in the past that certain changes haven't resulted in commit mail, but given that this happened so close to the update I thought I'd mention it. Doug From owner-freebsd-stable@FreeBSD.ORG Mon Apr 25 00:48:22 2011 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 5D2E8106566C for ; Mon, 25 Apr 2011 00:48:22 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta12.westchester.pa.mail.comcast.net (qmta12.westchester.pa.mail.comcast.net [76.96.59.227]) by mx1.freebsd.org (Postfix) with ESMTP id 8887B8FC14 for ; Mon, 25 Apr 2011 00:48:21 +0000 (UTC) Received: from omta22.westchester.pa.mail.comcast.net ([76.96.62.73]) by qmta12.westchester.pa.mail.comcast.net with comcast id bcav1g0021ap0As5CcoMhC; Mon, 25 Apr 2011 00:48:21 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta22.westchester.pa.mail.comcast.net with comcast id bcoK1g01M1t3BNj3icoLx7; Mon, 25 Apr 2011 00:48:21 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 7A4A49B418; Sun, 24 Apr 2011 17:48:18 -0700 (PDT) Date: Sun, 24 Apr 2011 17:48:18 -0700 From: Jeremy Chadwick To: Bartosz Fabianowski Message-ID: <20110425004818.GA22579@icarus.home.lan> References: <4DA596D3.1090803@chillt.de> <4DB44DA3.5060509@chillt.de> <4DB4589B.2020909@ksu.ru> <4DB45D6C.20203@chillt.de> <20110424182456.9DD03589@server.theusgroup.com> <4DB46ED4.2010500@chillt.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4DB46ED4.2010500@chillt.de> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@freebsd.org, John Subject: Re: System extremely slow under light load 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, 25 Apr 2011 00:48:22 -0000 On Sun, Apr 24, 2011 at 08:41:24PM +0200, Bartosz Fabianowski wrote: > >I don't know which i7 you have, but the intel datasheet for the i7-870 states > >that the maximum case temperature is 72.7C. > > I have a Core i7 Q740 with a native speed of 1.73GHz. My previous > Dell had a Q730. Both were exhibiting the same problems. > > Since this is a laptop, I would expect temperatures to be higher > than in a desktop box. So up to 50-60??C CPU temperature while > idling and 90??C under load may be acceptable. But the behavior the > computer is exhibiting definitely is not acceptable. The temperatures you reported in your earlier post: http://lists.freebsd.org/pipermail/freebsd-stable/2011-April/062377.html Are not normal, nor are they acceptable, even for a laptop. Desktop i7 boxes tend to run around 45C idle, 60-65C load with stock cooling. Laptops should be higher, but not 60-65C idle with 90C under load. Others have already stated what the thermal cut-off point is. As the processor gets hotter, internal clocks and so on are throttled within the hardware to try and stabilise the temperature (to keep the thermal trip point being reached, re: "emergency shutdown"), which greatly decreases performance. I'm not sure if there's a way to detect this, but I would hope (?) that it would be visible via the CPU clock frequency (on FreeBSD this would be sysctl dev.cpu.X.freq). If you were running Windows there would be a multitude of tools you could check to confirm this behaviour (Core Temp, CPU-Z, RMClock, etc.). If you boot into another operating system such as Linux or Windows, do you see the same overall behaviour? Linux might be easier and might have some built-in way to get at CPU temperatures (via /proc?). Trying to figure out if this is a FreeBSD issue or not is difficult. Can you please provide: - Contents of rc.conf - sysctl -a hw.acpi - sysctl -a dev.cpu - sysctl -a dev.est - sysctl -a dev.cpufreq - sysctl -a kern.timecounter Finally, just as a data point -- and this should be honoured no matter what -- there have been cases where manufacturers have incorrectly been applying thermal grease (if used rather than a TIM pad): http://gizmodo.com/#!171394/thermal-greasy-apple-sics-lawyers-on-something-awful So don't think necessarily that just because Dell replaced the entire laptop that the next one wouldn't behave the same way. This is why I recommend trying out another OS to see if it exhibits the problem. -- | Jeremy Chadwick jdc@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 Apr 25 07:14:11 2011 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 6C421106566B for ; Mon, 25 Apr 2011 07:14:11 +0000 (UTC) (envelope-from freebsd@chillt.de) Received: from dd16434.kasserver.com (dd16434.kasserver.com [85.13.137.111]) by mx1.freebsd.org (Postfix) with ESMTP id DA2808FC08 for ; Mon, 25 Apr 2011 07:14:10 +0000 (UTC) Received: from taiko.lan (ppp-94-44.21-151.libero.it [151.21.44.94]) by dd16434.kasserver.com (Postfix) with ESMTPSA id 6432F188603F; Mon, 25 Apr 2011 09:14:08 +0200 (CEST) Message-ID: <4DB51F27.5010508@chillt.de> Date: Mon, 25 Apr 2011 09:13:43 +0200 From: Bartosz Fabianowski User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110309 Thunderbird/3.1.9 MIME-Version: 1.0 To: Jeremy Chadwick References: <4DA596D3.1090803@chillt.de> <4DB44DA3.5060509@chillt.de> <4DB4589B.2020909@ksu.ru> <4DB45D6C.20203@chillt.de> <20110424182456.9DD03589@server.theusgroup.com> <4DB46ED4.2010500@chillt.de> <20110425004818.GA22579@icarus.home.lan> In-Reply-To: <20110425004818.GA22579@icarus.home.lan> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, John Subject: Re: System extremely slow under light load 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, 25 Apr 2011 07:14:11 -0000 > As the processor gets hotter, internal clocks and so on are throttled > within the hardware to try and stabilise the temperature (to keep the > thermal trip point being reached, re: "emergency shutdown"), which > greatly decreases performance. I'm not sure if there's a way to > detect this, but I would hope (?) that it would be visible via the > CPU clock frequency (on FreeBSD this would be sysctl > dev.cpu.X.freq). sysctl dev.cpu.X.freq is used to set the frequency. I have not found any way to read back its internal state so far. > If you boot into another operating system such as Linux or Windows, > do you see the same overall behaviour? Linux might be easier and > might have some built-in way to get at CPU temperatures (via > /proc?). I will download a Linux ISO and give it a try. The machine currently has FreeBSD and nothing else installed on it. > Trying to figure out if this is a FreeBSD issue or not is difficult. > Can you please provide: > > - Contents of rc.conf # Console keymap="german.iso" # Set German keyboard map # Network hostname="taiko.lan" # Set hostname to taiko.lan ifconfig_re0="DHCP" # Configure wired Ethernet via DHCP # Daemons powerd_enable="YES" # Run powerd to lower our power usage sshd_enable="YES" # Run the SSH daemon moused_enable="YES" # Run the mouse daemon dbus_enable="YES" # Run the D-Bus daemon hald_enable="YES" # Run the HAL daemon webcamd_enable="YES" # Run the webcam daemon cupsd_enable="YES" # Run the CUPS printer daemon # Miscellaneous clear_tmp_enable="YES" # Clear /tmp at startup devfs_system_ruleset="local" # Apply the "local" ruleset to /dev # PostgreSQL postgres_enable="YES" # Run the PostgreSQL server > - sysctl -a hw.acpi hw.acpi.supported_sleep_state: S3 S4 S5 hw.acpi.power_button_state: S5 hw.acpi.sleep_button_state: S3 hw.acpi.lid_switch_state: NONE hw.acpi.standby_state: NONE hw.acpi.suspend_state: S3 hw.acpi.sleep_delay: 1 hw.acpi.s4bios: 0 hw.acpi.verbose: 0 hw.acpi.disable_on_reboot: 0 hw.acpi.handle_reboot: 0 hw.acpi.reset_video: 0 hw.acpi.cpu.cx_lowest: C1 hw.acpi.acline: 1 hw.acpi.battery.life: -1 hw.acpi.battery.time: -1 hw.acpi.battery.state: 7 hw.acpi.battery.units: 1 hw.acpi.battery.info_expire: 5 hw.acpi.thermal.min_runtime: 0 hw.acpi.thermal.polling_rate: 10 hw.acpi.thermal.user_override: 0 hw.acpi.thermal.tz0.temperature: 26.8C hw.acpi.thermal.tz0.active: -1 hw.acpi.thermal.tz0.passive_cooling: 0 hw.acpi.thermal.tz0.thermal_flags: 0 hw.acpi.thermal.tz0._PSV: -1 hw.acpi.thermal.tz0._HOT: -1 hw.acpi.thermal.tz0._CRT: 100.0C hw.acpi.thermal.tz0._ACx: 71.0C 55.0C -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.thermal.tz0._TC1: -1 hw.acpi.thermal.tz0._TC2: -1 hw.acpi.thermal.tz0._TSP: -1 hw.acpi.thermal.tz1.temperature: 0.0C hw.acpi.thermal.tz1.active: -1 hw.acpi.thermal.tz1.passive_cooling: 1 hw.acpi.thermal.tz1.thermal_flags: 0 hw.acpi.thermal.tz1._PSV: 95.0C hw.acpi.thermal.tz1._HOT: -1 hw.acpi.thermal.tz1._CRT: 100.0C hw.acpi.thermal.tz1._ACx: 71.0C 55.0C -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.thermal.tz1._TC1: 0 hw.acpi.thermal.tz1._TC2: 2 hw.acpi.thermal.tz1._TSP: 10 > - sysctl -a dev.cpu dev.cpu.0.%desc: ACPI CPU dev.cpu.0.%driver: cpu dev.cpu.0.%location: handle=\_PR_.CPU0 dev.cpu.0.%pnpinfo: _HID=none _UID=0 dev.cpu.0.%parent: acpi0 dev.cpu.0.temperature: 82.0C dev.cpu.0.freq: 1333 dev.cpu.0.freq_levels: 1734/45000 1599/41741 1466/38582 1333/35485 1199/32426 1066/29457 933/26552 816/23233 699/19914 583/16595 466/13276 349/9957 233/6638 116/3319 dev.cpu.0.cx_supported: C1/3 C2/245 dev.cpu.0.cx_lowest: C1 dev.cpu.0.cx_usage: 100.00% 0.00% last 285us dev.cpu.1.%desc: ACPI CPU dev.cpu.1.%driver: cpu dev.cpu.1.%location: handle=\_PR_.CPU1 dev.cpu.1.%pnpinfo: _HID=none _UID=0 dev.cpu.1.%parent: acpi0 dev.cpu.1.temperature: 82.0C dev.cpu.1.cx_supported: C1/3 C2/245 dev.cpu.1.cx_lowest: C1 dev.cpu.1.cx_usage: 100.00% 0.00% last 383us dev.cpu.2.%desc: ACPI CPU dev.cpu.2.%driver: cpu dev.cpu.2.%location: handle=\_PR_.CPU2 dev.cpu.2.%pnpinfo: _HID=none _UID=0 dev.cpu.2.%parent: acpi0 dev.cpu.2.temperature: 82.0C dev.cpu.2.cx_supported: C1/3 C2/245 dev.cpu.2.cx_lowest: C1 dev.cpu.2.cx_usage: 100.00% 0.00% last 238us dev.cpu.3.%desc: ACPI CPU dev.cpu.3.%driver: cpu dev.cpu.3.%location: handle=\_PR_.CPU3 dev.cpu.3.%pnpinfo: _HID=none _UID=0 dev.cpu.3.%parent: acpi0 dev.cpu.3.temperature: 82.0C dev.cpu.3.cx_supported: C1/3 C2/245 dev.cpu.3.cx_lowest: C1 dev.cpu.3.cx_usage: 100.00% 0.00% last 187us dev.cpu.4.%desc: ACPI CPU dev.cpu.4.%driver: cpu dev.cpu.4.%location: handle=\_PR_.CPU4 dev.cpu.4.%pnpinfo: _HID=none _UID=0 dev.cpu.4.%parent: acpi0 dev.cpu.4.temperature: 82.0C dev.cpu.4.cx_supported: C1/3 C2/245 dev.cpu.4.cx_lowest: C1 dev.cpu.4.cx_usage: 100.00% 0.00% last 426us dev.cpu.5.%desc: ACPI CPU dev.cpu.5.%driver: cpu dev.cpu.5.%location: handle=\_PR_.CPU5 dev.cpu.5.%pnpinfo: _HID=none _UID=0 dev.cpu.5.%parent: acpi0 dev.cpu.5.temperature: 82.0C dev.cpu.5.cx_supported: C1/3 C2/245 dev.cpu.5.cx_lowest: C1 dev.cpu.5.cx_usage: 100.00% 0.00% last 439us dev.cpu.6.%desc: ACPI CPU dev.cpu.6.%driver: cpu dev.cpu.6.%location: handle=\_PR_.CPU6 dev.cpu.6.%pnpinfo: _HID=none _UID=0 dev.cpu.6.%parent: acpi0 dev.cpu.6.temperature: 82.0C dev.cpu.6.cx_supported: C1/3 C2/245 dev.cpu.6.cx_lowest: C1 dev.cpu.6.cx_usage: 100.00% 0.00% last 138us dev.cpu.7.%desc: ACPI CPU dev.cpu.7.%driver: cpu dev.cpu.7.%location: handle=\_PR_.CPU7 dev.cpu.7.%pnpinfo: _HID=none _UID=0 dev.cpu.7.%parent: acpi0 dev.cpu.7.temperature: 82.0C dev.cpu.7.cx_supported: C1/3 C2/245 dev.cpu.7.cx_lowest: C1 dev.cpu.7.cx_usage: 100.00% 0.00% last 434us > - sysctl -a dev.est dev.est.0.%desc: Enhanced SpeedStep Frequency Control dev.est.0.%driver: est dev.est.0.%parent: cpu0 dev.est.0.freq_settings: 1734/45000 1733/45000 1599/41741 1466/38582 1333/35485 1199/32426 1066/29457 933/26552 dev.est.1.%desc: Enhanced SpeedStep Frequency Control dev.est.1.%driver: est dev.est.1.%parent: cpu1 dev.est.1.freq_settings: 1734/45000 1733/45000 1599/41741 1466/38582 1333/35485 1199/32426 1066/29457 933/26552 dev.est.2.%desc: Enhanced SpeedStep Frequency Control dev.est.2.%driver: est dev.est.2.%parent: cpu2 dev.est.2.freq_settings: 1734/45000 1733/45000 1599/41741 1466/38582 1333/35485 1199/32426 1066/29457 933/26552 dev.est.3.%desc: Enhanced SpeedStep Frequency Control dev.est.3.%driver: est dev.est.3.%parent: cpu3 dev.est.3.freq_settings: 1734/45000 1733/45000 1599/41741 1466/38582 1333/35485 1199/32426 1066/29457 933/26552 dev.est.4.%desc: Enhanced SpeedStep Frequency Control dev.est.4.%driver: est dev.est.4.%parent: cpu4 dev.est.4.freq_settings: 1734/45000 1733/45000 1599/41741 1466/38582 1333/35485 1199/32426 1066/29457 933/26552 dev.est.5.%desc: Enhanced SpeedStep Frequency Control dev.est.5.%driver: est dev.est.5.%parent: cpu5 dev.est.5.freq_settings: 1734/45000 1733/45000 1599/41741 1466/38582 1333/35485 1199/32426 1066/29457 933/26552 dev.est.6.%desc: Enhanced SpeedStep Frequency Control dev.est.6.%driver: est dev.est.6.%parent: cpu6 dev.est.6.freq_settings: 1734/45000 1733/45000 1599/41741 1466/38582 1333/35485 1199/32426 1066/29457 933/26552 dev.est.7.%desc: Enhanced SpeedStep Frequency Control dev.est.7.%driver: est dev.est.7.%parent: cpu7 dev.est.7.freq_settings: 1734/45000 1733/45000 1599/41741 1466/38582 1333/35485 1199/32426 1066/29457 933/26552 > - sysctl -a dev.cpufreq dev.cpufreq.0.%driver: cpufreq dev.cpufreq.0.%parent: cpu0 dev.cpufreq.1.%driver: cpufreq dev.cpufreq.1.%parent: cpu1 dev.cpufreq.2.%driver: cpufreq dev.cpufreq.2.%parent: cpu2 dev.cpufreq.3.%driver: cpufreq dev.cpufreq.3.%parent: cpu3 dev.cpufreq.4.%driver: cpufreq dev.cpufreq.4.%parent: cpu4 dev.cpufreq.5.%driver: cpufreq dev.cpufreq.5.%parent: cpu5 dev.cpufreq.6.%driver: cpufreq dev.cpufreq.6.%parent: cpu6 dev.cpufreq.7.%driver: cpufreq dev.cpufreq.7.%parent: cpu7 > - sysctl -a kern.timecounter kern.timecounter.tick: 1 kern.timecounter.choice: TSC(-100) HPET(900) ACPI-safe(850) i8254(0) dummy(-1000000) kern.timecounter.hardware: HPET kern.timecounter.stepwarnings: 0 kern.timecounter.tc.i8254.mask: 65535 kern.timecounter.tc.i8254.counter: 56046 kern.timecounter.tc.i8254.frequency: 1193182 kern.timecounter.tc.i8254.quality: 0 kern.timecounter.tc.ACPI-safe.mask: 16777215 kern.timecounter.tc.ACPI-safe.counter: 11762669 kern.timecounter.tc.ACPI-safe.frequency: 3579545 kern.timecounter.tc.ACPI-safe.quality: 850 kern.timecounter.tc.HPET.mask: 4294967295 kern.timecounter.tc.HPET.counter: 4005351156 kern.timecounter.tc.HPET.frequency: 14318180 kern.timecounter.tc.HPET.quality: 900 kern.timecounter.tc.TSC.mask: 4294967295 kern.timecounter.tc.TSC.counter: 1320432496 kern.timecounter.tc.TSC.frequency: 1729007846 kern.timecounter.tc.TSC.quality: -100 kern.timecounter.smp_tsc: 0 kern.timecounter.invariant_tsc: 1 > Finally, just as a data point -- and this should be honoured no > matter what -- there have been cases where manufacturers have > incorrectly been applying thermal grease (if used rather than a TIM > pad) I watched the Dell technician during the various repairs. From what I remember, the CPU and GPU share a heat pipe and both have TIM pads. - Bartosz From owner-freebsd-stable@FreeBSD.ORG Mon Apr 25 10:26:56 2011 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 CC7F61065672 for ; Mon, 25 Apr 2011 10:26:56 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) by mx1.freebsd.org (Postfix) with ESMTP id 1E9158FC1A for ; Mon, 25 Apr 2011 10:26:55 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id p3PAQh6L078913; Mon, 25 Apr 2011 20:26:44 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Mon, 25 Apr 2011 20:26:42 +1000 (EST) From: Ian Smith To: Bartosz Fabianowski In-Reply-To: <4DB51F27.5010508@chillt.de> Message-ID: <20110425184728.C73992@sola.nimnet.asn.au> References: <4DA596D3.1090803@chillt.de> <4DB44DA3.5060509@chillt.de> <4DB4589B.2020909@ksu.ru> <4DB45D6C.20203@chillt.de> <20110424182456.9DD03589@server.theusgroup.com> <4DB46ED4.2010500@chillt.de> <20110425004818.GA22579@icarus.home.lan> <4DB51F27.5010508@chillt.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-stable@freebsd.org, John , Jeremy Chadwick Subject: Re: System extremely slow under light load 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, 25 Apr 2011 10:26:56 -0000 On Mon, 25 Apr 2011, Bartosz Fabianowski wrote: [Jeremy wrote:] > > As the processor gets hotter, internal clocks and so on are throttled > > within the hardware to try and stabilise the temperature (to keep the > > thermal trip point being reached, re: "emergency shutdown"), which > > greatly decreases performance. I'm not sure if there's a way to > > detect this, but I would hope (?) that it would be visible via the > > CPU clock frequency (on FreeBSD this would be sysctl > > dev.cpu.X.freq). > > sysctl dev.cpu.X.freq is used to set the frequency. I have not found any > way to read back its internal state so far. dev.cpu.X.freq does reflect the current frequency; I don't know whether or how any internal clock throttling might be exposed. Jeremy's right, it's running very hot, probably 20C too hot. I was just going to mention a couple of things you could try when it began to seem all too familiar .. a bit of hunting found your previous overheating problems on a Dell Studio 1557 from April last year: http://lists.freebsd.org/pipermail/freebsd-acpi/2010-April/006415.html and your eventual apparent solution which included some fiddling with thermal parameters but primarily by disabling p4tcc and acpi_throttle hint.p4tcc.0.disabled="1" hint.acpi_throttle.0.disabled="1" in loader.conf; I'm surprised you haven't tried that again on this one? > hw.acpi.cpu.cx_lowest: C1 See below. > hw.acpi.thermal.min_runtime: 0 > hw.acpi.thermal.polling_rate: 10 > hw.acpi.thermal.user_override: 0 > hw.acpi.thermal.tz0.temperature: 26.8C > hw.acpi.thermal.tz0.active: -1 > hw.acpi.thermal.tz0.passive_cooling: 0 > hw.acpi.thermal.tz0.thermal_flags: 0 > hw.acpi.thermal.tz0._PSV: -1 > hw.acpi.thermal.tz0._HOT: -1 > hw.acpi.thermal.tz0._CRT: 100.0C > hw.acpi.thermal.tz0._ACx: 71.0C 55.0C -1 -1 -1 -1 -1 -1 -1 -1 > hw.acpi.thermal.tz0._TC1: -1 > hw.acpi.thermal.tz0._TC2: -1 > hw.acpi.thermal.tz0._TSP: -1 tz0 looks to be a fan. It seems unlikely that any temp. sensor inside a machine with CPU temp. at 82C could possibly be as low as 26.8C, so this value is likely as bogus as the 0.0C CPU reported by tz1. This fan should come on at 55C and run fastest above 71C. If your CPU is at 82C and the fan isn't running flat out, it'd overheat for sure. tz0.active is -1, not running - but maybe the BIOS is controlling it? > hw.acpi.thermal.tz1.temperature: 0.0C > hw.acpi.thermal.tz1.active: -1 > hw.acpi.thermal.tz1.passive_cooling: 1 > hw.acpi.thermal.tz1.thermal_flags: 0 > hw.acpi.thermal.tz1._PSV: 95.0C > hw.acpi.thermal.tz1._HOT: -1 > hw.acpi.thermal.tz1._CRT: 100.0C > hw.acpi.thermal.tz1._ACx: 71.0C 55.0C -1 -1 -1 -1 -1 -1 -1 -1 > hw.acpi.thermal.tz1._TC1: 0 > hw.acpi.thermal.tz1._TC2: 2 > hw.acpi.thermal.tz1._TSP: 10 _ACx is N/A here, unless there's a separate CPU fan? Anyway at bogus 0.0C it's never going to trigger passive or active cooling. You said before that with the fixed DSDT to get proper temperature reading here, it shut down due to over temperature, which of course it should .. does that fixed DSDT include fixing detected tz0 temperature .. if so the fan might behave itself without having to use .thermal.user_override=1 > dev.cpu.0.temperature: 82.0C > dev.cpu.0.freq: 1333 Are you limiting it to 1333 manually, or with powerd's -M switch? > dev.cpu.0.freq_levels: 1734/45000 1599/41741 1466/38582 1333/35485 1199/32426 > 1066/29457 933/26552 816/23233 699/19914 583/16595 466/13276 349/9957 > 233/6638 116/3319 Clearly including p4tcc and/or acpi_throttle N*12.5% rates; compare to dev.est.0.freq_settings below to figure the freqs added by throttling. Hopefully this machine will respond as well to disabling both methods as your earlier one, as you reported here (same subject, later thread): http://lists.freebsd.org/pipermail/freebsd-acpi/2010-April/006443.html The more I review those threads, the more it seems likely that this is your main problem on this one too. > dev.cpu.0.cx_supported: C1/3 C2/245 > dev.cpu.0.cx_lowest: C1 > dev.cpu.0.cx_usage: 100.00% 0.00% last 285us Try using C2. It helps more with some CPUs than others, but it's worth a try for further reducing heat, especially at idle. Ie in rc.conf: performance_cx_lowest="C2" economy_cx_lowest="C2" Latency 245us isn't long compared to the delays you're experiencing :) > dev.est.0.freq_settings: 1734/45000 1733/45000 1599/41741 1466/38582 > 1333/35485 1199/32426 1066/29457 933/26552 With throttling disabled, those are what you should be left with for dev.cpu.0.freq_levels. cheers, Ian From owner-freebsd-stable@FreeBSD.ORG Mon Apr 25 12:46:09 2011 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 C66C0106566C for ; Mon, 25 Apr 2011 12:46:09 +0000 (UTC) (envelope-from freebsd@chillt.de) Received: from dd16434.kasserver.com (dd16434.kasserver.com [85.13.137.111]) by mx1.freebsd.org (Postfix) with ESMTP id 588638FC1B for ; Mon, 25 Apr 2011 12:46:08 +0000 (UTC) Received: from taiko.lan (ppp-94-44.21-151.libero.it [151.21.44.94]) by dd16434.kasserver.com (Postfix) with ESMTPSA id 2A1E3188603F; Mon, 25 Apr 2011 14:46:06 +0200 (CEST) Message-ID: <4DB56CDA.50504@chillt.de> Date: Mon, 25 Apr 2011 14:45:14 +0200 From: Bartosz Fabianowski User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110309 Thunderbird/3.1.9 MIME-Version: 1.0 To: Ian Smith References: <4DA596D3.1090803@chillt.de> <4DB44DA3.5060509@chillt.de> <4DB4589B.2020909@ksu.ru> <4DB45D6C.20203@chillt.de> <20110424182456.9DD03589@server.theusgroup.com> <4DB46ED4.2010500@chillt.de> <20110425004818.GA22579@icarus.home.lan> <4DB51F27.5010508@chillt.de> <20110425184728.C73992@sola.nimnet.asn.au> In-Reply-To: <20110425184728.C73992@sola.nimnet.asn.au> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-stable@freebsd.org, John , Jeremy Chadwick Subject: Re: System extremely slow under light load 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, 25 Apr 2011 12:46:09 -0000 > dev.cpu.X.freq does reflect the current frequency; I don't know whether > or how any internal clock throttling might be exposed. From what I have seen, dev.cpu.X.freq always retains the value I set it to. Internal CPU throttling does not seem to be reported this way. > a bit of hunting found your previous overheating > problems on a Dell Studio 1557 from April last year: > > and your eventual apparent solution which included some fiddling with > thermal parameters but primarily by disabling p4tcc and acpi_throttle Yes, that thread described the issues I had with my previous laptop before Dell exchanged it. I never posted an actual solution as I never found one. The problem only went away because the laptop went away. Disabling p4tcc and acpi_throttle may have seemed to address the problems at first - but longer-term evaluation showed that the issues persisted unchanged. > hint.p4tcc.0.disabled="1" > hint.acpi_throttle.0.disabled="1" I just tried this on my current Dell Studio 1558, with devastating results. The first boot attempt ended with the machine shutting down due to overheating while loading the kernel. I let it cool down a bit and then booted again. This time, I got to my desktop - with a CPU temperature of 95°C. If the DSDT was fixed, the machine would have shut down at this point. I only got down the temperature by reducing the maximal temperature to 1.2GHz again. With the above settings, the machine is idling at 80°C now and very sluggish - some internal throttling appears to be active again. > tz0 looks to be a fan. It seems unlikely that any temp. sensor inside a > machine with CPU temp. at 82C could possibly be as low as 26.8C, so this > value is likely as bogus as the 0.0C CPU reported by tz1. Yes, the 26.8°C is bogus. It never changes. Unfortunately, I have not found a way to fix this reading. The two thermal zones are implemented very differently in the DSDT and I have only managed to fix tz1. However, there is no second fan inside the laptop. I have taken it apart down to the last screw. There is one fan only and that corresponds to tz0. > This fan should come on at 55C and run fastest above 71C. If your CPU > is at 82C and the fan isn't running flat out, it'd overheat for sure. > tz0.active is -1, not running - but maybe the BIOS is controlling it? Yes, the BIOS appears to control the fan. The thresholds exposed via ACPI seem to be purely informative. Whether I fix the DSDT so that temperature readings work or not, the fan turns on at 55°C and speeds up at 71°C. It never spins down again after that as the CPU keeps running very hot. > _ACx is N/A here, unless there's a separate CPU fan? Anyway at bogus > 0.0C it's never going to trigger passive or active cooling. You said > before that with the fixed DSDT to get proper temperature reading here, > it shut down due to over temperature, which of course it should .. does > that fixed DSDT include fixing detected tz0 temperature .. if so the fan > might behave itself without having to use .thermal.user_override=1 See above: Fixing the DSDT makes tz1 work. tz0 remains broken. > Are you limiting it to 1333 manually, or with powerd's -M switch? I have tried both. It appears to make no difference whether I use powerd -M or just set dev.cpu.0.freq directly. > Clearly including p4tcc and/or acpi_throttle N*12.5% rates; compare to > dev.est.0.freq_settings below to figure the freqs added by throttling. > > Hopefully this machine will respond as well to disabling both methods as > your earlier one, as you reported here (same subject, later thread): See above: Unfortunately, the machine did nor respond well at all. Instead, it is overheating even worse. > Try using C2. It helps more with some CPUs than others, but it's worth > a try for further reducing heat, especially at idle. Ie in rc.conf: > > performance_cx_lowest="C2" > economy_cx_lowest="C2" I have set dev.cpu.X.cx_lowest="C2" at run-time. If I understand correctly, this should achieve the same effect. The CPU does not seem to ever make it to C2 though, even after I enable it: %sysctl dev.cpu | grep cx_usage dev.cpu.0.cx_usage: 100.00% 0.00% last 270us dev.cpu.1.cx_usage: 100.00% 0.00% last 399us dev.cpu.2.cx_usage: 100.00% 0.00% last 403us dev.cpu.3.cx_usage: 100.00% 0.00% last 404us dev.cpu.4.cx_usage: 100.00% 0.00% last 323us dev.cpu.5.cx_usage: 100.00% 0.00% last 313us dev.cpu.6.cx_usage: 100.00% 0.00% last 174us dev.cpu.7.cx_usage: 100.00% 0.00% last 137us > > dev.est.0.freq_settings: 1734/45000 1733/45000 1599/41741 1466/38582 > > 1333/35485 1199/32426 1066/29457 933/26552 > > With throttling disabled, those are what you should be left with for > dev.cpu.0.freq_levels. Yes, these are the frequencies I have available now. 1333 makes the machine idle around 85°C, 1999 leads to 78-80°C. - Bartosz From owner-freebsd-stable@FreeBSD.ORG Mon Apr 25 12:51:27 2011 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 4F5BB106566C for ; Mon, 25 Apr 2011 12:51:27 +0000 (UTC) (envelope-from bsd.gaijin@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 14D778FC0C for ; Mon, 25 Apr 2011 12:51:26 +0000 (UTC) Received: by iyj12 with SMTP id 12so2578025iyj.13 for ; Mon, 25 Apr 2011 05:51:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to:cc :content-type; bh=u87lH3rXTj5BboCazfc6kJey4ml76musjMFc3HlKDXE=; b=Lky/4Mvw1CBb3YLqzKix/x+nAu9uF3PSEim1yizhfwm2QOfq1I0wf/vVUBgU3LIwC7 wc0Og8gtebaAtujfBaBvASvD2wfYlPD5dQfrAJHTvOaxURve/4u7StKjHejA11TlpHxx K8XmhSkWgTHPBD19NWWTleYOOm12QE5yX1G30= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=GJiDSCvGAB87LJ7EYFOBiUY6e03PDfh756tgSK+gqtO7xT07UFubXk3qdJsZVY2+4N Us/Z6pBP6rgW9VA71FHJIf+C0Ln04D2Yb3f50fNiq/n4kjxn2eHdrchYlTPnMn0RMoGw R9K16XOuk/YAXaWIg1UIASrO8uDXJlY4V7EuQ= MIME-Version: 1.0 Received: by 10.42.11.207 with SMTP id v15mr4917723icv.22.1303734053540; Mon, 25 Apr 2011 05:20:53 -0700 (PDT) Received: by 10.42.225.200 with HTTP; Mon, 25 Apr 2011 05:20:53 -0700 (PDT) Received: by 10.42.225.200 with HTTP; Mon, 25 Apr 2011 05:20:53 -0700 (PDT) Date: Mon, 25 Apr 2011 08:20:53 -0400 Message-ID: From: Alexandre Kovalenko To: Ian Smith Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Bartosz Fabianowski , freebsd-stable@freebsd.org, John , Jeremy Chadwick Subject: Re: System extremely slow under light load 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, 25 Apr 2011 12:51:27 -0000 On Apr 25, 2011 6:28 AM, "Ian Smith" wrote: > > On Mon, 25 Apr 2011, Bartosz Fabianowski wrote: > [Jeremy wrote:] > > > As the processor gets hotter, internal clocks and so on are throttled > > > within the hardware to try and stabilise the temperature (to keep the > > > thermal trip point being reached, re: "emergency shutdown"), which > > > greatly decreases performance. I'm not sure if there's a way to > > > detect this, but I would hope (?) that it would be visible via the > > > CPU clock frequency (on FreeBSD this would be sysctl > > > dev.cpu.X.freq). > > > > sysctl dev.cpu.X.freq is used to set the frequency. I have not found any > > way to read back its internal state so far. > > dev.cpu.X.freq does reflect the current frequency; I don't know whether > or how any internal clock throttling might be exposed. > > Jeremy's right, it's running very hot, probably 20C too hot. I was just > going to mention a couple of things you could try when it began to seem > all too familiar .. a bit of hunting found your previous overheating > problems on a Dell Studio 1557 from April last year: > > http://lists.freebsd.org/pipermail/freebsd-acpi/2010-April/006415.html > > and your eventual apparent solution which included some fiddling with > thermal parameters but primarily by disabling p4tcc and acpi_throttle > > hint.p4tcc.0.disabled="1" > hint.acpi_throttle.0.disabled="1" > > in loader.conf; I'm surprised you haven't tried that again on this one? > > > hw.acpi.cpu.cx_lowest: C1 > > See below. > > > hw.acpi.thermal.min_runtime: 0 > > hw.acpi.thermal.polling_rate: 10 > > hw.acpi.thermal.user_override: 0 > > hw.acpi.thermal.tz0.temperature: 26.8C > > hw.acpi.thermal.tz0.active: -1 > > hw.acpi.thermal.tz0.passive_cooling: 0 > > hw.acpi.thermal.tz0.thermal_flags: 0 > > hw.acpi.thermal.tz0._PSV: -1 > > hw.acpi.thermal.tz0._HOT: -1 > > hw.acpi.thermal.tz0._CRT: 100.0C > > hw.acpi.thermal.tz0._ACx: 71.0C 55.0C -1 -1 -1 -1 -1 -1 -1 -1 > > hw.acpi.thermal.tz0._TC1: -1 > > hw.acpi.thermal.tz0._TC2: -1 > > hw.acpi.thermal.tz0._TSP: -1 > > tz0 looks to be a fan. It seems unlikely that any temp. sensor inside a > machine with CPU temp. at 82C could possibly be as low as 26.8C, so this > value is likely as bogus as the 0.0C CPU reported by tz1. I am not sure tz0 is the real thermal zone, especially given values of _tc1, _tc2 and _tsp. Temperature value (3001) looks suspicious as well. Can you, by any chance, put your ASL someplace accessible and provide a description of what you have done to fix the temperature reporting. As the side note: I have seen and do own pieces of equipment that use thermal zones to initiate critical shutdown for various and unrelated reasons. From owner-freebsd-stable@FreeBSD.ORG Mon Apr 25 13:21:24 2011 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 9ADF5106566C for ; Mon, 25 Apr 2011 13:21:24 +0000 (UTC) (envelope-from freebsd@chillt.de) Received: from dd16434.kasserver.com (dd16434.kasserver.com [85.13.137.111]) by mx1.freebsd.org (Postfix) with ESMTP id 5CDBF8FC17 for ; Mon, 25 Apr 2011 13:21:24 +0000 (UTC) Received: from taiko.lan (ppp-94-44.21-151.libero.it [151.21.44.94]) by dd16434.kasserver.com (Postfix) with ESMTPSA id 0B304188603F; Mon, 25 Apr 2011 15:21:14 +0200 (CEST) Message-ID: <4DB5751B.2050903@chillt.de> Date: Mon, 25 Apr 2011 15:20:27 +0200 From: Bartosz Fabianowski User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110309 Thunderbird/3.1.9 MIME-Version: 1.0 To: Alexandre Kovalenko References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-stable@freebsd.org, Ian Smith , Jeremy Chadwick , John Subject: Re: System extremely slow under light load 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, 25 Apr 2011 13:21:24 -0000 > I am not sure tz0 is the real thermal zone, especially given values > of _tc1, _tc2 and _tsp. Temperature value (3001) looks suspicious as > well. I agree. tz0 looks entirely bogus. There is no second fan to control for it and I have no idea what it is supposed to be monitoring. > Can you, by any chance, put your ASL someplace accessible and provide > a description of what you have done to fix the temperature > reporting. Certainly. I have uploaded the files at [1] through [5]. The DSDT source returned by acpidump -d is at [1]. I modified this so that it can be compiled back into AML without errors or warnings. This modified source is at [2]. It contains no functional changes. The thermal zones are still broken. A variant with fixed tz1 is at [3]. For convenience, I have also uploaded diffs between these source files. [4] is the diff required to make the source compile (difference between [1] and [2]). [5] is the actual change I made to fix tz1 (difference between [2] and [3]). As you can see, all I did was to remove a bogus function that ends up always returning 0°C. > As the side note: I have seen and do own pieces of equipment that > use thermal zones to initiate critical shutdown for various and > unrelated reasons. In my case, the thermal zone and its various tripping points do correspond to the actual system fan. It is just that the BIOS enforces power management itself, ignoring ACPI - except for critical shutdown which appears to be triggered by ACPI only. - Bartosz [1] http://www.fabianowski.de/dsdt/decompiled.asl [2] http://www.fabianowski.de/dsdt/compilable.asl [3] http://www.fabianowski.de/dsdt/fixed.asl [4] http://www.fabianowski.de/dsdt/decompile_compilable.diff [5] http://www.fabianowski.de/dsdt/compilable_fixed.diff From owner-freebsd-stable@FreeBSD.ORG Mon Apr 25 13:58:47 2011 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 7BA5A106564A for ; Mon, 25 Apr 2011 13:58:47 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) by mx1.freebsd.org (Postfix) with ESMTP id C1F0A8FC12 for ; Mon, 25 Apr 2011 13:58:46 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id p3PDwdbJ090015; Mon, 25 Apr 2011 23:58:40 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Mon, 25 Apr 2011 23:58:39 +1000 (EST) From: Ian Smith To: Bartosz Fabianowski In-Reply-To: <4DB56CDA.50504@chillt.de> Message-ID: <20110425232429.N85801@sola.nimnet.asn.au> References: <4DA596D3.1090803@chillt.de> <4DB44DA3.5060509@chillt.de> <4DB4589B.2020909@ksu.ru> <4DB45D6C.20203@chillt.de> <20110424182456.9DD03589@server.theusgroup.com> <4DB46ED4.2010500@chillt.de> <20110425004818.GA22579@icarus.home.lan> <4DB51F27.5010508@chillt.de> <20110425184728.C73992@sola.nimnet.asn.au> <4DB56CDA.50504@chillt.de> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-152062992-1303739724=:85801" Content-ID: <20110425235750.M85801@sola.nimnet.asn.au> Cc: freebsd-stable@freebsd.org, John , Jeremy Chadwick Subject: Re: System extremely slow under light load 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, 25 Apr 2011 13:58:47 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-152062992-1303739724=:85801 Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-1 Content-Transfer-Encoding: 8BIT Content-ID: <20110425235750.E85801@sola.nimnet.asn.au> On Mon, 25 Apr 2011, Bartosz Fabianowski wrote: [..] > See above: Unfortunately, the machine did nor respond well at all. Instead, > it is overheating even worse. Sorry to hear none of that helped. It seems a very serious problem, and it would be useful to know if it behaves any better under linux or not. > > Try using C2. It helps more with some CPUs than others, but it's worth > > a try for further reducing heat, especially at idle. Ie in rc.conf: > > > > performance_cx_lowest="C2" > > economy_cx_lowest="C2" > > I have set dev.cpu.X.cx_lowest="C2" at run-time. If I understand correctly, > this should achieve the same effect. The CPU does not seem to ever make it to > C2 though, even after I enable it: > > %sysctl dev.cpu | grep cx_usage > dev.cpu.0.cx_usage: 100.00% 0.00% last 270us > dev.cpu.1.cx_usage: 100.00% 0.00% last 399us > dev.cpu.2.cx_usage: 100.00% 0.00% last 403us > dev.cpu.3.cx_usage: 100.00% 0.00% last 404us > dev.cpu.4.cx_usage: 100.00% 0.00% last 323us > dev.cpu.5.cx_usage: 100.00% 0.00% last 313us > dev.cpu.6.cx_usage: 100.00% 0.00% last 174us > dev.cpu.7.cx_usage: 100.00% 0.00% last 137us You need sysctl hw.acpi.cpu.cx_lowest="C2" instead .. that's what /etc/rc.d/power_profile adjusts when you apply or remove power. I doubt it's likely to help much given the scale of overheating. > > > dev.est.0.freq_settings: 1734/45000 1733/45000 1599/41741 1466/38582 > > > 1333/35485 1199/32426 1066/29457 933/26552 > > > > With throttling disabled, those are what you should be left with for > > dev.cpu.0.freq_levels. > > Yes, these are the frequencies I have available now. 1333 makes the machine > idle around 85C, 1999 leads to 78-80C. That's pretty sad. Not sure what the first two differing by only 1MHz means .. but I'm out of ideas, and my depth. cheers, Ian --0-152062992-1303739724=:85801-- From owner-freebsd-stable@FreeBSD.ORG Mon Apr 25 14:04:37 2011 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 9117D1065670 for ; Mon, 25 Apr 2011 14:04:37 +0000 (UTC) (envelope-from freebsd@chillt.de) Received: from dd16434.kasserver.com (dd16434.kasserver.com [85.13.137.111]) by mx1.freebsd.org (Postfix) with ESMTP id 507BF8FC1A for ; Mon, 25 Apr 2011 14:04:36 +0000 (UTC) Received: from taiko.lan (ppp-94-44.21-151.libero.it [151.21.44.94]) by dd16434.kasserver.com (Postfix) with ESMTPSA id 0D9FA188603F; Mon, 25 Apr 2011 16:04:35 +0200 (CEST) Message-ID: <4DB57F45.4080107@chillt.de> Date: Mon, 25 Apr 2011 16:03:49 +0200 From: Bartosz Fabianowski User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110309 Thunderbird/3.1.9 MIME-Version: 1.0 To: Ian Smith References: <4DA596D3.1090803@chillt.de> <4DB44DA3.5060509@chillt.de> <4DB4589B.2020909@ksu.ru> <4DB45D6C.20203@chillt.de> <20110424182456.9DD03589@server.theusgroup.com> <4DB46ED4.2010500@chillt.de> <20110425004818.GA22579@icarus.home.lan> <4DB51F27.5010508@chillt.de> <20110425184728.C73992@sola.nimnet.asn.au> <4DB56CDA.50504@chillt.de> <20110425232429.N85801@sola.nimnet.asn.au> In-Reply-To: <20110425232429.N85801@sola.nimnet.asn.au> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, John , Jeremy Chadwick Subject: Re: System extremely slow under light load 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, 25 Apr 2011 14:04:37 -0000 > Sorry to hear none of that helped. It seems a very serious problem, and > it would be useful to know if it behaves any better under linux or not. I am still on the hunt for a bootable Linux distribution. I am in the unfortunate situation of having no CD-Rs at hand. And because it is Easter, shops are closed. Most Linux distributions require you to run a proprietary tool from inside Windows or another Linux installation to create a bootable USB medium. I found a USB image for OpenSUSE but that failed to boot. I am continuing to hunt... > You need sysctl hw.acpi.cpu.cx_lowest="C2" instead .. that's what > /etc/rc.d/power_profile adjusts when you apply or remove power. > I doubt it's likely to help much given the scale of overheating. I use the correct sysctl now, the cx_lowest value changed from C1 to C2 for all CPUs but nothing seems to have changed otherwise: %sysctl dev.cpu | grep cx_usage dev.cpu.0.cx_usage: 100.00% 0.00% last 230us dev.cpu.1.cx_usage: 100.00% 0.00% last 216us dev.cpu.2.cx_usage: 100.00% 0.00% last 159us dev.cpu.3.cx_usage: 100.00% 0.00% last 323us dev.cpu.4.cx_usage: 100.00% 0.00% last 320us dev.cpu.5.cx_usage: 100.00% 0.00% last 357us dev.cpu.6.cx_usage: 100.00% 0.00% last 378us dev.cpu.7.cx_usage: 100.00% 0.00% last 374us > That's pretty sad. Not sure what the first two differing by only 1MHz > means .. but I'm out of ideas, and my depth. Thanks for all the tips. I will report back once I have had a chance to compare with Linux. If nothing else helps, I will call Dell again in the futile attempt to have them magically fix the issue somehow. - Bartosz From owner-freebsd-stable@FreeBSD.ORG Mon Apr 25 14:16:45 2011 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 D17AA106564A for ; Mon, 25 Apr 2011 14:16:45 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta06.emeryville.ca.mail.comcast.net (qmta06.emeryville.ca.mail.comcast.net [76.96.30.56]) by mx1.freebsd.org (Postfix) with ESMTP id B485F8FC12 for ; Mon, 25 Apr 2011 14:16:45 +0000 (UTC) Received: from omta13.emeryville.ca.mail.comcast.net ([76.96.30.52]) by qmta06.emeryville.ca.mail.comcast.net with comcast id bpqY1g00517UAYkA6qGlhM; Mon, 25 Apr 2011 14:16:45 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta13.emeryville.ca.mail.comcast.net with comcast id bqGj1g00W1t3BNj8ZqGjPq; Mon, 25 Apr 2011 14:16:44 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 18B429B418; Mon, 25 Apr 2011 07:16:43 -0700 (PDT) Date: Mon, 25 Apr 2011 07:16:43 -0700 From: Jeremy Chadwick To: Bartosz Fabianowski Message-ID: <20110425141643.GA38380@icarus.home.lan> References: <4DB4589B.2020909@ksu.ru> <4DB45D6C.20203@chillt.de> <20110424182456.9DD03589@server.theusgroup.com> <4DB46ED4.2010500@chillt.de> <20110425004818.GA22579@icarus.home.lan> <4DB51F27.5010508@chillt.de> <20110425184728.C73992@sola.nimnet.asn.au> <4DB56CDA.50504@chillt.de> <20110425232429.N85801@sola.nimnet.asn.au> <4DB57F45.4080107@chillt.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4DB57F45.4080107@chillt.de> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@freebsd.org, Ian Smith , John Subject: Re: System extremely slow under light load 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, 25 Apr 2011 14:16:45 -0000 On Mon, Apr 25, 2011 at 04:03:49PM +0200, Bartosz Fabianowski wrote: > >Sorry to hear none of that helped. It seems a very serious problem, and > >it would be useful to know if it behaves any better under linux or not. > > I am still on the hunt for a bootable Linux distribution. I am in > the unfortunate situation of having no CD-Rs at hand. And because it > is Easter, shops are closed. > > Most Linux distributions require you to run a proprietary tool from > inside Windows or another Linux installation to create a bootable > USB medium. I found a USB image for OpenSUSE but that failed to > boot. I am continuing to hunt... Try Knoppix, or Ubuntu LiveCD. I tend to use the former for rescue situations: http://www.knopper.net/knoppix/index-en.html https://help.ubuntu.com/community/LiveCD Saves you from having to install anything as well. Don't expect good X performance, but even if it's software-driven that's still a good stress test for the CPU. > Thanks for all the tips. I will report back once I have had a chance > to compare with Linux. If nothing else helps, I will call Dell again > in the futile attempt to have them magically fix the issue somehow. I'll be very surprised if Dell is of any assistance, as the last I checked they did not officially "support" FreeBSD (that's usually their statement). I think testing Linux and/or Windows will overall act as a better confirmation. I wish I knew what else to recommend too, or what else to check. :-( Folks familiar with ACPI tables might be able to shed some light on the situation, if it is indeed a problem there. -- | Jeremy Chadwick jdc@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 Apr 25 14:24:26 2011 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 B5C21106566C for ; Mon, 25 Apr 2011 14:24:26 +0000 (UTC) (envelope-from freebsd@chillt.de) Received: from dd16434.kasserver.com (dd16434.kasserver.com [85.13.137.111]) by mx1.freebsd.org (Postfix) with ESMTP id 764008FC16 for ; Mon, 25 Apr 2011 14:24:26 +0000 (UTC) Received: from taiko.lan (ppp-94-44.21-151.libero.it [151.21.44.94]) by dd16434.kasserver.com (Postfix) with ESMTPSA id ECCB2188603F; Mon, 25 Apr 2011 16:24:24 +0200 (CEST) Message-ID: <4DB583E9.8080507@chillt.de> Date: Mon, 25 Apr 2011 16:23:37 +0200 From: Bartosz Fabianowski User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110309 Thunderbird/3.1.9 MIME-Version: 1.0 To: Jeremy Chadwick References: <4DB4589B.2020909@ksu.ru> <4DB45D6C.20203@chillt.de> <20110424182456.9DD03589@server.theusgroup.com> <4DB46ED4.2010500@chillt.de> <20110425004818.GA22579@icarus.home.lan> <4DB51F27.5010508@chillt.de> <20110425184728.C73992@sola.nimnet.asn.au> <4DB56CDA.50504@chillt.de> <20110425232429.N85801@sola.nimnet.asn.au> <4DB57F45.4080107@chillt.de> <20110425141643.GA38380@icarus.home.lan> In-Reply-To: <20110425141643.GA38380@icarus.home.lan> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Ian Smith , John Subject: Re: System extremely slow under light load 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, 25 Apr 2011 14:24:26 -0000 > Try Knoppix, or Ubuntu LiveCD. I tend to use the former for rescue > situations: Thanks. I am aware of both - but neither boots from USB (and I have no CD-Rs at hand). I am running UNetbootin under Windows XP in VirtualBox right now to try and get Xubuntu 10.04 onto a USB key. It is really sad that almost all Linux distributions require this detour via a proprietary operating system. > I'll be very surprised if Dell is of any assistance, as the last I > checked they did not officially "support" FreeBSD (that's usually their > statement). I think testing Linux and/or Windows will overall act as a > better confirmation. Absolutely, they do not "support" FreeBSD. But if the laptop overheats during normal usage, to me, the hardware is broken and needs to be fixed. So far, Dell have been very cooperative, sent out technicians several times and in the end provided me with a completely new laptop. Going by this previous experience, I expect them to send out a technician again and attempt a repair. I am doubtful it will actually fix anything though. > I wish I knew what else to recommend too, or what else to check. :-( > Folks familiar with ACPI tables might be able to shed some light on the > situation, if it is indeed a problem there. I will be able to provide a comparison with Linux soon. This may be helpful. - Bartosz From owner-freebsd-stable@FreeBSD.ORG Mon Apr 25 14:50:41 2011 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 4E62D106566B for ; Mon, 25 Apr 2011 14:50:41 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id BCD628FC13 for ; Mon, 25 Apr 2011 14:50:40 +0000 (UTC) Received: by qwc9 with SMTP id 9so1259838qwc.13 for ; Mon, 25 Apr 2011 07:50:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=9eDzCqQEk0L1Syqh3F8Xm3uV/qI2s+9chBNs9EIxElE=; b=A2dMUg2+YLvIukClQDKpWgT97oMWbb2E++B3a9KGurm5tepy66lDmd1zZ+vdZ+9KWs sEmL5uOjM/7sXDMg/Q0xSwURrznh9I/6+TNm27+X06CsDr+RBuiZQsUufCDP29R1ZuEV GBRGcCopRtz5HxS9c/PLPo4Rqe165IhKkwPbk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=fEsRaHMmN9iouR4/HHAQ5oDoBIkaTSdi5vrp91+89xxG/+0X8BSEPU6jSrAJPr8tiO ZpSBWwtYMI+nct56d/OSLd+JuZS7kHW/6SXyCL+XL8P7TAnp2dSozZELeH26b6fv3Mke g/LbwfMEqCG+IaIczEnxpYA2R6+VrPu3i9W1Y= MIME-Version: 1.0 Received: by 10.224.189.9 with SMTP id dc9mr2894905qab.11.1303743038647; Mon, 25 Apr 2011 07:50:38 -0700 (PDT) Received: by 10.224.179.212 with HTTP; Mon, 25 Apr 2011 07:50:38 -0700 (PDT) In-Reply-To: <4DB57F45.4080107@chillt.de> References: <4DA596D3.1090803@chillt.de> <4DB44DA3.5060509@chillt.de> <4DB4589B.2020909@ksu.ru> <4DB45D6C.20203@chillt.de> <20110424182456.9DD03589@server.theusgroup.com> <4DB46ED4.2010500@chillt.de> <20110425004818.GA22579@icarus.home.lan> <4DB51F27.5010508@chillt.de> <20110425184728.C73992@sola.nimnet.asn.au> <4DB56CDA.50504@chillt.de> <20110425232429.N85801@sola.nimnet.asn.au> <4DB57F45.4080107@chillt.de> Date: Mon, 25 Apr 2011 10:50:38 -0400 Message-ID: From: Mehmet Erol Sanliturk To: Bartosz Fabianowski Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org, Ian Smith , Jeremy Chadwick , John Subject: Re: System extremely slow under light load 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, 25 Apr 2011 14:50:41 -0000 On Mon, Apr 25, 2011 at 10:03 AM, Bartosz Fabianowski wrote: > Sorry to hear none of that helped. It seems a very serious problem, and >> it would be useful to know if it behaves any better under linux or not. >> > > I am still on the hunt for a bootable Linux distribution. I am in the > unfortunate situation of having no CD-Rs at hand. And because it is Easter, > shops are closed. > > Most Linux distributions require you to run a proprietary tool from inside > Windows or another Linux installation to create a bootable USB medium. I > found a USB image for OpenSUSE but that failed to boot. I am continuing to > hunt... > > You need sysctl hw.acpi.cpu.cx_lowest="C2" instead .. that's what >> /etc/rc.d/power_profile adjusts when you apply or remove power. >> I doubt it's likely to help much given the scale of overheating. >> > > I use the correct sysctl now, the cx_lowest value changed from C1 to C2 for > all CPUs but nothing seems to have changed otherwise: > > %sysctl dev.cpu | grep cx_usage > dev.cpu.0.cx_usage: 100.00% 0.00% last 230us > dev.cpu.1.cx_usage: 100.00% 0.00% last 216us > dev.cpu.2.cx_usage: 100.00% 0.00% last 159us > dev.cpu.3.cx_usage: 100.00% 0.00% last 323us > dev.cpu.4.cx_usage: 100.00% 0.00% last 320us > dev.cpu.5.cx_usage: 100.00% 0.00% last 357us > dev.cpu.6.cx_usage: 100.00% 0.00% last 378us > dev.cpu.7.cx_usage: 100.00% 0.00% last 374us > > That's pretty sad. Not sure what the first two differing by only 1MHz >> means .. but I'm out of ideas, and my depth. >> > > Thanks for all the tips. I will report back once I have had a chance to > compare with Linux. If nothing else helps, I will call Dell again in the > futile attempt to have them magically fix the issue somehow. > > - Bartosz > _______________________________________________ > > Please , see the site http://www.mandriva.com/en/linux/ My opinion is that Mandriva is a very good Linux distribution . Thank you very much . Mehmet Erol Sanliturk From owner-freebsd-stable@FreeBSD.ORG Mon Apr 25 14:59:13 2011 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 66263106566B for ; Mon, 25 Apr 2011 14:59:13 +0000 (UTC) (envelope-from freebsd@chillt.de) Received: from dd16434.kasserver.com (dd16434.kasserver.com [85.13.137.111]) by mx1.freebsd.org (Postfix) with ESMTP id 241D98FC1E for ; Mon, 25 Apr 2011 14:59:12 +0000 (UTC) Received: from taiko.lan (ppp-94-44.21-151.libero.it [151.21.44.94]) by dd16434.kasserver.com (Postfix) with ESMTPSA id CA2B0188603F; Mon, 25 Apr 2011 16:59:10 +0200 (CEST) Message-ID: <4DB58C0F.3020803@chillt.de> Date: Mon, 25 Apr 2011 16:58:23 +0200 From: Bartosz Fabianowski User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110309 Thunderbird/3.1.9 MIME-Version: 1.0 To: Mehmet Erol Sanliturk References: <4DA596D3.1090803@chillt.de> <4DB44DA3.5060509@chillt.de> <4DB4589B.2020909@ksu.ru> <4DB45D6C.20203@chillt.de> <20110424182456.9DD03589@server.theusgroup.com> <4DB46ED4.2010500@chillt.de> <20110425004818.GA22579@icarus.home.lan> <4DB51F27.5010508@chillt.de> <20110425184728.C73992@sola.nimnet.asn.au> <4DB56CDA.50504@chillt.de> <20110425232429.N85801@sola.nimnet.asn.au> <4DB57F45.4080107@chillt.de> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-stable@freebsd.org, Ian Smith , Jeremy Chadwick , John Subject: Re: System extremely slow under light load 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, 25 Apr 2011 14:59:13 -0000 > Please , see the site > > http://www.mandriva.com/en/linux/ Thanks for the link. It looks like this a USB with a preinstalled Mandriva Linux on it that you have to buy for €50 though. I am looking for an image that I can just download. - Bartosz From owner-freebsd-stable@FreeBSD.ORG Mon Apr 25 15:02:07 2011 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 90D731065676 for ; Mon, 25 Apr 2011 15:02:07 +0000 (UTC) (envelope-from florian@wagner-flo.net) Received: from umbracor.wagner-flo.net (umbracor.wagner-flo.net [213.165.81.202]) by mx1.freebsd.org (Postfix) with ESMTP id 470048FC20 for ; Mon, 25 Apr 2011 15:02:07 +0000 (UTC) Received: from naclador.mos32.de (ppp-188-174-58-111.dynamic.mnet-online.de [188.174.58.111]) by umbracor.wagner-flo.net (Postfix) with ESMTPSA id D24063C07EE4 for ; Mon, 25 Apr 2011 17:02:05 +0200 (CEST) Date: Mon, 25 Apr 2011 17:02:04 +0200 From: Florian Wagner To: freebsd-stable@freebsd.org Message-ID: <20110425170204.72c064cd@naclador.mos32.de> In-Reply-To: <4DB57F45.4080107@chillt.de> References: <4DA596D3.1090803@chillt.de> <4DB44DA3.5060509@chillt.de> <4DB4589B.2020909@ksu.ru> <4DB45D6C.20203@chillt.de> <20110424182456.9DD03589@server.theusgroup.com> <4DB46ED4.2010500@chillt.de> <20110425004818.GA22579@icarus.home.lan> <4DB51F27.5010508@chillt.de> <20110425184728.C73992@sola.nimnet.asn.au> <4DB56CDA.50504@chillt.de> <20110425232429.N85801@sola.nimnet.asn.au> <4DB57F45.4080107@chillt.de> X-Mailer: Claws Mail 3.7.8 (GTK+ 2.22.1; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/+.hgdF/3VC6Owz_HAWncCzD"; protocol="application/pgp-signature" Subject: Re: System extremely slow under light load 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, 25 Apr 2011 15:02:07 -0000 --Sig_/+.hgdF/3VC6Owz_HAWncCzD Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable > > Sorry to hear none of that helped. It seems a very serious > > problem, and it would be useful to know if it behaves any better > > under linux or not. >=20 > I am still on the hunt for a bootable Linux distribution. I am in the=20 > unfortunate situation of having no CD-Rs at hand. And because it is=20 > Easter, shops are closed. >=20 > Most Linux distributions require you to run a proprietary tool from=20 > inside Windows or another Linux installation to create a bootable USB=20 > medium. I found a USB image for OpenSUSE but that failed to boot. I > am continuing to hunt... GRML ISOs (from grml.org) can be dd-ed directly to a USB stick and should then boot with any reasonable current BIOS. Regards Florian --Sig_/+.hgdF/3VC6Owz_HAWncCzD Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iEYEARECAAYFAk21jOwACgkQLvW/2gp2pPzHjgCeKZ9rkM1DGkhC0pEYnKcYpqoB FMkAn1n+2GgrQ0YI0an2tiL5LMGKcvVj =gSr3 -----END PGP SIGNATURE----- --Sig_/+.hgdF/3VC6Owz_HAWncCzD-- From owner-freebsd-stable@FreeBSD.ORG Mon Apr 25 15:13:37 2011 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 D29FE106566C for ; Mon, 25 Apr 2011 15:13:37 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id 809118FC0A for ; Mon, 25 Apr 2011 15:13:37 +0000 (UTC) Received: by qwc9 with SMTP id 9so1272036qwc.13 for ; Mon, 25 Apr 2011 08:13:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=ooTGIH1KIkxvtwE5FJhU6/Vx1y44Fa2WNjLUNXR9/Tk=; b=mwHtnrJBaBOQO28jjFcdf+U2NSL6kwhLzZBb95GxtexLsSqmPNIeGeYsaa0ZJAMnyj hSQEDbjqC8RFYbu7um+5dtR1zFGYGMQJsEPJc35hNgICoNSdc/gIdOfjNH2iiFoe85s9 pYeDgsnggcbczkZ0792XyxvUsdLceRTlbB4Uw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=LOhJZ+lKq80ezHGIw8I6Twuw6uTnGE4Ah+NLZjcLRJqfIq7QYyiP8LignCZQox6hTB XuXuIcwlK/sfYTXzguhfqUbKgO8Vv/w2nsXDLRYlj6mvxaiUme09PiDAs0BfCBejFjHI EvoSezhQMHwgtlvWlG6K8zLhJoutwOfxeLcQk= MIME-Version: 1.0 Received: by 10.224.187.203 with SMTP id cx11mr2701959qab.311.1303744416527; Mon, 25 Apr 2011 08:13:36 -0700 (PDT) Received: by 10.224.179.212 with HTTP; Mon, 25 Apr 2011 08:13:36 -0700 (PDT) In-Reply-To: <4DB58C0F.3020803@chillt.de> References: <4DA596D3.1090803@chillt.de> <4DB44DA3.5060509@chillt.de> <4DB4589B.2020909@ksu.ru> <4DB45D6C.20203@chillt.de> <20110424182456.9DD03589@server.theusgroup.com> <4DB46ED4.2010500@chillt.de> <20110425004818.GA22579@icarus.home.lan> <4DB51F27.5010508@chillt.de> <20110425184728.C73992@sola.nimnet.asn.au> <4DB56CDA.50504@chillt.de> <20110425232429.N85801@sola.nimnet.asn.au> <4DB57F45.4080107@chillt.de> <4DB58C0F.3020803@chillt.de> Date: Mon, 25 Apr 2011 11:13:36 -0400 Message-ID: From: Mehmet Erol Sanliturk To: Bartosz Fabianowski Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org, Ian Smith , Jeremy Chadwick , John Subject: Re: System extremely slow under light load 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, 25 Apr 2011 15:13:37 -0000 On Mon, Apr 25, 2011 at 10:58 AM, Bartosz Fabianowski wr= ote: > Please , see the site >> >> http://www.mandriva.com/en/linux/ >> > > Thanks for the link. It looks like this a USB with a preinstalled Mandriv= a > Linux on it that you have to buy for =E2=82=AC50 though. I am looking for= an image > that I can just download. > > - Bartosz > There are downloadable free USB files , also . At the right of the page , http://www.mandriva.com/en/flash/ click the link 2009 Rescue iso , which will lead to http://dl1.mandriva.com/flash/rescue/2009.0/ Perhaps they may be useful . Also you may see : http://www.archlinux.org/download/ All available images can be burned to a CD, mounted as an ISO file, or be directly written to a USB stick using a utility like `dd`. http://mir.archlinux.fr/iso/latest/ Thank you very much . Mehmet Erol Sanliturk From owner-freebsd-stable@FreeBSD.ORG Mon Apr 25 15:19:36 2011 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 808CC106566C for ; Mon, 25 Apr 2011 15:19:36 +0000 (UTC) (envelope-from freebsd@chillt.de) Received: from dd16434.kasserver.com (dd16434.kasserver.com [85.13.137.111]) by mx1.freebsd.org (Postfix) with ESMTP id 3B93A8FC08 for ; Mon, 25 Apr 2011 15:19:36 +0000 (UTC) Received: from taiko.lan (ppp-94-44.21-151.libero.it [151.21.44.94]) by dd16434.kasserver.com (Postfix) with ESMTPSA id 039B8188603F; Mon, 25 Apr 2011 17:19:34 +0200 (CEST) Message-ID: <4DB590D8.2000409@chillt.de> Date: Mon, 25 Apr 2011 17:18:48 +0200 From: Bartosz Fabianowski User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110309 Thunderbird/3.1.9 MIME-Version: 1.0 To: Mehmet Erol Sanliturk References: <4DA596D3.1090803@chillt.de> <4DB44DA3.5060509@chillt.de> <4DB4589B.2020909@ksu.ru> <4DB45D6C.20203@chillt.de> <20110424182456.9DD03589@server.theusgroup.com> <4DB46ED4.2010500@chillt.de> <20110425004818.GA22579@icarus.home.lan> <4DB51F27.5010508@chillt.de> <20110425184728.C73992@sola.nimnet.asn.au> <4DB56CDA.50504@chillt.de> <20110425232429.N85801@sola.nimnet.asn.au> <4DB57F45.4080107@chillt.de> <4DB58C0F.3020803@chillt.de> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Ian Smith , Jeremy Chadwick , John Subject: Re: System extremely slow under light load 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, 25 Apr 2011 15:19:36 -0000 > click the link 2009 Rescue iso , which will lead to > > http://dl1.mandriva.com/flash/rescue/2009.0/ Thanks. There is no mention anywhere on the page that the ISO files can be treated as USB boot images as well. Hence, I did not realize they would suit my needs. > Also you may see : > > http://www.archlinux.org/download/ I know ArchLinux ISO files are also bootable from USB. However, Arch provides no LiveCD, just a simple installer. That said, I find Arch to be an excellent distribution. It just does not fit my particular needs at the moment. - Bartosz From owner-freebsd-stable@FreeBSD.ORG Mon Apr 25 15:22:33 2011 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 71953106566C for ; Mon, 25 Apr 2011 15:22:33 +0000 (UTC) (envelope-from freebsd@chillt.de) Received: from dd16434.kasserver.com (dd16434.kasserver.com [85.13.137.111]) by mx1.freebsd.org (Postfix) with ESMTP id 306D18FC13 for ; Mon, 25 Apr 2011 15:22:32 +0000 (UTC) Received: from taiko.lan (ppp-94-44.21-151.libero.it [151.21.44.94]) by dd16434.kasserver.com (Postfix) with ESMTPSA id 29E98188603F; Mon, 25 Apr 2011 17:22:32 +0200 (CEST) Message-ID: <4DB59189.3080606@chillt.de> Date: Mon, 25 Apr 2011 17:21:45 +0200 From: Bartosz Fabianowski User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110309 Thunderbird/3.1.9 MIME-Version: 1.0 To: Florian Wagner References: <4DA596D3.1090803@chillt.de> <4DB44DA3.5060509@chillt.de> <4DB4589B.2020909@ksu.ru> <4DB45D6C.20203@chillt.de> <20110424182456.9DD03589@server.theusgroup.com> <4DB46ED4.2010500@chillt.de> <20110425004818.GA22579@icarus.home.lan> <4DB51F27.5010508@chillt.de> <20110425184728.C73992@sola.nimnet.asn.au> <4DB56CDA.50504@chillt.de> <20110425232429.N85801@sola.nimnet.asn.au> <4DB57F45.4080107@chillt.de> <20110425170204.72c064cd@naclador.mos32.de> In-Reply-To: <20110425170204.72c064cd@naclador.mos32.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: System extremely slow under light load 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, 25 Apr 2011 15:22:33 -0000 > GRML ISOs (from grml.org) can be dd-ed directly to a USB stick and > should then boot with any reasonable current BIOS. Thanks. It is great to see that so many ISOs can be dd-ed to USB keys. I wish the distributions would make it clearer which ISOs work as USB images and which do not. I am reluctant to download gigabytes of ISOs just to find that most do not work. - Bartosz From owner-freebsd-stable@FreeBSD.ORG Mon Apr 25 15:41:30 2011 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 68354106564A for ; Mon, 25 Apr 2011 15:41:30 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id 14A808FC0C for ; Mon, 25 Apr 2011 15:41:29 +0000 (UTC) Received: by qwc9 with SMTP id 9so1287678qwc.13 for ; Mon, 25 Apr 2011 08:41:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=Vy7dq8RUt9fFIQzkgJwxLyBEezNSY9m51XYVHBeCrmU=; b=N+uVhBj4aCMsPsetZbswmgSxRXMole0rsyxLWn6I4AZAV9rYKGCO+Lxn6auvOVAeb5 /m2jYMWoIiXq6bCAPKqmBlL00bdZzRaj8lcxQjLuRPznuc+rStKVmyr0BTjKeezV3MSh qUoR+OBXmZZ5RWU+FZexNoOTxzXfBMVjM6AQg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=I2g58trkoLQyf2jkJ3NECVbOlogIigxjyiUO+Pg2LWj9H3rrMHaGsqr/IxSAedl1Nw sHdxanCzyxoldmG+RCb4hwtMl0T7MBoxe34HPtGv+p7HZV9AilFa4hzKAjG70qGmZVev P57PMcmwNviEQB/i1EnRre7doDaSM8BE5Mdsw= MIME-Version: 1.0 Received: by 10.224.187.203 with SMTP id cx11mr2724952qab.311.1303746088628; Mon, 25 Apr 2011 08:41:28 -0700 (PDT) Received: by 10.224.179.212 with HTTP; Mon, 25 Apr 2011 08:41:28 -0700 (PDT) In-Reply-To: <4DB590D8.2000409@chillt.de> References: <4DA596D3.1090803@chillt.de> <4DB44DA3.5060509@chillt.de> <4DB4589B.2020909@ksu.ru> <4DB45D6C.20203@chillt.de> <20110424182456.9DD03589@server.theusgroup.com> <4DB46ED4.2010500@chillt.de> <20110425004818.GA22579@icarus.home.lan> <4DB51F27.5010508@chillt.de> <20110425184728.C73992@sola.nimnet.asn.au> <4DB56CDA.50504@chillt.de> <20110425232429.N85801@sola.nimnet.asn.au> <4DB57F45.4080107@chillt.de> <4DB58C0F.3020803@chillt.de> <4DB590D8.2000409@chillt.de> Date: Mon, 25 Apr 2011 11:41:28 -0400 Message-ID: From: Mehmet Erol Sanliturk To: Bartosz Fabianowski Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org, Ian Smith , Jeremy Chadwick , John Subject: Re: System extremely slow under light load 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, 25 Apr 2011 15:41:30 -0000 On Mon, Apr 25, 2011 at 11:18 AM, Bartosz Fabianowski wrote: > click the link 2009 Rescue iso , which will lead to >> >> http://dl1.mandriva.com/flash/rescue/2009.0/ >> > > Thanks. There is no mention anywhere on the page that the ISO files can be > treated as USB boot images as well. Hence, I did not realize they would suit > my needs. > > Also you may see : >> >> http://www.archlinux.org/download/ >> > > I know ArchLinux ISO files are also bootable from USB. However, Arch > provides no LiveCD, just a simple installer. That said, I find Arch to be an > excellent distribution. It just does not fit my particular needs at the > moment. > > - Bartosz > Please , see : http://cdimage.debian.org/debian-cd/6.0.1-live/amd64/ http://cdimage.debian.org/debian-cd/6.0.1-live/i386/ By using dd , you may copy a hybrid .iso to USB stick . If you have USB HDD , also there are HDD .iso images in there . Previously , I copied an arbitrary .iso ( I do not remember which OS ) to a USB stick with dd , and it booted , and installed very well . My idea was to make an experiment about whether an .iso can be booted if it is recorded by dd into a USB stick . It was successful . Thank you very much . Mehmet Erol Sanliturk From owner-freebsd-stable@FreeBSD.ORG Mon Apr 25 15:56:50 2011 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 1BECF1065673 for ; Mon, 25 Apr 2011 15:56:50 +0000 (UTC) (envelope-from oberman@es.net) Received: from mailgw.es.net (mail1.es.net [IPv6:2001:400:201:1::2]) by mx1.freebsd.org (Postfix) with ESMTP id 0606D8FC0A for ; Mon, 25 Apr 2011 15:56:50 +0000 (UTC) Received: from ptavv.es.net (ptavv.es.net [IPv6:2001:400:910::29]) by mailgw.es.net (8.14.3/8.14.3) with ESMTP id p3PFuk8d021423 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 25 Apr 2011 08:56:46 -0700 Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 26D5C1CC0F; Mon, 25 Apr 2011 08:56:46 -0700 (PDT) To: Ian Smith In-reply-to: Your message of "Mon, 25 Apr 2011 23:58:39 +1000." <20110425232429.N85801@sola.nimnet.asn.au> Date: Mon, 25 Apr 2011 08:56:46 -0700 From: "Kevin Oberman" Message-Id: <20110425155646.26D5C1CC0F@ptavv.es.net> Cc: Bartosz Fabianowski , freebsd-stable@freebsd.org, John , Jeremy Chadwick Subject: Re: System extremely slow under light load 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, 25 Apr 2011 15:56:50 -0000 > Date: Mon, 25 Apr 2011 23:58:39 +1000 (EST) > From: Ian Smith > Sender: owner-freebsd-stable@freebsd.org > > On Mon, 25 Apr 2011, Bartosz Fabianowski wrote: > [..] > > See above: Unfortunately, the machine did nor respond well at all. Instead, > > it is overheating even worse. > > Sorry to hear none of that helped. It seems a very serious problem, and > it would be useful to know if it behaves any better under linux or not. > > > > Try using C2. It helps more with some CPUs than others, but it's worth > > > a try for further reducing heat, especially at idle. Ie in rc.conf: > > > > > > performance_cx_lowest="C2" > > > economy_cx_lowest="C2" > > > > I have set dev.cpu.X.cx_lowest="C2" at run-time. If I understand correctly, > > this should achieve the same effect. The CPU does not seem to ever make it to > > C2 though, even after I enable it: > > > > %sysctl dev.cpu | grep cx_usage > > dev.cpu.0.cx_usage: 100.00% 0.00% last 270us > > dev.cpu.1.cx_usage: 100.00% 0.00% last 399us > > dev.cpu.2.cx_usage: 100.00% 0.00% last 403us > > dev.cpu.3.cx_usage: 100.00% 0.00% last 404us > > dev.cpu.4.cx_usage: 100.00% 0.00% last 323us > > dev.cpu.5.cx_usage: 100.00% 0.00% last 313us > > dev.cpu.6.cx_usage: 100.00% 0.00% last 174us > > dev.cpu.7.cx_usage: 100.00% 0.00% last 137us > > You need sysctl hw.acpi.cpu.cx_lowest="C2" instead .. that's what > /etc/rc.d/power_profile adjusts when you apply or remove power. > I doubt it's likely to help much given the scale of overheating. > > > > > dev.est.0.freq_settings: 1734/45000 1733/45000 1599/41741 1466/38582 > > > > 1333/35485 1199/32426 1066/29457 933/26552 > > > > > > With throttling disabled, those are what you should be left with for > > > dev.cpu.0.freq_levels. > > > > Yes, these are the frequencies I have available now. 1333 makes the machine > > idle around 85C, 1999 leads to 78-80C. > > That's pretty sad. Not sure what the first two differing by only 1MHz > means .. but I'm out of ideas, and my depth. As several have either discovered or pointed out, the dev.cpu.X.freq is telling you what FreeBSD is requesting, not what the CPU is actually doing. Particularly, if high temperatures cause TCC to kick in, this will not show up. IF you really want to monitor CPU temperature on an Intel CPU, use the coretemp kernel module. I use it on Intel systems that lack ACPI support for temperature monitoring. It uses a junction on the die, so it will be somewhat higher than the package temperature. TCC works by simply skipping 'n' out of 8 clock cycles. It really does not change the clock speed at all. Typically, only EST or the AMD equivalent actually does this. FreeBSD attempts to use TCC for power management, for which it was not intended. As has been repeatedly reported, it is of no use for this. I always recommend that it be turned off. But this has NO effect on its use for temperature management. So turning off TCC (or p4tcc, as it is called on FreeBSD) does nothing. TCC will automatically skip cycles when the _PSV temperature is exceeded. On some CPUs, this can be VERY high. My old Pentium-M ThinkPad starts throttling at 95C and will shut down at 99C. Compared to desktop systems, this is REALLY high, but the output you posted shows yours at 100C! I would assume that means that TCC should kick in at about 95 or 96C which does not entirely explain what you are seeing. Unfortunately, your system does not provide a value for _PSV, so I have no idea when it will actually kick in, but it should be in the data sheet for the CPU. If ACPI does not hange it, it runs in a purely automated fashion with no human intervention available. I wish I could provide some easy way to detect when it kicks in, but I don't think there is one. You can force it while monitoring performance. Try running md5 or sha256 on a bunch of random (/dev/random) data. Collect the time it takes to do a bunch of these and you will see it increase by .125 every time throttling adds another step to the pause time. It will be fairly dramatic and very close to steps of exactly .125 of the original time. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 From owner-freebsd-stable@FreeBSD.ORG Mon Apr 25 16:11:46 2011 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 225A51065673 for ; Mon, 25 Apr 2011 16:11:46 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id D4C1F8FC08 for ; Mon, 25 Apr 2011 16:11:45 +0000 (UTC) Received: by qwc9 with SMTP id 9so1304028qwc.13 for ; Mon, 25 Apr 2011 09:11:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=DyNzp/wuLaxHOq7H1B599Trt+GyEpVNOWBL5+sLsxdw=; b=hXs5NfxqtOaHebMO7bxWfwor9rv5iqQJ6fNqJoyvrsCICFJRSpiGXTT2JyvQnzqu4S ABALxE61aQ3s/hX/JWwt8xLlQw9qqUosAsqKXLlXDW279HqGo/3RqWgEDt8JJgryXwXw lDQiJmR3N0JQVZjkWvrwfrDRATWQBkvnTt+VE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=UzGMn+zAJHKDCpseHmw6zzDPcx7xcmF/tlreV04+/yJIoKjb0GDFsCEu8urN3n5gXj IKL2tIwDUwHza/iOZTel/0haaoEnUYiMhrE0bhlbbYU9aq+xOK1MJffD6ilMRiJtjKyq 6FbJV+M6yZAesgAO4DQCinEGcaipqBw5RJnTE= MIME-Version: 1.0 Received: by 10.224.189.9 with SMTP id dc9mr2972458qab.11.1303747905034; Mon, 25 Apr 2011 09:11:45 -0700 (PDT) Received: by 10.224.179.212 with HTTP; Mon, 25 Apr 2011 09:11:45 -0700 (PDT) Date: Mon, 25 Apr 2011 12:11:45 -0400 Message-ID: From: Mehmet Erol Sanliturk To: freebsd-stable Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: System extremely slow under light load 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, 25 Apr 2011 16:11:46 -0000 I have read all of the messages in succession . No one of the messages are mentioning which software is running . Please see my message as http://lists.freebsd.org/pipermail/freebsd-stable/2011-February/061672.html Please read that message and compare with your case . The above message is went as unnoticed , although the same problem is still valid in FreeBSD 9.0 Current amd64 snapshots by Nathan Whitehorn and PC-BSD 8.2 and 9.0 Current amd64 snapshots . The reason of slowness is as follows : I have started x by startx , then started KDE by startkde in xterm . The reason of slowness is the generated endless amount of error messages . The GNOME is also generating endless amount of error messages displayed on the xterm terminal when it is started from xterm after starting X . When KDE or GNOME is started by the .xinitrc or rc.conf , those messages are NOT seen , but it is exposing itself as a very slow execution steps . During generation of those messages , CPU and other fans fan are becoming crazy . I did not test i386 snapshots . Thank you very much . Mehmet Erol Sanliturk From owner-freebsd-stable@FreeBSD.ORG Mon Apr 25 18:36:32 2011 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 80D461065673 for ; Mon, 25 Apr 2011 18:36:32 +0000 (UTC) (envelope-from cliftonr@oz.volcano.org) Received: from hrndva-omtalb.mail.rr.com (hrndva-omtalb.mail.rr.com [71.74.56.124]) by mx1.freebsd.org (Postfix) with ESMTP id 32E4A8FC08 for ; Mon, 25 Apr 2011 18:36:31 +0000 (UTC) Received: from hrndva-omtalb.mail.rr.com ([10.128.143.53]) by hrndva-qmta02.mail.rr.com with ESMTP id <20110425182455833.QPBI5185@hrndva-qmta02.mail.rr.com> for ; Mon, 25 Apr 2011 18:24:55 +0000 X-Authority-Analysis: v=1.1 cv=ZtuXOl23UuD1yoJUTgnZ6i6Z5VPlPhPMWCeUNtN8OGA= c=1 sm=0 a=z1TLwsU0kBEA:10 a=LJtIfV2HitoA:10 a=TgPToyY2OQsA:10 a=kj9zAlcOel0A:10 a=G5OLwwqwWgs+1dCEPNHTSw==:17 a=jb__rZ8GAAAA:8 a=GjEiR67sAAAA:8 a=ZqC2Wjb_awFvmOtpNZkA:9 a=CjuIK1q_8ugA:10 a=sHp_62vNEjwA:10 a=Ke08FT2oSu0A:10 a=G5OLwwqwWgs+1dCEPNHTSw==:117 X-Cloudmark-Score: 0 X-Originating-IP: 75.80.196.236 Received: from [75.80.196.236] ([75.80.196.236:12066] helo=oz.volcano.org) by hrndva-oedge03.mail.rr.com (envelope-from ) (ecelerity 2.2.3.46 r()) with ESMTP id 8A/80-22479-93CB5BD4; Mon, 25 Apr 2011 18:23:54 +0000 Received: by oz.volcano.org (Postfix, from userid 1001) id A80505082C; Mon, 25 Apr 2011 08:23:52 -1000 (HST) Date: Mon, 25 Apr 2011 08:23:52 -1000 From: Clifton Royston To: Bartosz Fabianowski Message-ID: <20110425182352.GA6768@lava.net> Mail-Followup-To: Bartosz Fabianowski , Ian Smith , freebsd-stable@freebsd.org, John , Jeremy Chadwick References: <4DB44DA3.5060509@chillt.de> <4DB4589B.2020909@ksu.ru> <4DB45D6C.20203@chillt.de> <20110424182456.9DD03589@server.theusgroup.com> <4DB46ED4.2010500@chillt.de> <20110425004818.GA22579@icarus.home.lan> <4DB51F27.5010508@chillt.de> <20110425184728.C73992@sola.nimnet.asn.au> <4DB56CDA.50504@chillt.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4DB56CDA.50504@chillt.de> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org, Ian Smith , Jeremy Chadwick , John Subject: Re: System extremely slow under light load 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, 25 Apr 2011 18:36:32 -0000 On Mon, Apr 25, 2011 at 02:45:14PM +0200, Bartosz Fabianowski wrote: > >dev.cpu.X.freq does reflect the current frequency; I don't know whether > >or how any internal clock throttling might be exposed. > > From what I have seen, dev.cpu.X.freq always retains the value I set it > to. Internal CPU throttling does not seem to be reported this way. ... > I just tried this on my current Dell Studio 1558, with devastating > results. The first boot attempt ended with the machine shutting down due > to overheating while loading the kernel. I let it cool down a bit and > then booted again. This time, I got to my desktop - with a CPU > temperature of 95??C. If the DSDT was fixed, the machine would have shut > down at this point. I could be wrong, but in my experience this really sounds like it is a hardware problem with the cooling system, and a very serious one at that. I would encourage you to take this up with Dell at once. While it's certainly possible that newer FreeBSD releases are failing to control the temperature as well as older ones due to some change, that does not mean that this is a FreeBSD problem - these temperatures are so far out of line that anything FreeBSD managed to do before should be viewed as an unexpectedly successful workaround. The only way I can see the core problem as OS-related is if the hardware design is relying on Windows-specific drivers to control the cooling system, which would be crazy though not impossible. ... > Yes, these are the frequencies I have available now. 1333 makes the > machine idle around 85??C, 1999 leads to 78-80??C. Apart from your immediate problems, in my past experience this range of CPU temperatures is likely to lead to early failure of the CPU, very likely within a year or less. -- Clifton -- Clifton Royston -- cliftonr@iandicomputing.com / cliftonr@volcano.org President - I and I Computing * http://www.iandicomputing.com/ Custom programming, network design, systems and network consulting services From owner-freebsd-stable@FreeBSD.ORG Mon Apr 25 18:46:56 2011 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 23190106564A; Mon, 25 Apr 2011 18:46:56 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id CCA8D8FC08; Mon, 25 Apr 2011 18:46:55 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 53B6F46B42; Mon, 25 Apr 2011 14:46:55 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id D2DF68A027; Mon, 25 Apr 2011 14:46:54 -0400 (EDT) From: John Baldwin To: freebsd-stable@freebsd.org Date: Mon, 25 Apr 2011 14:42:49 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110325; KDE/4.5.5; amd64; ; ) References: <4D9EEDAF.3020803@rulez.sk> <20110413024230.Y35056@sola.nimnet.asn.au> <20110420164100.Y43371@sola.nimnet.asn.au> In-Reply-To: <20110420164100.Y43371@sola.nimnet.asn.au> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201104251442.49926.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Mon, 25 Apr 2011 14:46:54 -0400 (EDT) Cc: Daniel Gerzo , Alexander Motin , Ian Smith Subject: Re: kern.smp.maxid error on i386 UP [was: powerd / cpufreq question] 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, 25 Apr 2011 18:46:56 -0000 On Wednesday, April 20, 2011 1:02:09 pm Ian Smith wrote: > On Wed, 13 Apr 2011, Ian Smith wrote: > > On Tue, 12 Apr 2011, Daniel Gerzo wrote: > > > On 11.4.2011 6:08, Ian Smith wrote: > [..] > > > > Are those kern.cp_times values as they came, or did you remove trailing > > > > zeroes? Reason I ask is that on my Thinkpad T23, single-core 1133/733 > > > > MHz, sysctl kern.cp_time shows the usual 5 values, but kern.cp_times has > > > > the same 5 values for cpu0, but then 5 zeroes for each of cpu1 through > > > > cpu31, on 8.2-PRE about early January. I need to update the script to > > > > remove surplus data for non-existing cpus, but wonder if the extra data > > > > also appeared on your 12 core box? > > > > > > I haven't removed anything, it's a pure copy&paste. > > > > Thanks. I'll check the single-cpu case again after updating to 8.2-R > > Ok, still a problem on at least my i386 single core Thinkpad T23 at > 8.2-R, since 8.0 I think, certainly evident in a sysctl -a at 8.1-R > > FreeBSD t23.smithi.id.au 8.2-RELEASE FreeBSD 8.2-RELEASE #1: Thu Apr 14 > 21:45:47 EST 2011 root@t23.smithi.id.au:/usr/obj/usr/src/sys/GENERIC i386 > > Verbose dmesg: http://smithi.id.au/t23_dmesg_boot-v.8.2-R.txt > sysctl -a: http://smithi.id.au/t23_sysctl-a_8.2-R.txt > > kern.ccpu: 0 > 0 > kern.smp.forward_signal_enabled: 1 > kern.smp.topology: 0 > kern.smp.cpus: 1 > kern.smp.disabled: 0 > kern.smp.active: 0 > kern.smp.maxcpus: 32 > kern.smp.maxid: 31 <<<<<<< > hw.ncpu: 1 > > kern.cp_times: 38548 1 120437 195677 9660939 0 0 0 0 0 0 0 0 0 0 0 0 0 0 > 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 > 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 > 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 > 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 > > /usr/src/sys/kern/kern_clock.c: > return SYSCTL_OUT(req, 0, sizeof(long) * CPUSTATES * (mp_maxid + 1)); > > Consumers of kern.cp_times like powerd, top, dtrace? and others have to > loop over 32 cpus, all but one non-existent, and there seem to be many > places in the kernel doing eg: for (cpu = 0; cpu <= mp_maxid; cpu++) { > and while CPU_FOREACH / CPU_ABSENT will skip over them, seems wasteful > at best on machines least likely to have cycles to spare. > > eg: powerd parses kern.cp_times to count cpus, wasting cycles adding > up the 31 'empty' cpus. I haven't explored other userland consumers. > > Clearly kern.smp.maxid (ie mp_maxid) should be 0, not 31. On i386, > non-APIC i386 at least, mp_maxid is not set to (mp_ncpus - 1) as on some > other archs .. after having being initialised to (MAXCPU - 1) in > /sys/i386/i386/mp_machdep.c it's never updated for non-smp machines. No, and your patch would break many things. The existence of mp_maxid is to allow very early kernel startup to know the largest possible CPU ID it has to contend with. Specifically, this is used by UMA to size an array of per-CPU bucket lists in UMA zones. However, this must be done before SI_SUB_KLD. The i386 platform in 8.x and earlier cannot enumerate CPUs until after SI_SUB_KLD in order to support having ACPI in a kernel module (as acpi.ko). For that reason, i386 cannot set mp_maxid optimally. Note that the only guarantee made with regards to mp_maxid is that all CPU IDs for all active CPUs in the system will be <= mp_maxid. There is no guarantee of denseness of CPU IDs (there can be holes), or even that the CPUs start at 0 (ACPI does require the BSP to be CPU 0 in its shutdown code, but that requirement only applies to x86 and ia64). -- John Baldwin From owner-freebsd-stable@FreeBSD.ORG Mon Apr 25 21:27:56 2011 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 36296106564A for ; Mon, 25 Apr 2011 21:27:56 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 0A8268FC13 for ; Mon, 25 Apr 2011 21:27:56 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id B0BCD46B98; Mon, 25 Apr 2011 17:27:55 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 3EA308A01B; Mon, 25 Apr 2011 17:27:55 -0400 (EDT) From: John Baldwin To: Przemyslaw Frasunek Date: Mon, 25 Apr 2011 16:04:04 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110325; KDE/4.5.5; amd64; ; ) References: <4DA4A96F.9000507@frasunek.com> <201104181430.13886.jhb@freebsd.org> <4DAE153E.1010405@frasunek.com> In-Reply-To: <4DAE153E.1010405@frasunek.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201104251604.04784.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Mon, 25 Apr 2011 17:27:55 -0400 (EDT) Cc: freebsd-stable@freebsd.org Subject: Re: Missing serial port after enabling serial console in loader.conf 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, 25 Apr 2011 21:27:56 -0000 On Tuesday, April 19, 2011 7:05:34 pm Przemyslaw Frasunek wrote: > > The _STA method is used to query a device's status, and a status of 0 means > > that the device is disabled. I believe that this means that when you have > > SOL enabled (SOLE?) that COM1 is marked inactive so the OS ignores the device. > > Good catch, thanks! I had a feeling, that it must be caused by firmware. Is > there any way to override above checks and make SIO detectable even with enabled > SOL? I don't think so. You can try swapping the hints for sio0 and sio1 and seeing if sio1 suddenly shows up as working and valid. If so, then the changes in 8 to bind unit numbers using hints might work for you to get COM1 back as sio0. -- John Baldwin From owner-freebsd-stable@FreeBSD.ORG Mon Apr 25 21:38:32 2011 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 C5002106566B; Mon, 25 Apr 2011 21:38:32 +0000 (UTC) (envelope-from przemyslaw@frasunek.com) Received: from lagoon.freebsd.lublin.pl (lagoon.freebsd.lublin.pl [IPv6:2a02:2928:a::3]) by mx1.freebsd.org (Postfix) with ESMTP id 5023C8FC0C; Mon, 25 Apr 2011 21:38:32 +0000 (UTC) Received: from [IPv6:2a02:2928:a:ffff:9cc2:4f3b:f287:78a0] (unknown [IPv6:2a02:2928:a:ffff:9cc2:4f3b:f287:78a0]) by lagoon.freebsd.lublin.pl (Postfix) with ESMTPSA id 7434823944E; Mon, 25 Apr 2011 23:38:30 +0200 (CEST) Message-ID: <4DB5E9D6.3040203@frasunek.com> Date: Mon, 25 Apr 2011 23:38:30 +0200 From: Przemyslaw Frasunek Organization: frasunek.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; pl; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9 MIME-Version: 1.0 To: John Baldwin References: <4DA4A96F.9000507@frasunek.com> <201104181430.13886.jhb@freebsd.org> <4DAE153E.1010405@frasunek.com> <201104251604.04784.jhb@freebsd.org> In-Reply-To: <201104251604.04784.jhb@freebsd.org> X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: Missing serial port after enabling serial console in loader.conf 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, 25 Apr 2011 21:38:32 -0000 > I don't think so. You can try swapping the hints for sio0 and sio1 and seeing if > sio1 suddenly shows up as working and valid. If so, then the changes in 8 to bind > unit numbers using hints might work for you to get COM1 back as sio0. Few days ago I decided to upgrade to 8.2-STABLE, partially due to some long-standing Netgraph issues (which I discussed on freebsd-net). To my surprise, sio0 (well, now uart0) had become detectable even in spite of enabled SOL: uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 uart0: [FILTER] uart0: console (9600,n,8,1) uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0 uart1: [FILTER] Eventually I'm able to use comconsole in loader.conf and getty simultaneously. BTW. I looked at the BIOS setup on my box - it has "Legacy OS" knob, allowing to hide serial port occupied by SOL from non ACPI aware OS. It was disabled for all the time, so my problem was probably related to sio(4) and fixed in uart(4). -- * Fido: 2:480/124 ** WWW: http://www.frasunek.com ** NICHDL: PMF9-RIPE * * Jabber ID: venglin@nette.pl ** PGP ID: 2578FCAD ** HAM-RADIO: SQ5JIV * From owner-freebsd-stable@FreeBSD.ORG Mon Apr 25 21:41:20 2011 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 721BC106564A for ; Mon, 25 Apr 2011 21:41:20 +0000 (UTC) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from thalia-smout.broadpark.no (thalia-smout.broadpark.no [80.202.8.21]) by mx1.freebsd.org (Postfix) with ESMTP id 2778A8FC19 for ; Mon, 25 Apr 2011 21:41:19 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from terra-smin.broadpark.no ([80.202.8.13]) by thalia-smout.broadpark.no (Sun Java(tm) System Messaging Server 7u3-15.01 64bit (built Feb 12 2010)) with ESMTP id <0LK8000VX9KUJD10@thalia-smout.broadpark.no> for freebsd-stable@freebsd.org; Mon, 25 Apr 2011 23:41:18 +0200 (CEST) Received: from kg-v2.kg4.no ([84.48.120.215]) by terra-smin.broadpark.no (Sun Java(tm) System Messaging Server 7u3-15.01 64bit (built Feb 12 2010)) with SMTP id <0LK800LCC9KT9B80@terra-smin.broadpark.no> for freebsd-stable@freebsd.org; Mon, 25 Apr 2011 23:41:18 +0200 (CEST) Date: Mon, 25 Apr 2011 23:41:17 +0200 From: Torfinn Ingolfsen To: freebsd-stable@freebsd.org Message-id: <20110425234117.d1476c95.torfinn.ingolfsen@broadpark.no> In-reply-to: <4DB583E9.8080507@chillt.de> References: <4DB4589B.2020909@ksu.ru> <4DB45D6C.20203@chillt.de> <20110424182456.9DD03589@server.theusgroup.com> <4DB46ED4.2010500@chillt.de> <20110425004818.GA22579@icarus.home.lan> <4DB51F27.5010508@chillt.de> <20110425184728.C73992@sola.nimnet.asn.au> <4DB56CDA.50504@chillt.de> <20110425232429.N85801@sola.nimnet.asn.au> <4DB57F45.4080107@chillt.de> <20110425141643.GA38380@icarus.home.lan> <4DB583E9.8080507@chillt.de> X-Mailer: Sylpheed 3.1.0 (GTK+ 2.22.1; amd64-portbld-freebsd8.1) 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: System extremely slow under light load 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, 25 Apr 2011 21:41:20 -0000 On Mon, 25 Apr 2011 16:23:37 +0200 Bartosz Fabianowski wrote: > > Try Knoppix, or Ubuntu LiveCD. I tend to use the former for rescue > > situations: > > Thanks. I am aware of both - but neither boots from USB (and I have no > CD-Rs at hand). I am running UNetbootin under Windows XP in VirtualBox > right now to try and get Xubuntu 10.04 onto a USB key. It is really sad > that almost all Linux distributions require this detour via a > proprietary operating system. Have you tried just using dd to copy the iso image of a Ubuntu / Linux LiveCD to a suitably sized USB memory stick? It has worked for me in the past. YMMV. -- Torfinn From owner-freebsd-stable@FreeBSD.ORG Mon Apr 25 21:51:12 2011 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 C7C65106564A for ; Mon, 25 Apr 2011 21:51:12 +0000 (UTC) (envelope-from bsd.gaijin@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 8CDA68FC18 for ; Mon, 25 Apr 2011 21:51:12 +0000 (UTC) Received: by iwn33 with SMTP id 33so50846iwn.13 for ; Mon, 25 Apr 2011 14:51:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=xoq/8pIbNKcBoTKJjV993YPL8Xf6wyA6C7WQUR/Kscc=; b=T0Qt2C9j1aWH+OTlB7P6Vv+/rVEKAh/xMVUwgFrfa8PhF94Dc08YU1W3pLkTrnO/Tu OsDVAAKWixusXaaqK5hkqGLRxTT5dSMjrYISDXOGT4s8EeTin8C8suiUtho92a++H6uC q+1WB/W3gHfrjkwrcnhhA2nbpy+0CkEWv9b+c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=blJg94rzo0YDXsq6A+zm52WWJCgIrcxTRnzJ0c21rdPS7sxyXUJYMjKWp5pC+FdHQW mI0LQ0MBtojGCJ6W3uZx7SWj5hf0kas+9fPXY1GMT2WqywUQiBajTOe92rPlEZEfs3uL YFzZD3TndJ261jgRLnHxep155N0Qf+Q7IbNbw= MIME-Version: 1.0 Received: by 10.42.19.136 with SMTP id c8mr5598791icb.290.1303768272012; Mon, 25 Apr 2011 14:51:12 -0700 (PDT) Received: by 10.42.225.200 with HTTP; Mon, 25 Apr 2011 14:51:11 -0700 (PDT) In-Reply-To: <4DB5751B.2050903@chillt.de> References: <4DB5751B.2050903@chillt.de> Date: Mon, 25 Apr 2011 17:51:11 -0400 Message-ID: From: Alexandre Kovalenko To: Bartosz Fabianowski Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org Subject: Re: System extremely slow under light load 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, 25 Apr 2011 21:51:12 -0000 On Mon, Apr 25, 2011 at 9:20 AM, Bartosz Fabianowski wr= ote: >> >> I am not sure tz0 is the real thermal zone, especially given values >> of _tc1, _tc2 and _tsp. Temperature value (3001) =A0looks suspicious as >> well. > > I agree. tz0 looks entirely bogus. There is no second fan to control for = it and I have no idea what it is supposed to be monitoring. > >> Can you, by any chance, put your ASL someplace accessible and provide >> a description of what you have done to fix the temperature >> reporting. > > Certainly. I have uploaded the files at [1] through [5]. > > The DSDT source returned by acpidump -d is at [1]. I modified this so tha= t it can be compiled back into AML without errors or warnings. This modifie= d source is at [2]. It contains no functional changes. The thermal zones ar= e still broken. A variant with fixed tz1 is at [3]. > > For convenience, I have also uploaded diffs between these source files. [= 4] is the diff required to make the source compile (difference between [1] = and [2]). [5] is the actual change I made to fix tz1 (difference between [2= ] and [3]). As you can see, all I did was to remove a bogus function that e= nds up always returning 0=B0C. > >> As the side note: I have seen and do own pieces of equipment that >> use thermal zones to initiate critical shutdown for various and >> unrelated reasons. > > In my case, the thermal zone and its various tripping points do correspon= d to the actual system fan. It is just that the BIOS enforces power managem= ent itself, ignoring ACPI - except for critical shutdown which appears to b= e triggered by ACPI only. Did you try to set OS override to any of the values, recognized by your BIOS, with most interesting being=A0 "Windows 2001 SP2", "Windows 2006" and "Windows 2009". There is no obvious impact on the thermal part per se, but at least some of values seem to change the timer configuration. You can change your OS name by setting hw.acpi.osname=3D in /boot/loader.conf (http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/acpi-debug.html)= . Additionally, could you, by any chance, replace _TMP method in TZ01 with the snippet below and let me know what the result is: =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Method (_TMP, 0, Serialized) =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 { =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 If (LEqual (\_SB.PCI0.LPCB.EC= 0.EIDL, 0xDD)) =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 { =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Return (0x0BB8) =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 } =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 If (LAnd (DTSE, ETMD)) =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 { =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 If (LGreater (\_S= B.PCI0.LPCB.EC0.DTS2, \_SB.PCI0.LPCB.EC0.DTS1)) =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 { =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Store= (\_SB.PCI0.LPCB.EC0.DTS2, Local0) =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 } =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Else =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 { =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Store= (\_SB.PCI0.LPCB.EC0.DTS1, Local0) =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 } =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Return (Add (0x0A= AC, Multiply (Local0, 0x0A))) =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 } =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 If (LAnd (ECON, ETMD)) =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 { =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Acquire (\_SB.PCI= 0.LPCB.EC0.MUT0, 0xFFFF) =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Store (\_SB.PCI0.= LPCB.EC0.DTS1, Local0) =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Release (\_SB.PCI= 0.LPCB.EC0.MUT0) =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 If (And (Local0, = 0x80)) =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 { =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Subtr= act (Local0, 0x0100, Local0) =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 } =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Return (Add (0x0A= AC, Multiply (Local0, 0x0A))) =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 } =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Return (0x0BB8) =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 } I assume, since you have already modified your ASL, you do realize all of the pitfalls of this activity, including but not limited to turning your laptop into molten blob of plastic ;) > > - Bartosz > > [1] http://www.fabianowski.de/dsdt/decompiled.asl > [2] http://www.fabianowski.de/dsdt/compilable.asl > [3] http://www.fabianowski.de/dsdt/fixed.asl > [4] http://www.fabianowski.de/dsdt/decompile_compilable.diff > [5] http://www.fabianowski.de/dsdt/compilable_fixed.diff > _______________________________________________ > 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 Mon Apr 25 23:03:04 2011 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 00A76106566B for ; Mon, 25 Apr 2011 23:03:04 +0000 (UTC) (envelope-from freebsd@chillt.de) Received: from dd16434.kasserver.com (dd16434.kasserver.com [85.13.137.111]) by mx1.freebsd.org (Postfix) with ESMTP id 8BCE18FC08 for ; Mon, 25 Apr 2011 23:03:03 +0000 (UTC) Received: from taiko.lan (ppp-197-43.21-151.libero.it [151.21.43.197]) by dd16434.kasserver.com (Postfix) with ESMTPSA id 600B4188606E; Tue, 26 Apr 2011 01:03:01 +0200 (CEST) Message-ID: <4DB5FD74.6060601@chillt.de> Date: Tue, 26 Apr 2011 01:02:12 +0200 From: Bartosz Fabianowski User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110309 Thunderbird/3.1.9 MIME-Version: 1.0 To: Jeremy Chadwick References: <4DA596D3.1090803@chillt.de> <4DB44DA3.5060509@chillt.de> <4DB4589B.2020909@ksu.ru> <4DB45D6C.20203@chillt.de> <20110424182456.9DD03589@server.theusgroup.com> <4DB46ED4.2010500@chillt.de> <20110425004818.GA22579@icarus.home.lan> In-Reply-To: <20110425004818.GA22579@icarus.home.lan> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-stable@freebsd.org, John Subject: Re: System extremely slow under light load 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, 25 Apr 2011 23:03:04 -0000 > If you boot into another operating system such as Linux or Windows, do > you see the same overall behaviour? Linux might be easier and might > have some built-in way to get at CPU temperatures (via /proc?). I finally found a working USB Linux image and have run some tests: Linux power management is quite different from FreeBSD. It clocks all cores at 933 MHz by default. When I start exercising the CPU, only the cores actually working hard get clocked up all the way to 1.7 GHz. This seems like a good idea but is not possible on FreeBSD right now as the only frequency sysctl is dev.cpu.0.freq. With the CPU idling at 933 MHz, the temperature is about 68°C. I am running FreeBSD with powerd -M 933 right now and the CPU is idling at 76°C while being clocked down to about 200 MHz most of the time. So Linux does something better here and manages to shave off about 10°C. As recommended by Kevin, I tried running md5 on a large chunk of data. I chose a Linux ISO file instead of /dev/random output to have reproducible input. Under FreeBSD, the machine currently is not sluggish and an md5 run completes in 5.7 seconds. I will retry the md5 experiment when the box becomes sluggish and will see whether I can detect TCC kicking in. Under Linux, the same md5 run took 12.6 seconds. This is surprising on the one hand as Linux clocked up all the way to 1.7 GHz while under FreeBSD, I was limiting the CPU to 1.199 GHz. On the other hand, Linux was running from a USB key while FreeBSD is properly installed. I tried running multiple copies of md5 in parallel to exercise multiple cores to the maximum under Linux. This actually made the temperature climb very quickly up to 95°-98°C. At 95°C, the fan audibly switched into a higher gear. I now remember that I have heard this under FreeBSD before as well. The fan seems to be controlled by the BIOS after all so when the CPU reaches 95°C, the BIOS turns up the fan, irrespective of the OS I am running. The great difference between FreeBSD and Linux was that I did not get any of the sluggishness and non-interactive response. Even under high load with a CPU temperature of 95°C and the fan in high gear, KDE was responsive and usable. I did have a few system stalls but according to the console, those were due to problems with reading from the USB key. There seemed to be no sudden breakdown of interactive performance even under load and thermal stress. So something is off under FreeBSD... - Bartosz From owner-freebsd-stable@FreeBSD.ORG Mon Apr 25 23:04:09 2011 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 260A41065670 for ; Mon, 25 Apr 2011 23:04:09 +0000 (UTC) (envelope-from freebsd@chillt.de) Received: from dd16434.kasserver.com (dd16434.kasserver.com [85.13.137.111]) by mx1.freebsd.org (Postfix) with ESMTP id D3B1D8FC0C for ; Mon, 25 Apr 2011 23:04:08 +0000 (UTC) Received: from taiko.lan (ppp-197-43.21-151.libero.it [151.21.43.197]) by dd16434.kasserver.com (Postfix) with ESMTPSA id DA53F188606E; Tue, 26 Apr 2011 01:04:06 +0200 (CEST) Message-ID: <4DB5FDB5.5020102@chillt.de> Date: Tue, 26 Apr 2011 01:03:17 +0200 From: Bartosz Fabianowski User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110309 Thunderbird/3.1.9 MIME-Version: 1.0 To: Mehmet Erol Sanliturk References: <4DA596D3.1090803@chillt.de> <4DB44DA3.5060509@chillt.de> <4DB4589B.2020909@ksu.ru> <4DB45D6C.20203@chillt.de> <20110424182456.9DD03589@server.theusgroup.com> <4DB46ED4.2010500@chillt.de> <20110425004818.GA22579@icarus.home.lan> <4DB51F27.5010508@chillt.de> <20110425184728.C73992@sola.nimnet.asn.au> <4DB56CDA.50504@chillt.de> <20110425232429.N85801@sola.nimnet.asn.au> <4DB57F45.4080107@chillt.de> <4DB58C0F.3020803@chillt.de> <4DB590D8.2000409@chillt.de> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Ian Smith , Jeremy Chadwick , John Subject: Re: System extremely slow under light load 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, 25 Apr 2011 23:04:09 -0000 > Please , see : > > http://cdimage.debian.org/debian-cd/6.0.1-live/amd64/ > http://cdimage.debian.org/debian-cd/6.0.1-live/i386/ > > By using dd , you may copy a hybrid .iso to USB stick . Thanks. I downloaded the amd64 image. It booted perfectly after copying to a USB key via dd. - Bartosz From owner-freebsd-stable@FreeBSD.ORG Mon Apr 25 23:19:54 2011 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 71EEC106564A for ; Mon, 25 Apr 2011 23:19:54 +0000 (UTC) (envelope-from freebsd@chillt.de) Received: from dd16434.kasserver.com (dd16434.kasserver.com [85.13.137.111]) by mx1.freebsd.org (Postfix) with ESMTP id 0C4598FC0A for ; Mon, 25 Apr 2011 23:19:53 +0000 (UTC) Received: from taiko.lan (ppp-197-43.21-151.libero.it [151.21.43.197]) by dd16434.kasserver.com (Postfix) with ESMTPSA id 6F791188606E; Tue, 26 Apr 2011 01:19:52 +0200 (CEST) Message-ID: <4DB60167.3090207@chillt.de> Date: Tue, 26 Apr 2011 01:19:03 +0200 From: Bartosz Fabianowski User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110309 Thunderbird/3.1.9 MIME-Version: 1.0 To: Kevin Oberman References: <20110425155646.26D5C1CC0F@ptavv.es.net> In-Reply-To: <20110425155646.26D5C1CC0F@ptavv.es.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-stable@freebsd.org, Ian Smith , Jeremy Chadwick , John Subject: Re: System extremely slow under light load 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, 25 Apr 2011 23:19:54 -0000 > As several have either discovered or pointed out, the dev.cpu.X.freq is > telling you what FreeBSD is requesting, not what the CPU is actually > doing. Particularly, if high temperatures cause TCC to kick in, this > will not show up. Yes, this is what I thought as well. > IF you really want to monitor CPU temperature on an Intel CPU, use the > coretemp kernel module. I use it on Intel systems that lack ACPI support > for temperature monitoring. It uses a junction on the die, so it will be > somewhat higher than the package temperature. Yes, I am using that module and monitoring the dev.cpu.X.temperature output. Technically, my system has support for ACPI monitoring but as I mentioned in earlier messages, the DSDT provided by Dell is broken. > I would assume that means that TCC should kick in at about 95 or 96C > which does not entirely explain what you are seeing. Unfortunately, your > system does not provide a value for _PSV, so I have no idea when it will > actually kick in, but it should be in the data sheet for the CPU. If > ACPI does not hange it, it runs in a purely automated fashion with no > human intervention available. I downloaded and read the specs. If I understand them correctly, the maximal junction temperature for this CPU is 100°C. TCC should kick in when any of the cores exceeds this value. It is unclear to me when exactly TCC deactivates again but if the diagrams in the documentation are drawn to scale, a pretty wide hysteresis is involved. So one explanation for what I am seeing may be this: One of the cores, for a split second, jumps over 100°C. TCC kicks in and does not turn off for a long while. During that time, the system feels sluggish and slow. > Try running md5 or sha256 on a bunch of random (/dev/random) data. > Collect the time it takes to do a bunch of these and you will see it > increase by .125 every time throttling adds another step to the pause > time. It will be fairly dramatic and very close to steps of exactly .125 > of the original time. Thanks, I will be using that to try and determine whether it really is TCC that makes my machine sluggish under load. - Bartosz From owner-freebsd-stable@FreeBSD.ORG Mon Apr 25 23:23:17 2011 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 F1481106566B for ; Mon, 25 Apr 2011 23:23:17 +0000 (UTC) (envelope-from freebsd@chillt.de) Received: from dd16434.kasserver.com (dd16434.kasserver.com [85.13.137.111]) by mx1.freebsd.org (Postfix) with ESMTP id B0F568FC08 for ; Mon, 25 Apr 2011 23:23:17 +0000 (UTC) Received: from taiko.lan (ppp-197-43.21-151.libero.it [151.21.43.197]) by dd16434.kasserver.com (Postfix) with ESMTPSA id B8CED188606E; Tue, 26 Apr 2011 01:23:16 +0200 (CEST) Message-ID: <4DB60233.3050609@chillt.de> Date: Tue, 26 Apr 2011 01:22:27 +0200 From: Bartosz Fabianowski User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110309 Thunderbird/3.1.9 MIME-Version: 1.0 To: Ian Smith , freebsd-stable@freebsd.org, John , Jeremy Chadwick References: <4DB44DA3.5060509@chillt.de> <4DB4589B.2020909@ksu.ru> <4DB45D6C.20203@chillt.de> <20110424182456.9DD03589@server.theusgroup.com> <4DB46ED4.2010500@chillt.de> <20110425004818.GA22579@icarus.home.lan> <4DB51F27.5010508@chillt.de> <20110425184728.C73992@sola.nimnet.asn.au> <4DB56CDA.50504@chillt.de> <20110425182352.GA6768@lava.net> In-Reply-To: <20110425182352.GA6768@lava.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: Subject: Re: System extremely slow under light load 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, 25 Apr 2011 23:23:18 -0000 > I could be wrong, but in my experience this really sounds like it is > a hardware problem with the cooling system, and a very serious one at > that. I would encourage you to take this up with Dell at once. Yes, I will. They have exchanged a lot of components already though (including the whole laptop) and so far, nothing has helped. > While it's certainly possible that newer FreeBSD releases are failing > to control the temperature as well as older ones due to some change, > that does not mean that this is a FreeBSD problem - these temperatures > are so far out of line that anything FreeBSD managed to do before > should be viewed as an unexpectedly successful workaround. This box has been running FreeBSD 8 since day one. It always had trouble with high temperatures. But now that summer is coming and ambient temperatures are rising, the issue keeps getting worse. > Apart from your immediate problems, in my past experience this range > of CPU temperatures is likely to lead to early failure of the CPU, very > likely within a year or less. Yes, I am afraid that may happen. Then again, Intel's data sheet clearly states that this CPU is designed to operate at up to 100°C. - Bartosz From owner-freebsd-stable@FreeBSD.ORG Mon Apr 25 23:24:22 2011 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 7E1271065673 for ; Mon, 25 Apr 2011 23:24:22 +0000 (UTC) (envelope-from freebsd@chillt.de) Received: from dd16434.kasserver.com (dd16434.kasserver.com [85.13.137.111]) by mx1.freebsd.org (Postfix) with ESMTP id 3B2928FC16 for ; Mon, 25 Apr 2011 23:24:22 +0000 (UTC) Received: from taiko.lan (ppp-197-43.21-151.libero.it [151.21.43.197]) by dd16434.kasserver.com (Postfix) with ESMTPSA id 5B44E188606E; Tue, 26 Apr 2011 01:24:21 +0200 (CEST) Message-ID: <4DB60274.60701@chillt.de> Date: Tue, 26 Apr 2011 01:23:32 +0200 From: Bartosz Fabianowski User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110309 Thunderbird/3.1.9 MIME-Version: 1.0 To: Torfinn Ingolfsen References: <4DB4589B.2020909@ksu.ru> <4DB45D6C.20203@chillt.de> <20110424182456.9DD03589@server.theusgroup.com> <4DB46ED4.2010500@chillt.de> <20110425004818.GA22579@icarus.home.lan> <4DB51F27.5010508@chillt.de> <20110425184728.C73992@sola.nimnet.asn.au> <4DB56CDA.50504@chillt.de> <20110425232429.N85801@sola.nimnet.asn.au> <4DB57F45.4080107@chillt.de> <20110425141643.GA38380@icarus.home.lan> <4DB583E9.8080507@chillt.de> <20110425234117.d1476c95.torfinn.ingolfsen@broadpark.no> In-Reply-To: <20110425234117.d1476c95.torfinn.ingolfsen@broadpark.no> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: System extremely slow under light load 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, 25 Apr 2011 23:24:22 -0000 > Have you tried just using dd to copy the iso image of a Ubuntu / Linux > LiveCD to a suitably sized USB memory stick? > It has worked for me in the past. As per Mehmet's tip, I did just that with a Debian image. If it works for Ubuntu images as well then I really wonder why the only documented way is via Unetbootin. - Bartosz From owner-freebsd-stable@FreeBSD.ORG Mon Apr 25 23:32:23 2011 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 65F971065672 for ; Mon, 25 Apr 2011 23:32:23 +0000 (UTC) (envelope-from oberman@es.net) Received: from mailgw.es.net (mail1.es.net [IPv6:2001:400:201:1::2]) by mx1.freebsd.org (Postfix) with ESMTP id 502B08FC15 for ; Mon, 25 Apr 2011 23:32:23 +0000 (UTC) Received: from ptavv.es.net (ptavv.es.net [IPv6:2001:400:910::29]) by mailgw.es.net (8.14.3/8.14.3) with ESMTP id p3PNWI9o028123 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 25 Apr 2011 16:32:18 -0700 Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 60BA31CC2B; Mon, 25 Apr 2011 16:32:18 -0700 (PDT) To: Bartosz Fabianowski In-reply-to: Your message of "Tue, 26 Apr 2011 01:19:03 +0200." <4DB60167.3090207@chillt.de> Date: Mon, 25 Apr 2011 16:32:18 -0700 From: "Kevin Oberman" Message-Id: <20110425233218.60BA31CC2B@ptavv.es.net> Cc: freebsd-stable@freebsd.org, Ian Smith , Jeremy Chadwick , John Subject: Re: System extremely slow under light load 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, 25 Apr 2011 23:32:23 -0000 > Date: Tue, 26 Apr 2011 01:19:03 +0200 > From: Bartosz Fabianowski > > > As several have either discovered or pointed out, the dev.cpu.X.freq is > > telling you what FreeBSD is requesting, not what the CPU is actually > > doing. Particularly, if high temperatures cause TCC to kick in, this > > will not show up. > > Yes, this is what I thought as well. > > > IF you really want to monitor CPU temperature on an Intel CPU, use the > > coretemp kernel module. I use it on Intel systems that lack ACPI support > > for temperature monitoring. It uses a junction on the die, so it will be > > somewhat higher than the package temperature. > > Yes, I am using that module and monitoring the dev.cpu.X.temperature > output. Technically, my system has support for ACPI monitoring but as I > mentioned in earlier messages, the DSDT provided by Dell is broken. > > > I would assume that means that TCC should kick in at about 95 or 96C > > which does not entirely explain what you are seeing. Unfortunately, your > > system does not provide a value for _PSV, so I have no idea when it will > > actually kick in, but it should be in the data sheet for the CPU. If > > ACPI does not hange it, it runs in a purely automated fashion with no > > human intervention available. > > I downloaded and read the specs. If I understand them correctly, the > maximal junction temperature for this CPU is 100°C. TCC should kick in > when any of the cores exceeds this value. It is unclear to me when > exactly TCC deactivates again but if the diagrams in the documentation > are drawn to scale, a pretty wide hysteresis is involved. So one > explanation for what I am seeing may be this: One of the cores, for a > split second, jumps over 100°C. TCC kicks in and does not turn off for a > long while. During that time, the system feels sluggish and slow. The specified maximum CPU temperature is usually the same at the ACPI _CRT, not _PSV. That is the temperature when an ACPI shutdown should be triggered, but TCC should kick in at some point below this. It does have significant hysteresis, but I'd need to look up the Intel documentation of TCC (which I have read in the past but can't seem to find now) to see just how it is governed. > > Try running md5 or sha256 on a bunch of random (/dev/random) data. > > Collect the time it takes to do a bunch of these and you will see it > > increase by .125 every time throttling adds another step to the pause > > time. It will be fairly dramatic and very close to steps of exactly .125 > > of the original time. > > Thanks, I will be using that to try and determine whether it really is > TCC that makes my machine sluggish under load. It works to tell you that TCC is doing the job, but does not explain in any way why your CPU is so hot. I'll be very curious as to what you find when running another OS. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 From owner-freebsd-stable@FreeBSD.ORG Mon Apr 25 23:32:35 2011 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 CFE7D1065797 for ; Mon, 25 Apr 2011 23:32:35 +0000 (UTC) (envelope-from gardnerbell@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 9C9FC8FC13 for ; Mon, 25 Apr 2011 23:32:35 +0000 (UTC) Received: by iwn33 with SMTP id 33so123343iwn.13 for ; Mon, 25 Apr 2011 16:32:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=ZiH5BaxrELmnblEWVN+gUY4yL6G3omhiXZvH/4e93/E=; b=Lzbdp7+J5/qhgv0Qq/gmICeNDtg6SpbbmYzUDMPTgYcy1GdBFFIrvZedGy+V4CEt/1 dZeKPRxYHSF9nm6ISq4CIxYDimNeyie8oMBXO5qTkNCQsOGIXHudiibQJkwqNCTfwVCA e43OLLJpj5ijakQ90YZc1Rk8aoiLtBnLvSz2s= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=hoZMSNOCmYQJGR/z38vjMwE7/qmrutlsOATe8t+nlhur1mJ4oyKuxrl3tFhvoOjlqh iWkr5zQYcMLvoPpGOgSLDYDBT7GylbElGOr9iUZld7seCsRIbtOPG0Hdq0jU/YZ0FMZ7 bCHLU1/v603jJAiBi2axyVgWG9X6Q9bPTuI9o= MIME-Version: 1.0 Received: by 10.42.141.202 with SMTP id p10mr76844icu.124.1303772982799; Mon, 25 Apr 2011 16:09:42 -0700 (PDT) Received: by 10.42.179.68 with HTTP; Mon, 25 Apr 2011 16:09:42 -0700 (PDT) Date: Mon, 25 Apr 2011 19:09:42 -0400 Message-ID: From: Gardner Bell To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Fatal trap 12: page fault while in kernel mode 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, 25 Apr 2011 23:32:36 -0000 Downloading a torrent with many peers on a toshiba satellite notebook using an Atheros AR5006 wireless nic caused the following panic. This is an i386 system running 8.2-STABLE from around April 06. Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0xc647a000 fault code = supervisor read, page not present instruction pointer = 0x20:0xc0999329 stack pointer = 0x28:0xc51c1c18 frame pointer = 0x28:0xc51c1c24 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 12 (swi4: clock) trap number = 12 panic: page fault cpuid = 0 KDB: stack backtrace: #0 0xc08e0d07 at kdb_backtrace+0x47 #1 0xc08b1dc7 at panic+0x117 #2 0xc0be4b43 at trap_fatal+0x323 #3 0xc0be4dc0 at trap_pfault+0x270 #4 0xc0be5305 at trap+0x465 #5 0xc0bcbebc at calltrap+0x6 #6 0xc08c508a at softclock+0x22a #7 0xc088903b at intr_event_execute_handlers+0x13b #8 0xc088a75b at ithread_loop+0x6b #9 0xc0886d51 at fork_exit+0x91 #10 0xc0bcbf34 at fork_trampoline+0x8 Uptime: 6m15s Physical memory: 2026 MB Dumping 99 MB: 84 68 52 36 20 4 #0 doadump () at pcpu.h:231 231 pcpu.h: No such file or directory. in pcpu.h (kgdb) #0 doadump () at pcpu.h:231 #1 0xc08b1b63 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:419 #2 0xc08b1e00 in panic (fmt=Variable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:592 #3 0xc0be4b43 in trap_fatal (frame=0xc51c1bd8, eva=3326582784) at /usr/src/sys/i386/i386/trap.c:946 #4 0xc0be4dc0 in trap_pfault (frame=0xc51c1bd8, usermode=0, eva=3326582784) at /usr/src/sys/i386/i386/trap.c:859 #5 0xc0be5305 in trap (frame=0xc51c1bd8) at /usr/src/sys/i386/i386/trap.c:532 #6 0xc0bcbebc in calltrap () at /usr/src/sys/i386/i386/exception.s:166 #7 0xc0999329 in ieee80211_tx_mgt_timeout (arg=0xc647a000) at /usr/src/sys/net80211/ieee80211_output.c:2478 #8 0xc08c508a in softclock (arg=0xc0df90e0) at /usr/src/sys/kern/kern_timeout.c:430 #9 0xc088903b in intr_event_execute_handlers (p=0xc55497f8, ie=0xc5591d00) at /usr/src/sys/kern/kern_intr.c:1220 #10 0xc088a75b in ithread_loop (arg=0xc5548070) at /usr/src/sys/kern/kern_intr.c:1233 #11 0xc0886d51 in fork_exit (callout=0xc088a6f0 , arg=0xc5548070, frame=0xc51c1d28) at /usr/src/sys/kern/kern_fork.c:845 #12 0xc0bcbf34 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:273 (kgdb) From owner-freebsd-stable@FreeBSD.ORG Mon Apr 25 23:41:10 2011 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 24286106564A for ; Mon, 25 Apr 2011 23:41:10 +0000 (UTC) (envelope-from freebsd@chillt.de) Received: from dd16434.kasserver.com (dd16434.kasserver.com [85.13.137.111]) by mx1.freebsd.org (Postfix) with ESMTP id DC4A48FC0A for ; Mon, 25 Apr 2011 23:41:09 +0000 (UTC) Received: from taiko.lan (ppp-197-43.21-151.libero.it [151.21.43.197]) by dd16434.kasserver.com (Postfix) with ESMTPSA id 960D5188606E; Tue, 26 Apr 2011 01:41:08 +0200 (CEST) Message-ID: <4DB60662.6040403@chillt.de> Date: Tue, 26 Apr 2011 01:40:18 +0200 From: Bartosz Fabianowski User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110309 Thunderbird/3.1.9 MIME-Version: 1.0 To: Kevin Oberman References: <20110425233218.60BA31CC2B@ptavv.es.net> In-Reply-To: <20110425233218.60BA31CC2B@ptavv.es.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-stable@freebsd.org, Ian Smith , Jeremy Chadwick , John Subject: Re: System extremely slow under light load 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, 25 Apr 2011 23:41:10 -0000 > The specified maximum CPU temperature is usually the same at the ACPI > _CRT, not _PSV. That is the temperature when an ACPI shutdown should be > triggered, but TCC should kick in at some point below this. This laptop is a replacement for an earlier one that had similar overheating issues. On that earlier laptop, Dell had managed to set _CRT=85°C with _PSV=95°C. This meant that the laptop did an emergency shutdown at 85°C *before* TCC got a chance to kick in at 95°C. At least on this one, _CRT=100°C and _PSV=95°C represent a more reasonable combination. > It works to tell you that TCC is doing the job, but does not explain in > any way why your CPU is so hot. I'll be very curious as to what you find > when running another OS. I experimented with a Debian Live CD. The results are here: http://lists.freebsd.org/pipermail/freebsd-stable/2011-April/062407.html - Bartosz From owner-freebsd-stable@FreeBSD.ORG Mon Apr 25 23:45:16 2011 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 933DF106564A for ; Mon, 25 Apr 2011 23:45:16 +0000 (UTC) (envelope-from freebsd@chillt.de) Received: from dd16434.kasserver.com (dd16434.kasserver.com [85.13.137.111]) by mx1.freebsd.org (Postfix) with ESMTP id 577848FC1B for ; Mon, 25 Apr 2011 23:45:16 +0000 (UTC) Received: from taiko.lan (ppp-197-43.21-151.libero.it [151.21.43.197]) by dd16434.kasserver.com (Postfix) with ESMTPSA id 5DB30188606E; Tue, 26 Apr 2011 01:45:15 +0200 (CEST) Message-ID: <4DB60759.1070906@chillt.de> Date: Tue, 26 Apr 2011 01:44:25 +0200 From: Bartosz Fabianowski User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110309 Thunderbird/3.1.9 MIME-Version: 1.0 To: Alexandre Kovalenko References: <4DB5751B.2050903@chillt.de> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-stable@freebsd.org Subject: Re: System extremely slow under light load 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, 25 Apr 2011 23:45:16 -0000 > Did you try to set OS override to any of the values, recognized by > your BIOS, with most interesting being "Windows 2001 SP2", "Windows > 2006" and "Windows 2009". Yes, I tried this a while ago, before messing with the DSDT. I figured it was unlikely that Dell shipped a DSDT which leads to 0°C readings under Windows. Alas, no OS override seemed to change anything. The CPU was running just as hot and the temperature reported by ACPI remained 0°C. Now that I have tried Linux, I can confirm that there, too, the temperature is 0°C. The DSDT is completely broken. > Additionally, could you, by any chance, replace _TMP method in TZ01 > with the snippet below and let me know what the result is: I am running with that change right now. It seems to have the same effect as my own fixes: hw.acpi.thermal.tz1.temperature works and returns a temperature that agrees with dev.cpu.X.temperature. No other obvious changes. All temperatures are still in the same ranges. - Bartosz From owner-freebsd-stable@FreeBSD.ORG Mon Apr 25 23:53:42 2011 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 B8D1A106566B for ; Mon, 25 Apr 2011 23:53:42 +0000 (UTC) (envelope-from freebsd@chillt.de) Received: from dd16434.kasserver.com (dd16434.kasserver.com [85.13.137.111]) by mx1.freebsd.org (Postfix) with ESMTP id 7D2EE8FC1D for ; Mon, 25 Apr 2011 23:53:42 +0000 (UTC) Received: from taiko.lan (ppp-197-43.21-151.libero.it [151.21.43.197]) by dd16434.kasserver.com (Postfix) with ESMTPSA id 92869188606E; Tue, 26 Apr 2011 01:53:41 +0200 (CEST) Message-ID: <4DB60953.4040906@chillt.de> Date: Tue, 26 Apr 2011 01:52:51 +0200 From: Bartosz Fabianowski User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110309 Thunderbird/3.1.9 MIME-Version: 1.0 To: Mehmet Erol Sanliturk References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable Subject: Re: System extremely slow under light load 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, 25 Apr 2011 23:53:42 -0000 This appears to be a different issue from the one I am seeing. The system is very responsive at first and only under load (and with rising temperatures) becomes extremely sluggish. As load (and temperatures) drop, the system becomes usable again. Also, there is no difference between Qt and Gtk apps. All of them are equally fast or slow. - Bartosz From owner-freebsd-stable@FreeBSD.ORG Tue Apr 26 00:46:56 2011 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 DEE811065672 for ; Tue, 26 Apr 2011 00:46:55 +0000 (UTC) (envelope-from bsd.gaijin@gmail.com) Received: from mail-qy0-f175.google.com (mail-qy0-f175.google.com [209.85.216.175]) by mx1.freebsd.org (Postfix) with ESMTP id 90D648FC12 for ; Tue, 26 Apr 2011 00:46:55 +0000 (UTC) Received: by qyk35 with SMTP id 35so1068191qyk.13 for ; Mon, 25 Apr 2011 17:46:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:from:to:cc:in-reply-to:references :content-type:date:message-id:mime-version:x-mailer :content-transfer-encoding; bh=HJwdl9Znn0AQWhIVAOiJ3T+GlVgWC5Da5GBTTRJWGO8=; b=IULEEj/jK6MmZN6szaf6nhmBPSOSyJi62eDOmNC8qvS/BIBOdTAIQjRB3d5gSOKG4M noC1yLJgkmrnxuuZPiSxvmp1eaQJ3emETfdzu8RqebO7SOH2JafvHzTuCoGGCHgqyVeL WW6q0Ha1kZxZW7UlYYgNNAXCrRz3XNaJw5iec= 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=rHcrr3F+58UOJQ/TVLZG5sSqIwSm/vB95K0Y9dY/dHJqBhrQ4O8CBQqxIs1IpO+kw4 z2SpcTfBjOAAP17mpFT1iBZzJbDySvluB5e/wgamYGx27tGwQ+0SV09/gh4GO7KgIy44 +WBvQWTCOetJSsHJK/82L/v6JhVIwCl+GawcI= Received: by 10.224.125.209 with SMTP id z17mr85342qar.223.1303778814697; Mon, 25 Apr 2011 17:46:54 -0700 (PDT) Received: from [10.0.3.231] (pool-74-105-210-169.nwrknj.fios.verizon.net [74.105.210.169]) by mx.google.com with ESMTPS id l10sm2610270qck.26.2011.04.25.17.46.53 (version=SSLv3 cipher=OTHER); Mon, 25 Apr 2011 17:46:54 -0700 (PDT) From: "Alexandre \"Sunny\" Kovalenko" To: Bartosz Fabianowski In-Reply-To: <4DB60759.1070906@chillt.de> References: <4DB5751B.2050903@chillt.de> <4DB60759.1070906@chillt.de> Content-Type: text/plain; charset="UTF-8" Date: Mon, 25 Apr 2011 20:46:41 -0400 Message-ID: <1303778801.10649.27.camel@RabbitsDen.RabbitsLawn.verizon.net> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 8bit Cc: freebsd-stable@freebsd.org Subject: Re: System extremely slow under light load 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, 26 Apr 2011 00:46:56 -0000 On Tue, 2011-04-26 at 01:44 +0200, Bartosz Fabianowski wrote: > > Did you try to set OS override to any of the values, recognized by > > your BIOS, with most interesting being "Windows 2001 SP2", "Windows > > 2006" and "Windows 2009". > > Yes, I tried this a while ago, before messing with the DSDT. I figured > it was unlikely that Dell shipped a DSDT which leads to 0°C readings > under Windows. Alas, no OS override seemed to change anything. The CPU > was running just as hot and the temperature reported by ACPI remained > 0°C. Now that I have tried Linux, I can confirm that there, too, the > temperature is 0°C. The DSDT is completely broken. > > > Additionally, could you, by any chance, replace _TMP method in TZ01 > > with the snippet below and let me know what the result is: > > I am running with that change right now. It seems to have the same > effect as my own fixes: hw.acpi.thermal.tz1.temperature works and > returns a temperature that agrees with dev.cpu.X.temperature. No other > obvious changes. All temperatures are still in the same ranges. There are two things of interest here: * Obviously Dell BIOS writer expected different scoping rules than FreeBSD is applying (DS1 and DS2 are defined in the two different scopes). As you have already pointed out it is unlikely that Dell has produced laptop which will not work correctly in Windows, so, likely Windows scoping rules are also different from FreeBSD ones. You might want to start thread on acpi@ and might get some suggestions from Intel folks who tend to hang out there and/or from people who, unlike me, know something about ACPI in general and FreeBSD ACPI implementation in particular. It is quite possible that scoping is causing some other problems as well, some of which, actually might be applicable to the problem in hand. Alternative approach would be to explicitly name all of the methods/fields in all _ACx, _ALx and fan objects and see whether fans will kick in in time and with the desired intensity and keep temperature at bay. * The main difference between your change and mine is that mine (or, rather, the intent of the original writer) uses two sources and the higher value of the two. I am curious whether the behavior WRT critical shutdown will be the same in both cases. > > - Bartosz -- Alexandre Kovalenko (Олександр Коваленко) From owner-freebsd-stable@FreeBSD.ORG Tue Apr 26 02:15:58 2011 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 F2E47106564A for ; Tue, 26 Apr 2011 02:15:58 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-qy0-f175.google.com (mail-qy0-f175.google.com [209.85.216.175]) by mx1.freebsd.org (Postfix) with ESMTP id A39B38FC14 for ; Tue, 26 Apr 2011 02:15:58 +0000 (UTC) Received: by qyk35 with SMTP id 35so1094213qyk.13 for ; Mon, 25 Apr 2011 19:15:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=DgAthPw1vsjtzl3Stt9xNlgDh/ZfObTccqwHMewgLf0=; b=RfxvdN1GKgXeaXVllOkdNiE9UIXjnYuWAuh5bJpRXhyYJ7S9FGg3CYmT1RViG7Fi4F GtmxvTSUSfzqDR/PJyN/iIIsO96uLWXojmRWmbvAsjTCsA2gxiGR0xIfxP0FyNlp9WeE 2nsQe4pTWJVbjEGGLBFdzuHPEK61x9O4drxto= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=gagatIhwhuMKoU8sYX7a+kUOZG0s3CvlylSplbZwYSqDYc/hktXoa/MVzlg/pzikpJ +W4aGwdqZfshpQ/tNEWcMbgdbVzDMigxSmlNMmMf/YJH6n+oK9U7e+IfT5zhlggriCD0 MEmsYikSghYTfKIMvVe37BiZXbIWV3yioWvho= MIME-Version: 1.0 Received: by 10.224.189.9 with SMTP id dc9mr144840qab.11.1303784157816; Mon, 25 Apr 2011 19:15:57 -0700 (PDT) Received: by 10.224.179.212 with HTTP; Mon, 25 Apr 2011 19:15:57 -0700 (PDT) In-Reply-To: <4DB60274.60701@chillt.de> References: <4DB4589B.2020909@ksu.ru> <4DB45D6C.20203@chillt.de> <20110424182456.9DD03589@server.theusgroup.com> <4DB46ED4.2010500@chillt.de> <20110425004818.GA22579@icarus.home.lan> <4DB51F27.5010508@chillt.de> <20110425184728.C73992@sola.nimnet.asn.au> <4DB56CDA.50504@chillt.de> <20110425232429.N85801@sola.nimnet.asn.au> <4DB57F45.4080107@chillt.de> <20110425141643.GA38380@icarus.home.lan> <4DB583E9.8080507@chillt.de> <20110425234117.d1476c95.torfinn.ingolfsen@broadpark.no> <4DB60274.60701@chillt.de> Date: Mon, 25 Apr 2011 22:15:57 -0400 Message-ID: From: Mehmet Erol Sanliturk To: Bartosz Fabianowski Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Torfinn Ingolfsen , freebsd-stable@freebsd.org Subject: Re: System extremely slow under light load 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, 26 Apr 2011 02:15:59 -0000 On Mon, Apr 25, 2011 at 7:23 PM, Bartosz Fabianowski wrote: > Have you tried just using dd to copy the iso image of a Ubuntu / Linux >> LiveCD to a suitably sized USB memory stick? >> It has worked for me in the past. >> > > As per Mehmet's tip, I did just that with a Debian image. If it works for > Ubuntu images as well then I really wonder why the only documented way is > via Unetbootin. > > - Bartosz > _______________________________________________ > To reduce the number of files to maintain , some Linux distributions started to generate .iso files both for CD/DVD burning and USB stick dd copying . Such distributions are mostly called "dual" or "hybrid" in their names with .iso extension to distinguish them from only CD/DVD burning .iso files . If an .iso is named for USB without "dual" or "hybrid" names , it is very likely that it is prepared in such a way for USB dd copying . With respect to my opinion , most .iso files which they are prepared for CD/DVD burning will be able to boot and install from dd copied USB sticks because .iso is a FILE format , NOT a DEVICE format . The problem is not the file format but the ability of the operating system to use devices . For example , I am seeing operating systems in CD , they are booting from DVD drive ( because BIOS is loading their kernel , etc. ) but failing to install because their kernels , etc. are NOT able to use the DVD drive when they are taking the control of the PC . Thank you very much . Mehmet Erol Sanliturk From owner-freebsd-stable@FreeBSD.ORG Tue Apr 26 06:52:11 2011 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 E6318106564A for ; Tue, 26 Apr 2011 06:52:11 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 1A5648FC0C for ; Tue, 26 Apr 2011 06:52:10 +0000 (UTC) Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id JAA15746; Tue, 26 Apr 2011 09:52:08 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost.topspin.kiev.ua ([127.0.0.1]) by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1QEc80-0005Nw-9q; Tue, 26 Apr 2011 09:52:08 +0300 Message-ID: <4DB66B97.1060703@FreeBSD.org> Date: Tue, 26 Apr 2011 09:52:07 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110308 Lightning/1.0b2 Thunderbird/3.1.9 MIME-Version: 1.0 To: Gardner Bell References: In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@FreeBSD.org Subject: Re: Fatal trap 12: page fault while in kernel mode 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, 26 Apr 2011 06:52:12 -0000 on 26/04/2011 02:09 Gardner Bell said the following: > #6 0xc0bcbebc in calltrap () at /usr/src/sys/i386/i386/exception.s:166 > #7 0xc0999329 in ieee80211_tx_mgt_timeout (arg=0xc647a000) > at /usr/src/sys/net80211/ieee80211_output.c:2478 Looks like an issue in wireless code... -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Tue Apr 26 08:39:42 2011 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 E9AF0106566C for ; Tue, 26 Apr 2011 08:39:42 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 865CA8FC23 for ; Tue, 26 Apr 2011 08:39:42 +0000 (UTC) Received: by fxm11 with SMTP id 11so373943fxm.13 for ; Tue, 26 Apr 2011 01:39:41 -0700 (PDT) Received: by 10.223.7.8 with SMTP id b8mr526679fab.19.1303805631691; Tue, 26 Apr 2011 01:13:51 -0700 (PDT) Received: from jessie.localnet (p5B2ECD44.dip0.t-ipconnect.de [91.46.205.68]) by mx.google.com with ESMTPS id 23sm1905250fay.28.2011.04.26.01.13.48 (version=SSLv3 cipher=OTHER); Tue, 26 Apr 2011 01:13:49 -0700 (PDT) Sender: Bernhard Schmidt From: Bernhard Schmidt To: freebsd-stable@freebsd.org Date: Tue, 26 Apr 2011 10:12:56 +0200 User-Agent: KMail/1.13.5 (Linux/2.6.32-31-generic; KDE/4.4.5; i686; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201104261012.57113.bschmidt@freebsd.org> Cc: Gardner Bell Subject: Re: Fatal trap 12: page fault while in kernel mode X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bschmidt@freebsd.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2011 08:39:43 -0000 On Tuesday, April 26, 2011 01:09:42 Gardner Bell wrote: > Downloading a torrent with many peers on a toshiba satellite notebook > using an Atheros AR5006 wireless nic caused the following panic. This > is an i386 system running 8.2-STABLE from around April 06. Can you reproduce that? A comment about the relevant code says: /* * XXX what happens if !acked but response shows up before callback? */ Guess we now know.. ;) -- Bernhard From owner-freebsd-stable@FreeBSD.ORG Tue Apr 26 09:44:38 2011 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 993E3106564A; Tue, 26 Apr 2011 09:44:38 +0000 (UTC) (envelope-from to.my.trociny@gmail.com) Received: from mail-ey0-f182.google.com (mail-ey0-f182.google.com [209.85.215.182]) by mx1.freebsd.org (Postfix) with ESMTP id F24CF8FC0C; Tue, 26 Apr 2011 09:44:37 +0000 (UTC) Received: by eyg7 with SMTP id 7so174173eyg.13 for ; Tue, 26 Apr 2011 02:44:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:to:cc:subject:organization:references :sender:date:in-reply-to:message-id:user-agent:mime-version :content-type; bh=SOPJjyo8AzVSr1mkcdYdE9kbuux7wq3sA0tNBboa9so=; b=iUJZfBClWNUm4cLusw/pYV+C+5Syz81KD+wdIugO5gIwYRt+BccJG2XjbLAD3D3I4A sLg4zQtdJeIpDa2G3zQ5dePJhtvjGj4kTPqyExT3uEIpd5XvucN5dMLjRPOLW63e/nsi AkXk7JZiGJpSIL0okhTxoOPM5PVVWjYzViK0Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:subject:organization:references:sender:date:in-reply-to :message-id:user-agent:mime-version:content-type; b=MvJbWMwUBhWz9em4K1fLahxI5zRI9op3WbKY+pqJN8Yg++pcEKHLSUC2BnuIY0ozLV dhMLZvlk2VNiblUS6w13MI0VPlpwmfTolir9w8610DXnt9xJy/k4n8qTihcR94EUw40v mjNDm1fiGxGAD9uzH4PCSOe3ZWTC/uE2et2xs= Received: by 10.213.108.135 with SMTP id f7mr1724327ebp.62.1303811076783; Tue, 26 Apr 2011 02:44:36 -0700 (PDT) Received: from localhost ([94.27.39.186]) by mx.google.com with ESMTPS id q53sm4669568eeh.4.2011.04.26.02.44.34 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 26 Apr 2011 02:44:35 -0700 (PDT) From: Mikolaj Golub To: "Matthew D. Fuller" Organization: TOA Ukraine References: <926783796.20110423022501@nitronet.pl> <20110423005422.GQ91591@over-yonder.net> <2910134705.20110423090442@nitronet.pl> <20110423125247.GA89102@icarus.home.lan> <20110423143838.GR91591@over-yonder.net> Sender: Mikolaj Golub Date: Tue, 26 Apr 2011 12:44:31 +0300 In-Reply-To: <20110423143838.GR91591@over-yonder.net> (Matthew D. Fuller's message of "Sat, 23 Apr 2011 09:38:39 -0500") Message-ID: <86mxjd1h4w.fsf@in138.ua3> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (berkeley-unix) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Cc: Pawel Tyll , freebsd-stable@freebsd.org, pjd@freebsd.org, Jeremy Chadwick Subject: Re: buildworld FAIL. 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, 26 Apr 2011 09:44:38 -0000 --=-=-= On Sat, 23 Apr 2011 09:38:39 -0500 Matthew D. Fuller wrote: MDF> On Sat, Apr 23, 2011 at 05:52:47AM -0700 I heard the voice of MDF> Jeremy Chadwick, and lo! it spake thus: >> On Sat, Apr 23, 2011 at 09:04:42AM +0200, Pawel Tyll wrote: >> > So was NO_OPENSSL deprecated or something? >> >> I think he's implying that hast indirectly relies upon OpenSSL. MDF> There's some conditionalization on MK_OPENSSL in the Makefile (and via MDF> that, in the code), but it's incomplete. Whether that means it MDF> _should_ be buildable without OpenSSL and is just insufficiently MDF> tested, or whether it really just flat needs OpenSSL and the MDF> conditionalization is vestigial, I don't know. pjd@ cc'd. The attached patch should fix this. -- Mikolaj Golub --=-=-= Content-Type: text/x-patch Content-Disposition: attachment; filename=hast_proto.c.HAVE_CRYPTO.patch Index: sbin/hastd/hast_proto.c =================================================================== --- sbin/hastd/hast_proto.c (revision 221054) +++ sbin/hastd/hast_proto.c (working copy) @@ -69,7 +69,9 @@ struct hast_pipe_stage { static struct hast_pipe_stage pipeline[] = { { "compression", compression_send, compression_recv }, +#ifdef HAVE_CRYPTO { "checksum", checksum_send, checksum_recv } +#endif }; /* --=-=-=-- From owner-freebsd-stable@FreeBSD.ORG Tue Apr 26 13:15:46 2011 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 1580D106564A for ; Tue, 26 Apr 2011 13:15:46 +0000 (UTC) (envelope-from gardnerbell@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id D22458FC0A for ; Tue, 26 Apr 2011 13:15:45 +0000 (UTC) Received: by iyj12 with SMTP id 12so669956iyj.13 for ; Tue, 26 Apr 2011 06:15:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=TIS04S927P/zZ0+mjJjC/HzHdxpORk1CTucFF0h4948=; b=KDF+Vz1TEsUaKSgZXQEnSB8fzjBpjtwVxDcVTDBPV8lXjLpNaxOx+C9om6hQxnKCVH nYdrCV66g2CF/e6nASOC2XAHAQFiB7lcbIICSJN697wnc9QIzoq064PbRgsGsGSXGON1 P7YaQ4oGv3ZTF1UEs5VyNLxc064n+Xx/eQ6GE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=BP04ezpTR+g/2vSImatx+/uEgfkoYCSM9onLkiuFEQUFVBuo8iezlcUceIX+SFdbi3 NmrdcJcn1F2UVpTE3/rDcKIjw6zCvP9P5/4xMrj1PqRLWAoDuIhY1ZCda7igal8/2xDy HIvLFGAHyzqtVL5JTPtu8v6Nic3LxxCLmFF/s= MIME-Version: 1.0 Received: by 10.42.136.129 with SMTP id u1mr844722ict.459.1303823745173; Tue, 26 Apr 2011 06:15:45 -0700 (PDT) Received: by 10.42.179.68 with HTTP; Tue, 26 Apr 2011 06:15:45 -0700 (PDT) In-Reply-To: <201104261012.57113.bschmidt@freebsd.org> References: <201104261012.57113.bschmidt@freebsd.org> Date: Tue, 26 Apr 2011 09:15:45 -0400 Message-ID: From: Gardner Bell To: bschmidt@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org Subject: Re: Fatal trap 12: page fault while in kernel mode 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, 26 Apr 2011 13:15:46 -0000 On Tue, Apr 26, 2011 at 4:12 AM, Bernhard Schmidt wr= ote: > On Tuesday, April 26, 2011 01:09:42 Gardner Bell wrote: >> Downloading a torrent with many peers on a toshiba satellite notebook >> using an Atheros AR5006 wireless nic caused the following panic. =A0This >> is an i386 system running 8.2-STABLE from around April 06. > > Can you reproduce that? So far I've not been able to reproduce this. > > A comment about the relevant code says: > =A0 =A0 =A0 =A0/* > =A0 =A0 =A0 =A0 * XXX what happens if !acked but response shows up before= callback? > =A0 =A0 =A0 =A0 */ > > Guess we now know.. ;) > > -- > Bernhard > From owner-freebsd-stable@FreeBSD.ORG Tue Apr 26 13:55:30 2011 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 D04AB1065688 for ; Tue, 26 Apr 2011 13:55:30 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id A1B638FC16 for ; Tue, 26 Apr 2011 13:55:30 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 4624146B45; Tue, 26 Apr 2011 09:55:30 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id C05578A01B; Tue, 26 Apr 2011 09:55:29 -0400 (EDT) From: John Baldwin To: Przemyslaw Frasunek Date: Tue, 26 Apr 2011 09:44:52 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110325; KDE/4.5.5; amd64; ; ) References: <4DA4A96F.9000507@frasunek.com> <201104251604.04784.jhb@freebsd.org> <4DB5E9D6.3040203@frasunek.com> In-Reply-To: <4DB5E9D6.3040203@frasunek.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201104260944.52476.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Tue, 26 Apr 2011 09:55:29 -0400 (EDT) Cc: freebsd-stable@freebsd.org Subject: Re: Missing serial port after enabling serial console in loader.conf 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, 26 Apr 2011 13:55:30 -0000 On Monday, April 25, 2011 5:38:30 pm Przemyslaw Frasunek wrote: > > I don't think so. You can try swapping the hints for sio0 and sio1 and seeing if > > sio1 suddenly shows up as working and valid. If so, then the changes in 8 to bind > > unit numbers using hints might work for you to get COM1 back as sio0. > > Few days ago I decided to upgrade to 8.2-STABLE, partially due to some > long-standing Netgraph issues (which I discussed on freebsd-net). To my > surprise, sio0 (well, now uart0) had become detectable even in spite of enabled SOL: > > uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 > uart0: [FILTER] > uart0: console (9600,n,8,1) > uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0 > uart1: [FILTER] > > Eventually I'm able to use comconsole in loader.conf and getty simultaneously. > > BTW. I looked at the BIOS setup on my box - it has "Legacy OS" knob, allowing to > hide serial port occupied by SOL from non ACPI aware OS. It was disabled for all > the time, so my problem was probably related to sio(4) and fixed in uart(4). No, this was almost certainly due to the hints logic in 8. :) Probably what happened before is that ACPI was not listing COM1 at all, but then COM2 probed as sio0. Then there was no device for the I/O port resources for COM1. The hint changes in 8 would work around that issue by recognizing that case and keeping COM2 at sio1. That would then have allowed sio0 to probe at isa0. -- John Baldwin From owner-freebsd-stable@FreeBSD.ORG Tue Apr 26 14:26:22 2011 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 DB153106566C for ; Tue, 26 Apr 2011 14:26:22 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 74E968FC12 for ; Tue, 26 Apr 2011 14:26:21 +0000 (UTC) Received: by fxm11 with SMTP id 11so637615fxm.13 for ; Tue, 26 Apr 2011 07:26:21 -0700 (PDT) Received: by 10.223.25.152 with SMTP id z24mr914988fab.123.1303827981235; Tue, 26 Apr 2011 07:26:21 -0700 (PDT) Received: from jessie.localnet (p5B2ECD44.dip0.t-ipconnect.de [91.46.205.68]) by mx.google.com with ESMTPS id l3sm2018736fap.36.2011.04.26.07.26.19 (version=SSLv3 cipher=OTHER); Tue, 26 Apr 2011 07:26:19 -0700 (PDT) Sender: Bernhard Schmidt From: Bernhard Schmidt To: freebsd-stable@freebsd.org Date: Tue, 26 Apr 2011 16:25:26 +0200 User-Agent: KMail/1.13.5 (Linux/2.6.32-31-generic; KDE/4.4.5; i686; ; ) References: <201104261012.57113.bschmidt@freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201104261625.26606.bschmidt@freebsd.org> Cc: Gardner Bell Subject: Re: Fatal trap 12: page fault while in kernel mode X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bschmidt@freebsd.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2011 14:26:22 -0000 On Tuesday, April 26, 2011 15:15:45 Gardner Bell wrote: > On Tue, Apr 26, 2011 at 4:12 AM, Bernhard Schmidt wrote: > > On Tuesday, April 26, 2011 01:09:42 Gardner Bell wrote: > >> Downloading a torrent with many peers on a toshiba satellite notebook > >> using an Atheros AR5006 wireless nic caused the following panic. This > >> is an i386 system running 8.2-STABLE from around April 06. > > > > Can you reproduce that? > > So far I've not been able to reproduce this. Ok. I assume this only happens when loosing the connection and trying to re-associate. At least that is the only possible scenario I can think of where a timeout for mgmt frames is involved. Probably we aren't bumping a refcount correctly or something. Actually that sounds rather plausible as it panics exactly when trying to access ni which should, for a station, always point to iv_bss, which can in turn be free'd almost unconditionally if someone's telling net80211 to associate to another (or even the same) network. Hmm.. tracing refcount it is. Were you running wpa_supplicant at that point? Any messages before the panic happened? -- Bernhard From owner-freebsd-stable@FreeBSD.ORG Tue Apr 26 15:35:33 2011 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 AF0A01065670; Tue, 26 Apr 2011 15:35:33 +0000 (UTC) (envelope-from gardnerbell@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 6E2298FC08; Tue, 26 Apr 2011 15:35:33 +0000 (UTC) Received: by iwn33 with SMTP id 33so830750iwn.13 for ; Tue, 26 Apr 2011 08:35:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to:cc :content-type; bh=Xz5iG63A+odphpH3ax3NrUk5xdzF4WpBJwxReJVEFu8=; b=ds8zzCLKNUk7TN7CJGkXbmL1whg4PnuaEn8HQ+pBIbaZxcwYKdxlGOqUn2SYkygEIm c8HYgUZG7QGqCJP5OUIXCkxzpQzOdbR6WzLdl24FlxgV8URXq5S1kCTCdQFSBOMTW3/9 xwzFsmtR3zZxcMWxMeLOJDsZKwuWTHHwTqPvI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=RRA9AlScJUUlEfrDMj6z0eMUvwPJxOEY0ehyo3mrW7aVc5z1fkRWmGlO1wyUS0edLa dcOGUy7GXCCAPCH+6bSqmnmlc23A4UIhv6ACsuzBunepmSDTyuJpn7IXg0DAC0Cot7Ij PmJafenchTThx2KLrhaKJB1gu8SCLoO+hTV4g= MIME-Version: 1.0 Received: by 10.42.170.73 with SMTP id e9mr1081089icz.258.1303832132759; Tue, 26 Apr 2011 08:35:32 -0700 (PDT) Received: by 10.42.179.68 with HTTP; Tue, 26 Apr 2011 08:35:32 -0700 (PDT) Date: Tue, 26 Apr 2011 11:35:32 -0400 Message-ID: From: Gardner Bell To: bschmidt@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-stable@freebsd.org Subject: Re: Fatal trap 12: page fault while in kernel mode 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, 26 Apr 2011 15:35:33 -0000 On Tue, Apr 26, 2011 at 04:25:26PM +0200, Bernhard Schmidt wrote: > On Tuesday, April 26, 2011 15:15:45 Gardner Bell wrote: > > On Tue, Apr 26, 2011 at 4:12 AM, Bernhard Schmidt wrote: > > > On Tuesday, April 26, 2011 01:09:42 Gardner Bell wrote: > > >> Downloading a torrent with many peers on a toshiba satellite notebook > > >> using an Atheros AR5006 wireless nic caused the following panic. This > > >> is an i386 system running 8.2-STABLE from around April 06. > > > > > > Can you reproduce that? > > > > So far I've not been able to reproduce this. > > Ok. I assume this only happens when loosing the connection and trying > to re-associate. At least that is the only possible scenario I can > think of where a timeout for mgmt frames is involved. Probably we > aren't bumping a refcount correctly or something. Actually that sounds > rather plausible as it panics exactly when trying to access ni which > should, for a station, always point to iv_bss, which can in turn be > free'd almost unconditionally if someone's telling net80211 to > associate to another (or even the same) network. Hmm.. tracing refcount > it is. > > Were you running wpa_supplicant at that point? Any messages before > the panic happened? > Yes, I'm running wpa_supplicant with the following settings: network={ ssid="xxxxx" psk="xxxxx" } Other settings for the wireless card I have in rc.conf: wlans_ath0="wlan0" ifconfig_wlan0="WPA DHCP" ifconfig_wlan0_alias0="inet 192.168.0.12 netmask 0xffffffff" The last messages seen on the console before the panic are wlan0: ieee80211_new_state_locked: pending SCAN -> AUTH transition lost and several UP/DOWN events. > -- > Bernhard -- Gardner Bell From owner-freebsd-stable@FreeBSD.ORG Tue Apr 26 16:25:27 2011 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 D6D091065670; Tue, 26 Apr 2011 16:25:27 +0000 (UTC) (envelope-from pawel@dawidek.net) Received: from mail.garage.freebsd.pl (60.wheelsystems.com [83.12.187.60]) by mx1.freebsd.org (Postfix) with ESMTP id 782D08FC13; Tue, 26 Apr 2011 16:25:27 +0000 (UTC) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 1B24645EA4; Tue, 26 Apr 2011 18:25:22 +0200 (CEST) Received: from localhost (89-73-195-149.dynamic.chello.pl [89.73.195.149]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id EB6E045E87; Tue, 26 Apr 2011 18:25:16 +0200 (CEST) Date: Tue, 26 Apr 2011 18:25:09 +0200 From: Pawel Jakub Dawidek To: Mikolaj Golub Message-ID: <20110426162509.GB1979@garage.freebsd.pl> References: <926783796.20110423022501@nitronet.pl> <20110423005422.GQ91591@over-yonder.net> <2910134705.20110423090442@nitronet.pl> <20110423125247.GA89102@icarus.home.lan> <20110423143838.GR91591@over-yonder.net> <86mxjd1h4w.fsf@in138.ua3> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="kORqDWCi7qDJ0mEj" Content-Disposition: inline In-Reply-To: <86mxjd1h4w.fsf@in138.ua3> X-OS: FreeBSD 9.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-0.6 required=4.5 tests=BAYES_00,RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 Cc: kib@FreeBSD.org, Pawel Tyll , freebsd-stable@freebsd.org, Jeremy Chadwick , "Matthew D. Fuller" Subject: Re: buildworld FAIL. 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, 26 Apr 2011 16:25:27 -0000 --kORqDWCi7qDJ0mEj Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 26, 2011 at 12:44:31PM +0300, Mikolaj Golub wrote: >=20 > On Sat, 23 Apr 2011 09:38:39 -0500 Matthew D. Fuller wrote: >=20 > MDF> On Sat, Apr 23, 2011 at 05:52:47AM -0700 I heard the voice of > MDF> Jeremy Chadwick, and lo! it spake thus: > >> On Sat, Apr 23, 2011 at 09:04:42AM +0200, Pawel Tyll wrote: > >> > So was NO_OPENSSL deprecated or something? > >>=20 > >> I think he's implying that hast indirectly relies upon OpenSSL. >=20 > MDF> There's some conditionalization on MK_OPENSSL in the Makefile (and = via > MDF> that, in the code), but it's incomplete. Whether that means it > MDF> _should_ be buildable without OpenSSL and is just insufficiently > MDF> tested, or whether it really just flat needs OpenSSL and the > MDF> conditionalization is vestigial, I don't know. pjd@ cc'd. >=20 > The attached patch should fix this. The patch looks good. Please commit. > Index: sbin/hastd/hast_proto.c > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- sbin/hastd/hast_proto.c (revision 221054) > +++ sbin/hastd/hast_proto.c (working copy) > @@ -69,7 +69,9 @@ struct hast_pipe_stage { > =20 > static struct hast_pipe_stage pipeline[] =3D { > { "compression", compression_send, compression_recv }, > +#ifdef HAVE_CRYPTO > { "checksum", checksum_send, checksum_recv } > +#endif > }; > =20 > /* --=20 Pawel Jakub Dawidek http://www.wheelsystems.com FreeBSD committer http://www.FreeBSD.org Am I Evil? Yes, I Am! http://yomoli.com --kORqDWCi7qDJ0mEj Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAk228eUACgkQForvXbEpPzSiSgCgm3Q1D1N9WWBpzplkuYuw3W9C AfMAoL+Duq19gAyFBSU7QTJ2hbxQZ14e =ruPZ -----END PGP SIGNATURE----- --kORqDWCi7qDJ0mEj-- From owner-freebsd-stable@FreeBSD.ORG Tue Apr 26 17:32:04 2011 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 1A1271065670 for ; Tue, 26 Apr 2011 17:32:04 +0000 (UTC) (envelope-from mailreturn@smtp.ymlp15.net) Received: from smtp.ymlp15.net (smtp.ymlp15.net [87.237.8.246]) by mx1.freebsd.org (Postfix) with SMTP id 3D0068FC0A for ; Tue, 26 Apr 2011 17:32:02 +0000 (UTC) Received: (qmail 23467 invoked by uid 0); 26 Apr 2011 17:05:21 -0000 Date: Tue, 26 Apr 2011 19:05:21 +0200 To: stable@freebsd.org From: Efficiency At Work Place Message-ID: X-YMLPcode: p82a+927+243307 MIME-Version: 1.0 Content-Type: text/plain; charset = "utf-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Management Training on Enhanced Productivity X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: support@thewodia.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2011 17:32:04 -0000 --------------------------------------------------------------------------= ------ This email newsletter was sent to you in graphical HTML format. If you're seeing this version, your email program prefers plain text = emails. You can read the original version online: http://ymlp47.net/z0l86J --------------------------------------------------------------------------= ------ WODIA TRAINING INSTITUTE (WOTI) Management Training and Skills Development THE BOAT HOUSE, 21, Ogunnusi Road, Ogba, Ikeja, Lagos. Website http://www.thewodia.org/2011.html. E-mail:- invitation@thewodia.org Tel: +234 802 307 9485; +234 813 3754 358 Human Resource Development. PROGRAM OBJECTIVES are to provide effective manpower training that will enhance human capital output through improved Attitude, Skills and Knowledge . NEWManagement Training Program holding in Lagos Nigeria: 2. Topic: EFFICIENCY AND PRODUCTIVITY AT WORK PLACE. Date: - April 26-28, 2011 (Three-Days) Fee: - N25, 000.00 (Twenty Five Thousand Naira Only) per head Venue : WODIA Training Institute (WOTI) The Boat House, 21, Ogunnusi Road, Ogba, Ikeja, Lagos. COURSE OUTLINES: v Motivational Strategies for Effective Performance v Time management and Responsibility v Mental Alertness and Commitment to organization goals v Formal Behavioral Patterns in an Organization v Personal development and Leadership focus v Interpersonal Relations v Communication in an organization v Confidentiality and Information Management v Stress and Anger Management WHO SHOULD ATTEND : Middle Level and Senior Officers in all Corporate, Public, Voluntary and Private entities. A high-powered training session where you'll spend Three Intensive Days immersed in the techniques that will improve your Personal Effectiveness, Efficiency, Team building and Leadership Skills. Program Description and Objectives: This intensive three-day training is a highly interactive forum designed for middle and senior level officers in all entities who want to grow their management skills fast - and get on the fast track to achieving ; more success for their establishments. At the end of the Training Program, Participants will lean how to : * handle key management challenges with ease * conduct effective self-assessment and improve on weak areas * maintain respect and compliance for organizational rules- * establish credibility and authority fast; * motivate employees to give 100 per cent output;- * manage attitude problems and rule-breakers;- * curb absenteeism and tardiness * obtain and give constructive feedback * conduct effective performance appraisals.- * develop listening skills that will lead to conflict resolutions;- * be information security conscious; and- * utilize stress and anger management skills for improved * corporate image. computers and other multi-media to facilitate learning. ACCREDITATION : WODIA is an Accredited Management Training Institution Certified by Centre for Management Development (CMD),Nigeria. PARTICIPATION should be confirmed by calling : 0802 307 9485or 0813 375 4358. You could also send an email to : support@thewodia.org PAYMENT : After confirmation of available spaces, payment should be made at least one week before program into any branch of Zenith Bank Account Number 6011822855 in favour of WODIA Training Institute (WOTI) . ALL PROGRAMS HOLD AT 9.00 A.M DAILY AT THE PREMISES OF : WODIA Training Institute (WOTI), The Boat House, 21, Ogunnusi Road, Ogba, Ikeja, Lagos. Website : www.thewodia.org, Email : support@thewodia.org. Telephone : 0802 307 9485; 08133754358. . TRAINING AIDS: Training Aids to be used include projector and screen, flip charts, magic boards, _____________________________ Unsubscribe / Change Profile: = http://ymlp47.net/u.php?id=3Dgewmweugsgejmmswgyew Powered by YourMailingListProvider From owner-freebsd-stable@FreeBSD.ORG Tue Apr 26 19:09:11 2011 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 D8258106567A for ; Tue, 26 Apr 2011 19:09:11 +0000 (UTC) (envelope-from gkontos.mail@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id A2C828FC19 for ; Tue, 26 Apr 2011 19:09:11 +0000 (UTC) Received: by iwn33 with SMTP id 33so1064691iwn.13 for ; Tue, 26 Apr 2011 12:09:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=YM4QWQpeSCIg8BtnW1z1/NtKFX2lgz+e2/TknriLxyQ=; b=B4K0tAT/udNo2lxH9l7fMfoKVM0IFYPMlbbOcaVobJiVBhf2+/iylCxeITs33fvitf eWWnOLDkposwSkVg/627H7Bp061700TyqZAGATorCZFW71BR2pJX8ACFC53VqqbwVtOM QPmFRIOaiKvvX9OZIa6mqcur//ANK2nRU5TfY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=I8O2THX6fs7p8A4YyDu874//ybc7es268gc0nlckUiUuN9wQcKSHpRhQONTZAP3SaE 9oX4R+OSbtEOIuodOePcqHEDyN6i28pdLn07SwezXc2YBCTsoZrYNEU8aLz81R1QVp0I WwA8Gy/sQN/fYPflQAQ8avJ5+vB6F+zH/yH9E= MIME-Version: 1.0 Received: by 10.231.171.205 with SMTP id i13mr884687ibz.181.1303844950771; Tue, 26 Apr 2011 12:09:10 -0700 (PDT) Received: by 10.231.35.2 with HTTP; Tue, 26 Apr 2011 12:09:10 -0700 (PDT) Date: Tue, 26 Apr 2011 22:09:10 +0300 Message-ID: From: George Kontostanos To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Promise SATA controller issues... 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, 26 Apr 2011 19:09:12 -0000 Greetings all, I have a Promise PDC40718 SATA300 controller running on a box from 8.0-Release since now now on 8.2-Stable 8.2-STABLE FreeBSD 8.2-STABLE #3: Thu Apr 21 15:23:08 EEST 2011. The controller is in jbod mode with 3 WD drives in Raidz1. ad6: 610480MB at ata3-master UDMA100 SATA 3Gb/s ad8: 610480MB at ata4-master UDMA100 SATA 3Gb/s ad10: 610480MB at ata5-master UDMA100 SATA 3Gb/s Today the box became unresponsive so I had to do a hard reset. From /var/log/messages: Apr 25 22:08:35 hp kernel: ata4: SIGNATURE: ffffffff Apr 25 22:08:35 hp kernel: ata4: timeout waiting to issue command Apr 25 22:08:35 hp kernel: ata4: error issuing SETFEATURES SET TRANSFER MODE command Apr 25 22:08:35 hp kernel: ata4: timeout waiting to issue command Apr 25 22:08:35 hp kernel: ata4: error issuing SETFEATURES ENABLE RCACHE command Apr 25 22:08:35 hp kernel: ata4: timeout waiting to issue command Apr 25 22:08:35 hp kernel: ata4: error issuing SETFEATURES ENABLE WCACHE command Apr 25 22:08:35 hp kernel: ata4: timeout waiting to issue command Apr 25 22:08:35 hp kernel: ata4: error issuing SET_MULTI command Apr 25 22:08:41 hp kernel: ata4: SIGNATURE: ffffffff Apr 25 22:08:41 hp kernel: ata4: timeout waiting to issue command Apr 25 22:08:41 hp kernel: ata4: error issuing SETFEATURES SET TRANSFER MODE command Apr 25 22:08:41 hp kernel: ata4: timeout waiting to issue command Apr 25 22:08:41 hp kernel: ata4: error issuing SETFEATURES ENABLE RCACHE command Apr 25 22:08:41 hp kernel: ata4: timeout waiting to issue command Apr 25 22:08:41 hp kernel: ata4: error issuing SETFEATURES ENABLE WCACHE command Apr 25 22:08:41 hp kernel: ata4: timeout waiting to issue command Apr 25 22:08:41 hp kernel: ata4: error issuing SET_MULTI command Apr 25 22:08:44 hp kernel: ata4: SIGNATURE: ffffffff Apr 25 22:08:44 hp kernel: ata4: timeout waiting to issue command ....... Apr 26 20:18:41 hp smartd[1049]: Device: /dev/ad8, failed to read SMART Attribute Data Apr 26 20:18:42 hp kernel: ata4: timeout waiting to issue command Apr 26 20:18:42 hp kernel: ata4: error issuing SMART command Apr 26 20:18:47 hp kernel: ata4: SIGNATURE: ffffffff Apr 26 20:18:47 hp kernel: ata4: timeout waiting to issue command Apr 26 20:18:47 hp kernel: ata4: error issuing SETFEATURES SET TRANSFER MODE command Apr 26 20:18:47 hp kernel: ata4: timeout waiting to issue command Apr 26 20:18:47 hp kernel: ata4: error issuing SETFEATURES ENABLE RCACHE command Apr 26 20:18:47 hp kernel: ata4: timeout waiting to issue command Apr 26 20:18:47 hp kernel: ata4: error issuing SETFEATURES ENABLE WCACHE command Apr 26 20:18:47 hp kernel: ata4: timeout waiting to issue command Apr 26 20:18:47 hp kernel: ata4: error issuing SET_MULTI command Apr 26 20:18:48 hp kernel: ata4: timeout waiting to issue command Apr 26 20:18:48 hp kernel: ata4: error issuing SMART command Apr 26 20:18:54 hp kernel: ata4: SIGNATURE: ffffffff Apr 26 20:18:54 hp kernel: ata4: timeout waiting to issue command Apr 26 20:18:54 hp kernel: ata4: error issuing SETFEATURES SET TRANSFER MODE command Apr 26 20:18:54 hp kernel: ata4: timeout waiting to issue command Apr 26 20:18:54 hp kernel: ata4: error issuing SETFEATURES ENABLE RCACHE command Apr 26 20:18:54 hp kernel: ata4: timeout waiting to issue command Apr 26 20:18:54 hp kernel: ata4: error issuing SETFEATURES ENABLE WCACHE command Apr 26 20:18:54 hp kernel: ata4: timeout waiting to issue command Apr 26 20:18:54 hp kernel: ata4: error issuing SET_MULTI command Apr 26 20:47:49 hp kernel: ata4: SIGNATURE: ffffffff Apr 26 20:47:49 hp kernel: ata4: timeout waiting to issue command Apr 26 20:47:49 hp kernel: ata4: error issuing SETFEATURES SET TRANSFER MODE command Apr 26 20:47:49 hp kernel: ata4: timeout waiting to issue command Apr 26 20:47:49 hp kernel: ata4: error issuing SETFEATURES ENABLE RCACHE command Apr 26 20:47:49 hp kernel: ata4: timeout waiting to issue command Apr 26 20:47:49 hp kernel: ata4: error issuing SETFEATURES ENABLE WCACHE command Apr 26 20:47:49 hp kernel: ata4: timeout waiting to issue command Apr 26 20:47:49 hp kernel: ata4: error issuing SET_MULTI command Apr 26 20:47:49 hp kernel: ad8: TIMEOUT - READ_DMA retrying (1 retry left) LBA=216798592 It appears from the logs that the problem lasted for a full day! However, after the reboot the drive did not perform any resilver and no data loss occurred. I have scrubbed my pool successfully and run smartmon tests also. SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 1466 - It doesn't appear to be a drive issue so I was wondering if the recent changes in controllers that appeared a few days ago might be related. Thanks -- George Kontostanos aisecure.net From owner-freebsd-stable@FreeBSD.ORG Tue Apr 26 19:26:39 2011 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 AC529106564A for ; Tue, 26 Apr 2011 19:26:39 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 338548FC13 for ; Tue, 26 Apr 2011 19:26:38 +0000 (UTC) Received: by bwz12 with SMTP id 12so1159441bwz.13 for ; Tue, 26 Apr 2011 12:26:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=XMNao6RSxfiGtEQXSGf2Y+AM0dQhf+9sONZZqsnLHXI=; b=IWdzyVsgnLtSEDqh1kab95nhvulypjMi7+Z8Kbr+uPV5aeGbceLEqEJNYShhrXn1gy jF3TPIwr3gEe/co/puF5RVEGEd1tz+TyJ6gfjFULurHTGIW+1I+baPujXn2yMUJmt/HA cVL1Q5nyxROjmrZQ2khDMIBXduGZ81qy5VtUc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=WQ0Y31af1aFVQb5eE9WjmSBVBpoR2YCMA+bfuKVvFvCux0y9LOIfEME964LMAuEHtH OHBMA74FBjWxd6PkgeVmYJZyUWuFSjqgpcz0QGGpmZ8dnuXRmv82qQkbpYvVFOm/cjUi XmkHvQvirsKc5PLR/zxK8oIZwuij6Q5HR36Xw= Received: by 10.204.20.134 with SMTP id f6mr1065007bkb.165.1303845997888; Tue, 26 Apr 2011 12:26:37 -0700 (PDT) Received: from mavbook2.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id q18sm20907bka.3.2011.04.26.12.26.36 (version=SSLv3 cipher=OTHER); Tue, 26 Apr 2011 12:26:37 -0700 (PDT) Sender: Alexander Motin Message-ID: <4DB71C65.7070700@FreeBSD.org> Date: Tue, 26 Apr 2011 22:26:29 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.23 (X11/20091212) MIME-Version: 1.0 To: George Kontostanos References: In-Reply-To: X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD Stable Subject: Re: Promise SATA controller issues... 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, 26 Apr 2011 19:26:39 -0000 George Kontostanos wrote: > I have a Promise PDC40718 SATA300 controller running on a box from > 8.0-Release since now now on 8.2-Stable 8.2-STABLE FreeBSD 8.2-STABLE #3: > Thu Apr 21 15:23:08 EEST 2011. The controller is in jbod mode with 3 WD > drives in Raidz1. > > ad6: 610480MB at ata3-master UDMA100 SATA > 3Gb/s > ad8: 610480MB at ata4-master UDMA100 SATA > 3Gb/s > ad10: 610480MB at ata5-master UDMA100 SATA > 3Gb/s > > Today the box became unresponsive so I had to do a hard reset. From > /var/log/messages: > > It appears from the logs that the problem lasted for a full day! However, > after the reboot the drive did not perform any resilver and no data loss > occurred. > I have scrubbed my pool successfully and run smartmon tests also. > > It doesn't appear to be a drive issue so I was wondering if the recent > changes in controllers that appeared a few days ago might be related. There was no changes specific to the Promise controllers for a long time. Mostly because I have no any documentation for them. For the same reason I hardly can say what could be wrong there. Some additional information is definitely required. -- Alexander Motin From owner-freebsd-stable@FreeBSD.ORG Tue Apr 26 19:35:29 2011 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 567D7106566B; Tue, 26 Apr 2011 19:35:29 +0000 (UTC) (envelope-from gkontos.mail@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 0E8778FC16; Tue, 26 Apr 2011 19:35:28 +0000 (UTC) Received: by iyj12 with SMTP id 12so1099409iyj.13 for ; Tue, 26 Apr 2011 12:35:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=XTUGQBOn67FGWy64D/6/ZmJSmVwjabzcueVIn1BboAk=; b=G3w0Ju9tftVqN8yheGENIKaL/38D/tPIpHA5Zu3NEFwpFlNax8PQruaKB/1f46LstM r9uFjkeFLbW/e04BQ6Q2wflLJYGmSp4lNf3J8N68JhbofLafS/YxZUSOKVU3eqUuWliu SpMr1TF34bzRUTnvrSYxNFVxUVJWw3Xlufcog= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=vTM+043k1pFKNjUjo9LgXXoz0qsZC1KjK5X+1B6x0Cuemq7UCBEbUbbEM94UalqNIA 3Br+E/oc99FjjaR7ATiBipJqfi16aC47SkqqEA3CxonpkjHQZ5VLUvTGdOkRofOmEd72 V+ofwS574qNSD5560jfO9pt4ZA5GmGt1ma11w= MIME-Version: 1.0 Received: by 10.43.59.140 with SMTP id wo12mr1271085icb.408.1303846527927; Tue, 26 Apr 2011 12:35:27 -0700 (PDT) Received: by 10.231.35.2 with HTTP; Tue, 26 Apr 2011 12:35:27 -0700 (PDT) In-Reply-To: <4DB71C65.7070700@FreeBSD.org> References: <4DB71C65.7070700@FreeBSD.org> Date: Tue, 26 Apr 2011 22:35:27 +0300 Message-ID: From: George Kontostanos To: Alexander Motin Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: FreeBSD Stable Subject: Re: Promise SATA controller issues... 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, 26 Apr 2011 19:35:29 -0000 Please let me know what kind of information might be also useful. glabel list | grep ad8 Geom name: ad8 Providers: 1. Name: label/zdisk3 Mediasize: 640135028224 (596G) Sectorsize: 512 Mode: r1w1e1 secoffset: 0 offset: 0 seclength: 1250263727 length: 640135028224 index: 0 Consumers: 1. Name: ad8 Mediasize: 640135028736 (596G) Sectorsize: 512 Mode: r1w1e2 dmesg: Copyright (c) 1992-2011 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 8.2-STABLE #3: Thu Apr 21 15:23:08 EEST 2011 gkontos@hp.aicom.loc:/usr/obj/usr/src/sys/ML110G3 amd64 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) D CPU 3.20GHz (3200.13-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0xf64 Family = f Model = 6 Stepping = 4 Features=0xbfebfbff Features2=0xe4bd AMD Features=0x20100800 AMD Features2=0x1 TSC: P-state invariant real memory = 4294967296 (4096 MB) avail memory = 4111331328 (3920 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) 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 acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 cpu1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: irq 16 at device 28.0 on pci0 pci1: on pcib1 pcib2: irq 17 at device 28.5 on pci0 pci7: on pcib2 bge0: mem 0xfeaf0000-0xfeafffff irq 17 at device 0.0 on pci7 bge0: CHIP ID 0x00004101; ASIC REV 0x04; CHIP REV 0x41; PCI-E miibus0: on bge0 brgphy0: PHY 1 on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow bge0: Ethernet address: 00:13:21:cc:39:35 bge0: [ITHREAD] uhci0: port 0xdc00-0xdc1f irq 23 at device 29.0 on pci0 uhci0: [ITHREAD] uhci0: LegSup = 0x2f00 usbus0: on uhci0 uhci1: port 0xd880-0xd89f irq 19 at device 29.1 on pci0 uhci1: [ITHREAD] uhci1: LegSup = 0x2f00 usbus1: on uhci1 uhci2: port 0xd800-0xd81f irq 18 at device 29.2 on pci0 uhci2: [ITHREAD] uhci2: LegSup = 0x2f00 usbus2: on uhci2 ehci0: mem 0xfe9ffc00-0xfe9fffff irq 23 at device 29.7 on pci0 ehci0: [ITHREAD] usbus3: EHCI version 1.0 usbus3: on ehci0 pcib3: at device 30.0 on pci0 pci8: on pcib3 atapci0: port 0xec00-0xec7f,0xe800-0xe8ff mem 0xfebff000-0xfebfffff,0xfebc0000-0xfebdffff irq 16 at device 0.0 on pci8 atapci0: [ITHREAD] atapci0: [ITHREAD] ata2: on atapci0 ata2: [ITHREAD] ata3: on atapci0 ata3: SIGNATURE: 00000101 ata3: [ITHREAD] ata4: on atapci0 ata4: SIGNATURE: 00000101 ata4: [ITHREAD] ata5: on atapci0 ata5: SIGNATURE: 00000101 ata5: [ITHREAD] vgapci0: port 0xe000-0xe0ff mem 0xe8000000-0xefffffff,0xfebb0000-0xfebbffff irq 16 at device 2.0 on pci8 isab0: at device 31.0 on pci0 isa0: on isab0 atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 31.1 on pci0 ata0: on atapci1 ata0: [ITHREAD] atapci2: port 0xd480-0xd487,0xd400-0xd403,0xd080-0xd087,0xd000-0xd003,0xcc00-0xcc0f mem 0xfe9ff800-0xfe9ffbff irq 19 at device 31.2 on pci0 atapci2: [ITHREAD] atapci2: AHCI called from vendor specific driver atapci2: AHCI v1.10 controller with 4 3Gbps ports, PM not supported ata6: on atapci2 ata6: [ITHREAD] ata7: on atapci2 ata7: [ITHREAD] ata8: on atapci2 ata8: [ITHREAD] ata9: on atapci2 ata9: [ITHREAD] acpi_button0: on acpi0 atrtc0: port 0x70-0x71 irq 8 on acpi0 uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 uart0: [FILTER] uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0 uart1: [FILTER] ppc0: port 0x378-0x37f,0x778-0x77f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppc0: [ITHREAD] ppbus0: on ppc0 plip0: on ppbus0 plip0: [ITHREAD] lpt0: on ppbus0 lpt0: [ITHREAD] lpt0: Interrupt-driven port ppi0: on ppbus0 orm0: at iomem 0xc0000-0xc8fff,0xc9000-0xcdfff,0xcf800-0xd47ff,0xd4800-0xd57ff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] est0: on cpu0 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 102400001024 device_attach: est0 attach returned 6 p4tcc0: on cpu0 est1: on cpu1 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 102400001024 device_attach: est1 attach returned 6 p4tcc1: on cpu1 ZFS NOTICE: Prefetch is disabled by default if less than 4GB of RAM is present; to enable, add "vfs.zfs.prefetch_disable=0" to /boot/loader.conf. ZFS filesystem version 4 ZFS storage pool version 15 Timecounters tick every 1.000 msec usbus0: 12Mbps Full Speed USB v1.0 usbus1: 12Mbps Full Speed USB v1.0 usbus2: 12Mbps Full Speed USB v1.0 usbus3: 480Mbps High Speed USB v2.0 ad6: 610480MB at ata3-master UDMA100 SATA 3Gb/s ugen0.1: at usbus0 uhub0: on usbus0 ugen1.1: at usbus1 uhub1: on usbus1 ugen2.1: at usbus2 uhub2: on usbus2 ugen3.1: at usbus3 uhub3: on usbus3 ad8: 610480MB at ata4-master UDMA100 SATA 3Gb/s ad10: 610480MB at ata5-master UDMA100 SATA 3Gb/s ad12: 238475MB at ata6-master UDMA100 SATA 1.5Gb/s ad14: 238475MB at ata7-master UDMA100 SATA 1.5Gb/s SMP: AP CPU #1 Launched! Root mount waiting for: usbus3 usbus2 usbus1 usbus0 uhub0: 2 ports with 2 removable, self powered uhub1: 2 ports with 2 removable, self powered uhub2: 2 ports with 2 removable, self powered Root mount waiting for: usbus3 uhub3: 6 ports with 6 removable, self powered Trying to mount root from zfs:zroot ugen0.2: at usbus0 bge0: link state changed to UP On Tue, Apr 26, 2011 at 10:26 PM, Alexander Motin wrote: > > > There was no changes specific to the Promise controllers for a long > time. Mostly because I have no any documentation for them. For the same > reason I hardly can say what could be wrong there. Some additional > information is definitely required. > > -- > Alexander Motin > -- George Kontostanos aisecure.net From owner-freebsd-stable@FreeBSD.ORG Tue Apr 26 19:39:54 2011 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 375F8106564A for ; Tue, 26 Apr 2011 19:39:54 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id B49208FC1A for ; Tue, 26 Apr 2011 19:39:53 +0000 (UTC) Received: by bwz12 with SMTP id 12so1174077bwz.13 for ; Tue, 26 Apr 2011 12:39:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=sIusT8Qz2MkumX07Lz+k8f+I9csNZsPOJL+UgkyIFjw=; b=TE165SjNGSxjXa3ZbJ/eV4KOpES5/CWKNWRvyIAPy+is3LSMotfYShbJGgp/HOKP7b NfmYV/5cxATmDersNUp9mR1LEg8pINdRgUsaH2aMh3erERS9ci0Ei057bTAb5X+qnGpU PR2Ljs5gw4h6L91tD4sMtYbON5+PSEWhvxknQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=aPOpRr6RdNM1WRcC0tty4+p6ctpieYUgi4kAY9AYRz4VmVf0pXd8OFfMz/l6JD4T3G popJFL504Rn/kKNc6JeOe2WTy3XaYjUkzSMrcndtXLlRX8Pl1MRHQZz0DR3J5PSxxwyP xvmHfjt7rhy5GBo9OszKsYnrQ+fM1L6edPTyk= Received: by 10.204.19.3 with SMTP id y3mr1062025bka.180.1303846792411; Tue, 26 Apr 2011 12:39:52 -0700 (PDT) Received: from mavbook2.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id w3sm21786bkt.17.2011.04.26.12.39.50 (version=SSLv3 cipher=OTHER); Tue, 26 Apr 2011 12:39:51 -0700 (PDT) Sender: Alexander Motin Message-ID: <4DB71F80.8030901@FreeBSD.org> Date: Tue, 26 Apr 2011 22:39:44 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.23 (X11/20091212) MIME-Version: 1.0 To: George Kontostanos References: <4DB71C65.7070700@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD Stable Subject: Re: Promise SATA controller issues... 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, 26 Apr 2011 19:39:54 -0000 George Kontostanos wrote: > Please let me know what kind of information might be also useful. I don't know. What were the first messages before the problem? Was there any specific activity? It would be most useful if you could reproduce the problem in controllable environment. > There was no changes specific to the Promise controllers for a long > time. Mostly because I have no any documentation for them. For the same > reason I hardly can say what could be wrong there. Some additional > information is definitely required. -- Alexander Motin From owner-freebsd-stable@FreeBSD.ORG Tue Apr 26 19:54:16 2011 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 3FEF61065677; Tue, 26 Apr 2011 19:54:16 +0000 (UTC) (envelope-from to.my.trociny@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 3064F8FC08; Tue, 26 Apr 2011 19:54:15 +0000 (UTC) Received: by fxm11 with SMTP id 11so969083fxm.13 for ; Tue, 26 Apr 2011 12:54:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:to:cc:subject:references:x-comment-to :sender:date:in-reply-to:message-id:user-agent:mime-version :content-type; bh=RiItolKCfGfx1gGFXwYNTdSYNqsPihpNCOQcl0mNcmA=; b=rJ4fpT+QIm6z+jaPNSXDxkydbVK7pTxm/4cvnywaY1Y9TqGVxzexokOcdtNzfUW+zB WvCaaJ+pZBe6ysmZ8oeOLyLaFBBK3lGe8Bis2LJlXnutj0A7lvwPRL8J5sHWuw1pPE0N nrQsQ5p7GT8neFpVoq6U5kNbsqI00uHAPWAs4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:subject:references:x-comment-to:sender:date:in-reply-to :message-id:user-agent:mime-version:content-type; b=a5pcH/M+ghrLFxTJIFIVINZg+LFvl/SF/FGA/yn2qcX36Tp3k2a932vIn7rsnhpbwR tH9WKMMI+1hLteMzxmJ9kVqUmYlAUw2yW6ips3h74VxV+WRRcYJ+aPOlseO8YbGjjC1I kcAPEAn0goppIDPcsEhYpiJaKgY2dIl4vMKdU= Received: by 10.223.55.200 with SMTP id v8mr1330131fag.82.1303847653954; Tue, 26 Apr 2011 12:54:13 -0700 (PDT) Received: from localhost ([95.69.172.154]) by mx.google.com with ESMTPS id x16sm15240fal.43.2011.04.26.12.54.11 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 26 Apr 2011 12:54:12 -0700 (PDT) From: Mikolaj Golub To: Pawel Jakub Dawidek References: <926783796.20110423022501@nitronet.pl> <20110423005422.GQ91591@over-yonder.net> <2910134705.20110423090442@nitronet.pl> <20110423125247.GA89102@icarus.home.lan> <20110423143838.GR91591@over-yonder.net> <86mxjd1h4w.fsf@in138.ua3> <20110426162509.GB1979@garage.freebsd.pl> X-Comment-To: Pawel Jakub Dawidek Sender: Mikolaj Golub Date: Tue, 26 Apr 2011 22:54:09 +0300 In-Reply-To: <20110426162509.GB1979@garage.freebsd.pl> (Pawel Jakub Dawidek's message of "Tue, 26 Apr 2011 18:25:09 +0200") Message-ID: <86oc3syeji.fsf@kopusha.home.net> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: kib@FreeBSD.org, Pawel Tyll , freebsd-stable@freebsd.org, Jeremy Chadwick , "Matthew D. Fuller" Subject: Re: buildworld FAIL. 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, 26 Apr 2011 19:54:16 -0000 On Tue, 26 Apr 2011 18:25:09 +0200 Pawel Jakub Dawidek wrote: PJD> On Tue, Apr 26, 2011 at 12:44:31PM +0300, Mikolaj Golub wrote: >> >> On Sat, 23 Apr 2011 09:38:39 -0500 Matthew D. Fuller wrote: >> >> MDF> On Sat, Apr 23, 2011 at 05:52:47AM -0700 I heard the voice of >> MDF> Jeremy Chadwick, and lo! it spake thus: >> >> On Sat, Apr 23, 2011 at 09:04:42AM +0200, Pawel Tyll wrote: >> >> > So was NO_OPENSSL deprecated or something? >> >> >> >> I think he's implying that hast indirectly relies upon OpenSSL. >> >> MDF> There's some conditionalization on MK_OPENSSL in the Makefile (and via >> MDF> that, in the code), but it's incomplete. Whether that means it >> MDF> _should_ be buildable without OpenSSL and is just insufficiently >> MDF> tested, or whether it really just flat needs OpenSSL and the >> MDF> conditionalization is vestigial, I don't know. pjd@ cc'd. >> >> The attached patch should fix this. PJD> The patch looks good. Please commit. Thanks. Committed. -- Mikolaj Golub From owner-freebsd-stable@FreeBSD.ORG Tue Apr 26 19:57:06 2011 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 5DC7E106566B; Tue, 26 Apr 2011 19:57:06 +0000 (UTC) (envelope-from gkontos.mail@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 185828FC12; Tue, 26 Apr 2011 19:57:05 +0000 (UTC) Received: by iyj12 with SMTP id 12so1121915iyj.13 for ; Tue, 26 Apr 2011 12:57:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=qPKhoNDykm+0Z9bln2CJQBq1QeeKTITeKKC7ng7jiv4=; b=LJcJ3pW3KwjEpIx3u3U3hERX1fnwpxcGKJT4/o5LCoCeYH+JokGIA5SyHSIsZtMtdZ uuDEFthVGdSGozx3x1Bh1ii91QtPTo8DcY2sfbl+JLtvGjxQw287ALu8Hn9tc7pFRkFh aBBR6hW6uaZHdJ5wccUH23xWWyYXQ169pLzhw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=BKdnuIJumXGdgDXtYnn6ihwYmeNbDXAft0ruLOd9q0cyb/nVSrhllpVjQSpQmx4SyA RncZaH7ID8dJ68sG2pR9ZoOZx8rZSrqJQyX3fLrkDAHzdIV8xXdUTqI3yCqthuXKmBGD sTGXc3uDdYA9ASWqGm2yeNds+pM05RyiXoDGo= MIME-Version: 1.0 Received: by 10.42.96.65 with SMTP id i1mr1521632icn.274.1303847825350; Tue, 26 Apr 2011 12:57:05 -0700 (PDT) Received: by 10.231.35.2 with HTTP; Tue, 26 Apr 2011 12:57:05 -0700 (PDT) In-Reply-To: <4DB71F80.8030901@FreeBSD.org> References: <4DB71C65.7070700@FreeBSD.org> <4DB71F80.8030901@FreeBSD.org> Date: Tue, 26 Apr 2011 22:57:05 +0300 Message-ID: From: George Kontostanos To: Alexander Motin Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: FreeBSD Stable Subject: Re: Promise SATA controller issues... 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, 26 Apr 2011 19:57:06 -0000 The system was up since April 21 when I upgraded to the latest world && kernel. There are 2 pools, a mirror with root on ZFS for the OS and a Raidz1 just for the data. hp# zpool status pool: tank state: ONLINE scrub: scrub completed after 1h30m with 0 errors on Tue Apr 26 22:48:32 2011 config: NAME STATE READ WRITE CKSUM tank ONLINE 0 0 0 raidz1 ONLINE 0 0 0 label/zdisk1 ONLINE 0 0 0 label/zdisk2 ONLINE 0 0 0 label/zdisk3 ONLINE 0 0 0 errors: No known data errors pool: zroot state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM zroot ONLINE 0 0 0 mirror ONLINE 0 0 0 gpt/disk0 ONLINE 0 0 0 gpt/disk1 ONLINE 0 0 0 The server is a SOHO fileserver with a few other services: sshd_enable="YES" named_enable="YES" #Caching name server samba_enable="YES" dhcpd_enable="YES" squid_enable="YES" apcupsd_enable="YES" apache22_enable="YES" mysql_enable="YES" syslogd_flags="-a 10.10.10.1" #Cisco Pix logging snmpd_enable="YES" nagios_enable="YES" munin_node_enable="YES" bsdstats_enable="YES" smartd_enable="YES" There was nothing out of the ordinary before this except some repeated power failures that where handled by the UPS as you can see in the logs: Apr 24 20:33:53 hp apcupsd[870]: Power failure. Apr 24 20:33:55 hp apcupsd[870]: Power is back. UPS running on mains. Apr 24 20:38:03 hp apcupsd[870]: Power failure. Apr 24 20:38:04 hp apcupsd[870]: Power is back. UPS running on mains. Apr 24 21:45:47 hp apcupsd[870]: Power failure. Apr 24 21:45:49 hp apcupsd[870]: Power is back. UPS running on mains. Apr 24 22:43:56 hp apcupsd[870]: Power failure. Apr 24 22:43:57 hp apcupsd[870]: Power is back. UPS running on mains. Apr 24 23:05:46 hp apcupsd[870]: Power failure. Apr 24 23:05:47 hp apcupsd[870]: Power is back. UPS running on mains. Apr 25 00:20:32 hp apcupsd[870]: Power failure. Apr 25 00:20:33 hp apcupsd[870]: Power is back. UPS running on mains. Apr 25 01:23:22 hp apcupsd[870]: Power failure. Apr 25 01:23:23 hp apcupsd[870]: Power is back. UPS running on mains. Apr 25 06:26:40 hp apcupsd[870]: Power failure. Apr 25 06:26:42 hp apcupsd[870]: Power is back. UPS running on mains. Apr 25 11:05:03 hp apcupsd[870]: Power failure. Apr 25 11:05:04 hp apcupsd[870]: Power is back. UPS running on mains. Apr 25 13:05:20 hp apcupsd[870]: Power failure. Apr 25 13:05:21 hp apcupsd[870]: Power is back. UPS running on mains. Apr 25 13:32:48 hp apcupsd[870]: Power failure. Apr 25 13:32:50 hp apcupsd[870]: Power is back. UPS running on mains. Apr 25 13:35:06 hp apcupsd[870]: Power failure. Apr 25 22:08:35 hp kernel: ata4: SIGNATURE: ffffffff Apr 25 22:08:35 hp kernel: ata4: timeout waiting to issue command Apr 25 22:08:35 hp kernel: ata4: error issuing SETFEATURES SET TRANSFER MODE command ......... On Tue, Apr 26, 2011 at 10:39 PM, Alexander Motin wrote: > George Kontostanos wrote: > > Please let me know what kind of information might be also useful. > > I don't know. What were the first messages before the problem? Was there > any specific activity? It would be most useful if you could reproduce > the problem in controllable environment. > > > There was no changes specific to the Promise controllers for a long > > time. Mostly because I have no any documentation for them. For the > same > > reason I hardly can say what could be wrong there. Some additional > > information is definitely required. > > -- > Alexander Motin > -- George Kontostanos aisecure.net From owner-freebsd-stable@FreeBSD.ORG Tue Apr 26 20:03:40 2011 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 D74561065673 for ; Tue, 26 Apr 2011 20:03:40 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 5E2678FC08 for ; Tue, 26 Apr 2011 20:03:40 +0000 (UTC) Received: by bwz12 with SMTP id 12so1199871bwz.13 for ; Tue, 26 Apr 2011 13:03:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=KqT8v2sKJnIfFAIQW1s3OGrNFq+Gvl99N5ogYt18n10=; b=c1L+gpyZTZxLAZEMoN1uNRfiSujIX/b86B3cXtfBtFxAgAFixE1QT5R3csONzfxBLj rj8U+0qHOFjHGq5pKCvFqnrvqUFvI1v3rfBRODU3XYFX2uEnIdy/nFry4tmJ6eaaTWRT flstWnNwrRRnwJ/f/Wl16ZeUr1/v5B1FG2VX0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=dk8FmwlxNkfY4ii8ynhlQJJtIbu34ODFjr4EIVo/3+4uNvqOBSCB3oFTp3e5r4JDHW qv62Rc472c05oIZZqXHxpKnQ5wVX48XahauFyd1grZ7xQE1mbZOaxBHFotDh7Lds5SmG 7R4EO7Ho2DIa3C2pp6ciA2cy6q2toeDiXf2+Y= Received: by 10.204.19.80 with SMTP id z16mr1101617bka.198.1303848218917; Tue, 26 Apr 2011 13:03:38 -0700 (PDT) Received: from mavbook2.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id l1sm32768bkl.13.2011.04.26.13.03.37 (version=SSLv3 cipher=OTHER); Tue, 26 Apr 2011 13:03:38 -0700 (PDT) Sender: Alexander Motin Message-ID: <4DB72512.4050001@FreeBSD.org> Date: Tue, 26 Apr 2011 23:03:30 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.23 (X11/20091212) MIME-Version: 1.0 To: George Kontostanos References: <4DB71C65.7070700@FreeBSD.org> <4DB71F80.8030901@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD Stable Subject: Re: Promise SATA controller issues... 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, 26 Apr 2011 20:03:41 -0000 George Kontostanos wrote: > The system was up since April 21 when I upgraded to the latest world && > kernel. > There are 2 pools, a mirror with root on ZFS for the OS and a Raidz1 > just for the data. > > There was nothing out of the ordinary before this except some repeated > power failures that where handled by the UPS as you can see in the logs: > > Apr 25 13:05:21 hp apcupsd[870]: Power is back. UPS running on mains. > Apr 25 13:32:48 hp apcupsd[870]: Power failure. > Apr 25 13:32:50 hp apcupsd[870]: Power is back. UPS running on mains. > Apr 25 13:35:06 hp apcupsd[870]: Power failure. > Apr 25 22:08:35 hp kernel: ata4: SIGNATURE: ffffffff > Apr 25 22:08:35 hp kernel: ata4: timeout waiting to issue command > Apr 25 22:08:35 hp kernel: ata4: error issuing SETFEATURES SET TRANSFER > MODE command > ......... I would enable verbose kernel messages for case it it repeats again. May be it gives some more understanding. But that's not a fact. > On Tue, Apr 26, 2011 at 10:39 PM, Alexander Motin > wrote: > > George Kontostanos wrote: > > Please let me know what kind of information might be also useful. > > I don't know. What were the first messages before the problem? Was there > any specific activity? It would be most useful if you could reproduce > the problem in controllable environment. > > > There was no changes specific to the Promise controllers for a > long > > time. Mostly because I have no any documentation for them. For > the same > > reason I hardly can say what could be wrong there. Some additional > > information is definitely required. -- Alexander Motin From owner-freebsd-stable@FreeBSD.ORG Wed Apr 27 06:08:51 2011 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 0D7641065670 for ; Wed, 27 Apr 2011 06:08:51 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id A013D8FC12 for ; Wed, 27 Apr 2011 06:08:50 +0000 (UTC) Received: by fxm11 with SMTP id 11so1305931fxm.13 for ; Tue, 26 Apr 2011 23:08:49 -0700 (PDT) Received: by 10.223.57.86 with SMTP id b22mr514288fah.95.1303884529614; Tue, 26 Apr 2011 23:08:49 -0700 (PDT) Received: from jessie.localnet (p5B2ECEF3.dip0.t-ipconnect.de [91.46.206.243]) by mx.google.com with ESMTPS id t2sm116863faa.47.2011.04.26.23.08.44 (version=SSLv3 cipher=OTHER); Tue, 26 Apr 2011 23:08:45 -0700 (PDT) Sender: Bernhard Schmidt From: Bernhard Schmidt To: Gardner Bell Date: Wed, 27 Apr 2011 08:07:51 +0200 User-Agent: KMail/1.13.5 (Linux/2.6.32-31-generic; KDE/4.4.5; i686; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201104270807.51592.bschmidt@freebsd.org> Cc: freebsd-stable@freebsd.org Subject: Re: Fatal trap 12: page fault while in kernel mode X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bschmidt@freebsd.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 06:08:51 -0000 On Tuesday, April 26, 2011 17:35:32 Gardner Bell wrote: > On Tue, Apr 26, 2011 at 04:25:26PM +0200, Bernhard Schmidt wrote: > > On Tuesday, April 26, 2011 15:15:45 Gardner Bell wrote: > > > On Tue, Apr 26, 2011 at 4:12 AM, Bernhard Schmidt wrote: > > > > On Tuesday, April 26, 2011 01:09:42 Gardner Bell wrote: > > > >> Downloading a torrent with many peers on a toshiba satellite notebook > > > >> using an Atheros AR5006 wireless nic caused the following panic. This > > > >> is an i386 system running 8.2-STABLE from around April 06. > > > > > > > > Can you reproduce that? > > > > > > So far I've not been able to reproduce this. > > > > Ok. I assume this only happens when loosing the connection and trying > > to re-associate. At least that is the only possible scenario I can > > think of where a timeout for mgmt frames is involved. Probably we > > aren't bumping a refcount correctly or something. Actually that sounds > > rather plausible as it panics exactly when trying to access ni which > > should, for a station, always point to iv_bss, which can in turn be > > free'd almost unconditionally if someone's telling net80211 to > > associate to another (or even the same) network. Hmm.. tracing refcount > > it is. > > > > Were you running wpa_supplicant at that point? Any messages before > > the panic happened? > > > > Yes, I'm running wpa_supplicant with the following settings: > > network={ > ssid="xxxxx" > psk="xxxxx" > } > > Other settings for the wireless card I have in rc.conf: > > wlans_ath0="wlan0" > ifconfig_wlan0="WPA DHCP" > ifconfig_wlan0_alias0="inet 192.168.0.12 netmask 0xffffffff" > > > The last messages seen on the console before the panic are wlan0: > ieee80211_new_state_locked: pending SCAN -> AUTH transition lost > and several UP/DOWN events. That's what I expected, thanks. I'll try to come up with something. -- Bernhard From owner-freebsd-stable@FreeBSD.ORG Wed Apr 27 10:58:24 2011 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 5E12E106582B; Wed, 27 Apr 2011 10:58:24 +0000 (UTC) (envelope-from danger@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 494C58FC12; Wed, 27 Apr 2011 10:58:24 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p3RAwOAe062697; Wed, 27 Apr 2011 10:58:24 GMT (envelope-from danger@freefall.freebsd.org) Received: (from danger@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p3RAwO7G062696; Wed, 27 Apr 2011 10:58:24 GMT (envelope-from danger) Date: Wed, 27 Apr 2011 10:58:24 +0000 From: Daniel Gerzo To: current@freebsd.org Message-ID: <20110427105824.GA62682@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.4.2.3i Cc: stable@freebsd.org, hackers@freebsd.org Subject: FreeBSD Status Report January-March, 2011 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, 27 Apr 2011 10:58:24 -0000 FreeBSD Quarterly Status Report January-March, 2011 Introduction This report covers FreeBSD-related projects between January and March 2011. It is the first of the four reports planned for 2011. During this quarter, the work was focused on releasing the new minor versions of FreeBSD, 7.4 and 8.2, which were released in February 2011. Currently, the project is starting to work on the next major version, 9.0. Thanks to all the reporters for the excellent work! This report contains 34 entries and we hope you enjoy reading it. Please note that the deadline for submissions covering the period between April and June 2011 is July 15th, 2011. __________________________________________________________________ Projects * Bringing up OMAP3 * GEOM-based ataraid(4) Replacement -- geom_raid. * HAST (Highly Available Storage) * New FreeBSD Installer * OpenAFS Port * pfSense * RCTL, aka Resource Containers * ZFSv28 available in FreeBSD 9-CURRENT FreeBSD Team Reports * FreeBSD Bugbusting Team * FreeBSD NYI Admins Status Report * The FreeBSD Foundation Status Report Network Infrastructure * DIstributed Firewall and Flow-shaper Using Statistical Evidence (DIFFUSE) * Five New TCP Congestion Control Algorithms for FreeBSD Kernel * Journaled Soft Updates * Linux Compatibility Layer - DVB and V4L2 Support Documentation * New FreeBSD Handbook Section Covering HAST * The FreeBSD German Documentation Project Status Report * The FreeBSD Japanese Documentation Project * Webcam and DVB Compatibility List Architectures * FreeBSD/arm on Marvell Raid-on-Chip * FreeBSD/EC2 * FreeBSD/powerpc on Freescale QorIQ * MIPS/Octeon Support and bootinfo Ports * FreeBSD as Home Theater PC * FreeBSD Chromium * FreeBSD Haskell Ports * KDE-FreeBSD * Linux Emulation Ports * Portmaster * Ports Collection * www/apache22 Default Miscellaneous * BSDCan Google Summer of Code * Extfs Status Report * Google Summer of Code 2011 __________________________________________________________________ Bringing up OMAP3 Contact: Warner Losh Contact: Mohammed Farrag OMAP3 Emulation: * Step #1: qemu-omap3 isn't ported to FreeBSD yet. So, * Step #2: Use qemu-omap3 on Gentoo Host .. * Step #3: Is the end reached ?! No, bcz qemu-omap3 is not full. So, go to step #4. * Step #4: Use Meego >> Download Ubuntu 10.10 >> Install it, and * Step #5: Compile FreeBSD kernel, Create root file system, mkimage, Emulate using Meego. Open tasks: 1. Device Drivers for OMAP3 Processors. __________________________________________________________________ BSDCan URL: http://www.bsdcan.org/2011/ Contact: Dan Langille Our list of talks has been settled, and the schedule is pretty much finalized. There is still time to get into the Works In Progress session. Best to book your on-campus accommodation now. Or stay at one of the nearby hotels. Open tasks: 1. Show up. Enjoy. Profit. __________________________________________________________________ DIstributed Firewall and Flow-shaper Using Statistical Evidence (DIFFUSE) URL: http://caia.swin.edu.au/urp/diffuse/ URL: http://caia.swin.edu.au/urp/diffuse/downloads.html Contact: Sebastian Zander Contact: Grenville Armitage DIFFUSE is a system enabling FreeBSD's IPFW firewall subsystem to classify IP traffic based on statistical traffic properties. With DIFFUSE, IPFW computes statistics (such as packet lengths or inter-packet time intervals) for observed flows, and uses ML (machine learning) to classify flows into classes. In addition to traditional packet inspection rules, IPFW rules may now also be expressed in terms of traffic statistics or classes identified by ML classification. This can be helpful when direct packet inspection is problematic (perhaps for administrative reasons, or because port numbers do not reliably identify applications). DIFFUSE also enables one instance of IPFW to send flow information and classes to other IPFW instances, which then can act on such traffic (e.g. prioritise, accept, deny, etc.) according to its class. This allows for distributed architectures, where classification at one location in your network is used to control fire-walling or rate-shaping actions at other locations. DIFFUSE is a set of patches for FreeBSD-CURRENT. It can be downloaded from the project's web site. The web site also contains a more comprehensive introduction, including application examples, links to related work and documentation. In February 2011 we released DIFFUSE v0.2.2. This release contains a number of bug fixes and new features. Most notably since version 0.2 there is a tool to build classifier models, and there is a feature module and classifier model to classify Skype traffic. We hope to release DIFFUSE v0.3 soon. Keep an eye on the freebsd-ipfw and freebsd-net mailing lists for project-related announcements. __________________________________________________________________ Extfs Status Report URL: http://p4web.FreeBSD.org/@md=d&cd=//depot/projects/soc2010/extfs/src/sy s/fs/&c=rFV@//depot/projects/soc2010/extfs/src/sys/fs/ext2fs/?ac=83 URL: http://p4web.FreeBSD.org/@md=d&cd=//depot/projects/soc2010/ext4fs/src/s ys/fs/&c=cc4@//depot/projects/soc2010/ext4fs/src/sys/fs/ext4fs/?ac=83 Contact: Zheng Liu I have implemented a reallocblks in ext2fs, like in ffs, and submitted a patch file to mailing list. Next I will try to implement htree directory index in ext2fs. __________________________________________________________________ Five New TCP Congestion Control Algorithms for FreeBSD URL: http://caia.swin.edu.au/freebsd/5cc/ URL: http://caia.swin.edu.au/urp/newtcp/ URL: http://www.FreeBSDFoundation.org/projects.shtml URL: http://FreeBSDfoundation.blogspot.com/2011/03/summary-of-five-new-tcp-c ongestion.html URL: http://people.FreeBSD.org/~lstewart/patches/5cc/ Contact: David Hayes Contact: Lawrence Stewart Contact: Grenville Armitage Contact: Rui Paulo Contact: Bjoern Zeeb The project is now complete, with the following code available in the svn head branch: * Modular congestion control framework. * Khelp (Kernel Helper) and Hhook (Helper Hook) frameworks. * Basic Khelp/Hhook integration with the TCP stack. * Enhanced Round Trip Time (ERTT) Khelp module. * Modularised implementations of NewReno, CUBIC, H-TCP, Vegas, Hamilton-Delay and CAIA-Hamilton-Delay congestion control algorithms. In addition to the code, a large set of documentation was committed (see the following man pages: cc(4), cc_newreno(4), cc_cubic(4), cc_htcp(4), cc_vegas(4), cc_hd(4), cc_chd(4), h_ertt(4), cc(9), khelp(9), hhook(9)) and a technical report was released which evaluates the computational overhead associated with TCP before and after the project's changes. A candidate patch to MFC the modular congestion control framework to the 8-STABLE branch is ready for testing here. If you try the patch, please send a note detailing your experience (positive or negative) to Lawrence Stewart. Thanks go to the FreeBSD Foundation for funding this work, to the project's technical reviewers for providing detailed feedback, and to all FreeBSD users who have provided testing feedback thus far. Open tasks: 1. Test 8-STABLE MFC candidate patch and do the merge in time for 8.3-RELEASE. __________________________________________________________________ FreeBSD as Home Theater PC URL: http://wiki.FreeBSD.org/HTPC Contact: Bernhard Froehlich Contact: Juergen Lock FreeBSD could be a much better platform for a Home Theater PC than it currently is. We are focusing on improving support for media center applications by extending the major ports (MythTV, VDR, XBMC) and creating some documentation to guide interested people. In the last months we continued to work on HTPC relevant ports, improved lirc and multimedia/webcamd remote control support. The last missing major HTPC application VDR (Video Disk Recorder) has finally been committed to the portstree as multimedia/vdr including 17 vdr plugin ports. Open tasks: 1. Improve remote control support in webcamd and with lirc. 2. Port more Media Center applications (Enna, me-tv, ...) 3. Create a small guide on how to build a great FreeBSD Home Theater PC. __________________________________________________________________ FreeBSD Bugbusting Team URL: http://www.FreeBSD.org/support.html#gnats URL: http://wiki.FreeBSD.org/BugBusting URL: http://people.FreeBSD.org/~linimon/studies/prs/ Contact: Gavin Atkinson Contact: Mark Linimon Contact: Remko Lodder Contact: Volker Werth The bugmeister team is happy to welcome Eitan Adler (eadler@) as the newest GNATS-only contributor. Eitan has been helping triage new bugs as they come in, as well as making good progress on many of the older bugs, closing duplicates and obsolete bugs and contacting submitters for extra information where necessary. For the first time in a long time we managed to get below 6000 open PRs, in no small part due to Eitan's efforts. Welcome aboard! PRs continue to be classified as they arrive, by adding 'tags' to the subject lines corresponding to the kernel subsystem involved, or man page references for userland PRs. Reports are generated from these nightly, grouping related PRs into one place, sorted by tag or man page. This allows an interested party working in one area or on one subsystem to easily find related bugs and issues in the same area, which has proven quite effective in getting some of the older bug reports closed. These reports can all be found by following the third link above. We continue to look for ideas for other reports that may help improve the PR closure rate. If you have any suggestions for reports which would contribute positively to the way you work, please email bugmeister@ and we shall try to produce such a report. Our clearance rate of PRs, especially in kern and bin, seems to be improving. The number of non-ports PRs has stayed almost constant since the last status report. As always, anybody interested in helping out with the PR queue is welcome to join us in #freebsd-bugbusters on EFnet. We are always looking for additional help, whether your interests lie in triaging incoming PRs, generating patches to resolve existing problems, or simply helping with the database housekeeping (identifying duplicate PRs, ones that have already been resolved, etc). This is a great way of getting more involved with FreeBSD! Open tasks: 1. Try to find ways to get more committers helping us with closing PRs that the team has already analyzed. __________________________________________________________________ FreeBSD Chromium URL: http://trillian.chruetertee.ch/chromium URL: http://lists.FreeBSD.org/mailman/listinfo/freebsd-chromium URL: http://www.chromium.org/Home Contact: FreeBSD Chromium Team Thanks to a great collaborative effort from the FreeBSD community, the OpenBSD community, and the Chromium developers, Chromium has been updated in the Ports tree. In the spirit of release early and release often, updates to Chromium happen frequently. The contributors of the FreeBSD Chromium team have demonstrated great agility in keeping pace with updates in the development repository hosted at http://trillian.chruetertee.ch/chromium. Open tasks: 1. A task that lies ahead is working with the Chromium developers at integrating the FreeBSD patches into the codebase. Volunteers are welcome. __________________________________________________________________ FreeBSD Haskell Ports URL: http://wiki.FreeBSD.org/Haskell URL: https://github.com/freebsd-haskell/freebsd-haskell URL: http://haskell.org/mailman/listinfo/freebsd-haskell/ Contact: Gbor Jnos PLI Contact: Ashish SHUKLA Contact: Giuseppe Pilichi We are proud to announce that the FreeBSD Haskell team has updated GHC to 7.0.3, and all other existing Haskell ports to the latest stable versions, as well as added new ports. The total number of Haskell ports in the FreeBSD repository is now more than 200. These ports are still waiting to be committed. At the moment, they are available from FreeBSD Haskell ports repository. Any users who would like to get early access to them, please refer to the FreeBSD Haskell ports Call For Testing. Open tasks: 1. Create a metaport for Haskell Platform. 2. Create a port for Happstack. 3. Create a port for gitit. __________________________________________________________________ FreeBSD NYI Admins Status Report Contact: NYI Admins Team The FreeBSD.org site at New York Internet is progressing, though more slowly than we had hoped. Due to problems with the old power controllers and serial console servers, new equipment has been bought by the FreeBSD Foundation. Installing the new equipment required re-racking all the existing servers which was done by the local FreeBSD team (Steven Kreuzer and John Baldwin). For basic infrastructure at the site (such as DHCP, DNS, console etc.) the FreeBSD Foundation bought some new servers which are in the process of being configured. The FreeBSD Ports team are currently using 9 of the NYI servers for package building. Open tasks: 1. We are looking for a storage system (15TB+) for keeping replicas of all the main FreeBSD.org systems, a full ftp-archive mirror, site local files etc. __________________________________________________________________ FreeBSD/arm on Marvell Raid-on-Chip Contact: Grzegorz Bernacki Contact: Rafal Jaworowski Marvell 88RC8180 is an integrated RAID-on-Chip controller, based on the Feroceon 88FR331 CPU core (ARMv5TE). The 88RC9580 is a next generation version, based on the Sheeva 88SV581 CPU core (ARMv6) of this system-on-chip devices family. Current FreeBSD suppport for 88RC8180 and 88RC9580 includes: * Booting via U-Boot bootloader * L1, L2 cache * Serial console support (UART) * Interrupt controller * Integrated timers * PCI Express (root complex and endpoint modes) * Doorbells and messages * Ethernet controller Open tasks: 1. Complete, clean up, merge with HEAD. __________________________________________________________________ FreeBSD/EC2 URL: http://www.daemonology.net/freebsd-on-ec2/ Contact: Colin Percival FreeBSD is now able to run on t1.micro and cc1.4xlarge instances in the Amazon EC2 cloud. FreeBSD 8.2-RELEASE is stable subject to the limitations of the instance type (e.g., running ZFS on a micro instance with only 600 MB of RAM doesn't work very well), but FreeBSD 9.0 has significant stability issues. A list of available FreeBSD AMIs (EC2 machine images) appears on the FreeBSD/EC2 status page. Open tasks: 1. Bring FreeBSD to a wider range of EC2 instance types. 2. Completely rework the locking in head/sys/i386/xen/pmap.c to eliminate races and make 9.0-CURRENT stable under paravirtualization. 3. Track down several possibly-related problems with scheduling and timekeeping. 4. Fix other issues shown on the FreeBSD/EC2 status page. __________________________________________________________________ FreeBSD/powerpc on Freescale QorIQ Contact: Michal Dubiel Contact: Rafal Jaworowski QorIQ is a brand of Power Architecture-based communications microprocessors from Freescale. It is an evolutionary step from the PowerQUICC platform (MPC85xx) and is built around one or more Power Architecture e500/e500mc cores. This work is bringing up FreeBSD on these system-on-chip devices along with device drivers for integrated peripherials. Current FreeBSD QorIQ support includes: * QorIQ P2020 support * Booting via U-Boot bootloader * L1, L2 cache * Serial console (UART) * Interrupt controller * Ethernet (TSEC, SGMII mode) * I2C * EHCI controller (no Transaction Translation Unit) * Security Engine (SEC) 3.1 * PCI Express controller (host mode) * Enhanced SDHC (no MMC support) * Dual-core (SMP) support __________________________________________________________________ GEOM-based ataraid(4) Replacement -- geom_raid. Contact: Alexander Motin Contact: M. Warner Losh A new RAID GEOM class (geom_raid) was added to FreeBSD 9-CURRENT, to replace ataraid(4) in supporting various BIOS-based software RAIDs. Unlike ataraid(4) this implementation does not depend on legacy ata(4) subsystem and can be used with any disk drivers, including new CAM-based ones (ahci(4), siis(4), mvs(4) and ata(4) with `options ATA_CAM`). To make code more readable and extensible, this implementation follows modular design, including a core part and two sets of modules, implementing support for different metadata formats and RAID levels. Support for such popular metadata formats is now implemented: Intel, JMicron, NVIDIA, Promise (also used by AMD/ATI) and SiliconImage. Such RAID levels are now supported: RAID0, RAID1, RAID1E, RAID10, SINGLE, CONCAT. For any all of these RAID levels and metadata formats this class supports full cycle of volume operations: reading, writing, creation, deletion, disk removal and insertion, rebuilding, dirty shutdown detection and resynchronization, bad sector recovery, faulty disks tracking, hot-spare disks. For Intel and Promise formats there is support for multiple volumes per disk set. See the graid(8) manual page for additional details. Sponsored by: Cisco Systems, Inc. and iXsystems, Inc. Open tasks: 1. Implement metadata modules for other formats (DDF, Highpoint, VIA, ...). 2. Implement transformation modules for other RAID levels (RAID5, ...). __________________________________________________________________ Google Summer of Code 2011 URL: http://www.google-melange.com/gsoc/org/google/gsoc2011/freebsd URL: http://wiki.freebsd.org/SummerOfCode2011 Contact: Brooks Davis Contact: Robert Watson FreeBSD is proud to be participating in our seventh year of Google Summer of Code. On Monday, April 25th we accepted 17 proposals from an overall excellent field. A full list of accepted proposals can be found on the GSoC website. We look forward to working with these students over the summer. As we did last year we plan to ask students to submit weekly status reports to the soc-status mailing list. Those wishing to keep up with the work in progress and offer review may wish to subscribe. __________________________________________________________________ HAST (Highly Available Storage) Contact: Pawel Jakub Dawidek Contact: Mikolaj Golub HAST development is progressing nicely. Mikolaj Golub who contributes to HAST is now a FreeBSD src committer. Some changes worth noting since the last report: * Compression of the data being sent over the network. This can speed up especially synchronization process. * Optional checksuming for the data being send over the network. * Capsicum sandboxing for secondary node and hastctl. * Chroot+setuid+setgid sandboxing for primary node. * Allow administrators to specify source IP address for connections. * When changing role wait for a while for the other node to switch from primary to secondary to avoid split-brain. * Many bug fixes. __________________________________________________________________ Journaled Soft Updates Contact: Jeff Roberson Contact: Kirk McKusick All known problems with journaled soft updates have been fixed in head. If you have any problems while running with journaled soft updates, please report them to us. We have addressed several performance issues that have been brought to our attention. If you have any performance problems while running with journaled soft updates, please report them to us. We have improved the recovery of resources when running with soft updates on small (root) filesystems. We anticipate being able to use soft updates for root filesystems in the 9.0 system. We expect to have journaled soft updates default to enabled in the 9.0 system. We encourage users of -CURRENT to enable journaled soft updates to help shake out any remaining performance problems and bugs. __________________________________________________________________ KDE-FreeBSD URL: http://FreeBSD.kde.org Contact: KDE FreeBSD The KDE on FreeBSD team have continued to improve the experience of KDE and Qt under FreeBSD. The latest round of improvements include: * Improved shared resources (i.e. pixmaps for KDE) * Improved file monitoring (using kevent) * Improved KSysGuard support (new and refined sensors) The team have also made many releases and upstreamed many fixes and patches. The latest round of releases include: * Qt: 4.7.2 * KDE: 4.5.5; 4.6.1; 4.6.2 * KOffice: 2.3.3 * KDevelop: 4.2.0; 4.2.2 (KDevPlatform: 1.2.0; 1.2.2) * many smaller ports The team needs more testers and porters so please visit us at kde-freebsd@kde.org Open tasks: 1. Continue improvements of KSysGuard. 2. General maintenance. 3. General testing. 4. Porting. __________________________________________________________________ Linux Compatibility Layer - DVB and V4L2 Support URL: http://people.FreeBSD.org/~nox/dvb/ Contact: Juergen Lock Following (separate) discussions on the mailing lists I have made patches to add DVB and V4L2 ioctl translation support to the Linux compatibility layer, allowing Linux apps like SageTV, Skype, and Flash to use DVB/ATSC tuners and webcams that previously only worked for native FreeBSD apps. (Most of this hardware uses Linux drivers via the multimedia/webcamd port.) Open tasks: 1. Handle the remaining ioctls that (I think) are not used by DVB tuners/cameras supported by webcamd (it only supports USB devices, the unhandled ioctls mostly have to do with video overlays and hardware MPEG2 decoding on analog or DVB tuners, features that AFAIK don't exist on USB hardware.) 2. Make the DVB support a port because there were concerns putting it in base due to the LGPL in one of the header files even though I already separated out the code into an extra kld. (linux_dvbwrapper.ko) 3. Get the patches polished and committed. :) (Until they are you can check my DVB page and the freebsd-emulation@ mailing list for updates.) __________________________________________________________________ Linux Emulation Ports URL: http://www.leidinger.net/blog/2011/02/25/howto-creating-your-own-update d-linux-rpm-for-the-freebsd-linuxulator/ Contact: Alexander Leidinger Contact: Emulation Mailinglist Old linux_base ports (all which are not used by default in some release) where marked as deprecated with a short expiration period. The reason is that all those ports are long past their end of life and do not receive security updates anymore. Unfortunately this is also true for the linux_base ports which are still used by default in the releases, but no replacement is available ATM (see open tasks). The linux-f10-pango port was updated to a more recent version whoch does not have a security problem by generating a linux-RPM in a VM with "FreeBSD" as the vendor (see the links section for a HOWTO). Open tasks: 1. Decide which RPM based linux distribution+version to track next for the linux_base ports, create ports for it and test for compatibility with our kernel code. __________________________________________________________________ MIPS/Octeon Support and bootinfo Contact: Andrew Duane Working on improving support for Octeon processors and integrating with other MIPS processor families. Currently working on support for the standard MIPS bootinfo structure as a boot API (to supplement/replace the Caviums-specific structure). Other Octeon improvements including cleanups to CF and USB drivers to come. __________________________________________________________________ New FreeBSD Handbook Section Covering HAST URL: http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/disks-hast.ht ml Contact: Daniel Gerzo A new FreeBSD Handbook section covering the Highly Available STorage, or HAST developed by Pawel Jakub Dawidek has been recently added. In this section, you will learn what HAST is, how it works, which features it provides and how to set it up. It also includes a working example on how it can be used together with devd(8) and CARP. Enjoy your reading. __________________________________________________________________ New FreeBSD Installer URL: http://wiki.FreeBSD.org/BSDInstall URL: http://wiki.FreeBSD.org/PCBSDInstallMerge Contact: Nathan Whitehorn On March 14th, sysinstall was replaced on the 9.0 snapshot media by a new, modular installer called BSDInstall. This adds support for a wide variety of new features while simplifying the installation process. Testing before the 9.0 release will be very much appreciated -- CD and memory stick images for a variety of platforms are linked from the BSDInstall wiki page. Interesting features: * Install CD media are always live CDs * Installations spanning multiple disks * Wireless setup * GPT disk formatting * Virtualization friendly: can install from a live system onto disk images * Easily hackable and more modular than sysinstall * Greater flexibility: shells available throughout the installation Work is presently ongoing to integrate this installer with the backend provided by pc-sysinstall (second wiki link). Open tasks: 1. ZFS installation support. 2. IA64 disk setup. __________________________________________________________________ OpenAFS Port URL: http://openafs.org URL: http://web.mit.edu/freebsd/openafs/openafs.shar Contact: Benjamin Kaduk Contact: Derrick Brashear AFS is a distributed network filesystem that originated from the Andrew Project at Carnegie-Mellon University. The OpenAFS client implementation has not been particularly useful on FreeBSD since the FreeBSD 4.X releases. Work covered in previous reports brought the OpenAFS client to a useful form on 9.0-CURRENT, though with some rough edges. Since our last report, we have fixed several bugs that were impacting usability, and we expect the upcoming 1.6.0 release to be usable for regular client workloads (though not heavy load). Accordingly, we have submitted packaging for inclusion in the Ports Collection (PR ports/152467). There are several known outstanding issues that are being worked on, but detailed bug reports are welcome at port-freebsd@openafs.org. Open tasks: 1. Update VFS locking to allow the use of disk-based client caches as well as memory-based caches. 2. Track down races and deadlocks that may appear under load. 3. Integrate with the bsd.kmod.mk kernel-module build infrastructure. 4. Eliminate a moderate memory leak from the kernel module. 5. PAG (Process Authentication Group) support is not functional. __________________________________________________________________ pfSense URL: www.pfsense.org Contact: Scott Ullrich Contact: Chris Buechler Contact: Ermal Luci Work on 2.0 is rapidly coming to an end. We released RC1 around Feb 25 2011 and so far it seems to be rather stable. 2.0 is our first major release in 2 years and almost all limitations of the previous version has been overcome. Open tasks: 1. Finish testing RC1 and certify for release. __________________________________________________________________ Portmaster URL: http://dougbarton.us/portmaster-proposal.html Contact: Doug Barton The latest version of portmaster contains numerous improvements aimed at large-scale enterprise users. Particularly, support for the --index-only/--packages-only code has been significantly improved. Some of the highlights include: * New --update-if-newer option which takes a list of ports and/or a glob pattern on the command line and only updates those that are out of date. This feature is very useful for ensuring that the packages needed for updating a system are all available and up to date on the package building system. * The portmaster.rc file can now be stored in the same directory as the script itself, which aids in shared access to the script (for example over an NFS mount) * More features now work (or work better) with --index-only, including --check-depends Open tasks: 1. I have received some support for items E.2 and E.3 on the web page listed above so I will be putting some effort into those areas in the coming months. I also have in mind to split out the "fetch" code to be its own script, in part to support goal E.2, and to allow for more efficient parallelization when downloading multiple distfiles (especially for multiple ports that download the same distfile). This will also allow me to set a global limit for the number of parallel fetches which should aid users on slow links. __________________________________________________________________ Ports Collection URL: http://www.FreeBSD.org/ports/ URL: http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/ URL: http://portsmon.FreeBSD.org/index.html URL: http://www.FreeBSD.org/portmgr/index.html URL: http://blogs.FreeBSDish.org/portmgr/ URL: http://www.twitter.com/freebsd_portmgr/ URL: http://www.facebook.com/group.php?gid=135441496471197 URL: http://tinderbox.marcuscom.com/ Contact: Thomas Abthorpe Contact: Port Management Team The ports tree slowly moves up closer to 23,000. The PR count still remains at about 1000. In Q1 we added 2 new committers, and took in 4 commit bits for safe keeping. After a year of serving as the team secretary, Thomas Abthorpe's membership was upgraded to full voting status. The Ports Management team have been running -exp runs on an ongoing basis, verifying how base system updates may affect the ports tree, as well as providing QA runs for major ports updates. Of note, -exp runs were done for: * erwin did a clang -exp run, and sent results to interested parties * kde@ requested an -exp run for KDE 4.6.1 and Qt 4.7.2 * linimon -exp for update of default zope version to 3.2 * miwi performed the following -exp runs, make fetch-original, xorg, cmake, pear, kde4 / py-qt / sip, and python2.7 * mm requested an -exp run to test the last GPLv2 version of gcc 4.2.2 * pav completed open-motif and mono -exp runs for respective submitters * ports/127214, -exp run to make copy/paste of portaudit user friendly * ports/144482, -exp run to fix package depends * ports/152102, -exp run to make dirrmtry more friendly * ports/152268, -exp run to update binutils * ports/153539, -exp run to allow checking STRIP when WITH_DEBUG is defined * ports/153547, -exp run to remove NO_SIZE * ports/153625, -exp run to pass CPPFLAGS to MAKE/CONFIGURE_ENV * ports/153634, -exp run to remove redundant PKGNAMEPREFIX for localised ports * ports/154121, -exp run to use --title for new libdialog * ports/154122, -exp run to update libtool to 2.4 * ports/154186, -exp to allow using linux 2.4 emulation on FreeBSD 8+ * ports/154390, -exp run to make fetching output copy/paste friendly * ports/154653, -exp run to remove superfluous slash * ports/154799, -exp run to update glib + gtk * ports/154994, -exp run for MASTER_SITE_PERL_CPAN enhancements * ports/155502, -exp run to remove sanity check for X_WINDOW_SYSTEM * ports/155504, -exp run to remove USE_XPM from b.p.m. * ports/155505, -exp run to update GNU m4 Open tasks: 1. Looking for help fixing ports broken on CURRENT. 2. Looking for help with Tier-2 architectures. 3. Most ports PRs are assigned, we now need to focus on testing, committing and closing. __________________________________________________________________ RCTL, aka Resource Containers Contact: Edward Tomasz Napierala Most of the code has already been merged into CURRENT. There are two remaining problems I would like to solve before 9.0-RELEASE - see below - but otherwise, the code is stable; please test and report any problems. You will need to rebuild the kernel with "options RACCT" and "options RCTL". The rctl(8) manual page should be a good introduction on how to use it. This project was sponsored by The FreeBSD Foundation. Open tasks: 1. Reimplementing %CPU accounting and CPU throttling. 2. Making jail rules persistent - right now, one cannot add jail rule before that jail is created, which makes it impossible to put them into /etc/rctl.conf; also, rules disappear when jail gets destroyed. __________________________________________________________________ The FreeBSD Foundation Status Report URL: http://www.FreeBSDfoundation.org Contact: Deb Goodkin We created our 2011 budget. Some of our plans for 2011 include spending $125,000 on project development and $75,000 on equipment to build up FreeBSD facilities in three locations. We were proud to be a sponsor for AsiaBSDCon 2011 in Tokyo. We also committed to sponsoring BSDCan 2011 in May, and EuroBSDCon 2011 in October. The Foundation was also represented at SCALE in Los Angeles, Indiana LinuxFest in Indianapolis, and Flourish in Chicago. Completed Foundation-funded projects: Five New TCP Congestion Control Algorithms project by Swinburne University and Resource Containers project by Edward Napierala. In February we visited companies in the Bay Area that use FreeBSD. Our goal was to promote FreeBSD, better understand their interests and needs, and help facilitate stronger relationships between these companies and the Project. The presentations we gave included the benefits of FreeBSD, Project road-map, potential areas of collaboration, case studies, and how the Foundation supports the project. By visiting in person we were able to show our commitment to the Project and respond directly to questions and concerns they may have had. We were pleased with the positive responses we received and plan on visiting more companies in the future. We are funding two new projects. The first project is Implementing Support of GEM, KMS, and DRI for Intel Drivers by Konstantin Belousov. The second is Improving the Maturity of IPv6 Support of FreeBSD and PC-BSD by Bjoern Zeeb. We continued our work on infrastructure projects to beef up hardware for package-building, network-testing, etc. This includes purchasing equipment as well as managing equipment donations. Stop by and visit with us at BSDCan (May 13-14) and SouthEast LinuxFest (June 10-12). The work above as well as many other tasks we do for the project, couldn't be done without donations. Please help us by making a donation or asking your company to make a donation. We would be happy to send marketing literature to you or your company. Find out how to make a donation at http://www.FreeBSDfoundation.org/donate/. __________________________________________________________________ The FreeBSD German Documentation Project Status Report URL: http://doc.bsdgroup.de Contact: Johann Kois Contact: Benedict Reuschling Benedict Reuschling contributed the translation of the new handbook section about HAST, while Benjamin Lukas was working on the first translation of the firewall chapter of the handbook. The committers to the German Documentation Project were busy with keeping the existing German documentation up-to-date. The website translations were also kept in sync with the ones on FreeBSD.org. We tried to re-activate committers who did not contribute for some time but most of them are currently unable to free up enough time. We hope to gain fresh contributor blood as we are getting occasional reports about bugs and grammar in the german translation. Open tasks: 1. Submit grammar, spelling or other errors you find in the german documents and the website. 2. Translate more articles and other open handbook sections. __________________________________________________________________ The FreeBSD Japanese Documentation Project URL: http://www.FreeBSD.org/ja/ URL: http://www.jp.FreeBSD.org/doc-jp/ Contact: Hiroki Sato Contact: Ryusuke Suzuki The www/ja and doc/ja_JP.eucJP/books/handbook have constantly been updated. During this period, translation of the handbook installation page was finished. The following chapters are now synchronized with the English version: * introduction * install * ports * x11 * desktop * multimedia * mirrors * pgpkeys Merging translation results from the www tree on a separate repository for the translation work into the main tree was also finished. Since outdated and/or non-translated documents also remain in both doc/ja_JP.eucJP and www, further translation work is still needed. Some progress has been made in the Porter's Handbook as well in this period. __________________________________________________________________ Webcam and DVB Compatibility List URL: http://wiki.FreeBSD.org/WebcamCompat Contact: Matthias Apitz Webcam and DVB Compatibility List This is the FreeBSD Webcam, DVB, and Remote Control Compatibility List. The main goal of this page is to give an exact answer about which application works with a given cam or DVB. Combinations of the hardware and software mentioned in this table are known to work. Please add more lines to the table or ask me to do so by just sending a mail with your Cam/DVB information. Please note: you should only add information you have seen working and not you may think of or imagine that they could work. The contact information (name and/or email addr) is optional. Open tasks: 1. Move this to a real database in where FreeBSD enduser could self insert their gadgets, like the FreeBSD Laptop Compat List. __________________________________________________________________ www/apache22 Default URL: http://people.FreeBSD.org/~pgollucci/FreeBSD/prs/maintainers.html#apach e URL: http://www.FreeBSD.org/cgi/query-pr.cgi?pr=ports/147009 URL: http://wiki.FreeBSD.org/Apache URL: http://lists.FreeBSD.org/pipermail/freebsd-apache/2011-March/002174.htm l Contact: Philip Gollucci Contact: Olli Hauer Contact: Apache Apache 95% done, pending final -exp run, and pulling the switch. HEADS-UP announcement already sent to relevant lists. This will be for 8.3/9.0. __________________________________________________________________ ZFSv28 available in FreeBSD 9-CURRENT Contact: Pawel Jakub Dawidek Contact: Martin Matuska ZFS v28 is now in HEAD! Test, test, test and test. Pretty please. New features include: * Data deduplication. * Triple parity RAIDZ (RAIDZ3). * zfs diff. * zpool split. * Snapshot holds. * zpool import -F. Allows to rewind corrupted pool to earlier transaction group. * Possibility to import pool in read-only mode. From owner-freebsd-stable@FreeBSD.ORG Wed Apr 27 12:05:07 2011 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 D9EA11065673 for ; Wed, 27 Apr 2011 12:05:07 +0000 (UTC) (envelope-from linuxmail@4lin.net) Received: from mail.4lin.net (mail.4lin.net [46.4.210.97]) by mx1.freebsd.org (Postfix) with ESMTP id 8BB348FC0A for ; Wed, 27 Apr 2011 12:05:07 +0000 (UTC) Received: from localhost (angelica.4lin.net [127.0.0.1]) by mail.4lin.net (Postfix) with ESMTP id A1B6B2E060 for ; Wed, 27 Apr 2011 14:09:26 +0200 (CEST) X-Virus-Scanned: amavisd-new at mail.4lin.net Received: from mail.4lin.net ([127.0.0.1]) by localhost (mail.4lin.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M7-11uVUBEj6 for ; Wed, 27 Apr 2011 14:09:23 +0200 (CEST) Received: from [130.83.160.152] (pcdenny.rbg.informatik.tu-darmstadt.de [130.83.160.152]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.4lin.net (Postfix) with ESMTPSA id 7F9B52D5DA for ; Wed, 27 Apr 2011 14:09:23 +0200 (CEST) From: Denny Schierz To: freebsd-stable In-Reply-To: <86ipv1ll4f.fsf@kopusha.home.net> References: <1301397421.11113.250.camel@pcdenny> <86ipv1ll4f.fsf@kopusha.home.net> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-xAeYeyhglNwB2RsVVH75" Date: Wed, 27 Apr 2011 14:05:11 +0200 Message-ID: <1303905911.4232.86.camel@pcdenny> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Subject: Re: way for failover zpool (no HAST needed) 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, 27 Apr 2011 12:05:07 -0000 --=-xAeYeyhglNwB2RsVVH75 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable hi, Am Dienstag, den 29.03.2011, 23:36 +0300 schrieb Mikolaj Golub: >=20 > 2) There are complaints from watchdog.=20 what happens, if the watchdog isn't available and one or both nodes are rebooting or something else? the other thing what could happen: the connection between the host and the SAS switch is death. carp, ifstate and hastmon looking for the reachable IP, but not, if the local storage is available. So I have a closer look to devd and zfs and shutdown in case of problems the carp interface / or whole machine, to force a switch. cu denny --=-xAeYeyhglNwB2RsVVH75 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEABECAAYFAk24BnQACgkQKlzhkqt9P+Dz/QCfd4NMjZW6dHVhMfoZ0BpSHrCu oaIAnjVadyqabgadbSsRg3kwAt/P0urd =00RP -----END PGP SIGNATURE----- --=-xAeYeyhglNwB2RsVVH75-- From owner-freebsd-stable@FreeBSD.ORG Wed Apr 27 12:20:28 2011 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 77BC9106566B for ; Wed, 27 Apr 2011 12:20:28 +0000 (UTC) (envelope-from linuxmail@4lin.net) Received: from mail.4lin.net (mail.4lin.net [46.4.210.97]) by mx1.freebsd.org (Postfix) with ESMTP id 3157B8FC24 for ; Wed, 27 Apr 2011 12:20:27 +0000 (UTC) Received: from localhost (angelica.4lin.net [127.0.0.1]) by mail.4lin.net (Postfix) with ESMTP id 051D72E063 for ; Wed, 27 Apr 2011 14:24:49 +0200 (CEST) X-Virus-Scanned: amavisd-new at mail.4lin.net Received: from mail.4lin.net ([127.0.0.1]) by localhost (mail.4lin.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ua4OMYBLBmUN for ; Wed, 27 Apr 2011 14:24:46 +0200 (CEST) Received: from [130.83.160.152] (pcdenny.rbg.informatik.tu-darmstadt.de [130.83.160.152]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.4lin.net (Postfix) with ESMTPSA id D7BE42D5DA for ; Wed, 27 Apr 2011 14:24:45 +0200 (CEST) From: Denny Schierz To: freebsd-stable Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-IQlT83v/b9VL1cZe5Cei" Date: Wed, 27 Apr 2011 14:20:34 +0200 Message-ID: <1303906834.4232.91.camel@pcdenny> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Subject: MPS driver: force bus rescan after remove SAS cable 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, 27 Apr 2011 12:20:28 -0000 --=-IQlT83v/b9VL1cZe5Cei Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable hi, if I remove the SAS cable from the JBOD (connected through a SAS switch), all disks disappears, that's fine and expected, but if I reconnect the cable, the disks are not added anymore. I've red to use "camcontrol rescan all", but nothing happens. I don't get my /dev/da0-47 devices anymore and have to reboot the whole machine. What is my mistake? cu denny --=-IQlT83v/b9VL1cZe5Cei Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEABECAAYFAk24ChIACgkQKlzhkqt9P+COQQCfbMpIU5u2ovRJpwhKTHYIFovK d+kAnRpmntKYxiZNa86mIJ4K185Utl/o =NjhM -----END PGP SIGNATURE----- --=-IQlT83v/b9VL1cZe5Cei-- From owner-freebsd-stable@FreeBSD.ORG Wed Apr 27 12:51:26 2011 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 5C392106564A for ; Wed, 27 Apr 2011 12:51:26 +0000 (UTC) (envelope-from linuxmail@4lin.net) Received: from mail.4lin.net (mail.4lin.net [46.4.210.97]) by mx1.freebsd.org (Postfix) with ESMTP id 1523B8FC13 for ; Wed, 27 Apr 2011 12:51:25 +0000 (UTC) Received: from localhost (angelica.4lin.net [127.0.0.1]) by mail.4lin.net (Postfix) with ESMTP id 646702E069 for ; Wed, 27 Apr 2011 14:55:45 +0200 (CEST) X-Virus-Scanned: amavisd-new at mail.4lin.net Received: from mail.4lin.net ([127.0.0.1]) by localhost (mail.4lin.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jCuZF6sg7uQL for ; Wed, 27 Apr 2011 14:55:42 +0200 (CEST) Received: from [130.83.160.152] (pcdenny.rbg.informatik.tu-darmstadt.de [130.83.160.152]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.4lin.net (Postfix) with ESMTPSA id 37AEA2D5DA for ; Wed, 27 Apr 2011 14:55:42 +0200 (CEST) From: Denny Schierz To: freebsd-stable In-Reply-To: <1303906834.4232.91.camel@pcdenny> References: <1303906834.4232.91.camel@pcdenny> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-RS/OVNgB5481/7Y1Zovo" Date: Wed, 27 Apr 2011 14:51:30 +0200 Message-ID: <1303908690.4232.95.camel@pcdenny> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Subject: Re: MPS driver: force bus rescan after remove SAS cable 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, 27 Apr 2011 12:51:26 -0000 --=-RS/OVNgB5481/7Y1Zovo Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable hi, Am Mittwoch, den 27.04.2011, 14:20 +0200 schrieb Denny Schierz: > I've red to use "camcontrol rescan all", but nothing happens. I don't > get my /dev/da0-47 devices anymore and have to reboot the whole machine. small update: I've tested it again and only some disks appear again, but not all. any suggestions? cu denny --=-RS/OVNgB5481/7Y1Zovo Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEABECAAYFAk24EUsACgkQKlzhkqt9P+AQ2wCgk0dkR5gvyyyaXEvfK0fjMMIB BZ4AnicAaP7Gyo0nIV+4aAU6j178fUgq =X3OI -----END PGP SIGNATURE----- --=-RS/OVNgB5481/7Y1Zovo-- From owner-freebsd-stable@FreeBSD.ORG Wed Apr 27 12:57:41 2011 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 84ACC1065675 for ; Wed, 27 Apr 2011 12:57:41 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta15.westchester.pa.mail.comcast.net (qmta15.westchester.pa.mail.comcast.net [76.96.59.228]) by mx1.freebsd.org (Postfix) with ESMTP id 2EFE38FC0A for ; Wed, 27 Apr 2011 12:57:40 +0000 (UTC) Received: from omta18.westchester.pa.mail.comcast.net ([76.96.62.90]) by qmta15.westchester.pa.mail.comcast.net with comcast id ccjP1g0031wpRvQ5Fcxh7s; Wed, 27 Apr 2011 12:57:41 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta18.westchester.pa.mail.comcast.net with comcast id ccxe1g00Z1t3BNj3ecxeq3; Wed, 27 Apr 2011 12:57:40 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id D677B9B418; Wed, 27 Apr 2011 05:57:36 -0700 (PDT) Date: Wed, 27 Apr 2011 05:57:36 -0700 From: Jeremy Chadwick To: Denny Schierz Message-ID: <20110427125736.GA1977@icarus.home.lan> References: <1303906834.4232.91.camel@pcdenny> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1303906834.4232.91.camel@pcdenny> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable Subject: Re: MPS driver: force bus rescan after remove SAS cable 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, 27 Apr 2011 12:57:41 -0000 On Wed, Apr 27, 2011 at 02:20:34PM +0200, Denny Schierz wrote: > hi, > > if I remove the SAS cable from the JBOD (connected through a SAS > switch), all disks disappears, that's fine and expected, but if I > reconnect the cable, the disks are not added anymore. > I've red to use "camcontrol rescan all", but nothing happens. I don't > get my /dev/da0-47 devices anymore and have to reboot the whole machine. > > What is my mistake? Does resetting the bus then rescanning improve things at all? E.g. for bus 0 (use "all" only if it's safe): camcontrol reset 0 camcontrol rescan 0 I'm doubting it will. This is the first time I've heard of something called a SAS switch (looks like a SAS expander to me), but searching the Web indicates that most of these devices have a form of firmware/administrative interface on them, which means it's highly likely that the device itself is "getting in the way". Meaning: what's to say the issue is with FreeBSD and not with the SAS switch? To me, my first choice of action would be to contact the device vendor and ask what the behaviour should be. If there's some sort of device with an ASIC in between your disks and the controller (which is the case here), that could be responsible for what you're seeing. Or, if the hot-swap backplane has something like SES (not a typo) or a QLogic GEM chip on it, that could be causing some issues. (In the case of the latter on our SCSI systems at work, we change the physical SCSI cabling in our systems to remove the GEM from the bus entirely, otherwise it does odd things like tries to renumber the SCSI IDs on devices during a failure, and more often than not locks the entire SCSI controller up). Bottom line: less actual stuff between the disk and the controller the better. :-) -- | Jeremy Chadwick jdc@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 Wed Apr 27 13:39:06 2011 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 4108A1065672 for ; Wed, 27 Apr 2011 13:39:06 +0000 (UTC) (envelope-from linuxmail@4lin.net) Received: from mail.4lin.net (mail.4lin.net [46.4.210.97]) by mx1.freebsd.org (Postfix) with ESMTP id EE52F8FC0A for ; Wed, 27 Apr 2011 13:39:05 +0000 (UTC) Received: from localhost (angelica.4lin.net [127.0.0.1]) by mail.4lin.net (Postfix) with ESMTP id 81C5C2E073 for ; Wed, 27 Apr 2011 15:43:25 +0200 (CEST) X-Virus-Scanned: amavisd-new at mail.4lin.net Received: from mail.4lin.net ([127.0.0.1]) by localhost (mail.4lin.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 286_tu9ByrAj for ; Wed, 27 Apr 2011 15:43:17 +0200 (CEST) Received: from [130.83.160.152] (pcdenny.rbg.informatik.tu-darmstadt.de [130.83.160.152]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.4lin.net (Postfix) with ESMTPSA id 975A82D5DA for ; Wed, 27 Apr 2011 15:43:17 +0200 (CEST) From: Denny Schierz To: freebsd-stable In-Reply-To: <20110427125736.GA1977@icarus.home.lan> References: <1303906834.4232.91.camel@pcdenny> <20110427125736.GA1977@icarus.home.lan> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-pCwkahB2uVpQCRAdqkA2" Date: Wed, 27 Apr 2011 15:39:05 +0200 Message-ID: <1303911545.4232.124.camel@pcdenny> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Subject: Re: MPS driver: force bus rescan after remove SAS cable 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, 27 Apr 2011 13:39:06 -0000 --=-pCwkahB2uVpQCRAdqkA2 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable hi, Am Mittwoch, den 27.04.2011, 05:57 -0700 schrieb Jeremy Chadwick: > camcontrol reset 0 0:22:0 is available, 0:46:0 not: root@iscsihead-m:~# camcontrol reset 0:22:0 Reset of 0:22:0 was successful root@iscsihead-m:~# camcontrol reset 0:46:0 camcontrol: cam_open_btl: no passthrough device found at 0:46:0 We bought the LSI SAS6160 switch: http://www.lsi.com/storage_home/products_home/sas_switch/sas6100/index.html use the LSI 9200-8e hostbusadapter and LSI JBODs 630j. We had a lot of e-mail conversation with LSI and they mean, that we need the switch for a clear failover setup. Also a reason for the switch: increase storage with more jbods. Every jbod has his own cable to the (later) redundant switch. Otherwise we have to build a "bus" from JBOD to JBOD to JBOD to JBOD to host ... bad idea ;-) The question is, what does the driver while FreeBSD starts? With Solaris10 we didn't have such a problem like this ... strange. cu denny --=-pCwkahB2uVpQCRAdqkA2 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEABECAAYFAk24HHQACgkQKlzhkqt9P+CcYwCeMUvOB9yE8jk1eic2xJDwExcL WlsAoJlZto6lx+r2NiSCogBEyj0SliaK =StLT -----END PGP SIGNATURE----- --=-pCwkahB2uVpQCRAdqkA2-- From owner-freebsd-stable@FreeBSD.ORG Wed Apr 27 14:09:29 2011 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 72E04106567B for ; Wed, 27 Apr 2011 14:09:29 +0000 (UTC) (envelope-from to.my.trociny@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id EF97D8FC22 for ; Wed, 27 Apr 2011 14:09:28 +0000 (UTC) Received: by wwc33 with SMTP id 33so1739002wwc.31 for ; Wed, 27 Apr 2011 07:09:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:to:cc:subject:organization:references :sender:date:in-reply-to:message-id:user-agent:mime-version :content-type; bh=vJGeDr/w7mlDf6kT6M2UmVIgQyj/XhuMdKeo9eSYvow=; b=XV5xlcgv91ZM7W67TbWhhRcxQQ6IuHIoLQh+hjxIRrRP/qUTmShCb/u3PMHZxkwUdi 8Fi73c3AbLcmJe03tlS0lNt+nsonOJAkb0HC6Z1lqWeZc59lh6yGw3ckbtOxNlya0Fia AYvn9SI1rYp93uuVxFS4wa/flMZPn5T43RQ+M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:subject:organization:references:sender:date:in-reply-to :message-id:user-agent:mime-version:content-type; b=l5O9rfjgD3JX45vCRnbY03hdCeWSsYZx+9ufqF5NOyCcP/oVIJhh0+8jDOBwejmW80 Unxv6IErwq3nVIixLKhZyet0oMcArBmlxeJ8MGAME2qJz+H6PFV+mrY54Nznf4Kpprq2 unJOiOLDDcLFvgXoSUkg5oDaXYYEKmY5NjL98= Received: by 10.216.241.197 with SMTP id g47mr2099274wer.110.1303913367785; Wed, 27 Apr 2011 07:09:27 -0700 (PDT) Received: from localhost ([94.27.39.186]) by mx.google.com with ESMTPS id k76sm386900wej.19.2011.04.27.07.09.25 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 27 Apr 2011 07:09:26 -0700 (PDT) From: Mikolaj Golub To: Denny Schierz Organization: TOA Ukraine References: <1301397421.11113.250.camel@pcdenny> <86ipv1ll4f.fsf@kopusha.home.net> <1303905911.4232.86.camel@pcdenny> Sender: Mikolaj Golub Date: Wed, 27 Apr 2011 17:09:23 +0300 In-Reply-To: <1303905911.4232.86.camel@pcdenny> (Denny Schierz's message of "Wed, 27 Apr 2011 14:05:11 +0200") Message-ID: <861v0nrdkc.fsf@in138.ua3> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-stable Subject: Re: way for failover zpool (no HAST needed) 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, 27 Apr 2011 14:09:29 -0000 On Wed, 27 Apr 2011 14:05:11 +0200 Denny Schierz wrote: DS> hi, DS> Am Dienstag, den 29.03.2011, 23:36 +0300 schrieb Mikolaj Golub: >> >> 2) There are complaints from watchdog. DS> what happens, if the watchdog isn't available and one or both nodes are DS> rebooting or something else? Without receiving complaints secondary wont switch to primary. This is done intentionally, so the node does not make decision on its own. But you can have several watchdogs if this really worries you. DS> the other thing what could happen: the connection between the host and DS> the SAS switch is death. DS> carp, ifstate and hastmon looking for the reachable IP, but not, if the DS> local storage is available. So I have a closer look to devd and zfs and hastmon isn't just looking if the IP reachable. watchdog connects to a cluster node and ask its status. So the result depends on how smart the script one use to get the status. DS> shutdown in case of problems the carp interface / or whole machine, to DS> force a switch. DS> cu denny -- Mikolaj Golub From owner-freebsd-stable@FreeBSD.ORG Wed Apr 27 15:37:04 2011 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 90EC01065694 for ; Wed, 27 Apr 2011 15:37:04 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 16F318FC23 for ; Wed, 27 Apr 2011 15:37:03 +0000 (UTC) Received: by bwz12 with SMTP id 12so2123066bwz.13 for ; Wed, 27 Apr 2011 08:37:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=mH6HfLS8lmbHTYrwMVE2u1P4Wr4BnqQEl3rLotgsnwE=; b=nWI4TERvbO5qXOR2mYLH102lnZqnJmzKDCuZU3hpAlRBNfgxtfzjPAm/p+IHh8qizk XR2bAb4+0d1/q/H4mD+/Hkw0/qOSJnNWkLGVqjYfdDvTnKC3C77ti8N/HXHazBOjBXyg JclIc9zzI6Resx4PErkA1NKrHJq8+59kvfx18= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=n70AiyP4pJ/Aqr5E+faYfTzWylDNFBJMNt/RDQvGDS8idPHpjeiRqPSZSAVIiBI+n8 cYziDeIROzxsu01Othi+qlzuIrn8xaipK5TGKyCLd0bhGxwmlq0wI9whp1Yw35JwzmZs wnMagjvwucK4WbSmKhZywEx3e6AvxzHcevRPs= Received: by 10.204.22.197 with SMTP id o5mr2154617bkb.68.1303918622733; Wed, 27 Apr 2011 08:37:02 -0700 (PDT) Received: from mavbook.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id 16sm502007bkm.6.2011.04.27.08.37.01 (version=SSLv3 cipher=OTHER); Wed, 27 Apr 2011 08:37:02 -0700 (PDT) Sender: Alexander Motin Message-ID: <4DB8381B.4030408@FreeBSD.org> Date: Wed, 27 Apr 2011 18:36:59 +0300 From: Alexander Motin User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110310 Thunderbird/3.1.9 MIME-Version: 1.0 To: Denny Schierz References: <20110427125736.GA1977@icarus.home.lan> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Stable Subject: Re: MPS driver: force bus rescan after remove SAS cable 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, 27 Apr 2011 15:37:04 -0000 On 27.04.2011 16:39, Denny Schierz wrote: > Am Mittwoch, den 27.04.2011, 05:57 -0700 schrieb Jeremy Chadwick: >> camcontrol reset 0 > > 0:22:0 is available, 0:46:0 not: > > root@iscsihead-m:~# camcontrol reset 0:22:0 > Reset of 0:22:0 was successful > > root@iscsihead-m:~# camcontrol reset 0:46:0 > camcontrol: cam_open_btl: no passthrough device found at 0:46:0 You should reset whole bus, not the specific LUN. Full reset doesn't need that passthrough device. IIRC it works via xpt0. > We bought the LSI SAS6160 switch: > > http://www.lsi.com/storage_home/products_home/sas_switch/sas6100/index.html > > use the LSI 9200-8e hostbusadapter and LSI JBODs 630j. We had a lot of > e-mail conversation with LSI and they mean, that we need the switch for > a clear failover setup. > Also a reason for the switch: increase storage with more jbods. Every > jbod has his own cable to the (later) redundant switch. Otherwise we > have to build a "bus" from JBOD to JBOD to JBOD to JBOD to host ... bad > idea ;-) > > The question is, what does the driver while FreeBSD starts? CAM exactly does full bus reset and after few seconds full rescan. What controller driver may do except it depends on it alone. -- Alexander Motin From owner-freebsd-stable@FreeBSD.ORG Wed Apr 27 18:44:33 2011 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 65B5E1065672 for ; Wed, 27 Apr 2011 18:44:33 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 205478FC1D for ; Wed, 27 Apr 2011 18:44:32 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1QF9ix-0005QF-Dx for freebsd-stable@freebsd.org; Wed, 27 Apr 2011 20:44:31 +0200 Received: from p5dcd6b31.dip.t-dialin.net ([93.205.107.49]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 27 Apr 2011 20:44:31 +0200 Received: from jumper99 by p5dcd6b31.dip.t-dialin.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 27 Apr 2011 20:44:31 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: "Helmut Schneider" Date: Wed, 27 Apr 2011 18:44:17 +0000 (UTC) Lines: 28 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: p5dcd6b31.dip.t-dialin.net User-Agent: XanaNews/1.19.1.320 X-Ref: news.gmane.org ~XNS:00000163 X-Antivirus: avast! (VPS 110427-1, 27.04.2011), Outbound message X-Antivirus-Status: Clean Subject: panic, but /var/crash ist empty 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, 27 Apr 2011 18:44:33 -0000 Hi, running 8.2-RELEASE-p1 within VMWare ESXi 4.1-u1 I want to use raw devices as hard disks. I create the devices using this link: http://www.mattiasholm.com/node/33 I tried 3 different hard drives (Seagate 2x80GB and 1x400GB SATA2) which are fine on a physical machine. I also ran Seatool many hours on all of them without errors. I can partiton the disks and create a few files/directories on it. But as soon as I copy a larger number of files to those disks (tried with MBR and GPT) the VM reboots *instantly* (I tried cp, dump/restore and rsync). No "Rebooting within 15 seconds", just *snap*. I think I can see an panic but I'm not sure, it's too fast. (as far as I can see most of the times the data on the first UFS slice (and only the first UFS slice!) of the partition gets *severly* corrupted, most of the time all that is left are a few files within lost+found. Sometimes all the labels are gone but are recoverable using bsdlabel -R) The problem is that /var/crash remains empty. What can I do to create a backtrace to open a PR? Thanks, Helmut From owner-freebsd-stable@FreeBSD.ORG Wed Apr 27 19:07:18 2011 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 31E931065675 for ; Wed, 27 Apr 2011 19:07:18 +0000 (UTC) (envelope-from mike@jellydonut.org) Received: from mail-ew0-f54.google.com (mail-ew0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id CC1978FC19 for ; Wed, 27 Apr 2011 19:07:17 +0000 (UTC) Received: by ewy1 with SMTP id 1so805320ewy.13 for ; Wed, 27 Apr 2011 12:07:16 -0700 (PDT) MIME-Version: 1.0 Received: by 10.213.110.203 with SMTP id o11mr1070346ebp.82.1303929822535; Wed, 27 Apr 2011 11:43:42 -0700 (PDT) Received: by 10.213.10.131 with HTTP; Wed, 27 Apr 2011 11:43:42 -0700 (PDT) Date: Wed, 27 Apr 2011 14:43:42 -0400 Message-ID: From: Michael Proto To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: correct way to setup gmirror on 7.4? 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, 27 Apr 2011 19:07:18 -0000 I'm migrating away from my old pseudo-RAID partitions to GEOM gmirror and I have some questions on the right way to accomplish this. I've got two new 1TB disks that I'm setting up for the new mirror, and unfortunately they're Western Digital drives with 4k sectors that report themselves as 512b. Here's what I'm currently doing to setup this array. The disks are detected as ad4 and ad6 on my FreeBSD 7.4 server. # initialize/wipe MBR dd if=/dev/zero of=/dev/ad4 bs=512 count=79 dd if=/dev/zero of=/dev/ad6 bs=512 count=79 # gpart gpart create -s gpt ad4 gpart create -s gpt ad6 gpart bootcode -b /boot/pmbr ad4 gpart bootcode -b /boot/pmbr ad6 # add partitions gpart add -t freebsd-ufs -l raidhome1-2 -b 2048 -s 195330048 ad4 gpart add -t freebsd-ufs -l raidhome2-2 -b 2048 -s 195330048 ad6 gpart add -t freebsd-ufs -l raidvault1-2 -b 195338240 -s 1758167040 ad4 gpart add -t freebsd-ufs -l raidvault2-2 -b 195338240 -s 1758167040 ad6 (I'm using these partition start values because they divide evenly into 4k blocks. I don't mind wasting a few MB on each disk to have correctly-aligned partitions) gpart show ad4 => 34 1953525101 ad4 GPT (932G) 34 2014 - free - (1.0M) 2048 195330048 1 freebsd-ufs (93G) 195332096 6144 - free - (3.0M) 195338240 1758167040 2 freebsd-ufs (838G) 1953505280 19855 - free - (9.7M) gpart show ad6 => 34 1953525101 ad6 GPT (932G) 34 2014 - free - (1.0M) 2048 195330048 1 freebsd-ufs (93G) 195332096 6144 - free - (3.0M) 195338240 1758167040 2 freebsd-ufs (838G) 1953505280 19855 - free - (9.7M) gmirror label -v -n -b round-robin gm0p1 /dev/ad4p1 newfs -U -b 32768 -f 4096 -S 4096 /dev/mirror/gm0p1 gmirror label -v -n -b round-robin gm0p2 /dev/ad4p2 newfs -U -b 32768 -f 4096 -S 4096 /dev/mirror/gm0p2 (then I mount /dev/mirror/gm0p1 and /dev/mirror/gm0p2 and copy data from my original array to this new array) Finally I insert the ad6 disk and wait for the array to sync: gmirror configure -a gm0p1 gmirror insert gm0p1 /dev/ad6p1 gmirror configure -a gm0p2 gmirror insert gm0p2 /dev/ad6p2 Once the array is synchronized things generally look good, although after a reboot I did see the following that had me concerned (from dmesg output): GEOM: ad4: the primary GPT table is corrupt or invalid. GEOM: ad4: using the secondary instead -- recovery strongly advised. Am I using the correct process to create this array? Since I still have my old array in the system I can rebuild it again if needed, and would prefer to do it correctly if I'm not already. Thanks all! -Proto From owner-freebsd-stable@FreeBSD.ORG Wed Apr 27 19:35:45 2011 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 3B2C21065676 for ; Wed, 27 Apr 2011 19:35:45 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id C09E88FC17 for ; Wed, 27 Apr 2011 19:35:44 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1QFAWM-0004HG-5B for freebsd-stable@freebsd.org; Wed, 27 Apr 2011 21:35:34 +0200 Received: from p5dcd6b31.dip.t-dialin.net ([93.205.107.49]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 27 Apr 2011 21:35:34 +0200 Received: from jumper99 by p5dcd6b31.dip.t-dialin.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 27 Apr 2011 21:35:34 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: "Helmut Schneider" Date: Wed, 27 Apr 2011 19:35:22 +0000 (UTC) Lines: 89 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: p5dcd6b31.dip.t-dialin.net User-Agent: XanaNews/1.19.1.320 X-Ref: news.gmane.org ~XNS:00000165 X-Antivirus: avast! (VPS 110427-1, 27.04.2011), Outbound message X-Antivirus-Status: Clean Subject: Re: correct way to setup gmirror on 7.4? 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, 27 Apr 2011 19:35:45 -0000 Michael Proto wrote: > I'm migrating away from my old pseudo-RAID partitions to GEOM gmirror > and I have some questions on the right way to accomplish this. I've > got two new 1TB disks that I'm setting up for the new mirror, and > unfortunately they're Western Digital drives with 4k sectors that > report themselves as 512b. > > Here's what I'm currently doing to setup this array. The disks are > detected as ad4 and ad6 on my FreeBSD 7.4 server. > > # initialize/wipe MBR > dd if=/dev/zero of=/dev/ad4 bs=512 count=79 > dd if=/dev/zero of=/dev/ad6 bs=512 count=79 > # gpart > gpart create -s gpt ad4 > gpart create -s gpt ad6 > gpart bootcode -b /boot/pmbr ad4 > gpart bootcode -b /boot/pmbr ad6 > # add partitions > gpart add -t freebsd-ufs -l raidhome1-2 -b 2048 -s 195330048 ad4 > gpart add -t freebsd-ufs -l raidhome2-2 -b 2048 -s 195330048 ad6 > gpart add -t freebsd-ufs -l raidvault1-2 -b 195338240 -s 1758167040 > ad4 gpart add -t freebsd-ufs -l raidvault2-2 -b 195338240 -s > 1758167040 ad6 > > (I'm using these partition start values because they divide evenly > into 4k blocks. I don't mind wasting a few MB on each disk to have > correctly-aligned partitions) > > gpart show ad4 > => 34 1953525101 ad4 GPT (932G) > 34 2014 - free - (1.0M) > 2048 195330048 1 freebsd-ufs (93G) > 195332096 6144 - free - (3.0M) > 195338240 1758167040 2 freebsd-ufs (838G) > 1953505280 19855 - free - (9.7M) > > gpart show ad6 > => 34 1953525101 ad6 GPT (932G) > 34 2014 - free - (1.0M) > 2048 195330048 1 freebsd-ufs (93G) > 195332096 6144 - free - (3.0M) > 195338240 1758167040 2 freebsd-ufs (838G) > 1953505280 19855 - free - (9.7M) > > gmirror label -v -n -b round-robin gm0p1 /dev/ad4p1 > newfs -U -b 32768 -f 4096 -S 4096 /dev/mirror/gm0p1 > > gmirror label -v -n -b round-robin gm0p2 /dev/ad4p2 > newfs -U -b 32768 -f 4096 -S 4096 /dev/mirror/gm0p2 > > (then I mount /dev/mirror/gm0p1 and /dev/mirror/gm0p2 and copy data > from my original array to this new array) > > Finally I insert the ad6 disk and wait for the array to sync: > > gmirror configure -a gm0p1 > gmirror insert gm0p1 /dev/ad6p1 > > gmirror configure -a gm0p2 > gmirror insert gm0p2 /dev/ad6p2 > > > Once the array is synchronized things generally look good, although > after a reboot I did see the following that had me concerned (from > dmesg output): > > GEOM: ad4: the primary GPT table is corrupt or invalid. > GEOM: ad4: using the secondary instead -- recovery strongly advised. > > Am I using the correct process to create this array? No. While this works with MBR it fails with GPT as GPT and GEOM both want to use the last sector of the disk. First create the mirror and after that gpart it. It will create a message like GEOM: da0: the secondary GPT header is not in the last LBA. GEOM: da1: the secondary GPT header is not in the last LBA. which afaik is ignorable. At least it works fine here and I didn't find any caveats in the net. Another workaround is not to mirror the disk but only slices or partitions. HTH, Helmut From owner-freebsd-stable@FreeBSD.ORG Wed Apr 27 19:49:13 2011 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 5EB46106564A for ; Wed, 27 Apr 2011 19:49:13 +0000 (UTC) (envelope-from mike@jellydonut.org) Received: from mail-ew0-f54.google.com (mail-ew0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 02F538FC13 for ; Wed, 27 Apr 2011 19:49:12 +0000 (UTC) Received: by ewy1 with SMTP id 1so820820ewy.13 for ; Wed, 27 Apr 2011 12:49:11 -0700 (PDT) MIME-Version: 1.0 Received: by 10.213.113.129 with SMTP id a1mr1190098ebq.44.1303933751699; Wed, 27 Apr 2011 12:49:11 -0700 (PDT) Received: by 10.213.10.131 with HTTP; Wed, 27 Apr 2011 12:49:11 -0700 (PDT) In-Reply-To: References: Date: Wed, 27 Apr 2011 15:49:11 -0400 Message-ID: From: Michael Proto To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: correct way to setup gmirror on 7.4? 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, 27 Apr 2011 19:49:13 -0000 On Wed, Apr 27, 2011 at 3:35 PM, Helmut Schneider wrote: > Michael Proto wrote: >> Am I using the correct process to create this array? > > No. While this works with MBR it fails with GPT as GPT and GEOM both > want to use the last sector of the disk. > > First create the mirror and after that gpart it. It will create a > message like > > GEOM: da0: the secondary GPT header is not in the last LBA. > GEOM: da1: the secondary GPT header is not in the last LBA. > > which afaik is ignorable. At least it works fine here and I didn't find > any caveats in the net. > > Another workaround is not to mirror the disk but only slices or > partitions. > > HTH, Helmut > Thank you for the advice and direction, but I'm still a bit confused. In my setup I am mirroring only partitions, creating partitions ad4p1, ad6p1, ad4p2 and ad6p2 with gpart first, and then mirrors gm0p1 and gm0p2 on top of those. I'd prefer not to mirror the whole disk. The "primary GPT table is corrupt or invalid" error I'm seeing is with this configuration. Or perhaps I'm misunderstanding what you're saying. -Proto From owner-freebsd-stable@FreeBSD.ORG Wed Apr 27 20:43:29 2011 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 005C9106566B for ; Wed, 27 Apr 2011 20:43:29 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id AADEE8FC16 for ; Wed, 27 Apr 2011 20:43:28 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1QFBa2-0003hQ-KG for freebsd-stable@freebsd.org; Wed, 27 Apr 2011 22:43:26 +0200 Received: from p5dcd6b31.dip.t-dialin.net ([93.205.107.49]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 27 Apr 2011 22:43:26 +0200 Received: from jumper99 by p5dcd6b31.dip.t-dialin.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 27 Apr 2011 22:43:26 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: "Helmut Schneider" Date: Wed, 27 Apr 2011 20:43:14 +0000 (UTC) Lines: 25 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: p5dcd6b31.dip.t-dialin.net User-Agent: XanaNews/1.19.1.320 X-Ref: news.gmane.org ~XNS:00000166 X-Antivirus: avast! (VPS 110427-2, 27.04.2011), Outbound message X-Antivirus-Status: Clean Subject: Re: correct way to setup gmirror on 7.4? 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, 27 Apr 2011 20:43:29 -0000 Michael Proto wrote: > On Wed, Apr 27, 2011 at 3:35 PM, Helmut Schneider > wrote: > > Michael Proto wrote: > >> Am I using the correct process to create this array? > > > > No. While this works with MBR it fails with GPT as GPT and GEOM both > > want to use the last sector of the disk. > > > > First create the mirror and after that gpart it. > > In my setup I am mirroring only partitions, creating partitions ad4p1, > ad6p1, ad4p2 and ad6p2 with gpart first, and then mirrors gm0p1 and > gm0p2 on top of those. [...] > Or perhaps I'm misunderstanding what you're saying. 1. Create the mirror 2. Create the partition(s) Or do the steps described in section 19.4.2 at http://eis.bris.ac.uk/~mexas/geom-mirror.html HTH, Helmut From owner-freebsd-stable@FreeBSD.ORG Wed Apr 27 20:59:17 2011 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 691191065673 for ; Wed, 27 Apr 2011 20:59:17 +0000 (UTC) (envelope-from mike@jellydonut.org) Received: from mail-ey0-f182.google.com (mail-ey0-f182.google.com [209.85.215.182]) by mx1.freebsd.org (Postfix) with ESMTP id 092458FC1C for ; Wed, 27 Apr 2011 20:59:16 +0000 (UTC) Received: by mail-ey0-f182.google.com with SMTP id 7so846013eyg.13 for ; Wed, 27 Apr 2011 13:59:16 -0700 (PDT) MIME-Version: 1.0 Received: by 10.213.113.129 with SMTP id a1mr1236224ebq.44.1303937956546; Wed, 27 Apr 2011 13:59:16 -0700 (PDT) Received: by 10.213.10.131 with HTTP; Wed, 27 Apr 2011 13:59:16 -0700 (PDT) In-Reply-To: References: Date: Wed, 27 Apr 2011 16:59:16 -0400 Message-ID: From: Michael Proto To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: correct way to setup gmirror on 7.4? 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, 27 Apr 2011 20:59:17 -0000 On Wed, Apr 27, 2011 at 4:43 PM, Helmut Schneider wrote: > Michael Proto wrote: > >> On Wed, Apr 27, 2011 at 3:35 PM, Helmut Schneider >> wrote: >> > Michael Proto wrote: >> >> Am I using the correct process to create this array? >> > >> > No. While this works with MBR it fails with GPT as GPT and GEOM both >> > want to use the last sector of the disk. >> > >> > First create the mirror and after that gpart it. >> >> In my setup I am mirroring only partitions, creating partitions ad4p1, >> ad6p1, ad4p2 and ad6p2 with gpart first, and then mirrors gm0p1 and >> gm0p2 on top of those. > [...] >> Or perhaps I'm misunderstanding what you're saying. > > 1. Create the mirror > 2. Create the partition(s) > > Or do the steps described in section 19.4.2 at > http://eis.bris.ac.uk/~mexas/geom-mirror.html > Ah, thanks for that link, 19.4.2 does seem to describe what I'm trying to do (couldn't find it via google search). I'll give this a thorough reading and try it out. Thanks again! -Proto From owner-freebsd-stable@FreeBSD.ORG Wed Apr 27 21:19:11 2011 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 0C49B106566B for ; Wed, 27 Apr 2011 21:19:11 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id B77DD8FC08 for ; Wed, 27 Apr 2011 21:19:10 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1QFC8b-0000Ha-Lp for freebsd-stable@freebsd.org; Wed, 27 Apr 2011 23:19:09 +0200 Received: from p5dcd6b31.dip.t-dialin.net ([93.205.107.49]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 27 Apr 2011 23:19:09 +0200 Received: from jumper99 by p5dcd6b31.dip.t-dialin.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 27 Apr 2011 23:19:09 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: "Helmut Schneider" Date: Wed, 27 Apr 2011 21:18:56 +0000 (UTC) Lines: 33 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: p5dcd6b31.dip.t-dialin.net User-Agent: XanaNews/1.19.1.320 X-Ref: news.gmane.org ~XNS:00000167 X-Antivirus: avast! (VPS 110427-2, 27.04.2011), Outbound message X-Antivirus-Status: Clean Subject: Re: panic, but /var/crash ist empty 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, 27 Apr 2011 21:19:11 -0000 Helmut 'Ingrid' Schneider wrote: > running 8.2-RELEASE-p1 within VMWare ESXi 4.1-u1 I want to use raw > devices as hard disks. I create the devices using this link: > > http://www.mattiasholm.com/node/33 > > I tried 3 different hard drives (Seagate 2x80GB and 1x400GB SATA2) > which are fine on a physical machine. I also ran Seatool many hours on > all of them without errors. > > I can partiton the disks and create a few files/directories on it. But > as soon as I copy a larger number of files to those disks (tried with > MBR and GPT) the VM reboots instantly (I tried cp, dump/restore and > rsync). No "Rebooting within 15 seconds", just snap. I think I can > see an panic but I'm not sure, it's too fast. > > (as far as I can see most of the times the data on the first UFS slice > (and only the first UFS slice!) of the partition gets severly > corrupted, most of the time all that is left are a few files within > lost+found. Sometimes all the labels are gone but are recoverable > using bsdlabel -R) > > The problem is that /var/crash remains empty. > > What can I do to create a backtrace to open a PR? FWIW: While a sysinstall from CD (tried 8.0, 8.1 and 8.2) also dies short before the end of the installation, Ubuntu 10.4 (EXT4), Windows 7 and OpenBSD install fine and also do not die when copying a lots of files... :( From owner-freebsd-stable@FreeBSD.ORG Wed Apr 27 22:15:56 2011 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 9D42B1065676 for ; Wed, 27 Apr 2011 22:15:56 +0000 (UTC) (envelope-from cliftonr@oz.volcano.org) Received: from hrndva-omtalb.mail.rr.com (hrndva-omtalb.mail.rr.com [71.74.56.122]) by mx1.freebsd.org (Postfix) with ESMTP id 59A6B8FC17 for ; Wed, 27 Apr 2011 22:15:55 +0000 (UTC) X-Authority-Analysis: v=1.1 cv=pN6kzQkhXdmdOr6Akjoh3kGBD/S3UyPMKQp53EJY+ro= c=1 sm=0 a=z1TLwsU0kBEA:10 a=NlqD0-V7MGoA:10 a=TgPToyY2OQsA:10 a=kj9zAlcOel0A:10 a=G5OLwwqwWgs+1dCEPNHTSw==:17 a=jb__rZ8GAAAA:8 a=GjEiR67sAAAA:8 a=bG_-vTu0E_V4jIW5eU8A:9 a=39GXB5GJEL7xEDFP7BAA:7 a=CjuIK1q_8ugA:10 a=sHp_62vNEjwA:10 a=Ke08FT2oSu0A:10 a=G5OLwwqwWgs+1dCEPNHTSw==:117 X-Cloudmark-Score: 0 X-Originating-IP: 75.80.196.236 Received: from [75.80.196.236] ([75.80.196.236:47438] helo=oz.volcano.org) by hrndva-oedge04.mail.rr.com (envelope-from ) (ecelerity 2.2.3.46 r()) with ESMTP id 2E/19-28036-A9598BD4; Wed, 27 Apr 2011 22:15:55 +0000 Received: by oz.volcano.org (Postfix, from userid 1001) id 633005082A; Wed, 27 Apr 2011 12:15:54 -1000 (HST) Date: Wed, 27 Apr 2011 12:15:54 -1000 From: Clifton Royston To: Helmut Schneider Message-ID: <20110427221554.GB22139@lava.net> Mail-Followup-To: Helmut Schneider , freebsd-stable@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org Subject: Re: correct way to setup gmirror on 7.4? 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, 27 Apr 2011 22:15:56 -0000 On Wed, Apr 27, 2011 at 07:35:22PM +0000, Helmut Schneider wrote: > Michael Proto wrote: ... > > gmirror label -v -n -b round-robin gm0p1 /dev/ad4p1 > > newfs -U -b 32768 -f 4096 -S 4096 /dev/mirror/gm0p1 > > > > gmirror label -v -n -b round-robin gm0p2 /dev/ad4p2 > > newfs -U -b 32768 -f 4096 -S 4096 /dev/mirror/gm0p2 > > > > (then I mount /dev/mirror/gm0p1 and /dev/mirror/gm0p2 and copy data > > from my original array to this new array) > > > > Finally I insert the ad6 disk and wait for the array to sync: > > > > gmirror configure -a gm0p1 > > gmirror insert gm0p1 /dev/ad6p1 > > > > gmirror configure -a gm0p2 > > gmirror insert gm0p2 /dev/ad6p2 .... > > > > GEOM: ad4: the primary GPT table is corrupt or invalid. > > GEOM: ad4: using the secondary instead -- recovery strongly advised. > > > > Am I using the correct process to create this array? > > No. While this works with MBR it fails with GPT as GPT and GEOM both > want to use the last sector of the disk. > > First create the mirror and after that gpart it. It will create a > message like > > GEOM: da0: the secondary GPT header is not in the last LBA. > GEOM: da1: the secondary GPT header is not in the last LBA. > > which afaik is ignorable. At least it works fine here and I didn't find > any caveats in the net. > > Another workaround is not to mirror the disk but only slices or > partitions. He is mirroring only the partitions - reread above: gmirror label -v -n -b round-robin gm0p1 /dev/ad4p1 etc. I don't know; it looks correct to me, but I may be missing something as I don't currently use gpart. -- Clifton -- Clifton Royston -- cliftonr@iandicomputing.com / cliftonr@volcano.org President - I and I Computing * http://www.iandicomputing.com/ Custom programming, network design, systems and network consulting services From owner-freebsd-stable@FreeBSD.ORG Wed Apr 27 22:30:41 2011 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 DCAF7106564A for ; Wed, 27 Apr 2011 22:30:41 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by mx1.freebsd.org (Postfix) with ESMTP id 94BC38FC17 for ; Wed, 27 Apr 2011 22:30:41 +0000 (UTC) Received: by gxk19 with SMTP id 19so1111181gxk.17 for ; Wed, 27 Apr 2011 15:30:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=SJm9nC0sAAH0MjrMoNAdNoHKzPP1zglTjgq3FHw9UQM=; b=mY/nqiPlkgdKOhaQfpUU7rCdkUan5iU9bFeYvhhQXOdWIz8PTQHqp7lxHRaZtsZdGn wTcVrUuytQ8CfR5mXsHJcATbvTCL3RQgnUITP4KwFNhyN3Zgq7BgobVIteioYFxPFKNE GC+Bn2clmnp6FyGmNDpzxQNLiAqyw1wQAeHdc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=Qf27U0IuH/2l7r7fZ0pObpPtQCSjuf38acGTNYQINm1wB8Ma0WmLEnpq2gm6v3HVgM 3SBR5bx2VPETeygDhMDLaskQDj35e8PZAVVlq6Ke31qLLI7bRxdhYvuxn5p+pqsa+h9v u0PXThN7c8IrhfsIN5Xm3e+13d2TjWTVPU8QA= MIME-Version: 1.0 Received: by 10.91.76.4 with SMTP id d4mr2485531agl.42.1303943440726; Wed, 27 Apr 2011 15:30:40 -0700 (PDT) Received: by 10.90.70.18 with HTTP; Wed, 27 Apr 2011 15:30:40 -0700 (PDT) In-Reply-To: <20110427221554.GB22139@lava.net> References: <20110427221554.GB22139@lava.net> Date: Wed, 27 Apr 2011 15:30:40 -0700 Message-ID: From: Freddie Cash To: Helmut Schneider Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org Subject: Re: correct way to setup gmirror on 7.4? 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, 27 Apr 2011 22:30:41 -0000 On Wed, Apr 27, 2011 at 3:15 PM, Clifton Royston wrote: > =C2=A0I don't know; it looks correct to me, but I may be missing somethin= g > as I don't currently use gpart. gmirror (well, really, any GEOM) doesn't play well with GPT due to the way they store their metadata. gmirror doesn't touch the start of the disk, but saves it's metadata in the last sector of the disk, and creates a new GEOM provider that's one sector shorter. GPT stores it's partition table in the first sector of the disk, and saves a backup copy of it in the last sector of the disk. Depending on the order you do things, gmirror can overwrite the secondary GPT table. Or, if you mirror the disk and then gpart the mirror, gpt will complain that the secondary table is not in the last sector of the disk (due to the order that GEOM tastes things as gpt goes first). I've tried to document it here. Let me know if there's anything incorrect. https://forums.freebsd.org/showthread.php?t=3D22125 --=20 Freddie Cash fjwcash@gmail.com From owner-freebsd-stable@FreeBSD.ORG Wed Apr 27 22:44:42 2011 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 36874106564A for ; Wed, 27 Apr 2011 22:44:42 +0000 (UTC) (envelope-from mike@jellydonut.org) Received: from mail-ew0-f54.google.com (mail-ew0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id C813F8FC14 for ; Wed, 27 Apr 2011 22:44:41 +0000 (UTC) Received: by ewy1 with SMTP id 1so870611ewy.13 for ; Wed, 27 Apr 2011 15:44:40 -0700 (PDT) MIME-Version: 1.0 Received: by 10.213.113.129 with SMTP id a1mr1264171ebq.44.1303944280483; Wed, 27 Apr 2011 15:44:40 -0700 (PDT) Received: by 10.213.10.131 with HTTP; Wed, 27 Apr 2011 15:44:40 -0700 (PDT) In-Reply-To: References: <20110427221554.GB22139@lava.net> Date: Wed, 27 Apr 2011 18:44:40 -0400 Message-ID: From: Michael Proto To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: correct way to setup gmirror on 7.4? 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, 27 Apr 2011 22:44:42 -0000 On Wed, Apr 27, 2011 at 6:30 PM, Freddie Cash wrote: > On Wed, Apr 27, 2011 at 3:15 PM, Clifton Royston wrot= e: >> =A0I don't know; it looks correct to me, but I may be missing something >> as I don't currently use gpart. > > gmirror (well, really, any GEOM) doesn't play well with GPT due to the > way they store their metadata. > > gmirror doesn't touch the start of the disk, but saves it's metadata > in the last sector of the disk, and creates a new GEOM provider that's > one sector shorter. > > GPT stores it's partition table in the first sector of the disk, and > saves a backup copy of it in the last sector of the disk. > > Depending on the order you do things, gmirror can overwrite the > secondary GPT table. =A0Or, if you mirror the disk and then gpart the > mirror, gpt will complain that the secondary table is not in the last > sector of the disk (due to the order that GEOM tastes things as gpt > goes first). > > I've tried to document it here. =A0Let me know if there's anything incorr= ect. > https://forums.freebsd.org/showthread.php?t=3D22125 > What I ultimately decided to do was use fdisk in interactive mode to manually align 2 4k-boundary MBR partitions, /dev/ad4s1 and /dev/ad4s2, created 2 gmirrors out of them, then bsdlabel-ed and newfs-ed the mirror devices. socrates:mike/ $ fdisk /dev/ad4 ******* Working on device /dev/ad4 ******* parameters extracted from in-core disklabel are: cylinders=3D1938021 heads=3D16 sectors/track=3D63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=3D1938021 heads=3D16 sectors/track=3D63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 2048, size 195330048 (95376 Meg), flag 80 (active) beg: cyl 2/ head 0/ sector 33; end: cyl 245/ head 13/ sector 29 The data for partition 2 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 195338240, size 1758167040 (858480 Meg), flag 0 beg: cyl 251/ head 14/ sector 63; end: cyl 593/ head 4/ sector 20 The data for partition 3 is: The data for partition 4 is: (note the "start 2048" and "start 195338240" for the partitions above, which are 4k-aligned) gmirror label -v -n -b round-robin gm0s1 /dev/ad4s1 gmirror configure -a gm0s1 gmirror label -v -n -b round-robin gm0s2 /dev/ad4s2 gmirror configure -a gm0s2 bsdlabel -w /dev/mirror/gm0s1 bsdlabel -w /dev/mirror/gm0s2 newfs -U -b 32768 -f 4096 -S 4096 /dev/mirror/gm0s1a newfs -U -b 32768 -f 4096 -S 4096 /dev/mirror/gm0s2a I believe this will work since there's no last-block used for MBR partitions, only GPT. gmirror should happily have its metadata in the last block and partitions shouldn't complain. I'm copying data to the arrays now and will insert my /dev/ad6 partitions after that. I'll reboot once more to confirm no strangeness (apart from GEOM complaining about my sector boundaries due to these 4k-reporting-as-512b disks). Thanks everyone for the suggestions and support, it is very much appreciated here!! -Proto From owner-freebsd-stable@FreeBSD.ORG Wed Apr 27 23:39:59 2011 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 C7ECD106566B for ; Wed, 27 Apr 2011 23:39:59 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 7CBDC8FC0C for ; Wed, 27 Apr 2011 23:39:59 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1QFEKs-0005CZ-2P for freebsd-stable@freebsd.org; Thu, 28 Apr 2011 01:39:58 +0200 Received: from p5dcd6b31.dip.t-dialin.net ([93.205.107.49]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 28 Apr 2011 01:39:58 +0200 Received: from jumper99 by p5dcd6b31.dip.t-dialin.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 28 Apr 2011 01:39:58 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: "Helmut Schneider" Date: Wed, 27 Apr 2011 23:39:46 +0000 (UTC) Lines: 13 Message-ID: References: <20110427221554.GB22139@lava.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: p5dcd6b31.dip.t-dialin.net User-Agent: XanaNews/1.19.1.320 X-Ref: news.gmane.org ~XNS:00000168 X-Antivirus: avast! (VPS 110427-2, 27.04.2011), Outbound message X-Antivirus-Status: Clean Subject: Re: correct way to setup gmirror on 7.4? 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, 27 Apr 2011 23:39:59 -0000 Michael Proto wrote: > What I ultimately decided to do was use fdisk in interactive mode to > manually align 2 4k-boundary MBR partitions Correct me if I'm wrong but from my point of view there is no need to fall back to MBR partitions. GPT partitions should be at least as robust as MBR partitions are if not even more (e.g. because of using CRC). We are still talking about /possible/ issues with /one copy/ (of two) of the GPT - MBR doesn't even have a backup copy nor uses CRC. And if you are still concerned run 'gpart backup $disk/$partition(s)' before your regular backup - one should do so anyway. From owner-freebsd-stable@FreeBSD.ORG Thu Apr 28 03:07:37 2011 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 AE785106566C; Thu, 28 Apr 2011 03:07:37 +0000 (UTC) (envelope-from telbizov@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id 4DBDC8FC15; Thu, 28 Apr 2011 03:07:36 +0000 (UTC) Received: by qwc9 with SMTP id 9so1352233qwc.13 for ; Wed, 27 Apr 2011 20:07:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=fIP+bgGwpZKE5Mg3FhZLX/MR5hHn58BsPXncNO0SMko=; b=sIvZs/8K+N8oqxaXN6XFTa6TO4FNv3nGbbQlw5m5iFTDDwr76ph+Z46k85LShimK60 jf24CHGTtf3E/9zUd65PykS/Zy5decNsT5Oz6qitc7BB+Kqp/7D1lUvxj2FQSf/rUBCm JK6+J7BFO6ClfPEZ0o8T35ydept1zo9TY/XnM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=mJoI8N8RmzpUBr0U+BH04PNXuo4hQzA/3PUyEI1H3NtsnsE+i4PdoYmfri5QkfRavq cnvj83GG5yD2g/qg7+R7u/CM3bjfmF/Xo/L9Zx9XlHV8LuTA0EBl4HaJdQt5x+JRugrA Z+a/o1Qvb9oaT5veOjVPlO9IQWMmBWVri5zGw= MIME-Version: 1.0 Received: by 10.229.79.196 with SMTP id q4mr2393406qck.132.1303960054823; Wed, 27 Apr 2011 20:07:34 -0700 (PDT) Received: by 10.229.86.9 with HTTP; Wed, 27 Apr 2011 20:07:34 -0700 (PDT) In-Reply-To: <4DB8381B.4030408@FreeBSD.org> References: <20110427125736.GA1977@icarus.home.lan> <4DB8381B.4030408@FreeBSD.org> Date: Wed, 27 Apr 2011 20:07:34 -0700 Message-ID: From: Rumen Telbizov To: Alexander Motin Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Denny Schierz , FreeBSD Stable Subject: Re: MPS driver: force bus rescan after remove SAS cable 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, 28 Apr 2011 03:07:37 -0000 Hello Denny, everyone, I confirm I experience the same behavior with just a SAS expander not via SAS switch. I've got no way to get my block device back but reboot. Also identify function doesn't work from the OS (no problem via the card BIOS). Don't remember having any luck with sg3_util package either but worth trying again. I talked to LSI about their own version of the driver and I was told that work on the FreeBSD driver is in progress apparently and there will be a driver sometime the first half of this year. Otherwise the driver and the chip (experience based on 9211-8i controller) seem to be working OK for me so far. I am in progress of putting a 9200-8e in production the coming week so I can share experience with this as well. On a related note: recently LSI released version 9.0 of their firmware for SAS2008 and I found it fixes certain performance problems with SuperMicro backplanes! Cheers, Rumen Telbizov On Wed, Apr 27, 2011 at 8:36 AM, Alexander Motin wrote: > On 27.04.2011 16:39, Denny Schierz wrote: > >> Am Mittwoch, den 27.04.2011, 05:57 -0700 schrieb Jeremy Chadwick: >> >>> camcontrol reset 0 >>> >> >> 0:22:0 is available, 0:46:0 not: >> >> root@iscsihead-m:~# camcontrol reset 0:22:0 >> Reset of 0:22:0 was successful >> >> root@iscsihead-m:~# camcontrol reset 0:46:0 >> camcontrol: cam_open_btl: no passthrough device found at 0:46:0 >> > > You should reset whole bus, not the specific LUN. Full reset doesn't need > that passthrough device. IIRC it works via xpt0. > > > We bought the LSI SAS6160 switch: >> >> >> http://www.lsi.com/storage_home/products_home/sas_switch/sas6100/index.html >> >> use the LSI 9200-8e hostbusadapter and LSI JBODs 630j. We had a lot of >> e-mail conversation with LSI and they mean, that we need the switch for >> a clear failover setup. >> Also a reason for the switch: increase storage with more jbods. Every >> jbod has his own cable to the (later) redundant switch. Otherwise we >> have to build a "bus" from JBOD to JBOD to JBOD to JBOD to host ... bad >> idea ;-) >> >> The question is, what does the driver while FreeBSD starts? >> > > CAM exactly does full bus reset and after few seconds full rescan. What > controller driver may do except it depends on it alone. > > -- > Alexander Motin > > _______________________________________________ > 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" > -- Rumen Telbizov http://telbizov.com From owner-freebsd-stable@FreeBSD.ORG Thu Apr 28 03:23:51 2011 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 18C671065674 for ; Thu, 28 Apr 2011 03:23:51 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta03.emeryville.ca.mail.comcast.net (qmta03.emeryville.ca.mail.comcast.net [76.96.30.32]) by mx1.freebsd.org (Postfix) with ESMTP id EE6B48FC19 for ; Thu, 28 Apr 2011 03:23:50 +0000 (UTC) Received: from omta09.emeryville.ca.mail.comcast.net ([76.96.30.20]) by qmta03.emeryville.ca.mail.comcast.net with comcast id crPe1g0020S2fkCA3rPq5b; Thu, 28 Apr 2011 03:23:50 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta09.emeryville.ca.mail.comcast.net with comcast id crPo1g00W1t3BNj8VrPo1k; Thu, 28 Apr 2011 03:23:50 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 018D29B418; Wed, 27 Apr 2011 20:23:47 -0700 (PDT) Date: Wed, 27 Apr 2011 20:23:47 -0700 From: Jeremy Chadwick To: Rumen Telbizov Message-ID: <20110428032347.GA15220@icarus.home.lan> References: <20110427125736.GA1977@icarus.home.lan> <4DB8381B.4030408@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Denny Schierz , Alexander Motin , FreeBSD Stable Subject: Re: MPS driver: force bus rescan after remove SAS cable 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, 28 Apr 2011 03:23:51 -0000 On Wed, Apr 27, 2011 at 08:07:34PM -0700, Rumen Telbizov wrote: > I confirm I experience the same behavior with just a SAS expander not > via SAS switch. I've got no way to get my block device back but > reboot. I don't mean to sound critical, but why do you guys do this? The reason I ask: on actual production filers (read: NetApps), you don't go yanking out the FC cable between the HBA and the NA and expect everything to "be happy" afterwards. Most SAN administrators tend to reboot an appliance when doing this kind of work -- because this kind of work is considered maintenance. I understand what you folks are reporting is a problem. I'm just wondering why you're complaining about having to reboot a machine with an HBA in it after doing this kind of *physical* cabling work. My immediate thought is "I'm really not surprised". I guess some other people *are* surprised. :-) > Also identify function doesn't work from the OS (no problem > via the card BIOS). Don't remember having any luck with sg3_util > package either but worth trying again. I don't use SAS myself, but wouldn't the command be "inquiry" and not "identify"? "identify" is for ATA (specifically SATA via CAM), while "inquiry" is for SCSI. Where SAS fits into this is unknown to me. > On a related note: recently LSI released version 9.0 of their firmware > for SAS2008 and I found it fixes certain performance problems with > SuperMicro backplanes! In another thread, or a PR, if you could provide those technical details that would be beneficial. There are a very large number of FreeBSD users who use Supermicro server-class hardware, and I'm certain they would be interested in a full disclosure. -- | Jeremy Chadwick jdc@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 Apr 28 06:42:22 2011 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 7D4BD1065672 for ; Thu, 28 Apr 2011 06:42:22 +0000 (UTC) (envelope-from linuxmail@4lin.net) Received: from mail.4lin.net (mail.4lin.net [46.4.210.97]) by mx1.freebsd.org (Postfix) with ESMTP id 33D5F8FC19 for ; Thu, 28 Apr 2011 06:42:21 +0000 (UTC) Received: from localhost (angelica.4lin.net [127.0.0.1]) by mail.4lin.net (Postfix) with ESMTP id 9CC522E141 for ; Thu, 28 Apr 2011 08:46:41 +0200 (CEST) X-Virus-Scanned: amavisd-new at mail.4lin.net Received: from mail.4lin.net ([127.0.0.1]) by localhost (mail.4lin.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zp117V1krOiH for ; Thu, 28 Apr 2011 08:46:38 +0200 (CEST) Received: from [130.83.160.152] (pcdenny.rbg.informatik.tu-darmstadt.de [130.83.160.152]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.4lin.net (Postfix) with ESMTPSA id 720F429D97 for ; Thu, 28 Apr 2011 08:46:38 +0200 (CEST) From: Denny Schierz To: freebsd-stable In-Reply-To: <20110428032347.GA15220@icarus.home.lan> References: <20110427125736.GA1977@icarus.home.lan> <4DB8381B.4030408@FreeBSD.org> <20110428032347.GA15220@icarus.home.lan> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-ykiwLNgWrNCepd/dPwXg" Date: Thu, 28 Apr 2011 08:42:33 +0200 Message-ID: <1303972953.4232.137.camel@pcdenny> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Subject: Re: MPS driver: force bus rescan after remove SAS cable 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, 28 Apr 2011 06:42:22 -0000 --=-ykiwLNgWrNCepd/dPwXg Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable hi, Am Mittwoch, den 27.04.2011, 20:23 -0700 schrieb Jeremy Chadwick: > I don't mean to sound critical, but why do you guys do this?=20 two answers: 1.) Think of: It could happen, instead of it shouldn't happen :-) 2.) Adding a new JBOD on the fly, without reboot the whole machine, what I've done under Solaris and Linux and that wasn't a big deal. It just works. At the moment, replug the SAS cable let you see not all the same disks, like before. Means, replug several times, you get different disks, but most the last 30~46 are missed. However: SAS is a hot pluggable "bus", so it should work, but it doesn't. Maybe a bug in the driver or something else. cu denny --=-ykiwLNgWrNCepd/dPwXg Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEABECAAYFAk25DFYACgkQKlzhkqt9P+AeGwCfduTQeRYSohfhrUJ+zw7q23ZE O8oAnjINiMGrnXPCfwozUm7AVCdazftu =heGv -----END PGP SIGNATURE----- --=-ykiwLNgWrNCepd/dPwXg-- From owner-freebsd-stable@FreeBSD.ORG Thu Apr 28 09:15:52 2011 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 74401106566C for ; Thu, 28 Apr 2011 09:15:52 +0000 (UTC) (envelope-from daniel@digsys.bg) Received: from smtp-sofia.digsys.bg (smtp-sofia.digsys.bg [193.68.3.230]) by mx1.freebsd.org (Postfix) with ESMTP id F39F08FC0C for ; Thu, 28 Apr 2011 09:15:51 +0000 (UTC) Received: from dcave.digsys.bg (dcave.digsys.bg [192.92.129.5]) (authenticated bits=0) by smtp-sofia.digsys.bg (8.14.4/8.14.4) with ESMTP id p3S9Fg53095300 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Thu, 28 Apr 2011 12:15:47 +0300 (EEST) (envelope-from daniel@digsys.bg) Message-ID: <4DB9303E.9090305@digsys.bg> Date: Thu, 28 Apr 2011 12:15:42 +0300 From: Daniel Kalchev User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110307 Thunderbird/3.1.9 MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <20110427221554.GB22139@lava.net> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: correct way to setup gmirror on 7.4? 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, 28 Apr 2011 09:15:52 -0000 On 28.04.11 01:30, Freddie Cash wrote: > gmirror doesn't touch the start of the disk, but saves it's metadata > in the last sector of the disk, and creates a new GEOM provider that's > one sector shorter. > > GPT stores it's partition table in the first sector of the disk, and > saves a backup copy of it in the last sector of the disk. This looks like layering issue to me. In theory, both gmirror and gpt should work on 'providers'. So if you give an gmirrored provider to gpt it should touch the last sector of the gmirror, but not the last sector of the disk - and not complain. It should not even be able to see the last sector of the real disk. Is this hard to fix? Daniel From owner-freebsd-stable@FreeBSD.ORG Thu Apr 28 09:50:06 2011 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 DA23F1065673 for ; Thu, 28 Apr 2011 09:50:06 +0000 (UTC) (envelope-from edhoprima@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 5F47C8FC14 for ; Thu, 28 Apr 2011 09:50:05 +0000 (UTC) Received: by bwz12 with SMTP id 12so3052467bwz.13 for ; Thu, 28 Apr 2011 02:50:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=zicydOrStaNaf1O+EpLFL0n4FVPgP94QQJoCz0CG7yc=; b=MLF0kRU5bG6JpnVlzTLsk4kk9XBYEh27QQWnYO1+MxtkCI5mQTRJFXiE9PLsYtFPVL e/aJnM5ZTADAHBvWeQcgDQU0aNN+EwSwlvAwo5MIi9hqZsd8Q8sPagC1ac0IVHLJZHNk 2SZkocJ9KXx/MMb6lDO5p5ZZ9CMsxBIBxxXe4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=P3HYHpi8c+WSMv18RiSEHM1MzzZ30XymV/oZahs4dzsgLpFEIhsGljYk9s5jLXtoPj W7t062Im30O7qXUtjJ11Q8NaLF15wQqZD5TDxbaVy40quaC8qF1aZ2go9quEPtW6Geef 9WPXmqpJMLu3G9aXsNNgF0FQaPerceHse5hkk= Received: by 10.204.19.6 with SMTP id y6mr3024631bka.159.1303982473088; Thu, 28 Apr 2011 02:21:13 -0700 (PDT) MIME-Version: 1.0 Received: by 10.204.112.71 with HTTP; Thu, 28 Apr 2011 02:20:52 -0700 (PDT) In-Reply-To: <4DB9303E.9090305@digsys.bg> References: <20110427221554.GB22139@lava.net> <4DB9303E.9090305@digsys.bg> From: Edho P Arief Date: Thu, 28 Apr 2011 16:20:52 +0700 Message-ID: To: Daniel Kalchev Content-Type: text/plain; charset=UTF-8 Cc: freebsd-stable@freebsd.org Subject: Re: correct way to setup gmirror on 7.4? 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, 28 Apr 2011 09:50:06 -0000 On Thu, Apr 28, 2011 at 4:15 PM, Daniel Kalchev wrote: > > > On 28.04.11 01:30, Freddie Cash wrote: >> >> gmirror doesn't touch the start of the disk, but saves it's metadata >> in the last sector of the disk, and creates a new GEOM provider that's >> one sector shorter. >> >> GPT stores it's partition table in the first sector of the disk, and >> saves a backup copy of it in the last sector of the disk. > > This looks like layering issue to me. > > In theory, both gmirror and gpt should work on 'providers'. So if you give > an gmirrored provider to gpt it should touch the last sector of the gmirror, > but not the last sector of the disk - and not complain. It should not even > be able to see the last sector of the real disk. > > Is this hard to fix? > I believe it goes like this gmX: | gpt | data | gpt | which in actual disk goes like this: adY: | gpt | data | gpt | gmirror | so geom read gpt in the first sector but doesn't find it in the last sector. From owner-freebsd-stable@FreeBSD.ORG Thu Apr 28 13:22:09 2011 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 CFA10106567A for ; Thu, 28 Apr 2011 13:22:09 +0000 (UTC) (envelope-from linuxmail@4lin.net) Received: from mail.4lin.net (mail.4lin.net [46.4.210.97]) by mx1.freebsd.org (Postfix) with ESMTP id 85B378FC16 for ; Thu, 28 Apr 2011 13:22:09 +0000 (UTC) Received: from localhost (angelica.4lin.net [127.0.0.1]) by mail.4lin.net (Postfix) with ESMTP id 4CF102E192 for ; Thu, 28 Apr 2011 15:26:29 +0200 (CEST) X-Virus-Scanned: amavisd-new at mail.4lin.net Received: from mail.4lin.net ([127.0.0.1]) by localhost (mail.4lin.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tAKKuxnxNEHi for ; Thu, 28 Apr 2011 15:26:26 +0200 (CEST) Received: from [130.83.160.152] (pcdenny.rbg.informatik.tu-darmstadt.de [130.83.160.152]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.4lin.net (Postfix) with ESMTPSA id F25BF2E002 for ; Thu, 28 Apr 2011 15:26:25 +0200 (CEST) From: Denny Schierz To: freebsd-stable In-Reply-To: <861v0nrdkc.fsf@in138.ua3> References: <1301397421.11113.250.camel@pcdenny> <86ipv1ll4f.fsf@kopusha.home.net> <1303905911.4232.86.camel@pcdenny> <861v0nrdkc.fsf@in138.ua3> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-pUAO9b1Gr/g5jfiNPtAd" Date: Thu, 28 Apr 2011 15:22:22 +0200 Message-ID: <1303996942.4232.160.camel@pcdenny> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Subject: Re: way for failover zpool (no HAST needed): hastmon 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, 28 Apr 2011 13:22:10 -0000 --=-pUAO9b1Gr/g5jfiNPtAd Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable hi, ok, here we go: I've installed hastmon and both FreeBSD nodes and one on Linux Debian as watchdog: Simple setup: =20 # cat /etc.local/hastmon.conf=20 resource sanip { exec /usr/local/_rbg/bin/san-ip friends iscsihead-m iscsihead-s nos on iscsihead-m { remote tcp4://iscsihead-s priority 0 } on iscsihead-s { remote tcp4://iscsihead-m priority 1 } on linux { remote tcp4://iscsihead-m tcp4://iscsihead-s } }=20 It works only half.=20 The simple script adds/remove an alias for the em0 and for status it does a ping -c 1 to the global ip. After tell every host, what is role is, I get on the primary "state unknown", in the secondary "state run" and watchdog for the Linux host. Than I rebooted the primary, the secondary take over and executed the script. After the primary was reachable again, he doesn't get the secondary role, but init/unknown. The same happens, in the opposite: from Linux: hastmonctl status sanip: role: watchdog exec: /usr/local/_rbg/bin/san-ip remote: tcp4://iscsihead-m (primary/run) tcp4://iscsihead-s (init/unknown) state: run attempts: 0 from 5 complaints: 0 for last 60 sec (threshold 3) heartbeat: 10 sec from iscsihead-s: hastmonctl status sanip: role: init exec: /usr/local/_rbg/bin/san-ip remote: tcp4://iscsihead-m state: unknown attempts: 0 from 5 complaints: 0 for last 60 sec (threshold 3) heartbeat: 10 sec and last from iscsihead-m hastmonctl status sanip: role: primary exec: /usr/local/_rbg/bin/san-ip remote: tcp4://iscsihead-s (disconnected) state: run attempts: 0 from 5 complaints: 0 for last 60 sec (threshold 3) heartbeat: 10 sec If I take a look into the logfile from the iscsihead-m: [sanip] (primary) Remote node acts as init for the resource and not as secondary. [sanip] (primary) Handshake header from tcp4://iscsihead-s has no 'token' field. Do I have missed something? cu denny --=-pUAO9b1Gr/g5jfiNPtAd Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEABECAAYFAk25agoACgkQKlzhkqt9P+CJeQCfQI9yRahaWWbt0C6kn9SWbDHY hZQAoIAjWItklDdViyn23qLP+sKGfBSB =z0j1 -----END PGP SIGNATURE----- --=-pUAO9b1Gr/g5jfiNPtAd-- From owner-freebsd-stable@FreeBSD.ORG Thu Apr 28 14:03:28 2011 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 65FFD106566B for ; Thu, 28 Apr 2011 14:03:28 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (unknown [IPv6:2001:44b8:7c07:5581:266:e1ff:fe0c:8f16]) by mx1.freebsd.org (Postfix) with ESMTP id 1CB868FC0A for ; Thu, 28 Apr 2011 14:03:26 +0000 (UTC) Received: from ur.dons.net.au (ppp208-191.lns1.adl2.internode.on.net [203.122.208.191] (may be forged)) (authenticated bits=0) by cain.gsoft.com.au (8.14.4/8.14.3) with ESMTP id p3SE3NgH048046 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 28 Apr 2011 23:33:23 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Thu, 28 Apr 2011 23:33:22 +0930 To: freebsd-stable List Message-Id: <537A8F4F-A302-40F9-92DF-403388D99B4B@gsoft.com.au> Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) X-Spam-Score: -0.272 () BAYES_00,RDNS_NONE X-Scanned-By: MIMEDefang 2.67 on 203.31.81.10 Subject: ZFS vs OSX Time Machine 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, 28 Apr 2011 14:03:28 -0000 Does anyone else use ZFS to store TM backups? I find that whenever my laptop (over wifi!) starts a TM the ZFS machine = it's backing up to grinds to a halt.. Other systems streaming stuff over = NFS from it also tend to stall.. I presume that TM is doing something which causes ZFS some issues but = I'm not sure how to find out what the real problem is let alone how to = fix it.. I am running FreeBSD midget.dons.net.au 8.2-PRERELEASE FreeBSD = 8.2-PRERELEASE #8 r217094M: Sat Jan 8 11:15:07 CST 2011 = darius@midget.dons.net.au:/usr/obj/usr/src/sys/MIDGET amd64 It is a 5 disk RAIDZ1 with 1.29Tb free using WD10EADS drives. I don't see any SMART errors or ZFS warnings. I have the following ZFS related tunables vfs.zfs.arc_max=3D"3072M" vfs.zfs.prefetch_disable=3D"1"=20 vfs.zfs.txg.timeout=3D5 vfs.zfs.cache_flush_disable=3D1 Any help appreciated, thanks :) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C From owner-freebsd-stable@FreeBSD.ORG Thu Apr 28 14:40:17 2011 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 32F2D106564A for ; Thu, 28 Apr 2011 14:40:17 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id DFC348FC08 for ; Thu, 28 Apr 2011 14:40:16 +0000 (UTC) Received: by gyg13 with SMTP id 13so1365288gyg.13 for ; Thu, 28 Apr 2011 07:40:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=mohRovtg5E6l8Ut5MksvvKNaEx4eKT8vHVCl9/n5qJM=; b=w88xpm2twlb17tfnly05zpv979owUR5VD8swLo6rKEWIitY9Skn1SlBAe+CehG8DTy jjXKsAnE6uIzsxKb1/f4LkGR1hUgsfGuP8RSmQAtGaLpopUvGlWN0+42+jSPZ3LQx1LA Grghp96Bhg+LYQCRgwGX0voMj0CY9y6ecmqB4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=LAQjkRLW8cwIIPJoLLHJU/dIRAsvJZUKR0iWAd6F6v0riG92XCmFySbsk6+zzrURGI 4Q7XudzOdw2JAoLqJxOv0Q6dYRGum1yc4q+qA6sIYVs2EqjDZswr0ANThFmoIScjhFE6 m+mWrdaVARVxix+8lkyvVmximMtBMrCt4AhfY= MIME-Version: 1.0 Received: by 10.91.32.6 with SMTP id k6mr3168673agj.123.1304001615918; Thu, 28 Apr 2011 07:40:15 -0700 (PDT) Received: by 10.90.70.18 with HTTP; Thu, 28 Apr 2011 07:40:15 -0700 (PDT) In-Reply-To: References: <20110427221554.GB22139@lava.net> <4DB9303E.9090305@digsys.bg> Date: Thu, 28 Apr 2011 07:40:15 -0700 Message-ID: From: Freddie Cash To: Edho P Arief Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org, Daniel Kalchev Subject: Re: correct way to setup gmirror on 7.4? 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, 28 Apr 2011 14:40:17 -0000 On Thu, Apr 28, 2011 at 2:20 AM, Edho P Arief wrote: > On Thu, Apr 28, 2011 at 4:15 PM, Daniel Kalchev wrote: >> >> >> On 28.04.11 01:30, Freddie Cash wrote: >>> >>> gmirror doesn't touch the start of the disk, but saves it's metadata >>> in the last sector of the disk, and creates a new GEOM provider that's >>> one sector shorter. >>> >>> GPT stores it's partition table in the first sector of the disk, and >>> saves a backup copy of it in the last sector of the disk. >> >> This looks like layering issue to me. >> >> In theory, both gmirror and gpt should work on 'providers'. So if you gi= ve >> an gmirrored provider to gpt it should touch the last sector of the gmir= ror, >> but not the last sector of the disk - and not complain. It should not ev= en >> be able to see the last sector of the real disk. >> >> Is this hard to fix? >> > > I believe it goes like this > > gmX: | gpt | =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0data =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 | gpt | > > which in actual disk goes like this: > > adY: | gpt | =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0data =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 | gpt | gmirror | > > so geom read gpt in the first sector but doesn't find it in the last sect= or. Correct. The layering is not, in itself, the issue. The issue is that the loader or kernel or whatever reads the first sector of the disk, finds a GPT so it then looks for the backup GPT in the last physical sector of the disk and doesn't find it. At this point, gmirror is not loaded (or not noticed, since there's nothing in the first sector of the disk to show it's a mirror). Once gmirror is loaded, then the GPT stops complaining as the first and last sectors of the gmirrror provider have the GPT tables. My completely WAG to a fix would be for all GEOM classes to store metadata in the last *and* first sector of the provider. Thus, allowing for proper stacking/layering, and proper, orderly tasting of providors: adX: | gmirror | gpt | data | gpt | gmirror | And to get complicated: adX: | glabel | gmirror | gpt | data | gpt | gmirror | glabel | And so on. Then the loader or kernel or whatever just starts at the beginning of the disk and reads metadata as needed. Granted, there may be reasons why it wasn't done like this in the beginning, but my non-GEOM programmer's eyes can't see any. --=20 Freddie Cash fjwcash@gmail.com From owner-freebsd-stable@FreeBSD.ORG Thu Apr 28 15:03:11 2011 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 D2318106566B for ; Thu, 28 Apr 2011 15:03:11 +0000 (UTC) (envelope-from edhoprima@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id 8B1CE8FC0C for ; Thu, 28 Apr 2011 15:03:11 +0000 (UTC) Received: by ywf7 with SMTP id 7so1390799ywf.13 for ; Thu, 28 Apr 2011 08:03:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=lKA3dnL16FFD+2/9dLeGHQzjoxtKKkXqXWtP14ht9qk=; b=CTnGaJjzyf0ucX9+1VZ1IEs0I9PT+pKpB6fnBZZkM+x56YkYEv6fuV86fdPtTyFjQw U4lS4FjQm+CfAkYPfLQ0tKAYTaqCyYj6Zs7xS9eQb5KvUDI0g0se4KWJU2JZe4wv4iF+ zYwNwxRORoahdj4ATwGWMbVNiT7aveD9qU/Kg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=Zmuyfzq8NgmjxtsH8pgWlwJuykKlQDNxE1N0Pzsk5rde3TpyNXlNYBpxu0sKpCcrTJ KamKZ0VTBwmvyuZ/eMpx3n/ageT6/Q7/6pcaFpFQJVt9qyTaSWcKoovl4t8Hop80NWnP rXB+8v7b+1AEyIO50trP3RMol80OjpvwGOhbM= Received: by 10.236.73.162 with SMTP id v22mr4752451yhd.247.1304002990736; Thu, 28 Apr 2011 08:03:10 -0700 (PDT) MIME-Version: 1.0 Received: by 10.236.105.234 with HTTP; Thu, 28 Apr 2011 08:02:50 -0700 (PDT) In-Reply-To: References: <20110427221554.GB22139@lava.net> <4DB9303E.9090305@digsys.bg> From: Edho P Arief Date: Thu, 28 Apr 2011 22:02:50 +0700 Message-ID: To: Freddie Cash Content-Type: text/plain; charset=UTF-8 Cc: freebsd-stable@freebsd.org, Daniel Kalchev Subject: Re: correct way to setup gmirror on 7.4? 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, 28 Apr 2011 15:03:11 -0000 On Thu, Apr 28, 2011 at 9:40 PM, Freddie Cash wrote: > Granted, there may be reasons why it wasn't done like this in the > beginning, but my non-GEOM programmer's eyes can't see any. I believe one of the reason is it would prevent conversion from non-gmirror disk to gmirror one as explained here http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/geom-mirror.html From owner-freebsd-stable@FreeBSD.ORG Thu Apr 28 15:32:12 2011 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 9678B106564A for ; Thu, 28 Apr 2011 15:32:12 +0000 (UTC) (envelope-from thomas@ronner.org) Received: from mail.knopje.net (unknown [IPv6:2001:470:1f15:a0::10]) by mx1.freebsd.org (Postfix) with ESMTP id 5A6BD8FC08 for ; Thu, 28 Apr 2011 15:32:12 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.knopje.net (Postfix) with ESMTP id 4022C38144 for ; Thu, 28 Apr 2011 17:32:11 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at knopje.net Received: from mail.knopje.net ([127.0.0.1]) by localhost (hal.knopje.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yEPvlbhMZYWp for ; Thu, 28 Apr 2011 17:32:10 +0200 (CEST) Received: from appelflap.local (unknown [IPv6:2001:610:799:0:223:6cff:fe7f:480e]) by mail.knopje.net (Postfix) with ESMTPSA id 6D1D7380C1 for ; Thu, 28 Apr 2011 17:32:10 +0200 (CEST) Message-ID: <4DB9887A.4080109@ronner.org> Date: Thu, 28 Apr 2011 17:32:10 +0200 From: Thomas Ronner User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9 MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <537A8F4F-A302-40F9-92DF-403388D99B4B@gsoft.com.au> In-Reply-To: <537A8F4F-A302-40F9-92DF-403388D99B4B@gsoft.com.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: ZFS vs OSX Time Machine 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, 28 Apr 2011 15:32:12 -0000 Hi, On 4/28/11 4:03 PM, Daniel O'Connor wrote: > Does anyone else use ZFS to store TM backups? > > I find that whenever my laptop (over wifi!) starts a TM the ZFS machine it's backing up to grinds to a halt.. Other systems streaming stuff over NFS from it also tend to stall.. Are you using zfs compression? If so, try turning that off. I have a pool with a couple of filesystems with gzip-9 compression enabled. Whenever I write (using zfs receive, it is a backup server) to one of those volumes the whole pool stalls with lots of disk activity. Even creating a snapshot on another filesystem within the same pool lasts a couple of minutes. Does anyone know how to make this perform a little better? It's only writing small amounts (70-100 ops/s, 1 MB/s) on an otherwise idle pool. Still the drive leds blink like crazy. One of my two CPU cores is maxed out, the other is idle. I suppose it won't get any faster (it's CPU bound because of the heavy gzip compression), but why is the pool so slow? Is zfs receive using synchonous writes? Sorry for maybe being offtopic :-) Regards, Thomas From owner-freebsd-stable@FreeBSD.ORG Thu Apr 28 15:43:14 2011 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 B7E0B106566B for ; Thu, 28 Apr 2011 15:43:14 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from constantine.ingresso.co.uk (constantine.ingresso.co.uk [IPv6:2001:470:1f09:176e::3]) by mx1.freebsd.org (Postfix) with ESMTP id 801CC8FC16 for ; Thu, 28 Apr 2011 15:43:14 +0000 (UTC) Received: from dilbert.london-internal.ingresso.co.uk ([10.64.50.6] helo=dilbert.ingresso.co.uk) by constantine.ingresso.co.uk with esmtps (TLSv1:AES256-SHA:256) (Exim 4.73 (FreeBSD)) (envelope-from ) id 1QFTMy-000EEB-DI; Thu, 28 Apr 2011 16:43:08 +0100 Received: from petefrench by dilbert.ingresso.co.uk with local (Exim 4.74 (FreeBSD)) (envelope-from ) id 1QFTMy-000JA0-9I; Thu, 28 Apr 2011 16:43:08 +0100 To: edhoprima@gmail.com, fjwcash@gmail.com In-Reply-To: Message-Id: From: Pete French Date: Thu, 28 Apr 2011 16:43:08 +0100 Cc: freebsd-stable@freebsd.org, daniel@digsys.bg Subject: Re: correct way to setup gmirror on 7.4? 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, 28 Apr 2011 15:43:14 -0000 > Correct. The layering is not, in itself, the issue. The issue is > that the loader or kernel or whatever reads the first sector of the > disk, finds a GPT so it then looks for the backup GPT in the last > physical sector of the disk and doesn't find it. At this point, > gmirror is not loaded (or not noticed, since there's nothing in the > first sector of the disk to show it's a mirror). Once gmirror is > loaded, then the GPT stops complaining as the first and last sectors > of the gmirrror provider have the GPT tables. Is not the problem here that you are trying to GPT label a gmirrored disc ? If you instead gmirror two GPT partitions then the problem goes away doesnt it ? Thats how I set things up - use parititoning on the ohysical drives, and then put the mirroring into the partitions thus created. Works fine, and doesnt suffer from any of the afforementioned problems. -pete. From owner-freebsd-stable@FreeBSD.ORG Thu Apr 28 16:14:06 2011 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 68B12106566B for ; Thu, 28 Apr 2011 16:14:06 +0000 (UTC) (envelope-from mike@jellydonut.org) Received: from mail-ew0-f54.google.com (mail-ew0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 09D1D8FC12 for ; Thu, 28 Apr 2011 16:14:05 +0000 (UTC) Received: by ewy1 with SMTP id 1so1127174ewy.13 for ; Thu, 28 Apr 2011 09:14:04 -0700 (PDT) MIME-Version: 1.0 Received: by 10.213.113.129 with SMTP id a1mr1671331ebq.44.1304007244391; Thu, 28 Apr 2011 09:14:04 -0700 (PDT) Received: by 10.213.10.131 with HTTP; Thu, 28 Apr 2011 09:14:04 -0700 (PDT) In-Reply-To: References: Date: Thu, 28 Apr 2011 12:14:04 -0400 Message-ID: From: Michael Proto To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: correct way to setup gmirror on 7.4? 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, 28 Apr 2011 16:14:06 -0000 On Thu, Apr 28, 2011 at 11:43 AM, Pete French w= rote: >> Correct. =A0The layering is not, in itself, the issue. =A0The issue is >> that the loader or kernel or whatever reads the first sector of the >> disk, finds a GPT so it then looks for the backup GPT in the last >> physical sector of the disk and doesn't find it. =A0At this point, >> gmirror is not loaded (or not noticed, since there's nothing in the >> first sector of the disk to show it's a mirror). =A0Once gmirror is >> loaded, then the GPT stops complaining as the first and last sectors >> of the gmirrror provider have the GPT tables. > > Is not the problem here that you are trying to GPT label a gmirrored disc= ? > If you instead gmirror two GPT partitions then the problem goes away > doesnt it ? Thats how I set things up - use parititoning on the ohysical > drives, and then put the mirroring into the partitions thus created. > Works fine, and doesnt suffer from any of the afforementioned problems. > > -pete. > _______________________________________________ > 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" > Actually I was first creating 2 GPT partitions on each disk and then creating a mirror on each of those partitions (2 partitions per disk, 2 mirrors). When doing that I ran into the secondary GPT block displaying as "not found" during boot. As I mentioned, I didn't know if that was a problem per-se, which is why I posted to the list to see if there was a better way of mirroring partitions. From what I'm gathering, I think I did things correctly actually. -Proto From owner-freebsd-stable@FreeBSD.ORG Thu Apr 28 16:24:32 2011 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 14CBD106564A for ; Thu, 28 Apr 2011 16:24:32 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id BD1308FC14 for ; Thu, 28 Apr 2011 16:24:31 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1QFU0z-0005h8-Ne for freebsd-stable@freebsd.org; Thu, 28 Apr 2011 18:24:29 +0200 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 28 Apr 2011 18:24:29 +0200 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 28 Apr 2011 18:24:29 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Ivan Voras Date: Thu, 28 Apr 2011 18:24:18 +0200 Lines: 22 Message-ID: References: <20110427221554.GB22139@lava.net> <4DB9303E.9090305@digsys.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.12) Gecko/20101102 Thunderbird/3.1.6 In-Reply-To: X-Enigmail-Version: 1.1.2 Subject: Re: correct way to setup gmirror on 7.4? 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, 28 Apr 2011 16:24:32 -0000 On 28/04/2011 17:02, Edho P Arief wrote: > On Thu, Apr 28, 2011 at 9:40 PM, Freddie Cash wrote: >> Granted, there may be reasons why it wasn't done like this in the >> beginning, but my non-GEOM programmer's eyes can't see any. > > I believe one of the reason is it would prevent conversion from > non-gmirror disk to gmirror one as explained here > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/geom-mirror.html Actually, storing any kind of metadata in the first sector can lead to weird and unexpected problems with some buggy disk controllers which parse the MBR for some (wrong) reasons. I personally have a disk controller which hangs on boot if the MBR contains anything but primary partitions of DOS type (even changing the partition type makes it hang), and that is not the only disk controller I've seen with this type of a bug. The second reason is that storing anything except the MBR in the first sector makes the drive non-bootable (even if the controller is ok) and it is kind of nice to be able to make a cheap soft-RAID1 from two ordinary (S)ATA drives. From owner-freebsd-stable@FreeBSD.ORG Thu Apr 28 16:29:38 2011 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 94434106568A for ; Thu, 28 Apr 2011 16:29:38 +0000 (UTC) (envelope-from tevans.uk@googlemail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 4B13A8FC0C for ; Thu, 28 Apr 2011 16:29:38 +0000 (UTC) Received: by vxc34 with SMTP id 34so2893773vxc.13 for ; Thu, 28 Apr 2011 09:29:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=oJYq1wJ/Aao359wd6h+QO99RaoBWSq8SaUARtSAKi+4=; b=q51gUXEtofJTWXacsDOurtqzk8DbZMhNyJ01P4yEfL0oD/F8BCzxa8fGc+j61eI3Tz ZgWKmbtt23Yi9/rOarGe+EWO1DyUKraBF9rOVLiLxsQZEcOxRGzrlMHP0vFCZ2jU3Cun FioV5X29Ju5TjwzNAxt6FcQcHX1bH+Y4tbIXo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=tQfwDXcgL4pqPBQrCu5VII+o+WJ1fwvK3z9inKL05aUcwlNffiCr3vzEgftcOgjPhr vigShAYBXnbXqmN2wULwSGl2wVQxJVdM2mg40co+EykLFD/FCjUWlVWUNJfy4DBiOY0Q JGKOBET8WDKTIA53eV+9OjtO60lJCH96MPvIg= MIME-Version: 1.0 Received: by 10.52.111.10 with SMTP id ie10mr1859072vdb.81.1304006779564; Thu, 28 Apr 2011 09:06:19 -0700 (PDT) Received: by 10.52.111.229 with HTTP; Thu, 28 Apr 2011 09:06:19 -0700 (PDT) In-Reply-To: References: Date: Thu, 28 Apr 2011 17:06:19 +0100 Message-ID: From: Tom Evans To: Pete French Content-Type: text/plain; charset=UTF-8 Cc: freebsd-stable@freebsd.org Subject: Re: correct way to setup gmirror on 7.4? 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, 28 Apr 2011 16:29:38 -0000 On Thu, Apr 28, 2011 at 4:43 PM, Pete French wrote: > Is not the problem here that you are trying to GPT label a gmirrored disc ? > If you instead gmirror two GPT partitions then the problem goes away > doesnt it ? Thats how I set things up - use parititoning on the ohysical > drives, and then put the mirroring into the partitions thus created. > Works fine, and doesnt suffer from any of the afforementioned problems. > > -pete. Is this simple to do? When I setup my home ZFS server, I couldn't get it to boot from ZFS, so I configured 2 disks as 'boot' discs: => 34 2930277101 ada5 GPT (1.4T) 34 128 1 (null) (64K) 162 12582912 2 root (6.0G) 12583074 2917694061 3 samsung15-1 (1.4T) The other 'boot' disc is configured the same, except it has altroot/samsung15-2 labels on the UFS/ZFS GPT partitions (the other 4 discs have a corresponding 6 GB partition for swap/dumps). However, this is as far as I got. I currently have vfs.root.mountfrom="ufs:/dev/gpt/root", and I'd like to gmirror 'root' onto 'altroot', without overwriting GPT labels or anything dangerous! Cheers Tom From owner-freebsd-stable@FreeBSD.ORG Thu Apr 28 16:32:17 2011 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 257E21065741 for ; Thu, 28 Apr 2011 16:32:17 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from constantine.ingresso.co.uk (constantine.ingresso.co.uk [IPv6:2001:470:1f09:176e::3]) by mx1.freebsd.org (Postfix) with ESMTP id E11668FC22 for ; Thu, 28 Apr 2011 16:32:16 +0000 (UTC) Received: from dilbert.london-internal.ingresso.co.uk ([10.64.50.6] helo=dilbert.ingresso.co.uk) by constantine.ingresso.co.uk with esmtps (TLSv1:AES256-SHA:256) (Exim 4.73 (FreeBSD)) (envelope-from ) id 1QFU8J-000Ej3-4v; Thu, 28 Apr 2011 17:32:03 +0100 Received: from petefrench by dilbert.ingresso.co.uk with local (Exim 4.74 (FreeBSD)) (envelope-from ) id 1QFU8J-000JnI-42; Thu, 28 Apr 2011 17:32:03 +0100 To: petefrench@ingresso.co.uk, tevans.uk@googlemail.com In-Reply-To: Message-Id: From: Pete French Date: Thu, 28 Apr 2011 17:32:03 +0100 Cc: freebsd-stable@freebsd.org Subject: Re: correct way to setup gmirror on 7.4? 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, 28 Apr 2011 16:32:17 -0000 > Is this simple to do? When I setup my home ZFS server, I couldn't get > it to boot from ZFS, so I configured 2 disks as 'boot' discs: Its fairly simple - I generally dont boot from ZFs either, my standard config has a 4 gig UFS boot partition, and then a large zpool on the rest of the drive. usually I add in a bit of swap there, which I dnt mirror, so I get swap on each drive. So each disk looks like this with MBR da0s1 - 4 gig for / da0s2 - 2 gig for swap da0s3 - rest of drive for zpool because the gmirror is at the end of the partiton then the boot code finds the UFS filesystem at the start and boots from it not needing to know about gmirror. The gmirror is loaded in the boot process, and then mirrors the drive being booted with the other drive. I can boot of either drive and the system comes up fine. As for the zpool, well that sorts itself out fne, as ZFS is wont to do ;-) > => 34 2930277101 ada5 GPT (1.4T) > 34 128 1 (null) (64K) > 162 12582912 2 root (6.0G) > 12583074 2917694061 3 samsung15-1 (1.4T) > > The other 'boot' disc is configured the same, except it has > altroot/samsung15-2 labels on the UFS/ZFS GPT partitions (the other 4 > discs have a corresponding 6 GB partition for swap/dumps). > > However, this is as far as I got. I currently have > vfs.root.mountfrom="ufs:/dev/gpt/root", and I'd like to gmirror 'root' > onto 'altroot', without overwriting GPT labels or anything dangerous! I havent tried with GPT, but it should be the same as with MBR. Boot off the 1st drive, create a gmirror inside the root partition on the 2nd drive, newfs it and then cpdup the running system over to it. Make sure you do the necessaries on the 2nd drive to make it bootable as if you just had a standard UFS filesystem in that partition, with no gmirror. Now on te 2nd drive edit loader.conf so it looks something like this: geom_mirror_load="YES" vfs.root.mountfrom="ufs:/dev/mirror/mymirror" and fstab similarly: /dev/mirror/mymirror / ufs rw 2 2 Yu shuld now be able to boot from the 2nd drive fine. Check that works - it should come up OK, running wth your root on agmirror with a single element on that partition. At this point you can then add in the partition from the first disc to the mirror. Should now boot from either drive fine. as I said, I havent tried it with GPT, but there is no reason I can see that it wudnt work the same as with MBR. The only reason I still stick with MBR is that I like the FreeBSD boot loader which will let me choose F5 to select the next drive to boot from. Last time I looked there wasn't an exquivalent for GPT (if I missed this then I will now feel foolish...) cheers, -pete. From owner-freebsd-stable@FreeBSD.ORG Thu Apr 28 17:04:12 2011 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 9EA91106564A for ; Thu, 28 Apr 2011 17:04:12 +0000 (UTC) (envelope-from mwaltz@PACIFIC.EDU) Received: from mx30.pacific.edu (mx30.pacific.edu [138.9.110.74]) by mx1.freebsd.org (Postfix) with ESMTP id 7B90D8FC0A for ; Thu, 28 Apr 2011 17:04:12 +0000 (UTC) Received: from mx30.pacific.edu (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 0EADC2C5D8D; Thu, 28 Apr 2011 09:46:32 -0700 (PDT) Received: from EXCASHUB2.stk.pacific.edu (excashub2.stk.pacific.edu [10.9.4.122]) by mx30.pacific.edu (Postfix) with ESMTP id 74EEC2C5D7B; Thu, 28 Apr 2011 09:46:31 -0700 (PDT) Received: from EXMB2.STK.PACIFIC.EDU ([10.9.4.102]) by excashub2.stk.pacific.edu ([10.9.4.122]) with mapi id 14.01.0289.001; Thu, 28 Apr 2011 09:46:30 -0700 From: Malcolm Waltz To: Daniel O'Connor Thread-Topic: ZFS vs OSX Time Machine Thread-Index: AQHMBa0X6h4oagP/h0u8OmOQbCHfSJRz8aKA Date: Thu, 28 Apr 2011 16:46:30 +0000 Message-ID: References: <537A8F4F-A302-40F9-92DF-403388D99B4B@gsoft.com.au> In-Reply-To: <537A8F4F-A302-40F9-92DF-403388D99B4B@gsoft.com.au> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.9.104.200] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-PMX-Version: 5.6.0.2009776, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2011.4.28.162420 X-PerlMx-Spam: Gauge=XIII, Probability=13%, Report=' URI_HOSTNAME_CONTAINS_EQUALS 1, BLOGSPOT_URI 0.05, KNOWN_FREEWEB_URI 0.05, SUPERLONG_LINE 0.05, BODYTEXTP_SIZE_3000_LESS 0, BODY_SIZE_2000_2999 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, ECARD_KNOWN_DOMAINS 0, FROM_EDU_TLD 0, WEBMAIL_SOURCE 0, WEBMAIL_XOIP 0, WEBMAIL_X_IP_HDR 0, __BOUNCE_CHALLENGE_SUBJ 0, __BOUNCE_NDR_SUBJ_EXEMPT 0, __CANPHARM_UNSUB_LINK 0, __CP_MEDIA_BODY 0, __CP_URI_IN_BODY 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_XOIP 0, __INT_PROD_COMP 0, __KNOWN_FREEWEB_URI1 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __MSGID_APPLEMAIL 0, __PHISH_SPEAR_STRUCTURE_1 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __URI_NS ' Cc: freebsd-stable List Subject: Re: ZFS vs OSX Time Machine 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, 28 Apr 2011 17:04:12 -0000 I doubt the issues you are encountering have much to do with ZFS. It sounds like you are using TimeMachine over NFS. Obviously, Apple does n= ot support that configuration: http://www.google.com/search?q=3Dtime+machine+nfs+site:apple.com In my opinion, TimeMachine should only be used with block storage. If you = use any kind of file-sharing protocol (AFP, SMB/CIFS or NFS), TimeMachine i= s implemented using a sparse disk image broken into hundreds or thousands o= f separate files. This is a hack at best. Time machine works very well with locally attached storage, but if you need= to use network storage, you might want to try iSCSI: http://thegreyblog.blogspot.com/2010/02/using-zfs-with-apple-time-machine.h= tml http://people.freebsd.org/~rse/iscsi/iscsi.txt On Apr 28, 2011, at 7:03 AM, Daniel O'Connor wrote: > Does anyone else use ZFS to store TM backups? >=20 > I find that whenever my laptop (over wifi!) starts a TM the ZFS machine i= t's backing up to grinds to a halt.. Other systems streaming stuff over NFS= from it also tend to stall.. >=20 > I presume that TM is doing something which causes ZFS some issues but I'm= not sure how to find out what the real problem is let alone how to fix it.= . >=20 > I am running FreeBSD midget.dons.net.au 8.2-PRERELEASE FreeBSD 8.2-PREREL= EASE #8 r217094M: Sat Jan 8 11:15:07 CST 2011 darius@midget.dons.net.a= u:/usr/obj/usr/src/sys/MIDGET amd64 >=20 > It is a 5 disk RAIDZ1 with 1.29Tb free using WD10EADS drives. >=20 > I don't see any SMART errors or ZFS warnings. >=20 > I have the following ZFS related tunables >=20 > vfs.zfs.arc_max=3D"3072M" > vfs.zfs.prefetch_disable=3D"1"=20 > vfs.zfs.txg.timeout=3D5 > vfs.zfs.cache_flush_disable=3D1 >=20 > Any help appreciated, thanks :) >=20 > -- > Daniel O'Connor software and network engineer > for Genesis Software - http://www.gsoft.com.au > "The nice thing about standards is that there > are so many of them to choose from." > -- Andrew Tanenbaum > GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C >=20 >=20 >=20 >=20 >=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" From owner-freebsd-stable@FreeBSD.ORG Thu Apr 28 17:34:23 2011 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 BADA4106566B for ; Thu, 28 Apr 2011 17:34:23 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 4F2DD8FC12 for ; Thu, 28 Apr 2011 17:34:22 +0000 (UTC) Received: by fxm11 with SMTP id 11so2837583fxm.13 for ; Thu, 28 Apr 2011 10:34:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=lwvZzPSt6RPZkxIYpuD8jDXGLQzrrGNGJ3VymA+2fT8=; b=gkkrXXp6ocupfcZgLlsmkVtMpp6pXQXWbX/Z88yZHY6aXTkZ4UAOxd4gX+vJt/I1DX pSEg0KwA+kdFzLgkDFcHyEi9X5WJtkL5Y2shijqp3jWt89XYDDyrA3q/KUonEu/qmNNj DAR719hl1AKR9mp/kVl/ixi8f17o1XLpe9Ikc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=RwitEre7IrCt/+qtXuGa6IalFG9I0iofa3/PIyW1OtUuC91XoXjnMjaeOe4mzBSFl3 Yacx8Fb0xSoFh/7y7AFLcQ22fcYNXRuZA9hzeICTev8fGo7ATLZmAyNRtLDYPAgP70+T FKWP17JaDi64Kf7ayk+DLrDZcD8KZf1wglegE= MIME-Version: 1.0 Received: by 10.223.97.142 with SMTP id l14mr885821fan.111.1304012061922; Thu, 28 Apr 2011 10:34:21 -0700 (PDT) Received: by 10.223.20.145 with HTTP; Thu, 28 Apr 2011 10:34:21 -0700 (PDT) In-Reply-To: <4DB9887A.4080109@ronner.org> References: <537A8F4F-A302-40F9-92DF-403388D99B4B@gsoft.com.au> <4DB9887A.4080109@ronner.org> Date: Thu, 28 Apr 2011 12:34:21 -0500 Message-ID: From: Adam Vande More To: Thomas Ronner Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: ZFS vs OSX Time Machine 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, 28 Apr 2011 17:34:23 -0000 On Thu, Apr 28, 2011 at 10:32 AM, Thomas Ronner wrote: > On 4/28/11 4:03 PM, Daniel O'Connor wrote: > >> Does anyone else use ZFS to store TM backups? >> >> I find that whenever my laptop (over wifi!) starts a TM the ZFS machine >> it's backing up to grinds to a halt.. Other systems streaming stuff over NFS >> from it also tend to stall.. >> > > > Are you using zfs compression? If so, try turning that off. > > I have a pool with a couple of filesystems with gzip-9 compression enabled. > Whenever I write (using zfs receive, it is a backup server) to one of those > volumes the whole pool stalls with lots of disk activity. Even creating a > snapshot on another filesystem within the same pool lasts a couple of > minutes. > > Does anyone know how to make this perform a little better? It's only > writing small amounts (70-100 ops/s, 1 MB/s) on an otherwise idle pool. > Still the drive leds blink like crazy. One of my two CPU cores is maxed out, > the other is idle. I suppose it won't get any faster (it's CPU bound because > of the heavy gzip compression), but why is the pool so slow? Is zfs receive > using synchonous writes? > gzip-9 is very poor choice for most datasets. It's going to be extremely slow especially with data that can't be compressed easily eg data that already compressed or encrypted. So yeah, if you're running into a cpu bottleneck, change your compression algo. I find lzjb to be a good one for general use. And to the OP, I'm not familar with TM, but see if disabling sendfile in any of your daemons helps. Also I don't think you want this setting: vfs.zfs.cache_flush_disable=1 -- Adam Vande More From owner-freebsd-stable@FreeBSD.ORG Thu Apr 28 18:25:59 2011 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 2A3C3106564A for ; Thu, 28 Apr 2011 18:25:59 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from asmtpout029.mac.com (asmtpout029.mac.com [17.148.16.104]) by mx1.freebsd.org (Postfix) with ESMTP id 0BDE08FC13 for ; Thu, 28 Apr 2011 18:25:58 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from cswiger1.apple.com ([17.209.4.71]) by asmtp029.mac.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPSA id <0LKD002AEKJ9J090@asmtp029.mac.com> for freebsd-stable@freebsd.org; Thu, 28 Apr 2011 11:25:58 -0700 (PDT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.2.15,1.0.148,0.0.0000 definitions=2011-04-28_06:2011-04-28, 2011-04-28, 1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=0 phishscore=0 bulkscore=1 adultscore=0 classifier=spam adjust=0 reason=mlx engine=6.0.2-1012030000 definitions=main-1104280114 From: Chuck Swiger In-reply-to: <537A8F4F-A302-40F9-92DF-403388D99B4B@gsoft.com.au> Date: Thu, 28 Apr 2011 11:25:56 -0700 Message-id: <2B80846C-E8A9-4FF6-962C-9405469661D6@mac.com> References: <537A8F4F-A302-40F9-92DF-403388D99B4B@gsoft.com.au> To: Daniel O'Connor X-Mailer: Apple Mail (2.1084) Cc: freebsd-stable List Subject: Re: ZFS vs OSX Time Machine 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, 28 Apr 2011 18:25:59 -0000 On Apr 28, 2011, at 7:03 AM, Daniel O'Connor wrote: > Does anyone else use ZFS to store TM backups? > > I find that whenever my laptop (over wifi!) starts a TM the ZFS machine it's backing up to grinds to a halt.. Other systems streaming stuff over NFS from it also tend to stall.. > > I presume that TM is doing something which causes ZFS some issues but I'm not sure how to find out what the real problem is let alone how to fix it.. Caveat: Time Machine is a viable backup system, but you're outside the configurations which it supports. TM really wants the backup to be located on an HFS+ filesystem because it makes very extensive use of hard links-- including hard links to directories-- which are not widely supported by other Unix filesystems. Even if you choose to continue using ZFS storage, please note that you'll obtain significantly better results by using AFP instead of NFS filesharing. Wikipedia has useful info here: http://en.wikipedia.org/wiki/Time_Machine_%28Mac_OS%29 http://en.wikipedia.org/wiki/Apple_Filing_Protocol Regards, -- -Chuck From owner-freebsd-stable@FreeBSD.ORG Thu Apr 28 19:17:27 2011 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 C83DF106564A for ; Thu, 28 Apr 2011 19:17:27 +0000 (UTC) (envelope-from gkontos.mail@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 8BE6D8FC17 for ; Thu, 28 Apr 2011 19:17:27 +0000 (UTC) Received: by iyj12 with SMTP id 12so3491223iyj.13 for ; Thu, 28 Apr 2011 12:17:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=+QAsya8k/TPxwQcp6x4MrAsS4w7V9yRi52gy0zy/mUs=; b=eOY/ZoM7YEPuoRrJvS3au+WI/xnx6UXxMG2aJJ7NiRIjffyvBa3ACLcnZkjixuIKZm bPwAjGYw0rHfkaE7RXiELdNNp5UuJVz0uAuHC/vpiPsfmJIKp1nsQySzvQZbszy4SLO/ Tjnbn5OxmyAuEdYdGuv6yotwZetOAPE4KVZ88= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=SdTIY9TtQd44nwoWtJe2r5coFZoyX3oC/2PK+mwSFewKSQ54TAzGONG62vowQDVh8+ Ar+aL+YmIIgeoWIgEDhha82yeLuu9dxaqc51UP84ViukVy1v3fKPiJ6Xdgv2oPpMiTt9 SdWOl9+/wQdOAGa1Ql3u4FMYMYpG4Wd8K5srE= MIME-Version: 1.0 Received: by 10.231.92.206 with SMTP id s14mr2937482ibm.106.1304018246939; Thu, 28 Apr 2011 12:17:26 -0700 (PDT) Received: by 10.231.35.2 with HTTP; Thu, 28 Apr 2011 12:17:26 -0700 (PDT) In-Reply-To: <2B80846C-E8A9-4FF6-962C-9405469661D6@mac.com> References: <537A8F4F-A302-40F9-92DF-403388D99B4B@gsoft.com.au> <2B80846C-E8A9-4FF6-962C-9405469661D6@mac.com> Date: Thu, 28 Apr 2011 22:17:26 +0300 Message-ID: From: George Kontostanos To: FreeBSD Stable Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: ZFS vs OSX Time Machine 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, 28 Apr 2011 19:17:27 -0000 I am using TM over smb on a ZFS Raidz1 pool of my fileserver with no problems whatsoever. NAME USED AVAIL REFER MOUNTPOINT tank/apple 37.2G 82.8G 37.2G /tank/apple Oldest backup 14 December 2009 On Thu, Apr 28, 2011 at 9:25 PM, Chuck Swiger wrote: > On Apr 28, 2011, at 7:03 AM, Daniel O'Connor wrote: > > Does anyone else use ZFS to store TM backups? > > > > I find that whenever my laptop (over wifi!) starts a TM the ZFS machine > it's backing up to grinds to a halt.. Other systems streaming stuff over NFS > from it also tend to stall.. > > > > I presume that TM is doing something which causes ZFS some issues but I'm > not sure how to find out what the real problem is let alone how to fix it.. > > > Caveat: Time Machine is a viable backup system, but you're outside the > configurations which it supports. > > TM really wants the backup to be located on an HFS+ filesystem because it > makes very extensive use of hard links-- including hard links to > directories-- which are not widely supported by other Unix filesystems. > Even if you choose to continue using ZFS storage, please note that you'll > obtain significantly better results by using AFP instead of NFS filesharing. > > Wikipedia has useful info here: > > http://en.wikipedia.org/wiki/Time_Machine_%28Mac_OS%29 > http://en.wikipedia.org/wiki/Apple_Filing_Protocol > > Regards, > -- > -Chuck > > _______________________________________________ > 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" > -- George Kontostanos aisecure.net From owner-freebsd-stable@FreeBSD.ORG Thu Apr 28 19:33:18 2011 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 77D421065670 for ; Thu, 28 Apr 2011 19:33:18 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from asmtpout026.mac.com (asmtpout026.mac.com [17.148.16.101]) by mx1.freebsd.org (Postfix) with ESMTP id 5C4858FC08 for ; Thu, 28 Apr 2011 19:33:18 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from cswiger1.apple.com ([17.209.4.71]) by asmtp026.mac.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPSA id <0LKD00MT4NN5IC00@asmtp026.mac.com> for freebsd-stable@freebsd.org; Thu, 28 Apr 2011 12:33:06 -0700 (PDT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.2.15,1.0.148,0.0.0000 definitions=2011-04-28_06:2011-04-28, 2011-04-28, 1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=6.0.2-1012030000 definitions=main-1104280128 From: Chuck Swiger In-reply-to: Date: Thu, 28 Apr 2011 12:33:05 -0700 Message-id: <8D2285F1-3706-4FEB-A4B4-10089AC7A622@mac.com> References: <537A8F4F-A302-40F9-92DF-403388D99B4B@gsoft.com.au> <2B80846C-E8A9-4FF6-962C-9405469661D6@mac.com> To: George Kontostanos X-Mailer: Apple Mail (2.1084) Cc: FreeBSD Stable Subject: Re: ZFS vs OSX Time Machine 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, 28 Apr 2011 19:33:18 -0000 On Apr 28, 2011, at 12:17 PM, George Kontostanos wrote: > I am using TM over smb on a ZFS Raidz1 pool of my fileserver with no problems whatsoever. > > NAME USED AVAIL REFER MOUNTPOINT > tank/apple 37.2G 82.8G 37.2G /tank/apple > > Oldest backup 14 December 2009 SMB aka CIFS is a better choice than NFS, because it supports better locking (oplocks or "stealable" locks), but it is not as good as AFP for this particular purpose. Also, ZFS isn't going to be as space efficient at storing TM backups compared with HFS+, because it doesn't support hard links to directories. Regards, -- -Chuck From owner-freebsd-stable@FreeBSD.ORG Thu Apr 28 19:56:07 2011 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 8DDC9106566C for ; Thu, 28 Apr 2011 19:56:07 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta06.westchester.pa.mail.comcast.net (qmta06.westchester.pa.mail.comcast.net [76.96.62.56]) by mx1.freebsd.org (Postfix) with ESMTP id 38D3A8FC0A for ; Thu, 28 Apr 2011 19:56:06 +0000 (UTC) Received: from omta01.westchester.pa.mail.comcast.net ([76.96.62.11]) by qmta06.westchester.pa.mail.comcast.net with comcast id d7uy1g0050EZKEL567w7wX; Thu, 28 Apr 2011 19:56:07 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta01.westchester.pa.mail.comcast.net with comcast id d7w31g0241t3BNj3M7w3eV; Thu, 28 Apr 2011 19:56:05 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 97D7E9B418; Thu, 28 Apr 2011 12:56:01 -0700 (PDT) Date: Thu, 28 Apr 2011 12:56:01 -0700 From: Jeremy Chadwick To: Daniel O'Connor Message-ID: <20110428195601.GA31807@icarus.home.lan> References: <537A8F4F-A302-40F9-92DF-403388D99B4B@gsoft.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <537A8F4F-A302-40F9-92DF-403388D99B4B@gsoft.com.au> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable List Subject: Re: ZFS vs OSX Time Machine 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, 28 Apr 2011 19:56:07 -0000 On Thu, Apr 28, 2011 at 11:33:22PM +0930, Daniel O'Connor wrote: > Does anyone else use ZFS to store TM backups? > > I find that whenever my laptop (over wifi!) starts a TM the ZFS machine it's backing up to grinds to a halt.. Other systems streaming stuff over NFS from it also tend to stall.. > > I presume that TM is doing something which causes ZFS some issues but I'm not sure how to find out what the real problem is let alone how to fix it.. > > I am running FreeBSD midget.dons.net.au 8.2-PRERELEASE FreeBSD 8.2-PRERELEASE #8 r217094M: Sat Jan 8 11:15:07 CST 2011 darius@midget.dons.net.au:/usr/obj/usr/src/sys/MIDGET amd64 > > It is a 5 disk RAIDZ1 with 1.29Tb free using WD10EADS drives. > > I don't see any SMART errors or ZFS warnings. > > I have the following ZFS related tunables > > vfs.zfs.arc_max="3072M" > vfs.zfs.prefetch_disable="1" > vfs.zfs.txg.timeout=5 > vfs.zfs.cache_flush_disable=1 Are the last two actually *working* in /boot/loader.conf? Can you verify by looking at them via sysctl? AFAIK they shouldn't work, since they lack double-quotes around the values. Parsing errors are supposed to throw you back to the loader prompt. See loader.conf(5) for the syntax. I'm also not sure why you're setting cache_flush_disable at all. > Any help appreciated, thanks :) Others seem to be battling stating that "NFS doesn't work for TM", but that isn't what you're complaining about. You're complaining that FreeBSD with ZFS + NFS performs extremely poorly when trying to do backups from an OS X client using TM (writing to the NFS mount). I have absolutely no experience with TM or OS X, so if it's actually a client-level problem (which I'm doubting) I can't help you there. Just sort of a ramble here at different things... It would be useful to provide ZFS ARC sysctl data from the FreeBSD system where you're seeing performance issues. "sysctl -a kstat.zfs.misc.arcstats" should suffice. You should also try executing "zpool iostat -v 1" during the TM backup to see if there's a particular device which is behaving poorly. There have been reports of ZFS pools behaving poorly when a single device within the pool has slow I/O (e.g. 5 hard disks, one of which has internal issues, resulting in the entire pool performing horribly). You should let this run for probably 60-120 seconds to get an idea. Given your parameters above (assuming vfs.zfs.txg.timeout IS in fact 5!), you should see "bursts" of writes every 5 seconds. I know that there are some things on ZFS that perform badly overall. Anything that involves excessive/large numbers of files (not file sizes, but actual files themselves) seems to perform not-so-great with ZFS. For example, Maildir on ZFS = piss-poor performance. There are ways to work around this issue (if I remember correctly, by adding a dedicated "log" device to your ZFS pool, but be aware your log devices need to be reliable (if you have a single log device and it fails the entire pool is damaged, if I remember right)), but I don't consider it feasible. So if TM is creating tons of files on the NFS mount (backed by ZFS), then I imagine the performance isn't so great. Could you please provide the following sysctl values? Thanks. kern.maxvnodes kern.minvnodes vfs.freevnodes vfs.numvnodes If the FreeBSD machine has a wireless card in it, if at all possible could you try ruling that out by hooking up wired Ethernet instead? It's probably not the cause, but worth trying anyway. If you have a home router or something doing 802.11, don't bother with this idea. Next, you COULD try using Samba/CIFS on the FreeBSD box to see if you can narrow the issue down to bad NFS performance. Please see this post of mine about tuning Samba on FreeBSD (backed by ZFS) to get extremely good performance. Many people responded and said their performance drastically improved (you can see the thread yourself). The trick is AIO. You can ignore the part about setting vm.kmem_size in loader.conf; that advice is now old/deprecated (does not pertain to you given the date of your kernel), and vfs.zfs.txg.write_limit_override is something you shouldn't mess with unless absolutely needed to leave it default: http://lists.freebsd.org/pipermail/freebsd-stable/2011-February/061642.html Finally, when was the last time this FreeBSD machine was rebooted? Some people have seen horrible performance that goes away after a reboot. There's some speculation that memory fragmentation has something to do with it. I simply don't know. I'm not telling you to reboot the box (please don't; it would be more useful if it could be kept up in case folks want to do analysis of it). -- | Jeremy Chadwick jdc@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 Apr 28 20:45:34 2011 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 C813C1065670 for ; Thu, 28 Apr 2011 20:45:34 +0000 (UTC) (envelope-from mwaltz@PACIFIC.EDU) Received: from mx10.pacific.edu (mx10.pacific.edu [138.9.240.95]) by mx1.freebsd.org (Postfix) with ESMTP id 9B3FB8FC17 for ; Thu, 28 Apr 2011 20:45:34 +0000 (UTC) Received: from mx10.pacific.edu (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 39710A49E50; Thu, 28 Apr 2011 13:45:34 -0700 (PDT) Received: from EXCASHUB1.stk.pacific.edu (excashub1.stk.pacific.edu [10.9.4.121]) by mx10.pacific.edu (Postfix) with ESMTP id F2893A49D04; Thu, 28 Apr 2011 13:45:33 -0700 (PDT) Received: from EXMB2.STK.PACIFIC.EDU ([10.9.4.102]) by excashub1.stk.pacific.edu ([10.9.4.121]) with mapi id 14.01.0289.001; Thu, 28 Apr 2011 13:45:34 -0700 From: Malcolm Waltz To: Chuck Swiger Thread-Topic: ZFS vs OSX Time Machine Thread-Index: AQHMBa0X6h4oagP/h0u8OmOQbCHfSJR0DWwAgAAOYwCAAARggIAAFD+A Date: Thu, 28 Apr 2011 20:45:33 +0000 Message-ID: References: <537A8F4F-A302-40F9-92DF-403388D99B4B@gsoft.com.au> <2B80846C-E8A9-4FF6-962C-9405469661D6@mac.com> <8D2285F1-3706-4FEB-A4B4-10089AC7A622@mac.com> In-Reply-To: <8D2285F1-3706-4FEB-A4B4-10089AC7A622@mac.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.9.104.200] Content-Type: text/plain; charset="us-ascii" Content-ID: <39424AA978AA2840B5B855915326F3A7@pacific.local> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-PMX-Version: 5.6.0.2009776, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2011.4.28.203318 X-PerlMx-Spam: Gauge=IIIIIIII, Probability=8%, Report=' SUPERLONG_LINE 0.05, BODYTEXTP_SIZE_3000_LESS 0, BODY_SIZE_2000_2999 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, FROM_EDU_TLD 0, WEBMAIL_SOURCE 0, WEBMAIL_XOIP 0, WEBMAIL_X_IP_HDR 0, __BOUNCE_CHALLENGE_SUBJ 0, __BOUNCE_NDR_SUBJ_EXEMPT 0, __CANPHARM_UNSUB_LINK 0, __CP_MEDIA_BODY 0, __CP_URI_IN_BODY 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_XOIP 0, __LINES_OF_YELLING 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __MSGID_APPLEMAIL 0, __PHISH_SPEAR_STRUCTURE_1 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __URI_NO_WWW 0, __URI_NS ' Cc: FreeBSD Stable Subject: Re: ZFS vs OSX Time Machine 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, 28 Apr 2011 20:45:35 -0000 AFP is not the same as HFS+. Time Machine will work better with AFP than N= FS or SMB/CIFS, but it's still not using native HFS+ unless you are using b= lock storage (even if you use AFP with an HFS+ filesystem). Time Machine cannot function at all without accessing HFS+ directly. If yo= u are using a network filesystem (AFP, SMB/CIFS or NFS), Time Machine creat= es a sparse disk image, formatted as HFS+ and stores it on your file-server= . It then attaches that disk image as a disk device and mounts it (somewha= t like "mdconfig -a -t vnode -f /path/to/disk-image -u 1; mount /dev/md1 /m= nt"). It then treats that disk image basically the same way that it treats= local attached storage, including creating hard directory links (but all i= nside the disk image). See man hdiutil (on OS X) for more info, particular= ly the part about SPARSEBUNDLEs, sparse images backing HFS+ filesystems and= band sizes. Even if you use Mac OS 10 Server and create a Time Machine share (which is = the best case scenario), it still uses emulated block storage as described = above (disk image over AFP on HFS+). I have personally done this and decid= ed that it was not a very good solution. Your milage may very. I know tha= t people do this, but it seems rather silly. If you have the knowledge to use ZFS, use a zvol via iSCSI. It is much mor= e efficient to use a form of network storage that handles block access nati= vely (like iSCSI) instead of accessing emulated block storage via file-shar= ing protocols that were not designed for such use. ZFS doesn't care what y= ou use it for. If you are using ZFSv28 (I wouldn't use it for critical dat= a on FreeBSD yet) you can even do dedupe and compression on a native HFS+ T= ime Machine volume (although you would only see the saved space from the pe= rspective of the zpool and make sure you have lots of RAM).=20 On Apr 28, 2011, at 12:33 PM, Chuck Swiger wrote: > On Apr 28, 2011, at 12:17 PM, George Kontostanos wrote: >> I am using TM over smb on a ZFS Raidz1 pool of my fileserver with no pro= blems whatsoever. =20 >>=20 >> NAME USED AVAIL REFER MOUNTPOINT >> tank/apple 37.2G 82.8G 37.2G /tank/apple >>=20 >> Oldest backup 14 December 2009 >=20 > SMB aka CIFS is a better choice than NFS, because it supports better lock= ing (oplocks or "stealable" locks), but it is not as good as AFP for this p= articular purpose. Also, ZFS isn't going to be as space efficient at stori= ng TM backups compared with HFS+, because it doesn't support hard links to = directories. >=20 > Regards, > --=20 > -Chuck >=20 >=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" From owner-freebsd-stable@FreeBSD.ORG Thu Apr 28 20:47:28 2011 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 3CAC4106566B for ; Thu, 28 Apr 2011 20:47:28 +0000 (UTC) (envelope-from bsd@vink.pl) Received: from mail-px0-f176.google.com (mail-px0-f176.google.com [209.85.212.176]) by mx1.freebsd.org (Postfix) with ESMTP id 17A748FC0A for ; Thu, 28 Apr 2011 20:47:28 +0000 (UTC) Received: by pxi11 with SMTP id 11so263492pxi.35 for ; Thu, 28 Apr 2011 13:47:27 -0700 (PDT) Received: by 10.142.140.8 with SMTP id n8mr935854wfd.214.1304022040355; Thu, 28 Apr 2011 13:20:40 -0700 (PDT) Received: from mail-pv0-f182.google.com (mail-pv0-f182.google.com [74.125.83.182]) by mx.google.com with ESMTPS id a6sm1412442pbs.81.2011.04.28.13.20.39 (version=SSLv3 cipher=OTHER); Thu, 28 Apr 2011 13:20:40 -0700 (PDT) Received: by pvg11 with SMTP id 11so2628794pvg.13 for ; Thu, 28 Apr 2011 13:20:39 -0700 (PDT) MIME-Version: 1.0 Received: by 10.68.34.136 with SMTP id z8mr3726328pbi.355.1304022039130; Thu, 28 Apr 2011 13:20:39 -0700 (PDT) Received: by 10.68.42.40 with HTTP; Thu, 28 Apr 2011 13:20:39 -0700 (PDT) Date: Thu, 28 Apr 2011 22:20:39 +0200 Message-ID: From: Wiktor Niesiobedzki To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: No data received with Intel Corporation Gigabit CT Desktop Adapter (82574L) 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, 28 Apr 2011 20:47:28 -0000 Hi, I've installed Intel Gigabit CT Desktop Adapter in my FreeBSD 8.2 box and I can't see any incoming traffic on this card. Even ARP resolution doesn't work. Though I see the outgoing traffic on the other end. Relevant info: kadlubek# uname -a FreeBSD kadlubek 8.2-PRERELEASE FreeBSD 8.2-PRERELEASE #20: Sat Feb 12 21:22:19 CET 2011 root@kadlubek:/usr/obj/usr/src/sys/KADLUB i386 kadlubek# dmesg | grep em0 em0: port 0xdc00-0xdc1f mem 0xfe9e0000-0xfe9fffff,0xfe900000-0xfe97ffff,0xfe9dc000-0xfe9dffff irq 24 at device 0.0 on pci2 em0: Using MSIX interrupts with 0 vectors em0: [FILTER] kadlubek# ping 192.168.115.1 PING 192.168.115.1 (192.168.115.1): 56 data bytes ping: sendto: Host is down ping: sendto: Host is down In mean time - tcpdump shows: kadlubek# tcpdump -i em0 22:03:55.962118 ARP, Request who-has 192.168.115.1 tell 192.168.115.220, length 28 22:03:56.967107 ARP, Request who-has 192.168.115.1 tell 192.168.115.220, length 28 22:03:57.972094 ARP, Request who-has 192.168.115.1 tell 192.168.115.220, length 28 I've checked the firewall rules, but there are none there: kadlubek# pfctl -s rules No ALTQ support in kernel ALTQ related functions disabled pciconf -lv shows the card as: em0@pci0:2:0:0: class=3D0x020000 card=3D0xa01f8086 chip=3D0x10d38086 rev=3D= 0x00 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'Intel 82574L Gigabit Ethernet Controller (82574L)' class =3D network subclass =3D ethernet kadlubek# sysctl dev.em.0 dev.em.0.%desc: Intel(R) PRO/1000 Network Connection 7.1.9 dev.em.0.%driver: em dev.em.0.%location: slot=3D0 function=3D0 handle=3D\_SB_.PCI0.NBPG.NPGS dev.em.0.%pnpinfo: vendor=3D0x8086 device=3D0x10d3 subvendor=3D0x8086 subdevice=3D0xa01f class=3D0x020000 dev.em.0.%parent: pci2 dev.em.0.nvm: -1 dev.em.0.debug: -1 dev.em.0.rx_int_delay: 0 dev.em.0.tx_int_delay: 66 dev.em.0.rx_abs_int_delay: 66 dev.em.0.tx_abs_int_delay: 66 dev.em.0.rx_processing_limit: 100 dev.em.0.flow_control: 3 dev.em.0.link_irq: 0 dev.em.0.mbuf_alloc_fail: 0 dev.em.0.cluster_alloc_fail: 0 dev.em.0.dropped: 0 dev.em.0.tx_dma_fail: 0 dev.em.0.rx_overruns: 0 dev.em.0.watchdog_timeouts: 0 dev.em.0.device_control: 1477444168 dev.em.0.rx_control: 67141634 dev.em.0.fc_high_water: 18432 dev.em.0.fc_low_water: 16932 dev.em.0.queue0.txd_head: 35 dev.em.0.queue0.txd_tail: 35 dev.em.0.queue0.tx_irq: 0 dev.em.0.queue0.no_desc_avail: 0 dev.em.0.queue0.rxd_head: 117 dev.em.0.queue0.rxd_tail: 1023 dev.em.0.queue0.rx_irq: 0 dev.em.0.mac_stats.excess_coll: 0 dev.em.0.mac_stats.single_coll: 0 dev.em.0.mac_stats.multiple_coll: 0 dev.em.0.mac_stats.late_coll: 0 dev.em.0.mac_stats.collision_count: 0 dev.em.0.mac_stats.symbol_errors: 0 dev.em.0.mac_stats.sequence_errors: 0 dev.em.0.mac_stats.defer_count: 0 dev.em.0.mac_stats.missed_packets: 0 dev.em.0.mac_stats.recv_no_buff: 0 dev.em.0.mac_stats.recv_undersize: 0 dev.em.0.mac_stats.recv_fragmented: 0 dev.em.0.mac_stats.recv_oversize: 0 dev.em.0.mac_stats.recv_jabber: 0 dev.em.0.mac_stats.recv_errs: 0 dev.em.0.mac_stats.crc_errs: 0 dev.em.0.mac_stats.alignment_errs: 0 dev.em.0.mac_stats.coll_ext_errs: 0 dev.em.0.mac_stats.xon_recvd: 0 dev.em.0.mac_stats.xon_txd: 0 dev.em.0.mac_stats.xoff_recvd: 0 dev.em.0.mac_stats.xoff_txd: 0 dev.em.0.mac_stats.total_pkts_recvd: 117 dev.em.0.mac_stats.good_pkts_recvd: 117 dev.em.0.mac_stats.bcast_pkts_recvd: 41 dev.em.0.mac_stats.mcast_pkts_recvd: 42 dev.em.0.mac_stats.rx_frames_64: 71 dev.em.0.mac_stats.rx_frames_65_127: 0 dev.em.0.mac_stats.rx_frames_128_255: 35 dev.em.0.mac_stats.rx_frames_256_511: 11 dev.em.0.mac_stats.rx_frames_512_1023: 0 dev.em.0.mac_stats.rx_frames_1024_1522: 0 dev.em.0.mac_stats.good_octets_recvd: 15499 dev.em.0.mac_stats.good_octets_txd: 2240 dev.em.0.mac_stats.total_pkts_txd: 35 dev.em.0.mac_stats.good_pkts_txd: 35 dev.em.0.mac_stats.bcast_pkts_txd: 35 dev.em.0.mac_stats.mcast_pkts_txd: 0 dev.em.0.mac_stats.tx_frames_64: 35 dev.em.0.mac_stats.tx_frames_65_127: 0 dev.em.0.mac_stats.tx_frames_128_255: 0 dev.em.0.mac_stats.tx_frames_256_511: 0 dev.em.0.mac_stats.tx_frames_512_1023: 0 dev.em.0.mac_stats.tx_frames_1024_1522: 0 dev.em.0.mac_stats.tso_txd: 0 dev.em.0.mac_stats.tso_ctx_fail: 0 dev.em.0.interrupts.asserts: 2 dev.em.0.interrupts.rx_pkt_timer: 0 dev.em.0.interrupts.rx_abs_timer: 0 dev.em.0.interrupts.tx_pkt_timer: 0 dev.em.0.interrupts.tx_abs_timer: 0 dev.em.0.interrupts.tx_queue_empty: 0 dev.em.0.interrupts.tx_queue_min_thresh: 0 dev.em.0.interrupts.rx_desc_min_thresh: 0 dev.em.0.interrupts.rx_overrun: 0 dev.em.0.wake: 0 kadlubek# sysctl dev.em.0.debug=3D1 Interface is RUNNING and INACTIVE em0: hw tdh =3D 35, hw tdt =3D 35 em0: hw rdh =3D 118, hw rdt =3D 1023 em0: Tx Queue Status =3D 1 em0: TX descriptors avail =3D 989 em0: Tx Descriptors avail failure =3D 0 em0: RX discarded packets =3D 0 em0: RX Next to Check =3D 0 em0: RX Next to Refresh =3D 0 I've tried booting linux on this box, and card is detected as follows: [ 16.376557] e1000e: Intel(R) PRO/1000 Network Driver - 1.2.20-k2 [ 16.376650] e1000e: Copyright(c) 1999 - 2011 Intel Corporation. [ 16.376949] e1000e 0000:02:00.0: PCI INT A -> GSI 24 (level, low) -> IRQ= 24 [ 16.377034] e1000e 0000:02:00.0: PCI: Disallowing DAC for device [ 16.377152] e1000e 0000:02:00.0: setting latency timer to 64 [ 16.377387] e1000e 0000:02:00.0: (unregistered net_device): Failed to initialize MSI-X interrupts. Falling back to MSI interrupts. [ 16.377511] e1000e 0000:02:00.0: (unregistered net_device): Failed to initialize MSI interrupts. Falling back to legacy interrupts. [ 16.377783] e1000e 0000:02:00.0: Disabling ASPM L0s [ 16.505464] e1000e 0000:02:00.0: eth2: (PCI Express:2.5GB/s:Width x1) 00:1b:21:9d:52:1b [ 16.505571] e1000e 0000:02:00.0: eth2: Intel(R) PRO/1000 Network Connect= ion [ 16.505668] e1000e 0000:02:00.0: eth2: MAC: 3, PHY: 8, PBA No: E46981-00= 5 [ 85.821142] e1000e: eth2 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx [ 85.821162] e1000e 0000:02:00.0: eth2: 10/100 speed: disabling TSO And works without a problem. I see, that 8-stable has 7.1.9 version of the driver, and current has 7.2.2. Are there any patches for stable to update the driver to version 7.2.2, so I can check, if this can help? Or maybe anyone has a clue, how to make this card function in FreeBSD? Cheers, Wiktor Niesiob=C4=99dzki From owner-freebsd-stable@FreeBSD.ORG Thu Apr 28 20:51:22 2011 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 46F801065670 for ; Thu, 28 Apr 2011 20:51:22 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id EDDB98FC08 for ; Thu, 28 Apr 2011 20:51:21 +0000 (UTC) Received: by ywf7 with SMTP id 7so1575446ywf.13 for ; Thu, 28 Apr 2011 13:51:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=xKbugY31JsAbSR/OVzEir3KzrhtfeU+SA3BdW3IUIxk=; b=imYwxLVxnBBebVAjjhna7b2L5o5Lc6d8OlEuCQP4qJCfpYnIJPUMR2w+y6wuO5jfxz er9bCeHS5iDnOQUzBAbVUfYTPwETGSSvrsWkw5YWiXmmmaRyTbGAsdKltI7YaMUuc/B7 7qfKNKEUMpNn0ygcGMnwv+1IDMcoCYTbRzsCQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=rAWRx+FtyMHXShAzl1CrSXXKVofYtS/33XTCfVmv7RHBAP+WECpEAl3B2qupLa2+Eo S8WDxlXg/OLs23iE3WWLNgylLvwQHhsrKvWLXwIlTVSHXTJ3dD/p/mb7J2WxxHZp7X/o LACLhEf7m6A4lAeSDCZMYvY9fzKFp1nrXtvWk= MIME-Version: 1.0 Received: by 10.150.233.2 with SMTP id f2mr3868165ybh.97.1304023881160; Thu, 28 Apr 2011 13:51:21 -0700 (PDT) Received: by 10.150.133.13 with HTTP; Thu, 28 Apr 2011 13:51:20 -0700 (PDT) In-Reply-To: References: Date: Thu, 28 Apr 2011 13:51:20 -0700 Message-ID: From: Jack Vogel To: Wiktor Niesiobedzki Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: No data received with Intel Corporation Gigabit CT Desktop Adapter (82574L) 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, 28 Apr 2011 20:51:22 -0000 Notice this: em0: Using MSIX interrupts with 0 vectors ZERO vectors are not a good sign :) You need to look at your system, you have MSIX disabled or something? Maybe some message in /var/log/messages?? Jack On Thu, Apr 28, 2011 at 1:20 PM, Wiktor Niesiobedzki wrote: > Hi, > > I've installed Intel Gigabit CT Desktop Adapter in my FreeBSD 8.2 box > and I can't see any incoming traffic on this card. Even ARP resolution > doesn't work. Though I see the outgoing traffic on the other end. > > Relevant info: > kadlubek# uname -a > FreeBSD kadlubek 8.2-PRERELEASE FreeBSD 8.2-PRERELEASE #20: Sat Feb 12 > 21:22:19 CET 2011 root@kadlubek:/usr/obj/usr/src/sys/KADLUB i386 > > kadlubek# dmesg | grep em0 > em0: port 0xdc00-0xdc1f > mem 0xfe9e0000-0xfe9fffff,0xfe900000-0xfe97ffff,0xfe9dc000-0xfe9dffff > irq 24 at device 0.0 on pci2 > em0: Using MSIX interrupts with 0 vectors > em0: [FILTER] > > kadlubek# ping 192.168.115.1 > PING 192.168.115.1 (192.168.115.1): 56 data bytes > ping: sendto: Host is down > ping: sendto: Host is down > > In mean time - tcpdump shows: > kadlubek# tcpdump -i em0 > 22:03:55.962118 ARP, Request who-has 192.168.115.1 tell > 192.168.115.220, length 28 > 22:03:56.967107 ARP, Request who-has 192.168.115.1 tell > 192.168.115.220, length 28 > 22:03:57.972094 ARP, Request who-has 192.168.115.1 tell > 192.168.115.220, length 28 > > I've checked the firewall rules, but there are none there: > kadlubek# pfctl -s rules > No ALTQ support in kernel > ALTQ related functions disabled > > pciconf -lv shows the card as: > em0@pci0:2:0:0: class=3D0x020000 card=3D0xa01f8086 chip=3D0x10d38086 rev= =3D0x00 > hdr=3D0x00 > vendor =3D 'Intel Corporation' > device =3D 'Intel 82574L Gigabit Ethernet Controller (82574L)' > class =3D network > subclass =3D ethernet > > > kadlubek# sysctl dev.em.0 > dev.em.0.%desc: Intel(R) PRO/1000 Network Connection 7.1.9 > dev.em.0.%driver: em > dev.em.0.%location: slot=3D0 function=3D0 handle=3D\_SB_.PCI0.NBPG.NPGS > dev.em.0.%pnpinfo: vendor=3D0x8086 device=3D0x10d3 subvendor=3D0x8086 > subdevice=3D0xa01f class=3D0x020000 > dev.em.0.%parent: pci2 > dev.em.0.nvm: -1 > dev.em.0.debug: -1 > dev.em.0.rx_int_delay: 0 > dev.em.0.tx_int_delay: 66 > dev.em.0.rx_abs_int_delay: 66 > dev.em.0.tx_abs_int_delay: 66 > dev.em.0.rx_processing_limit: 100 > dev.em.0.flow_control: 3 > dev.em.0.link_irq: 0 > dev.em.0.mbuf_alloc_fail: 0 > dev.em.0.cluster_alloc_fail: 0 > dev.em.0.dropped: 0 > dev.em.0.tx_dma_fail: 0 > dev.em.0.rx_overruns: 0 > dev.em.0.watchdog_timeouts: 0 > dev.em.0.device_control: 1477444168 > dev.em.0.rx_control: 67141634 > dev.em.0.fc_high_water: 18432 > dev.em.0.fc_low_water: 16932 > dev.em.0.queue0.txd_head: 35 > dev.em.0.queue0.txd_tail: 35 > dev.em.0.queue0.tx_irq: 0 > dev.em.0.queue0.no_desc_avail: 0 > dev.em.0.queue0.rxd_head: 117 > dev.em.0.queue0.rxd_tail: 1023 > dev.em.0.queue0.rx_irq: 0 > dev.em.0.mac_stats.excess_coll: 0 > dev.em.0.mac_stats.single_coll: 0 > dev.em.0.mac_stats.multiple_coll: 0 > dev.em.0.mac_stats.late_coll: 0 > dev.em.0.mac_stats.collision_count: 0 > dev.em.0.mac_stats.symbol_errors: 0 > dev.em.0.mac_stats.sequence_errors: 0 > dev.em.0.mac_stats.defer_count: 0 > dev.em.0.mac_stats.missed_packets: 0 > dev.em.0.mac_stats.recv_no_buff: 0 > dev.em.0.mac_stats.recv_undersize: 0 > dev.em.0.mac_stats.recv_fragmented: 0 > dev.em.0.mac_stats.recv_oversize: 0 > dev.em.0.mac_stats.recv_jabber: 0 > dev.em.0.mac_stats.recv_errs: 0 > dev.em.0.mac_stats.crc_errs: 0 > dev.em.0.mac_stats.alignment_errs: 0 > dev.em.0.mac_stats.coll_ext_errs: 0 > dev.em.0.mac_stats.xon_recvd: 0 > dev.em.0.mac_stats.xon_txd: 0 > dev.em.0.mac_stats.xoff_recvd: 0 > dev.em.0.mac_stats.xoff_txd: 0 > dev.em.0.mac_stats.total_pkts_recvd: 117 > dev.em.0.mac_stats.good_pkts_recvd: 117 > dev.em.0.mac_stats.bcast_pkts_recvd: 41 > dev.em.0.mac_stats.mcast_pkts_recvd: 42 > dev.em.0.mac_stats.rx_frames_64: 71 > dev.em.0.mac_stats.rx_frames_65_127: 0 > dev.em.0.mac_stats.rx_frames_128_255: 35 > dev.em.0.mac_stats.rx_frames_256_511: 11 > dev.em.0.mac_stats.rx_frames_512_1023: 0 > dev.em.0.mac_stats.rx_frames_1024_1522: 0 > dev.em.0.mac_stats.good_octets_recvd: 15499 > dev.em.0.mac_stats.good_octets_txd: 2240 > dev.em.0.mac_stats.total_pkts_txd: 35 > dev.em.0.mac_stats.good_pkts_txd: 35 > dev.em.0.mac_stats.bcast_pkts_txd: 35 > dev.em.0.mac_stats.mcast_pkts_txd: 0 > dev.em.0.mac_stats.tx_frames_64: 35 > dev.em.0.mac_stats.tx_frames_65_127: 0 > dev.em.0.mac_stats.tx_frames_128_255: 0 > dev.em.0.mac_stats.tx_frames_256_511: 0 > dev.em.0.mac_stats.tx_frames_512_1023: 0 > dev.em.0.mac_stats.tx_frames_1024_1522: 0 > dev.em.0.mac_stats.tso_txd: 0 > dev.em.0.mac_stats.tso_ctx_fail: 0 > dev.em.0.interrupts.asserts: 2 > dev.em.0.interrupts.rx_pkt_timer: 0 > dev.em.0.interrupts.rx_abs_timer: 0 > dev.em.0.interrupts.tx_pkt_timer: 0 > dev.em.0.interrupts.tx_abs_timer: 0 > dev.em.0.interrupts.tx_queue_empty: 0 > dev.em.0.interrupts.tx_queue_min_thresh: 0 > dev.em.0.interrupts.rx_desc_min_thresh: 0 > dev.em.0.interrupts.rx_overrun: 0 > dev.em.0.wake: 0 > > kadlubek# sysctl dev.em.0.debug=3D1 > Interface is RUNNING and INACTIVE > em0: hw tdh =3D 35, hw tdt =3D 35 > em0: hw rdh =3D 118, hw rdt =3D 1023 > em0: Tx Queue Status =3D 1 > em0: TX descriptors avail =3D 989 > em0: Tx Descriptors avail failure =3D 0 > em0: RX discarded packets =3D 0 > em0: RX Next to Check =3D 0 > em0: RX Next to Refresh =3D 0 > > > I've tried booting linux on this box, and card is detected as follows: > [ 16.376557] e1000e: Intel(R) PRO/1000 Network Driver - 1.2.20-k2 > [ 16.376650] e1000e: Copyright(c) 1999 - 2011 Intel Corporation. > [ 16.376949] e1000e 0000:02:00.0: PCI INT A -> GSI 24 (level, low) -> I= RQ > 24 > [ 16.377034] e1000e 0000:02:00.0: PCI: Disallowing DAC for device > [ 16.377152] e1000e 0000:02:00.0: setting latency timer to 64 > [ 16.377387] e1000e 0000:02:00.0: (unregistered net_device): Failed > to initialize MSI-X interrupts. Falling back to MSI interrupts. > [ 16.377511] e1000e 0000:02:00.0: (unregistered net_device): Failed > to initialize MSI interrupts. Falling back to legacy interrupts. > [ 16.377783] e1000e 0000:02:00.0: Disabling ASPM L0s > [ 16.505464] e1000e 0000:02:00.0: eth2: (PCI Express:2.5GB/s:Width > x1) 00:1b:21:9d:52:1b > [ 16.505571] e1000e 0000:02:00.0: eth2: Intel(R) PRO/1000 Network > Connection > [ 16.505668] e1000e 0000:02:00.0: eth2: MAC: 3, PHY: 8, PBA No: > E46981-005 > [ 85.821142] e1000e: eth2 NIC Link is Up 100 Mbps Full Duplex, Flow > Control: Rx/Tx > [ 85.821162] e1000e 0000:02:00.0: eth2: 10/100 speed: disabling TSO > > > And works without a problem. > > I see, that 8-stable has 7.1.9 version of the driver, and current has > 7.2.2. Are there any patches for stable to update the driver to > version 7.2.2, so I can check, if this can help? Or maybe anyone has a > clue, how to make this card function in FreeBSD? > > Cheers, > > Wiktor Niesiob=C4=99dzki > _______________________________________________ > 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 Thu Apr 28 21:06:33 2011 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 94CCE106564A; Thu, 28 Apr 2011 21:06:33 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-stable.sentex.ca (freebsd-stable.sentex.ca [IPv6:2607:f3e0:0:3::6502:9b]) by mx1.freebsd.org (Postfix) with ESMTP id 53F398FC13; Thu, 28 Apr 2011 21:06:33 +0000 (UTC) Received: from freebsd-stable.sentex.ca (localhost [127.0.0.1]) by freebsd-stable.sentex.ca (8.14.4/8.14.4) with ESMTP id p3SL6WuO030073; Thu, 28 Apr 2011 21:06:32 GMT (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-stable.sentex.ca (8.14.4/8.14.4/Submit) id p3SL6W1Y030026; Thu, 28 Apr 2011 21:06:32 GMT (envelope-from tinderbox@freebsd.org) Date: Thu, 28 Apr 2011 21:06:32 GMT Message-Id: <201104282106.p3SL6W1Y030026@freebsd-stable.sentex.ca> X-Authentication-Warning: freebsd-stable.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Cc: Subject: [releng_8 tinderbox] failure on arm/arm X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Apr 2011 21:06:33 -0000 TB --- 2011-04-28 20:03:30 - tinderbox 2.6 running on freebsd-stable.sentex.ca TB --- 2011-04-28 20:03:30 - starting RELENG_8 tinderbox run for arm/arm TB --- 2011-04-28 20:03:30 - cleaning the object tree TB --- 2011-04-28 20:03:37 - cvsupping the source tree TB --- 2011-04-28 20:03:37 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_8/arm/arm/supfile TB --- 2011-04-28 20:04:20 - building world TB --- 2011-04-28 20:04:20 - MAKEOBJDIRPREFIX=/obj TB --- 2011-04-28 20:04:20 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-04-28 20:04:20 - TARGET=arm TB --- 2011-04-28 20:04:20 - TARGET_ARCH=arm TB --- 2011-04-28 20:04:20 - TZ=UTC TB --- 2011-04-28 20:04:20 - __MAKE_CONF=/dev/null TB --- 2011-04-28 20:04:20 - cd /src TB --- 2011-04-28 20:04:20 - /usr/bin/make -B buildworld >>> World build started on Thu Apr 28 20:04:21 UTC 2011 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] gzip -cn /src/usr.sbin/uhsoctl/uhsoctl.1 > uhsoctl.1.gz ===> usr.sbin/usbdump (all) cc -O -pipe -std=gnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wno-uninitialized -Wno-pointer-sign -c /src/usr.sbin/usbdump/usbdump.c cc1: warnings being treated as errors /src/usr.sbin/usbdump/usbdump.c: In function 'print_apacket': /src/usr.sbin/usbdump/usbdump.c:353: warning: cast increases required alignment of target type /src/usr.sbin/usbdump/usbdump.c: In function 'print_packets': /src/usr.sbin/usbdump/usbdump.c:399: warning: cast increases required alignment of target type *** Error code 1 Stop in /src/usr.sbin/usbdump. *** Error code 1 Stop in /src/usr.sbin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2011-04-28 21:06:31 - WARNING: /usr/bin/make returned exit code 1 TB --- 2011-04-28 21:06:31 - ERROR: failed to build world TB --- 2011-04-28 21:06:31 - 2417.55 user 410.77 system 3780.77 real http://tinderbox.freebsd.org/tinderbox-releng_8-RELENG_8-arm-arm.full From owner-freebsd-stable@FreeBSD.ORG Thu Apr 28 21:17:15 2011 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 9907A106566B for ; Thu, 28 Apr 2011 21:17:15 +0000 (UTC) (envelope-from bsd@vink.pl) Received: from mail-px0-f176.google.com (mail-px0-f176.google.com [209.85.212.176]) by mx1.freebsd.org (Postfix) with ESMTP id 70C4F8FC17 for ; Thu, 28 Apr 2011 21:17:15 +0000 (UTC) Received: by pxi11 with SMTP id 11so281882pxi.35 for ; Thu, 28 Apr 2011 14:17:14 -0700 (PDT) Received: by 10.68.8.132 with SMTP id r4mr1365546pba.326.1304025433697; Thu, 28 Apr 2011 14:17:13 -0700 (PDT) Received: from mail-px0-f176.google.com (mail-px0-f176.google.com [209.85.212.176]) by mx.google.com with ESMTPS id j2sm1438248pbo.79.2011.04.28.14.17.12 (version=SSLv3 cipher=OTHER); Thu, 28 Apr 2011 14:17:13 -0700 (PDT) Received: by pxi11 with SMTP id 11so281857pxi.35 for ; Thu, 28 Apr 2011 14:17:11 -0700 (PDT) MIME-Version: 1.0 Received: by 10.68.51.98 with SMTP id j2mr4090684pbo.288.1304025431882; Thu, 28 Apr 2011 14:17:11 -0700 (PDT) Received: by 10.68.42.40 with HTTP; Thu, 28 Apr 2011 14:17:11 -0700 (PDT) In-Reply-To: References: Date: Thu, 28 Apr 2011 23:17:11 +0200 Message-ID: From: Wiktor Niesiobedzki To: Jack Vogel Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org Subject: Re: No data received with Intel Corporation Gigabit CT Desktop Adapter (82574L) 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, 28 Apr 2011 21:17:15 -0000 Hi, I really don't know (I haven't done that intentionally). There is nothing special in /var/log/messages: kadlubek# grep -i msix /var/log/messages Apr 28 21:37:03 kadlubek kernel: em0: Using MSIX interrupts with 0 vectors Though sysctl suggests, that I haven't disabled MSIX: kadlubek# sysctl -a | grep -i msix hw.pci.enable_msix: 1 I've checked further pciconf output (now with -c option also) and there is: em0@pci0:2:0:0: class=3D0x020000 card=3D0xa01f8086 chip=3D0x10d38086 rev=3D= 0x00 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'Intel 82574L Gigabit Ethernet Controller (82574L)' class =3D network subclass =3D ethernet cap 01[c8] =3D powerspec 2 supports D0 D3 current D0 cap 05[d0] =3D MSI supports 1 message, 64 bit cap 10[e0] =3D PCI-Express 1 endpoint max data 128(256) link x1(x1) cap 11[a0] =3D MSI-X supports 5 messages in map 0x1c enabled So it looks, like the card supports MSI-X and has them enabled. Though my PCI Express bridges report as: pcib2@pci0:0:2:0: class=3D0x060400 card=3D0xc3231106 chip=3D0xa364110= 6 rev=3D0x80 hdr=3D0x01 vendor =3D 'VIA Technologies, Inc.' device =3D 'P4M900 PCI to PCI Bridge Controller' class =3D bridge subclass =3D PCI-PCI cap 10[40] =3D PCI-Express 1 root port max data 128(256) link x1(x1) cap 01[68] =3D powerspec 2 supports D0 D3 current D0 cap 05[70] =3D MSI supports 1 message, 64 bit cap 08[88] =3D HT MSI fixed address window disabled at 0xfee00000 cap 0d[98] =3D PCI Bridge card=3D0xc3231106 ecap 0001[100] =3D AER 1 0 fatal 0 non-fatal 0 corrected ecap 0002[140] =3D VC 1 max VC1 ecap 0005[180] =3D unknown 1 pcib3@pci0:0:3:0: class=3D0x060400 card=3D0xc3231106 chip=3D0xc364110= 6 rev=3D0x80 hdr=3D0x01 vendor =3D 'VIA Technologies, Inc.' device =3D 'P4M900 PCI to PCI Bridge Controller' class =3D bridge subclass =3D PCI-PCI cap 10[40] =3D PCI-Express 1 root port max data 128(256) link x1(x1) cap 01[68] =3D powerspec 2 supports D0 D3 current D0 cap 05[70] =3D MSI supports 1 message, 64 bit cap 08[88] =3D HT MSI fixed address window disabled at 0xfee00000 cap 0d[98] =3D PCI Bridge card=3D0xc3231106 ecap 0001[100] =3D AER 1 0 fatal 0 non-fatal 0 corrected ecap 0002[140] =3D VC 1 max VC1 ecap 0005[180] =3D unknown 1 pcib5@pci0:128:0:0: class=3D0x060400 card=3D0x00000000 chip=3D0x287c110= 6 rev=3D0x00 hdr=3D0x01 vendor =3D 'VIA Technologies, Inc.' device =3D 'VT8251 Standard PCIe Root Port' class =3D bridge subclass =3D PCI-PCI cap 10[40] =3D PCI-Express 1 root port max data 128(256) link x0(x2) cap 01[68] =3D powerspec 2 supports D0 D3 current D0 cap 05[70] =3D MSI supports 1 message, 64 bit, vector masks cap 08[88] =3D HT MSI fixed address window disabled at 0xfee00000 cap 0d[90] =3D PCI Bridge card=3D0x00000000 ecap 0001[100] =3D AER 1 0 fatal 0 non-fatal 0 corrected ecap 0002[140] =3D VC 1 max VC1 ecap 0005[180] =3D unknown 1 pcib6@pci0:128:0:1: class=3D0x060400 card=3D0x00000004 chip=3D0x287d110= 6 rev=3D0x00 hdr=3D0x01 vendor =3D 'VIA Technologies, Inc.' device =3D 'VT8251 Standard PCIe Root Port' class =3D bridge subclass =3D PCI-PCI cap 10[40] =3D PCI-Express 1 root port max data 128(256) link x0(x1) cap 01[68] =3D powerspec 2 supports D0 D3 current D0 cap 05[70] =3D MSI supports 1 message, 64 bit, vector masks cap 08[88] =3D HT MSI fixed address window disabled at 0xfee00000 cap 0d[90] =3D PCI Bridge card=3D0x00000004 Though they mention that HT MSI windows is disabled. I'm not sure, whether this matters. Cheers, Wiktor 2011/4/28 Jack Vogel : > Notice this:=C2=A0 em0: Using MSIX interrupts with 0 vectors > > ZERO vectors are not a good sign :) You need to look at your system, you > have MSIX > disabled or something? Maybe some message in /var/log/messages?? > > Jack > > > On Thu, Apr 28, 2011 at 1:20 PM, Wiktor Niesiobedzki wrote: >> >> Hi, >> >> I've installed Intel Gigabit CT Desktop Adapter in my FreeBSD 8.2 box >> and I can't see any incoming traffic on this card. Even ARP resolution >> doesn't work. Though I see the outgoing traffic on the other end. >> >> Relevant info: >> kadlubek# uname -a >> FreeBSD kadlubek 8.2-PRERELEASE FreeBSD 8.2-PRERELEASE #20: Sat Feb 12 >> 21:22:19 CET 2011 =C2=A0 =C2=A0 root@kadlubek:/usr/obj/usr/src/sys/KADLU= B =C2=A0i386 >> >> kadlubek# dmesg | grep em0 >> em0: port 0xdc00-0xdc1f >> mem 0xfe9e0000-0xfe9fffff,0xfe900000-0xfe97ffff,0xfe9dc000-0xfe9dffff >> irq 24 at device 0.0 on pci2 >> em0: Using MSIX interrupts with 0 vectors >> em0: [FILTER] >> >> kadlubek# ping 192.168.115.1 >> PING 192.168.115.1 (192.168.115.1): 56 data bytes >> ping: sendto: Host is down >> ping: sendto: Host is down >> >> In mean time - tcpdump shows: >> kadlubek# tcpdump -i em0 >> 22:03:55.962118 ARP, Request who-has 192.168.115.1 tell >> 192.168.115.220, length 28 >> 22:03:56.967107 ARP, Request who-has 192.168.115.1 tell >> 192.168.115.220, length 28 >> 22:03:57.972094 ARP, Request who-has 192.168.115.1 tell >> 192.168.115.220, length 28 >> >> I've checked the firewall rules, but there are none there: >> kadlubek# pfctl -s rules >> No ALTQ support in kernel >> ALTQ related functions disabled >> >> pciconf -lv shows the card as: >> em0@pci0:2:0:0: class=3D0x020000 card=3D0xa01f8086 chip=3D0x10d38086 rev= =3D0x00 >> hdr=3D0x00 >> =C2=A0 =C2=A0vendor =C2=A0 =C2=A0 =3D 'Intel Corporation' >> =C2=A0 =C2=A0device =C2=A0 =C2=A0 =3D 'Intel 82574L Gigabit Ethernet Con= troller (82574L)' >> =C2=A0 =C2=A0class =C2=A0 =C2=A0 =C2=A0=3D network >> =C2=A0 =C2=A0subclass =C2=A0 =3D ethernet >> >> >> kadlubek# sysctl dev.em.0 >> dev.em.0.%desc: Intel(R) PRO/1000 Network Connection 7.1.9 >> dev.em.0.%driver: em >> dev.em.0.%location: slot=3D0 function=3D0 handle=3D\_SB_.PCI0.NBPG.NPGS >> dev.em.0.%pnpinfo: vendor=3D0x8086 device=3D0x10d3 subvendor=3D0x8086 >> subdevice=3D0xa01f class=3D0x020000 >> dev.em.0.%parent: pci2 >> dev.em.0.nvm: -1 >> dev.em.0.debug: -1 >> dev.em.0.rx_int_delay: 0 >> dev.em.0.tx_int_delay: 66 >> dev.em.0.rx_abs_int_delay: 66 >> dev.em.0.tx_abs_int_delay: 66 >> dev.em.0.rx_processing_limit: 100 >> dev.em.0.flow_control: 3 >> dev.em.0.link_irq: 0 >> dev.em.0.mbuf_alloc_fail: 0 >> dev.em.0.cluster_alloc_fail: 0 >> dev.em.0.dropped: 0 >> dev.em.0.tx_dma_fail: 0 >> dev.em.0.rx_overruns: 0 >> dev.em.0.watchdog_timeouts: 0 >> dev.em.0.device_control: 1477444168 >> dev.em.0.rx_control: 67141634 >> dev.em.0.fc_high_water: 18432 >> dev.em.0.fc_low_water: 16932 >> dev.em.0.queue0.txd_head: 35 >> dev.em.0.queue0.txd_tail: 35 >> dev.em.0.queue0.tx_irq: 0 >> dev.em.0.queue0.no_desc_avail: 0 >> dev.em.0.queue0.rxd_head: 117 >> dev.em.0.queue0.rxd_tail: 1023 >> dev.em.0.queue0.rx_irq: 0 >> dev.em.0.mac_stats.excess_coll: 0 >> dev.em.0.mac_stats.single_coll: 0 >> dev.em.0.mac_stats.multiple_coll: 0 >> dev.em.0.mac_stats.late_coll: 0 >> dev.em.0.mac_stats.collision_count: 0 >> dev.em.0.mac_stats.symbol_errors: 0 >> dev.em.0.mac_stats.sequence_errors: 0 >> dev.em.0.mac_stats.defer_count: 0 >> dev.em.0.mac_stats.missed_packets: 0 >> dev.em.0.mac_stats.recv_no_buff: 0 >> dev.em.0.mac_stats.recv_undersize: 0 >> dev.em.0.mac_stats.recv_fragmented: 0 >> dev.em.0.mac_stats.recv_oversize: 0 >> dev.em.0.mac_stats.recv_jabber: 0 >> dev.em.0.mac_stats.recv_errs: 0 >> dev.em.0.mac_stats.crc_errs: 0 >> dev.em.0.mac_stats.alignment_errs: 0 >> dev.em.0.mac_stats.coll_ext_errs: 0 >> dev.em.0.mac_stats.xon_recvd: 0 >> dev.em.0.mac_stats.xon_txd: 0 >> dev.em.0.mac_stats.xoff_recvd: 0 >> dev.em.0.mac_stats.xoff_txd: 0 >> dev.em.0.mac_stats.total_pkts_recvd: 117 >> dev.em.0.mac_stats.good_pkts_recvd: 117 >> dev.em.0.mac_stats.bcast_pkts_recvd: 41 >> dev.em.0.mac_stats.mcast_pkts_recvd: 42 >> dev.em.0.mac_stats.rx_frames_64: 71 >> dev.em.0.mac_stats.rx_frames_65_127: 0 >> dev.em.0.mac_stats.rx_frames_128_255: 35 >> dev.em.0.mac_stats.rx_frames_256_511: 11 >> dev.em.0.mac_stats.rx_frames_512_1023: 0 >> dev.em.0.mac_stats.rx_frames_1024_1522: 0 >> dev.em.0.mac_stats.good_octets_recvd: 15499 >> dev.em.0.mac_stats.good_octets_txd: 2240 >> dev.em.0.mac_stats.total_pkts_txd: 35 >> dev.em.0.mac_stats.good_pkts_txd: 35 >> dev.em.0.mac_stats.bcast_pkts_txd: 35 >> dev.em.0.mac_stats.mcast_pkts_txd: 0 >> dev.em.0.mac_stats.tx_frames_64: 35 >> dev.em.0.mac_stats.tx_frames_65_127: 0 >> dev.em.0.mac_stats.tx_frames_128_255: 0 >> dev.em.0.mac_stats.tx_frames_256_511: 0 >> dev.em.0.mac_stats.tx_frames_512_1023: 0 >> dev.em.0.mac_stats.tx_frames_1024_1522: 0 >> dev.em.0.mac_stats.tso_txd: 0 >> dev.em.0.mac_stats.tso_ctx_fail: 0 >> dev.em.0.interrupts.asserts: 2 >> dev.em.0.interrupts.rx_pkt_timer: 0 >> dev.em.0.interrupts.rx_abs_timer: 0 >> dev.em.0.interrupts.tx_pkt_timer: 0 >> dev.em.0.interrupts.tx_abs_timer: 0 >> dev.em.0.interrupts.tx_queue_empty: 0 >> dev.em.0.interrupts.tx_queue_min_thresh: 0 >> dev.em.0.interrupts.rx_desc_min_thresh: 0 >> dev.em.0.interrupts.rx_overrun: 0 >> dev.em.0.wake: 0 >> >> kadlubek# sysctl dev.em.0.debug=3D1 >> Interface is RUNNING and INACTIVE >> em0: hw tdh =3D 35, hw tdt =3D 35 >> em0: hw rdh =3D 118, hw rdt =3D 1023 >> em0: Tx Queue Status =3D 1 >> em0: TX descriptors avail =3D 989 >> em0: Tx Descriptors avail failure =3D 0 >> em0: RX discarded packets =3D 0 >> em0: RX Next to Check =3D 0 >> em0: RX Next to Refresh =3D 0 >> >> >> I've tried booting linux on this box, and card is detected as follows: >> [ =C2=A0 16.376557] e1000e: Intel(R) PRO/1000 Network Driver - 1.2.20-k2 >> [ =C2=A0 16.376650] e1000e: Copyright(c) 1999 - 2011 Intel Corporation. >> [ =C2=A0 16.376949] e1000e 0000:02:00.0: PCI INT A -> GSI 24 (level, low= ) -> >> IRQ 24 >> [ =C2=A0 16.377034] e1000e 0000:02:00.0: PCI: Disallowing DAC for device >> [ =C2=A0 16.377152] e1000e 0000:02:00.0: setting latency timer to 64 >> [ =C2=A0 16.377387] e1000e 0000:02:00.0: (unregistered net_device): Fail= ed >> to initialize MSI-X interrupts. =C2=A0Falling back to MSI interrupts. >> [ =C2=A0 16.377511] e1000e 0000:02:00.0: (unregistered net_device): Fail= ed >> to initialize MSI interrupts. =C2=A0Falling back to legacy interrupts. >> [ =C2=A0 16.377783] e1000e 0000:02:00.0: Disabling ASPM L0s >> [ =C2=A0 16.505464] e1000e 0000:02:00.0: eth2: (PCI Express:2.5GB/s:Widt= h >> x1) 00:1b:21:9d:52:1b >> [ =C2=A0 16.505571] e1000e 0000:02:00.0: eth2: Intel(R) PRO/1000 Network >> Connection >> [ =C2=A0 16.505668] e1000e 0000:02:00.0: eth2: MAC: 3, PHY: 8, PBA No: >> E46981-005 >> [ =C2=A0 85.821142] e1000e: eth2 NIC Link is Up 100 Mbps Full Duplex, Fl= ow >> Control: Rx/Tx >> [ =C2=A0 85.821162] e1000e 0000:02:00.0: eth2: 10/100 speed: disabling T= SO >> >> >> And works without a problem. >> >> I see, that 8-stable has 7.1.9 version of the driver, and current has >> 7.2.2. Are there any patches for stable to update the driver to >> version 7.2.2, so I can check, if this can help? Or maybe anyone has a >> clue, how to make this card function in FreeBSD? >> >> Cheers, >> >> Wiktor Niesiob=C4=99dzki >> _______________________________________________ >> 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 Thu Apr 28 21:20:38 2011 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 12A78106566B for ; Thu, 28 Apr 2011 21:20:38 +0000 (UTC) (envelope-from cscotts@gmail.com) Received: from mail-qy0-f175.google.com (mail-qy0-f175.google.com [209.85.216.175]) by mx1.freebsd.org (Postfix) with ESMTP id B78F68FC1B for ; Thu, 28 Apr 2011 21:20:37 +0000 (UTC) Received: by qyk35 with SMTP id 35so2911158qyk.13 for ; Thu, 28 Apr 2011 14:20:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=DgPLQtO6BPCdqY10a88De0bDradjaxCOvlipaJj16iw=; b=RN+CVriKUuxC4Gk/tMlO1H6xbJE3QgEyJhJd+iOdF3jqxrSrko5Oh0lIoRqF9MlU10 WY2BqwE4hHX8f15wObVg968p5/ctmFMbGCatyty2DfJSNhcNMORVk+yPcxLoJYt9NYgu bLbGS58Ar2LPThxxj3AUIe7BQUfX1Yo+wz000= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=utMKhuoyr3SBBIhhJz6nmq4lUOytOciPOjNQIxtPX7lEiraKlT3QSncf/nSZZGkNhz FgKnjh/+V95mrM+GVPiCwhC6+XW+HuIoKp7snClvmiqEJwAPwP0+RpLGOZFxejyWou7f f7mA/z0V6XyPxkTUP6YFeNH1P//wuf9n/6Pro= Received: by 10.224.100.200 with SMTP id z8mr1025763qan.159.1304023987781; Thu, 28 Apr 2011 13:53:07 -0700 (PDT) Received: from sahibkuran.cap-press.com (dsl093-240-245.ral1.dsl.speakeasy.net [66.93.240.245]) by mx.google.com with ESMTPS id t17sm1554743qcs.35.2011.04.28.13.53.06 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 28 Apr 2011 13:53:06 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Scott Sipe In-Reply-To: <20110428195601.GA31807@icarus.home.lan> Date: Thu, 28 Apr 2011 16:53:03 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: References: <537A8F4F-A302-40F9-92DF-403388D99B4B@gsoft.com.au> <20110428195601.GA31807@icarus.home.lan> To: Jeremy Chadwick X-Mailer: Apple Mail (2.1084) Cc: freebsd-stable List Subject: Re: ZFS vs OSX Time Machine 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, 28 Apr 2011 21:20:38 -0000 On Apr 28, 2011, at 3:56 PM, Jeremy Chadwick wrote: > On Thu, Apr 28, 2011 at 11:33:22PM +0930, Daniel O'Connor wrote: >> Does anyone else use ZFS to store TM backups? >>=20 >> I find that whenever my laptop (over wifi!) starts a TM the ZFS = machine it's backing up to grinds to a halt.. Other systems streaming = stuff over NFS from it also tend to stall.. >>=20 >> I presume that TM is doing something which causes ZFS some issues but = I'm not sure how to find out what the real problem is let alone how to = fix it.. >>=20 >> I am running FreeBSD midget.dons.net.au 8.2-PRERELEASE FreeBSD = 8.2-PRERELEASE #8 r217094M: Sat Jan 8 11:15:07 CST 2011 = darius@midget.dons.net.au:/usr/obj/usr/src/sys/MIDGET amd64 >>=20 >> It is a 5 disk RAIDZ1 with 1.29Tb free using WD10EADS drives. >>=20 >> I don't see any SMART errors or ZFS warnings. >>=20 >> I have the following ZFS related tunables >>=20 >> vfs.zfs.arc_max=3D"3072M" >> vfs.zfs.prefetch_disable=3D"1"=20 >> vfs.zfs.txg.timeout=3D5 >> vfs.zfs.cache_flush_disable=3D1 >=20 > Are the last two actually *working* in /boot/loader.conf? Can you > verify by looking at them via sysctl? AFAIK they shouldn't work, = since > they lack double-quotes around the values. Parsing errors are = supposed > to throw you back to the loader prompt. See loader.conf(5) for the > syntax. In my /boot/loader.conf I have: vfs.zfs.arc_max=3D6200000000 vfs.zfs.vdev.min_pending=3D4 vfs.zfs.vdev.max_pending=3D8 vfs.zfs.txg.timeout=3D5 vfs.zfs.prefetch_disable=3D1 And they all are properly reflected in sysctl values (no parse errors = seen). > Next, you COULD try using Samba/CIFS on the FreeBSD box to see if you > can narrow the issue down to bad NFS performance. Please see this = post > of mine about tuning Samba on FreeBSD (backed by ZFS) to get extremely > good performance. Many people responded and said their performance > drastically improved (you can see the thread yourself). The trick is > AIO. You can ignore the part about setting vm.kmem_size in = loader.conf; > that advice is now old/deprecated (does not pertain to you given the > date of your kernel), and vfs.zfs.txg.write_limit_override is = something > you shouldn't mess with unless absolutely needed to leave it default: >=20 > = http://lists.freebsd.org/pipermail/freebsd-stable/2011-February/061642.htm= l Just wanted to note that we were having a terrible time with ZFS = performance. Copying just a single large file over the network would = bring interactive system usage to an absolute crawl (system is 2x xeons, = 12gb ram). Thanks to your optimizations we have great ZFS + Samba = performance. We also use Netatalk for afpd file sharing (though I have = not tried Netatalk as a Time Machine target) and our performance is = quite good there as well. Scott From owner-freebsd-stable@FreeBSD.ORG Thu Apr 28 21:31:14 2011 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 8062C106566B for ; Thu, 28 Apr 2011 21:31:14 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id 349FC8FC0A for ; Thu, 28 Apr 2011 21:31:13 +0000 (UTC) Received: by gxk28 with SMTP id 28so1540488gxk.13 for ; Thu, 28 Apr 2011 14:31:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=DUYIymJei5Q2Qyr6/btWQYu1wHZYafzenwPgCRphUiE=; b=V1O4wkEhqzKLhiCwkFLsUj/KJ/sa3gRkIbJHIwLfwQll58HoM7IsvMBlg2Dvk76a7d HEB2K1w+Y1CzjQHN41p4VuG0+RhHCm2IclYtX7F6skmxFBtZCtB/sWHEkeSkBzy4FyZ1 rgVd0tOKqVTU0Hk6NKa+eL9co2pA0CCVyVESY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=dPNAOD3OFxCLUzSU8nlG7B42QERWjZv3sDUdoeMoAr/iks9zpICgDWgVW/yUhp8zj6 G1uzpvtp1b4oEYhaJC3TQ5wsn9nI2zxGBKY5kH0XNI+RikUiiOXLvHiMchOWm3jf+37Z 6JQeFVszIjWP9W5ApMlt29d2ta4wYC+Z5e3mc= MIME-Version: 1.0 Received: by 10.150.59.2 with SMTP id h2mr3462892yba.439.1304026272162; Thu, 28 Apr 2011 14:31:12 -0700 (PDT) Received: by 10.150.133.13 with HTTP; Thu, 28 Apr 2011 14:31:12 -0700 (PDT) In-Reply-To: References: Date: Thu, 28 Apr 2011 14:31:12 -0700 Message-ID: From: Jack Vogel To: Wiktor Niesiobedzki Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: No data received with Intel Corporation Gigabit CT Desktop Adapter (82574L) 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, 28 Apr 2011 21:31:14 -0000 Well, rebuild your kernel so the driver is not static, then you can load an= d unload the driver to see what happens. You only have one interface, no em1? Jack On Thu, Apr 28, 2011 at 2:17 PM, Wiktor Niesiobedzki wrote: > Hi, > > I really don't know (I haven't done that intentionally). There is > nothing special in /var/log/messages: > kadlubek# grep -i msix /var/log/messages > Apr 28 21:37:03 kadlubek kernel: em0: Using MSIX interrupts with 0 vector= s > > Though sysctl suggests, that I haven't disabled MSIX: > kadlubek# sysctl -a | grep -i msix > hw.pci.enable_msix: 1 > > I've checked further pciconf output (now with -c option also) and there i= s: > em0@pci0:2:0:0: class=3D0x020000 card=3D0xa01f8086 chip=3D0x10d38086 rev= =3D0x00 > hdr=3D0x00 > vendor =3D 'Intel Corporation' > device =3D 'Intel 82574L Gigabit Ethernet Controller (82574L)' > class =3D network > subclass =3D ethernet > cap 01[c8] =3D powerspec 2 supports D0 D3 current D0 > cap 05[d0] =3D MSI supports 1 message, 64 bit > cap 10[e0] =3D PCI-Express 1 endpoint max data 128(256) link x1(x1) > cap 11[a0] =3D MSI-X supports 5 messages in map 0x1c enabled > > So it looks, like the card supports MSI-X and has them enabled. > > Though my PCI Express bridges report as: > pcib2@pci0:0:2:0: class=3D0x060400 card=3D0xc3231106 chip=3D0xa3641= 106 > rev=3D0x80 hdr=3D0x01 > vendor =3D 'VIA Technologies, Inc.' > device =3D 'P4M900 PCI to PCI Bridge Controller' > class =3D bridge > subclass =3D PCI-PCI > cap 10[40] =3D PCI-Express 1 root port max data 128(256) link x1(x1) > cap 01[68] =3D powerspec 2 supports D0 D3 current D0 > cap 05[70] =3D MSI supports 1 message, 64 bit > cap 08[88] =3D HT MSI fixed address window disabled at 0xfee00000 > cap 0d[98] =3D PCI Bridge card=3D0xc3231106 > ecap 0001[100] =3D AER 1 0 fatal 0 non-fatal 0 corrected > ecap 0002[140] =3D VC 1 max VC1 > ecap 0005[180] =3D unknown 1 > pcib3@pci0:0:3:0: class=3D0x060400 card=3D0xc3231106 chip=3D0xc3641= 106 > rev=3D0x80 hdr=3D0x01 > vendor =3D 'VIA Technologies, Inc.' > device =3D 'P4M900 PCI to PCI Bridge Controller' > class =3D bridge > subclass =3D PCI-PCI > cap 10[40] =3D PCI-Express 1 root port max data 128(256) link x1(x1) > cap 01[68] =3D powerspec 2 supports D0 D3 current D0 > cap 05[70] =3D MSI supports 1 message, 64 bit > cap 08[88] =3D HT MSI fixed address window disabled at 0xfee00000 > cap 0d[98] =3D PCI Bridge card=3D0xc3231106 > ecap 0001[100] =3D AER 1 0 fatal 0 non-fatal 0 corrected > ecap 0002[140] =3D VC 1 max VC1 > ecap 0005[180] =3D unknown 1 > > pcib5@pci0:128:0:0: class=3D0x060400 card=3D0x00000000 chip=3D0x287c1= 106 > rev=3D0x00 hdr=3D0x01 > vendor =3D 'VIA Technologies, Inc.' > device =3D 'VT8251 Standard PCIe Root Port' > class =3D bridge > subclass =3D PCI-PCI > cap 10[40] =3D PCI-Express 1 root port max data 128(256) link x0(x2) > cap 01[68] =3D powerspec 2 supports D0 D3 current D0 > cap 05[70] =3D MSI supports 1 message, 64 bit, vector masks > cap 08[88] =3D HT MSI fixed address window disabled at 0xfee00000 > cap 0d[90] =3D PCI Bridge card=3D0x00000000 > ecap 0001[100] =3D AER 1 0 fatal 0 non-fatal 0 corrected > ecap 0002[140] =3D VC 1 max VC1 > ecap 0005[180] =3D unknown 1 > pcib6@pci0:128:0:1: class=3D0x060400 card=3D0x00000004 chip=3D0x287d1= 106 > rev=3D0x00 hdr=3D0x01 > vendor =3D 'VIA Technologies, Inc.' > device =3D 'VT8251 Standard PCIe Root Port' > class =3D bridge > subclass =3D PCI-PCI > cap 10[40] =3D PCI-Express 1 root port max data 128(256) link x0(x1) > cap 01[68] =3D powerspec 2 supports D0 D3 current D0 > cap 05[70] =3D MSI supports 1 message, 64 bit, vector masks > cap 08[88] =3D HT MSI fixed address window disabled at 0xfee00000 > cap 0d[90] =3D PCI Bridge card=3D0x00000004 > > Though they mention that HT MSI windows is disabled. I'm not sure, > whether this matters. > > Cheers, > > Wiktor > > 2011/4/28 Jack Vogel : > > Notice this: em0: Using MSIX interrupts with 0 vectors > > > > ZERO vectors are not a good sign :) You need to look at your system, yo= u > > have MSIX > > disabled or something? Maybe some message in /var/log/messages?? > > > > Jack > > > > > > On Thu, Apr 28, 2011 at 1:20 PM, Wiktor Niesiobedzki > wrote: > >> > >> Hi, > >> > >> I've installed Intel Gigabit CT Desktop Adapter in my FreeBSD 8.2 box > >> and I can't see any incoming traffic on this card. Even ARP resolution > >> doesn't work. Though I see the outgoing traffic on the other end. > >> > >> Relevant info: > >> kadlubek# uname -a > >> FreeBSD kadlubek 8.2-PRERELEASE FreeBSD 8.2-PRERELEASE #20: Sat Feb 12 > >> 21:22:19 CET 2011 root@kadlubek:/usr/obj/usr/src/sys/KADLUB i386 > >> > >> kadlubek# dmesg | grep em0 > >> em0: port 0xdc00-0xdc1f > >> mem 0xfe9e0000-0xfe9fffff,0xfe900000-0xfe97ffff,0xfe9dc000-0xfe9dffff > >> irq 24 at device 0.0 on pci2 > >> em0: Using MSIX interrupts with 0 vectors > >> em0: [FILTER] > >> > >> kadlubek# ping 192.168.115.1 > >> PING 192.168.115.1 (192.168.115.1): 56 data bytes > >> ping: sendto: Host is down > >> ping: sendto: Host is down > >> > >> In mean time - tcpdump shows: > >> kadlubek# tcpdump -i em0 > >> 22:03:55.962118 ARP, Request who-has 192.168.115.1 tell > >> 192.168.115.220, length 28 > >> 22:03:56.967107 ARP, Request who-has 192.168.115.1 tell > >> 192.168.115.220, length 28 > >> 22:03:57.972094 ARP, Request who-has 192.168.115.1 tell > >> 192.168.115.220, length 28 > >> > >> I've checked the firewall rules, but there are none there: > >> kadlubek# pfctl -s rules > >> No ALTQ support in kernel > >> ALTQ related functions disabled > >> > >> pciconf -lv shows the card as: > >> em0@pci0:2:0:0: class=3D0x020000 card=3D0xa01f8086 chip=3D0x10d38086 r= ev=3D0x00 > >> hdr=3D0x00 > >> vendor =3D 'Intel Corporation' > >> device =3D 'Intel 82574L Gigabit Ethernet Controller (82574L)' > >> class =3D network > >> subclass =3D ethernet > >> > >> > >> kadlubek# sysctl dev.em.0 > >> dev.em.0.%desc: Intel(R) PRO/1000 Network Connection 7.1.9 > >> dev.em.0.%driver: em > >> dev.em.0.%location: slot=3D0 function=3D0 handle=3D\_SB_.PCI0.NBPG.NPG= S > >> dev.em.0.%pnpinfo: vendor=3D0x8086 device=3D0x10d3 subvendor=3D0x8086 > >> subdevice=3D0xa01f class=3D0x020000 > >> dev.em.0.%parent: pci2 > >> dev.em.0.nvm: -1 > >> dev.em.0.debug: -1 > >> dev.em.0.rx_int_delay: 0 > >> dev.em.0.tx_int_delay: 66 > >> dev.em.0.rx_abs_int_delay: 66 > >> dev.em.0.tx_abs_int_delay: 66 > >> dev.em.0.rx_processing_limit: 100 > >> dev.em.0.flow_control: 3 > >> dev.em.0.link_irq: 0 > >> dev.em.0.mbuf_alloc_fail: 0 > >> dev.em.0.cluster_alloc_fail: 0 > >> dev.em.0.dropped: 0 > >> dev.em.0.tx_dma_fail: 0 > >> dev.em.0.rx_overruns: 0 > >> dev.em.0.watchdog_timeouts: 0 > >> dev.em.0.device_control: 1477444168 > >> dev.em.0.rx_control: 67141634 > >> dev.em.0.fc_high_water: 18432 > >> dev.em.0.fc_low_water: 16932 > >> dev.em.0.queue0.txd_head: 35 > >> dev.em.0.queue0.txd_tail: 35 > >> dev.em.0.queue0.tx_irq: 0 > >> dev.em.0.queue0.no_desc_avail: 0 > >> dev.em.0.queue0.rxd_head: 117 > >> dev.em.0.queue0.rxd_tail: 1023 > >> dev.em.0.queue0.rx_irq: 0 > >> dev.em.0.mac_stats.excess_coll: 0 > >> dev.em.0.mac_stats.single_coll: 0 > >> dev.em.0.mac_stats.multiple_coll: 0 > >> dev.em.0.mac_stats.late_coll: 0 > >> dev.em.0.mac_stats.collision_count: 0 > >> dev.em.0.mac_stats.symbol_errors: 0 > >> dev.em.0.mac_stats.sequence_errors: 0 > >> dev.em.0.mac_stats.defer_count: 0 > >> dev.em.0.mac_stats.missed_packets: 0 > >> dev.em.0.mac_stats.recv_no_buff: 0 > >> dev.em.0.mac_stats.recv_undersize: 0 > >> dev.em.0.mac_stats.recv_fragmented: 0 > >> dev.em.0.mac_stats.recv_oversize: 0 > >> dev.em.0.mac_stats.recv_jabber: 0 > >> dev.em.0.mac_stats.recv_errs: 0 > >> dev.em.0.mac_stats.crc_errs: 0 > >> dev.em.0.mac_stats.alignment_errs: 0 > >> dev.em.0.mac_stats.coll_ext_errs: 0 > >> dev.em.0.mac_stats.xon_recvd: 0 > >> dev.em.0.mac_stats.xon_txd: 0 > >> dev.em.0.mac_stats.xoff_recvd: 0 > >> dev.em.0.mac_stats.xoff_txd: 0 > >> dev.em.0.mac_stats.total_pkts_recvd: 117 > >> dev.em.0.mac_stats.good_pkts_recvd: 117 > >> dev.em.0.mac_stats.bcast_pkts_recvd: 41 > >> dev.em.0.mac_stats.mcast_pkts_recvd: 42 > >> dev.em.0.mac_stats.rx_frames_64: 71 > >> dev.em.0.mac_stats.rx_frames_65_127: 0 > >> dev.em.0.mac_stats.rx_frames_128_255: 35 > >> dev.em.0.mac_stats.rx_frames_256_511: 11 > >> dev.em.0.mac_stats.rx_frames_512_1023: 0 > >> dev.em.0.mac_stats.rx_frames_1024_1522: 0 > >> dev.em.0.mac_stats.good_octets_recvd: 15499 > >> dev.em.0.mac_stats.good_octets_txd: 2240 > >> dev.em.0.mac_stats.total_pkts_txd: 35 > >> dev.em.0.mac_stats.good_pkts_txd: 35 > >> dev.em.0.mac_stats.bcast_pkts_txd: 35 > >> dev.em.0.mac_stats.mcast_pkts_txd: 0 > >> dev.em.0.mac_stats.tx_frames_64: 35 > >> dev.em.0.mac_stats.tx_frames_65_127: 0 > >> dev.em.0.mac_stats.tx_frames_128_255: 0 > >> dev.em.0.mac_stats.tx_frames_256_511: 0 > >> dev.em.0.mac_stats.tx_frames_512_1023: 0 > >> dev.em.0.mac_stats.tx_frames_1024_1522: 0 > >> dev.em.0.mac_stats.tso_txd: 0 > >> dev.em.0.mac_stats.tso_ctx_fail: 0 > >> dev.em.0.interrupts.asserts: 2 > >> dev.em.0.interrupts.rx_pkt_timer: 0 > >> dev.em.0.interrupts.rx_abs_timer: 0 > >> dev.em.0.interrupts.tx_pkt_timer: 0 > >> dev.em.0.interrupts.tx_abs_timer: 0 > >> dev.em.0.interrupts.tx_queue_empty: 0 > >> dev.em.0.interrupts.tx_queue_min_thresh: 0 > >> dev.em.0.interrupts.rx_desc_min_thresh: 0 > >> dev.em.0.interrupts.rx_overrun: 0 > >> dev.em.0.wake: 0 > >> > >> kadlubek# sysctl dev.em.0.debug=3D1 > >> Interface is RUNNING and INACTIVE > >> em0: hw tdh =3D 35, hw tdt =3D 35 > >> em0: hw rdh =3D 118, hw rdt =3D 1023 > >> em0: Tx Queue Status =3D 1 > >> em0: TX descriptors avail =3D 989 > >> em0: Tx Descriptors avail failure =3D 0 > >> em0: RX discarded packets =3D 0 > >> em0: RX Next to Check =3D 0 > >> em0: RX Next to Refresh =3D 0 > >> > >> > >> I've tried booting linux on this box, and card is detected as follows: > >> [ 16.376557] e1000e: Intel(R) PRO/1000 Network Driver - 1.2.20-k2 > >> [ 16.376650] e1000e: Copyright(c) 1999 - 2011 Intel Corporation. > >> [ 16.376949] e1000e 0000:02:00.0: PCI INT A -> GSI 24 (level, low) -= > > >> IRQ 24 > >> [ 16.377034] e1000e 0000:02:00.0: PCI: Disallowing DAC for device > >> [ 16.377152] e1000e 0000:02:00.0: setting latency timer to 64 > >> [ 16.377387] e1000e 0000:02:00.0: (unregistered net_device): Failed > >> to initialize MSI-X interrupts. Falling back to MSI interrupts. > >> [ 16.377511] e1000e 0000:02:00.0: (unregistered net_device): Failed > >> to initialize MSI interrupts. Falling back to legacy interrupts. > >> [ 16.377783] e1000e 0000:02:00.0: Disabling ASPM L0s > >> [ 16.505464] e1000e 0000:02:00.0: eth2: (PCI Express:2.5GB/s:Width > >> x1) 00:1b:21:9d:52:1b > >> [ 16.505571] e1000e 0000:02:00.0: eth2: Intel(R) PRO/1000 Network > >> Connection > >> [ 16.505668] e1000e 0000:02:00.0: eth2: MAC: 3, PHY: 8, PBA No: > >> E46981-005 > >> [ 85.821142] e1000e: eth2 NIC Link is Up 100 Mbps Full Duplex, Flow > >> Control: Rx/Tx > >> [ 85.821162] e1000e 0000:02:00.0: eth2: 10/100 speed: disabling TSO > >> > >> > >> And works without a problem. > >> > >> I see, that 8-stable has 7.1.9 version of the driver, and current has > >> 7.2.2. Are there any patches for stable to update the driver to > >> version 7.2.2, so I can check, if this can help? Or maybe anyone has a > >> clue, how to make this card function in FreeBSD? > >> > >> Cheers, > >> > >> Wiktor Niesiob=EAdzki > >> _______________________________________________ > >> 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 Thu Apr 28 21:31:25 2011 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 B7B4E1065778 for ; Thu, 28 Apr 2011 21:31:25 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 8B75D8FC08 for ; Thu, 28 Apr 2011 21:31:25 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 313EF46B51; Thu, 28 Apr 2011 17:31:25 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id B0ED28A027; Thu, 28 Apr 2011 17:31:24 -0400 (EDT) From: John Baldwin To: freebsd-stable@freebsd.org Date: Thu, 28 Apr 2011 17:27:04 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110325; KDE/4.5.5; amd64; ; ) References: <537A8F4F-A302-40F9-92DF-403388D99B4B@gsoft.com.au> <20110428195601.GA31807@icarus.home.lan> In-Reply-To: <20110428195601.GA31807@icarus.home.lan> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201104281727.04425.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Thu, 28 Apr 2011 17:31:24 -0400 (EDT) Cc: Jeremy Chadwick Subject: Re: ZFS vs OSX Time Machine 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, 28 Apr 2011 21:31:25 -0000 On Thursday, April 28, 2011 3:56:01 pm Jeremy Chadwick wrote: > On Thu, Apr 28, 2011 at 11:33:22PM +0930, Daniel O'Connor wrote: > > Does anyone else use ZFS to store TM backups? > > > > I find that whenever my laptop (over wifi!) starts a TM the ZFS machine it's backing up to grinds to a halt.. Other systems streaming stuff over NFS from it also tend to stall.. > > > > I presume that TM is doing something which causes ZFS some issues but I'm not sure how to find out what the real problem is let alone how to fix it.. > > > > I am running FreeBSD midget.dons.net.au 8.2-PRERELEASE FreeBSD 8.2- PRERELEASE #8 r217094M: Sat Jan 8 11:15:07 CST 2011 darius@midget.dons.net.au:/usr/obj/usr/src/sys/MIDGET amd64 > > > > It is a 5 disk RAIDZ1 with 1.29Tb free using WD10EADS drives. > > > > I don't see any SMART errors or ZFS warnings. > > > > I have the following ZFS related tunables > > > > vfs.zfs.arc_max="3072M" > > vfs.zfs.prefetch_disable="1" > > vfs.zfs.txg.timeout=5 > > vfs.zfs.cache_flush_disable=1 > > Are the last two actually *working* in /boot/loader.conf? Can you > verify by looking at them via sysctl? AFAIK they shouldn't work, since > they lack double-quotes around the values. Parsing errors are supposed > to throw you back to the loader prompt. See loader.conf(5) for the > syntax. Huh? I use values without quotes all the time in loader.conf. -- John Baldwin From owner-freebsd-stable@FreeBSD.ORG Thu Apr 28 21:31:27 2011 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 07FD510657A7 for ; Thu, 28 Apr 2011 21:31:27 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id B0D688FC0C for ; Thu, 28 Apr 2011 21:31:26 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 3D0AB46B98; Thu, 28 Apr 2011 17:31:26 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 9AB278A02A; Thu, 28 Apr 2011 17:31:25 -0400 (EDT) From: John Baldwin To: freebsd-stable@freebsd.org Date: Thu, 28 Apr 2011 17:28:37 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110325; KDE/4.5.5; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201104281728.37497.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Thu, 28 Apr 2011 17:31:25 -0400 (EDT) Cc: Wiktor Niesiobedzki , Jack Vogel Subject: Re: No data received with Intel Corporation Gigabit CT Desktop Adapter (82574L) 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, 28 Apr 2011 21:31:27 -0000 On Thursday, April 28, 2011 5:17:11 pm Wiktor Niesiobedzki wrote: > Hi, > > I really don't know (I haven't done that intentionally). There is > nothing special in /var/log/messages: > kadlubek# grep -i msix /var/log/messages > Apr 28 21:37:03 kadlubek kernel: em0: Using MSIX interrupts with 0 vectors > > Though sysctl suggests, that I haven't disabled MSIX: > kadlubek# sysctl -a | grep -i msix > hw.pci.enable_msix: 1 > > I've checked further pciconf output (now with -c option also) and there is: > em0@pci0:2:0:0: class=0x020000 card=0xa01f8086 chip=0x10d38086 rev=0x00 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Intel 82574L Gigabit Ethernet Controller (82574L)' > class = network > subclass = ethernet > cap 01[c8] = powerspec 2 supports D0 D3 current D0 > cap 05[d0] = MSI supports 1 message, 64 bit > cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1) > cap 11[a0] = MSI-X supports 5 messages in map 0x1c enabled > > So it looks, like the card supports MSI-X and has them enabled. > > Though my PCI Express bridges report as: > pcib2@pci0:0:2:0: class=0x060400 card=0xc3231106 chip=0xa3641106 > rev=0x80 hdr=0x01 > vendor = 'VIA Technologies, Inc.' > device = 'P4M900 PCI to PCI Bridge Controller' > class = bridge > subclass = PCI-PCI > cap 10[40] = PCI-Express 1 root port max data 128(256) link x1(x1) > cap 01[68] = powerspec 2 supports D0 D3 current D0 > cap 05[70] = MSI supports 1 message, 64 bit > cap 08[88] = HT MSI fixed address window disabled at 0xfee00000 > cap 0d[98] = PCI Bridge card=0xc3231106 > ecap 0001[100] = AER 1 0 fatal 0 non-fatal 0 corrected > ecap 0002[140] = VC 1 max VC1 > ecap 0005[180] = unknown 1 > pcib3@pci0:0:3:0: class=0x060400 card=0xc3231106 chip=0xc3641106 > rev=0x80 hdr=0x01 > vendor = 'VIA Technologies, Inc.' > device = 'P4M900 PCI to PCI Bridge Controller' > class = bridge > subclass = PCI-PCI > cap 10[40] = PCI-Express 1 root port max data 128(256) link x1(x1) > cap 01[68] = powerspec 2 supports D0 D3 current D0 > cap 05[70] = MSI supports 1 message, 64 bit > cap 08[88] = HT MSI fixed address window disabled at 0xfee00000 > cap 0d[98] = PCI Bridge card=0xc3231106 > ecap 0001[100] = AER 1 0 fatal 0 non-fatal 0 corrected > ecap 0002[140] = VC 1 max VC1 > ecap 0005[180] = unknown 1 > > pcib5@pci0:128:0:0: class=0x060400 card=0x00000000 chip=0x287c1106 > rev=0x00 hdr=0x01 > vendor = 'VIA Technologies, Inc.' > device = 'VT8251 Standard PCIe Root Port' > class = bridge > subclass = PCI-PCI > cap 10[40] = PCI-Express 1 root port max data 128(256) link x0(x2) > cap 01[68] = powerspec 2 supports D0 D3 current D0 > cap 05[70] = MSI supports 1 message, 64 bit, vector masks > cap 08[88] = HT MSI fixed address window disabled at 0xfee00000 > cap 0d[90] = PCI Bridge card=0x00000000 > ecap 0001[100] = AER 1 0 fatal 0 non-fatal 0 corrected > ecap 0002[140] = VC 1 max VC1 > ecap 0005[180] = unknown 1 > pcib6@pci0:128:0:1: class=0x060400 card=0x00000004 chip=0x287d1106 > rev=0x00 hdr=0x01 > vendor = 'VIA Technologies, Inc.' > device = 'VT8251 Standard PCIe Root Port' > class = bridge > subclass = PCI-PCI > cap 10[40] = PCI-Express 1 root port max data 128(256) link x0(x1) > cap 01[68] = powerspec 2 supports D0 D3 current D0 > cap 05[70] = MSI supports 1 message, 64 bit, vector masks > cap 08[88] = HT MSI fixed address window disabled at 0xfee00000 > cap 0d[90] = PCI Bridge card=0x00000004 > > Though they mention that HT MSI windows is disabled. I'm not sure, > whether this matters. Yes, that is probably what breaks this. -- John Baldwin From owner-freebsd-stable@FreeBSD.ORG Thu Apr 28 21:42:16 2011 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 4DA481065674 for ; Thu, 28 Apr 2011 21:42:16 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 066928FC0C for ; Thu, 28 Apr 2011 21:42:15 +0000 (UTC) Received: by gwb15 with SMTP id 15so1595745gwb.13 for ; Thu, 28 Apr 2011 14:42:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=isDwZY+fY7aXAt61PHKPg2fIIYbpiXvD72/4BPMqlXU=; b=Wun6FvL6Ptg4KFKrfZ6hM4/HGSXNSgzfcNJlOXlNzrmngx8iG+Z7vLImvKCTZVUrP6 kpziqknUCULMmE84KdnGLOs+osZB2+TXBp+pILm1G3DqB0wpUy2phhJnfm4LrybPoT2J DsbSlZKnJKSxYJNiQxZyY0cmOQsM4R+KDnMcM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=juj5iWsrNpQCsntU89X5s/M7M2t+ktP1hn3jrDhUBzUTuDt7p9JrHpneu9Fb/PIaUk 88eGpcBf5v3S03P5xCK9fjz8nZ5C8+mARDLL6afM/aiqucjEh9kvBzMGYWNFvS17VXau mf/qd739iArM1+B23WbTdO5HAnJiJwipxrs9E= MIME-Version: 1.0 Received: by 10.150.166.17 with SMTP id o17mr3582363ybe.40.1304026934989; Thu, 28 Apr 2011 14:42:14 -0700 (PDT) Received: by 10.150.133.13 with HTTP; Thu, 28 Apr 2011 14:42:14 -0700 (PDT) In-Reply-To: <201104281728.37497.jhb@freebsd.org> References: <201104281728.37497.jhb@freebsd.org> Date: Thu, 28 Apr 2011 14:42:14 -0700 Message-ID: From: Jack Vogel To: John Baldwin Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Wiktor Niesiobedzki , freebsd-stable@freebsd.org Subject: Re: No data received with Intel Corporation Gigabit CT Desktop Adapter (82574L) 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, 28 Apr 2011 21:42:16 -0000 On Thu, Apr 28, 2011 at 2:28 PM, John Baldwin wrote: > On Thursday, April 28, 2011 5:17:11 pm Wiktor Niesiobedzki wrote: > > Hi, > > > > I really don't know (I haven't done that intentionally). There is > > nothing special in /var/log/messages: > > kadlubek# grep -i msix /var/log/messages > > Apr 28 21:37:03 kadlubek kernel: em0: Using MSIX interrupts with 0 > vectors > > > > Though sysctl suggests, that I haven't disabled MSIX: > > kadlubek# sysctl -a | grep -i msix > > hw.pci.enable_msix: 1 > > > > I've checked further pciconf output (now with -c option also) and there > is: > > em0@pci0:2:0:0: class=0x020000 card=0xa01f8086 chip=0x10d38086 rev=0x00 > hdr=0x00 > > vendor = 'Intel Corporation' > > device = 'Intel 82574L Gigabit Ethernet Controller (82574L)' > > class = network > > subclass = ethernet > > cap 01[c8] = powerspec 2 supports D0 D3 current D0 > > cap 05[d0] = MSI supports 1 message, 64 bit > > cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1) > > cap 11[a0] = MSI-X supports 5 messages in map 0x1c enabled > > > > So it looks, like the card supports MSI-X and has them enabled. > > > > Though my PCI Express bridges report as: > > pcib2@pci0:0:2:0: class=0x060400 card=0xc3231106 chip=0xa3641106 > > rev=0x80 hdr=0x01 > > vendor = 'VIA Technologies, Inc.' > > device = 'P4M900 PCI to PCI Bridge Controller' > > class = bridge > > subclass = PCI-PCI > > cap 10[40] = PCI-Express 1 root port max data 128(256) link x1(x1) > > cap 01[68] = powerspec 2 supports D0 D3 current D0 > > cap 05[70] = MSI supports 1 message, 64 bit > > cap 08[88] = HT MSI fixed address window disabled at 0xfee00000 > > cap 0d[98] = PCI Bridge card=0xc3231106 > > ecap 0001[100] = AER 1 0 fatal 0 non-fatal 0 corrected > > ecap 0002[140] = VC 1 max VC1 > > ecap 0005[180] = unknown 1 > > pcib3@pci0:0:3:0: class=0x060400 card=0xc3231106 chip=0xc3641106 > > rev=0x80 hdr=0x01 > > vendor = 'VIA Technologies, Inc.' > > device = 'P4M900 PCI to PCI Bridge Controller' > > class = bridge > > subclass = PCI-PCI > > cap 10[40] = PCI-Express 1 root port max data 128(256) link x1(x1) > > cap 01[68] = powerspec 2 supports D0 D3 current D0 > > cap 05[70] = MSI supports 1 message, 64 bit > > cap 08[88] = HT MSI fixed address window disabled at 0xfee00000 > > cap 0d[98] = PCI Bridge card=0xc3231106 > > ecap 0001[100] = AER 1 0 fatal 0 non-fatal 0 corrected > > ecap 0002[140] = VC 1 max VC1 > > ecap 0005[180] = unknown 1 > > > > pcib5@pci0:128:0:0: class=0x060400 card=0x00000000 chip=0x287c1106 > > rev=0x00 hdr=0x01 > > vendor = 'VIA Technologies, Inc.' > > device = 'VT8251 Standard PCIe Root Port' > > class = bridge > > subclass = PCI-PCI > > cap 10[40] = PCI-Express 1 root port max data 128(256) link x0(x2) > > cap 01[68] = powerspec 2 supports D0 D3 current D0 > > cap 05[70] = MSI supports 1 message, 64 bit, vector masks > > cap 08[88] = HT MSI fixed address window disabled at 0xfee00000 > > cap 0d[90] = PCI Bridge card=0x00000000 > > ecap 0001[100] = AER 1 0 fatal 0 non-fatal 0 corrected > > ecap 0002[140] = VC 1 max VC1 > > ecap 0005[180] = unknown 1 > > pcib6@pci0:128:0:1: class=0x060400 card=0x00000004 chip=0x287d1106 > > rev=0x00 hdr=0x01 > > vendor = 'VIA Technologies, Inc.' > > device = 'VT8251 Standard PCIe Root Port' > > class = bridge > > subclass = PCI-PCI > > cap 10[40] = PCI-Express 1 root port max data 128(256) link x0(x1) > > cap 01[68] = powerspec 2 supports D0 D3 current D0 > > cap 05[70] = MSI supports 1 message, 64 bit, vector masks > > cap 08[88] = HT MSI fixed address window disabled at 0xfee00000 > > cap 0d[90] = PCI Bridge card=0x00000004 > > > > Though they mention that HT MSI windows is disabled. I'm not sure, > > whether this matters. > > Yes, that is probably what breaks this. > > -- > John Baldwin > Opps, missed that, thanks John. So, disable MSIX and MSI using sysctl, then the driver should use legacy when it loads. Still, I'd get a different motherboard, sucks to not have MSIX :( Jack From owner-freebsd-stable@FreeBSD.ORG Thu Apr 28 21:59:57 2011 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 342631065673 for ; Thu, 28 Apr 2011 21:59:57 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta11.emeryville.ca.mail.comcast.net (qmta11.emeryville.ca.mail.comcast.net [76.96.27.211]) by mx1.freebsd.org (Postfix) with ESMTP id 1B7008FC1D for ; Thu, 28 Apr 2011 21:59:56 +0000 (UTC) Received: from omta22.emeryville.ca.mail.comcast.net ([76.96.30.89]) by qmta11.emeryville.ca.mail.comcast.net with comcast id d8fv1g0031vN32cAB9zwnQ; Thu, 28 Apr 2011 21:59:56 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta22.emeryville.ca.mail.comcast.net with comcast id d9zu1g01D1t3BNj8i9zuGR; Thu, 28 Apr 2011 21:59:55 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 2B0439B418; Thu, 28 Apr 2011 14:59:54 -0700 (PDT) Date: Thu, 28 Apr 2011 14:59:54 -0700 From: Jeremy Chadwick To: John Baldwin Message-ID: <20110428215954.GA34030@icarus.home.lan> References: <537A8F4F-A302-40F9-92DF-403388D99B4B@gsoft.com.au> <20110428195601.GA31807@icarus.home.lan> <201104281727.04425.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201104281727.04425.jhb@freebsd.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@freebsd.org Subject: Re: ZFS vs OSX Time Machine 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, 28 Apr 2011 21:59:57 -0000 On Thu, Apr 28, 2011 at 05:27:04PM -0400, John Baldwin wrote: > On Thursday, April 28, 2011 3:56:01 pm Jeremy Chadwick wrote: > > On Thu, Apr 28, 2011 at 11:33:22PM +0930, Daniel O'Connor wrote: > > > Does anyone else use ZFS to store TM backups? > > > > > > I find that whenever my laptop (over wifi!) starts a TM the ZFS machine > it's backing up to grinds to a halt.. Other systems streaming stuff over NFS > from it also tend to stall.. > > > > > > I presume that TM is doing something which causes ZFS some issues but I'm > not sure how to find out what the real problem is let alone how to fix it.. > > > > > > I am running FreeBSD midget.dons.net.au 8.2-PRERELEASE FreeBSD 8.2- > PRERELEASE #8 r217094M: Sat Jan 8 11:15:07 CST 2011 > darius@midget.dons.net.au:/usr/obj/usr/src/sys/MIDGET amd64 > > > > > > It is a 5 disk RAIDZ1 with 1.29Tb free using WD10EADS drives. > > > > > > I don't see any SMART errors or ZFS warnings. > > > > > > I have the following ZFS related tunables > > > > > > vfs.zfs.arc_max="3072M" > > > vfs.zfs.prefetch_disable="1" > > > vfs.zfs.txg.timeout=5 > > > vfs.zfs.cache_flush_disable=1 > > > > Are the last two actually *working* in /boot/loader.conf? Can you > > verify by looking at them via sysctl? AFAIK they shouldn't work, since > > they lack double-quotes around the values. Parsing errors are supposed > > to throw you back to the loader prompt. See loader.conf(5) for the > > syntax. > > Huh? I use values without quotes all the time in loader.conf. I've seen cases where entries in /boot/loader.conf throw parser errors during loader(8) when quotes aren't used. The man page denotes that quotes are required, which doesn't appear to be true? Possibly the parser only throws errors if non-numeric/non-integer values (e.g. strings) are specified without quotes. It's interesting that in the BUGS section of the man page the syntax shown for hw.ata.ata_dma=0 also ""violates"" the ""required"" syntax. So the question is: what's reality, and would better documentation suffice? -- | Jeremy Chadwick jdc@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 Apr 28 22:27:04 2011 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 3CAC81065672 for ; Thu, 28 Apr 2011 22:27:04 +0000 (UTC) (envelope-from bsd@vink.pl) Received: from mail-pv0-f182.google.com (mail-pv0-f182.google.com [74.125.83.182]) by mx1.freebsd.org (Postfix) with ESMTP id 1402B8FC1F for ; Thu, 28 Apr 2011 22:27:03 +0000 (UTC) Received: by pvg11 with SMTP id 11so2689155pvg.13 for ; Thu, 28 Apr 2011 15:27:03 -0700 (PDT) Received: by 10.68.31.169 with SMTP id b9mr4392395pbi.207.1304029623588; Thu, 28 Apr 2011 15:27:03 -0700 (PDT) Received: from mail-pw0-f54.google.com (mail-pw0-f54.google.com [209.85.160.54]) by mx.google.com with ESMTPS id o20sm1474027pbt.50.2011.04.28.15.27.02 (version=SSLv3 cipher=OTHER); Thu, 28 Apr 2011 15:27:03 -0700 (PDT) Received: by pwj8 with SMTP id 8so1987459pwj.13 for ; Thu, 28 Apr 2011 15:27:02 -0700 (PDT) MIME-Version: 1.0 Received: by 10.68.15.36 with SMTP id u4mr4390290pbc.20.1304029622494; Thu, 28 Apr 2011 15:27:02 -0700 (PDT) Received: by 10.68.42.40 with HTTP; Thu, 28 Apr 2011 15:27:02 -0700 (PDT) In-Reply-To: References: <201104281728.37497.jhb@freebsd.org> Date: Fri, 29 Apr 2011 00:27:02 +0200 Message-ID: From: Wiktor Niesiobedzki To: Jack Vogel Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org, John Baldwin Subject: Re: No data received with Intel Corporation Gigabit CT Desktop Adapter (82574L) 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, 28 Apr 2011 22:27:04 -0000 2011/4/28 Jack Vogel : > On Thu, Apr 28, 2011 at 2:28 PM, John Baldwin wrote: >> >> On Thursday, April 28, 2011 5:17:11 pm Wiktor Niesiobedzki wrote: >> > Though they mention that HT MSI windows is disabled. I'm not sure, >> > whether this matters. >> >> Yes, that is probably what breaks this. >> >> -- >> John Baldwin > > Opps, missed that, thanks John.=C2=A0 So, disable MSIX and MSI using sysc= tl, > then the driver should use legacy when it loads. > > Still, I'd get a different motherboard, sucks to not have MSIX :( > Thanks for hints. I've disabled MSIX and MSI: kadlubek# sysctl hw.pci | grep msi hw.pci.honor_msi_blacklist: 1 hw.pci.enable_msix: 0 hw.pci.enable_msi: 0 and reloaded if_em module. During initialization it confirmed, that will not use MSI(X): em0: port 0xdc00-0xdc1f mem 0xfe9e0000-0xfe9fffff,0xfe900000-0xfe97ffff,0xfe9dc000-0xfe9dffff irq 24 at device 0.0 on pci2 em0: MSIX: insufficient vectors, using MSI em0: No MSI/MSIX using a Legacy IRQ em0: [FILTER] em0: Ethernet address: 00:1b:21:9d:52:1b em0: link state changed to UP Though behavior hasn't change - I still see outgoing packets, and no incoming traffic. As far as I see, linux driver does that automagically, when no MSI(-X) is available, then it fallbacks to IRQ: [ 16.377387] e1000e 0000:02:00.0: (unregistered net_device): Failed to initialize MSI-X interrupts. Falling back to MSI interrupts. [ 16.377511] e1000e 0000:02:00.0: (unregistered net_device): Failed to initialize MSI interrupts. Falling back to legacy interrupts. Does anything come to your mind, that I can do, to debug, why this card is not working? Cheers, Wiktor From owner-freebsd-stable@FreeBSD.ORG Thu Apr 28 22:35:32 2011 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 597F21065672 for ; Thu, 28 Apr 2011 22:35:32 +0000 (UTC) (envelope-from frimik@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 1345A8FC0C for ; Thu, 28 Apr 2011 22:35:31 +0000 (UTC) Received: by vws18 with SMTP id 18so3160351vws.13 for ; Thu, 28 Apr 2011 15:35:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=Qpd29VjsyFnqG6YPXo8xwdTUKyxiRcqJaYNGMRthOoo=; b=Zh1BY9P5LkbuM4NRV139e8TugtujlsINtwLKVDmC6IqIHoBXEBAqoMTqHIyUpGW02O 63BIbZD0N23UV78pBUlF951oBSMCanJyJejN0kspDcNgLjEt4WB7xyB39EA8BtAgLiQ3 /RrZ3XbM1rRk13eFdDQkXxQbloiZHzfEILOzw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=C7YTyd+xZcPy4t9DXoub+gcHEx8MV3Y2rxWyGweG6fn6RLzMsMBZUcOlF53/mZCVgd 3sfKneop4TEN+TKb86kbPvH6YyPiG3mWojKK1m1aR+brpQj6YYF5ZDlOIoRwrZmcVvFq cNpVFbqjHQd9kFBjzZKVUfbPKiJuB/R3e5ZVY= MIME-Version: 1.0 Received: by 10.52.115.232 with SMTP id jr8mr1859179vdb.38.1304030131389; Thu, 28 Apr 2011 15:35:31 -0700 (PDT) Received: by 10.52.116.8 with HTTP; Thu, 28 Apr 2011 15:35:31 -0700 (PDT) In-Reply-To: <20110428215954.GA34030@icarus.home.lan> References: <537A8F4F-A302-40F9-92DF-403388D99B4B@gsoft.com.au> <20110428195601.GA31807@icarus.home.lan> <201104281727.04425.jhb@freebsd.org> <20110428215954.GA34030@icarus.home.lan> Date: Fri, 29 Apr 2011 00:35:31 +0200 Message-ID: From: Mikael Fridh To: Jeremy Chadwick Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org, John Baldwin Subject: Re: ZFS vs OSX Time Machine 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, 28 Apr 2011 22:35:32 -0000 On Thu, Apr 28, 2011 at 11:59 PM, Jeremy Chadwick wrote: > > I've seen cases where entries in /boot/loader.conf throw parser errors > during loader(8) when quotes aren't used. =A0The man page denotes that > quotes are required, which doesn't appear to be true? =A0Possibly the > parser only throws errors if non-numeric/non-integer values (e.g. > strings) are specified without quotes. > > It's interesting that in the BUGS section of the man page the syntax > shown for hw.ata.ata_dma=3D0 also ""violates"" the ""required"" syntax. > > So the question is: what's reality, and would better documentation > suffice? My reality: zfs_load=3D"YES" vfs.root.mountfrom=3D"zfs:zroot" vfs.root.mountfrom.options=3Drw vfs.zfs.debug=3D1 geom_mirror_load=3D"YES" ahci_load=3D"YES" ... works. And I've used even more sloppy syntax on occasion, basically I've left out quotes on pretty much all values which are pure alphanumeric. loader.conf(5) does say: > All settings have the following format: > variable=3D"value" but it also says it's format was defined explicitly to resemble rc.conf(5) and can be sourced by sh(1), which should mean that quoting is not required anywhere. If you read that literally, you should even be able to do this in loader.co= nf: some_value=3DVALUE\ WITH\ SPACES ... because that can be sourced by sh(1) and would result in some_value=3D'VALUE WITH SPACES', but I haven't tried rebooting a machine with such settings in loader.conf yet and I wouldn't bet on it working nor would I actually use such madness in loader.conf even if I could. -- Mikael From owner-freebsd-stable@FreeBSD.ORG Thu Apr 28 23:04:29 2011 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 481C2106564A; Thu, 28 Apr 2011 23:04:29 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-stable.sentex.ca (freebsd-stable.sentex.ca [IPv6:2607:f3e0:0:3::6502:9b]) by mx1.freebsd.org (Postfix) with ESMTP id 08C9E8FC0A; Thu, 28 Apr 2011 23:04:28 +0000 (UTC) Received: from freebsd-stable.sentex.ca (localhost [127.0.0.1]) by freebsd-stable.sentex.ca (8.14.4/8.14.4) with ESMTP id p3SN4SAo008889; Thu, 28 Apr 2011 23:04:28 GMT (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-stable.sentex.ca (8.14.4/8.14.4/Submit) id p3SN4S51008878; Thu, 28 Apr 2011 23:04:28 GMT (envelope-from tinderbox@freebsd.org) Date: Thu, 28 Apr 2011 23:04:28 GMT Message-Id: <201104282304.p3SN4S51008878@freebsd-stable.sentex.ca> X-Authentication-Warning: freebsd-stable.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Cc: Subject: [releng_8 tinderbox] failure on ia64/ia64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Apr 2011 23:04:29 -0000 TB --- 2011-04-28 21:26:53 - tinderbox 2.6 running on freebsd-stable.sentex.ca TB --- 2011-04-28 21:26:53 - starting RELENG_8 tinderbox run for ia64/ia64 TB --- 2011-04-28 21:26:53 - cleaning the object tree TB --- 2011-04-28 21:27:10 - cvsupping the source tree TB --- 2011-04-28 21:27:10 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_8/ia64/ia64/supfile TB --- 2011-04-28 21:27:42 - building world TB --- 2011-04-28 21:27:42 - MAKEOBJDIRPREFIX=/obj TB --- 2011-04-28 21:27:42 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-04-28 21:27:42 - TARGET=ia64 TB --- 2011-04-28 21:27:42 - TARGET_ARCH=ia64 TB --- 2011-04-28 21:27:42 - TZ=UTC TB --- 2011-04-28 21:27:42 - __MAKE_CONF=/dev/null TB --- 2011-04-28 21:27:42 - cd /src TB --- 2011-04-28 21:27:42 - /usr/bin/make -B buildworld >>> World build started on Thu Apr 28 21:27:43 UTC 2011 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] gzip -cn /src/usr.sbin/uhsoctl/uhsoctl.1 > uhsoctl.1.gz ===> usr.sbin/usbdump (all) cc -O2 -pipe -std=gnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wno-uninitialized -Wno-pointer-sign -c /src/usr.sbin/usbdump/usbdump.c cc1: warnings being treated as errors /src/usr.sbin/usbdump/usbdump.c: In function 'print_apacket': /src/usr.sbin/usbdump/usbdump.c:353: warning: cast increases required alignment of target type /src/usr.sbin/usbdump/usbdump.c: In function 'print_packets': /src/usr.sbin/usbdump/usbdump.c:399: warning: cast increases required alignment of target type *** Error code 1 Stop in /src/usr.sbin/usbdump. *** Error code 1 Stop in /src/usr.sbin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2011-04-28 23:04:28 - WARNING: /usr/bin/make returned exit code 1 TB --- 2011-04-28 23:04:28 - ERROR: failed to build world TB --- 2011-04-28 23:04:28 - 4070.73 user 440.80 system 5854.84 real http://tinderbox.freebsd.org/tinderbox-releng_8-RELENG_8-ia64-ia64.full From owner-freebsd-stable@FreeBSD.ORG Thu Apr 28 23:29:53 2011 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 9CDAD106564A; Thu, 28 Apr 2011 23:29:53 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-stable.sentex.ca (freebsd-stable.sentex.ca [IPv6:2607:f3e0:0:3::6502:9b]) by mx1.freebsd.org (Postfix) with ESMTP id 442318FC16; Thu, 28 Apr 2011 23:29:53 +0000 (UTC) Received: from freebsd-stable.sentex.ca (localhost [127.0.0.1]) by freebsd-stable.sentex.ca (8.14.4/8.14.4) with ESMTP id p3SNTqXi041724; Thu, 28 Apr 2011 23:29:52 GMT (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-stable.sentex.ca (8.14.4/8.14.4/Submit) id p3SNTq9W041707; Thu, 28 Apr 2011 23:29:52 GMT (envelope-from tinderbox@freebsd.org) Date: Thu, 28 Apr 2011 23:29:52 GMT Message-Id: <201104282329.p3SNTq9W041707@freebsd-stable.sentex.ca> X-Authentication-Warning: freebsd-stable.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Cc: Subject: [releng_8 tinderbox] failure on mips/mips X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Apr 2011 23:29:53 -0000 TB --- 2011-04-28 22:26:40 - tinderbox 2.6 running on freebsd-stable.sentex.ca TB --- 2011-04-28 22:26:40 - starting RELENG_8 tinderbox run for mips/mips TB --- 2011-04-28 22:26:40 - cleaning the object tree TB --- 2011-04-28 22:26:51 - cvsupping the source tree TB --- 2011-04-28 22:26:51 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_8/mips/mips/supfile TB --- 2011-04-28 22:27:25 - building world TB --- 2011-04-28 22:27:25 - MAKEOBJDIRPREFIX=/obj TB --- 2011-04-28 22:27:25 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-04-28 22:27:25 - TARGET=mips TB --- 2011-04-28 22:27:25 - TARGET_ARCH=mips TB --- 2011-04-28 22:27:25 - TZ=UTC TB --- 2011-04-28 22:27:25 - __MAKE_CONF=/dev/null TB --- 2011-04-28 22:27:25 - cd /src TB --- 2011-04-28 22:27:25 - /usr/bin/make -B buildworld >>> World build started on Thu Apr 28 22:27:26 UTC 2011 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] gzip -cn /src/usr.sbin/uhsoctl/uhsoctl.1 > uhsoctl.1.gz ===> usr.sbin/usbdump (all) cc -O -pipe -EL -msoft-float -G0 -mno-dsp -mabicalls -std=gnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wno-uninitialized -Wno-pointer-sign -c /src/usr.sbin/usbdump/usbdump.c cc1: warnings being treated as errors /src/usr.sbin/usbdump/usbdump.c: In function 'print_apacket': /src/usr.sbin/usbdump/usbdump.c:353: warning: cast increases required alignment of target type /src/usr.sbin/usbdump/usbdump.c: In function 'print_packets': /src/usr.sbin/usbdump/usbdump.c:399: warning: cast increases required alignment of target type *** Error code 1 Stop in /src/usr.sbin/usbdump. *** Error code 1 Stop in /src/usr.sbin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2011-04-28 23:29:52 - WARNING: /usr/bin/make returned exit code 1 TB --- 2011-04-28 23:29:52 - ERROR: failed to build world TB --- 2011-04-28 23:29:52 - 2348.38 user 376.27 system 3791.79 real http://tinderbox.freebsd.org/tinderbox-releng_8-RELENG_8-mips-mips.full From owner-freebsd-stable@FreeBSD.ORG Thu Apr 28 23:43:49 2011 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 B3C38106564A for ; Thu, 28 Apr 2011 23:43:49 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta14.westchester.pa.mail.comcast.net (qmta14.westchester.pa.mail.comcast.net [76.96.59.212]) by mx1.freebsd.org (Postfix) with ESMTP id 632538FC13 for ; Thu, 28 Apr 2011 23:43:49 +0000 (UTC) Received: from omta15.westchester.pa.mail.comcast.net ([76.96.62.87]) by qmta14.westchester.pa.mail.comcast.net with comcast id d9oy1g0071swQuc5EBWaCT; Thu, 28 Apr 2011 23:30:34 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta15.westchester.pa.mail.comcast.net with comcast id dBWY1g00x1t3BNj3bBWZUi; Thu, 28 Apr 2011 23:30:34 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 086CA9B418; Thu, 28 Apr 2011 16:30:31 -0700 (PDT) Date: Thu, 28 Apr 2011 16:30:31 -0700 From: Jeremy Chadwick To: FreeBSD Tinderbox Message-ID: <20110428233030.GA35428@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201104282106.p3SL6W1Y030026@freebsd-stable.sentex.ca> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: arm@freebsd.org, stable@freebsd.org, hselasky@freebsd.org Subject: Re: [releng_8 tinderbox] failure on arm/arm 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, 28 Apr 2011 23:43:49 -0000 On Thu, Apr 28, 2011 at 09:06:32PM +0000, FreeBSD Tinderbox wrote: > ===> usr.sbin/usbdump (all) > cc -O -pipe -std=gnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wno-uninitialized -Wno-pointer-sign -c /src/usr.sbin/usbdump/usbdump.c > cc1: warnings being treated as errors > /src/usr.sbin/usbdump/usbdump.c: In function 'print_apacket': > /src/usr.sbin/usbdump/usbdump.c:353: warning: cast increases required alignment of target type > /src/usr.sbin/usbdump/usbdump.c: In function 'print_packets': > /src/usr.sbin/usbdump/usbdump.c:399: warning: cast increases required alignment of target type > *** Error code 1 > > Stop in /src/usr.sbin/usbdump. > *** Error code 1 CC'ing hselasky and thompsa for review of this. For failure logs (so far ia64 and arm), please see end of this page: http://lists.freebsd.org/pipermail/freebsd-stable/2011-April/thread.html Commit question is revision 1.6.2.2 to RELENG_8: http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/usbdump/usbdump.c Relevant code bits: 290: static void 291: print_apacket(const struct bpf_xhdr *hdr, const uint8_t *ptr, int ptr_len) 292: { ... 349: const struct usbpf_framehdr *uf; ... 353: uf = (const struct usbpf_framehdr *)ptr; -- | Jeremy Chadwick jdc@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 Apr 29 00:02:51 2011 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 B27ED106564A for ; Fri, 29 Apr 2011 00:02:51 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (unknown [IPv6:2001:44b8:7c07:5581:266:e1ff:fe0c:8f16]) by mx1.freebsd.org (Postfix) with ESMTP id 6260B8FC0C for ; Fri, 29 Apr 2011 00:02:49 +0000 (UTC) Received: from ur.dons.net.au (ppp208-191.lns1.adl2.internode.on.net [203.122.208.191] (may be forged)) (authenticated bits=0) by cain.gsoft.com.au (8.14.4/8.14.3) with ESMTP id p3T02g9R095811 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 29 Apr 2011 09:32:42 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: "Daniel O'Connor" In-Reply-To: Date: Fri, 29 Apr 2011 09:32:41 +0930 Content-Transfer-Encoding: quoted-printable Message-Id: References: <537A8F4F-A302-40F9-92DF-403388D99B4B@gsoft.com.au> To: Malcolm Waltz X-Mailer: Apple Mail (2.1084) X-Spam-Score: -0.272 () BAYES_00,RDNS_NONE X-Scanned-By: MIMEDefang 2.67 on 203.31.81.10 Cc: freebsd-stable List Subject: Re: ZFS vs OSX Time Machine 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, 29 Apr 2011 00:02:51 -0000 On 29/04/2011, at 2:16, Malcolm Waltz wrote: > I doubt the issues you are encountering have much to do with ZFS. >=20 > It sounds like you are using TimeMachine over NFS. Obviously, Apple = does not support that configuration: > http://www.google.com/search?q=3Dtime+machine+nfs+site:apple.com >=20 > In my opinion, TimeMachine should only be used with block storage. If = you use any kind of file-sharing protocol (AFP, SMB/CIFS or NFS), = TimeMachine is implemented using a sparse disk image broken into = hundreds or thousands of separate files. This is a hack at best. >=20 > Time machine works very well with locally attached storage, but if you = need to use network storage, you might want to try iSCSI: > = http://thegreyblog.blogspot.com/2010/02/using-zfs-with-apple-time-machine.= html > http://people.freebsd.org/~rse/iscsi/iscsi.txt Hmm, I _am_ using AFPD, not NFS for this.. I will see about using an = ISCSI disk image instead (although that would make it impossible to = resize once it's created right?) I see that the sparse disk image does use ~80000 files in a single = directory which does take.. a while.. to stat.. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C From owner-freebsd-stable@FreeBSD.ORG Fri Apr 29 00:13:57 2011 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 105E3106564A for ; Fri, 29 Apr 2011 00:13:57 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (unknown [IPv6:2001:44b8:7c07:5581:266:e1ff:fe0c:8f16]) by mx1.freebsd.org (Postfix) with ESMTP id 6172B8FC12 for ; Fri, 29 Apr 2011 00:13:54 +0000 (UTC) Received: from ur.dons.net.au (ppp208-191.lns1.adl2.internode.on.net [203.122.208.191] (may be forged)) (authenticated bits=0) by cain.gsoft.com.au (8.14.4/8.14.3) with ESMTP id p3T0DlrU096129 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 29 Apr 2011 09:43:48 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: "Daniel O'Connor" In-Reply-To: <20110428195601.GA31807@icarus.home.lan> Date: Fri, 29 Apr 2011 09:43:47 +0930 Content-Transfer-Encoding: quoted-printable Message-Id: References: <537A8F4F-A302-40F9-92DF-403388D99B4B@gsoft.com.au> <20110428195601.GA31807@icarus.home.lan> To: Jeremy Chadwick X-Mailer: Apple Mail (2.1084) X-Spam-Score: -0.272 () BAYES_00,RDNS_NONE X-Scanned-By: MIMEDefang 2.67 on 203.31.81.10 Cc: freebsd-stable List Subject: Re: ZFS vs OSX Time Machine 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, 29 Apr 2011 00:13:57 -0000 On 29/04/2011, at 5:26, Jeremy Chadwick wrote: >> I have the following ZFS related tunables >>=20 >> vfs.zfs.arc_max=3D"3072M" >> vfs.zfs.prefetch_disable=3D"1"=20 >> vfs.zfs.txg.timeout=3D5 >> vfs.zfs.cache_flush_disable=3D1 >=20 > Are the last two actually *working* in /boot/loader.conf? Can you > verify by looking at them via sysctl? AFAIK they shouldn't work, = since > they lack double-quotes around the values. Parsing errors are = supposed > to throw you back to the loader prompt. See loader.conf(5) for the > syntax. Yep, they're working :) > I'm also not sure why you're setting cache_flush_disable at all. I think I was wondering if it would help the abysmal write performance = of these disks.. >> Any help appreciated, thanks :) >=20 > Others seem to be battling stating that "NFS doesn't work for TM", but > that isn't what you're complaining about. You're complaining that > FreeBSD with ZFS + NFS performs extremely poorly when trying to do > backups from an OS X client using TM (writing to the NFS mount). Yes, and also TM is over AFP not NFS (I forgot to mention that..) > I have absolutely no experience with TM or OS X, so if it's actually a > client-level problem (which I'm doubting) I can't help you there. >=20 > Just sort of a ramble here at different things... >=20 > It would be useful to provide ZFS ARC sysctl data from the FreeBSD > system where you're seeing performance issues. "sysctl -a > kstat.zfs.misc.arcstats" should suffice. kstat.zfs.misc.arcstats.hits: 236092077 kstat.zfs.misc.arcstats.misses: 6451964 kstat.zfs.misc.arcstats.demand_data_hits: 98087637 kstat.zfs.misc.arcstats.demand_data_misses: 1220891 kstat.zfs.misc.arcstats.demand_metadata_hits: 138004440 kstat.zfs.misc.arcstats.demand_metadata_misses: 5231073 kstat.zfs.misc.arcstats.prefetch_data_hits: 0 kstat.zfs.misc.arcstats.prefetch_data_misses: 0 kstat.zfs.misc.arcstats.prefetch_metadata_hits: 0 kstat.zfs.misc.arcstats.prefetch_metadata_misses: 0 kstat.zfs.misc.arcstats.mru_hits: 15041670 kstat.zfs.misc.arcstats.mru_ghost_hits: 956048 kstat.zfs.misc.arcstats.mfu_hits: 221050407 kstat.zfs.misc.arcstats.mfu_ghost_hits: 3269042 kstat.zfs.misc.arcstats.allocated: 15785717 kstat.zfs.misc.arcstats.deleted: 4690878 kstat.zfs.misc.arcstats.stolen: 4990300 kstat.zfs.misc.arcstats.recycle_miss: 2142423 kstat.zfs.misc.arcstats.mutex_miss: 518 kstat.zfs.misc.arcstats.evict_skip: 2251705 kstat.zfs.misc.arcstats.evict_l2_cached: 0 kstat.zfs.misc.arcstats.evict_l2_eligible: 470396116480 kstat.zfs.misc.arcstats.evict_l2_ineligible: 2048 kstat.zfs.misc.arcstats.hash_elements: 482679 kstat.zfs.misc.arcstats.hash_elements_max: 503063 kstat.zfs.misc.arcstats.hash_collisions: 19593315 kstat.zfs.misc.arcstats.hash_chains: 116103 kstat.zfs.misc.arcstats.hash_chain_max: 16 kstat.zfs.misc.arcstats.p: 1692798721 kstat.zfs.misc.arcstats.c: 3221225472 kstat.zfs.misc.arcstats.c_min: 402653184 kstat.zfs.misc.arcstats.c_max: 3221225472 kstat.zfs.misc.arcstats.size: 3221162968 kstat.zfs.misc.arcstats.hdr_size: 103492088 kstat.zfs.misc.arcstats.data_size: 2764591616 kstat.zfs.misc.arcstats.other_size: 353079264 kstat.zfs.misc.arcstats.l2_hits: 0 kstat.zfs.misc.arcstats.l2_misses: 0 kstat.zfs.misc.arcstats.l2_feeds: 0 kstat.zfs.misc.arcstats.l2_rw_clash: 0 kstat.zfs.misc.arcstats.l2_read_bytes: 0 kstat.zfs.misc.arcstats.l2_write_bytes: 0 kstat.zfs.misc.arcstats.l2_writes_sent: 0 kstat.zfs.misc.arcstats.l2_writes_done: 0 kstat.zfs.misc.arcstats.l2_writes_error: 0 kstat.zfs.misc.arcstats.l2_writes_hdr_miss: 0 kstat.zfs.misc.arcstats.l2_evict_lock_retry: 0 kstat.zfs.misc.arcstats.l2_evict_reading: 0 kstat.zfs.misc.arcstats.l2_free_on_write: 0 kstat.zfs.misc.arcstats.l2_abort_lowmem: 0 kstat.zfs.misc.arcstats.l2_cksum_bad: 0 kstat.zfs.misc.arcstats.l2_io_error: 0 kstat.zfs.misc.arcstats.l2_size: 0 kstat.zfs.misc.arcstats.l2_hdr_size: 0 kstat.zfs.misc.arcstats.memory_throttle_count: 19 kstat.zfs.misc.arcstats.l2_write_trylock_fail: 0 kstat.zfs.misc.arcstats.l2_write_passed_headroom: 0 kstat.zfs.misc.arcstats.l2_write_spa_mismatch: 0 kstat.zfs.misc.arcstats.l2_write_in_l2: 0 kstat.zfs.misc.arcstats.l2_write_io_in_progress: 0 kstat.zfs.misc.arcstats.l2_write_not_cacheable: 1 kstat.zfs.misc.arcstats.l2_write_full: 0 kstat.zfs.misc.arcstats.l2_write_buffer_iter: 0 kstat.zfs.misc.arcstats.l2_write_pios: 0 kstat.zfs.misc.arcstats.l2_write_buffer_bytes_scanned: 0 kstat.zfs.misc.arcstats.l2_write_buffer_list_iter: 0 kstat.zfs.misc.arcstats.l2_write_buffer_list_null_iter: 0 > You should also try executing "zpool iostat -v 1" during the TM backup > to see if there's a particular device which is behaving poorly. There > have been reports of ZFS pools behaving poorly when a single device > within the pool has slow I/O (e.g. 5 hard disks, one of which has > internal issues, resulting in the entire pool performing horribly). = You > should let this run for probably 60-120 seconds to get an idea. Given > your parameters above (assuming vfs.zfs.txg.timeout IS in fact 5!), = you > should see "bursts" of writes every 5 seconds. OK. > I know that there are some things on ZFS that perform badly overall. > Anything that involves excessive/large numbers of files (not file = sizes, > but actual files themselves) seems to perform not-so-great with ZFS. > For example, Maildir on ZFS =3D piss-poor performance. There are ways = to > work around this issue (if I remember correctly, by adding a dedicated > "log" device to your ZFS pool, but be aware your log devices need to > be reliable (if you have a single log device and it fails the entire > pool is damaged, if I remember right)), but I don't consider it > feasible. So if TM is creating tons of files on the NFS mount (backed > by ZFS), then I imagine the performance isn't so great. Hmm, the sparse disk image does have ~80000 files in a single = directory.. > Could you please provide the following sysctl values? Thanks. >=20 > kern.maxvnodes > kern.minvnodes > vfs.freevnodes > vfs.numvnodes kern.maxvnodes: 204477 kern.minvnodes: 51119 vfs.freevnodes: 51118 vfs.numvnodes: 66116 > If the FreeBSD machine has a wireless card in it, if at all possible > could you try ruling that out by hooking up wired Ethernet instead? > It's probably not the cause, but worth trying anyway. If you have a > home router or something doing 802.11, don't bother with this idea. The FreeBSD box is wired, although it's using an re card as the em card = died(!!). The OSX box is connected via an Airport Express (11n). > Next, you COULD try using Samba/CIFS on the FreeBSD box to see if you > can narrow the issue down to bad NFS performance. Please see this = post > of mine about tuning Samba on FreeBSD (backed by ZFS) to get extremely > good performance. Many people responded and said their performance > drastically improved (you can see the thread yourself). The trick is > AIO. You can ignore the part about setting vm.kmem_size in = loader.conf; > that advice is now old/deprecated (does not pertain to you given the > date of your kernel), and vfs.zfs.txg.write_limit_override is = something > you shouldn't mess with unless absolutely needed to leave it default: >=20 > = http://lists.freebsd.org/pipermail/freebsd-stable/2011-February/061642.htm= l OK. I don't think TM can use CIFS, I will try ISCSI as someone else = suggested, perhaps it will help. > Finally, when was the last time this FreeBSD machine was rebooted? = Some > people have seen horrible performance that goes away after a reboot. > There's some speculation that memory fragmentation has something to do > with it. I simply don't know. I'm not telling you to reboot the box > (please don't; it would be more useful if it could be kept up in case > folks want to do analysis of it). I think performance does improve after a reboot :( top looks like.. last pid: 16112; load averages: 0.24, 0.22, 0.23 = up 8+16:11:50 09:43:19 653 processes: 1 running, 652 sleeping CPU: 3.6% user, 0.0% nice, 3.4% system, 0.6% interrupt, 92.5% idle Mem: 1401M Active, 578M Inact, 4143M Wired, 4904K Cache, 16M Buf, 1658M = Free Swap: 4096M Total, 160M Used, 3936M Free, 3% Inuse although free does go down very low (~250MB) at times. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C From owner-freebsd-stable@FreeBSD.ORG Fri Apr 29 00:19:53 2011 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 686441065689; Fri, 29 Apr 2011 00:19:53 +0000 (UTC) (envelope-from andy@fud.org.nz) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id B06158FC15; Fri, 29 Apr 2011 00:19:52 +0000 (UTC) Received: by wyf23 with SMTP id 23so3254631wyf.13 for ; Thu, 28 Apr 2011 17:19:51 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.145.130 with SMTP id p2mr2448655wej.58.1304034684818; Thu, 28 Apr 2011 16:51:24 -0700 (PDT) Sender: andy@fud.org.nz Received: by 10.216.187.133 with HTTP; Thu, 28 Apr 2011 16:51:24 -0700 (PDT) In-Reply-To: <20110428233030.GA35428@icarus.home.lan> References: <201104282106.p3SL6W1Y030026@freebsd-stable.sentex.ca> <20110428233030.GA35428@icarus.home.lan> Date: Fri, 29 Apr 2011 11:51:24 +1200 X-Google-Sender-Auth: 0GlbRnwmJUPk9M-2En9IwVNpbN4 Message-ID: From: Andrew Thompson To: Jeremy Chadwick Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: arm@freebsd.org, stable@freebsd.org, FreeBSD Tinderbox , hselasky@freebsd.org Subject: Re: [releng_8 tinderbox] failure on arm/arm 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, 29 Apr 2011 00:19:53 -0000 On 29 April 2011 11:30, Jeremy Chadwick wrote: > On Thu, Apr 28, 2011 at 09:06:32PM +0000, FreeBSD Tinderbox wrote: > > ===> usr.sbin/usbdump (all) > > cc -O -pipe -std=gnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -W > -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes > -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow > -Wcast-align -Wunused-parameter -Wno-uninitialized -Wno-pointer-sign -c > /src/usr.sbin/usbdump/usbdump.c > > cc1: warnings being treated as errors > > /src/usr.sbin/usbdump/usbdump.c: In function 'print_apacket': > > /src/usr.sbin/usbdump/usbdump.c:353: warning: cast increases required > alignment of target type > > /src/usr.sbin/usbdump/usbdump.c: In function 'print_packets': > > /src/usr.sbin/usbdump/usbdump.c:399: warning: cast increases required > alignment of target type > > *** Error code 1 > > > > Stop in /src/usr.sbin/usbdump. > > *** Error code 1 > > CC'ing hselasky and thompsa for review of this. > > For failure logs (so far ia64 and arm), please see end of this page: > > http://lists.freebsd.org/pipermail/freebsd-stable/2011-April/thread.html > > Commit question is revision 1.6.2.2 to RELENG_8: > > http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/usbdump/usbdump.c > > Relevant code bits: > I merged the missing rev a few hours ago, http://svnweb.freebsd.org/base?view=revision&revision=221185 Andrew From owner-freebsd-stable@FreeBSD.ORG Fri Apr 29 01:08:32 2011 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 10508106564A for ; Fri, 29 Apr 2011 01:08:32 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta08.emeryville.ca.mail.comcast.net (qmta08.emeryville.ca.mail.comcast.net [76.96.30.80]) by mx1.freebsd.org (Postfix) with ESMTP id EB7968FC12 for ; Fri, 29 Apr 2011 01:08:31 +0000 (UTC) Received: from omta22.emeryville.ca.mail.comcast.net ([76.96.30.89]) by qmta08.emeryville.ca.mail.comcast.net with comcast id dD5n1g00D1vN32cA8D8XL4; Fri, 29 Apr 2011 01:08:31 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta22.emeryville.ca.mail.comcast.net with comcast id dD8V1g01N1t3BNj8iD8W3R; Fri, 29 Apr 2011 01:08:30 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 6C44E9B418; Thu, 28 Apr 2011 18:08:29 -0700 (PDT) Date: Thu, 28 Apr 2011 18:08:29 -0700 From: Jeremy Chadwick To: Daniel O'Connor Message-ID: <20110429010829.GA36744@icarus.home.lan> References: <537A8F4F-A302-40F9-92DF-403388D99B4B@gsoft.com.au> <20110428195601.GA31807@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable List Subject: Re: ZFS vs OSX Time Machine 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, 29 Apr 2011 01:08:32 -0000 On Fri, Apr 29, 2011 at 09:43:47AM +0930, Daniel O'Connor wrote: > > On 29/04/2011, at 5:26, Jeremy Chadwick wrote: > >> I have the following ZFS related tunables > >> > >> vfs.zfs.arc_max="3072M" > >> vfs.zfs.prefetch_disable="1" > >> vfs.zfs.txg.timeout=5 > >> vfs.zfs.cache_flush_disable=1 > > > > Are the last two actually *working* in /boot/loader.conf? Can you > > verify by looking at them via sysctl? AFAIK they shouldn't work, since > > they lack double-quotes around the values. Parsing errors are supposed > > to throw you back to the loader prompt. See loader.conf(5) for the > > syntax. > > Yep, they're working :) > > > I'm also not sure why you're setting cache_flush_disable at all. > > I think I was wondering if it would help the abysmal write performance of these disks.. > > >> Any help appreciated, thanks :) > > > > Others seem to be battling stating that "NFS doesn't work for TM", but > > that isn't what you're complaining about. You're complaining that > > FreeBSD with ZFS + NFS performs extremely poorly when trying to do > > backups from an OS X client using TM (writing to the NFS mount). > > Yes, and also TM is over AFP not NFS (I forgot to mention that..) > > > I have absolutely no experience with TM or OS X, so if it's actually a > > client-level problem (which I'm doubting) I can't help you there. > > > > Just sort of a ramble here at different things... > > > > It would be useful to provide ZFS ARC sysctl data from the FreeBSD > > system where you're seeing performance issues. "sysctl -a > > kstat.zfs.misc.arcstats" should suffice. > > kstat.zfs.misc.arcstats.hits: 236092077 > kstat.zfs.misc.arcstats.misses: 6451964 > kstat.zfs.misc.arcstats.demand_data_hits: 98087637 > kstat.zfs.misc.arcstats.demand_data_misses: 1220891 > kstat.zfs.misc.arcstats.demand_metadata_hits: 138004440 > kstat.zfs.misc.arcstats.demand_metadata_misses: 5231073 > kstat.zfs.misc.arcstats.prefetch_data_hits: 0 > kstat.zfs.misc.arcstats.prefetch_data_misses: 0 > kstat.zfs.misc.arcstats.prefetch_metadata_hits: 0 > kstat.zfs.misc.arcstats.prefetch_metadata_misses: 0 > kstat.zfs.misc.arcstats.mru_hits: 15041670 > kstat.zfs.misc.arcstats.mru_ghost_hits: 956048 > kstat.zfs.misc.arcstats.mfu_hits: 221050407 > kstat.zfs.misc.arcstats.mfu_ghost_hits: 3269042 > kstat.zfs.misc.arcstats.allocated: 15785717 > kstat.zfs.misc.arcstats.deleted: 4690878 > kstat.zfs.misc.arcstats.stolen: 4990300 > kstat.zfs.misc.arcstats.recycle_miss: 2142423 > kstat.zfs.misc.arcstats.mutex_miss: 518 > kstat.zfs.misc.arcstats.evict_skip: 2251705 > kstat.zfs.misc.arcstats.evict_l2_cached: 0 > kstat.zfs.misc.arcstats.evict_l2_eligible: 470396116480 > kstat.zfs.misc.arcstats.evict_l2_ineligible: 2048 > kstat.zfs.misc.arcstats.hash_elements: 482679 > kstat.zfs.misc.arcstats.hash_elements_max: 503063 > kstat.zfs.misc.arcstats.hash_collisions: 19593315 > kstat.zfs.misc.arcstats.hash_chains: 116103 > kstat.zfs.misc.arcstats.hash_chain_max: 16 > kstat.zfs.misc.arcstats.p: 1692798721 > kstat.zfs.misc.arcstats.c: 3221225472 > kstat.zfs.misc.arcstats.c_min: 402653184 > kstat.zfs.misc.arcstats.c_max: 3221225472 > kstat.zfs.misc.arcstats.size: 3221162968 > kstat.zfs.misc.arcstats.hdr_size: 103492088 > kstat.zfs.misc.arcstats.data_size: 2764591616 > kstat.zfs.misc.arcstats.other_size: 353079264 > kstat.zfs.misc.arcstats.l2_hits: 0 > kstat.zfs.misc.arcstats.l2_misses: 0 > kstat.zfs.misc.arcstats.l2_feeds: 0 > kstat.zfs.misc.arcstats.l2_rw_clash: 0 > kstat.zfs.misc.arcstats.l2_read_bytes: 0 > kstat.zfs.misc.arcstats.l2_write_bytes: 0 > kstat.zfs.misc.arcstats.l2_writes_sent: 0 > kstat.zfs.misc.arcstats.l2_writes_done: 0 > kstat.zfs.misc.arcstats.l2_writes_error: 0 > kstat.zfs.misc.arcstats.l2_writes_hdr_miss: 0 > kstat.zfs.misc.arcstats.l2_evict_lock_retry: 0 > kstat.zfs.misc.arcstats.l2_evict_reading: 0 > kstat.zfs.misc.arcstats.l2_free_on_write: 0 > kstat.zfs.misc.arcstats.l2_abort_lowmem: 0 > kstat.zfs.misc.arcstats.l2_cksum_bad: 0 > kstat.zfs.misc.arcstats.l2_io_error: 0 > kstat.zfs.misc.arcstats.l2_size: 0 > kstat.zfs.misc.arcstats.l2_hdr_size: 0 > kstat.zfs.misc.arcstats.memory_throttle_count: 19 > kstat.zfs.misc.arcstats.l2_write_trylock_fail: 0 > kstat.zfs.misc.arcstats.l2_write_passed_headroom: 0 > kstat.zfs.misc.arcstats.l2_write_spa_mismatch: 0 > kstat.zfs.misc.arcstats.l2_write_in_l2: 0 > kstat.zfs.misc.arcstats.l2_write_io_in_progress: 0 > kstat.zfs.misc.arcstats.l2_write_not_cacheable: 1 > kstat.zfs.misc.arcstats.l2_write_full: 0 > kstat.zfs.misc.arcstats.l2_write_buffer_iter: 0 > kstat.zfs.misc.arcstats.l2_write_pios: 0 > kstat.zfs.misc.arcstats.l2_write_buffer_bytes_scanned: 0 > kstat.zfs.misc.arcstats.l2_write_buffer_list_iter: 0 > kstat.zfs.misc.arcstats.l2_write_buffer_list_null_iter: 0 Thanks. I don't see anything indicative here of ARC problems. memory_throttle_count being 19 is acceptable as well (though a very large number could indicate issues of a different sort). Otherwise things look very good/normal. > > You should also try executing "zpool iostat -v 1" during the TM backup > > to see if there's a particular device which is behaving poorly. There > > have been reports of ZFS pools behaving poorly when a single device > > within the pool has slow I/O (e.g. 5 hard disks, one of which has > > internal issues, resulting in the entire pool performing horribly). You > > should let this run for probably 60-120 seconds to get an idea. Given > > your parameters above (assuming vfs.zfs.txg.timeout IS in fact 5!), you > > should see "bursts" of writes every 5 seconds. > > OK. > > > I know that there are some things on ZFS that perform badly overall. > > Anything that involves excessive/large numbers of files (not file sizes, > > but actual files themselves) seems to perform not-so-great with ZFS. > > For example, Maildir on ZFS = piss-poor performance. There are ways to > > work around this issue (if I remember correctly, by adding a dedicated > > "log" device to your ZFS pool, but be aware your log devices need to > > be reliable (if you have a single log device and it fails the entire > > pool is damaged, if I remember right)), but I don't consider it > > feasible. So if TM is creating tons of files on the NFS mount (backed > > by ZFS), then I imagine the performance isn't so great. > > Hmm, the sparse disk image does have ~80000 files in a single directory.. Have you tried looking at dirhash sysctls? Oh foo, that's for UFS only. Could you please provide output from "zfs get all poolname"? Myself and others would like to review what settings you're using on the filesystem. If it's a separate filesystem (e.g. pool/foobar), please also provide output from "zfs get all pool". > > Could you please provide the following sysctl values? Thanks. > > > > kern.maxvnodes > > kern.minvnodes > > vfs.freevnodes > > vfs.numvnodes > > kern.maxvnodes: 204477 > kern.minvnodes: 51119 > vfs.freevnodes: 51118 > vfs.numvnodes: 66116 You look fine here -- no need to increase the kern.maxvnodes sysctl. > > If the FreeBSD machine has a wireless card in it, if at all possible > > could you try ruling that out by hooking up wired Ethernet instead? > > It's probably not the cause, but worth trying anyway. If you have a > > home router or something doing 802.11, don't bother with this idea. > > The FreeBSD box is wired, although it's using an re card as the em card died(!!). > > The OSX box is connected via an Airport Express (11n). Can you connect something to it via Ethernet and attempt an FTP transfer (both PUT (store on server) and GET (retrieve from server)) from a client on the wired network? Make sure whatever you're PUT'ing and GET'ing are using the ZFS filesystem. Don't forget "binary" mode too. You should see very good performance on files that are already in the ARC. So for example, pick a 500MB ISO file that hasn't been accessed previously (thus isn't in the ARC). GET'ing it should result in a lot of disk I/O (zpool iostat -v 1). But a subsequent GET should show very little disk I/O, as all the data should be coming from memory (ARC). A PUT would test write. Basically what I'm trying to figure out here is if the network layer is somehow causing these problems for you or not. Wireless is simply too unreliable/too flippant in packet loss and latency to be a good medium to test throughput of a filesystem. Period. > > Next, you COULD try using Samba/CIFS on the FreeBSD box to see if you > > can narrow the issue down to bad NFS performance. Please see this post > > of mine about tuning Samba on FreeBSD (backed by ZFS) to get extremely > > good performance. Many people responded and said their performance > > drastically improved (you can see the thread yourself). The trick is > > AIO. You can ignore the part about setting vm.kmem_size in loader.conf; > > that advice is now old/deprecated (does not pertain to you given the > > date of your kernel), and vfs.zfs.txg.write_limit_override is something > > you shouldn't mess with unless absolutely needed to leave it default: > > > > http://lists.freebsd.org/pipermail/freebsd-stable/2011-February/061642.html > > OK. I don't think TM can use CIFS, I will try ISCSI as someone else suggested, perhaps it will help. Be aware there are all sorts of caveats/complexities with iSCSI on FreeBSD. There are past threads on -stable and -fs talking about them in great detail. I personally wouldn't go this route. Why can't OS X use CIFS? It has the ability to mount a SMB filesystem, right? Is there some reason you can't mount that, then tell TM to write its backups to /mountedcifs? > > Finally, when was the last time this FreeBSD machine was rebooted? Some > > people have seen horrible performance that goes away after a reboot. > > There's some speculation that memory fragmentation has something to do > > with it. I simply don't know. I'm not telling you to reboot the box > > (please don't; it would be more useful if it could be kept up in case > > folks want to do analysis of it). > > I think performance does improve after a reboot :( This could be a memory performance or fragmentation problem then. Gosh it's been a long time since I've read about that. Some FreeBSD folks knew of such, and I think someone came up with a patch for it, but I'm not sure. I wish I could remember the name of the developer who was talking about it. Artem Belevich maybe? The other problem a user had pertaining to ZFS and memory performance was even more odd, but was eventually tracked down. He had installed two DIMMs in his machine (making a total of 4) and suddenly memory performance was abysmal. Remove the DIMMs, performance restored. Put the two removed DIMMs in (previous working ones out), performance was fine. If I remember right, the issue turned out to be a bug in the BIOS, and a BIOS upgrade from Intel (it was an Intel motherboard) fixed it. Intel is one of the only companies that releases *very* concise and decent changelogs for their BIOSes, which is wonderful. > last pid: 16112; load averages: 0.24, 0.22, 0.23 up 8+16:11:50 09:43:19 > 653 processes: 1 running, 652 sleeping > CPU: 3.6% user, 0.0% nice, 3.4% system, 0.6% interrupt, 92.5% idle > Mem: 1401M Active, 578M Inact, 4143M Wired, 4904K Cache, 16M Buf, 1658M Free > Swap: 4096M Total, 160M Used, 3936M Free, 3% Inuse > > although free does go down very low (~250MB) at times. This is normal. The ZFS ARC has most of your memory (shown as "Wired" in the above top output). If something needs memory, parts of the ARC will be released/freed given memory pressure. I will note something, however: your ARC max is set to 3072MB, yet Wired is around 4143MB. Do you have something running on this box that takes up a lot of RAM? mysqld, etc..? I'm trying to account for the "extra gigabyte" in Wired. "top -o res" might help here, but we'd need to see the process list. I'm thinking something else on your machine is also taking up Wired, because your arcstats shows: > kstat.zfs.misc.arcstats.c: 3221225472 > kstat.zfs.misc.arcstats.c_min: 402653184 > kstat.zfs.misc.arcstats.c_max: 3221225472 > kstat.zfs.misc.arcstats.size: 3221162968 Which is about 3072MB (there is always some degree of variance). -- | Jeremy Chadwick jdc@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 Apr 29 01:08:33 2011 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 EAD6A106566B for ; Fri, 29 Apr 2011 01:08:32 +0000 (UTC) (envelope-from mwaltz@PACIFIC.EDU) Received: from mx10.pacific.edu (mx10.pacific.edu [138.9.240.95]) by mx1.freebsd.org (Postfix) with ESMTP id C5DE38FC15 for ; Fri, 29 Apr 2011 01:08:32 +0000 (UTC) Received: from mx10.pacific.edu (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 220BCA4A5B8; Thu, 28 Apr 2011 18:08:32 -0700 (PDT) Received: from EXCASHUB2.stk.pacific.edu (excashub2.stk.pacific.edu [10.9.4.122]) by mx10.pacific.edu (Postfix) with ESMTP id DF8D6A27A70; Thu, 28 Apr 2011 18:08:31 -0700 (PDT) Received: from EXMB2.STK.PACIFIC.EDU ([10.9.4.102]) by excashub2.stk.pacific.edu ([10.9.4.122]) with mapi id 14.01.0289.001; Thu, 28 Apr 2011 18:08:31 -0700 From: Malcolm Waltz To: Daniel O'Connor Thread-Topic: ZFS vs OSX Time Machine Thread-Index: AQHMBa0X6h4oagP/h0u8OmOQbCHfSJRz8aKAgAB54ICAABJigA== Date: Fri, 29 Apr 2011 01:08:30 +0000 Message-ID: References: <537A8F4F-A302-40F9-92DF-403388D99B4B@gsoft.com.au> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.9.104.200] Content-Type: text/plain; charset="us-ascii" Content-ID: <24325F0695B00D49A8B9FE0474F7576F@pacific.local> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-PMX-Version: 5.6.0.2009776, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2011.4.29.5414 X-PerlMx-Spam: Gauge=IIIIIIII, Probability=8%, Report=' BLOGSPOT_URI 0.05, KNOWN_FREEWEB_URI 0.05, SUPERLONG_LINE 0.05, BODYTEXTP_SIZE_3000_LESS 0, BODY_SIZE_2000_2999 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, ECARD_KNOWN_DOMAINS 0, FROM_EDU_TLD 0, WEBMAIL_SOURCE 0, WEBMAIL_XOIP 0, WEBMAIL_X_IP_HDR 0, __BOUNCE_CHALLENGE_SUBJ 0, __BOUNCE_NDR_SUBJ_EXEMPT 0, __CP_MEDIA_BODY 0, __CP_URI_IN_BODY 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_XOIP 0, __KNOWN_FREEWEB_URI1 0, __LINES_OF_YELLING 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __MSGID_APPLEMAIL 0, __PHISH_SPEAR_STRUCTURE_1 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __URI_NO_MAILTO 0, __URI_NS ' Cc: freebsd-stable List Subject: Re: ZFS vs OSX Time Machine 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, 29 Apr 2011 01:08:33 -0000 ZFS volumes (zvol s) can definitely be resized using the volsize property: # zfs get volsize mypool/myvol NAME PROPERTY VALUE SOURCE mypool/myvol volsize 2G - # zfs set volsize=3D4g mypool/myvol Mac OS 10.5 and later allows you to resize Journaled HFS+ volumes (using di= skutil or Disk Utility.app). Doing a quick google search, I see plenty of = references to decreasing the size of a TimeMachine volume, so it's probably= possible to increase it as well. I'm sure you can find more with a little= googleing. "man diskutil" (look for resizeVolume) indicates that you can increase and = decrease the size and doesn't mention anything special about Time Machine. On Apr 28, 2011, at 5:02 PM, Daniel O'Connor wrote: >=20 > On 29/04/2011, at 2:16, Malcolm Waltz wrote: >> I doubt the issues you are encountering have much to do with ZFS. >>=20 >> It sounds like you are using TimeMachine over NFS. Obviously, Apple doe= s not support that configuration: >> http://www.google.com/search?q=3Dtime+machine+nfs+site:apple.com >>=20 >> In my opinion, TimeMachine should only be used with block storage. If y= ou use any kind of file-sharing protocol (AFP, SMB/CIFS or NFS), TimeMachin= e is implemented using a sparse disk image broken into hundreds or thousand= s of separate files. This is a hack at best. >>=20 >> Time machine works very well with locally attached storage, but if you n= eed to use network storage, you might want to try iSCSI: >> http://thegreyblog.blogspot.com/2010/02/using-zfs-with-apple-time-machin= e.html >> http://people.freebsd.org/~rse/iscsi/iscsi.txt >=20 > Hmm, I _am_ using AFPD, not NFS for this.. I will see about using an ISCS= I disk image instead (although that would make it impossible to resize once= it's created right?) >=20 > I see that the sparse disk image does use ~80000 files in a single direct= ory which does take.. a while.. to stat.. >=20 > -- > Daniel O'Connor software and network engineer > for Genesis Software - http://www.gsoft.com.au > "The nice thing about standards is that there > are so many of them to choose from." > -- Andrew Tanenbaum > GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C >=20 >=20 >=20 >=20 >=20 >=20 From owner-freebsd-stable@FreeBSD.ORG Fri Apr 29 01:48:39 2011 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 1780D1065674 for ; Fri, 29 Apr 2011 01:48:39 +0000 (UTC) (envelope-from mwaltz@PACIFIC.EDU) Received: from mx20.pacific.edu (mx20.pacific.edu [138.9.110.64]) by mx1.freebsd.org (Postfix) with ESMTP id E20618FC16 for ; Fri, 29 Apr 2011 01:48:38 +0000 (UTC) Received: from mx20.pacific.edu (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 80D45AC8663; Thu, 28 Apr 2011 18:48:38 -0700 (PDT) Received: from EXCASHUB1.stk.pacific.edu (excashub1.stk.pacific.edu [10.9.4.121]) by mx20.pacific.edu (Postfix) with ESMTP id 13FA1AC8661; Thu, 28 Apr 2011 18:48:38 -0700 (PDT) Received: from EXMB2.STK.PACIFIC.EDU ([10.9.4.102]) by excashub1.stk.pacific.edu ([10.9.4.121]) with mapi id 14.01.0289.001; Thu, 28 Apr 2011 18:48:38 -0700 From: Malcolm Waltz To: Jeremy Chadwick Thread-Topic: ZFS vs OSX Time Machine Thread-Index: AQHMBa0X6h4oagP/h0u8OmOQbCHfSJR0JpeAgABIBYCAAA9IgIAACzYA Date: Fri, 29 Apr 2011 01:48:37 +0000 Message-ID: <5ED49CD2-5FF2-4110-8EEA-F754373D16F3@pacific.edu> References: <537A8F4F-A302-40F9-92DF-403388D99B4B@gsoft.com.au> <20110428195601.GA31807@icarus.home.lan> <20110429010829.GA36744@icarus.home.lan> In-Reply-To: <20110429010829.GA36744@icarus.home.lan> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.9.104.200] MIME-Version: 1.0 X-PMX-Version: 5.6.0.2009776, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2011.4.29.13317 X-PerlMx-Spam: Gauge=IIIIIIII, Probability=8%, Report=' SUPERLONG_LINE 0.05, BODYTEXTH_SIZE_10000_LESS 0, BODYTEXTP_SIZE_3000_LESS 0, BODY_SIZE_5000_5999 0, BODY_SIZE_7000_LESS 0, FROM_EDU_TLD 0, WEBMAIL_SOURCE 0, WEBMAIL_XOIP 0, WEBMAIL_X_IP_HDR 0, __BOUNCE_CHALLENGE_SUBJ 0, __BOUNCE_NDR_SUBJ_EXEMPT 0, __CP_MEDIA_BODY 0, __CP_URI_IN_BODY 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __CTYPE_MULTIPART_ALT 0, __HAS_HTML 0, __HAS_MSGID 0, __HAS_XOIP 0, __MIME_HTML 0, __MIME_VERSION 0, __MSGID_APPLEMAIL 0, __RATWARE_SIGNATURE_3_N1 0, __SANE_MSGID 0, __TAG_EXISTS_HTML 0, __TO_MALFORMED_2 0, __URI_NO_MAILTO 0, __URI_NS ' Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable List Subject: Re: ZFS vs OSX Time Machine 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, 29 Apr 2011 01:48:39 -0000 On Apr 28, 2011, at 6:08 PM, Jeremy Chadwick wrote: Be aware there are all sorts of caveats/complexities with iSCSI on FreeBSD. There are past threads on -stable and -fs talking about them in great detail. I personally wouldn't go this route. Why can't OS X use CIFS? It has the ability to mount a SMB filesystem, right? Is there some reason you can't mount that, then tell TM to write its backups to /mountedcifs? Ahh... I see. Well this works perfectly (iSCSI on ZFS): http://www.nexenta.org/ Perhaps we will see some improvements in the future. As for CIFS, yes some people do that. I wouldn't, but whatever. Certainly= you won't see _better_ performance. Most people choose AFP for this (as d= id the original poster). http://www.nickebo.net/tag/benchmark/ (there are plenty of others) As you can read in my previous posts, Time Machine needs block storage. If= you don't use block storage, it will emulate block storage using a disk im= age, which in this case is generating ~80000 files in one directory (sparse= -bands). Good luck with that. If iSCSI is not stable on FreeBSD, then it's probably best not to store Tim= e Machine data on FreeBSD. Some people don't seem to have issues with this= (as one other poster mentioned). I suppose it depends on how much and wha= t kind of data you are backing up. I can say that if you are backing up a media library and other normal user = data using Time Machine, it definitely performs poorly (unusable) after a w= hile if you are using anything but block based storage. If it hasn't happe= ned to you yet, just wait. It will. From owner-freebsd-stable@FreeBSD.ORG Fri Apr 29 02:13:18 2011 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 EFCBA106564A for ; Fri, 29 Apr 2011 02:13:18 +0000 (UTC) (envelope-from artemb@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id A51A28FC0C for ; Fri, 29 Apr 2011 02:13:18 +0000 (UTC) Received: by qwc9 with SMTP id 9so1966163qwc.13 for ; Thu, 28 Apr 2011 19:13:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=Baxs7jAIq5FCfeiAcIy1R2sh8CEW6XujghVI+7nmWvA=; b=Ld+Z6ec+3J5iT4sZXiX97GdcVJyL2Fu5j4rKQYOxYMxg1S+Z8XAFs6hUQmfuBcPE5e au/2gIhahz87PuiJg6YC6senkCQiEenvuIFtjL+7yoj2YmHLEguCGOivguEWKOuRxnBl pqf7aRvExcxUAPVhXxa6yxAZjm4XjG4Bfs/u0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=napQYeJbz0qwK6TOdH9opnE+SssXrp6xrdyxh6MrxpaSuEjnoZw8UbKXbyEj+Fp9KF FcGW4PDAXAVPCWSTeizeGB8RXapGpo+vy4Pz3uS/rT+Nwvf7L459YPcnnzdZ47WBPqUE itCduBFy9TMUDmbHqn+OAGVJZCI7yhXKrreeU= MIME-Version: 1.0 Received: by 10.229.27.193 with SMTP id j1mr3489082qcc.82.1304043197868; Thu, 28 Apr 2011 19:13:17 -0700 (PDT) Sender: artemb@gmail.com Received: by 10.229.95.140 with HTTP; Thu, 28 Apr 2011 19:13:17 -0700 (PDT) In-Reply-To: <20110429010829.GA36744@icarus.home.lan> References: <537A8F4F-A302-40F9-92DF-403388D99B4B@gsoft.com.au> <20110428195601.GA31807@icarus.home.lan> <20110429010829.GA36744@icarus.home.lan> Date: Thu, 28 Apr 2011 19:13:17 -0700 X-Google-Sender-Auth: tXHR5Io0WtoTMIuvgQTXLDuw0Ig Message-ID: From: Artem Belevich To: Jeremy Chadwick Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable List Subject: Re: ZFS vs OSX Time Machine 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, 29 Apr 2011 02:13:19 -0000 On Thu, Apr 28, 2011 at 6:08 PM, Jeremy Chadwick wrote: > I will note something, however: your ARC max is set to 3072MB, yet Wired > is around 4143MB. =A0Do you have something running on this box that takes > up a lot of RAM? =A0mysqld, etc..? =A0I'm trying to account for the "extr= a > gigabyte" in Wired. =A0"top -o res" might help here, but we'd need to see > the process list. > > I'm thinking something else on your machine is also taking up Wired, > because your arcstats shows: > >> kstat.zfs.misc.arcstats.c: 3221225472 >> kstat.zfs.misc.arcstats.c_min: 402653184 >> kstat.zfs.misc.arcstats.c_max: 3221225472 >> kstat.zfs.misc.arcstats.size: 3221162968 > > Which is about 3072MB (there is always some degree of variance). The difference is probably due to fragmentation (most of ARC allocations are served from power-of-2 zones, if I'm not mistaken) + a lot of wired memory sits in slab allocator caches (FREE column in vmstat -z). On a system with ARC size of ~16G I regularly see ~22GB wired. Ona smaller box I get about 7GB wired at around 5.5GB ARC size. --Artem From owner-freebsd-stable@FreeBSD.ORG Fri Apr 29 02:40:08 2011 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 3125E1065675; Fri, 29 Apr 2011 02:40:08 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (unknown [IPv6:2001:44b8:7c07:5581:266:e1ff:fe0c:8f16]) by mx1.freebsd.org (Postfix) with ESMTP id CA50E8FC20; Fri, 29 Apr 2011 02:40:06 +0000 (UTC) Received: from ur.gsoft.com.au (Ur.gsoft.com.au [203.31.81.44]) (authenticated bits=0) by cain.gsoft.com.au (8.14.4/8.14.3) with ESMTP id p3T2dxd2007270 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 29 Apr 2011 12:09:59 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: "Daniel O'Connor" In-Reply-To: Date: Fri, 29 Apr 2011 12:09:59 +0930 Content-Transfer-Encoding: quoted-printable Message-Id: References: <537A8F4F-A302-40F9-92DF-403388D99B4B@gsoft.com.au> <20110428195601.GA31807@icarus.home.lan> <20110429010829.GA36744@icarus.home.lan> To: Artem Belevich X-Mailer: Apple Mail (2.1084) X-Spam-Score: -2.51 () ALL_TRUSTED,BAYES_00,T_RP_MATCHES_RCVD X-Scanned-By: MIMEDefang 2.67 on 203.31.81.10 Cc: freebsd-stable List , Jeremy Chadwick Subject: Re: ZFS vs OSX Time Machine 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, 29 Apr 2011 02:40:08 -0000 On 29/04/2011, at 11:43, Artem Belevich wrote: > On Thu, Apr 28, 2011 at 6:08 PM, Jeremy Chadwick > wrote: >> I will note something, however: your ARC max is set to 3072MB, yet = Wired >> is around 4143MB. Do you have something running on this box that = takes >> up a lot of RAM? mysqld, etc..? I'm trying to account for the = "extra >> gigabyte" in Wired. "top -o res" might help here, but we'd need to = see >> the process list. >>=20 >> I'm thinking something else on your machine is also taking up Wired, >> because your arcstats shows: >>=20 >>> kstat.zfs.misc.arcstats.c: 3221225472 >>> kstat.zfs.misc.arcstats.c_min: 402653184 >>> kstat.zfs.misc.arcstats.c_max: 3221225472 >>> kstat.zfs.misc.arcstats.size: 3221162968 >>=20 >> Which is about 3072MB (there is always some degree of variance). >=20 > The difference is probably due to fragmentation (most of ARC > allocations are served from power-of-2 zones, if I'm not mistaken) + a > lot of wired memory sits in slab allocator caches (FREE column in > vmstat -z). On a system with ARC size of ~16G I regularly see ~22GB > wired. Ona smaller box I get about 7GB wired at around 5.5GB ARC size. This system also does double duty as a desktop PC so it gets a fair = hammering.. It did have 4GB of RAM but that was fairly terrible, 8GB is a lot better = though :) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C From owner-freebsd-stable@FreeBSD.ORG Fri Apr 29 02:51:19 2011 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 0BD241065670; Fri, 29 Apr 2011 02:51:19 +0000 (UTC) (envelope-from telbizov@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id 981878FC1B; Fri, 29 Apr 2011 02:51:18 +0000 (UTC) Received: by qwc9 with SMTP id 9so1976506qwc.13 for ; Thu, 28 Apr 2011 19:51:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=1FI/iUtfDLAO5HyqDPSiTM5Y7GLq1cfJ+dEdPx5XFDM=; b=k6eTxcwlB2/1krmOgGlMxuBroaHoky3VncJU5hsdkMT43ZEvAGRZ6H6wjR17lKWXsV ARfvOuxTYZGo1MHfErUqI1/rgwUzB+bX0yfOpyxMjm8BF8cmx+bvbyB75YwzKsYv1siC nJKQp9mHDvTwTr5GGgtyzFNYRu7odZbgje2Iw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=IMX/7ahYcvl1V0/rj0r2l+WliL3kA3Mx2rGEmzb3QnA69O+JypD8J18nU+PB8W7QFs oNjaxaCcNs9qYXvkEnrxRpPXVFQ9Ohxq2PjgIF5kiDY84uO871MgIWdCSDLLvK1NWZya AOuekzG+WDSD/PeP1924AJcmkY9nS9m3yRozQ= MIME-Version: 1.0 Received: by 10.229.79.196 with SMTP id q4mr3509719qck.132.1304045477626; Thu, 28 Apr 2011 19:51:17 -0700 (PDT) Received: by 10.229.98.195 with HTTP; Thu, 28 Apr 2011 19:51:17 -0700 (PDT) In-Reply-To: <20110428032347.GA15220@icarus.home.lan> References: <20110427125736.GA1977@icarus.home.lan> <4DB8381B.4030408@FreeBSD.org> <20110428032347.GA15220@icarus.home.lan> Date: Thu, 28 Apr 2011 19:51:17 -0700 Message-ID: From: Rumen Telbizov To: Jeremy Chadwick Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Denny Schierz , Alexander Motin , FreeBSD Stable Subject: Re: MPS driver: force bus rescan after remove SAS cable 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, 29 Apr 2011 02:51:19 -0000 Jeremy: > I don't mean to sound critical, but why do you guys do this? The reason > I ask: on actual production filers (read: NetApps), you don't go yanking > out the FC cable between the HBA and the NA and expect everything to "be > happy" afterwards. Most SAN administrators tend to reboot an appliance > when doing this kind of work -- because this kind of work is considered > maintenance. > I have just realized that I didn't respond with what I intended to. Sorry about that. What I meant to add to the discussion yesterday was that ejecting a single disk and plugging it back in does not cause (at least in my case) the block device to re-appear again. I haven't tried unplugging the whole cable/backplane. Don't see the point indeed. > I understand what you folks are reporting is a problem. I'm just > wondering why you're complaining about having to reboot a machine with > an HBA in it after doing this kind of *physical* cabling work. My > immediate thought is "I'm really not surprised". I guess some other > people *are* surprised. :-) > Again I missed the point and didn't respond properly. > > Also identify function doesn't work from the OS (no problem > > via the card BIOS). Don't remember having any luck with sg3_util > > package either but worth trying again. > > I don't use SAS myself, but wouldn't the command be "inquiry" and not > "identify"? "identify" is for ATA (specifically SATA via CAM), while > "inquiry" is for SCSI. Where SAS fits into this is unknown to me. Well I have SATA disks visible as /dev/da* . From camcontrol(8): inquiry Send a SCSI inquiry command (0x12) to a device. By default, camcontrol will print out the standard inquiry data, device serial number, and transfer rate information. The user can specify that only certain types of inquiry data be printed: Example: # camcontrol inquiry /dev/da47 pass48: Fixed Direct Access SCSI-5 device pass48: Serial Number WD-WMAUR0408496 pass48: 300.000MB/s transfers, Command Queueing Enabled It's a SATA disk in this case attached to SAS/SATA backplane and SAS2008 HBA chip (9211-8i) What I need is a way to light on the fault led on the disk that I want to identify (point to) This is usually what I need when I send a DC technician to replace a disk. For which I though I should be using: identify Send a ATA identify command (0xec) to a device. >From my experience SAS or SATA disks - I always get those as /dev/da* disks. It's a combo controller and backplane. So which is the correct way of identifying a disk? > On a related note: recently LSI released version 9.0 of their firmware > > for SAS2008 and I found it fixes certain performance problems with > > SuperMicro backplanes! > > In another thread, or a PR, if you could provide those technical details > that would be beneficial. There are a very large number of FreeBSD > users who use Supermicro server-class hardware, and I'm certain they > would be interested in a full disclosure. > What I meant was that it fixes problems not specific to FreeBSD. I don't have much more to add and don't think that a separate thread is required for this here (since it's not directly FreeBSD specific) but in a nutshell the issue that I was experiencing was that when I connect a 9211-8i to a 6Gbit/s SAS expander the performance/bandwidth was terrible and I couldn't get more than 200 MB/s of off the disk array in sequential access even when the disks were in a simple raid0 setup. With the release of version 9.0 everything is pretty good and am able to achieve gigabyte speeds in sequential access. Another bug they fixed which wasn't too bad but still ... is that each lane in a multilane cable (8087) to the backplane was reported as a separate connection so all the disks were visible 4 times (via 4 different expanders) even though there's only 1 multilane cable connected to 1 backplane. Again both those are fixed in 9.0. I hope this helps. Cheers, -- Rumen Telbizov http://telbizov.com From owner-freebsd-stable@FreeBSD.ORG Fri Apr 29 02:51:29 2011 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 E6252106564A for ; Fri, 29 Apr 2011 02:51:28 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (unknown [IPv6:2001:44b8:7c07:5581:266:e1ff:fe0c:8f16]) by mx1.freebsd.org (Postfix) with ESMTP id 38D738FC08 for ; Fri, 29 Apr 2011 02:51:26 +0000 (UTC) Received: from ur.gsoft.com.au (Ur.gsoft.com.au [203.31.81.44]) (authenticated bits=0) by cain.gsoft.com.au (8.14.4/8.14.3) with ESMTP id p3T2pIkY007621 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 29 Apr 2011 12:21:19 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: "Daniel O'Connor" In-Reply-To: <20110429010829.GA36744@icarus.home.lan> Date: Fri, 29 Apr 2011 12:21:18 +0930 Content-Transfer-Encoding: quoted-printable Message-Id: References: <537A8F4F-A302-40F9-92DF-403388D99B4B@gsoft.com.au> <20110428195601.GA31807@icarus.home.lan> <20110429010829.GA36744@icarus.home.lan> To: Jeremy Chadwick X-Mailer: Apple Mail (2.1084) X-Spam-Score: -2.51 () ALL_TRUSTED,BAYES_00,T_RP_MATCHES_RCVD X-Scanned-By: MIMEDefang 2.67 on 203.31.81.10 Cc: freebsd-stable List Subject: Re: ZFS vs OSX Time Machine 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, 29 Apr 2011 02:51:29 -0000 On 29/04/2011, at 10:38, Jeremy Chadwick wrote: > Could you please provide output from "zfs get all poolname"? Myself = and > others would like to review what settings you're using on the > filesystem. If it's a separate filesystem (e.g. pool/foobar), please > also provide output from "zfs get all pool". [midget 11:51] ~ >zfs get all tank NAME PROPERTY VALUE SOURCE tank type filesystem - tank creation Thu Sep 24 11:22 2009 - tank used 2.58T - tank available 981G - tank referenced 44.7K - tank compressratio 1.00x - tank mounted yes - tank quota none default tank reservation none default tank recordsize 128K default tank mountpoint /tank default tank sharenfs off default tank checksum on default tank compression off default tank atime on default tank devices on default tank exec on default tank setuid on default tank readonly off default tank jailed off default tank snapdir hidden default tank aclmode groupmask default tank aclinherit restricted default tank canmount on default tank shareiscsi off default tank xattr off temporary tank copies 1 default tank version 3 - tank utf8only off - tank normalization none - tank casesensitivity sensitive - tank vscan off default tank nbmand off default tank sharesmb off default tank refquota none default tank refreservation none default tank primarycache all default tank secondarycache all default tank usedbysnapshots 0 - tank usedbydataset 44.7K - tank usedbychildren 2.58T - tank usedbyrefreservation 0 - [midget 11:51] ~ >zfs get all tank/TimeMachine =20 NAME PROPERTY VALUE SOURCE tank/TimeMachine type filesystem - tank/TimeMachine creation Sat May 8 10:59 2010 - tank/TimeMachine used 555G - tank/TimeMachine available 45.3G - tank/TimeMachine referenced 555G - tank/TimeMachine compressratio 1.00x - tank/TimeMachine mounted yes - tank/TimeMachine quota 600G local tank/TimeMachine reservation none default tank/TimeMachine recordsize 128K default tank/TimeMachine mountpoint /tank/TimeMachine default tank/TimeMachine sharenfs off default tank/TimeMachine checksum on default tank/TimeMachine compression off default tank/TimeMachine atime on default tank/TimeMachine devices on default tank/TimeMachine exec on default tank/TimeMachine setuid on default tank/TimeMachine readonly off default tank/TimeMachine jailed off default tank/TimeMachine snapdir hidden default tank/TimeMachine aclmode groupmask default tank/TimeMachine aclinherit restricted default tank/TimeMachine canmount on default tank/TimeMachine shareiscsi off default tank/TimeMachine xattr off temporary tank/TimeMachine copies 1 default tank/TimeMachine version 3 - tank/TimeMachine utf8only off - tank/TimeMachine normalization none - tank/TimeMachine casesensitivity sensitive - tank/TimeMachine vscan off default tank/TimeMachine nbmand off default tank/TimeMachine sharesmb off default tank/TimeMachine refquota none default tank/TimeMachine refreservation none default tank/TimeMachine primarycache all default tank/TimeMachine secondarycache all default tank/TimeMachine usedbysnapshots 0 - tank/TimeMachine usedbydataset 555G - tank/TimeMachine usedbychildren 0 - tank/TimeMachine usedbyrefreservation 0 - >> The OSX box is connected via an Airport Express (11n). >=20 > Can you connect something to it via Ethernet and attempt an FTP = transfer > (both PUT (store on server) and GET (retrieve from server)) from a > client on the wired network? Make sure whatever you're PUT'ing and > GET'ing are using the ZFS filesystem. Don't forget "binary" mode too. I'll try that tonight. > You should see very good performance on files that are already in the > ARC. So for example, pick a 500MB ISO file that hasn't been accessed > previously (thus isn't in the ARC). GET'ing it should result in a lot > of disk I/O (zpool iostat -v 1). But a subsequent GET should show = very > little disk I/O, as all the data should be coming from memory (ARC). = A > PUT would test write. >=20 > Basically what I'm trying to figure out here is if the network layer = is > somehow causing these problems for you or not. Wireless is simply too > unreliable/too flippant in packet loss and latency to be a good medium > to test throughput of a filesystem. Period. I'll try but I would expect backup over wireless to cause less of a = performance degradation of other ZFS consumers because the backup is = being throttled by it. I am not concerned about the time it takes to do a time machine backup = since it happens in the background and in any case I believe OSX makes = it go slow to not hammer the machine being backed up. > Be aware there are all sorts of caveats/complexities with iSCSI on > FreeBSD. There are past threads on -stable and -fs talking about them > in great detail. I personally wouldn't go this route. OK. It also seems that OSX can't see iSCSI disks out of the box so I suspect = I would not be able to do a bare metal restore from one which greatly = limits the desirability of it. > Why can't OS X use CIFS? It has the ability to mount a SMB = filesystem, > right? Is there some reason you can't mount that, then tell TM to = write > its backups to /mountedcifs? I'm not sure.. You need to set a flag to allow it to backup to a "non = standard" (ie non TimeCapsule) AFS share. In any case I would still have to create a HFS+ volume on the CIFS = partition so I'm not sure it would make any practical difference (vs = AFP). >>> (please don't; it would be more useful if it could be kept up in = case >>> folks want to do analysis of it). >>=20 >> I think performance does improve after a reboot :( >=20 > This could be a memory performance or fragmentation problem then. = Gosh > it's been a long time since I've read about that. Some FreeBSD folks > knew of such, and I think someone came up with a patch for it, but I'm > not sure. I wish I could remember the name of the developer who was > talking about it. Artem Belevich maybe? OK.. It does act as a desktop box too which I imagine won't help any.. > The other problem a user had pertaining to ZFS and memory performance > was even more odd, but was eventually tracked down. He had installed > two DIMMs in his machine (making a total of 4) and suddenly memory > performance was abysmal. Remove the DIMMs, performance restored. Put > the two removed DIMMs in (previous working ones out), performance was Huh interesting :) > fine. If I remember right, the issue turned out to be a bug in the > BIOS, and a BIOS upgrade from Intel (it was an Intel motherboard) = fixed > it. Intel is one of the only companies that releases *very* concise = and > decent changelogs for their BIOSes, which is wonderful. Yes, most are opaque beyond belief.. Supermicro also label them MMDDYY just to minimise utility too.. >> although free does go down very low (~250MB) at times. >=20 > This is normal. The ZFS ARC has most of your memory (shown as "Wired" > in the above top output). If something needs memory, parts of the ARC > will be released/freed given memory pressure. OK. > I will note something, however: your ARC max is set to 3072MB, yet = Wired > is around 4143MB. Do you have something running on this box that = takes > up a lot of RAM? mysqld, etc..? I'm trying to account for the "extra > gigabyte" in Wired. "top -o res" might help here, but we'd need to = see > the process list. It runs X and so on which probably soak up a fair bit. It runs a very lightly loaded postgres as well. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C From owner-freebsd-stable@FreeBSD.ORG Fri Apr 29 03:52:50 2011 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 7D5C2106564A for ; Fri, 29 Apr 2011 03:52:50 +0000 (UTC) (envelope-from jamesbrandongooch@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 1303A8FC08 for ; Fri, 29 Apr 2011 03:52:49 +0000 (UTC) Received: by wyf23 with SMTP id 23so3348255wyf.13 for ; Thu, 28 Apr 2011 20:52:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=PaieVrqzYMptYRZMqAGEkcP7RYjA3ppIxpcs5u3CITA=; b=gdPoLtWODBm2tXjXtVExnYswbmS+NaL12dAUlENbj6e+aVJDEzsOqvejFSMU8cGDx0 +kuhdvLw4q4Vh7LftkDU45yFq2sVe6cS/PGU5IMSUkm6Wb40wCoeEYXqdTqbp+ToRWT2 Z9lzBONutcQSIS/UcieQOSLkIWAhrB004IbA4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=gVePL0s+9rINQlqWIaRoMQq8ITBQi0vaQWlqNibyxp94WYGfQRoxjIYBKYd0AwJ6gg 48pUJHCcB2fEtPjUJUmLga8ocsGY6usI8ce5dpc3+MJz+VuaGE2hKuTxXveZHZIri0CY 2Tw6+DMyKy/h3ZN97PscNWO+gsMb9BFzIUoh0= MIME-Version: 1.0 Received: by 10.216.188.20 with SMTP id z20mr823456wem.66.1304047384099; Thu, 28 Apr 2011 20:23:04 -0700 (PDT) Received: by 10.216.17.213 with HTTP; Thu, 28 Apr 2011 20:23:04 -0700 (PDT) In-Reply-To: References: Date: Thu, 28 Apr 2011 22:23:04 -0500 Message-ID: From: Brandon Gooch To: Helmut Schneider Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-stable@freebsd.org Subject: Re: panic, but /var/crash ist empty 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, 29 Apr 2011 03:52:50 -0000 On Wed, Apr 27, 2011 at 1:44 PM, Helmut Schneider wrote: > Hi, > > running 8.2-RELEASE-p1 within VMWare ESXi 4.1-u1 I want to use raw > devices as hard disks. I create the devices using this link: > > http://www.mattiasholm.com/node/33 > > I tried 3 different hard drives (Seagate 2x80GB and 1x400GB SATA2) > which are fine on a physical machine. I also ran Seatool many hours on > all of them without errors. > > I can partiton the disks and create a few files/directories on it. But > as soon as I copy a larger number of files to those disks (tried with > MBR and GPT) the VM reboots *instantly* (I tried cp, dump/restore and > rsync). No "Rebooting within 15 seconds", just *snap*. I think I can > see an panic but I'm not sure, it's too fast. > > (as far as I can see most of the times the data on the first UFS slice > (and only the first UFS slice!) of the partition gets *severly* > corrupted, most of the time all that is left are a few files within > lost+found. Sometimes all the labels are gone but are recoverable using > bsdlabel -R) > > The problem is that /var/crash remains empty. > > What can I do to create a backtrace to open a PR? > > Thanks, Helmut > Hi Helmut, To get a backtrace from the crash (or drop to the debugger), you'll need to compile a kernel with at least a couple of options defined. These two: options KDB options DDB ...will allow you to work with the debugger on the console after a crash. Further, with the option KDB_TRACE in the kernel config, you'll get a backtrace printed automatically when the kernel panicsb. Here are a couple of excellent documents to read to get you started: http://www.freebsd.org/doc/en/books/handbook/kernelconfig-building.html http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html Kernel debug options: http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-options.html From owner-freebsd-stable@FreeBSD.ORG Fri Apr 29 05:36:17 2011 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 0079D106566B for ; Fri, 29 Apr 2011 05:36:17 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 7711F8FC14 for ; Fri, 29 Apr 2011 05:36:16 +0000 (UTC) Received: by bwz12 with SMTP id 12so4087383bwz.13 for ; Thu, 28 Apr 2011 22:36:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=hgLs9DYglMteHdBfhPsC3IMrQw9VDu7FyYY1QJgfRG8=; b=kxpcLwtlQnr2ukDr1+T8EVT0MhomvdA1bgNGMPJZzWQAdEvvGX32OG0PphBwCjekuX iWnNAMJ/Q1eV3BaW5DAT8oRD3686rh4BQvWud5cJpBOk7HHtka4Q/f85bzODXd9EBhCE aSsWbf38pdZFcdM2nBUXauE2FLKorfv9JXHOE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=EnAHq/oy26TyWpgmT/TRPlIVFERZWFQkyRENq6QhhjjGCqkXTsW8Vhv4/crP0893hQ 4RyOC9NUfSFJBPvGB1XECcLBk2usFw6Gg4UmqwQhE7rWKfBONzMMu0n42ifmpOnOaugz qFn/Ynsa4N5dm9YXNkZgH5M3A2QQhIXkiQIeQ= Received: by 10.204.29.18 with SMTP id o18mr2183536bkc.12.1304055375311; Thu, 28 Apr 2011 22:36:15 -0700 (PDT) Received: from mavbook2.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id y22sm1396285bku.8.2011.04.28.22.36.13 (version=SSLv3 cipher=OTHER); Thu, 28 Apr 2011 22:36:14 -0700 (PDT) Sender: Alexander Motin Message-ID: <4DBA4E40.4000404@FreeBSD.org> Date: Fri, 29 Apr 2011 08:36:00 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.23 (X11/20091212) MIME-Version: 1.0 To: Rumen Telbizov References: <20110427125736.GA1977@icarus.home.lan> <4DB8381B.4030408@FreeBSD.org> <20110428032347.GA15220@icarus.home.lan> In-Reply-To: X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Denny Schierz , FreeBSD Stable , Jeremy Chadwick Subject: Re: MPS driver: force bus rescan after remove SAS cable 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, 29 Apr 2011 05:36:17 -0000 Rumen Telbizov wrote: > > Also identify function doesn't work from the OS (no problem > > via the card BIOS). Don't remember having any luck with sg3_util > > package either but worth trying again. > > I don't use SAS myself, but wouldn't the command be "inquiry" and not > "identify"? "identify" is for ATA (specifically SATA via CAM), while > "inquiry" is for SCSI. Where SAS fits into this is unknown to me. > > > Well I have SATA disks visible as /dev/da* . From camcontrol(8): > > inquiry Send a SCSI inquiry command (0x12) to a device. By > default, > camcontrol will print out the standard inquiry data, device > serial number, and transfer rate information. The user can > specify that only certain types of inquiry data be printed: > > Example: > > # camcontrol inquiry /dev/da47 > pass48: Fixed Direct Access SCSI-5 device > pass48: Serial Number WD-WMAUR0408496 > pass48: 300.000MB/s transfers, Command Queueing Enabled > > It's a SATA disk in this case attached to SAS/SATA backplane and SAS2008 > HBA chip (9211-8i) > What I need is a way to light on the fault led on the disk that I want > to identify (point to) > This is usually what I need when I send a DC technician to replace a > disk. For which I though I should > be using: > > identify Send a ATA identify command (0xec) to a device. > > From my experience SAS or SATA disks - I always get those as /dev/da* > disks. It's a combo controller and backplane. > So which is the correct way of identifying a disk? `camcontrol identify` means sending ATA IDENTIFY DEVICE command to the ATA device. That command is roughly the analogue of the SCSI INQUIRY command. It has nothing to do with LEDs. LEDs most likely controlled via ses device or some alike management thing. The fact that you see ATA device as daX is just means that your SAS controller does protocol translation on-the-fly. It allows you to communicate with disk using SCSI commands _instead_ of ATA. -- Alexander Motin From owner-freebsd-stable@FreeBSD.ORG Fri Apr 29 06:10:56 2011 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 08D7D106566B for ; Fri, 29 Apr 2011 06:10:56 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 51A8E8FC12 for ; Fri, 29 Apr 2011 06:10:55 +0000 (UTC) Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id IAA13752; Fri, 29 Apr 2011 08:59:40 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost.topspin.kiev.ua ([127.0.0.1]) by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1QFgjr-000F70-Ss; Fri, 29 Apr 2011 08:59:39 +0300 Message-ID: <4DBA53CB.4090403@FreeBSD.org> Date: Fri, 29 Apr 2011 08:59:39 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110308 Lightning/1.0b2 Thunderbird/3.1.9 MIME-Version: 1.0 To: current@FreeBSD.org, stable@FreeBSD.org X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Fwd: SNDCTL_DSP_GETIPTR implementation 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, 29 Apr 2011 06:10:56 -0000 I intend to commit the following change soon and MFC it after a short period of time. Please test it if you use multimedia applications, both native and Linux, especially if they deal with audio recording/capture. Thank you. -------- Original Message -------- Message-ID: <4DB6F7BA.4070808@FreeBSD.org> Date: Tue, 26 Apr 2011 19:50:02 +0300 From: Andriy Gapon To: multimedia@freebsd.org Subject: SNDCTL_DSP_GETIPTR implementation Guys, I reading this http://manuals.opensound.com/developer/SNDCTL_DSP_GETOPTR.html It says: "In mmap mode (only) the ptr field tells the location where the next sample will be recorded." In my opinion that means that we have a mistake in our code and the following patch should be applied. But I am not sufficiently familiar with this code. --- a/sys/dev/sound/pcm/dsp.c +++ b/sys/dev/sound/pcm/dsp.c @@ -1655,7 +1655,7 @@ dsp_ioctl /* XXX abusive DMA update: chn_rdupdate(rdch); */ a->bytes = sndbuf_gettotal(bs); a->blocks = sndbuf_getblocks(bs) - rdch->blocks; - a->ptr = sndbuf_getreadyptr(bs); + a->ptr = sndbuf_getfreeptr(bs); rdch->blocks = sndbuf_getblocks(bs); CHN_UNLOCK(rdch); } else P.S. leading (indenting) whitespace in this file is a mess. -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Fri Apr 29 06:14:58 2011 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 D0694106566B; Fri, 29 Apr 2011 06:14:58 +0000 (UTC) (envelope-from hselasky@freebsd.org) Received: from swip.net (mailfe05.c2i.net [212.247.154.130]) by mx1.freebsd.org (Postfix) with ESMTP id EEACD8FC17; Fri, 29 Apr 2011 06:14:57 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.1 cv=upTJuTb3ngPPUUVVSPoyO7jwIWz3rzPtkQxI490l6Ks= c=1 sm=1 a=SvYTsOw2Z4kA:10 a=mt-kpIeAPloA:10 a=dBRESv0yCI8A:10 a=Q9fys5e9bTEA:10 a=CL8lFSKtTFcA:10 a=i9M/sDlu2rpZ9XS819oYzg==:17 a=QycZ5dHgAAAA:8 a=6I5d2MoRAAAA:8 a=2fdRn4K4OjleMMEsELcA:9 a=Rus02wZm98K_IfYCS1QA:7 a=PUjeQqilurYA:10 a=K4TQeqUVedYA:10 a=i9M/sDlu2rpZ9XS819oYzg==:117 Received: from [188.126.198.129] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe05.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 118929950; Fri, 29 Apr 2011 08:04:54 +0200 Received-SPF: softfail receiver=mailfe05.swip.net; client-ip=188.126.198.129; envelope-from=hselasky@freebsd.org From: Hans Petter Selasky To: Andrew Thompson Date: Fri, 29 Apr 2011 08:03:45 +0200 User-Agent: KMail/1.13.5 (FreeBSD/8.2-STABLE; KDE/4.4.5; amd64; ; ) References: <20110428233030.GA35428@icarus.home.lan> In-Reply-To: X-Face: *nPdTl_}RuAI6^PVpA02T?$%Xa^>@hE0uyUIoiha$pC:9TVgl.Oq,NwSZ4V" =?iso-8859-1?q?=7CLR=2E+tj=7Dg5=0A=09=25V?=,x^qOs~mnU3]Gn; cQLv&.N>TrxmSFf+p6(30a/{)KUU!s}w\IhQBj}[g}bj0I3^glmC( =?iso-8859-1?q?=0A=09=3AAuzV9=3A=2EhESm-x4h240C=609=3Dw?= MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201104290803.45501.hselasky@freebsd.org> Cc: "arm@freebsd.org" , "stable@freebsd.org" , FreeBSD Tinderbox , Jeremy Chadwick Subject: Re: [releng_8 tinderbox] failure on arm/arm 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, 29 Apr 2011 06:14:58 -0000 On Friday 29 April 2011 01:51:24 Andrew Thompson wrote: > On 29 April 2011 11:30, Jeremy Chadwick wrote: > CC'ing hselasky and thompsa for review of this. > > For failure logs (so far ia64 and arm), please see end of this page: > > http://lists.freebsd.org/pipermail/freebsd-stable/2011-April/thread.html > > Commit question is revision 1.6.2.2 to RELENG_8: > > http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/usbdump/usbdump.c > > Relevant code bits: > > I merged the missing rev a few hours ago, > http://svnweb.freebsd.org/base?view=revision&revision=221185 Thank you Andrew! --HPS From owner-freebsd-stable@FreeBSD.ORG Fri Apr 29 06:52:11 2011 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 6457A106566B for ; Fri, 29 Apr 2011 06:52:11 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe08.c2i.net [212.247.154.226]) by mx1.freebsd.org (Postfix) with ESMTP id E5C358FC16 for ; Fri, 29 Apr 2011 06:52:10 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.1 cv=6QwXiDozn7Gnsf2tGidwH+ndAwLlGixx7JAIKZICKmI= c=1 sm=1 a=SvYTsOw2Z4kA:10 a=W04OnpUjfygA:10 a=WQU8e4WWZSUA:10 a=8nJEP1OIZ-IA:10 a=CL8lFSKtTFcA:10 a=i9M/sDlu2rpZ9XS819oYzg==:17 a=VCCo5Esqx7zTeV27Yt4A:9 a=wPNLvfGTeEIA:10 a=i9M/sDlu2rpZ9XS819oYzg==:117 Received: from [188.126.198.129] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe08.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 120018688; Fri, 29 Apr 2011 08:42:07 +0200 From: Hans Petter Selasky To: freebsd-current@freebsd.org Date: Fri, 29 Apr 2011 08:40:58 +0200 User-Agent: KMail/1.13.5 (FreeBSD/8.2-STABLE; KDE/4.4.5; amd64; ; ) References: <4DBA53CB.4090403@FreeBSD.org> In-Reply-To: <4DBA53CB.4090403@FreeBSD.org> X-Face: *nPdTl_}RuAI6^PVpA02T?$%Xa^>@hE0uyUIoiha$pC:9TVgl.Oq,NwSZ4V" =?iso-8859-1?q?=7CLR=2E+tj=7Dg5=0A=09=25V?=,x^qOs~mnU3]Gn; cQLv&.N>TrxmSFf+p6(30a/{)KUU!s}w\IhQBj}[g}bj0I3^glmC( =?iso-8859-1?q?=0A=09=3AAuzV9=3A=2EhESm-x4h240C=609=3Dw?= MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201104290840.58511.hselasky@c2i.net> Cc: stable@freebsd.org, current@freebsd.org, Andriy Gapon Subject: Re: Fwd: SNDCTL_DSP_GETIPTR implementation 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, 29 Apr 2011 06:52:11 -0000 On Friday 29 April 2011 07:59:39 Andriy Gapon wrote: > I intend to commit the following change soon and MFC it after a short > period of time. Please test it if you use multimedia applications, both > native and Linux, especially if they deal with audio recording/capture. > > Thank you. Seems to work with AMD64 8-stable. --HPS From owner-freebsd-stable@FreeBSD.ORG Fri Apr 29 08:06:35 2011 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 73CCE1065672; Fri, 29 Apr 2011 08:06:35 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.freebsd.org (Postfix) with ESMTP id F0C608FC20; Fri, 29 Apr 2011 08:06:34 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.14.4/8.14.4) with ESMTP id p3T7pLc0029344; Fri, 29 Apr 2011 11:51:21 +0400 (MSD) (envelope-from marck@rinet.ru) Date: Fri, 29 Apr 2011 11:51:21 +0400 (MSD) From: Dmitry Morozovsky To: ken@FreeBSD.org Message-ID: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.6 (woozle.rinet.ru [0.0.0.0]); Fri, 29 Apr 2011 11:51:21 +0400 (MSD) Cc: freebsd-stable@FreeBSD.org Subject: mps driver instability under stable/8 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, 29 Apr 2011 08:06:35 -0000 Dear Ken, I have SuperMicro Server with mps driver you managed, with 24 SATA disks under SAS x36 expander with large ZFS Sometimes, under random disk load such as daily find, it lost all its devices: [-- MARK -- Fri Apr 29 03:00:00 2011] mps0: IOC Fault 0x40005900, Resetting^M (pass20:mps0:0:22:0): SCSI command timeout on device handle 0x0020 SMID 442^M mps0: IOC Fault 0x40001500, Resetting^M (da19:mps0:0:21:0): SCSI command timeout on device handle 0x001f SMID 172^M (da19:mps0:0:21:0): SCSI command timeout on device handle 0x001f SMID 511^M (da20:mps0:0:20:0): SCSI command timeout on device handle 0x001e SMID 240^M .. (da4:mps0:0:0:0): SCSI command timeout on device handle 0x000a SMID 844^M (da22:mps0:0:23:0): SCSI command timeout on device handle 0x0021 SMID 713^M (da18:mps0:0:22:0): SCSI command timeout on device handle 0x0020 SMID 603^M and hangs there forever (in zio state). I've prepared debugging kernel with DDB and would be glad to help catch the situation. Thanks! -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: marck@FreeBSD.org ] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ From owner-freebsd-stable@FreeBSD.ORG Fri Apr 29 09:59:35 2011 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 61ABD1065678 for ; Fri, 29 Apr 2011 09:59:35 +0000 (UTC) (envelope-from dgeo@centrale-marseille.fr) Received: from melo.ec-m.fr (melo.ec-m.fr [147.94.19.139]) by mx1.freebsd.org (Postfix) with ESMTP id 1A72C8FC21 for ; Fri, 29 Apr 2011 09:59:34 +0000 (UTC) Received: from amavis4.serv.int (amavis4.serv.int [10.3.0.48]) by melo.ec-m.fr (GrosseBox 1743 XXL) with ESMTP id 58EF6AC8A7; Fri, 29 Apr 2011 11:40:06 +0200 (CEST) X-Virus-Scanned: amavisd-new at centrale-marseille.fr Received: from melo.ec-m.fr ([10.3.0.13]) by amavis4.serv.int (amavis4.serv.int [10.3.0.48]) (amavisd-new, port 10024) with LMTP id maPyNG-mkbl9; Fri, 29 Apr 2011 11:40:06 +0200 (CEST) Received: from dgeo.sysadm.ec-m.fr (dgeo.sysadm.ec-m.fr [147.94.19.169]) (Authenticated sender: dgeo) by melo.ec-m.fr (GrosseBox 1743 XXL) with ESMTPSA id 0DD86AC89A; Fri, 29 Apr 2011 11:40:06 +0200 (CEST) Message-ID: <4DBA8775.2030606@centrale-marseille.fr> Date: Fri, 29 Apr 2011 11:40:05 +0200 From: geoffroy desvernay User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; fr-FR; rv:1.9.2.15) Gecko/20110310 Lightning/1.0b2 Thunderbird/3.1.9 MIME-Version: 1.0 To: bug-followup@FreeBSD.org, andrew@ugh.net.au, freebsd-stable@FreeBSD.org X-Enigmail-Version: 1.1.2 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig3CBB833B104BECA81E87E6AE" Cc: Subject: Re: bin/136073: recent nscd(8) changes cause client processes to die with SIGPIPE 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, 29 Apr 2011 09:59:35 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig3CBB833B104BECA81E87E6AE Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable This change is not so recent now... But I'm still experiencing this bug with 8.2p1 :( This bug happens with nss_ldap-1.265_6 and nss-pam-ldapd, using one or more ldap:// and|or ldaps:// servers, and cache enabled in nsswitch.conf.= Some symptoms: # id dgeo; echo $? 141 cron jobs are logged as executed but are not ! I may test any patch or ? --=20 *geoffroy desvernay* C.R.I - Administration syst=E8mes et r=E9seaux Ecole Centrale de Marseille --------------enig3CBB833B104BECA81E87E6AE Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJNuod1AAoJEC0NWrh8JT1SBE4H/1JmXDLdI/HGI8GxLsssd3vh i4mnz0+iNnzAWVH1lFJtwQeJmZx0Q33U1axP7S3ONqdojAMV0k7sakVYPquBy/10 ikQDNG4XWLNfZxSQXVc9Y9t/TXCLxs96zR7ERa9DrAfx0MlqmctX4wv8Xu1QBM/c 77Gb75Ml/xUpedbcpeMOonOHTpfOeAQrj5vwPi0EIZjwoZMym1GDHHsVabmCiDtp rvY2xZr6+BBYep76cQ9io+K8FfheQMBLhrPED8R8cbteEgYfs4l1Tk4sbVPthWhG iC/5IAJHRdfg6bMUOo1Ggzex9hHvmMXlIINWk11DvNe892nSMP4nLEqcPNT4uDA= =c9iM -----END PGP SIGNATURE----- --------------enig3CBB833B104BECA81E87E6AE-- From owner-freebsd-stable@FreeBSD.ORG Fri Apr 29 12:54:14 2011 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 D01531065670 for ; Fri, 29 Apr 2011 12:54:14 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 875C38FC1E for ; Fri, 29 Apr 2011 12:54:13 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1QFnCy-0007In-Q4 for freebsd-stable@freebsd.org; Fri, 29 Apr 2011 14:54:08 +0200 Received: from p57915789.dip.t-dialin.net ([87.145.87.137]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 29 Apr 2011 14:54:08 +0200 Received: from jumper99 by p57915789.dip.t-dialin.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 29 Apr 2011 14:54:08 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: "Helmut Schneider" Date: Fri, 29 Apr 2011 12:53:56 +0000 (UTC) Lines: 36 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: p57915789.dip.t-dialin.net User-Agent: XanaNews/1.19.1.320 X-Ref: news.gmane.org ~XNS:0000016D X-Antivirus: avast! (VPS 110429-0, 29.04.2011), Outbound message X-Antivirus-Status: Clean Subject: Re: panic, but /var/crash ist empty 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, 29 Apr 2011 12:54:14 -0000 Brandon Gooch wrote: > On Wed, Apr 27, 2011 at 1:44 PM, Helmut Schneider > wrote: > > What can I do to create a backtrace to open a PR? > > To get a backtrace from the crash (or drop to the debugger), you'll > need to compile a kernel with at least a couple of options defined. > These two: > > options KDB > options DDB > > ...will allow you to work with the debugger on the console after a > crash. > > Further, with the option KDB_TRACE in the kernel config, you'll get a > backtrace printed automatically when the kernel panicsb. > > Here are a couple of excellent documents to read to get you started: > > http://www.freebsd.org/doc/en/books/handbook/kernelconfig-building.html > http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html > > Kernel debug options: > > http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-options.html Thanks for the links, I meanwhile was able to create the bt and the PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=156691 Helmut From owner-freebsd-stable@FreeBSD.ORG Fri Apr 29 14:24:36 2011 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 232311065673 for ; Fri, 29 Apr 2011 14:24:36 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id E9E918FC17 for ; Fri, 29 Apr 2011 14:24:35 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 84C9646B51; Fri, 29 Apr 2011 10:24:35 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id EDBF68A01B; Fri, 29 Apr 2011 10:24:34 -0400 (EDT) From: John Baldwin To: Jeremy Chadwick Date: Fri, 29 Apr 2011 09:25:03 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110325; KDE/4.5.5; amd64; ; ) References: <537A8F4F-A302-40F9-92DF-403388D99B4B@gsoft.com.au> <201104281727.04425.jhb@freebsd.org> <20110428215954.GA34030@icarus.home.lan> In-Reply-To: <20110428215954.GA34030@icarus.home.lan> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201104290925.03607.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Fri, 29 Apr 2011 10:24:35 -0400 (EDT) Cc: freebsd-stable@freebsd.org Subject: Re: ZFS vs OSX Time Machine 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, 29 Apr 2011 14:24:36 -0000 On Thursday, April 28, 2011 5:59:54 pm Jeremy Chadwick wrote: > I've seen cases where entries in /boot/loader.conf throw parser errors > during loader(8) when quotes aren't used. The man page denotes that > quotes are required, which doesn't appear to be true? Possibly the > parser only throws errors if non-numeric/non-integer values (e.g. > strings) are specified without quotes. > > It's interesting that in the BUGS section of the man page the syntax > shown for hw.ata.ata_dma=0 also ""violates"" the ""required"" syntax. Yes, it's confusing. My gut instinct is that quotes are only required if the value contains whitespace. I've certainly used 'autoboot_delay=NO' without quotes before. I just did some tests and it looks like quotes are only required for values that contain whitespace, so foo=bar bar=42G baz="foo bar" are fine, but baz=foo bar will fail. This is similar to normal shell syntax for assigning to variables. -- John Baldwin From owner-freebsd-stable@FreeBSD.ORG Fri Apr 29 15:01:41 2011 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 2DF06106566C; Fri, 29 Apr 2011 15:01:41 +0000 (UTC) (envelope-from roberto@keltia.freenix.fr) Received: from keltia.net (centre.keltia.net [IPv6:2a01:240:fe5c::41]) by mx1.freebsd.org (Postfix) with ESMTP id D4ED68FC13; Fri, 29 Apr 2011 15:01:40 +0000 (UTC) Received: from roberto-al.eurocontrol.fr (aran.keltia.net [88.191.250.24]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: roberto) by keltia.net (Postfix/TLS) with ESMTPSA id 164C4EDE5; Fri, 29 Apr 2011 17:01:36 +0200 (CEST) Date: Fri, 29 Apr 2011 17:01:34 +0200 From: Ollivier Robert To: freebsd-stable@freebsd.org, "freebsd-hardware@freebsd.org" Message-ID: <20110429150134.GB71582@roberto-al.eurocontrol.fr> References: <52A7DCCC-97EB-4C87-9AE6-95C26D0DD241@alogis.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <52A7DCCC-97EB-4C87-9AE6-95C26D0DD241@alogis.com> X-Operating-System: MacOS X / Macbook Pro - FreeBSD 7.2 / Dell D820 SMP User-Agent: Mutt/1.5.20 (2009-06-14) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.3 (keltia.net); Fri, 29 Apr 2011 17:01:37 +0200 (CEST) Cc: Subject: Re: FreeBSD and DELL Perc H200 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, 29 Apr 2011 15:01:41 -0000 According to Holger Kipp: > I have to install two production servers from Dell that come with a Perc H 200 controller. > > Disks are not recognized with 8.2-RELEASE :-( > > Any ideas? If this works with 8-stable, where can I download an ISO Image? I can suggest reading this http://www.keltia.net/howtos/freebsd-dedibox Should be applicable to any H200-based machine. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.net In memoriam to Ondine, our 2nd child: http://ondine.keltia.net/ From owner-freebsd-stable@FreeBSD.ORG Fri Apr 29 21:58:53 2011 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 E00C0106564A for ; Fri, 29 Apr 2011 21:58:53 +0000 (UTC) (envelope-from to.my.trociny@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 6BB538FC12 for ; Fri, 29 Apr 2011 21:58:52 +0000 (UTC) Received: by fxm11 with SMTP id 11so3991181fxm.13 for ; Fri, 29 Apr 2011 14:58:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:to:cc:subject:references:x-comment-to :sender:date:in-reply-to:message-id:user-agent:mime-version :content-type; bh=PaGF4rVDuYBzFZtuQgL5e4jQAYPHPzkwB+kPXlGtqyk=; b=QV/EXdbRgKQ3PdgB687teVTUW5ow9IHzIfsXmtyTXiHljkJhx9pLL2gff0oKO2x5kF smIf7jbCWTLdAxv7Jm0g1HbdL7q1gT0YwM/EyhVeXtT6QDXWwqipHpb7CMVdMfJGQnVf ITT1H0BAnw41WrIqduYqEdSdlkvTsPyfAkWCA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:subject:references:x-comment-to:sender:date:in-reply-to :message-id:user-agent:mime-version:content-type; b=OckUH0kpDLiPvybMaR8d52glaA5GdNgo8mrTFIsM/vW35P0VY6SDdhSNntH08AwYis uy7Sp4xkLciatOceJeHayOWkB4YL7o6/lO92RUUWhAimuFSjbWoSxg7v4mBRWJLXzTYi GiZws1F34SSQ4aB2J8Al/h9oDjHn9xB1ESrug= Received: by 10.223.23.212 with SMTP id s20mr843017fab.120.1304114332266; Fri, 29 Apr 2011 14:58:52 -0700 (PDT) Received: from localhost ([95.69.172.154]) by mx.google.com with ESMTPS id 13sm1013220fau.40.2011.04.29.14.58.49 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 29 Apr 2011 14:58:50 -0700 (PDT) From: Mikolaj Golub To: Denny Schierz References: <1301397421.11113.250.camel@pcdenny> <86ipv1ll4f.fsf@kopusha.home.net> <1303905911.4232.86.camel@pcdenny> <861v0nrdkc.fsf@in138.ua3> <1303996942.4232.160.camel@pcdenny> X-Comment-To: Denny Schierz Sender: Mikolaj Golub Date: Sat, 30 Apr 2011 00:58:48 +0300 In-Reply-To: <1303996942.4232.160.camel@pcdenny> (Denny Schierz's message of "Thu, 28 Apr 2011 15:22:22 +0200") Message-ID: <86mxj8lnxj.fsf@kopusha.home.net> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-stable Subject: Re: way for failover zpool (no HAST needed): hastmon 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, 29 Apr 2011 21:58:54 -0000 Oops, just noticed this mail :-) Denny sent me another message privately and I hope I answered his questions but will answer to this message too, in case someone is interested. On Thu, 28 Apr 2011 15:22:22 +0200 Denny Schierz wrote: DS> hi, DS> ok, here we go: I've installed hastmon and both FreeBSD nodes and one on DS> Linux Debian as watchdog: DS> Simple setup: DS> DS> # cat /etc.local/hastmon.conf DS> resource sanip { DS> exec /usr/local/_rbg/bin/san-ip DS> friends iscsihead-m iscsihead-s nos DS> on iscsihead-m { DS> remote tcp4://iscsihead-s DS> priority 0 DS> } DS> on iscsihead-s { DS> remote tcp4://iscsihead-m DS> priority 1 DS> } DS> on linux { DS> remote tcp4://iscsihead-m tcp4://iscsihead-s DS> } DS> } DS> It works only half. DS> The simple script adds/remove an alias for the em0 and for status it DS> does a ping -c 1 to the global ip. After tell every host, what is role DS> is, I get on the primary "state unknown", in the secondary "state run" DS> and watchdog for the Linux host. It is difficult to tell without additional information what happened. It might be that your '/usr/local/_rbg/bin/san-ip status' was returning unknown status. In this case running manually /usr/local/_rbg/bin/san-ip status; echo $? might be helpful. And logs too :-). DS> Than I rebooted the primary, the secondary take over and executed the DS> script. After the primary was reachable again, he doesn't get the DS> secondary role, but init/unknown. DS> The same happens, in the opposite: DS> from Linux: DS> hastmonctl status DS> sanip: DS> role: watchdog DS> exec: /usr/local/_rbg/bin/san-ip DS> remote: DS> tcp4://iscsihead-m (primary/run) DS> tcp4://iscsihead-s (init/unknown) DS> state: run DS> attempts: 0 from 5 DS> complaints: 0 for last 60 sec (threshold 3) DS> heartbeat: 10 sec DS> from iscsihead-s: DS> hastmonctl status DS> sanip: DS> role: init DS> exec: /usr/local/_rbg/bin/san-ip DS> remote: DS> tcp4://iscsihead-m DS> state: unknown DS> attempts: 0 from 5 DS> complaints: 0 for last 60 sec (threshold 3) DS> heartbeat: 10 sec DS> and last from iscsihead-m DS> hastmonctl status DS> sanip: DS> role: primary DS> exec: /usr/local/_rbg/bin/san-ip DS> remote: DS> tcp4://iscsihead-s (disconnected) DS> state: run DS> attempts: 0 from 5 DS> complaints: 0 for last 60 sec (threshold 3) DS> heartbeat: 10 sec DS> If I take a look into the logfile from the iscsihead-m: DS> [sanip] (primary) Remote node acts as init for the resource and not as DS> secondary. DS> [sanip] (primary) Handshake header from tcp4://iscsihead-s has no DS> 'token' field. DS> Do I have missed something? DS> cu denny This is expected behavior. After start hastmon is in init role. You need to setup the role you want manually or via a startup script. This is because you might want different configurations depending on your requirenments: 1) After start the role is set manually by administrator (useful e.g. if you prefer to investigate crashed host before returning it back to cluster). 2) After star the node is switched to secondary automatically (by rc script). If all cluster nodes are configured to be in secondary on startup, and all started simultaneously watchdog will figure out that there is no primary and will send complaints to all secondary nodes. The nodes will be trying to switch to master simultaneously and the node with highest priority will win. 3) One node that has highest priority configures is set on startup always to primary. All others are to secondary. With this configuration if the primary fails, secondary switches to primary, then when the initial primary comes back it becomes primary again automatically. -- Mikolaj Golub From owner-freebsd-stable@FreeBSD.ORG Sat Apr 30 00:17:28 2011 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 EBC27106566C for ; Sat, 30 Apr 2011 00:17:28 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta15.emeryville.ca.mail.comcast.net (qmta15.emeryville.ca.mail.comcast.net [76.96.27.228]) by mx1.freebsd.org (Postfix) with ESMTP id CF6FC8FC13 for ; Sat, 30 Apr 2011 00:17:28 +0000 (UTC) Received: from omta14.emeryville.ca.mail.comcast.net ([76.96.30.60]) by qmta15.emeryville.ca.mail.comcast.net with comcast id dcCH1g0051HpZEsAFcHUDg; Sat, 30 Apr 2011 00:17:28 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta14.emeryville.ca.mail.comcast.net with comcast id dcHS1g01Z1t3BNj8acHTvU; Sat, 30 Apr 2011 00:17:27 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 73E2E9B418; Fri, 29 Apr 2011 17:17:26 -0700 (PDT) Date: Fri, 29 Apr 2011 17:17:26 -0700 From: Jeremy Chadwick To: John Baldwin Message-ID: <20110430001726.GA58981@icarus.home.lan> References: <537A8F4F-A302-40F9-92DF-403388D99B4B@gsoft.com.au> <201104281727.04425.jhb@freebsd.org> <20110428215954.GA34030@icarus.home.lan> <201104290925.03607.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201104290925.03607.jhb@freebsd.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@freebsd.org Subject: Re: ZFS vs OSX Time Machine 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, 30 Apr 2011 00:17:29 -0000 On Fri, Apr 29, 2011 at 09:25:03AM -0400, John Baldwin wrote: > On Thursday, April 28, 2011 5:59:54 pm Jeremy Chadwick wrote: > > I've seen cases where entries in /boot/loader.conf throw parser errors > > during loader(8) when quotes aren't used. The man page denotes that > > quotes are required, which doesn't appear to be true? Possibly the > > parser only throws errors if non-numeric/non-integer values (e.g. > > strings) are specified without quotes. > > > > It's interesting that in the BUGS section of the man page the syntax > > shown for hw.ata.ata_dma=0 also ""violates"" the ""required"" syntax. > > Yes, it's confusing. My gut instinct is that quotes are only required > if the value contains whitespace. I've certainly used > 'autoboot_delay=NO' without quotes before. > > I just did some tests and it looks like quotes are only required for > values that contain whitespace, so > > foo=bar > bar=42G > baz="foo bar" > > are fine, but > > baz=foo bar > > will fail. > > This is similar to normal shell syntax for assigning to variables. As usual, thanks for the time you spent checking this out and verifying what reality is. :-) I'll file a PR to get the man page updated to reflect things. I believe what I've seen (re: parsing errors) is the latter case example you provided (baz=foo bar). So it seems that using quotes is the overall "safety mechanism" to ensure the value will work, but they're not required. -- | Jeremy Chadwick jdc@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 Apr 30 06:42:13 2011 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 1874E106564A; Sat, 30 Apr 2011 06:42:13 +0000 (UTC) (envelope-from bsd@vink.pl) Received: from mail-pw0-f54.google.com (mail-pw0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id DB0038FC08; Sat, 30 Apr 2011 06:42:12 +0000 (UTC) Received: by pwj8 with SMTP id 8so2698045pwj.13 for ; Fri, 29 Apr 2011 23:42:12 -0700 (PDT) Received: by 10.68.7.41 with SMTP id g9mr6367331pba.148.1304145732122; Fri, 29 Apr 2011 23:42:12 -0700 (PDT) Received: from mail-pv0-f182.google.com (mail-pv0-f182.google.com [74.125.83.182]) by mx.google.com with ESMTPS id u1sm2399145pbm.41.2011.04.29.23.42.11 (version=SSLv3 cipher=OTHER); Fri, 29 Apr 2011 23:42:12 -0700 (PDT) Received: by pvg11 with SMTP id 11so3399305pvg.13 for ; Fri, 29 Apr 2011 23:42:11 -0700 (PDT) MIME-Version: 1.0 Received: by 10.68.40.65 with SMTP id v1mr6356392pbk.154.1304145731232; Fri, 29 Apr 2011 23:42:11 -0700 (PDT) Received: by 10.68.42.40 with HTTP; Fri, 29 Apr 2011 23:42:11 -0700 (PDT) In-Reply-To: References: <201104281728.37497.jhb@freebsd.org> Date: Sat, 30 Apr 2011 08:42:11 +0200 Message-ID: From: Wiktor Niesiobedzki To: Jack Vogel , John Baldwin Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org Subject: Re: No data received with Intel Corporation Gigabit CT Desktop Adapter (82574L) 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, 30 Apr 2011 06:42:13 -0000 2011/4/29 Wiktor Niesiobedzki : > 2011/4/28 Jack Vogel : >> On Thu, Apr 28, 2011 at 2:28 PM, John Baldwin wrote: >>> >>> On Thursday, April 28, 2011 5:17:11 pm Wiktor Niesiobedzki wrote: >>> > Though they mention that HT MSI windows is disabled. I'm not sure, >>> > whether this matters. >>> >>> Yes, that is probably what breaks this. >>> >>> -- >>> John Baldwin >> >> Opps, missed that, thanks John.=C2=A0 So, disable MSIX and MSI using sys= ctl, >> then the driver should use legacy when it loads. >> >> Still, I'd get a different motherboard, sucks to not have MSIX :( >> > > Thanks for hints. I've disabled MSIX and MSI: > kadlubek# sysctl hw.pci | grep msi > hw.pci.honor_msi_blacklist: 1 > hw.pci.enable_msix: 0 > hw.pci.enable_msi: 0 > Ok, I found other way round about this. I've did some source code reading and found following tunable: hw.em.enable_msix=3D0 When set in loader.conf to 0, then the card magically starts to work properly. The only thing in our code in em_setup_msix(), that raises my doubts, is the following code path: int rid =3D PCIR_BAR(EM_MSIX_BAR); adapter->msix_mem =3D bus_alloc_resource_any(dev, SYS_RES_MEMORY, &rid, RF_ACTIVE); ... bus_release_resource(dev, SYS_RES_MEMORY, PCIR_BAR(EM_MSIX_BAR), adapter->msix_mem); Though manpage for bus_release_resource specifies, that rid needs to be exactly the same, as this returned by bus_alloc_resource. Changing the bus_release_resource to use rid instead of PCIR_BAR(EM_MSIX_BAR) makes the card working, with sysctl settings: hw.pci.enable_msix: 0 hw.pci.enable_msi: 0 instead of hw.em.enable_msix=3D0 The only thing that worries me, that when I don't have MSIX disabled (anyway), then driver succeeds with the MSI-X allocation. Shouldn't we in em_setup_msix check, how many vectors we have allocated with pci_alloc_msix and if this is 0, then fallback to MSI/Legacy? Or maybe pci_alloc_msix should report an error, when no PCIB_ALLOC_MSIX succeded? Cheers, Wiktor Niesiobedzki From owner-freebsd-stable@FreeBSD.ORG Sat Apr 30 13:14:45 2011 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 CF6FD106564A; Sat, 30 Apr 2011 13:14:45 +0000 (UTC) (envelope-from sklauder@trimind.de) Received: from mikako.shopkeeper.de (mikako.shopkeeper.de [82.119.175.20]) by mx1.freebsd.org (Postfix) with ESMTP id 3BA268FC0A; Sat, 30 Apr 2011 13:14:44 +0000 (UTC) Received: from avalon.dobu.local (pD951D203.dip.t-dialin.net [217.81.210.3]) (authenticated bits=0) by mikako.shopkeeper.de (8.14.3/8.14.3) with ESMTP id p3UCxeCn006034 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 30 Apr 2011 14:59:42 +0200 (CEST) (envelope-from sklauder@trimind.de) Received: from avalon.dobu.local (localhost [127.0.0.1]) by avalon.dobu.local (8.14.4/8.14.2) with ESMTP id p3UCxef8001887; Sat, 30 Apr 2011 14:59:40 +0200 (CEST) (envelope-from sklauder@avalon.dobu.local) Received: (from sklauder@localhost) by avalon.dobu.local (8.14.4/8.14.4/Submit) id p3UCxej2001886; Sat, 30 Apr 2011 14:59:40 +0200 (CEST) (envelope-from sklauder) Date: Sat, 30 Apr 2011 14:59:40 +0200 From: Sascha Klauder To: freebsd-stable@freebsd.org Message-ID: <20110430125940.GA1872@trimind.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.96.5 at mikako.shopkeeper.de X-Virus-Status: Clean Cc: freebsd-acpi@freebsd.org Subject: ale(4) not attaching after suspend/resume cycle X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: sklauder@trimind.de List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Apr 2011 13:14:45 -0000 Hi all, I'm trying to get suspend/resume functionality to work on my Acer Aspire One D250 netbook. I'm running 8.2-STABLE i386 as of 2011-02-25. Suspend was doing fine, but it would freeze on resume. By trial and error I've been able to pinpoint the problematic driver as ale(4). The machine will correctly resume once I un- load if_ale before suspending. I wouldn't mind that as a workaround, however, it fails to reattach after a suspend/resume cycle: pci0: driver added pci1: driver added found-> vendor=0x1969, dev=0x1026, revid=0xb0 domain=0, bus=1, slot=0, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0407, statreg=0x0010, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=16 powerspec 2 supports D0 D3 current D3 MSI supports 1 message, 64 bit pci0:1:0:0: reprobing on driver added pci0:1:0:0: Transition from D3 to D0 ale0: port 0x3000-0x307f mem 0x95200000-0x9523ffff irq 16 at device 0.0 on pci1 pcib1: ale0 requested memory range 0x95200000-0x9523ffff: good ale0: phy write timeout : 29 ale0: phy write timeout : 30 ale0: phy write timeout : 29 ale0: phy write timeout : 30 ale0: phy write timeout : 29 ale0: phy write timeout : 30 ale0: phy write timeout : 29 ale0: phy write timeout : 29 ale0: phy write timeout : 29 ale0: phy write timeout : 29 ale0: master reset timeout! ale0: reset timeout(0xffffffff)! ale0: PCI device revision : 0x00b0 ale0: Chip id/revision : 0xffff ale0: chip revision : 0xffff, 4294967295 Tx FIFO 4294967295 Rx FIFO -- not initialized? device_attach: ale0 attach returned 6 It does attach and work correctly even if loaded after booting. Repeated loading and unloading works as well. Anything obvious that I could try? Complete dmesg is available here: http://arwen.shopkeeper.de/~sascha/acer/dmesg.verbose Cheers, -sascha From owner-freebsd-stable@FreeBSD.ORG Sat Apr 30 21:37:46 2011 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 08BFF1065672 for ; Sat, 30 Apr 2011 21:37:46 +0000 (UTC) (envelope-from ken@kdm.org) Received: from nargothrond.kdm.org (nargothrond.kdm.org [70.56.43.81]) by mx1.freebsd.org (Postfix) with ESMTP id B6F228FC15 for ; Sat, 30 Apr 2011 21:37:45 +0000 (UTC) Received: from nargothrond.kdm.org (localhost [127.0.0.1]) by nargothrond.kdm.org (8.14.2/8.14.2) with ESMTP id p3ULJRd7067400; Sat, 30 Apr 2011 15:19:27 -0600 (MDT) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.14.2/8.14.2/Submit) id p3ULJRTb067399; Sat, 30 Apr 2011 15:19:27 -0600 (MDT) (envelope-from ken) Date: Sat, 30 Apr 2011 15:19:27 -0600 From: "Kenneth D. Merry" To: Dmitry Morozovsky Message-ID: <20110430211927.GA67374@nargothrond.kdm.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i Cc: freebsd-stable@FreeBSD.org Subject: Re: mps driver instability under stable/8 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, 30 Apr 2011 21:37:46 -0000 On Fri, Apr 29, 2011 at 11:51:21 +0400, Dmitry Morozovsky wrote: > Dear Ken, > > I have SuperMicro Server with mps driver you managed, with 24 SATA disks under > SAS x36 expander with large ZFS > > Sometimes, under random disk load such as daily find, it lost all its devices: > > [-- MARK -- Fri Apr 29 03:00:00 2011] > mps0: IOC Fault 0x40005900, Resetting^M > (pass20:mps0:0:22:0): SCSI command timeout on device handle 0x0020 SMID 442^M > mps0: IOC Fault 0x40001500, Resetting^M > (da19:mps0:0:21:0): SCSI command timeout on device handle 0x001f SMID 172^M > (da19:mps0:0:21:0): SCSI command timeout on device handle 0x001f SMID 511^M > (da20:mps0:0:20:0): SCSI command timeout on device handle 0x001e SMID 240^M > > .. > > (da4:mps0:0:0:0): SCSI command timeout on device handle 0x000a SMID 844^M > (da22:mps0:0:23:0): SCSI command timeout on device handle 0x0021 SMID 713^M > (da18:mps0:0:22:0): SCSI command timeout on device handle 0x0020 SMID 603^M > > and hangs there forever (in zio state). > > I've prepared debugging kernel with DDB and would be glad to help catch the > situation. Hmm... Can you send full dmesg output? What I'm most interested in is whether there is more kernel output before the IOC Fault that might shed some light on what is going on. Also, what brand (LSI, Maxim, etc.) and speed (3Gb, 6Gb) is the expander on the backplane? What model LSI controller do you have? How many lanes are connected between the controller and the backplane? What model disks do you have in the system? (dmesg will show that obviously.) Hopefully we can find some clues to point to the problem. Ken -- Kenneth Merry ken@FreeBSD.ORG