From owner-freebsd-stable@FreeBSD.ORG Sun Jan 11 00:20:53 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7B3601065686 for ; Sun, 11 Jan 2009 00:20:53 +0000 (UTC) (envelope-from me@janh.de) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.8]) by mx1.freebsd.org (Postfix) with ESMTP id EDF9B8FC13 for ; Sun, 11 Jan 2009 00:20:52 +0000 (UTC) (envelope-from me@janh.de) Received: from janh.freebsd (e177250030.adsl.alicedsl.de [85.177.250.30]) by mrelayeu.kundenserver.de (node=mrelayeu7) with ESMTP (Nemesis) id 0ML2xA-1LLo4R1VGj-0007Kb; Sun, 11 Jan 2009 01:20:51 +0100 Message-ID: <49693B62.2020104@janh.de> Date: Sun, 11 Jan 2009 01:20:50 +0100 From: Jan Henrik Sylvester User-Agent: Thunderbird 2.0.0.19 (X11/20090102) MIME-Version: 1.0 To: stable-list freebsd Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX1+RgBMhwMja/sm+vvdlUCo9W0BDkoN+Ml0nk5K JNwp8foNStaxzw8+YsyxEy9ptWB9agX/7J9OmuYi/VgNqso9TH F45cy7xAT9zzrksCi3nhg== Subject: 7.1 manpages: "first appeared in FreeBSD 8.0" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jan 2009 00:20:53 -0000 I found a 7.1-RELEASE manpage stating "first appeared in FreeBSD 8.0". A little bit of grepping revealed a few more: setfib(1) setfib(2) ffs(3) ffsl(3) ffsll(3) fls(3) flsl(3) flsll(3) memchr(3) memrchr(3) malo(4) crashinfo(8) savecore(8) Some others are correctly stating "7.1" for example textdump(4). Cheers, Jan Henrik From owner-freebsd-stable@FreeBSD.ORG Sun Jan 11 00:49:20 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 25736106564A for ; Sun, 11 Jan 2009 00:49:20 +0000 (UTC) (envelope-from ehrmann@gmail.com) Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by mx1.freebsd.org (Postfix) with ESMTP id F0D9B8FC1E for ; Sun, 11 Jan 2009 00:49:19 +0000 (UTC) (envelope-from ehrmann@gmail.com) Received: from [10.0.0.158] (unknown [64.9.236.71]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id DEBDCD051E for ; Sat, 10 Jan 2009 19:49:18 -0500 (EST) Message-ID: <496941FF.5090906@gmail.com> Date: Sat, 10 Jan 2009 16:49:03 -0800 From: David Ehrmann User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: stable-list freebsd Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: "vr0: rx packet lost" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jan 2009 00:49:20 -0000 I'm using 7.0-RELEASE. When there's heavy network traffic through the vr0 interface, I see lots of "vr0: rx packet lost" messages, and occasional "vr0: watchdog timeout" messages. I googled and found some information, but it was on an earlier version of FreeBSD, and there weren't any solutions. I didn't load vr as a module, and it's not listed by kldstat, so I assume it was build into the kernel. Ideas? Is there any additional information I should provide? From owner-freebsd-stable@FreeBSD.ORG Sun Jan 11 01:43:37 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 30847106566C; Sun, 11 Jan 2009 01:43:37 +0000 (UTC) (envelope-from rnoland@FreeBSD.org) Received: from gizmo.2hip.net (gizmo.2hip.net [64.74.207.195]) by mx1.freebsd.org (Postfix) with ESMTP id CF1238FC20; Sun, 11 Jan 2009 01:43:36 +0000 (UTC) (envelope-from rnoland@FreeBSD.org) Received: from [192.168.1.151] (adsl-154-162-115.bna.bellsouth.net [68.154.162.115]) (authenticated bits=0) by gizmo.2hip.net (8.14.3/8.14.3) with ESMTP id n0B1gof5019884 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 10 Jan 2009 20:42:50 -0500 (EST) (envelope-from rnoland@FreeBSD.org) From: Robert Noland To: vehemens In-Reply-To: <200901101553.21968.vehemens@verizon.net> References: <1231599679.1837.13.camel@wombat.2hip.net> <1231606142.1837.34.camel@wombat.2hip.net> <200901101553.21968.vehemens@verizon.net> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-SJJeAa9imQDZCqt5jFRf" Organization: FreeBSD Date: Sat, 10 Jan 2009 20:43:29 -0500 Message-Id: <1231638209.1764.13.camel@wombat.2hip.net> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 FreeBSD GNOME Team Port X-Spam-Status: No, score=-0.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_PBL, RCVD_IN_SORBS_DUL,RDNS_DYNAMIC autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on gizmo.2hip.net Cc: freebsd-x11@freebsd.org, freebsd-stable Subject: Re: [HEADS UP] drm merged to -STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jan 2009 01:43:37 -0000 --=-SJJeAa9imQDZCqt5jFRf Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sat, 2009-01-10 at 15:53 -0800, vehemens wrote: > On Saturday 10 January 2009 08:49:01 am Robert Noland wrote: > > On Sat, 2009-01-10 at 10:01 -0500, Robert Noland wrote: > > > I just merged drm (Direct Rendering) from HEAD. > > > > > > - Support for latest Intel chips > > > - Support and fixes for many AMD/ATI chips r500 and below > > > - Support AMD/ATI IGP based chips (rs690/rs485) > > > - Lots of code cleanups > > > - Lots of other fixes and changes since the existing drm > > > is 2+ years old > > > > > > If you are experiencing a "garbled" screen with certain pci/pci-e bas= ed > > > radeons, I have another patch in HEAD that isn't included yet. > > > > I decided to go ahead and fully sync to HEAD, so this should be resolve= d > > as well. This added: > > > > - Use bus_dma to allocate scatter/gather pages for pci GART. > > This fixes "garbled" screen issues on pci based radeons. > > - Prevent drm from attaching to secondary devices even if they > > have the the same pci id. >=20 > What's your plan on incorporating r6xx/r7xx drm :? The code isn't user ready yet. What AMD has released, I have building. AMD is being quite reasonable about their code, so it won't be a big deal to get that code imported quickly once it is ready. My expectation is that we will ship code, at least in -CURRENT, before any linux distro. ;) robert. > _______________________________________________ > freebsd-x11@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-x11 > To unsubscribe, send any mail to "freebsd-x11-unsubscribe@freebsd.org" --=-SJJeAa9imQDZCqt5jFRf Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEABECAAYFAklpTsEACgkQM4TrQ4qfROM4IACff1ks7Zf4O6m6uLyiHKO+kRFK PeIAnR6oL6+cYAKH60wzEluJn8/osCZ2 =e30i -----END PGP SIGNATURE----- --=-SJJeAa9imQDZCqt5jFRf-- From owner-freebsd-stable@FreeBSD.ORG Sun Jan 11 01:51:15 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B7F57106566C for ; Sun, 11 Jan 2009 01:51:15 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id 670D38FC08 for ; Sun, 11 Jan 2009 01:51:15 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost1.sentex.ca (8.14.3/8.14.3) with ESMTP id n0B1pD8Y070465; Sat, 10 Jan 2009 20:51:13 -0500 (EST) (envelope-from mike@sentex.net) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.8/8.13.3) with ESMTP id n0B1pC5o043840 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 10 Jan 2009 20:51:12 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <200901110151.n0B1pC5o043840@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Sat, 10 Jan 2009 20:51:06 -0500 To: David Ehrmann , stable-list freebsd From: Mike Tancsa In-Reply-To: <496941FF.5090906@gmail.com> References: <496941FF.5090906@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18 Cc: Subject: Re: "vr0: rx packet lost" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jan 2009 01:51:16 -0000 At 07:49 PM 1/10/2009, David Ehrmann wrote: >I'm using 7.0-RELEASE. >Ideas? Is there any additional information I should provide? 7.1R has a *far* better vr driver that has a lot of bug fixes in it. http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/vr/if_vr.c has details of what was fixed. ---Mike From owner-freebsd-stable@FreeBSD.ORG Sun Jan 11 02:07:49 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5E557106566B for ; Sun, 11 Jan 2009 02:07:49 +0000 (UTC) (envelope-from heliocentric@gmail.com) Received: from mail-gx0-f11.google.com (mail-gx0-f11.google.com [209.85.217.11]) by mx1.freebsd.org (Postfix) with ESMTP id F03C28FC14 for ; Sun, 11 Jan 2009 02:07:48 +0000 (UTC) (envelope-from heliocentric@gmail.com) Received: by gxk4 with SMTP id 4so2029068gxk.19 for ; Sat, 10 Jan 2009 18:07:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=UlUg6KEthL89G5Z7fyuKVaRkt7aJbPbIq1sHbxJFeKA=; b=iEfUel3JUFT5AwWrpeSDA4/ChqOu1tsXNVlSqyoPAU4G619x+UWFZglvG7h++o3hdZ 35OCPS6akVurX0+IMv8YgOTB4P7bwqWBUiLHCANk3WKieeO5dBk1FkHS3BYd0qWTEWdz tZH5mpYmkAnSrJRs3ltpd8EwRLpTw/63e7RJQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=yEjkVumJKXNFJ8eNHswRK3avbJHMc6V1uZz69GFoDI8skLFFzUb2DeDKjtGPzE7UdM iWcmnoh+l8sQs5/isHhmVNbh/0z5lIgy8jEeJAlgO4Z5ryRtgZnTcZoCQBYHO21bXMo/ isyejYzfjKjiqx4RAoOvvkSF7o0ffJmZFR/gA= Received: by 10.90.100.20 with SMTP id x20mr8295737agb.12.1231639667969; Sat, 10 Jan 2009 18:07:47 -0800 (PST) Received: by 10.90.36.7 with HTTP; Sat, 10 Jan 2009 18:07:47 -0800 (PST) Message-ID: Date: Sat, 10 Jan 2009 21:07:47 -0500 From: heliocentric@gmail.com To: "Pete French" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Cc: freebsd-stable@freebsd.org, drosih@rpi.edu, rblayzor.bulk@inoc.net Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jan 2009 02:07:49 -0000 I noticed a similar problem testing 7.1-RC1, It seemed to be a deep deadlock, as it was triggered by lighttpd doing kern_sendfile, and never returning. The side effects (being unable to create processes, etc) is similar. My kernconf is below, try building the kernel, and send an email containing the backtrace from any process that has blocked (in my case, lighttpd attempting to sendfile a large amount of data to php fastcgi triggered it, but that's a guess on my part). Note that this includes witness, and invariants, so performance will be hit. Also, enable watchdogd, and add -e 'ls -al /etc' to it's flags. It should drop you to a debugger with a backtrace within a few seconds of the lock being triggered, and it should output a backtrace and any invariant/witness lock warnings. Obviously if you don't have a serial or local console, don't do this. include GENERIC ident DEBUG options KDB options DDB options SW_WATCHDOG options DEBUG_VFS_LOCKS options INVARIANTS options WITNESS On 1/10/09, Pete French wrote: >> FWIW, the other guy I know who is having this problem had already >> switched to using ULE under 7.0-release, and did not have any >> problems with it. So *his* problem was probably not related to >> SCHED_ULE, unless something has recently changed there. > > Well, one of my machines just locked up again, even with SCHED_4BSD > on it, so I am now thinking it is unrelated. > > The machine has completely locked - no response to pings, no > response to keypresses, nor to the power button. There is nothing > printed on the console - it is just sitting there with a login prompt :-( > > This is really not good - these are extremely common servers after all, and > I am just running bog standard 7.1 with apache and mysql. This is happening > across several different servers, all of which are slight variants on > the DL360, so I dont think it is something perculiar to me. > > -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" > From owner-freebsd-stable@FreeBSD.ORG Sun Jan 11 02:42:02 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E4823106566C for ; Sun, 11 Jan 2009 02:42:02 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.237]) by mx1.freebsd.org (Postfix) with ESMTP id ACEDF8FC0C for ; Sun, 11 Jan 2009 02:42:02 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so11593868rvf.43 for ; Sat, 10 Jan 2009 18:42:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=9ThOl8txFJBtBqFSAtRUvktSwoLb426ex0xNtZ3zVCQ=; b=Kz0ouzNqLgMNw8PvyOxX6EFeVQdfRONfNSDFh5NJwHW28Iizw/TM+Z3bkb7PuAOd1K HAZOvSdbNMf6FBsGzxn+6yhiEjaBaQawTwZbCPoP8P3u7ZPZ4YQIpwFeJ1/RWYGQKXOn Kmh1uhP/Fo5h6wGtxZRpNxOcxA/KBkJQ7F578= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=PwA46D16FrWyrcXJFpJmvJvoSaw/wKN1ms0Z5ONg1/VezrwyHB9IqzHaHpFPM+nWoA Zc8sgGOp7tNpTC9k1uu36C3lXSVAPxTzIFaG4XeCbPGJfFLP9Ig30bpQ+nEOxfOGGp+v 6qOfL4WaxceWFfdfM275+sjEgCtB30NyvLWWs= Received: by 10.140.158.4 with SMTP id g4mr13623154rve.160.1231641722273; Sat, 10 Jan 2009 18:42:02 -0800 (PST) Received: from michelle.cdnetworks.co.kr ([211.53.35.84]) by mx.google.com with ESMTPS id b39sm36466267rvf.0.2009.01.10.18.41.59 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 10 Jan 2009 18:42:01 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.14.3/8.14.3) with ESMTP id n0B2fte9042865 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 11 Jan 2009 11:41:55 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.14.3/8.14.3/Submit) id n0B2ftsE042864; Sun, 11 Jan 2009 11:41:55 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Sun, 11 Jan 2009 11:41:55 +0900 From: Pyun YongHyeon To: Mike Tancsa Message-ID: <20090111024155.GA42714@cdnetworks.co.kr> References: <496941FF.5090906@gmail.com> <200901110151.n0B1pC5o043840@lava.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200901110151.n0B1pC5o043840@lava.sentex.ca> User-Agent: Mutt/1.4.2.3i Cc: David Ehrmann , stable-list freebsd Subject: Re: "vr0: rx packet lost" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jan 2009 02:42:03 -0000 On Sat, Jan 10, 2009 at 08:51:06PM -0500, Mike Tancsa wrote: > At 07:49 PM 1/10/2009, David Ehrmann wrote: > >I'm using 7.0-RELEASE. > >Ideas? Is there any additional information I should provide? > > 7.1R has a *far* better vr driver that has a lot of bug fixes in it. > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/vr/if_vr.c > has details of what was fixed. As Mike said several known bugs were fixed. If you still see problems on 7.1-RELEASE, let me know. -- Regards, Pyun YongHyeon From owner-freebsd-stable@FreeBSD.ORG Sun Jan 11 03:15:28 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1A538106564A for ; Sun, 11 Jan 2009 03:15:28 +0000 (UTC) (envelope-from ehrmann@gmail.com) Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by mx1.freebsd.org (Postfix) with ESMTP id E2BFE8FC16 for ; Sun, 11 Jan 2009 03:15:27 +0000 (UTC) (envelope-from ehrmann@gmail.com) Received: from [10.0.0.158] (unknown [64.9.236.71]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 7D059D05A2; Sat, 10 Jan 2009 22:15:26 -0500 (EST) Message-ID: <4969644A.1010306@gmail.com> Date: Sat, 10 Jan 2009 19:15:22 -0800 From: David Ehrmann User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Mike Tancsa References: <496941FF.5090906@gmail.com> <200901110151.n0B1pC5o043840@lava.sentex.ca> In-Reply-To: <200901110151.n0B1pC5o043840@lava.sentex.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: stable-list freebsd Subject: Re: "vr0: rx packet lost" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jan 2009 03:15:28 -0000 Wow. That really is a lot, but I might just wait for the final release, though with this command, it might not be such a big deal: freebsd-update upgrade -r 7.1-RC1 Mike Tancsa wrote: > At 07:49 PM 1/10/2009, David Ehrmann wrote: >> I'm using 7.0-RELEASE. >> Ideas? Is there any additional information I should provide? > > 7.1R has a *far* better vr driver that has a lot of bug fixes in it. > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/vr/if_vr.c > has details of what was fixed. > ---Mike From owner-freebsd-stable@FreeBSD.ORG Sun Jan 11 07:44:25 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D5785106564A for ; Sun, 11 Jan 2009 07:44:25 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail14.syd.optusnet.com.au (mail14.syd.optusnet.com.au [211.29.132.195]) by mx1.freebsd.org (Postfix) with ESMTP id 4ECF78FC0C for ; Sun, 11 Jan 2009 07:44:25 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c122-106-215-175.belrs3.nsw.optusnet.com.au [122.106.215.175]) by mail14.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id n0B7iN7u000952 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 11 Jan 2009 18:44:23 +1100 X-Bogosity: Ham, spamicity=0.000000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.3/8.14.3) with ESMTP id n0B7iMjv007099; Sun, 11 Jan 2009 18:44:22 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.3/8.14.3/Submit) id n0B7iMP1007098; Sun, 11 Jan 2009 18:44:22 +1100 (EST) (envelope-from peter) Date: Sun, 11 Jan 2009 18:44:22 +1100 From: Peter Jeremy To: David Ehrmann Message-ID: <20090111074422.GA7054@server.vk2pj.dyndns.org> References: <496941FF.5090906@gmail.com> <200901110151.n0B1pC5o043840@lava.sentex.ca> <4969644A.1010306@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="k1lZvvs/B4yU6o8G" Content-Disposition: inline In-Reply-To: <4969644A.1010306@gmail.com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.18 (2008-05-17) Cc: stable-list freebsd Subject: Re: "vr0: rx packet lost" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jan 2009 07:44:26 -0000 --k1lZvvs/B4yU6o8G Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2009-Jan-10 19:15:22 -0800, David Ehrmann wrote: >Wow. That really is a lot, but I might just wait for the final release,= =20 >though with this command, it might not be such a big deal: > >freebsd-update upgrade -r 7.1-RC1 FreeBSD 7.1-RELEASE has been available for nearly a week. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --k1lZvvs/B4yU6o8G Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAklpo1YACgkQ/opHv/APuIdwFQCggd7ywrnHCMhItxjuzl+eWYF5 3fcAni/4BXgcGim4GKaaxbIH5gBm52l8 =ab7+ -----END PGP SIGNATURE----- --k1lZvvs/B4yU6o8G-- From owner-freebsd-stable@FreeBSD.ORG Sun Jan 11 12:45:33 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 414461065672 for ; Sun, 11 Jan 2009 12:45:33 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from constantine.ticketswitch.com (constantine.ticketswitch.com [IPv6:2002:57e0:1d4e:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id F10FC8FC13 for ; Sun, 11 Jan 2009 12:45:32 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from dilbert.rattatosk ([10.64.50.6] helo=dilbert.ticketswitch.com) by constantine.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LLzgr-0004Gu-Pk; Sun, 11 Jan 2009 12:45:17 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LLzgr-00008v-Nu; Sun, 11 Jan 2009 12:45:17 +0000 To: heliocentric@gmail.com In-Reply-To: Message-Id: From: Pete French Date: Sun, 11 Jan 2009 12:45:17 +0000 Cc: freebsd-stable@freebsd.org, drosih@rpi.edu, rblayzor.bulk@inoc.net Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jan 2009 12:45:33 -0000 > I noticed a similar problem testing 7.1-RC1, It seemed to be a deep > deadlock, as it was triggered by lighttpd doing kern_sendfile, and > never returning. The side effects (being unable to create processes, > etc) is similar. Interesting - did you get any responses from anyone else regarding this ? My last box which locked up was essentialy idle, so I am very surprised by all of this - also none of the heavilt loaded machines (i.e. the actual webservers) have locked up. I am also surprised that this isn't more widely reported, as the hardware is very common. The only oddity with ym compile is that I set the CPUTYPE to 'core2' - that shouldnt have an effect, but I will remove it anyway, just so I am actually building a completely vanilla amd64. That way I should have what everyone else has, and since I don't see anyone else saying they have isues then maybe mine will go away too (fingers crossed) > My kernconf is below, try building the kernel, and send an email > containing the backtrace from any process that has blocked (in my OK, will do. I can try this on the one non-essential box which locked up yesterday. I don't know how long it will before it locks up again, but will see if I can do some things to provoke it. -pete. From owner-freebsd-stable@FreeBSD.ORG Sun Jan 11 12:58:58 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9A2051065672 for ; Sun, 11 Jan 2009 12:58:58 +0000 (UTC) (envelope-from me@pollux2.local.net) Received: from smtp2-g19.free.fr (smtp2-g19.free.fr [212.27.42.28]) by mx1.freebsd.org (Postfix) with ESMTP id 5D35B8FC0A for ; Sun, 11 Jan 2009 12:58:58 +0000 (UTC) (envelope-from me@pollux2.local.net) Received: from smtp2-g19.free.fr (localhost.localdomain [127.0.0.1]) by smtp2-g19.free.fr (Postfix) with ESMTP id CD32C12B6D5 for ; Sun, 11 Jan 2009 13:58:56 +0100 (CET) Received: from pollux2.local.net (che78-3-82-246-30-233.fbx.proxad.net [82.246.30.233]) by smtp2-g19.free.fr (Postfix) with ESMTP id AE2EB12B6B2 for ; Sun, 11 Jan 2009 13:58:56 +0100 (CET) Received: by pollux2.local.net (Postfix, from userid 2000) id 03D591DB1C; Sun, 11 Jan 2009 14:02:22 +0100 (CET) Date: Sun, 11 Jan 2009 14:02:22 +0100 From: Harald To: freebsd-stable@freebsd.org Message-ID: <20090111130222.GA13690@pollux2.free.local.net> Mail-Followup-To: freebsd-stable@freebsd.org References: <20090109184126.GA2501@pollux2.free.local.net> <20090109191007.GA6625@osiris.mauzo.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090109191007.GA6625@osiris.mauzo.dyndns.org> User-Agent: Mutt/1.4.2.3i Subject: Re: Medical database Vidal X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jan 2009 12:58:58 -0000 On Fri, Jan 09, 2009 at 07:10:07PM +0000, Ben Morrow wrote: > I would guess that your CD has both Rock Ridge and Joliet extensions, > and that the creator has hidden the Win32-specific files from the Unix > directory tree because they thought they wouldn't be useful. If for some > reason you need to see the CD as a Win32 machine would, you can use the > -r option to mount_cd9660. Thank you very much indeed for your detailed explanation. Before searching for help I have tried out all options of mount_cd9660, one after the other and all together or so without understanding their meaning. Therefore I obviously missed the working one. `mount_cd9660 -r /dev/acd0 /cdrom' works like a charm. `wine /cdrom/setup.exe' does the job as well, unfortunately with a certain number of `err:' and `fixme:' lines. `cd path/to/VidalCD ; wine VidalCD.exe' starts the application with the same or similar error lines (which is not surprising). The programme does run, but is not really operational: It is too slow, and exiting without problems requires to type `Ctrl+Alt+Backspace' ! No time yet to see whether I am capable to fix something without further help. Harald -- FreeBSD 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008 From owner-freebsd-stable@FreeBSD.ORG Sun Jan 11 15:55:15 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6442D1065670 for ; Sun, 11 Jan 2009 15:55:15 +0000 (UTC) (envelope-from msnkipa@mail.ru) Received: from mx44.mail.ru (mx44.mail.ru [195.239.211.10]) by mx1.freebsd.org (Postfix) with ESMTP id 1CB368FC0A for ; Sun, 11 Jan 2009 15:55:14 +0000 (UTC) (envelope-from msnkipa@mail.ru) Received: from f149.mail.ru (f149.mail.ru [194.67.57.228]) by mx44.mail.ru (mPOP.Fallback_MX) with ESMTP id 23DC53800372B for ; Sun, 11 Jan 2009 16:36:22 +0300 (MSK) Received: from mail by f149.mail.ru with local id 1LM0UG-0006sE-00 for freebsd-stable@freebsd.org; Sun, 11 Jan 2009 16:36:20 +0300 Received: from [89.113.74.101] by win.mail.ru with HTTP; Sun, 11 Jan 2009 16:36:20 +0300 From: =?koi8-r?Q?=ED=C9=C8=C1=C9=CC_=EB=C9=D0=C1?= To: freebsd-stable@freebsd.org Mime-Version: 1.0 X-Mailer: mPOP Web-Mail 2.19 X-Originating-IP: 192.168.7.100 via proxy [89.113.74.101] Date: Sun, 11 Jan 2009 16:36:20 +0300 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Message-Id: X-Spam: Not detected X-Mras: Ok Subject: ZFSv13 in RELENG7 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: =?koi8-r?Q?=ED=C9=C8=C1=C9=CC_=EB=C9=D0=C1?= List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jan 2009 15:55:15 -0000 Is any plans to backport ZFSv13 from CURRENT to RELENG7 branxh or not? From owner-freebsd-stable@FreeBSD.ORG Sun Jan 11 16:27:59 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3ADC3106564A for ; Sun, 11 Jan 2009 16:27:59 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from constantine.ticketswitch.com (constantine.ticketswitch.com [IPv6:2002:57e0:1d4e:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id F2D648FC08 for ; Sun, 11 Jan 2009 16:27:58 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from dilbert.rattatosk ([10.64.50.6] helo=dilbert.ticketswitch.com) by constantine.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LM3AF-0001er-Om for freebsd-stable@freebsd.org; Sun, 11 Jan 2009 16:27:51 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LM3AF-0000yL-Nh for freebsd-stable@freebsd.org; Sun, 11 Jan 2009 16:27:51 +0000 To: freebsd-stable@freebsd.org In-Reply-To: Message-Id: From: Pete French Date: Sun, 11 Jan 2009 16:27:51 +0000 Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jan 2009 16:27:59 -0000 > My kernconf is below, try building the kernel, and send an email > containing the backtrace from any process that has blocked (in my Well, I havent managed to get a backtrace, but immediately upon booting the system halts with the following: http://www.twisted.org.uk/~pete/71_lor1.jpg Interestingly, if I try and boot into safe mode then it will not even get that far: http://www.twisted.org.uk/~pete/71_safe1.jpg Am going to try and backtrace that now to see what I can get. Unfortunately I can only provide screen captures rather than actual text output from this due to having to go via a Mac running RDP thought an ssh tunnel to a Windows box and then using IE to go to the iLO :-) Convoluted, but it works... -pete. From owner-freebsd-stable@FreeBSD.ORG Sun Jan 11 16:37:26 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1897E106564A for ; Sun, 11 Jan 2009 16:37:26 +0000 (UTC) (envelope-from eugene@donpac.ru) Received: from cops.gladchenko.ru (cops.gladchenko.ru [195.161.106.100]) by mx1.freebsd.org (Postfix) with ESMTP id 720828FC08 for ; Sun, 11 Jan 2009 16:37:24 +0000 (UTC) (envelope-from eugene@donpac.ru) Received: from cerberus.rnd.cbr.ru (cerberus.rnd.cbr.ru [194.84.224.97]) by cops.gladchenko.ru (8.14.3/8.14.2) with ESMTP id n0BGMBZw057718 for ; Sun, 11 Jan 2009 19:22:14 +0300 (MSK) (envelope-from eugene@donpac.ru) Received: from [10.10.10.2] by cerberus.rnd.cbr.ru with ESMTP id n0BGM6KV078837 for ; Sun, 11 Jan 2009 19:22:10 +0300 (MSK) (envelope-from eugene@donpac.ru) X-Antivirus: Dr.Web (R) for Mail Servers on cops.gladchenko.ru host X-AntiVirus: Checked by Dr.Web [version: 4.44, engine: 4.44.0.09170, virus records: 498054, updated: 9.01.2009] Date: Sun, 11 Jan 2009 19:22:06 +0300 From: Eugene Gladchenko X-Priority: 3 (Normal) Message-ID: <88527079.20090111192206@donpac.ru> To: freebsd-stable@freebsd.org In-Reply-To: <8dfae1c10901071550s69d99802p31ca7c775f3d6823@mail.gmail.com> References: <8dfae1c10901070639x67945324jeeecfcac647d7976@mail.gmail.com> <8dfae1c10901071550s69d99802p31ca7c775f3d6823@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Antivirus-Code: 100000 X-Spam-Status: No, score=-100.0 required=5.0 tests=AWL,BAYES_50,RDNS_NONE, USER_IN_WHITELIST autolearn=no version=3.2.5 X-Spam-Report: * -100 USER_IN_WHITELIST From: address is in the user's white-list * 0.0 BAYES_50 BODY: Bayesian spam probability is 40 to 60% * [score: 0.5000] * 0.1 RDNS_NONE Delivered to trusted network by a host with no rDNS * -0.1 AWL AWL: From: address is in the auto white-list X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on cops.gladchenko.ru Subject: Re: FreeBSD 7.1 Breaks re and rl Network Interface Drivers X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Eugene Gladchenko List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jan 2009 16:37:26 -0000 Walter, Thursday, January 8, 2009, 2:50:40 AM, you wrote: WV> Booting kernel.old, which is 7.0-RELEASE-p7 completely alleviates all WV> problems. I believe this roundly confirms that this is a bug in the WV> 7.1-RELEASE re kernel drivers. Does kern/130011 look similar? http://www.freebsd.org/cgi/query-pr.cgi?pr=130011 The re driver was really broken in 7.1-RC2 and the fix didn't get to 7.1-RELEASE. -- Eugene Gladchenko EVG15-RIPE From owner-freebsd-stable@FreeBSD.ORG Sun Jan 11 17:16:10 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EC3E2106566B for ; Sun, 11 Jan 2009 17:16:10 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from constantine.ticketswitch.com (constantine.ticketswitch.com [IPv6:2002:57e0:1d4e:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id AFDE28FC23 for ; Sun, 11 Jan 2009 17:16:10 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from dilbert.rattatosk ([10.64.50.6] helo=dilbert.ticketswitch.com) by constantine.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LM3uv-0001xx-8c for freebsd-stable@freebsd.org; Sun, 11 Jan 2009 17:16:05 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LM3uv-0001CD-7X for freebsd-stable@freebsd.org; Sun, 11 Jan 2009 17:16:05 +0000 To: freebsd-stable@freebsd.org In-Reply-To: Message-Id: From: Pete French Date: Sun, 11 Jan 2009 17:16:05 +0000 Subject: Lock order reversals using bce in 7.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jan 2009 17:16:11 -0000 Here is a better set of images. This machine was compiled with the following config file: include GENERIC ident DEBUG options KDB options DDB options SW_WATCHDOG options DEBUG_VFS_LOCKS options MUTEX_DEBUG options WITNESS options WITNESS_KDB options LOCK_PROFILING options INVARIANTS options INVARIANT_SUPPORT options DIAGNOSTIC On booting it almost immediately does this: http://www.twisted.org.uk/~pete/71_lor.png The output of trace, show pcpu, show locks, show allpcpu and show alllocks are shown in the following images: http://www.twisted.org.uk/~pete/71_locks_trace.png http://www.twisted.org.uk/~pete/71_pcpu_alllocks.png http://www.twisted.org.uk/~pete/71_allpcpu1.png http://www.twisted.org.uk/~pete/71_allpcpu2.png I am going to revent the machine back to a normal kernel now - is there anything I might be able to do to stop this, or do I need to roll everything back to 7.0 ? cheers, -pete. From owner-freebsd-stable@FreeBSD.ORG Sun Jan 11 19:01:43 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 71794106566B for ; Sun, 11 Jan 2009 19:01:43 +0000 (UTC) (envelope-from heliocentric@gmail.com) Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.30]) by mx1.freebsd.org (Postfix) with ESMTP id 1F02F8FC1C for ; Sun, 11 Jan 2009 19:01:42 +0000 (UTC) (envelope-from heliocentric@gmail.com) Received: by yx-out-2324.google.com with SMTP id 8so4274832yxb.13 for ; Sun, 11 Jan 2009 11:01:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=vbJIity0fqxjM5UJBdvcTLV4GXDFsm16sFulhF13ZNE=; b=YclkDixXBejRLmVHNWI/wcLjwv2BrylhyYPmwr98uqhm8Sd+y1lWbe8gUAK+2V2zCG 9+WQGKUUhrk94/orz5DnqF87H+2f/2Hny9NujVYXVFlAP2zwesSkhcACZ/yO4e6sk+po 8e065fZLmbv0Pva77FcG5JU2rp+p3RJK/+lzk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=LJB4ZMD/Rr2t0Gcn/ubsz1REmnvXhtRzY9wKKYSFYlmcYIemPLOMWCoHXAsyPghFn1 4f0qkZsDLOMAuARJiTzXwp1bixiwTBd96YdBU4V5fUsZIpXq3mtpkZxbzQRT7WvLqQz5 OD7h+NJ5Fno/b16YoSZrlJ8ugry81PAQPPxlQ= Received: by 10.90.101.7 with SMTP id y7mr13241181agb.6.1231700502436; Sun, 11 Jan 2009 11:01:42 -0800 (PST) Received: by 10.90.36.7 with HTTP; Sun, 11 Jan 2009 11:01:42 -0800 (PST) Message-ID: Date: Sun, 11 Jan 2009 14:01:42 -0500 From: "Dylan Cochran" To: "Pete French" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Cc: freebsd-stable Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jan 2009 19:01:43 -0000 On Sun, Jan 11, 2009 at 11:27 AM, Pete French wrote: >> My kernconf is below, try building the kernel, and send an email >> containing the backtrace from any process that has blocked (in my > > Well, I havent managed to get a backtrace, but immediately upon > booting the system halts with the following: > > http://www.twisted.org.uk/~pete/71_lor1.jpg Not Found From owner-freebsd-stable@FreeBSD.ORG Sun Jan 11 19:10:41 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 50E20106564A for ; Sun, 11 Jan 2009 19:10:41 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from constantine.ticketswitch.com (constantine.ticketswitch.com [IPv6:2002:57e0:1d4e:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id 16C7C8FC14 for ; Sun, 11 Jan 2009 19:10:41 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from dilbert.rattatosk ([10.64.50.6] helo=dilbert.ticketswitch.com) by constantine.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LM5hi-0002hB-H9; Sun, 11 Jan 2009 19:10:34 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LM5hi-0001YF-Fs; Sun, 11 Jan 2009 19:10:34 +0000 To: heliocentric@gmail.com In-Reply-To: Message-Id: From: Pete French Date: Sun, 11 Jan 2009 19:10:34 +0000 Cc: freebsd-stable@freebsd.org Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jan 2009 19:10:41 -0000 > Not Found sorry, see the subsequent email, there are more links there to working PNG's -pete. From owner-freebsd-stable@FreeBSD.ORG Sun Jan 11 19:21:00 2009 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 DD55210656C0 for ; Sun, 11 Jan 2009 19:21:00 +0000 (UTC) (envelope-from hrs@FreeBSD.org) Received: from mail.allbsd.org (unknown [IPv6:2001:2f0:104:e001::32]) by mx1.freebsd.org (Postfix) with ESMTP id 687948FC13 for ; Sun, 11 Jan 2009 19:21:00 +0000 (UTC) (envelope-from hrs@FreeBSD.org) Received: from delta.allbsd.org (p2191-ipbf1403funabasi.chiba.ocn.ne.jp [118.7.161.191]) (authenticated bits=128) by mail.allbsd.org (8.14.3/8.14.2) with ESMTP id n0BJKlT4087958 for ; Mon, 12 Jan 2009 04:20:58 +0900 (JST) (envelope-from hrs@FreeBSD.org) Received: from localhost (alph.allbsd.org [192.168.0.10]) (authenticated bits=0) by delta.allbsd.org (8.13.4/8.13.4) with ESMTP id n0BJKdAk084746 for ; Mon, 12 Jan 2009 04:20:41 +0900 (JST) (envelope-from hrs@FreeBSD.org) Date: Mon, 12 Jan 2009 04:20:14 +0900 (JST) Message-Id: <20090112.042014.205677175.hrs@allbsd.org> To: stable@FreeBSD.org From: Hiroki Sato X-PGPkey-fingerprint: BDB3 443F A5DD B3D0 A530 FFD7 4F2C D3D8 2793 CF2D X-Mailer: Mew version 6.2 on Emacs 22.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Multipart/Signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="--Security_Multipart(Mon_Jan_12_04_20_14_2009_954)--" Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.93.3, clamav-milter version 0.93.3 on gatekeeper.allbsd.org X-Virus-Status: Clean X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (mail.allbsd.org [133.31.130.32]); Mon, 12 Jan 2009 04:20:58 +0900 (JST) Cc: Subject: IPv6 routing on 7.1R X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jan 2009 19:21:01 -0000 ----Security_Multipart(Mon_Jan_12_04_20_14_2009_954)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, I noticed an odd behavior regarding IPv6 after upgrading my 7.0R box to 7.1R. The situation and symptom are the following: 1. The box has two NICs. One has an address 2001:0db8:1::1/64 (NIC A), and another has 2001:0db8:2::1/64 (NIC B). These addresses are assigned manually ($ipv6_ifconfig in rc.conf). 2. RA is periodically sent to the network 2001:0db8:1::1/64 (NIC A) by a router on the subnet. The RA includes a source link-layer address option only. When setting net.inet6.ip6.accept_rtadv=1 in this configuration, I expected the box assigns an autoconf IPv6 address (prefix 2001:0db8:1::/64 + EUI64) to NIC A and an default route based on source link-layer address in the RA packet. Actually, these two were done as expected. However, after addresses are assigned, routes for NIC B disappeared from the routing table. More specifically, a cloning route "2001:0db8:2::1/64 -> link#2" was removed for some reason. Is this an expected behavior? IIRC, 7.0R does not remove the route and I think it is strange. It works fine if a box has a single NIC, though. -- | Hiroki SATO ----Security_Multipart(Mon_Jan_12_04_20_14_2009_954)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEABECAAYFAklqRm4ACgkQTyzT2CeTzy0vYgCgy2+jwbltC4hR4Gqs1o0LFy0L 2wcAoJkmPjB2wf/VEJedj4FrfyAySoUv =5+wj -----END PGP SIGNATURE----- ----Security_Multipart(Mon_Jan_12_04_20_14_2009_954)---- From owner-freebsd-stable@FreeBSD.ORG Sun Jan 11 19:22:52 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 78D56106570D for ; Sun, 11 Jan 2009 19:22:52 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from mail-bw0-f20.google.com (mail-bw0-f20.google.com [209.85.218.20]) by mx1.freebsd.org (Postfix) with ESMTP id C61DB8FC0C for ; Sun, 11 Jan 2009 19:22:51 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: by bwz13 with SMTP id 13so5145885bwz.19 for ; Sun, 11 Jan 2009 11:22:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=RBQLrdVzHU7y0C5D7LON6E9Q8IC3SGXjZwZ3Z0bSVxE=; b=cJtxn/SHAhz6dMK2gBzRaCrwY+guJSrPySdX+nGlq85EleWJaRYASJytexhX6JjNN5 1EK5lLMSMZ5fysk11pylqwCqgWhBESD3mlnX5HR+xS09uvZXrDdSoZLOzER6uF5xkZKh qHNIDizXWK7NjkR0oQ1ai9/UfWqvZm2HHnbMY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=ML5FmBP02YUvwAyxrbS6yiA9w/9YhnSSTYdJki1qIdnZdpDjB3e9WL5tM7PE9SCk38 OdmhmRvHgNloj42pjEHN3x+a2rs89y79miaqjWFEfNJTzw4hWUzS9EPGwx8wrnW86GZl 2FfccKju4zVr3xo5p0CZggwh2sliE3GhhY+lM= Received: by 10.181.33.8 with SMTP id l8mr10662241bkj.155.1231701770633; Sun, 11 Jan 2009 11:22:50 -0800 (PST) Received: by 10.181.26.3 with HTTP; Sun, 11 Jan 2009 11:22:50 -0800 (PST) Message-ID: <7d6fde3d0901111122v3813fe3ehf75de6a2a7e66203@mail.gmail.com> Date: Sun, 11 Jan 2009 11:22:50 -0800 From: "Garrett Cooper" To: "Pete French" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Cc: freebsd-stable@freebsd.org, drosih@rpi.edu, heliocentric@gmail.com, rblayzor.bulk@inoc.net Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jan 2009 19:22:53 -0000 On Sun, Jan 11, 2009 at 4:45 AM, Pete French wrote: >> I noticed a similar problem testing 7.1-RC1, It seemed to be a deep >> deadlock, as it was triggered by lighttpd doing kern_sendfile, and >> never returning. The side effects (being unable to create processes, >> etc) is similar. > > Interesting - did you get any responses from anyone else regarding > this ? My last box which locked up was essentialy idle, so I am very > surprised by all of this - also none of the heavilt loaded machines > (i.e. the actual webservers) have locked up. > > I am also surprised that this isn't more widely reported, as > the hardware is very common. The only oddity with ym compile > is that I set the CPUTYPE to 'core2' - that shouldnt have an effect, but > I will remove it anyway, just so I am actually building a completely > vanilla amd64. That way I should have what everyone else has, and since > I don't see anyone else saying they have isues then maybe mine will > go away too (fingers crossed) > >> My kernconf is below, try building the kernel, and send an email >> containing the backtrace from any process that has blocked (in my > > OK, will do. I can try this on the one non-essential box which > locked up yesterday. I don't know how long it will before it > locks up again, but will see if I can do some things to provoke it. > > -pete. Intel suggests nocona for x86_64 platforms and prescott for x86 (i386) based platforms on the 4.2 line, because they best matched the cache size and featureset of the Core2 processors. I don't think that core2 support was fully completed in 4.2 (in fact I believe it was just started), and I don't think that our binutils supports it properly. Some thoughts, -Garrett From owner-freebsd-stable@FreeBSD.ORG Mon Jan 12 01:11:55 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 09AAB1065676 for ; Mon, 12 Jan 2009 01:11:55 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.229]) by mx1.freebsd.org (Postfix) with ESMTP id C384D8FC19 for ; Mon, 12 Jan 2009 01:11:54 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so11923324rvf.43 for ; Sun, 11 Jan 2009 17:11:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=Vy7kuZQfbgh08F/Q1i6NB9U2/lPirpEtBwLyRWsZnPw=; b=UZcdIOOajTG2UKTWb8lZprLcwqhPDjtejEGgHzPmHJT6kv4ehYTvoAo+2H2eSmbNpt 6ytVYomws6LeN7EoCKAP5Ntsz4xOYOyEUPXyOhNXvw0JkcfH11gPhd5tOI0uDidDkdCP UoE88Wc0ONLY7BB/rUYSsjldI932ysenREWvs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=FkYMR9lG4lgIbrh10/XmChOH68+8511MQtIsnoXSocTDTcrEmDVX5bIWmJRduq6+8g Iiv7htlfBkiNU4CJIxkw1Ke6kEywLTO0+IteOKX6UKTbBmEYRVob4raA3PhpGSpFUDbq n+GLA7gi7naDW0qAFK78pqTfVhs0cUm1WH7Gk= Received: by 10.140.202.21 with SMTP id z21mr5936835rvf.260.1231722714368; Sun, 11 Jan 2009 17:11:54 -0800 (PST) Received: from michelle.cdnetworks.co.kr ([211.53.35.84]) by mx.google.com with ESMTPS id b39sm37023762rvf.0.2009.01.11.17.11.52 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 11 Jan 2009 17:11:53 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.14.3/8.14.3) with ESMTP id n0C1Bmb2046670 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 Jan 2009 10:11:48 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.14.3/8.14.3/Submit) id n0C1Bko0046669; Mon, 12 Jan 2009 10:11:46 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Mon, 12 Jan 2009 10:11:46 +0900 From: Pyun YongHyeon To: Eugene Gladchenko Message-ID: <20090112011146.GC46346@cdnetworks.co.kr> References: <8dfae1c10901070639x67945324jeeecfcac647d7976@mail.gmail.com> <8dfae1c10901071550s69d99802p31ca7c775f3d6823@mail.gmail.com> <88527079.20090111192206@donpac.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <88527079.20090111192206@donpac.ru> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 7.1 Breaks re and rl Network Interface Drivers X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2009 01:11:56 -0000 On Sun, Jan 11, 2009 at 07:22:06PM +0300, Eugene Gladchenko wrote: > Walter, > > Thursday, January 8, 2009, 2:50:40 AM, you wrote: > > WV> Booting kernel.old, which is 7.0-RELEASE-p7 completely alleviates all > WV> problems. I believe this roundly confirms that this is a bug in the > WV> 7.1-RELEASE re kernel drivers. > > Does kern/130011 look similar? http://www.freebsd.org/cgi/query-pr.cgi?pr=130011 Do you have RTL8168C controller? If not, it's not related with Walter's issue as 7.0-RELEASE didn't have a support for RTL8168C. > > The re driver was really broken in 7.1-RC2 and the fix didn't get to 7.1-RELEASE. If you have re(4) issues, please provide more details such as dmesg output, way to reproduce the issue etc. -- Regards, Pyun YongHyeon From owner-freebsd-stable@FreeBSD.ORG Mon Jan 12 04:32:35 2009 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 811EB106564A; Mon, 12 Jan 2009 04:32:35 +0000 (UTC) (envelope-from uwe@laverenz.de) Received: from mo-p00-ob.rzone.de (mo-p00-ob.rzone.de [81.169.146.160]) by mx1.freebsd.org (Postfix) with ESMTP id A640A8FC17; Mon, 12 Jan 2009 04:32:34 +0000 (UTC) (envelope-from uwe@laverenz.de) X-RZG-CLASS-ID: mo00 X-RZG-AUTH: :LWgJfE6Id/4Sm/WkdV0gEbKL+/p/UjmosA/b4BPf1Ida/LA6f2SjtTTKgA== Received: from athena.laverenz.de ([77.22.195.173]) by post.strato.de (mrclete mo49) (RZmta 18.8) with ESMTP id Y040fdl0C4BrLU ; Mon, 12 Jan 2009 05:32:32 +0100 (MET) Received: from localhost (localhost.localdomain [127.0.0.1]) by athena.laverenz.de (Postfix) with ESMTP id 5D0C8613CF; Mon, 12 Jan 2009 05:29:46 +0100 (CET) Received: from athena.laverenz.de ([127.0.0.1]) by localhost (athena [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 05323-04; Mon, 12 Jan 2009 05:29:45 +0100 (CET) Received: by athena.laverenz.de (Postfix, from userid 2000) id 82582613CE; Mon, 12 Jan 2009 05:29:45 +0100 (CET) Date: Mon, 12 Jan 2009 05:29:45 +0100 From: Uwe Laverenz To: Robert Noland Message-ID: <20090112042945.GA7583@laverenz.de> Mail-Followup-To: Robert Noland , freebsd-stable , freebsd-x11 References: <1231599679.1837.13.camel@wombat.2hip.net> <1231606142.1837.34.camel@wombat.2hip.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1231606142.1837.34.camel@wombat.2hip.net> Organization: private site Sender: uwe@laverenz.de User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at laverenz.de Cc: freebsd-x11 , freebsd-stable Subject: Re: [HEADS UP] drm merged to -STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2009 04:32:36 -0000 On Sat, Jan 10, 2009 at 11:49:01AM -0500, Robert Noland wrote: > > If you are experiencing a "garbled" screen with certain pci/pci-e based > > radeons, I have another patch in HEAD that isn't included yet. > > I decided to go ahead and fully sync to HEAD, so this should be resolved > as well. This added: Thank you! :) bye, Uwe From owner-freebsd-stable@FreeBSD.ORG Mon Jan 12 06:22:45 2009 Return-Path: Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B9F28106566B for ; Mon, 12 Jan 2009 06:22:45 +0000 (UTC) (envelope-from antik@bsd.ee) Received: from sorbesgroup.com (mail.sorbesgroup.com [217.159.241.118]) by mx1.freebsd.org (Postfix) with ESMTP id 4667B8FC13 for ; Mon, 12 Jan 2009 06:22:45 +0000 (UTC) (envelope-from antik@bsd.ee) Received: from localhost (localhost.localdomain [127.0.0.1]) by sorbesgroup.com (Postfix) with ESMTP id 0A7623C511DA; Mon, 12 Jan 2009 08:14:00 +0200 (EET) Received: from sorbesgroup.com ([127.0.0.1]) by localhost (sorbesgroup.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 20660-02; Mon, 12 Jan 2009 08:13:59 +0200 (EET) Received: from [192.168.0.80] (andrei [192.168.0.80]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by sorbesgroup.com (Postfix) with ESMTP id 6A02F3C511AA; Mon, 12 Jan 2009 08:13:59 +0200 (EET) Message-ID: <496AE1AF.9060104@bsd.ee> Date: Mon, 12 Jan 2009 08:22:40 +0200 From: Andrei Kolu User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Mike Lempriere , freebsd@byshenk.net, freebsd-stable@FreeBSD.ORG References: <200901081047.n08Alg2h000825@lurza.secnetix.de> <496819F0.9@vintners.net> In-Reply-To: <496819F0.9@vintners.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at localhost Cc: Subject: Re: mergemaster broken -- take 2 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2009 06:22:46 -0000 Mike Lempriere wrote: > Thanks everyone for the advice -- I got it working this time just > fine. Works much better when one follows the directions accurately > instead of by memory -- the bottom line is that this time I remembered > to jot down the commands before heading downtown to the machine rack > room where there's no browser access... I started over and followed > UPDATING: > cd /usr/obj > rm -R * > cd /usr/src > rm -R * > cvsup -g -L 2 -h cvsup10.freebsd.org |& tee /root/cvsup-090108.out > make buildworld |& tee /root/make-buildworld-090108.out > make kernel KERNCONF=GENERIC |& tee /root/make-kernel-090108.out > users > ps ax | more > shutdown -r now You can go into single user without rebooting just by issuing command: # shutdown now NOTE: Network access will be shut down also, so you should be on your console then. > 4 (single user) > fsck -p > mount -u / > mount -a > cd /usr/src > mergemaster -p > make installworld |& tee /root/make-installworld-090108.out > make delete-old (forgot to do tee redirect) > mergemaster -i (did not do tee redirect) > shutdown -r now > > Oliver Fromme wrote: >> Greg Byshenk wrote: >> > Andrei Kolu wrote: >> > > Mike Lempriere wrote: >> > > > Hi folks -- sorry to be a nag, but my main production system >> is barely > > > limping along on an old kernel with mismatched >> libraries. I have no > > > idea what else to do -- please help! >> > > > --- >> > > > I'm upgrading 5-stable (was at 5.5) to 6-stable, in >> preparation for > > > 6-stable to 7-stable. >> > > > No problems with cvsup, make buildworld, make installworld, >> make > > > buildkernel, mergemaster -p. >> > > > make installkernel, boot to single user. Then mergemaster -- >> blammo: >> >> As others have pointed out, the order is wrong, which caused >> the problem Mike is seeing. >> >> The correct order is listed in /usr/src/UPDATING. >> >> > The reasons for the other methods being wrong are (as I understand >> them): >> > > - You should build your new world before building your new >> kernel, as >> > it may be the case that some aspects of the new kernel build are >> > dependent upon aspects of the new world build. If you build your >> > new kernel before building your new world, you will be building >> > your new kernel against the old world. >> >> In particular, building the kernel uses the new toolchain >> (i.e. compiler, linker, make(1) binary and so on) that was >> built in /usr/obj during buildworld. That's why you have >> to do buildworld first, then "make kernel". >> >> > - You should install your new kernel before installing your new >> world, >> > as it can be the case that some aspects of the new world will >> not be >> > understood by your old kernel. A new kernel should always be >> > compatible with an old userland/world, but an old kernel may not >> > always be compatible with a new userland/world. >> >> That's correct. Note that your kernel config should include >> the appropriate "options COMPAT_*" lines if you update across >> a major version boundary, e.g. "options_COMPAT_FREEBSD6" when >> you update from 6.x to 7.x. The GENERIC kernel already has >> those. >> >> > > NOTE: I do not reboot my system until everything is updated. Why >> it is > > necessary to boot new kernel and then upgrade world is >> beyound me..YMMW >> > > - I suppose that it is not strictly necessary to reboot between >> > installing kernel and world, but I always do so. >> >> It _is_ necessary. If you don't reboot, you're still running >> the old kernel which might not be able to support new binaries >> and libraries that installworld will install on your system. >> >> For example, there may be new syscalls that the new binaries >> will try to use, but the old kernel doesn't know about them. >> It doesn't happen often, so you can get away without rebooting >> most of the time. But it's risky, especially when updating >> across major versions. So the recommendation is to always >> reboot after installing the new kernel and before performing >> the "installworld". >> >> It's also important that "installworld" is the last step >> (except for mergemaster), because this is the point of no >> return. As long as you still have the old userland (world), >> you can still boot the old kernel and everything is fine. >> You can start all over froms cratch, if necessary. >> But as soon as you have started "installworld", your system >> will not be able to work with the old kernel anymore. >> >> And remember: Always make a backup before you start to >> update. And verify that the backup works. Better safe >> than sorry. >> >> Best regards >> Oliver >> >> > From owner-freebsd-stable@FreeBSD.ORG Mon Jan 12 06:41:33 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3E45D106564A for ; Mon, 12 Jan 2009 06:41:33 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.237]) by mx1.freebsd.org (Postfix) with ESMTP id 011D78FC08 for ; Mon, 12 Jan 2009 06:41:32 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so12025833rvf.43 for ; Sun, 11 Jan 2009 22:41:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=gf8xLE5E4tNRQmOuCQL0xh8yBKpbitErnYXemQXV/Yw=; b=dulvhp48/4WjBnyZOaoodQvzlPFCtsPw8r2Uqw42wNKJtrT6v1tFxtqhactnaFeo1A GDdCEjKg6oP3M1W+vAaLwLLUlbHQ2KcYWjClTiIvQ5cir+F3hgnUlhOS/flqcaM02BJM wq0jUhZdWgVBOBwNlaMC4Ggvp2u9wsnEEoacQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=n7FDfg//eKgr44kp+eaGxYT/oZUnkCOrf2442KRvMsTyNPpmd+QrOeQ+Ul74A5X6Y4 y5KsGXPCYjBTpk8VcFuvkjiXOnsGuag7/IWIpEyNkMt5d4HF1i2dKr1EZ7IcWLWF5W2J Yu1o75sncDgdc4XXbW9zVfVzbIZ2Gj6L/lD38= Received: by 10.141.168.2 with SMTP id v2mr14247166rvo.47.1231742492585; Sun, 11 Jan 2009 22:41:32 -0800 (PST) Received: from michelle.cdnetworks.co.kr ([211.53.35.84]) by mx.google.com with ESMTPS id b39sm37372382rvf.0.2009.01.11.22.41.29 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 11 Jan 2009 22:41:31 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.14.3/8.14.3) with ESMTP id n0C6fM6s047754 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 Jan 2009 15:41:22 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.14.3/8.14.3/Submit) id n0C6fLkJ047753; Mon, 12 Jan 2009 15:41:21 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Mon, 12 Jan 2009 15:41:21 +0900 From: Pyun YongHyeon To: eugene@donpac.ru Message-ID: <20090112064121.GF46346@cdnetworks.co.kr> References: <8dfae1c10901070639x67945324jeeecfcac647d7976@mail.gmail.com> <8dfae1c10901071550s69d99802p31ca7c775f3d6823@mail.gmail.com> <88527079.20090111192206@donpac.ru> <20090112011146.GC46346@cdnetworks.co.kr> <64114.83.221.215.168.1231741940.squirrel@83.221.215.168> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <64114.83.221.215.168.1231741940.squirrel@83.221.215.168> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 7.1 Breaks re and rl Network Interface Drivers X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2009 06:41:33 -0000 On Mon, Jan 12, 2009 at 09:32:20AM +0300, eugene@donpac.ru wrote: > EG>> Does kern/130011 look similar? > EG>> http://www.freebsd.org/cgi/query-pr.cgi?pr=130011 > > > Do you have RTL8168C controller? If not, it's not related with > > Walter's issue as 7.0-RELEASE didn't have a support for RTL8168C. > > Look into kern/130011. As far as I can see I do have RTL8168C. > > EG>> The re driver was really broken in 7.1-RC2 and the fix didn't get > EG>> to 7.1-RELEASE. > > > If you have re(4) issues, please provide more details such as > > dmesg output, way to reproduce the issue etc. > > The issue is now gone but I am sorry 7.1 didn't get the fix in time. > I see, Unfortunately the issue was fixed in the end of 7.1-R release process so I wanted to get more exposure before MFC. I'll make sure to MFC to stable/7 after more testing. -- Regards, Pyun YongHyeon From owner-freebsd-stable@FreeBSD.ORG Mon Jan 12 06:50:37 2009 Return-Path: Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D6520106566C for ; Mon, 12 Jan 2009 06:50:37 +0000 (UTC) (envelope-from oberman@es.net) Received: from postal1.es.net (postal4.es.net [198.124.252.66]) by mx1.freebsd.org (Postfix) with ESMTP id 934D48FC19 for ; Mon, 12 Jan 2009 06:50:37 +0000 (UTC) (envelope-from oberman@es.net) Received: from postal1.es.net (postal3.es.net [198.128.3.207]) by postal4.es.net (Postal Node 4) with ESMTP (SSL) id THA03509; Sun, 11 Jan 2009 22:40:09 -0800 Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by postal3.es.net (Postal Node 3) with ESMTP (SSL) id THA69107; Sun, 11 Jan 2009 22:40:07 -0800 Received: from ptavv.es.net (ptavv.es.net [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 8463E1CC0B; Sun, 11 Jan 2009 22:40:07 -0800 (PST) To: Andrei Kolu In-Reply-To: Your message of "Mon, 12 Jan 2009 08:22:40 +0200." <496AE1AF.9060104@bsd.ee> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1231742407_89602P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Sun, 11 Jan 2009 22:40:07 -0800 From: "Kevin Oberman" Message-Id: <20090112064007.8463E1CC0B@ptavv.es.net> X-Sender-IP: 198.128.3.207 X-Sender-Domain: es.net X-Recipent: ; ; ; ; X-Sender: X-To_Name: Andrei Kolu X-To_Domain: bsd.ee X-To: Andrei Kolu X-To_Email: antik@bsd.ee X-To_Alias: antik Cc: Mike Lempriere , freebsd-stable@FreeBSD.ORG, freebsd@byshenk.net Subject: Re: mergemaster broken -- take 2 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2009 06:50:38 -0000 --==_Exmh_1231742407_89602P Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > Date: Mon, 12 Jan 2009 08:22:40 +0200 > From: Andrei Kolu > Sender: owner-freebsd-stable@freebsd.org > > Mike Lempriere wrote: > > Thanks everyone for the advice -- I got it working this time just > > fine. Works much better when one follows the directions accurately > > instead of by memory -- the bottom line is that this time I remembered > > to jot down the commands before heading downtown to the machine rack > > room where there's no browser access... I started over and followed > > UPDATING: > > cd /usr/obj > > rm -R * > > cd /usr/src > > rm -R * > > cvsup -g -L 2 -h cvsup10.freebsd.org |& tee /root/cvsup-090108.out > > make buildworld |& tee /root/make-buildworld-090108.out > > make kernel KERNCONF=GENERIC |& tee /root/make-kernel-090108.out > > users > > ps ax | more > > shutdown -r now > You can go into single user without rebooting just by issuing command: > > # shutdown now > > NOTE: Network access will be shut down also, so you should be on your > console then. Did you even bother reading Oliver's explanation as to why it's a very bad idea. The official upgrade procedure can be modified if you know EXACTLY what you are doing, but it is unwise to suggest that you can go ahead without adequate knowledge of the risks. Please don't suggest skipping the reboot. Feel free to do so yourself, but don't expect much sympathy when an upgrade blows up and a system is down for several hours while you clean up the mess. > >> It _is_ necessary. If you don't reboot, you're still running > >> the old kernel which might not be able to support new binaries > >> and libraries that installworld will install on your system. > >> > >> For example, there may be new syscalls that the new binaries > >> will try to use, but the old kernel doesn't know about them. > >> It doesn't happen often, so you can get away without rebooting > >> most of the time. But it's risky, especially when updating > >> across major versions. So the recommendation is to always > >> reboot after installing the new kernel and before performing > >> the "installworld". > >> > >> It's also important that "installworld" is the last step > >> (except for mergemaster), because this is the point of no > >> return. As long as you still have the old userland (world), > >> you can still boot the old kernel and everything is fine. > >> You can start all over froms cratch, if necessary. > >> But as soon as you have started "installworld", your system > >> will not be able to work with the old kernel anymore. > >> > >> And remember: Always make a backup before you start to > >> update. And verify that the backup works. Better safe > >> than sorry. > >> > >> Best regards > >> Oliver > >> > >> > > > > _______________________________________________ > 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" > --==_Exmh_1231742407_89602P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) Comment: Exmh version 2.5 06/03/2002 iD8DBQFJauXHkn3rs5h7N1ERAgbHAJwNL12u4Thb6KBsdXs8Ay1KSTjQtgCdH+of O10gVZ2J6mJR5UEzhzRiksA= =Ok7x -----END PGP SIGNATURE----- --==_Exmh_1231742407_89602P-- From owner-freebsd-stable@FreeBSD.ORG Mon Jan 12 07:26:48 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 40CBC1065673 for ; Mon, 12 Jan 2009 07:26:48 +0000 (UTC) (envelope-from eugene@donpac.ru) Received: from mail.donpac.ru (mail.donpac.ru [80.254.111.2]) by mx1.freebsd.org (Postfix) with ESMTP id D69968FC0C for ; Mon, 12 Jan 2009 07:26:47 +0000 (UTC) (envelope-from eugene@donpac.ru) Received: from mail.donpac.ru ([80.254.111.2]) by smtp.donpac.ru with esmtp on port 25 (Exim 4.67) id 1LMGLU-0000YT-SN; Mon, 12 Jan 2009 09:32:21 +0300 Received: from 83.221.215.168 (SquirrelMail authenticated user eugene); by localhost with HTTP; Mon, 12 Jan 2009 09:32:20 +0300 (MSK) Message-ID: <64114.83.221.215.168.1231741940.squirrel@83.221.215.168> In-Reply-To: <20090112011146.GC46346@cdnetworks.co.kr> References: <8dfae1c10901070639x67945324jeeecfcac647d7976@mail.gmail.com> <8dfae1c10901071550s69d99802p31ca7c775f3d6823@mail.gmail.com> <88527079.20090111192206@donpac.ru> <20090112011146.GC46346@cdnetworks.co.kr> Date: Mon, 12 Jan 2009 09:32:20 +0300 (MSK) From: eugene@donpac.ru To: pyunyh@gmail.com User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 7.1 Breaks re and rl Network Interface Drivers X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2009 07:26:48 -0000 EG>> Does kern/130011 look similar? EG>> http://www.freebsd.org/cgi/query-pr.cgi?pr=130011 > Do you have RTL8168C controller? If not, it's not related with > Walter's issue as 7.0-RELEASE didn't have a support for RTL8168C. Look into kern/130011. As far as I can see I do have RTL8168C. EG>> The re driver was really broken in 7.1-RC2 and the fix didn't get EG>> to 7.1-RELEASE. > If you have re(4) issues, please provide more details such as > dmesg output, way to reproduce the issue etc. The issue is now gone but I am sorry 7.1 didn't get the fix in time. -- Eugene Gladchenko EVG15-RIPE From owner-freebsd-stable@FreeBSD.ORG Mon Jan 12 08:09:57 2009 Return-Path: Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D414C106566C for ; Mon, 12 Jan 2009 08:09:57 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (unknown [IPv6:2a01:170:102f::2]) by mx1.freebsd.org (Postfix) with ESMTP id 5623D8FC17 for ; Mon, 12 Jan 2009 08:09:57 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.3/8.14.3) with ESMTP id n0C89tkd054680; Mon, 12 Jan 2009 09:09:55 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.3/8.14.3/Submit) id n0C89sib054679; Mon, 12 Jan 2009 09:09:54 +0100 (CET) (envelope-from olli) Date: Mon, 12 Jan 2009 09:09:54 +0100 (CET) Message-Id: <200901120809.n0C89sib054679@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG, msnkipa@mail.ru In-Reply-To: X-Newsgroups: list.freebsd-stable User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (FreeBSD/6.4-PRERELEASE-20080904 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Mon, 12 Jan 2009 09:09:55 +0100 (CET) Cc: Subject: Re: ZFSv13 in RELENG7 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG, msnkipa@mail.ru List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2009 08:09:58 -0000 msnkipa@mail.ru wrote: > Is any plans to backport ZFSv13 from CURRENT to RELENG7 branxh or not? AFAIR Pawel explained that he intends to backport it to RELENG7, but it will take some time because it is a huge amount of code. Also, it depends on other merges from -current by other people that are not directly ZFS-related. Therefore the time frame is currently unknown. On the other hand, 8-current seems to run quite stable at the moment; I have it running on a workstation for several weeks without problems. So if you're eager to try ZFS 13, you might consider upgrading to -current. Also note that there are improvements in -current (by Alan Cox) that fix issues related to kmem in 64bit mode (FreeBSD/amd64). ZFS will very much benefit from those improvements; you don't have to tune kmem anymore in order to avoid panics. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd Python is executable pseudocode. Perl is executable line noise. From owner-freebsd-stable@FreeBSD.ORG Mon Jan 12 10:38:08 2009 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CD4DE106566B for ; Mon, 12 Jan 2009 10:38:08 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from mail-gw0.york.ac.uk (mail-gw0.york.ac.uk [144.32.128.245]) by mx1.freebsd.org (Postfix) with ESMTP id 62E7E8FC08 for ; Mon, 12 Jan 2009 10:38:07 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from mail-gw6.york.ac.uk (mail-gw6.york.ac.uk [144.32.129.26]) by mail-gw0.york.ac.uk (8.13.6/8.13.6) with ESMTP id n0CAc54w015215; Mon, 12 Jan 2009 10:38:05 GMT Received: from buffy-128.york.ac.uk ([144.32.128.160] helo=buffy.york.ac.uk) by mail-gw6.york.ac.uk with esmtps (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from ) id 1LMKBJ-0000KL-D2; Mon, 12 Jan 2009 10:38:05 +0000 Received: from buffy.york.ac.uk (localhost [127.0.0.1]) by buffy.york.ac.uk (8.14.2/8.14.2) with ESMTP id n0CAc45I060239; Mon, 12 Jan 2009 10:38:04 GMT (envelope-from gavin@FreeBSD.org) Received: (from ga9@localhost) by buffy.york.ac.uk (8.14.2/8.14.2/Submit) id n0CAc4I2060238; Mon, 12 Jan 2009 10:38:04 GMT (envelope-from gavin@FreeBSD.org) X-Authentication-Warning: buffy.york.ac.uk: ga9 set sender to gavin@FreeBSD.org using -f From: Gavin Atkinson To: Pete French In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Mon, 12 Jan 2009 10:38:04 +0000 Message-Id: <1231756684.59797.1.camel@buffy.york.ac.uk> Mime-Version: 1.0 X-Mailer: Evolution 2.22.2 FreeBSD GNOME Team Port X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin@freebsd.org Cc: freebsd-stable@FreeBSD.org Subject: Re: Lock order reversals using bce in 7.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2009 10:38:09 -0000 On Sun, 2009-01-11 at 17:16 +0000, Pete French wrote: > Here is a better set of images. This machine was compiled > with the following config file: > > include GENERIC > ident DEBUG > > options KDB > options DDB > options SW_WATCHDOG > options DEBUG_VFS_LOCKS > options MUTEX_DEBUG > options WITNESS > options WITNESS_KDB You don't want WITNESS_KDB, but WITNESS_SKIPSPIN would probably be sensible to include. > options LOCK_PROFILING > options INVARIANTS > options INVARIANT_SUPPORT > options DIAGNOSTIC > > On booting it almost immediately does this: > > http://www.twisted.org.uk/~pete/71_lor.png That's due to WITNESS_KDB and probably unrelated to your problems. Gavin From owner-freebsd-stable@FreeBSD.ORG Mon Jan 12 10:38:49 2009 Return-Path: Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 42180106566C for ; Mon, 12 Jan 2009 10:38:49 +0000 (UTC) (envelope-from andrew@modulus.org) Received: from email.octopus.com.au (email.octopus.com.au [122.100.2.232]) by mx1.freebsd.org (Postfix) with ESMTP id 03D038FC12 for ; Mon, 12 Jan 2009 10:38:48 +0000 (UTC) (envelope-from andrew@modulus.org) Received: by email.octopus.com.au (Postfix, from userid 1002) id 028D017E62; Mon, 12 Jan 2009 21:38:48 +1100 (EST) X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on email.octopus.com.au X-Spam-Level: X-Spam-Status: No, score=-1.4 required=10.0 tests=ALL_TRUSTED autolearn=failed version=3.2.3 Received: from [10.20.30.100] (60.218.233.220.exetel.com.au [220.233.218.60]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: admin@email.octopus.com.au) by email.octopus.com.au (Postfix) with ESMTP id D808317D39; Mon, 12 Jan 2009 21:38:44 +1100 (EST) Message-ID: <496B1DA8.5010407@modulus.org> Date: Mon, 12 Jan 2009 21:38:32 +1100 From: Andrew Snow User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG, msnkipa@mail.ru References: <200901120809.n0C89sib054679@lurza.secnetix.de> In-Reply-To: <200901120809.n0C89sib054679@lurza.secnetix.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: ZFSv13 in RELENG7 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2009 10:38:49 -0000 Oliver Fromme wrote: > On the other hand, 8-current seems to run quite stable at > the moment; I have it running on a workstation for several > weeks without problems. What date of CURRENT are you running? I tracked down crashes related to changes in SMBFS, but I am still experiencing almost weekly crashes such as machine running out of swap space in the middle of the night for no apparent reason.. From owner-freebsd-stable@FreeBSD.ORG Mon Jan 12 11:21:16 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BF0AD10657C6 for ; Mon, 12 Jan 2009 11:21:16 +0000 (UTC) (envelope-from spry@anarchy.in.the.ph) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.155]) by mx1.freebsd.org (Postfix) with ESMTP id 3FB428FC14 for ; Mon, 12 Jan 2009 11:21:16 +0000 (UTC) (envelope-from spry@anarchy.in.the.ph) Received: by fg-out-1718.google.com with SMTP id l26so3649722fgb.35 for ; Mon, 12 Jan 2009 03:21:15 -0800 (PST) Received: by 10.86.91.12 with SMTP id o12mr922199fgb.16.1231759275237; Mon, 12 Jan 2009 03:21:15 -0800 (PST) Received: by 10.86.77.20 with HTTP; Mon, 12 Jan 2009 03:21:15 -0800 (PST) Message-ID: Date: Mon, 12 Jan 2009 19:21:15 +0800 From: "Mars G Miro" To: "Jack Vogel" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2a41acea0901080844y1c2ad632t12aeadfbe9f34d0a@mail.gmail.com> <2a41acea0901081033h7db7a1aej8399baf5dcbd270f@mail.gmail.com> <2a41acea0901090115q6af9f364qac23a8cce444d27a@mail.gmail.com> Cc: freebsd-stable@freebsd.org Subject: Re: igb on a Nehalem system, buildworld stats X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2009 11:21:26 -0000 On Fri, Jan 9, 2009 at 6:22 PM, Mars G Miro wrote: > On Fri, Jan 9, 2009 at 6:14 PM, Mars G Miro wrote: >> On Fri, Jan 9, 2009 at 5:15 PM, Jack Vogel wrote: >>> >> [snip] >>>> >> >>>> >> If you have a back to back connection to another NIC on Port 0, no >>>> >> switch, >>>> >> does >>>> >> it still autoneg to 100? >>>> >> >>>> >>>> Connected back to back w/ another box w/ a GigE NIC, it now does >>>> 1000baseTX: >>>> >>>> igb0: flags=8843 metric 0 mtu 1500 >>>> options=19b >>>> ether 00:30:48:c5:db:e2 >>>> inet6 fe80::230:48ff:fec5:dbe2%igb0 prefixlen 64 scopeid 0x1 >>>> inet 192.168.70.2 netmask 0xffffff00 broadcast 192.168.70.255 >>>> media: Ethernet autoselect (1000baseTX ) >>>> status: active >>>> >>>> But still not without problems. I hafta ifconfig down/up it several >>>> times until I can see the other end. W/c is the same for igb1. >>> >>> >>> OK, so you have some switch issue. What do you mean "see the other end", >>> if its back to back and boots up I assume it gets link, if you have the >>> address >>> assigned in rc.conf, and you run tcpdump on the partner do you see the arp >>> when it comes online, and at that point can the other side ping it? >>> >> >> By 'see the other end' , I meant that even if It says 1000baseTX, i >> still can't ping the other end, well not really, as I can now see it >> gots bad chksums: >> >> 1. 001691 00:30:48:c5:db:e2 > ff:ff:ff:ff:ff:ff, ethertype ARP >> (0x0806), length 60: arp who-has 192.168.70.2 tell 192.168.70.2 >> 1. 511111 00:30:48:c5:db:e2 > 00:30:48:61:d7:f2, ethertype IPv4 >> (0x0800), length 98: (tos 0x0, ttl 64, id 20346, offset 0, flags >> [none], proto ICMP (1), length 84) 192.168.70.2 > 192.168.70.1: ICMP >> echo request, id 14852, seq 0, length 64 >> 000012 00:30:48:61:d7:f2 > 00:30:48:c5:db:e2, ethertype IPv4 (0x0800), >> length 98: (tos 0x0, ttl 64, id 3034, offset 0, flags [none], proto >> ICMP (1), length 84, bad cksum 0 (->617b)!) 192.168.70.1 > >> 192.168.70.2: ICMP echo reply, id 14852, seq 0, length 64 >> 1. 001611 00:30:48:c5:db:e2 > 00:30:48:61:d7:f2, ethertype IPv4 >> (0x0800), length 98: (tos 0x0, ttl 64, id 57773, offset 0, flags >> [none], proto ICMP (1), length 84) 192.168.70.2 > 192.168.70.1: ICMP >> echo request, id 14852, seq 1, length 64 >> 000011 00:30:48:61:d7:f2 > 00:30:48:c5:db:e2, ethertype IPv4 (0x0800), >> length 98: (tos 0x0, ttl 64, id 59591, offset 0, flags [none], proto >> ICMP (1), length 84, bad cksum 0 (->848d)!) 192.168.70.1 > >> 192.168.70.2: ICMP echo reply, id 14852, seq 1, length 64 >> >> and this is back to back w/ another box w/ a GigE NIC (nfe, w/c has >> been in production for some time) >> >>> Oh, and what is the link partner hardware? >>> >> >> The switch? it's a Dlink 48-Port DGS-1248T GigE switch. >> >> Thanks. >> > > btw, I tried 200812-CURRENT and CURRENT as of Jan 7 and the behavior > is still the same :-( > > Hi again, We installed Windows 7 BETA on it, and altho the 1st NIC behaves the same way, e.g. if connected to a switch it stays at 100mbps, but if connected back to back w/ another GigE it can stay at 1.0Gbps, I do not get any network problems at all, for both igb NICs. So, something to do w/ the igb driver then ? Thanks. >>> Jack >>> -- cheers mars From owner-freebsd-stable@FreeBSD.ORG Mon Jan 12 11:28:13 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D7D6C1065678 for ; Mon, 12 Jan 2009 11:28:13 +0000 (UTC) (envelope-from kometen@gmail.com) Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.186]) by mx1.freebsd.org (Postfix) with ESMTP id 5C11A8FC17 for ; Mon, 12 Jan 2009 11:28:13 +0000 (UTC) (envelope-from kometen@gmail.com) Received: by mu-out-0910.google.com with SMTP id i2so4663493mue.3 for ; Mon, 12 Jan 2009 03:28:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=bl3RLPFXwDJBSA5aNkQGt5Rq0sqR7yUF9k7obLIbC9M=; b=XOlMuf6fcUAKSIl01Bmnc2JJG2kjcsVmfgUMce6AUh33mNiVBKwBrdvy6zc9FNNvtv sTaIibXCevJNRZdZoqyAkpwDz5IXdt0Wb7KMQ61J9wEpabVFhf0821jAylR7nctTaQ4V jC2usbhhL9s6doOWEcVLXiS55hYq1QUrH5Fe8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=BF2UmOeC59K+vBxTaW2uklwpcAm4MXL92Vzf1Mki817FQNzkMByveVrMcipxiTB6SU OkAaoJyNE9Hm8va5aR/OAcB73szF3a4M2mMtQWFRiqsi0B9RRdCBscYn8f9HqtIJLzw7 zWFVSW/mKpxzmYpL4CW/WTWTVaVLTdzbAQNTA= Received: by 10.103.160.9 with SMTP id m9mr10313131muo.96.1231759690248; Mon, 12 Jan 2009 03:28:10 -0800 (PST) Received: by 10.102.244.13 with HTTP; Mon, 12 Jan 2009 03:28:09 -0800 (PST) Message-ID: Date: Mon, 12 Jan 2009 12:28:09 +0100 From: "Claus Guttesen" To: "Garrett Cooper" In-Reply-To: <7d6fde3d0901111122v3813fe3ehf75de6a2a7e66203@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <7d6fde3d0901111122v3813fe3ehf75de6a2a7e66203@mail.gmail.com> Cc: freebsd-stable@freebsd.org Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2009 11:28:17 -0000 >> I am also surprised that this isn't more widely reported, as >> the hardware is very common. The only oddity with ym compile >> is that I set the CPUTYPE to 'core2' - that shouldnt have an effect, but >> I will remove it anyway, just so I am actually building a completely >> vanilla amd64. That way I should have what everyone else has, and since >> I don't see anyone else saying they have isues then maybe mine will >> go away too (fingers crossed) >> > Intel suggests nocona for x86_64 platforms and prescott for x86 > (i386) based platforms on the 4.2 line, because they best matched the > cache size and featureset of the Core2 processors. > > I don't think that core2 support was fully completed in 4.2 (in > fact I believe it was just started), and I don't think that our > binutils supports it properly. > > Some thoughts, > -Garrett I've updagraded a test-webserver to 7.1 when it was released. After a few days I upgraded a production-webserver to 7.1 on Jan. 8'th and it has been running without any problems. The webserver is not heavily loaded (load at 2-3 on average). I have made a buildworld -j 8 and it runs fine. If the reported lockup is due to i/o a buildworld will not be able to reproduce it. It has performed a buildworld without problems and I'll be doing some buildworlds throughout the day. This is on a HP c-class-blade with 8 GB ram, 2 x quad-core and the build-in p200-controller with 64 MB ram. -- regards Claus When lenity and cruelty play for a kingdom, the gentler gamester is the soonest winner. Shakespeare From owner-freebsd-stable@FreeBSD.ORG Mon Jan 12 11:37:16 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 908A1106564A for ; Mon, 12 Jan 2009 11:37:16 +0000 (UTC) (envelope-from kometen@gmail.com) Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.190]) by mx1.freebsd.org (Postfix) with ESMTP id 1C4008FC17 for ; Mon, 12 Jan 2009 11:37:15 +0000 (UTC) (envelope-from kometen@gmail.com) Received: by fk-out-0910.google.com with SMTP id k31so6851332fkk.11 for ; Mon, 12 Jan 2009 03:37:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=SopZ7iukdg8hy7cGW02FIHDIaz2uKyFE9Em7j00J9qs=; b=TrPNwqBxPZqcpgHFPJentD6bH0Gb+Zj/BcdlUMLwHHmw3o7cv75rdaIGU75mn/Yf8M +EFj4OKdLBqsgL//GO1Cjv2wRLrEGjPD18H3+GtAVMFhL9RCbiHhrlA+/AL/xWFAFRVt HBRfXFY9489OzyzpBxxo+PyuyKQMpPS1Var5Y= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=WVMpgMn5qXzxHZ27zGJllM4zrxevoJ3kWbzO+/v9hpkiuZ9a9S2aLkf4b6Pc/s4hg3 dEdVOJ+CMKU4AMzMShUVVlcJ9OABvxqpFvPKYfThXqNml8OWpqv/L87YtOYnGS2GlJmE IQv8LodExQc3YwGBXuOvP81Yg9ouFK4JVfqMg= Received: by 10.103.172.7 with SMTP id z7mr10329852muo.15.1231760234850; Mon, 12 Jan 2009 03:37:14 -0800 (PST) Received: by 10.102.244.13 with HTTP; Mon, 12 Jan 2009 03:37:14 -0800 (PST) Message-ID: Date: Mon, 12 Jan 2009 12:37:14 +0100 From: "Claus Guttesen" To: "Garrett Cooper" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <7d6fde3d0901111122v3813fe3ehf75de6a2a7e66203@mail.gmail.com> Cc: freebsd-stable@freebsd.org Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2009 11:37:17 -0000 > I've updagraded a test-webserver to 7.1 when it was released. After a > few days I upgraded a production-webserver to 7.1 on Jan. 8'th and it > has been running without any problems. The webserver is not heavily > loaded (load at 2-3 on average). I have made a buildworld -j 8 and it > runs fine. > > If the reported lockup is due to i/o a buildworld will not be able to > reproduce it. > > It has performed a buildworld without problems and I'll be doing some > buildworlds throughout the day. > > This is on a HP c-class-blade with 8 GB ram, 2 x quad-core and the > build-in p200-controller with 64 MB ram. Forgot to add that CPUTYPE=nocona in /etc/make.conf. -- regards Claus When lenity and cruelty play for a kingdom, the gentler gamester is the soonest winner. Shakespeare From owner-freebsd-stable@FreeBSD.ORG Mon Jan 12 11:39:30 2009 Return-Path: Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 960561065672 for ; Mon, 12 Jan 2009 11:39:30 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (unknown [IPv6:2a01:170:102f::2]) by mx1.freebsd.org (Postfix) with ESMTP id 130298FC20 for ; Mon, 12 Jan 2009 11:39:29 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.3/8.14.3) with ESMTP id n0CBdPwq063546; Mon, 12 Jan 2009 12:39:28 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.3/8.14.3/Submit) id n0CBdO6L063545; Mon, 12 Jan 2009 12:39:24 +0100 (CET) (envelope-from olli) Date: Mon, 12 Jan 2009 12:39:24 +0100 (CET) Message-Id: <200901121139.n0CBdO6L063545@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG, andrew@modulus.org In-Reply-To: <496B1DA8.5010407@modulus.org> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (FreeBSD/6.4-PRERELEASE-20080904 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Mon, 12 Jan 2009 12:39:28 +0100 (CET) Cc: Subject: Re: ZFSv13 in RELENG7 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG, andrew@modulus.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2009 11:39:31 -0000 Andrew Snow wrote: > Oliver Fromme wrote: > > On the other hand, 8-current seems to run quite stable at > > the moment; I have it running on a workstation for several > > weeks without problems. > > What date of CURRENT are you running? I tracked down crashes related to > changes in SMBFS, but I am still experiencing almost weekly crashes such > as machine running out of swap space in the middle of the night for no > apparent reason.. $ uname -rs FreeBSD 8.0-CURRENT-20081128 $ uptime 12:23PM up 25 days, 22:07, 0 users, load averages: 0.00, 0.00, 0.00 I'm not using SMBFS, though. It's a workstation running typical desktop things (xterms, web browser, gimp, sane and similar). Best regards Oliver PS: Just in case someone wonders how to get timestamp suffixes to the kernel version string: I'm using this little script in place of "make kernel": http://www.secnetix.de/olli/scripts/makekernel -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "[...] one observation we can make here is that Python makes an excellent pseudocoding language, with the wonderful attribute that it can actually be executed." -- Bruce Eckel From owner-freebsd-stable@FreeBSD.ORG Mon Jan 12 11:55:02 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 437C71065673 for ; Mon, 12 Jan 2009 11:55:02 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id E64748FC1F for ; Mon, 12 Jan 2009 11:55:01 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from root by ciao.gmane.org with local (Exim 4.43) id 1LMLNm-0004ne-8e for freebsd-stable@freebsd.org; Mon, 12 Jan 2009 11:55:02 +0000 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 ; Mon, 12 Jan 2009 11:55:02 +0000 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 12 Jan 2009 11:55:02 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Ivan Voras Date: Mon, 12 Jan 2009 12:52:23 +0100 Lines: 37 Message-ID: References: <200901120809.n0C89sib054679@lurza.secnetix.de> <496B1DA8.5010407@modulus.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig3DC846FE1C5DFF94451A72A1" X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 2.0.0.18 (X11/20081125) In-Reply-To: <496B1DA8.5010407@modulus.org> X-Enigmail-Version: 0.95.0 Sender: news Subject: Re: ZFSv13 in RELENG7 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2009 11:55:02 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig3DC846FE1C5DFF94451A72A1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Andrew Snow wrote: > Oliver Fromme wrote: >> On the other hand, 8-current seems to run quite stable at >> the moment; I have it running on a workstation for several >> weeks without problems. >=20 > What date of CURRENT are you running? I tracked down crashes related t= o > changes in SMBFS, but I am still experiencing almost weekly crashes suc= h > as machine running out of swap space in the middle of the night for no > apparent reason.. Are you running rsync? Are the crashes happenning at about 3 am? (these two questions are unrelated) --------------enig3DC846FE1C5DFF94451A72A1 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJay73ldnAQVacBcgRAohFAJ4ghrduCDHXCZNPTtztOX8EVRYAnQCg0pBK ssZli1Vui9XoBxgDgB/osz4= =jWDd -----END PGP SIGNATURE----- --------------enig3DC846FE1C5DFF94451A72A1-- From owner-freebsd-stable@FreeBSD.ORG Mon Jan 12 10:49:14 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6B6A1106564A for ; Mon, 12 Jan 2009 10:49:14 +0000 (UTC) (envelope-from msnkipa@mail.ru) Received: from f106.mail.ru (f106.mail.ru [194.67.57.205]) by mx1.freebsd.org (Postfix) with ESMTP id B8FD38FC08 for ; Mon, 12 Jan 2009 10:49:10 +0000 (UTC) (envelope-from msnkipa@mail.ru) Received: from mail by f106.mail.ru with local id 1LMKLy-0003oq-00 for freebsd-stable@freebsd.org; Mon, 12 Jan 2009 13:49:06 +0300 Received: from [89.113.74.101] by win.mail.ru with HTTP; Mon, 12 Jan 2009 13:49:06 +0300 From: =?koi8-r?Q?=ED=C9=C8=C1=C9=CC_=EB=C9=D0=C1?= To: freebsd-stable@freebsd.org Mime-Version: 1.0 X-Mailer: mPOP Web-Mail 2.19 X-Originating-IP: 192.168.7.11 via proxy [89.113.74.101] Date: Mon, 12 Jan 2009 13:49:06 +0300 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Message-Id: X-Spam: Not detected X-Mras: Ok X-Mailman-Approved-At: Mon, 12 Jan 2009 12:47:23 +0000 Subject: NFSv4 server X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: =?koi8-r?Q?=ED=C9=C8=C1=C9=CC_=EB=C9=D0=C1?= List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2009 10:49:14 -0000 Is there any plans to include NFSv4 server into FreeBSD? From owner-freebsd-stable@FreeBSD.ORG Mon Jan 12 12:57:17 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1837E1065758 for ; Mon, 12 Jan 2009 12:57:17 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 2AC2C8FC17 for ; Mon, 12 Jan 2009 12:57:15 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id OAA11785 for ; Mon, 12 Jan 2009 14:57:12 +0200 (EET) (envelope-from avg@icyb.net.ua) Message-ID: <496B3E28.3070902@icyb.net.ua> Date: Mon, 12 Jan 2009 14:57:12 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.18 (X11/20081124) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: fsck_y_enable: suboptimal/odd? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2009 12:57:18 -0000 System: stable/7 some time before New Year (sorry if this issue has already been acted upon). I have a system with perhaps sufficiently rare configuration: it has fsck_y_enable="YES" and it has multiple filesystems mounted (UFS2), some RW, some RO. Today I had a chance to see fsck_y_enable in action. After a hard-lock followed by a reset normal fsck process started, several filesystems had "expected" inconsistencies and were successfully repaired, and then one filesystem had an unexpected inconsistency (partially truncated inode it was). After that normal fsck process was aborted and "fsck_y" process started. To much of my surprise it started all over - the filesystems that had been just successfully checked were being checked again. Even more - filesystems that had been mounted RO before the reset were also being checked. To me it seems like fsck_y passes suboptimal flags to fsck, it doesn't have to examine each and every filesystem in fstab. -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Mon Jan 12 13:30:13 2009 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7D6BB106566C; Mon, 12 Jan 2009 13:30:13 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from constantine.ticketswitch.com (constantine.ticketswitch.com [IPv6:2002:57e0:1d4e:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id 42A938FC0A; Mon, 12 Jan 2009 13:30:13 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from dilbert.rattatosk ([10.64.50.6] helo=dilbert.ticketswitch.com) by constantine.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LMMrp-000Blp-1x; Mon, 12 Jan 2009 13:30:09 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LMMrp-0000S9-0I; Mon, 12 Jan 2009 13:30:09 +0000 To: gavin@FreeBSD.org In-Reply-To: <1231756684.59797.1.camel@buffy.york.ac.uk> Message-Id: From: Pete French Date: Mon, 12 Jan 2009 13:30:09 +0000 Cc: freebsd-stable@FreeBSD.org Subject: Re: Lock order reversals using bce in 7.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2009 13:30:13 -0000 > You don't want WITNESS_KDB, but WITNESS_SKIPSPIN would probably be > sensible to include. OK, I will take out the WITNESS_KDB. I am reluctant to add in WITNESS_SKIPSPIN though, as I understand it stops witnessing spin locks, is that right ? As the only error message I have ever got out of all fo this explicitly mentioned spinlocks then I'd rather have them monitored. > That's due to WITNESS_KDB and probably unrelated to your problems. OK, will re-do all those tests - and also revert to the correct subject line for this thread (I am not quite sure why I typed a new one, it's a stupid thing to do as it makes it hard to follow). cheers, -pete. From owner-freebsd-stable@FreeBSD.ORG Mon Jan 12 14:11:53 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 104CC106564A for ; Mon, 12 Jan 2009 14:11:53 +0000 (UTC) (envelope-from kometen@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.154]) by mx1.freebsd.org (Postfix) with ESMTP id 8ED7E8FC08 for ; Mon, 12 Jan 2009 14:11:52 +0000 (UTC) (envelope-from kometen@gmail.com) Received: by fg-out-1718.google.com with SMTP id l26so3690823fgb.35 for ; Mon, 12 Jan 2009 06:11:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=odF25W7wU3InEwhVdcyBdBYsfdBekDTAkD1BVOAY9nw=; b=ZGz9mBpMxbis6pEY4mjtjcOEwyNybv7F/szl4Rg7B1+o+M7B5c0H6gbbUpOfEnZrzo WpCn0qAQ2q6atCRjue8BhLKgH2lBEGdLvy+g0d0syX4wc3R2xK9uLHuupQNFevqetblp 2A/UG9shfXe+tskqOKsMZ2oCuT8cZWMeRFuUQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=OGL7s5kynxAf5IeToUghUSZYnERXwVHXaQkWGb1qtN8nqfoB5Yj1487D6UqKGnHEAZ 6Jv8l/EMFpNgqCn1diy6KIw+8qjvMXpxR/63kFqFgcHeUs8bely9y294+DvR4AeB3geh vlkrw3uzweV0p960M9pZ7WYkiWqnWoNHw8pJ8= Received: by 10.103.220.18 with SMTP id x18mr10508280muq.135.1231769511293; Mon, 12 Jan 2009 06:11:51 -0800 (PST) Received: by 10.102.244.13 with HTTP; Mon, 12 Jan 2009 06:11:51 -0800 (PST) Message-ID: Date: Mon, 12 Jan 2009 15:11:51 +0100 From: "Claus Guttesen" To: "Garrett Cooper" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <7d6fde3d0901111122v3813fe3ehf75de6a2a7e66203@mail.gmail.com> Cc: freebsd-stable@freebsd.org Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2009 14:11:53 -0000 >> It has performed a buildworld without problems and I'll be doing some >> buildworlds throughout the day. >> >> This is on a HP c-class-blade with 8 GB ram, 2 x quad-core and the >> build-in p200-controller with 64 MB ram. I've performed five buildworlds decrementing -j from 16 to 6 and I can't lock up the server. -- regards Claus When lenity and cruelty play for a kingdom, the gentler gamester is the soonest winner. Shakespeare From owner-freebsd-stable@FreeBSD.ORG Mon Jan 12 14:35:30 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 55BE2106564A for ; Mon, 12 Jan 2009 14:35:30 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from constantine.ticketswitch.com (constantine.ticketswitch.com [IPv6:2002:57e0:1d4e:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id 19CAB8FC0A for ; Mon, 12 Jan 2009 14:35:30 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from dilbert.rattatosk ([10.64.50.6] helo=dilbert.ticketswitch.com) by constantine.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LMNsw-000COo-RK; Mon, 12 Jan 2009 14:35:22 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LMNsw-0001ix-Q7; Mon, 12 Jan 2009 14:35:22 +0000 To: kometen@gmail.com, yanefbsd@gmail.com In-Reply-To: Message-Id: From: Pete French Date: Mon, 12 Jan 2009 14:35:22 +0000 Cc: freebsd-stable@freebsd.org Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2009 14:35:30 -0000 > I've performed five buildworlds decrementing -j from 16 to 6 and I > can't lock up the server. Mine never lock up doing buildworlds either. They only lock up when they are sitting there more of less idle! The machines which have never locked up are the webservers, which are fairly heavlt loaded. The machine which locks up the most frequently is a box sitting there doing nothing but DNS, which is the most lightly loaded of the lot. I am going to roll back to 7.0 on all of the HP machines now, having had yet another day of rebooting locked up machines. I will leave one running 7.1 with the debug options in the kernel to try and get some useful results out of this. All the machines are now running GENERIC with no specail optimisations, CPU types or anything like that. Absolutely out of the box vanilla 7.1/amd64 as far as I know :-( -pete. From owner-freebsd-stable@FreeBSD.ORG Mon Jan 12 14:55:23 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BADE9106566B for ; Mon, 12 Jan 2009 14:55:23 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 943C58FC13 for ; Mon, 12 Jan 2009 14:55:23 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id 4E19A46B0C; Mon, 12 Jan 2009 09:55:23 -0500 (EST) Date: Mon, 12 Jan 2009 14:55:23 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Garance A Drosihn In-Reply-To: Message-ID: References: <042FE04A-2F8D-47DD-8454-7BBA3791D7A8@inoc.net> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org, Pete French , Robert Blayzor Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2009 14:55:24 -0000 On Fri, 9 Jan 2009, Garance A Drosihn wrote: > At 2:39 PM -0500 1/9/09, Robert Blayzor wrote: >> On Jan 8, 2009, at 8:58 PM, Pete French wrote: >>> I have a number of HP 1U servers, all of which were running 7.0 perfectly >>> happily. I have been testing 7.1 in it's various incarnations for the last >>> couple of months on our test server and it has performed perfectly. >> >> I noticed a problem with 7.0 on a couple of Dell servers. [...] We've >> since then compiled the kernel under the BSD scheduler to rule that out, >> and so far so good. >> >> Since ULE is now default in 7.1 and not in 7.0, perhaps you can try that? > > FWIW, the other guy I know who is having this problem had already switched > to using ULE under 7.0-release, and did not have any problems with it. So > *his* problem was probably not related to SCHED_ULE, unless something has > recently changed there. > > Turns out he hasn't reverted back to 7.0-release just yet, so he's going to > try SCHED_4BSD and see if that helps his situation. Scheduler changes always come with some risk of exposing bugs that have existed in the code for a long time but never really manifested themselves. ULE is well shaken-out, having been under development for at least five years, but it is possible that some problems will become visible as a result of the switch. I would encourage people to stick with ULE, but if you're having a stability problem then experimenting with scheduler as a variable that could be triggering the problem may well be useful to help track down the bug. Most of the time the bugs will not be in ULE itself, rather, triggered because ULE will change the ordering or balancing of work in the system, so we should try to avoid situations where people switch to 4BSD from ULE and stick with it rather than getting the underlying problem fixed! Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-stable@FreeBSD.ORG Mon Jan 12 15:00:41 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D27861065672 for ; Mon, 12 Jan 2009 15:00:41 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id ADA548FC16 for ; Mon, 12 Jan 2009 15:00:41 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id 69C2E46B0D; Mon, 12 Jan 2009 10:00:41 -0500 (EST) Date: Mon, 12 Jan 2009 15:00:41 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Pete French In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org, drosih@rpi.edu, rblayzor.bulk@inoc.net Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2009 15:00:42 -0000 On Sat, 10 Jan 2009, Pete French wrote: >> FWIW, the other guy I know who is having this problem had already switched >> to using ULE under 7.0-release, and did not have any problems with it. So >> *his* problem was probably not related to SCHED_ULE, unless something has >> recently changed there. > > Well, one of my machines just locked up again, even with SCHED_4BSD on it, > so I am now thinking it is unrelated. > > The machine has completely locked - no response to pings, no response to > keypresses, nor to the power button. There is nothing printed on the console > - it is just sitting there with a login prompt :-( > > This is really not good - these are extremely common servers after all, and > I am just running bog standard 7.1 with apache and mysql. This is happening > across several different servers, all of which are slight variants on the > DL360, so I dont think it is something perculiar to me. I'm not sure if you've done this already, but the normal suggestions apply: have you compiled with INVARIANTS/WITNESS/DDB/KDB/BREAK_TO_DEBUGGER, and do any results / panics / etc result? Sometimes these debugging tools are able to convert hangs into panics, which gives us much more ability to debug them. If it still hangs rather than panicking, are you able to break into the debugger on the console? If you're using a video console and not able to get to the debugger, would it be possible to configure a serial console and use that -- serial breaks are often more successful at getting to the debugger than keyboard breaks. Likewise, I'm not sure if this hardware has an NMI button -- some HP servers have one on the motherboard that you can press -- but that is also potentially a way to get into the debugger the analyze the crash. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-stable@FreeBSD.ORG Mon Jan 12 15:16:50 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 45DD51065674; Mon, 12 Jan 2009 15:16:50 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from constantine.ticketswitch.com (constantine.ticketswitch.com [IPv6:2002:57e0:1d4e:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id 07D588FC13; Mon, 12 Jan 2009 15:16:49 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from dilbert.rattatosk ([10.64.50.6] helo=dilbert.ticketswitch.com) by constantine.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LMOWu-000Cm3-Cj; Mon, 12 Jan 2009 15:16:40 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LMOWu-0001t4-BH; Mon, 12 Jan 2009 15:16:40 +0000 To: rwatson@FreeBSD.org In-Reply-To: Message-Id: From: Pete French Date: Mon, 12 Jan 2009 15:16:40 +0000 Cc: freebsd-stable@freebsd.org, drosih@rpi.edu, rblayzor.bulk@inoc.net Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2009 15:16:51 -0000 > I'm not sure if you've done this already, but the normal suggestions apply: > have you compiled with INVARIANTS/WITNESS/DDB/KDB/BREAK_TO_DEBUGGER, and do > any results / panics / etc result? Sometimes these debugging tools are able > to convert hangs into panics, which gives us much more ability to debug them. I did, but it turns out I had an incorrect option in there which made the data I got not relevent. I now have another machine running a kernel with the following config: include GENERIC ident DEBUG options KDB options DDB options SW_WATCHDOG options DEBUG_VFS_LOCKS options MUTEX_DEBUG options WITNESS options LOCK_PROFILING options INVARIANTS options INVARIANT_SUPPORT options DIAGNOSTIC Those should enable me to get some useful output I hope. > If it still hangs rather than panicking, are you able to break into the > debugger on the console? If you're using a video console and not able to get > to the debugger, would it be possible to configure a serial console and use I cant add a sserial console - I am remote enough from most of these machines (Slough) and very remote from the test box (its in the USA!) so I cant get to them physicly. But I do have iLo which lets me use the console and gives me a bit of access to the front. I will check for NMI. Just had another lockup here - my working day has become a succession of running round rebooting servers though iLo at the moment. Will get back to you when the debug one has crashed - I could possibly give you direct access to the iLo console on that if you need it ? -pete. From owner-freebsd-stable@FreeBSD.ORG Mon Jan 12 16:37:45 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 936B7106564A for ; Mon, 12 Jan 2009 16:37:44 +0000 (UTC) (envelope-from dimitry@andric.com) Received: from tensor.andric.com (cl-327.ede-01.nl.sixxs.net [IPv6:2001:7b8:2ff:146::2]) by mx1.freebsd.org (Postfix) with ESMTP id 52BCC8FC19 for ; Mon, 12 Jan 2009 16:37:44 +0000 (UTC) (envelope-from dimitry@andric.com) Received: from [IPv6:2001:7b8:3a7:0:cc63:9c72:753c:54c6] (unknown [IPv6:2001:7b8:3a7:0:cc63:9c72:753c:54c6]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 1E97F11F838; Mon, 12 Jan 2009 17:37:42 +0100 (CET) Message-ID: <496B71D3.5050203@andric.com> Date: Mon, 12 Jan 2009 17:37:39 +0100 From: Dimitry Andric User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.1b3pre) Gecko/20090108 Shredder/3.0b2pre MIME-Version: 1.0 To: pyunyh@gmail.com References: <8dfae1c10901070639x67945324jeeecfcac647d7976@mail.gmail.com> <8dfae1c10901071550s69d99802p31ca7c775f3d6823@mail.gmail.com> <88527079.20090111192206@donpac.ru> <20090112011146.GC46346@cdnetworks.co.kr> <64114.83.221.215.168.1231741940.squirrel@83.221.215.168> <20090112064121.GF46346@cdnetworks.co.kr> In-Reply-To: <20090112064121.GF46346@cdnetworks.co.kr> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, eugene@donpac.ru Subject: Re: FreeBSD 7.1 Breaks re and rl Network Interface Drivers X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2009 16:37:45 -0000 On 2009-01-12 07:41, Pyun YongHyeon wrote: > I see, Unfortunately the issue was fixed in the end of 7.1-R > release process so I wanted to get more exposure before MFC. > I'll make sure to MFC to stable/7 after more testing. I'm also having problems with re's, in my case the interfaces take about 10 seconds to come up, if they come up at all. After the interfaces are up, half the time no packets go out at all. Usually it helps to bring them down via the console, wait about 10 seconds, and then bring them up again... These are the following variant: FreeBSD 7.1-STABLE #0: Mon Jan 12 14:22:11 CET 2009 [...] re0: port 0xf000-0xf0ff mem 0xfdfff000-0xfdfff0ff irq 18 at device 9.0 on pci0 re0: Chip rev. 0x18000000 re0: MAC rev. 0x00000000 miibus0: on re0 rgephy0: PHY 1 on miibus0 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto re0: Ethernet address: 00:30:18:a6:f1:a8 re0: [FILTER] re1: port 0xf200-0xf2ff mem 0xfdffe000-0xfdffe0ff irq 19 at device 11.0 on pci0 re1: Chip rev. 0x18000000 re1: MAC rev. 0x00000000 miibus1: on re1 rgephy1: PHY 1 on miibus1 rgephy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto re1: Ethernet address: 00:30:18:a6:f1:a9 re1: [FILTER] And just FYI, r187080-r187083 that you recently committed (MFCs of r184240-184243, r184245, 185575 and r186390), don't seem to change anything for this situation. :( From owner-freebsd-stable@FreeBSD.ORG Mon Jan 12 17:20:08 2009 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 DB2E51065689 for ; Mon, 12 Jan 2009 17:20:08 +0000 (UTC) (envelope-from sascha=stable=freebsd.org=vjbjfxor@holzleiter.name) Received: from serverbitch.de (unknown [IPv6:2001:8d8:80:11::351]) by mx1.freebsd.org (Postfix) with ESMTP id 862288FC1B for ; Mon, 12 Jan 2009 17:20:08 +0000 (UTC) (envelope-from sascha=stable=freebsd.org=vjbjfxor@holzleiter.name) Received: from oinetka.gfsrv.net ([79.110.95.2] helo=dreamland.office.local) by serverbitch.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim) (envelope-from ) id 1LMQSK-000J75-TM for stable@freebsd.org; Mon, 12 Jan 2009 18:20:05 +0100 Message-ID: <496B7C17.8010107@holzleiter.name> Date: Mon, 12 Jan 2009 18:21:27 +0100 From: Sascha Holzleiter User-Agent: Thunderbird 2.0.0.18 (X11/20081126) MIME-Version: 1.0 To: stable@freebsd.org References: <8dfae1c10901070639x67945324jeeecfcac647d7976@mail.gmail.com> In-Reply-To: <8dfae1c10901070639x67945324jeeecfcac647d7976@mail.gmail.com> Content-Type: multipart/mixed; boundary="------------090909020301030402090203" Cc: Subject: Re: FreeBSD 7.1 Breaks re and rl Network Interface Drivers X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2009 17:20:10 -0000 This is a multi-part message in MIME format. --------------090909020301030402090203 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Walter Venable wrote: > FreeBSD 7.1 upgrade broke my network access, machine is totally > offline (powered-on and I can play inside it at the terminal, but > absolutely 0 network access): > This happened AFTER make kernel but BEFORE make installworld. I think > this implies it's a kernel driver issue. Hi, i see similar problems with a re card: re0@pci0:4:7:0: class=0x020000 card=0x816710ec chip=0x816710ec rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8169/8110 Family Gigabit Ethernet NIC' class = network subclass = ethernet After upgrading to 7.1-RELEASE (and also STABLE) the NIC doesn't seem to receive any frames. I can see the DHCP Requests on the DHCP Server but the DHCPOFFERS are never seen by the client with the re0 device. After setting promiscious mode on the interface (i.e. by tcpdump -ni re0) the interface begins to work fine. I've attached a complete dmesg output, but i think the detection works fine, here the short version: re0: port 0x9c00-0x9cff mem 0xdfdff000-0xdfdff0ff irq 20 at device 7.0 on pci4 re0: Chip rev. 0x18000000 re0: MAC rev. 0x00000000 miibus0: on re0 rgephy0: PHY 1 on miibus0 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto re0: Ethernet address: 00:1a:92:35:29:fa re0: [FILTER] --------------090909020301030402090203 Content-Type: text/plain; name="dmesg.nolink" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="dmesg.nolink" Copyright (c) 1992-2009 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.1-STABLE #0: Mon Jan 12 14:18:26 CET 2009 root@dreamland.office.local:/usr/obj/usr/src/sys/DREAMLAND Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Core(TM)2 CPU 6320 @ 1.86GHz (1863.87-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6f6 Stepping = 6 Features=0xbfebfbff Features2=0xe3bd AMD Features=0x20100000 AMD Features2=0x1 Cores per package: 2 real memory = 2146304000 (2046 MB) avail memory = 2086531072 (1989 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 4 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 100000, 7fde0000 (3) failed acpi0: reservation of 0, a0000 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 acpi_hpet0: iomem 0xfe800000-0xfe8003ff on acpi0 device_attach: acpi_hpet0 attach returned 12 acpi_button0: on acpi0 acpi_button1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pcib2: irq 27 at device 2.0 on pci0 pci2: on pcib2 vgapci0: port 0xac00-0xac7f mem 0xdc000000-0xdcffffff,0xc0000000-0xcfffffff,0xdd000000-0xddffffff irq 24 at device 0.0 on pci2 nvidia0: on vgapci0 vgapci0: child nvidia0 requested pci_enable_busmaster vgapci0: child nvidia0 requested pci_enable_io nvidia0: [GIANT-LOCKED] nvidia0: [ITHREAD] pcib3: irq 31 at device 3.0 on pci0 pci3: on pcib3 atapci0: port 0xcc00-0xcc07,0xc800-0xc803,0xc400-0xc407,0xc000-0xc003,0xbc00-0xbc0f mem 0xdfefe000-0xdfefffff irq 28 at device 0.0 on pci3 atapci0: [ITHREAD] atapci0: AHCI called from vendor specific driver atapci0: AHCI Version 01.00 controller with 2 ports detected ata2: on atapci0 ata2: [ITHREAD] ata3: on atapci0 ata3: [ITHREAD] ata4: on atapci0 ata4: [ITHREAD] atapci1: port 0xfc00-0xfc07,0xf800-0xf803,0xf400-0xf407,0xf000-0xf003,0xec00-0xec0f,0xe800-0xe8ff irq 21 at device 15.0 on pci0 atapci1: [ITHREAD] ata5: on atapci1 ata5: [ITHREAD] ata6: on atapci1 ata6: [ITHREAD] atapci2: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xe400-0xe40f at device 15.1 on pci0 ata0: on atapci2 ata0: [ITHREAD] ata1: on atapci2 ata1: [ITHREAD] uhci0: port 0xe000-0xe01f irq 20 at device 16.0 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: on uhci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xdc00-0xdc1f irq 22 at device 16.1 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: on uhci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xd800-0xd81f irq 21 at device 16.2 on pci0 uhci2: [GIANT-LOCKED] uhci2: [ITHREAD] usb2: on uhci2 usb2: USB revision 1.0 uhub2: on usb2 uhub2: 2 ports with 2 removable, self powered uhci3: port 0xd400-0xd41f irq 23 at device 16.3 on pci0 uhci3: [GIANT-LOCKED] uhci3: [ITHREAD] usb3: on uhci3 usb3: USB revision 1.0 uhub3: on usb3 uhub3: 2 ports with 2 removable, self powered ehci0: mem 0xdffff000-0xdffff0ff irq 21 at device 16.4 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: on ehci0 usb4: USB revision 2.0 uhub4: on usb4 uhub4: 8 ports with 8 removable, self powered isab0: at device 17.0 on pci0 isa0: on isab0 pcib4: at device 19.1 on pci0 pci4: on pcib4 re0: port 0x9c00-0x9cff mem 0xdfdff000-0xdfdff0ff irq 20 at device 7.0 on pci4 re0: Chip rev. 0x18000000 re0: MAC rev. 0x00000000 miibus0: on re0 rgephy0: PHY 1 on miibus0 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto re0: Ethernet address: 00:1a:92:35:29:fa re0: [FILTER] pcib5: on acpi0 pci128: on pcib5 pci128: at device 1.0 (no driver attached) acpi_tz0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] cpu0: on acpi0 est0: on cpu0 p4tcc0: on cpu0 cpu1: on acpi0 est1: on cpu1 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 72a072a0600072a device_attach: est1 attach returned 6 p4tcc1: on cpu1 acpi_hpet0: iomem 0xfe800000-0xfe8003ff on acpi0 device_attach: acpi_hpet0 attach returned 12 pmtimer0 on isa0 orm0: at iomem 0xd0000-0xd2fff pnpid ORM0000 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ugen0: on uhub0 ums0: on uhub1 ums0: 3 buttons and Z dir. Timecounters tick every 1.000 msec acd0: DVDR at ata0-master UDMA66 ad10: 76319MB at ata5-master SATA150 SMP: AP CPU #1 Launched! Trying to mount root from ufs:/dev/ad10s1a --------------090909020301030402090203-- From owner-freebsd-stable@FreeBSD.ORG Mon Jan 12 17:45:02 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C9B21106566C for ; Mon, 12 Jan 2009 17:45:02 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 9148D8FC16 for ; Mon, 12 Jan 2009 17:45:02 +0000 (UTC) (envelope-from sam@errno.com) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id n0CHPh5Y003514 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 12 Jan 2009 09:25:44 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <496B7D17.7020407@errno.com> Date: Mon, 12 Jan 2009 09:25:43 -0800 From: Sam Leffler User-Agent: Thunderbird 2.0.0.18 (X11/20081209) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC-Rhyolite-Metrics: ebb.errno.com; whitelist Subject: HEADS UP: build changes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2009 17:45:03 -0000 r187106 syncs the Makefiles with HEAD so that RELENG_7 has the same set of build knobs. Let me know if you see any oddities that you can trace to this commit. Sam From owner-freebsd-stable@FreeBSD.ORG Mon Jan 12 18:10:27 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0290E1065670 for ; Mon, 12 Jan 2009 18:10:27 +0000 (UTC) (envelope-from nealhogan@gmail.com) Received: from mail-gx0-f16.google.com (mail-gx0-f16.google.com [209.85.217.16]) by mx1.freebsd.org (Postfix) with ESMTP id 0AC268FC24 for ; Mon, 12 Jan 2009 18:10:10 +0000 (UTC) (envelope-from nealhogan@gmail.com) Received: by gxk9 with SMTP id 9so12942gxk.7 for ; Mon, 12 Jan 2009 10:09:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=qtGXKJIoI0YEMkLiC9rCbNOE2vwWdVEXTlTB8sFrQk4=; b=DyoUuCkQRg+M7iHl7LvL4oaD9G4N6EkB5HuiDwtC2ITm37UMClwt3ZmOk5OVrZd+65 vR/gpIJnTm31PdPCW09EfeQ6AYWA+kjfmvDIjrlUzo63NUThAZEldXnMRwxMlwT7gkDa wzPJ2ee6h+zhdSF1n1QrE16wIxP2j2r3EpdZQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=fVuTPpImaIxPgJziRBDTqJo0z7VLIKPiAOiJpAEGtgYhfVRjan0sZUD02SdfADjzIY 9IfCXshHCKP+NrtK1mzpk0cR4TsJY7W+V0i9pFQplVH3sO7QBOLOz67I+Yivytjl0ow8 mc9g7fTKhCfvF30vfDIXbDfV6KKBNXsL3nA2g= Received: by 10.150.140.6 with SMTP id n6mr3364198ybd.124.1231782122552; Mon, 12 Jan 2009 09:42:02 -0800 (PST) Received: by 10.150.182.2 with HTTP; Mon, 12 Jan 2009 09:41:57 -0800 (PST) Message-ID: Date: Mon, 12 Jan 2009 11:41:57 -0600 From: "Neal Hogan" To: freebsd-questions@freebsd.org, freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: bwi: no DS tssi no OFDM tssi X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2009 18:10:27 -0000 Hello, I am attempting to get by broadcom wifi card up and running, am sick of trying to get ndis working, and am attempting to use the bwi driver (originating in dragonflyBSD). I'm hoping others here have tried to do the same and have some pointers. I'm using 7.1-RELEASE (system/source are in-sync) and my card is a BCM94306MP. My dmesg is posted below. Bwi(4) is installed and it recognizes my card (*if_bwi_load-"YES"* is in my /etc/rc.conf and *bwi_v3* and *if_bwi* are loaded). I can send a IP request to my WEP encrypted access point. Yet, it doesn't get an offer and says that *no DS tssi* and *no OFDM tssi* Being new to bwi(4) and have never seen references to DS/OFDM tssi, I'm not sure what info to provide. My research is not leading anywhere helpful. Thanks. Copyright (c) 1992-2009 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.1-RELEASE #0: Sat Jan 10 19:07:15 CST 2009 nph@frege.lambdaserver:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: mobile AMD Athlon(tm) XP2400+ (1788.94-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x6a0 Stepping = 0 Features=0x383f9ff AMD Features=0xc0480800 real memory = 468647936 (446 MB) avail memory = 444530688 (423 MB) kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0 acpi_ec0: port 0x62,0x66 on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci_link5: BIOS IRQ 10 for 0.10.INTA is invalid pci0: on pcib0 agp0: on hostb0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0x9000-0x90ff mem 0xe0000000-0xefffffff,0xd0100000-0xd010ffff irq 10 at device 5.0 on pci1 ohci0: mem 0xd0006000-0xd0006fff irq 9 at device 2.0 on pci0 ohci0: [GIANT-LOCKED] ohci0: [ITHREAD] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 4 ports with 4 removable, self powered pcm0: port 0x8400-0x84ff mem 0xd0007000-0xd0007fff irq 5 at device 6.0 on pci0 pcm0: pcm0: [GIANT-LOCKED] pcm0: [ITHREAD] isab0: at device 7.0 on pci0 isa0: on isab0 pci0: at device 8.0 (no driver attached) bwi0: mem 0xd0004000-0xd0005fff irq 9 at device 9.0 on pci0 bwi0: [ITHREAD] bwi0: regwin: chipcommon (0x800), rev 2, vendor 0x4243 bwi0: BBP: id 0x4306, rev 0x2, pkg 0 bwi0: nregwin 6, cap 0x0000002a bwi0: regwin: 802.11 MAC (0x812), rev 4, vendor 0x4243 bwi0: has TX stats bwi0: MAC: rev 4 bwi0: regwin: pcmcia (0x80d), rev 1, vendor 0x4243 bwi0: regwin: v90 codec (0x807), rev 1, vendor 0x4243 bwi0: regwin: pci (0x804), rev 7, vendor 0x4243 bwi0: regwin: 802.11 MAC (0x812), rev 4, vendor 0x4243 bwi0: ignore second MAC bwi0: bus rev 0 bwi0: pci is enabled bwi0: card flags 0x000f bwi0: 0th led, act 3, lowact 0 bwi0: 1th led, act 5, lowact 0 bwi0: 2th led, act 4, lowact 0 bwi0: 3th led, act 0, lowact 0 bwi0: 802.11 MAC was already disabled bwi0: PHY is linked bwi0: PHY: type 2, rev 1, ver 1 bwi0: PHY: 802.11G attach bwi0: RF: manu 0x17f, type 0x2050, rev 2 bwi0: bus rev 0 bwi0: PHY is linked bwi0: 30bit bus space bwi0: max txpower from sprom: 57 dBm bwi0: invalid antenna gain in sprom bwi0: ant gain 8 dBm bwi0: region/domain max txpower 76 dBm bwi0: max txpower 57 dBm bwi0: sprom idle tssi: 0x003e bwi0: TSSI-TX power map: 71 71 70 70 70 70 70 69 69 69 69 69 68 68 68 67 67 67 66 66 66 66 65 65 65 64 64 64 63 63 63 62 61 61 61 60 59 59 58 57 57 55 55 54 53 52 51 50 49 48 47 44 43 42 39 37 35 32 29 26 22 18 14 8 bwi0: idle tssi0: 62 bwi0: bus rev 0 bwi0: locale: 6 bwi0: WARNING: using obsoleted if_watchdog interface bwi0: Ethernet address: 00:90:4b:61:02:45 cbb0: irq 11 at device 10.0 on pci0 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 cbb0: [ITHREAD] fwohci0: mem 0xd0009000-0xd00097ff,0xd0000000-0xd0003fff irq 10 at device 12.0 on pci0 fwohci0: [FILTER] fwohci0: OHCI version 1.10 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:0d:9d:71:9e:43:0c:6a fwohci0: Phy 1394a available S400, 1 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:0d:9d:43:0c:6a fwe0: Ethernet address: 02:0d:9d:43:0c:6a fwip0: on firewire0 fwip0: Firewire address: 00:0d:9d:71:9e:43:0c:6a @ 0xfffe00000000, S400, maxrec 2048 sbp0: on firewire0 dcons_crom0: on firewire0 dcons_crom0: bus_addr 0x12bc000 fwohci0: Initiate bus reset fwohci0: BUS reset fwohci0: node_id=0xc000ffc0, gen=1, CYCLEMASTER mode atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x8080-0x808f at device 16.0 on pci0 atapci0: using PIO transfers above 137GB as workaround for 48bit DMA access bug, expect reduced performance ata0: on atapci0 ata0: [ITHREAD] ata1: on atapci0 ata1: [ITHREAD] pci0: at device 17.0 (no driver attached) sis0: port 0x8c00-0x8cff mem 0xd000a000-0xd000afff irq 11 at device 18.0 on pci0 sis0: Silicon Revision: DP83816A miibus0: on sis0 nsphyter0: PHY 0 on miibus0 nsphyter0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto sis0: Ethernet address: 00:0d:9d:43:2b:a7 sis0: [ITHREAD] acpi_button0: on acpi0 acpi_lid0: on acpi0 acpi_acad0: on acpi0 battery0: on acpi0 acpi_tz0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model IntelliMouse, device ID 3 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FILTER] sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio0: [FILTER] cpu0: on acpi0 powernow0: on cpu0 pmtimer0 on isa0 orm0: at iomem 0xc0000-0xcefff,0xcf000-0xcf7ff,0xdb000-0xdbfff,0xdc000-0xdffff pnpid ORM0000 on isa0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold ppbus0: on ppc0 ppbus0: [ITHREAD] ppi0: on ppbus0 plip0: on ppbus0 plip0: WARNING: using obsoleted IFF_NEEDSGIANT flag lpt0: on ppbus0 lpt0: Interrupt-driven port ppc0: [GIANT-LOCKED] ppc0: [ITHREAD] sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ums0: on uhub0 ums0: 16 buttons and Z dir. Timecounter "TSC" frequency 1788943467 Hz quality 800 Timecounters tick every 1.000 msec firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) ad0: 95396MB at ata0-master UDMA100 acd0: CDRW at ata1-master UDMA33 Trying to mount root from ufs:/dev/ad0s2a bwi0: bwi_init bwi0: bwi_stop bwi0: bbp atten: 0, rf atten: 3, ctrl1: 2, ctrl2: 65535 bwi0: bus rev 0 bwi0: 802.11 MAC is disabled bwi0: 802.11 MAC was already disabled bwi0: PHY is linked bwi0: bus rev 0 bwi0: PHY is unlinked bwi0: RF calibration value: 0x002a bwi0: bus rev 0 bwi0: PHY is linked firmware_get: failed to load firmware image bwi_v3_ucode4 bwi0: request firmware bwi_v3_ucode4 failed bwi0: bwi_stop -- www.nealhogan.net From owner-freebsd-stable@FreeBSD.ORG Mon Jan 12 18:28:04 2009 Return-Path: Delivered-To: FreeBSD-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B7B4D106567C for ; Mon, 12 Jan 2009 18:28:04 +0000 (UTC) (envelope-from l1nyx01d@googlemail.com) Received: from mail-ew0-f21.google.com (mail-ew0-f21.google.com [209.85.219.21]) by mx1.freebsd.org (Postfix) with ESMTP id 233CE8FC24 for ; Mon, 12 Jan 2009 18:28:03 +0000 (UTC) (envelope-from l1nyx01d@googlemail.com) Received: by ewy14 with SMTP id 14so13241569ewy.19 for ; Mon, 12 Jan 2009 10:28:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:date:from:x-mailer:reply-to :x-priority:message-id:to:subject:mime-version:content-type :content-transfer-encoding; bh=J3fastw4FY3+RvdHtLTAzWDILCX9JK5pucD6jlQqBOU=; b=t7NeMXsGhjASnWFwdTj4o96+cqkh5quAcWHd0PpBidNV5qSduZ7I4PnRWK+P/hhASi 862ZpRMwnlzWSDa4zJWnRJh8iPw1BuLQePi6DSgk3m7JgM7+dhQvX2wjFDHwvCWcjyxp 8T0yEfB9819P0JYkoYwnek659u0ucYvh5RU7E= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=date:from:x-mailer:reply-to:x-priority:message-id:to:subject :mime-version:content-type:content-transfer-encoding; b=w+nYaHefo0RAtZWnZm1DWRhDLhzCaxvIQR7PKrWbnMe82rCIATzCymFuM5baNQ9M+T NCMpOH0zoCDZQiJmO6sXkpIJLory8yFrSY/YliAiSzy5C44JrBzCDWbVg16otAIkQSIW zZXG/ne0nzuBqcSEAnNuBsr/zdWfNb4nQWllo= Received: by 10.210.61.8 with SMTP id j8mr34493507eba.45.1231784882069; Mon, 12 Jan 2009 10:28:02 -0800 (PST) Received: from goletsa (92.243.69.98.addr.datapoint.ru [92.243.69.98]) by mx.google.com with ESMTPS id 5sm529321eyh.38.2009.01.12.10.28.01 (version=SSLv3 cipher=OTHER); Mon, 12 Jan 2009 10:28:01 -0800 (PST) Date: Mon, 12 Jan 2009 21:27:57 +0300 From: "L1NYX01D@GOOGLEMAIL.COM" X-Mailer: Voyager (v4.0.18.4) Professional X-Priority: 3 (Normal) Message-ID: <54540134.20090112212757@gmail.com> To: FreeBSD-stable@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Cc: Subject: FreeBSD 7.0 kernel panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "L1NYX01D@GMAIL.COM" List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2009 18:28:06 -0000 Hello, FreeBSD-stable. Last week I have a lot of kernel panics like: > [root@router1 /usr/obj/usr/src/sys/TINCOKERNEL2]# kgdb kernel.debug /var/= crash/vmcore.20 > [GDB will not be able to debug user-mode threads: > /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] > GNU gdb 6.1.1 [FreeBSD] > Copyright 2004 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you = are > welcome to change it and/or distribute copies of it under certain conditi= ons. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for detail= s. > This GDB was configured as "i386-marcel-freebsd". > > Unread portion of the kernel message buffer: > kernel trap 12 with interrupts disabled > > > Fatal trap 12: page fault while in kernel mode > cpuid =3D 0; apic id =3D 00 > fault virtual address =3D 0x9 > fault code =3D supervisor read, page not present > instruction pointer =3D 0x20:0xc079f1af > stack pointer =3D 0x28:0xe5697c80 > frame pointer =3D 0x28:0xe5697cbc > code segment =3D base 0x0, limit 0xfffff, type 0x1b > =3D DPL 0, pres 1, def32 1, gran 1 > processor eflags =3D resume, IOPL =3D 0 > current process =3D 14 (swi4: clock) > trap number =3D 12 > panic: page fault > cpuid =3D 0 > Uptime: 51m49s > Physical memory: 2032 MB > Dumping 177 MB: 162 146 130 114 98 82 66 50 34 18 2 > > #0 doadump () at pcpu.h:195 > 195 __asm __volatile("movl %%fs:0,%0" : "=3Dr" (td)); > (kgdb) bt > #0 doadump () at pcpu.h:195 > #1 0xc078d1b7 in boot (howto=3D260) at > /usr/src/sys/kern/kern_shutdown.c:409 > #2 0xc078d479 in panic (fmt=3DVariable "fmt" is not available. > ) at /usr/src/sys/kern/kern_shutdown.c:563 > #3 0xc0a0eaac in trap_fatal (frame=3D0xe5697c40, eva=3D9) at /usr/src/sy= s/i386/i386/trap.c:899 > #4 0xc0a0f42f in trap (frame=3D0xe5697c40) at /usr/src/sys/i386/i386/tra= p.c:280 > #5 0xc09f565b in calltrap () at > /usr/src/sys/i386/i386/exception.s:139 > #6 0xc079f1af in softclock (dummy=3D0x0) at > /usr/src/sys/kern/kern_timeout.c:202 > #7 0xc076f31b in ithread_loop (arg=3D0xc5101250) at > /usr/src/sys/kern/kern_intr.c:1036 > #8 0xc076c119 in fork_exit (callout=3D0xc076f170 , arg=3D0= xc5101250, frame=3D0xe5697d38) > at /usr/src/sys/kern/kern_fork.c:781 > #9 0xc09f56d0 in fork_trampoline () at > /usr/src/sys/i386/i386/exception.s:205 > (kgdb) What I should do? --=20 =D1 =F3=E2=E0=E6=E5=ED=E8=E5=EC, L1NYX01D mailto:l1nyx01d@googlemail.com From owner-freebsd-stable@FreeBSD.ORG Mon Jan 12 18:32:56 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8AFD9106564A; Mon, 12 Jan 2009 18:32:56 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from mail-bw0-f20.google.com (mail-bw0-f20.google.com [209.85.218.20]) by mx1.freebsd.org (Postfix) with ESMTP id A09748FC18; Mon, 12 Jan 2009 18:32:55 +0000 (UTC) (envelope-from onemda@gmail.com) Received: by bwz13 with SMTP id 13so6805133bwz.19 for ; Mon, 12 Jan 2009 10:32:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=JuUx3snZSZCIow0hLbFsquPhm73L6YY3R4zmfT/PqFY=; b=qDPSMn7IWRxtzWYMexQF4EwaWT4dWFTQDOqezDp0CkiAvbngcBHIE0VkjKVnN3DZC6 ZFp6b+gZvy9mt706LBCShRNiJA40BtcxYJjx6sbty2suiJoNpA9iOrxaLkvwnekbL/j0 lWdj79vAnD0TXF8BsVjS+uyU0K54OTCvARfAo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=YzwpEh4A09HeMy4oLwm1eoBv8VbU9oxXHosAhtrv4vqU9uSnDjrG3AE2Y22pDYYLda X19kPEPxw51kDKsyUo69n4Jqk+KgSWiRxxfFpbxZp7METiEp+nEp3MJZA5FXyzy17DeE LI6V9scUyWfjUe2RtdFLN6duJiO6nT3JNykNg= Received: by 10.223.110.144 with SMTP id n16mr1411149fap.63.1231785174233; Mon, 12 Jan 2009 10:32:54 -0800 (PST) Received: by 10.223.115.1 with HTTP; Mon, 12 Jan 2009 10:32:54 -0800 (PST) Message-ID: <3a142e750901121032x79da7932se74c5511ec4a837b@mail.gmail.com> Date: Mon, 12 Jan 2009 18:32:54 +0000 From: "Paul B. Mahol" To: "Neal Hogan" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Cc: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: bwi: no DS tssi no OFDM tssi X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2009 18:32:57 -0000 On 1/12/09, Neal Hogan wrote: > Hello, > > I am attempting to get by broadcom wifi card up and running, am sick of > trying to get ndis working, and am attempting to use the bwi driver > (originating in dragonflyBSD). I'm hoping others here have tried to do the > same and have some pointers. I'm using 7.1-RELEASE (system/source are > in-sync) and my card is a BCM94306MP. My dmesg is posted below. > > Bwi(4) is installed and it recognizes my card (*if_bwi_load-"YES"* is in my > /etc/rc.conf and *bwi_v3* and *if_bwi* are loaded). I can send a IP request > to my WEP encrypted access point. Yet, it doesn't get an offer and says that > *no DS tssi* and *no OFDM tssi* Being new to bwi(4) and have never seen > references to DS/OFDM tssi, I'm not sure what info to provide. My research > is not leading anywhere helpful. Thanks. > > > > > Copyright (c) 1992-2009 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 7.1-RELEASE #0: Sat Jan 10 19:07:15 CST 2009 > nph@frege.lambdaserver:/usr/obj/usr/src/sys/GENERIC > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: mobile AMD Athlon(tm) XP2400+ (1788.94-MHz 686-class CPU) > Origin = "AuthenticAMD" Id = 0x6a0 Stepping = 0 > > Features=0x383f9ff > AMD Features=0xc0480800 > real memory = 468647936 (446 MB) > avail memory = 444530688 (423 MB) > kbd1 at kbdmux0 > ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) > acpi0: on motherboard > acpi0: [ITHREAD] > acpi0: Power Button (fixed) > Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 > acpi_timer0: <32-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0 > acpi_ec0: port 0x62,0x66 on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci_link5: BIOS IRQ 10 for 0.10.INTA is invalid > pci0: on pcib0 > agp0: on hostb0 > pcib1: at device 1.0 on pci0 > pci1: on pcib1 > vgapci0: port 0x9000-0x90ff mem > 0xe0000000-0xefffffff,0xd0100000-0xd010ffff irq 10 at device 5.0 on > pci1 > ohci0: mem > 0xd0006000-0xd0006fff irq 9 at device 2.0 on pci0 > ohci0: [GIANT-LOCKED] > ohci0: [ITHREAD] > usb0: OHCI version 1.0, legacy support > usb0: SMM does not respond, resetting > usb0: on ohci0 > usb0: USB revision 1.0 > uhub0: on usb0 > uhub0: 4 ports with 4 removable, self powered > pcm0: port 0x8400-0x84ff mem 0xd0007000-0xd0007fff > irq 5 at device 6.0 on pci0 > pcm0: > pcm0: [GIANT-LOCKED] > pcm0: [ITHREAD] > isab0: at device 7.0 on pci0 > isa0: on isab0 > pci0: at device 8.0 (no driver attached) > bwi0: mem > 0xd0004000-0xd0005fff irq 9 at device 9.0 on pci0 > bwi0: [ITHREAD] > bwi0: regwin: chipcommon (0x800), rev 2, vendor 0x4243 > bwi0: BBP: id 0x4306, rev 0x2, pkg 0 > bwi0: nregwin 6, cap 0x0000002a > bwi0: regwin: 802.11 MAC (0x812), rev 4, vendor 0x4243 > bwi0: has TX stats > bwi0: MAC: rev 4 > bwi0: regwin: pcmcia (0x80d), rev 1, vendor 0x4243 > bwi0: regwin: v90 codec (0x807), rev 1, vendor 0x4243 > bwi0: regwin: pci (0x804), rev 7, vendor 0x4243 > bwi0: regwin: 802.11 MAC (0x812), rev 4, vendor 0x4243 > bwi0: ignore second MAC > bwi0: bus rev 0 > bwi0: pci is enabled > bwi0: card flags 0x000f > bwi0: 0th led, act 3, lowact 0 > bwi0: 1th led, act 5, lowact 0 > bwi0: 2th led, act 4, lowact 0 > bwi0: 3th led, act 0, lowact 0 > bwi0: 802.11 MAC was already disabled > bwi0: PHY is linked > bwi0: PHY: type 2, rev 1, ver 1 > bwi0: PHY: 802.11G attach > bwi0: RF: manu 0x17f, type 0x2050, rev 2 > bwi0: bus rev 0 > bwi0: PHY is linked > bwi0: 30bit bus space > bwi0: max txpower from sprom: 57 dBm > bwi0: invalid antenna gain in sprom > bwi0: ant gain 8 dBm > bwi0: region/domain max txpower 76 dBm > bwi0: max txpower 57 dBm > bwi0: sprom idle tssi: 0x003e > bwi0: TSSI-TX power map: > 71 71 70 70 70 70 70 69 > 69 69 69 69 68 68 68 67 > 67 67 66 66 66 66 65 65 > 65 64 64 64 63 63 63 62 > 61 61 61 60 59 59 58 57 > 57 55 55 54 53 52 51 50 > 49 48 47 44 43 42 39 37 > 35 32 29 26 22 18 14 8 > bwi0: idle tssi0: 62 > bwi0: bus rev 0 > bwi0: locale: 6 > bwi0: WARNING: using obsoleted if_watchdog interface > bwi0: Ethernet address: 00:90:4b:61:02:45 > cbb0: irq 11 at device 10.0 on pci0 > cardbus0: on cbb0 > pccard0: <16-bit PCCard bus> on cbb0 > cbb0: [ITHREAD] > fwohci0: mem > 0xd0009000-0xd00097ff,0xd0000000-0xd0003fff irq 10 at device 12.0 on > pci0 > fwohci0: [FILTER] > fwohci0: OHCI version 1.10 (ROM=1) > fwohci0: No. of Isochronous channels is 4. > fwohci0: EUI64 00:0d:9d:71:9e:43:0c:6a > fwohci0: Phy 1394a available S400, 1 ports. > fwohci0: Link S400, max_rec 2048 bytes. > firewire0: on fwohci0 > fwe0: on firewire0 > if_fwe0: Fake Ethernet address: 02:0d:9d:43:0c:6a > fwe0: Ethernet address: 02:0d:9d:43:0c:6a > fwip0: on firewire0 > fwip0: Firewire address: 00:0d:9d:71:9e:43:0c:6a @ 0xfffe00000000, > S400, maxrec 2048 > sbp0: on firewire0 > dcons_crom0: on firewire0 > dcons_crom0: bus_addr 0x12bc000 > fwohci0: Initiate bus reset > fwohci0: BUS reset > fwohci0: node_id=0xc000ffc0, gen=1, CYCLEMASTER mode > atapci0: port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x8080-0x808f at device 16.0 on > pci0 > atapci0: using PIO transfers above 137GB as workaround for 48bit DMA > access bug, expect reduced performance > ata0: on atapci0 > ata0: [ITHREAD] > ata1: on atapci0 > ata1: [ITHREAD] > pci0: at device 17.0 (no driver attached) > sis0: port 0x8c00-0x8cff mem > 0xd000a000-0xd000afff irq 11 at device 18.0 on pci0 > sis0: Silicon Revision: DP83816A > miibus0: on sis0 > nsphyter0: PHY 0 on miibus0 > nsphyter0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > sis0: Ethernet address: 00:0d:9d:43:2b:a7 > sis0: [ITHREAD] > acpi_button0: on acpi0 > acpi_lid0: on acpi0 > acpi_acad0: on acpi0 > battery0: on acpi0 > acpi_tz0: on acpi0 > atkbdc0: port 0x60,0x64 irq 1 on acpi0 > atkbd0: irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > atkbd0: [ITHREAD] > psm0: irq 12 on atkbdc0 > psm0: [GIANT-LOCKED] > psm0: [ITHREAD] > psm0: model IntelliMouse, device ID 3 > fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 > fdc0: [FILTER] > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on > acpi0 > sio0: type 16550A > sio0: [FILTER] > cpu0: on acpi0 > powernow0: on cpu0 > pmtimer0 on isa0 > orm0: at iomem > 0xc0000-0xcefff,0xcf000-0xcf7ff,0xdb000-0xdbfff,0xdc000-0xdffff pnpid > ORM0000 on isa0 > ppc0: at port 0x378-0x37f irq 7 on isa0 > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > ppc0: FIFO with 16/16/16 bytes threshold > ppbus0: on ppc0 > ppbus0: [ITHREAD] > ppi0: on ppbus0 > plip0: on ppbus0 > plip0: WARNING: using obsoleted IFF_NEEDSGIANT flag > lpt0: on ppbus0 > lpt0: Interrupt-driven port > ppc0: [GIANT-LOCKED] > ppc0: [ITHREAD] > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > sio1: configured irq 3 not in bitmap of probed irqs 0 > sio1: port may not be enabled > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > ums0: on uhub0 > ums0: 16 buttons and Z dir. > Timecounter "TSC" frequency 1788943467 Hz quality 800 > Timecounters tick every 1.000 msec > firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) > firewire0: bus manager 0 (me) > ad0: 95396MB at ata0-master UDMA100 > acd0: CDRW at ata1-master UDMA33 > Trying to mount root from ufs:/dev/ad0s2a > bwi0: bwi_init > bwi0: bwi_stop > bwi0: bbp atten: 0, rf atten: 3, ctrl1: 2, ctrl2: 65535 > bwi0: bus rev 0 > bwi0: 802.11 MAC is disabled > bwi0: 802.11 MAC was already disabled > bwi0: PHY is linked > bwi0: bus rev 0 > bwi0: PHY is unlinked > bwi0: RF calibration value: 0x002a > bwi0: bus rev 0 > bwi0: PHY is linked > firmware_get: failed to load firmware image bwi_v3_ucode4 > bwi0: request firmware bwi_v3_ucode4 failed Looks like it either doesnt have such firmware loaded or firmware is not supported for your card. bwi works only with firmware version 3 and not with 4. To get right answer look in current openbsd and dragonfly bwi driver if your BCM94306MP is listed. -- Paul From owner-freebsd-stable@FreeBSD.ORG Mon Jan 12 18:36:22 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6F027106571A; Mon, 12 Jan 2009 18:36:22 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (wojtek.tensor.gdynia.pl [IPv6:2001:4070:101:2::1]) by mx1.freebsd.org (Postfix) with ESMTP id A95AC8FC22; Mon, 12 Jan 2009 18:36:19 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (localhost [IPv6:::1]) by wojtek.tensor.gdynia.pl (8.14.3/8.14.3) with ESMTP id n0CIa9nt034407; Mon, 12 Jan 2009 19:36:09 +0100 (CET) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from localhost (wojtek@localhost) by wojtek.tensor.gdynia.pl (8.14.3/8.14.3/Submit) with ESMTP id n0CIa9ts034404; Mon, 12 Jan 2009 19:36:09 +0100 (CET) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Date: Mon, 12 Jan 2009 19:36:09 +0100 (CET) From: Wojciech Puchar To: Neal Hogan In-Reply-To: Message-ID: <20090112193549.T34373@wojtek.tensor.gdynia.pl> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: bwi: no DS tssi no OFDM tssi X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2009 18:36:23 -0000 > firmware_get: failed to load firmware image bwi_v3_ucode4 > bwi0: request firmware bwi_v3_ucode4 failed > bwi0: bwi_stop looks like here is a problem From owner-freebsd-stable@FreeBSD.ORG Mon Jan 12 18:55:48 2009 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C7F70106564A for ; Mon, 12 Jan 2009 18:55:48 +0000 (UTC) (envelope-from drosih@rpi.edu) Received: from smtp8.server.rpi.edu (smtp8.server.rpi.edu [128.113.2.228]) by mx1.freebsd.org (Postfix) with ESMTP id 8167E8FC2B for ; Mon, 12 Jan 2009 18:55:48 +0000 (UTC) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp8.server.rpi.edu (8.13.1/8.13.1) with ESMTP id n0CItjch022765; Mon, 12 Jan 2009 13:55:47 -0500 Mime-Version: 1.0 Message-Id: In-Reply-To: References: <042FE04A-2F8D-47DD-8454-7BBA3791D7A8@inoc.net> Date: Mon, 12 Jan 2009 13:55:45 -0500 To: Robert Watson From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Bayes-Prob: 0.0001 (Score 0) X-RPI-SA-Score: 0.00 () [Hold at 20.00] 22490(-25) X-CanItPRO-Stream: outgoing X-Canit-Stats-ID: Bayes signature not available X-Scanned-By: CanIt (www . roaringpenguin . com) on 128.113.2.228 Cc: freebsd-stable@FreeBSD.org Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2009 18:55:49 -0000 At 2:55 PM +0000 1/12/09, Robert Watson wrote: >On Fri, 9 Jan 2009, Garance A Drosihn wrote: > >>At 2:39 PM -0500 1/9/09, Robert Blayzor wrote: >>>On Jan 8, 2009, at 8:58 PM, Pete French wrote: >>>>I have a number of HP 1U servers, all of which were running 7.0 >>>>perfectly happily. I have been testing 7.1 in it's various >>>>incarnations for the last couple of months on our test server and >>>>it has performed perfectly. >>> >>>I noticed a problem with 7.0 on a couple of Dell servers. [...] >>>We've since then compiled the kernel under the BSD scheduler to >>>rule that out, and so far so good. >>> >>>Since ULE is now default in 7.1 and not in 7.0, perhaps you can try that? >> >>FWIW, the other guy I know who is having this problem had already >>switched to using ULE under 7.0-release, and did not have any >>problems with it. So *his* problem was probably not related to >>SCHED_ULE, unless something has recently changed there. >> >>Turns out he hasn't reverted back to 7.0-release just yet, so he's >>going to try SCHED_4BSD and see if that helps his situation. > >Scheduler changes always come with some risk of exposing bugs that >have existed in the code for a long time but never really manifested >themselves. ULE is well shaken-out, having been under development >for at least five years, but it is possible that some problems will >become visible as a result of the switch. I would encourage people >to stick with ULE, but if you're having a stability problem then >experimenting with scheduler as a variable that could be triggering >the problem may well be useful to help track down the bug. Just to followup on this: My friend did switch back to a 7.1 kernel with SCHED_4BSD, and he still ran into problems. The error messages weren't the same, but errors did happen in the same high disk-I/O situations as the lockup happened with SCHED_ULE. At this point he's fallen back to the 7.0-kernel that he had been running (which also has SCHED_ULE), and all the problems have gone away. So at the moment he's running with a 7.0-ish kernel and the 7.1-release userland, without the hanging problems. So the problem is something in the kernel, but it is *NOT* the scheduler (at least, not in his case). He is not eager to do a whole lot of experiments to track down the problem, since this is happening on busy production machines and he can't afford to have a lot of downtime on them (especially now that the semester at RPI has started up). The systems have some large (2 TB) filesystems on them, and the lockups occur in high disk-I/O situations. He's seeing the problem on one system which is a dual CPU quad-core xeon, and another which is a 64 bit P4 with hyperthreading. The one thing in common between the two setups is that the boot drives + a 3ware controller (with its array of RAID disks) is moved from one machine to the other one: "its a 3ware 9500 12 port model, the boot drive is connected to an ICH6 in IDE mode, and yes, I've run it in single, single with hyper threading, and 8 way mode. All 64 bit." We still have no idea where the problem really is. For all we know, someone spilled a Pepsi on it when he wasn't looking... -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu From owner-freebsd-stable@FreeBSD.ORG Mon Jan 12 19:00:26 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 956F21065673; Mon, 12 Jan 2009 19:00:26 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from constantine.ticketswitch.com (constantine.ticketswitch.com [IPv6:2002:57e0:1d4e:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id 5B0B28FC13; Mon, 12 Jan 2009 19:00:26 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from dilbert.rattatosk ([10.64.50.6] helo=dilbert.ticketswitch.com) by constantine.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LMS1D-000FRa-FX; Mon, 12 Jan 2009 19:00:11 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LMS1C-0002x6-Je; Mon, 12 Jan 2009 19:00:10 +0000 To: petefrench@ticketswitch.com, rwatson@FreeBSD.org Message-Id: From: Pete French Date: Mon, 12 Jan 2009 19:00:10 +0000 Cc: freebsd-stable@freebsd.org, drosih@rpi.edu, rblayzor.bulk@inoc.net Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2009 19:00:26 -0000 > I'm not sure if you've done this already, but the normal suggestions apply: > have you compiled with INVARIANTS/WITNESS/DDB/KDB/BREAK_TO_DEBUGGER, and do > any results / panics / etc result? Sometimes these debugging tools are able > to convert hangs into panics, which gives us much more ability to debug them. OK, I have now had a machine hand again, with the correct debug options in the kernel. The screen looked like this when I went to restart it: http://toybox.twisted.org.uk/~pete/71_lor2.png It had not, however, dropped into any kind of debugger. Also there appear to me console messages after the lock order reversal - is that normal ? The machine did stay up for a signifanct amount of time before doing this. I notice that it is more or less identical to the one I posted whenI had WITNESS_KDB in the kernel too, so maybe those results arent entirely suprious after all ? Given it hasnt dropped to a debugger, is there anything else I can try ? -pete. From owner-freebsd-stable@FreeBSD.ORG Mon Jan 12 19:01:41 2009 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B365310656D7; Mon, 12 Jan 2009 19:01:41 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from constantine.ticketswitch.com (constantine.ticketswitch.com [IPv6:2002:57e0:1d4e:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id 760A38FC1F; Mon, 12 Jan 2009 19:01:41 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from dilbert.rattatosk ([10.64.50.6] helo=dilbert.ticketswitch.com) by constantine.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LMS2e-000FTZ-Sc; Mon, 12 Jan 2009 19:01:40 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LMS2e-00035C-BD; Mon, 12 Jan 2009 19:01:40 +0000 To: drosih@rpi.edu, rwatson@FreeBSD.org In-Reply-To: Message-Id: From: Pete French Date: Mon, 12 Jan 2009 19:01:40 +0000 Cc: freebsd-stable@FreeBSD.org Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2009 19:01:43 -0000 > Just to followup on this: My friend did switch back to a 7.1 kernel with > SCHED_4BSD, and he still ran into problems. The error messages weren't Acually, I dont know if I posted it, but that was the same for me too. The scheduler makes no difference, nor do CPU copile settings. -pete. From owner-freebsd-stable@FreeBSD.ORG Mon Jan 12 20:08:32 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 788CF10656CA; Mon, 12 Jan 2009 20:08:32 +0000 (UTC) (envelope-from nealhogan@gmail.com) Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.28]) by mx1.freebsd.org (Postfix) with ESMTP id DBD978FC26; Mon, 12 Jan 2009 20:08:31 +0000 (UTC) (envelope-from nealhogan@gmail.com) Received: by yx-out-2324.google.com with SMTP id 8so4473227yxb.13 for ; Mon, 12 Jan 2009 12:08:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=+A1DuP0708SGWJhvI19iCFh770uXQlpDTXik2gwR2xg=; b=Tt4yGB9hMYA+19EsZ0WOBIrNdH14noQyZFt9OwLJeHElg3iA85wtKhNnm7QDHp2tBj vPWS231N5V0U8VoNQhHY9m50Ip5mmugP1ap/J/c+lC2OswCd7m1AS2ZElCxTeOX0hrqV QuPgnOWhteCLDlBjndg1r2z5ENdTT0hjOHero= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=OG5/eq196tzHPPKMPCBKi0qqQMCqZJhGn6RAsxfpc/M+dUdv4ff1dlbhMjHy29S50A N02MsQXSdDLVfQqp/4a7rSUMO7Lx7yoi/38x9ZTjN/fjPYa2harYvtcyIAXXa8kXKlfl SRVFbyc+VCrqJCIsiP/dqMg3NYsFBst9f3opo= Received: by 10.150.57.5 with SMTP id f5mr10983437yba.66.1231790910080; Mon, 12 Jan 2009 12:08:30 -0800 (PST) Received: by 10.150.182.2 with HTTP; Mon, 12 Jan 2009 12:08:30 -0800 (PST) Message-ID: Date: Mon, 12 Jan 2009 14:08:30 -0600 From: "Neal Hogan" To: "Paul B. Mahol" In-Reply-To: <3a142e750901121032x79da7932se74c5511ec4a837b@mail.gmail.com> MIME-Version: 1.0 References: <3a142e750901121032x79da7932se74c5511ec4a837b@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: bwi: no DS tssi no OFDM tssi X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2009 20:08:33 -0000 I installed the firmware stuff from the dragonfly bwi(4) man page, yet I have the same issue. Is there a way to tell whether the firmware they provide supports my card? Like I said, I can locate my access point (and others that are around) and ask for an IP . . . it seems as though I'm so close. I'm fairly certain that I have all of the avliable bwi(4) bits installed correctly. I dwonloaded and installed the driver and added *if_bwi_load="YES"* in my loader.conf. I loaded the .ko file (bwi_v3). I downloaded and installed the firmware from dflyBSD and followed their directions. Yet I get no offer. Is the fact that I fail to get an offer indicate the firmware incompatinbility? Anyway, thanks for you help. On Mon, Jan 12, 2009 at 12:32 PM, Paul B. Mahol wrote: > On 1/12/09, Neal Hogan wrote: > > Hello, > > > > I am attempting to get by broadcom wifi card up and running, am sick > of > > trying to get ndis working, and am attempting to use the bwi driver > > (originating in dragonflyBSD). I'm hoping others here have tried to do > the > > same and have some pointers. I'm using 7.1-RELEASE (system/source are > > in-sync) and my card is a BCM94306MP. My dmesg is posted below. > > > > Bwi(4) is installed and it recognizes my card (*if_bwi_load-"YES"* is in > my > > /etc/rc.conf and *bwi_v3* and *if_bwi* are loaded). I can send a IP > request > > to my WEP encrypted access point. Yet, it doesn't get an offer and says > that > > *no DS tssi* and *no OFDM tssi* Being new to bwi(4) and have never seen > > references to DS/OFDM tssi, I'm not sure what info to provide. My > research > > is not leading anywhere helpful. Thanks. > > > > > > > > > > Copyright (c) 1992-2009 The FreeBSD Project. > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > > The Regents of the University of California. All rights reserved. > > FreeBSD is a registered trademark of The FreeBSD Foundation. > > FreeBSD 7.1-RELEASE #0: Sat Jan 10 19:07:15 CST 2009 > > nph@frege.lambdaserver:/usr/obj/usr/src/sys/GENERIC > > Timecounter "i8254" frequency 1193182 Hz quality 0 > > CPU: mobile AMD Athlon(tm) XP2400+ (1788.94-MHz 686-class CPU) > > Origin = "AuthenticAMD" Id = 0x6a0 Stepping = 0 > > > > > Features=0x383f9ff > > AMD Features=0xc0480800 > > real memory = 468647936 (446 MB) > > avail memory = 444530688 (423 MB) > > kbd1 at kbdmux0 > > ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, > RF5413) > > acpi0: on motherboard > > acpi0: [ITHREAD] > > acpi0: Power Button (fixed) > > Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 > > acpi_timer0: <32-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0 > > acpi_ec0: port 0x62,0x66 on acpi0 > > pcib0: port 0xcf8-0xcff on acpi0 > > pci_link5: BIOS IRQ 10 for 0.10.INTA is invalid > > pci0: on pcib0 > > agp0: on hostb0 > > pcib1: at device 1.0 on pci0 > > pci1: on pcib1 > > vgapci0: port 0x9000-0x90ff mem > > 0xe0000000-0xefffffff,0xd0100000-0xd010ffff irq 10 at device 5.0 on > > pci1 > > ohci0: mem > > 0xd0006000-0xd0006fff irq 9 at device 2.0 on pci0 > > ohci0: [GIANT-LOCKED] > > ohci0: [ITHREAD] > > usb0: OHCI version 1.0, legacy support > > usb0: SMM does not respond, resetting > > usb0: on ohci0 > > usb0: USB revision 1.0 > > uhub0: on usb0 > > uhub0: 4 ports with 4 removable, self powered > > pcm0: port 0x8400-0x84ff mem 0xd0007000-0xd0007fff > > irq 5 at device 6.0 on pci0 > > pcm0: > > pcm0: [GIANT-LOCKED] > > pcm0: [ITHREAD] > > isab0: at device 7.0 on pci0 > > isa0: on isab0 > > pci0: at device 8.0 (no driver attached) > > bwi0: mem > > 0xd0004000-0xd0005fff irq 9 at device 9.0 on pci0 > > bwi0: [ITHREAD] > > bwi0: regwin: chipcommon (0x800), rev 2, vendor 0x4243 > > bwi0: BBP: id 0x4306, rev 0x2, pkg 0 > > bwi0: nregwin 6, cap 0x0000002a > > bwi0: regwin: 802.11 MAC (0x812), rev 4, vendor 0x4243 > > bwi0: has TX stats > > bwi0: MAC: rev 4 > > bwi0: regwin: pcmcia (0x80d), rev 1, vendor 0x4243 > > bwi0: regwin: v90 codec (0x807), rev 1, vendor 0x4243 > > bwi0: regwin: pci (0x804), rev 7, vendor 0x4243 > > bwi0: regwin: 802.11 MAC (0x812), rev 4, vendor 0x4243 > > bwi0: ignore second MAC > > bwi0: bus rev 0 > > bwi0: pci is enabled > > bwi0: card flags 0x000f > > bwi0: 0th led, act 3, lowact 0 > > bwi0: 1th led, act 5, lowact 0 > > bwi0: 2th led, act 4, lowact 0 > > bwi0: 3th led, act 0, lowact 0 > > bwi0: 802.11 MAC was already disabled > > bwi0: PHY is linked > > bwi0: PHY: type 2, rev 1, ver 1 > > bwi0: PHY: 802.11G attach > > bwi0: RF: manu 0x17f, type 0x2050, rev 2 > > bwi0: bus rev 0 > > bwi0: PHY is linked > > bwi0: 30bit bus space > > bwi0: max txpower from sprom: 57 dBm > > bwi0: invalid antenna gain in sprom > > bwi0: ant gain 8 dBm > > bwi0: region/domain max txpower 76 dBm > > bwi0: max txpower 57 dBm > > bwi0: sprom idle tssi: 0x003e > > bwi0: TSSI-TX power map: > > 71 71 70 70 70 70 70 69 > > 69 69 69 69 68 68 68 67 > > 67 67 66 66 66 66 65 65 > > 65 64 64 64 63 63 63 62 > > 61 61 61 60 59 59 58 57 > > 57 55 55 54 53 52 51 50 > > 49 48 47 44 43 42 39 37 > > 35 32 29 26 22 18 14 8 > > bwi0: idle tssi0: 62 > > bwi0: bus rev 0 > > bwi0: locale: 6 > > bwi0: WARNING: using obsoleted if_watchdog interface > > bwi0: Ethernet address: 00:90:4b:61:02:45 > > cbb0: irq 11 at device 10.0 on > pci0 > > cardbus0: on cbb0 > > pccard0: <16-bit PCCard bus> on cbb0 > > cbb0: [ITHREAD] > > fwohci0: mem > > 0xd0009000-0xd00097ff,0xd0000000-0xd0003fff irq 10 at device 12.0 on > > pci0 > > fwohci0: [FILTER] > > fwohci0: OHCI version 1.10 (ROM=1) > > fwohci0: No. of Isochronous channels is 4. > > fwohci0: EUI64 00:0d:9d:71:9e:43:0c:6a > > fwohci0: Phy 1394a available S400, 1 ports. > > fwohci0: Link S400, max_rec 2048 bytes. > > firewire0: on fwohci0 > > fwe0: on firewire0 > > if_fwe0: Fake Ethernet address: 02:0d:9d:43:0c:6a > > fwe0: Ethernet address: 02:0d:9d:43:0c:6a > > fwip0: on firewire0 > > fwip0: Firewire address: 00:0d:9d:71:9e:43:0c:6a @ 0xfffe00000000, > > S400, maxrec 2048 > > sbp0: on firewire0 > > dcons_crom0: on firewire0 > > dcons_crom0: bus_addr 0x12bc000 > > fwohci0: Initiate bus reset > > fwohci0: BUS reset > > fwohci0: node_id=0xc000ffc0, gen=1, CYCLEMASTER mode > > atapci0: port > > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x8080-0x808f at device 16.0 on > > pci0 > > atapci0: using PIO transfers above 137GB as workaround for 48bit DMA > > access bug, expect reduced performance > > ata0: on atapci0 > > ata0: [ITHREAD] > > ata1: on atapci0 > > ata1: [ITHREAD] > > pci0: at device 17.0 (no driver attached) > > sis0: port 0x8c00-0x8cff mem > > 0xd000a000-0xd000afff irq 11 at device 18.0 on pci0 > > sis0: Silicon Revision: DP83816A > > miibus0: on sis0 > > nsphyter0: PHY 0 on miibus0 > > nsphyter0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > > sis0: Ethernet address: 00:0d:9d:43:2b:a7 > > sis0: [ITHREAD] > > acpi_button0: on acpi0 > > acpi_lid0: on acpi0 > > acpi_acad0: on acpi0 > > battery0: on acpi0 > > acpi_tz0: on acpi0 > > atkbdc0: port 0x60,0x64 irq 1 on acpi0 > > atkbd0: irq 1 on atkbdc0 > > kbd0 at atkbd0 > > atkbd0: [GIANT-LOCKED] > > atkbd0: [ITHREAD] > > psm0: irq 12 on atkbdc0 > > psm0: [GIANT-LOCKED] > > psm0: [ITHREAD] > > psm0: model IntelliMouse, device ID 3 > > fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on > acpi0 > > fdc0: [FILTER] > > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on > > acpi0 > > sio0: type 16550A > > sio0: [FILTER] > > cpu0: on acpi0 > > powernow0: on cpu0 > > pmtimer0 on isa0 > > orm0: at iomem > > 0xc0000-0xcefff,0xcf000-0xcf7ff,0xdb000-0xdbfff,0xdc000-0xdffff pnpid > > ORM0000 on isa0 > > ppc0: at port 0x378-0x37f irq 7 on isa0 > > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > > ppc0: FIFO with 16/16/16 bytes threshold > > ppbus0: on ppc0 > > ppbus0: [ITHREAD] > > ppi0: on ppbus0 > > plip0: on ppbus0 > > plip0: WARNING: using obsoleted IFF_NEEDSGIANT flag > > lpt0: on ppbus0 > > lpt0: Interrupt-driven port > > ppc0: [GIANT-LOCKED] > > ppc0: [ITHREAD] > > sc0: at flags 0x100 on isa0 > > sc0: VGA <16 virtual consoles, flags=0x300> > > sio1: configured irq 3 not in bitmap of probed irqs 0 > > sio1: port may not be enabled > > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > > ums0: on uhub0 > > ums0: 16 buttons and Z dir. > > Timecounter "TSC" frequency 1788943467 Hz quality 800 > > Timecounters tick every 1.000 msec > > firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) > > firewire0: bus manager 0 (me) > > ad0: 95396MB at ata0-master UDMA100 > > acd0: CDRW at ata1-master UDMA33 > > Trying to mount root from ufs:/dev/ad0s2a > > bwi0: bwi_init > > bwi0: bwi_stop > > bwi0: bbp atten: 0, rf atten: 3, ctrl1: 2, ctrl2: 65535 > > bwi0: bus rev 0 > > bwi0: 802.11 MAC is disabled > > bwi0: 802.11 MAC was already disabled > > bwi0: PHY is linked > > bwi0: bus rev 0 > > bwi0: PHY is unlinked > > bwi0: RF calibration value: 0x002a > > bwi0: bus rev 0 > > bwi0: PHY is linked > > firmware_get: failed to load firmware image bwi_v3_ucode4 > > bwi0: request firmware bwi_v3_ucode4 failed > > Looks like it either doesnt have such firmware loaded or firmware > is not supported for your card. bwi works only with firmware version 3 > and not with 4. > To get right answer look in current openbsd and dragonfly bwi driver if > your BCM94306MP is listed. > > -- > Paul > -- www.nealhogan.net From owner-freebsd-stable@FreeBSD.ORG Mon Jan 12 20:34:38 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DA47010656C8; Mon, 12 Jan 2009 20:34:38 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from mail-bw0-f20.google.com (mail-bw0-f20.google.com [209.85.218.20]) by mx1.freebsd.org (Postfix) with ESMTP id 04E048FC23; Mon, 12 Jan 2009 20:34:37 +0000 (UTC) (envelope-from onemda@gmail.com) Received: by bwz13 with SMTP id 13so7037658bwz.19 for ; Mon, 12 Jan 2009 12:34:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=M9xtz10Ijy61r1JRbc36V5WQyUFhvw8oEPzwrPc6l6o=; b=Zx6/+YM6iUZsWB2R4oYJ/mhWUUzHIm44Zgr48pLl7a6AjyiSXCcZcjN4cBEUOxRhVU xKenjiWFVSRFAoDBocsM/HrtD8BGzpjG0itaJcmq+qBMj25adzla+ecbWVqX+PPkjEel w1vrHwnU+2IBs2EZq0nY8zbU3/PcjO11/TELQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=LHmr+Kx9lOeMnKiIg58nhBJcoCM2AVaWv6Znz2PtnaV+70gHdiDNbyrXqHQQVfW50j Fn0HEgMmhFL9TLqTUSF7yUL2QATm675ZMaFi3L50cXOW2Yo1VRU3Z8q52SJyEX3f7Kgw 2bhpWK+3cY/+35A745uRxhrJOnJhCjlc5sev4= Received: by 10.223.110.144 with SMTP id n16mr1584440fap.63.1231792476509; Mon, 12 Jan 2009 12:34:36 -0800 (PST) Received: by 10.223.115.1 with HTTP; Mon, 12 Jan 2009 12:34:36 -0800 (PST) Message-ID: <3a142e750901121234t45a4b15dg91df69f983e9efd6@mail.gmail.com> Date: Mon, 12 Jan 2009 20:34:36 +0000 From: "Paul B. Mahol" To: "Neal Hogan" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <3a142e750901121032x79da7932se74c5511ec4a837b@mail.gmail.com> Cc: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: bwi: no DS tssi no OFDM tssi X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2009 20:34:40 -0000 On Mon, Jan 12, 2009 at 8:08 PM, Neal Hogan wrote: > I installed the firmware stuff from the dragonfly bwi(4) man page, yet I > have the same issue. Is there a way to tell whether the firmware they > provide supports my card? Like I said, I can locate my access point (and > others that are around) and ask for an IP . . . it seems as though I'm so > close. I'm fairly certain that I have all of the avliable bwi(4) bits > installed correctly. > > I dwonloaded and installed the driver and added *if_bwi_load="YES"* in my > loader.conf. I loaded the .ko file (bwi_v3). I downloaded and installed the > firmware from dflyBSD and followed their directions. Yet I get no offer. Is > the fact that I fail to get an offer indicate the firmware incompatinbility? 9 in BCM94306MP indicates that its supports 80211n and as such certainly it is not supported with bwi(4) and reason is that bwi developers do not plan to add support for 4 version firmware (when last time I played with bwi). > Anyway, thanks for you help. > > On Mon, Jan 12, 2009 at 12:32 PM, Paul B. Mahol wrote: >> >> On 1/12/09, Neal Hogan wrote: >> > Hello, >> > >> > I am attempting to get by broadcom wifi card up and running, am sick >> > of >> > trying to get ndis working, and am attempting to use the bwi driver >> > (originating in dragonflyBSD). I'm hoping others here have tried to do >> > the >> > same and have some pointers. I'm using 7.1-RELEASE (system/source are >> > in-sync) and my card is a BCM94306MP. My dmesg is posted below. >> > >> > Bwi(4) is installed and it recognizes my card (*if_bwi_load-"YES"* is in >> > my >> > /etc/rc.conf and *bwi_v3* and *if_bwi* are loaded). I can send a IP >> > request >> > to my WEP encrypted access point. Yet, it doesn't get an offer and says >> > that >> > *no DS tssi* and *no OFDM tssi* Being new to bwi(4) and have never seen >> > references to DS/OFDM tssi, I'm not sure what info to provide. My >> > research >> > is not leading anywhere helpful. Thanks. >> > >> > >> > >> > >> > Copyright (c) 1992-2009 The FreeBSD Project. >> > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 >> > The Regents of the University of California. All rights reserved. >> > FreeBSD is a registered trademark of The FreeBSD Foundation. >> > FreeBSD 7.1-RELEASE #0: Sat Jan 10 19:07:15 CST 2009 >> > nph@frege.lambdaserver:/usr/obj/usr/src/sys/GENERIC >> > Timecounter "i8254" frequency 1193182 Hz quality 0 >> > CPU: mobile AMD Athlon(tm) XP2400+ (1788.94-MHz 686-class CPU) >> > Origin = "AuthenticAMD" Id = 0x6a0 Stepping = 0 >> > >> > >> > Features=0x383f9ff >> > AMD Features=0xc0480800 >> > real memory = 468647936 (446 MB) >> > avail memory = 444530688 (423 MB) >> > kbd1 at kbdmux0 >> > ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, >> > RF5413) >> > acpi0: on motherboard >> > acpi0: [ITHREAD] >> > acpi0: Power Button (fixed) >> > Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 >> > acpi_timer0: <32-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0 >> > acpi_ec0: port 0x62,0x66 on acpi0 >> > pcib0: port 0xcf8-0xcff on acpi0 >> > pci_link5: BIOS IRQ 10 for 0.10.INTA is invalid >> > pci0: on pcib0 >> > agp0: on hostb0 >> > pcib1: at device 1.0 on pci0 >> > pci1: on pcib1 >> > vgapci0: port 0x9000-0x90ff mem >> > 0xe0000000-0xefffffff,0xd0100000-0xd010ffff irq 10 at device 5.0 on >> > pci1 >> > ohci0: mem >> > 0xd0006000-0xd0006fff irq 9 at device 2.0 on pci0 >> > ohci0: [GIANT-LOCKED] >> > ohci0: [ITHREAD] >> > usb0: OHCI version 1.0, legacy support >> > usb0: SMM does not respond, resetting >> > usb0: on ohci0 >> > usb0: USB revision 1.0 >> > uhub0: on >> > usb0 >> > uhub0: 4 ports with 4 removable, self powered >> > pcm0: port 0x8400-0x84ff mem 0xd0007000-0xd0007fff >> > irq 5 at device 6.0 on pci0 >> > pcm0: >> > pcm0: [GIANT-LOCKED] >> > pcm0: [ITHREAD] >> > isab0: at device 7.0 on pci0 >> > isa0: on isab0 >> > pci0: at device 8.0 (no driver attached) >> > bwi0: mem >> > 0xd0004000-0xd0005fff irq 9 at device 9.0 on pci0 >> > bwi0: [ITHREAD] >> > bwi0: regwin: chipcommon (0x800), rev 2, vendor 0x4243 >> > bwi0: BBP: id 0x4306, rev 0x2, pkg 0 >> > bwi0: nregwin 6, cap 0x0000002a >> > bwi0: regwin: 802.11 MAC (0x812), rev 4, vendor 0x4243 >> > bwi0: has TX stats >> > bwi0: MAC: rev 4 >> > bwi0: regwin: pcmcia (0x80d), rev 1, vendor 0x4243 >> > bwi0: regwin: v90 codec (0x807), rev 1, vendor 0x4243 >> > bwi0: regwin: pci (0x804), rev 7, vendor 0x4243 >> > bwi0: regwin: 802.11 MAC (0x812), rev 4, vendor 0x4243 >> > bwi0: ignore second MAC >> > bwi0: bus rev 0 >> > bwi0: pci is enabled >> > bwi0: card flags 0x000f >> > bwi0: 0th led, act 3, lowact 0 >> > bwi0: 1th led, act 5, lowact 0 >> > bwi0: 2th led, act 4, lowact 0 >> > bwi0: 3th led, act 0, lowact 0 >> > bwi0: 802.11 MAC was already disabled >> > bwi0: PHY is linked >> > bwi0: PHY: type 2, rev 1, ver 1 >> > bwi0: PHY: 802.11G attach >> > bwi0: RF: manu 0x17f, type 0x2050, rev 2 >> > bwi0: bus rev 0 >> > bwi0: PHY is linked >> > bwi0: 30bit bus space >> > bwi0: max txpower from sprom: 57 dBm >> > bwi0: invalid antenna gain in sprom >> > bwi0: ant gain 8 dBm >> > bwi0: region/domain max txpower 76 dBm >> > bwi0: max txpower 57 dBm >> > bwi0: sprom idle tssi: 0x003e >> > bwi0: TSSI-TX power map: >> > 71 71 70 70 70 70 70 69 >> > 69 69 69 69 68 68 68 67 >> > 67 67 66 66 66 66 65 65 >> > 65 64 64 64 63 63 63 62 >> > 61 61 61 60 59 59 58 57 >> > 57 55 55 54 53 52 51 50 >> > 49 48 47 44 43 42 39 37 >> > 35 32 29 26 22 18 14 8 >> > bwi0: idle tssi0: 62 >> > bwi0: bus rev 0 >> > bwi0: locale: 6 >> > bwi0: WARNING: using obsoleted if_watchdog interface >> > bwi0: Ethernet address: 00:90:4b:61:02:45 >> > cbb0: irq 11 at device 10.0 on >> > pci0 >> > cardbus0: on cbb0 >> > pccard0: <16-bit PCCard bus> on cbb0 >> > cbb0: [ITHREAD] >> > fwohci0: mem >> > 0xd0009000-0xd00097ff,0xd0000000-0xd0003fff irq 10 at device 12.0 on >> > pci0 >> > fwohci0: [FILTER] >> > fwohci0: OHCI version 1.10 (ROM=1) >> > fwohci0: No. of Isochronous channels is 4. >> > fwohci0: EUI64 00:0d:9d:71:9e:43:0c:6a >> > fwohci0: Phy 1394a available S400, 1 ports. >> > fwohci0: Link S400, max_rec 2048 bytes. >> > firewire0: on fwohci0 >> > fwe0: on firewire0 >> > if_fwe0: Fake Ethernet address: 02:0d:9d:43:0c:6a >> > fwe0: Ethernet address: 02:0d:9d:43:0c:6a >> > fwip0: on firewire0 >> > fwip0: Firewire address: 00:0d:9d:71:9e:43:0c:6a @ 0xfffe00000000, >> > S400, maxrec 2048 >> > sbp0: on firewire0 >> > dcons_crom0: on firewire0 >> > dcons_crom0: bus_addr 0x12bc000 >> > fwohci0: Initiate bus reset >> > fwohci0: BUS reset >> > fwohci0: node_id=0xc000ffc0, gen=1, CYCLEMASTER mode >> > atapci0: port >> > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x8080-0x808f at device 16.0 on >> > pci0 >> > atapci0: using PIO transfers above 137GB as workaround for 48bit DMA >> > access bug, expect reduced performance >> > ata0: on atapci0 >> > ata0: [ITHREAD] >> > ata1: on atapci0 >> > ata1: [ITHREAD] >> > pci0: at device 17.0 (no driver attached) >> > sis0: port 0x8c00-0x8cff mem >> > 0xd000a000-0xd000afff irq 11 at device 18.0 on pci0 >> > sis0: Silicon Revision: DP83816A >> > miibus0: on sis0 >> > nsphyter0: PHY 0 on miibus0 >> > nsphyter0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto >> > sis0: Ethernet address: 00:0d:9d:43:2b:a7 >> > sis0: [ITHREAD] >> > acpi_button0: on acpi0 >> > acpi_lid0: on acpi0 >> > acpi_acad0: on acpi0 >> > battery0: on acpi0 >> > acpi_tz0: on acpi0 >> > atkbdc0: port 0x60,0x64 irq 1 on acpi0 >> > atkbd0: irq 1 on atkbdc0 >> > kbd0 at atkbd0 >> > atkbd0: [GIANT-LOCKED] >> > atkbd0: [ITHREAD] >> > psm0: irq 12 on atkbdc0 >> > psm0: [GIANT-LOCKED] >> > psm0: [ITHREAD] >> > psm0: model IntelliMouse, device ID 3 >> > fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on >> > acpi0 >> > fdc0: [FILTER] >> > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on >> > acpi0 >> > sio0: type 16550A >> > sio0: [FILTER] >> > cpu0: on acpi0 >> > powernow0: on cpu0 >> > pmtimer0 on isa0 >> > orm0: at iomem >> > 0xc0000-0xcefff,0xcf000-0xcf7ff,0xdb000-0xdbfff,0xdc000-0xdffff pnpid >> > ORM0000 on isa0 >> > ppc0: at port 0x378-0x37f irq 7 on isa0 >> > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode >> > ppc0: FIFO with 16/16/16 bytes threshold >> > ppbus0: on ppc0 >> > ppbus0: [ITHREAD] >> > ppi0: on ppbus0 >> > plip0: on ppbus0 >> > plip0: WARNING: using obsoleted IFF_NEEDSGIANT flag >> > lpt0: on ppbus0 >> > lpt0: Interrupt-driven port >> > ppc0: [GIANT-LOCKED] >> > ppc0: [ITHREAD] >> > sc0: at flags 0x100 on isa0 >> > sc0: VGA <16 virtual consoles, flags=0x300> >> > sio1: configured irq 3 not in bitmap of probed irqs 0 >> > sio1: port may not be enabled >> > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on >> > isa0 >> > ums0: on >> > uhub0 >> > ums0: 16 buttons and Z dir. >> > Timecounter "TSC" frequency 1788943467 Hz quality 800 >> > Timecounters tick every 1.000 msec >> > firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) >> > firewire0: bus manager 0 (me) >> > ad0: 95396MB at ata0-master UDMA100 >> > acd0: CDRW at ata1-master UDMA33 >> > Trying to mount root from ufs:/dev/ad0s2a >> > bwi0: bwi_init >> > bwi0: bwi_stop >> > bwi0: bbp atten: 0, rf atten: 3, ctrl1: 2, ctrl2: 65535 >> > bwi0: bus rev 0 >> > bwi0: 802.11 MAC is disabled >> > bwi0: 802.11 MAC was already disabled >> > bwi0: PHY is linked >> > bwi0: bus rev 0 >> > bwi0: PHY is unlinked >> > bwi0: RF calibration value: 0x002a >> > bwi0: bus rev 0 >> > bwi0: PHY is linked >> > firmware_get: failed to load firmware image bwi_v3_ucode4 >> > bwi0: request firmware bwi_v3_ucode4 failed >> >> Looks like it either doesnt have such firmware loaded or firmware >> is not supported for your card. bwi works only with firmware version 3 >> and not with 4. >> To get right answer look in current openbsd and dragonfly bwi driver if >> your BCM94306MP is listed. >> >> -- >> Paul > > > > -- > www.nealhogan.net > -- Paul From owner-freebsd-stable@FreeBSD.ORG Mon Jan 12 21:04:17 2009 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2B3531065670 for ; Mon, 12 Jan 2009 21:04:17 +0000 (UTC) (envelope-from freebsd@max.af.czu.cz) Received: from chinook.internetservice.cz (caesar.internetservice.cz [217.11.237.121]) by mx1.freebsd.org (Postfix) with ESMTP id 921598FC1B for ; Mon, 12 Jan 2009 21:04:16 +0000 (UTC) (envelope-from freebsd@max.af.czu.cz) Received: (qmail 45346 invoked by uid 89); 12 Jan 2009 20:37:34 -0000 Received: from unknown (HELO ares.internetservice.cz) (public@chinook.internetservice.cz@217.11.239.237) by chinook.internetservice.cz with ESMTPA; 12 Jan 2009 20:37:34 -0000 Message-ID: <496BA9AE.10801@max.af.czu.cz> Date: Mon, 12 Jan 2009 21:35:58 +0100 From: Tomas Randa User-Agent: Thunderbird 2.0.0.14 (X11/20080723) MIME-Version: 1.0 To: Garance A Drosihn References: <042FE04A-2F8D-47DD-8454-7BBA3791D7A8@inoc.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@FreeBSD.org, Robert Watson Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2009 21:04:17 -0000 Hello, I have similar problems. The last "good" kernel I have from stable brach, october the 8. Then in next upgrade, I saw big problems with performance. I tried ULE, 4BSD etc, but nothing helps, only downgrading system back. Now I am trying 7.1-p1 and problems are here again. Mysql is waiting a lot of time with status "waiting for opening table" or "waiting for close tables" I have 32bit FreeBSD with PAE, 1x xeon 5420, supermicro motherboard, areca SATA controller. Could not be problem in "da" device for example? Thanks Tomas Randa Garance A Drosihn wrote: > At 2:55 PM +0000 1/12/09, Robert Watson wrote: >> On Fri, 9 Jan 2009, Garance A Drosihn wrote: >> >>> At 2:39 PM -0500 1/9/09, Robert Blayzor wrote: >>>> On Jan 8, 2009, at 8:58 PM, Pete French wrote: >>>>> I have a number of HP 1U servers, all of which were running 7.0 >>>>> perfectly happily. I have been testing 7.1 in it's various >>>>> incarnations for the last couple of months on our test server and >>>>> it has performed perfectly. >>>> >>>> I noticed a problem with 7.0 on a couple of Dell servers. [...] >>>> We've since then compiled the kernel under the BSD scheduler to >>>> rule that out, and so far so good. >>>> >>>> Since ULE is now default in 7.1 and not in 7.0, perhaps you can try >>>> that? >>> >>> FWIW, the other guy I know who is having this problem had already >>> switched to using ULE under 7.0-release, and did not have any >>> problems with it. So *his* problem was probably not related to >>> SCHED_ULE, unless something has recently changed there. >>> >>> Turns out he hasn't reverted back to 7.0-release just yet, so he's >>> going to try SCHED_4BSD and see if that helps his situation. >> >> Scheduler changes always come with some risk of exposing bugs that >> have existed in the code for a long time but never really manifested >> themselves. ULE is well shaken-out, having been under development for >> at least five years, but it is possible that some problems will >> become visible as a result of the switch. I would encourage people >> to stick with ULE, but if you're having a stability problem then >> experimenting with scheduler as a variable that could be triggering >> the problem may well be useful to help track down the bug. > > Just to followup on this: My friend did switch back to a 7.1 kernel with > SCHED_4BSD, and he still ran into problems. The error messages weren't > the same, but errors did happen in the same high disk-I/O situations as > the lockup happened with SCHED_ULE. At this point he's fallen back to > the 7.0-kernel that he had been running (which also has SCHED_ULE), and > all the problems have gone away. So at the moment he's running with a > 7.0-ish kernel and the 7.1-release userland, without the hanging > problems. > So the problem is something in the kernel, but it is *NOT* the scheduler > (at least, not in his case). > > He is not eager to do a whole lot of experiments to track down the > problem, since this is happening on busy production machines and he > can't afford to have a lot of downtime on them (especially now that the > semester at RPI has started up). The systems have some large (2 TB) > filesystems on them, and the lockups occur in high disk-I/O situations. > He's seeing the problem on one system which is a dual CPU quad-core > xeon, and another which is a 64 bit P4 with hyperthreading. The one > thing in common between the two setups is that the boot drives + a > 3ware controller (with its array of RAID disks) is moved from one > machine to the other one: > > "its a 3ware 9500 12 port model, the boot drive is connected to > an ICH6 in IDE mode, and yes, I've run it in single, single with > hyper threading, and 8 way mode. All 64 bit." > > We still have no idea where the problem really is. For all we know, > someone spilled a Pepsi on it when he wasn't looking... > From owner-freebsd-stable@FreeBSD.ORG Mon Jan 12 21:31:49 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C1326106564A for ; Mon, 12 Jan 2009 21:31:49 +0000 (UTC) (envelope-from kometen@gmail.com) Received: from mail-bw0-f20.google.com (mail-bw0-f20.google.com [209.85.218.20]) by mx1.freebsd.org (Postfix) with ESMTP id DEDBF8FC12 for ; Mon, 12 Jan 2009 21:31:48 +0000 (UTC) (envelope-from kometen@gmail.com) Received: by bwz13 with SMTP id 13so7138578bwz.19 for ; Mon, 12 Jan 2009 13:31:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=fhPCRsYcOHOSSGw+s49iZNGI0aoI2W32RJU7SQ0yCfk=; b=Cc8IgdERzNvhG5Wb4FMUXpUWnJ9XAFJe4Q89IvDxsobHZFUWsfrEGy178fEASFRZ3B PrIasCtMtPX42+pL2hu1TwNrsJek8NPhmvp4Ngnz9X6rwB3dLaBRnvp8y29F/1NVxRQZ O5A98aITZeL3+B4PSFbsoI4MJnF1/lCtNBiv0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=DEnfBClxUbXAQwDV6GqenCXOTiczYvvOZxLiY6Dmyb3fdPGBUXEUlUDzEVr+Y7VKFo +GcDoCXIzsx2E4hP1oXujEodk1etjCoGg68rslVkVaGZaD0CJ3CqW9/xcBlSUzEH4hGB SJgett54KmJIRV4J+ArSIhbO3JdmNb6N1ymzo= Received: by 10.103.160.9 with SMTP id m9mr10993592muo.53.1231795907527; Mon, 12 Jan 2009 13:31:47 -0800 (PST) Received: by 10.102.244.13 with HTTP; Mon, 12 Jan 2009 13:31:47 -0800 (PST) Message-ID: Date: Mon, 12 Jan 2009 22:31:47 +0100 From: "Claus Guttesen" To: "Tomas Randa" In-Reply-To: <496BA9AE.10801@max.af.czu.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <042FE04A-2F8D-47DD-8454-7BBA3791D7A8@inoc.net> <496BA9AE.10801@max.af.czu.cz> Cc: Robert Watson , freebsd-stable@freebsd.org, Garance A Drosihn Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2009 21:31:50 -0000 > I have similar problems. The last "good" kernel I have from stable brach, > october the 8. Then in next upgrade, I saw big problems with performance. > I tried ULE, 4BSD etc, but nothing helps, only downgrading system back. > > Now I am trying 7.1-p1 and problems are here again. Mysql is waiting a lot > of time with status "waiting for opening table" or "waiting for close > tables" > > I have 32bit FreeBSD with PAE, 1x xeon 5420, supermicro motherboard, areca > SATA controller. Could not be problem in "da" device for example? It was mentioned previous in this thread that CPUTYPE could be an issue. Did you change this if you customized your kernel? -- regards Claus When lenity and cruelty play for a kingdom, the gentler gamester is the soonest winner. Shakespeare From owner-freebsd-stable@FreeBSD.ORG Mon Jan 12 21:34:00 2009 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 10C461065675; Mon, 12 Jan 2009 21:34:00 +0000 (UTC) (envelope-from walt@relnor.com) Received: from rn-out-0910.google.com (rn-out-0910.google.com [64.233.170.185]) by mx1.freebsd.org (Postfix) with ESMTP id A28528FC20; Mon, 12 Jan 2009 21:33:59 +0000 (UTC) (envelope-from walt@relnor.com) Received: by rn-out-0910.google.com with SMTP id j71so7512956rne.12 for ; Mon, 12 Jan 2009 13:33:59 -0800 (PST) Received: by 10.65.97.18 with SMTP id z18mr20257839qbl.11.1231796038601; Mon, 12 Jan 2009 13:33:58 -0800 (PST) Received: by 10.64.199.2 with HTTP; Mon, 12 Jan 2009 13:33:58 -0800 (PST) Message-ID: <486185590901121333r7485ca7ga107f413f2c6e2e5@mail.gmail.com> Date: Mon, 12 Jan 2009 16:33:58 -0500 From: "Walter Venable" To: pyunyh@gmail.com In-Reply-To: <20090108023506.GF1256@cdnetworks.co.kr> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <8dfae1c10901070639x67945324jeeecfcac647d7976@mail.gmail.com> <8dfae1c10901071550s69d99802p31ca7c775f3d6823@mail.gmail.com> <20090108015036.GD1256@cdnetworks.co.kr> <486185590901071820tfcd3375sb890fe60867ec84d@mail.gmail.com> <20090108023506.GF1256@cdnetworks.co.kr> Cc: stable@freebsd.org, yongari@freebsd.org Subject: Re: FreeBSD 7.1 Breaks re and rl Network Interface Drivers X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2009 21:34:00 -0000 Pyun, I was able to perform a full source downgrade to 7.0 and all the problems went away. Curiously, re0 and re1 have reversed names -- what was re0 is now re1, and vice versa. I need my box to be up and working so I can't throw 7.1 on it again. If I can offer any data from 7.0, please let me know. On Wed, Jan 7, 2009 at 9:35 PM, Pyun YongHyeon wrote: > On Wed, Jan 07, 2009 at 09:20:05PM -0500, Walter Venable wrote: > > On Wed, Jan 7, 2009 at 8:50 PM, Pyun YongHyeon wrote: > > > Please show me full dmesg output. > > > > > > > Hi Pyun, > > I have attached the full dmesg output. > > Walter, I need dmesg output of 7.1-RELEASE. > > -- > Regards, > Pyun YongHyeon > From owner-freebsd-stable@FreeBSD.ORG Mon Jan 12 22:14:54 2009 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 79609106564A for ; Mon, 12 Jan 2009 22:14:54 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.9.129]) by mx1.freebsd.org (Postfix) with ESMTP id D0D2B8FC0C for ; Mon, 12 Jan 2009 22:14:53 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id A9AAF730A1; Mon, 12 Jan 2009 23:00:58 +0100 (CET) Date: Mon, 12 Jan 2009 23:00:58 +0100 From: Luigi Rizzo To: stable@freebsd.org Message-ID: <20090112220058.GA61788@onelab2.iet.unipi.it> References: <20090112181221.GA54984@onelab2.iet.unipi.it> <20090112183408.GE29426@gandalf.sssup.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090112183408.GE29426@gandalf.sssup.it> User-Agent: Mutt/1.4.2.3i Cc: fabio@gandalf.sssup.it Subject: New disk schedulers available for FreeBSD X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2009 22:14:54 -0000 Hi, Fabio Checconi and myself have developed a GEOM-based disk scheduler for FreeBSD. The scheduler is made of a GEOM kernel module, the corresponding userland claas library, and other loadable kernel modules that implement the actual scheduling algorithm. At the URL below you can find a tarball with full sources and also a set of pre-built modules/libraries for RELENG_7, to ease testing. http://feanor.sssup.it/~fabio/freebsd/io_sched/fc_sched.tar.gz Below you can find the README file that comes with the distribution. I would encourage people to try it and submit feedback, because the initial results are extremely interesting. While I just tried the code under RELENG_7/i386, it should build and work on all versions that have GEOM (but read below). Also the code is quite robust, because most of the difficult tasks (data moving, synchronization, etc.) are handled by GEOM, and the scheduler is only deciding which requests to serve and when. NOTE: The scheduler is designed to be distributed as a port, but it needs an extra field in 'struct bio' and a small change in function g_io_request() to work. Both changes are trivial but need a kernel rebuild. To try this code on AMD64 you do need to patch and rebuild the kernel. On i386, and purely to ease evaluation, we avoid the need for a kernel rebuild by patching one function in-memory (and patching it back when the module is unloaded). cheers luigi and fabio A copy of the README file follows: --- GEOM BASED DISK SCHEDULERS FOR FREEBSD --- This code contains a framework for GEOM-based disk schedulers and a couple of sample scheduling algorithms that use the framework and implement two forms of "anticipatory scheduling" (see below for more details). As a quick example of what this code can give you, try to run "dd", or "tar", or some other code with highly SEQUENTIAL access patterns, together with "cvs" or "cvsup" or other highly RANDOM access patterns (this is not a made-up example: it is pretty common for developers to have one or more apps doing random accesses, and others that do sequential accesses e.g., loading large binaries from disk, checking the integrity of tarballs, watching media streams and so on). These are the results we get on a local machine (AMD BE2400 dual core CPU, SATA 250GB disk): /mnt is a partition mounted on /dev/ad0s1f (or /dev/ad0-sched-s1f when used with the scheduler) cvs: cvs -d /mnt/home/ncvs-local update -Pd /mnt/ports dd-read: dd bs=128k of=/dev/null if=/dev/ad0 (or ad0-sched-) dd-writew dd bs=128k if=/dev/zero of=/mnt/largefile NO SCHEDULER RR SCHEDULER dd cvs dd cvs dd-read only 72 MB/s ---- 72 MB/s --- dd-write only 55 MB/s --- 55 MB/s --- dd-read+cvs 6 MB/s ok 30 MB/s ok dd-write+cvs 55 MB/s slooow 14 MB/s ok As you can see, when a cvs is running concurrently with dd, the performance drops dramatically, and depending on read or write mode, one of the two is severely penalized. The use of the RR scheduler in this example makes the dd-reader go much faster when competing with cvs, and lets cvs progress when competing with a writer. To try it out: 1. PLEASE READ CAREFULLY THE FOLLOWING: To avoid the need to rebuild a kernel, and just for testing purposes, we implemented a hack which consists in patching one kernel function (g_io_request) so that it executes the marking of "bio's" (I/O requests). Also, the classification info is stored in a rarely used field of struct bio. See details in the file g_sched.c . At the moment the 'patch' hack is only for i386 kernels built with standard flags. For other configurations, you need to manually patch sys/geom/geom_io.c as indicated by the error message that you will get. If you don't like the above, don't run this code. Also note that these hacks are only for testing purpose. If this code ever goes in the tree, it will use the correct approach which is adding a field to 'struct bio' to store the classification info, and modify g_io_request() to call a function to initialize that field. 2. PLEASE MAKE SURE THAT THE DISK THAT YOU WILL BE USING FOR TESTS DOES NOT CONTAIN PRECIOUS DATA. This is experimental code and may fail, especially at this stage. 3. EXTRACT AND BUILD THE PROGRAMS A 'make install' in the directory should work (with root privs), or you can even try the binary modules. If you want to build the modules yourself, look at the Makefile. 4. LOAD THE MODULE, CREATE A GEOM NODE, RUN TESTS kldload gsched_rr # --- configure the scheduler on device ad0 geom sched create -a rr ad0 # -- now you will have entries /dev/ad0-sched- For tests you can do the same as i did above, i.e. run concurrent programs that access the disk without the scheduler (/dev/ad0...) and with the scheduler (/dev/ad0-sched-...) and see the difference. --- NOTES ON THE SCHEDULERS --- The important contribution of this code is the framework to experiment with different scheduling algorithms. 'Anticipatory scheduling' is a very powerful technique based on the following reasoning: The disk throughput is much better if it serves sequential requests. If we have a mix of sequential and random requests, and we see a non-sequential request, do not serve it immediately but instead wait a little bit (2..5ms) to see if there is another one coming that the disk can serve more efficiently. There are many details that should be added to make sure that the mechanism is effective with different workloads and systems, to gain a few extra percent in performance, to improve fairness, insulation among processes etc. A discussion of the vast literature on the subject is beyond the purpose of this short note. -------------------------------------------------------------------------- From owner-freebsd-stable@FreeBSD.ORG Mon Jan 12 23:09:06 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C1DF110656C6 for ; Mon, 12 Jan 2009 23:09:06 +0000 (UTC) (envelope-from freebsd@optiksecurite.com) Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by mx1.freebsd.org (Postfix) with ESMTP id 92C448FC1E for ; Mon, 12 Jan 2009 23:09:06 +0000 (UTC) (envelope-from freebsd@optiksecurite.com) MIME-version: 1.0 Content-transfer-encoding: 8BIT Content-type: text/plain; charset=ISO-8859-1; format=flowed Received: from [69.69.69.183] ([69.70.93.206]) by VL-MH-MR002.ip.videotron.ca (Sun Java(tm) System Messaging Server 6.3-4.01 (built Aug 3 2007; 32bit)) with ESMTP id <0KDD00JDKPITASC1@VL-MH-MR002.ip.videotron.ca> for freebsd-stable@freebsd.org; Mon, 12 Jan 2009 17:08:53 -0500 (EST) Message-id: <496BBFF6.7010300@optiksecurite.com> Date: Mon, 12 Jan 2009 17:11:02 -0500 From: FreeBSD User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) To: pyunyh@gmail.com References: <8dfae1c10901070639x67945324jeeecfcac647d7976@mail.gmail.com> <8dfae1c10901071550s69d99802p31ca7c775f3d6823@mail.gmail.com> <88527079.20090111192206@donpac.ru> <20090112011146.GC46346@cdnetworks.co.kr> In-reply-to: <20090112011146.GC46346@cdnetworks.co.kr> Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 7.1 Breaks re and rl Network Interface Drivers X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2009 23:09:08 -0000 Pyun YongHyeon a écrit : > On Sun, Jan 11, 2009 at 07:22:06PM +0300, Eugene Gladchenko wrote: > > Walter, > > > > Thursday, January 8, 2009, 2:50:40 AM, you wrote: > > > > WV> Booting kernel.old, which is 7.0-RELEASE-p7 completely alleviates all > > WV> problems. I believe this roundly confirms that this is a bug in the > > WV> 7.1-RELEASE re kernel drivers. > > > > Does kern/130011 look similar? http://www.freebsd.org/cgi/query-pr.cgi?pr=130011 > > Do you have RTL8168C controller? If not, it's not related with > Walter's issue as 7.0-RELEASE didn't have a support for RTL8168C. > > > > > The re driver was really broken in 7.1-RC2 and the fix didn't get to 7.1-RELEASE. > > If you have re(4) issues, please provide more details such as > dmesg output, way to reproduce the issue etc. > Hi, I have the exact same card and the exact same problem as the PR you mentionned. re0@pci0:3:0:0: class=0x020000 card=0x02831028 chip=0x816810ec rev=0x02 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' class = network subclass = ethernet re0: port 0xd800-0xd8ff mem 0xfeaff000-0xfeafffff,0xfdff0000-0xfdffffff irq 18 at device 0.0 on pci3 re0: Chip rev. 0x3c000000 re0: MAC rev. 0x00400000 re0: PHY write failed re0: PHY write failed re0: MII without any phy! device_attach: re0 attach returned 6 I tried to compile a new kernel with the latest version of the 3 files listed in the PR: src/sys/dev/re/if_re.c,v 1.147 2008/12/22 00:46:22 yongari src/sys/pci/if_rl.c,v 1.170.2.10 2009/01/12 04:10:40 yongari src/sys/pci/if_rlreg.h,v 1.67.2.16 2009/01/12 03:48:25 yongari but I get the following error in buildworld: cc -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Werror /usr/src/sys/dev/re/if_re.c /usr/src/sys/dev/re/if_re.c: In function 're_miibus_statchg': /usr/src/sys/dev/re/if_re.c:594: error: 'RL_FLAG_FASTETHER' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c:594: error: (Each undeclared identifier is reported only once /usr/src/sys/dev/re/if_re.c:594: error: for each function it appears in.) /usr/src/sys/dev/re/if_re.c: In function 're_reset': /usr/src/sys/dev/re/if_re.c:703: error: 'RL_FLAG_PHY8169' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c:705: error: 'RL_FLAG_PHY8110S' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c: In function 're_attach': /usr/src/sys/dev/re/if_re.c:1160: error: 'RL_FLAG_PCIE' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c:1242: error: 'RL_FLAG_FASTETHER' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c:1245: error: 'RL_FLAG_PHY8110S' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c:1256: error: 'RL_FLAG_CMDSTOP' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c:1260: error: 'RL_FLAG_WOLRXENB' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c:1267: error: 'RL_FLAG_MACSLEEP' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c:1292: error: 'RL_FLAG_PHY8169' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c:1362: error: 'RL_MACDBG' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c:1363: error: 'RL_GPIO' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c: In function 're_int_task': /usr/src/sys/dev/re/if_re.c:2184: error: 'RL_FLAG_PCIE' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c: In function 're_stop': /usr/src/sys/dev/re/if_re.c:2908: error: 'RL_FLAG_CMDSTOP' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c:2909: error: 'RL_CMD_STOPREQ' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c: In function 're_resume': /usr/src/sys/dev/re/if_re.c:2989: error: 'RL_FLAG_MACSLEEP' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c:2990: error: 'RL_MACDBG' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c:2991: error: 'RL_GPIO' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c: In function 're_setwol': /usr/src/sys/dev/re/if_re.c:3050: error: 'RL_FLAG_MACSLEEP' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c:3051: error: 'RL_MACDBG' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c:3052: error: 'RL_GPIO' undeclared (first use in this function) /usr/src/sys/dev/re/if_re.c:3056: error: 'RL_FLAG_WOLRXENB' undeclared (first use in this function) *** Error code 1 Stop in /usr/obj/usr/src/sys/GENERIC. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. ------------ Thanks a lot for your help! Martin From owner-freebsd-stable@FreeBSD.ORG Tue Jan 13 00:05:03 2009 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E56F1106564A for ; Tue, 13 Jan 2009 00:05:03 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id BCAED8FC16 for ; Tue, 13 Jan 2009 00:05:03 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id 6289646B03; Mon, 12 Jan 2009 19:05:03 -0500 (EST) Date: Tue, 13 Jan 2009 00:05:03 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Tomas Randa In-Reply-To: <496BA9AE.10801@max.af.czu.cz> Message-ID: References: <042FE04A-2F8D-47DD-8454-7BBA3791D7A8@inoc.net> <496BA9AE.10801@max.af.czu.cz> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@FreeBSD.org, Garance A Drosihn Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 00:05:04 -0000 On Mon, 12 Jan 2009, Tomas Randa wrote: > I have similar problems. The last "good" kernel I have from stable brach, > october the 8. Then in next upgrade, I saw big problems with performance. I > tried ULE, 4BSD etc, but nothing helps, only downgrading system back. > > Now I am trying 7.1-p1 and problems are here again. Mysql is waiting a lot > of time with status "waiting for opening table" or "waiting for close > tables" > > I have 32bit FreeBSD with PAE, 1x xeon 5420, supermicro motherboard, areca > SATA controller. Could not be problem in "da" device for example? So far, this sounds like a different problem than the one others have been posting about, which involves full system freezes rather than specific processes wedging or responding poorly. I'd suggest starting by using "procstat -k" on the process ID to look at where specific threads are waiting in the kernel. Is it simply that MySQL is being unreasonably slow in certain situations, or does it actually entirely stop operating? If you're able to narrow down the date on the 7.x branch where the problem you're experiencing "begins", that would be most helpful. I'd suggest leaving your userspace on the 8th october, and sliding the kernel forward in a binary search until you've narrowed it down a bit. Obviously, this takes a bit of patience, but narrowing it down could be quite informative. Robert N M Watson Computer Laboratory University of Cambridge > > Thanks Tomas Randa > > Garance A Drosihn wrote: >> At 2:55 PM +0000 1/12/09, Robert Watson wrote: >>> On Fri, 9 Jan 2009, Garance A Drosihn wrote: >>> >>>> At 2:39 PM -0500 1/9/09, Robert Blayzor wrote: >>>>> On Jan 8, 2009, at 8:58 PM, Pete French wrote: >>>>>> I have a number of HP 1U servers, all of which were running 7.0 >>>>>> perfectly happily. I have been testing 7.1 in it's various incarnations >>>>>> for the last couple of months on our test server and it has performed >>>>>> perfectly. >>>>> >>>>> I noticed a problem with 7.0 on a couple of Dell servers. [...] We've >>>>> since then compiled the kernel under the BSD scheduler to rule that out, >>>>> and so far so good. >>>>> >>>>> Since ULE is now default in 7.1 and not in 7.0, perhaps you can try >>>>> that? >>>> >>>> FWIW, the other guy I know who is having this problem had already >>>> switched to using ULE under 7.0-release, and did not have any problems >>>> with it. So *his* problem was probably not related to SCHED_ULE, unless >>>> something has recently changed there. >>>> >>>> Turns out he hasn't reverted back to 7.0-release just yet, so he's going >>>> to try SCHED_4BSD and see if that helps his situation. >>> >>> Scheduler changes always come with some risk of exposing bugs that have >>> existed in the code for a long time but never really manifested >>> themselves. ULE is well shaken-out, having been under development for at >>> least five years, but it is possible that some problems will become >>> visible as a result of the switch. I would encourage people to stick with >>> ULE, but if you're having a stability problem then experimenting with >>> scheduler as a variable that could be triggering the problem may well be >>> useful to help track down the bug. >> >> Just to followup on this: My friend did switch back to a 7.1 kernel with >> SCHED_4BSD, and he still ran into problems. The error messages weren't >> the same, but errors did happen in the same high disk-I/O situations as >> the lockup happened with SCHED_ULE. At this point he's fallen back to >> the 7.0-kernel that he had been running (which also has SCHED_ULE), and >> all the problems have gone away. So at the moment he's running with a >> 7.0-ish kernel and the 7.1-release userland, without the hanging problems. >> So the problem is something in the kernel, but it is *NOT* the scheduler >> (at least, not in his case). >> >> He is not eager to do a whole lot of experiments to track down the >> problem, since this is happening on busy production machines and he >> can't afford to have a lot of downtime on them (especially now that the >> semester at RPI has started up). The systems have some large (2 TB) >> filesystems on them, and the lockups occur in high disk-I/O situations. >> He's seeing the problem on one system which is a dual CPU quad-core >> xeon, and another which is a 64 bit P4 with hyperthreading. The one >> thing in common between the two setups is that the boot drives + a >> 3ware controller (with its array of RAID disks) is moved from one >> machine to the other one: >> >> "its a 3ware 9500 12 port model, the boot drive is connected to >> an ICH6 in IDE mode, and yes, I've run it in single, single with >> hyper threading, and 8 way mode. All 64 bit." >> >> We still have no idea where the problem really is. For all we know, >> someone spilled a Pepsi on it when he wasn't looking... >> > From owner-freebsd-stable@FreeBSD.ORG Tue Jan 13 00:09:24 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 874CB1065672 for ; Tue, 13 Jan 2009 00:09:24 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 635E58FC0C for ; Tue, 13 Jan 2009 00:09:24 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id 1D97846B03; Mon, 12 Jan 2009 19:09:24 -0500 (EST) Date: Tue, 13 Jan 2009 00:09:24 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Pete French In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org, drosih@rpi.edu, rblayzor.bulk@inoc.net Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 00:09:24 -0000 On Mon, 12 Jan 2009, Pete French wrote: >> I'm not sure if you've done this already, but the normal suggestions apply: >> have you compiled with INVARIANTS/WITNESS/DDB/KDB/BREAK_TO_DEBUGGER, and do >> any results / panics / etc result? Sometimes these debugging tools are >> able to convert hangs into panics, which gives us much more ability to >> debug them. > > OK, I have now had a machine hand again, with the correct debug options in > the kernel. The screen looked like this when I went to restart it: > > http://toybox.twisted.org.uk/~pete/71_lor2.png > > It had not, however, dropped into any kind of debugger. Also there appear to > me console messages after the lock order reversal - is that normal ? Lock order reversals are warnings of potential deadlock due to a lock cycle, but deadlocks may not actually result, either because it's a false positive (some locking construct that is deadlock free but involves lock cycles), or because a cycle didn't actually form. The message is suggestive, but if you have significant system activity after the message, then it may be unrelated. > The machine did stay up for a signifanct amount of time before doing this. I > notice that it is more or less identical to the one I posted whenI had > WITNESS_KDB in the kernel too, so maybe those results arent entirely > suprious after all ? > > Given it hasnt dropped to a debugger, is there anything else I can try ? Features like WITNESS and INVARIANTS may change the timing of the kernel making certain race conditions less likely; I'd run with them for a bit and see if you can reproduce the hang with them present, as they will make debugging the problem a lot easier, if it's possible. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-stable@FreeBSD.ORG Tue Jan 13 00:13:25 2009 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 58D981065692 for ; Tue, 13 Jan 2009 00:13:25 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 310148FC24 for ; Tue, 13 Jan 2009 00:13:25 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id E0F4846B03; Mon, 12 Jan 2009 19:13:24 -0500 (EST) Date: Tue, 13 Jan 2009 00:13:24 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Garance A Drosihn In-Reply-To: Message-ID: References: <042FE04A-2F8D-47DD-8454-7BBA3791D7A8@inoc.net> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@FreeBSD.org Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 00:13:26 -0000 On Mon, 12 Jan 2009, Garance A Drosihn wrote: > He is not eager to do a whole lot of experiments to track down the problem, > since this is happening on busy production machines and he can't afford to > have a lot of downtime on them (especially now that the semester at RPI has > started up). The systems have some large (2 TB) filesystems on them, and > the lockups occur in high disk-I/O situations. He's seeing the problem on > one system which is a dual CPU quad-core xeon, and another which is a 64 bit > P4 with hyperthreading. The one thing in common between the two setups is > that the boot drives + a 3ware controller (with its array of RAID disks) is > moved from one machine to the other one: I think playing the combinatorics game on compile-time flags, kernel features, etc, is probably not the best way to go about debugging this. Instead, I'd debug this as a kernel hang by breaking into the debugger once it occurs, if possible, and ideally on a serial console. Often times hangs can be debugged looking solely at DDB output, or if possible, a crash dump. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-stable@FreeBSD.ORG Tue Jan 13 00:21:26 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 467671065673 for ; Tue, 13 Jan 2009 00:21:26 +0000 (UTC) (envelope-from andrew@modulus.org) Received: from email.octopus.com.au (email.octopus.com.au [122.100.2.232]) by mx1.freebsd.org (Postfix) with ESMTP id 07D158FC0C for ; Tue, 13 Jan 2009 00:21:25 +0000 (UTC) (envelope-from andrew@modulus.org) Received: by email.octopus.com.au (Postfix, from userid 1002) id 8120517E51; Tue, 13 Jan 2009 11:21:26 +1100 (EST) X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on email.octopus.com.au X-Spam-Level: X-Spam-Status: No, score=-1.4 required=10.0 tests=ALL_TRUSTED autolearn=failed version=3.2.3 Received: from [10.1.50.60] (ppp121-44-13-120.lns10.syd7.internode.on.net [121.44.13.120]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: admin@email.octopus.com.au) by email.octopus.com.au (Postfix) with ESMTP id 526AB17E54; Tue, 13 Jan 2009 11:21:21 +1100 (EST) Message-ID: <496BDE64.3020302@modulus.org> Date: Tue, 13 Jan 2009 11:20:52 +1100 From: Andrew Snow User-Agent: Thunderbird 2.0.0.14 (X11/20080523) MIME-Version: 1.0 To: Ivan Voras References: <200901120809.n0C89sib054679@lurza.secnetix.de> <496B1DA8.5010407@modulus.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: ZFSv13 in RELENG7 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 00:21:26 -0000 Ivan Voras wrote: > Andrew Snow wrote: >> Oliver Fromme wrote: >>> On the other hand, 8-current seems to run quite stable at >>> the moment; I have it running on a workstation for several >>> weeks without problems. >> What date of CURRENT are you running? I tracked down crashes related to >> changes in SMBFS, but I am still experiencing almost weekly crashes such >> as machine running out of swap space in the middle of the night for no >> apparent reason.. > > Are you running rsync? Are the crashes happenning at about 3 am? (these > two questions are unrelated) Yes, running lots of rsync. Also, yes, crashes have happened at night, not sure about 3am specifically, I've noticed more like 4am, 5am. But they always seem to happen when I'm not around. Most of our rsync processes happen at night starting from 7pm and running all night. - Andrew From owner-freebsd-stable@FreeBSD.ORG Tue Jan 13 00:31:20 2009 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 3D24B1065672; Tue, 13 Jan 2009 00:31:20 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.freebsd.org (Postfix) with ESMTP id F05828FC1A; Tue, 13 Jan 2009 00:31:19 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smarthost2.sentex.ca (8.14.3/8.14.3) with ESMTP id n0D0VHEo042147; Mon, 12 Jan 2009 19:31:17 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-stable.sentex.ca (freebsd-stable.sentex.ca [64.7.128.103]) by smtp1.sentex.ca (8.14.3/8.14.3) with ESMTP id n0D0VHvY077480; Mon, 12 Jan 2009 19:31:17 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-stable.sentex.ca (Postfix, from userid 666) id 9E9131B5060; Mon, 12 Jan 2009 19:31:17 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20090113003117.9E9131B5060@freebsd-stable.sentex.ca> Date: Mon, 12 Jan 2009 19:31:17 -0500 (EST) X-Virus-Scanned: ClamAV version 0.94.2, clamav-milter version 0.94.2 on clamscanner3 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.64 on 205.211.164.50 Cc: Subject: [releng_7 tinderbox] failure on powerpc/powerpc 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: Tue, 13 Jan 2009 00:31:21 -0000 TB --- 2009-01-12 23:22:06 - tinderbox 2.6 running on freebsd-stable.sentex.ca TB --- 2009-01-12 23:22:06 - starting RELENG_7 tinderbox run for powerpc/powerpc TB --- 2009-01-12 23:22:06 - cleaning the object tree TB --- 2009-01-12 23:22:27 - cvsupping the source tree TB --- 2009-01-12 23:22:27 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/powerpc/powerpc/supfile TB --- 2009-01-12 23:22:37 - building world TB --- 2009-01-12 23:22:37 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-12 23:22:37 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-12 23:22:37 - TARGET=powerpc TB --- 2009-01-12 23:22:37 - TARGET_ARCH=powerpc TB --- 2009-01-12 23:22:37 - TZ=UTC TB --- 2009-01-12 23:22:37 - __MAKE_CONF=/dev/null TB --- 2009-01-12 23:22:37 - cd /src TB --- 2009-01-12 23:22:37 - /usr/bin/make -B buildworld >>> World build started on Mon Jan 12 23:22:39 UTC 2009 >>> 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 >>> World build completed on Tue Jan 13 00:27:57 UTC 2009 TB --- 2009-01-13 00:27:57 - generating LINT kernel config TB --- 2009-01-13 00:27:57 - cd /src/sys/powerpc/conf TB --- 2009-01-13 00:27:57 - /usr/bin/make -B LINT TB --- 2009-01-13 00:27:57 - building LINT kernel TB --- 2009-01-13 00:27:57 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-13 00:27:57 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-13 00:27:57 - TARGET=powerpc TB --- 2009-01-13 00:27:57 - TARGET_ARCH=powerpc TB --- 2009-01-13 00:27:57 - TZ=UTC TB --- 2009-01-13 00:27:57 - __MAKE_CONF=/dev/null TB --- 2009-01-13 00:27:57 - cd /src TB --- 2009-01-13 00:27:57 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Tue Jan 13 00:27:58 UTC 2009 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] awk -f /src/sys/tools/makeobjops.awk /src/sys/dev/ata/ata_if.m -c ; cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -Werror ata_if.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -Werror /src/sys/dev/ata/ata-all.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -Werror /src/sys/dev/ata/ata-card.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -Werror /src/sys/dev/ata/ata-chipset.c /src/sys/dev/ata/ata-chipset.c: In function 'ata_marvell_ident': /src/sys/dev/ata/ata-chipset.c:2558: error: 'MV_61XX' undeclared (first use in this function) /src/sys/dev/ata/ata-chipset.c:2558: error: (Each undeclared identifier is reported only once /src/sys/dev/ata/ata-chipset.c:2558: error: for each function it appears in.) *** Error code 1 Stop in /obj/powerpc/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-01-13 00:31:16 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-01-13 00:31:16 - ERROR: failed to build lint kernel TB --- 2009-01-13 00:31:16 - 3493.72 user 348.45 system 4150.61 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-powerpc-powerpc.full From owner-freebsd-stable@FreeBSD.ORG Tue Jan 13 00:35:02 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 14E751065676 for ; Tue, 13 Jan 2009 00:35:02 +0000 (UTC) (envelope-from andrew@modulus.org) Received: from email.octopus.com.au (email.octopus.com.au [122.100.2.232]) by mx1.freebsd.org (Postfix) with ESMTP id CC3708FC16 for ; Tue, 13 Jan 2009 00:35:01 +0000 (UTC) (envelope-from andrew@modulus.org) Received: by email.octopus.com.au (Postfix, from userid 1002) id E7B7817E56; Tue, 13 Jan 2009 11:35:02 +1100 (EST) X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on email.octopus.com.au X-Spam-Level: X-Spam-Status: No, score=-1.4 required=10.0 tests=ALL_TRUSTED autolearn=failed version=3.2.3 Received: from [10.1.50.60] (ppp121-44-13-120.lns10.syd7.internode.on.net [121.44.13.120]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: admin@email.octopus.com.au) by email.octopus.com.au (Postfix) with ESMTP id EE61D17429; Tue, 13 Jan 2009 11:34:58 +1100 (EST) Message-ID: <496BE193.4070807@modulus.org> Date: Tue, 13 Jan 2009 11:34:27 +1100 From: Andrew Snow User-Agent: Thunderbird 2.0.0.14 (X11/20080523) MIME-Version: 1.0 To: Andriy Gapon References: <496B3E28.3070902@icyb.net.ua> In-Reply-To: <496B3E28.3070902@icyb.net.ua> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: fsck_y_enable: suboptimal/odd? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 00:35:02 -0000 Andriy Gapon wrote: > To me it seems like fsck_y passes suboptimal flags to fsck, it doesn't > have to examine each and every filesystem in fstab. I think think this is because it does a quick check first to see if it can run the fsck in background after boot into multi-user mode. If it cannot, then fsck exits and is re-run with fsck -y and runs in foreground mode. - Andrew From owner-freebsd-stable@FreeBSD.ORG Tue Jan 13 00:40:26 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C852E1065670 for ; Tue, 13 Jan 2009 00:40:26 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.239]) by mx1.freebsd.org (Postfix) with ESMTP id 8E99F8FC08 for ; Tue, 13 Jan 2009 00:40:26 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so12438022rvf.43 for ; Mon, 12 Jan 2009 16:40:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=QI2oyunlpicYdn8sfRjE1nGob5P1fQnNLipxiOZI5/A=; b=viWG6xxrwVeuoupxCu1oa/OR3BBxjTXxgLTlEmI7N/tdSmwxM4gFJePGkW8k5PhOfA 6K0qTzISX/HkLfwMeF1YaQw/d1zyboTE0u5/b6Z6lhXe1vdrw/qquOxxPk1g3ybRh/Mx zv7NXYlsJpXbHKpWawL96vcMcLQ4FhG37798c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=Wvo/1jdLMtl8AyiMeW9Z/loHHO7QA2fTBWQGTwhvvMcqFQ/j0SquAGRcKtePwzSQ6Y HqcXhz+EWvH9t8RiofxdwTJZ5lv1By1DzBS0Krx51a3iH1akK27hMCs/6z87PRQnnWb9 hb3sOnf2NH9qLVWYvbZrDr0n9WDyV+wTK3fwg= Received: by 10.141.122.1 with SMTP id z1mr14963748rvm.210.1231807226075; Mon, 12 Jan 2009 16:40:26 -0800 (PST) Received: from michelle.cdnetworks.co.kr ([211.53.35.84]) by mx.google.com with ESMTPS id b8sm13419687rvf.9.2009.01.12.16.40.23 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 12 Jan 2009 16:40:25 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.14.3/8.14.3) with ESMTP id n0D0eJto051234 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 13 Jan 2009 09:40:19 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.14.3/8.14.3/Submit) id n0D0eImp051233; Tue, 13 Jan 2009 09:40:18 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Tue, 13 Jan 2009 09:40:18 +0900 From: Pyun YongHyeon To: FreeBSD Message-ID: <20090113004018.GG46346@cdnetworks.co.kr> References: <8dfae1c10901070639x67945324jeeecfcac647d7976@mail.gmail.com> <8dfae1c10901071550s69d99802p31ca7c775f3d6823@mail.gmail.com> <88527079.20090111192206@donpac.ru> <20090112011146.GC46346@cdnetworks.co.kr> <496BBFF6.7010300@optiksecurite.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <496BBFF6.7010300@optiksecurite.com> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 7.1 Breaks re and rl Network Interface Drivers X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 00:40:27 -0000 On Mon, Jan 12, 2009 at 05:11:02PM -0500, FreeBSD wrote: > Pyun YongHyeon a ?crit : > >On Sun, Jan 11, 2009 at 07:22:06PM +0300, Eugene Gladchenko wrote: > > > Walter, > > > > > > Thursday, January 8, 2009, 2:50:40 AM, you wrote: > > > > > > WV> Booting kernel.old, which is 7.0-RELEASE-p7 completely alleviates > > all > > > WV> problems. I believe this roundly confirms that this is a bug in the > > > WV> 7.1-RELEASE re kernel drivers. > > > > > > Does kern/130011 look similar? > > http://www.freebsd.org/cgi/query-pr.cgi?pr=130011 > > > >Do you have RTL8168C controller? If not, it's not related with > >Walter's issue as 7.0-RELEASE didn't have a support for RTL8168C. > > > > > > > > The re driver was really broken in 7.1-RC2 and the fix didn't get to > > 7.1-RELEASE. > > > >If you have re(4) issues, please provide more details such as > >dmesg output, way to reproduce the issue etc. > > > > Hi, > > I have the exact same card and the exact same problem as the PR you > mentionned. > > re0@pci0:3:0:0: class=0x020000 card=0x02831028 chip=0x816810ec rev=0x02 > hdr=0x00 > vendor = 'Realtek Semiconductor' > device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' > class = network > subclass = ethernet > > > re0: Gigabit Ethernet> port 0xd800-0xd8ff mem > 0xfeaff000-0xfeafffff,0xfdff0000-0xfdffffff irq 18 at device 0.0 on pci3 > re0: Chip rev. 0x3c000000 > re0: MAC rev. 0x00400000 > re0: PHY write failed > re0: PHY write failed > re0: MII without any phy! > device_attach: re0 attach returned 6 > > I tried to compile a new kernel with the latest version of the 3 files > listed in the PR: > src/sys/dev/re/if_re.c,v 1.147 2008/12/22 00:46:22 yongari > src/sys/pci/if_rl.c,v 1.170.2.10 2009/01/12 04:10:40 yongari > src/sys/pci/if_rlreg.h,v 1.67.2.16 2009/01/12 03:48:25 yongari > You need lastest if_rl.c and if_rlreg.h as well as if_re.c. > but I get the following error in buildworld: [...] -- Regards, Pyun YongHyeon From owner-freebsd-stable@FreeBSD.ORG Tue Jan 13 01:10:54 2009 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id CA6E0106564A; Tue, 13 Jan 2009 01:10:52 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-stable@FreeBSD.org Date: Mon, 12 Jan 2009 20:10:34 -0500 User-Agent: KMail/1.6.2 References: <8dfae1c10901070639x67945324jeeecfcac647d7976@mail.gmail.com> <496B7C17.8010107@holzleiter.name> In-Reply-To: <496B7C17.8010107@holzleiter.name> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200901122010.37269.jkim@FreeBSD.org> Cc: Sascha Holzleiter Subject: Re: FreeBSD 7.1 Breaks re and rl Network Interface Drivers X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 01:10:54 -0000 On Monday 12 January 2009 12:21 pm, Sascha Holzleiter wrote: > Walter Venable wrote: > > FreeBSD 7.1 upgrade broke my network access, machine is totally > > offline (powered-on and I can play inside it at the terminal, but > > absolutely 0 network access): > > This happened AFTER make kernel but BEFORE make installworld. I > > think this implies it's a kernel driver issue. > > Hi, > > i see similar problems with a re card: > > re0@pci0:4:7:0: class=0x020000 card=0x816710ec chip=0x816710ec > rev=0x10 hdr=0x00 > vendor = 'Realtek Semiconductor' > device = 'RTL8169/8110 Family Gigabit Ethernet NIC' > class = network > subclass = ethernet > > After upgrading to 7.1-RELEASE (and also STABLE) the NIC doesn't > seem to receive any frames. I can see the DHCP Requests on the DHCP > Server but the DHCPOFFERS are never seen by the client with the re0 > device. After setting promiscious mode on the interface (i.e. by > tcpdump -ni re0) the interface begins to work fine. > > I've attached a complete dmesg output, but i think the detection > works fine, here the short version: > > re0: port > 0x9c00-0x9cff mem 0xdfdff000-0xdfdff0ff irq 20 at device 7.0 on > pci4 re0: Chip rev. 0x18000000 > re0: MAC rev. 0x00000000 > miibus0: on re0 > rgephy0: PHY 1 on miibus0 > rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, > 1000baseT, 1000baseT-FDX, auto > re0: Ethernet address: 00:1a:92:35:29:fa > re0: [FILTER] Please revert SVN r180519 (or CVS r1.95.2.22) and try again: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/re/if_re.c.diff?r1=1.95.2.21;r2=1.95.2.22 Jung-uk Kim From owner-freebsd-stable@FreeBSD.ORG Tue Jan 13 01:33:44 2009 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 D0FDD1065674; Tue, 13 Jan 2009 01:33:44 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.freebsd.org (Postfix) with ESMTP id 91F0D8FC0A; Tue, 13 Jan 2009 01:33:44 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smarthost2.sentex.ca (8.14.3/8.14.3) with ESMTP id n0D1XgC9046429; Mon, 12 Jan 2009 20:33:42 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-stable.sentex.ca (freebsd-stable.sentex.ca [64.7.128.103]) by smtp1.sentex.ca (8.14.3/8.14.3) with ESMTP id n0D1Xfl0009263; Mon, 12 Jan 2009 20:33:41 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-stable.sentex.ca (Postfix, from userid 666) id D390C1B5060; Mon, 12 Jan 2009 20:33:41 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20090113013341.D390C1B5060@freebsd-stable.sentex.ca> Date: Mon, 12 Jan 2009 20:33:41 -0500 (EST) X-Virus-Scanned: ClamAV version 0.94.2, clamav-milter version 0.94.2 on clamscanner2 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.64 on 205.211.164.50 Cc: Subject: [releng_7 tinderbox] failure on sparc64/sparc64 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: Tue, 13 Jan 2009 01:33:45 -0000 TB --- 2009-01-13 00:31:07 - tinderbox 2.6 running on freebsd-stable.sentex.ca TB --- 2009-01-13 00:31:07 - starting RELENG_7 tinderbox run for sparc64/sparc64 TB --- 2009-01-13 00:31:07 - cleaning the object tree TB --- 2009-01-13 00:31:22 - cvsupping the source tree TB --- 2009-01-13 00:31:22 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/sparc64/sparc64/supfile TB --- 2009-01-13 00:31:32 - building world TB --- 2009-01-13 00:31:32 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-13 00:31:32 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-13 00:31:32 - TARGET=sparc64 TB --- 2009-01-13 00:31:32 - TARGET_ARCH=sparc64 TB --- 2009-01-13 00:31:32 - TZ=UTC TB --- 2009-01-13 00:31:32 - __MAKE_CONF=/dev/null TB --- 2009-01-13 00:31:32 - cd /src TB --- 2009-01-13 00:31:32 - /usr/bin/make -B buildworld >>> World build started on Tue Jan 13 00:31:34 UTC 2009 >>> 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 >>> World build completed on Tue Jan 13 01:30:14 UTC 2009 TB --- 2009-01-13 01:30:14 - generating LINT kernel config TB --- 2009-01-13 01:30:14 - cd /src/sys/sparc64/conf TB --- 2009-01-13 01:30:14 - /usr/bin/make -B LINT TB --- 2009-01-13 01:30:15 - building LINT kernel TB --- 2009-01-13 01:30:15 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-13 01:30:15 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-13 01:30:15 - TARGET=sparc64 TB --- 2009-01-13 01:30:15 - TARGET_ARCH=sparc64 TB --- 2009-01-13 01:30:15 - TZ=UTC TB --- 2009-01-13 01:30:15 - __MAKE_CONF=/dev/null TB --- 2009-01-13 01:30:15 - cd /src TB --- 2009-01-13 01:30:15 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Tue Jan 13 01:30:15 UTC 2009 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] awk -f /src/sys/tools/makeobjops.awk /src/sys/dev/ata/ata_if.m -c ; cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medany -msoft-float -ffreestanding -Werror ata_if.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medany -msoft-float -ffreestanding -Werror /src/sys/dev/ata/ata-all.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medany -msoft-float -ffreestanding -Werror /src/sys/dev/ata/ata-card.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medany -msoft-float -ffreestanding -Werror /src/sys/dev/ata/ata-chipset.c /src/sys/dev/ata/ata-chipset.c: In function 'ata_marvell_ident': /src/sys/dev/ata/ata-chipset.c:2558: error: 'MV_61XX' undeclared (first use in this function) /src/sys/dev/ata/ata-chipset.c:2558: error: (Each undeclared identifier is reported only once /src/sys/dev/ata/ata-chipset.c:2558: error: for each function it appears in.) *** Error code 1 Stop in /obj/sparc64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-01-13 01:33:41 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-01-13 01:33:41 - ERROR: failed to build lint kernel TB --- 2009-01-13 01:33:41 - 3266.99 user 347.49 system 3753.93 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-sparc64-sparc64.full From owner-freebsd-stable@FreeBSD.ORG Tue Jan 13 02:45:15 2009 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 AC23E1065670 for ; Tue, 13 Jan 2009 02:45:15 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from mail-bw0-f20.google.com (mail-bw0-f20.google.com [209.85.218.20]) by mx1.freebsd.org (Postfix) with ESMTP id 0DDB48FC0C for ; Tue, 13 Jan 2009 02:45:14 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: by bwz13 with SMTP id 13so7467129bwz.19 for ; Mon, 12 Jan 2009 18:45:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=stu8bM+1jiQWsxk3d84Qk4uIw9DOp1dUdPLvICtACmE=; b=UZOsNhVsxftDBsvj6ueYQBfph0EcEAl9BVHeRafFvzpd8+8EA7r7i2rtBGd6EQXIYj iMrqKav/j6cvcjIAHFbGgi8PAaXutSy3FewJvX+F3LtnvxWUD6tTftmx77CLZX2nzAgf ZwT37e1RNsiy/wfYbqNwHp2uXgqQhKkDli0dU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=WKpWaMrQN+lD5EaW/UI41+6uk0dtialzj2tZ9a4utNxKtkBsEWsfYnutDVrFQOWi6Y NqcTtZooJhLPc3cB1p8v7AnX794d2EBwYxVwHzlRB4wU458qUieNk8xxa7cGjV+77IZr GQyV0DNz1nyzuNZjiZpMQ0fVZ6DAce7Nc19qY= Received: by 10.181.145.6 with SMTP id x6mr11209241bkn.94.1231814713820; Mon, 12 Jan 2009 18:45:13 -0800 (PST) Received: by 10.181.26.3 with HTTP; Mon, 12 Jan 2009 18:45:13 -0800 (PST) Message-ID: <7d6fde3d0901121845r6caf78c4vfec791e1afaa64c8@mail.gmail.com> Date: Mon, 12 Jan 2009 18:45:13 -0800 From: "Garrett Cooper" To: "Luigi Rizzo" In-Reply-To: <20090112220058.GA61788@onelab2.iet.unipi.it> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20090112181221.GA54984@onelab2.iet.unipi.it> <20090112183408.GE29426@gandalf.sssup.it> <20090112220058.GA61788@onelab2.iet.unipi.it> Cc: stable@freebsd.org, fabio@gandalf.sssup.it Subject: Re: New disk schedulers available for FreeBSD X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 02:45:15 -0000 On Mon, Jan 12, 2009 at 2:00 PM, Luigi Rizzo wrote: > Hi, > Fabio Checconi and myself have developed a GEOM-based disk scheduler > for FreeBSD. The scheduler is made of a GEOM kernel module, the > corresponding userland claas library, and other loadable kernel > modules that implement the actual scheduling algorithm. > > At the URL below you can find a tarball with full sources and > also a set of pre-built modules/libraries for RELENG_7, to ease testing. > > http://feanor.sssup.it/~fabio/freebsd/io_sched/fc_sched.tar.gz > > Below you can find the README file that comes with the distribution. > > I would encourage people to try it and submit feedback, because the > initial results are extremely interesting. While I just tried the > code under RELENG_7/i386, it should build and work on all versions > that have GEOM (but read below). Hi Luigi! Is this changeset already available in CURRENT? Thanks, -Garrett From owner-freebsd-stable@FreeBSD.ORG Tue Jan 13 04:11:17 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 67C23106564A for ; Tue, 13 Jan 2009 04:11:17 +0000 (UTC) (envelope-from ehrmann@gmail.com) Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by mx1.freebsd.org (Postfix) with ESMTP id 3F4678FC14 for ; Tue, 13 Jan 2009 04:11:16 +0000 (UTC) (envelope-from ehrmann@gmail.com) Received: from [10.0.0.158] (unknown [64.9.236.71]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id DD538D05AF for ; Mon, 12 Jan 2009 23:11:15 -0500 (EST) Message-ID: <496C1452.2020501@gmail.com> Date: Mon, 12 Jan 2009 20:10:58 -0800 From: David Ehrmann User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: zfs not exporting or unmounting X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 04:11:17 -0000 I tried to export/unmount my zpool: # zpool export tank cannot unmount '/tank': Device busy # zfs unmount /tank cannot unmount '/tank': Device busy but it wouldn't, so, after closing everything that could be using it, I tried again. No luck. Then I tried to see if I forgot something: # fstat -m /tank USER CMD PID FD MOUNT INUM MODE SZ|DV R/W NAME # lsof | grep tank I'm out of ideas. zpool export -f tank worked last time, but at the expense of taking down one drive in the mirror (it shouldn't have, but it did; I had to resilver it). The one thing: I just did freebsd-update upgrade -r 7.1-RELEASE, and possibly freebsd-update install. Thanks in advance. From owner-freebsd-stable@FreeBSD.ORG Tue Jan 13 05:02:33 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7F91B106564A for ; Tue, 13 Jan 2009 05:02:33 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.239]) by mx1.freebsd.org (Postfix) with ESMTP id 40B1B8FC08 for ; Tue, 13 Jan 2009 05:02:32 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so12540042rvf.43 for ; Mon, 12 Jan 2009 21:02:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=j85wN7IpJq4ygLQ90akdRpjY1mavSYvjlPrD8SVAwdc=; b=F4XdZyPsFYXeRikOO4bwLnQFFV0FlZK/svOUxGHI+0XQL58pF5k9elhuIHPGRI17kj 2JDkO1tgb2wmcp8zQAWxTX6MZlqTXrRI5UNOLcgZclmylwa0l2rb4kPv00Q9tQv+TS5m uvcjUi/we/NTcbfEBYVGOKMCTZ9QUYhVD/EjM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=IssE4BmWRr6J0/ewMFGhxBNUgWpT91MiHuoq4R1st8N3KrAQQBN66D5MJ0uNqZCEdV D9xuECj0rDZkD6HFlthFHv7c/+OfYKBLtz04wund8O5+IkHOhogI0A0N3/Gw/ivz0wbH usOZ0qCny/avKiLunREauqpSXYe2YcJ1bT/5Q= Received: by 10.141.29.8 with SMTP id g8mr15065672rvj.224.1231822952757; Mon, 12 Jan 2009 21:02:32 -0800 (PST) Received: from michelle.cdnetworks.co.kr ([211.53.35.84]) by mx.google.com with ESMTPS id b39sm6650822rvf.0.2009.01.12.21.02.29 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 12 Jan 2009 21:02:31 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.14.3/8.14.3) with ESMTP id n0D52PGq052001 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 13 Jan 2009 14:02:25 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.14.3/8.14.3/Submit) id n0D52NPn052000; Tue, 13 Jan 2009 14:02:23 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Tue, 13 Jan 2009 14:02:23 +0900 From: Pyun YongHyeon To: Dimitry Andric Message-ID: <20090113050223.GH46346@cdnetworks.co.kr> References: <8dfae1c10901070639x67945324jeeecfcac647d7976@mail.gmail.com> <8dfae1c10901071550s69d99802p31ca7c775f3d6823@mail.gmail.com> <88527079.20090111192206@donpac.ru> <20090112011146.GC46346@cdnetworks.co.kr> <64114.83.221.215.168.1231741940.squirrel@83.221.215.168> <20090112064121.GF46346@cdnetworks.co.kr> <496B71D3.5050203@andric.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="vkogqOf2sHV7VnPd" Content-Disposition: inline In-Reply-To: <496B71D3.5050203@andric.com> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org, eugene@donpac.ru Subject: Re: FreeBSD 7.1 Breaks re and rl Network Interface Drivers X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 05:02:33 -0000 --vkogqOf2sHV7VnPd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Jan 12, 2009 at 05:37:39PM +0100, Dimitry Andric wrote: > On 2009-01-12 07:41, Pyun YongHyeon wrote: > > I see, Unfortunately the issue was fixed in the end of 7.1-R > > release process so I wanted to get more exposure before MFC. > > I'll make sure to MFC to stable/7 after more testing. > > I'm also having problems with re's, in my case the interfaces take about > 10 seconds to come up, if they come up at all. After the interfaces are > up, half the time no packets go out at all. Usually it helps to bring > them down via the console, wait about 10 seconds, and then bring them up > again... > It looks like that RTL8169SC users see regression and I vaguely remember a couple of issues on RTL8169SC. As Jung-uk said in other post, would yoy try reverting r180519? If that have no effect would you try attached patch? > These are the following variant: > > FreeBSD 7.1-STABLE #0: Mon Jan 12 14:22:11 CET 2009 > [...] > re0: port 0xf000-0xf0ff mem 0xfdfff000-0xfdfff0ff irq 18 at device 9.0 on pci0 > re0: Chip rev. 0x18000000 > re0: MAC rev. 0x00000000 > miibus0: on re0 > rgephy0: PHY 1 on miibus0 > rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto > re0: Ethernet address: 00:30:18:a6:f1:a8 > re0: [FILTER] > re1: port 0xf200-0xf2ff mem 0xfdffe000-0xfdffe0ff irq 19 at device 11.0 on pci0 > re1: Chip rev. 0x18000000 > re1: MAC rev. 0x00000000 > miibus1: on re1 > rgephy1: PHY 1 on miibus1 > rgephy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto > re1: Ethernet address: 00:30:18:a6:f1:a9 > re1: [FILTER] > > And just FYI, r187080-r187083 that you recently committed (MFCs of > r184240-184243, r184245, 185575 and r186390), don't seem to change > anything for this situation. :( Those MFC are for rl(4), not re(4) so you should see no behavioural changes in re(4). -- Regards, Pyun YongHyeon --vkogqOf2sHV7VnPd Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="re.8169sc.diff" Index: sys/dev/re/if_re.c =================================================================== --- sys/dev/re/if_re.c (revision 187123) +++ sys/dev/re/if_re.c (working copy) @@ -1295,6 +1295,8 @@ case RL_HWREV_8169_8110SC: case RL_HWREV_8169_8110SBL: sc->rl_flags |= RL_FLAG_PHYWAKE | RL_FLAG_PHY8169; + if (hw_rev->rl_rev == RL_HWREV_8169_8110SC) + sc->rl_flags |= 0x10000; break; default: break; @@ -2504,6 +2506,7 @@ uint32_t align_dummy; u_char eaddr[ETHER_ADDR_LEN]; } eaddr; + int clk66; RL_LOCK_ASSERT(sc); @@ -2534,6 +2537,29 @@ } else cfg |= RL_CPLUSCMD_RXENB | RL_CPLUSCMD_TXENB; CSR_WRITE_2(sc, RL_CPLUS_CMD, cfg); + if ((sc->rl_flags & 0x10000) != 0) { + clk66 = (CSR_READ_1(sc, RL_CFG2) & RL_CFG2_PCI66MHZ) != 0; + switch (CSR_READ_4(sc, RL_TXCFG) & 0xFC800000) { + case 0x18000000: + /* 8169/8110SCd */ + if (clk66 > 0) + CSR_WRITE_4(sc, 0x7C, 0x000FFFFF); + else + CSR_WRITE_4(sc, 0x7C, 0x009FFFFF); + break; + case 0x98000000: + /* 8169/8110SCe */ + if (clk66 > 0) + CSR_WRITE_4(sc, 0x7C, 0x000FFF00); + else + CSR_WRITE_4(sc, 0x7C, 0x009FFF00); + break; + default: + break; + } + /* Disable interrupt mitigation. */ + CSR_WRITE_2(sc, 0xE2, 0); + } /* * Disable TSO if interface MTU size is greater than MSS * allowed in controller. --vkogqOf2sHV7VnPd-- From owner-freebsd-stable@FreeBSD.ORG Tue Jan 13 05:48:58 2009 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 241BD106564A for ; Tue, 13 Jan 2009 05:48:58 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.delphij.net (delphij-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:2c9::2]) by mx1.freebsd.org (Postfix) with ESMTP id B6D948FC16 for ; Tue, 13 Jan 2009 05:48:57 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.geekcn.org (tarsier.geekcn.org [211.166.10.233]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tarsier.delphij.net (Postfix) with ESMTPS id B6EC728449 for ; Tue, 13 Jan 2009 13:48:56 +0800 (CST) Received: from localhost (tarsier.geekcn.org [211.166.10.233]) by tarsier.geekcn.org (Postfix) with ESMTP id 28536ED9F5C; Tue, 13 Jan 2009 13:48:56 +0800 (CST) X-Virus-Scanned: amavisd-new at geekcn.org Received: from tarsier.geekcn.org ([211.166.10.233]) by localhost (mail.geekcn.org [211.166.10.233]) (amavisd-new, port 10024) with ESMTP id keD-ekkUJ-E8; Tue, 13 Jan 2009 13:48:51 +0800 (CST) Received: from charlie.delphij.net (c-67-188-86-134.hsd1.ca.comcast.net [67.188.86.134]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTPSA id 68BFEED9F59; Tue, 13 Jan 2009 13:48:47 +0800 (CST) DomainKey-Signature: a=rsa-sha1; s=default; d=delphij.net; c=nofws; q=dns; h=message-id:date:from:reply-to:organization:user-agent: mime-version:to:cc:subject:references:in-reply-to: x-enigmail-version:openpgp:content-type:content-transfer-encoding; b=HYre4OVa0pKISznPLXedR/MqBprmeS8GjtlwpJCDgqNWrfrQFpWSDFdUue8NkfZpf LrMqmQ9L/JZ/sKdlZM1vQ== Message-ID: <496C2B3D.2080400@delphij.net> Date: Mon, 12 Jan 2009 21:48:45 -0800 From: Xin LI Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.19 (X11/20090112) MIME-Version: 1.0 To: Garrett Cooper References: <20090112181221.GA54984@onelab2.iet.unipi.it> <20090112183408.GE29426@gandalf.sssup.it> <20090112220058.GA61788@onelab2.iet.unipi.it> <7d6fde3d0901121845r6caf78c4vfec791e1afaa64c8@mail.gmail.com> In-Reply-To: <7d6fde3d0901121845r6caf78c4vfec791e1afaa64c8@mail.gmail.com> X-Enigmail-Version: 0.95.7 OpenPGP: id=18EDEBA0; url=http://www.delphij.net/delphij.asc Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Luigi Rizzo , stable@freebsd.org, fabio@gandalf.sssup.it Subject: Re: New disk schedulers available for FreeBSD X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: d@delphij.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 05:48:58 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Garrett Cooper wrote: > On Mon, Jan 12, 2009 at 2:00 PM, Luigi Rizzo wrote: >> Hi, >> Fabio Checconi and myself have developed a GEOM-based disk scheduler >> for FreeBSD. The scheduler is made of a GEOM kernel module, the >> corresponding userland claas library, and other loadable kernel >> modules that implement the actual scheduling algorithm. >> >> At the URL below you can find a tarball with full sources and >> also a set of pre-built modules/libraries for RELENG_7, to ease testing. >> >> http://feanor.sssup.it/~fabio/freebsd/io_sched/fc_sched.tar.gz >> >> Below you can find the README file that comes with the distribution. >> >> I would encourage people to try it and submit feedback, because the >> initial results are extremely interesting. While I just tried the >> code under RELENG_7/i386, it should build and work on all versions >> that have GEOM (but read below). > > Hi Luigi! > Is this changeset already available in CURRENT? Not (yet). - -- Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAklsKz0ACgkQi+vbBBjt66A0oQCfaB3qBKF7QZ1lDMrSkHCmReUD Di4AoIBQgg/Pe8zKD6Y7TBZO3Mz4pqUj =pCBe -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Tue Jan 13 05:51:27 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 560171065688 for ; Tue, 13 Jan 2009 05:51:27 +0000 (UTC) (envelope-from ehrmann@gmail.com) Received: from mxout-03.mxes.net (mxout-03.mxes.net [216.86.168.178]) by mx1.freebsd.org (Postfix) with ESMTP id 2E75A8FC12 for ; Tue, 13 Jan 2009 05:51:26 +0000 (UTC) (envelope-from ehrmann@gmail.com) Received: from [10.0.0.158] (unknown [64.9.236.71]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id C5CB923E3F3 for ; Tue, 13 Jan 2009 00:51:25 -0500 (EST) Message-ID: <496C2BCC.9090903@gmail.com> Date: Mon, 12 Jan 2009 21:51:08 -0800 From: David Ehrmann User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <496C1452.2020501@gmail.com> In-Reply-To: <496C1452.2020501@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: zfs not exporting or unmounting X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 05:51:27 -0000 David Ehrmann wrote: > # fstat -m /tank I guess I should have used a different flag, but no luck there, either > USER CMD PID FD MOUNT INUM MODE SZ|DV R/W > NAME > > # lsof | grep tank > I did fix it. I had a runaway bash process (that kill -s HUP fixed, oddly enough), but why don't any of these commands list the files I have open, even when files really are open? From owner-freebsd-stable@FreeBSD.ORG Tue Jan 13 06:50:24 2009 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 9D2861065677 for ; Tue, 13 Jan 2009 06:50:24 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.9.129]) by mx1.freebsd.org (Postfix) with ESMTP id 619908FC1A for ; Tue, 13 Jan 2009 06:50:24 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 811F773098; Tue, 13 Jan 2009 07:55:32 +0100 (CET) Date: Tue, 13 Jan 2009 07:55:32 +0100 From: Luigi Rizzo To: Garrett Cooper Message-ID: <20090113065532.GA79190@onelab2.iet.unipi.it> References: <20090112181221.GA54984@onelab2.iet.unipi.it> <20090112183408.GE29426@gandalf.sssup.it> <20090112220058.GA61788@onelab2.iet.unipi.it> <7d6fde3d0901121845r6caf78c4vfec791e1afaa64c8@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7d6fde3d0901121845r6caf78c4vfec791e1afaa64c8@mail.gmail.com> User-Agent: Mutt/1.4.2.3i Cc: stable@freebsd.org, fabio@gandalf.sssup.it Subject: Re: New disk schedulers available for FreeBSD X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 06:50:25 -0000 On Mon, Jan 12, 2009 at 06:45:13PM -0800, Garrett Cooper wrote: > On Mon, Jan 12, 2009 at 2:00 PM, Luigi Rizzo wrote: > > Hi, > > Fabio Checconi and myself have developed a GEOM-based disk scheduler > > for FreeBSD. The scheduler is made of a GEOM kernel module, the > > corresponding userland claas library, and other loadable kernel > > modules that implement the actual scheduling algorithm. > > > > At the URL below you can find a tarball with full sources and > > also a set of pre-built modules/libraries for RELENG_7, to ease testing. > > > > http://feanor.sssup.it/~fabio/freebsd/io_sched/fc_sched.tar.gz > > > > Below you can find the README file that comes with the distribution. > > > > I would encourage people to try it and submit feedback, because the > > initial results are extremely interesting. While I just tried the > > code under RELENG_7/i386, it should build and work on all versions > > that have GEOM (but read below). > > Hi Luigi! > Is this changeset already available in CURRENT? no but the port above should hopefully build under -current as well, unless there are changes in the GEOM ABI. I built it on RELENG_7 and RELENG_6, will try HEAD today. cheers luigi From owner-freebsd-stable@FreeBSD.ORG Tue Jan 13 09:11:33 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AACED1065672 for ; Tue, 13 Jan 2009 09:11:33 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by mx1.freebsd.org (Postfix) with ESMTP id 3BD088FC4C for ; Tue, 13 Jan 2009 09:11:32 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 27261 invoked by uid 399); 13 Jan 2009 09:11:32 -0000 Received: from localhost (HELO lap.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 13 Jan 2009 09:11:32 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <496C5AC2.90408@FreeBSD.org> Date: Tue, 13 Jan 2009 01:11:30 -0800 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.19 (X11/20090111) MIME-Version: 1.0 To: Pete French References: In-Reply-To: X-Enigmail-Version: 0.95.7 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: yanefbsd@gmail.com, freebsd-stable@freebsd.org, kometen@gmail.com Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 09:11:33 -0000 Pete French wrote: > Mine never lock up doing buildworlds either. They only lock up when they are > sitting there more of less idle! The machines which have never locked up > are the webservers, which are fairly heavlt loaded. The machine which locks > up the most frequently is a box sitting there doing nothing but DNS, which is > the most lightly loaded of the lot. Silly question but do you have powerd enabled on that server? If so, does disabling it help? Also do you have any of these in /etc/rc.conf (i.e., they are not the same as the default values in /etc/defaults/rc.conf): performance_cx_lowest="HIGH" # Online CPU idle state performance_cpu_freq="NONE" # Online CPU frequency economy_cx_lowest="HIGH" # Offline CPU idle state economy_cpu_freq="NONE" # Offline CPU frequency Doug -- This .signature sanitized for your protection From owner-freebsd-stable@FreeBSD.ORG Tue Jan 13 09:19:28 2009 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 B21AC106564A for ; Tue, 13 Jan 2009 09:19:28 +0000 (UTC) (envelope-from oliver@nemesis.charlie.mouhaha.de) Received: from nemesis.charlie.mouhaha.de (nemesis.charlie.mouhaha.de [78.47.10.193]) by mx1.freebsd.org (Postfix) with ESMTP id 70E838FC14 for ; Tue, 13 Jan 2009 09:19:28 +0000 (UTC) (envelope-from oliver@nemesis.charlie.mouhaha.de) Received: from localhost (nemesis.charlie.mouhaha.de [78.47.10.193]) by nemesis.charlie.mouhaha.de (Postfix) with ESMTP id 421BB93F4 for ; Tue, 13 Jan 2009 08:59:44 +0000 (GMT) X-Virus-Scanned: amavisd-new at mouhaha.de Received: from nemesis.charlie.mouhaha.de ([78.47.10.193]) by localhost (nemesis.charlie.mouhaha.de [78.47.10.193]) (amavisd-new, port 10024) with ESMTP id tz7irAuYkbUP for ; Tue, 13 Jan 2009 08:59:41 +0000 (GMT) Received: by nemesis.charlie.mouhaha.de (Postfix, from userid 1001) id BD7E593E4; Tue, 13 Jan 2009 08:59:41 +0000 (GMT) Date: Tue, 13 Jan 2009 08:59:41 +0000 From: Oliver Peter To: stable@freebsd.org Message-ID: <20090113085941.GA95736@nemesis.frida.mouhaha.de> References: <8dfae1c10901070639x67945324jeeecfcac647d7976@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8dfae1c10901070639x67945324jeeecfcac647d7976@mail.gmail.com> X-Operating-System: FreeBSD 7.1-RELEASE amd64 User-Agent: Mutt/1.5.18 (2008-05-17) Cc: Subject: Re: FreeBSD 7.1 Breaks re and rl Network Interface Drivers X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 09:19:28 -0000 I'm on 7.1-RELEASE/amd64 with the following card: re0@pci0:2:0:0: class=0x020000 card=0x368c1462 chip=0x816810ec rev=0x01 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' class = network subclass = ethernet And luckey me does not experience any network problems at all. But I have to say that I was suffering an interrupt storm, and some smart people told me just to remove USB and Firewire support from the kernel which has fixed the problem. Dunno if this helps you. -- Oliver PETER, email: oliver@peter.de.com, ICQ# 113969174 "If it feels good, you're doing something wrong." -- Coach McTavish From owner-freebsd-stable@FreeBSD.ORG Tue Jan 13 09:51:17 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 63FF6106566B for ; Tue, 13 Jan 2009 09:51:17 +0000 (UTC) (envelope-from kometen@gmail.com) Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.188]) by mx1.freebsd.org (Postfix) with ESMTP id E674B8FC19 for ; Tue, 13 Jan 2009 09:51:16 +0000 (UTC) (envelope-from kometen@gmail.com) Received: by mu-out-0910.google.com with SMTP id i2so4904165mue.3 for ; Tue, 13 Jan 2009 01:51:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=LaAqAE6X5VgKnlZBOVIWw7GTJYq9D4dSoVTBPaayRbc=; b=Bx4Ny00BQQRr8aPoCvcu1WR/7RzvjLalLLnXLen3GsW6IF4/vXWo3QOrMxoTIlMA71 jFysLrMTpqLmvW7fH+MHk8NrDB4iAfiyOHY5bF8BfURcpkjXGvnOfubDE+XxN2CWBXbG grS2zeoDX40DKxyvmvdF7/y+AIn8XmIySj3b8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=QdZxZ1sMdPzbCZ9PCccZ8a8IwmSyXTwBTA7EyxwNrSMeqITtjoB/VxC5cisR9NyiEq lhACvVrfVcwTVAIaidURGj6gYCzzxcuxogkNrMlePkIbUfnE8kTeM54SsfCBldvpDy5O 6CEDKBkTAvo2Bp36Sv3VbJZRwczkJmOvMKGfY= Received: by 10.103.172.7 with SMTP id z7mr11211532muo.15.1231840275521; Tue, 13 Jan 2009 01:51:15 -0800 (PST) Received: by 10.103.198.19 with HTTP; Tue, 13 Jan 2009 01:51:15 -0800 (PST) Message-ID: Date: Tue, 13 Jan 2009 10:51:15 +0100 From: "Claus Guttesen" To: "Doug Barton" In-Reply-To: <496C5AC2.90408@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <496C5AC2.90408@FreeBSD.org> Cc: freebsd-stable@freebsd.org Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 09:51:17 -0000 >> Mine never lock up doing buildworlds either. They only lock up when they are >> sitting there more of less idle! The machines which have never locked up >> are the webservers, which are fairly heavlt loaded. The machine which locks >> up the most frequently is a box sitting there doing nothing but DNS, which is >> the most lightly loaded of the lot. The server has been idle for a day now and is up and running. I have then copied a file to generate some i/o and it copies without problems. for ((a=0;a<10;a++)) do cp netbeans-6.5-ml-macosx.dmg ${a}.dmg & done I can't (fortunately) make it lock up. I have a DL360 G5 which is unused atm. and can test on it if needed. -- regards Claus When lenity and cruelty play for a kingdom, the gentler gamester is the soonest winner. Shakespeare From owner-freebsd-stable@FreeBSD.ORG Tue Jan 13 09:52:44 2009 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 3366E10656E7 for ; Tue, 13 Jan 2009 09:52:44 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.235]) by mx1.freebsd.org (Postfix) with ESMTP id F15FE8FC0A for ; Tue, 13 Jan 2009 09:52:43 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so12642719rvf.43 for ; Tue, 13 Jan 2009 01:52:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=XTRKzEm3Ig9B5yKMOxw3xrE2MkB9jDpxsdJ1iqJhC7s=; b=EErSvFFOE0MUkrpTkWXxOgHuBRwYXZWUX6SBciJjhpFrmbutud+T24CDDx6Gtai/AQ +nKrISZweaY5H3Xf5unhfMDSyavO0+tlkVtyWxDLVbePA2KiemlgUzfYFCzxweD/oGFn fOUcmcMjQDxvxzOjPtp5PJlfn3cu+QWbgneyY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=Bjdap51v/jUkPYfhDEjsN+AmZZmTN6B3GTw5K+KZdYi3Wi1fWVhgEyb/yQnaWrFDHh TF9hed9DGsPTgiswHyd9gZTZmE80t8SNygi+OnH7GAgYzxB2/HPSpcr16v+SMbK7Jhly RcNMuo0WT6+x709O3SYA4OEEzMwYVIfSEXIzk= Received: by 10.140.202.21 with SMTP id z21mr7045594rvf.260.1231840363504; Tue, 13 Jan 2009 01:52:43 -0800 (PST) Received: from michelle.cdnetworks.co.kr ([211.53.35.84]) by mx.google.com with ESMTPS id k2sm75355117rvb.6.2009.01.13.01.52.37 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 13 Jan 2009 01:52:42 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.14.3/8.14.3) with ESMTP id n0D9qWZ8052842 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 13 Jan 2009 18:52:32 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.14.3/8.14.3/Submit) id n0D9qW7m052841; Tue, 13 Jan 2009 18:52:32 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Tue, 13 Jan 2009 18:52:32 +0900 From: Pyun YongHyeon To: Oliver Peter Message-ID: <20090113095232.GJ46346@cdnetworks.co.kr> References: <8dfae1c10901070639x67945324jeeecfcac647d7976@mail.gmail.com> <20090113085941.GA95736@nemesis.frida.mouhaha.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090113085941.GA95736@nemesis.frida.mouhaha.de> User-Agent: Mutt/1.4.2.3i Cc: stable@freebsd.org Subject: Re: FreeBSD 7.1 Breaks re and rl Network Interface Drivers X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 09:52:44 -0000 On Tue, Jan 13, 2009 at 08:59:41AM +0000, Oliver Peter wrote: > I'm on 7.1-RELEASE/amd64 with the following card: > > re0@pci0:2:0:0: class=0x020000 card=0x368c1462 chip=0x816810ec rev=0x01 hdr=0x00 > vendor = 'Realtek Semiconductor' > device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' > class = network > subclass = ethernet > > And luckey me does not experience any network problems at all. > > But I have to say that I was suffering an interrupt storm, and some > smart people told me just to remove USB and Firewire support from the > kernel which has fixed the problem. > Read the following thread and enable MSI feature of re(4). http://lists.freebsd.org/pipermail/freebsd-stable/2008-December/047010.html > Dunno if this helps you. -- Regards, Pyun YongHyeon From owner-freebsd-stable@FreeBSD.ORG Tue Jan 13 10:30:57 2009 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CC7C810656EB for ; Tue, 13 Jan 2009 10:30:57 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from mail-gw0.york.ac.uk (mail-gw0.york.ac.uk [144.32.128.245]) by mx1.freebsd.org (Postfix) with ESMTP id 62AFE8FC23 for ; Tue, 13 Jan 2009 10:30:56 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from mail-gw6.york.ac.uk (mail-gw6.york.ac.uk [144.32.129.26]) by mail-gw0.york.ac.uk (8.13.6/8.13.6) with ESMTP id n0DAUsVX001034; Tue, 13 Jan 2009 10:30:54 GMT Received: from buffy-128.york.ac.uk ([144.32.128.160] helo=buffy.york.ac.uk) by mail-gw6.york.ac.uk with esmtps (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from ) id 1LMgXu-0006TJ-27; Tue, 13 Jan 2009 10:30:54 +0000 Received: from buffy.york.ac.uk (localhost [127.0.0.1]) by buffy.york.ac.uk (8.14.2/8.14.2) with ESMTP id n0DAUrCm070660; Tue, 13 Jan 2009 10:30:53 GMT (envelope-from gavin@FreeBSD.org) Received: (from ga9@localhost) by buffy.york.ac.uk (8.14.2/8.14.2/Submit) id n0DAUrlj070659; Tue, 13 Jan 2009 10:30:53 GMT (envelope-from gavin@FreeBSD.org) X-Authentication-Warning: buffy.york.ac.uk: ga9 set sender to gavin@FreeBSD.org using -f From: Gavin Atkinson To: Pete French In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Tue, 13 Jan 2009 10:30:53 +0000 Message-Id: <1231842653.70382.8.camel@buffy.york.ac.uk> Mime-Version: 1.0 X-Mailer: Evolution 2.22.2 FreeBSD GNOME Team Port X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin@freebsd.org Cc: freebsd-stable@FreeBSD.org Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 10:30:58 -0000 On Mon, 2009-01-12 at 19:00 +0000, Pete French wrote: > > I'm not sure if you've done this already, but the normal suggestions apply: > > have you compiled with INVARIANTS/WITNESS/DDB/KDB/BREAK_TO_DEBUGGER, and do > > any results / panics / etc result? Sometimes these debugging tools are able > > to convert hangs into panics, which gives us much more ability to debug them. > > OK, I have now had a machine hand again, with the correct debug options in > the kernel. The screen looked like this when I went to restart it: > > http://toybox.twisted.org.uk/~pete/71_lor2.png > > It had not, however, dropped into any kind of debugger. Also there appear > to me console messages after the lock order reversal - is that normal ? > > The machine did stay up for a signifanct amount of time before doing this. I > notice that it is more or less identical to the one I posted whenI > had WITNESS_KDB in the kernel too, so maybe those results arent > entirely suprious after all ? > > Given it hasnt dropped to a debugger, is there anything else I can try ? Can you break into the debugger with Ctrl-Alt-Esc, or by sending a break over the serial line? Gavin From owner-freebsd-stable@FreeBSD.ORG Tue Jan 13 11:45:47 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 21184106564A; Tue, 13 Jan 2009 11:45:47 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from constantine.ticketswitch.com (constantine.ticketswitch.com [IPv6:2002:57e0:1d4e:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id D75208FC18; Tue, 13 Jan 2009 11:45:46 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from dilbert.rattatosk ([10.64.50.6] helo=dilbert.ticketswitch.com) by constantine.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LMhiD-000ONw-Cn; Tue, 13 Jan 2009 11:45:37 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LMhiD-0000Rp-B2; Tue, 13 Jan 2009 11:45:37 +0000 To: rwatson@FreeBSD.org In-Reply-To: Message-Id: From: Pete French Date: Tue, 13 Jan 2009 11:45:37 +0000 Cc: freebsd-stable@freebsd.org, drosih@rpi.edu, rblayzor.bulk@inoc.net Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 11:45:47 -0000 > Lock order reversals are warnings of potential deadlock due to a lock cycle, > but deadlocks may not actually result, either because it's a false positive > (some locking construct that is deadlock free but involves lock cycles), or > because a cycle didn't actually form. The message is suggestive, but if you > have significant system activity after the message, then it may be unrelated. Its hard to tell in this case as there are no timestamps, so I cant see if there is any activity after the lockup. > Features like WITNESS and INVARIANTS may change the timing of the kernel > making certain race conditions less likely; I'd run with them for a bit and > see if you can reproduce the hang with them present, as they will make > debugging the problem a lot easier, if it's possible. Uh, the above *was* me reproducing the hang with them present ;-)) It quite happily hangs with thoise things in the kernel - indeed the next hang was immediately after I rebooted the machine. But even with WITNESS and INVARIANTS and all the rest it does not drop to a debugger, it simply locks up. That machine is currently turned off, but still has 7.1 installed. What would you like me to try now ? I have a lockup I can reproduce pretty reliably now (just wait and it will always lock up). I also found that my other 7.1 box locks up fairly reliably when doing a buildworld. The only similarily between these two machines and the ones which dont lock up is that these are serving DNS. The others don't. Note that all the hardware is identical, as is the installed software and the configuration. I am at a total loss... -pete. From owner-freebsd-stable@FreeBSD.ORG Tue Jan 13 11:49:59 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AA38F1065673; Tue, 13 Jan 2009 11:49:59 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from constantine.ticketswitch.com (constantine.ticketswitch.com [IPv6:2002:57e0:1d4e:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id 6EC1A8FC18; Tue, 13 Jan 2009 11:49:59 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from dilbert.rattatosk ([10.64.50.6] helo=dilbert.ticketswitch.com) by constantine.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LMhmQ-000OQZ-BA; Tue, 13 Jan 2009 11:49:58 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LMhmQ-0000T0-9M; Tue, 13 Jan 2009 11:49:58 +0000 To: freebsd@max.af.czu.cz, kometen@gmail.com In-Reply-To: Message-Id: From: Pete French Date: Tue, 13 Jan 2009 11:49:58 +0000 Cc: rwatson@freebsd.org, freebsd-stable@freebsd.org, drosih@rpi.edu Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 11:50:00 -0000 > It was mentioned previous in this thread that CPUTYPE could be an > issue. Did you change this if you customized your kernel? Actually, I think thats been ruled out as a possible cause, along with the scheduler. Certainly I have tried it both ways and there is no difference, and I think i saw that the others had too. -pete. From owner-freebsd-stable@FreeBSD.ORG Tue Jan 13 12:02:02 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A9F08106567A for ; Tue, 13 Jan 2009 12:02:02 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id A45C58FC37 for ; Tue, 13 Jan 2009 12:02:01 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id OAA14596; Tue, 13 Jan 2009 14:01:54 +0200 (EET) (envelope-from avg@icyb.net.ua) Message-ID: <496C82B1.9030604@icyb.net.ua> Date: Tue, 13 Jan 2009 14:01:53 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.18 (X11/20081124) MIME-Version: 1.0 To: Andrew Snow References: <496B3E28.3070902@icyb.net.ua> <496BE193.4070807@modulus.org> In-Reply-To: <496BE193.4070807@modulus.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: fsck_y_enable: suboptimal/odd? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 12:02:16 -0000 on 13/01/2009 02:34 Andrew Snow said the following: > Andriy Gapon wrote: > >> To me it seems like fsck_y passes suboptimal flags to fsck, it doesn't >> have to examine each and every filesystem in fstab. > > I think think this is because it does a quick check first to see if it > can run the fsck in background after boot into multi-user mode. > > If it cannot, then fsck exits and is re-run with fsck -y and runs in > foreground mode. True, I do not have softupdates enabled and I also have bg fsck explicietely prohibited. Still I do not understand why clean filesystems have to be checked. -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Tue Jan 13 12:42:09 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B498B1065686 for ; Tue, 13 Jan 2009 12:42:09 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 8FE168FC17 for ; Tue, 13 Jan 2009 12:42:09 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id 34B1746B23; Tue, 13 Jan 2009 07:42:09 -0500 (EST) Date: Tue, 13 Jan 2009 12:42:09 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Pete French In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org, drosih@rpi.edu, rblayzor.bulk@inoc.net Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 12:42:10 -0000 On Tue, 13 Jan 2009, Pete French wrote: >> Features like WITNESS and INVARIANTS may change the timing of the kernel >> making certain race conditions less likely; I'd run with them for a bit and >> see if you can reproduce the hang with them present, as they will make >> debugging the problem a lot easier, if it's possible. > > Uh, the above *was* me reproducing the hang with them present ;-)) It quite > happily hangs with thoise things in the kernel - indeed the next hang was > immediately after I rebooted the machine. But even with WITNESS and > INVARIANTS and all the rest it does not drop to a debugger, it simply locks > up. > > That machine is currently turned off, but still has 7.1 installed. What > would you like me to try now ? I have a lockup I can reproduce pretty > reliably now (just wait and it will always lock up). I also found that my > other 7.1 box locks up fairly reliably when doing a buildworld. > > The only similarily between these two machines and the ones which dont lock > up is that these are serving DNS. The others don't. Note that all the > hardware is identical, as is the installed software and the configuration. If you have BREAK_TO_DEBUGGER compiled into the kernel, then try pressing ctrl-alt-break on the console to see if you can drop into the debugger, or issue a serial break on a serial console. For somewhat complicated reasons to explain, serial breaks are more effective at getting into the debugger, so are preferable -- also because you can more easily log output from the debugger. If you are able to get into the debugger, the normal commands would be most helpful, especially if you can log the results: ps show lockedvnods show alllocks Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-stable@FreeBSD.ORG Tue Jan 13 13:43:54 2009 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 22856106566B; Tue, 13 Jan 2009 13:43:54 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from constantine.ticketswitch.com (constantine.ticketswitch.com [IPv6:2002:57e0:1d4e:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id DB5568FC16; Tue, 13 Jan 2009 13:43:53 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from dilbert.rattatosk ([10.64.50.6] helo=dilbert.ticketswitch.com) by constantine.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LMjYc-000PSA-5A; Tue, 13 Jan 2009 13:43:50 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LMjYc-00010m-3z; Tue, 13 Jan 2009 13:43:50 +0000 To: gavin@FreeBSD.org In-Reply-To: <1231842653.70382.8.camel@buffy.york.ac.uk> Message-Id: From: Pete French Date: Tue, 13 Jan 2009 13:43:50 +0000 Cc: freebsd-stable@FreeBSD.org Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 13:43:54 -0000 > Can you break into the debugger with Ctrl-Alt-Esc, or by sending a break > over the serial line? No, ctrl-alt-esc doesnt work, and there is no serial line on the machine (not that I can access anyway) -pete. From owner-freebsd-stable@FreeBSD.ORG Tue Jan 13 14:11:36 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 79E641065675; Tue, 13 Jan 2009 14:11:36 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from constantine.ticketswitch.com (constantine.ticketswitch.com [IPv6:2002:57e0:1d4e:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id 3AEAC8FC1C; Tue, 13 Jan 2009 14:11:36 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from dilbert.rattatosk ([10.64.50.6] helo=dilbert.ticketswitch.com) by constantine.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LMjzP-000Pgc-5w; Tue, 13 Jan 2009 14:11:31 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LMjzP-0000L6-4A; Tue, 13 Jan 2009 14:11:31 +0000 To: dougb@FreeBSD.org In-Reply-To: <496C5AC2.90408@FreeBSD.org> Message-Id: From: Pete French Date: Tue, 13 Jan 2009 14:11:31 +0000 Cc: yanefbsd@gmail.com, freebsd-stable@freebsd.org, kometen@gmail.com Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 14:11:36 -0000 > Silly question but do you have powerd enabled on that server? If so, > does disabling it help? Also do you have any of these in /etc/rc.conf > (i.e., they are not the same as the default values in > /etc/defaults/rc.conf): > performance_cx_lowest="HIGH" # Online CPU idle state > performance_cpu_freq="NONE" # Online CPU frequency > economy_cx_lowest="HIGH" # Offline CPU idle state > economy_cpu_freq="NONE" # Offline CPU frequency No, none of those. My rc.conf is below. The only slightly unusual thing I am doing is using lagg rather than the interfaces directly I guess, but that has worked fine for ages. -pete. hostname="florentine.rattatosk" cloned_interfaces="lagg0" network_interfaces="lo0 bce0 bce1 lagg0" ifconfig_bce0="up" ifconfig_bce1="up" ifconfig_lagg0="laggproto lacp laggport bce0 laggport bce1" ipv4_addrs_lagg0="10.48.19.0/16 10.48.19.229/16 10.48.19.223/16 10.48.19.243/16 10.48.19.226/16 10 .48.19.224/16 10.48.19.227/16 10.48.19.239/16 10.48.19.225/16 10.48.19.230/16 10.48.19.232/16 10.4 8.19.228/16 10.48.19.235/16 10.48.19.244/16 10.48.19.245/16" defaultrouter="10.48.0.9" inetd_enable="YES" sshd_enable="YES" dhcpd_enable="YES" dhcpd_ifaces="lagg0" dhcpd_flags="-q" dhcpd_conf="/usr/local/etc/dhcpd.conf" dhcpd_withumask="022" nfs_client_enable="YES" nfs_server_enable="YES" portmap_enable="YES" rpcbind_enable="YES" named_enable="YES" pdns_enable="YES" pdns_recursor_enable="NO" mysql_enable="YES" apache22_http_accept_enable="YES" apache22_enable="YES" ntpd_enable="YES" ntpd_sync_on_start="YES" exim_enable="YES" exim_flags="-bd -q10m" sendmail_enable="NONE" sendmail_submit_enable="NO" sendmail_outbound_enable="NO" sendmail_msp_queue_enable="NO" From owner-freebsd-stable@FreeBSD.ORG Tue Jan 13 14:52:37 2009 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E73041065674 for ; Tue, 13 Jan 2009 14:52:37 +0000 (UTC) (envelope-from sascha=freebsd-stable=freebsd.org=cdpwplml@holzleiter.name) Received: from serverbitch.de (unknown [IPv6:2001:8d8:80:11::351]) by mx1.freebsd.org (Postfix) with ESMTP id A8B968FC14 for ; Tue, 13 Jan 2009 14:52:37 +0000 (UTC) (envelope-from sascha=freebsd-stable=freebsd.org=cdpwplml@holzleiter.name) Received: from oinetka.gfsrv.net ([79.110.95.2] helo=dreamland.office.local) by serverbitch.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim) (envelope-from ) id 1LMkd9-0009Lq-1d; Tue, 13 Jan 2009 15:52:35 +0100 Message-ID: <496CAB07.5020404@holzleiter.name> Date: Tue, 13 Jan 2009 15:53:59 +0100 From: Sascha Holzleiter User-Agent: Thunderbird 2.0.0.18 (X11/20081126) MIME-Version: 1.0 To: Jung-uk Kim References: <8dfae1c10901070639x67945324jeeecfcac647d7976@mail.gmail.com> <496B7C17.8010107@holzleiter.name> <200901122010.37269.jkim@FreeBSD.org> In-Reply-To: <200901122010.37269.jkim@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@FreeBSD.org Subject: Re: FreeBSD 7.1 Breaks re and rl Network Interface Drivers X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 14:52:38 -0000 Jung-uk Kim wrote: > On Monday 12 January 2009 12:21 pm, Sascha Holzleiter wrote: >> Hi, >> >> i see similar problems with a re card: >> >> re0@pci0:4:7:0: class=0x020000 card=0x816710ec chip=0x816710ec >> rev=0x10 hdr=0x00 >> vendor = 'Realtek Semiconductor' >> device = 'RTL8169/8110 Family Gigabit Ethernet NIC' >> class = network >> subclass = ethernet >> >> After upgrading to 7.1-RELEASE (and also STABLE) the NIC doesn't >> seem to receive any frames. I can see the DHCP Requests on the DHCP >> Server but the DHCPOFFERS are never seen by the client with the re0 >> device. After setting promiscious mode on the interface (i.e. by >> tcpdump -ni re0) the interface begins to work fine. >> >> I've attached a complete dmesg output, but i think the detection >> works fine, here the short version: >> >> re0: port >> 0x9c00-0x9cff mem 0xdfdff000-0xdfdff0ff irq 20 at device 7.0 on >> pci4 re0: Chip rev. 0x18000000 >> re0: MAC rev. 0x00000000 >> miibus0: on re0 >> rgephy0: PHY 1 on miibus0 >> rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, >> 1000baseT, 1000baseT-FDX, auto >> re0: Ethernet address: 00:1a:92:35:29:fa >> re0: [FILTER] > > Please revert SVN r180519 (or CVS r1.95.2.22) and try again: > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/re/if_re.c.diff?r1=1.95.2.21;r2=1.95.2.22 Thanks! This fixed my problem. I now have DHCP and a running network interface again with a 7.1-STABLE and the reverted r180519 changes. If you need to test another version for the changes in r180519 let me know and i'll test them on this machine. Cheers, Sascha From owner-freebsd-stable@FreeBSD.ORG Tue Jan 13 15:15:45 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DC7241065677 for ; Tue, 13 Jan 2009 15:15:45 +0000 (UTC) (envelope-from freebsd@optiksecurite.com) Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by mx1.freebsd.org (Postfix) with ESMTP id ACEB08FC1B for ; Tue, 13 Jan 2009 15:15:45 +0000 (UTC) (envelope-from freebsd@optiksecurite.com) MIME-version: 1.0 Content-transfer-encoding: 8BIT Content-type: text/plain; charset=ISO-8859-1; format=flowed Received: from [69.69.69.183] ([69.70.93.206]) by VL-MH-MR001.ip.videotron.ca (Sun Java(tm) System Messaging Server 6.3-4.01 (built Aug 3 2007; 32bit)) with ESMTP id <0KDF005HW128B9B0@VL-MH-MR001.ip.videotron.ca> for freebsd-stable@freebsd.org; Tue, 13 Jan 2009 10:15:44 -0500 (EST) Message-id: <496CB0A2.2020103@optiksecurite.com> Date: Tue, 13 Jan 2009 10:17:54 -0500 From: FreeBSD User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) To: pyunyh@gmail.com References: <8dfae1c10901070639x67945324jeeecfcac647d7976@mail.gmail.com> <8dfae1c10901071550s69d99802p31ca7c775f3d6823@mail.gmail.com> <88527079.20090111192206@donpac.ru> <20090112011146.GC46346@cdnetworks.co.kr> <496BBFF6.7010300@optiksecurite.com> <20090113004018.GG46346@cdnetworks.co.kr> In-reply-to: <20090113004018.GG46346@cdnetworks.co.kr> Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 7.1 Breaks re and rl Network Interface Drivers X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 15:15:47 -0000 Pyun YongHyeon a écrit : > On Mon, Jan 12, 2009 at 05:11:02PM -0500, FreeBSD wrote: > > Pyun YongHyeon a ?crit : > > >On Sun, Jan 11, 2009 at 07:22:06PM +0300, Eugene Gladchenko wrote: > > > > Walter, > > > > > > > > Thursday, January 8, 2009, 2:50:40 AM, you wrote: > > > > > > > > WV> Booting kernel.old, which is 7.0-RELEASE-p7 completely alleviates > > > all > > > > WV> problems. I believe this roundly confirms that this is a bug in the > > > > WV> 7.1-RELEASE re kernel drivers. > > > > > > > > Does kern/130011 look similar? > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=130011 > > > > > >Do you have RTL8168C controller? If not, it's not related with > > >Walter's issue as 7.0-RELEASE didn't have a support for RTL8168C. > > > > > > > > > > > The re driver was really broken in 7.1-RC2 and the fix didn't get to > > > 7.1-RELEASE. > > > > > >If you have re(4) issues, please provide more details such as > > >dmesg output, way to reproduce the issue etc. > > > > > > > Hi, > > > > I have the exact same card and the exact same problem as the PR you > > mentionned. > > > > re0@pci0:3:0:0: class=0x020000 card=0x02831028 chip=0x816810ec rev=0x02 > > hdr=0x00 > > vendor = 'Realtek Semiconductor' > > device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' > > class = network > > subclass = ethernet > > > > > > re0: > Gigabit Ethernet> port 0xd800-0xd8ff mem > > 0xfeaff000-0xfeafffff,0xfdff0000-0xfdffffff irq 18 at device 0.0 on pci3 > > re0: Chip rev. 0x3c000000 > > re0: MAC rev. 0x00400000 > > re0: PHY write failed > > re0: PHY write failed > > re0: MII without any phy! > > device_attach: re0 attach returned 6 > > > > I tried to compile a new kernel with the latest version of the 3 files > > listed in the PR: > > src/sys/dev/re/if_re.c,v 1.147 2008/12/22 00:46:22 yongari > > src/sys/pci/if_rl.c,v 1.170.2.10 2009/01/12 04:10:40 yongari > > src/sys/pci/if_rlreg.h,v 1.67.2.16 2009/01/12 03:48:25 yongari > > > > You need lastest if_rl.c and if_rlreg.h as well as if_re.c. > That's exactly what I tried. Look at the 3 revision of the specified files. I even tried with a if_rl.c from the 22/12/08 but got the same problem. Thanks for your quick reply. > > but I get the following error in buildworld: > > [...] > From owner-freebsd-stable@FreeBSD.ORG Tue Jan 13 15:17:44 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E7B151065676; Tue, 13 Jan 2009 15:17:44 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from constantine.ticketswitch.com (constantine.ticketswitch.com [IPv6:2002:57e0:1d4e:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id 6B6658FC21; Tue, 13 Jan 2009 15:17:44 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from dilbert.rattatosk ([10.64.50.6] helo=dilbert.ticketswitch.com) by constantine.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LMl1D-0000aq-BG; Tue, 13 Jan 2009 15:17:27 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LMl1D-0000cm-9v; Tue, 13 Jan 2009 15:17:27 +0000 To: dougb@freebsd.org, kometen@gmail.com In-Reply-To: Message-Id: From: Pete French Date: Tue, 13 Jan 2009 15:17:27 +0000 Cc: freebsd-stable@freebsd.org Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 15:17:45 -0000 > I can't (fortunately) make it lock up. I have a DL360 G5 which is > unused atm. and can test on it if needed. Would it be possible to install that under amd64 and hammer it with DNS requests ? I have been trying to think what the difference might be between my webservers and the machines which are freezing, and the opnly one I an come up with is UDP traffic as the locking machines are serving DNS and also NFS. -pete. ,. From owner-freebsd-stable@FreeBSD.ORG Tue Jan 13 15:27:39 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F2D0F1065673 for ; Tue, 13 Jan 2009 15:27:38 +0000 (UTC) (envelope-from dimitry@andric.com) Received: from tensor.andric.com (cl-327.ede-01.nl.sixxs.net [IPv6:2001:7b8:2ff:146::2]) by mx1.freebsd.org (Postfix) with ESMTP id AEA968FC1E for ; Tue, 13 Jan 2009 15:27:38 +0000 (UTC) (envelope-from dimitry@andric.com) Received: from [IPv6:2001:7b8:3a7:0:288b:5365:201d:ccd6] (unknown [IPv6:2001:7b8:3a7:0:288b:5365:201d:ccd6]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 8E9EF11F838; Tue, 13 Jan 2009 16:27:37 +0100 (CET) Message-ID: <496CB2E7.2060902@andric.com> Date: Tue, 13 Jan 2009 16:27:35 +0100 From: Dimitry Andric User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.1b3pre) Gecko/20090108 Shredder/3.0b2pre MIME-Version: 1.0 To: pyunyh@gmail.com References: <8dfae1c10901070639x67945324jeeecfcac647d7976@mail.gmail.com> <8dfae1c10901071550s69d99802p31ca7c775f3d6823@mail.gmail.com> <88527079.20090111192206@donpac.ru> <20090112011146.GC46346@cdnetworks.co.kr> <64114.83.221.215.168.1231741940.squirrel@83.221.215.168> <20090112064121.GF46346@cdnetworks.co.kr> <496B71D3.5050203@andric.com> <20090113050223.GH46346@cdnetworks.co.kr> In-Reply-To: <20090113050223.GH46346@cdnetworks.co.kr> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, eugene@donpac.ru Subject: Re: FreeBSD 7.1 Breaks re and rl Network Interface Drivers X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 15:27:39 -0000 On 2009-01-13 06:02, Pyun YongHyeon wrote: > > I'm also having problems with re's, in my case the interfaces take about > > 10 seconds to come up, if they come up at all. After the interfaces are > > up, half the time no packets go out at all. Usually it helps to bring > > them down via the console, wait about 10 seconds, and then bring them up > > again... > It looks like that RTL8169SC users see regression and I vaguely > remember a couple of issues on RTL8169SC. As Jung-uk said in other > post, would yoy try reverting r180519? Reverting r180519 seems to solve the problem of not being able to send any packets. It does not solve the other problem, which is that the interfaces can take a very long time to come up at boot time, e.g: Setting hostuuid: 3ee65237-8025-11dc-9ab5-003018a6f1a8. Setting hostid: 0xaaedab9a. Mounting local file systems:. Setting hostname: tensor.andric.com. [... pauses for 10 seconds here ...] re0: link state changed to DOWN re1: link state changed to DOWN lo0: flags=8049 metric 0 mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 inet 127.0.0.1 netmask 0xff000000 re0: flags=8843 metric 0 mtu 1500 options=389b ether 00:30:18:a6:f1:a8 inet6 fe80::230:18ff:fea6:f1a8%re0 prefixlen 64 tentative scopeid 0x1 inet 87.251.56.140 netmask 0xffffffc0 broadcast 87.251.56.191 media: Ethernet autoselect (none) status: no carrier re1: flags=8843 metric 0 mtu 1500 options=389b ether 00:30:18:a6:f1:a9 inet6 fe80::230:18ff:fea6:f1a9%re1 prefixlen 64 tentative scopeid 0x2 inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255 media: Ethernet autoselect (none) status: no carrier [...] (note also the "no carrier" just after upping those interfaces) > If that have no effect would > you try attached patch? Apply this patch sometimes speeds up the interfaces going up at boot time, sometimes it doesn't, I'd say about 50/50. It doesn't solve the problem of not being able to send any packets. > > And just FYI, r187080-r187083 that you recently committed (MFCs of > > r184240-184243, r184245, 185575 and r186390), don't seem to change > > anything for this situation. :( > Those MFC are for rl(4), not re(4) so you should see no behavioural > changes in re(4). Sorry about that, I always keep mixing up re(4) and rl(4)... From owner-freebsd-stable@FreeBSD.ORG Tue Jan 13 15:31:28 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D779D106564A; Tue, 13 Jan 2009 15:31:28 +0000 (UTC) (envelope-from nathan@datanode.com) Received: from ns1.datanode.com (static-66-13-158-11.bdsl.verizon.net [66.13.158.11]) by mx1.freebsd.org (Postfix) with ESMTP id A08808FC19; Tue, 13 Jan 2009 15:31:28 +0000 (UTC) (envelope-from nathan@datanode.com) Received: from dni-mail.datanode.com ([172.23.1.17]) by ns1.datanode.com (8.14.3/8.13.1) with ESMTP id n0DF6bwZ012592; Tue, 13 Jan 2009 07:06:37 -0800 (PST) (envelope-from nathan@datanode.com) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Tue, 13 Jan 2009 07:06:36 -0800 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Big problems with 7.1 locking up :-( Thread-Index: Acl1fJgCryZN1w97RPKqD4xYqPOKUAAEt7ag References: From: "Nathan Way" To: "Robert Watson" , "Pete French" X-Datanode-MailScanner-Information: Please contact the ISP for more information X-MailScanner-ID: n0DF6bwZ012592 X-Datanode-MailScanner: Found to be clean X-Datanode-MailScanner-From: nathan@datanode.com Cc: freebsd-stable@freebsd.org Subject: RE: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 15:31:29 -0000 I also am experiencing lock-ups on a server recently upgraded from 7.0-RELEASE to 7.1-STABLE. This server is a Supermicro 6022 dual-Xeon box running a GENERIC i386 SMP kernel. Since upgrading to 7.1-STABLE it has started locking up daily. I see similar symptoms that Pete is seeing - no ping response, no keyboard response, no video output on a very lightly loaded server. =20 I have a test machine with duplicate hardware to the one locking up that I just finished installing 7.1-STABLE on but so far it hasn't locked up. Coincidentally my locking machine is also a DNS server but I have not enabled DNS on my test machine yet. Since the locking server is remote to me, I need to downgrade it to 7.0 to get it stable again. Once I finish that process, I can provide remote access to the 7.1-STABLE machine in my office if anyone would like to test with it. From owner-freebsd-stable@FreeBSD.ORG Tue Jan 13 16:10:50 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 93ED91065672; Tue, 13 Jan 2009 16:10:50 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 6EBC98FC14; Tue, 13 Jan 2009 16:10:50 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id 2A42646B58; Tue, 13 Jan 2009 11:10:50 -0500 (EST) Date: Tue, 13 Jan 2009 16:10:50 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Pete French In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: dougb@freebsd.org, freebsd-stable@freebsd.org, kometen@gmail.com Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 16:10:50 -0000 On Tue, 13 Jan 2009, Pete French wrote: >> I can't (fortunately) make it lock up. I have a DL360 G5 which is unused >> atm. and can test on it if needed. > > Would it be possible to install that under amd64 and hammer it with DNS > requests ? I have been trying to think what the difference might be between > my webservers and the machines which are freezing, and the opnly one I an > come up with is UDP traffic as the locking machines are serving DNS and also > NFS. There are significant changes in UDP locking between 7.0 and 7.1, so it could be that we're looking at a regression there. If you're able to reproduce this reliably, it might well be worth doing a little search-and-replace in udp_usrreq.c along the following lines: INP_RLOCK_ASSERT -> INP_WLOCK_ASSERT INP_RLOCK -> INP_WLOCK INP_RUNLOCK -> INP_WUNLOCK However, before making these changes for debugging purposes, make sure it's 100% reproduceable without them in the configuration so that we don't find ourselves barking up the wrong tree. Normally deadlocks along these lines *do* allow breaking into the debugger from a serial console, but since there are significant changes here in 7.1 it is worth trying to see if this might be related. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-stable@FreeBSD.ORG Tue Jan 13 16:33:59 2009 Return-Path: Delivered-To: FreeBSD-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2BFFD10656BA for ; Tue, 13 Jan 2009 16:33:59 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from mail-gw0.york.ac.uk (mail-gw0.york.ac.uk [144.32.128.245]) by mx1.freebsd.org (Postfix) with ESMTP id CF4A88FC29 for ; Tue, 13 Jan 2009 16:33:58 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from mail-gw7.york.ac.uk (mail-gw7.york.ac.uk [144.32.129.30]) by mail-gw0.york.ac.uk (8.13.6/8.13.6) with ESMTP id n0DGXpLJ019673; Tue, 13 Jan 2009 16:33:51 GMT Received: from buffy-128.york.ac.uk ([144.32.128.160] helo=buffy.york.ac.uk) by mail-gw7.york.ac.uk with esmtps (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from ) id 1LMmD9-0001vF-97; Tue, 13 Jan 2009 16:33:51 +0000 Received: from buffy.york.ac.uk (localhost [127.0.0.1]) by buffy.york.ac.uk (8.14.2/8.14.2) with ESMTP id n0DGXpEs072615; Tue, 13 Jan 2009 16:33:51 GMT (envelope-from gavin@FreeBSD.org) Received: (from ga9@localhost) by buffy.york.ac.uk (8.14.2/8.14.2/Submit) id n0DGXoLV072614; Tue, 13 Jan 2009 16:33:50 GMT (envelope-from gavin@FreeBSD.org) X-Authentication-Warning: buffy.york.ac.uk: ga9 set sender to gavin@FreeBSD.org using -f From: Gavin Atkinson To: "L1NYX01D@GMAIL.COM" In-Reply-To: <54540134.20090112212757@gmail.com> References: <54540134.20090112212757@gmail.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Tue, 13 Jan 2009 16:33:50 +0000 Message-Id: <1231864430.70382.26.camel@buffy.york.ac.uk> Mime-Version: 1.0 X-Mailer: Evolution 2.22.2 FreeBSD GNOME Team Port X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin@freebsd.org Cc: FreeBSD-stable@FreeBSD.org Subject: Re: FreeBSD 7.0 kernel panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 16:33:59 -0000 On Mon, 2009-01-12 at 21:27 +0300, L1NYX01D@GOOGLEMAIL.COM wrote: > Hello, FreeBSD-stable. > > Last week I have a lot of kernel panics like: Firstly: are these new panics on a system that has been reliable until now, or has something changed on the system recently (hardware change, different software in use, increased load, etc)? Is there any way you can reliably reproduce this? And is the panic message and backtrace always the same? > > Fatal trap 12: page fault while in kernel mode > > cpuid = 0; apic id = 00 > > fault virtual address = 0x9 > > fault code = supervisor read, page not present > > instruction pointer = 0x20:0xc079f1af > > stack pointer = 0x28:0xe5697c80 > > frame pointer = 0x28:0xe5697cbc > > code segment = base 0x0, limit 0xfffff, type 0x1b > > = DPL 0, pres 1, def32 1, gran 1 > > processor eflags = resume, IOPL = 0 > > current process = 14 (swi4: clock) > > trap number = 12 > > panic: page fault > > cpuid = 0 > > Uptime: 51m49s > > Physical memory: 2032 MB > > Dumping 177 MB: 162 146 130 114 98 82 66 50 34 18 2 > > > > #0 doadump () at pcpu.h:195 > > 195 __asm __volatile("movl %%fs:0,%0" : "=r" (td)); > > (kgdb) bt > > #0 doadump () at pcpu.h:195 > > #1 0xc078d1b7 in boot (howto=260) at > > /usr/src/sys/kern/kern_shutdown.c:409 > > #2 0xc078d479 in panic (fmt=Variable "fmt" is not available. > > ) at /usr/src/sys/kern/kern_shutdown.c:563 > > #3 0xc0a0eaac in trap_fatal (frame=0xe5697c40, eva=9) at /usr/src/sys/i386/i386/trap.c:899 > > #4 0xc0a0f42f in trap (frame=0xe5697c40) at /usr/src/sys/i386/i386/trap.c:280 > > #5 0xc09f565b in calltrap () at > > /usr/src/sys/i386/i386/exception.s:139 > > #6 0xc079f1af in softclock (dummy=0x0) at > > /usr/src/sys/kern/kern_timeout.c:202 > > #7 0xc076f31b in ithread_loop (arg=0xc5101250) at > > /usr/src/sys/kern/kern_intr.c:1036 > > #8 0xc076c119 in fork_exit (callout=0xc076f170 , arg=0xc5101250, frame=0xe5697d38) > > at /usr/src/sys/kern/kern_fork.c:781 > > #9 0xc09f56d0 in fork_trampoline () at > > /usr/src/sys/i386/i386/exception.s:205 > > (kgdb) > > What I should do? In kgdb, enter "frame 6" then "list". The output should show where in the code this occurred. You can then print any variables that look interesting by: p c p c->ctime Gavin From owner-freebsd-stable@FreeBSD.ORG Tue Jan 13 18:56:43 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3BE4D1065695; Tue, 13 Jan 2009 18:56:43 +0000 (UTC) (envelope-from kensmith@cse.Buffalo.EDU) Received: from phoebe.cse.buffalo.edu (phoebe.cse.buffalo.edu [128.205.32.89]) by mx1.freebsd.org (Postfix) with ESMTP id EA9368FC1F; Tue, 13 Jan 2009 18:56:42 +0000 (UTC) (envelope-from kensmith@cse.Buffalo.EDU) Received: from [128.205.32.76] (bauer.cse.buffalo.edu [128.205.32.76]) (authenticated bits=0) by phoebe.cse.buffalo.edu (8.14.1/8.13.7) with ESMTP id n0DIuXpZ099683 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 13 Jan 2009 13:56:36 -0500 (EST) (envelope-from kensmith@cse.buffalo.edu) From: Ken Smith To: Tomas Randa In-Reply-To: <496BA9AE.10801@max.af.czu.cz> References: <042FE04A-2F8D-47DD-8454-7BBA3791D7A8@inoc.net> <496BA9AE.10801@max.af.czu.cz> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-uJ1ZaLICaGZmjQaD2H1q" Organization: U. Buffalo CSE Department Date: Tue, 13 Jan 2009 13:56:33 -0500 Message-Id: <1231872993.16701.9.camel@bauer.cse.buffalo.edu> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 FreeBSD GNOME Team Port X-DCC-Buffalo.EDU-Metrics: phoebe.cse.buffalo.edu 1336; Body=0 Fuz1=0 Fuz2=0 X-Spam-Status: No, score=-4.0 required=5.0 tests=RCVD_IN_DNSWL_MED autolearn=failed version=3.2.3 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on phoebe.cse.buffalo.edu Cc: Robert Watson , freebsd-stable@freebsd.org, Garance A Drosihn Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 18:56:44 -0000 --=-uJ1ZaLICaGZmjQaD2H1q Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Mon, 2009-01-12 at 21:35 +0100, Tomas Randa wrote: > I have similar problems. The last "good" kernel I have from stable=20 > brach, october the 8. Then in next upgrade, I saw big problems with=20 > performance. > I tried ULE, 4BSD etc, but nothing helps, only downgrading system back. >=20 > Now I am trying 7.1-p1 and problems are here again. Mysql is waiting a=20 > lot of time with status "waiting for opening table" or "waiting for=20 > close tables" >=20 > I have 32bit FreeBSD with PAE, 1x xeon 5420, supermicro motherboard,=20 > areca SATA controller. Could not be problem in "da" device for example? >=20 > Thanks Tomas Randa Could you give r186860 a try? It is an MFC into stable/7 so if the machine in question is something you can experiment with just updating to stable/7 would take care of it. Otherwise if you could just manually apply the patch to a 7.1 source tree and do a test build of the kernel that would also do it. I'm not experiencing lockups but this patch helped a lot on a machine I have with a particular disk I/O pattern that resulted in extremely poor performance with 7.1-RELEASE. This patch brought it back to its normal performance level. Thanks. --=20 Ken Smith - From there to here, from here to | kensmith@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | --=-uJ1ZaLICaGZmjQaD2H1q Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEABECAAYFAkls49kACgkQ/G14VSmup/ZOdQCfT+O86ObizOSJOhpRm9+AQprW RzAAn2Hs5MSkUBjNZ4donsc6O4btnADM =Sykk -----END PGP SIGNATURE----- --=-uJ1ZaLICaGZmjQaD2H1q-- From owner-freebsd-stable@FreeBSD.ORG Tue Jan 13 19:27:27 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 92A2E10656CB for ; Tue, 13 Jan 2009 19:27:27 +0000 (UTC) (envelope-from korvus@comcast.net) Received: from QMTA05.emeryville.ca.mail.comcast.net (qmta05.emeryville.ca.mail.comcast.net [76.96.30.48]) by mx1.freebsd.org (Postfix) with ESMTP id 7CEC08FC12 for ; Tue, 13 Jan 2009 19:27:27 +0000 (UTC) (envelope-from korvus@comcast.net) Received: from OMTA07.emeryville.ca.mail.comcast.net ([76.96.30.59]) by QMTA05.emeryville.ca.mail.comcast.net with comcast id 30xj1b00E1GXsucA57TUDQ; Tue, 13 Jan 2009 19:27:28 +0000 Received: from [192.168.2.164] ([206.210.89.202]) by OMTA07.emeryville.ca.mail.comcast.net with comcast id 37TH1b0074Mx3R28T7TK1i; Tue, 13 Jan 2009 19:27:26 +0000 Message-ID: <496CEB13.5040806@comcast.net> Date: Tue, 13 Jan 2009 14:27:15 -0500 From: Steve Polyack User-Agent: Thunderbird 2.0.0.19 (X11/20090105) MIME-Version: 1.0 To: freebsd-hardware@freebsd.org, Mike Tancsa Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: amr driver changes in FreeBSD 7.1-RELEASE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 19:27:28 -0000 Hello, We have a Dell PowerEdge 1850 server. It contains two PERC4 RAID controllers. One is a PERC4e/Si, and the other is a PERC4/DC. Right now we are running FreeBSD 6.3-RELEASE, with a 36GB RAID-1 on the PERC4e/Si (amr0), and both a 1TB RAID5 and a 136GB RAID1 on the PERC4/DC(amr1). Both adapters are running the latest firmware revision. When we boot FreeBSD7.1 install media, the amr driver fails to detect any volumes (disks) attached to amr0, the PERC4e/Si. However, it picks up the attached disks on the PERC4/DC just fine. However, if I boot 7.0-RELEASE install media, it picks up all of the attached volumes, leading me to believe the issue is due to changes in the amr driver between 7.0 and 7.1. During the 7.1 boot process, before probing disks, we see the message "amr0: adapter is busy" show up twice. This also does not occur on the 6.3, 6.4, or 7.0 releases. We also have another PE1850 with a very similar configuration, except the two PERCs get probed in a different order, and it detects all of the attached volumes without any issues. Any suggestions? These are semi-critical systems, so we aren't always able to test things like this. But, we can schedule downtime once or twice a week if necessary. -Steve Polyack From owner-freebsd-stable@FreeBSD.ORG Tue Jan 13 19:28:57 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 37DF310656F4 for ; Tue, 13 Jan 2009 19:28:57 +0000 (UTC) (envelope-from redcrash@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.173]) by mx1.freebsd.org (Postfix) with ESMTP id 0C0158FC1B for ; Tue, 13 Jan 2009 19:28:56 +0000 (UTC) (envelope-from redcrash@gmail.com) Received: by wf-out-1314.google.com with SMTP id 24so155424wfg.7 for ; Tue, 13 Jan 2009 11:28:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=DVpTZoCyuIcrSF62rQ7/+ytiOTheKBx2iECpDqpNytI=; b=ejJnCeYXiD77SNpukg0CFIT4TAFIlxaX9WscMTWHJ0QYSRdugeaDk1nCKuYV7zVS9v hDpxEivmr91X08V/5n6x3gZqfCGiX1dopHTJjrTVk3klEVf6rrrTiHt3ETq2DDcCVHqp kIa5ZoXYZdydS8xFpm2D+g9JMDcCfjGNQALw4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=GG7aQ/D/xSa5LFJTB9AhoK23O8Elo4kBox0Md029WzFtsmy0HDm9z6HnIxn1kH6KO1 FGeM1hsDvbTf5D9roKYmXbXPX18uy8AOv6TmgMHwPRQBwqLV3cCKtJVpvJlT5vISncxx DatQ2gSgOvDxFVt3XSlYmV26ogPGpjP7j6ONA= Received: by 10.142.139.14 with SMTP id m14mr12986806wfd.100.1231873056539; Tue, 13 Jan 2009 10:57:36 -0800 (PST) Received: by 10.142.239.14 with HTTP; Tue, 13 Jan 2009 10:57:36 -0800 (PST) Message-ID: Date: Tue, 13 Jan 2009 19:57:36 +0100 From: "Harald Servat" To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: lenovo t400 does not start 7.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 19:28:57 -0000 Hello, I downloaded FreeBSD 7.1 (DVD iso image) for amd64 architecture (with correct SHA256 checksum), but I'm unable to start the system (Lenovo T400). The boot process starts fine, the BTX messages appear, the 7-option menu also appears, but when I hit enter (or when I choose start without ACPI or start in safe mode) the \ symbols starts spinning for a while and then freezes. I also tried with the 7.1-amd64-CD1, 7.1-i386-CD1 and a snapshot of 8.0-CURRENT dated from December. And the result is the same for all of them. Does anyone have any idea on what can be happening? Or at least, how can I gather more information about this issue? Thank you. -- _________________________________________________________________ Empty your memory, with a free()... like a pointer! If you cast a pointer to an integer, it becomes an integer, if you cast a pointer to a struct, it becomes a struct. The pointer can crash..., and can overflow. Be a pointer my friend... From owner-freebsd-stable@FreeBSD.ORG Tue Jan 13 19:59:36 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2BC1110656E7 for ; Tue, 13 Jan 2009 19:59:36 +0000 (UTC) (envelope-from minimarmot@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.171]) by mx1.freebsd.org (Postfix) with ESMTP id 4C3638FC4D for ; Tue, 13 Jan 2009 19:59:34 +0000 (UTC) (envelope-from minimarmot@gmail.com) Received: by wf-out-1314.google.com with SMTP id 24so168226wfg.7 for ; Tue, 13 Jan 2009 11:59:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=cdq7nM91Ddr9eDnVnpFqTIU5zBKjA6C1+y46y34Baz4=; b=X7X9ixL9QlcbPO4uWY3CBIADPMWpycOfSJQEw4yOM5MBAiHMN1FdCn43jLE00xUgz7 mwaKj9lDPXbrI1OP5yScot5UA8rxOtKeI6W0PKes6q/EPOPikVPdkMFgi+qtfPaPQjXc UB8QjynGj+Tt7+v/JKVItyDOYKXg4czG6wI6g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=OK+P/t3jWUjSy80QlmA7EzE+tG/xEYewQlvRUocy1JfpkGU3DC5PIh0qZtac/+vAge dKoS2jX920vK0x+alYKS6tzhB9tl5uRD5yqIwBqrGSi2gkvrfR6205ZgypKPjjkrURPR X1iwEq5rSbSkNh80diFWsiygdGfkBvC/Lr8qg= Received: by 10.143.11.11 with SMTP id o11mr13000369wfi.193.1231876773812; Tue, 13 Jan 2009 11:59:33 -0800 (PST) Received: by 10.143.114.8 with HTTP; Tue, 13 Jan 2009 11:59:33 -0800 (PST) Message-ID: <47d0403c0901131159v1076fc6am45b2ef3b7f6ed934@mail.gmail.com> Date: Tue, 13 Jan 2009 14:59:33 -0500 From: "Ben Kaduk" To: "Harald Servat" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Cc: freebsd-stable@freebsd.org Subject: Re: lenovo t400 does not start 7.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 19:59:47 -0000 On Tue, Jan 13, 2009 at 1:57 PM, Harald Servat wrote: > Hello, > > I downloaded FreeBSD 7.1 (DVD iso image) for amd64 architecture (with > correct SHA256 checksum), but I'm unable to start the system (Lenovo T400). > > The boot process starts fine, the BTX messages appear, the 7-option menu > also appears, but when I hit enter (or when I choose start without ACPI or > start in safe mode) the \ symbols starts spinning for a while and then > freezes. Have you tried an ISO for FreeBSD-CURRENT? I also have a T400, and definitely had FreeBSD running on it for a while, but I don't remember if it was 7 or current. -Ben Kaduk From owner-freebsd-stable@FreeBSD.ORG Tue Jan 13 20:18:42 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1834E1065675; Tue, 13 Jan 2009 20:18:42 +0000 (UTC) (envelope-from hiryu@neo-zeon.de) Received: from neo-zeon.de (dsl-63-249-90-167.cruzio.com [63.249.90.167]) by mx1.freebsd.org (Postfix) with ESMTP id E335D8FC0C; Tue, 13 Jan 2009 20:18:41 +0000 (UTC) (envelope-from hiryu@neo-zeon.de) Received: from [216.113.168.128] (helo=hanzo.local) by neo-zeon.de with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from ) id 1LMpS6-0007bl-1Q; Tue, 13 Jan 2009 12:01:33 -0800 From: Cameron To: freebsd-hardware@freebsd.org Date: Tue, 13 Jan 2009 12:01:28 -0800 User-Agent: KMail/1.9.9 References: <496CEB13.5040806@comcast.net> In-Reply-To: <496CEB13.5040806@comcast.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200901131201.28226.hiryu@neo-zeon.de> X-SA-Exim-Connect-IP: 216.113.168.128 X-SA-Exim-Mail-From: hiryu@neo-zeon.de X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on panzer.lan.nerv X-Spam-Level: X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-SA-Exim-Version: 4.2.1 (built Tue, 09 Jan 2007 17:23:22 +0000) X-SA-Exim-Scanned: Yes (on neo-zeon.de) Cc: Mike Tancsa , Steve Polyack Subject: Re: amr driver changes in FreeBSD 7.1-RELEASE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 20:18:43 -0000 Hello, This seems related to a problem I had with a 7.1-PRERELEASE (I have since upgraded to 7.1-RELEASE, but haven't not tested if the problem is still there). If I compiled the kernel with only the amr driver, it would not see my raid volume. If I enabled a separate scsi driver (I think it was some LSI Logic scsi driver) in addition to amr, the amr driver would work fine. I wish I could give some exact details (like the name of the other scsi driver), but this is on my home machine, and I'm currently at work. While a generic 7.1-PRERELEASE kernel had both of these compiled in (of course), and worked fine for me, I suspect our problems are related. I have an LSI Logic 150-4 SATA raid controller. -Cameron n Tuesday 13 January 2009 11:27:15 am Steve Polyack wrote: > Hello, > > We have a Dell PowerEdge 1850 server. It contains two PERC4 RAID > controllers. One is a PERC4e/Si, and the other is a PERC4/DC. Right > now we are running FreeBSD 6.3-RELEASE, with a 36GB RAID-1 on the > PERC4e/Si (amr0), and both a 1TB RAID5 and a 136GB RAID1 on the > PERC4/DC(amr1). Both adapters are running the latest firmware revision. > > When we boot FreeBSD7.1 install media, the amr driver fails to detect > any volumes (disks) attached to amr0, the PERC4e/Si. However, it picks > up the attached disks on the PERC4/DC just fine. However, if I boot > 7.0-RELEASE install media, it picks up all of the attached volumes, > leading me to believe the issue is due to changes in the amr driver > between 7.0 and 7.1. During the 7.1 boot process, before probing disks, > we see the message "amr0: adapter is busy" show up twice. This also > does not occur on the 6.3, 6.4, or 7.0 releases. > > We also have another PE1850 with a very similar configuration, except > the two PERCs get probed in a different order, and it detects all of the > attached volumes without any issues. > > Any suggestions? These are semi-critical systems, so we aren't always > able to test things like this. But, we can schedule downtime once or > twice a week if necessary. > > -Steve Polyack > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Tue Jan 13 20:25:00 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6D378106564A for ; Tue, 13 Jan 2009 20:25:00 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from core.tav.kiev.ua (tavex.colocall.com [62.149.10.42]) by mx1.freebsd.org (Postfix) with ESMTP id F0E458FC17 for ; Tue, 13 Jan 2009 20:24:59 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from 204-174-83-31.static569.dsl.ucc-net.ca ([204.174.83.31] helo=[10.80.5.156]) by core.tav.kiev.ua with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.52 (FreeBSD)) id 1LMpEp-000PLI-9w; Tue, 13 Jan 2009 21:47:48 +0200 Message-ID: <496CEFBE.8030007@bluezbox.com> Date: Tue, 13 Jan 2009 11:47:10 -0800 From: Oleksandr Tymoshenko User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Harald Servat References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Core-Spam-Level: ---- X-Core-Spam-Report: Spam detection software, running on the system "core.tav.kiev.ua", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Harald Servat wrote: > Hello, > > I downloaded FreeBSD 7.1 (DVD iso image) for amd64 architecture (with > correct SHA256 checksum), but I'm unable to start the system (Lenovo T400). > > The boot process starts fine, the BTX messages appear, the 7-option menu > also appears, but when I hit enter (or when I choose start without ACPI or > start in safe mode) the \ symbols starts spinning for a while and then > freezes. > > I also tried with the 7.1-amd64-CD1, 7.1-i386-CD1 and a snapshot of > 8.0-CURRENT dated from December. And the result is the same for all of them. > > Does anyone have any idea on what can be happening? Or at least, how can I > gather more information about this issue? Not sure about install CDs but I tried all these systems on my t400. I installed 7.0 then upgraded it to 7.1 and when it turned out that atheros is not 100% supported by it I upgraded to CURRENT. (I used cvsup for upgrades). What is your HW configuration? [...] Content analysis details: (-4.4 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Cc: freebsd-stable@freebsd.org Subject: Re: lenovo t400 does not start 7.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 20:25:00 -0000 Harald Servat wrote: > Hello, > > I downloaded FreeBSD 7.1 (DVD iso image) for amd64 architecture (with > correct SHA256 checksum), but I'm unable to start the system (Lenovo T400). > > The boot process starts fine, the BTX messages appear, the 7-option menu > also appears, but when I hit enter (or when I choose start without ACPI or > start in safe mode) the \ symbols starts spinning for a while and then > freezes. > > I also tried with the 7.1-amd64-CD1, 7.1-i386-CD1 and a snapshot of > 8.0-CURRENT dated from December. And the result is the same for all of them. > > Does anyone have any idea on what can be happening? Or at least, how can I > gather more information about this issue? Not sure about install CDs but I tried all these systems on my t400. I installed 7.0 then upgraded it to 7.1 and when it turned out that atheros is not 100% supported by it I upgraded to CURRENT. (I used cvsup for upgrades). What is your HW configuration? From owner-freebsd-stable@FreeBSD.ORG Tue Jan 13 20:40:43 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0FC09106566B for ; Tue, 13 Jan 2009 20:40:43 +0000 (UTC) (envelope-from redcrash@gmail.com) Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.28]) by mx1.freebsd.org (Postfix) with ESMTP id AE4558FC19 for ; Tue, 13 Jan 2009 20:40:42 +0000 (UTC) (envelope-from redcrash@gmail.com) Received: by yx-out-2324.google.com with SMTP id 8so100999yxb.13 for ; Tue, 13 Jan 2009 12:40:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=o4pIH6GodX9uix3UDXmh4PdRnjxVPAMImX0nHUysRV0=; b=vmmJnxOrSjOLOEW+RpxXQgsQt8JOkDe2fX6MCnrKxKF9cxuQWSWnb8Sq0jYkEnMmdJ 93LTHaccc/srbvEYNZwPJRhkxmxkUDCyVgwNvFPIoOH8pNLBEJ4jR8xIWCFUjB7CZJLE /UqGusK11L+dpzkJVSF7b6Ima/oZu0uTdk4JQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=NC9LP92rFI6lPHXkZ0r563PnIVCH4v0dVXtvIzTgKcIjc0KXre4FcQbIy7If1DzQbD t0rTQAyBXrLEM9X9dS75xrg+hcM+yYZqNOV0Oxkddh/T+py/jXk/djlouBd1lVPymGRs R+ejb1a93l6pTgEWQPnDHpZ8WusXmiE3bm0RY= Received: by 10.143.7.5 with SMTP id k5mr13026705wfi.176.1231879241627; Tue, 13 Jan 2009 12:40:41 -0800 (PST) Received: by 10.142.239.14 with HTTP; Tue, 13 Jan 2009 12:40:41 -0800 (PST) Message-ID: Date: Tue, 13 Jan 2009 21:40:41 +0100 From: "Harald Servat" To: "Oleksandr Tymoshenko" In-Reply-To: <496CEFBE.8030007@bluezbox.com> MIME-Version: 1.0 References: <496CEFBE.8030007@bluezbox.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: lenovo t400 does not start 7.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 20:40:43 -0000 On Tue, Jan 13, 2009 at 8:47 PM, Oleksandr Tymoshenko wrote: > Harald Servat wrote: > >> Hello, >> >> I downloaded FreeBSD 7.1 (DVD iso image) for amd64 architecture (with >> correct SHA256 checksum), but I'm unable to start the system (Lenovo >> T400). >> >> The boot process starts fine, the BTX messages appear, the 7-option menu >> also appears, but when I hit enter (or when I choose start without ACPI or >> start in safe mode) the \ symbols starts spinning for a while and then >> freezes. >> >> I also tried with the 7.1-amd64-CD1, 7.1-i386-CD1 and a snapshot of >> 8.0-CURRENT dated from December. And the result is the same for all of >> them. >> >> Does anyone have any idea on what can be happening? Or at least, how can >> I >> gather more information about this issue? >> > Not sure about install CDs but I tried all these systems on my t400. > I installed 7.0 then upgraded it to 7.1 and when it turned out that > atheros is not 100% supported by it I upgraded to CURRENT. (I used cvsup > for upgrades). What is your HW configuration? > > Ok, thanks... I'll give a try to 7.0, and let's see if it works. -- _________________________________________________________________ Empty your memory, with a free()... like a pointer! If you cast a pointer to an integer, it becomes an integer, if you cast a pointer to a struct, it becomes a struct. The pointer can crash..., and can overflow. Be a pointer my friend... From owner-freebsd-stable@FreeBSD.ORG Tue Jan 13 20:42:57 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CAB3510656C1 for ; Tue, 13 Jan 2009 20:42:56 +0000 (UTC) (envelope-from redcrash@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.169]) by mx1.freebsd.org (Postfix) with ESMTP id D2DDE8FC0C for ; Tue, 13 Jan 2009 20:42:55 +0000 (UTC) (envelope-from redcrash@gmail.com) Received: by wf-out-1314.google.com with SMTP id 24so186273wfg.7 for ; Tue, 13 Jan 2009 12:42:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=Bd+bd88u9ziTVjhW+o7Auw3jxODstmpI8LJuyJnq8rE=; b=Ucgqhun2Pb0mOkbq32blbepGEwmntMXCcKQU6wNcRAktUeVvniqfpJMsrwrBVCctEQ 99CMk+kpKTkAg+kCXTUgvG0kqoFeCun1XgHdk9tCl6CSjn0x0y+Re2ORc3/nTT4YrOxq 1St8kr6u3cyWS0SS7nYP/5adkB9d1DwXoK6W4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=MT3ASofPxU/F26qIy8lsMnEVq1FCEkXMdnTc19zmY8/m2cBRLopsD27+nKgMzDND3/ PGtjwJgoj8vOxTXo9LZ/sQSKGXwanhhP4bL2tOokB0VYAnWMDStOGobIU/BI1EkYoHTb k7CeCpcs1NWueOXAA/2rxV1o7UwsjogRcYOio= Received: by 10.142.254.2 with SMTP id b2mr5094428wfi.323.1231879375542; Tue, 13 Jan 2009 12:42:55 -0800 (PST) Received: by 10.142.239.14 with HTTP; Tue, 13 Jan 2009 12:42:55 -0800 (PST) Message-ID: Date: Tue, 13 Jan 2009 21:42:55 +0100 From: "Harald Servat" To: "Ben Kaduk" In-Reply-To: <47d0403c0901131159v1076fc6am45b2ef3b7f6ed934@mail.gmail.com> MIME-Version: 1.0 References: <47d0403c0901131159v1076fc6am45b2ef3b7f6ed934@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: lenovo t400 does not start 7.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 20:42:59 -0000 On Tue, Jan 13, 2009 at 8:59 PM, Ben Kaduk wrote: > On Tue, Jan 13, 2009 at 1:57 PM, Harald Servat wrote: > > Hello, > > > > I downloaded FreeBSD 7.1 (DVD iso image) for amd64 architecture (with > > correct SHA256 checksum), but I'm unable to start the system (Lenovo > T400). > > > > The boot process starts fine, the BTX messages appear, the 7-option menu > > also appears, but when I hit enter (or when I choose start without ACPI > or > > start in safe mode) the \ symbols starts spinning for a while and then > > freezes. > > Have you tried an ISO for FreeBSD-CURRENT? > > I also have a T400, and definitely had FreeBSD running on it for a while, > but I don't remember if it was 7 or current. > > -Ben Kaduk > I tried 8.0-CURRENT snapshot from December with no luck. I'll give 7.0 a try (Oleksandr also suggested the same). Thanks! -- _________________________________________________________________ Empty your memory, with a free()... like a pointer! If you cast a pointer to an integer, it becomes an integer, if you cast a pointer to a struct, it becomes a struct. The pointer can crash..., and can overflow. Be a pointer my friend... From owner-freebsd-stable@FreeBSD.ORG Tue Jan 13 22:04:16 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 10655106566B for ; Tue, 13 Jan 2009 22:04:16 +0000 (UTC) (envelope-from redcrash@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.169]) by mx1.freebsd.org (Postfix) with ESMTP id D313A8FC08 for ; Tue, 13 Jan 2009 22:04:15 +0000 (UTC) (envelope-from redcrash@gmail.com) Received: by wf-out-1314.google.com with SMTP id 24so220552wfg.7 for ; Tue, 13 Jan 2009 14:04:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=Jd5RwwWOdfzD6N9aEeIKjYr0MaA15mRJNgBPvWhOq9U=; b=VtgeN6+NNdZ4l/j0ZiSDwVmG/Hdzh6gM5OG4kpny2Z9gUnr/3rfc8EPlW8nqk5N5wf TsTf2ghFJFTq2ugk62A3o063bBqkAmkoU4jlT3vZbKbJkffvvDpYsc8FPpgzwPb0QooF OwNHFW+kWIH7RNQMNaLt3cMr2vyEJc1240By4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=w79usi88xU7f4ndJwV3Aox87kVAuWHwL2JW1nGkxLOCa75TUhf2mtypuXOwLFrirV1 Lh0nLDE4NcfLzbIHX07irgj655YpJHql/hUm1kqJVh8SEzf7/wTceZmZhsg4/GNWdt+9 80+neMBfBPH4dxzFs2wJWMXf7GdqWTPj+qSSA= Received: by 10.142.82.13 with SMTP id f13mr13043423wfb.301.1231884255264; Tue, 13 Jan 2009 14:04:15 -0800 (PST) Received: by 10.142.239.14 with HTTP; Tue, 13 Jan 2009 14:04:15 -0800 (PST) Message-ID: Date: Tue, 13 Jan 2009 23:04:15 +0100 From: "Harald Servat" To: "Oleksandr Tymoshenko" In-Reply-To: MIME-Version: 1.0 References: <496CEFBE.8030007@bluezbox.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: lenovo t400 does not start 7.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 22:04:16 -0000 On Tue, Jan 13, 2009 at 9:40 PM, Harald Servat wrote: > > > On Tue, Jan 13, 2009 at 8:47 PM, Oleksandr Tymoshenko wrote: > >> Harald Servat wrote: >> >>> Hello, >>> >>> I downloaded FreeBSD 7.1 (DVD iso image) for amd64 architecture (with >>> correct SHA256 checksum), but I'm unable to start the system (Lenovo >>> T400). >>> >>> The boot process starts fine, the BTX messages appear, the 7-option menu >>> also appears, but when I hit enter (or when I choose start without ACPI >>> or >>> start in safe mode) the \ symbols starts spinning for a while and then >>> freezes. >>> >>> I also tried with the 7.1-amd64-CD1, 7.1-i386-CD1 and a snapshot of >>> 8.0-CURRENT dated from December. And the result is the same for all of >>> them. >>> >>> Does anyone have any idea on what can be happening? Or at least, how can >>> I >>> gather more information about this issue? >>> >> Not sure about install CDs but I tried all these systems on my >> t400. >> I installed 7.0 then upgraded it to 7.1 and when it turned out that >> atheros is not 100% supported by it I upgraded to CURRENT. (I used cvsup >> for upgrades). What is your HW configuration? >> >> > Ok, thanks... I'll give a try to 7.0, and let's see if it works. > > Uhm... FreeBSD 7.0 i386 CD1 behaves in the same manner. It frozes when spinning the backslash symbol. The BIOS reports 4GB of RAM and SATA disk configured in AHCI mode. Should I look for something unusual? and how? Thank you. From owner-freebsd-stable@FreeBSD.ORG Tue Jan 13 23:06:13 2009 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 4709010658A4; Tue, 13 Jan 2009 23:06:13 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-stable@FreeBSD.org Date: Tue, 13 Jan 2009 18:05:54 -0500 User-Agent: KMail/1.6.2 References: <8dfae1c10901070639x67945324jeeecfcac647d7976@mail.gmail.com> <20090113050223.GH46346@cdnetworks.co.kr> <496CB2E7.2060902@andric.com> In-Reply-To: <496CB2E7.2060902@andric.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200901131806.02868.jkim@FreeBSD.org> Cc: pyunyh@gmail.com, Dimitry Andric , eugene@donpac.ru Subject: Re: FreeBSD 7.1 Breaks re and rl Network Interface Drivers X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 23:06:16 -0000 On Tuesday 13 January 2009 10:27 am, Dimitry Andric wrote: > Reverting r180519 seems to solve the problem of not being able to > send any packets. It does not solve the other problem, which is > that the interfaces can take a very long time to come up at boot > time, e.g: > > Setting hostuuid: 3ee65237-8025-11dc-9ab5-003018a6f1a8. > Setting hostid: 0xaaedab9a. > Mounting local file systems:. > Setting hostname: tensor.andric.com. > [... pauses for 10 seconds here ...] > re0: link state changed to DOWN > re1: link state changed to DOWN > lo0: flags=8049 metric 0 mtu 16384 > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 > inet 127.0.0.1 netmask 0xff000000 > re0: flags=8843 metric 0 > mtu 1500 > options=389bUCAST,WOL_MCAST,WOL_MAGIC> ether 00:30:18:a6:f1:a8 > inet6 fe80::230:18ff:fea6:f1a8%re0 prefixlen 64 tentative > scopeid 0x1 inet 87.251.56.140 netmask 0xffffffc0 broadcast > 87.251.56.191 media: Ethernet autoselect (none) > status: no carrier > re1: flags=8843 metric 0 > mtu 1500 > options=389bUCAST,WOL_MCAST,WOL_MAGIC> ether 00:30:18:a6:f1:a9 > inet6 fe80::230:18ff:fea6:f1a9%re1 prefixlen 64 tentative > scopeid 0x2 inet 192.168.0.1 netmask 0xffffff00 broadcast > 192.168.0.255 media: Ethernet autoselect (none) > status: no carrier > [...] > > (note also the "no carrier" just after upping those interfaces) [...] Can you try one of the following patches? -CURRENT: http://people.freebsd.org/~jkim/re/re.current.diff -STABLE: http://people.freebsd.org/~jkim/re/re.stable.diff These patches contain all patches suggested by me and yongari and an additional patch, which may (or may not) decrease the initial setup time. Jung-uk Kim From owner-freebsd-stable@FreeBSD.ORG Tue Jan 13 23:57:34 2009 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 CAB681065680 for ; Tue, 13 Jan 2009 23:57:34 +0000 (UTC) (envelope-from vibarus@googlemail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.241]) by mx1.freebsd.org (Postfix) with ESMTP id 3177F8FC18 for ; Tue, 13 Jan 2009 23:57:34 +0000 (UTC) (envelope-from vibarus@googlemail.com) Received: by an-out-0708.google.com with SMTP id c2so155272anc.13 for ; Tue, 13 Jan 2009 15:57:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=GvW5i/cOEdYJumNy1wCSuKFfLAAg1A44GzPrIvv4hRo=; b=OIC0TJ/ejZhRTd/uQcydPA66WlJbRXOPx6hjoo9SRGuYkeW1guaggrKJ04WUjyJ/3I jLMcSLglPXilOoZRR+Z0Qpr3+AhpF1XJ6NSYR01ZUBpSUE1KBGmTHWGebYM10DykzCrI ySbzZPVWoQUMIfRyQ32rqpDw8PGbKtn9tfwqg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=PDuj27ebkNSHaA7AEqaLYWkDjlz+OhXz0wP8W2ixPE7GPqGrZO4nQS0zi6/vbtQiZT qQzI1ELfolqn0dhkoXqNn3di4RSRFEWkicdZw/nMMn4Em0xfnY+n8rkrpxMgHKLWUU8O DIKxaKuZvENu7HvloVnnF2D+p2Gp0Ae8f92Y8= Received: by 10.100.134.10 with SMTP id h10mr17032187and.116.1231889059961; Tue, 13 Jan 2009 15:24:19 -0800 (PST) Received: by 10.100.112.12 with HTTP; Tue, 13 Jan 2009 15:24:19 -0800 (PST) Message-ID: Date: Wed, 14 Jan 2009 00:24:19 +0100 From: "Vincent Barus" To: "Sam Leffler" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <49665E35.1050301@errno.com> Cc: stable@freebsd.org Subject: Re: CFT: ath hal src switchover X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 23:57:35 -0000 On Fri, Jan 9, 2009 at 5:32 AM, Sean C. Farley wrote: > On Thu, 8 Jan 2009, Sam Leffler wrote: > >> I've brought the hal source code back to RELENG_7 but not connected it to >> the build and/or driver. I want folks to test this before I commit those >> changes. To do this you must have an up to date RELENG_7 code base and then >> apply this patch: >> >> http://people.freebsd.org/~sam/ath_hal-releng7.patch > > *snip* > >> Please report any issues to this mailing list. > > No problems for my Netgear WPN511. It works well at home. > > Now, if I just could figure out why the recent Aruba update at work is > preventing me from authenticating with it, I would be happy. This is not > related to the MFC of the code. iPhones and MacOSX 10.4 (but not 10.5) are > also having problems. Windows works. > > Sean > -- > scf@FreeBSD.org > _______________________________________________ > 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" > Hi, today I tried to get a (samsung nc10 ath) nic working. The patch failed to edit this three files: sys/modules/ath_rate_onoe/Makefile sys/modules/ath_rate_sample/Makefile sys/modules/ath_rate_amrr/Makefile I emptied them manually and ran a buildworld/kernel/etc on a clean 7.1 stable but i get a error message while booting: ath0: unable to attach hardware; HAL status 13 After that I csuped the latest stable srcs, applied hal-20081015-sanitized.tgz and run the complete buildprocess again. The same error Message occurs. Is there any trick to get the samsungs ath card running? regards, Vincent Copyright (c) 1992-2009 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.1-STABLE #0: Tue Jan 13 21:21:53 CET 2009 root@:/usr/obj/usr/src/sys/BOOKLI Preloaded elf kernel "/boot/kernel/kernel" at 0xc0a99000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0a99250. Calibrating clock(s) ... i8254 clock: 1193244 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 1595994372 Hz CPU: Intel(R) Atom(TM) CPU N270 @ 1.60GHz (1595.99-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x106c2 Stepping = 2 Features=0xbfe9fbff Features2=0x40c39d> AMD Features2=0x1 Logical CPUs per core: 2 1st-level instruction cache: 32 KB, 8-way set associative, 64 byte line size L2 cache: 512 kbytes, 16-way associative, 64 bytes/line real memory = 1064108032 (1014 MB) Physical memory chunk(s): 0x0000000000001000 - 0x000000000009efff, 647168 bytes (158 pages) 0x0000000000100000 - 0x00000000003fffff, 3145728 bytes (768 pages) 0x0000000000c25000 - 0x000000003e4b0fff, 1032372224 bytes (252044 pages) avail memory = 1031852032 (984 MB) Table 'FACP' at 0x3f6e1bd2 Table 'APIC' at 0x3f6e1cc6 MADT: Found table at 0x3f6e1cc6 MP Configuration Table version 1.4 found at 0xc009fc71 APIC: Using the MADT enumerator. MADT: Found CPU APIC ID 0 ACPI ID 0: enabled SMP: Added CPU 0 (AP) MADT: Found CPU APIC ID 1 ACPI ID 1: enabled SMP: Added CPU 1 (AP) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 bios32: Found BIOS32 Service Directory header at 0xc00f7150 bios32: Entry = 0xfd5f0 (c00fd5f0) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xfd5f0+0x275 pnpbios: Found PnP BIOS data at 0xc00f71f0 pnpbios: Entry = f0000:b8d8 Rev = 1.0 Other BIOS signatures found: APIC: CPU 0 has ACPI ID 0 APIC: CPU 1 has ACPI ID 1 ULE: setup cpu group 0 ULE: setup cpu 0 ULE: adding cpu 0 to group 0: cpus 1 mask 0x1 ULE: setup cpu 1 ULE: adding cpu 1 to group 0: cpus 2 mask 0x3 ACPI: RSDP @ 0x0xf71a0/0x0024 (v 2 PTLTD ) ACPI: XSDT @ 0x0x3f6db94a/0x0084 (v 1 SECCSD LH43STAR 0x06040000 LTP 0x00000000) ACPI: FACP @ 0x0x3f6e1bd2/0x00F4 (v 3 INTEL CALISTGA 0x06040000 ALAN 0x00000001) ACPI: DSDT @ 0x0x3f6dd5f2/0x456C (v 1 INTEL CALISTGA 0x06040000 INTL 0x20050624) ACPI: FACS @ 0x0x3f6e2fc0/0x0040 ACPI: APIC @ 0x0x3f6e1cc6/0x0068 (v 1 INTEL CALISTGA 0x06040000 LOHR 0x0000005A) ACPI: HPET @ 0x0x3f6e1d2e/0x0038 (v 1 INTEL CALISTGA 0x06040000 LOHR 0x0000005A) ACPI: MCFG @ 0x0x3f6e1d66/0x003C (v 1 INTEL CALISTGA 0x06040000 LOHR 0x0000005A) ACPI: TCPA @ 0x0x3f6e1da2/0x0032 (v 1 PTLTD CALISTGA 0x06040000 PTL 0x00000001) ACPI: TMOR @ 0x0x3f6e1dd4/0x0026 (v 1 PTLTD 0x06040000 PTL 0x00000003) ACPI: APIC @ 0x0x3f6e1dfa/0x0068 (v 1 PTLTD APIC 0x06040000 LTP 0x00000000) ACPI: BOOT @ 0x0x3f6e1e62/0x0028 (v 1 PTLTD $SBFTBL$ 0x06040000 LTP 0x00000001) ACPI: SLIC @ 0x0x3f6e1e8a/0x0176 (v 1 SECCSD LH43STAR 0x06040000 LTP 0x00000000) ACPI: SSDT @ 0x0x3f6dcfa3/0x064F (v 1 SataRe SataPri 0x00001000 INTL 0x20050624) ACPI: SSDT @ 0x0x3f6dc907/0x069C (v 1 SataRe SataSec 0x00001000 INTL 0x20050624) ACPI: SSDT @ 0x0x3f6db9ce/0x04F6 (v 2 PmRef CpuPm 0x00003000 INTL 0x20050624) MADT: Found IO APIC ID 1, Interrupt 0 at 0xfec00000 ioapic0: Changing APIC ID to 1 ioapic0: Routing external 8259A's -> intpin 0 MADT: Interrupt override: source 0, irq 2 ioapic0: Routing IRQ 0 -> intpin 2 MADT: Interrupt override: source 9, irq 9 ioapic0: intpin 9 trigger: level lapic0: Routing NMI -> LINT1 lapic0: LINT1 trigger: edge lapic0: LINT1 polarity: high lapic1: Routing NMI -> LINT1 lapic1: LINT1 trigger: edge lapic1: LINT1 polarity: high ioapic0 irqs 0-23 on motherboard cpu0 BSP: ID: 0x00000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010000 ath_rate: version 1.2 wlan_amrr: wlan: <802.11 Link Layer> null: random: io: kbd: new array size 4 kbd1 at kbdmux0 mem: Pentium Pro MTRR support enabled nfslock: pseudo-device ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) npx0: INT 16 interface acpi0: on motherboard ioapic0: routing intpin 9 (ISA IRQ 9) to vector 48 acpi0: [MPSAFE] acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: wakeup code va 0xd7a69000 pa 0x1000 pci_open(1): mode 1 addr port (0x0cf8) is 0x8000fa04 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=27ac8086) pcibios: BIOS version 2.10 AcpiOsDerivePciId: \\_SB_.PCI0.HBUS -> bus 0 dev 0 func 0 AcpiOsDerivePciId: \\_SB_.PCI0.LPCB.LPC0 -> bus 0 dev 31 func 0 acpi_hpet0: vend: 0x8086 rev: 0x1 num: 2 hz: 14318180 opts: legacy_route 64-bit Timecounter "HPET" frequency 14318180 Hz quality 900 ACPI timer: 1/2 1/1 1/1 1/2 1/1 1/2 1/1 1/1 1/2 1/2 -> 10 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 acpi_ec0: port 0x62,0x66 on acpi0 pci_link0: Index IRQ Rtd Ref IRQs Initial Probe 0 11 N 0 1 3 4 5 6 7 10 12 14 15 Validation 0 255 N 0 1 3 4 5 6 7 10 12 14 15 After Disable 0 255 N 0 1 3 4 5 6 7 10 12 14 15 pci_link1: Index IRQ Rtd Ref IRQs Initial Probe 0 10 N 0 1 3 4 5 6 7 11 12 14 15 Validation 0 255 N 0 1 3 4 5 6 7 11 12 14 15 After Disable 0 255 N 0 1 3 4 5 6 7 11 12 14 15 pci_link2: Index IRQ Rtd Ref IRQs Initial Probe 0 5 N 0 1 3 4 5 6 7 10 12 14 15 Validation 0 5 N 0 1 3 4 5 6 7 10 12 14 15 After Disable 0 255 N 0 1 3 4 5 6 7 10 12 14 15 pci_link3: Index IRQ Rtd Ref IRQs Initial Probe 0 5 N 0 1 3 4 5 6 7 11 12 14 15 Validation 0 5 N 0 1 3 4 5 6 7 11 12 14 15 After Disable 0 255 N 0 1 3 4 5 6 7 11 12 14 15 pci_link4: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 1 3 4 5 6 7 10 12 14 15 Validation 0 255 N 0 1 3 4 5 6 7 10 12 14 15 After Disable 0 255 N 0 1 3 4 5 6 7 10 12 14 15 pci_link5: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 1 3 4 5 6 7 11 12 14 15 Validation 0 255 N 0 1 3 4 5 6 7 11 12 14 15 After Disable 0 255 N 0 1 3 4 5 6 7 11 12 14 15 pci_link6: Index IRQ Rtd Ref IRQs Initial Probe 0 5 N 0 1 3 4 5 6 7 10 12 14 15 Validation 0 5 N 0 1 3 4 5 6 7 10 12 14 15 After Disable 0 255 N 0 1 3 4 5 6 7 10 12 14 15 pci_link7: Index IRQ Rtd Ref IRQs Initial Probe 0 5 N 0 1 3 4 5 6 7 11 12 14 15 Validation 0 5 N 0 1 3 4 5 6 7 11 12 14 15 After Disable 0 255 N 0 1 3 4 5 6 7 11 12 14 15 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: domain=0, physical bus=0 found-> vendor=0x8086, dev=0x27ac, revid=0x03 domain=0, bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0106, statreg=0x2090, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x27ae, revid=0x03 domain=0, bus=0, slot=2, func=0 class=03-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x0090, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 2 supports D0 D3 current D0 MSI supports 1 message map[10]: type Memory, range 32, base 0xf0000000, size 19, enabled map[14]: type I/O Port, range 32, base 0x1800, size 3, enabled map[18]: type Prefetchable Memory, range 32, base 0xd0000000, size 28, enabled map[1c]: type Memory, range 32, base 0xf0300000, size 18, enabled pcib0: matched entry for 0.2.INTA pcib0: slot 2 INTA hardwired to IRQ 16 found-> vendor=0x8086, dev=0x27a6, revid=0x03 domain=0, bus=0, slot=2, func=1 class=03-80-00, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x0090, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) powerspec 2 supports D0 D3 current D0 map[10]: type Memory, range 32, base 0xf0080000, size 19, enabled found-> vendor=0x8086, dev=0x27d8, revid=0x02 domain=0, bus=0, slot=27, func=0 class=04-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=5 powerspec 2 supports D0 D3 current D0 MSI supports 1 message, 64 bit map[10]: type Memory, range 64, base 0xf0340000, size 14, enabled pcib0: matched entry for 0.27.INTA pcib0: slot 27 INTA hardwired to IRQ 22 found-> vendor=0x8086, dev=0x27d0, revid=0x02 domain=0, bus=0, slot=28, func=0 class=06-04-00, hdrtype=0x01, mfdev=1 cmdreg=0x0007, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x04 (1000 ns), maxlat=0x00 (0 ns) intpin=a, irq=10 powerspec 2 supports D0 D3 current D0 MSI supports 1 message pcib0: matched entry for 0.28.INTA pcib0: slot 28 INTA hardwired to IRQ 17 found-> vendor=0x8086, dev=0x27d4, revid=0x02 domain=0, bus=0, slot=28, func=2 class=06-04-00, hdrtype=0x01, mfdev=1 cmdreg=0x0007, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x04 (1000 ns), maxlat=0x00 (0 ns) intpin=c, irq=5 powerspec 2 supports D0 D3 current D0 MSI supports 1 message pcib0: matched entry for 0.28.INTC pcib0: slot 28 INTC hardwired to IRQ 18 found-> vendor=0x8086, dev=0x27c8, revid=0x02 domain=0, bus=0, slot=29, func=0 class=0c-03-00, hdrtype=0x00, mfdev=1 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=5 map[20]: type I/O Port, range 32, base 0x1820, size 5, enabled pcib0: matched entry for 0.29.INTA pcib0: slot 29 INTA hardwired to IRQ 23 found-> vendor=0x8086, dev=0x27c9, revid=0x02 domain=0, bus=0, slot=29, func=1 class=0c-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=5 map[20]: type I/O Port, range 32, base 0x1840, size 5, enabled pcib0: matched entry for 0.29.INTB pcib0: slot 29 INTB hardwired to IRQ 19 found-> vendor=0x8086, dev=0x27ca, revid=0x02 domain=0, bus=0, slot=29, func=2 class=0c-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=c, irq=5 map[20]: type I/O Port, range 32, base 0x1860, size 5, enabled pcib0: matched entry for 0.29.INTC pcib0: slot 29 INTC hardwired to IRQ 18 found-> vendor=0x8086, dev=0x27cb, revid=0x02 domain=0, bus=0, slot=29, func=3 class=0c-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=d, irq=11 map[20]: type I/O Port, range 32, base 0x1880, size 5, enabled pcib0: matched entry for 0.29.INTD pcib0: slot 29 INTD hardwired to IRQ 16 found-> vendor=0x8086, dev=0x27cc, revid=0x02 domain=0, bus=0, slot=29, func=7 class=0c-03-20, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x0290, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=5 powerspec 2 supports D0 D3 current D0 map[10]: type Memory, range 32, base 0xf0544000, size 10, enabled pcib0: matched entry for 0.29.INTA pcib0: slot 29 INTA hardwired to IRQ 23 found-> vendor=0x8086, dev=0x2448, revid=0xe2 domain=0, bus=0, slot=30, func=0 class=06-04-01, hdrtype=0x01, mfdev=0 cmdreg=0x0007, statreg=0x0010, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x04 (1000 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x27b9, revid=0x02 domain=0, bus=0, slot=31, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x0210, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x27c4, revid=0x02 domain=0, bus=0, slot=31, func=2 class=01-01-80, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x02b8, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=255 powerspec 2 supports D0 D3 current D0 map[20]: type I/O Port, range 32, base 0x1810, size 4, enabled found-> vendor=0x8086, dev=0x27da, revid=0x02 domain=0, bus=0, slot=31, func=3 class=0c-05-00, hdrtype=0x00, mfdev=0 cmdreg=0x0001, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=5 map[20]: type I/O Port, range 32, base 0x18a0, size 5, enabled pcib0: matched entry for 0.31.INTB pcib0: slot 31 INTB hardwired to IRQ 19 vgapci0: port 0x1800-0x1807 mem 0xf0000000-0xf007ffff,0xd0000000-0xdfffffff,0xf0300000-0xf033ffff irq 16 at device 2.0 on pci0 agp0: on vgapci0 vgapci0: Reserved 0x10000000 bytes for rid 0x18 type 3 at 0xd0000000 vgapci0: Reserved 0x80000 bytes for rid 0x10 type 3 at 0xf0000000 vgapci0: Reserved 0x40000 bytes for rid 0x1c type 3 at 0xf0300000 agp0: detected 7932k stolen memory agp0: aperture size is 256M vgapci1: mem 0xf0080000-0xf00fffff at device 2.1 on pci0 pci0: at device 27.0 (no driver attached) pcib1: irq 17 at device 28.0 on pci0 pcib1: domain 0 pcib1: secondary bus 2 pcib1: subordinate bus 2 pcib1: I/O decode 0xf000-0xfff pcib1: memory decode 0xf0100000-0xf01fffff pcib1: no prefetched decode pci2: on pcib1 pci2: domain=0, physical bus=2 found-> vendor=0x168c, dev=0x001c, revid=0x01 domain=0, bus=2, slot=0, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 2 supports D0 D3 current D0 MSI supports 1 message MSI-X supports 1 message in map 0x10 map[10]: type Memory, range 64, base 0xf0100000, size 16, enabled pcib1: requested memory range 0xf0100000-0xf010ffff: good pcib1: matched entry for 2.0.INTA pcib1: slot 0 INTA hardwired to IRQ 16 ath0: mem 0xf0100000-0xf010ffff irq 16 at device 0.0 on pci2 ath0: Reserved 0x10000 bytes for rid 0x10 type 3 at 0xf0100000 ioapic0: routing intpin 16 (PCI IRQ 16) to vector 49 ath0: [MPSAFE] ath0: [ITHREAD] ath0: unable to attach hardware; HAL status 13 device_attach: ath0 attach returned 6 pcib2: irq 18 at device 28.2 on pci0 pcib2: domain 0 pcib2: secondary bus 3 pcib2: subordinate bus 3 pcib2: I/O decode 0x2000-0x2fff pcib2: memory decode 0xf0200000-0xf02fffff pcib2: no prefetched decode pci3: on pcib2 pci3: domain=0, physical bus=3 found-> vendor=0x11ab, dev=0x4354, revid=0x13 domain=0, bus=3, slot=0, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=5 powerspec 3 supports D0 D1 D2 D3 current D0 MSI supports 1 message, 64 bit map[10]: type Memory, range 64, base 0xf0200000, size 14, enabled pcib2: requested memory range 0xf0200000-0xf0203fff: good map[18]: type I/O Port, range 32, base 0x2000, size 8, enabled pcib2: requested I/O range 0x2000-0x20ff: in range pcib2: matched entry for 3.0.INTA pcib2: slot 0 INTA hardwired to IRQ 18 pci3: at device 0.0 (no driver attached) uhci0: port 0x1820-0x183f irq 23 at device 29.0 on pci0 uhci0: Reserved 0x20 bytes for rid 0x20 type 4 at 0x1820 ioapic0: routing intpin 23 (PCI IRQ 23) to vector 49 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: on uhci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: port 0x1840-0x185f irq 19 at device 29.1 on pci0 uhci1: Reserved 0x20 bytes for rid 0x20 type 4 at 0x1840 ioapic0: routing intpin 19 (PCI IRQ 19) to vector 50 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: on uhci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0x1860-0x187f irq 18 at device 29.2 on pci0 uhci2: Reserved 0x20 bytes for rid 0x20 type 4 at 0x1860 ioapic0: routing intpin 18 (PCI IRQ 18) to vector 51 uhci2: [GIANT-LOCKED] uhci2: [ITHREAD] usb2: on uhci2 usb2: USB revision 1.0 uhub2: on usb2 uhub2: 2 ports with 2 removable, self powered uhci3: port 0x1880-0x189f irq 16 at device 29.3 on pci0 uhci3: Reserved 0x20 bytes for rid 0x20 type 4 at 0x1880 ioapic0: routing intpin 16 (PCI IRQ 16) to vector 52 uhci3: [GIANT-LOCKED] uhci3: [ITHREAD] usb3: on uhci3 usb3: USB revision 1.0 uhub3: on usb3 uhub3: 2 ports with 2 removable, self powered ehci0: mem 0xf0544000-0xf05443ff irq 23 at device 29.7 on pci0 ehci0: Reserved 0x400 bytes for rid 0x10 type 3 at 0xf0544000 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: on ehci0 usb4: USB revision 2.0 uhub4: on usb4 uhub4: 8 ports with 8 removable, self powered umass0: on uhub4 umass0:0:0:-1: Attached to scbus0 ugen0: on uhub4 pcib3: at device 30.0 on pci0 pcib3: domain 0 pcib3: secondary bus 4 pcib3: subordinate bus 4 pcib3: I/O decode 0xf000-0xfff pcib3: no prefetched decode pcib3: Subtractively decoded bridge. pci4: on pcib3 pci4: domain=0, physical bus=4 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1810-0x181f at device 31.2 on pci0 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0x1810 ata0: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 atapci0: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 ata0: reset tp1 mask=03 ostat0=50 ostat1=00 ata0: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata0: stat1=0x00 err=0x01 lsb=0x00 msb=0x00 ata0: reset tp2 stat0=50 stat1=00 devices=0x1 ioapic0: routing intpin 14 (ISA IRQ 14) to vector 53 ata0: [MPSAFE] ata0: [ITHREAD] ata1: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170 atapci0: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376 ata1: reset tp1 mask=00 ostat0=ff ostat1=ff ioapic0: routing intpin 15 (ISA IRQ 15) to vector 54 ata1: [MPSAFE] ata1: [ITHREAD] pci0: at device 31.3 (no driver attached) acpi_acad0: on acpi0 acpi_lid0: on acpi0 acpi_button0: on acpi0 acpi_button1: on acpi0 acpi_tz0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbd0 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 ioapic0: routing intpin 1 (ISA IRQ 1) to vector 55 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: unable to allocate IRQ psmcpnp0: irq 12 on acpi0 psm0: current command byte:0047 psm0: irq 12 on atkbdc0 ioapic0: routing intpin 12 (ISA IRQ 12) to vector 56 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model Generic PS/2 mouse, device ID 0-00, 2 buttons psm0: config:00000000, flags:00000008, packet size:3 psm0: syncmask:c0, syncbits:00 battery0: on acpi0 cpu0: on acpi0 ACPI: SSDT @ 0x0x3f6dc5ee/0x0245 (v 2 PmRef Cpu0Ist 0x00003000 INTL 0x20050624) ACPI: SSDT @ 0x0x3f6dbec4/0x06A5 (v 2 PmRef Cpu0Cst 0x00003001 INTL 0x20050624) est0: on cpu0 p4tcc0: on cpu0 cpu1: on acpi0 ACPI: SSDT @ 0x0x3f6dc833/0x00D4 (v 2 PmRef Cpu1Ist 0x00003000 INTL 0x20050624) ACPI: SSDT @ 0x0x3f6dc569/0x0085 (v 2 PmRef Cpu1Cst 0x00003000 INTL 0x20050624) est1: on cpu1 p4tcc1: on cpu1 ata: ata0 already exists; skipping it ata: ata1 already exists; skipping it atkbdc: atkbdc0 already exists; skipping it sc: sc0 already exists; skipping it vga: vga0 already exists; skipping it pnp_identify: Trying Read_Port at 203 pnp_identify: Trying Read_Port at 243 pnp_identify: Trying Read_Port at 283 pnp_identify: Trying Read_Port at 2c3 pnp_identify: Trying Read_Port at 303 pnp_identify: Trying Read_Port at 343 pnp_identify: Trying Read_Port at 383 pnp_identify: Trying Read_Port at 3c3 PNP Identify complete isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices pmtimer0 on isa0 orm0: at iomem 0xdf000-0xdffff,0xe0000-0xe17ff pnpid ORM0000 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sc0: fb0, kbd1, terminal emulator: sc (syscons terminal) vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 adv0: not probed (disabled) aha0: not probed (disabled) aic0: not probed (disabled) bt0: not probed (disabled) cs0: not probed (disabled) ed0: not probed (disabled) fdc0 failed to probe at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fe0: not probed (disabled) ie0: not probed (disabled) le0: not probed (disabled) ppc0 failed to probe at irq 7 on isa0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: irq maps: 0xe21 0xe21 0xe21 0xe21 sio0: probe failed test(s): 0 1 2 4 6 7 9 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: irq maps: 0xe21 0xe21 0xe21 0xe21 sio0: probe failed test(s): 0 1 2 4 6 7 9 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 or not responding ioapic0: routing intpin 4 (ISA IRQ 4) to vector 57 sio0: [FILTER] sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1: irq maps: 0xe21 0xe21 0xe21 0xe21 sio1: probe failed test(s): 0 1 2 4 6 7 9 sio1 failed to probe at port 0x2f8-0x2ff irq 3 on isa0 sio2: not probed (disabled) sio3: not probed (disabled) sn0: not probed (disabled) vt0: not probed (disabled) isa_probe_children: probing PnP devices Device configuration finished. procfs registered lapic: Divisor 2, Frequency 66499787 hz Timecounter "TSC" frequency 1595994372 Hz quality -100 Timecounters tick every 1.000 msec lo0: bpf attached acpi_acad0: acline initialization start battery0: acpi_acad0: On Line acpi_acad0: acline initialization done, tried 1 times battery initialization start ata0-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire battery0: battery initialization done, tried 1 times ad0: 152627MB at ata0-master SATA150 ad0: 312581808 sectors [310101C/16H/63S] 16 sectors/interrupt 1 depth queue GEOM: new disk ad0 GEOM_LABEL: Label for provider ad0s1 is ntfs/RECOVERY. GEOM: new disk da0 pass0 at umass-sim0 bus 0 target 0 lun 0 pass0: Removable Direct Access SCSI-0 device pass0: 40.000MB/s transfers da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 1967MB (4029440 512 byte sectors: 255H 63S/T 250C) SMP: AP CPU #1 Launched! cpu1 AP: ID: 0x01000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000200ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010000 ioapic0: Assigning ISA IRQ 1 to local APIC 0 ioapic0: Assigning ISA IRQ 4 to local APIC 0 ioapic0: Assigning ISA IRQ 9 to local APIC 0 ioapic0: Assigning ISA IRQ 12 to local APIC 0 ioapic0: Assigning ISA IRQ 14 to local APIC 0 ioapic0: Assigning ISA IRQ 15 to local APIC 0 ioapic0: Assigning PCI IRQ 16 to local APIC 0 ioapic0: Assigning PCI IRQ 18 to local APIC 0 ioapic0: Assigning PCI IRQ 19 to local APIC 0 ioapic0: Assigning PCI IRQ 23 to local APIC 0 Trying to mount root from ufs:/dev/ad0s3a start_init: trying /sbin/init Linux ELF exec handler installed hostb0@pci0:0:0:0: class=0x060000 card=0xca00144d chip=0x27ac8086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' class = bridge subclass = HOST-PCI cap 09[e0] = vendor (length 9) Intel cap 7 version 1 vgapci0@pci0:0:2:0: class=0x030000 card=0xca00144d chip=0x27ae8086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' class = display subclass = VGA cap 05[90] = MSI supports 1 message cap 01[d0] = powerspec 2 supports D0 D3 current D0 vgapci1@pci0:0:2:1: class=0x038000 card=0xca00144d chip=0x27a68086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = 'Mobile 945GM/GU Express Integrated Graphics Controller' class = display cap 01[d0] = powerspec 2 supports D0 D3 current D0 none0@pci0:0:27:0: class=0x040300 card=0xca00144d chip=0x27d88086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801G (ICH7 Family) High Definition Audio' class = multimedia subclass = HDA cap 01[50] = powerspec 2 supports D0 D3 current D0 cap 05[60] = MSI supports 1 message, 64 bit cap 10[70] = PCI-Express 1 type 0 pcib1@pci0:0:28:0: class=0x060400 card=0xca00144d chip=0x27d08086 rev=0x02 hdr=0x01 vendor = 'Intel Corporation' device = '82801G (ICH7 Family) PCIe Root Port' class = bridge subclass = PCI-PCI cap 10[40] = PCI-Express 1 root port cap 05[80] = MSI supports 1 message cap 0d[90] = PCI Bridge card=0xca00144d cap 01[a0] = powerspec 2 supports D0 D3 current D0 pcib2@pci0:0:28:2: class=0x060400 card=0xca00144d chip=0x27d48086 rev=0x02 hdr=0x01 vendor = 'Intel Corporation' device = '82801G (ICH7 Family) PCIe Root Port' class = bridge subclass = PCI-PCI cap 10[40] = PCI-Express 1 root port cap 05[80] = MSI supports 1 message cap 0d[90] = PCI Bridge card=0xca00144d cap 01[a0] = powerspec 2 supports D0 D3 current D0 uhci0@pci0:0:29:0: class=0x0c0300 card=0xca00144d chip=0x27c88086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801G (ICH7 Family) USB Universal Host Controller' class = serial bus subclass = USB uhci1@pci0:0:29:1: class=0x0c0300 card=0xca00144d chip=0x27c98086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801G (ICH7 Family) USB Universal Host Controller' class = serial bus subclass = USB uhci2@pci0:0:29:2: class=0x0c0300 card=0xca00144d chip=0x27ca8086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801G (ICH7 Family) USB Universal Host Controller' class = serial bus subclass = USB uhci3@pci0:0:29:3: class=0x0c0300 card=0xca00144d chip=0x27cb8086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801G (ICH7 Family) USB Universal Host Controller' class = serial bus subclass = USB ehci0@pci0:0:29:7: class=0x0c0320 card=0xca00144d chip=0x27cc8086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801G (ICH7 Family) USB 2.0 Enhanced Host Controller' class = serial bus subclass = USB cap 01[50] = powerspec 2 supports D0 D3 current D0 cap 0a[58] = EHCI Debug Port at offset 0xa0 in map 0x14 pcib3@pci0:0:30:0: class=0x060401 card=0xca00144d chip=0x24488086 rev=0xe2 hdr=0x01 vendor = 'Intel Corporation' device = '82801BAM/CAM/DBM (ICH2-M/3-M/4-M) Hub Interface to PCI Bridge' class = bridge subclass = PCI-PCI cap 0d[50] = PCI Bridge card=0xca00144d isab0@pci0:0:31:0: class=0x060100 card=0xca00144d chip=0x27b98086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801GBM (ICH7-M) LPC Interface Controller' class = bridge subclass = PCI-ISA cap 09[e0] = vendor (length 12) Intel cap 1 version 0 features: Quick Resume, SATA RAID-5, Mobile, 6 PCI-e x1 slots, SATA RAID-0/1/10 atapci0@pci0:0:31:2: class=0x010180 card=0xca00144d chip=0x27c48086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801GBM/GHM (ICH7-M Family) Serial ATA Storage Controller' class = mass storage subclass = ATA cap 01[70] = powerspec 2 supports D0 D3 current D0 none1@pci0:0:31:3: class=0x0c0500 card=0xca00144d chip=0x27da8086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801G (ICH7 Family) SMBus Controller' class = serial bus subclass = SMBus ath0@pci0:2:0:0: class=0x020000 card=0x7131144f chip=0x001c168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = 'AR5006 family 802.11abg Wireless NIC' class = network subclass = ethernet cap 01[40] = powerspec 2 supports D0 D3 current D0 cap 05[50] = MSI supports 1 message cap 10[60] = PCI-Express 1 legacy endpoint cap 11[90] = MSI-X supports 1 message in map 0x10 none2@pci0:3:0:0: class=0x020000 card=0xca00144d chip=0x435411ab rev=0x13 hdr=0x00 vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)' class = network subclass = ethernet cap 01[48] = powerspec 3 supports D0 D1 D2 D3 current D0 cap 05[5c] = MSI supports 1 message, 64 bit cap 10[c0] = PCI-Express 2 legacy endpoint -- ~ vb From owner-freebsd-stable@FreeBSD.ORG Wed Jan 14 00:32:37 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 32BAB106564A for ; Wed, 14 Jan 2009 00:32:37 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.229]) by mx1.freebsd.org (Postfix) with ESMTP id E97CC8FC0A for ; Wed, 14 Jan 2009 00:32:36 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so272044rvf.43 for ; Tue, 13 Jan 2009 16:32:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=zJAtnG6I8gi0mlXkVjLRwWfBe1OS1B8i81s0bxymWJo=; b=R989kXQRflOE1srdU+gODQUn07vysbM3F9hsuf4wj4PVPSwH9s2L7zB8GPEEQWIst4 Uyso8G/mfX0G47letzWka8dGM7jU83zhwuqQt5uUzx5AzeXXDxhlBxcihFtOr3XesRG5 CHRfRwgHHXtt52JS2n+152iQHNNFIQlgN5wCc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=UOL3tb5qRpuAP7pG6S/gC9BmbivBM7kBx5KPt1YOwsxv69wOtg2v40CS71Rl1at14I 46YsZZP/NJeWf8bYCkYjrXbKS+YLhZTO7LMY/QLRAY1FSm/Hc7RvSf5iRKB1tpQz+1wG 3fia2o8d2EU6N8UIsRUtIgHdXrVveJv67bLiU= Received: by 10.141.84.5 with SMTP id m5mr2646208rvl.175.1231893156651; Tue, 13 Jan 2009 16:32:36 -0800 (PST) Received: from michelle.cdnetworks.co.kr ([211.53.35.84]) by mx.google.com with ESMTPS id g31sm16574006rvb.4.2009.01.13.16.32.34 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 13 Jan 2009 16:32:35 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.14.3/8.14.3) with ESMTP id n0E0WUla055520 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 14 Jan 2009 09:32:30 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.14.3/8.14.3/Submit) id n0E0WT70055519; Wed, 14 Jan 2009 09:32:29 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Wed, 14 Jan 2009 09:32:28 +0900 From: Pyun YongHyeon To: FreeBSD Message-ID: <20090114003228.GA55351@cdnetworks.co.kr> References: <8dfae1c10901070639x67945324jeeecfcac647d7976@mail.gmail.com> <8dfae1c10901071550s69d99802p31ca7c775f3d6823@mail.gmail.com> <88527079.20090111192206@donpac.ru> <20090112011146.GC46346@cdnetworks.co.kr> <496BBFF6.7010300@optiksecurite.com> <20090113004018.GG46346@cdnetworks.co.kr> <496CB0A2.2020103@optiksecurite.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <496CB0A2.2020103@optiksecurite.com> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 7.1 Breaks re and rl Network Interface Drivers X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2009 00:32:37 -0000 On Tue, Jan 13, 2009 at 10:17:54AM -0500, FreeBSD wrote: > Pyun YongHyeon a ?crit : > >On Mon, Jan 12, 2009 at 05:11:02PM -0500, FreeBSD wrote: > > > Pyun YongHyeon a ?crit : > > > >On Sun, Jan 11, 2009 at 07:22:06PM +0300, Eugene Gladchenko wrote: > > > > > Walter, > > > > > > > > > > Thursday, January 8, 2009, 2:50:40 AM, you wrote: > > > > > > > > > > WV> Booting kernel.old, which is 7.0-RELEASE-p7 completely > > alleviates > > all > > > > > WV> problems. I believe this roundly confirms that this is a bug > > in the > > > > > WV> 7.1-RELEASE re kernel drivers. > > > > > > > > > > Does kern/130011 look similar? > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=130011 > > > > > > > >Do you have RTL8168C controller? If not, it's not related with > > > >Walter's issue as 7.0-RELEASE didn't have a support for RTL8168C. > > > > > > > > > > > > > > The re driver was really broken in 7.1-RC2 and the fix didn't get > > to > > 7.1-RELEASE. > > > > > > > >If you have re(4) issues, please provide more details such as > > > >dmesg output, way to reproduce the issue etc. > > > > > > > > > > Hi, > > > > > > I have the exact same card and the exact same problem as the PR you > > > mentionned. > > > > > > re0@pci0:3:0:0: class=0x020000 card=0x02831028 chip=0x816810ec rev=0x02 > > > hdr=0x00 > > > vendor = 'Realtek Semiconductor' > > > device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' > > > class = network > > > subclass = ethernet > > > > > > > > > re0: > > Gigabit Ethernet> port 0xd800-0xd8ff mem > > > 0xfeaff000-0xfeafffff,0xfdff0000-0xfdffffff irq 18 at device 0.0 on pci3 > > > re0: Chip rev. 0x3c000000 > > > re0: MAC rev. 0x00400000 > > > re0: PHY write failed > > > re0: PHY write failed > > > re0: MII without any phy! > > > device_attach: re0 attach returned 6 > > > > > > I tried to compile a new kernel with the latest version of the 3 files > > > listed in the PR: > > > src/sys/dev/re/if_re.c,v 1.147 2008/12/22 00:46:22 yongari > > > src/sys/pci/if_rl.c,v 1.170.2.10 2009/01/12 04:10:40 yongari > > > src/sys/pci/if_rlreg.h,v 1.67.2.16 2009/01/12 03:48:25 yongari > > > > > > >You need lastest if_rl.c and if_rlreg.h as well as if_re.c. > > > > That's exactly what I tried. Look at the 3 revision of the specified You've used if_rlreg.h in stable/7. > files. I even tried with a if_rl.c from the 22/12/08 but got the same > problem. > Use if_re.c, if_rl.h and if_rl.c in HEAD. Not all changes were MFCed. -- Regards, Pyun YongHyeon From owner-freebsd-stable@FreeBSD.ORG Wed Jan 14 00:41:40 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 798D51065670 for ; Wed, 14 Jan 2009 00:41:40 +0000 (UTC) (envelope-from amarat@ksu.ru) Received: from mx.kzn.ru (mx.kzn.ru [194.85.243.39]) by mx1.freebsd.org (Postfix) with ESMTP id 3D9368FC12 for ; Wed, 14 Jan 2009 00:41:38 +0000 (UTC) (envelope-from amarat@ksu.ru) X-IronPort-AV: E=Sophos;i="4.37,261,1231102800"; d="boot'?scan'208";a="1133706" Received: from mail.ksu.ru (HELO ruby.ksu.ru) ([193.232.252.56]) by iout.kzn.ru with ESMTP; 14 Jan 2009 03:31:33 +0300 X-Pass-Through: Kazan State University Network Received: from zealot.ksu.ru ([194.85.245.161]) by ksu.ru (8.13.4/8.13.4) with ESMTP id n0E0SsOL018169 for ; Wed, 14 Jan 2009 00:28:54 GMT Received: from zealot.ksu.ru (localhost.lnet [127.0.0.1]) by zealot.ksu.ru (8.14.3/8.14.3) with ESMTP id n0E0VOp3004442 for ; Wed, 14 Jan 2009 03:31:24 +0300 (MSK) (envelope-from amarat@ksu.ru) Message-ID: <496D325C.2020702@ksu.ru> Date: Wed, 14 Jan 2009 03:31:24 +0300 From: "Marat N.Afanasyev" User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.8.1.16) Gecko/20080903 SeaMonkey/1.1.11 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: multipart/mixed; boundary="------------060902040207000504050602" Subject: interrupt storm and usb issue on ati ixp600 based board X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2009 00:41:40 -0000 This is a multi-part message in MIME format. --------------060902040207000504050602 Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit I have two troubles with my freshly upgraded system. There are interrupt storm and usb issues on MSI K9A2 CF motherboard. it made of on amd 790X north-bridge and and SB600 south-bridge. As stated in [1] there is a problem with storms on re or atapci devices, but my experience shows that this storms are not bound to re or ixp600 atapci only. I can say that i have such storms on almost any of my devices. whether it sound-card, ata-device, scsi or network. any device that is used intensively can trigger this storm issue, e.g. playing music via audacious can trigger storm in about random() hours after fresh boot either cold or warm (i tried both built in hda that shares irq with ohci0 and standalone sblive! with its own interrupt), moving large files from one physical drive to another, etc. I've tried to turn off msi and msix setting hw.pci.enable_msix="0" hw.pci.enable_msi="0" in /boot/loader.conf interrupt storm arrived in about 27 hours. and it was on pcm0 (snd_hda) So, can this be hardware or software problem? can it be fixed by some workaround? and finally I've updated to 7.1-S. the same story. temporary workaround for interrupt storm issue is to wait until storm arrive on any device (emu10kx0 in this case, because of its own high interrupt rate) and work pretending to believe that nothing is wrong. second issue is neither 7.0 nor 7.1 refuse to detect in run-time any usb device that plugged into external USB HUB, I have two of them, first is on card-reader, second is in my monitor. devices plugged to these hubs before system boot are detected, but device plugged after boot -- they never appear in system, they silently ignored. so, what should i do? :) [1] http://lists.freebsd.org/pipermail/freebsd-stable/2008-December/047010.html [2] fresh boot vmstat: % vmstat -i interrupt total rate irq1: atkbd0 12524 1 irq9: acpi0 1 0 irq12: psm0 1173440 107 irq14: ata0 143 0 irq16: hdac0 ohci0 541673 49 irq17: ohci1 ohci3 1 0 irq18: ohci2 ohci+ 45 0 irq19: ehci0 259 0 irq21: emu10kx0 1137863753 103762 irq22: atapci0 210431 19 cpu0: timer 21929877 1999 irq256: re0 94789 8 cpu1: timer 21927861 1999 Total 1183754797 107947 [3] % uptime 3:15 up 3:03, 2 users, load averages: 0,60 0,47 0,63 [4] dmesg attached -- SY, Marat --------------060902040207000504050602 Content-Type: text/plain; name="dmesg.boot" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="dmesg.boot" interrupt storm detected on "irq21::irq21: emu10kx0"; throttling interrupt source interrupt storm detected on "irq21::irq21: emu10kx0"; throttling interrupt source interrupt storm detected on "irq21::irq21: emu10kx0"; throttling interrupt source interrupt storm detected on "irq21::irq21: emu10kx0"; throttling interrupt source interrupt storm detected on "irq21::irq21: emu10kx0"; throttling interrupt source interrupt storm detected on "irq21::irq21: emu10kx0"; throttling interrupt source interrupt storm detected on "irq21::irq21: emu10kx0"; throttling interrupt source interrupt storm detected on "irq21::irq21: emu10kx0"; throttling interrupt source info: [drm] wait for fifo failed status : 0x9803C100 0x00050000 interrupt storm detected on "irq21::irq21: emu10kx0"; throttling interrupt source interrupt storm detected on "irq21::irq21: emu10kx0"; throttling interrupt source interrupt storm detected on "irq21::irq21: emu10kx0"; throttling interrupt source interrupt storm detected on "irq21::irq21: emu10kx0"; throttling interrupt source info: [drm] Num pipes: 1 Waiting (max 60 seconds) for system process `vnlru' to stop...done Waiting (max 60 seconds) for system process `bufdaemon' to stop...done Waiting (max 60 seconds) for system process `syncer' to stop... Syncing disks, vnodes remaining...6 3 6 6 0 1 1 0 0 0 done All buffers synced. Uptime: 3d22h21m34s Copyright (c) 1992-2009 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.1-STABLE #0: Tue Jan 13 23:43:59 MSK 2009 root@zealot.ksu.ru:/usr/obj/usr/src/sys/ZEALOT Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) Dual Core Processor 4850e (2500.19-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x60fb2 Stepping = 2 Features=0x178bfbff Features2=0x2001 AMD Features=0xea500800 AMD Features2=0x11f Cores per package: 2 usable memory = 4285845504 (4087 MB) avail memory = 4124442624 (3933 MB) ACPI APIC Table: <061208 APIC1106> FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0 irqs 0-23 on motherboard netsmb_dev: loaded acpi0: <061208 RSDT1106> on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of ffb80000, 80000 (3) failed acpi0: reservation of fff00000, 100000 (3) failed acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, cff00000 (3) failed ACPI HPET table warning: Sequence is non-zero (2) Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 acpi_hpet0: iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 2.0 on pci0 pci1: on pcib1 vgapci0: port 0xc000-0xc0ff mem 0xd0000000-0xdfffffff,0xfeaf0000-0xfeafffff irq 18 at device 0.0 on pci1 drm0: on vgapci0 vgapci0: child drm0 requested pci_enable_busmaster info: [drm] Initialized radeon 1.29.0 20080613 vgapci1: mem 0xfeae0000-0xfeaeffff at device 0.1 on pci1 pcib2: at device 6.0 on pci0 pci2: on pcib2 re0: port 0xd800-0xd8ff mem 0xfebff000-0xfebfffff irq 18 at device 0.0 on pci2 re0: Using 2 MSI messages re0: Chip rev. 0x38000000 re0: MAC rev. 0x00000000 miibus0: on re0 rgephy0: PHY 1 on miibus0 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto re0: Ethernet address: 00:1d:92:da:0c:b0 re0: [FILTER] re0: [FILTER] atapci0: port 0xb000-0xb007,0xa000-0xa003,0x9000-0x9007,0x8000-0x8003,0x7000-0x700f mem 0xfe9ff800-0xfe9ffbff irq 22 at device 18.0 on pci0 atapci0: [ITHREAD] atapci0: AHCI Version 01.10 controller with 4 ports detected ata2: on atapci0 ata2: [ITHREAD] ata3: on atapci0 ata3: [ITHREAD] ata4: on atapci0 ata4: [ITHREAD] ata5: on atapci0 ata5: [ITHREAD] ohci0: mem 0xfe9fe000-0xfe9fefff irq 16 at device 19.0 on pci0 ohci0: [GIANT-LOCKED] ohci0: [ITHREAD] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered ohci1: mem 0xfe9fd000-0xfe9fdfff irq 17 at device 19.1 on pci0 ohci1: [GIANT-LOCKED] ohci1: [ITHREAD] usb1: OHCI version 1.0, legacy support usb1: SMM does not respond, resetting usb1: on ohci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered ohci2: mem 0xfe9fc000-0xfe9fcfff irq 18 at device 19.2 on pci0 ohci2: [GIANT-LOCKED] ohci2: [ITHREAD] usb2: OHCI version 1.0, legacy support usb2: SMM does not respond, resetting usb2: on ohci2 usb2: USB revision 1.0 uhub2: on usb2 uhub2: 2 ports with 2 removable, self powered ohci3: mem 0xfe9fb000-0xfe9fbfff irq 17 at device 19.3 on pci0 ohci3: [GIANT-LOCKED] ohci3: [ITHREAD] usb3: OHCI version 1.0, legacy support usb3: SMM does not respond, resetting usb3: on ohci3 usb3: USB revision 1.0 uhub3: on usb3 uhub3: 2 ports with 2 removable, self powered ohci4: mem 0xfe9fa000-0xfe9fafff irq 18 at device 19.4 on pci0 ohci4: [GIANT-LOCKED] ohci4: [ITHREAD] usb4: OHCI version 1.0, legacy support usb4: SMM does not respond, resetting usb4: on ohci4 usb4: USB revision 1.0 uhub4: on usb4 uhub4: 2 ports with 2 removable, self powered ehci0: mem 0xfe9ff000-0xfe9ff0ff irq 19 at device 19.5 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb5: EHCI version 1.0 usb5: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4 usb5: on ehci0 usb5: USB revision 2.0 uhub5: on usb5 uhub5: 10 ports with 10 removable, self powered uhub6: on uhub5 uhub6: multiple transaction translators uhub6: 6 ports with 6 removable, self powered ucom0: on uhub6 uhub7: on uhub5 uhub7: single transaction translator uhub7: 4 ports with 4 removable, self powered umass0: on uhub7 pci0: at device 20.0 (no driver attached) atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xff00-0xff0f at device 20.1 on pci0 ata0: on atapci1 ata0: [ITHREAD] pci0: at device 20.2 (no driver attached) isab0: at device 20.3 on pci0 isa0: on isab0 pcib3: at device 20.4 on pci0 pci3: on pcib3 pci3: at device 3.0 (no driver attached) pci3: at device 3.1 (no driver attached) k8temp0: on hostb4 acpi_button0: on acpi0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio0: [FILTER] atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model IntelliMouse Explorer, device ID 4 cpu0: on acpi0 acpi_throttle0: on cpu0 acpi_throttle0: CLK_VAL field overlaps THT_EN bit device_attach: acpi_throttle0 attach returned 6 powernow0: on cpu0 cpu1: on acpi0 powernow1: on cpu1 orm0: at iomem 0xc0000-0xcf7ff 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 uscanner0: on uhub2 ulpt0: on uhub2 ulpt0: using bi-directional mode Timecounters tick every 1.000 msec ipfw2 initialized, divert enabled, nat loadable, rule-based forwarding enabled, default to accept, logging limited to 1000 packets/entry by default acd0: DVDR at ata0-master UDMA66 ad4: 238475MB at ata2-master SATA300 ad6: 476940MB at ata3-master SATA150 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x48 0x00 0x01 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x48 0x00 0x01 SMP: AP CPU #1 Launched! da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present cd0 at ata0 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 66.000MB/s transfers cd0: cd present [2288832 x 2048 byte records] da1 at umass-sim0 bus 0 target 0 lun 1 da1: Removable Direct Access SCSI-0 device da1: 40.000MB/s transfers da1: Attempt to query device size failed: NOT READY, Medium not present da2 at umass-sim0 bus 0 target 0 lun 2 da2: Removable Direct Access SCSI-0 device da2: 40.000MB/s transfers da2: Attempt to query device size failed: NOT READY, Medium not present da3 at umass-sim0 bus 0 target 0 lun 3 da3: Removable Direct Access SCSI-0 device da3: 40.000MB/s transfers da3: Attempt to query device size failed: NOT READY, Medium not present Trying to mount root from ufs:/dev/ad4s1a re0: link state changed to UP vlan1: link state changed to UP vlan3: link state changed to UP vlan4: link state changed to UP vlan11: link state changed to UP --------------060902040207000504050602-- From owner-freebsd-stable@FreeBSD.ORG Wed Jan 14 01:09:29 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1C1C21065677 for ; Wed, 14 Jan 2009 01:09:29 +0000 (UTC) (envelope-from dan@langille.org) Received: from nyi.unixathome.org (nyi.unixathome.org [64.147.113.42]) by mx1.freebsd.org (Postfix) with ESMTP id D55878FC0A for ; Wed, 14 Jan 2009 01:09:28 +0000 (UTC) (envelope-from dan@langille.org) Received: from localhost (localhost [127.0.0.1]) by nyi.unixathome.org (Postfix) with ESMTP id 63F68509BF for ; Wed, 14 Jan 2009 00:53:37 +0000 (GMT) X-Virus-Scanned: amavisd-new at unixathome.org Received: from nyi.unixathome.org ([127.0.0.1]) by localhost (nyi.unixathome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f5uF5yoh-Xzt for ; Wed, 14 Jan 2009 00:53:35 +0000 (GMT) Received: from smtp-auth.unixathome.org (smtp-auth.unixathome.org [10.4.7.7]) (Authenticated sender: hidden) by nyi.unixathome.org (Postfix) with ESMTPSA id 32E2A50990 for ; Wed, 14 Jan 2009 00:53:35 +0000 (GMT) Message-ID: <496D374A.3020704@langille.org> Date: Tue, 13 Jan 2009 19:52:26 -0500 From: Dan Langille Organization: The FreeBSD Diary User-Agent: Thunderbird 2.0.0.19 (X11/20090111) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: interrupt storm X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2009 01:09:29 -0000 Hi, I'm getting this: kernel: interrupt storm detected on "irq22:"; throttling interrupt source on FreeBSD 7.1-STABLE #6: Sat Jan 10 21:45:05 EST 2009 FWIW, I got the same thing on 7.0-stable from back in May (IIRC). Of note, atapci0 and fxp0 are both on irq 22. Ideas? suggestions? Copyright (c) 1992-2009 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.1-STABLE #6: Sat Jan 10 21:45:05 EST 2009 dan@polo.unixathome.org:/usr/obj/usr/src/sys/PHENOM Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Phenom(tm) 9600 Quad-Core Processor (2300.18-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x100f22 Stepping = 2 Features=0x178bfbff Features2=0x802009> AMD Features=0xee500800 AMD Features2=0x7ff,,,Prefetch,,> Cores per package: 4 usable memory = 4281454592 (4083 MB) avail memory = 4119994368 (3929 MB) ACPI APIC Table: <122107 APIC0947> FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: <122107 RSDT0947> on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of fee00000, 1000 (3) failed acpi0: reservation of ffb80000, 80000 (3) failed acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, cff00000 (3) failed ACPI HPET table warning: Sequence is non-zero (2) Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 acpi_hpet0: iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 5.0 on pci0 pci1: on pcib1 re0: port 0xc800-0xc8ff mem 0xf9fff000-0xf9ffffff irq 17 at device 0.0 on pci1 re0: turning off MSI enable bit. re0: Chip rev. 0x38000000 re0: MAC rev. 0x00000000 miibus0: on re0 rgephy0: PHY 1 on miibus0 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto re0: Ethernet address: 00:1d:92:63:8b:28 re0: [FILTER] pcib2: at device 11.0 on pci0 pci2: on pcib2 vgapci0: port 0xd800-0xd87f mem 0xfd000000-0xfdffffff,0xd0000000-0xdfffffff,0xfa000000-0xfbffffff irq 19 at device 0.0 on pci2 atapci0: port 0xb000-0xb007,0xa000-0xa003,0x9000-0x9007,0x8000-0x8003,0x7000-0x700f mem 0xf9eff800-0xf9effbff irq 22 at device 18.0 on pci0 atapci0: [ITHREAD] atapci0: AHCI Version 01.10 controller with 4 ports detected ata2: on atapci0 ata2: [ITHREAD] ata3: on atapci0 ata3: [ITHREAD] ata4: on atapci0 ata4: [ITHREAD] ata5: on atapci0 ata5: [ITHREAD] ohci0: mem 0xf9efe000-0xf9efefff irq 16 at device 19.0 on pci0 ohci0: [GIANT-LOCKED] ohci0: [ITHREAD] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered ohci1: mem 0xf9efd000-0xf9efdfff irq 17 at device 19.1 on pci0 ohci1: [GIANT-LOCKED] ohci1: [ITHREAD] usb1: OHCI version 1.0, legacy support usb1: SMM does not respond, resetting usb1: on ohci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered ohci2: mem 0xf9efc000-0xf9efcfff irq 18 at device 19.2 on pci0 ohci2: [GIANT-LOCKED] ohci2: [ITHREAD] usb2: OHCI version 1.0, legacy support usb2: SMM does not respond, resetting usb2: on ohci2 usb2: USB revision 1.0 uhub2: on usb2 uhub2: 2 ports with 2 removable, self powered ohci3: mem 0xf9efb000-0xf9efbfff irq 17 at device 19.3 on pci0 ohci3: [GIANT-LOCKED] ohci3: [ITHREAD] usb3: OHCI version 1.0, legacy support usb3: SMM does not respond, resetting usb3: on ohci3 usb3: USB revision 1.0 uhub3: on usb3 uhub3: 2 ports with 2 removable, self powered ohci4: mem 0xf9efa000-0xf9efafff irq 18 at device 19.4 on pci0 ohci4: [GIANT-LOCKED] ohci4: [ITHREAD] usb4: OHCI version 1.0, legacy support usb4: SMM does not respond, resetting usb4: on ohci4 usb4: USB revision 1.0 uhub4: on usb4 uhub4: 2 ports with 2 removable, self powered ehci0: mem 0xf9eff000-0xf9eff0ff irq 19 at device 19.5 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb5: EHCI version 1.0 usb5: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4 usb5: on ehci0 usb5: USB revision 2.0 uhub5: on usb5 uhub5: 10 ports with 10 removable, self powered pci0: at device 20.0 (no driver attached) atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xff00-0xff0f at device 20.1 on pci0 ata0: on atapci1 ata0: [ITHREAD] pci0: at device 20.2 (no driver attached) isab0: at device 20.3 on pci0 isa0: on isab0 pcib3: at device 20.4 on pci0 pci3: on pcib3 fwohci0: port 0xe800-0xe87f mem 0xfebff800-0xfebfffff irq 23 at device 0.0 on pci3 fwohci0: [FILTER] fwohci0: OHCI version 1.10 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:dc:10:00:01:53:a0:bc fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 dcons_crom0: on firewire0 dcons_crom0: bus_addr 0x1190000 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:dc:10:53:a0:bc fwe0: Ethernet address: 02:dc:10:53:a0:bc fwip0: on firewire0 fwip0: Firewire address: 00:dc:10:00:01:53:a0:bc @ 0xfffe00000000, S400, maxrec 2048 sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: BUS reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode fxp0: port 0xe400-0xe43f mem 0xfebfe000-0xfebfefff,0xfea00000-0xfeafffff irq 22 at device 2.0 on pci3 miibus1: on fxp0 inphy0: PHY 1 on miibus1 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:04:ac:d3:78:23 fxp0: [ITHREAD] acpi_button0: on acpi0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio0: [FILTER] fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FILTER] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model IntelliMouse, device ID 3 cpu0: on acpi0 acpi_throttle0: on cpu0 acpi_throttle0: CLK_VAL field overlaps THT_EN bit device_attach: acpi_throttle0 attach returned 6 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 ppc0: cannot reserve I/O port range sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) acd0: CDRW at ata0-slave UDMA33 ad4: 476940MB at ata2-master SATA300 ad6: 476940MB at ata3-master SATA300 GEOM_MIRROR: Device mirror/gm0 launched (2/2). acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 cd0 at ata0 bus 0 target 1 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed SMP: AP CPU #3 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #1 Launched! Trying to mount root from ufs:/dev/mirror/gm0s1a From owner-freebsd-stable@FreeBSD.ORG Wed Jan 14 01:19:33 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B489A106564A for ; Wed, 14 Jan 2009 01:19:33 +0000 (UTC) (envelope-from amarat@ksu.ru) Received: from mx.kzn.ru (mx.kzn.ru [194.85.243.39]) by mx1.freebsd.org (Postfix) with ESMTP id 2EA268FC12 for ; Wed, 14 Jan 2009 01:19:32 +0000 (UTC) (envelope-from amarat@ksu.ru) X-IronPort-AV: E=Sophos;i="4.37,261,1231102800"; d="scan'208";a="1134075" Received: from mail.ksu.ru (HELO ruby.ksu.ru) ([193.232.252.56]) by iout.kzn.ru with ESMTP; 14 Jan 2009 04:19:32 +0300 X-Pass-Through: Kazan State University Network Received: from zealot.ksu.ru ([194.85.245.161]) by ksu.ru (8.13.4/8.13.4) with ESMTP id n0E1Gdpf025447 for ; Wed, 14 Jan 2009 01:16:39 GMT Received: from zealot.ksu.ru (localhost.lnet [127.0.0.1]) by zealot.ksu.ru (8.14.3/8.14.3) with ESMTP id n0E1J9LL004799 for ; Wed, 14 Jan 2009 04:19:09 +0300 (MSK) (envelope-from amarat@ksu.ru) Message-ID: <496D3D8D.4040609@ksu.ru> Date: Wed, 14 Jan 2009 04:19:09 +0300 From: "Marat N.Afanasyev" User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.8.1.16) Gecko/20080903 SeaMonkey/1.1.11 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Subject: interrupt storm X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2009 01:19:34 -0000 it seems that you hit the same issue with amd sb600 as me :) -- SY, Marat From owner-freebsd-stable@FreeBSD.ORG Wed Jan 14 01:46:47 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0C3FF106566B for ; Wed, 14 Jan 2009 01:46:47 +0000 (UTC) (envelope-from stef@memberwebs.com) Received: from mx.npubs.com (mx.npubs.com [209.66.100.224]) by mx1.freebsd.org (Postfix) with ESMTP id E89878FC1F for ; Wed, 14 Jan 2009 01:46:46 +0000 (UTC) (envelope-from stef@memberwebs.com) Received: from mx.npubs.com (avhost [209.66.100.194]) by mx.npubs.com (Postfix) with ESMTP id 30E8C8C2D74 for ; Wed, 14 Jan 2009 01:24:21 +0000 (UTC) Received: from northstar-srv2 (unknown [172.27.2.11]) by mx.npubs.com (Postfix) with ESMTP id A59868C2D30 for ; Wed, 14 Jan 2009 01:24:20 +0000 (UTC) From: Stef Walter User-Agent: Thunderbird 2.0.0.19 (X11/20090105) MIME-Version: 1.0 To: freebsd-stable X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Message-Id: <20090114012420.A59868C2D30@mx.npubs.com> X-Virus-Scanned: ClamAV using ClamSMTP Date: Wed, 14 Jan 2009 01:24:21 +0000 (UTC) Subject: Reproducible panic (page fault) in poll on 6.3-RELEASE-p4 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2009 01:46:47 -0000 I have a kernel panic that I can consistently trigger. After a short while (5 to 30 minutes) with a certain connection pattern of UDP openvpn connections the server crashes. I have a crash dump, and stack trace. It seems td->td_selq has been corrupted (see below). The only similar panic I've found is: http://unix.derkeiler.com/Mailing-Lists/FreeBSD/current/2004-02/0867.html Does anyone know of a patch or any other pointers in the direction of solving this problem? Thanks in advance, Stef Walter ------- 8< ------- 8< -------- 6.3-RELEASE-p4 FreeBSD 6.3-RELEASE-p4 #0: Thu Sep 25 20:16:32 UTC 2008 kgdb: kvm_nlist(_stopped_cpus): kgdb: kvm_nlist(_stoppcbs): [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd". Unread portion of the kernel message buffer: Fatal trap 12: page fault while in kernel mode fault virtual address = 0xd fault code = supervisor write, page not present instruction pointer = 0x20:0xc055d5ec stack pointer = 0x28:0xeb927b9c frame pointer = 0x28:0xeb927b9c 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 = 49994 (openvpn) trap number = 12 panic: page fault Uptime: 14h58m30s Dumping 3326 MB (2 chunks) chunk 0: 1MB (157 pages) ... ok chunk 1: 3326MB (851312 pages) 3310 3294 3278 3262 3246 3230 3214 3198 3182 3166 3150 3134 3118 3102 3086 3070 3054 3038 3022 3006 2990 2974 2958 2942 2926 2910 2894 2878 2862 2846 2830 2814 2798 2782 2766 2750 2734 2718 2702 2686 2670 2654 2638 2622 2606 2590 2574 2558 2542 2526 2510 2494 2478 2462 2446 2430 2414 2398 2382 2366 2350 2334 2318 2302 2286 2270 2254 2238 2222 2206 2190 2174 2158 2142 2126 2110 2094 2078 2062 2046 2030 2014 1998 1982 1966 1950 1934 1918 1902 1886 1870 1854 1838 1822 1806 1790 1774 1758 1742 1726 1710 1694 1678 1662 1646 1630 1614 1598 1582 1566 1550 1534 1518 1502 1486 1470 1454 1438 1422 1406 1390 1374 1358 1342 1326 1310 1294 1278 1262 1246 1230 1214 1198 1182 1166 1150 1134 1118 1102 1086 1070 1054 1038 1022 1006 990 974 958 942 926 910 894 878 862 846 830 814 798 782 766 750 734 718 702 686 670 654 638 622 606 590 574 558 542 526 510 494 478 462 446 430 414 398 382 366 350 334 318 302 286 270 254 238 222 206 190 174 158 142 126 110 94 78 62 46 30 14 #0 doadump () at pcpu.h:165 165 __asm __volatile("movl %%fs:0,%0" : "=r" (td)); (kgdb) bt #0 doadump () at pcpu.h:165 #1 0xc053952e in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409 #2 0xc05397c4 in panic (fmt=0xc071b0fc "%s") at /usr/src/sys/kern/kern_shutdown.c:565 #3 0xc06f3208 in trap_fatal (frame=0xeb927b5c, eva=13) at /usr/src/sys/i386/i386/trap.c:838 #4 0xc06f2f6f in trap_pfault (frame=0xeb927b5c, usermode=0, eva=13) at /usr/src/sys/i386/i386/trap.c:745 #5 0xc06f2bcd in trap (frame= {tf_fs = -342753272, tf_es = -1068498904, tf_ds = -1065746392, tf_edi = -929257216, tf_esi = 23531, tf_ebp = -342721636, tf_isp = -342721656, tf_ebx = 35, tf_edx = -929257216, tf_ecx = -1065693536, tf_eax = 5, tf_trapno = 12, tf_err = 2, tf_eip = -1068116500, tf_cs = 32, tf_eflags = 590342, tf_esp = -342721316, tf_ss = -1068117214}) at /usr/src/sys/i386/i386/trap.c:435 #6 0xc06e096a in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #7 0xc055d5ec in clear_selinfo_list (td=0xc89ca900) at /usr/src/sys/kern/sys_generic.c:1085 #8 0xc055d322 in poll (td=0xc89ca900, uap=0xeb927d04) at /usr/src/sys/kern/sys_generic.c:984 #9 0xc06f351f in syscall (frame= {tf_fs = 59, tf_es = 59, tf_ds = 59, tf_edi = -1077943456, tf_esi = 134902336, tf_ebp = -1077943512, tf_isp = -342721180, tf_ebx = 0, tf_edx = 1034, tf_ecx = 1034, tf_eax = 209, tf_trapno = 22, tf_err = 2, tf_eip = 673704855, tf_cs = ---Type to continue, or q to quit--- 51, tf_eflags = 662, tf_esp = -1077943556, tf_ss = 59}) at /usr/src/sys/i386/i386/trap.c:984 #10 0xc06e09bf in Xint0x80_syscall () at /usr/src/sys/i386/i386/exception.s:200 #11 0x00000033 in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb) up 7 #7 0xc055d5ec in clear_selinfo_list (td=0xc89ca900) at /usr/src/sys/kern/sys_generic.c:1085 1085 TAILQ_FOREACH(si, &td->td_selq, si_thrlist) (kgdb) p td $1 = (struct thread *) 0xc89ca900 (kgdb) p *td $2 = {td_proc = 0xc89c8c90, td_ksegrp = 0xc82e1540, td_plist = { tqe_next = 0x0, tqe_prev = 0xc89c8ca0}, td_kglist = {tqe_next = 0x0, tqe_prev = 0xc82e154c}, td_slpq = {tqe_next = 0xc8aa9180, tqe_prev = 0xc89cac18}, td_lockq = {tqe_next = 0x0, tqe_prev = 0xebb6bbac}, td_runq = {tqe_next = 0x0, tqe_prev = 0x0}, td_selq = {tqh_first = 0xcb11a8a8, tqh_last = 0xce64f89c}, td_sleepqueue = 0xc82d4bc0, td_turnstile = 0xc82c4e00, td_umtxq = 0xc8678280, td_tid = 100069, td_flags = 16842819, td_inhibitors = 0, td_pflags = 0, td_dupfd = 0, td_wchan = 0x0, td_wmesg = 0x0, td_lastcpu = 0 '\0', td_oncpu = 0 '\0', td_owepreempt = 0 '\0', td_locks = 5, td_tsqueue = 0 '\0', td_sqqueue = 0 '\0', td_blocked = 0x0, td_ithd = 0x0, td_lockname = 0x0, td_contested = {lh_first = 0xc82c3d40}, td_sleeplocks = 0x0, td_intr_nesting_level = 0, td_pinned = 1, td_mailbox = 0x0, td_ucred = 0xce6e2b00, td_standin = 0x0, td_upcall = 0x0, td_sticks = 4353, td_uuticks = 0, td_usticks = 0, td_intrval = 0, td_oldsigmask = {__bits = { 0, 0, 0, 0}}, td_sigmask = {__bits = {0, 0, 0, 0}}, td_siglist = { __bits = {0, 0, 0, 0}}, td_generation = 43, td_sigstk = {ss_sp = 0x0, ss_size = 0, ss_flags = 4}, td_kflags = 0, td_xsig = 0, td_profil_addr = 0, td_profil_ticks = 0, td_base_pri = 180 '�', td_priority = 16 '\020', td_pcb = 0xeb927d90, td_state = TDS_RUNNING, td_retval = {0, 1034}, td_slpcallout = {c_links = {sle = {sle_next = 0x0}, tqe = {tqe_next = 0x0, tqe_prev = 0xdc3250e0}}, c_time = 53907218, ---Type to continue, or q to quit---q c_arg =Quit (kgdb) up #8 0xc055d322 in poll (td=0xc89ca900, uap=0xeb927d04) at /usr/src/sys/kern/sys_generic.c:984 984 clear_selinfo_list(td); (kgdb) p td $3 = (struct thread *) 0xc89ca900 (kgdb) down #7 0xc055d5ec in clear_selinfo_list (td=0xc89ca900) at /usr/src/sys/kern/sys_generic.c:1085 1085 TAILQ_FOREACH(si, &td->td_selq, si_thrlist) (kgdb) p td->td_selq $6 = {tqh_first = 0xcb11a8a8, tqh_last = 0xce64f89c} (kgdb) p td->td_selq->tqh_first $7 = (struct selinfo *) 0xcb11a8a8 (kgdb) p *td->td_selq->tqh_first $8 = {si_thrlist = {tqe_next = 0xce64f89c, tqe_prev = 0xc89ca930}, si_thread = 0x0, si_note = {kl_list = {slh_first = 0x0}, kl_lock = 0xc051cd38 , kl_unlock = 0xc051cd6c , kl_locked = 0xc051cda8 , kl_lockarg = 0xcb11a8cc}, si_flags = 0} (kgdb) p *td->td_selq->tqh_last $9 = (struct selinfo *) 0x5 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 14 01:47:30 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 24614106566B for ; Wed, 14 Jan 2009 01:47:30 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from mail-bw0-f20.google.com (mail-bw0-f20.google.com [209.85.218.20]) by mx1.freebsd.org (Postfix) with ESMTP id 73E7A8FC12 for ; Wed, 14 Jan 2009 01:47:29 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: by bwz13 with SMTP id 13so1072067bwz.19 for ; Tue, 13 Jan 2009 17:47:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=i/A/K5kfwAeo9QjpXkPHWzrbBWsDWCCNnk7Zae+smTo=; b=Pm4BdBf85uqgXWxVjqxmqch9YTdcJZsGb21uAxNzvR81sbr1z3XnpO2eyRPUEl7kwU qJDkQ077iB3UIkJcmQ32hgDy/WJLKT28STu9c/xdOrwEyMARpscoLRzxErgHP9bICgc7 pbHCxUA2yflhI4tMmJAxVZVbBUf7HGt5WDWcU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=I3wJhXFNTHo3FL4yXkWs5fOnSaaeITlocanaZxrXjpKaBiVeO3Rqhz6BAJ1ITblJ9G 6snJJrtvFce7aEJYIS93+dk2cqldbP1Ku5wTdLebL8u0Di6i0YfPw+14XahNnk+5crcZ 0hW1d3Yvzt7Zw9GoZTFDKQbwUk1w++YGENKZ8= Received: by 10.180.208.2 with SMTP id f2mr11599555bkg.83.1231897648032; Tue, 13 Jan 2009 17:47:28 -0800 (PST) Received: by 10.181.26.3 with HTTP; Tue, 13 Jan 2009 17:47:27 -0800 (PST) Message-ID: <7d6fde3d0901131747m615fc8afr52cc6bd8ba742dd9@mail.gmail.com> Date: Tue, 13 Jan 2009 17:47:27 -0800 From: "Garrett Cooper" To: "Harald Servat" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <496CEFBE.8030007@bluezbox.com> Cc: freebsd-stable@freebsd.org, Oleksandr Tymoshenko Subject: Re: lenovo t400 does not start 7.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2009 01:47:30 -0000 On Tue, Jan 13, 2009 at 2:04 PM, Harald Servat wrote: > On Tue, Jan 13, 2009 at 9:40 PM, Harald Servat wrote: > >> >> >> On Tue, Jan 13, 2009 at 8:47 PM, Oleksandr Tymoshenko wrote: >> >>> Harald Servat wrote: >>> >>>> Hello, >>>> >>>> I downloaded FreeBSD 7.1 (DVD iso image) for amd64 architecture (with >>>> correct SHA256 checksum), but I'm unable to start the system (Lenovo >>>> T400). >>>> >>>> The boot process starts fine, the BTX messages appear, the 7-option menu >>>> also appears, but when I hit enter (or when I choose start without ACPI >>>> or >>>> start in safe mode) the \ symbols starts spinning for a while and then >>>> freezes. >>>> >>>> I also tried with the 7.1-amd64-CD1, 7.1-i386-CD1 and a snapshot of >>>> 8.0-CURRENT dated from December. And the result is the same for all of >>>> them. >>>> >>>> Does anyone have any idea on what can be happening? Or at least, how can >>>> I >>>> gather more information about this issue? >>>> >>> Not sure about install CDs but I tried all these systems on my >>> t400. >>> I installed 7.0 then upgraded it to 7.1 and when it turned out that >>> atheros is not 100% supported by it I upgraded to CURRENT. (I used cvsup >>> for upgrades). What is your HW configuration? >>> >>> >> Ok, thanks... I'll give a try to 7.0, and let's see if it works. >> >> > Uhm... FreeBSD 7.0 i386 CD1 behaves in the same manner. It frozes when > spinning the backslash symbol. > > The BIOS reports 4GB of RAM and SATA disk configured in AHCI mode. Should I > look for something unusual? and how? > > Thank you. Could you try booting with verbose information (option 5)? Also, have you tried disabling ACPI, or switching AHCI over to EIDE/compatible mode? Thanks, -Garrett From owner-freebsd-stable@FreeBSD.ORG Wed Jan 14 01:48:39 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AAE851065714 for ; Wed, 14 Jan 2009 01:48:39 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from mail-bw0-f20.google.com (mail-bw0-f20.google.com [209.85.218.20]) by mx1.freebsd.org (Postfix) with ESMTP id 025C88FC13 for ; Wed, 14 Jan 2009 01:48:38 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: by bwz13 with SMTP id 13so1073024bwz.19 for ; Tue, 13 Jan 2009 17:48:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=xz10iy6Qo1d2eppQhg535a/+5tW91+W/Jz/VBZOr1f0=; b=wkqxhnAnTyggqS1cilwBXIfEfM5GXq26ow4pEcZaVqXocgl2nKWHclxAQGwVCm1rAG pTlnQ90u4a7jhph+Je6zzMfhs4OlW83qTYYAxsnjVpvmm6h5OrvJ2LUbguvSQWGr5xmb 61GEnr4lS9wj39LHtqDLgcc1wZPn6EtaXh+oA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=E4EHCK8LJ4AKgKwxS5HSrriifAqqqs4BaDQPYszAjXl/oioUGSiysQ1DbNb6ex/Wiw 1FvJHc7WNbX/yhGrD++2OfJuBAmjqdSv2wsft03opSwmOGZzxytBNcLwv7qACrNnJJ8d 97p4lbQ6+J89anm790VxqzWfQgopnYrHSXp08= Received: by 10.181.145.7 with SMTP id x7mr11594172bkn.159.1231897718071; Tue, 13 Jan 2009 17:48:38 -0800 (PST) Received: by 10.181.26.3 with HTTP; Tue, 13 Jan 2009 17:48:38 -0800 (PST) Message-ID: <7d6fde3d0901131748pc25c1c0y87ff1d2400b7b815@mail.gmail.com> Date: Tue, 13 Jan 2009 17:48:38 -0800 From: "Garrett Cooper" To: "Harald Servat" In-Reply-To: <7d6fde3d0901131747m615fc8afr52cc6bd8ba742dd9@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <496CEFBE.8030007@bluezbox.com> <7d6fde3d0901131747m615fc8afr52cc6bd8ba742dd9@mail.gmail.com> Cc: freebsd-stable@freebsd.org, Oleksandr Tymoshenko Subject: Re: lenovo t400 does not start 7.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2009 01:48:41 -0000 On Tue, Jan 13, 2009 at 5:47 PM, Garrett Cooper wrote: > On Tue, Jan 13, 2009 at 2:04 PM, Harald Servat wrote: > >> On Tue, Jan 13, 2009 at 9:40 PM, Harald Servat wrote: >> >>> >>> >>> On Tue, Jan 13, 2009 at 8:47 PM, Oleksandr Tymoshenko wrote: >>> >>>> Harald Servat wrote: >>>> >>>>> Hello, >>>>> >>>>> I downloaded FreeBSD 7.1 (DVD iso image) for amd64 architecture (with >>>>> correct SHA256 checksum), but I'm unable to start the system (Lenovo >>>>> T400). >>>>> >>>>> The boot process starts fine, the BTX messages appear, the 7-option menu >>>>> also appears, but when I hit enter (or when I choose start without ACPI >>>>> or >>>>> start in safe mode) the \ symbols starts spinning for a while and then >>>>> freezes. >>>>> >>>>> I also tried with the 7.1-amd64-CD1, 7.1-i386-CD1 and a snapshot of >>>>> 8.0-CURRENT dated from December. And the result is the same for all of >>>>> them. >>>>> >>>>> Does anyone have any idea on what can be happening? Or at least, how can >>>>> I >>>>> gather more information about this issue? >>>>> >>>> Not sure about install CDs but I tried all these systems on my >>>> t400. >>>> I installed 7.0 then upgraded it to 7.1 and when it turned out that >>>> atheros is not 100% supported by it I upgraded to CURRENT. (I used cvsup >>>> for upgrades). What is your HW configuration? >>>> >>>> >>> Ok, thanks... I'll give a try to 7.0, and let's see if it works. >>> >>> >> Uhm... FreeBSD 7.0 i386 CD1 behaves in the same manner. It frozes when >> spinning the backslash symbol. >> >> The BIOS reports 4GB of RAM and SATA disk configured in AHCI mode. Should I >> look for something unusual? and how? >> >> Thank you. > > Could you try booting with verbose information (option 5)? Also, > have you tried disabling ACPI, or switching AHCI over to > EIDE/compatible mode? > Thanks, > -Garrett Also, try upgrading your BIOS to the latest version, if at all possible. -Garrett From owner-freebsd-stable@FreeBSD.ORG Wed Jan 14 01:59:39 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C7F7A1065670 for ; Wed, 14 Jan 2009 01:59:39 +0000 (UTC) (envelope-from glen.j.barber@gmail.com) Received: from mail-bw0-f20.google.com (mail-bw0-f20.google.com [209.85.218.20]) by mx1.freebsd.org (Postfix) with ESMTP id 4FC5E8FC19 for ; Wed, 14 Jan 2009 01:59:39 +0000 (UTC) (envelope-from glen.j.barber@gmail.com) Received: by bwz13 with SMTP id 13so1082119bwz.19 for ; Tue, 13 Jan 2009 17:59:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=Q9KBDw7HbXqwmZ7Y52/xAsr++rvW6mO7uUwzu65IbZk=; b=WTLiY/3eLjobSYct2E4nwssPcmjUJqjP2aBvykdhVfckYcffxm+tcYDmITybbSdy3Y aMVdjWJI5UIOe+f6anVGGJ3mb7yX6QeJIA6BIRaTNrg48L9zm0vjwv3uDwB93WdCLDVq K68aRm8hkuJrCC3uMPW2XUfBd8Y8Dh7WxnyoY= 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=nanBVl+fozZTHCdNQ1zVElo0uJPuKmy7HsWtQBUv5jdUbj9CZiUJCQCX+zi4tn55av vWfdhrnNrnHQPvFYxZb3DPnRBrYsXQ1fNTa2xu6B/sbkWrjS/0cNbbYiINiXixY+fO9m S88kTBeIGx8NjAdzY4p/4215Pjy8lpTWWgOlA= MIME-Version: 1.0 Received: by 10.223.111.19 with SMTP id q19mr2910371fap.58.1231898378238; Tue, 13 Jan 2009 17:59:38 -0800 (PST) In-Reply-To: References: Date: Tue, 13 Jan 2009 20:59:38 -0500 Message-ID: <4ad871310901131759o5579f365n25d554e586513c7d@mail.gmail.com> From: Glen Barber To: Harald Servat Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: lenovo t400 does not start 7.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2009 01:59:40 -0000 On Tue, Jan 13, 2009 at 1:57 PM, Harald Servat wrote: > Hello, > > I downloaded FreeBSD 7.1 (DVD iso image) for amd64 architecture (with > correct SHA256 checksum), but I'm unable to start the system (Lenovo T400). > Could you test the disc on a different machine to verify a good burn? [snip] -- Glen Barber From owner-freebsd-stable@FreeBSD.ORG Wed Jan 14 02:15:40 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CBD9F1065670 for ; Wed, 14 Jan 2009 02:15:40 +0000 (UTC) (envelope-from ganbold@micom.mng.net) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.freebsd.org (Postfix) with ESMTP id 82B168FC16 for ; Wed, 14 Jan 2009 02:15:40 +0000 (UTC) (envelope-from ganbold@micom.mng.net) Received: from [202.179.0.164] (helo=daemon.micom.mng.net) by publicd.ub.mng.net with esmtpa (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LMug4-0007ZM-48; Wed, 14 Jan 2009 09:36:16 +0800 Message-ID: <496D41A3.2040306@micom.mng.net> Date: Wed, 14 Jan 2009 09:36:35 +0800 From: Ganbold User-Agent: Thunderbird 2.0.0.12 (X11/20080415) MIME-Version: 1.0 To: Harald Servat References: In-Reply-To: X-Enigmail-Version: 0.95.6 OpenPGP: id=78F6425E Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: lenovo t400 does not start 7.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2009 02:15:41 -0000 Harald Servat wrote: > Hello, > > I downloaded FreeBSD 7.1 (DVD iso image) for amd64 architecture (with > correct SHA256 checksum), but I'm unable to start the system (Lenovo T400). > > The boot process starts fine, the BTX messages appear, the 7-option menu > also appears, but when I hit enter (or when I choose start without ACPI or > start in safe mode) the \ symbols starts spinning for a while and then > freezes. > > I also tried with the 7.1-amd64-CD1, 7.1-i386-CD1 and a snapshot of > 8.0-CURRENT dated from December. And the result is the same for all of them. > > Does anyone have any idea on what can be happening? Or at least, how can I > gather more information about this issue? > Please try setting "Integrated Graphics" or "Switchable Graphics" mode on Display setting in BIOS. AFAICT it is known issue and FreeBSD doesn't boot when set to Discrete Graphics in BIOS. Ganbold > Thank you. > -- Too often I find that the volume of paper expands to fill the available briefcases. -- Governor Jerry Brown From owner-freebsd-stable@FreeBSD.ORG Wed Jan 14 02:18:10 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A74861065670 for ; Wed, 14 Jan 2009 02:18:10 +0000 (UTC) (envelope-from ganbold@micom.mng.net) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.freebsd.org (Postfix) with ESMTP id 5E26E8FC1A for ; Wed, 14 Jan 2009 02:18:10 +0000 (UTC) (envelope-from ganbold@micom.mng.net) Received: from [202.179.0.164] (helo=daemon.micom.mng.net) by publicd.ub.mng.net with esmtpa (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LMvKG-0007pH-TW; Wed, 14 Jan 2009 10:17:48 +0800 Message-ID: <496D4B60.5050807@micom.mng.net> Date: Wed, 14 Jan 2009 10:18:08 +0800 From: Ganbold User-Agent: Thunderbird 2.0.0.12 (X11/20080415) MIME-Version: 1.0 To: Harald Servat References: <496D41A3.2040306@micom.mng.net> In-Reply-To: <496D41A3.2040306@micom.mng.net> X-Enigmail-Version: 0.95.6 OpenPGP: id=78F6425E Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: lenovo t400 does not start 7.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2009 02:18:11 -0000 Ganbold wrote: > Harald Servat wrote: >> Hello, >> >> I downloaded FreeBSD 7.1 (DVD iso image) for amd64 architecture (with >> correct SHA256 checksum), but I'm unable to start the system (Lenovo >> T400). >> >> The boot process starts fine, the BTX messages appear, the 7-option >> menu >> also appears, but when I hit enter (or when I choose start without >> ACPI or >> start in safe mode) the \ symbols starts spinning for a while and then >> freezes. >> >> I also tried with the 7.1-amd64-CD1, 7.1-i386-CD1 and a snapshot of >> 8.0-CURRENT dated from December. And the result is the same for all >> of them. >> >> Does anyone have any idea on what can be happening? Or at least, >> how can I >> gather more information about this issue? >> > > Please try setting "Integrated Graphics" or "Switchable Graphics" mode > on Display setting in > BIOS. AFAICT it is known issue and FreeBSD doesn't boot when set to > Discrete Graphics in BIOS. Or maybe it boots but nothing shows on screen. Ganbold From owner-freebsd-stable@FreeBSD.ORG Wed Jan 14 04:05:50 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 53ADB1065670 for ; Wed, 14 Jan 2009 04:05:50 +0000 (UTC) (envelope-from freebsd@optiksecurite.com) Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by mx1.freebsd.org (Postfix) with ESMTP id 260388FC1A for ; Wed, 14 Jan 2009 04:05:50 +0000 (UTC) (envelope-from freebsd@optiksecurite.com) MIME-version: 1.0 Content-transfer-encoding: 8BIT Content-type: text/plain; charset=ISO-8859-1; format=flowed Received: from [192.168.10.103] ([74.56.107.65]) by VL-MO-MR003.ip.videotron.ca (Sun Java(tm) System Messaging Server 6.3-4.01 (built Aug 3 2007; 32bit)) with ESMTP id <0KDG00JG10POM390@VL-MO-MR003.ip.videotron.ca> for freebsd-stable@freebsd.org; Tue, 13 Jan 2009 23:05:49 -0500 (EST) Message-id: <496D6527.7060207@optiksecurite.com> Date: Tue, 13 Jan 2009 23:08:07 -0500 From: FreeBSD User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) To: pyunyh@gmail.com References: <8dfae1c10901070639x67945324jeeecfcac647d7976@mail.gmail.com> <8dfae1c10901071550s69d99802p31ca7c775f3d6823@mail.gmail.com> <88527079.20090111192206@donpac.ru> <20090112011146.GC46346@cdnetworks.co.kr> <496BBFF6.7010300@optiksecurite.com> <20090113004018.GG46346@cdnetworks.co.kr> <496CB0A2.2020103@optiksecurite.com> <20090114003228.GA55351@cdnetworks.co.kr> In-reply-to: <20090114003228.GA55351@cdnetworks.co.kr> Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 7.1 Breaks re and rl Network Interface Drivers X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2009 04:05:50 -0000 Pyun YongHyeon a écrit : > On Tue, Jan 13, 2009 at 10:17:54AM -0500, FreeBSD wrote: > > Pyun YongHyeon a ?crit : > > >On Mon, Jan 12, 2009 at 05:11:02PM -0500, FreeBSD wrote: > > > > Pyun YongHyeon a ?crit : > > > > >On Sun, Jan 11, 2009 at 07:22:06PM +0300, Eugene Gladchenko wrote: > > > > > > Walter, > > > > > > > > > > > > Thursday, January 8, 2009, 2:50:40 AM, you wrote: > > > > > > > > > > > > WV> Booting kernel.old, which is 7.0-RELEASE-p7 completely > > > alleviates > > all > > > > > > WV> problems. I believe this roundly confirms that this is a bug > > > in the > > > > > > WV> 7.1-RELEASE re kernel drivers. > > > > > > > > > > > > Does kern/130011 look similar? > > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=130011 > > > > > > > > > >Do you have RTL8168C controller? If not, it's not related with > > > > >Walter's issue as 7.0-RELEASE didn't have a support for RTL8168C. > > > > > > > > > > > > > > > > > The re driver was really broken in 7.1-RC2 and the fix didn't get > > > to > > 7.1-RELEASE. > > > > > > > > > >If you have re(4) issues, please provide more details such as > > > > >dmesg output, way to reproduce the issue etc. > > > > > > > > > > > > > Hi, > > > > > > > > I have the exact same card and the exact same problem as the PR you > > > > mentionned. > > > > > > > > re0@pci0:3:0:0: class=0x020000 card=0x02831028 chip=0x816810ec rev=0x02 > > > > hdr=0x00 > > > > vendor = 'Realtek Semiconductor' > > > > device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' > > > > class = network > > > > subclass = ethernet > > > > > > > > > > > > re0: > > > Gigabit Ethernet> port 0xd800-0xd8ff mem > > > > 0xfeaff000-0xfeafffff,0xfdff0000-0xfdffffff irq 18 at device 0.0 on pci3 > > > > re0: Chip rev. 0x3c000000 > > > > re0: MAC rev. 0x00400000 > > > > re0: PHY write failed > > > > re0: PHY write failed > > > > re0: MII without any phy! > > > > device_attach: re0 attach returned 6 > > > > > > > > I tried to compile a new kernel with the latest version of the 3 files > > > > listed in the PR: > > > > src/sys/dev/re/if_re.c,v 1.147 2008/12/22 00:46:22 yongari > > > > src/sys/pci/if_rl.c,v 1.170.2.10 2009/01/12 04:10:40 yongari > > > > src/sys/pci/if_rlreg.h,v 1.67.2.16 2009/01/12 03:48:25 yongari > > > > > > > > > >You need lastest if_rl.c and if_rlreg.h as well as if_re.c. > > > > > > > That's exactly what I tried. Look at the 3 revision of the specified > > You've used if_rlreg.h in stable/7. > > > files. I even tried with a if_rl.c from the 22/12/08 but got the same > > problem. > > > > Use if_re.c, if_rl.h and if_rl.c in HEAD. Not all changes were > MFCed. > > Oups... I didn't check the branch. I just concentrated on the "latest revision" not the latest revision in HEAD. Sorry for the noise, it's the first time I have to deal with that kind of kernel modification. I just rebooted and the interface appears in ifconfig. I will let you know if I experience any problem. Thanks again for your good work and the time to took to help me resolve this issue. Martin From owner-freebsd-stable@FreeBSD.ORG Wed Jan 14 05:21:39 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 30145106564A for ; Wed, 14 Jan 2009 05:21:39 +0000 (UTC) (envelope-from tom@tomjudge.com) 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 1C9A98FC16 for ; Wed, 14 Jan 2009 05:21:39 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from OMTA12.emeryville.ca.mail.comcast.net ([76.96.30.44]) by QMTA08.emeryville.ca.mail.comcast.net with comcast id 3AAt1b0050x6nqcA8H5gby; Wed, 14 Jan 2009 05:05:40 +0000 Received: from [192.168.1.104] ([71.57.105.220]) by OMTA12.emeryville.ca.mail.comcast.net with comcast id 3H5e1b0034lKpr38YH5fQE; Wed, 14 Jan 2009 05:05:39 +0000 Message-ID: <496D72AE.8090303@tomjudge.com> Date: Tue, 13 Jan 2009 23:05:50 -0600 From: Tom Judge User-Agent: Thunderbird 2.0.0.19 (X11/20090105) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: cperciva@freebsd.org Subject: Using FreeBSD Update to deploy system updates from custom builds X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2009 05:21:39 -0000 Hi, I was wondering if anyone was using freebsd-update to manage deployment of custom FreeBSD builds to there systems. Here is the scenario, I have 2 binary build servers at the moment (one for i386 and one for amd64) and currently we stage the deployments of updates on NFS servers at each site. We use make installworld/kernel to update the servers from read only src and obj NFS mounts. I'm now looking to remove the src trees from the NFS servers and possibly the obj trees and use freebsd-update to deploy and maintain the custom build installation and updates. So I have 2 questions: 1) Does this seem sensible? It seems within scope of what freebsd-update was designed to do. 2) How does one go about building the binary distributions that freebsd-update expects to be on the update server? Thanks Tom From owner-freebsd-stable@FreeBSD.ORG Wed Jan 14 06:39:25 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5ED28106564A for ; Wed, 14 Jan 2009 06:39:25 +0000 (UTC) (envelope-from pldrouin@pldrouin.net) Received: from smtp.cyberfingers.net (smtp.cyberfingers.net [198.177.254.227]) by mx1.freebsd.org (Postfix) with ESMTP id 3F73B8FC12 for ; Wed, 14 Jan 2009 06:39:25 +0000 (UTC) (envelope-from pldrouin@pldrouin.net) Received: from mdaemon.pldrouin.net (static-68-162-93-99.phil.east.verizon.net [68.162.93.99]) by smtp.cyberfingers.net (Postfix) with ESMTP id E28FDAB6C14 for ; Wed, 14 Jan 2009 01:33:02 -0500 (EST) Message-ID: <496D889C.2030305@pldrouin.net> Date: Wed, 14 Jan 2009 01:39:24 -0500 From: Pierre-Luc Drouin User-Agent: Thunderbird 2.0.0.19 (X11/20090108) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Problem with CPU freq in 7.1-STABLE -- take 2 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2009 06:39:25 -0000 Hi, I noticed a problem with CPU freq in 7.1-STABLE. The maximum frequency showed by sysctl is 500Mhz lower than what it should be for my Pentium M 2Ghz. Here is the output from dmesg: Copyright (c) 1992-2009 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.1-STABLE #7: Tue Jan 6 16:01:20 EST 2009 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) M processor 2.00GHz (1995.15-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6d8 Stepping = 8 Features=0xafe9fbff Features2=0x180 AMD Features=0x100000 and the output from sysctl: dev.cpu.0.freq_levels: 1500/-1 1312/-1 1200/-1 1050/-1 1000/-1 875/-1 800/-1 700/-1 600/-1 525/-1 450/-1 375/-1 300/-1 225/-1 150/-1 75/-1 dev.est.0.freq_settings: 1500/-1 1200/-1 1000/-1 800/-1 600/-1 This used to work correctly in 7.0... Thanks! Pierre-Luc Drouin From owner-freebsd-stable@FreeBSD.ORG Wed Jan 14 08:34:07 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B335C1065670 for ; Wed, 14 Jan 2009 08:34:07 +0000 (UTC) (envelope-from db@danielbond.org) Received: from mail.nsn.no (mailone.nsn.no [62.89.38.160]) by mx1.freebsd.org (Postfix) with SMTP id 273758FC12 for ; Wed, 14 Jan 2009 08:34:06 +0000 (UTC) (envelope-from db@danielbond.org) Received: (qmail 18051 invoked by uid 0); 14 Jan 2009 08:34:05 -0000 Received: from unknown (HELO ?172.16.3.90?) (85.95.44.187) by mail.nsn.no with SMTP; 14 Jan 2009 08:34:05 -0000 Message-Id: <76BAA4E0-A567-4173-A67E-38BD112F93C1@danielbond.org> From: Daniel Bond To: Tom Judge In-Reply-To: <496D72AE.8090303@tomjudge.com> Mime-Version: 1.0 (Apple Message framework v930.3) Date: Wed, 14 Jan 2009 09:34:04 +0100 References: <496D72AE.8090303@tomjudge.com> X-Mailer: Apple Mail (2.930.3) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: Using FreeBSD Update to deploy system updates from custom builds X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2009 08:34:07 -0000 Hi Tom, I don't know how much documentation there is on this, but if you are investigating this issue, maybe you would like to contribute/update some documentation on it? Royce gave me a link to the tools, http://www.freebsd.org/cgi/cvsweb.cgi/projects/freebsd-update-server/ reading through some of the scripts might give some clues. Regards, Daniel Bond. On Jan 14, 2009, at 6:05 AM, Tom Judge wrote: > Hi, > > I was wondering if anyone was using freebsd-update to manage > deployment of custom FreeBSD builds to there systems. > > Here is the scenario, I have 2 binary build servers at the moment > (one for i386 and one for amd64) and currently we stage the > deployments of updates on NFS servers at each site. We use make > installworld/kernel to update the servers from read only src and obj > NFS mounts. > > I'm now looking to remove the src trees from the NFS servers and > possibly the obj trees and use freebsd-update to deploy and maintain > the custom build installation and updates. > > So I have 2 questions: > > 1) Does this seem sensible? It seems within scope of what freebsd- > update was designed to do. > > 2) How does one go about building the binary distributions that > freebsd-update expects to be on the update server? > > > Thanks > > Tom > > _______________________________________________ > 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 Wed Jan 14 13:16:55 2009 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 4DB961065674 for ; Wed, 14 Jan 2009 13:16:55 +0000 (UTC) (envelope-from gunnar@bsd-gf.sr.se) Received: from dart.sr.se (dart.SR.SE [134.25.0.132]) by mx1.freebsd.org (Postfix) with ESMTP id D48C98FC22 for ; Wed, 14 Jan 2009 13:16:54 +0000 (UTC) (envelope-from gunnar@bsd-gf.sr.se) Received: from honken.sr.se (honken.sr.se [134.25.128.27]) by dart.sr.se (8.14.2/8.14.2) with ESMTP id n0ECcDsk045750 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 14 Jan 2009 13:38:18 +0100 (CET) (envelope-from gunnar@bsd-gf.sr.se) Received: from bsd-gf.sr.se (bsd-gf.sr.se [134.25.191.27]) by honken.sr.se (8.14.2/8.14.2) with ESMTP id n0ECcDow044903 for ; Wed, 14 Jan 2009 13:38:13 +0100 (CET) (envelope-from gunnar@bsd-gf.sr.se) Received: from bsd-gf.sr.se (localhost [127.0.0.1]) by bsd-gf.sr.se (8.14.3/8.14.2) with ESMTP id n0ECcDUA005591 for ; Wed, 14 Jan 2009 13:38:13 +0100 (CET) (envelope-from gunnar@bsd-gf.sr.se) Received: (from gunnar@localhost) by bsd-gf.sr.se (8.14.3/8.14.3/Submit) id n0ECcDq5005590 for stable@freebsd.org; Wed, 14 Jan 2009 13:38:13 +0100 (CET) (envelope-from gunnar) Date: Wed, 14 Jan 2009 13:38:13 +0100 From: Gunnar Flygt To: stable@freebsd.org Message-ID: <20090114123813.GA76310@sr.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Cc: Subject: Heimdal 1.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Gunnar Flygt List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2009 13:16:55 -0000 I asked this question a while ago, but got no answers. I'm trying again Is there any possibility that heimdal 1.1 that works beautifully in Current will be backported to FreeBSD-7.x? Gunnar Flygt Sveriges Radio Teknik/IT From owner-freebsd-stable@FreeBSD.ORG Wed Jan 14 13:26:00 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C8EF7106567C; Wed, 14 Jan 2009 13:26:00 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from constantine.ticketswitch.com (constantine.ticketswitch.com [IPv6:2002:57e0:1d4e:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id 85AC68FC1B; Wed, 14 Jan 2009 13:26:00 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from dilbert.rattatosk ([10.64.50.6] helo=dilbert.ticketswitch.com) by constantine.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LN5kn-000A4k-Ni; Wed, 14 Jan 2009 13:25:53 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LN5km-0000z7-Sz; Wed, 14 Jan 2009 13:25:52 +0000 To: rwatson@FreeBSD.org In-Reply-To: Message-Id: From: Pete French Date: Wed, 14 Jan 2009 13:25:52 +0000 Cc: freebsd-stable@freebsd.org, drosih@rpi.edu, rblayzor.bulk@inoc.net Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2009 13:26:01 -0000 > If you have BREAK_TO_DEBUGGER compiled into the kernel, then try pressing > ctrl-alt-break on the console to see if you can drop into the debugger, or > issue a serial break on a serial console. Well, I added BREAK_TO_DEBUGGER to the kernel config I had which contained all the other stuff (WITNESS etc...). The end result... ...it no longer crashes :-( I am not sure what to make of that! Wat could adding this to the kernel possibly do which would make my problems go away ? Should I try just adding this option to my GENERIC kernel and seeing if that also gives me something stable ? -pete. From owner-freebsd-stable@FreeBSD.ORG Wed Jan 14 13:42:37 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3FD9D106564A for ; Wed, 14 Jan 2009 13:42:37 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 1BBBE8FC0C for ; Wed, 14 Jan 2009 13:42:37 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id CAD3D46B0C; Wed, 14 Jan 2009 08:42:36 -0500 (EST) Date: Wed, 14 Jan 2009 13:42:36 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Pete French In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org, drosih@rpi.edu, rblayzor.bulk@inoc.net Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2009 13:42:37 -0000 On Wed, 14 Jan 2009, Pete French wrote: >> If you have BREAK_TO_DEBUGGER compiled into the kernel, then try pressing >> ctrl-alt-break on the console to see if you can drop into the debugger, or >> issue a serial break on a serial console. > > Well, I added BREAK_TO_DEBUGGER to the kernel config I had which contained > all the other stuff (WITNESS etc...). The end result... > > ...it no longer crashes :-( > > I am not sure what to make of that! Wat could adding this to the kernel > possibly do which would make my problems go away ? Should I try just adding > this option to my GENERIC kernel and seeing if that also gives me something > stable ? Yeah, that is unexpected -- the BREAK_TO_DEBUGGER path should have almost know effect on control flow, unlike, say, WITNESS, which significantly distorts timing. Is there any chance you picked up any of the recent fixes that went into RELENG_7 without noticing, and that perhaps one of those did it? With regard to what to do: if you didn't pick up a fix without noticing, yeah, I think it's worth testing the hypothesis that BREAK_TO_DEBUGGER fixed (or at least, masked) the problem. Generally with this sort of testing one has to be pretty rigorous in testing assumptions, because it's easy for changes to sneak in. Particularly annoying are seemingly innocuous code changes that do things like slightly rearrange kernel memory. FWIW, I suspect the various reports we are seeing reflect more than one problem, and that they must be relatively edge-case individually but reports of a few problems have lead to more "coming out of the woodwork". Obviously, the problems are not edge-case to the people experiencing them... Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-stable@FreeBSD.ORG Wed Jan 14 14:16:44 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 15E8F106567F; Wed, 14 Jan 2009 14:16:44 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from constantine.ticketswitch.com (constantine.ticketswitch.com [IPv6:2002:57e0:1d4e:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id C560D8FC1A; Wed, 14 Jan 2009 14:16:43 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from dilbert.rattatosk ([10.64.50.6] helo=dilbert.ticketswitch.com) by constantine.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LN6Xt-000AtJ-Qj; Wed, 14 Jan 2009 14:16:37 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LN6Xt-0001Je-On; Wed, 14 Jan 2009 14:16:37 +0000 To: rwatson@FreeBSD.org In-Reply-To: Message-Id: From: Pete French Date: Wed, 14 Jan 2009 14:16:37 +0000 Cc: freebsd-stable@freebsd.org, drosih@rpi.edu, rblayzor.bulk@inoc.net Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2009 14:16:44 -0000 > effect on control flow, unlike, say, WITNESS, which significantly distorts > timing. Is there any chance you picked up any of the recent fixes that went > into RELENG_7 without noticing, and that perhaps one of those did it? With I'm pretty certian of that - I hav just been changing kernel config files, I havent actually csup'd at all. > regard to what to do: if you didn't pick up a fix without noticing, yeah, I > think it's worth testing the hypothesis that BREAK_TO_DEBUGGER fixed (or at > least, masked) the problem. OK. I think I need at leats 4 kernels to try here: GENERIC (which should show the problenm), my original DEBUG (which also shows the problem) plus both of those with BREAK_TO_DEBUGGER included to see if that fixes it. Can I just add BREAK_TO_DEBUGGER on its own to a config file ? I was wondering if I need to include one of the other debugger options so that it has something to break to ? > FWIW, I suspect the various reports we are seeing reflect more than one > problem, and that they must be relatively edge-case individually but reports > of a few problems have lead to more "coming out of the woodwork". Obviously, > the problems are not edge-case to the people experiencing them... I was thinking that too - I've been guilty of this in the past too, lumping my problem in with others under the asusmption that it's all the same. This is onbiously pretty rare - out of 24 of the HP servers the problems only crops up on 4 of them. But there is nothing dfferent about those 4. I will let you know what my various kerenl compiles give me - am buolding again from scratch, which is slow with WITNESS enabled. -pete. From owner-freebsd-stable@FreeBSD.ORG Wed Jan 14 14:41:32 2009 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 89F671065688; Wed, 14 Jan 2009 14:41:32 +0000 (UTC) (envelope-from admin@kkip.pl) Received: from mainframe.kkip.pl (kkip.pl [87.105.164.78]) by mx1.freebsd.org (Postfix) with ESMTP id 35C0B8FC1A; Wed, 14 Jan 2009 14:41:32 +0000 (UTC) (envelope-from admin@kkip.pl) Received: from admin.admin.lan.kkip.pl ([10.66.3.253]) by mainframe.kkip.pl with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LN6ZT-0007wy-BO; Wed, 14 Jan 2009 15:18:15 +0100 Message-ID: <496DF428.6050800@kkip.pl> Date: Wed, 14 Jan 2009 15:18:16 +0100 From: Bartosz Stec User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Walter Venable References: <8dfae1c10901070639x67945324jeeecfcac647d7976@mail.gmail.com> In-Reply-To: <8dfae1c10901070639x67945324jeeecfcac647d7976@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated-User: admin@kkip.pl X-Authenticator: plain X-Sender-Verify: SUCCEEDED (sender exists & accepts mail) X-Exim-Version: 4.69 (build at 14-Jan-2009 11:48:13) X-Date: 2009-01-14 15:18:15 X-Connected-IP: 10.66.3.253:3749 X-Message-Linecount: 45 X-Body-Linecount: 31 X-Message-Size: 1794 X-Body-Size: 1163 X-Received-Count: 1 X-Recipient-Count: 3 X-Local-Recipient-Count: 3 X-Local-Recipient-Defer-Count: 0 X-Local-Recipient-Fail-Count: 0 Cc: stable@freebsd.org, yongari@freebsd.org Subject: Re: FreeBSD 7.1 Breaks re and rl Network Interface Drivers X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2009 14:41:33 -0000 Walter Venable pisze: > FreeBSD 7.1 upgrade broke my network access, machine is totally > offline (powered-on and I can play inside it at the terminal, but > absolutely 0 network access): > This happened AFTER make kernel but BEFORE make installworld. I think > this implies it's a kernel driver issue. > > http://forums.freebsd.org/showthread.php?t=1323 (this is an ongoing > thread on the issue, the rl driver has also been reported broken). > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > I can confirm issues with re and 7.1-R dmesg: re0: port 0xbc00-0xbcff mem 0xfbfff000-0xfbfff0ff irq 17 at device 7.0 on pci1 re0: Chip rev. 0x18000000 re0: MAC rev. 0x00000000 In my case this NIC works, but lags like hell after upgrade! Working on console gives me pauses every 3-4 second, and second server which connect to this one with re0 is reporting that communication is lost every couple of minutes -- Bartosz Stec From owner-freebsd-stable@FreeBSD.ORG Wed Jan 14 14:59:09 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 906C210656E3 for ; Wed, 14 Jan 2009 14:59:09 +0000 (UTC) (envelope-from jbiquez@icsmx.com) Received: from mail.icsmx.com (mail.icsmx.com [200.33.246.8]) by mx1.freebsd.org (Postfix) with ESMTP id 50E8D8FC14 for ; Wed, 14 Jan 2009 14:59:08 +0000 (UTC) (envelope-from jbiquez@icsmx.com) Received: from PC.icsmx.com (dsl-189-144-45-147.prod-infinitum.com.mx [189.144.45.147] (may be forged)) by mail.icsmx.com (8.13.7/8.13.6) with ESMTP id n0EEc0ww071823 for ; Wed, 14 Jan 2009 08:38:01 -0600 (CST) (envelope-from jbiquez@icsmx.com) Message-Id: <200901141438.n0EEc0ww071823@mail.icsmx.com> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Wed, 14 Jan 2009 08:34:44 -0600 To: freebsd-stable@freebsd.org From: Jorge Biquez In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: Simple? Hardware 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: Wed, 14 Jan 2009 14:59:10 -0000 Hello all. I have a 4.11 Stable version that has been working without problems in the last years. We do not need nothing else for the moment but we are looking to have more speed. It has been running under a double Pentium III processor with 512MB of ram and it has a disk of 40GB. I was wondering of it is possible to do 2 things. a) Only put the disk in a new machine at least a double core with 2GB of RAM. My guess is that could boot with a few problems on hardware.... what do you think? b) If is possible to "clone" the same installation to a new faster disk (like a sata 250GB). I know I can install a /.x version and for sure will work but here the idea is to have things running as usual without problems. This installation is very stable and secure and has been with us for years.... we would like to keep it working for more years.... :=) on b). Is there a simple way to do it? Thanks in advance Jorge Biquez From owner-freebsd-stable@FreeBSD.ORG Wed Jan 14 15:17:37 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A13C41065670 for ; Wed, 14 Jan 2009 15:17:37 +0000 (UTC) (envelope-from krassi@bulinfo.net) Received: from mx.bulinfo.net (mx.bulinfo.net [193.194.156.1]) by mx1.freebsd.org (Postfix) with ESMTP id 044428FC20 for ; Wed, 14 Jan 2009 15:17:36 +0000 (UTC) (envelope-from krassi@bulinfo.net) Received: from localhost (localhost [127.0.0.1]) by mx.bulinfo.net (Postfix) with ESMTP id EB5A4C1A7; Wed, 14 Jan 2009 17:17:34 +0200 (EET) Received: from mx.bulinfo.net ([127.0.0.1]) by localhost (mx.bulinfo.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 29884-08; Wed, 14 Jan 2009 17:17:33 +0200 (EET) Received: from [192.168.2.188] (pythia.bulinfo.net [212.72.195.5]) by mx.bulinfo.net (Postfix) with ESMTP id 8EF2DBDF5; Wed, 14 Jan 2009 17:17:33 +0200 (EET) Message-ID: <496E0207.8030302@bulinfo.net> Date: Wed, 14 Jan 2009 17:17:27 +0200 From: Krassimir Slavchev User-Agent: Thunderbird 2.0.0.14 (X11/20080616) MIME-Version: 1.0 To: Torfinn Ingolfsen References: <49633C85.3090507@bulinfo.net> <20090108204311.c9700e91.torfinn.ingolfsen@broadpark.no> <4967045D.30109@bulinfo.net> <20090109202457.19d0fc1a.torfinn.ingolfsen@broadpark.no> In-Reply-To: <20090109202457.19d0fc1a.torfinn.ingolfsen@broadpark.no> X-Enigmail-Version: 0.95.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigB647D0FEC8617316E0568C6C" X-Virus-Scanned: amavisd-new at mx.bulinfo.net Cc: freebsd-stable@freebsd.org, Nate Lawson Subject: Re: ACPI support? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2009 15:17:38 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigB647D0FEC8617316E0568C6C Content-Type: multipart/mixed; boundary="------------060905050403070305090308" This is a multi-part message in MIME format. --------------060905050403070305090308 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello, Finally I found what is the problem. from ACPI CA release notes: =2E.. 14 May 2008. Summary of changes for version 20080514: 1) ACPI CA Core Subsystem: Fixed a problem where GPEs were enabled too early during the ACPICA initialization. This could lead to "handler not installed" errors on some= machines. Moved GPE enable until after _REG/_STA/_INI methods are run. Th= is ensures that all operation regions and devices throughout the namespace have been initialized before GPEs are enabled. Alexey Starikovskiy, BZ 9916. =2E.. See the attached patch for possible workaround of the problem. References: http://lists.freebsd.org/pipermail/freebsd-acpi/2008-October/005167.html Best Regards Torfinn Ingolfsen wrote: > On Fri, 09 Jan 2009 10:01:33 +0200 > Krassimir Slavchev wrote: >=20 >> I have found that thread. >=20 > FWIW, I started a new thread[1] on freebsd-mobile, to update the status= > now after FreeBSD 7.1 has been released >=20 >> The problem may be with allocating resources by ACPI PCI-PCI bridge. >> There is a way to set needed values: >> http://lists.freebsd.org/pipermail/freebsd-acpi/2008-May/004905.html >=20 > Interesting. For my laptop, it seems that these bridges have the > problem: > pcib2: irq 17 at device 28.0 on pci0 > pcib2: domain 0 > pcib2: secondary bus 2 > pcib2: subordinate bus 2 > pcib2: I/O decode 0x0-0x0 > pcib2: no prefetched decode > pci2: on pcib2 > pci2: domain=3D0, physical bus=3D2 > pcib3: irq 16 at device 28.1 on pci0 > pcib3: domain 0 > pcib3: secondary bus 3 > pcib3: subordinate bus 3 > pcib3: I/O decode 0x0-0x0 > pcib3: no prefetched decode > pci3: on pcib3 > pci3: domain=3D0, physical bus=3D3 >=20 > and also these: >=20 > pcib4: irq 18 at device 28.2 on pci0 > pcib4: domain 0 > pcib4: secondary bus 4 > pcib4: subordinate bus 4 > pcib4: I/O decode 0x0-0x0 > pcib4: no prefetched decode > pci4: on pcib4 > pci4: domain=3D0, physical bus=3D4 >=20 > pcib5: irq 19 at device 28.3 on pci0 > pcib5: domain 0 > pcib5: secondary bus 5 > pcib5: subordinate bus 7 > pcib5: I/O decode 0x0-0x0 > pcib5: no prefetched decode > pcib5: could not get PCI interrupt routing table for \\_SB_.PCI0.RP04 -= AE_NOT_FOUND > pci5: on pcib5 > pci5: domain=3D0, physical bus=3D5 >=20 > bge0 (the wired interface is on pcib4: >=20 > bge0: irq 18 at device 0.0 on pci4 > pcib4: bge0 requested unsupported memory range 0-0xffffffff (decoding 0= -0, 0-0) > bge0: 0x10000 bytes of rid 0x10 res 3 failed (0, 0xffffffff). > bge0: couldn't map memory > device_attach: bge0 attach returned 6 >=20 > and wpi0 (the wireless) is on pcib3: >=20 > wpi0: irq 17 at device 0.0 on pci3 > wpi0: Driver Revision 20071127 > pcib3: wpi0 requested unsupported memory range 0-0xffffffff (decoding 0= -0, 0-0) > wpi0: 0x1000 bytes of rid 0x10 res 3 failed (0, 0xffffffff). > wpi0: could not allocate memory resource > device_attach: wpi0 attach returned 6 >=20 > With acpi disabled, the bridges shoiw up like this: > pcib2: irq 17 at device 28.0 on pci0 > pcib2: domain 0 > pcib2: secondary bus 2 > pcib2: subordinate bus 2 > pcib2: I/O decode 0xf000-0xfff > pcib2: no prefetched decode > pci2: on pcib2 > pci2: domain=3D0, physical bus=3D2 > pcib3: irq 16 at device 28.1 on pci0 > pcib3: domain 0 > pcib3: secondary bus 3 > pcib3: subordinate bus 3 > pcib3: I/O decode 0xf000-0xfff > pcib3: memory decode 0xc8200000-0xc82fffff > pcib3: no prefetched decode > pci3: on pcib3 > pci3: domain=3D0, physical bus=3D3 >=20 > pcib4: irq 18 at device 28.2 on pci0 > pcib4: domain 0 > pcib4: secondary bus 4 > pcib4: subordinate bus 4 > pcib4: I/O decode 0xf000-0xfff > pcib4: memory decode 0xc8300000-0xc83fffff > pcib4: no prefetched decode > pci4: on pcib4 > pci4: domain=3D0, physical bus=3D4 >=20 > pcib5: irq 19 at device 28.3 on pci0 > pcib5: domain 0 > pcib5: secondary bus 5 > pcib5: subordinate bus 5 > pcib5: I/O decode 0xf000-0xfff > pcib5: no prefetched decode > pci5: on pcib5 > pci5: domain=3D0, physical bus=3D5 >=20 > bge with acpi disabled: >=20 > bge0: mem 0xc8300000-0xc830ffff irq 17 at device 0.0 on pci4 > bge0: Reserved 0x10000 bytes for rid 0x10 type 3 at 0xc8300000 > bge0: attempting to allocate 1 MSI vectors (8 supported) > msi: routing MSI IRQ 256 to vector 48 > bge0: using IRQ 256 for MSI > miibus0: on bge0 > brgphy0: PHY 1 on miibus0 > brgphy0: OUI 0x000818, model 0x0018, rev. 0 > brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 10= 00baseT-FDX, auto > bge0: bpf attached > bge0: Ethernet address: 00:16:36:54:a9:ae > bge0: [MPSAFE] > bge0: [ITHREAD] >=20 > wpi with acpi disabled: > wpi0: mem 0xc8200000-0xc8200fff irq 17 = at device 0.0 on pci3 > wpi0: Driver Revision 20071127 > wpi0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xc8200000 > wpi0: Hardware Revision (0x1) > wpi0: Regulatory Domain: MoW2 > wpi0: Hardware Type: B > wpi0: Hardware Revision: ? > wpi0: SKU does support 802.11a > wpi0: bpf attached > wpi0: Ethernet address: 00:13:02:3e:d4:ce > wpi0: bpf attached > wpi0: bpf attached > ioapic0: Assigning PCI IRQ 17 to local APIC 0 > ioapic0: routing intpin 17 (PCI IRQ 17) to vector 60 > wpi0: [MPSAFE] > wpi0: [ITHREAD] > wpi0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps > wpi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps > wpi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 2= 4Mbps 36Mbps 48Mbps 54Mbps >=20 > Perhaps I should try to patch my pci too. >=20 > References: > 1) > http://lists.freebsd.org/pipermail/freebsd-mobile/2009-January/011294.h= tml --------------060905050403070305090308 Content-Type: text/plain; name="acpi_ec.c.diff" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline; filename="acpi_ec.c.diff" --- sys/dev/acpica/acpi_ec.c.orig 2009-01-14 16:52:40.000000000 +0200 +++ sys/dev/acpica/acpi_ec.c 2009-01-14 16:58:05.000000000 +0200 @@ -828,6 +828,11 @@ if (need_poll) { static int once; =20 + /* + * XXX Workaround for ACPI CA versions < 20080514 + */ + sleep(1); + if (EcCheckStatus(sc, "pre-check", Event) =3D=3D AE_OK) { if (!once) { device_printf(sc->ec_dev, --------------060905050403070305090308-- --------------enigB647D0FEC8617316E0568C6C Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFJbgIMxJBWvpalMpkRAiv7AJ9XSijgx0H+xlTwehNbiGieK/Ra3gCfQ+5R Ufcg+186AkD/BbSvrNB/tv8= =cP7N -----END PGP SIGNATURE----- --------------enigB647D0FEC8617316E0568C6C-- From owner-freebsd-stable@FreeBSD.ORG Wed Jan 14 15:28:14 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 635BD10656C6 for ; Wed, 14 Jan 2009 15:28:14 +0000 (UTC) (envelope-from krassi@bulinfo.net) Received: from mx.bulinfo.net (mx.bulinfo.net [193.194.156.1]) by mx1.freebsd.org (Postfix) with ESMTP id ADA8D8FC1C for ; Wed, 14 Jan 2009 15:28:12 +0000 (UTC) (envelope-from krassi@bulinfo.net) Received: from localhost (localhost [127.0.0.1]) by mx.bulinfo.net (Postfix) with ESMTP id 3A555C1A5; Wed, 14 Jan 2009 17:28:11 +0200 (EET) Received: from mx.bulinfo.net ([127.0.0.1]) by localhost (mx.bulinfo.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 30531-09; Wed, 14 Jan 2009 17:28:10 +0200 (EET) Received: from [192.168.2.188] (pythia.bulinfo.net [212.72.195.5]) by mx.bulinfo.net (Postfix) with ESMTP id 1D4BDBDF5; Wed, 14 Jan 2009 17:28:10 +0200 (EET) Message-ID: <496E0489.5000900@bulinfo.net> Date: Wed, 14 Jan 2009 17:28:09 +0200 From: Krassimir Slavchev User-Agent: Thunderbird 2.0.0.14 (X11/20080616) MIME-Version: 1.0 To: Torfinn Ingolfsen References: <49633C85.3090507@bulinfo.net> <20090108204311.c9700e91.torfinn.ingolfsen@broadpark.no> <4967045D.30109@bulinfo.net> <20090109202457.19d0fc1a.torfinn.ingolfsen@broadpark.no> <496E0207.8030302@bulinfo.net> In-Reply-To: <496E0207.8030302@bulinfo.net> X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at mx.bulinfo.net Cc: freebsd-stable@freebsd.org, Nate Lawson Subject: Re: ACPI support? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2009 15:28:15 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ooops, sorry sleep() prevents loading of acpi module! Krassimir Slavchev wrote: > Hello, > > Finally I found what is the problem. > > from ACPI CA release notes: > ... > 14 May 2008. Summary of changes for version 20080514: > > 1) ACPI CA Core Subsystem: > > Fixed a problem where GPEs were enabled too early during the ACPICA > initialization. This could lead to "handler not installed" errors on some > machines. Moved GPE enable until after _REG/_STA/_INI methods are run. This > ensures that all operation regions and devices throughout the namespace > have > been initialized before GPEs are enabled. Alexey Starikovskiy, BZ 9916. > ... > > See the attached patch for possible workaround of the problem. > > References: > http://lists.freebsd.org/pipermail/freebsd-acpi/2008-October/005167.html > > Best Regards > > Torfinn Ingolfsen wrote: >> On Fri, 09 Jan 2009 10:01:33 +0200 >> Krassimir Slavchev wrote: >> >>> I have found that thread. >> FWIW, I started a new thread[1] on freebsd-mobile, to update the status >> now after FreeBSD 7.1 has been released >> >>> The problem may be with allocating resources by ACPI PCI-PCI bridge. >>> There is a way to set needed values: >>> http://lists.freebsd.org/pipermail/freebsd-acpi/2008-May/004905.html >> Interesting. For my laptop, it seems that these bridges have the >> problem: >> pcib2: irq 17 at device 28.0 on pci0 >> pcib2: domain 0 >> pcib2: secondary bus 2 >> pcib2: subordinate bus 2 >> pcib2: I/O decode 0x0-0x0 >> pcib2: no prefetched decode >> pci2: on pcib2 >> pci2: domain=0, physical bus=2 >> pcib3: irq 16 at device 28.1 on pci0 >> pcib3: domain 0 >> pcib3: secondary bus 3 >> pcib3: subordinate bus 3 >> pcib3: I/O decode 0x0-0x0 >> pcib3: no prefetched decode >> pci3: on pcib3 >> pci3: domain=0, physical bus=3 >> >> and also these: >> >> pcib4: irq 18 at device 28.2 on pci0 >> pcib4: domain 0 >> pcib4: secondary bus 4 >> pcib4: subordinate bus 4 >> pcib4: I/O decode 0x0-0x0 >> pcib4: no prefetched decode >> pci4: on pcib4 >> pci4: domain=0, physical bus=4 >> >> pcib5: irq 19 at device 28.3 on pci0 >> pcib5: domain 0 >> pcib5: secondary bus 5 >> pcib5: subordinate bus 7 >> pcib5: I/O decode 0x0-0x0 >> pcib5: no prefetched decode >> pcib5: could not get PCI interrupt routing table for \\_SB_.PCI0.RP04 - AE_NOT_FOUND >> pci5: on pcib5 >> pci5: domain=0, physical bus=5 >> >> bge0 (the wired interface is on pcib4: >> >> bge0: irq 18 at device 0.0 on pci4 >> pcib4: bge0 requested unsupported memory range 0-0xffffffff (decoding 0-0, 0-0) >> bge0: 0x10000 bytes of rid 0x10 res 3 failed (0, 0xffffffff). >> bge0: couldn't map memory >> device_attach: bge0 attach returned 6 >> >> and wpi0 (the wireless) is on pcib3: >> >> wpi0: irq 17 at device 0.0 on pci3 >> wpi0: Driver Revision 20071127 >> pcib3: wpi0 requested unsupported memory range 0-0xffffffff (decoding 0-0, 0-0) >> wpi0: 0x1000 bytes of rid 0x10 res 3 failed (0, 0xffffffff). >> wpi0: could not allocate memory resource >> device_attach: wpi0 attach returned 6 >> >> With acpi disabled, the bridges shoiw up like this: >> pcib2: irq 17 at device 28.0 on pci0 >> pcib2: domain 0 >> pcib2: secondary bus 2 >> pcib2: subordinate bus 2 >> pcib2: I/O decode 0xf000-0xfff >> pcib2: no prefetched decode >> pci2: on pcib2 >> pci2: domain=0, physical bus=2 >> pcib3: irq 16 at device 28.1 on pci0 >> pcib3: domain 0 >> pcib3: secondary bus 3 >> pcib3: subordinate bus 3 >> pcib3: I/O decode 0xf000-0xfff >> pcib3: memory decode 0xc8200000-0xc82fffff >> pcib3: no prefetched decode >> pci3: on pcib3 >> pci3: domain=0, physical bus=3 >> >> pcib4: irq 18 at device 28.2 on pci0 >> pcib4: domain 0 >> pcib4: secondary bus 4 >> pcib4: subordinate bus 4 >> pcib4: I/O decode 0xf000-0xfff >> pcib4: memory decode 0xc8300000-0xc83fffff >> pcib4: no prefetched decode >> pci4: on pcib4 >> pci4: domain=0, physical bus=4 >> >> pcib5: irq 19 at device 28.3 on pci0 >> pcib5: domain 0 >> pcib5: secondary bus 5 >> pcib5: subordinate bus 5 >> pcib5: I/O decode 0xf000-0xfff >> pcib5: no prefetched decode >> pci5: on pcib5 >> pci5: domain=0, physical bus=5 >> >> bge with acpi disabled: >> >> bge0: mem 0xc8300000-0xc830ffff irq 17 at device 0.0 on pci4 >> bge0: Reserved 0x10000 bytes for rid 0x10 type 3 at 0xc8300000 >> bge0: attempting to allocate 1 MSI vectors (8 supported) >> msi: routing MSI IRQ 256 to vector 48 >> bge0: using IRQ 256 for MSI >> miibus0: on bge0 >> brgphy0: PHY 1 on miibus0 >> brgphy0: OUI 0x000818, model 0x0018, rev. 0 >> brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto >> bge0: bpf attached >> bge0: Ethernet address: 00:16:36:54:a9:ae >> bge0: [MPSAFE] >> bge0: [ITHREAD] >> >> wpi with acpi disabled: >> wpi0: mem 0xc8200000-0xc8200fff irq 17 at device 0.0 on pci3 >> wpi0: Driver Revision 20071127 >> wpi0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xc8200000 >> wpi0: Hardware Revision (0x1) >> wpi0: Regulatory Domain: MoW2 >> wpi0: Hardware Type: B >> wpi0: Hardware Revision: ? >> wpi0: SKU does support 802.11a >> wpi0: bpf attached >> wpi0: Ethernet address: 00:13:02:3e:d4:ce >> wpi0: bpf attached >> wpi0: bpf attached >> ioapic0: Assigning PCI IRQ 17 to local APIC 0 >> ioapic0: routing intpin 17 (PCI IRQ 17) to vector 60 >> wpi0: [MPSAFE] >> wpi0: [ITHREAD] >> wpi0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps >> wpi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps >> wpi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps >> >> Perhaps I should try to patch my pci too. >> >> References: >> 1) >> http://lists.freebsd.org/pipermail/freebsd-mobile/2009-January/011294.html > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFJbgSIxJBWvpalMpkRArjlAJ9NDo3GDHAoT6DBQ/UBS5PnwQL6EQCfSMng 4HL+qQCZUymg3tSOi8/CNyU= =eMlS -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Wed Jan 14 15:28:56 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 00E8A1065694 for ; Wed, 14 Jan 2009 15:28:56 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 1D10C8FC1B for ; Wed, 14 Jan 2009 15:28:54 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id RAA28906; Wed, 14 Jan 2009 17:28:47 +0200 (EET) (envelope-from avg@icyb.net.ua) Message-ID: <496E04AD.7010607@icyb.net.ua> Date: Wed, 14 Jan 2009 17:28:45 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.18 (X11/20081124) MIME-Version: 1.0 To: Jorge Biquez References: <200901141438.n0EEc0ww071823@mail.icsmx.com> In-Reply-To: <200901141438.n0EEc0ww071823@mail.icsmx.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: Simple? Hardware 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: Wed, 14 Jan 2009 15:28:56 -0000 on 14/01/2009 16:34 Jorge Biquez said the following: > b) If is possible to "clone" the same installation to a new faster disk > (like a sata 250GB). I know I can install a /.x version and for sure > will work but here the idea is to have things running as usual without > problems. This installation is very stable and secure and has been with > us for years.... we would like to keep it working for more years.... :=) Somewhat tangential - are you sure that a new faster disk would really perform faster on that old PIII system? Even if you use an expansion card (which itself might require updates to kernel, ata driver at least), PCI bus speed will stay limited to the same old value. -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Wed Jan 14 15:29:34 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E606C1065675; Wed, 14 Jan 2009 15:29:34 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.terabit.net.ua (mail.terabit.net.ua [195.137.202.147]) by mx1.freebsd.org (Postfix) with ESMTP id 881F58FC21; Wed, 14 Jan 2009 15:29:34 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from skuns.zoral.com.ua ([91.193.166.194] helo=mail.zoral.com.ua) by mail.terabit.net.ua with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1LN7gS-0005wa-Lc; Wed, 14 Jan 2009 17:29:32 +0200 Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id n0EFTTOr005206 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 14 Jan 2009 17:29:29 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id n0EFTT7D070851; Wed, 14 Jan 2009 17:29:29 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id n0EFTTkS070850; Wed, 14 Jan 2009 17:29:29 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 14 Jan 2009 17:29:29 +0200 From: Kostik Belousov To: freebsd-stable@freebsd.org Message-ID: <20090114152929.GO2247@deviant.kiev.zoral.com.ua> References: <75a268720901090839q406ed8f3g8d09e83a9a452415@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="oJAv8lSwuaQsYd0G" Content-Disposition: inline In-Reply-To: <75a268720901090839q406ed8f3g8d09e83a9a452415@mail.gmail.com> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: ClamAV version 0.94.2, clamav-milter version 0.94.2 on skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua X-Virus-Scanned: mail.terabit.net.ua 1LN7gS-0005wa-Lc 67d0892b47241b544b90df5dbcb15952 X-Terabit: YES Cc: Omer Faruk Sen , freebsd-hackers@freebsd.org Subject: Re: kernel dump with 7.1-RELEASE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2009 15:29:36 -0000 --oJAv8lSwuaQsYd0G Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 09, 2009 at 06:39:53PM +0200, Omer Faruk Sen wrote: > Hi, >=20 > I am having kernel dump with FreeBSD 7.1: >=20 > Here is crashinfo output of it (Actually i don't know the state of > crashinfo in Fbsd 7.1) >=20 > 7.1-RELEASE FreeBSD 7.1-RELEASE #0: Thu Jan 1 08:58:24 UTC 2009 > root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 >=20 >=20 >=20 > panic: semexit - semid not allocated >=20 > GNU gdb 6.1.1 [FreeBSD] > Copyright 2004 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you = are > welcome to change it and/or distribute copies of it under certain conditi= ons. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for detail= s. > This GDB was configured as "amd64-marcel-freebsd"... >=20 > Unread portion of the kernel message buffer: > Physical memory: 8173 MB > Dumping 437 MB: 422 406 390 374 358 342 326 310 294 278 262 246 230 > 214 198 182 166 150 134 118 102 86 70 54 38 22 6 >=20 > #0 doadump () at pcpu.h:195 > 195 pcpu.h: No such file or directory. > in pcpu.h > (kgdb) #0 doadump () at pcpu.h:195 > #1 0x0000000000000004 in ?? () > #2 0xffffffff804b4ce9 in boot (howto=3D260) > at /usr/src/sys/kern/kern_shutdown.c:418 > #3 0xffffffff804b50f2 in panic (fmt=3D0x104
) > at /usr/src/sys/kern/kern_shutdown.c:574 > #4 0xffffffff804f846d in semexit_myhook (arg=3DVariable "arg" is not ava= ilable. > ) > at /usr/src/sys/kern/sysv_sem.c:1328 > #5 0xffffffff80490dbc in exit1 (td=3D0xffffff000995f370, rv=3D0) > at /usr/src/sys/kern/kern_exit.c:244 > #6 0xffffffff8049239e in sys_exit (td=3DVariable "td" is not available. > ) at /usr/src/sys/kern/kern_exit.c:109 > #7 0xffffffff8078a7c7 in syscall (frame=3D0xffffffffb0d4ac80) > at /usr/src/sys/amd64/amd64/trap.c:907 > #8 0xffffffff8077088b in Xfast_syscall () > at /usr/src/sys/amd64/amd64/exception.S:330 > #9 0x0000000800a2a30c in ?? () > Previous frame inner to this frame (corrupt stack?) > (kgdb) The change that is believed to fix the reported panic is committed as r187223 to HEAD. MFC is set to 1 month, because, mmm, because. The MFC requires mostly mechanical changes of the MAC hook names. --oJAv8lSwuaQsYd0G Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkluBNgACgkQC3+MBN1Mb4i13wCgz0ReCvIsK93lCuIZhj+Hgokr UugAnjcstSMmRib2kRVNNVGYThWf3+dP =mza0 -----END PGP SIGNATURE----- --oJAv8lSwuaQsYd0G-- From owner-freebsd-stable@FreeBSD.ORG Wed Jan 14 15:42:32 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3184F1065704 for ; Wed, 14 Jan 2009 15:42:32 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from constantine.ticketswitch.com (constantine.ticketswitch.com [IPv6:2002:57e0:1d4e:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id C1B3D8FC0C for ; Wed, 14 Jan 2009 15:42:31 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from dilbert.rattatosk ([10.64.50.6] helo=dilbert.ticketswitch.com) by constantine.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LN7su-000Cgg-K9; Wed, 14 Jan 2009 15:42:24 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LN7su-0000ga-Ie; Wed, 14 Jan 2009 15:42:24 +0000 To: freebsd-stable@freebsd.org, jbiquez@icsmx.com In-Reply-To: <200901141438.n0EEc0ww071823@mail.icsmx.com> Message-Id: From: Pete French Date: Wed, 14 Jan 2009 15:42:24 +0000 Cc: Subject: Re: Simple? Hardware 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: Wed, 14 Jan 2009 15:42:34 -0000 > a) Only put the disk in a new machine at least a double core with 2GB > of RAM. My guess is that could boot with a few problems on > hardware.... what do you think? That should work fine - I have moved discs between machines with no problems. > b) If is possible to "clone" the same installation to a new faster > disk (like a sata 250GB). I know I can install a /.x version and for Yes, this is also do-able. I always do this via a 3rd bootable drive or partition. have the old and the new drive attached to a system, boot from the 3rd and use 'cpdup' (which is in ports) to copy everythong from / downwards from the old drive to the new. The reason I do this from a 3rd drive is to avid copying a running system. You neeed to mark the new drive as bootable using disklabel, and possibly make some changes to fstab if the drive name has changed, but it will then boot as a clone of the old one. -pete. From owner-freebsd-stable@FreeBSD.ORG Wed Jan 14 15:50:53 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3AD1D10658BA for ; Wed, 14 Jan 2009 15:50:53 +0000 (UTC) (envelope-from erikt@midgard.homeip.net) Received: from ch-smtp02.sth.basefarm.net (ch-smtp02.sth.basefarm.net [80.76.149.213]) by mx1.freebsd.org (Postfix) with ESMTP id E69728FC0A for ; Wed, 14 Jan 2009 15:50:52 +0000 (UTC) (envelope-from erikt@midgard.homeip.net) Received: from c83-255-48-78.bredband.comhem.se ([83.255.48.78]:49266 helo=falcon.midgard.homeip.net) by ch-smtp02.sth.basefarm.net with esmtp (Exim 4.68) (envelope-from ) id 1LN7mN-0003vQ-8Z for freebsd-stable@freebsd.org; Wed, 14 Jan 2009 16:35:39 +0100 Received: (qmail 7554 invoked from network); 14 Jan 2009 16:35:36 +0100 Received: from owl.midgard.homeip.net (10.1.5.7) by falcon.midgard.homeip.net with ESMTP; 14 Jan 2009 16:35:36 +0100 Received: (qmail 23044 invoked by uid 1001); 14 Jan 2009 16:35:36 +0100 Date: Wed, 14 Jan 2009 16:35:36 +0100 From: Erik Trulsson To: Andriy Gapon Message-ID: <20090114153536.GA23011@owl.midgard.homeip.net> References: <200901141438.n0EEc0ww071823@mail.icsmx.com> <496E04AD.7010607@icyb.net.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <496E04AD.7010607@icyb.net.ua> User-Agent: Mutt/1.5.18 (2008-05-17) X-Originating-IP: 83.255.48.78 X-Scan-Result: No virus found in message 1LN7mN-0003vQ-8Z. X-Scan-Signature: ch-smtp02.sth.basefarm.net 1LN7mN-0003vQ-8Z 3844372c0e541aac38cd9c29bd03c380 Cc: freebsd-stable@freebsd.org Subject: Re: Simple? Hardware 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: Wed, 14 Jan 2009 15:50:54 -0000 On Wed, Jan 14, 2009 at 05:28:45PM +0200, Andriy Gapon wrote: > on 14/01/2009 16:34 Jorge Biquez said the following: > > b) If is possible to "clone" the same installation to a new faster disk > > (like a sata 250GB). I know I can install a /.x version and for sure > > will work but here the idea is to have things running as usual without > > problems. This installation is very stable and secure and has been with > > us for years.... we would like to keep it working for more years.... :=) > > Somewhat tangential - are you sure that a new faster disk would really > perform faster on that old PIII system? Even if you use an expansion > card (which itself might require updates to kernel, ata driver at > least), PCI bus speed will stay limited to the same old value. The PCI bus should still be much faster than his old disk, so there is almost certainly room for improvement. (The latest generation of harddisk, on the other hand, are fast enough that a standard 32-bit/33MHz PCI-bus can actually be a bottle-neck.) -- Erik Trulsson ertr1013@student.uu.se From owner-freebsd-stable@FreeBSD.ORG Wed Jan 14 17:00:16 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7D6AF1065672 for ; Wed, 14 Jan 2009 17:00:16 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id A8AD58FC16 for ; Wed, 14 Jan 2009 17:00:14 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost1.sentex.ca (8.14.3/8.14.3) with ESMTP id n0EH0CEY012014; Wed, 14 Jan 2009 12:00:12 -0500 (EST) (envelope-from mike@sentex.net) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.8/8.13.3) with ESMTP id n0EH0CY4065716 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 14 Jan 2009 12:00:12 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <200901141700.n0EH0CY4065716@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Wed, 14 Jan 2009 12:00:11 -0500 To: Jorge Biquez , freebsd-stable@freebsd.org From: Mike Tancsa In-Reply-To: <200901141438.n0EEc0ww071823@mail.icsmx.com> References: <200901141438.n0EEc0ww071823@mail.icsmx.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18 Cc: Subject: Re: Simple? Hardware 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: Wed, 14 Jan 2009 17:00:18 -0000 At 09:34 AM 1/14/2009, Jorge Biquez wrote: >Hello all. > >I have a 4.11 Stable version that has been working without problems >in the last years. We do not need nothing else for the moment but we >are looking to have more speed. It has been running under a double >Pentium III processor with 512MB of ram and it has a disk of 40GB. > >I was wondering of it is possible to do 2 things. > >a) Only put the disk in a new machine at least a double core with >2GB of RAM. My guess is that could boot with a few problems on >hardware.... what do you think? > >b) If is possible to "clone" the same installation to a new faster >disk (like a sata 250GB). I know I can install a /.x version and for >sure will work but here the idea is to have things running as usual >without problems. This installation is very stable and secure and >has been with us for years.... we would like to keep it working for >more years.... :=) > >on b). Is there a simple way to do it? Copying the disk is easy enough. However, 4.11 is VERY old and doesnt necessarily support the latest in hardware or even recent hardware. e.g. it might not recognize the SATA controller, or might not work well with it. Cloning the disk is easy. dump | restore will work well. Google for the terms "copy disk dump restore freebsd" and you will find lots of HOWTO docs What I suggest is if you really cant start fresh with 7.1R, install a fresh copy of 4.11 onto the new hardware and make sure it works. Then try duplicating the disk via dump and restore. ---Mike From owner-freebsd-stable@FreeBSD.ORG Wed Jan 14 17:22:13 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E9A78106574E for ; Wed, 14 Jan 2009 17:22:13 +0000 (UTC) (envelope-from kometen@gmail.com) Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.188]) by mx1.freebsd.org (Postfix) with ESMTP id 764778FC18 for ; Wed, 14 Jan 2009 17:22:13 +0000 (UTC) (envelope-from kometen@gmail.com) Received: by fk-out-0910.google.com with SMTP id k31so404171fkk.11 for ; Wed, 14 Jan 2009 09:22:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=wbi6TH03fPpgspqtY2+sz2JMCw2/x9//cWvsxsqFpi0=; b=bN2oQoZp9IyuOWoisLWtzO+isWjqfCbCNU7tiGWfCbpQeNn7+u0IwCUPD2n27u3wis wkLr9BFDBnqf6db01p3PTJvghZkb0Rkeg4nKMijYGW2iDx5f6PyfXXva+WptJm9G81RK YgNiRaEGiSncNGQWnsSPxN1gIjToaoTYYcvGw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=xuEEHi38FhCCSgMGHToX02h8ljZWoFLKikPAj36Ene6vlecot4Nj7Hwmq/xwofmcRy ao16+p5/cpylM42sJrxmV1fvUHnQrrHaA8WDN9yxSjLFaCRK1VE2WCgT2hLU/3Jy1ZiG nBA85tUkSGZI9p8hPjT7GPYfGdPJxyBjMSTWY= Received: by 10.103.119.19 with SMTP id w19mr177194mum.80.1231953732408; Wed, 14 Jan 2009 09:22:12 -0800 (PST) Received: by 10.103.198.19 with HTTP; Wed, 14 Jan 2009 09:22:12 -0800 (PST) Message-ID: Date: Wed, 14 Jan 2009 18:22:12 +0100 From: "Claus Guttesen" To: "Pete French" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Cc: freebsd-stable@freebsd.org, naliyev@ultel.az Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2009 17:22:14 -0000 > my problem in with others under the asusmption that it's all the same. This > is onbiously pretty rare - out of 24 of the HP servers the problems only crops > up on 4 of them. But there is nothing dfferent about those 4. Could it be different bios/firmware on the hp-servers? Mr. Aliyev was unable to install 7.1 release on amd64 on a DL380 G5. -- regards Claus When lenity and cruelty play for a kingdom, the gentler gamester is the soonest winner. Shakespeare From owner-freebsd-stable@FreeBSD.ORG Wed Jan 14 18:00:23 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 296BD10656FA for ; Wed, 14 Jan 2009 18:00:23 +0000 (UTC) (envelope-from v.haisman@sh.cvut.cz) Received: from service1.sh.cvut.cz (service1.sh.cvut.cz [IPv6:2001:718:2::214]) by mx1.freebsd.org (Postfix) with ESMTP id AA2CE8FC1A for ; Wed, 14 Jan 2009 18:00:22 +0000 (UTC) (envelope-from v.haisman@sh.cvut.cz) Received: from localhost (localhost [127.0.0.1]) by service1.sh.cvut.cz (Postfix) with ESMTP id 014FB123D98; Wed, 14 Jan 2009 19:00:22 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at service1.sh.cvut.cz X-Spam-Score: -87.683 X-Spam-Level: X-Spam-Status: No, score=-87.683 tagged_above=-255 required=5 tests=[ALL_TRUSTED=-1.44, AWL=14.757, CRM114_HAM_00=, SMTPAUTH_SHDOMAIN=-100] Received: from service1.sh.cvut.cz ([127.0.0.1]) by localhost (service1.sh.cvut.cz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZsgAMuPj6fQd; Wed, 14 Jan 2009 19:00:14 +0100 (CET) Received: from [192.168.1.2] (35.201.broadband4.iol.cz [85.71.201.35]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: v.haisman@sh.cvut.cz) by service1.sh.cvut.cz (Postfix) with ESMTP id 1B09D12386C; Wed, 14 Jan 2009 19:00:14 +0100 (CET) Message-ID: <496E282A.5070004@sh.cvut.cz> Date: Wed, 14 Jan 2009 19:00:10 +0100 From: =?UTF-8?B?VsOhY2xhdiBIYWlzbWFu?= User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: freebsd-stable@freebsd.org X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Mounting / using /dev/ufs/name X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2009 18:00:26 -0000 Hi, I tried to mount root slice using the device nodes provided in /dev/ufs directory. It works fine for other slices but not for the root slice. If I try it I get prompt asking for root slice at boot time. It this not possible at all or am I doing something wrong? -- VH From owner-freebsd-stable@FreeBSD.ORG Wed Jan 14 18:11:33 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DF7351065726 for ; Wed, 14 Jan 2009 18:11:33 +0000 (UTC) (envelope-from frank@exit.com) Received: from tinker.exit.com (tinker.exit.com [IPv6:2001:470:80f4:0:2e0:81ff:fe2b:acbc]) by mx1.freebsd.org (Postfix) with ESMTP id 968838FC24 for ; Wed, 14 Jan 2009 18:11:33 +0000 (UTC) (envelope-from frank@exit.com) Received: from jill.exit.com (jill.exit.com [IPv6:2001:470:80f4:0:2e0:81ff:fe33:7e9a]) by tinker.exit.com (8.14.2/8.14.2) with ESMTP id n0EIBWeL038179; Wed, 14 Jan 2009 10:11:32 -0800 (PST) (envelope-from frank@exit.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=exit.com; s=tinker; t=1231956692; bh=jSZisOx5zwlceF7P0W6k4qPJNYOC00GUdl7AFegVXDE=; h=Subject:From:Reply-To:To:Cc:In-Reply-To:References:Content-Type: Content-Transfer-Encoding:Date:Message-Id:Mime-Version; b=L6uRXVAA Jy3t4dcAiw8EAx1DUhBH/NFTYDsx2+/cMCq9iMtRECJA/BeRKcoTzPLi2PmaD8LXscH 2P7g8upqN1uwvsEqTa9YBe34sNeTK71vmJYyJUqFYjrmRHWk74EpqkDCKCzxbqeZM9Y bW6HqUHrSKx5/tnW1i5JDD4arTkYo= Received: from jill.exit.com (localhost [127.0.0.1]) by jill.exit.com (8.14.3/8.14.2) with ESMTP id n0EIBWkJ081041; Wed, 14 Jan 2009 10:11:32 -0800 (PST) (envelope-from frank@exit.com) Received: (from frank@localhost) by jill.exit.com (8.14.3/8.14.3/Submit) id n0EIBWv2081040; Wed, 14 Jan 2009 10:11:32 -0800 (PST) (envelope-from frank@exit.com) X-Authentication-Warning: jill.exit.com: frank set sender to frank@exit.com using -f From: Frank Mayhar To: =?ISO-8859-1?Q?V=E1clav?= Haisman In-Reply-To: <496E282A.5070004@sh.cvut.cz> References: <496E282A.5070004@sh.cvut.cz> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Organization: Exit Consulting Date: Wed, 14 Jan 2009 10:11:32 -0800 Message-Id: <1231956692.80624.1.camel@jill.exit.com> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 FreeBSD GNOME Team Port X-Virus-Scanned: ClamAV 0.93.3/8864/Wed Jan 14 04:50:32 2009 on tinker.exit.com X-Virus-Status: Clean Cc: freebsd-stable@freebsd.org Subject: Re: Mounting / using /dev/ufs/name X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: frank@exit.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2009 18:11:34 -0000 On Wed, 2009-01-14 at 19:00 +0100, V=E1clav Haisman wrote: > Hi, > I tried to mount root slice using the device nodes provided in /dev/ufs > directory. It works fine for other slices but not for the root slice. If = I > try it I get prompt asking for root slice at boot time. It this not possi= ble > at all or am I doing something wrong? If you don't have geom_label built into the kernel it's a chicken-egg problem. Even if you do, early startup almost certainly doesn't have devfs available yet. --=20 Frank Mayhar frank@exit.com http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/ http://www.zazzle.com/fmayhar* From owner-freebsd-stable@FreeBSD.ORG Wed Jan 14 19:17:32 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DBCC91065673 for ; Wed, 14 Jan 2009 19:17:32 +0000 (UTC) (envelope-from redcrash@gmail.com) Received: from mail-gx0-f21.google.com (mail-gx0-f21.google.com [209.85.217.21]) by mx1.freebsd.org (Postfix) with ESMTP id 7555E8FC13 for ; Wed, 14 Jan 2009 19:17:32 +0000 (UTC) (envelope-from redcrash@gmail.com) Received: by gxk14 with SMTP id 14so762881gxk.19 for ; Wed, 14 Jan 2009 11:17:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=N9pkZNzB2lK+/XHaWeyiekGYsc8Ymf+Yvuabbcmnbb4=; b=mvwaqttZKdP/7fDxojGXTQ/tUtnkKMTPez0zYhqJUuMUl+dnFo18PCbh7zDgbMYFms in3WP9k58W0ltdLZzHTzM9rbe4BDRR+nHVnaIx6GbwMi6Niv0fRfvDm7uI5SgVO/234Y EuCKRzJIitMEGO/8KIZCVIWN5TTAg1r61M/lc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=VfQa9JPMCwpWp15s7QHYJPiEUqWhgPufwY8ZU5nVilMYtSEUEoS+6u7wfzfEO5CJQU VjINPIELUM3mYjBaAZiDPDj/BuaGMo2ExNXXvwJ8FZi05xTDi/VnkvWAfPydSSnNoBfp /JDfdMGOWgIMtv28b/K1YFz5B/IjaWVNRKD1U= Received: by 10.142.255.14 with SMTP id c14mr144684wfi.91.1231960651395; Wed, 14 Jan 2009 11:17:31 -0800 (PST) Received: by 10.142.239.14 with HTTP; Wed, 14 Jan 2009 11:17:31 -0800 (PST) Message-ID: Date: Wed, 14 Jan 2009 20:17:31 +0100 From: "Harald Servat" To: Ganbold In-Reply-To: <496D4B60.5050807@micom.mng.net> MIME-Version: 1.0 References: <496D41A3.2040306@micom.mng.net> <496D4B60.5050807@micom.mng.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: lenovo t400 does not start 7.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2009 19:17:33 -0000 On Wed, Jan 14, 2009 at 3:18 AM, Ganbold wrote: > Ganbold wrote: > >> Harald Servat wrote: >> >>> Hello, >>> >>> I downloaded FreeBSD 7.1 (DVD iso image) for amd64 architecture (with >>> correct SHA256 checksum), but I'm unable to start the system (Lenovo >>> T400). >>> >>> The boot process starts fine, the BTX messages appear, the 7-option menu >>> also appears, but when I hit enter (or when I choose start without ACPI >>> or >>> start in safe mode) the \ symbols starts spinning for a while and then >>> freezes. >>> >>> I also tried with the 7.1-amd64-CD1, 7.1-i386-CD1 and a snapshot of >>> 8.0-CURRENT dated from December. And the result is the same for all of >>> them. >>> >>> Does anyone have any idea on what can be happening? Or at least, how can >>> I >>> gather more information about this issue? >>> >>> >> >> Please try setting "Integrated Graphics" or "Switchable Graphics" mode on >> Display setting in >> BIOS. AFAICT it is known issue and FreeBSD doesn't boot when set to >> Discrete Graphics in BIOS. >> > > Or maybe it boots but nothing shows on screen. > > Ganbold > > Ganbold, you were right. I've switched the BIOS>Display into Switchable graphics and now the system does not freeze while the backslash symbol is spinning. It occurs the same as you described in the -current list (see http://lists.freebsd.org/pipermail/freebsd-current/2009-January/001941.html) However, let me tell you what I've found now (I tried these options in the following order). ** a) I've started with option 2 (ACPI disabled) because I read somewhere that FreeBSD did not support Lenovo T400's ACPI. The system boots and freezes after showing (something related with Timecounters) md0: Preloaded image 4194304 bytes at Trying to mount root from ufs:/dev/md0 b) When I chose option Safe mode (3, IIRC) Happens the same as a) c) I've tried with verbose logging (option 5, I think) The initialization dumps a lot of debugging information and after some time, it brings me the "Choosing region" screen. I didn't get further because I will not install the system right now (I have to prepare the backups first ;) ) I tried to use ScrollLock + RePag to look for the conflicting line found in a) or any suspicious message but it didn't work. I also tried with an holographic shell and the livefs without luck. d) I also tried option 1 (default boot) -- just in order to check. It also worked. Like c) but without debugging information. ** So, right now, it seems that the system allows me to begin the installation of FreeBSD 7.1 amd64 on the T400 but I'm scared due to the lack of functionality of options 2 and 3. This behavior is not normal, is it? Any thoughts about this? Thank you very much! From owner-freebsd-stable@FreeBSD.ORG Wed Jan 14 20:16:37 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 30ADA106564A for ; Wed, 14 Jan 2009 20:16:37 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mail.bsdforen.de (bsdforen.de [212.204.60.79]) by mx1.freebsd.org (Postfix) with ESMTP id E1D448FC19 for ; Wed, 14 Jan 2009 20:16:36 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mobileKamikaze.norad (unknown [92.116.153.250]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.bsdforen.de (Postfix) with ESMTP id E5D238A00D3; Wed, 14 Jan 2009 21:16:06 +0100 (CET) Message-ID: <496E47FA.1080103@bsdforen.de> Date: Wed, 14 Jan 2009 21:15:54 +0100 From: Dominic Fandrey User-Agent: Thunderbird 2.0.0.19 (X11/20090110) MIME-Version: 1.0 To: frank@exit.com References: <496E282A.5070004@sh.cvut.cz> <1231956692.80624.1.camel@jill.exit.com> In-Reply-To: <1231956692.80624.1.camel@jill.exit.com> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: =?UTF-8?B?VsOhY2xhdiBIYWlzbWFu?= , freebsd-stable@freebsd.org Subject: Re: Mounting / using /dev/ufs/name X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2009 20:16:37 -0000 Frank Mayhar wrote: > On Wed, 2009-01-14 at 19:00 +0100, Václav Haisman wrote: >> Hi, >> I tried to mount root slice using the device nodes provided in /dev/ufs >> directory. It works fine for other slices but not for the root slice. If I >> try it I get prompt asking for root slice at boot time. It this not possible >> at all or am I doing something wrong? > > If you don't have geom_label built into the kernel it's a chicken-egg > problem. Even if you do, early startup almost certainly doesn't have > devfs available yet. # mount /dev/ufs/2root on / (ufs, local) devfs on /dev (devfs, local) /dev/ufs/2tmp on /tmp (ufs, local, soft-updates) /dev/ufs/2usr on /usr (ufs, local, soft-updates) /dev/ufs/2var on /var (ufs, local, soft-updates) /usr/home/root on /root (nullfs, local) pid1026@mobileKamikaze:/var/run/automounter.amd.mnt on /var/run/automounter.amd.mnt (nfs) /dev/fuse0 on /var/run/automounter.mnt/ntfs/2vault (fusefs, local, noatime, synchronous Try to add geom_label_load="YES" to your /boot/loader.conf file. From owner-freebsd-stable@FreeBSD.ORG Wed Jan 14 20:47:56 2009 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 093551065686 for ; Wed, 14 Jan 2009 20:47:56 +0000 (UTC) (envelope-from dudu.meyer@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.171]) by mx1.freebsd.org (Postfix) with ESMTP id D41EF8FC16 for ; Wed, 14 Jan 2009 20:47:55 +0000 (UTC) (envelope-from dudu.meyer@gmail.com) Received: by wf-out-1314.google.com with SMTP id 24so774598wfg.7 for ; Wed, 14 Jan 2009 12:47:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=dSAZrJVvhZCb5w2JQmZjG5hl1LsjMzcj4HZC/iYCiZU=; b=VMWi/3NuBVlQLqN3jnUBPtSohMT6YG4qg9TD8zQe+VT8HNaNt6XGZpyKQZ0jbab6Dt 6kqzQ0fPwE6kR32HMqAjQ1fY7YH+hA2qTPE58cJMEiIcP7UNAPhrjgmBVy04Z1ZcRYaG LMtBxOT4sBNGaGPEOG1fvegzmRgZp97LPac+s= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=j9PLRVHcatWYFoEOXvtH2vhc+fpfspFIXZ4kfbiWhpheWnBkBCQ1umS8q/A4ssa9Fm RNuyy7E/aaECLCZkWCcyxlbCBTKs2NitGK6GtwyXda7FpucOQAUqPDNSLOhjTMzScEzp VwFdPIC2l1yY9KnldxYBQtkd4N9JrbwJFDJkY= Received: by 10.142.48.14 with SMTP id v14mr162632wfv.138.1231964585761; Wed, 14 Jan 2009 12:23:05 -0800 (PST) Received: by 10.142.201.8 with HTTP; Wed, 14 Jan 2009 12:23:05 -0800 (PST) Message-ID: Date: Wed, 14 Jan 2009 18:23:05 -0200 From: "Eduardo Meyer" To: stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: Multiple Routing Tables (FIB) + IPFW problem (basic understading wont work) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2009 20:47:56 -0000 Hello, I am trying the new FIB stuff on -STABLE with IPFW, I made many tests and it did not work as I expected. Quick testing: # lynx -dump http://www.whatismyip.org 200.165.75.10 # setfib -1 lynx -dump http://www.whatismyip.org 189.52.141.2 # setfib -2 lynx -dump http://www.whatismyip.org 201.91.92.154 # ipfw -q flush # ipfw add 1 setfib 1 all from any to any 00001 setfib 1 ip from any to any # lynx -dump http://www.whatismyip.org 200.165.75.10 Check for counters: # ipfw -q add 2 allow all from any to any fib 1 # ipfw show 00001 388599 139653215 setfib 1 ip from any to any 00002 4253 2221474 allow ip from any to any fib 1 65535 2419650 983279227 allow ip from any to any # lynx -dump http://www.whatismyip.org 200.165.75.10 # setfib -1 lynx -dump http://www.whatismyip.org 189.52.141.2 Whats wrong with my concepts? -- =========== Eduardo Meyer pessoal: dudu.meyer@gmail.com profissional: ddm.farmaciap@saude.gov.br From owner-freebsd-stable@FreeBSD.ORG Wed Jan 14 22:45:44 2009 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 19A2E1065670 for ; Wed, 14 Jan 2009 22:45:44 +0000 (UTC) (envelope-from lslaw@israelinsurancelaw.com) Received: from server.loads.co.il (loads.co.il [212.150.184.30]) by mx1.freebsd.org (Postfix) with ESMTP id 5D8A48FC1B for ; Wed, 14 Jan 2009 22:45:43 +0000 (UTC) (envelope-from lslaw@israelinsurancelaw.com) Received: from apache by server.loads.co.il with local (Exim 4.60) (envelope-from ) id 1LNDip-0003Fx-1D for stable@freebsd.org; Wed, 14 Jan 2009 23:56:23 +0200 To: stable@freebsd.org X-PHP-Script: israelinsurancelaw.com/demosite/Mail.php for 84.22.44.133 From: Paypal Billing Departament Content-Transfer-Encoding: 8bit Message-Id: Date: Wed, 14 Jan 2009 23:56:23 +0200 MIME-Version: 1.0 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Please Restore Your Account Access X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2009 22:45:44 -0000 PayPal [] [] Notification of Limited Account Access Dear PayPal valued member , As part of our security measures, we regularly screen activity in the PayPal system. We recently contacted you after noticing an issue on your account.We requested information from you for the following reason: We recently received a report of unauthorized credit card use associated with this account. As a precaution, we have limited access to your PayPal account in order to protect against future unauthorized transactions. Case ID Number: PP-430-506-971 In accordance with PayPal's User Agreement, your account access will remain limited until the issue has been resolved. Unfortunately, if access to your account remains limited for an extended period of time, it may result in further limitations or eventual account closure. We encourage you to follow our verification procedure as soon as possible to help avoid this. [1]Click here to login and restore your account access Once you log in, you will be provided with steps to restore your account access. We appreciate your understanding as we work to ensure account safety. This is a final reminder to [2]log in to PayPal as soon as possible. We thank you for your prompt attention to this matter. Please understand that this is a security measure intended to help protect you and your account. We apologize for any inconvenience. Sincerely, PayPal Account Review Department PayPal Email ID PP638 _________________________________________________________________ Please do not reply to this e-mail. Mail sent to this address cannot be answered. For assistance, [3]log in to your PayPal account and choose the "Help" link in the footer of any page. [] PayPal Email ID PP638 [] Protect Your Account Info Make sure you never provide your password to fraudulent websites To safely and securely access the PayPal website or your account, open a new web browser (e.g. Internet Explorer or Netscape) and type in the PayPal URL (https://www.paypal.com/row/) to be sure you are on the real PayPal site. PayPal will never ask you to enter your password in an email. For more information on protecting yourself from fraud, please review our Security Tips at [4]https://www.paypal.com/row/securitytips [] Protect Your Password You should never give your PayPal password to anyone, including PayPal employees. [] References 1. http://paypal.billing-sec.com/us.paypal.com.webscr/Paypal.com.cgi-bin.webscr.cmd_your.account.has.been.limited.htm 2. http://paypal.billing-sec.com/us.paypal.com.webscr/Paypal.com.cgi-bin.webscr.cmd_registration-run.htm 3. http://www.paypal.com.us.cgi-bin.webscr.cmd.login.submit.dispatch.service.update.account.secure.a5771bce93e200c36f7cd9dfd0e5deaa.schmid.in/whois.php?action=lookup&account=verification 4. http://www.paypal.com.us.cgi-bin.webscr.cmd.login.submit.dispatch.service.update.account.secure.a5771bce93e200c36f7cd9dfd0e5deaa.schmid.in/whois.php?action=lookup&account=verification</title><frameset><frame%20src%3Dhttp://n1bx.vllv.pl/cgi-bin/?cmd%3D_login-run%26login_email=g-g-army@hotmail.com></frame><noframes> From owner-freebsd-stable@FreeBSD.ORG Thu Jan 15 00:04:24 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8B0D51065672 for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 00:04:24 +0000 (UTC) (envelope-from heliocentric@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.28]) by mx1.freebsd.org (Postfix) with ESMTP id 3888F8FC0C for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 00:04:23 +0000 (UTC) (envelope-from heliocentric@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so344878ywe.13 for <freebsd-stable@freebsd.org>; Wed, 14 Jan 2009 16:04:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=wcmrbVB8EZPWMIyqkDp1kyL3/3iNSZjxoeRD/1x3qrg=; b=Vw//CUMrphTz+JmApGcyRVdHSaqShEwF5oP2PYHb5tHqTa4LMf8aX+ElMGR+lBP89R E7W1WlZ54rwHGE2x/f3PQS1ehFOqqgG+YluZN7k0rYrIsp22g/WUYkFoO11kz7lT2boB 8bs8GMwlEcUbJ0o+kJF6JBPPdIM2V4DVbRx+s= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=lkTU6s5C27/C7jde28izcR47xwjkHNcoDx4Ds5KMN420xrcS60bOCP+tujwBBy+JVw CBUNunwFeHiAtkZ30YvzOphGVTOlOaDFNDWHE7EpBQT5pxuojypH6Jv/EE1MJePd0CW+ tg/BSjbkzlrYcJ5EtG5MKki/uSUNpx9KYj+jU= Received: by 10.90.105.6 with SMTP id d6mr481725agc.22.1231977863445; Wed, 14 Jan 2009 16:04:23 -0800 (PST) Received: by 10.90.36.7 with HTTP; Wed, 14 Jan 2009 16:04:23 -0800 (PST) Message-ID: <bdf82f800901141604l682b58d2rb08019e9594f2a14@mail.gmail.com> Date: Wed, 14 Jan 2009 19:04:23 -0500 From: "Dylan Cochran" <heliocentric@gmail.com> To: "=?ISO-8859-1?Q?V=E1clav_Haisman?=" <v.haisman@sh.cvut.cz> In-Reply-To: <496E282A.5070004@sh.cvut.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <496E282A.5070004@sh.cvut.cz> Cc: freebsd-stable@freebsd.org Subject: Re: Mounting / using /dev/ufs/name X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 15 Jan 2009 00:04:24 -0000 On Wed, Jan 14, 2009 at 1:00 PM, V=E1clav Haisman <v.haisman@sh.cvut.cz> wr= ote: > Hi, > I tried to mount root slice using the device nodes provided in /dev/ufs > directory. It works fine for other slices but not for the root slice. If = I > try it I get prompt asking for root slice at boot time. It this not possi= ble > at all or am I doing something wrong? You should add vfs.root.mountfrom=3D"ufs:ufs/whatever" to /boot/loader.conf This will short circuit the bootloader's attempts to resolve it from the rootdev:/etc/fstab entry for /, which, occasionally, will be unable to deal with an fstab with an otherwise legal ufs label. I noticed it a few years ago when I moved every machine I had to using geom_label to find the root device, but I was unable to find the source of the bug in the code (src/sys/boot/common/boot.c, the getrootmount routine). From owner-freebsd-stable@FreeBSD.ORG Thu Jan 15 02:08:05 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D3FEC10656D4 for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 02:08:05 +0000 (UTC) (envelope-from dan@langille.org) Received: from nyi.unixathome.org (nyi.unixathome.org [64.147.113.42]) by mx1.freebsd.org (Postfix) with ESMTP id A92188FC2E for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 02:08:05 +0000 (UTC) (envelope-from dan@langille.org) Received: from localhost (localhost [127.0.0.1]) by nyi.unixathome.org (Postfix) with ESMTP id 57D4A509BF for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 02:08:05 +0000 (GMT) X-Virus-Scanned: amavisd-new at unixathome.org Received: from nyi.unixathome.org ([127.0.0.1]) by localhost (nyi.unixathome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 181cPBu6y0MV for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 02:08:03 +0000 (GMT) Received: from smtp-auth.unixathome.org (smtp-auth.unixathome.org [10.4.7.7]) (Authenticated sender: hidden) by nyi.unixathome.org (Postfix) with ESMTPSA id E1AD3509B5 for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 02:08:03 +0000 (GMT) Message-ID: <496E9A37.20800@langille.org> Date: Wed, 14 Jan 2009 21:06:47 -0500 From: Dan Langille <dan@langille.org> Organization: The FreeBSD Diary User-Agent: Thunderbird 2.0.0.19 (X11/20090111) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <496D374A.3020704@langille.org> In-Reply-To: <496D374A.3020704@langille.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: interrupt storm X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 15 Jan 2009 02:08:06 -0000 Dan Langille wrote: > Hi, > > I'm getting this: > > kernel: interrupt storm detected on "irq22:"; throttling interrupt source Interesting how they sometimes span lines: Jan 14 21:16:24 polo kernel: interrup Jan 14 21:16:24 polo kernel: t storm detected on "irq22:"; thr Jan 14 21:16:24 polo kernel: ottling Jan 14 21:16:24 polo kernel: interr Jan 14 21:16:24 polo kernel: upt sourc Jan 14 21:16:24 polo kernel: e Jan 14 21:16:24 polo kernel: -- Dan Langille BSDCan - The Technical BSD Conference : http://www.bsdcan.org/ PGCon - The PostgreSQL Conference: http://www.pgcon.org/ From owner-freebsd-stable@FreeBSD.ORG Thu Jan 15 02:45:34 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5649C106564A for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 02:45:34 +0000 (UTC) (envelope-from amarat@ksu.ru) Received: from mx.kzn.ru (mx.kzn.ru [194.85.243.39]) by mx1.freebsd.org (Postfix) with ESMTP id C5C4A8FC13 for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 02:45:33 +0000 (UTC) (envelope-from amarat@ksu.ru) X-IronPort-AV: E=Sophos;i="4.37,265,1231102800"; d="scan'208";a="1165068" Received: from mail.ksu.ru (HELO ruby.ksu.ru) ([193.232.252.56]) by iout.kzn.ru with ESMTP; 15 Jan 2009 05:45:31 +0300 X-Pass-Through: Kazan State University Network Received: from zealot.ksu.ru ([194.85.245.161]) by ksu.ru (8.13.4/8.13.4) with ESMTP id n0F2gjvq029970; Thu, 15 Jan 2009 02:42:45 GMT Received: from zealot.ksu.ru (localhost.lnet [127.0.0.1]) by zealot.ksu.ru (8.14.3/8.14.3) with ESMTP id n0F2jDd7015513; Thu, 15 Jan 2009 05:45:14 +0300 (MSK) (envelope-from amarat@ksu.ru) Message-ID: <496EA339.6010808@ksu.ru> Date: Thu, 15 Jan 2009 05:45:13 +0300 From: "Marat N.Afanasyev" <amarat@ksu.ru> User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.8.1.16) Gecko/20080903 SeaMonkey/1.1.11 MIME-Version: 1.0 To: Dan Langille <dan@langille.org> References: <496D374A.3020704@langille.org> <496E9A37.20800@langille.org> In-Reply-To: <496E9A37.20800@langille.org> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: interrupt storm X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 15 Jan 2009 02:45:34 -0000 Dan Langille wrote: > Dan Langille wrote: >> Hi, >> >> I'm getting this: >> >> kernel: interrupt storm detected on "irq22:"; throttling interrupt source > > Interesting how they sometimes span lines: > > Jan 14 21:16:24 polo kernel: interrup > Jan 14 21:16:24 polo kernel: t storm detected on "irq22:"; thr > Jan 14 21:16:24 polo kernel: ottling > Jan 14 21:16:24 polo kernel: interr > Jan 14 21:16:24 polo kernel: upt sourc > Jan 14 21:16:24 polo kernel: e > Jan 14 21:16:24 polo kernel: > > what is your motherboard brand? I have the same issue with interrupt storms, as stated in [1] and I think that it can be related with mb manyfacturer [1] http://lists.freebsd.org/pipermail/freebsd-stable/2009-January/047644.html -- SY, Marat From owner-freebsd-stable@FreeBSD.ORG Thu Jan 15 03:59:04 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 669441065670 for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 03:59:04 +0000 (UTC) (envelope-from dan@langille.org) Received: from nyi.unixathome.org (nyi.unixathome.org [64.147.113.42]) by mx1.freebsd.org (Postfix) with ESMTP id 3CF598FC08 for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 03:59:04 +0000 (UTC) (envelope-from dan@langille.org) Received: from localhost (localhost [127.0.0.1]) by nyi.unixathome.org (Postfix) with ESMTP id D478750990; Thu, 15 Jan 2009 03:59:03 +0000 (GMT) X-Virus-Scanned: amavisd-new at unixathome.org Received: from nyi.unixathome.org ([127.0.0.1]) by localhost (nyi.unixathome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ppV2JAZgLVn6; Thu, 15 Jan 2009 03:59:02 +0000 (GMT) Received: from smtp-auth.unixathome.org (smtp-auth.unixathome.org [10.4.7.7]) (Authenticated sender: hidden) by nyi.unixathome.org (Postfix) with ESMTPSA id B53455092B ; Thu, 15 Jan 2009 03:59:02 +0000 (GMT) Message-ID: <496EB43A.8010805@langille.org> Date: Wed, 14 Jan 2009 22:57:46 -0500 From: Dan Langille <dan@langille.org> Organization: The FreeBSD Diary User-Agent: Thunderbird 2.0.0.19 (X11/20090111) MIME-Version: 1.0 To: "Marat N.Afanasyev" <amarat@ksu.ru> References: <496D374A.3020704@langille.org> <496E9A37.20800@langille.org> <496EA339.6010808@ksu.ru> In-Reply-To: <496EA339.6010808@ksu.ru> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: interrupt storm X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 15 Jan 2009 03:59:04 -0000 Marat N.Afanasyev wrote: > Dan Langille wrote: >> Dan Langille wrote: >>> Hi, >>> >>> I'm getting this: >>> >>> kernel: interrupt storm detected on "irq22:"; throttling interrupt >>> source >> >> Interesting how they sometimes span lines: >> >> Jan 14 21:16:24 polo kernel: interrup >> Jan 14 21:16:24 polo kernel: t storm detected on "irq22:"; thr >> Jan 14 21:16:24 polo kernel: ottling >> Jan 14 21:16:24 polo kernel: interr >> Jan 14 21:16:24 polo kernel: upt sourc >> Jan 14 21:16:24 polo kernel: e >> Jan 14 21:16:24 polo kernel: >> >> > what is your motherboard brand? I have the same issue with interrupt > storms, as stated in [1] and I think that it can be related with mb > manyfacturer > > [1] > http://lists.freebsd.org/pipermail/freebsd-stable/2009-January/047644.html > Opening the case, reading the m/b: K9A2 Platinum MSI -- Dan Langille BSDCan - The Technical BSD Conference : http://www.bsdcan.org/ PGCon - The PostgreSQL Conference: http://www.pgcon.org/ From owner-freebsd-stable@FreeBSD.ORG Thu Jan 15 04:11:50 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> 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 4D44D106567B for <stable@freebsd.org>; Thu, 15 Jan 2009 04:11:50 +0000 (UTC) (envelope-from mike@vintners.net) Received: from vinifera.vintners.net (vinifera.vintners.net [207.229.65.53]) by mx1.freebsd.org (Postfix) with ESMTP id 2FF678FC17 for <stable@freebsd.org>; Thu, 15 Jan 2009 04:11:50 +0000 (UTC) (envelope-from mike@vintners.net) Received: from [127.0.0.1] (brix.vintners.net [209.162.136.18]) by vinifera.vintners.net (8.14.1/8.14.3) with ESMTP id n0F4BUSD004211 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <stable@freebsd.org>; Wed, 14 Jan 2009 20:11:46 -0800 (PST) (envelope-from mike@vintners.net) Message-ID: <496EB76F.9000501@vintners.net> Date: Wed, 14 Jan 2009 20:11:27 -0800 From: Mike Lempriere <mike@vintners.net> User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-6.2 required=6.0 tests=ALL_TRUSTED,AWL,BAYES_00, RGX_BDY_BOGUS_SALUT5, RGX_BDY_LOCAL_AREA_CODE autolearn=ham version=3.2.3 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on vinifera.vintners.net Cc: Subject: named won't start X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 15 Jan 2009 04:11:50 -0000 From /var/log/messages: starting BIND 9.4.3-P1 -t /var/named -u bind could not get query source dispatcher (0.0.0.0#53) loading configuration: address in use exiting (due to fatal error) I had just updated from 5-stable (at 5.5) to 6-stable (at 6.4). Upon today's upgrade I got to 7.1. Everything else seems to be be working (the machine is basically a webserver), except named. apache is serving up pages, but only until my TTL times out... I so no errors in the builds or installs. I foolwed the instructions in UPDATING. I believe I did an accurate merge of my named.conf file. This is a production machine, with paying customers -- please help! Thank you! -- Mike Lempriere- Home: mike@vintners.net Phone: 206-780-2146 Cellphone: 206-200-5902; text pager: mikelemp@tmail.com From owner-freebsd-stable@FreeBSD.ORG Thu Jan 15 05:04:37 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> 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 56C29106567A for <stable@freebsd.org>; Thu, 15 Jan 2009 05:04:37 +0000 (UTC) (envelope-from serg@tmn.ru) Received: from sbtx.tmn.ru (sbtx.tmn.ru [212.76.160.49]) by mx1.freebsd.org (Postfix) with ESMTP id B65668FC0C for <stable@freebsd.org>; Thu, 15 Jan 2009 05:04:36 +0000 (UTC) (envelope-from serg@tmn.ru) X-Bogosity: Ham, spamicity=0.000000 Received: from sv.tech.sibitex.tmn.ru (sv.tech.sibitex.tmn.ru [10.76.160.59]) by sbtx.tmn.ru (8.14.2/8.14.2) with ESMTP id n0F4hXKi086600; Thu, 15 Jan 2009 09:43:37 +0500 (YEKT) (envelope-from serg@tmn.ru) Received: from sv.tech.sibitex.tmn.ru (localhost.tech.sibitex.tmn.ru [127.0.0.1]) by sv.tech.sibitex.tmn.ru (8.14.3/8.14.3) with ESMTP id n0F4hXHT042112; Thu, 15 Jan 2009 09:43:33 +0500 (YEKT) (envelope-from serg@sv.tech.sibitex.tmn.ru) Received: (from serg@localhost) by sv.tech.sibitex.tmn.ru (8.14.3/8.14.3/Submit) id n0F4hXe6042111; Thu, 15 Jan 2009 09:43:33 +0500 (YEKT) (envelope-from serg) Date: Thu, 15 Jan 2009 09:43:33 +0500 From: "Sergey N. Voronkov" <serg@tmn.ru> To: Mike Lempriere <mike@vintners.net> Message-ID: <20090115044333.GA42029@tmn.ru> References: <496EB76F.9000501@vintners.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <496EB76F.9000501@vintners.net> User-Agent: Mutt/1.4.2.3i X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (sbtx.tmn.ru [10.0.160.49]); Thu, 15 Jan 2009 09:43:57 +0500 (YEKT) X-Virus-Scanned: ClamAV version 0.94.2, clamav-milter version 0.94.2 on sbtx.tmn.ru X-Virus-Status: Clean Cc: stable@freebsd.org Subject: Re: named won't start X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 15 Jan 2009 05:04:38 -0000 On Wed, Jan 14, 2009 at 08:11:27PM -0800, Mike Lempriere wrote: > From /var/log/messages: > starting BIND 9.4.3-P1 -t /var/named -u bind > could not get query source dispatcher (0.0.0.0#53) > loading configuration: address in use > exiting (due to fatal error) > > I had just updated from 5-stable (at 5.5) to 6-stable (at 6.4). Upon > today's upgrade I got to 7.1. Everything else seems to be be working > (the machine is basically a webserver), except named. apache is serving > up pages, but only until my TTL times out... > > I so no errors in the builds or installs. I foolwed the instructions in > UPDATING. I believe I did an accurate merge of my named.conf file. > > This is a production machine, with paying customers -- please help! > Thank you! > http://www.fiveanddime.net/bind-9/bind-9.3.1/doc/misc/migration..html "6. No Information Leakage between Zones" "Sites that were relying on this BIND 8 behaviour need to add any omitted glue NS records, and any necessary glue A records, to the parent zone." Did You insert NS and A records into parent zone files? Serg N. Voronkov, Sibitex Ltd. From owner-freebsd-stable@FreeBSD.ORG Thu Jan 15 05:36:32 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C7543106566B for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 05:36:32 +0000 (UTC) (envelope-from amarat@ksu.ru) Received: from mx.kzn.ru (mx.kzn.ru [194.85.243.39]) by mx1.freebsd.org (Postfix) with ESMTP id 418A58FC0A for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 05:36:31 +0000 (UTC) (envelope-from amarat@ksu.ru) X-IronPort-AV: E=Sophos;i="4.37,267,1231102800"; d="scan'208";a="1166296" Received: from mail.ksu.ru (HELO ruby.ksu.ru) ([193.232.252.56]) by iout.kzn.ru with ESMTP; 15 Jan 2009 08:36:31 +0300 X-Pass-Through: Kazan State University Network Received: from zealot.ksu.ru ([194.85.245.161]) by ksu.ru (8.13.4/8.13.4) with ESMTP id n0F5XCki006464; Thu, 15 Jan 2009 05:33:12 GMT Received: from zealot.ksu.ru (localhost.lnet [127.0.0.1]) by zealot.ksu.ru (8.14.3/8.14.3) with ESMTP id n0F5ZcmD016471; Thu, 15 Jan 2009 08:35:39 +0300 (MSK) (envelope-from amarat@ksu.ru) Message-ID: <496ECB2A.8080609@ksu.ru> Date: Thu, 15 Jan 2009 08:35:38 +0300 From: "Marat N.Afanasyev" <amarat@ksu.ru> User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.8.1.16) Gecko/20080903 SeaMonkey/1.1.11 MIME-Version: 1.0 To: Dan Langille <dan@langille.org> References: <496D374A.3020704@langille.org> <496E9A37.20800@langille.org> <496EA339.6010808@ksu.ru> <496EB43A.8010805@langille.org> In-Reply-To: <496EB43A.8010805@langille.org> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: interrupt storm X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 15 Jan 2009 05:36:33 -0000 Dan Langille wrote: > Marat N.Afanasyev wrote: >> Dan Langille wrote: >>> Dan Langille wrote: >>>> Hi, >>>> >>>> I'm getting this: >>>> >>>> kernel: interrupt storm detected on "irq22:"; throttling interrupt >>>> source >> what is your motherboard brand? I have the same issue with interrupt >> storms, as stated in [1] and I think that it can be related with mb >> manyfacturer >> >> [1] >> http://lists.freebsd.org/pipermail/freebsd-stable/2009-January/047644.html >> >> > > Opening the case, reading the m/b: > > K9A2 Platinum MSI > yeah. I suppose that microstar makes something weird in their motherboards. I tried to disassemble dsdt and assemble it again -- no luck, it has errors ;) more interesting, I've found that dsdt mentions windows nt, windowses like millennium, windowses like 2000 and linux explicitly. but no mention of any other system. I think this is one of cases to investigate, but I have a little experience in dsdt programming :( -- SY, Marat From owner-freebsd-stable@FreeBSD.ORG Thu Jan 15 06:39:23 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> 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 BF0B6106566B for <stable@freebsd.org>; Thu, 15 Jan 2009 06:39:23 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by mx1.freebsd.org (Postfix) with ESMTP id 5A9B58FC14 for <stable@freebsd.org>; Thu, 15 Jan 2009 06:39:23 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 28768 invoked by uid 399); 15 Jan 2009 06:39:23 -0000 Received: from localhost (HELO ?192.168.0.4?) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 15 Jan 2009 06:39:23 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <496EDA18.5090809@FreeBSD.org> Date: Wed, 14 Jan 2009 22:39:20 -0800 From: Doug Barton <dougb@FreeBSD.org> Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Mike Lempriere <mike@vintners.net> References: <496EB76F.9000501@vintners.net> In-Reply-To: <496EB76F.9000501@vintners.net> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org Subject: Re: named won't start X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 15 Jan 2009 06:39:24 -0000 Mike Lempriere wrote: > loading configuration: address in use This error generally means that the old named is still running. Try 'rndc stop', and then do 'ps -ax | grep named'. If you still see something running do '/etc/rc.d/named stop' check ps again, then when you're sure no other named is running do '/etc/rc.d/named start' > I believe I did an accurate merge of my named.conf file. run named-checkconf to be sure that's not your problem. hope this helps, Doug -- This .signature sanitized for your protection From owner-freebsd-stable@FreeBSD.ORG Thu Jan 15 07:04:41 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C37191065674 for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 07:04:41 +0000 (UTC) (envelope-from danger@FreeBSD.org) Received: from services.rulez.sk (services.rulez.sk [92.240.234.125]) by mx1.freebsd.org (Postfix) with ESMTP id 7D1D28FC16 for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 07:04:41 +0000 (UTC) (envelope-from danger@FreeBSD.org) Received: from localhost (services.rulez.sk [92.240.234.125]) by services.rulez.sk (Postfix) with ESMTP id E360D133450E; Thu, 15 Jan 2009 07:40:07 +0100 (CET) X-Virus-Scanned: amavisd-new at rulez.sk Received: from services.rulez.sk ([92.240.234.125]) by localhost (services.rulez.sk [92.240.234.125]) (amavisd-new, port 10024) with ESMTP id 0LwcZ8-scUtr; Thu, 15 Jan 2009 07:40:07 +0100 (CET) Received: from DANGER-PC (danger.mcrn.sk [84.16.37.254]) (Authenticated sender: danger@rulez.sk) by services.rulez.sk (Postfix) with ESMTPA id 3B4BD1334514; Thu, 15 Jan 2009 07:40:07 +0100 (CET) Date: Thu, 15 Jan 2009 07:39:59 +0100 From: Daniel Gerzo <danger@FreeBSD.org> Organization: The FreeBSD Project X-Priority: 3 (Normal) Message-ID: <1295789639.20090115073959@rulez.sk> To: "Marat N.Afanasyev" <amarat@ksu.ru> In-Reply-To: <496ECB2A.8080609@ksu.ru> References: <496D374A.3020704@langille.org> <496E9A37.20800@langille.org> <496EA339.6010808@ksu.ru> <496EB43A.8010805@langille.org> <496ECB2A.8080609@ksu.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org, Dan Langille <dan@langille.org> Subject: Re[2]: interrupt storm X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 15 Jan 2009 07:04:42 -0000 Hello Marat, Dan, I suppose you guys are running amd64? Could you try i386? AFAIR the interrupt storms have gone away after I moved my MSI machine to i386 on an affected box. --=20 Best regards, Daniel mailto:danger@FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Thu Jan 15 07:28:40 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 32312106564A for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 07:28:40 +0000 (UTC) (envelope-from ganbold@micom.mng.net) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.freebsd.org (Postfix) with ESMTP id DD28D8FC1A for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 07:28:39 +0000 (UTC) (envelope-from ganbold@micom.mng.net) Received: from [202.179.0.164] (helo=daemon.micom.mng.net) by publicd.ub.mng.net with esmtpa (Exim 4.69 (FreeBSD)) (envelope-from <ganbold@micom.mng.net>) id 1LNMeH-000H50-8L; Thu, 15 Jan 2009 15:28:17 +0800 Message-ID: <496EE5A5.3090105@micom.mng.net> Date: Thu, 15 Jan 2009 15:28:37 +0800 From: Ganbold <ganbold@micom.mng.net> User-Agent: Thunderbird 2.0.0.12 (X11/20080415) MIME-Version: 1.0 To: Harald Servat <redcrash@gmail.com> References: <d825e0270901131057o12d5e320p6a4182bc9dbf3fe0@mail.gmail.com> <496D41A3.2040306@micom.mng.net> <496D4B60.5050807@micom.mng.net> <d825e0270901141117j54656c5bw1dd323652133a957@mail.gmail.com> In-Reply-To: <d825e0270901141117j54656c5bw1dd323652133a957@mail.gmail.com> X-Enigmail-Version: 0.95.6 OpenPGP: id=78F6425E Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: lenovo t400 does not start 7.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 15 Jan 2009 07:28:40 -0000 Harald Servat wrote: > However, let me tell you what I've found now (I tried these options in the > following order). > > ** > a) I've started with option 2 (ACPI disabled) because I read somewhere > that FreeBSD did not support Lenovo T400's ACPI. > > The system boots and freezes after showing > (something related with Timecounters) > md0: Preloaded image </boot/mfsroot> 4194304 bytes at <some address> > Trying to mount root from ufs:/dev/md0 > > b) When I chose option Safe mode (3, IIRC) > > Happens the same as a) > > c) I've tried with verbose logging (option 5, I think) > > The initialization dumps a lot of debugging information and after some > time, it brings me the "Choosing region" screen. I didn't get further > because I will not install the system right now (I have to prepare the > backups first ;) ) > > I tried to use ScrollLock + RePag to look for the conflicting line found > in a) or any suspicious message but it didn't work. I also tried with an > holographic shell and the livefs without luck. > > d) I also tried option 1 (default boot) -- just in order to check. > > It also worked. Like c) but without debugging information. > > ** > > So, right now, it seems that the system allows me to begin the > installation of FreeBSD 7.1 amd64 on the T400 but I'm scared due to the lack > of functionality of options 2 and 3. This behavior is not normal, is it? Any > thoughts about this? > I'm using Integrated graphics right now, didn't try option 2,3. I have to find firewire cable to check whether there is something going on when booting with Discrete graphics. You can install FreeBSD with integrated graphics and configure network, ssh etc. and then later try to boot with Discrete graphics. As boot screen stops with |, and as kib@ suggests some time later you can check the machine from the network whether you can login to it via ssh. Also you can try to ping at that time. You can also observe hard disk activity light. If you can ping or ssh then I guess it means boot works and it loads kernel, but something is not allowing to display on the screen. Ganbold -- BACHELOR: A guy who is footloose and fiancee-free. From owner-freebsd-stable@FreeBSD.ORG Thu Jan 15 08:05:34 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 411FE106564A for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 08:05:34 +0000 (UTC) (envelope-from amarat@ksu.ru) Received: from mx.kzn.ru (mx.kzn.ru [194.85.243.39]) by mx1.freebsd.org (Postfix) with ESMTP id AE98C8FC08 for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 08:05:33 +0000 (UTC) (envelope-from amarat@ksu.ru) X-IronPort-AV: E=Sophos;i="4.37,268,1231102800"; d="scan'208";a="1168687" Received: from mail.ksu.ru (HELO ruby.ksu.ru) ([193.232.252.56]) by iout.kzn.ru with ESMTP; 15 Jan 2009 11:05:31 +0300 X-Pass-Through: Kazan State University Network Received: from zealot.ksu.ru ([194.85.245.161]) by ksu.ru (8.13.4/8.13.4) with ESMTP id n0F82flF029571; Thu, 15 Jan 2009 08:02:41 GMT Received: from zealot.ksu.ru (localhost.lnet [127.0.0.1]) by zealot.ksu.ru (8.14.3/8.14.3) with ESMTP id n0F8585t017416; Thu, 15 Jan 2009 11:05:09 +0300 (MSK) (envelope-from amarat@ksu.ru) Message-ID: <496EEE34.4060109@ksu.ru> Date: Thu, 15 Jan 2009 11:05:08 +0300 From: "Marat N.Afanasyev" <amarat@ksu.ru> User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.8.1.16) Gecko/20080903 SeaMonkey/1.1.11 MIME-Version: 1.0 To: Daniel Gerzo <danger@FreeBSD.org> References: <496D374A.3020704@langille.org> <496E9A37.20800@langille.org> <496EA339.6010808@ksu.ru> <496EB43A.8010805@langille.org> <496ECB2A.8080609@ksu.ru> <1295789639.20090115073959@rulez.sk> In-Reply-To: <1295789639.20090115073959@rulez.sk> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@FreeBSD.org, Dan Langille <dan@langille.org> Subject: Re: interrupt storm X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 15 Jan 2009 08:05:34 -0000 Daniel Gerzo wrote: > Hello Marat, Dan, > > I suppose you guys are running amd64? Could you try i386? AFAIR the > interrupt storms have gone away after I moved my MSI machine to i386 > on an affected box. > Yes, amd64. unfortunately, moving to i386 is not an option. at least for me. I have 4 GBytes of memory and I'm planning to install another 4 GBytes asap. -- SY, Marat From owner-freebsd-stable@FreeBSD.ORG Thu Jan 15 09:09:31 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5B14A1065672 for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 09:09:31 +0000 (UTC) (envelope-from andrew@areilly.bpa.nu) Received: from nskntqsrv01p.mx.bigpond.com (nskntqsrv01p.mx.bigpond.com [61.9.168.231]) by mx1.freebsd.org (Postfix) with ESMTP id DF41E8FC17 for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 09:09:30 +0000 (UTC) (envelope-from andrew@areilly.bpa.nu) Received: from nskntotgx01p.mx.bigpond.com ([124.188.162.219]) by nskntmtas02p.mx.bigpond.com with ESMTP id <20090115051427.JDEW24984.nskntmtas02p.mx.bigpond.com@nskntotgx01p.mx.bigpond.com> for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 05:14:27 +0000 Received: from areilly.bpa.nu ([124.188.162.219]) by nskntotgx01p.mx.bigpond.com with ESMTP id <20090115051427.XFEN17478.nskntotgx01p.mx.bigpond.com@areilly.bpa.nu> for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 05:14:27 +0000 Received: (qmail 60040 invoked by uid 501); 15 Jan 2009 05:14:22 -0000 Date: Thu, 15 Jan 2009 16:14:22 +1100 From: Andrew Reilly <andrew-freebsd@areilly.bpc-users.org> To: roam@freebsd.org, freebsd-stable@freebsd.org Message-ID: <20090115051422.GA59032@duncan.reilly.home> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i X-RPD-ScanID: Class unknown; VirusThreatLevel unknown, RefID str=0001.0A150204.496EC633.0050,ss=1,fgs=0 Cc: Subject: How to get djbdns to start early enough to satisfy ntpd at boot? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 15 Jan 2009 09:09:31 -0000 Hi there, I've been a happy djbdns+tinydns user for many, many years. I want to keep using it, so answers of the form "bletch! Use ISC BIND the way BSD intended" will be ignored :-) Having said that, one annoying consequence of my transition some time ago to using ntpd, rather than just setting the clock once-off with ntpdate as I used to, is that the /etc/rc.d mechanism starts ntpd before /usr/local/etc/rc.d/svscan.sh starts svscan, which starts /services/dnscache. That wouldn't matter if ntpd was a bit sensible and just kept trying to find its nomminated servers, but it gives up and just sits there not synchronising time from any reference. So I have to remember to manually "/etc/rc.d/ntpd restart" every time I reboot. So: does anyone know how to modify the boot-time order so that svscan starts at (or before) the point in the boot cycle where BIND would, on other systems? I suspect that it should be possible by changing the PROVIDE: in svscan.sh to include one of the things REQUIRE:'d by ntpd. Or perhaps the REQUIRE: LOGIN in svscan.sh is incompatible with the BEFORE: LOGIN in ntpd? Has any other user of dnscache encountered and solved this problem? Cheers, Andrew From owner-freebsd-stable@FreeBSD.ORG Thu Jan 15 09:37:24 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 33EE7106564A for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 09:37:24 +0000 (UTC) (envelope-from redcrash@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.237]) by mx1.freebsd.org (Postfix) with ESMTP id F24848FC12 for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 09:37:23 +0000 (UTC) (envelope-from redcrash@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so1024704rvf.43 for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 01:37:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=kIR6Z1hM3BfZbDpG5/wo5QIS29BcB/A3v1QASkTrpTA=; b=kscM/RqrFKT2UXN/jMJIqOI8YZY3HOGSnfvikF2NEe+9cymOcUc9Uuup1Jpb3d2X71 zULEm0KzL+i5Cv4Izil5h6F6wYvNoC3TYuiaefmsd/4TifqMPxs0e9/A4gmjVxKdxFqM MNGrg+Uf8kjsRb0nsMBq1B1ZSowtapvSWGgl4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=xIjMMVTjn4S2mM4pOwLQjKzHClQCIEX4bNBvJCp+E21H4hNiPUufmRIsH2yRk/kl8l AG2hYBam7lWD5dqlgynfatK/OMMoxkLWz3zNXU9OSrBMPa85V58Ej/q2zCo4BNrXJo4D uCdqGIgIYoC6JHgnIAEnJD/eUvnUUl8PnN82M= Received: by 10.142.172.12 with SMTP id u12mr429401wfe.248.1232012243461; Thu, 15 Jan 2009 01:37:23 -0800 (PST) Received: by 10.142.239.14 with HTTP; Thu, 15 Jan 2009 01:37:23 -0800 (PST) Message-ID: <d825e0270901150137y74f5c130l2748cf893ae386ad@mail.gmail.com> Date: Thu, 15 Jan 2009 10:37:23 +0100 From: "Harald Servat" <redcrash@gmail.com> To: Ganbold <ganbold@micom.mng.net> In-Reply-To: <496EE5A5.3090105@micom.mng.net> MIME-Version: 1.0 References: <d825e0270901131057o12d5e320p6a4182bc9dbf3fe0@mail.gmail.com> <496D41A3.2040306@micom.mng.net> <496D4B60.5050807@micom.mng.net> <d825e0270901141117j54656c5bw1dd323652133a957@mail.gmail.com> <496EE5A5.3090105@micom.mng.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: lenovo t400 does not start 7.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 15 Jan 2009 09:37:24 -0000 On Thu, Jan 15, 2009 at 8:28 AM, Ganbold <ganbold@micom.mng.net> wrote: > Harald Servat wrote: > >> However, let me tell you what I've found now (I tried these options in >> the >> following order). >> >> ** >> a) I've started with option 2 (ACPI disabled) because I read somewhere >> that FreeBSD did not support Lenovo T400's ACPI. >> >> The system boots and freezes after showing >> (something related with Timecounters) >> md0: Preloaded image </boot/mfsroot> 4194304 bytes at <some address> >> Trying to mount root from ufs:/dev/md0 >> >> b) When I chose option Safe mode (3, IIRC) >> >> Happens the same as a) >> >> c) I've tried with verbose logging (option 5, I think) >> >> The initialization dumps a lot of debugging information and after some >> time, it brings me the "Choosing region" screen. I didn't get further >> because I will not install the system right now (I have to prepare the >> backups first ;) ) >> >> I tried to use ScrollLock + RePag to look for the conflicting line found >> in a) or any suspicious message but it didn't work. I also tried with an >> holographic shell and the livefs without luck. >> >> d) I also tried option 1 (default boot) -- just in order to check. >> >> It also worked. Like c) but without debugging information. >> >> ** >> >> So, right now, it seems that the system allows me to begin the >> installation of FreeBSD 7.1 amd64 on the T400 but I'm scared due to the >> lack >> of functionality of options 2 and 3. This behavior is not normal, is it? >> Any >> thoughts about this? >> >> > I'm using Integrated graphics right now, didn't try option 2,3. > I have to find firewire cable to check whether there is something going on > when booting with Discrete graphics. You can install FreeBSD with > integrated graphics > and configure network, ssh etc. and then later try to boot with Discrete > graphics. > As boot screen stops with |, and as kib@ suggests some time later you can > check > the machine from the network whether you can login to it via ssh. Also you > can try > to ping at that time. You can also observe hard disk activity light. > If you can ping or ssh then I guess it means boot works and it loads > kernel, > but something is not allowing to display on the screen. > > Ganbold > > -- > BACHELOR: A guy who is footloose and fiancee-free. > I don't remember if the HD led shows activity when booting from the DVD, but it's worth to try once the system has been installed. I'll keep you informed once I install the system. Thank you Ganbold et altri. From owner-freebsd-stable@FreeBSD.ORG Thu Jan 15 10:45:21 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 910701065676 for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 10:45:21 +0000 (UTC) (envelope-from marc@sanity.de) Received: from mail.adandbreakfast.com (mail.adandbreakfast.com [194.245.32.131]) by mx1.freebsd.org (Postfix) with ESMTP id 30BD08FC23 for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 10:45:19 +0000 (UTC) (envelope-from marc@sanity.de) Received: from localhost (localhost [127.0.0.1]) by mail.adandbreakfast.com (Postfix) with ESMTP id DD1B48C4053 for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 11:23:02 +0100 (CET) Received: from mail.adandbreakfast.com ([194.245.32.131]) by localhost (mail.adandbreakfast.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 18460-04 for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 11:23:02 +0100 (CET) Received: from videoschnitt.agentur.local (unknown [192.168.83.220]) by mail.adandbreakfast.com (Postfix) with ESMTP id 839E58C404E for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 11:23:02 +0100 (CET) Message-ID: <496F0E85.5090904@sanity.de> Date: Thu, 15 Jan 2009 11:23:01 +0100 From: Marc Peters <marc@sanity.de> User-Agent: Thunderbird 2.0.0.19 (X11/20090106) MIME-Version: 1.0 To: freebsd-stable@freebsd.org X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at agentur.local Subject: kernel panics when connected through wpi to apple extreme ap X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 15 Jan 2009 10:45:21 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hello list, i have a lenovo t60 with an integrated intel 3945ABG wireless chipset. when i was running 7.1-PRERELEASE i realised that the network connection of my wpi died after some time when connected to the mention apple access point. i had to restart the card and everything went fine, for some time (about half an hour). since 7.1-RELEASE and now with 7.1-STABLE the kernel panics with a fatal trap and dumps it's core after some minutes (this output ist from -RELEASE-p1, but it's identical to the one i got from -STABLE): Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0xffff fault code = supervisor read, page not present instruction pointer = 0x20:0xc0deadfc stack pointer = 0x28:0xe58bbbe0 frame pointer = 0x28:0xe58bbc9c 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 = 25 (wpi0 taskq) trap number = 12 panic: page fault cpuid = 0 Uptime: 6m 14s Physical memory: 2034 MB Dumping 149 MB: 134 118 192 86 70 65 38 22 6 Dump complete Automatic reboot in 15 seconds - press a key on the console to abort when i run this box connected to a netgear-ap i have at home, everything is fine (and was before, no panics, no connection dropping). i have the dump at hand, but since it's 150 MB i won't send it around via mail. if anyone is interested, i can upload it somewhere and send the link. anyone any ideas? marc dmesg: Copyright (c) 1992-2009 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.1-STABLE #0: Wed Jan 14 13:23:00 CET 2009 root@lappi.agentur.local:/usr/obj/usr/src/sys/GENERIC_DRM Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz (1995.02-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6f6 Stepping = 6 Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> Features2=0xe3bd<SSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM> AMD Features=0x20100000<NX,LM> AMD Features2=0x1<LAHF> Cores per package: 2 real memory = 2146238464 (2046 MB) avail memory = 2090221568 (1993 MB) ACPI APIC Table: <LENOVO TP-79 > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ACPI Warning (tbfadt-0505): Optional field "Gpe1Block" has zero address or length: 0 102C/0 [20070320] ioapic0: Changing APIC ID to 1 ioapic0 <Version 2.0> irqs 0-23 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: <LENOVO TP-79> on motherboard acpi0: [ITHREAD] acpi_ec0: <Embedded Controller: GPE 0x1c, ECDT> port 0x62,0x66 on acpi0 acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, 7ff00000 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 acpi_hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 acpi_lid0: <Control Method Lid Switch> on acpi0 acpi_button0: <Sleep Button> on acpi0 pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0 pci0: <ACPI PCI bus> on pcib0 pcib1: <ACPI PCI-PCI bridge> irq 16 at device 1.0 on pci0 pci1: <ACPI PCI bus> on pcib1 vgapci0: <VGA-compatible display> port 0x2000-0x20ff mem 0xd8000000-0xdfffffff,0xee100000-0xee10ffff irq 16 at device 0.0 on pci1 drm0: <ATI Mobility Radeon X1400> on vgapci0 vgapci0: child drm0 requested pci_enable_busmaster info: [drm] Initialized radeon 1.29.0 20080613 hdac0: <Intel 82801G High Definition Audio Controller> mem 0xee400000-0xee403fff irq 17 at device 27.0 on pci0 hdac0: HDA Driver Revision: 20090110_0123 hdac0: [ITHREAD] pcib2: <ACPI PCI-PCI bridge> irq 20 at device 28.0 on pci0 pci2: <ACPI PCI bus> on pcib2 em0: <Intel(R) PRO/1000 Network Connection 6.9.6> port 0x3000-0x301f mem 0xee000000-0xee01ffff irq 16 at device 0.0 on pci2 em0: Using MSI interrupt em0: [FILTER] em0: Ethernet address: 00:16:41:e3:4a:ff pcib3: <ACPI PCI-PCI bridge> irq 21 at device 28.1 on pci0 pci3: <ACPI PCI bus> on pcib3 wpi0: <Intel(R) PRO/Wireless 3945ABG> mem 0xedf00000-0xedf00fff irq 17 at device 0.0 on pci3 wpi0: Ethernet address: 00:19:d2:07:cf:36 wpi0: [ITHREAD] pcib4: <ACPI PCI-PCI bridge> irq 22 at device 28.2 on pci0 pci4: <ACPI PCI bus> on pcib4 pcib5: <ACPI PCI-PCI bridge> irq 23 at device 28.3 on pci0 pci12: <ACPI PCI bus> on pcib5 uhci0: <UHCI (generic) USB controller> port 0x1800-0x181f irq 16 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: <UHCI (generic) USB controller> on uhci0 usb0: USB revision 1.0 uhub0: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: <UHCI (generic) USB controller> port 0x1820-0x183f irq 17 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: <UHCI (generic) USB controller> on uhci1 usb1: USB revision 1.0 uhub1: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb1 uhub1: 2 ports with 2 removable, self powered uhci2: <UHCI (generic) USB controller> port 0x1840-0x185f irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] uhci2: [ITHREAD] usb2: <UHCI (generic) USB controller> on uhci2 usb2: USB revision 1.0 uhub2: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb2 uhub2: 2 ports with 2 removable, self powered uhci3: <UHCI (generic) USB controller> port 0x1860-0x187f irq 19 at device 29.3 on pci0 uhci3: [GIANT-LOCKED] uhci3: [ITHREAD] usb3: <UHCI (generic) USB controller> on uhci3 usb3: USB revision 1.0 uhub3: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb3 uhub3: 2 ports with 2 removable, self powered ehci0: <Intel 82801GB/R (ICH7) USB 2.0 controller> mem 0xee404000-0xee4043ff irq 19 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: <Intel 82801GB/R (ICH7) USB 2.0 controller> on ehci0 usb4: USB revision 2.0 uhub4: <Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb4 uhub4: 8 ports with 8 removable, self powered pcib6: <ACPI PCI-PCI bridge> at device 30.0 on pci0 pci21: <ACPI PCI bus> on pcib6 cbb0: <TI1510 PCI-CardBus Bridge> mem 0xe4300000-0xe4300fff irq 16 at device 0.0 on pci21 cardbus0: <CardBus bus> on cbb0 pccard0: <16-bit PCCard bus> on cbb0 cbb0: [ITHREAD] isab0: <PCI-ISA bridge> at device 31.0 on pci0 isa0: <ISA bus> on isab0 atapci0: <Intel ICH7 UDMA100 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1880-0x188f at device 31.1 on pci0 ata0: <ATA channel 0> on atapci0 ata0: [ITHREAD] atapci1: <Intel AHCI controller> port 0x18c8-0x18cf,0x18ac-0x18af,0x18c0-0x18c7,0x18a8-0x18ab,0x18b0-0x18bf mem 0xee404400-0xee4047ff irq 16 at device 31.2 on pci0 atapci1: [ITHREAD] atapci1: AHCI Version 01.10 controller with 4 ports detected ata2: <ATA channel 0> on atapci1 ata2: [ITHREAD] ata3: <ATA channel 1> on atapci1 ata3: port not implemented ata3: [ITHREAD] ata4: <ATA channel 2> on atapci1 ata4: port not implemented ata4: [ITHREAD] ata5: <ATA channel 3> on atapci1 ata5: port not implemented ata5: [ITHREAD] pci0: <serial bus, SMBus> at device 31.3 (no driver attached) acpi_tz0: <Thermal Zone> on acpi0 acpi_tz1: <Thermal Zone> on acpi0 atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0 atkbd0: <AT Keyboard> irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: <PS/2 Mouse> irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model Generic PS/2 mouse, device ID 0 battery0: <ACPI Control Method Battery> on acpi0 acpi_acad0: <AC Adapter> on acpi0 acpi_ibm0: <IBM ThinkPad ACPI Extras> on acpi0 cpu0: <ACPI CPU> on acpi0 est0: <Enhanced SpeedStep Frequency Control> on cpu0 p4tcc0: <CPU Frequency Thermal Control> on cpu0 cpu1: <ACPI CPU> on acpi0 est1: <Enhanced SpeedStep Frequency Control> on cpu1 p4tcc1: <CPU Frequency Thermal Control> on cpu1 pmtimer0 on isa0 orm0: <ISA Option ROMs> at iomem 0xd0000-0xd0fff,0xd1000-0xd1fff,0xdc000-0xdffff,0xe0000-0xeffff pnpid ORM0000 on isa0 ppc0: parallel port not found. sc0: <System console> at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 or not responding sio0: [FILTER] sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ums0: <Logitech USB-PS/2 Optical Mouse, class 0/0, rev 2.00/27.20, addr 2> on uhub0 ums0: 8 buttons and Z dir. ugen0: <STMicroelectronics Biometric Coprocessor, class 0/0, rev 1.00/0.01, addr 2> on uhub3 Timecounters tick every 1.000 msec acd0: DVDR <HL-DT-ST DVDRAM GSA-4083N/1.08> at ata0-master UDMA33 ad4: 152627MB <SAMSUNG HM160HI HR100-08> at ata2-master SATA150 hdac0: HDA Codec #0: Analog Devices AD1981HD hdac0: HDA Codec #1: Conexant (Unknown) pcm0: <HDA Analog Devices AD1981HD PCM #0 Analog> at cad 0 nid 1 on hdac0 pcm1: <HDA Analog Devices AD1981HD PCM #1 Digital> at cad 0 nid 1 on hdac0 SMP: AP CPU #1 Launched! Trying to mount root from ufs:/dev/ad4s1a -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAklvDoUACgkQCnBgS+kUGEvHIACgljhgGyTqyxuJI+o5v7CnvQ7x 4EAAmwfPW1W329FkWPqTcxkWSdTr4DFs =WDri -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Thu Jan 15 10:52:37 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 138021065673 for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 10:52:37 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from mail-ew0-f21.google.com (mail-ew0-f21.google.com [209.85.219.21]) by mx1.freebsd.org (Postfix) with ESMTP id 6ACDB8FC08 for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 10:52:36 +0000 (UTC) (envelope-from onemda@gmail.com) Received: by ewy14 with SMTP id 14so1534240ewy.19 for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 02:52:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=VWgo9/xBkRphBPkH9Rv7JVc1ijJjU5cM9YjiXTQEo20=; b=uqe7eMeFd+SNSsvwhcSFnkCj+w8uVz4k3huvO8JyTbWVjfJ2YV/9FXFfbvqmsHq+Qg t9iEaaXNTpcuhziObM/YUCph0RGoxmW0nbIjbB8hzADHmpvd3P/Z8kjU7B867obtnso9 NJE6c5S1DOquZvqNsLLnEWYn5RcEKd9NCqfCo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=e83mh7194tfrmQBoKwUELxhZZyfaI6sv4DeZkAFO/y14y/FEmjPuGH7lCKMAn32JTN RlpGTvR+/nxXPk1ML/YY0omANnFVOHnlR/YsmUBN4O9jQs3CYda0o/wnwclkrFYMhcZK sysySJq41ak8j5Rgh4EKt+Uq/3jW2ZXcqL5SE= Received: by 10.210.34.19 with SMTP id h19mr1431232ebh.132.1232016755281; Thu, 15 Jan 2009 02:52:35 -0800 (PST) Received: by 10.210.61.13 with HTTP; Thu, 15 Jan 2009 02:52:35 -0800 (PST) Message-ID: <3a142e750901150252v5633f808q71d3fa3ab5050b20@mail.gmail.com> Date: Thu, 15 Jan 2009 10:52:35 +0000 From: "Paul B. Mahol" <onemda@gmail.com> To: "Marc Peters" <marc@sanity.de> In-Reply-To: <496F0E85.5090904@sanity.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <496F0E85.5090904@sanity.de> Cc: freebsd-stable@freebsd.org Subject: Re: kernel panics when connected through wpi to apple extreme ap X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 15 Jan 2009 10:52:37 -0000 On 1/15/09, Marc Peters <marc@sanity.de> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > hello list, > > i have a lenovo t60 with an integrated intel 3945ABG wireless chipset. > when i was running 7.1-PRERELEASE i realised that the network connection > of my wpi died after some time when connected to the mention apple > access point. i had to restart the card and everything went fine, for > some time (about half an hour). since 7.1-RELEASE and now with > 7.1-STABLE the kernel panics with a fatal trap and dumps it's core after > some minutes (this output ist from -RELEASE-p1, but it's identical to > the one i got from -STABLE): > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0xffff > fault code = supervisor read, page not present > instruction pointer = 0x20:0xc0deadfc > stack pointer = 0x28:0xe58bbbe0 > frame pointer = 0x28:0xe58bbc9c > 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 = 25 (wpi0 taskq) > trap number = 12 > panic: page fault > cpuid = 0 > Uptime: 6m 14s > Physical memory: 2034 MB > Dumping 149 MB: 134 118 192 86 70 65 38 22 6 > Dump complete > Automatic reboot in 15 seconds - press a key on the console to abort > > when i run this box connected to a netgear-ap i have at home, everything > is fine (and was before, no panics, no connection dropping). i have the > dump at hand, but since it's 150 MB i won't send it around via mail. if > anyone is interested, i can upload it somewhere and send the link. > > anyone any ideas? Enable textdump(8) and post bt output from debuger once panic happen. (I'm not going to download 150MB) > marc > > dmesg: > > Copyright (c) 1992-2009 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 7.1-STABLE #0: Wed Jan 14 13:23:00 CET 2009 > root@lappi.agentur.local:/usr/obj/usr/src/sys/GENERIC_DRM > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz (1995.02-MHz > 686-class CPU) > Origin = "GenuineIntel" Id = 0x6f6 Stepping = 6 > > Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > Features2=0xe3bd<SSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM> > AMD Features=0x20100000<NX,LM> > AMD Features2=0x1<LAHF> > Cores per package: 2 > real memory = 2146238464 (2046 MB) > avail memory = 2090221568 (1993 MB) > ACPI APIC Table: <LENOVO TP-79 > > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > ACPI Warning (tbfadt-0505): Optional field "Gpe1Block" has zero address > or length: 0 102C/0 [20070320] > ioapic0: Changing APIC ID to 1 > ioapic0 <Version 2.0> irqs 0-23 on motherboard > kbd1 at kbdmux0 > ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) > acpi0: <LENOVO TP-79> on motherboard > acpi0: [ITHREAD] > acpi_ec0: <Embedded Controller: GPE 0x1c, ECDT> port 0x62,0x66 on acpi0 > acpi0: Power Button (fixed) > acpi0: reservation of 0, a0000 (3) failed > acpi0: reservation of 100000, 7ff00000 (3) failed > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 > acpi_hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on > acpi0 > Timecounter "HPET" frequency 14318180 Hz quality 900 > acpi_lid0: <Control Method Lid Switch> on acpi0 > acpi_button0: <Sleep Button> on acpi0 > pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0 > pci0: <ACPI PCI bus> on pcib0 > pcib1: <ACPI PCI-PCI bridge> irq 16 at device 1.0 on pci0 > pci1: <ACPI PCI bus> on pcib1 > vgapci0: <VGA-compatible display> port 0x2000-0x20ff mem > 0xd8000000-0xdfffffff,0xee100000-0xee10ffff irq 16 at device 0.0 on pci1 > drm0: <ATI Mobility Radeon X1400> on vgapci0 > vgapci0: child drm0 requested pci_enable_busmaster > info: [drm] Initialized radeon 1.29.0 20080613 > hdac0: <Intel 82801G High Definition Audio Controller> mem > 0xee400000-0xee403fff irq 17 at device 27.0 on pci0 > hdac0: HDA Driver Revision: 20090110_0123 > hdac0: [ITHREAD] > pcib2: <ACPI PCI-PCI bridge> irq 20 at device 28.0 on pci0 > pci2: <ACPI PCI bus> on pcib2 > em0: <Intel(R) PRO/1000 Network Connection 6.9.6> port 0x3000-0x301f mem > 0xee000000-0xee01ffff irq 16 at device 0.0 on pci2 > em0: Using MSI interrupt > em0: [FILTER] > em0: Ethernet address: 00:16:41:e3:4a:ff > pcib3: <ACPI PCI-PCI bridge> irq 21 at device 28.1 on pci0 > pci3: <ACPI PCI bus> on pcib3 > wpi0: <Intel(R) PRO/Wireless 3945ABG> mem 0xedf00000-0xedf00fff irq 17 > at device 0.0 on pci3 > wpi0: Ethernet address: 00:19:d2:07:cf:36 > wpi0: [ITHREAD] > pcib4: <ACPI PCI-PCI bridge> irq 22 at device 28.2 on pci0 > pci4: <ACPI PCI bus> on pcib4 > pcib5: <ACPI PCI-PCI bridge> irq 23 at device 28.3 on pci0 > pci12: <ACPI PCI bus> on pcib5 > uhci0: <UHCI (generic) USB controller> port 0x1800-0x181f irq 16 at > device 29.0 on pci0 > uhci0: [GIANT-LOCKED] > uhci0: [ITHREAD] > usb0: <UHCI (generic) USB controller> on uhci0 > usb0: USB revision 1.0 > uhub0: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0 > uhub0: 2 ports with 2 removable, self powered > uhci1: <UHCI (generic) USB controller> port 0x1820-0x183f irq 17 at > device 29.1 on pci0 > uhci1: [GIANT-LOCKED] > uhci1: [ITHREAD] > usb1: <UHCI (generic) USB controller> on uhci1 > usb1: USB revision 1.0 > uhub1: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb1 > uhub1: 2 ports with 2 removable, self powered > uhci2: <UHCI (generic) USB controller> port 0x1840-0x185f irq 18 at > device 29.2 on pci0 > uhci2: [GIANT-LOCKED] > uhci2: [ITHREAD] > usb2: <UHCI (generic) USB controller> on uhci2 > usb2: USB revision 1.0 > uhub2: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb2 > uhub2: 2 ports with 2 removable, self powered > uhci3: <UHCI (generic) USB controller> port 0x1860-0x187f irq 19 at > device 29.3 on pci0 > uhci3: [GIANT-LOCKED] > uhci3: [ITHREAD] > usb3: <UHCI (generic) USB controller> on uhci3 > usb3: USB revision 1.0 > uhub3: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb3 > uhub3: 2 ports with 2 removable, self powered > ehci0: <Intel 82801GB/R (ICH7) USB 2.0 controller> mem > 0xee404000-0xee4043ff irq 19 at device 29.7 on pci0 > ehci0: [GIANT-LOCKED] > ehci0: [ITHREAD] > usb4: EHCI version 1.0 > usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 > usb4: <Intel 82801GB/R (ICH7) USB 2.0 controller> on ehci0 > usb4: USB revision 2.0 > uhub4: <Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb4 > uhub4: 8 ports with 8 removable, self powered > pcib6: <ACPI PCI-PCI bridge> at device 30.0 on pci0 > pci21: <ACPI PCI bus> on pcib6 > cbb0: <TI1510 PCI-CardBus Bridge> mem 0xe4300000-0xe4300fff irq 16 at > device 0.0 on pci21 > cardbus0: <CardBus bus> on cbb0 > pccard0: <16-bit PCCard bus> on cbb0 > cbb0: [ITHREAD] > isab0: <PCI-ISA bridge> at device 31.0 on pci0 > isa0: <ISA bus> on isab0 > atapci0: <Intel ICH7 UDMA100 controller> port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1880-0x188f at device 31.1 on pci0 > ata0: <ATA channel 0> on atapci0 > ata0: [ITHREAD] > atapci1: <Intel AHCI controller> port > 0x18c8-0x18cf,0x18ac-0x18af,0x18c0-0x18c7,0x18a8-0x18ab,0x18b0-0x18bf > mem 0xee404400-0xee4047ff irq 16 at device 31.2 on pci0 > atapci1: [ITHREAD] > atapci1: AHCI Version 01.10 controller with 4 ports detected > ata2: <ATA channel 0> on atapci1 > ata2: [ITHREAD] > ata3: <ATA channel 1> on atapci1 > ata3: port not implemented > ata3: [ITHREAD] > ata4: <ATA channel 2> on atapci1 > ata4: port not implemented > ata4: [ITHREAD] > ata5: <ATA channel 3> on atapci1 > ata5: port not implemented > ata5: [ITHREAD] > pci0: <serial bus, SMBus> at device 31.3 (no driver attached) > acpi_tz0: <Thermal Zone> on acpi0 > acpi_tz1: <Thermal Zone> on acpi0 > atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0 > atkbd0: <AT Keyboard> irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > atkbd0: [ITHREAD] > psm0: <PS/2 Mouse> irq 12 on atkbdc0 > psm0: [GIANT-LOCKED] > psm0: [ITHREAD] > psm0: model Generic PS/2 mouse, device ID 0 > battery0: <ACPI Control Method Battery> on acpi0 > acpi_acad0: <AC Adapter> on acpi0 > acpi_ibm0: <IBM ThinkPad ACPI Extras> on acpi0 > cpu0: <ACPI CPU> on acpi0 > est0: <Enhanced SpeedStep Frequency Control> on cpu0 > p4tcc0: <CPU Frequency Thermal Control> on cpu0 > cpu1: <ACPI CPU> on acpi0 > est1: <Enhanced SpeedStep Frequency Control> on cpu1 > p4tcc1: <CPU Frequency Thermal Control> on cpu1 > pmtimer0 on isa0 > orm0: <ISA Option ROMs> at iomem > 0xd0000-0xd0fff,0xd1000-0xd1fff,0xdc000-0xdffff,0xe0000-0xeffff pnpid > ORM0000 on isa0 > ppc0: parallel port not found. > sc0: <System console> at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > sio0: configured irq 4 not in bitmap of probed irqs 0 > sio0: port may not be enabled > sio0: configured irq 4 not in bitmap of probed irqs 0 > sio0: port may not be enabled > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 8250 or not responding > sio0: [FILTER] > sio1: configured irq 3 not in bitmap of probed irqs 0 > sio1: port may not be enabled > vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > ums0: <Logitech USB-PS/2 Optical Mouse, class 0/0, rev 2.00/27.20, addr > 2> on uhub0 > ums0: 8 buttons and Z dir. > ugen0: <STMicroelectronics Biometric Coprocessor, class 0/0, rev > 1.00/0.01, addr 2> on uhub3 > Timecounters tick every 1.000 msec > acd0: DVDR <HL-DT-ST DVDRAM GSA-4083N/1.08> at ata0-master UDMA33 > ad4: 152627MB <SAMSUNG HM160HI HR100-08> at ata2-master SATA150 > hdac0: HDA Codec #0: Analog Devices AD1981HD > hdac0: HDA Codec #1: Conexant (Unknown) > pcm0: <HDA Analog Devices AD1981HD PCM #0 Analog> at cad 0 nid 1 on hdac0 > pcm1: <HDA Analog Devices AD1981HD PCM #1 Digital> at cad 0 nid 1 on hdac0 > SMP: AP CPU #1 Launched! > Trying to mount root from ufs:/dev/ad4s1a > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.9 (FreeBSD) > > iEYEARECAAYFAklvDoUACgkQCnBgS+kUGEvHIACgljhgGyTqyxuJI+o5v7CnvQ7x > 4EAAmwfPW1W329FkWPqTcxkWSdTr4DFs > =WDri > -----END PGP SIGNATURE----- > _______________________________________________ > 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" > -- Paul From owner-freebsd-stable@FreeBSD.ORG Thu Jan 15 11:47:46 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9C752106567D for <freebsd-stable@FreeBSD.ORG>; Thu, 15 Jan 2009 11:47:46 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (unknown [IPv6:2a01:170:102f::2]) by mx1.freebsd.org (Postfix) with ESMTP id 195CC8FC14 for <freebsd-stable@FreeBSD.ORG>; Thu, 15 Jan 2009 11:47:45 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.3/8.14.3) with ESMTP id n0FBlc2Z066047; Thu, 15 Jan 2009 12:47:38 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.3/8.14.3/Submit) id n0FBlbiU066046; Thu, 15 Jan 2009 12:47:37 +0100 (CET) (envelope-from olli) Date: Thu, 15 Jan 2009 12:47:37 +0100 (CET) Message-Id: <200901151147.n0FBlbiU066046@lurza.secnetix.de> From: Oliver Fromme <olli@lurza.secnetix.de> To: freebsd-stable@FreeBSD.ORG, andrew-freebsd@areilly.bpc-users.org In-Reply-To: <20090115051422.GA59032@duncan.reilly.home> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (FreeBSD/6.4-PRERELEASE-20080904 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Thu, 15 Jan 2009 12:47:39 +0100 (CET) Cc: Subject: Re: How to get djbdns to start early enough to satisfy ntpd at boot? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG, andrew-freebsd@areilly.bpc-users.org List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 15 Jan 2009 11:47:47 -0000 Andrew Reilly wrote: > So: does anyone know how to modify the boot-time order so that > svscan starts at (or before) the point in the boot cycle where > BIND would, on other systems? I suspect that it should be > possible by changing the PROVIDE: in svscan.sh to include one of > the things REQUIRE:'d by ntpd. Or perhaps the REQUIRE: LOGIN in > svscan.sh is incompatible with the BEFORE: LOGIN in ntpd? I think "BEFORE: ntpd" should be sufficient. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "Unix gives you just enough rope to hang yourself -- and then a couple of more feet, just to be sure." -- Eric Allman From owner-freebsd-stable@FreeBSD.ORG Thu Jan 15 12:00:17 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AA43E10656BB for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 12:00:17 +0000 (UTC) (envelope-from ben@morrow.me.uk) Received: from plesk-mail01.plus.net (plesk-mail01.plus.net [212.56.83.229]) by mx1.freebsd.org (Postfix) with ESMTP id 0B6878FC24 for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 12:00:16 +0000 (UTC) (envelope-from ben@morrow.me.uk) Received: (qmail 31383 invoked from network); 15 Jan 2009 12:00:15 +0000 Received: from host81-141-107-54.wlms-broadband.com (HELO osiris.mauzo.dyndns.org) (81.141.107.54) by plesk-mail01.plus.net with SMTP; 15 Jan 2009 12:00:14 +0000 Received: (qmail 67128 invoked by uid 1001); 15 Jan 2009 12:00:01 -0000 Date: Thu, 15 Jan 2009 12:00:01 +0000 From: Ben Morrow <ben@morrow.me.uk> To: freebsd-stable@freebsd.org Message-ID: <20090115120001.GA23934@osiris.mauzo.dyndns.org> Mail-Followup-To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="oyUTqETQ0mS9luUI" Content-Disposition: inline In-Reply-To: <20090115051422.GA59032@duncan.reilly.home> X-Newsgroups: gmane.os.freebsd.stable Organization: Who, me? User-Agent: Mutt/1.5.17 (2007-11-01) Subject: Re: How to get djbdns to start early enough to satisfy ntpd at boot? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 15 Jan 2009 12:00:21 -0000 --oyUTqETQ0mS9luUI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Quoth Andrew Reilly <andrew-freebsd@areilly.bpc-users.org>: > > So: does anyone know how to modify the boot-time order so that > svscan starts at (or before) the point in the boot cycle where > BIND would, on other systems? I suspect that it should be > possible by changing the PROVIDE: in svscan.sh to include one of > the things REQUIRE:'d by ntpd. Or perhaps the REQUIRE: LOGIN in > svscan.sh is incompatible with the BEFORE: LOGIN in ntpd? > > Has any other user of dnscache encountered and solved this > problem? I have, in my svscan.sh, # PROVIDE: svscan # REQUIRE: SERVERS cleanvar and I also have a /usr/local/etc/rc.d/dnscache which looks like #!/bin/sh # PROVIDE: named # REQUIRE: svscan . /etc/rc.subr . /usr/local/etc/svc.subr name="dnscache" rcvar=`set_rcvar` : ${dnscache_enable:="NO"} load_rc_config $name load_svc_subr_config run_rc_command "$1" and a /usr/local/etc/svc.subr as attached. It's somewhat more general than is needed for dnscache, as I also use it to start qmail. Basically: the PROVIDE: named line is needed to get dnscache up before ntpd, and the REQUIRE: LOGIN line needs to be changed. Ben --oyUTqETQ0mS9luUI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline; filename="svc.subr" # # Subroutines for handling services under the control of svscan(8). # Requires rc.subr is loaded first. # load_svc_subr_config () { load_rc_config_var svscan svscan_servicedir : ${svscan_servicedir:=/var/service} : ${svc:=/usr/local/bin/svc} : ${svok:=/usr/local/bin/svok} : ${svstat:=/usr/local/bin/svstat} : ${svcname:=${name}} : ${service_dir:=${svscan_servicedir}/${svcname}} : ${svok_timeout:=30} : ${svstat_timeout:=30} : ${start_cmd:=svc_subr_start} : ${stop_cmd:=svc_subr_stop} : ${restart_cmd:=svc_subr_restart} : ${extra_commands:="status reload flush"} : ${status_cmd:=svc_subr_status} : ${reload_cmd:=svc_subr_reload} : ${flush_cmd:=svc_subr_flush} } svc_subr_isup () { $svstat $1 | grep -q ": up" } svc_subr_isdown () { $svstat $1 | grep -q ": down" } svc_subr_waitfor () { local n check timeout err check="$1" timeout=$2 err="$3" n=0 while [ $n -lt $timeout ] && ! $check $service_dir do sleep 1 n=$(( n + 1 )) done if ! $check $service_dir then echo "$err" >&2 exit 1 fi } svc_subr_start () { echo -n "Checking ${name} is up" svc_subr_waitfor $svok $svok_timeout \ "supervise is not running in ${service_dir}!" $svc -u $service_dir svc_subr_waitfor svc_subr_isup $svstat_timeout \ "${service_dir} won't come up!" echo "." } svc_subr_stop () { echo -n "Bringing ${name} down" $svc -d $service_dir svc_subr_waitfor svc_subr_isdown $svstat_timeout \ "${service_dir} won't come down, trying SIGKILL" svc -k $service_dir svc_subr_waitfor svc_subr_isdown $svstat_timeout \ "${service_dir} won't come down!" echo "." } svc_subr_restart () { echo -n "Sending ${name} a SIGTERM" $svc -t $service_dir echo "." } svc_subr_reload () { echo -n "Sending ${name} a SIGHUP" $svc -h $service_dir echo "." } svc_subr_flush () { echo -n "Sending ${name} a SIGALRM" $svc -a $service_dir echo "." } svc_subr_status () { $svstat $service_dir } --oyUTqETQ0mS9luUI-- From owner-freebsd-stable@FreeBSD.ORG Thu Jan 15 12:07:51 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3BA0D106573A for <freebsd-stable@FreeBSD.org>; Thu, 15 Jan 2009 12:07:51 +0000 (UTC) (envelope-from dan@langille.org) Received: from nyi.unixathome.org (nyi.unixathome.org [64.147.113.42]) by mx1.freebsd.org (Postfix) with ESMTP id DA6B98FC14 for <freebsd-stable@FreeBSD.org>; Thu, 15 Jan 2009 12:07:50 +0000 (UTC) (envelope-from dan@langille.org) Received: from localhost (localhost [127.0.0.1]) by nyi.unixathome.org (Postfix) with ESMTP id 19D28509C4; Thu, 15 Jan 2009 12:07:50 +0000 (GMT) X-Virus-Scanned: amavisd-new at unixathome.org Received: from nyi.unixathome.org ([127.0.0.1]) by localhost (nyi.unixathome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bFPFHacJ3WCF; Thu, 15 Jan 2009 12:07:45 +0000 (GMT) Received: from smtp-auth.unixathome.org (smtp-auth.unixathome.org [10.4.7.7]) (Authenticated sender: hidden) by nyi.unixathome.org (Postfix) with ESMTPSA id 65E95509C7 ; Thu, 15 Jan 2009 12:07:44 +0000 (GMT) Message-ID: <496F26C4.3020702@langille.org> Date: Thu, 15 Jan 2009 07:06:28 -0500 From: Dan Langille <dan@langille.org> Organization: The FreeBSD Diary User-Agent: Thunderbird 2.0.0.19 (X11/20090111) MIME-Version: 1.0 To: "Marat N.Afanasyev" <amarat@ksu.ru> References: <496D374A.3020704@langille.org> <496E9A37.20800@langille.org> <496EA339.6010808@ksu.ru> <496EB43A.8010805@langille.org> <496ECB2A.8080609@ksu.ru> <1295789639.20090115073959@rulez.sk> <496EEE34.4060109@ksu.ru> In-Reply-To: <496EEE34.4060109@ksu.ru> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: Daniel Gerzo <danger@FreeBSD.org>, freebsd-stable@FreeBSD.org Subject: Re: interrupt storm X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 15 Jan 2009 12:08:01 -0000 Marat N.Afanasyev wrote: > Daniel Gerzo wrote: >> Hello Marat, Dan, >> >> I suppose you guys are running amd64? Could you try i386? AFAIR the >> interrupt storms have gone away after I moved my MSI machine to i386 >> on an affected box. >> > > Yes, amd64. unfortunately, moving to i386 is not an option. at least for > me. I have 4 GBytes of memory and I'm planning to install another 4 > GBytes asap. FWIW, I also have 4GB RAM. This box is destined to be a jail server for running regression testing of various projects (e.g Bacula). -- Dan Langille BSDCan - The Technical BSD Conference : http://www.bsdcan.org/ PGCon - The PostgreSQL Conference: http://www.pgcon.org/ From owner-freebsd-stable@FreeBSD.ORG Thu Jan 15 12:21:21 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E34FA10656F7 for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 12:21:21 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from constantine.ticketswitch.com (constantine.ticketswitch.com [IPv6:2002:57e0:1d4e:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id A0AEB8FC1A for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 12:21:21 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from dilbert.rattatosk ([10.64.50.6] helo=dilbert.ticketswitch.com) by constantine.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from <petefrench@ticketswitch.com>) id 1LNRDZ-0000ji-La; Thu, 15 Jan 2009 12:21:01 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from <petefrench@ticketswitch.com>) id 1LNRDZ-0005sH-JS; Thu, 15 Jan 2009 12:21:01 +0000 To: amarat@ksu.ru, dan@langille.org In-Reply-To: <496EB43A.8010805@langille.org> Message-Id: <E1LNRDZ-0005sH-JS@dilbert.ticketswitch.com> From: Pete French <petefrench@ticketswitch.com> Date: Thu, 15 Jan 2009 12:21:01 +0000 Cc: freebsd-stable@freebsd.org Subject: Re: interrupt storm X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 15 Jan 2009 12:21:22 -0000 >>>> kernel: interrupt storm detected on "irq22:"; throttling interrupt >>>> source .... > Opening the case, reading the m/b: > > K9A2 Platinum MSI I hadnt been paying much attention to this thread, but just to let you know that I also saw the same thing on this machine which has an MSI 790FX Platinum motherboard. It was also irq22, and I am also running amd64. In my case I simply disabled the onboard ethernet (which I wasnt using) and the problem went away - but then I only saw the problem once, it wasnt a regular occurrance. If you have an alternative ether card you can drop in thn you could try that... I've never had any problem running FreeBSD on MSI boards, but I recently purchased a new 790GX board, and that will not boot 7.1. Will oput in a PR about that when I have sorted my other 7.1 woes though :-) -pete. From owner-freebsd-stable@FreeBSD.ORG Thu Jan 15 12:46:12 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7D3BB1065680 for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 12:46:12 +0000 (UTC) (envelope-from mkhitrov@gmail.com) Received: from mail-bw0-f20.google.com (mail-bw0-f20.google.com [209.85.218.20]) by mx1.freebsd.org (Postfix) with ESMTP id 0522D8FC1C for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 12:46:11 +0000 (UTC) (envelope-from mkhitrov@gmail.com) Received: by bwz13 with SMTP id 13so3655579bwz.19 for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 04:46:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=A8EtmSgoaZmUx6Wb4kcxGN6PM4CJ6hoLJaddsV3M04c=; b=DHGCI9dDZ85g50QkX6U1O7np5/1IG+OKI4xmPuVBiCAzVMYHjXR41OfbTmKZPN2ZvT geWfbH7oRie2ADQLH/OUTuz5IC9uMWTEkcC5t2YagRydl8EzbRJmbGKuh5ygH5UNRth2 u8hg8jzs2ofz6gdy2K9482IngW9NMuoxKDeyE= 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=KQxbeSg49hgl7uHaKTm5EuS77zTC07J1Vu+iZAoOQwLFx2VsivNoSU60SD07HLKc9i vgNXdVE4UQJGBXYgE5GpGQ1HqALrIVOJMUmnUFTuL/jMFEvLye/SMKwd6Hlz/eXyTRKx WeMPtA10cabx8S+GIwqVw7cOuak8joFUblAHc= MIME-Version: 1.0 Received: by 10.223.110.144 with SMTP id n16mr1512625fap.63.1232022159627; Thu, 15 Jan 2009 04:22:39 -0800 (PST) In-Reply-To: <20090115051422.GA59032@duncan.reilly.home> References: <20090115051422.GA59032@duncan.reilly.home> Date: Thu, 15 Jan 2009 07:22:39 -0500 Message-ID: <26ddd1750901150422t11ca7188hf4f3f25b797f8a61@mail.gmail.com> From: Maxim Khitrov <mkhitrov@gmail.com> To: Andrew Reilly <andrew-freebsd@areilly.bpc-users.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: roam@freebsd.org, freebsd-stable@freebsd.org Subject: Re: How to get djbdns to start early enough to satisfy ntpd at boot? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 15 Jan 2009 12:46:13 -0000 On Thu, Jan 15, 2009 at 12:14 AM, Andrew Reilly <andrew-freebsd@areilly.bpc-users.org> wrote: > Hi there, > > I've been a happy djbdns+tinydns user for many, many years. I > want to keep using it, so answers of the form "bletch! Use ISC > BIND the way BSD intended" will be ignored :-) > > Having said that, one annoying consequence of my transition > some time ago to using ntpd, rather than just setting the clock > once-off with ntpdate as I used to, is that the /etc/rc.d > mechanism starts ntpd before /usr/local/etc/rc.d/svscan.sh > starts svscan, which starts /services/dnscache. That wouldn't > matter if ntpd was a bit sensible and just kept trying to find > its nomminated servers, but it gives up and just sits there not > synchronising time from any reference. So I have to remember to > manually "/etc/rc.d/ntpd restart" every time I reboot. > > So: does anyone know how to modify the boot-time order so that > svscan starts at (or before) the point in the boot cycle where > BIND would, on other systems? I suspect that it should be > possible by changing the PROVIDE: in svscan.sh to include one of > the things REQUIRE:'d by ntpd. Or perhaps the REQUIRE: LOGIN in > svscan.sh is incompatible with the BEFORE: LOGIN in ntpd? > > Has any other user of dnscache encountered and solved this > problem? > I use the following in svscan.sh, no problems with ntpdate or any other service: # PROVIDE: svscan # REQUIRE: FILESYSTEMS netif pf # BEFORE: routing - Max From owner-freebsd-stable@FreeBSD.ORG Thu Jan 15 12:54:04 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from straylight.ringlet.net (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with SMTP id EFD43106564A for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 12:54:02 +0000 (UTC) (envelope-from roam@ringlet.net) Received: (qmail 70315 invoked by uid 1000); 15 Jan 2009 12:53:24 -0000 Date: Thu, 15 Jan 2009 14:53:24 +0200 From: Peter Pentchev <roam@ringlet.net> To: Maxim Khitrov <mkhitrov@gmail.com> Message-ID: <20090115125324.GA1102@straylight.m.ringlet.net> References: <20090115051422.GA59032@duncan.reilly.home> <26ddd1750901150422t11ca7188hf4f3f25b797f8a61@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ZPt4rx8FFjLCG7dd" Content-Disposition: inline In-Reply-To: <26ddd1750901150422t11ca7188hf4f3f25b797f8a61@mail.gmail.com> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-stable@freebsd.org Subject: Re: How to get djbdns to start early enough to satisfy ntpd at boot? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 15 Jan 2009 12:54:04 -0000 --ZPt4rx8FFjLCG7dd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 15, 2009 at 07:22:39AM -0500, Maxim Khitrov wrote: > On Thu, Jan 15, 2009 at 12:14 AM, Andrew Reilly > <andrew-freebsd@areilly.bpc-users.org> wrote: [snip] > > So: does anyone know how to modify the boot-time order so that > > svscan starts at (or before) the point in the boot cycle where > > BIND would, on other systems? I suspect that it should be > > possible by changing the PROVIDE: in svscan.sh to include one of > > the things REQUIRE:'d by ntpd. Or perhaps the REQUIRE: LOGIN in > > svscan.sh is incompatible with the BEFORE: LOGIN in ntpd? > > > > Has any other user of dnscache encountered and solved this > > problem? > > >=20 > I use the following in svscan.sh, no problems with ntpdate or any other s= ervice: >=20 > # PROVIDE: svscan > # REQUIRE: FILESYSTEMS netif pf > # BEFORE: routing Thanks a lot for that! I'll test it on one of my own machines[1] and I'll incorporate it into the port's options in a couple of days. G'luck, Peter [1] Yes, Andrew, I have the same problem on one machine which is only restarted very rarely, so I just drop a curse and restart ntpd and I couldn't be bothered to actually automate it... sorry for that! --=20 Peter Pentchev roam@ringlet.net roam@space.bg roam@FreeBSD.org PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 The rest of this sentence is written in Thailand, on --ZPt4rx8FFjLCG7dd Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAklvMcMACgkQ7Ri2jRYZRVPGcwCeMdPNJDpRYvJVrdEcde/IWal8 eSEAoKSHbCbvmOatXlxTogcwpkdlBJAm =nM04 -----END PGP SIGNATURE----- --ZPt4rx8FFjLCG7dd-- From owner-freebsd-stable@FreeBSD.ORG Thu Jan 15 13:16:02 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> 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 CD6C71065670 for <stable@FreeBSD.org>; Thu, 15 Jan 2009 13:16:02 +0000 (UTC) (envelope-from mike@vintners.net) Received: from vinifera.vintners.net (vinifera.vintners.net [207.229.65.53]) by mx1.freebsd.org (Postfix) with ESMTP id ADAEF8FC1C for <stable@FreeBSD.org>; Thu, 15 Jan 2009 13:16:02 +0000 (UTC) (envelope-from mike@vintners.net) Received: from [127.0.0.1] (brix.vintners.net [209.162.136.18]) by vinifera.vintners.net (8.14.1/8.14.3) with ESMTP id n0FDGJ1c011714 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 15 Jan 2009 05:16:20 -0800 (PST) (envelope-from mike@vintners.net) Message-ID: <496F372B.2010805@vintners.net> Date: Thu, 15 Jan 2009 05:16:27 -0800 From: Mike Lempriere <mike@vintners.net> User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Doug Barton <dougb@FreeBSD.org> References: <496EB76F.9000501@vintners.net> <496EDA18.5090809@FreeBSD.org> In-Reply-To: <496EDA18.5090809@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-6.6 required=6.0 tests=ALL_TRUSTED,AWL,BAYES_00, RGX_BDY_LOCAL_AREA_CODE autolearn=ham version=3.2.3 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on vinifera.vintners.net Cc: stable@FreeBSD.org Subject: Re: named won't start X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 15 Jan 2009 13:16:03 -0000 Thanks for getting back to me... I guess I was a little panicy when I entered my note, I didn't explain much about what I'd already done. There was no named running, 'ps ax | grep named' showed only my grep and syslog. 'rndc' simply returns a "connection refused" error, I assume this is a poor excuse for an error mesage that really indicates that there is no named running to talk to. I believe the 'in use' message is an artifact of the first failure as there is definately no named running. I've just tried named-checkconf (I didn't know about that one -- thank you!) it says nothing, returns zero. Didn't help -- but thanks for trying! Doug Barton wrote: > Mike Lempriere wrote: > > >> loading configuration: address in use >> > > This error generally means that the old named is still running. Try > 'rndc stop', and then do 'ps -ax | grep named'. If you still see > something running do '/etc/rc.d/named stop' check ps again, then when > you're sure no other named is running do '/etc/rc.d/named start' > > >> I believe I did an accurate merge of my named.conf file. >> > > run named-checkconf to be sure that's not your problem. > > > hope this helps, > > Doug > > -- Mike Lempriere- Home: mike@vintners.net Phone: 206-780-2146 Cellphone: 206-200-5902; text pager: mikelemp@tmail.com From owner-freebsd-stable@FreeBSD.ORG Thu Jan 15 13:29:59 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> 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 8A3B2106568A for <stable@freebsd.org>; Thu, 15 Jan 2009 13:29:59 +0000 (UTC) (envelope-from mike@vintners.net) Received: from vinifera.vintners.net (vinifera.vintners.net [207.229.65.53]) by mx1.freebsd.org (Postfix) with ESMTP id 632F98FC37 for <stable@freebsd.org>; Thu, 15 Jan 2009 13:29:59 +0000 (UTC) (envelope-from mike@vintners.net) Received: from [127.0.0.1] (brix.vintners.net [209.162.136.18]) by vinifera.vintners.net (8.14.1/8.14.3) with ESMTP id n0FDUFbX011851 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 15 Jan 2009 05:30:16 -0800 (PST) (envelope-from mike@vintners.net) Message-ID: <496F3A6F.1050505@vintners.net> Date: Thu, 15 Jan 2009 05:30:23 -0800 From: Mike Lempriere <mike@vintners.net> User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: "Sergey N. Voronkov" <serg@tmn.ru> References: <496EB76F.9000501@vintners.net> <20090115044333.GA42029@tmn.ru> In-Reply-To: <20090115044333.GA42029@tmn.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-6.2 required=6.0 tests=ALL_TRUSTED,AWL,BAYES_00, RGX_BDY_BOGUS_SALUT5, RGX_BDY_LOCAL_AREA_CODE autolearn=ham version=3.2.3 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on vinifera.vintners.net Cc: stable@freebsd.org Subject: Re: named won't start X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 15 Jan 2009 13:30:09 -0000 I'm not real clear on what item 6 means. However all of my specified zones have at least one NS and one A record. Does this mean I'm Ok? Sergey N. Voronkov wrote: > On Wed, Jan 14, 2009 at 08:11:27PM -0800, Mike Lempriere wrote: > >> From /var/log/messages: >> starting BIND 9.4.3-P1 -t /var/named -u bind >> could not get query source dispatcher (0.0.0.0#53) >> loading configuration: address in use >> exiting (due to fatal error) >> >> I had just updated from 5-stable (at 5.5) to 6-stable (at 6.4). Upon >> today's upgrade I got to 7.1. Everything else seems to be be working >> (the machine is basically a webserver), except named. apache is serving >> up pages, but only until my TTL times out... >> >> I so no errors in the builds or installs. I foolwed the instructions in >> UPDATING. I believe I did an accurate merge of my named.conf file. >> >> This is a production machine, with paying customers -- please help! >> Thank you! >> >> > > http://www.fiveanddime.net/bind-9/bind-9.3.1/doc/misc/migration..html > > "6. No Information Leakage between Zones" > > "Sites that were relying on this BIND 8 behaviour need to add any > omitted glue NS records, and any necessary glue A records, to the > parent zone." > > Did You insert NS and A records into parent zone files? > > Serg N. Voronkov, > Sibitex Ltd. > > > > -- Mike Lempriere- Home: mike@vintners.net Phone: 206-780-2146 Cellphone: 206-200-5902; text pager: mikelemp@tmail.com From owner-freebsd-stable@FreeBSD.ORG Thu Jan 15 13:38:47 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> 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 7EFCE106564A for <stable@freebsd.org>; Thu, 15 Jan 2009 13:38:47 +0000 (UTC) (envelope-from mike@vintners.net) Received: from vinifera.vintners.net (vinifera.vintners.net [207.229.65.53]) by mx1.freebsd.org (Postfix) with ESMTP id 44F988FC16 for <stable@freebsd.org>; Thu, 15 Jan 2009 13:38:47 +0000 (UTC) (envelope-from mike@vintners.net) Received: from [127.0.0.1] (brix.vintners.net [209.162.136.18]) by vinifera.vintners.net (8.14.1/8.14.3) with ESMTP id n0FDd4Mm011933 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 15 Jan 2009 05:39:05 -0800 (PST) (envelope-from mike@vintners.net) Message-ID: <496F3C80.3050205@vintners.net> Date: Thu, 15 Jan 2009 05:39:12 -0800 From: Mike Lempriere <mike@vintners.net> User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: "Sergey N. Voronkov" <serg@tmn.ru> References: <496EB76F.9000501@vintners.net> <20090115044333.GA42029@tmn.ru> In-Reply-To: <20090115044333.GA42029@tmn.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-6.2 required=6.0 tests=ALL_TRUSTED,AWL,BAYES_00, RGX_BDY_BOGUS_SALUT5, RGX_BDY_LOCAL_AREA_CODE autolearn=ham version=3.2.3 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on vinifera.vintners.net Cc: stable@freebsd.org Subject: Re: named won't start -- solved X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 15 Jan 2009 13:38:47 -0000 Got it! Thanks Sergey, the migration doc you pinted out below showed me to the real problem. I had an old directive: query-source address * port 53; Commenting this out now allows named to start. I'm getting a working directory is not writable error now, but that's something I should be able to figure out myself! Interestingly enough, I have this same declaration on my secondary machine. That machine just went through the same process, and it did not have this problem... Thanks for all the help guys -- much appreciated! Sergey N. Voronkov wrote: > On Wed, Jan 14, 2009 at 08:11:27PM -0800, Mike Lempriere wrote: > >> From /var/log/messages: >> starting BIND 9.4.3-P1 -t /var/named -u bind >> could not get query source dispatcher (0.0.0.0#53) >> loading configuration: address in use >> exiting (due to fatal error) >> >> I had just updated from 5-stable (at 5.5) to 6-stable (at 6.4). Upon >> today's upgrade I got to 7.1. Everything else seems to be be working >> (the machine is basically a webserver), except named. apache is serving >> up pages, but only until my TTL times out... >> >> I so no errors in the builds or installs. I foolwed the instructions in >> UPDATING. I believe I did an accurate merge of my named.conf file. >> >> This is a production machine, with paying customers -- please help! >> Thank you! >> >> > > http://www.fiveanddime.net/bind-9/bind-9.3.1/doc/misc/migration..html > > "6. No Information Leakage between Zones" > > "Sites that were relying on this BIND 8 behaviour need to add any > omitted glue NS records, and any necessary glue A records, to the > parent zone." > > Did You insert NS and A records into parent zone files? > > Serg N. Voronkov, > Sibitex Ltd. > > > > -- Mike Lempriere- Home: mike@vintners.net Phone: 206-780-2146 Cellphone: 206-200-5902; text pager: mikelemp@tmail.com From owner-freebsd-stable@FreeBSD.ORG Thu Jan 15 13:47:01 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9824B1065673 for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 13:47:01 +0000 (UTC) (envelope-from janm@transactionware.com) Received: from mailout2.pacific.net.au (mailout2-5.pacific.net.au [61.8.2.228]) by mx1.freebsd.org (Postfix) with ESMTP id 559A98FC12 for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 13:47:00 +0000 (UTC) (envelope-from janm@transactionware.com) Received: from mailproxy1.pacific.net.au (mailproxy1.pacific.net.au [61.8.2.162]) by mailout2.pacific.net.au (Postfix) with ESMTP id 5AE48124233 for <freebsd-stable@freebsd.org>; Fri, 16 Jan 2009 00:23:23 +1100 (EST) Received: from mail.transactionware.com (mail.transactionware.com [203.14.245.7]) by mailproxy1.pacific.net.au (Postfix) with SMTP id 3AF978C04 for <freebsd-stable@freebsd.org>; Fri, 16 Jan 2009 00:23:23 +1100 (EST) Received: (qmail 9074 invoked from network); 15 Jan 2009 13:23:44 -0000 Received: from midgard.transactionware.com (192.168.1.55) by dm.transactionware.com with SMTP; 15 Jan 2009 13:23:44 -0000 Received: (qmail 32946 invoked by uid 907); 15 Jan 2009 13:23:21 -0000 Received: from midgard.transactionware.com (HELO jmlaptop) (192.168.1.55) by midgard.transactionware.com (qpsmtpd/0.40) with SMTP; Fri, 16 Jan 2009 00:23:21 +1100 Message-ID: <3D264F4D61AD4E6995464CBA2C5C768E@jmlaptop> From: "Jan Mikkelsen" <janm@transactionware.com> To: "Andrew Reilly" <andrew-freebsd@areilly.bpc-users.org>, <roam@freebsd.org>, <freebsd-stable@freebsd.org> References: <20090115051422.GA59032@duncan.reilly.home> Date: Fri, 16 Jan 2009 00:23:18 +1100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5512 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 Cc: Subject: Re: How to get djbdns to start early enough to satisfy ntpd at boot? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 15 Jan 2009 13:47:01 -0000 Hi, Andrew Reilly wrote: > I've been a happy djbdns+tinydns user for many, many years. I > want to keep using it, so answers of the form "bletch! Use ISC > BIND the way BSD intended" will be ignored :-) ... Well, the other alternative is to ditch ntpd and go to clockspeed the way djb intended ... Regards, Jan :-) From owner-freebsd-stable@FreeBSD.ORG Thu Jan 15 14:17:53 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 33D9D1065672 for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 14:17:53 +0000 (UTC) (envelope-from marc@sanity.de) Received: from mail.adandbreakfast.com (mail.adandbreakfast.com [194.245.32.131]) by mx1.freebsd.org (Postfix) with ESMTP id 849858FC16 for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 14:17:52 +0000 (UTC) (envelope-from marc@sanity.de) Received: from localhost (localhost [127.0.0.1]) by mail.adandbreakfast.com (Postfix) with ESMTP id 8D4898C4053; Thu, 15 Jan 2009 15:17:51 +0100 (CET) Received: from mail.adandbreakfast.com ([194.245.32.131]) by localhost (mail.adandbreakfast.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 19540-10; Thu, 15 Jan 2009 15:17:51 +0100 (CET) Received: from videoschnitt.agentur.local (unknown [192.168.83.220]) by mail.adandbreakfast.com (Postfix) with ESMTP id 414DD8C404E; Thu, 15 Jan 2009 15:17:51 +0100 (CET) Message-ID: <496F458E.6050708@sanity.de> Date: Thu, 15 Jan 2009 15:17:50 +0100 From: Marc Peters <marc@sanity.de> User-Agent: Thunderbird 2.0.0.19 (X11/20090106) MIME-Version: 1.0 To: "Paul B. Mahol" <onemda@gmail.com> References: <496F0E85.5090904@sanity.de> <3a142e750901150252v5633f808q71d3fa3ab5050b20@mail.gmail.com> In-Reply-To: <3a142e750901150252v5633f808q71d3fa3ab5050b20@mail.gmail.com> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at agentur.local Cc: freebsd-stable@freebsd.org Subject: Re: kernel panics when connected through wpi to apple extreme ap X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 15 Jan 2009 14:17:53 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi paul, msgbuf.txt: [snipping dmesg and startup-messages] Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0xffff fault code = supervisor read, page not present instruction pointer = 0x20:0xc0e70dfc stack pointer = 0x28:0xe58bbbe0 frame pointer = 0x28:0xe58bbc9c 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 = 25 (wpi0 taskq) ddb.txt (just bt output here): db> bt Tracing pid 25 tid 100024 td 0xc5189af0 wpi_ops(c52c5000,1,c0b7cf36,0,0,...) at wpi_ops+0x89c taskqueue_run(c52ab200,c52ab21c,0,c0b7cf36,0,...) at taskqueue_run+0x175 taskqueue_thread_loop(c52c69b4,e58bbd38,0,0,0,...) at taskqueue_thread_loop+0xbb fork_exit(c07fb2b0,c52c69b4,e58bbd38) at fork_exit+0x99 fork_trampoline() at fork_trampoline+0x8 - --- trap 0, eip = 0, esp = 0xe58bbd70, ebp = 0 --- version.txt: FreeBSD 7.1-STABLE #0: Thu Jan 15 13:51:12 CET 2009 root@lappi.agentur.local:/usr/obj/usr/src/sys/DEBUG_DRM if you need more information, i will provide it. it took wpi some time to crash, so i stressed it a little bit with an ftp download and a buildworld through an ssh-screen. marc Paul B. Mahol schrieb: > On 1/15/09, Marc Peters <marc@sanity.de> wrote: > hello list, > > i have a lenovo t60 with an integrated intel 3945ABG wireless chipset. > when i was running 7.1-PRERELEASE i realised that the network connection > of my wpi died after some time when connected to the mention apple > access point. i had to restart the card and everything went fine, for > some time (about half an hour). since 7.1-RELEASE and now with > 7.1-STABLE the kernel panics with a fatal trap and dumps it's core after > some minutes (this output ist from -RELEASE-p1, but it's identical to > the one i got from -STABLE): > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0xffff > fault code = supervisor read, page not present > instruction pointer = 0x20:0xc0deadfc > stack pointer = 0x28:0xe58bbbe0 > frame pointer = 0x28:0xe58bbc9c > 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 = 25 (wpi0 taskq) > trap number = 12 > panic: page fault > cpuid = 0 > Uptime: 6m 14s > Physical memory: 2034 MB > Dumping 149 MB: 134 118 192 86 70 65 38 22 6 > Dump complete > Automatic reboot in 15 seconds - press a key on the console to abort > > when i run this box connected to a netgear-ap i have at home, everything > is fine (and was before, no panics, no connection dropping). i have the > dump at hand, but since it's 150 MB i won't send it around via mail. if > anyone is interested, i can upload it somewhere and send the link. > > anyone any ideas? > >> Enable textdump(8) and post bt output from debuger once panic happen. >> (I'm not going to download 150MB) > marc > > dmesg: > > Copyright (c) 1992-2009 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 7.1-STABLE #0: Wed Jan 14 13:23:00 CET 2009 > root@lappi.agentur.local:/usr/obj/usr/src/sys/GENERIC_DRM > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz (1995.02-MHz > 686-class CPU) > Origin = "GenuineIntel" Id = 0x6f6 Stepping = 6 > > Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > Features2=0xe3bd<SSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM> > AMD Features=0x20100000<NX,LM> > AMD Features2=0x1<LAHF> > Cores per package: 2 > real memory = 2146238464 (2046 MB) > avail memory = 2090221568 (1993 MB) > ACPI APIC Table: <LENOVO TP-79 > > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > ACPI Warning (tbfadt-0505): Optional field "Gpe1Block" has zero address > or length: 0 102C/0 [20070320] > ioapic0: Changing APIC ID to 1 > ioapic0 <Version 2.0> irqs 0-23 on motherboard > kbd1 at kbdmux0 > ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) > acpi0: <LENOVO TP-79> on motherboard > acpi0: [ITHREAD] > acpi_ec0: <Embedded Controller: GPE 0x1c, ECDT> port 0x62,0x66 on acpi0 > acpi0: Power Button (fixed) > acpi0: reservation of 0, a0000 (3) failed > acpi0: reservation of 100000, 7ff00000 (3) failed > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 > acpi_hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on > acpi0 > Timecounter "HPET" frequency 14318180 Hz quality 900 > acpi_lid0: <Control Method Lid Switch> on acpi0 > acpi_button0: <Sleep Button> on acpi0 > pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0 > pci0: <ACPI PCI bus> on pcib0 > pcib1: <ACPI PCI-PCI bridge> irq 16 at device 1.0 on pci0 > pci1: <ACPI PCI bus> on pcib1 > vgapci0: <VGA-compatible display> port 0x2000-0x20ff mem > 0xd8000000-0xdfffffff,0xee100000-0xee10ffff irq 16 at device 0.0 on pci1 > drm0: <ATI Mobility Radeon X1400> on vgapci0 > vgapci0: child drm0 requested pci_enable_busmaster > info: [drm] Initialized radeon 1.29.0 20080613 > hdac0: <Intel 82801G High Definition Audio Controller> mem > 0xee400000-0xee403fff irq 17 at device 27.0 on pci0 > hdac0: HDA Driver Revision: 20090110_0123 > hdac0: [ITHREAD] > pcib2: <ACPI PCI-PCI bridge> irq 20 at device 28.0 on pci0 > pci2: <ACPI PCI bus> on pcib2 > em0: <Intel(R) PRO/1000 Network Connection 6.9.6> port 0x3000-0x301f mem > 0xee000000-0xee01ffff irq 16 at device 0.0 on pci2 > em0: Using MSI interrupt > em0: [FILTER] > em0: Ethernet address: 00:16:41:e3:4a:ff > pcib3: <ACPI PCI-PCI bridge> irq 21 at device 28.1 on pci0 > pci3: <ACPI PCI bus> on pcib3 > wpi0: <Intel(R) PRO/Wireless 3945ABG> mem 0xedf00000-0xedf00fff irq 17 > at device 0.0 on pci3 > wpi0: Ethernet address: 00:19:d2:07:cf:36 > wpi0: [ITHREAD] > pcib4: <ACPI PCI-PCI bridge> irq 22 at device 28.2 on pci0 > pci4: <ACPI PCI bus> on pcib4 > pcib5: <ACPI PCI-PCI bridge> irq 23 at device 28.3 on pci0 > pci12: <ACPI PCI bus> on pcib5 > uhci0: <UHCI (generic) USB controller> port 0x1800-0x181f irq 16 at > device 29.0 on pci0 > uhci0: [GIANT-LOCKED] > uhci0: [ITHREAD] > usb0: <UHCI (generic) USB controller> on uhci0 > usb0: USB revision 1.0 > uhub0: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0 > uhub0: 2 ports with 2 removable, self powered > uhci1: <UHCI (generic) USB controller> port 0x1820-0x183f irq 17 at > device 29.1 on pci0 > uhci1: [GIANT-LOCKED] > uhci1: [ITHREAD] > usb1: <UHCI (generic) USB controller> on uhci1 > usb1: USB revision 1.0 > uhub1: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb1 > uhub1: 2 ports with 2 removable, self powered > uhci2: <UHCI (generic) USB controller> port 0x1840-0x185f irq 18 at > device 29.2 on pci0 > uhci2: [GIANT-LOCKED] > uhci2: [ITHREAD] > usb2: <UHCI (generic) USB controller> on uhci2 > usb2: USB revision 1.0 > uhub2: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb2 > uhub2: 2 ports with 2 removable, self powered > uhci3: <UHCI (generic) USB controller> port 0x1860-0x187f irq 19 at > device 29.3 on pci0 > uhci3: [GIANT-LOCKED] > uhci3: [ITHREAD] > usb3: <UHCI (generic) USB controller> on uhci3 > usb3: USB revision 1.0 > uhub3: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb3 > uhub3: 2 ports with 2 removable, self powered > ehci0: <Intel 82801GB/R (ICH7) USB 2.0 controller> mem > 0xee404000-0xee4043ff irq 19 at device 29.7 on pci0 > ehci0: [GIANT-LOCKED] > ehci0: [ITHREAD] > usb4: EHCI version 1.0 > usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 > usb4: <Intel 82801GB/R (ICH7) USB 2.0 controller> on ehci0 > usb4: USB revision 2.0 > uhub4: <Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb4 > uhub4: 8 ports with 8 removable, self powered > pcib6: <ACPI PCI-PCI bridge> at device 30.0 on pci0 > pci21: <ACPI PCI bus> on pcib6 > cbb0: <TI1510 PCI-CardBus Bridge> mem 0xe4300000-0xe4300fff irq 16 at > device 0.0 on pci21 > cardbus0: <CardBus bus> on cbb0 > pccard0: <16-bit PCCard bus> on cbb0 > cbb0: [ITHREAD] > isab0: <PCI-ISA bridge> at device 31.0 on pci0 > isa0: <ISA bus> on isab0 > atapci0: <Intel ICH7 UDMA100 controller> port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1880-0x188f at device 31.1 on pci0 > ata0: <ATA channel 0> on atapci0 > ata0: [ITHREAD] > atapci1: <Intel AHCI controller> port > 0x18c8-0x18cf,0x18ac-0x18af,0x18c0-0x18c7,0x18a8-0x18ab,0x18b0-0x18bf > mem 0xee404400-0xee4047ff irq 16 at device 31.2 on pci0 > atapci1: [ITHREAD] > atapci1: AHCI Version 01.10 controller with 4 ports detected > ata2: <ATA channel 0> on atapci1 > ata2: [ITHREAD] > ata3: <ATA channel 1> on atapci1 > ata3: port not implemented > ata3: [ITHREAD] > ata4: <ATA channel 2> on atapci1 > ata4: port not implemented > ata4: [ITHREAD] > ata5: <ATA channel 3> on atapci1 > ata5: port not implemented > ata5: [ITHREAD] > pci0: <serial bus, SMBus> at device 31.3 (no driver attached) > acpi_tz0: <Thermal Zone> on acpi0 > acpi_tz1: <Thermal Zone> on acpi0 > atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0 > atkbd0: <AT Keyboard> irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > atkbd0: [ITHREAD] > psm0: <PS/2 Mouse> irq 12 on atkbdc0 > psm0: [GIANT-LOCKED] > psm0: [ITHREAD] > psm0: model Generic PS/2 mouse, device ID 0 > battery0: <ACPI Control Method Battery> on acpi0 > acpi_acad0: <AC Adapter> on acpi0 > acpi_ibm0: <IBM ThinkPad ACPI Extras> on acpi0 > cpu0: <ACPI CPU> on acpi0 > est0: <Enhanced SpeedStep Frequency Control> on cpu0 > p4tcc0: <CPU Frequency Thermal Control> on cpu0 > cpu1: <ACPI CPU> on acpi0 > est1: <Enhanced SpeedStep Frequency Control> on cpu1 > p4tcc1: <CPU Frequency Thermal Control> on cpu1 > pmtimer0 on isa0 > orm0: <ISA Option ROMs> at iomem > 0xd0000-0xd0fff,0xd1000-0xd1fff,0xdc000-0xdffff,0xe0000-0xeffff pnpid > ORM0000 on isa0 > ppc0: parallel port not found. > sc0: <System console> at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > sio0: configured irq 4 not in bitmap of probed irqs 0 > sio0: port may not be enabled > sio0: configured irq 4 not in bitmap of probed irqs 0 > sio0: port may not be enabled > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 8250 or not responding > sio0: [FILTER] > sio1: configured irq 3 not in bitmap of probed irqs 0 > sio1: port may not be enabled > vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > ums0: <Logitech USB-PS/2 Optical Mouse, class 0/0, rev 2.00/27.20, addr > 2> on uhub0 > ums0: 8 buttons and Z dir. > ugen0: <STMicroelectronics Biometric Coprocessor, class 0/0, rev > 1.00/0.01, addr 2> on uhub3 > Timecounters tick every 1.000 msec > acd0: DVDR <HL-DT-ST DVDRAM GSA-4083N/1.08> at ata0-master UDMA33 > ad4: 152627MB <SAMSUNG HM160HI HR100-08> at ata2-master SATA150 > hdac0: HDA Codec #0: Analog Devices AD1981HD > hdac0: HDA Codec #1: Conexant (Unknown) > pcm0: <HDA Analog Devices AD1981HD PCM #0 Analog> at cad 0 nid 1 on hdac0 > pcm1: <HDA Analog Devices AD1981HD PCM #1 Digital> at cad 0 nid 1 on hdac0 > SMP: AP CPU #1 Launched! > Trying to mount root from ufs:/dev/ad4s1a _______________________________________________ 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" >> -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAklvRY4ACgkQCnBgS+kUGEuz7ACdEeaBAcz+qj5SSwEYFQ5Pxyfm dGoAoIlpfyYeLqq7K4G1WIWQ2FbVmhsW =jBkd -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Thu Jan 15 14:43:33 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: FreeBSD-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4890E1065673 for <FreeBSD-stable@freebsd.org>; Thu, 15 Jan 2009 14:43:33 +0000 (UTC) (envelope-from vibarus@googlemail.com) Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.28]) by mx1.freebsd.org (Postfix) with ESMTP id 02AF08FC17 for <FreeBSD-stable@freebsd.org>; Thu, 15 Jan 2009 14:43:32 +0000 (UTC) (envelope-from vibarus@googlemail.com) Received: by yx-out-2324.google.com with SMTP id 8so435718yxb.13 for <FreeBSD-stable@freebsd.org>; Thu, 15 Jan 2009 06:43:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=ffJ0UFJPyzmunKSKOVq7GKAFBRUBu8//u559sgdGMOI=; b=R8pBCnCXT16M9pDGSISK0BvtZ3lTlCpqaKP69tGo7rGNKd2MU4ssX2aGqr2izHCt67 Zlls7xg204U714s4UB+KS0J59QP6OonIKPt7a5LCRUiEm6HPV34IULcOwLH4B9LruyhB RD4xDna8kjRhbXC5XS5+jX8YluiVo66kkZX5I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=so2kp0bmTD0qQiDuBiyCzGgqHd7tpPgQAhxK/Hw3nCF/NGZdxrM6haTEir/+ek0v8B 4pRVCaG1rrrS/AXVvSJEazgdu/Kj274GPpKJUTt/EQWB/W6yoDVnxu67pWSuMMe/9ffO h7JId6WRmoMgIiKGJi7ctxOmULBb6wODz7mKQ= Received: by 10.100.96.10 with SMTP id t10mr1143011anb.32.1232029394711; Thu, 15 Jan 2009 06:23:14 -0800 (PST) Received: by 10.100.112.12 with HTTP; Thu, 15 Jan 2009 06:23:14 -0800 (PST) Message-ID: <e4207650901150623l23f5c3c0q71e88cd80170aba7@mail.gmail.com> Date: Thu, 15 Jan 2009 15:23:14 +0100 From: "Vincent Barus" <vibarus@googlemail.com> To: pyunyh@gmail.com In-Reply-To: <20090109121930.GJ30747@cdnetworks.co.kr> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <E1LLFqi-0001Ew-4K@kabab.cs.huji.ac.il> <20090109121930.GJ30747@cdnetworks.co.kr> Cc: FreeBSD-stable@freebsd.org Subject: Re: more marvell marvels X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 15 Jan 2009 14:43:33 -0000 On Fri, Jan 9, 2009 at 1:19 PM, Pyun YongHyeon <pyunyh@gmail.com> wrote: > On Fri, Jan 09, 2009 at 01:48:24PM +0200, Danny Braniss wrote: > > hi, the mb is asus P5K-VM, the onboard nic is, acccording to pciconf: > > > > mskc0@pci0:1:0:0: class=0x020000 card=0x81f81043 chip=0x436411ab > > rev=0x12 hdr=0x00 > > vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)' > > device = '88E8056 Yukon PCI-E Gigabit Ethernet Controller' > > class = network > > subclass = ethernet > > cap 01[48] = powerspec 3 supports D0 D1 D2 D3 current D0 > > cap 03[50] = VPD > > cap 05[5c] = MSI supports 1 message, 64 bit > > cap 10[e0] = PCI-Express 1 legacy endpoint > > > > nothing new here, problems have been reported before, but: > > > > my very first attempt - after a very long time - of booting 7.1-stable, > > produced > > a panic because msk could not find its physio, by the time i had the serial > > console > > attached and working, that problem disappeared :-( > > now, after reboot, it sometimes hangs - because the net is not working, and > > only if > > I unplug the ethernet, (no signs of the driver seeing this), and replug things > > begin > > to work. btw, i had to set > > hw.msk.legacy_intr="1" > > to get things working. > > > > any patches for 7.1-stable to test? > > > > If memory serve me right you have Yukon EC Ultra with 88E1149 PHY, > right? CURRENT has some stability fixes but the source wouldn't be > compiled on stable/7 yet due to KPI differences. I have plan to add > some features in next week which make it possible to use HEAD > version on stable/7. > > I'm not sure the patch for 88E8040 could be applied to stable/7 > but the patch has some fixes for link state handling. Would you > give it try? > http://people.freebsd.org/~yongari/msk/msk.88E8040.patch14 > Note, the 88E8040 patch is not complete yet and may cause other > problems too. > > -- > Regards, > Pyun YongHyeon > _______________________________________________ > 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" > Hi Pyun, are if_msk.c and if_mskreg.h from http://people.freebsd.org/~yongari/msk/ the patched version? With this files I get an error Message regarding MEXTADD(m, buf, MSK_JLEN, msk_jfree, buf, (struct msk_if_softc *)sc_if, 0, EXT_NET_DRV); Is there a "buf," too much? I deleted the second "buf," and I was able to compile the Kernel. But I can't assign an IP with dhcp because msk0 always goes up and down. This is my nic: pci3: domain=0, physical bus=3 found-> vendor=0x11ab, dev=0x4354, revid=0x13 domain=0, bus=3, slot=0, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=5 powerspec 3 supports D0 D1 D2 D3 current D0 MSI supports 1 message, 64 bit map[10]: type Memory, range 64, base 0xf0200000, size 14, enabled none2@pci0:3:0:0: class=0x020000 card=0xca00144d chip=0x435411ab rev=0x13 hdr=0x00 vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)' class = network subclass = ethernet cap 01[48] = powerspec 3 supports D0 D1 D2 D3 current D0 cap 05[5c] = MSI supports 1 message, 64 bit cap 10[c0] = PCI-Express 2 legacy endpoint Regards, ~ vb From owner-freebsd-stable@FreeBSD.ORG Thu Jan 15 15:35:38 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 39FDF10656BC; Thu, 15 Jan 2009 15:35:38 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from constantine.ticketswitch.com (constantine.ticketswitch.com [IPv6:2002:57e0:1d4e:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id EAA4F8FC13; Thu, 15 Jan 2009 15:35:37 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from dilbert.rattatosk ([10.64.50.6] helo=dilbert.ticketswitch.com) by constantine.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from <petefrench@ticketswitch.com>) id 1LNUFg-0002xi-LN; Thu, 15 Jan 2009 15:35:24 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from <petefrench@ticketswitch.com>) id 1LNUFg-0001YK-Gt; Thu, 15 Jan 2009 15:35:24 +0000 To: rwatson@FreeBSD.org In-Reply-To: <alpine.BSF.2.00.0901141339390.24256@fledge.watson.org> Message-Id: <E1LNUFg-0001YK-Gt@dilbert.ticketswitch.com> From: Pete French <petefrench@ticketswitch.com> Date: Thu, 15 Jan 2009 15:35:24 +0000 Cc: freebsd-stable@freebsd.org, drosih@rpi.edu, rblayzor.bulk@inoc.net Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 15 Jan 2009 15:35:38 -0000 Just an update on this - I tried the various kernels, but now the machine is not locking up at all. As I havent actually chnaged anything then this does not make me as happy as you might expect. I don;t know what to do now - I daare not upgrade the machines to an OS that I know locks, but if I cant make it lock then it is impossible to get any useful debugging info out of. maybe waiting for 7.2 is the best move... -pete. From owner-freebsd-stable@FreeBSD.ORG Thu Jan 15 15:48:18 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A7A0D1065677 for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 15:48:18 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 833AB8FC14 for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 15:48:18 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id 3C47946B58; Thu, 15 Jan 2009 10:48:18 -0500 (EST) Date: Thu, 15 Jan 2009 15:48:18 +0000 (GMT) From: Robert Watson <rwatson@FreeBSD.org> X-X-Sender: robert@fledge.watson.org To: Pete French <petefrench@ticketswitch.com> In-Reply-To: <E1LNUFg-0001YK-Gt@dilbert.ticketswitch.com> Message-ID: <alpine.BSF.2.00.0901151545001.45995@fledge.watson.org> References: <E1LNUFg-0001YK-Gt@dilbert.ticketswitch.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org, drosih@rpi.edu, rblayzor.bulk@inoc.net Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 15 Jan 2009 15:48:19 -0000 On Thu, 15 Jan 2009, Pete French wrote: > Just an update on this - I tried the various kernels, but now the machine is > not locking up at all. As I havent actually chnaged anything then this does > not make me as happy as you might expect. I don;t know what to do now - I > daare not upgrade the machines to an OS that I know locks, but if I cant > make it lock then it is impossible to get any useful debugging info out of. > maybe waiting for 7.2 is the best move... Well, one slightly pessimistic (or realistic) view says that all software contains bugs, it's just a question of whether or not your workload and environment trigger those bugs in a noticeable way. Given the inconsistency of the symptoms, I wouldn't preclude something environmental: could it be that it was the bottom, or more likely, top box in a rack and that your air conditioning isn't quite as effective there when the outside temperature is above/below some threshold? Alternatively, could it be that the workload changed very slightly -- you're doing less DNS queries, or the network latency to the DNS server changed? Certainly, whoever gave the advise on checking BIOS revisions is right: you can spend a lot of time tracking down a bug to realize that one box has a slightly different BIOS rev and therefore does/doesn't suffer from an obscure SMI bug. In any case, if it starts to reproduceably recur, send out mail and we can see if we can track it down some more. BTW, did you establish if the version of iLo you have has a remote NMI? I seem to recall that some do, and being able to deliver an NMI is really quite valuable. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-stable@FreeBSD.ORG Thu Jan 15 15:59:02 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 282921065736; Thu, 15 Jan 2009 15:59:02 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from constantine.ticketswitch.com (constantine.ticketswitch.com [IPv6:2002:57e0:1d4e:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id 5EC778FC0A; Thu, 15 Jan 2009 15:59:01 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from dilbert.rattatosk ([10.64.50.6] helo=dilbert.ticketswitch.com) by constantine.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from <petefrench@ticketswitch.com>) id 1LNUcS-0003GO-91; Thu, 15 Jan 2009 15:58:56 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from <petefrench@ticketswitch.com>) id 1LNUcS-0001dY-5e; Thu, 15 Jan 2009 15:58:56 +0000 To: rwatson@FreeBSD.org In-Reply-To: <alpine.BSF.2.00.0901151545001.45995@fledge.watson.org> Message-Id: <E1LNUcS-0001dY-5e@dilbert.ticketswitch.com> From: Pete French <petefrench@ticketswitch.com> Date: Thu, 15 Jan 2009 15:58:56 +0000 Cc: freebsd-stable@freebsd.org, drosih@rpi.edu, rblayzor.bulk@inoc.net Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 15 Jan 2009 15:59:03 -0000 > Given the inconsistency of the symptoms, I wouldn't preclude something > environmental: could it be that it was the bottom, or more likely, top box in > a rack and that your air conditioning isn't quite as effective there when the > outside temperature is above/below some threshold? It's a possibility - but the two machines which were exhibiting the fault are in Slough and Baton Rouge respectively, so under very diferent cliatic conditions. Howevere, something, has chhnaged to make it stop locking up! The USA one was doing it every couple of hours at the start of the week, and the UK on wouldnt last more than half an hour at one point. > Alternatively, could it be that the workload changed very slightly -- you're > doing less DNS queries, or the network latency to the DNS server changed? Also a possibility - that workload is entirely dependent on customer behaviour which is an unpredictable beast! > Certainly, whoever gave the advise on checking BIOS revisions is right: you > can spend a lot of time tracking down a bug to realize that one box has a > slightly different BIOS rev and therefore does/doesn't suffer from an obscure > SMI bug. Yes, thats next on my list - make sure they are all on the same version. > In any case, if it starts to reproduceably recur, send out mail and we can see > if we can track it down some more. BTW, did you establish if the version of > iLo you have has a remote NMI? I seem to recall that some do, and being able > to deliver an NMI is really quite valuable. OK, thanks. My iiLO2 appears to have the ability to generate an NMI oon demand, so that could be used if/whhen the fault crops up again. thanks, will let this lie for now and resurrect the thread when I can get some more useful data. -pete. From owner-freebsd-stable@FreeBSD.ORG Thu Jan 15 16:04:49 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DAF3B10656C5 for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 16:04:49 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id B270B8FC08 for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 16:04:49 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id 6D2A746B88; Thu, 15 Jan 2009 11:04:49 -0500 (EST) Date: Thu, 15 Jan 2009 16:04:49 +0000 (GMT) From: Robert Watson <rwatson@FreeBSD.org> X-X-Sender: robert@fledge.watson.org To: Pete French <petefrench@ticketswitch.com> In-Reply-To: <E1LNUcS-0001dY-5e@dilbert.ticketswitch.com> Message-ID: <alpine.BSF.2.00.0901151602070.45995@fledge.watson.org> References: <E1LNUcS-0001dY-5e@dilbert.ticketswitch.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org, drosih@rpi.edu, rblayzor.bulk@inoc.net Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 15 Jan 2009 16:04:53 -0000 On Thu, 15 Jan 2009, Pete French wrote: >> In any case, if it starts to reproduceably recur, send out mail and we can >> see if we can track it down some more. BTW, did you establish if the >> version of iLo you have has a remote NMI? I seem to recall that some do, >> and being able to deliver an NMI is really quite valuable. > > OK, thanks. My iiLO2 appears to have the ability to generate an NMI oon > demand, so that could be used if/whhen the fault crops up again. > > thanks, will let this lie for now and resurrect the thread when I can get > some more useful data. Excellent WRT NMI. As long as you have DDB, KDB, and BREAK_TO_DEBUGGER compiled into the kernel, generating that should reliably get you into the debugger. If it's possible to keep running with INVARIANTS and WITNESS, or just INVARIANTS if WITNESS slows things down too much, that would be desirable. You might want to give the NMI a test run just to make sure it behaves as you think it should, though -- be aware that if DDB/KDB aren't compiled into the kernel, then an NMI will panic the box. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-stable@FreeBSD.ORG Thu Jan 15 17:19:26 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8343F106566B; Thu, 15 Jan 2009 17:19:26 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from constantine.ticketswitch.com (constantine.ticketswitch.com [IPv6:2002:57e0:1d4e:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id 3FFF88FC16; Thu, 15 Jan 2009 17:19:26 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from dilbert.rattatosk ([10.64.50.6] helo=dilbert.ticketswitch.com) by constantine.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from <petefrench@ticketswitch.com>) id 1LNVsF-0004Ng-24; Thu, 15 Jan 2009 17:19:19 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from <petefrench@ticketswitch.com>) id 1LNVsF-0000WG-0T; Thu, 15 Jan 2009 17:19:19 +0000 To: rwatson@FreeBSD.org In-Reply-To: <alpine.BSF.2.00.0901151602070.45995@fledge.watson.org> Message-Id: <E1LNVsF-0000WG-0T@dilbert.ticketswitch.com> From: Pete French <petefrench@ticketswitch.com> Date: Thu, 15 Jan 2009 17:19:19 +0000 Cc: freebsd-stable@freebsd.org, drosih@rpi.edu, rblayzor.bulk@inoc.net Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 15 Jan 2009 17:19:26 -0000 > desirable. You might want to give the NMI a test run just to make sure it > behaves as you think it should, though -- be aware that if DDB/KDB aren't > compiled into the kernel, then an NMI will panic the box. Unfortunately it does this... http://toybox.twisted.org.uk/~pete/71_nmi1.png That is locked up too - hitting return does nothing. I was hoping it was just garbled output but had actually gone to the debugger. Apparently not. Thats with a config file containing KDB, DDB and BREAK_TO_DEBUGGER, which does work as I have tested it with CTRL_ALT_ESC. Mmmmm.... -pete. From owner-freebsd-stable@FreeBSD.ORG Thu Jan 15 17:49:12 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 876761065672; Thu, 15 Jan 2009 17:49:12 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 61D1D8FC14; Thu, 15 Jan 2009 17:49:12 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id CF69F46B17; Thu, 15 Jan 2009 12:49:11 -0500 (EST) Date: Thu, 15 Jan 2009 17:49:11 +0000 (GMT) From: Robert Watson <rwatson@FreeBSD.org> X-X-Sender: robert@fledge.watson.org To: Pete French <petefrench@ticketswitch.com> In-Reply-To: <E1LNVsF-0000WG-0T@dilbert.ticketswitch.com> Message-ID: <alpine.BSF.2.00.0901151747461.45995@fledge.watson.org> References: <E1LNVsF-0000WG-0T@dilbert.ticketswitch.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org, drosih@rpi.edu, jhb@FreeBSD.org, rblayzor.bulk@inoc.net Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 15 Jan 2009 17:49:13 -0000 On Thu, 15 Jan 2009, Pete French wrote: >> desirable. You might want to give the NMI a test run just to make sure it >> behaves as you think it should, though -- be aware that if DDB/KDB aren't >> compiled into the kernel, then an NMI will panic the box. > > Unfortunately it does this... > > http://toybox.twisted.org.uk/~pete/71_nmi1.png > > That is locked up too - hitting return does nothing. I was hoping it was > just garbled output but had actually gone to the debugger. Apparently not. > > Thats with a config file containing KDB, DDB and BREAK_TO_DEBUGGER, which > does work as I have tested it with CTRL_ALT_ESC. Er, that's rather upsetting. John, do you have any ideas about this? Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-stable@FreeBSD.ORG Thu Jan 15 20:10:15 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D8F7C1065676; Thu, 15 Jan 2009 20:10:15 +0000 (UTC) (envelope-from dimitry@andric.com) Received: from tensor.andric.com (cl-327.ede-01.nl.sixxs.net [IPv6:2001:7b8:2ff:146::2]) by mx1.freebsd.org (Postfix) with ESMTP id 98CA78FC16; Thu, 15 Jan 2009 20:10:15 +0000 (UTC) (envelope-from dimitry@andric.com) Received: from [IPv6:2001:7b8:3a7:0:9495:274b:b36c:ce34] (unknown [IPv6:2001:7b8:3a7:0:9495:274b:b36c:ce34]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id B206311F838; Thu, 15 Jan 2009 21:10:13 +0100 (CET) Message-ID: <496F9823.4060503@andric.com> Date: Thu, 15 Jan 2009 21:10:11 +0100 From: Dimitry Andric <dimitry@andric.com> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.1b3pre) Gecko/20090108 Shredder/3.0b2pre MIME-Version: 1.0 To: Jung-uk Kim <jkim@FreeBSD.org> References: <8dfae1c10901070639x67945324jeeecfcac647d7976@mail.gmail.com> <20090113050223.GH46346@cdnetworks.co.kr> <496CB2E7.2060902@andric.com> <200901131806.02868.jkim@FreeBSD.org> In-Reply-To: <200901131806.02868.jkim@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: pyunyh@gmail.com, freebsd-stable@FreeBSD.org, eugene@donpac.ru Subject: Re: FreeBSD 7.1 Breaks re and rl Network Interface Drivers X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 15 Jan 2009 20:10:16 -0000 On 2009-01-14 00:05, Jung-uk Kim wrote: > Can you try one of the following patches? > > -CURRENT: http://people.freebsd.org/~jkim/re/re.current.diff > -STABLE: http://people.freebsd.org/~jkim/re/re.stable.diff > > These patches contain all patches suggested by me and yongari and an > additional patch, which may (or may not) decrease the initial setup > time. I have applied the -STABLE patch, and while this doesn't have much influence on the initial setup time, it does seem to solve the problem of not being able to send any packets. From owner-freebsd-stable@FreeBSD.ORG Thu Jan 15 20:29:53 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0067C1065672 for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 20:29:52 +0000 (UTC) (envelope-from ehrmann@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.31]) by mx1.freebsd.org (Postfix) with ESMTP id AB1FF8FC18 for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 20:29:52 +0000 (UTC) (envelope-from ehrmann@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so522570ywe.13 for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 12:29:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=cC4J+lqExD69QHn5O3LTulmMwA2nBhoi2eGACbUSyK0=; b=c0lZdvBv2ZOfj9w5Kp08IYg8/q6OudOTq0WIH7DW/aghbLknk8hqaQqQhCboIMM9jo RCgLWxnm0A1A4F/PtYaGMKeFESI981TeU9/7K0NQFPUh1jkeEGhVvbbjHGbTSJ4hNwGH 32KPwAr6SHXU3xAWxtNE6Wp4AocXwyeiLb+Ds= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=AWMy7sC4I6GKFHlxPT3wKcSMq/xYzKGv22KUUGAMV9FaVKs7t6a9D33ly6Kws7cRtv GDxi20WukUtCMqlDby1Q3l5lXWTXdJnaa2v9CNNY+HF2pNKWCKhlCmuZdhXz+mlmqkCb yriVREMOjtt0WULS1ExQkaAEi3TqPckCGwbWw= Received: by 10.100.112.9 with SMTP id k9mr1417203anc.65.1232049484967; Thu, 15 Jan 2009 11:58:04 -0800 (PST) Received: by 10.100.45.1 with HTTP; Thu, 15 Jan 2009 11:58:04 -0800 (PST) Message-ID: <6e0e5340901151158n5108ba8ct6af8fb270b10b75b@mail.gmail.com> Date: Thu, 15 Jan 2009 11:58:04 -0800 From: "David Ehrmann" <ehrmann@gmail.com> To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: zfs drive keeps failing between export and import X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 15 Jan 2009 20:29:53 -0000 I have a zpool that consists for a two-drive mirror. The two times I took the zpool offline, I had to resilver one of the drives (the same drive both times) when I imported it back. All drives in the pool show no read, write, or checksum errors and are new, so I'm looking to a software problem before hardware. Both drives are encrypted geli devices. I tried to reproduce the error with 1GB disk images (vs 1TB), mdconfig, geli, and zpool, but no luck; importing and exporting work fine. Here's the history of the pool: History for 'tank': 2009-01-07.19:06:53 zpool create tank mirror /dev/ad8.eli /dev/ad10.eli 2009-01-12.12:34:20 zpool export -f tank 2009-01-12.12:38:12 zpool import tank 2009-01-12.12:41:43 zpool replace tank 5217673744218787970 /dev/ad10.eli 2009-01-12.21:48:12 zpool export tank 2009-01-13.20:20:27 zpool import tank 2009-01-13.20:22:18 zpool replace tank 2270010454322471606 /dev/ad10.eli 2009-01-14.08:04:52 zpool scrub tank 2009-01-14.08:08:38 zpool scrub -s tank When I do zdb tank, I get "zdb: can't open tank: No such file or directory." Somehow, I did the same command earlier and got pointed to http://www.sun.com/msg/ZFS-8000-EY There's a chance this drive (ad10 or ad10.eli) was in a zpool before this one that never got destroyed. Ideas? Any more information I should provide? From owner-freebsd-stable@FreeBSD.ORG Thu Jan 15 22:47:39 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 102DA106582B; Thu, 15 Jan 2009 22:47:37 +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 664A58FC25; Thu, 15 Jan 2009 22:47:37 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (pool-98-109-39-197.nwrknj.fios.verizon.net [98.109.39.197]) by cyrus.watson.org (Postfix) with ESMTPSA id 0884746B3C; Thu, 15 Jan 2009 17:47:36 -0500 (EST) Received: from localhost (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.14.3/8.14.3) with ESMTP id n0FMkttL004922; Thu, 15 Jan 2009 17:47:29 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin <jhb@freebsd.org> To: Robert Watson <rwatson@freebsd.org> Date: Thu, 15 Jan 2009 17:05:06 -0500 User-Agent: KMail/1.9.7 References: <E1LNVsF-0000WG-0T@dilbert.ticketswitch.com> <alpine.BSF.2.00.0901151747461.45995@fledge.watson.org> In-Reply-To: <alpine.BSF.2.00.0901151747461.45995@fledge.watson.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200901151705.06989.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Thu, 15 Jan 2009 17:47:30 -0500 (EST) X-Virus-Scanned: ClamAV 0.94.2/8870/Thu Jan 15 15:57:00 2009 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: freebsd-stable@freebsd.org, drosih@rpi.edu, Pete French <petefrench@ticketswitch.com>, rblayzor.bulk@inoc.net Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 15 Jan 2009 22:47:41 -0000 On Thursday 15 January 2009 12:49:11 pm Robert Watson wrote: > On Thu, 15 Jan 2009, Pete French wrote: > > >> desirable. You might want to give the NMI a test run just to make sure it > >> behaves as you think it should, though -- be aware that if DDB/KDB aren't > >> compiled into the kernel, then an NMI will panic the box. > > > > Unfortunately it does this... > > > > http://toybox.twisted.org.uk/~pete/71_nmi1.png > > > > That is locked up too - hitting return does nothing. I was hoping it was > > just garbled output but had actually gone to the debugger. Apparently not. > > > > Thats with a config file containing KDB, DDB and BREAK_TO_DEBUGGER, which > > does work as I have tested it with CTRL_ALT_ESC. > > Er, that's rather upsetting. John, do you have any ideas about this? The rest of the thread I have no context on still. The garbage is due to competing panics I think. The problem is we don't single thread the printf's in 'trap_fatal()'. We should probably have some sort of simple spin lock thing in the x86 code to only allow 1 CPU at a time to run through that routine. -- John Baldwin From owner-freebsd-stable@FreeBSD.ORG Thu Jan 15 23:29:54 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C03D6106566B for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 23:29:54 +0000 (UTC) (envelope-from morganw@chemikals.org) Received: from warped.bluecherry.net (unknown [IPv6:2001:440:eeee:fffb::2]) by mx1.freebsd.org (Postfix) with ESMTP id 5E68D8FC0A for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 23:29:54 +0000 (UTC) (envelope-from morganw@chemikals.org) Received: from volatile.chemikals.org (morganw-1-pt.tunnel.tserv8.dal1.ipv6.he.net [IPv6:2001:470:1f0e:47e::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by warped.bluecherry.net (Postfix) with ESMTPSA id DEDD084CAC0A; Thu, 15 Jan 2009 17:29:51 -0600 (CST) Received: from localhost (morganw@localhost [127.0.0.1]) by volatile.chemikals.org (8.14.3/8.14.3) with ESMTP id n0FNTVN6039919; Thu, 15 Jan 2009 17:29:36 -0600 (CST) (envelope-from morganw@chemikals.org) Date: Thu, 15 Jan 2009 17:29:31 -0600 (CST) From: Wes Morgan <morganw@chemikals.org> To: David Ehrmann <ehrmann@gmail.com> In-Reply-To: <6e0e5340901151158n5108ba8ct6af8fb270b10b75b@mail.gmail.com> Message-ID: <alpine.BSF.2.00.0901151729130.22937@ibyngvyr.purzvxnyf.bet> References: <6e0e5340901151158n5108ba8ct6af8fb270b10b75b@mail.gmail.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: zfs drive keeps failing between export and import X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 15 Jan 2009 23:29:55 -0000 On Thu, 15 Jan 2009, David Ehrmann wrote: > I have a zpool that consists for a two-drive mirror. The two times I > took the zpool offline, I had to resilver one of the drives (the same > drive both times) when I imported it back. All drives in the pool > show no read, write, or checksum errors and are new, so I'm looking to > a software problem before hardware. Both drives are encrypted geli > devices. I tried to reproduce the error with 1GB disk images (vs > 1TB), mdconfig, geli, and zpool, but no luck; importing and exporting > work fine. > > Here's the history of the pool: > > History for 'tank': > 2009-01-07.19:06:53 zpool create tank mirror /dev/ad8.eli /dev/ad10.eli > 2009-01-12.12:34:20 zpool export -f tank > 2009-01-12.12:38:12 zpool import tank > 2009-01-12.12:41:43 zpool replace tank 5217673744218787970 /dev/ad10.eli > 2009-01-12.21:48:12 zpool export tank > 2009-01-13.20:20:27 zpool import tank > 2009-01-13.20:22:18 zpool replace tank 2270010454322471606 /dev/ad10.eli > 2009-01-14.08:04:52 zpool scrub tank > 2009-01-14.08:08:38 zpool scrub -s tank > > When I do zdb tank, I get "zdb: can't open tank: No such file or > directory." Somehow, I did the same command earlier and got pointed > to http://www.sun.com/msg/ZFS-8000-EY > > There's a chance this drive (ad10 or ad10.eli) was in a zpool before > this one that never got destroyed. > > Ideas? Any more information I should provide? What does "zdb /dev/ad10.eli" show? From owner-freebsd-stable@FreeBSD.ORG Thu Jan 15 23:55:28 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 88109106566B for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 23:55:28 +0000 (UTC) (envelope-from andrew@areilly.bpa.nu) Received: from nschwmtas02p.mx.bigpond.com (nschwmtas02p.mx.bigpond.com [61.9.189.140]) by mx1.freebsd.org (Postfix) with ESMTP id 1621D8FC0A for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 23:55:27 +0000 (UTC) (envelope-from andrew@areilly.bpa.nu) Received: from nschwotgx01p.mx.bigpond.com ([124.188.162.219]) by nschwmtas02p.mx.bigpond.com with ESMTP id <20090115235526.DUCH22514.nschwmtas02p.mx.bigpond.com@nschwotgx01p.mx.bigpond.com> for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 23:55:26 +0000 Received: from areilly.bpa.nu ([124.188.162.219]) by nschwotgx01p.mx.bigpond.com with ESMTP id <20090115235523.MKCO6454.nschwotgx01p.mx.bigpond.com@areilly.bpa.nu> for <freebsd-stable@freebsd.org>; Thu, 15 Jan 2009 23:55:23 +0000 Received: (qmail 40958 invoked by uid 501); 15 Jan 2009 23:55:23 -0000 Date: Fri, 16 Jan 2009 10:55:23 +1100 From: Andrew Reilly <andrew-freebsd@areilly.bpc-users.org> To: freebsd-stable@freebsd.org Message-ID: <20090115235523.GA39905@duncan.reilly.home> References: <20090115051422.GA59032@duncan.reilly.home> <20090115120001.GA23934@osiris.mauzo.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090115120001.GA23934@osiris.mauzo.dyndns.org> User-Agent: Mutt/1.4.2.3i X-RPD-ScanID: Class unknown; VirusThreatLevel unknown, RefID str=0001.0A150202.496FCCEC.0001,ss=1,fgs=0 Subject: Re: How to get djbdns to start early enough to satisfy ntpd at boot? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 15 Jan 2009 23:55:29 -0000 On Thu, Jan 15, 2009 at 12:00:01PM +0000, Ben Morrow wrote: > Quoth Andrew Reilly <andrew-freebsd@areilly.bpc-users.org>: > > > > So: does anyone know how to modify the boot-time order so that > > svscan starts at (or before) the point in the boot cycle where > > BIND would, on other systems? I suspect that it should be > I have, in my svscan.sh, > > # PROVIDE: svscan > # REQUIRE: SERVERS cleanvar > > and I also have a /usr/local/etc/rc.d/dnscache which looks like [snip] > > and a /usr/local/etc/svc.subr as attached. It's somewhat more general > than is needed for dnscache, as I also use it to start qmail. > > Basically: the PROVIDE: named line is needed to get dnscache up before > ntpd, and the REQUIRE: LOGIN line needs to be changed. Wow, those scripts are an extremely cool integration of the rcorder framework and the svscan framework. Could these be incorporated into the daemontools and djbdns ports as permanent goodness? I'll give them a try-out myself, pronto. (Might also investigate clockspeed, per Jan's suggestiong, too.) Cheers, Andrew From owner-freebsd-stable@FreeBSD.ORG Fri Jan 16 01:49:34 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5B7431065701 for <freebsd-stable@freebsd.org>; Fri, 16 Jan 2009 01:49:34 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from QMTA10.emeryville.ca.mail.comcast.net (qmta10.emeryville.ca.mail.comcast.net [76.96.30.17]) by mx1.freebsd.org (Postfix) with ESMTP id 434F98FC1C for <freebsd-stable@freebsd.org>; Fri, 16 Jan 2009 01:49:34 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from OMTA01.emeryville.ca.mail.comcast.net ([76.96.30.11]) by QMTA10.emeryville.ca.mail.comcast.net with comcast id 3xsF1b0010EPchoAA1pbzS; Fri, 16 Jan 2009 01:49:35 +0000 Received: from [192.168.1.104] ([71.57.105.220]) by OMTA01.emeryville.ca.mail.comcast.net with comcast id 41op1b00B4lKpr38M1pa29; Fri, 16 Jan 2009 01:49:34 +0000 Message-ID: <496FE784.3040505@tomjudge.com> Date: Thu, 15 Jan 2009 19:48:52 -0600 From: Tom Judge <tom@tomjudge.com> User-Agent: Thunderbird 2.0.0.19 (X11/20090105) MIME-Version: 1.0 To: Daniel Bond <db@danielbond.org> References: <496D72AE.8090303@tomjudge.com> <76BAA4E0-A567-4173-A67E-38BD112F93C1@danielbond.org> In-Reply-To: <76BAA4E0-A567-4173-A67E-38BD112F93C1@danielbond.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: Using FreeBSD Update to deploy system updates from custom builds X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 16 Jan 2009 01:49:34 -0000 Daniel Bond wrote: > Hi Tom, > > I don't know how much documentation there is on this, but if you are > investigating this issue, maybe you would like to contribute/update > some documentation on it? > > Royce gave me a link to the tools, > http://www.freebsd.org/cgi/cvsweb.cgi/projects/freebsd-update-server/ > reading through some of the scripts might give some clues. > > > > Regards, > > Daniel Bond. > Thanks for the info, I will look into this over the next few weeks and see what I can come up with. Regards Tom Judge > On Jan 14, 2009, at 6:05 AM, Tom Judge wrote: > >> Hi, >> >> I was wondering if anyone was using freebsd-update to manage >> deployment of custom FreeBSD builds to there systems. >> >> Here is the scenario, I have 2 binary build servers at the moment >> (one for i386 and one for amd64) and currently we stage the >> deployments of updates on NFS servers at each site. We use make >> installworld/kernel to update the servers from read only src and obj >> NFS mounts. >> >> I'm now looking to remove the src trees from the NFS servers and >> possibly the obj trees and use freebsd-update to deploy and maintain >> the custom build installation and updates. >> >> So I have 2 questions: >> >> 1) Does this seem sensible? It seems within scope of what >> freebsd-update was designed to do. >> >> 2) How does one go about building the binary distributions that >> freebsd-update expects to be on the update server? >> >> >> Thanks >> >> Tom >> >> _______________________________________________ >> 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" > > _______________________________________________ > 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 Fri Jan 16 03:12:41 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6C2781065670 for <freebsd-stable@freebsd.org>; Fri, 16 Jan 2009 03:12:41 +0000 (UTC) (envelope-from dan@langille.org) Received: from nyi.unixathome.org (nyi.unixathome.org [64.147.113.42]) by mx1.freebsd.org (Postfix) with ESMTP id 4217B8FC1A for <freebsd-stable@freebsd.org>; Fri, 16 Jan 2009 03:12:41 +0000 (UTC) (envelope-from dan@langille.org) Received: from localhost (localhost [127.0.0.1]) by nyi.unixathome.org (Postfix) with ESMTP id 95F90509C0; Fri, 16 Jan 2009 03:12:40 +0000 (GMT) X-Virus-Scanned: amavisd-new at unixathome.org Received: from nyi.unixathome.org ([127.0.0.1]) by localhost (nyi.unixathome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ILCp0IT+ojDm; Fri, 16 Jan 2009 03:12:38 +0000 (GMT) Received: from smtp-auth.unixathome.org (smtp-auth.unixathome.org [10.4.7.7]) (Authenticated sender: hidden) by nyi.unixathome.org (Postfix) with ESMTPSA id E24BD509B5 ; Fri, 16 Jan 2009 03:12:37 +0000 (GMT) Message-ID: <496FFADB.1080900@langille.org> Date: Thu, 15 Jan 2009 22:11:23 -0500 From: Dan Langille <dan@langille.org> Organization: The FreeBSD Diary User-Agent: Thunderbird 2.0.0.19 (X11/20090111) MIME-Version: 1.0 To: Pete French <petefrench@ticketswitch.com> References: <E1LNRDZ-0005sH-JS@dilbert.ticketswitch.com> In-Reply-To: <E1LNRDZ-0005sH-JS@dilbert.ticketswitch.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: amarat@ksu.ru, freebsd-stable@freebsd.org Subject: Re: interrupt storm X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 16 Jan 2009 03:12:42 -0000 Pete French wrote: >>>>> kernel: interrupt storm detected on "irq22:"; throttling interrupt >>>>> source > > .... > >> Opening the case, reading the m/b: >> >> K9A2 Platinum MSI > > > I hadnt been paying much attention to this thread, but just to let you > know that I also saw the same thing on this machine which has an MSI 790FX > Platinum motherboard. It was also irq22, and I am also running amd64. > > In my case I simply disabled the onboard ethernet (which I wasnt using) > and the problem went away - but then I only saw the problem once, it wasnt > a regular occurrance. If you have an alternative ether card you can drop > in thn you could try that... FYI, this box has always run off an ethernet card (fxp). The on-board NIC (re) was enabled. After disabling, the ethernet storms persisted. -- Dan Langille BSDCan - The Technical BSD Conference : http://www.bsdcan.org/ PGCon - The PostgreSQL Conference: http://www.pgcon.org/ From owner-freebsd-stable@FreeBSD.ORG Fri Jan 16 03:38:44 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> 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 C938D10656CD for <stable@freebsd.org>; Fri, 16 Jan 2009 03:38:44 +0000 (UTC) (envelope-from serg@tmn.ru) Received: from sbtx.tmn.ru (relay.tmn.ru [212.76.160.49]) by mx1.freebsd.org (Postfix) with ESMTP id 18AC58FC12 for <stable@freebsd.org>; Fri, 16 Jan 2009 03:38:43 +0000 (UTC) (envelope-from serg@tmn.ru) X-Bogosity: Ham, spamicity=0.000000 Received: from sv.tech.sibitex.tmn.ru (sv.tech.sibitex.tmn.ru [10.76.160.59]) by sbtx.tmn.ru (8.14.2/8.14.2) with ESMTP id n0G3cCj3020795; Fri, 16 Jan 2009 08:38:16 +0500 (YEKT) (envelope-from serg@tmn.ru) Received: from sv.tech.sibitex.tmn.ru (localhost.tech.sibitex.tmn.ru [127.0.0.1]) by sv.tech.sibitex.tmn.ru (8.14.3/8.14.3) with ESMTP id n0G3cCcL048402; Fri, 16 Jan 2009 08:38:12 +0500 (YEKT) (envelope-from serg@sv.tech.sibitex.tmn.ru) Received: (from serg@localhost) by sv.tech.sibitex.tmn.ru (8.14.3/8.14.3/Submit) id n0G3cBe6048401; Fri, 16 Jan 2009 08:38:11 +0500 (YEKT) (envelope-from serg) Date: Fri, 16 Jan 2009 08:38:11 +0500 From: "Sergey N. Voronkov" <serg@tmn.ru> To: Mike Lempriere <mike@vintners.net> Message-ID: <20090116033811.GA48368@tmn.ru> References: <496EB76F.9000501@vintners.net> <20090115044333.GA42029@tmn.ru> <496F3A6F.1050505@vintners.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <496F3A6F.1050505@vintners.net> User-Agent: Mutt/1.4.2.3i X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (sbtx.tmn.ru [10.0.160.49]); Fri, 16 Jan 2009 08:38:36 +0500 (YEKT) X-Virus-Scanned: ClamAV version 0.94.2, clamav-milter version 0.94.2 on sbtx.tmn.ru X-Virus-Status: Clean Cc: stable@freebsd.org Subject: Re: named won't start X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 16 Jan 2009 03:38:45 -0000 On Thu, Jan 15, 2009 at 05:30:23AM -0800, Mike Lempriere wrote: > I'm not real clear on what item 6 means. However all of my specified > zones have at least one NS and one A record. Does this mean I'm Ok? "Sites that were relying on this BIND 8 behaviour need to add any omitted glue NS records, and any necessary glue A records, to the parent zone." Exactly as: domain.com.zone: [...] sec IN NS ns.sec.domain.com. ns.sec IN A 1.2.3.4 [...] sec.domain.com.zone: @ IN SOA [...] Nothing more. But I'v miss Your real problem below. > Sergey N. Voronkov wrote: > >On Wed, Jan 14, 2009 at 08:11:27PM -0800, Mike Lempriere wrote: > > > >>From /var/log/messages: > >>starting BIND 9.4.3-P1 -t /var/named -u bind > >>could not get query source dispatcher (0.0.0.0#53) > >>loading configuration: address in use > >>exiting (due to fatal error) So, the EXACT problem is a double start of the daemon. Please double check merge of rc files after upgrade. > >>I had just updated from 5-stable (at 5.5) to 6-stable (at 6.4). Upon > >>today's upgrade I got to 7.1. Everything else seems to be be working > >>(the machine is basically a webserver), except named. apache is serving > >>up pages, but only until my TTL times out... > >> > >>I so no errors in the builds or installs. I foolwed the instructions in > >>UPDATING. I believe I did an accurate merge of my named.conf file. > >> [skip] Sergey N. Voronkov, Sibitex Ltd. From owner-freebsd-stable@FreeBSD.ORG Fri Jan 16 04:18:33 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 66D1B1065672 for <freebsd-stable@freebsd.org>; Fri, 16 Jan 2009 04:18:33 +0000 (UTC) (envelope-from amarat@ksu.ru) Received: from mx.kzn.ru (mx.kzn.ru [194.85.243.39]) by mx1.freebsd.org (Postfix) with ESMTP id D57FA8FC08 for <freebsd-stable@freebsd.org>; Fri, 16 Jan 2009 04:18:32 +0000 (UTC) (envelope-from amarat@ksu.ru) X-IronPort-AV: E=Sophos;i="4.37,274,1231102800"; d="scan'208";a="1190577" Received: from mail.ksu.ru (HELO ruby.ksu.ru) ([193.232.252.56]) by iout.kzn.ru with ESMTP; 16 Jan 2009 07:18:29 +0300 X-Pass-Through: Kazan State University Network Received: from zealot.ksu.ru ([194.85.245.161]) by ksu.ru (8.13.4/8.13.4) with ESMTP id n0G4FHVq016708; Fri, 16 Jan 2009 04:15:17 GMT Received: from zealot.ksu.ru (localhost.lnet [127.0.0.1]) by zealot.ksu.ru (8.14.3/8.14.3) with ESMTP id n0G4Hg5E026727; Fri, 16 Jan 2009 07:17:44 +0300 (MSK) (envelope-from amarat@ksu.ru) Message-ID: <49700A66.800@ksu.ru> Date: Fri, 16 Jan 2009 07:17:42 +0300 From: "Marat N.Afanasyev" <amarat@ksu.ru> User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.8.1.16) Gecko/20080903 SeaMonkey/1.1.11 MIME-Version: 1.0 To: Dan Langille <dan@langille.org> References: <E1LNRDZ-0005sH-JS@dilbert.ticketswitch.com> <496FFADB.1080900@langille.org> In-Reply-To: <496FFADB.1080900@langille.org> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Pete French <petefrench@ticketswitch.com> Subject: Re: interrupt storm on MSI IXP600 based motherboards X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 16 Jan 2009 04:18:33 -0000 Dan Langille wrote: > Pete French wrote: >>>>>> kernel: interrupt storm detected on "irq22:"; throttling interrupt >>>>>> source >> >> .... >> >>> Opening the case, reading the m/b: >>> >>> K9A2 Platinum MSI >> >> >> I hadnt been paying much attention to this thread, but just to let you >> know that I also saw the same thing on this machine which has an MSI >> 790FX >> Platinum motherboard. It was also irq22, and I am also running amd64. >> >> In my case I simply disabled the onboard ethernet (which I wasnt using) >> and the problem went away - but then I only saw the problem once, it >> wasnt >> a regular occurrance. If you have an alternative ether card you can drop >> in thn you could try that... > > FYI, this box has always run off an ethernet card (fxp). The on-board > NIC (re) was enabled. After disabling, the ethernet storms persisted. > > trouble with onboard re(4) was resolved in -CURRENT and -STABLE, but storms are not bound to ethernet only. storm may appear on any device. if any device generates enough interrupts rate, storm will arrive. I've written about it in http://lists.freebsd.org/pipermail/freebsd-stable/2009-January/047644.html so far i can say that this issue is related on MSI IXP600 based motherboards only. well, we should try to find out what we can do to resolve it. -- SY, Marat From owner-freebsd-stable@FreeBSD.ORG Fri Jan 16 04:22:17 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 565F91065672 for <freebsd-stable@freebsd.org>; Fri, 16 Jan 2009 04:22:17 +0000 (UTC) (envelope-from dan@langille.org) Received: from nyi.unixathome.org (nyi.unixathome.org [64.147.113.42]) by mx1.freebsd.org (Postfix) with ESMTP id 2A3BE8FC12 for <freebsd-stable@freebsd.org>; Fri, 16 Jan 2009 04:22:17 +0000 (UTC) (envelope-from dan@langille.org) Received: from localhost (localhost [127.0.0.1]) by nyi.unixathome.org (Postfix) with ESMTP id C7535509BF; Fri, 16 Jan 2009 04:22:16 +0000 (GMT) X-Virus-Scanned: amavisd-new at unixathome.org Received: from nyi.unixathome.org ([127.0.0.1]) by localhost (nyi.unixathome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mb7vYwxNMBmS; Fri, 16 Jan 2009 04:22:16 +0000 (GMT) Received: from smtp-auth.unixathome.org (smtp-auth.unixathome.org [10.4.7.7]) (Authenticated sender: hidden) by nyi.unixathome.org (Postfix) with ESMTPSA id E01C2509B5 ; Fri, 16 Jan 2009 04:22:15 +0000 (GMT) Message-ID: <49700B2D.6000206@langille.org> Date: Thu, 15 Jan 2009 23:21:01 -0500 From: Dan Langille <dan@langille.org> Organization: The FreeBSD Diary User-Agent: Thunderbird 2.0.0.19 (X11/20090111) MIME-Version: 1.0 To: "Marat N.Afanasyev" <amarat@ksu.ru> References: <E1LNRDZ-0005sH-JS@dilbert.ticketswitch.com> <496FFADB.1080900@langille.org> <49700A66.800@ksu.ru> In-Reply-To: <49700A66.800@ksu.ru> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Pete French <petefrench@ticketswitch.com> Subject: Re: interrupt storm on MSI IXP600 based motherboards X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 16 Jan 2009 04:22:17 -0000 Marat N.Afanasyev wrote: > Dan Langille wrote: >> Pete French wrote: >>>>>>> kernel: interrupt storm detected on "irq22:"; throttling >>>>>>> interrupt source >>> >>> .... >>> >>>> Opening the case, reading the m/b: >>>> >>>> K9A2 Platinum MSI >>> >>> >>> I hadnt been paying much attention to this thread, but just to let you >>> know that I also saw the same thing on this machine which has an MSI >>> 790FX >>> Platinum motherboard. It was also irq22, and I am also running amd64. >>> >>> In my case I simply disabled the onboard ethernet (which I wasnt using) >>> and the problem went away - but then I only saw the problem once, it >>> wasnt >>> a regular occurrance. If you have an alternative ether card you can drop >>> in thn you could try that... >> >> FYI, this box has always run off an ethernet card (fxp). The on-board >> NIC (re) was enabled. After disabling, the ethernet storms persisted. >> >> > trouble with onboard re(4) was resolved in -CURRENT and -STABLE, but > storms are not bound to ethernet only. storm may appear on any device. > if any device generates enough interrupts rate, storm will arrive. > > I've written about it in > http://lists.freebsd.org/pipermail/freebsd-stable/2009-January/047644.html > > so far i can say that this issue is related on MSI IXP600 based > motherboards only. well, we should try to find out what we can do to > resolve it. Any committer that would like ssh access to this box in order to fix the problem, mail me your public-ssh key. :) -- Dan Langille BSDCan - The Technical BSD Conference : http://www.bsdcan.org/ PGCon - The PostgreSQL Conference: http://www.pgcon.org/ From owner-freebsd-stable@FreeBSD.ORG Fri Jan 16 05:27:02 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 131E11065698 for <freebsd-stable@freebsd.org>; Fri, 16 Jan 2009 05:27:02 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail34.syd.optusnet.com.au (mail34.syd.optusnet.com.au [211.29.133.218]) by mx1.freebsd.org (Postfix) with ESMTP id 822228FC1E for <freebsd-stable@freebsd.org>; Fri, 16 Jan 2009 05:27:01 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c122-106-215-175.belrs3.nsw.optusnet.com.au [122.106.215.175]) by mail34.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id n0G5QvlN002502 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 16 Jan 2009 16:26:59 +1100 X-Bogosity: Ham, spamicity=0.000000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.3/8.14.3) with ESMTP id n0G5QvDQ003392; Fri, 16 Jan 2009 16:26:57 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.3/8.14.3/Submit) id n0G5QuW6003391; Fri, 16 Jan 2009 16:26:56 +1100 (EST) (envelope-from peter) Date: Fri, 16 Jan 2009 16:26:56 +1100 From: Peter Jeremy <peterjeremy@optushome.com.au> To: Dan Langille <dan@langille.org> Message-ID: <20090116052656.GF16116@server.vk2pj.dyndns.org> References: <496D374A.3020704@langille.org> <496E9A37.20800@langille.org> <496EA339.6010808@ksu.ru> <496EB43A.8010805@langille.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ieNMXl1Fr3cevapt" Content-Disposition: inline In-Reply-To: <496EB43A.8010805@langille.org> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-stable@freebsd.org Subject: Re: interrupt storm X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 16 Jan 2009 05:27:02 -0000 --ieNMXl1Fr3cevapt Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2009-Jan-14 22:57:46 -0500, Dan Langille <dan@langille.org> wrote: >Opening the case, reading the m/b: > > K9A2 Platinum MSI Tangentially related: For any decent M/B, kenv(8) should tell you this without needing to open the box. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --ieNMXl1Fr3cevapt Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAklwGqAACgkQ/opHv/APuIdr7ACeLPr58rdmTYzZxWnHsaVMN259 bQwAoLGVViXFuTlA3XgaRa+a/qZoyZlq =W1ff -----END PGP SIGNATURE----- --ieNMXl1Fr3cevapt-- From owner-freebsd-stable@FreeBSD.ORG Fri Jan 16 05:48:17 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3E23A1065672 for <freebsd-stable@freebsd.org>; Fri, 16 Jan 2009 05:48:17 +0000 (UTC) (envelope-from ehrmann@gmail.com) Received: from mxout-03.mxes.net (mxout-03.mxes.net [216.86.168.178]) by mx1.freebsd.org (Postfix) with ESMTP id DBDFD8FC3A for <freebsd-stable@freebsd.org>; Fri, 16 Jan 2009 05:48:16 +0000 (UTC) (envelope-from ehrmann@gmail.com) Received: from [10.0.0.158] (unknown [64.9.236.71]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id D587023E402; Fri, 16 Jan 2009 00:48:12 -0500 (EST) Message-ID: <49701F94.6030507@gmail.com> Date: Thu, 15 Jan 2009 21:48:04 -0800 From: David Ehrmann <ehrmann@gmail.com> User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Wes Morgan <morganw@chemikals.org> References: <6e0e5340901151158n5108ba8ct6af8fb270b10b75b@mail.gmail.com> <alpine.BSF.2.00.0901151729130.22937@ibyngvyr.purzvxnyf.bet> In-Reply-To: <alpine.BSF.2.00.0901151729130.22937@ibyngvyr.purzvxnyf.bet> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: zfs drive keeps failing between export and import X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 16 Jan 2009 05:48:17 -0000 Wes Morgan wrote: > What does "zdb /dev/ad10.eli" show? First, a quick update: removing the drive without ANY unmounts (I accidentally pulled it from the backplane) didn't cause any problems. I plugged it back in, reset the atachannel (there's a bug somewhere related to that, but I can live with "atacontroll detach/attach"), reattached with geli, ran the above command (it was identical the same as before), and within a minute, it showed up in zpool status as ONLINE (it was offline and in a degraded state, earlier). Anyway, the dump: -------------------------------------------- LABEL 0 -------------------------------------------- version=6 name='tank' state=0 txg=289956 pool_guid=6825823102095709452 hostid=2180312168 hostname='share2.lan' top_guid=5286005479160756084 guid=2749356003825630058 vdev_tree type='mirror' id=0 guid=5286005479160756084 metaslab_array=14 metaslab_shift=30 ashift=9 asize=1000199946240 children[0] type='disk' id=0 guid=1472646983867204022 path='/dev/ad8.eli' devid='ad:WD-WCASJ2219110' whole_disk=0 DTL=626 children[1] type='disk' id=1 guid=2749356003825630058 path='/dev/ad10.eli' devid='ad:WD-WCAU44729718' whole_disk=0 DTL=625 -------------------------------------------- LABEL 1 -------------------------------------------- version=6 name='tank' state=0 txg=289956 pool_guid=6825823102095709452 hostid=2180312168 hostname='share2.lan' top_guid=5286005479160756084 guid=2749356003825630058 vdev_tree type='mirror' id=0 guid=5286005479160756084 metaslab_array=14 metaslab_shift=30 ashift=9 asize=1000199946240 children[0] type='disk' id=0 guid=1472646983867204022 path='/dev/ad8.eli' devid='ad:WD-WCASJ2219110' whole_disk=0 DTL=626 children[1] type='disk' id=1 guid=2749356003825630058 path='/dev/ad10.eli' devid='ad:WD-WCAU44729718' whole_disk=0 DTL=625 -------------------------------------------- LABEL 2 -------------------------------------------- version=6 name='tank' state=0 txg=289956 pool_guid=6825823102095709452 hostid=2180312168 hostname='share2.lan' top_guid=5286005479160756084 guid=2749356003825630058 vdev_tree type='mirror' id=0 guid=5286005479160756084 metaslab_array=14 metaslab_shift=30 ashift=9 asize=1000199946240 children[0] type='disk' id=0 guid=1472646983867204022 path='/dev/ad8.eli' devid='ad:WD-WCASJ2219110' whole_disk=0 DTL=626 children[1] type='disk' id=1 guid=2749356003825630058 path='/dev/ad10.eli' devid='ad:WD-WCAU44729718' whole_disk=0 DTL=625 -------------------------------------------- LABEL 3 -------------------------------------------- version=6 name='tank' state=0 txg=289956 pool_guid=6825823102095709452 hostid=2180312168 hostname='share2.lan' top_guid=5286005479160756084 guid=2749356003825630058 vdev_tree type='mirror' id=0 guid=5286005479160756084 metaslab_array=14 metaslab_shift=30 ashift=9 asize=1000199946240 children[0] type='disk' id=0 guid=1472646983867204022 path='/dev/ad8.eli' devid='ad:WD-WCASJ2219110' whole_disk=0 DTL=626 children[1] type='disk' id=1 guid=2749356003825630058 path='/dev/ad10.eli' devid='ad:WD-WCAU44729718' whole_disk=0 DTL=625 From owner-freebsd-stable@FreeBSD.ORG Fri Jan 16 09:10:53 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 970F8106567D for <freebsd-stable@freebsd.org>; Fri, 16 Jan 2009 09:10:53 +0000 (UTC) (envelope-from marc@sanity.de) Received: from mail.adandbreakfast.com (mail.adandbreakfast.com [194.245.32.131]) by mx1.freebsd.org (Postfix) with ESMTP id CFEC68FC18 for <freebsd-stable@freebsd.org>; Fri, 16 Jan 2009 09:10:52 +0000 (UTC) (envelope-from marc@sanity.de) Received: from localhost (localhost [127.0.0.1]) by mail.adandbreakfast.com (Postfix) with ESMTP id C4BD58C4053; Fri, 16 Jan 2009 10:10:51 +0100 (CET) Received: from mail.adandbreakfast.com ([194.245.32.131]) by localhost (mail.adandbreakfast.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 22121-06; Fri, 16 Jan 2009 10:10:51 +0100 (CET) Received: from videoschnitt.agentur.local (unknown [192.168.83.220]) by mail.adandbreakfast.com (Postfix) with ESMTP id 5A8788C404E; Fri, 16 Jan 2009 10:10:51 +0100 (CET) Message-ID: <49704F1A.8060706@sanity.de> Date: Fri, 16 Jan 2009 10:10:50 +0100 From: Marc Peters <marc@sanity.de> User-Agent: Thunderbird 2.0.0.19 (X11/20090106) MIME-Version: 1.0 To: "Paul B. Mahol" <onemda@gmail.com> References: <496F0E85.5090904@sanity.de> <3a142e750901150252v5633f808q71d3fa3ab5050b20@mail.gmail.com> <496F458E.6050708@sanity.de> <3a142e750901150825r73fa6d82g6b14d20f3548b8eb@mail.gmail.com> In-Reply-To: <3a142e750901150825r73fa6d82g6b14d20f3548b8eb@mail.gmail.com> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at agentur.local Cc: freebsd-stable@freebsd.org Subject: Re: kernel panics when connected through wpi to apple extreme ap X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 16 Jan 2009 09:10:56 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Paul B. Mahol schrieb: > On 1/15/09, Marc Peters <marc@sanity.de> wrote: > hi paul, > > msgbuf.txt: > [snipping dmesg and startup-messages] > Fatal trap 12: page fault while in kernel mode > cpuid = 1; apic id = 01 > fault virtual address = 0xffff > fault code = supervisor read, page not present > instruction pointer = 0x20:0xc0e70dfc > stack pointer = 0x28:0xe58bbbe0 > frame pointer = 0x28:0xe58bbc9c > 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 = 25 (wpi0 taskq) > > ddb.txt (just bt output here): > > db> bt > > Tracing pid 25 tid 100024 td 0xc5189af0 > wpi_ops(c52c5000,1,c0b7cf36,0,0,...) at wpi_ops+0x89c > taskqueue_run(c52ab200,c52ab21c,0,c0b7cf36,0,...) at taskqueue_run+0x175 > taskqueue_thread_loop(c52c69b4,e58bbd38,0,0,0,...) at > taskqueue_thread_loop+0xbb > fork_exit(c07fb2b0,c52c69b4,e58bbd38) at fork_exit+0x99 > fork_trampoline() at fork_trampoline+0x8 > --- trap 0, eip = 0, esp = 0xe58bbd70, ebp = 0 --- > > version.txt: > FreeBSD 7.1-STABLE #0: Thu Jan 15 13:51:12 CET 2009 > root@lappi.agentur.local:/usr/obj/usr/src/sys/DEBUG_DRM > > if you need more information, i will provide it. it took wpi some time > to crash, so i stressed it a little bit with an ftp download and a > buildworld through an ssh-screen. > > >> Maybe it is some locking issue at first look. Send problem report so >> that this doesnt get lost. >> Are you sure this is regression? Anyway check if same issue is not >> already reported. i will to so and send a PR. i will include our mailings. > >> Give this a try: > >> gdb >> gdb> file /boot/YOUR_KERNEL/if_wpi.ko Reading symbols from /boot/kernel/if_wpi.ko...Reading symbols from /boot/kernel/if_wpi.ko.symbols...done. >> gdb> l *wpi_ops+0x89c (the mail will wrap the first line) 0x9dfc is in wpi_ops (/usr/src/sys/modules/wpi/../../dev/wpi/if_wpi.c:2411). 2406 /* update adapter's configuration */ 2407 sc->config.associd = 0; 2408 sc->config.filter &= ~htole32(WPI_FILTER_BSS); 2409 IEEE80211_ADDR_COPY(sc->config.bssid, ni->ni_bssid); 2410 sc->config.chan = ieee80211_chan2ieee(ic, ni->ni_chan); 2411 if (IEEE80211_IS_CHAN_2GHZ(ni->ni_chan)) { 2412 sc->config.flags |= htole32(WPI_CONFIG_AUTO | 2413 WPI_CONFIG_24GHZ); 2414 } 2415 switch (ic->ic_curmode) { > >> And post output. > > marc > > > Paul B. Mahol schrieb: >>>> On 1/15/09, Marc Peters <marc@sanity.de> wrote: >>>> hello list, >>>> >>>> i have a lenovo t60 with an integrated intel 3945ABG wireless chipset. >>>> when i was running 7.1-PRERELEASE i realised that the network connection >>>> of my wpi died after some time when connected to the mention apple >>>> access point. i had to restart the card and everything went fine, for >>>> some time (about half an hour). since 7.1-RELEASE and now with >>>> 7.1-STABLE the kernel panics with a fatal trap and dumps it's core after >>>> some minutes (this output ist from -RELEASE-p1, but it's identical to >>>> the one i got from -STABLE): >>>> >>>> Fatal trap 12: page fault while in kernel mode >>>> cpuid = 0; apic id = 00 >>>> fault virtual address = 0xffff >>>> fault code = supervisor read, page not present >>>> instruction pointer = 0x20:0xc0deadfc >>>> stack pointer = 0x28:0xe58bbbe0 >>>> frame pointer = 0x28:0xe58bbc9c >>>> 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 = 25 (wpi0 taskq) >>>> trap number = 12 >>>> panic: page fault >>>> cpuid = 0 >>>> Uptime: 6m 14s >>>> Physical memory: 2034 MB >>>> Dumping 149 MB: 134 118 192 86 70 65 38 22 6 >>>> Dump complete >>>> Automatic reboot in 15 seconds - press a key on the console to abort >>>> >>>> when i run this box connected to a netgear-ap i have at home, everything >>>> is fine (and was before, no panics, no connection dropping). i have the >>>> dump at hand, but since it's 150 MB i won't send it around via mail. if >>>> anyone is interested, i can upload it somewhere and send the link. >>>> >>>> anyone any ideas? >>>> >>>>> Enable textdump(8) and post bt output from debuger once panic happen. >>>>> (I'm not going to download 150MB) >>>> marc >>>> >>>> dmesg: >>>> >>>> Copyright (c) 1992-2009 The FreeBSD Project. >>>> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 >>>> The Regents of the University of California. All rights reserved. >>>> FreeBSD is a registered trademark of The FreeBSD Foundation. >>>> FreeBSD 7.1-STABLE #0: Wed Jan 14 13:23:00 CET 2009 >>>> root@lappi.agentur.local:/usr/obj/usr/src/sys/GENERIC_DRM >>>> Timecounter "i8254" frequency 1193182 Hz quality 0 >>>> CPU: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz (1995.02-MHz >>>> 686-class CPU) >>>> Origin = "GenuineIntel" Id = 0x6f6 Stepping = 6 >>>> >>>> Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> >>>> >>>> Features2=0xe3bd<SSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM> >>>> AMD Features=0x20100000<NX,LM> >>>> AMD Features2=0x1<LAHF> >>>> Cores per package: 2 >>>> real memory = 2146238464 (2046 MB) >>>> avail memory = 2090221568 (1993 MB) >>>> ACPI APIC Table: <LENOVO TP-79 > >>>> FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs >>>> cpu0 (BSP): APIC ID: 0 >>>> cpu1 (AP): APIC ID: 1 >>>> ACPI Warning (tbfadt-0505): Optional field "Gpe1Block" has zero address >>>> or length: 0 102C/0 [20070320] >>>> ioapic0: Changing APIC ID to 1 >>>> ioapic0 <Version 2.0> irqs 0-23 on motherboard >>>> kbd1 at kbdmux0 >>>> ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) >>>> acpi0: <LENOVO TP-79> on motherboard >>>> acpi0: [ITHREAD] >>>> acpi_ec0: <Embedded Controller: GPE 0x1c, ECDT> port 0x62,0x66 on acpi0 >>>> acpi0: Power Button (fixed) >>>> acpi0: reservation of 0, a0000 (3) failed >>>> acpi0: reservation of 100000, 7ff00000 (3) failed >>>> Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 >>>> acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 >>>> acpi_hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on >>>> acpi0 >>>> Timecounter "HPET" frequency 14318180 Hz quality 900 >>>> acpi_lid0: <Control Method Lid Switch> on acpi0 >>>> acpi_button0: <Sleep Button> on acpi0 >>>> pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0 >>>> pci0: <ACPI PCI bus> on pcib0 >>>> pcib1: <ACPI PCI-PCI bridge> irq 16 at device 1.0 on pci0 >>>> pci1: <ACPI PCI bus> on pcib1 >>>> vgapci0: <VGA-compatible display> port 0x2000-0x20ff mem >>>> 0xd8000000-0xdfffffff,0xee100000-0xee10ffff irq 16 at device 0.0 on pci1 >>>> drm0: <ATI Mobility Radeon X1400> on vgapci0 >>>> vgapci0: child drm0 requested pci_enable_busmaster >>>> info: [drm] Initialized radeon 1.29.0 20080613 >>>> hdac0: <Intel 82801G High Definition Audio Controller> mem >>>> 0xee400000-0xee403fff irq 17 at device 27.0 on pci0 >>>> hdac0: HDA Driver Revision: 20090110_0123 >>>> hdac0: [ITHREAD] >>>> pcib2: <ACPI PCI-PCI bridge> irq 20 at device 28.0 on pci0 >>>> pci2: <ACPI PCI bus> on pcib2 >>>> em0: <Intel(R) PRO/1000 Network Connection 6.9.6> port 0x3000-0x301f mem >>>> 0xee000000-0xee01ffff irq 16 at device 0.0 on pci2 >>>> em0: Using MSI interrupt >>>> em0: [FILTER] >>>> em0: Ethernet address: 00:16:41:e3:4a:ff >>>> pcib3: <ACPI PCI-PCI bridge> irq 21 at device 28.1 on pci0 >>>> pci3: <ACPI PCI bus> on pcib3 >>>> wpi0: <Intel(R) PRO/Wireless 3945ABG> mem 0xedf00000-0xedf00fff irq 17 >>>> at device 0.0 on pci3 >>>> wpi0: Ethernet address: 00:19:d2:07:cf:36 >>>> wpi0: [ITHREAD] >>>> pcib4: <ACPI PCI-PCI bridge> irq 22 at device 28.2 on pci0 >>>> pci4: <ACPI PCI bus> on pcib4 >>>> pcib5: <ACPI PCI-PCI bridge> irq 23 at device 28.3 on pci0 >>>> pci12: <ACPI PCI bus> on pcib5 >>>> uhci0: <UHCI (generic) USB controller> port 0x1800-0x181f irq 16 at >>>> device 29.0 on pci0 >>>> uhci0: [GIANT-LOCKED] >>>> uhci0: [ITHREAD] >>>> usb0: <UHCI (generic) USB controller> on uhci0 >>>> usb0: USB revision 1.0 >>>> uhub0: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0 >>>> uhub0: 2 ports with 2 removable, self powered >>>> uhci1: <UHCI (generic) USB controller> port 0x1820-0x183f irq 17 at >>>> device 29.1 on pci0 >>>> uhci1: [GIANT-LOCKED] >>>> uhci1: [ITHREAD] >>>> usb1: <UHCI (generic) USB controller> on uhci1 >>>> usb1: USB revision 1.0 >>>> uhub1: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb1 >>>> uhub1: 2 ports with 2 removable, self powered >>>> uhci2: <UHCI (generic) USB controller> port 0x1840-0x185f irq 18 at >>>> device 29.2 on pci0 >>>> uhci2: [GIANT-LOCKED] >>>> uhci2: [ITHREAD] >>>> usb2: <UHCI (generic) USB controller> on uhci2 >>>> usb2: USB revision 1.0 >>>> uhub2: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb2 >>>> uhub2: 2 ports with 2 removable, self powered >>>> uhci3: <UHCI (generic) USB controller> port 0x1860-0x187f irq 19 at >>>> device 29.3 on pci0 >>>> uhci3: [GIANT-LOCKED] >>>> uhci3: [ITHREAD] >>>> usb3: <UHCI (generic) USB controller> on uhci3 >>>> usb3: USB revision 1.0 >>>> uhub3: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb3 >>>> uhub3: 2 ports with 2 removable, self powered >>>> ehci0: <Intel 82801GB/R (ICH7) USB 2.0 controller> mem >>>> 0xee404000-0xee4043ff irq 19 at device 29.7 on pci0 >>>> ehci0: [GIANT-LOCKED] >>>> ehci0: [ITHREAD] >>>> usb4: EHCI version 1.0 >>>> usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 >>>> usb4: <Intel 82801GB/R (ICH7) USB 2.0 controller> on ehci0 >>>> usb4: USB revision 2.0 >>>> uhub4: <Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb4 >>>> uhub4: 8 ports with 8 removable, self powered >>>> pcib6: <ACPI PCI-PCI bridge> at device 30.0 on pci0 >>>> pci21: <ACPI PCI bus> on pcib6 >>>> cbb0: <TI1510 PCI-CardBus Bridge> mem 0xe4300000-0xe4300fff irq 16 at >>>> device 0.0 on pci21 >>>> cardbus0: <CardBus bus> on cbb0 >>>> pccard0: <16-bit PCCard bus> on cbb0 >>>> cbb0: [ITHREAD] >>>> isab0: <PCI-ISA bridge> at device 31.0 on pci0 >>>> isa0: <ISA bus> on isab0 >>>> atapci0: <Intel ICH7 UDMA100 controller> port >>>> 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1880-0x188f at device 31.1 on pci0 >>>> ata0: <ATA channel 0> on atapci0 >>>> ata0: [ITHREAD] >>>> atapci1: <Intel AHCI controller> port >>>> 0x18c8-0x18cf,0x18ac-0x18af,0x18c0-0x18c7,0x18a8-0x18ab,0x18b0-0x18bf >>>> mem 0xee404400-0xee4047ff irq 16 at device 31.2 on pci0 >>>> atapci1: [ITHREAD] >>>> atapci1: AHCI Version 01.10 controller with 4 ports detected >>>> ata2: <ATA channel 0> on atapci1 >>>> ata2: [ITHREAD] >>>> ata3: <ATA channel 1> on atapci1 >>>> ata3: port not implemented >>>> ata3: [ITHREAD] >>>> ata4: <ATA channel 2> on atapci1 >>>> ata4: port not implemented >>>> ata4: [ITHREAD] >>>> ata5: <ATA channel 3> on atapci1 >>>> ata5: port not implemented >>>> ata5: [ITHREAD] >>>> pci0: <serial bus, SMBus> at device 31.3 (no driver attached) >>>> acpi_tz0: <Thermal Zone> on acpi0 >>>> acpi_tz1: <Thermal Zone> on acpi0 >>>> atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0 >>>> atkbd0: <AT Keyboard> irq 1 on atkbdc0 >>>> kbd0 at atkbd0 >>>> atkbd0: [GIANT-LOCKED] >>>> atkbd0: [ITHREAD] >>>> psm0: <PS/2 Mouse> irq 12 on atkbdc0 >>>> psm0: [GIANT-LOCKED] >>>> psm0: [ITHREAD] >>>> psm0: model Generic PS/2 mouse, device ID 0 >>>> battery0: <ACPI Control Method Battery> on acpi0 >>>> acpi_acad0: <AC Adapter> on acpi0 >>>> acpi_ibm0: <IBM ThinkPad ACPI Extras> on acpi0 >>>> cpu0: <ACPI CPU> on acpi0 >>>> est0: <Enhanced SpeedStep Frequency Control> on cpu0 >>>> p4tcc0: <CPU Frequency Thermal Control> on cpu0 >>>> cpu1: <ACPI CPU> on acpi0 >>>> est1: <Enhanced SpeedStep Frequency Control> on cpu1 >>>> p4tcc1: <CPU Frequency Thermal Control> on cpu1 >>>> pmtimer0 on isa0 >>>> orm0: <ISA Option ROMs> at iomem >>>> 0xd0000-0xd0fff,0xd1000-0xd1fff,0xdc000-0xdffff,0xe0000-0xeffff pnpid >>>> ORM0000 on isa0 >>>> ppc0: parallel port not found. >>>> sc0: <System console> at flags 0x100 on isa0 >>>> sc0: VGA <16 virtual consoles, flags=0x300> >>>> sio0: configured irq 4 not in bitmap of probed irqs 0 >>>> sio0: port may not be enabled >>>> sio0: configured irq 4 not in bitmap of probed irqs 0 >>>> sio0: port may not be enabled >>>> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 >>>> sio0: type 8250 or not responding >>>> sio0: [FILTER] >>>> sio1: configured irq 3 not in bitmap of probed irqs 0 >>>> sio1: port may not be enabled >>>> vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 >>>> ums0: <Logitech USB-PS/2 Optical Mouse, class 0/0, rev 2.00/27.20, addr >>>> 2> on uhub0 >>>> ums0: 8 buttons and Z dir. >>>> ugen0: <STMicroelectronics Biometric Coprocessor, class 0/0, rev >>>> 1.00/0.01, addr 2> on uhub3 >>>> Timecounters tick every 1.000 msec >>>> acd0: DVDR <HL-DT-ST DVDRAM GSA-4083N/1.08> at ata0-master UDMA33 >>>> ad4: 152627MB <SAMSUNG HM160HI HR100-08> at ata2-master SATA150 >>>> hdac0: HDA Codec #0: Analog Devices AD1981HD >>>> hdac0: HDA Codec #1: Conexant (Unknown) >>>> pcm0: <HDA Analog Devices AD1981HD PCM #0 Analog> at cad 0 nid 1 on hdac0 >>>> pcm1: <HDA Analog Devices AD1981HD PCM #1 Digital> at cad 0 nid 1 on hdac0 >>>> SMP: AP CPU #1 Launched! >>>> Trying to mount root from ufs:/dev/ad4s1a > _______________________________________________ > 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" >> -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAklwTxoACgkQCnBgS+kUGEtxkQCgnfjsmtfjEMcRW10ps3rRXf7l Mj8AnRwN178JrMkqeKMKQnCIKz7a/ohA =uGLT -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Fri Jan 16 10:48:36 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 30A181065741 for <freebsd-stable@freebsd.org>; Fri, 16 Jan 2009 10:48:36 +0000 (UTC) (envelope-from marc@sanity.de) Received: from mail.adandbreakfast.com (mail.adandbreakfast.com [194.245.32.131]) by mx1.freebsd.org (Postfix) with ESMTP id 6F0668FC25 for <freebsd-stable@freebsd.org>; Fri, 16 Jan 2009 10:48:35 +0000 (UTC) (envelope-from marc@sanity.de) Received: from localhost (localhost [127.0.0.1]) by mail.adandbreakfast.com (Postfix) with ESMTP id 050868C4053; Fri, 16 Jan 2009 11:48:34 +0100 (CET) Received: from mail.adandbreakfast.com ([194.245.32.131]) by localhost (mail.adandbreakfast.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 22625-10; Fri, 16 Jan 2009 11:48:33 +0100 (CET) Received: from videoschnitt.agentur.local (unknown [192.168.83.220]) by mail.adandbreakfast.com (Postfix) with ESMTP id 7BAA28C404E; Fri, 16 Jan 2009 11:48:33 +0100 (CET) Message-ID: <49706601.4090405@sanity.de> Date: Fri, 16 Jan 2009 11:48:33 +0100 From: Marc Peters <marc@sanity.de> User-Agent: Thunderbird 2.0.0.19 (X11/20090106) MIME-Version: 1.0 To: "Paul B. Mahol" <onemda@gmail.com> References: <496F0E85.5090904@sanity.de> <3a142e750901150252v5633f808q71d3fa3ab5050b20@mail.gmail.com> <496F458E.6050708@sanity.de> <3a142e750901150825r73fa6d82g6b14d20f3548b8eb@mail.gmail.com> In-Reply-To: <3a142e750901150825r73fa6d82g6b14d20f3548b8eb@mail.gmail.com> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at agentur.local Cc: freebsd-stable@freebsd.org Subject: Re: kernel panics when connected through wpi to apple extreme ap X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 16 Jan 2009 10:48:37 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 after searching the PR database it looks to me, that my problem is related to http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/128917 , which describes problem of if_wpi with WPA + TKIP. unfortunately the apple gui for their base stations don't give me any option to see, what encryption type it's using with WPA/WPA2 but it looks like their using TKIP with WPA and AES only with WPA2. i will try to force FreeBSD to use AES and will test a little further or switch the base station to WPA2, where it should use AES only. Paul B. Mahol schrieb: > On 1/15/09, Marc Peters <marc@sanity.de> wrote: > hi paul, > > msgbuf.txt: > [snipping dmesg and startup-messages] > Fatal trap 12: page fault while in kernel mode > cpuid = 1; apic id = 01 > fault virtual address = 0xffff > fault code = supervisor read, page not present > instruction pointer = 0x20:0xc0e70dfc > stack pointer = 0x28:0xe58bbbe0 > frame pointer = 0x28:0xe58bbc9c > 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 = 25 (wpi0 taskq) > > ddb.txt (just bt output here): > > db> bt > > Tracing pid 25 tid 100024 td 0xc5189af0 > wpi_ops(c52c5000,1,c0b7cf36,0,0,...) at wpi_ops+0x89c > taskqueue_run(c52ab200,c52ab21c,0,c0b7cf36,0,...) at taskqueue_run+0x175 > taskqueue_thread_loop(c52c69b4,e58bbd38,0,0,0,...) at > taskqueue_thread_loop+0xbb > fork_exit(c07fb2b0,c52c69b4,e58bbd38) at fork_exit+0x99 > fork_trampoline() at fork_trampoline+0x8 > --- trap 0, eip = 0, esp = 0xe58bbd70, ebp = 0 --- > > version.txt: > FreeBSD 7.1-STABLE #0: Thu Jan 15 13:51:12 CET 2009 > root@lappi.agentur.local:/usr/obj/usr/src/sys/DEBUG_DRM > > if you need more information, i will provide it. it took wpi some time > to crash, so i stressed it a little bit with an ftp download and a > buildworld through an ssh-screen. > > >> Maybe it is some locking issue at first look. Send problem report so >> that this doesnt get lost. >> Are you sure this is regression? Anyway check if same issue is not >> already reported. > >> Give this a try: > >> gdb >> gdb> file /boot/YOUR_KERNEL/if_wpi.ko >> gdb> l *wpi_ops+0x89c > >> And post output. > > marc > > > Paul B. Mahol schrieb: >>>> On 1/15/09, Marc Peters <marc@sanity.de> wrote: >>>> hello list, >>>> >>>> i have a lenovo t60 with an integrated intel 3945ABG wireless chipset. >>>> when i was running 7.1-PRERELEASE i realised that the network connection >>>> of my wpi died after some time when connected to the mention apple >>>> access point. i had to restart the card and everything went fine, for >>>> some time (about half an hour). since 7.1-RELEASE and now with >>>> 7.1-STABLE the kernel panics with a fatal trap and dumps it's core after >>>> some minutes (this output ist from -RELEASE-p1, but it's identical to >>>> the one i got from -STABLE): >>>> >>>> Fatal trap 12: page fault while in kernel mode >>>> cpuid = 0; apic id = 00 >>>> fault virtual address = 0xffff >>>> fault code = supervisor read, page not present >>>> instruction pointer = 0x20:0xc0deadfc >>>> stack pointer = 0x28:0xe58bbbe0 >>>> frame pointer = 0x28:0xe58bbc9c >>>> 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 = 25 (wpi0 taskq) >>>> trap number = 12 >>>> panic: page fault >>>> cpuid = 0 >>>> Uptime: 6m 14s >>>> Physical memory: 2034 MB >>>> Dumping 149 MB: 134 118 192 86 70 65 38 22 6 >>>> Dump complete >>>> Automatic reboot in 15 seconds - press a key on the console to abort >>>> >>>> when i run this box connected to a netgear-ap i have at home, everything >>>> is fine (and was before, no panics, no connection dropping). i have the >>>> dump at hand, but since it's 150 MB i won't send it around via mail. if >>>> anyone is interested, i can upload it somewhere and send the link. >>>> >>>> anyone any ideas? >>>> >>>>> Enable textdump(8) and post bt output from debuger once panic happen. >>>>> (I'm not going to download 150MB) >>>> marc >>>> >>>> dmesg: >>>> >>>> Copyright (c) 1992-2009 The FreeBSD Project. >>>> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 >>>> The Regents of the University of California. All rights reserved. >>>> FreeBSD is a registered trademark of The FreeBSD Foundation. >>>> FreeBSD 7.1-STABLE #0: Wed Jan 14 13:23:00 CET 2009 >>>> root@lappi.agentur.local:/usr/obj/usr/src/sys/GENERIC_DRM >>>> Timecounter "i8254" frequency 1193182 Hz quality 0 >>>> CPU: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz (1995.02-MHz >>>> 686-class CPU) >>>> Origin = "GenuineIntel" Id = 0x6f6 Stepping = 6 >>>> >>>> Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> >>>> >>>> Features2=0xe3bd<SSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM> >>>> AMD Features=0x20100000<NX,LM> >>>> AMD Features2=0x1<LAHF> >>>> Cores per package: 2 >>>> real memory = 2146238464 (2046 MB) >>>> avail memory = 2090221568 (1993 MB) >>>> ACPI APIC Table: <LENOVO TP-79 > >>>> FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs >>>> cpu0 (BSP): APIC ID: 0 >>>> cpu1 (AP): APIC ID: 1 >>>> ACPI Warning (tbfadt-0505): Optional field "Gpe1Block" has zero address >>>> or length: 0 102C/0 [20070320] >>>> ioapic0: Changing APIC ID to 1 >>>> ioapic0 <Version 2.0> irqs 0-23 on motherboard >>>> kbd1 at kbdmux0 >>>> ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) >>>> acpi0: <LENOVO TP-79> on motherboard >>>> acpi0: [ITHREAD] >>>> acpi_ec0: <Embedded Controller: GPE 0x1c, ECDT> port 0x62,0x66 on acpi0 >>>> acpi0: Power Button (fixed) >>>> acpi0: reservation of 0, a0000 (3) failed >>>> acpi0: reservation of 100000, 7ff00000 (3) failed >>>> Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 >>>> acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 >>>> acpi_hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on >>>> acpi0 >>>> Timecounter "HPET" frequency 14318180 Hz quality 900 >>>> acpi_lid0: <Control Method Lid Switch> on acpi0 >>>> acpi_button0: <Sleep Button> on acpi0 >>>> pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0 >>>> pci0: <ACPI PCI bus> on pcib0 >>>> pcib1: <ACPI PCI-PCI bridge> irq 16 at device 1.0 on pci0 >>>> pci1: <ACPI PCI bus> on pcib1 >>>> vgapci0: <VGA-compatible display> port 0x2000-0x20ff mem >>>> 0xd8000000-0xdfffffff,0xee100000-0xee10ffff irq 16 at device 0.0 on pci1 >>>> drm0: <ATI Mobility Radeon X1400> on vgapci0 >>>> vgapci0: child drm0 requested pci_enable_busmaster >>>> info: [drm] Initialized radeon 1.29.0 20080613 >>>> hdac0: <Intel 82801G High Definition Audio Controller> mem >>>> 0xee400000-0xee403fff irq 17 at device 27.0 on pci0 >>>> hdac0: HDA Driver Revision: 20090110_0123 >>>> hdac0: [ITHREAD] >>>> pcib2: <ACPI PCI-PCI bridge> irq 20 at device 28.0 on pci0 >>>> pci2: <ACPI PCI bus> on pcib2 >>>> em0: <Intel(R) PRO/1000 Network Connection 6.9.6> port 0x3000-0x301f mem >>>> 0xee000000-0xee01ffff irq 16 at device 0.0 on pci2 >>>> em0: Using MSI interrupt >>>> em0: [FILTER] >>>> em0: Ethernet address: 00:16:41:e3:4a:ff >>>> pcib3: <ACPI PCI-PCI bridge> irq 21 at device 28.1 on pci0 >>>> pci3: <ACPI PCI bus> on pcib3 >>>> wpi0: <Intel(R) PRO/Wireless 3945ABG> mem 0xedf00000-0xedf00fff irq 17 >>>> at device 0.0 on pci3 >>>> wpi0: Ethernet address: 00:19:d2:07:cf:36 >>>> wpi0: [ITHREAD] >>>> pcib4: <ACPI PCI-PCI bridge> irq 22 at device 28.2 on pci0 >>>> pci4: <ACPI PCI bus> on pcib4 >>>> pcib5: <ACPI PCI-PCI bridge> irq 23 at device 28.3 on pci0 >>>> pci12: <ACPI PCI bus> on pcib5 >>>> uhci0: <UHCI (generic) USB controller> port 0x1800-0x181f irq 16 at >>>> device 29.0 on pci0 >>>> uhci0: [GIANT-LOCKED] >>>> uhci0: [ITHREAD] >>>> usb0: <UHCI (generic) USB controller> on uhci0 >>>> usb0: USB revision 1.0 >>>> uhub0: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0 >>>> uhub0: 2 ports with 2 removable, self powered >>>> uhci1: <UHCI (generic) USB controller> port 0x1820-0x183f irq 17 at >>>> device 29.1 on pci0 >>>> uhci1: [GIANT-LOCKED] >>>> uhci1: [ITHREAD] >>>> usb1: <UHCI (generic) USB controller> on uhci1 >>>> usb1: USB revision 1.0 >>>> uhub1: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb1 >>>> uhub1: 2 ports with 2 removable, self powered >>>> uhci2: <UHCI (generic) USB controller> port 0x1840-0x185f irq 18 at >>>> device 29.2 on pci0 >>>> uhci2: [GIANT-LOCKED] >>>> uhci2: [ITHREAD] >>>> usb2: <UHCI (generic) USB controller> on uhci2 >>>> usb2: USB revision 1.0 >>>> uhub2: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb2 >>>> uhub2: 2 ports with 2 removable, self powered >>>> uhci3: <UHCI (generic) USB controller> port 0x1860-0x187f irq 19 at >>>> device 29.3 on pci0 >>>> uhci3: [GIANT-LOCKED] >>>> uhci3: [ITHREAD] >>>> usb3: <UHCI (generic) USB controller> on uhci3 >>>> usb3: USB revision 1.0 >>>> uhub3: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb3 >>>> uhub3: 2 ports with 2 removable, self powered >>>> ehci0: <Intel 82801GB/R (ICH7) USB 2.0 controller> mem >>>> 0xee404000-0xee4043ff irq 19 at device 29.7 on pci0 >>>> ehci0: [GIANT-LOCKED] >>>> ehci0: [ITHREAD] >>>> usb4: EHCI version 1.0 >>>> usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 >>>> usb4: <Intel 82801GB/R (ICH7) USB 2.0 controller> on ehci0 >>>> usb4: USB revision 2.0 >>>> uhub4: <Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb4 >>>> uhub4: 8 ports with 8 removable, self powered >>>> pcib6: <ACPI PCI-PCI bridge> at device 30.0 on pci0 >>>> pci21: <ACPI PCI bus> on pcib6 >>>> cbb0: <TI1510 PCI-CardBus Bridge> mem 0xe4300000-0xe4300fff irq 16 at >>>> device 0.0 on pci21 >>>> cardbus0: <CardBus bus> on cbb0 >>>> pccard0: <16-bit PCCard bus> on cbb0 >>>> cbb0: [ITHREAD] >>>> isab0: <PCI-ISA bridge> at device 31.0 on pci0 >>>> isa0: <ISA bus> on isab0 >>>> atapci0: <Intel ICH7 UDMA100 controller> port >>>> 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1880-0x188f at device 31.1 on pci0 >>>> ata0: <ATA channel 0> on atapci0 >>>> ata0: [ITHREAD] >>>> atapci1: <Intel AHCI controller> port >>>> 0x18c8-0x18cf,0x18ac-0x18af,0x18c0-0x18c7,0x18a8-0x18ab,0x18b0-0x18bf >>>> mem 0xee404400-0xee4047ff irq 16 at device 31.2 on pci0 >>>> atapci1: [ITHREAD] >>>> atapci1: AHCI Version 01.10 controller with 4 ports detected >>>> ata2: <ATA channel 0> on atapci1 >>>> ata2: [ITHREAD] >>>> ata3: <ATA channel 1> on atapci1 >>>> ata3: port not implemented >>>> ata3: [ITHREAD] >>>> ata4: <ATA channel 2> on atapci1 >>>> ata4: port not implemented >>>> ata4: [ITHREAD] >>>> ata5: <ATA channel 3> on atapci1 >>>> ata5: port not implemented >>>> ata5: [ITHREAD] >>>> pci0: <serial bus, SMBus> at device 31.3 (no driver attached) >>>> acpi_tz0: <Thermal Zone> on acpi0 >>>> acpi_tz1: <Thermal Zone> on acpi0 >>>> atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0 >>>> atkbd0: <AT Keyboard> irq 1 on atkbdc0 >>>> kbd0 at atkbd0 >>>> atkbd0: [GIANT-LOCKED] >>>> atkbd0: [ITHREAD] >>>> psm0: <PS/2 Mouse> irq 12 on atkbdc0 >>>> psm0: [GIANT-LOCKED] >>>> psm0: [ITHREAD] >>>> psm0: model Generic PS/2 mouse, device ID 0 >>>> battery0: <ACPI Control Method Battery> on acpi0 >>>> acpi_acad0: <AC Adapter> on acpi0 >>>> acpi_ibm0: <IBM ThinkPad ACPI Extras> on acpi0 >>>> cpu0: <ACPI CPU> on acpi0 >>>> est0: <Enhanced SpeedStep Frequency Control> on cpu0 >>>> p4tcc0: <CPU Frequency Thermal Control> on cpu0 >>>> cpu1: <ACPI CPU> on acpi0 >>>> est1: <Enhanced SpeedStep Frequency Control> on cpu1 >>>> p4tcc1: <CPU Frequency Thermal Control> on cpu1 >>>> pmtimer0 on isa0 >>>> orm0: <ISA Option ROMs> at iomem >>>> 0xd0000-0xd0fff,0xd1000-0xd1fff,0xdc000-0xdffff,0xe0000-0xeffff pnpid >>>> ORM0000 on isa0 >>>> ppc0: parallel port not found. >>>> sc0: <System console> at flags 0x100 on isa0 >>>> sc0: VGA <16 virtual consoles, flags=0x300> >>>> sio0: configured irq 4 not in bitmap of probed irqs 0 >>>> sio0: port may not be enabled >>>> sio0: configured irq 4 not in bitmap of probed irqs 0 >>>> sio0: port may not be enabled >>>> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 >>>> sio0: type 8250 or not responding >>>> sio0: [FILTER] >>>> sio1: configured irq 3 not in bitmap of probed irqs 0 >>>> sio1: port may not be enabled >>>> vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 >>>> ums0: <Logitech USB-PS/2 Optical Mouse, class 0/0, rev 2.00/27.20, addr >>>> 2> on uhub0 >>>> ums0: 8 buttons and Z dir. >>>> ugen0: <STMicroelectronics Biometric Coprocessor, class 0/0, rev >>>> 1.00/0.01, addr 2> on uhub3 >>>> Timecounters tick every 1.000 msec >>>> acd0: DVDR <HL-DT-ST DVDRAM GSA-4083N/1.08> at ata0-master UDMA33 >>>> ad4: 152627MB <SAMSUNG HM160HI HR100-08> at ata2-master SATA150 >>>> hdac0: HDA Codec #0: Analog Devices AD1981HD >>>> hdac0: HDA Codec #1: Conexant (Unknown) >>>> pcm0: <HDA Analog Devices AD1981HD PCM #0 Analog> at cad 0 nid 1 on hdac0 >>>> pcm1: <HDA Analog Devices AD1981HD PCM #1 Digital> at cad 0 nid 1 on hdac0 >>>> SMP: AP CPU #1 Launched! >>>> Trying to mount root from ufs:/dev/ad4s1a > _______________________________________________ > 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" >> -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAklwZgEACgkQCnBgS+kUGEuw/ACcCnzXTOAIV0aSAUxtKna/SpBL 63UAnj6t+LR7LwEMmcCwxjchpg5Mrmpf =gnG0 -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Fri Jan 16 11:33:51 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ABED51065705 for <freebsd-stable@freebsd.org>; Fri, 16 Jan 2009 11:33:51 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from constantine.ticketswitch.com (constantine.ticketswitch.com [IPv6:2002:57e0:1d4e:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id 62EBA8FC0C for <freebsd-stable@freebsd.org>; Fri, 16 Jan 2009 11:33:51 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from dilbert.rattatosk ([10.64.50.6] helo=dilbert.ticketswitch.com) by constantine.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from <petefrench@ticketswitch.com>) id 1LNmxP-000FGD-NH; Fri, 16 Jan 2009 11:33:47 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from <petefrench@ticketswitch.com>) id 1LNmxP-0003vM-Lx; Fri, 16 Jan 2009 11:33:47 +0000 To: ehrmann@gmail.com, freebsd-stable@freebsd.org In-Reply-To: <6e0e5340901151158n5108ba8ct6af8fb270b10b75b@mail.gmail.com> Message-Id: <E1LNmxP-0003vM-Lx@dilbert.ticketswitch.com> From: Pete French <petefrench@ticketswitch.com> Date: Fri, 16 Jan 2009 11:33:47 +0000 Cc: Subject: Re: zfs drive keeps failing between export and import X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 16 Jan 2009 11:33:54 -0000 > a software problem before hardware. Both drives are encrypted geli > devices. I tried to reproduce the error with 1GB disk images (vs This is probably a silly question, but are you sure that the drives are not auto detaching ? I had big problems with a zfs mirror on top of geli which turned out to be that drives mounted using "geli_devices" in rc.conf will auto detach unless you set "geli_autodetach" to NO. -pete. From owner-freebsd-stable@FreeBSD.ORG Fri Jan 16 11:52:46 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3AE4C1065673 for <freebsd-stable@freebsd.org>; Fri, 16 Jan 2009 11:52:46 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from constantine.ticketswitch.com (constantine.ticketswitch.com [IPv6:2002:57e0:1d4e:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id EE28B8FC1C for <freebsd-stable@freebsd.org>; Fri, 16 Jan 2009 11:52:45 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from dilbert.rattatosk ([10.64.50.6] helo=dilbert.ticketswitch.com) by constantine.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from <petefrench@ticketswitch.com>) id 1LNnFa-000FVN-9D; Fri, 16 Jan 2009 11:52:34 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from <petefrench@ticketswitch.com>) id 1LNnFa-0003ze-7k; Fri, 16 Jan 2009 11:52:34 +0000 To: amarat@ksu.ru, dan@langille.org In-Reply-To: <49700A66.800@ksu.ru> Message-Id: <E1LNnFa-0003ze-7k@dilbert.ticketswitch.com> From: Pete French <petefrench@ticketswitch.com> Date: Fri, 16 Jan 2009 11:52:34 +0000 Cc: freebsd-stable@freebsd.org Subject: Re: interrupt storm on MSI IXP600 based motherboards X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 16 Jan 2009 11:52:46 -0000 > trouble with onboard re(4) was resolved in -CURRENT and -STABLE, but > storms are not bound to ethernet only. storm may appear on any device. > if any device generates enough interrupts rate, storm will arrive. Yes, I just got another storm, on my ATA controller this time. Ah well, so much for the idea of disabling unneeded devices! -pete. From owner-freebsd-stable@FreeBSD.ORG Fri Jan 16 12:04:45 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8963D1065978 for <freebsd-stable@freebsd.org>; Fri, 16 Jan 2009 12:04:45 +0000 (UTC) (envelope-from dan@langille.org) Received: from nyi.unixathome.org (nyi.unixathome.org [64.147.113.42]) by mx1.freebsd.org (Postfix) with ESMTP id 4B93A8FC0A for <freebsd-stable@freebsd.org>; Fri, 16 Jan 2009 12:04:45 +0000 (UTC) (envelope-from dan@langille.org) Received: from localhost (localhost [127.0.0.1]) by nyi.unixathome.org (Postfix) with ESMTP id 7B071509C7; Fri, 16 Jan 2009 12:04:44 +0000 (GMT) X-Virus-Scanned: amavisd-new at unixathome.org Received: from nyi.unixathome.org ([127.0.0.1]) by localhost (nyi.unixathome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H4FWaOLJxATM; Fri, 16 Jan 2009 12:04:42 +0000 (GMT) Received: from smtp-auth.unixathome.org (smtp-auth.unixathome.org [10.4.7.7]) (Authenticated sender: hidden) by nyi.unixathome.org (Postfix) with ESMTPSA id 796C1509C4 ; Fri, 16 Jan 2009 12:04:42 +0000 (GMT) Message-ID: <49707790.3040102@langille.org> Date: Fri, 16 Jan 2009 07:03:28 -0500 From: Dan Langille <dan@langille.org> Organization: The FreeBSD Diary User-Agent: Thunderbird 2.0.0.19 (X11/20090111) MIME-Version: 1.0 To: Peter Jeremy <peterjeremy@optushome.com.au> References: <496D374A.3020704@langille.org> <496E9A37.20800@langille.org> <496EA339.6010808@ksu.ru> <496EB43A.8010805@langille.org> <20090116052656.GF16116@server.vk2pj.dyndns.org> In-Reply-To: <20090116052656.GF16116@server.vk2pj.dyndns.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: interrupt storm X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 16 Jan 2009 12:05:02 -0000 Peter Jeremy wrote: > On 2009-Jan-14 22:57:46 -0500, Dan Langille <dan@langille.org> wrote: >> Opening the case, reading the m/b: >> >> K9A2 Platinum MSI > > Tangentially related: For any decent M/B, kenv(8) should tell you > this without needing to open the box. woo! $ kenv LINES="24" acpi_load="YES" bootfile="kernel" comconsole_speed="9600" console="vidconsole" currdev="disk1s1a:" hint.acpi.0.oem="ACPIAM" hint.acpi.0.revision="1" hint.acpi.0.rsdp="0xfaf60" hint.acpi.0.rsdt="0xcffc0000" hint.atkbd.0.at="atkbdc" hint.atkbd.0.irq="1" hint.atkbdc.0.at="isa" hint.atkbdc.0.port="0x060" hint.fd.0.at="fdc0" hint.fd.0.drive="0" hint.fd.1.at="fdc0" hint.fd.1.drive="1" hint.fdc.0.at="isa" hint.fdc.0.drq="2" hint.fdc.0.irq="6" hint.fdc.0.port="0x3F0" hint.ppc.0.at="isa" hint.ppc.0.irq="7" hint.psm.0.at="atkbdc" hint.psm.0.irq="12" hint.sc.0.at="isa" hint.sc.0.flags="0x100" hint.sio.0.at="isa" hint.sio.0.flags="0x10" hint.sio.0.irq="4" hint.sio.0.port="0x3F8" hint.sio.1.at="isa" hint.sio.1.irq="3" hint.sio.1.port="0x2F8" hint.sio.2.at="isa" hint.sio.2.disabled="1" hint.sio.2.irq="5" hint.sio.2.port="0x3E8" hint.sio.3.at="isa" hint.sio.3.disabled="1" hint.sio.3.irq="9" hint.sio.3.port="0x2E8" hint.vga.0.at="isa" hw.ata.atapi_dma="1" interpret="OK" kernel="kernel" kernel_options="" kernelname="/boot/kernel/kernel" loaddev="disk1s1a:" mac_ifoff="NO" module_path="/boot/kernel;/boot/modules" smbios.bios.reldate="12/21/2007" smbios.bios.vendor="American Megatrends Inc." smbios.bios.version="V1.2" smbios.chassis.maker="MICRO-STAR INTERANTIONAL CO.,LTD" smbios.chassis.serial="To Be Filled By O.E.M." smbios.chassis.tag="To Be Filled By O.E.M." smbios.chassis.version="1.0" smbios.planar.maker="MICRO-STAR INTERANTIONAL CO.,LTD" smbios.planar.product="MS-7376" smbios.planar.serial="To be filled by O.E.M." smbios.planar.version="1.0" smbios.socket.enabled="1" smbios.socket.populated="1" smbios.system.maker="MICRO-STAR INTERANTIONAL CO.,LTD" smbios.system.product="MS-7376" smbios.system.serial="To Be Filled By O.E.M." smbios.system.uuid="00000000-0000-0000-0000-001d92638b28" smbios.system.version="1.0" vfs.root.mountfrom="ufs:/dev/mirror/gm0s1a" -- Dan Langille BSDCan - The Technical BSD Conference : http://www.bsdcan.org/ PGCon - The PostgreSQL Conference: http://www.pgcon.org/ From owner-freebsd-stable@FreeBSD.ORG Fri Jan 16 12:20:13 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B683110656E1; Fri, 16 Jan 2009 12:20:13 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from constantine.ticketswitch.com (constantine.ticketswitch.com [IPv6:2002:57e0:1d4e:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id 7A2728FC08; Fri, 16 Jan 2009 12:20:13 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from dilbert.rattatosk ([10.64.50.6] helo=dilbert.ticketswitch.com) by constantine.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from <petefrench@ticketswitch.com>) id 1LNng9-000FtD-G4; Fri, 16 Jan 2009 12:20:01 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from <petefrench@ticketswitch.com>) id 1LNng9-00049c-7B; Fri, 16 Jan 2009 12:20:01 +0000 To: rwatson@FreeBSD.org In-Reply-To: <alpine.BSF.2.00.0901131240330.16794@fledge.watson.org> Message-Id: <E1LNng9-00049c-7B@dilbert.ticketswitch.com> From: Pete French <petefrench@ticketswitch.com> Date: Fri, 16 Jan 2009 12:20:01 +0000 Cc: freebsd-stable@freebsd.org, drosih@rpi.edu, rblayzor.bulk@inoc.net Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 16 Jan 2009 12:20:14 -0000 > If you are able to get into the debugger, the normal commands would be most > helpful, especially if you can log the results: It finally locked up, and ctrl-alt-esc got me into the debugger at last! is there anything else you want me to get whilst it is like that aside from: > ps > show lockedvnods > show alllocks which I can go and capture as screenshots. I can probably sort out console access to it potentially if taht would eb useful whilst it is in this state ? -pete. From owner-freebsd-stable@FreeBSD.ORG Fri Jan 16 12:35:52 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B4AE4106567D; Fri, 16 Jan 2009 12:35:52 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from constantine.ticketswitch.com (constantine.ticketswitch.com [IPv6:2002:57e0:1d4e:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id 724B98FC20; Fri, 16 Jan 2009 12:35:52 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from dilbert.rattatosk ([10.64.50.6] helo=dilbert.ticketswitch.com) by constantine.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from <petefrench@ticketswitch.com>) id 1LNnvR-000G7B-CV; Fri, 16 Jan 2009 12:35:49 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from <petefrench@ticketswitch.com>) id 1LNnvR-0004Fi-An; Fri, 16 Jan 2009 12:35:49 +0000 To: rwatson@FreeBSD.org In-Reply-To: <alpine.BSF.2.00.0901131240330.16794@fledge.watson.org> Message-Id: <E1LNnvR-0004Fi-An@dilbert.ticketswitch.com> From: Pete French <petefrench@ticketswitch.com> Date: Fri, 16 Jan 2009 12:35:49 +0000 Cc: freebsd-stable@freebsd.org, drosih@rpi.edu, rblayzor.bulk@inoc.net Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 16 Jan 2009 12:35:53 -0000 > ps output from 'ps' is here: http://toybox.twisted.org.uk/~pete/71_lock_ps/ there are a lot of processes as this machine runes the same webservices as the actual webservers, just that nobody connects to them. > show lockedvnods nothing - there are no locked vnodes > show alllocks this gives me 'no suich command' theres a whole list of things I can show, but none of them look like all the locks. what about the locktree or the lockchain ? -pete. From owner-freebsd-stable@FreeBSD.ORG Fri Jan 16 13:31:10 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2DBCA106566B; Fri, 16 Jan 2009 13:31:10 +0000 (UTC) (envelope-from root@dchagin.dialup.corbina.ru) Received: from contrabass.post.ru (contrabass.post.ru [85.21.78.5]) by mx1.freebsd.org (Postfix) with ESMTP id D352D8FC14; Fri, 16 Jan 2009 13:31:09 +0000 (UTC) (envelope-from root@dchagin.dialup.corbina.ru) Received: from corbina.ru (mail.post.ru [195.14.50.16]) by contrabass.post.ru (Postfix) with ESMTP id 5B60447124; Fri, 16 Jan 2009 16:08:53 +0300 (MSK) X-Virus-Scanned: by cgpav Uf39PSi9pFi9oFi9 Received: from dchagin.dialup.corbina.ru ([78.107.232.239] verified) by corbina.ru (CommuniGate Pro SMTP 5.1.14) with ESMTPS id 1572609744; Fri, 16 Jan 2009 16:08:53 +0300 Received: from dchagin.dialup.corbina.ru (localhost.chd.net [127.0.0.1]) by dchagin.dialup.corbina.ru (8.14.3/8.14.3) with ESMTP id n0GD8qT4004747; Fri, 16 Jan 2009 16:08:52 +0300 (MSK) (envelope-from root@dchagin.dialup.corbina.ru) Received: (from root@localhost) by dchagin.dialup.corbina.ru (8.14.3/8.14.3/Submit) id n0GD8k6W004746; Fri, 16 Jan 2009 16:08:46 +0300 (MSK) (envelope-from root) Date: Fri, 16 Jan 2009 16:08:46 +0300 From: Chagin Dmitry <dchagin@freebsd.org> To: Pete French <petefrench@ticketswitch.com> Message-ID: <20090116130846.GA4726@dchagin.dialup.corbina.ru> References: <alpine.BSF.2.00.0901131240330.16794@fledge.watson.org> <E1LNnvR-0004Fi-An@dilbert.ticketswitch.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <E1LNnvR-0004Fi-An@dilbert.ticketswitch.com> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-stable@freebsd.org, drosih@rpi.edu, rwatson@freebsd.org, rblayzor.bulk@inoc.net Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 16 Jan 2009 13:31:10 -0000 On Fri, Jan 16, 2009 at 12:35:49PM +0000, Pete French wrote: > > ps > > output from 'ps' is here: http://toybox.twisted.org.uk/~pete/71_lock_ps/ > there are a lot of processes as this machine runes the same webservices > as the actual webservers, just that nobody connects to them. > > > show lockedvnods > > nothing - there are no locked vnodes > > > show alllocks > > this gives me 'no suich command' theres a whole list of things I > can show, but none of them look like all the locks. what about the locktree > or the lockchain ? > hi, please type: show lock 0xffffff0001254d20 and then show thread 0xXXXXXXXXXXX where XXXXX is 'owner' of previous output. -- Have fun! chd From owner-freebsd-stable@FreeBSD.ORG Fri Jan 16 13:34:19 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D71BB1065676; Fri, 16 Jan 2009 13:34:19 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from constantine.ticketswitch.com (constantine.ticketswitch.com [IPv6:2002:57e0:1d4e:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id 94D448FC0C; Fri, 16 Jan 2009 13:34:19 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from dilbert.rattatosk ([10.64.50.6] helo=dilbert.ticketswitch.com) by constantine.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from <petefrench@ticketswitch.com>) id 1LNopy-000Gv2-CP; Fri, 16 Jan 2009 13:34:14 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from <petefrench@ticketswitch.com>) id 1LNopy-0004ZF-AW; Fri, 16 Jan 2009 13:34:14 +0000 To: dchagin@freebsd.org In-Reply-To: <20090116130846.GA4726@dchagin.dialup.corbina.ru> Message-Id: <E1LNopy-0004ZF-AW@dilbert.ticketswitch.com> From: Pete French <petefrench@ticketswitch.com> Date: Fri, 16 Jan 2009 13:34:14 +0000 Cc: rwatson@freebsd.org, freebsd-stable@freebsd.org, drosih@rpi.edu, rblayzor.bulk@inoc.net Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 16 Jan 2009 13:34:20 -0000 > hi, please type: > show lock 0xffffff0001254d20 > and then show thread 0xXXXXXXXXXXX where XXXXX is 'owner' of previous output. http://toybox.twisted.org.uk/~pete/71_pdns_lock.png That's in Power DNS - which is interesting because the one difference between the boxes that lock and those which dont is that the locking ones are serving DNS. -pete. From owner-freebsd-stable@FreeBSD.ORG Fri Jan 16 13:47:28 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0ACE3106566B; Fri, 16 Jan 2009 13:47:28 +0000 (UTC) (envelope-from root@dchagin.dialup.corbina.ru) Received: from contrabass.post.ru (contrabass.post.ru [85.21.78.5]) by mx1.freebsd.org (Postfix) with ESMTP id AF5CD8FC17; Fri, 16 Jan 2009 13:47:27 +0000 (UTC) (envelope-from root@dchagin.dialup.corbina.ru) Received: from corbina.ru (mail.post.ru [195.14.50.16]) by contrabass.post.ru (Postfix) with ESMTP id D130544D0B; Fri, 16 Jan 2009 16:47:26 +0300 (MSK) X-Virus-Scanned: by cgpav Uf39PSi9pFi9oFi9 Received: from dchagin.dialup.corbina.ru ([78.107.232.239] verified) by corbina.ru (CommuniGate Pro SMTP 5.1.14) with ESMTPS id 1572692067; Fri, 16 Jan 2009 16:47:26 +0300 Received: from dchagin.dialup.corbina.ru (localhost.chd.net [127.0.0.1]) by dchagin.dialup.corbina.ru (8.14.3/8.14.3) with ESMTP id n0GDlQTq005018; Fri, 16 Jan 2009 16:47:26 +0300 (MSK) (envelope-from root@dchagin.dialup.corbina.ru) Received: (from root@localhost) by dchagin.dialup.corbina.ru (8.14.3/8.14.3/Submit) id n0GDlM6h005017; Fri, 16 Jan 2009 16:47:22 +0300 (MSK) (envelope-from root) Date: Fri, 16 Jan 2009 16:47:22 +0300 From: Chagin Dmitry <dchagin@freebsd.org> To: Pete French <petefrench@ticketswitch.com> Message-ID: <20090116134722.GA5000@dchagin.dialup.corbina.ru> References: <20090116130846.GA4726@dchagin.dialup.corbina.ru> <E1LNopy-0004ZF-AW@dilbert.ticketswitch.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <E1LNopy-0004ZF-AW@dilbert.ticketswitch.com> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: rwatson@freebsd.org, freebsd-stable@freebsd.org, drosih@rpi.edu, rblayzor.bulk@inoc.net Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 16 Jan 2009 13:47:28 -0000 On Fri, Jan 16, 2009 at 01:34:14PM +0000, Pete French wrote: > > hi, please type: > > show lock 0xffffff0001254d20 > > and then show thread 0xXXXXXXXXXXX where XXXXX is 'owner' of previous output. > > http://toybox.twisted.org.uk/~pete/71_pdns_lock.png > > That's in Power DNS - which is interesting because the one difference > between the boxes that lock and those which dont is that the locking > ones are serving DNS. > trace 832 -- Have fun! chd From owner-freebsd-stable@FreeBSD.ORG Fri Jan 16 13:51:30 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 027791065674; Fri, 16 Jan 2009 13:51:30 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id D27198FC1C; Fri, 16 Jan 2009 13:51:29 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id 7485A46B0C; Fri, 16 Jan 2009 08:51:29 -0500 (EST) Date: Fri, 16 Jan 2009 13:51:29 +0000 (GMT) From: Robert Watson <rwatson@FreeBSD.org> X-X-Sender: robert@fledge.watson.org To: Pete French <petefrench@ticketswitch.com> In-Reply-To: <E1LNopy-0004ZF-AW@dilbert.ticketswitch.com> Message-ID: <alpine.BSF.2.00.0901161347030.21561@fledge.watson.org> References: <E1LNopy-0004ZF-AW@dilbert.ticketswitch.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org, drosih@rpi.edu, dchagin@freebsd.org, rblayzor.bulk@inoc.net Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 16 Jan 2009 13:51:30 -0000 On Fri, 16 Jan 2009, Pete French wrote: >> hi, please type: show lock 0xffffff0001254d20 and then show thread >> 0xXXXXXXXXXXX where XXXXX is 'owner' of previous output. > > http://toybox.twisted.org.uk/~pete/71_pdns_lock.png > > That's in Power DNS - which is interesting because the one difference > between the boxes that lock and those which dont is that the locking ones > are serving DNS. I rather feared as much. Let's run down the path of "perhaps there's a problem with the new UDP locking code" for a bit and see where it takes us. Is it possible to run those boxes with WITNESS -- I believe that the fact that "show alllocks" is failing is because WITNESS isn't present. The other thing we can do is revert UDP to using purely write locks -- the risk there is that it might change the timing but not actually resolve the bug, so if we can analyze it a bit using WITNESS first that would be useful. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-stable@FreeBSD.ORG Fri Jan 16 14:09:27 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A63C2106567A; Fri, 16 Jan 2009 14:09:27 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from constantine.ticketswitch.com (constantine.ticketswitch.com [IPv6:2002:57e0:1d4e:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id 61FB28FC22; Fri, 16 Jan 2009 14:09:27 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from dilbert.rattatosk ([10.64.50.6] helo=dilbert.ticketswitch.com) by constantine.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from <petefrench@ticketswitch.com>) id 1LNpO1-000HLQ-2H; Fri, 16 Jan 2009 14:09:25 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from <petefrench@ticketswitch.com>) id 1LNpO1-0004li-0P; Fri, 16 Jan 2009 14:09:25 +0000 To: dchagin@freebsd.org In-Reply-To: <20090116134722.GA5000@dchagin.dialup.corbina.ru> Message-Id: <E1LNpO1-0004li-0P@dilbert.ticketswitch.com> From: Pete French <petefrench@ticketswitch.com> Date: Fri, 16 Jan 2009 14:09:25 +0000 Cc: rwatson@freebsd.org, freebsd-stable@freebsd.org, drosih@rpi.edu, rblayzor.bulk@inoc.net Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 16 Jan 2009 14:09:28 -0000 > trace 832 http://toybox.twisted.org.uk/~pete/71_trace_832_1.png http://toybox.twisted.org.uk/~pete/71_trace_832_2.png -pete. From owner-freebsd-stable@FreeBSD.ORG Fri Jan 16 14:14:19 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3CA62106564A; Fri, 16 Jan 2009 14:14:19 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from constantine.ticketswitch.com (constantine.ticketswitch.com [IPv6:2002:57e0:1d4e:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id EB1308FC1A; Fri, 16 Jan 2009 14:14:18 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from dilbert.rattatosk ([10.64.50.6] helo=dilbert.ticketswitch.com) by constantine.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from <petefrench@ticketswitch.com>) id 1LNpSj-000HPJ-PW; Fri, 16 Jan 2009 14:14:17 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from <petefrench@ticketswitch.com>) id 1LNpSj-0004n7-Na; Fri, 16 Jan 2009 14:14:17 +0000 To: rwatson@FreeBSD.org In-Reply-To: <alpine.BSF.2.00.0901161347030.21561@fledge.watson.org> Message-Id: <E1LNpSj-0004n7-Na@dilbert.ticketswitch.com> From: Pete French <petefrench@ticketswitch.com> Date: Fri, 16 Jan 2009 14:14:17 +0000 Cc: freebsd-stable@freebsd.org, drosih@rpi.edu, dchagin@freebsd.org, rblayzor.bulk@inoc.net Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 16 Jan 2009 14:14:19 -0000 > I rather feared as much. Let's run down the path of "perhaps there's a > problem with the new UDP locking code" for a bit and see where it takes us. > Is it possible to run those boxes with WITNESS -- I believe that the fact that > "show alllocks" is failing is because WITNESS isn't present. Yes, I can do that. The only reason I wasn't running with WITNESS is that it didn't lock up when I added the BREAK_TO_DEBUGGER so I was seeing if a simple GENERIC kernel would lock up when I added that. I will go back and add WITNESS when you tell me theres nothing more we can get out of this lock up (recompiling will involve restarting the machine so I loose the 'boekn to debugger' state). Should I add anything else ? Skip spinlocks ? Invariants ? > The other thing we can do is revert UDP to using purely write locks -- the > risk there is that it might change the timing but not actually resolve the > bug, so if we can analyze it a bit using WITNESS first that would be useful. Yes, I will run with WITNESS and anything else you might want. Is there anything else you, or anyone else, wants from this kernel ? It may take another day to lock up when I've restarted it unfortunately. -pete. From owner-freebsd-stable@FreeBSD.ORG Fri Jan 16 14:16:48 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4C33F106564A; Fri, 16 Jan 2009 14:16:48 +0000 (UTC) (envelope-from rwatson@FreeBSD.ogr) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 27FE98FC1B; Fri, 16 Jan 2009 14:16:48 +0000 (UTC) (envelope-from rwatson@FreeBSD.ogr) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id D532446B42; Fri, 16 Jan 2009 09:16:47 -0500 (EST) Date: Fri, 16 Jan 2009 14:16:47 +0000 (GMT) From: Robert Watson <rwatson@FreeBSD.ogr> X-X-Sender: robert@fledge.watson.org To: Pete French <petefrench@ticketswitch.com> In-Reply-To: <E1LNpSj-0004n7-Na@dilbert.ticketswitch.com> Message-ID: <alpine.BSF.2.00.0901161415360.21561@fledge.watson.org> References: <E1LNpSj-0004n7-Na@dilbert.ticketswitch.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org, drosih@rpi.edu, dchagin@freebsd.org, rblayzor.bulk@inoc.net Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 16 Jan 2009 14:16:48 -0000 On Fri, 16 Jan 2009, Pete French wrote: >> I rather feared as much. Let's run down the path of "perhaps there's a >> problem with the new UDP locking code" for a bit and see where it takes us. >> Is it possible to run those boxes with WITNESS -- I believe that the fact >> that "show alllocks" is failing is because WITNESS isn't present. > > Yes, I can do that. The only reason I wasn't running with WITNESS is that it > didn't lock up when I added the BREAK_TO_DEBUGGER so I was seeing if a > simple GENERIC kernel would lock up when I added that. I will go back and > add WITNESS when you tell me theres nothing more we can get out of this lock > up (recompiling will involve restarting the machine so I loose the 'boekn to > debugger' state). Should I add anything else ? Skip spinlocks ? Invariants ? > >> The other thing we can do is revert UDP to using purely write locks -- the >> risk there is that it might change the timing but not actually resolve the >> bug, so if we can analyze it a bit using WITNESS first that would be >> useful. > > Yes, I will run with WITNESS and anything else you might want. Is there > anything else you, or anyone else, wants from this kernel ? It may take > another day to lock up when I've restarted it unfortunately. If you do INVARIANTS + WITNESS + WITNESS_SKIPSPIN, that should be good. WITNESS does a number of things, including tracking (and being judgemental about) lock order. One nice side effect of that tracking is that we keep track of a lot more lock state explicitly, so DDB's "show allocks", "show locks", etc, commands can build on that. "show lockedvnods" works without WITNESS, though, so your results so far suggest this is likely not related to vnode locking. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-stable@FreeBSD.ORG Fri Jan 16 15:24:58 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 20F48106564A for <freebsd-stable@FreeBSD.org>; Fri, 16 Jan 2009 15:24:58 +0000 (UTC) (envelope-from danger@FreeBSD.org) Received: from hosting.cia.sk (hosting.cia.sk [92.240.234.123]) by mx1.freebsd.org (Postfix) with ESMTP id A2A0E8FC0A for <freebsd-stable@FreeBSD.org>; Fri, 16 Jan 2009 15:24:57 +0000 (UTC) (envelope-from danger@FreeBSD.org) Received: from hosting.cia.sk (hosting.cia.sk [92.240.234.123]) by hosting.cia.sk (8.14.3/8.14.3) with ESMTP id n0GF9PVk048546; Fri, 16 Jan 2009 16:09:25 +0100 (CET) (envelope-from danger@FreeBSD.org) Received: (from www@localhost) by hosting.cia.sk (8.14.3/8.14.3/Submit) id n0GF9JBg048442; Fri, 16 Jan 2009 16:09:19 +0100 (CET) (envelope-from danger@FreeBSD.org) X-Authentication-Warning: hosting.cia.sk: www set sender to danger@FreeBSD.org using -f To: Pete French <petefrench@ticketswitch.com> MIME-Version: 1.0 Date: Fri, 16 Jan 2009 16:09:19 +0100 From: Daniel Gerzo <danger@FreeBSD.org> Organization: The FreeBSD Project In-Reply-To: <E1LNnFa-0003ze-7k@dilbert.ticketswitch.com> References: <E1LNnFa-0003ze-7k@dilbert.ticketswitch.com> Message-ID: <e6d031b4f7bf9851833cef028b3870cb@services.rulez.sk> X-Sender: danger@FreeBSD.org User-Agent: RoundCube Webmail/0.2a Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="UTF-8" Cc: amarat@ksu.ru, freebsd-stable@FreeBSD.org, dan@langille.org Subject: Re: interrupt storm on MSI IXP600 based motherboards X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 16 Jan 2009 15:24:58 -0000 On Fri, 16 Jan 2009 11:52:34 +0000, Pete French <petefrench@ticketswitch.com> wrote: >> trouble with onboard re(4) was resolved in -CURRENT and -STABLE, but >> storms are not bound to ethernet only. storm may appear on any device. >> if any device generates enough interrupts rate, storm will arrive. > > Yes, I just got another storm, on my ATA controller this time. Ah > well, so much for the idea of disabling unneeded devices! Yah, I have the same exprience when we disabled onboard nic and added intel pci based one; the storm went elsewhere... I don't personally own such box, but I had a few of them at hetzner.de. -- Kind regards Daniel From owner-freebsd-stable@FreeBSD.ORG Fri Jan 16 15:40:16 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 83E80106566B; Fri, 16 Jan 2009 15:40:16 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from constantine.ticketswitch.com (constantine.ticketswitch.com [IPv6:2002:57e0:1d4e:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id 64FC28FC20; Fri, 16 Jan 2009 15:40:15 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from dilbert.rattatosk ([10.64.50.6] helo=dilbert.ticketswitch.com) by constantine.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from <petefrench@ticketswitch.com>) id 1LNqnr-000IeC-VZ; Fri, 16 Jan 2009 15:40:11 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from <petefrench@ticketswitch.com>) id 1LNqnr-0005Lo-UC; Fri, 16 Jan 2009 15:40:11 +0000 To: rwatson@FreeBSD.org Message-Id: <E1LNqnr-0005Lo-UC@dilbert.ticketswitch.com> From: Pete French <petefrench@ticketswitch.com> Date: Fri, 16 Jan 2009 15:40:11 +0000 Cc: freebsd-stable@freebsd.org Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 16 Jan 2009 15:40:16 -0000 > If you do INVARIANTS + WITNESS + WITNESS_SKIPSPIN, that should be good. > WITNESS does a number of things, including tracking (and being judgemental > about) lock order. One nice side effect of that tracking is that we keep > track of a lot more lock state explicitly, so DDB's "show allocks", "show > locks", etc, commands can build on that. "show lockedvnods" works without > WITNESS, though, so your results so far suggest this is likely not related to > vnode locking. Right, I've gone back to my DEBUG kernel which has a lot of options in it, including all the above. It has locked almost immediately luckily, so now I have it sitting at the debugger prompt. The output from 'show alllocks' is here: http://toybox.twisted.org.uk/~pete/71_show_alllocks.png Which of these are worth tracing ? -pte. From owner-freebsd-stable@FreeBSD.ORG Fri Jan 16 17:38:03 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D696C1065675; Fri, 16 Jan 2009 17:38:03 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from constantine.ticketswitch.com (constantine.ticketswitch.com [IPv6:2002:57e0:1d4e:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id F0A978FC18; Fri, 16 Jan 2009 17:38:02 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from dilbert.rattatosk ([10.64.50.6] helo=dilbert.ticketswitch.com) by constantine.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from <petefrench@ticketswitch.com>) id 1LNsdu-000K1S-2E; Fri, 16 Jan 2009 17:38:02 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from <petefrench@ticketswitch.com>) id 1LNsdu-0005vy-0W; Fri, 16 Jan 2009 17:38:02 +0000 To: rwatson@FreeBSD.org In-Reply-To: <alpine.BSF.2.00.0901131607580.95856@fledge.watson.org> Message-Id: <E1LNsdu-0005vy-0W@dilbert.ticketswitch.com> From: Pete French <petefrench@ticketswitch.com> Date: Fri, 16 Jan 2009 17:38:02 +0000 Cc: dougb@freebsd.org, freebsd-stable@freebsd.org, kometen@gmail.com Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 16 Jan 2009 17:38:07 -0000 Just confinuing to look at this with the help of Dimity, and the output from 'bt' is here: http://toybox.twisted.org.uk/~pete/71_bt.png The top bit of that is from my 'show alllocks' the full version of whih is here: http://toybox.twisted.org.uk/~pete/71_show_alllocks.png -pete. From owner-freebsd-stable@FreeBSD.ORG Fri Jan 16 17:51:57 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B74BE106566B for <freebsd-stable@freebsd.org>; Fri, 16 Jan 2009 17:51:57 +0000 (UTC) (envelope-from korvus@comcast.net) Received: from QMTA08.westchester.pa.mail.comcast.net (qmta08.westchester.pa.mail.comcast.net [76.96.62.80]) by mx1.freebsd.org (Postfix) with ESMTP id 662D18FC12 for <freebsd-stable@freebsd.org>; Fri, 16 Jan 2009 17:51:57 +0000 (UTC) (envelope-from korvus@comcast.net) Received: from OMTA02.westchester.pa.mail.comcast.net ([76.96.62.19]) by QMTA08.westchester.pa.mail.comcast.net with comcast id 4Er01b00A0QuhwU58HeiGX; Fri, 16 Jan 2009 17:38:42 +0000 Received: from [192.168.2.164] ([206.210.89.202]) by OMTA02.westchester.pa.mail.comcast.net with comcast id 4HeY1b00C4Mx3R23NHeaJU; Fri, 16 Jan 2009 17:38:40 +0000 Message-ID: <4970C617.50309@comcast.net> Date: Fri, 16 Jan 2009 12:38:31 -0500 From: Steve Polyack <korvus@comcast.net> User-Agent: Thunderbird 2.0.0.19 (X11/20090105) MIME-Version: 1.0 To: freebsd-hardware@freebsd.org, Mike Tancsa <freebsd-stable@freebsd.org> References: <496CEB13.5040806@comcast.net> In-Reply-To: <496CEB13.5040806@comcast.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: amr driver changes in FreeBSD 7.1-RELEASE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 16 Jan 2009 17:51:58 -0000 In case anyone is interested, the situation has only gotten weirder. Booting 7.1-R with 'boot -v' mysteriously adds: (probe32:amr1:1:6:0): error 22 (probe32:amr1:1:6:0): Unretryable Error However, amr1 is not the one that is giving us issues. It appears to work fine. amr0 is the one on which 7.1-R fails to find any volumes. Even stranger, a 'camcontrol devlist' manages to display all off the individual SCSI drives attached to amr0. Finally, this problem was solved whilst writing this e-mail. The default for kern.cam.scsi_delay (5000ms) appears to be too aggressive in my circumstances. Increasing it to 15000 solves my issue (and gets rid of "amr0: adapter is busy" messages). Steve Polyack wrote: > Hello, > > We have a Dell PowerEdge 1850 server. It contains two PERC4 RAID > controllers. One is a PERC4e/Si, and the other is a PERC4/DC. Right > now we are running FreeBSD 6.3-RELEASE, with a 36GB RAID-1 on the > PERC4e/Si (amr0), and both a 1TB RAID5 and a 136GB RAID1 on the > PERC4/DC(amr1). Both adapters are running the latest firmware revision. > > When we boot FreeBSD7.1 install media, the amr driver fails to detect > any volumes (disks) attached to amr0, the PERC4e/Si. However, it > picks up the attached disks on the PERC4/DC just fine. However, if I > boot 7.0-RELEASE install media, it picks up all of the attached > volumes, leading me to believe the issue is due to changes in the amr > driver between 7.0 and 7.1. During the 7.1 boot process, before > probing disks, we see the message "amr0: adapter is busy" show up > twice. This also does not occur on the 6.3, 6.4, or 7.0 releases. > > We also have another PE1850 with a very similar configuration, except > the two PERCs get probed in a different order, and it detects all of > the attached volumes without any issues. > > Any suggestions? These are semi-critical systems, so we aren't always > able to test things like this. But, we can schedule downtime once or > twice a week if necessary. > > -Steve Polyack > _______________________________________________ > 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 Fri Jan 16 20:11:19 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 549D61065677 for <freebsd-stable@freebsd.org>; Fri, 16 Jan 2009 20:11:19 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: from mail-bw0-f20.google.com (mail-bw0-f20.google.com [209.85.218.20]) by mx1.freebsd.org (Postfix) with ESMTP id A99A08FC21 for <freebsd-stable@freebsd.org>; Fri, 16 Jan 2009 20:11:18 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: by bwz13 with SMTP id 13so6200815bwz.19 for <freebsd-stable@freebsd.org>; Fri, 16 Jan 2009 12:11:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=PDeqRGKAjib0bic/yZjy6ClT/wamoXlyqGoYzbzIP+E=; b=CEt3HIoW5Wc/D79BxU2IwQuQsA5L0RRBxj5aIbJmakM6/2sF74w3kUM4fjGshN6VDE wVRXRSDgGcUOgdOHVnqOOI7ZPFlCI8OdUmzVo/Z5942Dm+8HewQWYKO+gNLHI8+6256G p8gMebsrEDoEgcrD2Lrkj+hy6cimyZNVEX2Gg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=pqRSsbqZdEc36Fk3G5T6kNIsEW1QrrJolS8Otu/mU8q7fW4mLLVgcjjealchnjAMNg E1mOv+AzOfNdzzneOlWSPI4zULfWkZTJWqkZrVCBDLsci1T97Y+0IzPmdcKU7RqIOXES HGJPLKKV0I5ZgCu+eRmZNyuMFzvVkgU+PgBWQ= MIME-Version: 1.0 Received: by 10.103.214.8 with SMTP id r8mr1376046muq.92.1232135099569; Fri, 16 Jan 2009 11:44:59 -0800 (PST) Date: Fri, 16 Jan 2009 14:44:59 -0500 Message-ID: <d2e731a10901161144j50889051ka10c911214cb733a@mail.gmail.com> From: grarpamp <grarpamp@gmail.com> To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: USB devices fail to attach as umass scsi da[n] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 16 Jan 2009 20:11:19 -0000 This dictation recorder fails to attach via usb. The same problem occurs with a Nikon Coolpix L1. Both work fine under windows on the same hardware. Do I need to do something to GENERIC to get this working? The machine is spare so I can recompile and submit debug info as need be. Thanks. GENERIC, RELENG_7 a few days past the 7.1 release. SuperMicro 370DER motherboard, most recent bios. The Nikon is set to mass storage. The RCA has no such option. Both have the latest firmware. By the way, the RCA records natively in mp3 format. Handy as most seem to use some closed format. Worth a try if you need one. # camcontrol devl - should be: (pass2,da2) when attach is complete scbus2 on umass-sim0 bus 0: < RCA_TKCF2494_US 1.00> at scbus2 target 0 lun 0 (da2,pass2) # dmesg - reordered a bit umass0: <RCA RCA_TKCF2494_US USB DEVICE, class 0/0, rev 1.10/1.00, addr 2> on uhub0 umass0:2:0:-1: Attached to scbus2 pass2 at umass-sim0 bus 0 target 0 lun 0 pass2: < RCA_TKCF2494_US 1.00> Removable Direct Access SCSI-0 device pass2: 1.000MB/s transfers GEOM: da2 at umass-sim0 bus 0 target 0 lun 0 new disk da2 da2: < RCA_TKCF2494_US 1.00> Removable Direct Access SCSI-0 device da2: 1.000MB/s transfers da2: 122MB (251136 512 byte sectors: 64H 32S/T 122C) (da2:umass-sim0:0:0:0): Synchronize cache failed, status == 0x4, scsi status == 0x0 (da2:umass-sim0:0:0:0): Request completed with CAM_REQ_CMP_ERR (da2:umass-sim0:0:0:0): Retrying Command (da2:umass-sim0:0:0:0): error 5 (da2:umass-sim0:0:0:0): Retries Exausted Opened disk da2 -> 5 umass0: BBB bulk-in clear stall failed, STALLED umass0: BBB bulk-out clear stall failed, STALLED umass0: BBB reset failed, STALLED umass0: Invalid CSW: tag 14 should be 15 From owner-freebsd-stable@FreeBSD.ORG Fri Jan 16 23:33:20 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> 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 46F381065674 for <stable@freebsd.org>; Fri, 16 Jan 2009 23:33:20 +0000 (UTC) (envelope-from mike@vintners.net) Received: from vinifera.vintners.net (vinifera.vintners.net [207.229.65.53]) by mx1.freebsd.org (Postfix) with ESMTP id 0CBEF8FC13 for <stable@freebsd.org>; Fri, 16 Jan 2009 23:33:19 +0000 (UTC) (envelope-from mike@vintners.net) Received: from [127.0.0.1] (brix.vintners.net [209.162.136.18]) by vinifera.vintners.net (8.14.1/8.14.3) with ESMTP id n0GNXCBt056536 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 16 Jan 2009 15:33:16 -0800 (PST) (envelope-from mike@vintners.net) Message-ID: <4971193D.9010104@vintners.net> Date: Fri, 16 Jan 2009 15:33:17 -0800 From: Mike Lempriere <mike@vintners.net> User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: "Sergey N. Voronkov" <serg@tmn.ru> References: <496EB76F.9000501@vintners.net> <20090115044333.GA42029@tmn.ru> <496F3A6F.1050505@vintners.net> <20090116033811.GA48368@tmn.ru> In-Reply-To: <20090116033811.GA48368@tmn.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-6.3 required=6.0 tests=ALL_TRUSTED,AWL,BAYES_00, RGX_BDY_BOGUS_SALUT5, RGX_BDY_LOCAL_AREA_CODE autolearn=ham version=3.2.3 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on vinifera.vintners.net Cc: stable@freebsd.org Subject: Re: named won't start X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 16 Jan 2009 23:33:20 -0000 Ah, gotcha -- I'm not using any secondary domains so this is not an issue for me. I do have an internal network, but it's mostly blocked by ipfw/nat and doesn't have a subdomain name. Thanks for explaining! Sergey N. Voronkov wrote: > On Thu, Jan 15, 2009 at 05:30:23AM -0800, Mike Lempriere wrote: > >> I'm not real clear on what item 6 means. However all of my specified >> zones have at least one NS and one A record. Does this mean I'm Ok? >> > > "Sites that were relying on this BIND 8 behaviour need to add any > omitted glue NS records, and any necessary glue A records, to the > parent zone." > > Exactly as: > > domain.com.zone: > [...] > sec IN NS ns.sec.domain.com. > ns.sec IN A 1.2.3.4 > [...] > > sec.domain.com.zone: > @ IN SOA > [...] > > Nothing more. But I'v miss Your real problem below. > > >> Sergey N. Voronkov wrote: >> >>> On Wed, Jan 14, 2009 at 08:11:27PM -0800, Mike Lempriere wrote: >>> >>> >From /var/log/messages: >>> >>>> starting BIND 9.4.3-P1 -t /var/named -u bind >>>> could not get query source dispatcher (0.0.0.0#53) >>>> loading configuration: address in use >>>> exiting (due to fatal error) >>>> > > So, the EXACT problem is a double start of the daemon. Please double check > merge of rc files after upgrade. > > >>>> I had just updated from 5-stable (at 5.5) to 6-stable (at 6.4). Upon >>>> today's upgrade I got to 7.1. Everything else seems to be be working >>>> (the machine is basically a webserver), except named. apache is serving >>>> up pages, but only until my TTL times out... >>>> >>>> I so no errors in the builds or installs. I foolwed the instructions in >>>> UPDATING. I believe I did an accurate merge of my named.conf file. >>>> >>>> > [skip] > > Sergey N. Voronkov, > Sibitex Ltd. > > > > -- Mike Lempriere- Home: mike@vintners.net Phone: 206-780-2146 Cellphone: 206-200-5902; text pager: mikelemp@tmail.com From owner-freebsd-stable@FreeBSD.ORG Fri Jan 16 23:34:58 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 061C910656F6 for <freebsd-stable@freebsd.org>; Fri, 16 Jan 2009 23:34:58 +0000 (UTC) (envelope-from ben@morrow.me.uk) Received: from plesk-mail01.plus.net (plesk-mail01.plus.net [212.56.83.229]) by mx1.freebsd.org (Postfix) with ESMTP id 4996D8FC12 for <freebsd-stable@freebsd.org>; Fri, 16 Jan 2009 23:34:56 +0000 (UTC) (envelope-from ben@morrow.me.uk) Received: (qmail 6661 invoked from network); 16 Jan 2009 23:34:55 +0000 Received: from host81-141-107-54.wlms-broadband.com (HELO osiris.mauzo.dyndns.org) (81.141.107.54) by plesk-mail01.plus.net with SMTP; 16 Jan 2009 23:34:55 +0000 Received: (qmail 18335 invoked by uid 1001); 16 Jan 2009 23:14:41 -0000 Date: Fri, 16 Jan 2009 23:14:41 +0000 From: Ben Morrow <ben@morrow.me.uk> To: freebsd-stable@freebsd.org Message-ID: <20090116231441.GA18249@osiris.mauzo.dyndns.org> Mail-Followup-To: freebsd-stable@freebsd.org References: <20090115051422.GA59032@duncan.reilly.home> <20090115120001.GA23934@osiris.mauzo.dyndns.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090115235523.GA39905@duncan.reilly.home> X-Newsgroups: gmane.os.freebsd.stable Organization: Who, me? User-Agent: Mutt/1.5.17 (2007-11-01) Subject: Re: How to get djbdns to start early enough to satisfy ntpd at boot? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 16 Jan 2009 23:34:58 -0000 Quoth Andrew Reilly <andrew-freebsd@areilly.bpc-users.org>: > On Thu, Jan 15, 2009 at 12:00:01PM +0000, Ben Morrow wrote: > > > > and I also have a /usr/local/etc/rc.d/dnscache which looks like > [snip] > > > > and a /usr/local/etc/svc.subr as attached. It's somewhat more general > > than is needed for dnscache, as I also use it to start qmail. > > Wow, those scripts are an extremely cool integration of the > rcorder framework and the svscan framework. Could these be > incorporated into the daemontools and djbdns ports as permanent > goodness? Well, it's hardly up to me :). I was wondering about submitting a patch to the appropriate ports; if you want to preempt me, feel free :). (The files would presumably need appropriate copyright and license lines added, of course.) Ben From owner-freebsd-stable@FreeBSD.ORG Fri Jan 16 23:51:28 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 28D911065673 for <freebsd-stable@freebsd.org>; Fri, 16 Jan 2009 23:51:28 +0000 (UTC) (envelope-from ehrmann@gmail.com) Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.29]) by mx1.freebsd.org (Postfix) with ESMTP id C9E468FC23 for <freebsd-stable@freebsd.org>; Fri, 16 Jan 2009 23:51:27 +0000 (UTC) (envelope-from ehrmann@gmail.com) Received: by yx-out-2324.google.com with SMTP id 8so767690yxb.13 for <freebsd-stable@freebsd.org>; Fri, 16 Jan 2009 15:51:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=Yf3haicbgqAfH6iYOfVjmghDaONUL5MQ66/uZFkJ9Rc=; b=FjbI29AB+RoIsai7oLJYlZJtLYlhpqS10vOMpXL9ADUSSHMFPdYil2ZQuGLDttzMIc LbKjLAalcQ0PmNlrqy+t5dt99M0zpMLu6NO+b9kOEAKK9htRoXUbkVMYh68bIlhSXUH0 4YbxGAM6Rzbc+uD8+fwC22jdelxdFqh5PS+S0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=RfSB3aPr4HtBz3mvjfCFpIFyfzYKveIPV6AA+KH8g5q0ra4+AyBpGYq+BgEuAqO+ua NFue5ewkL3+tO72g/8X79aIMZdDfYppIx1VcIFsgvK/1AWv9j+QDGOY4cMGExsyNFs1W viG/w1Y4EcKoQchQRxQmlwlvB3OThF6zAYXDg= Received: by 10.100.110.16 with SMTP id i16mr2444012anc.133.1232148069381; Fri, 16 Jan 2009 15:21:09 -0800 (PST) Received: by 10.100.45.1 with HTTP; Fri, 16 Jan 2009 15:21:09 -0800 (PST) Message-ID: <6e0e5340901161521t30845197s9529fb5a55dbba13@mail.gmail.com> Date: Fri, 16 Jan 2009 15:21:09 -0800 From: "David Ehrmann" <ehrmann@gmail.com> To: "Pete French" <petefrench@ticketswitch.com> In-Reply-To: <E1LNmxP-0003vM-Lx@dilbert.ticketswitch.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <6e0e5340901151158n5108ba8ct6af8fb270b10b75b@mail.gmail.com> <E1LNmxP-0003vM-Lx@dilbert.ticketswitch.com> Cc: freebsd-stable@freebsd.org Subject: Re: zfs drive keeps failing between export and import X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 16 Jan 2009 23:51:28 -0000 On Fri, Jan 16, 2009 at 3:33 AM, Pete French <petefrench@ticketswitch.com> wrote: >> a software problem before hardware. Both drives are encrypted geli >> devices. I tried to reproduce the error with 1GB disk images (vs > > This is probably a silly question, but are you sure that the drives > are not auto detaching ? I had big problems with a zfs mirror on top > of geli which turned out to be that drives mounted using "geli_devices" > in rc.conf will auto detach unless you set "geli_autodetach" to NO. Not silly at all. I didn't know that could be an issue, but they weren't mounted with "geli_devices," they were mounted by hand with "geli attach /dev/ad<disk>." I did not set the -d flag on attach, and I don't think I used the -l flag on detach, either. Listing the device says this: Geom name: ad10.eli EncryptionAlgorithm: AES-CBC KeyLength: 128 Crypto: hardware UsedKey: 0 Flags: NONE (and more stuff) One more interesting thing: I accidentally rebooted the system without any detaching/exporting (it involved a different, bad drive). When it came up, I was able to re-import tank without any problems. From owner-freebsd-stable@FreeBSD.ORG Sat Jan 17 00:00:06 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: FreeBSD-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F3222106564A for <FreeBSD-stable@FreeBSD.org>; Sat, 17 Jan 2009 00:00:05 +0000 (UTC) (envelope-from barbara.xxx1975@libero.it) Received: from cp-out1.libero.it (cp-out1.libero.it [212.52.84.101]) by mx1.freebsd.org (Postfix) with ESMTP id 73CDC8FC14 for <FreeBSD-stable@FreeBSD.org>; Sat, 17 Jan 2009 00:00:04 +0000 (UTC) (envelope-from barbara.xxx1975@libero.it) Received: from libero.it (192.168.17.6) by cp-out1.libero.it (8.5.016.1) id 495844B60150E802 for FreeBSD-stable@FreeBSD.org; Sat, 17 Jan 2009 01:00:03 +0100 Date: Sat, 17 Jan 2009 01:00:03 +0100 Message-Id: <KDL9C3$74E34BD73EE4E19F5127AF2F7D9840E5@libero.it> MIME-Version: 1.0 X-Sensitivity: 3 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable From: "barbara" <barbara.xxx1975@libero.it> To: "FreeBSD-stable" <FreeBSD-stable@FreeBSD.org> X-XaM3-API-Version: 4.3 (R1) (B3pl25) X-SenderIP: 79.18.238.74 Cc: Subject: g_vfs_done()...errors X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sat, 17 Jan 2009 00:00:06 -0000 Hello, while reading/writing dvd on 6-STABLE (can't remember on 7-STABLE right n= ow), I'm getting the message buffer filled by errors. This is my dvd-rw $ sysctl dev.acd.0.%desc dev.acd.0.%desc: PIONEER DVD-RW DVR-109/1.58 attached to $ sysctl dev.atapci.1.%desc dev.atapci.1.%desc: VIA 8237A UDMA133 controller And the followings are some examples of the error: g_vfs_done():cd0[READ(offset=3D3533693165190270976, length=3D2048)]error = =3D 5 g_vfs_done():cd0[READ(offset=3D8751655366962446336, length=3D2048)]error = =3D 5 g_vfs_done():cd0[READ(offset=3D8751655370713257984, length=3D2048)]error = =3D 5 g_vfs_done():acd0[READ(offset=3D3533693165190270976, length=3D2048)]error= =3D 5 g_vfs_done():acd0[READ(offset=3D8751655366962446336, length=3D2048)]error= =3D 5 g_vfs_done():acd0[READ(offset=3D8751655370713257984, length=3D2048)]error= =3D 5 Is it possible such a value for offset (DVD-SL)? Does anyone know the reason of the error? Should I be somehow worried? Thanks From owner-freebsd-stable@FreeBSD.ORG Sat Jan 17 04:45:56 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> 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 788261065670; Sat, 17 Jan 2009 04:45:56 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.230]) by mx1.freebsd.org (Postfix) with ESMTP id 3544A8FC1A; Sat, 17 Jan 2009 04:45:55 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so1961495rvf.43 for <multiple recipients>; Fri, 16 Jan 2009 20:45:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=6mZzrmHdQe/nAxQK23D6LgfN5UHwYZCVW6Jy9p5+HJs=; b=q+ttTelnS0vyFf2AZOk86zK+fgYYd7djXSLzWOnPtLFwii+cBk4wmZ7nRxRnFgrDnX fOI8p0moC2AOeJlVCH5MAfiqEyrBRBpm09CzI7gMR3fU6y6bN5QDB454b36pI7FCVTG8 UzUPYbVyWd7SMbGMujHhIyRFwPvSj8RLE9vDw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=ZY5ku/gOnBM2SIMzE346t5Pl17lxaF1TC60C3+bjavypXvk8apZpNVWzF7xMorvTxc Na5IY9rANPqqGofn6KvIVUTSyMYBWV5BgXJ5yRDGLKKQTtEJZWPjiJJVxav9LZwFLJnR GjQdRFW3rMd+b/7XTtYuNjJmE/rBL00KO2oFA= Received: by 10.141.197.14 with SMTP id z14mr222224rvp.63.1232167555795; Fri, 16 Jan 2009 20:45:55 -0800 (PST) Received: from michelle.cdnetworks.co.kr ([211.53.35.84]) by mx.google.com with ESMTPS id g31sm4228153rvb.4.2009.01.16.20.45.52 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 16 Jan 2009 20:45:53 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.14.3/8.14.3) with ESMTP id n0H4jlZw068865 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 17 Jan 2009 13:45:47 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.14.3/8.14.3/Submit) id n0H4jjVg068864; Sat, 17 Jan 2009 13:45:45 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Sat, 17 Jan 2009 13:45:45 +0900 From: Pyun YongHyeon <pyunyh@gmail.com> To: Bartosz Stec <admin@kkip.pl> Message-ID: <20090117044545.GA68290@cdnetworks.co.kr> References: <8dfae1c10901070639x67945324jeeecfcac647d7976@mail.gmail.com> <496DF428.6050800@kkip.pl> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="mP3DRpeJDSE+ciuQ" Content-Disposition: inline In-Reply-To: <496DF428.6050800@kkip.pl> User-Agent: Mutt/1.4.2.3i Cc: Walter Venable <walt@relnor.com>, stable@freebsd.org, yongari@freebsd.org Subject: Re: FreeBSD 7.1 Breaks re and rl Network Interface Drivers X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sat, 17 Jan 2009 04:45:56 -0000 --mP3DRpeJDSE+ciuQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Jan 14, 2009 at 03:18:16PM +0100, Bartosz Stec wrote: > Walter Venable pisze: > >FreeBSD 7.1 upgrade broke my network access, machine is totally > >offline (powered-on and I can play inside it at the terminal, but > >absolutely 0 network access): > >This happened AFTER make kernel but BEFORE make installworld. I think > >this implies it's a kernel driver issue. > > > >http://forums.freebsd.org/showthread.php?t=1323 (this is an ongoing > >thread on the issue, the rl driver has also been reported broken). > >_______________________________________________ > >freebsd-stable@freebsd.org mailing list > >http://lists.freebsd.org/mailman/listinfo/freebsd-stable > >To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > > I can confirm issues with re and 7.1-R > > dmesg: > re0: <RealTek 8169SC/8110SC Single-chip Gigabit Ethernet> port > 0xbc00-0xbcff mem 0xfbfff000-0xfbfff0ff irq 17 at device 7.0 on pci1 > re0: Chip rev. 0x18000000 > re0: MAC rev. 0x00000000 > > In my case this NIC works, but lags like hell after upgrade! Working on > console gives me pauses every 3-4 second, and second server which > connect to this one with re0 is reporting that communication is lost > every couple of minutes > Would you try attached patch? -- Regards, Pyun YongHyeon --mP3DRpeJDSE+ciuQ Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="re.8169sc.diff" Index: sys/dev/re/if_re.c =================================================================== --- sys/dev/re/if_re.c (revision 187352) +++ sys/dev/re/if_re.c (working copy) @@ -158,6 +158,8 @@ /* Tunables. */ static int msi_disable = 1; TUNABLE_INT("hw.re.msi_disable", &msi_disable); +static int prefer_iomap = 0; +TUNABLE_INT("hw.re.prefer_iomap", &prefer_iomap); #define RE_CSUM_FEATURES (CSUM_IP | CSUM_TCP | CSUM_UDP) @@ -1131,26 +1133,36 @@ pci_enable_busmaster(dev); devid = pci_get_device(dev); - /* Prefer memory space register mapping over IO space. */ - sc->rl_res_id = PCIR_BAR(1); - sc->rl_res_type = SYS_RES_MEMORY; - /* RTL8168/8101E seems to use different BARs. */ - if (devid == RT_DEVICEID_8168 || devid == RT_DEVICEID_8101E) - sc->rl_res_id = PCIR_BAR(2); + /* + * Prefer memory space register mapping over IO space. + * Because RTL8169SC does not seem to work when memory mapping + * is used always activate io mapping. + */ + if (devid == RT_DEVICEID_8169SC) + prefer_iomap = 1; + if (prefer_iomap == 0) { + sc->rl_res_id = PCIR_BAR(1); + sc->rl_res_type = SYS_RES_MEMORY; + /* RTL8168/8101E seems to use different BARs. */ + if (devid == RT_DEVICEID_8168 || devid == RT_DEVICEID_8101E) + sc->rl_res_id = PCIR_BAR(2); + } else { + sc->rl_res_id = PCIR_BAR(0); + sc->rl_res_type = SYS_RES_IOPORT; + } sc->rl_res = bus_alloc_resource_any(dev, sc->rl_res_type, &sc->rl_res_id, RF_ACTIVE); - - if (sc->rl_res == NULL) { + if (sc->rl_res == NULL && prefer_iomap == 0) { sc->rl_res_id = PCIR_BAR(0); sc->rl_res_type = SYS_RES_IOPORT; sc->rl_res = bus_alloc_resource_any(dev, sc->rl_res_type, &sc->rl_res_id, RF_ACTIVE); - if (sc->rl_res == NULL) { - device_printf(dev, "couldn't map ports/memory\n"); - error = ENXIO; - goto fail; - } } + if (sc->rl_res == NULL) { + device_printf(dev, "couldn't map ports/memory\n"); + error = ENXIO; + goto fail; + } sc->rl_btag = rman_get_bustag(sc->rl_res); sc->rl_bhandle = rman_get_bushandle(sc->rl_res); --mP3DRpeJDSE+ciuQ-- From owner-freebsd-stable@FreeBSD.ORG Sat Jan 17 04:48:08 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0A58510656BD; Sat, 17 Jan 2009 04:48:08 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.239]) by mx1.freebsd.org (Postfix) with ESMTP id AEA898FC1C; Sat, 17 Jan 2009 04:48:07 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so1961912rvf.43 for <multiple recipients>; Fri, 16 Jan 2009 20:48:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=wjitnP46DdG5iuzGawv+Q8cTtg9PMiFVWMRDuFNxdTo=; b=jCpOHhSGq4yRTXMLSBDL5jHSyNVuIu+Iofn2MKu54hV7mWLodSESqggi79YsA1ScZt seE64oU2mABqXqGtGHNVYEYBwj/3XgH6wg0+iJ0zaIUV1b3tDNhe35MCFjemebAf0VCa 8nfDczivnFlYEviHIuaHdclKf1jAuX/yKjP/A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=ZfM412goDUnM3hnssViejniI/CIOlPpGSuFoFYB+UX2agMvqwBd8nPB7FslAkszxDW iqerX7LYBmLnRpBxdlNHshSzBTBfIzHKRAlSsj4UCR7vTu65PL5iocWfGuBqYkBLPvfk 1L9imhIhtfJu5qHWb/2Rx3BUYLcEvBgqTcSoM= Received: by 10.141.137.8 with SMTP id p8mr1590535rvn.170.1232167687368; Fri, 16 Jan 2009 20:48:07 -0800 (PST) Received: from michelle.cdnetworks.co.kr ([211.53.35.84]) by mx.google.com with ESMTPS id b8sm4265675rvf.9.2009.01.16.20.48.04 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 16 Jan 2009 20:48:06 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.14.3/8.14.3) with ESMTP id n0H4m0QI068876 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 17 Jan 2009 13:48:00 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.14.3/8.14.3/Submit) id n0H4lwgl068875; Sat, 17 Jan 2009 13:47:58 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Sat, 17 Jan 2009 13:47:58 +0900 From: Pyun YongHyeon <pyunyh@gmail.com> To: Sascha Holzleiter <sascha@holzleiter.name> Message-ID: <20090117044758.GB68290@cdnetworks.co.kr> References: <8dfae1c10901070639x67945324jeeecfcac647d7976@mail.gmail.com> <496B7C17.8010107@holzleiter.name> <200901122010.37269.jkim@FreeBSD.org> <496CAB07.5020404@holzleiter.name> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="cvVnyQ+4j833TQvp" Content-Disposition: inline In-Reply-To: <496CAB07.5020404@holzleiter.name> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org, Jung-uk Kim <jkim@freebsd.org> Subject: Re: FreeBSD 7.1 Breaks re and rl Network Interface Drivers X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sat, 17 Jan 2009 04:48:08 -0000 --cvVnyQ+4j833TQvp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Jan 13, 2009 at 03:53:59PM +0100, Sascha Holzleiter wrote: > Jung-uk Kim wrote: > >On Monday 12 January 2009 12:21 pm, Sascha Holzleiter wrote: > >>Hi, > >> > >>i see similar problems with a re card: > >> > >>re0@pci0:4:7:0: class=0x020000 card=0x816710ec chip=0x816710ec > >>rev=0x10 hdr=0x00 > >> vendor = 'Realtek Semiconductor' > >> device = 'RTL8169/8110 Family Gigabit Ethernet NIC' > >> class = network > >> subclass = ethernet > >> > >>After upgrading to 7.1-RELEASE (and also STABLE) the NIC doesn't > >>seem to receive any frames. I can see the DHCP Requests on the DHCP > >>Server but the DHCPOFFERS are never seen by the client with the re0 > >>device. After setting promiscious mode on the interface (i.e. by > >>tcpdump -ni re0) the interface begins to work fine. > >> > >>I've attached a complete dmesg output, but i think the detection > >>works fine, here the short version: > >> > >>re0: <RealTek 8169SC/8110SC Single-chip Gigabit Ethernet> port > >>0x9c00-0x9cff mem 0xdfdff000-0xdfdff0ff irq 20 at device 7.0 on > >>pci4 re0: Chip rev. 0x18000000 > >>re0: MAC rev. 0x00000000 > >>miibus0: <MII bus> on re0 > >>rgephy0: <RTL8169S/8110S/8211B media interface> PHY 1 on miibus0 > >>rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, > >>1000baseT, 1000baseT-FDX, auto > >>re0: Ethernet address: 00:1a:92:35:29:fa > >>re0: [FILTER] > > > >Please revert SVN r180519 (or CVS r1.95.2.22) and try again: > > > >http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/re/if_re.c.diff?r1=1.95.2.21;r2=1.95.2.22 > > Thanks! This fixed my problem. I now have DHCP and a running network > interface again with a 7.1-STABLE and the reverted r180519 changes. > If you need to test another version for the changes in r180519 let me > know and i'll test them on this machine. > It seems that RTL8169SC does not like memory mapping. Instead of using io mapping for all revisions, how about attached patch? -- Regards, Pyun YongHyeon --cvVnyQ+4j833TQvp Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="re.8169sc.diff" Index: sys/dev/re/if_re.c =================================================================== --- sys/dev/re/if_re.c (revision 187352) +++ sys/dev/re/if_re.c (working copy) @@ -158,6 +158,8 @@ /* Tunables. */ static int msi_disable = 1; TUNABLE_INT("hw.re.msi_disable", &msi_disable); +static int prefer_iomap = 0; +TUNABLE_INT("hw.re.prefer_iomap", &prefer_iomap); #define RE_CSUM_FEATURES (CSUM_IP | CSUM_TCP | CSUM_UDP) @@ -1131,26 +1133,36 @@ pci_enable_busmaster(dev); devid = pci_get_device(dev); - /* Prefer memory space register mapping over IO space. */ - sc->rl_res_id = PCIR_BAR(1); - sc->rl_res_type = SYS_RES_MEMORY; - /* RTL8168/8101E seems to use different BARs. */ - if (devid == RT_DEVICEID_8168 || devid == RT_DEVICEID_8101E) - sc->rl_res_id = PCIR_BAR(2); + /* + * Prefer memory space register mapping over IO space. + * Because RTL8169SC does not seem to work when memory mapping + * is used always activate io mapping. + */ + if (devid == RT_DEVICEID_8169SC) + prefer_iomap = 1; + if (prefer_iomap == 0) { + sc->rl_res_id = PCIR_BAR(1); + sc->rl_res_type = SYS_RES_MEMORY; + /* RTL8168/8101E seems to use different BARs. */ + if (devid == RT_DEVICEID_8168 || devid == RT_DEVICEID_8101E) + sc->rl_res_id = PCIR_BAR(2); + } else { + sc->rl_res_id = PCIR_BAR(0); + sc->rl_res_type = SYS_RES_IOPORT; + } sc->rl_res = bus_alloc_resource_any(dev, sc->rl_res_type, &sc->rl_res_id, RF_ACTIVE); - - if (sc->rl_res == NULL) { + if (sc->rl_res == NULL && prefer_iomap == 0) { sc->rl_res_id = PCIR_BAR(0); sc->rl_res_type = SYS_RES_IOPORT; sc->rl_res = bus_alloc_resource_any(dev, sc->rl_res_type, &sc->rl_res_id, RF_ACTIVE); - if (sc->rl_res == NULL) { - device_printf(dev, "couldn't map ports/memory\n"); - error = ENXIO; - goto fail; - } } + if (sc->rl_res == NULL) { + device_printf(dev, "couldn't map ports/memory\n"); + error = ENXIO; + goto fail; + } sc->rl_btag = rman_get_bustag(sc->rl_res); sc->rl_bhandle = rman_get_bushandle(sc->rl_res); --cvVnyQ+4j833TQvp-- From owner-freebsd-stable@FreeBSD.ORG Sat Jan 17 04:54:36 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4C078106564A; Sat, 17 Jan 2009 04:54:36 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.233]) by mx1.freebsd.org (Postfix) with ESMTP id 07C348FC1D; Sat, 17 Jan 2009 04:54:35 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so1963460rvf.43 for <multiple recipients>; Fri, 16 Jan 2009 20:54:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=eWZXHE8sbo6PgSZqyJC29PT3KTjk3Ys+fsy4R9YIYdY=; b=j/X4ZUY2P8EwGC/bYic7wia45Jtb374TxJgPfXLDpwRuM2zHG9fdb5SKPER5mwtQJd Ey3v4dfFJOikzSXC/bu2VFv8Udv5fk7WZjMsQCMnWOrTv7na8O/p37hAWwujNkjHHeg/ 14XLTW392cGJh7JQcm7GDT1PgZ8m7bBdK958g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=bs5LFAusEauMKmxqQ3t4pZjKtzEH5EkjP+vEv6qTdVI11BxGOGkEw2SDPQtDQ86LOr P1H0n8kBS4M6lqvcDnc0Qy+B5OPiMgmUQcXgas5XBfsqnZXoAYuvETPAVrl3HHs3fG5f jEY1kVZxpFI/vyyXyaCK6ahWlJnFO1FQW7pWY= Received: by 10.141.175.5 with SMTP id c5mr1586075rvp.243.1232168075612; Fri, 16 Jan 2009 20:54:35 -0800 (PST) Received: from michelle.cdnetworks.co.kr ([211.53.35.84]) by mx.google.com with ESMTPS id f42sm1867178rvb.5.2009.01.16.20.54.32 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 16 Jan 2009 20:54:34 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.14.3/8.14.3) with ESMTP id n0H4sP8g068892 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 17 Jan 2009 13:54:25 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.14.3/8.14.3/Submit) id n0H4sNlw068891; Sat, 17 Jan 2009 13:54:23 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Sat, 17 Jan 2009 13:54:23 +0900 From: Pyun YongHyeon <pyunyh@gmail.com> To: Dimitry Andric <dimitry@andric.com> Message-ID: <20090117045423.GC68290@cdnetworks.co.kr> References: <8dfae1c10901070639x67945324jeeecfcac647d7976@mail.gmail.com> <20090113050223.GH46346@cdnetworks.co.kr> <496CB2E7.2060902@andric.com> <200901131806.02868.jkim@FreeBSD.org> <496F9823.4060503@andric.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="0vzXIDBeUiKkjNJl" Content-Disposition: inline In-Reply-To: <496F9823.4060503@andric.com> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@FreeBSD.org, Jung-uk Kim <jkim@FreeBSD.org>, eugene@donpac.ru Subject: Re: FreeBSD 7.1 Breaks re and rl Network Interface Drivers X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sat, 17 Jan 2009 04:54:36 -0000 --0vzXIDBeUiKkjNJl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Jan 15, 2009 at 09:10:11PM +0100, Dimitry Andric wrote: > On 2009-01-14 00:05, Jung-uk Kim wrote: > > Can you try one of the following patches? > > > > -CURRENT: http://people.freebsd.org/~jkim/re/re.current.diff > > -STABLE: http://people.freebsd.org/~jkim/re/re.stable.diff > > > > These patches contain all patches suggested by me and yongari and an > > additional patch, which may (or may not) decrease the initial setup > > time. > > I have applied the -STABLE patch, and while this doesn't have much > influence on the initial setup time, it does seem to solve the problem > of not being able to send any packets. I think the initial setup time issue of 8169SC is different one. Did re(4) of 7.0-RELEASE also have the same issue? Also would you try attached patch? It doesn't fix initial setup time issue but I'd like to know whether it makes your controller work. -- Regards, Pyun YongHyeon --0vzXIDBeUiKkjNJl Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="re.8169sc.diff" Index: sys/dev/re/if_re.c =================================================================== --- sys/dev/re/if_re.c (revision 187352) +++ sys/dev/re/if_re.c (working copy) @@ -158,6 +158,8 @@ /* Tunables. */ static int msi_disable = 1; TUNABLE_INT("hw.re.msi_disable", &msi_disable); +static int prefer_iomap = 0; +TUNABLE_INT("hw.re.prefer_iomap", &prefer_iomap); #define RE_CSUM_FEATURES (CSUM_IP | CSUM_TCP | CSUM_UDP) @@ -1131,26 +1133,36 @@ pci_enable_busmaster(dev); devid = pci_get_device(dev); - /* Prefer memory space register mapping over IO space. */ - sc->rl_res_id = PCIR_BAR(1); - sc->rl_res_type = SYS_RES_MEMORY; - /* RTL8168/8101E seems to use different BARs. */ - if (devid == RT_DEVICEID_8168 || devid == RT_DEVICEID_8101E) - sc->rl_res_id = PCIR_BAR(2); + /* + * Prefer memory space register mapping over IO space. + * Because RTL8169SC does not seem to work when memory mapping + * is used always activate io mapping. + */ + if (devid == RT_DEVICEID_8169SC) + prefer_iomap = 1; + if (prefer_iomap == 0) { + sc->rl_res_id = PCIR_BAR(1); + sc->rl_res_type = SYS_RES_MEMORY; + /* RTL8168/8101E seems to use different BARs. */ + if (devid == RT_DEVICEID_8168 || devid == RT_DEVICEID_8101E) + sc->rl_res_id = PCIR_BAR(2); + } else { + sc->rl_res_id = PCIR_BAR(0); + sc->rl_res_type = SYS_RES_IOPORT; + } sc->rl_res = bus_alloc_resource_any(dev, sc->rl_res_type, &sc->rl_res_id, RF_ACTIVE); - - if (sc->rl_res == NULL) { + if (sc->rl_res == NULL && prefer_iomap == 0) { sc->rl_res_id = PCIR_BAR(0); sc->rl_res_type = SYS_RES_IOPORT; sc->rl_res = bus_alloc_resource_any(dev, sc->rl_res_type, &sc->rl_res_id, RF_ACTIVE); - if (sc->rl_res == NULL) { - device_printf(dev, "couldn't map ports/memory\n"); - error = ENXIO; - goto fail; - } } + if (sc->rl_res == NULL) { + device_printf(dev, "couldn't map ports/memory\n"); + error = ENXIO; + goto fail; + } sc->rl_btag = rman_get_bustag(sc->rl_res); sc->rl_bhandle = rman_get_bushandle(sc->rl_res); --0vzXIDBeUiKkjNJl-- From owner-freebsd-stable@FreeBSD.ORG Sat Jan 17 09:53:09 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: FreeBSD-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 58FEC1065679 for <FreeBSD-stable@freebsd.org>; Sat, 17 Jan 2009 09:53:09 +0000 (UTC) (envelope-from rsmith@xs4all.nl) Received: from smtp-vbr7.xs4all.nl (smtp-vbr7.xs4all.nl [194.109.24.27]) by mx1.freebsd.org (Postfix) with ESMTP id C9E818FC19 for <FreeBSD-stable@freebsd.org>; Sat, 17 Jan 2009 09:53:08 +0000 (UTC) (envelope-from rsmith@xs4all.nl) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr7.xs4all.nl (8.13.8/8.13.8) with ESMTP id n0H9r7jQ065155; Sat, 17 Jan 2009 10:53:07 +0100 (CET) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id 365B1B853; Sat, 17 Jan 2009 10:53:07 +0100 (CET) Date: Sat, 17 Jan 2009 10:53:07 +0100 From: Roland Smith <rsmith@xs4all.nl> To: barbara <barbara.xxx1975@libero.it> Message-ID: <20090117095307.GA36855@slackbox.xs4all.nl> References: <KDL9C3$74E34BD73EE4E19F5127AF2F7D9840E5@libero.it> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="MGYHOYXEY6WxJCY8" Content-Disposition: inline In-Reply-To: <KDL9C3$74E34BD73EE4E19F5127AF2F7D9840E5@libero.it> X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 X-GPG-Key: http://www.xs4all.nl/~rsmith/pubkey.txt X-GPG-Notice: If this message is not signed, don't assume I sent it! User-Agent: Mutt/1.5.18 (2008-05-17) X-Virus-Scanned: by XS4ALL Virus Scanner Cc: FreeBSD-stable <FreeBSD-stable@freebsd.org> Subject: Re: g_vfs_done()...errors X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sat, 17 Jan 2009 09:53:09 -0000 --MGYHOYXEY6WxJCY8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jan 17, 2009 at 01:00:03AM +0100, barbara wrote: >=20 > Hello, > while reading/writing dvd on 6-STABLE (can't remember on 7-STABLE right n= ow), I'm getting the message buffer filled by errors. > This is my dvd-rw > $ sysctl dev.acd.0.%desc > dev.acd.0.%desc: PIONEER DVD-RW DVR-109/1.58 > attached to > $ sysctl dev.atapci.1.%desc > dev.atapci.1.%desc: VIA 8237A UDMA133 controller >=20 > And the followings are some examples of the error: >=20 > g_vfs_done():cd0[READ(offset=3D3533693165190270976, length=3D2048)]error = =3D 5 > g_vfs_done():cd0[READ(offset=3D8751655366962446336, length=3D2048)]error = =3D 5 > g_vfs_done():cd0[READ(offset=3D8751655370713257984, length=3D2048)]error = =3D 5 >=20 > g_vfs_done():acd0[READ(offset=3D3533693165190270976, length=3D2048)]error= =3D 5 > g_vfs_done():acd0[READ(offset=3D8751655366962446336, length=3D2048)]error= =3D 5 > g_vfs_done():acd0[READ(offset=3D8751655370713257984, length=3D2048)]error= =3D 5 >=20 > Is it possible such a value for offset (DVD-SL)? The offset is rediculously large. > Does anyone know the reason of the error? I had this problem once with a harddisk. It turned out that the (S)ATA data cable wasn't connected properly. It had probably come somewhat loose when I was putting in a PCI card. Pulling the cable from the drive and re-attaching it again solved the problem in that case. Roland --=20 R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) --MGYHOYXEY6WxJCY8 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAklxqn0ACgkQEnfvsMMhpyUrRgCfSz3bZIGeNpGF8+KftUetQVnP wOAAn1WScPr8Gogz4Vjn9TjIALqncitJ =ceid -----END PGP SIGNATURE----- --MGYHOYXEY6WxJCY8-- From owner-freebsd-stable@FreeBSD.ORG Sat Jan 17 12:20:24 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D9F3D106564A for <freebsd-stable@freebsd.org>; Sat, 17 Jan 2009 12:20:24 +0000 (UTC) (envelope-from patfbsd@davenulle.org) Received: from smtp.lamaiziere.net (net.lamaiziere.net [91.121.44.19]) by mx1.freebsd.org (Postfix) with ESMTP id 9EF4E8FC1C for <freebsd-stable@freebsd.org>; Sat, 17 Jan 2009 12:20:24 +0000 (UTC) (envelope-from patfbsd@davenulle.org) Received: from baby-jane.lamaiziere.net (67.158.192-77.rev.gaoland.net [77.192.158.67]) by smtp.lamaiziere.net (Postfix) with ESMTPA id 090016332D9; Sat, 17 Jan 2009 13:20:23 +0100 (CET) Received: from baby-jane (localhost [127.0.0.1]) by baby-jane.lamaiziere.net (Postfix) with ESMTP id 580DA6A4DF5; Sat, 17 Jan 2009 13:20:22 +0100 (CET) Date: Sat, 17 Jan 2009 13:20:20 +0100 From: Patrick =?ISO-8859-15?Q?Lamaizi=E8re?= <patfbsd@davenulle.org> To: freebsd-stable@freebsd.org, grarpamp <grarpamp@gmail.com> Message-ID: <20090117132020.370b841d@baby-jane> In-Reply-To: <d2e731a10901161144j50889051ka10c911214cb733a@mail.gmail.com> References: <d2e731a10901161144j50889051ka10c911214cb733a@mail.gmail.com> Organization: /dave/nulle X-Mailer: Claws Mail 3.3.1 (GTK+ 2.12.9; i386-apple-darwin9.3.0) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 8bit Cc: Subject: Re: USB devices fail to attach as umass scsi da[n] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sat, 17 Jan 2009 12:20:25 -0000 Le Fri, 16 Jan 2009 14:44:59 -0500, grarpamp <grarpamp@gmail.com> a écrit : > GENERIC, RELENG_7 a few days past the 7.1 release. > SuperMicro 370DER motherboard, most recent bios. > The Nikon is set to mass storage. The RCA has no such option. > Both have the latest firmware. > > By the way, the RCA records natively in mp3 format. Handy as most > seem to use some closed format. Worth a try if you need one. > > # camcontrol devl - should be: (pass2,da2) when attach is complete > scbus2 on umass-sim0 bus 0: > < RCA_TKCF2494_US 1.00> at scbus2 target 0 lun 0 > (da2,pass2) > > # dmesg - reordered a bit > umass0: <RCA RCA_TKCF2494_US USB DEVICE, class 0/0, rev 1.10/1.00, > addr 2> on uhub0 > umass0:2:0:-1: Attached to scbus2 > pass2 at umass-sim0 bus 0 target 0 lun 0 > pass2: < RCA_TKCF2494_US 1.00> Removable Direct Access SCSI-0 device > pass2: 1.000MB/s transfers > GEOM: da2 at umass-sim0 bus 0 target 0 lun 0 > new disk da2 > da2: < RCA_TKCF2494_US 1.00> Removable Direct Access SCSI-0 device > da2: 1.000MB/s transfers > da2: 122MB (251136 512 byte sectors: 64H 32S/T 122C) > > (da2:umass-sim0:0:0:0): Synchronize cache failed, status == 0x4, scsi > status == 0x0 You can try to add a quirk for this device : http://www.root.org/~nate/freebsd/scsi/quirks.html [not sure if this is uptodate, i did it in the past (RELENG_5/6) for my mp3 player] I would start with a DA_Q_NO_SYNC_CACHE quirk. From owner-freebsd-stable@FreeBSD.ORG Sat Jan 17 13:06:02 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2B495106564A for <freebsd-stable@freebsd.org>; Sat, 17 Jan 2009 13:06:02 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.9.129]) by mx1.freebsd.org (Postfix) with ESMTP id E2C418FC0C for <freebsd-stable@freebsd.org>; Sat, 17 Jan 2009 13:06:01 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id BA58473098; Sat, 17 Jan 2009 14:11:16 +0100 (CET) Date: Sat, 17 Jan 2009 14:11:16 +0100 From: Luigi Rizzo <rizzo@iet.unipi.it> To: Patrick Lamaizi?re <patfbsd@davenulle.org> Message-ID: <20090117131116.GA75751@onelab2.iet.unipi.it> References: <d2e731a10901161144j50889051ka10c911214cb733a@mail.gmail.com> <20090117132020.370b841d@baby-jane> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090117132020.370b841d@baby-jane> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org, grarpamp <grarpamp@gmail.com> Subject: Re: USB devices fail to attach as umass scsi da[n] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sat, 17 Jan 2009 13:06:02 -0000 On Sat, Jan 17, 2009 at 01:20:20PM +0100, Patrick Lamaizi?re wrote: > Le Fri, 16 Jan 2009 14:44:59 -0500, > grarpamp <grarpamp@gmail.com> a ?crit : > > > GENERIC, RELENG_7 a few days past the 7.1 release. > > SuperMicro 370DER motherboard, most recent bios. > > The Nikon is set to mass storage. The RCA has no such option. > > Both have the latest firmware. > > > > By the way, the RCA records natively in mp3 format. Handy as most > > seem to use some closed format. Worth a try if you need one. > > > > # camcontrol devl - should be: (pass2,da2) when attach is complete > > scbus2 on umass-sim0 bus 0: > > < RCA_TKCF2494_US 1.00> at scbus2 target 0 lun 0 > > (da2,pass2) > > > > # dmesg - reordered a bit > > umass0: <RCA RCA_TKCF2494_US USB DEVICE, class 0/0, rev 1.10/1.00, > > addr 2> on uhub0 > > umass0:2:0:-1: Attached to scbus2 > > pass2 at umass-sim0 bus 0 target 0 lun 0 > > pass2: < RCA_TKCF2494_US 1.00> Removable Direct Access SCSI-0 device > > pass2: 1.000MB/s transfers > > GEOM: da2 at umass-sim0 bus 0 target 0 lun 0 > > new disk da2 > > da2: < RCA_TKCF2494_US 1.00> Removable Direct Access SCSI-0 device > > da2: 1.000MB/s transfers > > da2: 122MB (251136 512 byte sectors: 64H 32S/T 122C) > > > > (da2:umass-sim0:0:0:0): Synchronize cache failed, status == 0x4, scsi > > status == 0x0 > > You can try to add a quirk for this device : > http://www.root.org/~nate/freebsd/scsi/quirks.html > > [not sure if this is uptodate, i did it in the past (RELENG_5/6) for > my mp3 player] > > I would start with a DA_Q_NO_SYNC_CACHE quirk. also, to apply quirks without rebuilding a kernel you can use the recent 'kldpatch' port -- the man page contains an example for umass.ko that should cover your case (by changing the numbers of course) cheers luigi From owner-freebsd-stable@FreeBSD.ORG Sat Jan 17 13:12:55 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> 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 5D844106564A; Sat, 17 Jan 2009 13:12:55 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.cksoft.de (mail.cksoft.de [62.111.66.27]) by mx1.freebsd.org (Postfix) with ESMTP id 12C468FC14; Sat, 17 Jan 2009 13:12:54 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from localhost (amavis.str.cksoft.de [192.168.74.71]) by mail.cksoft.de (Postfix) with ESMTP id 4F9C741C650; Sat, 17 Jan 2009 13:55:06 +0100 (CET) X-Virus-Scanned: amavisd-new at cksoft.de Received: from mail.cksoft.de ([62.111.66.27]) by localhost (amavis.str.cksoft.de [192.168.74.71]) (amavisd-new, port 10024) with ESMTP id YZaEfIrl7nAu; Sat, 17 Jan 2009 13:55:05 +0100 (CET) Received: by mail.cksoft.de (Postfix, from userid 66) id ADE7041C64C; Sat, 17 Jan 2009 13:55:05 +0100 (CET) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id 237594448D5; Sat, 17 Jan 2009 12:50:51 +0000 (UTC) Date: Sat, 17 Jan 2009 12:50:50 +0000 (UTC) From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> X-X-Sender: bz@maildrop.int.zabbadoz.net To: Hiroki Sato <hrs@FreeBSD.org> In-Reply-To: <20090112.042014.205677175.hrs@allbsd.org> Message-ID: <20090117124940.D45399@maildrop.int.zabbadoz.net> References: <20090112.042014.205677175.hrs@allbsd.org> X-OpenPGP-Key: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: stable@FreeBSD.org Subject: Re: IPv6 routing on 7.1R X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sat, 17 Jan 2009 13:12:55 -0000 On Mon, 12 Jan 2009, Hiroki Sato wrote: Hi, > I noticed an odd behavior regarding IPv6 after upgrading my 7.0R box > to 7.1R. The situation and symptom are the following: > > 1. The box has two NICs. One has an address 2001:0db8:1::1/64 (NIC > A), and another has 2001:0db8:2::1/64 (NIC B). These addresses > are assigned manually ($ipv6_ifconfig in rc.conf). > > 2. RA is periodically sent to the network 2001:0db8:1::1/64 (NIC A) > by a router on the subnet. The RA includes a source link-layer > address option only. > > When setting net.inet6.ip6.accept_rtadv=1 in this configuration, I > expected the box assigns an autoconf IPv6 address (prefix > 2001:0db8:1::/64 + EUI64) to NIC A and an default route based on > source link-layer address in the RA packet. Actually, these two were > done as expected. However, after addresses are assigned, routes for > NIC B disappeared from the routing table. More specifically, a > cloning route "2001:0db8:2::1/64 -> link#2" was removed for some > reason. > > Is this an expected behavior? I don't think so. Can you file a PR and get it assigned to bz@ and I'll look in two weeks or so once I am fully back. /bz -- Bjoern A. Zeeb The greatest risk is not taking one. From owner-freebsd-stable@FreeBSD.ORG Sat Jan 17 13:21:53 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> 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 4A422106566B for <stable@freebsd.org>; Sat, 17 Jan 2009 13:21:53 +0000 (UTC) (envelope-from tonymaher@optusnet.com.au) Received: from fallbackmx10.syd.optusnet.com.au (fallbackmx10.syd.optusnet.com.au [211.29.132.251]) by mx1.freebsd.org (Postfix) with ESMTP id DE8A78FC08 for <stable@freebsd.org>; Sat, 17 Jan 2009 13:21:52 +0000 (UTC) (envelope-from tonymaher@optusnet.com.au) Received: from mail01.syd.optusnet.com.au (mail01.syd.optusnet.com.au [211.29.132.182]) by fallbackmx10.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id n0HANCZ1026669 for <stable@freebsd.org>; Sat, 17 Jan 2009 21:23:12 +1100 Received: from karma.home (c58-107-102-243.thorn1.nsw.optusnet.com.au [58.107.102.243]) (authenticated sender tonymaher) by mail01.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id n0HAN9bP012294 for <stable@freebsd.org>; Sat, 17 Jan 2009 21:23:10 +1100 Message-ID: <4971B18D.3090803@optusnet.com.au> Date: Sat, 17 Jan 2009 21:23:09 +1100 From: Tony Maher <tonymaher@optusnet.com.au> User-Agent: Thunderbird 2.0.0.19 (X11/20090113) MIME-Version: 1.0 To: stable@freebsd.org X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: 7.1 Release and usb keyboard/mouse problems X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sat, 17 Jan 2009 13:21:53 -0000 Hello, I have been running FreeBSD 7 from around 2008-10-20 and experienced the occasional problems with usb mouse and keyboard. The mouse pointer slowly drift to a corner of the screen and not respond, and the keyboard would become unresponsive. Unplugging and plugging back in fixed the problem. This would happen a few times per week. However after I upgraded to 7.1-RELEASE-p2, I now get this problem every few hours if idle (hard to know exactly when it occurs since i am not at keyboard) and a few minutes if doing a background compilation. The keyboard often shows one of the LEDs constantly flashing at high speed. Unplugging and replugging often does not work and needs to be done several times (and use a different usb port). I saw some email reports and tried in /boot/device.hints hint.atkbd.0.disable="1" hint.atkbdc.0.disable="1" No change. Tried a different mouse and it would continue to work but my normal mouse would disconnect. Tried an identical keyboard and it exhibited the same problem ruling out a bad keyboard. I then tried another keyboard and have not had any problem since. The main thing I can see different is the working keyboard is a Logitech and the two problematic keyboards are (very) cheap noname keyboards. Both the mice are Logitech but the mouse that has problems is very old (from around year 2000 - model M-BA47). The working mouse is newer but still fairly old (Model M-UV96). The box is a amd64 with Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GH 4GB RAM and motherboard is Intel DP35DP. So my setup now appears to be fine. If anyone is having similar problems, I suggest trying different (more modern) mice/keyboards. cheers -- Tony Maher email: tonymaher@optusnet.com.au From owner-freebsd-stable@FreeBSD.ORG Sat Jan 17 14:10:31 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DE8951065676 for <freebsd-stable@freebsd.org>; Sat, 17 Jan 2009 14:10:31 +0000 (UTC) (envelope-from sascha=freebsd-stable=freebsd.org=cdpwplml@holzleiter.name) Received: from serverbitch.de (unknown [IPv6:2001:8d8:80:11::351]) by mx1.freebsd.org (Postfix) with ESMTP id A06998FC0A for <freebsd-stable@freebsd.org>; Sat, 17 Jan 2009 14:10:31 +0000 (UTC) (envelope-from sascha=freebsd-stable=freebsd.org=cdpwplml@holzleiter.name) Received: from p54a3e08c.dip.t-dialin.net ([84.163.224.140] helo=[127.0.0.1]) by serverbitch.de with esmtpa (Exim) (envelope-from <sascha@holzleiter.name>) id 1LOBsa-000L6Q-Cr; Sat, 17 Jan 2009 15:10:28 +0100 Message-ID: <4971E6D3.50804@holzleiter.name> Date: Sat, 17 Jan 2009 15:10:27 +0100 From: Sascha Holzleiter <sascha@holzleiter.name> User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: pyunyh@gmail.com References: <8dfae1c10901070639x67945324jeeecfcac647d7976@mail.gmail.com> <496B7C17.8010107@holzleiter.name> <200901122010.37269.jkim@FreeBSD.org> <496CAB07.5020404@holzleiter.name> <20090117044758.GB68290@cdnetworks.co.kr> In-Reply-To: <20090117044758.GB68290@cdnetworks.co.kr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Jung-uk Kim <jkim@freebsd.org> Subject: Re: FreeBSD 7.1 Breaks re and rl Network Interface Drivers X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sat, 17 Jan 2009 14:10:32 -0000 Pyun YongHyeon wrote: > On Tue, Jan 13, 2009 at 03:53:59PM +0100, Sascha Holzleiter wrote: > > Jung-uk Kim wrote: > > >On Monday 12 January 2009 12:21 pm, Sascha Holzleiter wrote: > > >>Hi, > > >> > > >>i see similar problems with a re card: > > >> > > >>re0@pci0:4:7:0: class=0x020000 card=0x816710ec chip=0x816710ec > > >>rev=0x10 hdr=0x00 > > >> vendor = 'Realtek Semiconductor' > > >> device = 'RTL8169/8110 Family Gigabit Ethernet NIC' > > >> class = network > > >> subclass = ethernet > > >> > > >>After upgrading to 7.1-RELEASE (and also STABLE) the NIC doesn't > > >>seem to receive any frames. I can see the DHCP Requests on the DHCP > > >>Server but the DHCPOFFERS are never seen by the client with the re0 > > >>device. After setting promiscious mode on the interface (i.e. by > > >>tcpdump -ni re0) the interface begins to work fine. > > >> > > >>I've attached a complete dmesg output, but i think the detection > > >>works fine, here the short version: > > >> > > >>re0: <RealTek 8169SC/8110SC Single-chip Gigabit Ethernet> port > > >>0x9c00-0x9cff mem 0xdfdff000-0xdfdff0ff irq 20 at device 7.0 on > > >>pci4 re0: Chip rev. 0x18000000 > > >>re0: MAC rev. 0x00000000 > > >>miibus0: <MII bus> on re0 > > >>rgephy0: <RTL8169S/8110S/8211B media interface> PHY 1 on miibus0 > > >>rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, > > >>1000baseT, 1000baseT-FDX, auto > > >>re0: Ethernet address: 00:1a:92:35:29:fa > > >>re0: [FILTER] > > > > > >Please revert SVN r180519 (or CVS r1.95.2.22) and try again: > > > > > >http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/re/if_re.c.diff?r1=1.95.2.21;r2=1.95.2.22 > > > > Thanks! This fixed my problem. I now have DHCP and a running network > > interface again with a 7.1-STABLE and the reverted r180519 changes. > > If you need to test another version for the changes in r180519 let me > > know and i'll test them on this machine. > > > > It seems that RTL8169SC does not like memory mapping. Instead of > using io mapping for all revisions, how about attached patch? > > I'll test the patch on monday when i'm at the office as this machine is my workstation there. From owner-freebsd-stable@FreeBSD.ORG Sat Jan 17 17:04:40 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2B8CA106566B; Sat, 17 Jan 2009 17:04:40 +0000 (UTC) (envelope-from dimitry@andric.com) Received: from tensor.andric.com (cl-327.ede-01.nl.sixxs.net [IPv6:2001:7b8:2ff:146::2]) by mx1.freebsd.org (Postfix) with ESMTP id DE4F88FC08; Sat, 17 Jan 2009 17:04:39 +0000 (UTC) (envelope-from dimitry@andric.com) Received: from [IPv6:2001:7b8:3a7:0:1883:bc29:2312:23a6] (unknown [IPv6:2001:7b8:3a7:0:1883:bc29:2312:23a6]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id DF6AE11F859; Sat, 17 Jan 2009 18:04:38 +0100 (CET) Message-ID: <49720FA5.6060508@andric.com> Date: Sat, 17 Jan 2009 18:04:37 +0100 From: Dimitry Andric <dimitry@andric.com> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.1b3pre) Gecko/20090116 Shredder/3.0b2pre MIME-Version: 1.0 To: pyunyh@gmail.com References: <8dfae1c10901070639x67945324jeeecfcac647d7976@mail.gmail.com> <20090113050223.GH46346@cdnetworks.co.kr> <496CB2E7.2060902@andric.com> <200901131806.02868.jkim@FreeBSD.org> <496F9823.4060503@andric.com> <20090117045423.GC68290@cdnetworks.co.kr> In-Reply-To: <20090117045423.GC68290@cdnetworks.co.kr> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@FreeBSD.org, Jung-uk Kim <jkim@FreeBSD.org>, eugene@donpac.ru Subject: Re: FreeBSD 7.1 Breaks re and rl Network Interface Drivers X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sat, 17 Jan 2009 17:04:40 -0000 On 2009-01-17 05:54, Pyun YongHyeon wrote: > I think the initial setup time issue of 8169SC is different one. > Did re(4) of 7.0-RELEASE also have the same issue? Sometimes, and sometimes not. :) It was flaky, to say the least... > Also would you try attached patch? It doesn't fix initial setup > time issue but I'd like to know whether it makes your controller > work. This patch not only makes my controller(s) work, it also speeds up the initial setup time greatly! I have tested this through about 3 reboots, and one complete powerdown + powerup cycle. From owner-freebsd-stable@FreeBSD.ORG Sat Jan 17 19:37:55 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 55C881065672 for <freebsd-stable@freebsd.org>; Sat, 17 Jan 2009 19:37:55 +0000 (UTC) (envelope-from mikael@t-online.hu) Received: from thor.iszerviz.hu (thor.iszerviz.hu [62.77.131.9]) by mx1.freebsd.org (Postfix) with ESMTP id 1667C8FC14 for <freebsd-stable@freebsd.org>; Sat, 17 Jan 2009 19:37:54 +0000 (UTC) (envelope-from mikael@t-online.hu) Received: from [192.168.1.107] (87.97.85.99.pool.invitel.hu [87.97.85.99]) by thor.iszerviz.hu (Postfix) with ESMTP id ED03C5008F for <freebsd-stable@freebsd.org>; Sat, 17 Jan 2009 20:20:09 +0100 (CET) Message-ID: <49722F64.4040301@t-online.hu> Date: Sat, 17 Jan 2009 20:20:04 +0100 From: Mikael Bak <mikael@t-online.hu> User-Agent: Thunderbird 2.0.0.19 (X11/20090105) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: mydns-mysql starts before mysql has finished starting X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sat, 17 Jan 2009 19:37:56 -0000 Hi list, This is my first post to this list. I'm not exactly new to freebsd but I have used GNU/Linux more. Last week I installed my first FreeBSD 7.1 machine. A base system with only mc, mysql and mydns-mysql packages. I installed all from pre compiled packages, not from ports. When I reboot the machine the mysql server is not finished starting before mydns tries to start, so it fails leaving me with a not working DNS server. I have to manually start mydns-mysql. As a very ugly fix I have edited the startup script for mydns-mysql and added a 10 sec delay. I wonder what else I can do. Should I perhaps contact the port maintainer? How do I reach him/her? TIA, Mikael Bak Budapest, Hungary From owner-freebsd-stable@FreeBSD.ORG Sat Jan 17 20:11:15 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D85791065686 for <freebsd-stable@freebsd.org>; Sat, 17 Jan 2009 20:11:15 +0000 (UTC) (envelope-from simond@irrelevant.org) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id B03DA8FC13 for <freebsd-stable@freebsd.org>; Sat, 17 Jan 2009 20:11:15 +0000 (UTC) (envelope-from simond@irrelevant.org) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 12481212917; Sat, 17 Jan 2009 14:52:07 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Sat, 17 Jan 2009 14:52:07 -0500 X-Sasl-enc: Lflko4RW4t/u3IA32UUnz1DFYQcY83Fiz5aK2DEq/8zG 1232221926 Received: from Inbox (home.irrelevant.org [87.194.2.108]) by mail.messagingengine.com (Postfix) with ESMTPSA id A9CB527B5E; Sat, 17 Jan 2009 14:52:05 -0500 (EST) MIME-Version: 1.0 content-class: From: Simon Dick <simond@irrelevant.org> Date: Sat, 17 Jan 2009 19:52:01 +0000 Importance: normal X-Priority: 3 To: Mikael Bak <mikael@t-online.hu> Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" Message-Id: <20090117195205.A9CB527B5E@heartbeat2.messagingengine.com> Cc: freebsd-stable@freebsd.org Subject: RE: mydns-mysql starts before mysql has finished starting X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sat, 17 Jan 2009 20:11:16 -0000 I'll see if I'm still maintainer and see if there's a better way of doing t= hings.=20 -----Original Message----- From: Mikael Bak <mikael@t-online.hu> Sent: 17 January 2009 19:20 To: freebsd-stable@freebsd.org Subject: mydns-mysql starts before mysql has finished starting Hi list, This is my first post to this list. I'm not exactly new to freebsd but I have used GNU/Linux more. Last week I installed my first FreeBSD 7.1 machine. A base system with only mc, mysql and mydns-mysql packages. I installed all from pre compiled packages, not from ports. When I reboot the machine the mysql server is not finished starting before mydns tries to start, so it fails leaving me with a not working DNS server. I have to manually start mydns-mysql. As a very ugly fix I have edited the startup script for mydns-mysql and added a 10 sec delay. I wonder what else I can do. Should I perhaps contact the port maintainer? How do I reach him/her? TIA, Mikael Bak Budapest, Hungary _______________________________________________ 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 Sat Jan 17 20:22:28 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D98811065673 for <freebsd-stable@freebsd.org>; Sat, 17 Jan 2009 20:22:28 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id CA10D8FC1C for <freebsd-stable@freebsd.org>; Sat, 17 Jan 2009 20:22:28 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id 7541F1A3C39; Sat, 17 Jan 2009 12:03:14 -0800 (PST) Date: Sat, 17 Jan 2009 12:03:14 -0800 From: Alfred Perlstein <alfred@freebsd.org> To: Mikael Bak <mikael@t-online.hu> Message-ID: <20090117200314.GR60686@elvis.mu.org> References: <49722F64.4040301@t-online.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49722F64.4040301@t-online.hu> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org Subject: Re: mydns-mysql starts before mysql has finished starting X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sat, 17 Jan 2009 20:22:29 -0000 Hey Mikael, Thank you for your feedback. To find out a port's maintainer, you can look into the makefile under CVS: http://www.freebsd.org/cgi/cvsweb.cgi/ports/dns/mydns/Makefile It looks to be: MAINTAINER= ale@FreeBSD.org If you don't a get a response from this developer, then try the generic "ports@freebsd.org" address. As far as fixing the problem, I think a trick might be to do something like this: while /etc/rc.d/mysql status = up && mydns == exit failure ... You might want to fork off the process to do this so if mysql hangs then your startup script doesn't hang the boot sequence waiting for it.. -Alfred * Mikael Bak <mikael@t-online.hu> [090117 11:38] wrote: > Hi list, > > This is my first post to this list. > I'm not exactly new to freebsd but I have used GNU/Linux more. > > Last week I installed my first FreeBSD 7.1 machine. A base system with > only mc, mysql and mydns-mysql packages. I installed all from pre > compiled packages, not from ports. > > When I reboot the machine the mysql server is not finished starting > before mydns tries to start, so it fails leaving me with a not working > DNS server. I have to manually start mydns-mysql. > > As a very ugly fix I have edited the startup script for mydns-mysql and > added a 10 sec delay. > > I wonder what else I can do. Should I perhaps contact the port > maintainer? How do I reach him/her? > > TIA, > Mikael Bak > Budapest, Hungary > _______________________________________________ > 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" -- - Alfred Perlstein From owner-freebsd-stable@FreeBSD.ORG Sat Jan 17 20:29:49 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3098410656DA for <freebsd-stable@freebsd.org>; Sat, 17 Jan 2009 20:29:49 +0000 (UTC) (envelope-from thompsa@FreeBSD.org) Received: from pele.citylink.co.nz (pele.citylink.co.nz [202.8.44.226]) by mx1.freebsd.org (Postfix) with ESMTP id 5D1358FC17 for <freebsd-stable@freebsd.org>; Sat, 17 Jan 2009 20:29:48 +0000 (UTC) (envelope-from thompsa@FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by pele.citylink.co.nz (Postfix) with ESMTP id 27738FEF4; Sun, 18 Jan 2009 08:59:37 +1300 (NZDT) X-Virus-Scanned: Debian amavisd-new at citylink.co.nz Received: from pele.citylink.co.nz ([127.0.0.1]) by localhost (pele.citylink.co.nz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id foc8aIT06Zh0; Sun, 18 Jan 2009 08:59:30 +1300 (NZDT) Received: from citylink.fud.org.nz (unknown [202.8.44.45]) by pele.citylink.co.nz (Postfix) with ESMTP; Sun, 18 Jan 2009 08:59:30 +1300 (NZDT) Received: by citylink.fud.org.nz (Postfix, from userid 1001) id 6C87711428; Sun, 18 Jan 2009 08:59:29 +1300 (NZDT) Date: Sat, 17 Jan 2009 11:59:29 -0800 From: Andrew Thompson <thompsa@FreeBSD.org> To: Mikael Bak <mikael@t-online.hu> Message-ID: <20090117195929.GA27494@citylink.fud.org.nz> References: <49722F64.4040301@t-online.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49722F64.4040301@t-online.hu> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-stable@freebsd.org Subject: Re: mydns-mysql starts before mysql has finished starting X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sat, 17 Jan 2009 20:29:50 -0000 On Sat, Jan 17, 2009 at 08:20:04PM +0100, Mikael Bak wrote: > Hi list, > > This is my first post to this list. > I'm not exactly new to freebsd but I have used GNU/Linux more. > > Last week I installed my first FreeBSD 7.1 machine. A base system with > only mc, mysql and mydns-mysql packages. I installed all from pre > compiled packages, not from ports. > > When I reboot the machine the mysql server is not finished starting > before mydns tries to start, so it fails leaving me with a not working > DNS server. I have to manually start mydns-mysql. > > As a very ugly fix I have edited the startup script for mydns-mysql and > added a 10 sec delay. > > I wonder what else I can do. Should I perhaps contact the port > maintainer? How do I reach him/her? http://www.freshports.org/dns/mydns/ (see Maintained by:) Andrew From owner-freebsd-stable@FreeBSD.ORG Sat Jan 17 21:33:10 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 37FA81065693; Sat, 17 Jan 2009 21:33:10 +0000 (UTC) (envelope-from mikael@t-online.hu) Received: from thor.iszerviz.hu (thor.iszerviz.hu [62.77.131.9]) by mx1.freebsd.org (Postfix) with ESMTP id BE3AE8FC24; Sat, 17 Jan 2009 21:33:09 +0000 (UTC) (envelope-from mikael@t-online.hu) Received: from [192.168.100.114] (catv5403E2DB.pool.t-online.hu [84.3.226.219]) by thor.iszerviz.hu (Postfix) with ESMTP id 02B0F50082; Sat, 17 Jan 2009 22:33:08 +0100 (CET) Message-ID: <49724E94.4000406@t-online.hu> Date: Sat, 17 Jan 2009 22:33:08 +0100 From: Mikael Bak <mikael@t-online.hu> User-Agent: Thunderbird 2.0.0.19 (X11/20090105) MIME-Version: 1.0 To: Alfred Perlstein <alfred@freebsd.org> References: <49722F64.4040301@t-online.hu> <20090117200314.GR60686@elvis.mu.org> In-Reply-To: <20090117200314.GR60686@elvis.mu.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: mydns-mysql starts before mysql has finished starting X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sat, 17 Jan 2009 21:33:10 -0000 Alfred Perlstein wrote: > > It looks to be: > MAINTAINER= ale@FreeBSD.org > Alfred, Simon, Andrew, Thanks for the fast responses. I have contacted the maintainer on the above address. Thanks, Mikael From owner-freebsd-stable@FreeBSD.ORG Sat Jan 17 23:00:35 2009 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 43A6A1065670 for <freebsd-stable@freebsd.org>; Sat, 17 Jan 2009 23:00:35 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [91.103.162.4]) by mx1.freebsd.org (Postfix) with ESMTP id 030408FC16 for <freebsd-stable@freebsd.org>; Sat, 17 Jan 2009 23:00:34 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from localhost (localhost.codelab.cz [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 6EF8019E019; Sun, 18 Jan 2009 00:00:33 +0100 (CET) Received: from [192.168.1.2] (r5bb235.net.upc.cz [86.49.61.235]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 72A6E19E057; Sun, 18 Jan 2009 00:00:30 +0100 (CET) Message-ID: <49726344.70709@quip.cz> Date: Sun, 18 Jan 2009 00:01:24 +0100 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: cz, cs, en, en-us MIME-Version: 1.0 To: =?UTF-8?B?VsOhY2xhdiBIYWlzbWFu?= <v.haisman@sh.cvut.cz> References: <496E282A.5070004@sh.cvut.cz> In-Reply-To: <496E282A.5070004@sh.cvut.cz> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-stable@freebsd.org Subject: Re: Mounting / using /dev/ufs/name X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sat, 17 Jan 2009 23:00:35 -0000 Václav Haisman wrote: > Hi, > I tried to mount root slice using the device nodes provided in /dev/ufs > directory. It works fine for other slices but not for the root slice. If I > try it I get prompt asking for root slice at boot time. It this not possible > at all or am I doing something wrong? It works for me without any issues on FreeBSD 7.1-BETA2 amd64 (booting from USB flash disk): # cat /etc/fstab /dev/ufs/2gLive / ufs ro 1 1 I am using GENERIC without tuning in loader.conf Miroslav Lachman