From owner-freebsd-stable@FreeBSD.ORG Sun Jan 18 00:39: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 0E5BF1065676 for ; Sun, 18 Jan 2009 00:39:55 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [199.26.172.34]) by mx1.freebsd.org (Postfix) with ESMTP id C63058FC17 for ; Sun, 18 Jan 2009 00:39:54 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id n0I0Pk7E092795 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 17 Jan 2009 16:25:46 -0800 (PST) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id n0I0PkHa092794; Sat, 17 Jan 2009 16:25:46 -0800 (PST) Received: from fbsd61 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA17264; Sat, 17 Jan 09 16:12:14 PST Date: Sat, 17 Jan 2009 16:14:08 -0800 From: perryh@pluto.rain.com To: rizzo@iet.unipi.it Message-Id: <49727450.f77ZCPa++6+6qYVh%perryh@pluto.rain.com> References: <20090117132020.370b841d@baby-jane> <20090117131116.GA75751@onelab2.iet.unipi.it> In-Reply-To: <20090117131116.GA75751@onelab2.iet.unipi.it> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Jan 2009 00:39:55 -0000 > to apply quirks without rebuilding a kernel you can use the recent > 'kldpatch' port ... "recent" as in "added within the last couple of weeks"? I don't see it in an INDEX from Jan. 4. Sounds useful. From owner-freebsd-stable@FreeBSD.ORG Sun Jan 18 00:47:11 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 497901065674 for ; Sun, 18 Jan 2009 00:47:11 +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 0C9668FC12 for ; Sun, 18 Jan 2009 00:47:11 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id E83DF73098; Sun, 18 Jan 2009 01:52:26 +0100 (CET) Date: Sun, 18 Jan 2009 01:52:26 +0100 From: Luigi Rizzo To: perryh@pluto.rain.com Message-ID: <20090118005226.GA94685@onelab2.iet.unipi.it> References: <20090117132020.370b841d@baby-jane> <20090117131116.GA75751@onelab2.iet.unipi.it> <49727450.f77ZCPa++6+6qYVh%perryh@pluto.rain.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49727450.f77ZCPa++6+6qYVh%perryh@pluto.rain.com> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Jan 2009 00:47:11 -0000 On Sat, Jan 17, 2009 at 04:14:08PM -0800, perryh@pluto.rain.com wrote: > > to apply quirks without rebuilding a kernel you can use the recent > > 'kldpatch' port ... > > "recent" as in "added within the last couple of weeks"? > I don't see it in an INDEX from Jan. 4. Sounds useful. yes, jan 13 and updated today From owner-freebsd-stable@FreeBSD.ORG Sun Jan 18 03:54:47 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 5CA3E106566B for ; Sun, 18 Jan 2009 03:54:47 +0000 (UTC) (envelope-from lankfordandrew@charter.net) Received: from que31.charter.net (que31.charter.net [209.225.8.23]) by mx1.freebsd.org (Postfix) with ESMTP id EA5548FC1F for ; Sun, 18 Jan 2009 03:54:46 +0000 (UTC) (envelope-from lankfordandrew@charter.net) Received: from aarprv06.charter.net ([10.20.200.76]) by mta21.charter.net (InterMail vM.7.09.01.00 201-2219-108-20080618) with ESMTP id <20090118030952.KTSF7559.mta21.charter.net@aarprv06.charter.net> for ; Sat, 17 Jan 2009 22:09:52 -0500 Received: from [192.168.1.151] (really [68.191.116.244]) by aarprv06.charter.net with ESMTP id <20090118030952.QBEZ128.aarprv06.charter.net@[192.168.1.151]> for ; Sat, 17 Jan 2009 22:09:52 -0500 Message-ID: <49729D80.8010506@charter.net> Date: Sat, 17 Jan 2009 22:09:52 -0500 From: Andrew Lankford 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-Chzlrs: 0 Cc: Subject: System borked: loader stack overflow. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Jan 2009 03:54:47 -0000 After rebuilding world from 7-stable after cvsup, I can no longer boot. The loader tries to load the kernel but instead locks up with a stack overflow. Wish I could send more details, but I'll have to find another way to boot up my system first. Andrew Lankford From owner-freebsd-stable@FreeBSD.ORG Sun Jan 18 09:28:30 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 2F5F7106567C for ; Sun, 18 Jan 2009 09:28:30 +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 E9A648FC13 for ; Sun, 18 Jan 2009 09:28:29 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 2A65773098; Sun, 18 Jan 2009 10:33:46 +0100 (CET) Date: Sun, 18 Jan 2009 10:33:46 +0100 From: Luigi Rizzo To: Andrew Lankford Message-ID: <20090118093346.GA9819@onelab2.iet.unipi.it> References: <49729D80.8010506@charter.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49729D80.8010506@charter.net> User-Agent: Mutt/1.4.2.3i Cc: stable@freebsd.org Subject: Re: System borked: loader stack overflow. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Jan 2009 09:28:30 -0000 On Sat, Jan 17, 2009 at 10:09:52PM -0500, Andrew Lankford wrote: > After rebuilding world from 7-stable after cvsup, I can no longer boot. > The loader tries to load the kernel but instead locks up with a stack > overflow. Wish I could send more details, but I'll have to find another > way to boot up my system first. just to identify the problem - what was the version of your previous loader, and what kind of CPU do you have (Intel or AMD, single or multi core) etc. (to boot again you can replace /boot/loader with one taken from an older 6.3 or 7.0 CD) cheers luigi From owner-freebsd-stable@FreeBSD.ORG Sun Jan 18 10:06:21 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 4B7271065674 for ; Sun, 18 Jan 2009 10:06:21 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from fallbackmx06.syd.optusnet.com.au (fallbackmx06.syd.optusnet.com.au [211.29.132.8]) by mx1.freebsd.org (Postfix) with ESMTP id D22B98FC1E for ; Sun, 18 Jan 2009 10:06:20 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail13.syd.optusnet.com.au (mail13.syd.optusnet.com.au [211.29.132.194]) by fallbackmx06.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id n0I7CuJm004953 for ; Sun, 18 Jan 2009 18:12:56 +1100 Received: from server.vk2pj.dyndns.org (c122-106-215-175.belrs3.nsw.optusnet.com.au [122.106.215.175]) by mail13.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id n0I7CoIu007143 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 18 Jan 2009 18:12:51 +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 n0I7CofR000969; Sun, 18 Jan 2009 18:12:50 +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 n0I7Cn1E000968; Sun, 18 Jan 2009 18:12:49 +1100 (EST) (envelope-from peter) Date: Sun, 18 Jan 2009 18:12:49 +1100 From: Peter Jeremy To: Andrew Lankford Message-ID: <20090118071249.GK16116@server.vk2pj.dyndns.org> References: <49729D80.8010506@charter.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="UBnjLfzoMQYIXCvq" Content-Disposition: inline In-Reply-To: <49729D80.8010506@charter.net> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.18 (2008-05-17) Cc: stable@freebsd.org Subject: Re: System borked: loader stack overflow. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Jan 2009 10:06:21 -0000 --UBnjLfzoMQYIXCvq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2009-Jan-17 22:09:52 -0500, Andrew Lankford = wrote: >After rebuilding world from 7-stable after cvsup, I can no longer boot. = =20 >The loader tries to load the kernel but instead locks up with a stack=20 >overflow. Wish I could send more details, but I'll have to find another= =20 >way to boot up my system first. If you press any key during the first spinner, you should get a prompt similar to the following: >> FreeBSD/i386 BOOT Default: 0:ad(0,a)/boot/loader boot: You can then enter the name of the program you wish to run - eg /boot/loader.old (or directly load /boot/kernel/kernel) See the following for a more complete description: http://www.freebsd.org/cgi/man.cgi?query=3Dboot&apropos=3D0&sektion=3D0&man= path=3DFreeBSD+7.1-RELEASE&format=3Dhtml Alternatively, you could boot off a "live filesystem" CD. --=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. --UBnjLfzoMQYIXCvq Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAkly1mwACgkQ/opHv/APuIcD9QCgsWFSMOdyMitgTpu7R9syiSE+ N9wAn1b9wKtE+4u7GORO5IgBIusId0W7 =ma7y -----END PGP SIGNATURE----- --UBnjLfzoMQYIXCvq-- From owner-freebsd-stable@FreeBSD.ORG Sun Jan 18 10:08:06 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 E7C60106568E for ; Sun, 18 Jan 2009 10:08:06 +0000 (UTC) (envelope-from xxjack12xx@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 BCB268FC21 for ; Sun, 18 Jan 2009 10:08:06 +0000 (UTC) (envelope-from xxjack12xx@gmail.com) Received: by wf-out-1314.google.com with SMTP id 24so2513106wfg.7 for ; Sun, 18 Jan 2009 02:08:06 -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=hXOjgC9y/dU9tlwBmfOx0OnSY7AeWKMhJtlGdkeH5Og=; b=QfTt8P+p8nYmNXvs5pyRgMcYvJbco1TdVYL6U5BpveVnQZjiBKpSUAMEsH+nu2tXwa q+sEnuZfv329+aeWmTT5zvVSwjeMhiHhEN7oPe+6ABW3ZnSKE8XhQn430mXH9Ma4b3zb u4x3bxj+TpYGNYWIRfxjME27FRnu9UzyEn9EI= 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=EWxLtOW46oocduPqiBlcbI0KQILPWMre4O9wMh2KzG4SAwfn3fHkzFeAIlQyIfAUtk 1OumxyLzqEFJcmlGs8abZcfBuZ/F8XMwioToskHqSnf+JjXu7cTUdmhCbNeb0Xju04x/ /AM6IxbsZx+5xwWJR+ZJQY3SMnQUGkyXmeoME= MIME-Version: 1.0 Received: by 10.143.10.15 with SMTP id n15mr1836564wfi.319.1232271319919; Sun, 18 Jan 2009 01:35:19 -0800 (PST) In-Reply-To: <20090118093346.GA9819@onelab2.iet.unipi.it> References: <49729D80.8010506@charter.net> <20090118093346.GA9819@onelab2.iet.unipi.it> Date: Sun, 18 Jan 2009 01:35:19 -0800 Message-ID: From: "Jack L." To: Luigi Rizzo Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Andrew Lankford , stable@freebsd.org Subject: Re: System borked: loader stack overflow. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Jan 2009 10:08:07 -0000 I got the same thing. I put only the options I needed into loader.conf and it booted fine. On Sun, Jan 18, 2009 at 1:33 AM, Luigi Rizzo wrote: > On Sat, Jan 17, 2009 at 10:09:52PM -0500, Andrew Lankford wrote: >> After rebuilding world from 7-stable after cvsup, I can no longer boot. >> The loader tries to load the kernel but instead locks up with a stack >> overflow. Wish I could send more details, but I'll have to find another >> way to boot up my system first. > > just to identify the problem - what was the version of your > previous loader, and what kind of CPU do you have (Intel or AMD, > single or multi core) etc. > > (to boot again you can replace /boot/loader with one taken from > an older 6.3 or 7.0 CD) > > cheers > luigi > _______________________________________________ > 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 18 10:31:31 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 0D6B81065701 for ; Sun, 18 Jan 2009 10:31:31 +0000 (UTC) (envelope-from msch@snafu.de) Received: from waikiki.ops.eusc.inter.net (waikiki.ops.eusc.inter.net [84.23.254.155]) by mx1.freebsd.org (Postfix) with ESMTP id BC88E8FC1B for ; Sun, 18 Jan 2009 10:31:30 +0000 (UTC) (envelope-from msch@snafu.de) X-Trace: 507c6d73636840736e6166752e64657c38372e3138372e3130392e3235347c314c 4f5567772d3030303936582d41317c31323332323733373432 Received: from waikiki.ops.eusc.inter.net ([10.155.10.19] helo=localhost) by waikiki.ops.eusc.inter.net with esmtpa (Exim 4.69) id 1LOUgw-00096X-A1 for stable@freebsd.org; Sun, 18 Jan 2009 11:15:42 +0100 Message-Id: From: Matthias Schuendehuette To: stable@freebsd.org Content-Type: multipart/signed; boundary=Apple-Mail-1-563471706; micalg=sha1; protocol="application/pkcs7-signature" Mime-Version: 1.0 (Apple Message framework v930.3) Date: Sun, 18 Jan 2009 11:15:41 +0100 X-Mailer: Apple Mail (2.930.3) X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: NFS-Locking problem with 6.4/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: Sun, 18 Jan 2009 10:31:31 -0000 --Apple-Mail-1-563471706 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Hello, I operate two FreeBSD-Servers in a Windows- and HP-UX Environment. One is a SAMBA-Server as a gateway between the Windows and the Unix world, the other is NFS-Server for the HP-UX 11i v1 Workstations. Both are HP ProLiants DL380 with additional external disks on SmartRAID Controllers. Since the HP-UX Workstations and their disks are becoming quite old, I started to move the home-directories to the FreeBSD Server, wich worked with 6.3-RELEASE quite good so far. Brave as I am, I updated the servers to 6.4 RELEASE and since then the users on the HP-UX machines with the homedirs on the FreeBSD-Server were locked... :-( I tried to find out what was happening and this are my results: When a user logs in on a HP-UX machine, his '.profile' file is opened and read/executed, but it seems, that it cannot be closed any more. So if the last line in the '.profile' is "echo foo bar" you *can* see "foo bar" on the screen, but then nothing happens any more, the machine is locked. I recorded such a session with 'tcpdump' and looked at the dump... the only noticeable things are *Bursts* of NLM V4 CANCEL_MSGes on the same filehandle. Eg: "V4 CANCEL_MSG Call FH:0x644201fe svid:xxxx pos:0-0" This line is repeated 7 times with various values for 'svid'. I'm no NFS specialist at all, so I cannot tell you more :-/ But I can supply the dump (if needed), it's 92KB, so the size should not be a problem... BTW: I tried this with and without kernel support for NFS-Locking - no difference. I also tried the new replacement server with FreeBSD 7.1- RELEASE: Just the same problems, with and without kernel support. I hope someone is willing to work on that issue... As mentioned, a new, non-productive server is available in the moment, so tests are easily possible. TIA Matthew -- Ciao/BSD - Matthias Matthias Schuendehuette , Berlin (Germany) --Apple-Mail-1-563471706-- From owner-freebsd-stable@FreeBSD.ORG Sun Jan 18 11:47: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 C43461065674; Sun, 18 Jan 2009 11:47:23 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from host57.msm.che.vodafone (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 37ECD8FC14; Sun, 18 Jan 2009 11:47:21 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <497316C8.5050001@FreeBSD.org> Date: Sun, 18 Jan 2009 11:47:20 +0000 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) MIME-Version: 1.0 To: Tomas Randa References: <042FE04A-2F8D-47DD-8454-7BBA3791D7A8@inoc.net> <496BA9AE.10801@max.af.czu.cz> In-Reply-To: <496BA9AE.10801@max.af.czu.cz> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@FreeBSD.org, Robert Watson , 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: Sun, 18 Jan 2009 11:47:24 -0000 Tomas Randa wrote: > 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? You and anyone else seeing performance problems should try to work through the advice given here: http://people.freebsd.org/~kris/scaling/Help_my_system_is_slow.pdf Kris From owner-freebsd-stable@FreeBSD.ORG Sun Jan 18 12:50: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 74B80106564A for ; Sun, 18 Jan 2009 12:50:52 +0000 (UTC) (envelope-from talon@lpthe.jussieu.fr) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.freebsd.org (Postfix) with ESMTP id F2C5B8FC21 for ; Sun, 18 Jan 2009 12:50:51 +0000 (UTC) (envelope-from talon@lpthe.jussieu.fr) Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.14.3/jtpda-5.4) with ESMTP id n0ICLINY061084 for ; Sun, 18 Jan 2009 13:21:19 +0100 (CET) X-Ids: 165 Received: from niobe.lpthe.jussieu.fr (niobe.lpthe.jussieu.fr [134.157.10.41]) by parthe.lpthe.jussieu.fr (Postfix) with ESMTP id 975F489DEE for ; Sun, 18 Jan 2009 13:21:17 +0100 (CET) Received: by niobe.lpthe.jussieu.fr (Postfix, from userid 2005) id 4D6543D; Sun, 18 Jan 2009 13:21:17 +0100 (CET) Date: Sun, 18 Jan 2009 13:21:17 +0100 From: Michel Talon To: freebsd-stable@FreeBSD.org Message-ID: <20090118122117.GA62704@lpthe.jussieu.fr> Mail-Followup-To: Michel Talon , freebsd-stable@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0.1 (shiva.jussieu.fr [134.157.0.165]); Sun, 18 Jan 2009 13:21:19 +0100 (CET) X-Virus-Scanned: ClamAV 0.94.2/8874/Sun Jan 18 06:02:00 2009 on shiva.jussieu.fr X-Virus-Status: Clean X-Miltered: at jchkmail2.jussieu.fr with ID 497302C3.006 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)! X-j-chkmail-Enveloppe: 497302C3.006/134.157.10.1/parthe.lpthe.jussieu.fr/parthe.lpthe.jussieu.fr/ X-j-chkmail-Score: MSGID : 497302C3.006 on jchkmail2.jussieu.fr : j-chkmail score : . : R=. U=. O=. B=0.011 -> S=0.011 X-j-chkmail-Status: Ham Cc: 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, 18 Jan 2009 12:50:52 -0000 Tomas Randa wrote: > 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 can add a "me too" here. This is on my desktop, very lightly loaded. This computer never had a single problem under FreeBSD so i don't suspect a hardware problem. My previous upgrade was FreeBSD 7.0-STABLE #0: Tue Jul 22, and worked perfectly fine with exactly the same software configuration. Now i have FreeBSD 7.1-STABLE #0: Mon Jan 5 , and the situation is disastrous. Freshly after boot the machine seems to work normal, but after a few days it becomes slower and slower, windows takes seconds to appear, firefox3 begins to have garbled output, etc. Then i had the following problem, firefox got stuck in kernel, impossible to kill it by kill -9. Needless to say i inspected everything, dmesg, xsession-errors, top, etc. without seeing anything suspicious. So i rebooted, and bingo! the machine paniced, mentioning firefox. But the panic itself get stuck and i had to push the reset button, so no dump. After reboot, machine works OK for two or three days, then problems begin again. I am convinced there is a big problem in the kernel. For reference, here is top and dmesg: CPU: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle Mem: 264M Active, 613M Inact, 485M Wired, 22M Cache, 112M Buf, 116M Free Swap: 2023M Total, 4K Used, 2023M Free PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 62965 michel 1 44 0 3532K 1884K CPU1 1 0:00 0.29% top 2327 root 1 44 0 161M 29228K select 1 30:39 0.00% Xorg 95937 root 1 44 0 24112K 16800K select 1 2:35 0.00% kdm-bin_gr 3099 root 1 4 0 3304K 1028K select 0 1:30 0.00% moused 2209 news 1 8 0 3464K 1052K wait 0 0:37 0.00% sh 884 root 1 44 0 4712K 2028K select 1 0:12 0.00% ntpd 453 _pflogd 1 -58 0 3380K 1352K bpf 0 0:11 0.00% pflogd 1634 www 1 4 0 6268K 2656K kqread 0 0:10 0.00% lighttpd 788 root 1 44 0 3164K 3184K select 0 0:04 0.00% amd 2206 news 1 44 0 15208K 12160K select 0 0:03 0.00% innd 879 root 9 4 0 5432K 2460K kqread 1 0:02 0.00% nscd 955 root 1 44 0 2736K 1216K select 1 0:02 0.00% master 758 root 1 44 0 3164K 1340K select 1 0:02 0.00% ypbind ........... so no memory problem 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 5 14:29:23 CET 2009 michel@niobe.lpthe.jussieu.fr:/usr/obj/usr/src/sys/NIOBE Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 3.06GHz (3073.65-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf27 Stepping = 7 Features=0xbfebfbff Features2=0x4400 Logical CPUs per core: 2 real memory = 1610530816 (1535 MB) avail memory = 1568387072 (1495 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 This module (opensolaris) contains code covered by the Common Development and Distribution License (CDDL) see http://opensolaris.org/os/licensing/opensolaris_license/ ioapic0 irqs 0-23 on motherboard acpi0: on motherboard acpi0: Overriding SCI Interrupt from IRQ 9 to IRQ 22 acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, 5ff00000 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: on hostb0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0xd800-0xd8ff mem 0xe0000000-0xefffffff,0xdf000000-0xdf00ffff irq 16 at device 0.0 on pci1 uhci0: port 0xb800-0xb81f irq 16 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: on uhci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xb400-0xb41f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: on uhci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xb000-0xb01f irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] uhci2: [ITHREAD] usb2: on uhci2 usb2: USB revision 1.0 uhub2: on usb2 uhub2: 2 ports with 2 removable, self powered ehci0: mem 0xde800000-0xde8003ff irq 23 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb3: EHCI version 1.0 usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 uhub3: on usb3 uhub3: 6 ports with 6 removable, self powered pcib2: at device 30.0 on pci0 pci2: on pcib2 bfe0: mem 0xde000000-0xde001fff irq 20 at device 5.0 on pci2 miibus0: on bfe0 bmtphy0: PHY 1 on miibus0 bmtphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto bfe0: Ethernet address: 00:0c:6e:04:5d:39 bfe0: [ITHREAD] fxp0: port 0xa800-0xa83f mem 0xdd800000-0xdd800fff,0xdd000000-0xdd0fffff irq 23 at device 11.0 on pci2 miibus1: on fxp0 inphy0: PHY 1 on miibus1 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:02:b3:1d:df:8e fxp0: [ITHREAD] sym0: <875> port 0xa400-0xa4ff mem 0xdc800000-0xdc8000ff,0xdc000000-0xdc000fff irq 20 at device 12.0 on pci2 sym0: Tekram NVRAM, ID 7, Fast-20, SE, parity checking sym0: [ITHREAD] isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f irq 18 at device 31.1 on pci0 ata0: on atapci0 ata0: [ITHREAD] ata1: on atapci0 ata1: [ITHREAD] pcm0: port 0x9800-0x98ff,0x9400-0x943f mem 0xdb800000-0xdb8001ff,0xdb000000-0xdb0000ff irq 17 at device 31.5 on pci0 pcm0: [ITHREAD] pcm0: fdc0: port 0x3f2-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FILTER] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio0: [FILTER] sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A sio1: [FILTER] atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] cpu0: on acpi0 p4tcc0: on cpu0 cpu1: on acpi0 p4tcc1: on cpu1 pmtimer0 on isa0 orm0: at iomem 0xc0000-0xccfff,0xd0000-0xd0fff 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 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppbus0: on ppc0 ppbus0: [ITHREAD] lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 ppc0: [GIANT-LOCKED] ppc0: [ITHREAD] ums0: on uhub1 ums0: 5 buttons and Z dir. WARNING: ZFS is considered to be an experimental feature in FreeBSD. Timecounters tick every 1.000 msec Waiting 5 seconds for SCSI devices to settle ZFS filesystem version 6 ZFS storage pool version 6 ad0: 58644MB at ata0-master UDMA100 acd0: DVDR at ata1-master UDMA33 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 (probe5:sym0:0:5:0): phase change 6-7 6@01a0c7a8 resid=4. (da0:sym0:0:5:0): phase change 6-7 6@01a0c7a8 resid=4. da0 at sym0 bus 0 target 5 lun 0 da0: Removable Direct Access SCSI-2 device da0: 3.300MB/s transfers da0: 96MB (196608 512 byte sectors: 64H 32S/T 96C) cd0 at ata1 bus 0 target 0 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 #1 Launched! Trying to mount root from ufs:/dev/ad0s1a WARNING: / was not properly dismounted WARNING: /home was not properly dismounted /home: mount pending error: blocks 128 files 10 WARNING: /usr was not properly dismounted WARNING: /var was not properly dismounted WARNING: TMPFS is considered to be a highly experimental feature in FreeBSD. fxp0: Microcode loaded, int_delay: 1000 usec bundle_max: 6 fxp0: Microcode loaded, int_delay: 1000 usec bundle_max: 6 fxp0: Microcode loaded, int_delay: 1000 usec bundle_max: 6 fxp0: Microcode loaded, int_delay: 1000 usec bundle_max: 6 -- Michel TALON From owner-freebsd-stable@FreeBSD.ORG Sun Jan 18 15:38:53 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 7DF7B106564A for ; Sun, 18 Jan 2009 15:38:53 +0000 (UTC) (envelope-from lankfordandrew@charter.net) Received: from mta21.charter.net (mta21.charter.net [216.33.127.81]) by mx1.freebsd.org (Postfix) with ESMTP id D40098FC08 for ; Sun, 18 Jan 2009 15:38:52 +0000 (UTC) (envelope-from lankfordandrew@charter.net) Received: from aarprv04.charter.net ([10.20.200.74]) by mta21.charter.net (InterMail vM.7.09.01.00 201-2219-108-20080618) with ESMTP id <20090118153852.PUDX7559.mta21.charter.net@aarprv04.charter.net>; Sun, 18 Jan 2009 10:38:52 -0500 Received: from [192.168.1.151] (really [68.191.116.244]) by aarprv04.charter.net with ESMTP id <20090118153852.INRQ25639.aarprv04.charter.net@[192.168.1.151]>; Sun, 18 Jan 2009 10:38:52 -0500 Message-ID: <49734D0B.8050604@charter.net> Date: Sun, 18 Jan 2009 10:38:51 -0500 From: Andrew Lankford User-Agent: Thunderbird 2.0.0.19 (X11/20090111) MIME-Version: 1.0 To: Luigi Rizzo References: <49729D80.8010506@charter.net> <20090118093346.GA9819@onelab2.iet.unipi.it> In-Reply-To: <20090118093346.GA9819@onelab2.iet.unipi.it> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Chzlrs: 0 Cc: peterjeremy@optushome.com.au, stable@freebsd.org, xxjack12xx@gmail.com Subject: Re: System borked: loader stack overflow. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Jan 2009 15:38:53 -0000 I can't say what version of the loader it is that I'm using, but (following Peter's advice, thanks), I've tried loader.old (about a week old) and the latest loader (built yesterday), and both start. Where each loader has a problem appears to be reading (include-ing?) /boot/default/loader.conf . The spinner spins for a longer time than usual, and then the loader gives up with the stack overflow. Fortunately, I still got a prompt and am able to load the latest kernel acpi and a what few other modules I need to boot successfully and reply to your emails. A quick look at /boot/defaults/loader.conf ( version 1.122.2.4 2008/11/24 00:52:26 ) shows nothing out of the ordinary. FYI: I'm using the Windows Vista boot manager with boot1 instead of boot0, although boot1 doesn't appear to have changed since I first installed 7.0 on my notebook. Andrew Lankford Luigi Rizzo wrote: > On Sat, Jan 17, 2009 at 10:09:52PM -0500, Andrew Lankford wrote: > >> After rebuilding world from 7-stable after cvsup, I can no longer boot. >> The loader tries to load the kernel but instead locks up with a stack >> overflow. Wish I could send more details, but I'll have to find another >> way to boot up my system first. >> > > just to identify the problem - what was the version of your > previous loader, and what kind of CPU do you have (Intel or AMD, > single or multi core) etc. > > (to boot again you can replace /boot/loader with one taken from > an older 6.3 or 7.0 CD) > > cheers > luigi > > From owner-freebsd-stable@FreeBSD.ORG Sun Jan 18 15:51:29 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 F1DC4106566B for ; Sun, 18 Jan 2009 15:51:29 +0000 (UTC) (envelope-from lankfordandrew@charter.net) Received: from mta21.charter.net (mta21.charter.net [216.33.127.81]) by mx1.freebsd.org (Postfix) with ESMTP id 88C488FC1D for ; Sun, 18 Jan 2009 15:51:29 +0000 (UTC) (envelope-from lankfordandrew@charter.net) Received: from aarprv04.charter.net ([10.20.200.74]) by mta21.charter.net (InterMail vM.7.09.01.00 201-2219-108-20080618) with ESMTP id <20090118155129.PZSG7559.mta21.charter.net@aarprv04.charter.net>; Sun, 18 Jan 2009 10:51:29 -0500 Received: from [192.168.1.151] (really [68.191.116.244]) by aarprv04.charter.net with ESMTP id <20090118155128.IWSX25639.aarprv04.charter.net@[192.168.1.151]>; Sun, 18 Jan 2009 10:51:28 -0500 Message-ID: <49735000.5040500@charter.net> Date: Sun, 18 Jan 2009 10:51:28 -0500 From: Andrew Lankford User-Agent: Thunderbird 2.0.0.19 (X11/20090111) MIME-Version: 1.0 To: Luigi Rizzo , stable@freebsd.org References: <49729D80.8010506@charter.net> <20090118093346.GA9819@onelab2.iet.unipi.it> In-Reply-To: <20090118093346.GA9819@onelab2.iet.unipi.it> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Chzlrs: 0 Cc: Subject: Re: System borked: loader stack overflow. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Jan 2009 15:51:30 -0000 The cpu I'm using is: CPU: Intel(R) Core(TM)2 Duo CPU T7500 @ 2.20GHz (2194.52-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6fb Stepping = 11 Features=0xbfebfbff Features2=0xe3bd AMD Features=0x20100000 AMD Features2=0x1 Cores per package: 2 real memory = 2137444352 (2038 MB) avail memory = 2086969344 (1990 MB) ACPI APIC Table: It's a Dell Vostro 1400. Andrew Lankford Luigi Rizzo wrote: > On Sat, Jan 17, 2009 at 10:09:52PM -0500, Andrew Lankford wrote: > >> After rebuilding world from 7-stable after cvsup, I can no longer boot. >> The loader tries to load the kernel but instead locks up with a stack >> overflow. Wish I could send more details, but I'll have to find another >> way to boot up my system first. >> > > just to identify the problem - what was the version of your > previous loader, and what kind of CPU do you have (Intel or AMD, > single or multi core) etc. > > (to boot again you can replace /boot/loader with one taken from > an older 6.3 or 7.0 CD) > > cheers > luigi > > From owner-freebsd-stable@FreeBSD.ORG Sun Jan 18 16:42: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 16B04106566B for ; Sun, 18 Jan 2009 16:42:08 +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 CE9CB8FC14 for ; Sun, 18 Jan 2009 16:42:07 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 7BB9B73098; Sun, 18 Jan 2009 17:47:24 +0100 (CET) Date: Sun, 18 Jan 2009 17:47:24 +0100 From: Luigi Rizzo To: Andrew Lankford Message-ID: <20090118164724.GA21705@onelab2.iet.unipi.it> References: <49729D80.8010506@charter.net> <20090118093346.GA9819@onelab2.iet.unipi.it> <49734D0B.8050604@charter.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49734D0B.8050604@charter.net> User-Agent: Mutt/1.4.2.3i Cc: peterjeremy@optushome.com.au, stable@freebsd.org, xxjack12xx@gmail.com Subject: Re: System borked: loader stack overflow. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Jan 2009 16:42:08 -0000 On Sun, Jan 18, 2009 at 10:38:51AM -0500, Andrew Lankford wrote: > > I can't say what version of the loader it is that I'm using, but > (following Peter's advice, thanks), I've tried loader.old (about a week > old) and the latest loader (built yesterday), and both start. Where > each loader has a problem appears to be reading (include-ing?) > /boot/default/loader.conf . The spinner spins for a longer time than ok so the problem could be is a recursive assignment of loader_conf_files in your previous installation (either as a result of the default installation, or because of manual modifications). Could you please send me a copy of your /boot/loader.conf and /boot/defaults/loader.conf so i can check ? A recent commit fixed the handling of loader_conf_files, which previously was broken (in some cases assignments were ignored). A side effect of the fix is that now certain errors in the config files are now detected as such. cheers luigi From owner-freebsd-stable@FreeBSD.ORG Sun Jan 18 16:46:17 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 761DD106564A for ; Sun, 18 Jan 2009 16:46:17 +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 3928C8FC21 for ; Sun, 18 Jan 2009 16:46:17 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 2EC4773098; Sun, 18 Jan 2009 17:51:34 +0100 (CET) Date: Sun, 18 Jan 2009 17:51:34 +0100 From: Luigi Rizzo To: Andrew Lankford Message-ID: <20090118165134.GB21705@onelab2.iet.unipi.it> References: <49729D80.8010506@charter.net> <20090118093346.GA9819@onelab2.iet.unipi.it> <49734D0B.8050604@charter.net> <20090118164724.GA21705@onelab2.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090118164724.GA21705@onelab2.iet.unipi.it> User-Agent: Mutt/1.4.2.3i Cc: peterjeremy@optushome.com.au, stable@freebsd.org, xxjack12xx@gmail.com Subject: Re: System borked: loader stack overflow. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Jan 2009 16:46:17 -0000 On Sun, Jan 18, 2009 at 05:47:24PM +0100, Luigi Rizzo wrote: > On Sun, Jan 18, 2009 at 10:38:51AM -0500, Andrew Lankford wrote: > > > > I can't say what version of the loader it is that I'm using, but > > (following Peter's advice, thanks), I've tried loader.old (about a week > > old) and the latest loader (built yesterday), and both start. Where > > each loader has a problem appears to be reading (include-ing?) > > /boot/default/loader.conf . The spinner spins for a longer time than > > ok so the problem could be is a recursive assignment of loader_conf_files > in your previous installation (either as a result of the default > installation, or because of manual modifications). > Could you please send me a copy of your /boot/loader.conf and > /boot/defaults/loader.conf so i can check ? also /boot/loader.conf.local please... thanks luigi > A recent commit fixed the handling of loader_conf_files, > which previously was broken (in some cases assignments were ignored). > A side effect of the fix is that now certain errors in the config > files are now detected as such. > > cheers > luigi From owner-freebsd-stable@FreeBSD.ORG Sun Jan 18 16:57:43 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 CDE2A1065670 for ; Sun, 18 Jan 2009 16:57:43 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from mail-gw1.york.ac.uk (mail-gw1.york.ac.uk [144.32.128.246]) by mx1.freebsd.org (Postfix) with ESMTP id 5B4178FC17 for ; Sun, 18 Jan 2009 16:57:43 +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-gw1.york.ac.uk (8.13.6/8.13.6) with ESMTP id n0IGvbmx017836; Sun, 18 Jan 2009 16:57:37 GMT Received: from ury.york.ac.uk ([144.32.108.81]) by mail-gw6.york.ac.uk with esmtps (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from ) id 1LOaxt-0006Vs-TX; Sun, 18 Jan 2009 16:57:37 +0000 Received: from ury.york.ac.uk (localhost.york.ac.uk [127.0.0.1]) by ury.york.ac.uk (8.14.3/8.14.3) with ESMTP id n0IGvbdt016279; Sun, 18 Jan 2009 16:57:37 GMT (envelope-from gavin@FreeBSD.org) Received: from localhost (gavin@localhost) by ury.york.ac.uk (8.14.3/8.14.3/Submit) with ESMTP id n0IGvb6F016276; Sun, 18 Jan 2009 16:57:37 GMT (envelope-from gavin@FreeBSD.org) X-Authentication-Warning: ury.york.ac.uk: gavin owned process doing -bs Date: Sun, 18 Jan 2009 16:57:37 +0000 (GMT) From: Gavin Atkinson X-X-Sender: gavin@ury.york.ac.uk To: Andrew Lankford In-Reply-To: <49734D0B.8050604@charter.net> Message-ID: <20090118165632.O24894@ury.york.ac.uk> References: <49729D80.8010506@charter.net> <20090118093346.GA9819@onelab2.iet.unipi.it> <49734D0B.8050604@charter.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin@freebsd.org Cc: peterjeremy@optushome.com.au, stable@FreeBSD.org, Luigi Rizzo , xxjack12xx@gmail.com Subject: Re: System borked: loader stack overflow. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Jan 2009 16:57:44 -0000 On Sun, 18 Jan 2009, Andrew Lankford wrote: > I can't say what version of the loader it is that I'm using, but (following > Peter's advice, thanks), I've tried loader.old (about a week old) and the > latest loader (built yesterday), and both start. Where each loader has a > problem appears to be reading (include-ing?) /boot/default/loader.conf . The > spinner spins for a longer time than usual, and then the loader gives up with > the stack overflow. Fortunately, I still got a prompt and am able to load > the latest kernel acpi and a what few other modules I need to boot > successfully and reply to your emails. Hmm, there's also a new PR in (kern/130674) which sounds like the same issue, on -HEAD. Gavin From owner-freebsd-stable@FreeBSD.ORG Sun Jan 18 17:11: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 B5B111065674 for ; Sun, 18 Jan 2009 17:11:38 +0000 (UTC) (envelope-from stas@FreeBSD.org) Received: from mx0.deglitch.com (backbone.deglitch.com [IPv6:2001:16d8:fffb:4::abba]) by mx1.freebsd.org (Postfix) with ESMTP id 397E38FC1A for ; Sun, 18 Jan 2009 17:11:38 +0000 (UTC) (envelope-from stas@FreeBSD.org) Received: from DSPAM-Daemon (localhost [127.0.0.1]) by mx0.deglitch.com (Postfix) with SMTP id 0B33F8FC51 for ; Sun, 18 Jan 2009 20:11:36 +0300 (MSK) Received: from orion.SpringDaemons.com (drsun1.dialup.corbina.ru [85.21.245.235]) by mx0.deglitch.com (Postfix) with ESMTPA id B8A8B8FC18; Sun, 18 Jan 2009 20:11:35 +0300 (MSK) Received: from orion (localhost [127.0.0.1]) by orion.SpringDaemons.com (Postfix) with SMTP id DB77B398F3; Sun, 18 Jan 2009 20:11:38 +0300 (MSK) Date: Sun, 18 Jan 2009 20:11:38 +0300 From: Stanislav Sedov To: josh.carroll@gmail.com Message-Id: <20090118201138.eeb5d9ad.stas@FreeBSD.org> In-Reply-To: <8cb6106e0812031453j6dc2f2f4i374145823c084eaa@mail.gmail.com> References: <8cb6106e0811241129o642dcf28re4ae177c8ccbaa25@mail.gmail.com> <20081125140601.GH2042@deviant.kiev.zoral.com.ua> <8cb6106e0811250617q5fffb41exe20dfb8314fc4a9d@mail.gmail.com> <20081125142827.GI2042@deviant.kiev.zoral.com.ua> <8cb6106e0811250657q6fdf08b0x1e94f35fd0a7ed4f@mail.gmail.com> <20081125150342.GL2042@deviant.kiev.zoral.com.ua> <8cb6106e0812031453j6dc2f2f4i374145823c084eaa@mail.gmail.com> Organization: The FreeBSD Project X-XMPP: ssedov@jabber.ru X-Voice: +7 916 849 20 23 X-PGP-Fingerprint: F21E D6CC 5626 9609 6CE2 A385 2BF5 5993 EB26 9581 X-Mailer: carrier-pigeon Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-DSPAM-Result: Innocent X-DSPAM-Processed: Sun Jan 18 20:11:36 2009 X-DSPAM-Confidence: 1.0000 X-DSPAM-Improbability: 1 in 98689409 chance of being spam X-DSPAM-Probability: 0.0023 X-DSPAM-Signature: 497362c8967002668918391 Cc: Kostik Belousov , freebsd-fs@freebsd.org, Stable , FreeBSD Subject: Re: ext2 inode size patch - RE: PR kern/124621 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Jan 2009 17:11:39 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 3 Dec 2008 17:53:43 -0500 "Josh Carroll" mentioned: > > Ok, I describe my concern once more. I do not object against the checking > > of the inode size. But, if inode size is changed, then some data is added > > to the inode, that could (and usually does, otherwise why extend it ?) > > change intrerpetation of the inode. Thus, we need a verification of the > > fact that simply ignoring added fields does not damage filesystem or > > cause user data corruption. Verification != testing. > > Let me take another crack at explaining why I think this patch is not dangerous. > > The inode size is determined by reading the following member: > > __u16 s_inode_size; > > of the ext2_super_block structure. > > I took a look at the Linux 2.6.27.7 kernel source, and indeed they do > something very similar if not the same: > > #define EXT2_INODE_SIZE(s) (EXT2_SB(s)->s_inode_size) > > If you compare to what I did: > > #define EXT2_INODE_SIZE(s) ((s)->u.ext2_sb.s_inode_size) > > This is really the same thing, since EXT2_SB is defined (in the Linux > kernel src as): > > #ifdef __KERNEL__ > #include > static inline struct ext2_sb_info *EXT2_SB(struct super_block *sb) > { > return sb->s_fs_info; > } > > And struct ext2_sb_info has the following member: > > int s_inode_size; > > Essentially, the changes I made simply query the existing information > from the filesystem, which is what the Linux kernel does as well. > > The inode size, blocks per group, etc are all defined at filesystem > creation time by mke2fs and it ensures the sanity of the relationship > between the inodes/blocks/block groups. > > The first diagram here: > > http://sunsite.nus.sg/LDP/LDP/tlk/node95.html > > Makes it clear that as long as the number of inodes per block and the > blocks per group is is sane during fs creation, looking up the inode > size as my patch does is fine, since the creation of the filesystem is > ensures a correct by construction situation. We're simply reading the > size of the inode based on the filesystem. > > I hope this is sufficient to convince some further thought about > committing this. > > For those interested in the relevant Linux kernel source, you can have > a look at line 105 of include/linux/ext2_fs.h from the linux-2.6.27.7 > kernel source. > Hi Josh! I've commited the similar patch today that should be fixing your problem. Can you check this, please? Sorry I've missed this thread in the first place. - -- Stanislav Sedov ST4096-RIPE -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAklzYsoACgkQK/VZk+smlYF3ZwCeOyVUdzrKOdu4Pg3ztAZ0QQaY GGIAnA+oL054T0EAajbfwpYSTDRKVISC =jJFT -----END PGP SIGNATURE----- !DSPAM:497362c8967002668918391! From owner-freebsd-stable@FreeBSD.ORG Sun Jan 18 17:38: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 1AAF0106564A for ; Sun, 18 Jan 2009 17:38:45 +0000 (UTC) (envelope-from dick@nagual.nl) Received: from nagual.nl (cc20684-a.assen1.dr.home.nl [82.74.10.158]) by mx1.freebsd.org (Postfix) with ESMTP id 8F4828FC13 for ; Sun, 18 Jan 2009 17:38:44 +0000 (UTC) (envelope-from dick@nagual.nl) Received: from westmark (westmark.nagual.nl [192.168.11.22]) by nagual.nl (8.13.8+Sun/8.13.8/yanta) with SMTP id n0IHGgSo009348 for ; Sun, 18 Jan 2009 18:16:42 +0100 (CET) Date: Sun, 18 Jan 2009 18:15:06 +0100 From: dick hoogendijk To: freebsd-stable@freebsd.org Message-Id: <20090118181506.d49fd170.dick@nagual.nl> In-Reply-To: <20090118122117.GA62704@lpthe.jussieu.fr> References: <20090118122117.GA62704@lpthe.jussieu.fr> Organization: de nagual X-Mailer: Sylpheed 2.6.0 (GTK+ 2.14.5; i386-pc-solaris2.11) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.63 on 192.168.11.35 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, 18 Jan 2009 17:38:45 -0000 On Sun, 18 Jan 2009 13:21:17 +0100 Michel Talon wrote: > My previous upgrade was FreeBSD 7.0-STABLE #0: Tue Jul 22, and worked > perfectly fine with exactly the same software configuration. > Now i have FreeBSD 7.1-STABLE #0: Mon Jan5, and the situation is > disastrous. Makes you wonder on on earth could have changed that much between 7.0/7.1 Nice upgrade.. This should not happen on the same hardware! -- Dick Hoogendijk -- PGP/GnuPG key: 01D2433D + http://nagual.nl/ | SunOS sxce snv105 ++ + All that's really worth doing is what we do for others (Lewis Carrol) From owner-freebsd-stable@FreeBSD.ORG Sun Jan 18 17:50:25 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 39A29106566B for ; Sun, 18 Jan 2009 17:50:25 +0000 (UTC) (envelope-from lankfordandrew@charter.net) Received: from mta21.charter.net (mta21.charter.net [216.33.127.81]) by mx1.freebsd.org (Postfix) with ESMTP id C82AC8FC13 for ; Sun, 18 Jan 2009 17:50:24 +0000 (UTC) (envelope-from lankfordandrew@charter.net) Received: from aarprv04.charter.net ([10.20.200.74]) by mta21.charter.net (InterMail vM.7.09.01.00 201-2219-108-20080618) with ESMTP id <20090118175012.SEND7559.mta21.charter.net@aarprv04.charter.net>; Sun, 18 Jan 2009 12:50:12 -0500 Received: from [192.168.1.151] (really [68.191.116.244]) by aarprv04.charter.net with ESMTP id <20090118175011.MLDT25639.aarprv04.charter.net@[192.168.1.151]>; Sun, 18 Jan 2009 12:50:11 -0500 Message-ID: <49736BD3.8020907@charter.net> Date: Sun, 18 Jan 2009 12:50:11 -0500 From: Andrew Lankford User-Agent: Thunderbird 2.0.0.19 (X11/20090111) MIME-Version: 1.0 To: stable@freebsd.org, Luigi Rizzo Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Chzlrs: 0 Cc: Subject: Re: System borked: loader stack overflow. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Jan 2009 17:50:25 -0000 Shortened my loader.conf to the bare essentials and now I'm back in business! Still curious whether redefining loader_conf_files (which I suppose should only be defined in the default loader.conf) caused the problem or whether it was something else. Thanks, Andrew Lankford From owner-freebsd-stable@FreeBSD.ORG Sun Jan 18 18:47: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 A5458106564A for ; Sun, 18 Jan 2009 18:47:32 +0000 (UTC) (envelope-from kometen@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.155]) by mx1.freebsd.org (Postfix) with ESMTP id B9C0D8FC13 for ; Sun, 18 Jan 2009 18:47:31 +0000 (UTC) (envelope-from kometen@gmail.com) Received: by fg-out-1718.google.com with SMTP id l26so1386800fgb.35 for ; Sun, 18 Jan 2009 10:47:30 -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=e19yuXOXfu74BucWr1HnXEmEZP5+xzr5kDcYZeGxTUw=; b=XzHB/WoYMVMAq8tcTyUk4swCnkXdPE59RStf1jTQYHk6yXK3K44w5F2UVZ1U+BT81H 8ilPEyVCfrNDgv2i4p0XJuGFWrBN16ljHIhoy3s9i38s+CMl62tFU/XGwkLVYet6/8sA fGCsLiHAuZuL49wu+VNCscLn30WIgyTg6CF8k= 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=r7jIZekhhB17371sO+2M2VBE7iNoztiJrca7OVT/PpsfNqKPjjGa725twksmPgAE56 loARXMH0tDE2Qx41/une38+A/llSqferQUC8XuocrXzfasPvA7QfKlAe9eR9zXhI0ApR pFSX+E4eqOaTHmjtTHbpwbbL5viWrtP6Z/KZo= Received: by 10.86.52.6 with SMTP id z6mr1851960fgz.63.1232304450355; Sun, 18 Jan 2009 10:47:30 -0800 (PST) Received: by 10.86.4.1 with HTTP; Sun, 18 Jan 2009 10:47:30 -0800 (PST) Message-ID: Date: Sun, 18 Jan 2009 19:47:30 +0100 From: "Claus Guttesen" To: "dick hoogendijk" In-Reply-To: <20090118181506.d49fd170.dick@nagual.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20090118122117.GA62704@lpthe.jussieu.fr> <20090118181506.d49fd170.dick@nagual.nl> 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, 18 Jan 2009 18:47:32 -0000 >> My previous upgrade was FreeBSD 7.0-STABLE #0: Tue Jul 22, and worked >> perfectly fine with exactly the same software configuration. >> Now i have FreeBSD 7.1-STABLE #0: Mon Jan5, and the situation is >> disastrous. > > Makes you wonder on on earth could have changed that much between > 7.0/7.1 Nice upgrade.. This should not happen on the same hardware! There will always be changes when new features/options/enhancements are introduced. Me for my part have never had any serious trouble with FreeBSD what so ever since FreeBSD 5.1/2 when some kernel-limits had to be changed. My problem was solved with the help from this list. -- regards Claus When lenity and cruelty play for a kingdom, the gentler gamester is the soonest winner. Shakespeare From owner-freebsd-stable@FreeBSD.ORG Sun Jan 18 19:16: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 EB41C1065674 for ; Sun, 18 Jan 2009 19:16:28 +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 AEE688FC20 for ; Sun, 18 Jan 2009 19:16:28 +0000 (UTC) (envelope-from thompsa@FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by pele.citylink.co.nz (Postfix) with ESMTP id 48913FEF4; Mon, 19 Jan 2009 07:56:09 +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 4TC2oRUAbpIn; Mon, 19 Jan 2009 07:56:05 +1300 (NZDT) Received: from citylink.fud.org.nz (unknown [202.8.44.45]) by pele.citylink.co.nz (Postfix) with ESMTP; Mon, 19 Jan 2009 07:56:05 +1300 (NZDT) Received: by citylink.fud.org.nz (Postfix, from userid 1001) id 3925E1142D; Mon, 19 Jan 2009 07:56:05 +1300 (NZDT) Date: Sun, 18 Jan 2009 10:56:05 -0800 From: Andrew Thompson To: Luigi Rizzo Message-ID: <20090118185605.GA28874@citylink.fud.org.nz> References: <49729D80.8010506@charter.net> <20090118093346.GA9819@onelab2.iet.unipi.it> <49734D0B.8050604@charter.net> <20090118164724.GA21705@onelab2.iet.unipi.it> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090118164724.GA21705@onelab2.iet.unipi.it> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: Andrew Lankford , peterjeremy@optushome.com.au, stable@freebsd.org, xxjack12xx@gmail.com Subject: Re: System borked: loader stack overflow. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Jan 2009 19:16:29 -0000 On Sun, Jan 18, 2009 at 05:47:24PM +0100, Luigi Rizzo wrote: > On Sun, Jan 18, 2009 at 10:38:51AM -0500, Andrew Lankford wrote: > > > > I can't say what version of the loader it is that I'm using, but > > (following Peter's advice, thanks), I've tried loader.old (about a week > > old) and the latest loader (built yesterday), and both start. Where > > each loader has a problem appears to be reading (include-ing?) > > /boot/default/loader.conf . The spinner spins for a longer time than > > ok so the problem could be is a recursive assignment of loader_conf_files > in your previous installation (either as a result of the default > installation, or because of manual modifications). > Could you please send me a copy of your /boot/loader.conf and > /boot/defaults/loader.conf so i can check ? > > A recent commit fixed the handling of loader_conf_files, > which previously was broken (in some cases assignments were ignored). > A side effect of the fix is that now certain errors in the config > files are now detected as such. Having the following in /boot/loader.conf triggers it for me, loader_conf_files="/boot/device.hints /boot/loader.conf" You may say thats its an invalid config line but the loader shouldnt blow up from it. Can this be fixed up somehow? Andrew From owner-freebsd-stable@FreeBSD.ORG Sun Jan 18 19:19:37 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 C23F8106564A for ; Sun, 18 Jan 2009 19:19:37 +0000 (UTC) (envelope-from lankfordandrew@charter.net) Received: from mta11.charter.net (mta11.charter.net [216.33.127.80]) by mx1.freebsd.org (Postfix) with ESMTP id 581D88FC08 for ; Sun, 18 Jan 2009 19:19:37 +0000 (UTC) (envelope-from lankfordandrew@charter.net) Received: from aarprv06.charter.net ([10.20.200.76]) by mta11.charter.net (InterMail vM.7.09.01.00 201-2219-108-20080618) with ESMTP id <20090118191924.DYGC21265.mta11.charter.net@aarprv06.charter.net> for ; Sun, 18 Jan 2009 14:19:24 -0500 Received: from [192.168.1.151] (really [68.191.116.244]) by aarprv06.charter.net with ESMTP id <20090118191924.GISH128.aarprv06.charter.net@[192.168.1.151]> for ; Sun, 18 Jan 2009 14:19:24 -0500 Message-ID: <497380BB.1050409@charter.net> Date: Sun, 18 Jan 2009 14:19:23 -0500 From: Andrew Lankford User-Agent: Thunderbird 2.0.0.19 (X11/20090111) MIME-Version: 1.0 To: stable@freebsd.org References: <49729D80.8010506@charter.net> <20090118093346.GA9819@onelab2.iet.unipi.it> <49734D0B.8050604@charter.net> <20090118164724.GA21705@onelab2.iet.unipi.it> <20090118185605.GA28874@citylink.fud.org.nz> In-Reply-To: <20090118185605.GA28874@citylink.fud.org.nz> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Chzlrs: 0 Cc: Subject: Re: System borked: loader stack overflow. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Jan 2009 19:19:38 -0000 Andrew Thompson wrote: > On Sun, Jan 18, 2009 at 05:47:24PM +0100, Luigi Rizzo wrote: > >> On Sun, Jan 18, 2009 at 10:38:51AM -0500, Andrew Lankford wrote: >> >>> I can't say what version of the loader it is that I'm using, but >>> (following Peter's advice, thanks), I've tried loader.old (about a week >>> old) and the latest loader (built yesterday), and both start. Where >>> each loader has a problem appears to be reading (include-ing?) >>> /boot/default/loader.conf . The spinner spins for a longer time than >>> >> ok so the problem could be is a recursive assignment of loader_conf_files >> in your previous installation (either as a result of the default >> installation, or because of manual modifications). >> Could you please send me a copy of your /boot/loader.conf and >> /boot/defaults/loader.conf so i can check ? >> >> A recent commit fixed the handling of loader_conf_files, >> which previously was broken (in some cases assignments were ignored). >> A side effect of the fix is that now certain errors in the config >> files are now detected as such. >> > > Having the following in /boot/loader.conf triggers it for me, > > loader_conf_files="/boot/device.hints /boot/loader.conf" > > You may say thats its an invalid config line but the loader shouldnt > blow up from it. Can this be fixed up somehow? > > Andrew > > Indeed, it would be nice if um someone (anyone, mind you) with commit priviledges might put some descriptive comments around the "default-only" settings in /boot/default/loader.conf...:) Andrew Lankford From owner-freebsd-stable@FreeBSD.ORG Sun Jan 18 20:03:40 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 40DFE1065674 for ; Sun, 18 Jan 2009 20:03:40 +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 045B48FC1A for ; Sun, 18 Jan 2009 20:03:39 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 3EF4273098; Sun, 18 Jan 2009 21:08:56 +0100 (CET) Date: Sun, 18 Jan 2009 21:08:56 +0100 From: Luigi Rizzo To: Andrew Lankford Message-ID: <20090118200856.GA28366@onelab2.iet.unipi.it> References: <49729D80.8010506@charter.net> <20090118093346.GA9819@onelab2.iet.unipi.it> <49734D0B.8050604@charter.net> <20090118164724.GA21705@onelab2.iet.unipi.it> <20090118185605.GA28874@citylink.fud.org.nz> <497380BB.1050409@charter.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <497380BB.1050409@charter.net> User-Agent: Mutt/1.4.2.3i Cc: stable@freebsd.org Subject: Re: System borked: loader stack overflow. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Jan 2009 20:03:40 -0000 On Sun, Jan 18, 2009 at 02:19:23PM -0500, Andrew Lankford wrote: > Andrew Thompson wrote: ... > >Having the following in /boot/loader.conf triggers it for me, > > > > loader_conf_files="/boot/device.hints /boot/loader.conf" > > > >You may say thats its an invalid config line but the loader shouldnt > >blow up from it. Can this be fixed up somehow? no, this cannot be "fixed" because it is the user misprogramming the system, such as providing the wrong path to the kernel or writing a loop in /etc/rc.conf or a billion other ways. Setting loader_conf_files="x y z" is basically equivalent to writing "call a; call b; call c;" in a programming language, with the only difference that the action is done at the end of the current file. > Indeed, it would be nice if um someone (anyone, mind you) with commit > priviledges might put some descriptive comments around the > "default-only" settings in /boot/default/loader.conf...:) it is not "default only", either - it is just one of the many files loaded by /boot/loader, you just need to avoid infinite loops. I can write some extra notes in the manpage, and perhaps suggest a rename of the /boot/defaults/ file so one does not end up with two copies by mistake. cheers luigi From owner-freebsd-stable@FreeBSD.ORG Sun Jan 18 20:18:14 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 DCD8F106564A for ; Sun, 18 Jan 2009 20:18:14 +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 9FC638FC17 for ; Sun, 18 Jan 2009 20:18:14 +0000 (UTC) (envelope-from thompsa@FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by pele.citylink.co.nz (Postfix) with ESMTP id 7DC52FEF4; Mon, 19 Jan 2009 09:18:13 +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 GSAmbGtn6CpW; Mon, 19 Jan 2009 09:18:10 +1300 (NZDT) Received: from citylink.fud.org.nz (unknown [202.8.44.45]) by pele.citylink.co.nz (Postfix) with ESMTP; Mon, 19 Jan 2009 09:18:10 +1300 (NZDT) Received: by citylink.fud.org.nz (Postfix, from userid 1001) id A356D11431; Mon, 19 Jan 2009 09:18:09 +1300 (NZDT) Date: Sun, 18 Jan 2009 12:18:09 -0800 From: Andrew Thompson To: Luigi Rizzo Message-ID: <20090118201809.GA44812@citylink.fud.org.nz> References: <49729D80.8010506@charter.net> <20090118093346.GA9819@onelab2.iet.unipi.it> <49734D0B.8050604@charter.net> <20090118164724.GA21705@onelab2.iet.unipi.it> <20090118185605.GA28874@citylink.fud.org.nz> <497380BB.1050409@charter.net> <20090118200856.GA28366@onelab2.iet.unipi.it> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090118200856.GA28366@onelab2.iet.unipi.it> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: Andrew Lankford , stable@freebsd.org Subject: Re: System borked: loader stack overflow. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Jan 2009 20:18:15 -0000 On Sun, Jan 18, 2009 at 09:08:56PM +0100, Luigi Rizzo wrote: > On Sun, Jan 18, 2009 at 02:19:23PM -0500, Andrew Lankford wrote: > > Andrew Thompson wrote: > ... > > >Having the following in /boot/loader.conf triggers it for me, > > > > > > loader_conf_files="/boot/device.hints /boot/loader.conf" > > > > > >You may say thats its an invalid config line but the loader shouldnt > > >blow up from it. Can this be fixed up somehow? > > no, this cannot be "fixed" because it is the user misprogramming > the system, such as providing the wrong path to the kernel > or writing a loop in /etc/rc.conf or a billion other ways. Yes, but you can copy /etc/defaults/rc.conf to /etc/rc.conf and things still work. > Setting loader_conf_files="x y z" is basically equivalent to > writing "call a; call b; call c;" in a programming language, > with the only difference that the action is done at the end of > the current file. Ok, then loader_conf_files needs to be marked as special and not to be overridden from /boot/defaults/loader.conf like all the other options. A better way would be to track included files and not reprocess them. Also an entry in UPDATING that a config error that was once harmless now renders the system unbootable (without intervention). cheers, Andrew From owner-freebsd-stable@FreeBSD.ORG Sun Jan 18 21:14:12 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 22624106566B; Sun, 18 Jan 2009 21:14:12 +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 D5AC08FC16; Sun, 18 Jan 2009 21:14:11 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 15B4273098; Sun, 18 Jan 2009 22:19:29 +0100 (CET) Date: Sun, 18 Jan 2009 22:19:29 +0100 From: Luigi Rizzo To: Andrew Thompson Message-ID: <20090118211929.GA29063@onelab2.iet.unipi.it> References: <49729D80.8010506@charter.net> <20090118093346.GA9819@onelab2.iet.unipi.it> <49734D0B.8050604@charter.net> <20090118164724.GA21705@onelab2.iet.unipi.it> <20090118185605.GA28874@citylink.fud.org.nz> <497380BB.1050409@charter.net> <20090118200856.GA28366@onelab2.iet.unipi.it> <20090118201809.GA44812@citylink.fud.org.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090118201809.GA44812@citylink.fud.org.nz> User-Agent: Mutt/1.4.2.3i Cc: Andrew Lankford , stable@freebsd.org Subject: Re: System borked: loader stack overflow. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Jan 2009 21:14:12 -0000 On Sun, Jan 18, 2009 at 12:18:09PM -0800, Andrew Thompson wrote: > On Sun, Jan 18, 2009 at 09:08:56PM +0100, Luigi Rizzo wrote: > > On Sun, Jan 18, 2009 at 02:19:23PM -0500, Andrew Lankford wrote: > > > Andrew Thompson wrote: > > ... > > > >Having the following in /boot/loader.conf triggers it for me, > > > > > > > > loader_conf_files="/boot/device.hints /boot/loader.conf" > > > > > > > >You may say thats its an invalid config line but the loader shouldnt > > > >blow up from it. Can this be fixed up somehow? > > > > no, this cannot be "fixed" because it is the user misprogramming > > the system, such as providing the wrong path to the kernel > > or writing a loop in /etc/rc.conf or a billion other ways. > > Yes, but you can copy /etc/defaults/rc.conf to /etc/rc.conf and things > still work. just because it contains only variable assignments, whereas the "assignments" in loader.conf have other side effects. However, I agree that a split of the content of loader.conf might make reduce the chance of mistakes. I'll look into this. > Ok, then loader_conf_files needs to be marked as special and not to be > overridden from /boot/defaults/loader.conf like all the other options. Unless i misunderstand what you say, this is already documented in loader.conf(5) cheers luigi From owner-freebsd-stable@FreeBSD.ORG Sun Jan 18 21:30: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 5F9B410656C0 for ; Sun, 18 Jan 2009 21:30:41 +0000 (UTC) (envelope-from jamesbrandongooch@gmail.com) Received: from mail-bw0-f10.google.com (mail-bw0-f10.google.com [209.85.218.10]) by mx1.freebsd.org (Postfix) with ESMTP id D6E048FC12 for ; Sun, 18 Jan 2009 21:30:40 +0000 (UTC) (envelope-from jamesbrandongooch@gmail.com) Received: by bwz3 with SMTP id 3so311230bwz.19 for ; Sun, 18 Jan 2009 13:30:39 -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=eTNoDCCuZYxmm7FxtlwrFgsaRKGAFYjQHbBob5vvz4Q=; b=aKldhlbg4YT61v7F3g1bCJM61E68VNYKuZc1A2SzCXZfCDJCDRHt1Vs9WfeyBocDJ0 SfQj+iZGw1orUyBS3VjxKiUJEetZx9tzF+0h4ocR+ifn3o72cuI9hKa9m/ej5iFQ9x2k P02EaT0ZxhBYohmA7IIcp1n5cbD+D1KmhYUuk= 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=x2JJoNci1YUSmi3iv4visFeSajiFJZNonw2JMclwqpjsXJY9g/udOMGtzIcZgznqag rh65SZ6d5CgYXSa8890CGtsmeEimopMq78jBvn7wi4PJXG4ywOMs3RUoBQJed3oi+m6D yFK0M4JbyaZsJrN3409py5z61MEljC9xbmmEo= Received: by 10.181.221.7 with SMTP id y7mr1777940bkq.195.1232309859091; Sun, 18 Jan 2009 12:17:39 -0800 (PST) Received: by 10.181.204.1 with HTTP; Sun, 18 Jan 2009 12:17:39 -0800 (PST) Message-ID: <179b97fb0901181217v475a4a6aw127634c4c472266@mail.gmail.com> Date: Sun, 18 Jan 2009 14:17:39 -0600 From: "Brandon Gooch" To: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: iwn driver on 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, 18 Jan 2009 21:30:41 -0000 I have a working driver for the Intel 4965, aka iwn(4), loaded on my Lenovo X300 running FreeBSD 7.1-RELEASE (amd64). This driver is a slightly-modified version of the iwn(4) driver backported from 8.0-CURRENT by Gavin Atkinson: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=221758+0+/usr/local/www/db/text/2008/freebsd-stable/20080928.freebsd-stable I was seeing the same symptoms described in these threads (among others): http://lists.freebsd.org/pipermail/freebsd-stable/2008-September/045264.html http://www.freebsd.org/cgi/getmsg.cgi?fetch=1334322+1338147+/usr/local/www/db/text/2009/freebsd-questions/20090118.freebsd-questions http://www.freebsd.org/cgi/getmsg.cgi?fetch=1418632+1421765+/usr/local/www/db/text/2009/freebsd-questions/20090118.freebsd-questions ...so I debugged and modified Gavin's driver for my system. The driver and the source tree diff can be downloaded here for any brave souls wanting to test it out: http://sites.google.com/site/bsdgooch/files I'm using the driver now to send this e-mail over a link to my TP-LINK TL-WR941ND access point (with WPA2). Feedback and bug reports would be useful. -brandon From owner-freebsd-stable@FreeBSD.ORG Sun Jan 18 21:55: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 6494F1065670 for ; Sun, 18 Jan 2009 21:55:20 +0000 (UTC) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1smout1.broadpark.no (osl1smout1.broadpark.no [80.202.4.58]) by mx1.freebsd.org (Postfix) with ESMTP id 239698FC13 for ; Sun, 18 Jan 2009 21:55:19 +0000 (UTC) (envelope-from torfinn.ingolfsen@broadpark.no) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=US-ASCII Received: from osl1sminn1.broadpark.no ([80.202.4.59]) by osl1smout1.broadpark.no (Sun Java(tm) System Messaging Server 6.3-3.01 (built Jul 12 2007; 32bit)) with ESMTP id <0KDO00GBASW6K750@osl1smout1.broadpark.no> for freebsd-stable@freebsd.org; Sun, 18 Jan 2009 22:55:18 +0100 (CET) Received: from kg-work2.kg4.no ([80.203.109.110]) by osl1sminn1.broadpark.no (Sun Java(tm) System Messaging Server 6.3-3.01 (built Jul 12 2007; 32bit)) with SMTP id <0KDO0001ESW6HVA0@osl1sminn1.broadpark.no> for freebsd-stable@freebsd.org; Sun, 18 Jan 2009 22:55:18 +0100 (CET) Date: Sun, 18 Jan 2009 22:55:18 +0100 From: Torfinn Ingolfsen To: freebsd-stable@freebsd.org Message-id: <20090118225518.63d6b8e8.torfinn.ingolfsen@broadpark.no> In-reply-to: <179b97fb0901181217v475a4a6aw127634c4c472266@mail.gmail.com> References: <179b97fb0901181217v475a4a6aw127634c4c472266@mail.gmail.com> X-Mailer: Sylpheed 2.6.0 (GTK+ 2.14.7; i386-portbld-freebsd7.1) X-Face: "t9w2,-X@O^I`jVW\sonI3.,36KBLZE*AL[y9lL[PyFD*r_S:dIL9c[8Y>V42R0"!"yb_zN,f#%.[PYYNq; m"_0v; ~rUM2Yy!zmkh)3&U|u!=T(zyv,MHJv"nDH>OJ`t(@mil461d_B'Uo|'nMwlKe0Mv=kvV?Nh@>Hb<3s_z2jYgZhPb@?Wi^x1a~Hplz1.zH Subject: Re: iwn driver on 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, 18 Jan 2009 21:55:20 -0000 On Sun, 18 Jan 2009 14:17:39 -0600 Brandon Gooch wrote: > I have a working driver for the Intel 4965, aka iwn(4), loaded on my > Lenovo X300 running FreeBSD 7.1-RELEASE (amd64). FWIW, I am using the latest perforce version of the iwn driver as documented here[1] on a ThinkPad T61 running FreeBSD 7.1-stable / i386 - no modifications necessary. It works great. I just use the p4fetch.rb script to get the driver. HTH References: 1) http://clearchain.com/wiki/iwn -- Regards, Torfinn Ingolfsen From owner-freebsd-stable@FreeBSD.ORG Sun Jan 18 22:10:31 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 D6C3110656FE; Sun, 18 Jan 2009 22:10:31 +0000 (UTC) (envelope-from me@janh.de) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.9]) by mx1.freebsd.org (Postfix) with ESMTP id 6C29C8FC32; Sun, 18 Jan 2009 22:10:30 +0000 (UTC) (envelope-from me@janh.de) Received: from janh.freebsd (e177246053.adsl.alicedsl.de [85.177.246.53]) by mrelayeu.kundenserver.de (node=mrelayeu7) with ESMTP (Nemesis) id 0ML2xA-1LOfqc0Jbi-0005aY; Sun, 18 Jan 2009 23:10:28 +0100 Message-ID: <4973A8CE.9060909@janh.de> Date: Sun, 18 Jan 2009 23:10:22 +0100 From: Jan Henrik Sylvester User-Agent: Thunderbird 2.0.0.19 (X11/20090115) MIME-Version: 1.0 To: stable-list freebsd References: 179b97fb0901181217v475a4a6aw127634c4c472266@mail.gmail.com Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX18CKTZojz4YIXT6O9czel6CXZbts86zweYZ7tW NkWkwMffKIUTOZLhhc2UujwnVWFOAXJHJDB7xcvxnknDUK/RXA fAc5fJ0rltEBV6DO8AZcQ== Cc: Brandon Gooch , Da Rock , questions-list freebsd Subject: Re: iwn driver on 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, 18 Jan 2009 22:10:32 -0000 Da Rock wrote: > On Sun, 2009-01-18 at 14:17 -0600, Brandon Gooch wrote: >> I have a working driver for the Intel 4965, aka iwn(4), loaded on my >> Lenovo X300 running FreeBSD 7.1-RELEASE (amd64). >> >> This driver is a slightly-modified version of the iwn(4) driver >> backported from 8.0-CURRENT by Gavin Atkinson: >> >> http://docs.freebsd.org/cgi/getmsg.cgi?fetch=221758+0+/usr/local/www/db/text/2008/freebsd-stable/20080928.freebsd-stable >> >> I was seeing the same symptoms described in these threads (among others): >> >> http://lists.freebsd.org/pipermail/freebsd-stable/2008-September/045264.html >> >> http://www.freebsd.org/cgi/getmsg.cgi?fetch=1334322+1338147+/usr/local/www/db/text/2009/freebsd-questions/20090118.freebsd-questions >> >> http://www.freebsd.org/cgi/getmsg.cgi?fetch=1418632+1421765+/usr/local/www/db/text/2009/freebsd-questions/20090118.freebsd-questions >> >> ...so I debugged and modified Gavin's driver for my system. >> >> The driver and the source tree diff can be downloaded here for any >> brave souls wanting to test it out: >> >> http://sites.google.com/site/bsdgooch/files >> >> I'm using the driver now to send this e-mail over a link to my TP-LINK >> TL-WR941ND access point (with WPA2). Feedback and bug reports would be >> useful. >> >> -brandon > > Sounds like you got to it before I did- thank god! :) > > Question though: have you got it figured for a channels yet? > > I'll test it for you and keep you updated with my results. Thanks for working on the driver! The only difference to the version of gavin that I could see is that the bands in iwn_bands that got commented out were brought back. Or did I miss something? Do you know why they were commented out and it was unnecessary? Or was it just to fix the crash? I did a few test runs: It does not crash immediately as the version from gavin, but the error I had with the perforce version iwn0: error, INTR=82000000 STATUS=0x10000 iwn0: iwn_config: could not set power mode, error 35 is there -- in 3 out of 3 tries. So nothing improved there. (I hit that error on first use in about 50% of the cases before.) Moreover, at 3 out of 4 tries to 'kldunload if_iwn' after hitting the error (after '/etc/rc.d/netif stop iwn0' and 'ifconfig iwn0 down'), there was a crash: 2 page faults and 1 freeze. I have not had that with the perforce version. (Maybe once long ago, but I think I forgot to stop iwn0 at that time.) The one time I actually got the (WPA2) connection up, I was able to transfer with a similar speed as with the perforce version. Thus, for me, there are no improvement over the (old) perforce version. Probably by chance, but I had more crashes. I think the thread on stable@ should rather be continued than the one on questions@, but since Da Rock answered on questions@, I reinclude both. Cheers, Jan Henrik From owner-freebsd-stable@FreeBSD.ORG Sun Jan 18 22:16: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 9C50A106566B for ; Sun, 18 Jan 2009 22:16:57 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from dhcp-172-28-76-187.eur.corp.google.com (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id EB4268FC21; Sun, 18 Jan 2009 22:16:37 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <4973AA3F.6090504@FreeBSD.org> Date: Sun, 18 Jan 2009 22:16:31 +0000 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) MIME-Version: 1.0 To: "L1NYX01D@GMAIL.COM" References: <54540134.20090112212757@gmail.com> In-Reply-To: <54540134.20090112212757@gmail.com> Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit 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: Sun, 18 Jan 2009 22:16:57 -0000 L1NYX01D@GOOGLEMAIL.COM wrote: > 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 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: >> kernel trap 12 with interrupts disabled >> >> >> 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) Looks likely to be a hardware fault, to me. Kris From owner-freebsd-stable@FreeBSD.ORG Sun Jan 18 22:24:41 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 9A1651065678 for ; Sun, 18 Jan 2009 22:24:41 +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 60F3C8FC16 for ; Sun, 18 Jan 2009 22:24:41 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 98AF97309E; Sun, 18 Jan 2009 23:29:58 +0100 (CET) Date: Sun, 18 Jan 2009 23:29:58 +0100 From: Luigi Rizzo To: stable@freebsd.org Message-ID: <20090118222958.GA32414@onelab2.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Cc: re@freebsd.org Subject: RFC: side effects of fixing loader_conf_files handling X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Jan 2009 22:24:42 -0000 hi, in some recent commits to HEAD and stable/7 i fixed the handling of loader_conf_files so that it behaves as always intended and documented in loader.conf(5): ... loader_conf_files Defines additional configuration files to be processed right after the present file. Previously, the check for new assignments was incorrect, and it happened to ignored assignments which did not result in a buffer reallocation by the Forth interpreter (essentially, any string not longer than the current one was ignored). An annoying side effect of the fix is that now people who (mistakenly) copied /boot/defaults/loader.conf into /boot/loader.conf (and possibly edit it), now create a loop because their /boot/loader.conf now contains loader_conf_files="/boot/device.hints /boot/loader.conf /boot/loader.conf.local" which is not just a pure assignments. Never mind the fact nobody ever recommended to copy the file and then modify the copy, there seem to be several people who do this (and do the same for /etc/defaults/rc.conf). I think we should remove the use of loader_conf_files=... from /boot/defaults/loader.conf, partly to prevent this kind of bugs, and partly because it is nice to have only "pure assigments" in this file. If there are no objections, i will look at how to do it. Probably this requires putting the initial list of files somewhere else, probably in /boot/loader.rc after the include /boot/loader.4th statement. Comments ? cheers luigi From owner-freebsd-stable@FreeBSD.ORG Sun Jan 18 22:34: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 5AD75106564A for ; Sun, 18 Jan 2009 22:34:10 +0000 (UTC) (envelope-from me@janh.de) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.9]) by mx1.freebsd.org (Postfix) with ESMTP id E55AC8FC18 for ; Sun, 18 Jan 2009 22:34:09 +0000 (UTC) (envelope-from me@janh.de) Received: from janh.freebsd (e177246053.adsl.alicedsl.de [85.177.246.53]) by mrelayeu.kundenserver.de (node=mrelayeu5) with ESMTP (Nemesis) id 0ML25U-1LOgDX0U0p-0000L5; Sun, 18 Jan 2009 23:34:08 +0100 Message-ID: <4973AE61.2040805@janh.de> Date: Sun, 18 Jan 2009 23:34:09 +0100 From: Jan Henrik Sylvester User-Agent: Thunderbird 2.0.0.19 (X11/20090115) MIME-Version: 1.0 To: Torfinn Ingolfsen References: 179b97fb0901181217v475a4a6aw127634c4c472266@mail.gmail.com Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX180awoqctSjFJt8YXzmdeV1cB1H1rFpgFN/qFD hkCxwX6zEw67t5A9hhJcHkWR2INxSYA7hHwNYS7VwJHIUZ/YRG yKvWPy2fTIKRWcnVH3nMg== Cc: Brandon Gooch , stable-list freebsd , Da Rock Subject: Re: iwn driver on 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, 18 Jan 2009 22:34:10 -0000 Torfinn Ingolfsen wrote: > On Sun, 18 Jan 2009 14:17:39 -0600 > Brandon Gooch wrote: > >> I have a working driver for the Intel 4965, aka iwn(4), loaded on my >> Lenovo X300 running FreeBSD 7.1-RELEASE (amd64). > > FWIW, I am using the latest perforce version of the iwn driver as > documented here[1] on a ThinkPad T61 running FreeBSD 7.1-stable / i386 - > no modifications necessary. It works great. > I just use the p4fetch.rb script to get the driver. > > HTH > > References: > 1) http://clearchain.com/wiki/iwn Since from that address, you are using the latest version of the benjsc perforce branch, you are probably using the same as I, since I took the initial version from the sam_vap branch (before vap got introduced). I do not know how far it is, but there is vap_releng7 in the sam perforce and projects/vap7 in svn on which Sam Leffler is actively working: http://lists.freebsd.org/pipermail/svn-src-projects/2009-January/thread.html I would like to have if_iwn working on a otherwise unmodified 7.1-RELEASE-pX and help to test it, but maybe waiting on sam to bring vap to 7 would be a better way to go. Cheers, Jan Henrik From owner-freebsd-stable@FreeBSD.ORG Mon Jan 19 00:05: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 443221065672; Mon, 19 Jan 2009 00:05:44 +0000 (UTC) (envelope-from jamesbrandongooch@gmail.com) Received: from mail-bw0-f10.google.com (mail-bw0-f10.google.com [209.85.218.10]) by mx1.freebsd.org (Postfix) with ESMTP id 020A38FC18; Mon, 19 Jan 2009 00:05:42 +0000 (UTC) (envelope-from jamesbrandongooch@gmail.com) Received: by bwz3 with SMTP id 3so435992bwz.19 for ; Sun, 18 Jan 2009 16:05:41 -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=hh8lNfpkt7q9yyO2C6ts5A/hV6sOPYNW0PuI18HFYTU=; b=YW56dlG+QK+zbZjk/REz52RaGvWjSYrVx1FVm2wGFg+fBiIe9bIFbnsOIPVsWujBrE DNuh4UKcchZ4j6YmMgNaGSBTpmaEF9jguRo0iwTzOKUfzE7dK6RmDi1q/h1oGf/+2Eir n5ll7z0yG0RiSdufAWVlmLmrUnBQoVaTO1OWs= 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=aEbj2nl4O8U438LSGAFqDv1fEMVUi1JoaBVtmgyCTxyYLcOgxJoYuASNxPFvsFaOPU Z0wq2ihJL2GUuGOKocMvwN2IqweXG8IG8rAgVu/BLKac5IbR2d4h9WnasPhxKyczwLNp KIuln7+YXhr8sL4kYd+gPSaE/5GVYLi8lwGZw= Received: by 10.181.239.8 with SMTP id q8mr473349bkr.109.1232323540922; Sun, 18 Jan 2009 16:05:40 -0800 (PST) Received: by 10.181.204.1 with HTTP; Sun, 18 Jan 2009 16:05:40 -0800 (PST) Message-ID: <179b97fb0901181605r56ec98f8g7aa31fa4a6e51e99@mail.gmail.com> Date: Sun, 18 Jan 2009 18:05:40 -0600 From: "Brandon Gooch" To: "Jan Henrik Sylvester" In-Reply-To: <4973A8CE.9060909@janh.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4973A8CE.9060909@janh.de> Cc: stable-list freebsd , Da Rock , questions-list freebsd Subject: Re: iwn driver on 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, 19 Jan 2009 00:05:45 -0000 The kernel panic was due to a NULL pointer dereference in the module. The code that was commented out created a situation in which the array of structs (line 2412): static const struct iwn_chan_band iwn_bands[] contained only 2 items. The code following the struct array that obtained the list of authorized channels: /* read the list of authorized channels */ for (i = 0; i < N(iwn_bands)-2; i++) iwn_read_eeprom_band(sc, &iwn_bands[i]); didn't actually get a list of anything, since N(iwn_bands)-2 evaluates to zero in this case. The NULL pointer part comes in when the call to ieee80211_sort_channels() on line 2436 sends a list of no items with a value of 0 for ic->ic_nchans. The backported insertion sort code from 8.0-CURRENT's 802.11 stack fails somewhere because of this value, due to access of some memory address in the chancompar() or swap(?) -- I didn't really dig that far into it. I guess the purpose of commenting out the A channels in the iwn_bands[] was to keep the driver from potentially using them, but honestly, I'm not sure if that's the appropriate way to do that (I'm just getting into this stuff). I'm sure the MFC'd VAP stuff that Sam Leffler is working on will alleviate all of this, but I wanted a working iwn(4) for now ;) On Sun, Jan 18, 2009 at 4:10 PM, Jan Henrik Sylvester wrote: > Da Rock wrote: >> >> On Sun, 2009-01-18 at 14:17 -0600, Brandon Gooch wrote: >>> >>> I have a working driver for the Intel 4965, aka iwn(4), loaded on my >>> Lenovo X300 running FreeBSD 7.1-RELEASE (amd64). >>> >>> This driver is a slightly-modified version of the iwn(4) driver >>> backported from 8.0-CURRENT by Gavin Atkinson: >>> >>> >>> http://docs.freebsd.org/cgi/getmsg.cgi?fetch=221758+0+/usr/local/www/db/text/2008/freebsd-stable/20080928.freebsd-stable >>> >>> I was seeing the same symptoms described in these threads (among others): >>> >>> >>> http://lists.freebsd.org/pipermail/freebsd-stable/2008-September/045264.html >>> >>> >>> http://www.freebsd.org/cgi/getmsg.cgi?fetch=1334322+1338147+/usr/local/www/db/text/2009/freebsd-questions/20090118.freebsd-questions >>> >>> >>> http://www.freebsd.org/cgi/getmsg.cgi?fetch=1418632+1421765+/usr/local/www/db/text/2009/freebsd-questions/20090118.freebsd-questions >>> >>> ...so I debugged and modified Gavin's driver for my system. >>> >>> The driver and the source tree diff can be downloaded here for any >>> brave souls wanting to test it out: >>> >>> http://sites.google.com/site/bsdgooch/files >>> >>> I'm using the driver now to send this e-mail over a link to my TP-LINK >>> TL-WR941ND access point (with WPA2). Feedback and bug reports would be >>> useful. >>> >>> -brandon >> >> Sounds like you got to it before I did- thank god! :) >> >> Question though: have you got it figured for a channels yet? >> >> I'll test it for you and keep you updated with my results. > > Thanks for working on the driver! > > The only difference to the version of gavin that I could see is that the > bands in iwn_bands that got commented out were brought back. Or did I miss > something? Do you know why they were commented out and it was unnecessary? > Or was it just to fix the crash? > > I did a few test runs: It does not crash immediately as the version from > gavin, but the error I had with the perforce version > iwn0: error, INTR=82000000 STATUS=0x10000 > iwn0: iwn_config: could not set power mode, error 35 > is there -- in 3 out of 3 tries. So nothing improved there. (I hit that > error on first use in about 50% of the cases before.) > > Moreover, at 3 out of 4 tries to 'kldunload if_iwn' after hitting the error > (after '/etc/rc.d/netif stop iwn0' and 'ifconfig iwn0 down'), there was a > crash: 2 page faults and 1 freeze. I have not had that with the perforce > version. (Maybe once long ago, but I think I forgot to stop iwn0 at that > time.) > > The one time I actually got the (WPA2) connection up, I was able to transfer > with a similar speed as with the perforce version. > > Thus, for me, there are no improvement over the (old) perforce version. > Probably by chance, but I had more crashes. > > I think the thread on stable@ should rather be continued than the one on > questions@, but since Da Rock answered on questions@, I reinclude both. > > Cheers, > Jan Henrik > From owner-freebsd-stable@FreeBSD.ORG Mon Jan 19 01:07:41 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 E71CA1065673 for ; Mon, 19 Jan 2009 01:07:41 +0000 (UTC) (envelope-from markir@paradise.net.nz) Received: from smtp3.clear.net.nz (smtp3.clear.net.nz [203.97.33.64]) by mx1.freebsd.org (Postfix) with ESMTP id B51748FC1A for ; Mon, 19 Jan 2009 01:07:41 +0000 (UTC) (envelope-from markir@paradise.net.nz) Received: from zmori.markir.net (121-73-173-247.dsl.telstraclear.net [121.73.173.247]) by smtp3.clear.net.nz (CLEAR Net Mail) with ESMTP id <0KDP00BHG13GPJ20@smtp3.clear.net.nz> for stable@freebsd.org; Mon, 19 Jan 2009 13:52:29 +1300 (NZDT) Date: Mon, 19 Jan 2009 13:52:27 +1300 From: Mark Kirkwood To: stable@freebsd.org Message-id: <4973CECB.20201@paradise.net.nz> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7bit User-Agent: Thunderbird 2.0.0.19 (X11/20090117) Cc: Subject: Sound only on 1 channel, plus other quirks post snd_hda import X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Jan 2009 01:07:42 -0000 I am running RELENG_7 from 12 Jan, I noticed that I am only getting sound on 1 channel. Also opening up "Volume Control" from Gnome and altering either of "Volume" or "PCM" produces crackles on the non functioning channel, and kills susbsequent sound output on either channel! (Just to be sure I tried the speakers out with another machine, and they work fine - both channels) I have hw.snd.maxautovchans=2 set in /etc/sysctl.conf - I'm wondering if that is wrong these days. $ dmesg|grep -i hda hdac0: mem 0xff5fc000-0xff5fffff irq 17 at device 1.0 on pci2 hdac0: HDA Driver Revision: 20081226_0122 hdac0: [ITHREAD] hdac0: HDA Codec #0: Analog Devices AD1986A hdac0: hdac_widget_connection_parse: nid=18 WARNING: zero cnid entnum=4 j=2 index=0 entries=8 found=2 res=0x21002211 pcm0: at cad 0 nid 1 on hdac0 pcm1: at cad 0 nid 1 on hdac0 hdac0: mem 0xff5fc000-0xff5fffff irq 17 at device 1.0 on pci2 hdac0: HDA Driver Revision: 20081226_0122 hdac0: [ITHREAD] hdac0: HDA Codec #0: Analog Devices AD1986A hdac0: hdac_widget_connection_parse: nid=18 WARNING: zero cnid entnum=4 j=2 index=0 entries=8 found=2 res=0x21002211 pcm0: at cad 0 nid 1 on hdac0 pcm1: at cad 0 nid 1 on hdac0 hdac0: mem 0xff5fc000-0xff5fffff irq 17 at device 1.0 on pci2 hdac0: HDA Driver Revision: 20081226_0122 hdac0: [ITHREAD] hdac0: HDA Codec #0: Analog Devices AD1986A hdac0: hdac_widget_connection_parse: nid=18 WARNING: zero cnid entnum=4 j=2 index=0 entries=8 found=2 res=0x21002211 pcm0: at cad 0 nid 1 on hdac0 pcm1: at cad 0 nid 1 on hdac0 From owner-freebsd-stable@FreeBSD.ORG Mon Jan 19 02:53:06 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 0B1DC106564A; Mon, 19 Jan 2009 02:53:06 +0000 (UTC) (envelope-from lists@pingle.org) Received: from willow.pingle.org (willow.pingle.org [68.76.213.30]) by mx1.freebsd.org (Postfix) with ESMTP id CB5DF8FC14; Mon, 19 Jan 2009 02:53:05 +0000 (UTC) (envelope-from lists@pingle.org) Received: from localhost (unknown [127.0.0.1]) by willow.pingle.org (Postfix) with ESMTP id D8B601145A; Sun, 18 Jan 2009 21:36:49 -0500 (EST) X-Virus-Scanned: amavisd-new at pingle.org Received: from willow.pingle.org ([127.0.0.1]) by localhost (willow.pingle.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gi7bef72TcGi; Sun, 18 Jan 2009 21:36:48 -0500 (EST) Received: from [192.168.10.22] (pool-72-69-73-198.chi01.dsl-w.verizon.net [72.69.73.198]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jim) by willow.pingle.org (Postfix) with ESMTPSA id 1E00011455; Sun, 18 Jan 2009 21:36:47 -0500 (EST) Message-ID: <4973E73E.6040805@pingle.org> Date: Sun, 18 Jan 2009 21:36:46 -0500 From: Jim Pingle User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Andrew Thompson References: <49729D80.8010506@charter.net> <20090118093346.GA9819@onelab2.iet.unipi.it> <49734D0B.8050604@charter.net> <20090118164724.GA21705@onelab2.iet.unipi.it> <20090118185605.GA28874@citylink.fud.org.nz> <497380BB.1050409@charter.net> <20090118200856.GA28366@onelab2.iet.unipi.it> <20090118201809.GA44812@citylink.fud.org.nz> In-Reply-To: <20090118201809.GA44812@citylink.fud.org.nz> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org, Luigi Rizzo Subject: Re: System borked: loader stack overflow. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Jan 2009 02:53:06 -0000 Andrew Thompson wrote: > Also an entry in UPDATING that a config error that was once harmless now > renders the system unbootable (without intervention). Would this also be something that mergemaster could check for and warn against? Jim From owner-freebsd-stable@FreeBSD.ORG Mon Jan 19 03:09: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 ECF311065673 for ; Mon, 19 Jan 2009 03:09:20 +0000 (UTC) (envelope-from pete@port2.altadena.net) Received: from port2.altadena.net (c-69-137-63-84.hsd1.md.comcast.net [69.137.63.84]) by mx1.freebsd.org (Postfix) with ESMTP id 9749A8FC14 for ; Mon, 19 Jan 2009 03:09:20 +0000 (UTC) (envelope-from pete@port2.altadena.net) Received: from port2.altadena.net (localhost [127.0.0.1]) by port2.altadena.net (8.14.3/8.13.1) with ESMTP id n0J2U5om002221 for ; Sun, 18 Jan 2009 21:30:05 -0500 (EST) (envelope-from pete@port2.altadena.net) Received: (from pete@localhost) by port2.altadena.net (8.14.3/8.13.1/Submit) id n0J2U5S5002220 for stable@freebsd.org; Sun, 18 Jan 2009 21:30:05 -0500 (EST) (envelope-from pete) Date: Sun, 18 Jan 2009 21:30:05 -0500 (EST) From: Pete Carah Message-Id: <200901190230.n0J2U5S5002220@port2.altadena.net> To: stable@freebsd.org Cc: Subject: Hangs, maybe a clue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Jan 2009 03:09:21 -0000 I've had some mysterious hangs which I notice that several others have too. Two of the machines in question are Soekris 4801's running as routers; this is hard to handle ddb with (though possible for one of them...) I started noticing this sometime in December. My laptop finally hung in a state where I could do a ps (waiting a long time for the response.) The strange and likely related to the hang was softdepflush in R state with 43 MINUTES of cpu. (the machine has been up maybe an hour.) This is 7.1-stable csup'd Jan 9. I'm backing up to Dec 1 since I didn't notice it (maybe just didn't notice?). The load average was about 10 but mostly that was lower-priority things ready but not run. -- Pete From owner-freebsd-stable@FreeBSD.ORG Mon Jan 19 03:26:31 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 4E56F106566B; Mon, 19 Jan 2009 03:26:31 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0708.google.com (rv-out-0708.google.com [209.85.198.249]) by mx1.freebsd.org (Postfix) with ESMTP id 0D8B38FC0A; Mon, 19 Jan 2009 03:26:30 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0708.google.com with SMTP id k29so2999335rvb.0 for ; Sun, 18 Jan 2009 19:26:30 -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=e9oYsE6cOZ2dKWZ6JcIUXWjz8jn3+fSo3xS1yJudCiI=; b=LJXZ53YYv0VAxH4D81JY1hHglkSPCrSPb/0Byp5POuRmqJN6tUeq4zpxwAxAnvftTo YPhh/ZLgv+YXkZYWOmors5r6TelWzgkBEG/PYCD6oWbqvrb4taRHcymlACVsusnjkDw7 O/q0ddw9oiO+saVYMI8b6jLtp9crLzHFoZbR8= 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=o4Rv7oEjjwFSZGiyrn5zmOazNB/XV6PoGmlR34DKkt8WGEdS3JBtuzZDTct/HEYEi4 FRQhVGVThizU1NHAgrO47sGEdX54tKbhZPEyOFsiBH6Mo8xL7Y9VEeK1/dX/DSRhGnJ4 xcTKvyAqQ0deGapk19lI2lc3gSw+dSaIG4pT0= Received: by 10.141.128.19 with SMTP id f19mr1061398rvn.9.1232335590423; Sun, 18 Jan 2009 19:26:30 -0800 (PST) Received: from michelle.cdnetworks.co.kr ([211.53.35.84]) by mx.google.com with ESMTPS id g31sm8967768rvb.4.2009.01.18.19.26.27 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 18 Jan 2009 19:26:28 -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 n0J3QNV1076292 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 19 Jan 2009 12:26:23 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.14.3/8.14.3/Submit) id n0J3QKIX076291; Mon, 19 Jan 2009 12:26:20 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Mon, 19 Jan 2009 12:26:19 +0900 From: Pyun YongHyeon To: Dimitry Andric Message-ID: <20090119032619.GD75541@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> <20090117045423.GC68290@cdnetworks.co.kr> <49720FA5.6060508@andric.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49720FA5.6060508@andric.com> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@FreeBSD.org, Jung-uk Kim , 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: Mon, 19 Jan 2009 03:26:31 -0000 On Sat, Jan 17, 2009 at 06:04:37PM +0100, Dimitry Andric wrote: > 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. Thanks for testing. But the patch does not have any changes to fix your intitial setup time issue. If the patch has any effects on the issue it's a luck, I guess. -- Regards, Pyun YongHyeon From owner-freebsd-stable@FreeBSD.ORG Mon Jan 19 04:14:26 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 D2CCA1065670 for ; Mon, 19 Jan 2009 04:14:26 +0000 (UTC) (envelope-from markir@paradise.net.nz) Received: from smtp3.clear.net.nz (smtp3.clear.net.nz [203.97.33.64]) by mx1.freebsd.org (Postfix) with ESMTP id 9EB968FC0A for ; Mon, 19 Jan 2009 04:14:26 +0000 (UTC) (envelope-from markir@paradise.net.nz) Received: from zmori.markir.net (121-73-174-235.dsl.telstraclear.net [121.73.174.235]) by smtp3.clear.net.nz (CLEAR Net Mail) with ESMTP id <0KDP001OCAFVN700@smtp3.clear.net.nz> for stable@freebsd.org; Mon, 19 Jan 2009 17:14:19 +1300 (NZDT) Date: Mon, 19 Jan 2009 17:14:18 +1300 From: Mark Kirkwood In-reply-to: <4973CECB.20201@paradise.net.nz> To: stable@freebsd.org Message-id: <4973FE1A.9040709@paradise.net.nz> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7bit References: <4973CECB.20201@paradise.net.nz> User-Agent: Thunderbird 2.0.0.19 (X11/20090117) Cc: Subject: Re: Sound only on 1 channel, plus other quirks post snd_hda import X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Jan 2009 04:14:27 -0000 Mark Kirkwood wrote: > I am running RELENG_7 from 12 Jan, I noticed that I am only getting > sound on 1 channel. Also opening up "Volume Control" from Gnome and > altering either of "Volume" or "PCM" produces crackles on the non > functioning channel, and kills susbsequent sound output on either > channel! > > > I have hw.snd.maxautovchans=2 set in /etc/sysctl.conf - I'm wondering > if that is wrong these days. > > Removing this makes no difference. Also here is output from /dev/sndstat: FreeBSD Audio Driver (newpcm: 32bit 2007061600/i386) Installed devices: pcm0: at cad 0 nid 1 on hdac0 kld snd_hda [MPSAFE] (1p:1v/1r:1v channels duplex default) pcm1: at cad 0 nid 1 on hdac0 kld snd_hda [MPSAFE] (1p:1v/0r:0v channels) regards Mark From owner-freebsd-stable@FreeBSD.ORG Mon Jan 19 08:31:37 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 DB8C41065672 for ; Mon, 19 Jan 2009 08:31:37 +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 899208FC50 for ; Mon, 19 Jan 2009 08:31:37 +0000 (UTC) (envelope-from admin@kkip.pl) Received: from admin.admin.lan.kkip.pl ([10.66.3.254]) by mainframe.kkip.pl with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LOpXh-0001A3-2E; Mon, 19 Jan 2009 09:31:35 +0100 Message-ID: <49743A68.3020305@kkip.pl> Date: Mon, 19 Jan 2009 09:31:36 +0100 From: Bartosz Stec User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: pyunyh@gmail.com References: <8dfae1c10901070639x67945324jeeecfcac647d7976@mail.gmail.com> <496DF428.6050800@kkip.pl> <20090117044545.GA68290@cdnetworks.co.kr> In-Reply-To: <20090117044545.GA68290@cdnetworks.co.kr> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated-User: admin@kkip.pl X-Authenticator: plain X-Sender-Verify: SUCCEEDED (sender exists & accepts mail) X-Spam-Score: -8.9 X-Spam-Score-Int: -88 X-Exim-Version: 4.69 (build at 14-Jan-2009 11:48:13) X-Date: 2009-01-19 09:31:35 X-Connected-IP: 10.66.3.254:1515 X-Message-Linecount: 56 X-Body-Linecount: 42 X-Message-Size: 2337 X-Body-Size: 1694 X-Received-Count: 1 X-Recipient-Count: 2 X-Local-Recipient-Count: 2 X-Local-Recipient-Defer-Count: 0 X-Local-Recipient-Fail-Count: 0 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 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jan 2009 08:31:38 -0000 Pyun YongHyeon pisze: > 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: 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? > > I could test patch today BUT I made machine restart a couple of hours after NIC problem occurs (just to be sure) and after reboot re0 starts working OK until now. So maybe it was re0 problem or maybe it was something else. Even so, should I apply patch and report if NIC works? -- Bartosz Stec From owner-freebsd-stable@FreeBSD.ORG Mon Jan 19 08:46:57 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 856691065673 for ; Mon, 19 Jan 2009 08:46:57 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.236]) by mx1.freebsd.org (Postfix) with ESMTP id 4C67E8FC1C for ; Mon, 19 Jan 2009 08:46:57 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so2641240rvf.43 for ; Mon, 19 Jan 2009 00:46:56 -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=YiibezDE7NHo5odwdO7wDMZ3Gq9Q9j7MbNxbJEdtmLg=; b=SW0WoXjzPXQIosp8BEYE7VPZyf6jkJeMRRhW0rXEzjxvOJTbion5nVqAZJBjD4erne 27VhhTdctEh2DOXTBgOMmLtXo64GGMujDTekc0OZke1Cl+bRh8ZV/vT/qnkkbGH+WaEu f501T1sueHsopA4lAHUXi1Q7F8m3TnRcRMoIw= 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=rEjF6qlTN9/FDGCsDoxvHGAJ7RjNmNeDyWUoJn7VpMTvdjrOKTUPH/mEV+lBA/UEw+ ExvzdWKIIU/sp/LAYOvmeADSQnNDzILNaAkFmr7++njhFffHeCW4VcEDrbybPYDLRwzX i/4j3YqvK+JD7WouAqo+o2p46WHjlF+GN+TD0= Received: by 10.140.187.10 with SMTP id k10mr267238rvf.264.1232354816887; Mon, 19 Jan 2009 00:46:56 -0800 (PST) Received: from michelle.cdnetworks.co.kr ([211.53.35.84]) by mx.google.com with ESMTPS id b39sm4234405rvf.0.2009.01.19.00.46.54 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 19 Jan 2009 00:46:55 -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 n0J8korM077164 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 19 Jan 2009 17:46:50 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.14.3/8.14.3/Submit) id n0J8kovE077163; Mon, 19 Jan 2009 17:46:50 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Mon, 19 Jan 2009 17:46:50 +0900 From: Pyun YongHyeon To: Bartosz Stec Message-ID: <20090119084650.GG75541@cdnetworks.co.kr> References: <8dfae1c10901070639x67945324jeeecfcac647d7976@mail.gmail.com> <496DF428.6050800@kkip.pl> <20090117044545.GA68290@cdnetworks.co.kr> <49743A68.3020305@kkip.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49743A68.3020305@kkip.pl> 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: Mon, 19 Jan 2009 08:46:58 -0000 On Mon, Jan 19, 2009 at 09:31:36AM +0100, Bartosz Stec wrote: > Pyun YongHyeon pisze: > >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: 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? > > > > > I could test patch today BUT I made machine restart a couple of hours > after NIC problem occurs (just to be sure) and after reboot re0 starts > working OK until now. > So maybe it was re0 problem or maybe it was something else. Even so, > should I apply patch and report if NIC works? > Yes, I'd like to see how the patch works on your box. Due to instability of memory register mapping on RTL8169SC, I'd like to make re(4) use io register mapping on RTL8169SC. -- Regards, Pyun YongHyeon From owner-freebsd-stable@FreeBSD.ORG Mon Jan 19 09:21: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 90F54106564A for ; Mon, 19 Jan 2009 09:21:22 +0000 (UTC) (envelope-from victor@bsdes.net) Received: from alf.bsdes.net (244.Red-217-126-240.staticIP.rima-tde.net [217.126.240.244]) by mx1.freebsd.org (Postfix) with ESMTP id 398F88FC20 for ; Mon, 19 Jan 2009 09:21:21 +0000 (UTC) (envelope-from victor@bsdes.net) Received: by alf.bsdes.net (Postfix, from userid 1001) id 4D2BF11A2AE; Mon, 19 Jan 2009 10:21:20 +0100 (CET) Date: Mon, 19 Jan 2009 10:21:20 +0100 From: Victor Balada Diaz To: Dan Langille Message-ID: <20090119092119.GC4881@alf.bsdes.net> References: <496D374A.3020704@langille.org> <496E9A37.20800@langille.org> <496EA339.6010808@ksu.ru> <496EB43A.8010805@langille.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <496EB43A.8010805@langille.org> User-Agent: Mutt/1.4.2.3i Cc: "Marat N.Afanasyev" , 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jan 2009 09:21:22 -0000 On Wed, Jan 14, 2009 at 10:57:46PM -0500, Dan Langille wrote: > Marat N.Afanasyev 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 I also have the same problem with various machines at hetzner.de. The motherboard is: smbios.planar.maker="MICRO-STAR INTERANTIONAL CO.,LTD" smbios.planar.product="MS-7368" mbios.bios.reldate="10/31/2007" smbios.bios.version="V1.5B2" I've been trying to find a solution for this for some months, but so far i've been unable to find anything. This problem is poping up in the lists every few months. I tried asking for help on how to debug this at least twice but i didn't get much help with it. Looking at the archives this is the most interesting things i could find: http://lists.freebsd.org/pipermail/freebsd-acpi/2008-September/005127.html and http://unix.derkeiler.com/Mailing-Lists/FreeBSD/current/2003-09/0574.html The former seems to be totally related and suggests using KTR to debug it. The second have some info about how did Bruce Evans debug some ATA interrupt problems. I don't know if it could be related or not, but at least gives me some ideas on what to look at when debugging it. If anyone have any idea on how could i debug this or patches to test i can try them. Regards. -- La prueba más fehaciente de que existe vida inteligente en otros planetas, es que no han intentado contactar con nosotros. From owner-freebsd-stable@FreeBSD.ORG Mon Jan 19 09:55: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 C05D4106566B for ; Mon, 19 Jan 2009 09:55:52 +0000 (UTC) (envelope-from eriam@mediavirtuel.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 85B828FC0C for ; Mon, 19 Jan 2009 09:55:52 +0000 (UTC) (envelope-from eriam@mediavirtuel.com) Received: by yx-out-2324.google.com with SMTP id 8so1073026yxb.13 for ; Mon, 19 Jan 2009 01:55:51 -0800 (PST) MIME-Version: 1.0 Received: by 10.100.136.15 with SMTP id j15mr1031407and.11.1232351105262; Sun, 18 Jan 2009 23:45:05 -0800 (PST) In-Reply-To: <179b97fb0901181217v475a4a6aw127634c4c472266@mail.gmail.com> References: <179b97fb0901181217v475a4a6aw127634c4c472266@mail.gmail.com> Date: Mon, 19 Jan 2009 08:45:05 +0100 Message-ID: From: Eriam Schaffter To: Brandon Gooch Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: iwn driver on 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, 19 Jan 2009 09:55:53 -0000 2009/1/18 Brandon Gooch > I have a working driver for the Intel 4965, aka iwn(4), loaded on my > Lenovo X300 running FreeBSD 7.1-RELEASE (amd64). > Wonderfull to say the least ! Seeing that you run successfully 7.1 on a X300 is excellent ! Did you manage to get suspend/resume aka hibernation working somehow ? Thanks Eriam From owner-freebsd-stable@FreeBSD.ORG Mon Jan 19 11:39:12 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 1D89D1065675; Mon, 19 Jan 2009 11:39:12 +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 D71DE8FC13; Mon, 19 Jan 2009 11:39:11 +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 1LOsTE-000OpF-Tq; Mon, 19 Jan 2009 11:39:08 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LOsTE-000N7h-SL; Mon, 19 Jan 2009 11:39:08 +0000 To: dchagin@freebsd.org In-Reply-To: <20090116180941.GA26226@dchagin.dialup.corbina.ru> Message-Id: From: Pete French Date: Mon, 19 Jan 2009 11:39:08 +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, 19 Jan 2009 11:39:12 -0000 > yes, do ps - threads in state L or LL and RUN are especially interesting, > trace of pids 28, 27, and threads wich L on locked chan. heres the output of alllocks, http://toybox.twisted.org.uk/~pete/71_show_alllocks.png here are the pages of PS: http://toybox.twisted.org.uk/~pete/71_lock_ps2/ (next time I boot this I will disable http to avoid getting so many) I cant see any which are in L, LL or RUN state there though. A few RL and WL towards the end. Traces on 28 and 27 are here: http://toybox.twisted.org.uk/~pete/71_trace_28.png http://toybox.twisted.org.uk/~pete/71_trace_27a.png http://toybox.twisted.org.uk/~pete/71_trace_27b.png I also did traces on 19 and 16 as (like 28 and 27) they are in a "CPU" state, so may be of interest ? http://toybox.twisted.org.uk/~pete/71_trace_19.png http://toybox.twisted.org.uk/~pete/71_trace_16.png -pete. From owner-freebsd-stable@FreeBSD.ORG Mon Jan 19 13:25: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 8A2BF1065672 for ; Mon, 19 Jan 2009 13:25:14 +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 3F1318FC17 for ; Mon, 19 Jan 2009 13:25:13 +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 E16D848078; Mon, 19 Jan 2009 16:25:11 +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 1577441590; Mon, 19 Jan 2009 16:25:11 +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 n0JDPBvg006882; Mon, 19 Jan 2009 16:25:11 +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 n0JDP4mT006881; Mon, 19 Jan 2009 16:25:04 +0300 (MSK) (envelope-from root) Date: Mon, 19 Jan 2009 16:25:04 +0300 From: Chagin Dmitry To: Pete French Message-ID: <20090119132504.GA6853@dchagin.dialup.corbina.ru> References: <20090116180941.GA26226@dchagin.dialup.corbina.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) 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, 19 Jan 2009 13:25:14 -0000 On Mon, Jan 19, 2009 at 11:39:08AM +0000, Pete French wrote: > > yes, do ps - threads in state L or LL and RUN are especially interesting, > > trace of pids 28, 27, and threads wich L on locked chan. > > heres the output of alllocks, > > http://toybox.twisted.org.uk/~pete/71_show_alllocks.png > > here are the pages of PS: > > http://toybox.twisted.org.uk/~pete/71_lock_ps2/ > > (next time I boot this I will disable http to avoid getting so many) > > I cant see any which are in L, LL or RUN state there though. A few RL > and WL towards the end. Traces on 28 and 27 are here: > > http://toybox.twisted.org.uk/~pete/71_trace_28.png > http://toybox.twisted.org.uk/~pete/71_trace_27a.png > http://toybox.twisted.org.uk/~pete/71_trace_27b.png > > I also did traces on 19 and 16 as (like 28 and 27) they are in a "CPU" > state, so may be of interest ? > > http://toybox.twisted.org.uk/~pete/71_trace_19.png > http://toybox.twisted.org.uk/~pete/71_trace_16.png > Probably it is your case, try please. http://www.freebsd.org/cgi/query-pr.cgi?pr=130652&cat= -- Have fun! chd From owner-freebsd-stable@FreeBSD.ORG Mon Jan 19 13:34: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 3C202106566B; Mon, 19 Jan 2009 13:34: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 02E368FC12; Mon, 19 Jan 2009 13:34: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 ) id 1LOuGG-000Psa-3X; Mon, 19 Jan 2009 13:33:52 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LOuGG-000NW3-1y; Mon, 19 Jan 2009 13:33:52 +0000 To: dchagin@freebsd.org In-Reply-To: <20090119132504.GA6853@dchagin.dialup.corbina.ru> Message-Id: From: Pete French Date: Mon, 19 Jan 2009 13:33:52 +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, 19 Jan 2009 13:34:02 -0000 > Probably it is your case, try please. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=130652&cat= OK, will give this a try, unless anyone else wants any traces from this locked machine ? Is there a known way to tickle this bug when I've rebooted, to make sure it's fixed ? thanks, -pete. From owner-freebsd-stable@FreeBSD.ORG Mon Jan 19 13:40: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 915C3106566B; Mon, 19 Jan 2009 13:40:03 +0000 (UTC) (envelope-from pete@altadena.net) Received: from kestrel.altadena.net (kestrel.altadena.net [207.136.131.34]) by mx1.freebsd.org (Postfix) with ESMTP id 7730F8FC12; Mon, 19 Jan 2009 13:40:03 +0000 (UTC) (envelope-from pete@altadena.net) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=1.kestrel; d=altadena.net; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:X-Enigmail-Version:Content-Type:Content-Transfer-Encoding; b=F2cUkSrNWO9KtAbnRfxQHn7XUpBrlD1c+EehPSTUW137dGi8WHVK330RCNBpibe5Rjtg3b9Hs4MljngAY+mnAqHjgdW4/ORsvw36DWt6V+Z86Xx+0fPhBlHiuIY+9/ukZwe7DEk1DYD9krCcitwgHU7fqOxtt6bGok9Jn/knq1c=; Received: from c-69-137-63-84.hsd1.md.comcast.net ([69.137.63.84] helo=port3.altadena.net) by kestrel.altadena.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1LOu7G-000O2E-CQ; Mon, 19 Jan 2009 05:24:34 -0800 Message-ID: <49747F10.7050801@altadena.net> Date: Mon, 19 Jan 2009 08:24:32 -0500 From: Pete Carah User-Agent: Thunderbird 2.0.0.19 (X11/20090111) To: Kris Kennaway X-Enigmail-Version: 0.95.6 Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 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, 19 Jan 2009 13:40:03 -0000 Kris writes: > You and anyone else seeing performance problems should try to work > through the advice given here: > [1]http://people.freebsd.org/~kris/scaling/Help_my_system_is_slow.pdf Well, all the people in this thread have noticed that WITH NO CONFIG CHANGES f rom configs that worked fine in the past, their systems are very slow and/or locking up (mi ne are both) with the stable branch sometime (I noticed it sometime in December, but it got worse with the release.) Most were OK in October; mine (I think) were OK in late November - may narrow t hings down? Two of my systems that lock up have no internal visibility when they do (Soekris 4801's r outing; the only time-intensive things running are routing (done in irq context) and pflog. The se run with 60+ meg ram free.) These are complete lockups, though I did manage to get a ps out of my laptop last night by waiting 20 _minutes_ for it to start (!). This is not a generic perfo rmance problem. The laptop had 55 minutes of cpu time in the softdepflush thread after being up about an h our and 10 mins; this might give a hint. I didn't spot LL/RL state threads at the same time bec ause I didn't know to. Now I do. BTW - the same ps showed 8 or so user-space procs in R state wi th NO cpu time; the kernel was hogging all of it for over an hour. Firefox did indeed trigger this one as someone else noted. A soekris doing onl y routing+nat has no such excuse... At least PHK was nice enough to note the watchdog in another thread :-) -- Pete References 1. http://people.freebsd.org/%7Ekris/scaling/Help_my_system_is_slow.pdf From owner-freebsd-stable@FreeBSD.ORG Mon Jan 19 15:20: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 5A83A106566B; Mon, 19 Jan 2009 15: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 1FFF68FC14; Mon, 19 Jan 2009 15:20:12 +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 1LOvv3-0000ts-CY; Mon, 19 Jan 2009 15:20:05 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LOvv3-000Nvk-B1; Mon, 19 Jan 2009 15:20:05 +0000 To: dchagin@freebsd.org In-Reply-To: <20090119132504.GA6853@dchagin.dialup.corbina.ru> Message-Id: From: Pete French Date: Mon, 19 Jan 2009 15:20:05 +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, 19 Jan 2009 15:20:14 -0000 > Probably it is your case, try please. > http://www.freebsd.org/cgi/query-pr.cgi?pr=130652&cat= Well, I have been running this for a while now. I still get this: http://toybox.twisted.org.uk/~pete/71_lor3.png On the console, but so far the machine has not crashed. Obviously it's only been an hour or so as yet, buit given that it was freezing in about 5 minutes earlier this morning it does look good. So thanks for a good patch so far ;-) -pete. From owner-freebsd-stable@FreeBSD.ORG Mon Jan 19 16:08: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 D3ABE10656EC; Mon, 19 Jan 2009 16:08: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 98FAC8FC1F; Mon, 19 Jan 2009 16:08: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 1LOwg6-0001YY-9h; Mon, 19 Jan 2009 16:08:42 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LOwg6-000O7T-89; Mon, 19 Jan 2009 16:08:42 +0000 To: dchagin@freebsd.org In-Reply-To: <20090119132504.GA6853@dchagin.dialup.corbina.ru> Message-Id: From: Pete French Date: Mon, 19 Jan 2009 16:08:42 +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, 19 Jan 2009 16:08:45 -0000 > http://www.freebsd.org/cgi/query-pr.cgi?pr=130652&cat= Looks like I spoke too soon - It just locked up again I am afraid. Sitting there now at the debug prompt. It does, however, look very different this time: For example here is 'show alllocks': http://toybox.twisted.org.uk/~pete/71_alllocks2.png That shows a lot of locks in UDP - is this the kind of thing you were worried about Robert ? When I do a 'ps' there are, this time, a number of processes in the 'LL' and 'L' state. The images of the 'ps' and the traces or those locked processed are to be found here: http://toybox.twisted.org.uk/~pete/71_lock_ps3/ I tried to keep the threads which belong to each process together. What else can I get out of this lockup ? It looks like the most promising so far... -pete. From owner-freebsd-stable@FreeBSD.ORG Mon Jan 19 16:20: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 D267E10656C4; Mon, 19 Jan 2009 16:20:15 +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 9576B8FC0C; Mon, 19 Jan 2009 16:20: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 ) id 1LOwrE-0001g5-Cb; Mon, 19 Jan 2009 16:20:12 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LOwrE-000OAg-Ag; Mon, 19 Jan 2009 16:20:12 +0000 To: rwatson@FreeBSD.org In-Reply-To: Message-Id: From: Pete French Date: Mon, 19 Jan 2009 16:20:12 +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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jan 2009 16:20:16 -0000 > 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 Given that the latest lockup (see other email) has lots of locks in the UDP code, would you like me to try this next ? The kernel which has just locked is one using Dimtry's patch from http://www.freebsd.org/cgi/query-pr.cgi?pr=130652 I am not sure why that would give me different traces during the lockup though. I was doing a lot more TCP traffic this time, but that shouldnt interfere with UDP should it ? -pete. From owner-freebsd-stable@FreeBSD.ORG Mon Jan 19 16:49: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 175101065672 for ; Mon, 19 Jan 2009 16:49:06 +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 9EBA48FC1F for ; Mon, 19 Jan 2009 16:49:06 +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 1LOxJ8-000DLf-U0; Mon, 19 Jan 2009 17:49:02 +0100 Message-ID: <4974AF5B.9050505@holzleiter.name> Date: Mon, 19 Jan 2009 17:50:35 +0100 From: Sascha Holzleiter User-Agent: Thunderbird 2.0.0.18 (X11/20081126) 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 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, 19 Jan 2009 16:49:07 -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: 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. > > > > It seems that RTL8169SC does not like memory mapping. Instead of > using io mapping for all revisions, how about attached patch? I updated the source to stable and applied your patch which seems to fix the stable code for me. I still have instant DHCP discovery and the interface is running smoothly. I could transfer a 500M file without problems so connectivity seems to be stable with this patch. Thanks, Sascha From owner-freebsd-stable@FreeBSD.ORG Mon Jan 19 17:45: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 F3EED106564A for ; Mon, 19 Jan 2009 17:45:08 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id C385A8FC24 for ; Mon, 19 Jan 2009 17:45:08 +0000 (UTC) (envelope-from sam@freebsd.org) 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 n0JHDNC2059224 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 19 Jan 2009 09:13:23 -0800 (PST) (envelope-from sam@freebsd.org) Message-ID: <4974B4B2.5020308@freebsd.org> Date: Mon, 19 Jan 2009 09:13:22 -0800 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.18 (X11/20081209) MIME-Version: 1.0 To: Jan Henrik Sylvester References: 179b97fb0901181217v475a4a6aw127634c4c472266@mail.gmail.com <4973AE61.2040805@janh.de> In-Reply-To: <4973AE61.2040805@janh.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC-sonic.net-Metrics: ebb.errno.com; whitelist Cc: stable-list freebsd Subject: Re: iwn driver on 7.1 [no vaps in RELENG_7] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jan 2009 17:45:11 -0000 Jan Henrik Sylvester wrote: > Torfinn Ingolfsen wrote: >> On Sun, 18 Jan 2009 14:17:39 -0600 >> Brandon Gooch wrote: >> >>> I have a working driver for the Intel 4965, aka iwn(4), loaded on my >>> Lenovo X300 running FreeBSD 7.1-RELEASE (amd64). >> >> FWIW, I am using the latest perforce version of the iwn driver as >> documented here[1] on a ThinkPad T61 running FreeBSD 7.1-stable / i386 - >> no modifications necessary. It works great. >> I just use the p4fetch.rb script to get the driver. >> >> HTH >> >> References: >> 1) http://clearchain.com/wiki/iwn > > Since from that address, you are using the latest version of the > benjsc perforce branch, you are probably using the same as I, since I > took the initial version from the sam_vap branch (before vap got > introduced). > > I do not know how far it is, but there is vap_releng7 in the sam > perforce and projects/vap7 in svn on which Sam Leffler is actively > working: > http://lists.freebsd.org/pipermail/svn-src-projects/2009-January/thread.html > > > I would like to have if_iwn working on a otherwise unmodified > 7.1-RELEASE-pX and help to test it, but maybe waiting on sam to bring > vap to 7 would be a better way to go. vaps will never be committed to RELENG_7 due to API/ABI constraints. However that svn branch is operational and being maintained as it's used by multiple people. I considered bringing back iwn (it's just copying the bits); will add it to my TODO list. OTOH iwn is now out of date and someone needs to update it. There's newer firmware that is supposed to fix many of the bugs I hit when I worked on the driver (and Intel refused to acknowledge) and obsd has added support for newer parts that people want. It'd be great if someone wanted to take over this driver. Sam From owner-freebsd-stable@FreeBSD.ORG Mon Jan 19 19:24:12 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 E6DCA106566B for ; Mon, 19 Jan 2009 19:24:12 +0000 (UTC) (envelope-from ubm@u-boot-man.de) Received: from mail.upper.net (mail.upper.net [62.75.224.33]) by mx1.freebsd.org (Postfix) with ESMTP id 8CEE38FC08 for ; Mon, 19 Jan 2009 19:24:10 +0000 (UTC) (envelope-from ubm@u-boot-man.de) Received: from ubm.mine.nu (mail.upper.net [62.75.224.33]) (authenticated bits=0) by mail.upper.net (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id n0JJDrUP005672 for ; Mon, 19 Jan 2009 20:13:54 +0100 Received: from ubm.mine.nu ([85.181.0.109] helo=ubm.mine.nu) by ASSP.nospam; 19 Jan 2009 20:13:53 +0100 Date: Mon, 19 Jan 2009 20:13:51 +0100 From: Marc "UBM" Bocklet To: freebsd-stable@freebsd.org Message-Id: <20090119201351.ac77e1f9.ubm@u-boot-man.de> X-Mailer: Sylpheed 2.6.0 (GTK+ 2.12.10; i386-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: problems with sata disks (taskqueue timeout) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Jan 2009 19:24:13 -0000 Hiho! :-) Occasionally, especially when uploading a large number of files, the (brand-new, tested) sata disks in my fileserver spit out some of these errors: ----------------------- Jan 19 19:51:14 hamstor kernel: ad10: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=882778752 Jan 19 19:51:23 hamstor kernel: ad10: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly Jan 19 19:51:27 hamstor kernel: ad10: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly Jan 19 19:51:31 hamstor kernel: ad10: WARNING - SETFEATURES ENABLE WCACHE taskqueue timeout - completing request directly Jan 19 19:51:35 hamstor kernel: ad10: WARNING - SET_MULTI taskqueue timeout - completing request directly Jan 19 19:51:35 hamstor kernel: ad10: TIMEOUT - WRITE_DMA48 retrying (0 retries left) LBA=882778752 Jan 19 19:51:35 hamstor kernel: ad10: FAILURE - WRITE_DMA48 status=ff error=ff LBA=882778752 Jan 19 19:51:35 hamstor root: ZFS: vdev I/O failure, zpool=gedaerm path=/dev/ad10 offset=451982655488 size=131072 error=5 Jan 19 19:51:41 hamstor kernel: ad10: FAILURE - SET_MULTI status=51 error=4 Jan 19 19:51:41 hamstor kernel: ad10: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=882779008 Jan 19 19:51:41 hamstor kernel: ad10: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=882779008 Jan 19 19:51:50 hamstor kernel: ad10: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly Jan 19 19:51:54 hamstor kernel: ad10: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly Jan 19 19:51:58 hamstor kernel: ad10: WARNING - SETFEATURES ENABLE WCACHE taskqueue timeout - completing request directly Jan 19 19:52:02 hamstor kernel: ad10: WARNING - SET_MULTI taskqueue timeout - completing request directly Jan 19 19:52:02 hamstor kernel: ad10: FAILURE - WRITE_DMA48 timed out LBA=882779008 Jan 19 19:52:02 hamstor root: ZFS: vdev I/O failure, zpool=gedaerm path=/dev/ad10 offset=451982786560 size=131072 error=5 ----------------------- I've fiddled with the cables, which seemed to help, but I've been unable to completely eliminate the errors. The disks are two Western Digital MyBooks Home Edition (1 TB per disk), connected to a Promise TX 4 SATA Controller: atapci0@pci0:1:6:0: class=0x018000 card=0x3d17105a chip=0x3d17105a rev=0x02 hdr=0x00 vendor = 'Promise Technology Inc' device = 'PDC40718-GP SATA 300 TX4 Controller' class = mass storage They're connected via 50cm esata cables. I've googled on the net and found some vague hints about problems with the Promise TX4, but nothing concrete. What I've found is http://wiki.freebsd.org/JeremyChadwick/ATA_issues_and_troubleshooting basically telling me "these things happen, deal with it" :-) The problem is, I cannot produce these problems reliably, only thing I notice is that they *seem* to happen more often if a lot of large files are copied in succession. Can anybody tell me if upgrading to 7.2 oder -current will help? I'm currently running 7.0-STABLE-200804 FreeBSD 7.0-STABLE-200804 #0: Wed Dec 10 15:29:03 CET 2008 ***@host:/usr/obj/usr/src/sys/GENERIC amd64 Next step I'll try is upgrading to RELENG_7 to see if that helps. Greetings, Marc From owner-freebsd-stable@FreeBSD.ORG Mon Jan 19 19:52: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 A98B21065676 for ; Mon, 19 Jan 2009 19:52:54 +0000 (UTC) (envelope-from ubm.freebsd@googlemail.com) Received: from mail-bw0-f10.google.com (mail-bw0-f10.google.com [209.85.218.10]) by mx1.freebsd.org (Postfix) with ESMTP id 02A668FC1E for ; Mon, 19 Jan 2009 19:52:53 +0000 (UTC) (envelope-from ubm.freebsd@googlemail.com) Received: by bwz3 with SMTP id 3so53841bwz.19 for ; Mon, 19 Jan 2009 11:52:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:subject :message-id:x-mailer:mime-version:content-type :content-transfer-encoding; bh=92t3h2qIQMpJrn0Nd4/mCq1sTfqVmOj4B9ydIk5fMAg=; b=ZR/byzVznVTI4eLNzNRcHFu3HbiBzbvo8yAAPzxFqA/hM+jIe7nESRBDw4SrWSZtfs 7a6xKBaA+wpsH6UyzNlEhUKfkIBTm3jnygNpR55Ih3sQzw6i0Pegy986Yx/E7tlXOYEZ nPz6XU5FlWAQy4oY3MChP7Kon92cp4hf2ksdU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=date:from:to:subject:message-id:x-mailer:mime-version:content-type :content-transfer-encoding; b=UnMnOVX+rziVDzDZ4rV4adKLGlbMCXbkWMooSKUWKKWvq8QZX6lGabG72YGZhwA1WC 4qRaa0Bgy0C6ziMhVdlLWoFt8mjCVgK25y6VTDlMUmv9+Zlgg48Kk9OrPwHY5Ph/vZaK PAoydZif+Sa27xN7xTSUUIcXRlyVLUpdA5wuA= Received: by 10.223.114.2 with SMTP id c2mr4140558faq.85.1232392818457; Mon, 19 Jan 2009 11:20:18 -0800 (PST) Received: from ubm.mine.nu (e181000109.adsl.alicedsl.de [85.181.0.109]) by mx.google.com with ESMTPS id y15sm5321009fkd.32.2009.01.19.11.20.17 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 19 Jan 2009 11:20:17 -0800 (PST) Date: Mon, 19 Jan 2009 20:20:16 +0100 From: Marc UBM To: freebsd-stable@freebsd.org Message-Id: <20090119202016.11f42e3b.ubm.freebsd@gmail.com> X-Mailer: Sylpheed 2.6.0 (GTK+ 2.12.10; i386-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: problems with sata disks (taskqueue timeout) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Jan 2009 19:52:55 -0000 Hiho! :-) Occasionally, especially when uploading a large number of files, the (brand-new, tested) sata disks in my fileserver spit out some of these errors: ----------------------- Jan 19 19:51:14 hamstor kernel: ad10: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=882778752 Jan 19 19:51:23 hamstor kernel: ad10: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly Jan 19 19:51:27 hamstor kernel: ad10: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly Jan 19 19:51:31 hamstor kernel: ad10: WARNING - SETFEATURES ENABLE WCACHE taskqueue timeout - completing request directly Jan 19 19:51:35 hamstor kernel: ad10: WARNING - SET_MULTI taskqueue timeout - completing request directly Jan 19 19:51:35 hamstor kernel: ad10: TIMEOUT - WRITE_DMA48 retrying (0 retries left) LBA=882778752 Jan 19 19:51:35 hamstor kernel: ad10: FAILURE - WRITE_DMA48 status=ff error=ff LBA=882778752 Jan 19 19:51:35 hamstor root: ZFS: vdev I/O failure, zpool=gedaerm path=/dev/ad10 offset=451982655488 size=131072 error=5 Jan 19 19:51:41 hamstor kernel: ad10: FAILURE - SET_MULTI status=51 error=4 Jan 19 19:51:41 hamstor kernel: ad10: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=882779008 Jan 19 19:51:41 hamstor kernel: ad10: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=882779008 Jan 19 19:51:50 hamstor kernel: ad10: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly Jan 19 19:51:54 hamstor kernel: ad10: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly Jan 19 19:51:58 hamstor kernel: ad10: WARNING - SETFEATURES ENABLE WCACHE taskqueue timeout - completing request directly Jan 19 19:52:02 hamstor kernel: ad10: WARNING - SET_MULTI taskqueue timeout - completing request directly Jan 19 19:52:02 hamstor kernel: ad10: FAILURE - WRITE_DMA48 timed out LBA=882779008 Jan 19 19:52:02 hamstor root: ZFS: vdev I/O failure, zpool=gedaerm path=/dev/ad10 offset=451982786560 size=131072 error=5 ----------------------- I've fiddled with the cables, which seemed to help, but I've been unable to completely eliminate the errors. The disks are two Western Digital MyBooks Home Edition (1 TB per disk), connected to a Promise TX 4 SATA Controller: atapci0@pci0:1:6:0: class=0x018000 card=0x3d17105a chip=0x3d17105a rev=0x02 hdr=0x00 vendor = 'Promise Technology Inc' device = 'PDC40718-GP SATA 300 TX4 Controller' class = mass storage They're connected via 50cm esata cables. I've googled on the net and found some vague hints about problems with the Promise TX4, but nothing concrete. What I've found is http://wiki.freebsd.org/JeremyChadwick/ATA_issues_and_troubleshooting basically telling me "these things happen, deal with it" :-) The problem is, I cannot produce these problems reliably, only thing I notice is that they *seem* to happen more often if a lot of large files are copied in succession. Can anybody tell me if upgrading to 7.2 oder -current will help? I'm currently running 7.0-STABLE-200804 FreeBSD 7.0-STABLE-200804 #0: Wed Dec 10 15:29:03 CET 2008 ***@host:/usr/obj/usr/src/sys/GENERIC amd64 Next step I'll try is upgrading to RELENG_7 to see if that helps. Greetings, Marc -- Marc "UBM" Bocklet From owner-freebsd-stable@FreeBSD.ORG Mon Jan 19 20:23: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 05691106567F for ; Mon, 19 Jan 2009 20:23:06 +0000 (UTC) (envelope-from hartzell@alerce.com) Received: from merlin.alerce.com (merlin.alerce.com [64.62.142.94]) by mx1.freebsd.org (Postfix) with ESMTP id E5D608FC30 for ; Mon, 19 Jan 2009 20:23:05 +0000 (UTC) (envelope-from hartzell@alerce.com) Received: from merlin.alerce.com (localhost [127.0.0.1]) by merlin.alerce.com (Postfix) with ESMTP id 321DD33C62 for ; Mon, 19 Jan 2009 12:01:47 -0800 (PST) Received: from merlin.alerce.com (localhost [127.0.0.1]) by merlin.alerce.com (Postfix) with ESMTP id C367D33C5B for ; Mon, 19 Jan 2009 12:01:46 -0800 (PST) From: George Hartzell MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18804.56362.665722.719912@almost.alerce.com> Date: Mon, 19 Jan 2009 12:01:46 -0800 To: freebsd-stable@freebsd.org X-Mailer: VM 7.19 under Emacs 22.1.50.1 X-Virus-Scanned: ClamAV using ClamSMTP Subject: success with snd_hda and 7.1-STABLE on Mac Pro, default changed. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: hartzell@alerce.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jan 2009 20:23:06 -0000 I upgraded my early-2008 Mac Pro to 7.1-STABLE and Gnome 2.24.3 over the weekend, it had been tracking -STABLE. I'd imported the snd_hda driver and had it running with a few tweaks, which I needed to adjust to get it running under this version of the driver. I'm only able to get the rear line-out jack to work, I haven't found anything combination of ....config values and/or default_unit's that make the front headphone jack work. For posterity's sake, here are the details: /boot/device.hints (added at the bottom) hint.hdac.0.config="gpio0 gpio1" /boot/loader.conf hw.snd.default_unit=3 Details are available at: http://shrimp.alerce.com/snd_hda/sndstat.txt http://shrimp.alerce.com/snd_hda/dmesg.txt http://shrimp.alerce.com/snd_hda/pindump.txt g. From owner-freebsd-stable@FreeBSD.ORG Mon Jan 19 21:09:37 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 26E881065676 for ; Mon, 19 Jan 2009 21:09:37 +0000 (UTC) (envelope-from cpghost@cordula.ws) Received: from fw.farid-hajji.net (fw.farid-hajji.net [213.146.115.42]) by mx1.freebsd.org (Postfix) with ESMTP id 7B3C18FC0C for ; Mon, 19 Jan 2009 21:09:36 +0000 (UTC) (envelope-from cpghost@cordula.ws) Received: from phenom.cordula.ws (phenom [192.168.254.60]) by fw.farid-hajji.net (Postfix) with ESMTP id 16ACB36824; Mon, 19 Jan 2009 21:54:05 +0100 (CET) Date: Mon, 19 Jan 2009 21:56:24 +0100 From: cpghost To: Pete Carah Message-ID: <20090119205624.GA1375@phenom.cordula.ws> References: <200901190230.n0J2U5S5002220@port2.altadena.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200901190230.n0J2U5S5002220@port2.altadena.net> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: stable@freebsd.org Subject: Soekris 4801 hangs (was Re: Hangs, maybe a clue) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Jan 2009 21:09:37 -0000 On Sun, Jan 18, 2009 at 09:30:05PM -0500, Pete Carah wrote: > I've had some mysterious hangs which I notice that several others have too. > Two of the machines in question are Soekris 4801's running as routers; this > is hard to handle ddb with (though possible for one of them...) I started > noticing this sometime in December. My laptop finally hung in a state where > I could do a ps (waiting a long time for the response.) The strange and > likely related to the hang was softdepflush in R state with 43 MINUTES of > cpu. (the machine has been up maybe an hour.) I'm seeing those hangs on Soekris 4801 routers running RELENG_7 as well. The boxes are used as SoHo appliances and run mpd5, pf, named, postfix, cyrus-imapd, lighttpd, openntpd and sshd. On all of them, softupdates are enabled on all partitions except root and they use real HDDs (not compact flash). The hangs appear now every 2 or 3 days at different times. They don't seem related to traffic type (heavy p2p, normal upload/download, or idle) and also seem independent on disk activity (i.e. there's no more during 3am than other time). They were less frequent before Dec 1st, and IIRC the last RELENG_7 that was nearly hang-free was 2008-11-07. IMHO, it could be some kind of resource leak (?), but I'm not sure. Since the only serial port is used by getty, I'm not sure how to break into the debugger and how to trace the problem (and I'm not experienced enough for this). :( > -- Pete Regards, -cpghost. -- Cordula's Web. http://www.cordula.ws/ From owner-freebsd-stable@FreeBSD.ORG Mon Jan 19 21:10: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 0CEFE10656C5 for ; Mon, 19 Jan 2009 21:10:40 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from dhcp-172-28-76-122.eur.corp.google.com (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id DC5188FC18; Mon, 19 Jan 2009 21:10:38 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <4974EC4C.4020004@FreeBSD.org> Date: Mon, 19 Jan 2009 21:10:36 +0000 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) MIME-Version: 1.0 To: Pete Carah References: <49747F10.7050801@altadena.net> In-Reply-To: <49747F10.7050801@altadena.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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, 19 Jan 2009 21:10:40 -0000 Pete Carah wrote: > Kris writes: > >> You and anyone else seeing performance problems should try to work >> through the advice given here: > > > > http://people.freebsd.org/~kris/scaling/Help_my_system_is_slow.pdf > > Well, all the people in this thread have noticed that WITH NO CONFIG CHANGES from configs > that worked fine in the past, their systems are very slow and/or locking up (mine are both) with > the stable branch sometime (I noticed it sometime in December, but it got worse with the release.) > Most were OK in October; mine (I think) were OK in late November - may narrow things down? Two of my > systems that lock up have no internal visibility when they do (Soekris 4801's routing; the only > time-intensive things running are routing (done in irq context) and pflog. These run with 60+ > meg ram free.) These are complete lockups, though I did manage to get a ps out of my laptop last > night by waiting 20 _minutes_ for it to start (!). This is not a generic performance problem. The laptop > had 55 minutes of cpu time in the softdepflush thread after being up about an hour and 10 mins; > this might give a hint. I didn't spot LL/RL state threads at the same time because I didn't know > to. Now I do. BTW - the same ps showed 8 or so user-space procs in R state with NO cpu time; the > kernel was hogging all of it for over an hour. > Firefox did indeed trigger this one as someone else noted. A soekris doing only routing+nat has no such > excuse... At least PHK was nice enough to note the watchdog in another thread :-) Actually, there have been several apparently different problems reported in this thread, some of which (including the message I replied to) *are* generic "my system is slower" problems. For generic "my system hangs" problems, see the chapter on kernel debugging in the handbook or follow the (same) advice given by Robert earlier in the thread. Kris From owner-freebsd-stable@FreeBSD.ORG Mon Jan 19 21:32:18 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 DECA9106566B for ; Mon, 19 Jan 2009 21:32:18 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from mail-bw0-f15.google.com (mail-bw0-f15.google.com [209.85.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id 3E7098FC0A for ; Mon, 19 Jan 2009 21:32:17 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: by bwz8 with SMTP id 8so7550347bwz.12 for ; Mon, 19 Jan 2009 13:32:16 -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=EbVEK83j1U2oXGbXPa1xvugsysgUb/S7wIBf5I9yOCM=; b=Gjgbn9DDg8+QQ6s2Q6owKkX7eliZf5CYYZXfzuYxya4Q9z8dPoZwrHGarA7Z0/WIKD iKdEVzG/b60x0zuvVs1wqGDKw35kYA8XjklzD8x6ZywHh9WVj4MSeg9XWwA1S8CP2nbm Cv5slMT71pXLO+fJERaFS1MVnTDYNolrzJsn0= 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=cTNJ8hC/PEQGn4XUvZRIect/iOHlc6w3wcGYo+W3xfGj9acj4wKhwHc9EUB63neOPX edm9zWFajAH477c1GynJHOnYYChUGDw5MxpTAgOYEB6gxPGaUjZlDGJNuJZp3TxHy5xZ 7I4t0jJ9StRb3GUzEG1EhHrAMPZAH8OtSBOuo= MIME-Version: 1.0 Received: by 10.181.209.1 with SMTP id l1mr514600bkq.113.1232400599039; Mon, 19 Jan 2009 13:29:59 -0800 (PST) In-Reply-To: References: Date: Mon, 19 Jan 2009 13:29:58 -0800 Message-ID: <7d6fde3d0901191329ha01bcd3t4939b305ef101227@mail.gmail.com> From: Garrett Cooper To: Matthias Schuendehuette Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org Subject: Re: NFS-Locking problem with 6.4/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: Mon, 19 Jan 2009 21:32:19 -0000 On Sun, Jan 18, 2009 at 2:15 AM, Matthias Schuendehuette wrote: > Hello, > > I operate two FreeBSD-Servers in a Windows- and HP-UX Environment. One is a > SAMBA-Server as a gateway between the Windows and the Unix world, the other > is NFS-Server for the HP-UX 11i v1 Workstations. Both are HP ProLiants DL380 > with additional external disks on SmartRAID Controllers. > > Since the HP-UX Workstations and their disks are becoming quite old, I > started to move the home-directories to the FreeBSD Server, wich worked with > 6.3-RELEASE quite good so far. > > > Brave as I am, I updated the servers to 6.4 RELEASE and since then the users > on the HP-UX machines with the homedirs on the FreeBSD-Server were locked... > :-( > > I tried to find out what was happening and this are my results: > > When a user logs in on a HP-UX machine, his '.profile' file is opened and > read/executed, but it seems, that it cannot be closed any more. So if the > last line in the '.profile' is "echo foo bar" you *can* see "foo bar" on the > screen, but then nothing happens any more, the machine is locked. > > I recorded such a session with 'tcpdump' and looked at the dump... the only > noticeable things are *Bursts* of NLM V4 CANCEL_MSGes on the same > filehandle. Eg: > > "V4 CANCEL_MSG Call FH:0x644201fe svid:xxxx pos:0-0" > > This line is repeated 7 times with various values for 'svid'. > > I'm no NFS specialist at all, so I cannot tell you more :-/ But I can supply > the dump (if needed), > it's 92KB, so the size should not be a problem... > > BTW: I tried this with and without kernel support for NFS-Locking - no > difference. I also tried the new replacement server with FreeBSD > 7.1-RELEASE: Just the same problems, with and without kernel support. > > I hope someone is willing to work on that issue... > > As mentioned, a new, non-productive server is available in the moment, so > tests are easily possible. > > TIA > > Matthew What OS and what NFS version are the HP-UX servers running? Have you checked /var/log/messages on the clients and on the server for helpful messages? Thanks, -Garrett From owner-freebsd-stable@FreeBSD.ORG Mon Jan 19 21:33:56 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 33D9E106573B; Mon, 19 Jan 2009 21:33:54 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: pyunyh@gmail.com Date: Mon, 19 Jan 2009 16:33:34 -0500 User-Agent: KMail/1.6.2 References: <8dfae1c10901070639x67945324jeeecfcac647d7976@mail.gmail.com> <496CAB07.5020404@holzleiter.name> <20090117044758.GB68290@cdnetworks.co.kr> In-Reply-To: <20090117044758.GB68290@cdnetworks.co.kr> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200901191633.37309.jkim@FreeBSD.org> Cc: freebsd-stable@freebsd.org, 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: Mon, 19 Jan 2009 21:33:58 -0000 On Friday 16 January 2009 11:47 pm, 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: 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.di > > >ff?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 found something interesting. I have another RTL8169SC that works perfectly fine without the patch. The hardware revision is 0x18000000. After reading Linux driver (drivers/net/r8169c), I realised they use different masks for hardware revisions. With their logic, non-working chip seems to be 0x98000000 (8110SCe) while working chip seems to be 0x18000000 (8110SCd) with 0xfc800000. FYI... Jung-uk Kim From owner-freebsd-stable@FreeBSD.ORG Mon Jan 19 21:51:50 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 070F4106568A for ; Mon, 19 Jan 2009 21:51:50 +0000 (UTC) (envelope-from msch@snafu.de) Received: from sour.ops.eusc.inter.net (sour.ops.eusc.inter.net [84.23.254.154]) by mx1.freebsd.org (Postfix) with ESMTP id B43728FC14 for ; Mon, 19 Jan 2009 21:51:49 +0000 (UTC) (envelope-from msch@snafu.de) X-Trace: 507c6d73636840736e6166752e64657c38372e3138372e38322e3231317c314c50 3232372d3030303462592d49677c31323332343031393037 Received: from sour.ops.eusc.inter.net ([10.154.10.19] helo=localhost) by sour.ops.eusc.inter.net with esmtpa (Exim 4.69) id 1LP227-0004bY-Ig; Mon, 19 Jan 2009 22:51:47 +0100 Message-Id: From: Matthias Schuendehuette To: Garrett Cooper In-Reply-To: <7d6fde3d0901191329ha01bcd3t4939b305ef101227@mail.gmail.com> Content-Type: multipart/signed; boundary=Apple-Mail-7-691636854; micalg=sha1; protocol="application/pkcs7-signature" Mime-Version: 1.0 (Apple Message framework v930.3) Date: Mon, 19 Jan 2009 22:51:47 +0100 References: <7d6fde3d0901191329ha01bcd3t4939b305ef101227@mail.gmail.com> X-Mailer: Apple Mail (2.930.3) X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: stable@freebsd.org Subject: Re: NFS-Locking problem with 6.4/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: Mon, 19 Jan 2009 21:51:50 -0000 --Apple-Mail-7-691636854 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Hi Garret, Am 19.01.2009 um 22:29 schrieb Garrett Cooper: > What OS and what NFS version are the HP-UX servers running? The OS is "HP-UX 11.11" a.k.a "HP-UX 11iv1". NFS-Version is NFSV3 (of course ;-) via TCP > Have > you checked /var/log/messages on the clients and on the server for > helpful messages? No, I'll look tomorrow. I tested today against 7.1-STABLE (of today) but no change in behaviour so far. In the meantime I found PR "kern/130628" and that could be the problem here too. I started 'wireshark' on the NFS-server today and it showed endless requests from the client to release a lock and equally endless error-replies... At least I would expect that an error like that in kern/130628 would look like what I observed today - but I may fail. Thanks for your reply - Matthew -- Ciao/BSD - Matthias Matthias Schuendehuette , Berlin (Germany) --Apple-Mail-7-691636854-- From owner-freebsd-stable@FreeBSD.ORG Mon Jan 19 22:20:05 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 91C851065672; Mon, 19 Jan 2009 22:20:05 +0000 (UTC) (envelope-from pete@port3.altadena.net) Received: from kestrel.altadena.net (kestrel.altadena.net [207.136.131.34]) by mx1.freebsd.org (Postfix) with ESMTP id 7805C8FC18; Mon, 19 Jan 2009 22:20:05 +0000 (UTC) (envelope-from pete@port3.altadena.net) Received: from office.cerona.com ([75.148.25.105] helo=port3.altadena.net) by kestrel.altadena.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1LP2A6-000OFH-7r; Mon, 19 Jan 2009 14:00:02 -0800 Received: from port3.altadena.net (localhost [127.0.0.1]) by port3.altadena.net (8.14.3/8.13.4) with ESMTP id n0JM00gF001225; Mon, 19 Jan 2009 17:00:00 -0500 (EST) (envelope-from pete@port3.altadena.net) Received: (from pete@localhost) by port3.altadena.net (8.14.3/8.13.4/Submit) id n0JLxx7w001224; Mon, 19 Jan 2009 16:59:59 -0500 (EST) (envelope-from pete) Date: Mon, 19 Jan 2009 16:59:59 -0500 From: Pete Carah To: kris@freebsd.org Message-ID: <20090119215959.GA1185@port3.altadena.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Cc: 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, 19 Jan 2009 22:20:05 -0000 I have done some (lots of) kernel debugging in the past. I have several points: 1. I shouldn't *have* to kernel debug for a normal usage of an official release. 2. One of the soekris boxes is 2800 MILES away, in a remote location, with noone present that is a skilled (or, indeed, any kind of) programmer. I usually thought I could trust a release, especially when I had been using the stable branch updated at about monthly intervals on 3 servers with no problems. (actually, I waited a while on 7.0 because .0 releases are traditionally quirky; in this case 7.0-rel worked fine and 7.1 has problems.) (and my servers are still running the *same* compilation of kernel/world with no problems; the hangs are unique to either the laptop (which only started doing this badly with a Jan 9 csup) and the Soekris boxes (which started hangs sometime in December; they clearly don't run X...) [ I've backed my house source to -stable of 12/1/08 and hope this will help; I don't have the time to fool around too much, and particularly to kernel debug something that shouldn't need it.] I can't even start X at all on this laptop now. At least I can boot it, but it isn't much use for work unless it can run X. 3. I can't afford the time to debug my tools (freebsd is a tool, not an experiment, for lots of people, including me...) I use this laptop at work in a place where I am *not* working on freebsd. (nor am I even allowed to at work...) -- Pete From owner-freebsd-stable@FreeBSD.ORG Mon Jan 19 22:40: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 DFE45106564A for ; Mon, 19 Jan 2009 22:40:40 +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 A150B8FC18 for ; Mon, 19 Jan 2009 22:40:40 +0000 (UTC) (envelope-from andrew@modulus.org) Received: by email.octopus.com.au (Postfix, from userid 1002) id BB19E1788B; Tue, 20 Jan 2009 09:40:41 +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 C864117267; Tue, 20 Jan 2009 09:40:33 +1100 (EST) Message-ID: <49750137.7020105@modulus.org> Date: Tue, 20 Jan 2009 09:39:51 +1100 From: Andrew Snow User-Agent: Thunderbird 2.0.0.14 (X11/20080523) MIME-Version: 1.0 To: Marc UBM , freebsd-stable@freebsd.org References: <20090119202016.11f42e3b.ubm.freebsd@gmail.com> In-Reply-To: <20090119202016.11f42e3b.ubm.freebsd@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: problems with sata disks (taskqueue timeout) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Jan 2009 22:40:41 -0000 I think that if you use eSATA you probably need dedicated eSATA controller ports. eSATA standard specifies a higher voltage for the longer cable distances. Judging from the sporadic problem reports, Promise TX4 is probably not the best at signal purity to begin with so using it for eSATA pushes it over the edge. Hope that helps, - Andrew From owner-freebsd-stable@FreeBSD.ORG Mon Jan 19 22:47: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 2A69D10656D7 for ; Mon, 19 Jan 2009 22:47:53 +0000 (UTC) (envelope-from roberto@keltia.freenix.fr) Received: from keltia.freenix.fr (keltia.freenix.org [IPv6:2001:660:330f:f820:213:72ff:fe15:f44]) by mx1.freebsd.org (Postfix) with ESMTP id CEFDC8FC14 for ; Mon, 19 Jan 2009 22:47:52 +0000 (UTC) (envelope-from roberto@keltia.freenix.fr) Received: from localhost (localhost [127.0.0.1]) by keltia.freenix.fr (Postfix/TLS) with ESMTP id 317443B742 for ; Mon, 19 Jan 2009 23:47:51 +0100 (CET) X-Virus-Scanned: amavisd-new at keltia.freenix.fr Received: from keltia.freenix.fr ([127.0.0.1]) by localhost (keltia.freenix.fr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h2C6comXtuzc for ; Mon, 19 Jan 2009 23:47:50 +0100 (CET) Received: by keltia.freenix.fr (Postfix/TLS, from userid 101) id D9E693B73A; Mon, 19 Jan 2009 23:47:50 +0100 (CET) Date: Mon, 19 Jan 2009 23:47:50 +0100 From: Ollivier Robert To: freebsd-stable@freebsd.org Message-ID: <20090119224750.GA7463@keltia.freenix.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: MacOS X / Macbook Pro - FreeBSD 7 / Dell D820 SMP User-Agent: Mutt/1.5.18 (2008-05-17) Subject: SYSV* mandatory for COMPAT_IA32 on amd64? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jan 2009 22:47:53 -0000 I must have missed the HEADS-UP or something but it seems that the SYSV IPC options are now mandatory in order to compile an amd64 kernel with COMPAT_IA32... I get linking errors in kernel.debug because freebsd32_syscalls.o is referencing the SYSV syscalls... Am I alone? -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr Dons / donation Ondine : http://ondine.keltia.net/ From owner-freebsd-stable@FreeBSD.ORG Mon Jan 19 23:01:52 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 A80EC1065679 for ; Mon, 19 Jan 2009 23:01:52 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (lefty.soaustin.net [66.135.55.46]) by mx1.freebsd.org (Postfix) with ESMTP id 8A7978FC1E for ; Mon, 19 Jan 2009 23:01:52 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id 79C418C07F; Mon, 19 Jan 2009 16:33:44 -0600 (CST) Date: Mon, 19 Jan 2009 16:33:44 -0600 To: Pete Carah Message-ID: <20090119223344.GB32637@soaustin.net> References: <20090119215959.GA1185@port3.altadena.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090119215959.GA1185@port3.altadena.net> User-Agent: Mutt/1.5.13 (2006-08-11) From: linimon@lonesome.com (Mark Linimon) Cc: kris@freebsd.org, 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, 19 Jan 2009 23:01:53 -0000 On Mon, Jan 19, 2009 at 04:59:59PM -0500, Pete Carah wrote: > I shouldn't *have* to kernel debug for a normal usage of an > official release. Agreed, but the problems that people are having do not seem to have arisen on any of the systems that ran prelease tests for 7.1. Although I'm sure it does not seem that way to you, 7.1R had a very long QA cycle, and as far as I knew all the showstopper issues had already been addressed (although I don't officially speak for re@, I'm just an observer.) With my bugmeister hat on, I'll happily accept suggestions about how we can get more people involved in testing the prelease images. Clearly the situtation we're in right now is not where anyone wants us to be. mcl From owner-freebsd-stable@FreeBSD.ORG Mon Jan 19 23:10: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 801311065693 for ; Mon, 19 Jan 2009 23:10:25 +0000 (UTC) (envelope-from david.figuera@gmail.com) Received: from mail-ew0-f20.google.com (mail-ew0-f20.google.com [209.85.219.20]) by mx1.freebsd.org (Postfix) with ESMTP id 111B58FC08 for ; Mon, 19 Jan 2009 23:10:24 +0000 (UTC) (envelope-from david.figuera@gmail.com) Received: by ewy13 with SMTP id 13so851486ewy.19 for ; Mon, 19 Jan 2009 15:10:24 -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 :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=4Dx1D4i2qY5O7ZVfG8+YNJ+TaI8frELTKbg3jMqk26o=; b=joZYnwLZx5FFkmKuGYBQbNEqwTtfpj3m2aj/TpRbKOwBKnATGrrDg/fqevYPI11llG dtLIR3K7Zf89Hf/yBoZDs/7ura5jOdYzWKCZPJtAifsFFlPsw2r5FMCLOuasq1dRr2Nw oT1OT3pGrOEhjyaTjSHukJooMyFcSoTN0P6iM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=PJyI/DD/tddl7l2IV4bFB6XKEVPll2UUgURNK63b67ipZzzXv5fW0nwlNALZqopLJI yBgDsSUX9cFyeQSgD5WVhIz0ziNQ3UVLymrzfF7ydeZS08lYVdjlss0t9ZiJLAjuGU3j gRc0C++WmIQ/2JE+Qa+lvT1NcV5pD/45RLAVQ= Received: by 10.210.109.10 with SMTP id h10mr7795822ebc.10.1232405292783; Mon, 19 Jan 2009 14:48:12 -0800 (PST) Received: from ?192.168.1.100? (137.Red-81-32-31.dynamicIP.rima-tde.net [81.32.31.137]) by mx.google.com with ESMTPS id t12sm1181498gvd.32.2009.01.19.14.48.11 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 19 Jan 2009 14:48:12 -0800 (PST) Message-ID: <497502EE.1090804@gmail.com> Date: Mon, 19 Jan 2009 23:47:10 +0100 From: David Figuera User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <20090119202016.11f42e3b.ubm.freebsd@gmail.com> In-Reply-To: <20090119202016.11f42e3b.ubm.freebsd@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: problems with sata disks (taskqueue timeout) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Jan 2009 23:10:26 -0000 > I've fiddled with the cables, which seemed to help, but I've been > unable to completely eliminate the errors. The disks are two Western > Digital MyBooks Home Edition (1 TB per disk), connected to a Promise TX > 4 SATA Controller: > > atapci0@pci0:1:6:0: class=0x018000 card=0x3d17105a chip=0x3d17105a > rev=0x02 hdr=0x00 vendor = 'Promise Technology Inc' > device = 'PDC40718-GP SATA 300 TX4 Controller' > class = mass storage I have a similar setup, same card, two WD disks. On 6.3 it was affected by the problem you mention, but when I moved to 7.0, it disapeared. From owner-freebsd-stable@FreeBSD.ORG Mon Jan 19 23:30: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 E14851065686 for ; Mon, 19 Jan 2009 23:30:34 +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 1211A8FC08 for ; Mon, 19 Jan 2009 23:30:34 +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 9EA3084CE205; Mon, 19 Jan 2009 17:30:32 -0600 (CST) Received: from localhost (morganw@localhost [127.0.0.1]) by volatile.chemikals.org (8.14.3/8.14.3) with ESMTP id n0JNUQF7010657; Mon, 19 Jan 2009 17:30:27 -0600 (CST) (envelope-from morganw@chemikals.org) Date: Mon, 19 Jan 2009 17:30:26 -0600 (CST) From: Wes Morgan To: Marc UBM In-Reply-To: <20090119202016.11f42e3b.ubm.freebsd@gmail.com> Message-ID: References: <20090119202016.11f42e3b.ubm.freebsd@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: problems with sata disks (taskqueue timeout) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Jan 2009 23:30:37 -0000 On Mon, 19 Jan 2009, Marc UBM wrote: > > Hiho! :-) > > Occasionally, especially when uploading a large number of files, the > (brand-new, tested) sata disks in my fileserver spit out some of these > errors: I've found that those kind of errors are very, very controller-dependent. Case in point - a 4-disk raidz on an ASUS board with a VIA SATA controller. The drives were attached to a highpoint rocketraid controller, then the data was moved off and the drives attached to the VIA controller. As soon as the raidz was created and data was being copied back to the array, taskqueue errors. So, back to the highpoint controller. Swapped out the board for another ASUS, but this time with the Q35 / ICH9 controller. No a single problem whatsoever. > > ----------------------- > > Jan 19 19:51:14 hamstor kernel: ad10: WARNING - WRITE_DMA48 UDMA ICRC > error (retrying request) LBA=882778752 > > Jan 19 19:51:23 hamstor kernel: > ad10: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - > completing request directly > > Jan 19 19:51:27 hamstor kernel: ad10: > WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing > request directly > > Jan 19 19:51:31 hamstor kernel: ad10: WARNING - > SETFEATURES ENABLE WCACHE taskqueue timeout - completing request > directly > > Jan 19 19:51:35 hamstor kernel: ad10: WARNING - SET_MULTI > taskqueue timeout - completing request directly > > Jan 19 19:51:35 hamstor > kernel: ad10: TIMEOUT - WRITE_DMA48 retrying (0 retries left) > LBA=882778752 > > Jan 19 19:51:35 hamstor kernel: ad10: FAILURE - > WRITE_DMA48 > status=ff > error=ff > LBA=882778752 > > Jan 19 19:51:35 hamstor root: ZFS: vdev I/O failure, > zpool=gedaerm path=/dev/ad10 offset=451982655488 size=131072 error=5 > > Jan 19 19:51:41 hamstor kernel: ad10: FAILURE - SET_MULTI > status=51 error=4 > > Jan 19 19:51:41 hamstor > kernel: ad10: TIMEOUT - WRITE_DMA48 retrying (1 retry left) > LBA=882779008 > > Jan 19 19:51:41 hamstor kernel: ad10: WARNING - > WRITE_DMA48 UDMA ICRC error (retrying request) LBA=882779008 Jan 19 > 19:51:50 hamstor kernel: ad10: WARNING - SETFEATURES SET TRANSFER MODE > taskqueue timeout - completing request directly > > Jan 19 19:51:54 hamstor > kernel: ad10: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout > - completing request directly > > Jan 19 19:51:58 hamstor kernel: ad10: > WARNING - SETFEATURES ENABLE WCACHE taskqueue timeout - completing > request directly > > Jan 19 19:52:02 hamstor kernel: ad10: WARNING - > SET_MULTI taskqueue timeout - completing request directly Jan 19 > 19:52:02 hamstor kernel: ad10: FAILURE - WRITE_DMA48 timed out > LBA=882779008 > > Jan 19 19:52:02 hamstor root: ZFS: vdev I/O failure, > zpool=gedaerm path=/dev/ad10 offset=451982786560 size=131072 error=5 > > ----------------------- > > I've fiddled with the cables, which seemed to help, but I've been > unable to completely eliminate the errors. The disks are two Western > Digital MyBooks Home Edition (1 TB per disk), connected to a Promise TX > 4 SATA Controller: > > atapci0@pci0:1:6:0: class=0x018000 card=0x3d17105a chip=0x3d17105a > rev=0x02 hdr=0x00 vendor = 'Promise Technology Inc' > device = 'PDC40718-GP SATA 300 TX4 Controller' > class = mass storage > > They're connected via 50cm esata cables. > > I've googled on the net and found some vague hints about problems with > the Promise TX4, but nothing concrete. > > What I've found is > > http://wiki.freebsd.org/JeremyChadwick/ATA_issues_and_troubleshooting > > basically telling me "these things happen, deal with it" :-) > > The problem is, I cannot produce these problems reliably, only thing I > notice is that they *seem* to happen more often if a lot of large files > are copied in succession. > > Can anybody tell me if upgrading to 7.2 oder -current will help? > > I'm currently running > > 7.0-STABLE-200804 FreeBSD 7.0-STABLE-200804 #0: Wed Dec 10 15:29:03 CET > 2008 ***@host:/usr/obj/usr/src/sys/GENERIC amd64 > > Next step I'll try is upgrading to RELENG_7 to see if that helps. > > > Greetings, > Marc > > > > > > > > > From owner-freebsd-stable@FreeBSD.ORG Mon Jan 19 23:34:06 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 124C81065670; Mon, 19 Jan 2009 23:34:06 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-stable@FreeBSD.org Date: Mon, 19 Jan 2009 18:33:46 -0500 User-Agent: KMail/1.6.2 References: <8dfae1c10901070639x67945324jeeecfcac647d7976@mail.gmail.com> <20090117044758.GB68290@cdnetworks.co.kr> <200901191633.37309.jkim@FreeBSD.org> In-Reply-To: <200901191633.37309.jkim@FreeBSD.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200901191833.51320.jkim@FreeBSD.org> Cc: pyunyh@gmail.com, 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: Mon, 19 Jan 2009 23:34:09 -0000 On Monday 19 January 2009 04:33 pm, Jung-uk Kim wrote: > I found something interesting. I have another RTL8169SC that works > perfectly fine without the patch. The hardware revision is > 0x18000000. After reading Linux driver (drivers/net/r8169c), I > realised they use different masks for hardware revisions. With > their logic, non-working chip seems to be 0x98000000 (8110SCe) > while working chip seems to be 0x18000000 (8110SCd) with > 0xfc800000. FYI... Now armed with the information, I made it work without reverting memory mapped I/O. :-) http://people.freebsd.org/~jkim/re/re.current2.diff http://people.freebsd.org/~jkim/re/re.stable2.diff Jung-uk Kim From owner-freebsd-stable@FreeBSD.ORG Mon Jan 19 23:42:36 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 A2C0C106564A for ; Mon, 19 Jan 2009 23:42:36 +0000 (UTC) (envelope-from campaign@online.intelestream.net) Received: from mail.opendataonline.com (mail.opendataonline.com [208.71.148.187]) by mx1.freebsd.org (Postfix) with ESMTP id 728698FC0C for ; Mon, 19 Jan 2009 23:42:36 +0000 (UTC) (envelope-from campaign@online.intelestream.net) Received: from online.intelestream.net (localhost [127.0.0.1]) by mail.opendataonline.com (Postfix) with ESMTP id 34D972E79C1 for ; Mon, 19 Jan 2009 16:37:51 -0600 (CST) To: "Daniel Connor" Message-ID: <96b2cd7ec6772a1be50b93deed51fc02@online.intelestream.net> Date: Mon, 19 Jan 2009 11:13:36 -0600 From: "Matthew Kallas" MIME-Version: 1.0 X-Mailer-LID: 8 X-Mailer-SID: 206 X-Mailer-Sent-By: 1 Content-Type: text/plain; format=flowed; charset="UTF-8" Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Webinar Invitation X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: matthew.kallas@online.intelestream.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jan 2009 23:42:37 -0000 Your invitation to join our webinar: Reducing IT Expenses with Open Source Technology Thursday, January 22nd No cost to attendees, but space is limited. Sign up by visiting: http://online.intelestream.net/em/link.php?M=425083&N=206&L=40&F=T Intelestream’s COO Richard Baldwin will discuss how businesses of all sizes can lower IT budgets and enhance business process automation through Open Source Technology. Baldwin, who has 20 years of experience in the IT industry, will demonstrate fundamental ROI and functionality distinctions between Open Source and Enterprise Software solutions, focusing on CRM, ERP, Email Marketing, E-commerce and Web Site Development. There will be a question and answer session focusing on the specific business case scenarios of attendees. More about Intelestream To learn more about Intelestream, go to www.intelestream.net To unsubscribe: go to http://online.intelestream.net/em/unsubscribe.php?M=425083&C=7b8148b5f145a9e926f5d9be209174dd&L=8&N=206 Intelestream Inc - Phone: (800) 391.4055 - Fax: (312) 244.3765 Address: 27 North Wacker Drive Suite 370 Chicago IL 60606 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 20 01: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 7BA651065676; Tue, 20 Jan 2009 01:55:23 +0000 (UTC) (envelope-from dgerow@afflictions.org) Received: from slow2-v.mail.gandi.net (slow2-v.mail.gandi.net [217.70.178.89]) by mx1.freebsd.org (Postfix) with ESMTP id 3CE788FC13; Tue, 20 Jan 2009 01:55:22 +0000 (UTC) (envelope-from dgerow@afflictions.org) Received: from relay1-v.mail.gandi.net (relay1-v.mail.gandi.net [217.70.178.75]) by slow2-v.mail.gandi.net (Postfix) with ESMTP id 852DB1BCDB4; Tue, 20 Jan 2009 02:38:27 +0100 (CET) Received: from plebeian.afflictions.org (206-248-171-136.dsl.teksavvy.com [206.248.171.136]) by relay1-v.mail.gandi.net (Postfix) with ESMTP id E97AC362AA; Tue, 20 Jan 2009 02:38:25 +0100 (CET) Received: by plebeian.afflictions.org (Postfix, from userid 1001) id 202A9610B; Mon, 19 Jan 2009 20:38:24 -0500 (EST) Date: Mon, 19 Jan 2009 20:38:24 -0500 From: Damian Gerow To: Sam Leffler Message-ID: <20090120013823.GA62274@plebeian.afflictions.org> References: <4973AE61.2040805@janh.de> <4974B4B2.5020308@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4974B4B2.5020308@freebsd.org> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: Jan Henrik Sylvester , stable-list freebsd Subject: Re: iwn driver on 7.1 [no vaps in RELENG_7] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jan 2009 01:55:23 -0000 Sam Leffler wrote: : OTOH iwn is now out of date and someone needs to update it. There's : newer firmware that is supposed to fix many of the bugs I hit when I : worked on the driver (and Intel refused to acknowledge) and obsd has : added support for newer parts that people want. It'd be great if : someone wanted to take over this driver. I've been working on this driver for the past few weeks (Christmas provided a healthy distraction), but it's a steep learning curve for a novice C coder. If anyone wants to work on this, let me know, as I have a small portion of the work already done. - Damian From owner-freebsd-stable@FreeBSD.ORG Tue Jan 20 02:45: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 3A3AF106566B; Tue, 20 Jan 2009 02:45:28 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.231]) by mx1.freebsd.org (Postfix) with ESMTP id EF7558FC0C; Tue, 20 Jan 2009 02:45:27 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so3026722rvf.43 for ; Mon, 19 Jan 2009 18:45:27 -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=eo/92ai2Jal4GAPOqk23k6TxU5x70Oqky7EWZEBJSmA=; b=K14ic96bpCNmgxurDIEtGmmkmVgUPDCROkL1x3L1HVjZm58uVMZhNRSwFIh5qQ/fm0 uHbxx8MdcE4sOfLVnoMLuZuKnu+i4Pz6UAsWBso/MbUhDdBFxtW5A7ajlAHyxCVrVILy 4pEYeW4NfSwUGSTRw66y55P4/PPULD7uc8aak= 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=DyAgOco1J/IMx7rMsgWCaITtOkAK2BqZ6XlJyc11DbAlZYrtGMm+telsq1GBMuga6G PpIi3HsJVAPrV2c1D0mcHRrMwwNm+8OI+mBvvQTimnBTKeRng/NdDkNotTQFjfQ/ZJ1I 5Sn/hh8Q5YcUO/j74Mwcrfz5x7eF+RaP4POfQ= Received: by 10.140.125.1 with SMTP id x1mr194519rvc.265.1232419527651; Mon, 19 Jan 2009 18:45:27 -0800 (PST) Received: from michelle.cdnetworks.co.kr ([211.53.35.84]) by mx.google.com with ESMTPS id b39sm4982363rvf.0.2009.01.19.18.45.25 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 19 Jan 2009 18:45:26 -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 n0K2jKSK080448 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 20 Jan 2009 11:45:20 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.14.3/8.14.3/Submit) id n0K2jJwa080447; Tue, 20 Jan 2009 11:45:19 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Tue, 20 Jan 2009 11:45:19 +0900 From: Pyun YongHyeon To: Jung-uk Kim Message-ID: <20090120024519.GB79785@cdnetworks.co.kr> References: <8dfae1c10901070639x67945324jeeecfcac647d7976@mail.gmail.com> <20090117044758.GB68290@cdnetworks.co.kr> <200901191633.37309.jkim@FreeBSD.org> <200901191833.51320.jkim@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200901191833.51320.jkim@FreeBSD.org> User-Agent: Mutt/1.4.2.3i Cc: Sascha Holzleiter , 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, 20 Jan 2009 02:45:28 -0000 On Mon, Jan 19, 2009 at 06:33:46PM -0500, Jung-uk Kim wrote: > On Monday 19 January 2009 04:33 pm, Jung-uk Kim wrote: > > I found something interesting. I have another RTL8169SC that works > > perfectly fine without the patch. The hardware revision is > > 0x18000000. After reading Linux driver (drivers/net/r8169c), I > > realised they use different masks for hardware revisions. With > > their logic, non-working chip seems to be 0x98000000 (8110SCe) > > while working chip seems to be 0x18000000 (8110SCd) with > > 0xfc800000. FYI... > > Now armed with the information, I made it work without reverting > memory mapped I/O. :-) > > http://people.freebsd.org/~jkim/re/re.current2.diff > http://people.freebsd.org/~jkim/re/re.stable2.diff > I like the patch. Since only RTL8169 family uses mask 0xfc800000 it would be even better we can limit checking scope for RTL8169SC by comparing PCI device id. I don't know what other side effect would happen if the mask 0xfc800000 would be used on 8101/8168 controllers. If the patch works on RTL8169SC would you commit the patch? I'd like to see multiple commits separated by each enhancements as the patch contains several fixes which are not directly related with the issue. -- Regards, Pyun YongHyeon From owner-freebsd-stable@FreeBSD.ORG Tue Jan 20 02:57: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 9B08A1065672 for ; Tue, 20 Jan 2009 02:57:45 +0000 (UTC) (envelope-from jamesbrandongooch@gmail.com) Received: from mail-bw0-f19.google.com (mail-bw0-f19.google.com [209.85.218.19]) by mx1.freebsd.org (Postfix) with ESMTP id E14728FC0C for ; Tue, 20 Jan 2009 02:57:44 +0000 (UTC) (envelope-from jamesbrandongooch@gmail.com) Received: by bwz12 with SMTP id 12so8832411bwz.4 for ; Mon, 19 Jan 2009 18:57:43 -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:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=IKikGm0JyPKks+l4G+XXCYZtTh61m3FUag8iUswhIf0=; b=xj05mekA7bOh2Wpz8U00GOinl1UT53S8meisZ3MpepfHUVfK0vXtEbqeO6dzhC6wV1 J1G95A/hq8QbhDbnxe9hbM0oP7pxnB4P9/nz9SH+f2J+xoOZZnmYw0ZXBWuWkLzL5AwL 93ILEiuG1SaSnYzjZUxQMUWrXU3980+D6OMfI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=awhqT3SyapWm52j+Z8QORAfJYyZ/7nwYdDMq3PqrNlPWdO00coXaw1WTFtYuwg25uw BRJ/8GpEGZwik+/Jkn/kyvdN5pkWp7uN0q1aPA+JWXQ9UktZksFN96u7OWVgmrH0IXIf O7TzEiAWZxYAnvWMkEJ3LXhkcoOpsyCmen+ig= Received: by 10.181.24.14 with SMTP id b14mr2306750bkj.104.1232420263629; Mon, 19 Jan 2009 18:57:43 -0800 (PST) Received: by 10.181.222.16 with HTTP; Mon, 19 Jan 2009 18:57:43 -0800 (PST) Message-ID: <179b97fb0901191857h2a7ee52cq36767089acaaa04c@mail.gmail.com> Date: Mon, 19 Jan 2009 20:57:43 -0600 From: "Brandon Gooch" To: "Damian Gerow" , "stable-list freebsd" In-Reply-To: <20090120013823.GA62274@plebeian.afflictions.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4973AE61.2040805@janh.de> <4974B4B2.5020308@freebsd.org> <20090120013823.GA62274@plebeian.afflictions.org> Cc: Subject: Re: iwn driver on 7.1 [no vaps in RELENG_7] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jan 2009 02:57:45 -0000 On Mon, Jan 19, 2009 at 7:38 PM, Damian Gerow wrote: > Sam Leffler wrote: > : OTOH iwn is now out of date and someone needs to update it. There's > : newer firmware that is supposed to fix many of the bugs I hit when I > : worked on the driver (and Intel refused to acknowledge) and obsd has > : added support for newer parts that people want. It'd be great if > : someone wanted to take over this driver. > > I've been working on this driver for the past few weeks (Christmas provided > a healthy distraction), but it's a steep learning curve for a novice C > coder. If anyone wants to work on this, let me know, as I have a small > portion of the work already done. > > - Damian > _______________________________________________ > 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'd like to work on this as well. I just pulled down the iwn code from OpenBSD current a little while ago and started hacking on it. I haven't made a lot of progress, so I'll gladly work with you on it. I'm a decent C programmer, but my lack of knowledge of kernel internals, functions, and data structures is my stumbling block. That's one of the main reasons I'm all about getting this driver working -- it gives me yet another chance to get into the kernel source and learn something new. Where do we begin? From owner-freebsd-stable@FreeBSD.ORG Tue Jan 20 03:04: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 035231065672 for ; Tue, 20 Jan 2009 03:04:28 +0000 (UTC) (envelope-from rock_on_the_web@comcen.com.au) Received: from angel.comcen.com.au (angel.comcen.com.au [203.23.236.69]) by mx1.freebsd.org (Postfix) with ESMTP id C18838FC08 for ; Tue, 20 Jan 2009 03:04:27 +0000 (UTC) (envelope-from rock_on_the_web@comcen.com.au) Received: from [192.168.0.199] (unknown [202.172.126.254]) by angel.comcen.com.au (Postfix) with ESMTP id C3C0D5C2F460 for ; Tue, 20 Jan 2009 13:50:02 +1100 (EST) From: Da Rock To: freebsd-stable@freebsd.org In-Reply-To: <20090120013823.GA62274@plebeian.afflictions.org> References: <4973AE61.2040805@janh.de> <4974B4B2.5020308@freebsd.org> <20090120013823.GA62274@plebeian.afflictions.org> Content-Type: text/plain Date: Tue, 20 Jan 2009 12:48:24 +1000 Message-Id: <1232419704.1138.57.camel@laptop2.herveybayaustralia.com.au> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Subject: Re: iwn driver on 7.1 [no vaps in RELENG_7] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jan 2009 03:04:28 -0000 On Mon, 2009-01-19 at 20:38 -0500, Damian Gerow wrote: > Sam Leffler wrote: > : OTOH iwn is now out of date and someone needs to update it. There's > : newer firmware that is supposed to fix many of the bugs I hit when I > : worked on the driver (and Intel refused to acknowledge) and obsd has > : added support for newer parts that people want. It'd be great if > : someone wanted to take over this driver. > > I've been working on this driver for the past few weeks (Christmas provided > a healthy distraction), but it's a steep learning curve for a novice C > coder. If anyone wants to work on this, let me know, as I have a small > portion of the work already done. > > - Damian I'm willing to work on it (doing so now), but from what you have said here it sounds like you're in the same boat as myself as I'm very new to this too :) What about collaboration between us with a Freebsd core team mentor? Is this possible? Code, test, then send the new code through the core team member for approval as well as hints to get the job done? From owner-freebsd-stable@FreeBSD.ORG Tue Jan 20 03:24: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 640BE106564A for ; Tue, 20 Jan 2009 03:24:49 +0000 (UTC) (envelope-from jamesbrandongooch@gmail.com) Received: from mail-bw0-f17.google.com (mail-bw0-f17.google.com [209.85.218.17]) by mx1.freebsd.org (Postfix) with ESMTP id B2F2C8FC0A for ; Tue, 20 Jan 2009 03:24:48 +0000 (UTC) (envelope-from jamesbrandongooch@gmail.com) Received: by bwz10 with SMTP id 10so83600bwz.19 for ; Mon, 19 Jan 2009 19:24: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:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=MiGShLZOomi0HquB4VK4bSFBaeG0C9FpDvddEZ3MaTg=; b=wVmvYqeBGuKLCwcsEwtT+uRQsi3Nsq31E4keBC2Axfg34+NL4S8vUvB0mnsjMd7Q68 BhynXX9DFjNfLV/dQ57ADRecCdpn2h+6C/WDLgHLBvmZUaibYxyCsHwKErJbsr/tZZ99 5LA3OlgAchUbCawgZyWYPxkagb99Nz6w9+rZo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=YKiTtBt6a8ry+t8srdptLb9Fn+jIHkntFtQuzCv3lpKfUPUCncvg5mkEwQqUfWjVX4 AOevXqBjz4ijZGVmEK9UY0e4k9LjsuLAKmkqJtZt97bQ5SV46iOi6qvol0tGx3KBLDtg Kyj3hnYHI1Qoa1x1VQc9rybj5PkEzaTX7YQfM= Received: by 10.181.145.7 with SMTP id x7mr2310228bkn.177.1232421887676; Mon, 19 Jan 2009 19:24:47 -0800 (PST) Received: by 10.181.222.16 with HTTP; Mon, 19 Jan 2009 19:24:47 -0800 (PST) Message-ID: <179b97fb0901191924s5646189ctfc9e08f4bc531937@mail.gmail.com> Date: Mon, 19 Jan 2009 21:24:47 -0600 From: "Brandon Gooch" To: "Da Rock" , "stable-list freebsd" In-Reply-To: <1232419704.1138.57.camel@laptop2.herveybayaustralia.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4973AE61.2040805@janh.de> <4974B4B2.5020308@freebsd.org> <20090120013823.GA62274@plebeian.afflictions.org> <1232419704.1138.57.camel@laptop2.herveybayaustralia.com.au> Cc: Subject: Re: iwn driver on 7.1 [no vaps in RELENG_7] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jan 2009 03:24:49 -0000 On Mon, Jan 19, 2009 at 8:48 PM, Da Rock wrote: > On Mon, 2009-01-19 at 20:38 -0500, Damian Gerow wrote: >> Sam Leffler wrote: >> : OTOH iwn is now out of date and someone needs to update it. There's >> : newer firmware that is supposed to fix many of the bugs I hit when I >> : worked on the driver (and Intel refused to acknowledge) and obsd has >> : added support for newer parts that people want. It'd be great if >> : someone wanted to take over this driver. >> >> I've been working on this driver for the past few weeks (Christmas provided >> a healthy distraction), but it's a steep learning curve for a novice C >> coder. If anyone wants to work on this, let me know, as I have a small >> portion of the work already done. >> >> - Damian > > I'm willing to work on it (doing so now), but from what you have said > here it sounds like you're in the same boat as myself as I'm very new to > this too :) > > What about collaboration between us with a Freebsd core team mentor? Is > this possible? Code, test, then send the new code through the core team > member for approval as well as hints to get the job done? > > _______________________________________________ > 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 don't know how mentoring works in the FreeBSD world or if a canonical process of mentoring even exists, but I would definitely be willing to participate. I know it would be a heck of a lot better than hacking around on this stuff by myself. -Brandon From owner-freebsd-stable@FreeBSD.ORG Tue Jan 20 03:54: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 935D01065674 for ; Tue, 20 Jan 2009 03:54:41 +0000 (UTC) (envelope-from rock_on_the_web@comcen.com.au) Received: from angel.comcen.com.au (angel.comcen.com.au [203.23.236.69]) by mx1.freebsd.org (Postfix) with ESMTP id 5A7F88FC14 for ; Tue, 20 Jan 2009 03:54:41 +0000 (UTC) (envelope-from rock_on_the_web@comcen.com.au) Received: from [192.168.0.199] (unknown [202.172.126.254]) by angel.comcen.com.au (Postfix) with ESMTP id 059D15C2F197 for ; Tue, 20 Jan 2009 14:56:01 +1100 (EST) From: Da Rock To: freebsd-stable@freebsd.org In-Reply-To: <179b97fb0901191924s5646189ctfc9e08f4bc531937@mail.gmail.com> References: <4973AE61.2040805@janh.de> <4974B4B2.5020308@freebsd.org> <20090120013823.GA62274@plebeian.afflictions.org> <1232419704.1138.57.camel@laptop2.herveybayaustralia.com.au> <179b97fb0901191924s5646189ctfc9e08f4bc531937@mail.gmail.com> Content-Type: text/plain Date: Tue, 20 Jan 2009 13:54:23 +1000 Message-Id: <1232423663.1138.66.camel@laptop2.herveybayaustralia.com.au> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Subject: Re: iwn driver on 7.1 [no vaps in RELENG_7] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jan 2009 03:54:42 -0000 On Mon, 2009-01-19 at 21:24 -0600, Brandon Gooch wrote: > On Mon, Jan 19, 2009 at 8:48 PM, Da Rock wrote: > > On Mon, 2009-01-19 at 20:38 -0500, Damian Gerow wrote: > >> Sam Leffler wrote: > >> : OTOH iwn is now out of date and someone needs to update it. There's > >> : newer firmware that is supposed to fix many of the bugs I hit when I > >> : worked on the driver (and Intel refused to acknowledge) and obsd has > >> : added support for newer parts that people want. It'd be great if > >> : someone wanted to take over this driver. > >> > >> I've been working on this driver for the past few weeks (Christmas provided > >> a healthy distraction), but it's a steep learning curve for a novice C > >> coder. If anyone wants to work on this, let me know, as I have a small > >> portion of the work already done. > >> > >> - Damian > > > > I'm willing to work on it (doing so now), but from what you have said > > here it sounds like you're in the same boat as myself as I'm very new to > > this too :) > > > > What about collaboration between us with a Freebsd core team mentor? Is > > this possible? Code, test, then send the new code through the core team > > member for approval as well as hints to get the job done? > > > > _______________________________________________ > > 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 don't know how mentoring works in the FreeBSD world or if a > canonical process of mentoring even exists, but I would definitely be > willing to participate. I know it would be a heck of a lot better than > hacking around on this stuff by myself. > > -Brandon Ok then, as you said- where do we start? From what I can see in the running of the card currently is its having trouble scanning- but they maybe a ruse, I'm trying to find a way to definitively determine what is going on here. Also, once the card has started scanning it locks up and appears to 'reset' or something, so that when I run wpa_supplicant the next time round it works again- but still won't scan. I'll just run through what I did yesterday again and post the results, but I believe those results from yesterday are already there on the -questions@ list if you wish to jump the gun. I'm currently looking along the lines of what people are running atm- it just clicked with me that my card is 4965AGN, but most reference this card as BGN, so I'm wondering if thats making a difference. From owner-freebsd-stable@FreeBSD.ORG Tue Jan 20 04:03: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 8EF08106564A; Tue, 20 Jan 2009 04:03:59 +0000 (UTC) (envelope-from pete@altadena.net) Received: from kestrel.altadena.net (kestrel.altadena.net [207.136.131.34]) by mx1.freebsd.org (Postfix) with ESMTP id 734268FC1C; Tue, 20 Jan 2009 04:03:59 +0000 (UTC) (envelope-from pete@altadena.net) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=1.kestrel; d=altadena.net; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:X-Enigmail-Version:Content-Type:Content-Transfer-Encoding; b=pyXqvADQ7zsjZZJiJ1kRzhji7Gy7QFRMsnNogkIgBYINnYlXIm3muCxOk2MnvA8cgiafjOA2VScR8g34juVaDZ/376VjHsPhTrB4HX5WEL4ph79cXxR8teZ6kxSqzDWvARyZXOLHAoEVV3aIGFOofMBe12pbE3PrWY83xz+gMq4=; Received: from c-69-137-63-84.hsd1.md.comcast.net ([69.137.63.84] helo=port3.altadena.net) by kestrel.altadena.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1LP7qI-000GBk-Uk; Mon, 19 Jan 2009 20:03:59 -0800 Message-ID: <49754D2D.2030902@altadena.net> Date: Mon, 19 Jan 2009 23:03:57 -0500 From: Pete Carah User-Agent: Thunderbird 2.0.0.19 (X11/20090111) MIME-Version: 1.0 To: Kris Kennaway References: <49747F10.7050801@altadena.net> <4974EC4C.4020004@FreeBSD.org> In-Reply-To: <4974EC4C.4020004@FreeBSD.org> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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, 20 Jan 2009 04:03:59 -0000 Well, following up on my own reply earlier, I csup'd releng_7 with a date of last dec 1; the result works fine in the laptop. I'll reload the eastern soekris tonight and see how it does. If the soekris is fine also then this gives a data point for whenever the bad commit(s) happened. I had apparently made the mistaken assumption that a general release should be better debugged than the work-in-progress leading up to it... As I noted before - I'm in the business of *using* computers, not doing fbsd kernel work (I actually do linux kernel (device driver) work in $dayjob, but so far prefer fbsd for general use, like routers and servers.) I need to regen the soekris config here with the 12.01 also; if it doesn't hang either then I can hope that someone can look through commit notes (I certainly don't have the time or internal knowledge of 7.x to do so) and try figure out what may have happened. My daughter is tired of rebooting the soekris that is 2800 miles west of here. One extra data point: the systems that work OK with the release code have Intel chipsets (older - ich3 and ich5). The laptop is an AMD64 in 32-bit mode with an ATI chipset and broadcom wireless (hence uses project evil, which has its own problems with hangs). Soekris is Geode SC1100 with its own builtin "chipset", presumably a mish-mash of things from Cyrix, National, and AMD, given the Geode series's history. It is not possible to gen a system or kernel on the soekris; gcc 4.x won't run in 128mb of ram with no swap (they run from cf cards; swap is not possible.) I have to cross-compile them and reload the cf cards externally if possible; if not I use nfs (which breaks the system badly if it hangs during a make install; this happened this past weekend, fortunately not on the other coast :-( -- Pete From owner-freebsd-stable@FreeBSD.ORG Tue Jan 20 04: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 745DD1065675 for ; Tue, 20 Jan 2009 04:15:28 +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 E295F8FC0C for ; Tue, 20 Jan 2009 04:15:27 +0000 (UTC) (envelope-from amarat@ksu.ru) X-IronPort-AV: E=Sophos;i="4.37,293,1231102800"; d="scan'208";a="1250972" Received: from mail.ksu.ru (HELO ruby.ksu.ru) ([193.232.252.56]) by iout.kzn.ru with ESMTP; 20 Jan 2009 07:15:25 +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 n0K4C3KO008083; Tue, 20 Jan 2009 04:12:03 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 n0K4EPLY021744; Tue, 20 Jan 2009 07:14:25 +0300 (MSK) (envelope-from amarat@ksu.ru) Message-ID: <49754FA1.3070004@ksu.ru> Date: Tue, 20 Jan 2009 07:14:25 +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: "Marat N.Afanasyev" References: <496D374A.3020704@langille.org> <496E9A37.20800@langille.org> <496EA339.6010808@ksu.ru> <496EB43A.8010805@langille.org> <496ECB2A.8080609@ksu.ru> In-Reply-To: <496ECB2A.8080609@ksu.ru> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: pyunyh@gmail.com, freebsd-stable@freebsd.org, Dan Langille 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jan 2009 04:15:28 -0000 Marat N.Afanasyev wrote: > 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 :( > still no luck with fixing dsdt. I tried to build a custom dsdt, tried to set hw.acpi.osname="Linux" in /boot/loader.conf, nothing changes. so it may be related with APIC, not dsdt only. So, if anyone has any idea how to find out what is happening, please tell me, we'll try to fix this. Probably Pyun will give us some advice, wouldn't you? :) Or should I make a problem report? -- SY, Marat From owner-freebsd-stable@FreeBSD.ORG Tue Jan 20 07:08: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 E378B1065670 for ; Tue, 20 Jan 2009 07:08:34 +0000 (UTC) (envelope-from ubm@u-boot-man.de) Received: from mail.upper.net (mail.upper.net [62.75.224.33]) by mx1.freebsd.org (Postfix) with ESMTP id 7E3548FC14 for ; Tue, 20 Jan 2009 07:08:34 +0000 (UTC) (envelope-from ubm@u-boot-man.de) Received: from ubm.mine.nu (mail.upper.net [62.75.224.33]) (authenticated bits=0) by mail.upper.net (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id n0K78TD4028731 for ; Tue, 20 Jan 2009 08:08:30 +0100 Received: from ubm.mine.nu ([85.181.0.109] helo=ubm.mine.nu) by ASSP.nospam; 20 Jan 2009 08:08:29 +0100 Date: Tue, 20 Jan 2009 08:08:29 +0100 From: Marc "UBM" Bocklet To: freebsd-stable@freebsd.org Message-Id: <20090120080829.b4006877.ubm@u-boot-man.de> In-Reply-To: <49750137.7020105@modulus.org> References: <20090119202016.11f42e3b.ubm.freebsd@gmail.com> <49750137.7020105@modulus.org> X-Mailer: Sylpheed 2.6.0 (GTK+ 2.12.10; i386-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: problems with sata disks (taskqueue timeout) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Jan 2009 07:08:35 -0000 On Tue, 20 Jan 2009 09:39:51 +1100 Andrew Snow wrote: > > I think that if you use eSATA you probably need dedicated eSATA > controller ports. eSATA standard specifies a higher voltage for the > longer cable distances. > > Judging from the sporadic problem reports, Promise TX4 is probably > not the best at signal purity to begin with so using it for eSATA > pushes it over the edge. > > > Hope that helps, Thanks for the fast answer! :-) Although my version of the TX4 has two dedicated e-sata ports, the other posts seem to indicate that it got something to do with the controller (maybe signal purity, like you said). I'll try upgrading next and will report back after that. Bye Marc From owner-freebsd-stable@FreeBSD.ORG Tue Jan 20 09:16: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 E9A47106566B for ; Tue, 20 Jan 2009 09:16:43 +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 6BF368FC08 for ; Tue, 20 Jan 2009 09:16:43 +0000 (UTC) (envelope-from admin@kkip.pl) Received: from admin.admin.lan.kkip.pl ([10.66.3.254]) by mainframe.kkip.pl with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LPCGl-0006W6-Bx; Tue, 20 Jan 2009 09:47:39 +0100 Message-ID: <49758FA7.3060606@kkip.pl> Date: Tue, 20 Jan 2009 09:47:35 +0100 From: Bartosz Stec User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Marc UBM References: <20090119202016.11f42e3b.ubm.freebsd@gmail.com> In-Reply-To: <20090119202016.11f42e3b.ubm.freebsd@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-Spam-Score: -8.9 X-Spam-Score-Int: -88 X-Exim-Version: 4.69 (build at 14-Jan-2009 11:48:13) X-Date: 2009-01-20 09:47:39 X-Connected-IP: 10.66.3.254:2488 X-Message-Linecount: 144 X-Body-Linecount: 130 X-Message-Size: 5178 X-Body-Size: 4593 X-Received-Count: 1 X-Recipient-Count: 2 X-Local-Recipient-Count: 2 X-Local-Recipient-Defer-Count: 0 X-Local-Recipient-Fail-Count: 0 Cc: freebsd-stable@freebsd.org Subject: Re: problems with sata disks (taskqueue timeout) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Jan 2009 09:16:44 -0000 Marc UBM pisze: > Hiho! :-) > > Occasionally, especially when uploading a large number of files, the > (brand-new, tested) sata disks in my fileserver spit out some of these > errors: > > ----------------------- > > Jan 19 19:51:14 hamstor kernel: ad10: WARNING - WRITE_DMA48 UDMA ICRC > error (retrying request) LBA=882778752 > > Jan 19 19:51:23 hamstor kernel: > ad10: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - > completing request directly > > Jan 19 19:51:27 hamstor kernel: ad10: > WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing > request directly > > Jan 19 19:51:31 hamstor kernel: ad10: WARNING - > SETFEATURES ENABLE WCACHE taskqueue timeout - completing request > directly > > Jan 19 19:51:35 hamstor kernel: ad10: WARNING - SET_MULTI > taskqueue timeout - completing request directly > > Jan 19 19:51:35 hamstor > kernel: ad10: TIMEOUT - WRITE_DMA48 retrying (0 retries left) > LBA=882778752 > > Jan 19 19:51:35 hamstor kernel: ad10: FAILURE - > WRITE_DMA48 > status=ff > error=ff > LBA=882778752 > > Jan 19 19:51:35 hamstor root: ZFS: vdev I/O failure, > zpool=gedaerm path=/dev/ad10 offset=451982655488 size=131072 error=5 > > Jan 19 19:51:41 hamstor kernel: ad10: FAILURE - SET_MULTI > status=51 error=4 > > Jan 19 19:51:41 hamstor > kernel: ad10: TIMEOUT - WRITE_DMA48 retrying (1 retry left) > LBA=882779008 > > Jan 19 19:51:41 hamstor kernel: ad10: WARNING - > WRITE_DMA48 UDMA ICRC error (retrying request) LBA=882779008 Jan 19 > 19:51:50 hamstor kernel: ad10: WARNING - SETFEATURES SET TRANSFER MODE > taskqueue timeout - completing request directly > > Jan 19 19:51:54 hamstor > kernel: ad10: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout > - completing request directly > > Jan 19 19:51:58 hamstor kernel: ad10: > WARNING - SETFEATURES ENABLE WCACHE taskqueue timeout - completing > request directly > > Jan 19 19:52:02 hamstor kernel: ad10: WARNING - > SET_MULTI taskqueue timeout - completing request directly Jan 19 > 19:52:02 hamstor kernel: ad10: FAILURE - WRITE_DMA48 timed out > LBA=882779008 > > Jan 19 19:52:02 hamstor root: ZFS: vdev I/O failure, > zpool=gedaerm path=/dev/ad10 offset=451982786560 size=131072 error=5 > > ----------------------- > > I've fiddled with the cables, which seemed to help, but I've been > unable to completely eliminate the errors. The disks are two Western > Digital MyBooks Home Edition (1 TB per disk), connected to a Promise TX > 4 SATA Controller: > > atapci0@pci0:1:6:0: class=0x018000 card=0x3d17105a chip=0x3d17105a > rev=0x02 hdr=0x00 vendor = 'Promise Technology Inc' > device = 'PDC40718-GP SATA 300 TX4 Controller' > class = mass storage > > They're connected via 50cm esata cables. > > I've googled on the net and found some vague hints about problems with > the Promise TX4, but nothing concrete. > > What I've found is > > http://wiki.freebsd.org/JeremyChadwick/ATA_issues_and_troubleshooting > > basically telling me "these things happen, deal with it" :-) > > The problem is, I cannot produce these problems reliably, only thing I > notice is that they *seem* to happen more often if a lot of large files > are copied in succession. > > Can anybody tell me if upgrading to 7.2 oder -current will help? > > I'm currently running > > 7.0-STABLE-200804 FreeBSD 7.0-STABLE-200804 #0: Wed Dec 10 15:29:03 CET > 2008 ***@host:/usr/obj/usr/src/sys/GENERIC amd64 > > Next step I'll try is upgrading to RELENG_7 to see if that helps. > > > Greetings, > Marc > Cheers Marc. My personal experience makes me think that this issue is controller/driver related. I'm using SATA 300 TX4 Controller from times of 6.1-Relaese on my fileserver (with 2 of 4 ports used) and I saw a lot of exactly the same errors in logs. Sometimes it was harmless, but sometimes as an effect of these one of disks magically disconnected from controller and only way to get it back and working was power down and up PC. That mostly happened while heavy I/O like while dumping filesystems. Good thing is that starting from 7.0-release I saw such errors maybe 2-3 times and I didn't saw them at all from at least 6 months. Probably because I rebuild my system about once a month to keep up with stable branch and something was corrected in sources through that time. So I also advice to upgrade to RELENG_7 and you probably get rid of these. Good luck! -- Bartosz Stec From owner-freebsd-stable@FreeBSD.ORG Tue Jan 20 11:12: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 2AB06106566C for ; Tue, 20 Jan 2009 11:12:08 +0000 (UTC) (envelope-from markir@paradise.net.nz) Received: from smtp5.clear.net.nz (smtp5.clear.net.nz [203.97.33.68]) by mx1.freebsd.org (Postfix) with ESMTP id EA40E8FC0C for ; Tue, 20 Jan 2009 11:12:07 +0000 (UTC) (envelope-from markir@paradise.net.nz) Received: from zmori.markir.net (121-73-164-72.dsl.telstraclear.net [121.73.164.72]) by smtp5.clear.net.nz (CLEAR Net Mail) with ESMTP id <0KDR00JGKNQSTH00@smtp5.clear.net.nz> for FreeBSD-stable@FreeBSD.org; Tue, 20 Jan 2009 23:56:53 +1300 (NZDT) Date: Tue, 20 Jan 2009 23:56:52 +1300 From: Mark Kirkwood In-reply-to: <20090109171857.GA49752@marvin.eastcentral.edu> To: Reuben Message-id: <4975ADF4.1070103@paradise.net.nz> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7bit References: <20090109171857.GA49752@marvin.eastcentral.edu> User-Agent: Thunderbird 2.0.0.19 (X11/20090117) Cc: FreeBSD-stable@FreeBSD.org Subject: Re: Broken loader on 7.1-STABLE? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jan 2009 11:12:08 -0000 Reuben wrote: > > I was wondering if anyone else was seeing loader (v1.02) break after updating from 7.1-RELEASE to 7.1-STABLE. After performing the prescribed updating procedure (via the handbook), the system will go through the normal steps and after the boot menu will present the following error: > > Can't work out which disk we are booting from. > Guessed BIOS device 0xffffffff not found by probes, defaulting to disk0 > > According to the bugbusting page on the FreeBSD wiki there's two issues at work that cause this behavior; patches were committed to HEAD/RELENG earlier last year in Mar and Aug. Up until now I've never come across this problem in 6.x or 7.0. In doing a little research I've come across a few older threads via google where it was believed that the problem was caused by improper CFLAGS in make.conf. I've commented mine out and rebuilt things.. with the same end result. In fact, if it's any help, my CFLAGS declaration in make.conf is taken verbatim from the /usr/share/examples/etc/make.conf. Furthermore, on selecting option 6 from the boot menu (escape to loader prompt), the system [I'm assuming] crashes displaying a blinking ASCII pattern from which only a hard reboot will work. > > FWIW, this is a fairly plain system.. nothing special in sysctl.conf or loader.conf, and the kernel is pretty stock as well (more or less GENERIC with my sound device and pf). > > A temporary fix for me was to copy over loader.old to loader in /boot. > > > I am getting this too - update from RELENG_7 @12 Jan src to 20 Jan and I have: panic: free: guard1 fail @ 0x511d from /usr/src/sys/boot/i386/loader/../../common/module.c:959 Can't work out which disk we are booting from. Guessed BIOS device 0xffffffff not found by probes, defaulting to disk0 Copying loader.old to loader did not work around this for me - I had to empty loader.conf too. Here is what *was* in there: ---> begin loader.conf # Sound sound_load="YES" snd_hda_load="YES" # IPC kern.ipc.semmni=500 kern.ipc.semmns=500 # CD/DVD DMA atapicam_load="YES" hw.ata.atapi_dma=0 --> end loader.conf At this point I am not sure which if are the bad guys... The machine is an Asus a8vx. regards Mark From owner-freebsd-stable@FreeBSD.ORG Tue Jan 20 11:39: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 B7DC51065673 for ; Tue, 20 Jan 2009 11:39:09 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from kagate.punkt.de (kagate.punkt.de [217.29.33.131]) by mx1.freebsd.org (Postfix) with ESMTP id 4960C8FC16 for ; Tue, 20 Jan 2009 11:39:09 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from hugo10.ka.punkt.de (hugo10.ka.punkt.de [10.0.0.110]) by kagate2.punkt.de with ESMTP id n0KBRUXW064874 for ; Tue, 20 Jan 2009 12:27:30 +0100 (CET) Received: from hugo10.ka.punkt.de (localhost [127.0.0.1]) by hugo10.ka.punkt.de (8.14.2/8.14.2) with ESMTP id n0KBRUg0019451 for ; Tue, 20 Jan 2009 12:27:30 +0100 (CET) (envelope-from ry93@hugo10.ka.punkt.de) Received: (from ry93@localhost) by hugo10.ka.punkt.de (8.14.2/8.14.2/Submit) id n0KBRU3k019450 for freebsd-stable@freebsd.org; Tue, 20 Jan 2009 12:27:30 +0100 (CET) (envelope-from ry93) Date: Tue, 20 Jan 2009 12:27:30 +0100 From: "Patrick M. Hausen" To: freebsd-stable@freebsd.org Message-ID: <20090120112730.GA19241@hugo10.ka.punkt.de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.5.17 (2007-11-01) Subject: LSI SAS3442e supported in 6.4 or 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, 20 Jan 2009 11:39:10 -0000 Hello, seems like I cannot find out if this card is supported or not. LSI provide drivers for Windows and Linux as usual, and mfi(4) doesn't mention that particular one. But possibly it's of the "MegaRAID Firmware Interface" type that mfi(4) supports? Unfortunately for a particular server model this controller is the only one our vendor (Fujitsu Siemens) offers. Thanks for any hints, Patrick -- punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe Tel. 0721 9109 0 * Fax 0721 9109 100 info@punkt.de http://www.punkt.de Gf: Jürgen Egeling AG Mannheim 108285 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 20 11:56: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 7BFD21065675 for ; Tue, 20 Jan 2009 11:56:20 +0000 (UTC) (envelope-from pluknet@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 0E96C8FC21 for ; Tue, 20 Jan 2009 11:56:19 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: by fg-out-1718.google.com with SMTP id l26so1859138fgb.35 for ; Tue, 20 Jan 2009 03:56:19 -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=dBPxxGgI/hedRroSrYrwANAit4ZfHzu45JnPZirpk4o=; b=i0YTxRlLudaJbzP3WdDD1/b+IfPP5cVoqXgMyb4DKC7gryR/RjgQKRDZ4ePQl4XxpE YIoZRM4Tp0TMy9KrCUzAHvW4vmesD++OEIZno69wMn1Dd1k3shDgZF9tr3I5tIwqwsJA 4yCd3eYV2AAeIUNYZK78SRZgp1nl/exP+6+j0= 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=AQUMrqgi1TfP+9tYT3JRRkumZJDXagNuYTh13oE8lOuPRX/Xhda+o+rSzPBwjFbroi A3tiU2ZRy5amonjRdWYNaEAwytgyPo9DDB/y+PCdUP0OuZ0pRTI+2kOAJyXZTbsabEFR namdNzCIpsKdl8Zfo6rURbHxiMe2o4Ij8V0uc= MIME-Version: 1.0 Received: by 10.86.25.17 with SMTP id 17mr699212fgy.6.1232452578188; Tue, 20 Jan 2009 03:56:18 -0800 (PST) In-Reply-To: <20090119224750.GA7463@keltia.freenix.fr> References: <20090119224750.GA7463@keltia.freenix.fr> Date: Tue, 20 Jan 2009 14:56:18 +0300 Message-ID: From: pluknet To: Ollivier Robert Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: SYSV* mandatory for COMPAT_IA32 on amd64? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jan 2009 11:56:21 -0000 2009/1/20 Ollivier Robert : > I must have missed the HEADS-UP or something but it seems that the SYSV IPC > options are now mandatory in order to compile an amd64 kernel with > COMPAT_IA32... I get linking errors in kernel.debug because > freebsd32_syscalls.o is referencing the SYSV syscalls... > > Am I alone? To clarify: I.e. on older versions you had no errors with COMPAT_IA32 and without SYSV* ? -- wbr, pluknet From owner-freebsd-stable@FreeBSD.ORG Tue Jan 20 13:20:51 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 63F771065726 for ; Tue, 20 Jan 2009 13:20: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 2FC518FC26 for ; Tue, 20 Jan 2009 13:20:51 +0000 (UTC) (envelope-from dan@langille.org) Received: from localhost (localhost [127.0.0.1]) by nyi.unixathome.org (Postfix) with ESMTP id B43B6509DB; Tue, 20 Jan 2009 13:20: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 kHoBJCKr1VMY; Tue, 20 Jan 2009 13:20:49 +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 00A7E509DD ; Tue, 20 Jan 2009 13:20:48 +0000 (GMT) Message-Id: From: Dan Langille To: Marat N.Afanasyev In-Reply-To: <49754FA1.3070004@ksu.ru> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Tue, 20 Jan 2009 08:20:47 -0500 References: <496D374A.3020704@langille.org> <496E9A37.20800@langille.org> <496EA339.6010808@ksu.ru> <496EB43A.8010805@langille.org> <496ECB2A.8080609@ksu.ru> <49754FA1.3070004@ksu.ru> X-Mailer: Apple Mail (2.930.3) Cc: pyunyh@gmail.com, 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jan 2009 13:20:57 -0000 On Jan 19, 2009, at 11:14 PM, Marat N.Afanasyev wrote: > Marat N.Afanasyev wrote: >> 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 :( > still no luck with fixing dsdt. I tried to build a custom dsdt, > tried to set hw.acpi.osname="Linux" in /boot/loader.conf, nothing > changes. so it may be related with APIC, not dsdt only. So, if > anyone has any idea how to find out what is happening, please tell > me, we'll try to fix this. > > Probably Pyun will give us some advice, wouldn't you? :) > > Or should I make a problem report? Please. -- Dan Langille http://langille.org/ From owner-freebsd-stable@FreeBSD.ORG Tue Jan 20 13:39: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 9F2F11065674 for ; Tue, 20 Jan 2009 13:39:29 +0000 (UTC) (envelope-from wendell@ramenzoni.com.br) Received: from monarco.ramenzoni.com.br (monarco.ramenzoni.com.br [200.178.230.133]) by mx1.freebsd.org (Postfix) with ESMTP id C1A558FC1D for ; Tue, 20 Jan 2009 13:39:28 +0000 (UTC) (envelope-from wendell@ramenzoni.com.br) Received: (qmail 40627 invoked by uid 98); 20 Jan 2009 11:12:46 -0200 Received: from 200.178.230.134 (wendell@200.178.230.134) by monarco.ramenzoni.com.br (envelope-from , uid 82) with qmail-scanner-2.01 (clamdscan: 0.94.2/8728. spamassassin: 3.2.5. Clear:RC:1(200.178.230.134):. Processed in 0.066802 secs); 20 Jan 2009 13:12:46 -0000 Received: from firewall.ramenzoni.com.br (HELO ?192.168.112.8?) (wendell@200.178.230.134) by 0 with ESMTPA; 20 Jan 2009 11:12:46 -0200 Message-Id: <5F259223-D531-4E25-9814-C0C90250707D@ramenzoni.com.br> From: Wendell Martins Borges To: freebsd-stable@freebsd.org Mime-Version: 1.0 (Apple Message framework v930.3) Date: Tue, 20 Jan 2009 11:12:45 -0200 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 Subject: aliases not working in em0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Jan 2009 13:39:30 -0000 I had a 7.0 server and my card worked fine, upgraded to 7.1 and aliases stopped working, below some information from my server. # uname -a FreeBSD stewie.ramenzoni.com.br 7.1-RELEASE FreeBSD 7.1-RELEASE #0: Thu Jan 1 14:37:25 UTC 2009 root@logan.cse.buffalo.edu:/usr/obj/ usr/src/sys/GENERIC i386 # ifconfig em0 em0: flags=8843 metric 0 mtu 1500 options=9b ether 00:15:17:16:bf:9a inet 192.168.112.1 netmask 0xffffff00 broadcast 192.168.112.255 inet 192.168.112.181 netmask 0xffffffff broadcast 192.168.112.181 media: Ethernet autoselect (100baseTX ) status: active # cat /etc/rc.conf ifconfig_em0="inet 192.168.112.1 netmask 255.255.255.0" ifconfig_em0_alias0="inet 192.168.112.181 netmask 255.255.255.255" # pciconf -vl em0@pci0:1:0:0: class=0x020000 card=0x10848086 chip=0x107d8086 rev=0x06 hdr=0x00 vendor = 'Intel Corporation' device = 'PRO/1000 PT' class = network subclass = ethernet # dmesg | grep em0 em0: port 0xece0-0xecff mem 0xfe9e0000-0xfe9fffff,0xfe9c0000-0xfe9dffff irq 16 at device 0.0 on pci1 em0: Using MSI interrupt em0: [FILTER] em0: Ethernet address: 00:15:17:16:bf:9a -- best regards, Wendell Martins Borges Administrador de Redes e Sistemas Inds. Papel R. Ramenzoni S/A From owner-freebsd-stable@FreeBSD.ORG Tue Jan 20 13:43: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 26650106564A for ; Tue, 20 Jan 2009 13:43:55 +0000 (UTC) (envelope-from steve@ibctech.ca) Received: from ibctech.ca (v6.ibctech.ca [IPv6:2607:f118::b6]) by mx1.freebsd.org (Postfix) with SMTP id AEE278FC18 for ; Tue, 20 Jan 2009 13:43:54 +0000 (UTC) (envelope-from steve@ibctech.ca) Received: (qmail 84462 invoked by uid 89); 20 Jan 2009 13:57:48 -0000 Received: from unknown (HELO ?IPv6:2607:f118::5?) (steve@ibctech.ca@2607:f118::5) by 2607:f118::b6 with ESMTPA; 20 Jan 2009 13:57:48 -0000 Message-ID: <4975D50B.2030307@ibctech.ca> Date: Tue, 20 Jan 2009 08:43:39 -0500 From: Steve Bertrand User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: Wendell Martins Borges References: <5F259223-D531-4E25-9814-C0C90250707D@ramenzoni.com.br> In-Reply-To: <5F259223-D531-4E25-9814-C0C90250707D@ramenzoni.com.br> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: aliases not working in em0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Jan 2009 13:43:55 -0000 Wendell Martins Borges wrote: > I had a 7.0 server and my card worked fine, upgraded to 7.1 and aliases > stopped working, below some information from my server. > > # uname -a > FreeBSD stewie.ramenzoni.com.br 7.1-RELEASE FreeBSD 7.1-RELEASE #0: Thu > Jan 1 14:37:25 UTC 2009 > root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 > > # ifconfig em0 > > em0: flags=8843 metric 0 mtu 1500 > options=9b > ether 00:15:17:16:bf:9a > inet 192.168.112.1 netmask 0xffffff00 broadcast 192.168.112.255 > inet 192.168.112.181 netmask 0xffffffff broadcast 192.168.112.181 > media: Ethernet autoselect (100baseTX ) > status: active > > # cat /etc/rc.conf > > ifconfig_em0="inet 192.168.112.1 netmask 255.255.255.0" > ifconfig_em0_alias0="inet 192.168.112.181 netmask 255.255.255.255" I'm confused. Given the /etc/rc.conf settings, the above ifconfig output appears to be exactly what I would expect. What is not working? Steve From owner-freebsd-stable@FreeBSD.ORG Tue Jan 20 13:47: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 A57EA10656BF for ; Tue, 20 Jan 2009 13:47:35 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from kagate.punkt.de (kagate.punkt.de [217.29.33.131]) by mx1.freebsd.org (Postfix) with ESMTP id 34C2D8FC0C for ; Tue, 20 Jan 2009 13:47:34 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from hugo10.ka.punkt.de (hugo10.ka.punkt.de [10.0.0.110]) by kagate2.punkt.de with ESMTP id n0KDlYjx066406 for ; Tue, 20 Jan 2009 14:47:34 +0100 (CET) Received: from hugo10.ka.punkt.de (localhost [127.0.0.1]) by hugo10.ka.punkt.de (8.14.2/8.14.2) with ESMTP id n0KDlXNY023923; Tue, 20 Jan 2009 14:47:33 +0100 (CET) (envelope-from ry93@hugo10.ka.punkt.de) Received: (from ry93@localhost) by hugo10.ka.punkt.de (8.14.2/8.14.2/Submit) id n0KDlX8W023922; Tue, 20 Jan 2009 14:47:33 +0100 (CET) (envelope-from ry93) Date: Tue, 20 Jan 2009 14:47:33 +0100 From: "Patrick M. Hausen" To: Wendell Martins Borges Message-ID: <20090120134733.GB22114@hugo10.ka.punkt.de> References: <5F259223-D531-4E25-9814-C0C90250707D@ramenzoni.com.br> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <5F259223-D531-4E25-9814-C0C90250707D@ramenzoni.com.br> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-stable@freebsd.org Subject: Re: aliases not working in em0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Jan 2009 13:47:36 -0000 Hello, On Tue, Jan 20, 2009 at 11:12:45AM -0200, Wendell Martins Borges wrote: > ifconfig_em0="inet 192.168.112.1 netmask 255.255.255.0" > ifconfig_em0_alias0="inet 192.168.112.181 netmask 255.255.255.255" I don't know if this can be the cause of your problem, but the /32 netmask for aliases has been deprecated quite a while ago. Try: ipv4_addrs_em0="192.168.112.1/24 192.168.112.181/24" Kind regards, Patrick -- punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe Tel. 0721 9109 0 * Fax 0721 9109 100 info@punkt.de http://www.punkt.de Gf: Jürgen Egeling AG Mannheim 108285 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 20 13:47:48 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 90D861065822 for ; Tue, 20 Jan 2009 13:47:48 +0000 (UTC) (envelope-from lankfordandrew@charter.net) Received: from mta21.charter.net (mta21.charter.net [216.33.127.81]) by mx1.freebsd.org (Postfix) with ESMTP id 266548FC1A for ; Tue, 20 Jan 2009 13:47:48 +0000 (UTC) (envelope-from lankfordandrew@charter.net) Received: from aarprv04.charter.net ([10.20.200.74]) by mta21.charter.net (InterMail vM.7.09.01.00 201-2219-108-20080618) with ESMTP id <20090120134742.PONV7559.mta21.charter.net@aarprv04.charter.net>; Tue, 20 Jan 2009 08:47:42 -0500 Received: from [192.168.1.151] (really [68.191.116.244]) by aarprv04.charter.net with ESMTP id <20090120134742.QPDE25639.aarprv04.charter.net@[192.168.1.151]>; Tue, 20 Jan 2009 08:47:42 -0500 Message-ID: <4975D5FE.4090406@charter.net> Date: Tue, 20 Jan 2009 08:47:42 -0500 From: Andrew Lankford User-Agent: Thunderbird 2.0.0.19 (X11/20090111) MIME-Version: 1.0 To: Bruce Simpson , stable@freebsd.org References: <49729D80.8010506@charter.net> <20090118093346.GA9819@onelab2.iet.unipi.it> <49734D0B.8050604@charter.net> <4975A535.4000202@incunabulum.net> In-Reply-To: <4975A535.4000202@incunabulum.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Chzlrs: 0 Cc: Subject: Re: System borked: loader stack overflow. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Jan 2009 13:47:50 -0000 I suppose that was what was required with XP (normally used boot0, but tinkered with using windows boot as an alternate method), but I haven't had to update boot1 since I first installed everything on this laptop ...so far. Andrew Lankford Bruce Simpson wrote: > Andrew Lankford wrote: >> >> >> FYI: I'm using the Windows Vista boot manager with boot1 instead of >> boot0, although boot1 doesn't appear to have changed since I first >> installed 7.0 on my notebook. > > grub4dos is good, means you don't need to keep dd'ing the boot1 out of > the FreeBSD slice. > From owner-freebsd-stable@FreeBSD.ORG Tue Jan 20 13:49: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 F149D106579D for ; Tue, 20 Jan 2009 13:49:42 +0000 (UTC) (envelope-from wendell@ramenzoni.com.br) Received: from monarco.ramenzoni.com.br (monarco.ramenzoni.com.br [200.178.230.133]) by mx1.freebsd.org (Postfix) with ESMTP id 19AB88FC12 for ; Tue, 20 Jan 2009 13:49:41 +0000 (UTC) (envelope-from wendell@ramenzoni.com.br) Received: (qmail 44264 invoked by uid 98); 20 Jan 2009 11:49:40 -0200 Received: from 200.178.230.134 (wendell@200.178.230.134) by monarco.ramenzoni.com.br (envelope-from , uid 82) with qmail-scanner-2.01 (clamdscan: 0.94.2/8728. spamassassin: 3.2.5. Clear:RC:1(200.178.230.134):. Processed in 0.068033 secs); 20 Jan 2009 13:49:40 -0000 Received: from firewall.ramenzoni.com.br (HELO ?192.168.112.8?) (wendell@200.178.230.134) by 0 with ESMTPA; 20 Jan 2009 11:49:40 -0200 Message-Id: <9600F322-8884-486E-B594-497A2FBFECD2@ramenzoni.com.br> From: Wendell Martins Borges To: Steve Bertrand In-Reply-To: <4975D50B.2030307@ibctech.ca> Mime-Version: 1.0 (Apple Message framework v930.3) Date: Tue, 20 Jan 2009 11:49:40 -0200 References: <5F259223-D531-4E25-9814-C0C90250707D@ramenzoni.com.br> <4975D50B.2030307@ibctech.ca> 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: aliases not working in em0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Jan 2009 13:49:45 -0000 On 20/01/2009, at 11:43, Steve Bertrand wrote: > I'm confused. Given the /etc/rc.conf settings, the above ifconfig > output > appears to be exactly what I would expect. > > What is not working? > > Steve Hi Steve, The settings are really OK. However after the update does not can access the alias of IP inside my network. thanks for the reply -- best regards, Wendell Martins Borges Administrador de Redes e Sistemas Inds. Papel R. Ramenzoni S/A From owner-freebsd-stable@FreeBSD.ORG Tue Jan 20 13:52: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 2645A1065714 for ; Tue, 20 Jan 2009 13:52:34 +0000 (UTC) (envelope-from steve@ibctech.ca) Received: from ibctech.ca (v6.ibctech.ca [IPv6:2607:f118::b6]) by mx1.freebsd.org (Postfix) with SMTP id A952E8FC24 for ; Tue, 20 Jan 2009 13:52:33 +0000 (UTC) (envelope-from steve@ibctech.ca) Received: (qmail 84877 invoked by uid 89); 20 Jan 2009 14:06:27 -0000 Received: from unknown (HELO ?IPv6:2607:f118::5?) (steve@ibctech.ca@2607:f118::5) by 2607:f118::b6 with ESMTPA; 20 Jan 2009 14:06:27 -0000 Message-ID: <4975D712.2080101@ibctech.ca> Date: Tue, 20 Jan 2009 08:52:18 -0500 From: Steve Bertrand User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: "Patrick M. Hausen" References: <5F259223-D531-4E25-9814-C0C90250707D@ramenzoni.com.br> <20090120134733.GB22114@hugo10.ka.punkt.de> In-Reply-To: <20090120134733.GB22114@hugo10.ka.punkt.de> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Wendell Martins Borges Subject: Re: aliases not working in em0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Jan 2009 13:52:37 -0000 Patrick M. Hausen wrote: > Hello, > > On Tue, Jan 20, 2009 at 11:12:45AM -0200, Wendell Martins Borges wrote: > >> ifconfig_em0="inet 192.168.112.1 netmask 255.255.255.0" >> ifconfig_em0_alias0="inet 192.168.112.181 netmask 255.255.255.255" > > I don't know if this can be the cause of your problem, but > the /32 netmask for aliases has been deprecated quite a while > ago. For how long? On a 7.0-R box, it works ok with a /32 prefix len: %ifconfig re0: flags=8843 metric 0 mtu 1500 options=9b ether 00:0f:b5:80:53:85 inet 208.70.104.210 netmask 0xffffff00 broadcast 255.255.255.192 inet 208.70.104.211 netmask 0xffffff00 broadcast 255.255.255.255 inet6 2607:f118::b6 prefixlen 64 inet6 2607:f118::b7 prefixlen 64 media: Ethernet autoselect (1000baseTX ) status: active %ping 208.70.104.211 PING 208.70.104.211 (208.70.104.211): 56 data bytes 64 bytes from 208.70.104.211: icmp_seq=0 ttl=64 time=0.079 ms ^C I'll try it on one of my 7.1 boxes to see if I can reproduce the OP's issue. Steve From owner-freebsd-stable@FreeBSD.ORG Tue Jan 20 14:00: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 44A1F1065670 for ; Tue, 20 Jan 2009 14:00:40 +0000 (UTC) (envelope-from steve@ibctech.ca) Received: from ibctech.ca (v6.ibctech.ca [IPv6:2607:f118::b6]) by mx1.freebsd.org (Postfix) with SMTP id 06A9E8FC13 for ; Tue, 20 Jan 2009 14:00:39 +0000 (UTC) (envelope-from steve@ibctech.ca) Received: (qmail 85091 invoked by uid 89); 20 Jan 2009 14:14:34 -0000 Received: from unknown (HELO ?IPv6:2607:f118::5?) (steve@ibctech.ca@2607:f118::5) by 2607:f118::b6 with ESMTPA; 20 Jan 2009 14:14:34 -0000 Message-ID: <4975D8F9.9000700@ibctech.ca> Date: Tue, 20 Jan 2009 09:00:25 -0500 From: Steve Bertrand User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: "Patrick M. Hausen" References: <5F259223-D531-4E25-9814-C0C90250707D@ramenzoni.com.br> <20090120134733.GB22114@hugo10.ka.punkt.de> <4975D712.2080101@ibctech.ca> In-Reply-To: <4975D712.2080101@ibctech.ca> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Wendell Martins Borges Subject: Re: aliases not working in em0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Jan 2009 14:00:40 -0000 Steve Bertrand wrote: > Patrick M. Hausen wrote: >> Hello, >> >> On Tue, Jan 20, 2009 at 11:12:45AM -0200, Wendell Martins Borges wrote: >> >>> ifconfig_em0="inet 192.168.112.1 netmask 255.255.255.0" >>> ifconfig_em0_alias0="inet 192.168.112.181 netmask 255.255.255.255" >> I don't know if this can be the cause of your problem, but >> the /32 netmask for aliases has been deprecated quite a while >> ago. > > For how long? On a 7.0-R box, it works ok with a /32 prefix len: > > %ifconfig > re0: flags=8843 metric 0 mtu 1500 > options=9b > ether 00:0f:b5:80:53:85 > inet 208.70.104.210 netmask 0xffffff00 broadcast 255.255.255.192 > inet 208.70.104.211 netmask 0xffffff00 broadcast 255.255.255.255 > inet6 2607:f118::b6 prefixlen 64 > inet6 2607:f118::b7 prefixlen 64 > media: Ethernet autoselect (1000baseTX ) > status: active > > %ping 208.70.104.211 > PING 208.70.104.211 (208.70.104.211): 56 data bytes > 64 bytes from 208.70.104.211: icmp_seq=0 ttl=64 time=0.079 ms > ^C > > I'll try it on one of my 7.1 boxes to see if I can reproduce the OP's issue. Interestingly enough, it does work here: vm# uname -a FreeBSD ww3.eagle.ca 7.1-RELEASE FreeBSD 7.1-RELEASE #0: Thu Jan 1 14:37:25 UTC 2009 root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 vm# ifconfig le0 le0: flags=8843 metric 0 mtu 1500 options=8 ether 00:0c:29:31:e7:11 inet6 fe80::20c:29ff:fe31:e711%le0 prefixlen 64 scopeid 0x1 inet 208.70.104.27 netmask 0xffffff80 broadcast 208.70.104.127 inet 208.70.104.29 netmask 0xffffffff broadcast 208.70.104.29 ...and from another box: pearl# ping 208.70.104.29 PING 208.70.104.29 (208.70.104.29): 56 data bytes 64 bytes from 208.70.104.29: icmp_seq=0 ttl=63 time=1.275 ms ^C Wendell, what does #netstat -rn say? Also, if you run tcpdump listening on the alias IP address, do you see the ingress traffic from the remote workstations? ie: # tcpdump -n -i em0 host 192.168.112.181 Steve From owner-freebsd-stable@FreeBSD.ORG Tue Jan 20 14:12: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 4B43D10656C1 for ; Tue, 20 Jan 2009 14:12:26 +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 08F788FC17 for ; Tue, 20 Jan 2009 14:12:25 +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 753C019E019; Tue, 20 Jan 2009 15:12:24 +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 00D9019E023; Tue, 20 Jan 2009 15:12:18 +0100 (CET) Message-ID: <4975DBF9.6000608@quip.cz> Date: Tue, 20 Jan 2009 15:13:13 +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: "Patrick M. Hausen" References: <5F259223-D531-4E25-9814-C0C90250707D@ramenzoni.com.br> <20090120134733.GB22114@hugo10.ka.punkt.de> In-Reply-To: <20090120134733.GB22114@hugo10.ka.punkt.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Wendell Martins Borges Subject: Re: aliases not working in em0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Jan 2009 14:12:26 -0000 Patrick M. Hausen wrote: > Hello, > > On Tue, Jan 20, 2009 at 11:12:45AM -0200, Wendell Martins Borges wrote: > > >>ifconfig_em0="inet 192.168.112.1 netmask 255.255.255.0" >>ifconfig_em0_alias0="inet 192.168.112.181 netmask 255.255.255.255" > > > I don't know if this can be the cause of your problem, but > the /32 netmask for aliases has been deprecated quite a while > ago. Can you point me to some doc about this? Manpage for ifconfig still say: "If the address is on the same subnet as the first network address for this interface, a non-conflicting netmask must be given. Usually 0xffffffff is most appropriate." Miroslav Lachman From owner-freebsd-stable@FreeBSD.ORG Tue Jan 20 14:22: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 A288D1065670 for ; Tue, 20 Jan 2009 14:22:10 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from kagate.punkt.de (kagate.punkt.de [217.29.33.131]) by mx1.freebsd.org (Postfix) with ESMTP id 2FA458FC17 for ; Tue, 20 Jan 2009 14:22:09 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from hugo10.ka.punkt.de (hugo10.ka.punkt.de [10.0.0.110]) by kagate2.punkt.de with ESMTP id n0KEM9DW066718 for ; Tue, 20 Jan 2009 15:22:09 +0100 (CET) Received: from hugo10.ka.punkt.de (localhost [127.0.0.1]) by hugo10.ka.punkt.de (8.14.2/8.14.2) with ESMTP id n0KEM88R025048; Tue, 20 Jan 2009 15:22:08 +0100 (CET) (envelope-from ry93@hugo10.ka.punkt.de) Received: (from ry93@localhost) by hugo10.ka.punkt.de (8.14.2/8.14.2/Submit) id n0KEM82g025047; Tue, 20 Jan 2009 15:22:08 +0100 (CET) (envelope-from ry93) Date: Tue, 20 Jan 2009 15:22:08 +0100 From: "Patrick M. Hausen" To: Steve Bertrand Message-ID: <20090120142208.GA24949@hugo10.ka.punkt.de> References: <5F259223-D531-4E25-9814-C0C90250707D@ramenzoni.com.br> <20090120134733.GB22114@hugo10.ka.punkt.de> <4975D712.2080101@ibctech.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <4975D712.2080101@ibctech.ca> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-stable@freebsd.org, Wendell Martins Borges Subject: Re: aliases not working in em0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Jan 2009 14:22:11 -0000 Hi, all, On Tue, Jan 20, 2009 at 08:52:18AM -0500, Steve Bertrand wrote: > For how long? On a 7.0-R box, it works ok with a /32 prefix len: > > %ifconfig > re0: flags=8843 metric 0 mtu 1500 > options=9b > ether 00:0f:b5:80:53:85 > inet 208.70.104.210 netmask 0xffffff00 broadcast 255.255.255.192 > inet 208.70.104.211 netmask 0xffffff00 broadcast 255.255.255.255 Did you manually edit the ifconfig output? The broadcast addresses should both be 208.70.104.255 for the shown prefixes and netmasks. And I don't see a /32 here, either. Kind regards, Patrick -- punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe Tel. 0721 9109 0 * Fax 0721 9109 100 info@punkt.de http://www.punkt.de Gf: Jürgen Egeling AG Mannheim 108285 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 20 14:26: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 3D63C1065675 for ; Tue, 20 Jan 2009 14:26:57 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from mail-gw1.york.ac.uk (mail-gw1.york.ac.uk [144.32.128.246]) by mx1.freebsd.org (Postfix) with ESMTP id C70BC8FC19 for ; Tue, 20 Jan 2009 14:26:56 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from mail-gw7.york.ac.uk (mail-gw7.york.ac.uk [144.32.129.30]) by mail-gw1.york.ac.uk (8.13.6/8.13.6) with ESMTP id n0KEQpXl015732; Tue, 20 Jan 2009 14:26: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 1LPHZ5-0000YZ-QC; Tue, 20 Jan 2009 14:26: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 n0KEQnvN064298; Tue, 20 Jan 2009 14:26:49 GMT (envelope-from gavin@FreeBSD.org) Received: (from ga9@localhost) by buffy.york.ac.uk (8.14.2/8.14.2/Submit) id n0KEQf4s064247; Tue, 20 Jan 2009 14:26:41 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: Wendell Martins Borges In-Reply-To: <5F259223-D531-4E25-9814-C0C90250707D@ramenzoni.com.br> References: <5F259223-D531-4E25-9814-C0C90250707D@ramenzoni.com.br> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Tue, 20 Jan 2009 14:26:41 +0000 Message-Id: <1232461601.22840.28.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: aliases not working in em0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Jan 2009 14:26:57 -0000 On Tue, 2009-01-20 at 11:12 -0200, Wendell Martins Borges wrote: > I had a 7.0 server and my card worked fine, upgraded to 7.1 and > aliases stopped working, below some information from my server. > > # uname -a > FreeBSD stewie.ramenzoni.com.br 7.1-RELEASE FreeBSD 7.1-RELEASE #0: > Thu Jan 1 14:37:25 UTC 2009 root@logan.cse.buffalo.edu:/usr/obj/ > usr/src/sys/GENERIC i386 > > # ifconfig em0 > > em0: flags=8843 metric 0 mtu > 1500 > options=9b > ether 00:15:17:16:bf:9a > inet 192.168.112.1 netmask 0xffffff00 broadcast 192.168.112.255 > inet 192.168.112.181 netmask 0xffffffff broadcast > 192.168.112.181 > media: Ethernet autoselect (100baseTX ) > status: active > > # cat /etc/rc.conf > > ifconfig_em0="inet 192.168.112.1 netmask 255.255.255.0" > ifconfig_em0_alias0="inet 192.168.112.181 netmask 255.255.255.255" Can you try the following: ping -S 192.168.112.181 host and then try pinging 192.168.112.181 from the host? I'm wondering if it is the old "em fails to send gratuitous arp on alias addition" problem, back again. Also, run "tcpdump -vvvxXs0 -i em0 host 192.168.112.181" on the host in question and try pinging it from a different host. Do you see anything? Gavin From owner-freebsd-stable@FreeBSD.ORG Tue Jan 20 14:30:01 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 4D50D1065679 for ; Tue, 20 Jan 2009 14:30:01 +0000 (UTC) (envelope-from steve@ibctech.ca) Received: from ibctech.ca (v6.ibctech.ca [IPv6:2607:f118::b6]) by mx1.freebsd.org (Postfix) with SMTP id CE0BB8FC1C for ; Tue, 20 Jan 2009 14:30:00 +0000 (UTC) (envelope-from steve@ibctech.ca) Received: (qmail 86047 invoked by uid 89); 20 Jan 2009 14:43:54 -0000 Received: from unknown (HELO ?IPv6:2607:f118::5?) (steve@ibctech.ca@2607:f118::5) by 2607:f118::b6 with ESMTPA; 20 Jan 2009 14:43:54 -0000 Message-ID: <4975DFD9.3050003@ibctech.ca> Date: Tue, 20 Jan 2009 09:29:45 -0500 From: Steve Bertrand User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: "Patrick M. Hausen" References: <5F259223-D531-4E25-9814-C0C90250707D@ramenzoni.com.br> <20090120134733.GB22114@hugo10.ka.punkt.de> <4975D712.2080101@ibctech.ca> <20090120142208.GA24949@hugo10.ka.punkt.de> In-Reply-To: <20090120142208.GA24949@hugo10.ka.punkt.de> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Wendell Martins Borges Subject: Re: aliases not working in em0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Jan 2009 14:30:02 -0000 Patrick M. Hausen wrote: > Hi, all, > > On Tue, Jan 20, 2009 at 08:52:18AM -0500, Steve Bertrand wrote: >> For how long? On a 7.0-R box, it works ok with a /32 prefix len: >> >> %ifconfig >> re0: flags=8843 metric 0 mtu 1500 >> options=9b >> ether 00:0f:b5:80:53:85 >> inet 208.70.104.210 netmask 0xffffff00 broadcast 255.255.255.192 >> inet 208.70.104.211 netmask 0xffffff00 broadcast 255.255.255.255 > > Did you manually edit the ifconfig output? The broadcast addresses > should both be 208.70.104.255 for the shown prefixes and netmasks. Hmmm... thats my bad. I have a fsck-up in my rc.conf on that box... ifconfig_re0="inet 208.70.104.210 255.255.255.192" ifconfig_re0_alias0="inet 208.70.104.211 255.255.255.255" I guess when one leaves out the 'netmask' keyword, the next parameter after the IP becomes the broadcast address. I'm actually quite surprised and perplexed as to how this box has been able to communicate to other prefixes on the network :) Thanks for the keen eye. You've most certainly saved me some future anguish! Steve From owner-freebsd-stable@FreeBSD.ORG Tue Jan 20 15:07: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 D89D810656EA for ; Tue, 20 Jan 2009 15:07:00 +0000 (UTC) (envelope-from bp@eden.barryp.org) Received: from itasca.hexavalent.net (itasca.hexavalent.net [67.207.138.180]) by mx1.freebsd.org (Postfix) with ESMTP id B4B728FC12 for ; Tue, 20 Jan 2009 15:07:00 +0000 (UTC) (envelope-from bp@eden.barryp.org) Received: from host-236-232-107-208.midco.net ([208.107.232.236] helo=eden.barryp.org) by itasca.hexavalent.net with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1LPHf8-0000gJ-NM for freebsd-stable@freebsd.org; Tue, 20 Jan 2009 08:33:06 -0600 Received: from macbook.home ([10.66.1.10]) by eden.barryp.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67 (FreeBSD)) (envelope-from ) id 1LPHf1-0006a3-Cm; Tue, 20 Jan 2009 08:32:59 -0600 Message-ID: <4975E09A.4090507@barryp.org> Date: Tue, 20 Jan 2009 08:32:58 -0600 From: Barry Pederson User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) MIME-Version: 1.0 To: "Patrick M. Hausen" References: <20090120112730.GA19241@hugo10.ka.punkt.de> In-Reply-To: <20090120112730.GA19241@hugo10.ka.punkt.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: LSI SAS3442e supported in 6.4 or 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, 20 Jan 2009 15:07:03 -0000 Patrick M. Hausen wrote: > Hello, > > seems like I cannot find out if this card is supported > or not. LSI provide drivers for Windows and Linux as > usual, and mfi(4) doesn't mention that particular one. > But possibly it's of the "MegaRAID Firmware Interface" > type that mfi(4) supports? > > Unfortunately for a particular server model this controller > is the only one our vendor (Fujitsu Siemens) offers. > > Thanks for any hints, > Patrick I think the mpt(4) driver covers that card. I've got a few similar LSI SAS cards that work fine with that on FreeBSD 7.0 (SAS3081E-R and SAS3041E-R I believe). Barry From owner-freebsd-stable@FreeBSD.ORG Tue Jan 20 15:14:19 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 97B21106564A for ; Tue, 20 Jan 2009 15:14:19 +0000 (UTC) (envelope-from wendell@ramenzoni.com.br) Received: from monarco.ramenzoni.com.br (monarco.ramenzoni.com.br [200.178.230.133]) by mx1.freebsd.org (Postfix) with ESMTP id 7A4D48FC38 for ; Tue, 20 Jan 2009 15:14:17 +0000 (UTC) (envelope-from wendell@ramenzoni.com.br) Received: (qmail 49773 invoked by uid 98); 20 Jan 2009 13:14:16 -0200 Received: from 200.178.230.134 (wendell@200.178.230.134) by monarco.ramenzoni.com.br (envelope-from , uid 82) with qmail-scanner-2.01 (clamdscan: 0.94.2/8728. spamassassin: 3.2.5. Clear:RC:1(200.178.230.134):. Processed in 0.076735 secs); 20 Jan 2009 15:14:16 -0000 Received: from firewall.ramenzoni.com.br (HELO ?192.168.112.8?) (wendell@200.178.230.134) by 0 with ESMTPA; 20 Jan 2009 13:14:16 -0200 Message-Id: <77290DC5-426C-4B5E-B718-94E1DCDC0B57@ramenzoni.com.br> From: Wendell Martins Borges To: freebsd-stable@freebsd.org In-Reply-To: <4975D8F9.9000700@ibctech.ca> Mime-Version: 1.0 (Apple Message framework v930.3) Date: Tue, 20 Jan 2009 13:14:15 -0200 References: <5F259223-D531-4E25-9814-C0C90250707D@ramenzoni.com.br> <20090120134733.GB22114@hugo10.ka.punkt.de> <4975D712.2080101@ibctech.ca> <4975D8F9.9000700@ibctech.ca> 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 Subject: Re: aliases not working in em0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Jan 2009 15:14:20 -0000 On 20/01/2009, at 12:00, Steve Bertrand wrote: > Wendell, what does #netstat -rn say? Also, if you run tcpdump > listening > on the alias IP address, do you see the ingress traffic from the > remote > workstations? ie: stewie# netstat -rn | grep 192.168.112.181 192.168.112.181 00:15:17:16:bf:9a UHLW 1 121 lo0 => 192.168.112.181/32 link#1 UC 0 0 em0 > > # tcpdump -n -i em0 host 192.168.112.181 ping for another host: stewie# tcpdump -n -i em0 host 192.168.112.181 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on em0, link-type EN10MB (Ethernet), capture size 96 bytes 13:11:21.530635 IP 192.168.112.8 > 192.168.112.181: ICMP echo request, id 11852, seq 0, length 64 13:11:22.530803 IP 192.168.112.8 > 192.168.112.181: ICMP echo request, id 11852, seq 1, length 64 13:11:23.530969 IP 192.168.112.8 > 192.168.112.181: ICMP echo request, id 11852, seq 2, length 64 trying to access via http 13:12:28.301445 IP 192.168.112.8.57630 > 192.168.112.181.80: S 1104784481:1104784481(0) win 65535 13:12:29.215662 IP 192.168.112.8.57630 > 192.168.112.181.80: S 1104784481:1104784481(0) win 65535 13:12:30.217078 IP 192.168.112.8.57630 > 192.168.112.181.80: S 1104784481:1104784481(0) win 65535 13:12:31.218369 IP 192.168.112.8.57630 > 192.168.112.181.80: S 1104784481:1104784481(0) win 65535 13:12:32.219786 IP 192.168.112.8.57630 > 192.168.112.181.80: S 1104784481:1104784481(0) win 65535 13:12:33.221201 IP 192.168.112.8.57630 > 192.168.112.181.80: S 1104784481:1104784481(0) win 65535 -- best regards, Wendell Martins Borges Administrador de Redes e Sistemas Inds. Papel R. Ramenzoni S/A From owner-freebsd-stable@FreeBSD.ORG Tue Jan 20 15:18: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 34766106564A for ; Tue, 20 Jan 2009 15:18:52 +0000 (UTC) (envelope-from wendell@ramenzoni.com.br) Received: from monarco.ramenzoni.com.br (monarco.ramenzoni.com.br [200.178.230.133]) by mx1.freebsd.org (Postfix) with ESMTP id 099C78FC17 for ; Tue, 20 Jan 2009 15:18:50 +0000 (UTC) (envelope-from wendell@ramenzoni.com.br) Received: (qmail 50313 invoked by uid 98); 20 Jan 2009 13:18:50 -0200 Received: from 200.178.230.134 (wendell@200.178.230.134) by monarco.ramenzoni.com.br (envelope-from , uid 82) with qmail-scanner-2.01 (clamdscan: 0.94.2/8728. spamassassin: 3.2.5. Clear:RC:1(200.178.230.134):. Processed in 0.084411 secs); 20 Jan 2009 15:18:50 -0000 Received: from firewall.ramenzoni.com.br (HELO ?192.168.112.8?) (wendell@200.178.230.134) by 0 with ESMTPA; 20 Jan 2009 13:18:49 -0200 Message-Id: <331F8138-1E86-435F-900A-47E3E5BE913D@ramenzoni.com.br> From: Wendell Martins Borges To: freebsd-stable@freebsd.org In-Reply-To: <1232461601.22840.28.camel@buffy.york.ac.uk> Mime-Version: 1.0 (Apple Message framework v930.3) Date: Tue, 20 Jan 2009 13:18:49 -0200 References: <5F259223-D531-4E25-9814-C0C90250707D@ramenzoni.com.br> <1232461601.22840.28.camel@buffy.york.ac.uk> 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 Subject: Re: aliases not working in em0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Jan 2009 15:18:52 -0000 On 20/01/2009, at 12:26, Gavin Atkinson wrote: > Can you try the following: > > ping -S 192.168.112.181 host > and then try pinging 192.168.112.181 from the host? stewie# ping -S 192.168.112.181 192.168.112.8 PING 192.168.112.8 (192.168.112.8) from 192.168.112.181: 56 data bytes 64 bytes from 192.168.112.8: icmp_seq=0 ttl=64 time=0.353 ms 64 bytes from 192.168.112.8: icmp_seq=1 ttl=64 time=0.388 ms 64 bytes from 192.168.112.8: icmp_seq=2 ttl=64 time=0.329 ms 64 bytes from 192.168.112.8: icmp_seq=3 ttl=64 time=0.382 ms 64 bytes from 192.168.112.8: icmp_seq=4 ttl=64 time=0.198 ms 64 bytes from 192.168.112.8: icmp_seq=5 ttl=64 time=0.364 ms ^C --- 192.168.112.8 ping statistics --- 6 packets transmitted, 6 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 0.198/0.336/0.388/0.065 ms mordor:~ wendell$ ping 192.168.112.181 PING 192.168.112.181 (192.168.112.181): 56 data bytes ^C --- 192.168.112.181 ping statistics --- 4 packets transmitted, 0 packets received, 100% packet loss > > > I'm wondering if it is the old "em fails to send gratuitous arp on > alias > addition" problem, back again. > > Also, run "tcpdump -vvvxXs0 -i em0 host 192.168.112.181" on the host > in > question and try pinging it from a different host. Do you see > anything? > stewie# tcpdump -nvvvxXs0 -i em0 host 192.168.112.181 tcpdump: listening on em0, link-type EN10MB (Ethernet), capture size 65535 bytes 13:18:20.479184 IP (tos 0x0, ttl 64, id 34240, offset 0, flags [none], proto ICMP (1), length 84) 192.168.112.8 > 192.168.112.181: ICMP echo request, id 18764, seq 0, length 64 0x0000: 4500 0054 85c0 0000 4001 92da c0a8 7008 E..T....@.....p. 0x0010: c0a8 70b5 0800 da85 494c 0000 3beb 7549 ..p.....IL..;.uI 0x0020: 34f6 0300 0809 0a0b 0c0d 0e0f 1011 1213 4............... 0x0030: 1415 1617 1819 1a1b 1c1d 1e1f 2021 2223 .............!"# 0x0040: 2425 2627 2829 2a2b 2c2d 2e2f 3031 3233 $%&'()*+,-./ 0123 0x0050: 3435 3637 4567 13:18:21.479226 IP (tos 0x0, ttl 64, id 25324, offset 0, flags [none], proto ICMP (1), length 84) 192.168.112.8 > 192.168.112.181: ICMP echo request, id 18764, seq 1, length 64 0x0000: 4500 0054 62ec 0000 4001 b5ae c0a8 7008 E..Tb...@.....p. 0x0010: c0a8 70b5 0800 8684 494c 0001 3ceb 7549 ..p.....IL..<.uI 0x0020: 87f6 0300 0809 0a0b 0c0d 0e0f 1011 1213 ................ 0x0030: 1415 1617 1819 1a1b 1c1d 1e1f 2021 2223 .............!"# 0x0040: 2425 2627 2829 2a2b 2c2d 2e2f 3031 3233 $%&'()*+,-./ 0123 0x0050: 3435 3637 4567 13:18:22.479392 IP (tos 0x0, ttl 64, id 61679, offset 0, flags [none], proto ICMP (1), length 84) 192.168.112.8 > 192.168.112.181: ICMP echo request, id 18764, seq 2, length 64 0x0000: 4500 0054 f0ef 0000 4001 27ab c0a8 7008 E..T....@.'...p. 0x0010: c0a8 70b5 0800 ef82 494c 0002 3deb 7549 ..p.....IL..=.uI 0x0020: 1df7 0300 0809 0a0b 0c0d 0e0f 1011 1213 ................ 0x0030: 1415 1617 1819 1a1b 1c1d 1e1f 2021 2223 .............!"# 0x0040: 2425 2627 2829 2a2b 2c2d 2e2f 3031 3233 $%&'()*+,-./ 0123 0x0050: 3435 3637 4567 13:18:23.479559 IP (tos 0x0, ttl 64, id 10446, offset 0, flags [none], proto ICMP (1), length 84) 192.168.112.8 > 192.168.112.181: ICMP echo request, id 18764, seq 3, length 64 0x0000: 4500 0054 28ce 0000 4001 efcc c0a8 7008 E..T(...@.....p. 0x0010: c0a8 70b5 0800 5081 494c 0003 3eeb 7549 ..p...P.IL..>.uI 0x0020: bbf7 0300 0809 0a0b 0c0d 0e0f 1011 1213 ................ 0x0030: 1415 1617 1819 1a1b 1c1d 1e1f 2021 2223 .............!"# 0x0040: 2425 2627 2829 2a2b 2c2d 2e2f 3031 3233 $%&'()*+,-./ 0123 0x0050: 3435 3637 4567 [ ]s -- best regards, Wendell Martins Borges Administrador de Redes e Sistemas Inds. Papel R. Ramenzoni S/A From owner-freebsd-stable@FreeBSD.ORG Tue Jan 20 15:22: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 271E01065731 for ; Tue, 20 Jan 2009 15:22:27 +0000 (UTC) (envelope-from steve@ibctech.ca) Received: from ibctech.ca (v6.ibctech.ca [IPv6:2607:f118::b6]) by mx1.freebsd.org (Postfix) with SMTP id 3AA368FC1D for ; Tue, 20 Jan 2009 15:22:25 +0000 (UTC) (envelope-from steve@ibctech.ca) Received: (qmail 87958 invoked by uid 89); 20 Jan 2009 15:36:18 -0000 Received: from unknown (HELO ?IPv6:2607:f118::5?) (steve@ibctech.ca@2607:f118::5) by 2607:f118::b6 with ESMTPA; 20 Jan 2009 15:36:18 -0000 Message-ID: <4975EC21.2040101@ibctech.ca> Date: Tue, 20 Jan 2009 10:22:09 -0500 From: Steve Bertrand User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: Wendell Martins Borges References: <5F259223-D531-4E25-9814-C0C90250707D@ramenzoni.com.br> <20090120134733.GB22114@hugo10.ka.punkt.de> <4975D712.2080101@ibctech.ca> <4975D8F9.9000700@ibctech.ca> <77290DC5-426C-4B5E-B718-94E1DCDC0B57@ramenzoni.com.br> In-Reply-To: <77290DC5-426C-4B5E-B718-94E1DCDC0B57@ramenzoni.com.br> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: aliases not working in em0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Jan 2009 15:22:28 -0000 Wendell Martins Borges wrote: >> # tcpdump -n -i em0 host 192.168.112.181 > > ping for another host: > > stewie# tcpdump -n -i em0 host 192.168.112.181 > tcpdump: verbose output suppressed, use -v or -vv for full protocol decode > listening on em0, link-type EN10MB (Ethernet), capture size 96 bytes > 13:11:21.530635 IP 192.168.112.8 > 192.168.112.181: ICMP echo request, > id 11852, seq 0, length 64 > 13:11:22.530803 IP 192.168.112.8 > 192.168.112.181: ICMP echo request, > id 11852, seq 1, length 64 So, the box can be found on the network, but it is not returning traffic properly. What does # arp -a have to say, on both boxes? Steve From owner-freebsd-stable@FreeBSD.ORG Tue Jan 20 15:24: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 ADCE5106566B for ; Tue, 20 Jan 2009 15:24:28 +0000 (UTC) (envelope-from dudu.meyer@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.30]) by mx1.freebsd.org (Postfix) with ESMTP id 6A15C8FC0C for ; Tue, 20 Jan 2009 15:24:28 +0000 (UTC) (envelope-from dudu.meyer@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so1365849ywe.13 for ; Tue, 20 Jan 2009 07:24:27 -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=GjtJ4MKEI0yfzcNIavTvjoa5P+4VnvpaQp5pdWwZBFI=; b=iKmGSxZMxLoFLN3jKhP7ms1dk8vKv5lepIfBymWqXbhKD56nQAeapmi4p3do9mGDdC 2YtD+C95fdRUQtEwR80YAcBdKGbL22D49Qo4a2gwusHo9dwNV6+S3BK0n/QJD11OjBdh WUbLD45eDUIIsCEFBIglOvSECr7Y7BSabGexE= 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=Jam0WyBrldZl2Xbux1VlQSzc9FuzPLvZtfNppBOSRwD0rPVWztQMeNMOo8+of3mpm4 jfKIZAUSnnF6ED7rMCrL3ChHn6JLQF/XN7VaF8YpiJOBQHcjZPmC1Yq7n30/g4DwsZUG Y4b5TGJLlG1tE/avrm+1NSvJXeRbiJC8ZTz+4= MIME-Version: 1.0 Received: by 10.142.141.21 with SMTP id o21mr2574506wfd.327.1232465067280; Tue, 20 Jan 2009 07:24:27 -0800 (PST) Date: Tue, 20 Jan 2009 13:24:27 -0200 Message-ID: From: Eduardo Meyer To: questions@freebsd.org, stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: switching bsdlabel's label X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Jan 2009 15:24:29 -0000 Hello, I have a certain disk where da0s1a and da0s1d are inverted. By some reason someone labelled root as 'd' and home as 'a'. Can I just bsdlabel -n da0s1 > savedabel.txt Edit savedlabel.txt, switch and restore? (bsdlabel -R da0s1 savedlabel) -- =========== Eduardo Meyer pessoal: dudu.meyer@gmail.com profissional: ddm.farmaciap@saude.gov.br From owner-freebsd-stable@FreeBSD.ORG Tue Jan 20 15:24: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 2F4CF10656C8 for ; Tue, 20 Jan 2009 15:24:42 +0000 (UTC) (envelope-from wendell@ramenzoni.com.br) Received: from monarco.ramenzoni.com.br (monarco.ramenzoni.com.br [200.178.230.133]) by mx1.freebsd.org (Postfix) with ESMTP id 7D46C8FC18 for ; Tue, 20 Jan 2009 15:24:41 +0000 (UTC) (envelope-from wendell@ramenzoni.com.br) Received: (qmail 50856 invoked by uid 98); 20 Jan 2009 13:24:40 -0200 Received: from 200.178.230.134 (wendell@200.178.230.134) by monarco.ramenzoni.com.br (envelope-from , uid 82) with qmail-scanner-2.01 (clamdscan: 0.94.2/8728. spamassassin: 3.2.5. Clear:RC:1(200.178.230.134):. Processed in 0.066792 secs); 20 Jan 2009 15:24:40 -0000 Received: from firewall.ramenzoni.com.br (HELO ?192.168.112.8?) (wendell@200.178.230.134) by 0 with ESMTPA; 20 Jan 2009 13:24:40 -0200 Message-Id: <512FEF10-0EC9-47C2-8028-F5792511BA57@ramenzoni.com.br> From: Wendell Martins Borges To: freebsd-stable@freebsd.org In-Reply-To: <4975EC21.2040101@ibctech.ca> Mime-Version: 1.0 (Apple Message framework v930.3) Date: Tue, 20 Jan 2009 13:24:39 -0200 References: <5F259223-D531-4E25-9814-C0C90250707D@ramenzoni.com.br> <20090120134733.GB22114@hugo10.ka.punkt.de> <4975D712.2080101@ibctech.ca> <4975D8F9.9000700@ibctech.ca> <77290DC5-426C-4B5E-B718-94E1DCDC0B57@ramenzoni.com.br> <4975EC21.2040101@ibctech.ca> 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 Subject: Re: aliases not working in em0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Jan 2009 15:24:43 -0000 On 20/01/2009, at 13:22, Steve Bertrand wrote: > So, the box can be found on the network, but it is not returning > traffic > properly. > > What does # arp -a have to say, on both boxes? stewie# arp -a stewie (192.168.112.1) at 00:15:17:16:bf:9a on em0 permanent [ethernet] cartola (192.168.112.181) at 00:15:17:16:bf:9a on em0 permanent [ethernet] -- Atenciosamente, Wendell Martins Borges Administrador de Redes e Sistemas Inds. Papel R. Ramenzoni S/A From owner-freebsd-stable@FreeBSD.ORG Tue Jan 20 15:25: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 C1D7B10656DC for ; Tue, 20 Jan 2009 15:25:37 +0000 (UTC) (envelope-from steve@ibctech.ca) Received: from ibctech.ca (v6.ibctech.ca [IPv6:2607:f118::b6]) by mx1.freebsd.org (Postfix) with SMTP id 1E4218FC21 for ; Tue, 20 Jan 2009 15:25:37 +0000 (UTC) (envelope-from steve@ibctech.ca) Received: (qmail 88042 invoked by uid 89); 20 Jan 2009 15:39:31 -0000 Received: from unknown (HELO ?IPv6:2607:f118::5?) (steve@ibctech.ca@2607:f118::5) by 2607:f118::b6 with ESMTPA; 20 Jan 2009 15:39:31 -0000 Message-ID: <4975ECE2.9030104@ibctech.ca> Date: Tue, 20 Jan 2009 10:25:22 -0500 From: Steve Bertrand User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: Wendell Martins Borges References: <5F259223-D531-4E25-9814-C0C90250707D@ramenzoni.com.br> <20090120134733.GB22114@hugo10.ka.punkt.de> <4975D712.2080101@ibctech.ca> <4975D8F9.9000700@ibctech.ca> <77290DC5-426C-4B5E-B718-94E1DCDC0B57@ramenzoni.com.br> <4975EC21.2040101@ibctech.ca> In-Reply-To: <4975EC21.2040101@ibctech.ca> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: aliases not working in em0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Jan 2009 15:25:38 -0000 Steve Bertrand wrote: > Wendell Martins Borges wrote: > >>> # tcpdump -n -i em0 host 192.168.112.181 >> ping for another host: >> >> stewie# tcpdump -n -i em0 host 192.168.112.181 >> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode >> listening on em0, link-type EN10MB (Ethernet), capture size 96 bytes >> 13:11:21.530635 IP 192.168.112.8 > 192.168.112.181: ICMP echo request, >> id 11852, seq 0, length 64 >> 13:11:22.530803 IP 192.168.112.8 > 192.168.112.181: ICMP echo request, >> id 11852, seq 1, length 64 > > So, the box can be found on the network, but it is not returning traffic > properly. > > What does # arp -a have to say, on both boxes? Also, it may help to run tcpdump without the 'host' parameter on em0 while the pinging is occurring to see if you can find out whether the ICMP replies are being sent out as the primary IP. Steve From owner-freebsd-stable@FreeBSD.ORG Tue Jan 20 15:34: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 DDAA610656BA for ; Tue, 20 Jan 2009 15:34:13 +0000 (UTC) (envelope-from wendell@ramenzoni.com.br) Received: from monarco.ramenzoni.com.br (monarco.ramenzoni.com.br [200.178.230.133]) by mx1.freebsd.org (Postfix) with ESMTP id CF01F8FC16 for ; Tue, 20 Jan 2009 15:34:12 +0000 (UTC) (envelope-from wendell@ramenzoni.com.br) Received: (qmail 51839 invoked by uid 98); 20 Jan 2009 13:34:11 -0200 Received: from 200.178.230.134 (wendell@200.178.230.134) by monarco.ramenzoni.com.br (envelope-from , uid 82) with qmail-scanner-2.01 (clamdscan: 0.94.2/8728. spamassassin: 3.2.5. Clear:RC:1(200.178.230.134):. Processed in 0.075016 secs); 20 Jan 2009 15:34:11 -0000 Received: from firewall.ramenzoni.com.br (HELO ?192.168.112.8?) (wendell@200.178.230.134) by 0 with ESMTPA; 20 Jan 2009 13:34:11 -0200 Message-Id: <502BA672-2861-47C1-8F01-8A5ACC7A6732@ramenzoni.com.br> From: Wendell Martins Borges To: freebsd-stable@freebsd.org In-Reply-To: <4975ECE2.9030104@ibctech.ca> Mime-Version: 1.0 (Apple Message framework v930.3) Date: Tue, 20 Jan 2009 13:34:10 -0200 References: <5F259223-D531-4E25-9814-C0C90250707D@ramenzoni.com.br> <20090120134733.GB22114@hugo10.ka.punkt.de> <4975D712.2080101@ibctech.ca> <4975D8F9.9000700@ibctech.ca> <77290DC5-426C-4B5E-B718-94E1DCDC0B57@ramenzoni.com.br> <4975EC21.2040101@ibctech.ca> <4975ECE2.9030104@ibctech.ca> 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 Subject: Re: aliases not working in em0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Jan 2009 15:34:14 -0000 On 20/01/2009, at 13:25, Steve Bertrand wrote: > Also, it may help to run tcpdump without the 'host' parameter on em0 > while the pinging is occurring to see if you can find out whether the > ICMP replies are being sent out as the primary IP. stewie# tcpdump -n -i em0 icmp tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on em0, link-type EN10MB (Ethernet), capture size 96 bytes 13:33:13.891786 IP 192.168.112.8 > 192.168.112.181: ICMP echo request, id 30284, seq 0, length 64 13:33:14.891704 IP 192.168.112.8 > 192.168.112.181: ICMP echo request, id 30284, seq 1, length 64 13:33:15.891870 IP 192.168.112.8 > 192.168.112.181: ICMP echo request, id 30284, seq 2, length 64 13:33:16.891912 IP 192.168.112.8 > 192.168.112.181: ICMP echo request, id 30284, seq 3, length 64 13:33:17.892079 IP 192.168.112.8 > 192.168.112.181: ICMP echo request, id 30284, seq 4, length 64 13:33:18.892252 IP 192.168.112.8 > 192.168.112.181: ICMP echo request, id 30284, seq 5, length 64 13:33:19.892412 IP 192.168.112.8 > 192.168.112.181: ICMP echo request, id 30284, seq 6, length 64 13:33:20.892580 IP 192.168.112.8 > 192.168.112.181: ICMP echo request, id 30284, seq 7, length 64 13:33:21.892621 IP 192.168.112.8 > 192.168.112.181: ICMP echo request, id 30284, seq 8, length 64 13:33:22.892787 IP 192.168.112.8 > 192.168.112.181: ICMP echo request, id 30284, seq 9, length 64 -- Atenciosamente, Wendell Martins Borges Administrador de Redes e Sistemas Inds. Papel R. Ramenzoni S/A From owner-freebsd-stable@FreeBSD.ORG Tue Jan 20 16:46: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 63A721065807; Tue, 20 Jan 2009 16:46:55 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from kagate.punkt.de (kagate.punkt.de [217.29.33.131]) by mx1.freebsd.org (Postfix) with ESMTP id 56D1D8FC4B; Tue, 20 Jan 2009 16:46:53 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from hugo10.ka.punkt.de (hugo10.ka.punkt.de [10.0.0.110]) by kagate2.punkt.de with ESMTP id n0KGDu6s067714; Tue, 20 Jan 2009 17:13:56 +0100 (CET) Received: from hugo10.ka.punkt.de (localhost [127.0.0.1]) by hugo10.ka.punkt.de (8.14.2/8.14.2) with ESMTP id n0KGDuRS028605; Tue, 20 Jan 2009 17:13:56 +0100 (CET) (envelope-from ry93@hugo10.ka.punkt.de) Received: (from ry93@localhost) by hugo10.ka.punkt.de (8.14.2/8.14.2/Submit) id n0KGDuOt028604; Tue, 20 Jan 2009 17:13:56 +0100 (CET) (envelope-from ry93) Date: Tue, 20 Jan 2009 17:13:56 +0100 From: "Patrick M. Hausen" To: Eduardo Meyer Message-ID: <20090120161355.GA28525@hugo10.ka.punkt.de> References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Cc: stable@freebsd.org, questions@freebsd.org Subject: Re: switching bsdlabel's label X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Jan 2009 16:47:19 -0000 Hello, On Tue, Jan 20, 2009 at 01:24:27PM -0200, Eduardo Meyer wrote: > I have a certain disk where da0s1a and da0s1d are inverted. By some > reason someone labelled root as 'd' and home as 'a'. > > Can I just > > bsdlabel -n da0s1 > savedabel.txt > > Edit savedlabel.txt, switch and restore? (bsdlabel -R da0s1 savedlabel) Why not simply use bsdlabel -e da0s1? Kind regards, Patrick -- punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe Tel. 0721 9109 0 * Fax 0721 9109 100 info@punkt.de http://www.punkt.de Gf: Jürgen Egeling AG Mannheim 108285 From owner-freebsd-stable@FreeBSD.ORG Tue Jan 20 17:36:36 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 1737F1065672; Tue, 20 Jan 2009 17:36:36 +0000 (UTC) (envelope-from dudu.meyer@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 AF1518FC13; Tue, 20 Jan 2009 17:36:35 +0000 (UTC) (envelope-from dudu.meyer@gmail.com) Received: by gxk14 with SMTP id 14so3812861gxk.19 for ; Tue, 20 Jan 2009 09:36:35 -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=IjQozoAZExgEYyREsLAK41zrfIgrzx+Rur6Yjrpfxdk=; b=bAn9fRXxA582TcY5s1aowJNw1FTTBgx8L+ey0iAps/Tx5avkwQtoq3wkxU01/9k2Tb Zy6jHjuLWHnzPvbMmhO14Fi/ObC9YYvxWHv8LuWcorwRFm0nNXeOX1V5KYyZ6aSJ8/ih T2i52N/+KFXDqZe+tXtZ6u8J0LGgN3KO8R3CU= 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=EblYOvOmxioKz/kspnnKrFbzrH38VmpKawC4JS5av55ZI6BmeA3UzqKwUxBV0x5ob5 6YdsSkFOrfOBPv6hn22+xX1J6mNa0wYJCkPZzHuu58FmdzpftjoMFiksKtc3w2T7TadV aOzJVepKtUS5NqNAGfFfQXQkSFLsU5rdgjeDI= MIME-Version: 1.0 Received: by 10.142.203.19 with SMTP id a19mr192960wfg.310.1232472994109; Tue, 20 Jan 2009 09:36:34 -0800 (PST) In-Reply-To: <20090120161355.GA28525@hugo10.ka.punkt.de> References: <20090120161355.GA28525@hugo10.ka.punkt.de> Date: Tue, 20 Jan 2009 15:36:34 -0200 Message-ID: From: Eduardo Meyer To: "Patrick M. Hausen" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: stable@freebsd.org, questions@freebsd.org Subject: Re: switching bsdlabel's label X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Jan 2009 17:36:36 -0000 On Tue, Jan 20, 2009 at 2:13 PM, Patrick M. Hausen wrote: > Hello, > > On Tue, Jan 20, 2009 at 01:24:27PM -0200, Eduardo Meyer wrote: >> I have a certain disk where da0s1a and da0s1d are inverted. By some >> reason someone labelled root as 'd' and home as 'a'. >> >> Can I just >> >> bsdlabel -n da0s1 > savedabel.txt >> >> Edit savedlabel.txt, switch and restore? (bsdlabel -R da0s1 savedlabel) > > Why not simply use bsdlabel -e da0s1? Because I didnt know about that? ;-) Thank you for the hint. However I still have the same doubt. Since basically its the same task, Is it safe do relabel this way? > > Kind regards, > Patrick > -- > punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe > Tel. 0721 9109 0 * Fax 0721 9109 100 > info@punkt.de http://www.punkt.de > Gf: J=FCrgen Egeling AG Mannheim 108285 > --=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Eduardo Meyer pessoal: dudu.meyer@gmail.com profissional: ddm.farmaciap@saude.gov.br From owner-freebsd-stable@FreeBSD.ORG Tue Jan 20 17:41:13 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 A0B12106564A for ; Tue, 20 Jan 2009 17:41:13 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by mx1.freebsd.org (Postfix) with ESMTP id 6CE258FC08 for ; Tue, 20 Jan 2009 17:41:13 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.14.3/8.14.3) with ESMTP id n0KHfCog080972; Tue, 20 Jan 2009 09:41:12 -0800 (PST) (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.14.3/8.14.3/Submit) id n0KHfCct080971; Tue, 20 Jan 2009 09:41:12 -0800 (PST) (envelope-from david) Date: Tue, 20 Jan 2009 09:41:12 -0800 From: David Wolfskill To: Eduardo Meyer Message-ID: <20090120174112.GS17567@albert.catwhisker.org> Mail-Followup-To: David Wolfskill , Eduardo Meyer , stable@freebsd.org, questions@freebsd.org References: <20090120161355.GA28525@hugo10.ka.punkt.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="HL+2C3YiDdBCOf2R" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: stable@freebsd.org, questions@freebsd.org Subject: Re: switching bsdlabel's label X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Jan 2009 17:41:13 -0000 --HL+2C3YiDdBCOf2R Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jan 20, 2009 at 03:36:34PM -0200, Eduardo Meyer wrote: > ... > > Why not simply use bsdlabel -e da0s1? >=20 > Because I didnt know about that? ;-) >=20 > Thank you for the hint. >=20 > However I still have the same doubt. Since basically its the same > task, Is it safe do relabel this way? I have done it several times without any problems. Do, however, ensure that your /etc/fstab entries match the result before you reboot; attempting a "mount" by hand (merely specifying either the mount point or the device, but not both) before your next reboot can serve as a useful reality check. Peace, david --=20 David H. Wolfskill david@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --HL+2C3YiDdBCOf2R Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkl2DLgACgkQmprOCmdXAD01UgCfUwuVN3vG7ZQ1j3vAsEVYKGhU /AgAnA/Hf7EuHcWHIpJjYVQwd/+C24Xa =lnT/ -----END PGP SIGNATURE----- --HL+2C3YiDdBCOf2R-- From owner-freebsd-stable@FreeBSD.ORG Tue Jan 20 17:42: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 59D8910656D0 for ; Tue, 20 Jan 2009 17:42:27 +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 BB7F48FC08 for ; Tue, 20 Jan 2009 17:42:26 +0000 (UTC) (envelope-from amarat@ksu.ru) X-IronPort-AV: E=Sophos;i="4.37,295,1231102800"; d="scan'208";a="1268416" Received: from mail.ksu.ru (HELO ruby.ksu.ru) ([193.232.252.56]) by iout.kzn.ru with ESMTP; 20 Jan 2009 20:42:24 +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 n0KHe0Eb022988; Tue, 20 Jan 2009 17:40:00 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 n0KHgLPE027257; Tue, 20 Jan 2009 20:42:21 +0300 (MSK) (envelope-from amarat@ksu.ru) Message-ID: <49760CFD.1040705@ksu.ru> Date: Tue, 20 Jan 2009 20:42:21 +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: Dan Langille References: <496D374A.3020704@langille.org> <496E9A37.20800@langille.org> <496EA339.6010808@ksu.ru> <496EB43A.8010805@langille.org> <496ECB2A.8080609@ksu.ru> <49754FA1.3070004@ksu.ru> In-Reply-To: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jan 2009 17:42:31 -0000 Dan Langille wrote: > > Please. > btw, did you try to set hw.acpi.osname="Linux" in /boot/loader.conf? -- SY, Marat From owner-freebsd-stable@FreeBSD.ORG Tue Jan 20 19:05: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 D7DF21065674 for ; Tue, 20 Jan 2009 19:05:56 +0000 (UTC) (envelope-from jerrymc@gizmo.acns.msu.edu) Received: from gizmo.acns.msu.edu (gizmo.acns.msu.edu [35.8.1.43]) by mx1.freebsd.org (Postfix) with ESMTP id 77F038FC3E for ; Tue, 20 Jan 2009 19:05:56 +0000 (UTC) (envelope-from jerrymc@gizmo.acns.msu.edu) Received: from gizmo.acns.msu.edu (localhost [127.0.0.1]) by gizmo.acns.msu.edu (8.13.6/8.13.6) with ESMTP id n0KIgHmJ057341; Tue, 20 Jan 2009 13:42:17 -0500 (EST) (envelope-from jerrymc@gizmo.acns.msu.edu) Received: (from jerrymc@localhost) by gizmo.acns.msu.edu (8.13.6/8.13.6/Submit) id n0KIgGVb057340; Tue, 20 Jan 2009 13:42:16 -0500 (EST) (envelope-from jerrymc) Date: Tue, 20 Jan 2009 13:42:16 -0500 From: Jerry McAllister To: Eduardo Meyer Message-ID: <20090120184216.GA57318@gizmo.acns.msu.edu> References: <20090120161355.GA28525@hugo10.ka.punkt.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.4.2.2i Cc: stable@freebsd.org, questions@freebsd.org Subject: Re: switching bsdlabel's label X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Jan 2009 19:05:57 -0000 On Tue, Jan 20, 2009 at 03:36:34PM -0200, Eduardo Meyer wrote: > On Tue, Jan 20, 2009 at 2:13 PM, Patrick M. Hausen wrote: > > Hello, > > > > On Tue, Jan 20, 2009 at 01:24:27PM -0200, Eduardo Meyer wrote: > >> I have a certain disk where da0s1a and da0s1d are inverted. By some > >> reason someone labelled root as 'd' and home as 'a'. > >> > >> Can I just > >> > >> bsdlabel -n da0s1 > savedabel.txt > >> > >> Edit savedlabel.txt, switch and restore? (bsdlabel -R da0s1 savedlabel) > > > > Why not simply use bsdlabel -e da0s1? > > Because I didnt know about that? ;-) > > Thank you for the hint. > > However I still have the same doubt. Since basically its the same > task, Is it safe do relabel this way? Hmmm. Is there stuff written on the disk. Is root stuff really written on da0s1d and /home stuff really written on da0s1a? Does the system boot from it OK? Or is it just that the mounts are switched. The mount points are not written in to the label. That comes after booting. If it boots, I wonder if it really is switched on the partitions or if it is just that the partitions are mounted backwards (probably due to editing /etc/fstab incorrectly). ////jerry > > > > > Kind regards, > > Patrick > > -- > > punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe > > Tel. 0721 9109 0 * Fax 0721 9109 100 > > info@punkt.de http://www.punkt.de > > Gf: Jürgen Egeling AG Mannheim 108285 > > > > > > -- > =========== > Eduardo Meyer > pessoal: dudu.meyer@gmail.com > profissional: ddm.farmaciap@saude.gov.br > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Tue Jan 20 20:15:51 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 D7E35106564A for ; Tue, 20 Jan 2009 20:15:51 +0000 (UTC) (envelope-from roberto@keltia.freenix.fr) Received: from keltia.freenix.fr (keltia.freenix.org [IPv6:2001:660:330f:f820:213:72ff:fe15:f44]) by mx1.freebsd.org (Postfix) with ESMTP id 8754B8FC12 for ; Tue, 20 Jan 2009 20:15:51 +0000 (UTC) (envelope-from roberto@keltia.freenix.fr) Received: from localhost (localhost [127.0.0.1]) by keltia.freenix.fr (Postfix/TLS) with ESMTP id 8596E3B742; Tue, 20 Jan 2009 21:15:50 +0100 (CET) X-Virus-Scanned: amavisd-new at keltia.freenix.fr Received: from keltia.freenix.fr ([127.0.0.1]) by localhost (keltia.freenix.fr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ynJQ7Bo+6+1I; Tue, 20 Jan 2009 21:15:50 +0100 (CET) Received: by keltia.freenix.fr (Postfix/TLS, from userid 101) id 334BF3B73A; Tue, 20 Jan 2009 21:15:50 +0100 (CET) Date: Tue, 20 Jan 2009 21:15:50 +0100 From: Ollivier Robert To: pluknet Message-ID: <20090120201550.GA25090@keltia.freenix.fr> References: <20090119224750.GA7463@keltia.freenix.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: MacOS X / Macbook Pro - FreeBSD 7 / Dell D820 SMP User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-stable@freebsd.org Subject: Re: SYSV* mandatory for COMPAT_IA32 on amd64? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jan 2009 20:15:52 -0000 According to pluknet: > To clarify: > I.e. on older versions you had no errors with COMPAT_IA32 and without SYSV* ? I think so. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr Dons / donation Ondine : http://ondine.keltia.net/ From owner-freebsd-stable@FreeBSD.ORG Tue Jan 20 20:25:47 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 8273D106596F for ; Tue, 20 Jan 2009 20:25:47 +0000 (UTC) (envelope-from ralf.vanderenden@deltares.nl) Received: from deltares.nl (mail.deltares.nl [145.9.190.122]) by mx1.freebsd.org (Postfix) with ESMTP id EA9F18FC27 for ; Tue, 20 Jan 2009 20:25:46 +0000 (UTC) (envelope-from ralf.vanderenden@deltares.nl) Received: by deltares.nl (CommuniGate Pro PIPE 5.2.11) with PIPE id 9087969; Tue, 20 Jan 2009 20:25:45 +0100 X-ExtScanner: Niversoft's AddFooter filter Received: from [82.170.23.130] (account enden HELO ralf) by deltares.nl (CommuniGate Pro SMTP 5.2.11) with ESMTPA id 9087962 for stable@freebsd.org; Tue, 20 Jan 2009 20:25:29 +0100 Message-ID: <9F9D589A398D4B3983D9D423E07718CB@ralf> From: "Ralf van der Enden" To: Date: Tue, 20 Jan 2009 20:25:23 +0100 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 14.0.8050.1202 X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8050.1202 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: New BTX bootloader hangs my box X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Jan 2009 20:25:48 -0000 Hi, I've recently upgraded my box from FreeBSD 7.0-RELEASE to 7.1-RELEASE. Now, whenever I reboot my machine it hangs during the boot proces. I have a Fasttrak TX2 100 card in my system which is used for booting = FreeBSD and it shows fine while it's searching for attached drives, but = after it loads the MBR the system shows the Fasttrak BIOS again and = locks up everything. The only way to resolve this is: 1) Turn off the system with the power button (reset button and = ctrl-alt-delete don't work) 2) Turn it back on and go into the Fasttrak BIOS setup. (This is = required, because if I don't it'll get stuck like I explained above). 3) Quit the Fasttrak BIOS and restart the system 4) Everything loads fine now until I do another 'shutdown -r now' FreeBSD 7.0 never caused any trouble so I'm assuming this has to do with = the changes to the BTX bootloader. Does anyone know how to fix this ? Thanks in advance. Best, Ralf van der Enden Delft Hydraulics, GeoDelft, the Subsurface and Groundwater unit of TNO=20= and parts of Rijkswaterstaat have joined forces in a new independent inst= itute for delta technology, Deltares. Deltares combines knowledge and exp= erience in the field of water, soil and the subsurface. We provide innova= tive solutions to make living in deltas, coastal areas and river basins=20= safe, clean and sustainable.=20 =20 DISCLAIMER: This message is intende= d exclusively for the addressee(s) and may contain confidential and privi= leged information. If you are not the intended recipient please notify th= e sender immediately and destroy this message. Unauthorized use, disclosu= re or copying of this message is strictly prohibited. The foundation 'Sti= chting Deltares', which has its seat at Delft, The Netherlands, Commercia= l Registration Number 41146461, is not liable in any way whatsoever for=20= consequences and/or damages resulting from the improper, incomplete and=20= untimely dispatch, receipt and/or content of this e-mail. From owner-freebsd-stable@FreeBSD.ORG Tue Jan 20 21:59: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 62E61106566B; Tue, 20 Jan 2009 21:59:55 +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 94C328FC14; Tue, 20 Jan 2009 21:59:54 +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 n0KLxkFS019355; Tue, 20 Jan 2009 22:59:46 +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 n0KLxjdW019352; Tue, 20 Jan 2009 22:59:46 +0100 (CET) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Date: Tue, 20 Jan 2009 22:59:45 +0100 (CET) From: Wojciech Puchar To: Eduardo Meyer In-Reply-To: Message-ID: <20090120225943.T19343@wojtek.tensor.gdynia.pl> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: stable@freebsd.org, questions@freebsd.org Subject: Re: switching bsdlabel's label X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Jan 2009 21:59:56 -0000 yes On Tue, 20 Jan 2009, Eduardo Meyer wrote: > Hello, > > I have a certain disk where da0s1a and da0s1d are inverted. By some > reason someone labelled root as 'd' and home as 'a'. > > Can I just > > bsdlabel -n da0s1 > savedabel.txt > > Edit savedlabel.txt, switch and restore? (bsdlabel -R da0s1 savedlabel) > > -- > =========== > Eduardo Meyer > pessoal: dudu.meyer@gmail.com > profissional: ddm.farmaciap@saude.gov.br > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > > From owner-freebsd-stable@FreeBSD.ORG Tue Jan 20 23:11:06 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 4C94F106566C for ; Tue, 20 Jan 2009 23:11:06 +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 132018FC08 for ; Tue, 20 Jan 2009 23:11:05 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 2D6C77309E; Wed, 21 Jan 2009 00:16:25 +0100 (CET) Date: Wed, 21 Jan 2009 00:16:25 +0100 From: Luigi Rizzo To: Ralf van der Enden Message-ID: <20090120231625.GA36029@onelab2.iet.unipi.it> References: <9F9D589A398D4B3983D9D423E07718CB@ralf> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9F9D589A398D4B3983D9D423E07718CB@ralf> User-Agent: Mutt/1.4.2.3i Cc: stable@freebsd.org Subject: Re: New BTX bootloader hangs my box X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Jan 2009 23:11:06 -0000 On Tue, Jan 20, 2009 at 08:25:23PM +0100, Ralf van der Enden wrote: > Hi, > > I've recently upgraded my box from FreeBSD 7.0-RELEASE to 7.1-RELEASE. > > Now, whenever I reboot my machine it hangs during the boot proces. > > I have a Fasttrak TX2 100 card in my system which is used for booting FreeBSD and it shows fine while it's searching for attached drives, but after it loads the MBR the system shows the Fasttrak BIOS again and locks up everything. The only way to resolve this is: > > 1) Turn off the system with the power button (reset button and ctrl-alt-delete don't work) > 2) Turn it back on and go into the Fasttrak BIOS setup. (This is required, because if I don't it'll get stuck like I explained above). > 3) Quit the Fasttrak BIOS and restart the system > 4) Everything loads fine now until I do another 'shutdown -r now' > > FreeBSD 7.0 never caused any trouble so I'm assuming this has to do with the changes to the BTX bootloader. > > Does anyone know how to fix this ? the easiest fix is to replace /boot/loader with the version from a 7.0 CD In the meantime (i am collecting data) can you tell us whether this uses an Intel or AMD CPU, sine or multi core ? cheers luigi From owner-freebsd-stable@FreeBSD.ORG Wed Jan 21 01:49:51 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 F0844106564A for ; Wed, 21 Jan 2009 01:49:51 +0000 (UTC) (envelope-from jjr@alisa.org) Received: from mail.alisa.org (mail.alisa.org [65.103.114.105]) by mx1.freebsd.org (Postfix) with ESMTP id 8C3118FC18 for ; Wed, 21 Jan 2009 01:49:51 +0000 (UTC) (envelope-from jjr@alisa.org) Received: from [192.168.1.102] (c-98-245-37-189.hsd1.co.comcast.net [98.245.37.189]) (authenticated bits=0) by mail.alisa.org (8.14.3/8.14.3) with ESMTP id n0L1M2OY051525; Tue, 20 Jan 2009 18:22:03 -0700 (MST) (envelope-from jjr@alisa.org) User-Agent: Microsoft-Entourage/11.4.0.080122 Date: Tue, 20 Jan 2009 18:22:00 -0700 From: John Rushford To: Mark Kirkwood , Reuben Message-ID: Thread-Topic: Broken loader on 7.1-STABLE? Thread-Index: Acl7Zqh250rLWudZEd2PXAAX8gEdYA== In-Reply-To: <4975ADF4.1070103@paradise.net.nz> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (mail.alisa.org [65.103.114.105]); Tue, 20 Jan 2009 18:22:05 -0700 (MST) Cc: FreeBSD-stable@freebsd.org Subject: Re: Broken loader on 7.1-STABLE? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jan 2009 01:49:52 -0000 Hello, Perhaps mine is a different issue but I ran into this today. I loaded FreeBSD 7.1-RELEASE from a DVD onto an Apple Mac Pro after partitioning a drive with bootcamp. The install went quite well and the machine came up with no issues. I configured networking, X, and got gnome working. I setup cvsup and loaded the STABLE sources, ran make buildworld, make kernel, etc... I attempted to boot into single user to run mergemaster, installworld, etc.. But the machine will not boot, I now get the following errror and prompt: Trying to mount root from ufs:/dev/ad9s1a Manual root filesystem specification: : Mount using filesystem e.g. ufs:da0s1a ? List valid disk boot devices Abort manual input I input ufs:/dev/ad9s1a to no avail and ? Does not list any other devices. I've booted from the DVD and gone into Fixit mode and can mount /dev/ad9s1a just fine. I thought that I'd try putting back loader.old on the off chance that might solve the problem but, I do not see a loader.old, just loader. The kernel.old directory is there. Any ideas on what the issue might be and how to fix? Appreciate the help as I'd like to get 7.1-STABLE running on this machine. Regards John On 1/20/09 3:56 AM, "Mark Kirkwood" wrote: > Reuben wrote: >> >> I was wondering if anyone else was seeing loader (v1.02) break after updating >> from 7.1-RELEASE to 7.1-STABLE. After performing the prescribed updating >> procedure (via the handbook), the system will go through the normal steps and >> after the boot menu will present the following error: >> >> Can't work out which disk we are booting from. >> Guessed BIOS device 0xffffffff not found by probes, defaulting to disk0 >> >> According to the bugbusting page on the FreeBSD wiki there's two issues at >> work that cause this behavior; patches were committed to HEAD/RELENG earlier >> last year in Mar and Aug. Up until now I've never come across this problem >> in 6.x or 7.0. In doing a little research I've come across a few older >> threads via google where it was believed that the problem was caused by >> improper CFLAGS in make.conf. I've commented mine out and rebuilt things.. >> with the same end result. In fact, if it's any help, my CFLAGS declaration >> in make.conf is taken verbatim from the /usr/share/examples/etc/make.conf. >> Furthermore, on selecting option 6 from the boot menu (escape to loader >> prompt), the system [I'm assuming] crashes displaying a blinking ASCII >> pattern from which only a hard reboot will work. >> >> FWIW, this is a fairly plain system.. nothing special in sysctl.conf or >> loader.conf, and the kernel is pretty stock as well (more or less GENERIC >> with my sound device and pf). >> >> A temporary fix for me was to copy over loader.old to loader in /boot. >> >> >> > > I am getting this too - update from RELENG_7 @12 Jan src to 20 Jan and I > have: > > panic: free: guard1 fail @ 0x511d > from /usr/src/sys/boot/i386/loader/../../common/module.c:959 > > Can't work out which disk we are booting from. > Guessed BIOS device 0xffffffff not found by probes, defaulting to disk0 > > > > Copying loader.old to loader did not work around this for me - I had to > empty loader.conf too. > > Here is what *was* in there: > > ---> begin loader.conf > # Sound > sound_load="YES" > snd_hda_load="YES" > > # IPC > kern.ipc.semmni=500 > kern.ipc.semmns=500 > > > # CD/DVD DMA > atapicam_load="YES" > hw.ata.atapi_dma=0 > --> end loader.conf > > > At this point I am not sure which if are the bad guys... > > > The machine is an Asus a8vx. > > regards > > Mark > _______________________________________________ > 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 21 03:32: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 9DEE8106566B for ; Wed, 21 Jan 2009 03:32:41 +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 636C78FC18 for ; Wed, 21 Jan 2009 03:32:41 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so3553665rvf.43 for ; Tue, 20 Jan 2009 19:32:41 -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=bHr2oxpPhE5hQWaY+IMugs7ij9H365ICol8OG4uAlUc=; b=xg0Xs9jnuE6mWo4GYW//VIR5Ud5nOGYk/wEmFI0RxffYB/XU2+NrhOWwtYAcA2nPxK ZOz0RkEIJJfu3zwTgeJ32aumUeDjit6kCEgLxuhrKwERjSQyRekdZ3DIHq9yzD6DGZPa 34Q1qinDVNMkltqZqqZc58Wxe1GTWJIcz/SmY= 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=WtOGGsSGJFA8MwCSyey3K8qYVuOyCEP3bsyRYuv3nPpQfb3tAkCW2Q6+3PznFQ4M4g TwhsiM40clri25PC5aL5HIIdKXdTng3ZFKNRe8al2nCWUph3GFUPRnm4hBpTWP++ahto DrWee9bjBH7X5xOoJPW27ixWRNitCo7Lewm4Q= Received: by 10.141.89.13 with SMTP id r13mr3717728rvl.271.1232508757572; Tue, 20 Jan 2009 19:32:37 -0800 (PST) Received: from michelle.cdnetworks.co.kr ([211.53.35.84]) by mx.google.com with ESMTPS id g31sm14101180rvb.4.2009.01.20.19.32.34 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 20 Jan 2009 19:32:36 -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 n0L3WUhA084758 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 21 Jan 2009 12: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 n0L3WRc9084757; Wed, 21 Jan 2009 12:32:27 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Wed, 21 Jan 2009 12:32:27 +0900 From: Pyun YongHyeon To: "Marat N.Afanasyev" Message-ID: <20090121033227.GC84185@cdnetworks.co.kr> References: <496D374A.3020704@langille.org> <496E9A37.20800@langille.org> <496EA339.6010808@ksu.ru> <496EB43A.8010805@langille.org> <496ECB2A.8080609@ksu.ru> <49754FA1.3070004@ksu.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49754FA1.3070004@ksu.ru> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org, Dan Langille Subject: Re: interrupt storm 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, 21 Jan 2009 03:32:42 -0000 On Tue, Jan 20, 2009 at 07:14:25AM +0300, Marat N.Afanasyev wrote: > Marat N.Afanasyev wrote: > >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 :( > > > still no luck with fixing dsdt. I tried to build a custom dsdt, tried to > set hw.acpi.osname="Linux" in /boot/loader.conf, nothing changes. so it > may be related with APIC, not dsdt only. So, if anyone has any idea how > to find out what is happening, please tell me, we'll try to fix this. > > Probably Pyun will give us some advice, wouldn't you? :) > Sorry, I have no idea. > Or should I make a problem report? -- Regards, Pyun YongHyeon From owner-freebsd-stable@FreeBSD.ORG Wed Jan 21 07:13: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 408CE106564A for ; Wed, 21 Jan 2009 07:13:41 +0000 (UTC) (envelope-from markir@paradise.net.nz) Received: from smtp3.clear.net.nz (smtp3.clear.net.nz [203.97.33.64]) by mx1.freebsd.org (Postfix) with ESMTP id 0A5138FC18 for ; Wed, 21 Jan 2009 07:13:40 +0000 (UTC) (envelope-from markir@paradise.net.nz) Received: from zmori.markir.net (121-73-178-201.dsl.telstraclear.net [121.73.178.201]) by smtp3.clear.net.nz (CLEAR Net Mail) with ESMTP id <0KDT00FQ082K9Z20@smtp3.clear.net.nz> for FreeBSD-stable@FreeBSD.org; Wed, 21 Jan 2009 20:13:33 +1300 (NZDT) Date: Wed, 21 Jan 2009 20:13:32 +1300 From: Mark Kirkwood In-reply-to: <4975ADF4.1070103@paradise.net.nz> To: FreeBSD-stable@FreeBSD.org Message-id: <4976CB1C.7050409@paradise.net.nz> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7bit References: <20090109171857.GA49752@marvin.eastcentral.edu> <4975ADF4.1070103@paradise.net.nz> User-Agent: Thunderbird 2.0.0.19 (X11/20090117) Cc: rizzo@iet.unipi.it Subject: Re: Broken loader on 7.1-STABLE? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jan 2009 07:13:41 -0000 I wrote: > > I am getting this too - update from RELENG_7 @12 Jan src to 20 Jan and > I have: > > panic: free: guard1 fail @ 0x511d > from /usr/src/sys/boot/i386/loader/../../common/module.c:959 > > Can't work out which disk we are booting from. > Guessed BIOS device 0xffffffff not found by probes, defaulting to disk0 > > Forgot to say (cc'ing Luigi as he is collecting info): Asus a8vx with an AMD 64x2 3800+ dual core From owner-freebsd-stable@FreeBSD.ORG Wed Jan 21 11:43: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 5DDCE10657AD for ; Wed, 21 Jan 2009 11:43:36 +0000 (UTC) (envelope-from dikshie@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 1E6838FC1C for ; Wed, 21 Jan 2009 11:43:35 +0000 (UTC) (envelope-from dikshie@gmail.com) Received: by yx-out-2324.google.com with SMTP id 8so1523178yxb.13 for ; Wed, 21 Jan 2009 03:43:35 -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=aqCNPyubVeFYyDpCJhmN2v/MFa+51u1FUzNw6qicIkA=; b=qU0aGJRhNxdT+LQEDdUQheSmy71QaYHLQukapBRchJ4EDqBC5WwrymkqxIZp0jyP0e M5kEkQ4SvX2HkpW6jmZNvoScXG9udQ4P5PIah4Fvky+g/z4OsswaQJbfbfWhXMXOYkeU sHPleNgRU/TikWPtCqjImD1alzku4m0qI1/ss= 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=cbMtC0vrZWNYG2e4cKJqYU05Xsg1fjrN2zLNdR3fEK+QGAkl5ACyhmZLMzez/cLMs6 lwoffHbEOUdXvzKW4ab0YWDtr8G2jpk20v5LISpNgPR5iINbukLWR6GGF+mlTGa8wpBX BMVMW6LkJ3ZmU/Kpo5SijUf4dUdw/u9HmNupA= MIME-Version: 1.0 Received: by 10.151.114.13 with SMTP id r13mr4078129ybm.21.1232536769216; Wed, 21 Jan 2009 03:19:29 -0800 (PST) Date: Wed, 21 Jan 2009 20:19:29 +0900 Message-ID: <910e60e80901210319mbb13fbxa8659577bb5ea162@mail.gmail.com> From: dikshie To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: unkillable proceess X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Jan 2009 11:43:37 -0000 Hi, how to kill unkillable process: # ps axuf |grep http www 66005 73.4 1.3 87656 13164 ?? R 4:58PM 62:24.41 /usr/local/sbin/httpd -DSSL -DNOHTTPACCEPT www 4277 71.6 1.4 88680 13964 ?? R 4:12PM 48:23.40 /usr/local/sbin/httpd -DSSL -DNOHTTPACCEPT www 2708 65.5 1.4 88680 14112 ?? R 4:12PM 54:39.50 /usr/local/sbin/httpd -DSSL -DNOHTTPACCEPT above processes unkillable regards, -dikshie- From owner-freebsd-stable@FreeBSD.ORG Wed Jan 21 12:02: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 B9FF510658F2 for ; Wed, 21 Jan 2009 12:02:27 +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 984488FC4C for ; Wed, 21 Jan 2009 12:02:18 +0000 (UTC) (envelope-from admin@kkip.pl) Received: from admin.admin.lan.kkip.pl ([10.66.3.254]) by mainframe.kkip.pl with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LPbme-0001Ee-4m; Wed, 21 Jan 2009 13:02:16 +0100 Message-ID: <49770EC3.9000205@kkip.pl> Date: Wed, 21 Jan 2009 13:02:11 +0100 From: Bartosz Stec User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: dikshie References: <910e60e80901210319mbb13fbxa8659577bb5ea162@mail.gmail.com> In-Reply-To: <910e60e80901210319mbb13fbxa8659577bb5ea162@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-Spam-Score: -8.9 X-Spam-Score-Int: -88 X-Exim-Version: 4.69 (build at 14-Jan-2009 11:48:13) X-Date: 2009-01-21 13:02:16 X-Connected-IP: 10.66.3.254:4691 X-Message-Linecount: 41 X-Body-Linecount: 27 X-Message-Size: 1127 X-Body-Size: 553 X-Received-Count: 1 X-Recipient-Count: 2 X-Local-Recipient-Count: 2 X-Local-Recipient-Defer-Count: 0 X-Local-Recipient-Fail-Count: 0 Cc: freebsd-stable@freebsd.org Subject: Re: unkillable proceess X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Jan 2009 12:02:48 -0000 dikshie pisze: > Hi, > how to kill unkillable process: > > # ps axuf |grep http > www 66005 73.4 1.3 87656 13164 ?? R 4:58PM 62:24.41 > /usr/local/sbin/httpd -DSSL -DNOHTTPACCEPT > www 4277 71.6 1.4 88680 13964 ?? R 4:12PM 48:23.40 > /usr/local/sbin/httpd -DSSL -DNOHTTPACCEPT > www 2708 65.5 1.4 88680 14112 ?? R 4:12PM 54:39.50 > /usr/local/sbin/httpd -DSSL -DNOHTTPACCEPT > > above processes unkillable > > > regards, > > -dikshie- > > Try: apachectl stop /usr/local/etc/rc.d/apache22 stop -- Bartosz Stec From owner-freebsd-stable@FreeBSD.ORG Wed Jan 21 12:40: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 66EA11065673 for ; Wed, 21 Jan 2009 12:40:54 +0000 (UTC) (envelope-from nakal@web.de) Received: from fmmailgate02.web.de (fmmailgate02.web.de [217.72.192.227]) by mx1.freebsd.org (Postfix) with ESMTP id 258028FC16 for ; Wed, 21 Jan 2009 12:40:53 +0000 (UTC) (envelope-from nakal@web.de) Received: from smtp08.web.de (fmsmtp08.dlan.cinetic.de [172.20.5.216]) by fmmailgate02.web.de (Postfix) with ESMTP id B543CF934686; Wed, 21 Jan 2009 13:40:50 +0100 (CET) Received: from [217.236.0.162] (helo=zelda.local) by smtp08.web.de with asmtp (TLSv1:AES128-SHA:128) (WEB.DE 4.110 #277) id 1LPcO2-0000Td-00; Wed, 21 Jan 2009 13:40:50 +0100 Date: Wed, 21 Jan 2009 13:40:47 +0100 From: Martin To: Tony Maher Message-ID: <20090121134047.3176a950@zelda.local> In-Reply-To: <4971B18D.3090803@optusnet.com.au> References: <4971B18D.3090803@optusnet.com.au> X-Mailer: Claws Mail 3.7.0 (GTK+ 2.14.7; amd64-portbld-freebsd7.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: nakal@web.de X-Sender: nakal@web.de X-Provags-ID: V01U2FsdGVkX18nc3CcUMN6dcW3pWI09J/8NuoTvt2xpfGjoKx3 2RUajA0k7JJaIf4tETv9MKOsSLidnC4BP8pO8iAtQXkmm9HX31 i/5BEgLTI= Cc: stable@freebsd.org Subject: Re: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jan 2009 12:40:55 -0000 Am Sat, 17 Jan 2009 21:23:09 +1100 schrieb Tony Maher : > 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. Hi, I've reported problems like this on -STABLE more than once already. Apparently it is a very uncommon problem for the developers. I have to say that all my new PCs and the new laptop has problems with USB keyboards and mice generally. The laptop (IBM Thinkpad T60p) has the most problems, -STABLE switches the USB devices off in intervals of about 2h. I have updated (flashed) my BIOS firmware on this mainboard here (Gigabyte GA-EP35C-DS3R rev 2.1) to the recent firmware F4a (it's a 6 month old beta release). The problem worsened now. I cannot get my USB mouse working until I reattach it physically. This is not a problem on other OSes, it seems. During device detection and initialization of uhci/ehci my USB-mouse is switched off and does not get power anymore. I get the same effect on -CURRENT as of yesterday. Mouse is Logitech G5, btw. I tried various USB settings in BIOS. USB mouse support on/off, USB legacy device support on/off. What else can I do? This is very annoying. (I wonder if it can be the source of many problems that people report here about umass devices.) -- Martin From owner-freebsd-stable@FreeBSD.ORG Wed Jan 21 12:45:29 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 D981D106566C; Wed, 21 Jan 2009 12:45:29 +0000 (UTC) (envelope-from dudu.meyer@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.172]) by mx1.freebsd.org (Postfix) with ESMTP id A50C78FC1D; Wed, 21 Jan 2009 12:45:29 +0000 (UTC) (envelope-from dudu.meyer@gmail.com) Received: by wf-out-1314.google.com with SMTP id 24so4040836wfg.7 for ; Wed, 21 Jan 2009 04:45:29 -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=nXG/q+XXIuzUTv2TIPHSi0n+ksClY0B4t9M51Y6xs5M=; b=mn4ZX6sDafImTeiUS+wxMu1jFY812r9XbBl5cTXp1DaTpPpOAgt6qIYiekIWvjHnD2 1NPbbagl1YqMG+wdK2XGHX9ZWZR81AhO0fA3IT37rPeMzadb1H7orzM3C5FByQ+v81uo XwRdhXNiBt4OFkDq+sg8wzvrgtFBrfNlRRLkE= 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=Ow7jqzFeHV0E56TlsgLl+odBqPlyy5zN6hlPlflxzGifIdqKilOpe+cTHLuHSNscjL joyGavYoucoT8oQRSx7jXwrq29751Sd3Z5AD+OsY/AHEmbWF5wohjemg9YRCBl9Wc5sO KVUPq2y3Z8MhtkVN4tU3gWHM5godKTG/CRnXA= MIME-Version: 1.0 Received: by 10.142.134.17 with SMTP id h17mr28408wfd.228.1232541928053; Wed, 21 Jan 2009 04:45:28 -0800 (PST) In-Reply-To: <20090120184216.GA57318@gizmo.acns.msu.edu> References: <20090120161355.GA28525@hugo10.ka.punkt.de> <20090120184216.GA57318@gizmo.acns.msu.edu> Date: Wed, 21 Jan 2009 10:45:28 -0200 Message-ID: From: Eduardo Meyer To: Jerry McAllister Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: stable@freebsd.org, questions@freebsd.org Subject: Re: switching bsdlabel's label X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Jan 2009 12:45:30 -0000 On Tue, Jan 20, 2009 at 4:42 PM, Jerry McAllister wrote: > On Tue, Jan 20, 2009 at 03:36:34PM -0200, Eduardo Meyer wrote: > >> On Tue, Jan 20, 2009 at 2:13 PM, Patrick M. Hausen wro= te: >> > Hello, >> > >> > On Tue, Jan 20, 2009 at 01:24:27PM -0200, Eduardo Meyer wrote: >> >> I have a certain disk where da0s1a and da0s1d are inverted. By some >> >> reason someone labelled root as 'd' and home as 'a'. >> >> >> >> Can I just >> >> >> >> bsdlabel -n da0s1 > savedabel.txt >> >> >> >> Edit savedlabel.txt, switch and restore? (bsdlabel -R da0s1 savedlabe= l) >> > >> > Why not simply use bsdlabel -e da0s1? >> >> Because I didnt know about that? ;-) >> >> Thank you for the hint. >> >> However I still have the same doubt. Since basically its the same >> task, Is it safe do relabel this way? > > Hmmm. Is there stuff written on the disk. Is root stuff really written > on da0s1d and /home stuff really written on da0s1a? Does the system boo= t > from it OK? > > Or is it just that the mounts are switched. > The mount points are not written in to the label. That comes after > booting. If it boots, I wonder if it really is switched on the > partitions or if it is just that the partitions are mounted backwards > (probably due to editing /etc/fstab incorrectly). > > ////jerry Hello Patrick, thanks again. Yes, label is switched. Yes there really are stuff on the partitions. No, I dont boot from da0s1d. It is a disk for migration. But the one who partitioned was fooled by Sysinstall which creates the first label on extra disks as 'd' and the last from the allowed 7 as 'a'. Therefore this server is still booting on the original disk (ad6s1a) and everything else is mounted in the new one (da0s1), everything but root. > > > > >> >> > >> > Kind regards, >> > Patrick >> > -- >> > punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe >> > Tel. 0721 9109 0 * Fax 0721 9109 100 >> > info@punkt.de http://www.punkt.de >> > Gf: J=FCrgen Egeling AG Mannheim 108285 >> > >> >> >> >> -- >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> Eduardo Meyer >> pessoal: dudu.meyer@gmail.com >> profissional: ddm.farmaciap@saude.gov.br >> _______________________________________________ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.= org" >> > --=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Eduardo Meyer pessoal: dudu.meyer@gmail.com profissional: ddm.farmaciap@saude.gov.br From owner-freebsd-stable@FreeBSD.ORG Wed Jan 21 12:54:33 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 E1356106566B for ; Wed, 21 Jan 2009 12:54:33 +0000 (UTC) (envelope-from ralf.vanderenden@deltares.nl) Received: from deltares.nl (mail.deltares.nl [145.9.190.122]) by mx1.freebsd.org (Postfix) with ESMTP id 58E3C8FC13 for ; Wed, 21 Jan 2009 12:54:32 +0000 (UTC) (envelope-from ralf.vanderenden@deltares.nl) Received: by deltares.nl (CommuniGate Pro PIPE 5.2.11) with PIPE id 9096640; Wed, 21 Jan 2009 13:54:31 +0100 X-ExtScanner: Niversoft's AddFooter filter Received: from [145.9.225.229] (HELO wl06640) by deltares.nl (CommuniGate Pro SMTP 5.2.11) with SMTP id 9096642; Wed, 21 Jan 2009 13:54:20 +0100 Message-ID: <6B361FD387BC4FD69473820EB4DA3772@wl06640> From: "Ralf van der Enden" To: "Luigi Rizzo" References: <9F9D589A398D4B3983D9D423E07718CB@ralf> <20090120231625.GA36029@onelab2.iet.unipi.it> Date: Wed, 21 Jan 2009 13:54:20 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 12.0.1606 X-MimeOLE: Produced By Microsoft MimeOLE V12.0.1606 Cc: stable@freebsd.org Subject: Re: New BTX bootloader hangs my box X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Jan 2009 12:54:34 -0000 Luigi, It's an AMD Thunderbird 1.2GHz (single core) on an AOpen motherboard. For more system info you can check http://sysinfo.cainites.net Thanks for the /boot/loader suggestion. Cheers, Ralf -------------------------------------------------- From: "Luigi Rizzo" Sent: Wednesday, January 21, 2009 12:16 AM To: "Ralf van der Enden" Cc: Subject: Re: New BTX bootloader hangs my box On Tue, Jan 20, 2009 at 08:25:23PM +0100, Ralf van der Enden wrote: > Hi, > > I've recently upgraded my box from FreeBSD 7.0-RELEASE to 7.1-RELEASE. > > Now, whenever I reboot my machine it hangs during the boot proces. > > I have a Fasttrak TX2 100 card in my system which is used for booting > FreeBSD and it shows fine while it's searching for attached drives, but > after it loads the MBR the system shows the Fasttrak BIOS again and locks > up everything. The only way to resolve this is: > > 1) Turn off the system with the power button (reset button and > ctrl-alt-delete don't work) > 2) Turn it back on and go into the Fasttrak BIOS setup. (This is required, > because if I don't it'll get stuck like I explained above). > 3) Quit the Fasttrak BIOS and restart the system > 4) Everything loads fine now until I do another 'shutdown -r now' > > FreeBSD 7.0 never caused any trouble so I'm assuming this has to do with > the changes to the BTX bootloader. > > Does anyone know how to fix this ? the easiest fix is to replace /boot/loader with the version from a 7.0 CD In the meantime (i am collecting data) can you tell us whether this uses an Intel or AMD CPU, sine or multi core ? cheers luigi Delft Hydraulics, GeoDelft, the Subsurface and Groundwater unit of TNO and parts of Rijkswaterstaat have joined forces in a new independent institute for delta technology, Deltares. Deltares combines knowledge and experience in the field of water, soil and the subsurface. We provide innovative solutions to make living in deltas, coastal areas and river basins safe, clean and sustainable. DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail. From owner-freebsd-stable@FreeBSD.ORG Wed Jan 21 12:55: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 DF51C1065731 for ; Wed, 21 Jan 2009 12:55:15 +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 6CAC48FC0A for ; Wed, 21 Jan 2009 12:55:15 +0000 (UTC) (envelope-from antik@bsd.ee) Received: from localhost (localhost.localdomain [127.0.0.1]) by sorbesgroup.com (Postfix) with ESMTP id 0C53E3C5129E; Wed, 21 Jan 2009 14:44:34 +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 12519-06; Wed, 21 Jan 2009 14:44:34 +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 CF8053C512D3; Wed, 21 Jan 2009 14:44:33 +0200 (EET) Message-ID: <49771B2F.7050902@bsd.ee> Date: Wed, 21 Jan 2009 14:55:11 +0200 From: Andrei Kolu User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Martin References: <4971B18D.3090803@optusnet.com.au> <20090121134047.3176a950@zelda.local> In-Reply-To: <20090121134047.3176a950@zelda.local> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at localhost Cc: Tony Maher , stable@freebsd.org Subject: Re: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jan 2009 12:55:16 -0000 Martin wrote: > Am Sat, 17 Jan 2009 21:23:09 +1100 > schrieb Tony Maher : > > >> 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. >> > > Hi, > > I've reported problems like this on -STABLE more than once already. > Apparently it is a very uncommon problem for the developers. I have to > say that all my new PCs and the new laptop has problems with USB > keyboards and mice generally. The laptop (IBM Thinkpad T60p) has the > most problems, -STABLE switches the USB devices off in intervals of > about 2h. > > I have updated (flashed) my BIOS firmware on this mainboard here > (Gigabyte GA-EP35C-DS3R rev 2.1) to the recent firmware F4a (it's a > 6 month old beta release). > > > The problem worsened now. I cannot get my USB mouse working until I > reattach it physically. This is not a problem on other OSes, it seems. > > During device detection and initialization of uhci/ehci my USB-mouse > is switched off and does not get power anymore. > > I get the same effect on -CURRENT as of yesterday. Mouse is Logitech > G5, btw. > > I tried various USB settings in BIOS. USB mouse support on/off, USB > legacy device support on/off. What else can I do? This is very annoying. > > (I wonder if it can be the source of many problems that people report > here about umass devices.) > > Hi, I have similar problem with Gigabyte GA-X48-DS4- I can't boot from usb flash drive or usb floppy drive 9times of 10. My APC ups was recognized only after OS is booted up and usb cable reinserted. Looks like this is Gigabyte problem only- all other motherboards work without any usb issues. Bios upgrade does not help. Changing any bios setting does not help either. From owner-freebsd-stable@FreeBSD.ORG Wed Jan 21 13:27: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 ADCFA1065687; Wed, 21 Jan 2009 13:27:44 +0000 (UTC) (envelope-from pieter@degoeje.nl) Received: from s2m-is-001.service2media.com (rev-130-102.virtu.nl [217.114.102.130]) by mx1.freebsd.org (Postfix) with ESMTP id 0D3348FC14; Wed, 21 Jan 2009 13:27:43 +0000 (UTC) (envelope-from pieter@degoeje.nl) Received: from nox-laptop.localnet ([10.0.1.45] RDNS failed) by s2m-is-001.service2media.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 21 Jan 2009 14:15:38 +0100 From: Pieter de Goeje To: freebsd-stable@freebsd.org Date: Wed, 21 Jan 2009 14:15:38 +0100 User-Agent: KMail/1.10.4 (Linux/2.6.27-11-generic; KDE/4.1.4; x86_64; ; ) References: <4971B18D.3090803@optusnet.com.au> <20090121134047.3176a950@zelda.local> <49771B2F.7050902@bsd.ee> In-Reply-To: <49771B2F.7050902@bsd.ee> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200901211415.38384.pieter@degoeje.nl> X-OriginalArrivalTime: 21 Jan 2009 13:15:38.0803 (UTC) FILETIME=[5A758030:01C97BCA] Cc: Andrei Kolu , Tony Maher , stable@freebsd.org, Martin Subject: Re: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jan 2009 13:27:45 -0000 On Wednesday 21 January 2009 13:55:11 Andrei Kolu wrote: > Martin wrote: > > Am Sat, 17 Jan 2009 21:23:09 +1100 > > > > schrieb Tony Maher : > >> 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. > > > > Hi, > > > > I've reported problems like this on -STABLE more than once already. > > Apparently it is a very uncommon problem for the developers. I have to > > say that all my new PCs and the new laptop has problems with USB > > keyboards and mice generally. The laptop (IBM Thinkpad T60p) has the > > most problems, -STABLE switches the USB devices off in intervals of > > about 2h. > > > > I have updated (flashed) my BIOS firmware on this mainboard here > > (Gigabyte GA-EP35C-DS3R rev 2.1) to the recent firmware F4a (it's a > > 6 month old beta release). > > > > > > The problem worsened now. I cannot get my USB mouse working until I > > reattach it physically. This is not a problem on other OSes, it seems. > > > > During device detection and initialization of uhci/ehci my USB-mouse > > is switched off and does not get power anymore. > > > > I get the same effect on -CURRENT as of yesterday. Mouse is Logitech > > G5, btw. > > > > I tried various USB settings in BIOS. USB mouse support on/off, USB > > legacy device support on/off. What else can I do? This is very annoying. > > > > (I wonder if it can be the source of many problems that people report > > here about umass devices.) > > Hi, I have similar problem with Gigabyte GA-X48-DS4- I can't boot from > usb flash drive or usb floppy drive 9times of 10. My APC ups was > recognized only after OS is booted up and usb cable reinserted. Looks > like this is Gigabyte problem only- all other motherboards work without > any usb issues. Bios upgrade does not help. Changing any bios setting > does not help either. I have a Gigabyte GA-P35-DS3R w/ a Logitech G5 mouse and usb keyboard. I had to switch to usb2 on freebsd 8-current for the keyboard to attach after boot. I have enabled usb keyboard support in the BIOS (otherwise the keyboard cannot be used during the boot process). Everything is working fine now. -- Pieter de Goeje From owner-freebsd-stable@FreeBSD.ORG Wed Jan 21 13:27: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 ADCFA1065687; Wed, 21 Jan 2009 13:27:44 +0000 (UTC) (envelope-from pieter@degoeje.nl) Received: from s2m-is-001.service2media.com (rev-130-102.virtu.nl [217.114.102.130]) by mx1.freebsd.org (Postfix) with ESMTP id 0D3348FC14; Wed, 21 Jan 2009 13:27:43 +0000 (UTC) (envelope-from pieter@degoeje.nl) Received: from nox-laptop.localnet ([10.0.1.45] RDNS failed) by s2m-is-001.service2media.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 21 Jan 2009 14:15:38 +0100 From: Pieter de Goeje To: freebsd-stable@freebsd.org Date: Wed, 21 Jan 2009 14:15:38 +0100 User-Agent: KMail/1.10.4 (Linux/2.6.27-11-generic; KDE/4.1.4; x86_64; ; ) References: <4971B18D.3090803@optusnet.com.au> <20090121134047.3176a950@zelda.local> <49771B2F.7050902@bsd.ee> In-Reply-To: <49771B2F.7050902@bsd.ee> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200901211415.38384.pieter@degoeje.nl> X-OriginalArrivalTime: 21 Jan 2009 13:15:38.0803 (UTC) FILETIME=[5A758030:01C97BCA] Cc: Andrei Kolu , Tony Maher , stable@freebsd.org, Martin Subject: Re: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jan 2009 13:27:45 -0000 On Wednesday 21 January 2009 13:55:11 Andrei Kolu wrote: > Martin wrote: > > Am Sat, 17 Jan 2009 21:23:09 +1100 > > > > schrieb Tony Maher : > >> 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. > > > > Hi, > > > > I've reported problems like this on -STABLE more than once already. > > Apparently it is a very uncommon problem for the developers. I have to > > say that all my new PCs and the new laptop has problems with USB > > keyboards and mice generally. The laptop (IBM Thinkpad T60p) has the > > most problems, -STABLE switches the USB devices off in intervals of > > about 2h. > > > > I have updated (flashed) my BIOS firmware on this mainboard here > > (Gigabyte GA-EP35C-DS3R rev 2.1) to the recent firmware F4a (it's a > > 6 month old beta release). > > > > > > The problem worsened now. I cannot get my USB mouse working until I > > reattach it physically. This is not a problem on other OSes, it seems. > > > > During device detection and initialization of uhci/ehci my USB-mouse > > is switched off and does not get power anymore. > > > > I get the same effect on -CURRENT as of yesterday. Mouse is Logitech > > G5, btw. > > > > I tried various USB settings in BIOS. USB mouse support on/off, USB > > legacy device support on/off. What else can I do? This is very annoying. > > > > (I wonder if it can be the source of many problems that people report > > here about umass devices.) > > Hi, I have similar problem with Gigabyte GA-X48-DS4- I can't boot from > usb flash drive or usb floppy drive 9times of 10. My APC ups was > recognized only after OS is booted up and usb cable reinserted. Looks > like this is Gigabyte problem only- all other motherboards work without > any usb issues. Bios upgrade does not help. Changing any bios setting > does not help either. I have a Gigabyte GA-P35-DS3R w/ a Logitech G5 mouse and usb keyboard. I had to switch to usb2 on freebsd 8-current for the keyboard to attach after boot. I have enabled usb keyboard support in the BIOS (otherwise the keyboard cannot be used during the boot process). Everything is working fine now. -- Pieter de Goeje From owner-freebsd-stable@FreeBSD.ORG Wed Jan 21 13:34:07 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 84D491065770 for ; Wed, 21 Jan 2009 13:34:07 +0000 (UTC) (envelope-from dieterich.joh@googlemail.com) Received: from ik-out-1112.google.com (ik-out-1112.google.com [66.249.90.179]) by mx1.freebsd.org (Postfix) with ESMTP id 012488FC12 for ; Wed, 21 Jan 2009 13:34:06 +0000 (UTC) (envelope-from dieterich.joh@googlemail.com) Received: by ik-out-1112.google.com with SMTP id c21so98447ika.3 for ; Wed, 21 Jan 2009 05:34:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=GO3h274QvL1sRoqu4p8bWasm6OgD3JIJyzdgHoUvtzI=; b=Qpho27nH4ChNOnDwP7WuyGz+TKzF6GgZxzZJqRsotBjplfxJny4YUvIRfyZ+ugA4Db qxtXl7mCP62WvjZ63ZYlAANv/SnMszlvsaLkc59jNqF5X19QTjChhU/0Me399vJr1van pbWQfOyp3s8dNIqCJdHc4+QkxXYOmKfPQweOk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=QDTQl9SJpfWb4HVZRL+6gFYKl4yFcAf1PMP7ybUOWBEOfMIXvENWR+ccVvXKsXyIy3 Mv00D8F3vPj4Y0OT2vCPViH0EPW2c5cUEHSBIyVxDNgFJO4Omniy/GU8T5OXIpvY5Fpc baPcjLpEwoGbtlIPsGzAjLeQJL/TAj3KuyIJM= MIME-Version: 1.0 Received: by 10.210.19.7 with SMTP id 7mr2432357ebs.34.1232543005962; Wed, 21 Jan 2009 05:03:25 -0800 (PST) In-Reply-To: <20090121134047.3176a950@zelda.local> References: <4971B18D.3090803@optusnet.com.au> <20090121134047.3176a950@zelda.local> Date: Wed, 21 Jan 2009 14:03:25 +0100 Message-ID: <542798610901210503p5a98be5byb688b9d0bb8ae142@mail.gmail.com> From: Johannes Dieterich To: Martin Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: stable@freebsd.org Subject: Re: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jan 2009 13:34:13 -0000 Hello Martin and Tony, On Wed, Jan 21, 2009 at 1:40 PM, Martin wrote: > Am Sat, 17 Jan 2009 21:23:09 +1100 > schrieb Tony Maher : > > > 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. > > Hi, > > I've reported problems like this on -STABLE more than once already. > Apparently it is a very uncommon problem for the developers. I have to > say that all my new PCs and the new laptop has problems with USB > keyboards and mice generally. The laptop (IBM Thinkpad T60p) has the > most problems, -STABLE switches the USB devices off in intervals of > about 2h. > > I have updated (flashed) my BIOS firmware on this mainboard here > (Gigabyte GA-EP35C-DS3R rev 2.1) to the recent firmware F4a (it's a > 6 month old beta release). I am adding a "me too" here. Interesting is, that I see same behaviour on two Gigabyte boards, a GA-MA790X-DS4 and another one (model number I do not have right here ATM, need to check, Intel-based board though). No problems on my Thinkpad X60s though. > > > > The problem worsened now. I cannot get my USB mouse working until I > reattach it physically. This is not a problem on other OSes, it seems. Also here a me too. Reattaching always works, on the intel-based board I've been running an openSUSE 10.3 w/o problems. > > > During device detection and initialization of uhci/ehci my USB-mouse > is switched off and does not get power anymore. The usb port of the GA-MA790X-DS4 actually get powered off if USB mouse is plugged-in during boot. This also causes a time-out which sucks a little. Johannes > > > I get the same effect on -CURRENT as of yesterday. Mouse is Logitech > G5, btw. > > I tried various USB settings in BIOS. USB mouse support on/off, USB > legacy device support on/off. What else can I do? This is very annoying. > > (I wonder if it can be the source of many problems that people report > here about umass devices.) > > From owner-freebsd-stable@FreeBSD.ORG Wed Jan 21 14:03: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 79988106571B for ; Wed, 21 Jan 2009 14:03:08 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from noop.in-addr.com (mail.in-addr.com [IPv6:2001:470:8:162::1]) by mx1.freebsd.org (Postfix) with ESMTP id 46E298FC20 for ; Wed, 21 Jan 2009 14:03:08 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from gjp by noop.in-addr.com with local (Exim 4.54 (FreeBSD)) id 1LPdff-000PfV-7w; Wed, 21 Jan 2009 09:03:07 -0500 Date: Wed, 21 Jan 2009 09:03:07 -0500 From: Gary Palmer To: John Rushford Message-ID: <20090121140307.GE81380@in-addr.com> References: <4975ADF4.1070103@paradise.net.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: FreeBSD-stable@freebsd.org, Reuben , Mark Kirkwood Subject: Re: Broken loader on 7.1-STABLE? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jan 2009 14:03:10 -0000 On Tue, Jan 20, 2009 at 06:22:00PM -0700, John Rushford wrote: > Hello, > > Perhaps mine is a different issue but I ran into this today. > > I loaded FreeBSD 7.1-RELEASE from a DVD onto an Apple Mac Pro after > partitioning a drive with bootcamp. The install went quite well and the > machine came up with no issues. I configured networking, X, and got gnome > working. I setup cvsup and loaded the STABLE sources, ran make buildworld, > make kernel, etc... > > I attempted to boot into single user to run mergemaster, installworld, etc.. > But the machine will not boot, I now get the following errror and prompt: > > Trying to mount root from ufs:/dev/ad9s1a > > Manual root filesystem specification: > : Mount using filesystem > e.g. ufs:da0s1a > ? List valid disk boot devices > Abort manual input > > I input ufs:/dev/ad9s1a to no avail and ? Does not list any other devices. > > I've booted from the DVD and gone into Fixit mode and can mount /dev/ad9s1a > just fine. I thought that I'd try putting back loader.old on the off chance > that might solve the problem but, I do not see a loader.old, just loader. > The kernel.old directory is there. > > Any ideas on what the issue might be and how to fix? > > Appreciate the help as I'd like to get 7.1-STABLE running on this machine. Did the kernel probe messages prior to the mountroot prompt indicate that the appropriate disk controllers were found/probed and that the disk devices were found on the disk controllers? The lack of any devices listed when you asked might indicate a kernel configuration problem. Regards, Gary P.S. Please do not top post. > > Regards > John > > > > > On 1/20/09 3:56 AM, "Mark Kirkwood" wrote: > > > Reuben wrote: > >> > >> I was wondering if anyone else was seeing loader (v1.02) break after updating > >> from 7.1-RELEASE to 7.1-STABLE. After performing the prescribed updating > >> procedure (via the handbook), the system will go through the normal steps and > >> after the boot menu will present the following error: > >> > >> Can't work out which disk we are booting from. > >> Guessed BIOS device 0xffffffff not found by probes, defaulting to disk0 > >> > >> According to the bugbusting page on the FreeBSD wiki there's two issues at > >> work that cause this behavior; patches were committed to HEAD/RELENG earlier > >> last year in Mar and Aug. Up until now I've never come across this problem > >> in 6.x or 7.0. In doing a little research I've come across a few older > >> threads via google where it was believed that the problem was caused by > >> improper CFLAGS in make.conf. I've commented mine out and rebuilt things.. > >> with the same end result. In fact, if it's any help, my CFLAGS declaration > >> in make.conf is taken verbatim from the /usr/share/examples/etc/make.conf. > >> Furthermore, on selecting option 6 from the boot menu (escape to loader > >> prompt), the system [I'm assuming] crashes displaying a blinking ASCII > >> pattern from which only a hard reboot will work. > >> > >> FWIW, this is a fairly plain system.. nothing special in sysctl.conf or > >> loader.conf, and the kernel is pretty stock as well (more or less GENERIC > >> with my sound device and pf). > >> > >> A temporary fix for me was to copy over loader.old to loader in /boot. > >> > >> > >> > > > > I am getting this too - update from RELENG_7 @12 Jan src to 20 Jan and I > > have: > > > > panic: free: guard1 fail @ 0x511d > > from /usr/src/sys/boot/i386/loader/../../common/module.c:959 > > > > Can't work out which disk we are booting from. > > Guessed BIOS device 0xffffffff not found by probes, defaulting to disk0 > > > > > > > > Copying loader.old to loader did not work around this for me - I had to > > empty loader.conf too. > > > > Here is what *was* in there: > > > > ---> begin loader.conf > > # Sound > > sound_load="YES" > > snd_hda_load="YES" > > > > # IPC > > kern.ipc.semmni=500 > > kern.ipc.semmns=500 > > > > > > # CD/DVD DMA > > atapicam_load="YES" > > hw.ata.atapi_dma=0 > > --> end loader.conf > > > > > > At this point I am not sure which if are the bad guys... > > > > > > The machine is an Asus a8vx. > > > > regards > > > > Mark > > _______________________________________________ > > 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 Wed Jan 21 14:12: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 1BCFA1065740 for ; Wed, 21 Jan 2009 14:12:58 +0000 (UTC) (envelope-from hlh@restart.be) Received: from tignes.restart.be (tignes.restart.be [IPv6:2001:41d0:1:2ad2:0:1::]) by mx1.freebsd.org (Postfix) with ESMTP id A04D58FC0C for ; Wed, 21 Jan 2009 14:12:56 +0000 (UTC) (envelope-from hlh@restart.be) Received: from restart.be (avoriaz.tunnel.bel [IPv6:2001:41d0:1:2ad2:1:ffff::]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "avoriaz.restart.be", Issuer "CA master" (verified OK)) by tignes.restart.be (Postfix) with ESMTPS id 7AE22E0420 for ; Wed, 21 Jan 2009 15:12:55 +0100 (CET) Received: from morzine.restart.bel (morzine.restart.be [IPv6:2001:41d0:1:2ad2:1:2::]) (authenticated bits=0) by restart.be (8.14.3/8.14.3) with ESMTP id n0LECrg9053122 for ; Wed, 21 Jan 2009 15:12:53 +0100 (CET) (envelope-from hlh@restart.be) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=restart.be; s=avoriaz; t=1232547175; bh=X+VH/Fqr5rKKFeX3ZbLIHb2KXUOEIYHMEY4TeRS6ci8=; h=Message-ID:Date:From:MIME-Version:To:Subject:Content-Type: Content-Transfer-Encoding; b=vhUozeSpLB48+8O+PHYOFNtZg3Up4EkL0wTSCbcql7LQ9moB0MS8PqY2zM4OrWCbu A4i9WKyx2VKIYL2lSmNhw== DomainKey-Signature: a=rsa-sha1; s=avoriaz; d=restart.be; c=nofws; q=dns; h=message-id:date:from:organization:user-agent:mime-version:to: subject:content-type:content-transfer-encoding:x-scanned-by; b=oBund9SDM6uSYC93x7eSFw+EV5Rx18LizRaB+CzqSTtMRbT/IKkHCyMVpbiPrEUkF PWW9EVFvc9iaDFzQR3qfw== Message-ID: <49772D65.7060302@restart.be> Date: Wed, 21 Jan 2009 15:12:53 +0100 From: Henri Hennebert Organization: RestartSoft User-Agent: Thunderbird 2.0.0.19 (X11/20090113) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.64 on IPv6:2001:41d0:1:2ad2:1:1:: Subject: hald and GEOM_PART_BSD + GEOM_PART_MBR X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Jan 2009 14:12:59 -0000 Just for the record, I add options GEOM_PART_BSD and GEOM_PART_MBR to my kernel config (I want to see what gpart was saying abount my disks). At boot time I get some messages as: GEOM: ad4s2: geometry does not match label. GEOM: ad4s2: media size does not match label. and more important: hald eats up cpu time and can't answer to lshal. Removing those options resolve the problem. Henri PS - I'm ready to test some patches From owner-freebsd-stable@FreeBSD.ORG Wed Jan 21 14:36: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 B549E1065686 for ; Wed, 21 Jan 2009 14:36:44 +0000 (UTC) (envelope-from frzzowear@trip.webair.com) Received: from trip.webair.com (trip.webair.com [216.130.161.100]) by mx1.freebsd.org (Postfix) with ESMTP id 74FE58FC27 for ; Wed, 21 Jan 2009 14:36:44 +0000 (UTC) (envelope-from frzzowear@trip.webair.com) Received: from trip.webair.com (localhost.webair.com [127.0.0.1]) by trip.webair.com (8.13.6/8.12.11) with ESMTP id n0LFIT1k048366 for ; Wed, 21 Jan 2009 10:18:29 -0500 (EST) (envelope-from frzzowear@trip.webair.com) Received: (from frzzowear@localhost) by trip.webair.com (8.13.6/8.12.11/Submit) id n0LFITEg048365; Wed, 21 Jan 2009 10:18:29 -0500 (EST) (envelope-from frzzowear) Date: Wed, 21 Jan 2009 10:18:29 -0500 (EST) Message-Id: <200901211518.n0LFITEg048365@trip.webair.com> To: stable@FreeBSD.ORG From: Bank of Montreal Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: unlock your account X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: securitycheck@bmo.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jan 2009 14:36:50 -0000 Access denied Your internet banking has been locked due to three consecutive failures of the banking security check. To unlock your internet banking, please activate your account below : [1] Unlock Your Internet Banking © 2009 BMO Bank of Montreal. All rights reserved. References 1. http://kellyskeepsakes.us/taggerle/BMO/BMO/BMO/BMO/BMO/BMO/BMO/bmo/ From owner-freebsd-stable@FreeBSD.ORG Wed Jan 21 14:36:50 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 BF30010656BE for ; Wed, 21 Jan 2009 14:36:44 +0000 (UTC) (envelope-from frzzowear@trip.webair.com) Received: from trip.webair.com (trip.webair.com [216.130.161.100]) by mx1.freebsd.org (Postfix) with ESMTP id 74E1A8FC26 for ; Wed, 21 Jan 2009 14:36:44 +0000 (UTC) (envelope-from frzzowear@trip.webair.com) Received: from trip.webair.com (localhost.webair.com [127.0.0.1]) by trip.webair.com (8.13.6/8.12.11) with ESMTP id n0LFITJ1048375 for ; Wed, 21 Jan 2009 10:18:29 -0500 (EST) (envelope-from frzzowear@trip.webair.com) Received: (from frzzowear@localhost) by trip.webair.com (8.13.6/8.12.11/Submit) id n0LFITsw048372; Wed, 21 Jan 2009 10:18:29 -0500 (EST) (envelope-from frzzowear) Date: Wed, 21 Jan 2009 10:18:29 -0500 (EST) Message-Id: <200901211518.n0LFITsw048372@trip.webair.com> To: stable@freebsd.org From: Bank of Montreal Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: unlock your account X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: securitycheck@bmo.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jan 2009 14:36:54 -0000 Access denied Your internet banking has been locked due to three consecutive failures of the banking security check. To unlock your internet banking, please activate your account below : [1] Unlock Your Internet Banking © 2009 BMO Bank of Montreal. All rights reserved. References 1. http://kellyskeepsakes.us/taggerle/BMO/BMO/BMO/BMO/BMO/BMO/BMO/bmo/ From owner-freebsd-stable@FreeBSD.ORG Wed Jan 21 15:01:38 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 A0DA31065676; Wed, 21 Jan 2009 15:01:38 +0000 (UTC) (envelope-from jerrymc@gizmo.acns.msu.edu) Received: from gizmo.acns.msu.edu (gizmo.acns.msu.edu [35.8.1.43]) by mx1.freebsd.org (Postfix) with ESMTP id 714BE8FC19; Wed, 21 Jan 2009 15:01:37 +0000 (UTC) (envelope-from jerrymc@gizmo.acns.msu.edu) Received: from gizmo.acns.msu.edu (localhost [127.0.0.1]) by gizmo.acns.msu.edu (8.13.6/8.13.6) with ESMTP id n0LF0ksa061526; Wed, 21 Jan 2009 10:00:46 -0500 (EST) (envelope-from jerrymc@gizmo.acns.msu.edu) Received: (from jerrymc@localhost) by gizmo.acns.msu.edu (8.13.6/8.13.6/Submit) id n0LF0kLY061525; Wed, 21 Jan 2009 10:00:46 -0500 (EST) (envelope-from jerrymc) Date: Wed, 21 Jan 2009 10:00:46 -0500 From: Jerry McAllister To: Eduardo Meyer Message-ID: <20090121150046.GA61468@gizmo.acns.msu.edu> References: <20090120161355.GA28525@hugo10.ka.punkt.de> <20090120184216.GA57318@gizmo.acns.msu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.4.2.2i Cc: Jerry McAllister , stable@freebsd.org, questions@freebsd.org Subject: Re: switching bsdlabel's label X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Jan 2009 15:01:39 -0000 On Wed, Jan 21, 2009 at 10:45:28AM -0200, Eduardo Meyer wrote: > On Tue, Jan 20, 2009 at 4:42 PM, Jerry McAllister wrote: > > On Tue, Jan 20, 2009 at 03:36:34PM -0200, Eduardo Meyer wrote: > > > >> On Tue, Jan 20, 2009 at 2:13 PM, Patrick M. Hausen wrote: > >> > Hello, > >> > > >> > On Tue, Jan 20, 2009 at 01:24:27PM -0200, Eduardo Meyer wrote: > >> >> I have a certain disk where da0s1a and da0s1d are inverted. By some > >> >> reason someone labelled root as 'd' and home as 'a'. > >> >> > >> >> Can I just > >> >> > >> >> bsdlabel -n da0s1 > savedabel.txt > >> >> > >> >> Edit savedlabel.txt, switch and restore? (bsdlabel -R da0s1 savedlabel) > >> > > >> > Why not simply use bsdlabel -e da0s1? > >> > >> Because I didnt know about that? ;-) > >> > >> Thank you for the hint. > >> > >> However I still have the same doubt. Since basically its the same > >> task, Is it safe do relabel this way? > > > > Hmmm. Is there stuff written on the disk. Is root stuff really written > > on da0s1d and /home stuff really written on da0s1a? Does the system boot > > from it OK? > > > > Or is it just that the mounts are switched. > > The mount points are not written in to the label. That comes after > > booting. If it boots, I wonder if it really is switched on the > > partitions or if it is just that the partitions are mounted backwards > > (probably due to editing /etc/fstab incorrectly). > > > > ////jerry > > Hello Patrick, thanks again. Yes, label is switched. Yes there really > are stuff on the partitions. No, I dont boot from da0s1d. It is a disk > for migration. But the one who partitioned was fooled by Sysinstall > which creates the first label on extra disks as 'd' and the last from > the allowed 7 as 'a'. Therefore this server is still booting on the > original disk (ad6s1a) and everything else is mounted in the new one > (da0s1), everything but root. What sysinstall does is assume that the 'a' partition will be used for a root mount and the 'b' partition will be used for swap. Sinc 'c' is reserved, it starts with 'd'. Then, if you later add an 'a' it will end up being later (higher offset) than the 'd'. I suppose it might confuse a person, but otherwise it is no problem and probably would be best to just leave it that way. You really only need to use the mount point anyway most of the time. So, if the mount point addresses the partition you want to with that name, then you should have no problem. You could switch it around using bsdlabel, but I don't think the risk would be worth the negligible gain. But, do as you wish. ////jerry > > > > > > > > > > >> > >> > > >> > Kind regards, > >> > Patrick > >> > -- > >> > punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe > >> > Tel. 0721 9109 0 * Fax 0721 9109 100 > >> > info@punkt.de http://www.punkt.de > >> > Gf: Jürgen Egeling AG Mannheim 108285 > >> > > >> > >> > >> > >> -- > >> =========== > >> Eduardo Meyer > >> pessoal: dudu.meyer@gmail.com > >> profissional: ddm.farmaciap@saude.gov.br > >> _______________________________________________ > >> freebsd-questions@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions > >> To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > >> > > > > > > -- > =========== > Eduardo Meyer > pessoal: dudu.meyer@gmail.com > profissional: ddm.farmaciap@saude.gov.br > From owner-freebsd-stable@FreeBSD.ORG Wed Jan 21 15:27: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 BA5D61065697; Wed, 21 Jan 2009 15:27:58 +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 1D0488FC1B; Wed, 21 Jan 2009 15:27: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 n0LFRoLA031741; Wed, 21 Jan 2009 16:27:56 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.3/8.14.3/Submit) id n0LFRoGp031740; Wed, 21 Jan 2009 16:27:50 +0100 (CET) (envelope-from olli) Date: Wed, 21 Jan 2009 16:27:50 +0100 (CET) Message-Id: <200901211527.n0LFRoGp031740@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, jerrymc@msu.edu, Eduardo Meyer In-Reply-To: <20090121150046.GA61468@gizmo.acns.msu.edu> 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]); Wed, 21 Jan 2009 16:27:56 +0100 (CET) Cc: Subject: Re: switching bsdlabel's label X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, jerrymc@msu.edu, Eduardo Meyer List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jan 2009 15:27:59 -0000 Jerry McAllister wrote: > What sysinstall does is assume that the 'a' partition will be > used for a root mount and the 'b' partition will be used for swap. > Sinc 'c' is reserved, it starts with 'd'. Then, if you later > add an 'a' it will end up being later (higher offset) than the 'd'. > > I suppose it might confuse a person, but otherwise it is no problem > and probably would be best to just leave it that way. The boot process assumes (by default) that the root file system is on the "a" partition. If it isn't, you won't be able to boot from that disk, unless you enter the real root partition at the boot0 prompt. So it is really a good idea to switch the partitions in the label before putting that disk into production. 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 "I learned Java 3 years before Python. It was my language of choice. It took me two weekends with Python before I was more productive with it than with Java." -- Anthony Roberts From owner-freebsd-stable@FreeBSD.ORG Wed Jan 21 15:40:40 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 19D451065676 for ; Wed, 21 Jan 2009 15:40:40 +0000 (UTC) (envelope-from eksffa@freebsdbrasil.com.br) Received: from capeta.freebsdbrasil.com.br (capeta.freebsdbrasil.com.br [201.48.151.3]) by mx1.freebsd.org (Postfix) with SMTP id 601388FC08 for ; Wed, 21 Jan 2009 15:40:39 +0000 (UTC) (envelope-from eksffa@freebsdbrasil.com.br) Received: (qmail 35815 invoked from network); 21 Jan 2009 13:13:57 -0200 Received: from unknown (HELO claire.bh.freebsdbrasil.com.br) (201.48.151.226) by capeta.freebsdbrasil.com.br with SMTP; 21 Jan 2009 13:13:57 -0200 Message-ID: <49773B9B.4060402@freebsdbrasil.com.br> Date: Wed, 21 Jan 2009 13:13:31 -0200 From: Patrick Tracanelli Organization: FreeBSD Brasil LTDA User-Agent: Thunderbird 2.0.0.0 (X11/20070612) MIME-Version: 1.0 To: Jerry McAllister References: <20090120161355.GA28525@hugo10.ka.punkt.de> <20090120184216.GA57318@gizmo.acns.msu.edu> <20090121150046.GA61468@gizmo.acns.msu.edu> In-Reply-To: <20090121150046.GA61468@gizmo.acns.msu.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: stable@freebsd.org, Eduardo Meyer , questions@freebsd.org Subject: Re: switching bsdlabel's label X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Jan 2009 15:40:40 -0000 Jerry McAllister escreveu: > On Wed, Jan 21, 2009 at 10:45:28AM -0200, Eduardo Meyer wrote: > >> On Tue, Jan 20, 2009 at 4:42 PM, Jerry McAllister wrote: >>> On Tue, Jan 20, 2009 at 03:36:34PM -0200, Eduardo Meyer wrote: >>> >>>> On Tue, Jan 20, 2009 at 2:13 PM, Patrick M. Hausen wrote: >>>>> Hello, >>>>> >>>>> On Tue, Jan 20, 2009 at 01:24:27PM -0200, Eduardo Meyer wrote: >>>>>> I have a certain disk where da0s1a and da0s1d are inverted. By some >>>>>> reason someone labelled root as 'd' and home as 'a'. >>>>>> >>>>>> Can I just >>>>>> >>>>>> bsdlabel -n da0s1 > savedabel.txt >>>>>> >>>>>> Edit savedlabel.txt, switch and restore? (bsdlabel -R da0s1 savedlabel) >>>>> Why not simply use bsdlabel -e da0s1? >>>> Because I didnt know about that? ;-) >>>> >>>> Thank you for the hint. >>>> >>>> However I still have the same doubt. Since basically its the same >>>> task, Is it safe do relabel this way? >>> Hmmm. Is there stuff written on the disk. Is root stuff really written >>> on da0s1d and /home stuff really written on da0s1a? Does the system boot >>> from it OK? >>> >>> Or is it just that the mounts are switched. >>> The mount points are not written in to the label. That comes after >>> booting. If it boots, I wonder if it really is switched on the >>> partitions or if it is just that the partitions are mounted backwards >>> (probably due to editing /etc/fstab incorrectly). >>> >>> ////jerry >> Hello Patrick, thanks again. Yes, label is switched. Yes there really >> are stuff on the partitions. No, I dont boot from da0s1d. It is a disk >> for migration. But the one who partitioned was fooled by Sysinstall >> which creates the first label on extra disks as 'd' and the last from >> the allowed 7 as 'a'. Therefore this server is still booting on the >> original disk (ad6s1a) and everything else is mounted in the new one >> (da0s1), everything but root. > > What sysinstall does is assume that the 'a' partition will be > used for a root mount and the 'b' partition will be used for swap. > Sinc 'c' is reserved, it starts with 'd'. Then, if you later > add an 'a' it will end up being later (higher offset) than the 'd'. > > I suppose it might confuse a person, but otherwise it is no problem > and probably would be best to just leave it that way. You really > only need to use the mount point anyway most of the time. So, if > the mount point addresses the partition you want to with that name, > then you should have no problem. > > You could switch it around using bsdlabel, but I don't think the > risk would be worth the negligible gain. But, do as you wish. > > ////jerry > > >>> >>> >>> >>>>> Kind regards, >>>>> Patrick >>>>> -- >>>>> punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe >>>>> Tel. 0721 9109 0 * Fax 0721 9109 100 >>>>> info@punkt.de http://www.punkt.de >>>>> Gf: Jürgen Egeling AG Mannheim 108285 Hello, Yes, you can do this change anytime you want, since (1) da0s1* are unmounted and (2) disk is clean. Therefore I suggest you are in single user mode. If you feel unsure, backup the current label scheme with disklabel da0s1 -n > da0s1.disklabel.bk You can restore anytime with the Rescue Disk. Go ahead, no problem. Sometimes you will really have problem booting from a disk if root is not on label 'a'. I believe it can be workarounded, but your will is safe, go ahead and switch the labels. You can always remember the person who did this from sysinstall that sysinstall will label as 'a' if the mount point is root (/). Therefore if someone wants to use sysinstall for labelling in production, and wont mount on / since / has the current root, one can always fool sysinstall, (C)reating the partition, using / as mpoint and mater redefining the (M)ount point to somewhere else, say, to /mnt. I always relabel this way, never had a problem. TinyBSD sometimes relabels this way too, for some PC Engines Wrap boards. Go ahead. -- Patrick Tracanelli Tel.: (31) 3516-0800 316601@sip.freebsdbrasil.com.br http://www.freebsdbrasil.com.br "Long live Hanin Elias, Kim Deal!" From owner-freebsd-stable@FreeBSD.ORG Wed Jan 21 16:22: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 2FBF11065754 for ; Wed, 21 Jan 2009 16:22:41 +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 9A32D8FC19 for ; Wed, 21 Jan 2009 16:22:39 +0000 (UTC) (envelope-from amarat@ksu.ru) X-IronPort-AV: E=Sophos;i="4.37,301,1231102800"; d="scan'208";a="1293129" Received: from mail.ksu.ru (HELO ruby.ksu.ru) ([193.232.252.56]) by iout.kzn.ru with ESMTP; 21 Jan 2009 19:22:23 +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 n0LGJlZv012482; Wed, 21 Jan 2009 16:19:47 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 n0LGM6Gm083023; Wed, 21 Jan 2009 19:22:08 +0300 (MSK) (envelope-from amarat@ksu.ru) Message-ID: <49774BAE.3000809@ksu.ru> Date: Wed, 21 Jan 2009 19:22:06 +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: Pete French References: In-Reply-To: Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jan 2009 16:22:41 -0000 Pete French 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! > > -pete. > it's a kind of magic, really. I built a new kernel with KDB and DDB and after 1 day, 13:15 I'm still waiting for storm to arrive. And I added hw.acpi.osname="Linux" to /boot/loader.conf. -- SY, Marat From owner-freebsd-stable@FreeBSD.ORG Wed Jan 21 16:30: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 A72B5106575F for ; Wed, 21 Jan 2009 16:30:27 +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 77F568FC25 for ; Wed, 21 Jan 2009 16:30:27 +0000 (UTC) (envelope-from dan@langille.org) Received: from localhost (localhost [127.0.0.1]) by nyi.unixathome.org (Postfix) with ESMTP id 2335A509B5; Wed, 21 Jan 2009 16:30:27 +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 exi7Bd1vGlo8; Wed, 21 Jan 2009 16:30:24 +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 8EFCA509AD ; Wed, 21 Jan 2009 16:30:24 +0000 (GMT) Message-ID: <49774D93.2080503@langille.org> Date: Wed, 21 Jan 2009 11:30:11 -0500 From: Dan Langille Organization: The FreeBSD Diary User-Agent: Thunderbird 2.0.0.19 (X11/20090119) MIME-Version: 1.0 To: "Marat N.Afanasyev" References: <49774BAE.3000809@ksu.ru> In-Reply-To: <49774BAE.3000809@ksu.ru> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Pete French 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jan 2009 16:30:30 -0000 Marat N.Afanasyev wrote: > Pete French 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! >> >> -pete. >> > > it's a kind of magic, really. I built a new kernel with KDB and DDB and > after 1 day, 13:15 I'm still waiting for storm to arrive. And I added > hw.acpi.osname="Linux" to /boot/loader.conf. If that solution works, it'd got to leave a 'bad' taste in your mouth. ;) -- 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 Wed Jan 21 16:49:29 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 606B1106564A for ; Wed, 21 Jan 2009 16:49:29 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.157]) by mx1.freebsd.org (Postfix) with ESMTP id E11268FC08 for ; Wed, 21 Jan 2009 16:49:28 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: by fg-out-1718.google.com with SMTP id l26so2204743fgb.35 for ; Wed, 21 Jan 2009 08:49:27 -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=p6CPPfi2sv5RWCgUMOs9JWJN17226K3JkOJHyu71f5c=; b=GGTGH1+q3KdBslukPoWWU37d2k+Sy79i9qzstamDLbcYHHaWYXV0IVA7BgSTCQh6Ar n+BYlNKWu2osOKlVolfRa4K8eWJWTrXkadc8o6bHutBhxoyDbwQcABWd3bxBt/RSyC3V zAWKwTxRY8zvrT+7LzYPIQ05lPBs6dOL0MP+c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=sVB89qfv3jgVWedSf26iVXkcJglIIP+dQw2NNQuIQHDb74/VBm+50TEyEixjjLXGBv 7oDPn8orNRiE5ZMav300FQUSh9SgNYKPwt4bztucM6exAAj1OnWafSPW1jnEgZn0oKmj ydETAFDrqGLnPkdDTgJGEyXpIrUtuDnABoq/A= MIME-Version: 1.0 Received: by 10.86.79.19 with SMTP id c19mr2520697fgb.41.1232556567889; Wed, 21 Jan 2009 08:49:27 -0800 (PST) In-Reply-To: <20090121134047.3176a950@zelda.local> References: <4971B18D.3090803@optusnet.com.au> <20090121134047.3176a950@zelda.local> Date: Wed, 21 Jan 2009 19:49:27 +0300 Message-ID: From: pluknet To: Martin Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Tony Maher , stable@freebsd.org Subject: Re: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jan 2009 16:49:29 -0000 2009/1/21 Martin : > The problem worsened now. I cannot get my USB mouse working until I > reattach it physically. This is not a problem on other OSes, it seems. > > During device detection and initialization of uhci/ehci my USB-mouse > is switched off and does not get power anymore. Seen also on -CURRENT (an old usb stack) installed on my Asus P5k with all USB devices used (mouse & kboard). -- wbr, pluknet From owner-freebsd-stable@FreeBSD.ORG Wed Jan 21 17:19: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 48666106566C; Wed, 21 Jan 2009 17:19:40 +0000 (UTC) (envelope-from jjr@larush.com) Received: from mail.alisa.org (mail.alisa.org [65.103.114.105]) by mx1.freebsd.org (Postfix) with ESMTP id C1A6D8FC25; Wed, 21 Jan 2009 17:19:39 +0000 (UTC) (envelope-from jjr@larush.com) Received: from mail.alisa.org (localhost [127.0.0.1]) by mail.alisa.org (8.14.3/8.14.3) with ESMTP id n0LGqpRN058442 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 21 Jan 2009 09:52:51 -0700 (MST) (envelope-from jjr@larush.com) Received: (from www@localhost) by mail.alisa.org (8.14.3/8.14.3/Submit) id n0LGqofN058440; Wed, 21 Jan 2009 09:52:50 -0700 (MST) (envelope-from jjr@larush.com) X-Authentication-Warning: mail.alisa.org: www set sender to jjr@larush.com using -f Received: from 198.178.8.81 (SquirrelMail authenticated user jjr) by www.larush.com with HTTP; Wed, 21 Jan 2009 09:52:50 -0700 (MST) Message-ID: <1f05a49079a04f3041197f13323105e5.squirrel@www.larush.com> In-Reply-To: <20090121140307.GE81380@in-addr.com> References: <4975ADF4.1070103@paradise.net.nz> <20090121140307.GE81380@in-addr.com> Date: Wed, 21 Jan 2009 09:52:50 -0700 (MST) From: jjr@larush.com To: "Gary Palmer" User-Agent: SquirrelMail/1.4.17 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0.1 (mail.alisa.org [127.0.0.1]); Wed, 21 Jan 2009 09:52:51 -0700 (MST) Cc: freebsd-stable@freebsd.org, John Rushford , Reuben , Mark Kirkwood Subject: Re: Broken loader on 7.1-STABLE? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jan 2009 17:19:40 -0000 > On Tue, Jan 20, 2009 at 06:22:00PM -0700, John Rushford wrote: >> Hello, >> >> Perhaps mine is a different issue but I ran into this today. >> >> I loaded FreeBSD 7.1-RELEASE from a DVD onto an Apple Mac Pro after >> partitioning a drive with bootcamp. The install went quite well and the >> machine came up with no issues. I configured networking, X, and got >> gnome >> working. I setup cvsup and loaded the STABLE sources, ran make >> buildworld, >> make kernel, etc... >> >> I attempted to boot into single user to run mergemaster, installworld, >> etc.. >> But the machine will not boot, I now get the following errror and >> prompt: >> >> Trying to mount root from ufs:/dev/ad9s1a >> >> Manual root filesystem specification: >> : Mount using filesystem >> e.g. ufs:da0s1a >> ? List valid disk boot devices >> Abort manual input >> >> I input ufs:/dev/ad9s1a to no avail and ? Does not list any other >> devices. >> >> I've booted from the DVD and gone into Fixit mode and can mount >> /dev/ad9s1a >> just fine. I thought that I'd try putting back loader.old on the off >> chance >> that might solve the problem but, I do not see a loader.old, just >> loader. >> The kernel.old directory is there. >> >> Any ideas on what the issue might be and how to fix? >> >> Appreciate the help as I'd like to get 7.1-STABLE running on this >> machine. > > Did the kernel probe messages prior to the mountroot prompt indicate that > the appropriate disk controllers were found/probed and that the > disk devices were found on the disk controllers? The lack of > any devices listed when you asked might indicate a kernel configuration > problem. > > Regards, > > Gary > > P.S. Please do not top post. > I believe the appropriate disk controllers were found, I had no trouble mounting the root filesystem while in Fixit. I'll double check this evening and let you know. I have gone back and booted without issue from kernel.old and the machine is running 7.1-RELEASE. John From owner-freebsd-stable@FreeBSD.ORG Wed Jan 21 18:10:11 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 567131065757 for ; Wed, 21 Jan 2009 18:10:11 +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 9D6638FC26 for ; Wed, 21 Jan 2009 18:10:07 +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 4169D46B32; Wed, 21 Jan 2009 13:10:07 -0500 (EST) Date: Wed, 21 Jan 2009 18:10:07 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: dikshie In-Reply-To: <910e60e80901210319mbb13fbxa8659577bb5ea162@mail.gmail.com> Message-ID: References: <910e60e80901210319mbb13fbxa8659577bb5ea162@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: unkillable proceess X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Jan 2009 18:10:29 -0000 On Wed, 21 Jan 2009, dikshie wrote: > Hi, > how to kill unkillable process: > > # ps axuf |grep http > www 66005 73.4 1.3 87656 13164 ?? R 4:58PM 62:24.41 > /usr/local/sbin/httpd -DSSL -DNOHTTPACCEPT > www 4277 71.6 1.4 88680 13964 ?? R 4:12PM 48:23.40 > /usr/local/sbin/httpd -DSSL -DNOHTTPACCEPT > www 2708 65.5 1.4 88680 14112 ?? R 4:12PM 54:39.50 > /usr/local/sbin/httpd -DSSL -DNOHTTPACCEPT > > above processes unkillable Could you show us the output of "procstat -kk" on one or all of the above processes? Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-stable@FreeBSD.ORG Wed Jan 21 19:23: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 03B4A1065673 for ; Wed, 21 Jan 2009 19:23:27 +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 6F8BB8FC12 for ; Wed, 21 Jan 2009 19:23:25 +0000 (UTC) (envelope-from amarat@ksu.ru) X-IronPort-AV: E=Sophos;i="4.37,301,1231102800"; d="scan'208";a="1294944" Received: from mail.ksu.ru (HELO ruby.ksu.ru) ([193.232.252.56]) by iout.kzn.ru with ESMTP; 21 Jan 2009 22:23:24 +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 n0LJKr1K001080; Wed, 21 Jan 2009 19:20: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 n0LJNC9f084078; Wed, 21 Jan 2009 22:23:13 +0300 (MSK) (envelope-from amarat@ksu.ru) Message-ID: <49777620.8080307@ksu.ru> Date: Wed, 21 Jan 2009 22:23:12 +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: Dan Langille References: <49774BAE.3000809@ksu.ru> <49774D93.2080503@langille.org> In-Reply-To: <49774D93.2080503@langille.org> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Pete French 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jan 2009 19:23:27 -0000 Dan Langille wrote: > Marat N.Afanasyev wrote: >> Pete French 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! >>> >>> -pete. >>> >> >> it's a kind of magic, really. I built a new kernel with KDB and DDB >> and after 1 day, 13:15 I'm still waiting for storm to arrive. And I added >> hw.acpi.osname="Linux" to /boot/loader.conf. > > If that solution works, it'd got to leave a 'bad' taste in your mouth. ;) > yeah, but it would taste not so bad as hw.acpi.osname="Windows ..." ;) -- SY, Marat From owner-freebsd-stable@FreeBSD.ORG Wed Jan 21 19:39: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 5B74E106564A for ; Wed, 21 Jan 2009 19:39:04 +0000 (UTC) (envelope-from nakal@web.de) Received: from fmmailgate02.web.de (fmmailgate02.web.de [217.72.192.227]) by mx1.freebsd.org (Postfix) with ESMTP id 17B588FC08 for ; Wed, 21 Jan 2009 19:39:04 +0000 (UTC) (envelope-from nakal@web.de) Received: from smtp06.web.de (fmsmtp06.dlan.cinetic.de [172.20.5.172]) by fmmailgate02.web.de (Postfix) with ESMTP id 092ADF93D326; Wed, 21 Jan 2009 20:39:03 +0100 (CET) Received: from [217.236.0.162] (helo=zelda.local) by smtp06.web.de with asmtp (TLSv1:AES128-SHA:128) (WEB.DE 4.110 #277) id 1LPiui-0005Dx-00; Wed, 21 Jan 2009 20:39:00 +0100 Date: Wed, 21 Jan 2009 20:38:56 +0100 From: Martin To: Pieter de Goeje Message-ID: <20090121203856.387afd82@zelda.local> In-Reply-To: <200901211415.38384.pieter@degoeje.nl> References: <4971B18D.3090803@optusnet.com.au> <20090121134047.3176a950@zelda.local> <49771B2F.7050902@bsd.ee> <200901211415.38384.pieter@degoeje.nl> X-Mailer: Claws Mail 3.7.0 (GTK+ 2.14.7; amd64-portbld-freebsd7.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: nakal@web.de X-Sender: nakal@web.de X-Provags-ID: V01U2FsdGVkX1/tN5bll6dOh1m8z5FI8bgG8OUXagREVjVNje39 Ux8Zq6s4Lqzu1sD47W86BQ+I+jhkTFu3F9wn1W9OUcBX6Ll9Qh d+s/7q7pU= Cc: Andrei Kolu , Tony Maher , freebsd-stable@freebsd.org Subject: Re: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jan 2009 19:39:04 -0000 Am Wed, 21 Jan 2009 14:15:38 +0100 schrieb Pieter de Goeje : > I have a Gigabyte GA-P35-DS3R w/ a Logitech G5 mouse and usb > keyboard. I had to switch to usb2 on freebsd 8-current for the > keyboard to attach after boot. I have enabled usb keyboard support in > the BIOS (otherwise the keyboard cannot be used during the boot > process). Everything is working fine now. Hi Pieter. Thank you for the hint with usb2. I'll try it as soon as possible. -- Martin From owner-freebsd-stable@FreeBSD.ORG Wed Jan 21 19:57: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 0CD5010656C3 for ; Wed, 21 Jan 2009 19:57:38 +0000 (UTC) (envelope-from jeff@sailorfej.net) Received: from mail.sailorfej.net (mail.sailorfej.net [66.93.72.123]) by mx1.freebsd.org (Postfix) with ESMTP id DAB2A8FC1C for ; Wed, 21 Jan 2009 19:57:37 +0000 (UTC) (envelope-from jeff@sailorfej.net) Received: from [10.3.3.117] (65-122-120-98.dia.static.qwest.net [65.122.120.98]) (authenticated bits=0) by mail.sailorfej.net (8.13.8/8.13.8) with ESMTP id n0LJfteK095384 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 21 Jan 2009 11:41:57 -0800 (PST) (envelope-from jeff@sailorfej.net) Message-ID: <49777A7E.30904@sailorfej.net> Date: Wed, 21 Jan 2009 11:41:50 -0800 From: Jeffrey Williams 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 X-Spam-Status: No, score=-1.2 required=6.0 tests=BAYES_00,SPF_SOFTFAIL autolearn=no version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on mail.sailorfej.net Subject: FreeBSD 7, runaway clock as guest OS on Microsoft Virtual Server X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Jan 2009 19:57:38 -0000 Hi Folks, I am trying to run FreeBSD 7 on Microsoft Virtual Server 2005 R2, Windows Server 2003, on a Dell 2950. I am having a problem with the system clock running excessively fast, I initially tried installing 7.1 release but received a nearly continuous stream of the "calcru: runtime went backward errors", I tried rolling back to 7.0, and it improved somewhat, but I still received regular "calcru" errors, and it the system clock was running to fast for ntpd to keep up with it, I set sysctl kern.timecounter.hardware to i8254 (it tries to default to ACPI-safe), which helped more, ntpd is now able to keep pace with it, but only barely, and I haven't seen any "calcru" errors yet. From the boot time dmesg, on the CPU line, the frequency reported with in the parenthesizes varies on almost every reboot. Are there any other adjustments I can make to get this under control? Following are samples of sysctl values, dmesg, and a short log sample to show the time and time reset rates. ******** sysctl grep clockrate: kern.clockrate: { hz = 1000, tick = 1000, profhz = 1024, stathz = 128 } hw.clockrate: 1061 ******** sysctl grep timecounter: kern.timecounter.tick: 1 kern.timecounter.choice: TSC(800) ACPI-safe(850) i8254(0) dummy(-1000000) kern.timecounter.hardware: i8254 kern.timecounter.nsetclock: 12 kern.timecounter.ngetmicrotime: 8071302 kern.timecounter.ngetnanotime: 9 kern.timecounter.ngetbintime: 0 kern.timecounter.ngetmicrouptime: 2310540 kern.timecounter.ngetnanouptime: 3870 kern.timecounter.ngetbinuptime: 237939 kern.timecounter.nmicrotime: 48722 kern.timecounter.nnanotime: 2143 kern.timecounter.nbintime: 50865 kern.timecounter.nmicrouptime: 4498 kern.timecounter.nnanouptime: 1 kern.timecounter.nbinuptime: 477504 kern.timecounter.stepwarnings: 0 kern.timecounter.tc.i8254.mask: 4294967295 kern.timecounter.tc.i8254.counter: 3077011530 kern.timecounter.tc.i8254.frequency: 1193182 kern.timecounter.tc.i8254.quality: 0 kern.timecounter.tc.ACPI-safe.mask: 16777215 kern.timecounter.tc.ACPI-safe.counter: 14993826 kern.timecounter.tc.ACPI-safe.frequency: 3579545 kern.timecounter.tc.ACPI-safe.quality: 850 kern.timecounter.tc.TSC.mask: 4294967295 kern.timecounter.tc.TSC.counter: 3664196446 kern.timecounter.tc.TSC.frequency: 1061252458 kern.timecounter.tc.TSC.quality: 800 kern.timecounter.smp_tsc: 0 ********** sample log: Jan 20 19:25:08 host ntpd[1829]: time reset -12.179675 s Jan 20 19:25:08 host ntpd[1829]: kernel time sync disabled 6041 Jan 20 21:25:34 host ntpd[1829]: time reset -17.665523 s Jan 20 21:25:34 host ntpd[1829]: kernel time sync enabled 2001 Jan 20 23:43:24 host ntpd[1829]: kernel time sync enabled 6001 Jan 20 23:59:15 host ntpd[1829]: time reset -67.677336 s Jan 20 23:59:15 host ntpd[1829]: kernel time sync enabled 2001 Jan 21 00:51:31 host ntpd[1829]: kernel time sync enabled 6001 Jan 21 00:51:27 host ntpd[1829]: time reset -11.695334 s Jan 21 00:51:27 host ntpd[1829]: kernel time sync enabled 2001 ********** dmesg.boot: Copyright (c) 1992-2008 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.0-RELEASE-p9 #0: Tue Jan 13 19:45:51 PST 2009 root@host:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(R) CPU E5320 @ 1.86GHz (1364.45-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6fb Stepping = 11 Features=0x7c0a97b AMD Features2=0x1 Cores per package: 4 real memory = 536805376 (511 MB) avail memory = 511385600 (487 MB) kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) hptrr: HPT RocketRAID controller driver v1.1 (Jan 13 2009 19:45:26) acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, 1ff00000 (3) failed Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 7.1 on pci0 ata0: on atapci0 ata0: [ITHREAD] ata1: on atapci0 ata1: [ITHREAD] pci0: at device 7.3 (no driver attached) vgapci0: mem 0xf8000000-0xfbffffff at device 8.0 on pci0 de0: port 0xec00-0xec7f mem 0xfebff000-0xfebfffff irq 11 at device 10.0 on pci0 de0: 21140A [10-100Mb/s] pass 2.0 de0: using obsoleted if_watchdog interface de0: Ethernet address: 00:03:ff:48:a7:20 de0: [ITHREAD] 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 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio0: [FILTER] sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A sio1: [FILTER] fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: does not respond device_attach: fdc0 attach returned 6 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: does not respond device_attach: fdc0 attach returned 6 pmtimer0 on isa0 orm0: at iomem 0xc0000-0xcbfff,0xcc000-0xcc7ff pnpid ORM0000 on isa0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppbus0: on ppc0 ppbus0: [ITHREAD] plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 ppc0: [GIANT-LOCKED] ppc0: [ITHREAD] sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounter "TSC" frequency 1364446545 Hz quality 800 Timecounters tick every 1.000 msec hptrr: no controller detected. ad0: 81918MB at ata0-master WDMA2 acd0: DVDROM at ata1-master PIO4 Trying to mount root from ufs:/dev/ad0s1a From owner-freebsd-stable@FreeBSD.ORG Wed Jan 21 19:59: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 5A05110656EA for ; Wed, 21 Jan 2009 19:59:59 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from mail-ew0-f20.google.com (mail-ew0-f20.google.com [209.85.219.20]) by mx1.freebsd.org (Postfix) with ESMTP id DBEA98FC1A for ; Wed, 21 Jan 2009 19:59:58 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: by ewy13 with SMTP id 13so2253261ewy.19 for ; Wed, 21 Jan 2009 11:59:58 -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=auPuOzgug47nFPV8GPAukIO1QSrkG3OkGy7BpJZCNFo=; b=P7RRSAgcixdVUxfn6Ft/1z14wikXXrDixdNtAHu9vKoLuflfDrRTxRs5nP1fGkv/17 i62KIxbmVgIkS4HMH1cx5bjtGyK7MUiaT0LGsnvBdca+jIzFf6OR+s6/p41C6hAjjPIM ByANdrsVLQmXPUWfWtB6LFCqBggWDHG+/8kpg= 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=u3xKRRrVhKSump6UoQg35+w0XLLYDSrwy6LO6+KDacSz5VWovfMMXyvHhPmKRznxXk 3KY637VyapnD/YA2R+H1suAyVRq0ZtkuzBQevh5p6HoM5Cf8WCb7MocDO275QRdtpFSQ Xa/wFOMtSH1nr+fEa/wqxcRRy/nyoTmyF0frA= MIME-Version: 1.0 Received: by 10.86.60.14 with SMTP id i14mr1311526fga.70.1232567997340; Wed, 21 Jan 2009 11:59:57 -0800 (PST) In-Reply-To: <20090120201550.GA25090@keltia.freenix.fr> References: <20090119224750.GA7463@keltia.freenix.fr> <20090120201550.GA25090@keltia.freenix.fr> Date: Wed, 21 Jan 2009 22:59:57 +0300 Message-ID: From: pluknet To: Ollivier Robert Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: SYSV* mandatory for COMPAT_IA32 on amd64? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jan 2009 20:00:00 -0000 2009/1/20 Ollivier Robert : > According to pluknet: >> To clarify: >> I.e. on older versions you had no errors with COMPAT_IA32 and without SYSV* ? > > I think so. I may be wrong, but according to compat/freebsd32/syscalls.master 32bit compat SYSV* syscalls are mandatory (marked as STD) for kernel since long time ago. And "usual" ones are marked as NOSTD and "initialized by the SYSV* code if present or loaded". -- wbr, pluknet From owner-freebsd-stable@FreeBSD.ORG Wed Jan 21 20:09: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 1F91B10656CB for ; Wed, 21 Jan 2009 20:09:59 +0000 (UTC) (envelope-from mkhitrov@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.156]) by mx1.freebsd.org (Postfix) with ESMTP id A0F428FC12 for ; Wed, 21 Jan 2009 20:09:58 +0000 (UTC) (envelope-from mkhitrov@gmail.com) Received: by fg-out-1718.google.com with SMTP id l26so2275606fgb.35 for ; Wed, 21 Jan 2009 12:09:57 -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=h5ee61LbnAA1mu768ox04dV2/iyReaihaPXnrVR1D7o=; b=qwmrT5dVsy88LjwUxhyoZPNsqduE3ehINYt3D5VOhC35KbF2OG0Sx6mfSDmajOedMb 8wMhl3F2PmNwFqYABZEd/ZNmg0Iip1xVRIC2xx15XFaTq43xXxk79CPOfmQoxGoXVdAF OoMI/EqCIskMaEaqdlWnFW3xtS6qkvCqOrRXM= 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=qTFNsEO3Gcz1BWAXyPTGBJvDRQBU7d0WeHOxQn9ZRLPx/yXoXzYr6UnnsT+FjwUkAK LbVesdKaxild4v8MMwUkX+QbK2PaPS26jHUeONj1C37+xPsli5hW9neSrRpYPuCb1bN+ lpHLy5pyZTPDKHy/h//Y95zvIrQTtBiD97hos= MIME-Version: 1.0 Received: by 10.223.106.68 with SMTP id w4mr772351fao.19.1232568597057; Wed, 21 Jan 2009 12:09:57 -0800 (PST) In-Reply-To: <49777A7E.30904@sailorfej.net> References: <49777A7E.30904@sailorfej.net> Date: Wed, 21 Jan 2009 15:09:56 -0500 Message-ID: <26ddd1750901211209k83250d7re8bb82dc2965ccd0@mail.gmail.com> From: Maxim Khitrov To: Jeffrey Williams Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 7, runaway clock as guest OS on Microsoft Virtual Server X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Jan 2009 20:10:00 -0000 On Wed, Jan 21, 2009 at 2:41 PM, Jeffrey Williams wrote: > Hi Folks, > > I am trying to run FreeBSD 7 on Microsoft Virtual Server 2005 R2, Windows > Server 2003, on a Dell 2950. > > I am having a problem with the system clock running excessively fast, I > initially tried installing 7.1 release but received a nearly continuous > stream of the "calcru: runtime went backward errors", I tried rolling back > to 7.0, and it improved somewhat, but I still received regular "calcru" > errors, and it the system clock was running to fast for ntpd to keep up with > it, I set sysctl kern.timecounter.hardware to i8254 (it tries to default to > ACPI-safe), which helped more, ntpd is now able to keep pace with it, but > only barely, and I haven't seen any "calcru" errors yet. > > From the boot time dmesg, on the CPU line, the frequency reported with in > the parenthesizes varies on almost every reboot. > > Are there any other adjustments I can make to get this under control? Have you tried reducing the value of kern.hz (kern.hz="100" in /boot/loader.conf)? That fixes some clock-related problems on VMWare Server. - Max From owner-freebsd-stable@FreeBSD.ORG Wed Jan 21 20:10: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 2EA3F1065779 for ; Wed, 21 Jan 2009 20:10:16 +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 E41CC8FC18 for ; Wed, 21 Jan 2009 20:10:15 +0000 (UTC) (envelope-from dimitry@andric.com) Received: from [IPv6:2001:7b8:3a7:0:1416:e549:1db8:acb8] (unknown [IPv6:2001:7b8:3a7:0:1416:e549:1db8:acb8]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 0E67E11F838; Wed, 21 Jan 2009 21:10:15 +0100 (CET) Message-ID: <49778128.1080104@andric.com> Date: Wed, 21 Jan 2009 21:10:16 +0100 From: Dimitry Andric 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: Jeffrey Williams References: <49777A7E.30904@sailorfej.net> In-Reply-To: <49777A7E.30904@sailorfej.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 7, runaway clock as guest OS on Microsoft Virtual Server X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Jan 2009 20:10:17 -0000 On 2009-01-21 20:41, Jeffrey Williams wrote: > I am having a problem with the system clock running excessively fast, I > initially tried installing 7.1 release but received a nearly continuous > stream of the "calcru: runtime went backward errors" Add the following to your /boot/loader.conf file: kern.hz="100" I always use this setting with FreeBSD under VMware, and it solves all these timing problems for me. (But YMMV.) However, I am not sure what is at fault here, VMware or FreeBSD... I'd guess the latter, since neither Linux nor Windows guest OSes seem to have any such timing problems. From owner-freebsd-stable@FreeBSD.ORG Wed Jan 21 20:12:18 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 48AE61065754 for ; Wed, 21 Jan 2009 20:12:18 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from mail-ew0-f20.google.com (mail-ew0-f20.google.com [209.85.219.20]) by mx1.freebsd.org (Postfix) with ESMTP id A272B8FC17 for ; Wed, 21 Jan 2009 20:12:17 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: by ewy13 with SMTP id 13so2271205ewy.19 for ; Wed, 21 Jan 2009 12:12:16 -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=o5868Rh9SGC/Oi/Rfh27dlw1iAj+VZ7aYWfNqtzWO1M=; b=iPKqqFs9iIi8zZldwWH4Bu6ITmk1qQjtkUhz06DcYYQ1s6fWSLaKRAxb3dt4sNNs9I nkJ7cKxvXnwvzL54hEYrDUhlvJKpQhBgtIFM8oRfIwqjSZdD+KblWlCVtQjuTcGq8Xwr ChqzimBC/ntaRlGRIx7RAtalwD9Cxppmr79Hk= 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=CLKByrRgiFu1A4Z7YsTAmbCB01ev1rB27LuBNTd/KnedP7eeIVSTkcKyZ6ayUWcqVG HxZDWKgjCXeLJslJKNbwdNfP9gSB//bz4Pd+e35yBy5PgAi7K0F9Ftz1mxBbxTriV0o4 mzerlrTnV5K/QxOGHNmIj7Tc+3MM21Z8xUEEg= MIME-Version: 1.0 Received: by 10.86.99.9 with SMTP id w9mr1794548fgb.38.1232568736382; Wed, 21 Jan 2009 12:12:16 -0800 (PST) In-Reply-To: <20090119224750.GA7463@keltia.freenix.fr> References: <20090119224750.GA7463@keltia.freenix.fr> Date: Wed, 21 Jan 2009 23:12:16 +0300 Message-ID: From: pluknet To: Ollivier Robert Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, John Baldwin Subject: Re: SYSV* mandatory for COMPAT_IA32 on amd64? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jan 2009 20:12:19 -0000 2009/1/20 Ollivier Robert : > I must have missed the HEADS-UP or something but it seems that the SYSV IPC > options are now mandatory in order to compile an amd64 kernel with > COMPAT_IA32... I get linking errors in kernel.debug because > freebsd32_syscalls.o is referencing the SYSV syscalls... > > Am I alone? It seems there was always so that COMPAT_IA32 option also required SYSV* options. At least since sys/compat/freebsd32/syscalls.master v1.2 those sysv* marked as always included. Earlier COMPAT_IA32 sysv* modules could not be loaded (even if such one exists). But since r183365 (and subsequent MFC to 6/7) this restriction starts to look odd. -- wbr, pluknet From owner-freebsd-stable@FreeBSD.ORG Wed Jan 21 20:27:16 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 2ACDB106577A; Wed, 21 Jan 2009 20:27:16 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id 149388FC22; Wed, 21 Jan 2009 20:27:14 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.14.3/8.14.3) with ESMTP id n0LKRCOp099817; Wed, 21 Jan 2009 15:27:12 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-legacy.sentex.ca (freebsd-legacy.sentex.ca [64.7.128.104]) by smtp2.sentex.ca (8.14.3/8.14.3) with ESMTP id n0LKRC1H041564; Wed, 21 Jan 2009 15:27:12 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-legacy.sentex.ca (Postfix, from userid 666) id D18E5241BA; Wed, 21 Jan 2009 15:27:11 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20090121202711.D18E5241BA@freebsd-legacy.sentex.ca> Date: Wed, 21 Jan 2009 15:27:11 -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 64.7.153.18 Cc: Subject: [releng_6 tinderbox] failure on i386/i386 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: Wed, 21 Jan 2009 20:27:18 -0000 TB --- 2009-01-21 19:22:27 - tinderbox 2.6 running on freebsd-legacy.sentex.ca TB --- 2009-01-21 19:22:27 - starting RELENG_6 tinderbox run for i386/i386 TB --- 2009-01-21 19:22:27 - cleaning the object tree TB --- 2009-01-21 19:23:24 - cvsupping the source tree TB --- 2009-01-21 19:23:24 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_6/i386/i386/supfile TB --- 2009-01-21 19:23:36 - building world TB --- 2009-01-21 19:23:36 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-21 19:23:36 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-21 19:23:36 - TARGET=i386 TB --- 2009-01-21 19:23:36 - TARGET_ARCH=i386 TB --- 2009-01-21 19:23:36 - TZ=UTC TB --- 2009-01-21 19:23:36 - __MAKE_CONF=/dev/null TB --- 2009-01-21 19:23:36 - cd /src TB --- 2009-01-21 19:23:36 - /usr/bin/make -B buildworld >>> 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 TB --- 2009-01-21 20:17:50 - generating LINT kernel config TB --- 2009-01-21 20:17:50 - cd /src/sys/i386/conf TB --- 2009-01-21 20:17:50 - /usr/bin/make -B LINT TB --- 2009-01-21 20:17:50 - building LINT kernel TB --- 2009-01-21 20:17:50 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-21 20:17:50 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-21 20:17:50 - TARGET=i386 TB --- 2009-01-21 20:17:50 - TARGET_ARCH=i386 TB --- 2009-01-21 20:17:50 - TZ=UTC TB --- 2009-01-21 20:17:50 - __MAKE_CONF=/dev/null TB --- 2009-01-21 20:17:50 - cd /src TB --- 2009-01-21 20:17:50 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Wed Jan 21 20:17:50 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 [...] cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -I/src/sys/dev/em -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 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/kern/vfs_lookup.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -I/src/sys/dev/em -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 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/kern/vfs_mount.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -I/src/sys/dev/em -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 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/kern/vfs_subr.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -I/src/sys/dev/em -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 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/kern/vfs_syscalls.c /src/sys/kern/vfs_syscalls.c: In function `kern_getdirentries': /src/sys/kern/vfs_syscalls.c:3715: error: `uap' undeclared (first use in this function) /src/sys/kern/vfs_syscalls.c:3715: error: (Each undeclared identifier is reported only once /src/sys/kern/vfs_syscalls.c:3715: error: for each function it appears in.) *** Error code 1 Stop in /obj/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-01-21 20:27:11 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-01-21 20:27:11 - ERROR: failed to build lint kernel TB --- 2009-01-21 20:27:11 - 2987.88 user 366.90 system 3884.59 real http://tinderbox.des.no/tinderbox-releng_6-RELENG_6-i386-i386.full From owner-freebsd-stable@FreeBSD.ORG Wed Jan 21 20:28: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 66D171065BFE for ; Wed, 21 Jan 2009 20:28:44 +0000 (UTC) (envelope-from mike@jellydonut.org) Received: from rn-out-0910.google.com (rn-out-0910.google.com [64.233.170.185]) by mx1.freebsd.org (Postfix) with ESMTP id 2E1E98FC23 for ; Wed, 21 Jan 2009 20:28:43 +0000 (UTC) (envelope-from mike@jellydonut.org) Received: by rn-out-0910.google.com with SMTP id k32so549365rnd.12 for ; Wed, 21 Jan 2009 12:28:43 -0800 (PST) MIME-Version: 1.0 Received: by 10.90.94.15 with SMTP id r15mr3589802agb.56.1232568055945; Wed, 21 Jan 2009 12:00:55 -0800 (PST) In-Reply-To: <49777A7E.30904@sailorfej.net> References: <49777A7E.30904@sailorfej.net> Date: Wed, 21 Jan 2009 15:00:55 -0500 Message-ID: <1de79840901211200o7cd53ba8xfc23a7ab8c4ea6e5@mail.gmail.com> From: Michael Proto To: Jeffrey Williams Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 7, runaway clock as guest OS on Microsoft Virtual Server X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Jan 2009 20:28:45 -0000 On Wed, Jan 21, 2009 at 2:41 PM, Jeffrey Williams wrote: > Hi Folks, > > I am trying to run FreeBSD 7 on Microsoft Virtual Server 2005 R2, Windows > Server 2003, on a Dell 2950. > > I am having a problem with the system clock running excessively fast, I > initially tried installing 7.1 release but received a nearly continuous > stream of the "calcru: runtime went backward errors", I tried rolling back > to 7.0, and it improved somewhat, but I still received regular "calcru" > errors, and it the system clock was running to fast for ntpd to keep up with > it, I set sysctl kern.timecounter.hardware to i8254 (it tries to default to > ACPI-safe), which helped more, ntpd is now able to keep pace with it, but > only barely, and I haven't seen any "calcru" errors yet. > > From the boot time dmesg, on the CPU line, the frequency reported with in > the parenthesizes varies on almost every reboot. > > Are there any other adjustments I can make to get this under control? > > Following are samples of sysctl values, dmesg, and a short log sample to > show the time and time reset rates. > > ******** sysctl grep clockrate: > > kern.clockrate: { hz = 1000, tick = 1000, profhz = 1024, stathz = 128 } > hw.clockrate: 1061 > > ******** sysctl grep timecounter: > > kern.timecounter.tick: 1 > kern.timecounter.choice: TSC(800) ACPI-safe(850) i8254(0) dummy(-1000000) > kern.timecounter.hardware: i8254 > kern.timecounter.nsetclock: 12 > kern.timecounter.ngetmicrotime: 8071302 > kern.timecounter.ngetnanotime: 9 > kern.timecounter.ngetbintime: 0 > kern.timecounter.ngetmicrouptime: 2310540 > kern.timecounter.ngetnanouptime: 3870 > kern.timecounter.ngetbinuptime: 237939 > kern.timecounter.nmicrotime: 48722 > kern.timecounter.nnanotime: 2143 > kern.timecounter.nbintime: 50865 > kern.timecounter.nmicrouptime: 4498 > kern.timecounter.nnanouptime: 1 > kern.timecounter.nbinuptime: 477504 > kern.timecounter.stepwarnings: 0 > kern.timecounter.tc.i8254.mask: 4294967295 > kern.timecounter.tc.i8254.counter: 3077011530 > kern.timecounter.tc.i8254.frequency: 1193182 > kern.timecounter.tc.i8254.quality: 0 > kern.timecounter.tc.ACPI-safe.mask: 16777215 > kern.timecounter.tc.ACPI-safe.counter: 14993826 > kern.timecounter.tc.ACPI-safe.frequency: 3579545 > kern.timecounter.tc.ACPI-safe.quality: 850 > kern.timecounter.tc.TSC.mask: 4294967295 > kern.timecounter.tc.TSC.counter: 3664196446 > kern.timecounter.tc.TSC.frequency: 1061252458 > kern.timecounter.tc.TSC.quality: 800 > kern.timecounter.smp_tsc: 0 > > ********** sample log: > > Jan 20 19:25:08 host ntpd[1829]: time reset -12.179675 s > Jan 20 19:25:08 host ntpd[1829]: kernel time sync disabled 6041 > Jan 20 21:25:34 host ntpd[1829]: time reset -17.665523 s > Jan 20 21:25:34 host ntpd[1829]: kernel time sync enabled 2001 > Jan 20 23:43:24 host ntpd[1829]: kernel time sync enabled 6001 > Jan 20 23:59:15 host ntpd[1829]: time reset -67.677336 s > Jan 20 23:59:15 host ntpd[1829]: kernel time sync enabled 2001 > Jan 21 00:51:31 host ntpd[1829]: kernel time sync enabled 6001 > Jan 21 00:51:27 host ntpd[1829]: time reset -11.695334 s > Jan 21 00:51:27 host ntpd[1829]: kernel time sync enabled 2001 > > ********** dmesg.boot: > > Copyright (c) 1992-2008 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 7.0-RELEASE-p9 #0: Tue Jan 13 19:45:51 PST 2009 > root@host:/usr/obj/usr/src/sys/GENERIC > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Xeon(R) CPU E5320 @ 1.86GHz (1364.45-MHz 686-class > CPU) > Origin = "GenuineIntel" Id = 0x6fb Stepping = 11 > Features=0x7c0a97b > AMD Features2=0x1 > Cores per package: 4 > real memory = 536805376 (511 MB) > avail memory = 511385600 (487 MB) > kbd1 at kbdmux0 > ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) > hptrr: HPT RocketRAID controller driver v1.1 (Jan 13 2009 19:45:26) > acpi0: on motherboard > acpi0: [ITHREAD] > acpi0: Power Button (fixed) > acpi0: reservation of 0, a0000 (3) failed > acpi0: reservation of 100000, 1ff00000 (3) failed > Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > isab0: at device 7.0 on pci0 > isa0: on isab0 > atapci0: port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 7.1 on pci0 > ata0: on atapci0 > ata0: [ITHREAD] > ata1: on atapci0 > ata1: [ITHREAD] > pci0: at device 7.3 (no driver attached) > vgapci0: mem 0xf8000000-0xfbffffff at device 8.0 on > pci0 > de0: port 0xec00-0xec7f mem > 0xfebff000-0xfebfffff irq 11 at device 10.0 on pci0 > de0: 21140A [10-100Mb/s] pass 2.0 > de0: using obsoleted if_watchdog interface > de0: Ethernet address: 00:03:ff:48:a7:20 > de0: [ITHREAD] > 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 > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on > acpi0 > sio0: type 16550A > sio0: [FILTER] > sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 > sio1: type 16550A > sio1: [FILTER] > fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on > acpi0 > fdc0: does not respond > device_attach: fdc0 attach returned 6 > fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on > acpi0 > fdc0: does not respond > device_attach: fdc0 attach returned 6 > pmtimer0 on isa0 > orm0: at iomem 0xc0000-0xcbfff,0xcc000-0xcc7ff pnpid > ORM0000 on isa0 > ppc0: at port 0x378-0x37f irq 7 on isa0 > ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode > ppbus0: on ppc0 > ppbus0: [ITHREAD] > plip0: on ppbus0 > lpt0: on ppbus0 > lpt0: Interrupt-driven port > ppi0: on ppbus0 > ppc0: [GIANT-LOCKED] > ppc0: [ITHREAD] > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > Timecounter "TSC" frequency 1364446545 Hz quality 800 > Timecounters tick every 1.000 msec > hptrr: no controller detected. > ad0: 81918MB at ata0-master WDMA2 > acd0: DVDROM at ata1-master PIO4 > Trying to mount root from ufs:/dev/ad0s1a > > _______________________________________________ > 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 use VMware, not VirtualServer, but you might want to set kern.hz in your loader.conf to something less than 1000. I use the following: kern.hz="100" That, combined with vmware-tools' option to sync the VM clock to the host works very well for me. -Proto From owner-freebsd-stable@FreeBSD.ORG Wed Jan 21 20:30: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 6C0301065C36 for ; Wed, 21 Jan 2009 20:30:41 +0000 (UTC) (envelope-from jeff@sailorfej.net) Received: from mail.sailorfej.net (mail.sailorfej.net [66.93.72.123]) by mx1.freebsd.org (Postfix) with ESMTP id 31BB88FC3D for ; Wed, 21 Jan 2009 20:30:40 +0000 (UTC) (envelope-from jeff@sailorfej.net) Received: from [10.3.3.117] (65-122-120-98.dia.static.qwest.net [65.122.120.98]) (authenticated bits=0) by mail.sailorfej.net (8.13.8/8.13.8) with ESMTP id n0LKUVlE095869 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 21 Jan 2009 12:30:33 -0800 (PST) (envelope-from jeff@sailorfej.net) Message-ID: <497785E2.5040007@sailorfej.net> Date: Wed, 21 Jan 2009 12:30:26 -0800 From: Jeffrey Williams User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Maxim Khitrov , dimitry@andric.com, mike@jellydonut.org References: <49777A7E.30904@sailorfej.net> <26ddd1750901211209k83250d7re8bb82dc2965ccd0@mail.gmail.com> In-Reply-To: <26ddd1750901211209k83250d7re8bb82dc2965ccd0@mail.gmail.com> X-Spam-Status: No, score=-0.8 required=6.0 tests=BAYES_00,HTML_30_40, HTML_MESSAGE,SPF_SOFTFAIL autolearn=no version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on mail.sailorfej.net Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 7, runaway clock as guest OS on Microsoft Virtual Server X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Jan 2009 20:30:42 -0000 Hi Guys, Thanks for kern.hz suggestion, but according loader.conf in the /boot/defaults directory, kern.hz is already set to 100, is this overridden somewhere else? Thanks, Jeff Maxim Khitrov wrote: > On Wed, Jan 21, 2009 at 2:41 PM, Jeffrey Williams wrote: > >> Hi Folks, >> >> I am trying to run FreeBSD 7 on Microsoft Virtual Server 2005 R2, Windows >> Server 2003, on a Dell 2950. >> >> I am having a problem with the system clock running excessively fast, I >> initially tried installing 7.1 release but received a nearly continuous >> stream of the "calcru: runtime went backward errors", I tried rolling back >> to 7.0, and it improved somewhat, but I still received regular "calcru" >> errors, and it the system clock was running to fast for ntpd to keep up with >> it, I set sysctl kern.timecounter.hardware to i8254 (it tries to default to >> ACPI-safe), which helped more, ntpd is now able to keep pace with it, but >> only barely, and I haven't seen any "calcru" errors yet. >> >> From the boot time dmesg, on the CPU line, the frequency reported with in >> the parenthesizes varies on almost every reboot. >> >> Are there any other adjustments I can make to get this under control? >> > > Have you tried reducing the value of kern.hz (kern.hz="100" in > /boot/loader.conf)? That fixes some clock-related problems on VMWare > Server. > > - Max > _______________________________________________ > 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 21 20:33: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 D4F9A1065864 for ; Wed, 21 Jan 2009 20:33:48 +0000 (UTC) (envelope-from peter@simons-rock.edu) Received: from hedwig.simons-rock.edu (hedwig.simons-rock.edu [208.81.88.14]) by mx1.freebsd.org (Postfix) with ESMTP id AB5648FC1A for ; Wed, 21 Jan 2009 20:33:48 +0000 (UTC) (envelope-from peter@simons-rock.edu) Received: from cesium.hyperfine.info (c2.8d.5646.static.theplanet.com [70.86.141.194]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by hedwig.simons-rock.edu (Postfix) with ESMTP id 9E00E2BB35A; Wed, 21 Jan 2009 15:33:47 -0500 (EST) Date: Wed, 21 Jan 2009 15:33:46 -0500 From: "Peter C. Lai" To: Dimitry Andric Message-ID: <20090121203345.GA58991@cesium.hyperfine.info> References: <49777A7E.30904@sailorfej.net> <49778128.1080104@andric.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49778128.1080104@andric.com> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: Jeffrey Williams , freebsd-stable@freebsd.org Subject: Re: FreeBSD 7, runaway clock as guest OS on Microsoft Virtual Server X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Jan 2009 20:33:50 -0000 On 2009-01-21 09:10:16PM +0100, Dimitry Andric wrote: > However, I am not sure what is at fault here, VMware or FreeBSD... I'd > guess the latter, since neither Linux nor Windows guest OSes seem to > have any such timing problems. Actually I have encountered such problems in mixed-bit environments (64bit VMware hosting 32bit Ubuntu or vice versa). -- =========================================================== Peter C. Lai | Bard College at Simon's Rock Systems Administrator | 84 Alford Rd. Information Technology Svcs. | Gt. Barrington, MA 01230 USA peter AT simons-rock.edu | (413) 528-7428 =========================================================== From owner-freebsd-stable@FreeBSD.ORG Wed Jan 21 20:35:12 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 3896110659C7; Wed, 21 Jan 2009 20:35:12 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from amailer.gwdg.de (amailer.gwdg.de [134.76.10.18]) by mx1.freebsd.org (Postfix) with ESMTP id BA8478FC21; Wed, 21 Jan 2009 20:35:11 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from p578b68b8.dip0.t-ipconnect.de ([87.139.104.184] helo=krabat.raven.hur) by mailer.gwdg.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1LPiy9-000599-PM; Wed, 21 Jan 2009 20:42:34 +0100 Message-ID: <49777AA3.5070202@gwdg.de> Date: Wed, 21 Jan 2009 20:42:27 +0100 From: Rainer Hurling User-Agent: Thunderbird 2.0.0.19 (X11/20090113) MIME-Version: 1.0 To: Gary Palmer References: <4975ADF4.1070103@paradise.net.nz> <20090121140307.GE81380@in-addr.com> In-Reply-To: <20090121140307.GE81380@in-addr.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated: Id:rhurlin X-Spam-Level: - X-Virus-Scanned: (clean) by exiscan+sophie Cc: Reuben , John Rushford , FreeBSD-stable@freebsd.org, Mark Kirkwood Subject: Re: Broken loader on 7.1-STABLE? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jan 2009 20:35:13 -0000 I have this issue only with amd64, not with i386. Both on the same hardware with up to date 8.0-CURRENT. In the not booting (amd64) version the following both lines, which indicate the detection of disks, are absent: ad4: 381554MB at ata2-master SATA300 ad6: 476940MB at ata3-master SATA300. I think the boot loader is ok, because I can load old amd64 kernel structures (before Oct. 9th 2008), but no newer one on this hardware. I have no clue what could be reason. Perhaps you are right with your suspicion about a kernel config problem? Please let me know if I can help. Thank you, Rainer On 21.01.2009 15:03 (UTC+1), Gary Palmer wrote: > On Tue, Jan 20, 2009 at 06:22:00PM -0700, John Rushford wrote: >> Hello, >> >> Perhaps mine is a different issue but I ran into this today. >> >> I loaded FreeBSD 7.1-RELEASE from a DVD onto an Apple Mac Pro after >> partitioning a drive with bootcamp. The install went quite well and the >> machine came up with no issues. I configured networking, X, and got gnome >> working. I setup cvsup and loaded the STABLE sources, ran make buildworld, >> make kernel, etc... >> >> I attempted to boot into single user to run mergemaster, installworld, etc.. >> But the machine will not boot, I now get the following errror and prompt: >> >> Trying to mount root from ufs:/dev/ad9s1a >> >> Manual root filesystem specification: >> : Mount using filesystem >> e.g. ufs:da0s1a >> ? List valid disk boot devices >> Abort manual input >> >> I input ufs:/dev/ad9s1a to no avail and ? Does not list any other devices. >> >> I've booted from the DVD and gone into Fixit mode and can mount /dev/ad9s1a >> just fine. I thought that I'd try putting back loader.old on the off chance >> that might solve the problem but, I do not see a loader.old, just loader. >> The kernel.old directory is there. >> >> Any ideas on what the issue might be and how to fix? >> >> Appreciate the help as I'd like to get 7.1-STABLE running on this machine. > > Did the kernel probe messages prior to the mountroot prompt indicate that > the appropriate disk controllers were found/probed and that the > disk devices were found on the disk controllers? The lack of > any devices listed when you asked might indicate a kernel configuration > problem. > > Regards, > > Gary > > P.S. Please do not top post. > >> Regards >> John >> >> >> >> >> On 1/20/09 3:56 AM, "Mark Kirkwood" wrote: >> >>> Reuben wrote: >>>> I was wondering if anyone else was seeing loader (v1.02) break after updating >>>> from 7.1-RELEASE to 7.1-STABLE. After performing the prescribed updating >>>> procedure (via the handbook), the system will go through the normal steps and >>>> after the boot menu will present the following error: >>>> >>>> Can't work out which disk we are booting from. >>>> Guessed BIOS device 0xffffffff not found by probes, defaulting to disk0 >>>> >>>> According to the bugbusting page on the FreeBSD wiki there's two issues at >>>> work that cause this behavior; patches were committed to HEAD/RELENG earlier >>>> last year in Mar and Aug. Up until now I've never come across this problem >>>> in 6.x or 7.0. In doing a little research I've come across a few older >>>> threads via google where it was believed that the problem was caused by >>>> improper CFLAGS in make.conf. I've commented mine out and rebuilt things.. >>>> with the same end result. In fact, if it's any help, my CFLAGS declaration >>>> in make.conf is taken verbatim from the /usr/share/examples/etc/make.conf. >>>> Furthermore, on selecting option 6 from the boot menu (escape to loader >>>> prompt), the system [I'm assuming] crashes displaying a blinking ASCII >>>> pattern from which only a hard reboot will work. >>>> >>>> FWIW, this is a fairly plain system.. nothing special in sysctl.conf or >>>> loader.conf, and the kernel is pretty stock as well (more or less GENERIC >>>> with my sound device and pf). >>>> >>>> A temporary fix for me was to copy over loader.old to loader in /boot. >>>> >>>> >>>> >>> I am getting this too - update from RELENG_7 @12 Jan src to 20 Jan and I >>> have: >>> >>> panic: free: guard1 fail @ 0x511d >>> from /usr/src/sys/boot/i386/loader/../../common/module.c:959 >>> >>> Can't work out which disk we are booting from. >>> Guessed BIOS device 0xffffffff not found by probes, defaulting to disk0 >>> >>> >>> >>> Copying loader.old to loader did not work around this for me - I had to >>> empty loader.conf too. >>> >>> Here is what *was* in there: >>> >>> ---> begin loader.conf >>> # Sound >>> sound_load="YES" >>> snd_hda_load="YES" >>> >>> # IPC >>> kern.ipc.semmni=500 >>> kern.ipc.semmns=500 >>> >>> >>> # CD/DVD DMA >>> atapicam_load="YES" >>> hw.ata.atapi_dma=0 >>> --> end loader.conf >>> >>> >>> At this point I am not sure which if are the bad guys... >>> >>> >>> The machine is an Asus a8vx. >>> >>> regards >>> >>> Mark From owner-freebsd-stable@FreeBSD.ORG Wed Jan 21 20:36: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 63DDC1065D31 for ; Wed, 21 Jan 2009 20:36:59 +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 225618FC1E for ; Wed, 21 Jan 2009 20:36:59 +0000 (UTC) (envelope-from thompsa@FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by pele.citylink.co.nz (Postfix) with ESMTP id 6C01AFEF2; Thu, 22 Jan 2009 09:36:58 +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 JM-7Qk2aTSkq; Thu, 22 Jan 2009 09:36:54 +1300 (NZDT) Received: from citylink.fud.org.nz (unknown [202.8.44.45]) by pele.citylink.co.nz (Postfix) with ESMTP; Thu, 22 Jan 2009 09:36:54 +1300 (NZDT) Received: by citylink.fud.org.nz (Postfix, from userid 1001) id 598261142D; Thu, 22 Jan 2009 09:36:54 +1300 (NZDT) Date: Wed, 21 Jan 2009 12:36:54 -0800 From: Andrew Thompson To: Jeffrey Williams Message-ID: <20090121203654.GB84399@citylink.fud.org.nz> References: <49777A7E.30904@sailorfej.net> <26ddd1750901211209k83250d7re8bb82dc2965ccd0@mail.gmail.com> <497785E2.5040007@sailorfej.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <497785E2.5040007@sailorfej.net> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: Maxim Khitrov , dimitry@andric.com, freebsd-stable@freebsd.org, mike@jellydonut.org Subject: Re: FreeBSD 7, runaway clock as guest OS on Microsoft Virtual Server X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Jan 2009 20:37:02 -0000 On Wed, Jan 21, 2009 at 12:30:26PM -0800, Jeffrey Williams wrote: > Hi Guys, > > Thanks for kern.hz suggestion, but according loader.conf in the > /boot/defaults directory, kern.hz is already set to 100, is this overridden > somewhere else? > Thats a bit misleading, the commented out value isnt actually the default. Set it in the loader.conf, can verify this with 'sysctl kern.hz' Andrew From owner-freebsd-stable@FreeBSD.ORG Wed Jan 21 20:37: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 49C701065A2C for ; Wed, 21 Jan 2009 20:37:52 +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 059C18FC0A for ; Wed, 21 Jan 2009 20:37:52 +0000 (UTC) (envelope-from dimitry@andric.com) Received: from [IPv6:2001:7b8:3a7:0:1416:e549:1db8:acb8] (unknown [IPv6:2001:7b8:3a7:0:1416:e549:1db8:acb8]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 945C311F838; Wed, 21 Jan 2009 21:37:50 +0100 (CET) Message-ID: <497787A1.2050607@andric.com> Date: Wed, 21 Jan 2009 21:37:53 +0100 From: Dimitry Andric 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: Jeffrey Williams References: <49777A7E.30904@sailorfej.net> <26ddd1750901211209k83250d7re8bb82dc2965ccd0@mail.gmail.com> <497785E2.5040007@sailorfej.net> In-Reply-To: <497785E2.5040007@sailorfej.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Maxim Khitrov , freebsd-stable@freebsd.org, mike@jellydonut.org Subject: Re: FreeBSD 7, runaway clock as guest OS on Microsoft Virtual Server X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Jan 2009 20:37:53 -0000 On 2009-01-21 21:30, Jeffrey Williams wrote: > Thanks for kern.hz suggestion, but according loader.conf in the > /boot/defaults directory, kern.hz is already set to 100, is this > overridden somewhere else? Look closer, it is commented out in /boot/defaults/loader.conf. :) From owner-freebsd-stable@FreeBSD.ORG Wed Jan 21 20:39:35 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 E92661065923 for ; Wed, 21 Jan 2009 20:39:35 +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 A6A4B8FC0C for ; Wed, 21 Jan 2009 20:39:35 +0000 (UTC) (envelope-from thompsa@FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by pele.citylink.co.nz (Postfix) with ESMTP id 029A2FEF2; Thu, 22 Jan 2009 09:39:35 +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 9El6sPp0cP5l; Thu, 22 Jan 2009 09:39:31 +1300 (NZDT) Received: from citylink.fud.org.nz (unknown [202.8.44.45]) by pele.citylink.co.nz (Postfix) with ESMTP; Thu, 22 Jan 2009 09:39:31 +1300 (NZDT) Received: by citylink.fud.org.nz (Postfix, from userid 1001) id 86A131142B; Thu, 22 Jan 2009 09:39:31 +1300 (NZDT) Date: Wed, 21 Jan 2009 12:39:31 -0800 From: Andrew Thompson To: Luigi Rizzo Message-ID: <20090121203931.GA84448@citylink.fud.org.nz> References: <20090118222958.GA32414@onelab2.iet.unipi.it> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090118222958.GA32414@onelab2.iet.unipi.it> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: stable@freebsd.org, re@freebsd.org Subject: Re: RFC: side effects of fixing loader_conf_files handling X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Jan 2009 20:39:36 -0000 On Sun, Jan 18, 2009 at 11:29:58PM +0100, Luigi Rizzo wrote: > hi, > > Previously, the check for new assignments was incorrect, and it happened > to ignored assignments which did not result in a buffer reallocation > by the Forth interpreter (essentially, any string not longer > than the current one was ignored). > > An annoying side effect of the fix is that now people who (mistakenly) > copied /boot/defaults/loader.conf into /boot/loader.conf (and > possibly edit it), now create a loop because their /boot/loader.conf > now contains > > loader_conf_files="/boot/device.hints /boot/loader.conf /boot/loader.conf.local" > > which is not just a pure assignments. > > I think we should remove the use of loader_conf_files=... > from /boot/defaults/loader.conf, partly to prevent this kind > of bugs, and partly because it is nice to have only "pure assigments" > in this file. > > If there are no objections, i will look at how to do it. > Probably this requires putting the initial list of files > somewhere else, probably in /boot/loader.rc after the > > include /boot/loader.4th > > statement. > > Comments ? That sounds good, thanks for working on this. Andrew From owner-freebsd-stable@FreeBSD.ORG Wed Jan 21 20:49:36 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 8D1B11065712; Wed, 21 Jan 2009 20:49:36 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id 4A7318FC08; Wed, 21 Jan 2009 20:49:36 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.14.3/8.14.3) with ESMTP id n0LKnUNJ004117; Wed, 21 Jan 2009 15:49:31 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-legacy.sentex.ca (freebsd-legacy.sentex.ca [64.7.128.104]) by smtp2.sentex.ca (8.14.3/8.14.3) with ESMTP id n0LKnUUT094427; Wed, 21 Jan 2009 15:49:30 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-legacy.sentex.ca (Postfix, from userid 666) id C4437241BA; Wed, 21 Jan 2009 15:49:30 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20090121204930.C4437241BA@freebsd-legacy.sentex.ca> Date: Wed, 21 Jan 2009 15:49:30 -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 64.7.153.18 Cc: Subject: [releng_6 tinderbox] failure on amd64/amd64 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: Wed, 21 Jan 2009 20:49:38 -0000 TB --- 2009-01-21 19:22:12 - tinderbox 2.6 running on freebsd-legacy.sentex.ca TB --- 2009-01-21 19:22:12 - starting RELENG_6 tinderbox run for amd64/amd64 TB --- 2009-01-21 19:22:12 - cleaning the object tree TB --- 2009-01-21 19:23:08 - cvsupping the source tree TB --- 2009-01-21 19:23:08 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_6/amd64/amd64/supfile TB --- 2009-01-21 19:23:19 - building world TB --- 2009-01-21 19:23:19 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-21 19:23:19 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-21 19:23:19 - TARGET=amd64 TB --- 2009-01-21 19:23:19 - TARGET_ARCH=amd64 TB --- 2009-01-21 19:23:19 - TZ=UTC TB --- 2009-01-21 19:23:19 - __MAKE_CONF=/dev/null TB --- 2009-01-21 19:23:19 - cd /src TB --- 2009-01-21 19:23:19 - /usr/bin/make -B buildworld >>> 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 >>> stage 5.1: building 32 bit shim libraries TB --- 2009-01-21 20:41:11 - generating LINT kernel config TB --- 2009-01-21 20:41:11 - cd /src/sys/amd64/conf TB --- 2009-01-21 20:41:11 - /usr/bin/make -B LINT TB --- 2009-01-21 20:41:12 - building LINT kernel TB --- 2009-01-21 20:41:12 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-21 20:41:12 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-21 20:41:12 - TARGET=amd64 TB --- 2009-01-21 20:41:12 - TARGET_ARCH=amd64 TB --- 2009-01-21 20:41:12 - TZ=UTC TB --- 2009-01-21 20:41:12 - __MAKE_CONF=/dev/null TB --- 2009-01-21 20:41:12 - cd /src TB --- 2009-01-21 20:41:12 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Wed Jan 21 20:41:12 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 [...] cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -I/src/sys/dev/em -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 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/kern/vfs_lookup.c cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -I/src/sys/dev/em -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 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/kern/vfs_mount.c cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -I/src/sys/dev/em -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 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/kern/vfs_subr.c cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -I/src/sys/dev/em -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 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/kern/vfs_syscalls.c /src/sys/kern/vfs_syscalls.c: In function `kern_getdirentries': /src/sys/kern/vfs_syscalls.c:3715: error: `uap' undeclared (first use in this function) /src/sys/kern/vfs_syscalls.c:3715: error: (Each undeclared identifier is reported only once /src/sys/kern/vfs_syscalls.c:3715: error: for each function it appears in.) *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-01-21 20:49:30 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-01-21 20:49:30 - ERROR: failed to build lint kernel TB --- 2009-01-21 20:49:30 - 4108.22 user 534.38 system 5237.80 real http://tinderbox.des.no/tinderbox-releng_6-RELENG_6-amd64-amd64.full From owner-freebsd-stable@FreeBSD.ORG Wed Jan 21 21:12: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 74A721065672 for ; Wed, 21 Jan 2009 21:12:47 +0000 (UTC) (envelope-from prvs=12729c8c6e=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (core6.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id EB1848FC1E for ; Wed, 21 Jan 2009 21:12:46 +0000 (UTC) (envelope-from prvs=12729c8c6e=killing@multiplay.co.uk) DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=multiplay.co.uk; s=Multiplay; t=1232571225; x=1233176025; q=dns/txt; h=Received: Message-ID:From:To:Cc:References:Subject:Date:MIME-Version: Content-Type:Content-Transfer-Encoding; bh=LcrlykgARr8qOdmXsLnUy xfhjroy4wlMo/SADWsvMJs=; b=HnJ/lm87a/inA46nz2ES7WORZjpnvA+iorO7Q pgA9ggw7Vy27ZiJS38DCY5AnHROxKNLSE70bInreE8enDwiSIA+rjQB9lnOjSXuP XiLJ1duB9D+w7phQN0lPD4QVIZPcbLCklyJD6JwApLEi1Rxmbk9tiGrsId9t076t 95W4sc= X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on mail1.multiplay.co.uk X-Spam-Level: X-Spam-Status: No, score=-14.7 required=6.0 tests=BAYES_00, FORGED_MUA_OUTLOOK, USER_IN_WHITELIST,USER_IN_WHITELIST_TO autolearn=ham version=3.1.8 Received: from r2d2 by mail1.multiplay.co.uk (MDaemon PRO v9.6.6) with ESMTP id md50006861247.msg for ; Wed, 21 Jan 2009 20:53:44 +0000 X-Authenticated-Sender: Killing@multiplay.co.uk X-MDRemoteIP: 85.236.106.102 X-Return-Path: prvs=12729c8c6e=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-stable@freebsd.org Message-ID: <7EABD35A61E1435DB6519BF8F6259C0D@multiplay.co.uk> From: "Steven Hartland" To: "Michael Proto" , "Jeffrey Williams" References: <49777A7E.30904@sailorfej.net> <1de79840901211200o7cd53ba8xfc23a7ab8c4ea6e5@mail.gmail.com> Date: Wed, 21 Jan 2009 20:53:45 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5512 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 X-Spam-Processed: mail1.multiplay.co.uk, Wed, 21 Jan 2009 20:53:44 +0000 X-MDAV-Processed: mail1.multiplay.co.uk, Wed, 21 Jan 2009 20:53:45 +0000 Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 7, runaway clock as guest OS on Microsoft Virtual Server X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Jan 2009 21:12:48 -0000 Not read all the thread but if you haven't already just set the timer to TSC fixes things here. Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-stable@FreeBSD.ORG Wed Jan 21 21:28: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 B07921065676; Wed, 21 Jan 2009 21:28:08 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id 83F4E8FC17; Wed, 21 Jan 2009 21:28:08 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.14.3/8.14.3) with ESMTP id n0LLS5K3010052; Wed, 21 Jan 2009 16:28:05 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-legacy.sentex.ca (freebsd-legacy.sentex.ca [64.7.128.104]) by smtp2.sentex.ca (8.14.3/8.14.3) with ESMTP id n0LLS5EU078569; Wed, 21 Jan 2009 16:28:05 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-legacy.sentex.ca (Postfix, from userid 666) id 7C61D241BA; Wed, 21 Jan 2009 16:28:05 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20090121212805.7C61D241BA@freebsd-legacy.sentex.ca> Date: Wed, 21 Jan 2009 16:28:05 -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 64.7.153.18 Cc: Subject: [releng_6 tinderbox] failure on i386/pc98 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: Wed, 21 Jan 2009 21:28:09 -0000 TB --- 2009-01-21 20:27:11 - tinderbox 2.6 running on freebsd-legacy.sentex.ca TB --- 2009-01-21 20:27:11 - starting RELENG_6 tinderbox run for i386/pc98 TB --- 2009-01-21 20:27:12 - cleaning the object tree TB --- 2009-01-21 20:27:41 - cvsupping the source tree TB --- 2009-01-21 20:27:41 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_6/i386/pc98/supfile TB --- 2009-01-21 20:27:49 - building world TB --- 2009-01-21 20:27:49 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-21 20:27:49 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-21 20:27:49 - TARGET=pc98 TB --- 2009-01-21 20:27:49 - TARGET_ARCH=i386 TB --- 2009-01-21 20:27:49 - TZ=UTC TB --- 2009-01-21 20:27:49 - __MAKE_CONF=/dev/null TB --- 2009-01-21 20:27:49 - cd /src TB --- 2009-01-21 20:27:49 - /usr/bin/make -B buildworld >>> 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 TB --- 2009-01-21 21:20:58 - generating LINT kernel config TB --- 2009-01-21 21:20:58 - cd /src/sys/pc98/conf TB --- 2009-01-21 21:20:58 - /usr/bin/make -B LINT TB --- 2009-01-21 21:20:58 - building LINT kernel TB --- 2009-01-21 21:20:58 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-21 21:20:58 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-21 21:20:58 - TARGET=pc98 TB --- 2009-01-21 21:20:58 - TARGET_ARCH=i386 TB --- 2009-01-21 21:20:58 - TZ=UTC TB --- 2009-01-21 21:20:58 - __MAKE_CONF=/dev/null TB --- 2009-01-21 21:20:58 - cd /src TB --- 2009-01-21 21:20:58 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Wed Jan 21 21:20: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 [...] cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -I/src/sys/dev/em -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 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/kern/vfs_lookup.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -I/src/sys/dev/em -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 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/kern/vfs_mount.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -I/src/sys/dev/em -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 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/kern/vfs_subr.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -I/src/sys/dev/em -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 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/kern/vfs_syscalls.c /src/sys/kern/vfs_syscalls.c: In function `kern_getdirentries': /src/sys/kern/vfs_syscalls.c:3715: error: `uap' undeclared (first use in this function) /src/sys/kern/vfs_syscalls.c:3715: error: (Each undeclared identifier is reported only once /src/sys/kern/vfs_syscalls.c:3715: error: for each function it appears in.) *** Error code 1 Stop in /obj/pc98/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-01-21 21:28:05 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-01-21 21:28:05 - ERROR: failed to build lint kernel TB --- 2009-01-21 21:28:05 - 2875.12 user 372.34 system 3653.45 real http://tinderbox.des.no/tinderbox-releng_6-RELENG_6-i386-pc98.full From owner-freebsd-stable@FreeBSD.ORG Wed Jan 21 21:49:09 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 C182A106564A; Wed, 21 Jan 2009 21:49:09 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id 96F3A8FC1A; Wed, 21 Jan 2009 21:49:09 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.14.3/8.14.3) with ESMTP id n0LLn73W013367; Wed, 21 Jan 2009 16:49:07 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-legacy.sentex.ca (freebsd-legacy.sentex.ca [64.7.128.104]) by smtp2.sentex.ca (8.14.3/8.14.3) with ESMTP id n0LLn7Qc025241; Wed, 21 Jan 2009 16:49:07 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-legacy.sentex.ca (Postfix, from userid 666) id 28297241BA; Wed, 21 Jan 2009 16:49:07 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20090121214907.28297241BA@freebsd-legacy.sentex.ca> Date: Wed, 21 Jan 2009 16:49:07 -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 64.7.153.18 Cc: Subject: [releng_6 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: Wed, 21 Jan 2009 21:49:10 -0000 TB --- 2009-01-21 20:49:30 - tinderbox 2.6 running on freebsd-legacy.sentex.ca TB --- 2009-01-21 20:49:30 - starting RELENG_6 tinderbox run for sparc64/sparc64 TB --- 2009-01-21 20:49:30 - cleaning the object tree TB --- 2009-01-21 20:49:59 - cvsupping the source tree TB --- 2009-01-21 20:49:59 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_6/sparc64/sparc64/supfile TB --- 2009-01-21 20:50:08 - building world TB --- 2009-01-21 20:50:08 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-21 20:50:08 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-21 20:50:08 - TARGET=sparc64 TB --- 2009-01-21 20:50:08 - TARGET_ARCH=sparc64 TB --- 2009-01-21 20:50:08 - TZ=UTC TB --- 2009-01-21 20:50:08 - __MAKE_CONF=/dev/null TB --- 2009-01-21 20:50:08 - cd /src TB --- 2009-01-21 20:50:08 - /usr/bin/make -B buildworld >>> 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 TB --- 2009-01-21 21:42:30 - generating LINT kernel config TB --- 2009-01-21 21:42:30 - cd /src/sys/sparc64/conf TB --- 2009-01-21 21:42:30 - /usr/bin/make -B LINT TB --- 2009-01-21 21:42:30 - building LINT kernel TB --- 2009-01-21 21:42:30 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-21 21:42:30 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-21 21:42:30 - TARGET=sparc64 TB --- 2009-01-21 21:42:30 - TARGET_ARCH=sparc64 TB --- 2009-01-21 21:42:30 - TZ=UTC TB --- 2009-01-21 21:42:30 - __MAKE_CONF=/dev/null TB --- 2009-01-21 21:42:30 - cd /src TB --- 2009-01-21 21:42:30 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Wed Jan 21 21:42:30 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 [...] cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -I/src/sys/dev/em -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=medlow -msoft-float -ffreestanding -Werror /src/sys/kern/vfs_lookup.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -I/src/sys/dev/em -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=medlow -msoft-float -ffreestanding -Werror /src/sys/kern/vfs_mount.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -I/src/sys/dev/em -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=medlow -msoft-float -ffreestanding -Werror /src/sys/kern/vfs_subr.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -I/src/sys/dev/em -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=medlow -msoft-float -ffreestanding -Werror /src/sys/kern/vfs_syscalls.c /src/sys/kern/vfs_syscalls.c: In function `kern_getdirentries': /src/sys/kern/vfs_syscalls.c:3715: error: `uap' undeclared (first use in this function) /src/sys/kern/vfs_syscalls.c:3715: error: (Each undeclared identifier is reported only once /src/sys/kern/vfs_syscalls.c:3715: 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-21 21:49:07 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-01-21 21:49:07 - ERROR: failed to build lint kernel TB --- 2009-01-21 21:49:07 - 2922.20 user 335.97 system 3576.18 real http://tinderbox.des.no/tinderbox-releng_6-RELENG_6-sparc64-sparc64.full From owner-freebsd-stable@FreeBSD.ORG Wed Jan 21 22:23: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 BB0F71065672 for ; Wed, 21 Jan 2009 22:23:54 +0000 (UTC) (envelope-from jeff@sailorfej.net) Received: from mail.sailorfej.net (mail.sailorfej.net [66.93.72.123]) by mx1.freebsd.org (Postfix) with ESMTP id 81F278FC14 for ; Wed, 21 Jan 2009 22:23:54 +0000 (UTC) (envelope-from jeff@sailorfej.net) Received: from [10.3.3.117] (65-122-120-98.dia.static.qwest.net [65.122.120.98]) (authenticated bits=0) by mail.sailorfej.net (8.13.8/8.13.8) with ESMTP id n0LMNjqO097067 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 21 Jan 2009 14:23:46 -0800 (PST) (envelope-from jeff@sailorfej.net) Message-ID: <4977A06B.7060605@sailorfej.net> Date: Wed, 21 Jan 2009 14:23:39 -0800 From: Jeffrey Williams User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Andrew Thompson , dimitry@andric.com References: <49777A7E.30904@sailorfej.net> <26ddd1750901211209k83250d7re8bb82dc2965ccd0@mail.gmail.com> <497785E2.5040007@sailorfej.net> <20090121203654.GB84399@citylink.fud.org.nz> In-Reply-To: <20090121203654.GB84399@citylink.fud.org.nz> X-Spam-Status: No, score=-0.8 required=6.0 tests=BAYES_00,HTML_30_40, HTML_MESSAGE,SPF_SOFTFAIL autolearn=no version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on mail.sailorfej.net Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: killing@multiplay.co.uk, freebsd-stable@freebsd.org Subject: Re: FreeBSD 7, runaway clock as guest OS on Microsoft Virtual Server X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Jan 2009 22:23:55 -0000 Hi Guys, Ok it is set, it does seem a little better, the clocks are still running ahead by an average of about 30-40 seconds, but they seem to have slowed down enough for ntpd to maintain the time by slewing, instead of stepping. I did get a fresh batch of calcru errors from one of the servers right after reboot (possibly because I am setting kern.timecounter.hardware in sysctl.conf instead of loader.conf). I will let you know how it looks after it has run for an hour or two. I tried TSC instead of i8254 on a third server, it was better than ACPI-safe, but much worse than i8254. Thanks, Jeff Andrew Thompson wrote: > On Wed, Jan 21, 2009 at 12:30:26PM -0800, Jeffrey Williams wrote: > >> Hi Guys, >> >> Thanks for kern.hz suggestion, but according loader.conf in the >> /boot/defaults directory, kern.hz is already set to 100, is this overridden >> somewhere else? >> >> > > Thats a bit misleading, the commented out value isnt actually the > default. Set it in the loader.conf, can verify this with 'sysctl kern.hz' > > > Andrew > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > From owner-freebsd-stable@FreeBSD.ORG Thu Jan 22 01:23: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 9451A1065670 for ; Thu, 22 Jan 2009 01:23:32 +0000 (UTC) (envelope-from jjr@alisa.org) Received: from mail.alisa.org (mail.alisa.org [65.103.114.105]) by mx1.freebsd.org (Postfix) with ESMTP id 2E9ED8FC0C for ; Thu, 22 Jan 2009 01:23:31 +0000 (UTC) (envelope-from jjr@alisa.org) Received: from [192.168.1.102] (c-98-245-37-189.hsd1.co.comcast.net [98.245.37.189]) (authenticated bits=0) by mail.alisa.org (8.14.3/8.14.3) with ESMTP id n0M1NS7C061768; Wed, 21 Jan 2009 18:23:29 -0700 (MST) (envelope-from jjr@alisa.org) User-Agent: Microsoft-Entourage/11.4.0.080122 Date: Wed, 21 Jan 2009 18:23:26 -0700 From: John Rushford To: , Gary Palmer Message-ID: Thread-Topic: Broken loader on 7.1-STABLE? Thread-Index: Acl8MAYiRPzIVugjEd2BJgAX8gEdYA== In-Reply-To: <1f05a49079a04f3041197f13323105e5.squirrel@www.larush.com> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (mail.alisa.org [65.103.114.105]); Wed, 21 Jan 2009 18:23:31 -0700 (MST) Cc: Reuben , freebsd-stable@freebsd.org, Mark Kirkwood Subject: Re: Broken loader on 7.1-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: Thu, 22 Jan 2009 01:23:32 -0000 On 1/21/09 9:52 AM, "jjr@larush.com" wrote: >> On Tue, Jan 20, 2009 at 06:22:00PM -0700, John Rushford wrote: >>> Hello, >>> >>> Perhaps mine is a different issue but I ran into this today. >>> >>> I loaded FreeBSD 7.1-RELEASE from a DVD onto an Apple Mac Pro after >>> partitioning a drive with bootcamp. The install went quite well and the >>> machine came up with no issues. I configured networking, X, and got >>> gnome >>> working. I setup cvsup and loaded the STABLE sources, ran make >>> buildworld, >>> make kernel, etc... >>> >>> I attempted to boot into single user to run mergemaster, installworld, >>> etc.. >>> But the machine will not boot, I now get the following errror and >>> prompt: >>> >>> Trying to mount root from ufs:/dev/ad9s1a >>> >>> Manual root filesystem specification: >>> : Mount using filesystem >>> e.g. ufs:da0s1a >>> ? List valid disk boot devices >>> Abort manual input >>> >>> I input ufs:/dev/ad9s1a to no avail and ? Does not list any other >>> devices. >>> >>> I've booted from the DVD and gone into Fixit mode and can mount >>> /dev/ad9s1a >>> just fine. I thought that I'd try putting back loader.old on the off >>> chance >>> that might solve the problem but, I do not see a loader.old, just >>> loader. >>> The kernel.old directory is there. >>> >>> Any ideas on what the issue might be and how to fix? >>> >>> Appreciate the help as I'd like to get 7.1-STABLE running on this >>> machine. >> >> Did the kernel probe messages prior to the mountroot prompt indicate that >> the appropriate disk controllers were found/probed and that the >> disk devices were found on the disk controllers? The lack of >> any devices listed when you asked might indicate a kernel configuration >> problem. >> >> Regards, >> >> Gary >> >> P.S. Please do not top post. >> > > I believe the appropriate disk controllers were found, I had no trouble > mounting the root filesystem while in Fixit. I'll double check this > evening and let you know. I have gone back and booted without issue from > kernel.old and the machine is running 7.1-RELEASE. > > John Hmm, I have 3 disks in this Mac Pro with FreeBSD installed on the disk in Bay 3. When I boot the 7.1-RELEASE GENERIC kernel from the DVD install, these 3 disks are named ad8, ad9, and ad10. The FreeBSD resides on ad9s1a. I built 7.1-STABLE GENERIC kernel with no modifications except to comment out the debug option. When I boot this kernel, the disks are re-named as ad6, ad7, and ad8 and I'm dropped into this prompt: Manual root filesystem specification: : Mount using filesystem e.g. ufs:da0s1a ? List valid disk boot devices Abort manual input ? Lists no valid disks. Next I boot from DVD with the 7.1-RELEASE Kernel and the disks are named as before, I can mount /dev/ad9s1a and switch back to the 7.1-RELEASE kernel in /boot to get the machine back up. Any ideas? John From owner-freebsd-stable@FreeBSD.ORG Thu Jan 22 01:45: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 EBAF0106564A; Thu, 22 Jan 2009 01:45:07 +0000 (UTC) (envelope-from jjr@alisa.org) Received: from mail.alisa.org (mail.alisa.org [65.103.114.105]) by mx1.freebsd.org (Postfix) with ESMTP id 888678FC0C; Thu, 22 Jan 2009 01:45:07 +0000 (UTC) (envelope-from jjr@alisa.org) Received: from [192.168.1.102] (c-98-245-37-189.hsd1.co.comcast.net [98.245.37.189]) (authenticated bits=0) by mail.alisa.org (8.14.3/8.14.3) with ESMTP id n0M1j47Z061919; Wed, 21 Jan 2009 18:45:05 -0700 (MST) (envelope-from jjr@alisa.org) User-Agent: Microsoft-Entourage/11.4.0.080122 Date: Wed, 21 Jan 2009 18:45:02 -0700 From: John Rushford To: John Rushford , , Gary Palmer Message-ID: Thread-Topic: Broken loader on 7.1-STABLE? Thread-Index: Acl8MAYiRPzIVugjEd2BJgAX8gEdYAAAwR7x In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (mail.alisa.org [65.103.114.105]); Wed, 21 Jan 2009 18:45:06 -0700 (MST) Cc: freebsd-stable@freebsd.org, Reuben , Mark Kirkwood Subject: Re: Broken loader on 7.1-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: Thu, 22 Jan 2009 01:45:08 -0000 On 1/21/09 6:23 PM, "John Rushford" wrote: > > > > On 1/21/09 9:52 AM, "jjr@larush.com" wrote: > >>> On Tue, Jan 20, 2009 at 06:22:00PM -0700, John Rushford wrote: >>>> Hello, >>>> >>>> Perhaps mine is a different issue but I ran into this today. >>>> >>>> I loaded FreeBSD 7.1-RELEASE from a DVD onto an Apple Mac Pro after >>>> partitioning a drive with bootcamp. The install went quite well and the >>>> machine came up with no issues. I configured networking, X, and got >>>> gnome >>>> working. I setup cvsup and loaded the STABLE sources, ran make >>>> buildworld, >>>> make kernel, etc... >>>> >>>> I attempted to boot into single user to run mergemaster, installworld, >>>> etc.. >>>> But the machine will not boot, I now get the following errror and >>>> prompt: >>>> >>>> Trying to mount root from ufs:/dev/ad9s1a >>>> >>>> Manual root filesystem specification: >>>> : Mount using filesystem >>>> e.g. ufs:da0s1a >>>> ? List valid disk boot devices >>>> Abort manual input >>>> >>>> I input ufs:/dev/ad9s1a to no avail and ? Does not list any other >>>> devices. >>>> >>>> I've booted from the DVD and gone into Fixit mode and can mount >>>> /dev/ad9s1a >>>> just fine. I thought that I'd try putting back loader.old on the off >>>> chance >>>> that might solve the problem but, I do not see a loader.old, just >>>> loader. >>>> The kernel.old directory is there. >>>> >>>> Any ideas on what the issue might be and how to fix? >>>> >>>> Appreciate the help as I'd like to get 7.1-STABLE running on this >>>> machine. >>> >>> Did the kernel probe messages prior to the mountroot prompt indicate that >>> the appropriate disk controllers were found/probed and that the >>> disk devices were found on the disk controllers? The lack of >>> any devices listed when you asked might indicate a kernel configuration >>> problem. >>> >>> Regards, >>> >>> Gary >>> >>> P.S. Please do not top post. >>> >> >> I believe the appropriate disk controllers were found, I had no trouble >> mounting the root filesystem while in Fixit. I'll double check this >> evening and let you know. I have gone back and booted without issue from >> kernel.old and the machine is running 7.1-RELEASE. >> >> John > > Hmm, I have 3 disks in this Mac Pro with FreeBSD installed on the disk in > Bay 3. When I boot the 7.1-RELEASE GENERIC kernel from the DVD install, > these 3 disks are named ad8, ad9, and ad10. The FreeBSD resides on ad9s1a. > I built 7.1-STABLE GENERIC kernel with no modifications except to comment > out the debug option. When I boot this kernel, the disks are re-named as > ad6, ad7, and ad8 and I'm dropped into this prompt: > > Manual root filesystem specification: > > : Mount using filesystem > e.g. ufs:da0s1a > ? List valid disk boot devices > Abort manual input > > ? Lists no valid disks. > > Next I boot from DVD with the 7.1-RELEASE Kernel and the disks are named as > before, I can mount /dev/ad9s1a and switch back to the 7.1-RELEASE kernel in > /boot to get the machine back up. > > Any ideas? > > John > BTW, its a Mac Pro and an AMD64 kernel From owner-freebsd-stable@FreeBSD.ORG Thu Jan 22 05:45:06 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 51678106567F; Thu, 22 Jan 2009 05:45:06 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id CBAEC8FC19; Thu, 22 Jan 2009 05:45:05 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.14.3/8.14.3) with ESMTP id n0M5j3R9044604; Thu, 22 Jan 2009 00:45:03 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-stable.sentex.ca (freebsd-stable.sentex.ca [64.7.128.103]) by smtp2.sentex.ca (8.14.3/8.14.3) with ESMTP id n0M5j3Ir089500; Thu, 22 Jan 2009 00:45:03 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-stable.sentex.ca (Postfix, from userid 666) id 11F131B5060; Thu, 22 Jan 2009 00:45:03 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20090122054503.11F131B5060@freebsd-stable.sentex.ca> Date: Thu, 22 Jan 2009 00:45:02 -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 64.7.153.18 Cc: Subject: [releng_7 tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jan 2009 05:45:07 -0000 TB --- 2009-01-22 04:06:26 - tinderbox 2.6 running on freebsd-stable.sentex.ca TB --- 2009-01-22 04:06:26 - starting RELENG_7 tinderbox run for amd64/amd64 TB --- 2009-01-22 04:06:26 - cleaning the object tree TB --- 2009-01-22 04:06:46 - cvsupping the source tree TB --- 2009-01-22 04:06:46 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/amd64/amd64/supfile TB --- 2009-01-22 04:06:56 - building world TB --- 2009-01-22 04:06:56 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-22 04:06:56 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-22 04:06:56 - TARGET=amd64 TB --- 2009-01-22 04:06:56 - TARGET_ARCH=amd64 TB --- 2009-01-22 04:06:56 - TZ=UTC TB --- 2009-01-22 04:06:56 - __MAKE_CONF=/dev/null TB --- 2009-01-22 04:06:56 - cd /src TB --- 2009-01-22 04:06:56 - /usr/bin/make -B buildworld >>> World build started on Thu Jan 22 04:06:57 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 >>> stage 5.1: building 32 bit shim libraries >>> World build completed on Thu Jan 22 05:36:38 UTC 2009 TB --- 2009-01-22 05:36:38 - generating LINT kernel config TB --- 2009-01-22 05:36:38 - cd /src/sys/amd64/conf TB --- 2009-01-22 05:36:38 - /usr/bin/make -B LINT TB --- 2009-01-22 05:36:38 - building LINT kernel TB --- 2009-01-22 05:36:38 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-22 05:36:38 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-22 05:36:38 - TARGET=amd64 TB --- 2009-01-22 05:36:38 - TARGET_ARCH=amd64 TB --- 2009-01-22 05:36:38 - TZ=UTC TB --- 2009-01-22 05:36:38 - __MAKE_CONF=/dev/null TB --- 2009-01-22 05:36:38 - cd /src TB --- 2009-01-22 05:36:38 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Thu Jan 22 05:36:38 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 [...] cc -c -O2 -frename-registers -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=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/dev/usb/uhid.c cc -c -O2 -frename-registers -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=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/dev/usb/uhub.c cc -c -O2 -frename-registers -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=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/dev/usb/uipaq.c cc -c -O2 -frename-registers -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=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/dev/usb/ukbd.c cc -c -O2 -frename-registers -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=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/dev/usb/ulpt.c cc -c -O2 -frename-registers -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=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/dev/usb/umass.c /src/sys/dev/usb/umass.c:577: error: 'USB_PRODUCT_NETAC_ONLYDISK' undeclared here (not in a function) /src/sys/dev/usb/umass.c:613: error: 'USB_PRODUCT_ONSPEC_SDS_HOTFIND_D' undeclared here (not in a function) *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-01-22 05:45:02 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-01-22 05:45:02 - ERROR: failed to build lint kernel TB --- 2009-01-22 05:45:02 - 4882.45 user 554.26 system 5916.19 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-amd64-amd64.full From owner-freebsd-stable@FreeBSD.ORG Thu Jan 22 06:18:35 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 232F31065672; Thu, 22 Jan 2009 06:18:35 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id DF8DA8FC18; Thu, 22 Jan 2009 06:18:34 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1c.sentex.ca [64.7.153.10]) by smarthost1.sentex.ca (8.14.3/8.14.3) with ESMTP id n0M6IW60045947; Thu, 22 Jan 2009 01:18:32 -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 n0M6IWPi038256; Thu, 22 Jan 2009 01:18:32 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-stable.sentex.ca (Postfix, from userid 666) id 395441B5060; Thu, 22 Jan 2009 01:18:32 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20090122061832.395441B5060@freebsd-stable.sentex.ca> Date: Thu, 22 Jan 2009 01:18:32 -0500 (EST) X-Virus-Scanned: ClamAV version 0.94.2, clamav-milter version 0.94.2 on clamscanner1 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18 Cc: Subject: [releng_7 tinderbox] failure on i386/i386 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jan 2009 06:18:35 -0000 TB --- 2009-01-22 05:04:46 - tinderbox 2.6 running on freebsd-stable.sentex.ca TB --- 2009-01-22 05:04:46 - starting RELENG_7 tinderbox run for i386/i386 TB --- 2009-01-22 05:04:46 - cleaning the object tree TB --- 2009-01-22 05:05:15 - cvsupping the source tree TB --- 2009-01-22 05:05:15 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/i386/i386/supfile TB --- 2009-01-22 05:05:27 - building world TB --- 2009-01-22 05:05:27 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-22 05:05:27 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-22 05:05:27 - TARGET=i386 TB --- 2009-01-22 05:05:27 - TARGET_ARCH=i386 TB --- 2009-01-22 05:05:27 - TZ=UTC TB --- 2009-01-22 05:05:27 - __MAKE_CONF=/dev/null TB --- 2009-01-22 05:05:27 - cd /src TB --- 2009-01-22 05:05:27 - /usr/bin/make -B buildworld >>> World build started on Thu Jan 22 05:05:28 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 Thu Jan 22 06:09:01 UTC 2009 TB --- 2009-01-22 06:09:01 - generating LINT kernel config TB --- 2009-01-22 06:09:01 - cd /src/sys/i386/conf TB --- 2009-01-22 06:09:01 - /usr/bin/make -B LINT TB --- 2009-01-22 06:09:01 - building LINT kernel TB --- 2009-01-22 06:09:01 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-22 06:09:01 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-22 06:09:01 - TARGET=i386 TB --- 2009-01-22 06:09:01 - TARGET_ARCH=i386 TB --- 2009-01-22 06:09:01 - TZ=UTC TB --- 2009-01-22 06:09:01 - __MAKE_CONF=/dev/null TB --- 2009-01-22 06:09:01 - cd /src TB --- 2009-01-22 06:09:01 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Thu Jan 22 06:09:01 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 [...] 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=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/dev/usb/uhid.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=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/dev/usb/uhub.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=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/dev/usb/uipaq.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=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/dev/usb/ukbd.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=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/dev/usb/ulpt.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=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/dev/usb/umass.c /src/sys/dev/usb/umass.c:577: error: 'USB_PRODUCT_NETAC_ONLYDISK' undeclared here (not in a function) /src/sys/dev/usb/umass.c:613: error: 'USB_PRODUCT_ONSPEC_SDS_HOTFIND_D' undeclared here (not in a function) *** Error code 1 Stop in /obj/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-01-22 06:18:32 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-01-22 06:18:32 - ERROR: failed to build lint kernel TB --- 2009-01-22 06:18:32 - 3674.97 user 391.30 system 4425.80 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-i386-i386.full From owner-freebsd-stable@FreeBSD.ORG Thu Jan 22 06:32:04 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 629D11065680 for ; Thu, 22 Jan 2009 06:32:04 +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 F0D468FC13 for ; Thu, 22 Jan 2009 06:32:03 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 23823 invoked by uid 399); 22 Jan 2009 06:32:02 -0000 Received: from localhost (HELO ?192.168.0.19?) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 22 Jan 2009 06:32:02 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <497812FB.3050100@FreeBSD.org> Date: Wed, 21 Jan 2009 22:32:27 -0800 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Pete Carah References: <20090119215959.GA1185@port3.altadena.net> In-Reply-To: <20090119215959.GA1185@port3.altadena.net> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: kris@freebsd.org, 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: Thu, 22 Jan 2009 06:32:04 -0000 Pete Carah wrote: > I have done some (lots of) kernel debugging in the past. I have several > points: > > 1. I shouldn't *have* to kernel debug for a normal usage of an > official release. Um, why not? We certainly put every possible effort into making sure that releases (and in fact stable branches in general) do not regress, but it is inevitable that with the extraordinarily wide range of hardware and workloads that run FreeBSD there will be regressions. Mark has already commented on the need for wider community review of release candidates, so I won't go there. Helping the community understand and hopefully fix the problem when something goes pear-shaped for you is part of the "price" of free software. If you're unwilling (or unable, as you indicate below) to pay that price, you may just have to find another tool for the job. > 2. One of the soekris boxes is 2800 MILES away, in a remote location, That's what serial consoles and remote power switches are for. It's not our fault if you don't have access to those. > 3. I can't afford the time to debug my tools (freebsd is a tool, not an > experiment, for lots of people, including me...) I use this laptop at > work in a place where I am *not* working on freebsd. (nor am I even allowed > to at work...) Doug (who's still a volunteer, last time I checked) -- This .signature sanitized for your protection From owner-freebsd-stable@FreeBSD.ORG Thu Jan 22 06:56:11 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 B9502106566B; Thu, 22 Jan 2009 06:56:11 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id 37F038FC1A; Thu, 22 Jan 2009 06:56:10 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.14.3/8.14.3) with ESMTP id n0M6u8Bc047419; Thu, 22 Jan 2009 01:56:08 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-stable.sentex.ca (freebsd-stable.sentex.ca [64.7.128.103]) by smtp2.sentex.ca (8.14.3/8.14.3) with ESMTP id n0M6u8xC034754; Thu, 22 Jan 2009 01:56:08 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-stable.sentex.ca (Postfix, from userid 666) id 0F8791B5060; Thu, 22 Jan 2009 01:56:08 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20090122065608.0F8791B5060@freebsd-stable.sentex.ca> Date: Thu, 22 Jan 2009 01:56:07 -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 64.7.153.18 Cc: Subject: [releng_7 tinderbox] failure on i386/pc98 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jan 2009 06:56:12 -0000 TB --- 2009-01-22 05:45:03 - tinderbox 2.6 running on freebsd-stable.sentex.ca TB --- 2009-01-22 05:45:03 - starting RELENG_7 tinderbox run for i386/pc98 TB --- 2009-01-22 05:45:03 - cleaning the object tree TB --- 2009-01-22 05:45:27 - cvsupping the source tree TB --- 2009-01-22 05:45:27 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/i386/pc98/supfile TB --- 2009-01-22 05:45:37 - building world TB --- 2009-01-22 05:45:37 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-22 05:45:37 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-22 05:45:37 - TARGET=pc98 TB --- 2009-01-22 05:45:37 - TARGET_ARCH=i386 TB --- 2009-01-22 05:45:37 - TZ=UTC TB --- 2009-01-22 05:45:37 - __MAKE_CONF=/dev/null TB --- 2009-01-22 05:45:37 - cd /src TB --- 2009-01-22 05:45:37 - /usr/bin/make -B buildworld >>> World build started on Thu Jan 22 05:45:38 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 Thu Jan 22 06:49:00 UTC 2009 TB --- 2009-01-22 06:49:00 - generating LINT kernel config TB --- 2009-01-22 06:49:00 - cd /src/sys/pc98/conf TB --- 2009-01-22 06:49:00 - /usr/bin/make -B LINT TB --- 2009-01-22 06:49:00 - building LINT kernel TB --- 2009-01-22 06:49:00 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-22 06:49:00 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-22 06:49:00 - TARGET=pc98 TB --- 2009-01-22 06:49:00 - TARGET_ARCH=i386 TB --- 2009-01-22 06:49:00 - TZ=UTC TB --- 2009-01-22 06:49:00 - __MAKE_CONF=/dev/null TB --- 2009-01-22 06:49:00 - cd /src TB --- 2009-01-22 06:49:00 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Thu Jan 22 06:49:00 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 [...] 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=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -pg -mprofiler-epilogue /src/sys/dev/usb/uhid.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=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -pg -mprofiler-epilogue /src/sys/dev/usb/uhub.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=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -pg -mprofiler-epilogue /src/sys/dev/usb/uipaq.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=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -pg -mprofiler-epilogue /src/sys/dev/usb/ukbd.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=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -pg -mprofiler-epilogue /src/sys/dev/usb/ulpt.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=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -pg -mprofiler-epilogue /src/sys/dev/usb/umass.c /src/sys/dev/usb/umass.c:577: error: 'USB_PRODUCT_NETAC_ONLYDISK' undeclared here (not in a function) /src/sys/dev/usb/umass.c:613: error: 'USB_PRODUCT_ONSPEC_SDS_HOTFIND_D' undeclared here (not in a function) *** Error code 1 Stop in /obj/pc98/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-01-22 06:56:07 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-01-22 06:56:07 - ERROR: failed to build lint kernel TB --- 2009-01-22 06:56:07 - 3544.73 user 391.76 system 4264.73 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-i386-pc98.full From owner-freebsd-stable@FreeBSD.ORG Thu Jan 22 07:18: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 2A874106564A for ; Thu, 22 Jan 2009 07:18:48 +0000 (UTC) (envelope-from victor@bsdes.net) Received: from alf.bsdes.net (244.Red-217-126-240.staticIP.rima-tde.net [217.126.240.244]) by mx1.freebsd.org (Postfix) with ESMTP id CC38F8FC12 for ; Thu, 22 Jan 2009 07:18:47 +0000 (UTC) (envelope-from victor@bsdes.net) Received: by alf.bsdes.net (Postfix, from userid 1001) id D75EE11A2AE; Thu, 22 Jan 2009 08:18:45 +0100 (CET) Date: Thu, 22 Jan 2009 08:18:45 +0100 From: Victor Balada Diaz To: "Marat N.Afanasyev" Message-ID: <20090122071845.GF4881@alf.bsdes.net> References: <49774BAE.3000809@ksu.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <49774BAE.3000809@ksu.ru> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org, dan@langille.org, Pete French 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jan 2009 07:18:48 -0000 On Wed, Jan 21, 2009 at 07:22:06PM +0300, Marat N.Afanasyev 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! > > > >-pete. > > > > it's a kind of magic, really. I built a new kernel with KDB and DDB and > after 1 day, 13:15 I'm still waiting for storm to arrive. And I added > hw.acpi.osname="Linux" to /boot/loader.conf. Try doing lots of IO and you will get the problem soon. You might want to try: while true; do dd if=/dev/zero of=BAH bs=1M count=1024; sync; done Regards. -- La prueba más fehaciente de que existe vida inteligente en otros planetas, es que no han intentado contactar con nosotros. From owner-freebsd-stable@FreeBSD.ORG Thu Jan 22 07:40: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 7F0371065673 for ; Thu, 22 Jan 2009 07:40:55 +0000 (UTC) (envelope-from tonymaher@optusnet.com.au) Received: from mail07.syd.optusnet.com.au (mail07.syd.optusnet.com.au [211.29.132.188]) by mx1.freebsd.org (Postfix) with ESMTP id 1C9B98FC1F for ; Thu, 22 Jan 2009 07:40:54 +0000 (UTC) (envelope-from tonymaher@optusnet.com.au) Received: from karma.home (c58-107-102-243.thorn1.nsw.optusnet.com.au [58.107.102.243]) (authenticated sender tonymaher) by mail07.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id n0M7ekWB029078; Thu, 22 Jan 2009 18:40:47 +1100 Message-ID: <497822FE.6030805@optusnet.com.au> Date: Thu, 22 Jan 2009 18:40:46 +1100 From: Tony Maher User-Agent: Thunderbird 2.0.0.19 (X11/20090113) MIME-Version: 1.0 To: Andrei Kolu References: <4971B18D.3090803@optusnet.com.au> <20090121134047.3176a950@zelda.local> <49771B2F.7050902@bsd.ee> In-Reply-To: <49771B2F.7050902@bsd.ee> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org, Martin Subject: Re: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jan 2009 07:40:56 -0000 Andrei Kolu wrote: > Martin wrote: >> Am Sat, 17 Jan 2009 21:23:09 +1100 >> schrieb Tony Maher : >> >> >>> 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. >>> >> >> Hi, >> >> I've reported problems like this on -STABLE more than once already. >> Apparently it is a very uncommon problem for the developers. I have to >> say that all my new PCs and the new laptop has problems with USB >> keyboards and mice generally. The laptop (IBM Thinkpad T60p) has the >> most problems, -STABLE switches the USB devices off in intervals of >> about 2h. >> >> I have updated (flashed) my BIOS firmware on this mainboard here >> (Gigabyte GA-EP35C-DS3R rev 2.1) to the recent firmware F4a (it's a >> 6 month old beta release). >> >> >> The problem worsened now. I cannot get my USB mouse working until I >> reattach it physically. This is not a problem on other OSes, it seems. >> >> During device detection and initialization of uhci/ehci my USB-mouse >> is switched off and does not get power anymore. >> >> I get the same effect on -CURRENT as of yesterday. Mouse is Logitech >> G5, btw. >> >> I tried various USB settings in BIOS. USB mouse support on/off, USB >> legacy device support on/off. What else can I do? This is very annoying. >> >> (I wonder if it can be the source of many problems that people report >> here about umass devices.) >> >> > Hi, I have similar problem with Gigabyte GA-X48-DS4- I can't boot from > usb flash drive or usb floppy drive 9times of 10. My APC ups was > recognized only after OS is booted up and usb cable reinserted. Looks > like this is Gigabyte problem only- all other motherboards work without > any usb issues. Bios upgrade does not help. Changing any bios setting > does not help either. My problem is on an Intel based board. Just tried my USB based disk and it appears to work fine. It was just the old keyboard and mouse. Since replacing them there has been zero problems. Given the symptoms it appears it is a subtle timing bug and thus unfortunately very hard to debug. :-( You could try reverting to older versions to try an pinpoint which commit changed things. Very time consuming I know. sorry -- Tony Maher email: tonymaher@optusnet.com.au From owner-freebsd-stable@FreeBSD.ORG Thu Jan 22 07:53:36 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 13988106564A; Thu, 22 Jan 2009 07:53:36 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id C6C598FC1F; Thu, 22 Jan 2009 07:53:35 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.14.3/8.14.3) with ESMTP id n0M7rXfs049797; Thu, 22 Jan 2009 02:53:33 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-stable.sentex.ca (freebsd-stable.sentex.ca [64.7.128.103]) by smtp2.sentex.ca (8.14.3/8.14.3) with ESMTP id n0M7rXIQ048950; Thu, 22 Jan 2009 02:53:33 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-stable.sentex.ca (Postfix, from userid 666) id 6C7E11B5060; Thu, 22 Jan 2009 02:53:33 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20090122075333.6C7E11B5060@freebsd-stable.sentex.ca> Date: Thu, 22 Jan 2009 02:53:33 -0500 (EST) X-Virus-Scanned: ClamAV version 0.94.2, clamav-milter version 0.94.2 on clamscanner1 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18 Cc: Subject: [releng_7 tinderbox] failure on ia64/ia64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jan 2009 07:53:36 -0000 TB --- 2009-01-22 06:18:32 - tinderbox 2.6 running on freebsd-stable.sentex.ca TB --- 2009-01-22 06:18:32 - starting RELENG_7 tinderbox run for ia64/ia64 TB --- 2009-01-22 06:18:32 - cleaning the object tree TB --- 2009-01-22 06:18:50 - cvsupping the source tree TB --- 2009-01-22 06:18:50 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/ia64/ia64/supfile TB --- 2009-01-22 06:19:00 - building world TB --- 2009-01-22 06:19:00 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-22 06:19:00 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-22 06:19:00 - TARGET=ia64 TB --- 2009-01-22 06:19:00 - TARGET_ARCH=ia64 TB --- 2009-01-22 06:19:00 - TZ=UTC TB --- 2009-01-22 06:19:00 - __MAKE_CONF=/dev/null TB --- 2009-01-22 06:19:00 - cd /src TB --- 2009-01-22 06:19:00 - /usr/bin/make -B buildworld >>> World build started on Thu Jan 22 06:19:01 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 Thu Jan 22 07:44:03 UTC 2009 TB --- 2009-01-22 07:44:03 - generating LINT kernel config TB --- 2009-01-22 07:44:03 - cd /src/sys/ia64/conf TB --- 2009-01-22 07:44:03 - /usr/bin/make -B LINT TB --- 2009-01-22 07:44:03 - building LINT kernel TB --- 2009-01-22 07:44:03 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-22 07:44:03 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-22 07:44:03 - TARGET=ia64 TB --- 2009-01-22 07:44:03 - TARGET_ARCH=ia64 TB --- 2009-01-22 07:44:03 - TZ=UTC TB --- 2009-01-22 07:44:03 - __MAKE_CONF=/dev/null TB --- 2009-01-22 07:44:03 - cd /src TB --- 2009-01-22 07:44:03 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Thu Jan 22 07:44:04 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 [...] 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 -I/src/sys/contrib/ia64/libuwx/src -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 -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror /src/sys/dev/usb/uhid.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 -I/src/sys/contrib/ia64/libuwx/src -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 -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror /src/sys/dev/usb/uhub.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 -I/src/sys/contrib/ia64/libuwx/src -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 -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror /src/sys/dev/usb/uipaq.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 -I/src/sys/contrib/ia64/libuwx/src -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 -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror /src/sys/dev/usb/ukbd.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 -I/src/sys/contrib/ia64/libuwx/src -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 -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror /src/sys/dev/usb/ulpt.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 -I/src/sys/contrib/ia64/libuwx/src -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 -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror /src/sys/dev/usb/umass.c /src/sys/dev/usb/umass.c:577: error: 'USB_PRODUCT_NETAC_ONLYDISK' undeclared here (not in a function) /src/sys/dev/usb/umass.c:613: error: 'USB_PRODUCT_ONSPEC_SDS_HOTFIND_D' undeclared here (not in a function) *** Error code 1 Stop in /obj/ia64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-01-22 07:53:33 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-01-22 07:53:33 - ERROR: failed to build lint kernel TB --- 2009-01-22 07:53:33 - 4968.81 user 388.81 system 5700.93 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-ia64-ia64.full From owner-freebsd-stable@FreeBSD.ORG Thu Jan 22 08:10: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 B4975106567A; Thu, 22 Jan 2009 08:10:32 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id 89BBB8FC1F; Thu, 22 Jan 2009 08:10:32 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1c.sentex.ca [64.7.153.10]) by smarthost1.sentex.ca (8.14.3/8.14.3) with ESMTP id n0M8AT1S051276; Thu, 22 Jan 2009 03:10:29 -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 n0M8ATwR087793; Thu, 22 Jan 2009 03:10:29 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-stable.sentex.ca (Postfix, from userid 666) id 136331B5060; Thu, 22 Jan 2009 03:10:29 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20090122081029.136331B5060@freebsd-stable.sentex.ca> Date: Thu, 22 Jan 2009 03:10:29 -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 64.7.153.18 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: Thu, 22 Jan 2009 08:10:33 -0000 TB --- 2009-01-22 06:56:08 - tinderbox 2.6 running on freebsd-stable.sentex.ca TB --- 2009-01-22 06:56:08 - starting RELENG_7 tinderbox run for powerpc/powerpc TB --- 2009-01-22 06:56:08 - cleaning the object tree TB --- 2009-01-22 06:56:29 - cvsupping the source tree TB --- 2009-01-22 06:56:29 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/powerpc/powerpc/supfile TB --- 2009-01-22 06:56:40 - building world TB --- 2009-01-22 06:56:40 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-22 06:56:40 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-22 06:56:40 - TARGET=powerpc TB --- 2009-01-22 06:56:40 - TARGET_ARCH=powerpc TB --- 2009-01-22 06:56:40 - TZ=UTC TB --- 2009-01-22 06:56:40 - __MAKE_CONF=/dev/null TB --- 2009-01-22 06:56:40 - cd /src TB --- 2009-01-22 06:56:40 - /usr/bin/make -B buildworld >>> World build started on Thu Jan 22 06:56:41 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 Thu Jan 22 08:02:21 UTC 2009 TB --- 2009-01-22 08:02:21 - generating LINT kernel config TB --- 2009-01-22 08:02:21 - cd /src/sys/powerpc/conf TB --- 2009-01-22 08:02:21 - /usr/bin/make -B LINT TB --- 2009-01-22 08:02:21 - building LINT kernel TB --- 2009-01-22 08:02:21 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-22 08:02:21 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-22 08:02:21 - TARGET=powerpc TB --- 2009-01-22 08:02:21 - TARGET_ARCH=powerpc TB --- 2009-01-22 08:02:21 - TZ=UTC TB --- 2009-01-22 08:02:21 - __MAKE_CONF=/dev/null TB --- 2009-01-22 08:02:21 - cd /src TB --- 2009-01-22 08:02:21 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Thu Jan 22 08:02:21 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 [...] 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/usb/uhid.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/usb/uhub.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/usb/uipaq.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/usb/ukbd.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/usb/ulpt.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/usb/umass.c /src/sys/dev/usb/umass.c:577: error: 'USB_PRODUCT_NETAC_ONLYDISK' undeclared here (not in a function) /src/sys/dev/usb/umass.c:613: error: 'USB_PRODUCT_ONSPEC_SDS_HOTFIND_D' undeclared here (not in a function) *** 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-22 08:10:28 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-01-22 08:10:28 - ERROR: failed to build lint kernel TB --- 2009-01-22 08:10:28 - 3658.32 user 362.18 system 4460.30 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-powerpc-powerpc.full From owner-freebsd-stable@FreeBSD.ORG Thu Jan 22 09:02:51 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 261421065673; Thu, 22 Jan 2009 09:02:51 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id F01C88FC12; Thu, 22 Jan 2009 09:02:50 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.14.3/8.14.3) with ESMTP id n0M92m4c053357; Thu, 22 Jan 2009 04:02:48 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-stable.sentex.ca (freebsd-stable.sentex.ca [64.7.128.103]) by smtp2.sentex.ca (8.14.3/8.14.3) with ESMTP id n0M92mOq093074; Thu, 22 Jan 2009 04:02:48 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-stable.sentex.ca (Postfix, from userid 666) id 195761B5060; Thu, 22 Jan 2009 04:02:48 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20090122090248.195761B5060@freebsd-stable.sentex.ca> Date: Thu, 22 Jan 2009 04:02:48 -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 64.7.153.18 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: Thu, 22 Jan 2009 09:02:51 -0000 TB --- 2009-01-22 07:53:33 - tinderbox 2.6 running on freebsd-stable.sentex.ca TB --- 2009-01-22 07:53:33 - starting RELENG_7 tinderbox run for sparc64/sparc64 TB --- 2009-01-22 07:53:33 - cleaning the object tree TB --- 2009-01-22 07:53:52 - cvsupping the source tree TB --- 2009-01-22 07:53:52 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/sparc64/sparc64/supfile TB --- 2009-01-22 07:54:03 - building world TB --- 2009-01-22 07:54:03 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-22 07:54:03 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-22 07:54:03 - TARGET=sparc64 TB --- 2009-01-22 07:54:03 - TARGET_ARCH=sparc64 TB --- 2009-01-22 07:54:03 - TZ=UTC TB --- 2009-01-22 07:54:03 - __MAKE_CONF=/dev/null TB --- 2009-01-22 07:54:03 - cd /src TB --- 2009-01-22 07:54:03 - /usr/bin/make -B buildworld >>> World build started on Thu Jan 22 07:54:04 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 Thu Jan 22 08:56:18 UTC 2009 TB --- 2009-01-22 08:56:18 - generating LINT kernel config TB --- 2009-01-22 08:56:18 - cd /src/sys/sparc64/conf TB --- 2009-01-22 08:56:18 - /usr/bin/make -B LINT TB --- 2009-01-22 08:56:18 - building LINT kernel TB --- 2009-01-22 08:56:18 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-22 08:56:18 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-22 08:56:18 - TARGET=sparc64 TB --- 2009-01-22 08:56:18 - TARGET_ARCH=sparc64 TB --- 2009-01-22 08:56:18 - TZ=UTC TB --- 2009-01-22 08:56:18 - __MAKE_CONF=/dev/null TB --- 2009-01-22 08:56:18 - cd /src TB --- 2009-01-22 08:56:18 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Thu Jan 22 08:56:18 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 [...] 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/usb/uhid.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/usb/uhub.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/usb/uipaq.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/usb/ukbd.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/usb/ulpt.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/usb/umass.c /src/sys/dev/usb/umass.c:577: error: 'USB_PRODUCT_NETAC_ONLYDISK' undeclared here (not in a function) /src/sys/dev/usb/umass.c:613: error: 'USB_PRODUCT_ONSPEC_SDS_HOTFIND_D' undeclared here (not in a function) *** 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-22 09:02:48 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-01-22 09:02:48 - ERROR: failed to build lint kernel TB --- 2009-01-22 09:02:48 - 3458.30 user 357.01 system 4154.52 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-sparc64-sparc64.full From owner-freebsd-stable@FreeBSD.ORG Thu Jan 22 09:59: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 1C262106566B for ; Thu, 22 Jan 2009 09:59:44 +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 D19028FC1B for ; Thu, 22 Jan 2009 09:59:43 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mobileKamikaze.norad (vpn-cl-167-48.rz.uni-karlsruhe.de [141.3.167.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.bsdforen.de (Postfix) with ESMTP id D7BA18A000B for ; Thu, 22 Jan 2009 10:59:27 +0100 (CET) Message-ID: <49784370.6050107@bsdforen.de> Date: Thu, 22 Jan 2009 10:59:12 +0100 From: Dominic Fandrey User-Agent: Thunderbird 2.0.0.19 (X11/20090110) 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: mic is monitor, snd_hda X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jan 2009 09:59:44 -0000 With the new snd_hda that was recently MFCed, my microphone input is now accessible through a new input named monitor. The input mic only creates static noise. From owner-freebsd-stable@FreeBSD.ORG Thu Jan 22 16:39: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 6EFAA1065674 for ; Thu, 22 Jan 2009 16:39:53 +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 1C4F68FC22 for ; Thu, 22 Jan 2009 16:39:52 +0000 (UTC) (envelope-from dan@langille.org) Received: from localhost (localhost [127.0.0.1]) by nyi.unixathome.org (Postfix) with ESMTP id 9C565509D4; Thu, 22 Jan 2009 16:39:52 +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 AqxYGKiWn9M0; Thu, 22 Jan 2009 16:39:51 +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 3E270509AD ; Thu, 22 Jan 2009 16:39:51 +0000 (GMT) Message-ID: <4978A10A.9060006@langille.org> Date: Thu, 22 Jan 2009 11:38:34 -0500 From: Dan Langille Organization: The FreeBSD Diary User-Agent: Thunderbird 2.0.0.19 (X11/20090111) MIME-Version: 1.0 To: Victor Balada Diaz References: <49774BAE.3000809@ksu.ru> <20090122071845.GF4881@alf.bsdes.net> In-Reply-To: <20090122071845.GF4881@alf.bsdes.net> Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "Marat N.Afanasyev" , freebsd-stable@freebsd.org, Pete French 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jan 2009 16:39:53 -0000 Victor Balada Diaz wrote: > On Wed, Jan 21, 2009 at 07:22:06PM +0300, Marat N.Afanasyev 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! >>> >>> -pete. >>> >> it's a kind of magic, really. I built a new kernel with KDB and DDB and >> after 1 day, 13:15 I'm still waiting for storm to arrive. And I added >> hw.acpi.osname="Linux" to /boot/loader.conf. > > Try doing lots of IO and you will get the problem soon. You might > want to try: > > while true; do dd if=/dev/zero of=BAH bs=1M count=1024; sync; done FWIW, last night I changed the address of the comm port IO in my BIOS. Then I ran the Bacula regression test suite (lots of IO). For my machine, once the interrupt storm starts, it continues. I do not know if that happens to everyone. Since changing the address, I have had no interrupt storms. I have been running the above IO loop for about ten minutes. No storm yet (knock on wood). -- 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 22 18:15: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 3B2D210656BA for ; Thu, 22 Jan 2009 18:15:15 +0000 (UTC) (envelope-from wearabnet@yahoo.ca) Received: from n62.bullet.mail.sp1.yahoo.com (n62.bullet.mail.sp1.yahoo.com [98.136.44.35]) by mx1.freebsd.org (Postfix) with SMTP id 19FD38FC2B for ; Thu, 22 Jan 2009 18:15:15 +0000 (UTC) (envelope-from wearabnet@yahoo.ca) Received: from [69.147.84.144] by n62.bullet.mail.sp1.yahoo.com with NNFMP; 22 Jan 2009 18:02:00 -0000 Received: from [67.195.9.83] by t6.bullet.mail.sp1.yahoo.com with NNFMP; 22 Jan 2009 18:02:00 -0000 Received: from [67.195.9.105] by t3.bullet.mail.gq1.yahoo.com with NNFMP; 22 Jan 2009 18:02:00 -0000 Received: from [127.0.0.1] by omp109.mail.gq1.yahoo.com with NNFMP; 22 Jan 2009 18:02:00 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 195105.7466.bm@omp109.mail.gq1.yahoo.com Received: (qmail 42771 invoked by uid 60001); 22 Jan 2009 18:02:00 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.ca; h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:MIME-Version:Content-Type:Message-ID; b=05t1KkCtch9RqO2No+gKZ8+IXJgfSGUaVn37tvgFrzaAoJfjsC3K39bEdLdbDcEiNo7pLGaUCeT+P8w7b9Jog/WpdcdUY6EM9oFpJErdgssJmgON0087gWnAxLzlMJhzWaterTmiGeCf8sVRq3FZ3BhdVsUfjWy8lXmi+A//kho=; X-YMail-OSG: YkPzGLQVM1nTrCfsptsHCd7Z1P8EtShM1LBzNmvnT.glJFA5a.H_gmjo1KBFdWbIjL8UlxUBb042DIMo4n1BUOoZ5poflkOuxkc6.BzWnuSWDcLqavirRfRRb2gT8l_pUESgJZkwEEW1JVaCk2v0k8t6xdG0P0ySmzAt56e6pFAe6v5y_fFyF9W3g2pO Received: from [78.101.71.254] by web111310.mail.gq1.yahoo.com via HTTP; Thu, 22 Jan 2009 10:01:58 PST X-Mailer: YahooMailRC/1156.82 YahooMailWebService/0.7.260.1 Date: Thu, 22 Jan 2009 10:01:58 -0800 (PST) From: Abdullah Ibn Hamad Al-Marri To: FreeBSD STABLE MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <63135.16361.qm@web111310.mail.gq1.yahoo.com> Cc: FreeBSD Questions Subject: Is aio or vm broken for FreeBSD 7-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: Thu, 22 Jan 2009 18:15:15 -0000 Hello, This is fresh csup and buildworld after make cleandir and make cleanworld, then I built world. GENERIC KERNEL conf. ===> aio (all) cc -O2 -fno-strict-aliasing -pipe -D_KERNEL -DKLD_MODULE -std=c99 -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj/usr/src/sys/GENERIC/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -g -fno-omit-frame-pointer -I/usr/obj/usr/src/sys/GENERIC -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c /usr/src/sys/modules/aio/../../kern/vfs_aio.c cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -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 -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /usr/src/sys/vm/vm_unix.c /usr/src/sys/modules/aio/../../kern/vfs_aio.c:2548: error: field 'aio_sigevent' has incomplete type /usr/src/sys/modules/aio/../../kern/vfs_aio.c:2564: error: field 'aio_sigevent' has incomplete type /usr/src/sys/modules/aio/../../kern/vfs_aio.c: In function 'convert_old_sigevent32': /usr/src/sys/modules/aio/../../kern/vfs_aio.c:2575: error: dereferencing pointer to incomplete type /usr/src/sys/modules/aio/../../kern/vfs_aio.c:2580: error: dereferencing pointer to incomplete type /usr/src/sys/modules/aio/../../kern/vfs_aio.c:2584: error: dereferencing pointer to incomplete type /usr/src/sys/modules/aio/../../kern/vfs_aio.c:2585: error: dereferencing pointer to incomplete type /usr/src/sys/modules/aio/../../kern/vfs_aio.c: In function 'convert_sigevent32': /usr/src/sys/modules/aio/../../kern/vfs_aio.c:2621: error: dereferencing pointer to incomplete type /usr/src/sys/modules/aio/../../kern/vfs_aio.c:2626: error: dereferencing pointer to incomplete type /usr/src/sys/modules/aio/../../kern/vfs_aio.c:2629: error: dereferencing pointer to incomplete type /usr/src/sys/modules/aio/../../kern/vfs_aio.c:2632: error: dereferencing pointer to incomplete type /usr/src/sys/modules/aio/../../kern/vfs_aio.c:2633: error: dereferencing pointer to incomplete type /usr/src/sys/modules/aio/../../kern/vfs_aio.c: In function 'freebsd32_olio_listio': /usr/src/sys/modules/aio/../../kern/vfs_aio.c:2859: error: storage size of 'osig' isn't known /usr/src/sys/modules/aio/../../kern/vfs_aio.c:2859: warning: unused variable 'osig' /usr/src/sys/modules/aio/../../kern/vfs_aio.c: In function 'freebsd32_lio_listio': /usr/src/sys/modules/aio/../../kern/vfs_aio.c:2904: error: storage size of 'sig32' isn't known /usr/src/sys/modules/aio/../../kern/vfs_aio.c:2904: warning: unused variable 'sig32' *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -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 -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /usr/src/sys/vm/vm_zeroidle.c 1 error *** Error code 2 1 error *** Error code 2 1 error Regards, -Abdullah Ibn Hamad Al-Marri Arab Portal http://www.WeArab.Net/ From owner-freebsd-stable@FreeBSD.ORG Thu Jan 22 18:43: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 1B5A01065673 for ; Thu, 22 Jan 2009 18:43:45 +0000 (UTC) (envelope-from korvus@comcast.net) Received: from QMTA07.emeryville.ca.mail.comcast.net (qmta07.emeryville.ca.mail.comcast.net [76.96.30.64]) by mx1.freebsd.org (Postfix) with ESMTP id 033E28FC2B for ; Thu, 22 Jan 2009 18:43:44 +0000 (UTC) (envelope-from korvus@comcast.net) Received: from OMTA07.emeryville.ca.mail.comcast.net ([76.96.30.59]) by QMTA07.emeryville.ca.mail.comcast.net with comcast id 6gy91b00W1GXsucA7ijlmT; Thu, 22 Jan 2009 18:43:45 +0000 Received: from [192.168.2.164] ([206.210.89.202]) by OMTA07.emeryville.ca.mail.comcast.net with comcast id 6ija1b00J4Mx3R28TijdFY; Thu, 22 Jan 2009 18:43:43 +0000 Message-ID: <4978BE54.9060203@comcast.net> Date: Thu, 22 Jan 2009 13:43:32 -0500 From: Steve Polyack User-Agent: Thunderbird 2.0.0.19 (X11/20090105) MIME-Version: 1.0 To: freebsd-questions@FreeBSD.org, Mike Tancsa References: <4977950D.7090900@comcast.net> In-Reply-To: <4977950D.7090900@comcast.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: Sysinstall partition oddities (6.3/i386 -> 7.x/amd64) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jan 2009 18:43:45 -0000 Steve Polyack wrote: > I've seen some oddities with the partition and bsdlabel editors in the > sysinstall program on the 7.0 and 7.1 releases. The partition editor > seems to be reading or parsing the partition table incorrectly. I had > a 6.3-RELEASE system with the following layout: > /dev/amrd3s1a on / (ufs, local) > /dev/amrd3s1g on /opt (ufs, local, soft-updates) > /dev/amrd3s1f on /usr (ufs, local, soft-updates) > /dev/amrd3s1d on /var (ufs, local, soft-updates) > /dev/amrd3s1e on /var/log (ufs, local, soft-updates) > > Upon booting into the 7.x install media and encountering the FDISK > Partition Editor, the partition it's seeing is amrd3*a*s1, as opposed > to amrd3s1. Trying to continue with the partition table and bsd > labels as is only led to the installer bailing out. As soon as it > would attempt to newfs the disk partitions, the installer would error > and report that it can't find a device entry in /dev for amrd3*a*s1a. > Since preserving the data on the disk was not critical, I was able to > continue by deleting the original partition/slice and recreating > them. This worked fine. > > However, I'm still curious as to what the cause of this is. I have > seen this before on two other systems while installing 7.x, quite > possibly while upgrading from 6.3. When this occurred, I was also > moving from i386 to amd64; Is there some kind of offset for partition > tables which may change based on architecture? > > Lastly, here's a screenshot of the partition editor: > http://people.collaborativefusion.com/~spolyack/fbsd-install.jpg > > Unfortunately, I do not have any screenshots of the errors during the > newfs step. If this comes up again, I'll be sure to take some. Thanks. > This also occurs in VMWare. I'm able to get the exact same behavior by installing a 7.1-RELEASE system (single slice, da0s1), then booting off the install media and start a new installation. It picks up the partition as da0as1 instead of da0s1, making it impossible to use sysinstall while preserving existing partitions. -Steve Polyack From owner-freebsd-stable@FreeBSD.ORG Thu Jan 22 19:08: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 01C3B1065674; Thu, 22 Jan 2009 19:08:45 +0000 (UTC) (envelope-from jeff@sailorfej.net) Received: from mail.sailorfej.net (mail.sailorfej.net [66.93.72.123]) by mx1.freebsd.org (Postfix) with ESMTP id A7BFE8FC1C; Thu, 22 Jan 2009 19:08:44 +0000 (UTC) (envelope-from jeff@sailorfej.net) Received: from [10.3.3.117] (65-122-120-98.dia.static.qwest.net [65.122.120.98]) (authenticated bits=0) by mail.sailorfej.net (8.13.8/8.13.8) with ESMTP id n0MJ8Zsk008178 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 22 Jan 2009 11:08:36 -0800 (PST) (envelope-from jeff@sailorfej.net) Message-ID: <4978C42E.5050500@sailorfej.net> Date: Thu, 22 Jan 2009 11:08:30 -0800 From: Jeffrey Williams User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <49777A7E.30904@sailorfej.net> <26ddd1750901211209k83250d7re8bb82dc2965ccd0@mail.gmail.com> <497785E2.5040007@sailorfej.net> <20090121203654.GB84399@citylink.fud.org.nz> <4977A06B.7060605@sailorfej.net> In-Reply-To: <4977A06B.7060605@sailorfej.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.2 required=6.0 tests=BAYES_00,SPF_SOFTFAIL autolearn=no version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on mail.sailorfej.net Cc: mike@jellydonut.org, dimitry@andric.com, killing@multiplay.co.uk, Andrew Thompson Subject: Re: FreeBSD 7, runaway clock as guest OS on Microsoft Virtual Server X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jan 2009 19:08:45 -0000 Hi Guys, Well this helped sort of, the clocks are running only a little fast at this point (roughly seven minutes gained over 12 hours), but now for some reason, ntpd is not resetting the clocks at all, despite multiple good time sources, it was working fine before the kern.hz change. Any reason why that would break ntpd? Thanks, Jeff Jeffrey Williams wrote: > Hi Guys, > > Ok it is set, it does seem a little better, the clocks are still > running ahead by an average of about 30-40 seconds, but they seem to > have slowed down enough for ntpd to maintain the time by slewing, > instead of stepping. I did get a fresh batch of calcru errors from > one of the servers right after reboot (possibly because I am setting > kern.timecounter.hardware in sysctl.conf instead of loader.conf). I > will let you know how it looks after it has run for an hour or two. > > I tried TSC instead of i8254 on a third server, it was better than > ACPI-safe, but much worse than i8254. > > Thanks, > Jeff > > Andrew Thompson wrote: >> On Wed, Jan 21, 2009 at 12:30:26PM -0800, Jeffrey Williams wrote: >> >>> Hi Guys, >>> >>> Thanks for kern.hz suggestion, but according loader.conf in the >>> /boot/defaults directory, kern.hz is already set to 100, is this >>> overridden somewhere else? >>> >>> >> >> Thats a bit misleading, the commented out value isnt actually the >> default. Set it in the loader.conf, can verify this with 'sysctl >> kern.hz' >> >> >> Andrew >> _______________________________________________ >> 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 Thu Jan 22 19:41: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 E83F410657E4 for ; Thu, 22 Jan 2009 19:41:34 +0000 (UTC) (envelope-from opt1k2@mail.ru) Received: from mx45.mail.ru (mx45.mail.ru [194.67.23.236]) by mx1.freebsd.org (Postfix) with ESMTP id 9E4F58FC58 for ; Thu, 22 Jan 2009 19:41:34 +0000 (UTC) (envelope-from opt1k2@mail.ru) Received: from f136.mail.ru (f136.mail.ru [194.67.57.117]) by mx45.mail.ru (mPOP.Fallback_MX) with ESMTP id D3502E002506 for ; Thu, 22 Jan 2009 22:15:08 +0300 (MSK) Received: from mail by f136.mail.ru with local id 1LQ519-0005nU-00 for freebsd-stable@freebsd.org; Thu, 22 Jan 2009 22:15:07 +0300 Received: from [79.120.80.43] by win.mail.ru with HTTP; Thu, 22 Jan 2009 22:15:07 +0300 From: Alexey Beketov To: freebsd-stable@freebsd.org Mime-Version: 1.0 X-Mailer: mPOP Web-Mail 2.19 X-Originating-IP: [79.120.80.43] Date: Thu, 22 Jan 2009 22:15:07 +0300 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Message-Id: X-Spam: Not detected Subject: make buildkernel fails X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Alexey Beketov List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jan 2009 19:41:38 -0000 I trying to rebuild world and kernel on 7.1 My steps: 1) updated sources ok 2) make buildworld ok 3) make buildkernel fail here is an error I got: ------------------------------------------------------- ===> umass (all) awk -f @/tools/makeobjops.awk @/kern/device_if.m -h awk -f @/tools/makeobjops.awk @/kern/bus_if.m -h awk -f @/tools/usbdevs2h.awk @/dev/usb/usbdevs -h cc -O2 -fno-strict-aliasing -pipe -D_KERNEL -DKLD_MODULE -std=c99 -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj/usr/src/sys/my_kern/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -I/usr/obj/usr/src/sys/my_kern -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c /usr/src/sys/modules/umass/../../dev/usb/umass.c /usr/src/sys/modules/umass/../../dev/usb/umass.c:577: error: 'USB_PRODUCT_NETAC_ONLYDISK' undeclared here (not in a function) /usr/src/sys/modules/umass/../../dev/usb/umass.c:613: error: 'USB_PRODUCT_ONSPEC_SDS_HOTFIND_D' undeclared here (not in a function) *** Error code 1 Stop in /usr/src/sys/modules/umass. *** Error code 1 Stop in /usr/src/sys/modules. *** Error code 1 Stop in /usr/obj/usr/src/sys/my_kern. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. --------------------------------------------------------- What wrong? From owner-freebsd-stable@FreeBSD.ORG Thu Jan 22 19:50: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 00A5F1065675 for ; Thu, 22 Jan 2009 19:50:10 +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 B24C28FC14 for ; Thu, 22 Jan 2009 19:50:09 +0000 (UTC) (envelope-from korvus@comcast.net) Received: from OMTA06.emeryville.ca.mail.comcast.net ([76.96.30.51]) by QMTA05.emeryville.ca.mail.comcast.net with comcast id 6eeN1b00A16AWCUA5jqAzH; Thu, 22 Jan 2009 19:50:10 +0000 Received: from [192.168.2.164] ([206.210.89.202]) by OMTA06.emeryville.ca.mail.comcast.net with comcast id 6jpw1b00a4Mx3R28SjpzY0; Thu, 22 Jan 2009 19:50:08 +0000 Message-ID: <4978CDE3.4040700@comcast.net> Date: Thu, 22 Jan 2009 14:49:55 -0500 From: Steve Polyack User-Agent: Thunderbird 2.0.0.19 (X11/20090105) MIME-Version: 1.0 To: freebsd-hardware@freebsd.org, Mike Tancsa , scottl@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: amr driver issues in 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: Thu, 22 Jan 2009 19:50:10 -0000 We have multiple systems using LSILogic PERC4 cards (PERC4e/Si, PERC4/DC, amr driver). After recently upgrading two of them from 6.3 to 7.1, we have begun to see the following errors in our logs during heavy use in both systems: amr0: Too many retries on command 0xffffffff80a4da58. Controller is likely dead amr0: Too many retries on command 0xffffffff80a4eaa8. Controller is likely dead amr0: Too many retries on command 0xffffffff80a497a0. Controller is likely dead amr0: Too many retries on command 0xffffffff80a4eaa8. Controller is likely dead However, the system continues working and the volumes remain accessible. This happens on the PERC4/DC controllers in both systems. Firmware version is 352D. MegaCLI reports no problems. Has anyone else seen these messages? A google search turns up nothing but results in the driver code. Is this something we should be worried about? We won't be moving any other systems to 7.1 until we can clear this up. Thanks! -Steve Polyack From owner-freebsd-stable@FreeBSD.ORG Thu Jan 22 19:50: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 5B34F106566B for ; Thu, 22 Jan 2009 19:50:54 +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 0905D8FC1C for ; Thu, 22 Jan 2009 19:50:53 +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 n0MJoptj031703; Thu, 22 Jan 2009 14:50:51 -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 n0MJooKx016757 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 22 Jan 2009 14:50:50 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <200901221950.n0MJooKx016757@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Thu, 22 Jan 2009 14:50:52 -0500 To: Alexey Beketov , freebsd-stable@freebsd.org From: Mike Tancsa In-Reply-To: References: 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: make buildkernel fails X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jan 2009 19:50:55 -0000 At 02:15 PM 1/22/2009, Alexey Beketov wrote: >I trying to rebuild world and kernel on 7.1 >My steps: >1) updated sources ok Hi, There was a commit just recently that fixed this problem. Try and cvsup again and all should be fixed. ---Mike From owner-freebsd-stable@FreeBSD.ORG Thu Jan 22 19:55: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 28B1710656CD for ; Thu, 22 Jan 2009 19:55:53 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from mail.rachie.is-a-geek.net (rachie.is-a-geek.net [66.230.99.27]) by mx1.freebsd.org (Postfix) with ESMTP id D7DCF8FC21 for ; Thu, 22 Jan 2009 19:55:52 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from localhost (mail.rachie.is-a-geek.net [192.168.2.101]) by mail.rachie.is-a-geek.net (Postfix) with ESMTP id 048D3AFC1FF; Thu, 22 Jan 2009 10:41:02 -0900 (AKST) From: Mel To: freebsd-stable@freebsd.org Date: Thu, 22 Jan 2009 10:41:01 -0900 User-Agent: KMail/1.9.10 References: <200901220924.14957.fbsd.questions@rachie.is-a-geek.net> <37861.8202.qm@web111307.mail.gq1.yahoo.com> In-Reply-To: <37861.8202.qm@web111307.mail.gq1.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200901221041.01780.fbsd.questions@rachie.is-a-geek.net> Cc: Janos Dohanics , freebsd-questions@freebsd.org, Abdullah Ibn Hamad Al-Marri Subject: Re: error: field 'aio_sigevent' has incomplete type X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jan 2009 19:55:54 -0000 On Thursday 22 January 2009 09:32:45 Abdullah Ibn Hamad Al-Marri wrote: > ----- Original Message ---- > > > From: Mel > > To: freebsd-questions@freebsd.org > > Cc: Janos Dohanics > > Sent: Thursday, January 22, 2009 9:24:14 PM > > Subject: Re: error: field 'aio_sigevent' has incomplete type > > > > On Wednesday 21 January 2009 22:48:45 Janos Dohanics wrote: > > > cc -O2 -fno-strict-aliasing -pipe -D_KERNEL -DKLD_MODULE -std=c99 > > > -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include > > > /usr/obj/usr/src/sys/FRACASSO2009012201/opt_global.h -I. -I@ > > > -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 > > > --param large-function-growth=1000 -fno-common -g > > > -fno-omit-frame-pointer -I/usr/obj/usr/src/sys/FRACASSO2009012201 > > > -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx > > > -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding > > > -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes > > > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef > > > -Wno-pointer-sign -fformat-extensions -c > > > /usr/src/sys/modules/aio/../../kern/vfs_aio.c > > > /usr/src/sys/modules/aio/../../kern/vfs_aio.c:2548: error: field > > > 'aio_sigevent' has incomplete type > > > > > > > > > > > > *** Error code 1 > > > 1 error > > > *** Error code 2 > > > 1 error > > > *** Error code 2 > > > > build continues: > > > cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -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 > > > -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx > > > -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding > > > -Werror /usr/src/sys/libkern/strcmp.c > > > > Build kernel without -j2, then report if error persists. > > -- > > Mel > > > > Problem with today's modular software: they start with the modules > > and never get to the software part. > > Here we go without -j flag for the kernel. > > ===> aio (all) > cc -O2 -fno-strict-aliasing -pipe -D_KERNEL -DKLD_MODULE -std=c99 > -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include > /usr/obj/usr/src/sys/VB/opt_global.h -I. -I@ -I@/contrib/altq > -finline-limit=8000 --param inline-unit-growth=100 --param > large-function-growth=1000 -fno-common -g -fno-omit-frame-pointer > -I/usr/obj/usr/src/sys/VB -mcmodel=kernel -mno-red-zone -mfpmath=387 > -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float > -fno-asynchronous-unwind-tables -ffreestanding -Wall -Wredundant-decls > -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith > -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c > /usr/src/sys/modules/aio/../../kern/vfs_aio.c > /usr/src/sys/modules/aio/../../kern/vfs_aio.c:2548: error: field > 'aio_sigevent' has incomplete type > /usr/src/sys/modules/aio/../../kern/vfs_aio.c:2564: error: field > 'aio_sigevent' has incomplete type > /usr/src/sys/modules/aio/../../kern/vfs_aio.c: In function > 'convert_old_sigevent32': > /usr/src/sys/modules/aio/../../kern/vfs_aio.c:2575: error: dereferencing > pointer to incomplete type > /usr/src/sys/modules/aio/../../kern/vfs_aio.c:2580: error: dereferencing > pointer to incomplete type > /usr/src/sys/modules/aio/../../kern/vfs_aio.c:2584: error: dereferencing > pointer to incomplete type > /usr/src/sys/modules/aio/../../kern/vfs_aio.c:2585: error: dereferencing > pointer to incomplete type /usr/src/sys/modules/aio/../../kern/vfs_aio.c: > In function 'convert_sigevent32': > /usr/src/sys/modules/aio/../../kern/vfs_aio.c:2621: error: dereferencing > pointer to incomplete type > /usr/src/sys/modules/aio/../../kern/vfs_aio.c:2626: error: dereferencing > pointer to incomplete type > /usr/src/sys/modules/aio/../../kern/vfs_aio.c:2629: error: dereferencing > pointer to incomplete type > /usr/src/sys/modules/aio/../../kern/vfs_aio.c:2632: error: dereferencing > pointer to incomplete type > /usr/src/sys/modules/aio/../../kern/vfs_aio.c:2633: error: dereferencing > pointer to incomplete type /usr/src/sys/modules/aio/../../kern/vfs_aio.c: > In function 'freebsd32_olio_listio': > /usr/src/sys/modules/aio/../../kern/vfs_aio.c:2859: error: storage size of > 'osig' isn't known /usr/src/sys/modules/aio/../../kern/vfs_aio.c:2859: > warning: unused variable 'osig' > /usr/src/sys/modules/aio/../../kern/vfs_aio.c: In function > 'freebsd32_lio_listio': /usr/src/sys/modules/aio/../../kern/vfs_aio.c:2904: > error: storage size of 'sig32' isn't known > /usr/src/sys/modules/aio/../../kern/vfs_aio.c:2904: warning: unused > variable 'sig32' *** Error code 1 > > Stop in /usr/src/sys/modules/aio. > *** Error code 1 Likely culprit: http://svn.freebsd.org/viewvc/base?view=revision&revision=187559 Best continued on -stable. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. From owner-freebsd-stable@FreeBSD.ORG Thu Jan 22 20:00: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 A9511106566B for ; Thu, 22 Jan 2009 20:00:52 +0000 (UTC) (envelope-from ciel-par-webcarnews-14017@votremessage.net) Received: from smtp523.votremessage.net (ns-252-213.votremessage.net [81.93.252.213]) by mx1.freebsd.org (Postfix) with SMTP id 35DDB8FC14 for ; Thu, 22 Jan 2009 20:00:52 +0000 (UTC) (envelope-from ciel-par-webcarnews-14017@votremessage.net) Date: Thu, 22 Jan 2009 21:00:51 +0100 To: "freebsd-stable@freebsd.org" From: Ciel par Webcarnews Message-ID: X-Priority: 3 X-MDW-MemberId: h4b68f65696$ X-MDW-opeId: 14017$ X-Abuse-Contact: abuse@votremessage.net X-Abuse-Info: Please forward a copy of all headers for proper handling MIME-Version: 1.0 Content-Type: text/plain; charset = "iso-8859-1" Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: =?iso-8859-1?q?G=E9rez_et_fid=E9lisez_vos_clients?= X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Ciel par Webcarnews List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jan 2009 20:00:53 -0000 Si vous desirez visualiser ce mail au format html, recopiez l'adresse suivante dans votre navigateur: http://www.vmail-gamma.com/view.html?id=14017&ref=h4b68f65696 From owner-freebsd-stable@FreeBSD.ORG Thu Jan 22 20:28: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 4F4BC106567C; Thu, 22 Jan 2009 20:28:20 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id C0C938FC19; Thu, 22 Jan 2009 20:28:19 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from [10.92.110.42] (mobile-032-158-094-188.mycingular.net [32.158.94.188] (may be forged)) (authenticated bits=0) by pooker.samsco.org (8.14.2/8.14.2) with ESMTP id n0MJqP11053693; Thu, 22 Jan 2009 12:52:35 -0700 (MST) (envelope-from scottl@samsco.org) References: <4978CDE3.4040700@comcast.net> Message-Id: <55889FEE-0F42-4D40-8E90-447A2AFF70A6@samsco.org> From: Scott Long To: Steve Polyack In-Reply-To: <4978CDE3.4040700@comcast.net> Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-Mailer: iPhone Mail (5G77) Mime-Version: 1.0 (iPhone Mail 5G77) Date: Thu, 22 Jan 2009 12:52:15 -0700 X-Spam-Status: No, score=-2.6 required=3.8 tests=BAYES_00 autolearn=ham version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: "scottl@freebsd.org" , Mike Tancsa , "freebsd-hardware@freebsd.org" Subject: Re: amr driver issues in 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: Thu, 22 Jan 2009 20:28:21 -0000 I might have a fix for this, let me check and get back to you. Scott Sent from my iPhone On Jan 22, 2009, at 12:49 PM, Steve Polyack wrote: > We have multiple systems using LSILogic PERC4 cards (PERC4e/Si, > PERC4/DC, amr driver). After recently upgrading two of them from > 6.3 to 7.1, we have begun to see the following errors in our logs > during heavy use in both systems: > amr0: Too many retries on command 0xffffffff80a4da58. Controller is > likely dead > amr0: Too many retries on command 0xffffffff80a4eaa8. Controller is > likely dead > amr0: Too many retries on command 0xffffffff80a497a0. Controller is > likely dead > amr0: Too many retries on command 0xffffffff80a4eaa8. Controller is > likely dead > > However, the system continues working and the volumes remain > accessible. This happens on the PERC4/DC controllers in both > systems. Firmware version is 352D. MegaCLI reports no problems. > > Has anyone else seen these messages? A google search turns up > nothing but results in the driver code. Is this something we should > be worried about? We won't be moving any other systems to 7.1 until > we can clear this up. > > Thanks! > > -Steve Polyack From owner-freebsd-stable@FreeBSD.ORG Thu Jan 22 21:15: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 6A07A1065673; Thu, 22 Jan 2009 21:15:53 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id 1E2BD8FC25; Thu, 22 Jan 2009 21:15:52 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.local ([192.168.254.200]) (authenticated bits=0) by pooker.samsco.org (8.14.2/8.14.2) with ESMTP id n0MLFkFK054146; Thu, 22 Jan 2009 14:15:47 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <4978E202.70408@samsco.org> Date: Thu, 22 Jan 2009 14:15:46 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.13) Gecko/20080313 SeaMonkey/1.1.9 MIME-Version: 1.0 To: Steve Polyack References: <4978CDE3.4040700@comcast.net> In-Reply-To: <4978CDE3.4040700@comcast.net> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.4 required=3.8 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: Mike Tancsa , freebsd-hardware@freebsd.org Subject: Re: amr driver issues in 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: Thu, 22 Jan 2009 21:15:53 -0000 Steve Polyack wrote: > We have multiple systems using LSILogic PERC4 cards (PERC4e/Si, > PERC4/DC, amr driver). After recently upgrading two of them from 6.3 to > 7.1, we have begun to see the following errors in our logs during heavy > use in both systems: > amr0: Too many retries on command 0xffffffff80a4da58. Controller is > likely dead > amr0: Too many retries on command 0xffffffff80a4eaa8. Controller is > likely dead > amr0: Too many retries on command 0xffffffff80a497a0. Controller is > likely dead > amr0: Too many retries on command 0xffffffff80a4eaa8. Controller is > likely dead > > However, the system continues working and the volumes remain > accessible. This happens on the PERC4/DC controllers in both systems. > Firmware version is 352D. MegaCLI reports no problems. > > Has anyone else seen these messages? A google search turns up nothing > but results in the driver code. Is this something we should be worried > about? We won't be moving any other systems to 7.1 until we can clear > this up. > The fix for this that I was thinking of is already in 7.1. There might still be a driver bug, but I'm leaning more towards the controller simply being busy. Do you have a reproducible test case that I could try? Scott From owner-freebsd-stable@FreeBSD.ORG Thu Jan 22 21:24:18 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 2E392106564A for ; Thu, 22 Jan 2009 21:24:18 +0000 (UTC) (envelope-from ehrmann@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 CD2768FC1E for ; Thu, 22 Jan 2009 21:24:17 +0000 (UTC) (envelope-from ehrmann@gmail.com) Received: by yx-out-2324.google.com with SMTP id 8so1848492yxb.13 for ; Thu, 22 Jan 2009 13:24:17 -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=OyL2LS3IKle/C6+bHREMpnylDnuuz1/FhytqXHkATpU=; b=uo/wgLpgsNxAC7dqm36Sre+ey2/cNzziRzoR26WawUJireULzJTwIm9j3/tKaFin4q bN3CGwMYJuZK2tRTfOD18RfIox45CIpl8GVa12UfGHkYEtIB1xgb9SjyXhWdO/q1+9v4 XFF+BS6t9F9ZvRPnEAxkTbgZsH39wV6HjgBls= 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=io2WvLxQ6SsgI3kn/VR8bmO3TU8njlXxdoV1aYAsX8pS3TSlXfzQtSAmIUw9MdWgHj pChbR6orRxuXObSkPydcweFjGMqwh+3uBkLjEFWHt6kFp07ghyrgfBZmW2Hq9yYKsKEc PIaA+56Dh1Kmy1lROWiMh1PxHWZXjTdtxcUac= MIME-Version: 1.0 Received: by 10.100.164.20 with SMTP id m20mr221531ane.97.1232659457230; Thu, 22 Jan 2009 13:24:17 -0800 (PST) In-Reply-To: <6e0e5340901161521t30845197s9529fb5a55dbba13@mail.gmail.com> References: <6e0e5340901151158n5108ba8ct6af8fb270b10b75b@mail.gmail.com> <6e0e5340901161521t30845197s9529fb5a55dbba13@mail.gmail.com> Date: Thu, 22 Jan 2009 13:24:17 -0800 Message-ID: <6e0e5340901221324o33f1e2b1l53c842ebf9dad9a8@mail.gmail.com> From: David Ehrmann To: Pete French Content-Type: text/plain; charset=ISO-8859-1 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jan 2009 21:24:18 -0000 On Fri, Jan 16, 2009 at 3:21 PM, David Ehrmann wrote: > On Fri, Jan 16, 2009 at 3:33 AM, Pete French > 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." 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. > Ok, here's where it gets interesting: The next time I saw the import error, I ran zdb -l on the actual dev. It couldn't find the labels. So I used dd to grab the first 4k of the .eli device and the actual device. Once I got it working, I repeated. The data in the first 4k of /dev/ad8 were all 0x00 both times. I'm guessing this is reserved, or something. The data in the first 4k of /dev/ad8.eli differed between runs (so zdb -l is probably right about not finding the label). In the /dev/ad8.eli that zfs doesn't recognize, I found a 16 byte string that was repeated a lot, but it was also repeated in another place: the good /dev/ad10.eli (though the offsets were different). The other weird thing: the good and bad /dev/ad8.eli look a lot alike: one 16 byte string, then another that gets repeated, then another 16 byte string randomly shows up at 0x200. Why the same data appear in the bad ad8.eli as the good ad10.eli, I'm not sure (I do have the same password and no keyfile with geli), but the patterns of data looking the same make me think something's wrong with the encryption. It's using 128 bit AES-CBC, and these patterns would not be hidden by it (128 bits == 16 bytes). I'm using a Via C7 CPU's padlock cryptographic accelerator, and geli reports this. I'm guessing this is either a padlock or a geli bug. I can't reliably reproduce this problem, but doing it with padlock off might be a good test. From owner-freebsd-stable@FreeBSD.ORG Thu Jan 22 21:26:25 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 F090A106568E; Thu, 22 Jan 2009 21:26:25 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id C495C8FC1D; Thu, 22 Jan 2009 21:26:25 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.14.3/8.14.3) with ESMTP id n0MLQJfT044913; Thu, 22 Jan 2009 16:26:19 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-stable.sentex.ca (freebsd-stable.sentex.ca [64.7.128.103]) by smtp2.sentex.ca (8.14.3/8.14.3) with ESMTP id n0MLQJJv053196; Thu, 22 Jan 2009 16:26:19 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-stable.sentex.ca (Postfix, from userid 666) id 1A5181B5060; Thu, 22 Jan 2009 16:26:19 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20090122212619.1A5181B5060@freebsd-stable.sentex.ca> Date: Thu, 22 Jan 2009 16:26:19 -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 64.7.153.18 Cc: Subject: [releng_7 tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jan 2009 21:26:26 -0000 TB --- 2009-01-22 19:46:04 - tinderbox 2.6 running on freebsd-stable.sentex.ca TB --- 2009-01-22 19:46:04 - starting RELENG_7 tinderbox run for amd64/amd64 TB --- 2009-01-22 19:46:04 - cleaning the object tree TB --- 2009-01-22 19:46:19 - cvsupping the source tree TB --- 2009-01-22 19:46:19 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/amd64/amd64/supfile TB --- 2009-01-22 19:46:28 - building world TB --- 2009-01-22 19:46:28 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-22 19:46:28 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-22 19:46:28 - TARGET=amd64 TB --- 2009-01-22 19:46:28 - TARGET_ARCH=amd64 TB --- 2009-01-22 19:46:28 - TZ=UTC TB --- 2009-01-22 19:46:28 - __MAKE_CONF=/dev/null TB --- 2009-01-22 19:46:28 - cd /src TB --- 2009-01-22 19:46:28 - /usr/bin/make -B buildworld >>> World build started on Thu Jan 22 19:46:29 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 >>> stage 5.1: building 32 bit shim libraries >>> World build completed on Thu Jan 22 21:16:03 UTC 2009 TB --- 2009-01-22 21:16:03 - generating LINT kernel config TB --- 2009-01-22 21:16:03 - cd /src/sys/amd64/conf TB --- 2009-01-22 21:16:03 - /usr/bin/make -B LINT TB --- 2009-01-22 21:16:03 - building LINT kernel TB --- 2009-01-22 21:16:03 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-22 21:16:03 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-22 21:16:03 - TARGET=amd64 TB --- 2009-01-22 21:16:03 - TARGET_ARCH=amd64 TB --- 2009-01-22 21:16:03 - TZ=UTC TB --- 2009-01-22 21:16:03 - __MAKE_CONF=/dev/null TB --- 2009-01-22 21:16:03 - cd /src TB --- 2009-01-22 21:16:03 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Thu Jan 22 21:16:03 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 [...] /src/sys/kern/vfs_aio.c:2633: error: dereferencing pointer to incomplete type /src/sys/kern/vfs_aio.c: In function 'freebsd32_olio_listio': /src/sys/kern/vfs_aio.c:2859: error: storage size of 'osig' isn't known cc1: warnings being treated as errors /src/sys/kern/vfs_aio.c:2859: warning: unused variable 'osig' /src/sys/kern/vfs_aio.c: In function 'freebsd32_lio_listio': /src/sys/kern/vfs_aio.c:2904: error: storage size of 'sig32' isn't known /src/sys/kern/vfs_aio.c:2904: warning: unused variable 'sig32' *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-01-22 21:26:18 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-01-22 21:26:18 - ERROR: failed to build lint kernel TB --- 2009-01-22 21:26:18 - 4963.09 user 557.23 system 6014.45 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-amd64-amd64.full From owner-freebsd-stable@FreeBSD.ORG Thu Jan 22 21:27: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 03113106571B for ; Thu, 22 Jan 2009 21:27:22 +0000 (UTC) (envelope-from korvus@comcast.net) Received: from QMTA04.westchester.pa.mail.comcast.net (qmta04.westchester.pa.mail.comcast.net [76.96.62.40]) by mx1.freebsd.org (Postfix) with ESMTP id 9317F8FC1F for ; Thu, 22 Jan 2009 21:27:22 +0000 (UTC) (envelope-from korvus@comcast.net) Received: from OMTA04.westchester.pa.mail.comcast.net ([76.96.62.35]) by QMTA04.westchester.pa.mail.comcast.net with comcast id 6bYp1b0070ldTLk54lTNtH; Thu, 22 Jan 2009 21:27:23 +0000 Received: from [192.168.2.164] ([206.210.89.202]) by OMTA04.westchester.pa.mail.comcast.net with comcast id 6lT71b00P4Mx3R23QlTAdt; Thu, 22 Jan 2009 21:27:18 +0000 Message-ID: <4978E4AA.8050601@comcast.net> Date: Thu, 22 Jan 2009 16:27:06 -0500 From: Steve Polyack User-Agent: Thunderbird 2.0.0.19 (X11/20090105) MIME-Version: 1.0 To: Scott Long References: <4978CDE3.4040700@comcast.net> <4978E202.70408@samsco.org> In-Reply-To: <4978E202.70408@samsco.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Mike Tancsa , freebsd-hardware@freebsd.org Subject: Re: amr driver issues in 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: Thu, 22 Jan 2009 21:27:24 -0000 Scott Long wrote: > The fix for this that I was thinking of is already in 7.1. There > might still be a driver bug, but I'm leaning more towards the > controller simply being busy. Do you have a reproducible test case > that I could > try? > > Scott > We saw this one while backups wrote from an array on the PERC4/DC to a tape drive (on a separate controller). amr1: Too many retries on command 0xffffffff80a6d060. Controller is likely dead The other four which I noted came during writes to the array attached to the PERC4/DC (external Dell PowerVault). I want to say they showed up while writing a 30G junkfile (/dev/random) to the array which we were using to test the tape access; either that, or while we wrote that file out to the tape drive. If it matters, we also use ports/sysutils/linux-megacli2 to periodically check the status of our arrays. It's possible that this happened during one of these long writes/reads. I'm not having any luck reproducing at the moment, but if I come across a reproducible test, I will let you know. Thanks! Steve Polyack From owner-freebsd-stable@FreeBSD.ORG Thu Jan 22 21:49:05 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 B6A58106568A; Thu, 22 Jan 2009 21:49:05 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id 683168FC22; Thu, 22 Jan 2009 21:49:05 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.local ([192.168.254.200]) (authenticated bits=0) by pooker.samsco.org (8.14.2/8.14.2) with ESMTP id n0MLmwOW054263; Thu, 22 Jan 2009 14:48:58 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <4978E9CA.8040908@samsco.org> Date: Thu, 22 Jan 2009 14:48:58 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.13) Gecko/20080313 SeaMonkey/1.1.9 MIME-Version: 1.0 To: Steve Polyack References: <4978CDE3.4040700@comcast.net> <4978E202.70408@samsco.org> <4978E4AA.8050601@comcast.net> In-Reply-To: <4978E4AA.8050601@comcast.net> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.4 required=3.8 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: Mike Tancsa , freebsd-hardware@freebsd.org Subject: Re: amr driver issues in 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: Thu, 22 Jan 2009 21:49:06 -0000 Steve Polyack wrote: > Scott Long wrote: >> The fix for this that I was thinking of is already in 7.1. There >> might still be a driver bug, but I'm leaning more towards the >> controller simply being busy. Do you have a reproducible test case >> that I could >> try? >> >> Scott >> > We saw this one while backups wrote from an array on the PERC4/DC to a > tape drive (on a separate controller). > amr1: Too many retries on command 0xffffffff80a6d060. Controller is > likely dead > > The other four which I noted came during writes to the array attached to > the PERC4/DC (external Dell PowerVault). I want to say they showed up > while writing a 30G junkfile (/dev/random) to the array which we were > using to test the tape access; either that, or while we wrote that file > out to the tape drive. > > If it matters, we also use ports/sysutils/linux-megacli2 to periodically > check the status of our arrays. It's possible that this happened during > one of these long writes/reads. I'm not having any luck reproducing at > the moment, but if I come across a reproducible test, I will let you know. > I don't know too much about the internals of the AMR firmware, but I imagine that it could be possible that a management command from megacli could stall the firmware and make this warning pop up. I'll see if I can reproduce it. The warning is harmless, though, even if it is strongly worded. Scott From owner-freebsd-stable@FreeBSD.ORG Thu Jan 22 22:11: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 D45951065675 for ; Thu, 22 Jan 2009 22:11:50 +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 A212A8FC14 for ; Thu, 22 Jan 2009 22:11:50 +0000 (UTC) (envelope-from dan@langille.org) Received: from localhost (localhost [127.0.0.1]) by nyi.unixathome.org (Postfix) with ESMTP id F1B16509B5; Thu, 22 Jan 2009 22:11:49 +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 SKN77h84y7BD; Thu, 22 Jan 2009 22:11:41 +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 4A9B4509AD ; Thu, 22 Jan 2009 22:11:41 +0000 (GMT) Message-Id: <7697CDAB-B4E7-480A-B31A-1F54275B8D54@langille.org> From: Dan Langille To: Dan Langille In-Reply-To: <4978A10A.9060006@langille.org> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Thu, 22 Jan 2009 17:11:39 -0500 References: <49774BAE.3000809@ksu.ru> <20090122071845.GF4881@alf.bsdes.net> <4978A10A.9060006@langille.org> X-Mailer: Apple Mail (2.930.3) Cc: Victor Balada Diaz , freebsd-stable@freebsd.org, Pete French , "Marat N.Afanasyev" 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jan 2009 22:11:51 -0000 On Jan 22, 2009, at 11:38 AM, Dan Langille wrote: > Victor Balada Diaz wrote: >> On Wed, Jan 21, 2009 at 07:22:06PM +0300, Marat N.Afanasyev 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! >>>> >>>> -pete. >>>> >>> it's a kind of magic, really. I built a new kernel with KDB and >>> DDB and after 1 day, 13:15 I'm still waiting for storm to arrive. >>> And I added >>> hw.acpi.osname="Linux" to /boot/loader.conf. >> Try doing lots of IO and you will get the problem soon. You might >> want to try: >> while true; do dd if=/dev/zero of=BAH bs=1M count=1024; sync; done > > FWIW, last night I changed the address of the comm port IO in my > BIOS. Then I ran the Bacula regression test suite (lots of IO). For > my machine, once the interrupt storm starts, it continues. I do not > know if that happens to everyone. > > Since changing the address, I have had no interrupt storms. I have > been running the above IO loop for about ten minutes. > > No storm yet (knock on wood). And it's back: Jan 22 17:21:46 polo kernel: interrupt storm detected on "irq22:"; throttling interrupt source Jan 22 17:23:19 polo kernel: interrupt storm detected on "irq22:"; throttling interrupt source Jan 22 17:28:20 polo kernel: interrupt storm detected on "irq22:"; throttling interrupt source Jan 22 17:33:20 polo kernel: interrupt storm detected on "irq22:"; throttling interrupt source Jan 22 17:38:20 polo kernel: interrupt storm detected on "irq22:"; throttling interrupt source I shall try the hw.acpi.osname="Linux" option now. From dmsg: Jan 22 18:10:07 polo kernel: ACPI: Overriding _OS definition with "Linux" -- Dan Langille http://langille.org/ From owner-freebsd-stable@FreeBSD.ORG Thu Jan 22 22:22: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 19CC11065670 for ; Thu, 22 Jan 2009 22:22:36 +0000 (UTC) (envelope-from danallen46@airwired.net) Received: from mail.utahbroadband.com (mail.utahbroadband.com [204.14.20.91]) by mx1.freebsd.org (Postfix) with ESMTP id D29248FC1A for ; Thu, 22 Jan 2009 22:22:35 +0000 (UTC) (envelope-from danallen46@airwired.net) Received: (qmail 6784 invoked by uid 89); 22 Jan 2009 21:46:19 -0000 Received: from unknown (HELO ?192.168.0.16?) (danallen46@airwired.net@66.29.174.6) by 0 with ESMTPA; 22 Jan 2009 21:46:19 -0000 Message-Id: <688E898C-3241-4182-BF79-083F7523BDA5@airwired.net> From: Dan Allen To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Thu, 22 Jan 2009 14:55:52 -0700 X-Mailer: Apple Mail (2.930.3) Subject: Re: make buildkernel fails X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jan 2009 22:22:36 -0000 > ===> umass (all) > /usr/src/sys/modules/umass/../../dev/usb/umass.c:577: error: > 'USB_PRODUCT_NETAC_ONLYDISK' undeclared here (not in a function) > /usr/src/sys/modules/umass/../../dev/usb/umass.c:613: error: > 'USB_PRODUCT_ONSPEC_SDS_HOTFIND_D' undeclared here (not in a function) > *** Error code 1 I got this same error but after syncing just now to get a new /usr/src/ sys/dev/usb/usbdevs file the build once again succeeds. Dan From owner-freebsd-stable@FreeBSD.ORG Fri Jan 23 00:13:12 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 883E5106566B; Fri, 23 Jan 2009 00:13:12 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id 413988FC18; Fri, 23 Jan 2009 00:13:12 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.14.3/8.14.3) with ESMTP id n0N0D9aD056715; Thu, 22 Jan 2009 19:13:09 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-stable.sentex.ca (freebsd-stable.sentex.ca [64.7.128.103]) by smtp2.sentex.ca (8.14.3/8.14.3) with ESMTP id n0N0D9pX015230; Thu, 22 Jan 2009 19:13:09 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-stable.sentex.ca (Postfix, from userid 666) id 579201B5060; Thu, 22 Jan 2009 19:13:09 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20090123001309.579201B5060@freebsd-stable.sentex.ca> Date: Thu, 22 Jan 2009 19:13:09 -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 64.7.153.18 Cc: Subject: [releng_7 tinderbox] failure on ia64/ia64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jan 2009 00:13:13 -0000 TB --- 2009-01-22 22:35:53 - tinderbox 2.6 running on freebsd-stable.sentex.ca TB --- 2009-01-22 22:35:53 - starting RELENG_7 tinderbox run for ia64/ia64 TB --- 2009-01-22 22:35:53 - cleaning the object tree TB --- 2009-01-22 22:36:07 - cvsupping the source tree TB --- 2009-01-22 22:36:07 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/ia64/ia64/supfile TB --- 2009-01-22 22:36:15 - building world TB --- 2009-01-22 22:36:15 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-22 22:36:15 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-22 22:36:15 - TARGET=ia64 TB --- 2009-01-22 22:36:15 - TARGET_ARCH=ia64 TB --- 2009-01-22 22:36:15 - TZ=UTC TB --- 2009-01-22 22:36:15 - __MAKE_CONF=/dev/null TB --- 2009-01-22 22:36:15 - cd /src TB --- 2009-01-22 22:36:15 - /usr/bin/make -B buildworld >>> World build started on Thu Jan 22 22:36:16 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 Fri Jan 23 00:01:20 UTC 2009 TB --- 2009-01-23 00:01:20 - generating LINT kernel config TB --- 2009-01-23 00:01:20 - cd /src/sys/ia64/conf TB --- 2009-01-23 00:01:20 - /usr/bin/make -B LINT TB --- 2009-01-23 00:01:20 - building LINT kernel TB --- 2009-01-23 00:01:20 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-23 00:01:20 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-23 00:01:20 - TARGET=ia64 TB --- 2009-01-23 00:01:20 - TARGET_ARCH=ia64 TB --- 2009-01-23 00:01:20 - TZ=UTC TB --- 2009-01-23 00:01:20 - __MAKE_CONF=/dev/null TB --- 2009-01-23 00:01:20 - cd /src TB --- 2009-01-23 00:01:20 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri Jan 23 00:01:20 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 [...] /src/sys/kern/vfs_aio.c:2633: error: dereferencing pointer to incomplete type /src/sys/kern/vfs_aio.c: In function 'freebsd32_olio_listio': /src/sys/kern/vfs_aio.c:2859: error: storage size of 'osig' isn't known cc1: warnings being treated as errors /src/sys/kern/vfs_aio.c:2859: warning: unused variable 'osig' /src/sys/kern/vfs_aio.c: In function 'freebsd32_lio_listio': /src/sys/kern/vfs_aio.c:2904: error: storage size of 'sig32' isn't known /src/sys/kern/vfs_aio.c:2904: warning: unused variable 'sig32' *** Error code 1 Stop in /obj/ia64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-01-23 00:13:09 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-01-23 00:13:09 - ERROR: failed to build lint kernel TB --- 2009-01-23 00:13:09 - 5096.29 user 392.15 system 5835.46 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-ia64-ia64.full From owner-freebsd-stable@FreeBSD.ORG Fri Jan 23 01:45:05 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 1C97A106564A for ; Fri, 23 Jan 2009 01:45:05 +0000 (UTC) (envelope-from mike@jellydonut.org) Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.30]) by mx1.freebsd.org (Postfix) with ESMTP id C32CE8FC19 for ; Fri, 23 Jan 2009 01:45:04 +0000 (UTC) (envelope-from mike@jellydonut.org) Received: by yx-out-2324.google.com with SMTP id 8so1887531yxb.13 for ; Thu, 22 Jan 2009 17:45:04 -0800 (PST) MIME-Version: 1.0 Received: by 10.90.56.16 with SMTP id e16mr4416259aga.46.1232675104015; Thu, 22 Jan 2009 17:45:04 -0800 (PST) In-Reply-To: <6e0e5340901221324o33f1e2b1l53c842ebf9dad9a8@mail.gmail.com> References: <6e0e5340901151158n5108ba8ct6af8fb270b10b75b@mail.gmail.com> <6e0e5340901161521t30845197s9529fb5a55dbba13@mail.gmail.com> <6e0e5340901221324o33f1e2b1l53c842ebf9dad9a8@mail.gmail.com> Date: Thu, 22 Jan 2009 20:45:03 -0500 Message-ID: <1de79840901221745r4149dc30yfcfcb8c8a24ad8ce@mail.gmail.com> From: Michael Proto To: David Ehrmann Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Pete French 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jan 2009 01:45:05 -0000 On Thu, Jan 22, 2009 at 4:24 PM, David Ehrmann wrote: > On Fri, Jan 16, 2009 at 3:21 PM, David Ehrmann wrote: >> On Fri, Jan 16, 2009 at 3:33 AM, Pete French >> 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." 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. >> > > Ok, here's where it gets interesting: > > The next time I saw the import error, I ran zdb -l on the actual dev. > It couldn't find the labels. So I used dd to grab the first 4k of the > .eli device and the actual device. Once I got it working, I repeated. > The data in the first 4k of /dev/ad8 were all 0x00 both times. I'm > guessing this is reserved, or something. The data in the first 4k of > /dev/ad8.eli differed between runs (so zdb -l is probably right about > not finding the label). > > In the /dev/ad8.eli that zfs doesn't recognize, I found a 16 byte > string that was repeated a lot, but it was also repeated in another > place: the good /dev/ad10.eli (though the offsets were different). > The other weird thing: the good and bad /dev/ad8.eli look a lot alike: > one 16 byte string, then another that gets repeated, then another 16 > byte string randomly shows up at 0x200. > > Why the same data appear in the bad ad8.eli as the good ad10.eli, I'm > not sure (I do have the same password and no keyfile with geli), but > the patterns of data looking the same make me think something's wrong > with the encryption. It's using 128 bit AES-CBC, and these patterns > would not be hidden by it (128 bits == 16 bytes). > > I'm using a Via C7 CPU's padlock cryptographic accelerator, and geli > reports this. I'm guessing this is either a padlock or a geli bug. > > I can't reliably reproduce this problem, but doing it with padlock off > might be a good test. > _______________________________________________ > 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 saw something similar (minus zfs) when I was playing with padlock and geli on my C7-Esther fileserver. When trying to mount a geli partition I'd intermittently get a bad decryption key error. Run the same command again to mount the partition and it'd work fine. This was using both password and key-file operations. IIRC when I disabled padlock acceleration it worked fine in my limited testing. That was 6.4, now that I'm on 7.1 it might be worth looking at again. -Proto From owner-freebsd-stable@FreeBSD.ORG Fri Jan 23 02:05: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 2863C106566B for ; Fri, 23 Jan 2009 02:05:25 +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 EC19E8FC12 for ; Fri, 23 Jan 2009 02:05:24 +0000 (UTC) (envelope-from dan@langille.org) Received: from localhost (localhost [127.0.0.1]) by nyi.unixathome.org (Postfix) with ESMTP id 8FD8B509BF; Fri, 23 Jan 2009 02:05:24 +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 3IOPI88i1eDd; Fri, 23 Jan 2009 02:05:23 +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 E15DB509B5 ; Fri, 23 Jan 2009 02:05:22 +0000 (GMT) Message-Id: From: Dan Langille To: SEan Strand In-Reply-To: <7619cc20901200749w5126264bka61b7ac62188a578@mail.gmail.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Thu, 22 Jan 2009 21:05:21 -0500 References: <496D374A.3020704@langille.org> <496E9A37.20800@langille.org> <496EA339.6010808@ksu.ru> <496EB43A.8010805@langille.org> <496ECB2A.8080609@ksu.ru> <49754FA1.3070004@ksu.ru> <7619cc20901200749w5126264bka61b7ac62188a578@mail.gmail.com> X-Mailer: Apple Mail (2.930.3) 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jan 2009 02:05:25 -0000 On Jan 20, 2009, at 10:49 AM, SEan Strand wrote: > Re:K9A2 Platinum MSI repeated irq22. > > Hi gents, I once had this and just opened up the BIOS and changed > the comms-tty IRQ address and problem gone. Try ity and see if it > helps you? > Rgds SEanS That worked for a while. > > NB has any one had major problems updating this board from MSI with > a XP-64 bit CPU , I tryed all last week and no go, or am I the only > one? > Thanks in advance SEanS. > . > > 2009/1/20 Dan Langille > > On Jan 19, 2009, at 11:14 PM, Marat N.Afanasyev wrote: > > Marat N.Afanasyev wrote: > 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 :( > still no luck with fixing dsdt. I tried to build a custom dsdt, > tried to set hw.acpi.osname="Linux" in /boot/loader.conf, nothing > changes. so it may be related with APIC, not dsdt only. So, if > anyone has any idea how to find out what is happening, please tell > me, we'll try to fix this. > > Probably Pyun will give us some advice, wouldn't you? :) > > Or should I make a problem report? > > > Please. > > -- > Dan Langille > http://langille.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 > " > -- Dan Langille http://langille.org/ From owner-freebsd-stable@FreeBSD.ORG Fri Jan 23 03:43: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 B05DD106564A; Fri, 23 Jan 2009 03:43:04 +0000 (UTC) (envelope-from aw1@stade.co.uk) Received: from v-smtp-auth-relay-2.gradwell.net (v-smtp-auth-relay-2.gradwell.net [79.135.125.41]) by mx1.freebsd.org (Postfix) with ESMTP id D77C28FC41; Fri, 23 Jan 2009 03:43:03 +0000 (UTC) (envelope-from aw1@stade.co.uk) Received: from 5ad19545.bb.sky.com ([90.209.149.69] helo=access2.hanley.stade.co.uk country=GB) by v-smtp-auth-relay-2.gradwell.net with esmtp (Gradwell gwh-smtpd 1.290) id 49793325.773a.22b; Fri, 23 Jan 2009 03:01:57 +0000 (envelope-sender ) Received: from steerpike.hanley.stade.co.uk (steerpike [192.168.1.10]) by access2.hanley.stade.co.uk (8.14.1/8.14.1) with ESMTP id n0N31s8o066655; Fri, 23 Jan 2009 03:01:54 GMT (envelope-from aw1@steerpike.hanley.stade.co.uk) Received: from steerpike.hanley.stade.co.uk (localhost [127.0.0.1]) by steerpike.hanley.stade.co.uk (8.14.3/8.14.3) with ESMTP id n0N31sDK063262; Fri, 23 Jan 2009 03:01:54 GMT (envelope-from aw1@steerpike.hanley.stade.co.uk) Received: (from aw1@localhost) by steerpike.hanley.stade.co.uk (8.14.3/8.14.3/Submit) id n0N31pvM063261; Fri, 23 Jan 2009 03:01:51 GMT (envelope-from aw1) Date: Fri, 23 Jan 2009 03:01:51 +0000 From: Adrian Wontroba To: Jeffrey Williams Message-ID: <20090123030151.GA51388@steerpike.hanley.stade.co.uk> Mail-Followup-To: Adrian Wontroba , Jeffrey Williams , freebsd-stable@freebsd.org, mike@jellydonut.org, dimitry@andric.com, killing@multiplay.co.uk, Andrew Thompson References: <49777A7E.30904@sailorfej.net> <26ddd1750901211209k83250d7re8bb82dc2965ccd0@mail.gmail.com> <497785E2.5040007@sailorfej.net> <20090121203654.GB84399@citylink.fud.org.nz> <4977A06B.7060605@sailorfej.net> <4978C42E.5050500@sailorfej.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4978C42E.5050500@sailorfej.net> User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.1-PRERELEASE Organization: Oh dear, I've joined one again. X-Virus-Scanned: ClamAV version 0.94.2, clamav-milter version 0.94.2 on steerpike.hanley.stade.co.uk X-Virus-Status: Clean Cc: mike@jellydonut.org, dimitry@andric.com, freebsd-stable@freebsd.org, Andrew Thompson , killing@multiplay.co.uk Subject: Re: FreeBSD 7, runaway clock as guest OS on Microsoft Virtual Server X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: aw1@stade.co.uk List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jan 2009 03:43:04 -0000 On Thu, Jan 22, 2009 at 11:08:30AM -0800, Jeffrey Williams wrote: > Well this helped sort of, the clocks are running only a little fast at > this point (roughly seven minutes gained over 12 hours), but now for > some reason, ntpd is not resetting the clocks at all, despite multiple > good time sources, it was working fine before the kern.hz change. Any > reason why that would break ntpd? I'm afraid that most of the salient details are inaccessible at work, but I found this necessary to get sort of acceptable[*] time keeping in FreeBSD guests under VMware on Windows. Run a NTP server on the host. I used the Trimble NTP implementation, which I believe is no longer available. Disable Windows Time service. The last thing you want is more than one time adjustment mechanism - they fight, horribly. Run ntpd -b every minute on the guest against the host. Set VMware tools to not sync time. Make several non-standard settings in the guest's .vmx configuration file which disable time syncronisation at various points not covered by the VMware tools setting. Information found in some VMware technical documents. I'll dig this out tomorrow. End result - time skips +/- a few milliseconds each minute, and takes a while to sort itself out when the guest is suspended over a host reboot. [*] I've a thing about time. If all you want is a clock which is no slower than a minute out, and always goes forwards, ignore all of the above, don't run NTP on the guest, and set VMware tools to syncronise clocks. This is adequate for many. For my systems, I need better time keeping to distinguish cause from effect in problems involving interacting applications on multiple machines. -- Adrian Wontroba No matter what Cliff said, time is not the simplest thing (8-( From owner-freebsd-stable@FreeBSD.ORG Fri Jan 23 03:58:21 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 0A2CC1065676; Fri, 23 Jan 2009 03:58:21 +0000 (UTC) (envelope-from aw1@stade.co.uk) Received: from v-smtp-auth-relay-4.gradwell.net (v-smtp-auth-relay-4.gradwell.net [79.135.125.43]) by mx1.freebsd.org (Postfix) with ESMTP id 301B38FC12; Fri, 23 Jan 2009 03:58:20 +0000 (UTC) (envelope-from aw1@stade.co.uk) Received: from 5ad19545.bb.sky.com ([90.209.149.69] helo=access2.hanley.stade.co.uk country=GB) by v-smtp-auth-relay-4.gradwell.net with esmtp (Gradwell gwh-smtpd 1.290) id 4979405a.a67.33c; Fri, 23 Jan 2009 03:58:18 +0000 (envelope-sender ) Received: from steerpike.hanley.stade.co.uk (steerpike [192.168.1.10]) by access2.hanley.stade.co.uk (8.14.1/8.14.1) with ESMTP id n0N3wG0v066920; Fri, 23 Jan 2009 03:58:16 GMT (envelope-from aw1@steerpike.hanley.stade.co.uk) Received: from steerpike.hanley.stade.co.uk (localhost [127.0.0.1]) by steerpike.hanley.stade.co.uk (8.14.3/8.14.3) with ESMTP id n0N3wGLU064412; Fri, 23 Jan 2009 03:58:16 GMT (envelope-from aw1@steerpike.hanley.stade.co.uk) Received: (from aw1@localhost) by steerpike.hanley.stade.co.uk (8.14.3/8.14.3/Submit) id n0N3wFhc064411; Fri, 23 Jan 2009 03:58:15 GMT (envelope-from aw1) Date: Fri, 23 Jan 2009 03:58:15 +0000 From: Adrian Wontroba To: Jeffrey Williams , freebsd-stable@freebsd.org, mike@jellydonut.org, dimitry@andric.com, killing@multiplay.co.uk, Andrew Thompson Message-ID: <20090123035815.GA64127@steerpike.hanley.stade.co.uk> Mail-Followup-To: Adrian Wontroba , Jeffrey Williams , freebsd-stable@freebsd.org, mike@jellydonut.org, dimitry@andric.com, killing@multiplay.co.uk, Andrew Thompson References: <49777A7E.30904@sailorfej.net> <26ddd1750901211209k83250d7re8bb82dc2965ccd0@mail.gmail.com> <497785E2.5040007@sailorfej.net> <20090121203654.GB84399@citylink.fud.org.nz> <4977A06B.7060605@sailorfej.net> <4978C42E.5050500@sailorfej.net> <20090123030151.GA51388@steerpike.hanley.stade.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090123030151.GA51388@steerpike.hanley.stade.co.uk> User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.1-PRERELEASE Organization: Oh dear, I've joined one again. X-Virus-Scanned: ClamAV version 0.94.2, clamav-milter version 0.94.2 on steerpike.hanley.stade.co.uk X-Virus-Status: Clean Cc: Subject: Re: FreeBSD 7, runaway clock as guest OS on Microsoft Virtual Server X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: aw1@stade.co.uk List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jan 2009 03:58:21 -0000 On Fri, Jan 23, 2009 at 03:01:51AM +0000, Adrian Wontroba wrote: > I'm afraid that most of the salient details are inaccessible at work, > but I found this necessary to get sort of acceptable[*] time keeping in > FreeBSD guests under VMware on Windows. Sorry, I've got VMware on the brain at present, and missed the fact that you are using MS VS. We had time keeping problems with that too. And far worse ones with FreeBSD ATA drives dropping of the system and the unforgiveable fault of data corruption on Windows drives. Though the latter problem has been fixed, we've abandoned MS VS, VMware suits us better. -- Adrian Wontroba Organic chemistry is the chemistry of carbon compounds. Biochemistry is the study of carbon compounds that crawl. -- Mike Adams From owner-freebsd-stable@FreeBSD.ORG Fri Jan 23 04:08: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 C725D106564A for ; Fri, 23 Jan 2009 04:08:08 +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 DDE7A8FC13 for ; Fri, 23 Jan 2009 04:08:07 +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 DD0DF87F7A1A; Thu, 22 Jan 2009 22:08:05 -0600 (CST) Received: from localhost (morganw@localhost [127.0.0.1]) by volatile.chemikals.org (8.14.3/8.14.3) with ESMTP id n0N47sJ1055060; Thu, 22 Jan 2009 22:07:54 -0600 (CST) (envelope-from morganw@chemikals.org) Date: Thu, 22 Jan 2009 22:07:53 -0600 (CST) From: Wes Morgan To: David Ehrmann In-Reply-To: <6e0e5340901221324o33f1e2b1l53c842ebf9dad9a8@mail.gmail.com> Message-ID: References: <6e0e5340901151158n5108ba8ct6af8fb270b10b75b@mail.gmail.com> <6e0e5340901161521t30845197s9529fb5a55dbba13@mail.gmail.com> <6e0e5340901221324o33f1e2b1l53c842ebf9dad9a8@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, Pete French 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jan 2009 04:08:09 -0000 On Thu, 22 Jan 2009, David Ehrmann wrote: > On Fri, Jan 16, 2009 at 3:21 PM, David Ehrmann wrote: >> On Fri, Jan 16, 2009 at 3:33 AM, Pete French >> 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." 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. >> > > Ok, here's where it gets interesting: > > The next time I saw the import error, I ran zdb -l on the actual dev. > It couldn't find the labels. So I used dd to grab the first 4k of the > .eli device and the actual device. Once I got it working, I repeated. > The data in the first 4k of /dev/ad8 were all 0x00 both times. I'm > guessing this is reserved, or something. The data in the first 4k of > /dev/ad8.eli differed between runs (so zdb -l is probably right about > not finding the label). If your disk does not have an MBR or BSD disklabel, and you are using the whole device, the first 8k of the drive should be 0x00. > In the /dev/ad8.eli that zfs doesn't recognize, I found a 16 byte > string that was repeated a lot, but it was also repeated in another > place: the good /dev/ad10.eli (though the offsets were different). > The other weird thing: the good and bad /dev/ad8.eli look a lot alike: > one 16 byte string, then another that gets repeated, then another 16 > byte string randomly shows up at 0x200. The "xxx.eli" devices are the decrypted versions, aren't they? ZFS vdev labels and uberblocks occupy the first 512k of the device, and consist of virtually identical data, differing only by the GUID that the label claims to be and a sha256 checksum... So, decrypted, they should all be very, very similar. You could actually use the label from any device in a pool to reconstruct the label for any other device. > Why the same data appear in the bad ad8.eli as the good ad10.eli, I'm > not sure (I do have the same password and no keyfile with geli), but > the patterns of data looking the same make me think something's wrong > with the encryption. It's using 128 bit AES-CBC, and these patterns > would not be hidden by it (128 bits == 16 bytes). > > I'm using a Via C7 CPU's padlock cryptographic accelerator, and geli > reports this. I'm guessing this is either a padlock or a geli bug. > > I can't reliably reproduce this problem, but doing it with padlock off > might be a good test. > _______________________________________________ > 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 23 05:08: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 8C7221065675 for ; Fri, 23 Jan 2009 05:08:06 +0000 (UTC) (envelope-from ehrmann@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.248]) by mx1.freebsd.org (Postfix) with ESMTP id 3AA238FC14 for ; Fri, 23 Jan 2009 05:08:06 +0000 (UTC) (envelope-from ehrmann@gmail.com) Received: by an-out-0708.google.com with SMTP id b38so558540ana.13 for ; Thu, 22 Jan 2009 21:08:05 -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=f71o2JTXGF/3RyPjFCyUncxDaSpwtqfvHPh7lxigke4=; b=VGcOqAG4HqO1AcTCDZMbU1eX9q4vQStkyPfTm7w3y/uO/cRbe5cvbjQ2e7DkXml9V0 TX+AuQArz16MvD+FMR/wPeneewMbG9XpFBhwr099dhj5UiJsfhmgbq7Z27c2X4RhskBU 8XIa3nRXMqRX17ryKLqSIF5V0PUQYhdihYnw4= 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=TFgqMgSuvoqFR7u4WajI2nN9KghGc0RW5MuT/wrVybMmwtYL4TaHIbs/NwG1KPoBPt iMoUKrDloEX0LVkaty+eFQN7NkZChbHL6OXRymz1Chka4uYbLdIQyRw2jFrUFZHfWd4S HwVJEP4kkezishBajhddH3sXnxXqO8ps13DNo= MIME-Version: 1.0 Received: by 10.100.154.17 with SMTP id b17mr4285464ane.155.1232687285542; Thu, 22 Jan 2009 21:08:05 -0800 (PST) In-Reply-To: <1de79840901221745r4149dc30yfcfcb8c8a24ad8ce@mail.gmail.com> References: <6e0e5340901151158n5108ba8ct6af8fb270b10b75b@mail.gmail.com> <6e0e5340901161521t30845197s9529fb5a55dbba13@mail.gmail.com> <6e0e5340901221324o33f1e2b1l53c842ebf9dad9a8@mail.gmail.com> <1de79840901221745r4149dc30yfcfcb8c8a24ad8ce@mail.gmail.com> Date: Thu, 22 Jan 2009 21:08:05 -0800 Message-ID: <6e0e5340901222108i6a5e300fte7fdd1a517fbe049@mail.gmail.com> From: David Ehrmann To: Michael Proto Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Pete French 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jan 2009 05:08:07 -0000 On Thu, Jan 22, 2009 at 5:45 PM, Michael Proto wrote: > On Thu, Jan 22, 2009 at 4:24 PM, David Ehrmann wrote: >> On Fri, Jan 16, 2009 at 3:21 PM, David Ehrmann wrote: >>> On Fri, Jan 16, 2009 at 3:33 AM, Pete French >>> 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." 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. >>> >> >> Ok, here's where it gets interesting: >> >> The next time I saw the import error, I ran zdb -l on the actual dev. >> It couldn't find the labels. So I used dd to grab the first 4k of the >> .eli device and the actual device. Once I got it working, I repeated. >> The data in the first 4k of /dev/ad8 were all 0x00 both times. I'm >> guessing this is reserved, or something. The data in the first 4k of >> /dev/ad8.eli differed between runs (so zdb -l is probably right about >> not finding the label). >> >> In the /dev/ad8.eli that zfs doesn't recognize, I found a 16 byte >> string that was repeated a lot, but it was also repeated in another >> place: the good /dev/ad10.eli (though the offsets were different). >> The other weird thing: the good and bad /dev/ad8.eli look a lot alike: >> one 16 byte string, then another that gets repeated, then another 16 >> byte string randomly shows up at 0x200. >> >> Why the same data appear in the bad ad8.eli as the good ad10.eli, I'm >> not sure (I do have the same password and no keyfile with geli), but >> the patterns of data looking the same make me think something's wrong >> with the encryption. It's using 128 bit AES-CBC, and these patterns >> would not be hidden by it (128 bits == 16 bytes). >> >> I'm using a Via C7 CPU's padlock cryptographic accelerator, and geli >> reports this. I'm guessing this is either a padlock or a geli bug. >> >> I can't reliably reproduce this problem, but doing it with padlock off >> might be a good test. >> _______________________________________________ >> 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 saw something similar (minus zfs) when I was playing with padlock > and geli on my C7-Esther fileserver. When trying to mount a geli > partition I'd intermittently get a bad decryption key error. Run the > same command again to mount the partition and it'd work fine. This was > using both password and key-file operations. IIRC when I disabled > padlock acceleration it worked fine in my limited testing. That was > 6.4, now that I'm on 7.1 it might be worth looking at again. I just got around to trying it without padlock. I tried to replicate the problem 5 or 6 times, but no luck. This is 7.1. It *sounds* like a padlock problem, but I'd like to see it make the same mistake with a file or memory backed md device. Anyway, that this point, I can pretty much rule out zfs as the culprit. From owner-freebsd-stable@FreeBSD.ORG Fri Jan 23 05:12: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 7514E1065670 for ; Fri, 23 Jan 2009 05:12:07 +0000 (UTC) (envelope-from ehrmann@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 24C1D8FC17 for ; Fri, 23 Jan 2009 05:12:06 +0000 (UTC) (envelope-from ehrmann@gmail.com) Received: by yx-out-2324.google.com with SMTP id 8so1908642yxb.13 for ; Thu, 22 Jan 2009 21:12:06 -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=7LU29ujuhytC2OghA7QP6KGvFkmfvVmfB3bXw+dObHQ=; b=DjKKGk36IIuR8+DDQaRSCGQasKhrP16qXd7jy6ZVGO5FVMGlY9E91+HLMN97Whf2sV tJ626UAUC6MfTHzGQuv/l2ZG/zDHDNeGRz8ZrcBav5pnOKVKGmnVzVz8LU8rBkH/XkBL t31NxOx2mJQnXf1UOZ8brsoVzDhCDj4G3Fogo= 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=Zx+OKYGBL3LxvpJg+exnJyzn0jUoiqiZjpNKAKqR4F0s4ZYbMK9n9px5ef6x1iR+Os F7uaR6EjysCx4Jtgw5uM1xrZEcLtkGunRcXBrXe5YOKuWSakJLDHeA/WNQA6BAeDjmjj KGiy3noHILGbOFEtR/XgSyUZsCWeoxJqelCwY= MIME-Version: 1.0 Received: by 10.100.93.19 with SMTP id q19mr496548anb.156.1232687526482; Thu, 22 Jan 2009 21:12:06 -0800 (PST) In-Reply-To: <6e0e5340901222108i6a5e300fte7fdd1a517fbe049@mail.gmail.com> References: <6e0e5340901151158n5108ba8ct6af8fb270b10b75b@mail.gmail.com> <6e0e5340901161521t30845197s9529fb5a55dbba13@mail.gmail.com> <6e0e5340901221324o33f1e2b1l53c842ebf9dad9a8@mail.gmail.com> <1de79840901221745r4149dc30yfcfcb8c8a24ad8ce@mail.gmail.com> <6e0e5340901222108i6a5e300fte7fdd1a517fbe049@mail.gmail.com> Date: Thu, 22 Jan 2009 21:12:06 -0800 Message-ID: <6e0e5340901222112x159409c5xd2fd93e32b020c0f@mail.gmail.com> From: David Ehrmann To: Michael Proto Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Pete French 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jan 2009 05:12:07 -0000 On Thu, Jan 22, 2009 at 9:08 PM, David Ehrmann wrote: > On Thu, Jan 22, 2009 at 5:45 PM, Michael Proto wrote: >> On Thu, Jan 22, 2009 at 4:24 PM, David Ehrmann wrote: >>> On Fri, Jan 16, 2009 at 3:21 PM, David Ehrmann wrote: >>>> On Fri, Jan 16, 2009 at 3:33 AM, Pete French >>>> 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." 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. >>>> >>> >>> Ok, here's where it gets interesting: >>> >>> The next time I saw the import error, I ran zdb -l on the actual dev. >>> It couldn't find the labels. So I used dd to grab the first 4k of the >>> .eli device and the actual device. Once I got it working, I repeated. >>> The data in the first 4k of /dev/ad8 were all 0x00 both times. I'm >>> guessing this is reserved, or something. The data in the first 4k of >>> /dev/ad8.eli differed between runs (so zdb -l is probably right about >>> not finding the label). >>> >>> In the /dev/ad8.eli that zfs doesn't recognize, I found a 16 byte >>> string that was repeated a lot, but it was also repeated in another >>> place: the good /dev/ad10.eli (though the offsets were different). >>> The other weird thing: the good and bad /dev/ad8.eli look a lot alike: >>> one 16 byte string, then another that gets repeated, then another 16 >>> byte string randomly shows up at 0x200. >>> >>> Why the same data appear in the bad ad8.eli as the good ad10.eli, I'm >>> not sure (I do have the same password and no keyfile with geli), but >>> the patterns of data looking the same make me think something's wrong >>> with the encryption. It's using 128 bit AES-CBC, and these patterns >>> would not be hidden by it (128 bits == 16 bytes). >>> >>> I'm using a Via C7 CPU's padlock cryptographic accelerator, and geli >>> reports this. I'm guessing this is either a padlock or a geli bug. >>> >>> I can't reliably reproduce this problem, but doing it with padlock off >>> might be a good test. >>> _______________________________________________ >>> 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 saw something similar (minus zfs) when I was playing with padlock >> and geli on my C7-Esther fileserver. When trying to mount a geli >> partition I'd intermittently get a bad decryption key error. Run the >> same command again to mount the partition and it'd work fine. This was >> using both password and key-file operations. IIRC when I disabled >> padlock acceleration it worked fine in my limited testing. That was >> 6.4, now that I'm on 7.1 it might be worth looking at again. > > I just got around to trying it without padlock. I tried to replicate > the problem 5 or 6 times, but no luck. > > This is 7.1. > > It *sounds* like a padlock problem, but I'd like to see it make the > same mistake with a file or memory backed md device. Anyway, that > this point, I can pretty much rule out zfs as the culprit. > Or geli... Any success (not intermittent) reports with a hifn or broadcom accelerator and geli? From owner-freebsd-stable@FreeBSD.ORG Fri Jan 23 08:05:05 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 74CC11065674; Fri, 23 Jan 2009 08:05:05 +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 383098FC1B; Fri, 23 Jan 2009 08:05:04 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id B3B0B73098; Fri, 23 Jan 2009 09:10:28 +0100 (CET) Date: Fri, 23 Jan 2009 09:10:28 +0100 From: Luigi Rizzo To: stable@freebsd.org Message-ID: <20090123081028.GA38763@onelab2.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Cc: oleg@freebsd.org, re@freebsd.org Subject: backporting dummynet's q_time change ? (svn 184414) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jan 2009 08:05:06 -0000 in your logmessage for the q_time change in dummynet http://svn.freebsd.org/viewvc/base?view=revision&revision=184414 mentions an ABI change that would prevent backporting. However, as far as I can tell, the kernel side of the change is fully self-contained in the ip_dummynet module, and the only side effect on an out-of-sync userland (/sbin/ipfw) is that you would not be able to run "ipfw pipe show" -- but you can still configure ipfw rules and pipes and tables without problems. It seems to me that the change is sufficiently useful to deserve a MFC, and the side effects are negligible and do not prevent an upgrade with the usual sequence (installkernel-reboot-installworld) Any objection to an MFC ? cheers luigi From owner-freebsd-stable@FreeBSD.ORG Fri Jan 23 09:09:03 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 6F2A6106566C; Fri, 23 Jan 2009 09:09:03 +0000 (UTC) (envelope-from oleg@lath.rinet.ru) Received: from lath.rinet.ru (lath.rinet.ru [195.54.192.90]) by mx1.freebsd.org (Postfix) with ESMTP id 2981E8FC12; Fri, 23 Jan 2009 09:09:02 +0000 (UTC) (envelope-from oleg@lath.rinet.ru) Received: by lath.rinet.ru (Postfix, from userid 222) id 1F21E7018; Fri, 23 Jan 2009 11:53:37 +0300 (MSK) Date: Fri, 23 Jan 2009 11:53:37 +0300 From: Oleg Bulyzhin To: Luigi Rizzo Message-ID: <20090123085337.GB54838@lath.rinet.ru> References: <20090123081028.GA38763@onelab2.iet.unipi.it> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090123081028.GA38763@onelab2.iet.unipi.it> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: stable@freebsd.org, re@freebsd.org Subject: Re: backporting dummynet's q_time change ? (svn 184414) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jan 2009 09:09:03 -0000 On Fri, Jan 23, 2009 at 09:10:28AM +0100, Luigi Rizzo wrote: > in your logmessage for the q_time change in dummynet > http://svn.freebsd.org/viewvc/base?view=revision&revision=184414 > > mentions an ABI change that would prevent backporting. > > However, as far as I can tell, the kernel side of the change is > fully self-contained in the ip_dummynet module, and the only > side effect on an out-of-sync userland (/sbin/ipfw) is that > you would not be able to run "ipfw pipe show" -- but you > can still configure ipfw rules and pipes and tables without > problems. > > It seems to me that the change is sufficiently useful to deserve > a MFC, and the side effects are negligible and do not prevent an > upgrade with the usual sequence (installkernel-reboot-installworld) > > Any objection to an MFC ? > > cheers > luigi > > _______________________________________________ > 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" Have you seen this? http://svn.freebsd.org/changeset/base/184506 -- Oleg. ================================================================ === Oleg Bulyzhin -- OBUL-RIPN -- OBUL-RIPE -- oleg@rinet.ru === ================================================================ From owner-freebsd-stable@FreeBSD.ORG Fri Jan 23 09:17:48 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 6835C10656CC; Fri, 23 Jan 2009 09:17:48 +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 288588FC08; Fri, 23 Jan 2009 09:17:47 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 74B0873098; Fri, 23 Jan 2009 10:23:12 +0100 (CET) Date: Fri, 23 Jan 2009 10:23:12 +0100 From: Luigi Rizzo To: Oleg Bulyzhin Message-ID: <20090123092312.GC40642@onelab2.iet.unipi.it> References: <20090123081028.GA38763@onelab2.iet.unipi.it> <20090123085337.GB54838@lath.rinet.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090123085337.GB54838@lath.rinet.ru> User-Agent: Mutt/1.4.2.3i Cc: stable@FreeBSD.org, re@FreeBSD.org Subject: Re: backporting dummynet's q_time change ? (svn 184414) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jan 2009 09:17:49 -0000 On Fri, Jan 23, 2009 at 11:53:37AM +0300, Oleg Bulyzhin wrote: > On Fri, Jan 23, 2009 at 09:10:28AM +0100, Luigi Rizzo wrote: > > in your logmessage for the q_time change in dummynet > > http://svn.freebsd.org/viewvc/base?view=revision&revision=184414 > > > > mentions an ABI change that would prevent backporting. > > > > However, as far as I can tell, the kernel side of the change is > > fully self-contained in the ip_dummynet module, and the only > > side effect on an out-of-sync userland (/sbin/ipfw) is that > > you would not be able to run "ipfw pipe show" -- but you > > can still configure ipfw rules and pipes and tables without > > problems. > > > > It seems to me that the change is sufficiently useful to deserve > > a MFC, and the side effects are negligible and do not prevent an > > upgrade with the usual sequence (installkernel-reboot-installworld) > > > > Any objection to an MFC ? > > > > cheers > > luigi > > > > _______________________________________________ > > 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" > > Have you seen this? > http://svn.freebsd.org/changeset/base/184506 this is also in RELENG_7 but i am not sure whether this workaround has any drawback e.g., when curr_time passes a 32-bit boundary there seems to be an incorrect setting of q->numbytes @@ -1382,7 +1383,7 @@ if (q->head != m) /* Flow was not idle, we are done. */ goto done; - if (q->q_time < curr_time) + if (q->q_time < (uint32_t)curr_time) q->numbytes = io_fast ? fs->pipe->bandwidth : 0; q->q_time = curr_time; cheers luigi From owner-freebsd-stable@FreeBSD.ORG Fri Jan 23 09:44:22 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 117B31065672; Fri, 23 Jan 2009 09:44:22 +0000 (UTC) (envelope-from oleg@lath.rinet.ru) Received: from lath.rinet.ru (lath.rinet.ru [195.54.192.90]) by mx1.freebsd.org (Postfix) with ESMTP id BF8658FC13; Fri, 23 Jan 2009 09:44:21 +0000 (UTC) (envelope-from oleg@lath.rinet.ru) Received: by lath.rinet.ru (Postfix, from userid 222) id BAF427015; Fri, 23 Jan 2009 12:44:20 +0300 (MSK) Date: Fri, 23 Jan 2009 12:44:20 +0300 From: Oleg Bulyzhin To: Luigi Rizzo Message-ID: <20090123094420.GC54838@lath.rinet.ru> References: <20090123081028.GA38763@onelab2.iet.unipi.it> <20090123085337.GB54838@lath.rinet.ru> <20090123092312.GC40642@onelab2.iet.unipi.it> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090123092312.GC40642@onelab2.iet.unipi.it> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: stable@FreeBSD.org, re@FreeBSD.org Subject: Re: backporting dummynet's q_time change ? (svn 184414) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jan 2009 09:44:22 -0000 On Fri, Jan 23, 2009 at 10:23:12AM +0100, Luigi Rizzo wrote: > this is also in RELENG_7 but i am not sure whether this workaround > has any drawback e.g., when curr_time passes a 32-bit boundary > there seems to be an incorrect setting of q->numbytes Workaround is fine in average. It may fail for: 1) _very_ idle flow (more than 2^32 ticks) while calculating q->avg 2) any flow once per 2^32 ticks then q_time will be updated and things will be ok again. -- Oleg. ================================================================ === Oleg Bulyzhin -- OBUL-RIPN -- OBUL-RIPE -- oleg@rinet.ru === ================================================================ From owner-freebsd-stable@FreeBSD.ORG Fri Jan 23 10:15:50 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 11A76106564A; Fri, 23 Jan 2009 10:15:50 +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 C69B58FC16; Fri, 23 Jan 2009 10:15:49 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 3FF6373098; Fri, 23 Jan 2009 11:21:14 +0100 (CET) Date: Fri, 23 Jan 2009 11:21:14 +0100 From: Luigi Rizzo To: Oleg Bulyzhin Message-ID: <20090123102114.GA42867@onelab2.iet.unipi.it> References: <20090123081028.GA38763@onelab2.iet.unipi.it> <20090123085337.GB54838@lath.rinet.ru> <20090123092312.GC40642@onelab2.iet.unipi.it> <20090123094420.GC54838@lath.rinet.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090123094420.GC54838@lath.rinet.ru> User-Agent: Mutt/1.4.2.3i Cc: stable@FreeBSD.org, re@FreeBSD.org Subject: Re: backporting dummynet's q_time change ? (svn 184414) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jan 2009 10:15:50 -0000 On Fri, Jan 23, 2009 at 12:44:20PM +0300, Oleg Bulyzhin wrote: > On Fri, Jan 23, 2009 at 10:23:12AM +0100, Luigi Rizzo wrote: > > > this is also in RELENG_7 but i am not sure whether this workaround > > has any drawback e.g., when curr_time passes a 32-bit boundary > > there seems to be an incorrect setting of q->numbytes > > Workaround is fine in average. It may fail for: > 1) _very_ idle flow (more than 2^32 ticks) while calculating q->avg > 2) any flow once per 2^32 ticks > then q_time will be updated and things will be ok again. understand - my question is whether there is strong objection in applying the real fix (the one in HEAD) rather than this workaround. In my opinion the MFC is quite safe as I explained. cheers luigi From owner-freebsd-stable@FreeBSD.ORG Fri Jan 23 10:25:53 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 E37DB1065670; Fri, 23 Jan 2009 10:25:53 +0000 (UTC) (envelope-from oleg@lath.rinet.ru) Received: from lath.rinet.ru (lath.rinet.ru [195.54.192.90]) by mx1.freebsd.org (Postfix) with ESMTP id 9C3DE8FC13; Fri, 23 Jan 2009 10:25:53 +0000 (UTC) (envelope-from oleg@lath.rinet.ru) Received: by lath.rinet.ru (Postfix, from userid 222) id 917CE7016; Fri, 23 Jan 2009 13:25:52 +0300 (MSK) Date: Fri, 23 Jan 2009 13:25:52 +0300 From: Oleg Bulyzhin To: Luigi Rizzo Message-ID: <20090123102552.GD54838@lath.rinet.ru> References: <20090123081028.GA38763@onelab2.iet.unipi.it> <20090123085337.GB54838@lath.rinet.ru> <20090123092312.GC40642@onelab2.iet.unipi.it> <20090123094420.GC54838@lath.rinet.ru> <20090123102114.GA42867@onelab2.iet.unipi.it> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090123102114.GA42867@onelab2.iet.unipi.it> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: stable@FreeBSD.org, re@FreeBSD.org Subject: Re: backporting dummynet's q_time change ? (svn 184414) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jan 2009 10:25:54 -0000 On Fri, Jan 23, 2009 at 11:21:14AM +0100, Luigi Rizzo wrote: > On Fri, Jan 23, 2009 at 12:44:20PM +0300, Oleg Bulyzhin wrote: > > On Fri, Jan 23, 2009 at 10:23:12AM +0100, Luigi Rizzo wrote: > > > > > this is also in RELENG_7 but i am not sure whether this workaround > > > has any drawback e.g., when curr_time passes a 32-bit boundary > > > there seems to be an incorrect setting of q->numbytes > > > > Workaround is fine in average. It may fail for: > > 1) _very_ idle flow (more than 2^32 ticks) while calculating q->avg > > 2) any flow once per 2^32 ticks > > then q_time will be updated and things will be ok again. > > understand - my question is whether there is strong objection > in applying the real fix (the one in HEAD) rather than this > workaround. > In my opinion the MFC is quite safe as I explained. > > cheers > luigi I see. I have no objection but i think this is policy question so i'm not the right person to ask. -- Oleg. ================================================================ === Oleg Bulyzhin -- OBUL-RIPN -- OBUL-RIPE -- oleg@rinet.ru === ================================================================ From owner-freebsd-stable@FreeBSD.ORG Fri Jan 23 12:10: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 1D9F810656C8; Fri, 23 Jan 2009 12:10:44 +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 D21D28FC0C; Fri, 23 Jan 2009 12:10:43 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 24B7773098; Fri, 23 Jan 2009 13:16:08 +0100 (CET) Date: Fri, 23 Jan 2009 13:16:08 +0100 From: Luigi Rizzo To: Oleg Bulyzhin Message-ID: <20090123121608.GC46033@onelab2.iet.unipi.it> References: <20090123081028.GA38763@onelab2.iet.unipi.it> <20090123085337.GB54838@lath.rinet.ru> <20090123092312.GC40642@onelab2.iet.unipi.it> <20090123094420.GC54838@lath.rinet.ru> <20090123102114.GA42867@onelab2.iet.unipi.it> <20090123102552.GD54838@lath.rinet.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090123102552.GD54838@lath.rinet.ru> User-Agent: Mutt/1.4.2.3i Cc: stable@FreeBSD.org, re@FreeBSD.org Subject: Re: backporting dummynet's q_time change ? (svn 184414) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jan 2009 12:10:45 -0000 On Fri, Jan 23, 2009 at 01:25:52PM +0300, Oleg Bulyzhin wrote: ... > > understand - my question is whether there is strong objection > > in applying the real fix (the one in HEAD) rather than this > > workaround. > > In my opinion the MFC is quite safe as I explained. > > > > cheers > > luigi > > I see. I have no objection but i think this is policy question so i'm not the > right person to ask. your feedback on technical issues is still important and a prerequisite for acting. The policy is there to prevent, among other things, breakage in upgrades, which in this case are not possible so the policy should not affect us. cheers luigi From owner-freebsd-stable@FreeBSD.ORG Fri Jan 23 12:43:21 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 E13CB1065674 for ; Fri, 23 Jan 2009 12:43:21 +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 9ED9A8FC08 for ; Fri, 23 Jan 2009 12:43:21 +0000 (UTC) (envelope-from antik@bsd.ee) Received: from localhost (localhost.localdomain [127.0.0.1]) by sorbesgroup.com (Postfix) with ESMTP id 79D213C51649 for ; Fri, 23 Jan 2009 14:32:16 +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 26602-01 for ; Fri, 23 Jan 2009 14:32:15 +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 8FDB33C51610 for ; Fri, 23 Jan 2009 14:32:15 +0200 (EET) Message-ID: <4979BB69.3080407@bsd.ee> Date: Fri, 23 Jan 2009 14:43:21 +0200 From: Andrei Kolu 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-Virus-Scanned: amavisd-new at localhost Cc: Subject: iscsi unsupported INQUIRY X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jan 2009 12:43:22 -0000 I configured iscsi-target on FreeBSD 7.1 and after I mounted target from VMware ESXi I got this following error message: ------------------------------------------------------------------------------------------------------------------- Jan 23 14:26:35 srv6 iscsi-target: pid 11892:disk.c:956: ***ERROR*** Unsupported INQUIRY VPD page 85 Jan 23 14:26:35 srv6 last message repeated 1000 times ------------------------------------------------------------------------------------------------------------------- Actually I see no strange behaviour or something wrong in server configuration- just does not understand what this error message means? From owner-freebsd-stable@FreeBSD.ORG Fri Jan 23 13:20: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 6B99010656BB for ; Fri, 23 Jan 2009 13:20:22 +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 E3F0A8FC24 for ; Fri, 23 Jan 2009 13:20:21 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1LQLxI-0001Vz-4O for freebsd-stable@freebsd.org; Fri, 23 Jan 2009 13:20:16 +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 ; Fri, 23 Jan 2009 13:20:16 +0000 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 23 Jan 2009 13:20:16 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Ivan Voras Date: Fri, 23 Jan 2009 14:19:54 +0100 Lines: 50 Message-ID: References: <4979BB69.3080407@bsd.ee> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigD5D13803A6DFDACB499C8F58" X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 2.0.0.19 (X11/20090105) In-Reply-To: <4979BB69.3080407@bsd.ee> X-Enigmail-Version: 0.95.0 Sender: news Subject: Re: iscsi unsupported INQUIRY X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jan 2009 13:20:23 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigD5D13803A6DFDACB499C8F58 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Andrei Kolu wrote: > I configured iscsi-target on FreeBSD 7.1 and after I mounted target fro= m > VMware ESXi I got this following error message: > -----------------------------------------------------------------------= -------------------------------------------- >=20 > Jan 23 14:26:35 srv6 iscsi-target: pid 11892:disk.c:956: ***ERROR*** > Unsupported INQUIRY VPD page 85 > Jan 23 14:26:35 srv6 last message repeated 1000 times > -----------------------------------------------------------------------= -------------------------------------------- >=20 >=20 > Actually I see no strange behaviour or something wrong in server > configuration- just does not understand what this error message means? Googling suggests VPD page 85 is a part of yet unfinished specification for communicating web management URL's between devices and, presumably, users. It should probably not be logged so insistently :) ref: (via induction): http://209.85.129.132/search?q=3Dcache:aFHfjpdAyRYJ:www.t10.org/cgi-bin/a= c.pl%3Ft%3Dd%26f%3D03-316r1.pdf+scsi+vpd+page+code+85h and http://209.85.129.132/search?q=3Dcache:U9HHcy5MMqIJ:www.t10.org/cgi-bin/a= c.pl%3Ft%3Dd%26f%3D03-247r0.pdf+scsi+03-183&hl=3Den&ct=3Dclnk&cd=3D1 --------------enigD5D13803A6DFDACB499C8F58 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 iD8DBQFJecP6ldnAQVacBcgRAvSKAJ941J2fCzzjIir0BNMA89BjsAqGGwCfWkef 3+NTIQ/XIjHeeC08Qxv+Djs= =SotN -----END PGP SIGNATURE----- --------------enigD5D13803A6DFDACB499C8F58-- From owner-freebsd-stable@FreeBSD.ORG Fri Jan 23 15:58: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 86AE3106566B for ; Fri, 23 Jan 2009 15:58:04 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from dhcp-172-16-22-158.lon.corp.google.com (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 02A7F8FC0C; Fri, 23 Jan 2009 15:58:03 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <4979E90B.8070403@FreeBSD.org> Date: Fri, 23 Jan 2009 15:58:03 +0000 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) MIME-Version: 1.0 To: Pete Carah References: <49747F10.7050801@altadena.net> <4974EC4C.4020004@FreeBSD.org> <49754D2D.2030902@altadena.net> In-Reply-To: <49754D2D.2030902@altadena.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: Fri, 23 Jan 2009 15:58:04 -0000 Pete Carah wrote: > Well, following up on my own reply earlier, I csup'd releng_7 with a > date of last dec 1; the result works fine > in the laptop. I'll reload the eastern soekris tonight and see how it > does. If the soekris is fine also then this gives a data point for > whenever the bad commit(s) happened. > > I had apparently made the mistaken assumption that a general release > should be better debugged than the work-in-progress leading up to it... I'm sorry FreeBSD has failed to live up to your expectations. As ever, we strive to fix more bugs than we introduce, but in a changing codebase this is never possible to guarantee or to always achieve. Kris From owner-freebsd-stable@FreeBSD.ORG Fri Jan 23 18:26:21 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 32B3B106566C for ; Fri, 23 Jan 2009 18:26:21 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by mx1.freebsd.org (Postfix) with ESMTP id 0896A8FC08 for ; Fri, 23 Jan 2009 18:26:21 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.fastmail.fm (Postfix) with ESMTP id 61AB325602D for ; Fri, 23 Jan 2009 13:26:20 -0500 (EST) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Fri, 23 Jan 2009 13:26:20 -0500 X-Sasl-enc: VciPJduHHLPXRsYxzBVkAVthBf4KQt7cdoiKzEadxuka 1232735179 Received: from empiric.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTPSA id C69A7B371 for ; Fri, 23 Jan 2009 13:26:19 -0500 (EST) Message-ID: <497A0BCA.5070904@incunabulum.net> Date: Fri, 23 Jan 2009 18:26:18 +0000 From: Bruce M Simpson User-Agent: Thunderbird 2.0.0.19 (X11/20090116) MIME-Version: 1.0 To: FreeBSD STABLE X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: A nasty ataraid experience. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jan 2009 18:26:21 -0000 Hi there, I had a bit of a nasty experience this week with ataraid(4). I thought I would summarize the issues I ran into so hopefully others can benefit from my nasty experience, should they experience catastophic failure of a Pseudo-RAID. I was surprised that I was unable to find much in the way of similar experience in forums. Luckily, I didn't lose any data, thanks to mr ports/sysutils/scan_ffs. Bog simple setup. Gigabyte VM900M motherboard, Intel Core Duo T4300. JMicron JMB363 controller, two SATA ports, RAID mode. Two Seagate 160GB drives. I'll skip the stuff about the strange loop I got into with having to recreate the MBR and disklabels after they got trashed -- suffice to say, BACK THEM UP... BACK THEM UP... --- 1. atacontrol rebuild. There are a few issues here. I'm partly to blame here for not reading the documentation in the handbook about the rebuild process -- however -- hilarity ensued. Following the rebuild procedure in the Handbook, if you try to run "atacontrol rebuild" from the FreeBSD 7.1 LiveFS, it'll break. I ran it thinking that it had some kind of magic in it which I couldn't achieve using dd alone, which is partly true, but also partly not true. It has a hardcoded path to /usr/bin/nice, which it runs using the system() libc call, and unfortunately, the LiveFS is rooted at /mnt2. It does this after it issues an ioctl() to tell the ATA driver to copy and rewrite the meta-data to the new "spare" drive. Ooops. At this point the state of the array is inconsistent. "atacontrol status" will report the array as REBUILDING, despite the fact that the dd job never kicked off. Because the metadata has now been rewritten, and the ataraid driver has entered a REBUILDING state, you can't stop it, and it won't rebuild. I also found that the default dd block size it uses, 1m, didn't work with my drives -- I had to dd manually with a 64KB block size to get things to work, otherwise I got lots and lots of ATA read/write errors related to trying to write beyond the last part of the disk. The drives themselves are fine, though. HOMEWORK: "atacontrol rebuild" needs to be taught to play nice when run in a catastrophic recovery situation; the path stuff needs to be fixed, and perhaps some magic should be added to allow the metadata to be zapped when Really Bad Stuff happens. --- 2. raid metadata, and drive sizes. OK, the tradeoff with ataraid is that it is pseudo-raid. That's understood, however, it's easy for the metadata to be downright out of sync with After my bad experience with "atacontrol rebuild" from the LiveFS, to trick FreeBSD back into understanding that the array was in fact degraded, I had to read the ataraid driver code to figure out which LBA it was expecting to see the metadata at, and then wipe that out with dd. It doesn't help that the drives themselves are of different sizes. So. Imagine the hilarity when I just swap the drives and try to rebuild the array. Ooops. HOMEWORK: Is there a way to use the system partition stuff e.g. ATA SET MAX ADDRESS to get around this? Obviously it would mean losing a few sectors at the end of the drive, but it's a small price to pay for sanity with Pseudo-RAID. --- 2. RAID BIOS. I have been using a JMicron 36x PCI-e controller. Unfortunately, when stuff like the MBR is broken, it says nothing informative -- it will just skip to the next INT 19h handler. This is more something which should be thrown at the BIOS vendors -- I don't believe there isn't enough space in there to print a message which says "The drive geometry is invalid". HOMEWORK: Someone needs to throw a wobbly at the vendors. --- 3. fdisk and drive geometry. The root cause of my boot failure, it turned out, was that the drive geometry was "wrong" for the JMicron SATA RAID BIOS. It turns out sysinstall's guess at the drive geometry is "right" for LBA mode (C/H/S n/255/63), and thus "right" for my SATA controller BIOS. fdisk, however, wants to use a C/H/S of n/16/63 by default. Profanity ensues. HOMEWORK: Why does fdisk still assume 16 heads... ? Perhaps we should have a switch to tell it to use the LBA-style C/H/S converted geometry? --- Redux I understand why organisations pay good money for hardware RAID controllers, but given that time has moved on, this is kinda effed up. I shouldn't, in an ideal world, have to bust hours of ninja admin moves just to get a single RAID-ed home server back up and running. I also now understand that I can't rely on RAID alone to keep the integrity of my own data -- there is no substitute for backups, I just wish there were realistic backup solutions for individuals trying to do things with technology right now, without paying over the odds, or being ripped off. A "good enough" cheap solution is what individuals often end up using, to get things going in life with minimal resources or wastage. I hope others benefit from my experience. cheers BMS P.S. Big thanks to Doug White for helping me to get /etc recreated after bits of it got trashed. From owner-freebsd-stable@FreeBSD.ORG Fri Jan 23 19:35: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 A3D121065673 for ; Fri, 23 Jan 2009 19:35:24 +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 172DC8FC1A for ; Fri, 23 Jan 2009 19:35:23 +0000 (UTC) (envelope-from amarat@ksu.ru) X-IronPort-AV: E=Sophos;i="4.37,314,1231102800"; d="scan'208";a="1336445" Received: from mail.ksu.ru (HELO ruby.ksu.ru) ([193.232.252.56]) by iout.kzn.ru with ESMTP; 23 Jan 2009 22:35:21 +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 n0NJVwQ2007249; Fri, 23 Jan 2009 19:31:59 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 n0NJY70X063106; Fri, 23 Jan 2009 22:34:07 +0300 (MSK) (envelope-from amarat@ksu.ru) Message-ID: <497A1BAF.9090502@ksu.ru> Date: Fri, 23 Jan 2009 22:34:07 +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: Dan Langille References: <49774BAE.3000809@ksu.ru> <20090122071845.GF4881@alf.bsdes.net> <4978A10A.9060006@langille.org> <7697CDAB-B4E7-480A-B31A-1F54275B8D54@langille.org> In-Reply-To: <7697CDAB-B4E7-480A-B31A-1F54275B8D54@langille.org> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: Victor Balada Diaz , freebsd-stable@freebsd.org, Pete French 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jan 2009 19:35:25 -0000 Dan Langille wrote: > > On Jan 22, 2009, at 11:38 AM, Dan Langille wrote: > >> Victor Balada Diaz wrote: >>> On Wed, Jan 21, 2009 at 07:22:06PM +0300, Marat N.Afanasyev 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! >>>>> >>>>> -pete. >>>>> >>>> it's a kind of magic, really. I built a new kernel with KDB and DDB >>>> and after 1 day, 13:15 I'm still waiting for storm to arrive. And I >>>> added >>>> hw.acpi.osname="Linux" to /boot/loader.conf. >>> Try doing lots of IO and you will get the problem soon. You might >>> want to try: >>> while true; do dd if=/dev/zero of=BAH bs=1M count=1024; sync; done >> >> FWIW, last night I changed the address of the comm port IO in my BIOS. >> Then I ran the Bacula regression test suite (lots of IO). For my >> machine, once the interrupt storm starts, it continues. I do not know >> if that happens to everyone. >> >> Since changing the address, I have had no interrupt storms. I have >> been running the above IO loop for about ten minutes. >> >> No storm yet (knock on wood). > > > And it's back: > > Jan 22 17:21:46 polo kernel: interrupt storm detected on "irq22:"; > throttling interrupt source > Jan 22 17:23:19 polo kernel: interrupt storm detected on "irq22:"; > throttling interrupt source > Jan 22 17:28:20 polo kernel: interrupt storm detected on "irq22:"; > throttling interrupt source > Jan 22 17:33:20 polo kernel: interrupt storm detected on "irq22:"; > throttling interrupt source > Jan 22 17:38:20 polo kernel: interrupt storm detected on "irq22:"; > throttling interrupt source > > I shall try the hw.acpi.osname="Linux" option now. > > From dmsg: Jan 22 18:10:07 polo kernel: ACPI: Overriding _OS definition > with "Linux" > it works for me for 3 days, 16:27 and still no sign of interrupt storm. and emu10kx0 generates as many as 93 interrupt per second without trouble. What is your situation? -- SY, Marat From owner-freebsd-stable@FreeBSD.ORG Fri Jan 23 19:42: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 5865F1065670 for ; Fri, 23 Jan 2009 19:42:35 +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 290BB8FC16 for ; Fri, 23 Jan 2009 19:42:35 +0000 (UTC) (envelope-from dan@langille.org) Received: from localhost (localhost [127.0.0.1]) by nyi.unixathome.org (Postfix) with ESMTP id BCAB9509BF; Fri, 23 Jan 2009 19:42:34 +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 ZQBmRYU8yG-R; Fri, 23 Jan 2009 19:42:33 +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 7432A509B5 ; Fri, 23 Jan 2009 19:42:33 +0000 (GMT) Message-Id: From: Dan Langille To: Marat N.Afanasyev In-Reply-To: <497A1BAF.9090502@ksu.ru> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Fri, 23 Jan 2009 14:42:31 -0500 References: <49774BAE.3000809@ksu.ru> <20090122071845.GF4881@alf.bsdes.net> <4978A10A.9060006@langille.org> <7697CDAB-B4E7-480A-B31A-1F54275B8D54@langille.org> <497A1BAF.9090502@ksu.ru> X-Mailer: Apple Mail (2.930.3) Cc: Victor Balada Diaz , freebsd-stable@freebsd.org, Pete French 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jan 2009 19:42:35 -0000 On Jan 23, 2009, at 2:34 PM, Marat N.Afanasyev wrote: > Dan Langille wrote: >> On Jan 22, 2009, at 11:38 AM, Dan Langille wrote: >>> Victor Balada Diaz wrote: >>>> On Wed, Jan 21, 2009 at 07:22:06PM +0300, Marat N.Afanasyev 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! >>>>>> >>>>>> -pete. >>>>>> >>>>> it's a kind of magic, really. I built a new kernel with KDB and >>>>> DDB and after 1 day, 13:15 I'm still waiting for storm to >>>>> arrive. And I added >>>>> hw.acpi.osname="Linux" to /boot/loader.conf. >>>> Try doing lots of IO and you will get the problem soon. You might >>>> want to try: >>>> while true; do dd if=/dev/zero of=BAH bs=1M count=1024; sync; done >>> >>> FWIW, last night I changed the address of the comm port IO in my >>> BIOS. Then I ran the Bacula regression test suite (lots of IO). >>> For my machine, once the interrupt storm starts, it continues. I >>> do not know if that happens to everyone. >>> >>> Since changing the address, I have had no interrupt storms. I have >>> been running the above IO loop for about ten minutes. >>> >>> No storm yet (knock on wood). >> And it's back: >> Jan 22 17:21:46 polo kernel: interrupt storm detected on "irq22:"; >> throttling interrupt source >> Jan 22 17:23:19 polo kernel: interrupt storm detected on "irq22:"; >> throttling interrupt source >> Jan 22 17:28:20 polo kernel: interrupt storm detected on "irq22:"; >> throttling interrupt source >> Jan 22 17:33:20 polo kernel: interrupt storm detected on "irq22:"; >> throttling interrupt source >> Jan 22 17:38:20 polo kernel: interrupt storm detected on "irq22:"; >> throttling interrupt source >> I shall try the hw.acpi.osname="Linux" option now. >> From dmsg: Jan 22 18:10:07 polo kernel: ACPI: Overriding _OS >> definition with "Linux" > > it works for me for 3 days, 16:27 and still no sign of interrupt > storm. and emu10kx0 generates as many as 93 interrupt per second > without trouble. > > What is your situation? Fails Jan 23 15:38:20 polo kernel: interrupt storm detected on "irq22:"; throttling interrupt source It started this morning. $ kenv | grep osname hw.acpi.osname="Linux" -- Dan Langille http://langille.org/ From owner-freebsd-stable@FreeBSD.ORG Fri Jan 23 20: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 5AD451065674 for ; Fri, 23 Jan 2009 20:43:37 +0000 (UTC) (envelope-from talon@lpthe.jussieu.fr) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.freebsd.org (Postfix) with ESMTP id DF2548FC13 for ; Fri, 23 Jan 2009 20:43:36 +0000 (UTC) (envelope-from talon@lpthe.jussieu.fr) Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.14.3/jtpda-5.4) with ESMTP id n0NKhZYC033427 for ; Fri, 23 Jan 2009 21:43:35 +0100 (CET) X-Ids: 165 Received: from niobe.lpthe.jussieu.fr (niobe.lpthe.jussieu.fr [134.157.10.41]) by parthe.lpthe.jussieu.fr (Postfix) with ESMTP id 387B189E6E for ; Fri, 23 Jan 2009 21:43:34 +0100 (CET) Received: by niobe.lpthe.jussieu.fr (Postfix, from userid 2005) id 0966351; Fri, 23 Jan 2009 21:43:33 +0100 (CET) Date: Fri, 23 Jan 2009 21:43:33 +0100 From: Michel Talon To: freebsd-stable@freebsd.org Message-ID: <20090123204333.GA97149@lpthe.jussieu.fr> Mail-Followup-To: Michel Talon , freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0.1 (shiva.jussieu.fr [134.157.0.165]); Fri, 23 Jan 2009 21:43:35 +0100 (CET) X-Virus-Scanned: ClamAV 0.94.2/8897/Fri Jan 23 13:59:36 2009 on shiva.jussieu.fr X-Virus-Status: Clean X-Miltered: at jchkmail2.jussieu.fr with ID 497A2BF7.003 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)! X-j-chkmail-Enveloppe: 497A2BF7.003/134.157.10.1/parthe.lpthe.jussieu.fr/parthe.lpthe.jussieu.fr/ X-j-chkmail-Score: MSGID : 497A2BF7.003 on jchkmail2.jussieu.fr : j-chkmail score : . : R=. U=. O=. B=0.009 -> S=0.009 X-j-chkmail-Status: Ham Subject: Re: A nasty ataraid experience. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jan 2009 20:43:37 -0000 Bruce M Simpson wrote: > Following the rebuild procedure in the Handbook, if you try to run > "atacontrol rebuild" from the FreeBSD 7.1 LiveFS, it'll break. I ran it > thinking that it had some kind of magic in it which I couldn't achieve > using dd alone, which is partly true, but also partly not true. > > It has a hardcoded path to /usr/bin/nice, which it runs using the > system() libc call, and unfortunately, the LiveFS is rooted at /mnt2. It > does this after it issues an ioctl() to tell the ATA driver to copy and > rewrite the meta-data to the new "spare" drive. I always use the LiveFS cdromin the following way: chroot /mnt2 set -o emacs mount -t devfs devfs /dev export PAGER=more so that i am exactly in the same situation as on a real machine. > HOMEWORK: Why does fdisk still assume 16 heads... ? Perhaps we should > have a switch to tell it to use the LBA-style C/H/S converted geometry? FreeBSD fdisk is a calamity. > I also now understand that I can't rely on RAID alone to keep the > integrity of my own data -- there is no substitute for backups, I just > wish there were realistic backup solutions for individuals trying to do > things with technology right now, without paying over the odds, or being > ripped off. A solution to keep backups without "paying over the odds" is to backup your data to another hard disk. This doesn't mean using RAID mirror, it means using rsync or similar to copy data regularly. It is preferable that this occurs on another machine, and even better in another geographic location. But even if the backup disk is on the same machine, this protects againts inadvertent deletions of a file or RAID misbehaviors. The risk being that some hardware problem simultaneously corrupts the main storage and the backup. Modern features such as UFS snapshots or better ZFS snapshots allow to produce better backups. -- Michel TALON From owner-freebsd-stable@FreeBSD.ORG Fri Jan 23 22:44: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 F3912106566C for ; Fri, 23 Jan 2009 22:44:29 +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 76B628FC19 for ; Fri, 23 Jan 2009 22:44: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 n0NMiRHl098647; Fri, 23 Jan 2009 23:44: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 n0NMiRmM098646; Fri, 23 Jan 2009 23:44:27 +0100 (CET) (envelope-from olli) Date: Fri, 23 Jan 2009 23:44:27 +0100 (CET) Message-Id: <200901232244.n0NMiRmM098646@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG, bms@incunabulum.net In-Reply-To: <497A0BCA.5070904@incunabulum.net> 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]); Fri, 23 Jan 2009 23:44:28 +0100 (CET) Cc: Subject: Re: A nasty ataraid experience. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG, bms@incunabulum.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jan 2009 22:44:30 -0000 Bruce M Simpson wrote: > [...] > I also now understand that I can't rely on RAID alone to keep the > integrity of my own data -- there is no substitute for backups, That's 100% true. RAID -- even true hardware RAID -- is *never* a substitute for backup. Consider: - Fire. - Theft. - Lightning strike or power surge. - The cleaning woman knocks the tower over. - ... In all of those cases, chances are that both disks in the RAID mirror die. Also, as you mentioned, it doesn't protect agains human errors ("rm *" in the wrong directory and similar things). Backups should always be made to media that can be taken offline and stored in a safe place: Tape, optical disks, hard disks in swappable drive trays, or external drives. > I just wish there were realistic backup solutions for individuals > trying to do things with technology right now, without paying over > the odds, or being ripped off. I think the best solution is to use standard hard disks in external enclosures (USB, Firewire, eSATA). They're fairly cheap these days and easy to handle. Furthermore they're quite fast. For a very simple backup solution I recommend to buy at least two USB disks and use them alternating, so you still have a good backup on the shelf when something catastrophic happens while the other one is connected to your computer. As for the backup software, I simply use "cpdup" (from ports/sysutils/cpdup) to duplicate the file systems. It's fast (copies only changed files), and you can easily restore files after an "rm *" by simply copying them back with cp. (The only gotcha is that cpdup doesn't preserve "holes" in sparse files, but cases are rare where you need that.) Of course you can also treat the disks like tapes and dump(8) to the raw device (or tar, cpio, whatever), if you prefer. YMMV, of course. 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 "We will perhaps eventually be writing only small modules which are identi- fied by name as they are used to build larger ones, so that devices like indentation, rather than delimiters, might become feasible for expressing local structure in the source language." -- Donald E. Knuth, 1974 From owner-freebsd-stable@FreeBSD.ORG Sat Jan 24 01:57: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 A75C2106564A for ; Sat, 24 Jan 2009 01:57:00 +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 4D3A48FC12 for ; Sat, 24 Jan 2009 01:57:00 +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 414642846D for ; Sat, 24 Jan 2009 09:56:59 +0800 (CST) Received: from localhost (tarsier.geekcn.org [211.166.10.233]) by tarsier.geekcn.org (Postfix) with ESMTP id D8EBAEB45F3; Sat, 24 Jan 2009 09:56:58 +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 Tdv0pDcVjNEW; Sat, 24 Jan 2009 09:56:53 +0800 (CST) Received: from charlie.delphij.net (adsl-76-237-33-62.dsl.pltn13.sbcglobal.net [76.237.33.62]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTPSA id 12474EB4D1E; Sat, 24 Jan 2009 09:56:51 +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=jp3BdawwOu/wDBQL3bQftxPtIJ3V+Cf0vzXbk5wfgfqMk7INujVvhdd8qL2pL5/+8 x+cBDZvblfow7zTvSo/iA== Message-ID: <497A755F.7000605@delphij.net> Date: Fri, 23 Jan 2009 17:56:47 -0800 From: Xin LI Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.19 (X11/20090112) MIME-Version: 1.0 To: Stephen Sanders , d@delphij.net References: <497A43DA.8040907@softhammer.net> In-Reply-To: <497A43DA.8040907@softhammer.net> 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: FreeBSD Stable Subject: Re: Heard of this? 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: Sat, 24 Jan 2009 01:57:00 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [redirected from -bugs@ to -stable@] Stephen Sanders wrote: > I'm tracking what I believe to be a bug in 32 bit compat5x. > > The situation is as follows: > > 6.3 amd64 FreeBSD running 32 bit FreeBSD 5.3 applications. On fairly > random intervals, applications core drop in open(), fopen(), and kill() > in the 32 bit compat5x layer. The core usually occur during process > startup. > > A) Does this sound familiar. Nope... Do you have a custom built kernel or is it the stock kernel? Is it possible for you to try running a FreeBSD 7.1-RELEASE kernel? > B) Is there a specific place in the source tree to look for compat5x? Basically compat5x is just library from FreeBSD 5.x, say, 5.4. Cheers, - -- Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAkl6dV8ACgkQi+vbBBjt66DwAACfbhWo08hLNiw5zpnHrwUnFL/E nYcAnR+ReOON9UDbj4zCEj0J8R5YinJw =GZR9 -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Sat Jan 24 04:21: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 EA0FF106564A for ; Sat, 24 Jan 2009 04:21: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 A83AC8FC20 for ; Sat, 24 Jan 2009 04:21:04 +0000 (UTC) (envelope-from dan@langille.org) Received: from localhost (localhost [127.0.0.1]) by nyi.unixathome.org (Postfix) with ESMTP id 4A1DB509C4; Sat, 24 Jan 2009 04:21:04 +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 Ud1U-8s98e+l; Sat, 24 Jan 2009 04:21: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 8E9B7509D3 ; Sat, 24 Jan 2009 04:21:02 +0000 (GMT) Message-Id: <045DAFBB-ACAA-4C43-8A31-38C37D78E586@langille.org> From: Dan Langille To: Marat N.Afanasyev In-Reply-To: <497A1BAF.9090502@ksu.ru> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Fri, 23 Jan 2009 23:21:00 -0500 References: <49774BAE.3000809@ksu.ru> <20090122071845.GF4881@alf.bsdes.net> <4978A10A.9060006@langille.org> <7697CDAB-B4E7-480A-B31A-1F54275B8D54@langille.org> <497A1BAF.9090502@ksu.ru> X-Mailer: Apple Mail (2.930.3) Cc: Victor Balada Diaz , freebsd-stable@freebsd.org, Pete French 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jan 2009 04:21:05 -0000 On Jan 23, 2009, at 2:34 PM, Marat N.Afanasyev wrote: > Dan Langille wrote: >> On Jan 22, 2009, at 11:38 AM, Dan Langille wrote: >>> Victor Balada Diaz wrote: >>>> On Wed, Jan 21, 2009 at 07:22:06PM +0300, Marat N.Afanasyev 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! >>>>>> >>>>>> -pete. >>>>>> >>>>> it's a kind of magic, really. I built a new kernel with KDB and >>>>> DDB and after 1 day, 13:15 I'm still waiting for storm to >>>>> arrive. And I added >>>>> hw.acpi.osname="Linux" to /boot/loader.conf. >>>> Try doing lots of IO and you will get the problem soon. You might >>>> want to try: >>>> while true; do dd if=/dev/zero of=BAH bs=1M count=1024; sync; done >>> >>> FWIW, last night I changed the address of the comm port IO in my >>> BIOS. Then I ran the Bacula regression test suite (lots of IO). >>> For my machine, once the interrupt storm starts, it continues. I >>> do not know if that happens to everyone. >>> >>> Since changing the address, I have had no interrupt storms. I have >>> been running the above IO loop for about ten minutes. >>> >>> No storm yet (knock on wood). >> And it's back: >> Jan 22 17:21:46 polo kernel: interrupt storm detected on "irq22:"; >> throttling interrupt source >> Jan 22 17:23:19 polo kernel: interrupt storm detected on "irq22:"; >> throttling interrupt source >> Jan 22 17:28:20 polo kernel: interrupt storm detected on "irq22:"; >> throttling interrupt source >> Jan 22 17:33:20 polo kernel: interrupt storm detected on "irq22:"; >> throttling interrupt source >> Jan 22 17:38:20 polo kernel: interrupt storm detected on "irq22:"; >> throttling interrupt source >> I shall try the hw.acpi.osname="Linux" option now. >> From dmsg: Jan 22 18:10:07 polo kernel: ACPI: Overriding _OS >> definition with "Linux" > > it works for me for 3 days, 16:27 and still no sign of interrupt > storm. and emu10kx0 generates as many as 93 interrupt per second > without trouble. > > What is your situation? The box has rebooted twice tonight. The first time, it was running the "while true; do dd..." script. The second time, it was not. The box is now up responding to pings, but I cannot ssh to it. I can't get to the console until Monday. -- Dan Langille http://langille.org/ From owner-freebsd-stable@FreeBSD.ORG Sat Jan 24 04:57: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 6F6401065672 for ; Sat, 24 Jan 2009 04:57:38 +0000 (UTC) (envelope-from ehrmann@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.240]) by mx1.freebsd.org (Postfix) with ESMTP id 23EF88FC13 for ; Sat, 24 Jan 2009 04:57:38 +0000 (UTC) (envelope-from ehrmann@gmail.com) Received: by an-out-0708.google.com with SMTP id b38so753995ana.13 for ; Fri, 23 Jan 2009 20:57:37 -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=cJ2u46faDA+MWW3uloMR9phzOG52jJ07xk+0VigtTfM=; b=fnA0fF0fUQsozkMwHQICdEgCLWMT6CrRmROC4+EhRFVgJwInqFLprR76hn55YrO3Qd fyZq9GI83NDAtUfkiBF9kyYO5xEEGN01H1Yn1q2EQQTQP5Sy23Ts9GUSDVkjHTG4XU5E 6IYXoAPIqizMkRCy1MI/b57Wg3e5p5I1ueLYc= 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=Ikb0vS56r7iMzM4njXKJEVNq5HUHPmQwsHGcII4/WPLNNnD3zXbHdBaPk37dbzdEng H+I8MG9VoJIq5cmtHDdaDhyNKSBBZ87EfK8i3qEab1zQbR1DmxYUuCZN661No6ahfzmR uyiHo5RI3sZ0cc1MuW5TOhPln5sdeQ/Jt6w8c= MIME-Version: 1.0 Received: by 10.100.93.17 with SMTP id q17mr307168anb.104.1232773057637; Fri, 23 Jan 2009 20:57:37 -0800 (PST) In-Reply-To: <6e0e5340901222112x159409c5xd2fd93e32b020c0f@mail.gmail.com> References: <6e0e5340901151158n5108ba8ct6af8fb270b10b75b@mail.gmail.com> <6e0e5340901161521t30845197s9529fb5a55dbba13@mail.gmail.com> <6e0e5340901221324o33f1e2b1l53c842ebf9dad9a8@mail.gmail.com> <1de79840901221745r4149dc30yfcfcb8c8a24ad8ce@mail.gmail.com> <6e0e5340901222108i6a5e300fte7fdd1a517fbe049@mail.gmail.com> <6e0e5340901222112x159409c5xd2fd93e32b020c0f@mail.gmail.com> Date: Fri, 23 Jan 2009 20:57:37 -0800 Message-ID: <6e0e5340901232057p4f696455lbbe0bb4e38248837@mail.gmail.com> From: David Ehrmann To: Michael Proto Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Pete French 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jan 2009 04:57:38 -0000 On Thu, Jan 22, 2009 at 9:12 PM, David Ehrmann wrote: > On Thu, Jan 22, 2009 at 9:08 PM, David Ehrmann wrote: >> On Thu, Jan 22, 2009 at 5:45 PM, Michael Proto wrote: >>> On Thu, Jan 22, 2009 at 4:24 PM, David Ehrmann wrote: >>>> On Fri, Jan 16, 2009 at 3:21 PM, David Ehrmann wrote: >>>>> On Fri, Jan 16, 2009 at 3:33 AM, Pete French >>>>> 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." 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. >>>>> >>>> >>>> Ok, here's where it gets interesting: >>>> >>>> The next time I saw the import error, I ran zdb -l on the actual dev. >>>> It couldn't find the labels. So I used dd to grab the first 4k of the >>>> .eli device and the actual device. Once I got it working, I repeated. >>>> The data in the first 4k of /dev/ad8 were all 0x00 both times. I'm >>>> guessing this is reserved, or something. The data in the first 4k of >>>> /dev/ad8.eli differed between runs (so zdb -l is probably right about >>>> not finding the label). >>>> >>>> In the /dev/ad8.eli that zfs doesn't recognize, I found a 16 byte >>>> string that was repeated a lot, but it was also repeated in another >>>> place: the good /dev/ad10.eli (though the offsets were different). >>>> The other weird thing: the good and bad /dev/ad8.eli look a lot alike: >>>> one 16 byte string, then another that gets repeated, then another 16 >>>> byte string randomly shows up at 0x200. >>>> >>>> Why the same data appear in the bad ad8.eli as the good ad10.eli, I'm >>>> not sure (I do have the same password and no keyfile with geli), but >>>> the patterns of data looking the same make me think something's wrong >>>> with the encryption. It's using 128 bit AES-CBC, and these patterns >>>> would not be hidden by it (128 bits == 16 bytes). >>>> >>>> I'm using a Via C7 CPU's padlock cryptographic accelerator, and geli >>>> reports this. I'm guessing this is either a padlock or a geli bug. >>>> >>>> I can't reliably reproduce this problem, but doing it with padlock off >>>> might be a good test. >>>> _______________________________________________ >>>> 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 saw something similar (minus zfs) when I was playing with padlock >>> and geli on my C7-Esther fileserver. When trying to mount a geli >>> partition I'd intermittently get a bad decryption key error. Run the >>> same command again to mount the partition and it'd work fine. This was >>> using both password and key-file operations. IIRC when I disabled >>> padlock acceleration it worked fine in my limited testing. That was >>> 6.4, now that I'm on 7.1 it might be worth looking at again. >> >> I just got around to trying it without padlock. I tried to replicate >> the problem 5 or 6 times, but no luck. >> >> This is 7.1. >> >> It *sounds* like a padlock problem, but I'd like to see it make the >> same mistake with a file or memory backed md device. Anyway, that >> this point, I can pretty much rule out zfs as the culprit. >> > > Or geli... Any success (not intermittent) reports with a hifn or > broadcom accelerator and geli? > I wasn't able to reproduce the problem with two ~100MB disk-backed md devices and just geli. Next up is a real disk. From owner-freebsd-stable@FreeBSD.ORG Sat Jan 24 08:26: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 BF663106564A for ; Sat, 24 Jan 2009 08:26:29 +0000 (UTC) (envelope-from ehrmann@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.249]) by mx1.freebsd.org (Postfix) with ESMTP id 75D018FC18 for ; Sat, 24 Jan 2009 08:26:29 +0000 (UTC) (envelope-from ehrmann@gmail.com) Received: by an-out-0708.google.com with SMTP id b38so765826ana.13 for ; Sat, 24 Jan 2009 00:26:29 -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=3gZbBkda3f4EDWLZ3wRHldopxt8kfo+r5iCh/rq3buY=; b=IJyTlXvclMP1mh30iIDh2mm3RlLqV3K00unGR7YBTNsyXdFM3wIn5z9u/f4LU1BxXp DyLl5ELgYUNeqhx3fxseocj2WfRde9jtsEdjD0WfAopUnz9OSmxd1C+/hDy8VdKK/pFW BIhs/M8VGrNOCNPgPMbeiSjmqU4/fLqXJggLM= 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=FI2i2Eo25IToRAyKjz0oGzU/hmOuhuN4hrf9iGkQM3yILgCsvYGvKayBR60I45BQr3 Cx55Wd0pdlNdJEfaerjq5o+ObRDxeqDdjeD8SfSet5OhNG+0wgfTMx1w2Lx/0PonCNik aYe+bqARg1wmoraPiL7RUTFtF4s4Wi5QLrV2s= MIME-Version: 1.0 Received: by 10.100.168.18 with SMTP id q18mr8027606ane.7.1232785588957; Sat, 24 Jan 2009 00:26:28 -0800 (PST) In-Reply-To: References: <6e0e5340901151158n5108ba8ct6af8fb270b10b75b@mail.gmail.com> <6e0e5340901161521t30845197s9529fb5a55dbba13@mail.gmail.com> <6e0e5340901221324o33f1e2b1l53c842ebf9dad9a8@mail.gmail.com> Date: Sat, 24 Jan 2009 00:26:28 -0800 Message-ID: <6e0e5340901240026o39eb4554u6d8eb8c00ee2adbb@mail.gmail.com> From: David Ehrmann To: Wes Morgan Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Pete French 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jan 2009 08:26:30 -0000 On Thu, Jan 22, 2009 at 8:07 PM, Wes Morgan wrote: > On Thu, 22 Jan 2009, David Ehrmann wrote: > >> On Fri, Jan 16, 2009 at 3:21 PM, David Ehrmann wrote: >> >> In the /dev/ad8.eli that zfs doesn't recognize, I found a 16 byte >> string that was repeated a lot, but it was also repeated in another >> place: the good /dev/ad10.eli (though the offsets were different). >> The other weird thing: the good and bad /dev/ad8.eli look a lot alike: >> one 16 byte string, then another that gets repeated, then another 16 >> byte string randomly shows up at 0x200. > > The "xxx.eli" devices are the decrypted versions, aren't they? ZFS vdev > labels and uberblocks occupy the first 512k of the device, and consist of > virtually identical data, differing only by the GUID that the label claims > to be and a sha256 checksum... So, decrypted, they should all be very, very > similar. You could actually use the label from any device in a pool to > reconstruct the label for any other device. Let me clarify one thing: when zfs has problems reading the device, the data resemble the data when it's read fine, but by resemble, I don't mean values as much as structure. The values are all wrong, but if you overlaid hexdumps, both share repeated patterns. That makes me think it's an encryption problem, but I haven't been able to reproduce it with other configurations. From owner-freebsd-stable@FreeBSD.ORG Sat Jan 24 09:19: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 DE23F106564A for ; Sat, 24 Jan 2009 09:19:22 +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 4E3738FC1A for ; Sat, 24 Jan 2009 09:19:22 +0000 (UTC) (envelope-from amarat@ksu.ru) X-IronPort-AV: E=Sophos;i="4.37,317,1231102800"; d="scan'208";a="1339746" Received: from mail.ksu.ru (HELO ruby.ksu.ru) ([193.232.252.56]) by iout.kzn.ru with ESMTP; 24 Jan 2009 12:19:20 +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 n0O9GFLv013945; Sat, 24 Jan 2009 09:16:15 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 n0O9IVWM016934; Sat, 24 Jan 2009 12:18:31 +0300 (MSK) (envelope-from amarat@ksu.ru) Message-ID: <497ADCE7.2030008@ksu.ru> Date: Sat, 24 Jan 2009 12:18:31 +0300 From: "Marat N.Afanasyev" User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.8.1.19) Gecko/20090124 SeaMonkey/1.1.14 MIME-Version: 1.0 To: Dan Langille References: <49774BAE.3000809@ksu.ru> <20090122071845.GF4881@alf.bsdes.net> <4978A10A.9060006@langille.org> <7697CDAB-B4E7-480A-B31A-1F54275B8D54@langille.org> <497A1BAF.9090502@ksu.ru> <045DAFBB-ACAA-4C43-8A31-38C37D78E586@langille.org> In-Reply-To: <045DAFBB-ACAA-4C43-8A31-38C37D78E586@langille.org> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: Victor Balada Diaz , freebsd-stable@freebsd.org, Pete French 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jan 2009 09:19:23 -0000 Dan Langille wrote: >>> I shall try the hw.acpi.osname="Linux" option now. >>> From dmsg: Jan 22 18:10:07 polo kernel: ACPI: Overriding _OS >>> definition with "Linux" >> >> it works for me for 3 days, 16:27 and still no sign of interrupt >> storm. and emu10kx0 generates as many as 93 interrupt per second >> without trouble. >> >> What is your situation? > > The box has rebooted twice tonight. The first time, it was running the > "while true; do dd..." script. The second time, it was not. > > The box is now up responding to pings, but I cannot ssh to it. I can't > get to the console until Monday. > try to build kernel with KDB and DDB. -- SY, Marat From owner-freebsd-stable@FreeBSD.ORG Sat Jan 24 10:53: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 D6C921065675; Sat, 24 Jan 2009 10:53:50 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from ftp.translate.ru (ftp.translate.ru [195.131.4.140]) by mx1.freebsd.org (Postfix) with ESMTP id 4CA538FC13; Sat, 24 Jan 2009 10:53:50 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from desktop.home.serebryakov.spb.ru (blacklion.dialup.corbina.ru [89.179.122.169]) (Authenticated sender: lev@serebryakov.spb.ru) by ftp.translate.ru (Postfix) with ESMTPA id C523713DF62; Sat, 24 Jan 2009 13:37:34 +0300 (MSK) Date: Sat, 24 Jan 2009 13:37:33 +0300 From: Lev Serebryakov Organization: FreeBSD X-Priority: 3 (Normal) Message-ID: <11410349378.20090124133733@serebryakov.spb.ru> To: freebsd-stable@freebsd.org, freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Cc: Subject: BIND 9.4.3-P1: internal_send: 199.7.83.42#53: Device not configured, where 199.7.83.42 is RANDOM IP address X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lev@FreeBSD.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jan 2009 10:53:51 -0000 Hello, Freebsd-stable. BIND on my new router (7.1-STABLE, BIND 9.4.3-P1) shows bunch of errors on every start and doesn't answer on requests for 30-60 seconds after that. Errors are like this: Jan 24 12:18:12 gateway named[1455]: /usr/src/lib/bind/isc/../../../contrib= /bind9/lib/isc/unix/socket.c:1567: unexpected error: Jan 24 12:18:12 gateway named[1455]: internal_send: 193.0.14.129#53: Device= not configured Jan 24 12:18:12 gateway named[1455]: /usr/src/lib/bind/isc/../../../contrib= /bind9/lib/isc/unix/errno2result.c:111: unexpected error: Jan 24 12:18:12 gateway named[1455]: unable to convert errno to isc_result:= 6: Device not configured Jan 24 12:18:12 gateway named[1455]: /usr/src/lib/bind/isc/../../../contrib= /bind9/lib/isc/unix/socket.c:1567: unexpected error: Jan 24 12:18:12 gateway named[1455]: internal_send: 193.0.14.129#53: Device= not configured Jan 24 12:18:12 gateway named[1455]: /usr/src/lib/bind/isc/../../../contrib= /bind9/lib/isc/unix/errno2result.c:111: unexpected error: Jan 24 12:18:12 gateway named[1455]: unable to convert errno to isc_result:= 6: Device not configured Jan 24 12:18:12 gateway named[1455]: /usr/src/lib/bind/isc/../../../contrib= /bind9/lib/isc/unix/socket.c:1567: unexpected error: Jan 24 12:18:12 gateway named[1455]: internal_send: 193.0.14.129#53: Device= not configured Jan 24 12:18:12 gateway named[1455]: /usr/src/lib/bind/isc/../../../contrib= /bind9/lib/isc/unix/errno2result.c:111: unexpected error: Jan 24 12:18:12 gateway named[1455]: unable to convert errno to isc_result:= 6: Device not configured Jan 24 12:18:12 gateway named[1455]: /usr/src/lib/bind/isc/../../../contrib= /bind9/lib/isc/unix/socket.c:1567: unexpected error: Jan 24 12:18:12 gateway named[1455]: internal_send: 193.0.14.129#53: Device= not configured Jan 24 12:18:12 gateway named[1455]: /usr/src/lib/bind/isc/../../../contrib= /bind9/lib/isc/unix/errno2result.c:111: unexpected error: Jan 24 12:18:12 gateway named[1455]: unable to convert errno to isc_result:= 6: Device not configured Jan 24 12:18:12 gateway named[1455]: /usr/src/lib/bind/isc/../../../contrib= /bind9/lib/isc/unix/socket.c:1567: unexpected error: Jan 24 12:18:12 gateway named[1455]: internal_send: 192.112.36.4#53: Device= not configured Jan 24 12:18:12 gateway named[1455]: /usr/src/lib/bind/isc/../../../contrib= /bind9/lib/isc/unix/errno2result.c:111: unexpected error: Jan 24 12:18:12 gateway named[1455]: unable to convert errno to isc_result:= 6: Device not configured Jan 24 12:18:12 gateway named[1455]: /usr/src/lib/bind/isc/../../../contrib= /bind9/lib/isc/unix/socket.c:1567: unexpected error: Jan 24 12:18:12 gateway named[1455]: internal_send: 192.112.36.4#53: Device= not configured Jan 24 12:18:12 gateway named[1455]: /usr/src/lib/bind/isc/../../../contrib= /bind9/lib/isc/unix/errno2result.c:111: unexpected error: Jan 24 12:18:12 gateway named[1455]: unable to convert errno to isc_result:= 6: Device not configured Jan 24 12:18:12 gateway named[1455]: /usr/src/lib/bind/isc/../../../contrib= /bind9/lib/isc/unix/socket.c:1567: unexpected error: Jan 24 12:18:12 gateway named[1455]: internal_send: 193.0.14.129#53: Device= not configured Jan 24 12:18:12 gateway named[1455]: /usr/src/lib/bind/isc/../../../contrib= /bind9/lib/isc/unix/errno2result.c:111: unexpected error: Jan 24 12:18:12 gateway named[1455]: unable to convert errno to isc_result:= 6: Device not configured IP addresses are RANDOM and DIFFERENT on every restart. These IP addresses are not mentioned in ANY config file on my computer, and addresses on my network interfaces IS NOT from these networks. Main problem is, that mount_nfs failed on startup on this router because bind is not ready due to these errors and all system goes to single-user mode :( Computer is Soekris net5501, with 6 network interfaces (vr0-vr3 on board, em0 and ath0 attached). Only vr0 and vr1 are used, but adding fake addresses to vr2 and vr3 doesn't help at all. Also, mpd5 creates two NG interfaces (ng0 and ng1) on startup to connect t= o two providers. But previous installation (on faster hardware) doesn't show these errors at all! --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-stable@FreeBSD.ORG Sat Jan 24 11:00: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 6B650106564A for ; Sat, 24 Jan 2009 11:00:27 +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 8757F8FC17 for ; Sat, 24 Jan 2009 11:00:26 +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 NAA22058 for ; Sat, 24 Jan 2009 13:00:24 +0200 (EET) (envelope-from avg@icyb.net.ua) Message-ID: <497AF4C7.3080309@icyb.net.ua> Date: Sat, 24 Jan 2009 13:00:23 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.18 (X11/20081124) MIME-Version: 1.0 To: FreeBSD Stable Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: panic in callout_reset: bad link in callwheel X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jan 2009 11:00:27 -0000 System: FreeBSD 7.1-STABLE i386 (revision 187025) Panic message: kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode fault virtual address = 0xd2006ad0 fault code = supervisor write, page not present instruction pointer = 0x20:0xc05623aa stack pointer = 0x28:0xdd4f6c34 frame pointer = 0x28:0xdd4f6c40 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 current process = 13 (swi4: clock) trap number = 12 panic: page fault KDB: stack backtrace: db_trace_self_wrapper(c074bb2f,dd4f6b14,c05514af,c0749d10,c07b85e0,...) at 0xc0478466 = db_trace_self_wrapper+0x26 kdb_backtrace(c0749d10,c07b85e0,c073b02b,dd4f6b20,dd4f6b20,...) at 0xc057a639 = kdb_backtrace+0x29 panic(c073b02b,c0761cb4,c36104dc,1,1,...) at 0xc05514af = panic+0xaf trap_fatal(c0761bb6,c,c3a89460,c3a8965c,c,...) at 0xc0705723 = trap_fatal+0x353 trap(dd4f6bf4) at 0xc07060ca = trap+0x10a calltrap() at 0xc06f463b = calltrap+0x6 --- trap 0xc, eip = 0xc05623aa, esp = 0xdd4f6c34, ebp = 0xdd4f6c40 --- callout_reset(c3a8552c,13,c0561940,c3a852b8,c3612690,...) at 0xc05623aa = callout_reset+0x14a realitexpire(c3a852b8,2d6100,c3612690,1,dd4f6cbc,...) at 0xc0561ab6 = realitexpire+0x176 softclock(0,0,c0747617,4a1,0,...) at 0xc0562c25 = softclock+0x235 ithread_loop(c35e5a20,dd4f6d38,0,0,0,...) at 0xc053268b = ithread_loop+0x1cb fork_exit(c05324c0,c35e5a20,dd4f6d38) at 0xc052eda1 = fork_exit+0xa1 fork_trampoline() at 0xc06f46b0 = fork_trampoline+0x8 --- trap 0, eip = 0, esp = 0xdd4f6d70, ebp = 0 --- Some debugging: (kgdb) bt #0 doadump () at pcpu.h:196 #1 0xc05512b3 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418 #2 0xc05514ff in panic (fmt=Variable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:574 #3 0xc0705723 in trap_fatal (frame=0xdd4f6bf4, eva=3523242704) at /usr/src/sys/i386/i386/trap.c:939 #4 0xc07060ca in trap (frame=0xdd4f6bf4) at /usr/src/sys/i386/i386/trap.c:320 #5 0xc06f463b in calltrap () at /usr/src/sys/i386/i386/exception.s:159 #6 0xc05623aa in callout_reset (c=0xc3a8552c, to_ticks=19, ftn=0xc0561940 , arg=0xc3a852b8) at /usr/src/sys/kern/kern_timeout.c:471 #7 0xc0561ab6 in realitexpire (arg=0xc3a852b8) at /usr/src/sys/kern/kern_time.c:684 #8 0xc0562c25 in softclock (dummy=0x0) at /usr/src/sys/kern/kern_timeout.c:274 #9 0xc053268b in ithread_loop (arg=0xc35e5a20) at /usr/src/sys/kern/kern_intr.c:1088 #10 0xc052eda1 in fork_exit (callout=0xc05324c0 , arg=0xc35e5a20, frame=0xdd4f6d38) at /usr/src/sys/kern/kern_fork.c:804 #11 0xc06f46b0 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:264 (kgdb) fr 6 #6 0xc05623aa in callout_reset (c=0xc3a8552c, to_ticks=19, ftn=0xc0561940 , arg=0xc3a852b8) at /usr/src/sys/kern/kern_timeout.c:471 471 /usr/src/sys/kern/kern_timeout.c: No such file or directory. in /usr/src/sys/kern/kern_timeout.c (kgdb) p *c $1 = {c_links = {sle = {sle_next = 0x0}, tqe = {tqe_next = 0x0, tqe_prev = 0xd2006ad0}}, c_time = 2974104, c_arg = 0xc3a852b8, c_func = 0xc0561940 , c_mtx = 0x0, c_flags = 22} (kgdb) p c->c_links.tqe.tqe_prev $2 = (struct callout **) 0xd2006ad0 (kgdb) p *c->c_links.tqe.tqe_prev Cannot access memory at address 0xd2006ad0 (kgdb) p callwheel[c->c_time & callwheelmask] $4 = {tqh_first = 0x0, tqh_last = 0xd2006ad0} The code: 467 c->c_arg = arg; 468 c->c_flags |= (CALLOUT_ACTIVE | CALLOUT_PENDING); 469 c->c_func = ftn; 470 c->c_time = ticks + to_ticks; 471 TAILQ_INSERT_TAIL(&callwheel[c->c_time & callwheelmask], 472 c, c_links.tqe); Additional info: I recently added some new memory to this system. The memory survived several passes of memtest86 before booting to FreeBSD. It also survived one pass after the incident. Still I wouldn't exclude a possibility of it being bad. Small analysis: If this is not because of bad memory, then it probably means that a struct callout was earlier deallocated somewhere (possibly as a part of a bigger object), but not unregistered/removed from callout mechanism. I guess it is quite hard to backtrack that now. All I can say that was nothing "funny" happening on the machine from the point of view of attaching/detaching any HW or loading/unloading modules or anything like that. Just "normal" work. So it could be something that it is always "on", like network stack or ata subsystem, etc. -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Sat Jan 24 11:29: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 EEF5C1065686; Sat, 24 Jan 2009 11:29:22 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from ftp.translate.ru (ftp.translate.ru [195.131.4.140]) by mx1.freebsd.org (Postfix) with ESMTP id A32928FC2C; Sat, 24 Jan 2009 11:29:22 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from desktop.home.serebryakov.spb.ru (blacklion.dialup.corbina.ru [89.179.122.169]) (Authenticated sender: lev@serebryakov.spb.ru) by ftp.translate.ru (Postfix) with ESMTPA id 7D4CB13DF62; Sat, 24 Jan 2009 14:29:21 +0300 (MSK) Date: Sat, 24 Jan 2009 14:29:20 +0300 From: Lev Serebryakov Organization: FreeBSD X-Priority: 3 (Normal) Message-ID: <873658171.20090124142920@serebryakov.spb.ru> To: freebsd-stable@freebsd.org, freebsd-net@freebsd.org In-Reply-To: <11410349378.20090124133733@serebryakov.spb.ru> References: <11410349378.20090124133733@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Cc: Subject: Re: BIND 9.4.3-P1: internal_send: 199.7.83.42#53: Device not configured, where 199.7.83.42 is RANDOM IP address X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lev@FreeBSD.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jan 2009 11:29:26 -0000 Hello, Lev. You wrote 24 =FF=ED=E2=E0=F0=FF 2009 =E3., 13:37:33: > IP addresses are RANDOM and DIFFERENT on every restart. These IP > addresses are not mentioned in ANY config file on my computer, and > addresses on my network interfaces IS NOT from these networks. Ok, I'm stupid, it is root servers. Ok. But this knowledge doesn't help to fix problem :( > Main problem is, that mount_nfs failed on startup on this router > because bind is not ready due to these errors and all system goes to > single-user mode :( --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-stable@FreeBSD.ORG Sat Jan 24 12:23: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 4E9F6106564A; Sat, 24 Jan 2009 12:23:52 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id 98F828FC0A; Sat, 24 Jan 2009 12:23:51 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.localnet (ppp121-45-116-6.lns11.adl6.internode.on.net [121.45.116.6]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id n0OCAaEk030376 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 24 Jan 2009 22:40:36 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-stable@freebsd.org, lev@freebsd.org Date: Sat, 24 Jan 2009 22:40:24 +1030 User-Agent: KMail/1.10.3 (Linux/2.6.27-9-generic; KDE/4.1.3; i686; ; ) References: <11410349378.20090124133733@serebryakov.spb.ru> In-Reply-To: <11410349378.20090124133733@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2050353.xrCLn9l8h4"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200901242240.33321.doconnor@gsoft.com.au> X-Spam-Score: -2.212 () BAYES_00,RDNS_DYNAMIC X-Scanned-By: MIMEDefang 2.63 on 203.31.81.10 Cc: freebsd-net@freebsd.org Subject: Re: BIND 9.4.3-P1: internal_send: 199.7.83.42#53: Device not configured, where 199.7.83.42 is RANDOM IP address X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jan 2009 12:23:52 -0000 --nextPart2050353.xrCLn9l8h4 Content-Type: text/plain; charset="windows-1251" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Saturday 24 January 2009 21:07:33 Lev Serebryakov wrote: > BIND on my new router (7.1-STABLE, BIND 9.4.3-P1) shows bunch of > errors on every start and doesn't answer on requests for 30-60 seconds > after that. Errors are like this: > > Jan 24 12:18:12 gateway named[1455]: > /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/socket.c:1567: > unexpected error: Jan 24 12:18:12 gateway named[1455]: internal_send: > 193.0.14.129#53: Device not configured Jan 24 12:18:12 gateway named[1455= ]: > /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/errno2result.c:= 11 >1: unexpected error: Jan 24 12:18:12 gateway named[1455]: unable to convert > errno to isc_result: 6: Device not configured Jan 24 12:18:12 gateway =2E.. > > Also, mpd5 creates two NG interfaces (ng0 and ng1) on startup to connect > to two providers. > > But previous installation (on faster hardware) doesn't show these > errors at all! I think this is an mpd problem - I had the same issue and I couldn't find a= =20 solution. In the end I switched to userland PPP (which has an issue with PF= =20 but you can work around that). =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart2050353.xrCLn9l8h4 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 (GNU/Linux) iD8DBQBJewUx5ZPcIHs/zowRAo+mAJ4468aSWWSyRrnTdG3BHLYFs7A9RACfcf7c 8wZpdE7Wa4Tvj+QkyPSNRVw= =Rdtk -----END PGP SIGNATURE----- --nextPart2050353.xrCLn9l8h4-- From owner-freebsd-stable@FreeBSD.ORG Sat Jan 24 13:17: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 DC3E7106566C for ; Sat, 24 Jan 2009 13:17:58 +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 50C1F8FC1F for ; Sat, 24 Jan 2009 13:17:58 +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 AFD3684CE05A; Sat, 24 Jan 2009 07:17:56 -0600 (CST) Received: from localhost (morganw@localhost [127.0.0.1]) by volatile.chemikals.org (8.14.3/8.14.3) with ESMTP id n0ODHn8R072581; Sat, 24 Jan 2009 07:17:50 -0600 (CST) (envelope-from morganw@chemikals.org) Date: Sat, 24 Jan 2009 07:17:49 -0600 (CST) From: Wes Morgan To: David Ehrmann In-Reply-To: <6e0e5340901240026o39eb4554u6d8eb8c00ee2adbb@mail.gmail.com> Message-ID: References: <6e0e5340901151158n5108ba8ct6af8fb270b10b75b@mail.gmail.com> <6e0e5340901161521t30845197s9529fb5a55dbba13@mail.gmail.com> <6e0e5340901221324o33f1e2b1l53c842ebf9dad9a8@mail.gmail.com> <6e0e5340901240026o39eb4554u6d8eb8c00ee2adbb@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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jan 2009 13:17:59 -0000 On Sat, 24 Jan 2009, David Ehrmann wrote: > On Thu, Jan 22, 2009 at 8:07 PM, Wes Morgan wrote: >> On Thu, 22 Jan 2009, David Ehrmann wrote: >> >>> On Fri, Jan 16, 2009 at 3:21 PM, David Ehrmann wrote: >>> >>> In the /dev/ad8.eli that zfs doesn't recognize, I found a 16 byte >>> string that was repeated a lot, but it was also repeated in another >>> place: the good /dev/ad10.eli (though the offsets were different). >>> The other weird thing: the good and bad /dev/ad8.eli look a lot alike: >>> one 16 byte string, then another that gets repeated, then another 16 >>> byte string randomly shows up at 0x200. >> >> The "xxx.eli" devices are the decrypted versions, aren't they? ZFS vdev >> labels and uberblocks occupy the first 512k of the device, and consist of >> virtually identical data, differing only by the GUID that the label claims >> to be and a sha256 checksum... So, decrypted, they should all be very, very >> similar. You could actually use the label from any device in a pool to >> reconstruct the label for any other device. > > Let me clarify one thing: when zfs has problems reading the device, > the data resemble the data when it's read fine, but by resemble, I > don't mean values as much as structure. The values are all wrong, but > if you overlaid hexdumps, both share repeated patterns. That makes me > think it's an encryption problem, but I haven't been able to reproduce > it with other configurations. You might try creating the pool, saving the first 512k of each block device to a file, then export the pool and repeat, then import (or try to). Run zdb on each file and compare the output. From creation to export to import they should only differ by the "state" in the top level of the label nvlist. If the entire label is corrupted, then likely it's a crypto problem. Although, it really sounds like you've been able to eliminate zfs as a culprit. From owner-freebsd-stable@FreeBSD.ORG Sat Jan 24 13:24:11 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 655D0106568A; Sat, 24 Jan 2009 13:24:11 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from ftp.translate.ru (ftp.translate.ru [195.131.4.140]) by mx1.freebsd.org (Postfix) with ESMTP id 17D248FC18; Sat, 24 Jan 2009 13:24:10 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from desktop.home.serebryakov.spb.ru (blacklion.dialup.corbina.ru [89.179.122.169]) (Authenticated sender: lev@serebryakov.spb.ru) by ftp.translate.ru (Postfix) with ESMTPA id F3DD213DF6E; Sat, 24 Jan 2009 16:24:09 +0300 (MSK) Date: Sat, 24 Jan 2009 16:24:08 +0300 From: Lev Serebryakov Organization: FreeBSD Project X-Priority: 3 (Normal) Message-ID: <1708297021.20090124162408@serebryakov.spb.ru> To: "Daniel O'Connor" In-Reply-To: <200901242240.33321.doconnor@gsoft.com.au> References: <11410349378.20090124133733@serebryakov.spb.ru> <200901242240.33321.doconnor@gsoft.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Cc: freebsd-net@freebsd.org, lev@freebsd.org, freebsd-stable@freebsd.org Subject: Re[2]: BIND 9.4.3-P1: internal_send: 199.7.83.42#53: Device not configured, where 199.7.83.42 is RANDOM IP address X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lev@FreeBSD.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jan 2009 13:24:11 -0000 Hello, Daniel. You wrote 24 =FF=ED=E2=E0=F0=FF 2009 =E3., 15:10:24: >> Also, mpd5 creates two NG interfaces (ng0 and ng1) on startup to connect >> to two providers. >> >> But previous installation (on faster hardware) doesn't show these >> errors at all! > I think this is an mpd problem - I had the same issue and I couldn't find= a > solution. In the end I switched to userland PPP (which has an issue with = PF > but you can work around that). userland ppp doesn't support l2tp :( --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-stable@FreeBSD.ORG Sat Jan 24 13:54: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 9AA3910656DC for ; Sat, 24 Jan 2009 13:54:08 +0000 (UTC) (envelope-from hg@queue.to) Received: from pickle.queue.to (pickle.queue.to [71.180.69.18]) by mx1.freebsd.org (Postfix) with ESMTP id 3DCFE8FC19 for ; Sat, 24 Jan 2009 13:54:08 +0000 (UTC) (envelope-from hg@queue.to) Received: (qmail 57717 invoked from network); 24 Jan 2009 08:27:26 -0500 Received: from cally.queue.to (172.16.0.6) by with ESMTP; 24 Jan 2009 08:27:26 -0500 Message-ID: <497B173D.9090103@queue.to> Date: Sat, 24 Jan 2009 08:27:25 -0500 From: Howard Goldstein User-Agent: Thunderbird 2.0.0.19 (X11/20090117) MIME-Version: 1.0 To: freebsd-stable@freebsd.org, bms@incunabulum.net References: <200901232244.n0NMiRmM098646@lurza.secnetix.de> In-Reply-To: <200901232244.n0NMiRmM098646@lurza.secnetix.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Oliver Fromme Subject: Re: A nasty ataraid experience. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jan 2009 13:54:08 -0000 Oliver Fromme wrote: > Bruce M Simpson wrote: > > [...] > > I also now understand that I can't rely on RAID alone to keep the > > integrity of my own data -- there is no substitute for backups, > > That's 100% true. RAID -- even true hardware RAID -- is > *never* a substitute for backup. Consider: > - Fire. > - Theft. > - Lightning strike or power surge. > - The cleaning woman knocks the tower over. > - ... > In all of those cases, chances are that both disks in the > RAID mirror die. Also, as you mentioned, it doesn't > protect agains human errors ("rm *" in the wrong directory > and similar things). > > Backups should always be made to media that can be taken > offline and stored in a safe place: Tape, optical disks, > hard disks in swappable drive trays, or external drives. > Messr. Fromme's point _can never_ be restated too often: Offline and offsite. Pick your religion: dump, rsync, bacula, amanda, whatever, just stick with it. (To the list I would add: - Fancy new well known manuf's ATX power supply received from a reputable reseller. Unwrapped from factory package, installed and the RAID array discovered the 12v and 5v rails were swapped internally at the factory and there went all of the magic smoke.) From owner-freebsd-stable@FreeBSD.ORG Sat Jan 24 15:22: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 BF9D8106566C for ; Sat, 24 Jan 2009 15:22:34 +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 EF8C98FC0C for ; Sat, 24 Jan 2009 15:22:33 +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 RAA25146 for ; Sat, 24 Jan 2009 17:22:31 +0200 (EET) (envelope-from avg@icyb.net.ua) Message-ID: <497B3237.4000708@icyb.net.ua> Date: Sat, 24 Jan 2009 17:22:31 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.19 (X11/20090110) MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Subject: panic in destroy_devl: null si_devsw X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jan 2009 15:22:35 -0000 System: FreeBSD 7.1-PRERELEASE amd64 somewhere from the beginning of Decemeber I am not sure how I managed to get to this panic - I believe my code is correct - but I got a panic in destroy_devl on NULL si_devsw. Backtrace: --- trap 0xc, rip = 0xffffffff80271c3f, rsp = 0xffffffffdb3e8510, rbp = 0xffffffffdb3e8550 --- destroy_devl() at 0xffffffff80271c3f = destroy_devl+0x316 destroy_dev() at 0xffffffff80271e2c = destroy_dev+0x19 heci_deallocate_resources() at 0xffffffffdb63e0e6 = heci_deallocate_resources+0x20 heci_detach() at 0xffffffffdb63e183 = heci_detach+0x11 heci_pci_attach() at 0xffffffffdb63f921 = heci_pci_attach+0x123 device_attach() at 0xffffffff802caa21 = device_attach+0x327 device_probe_and_attach() at 0xffffffff802cb8ef = device_probe_and_attach+0xe2 pci_driver_added() at 0xffffffff80212e82 = pci_driver_added+0xf9 devclass_add_driver() at 0xffffffff802c98fa = devclass_add_driver+0xd7 driver_module_handler() at 0xffffffff802ca641 = driver_module_handler+0x74 module_register_init() at 0xffffffff8029901d = module_register_init+0xf7 linker_load_module() at 0xffffffff80292582 = linker_load_module+0xa01 kern_kldload() at 0xffffffff80292aa2 = kern_kldload+0xd4 kldload() at 0xffffffff80292b66 = kldload+0x61 syscall() at 0xffffffff8043d58d = syscall+0x347 Xfast_syscall() at 0xffffffff80423a5b = Xfast_syscall+0xab --- syscall (304, FreeBSD ELF64, kldload), rip = 0x80067ff3c, rsp = 0x7fffffffe5b8, rbp = 0 --- Debug: (kgdb) fr 7 #7 0xffffffff80271c3f in destroy_devl (dev=0xffffff0075d45800) at /usr/src/sys/kern/kern_conf.c:906 906 if (LIST_EMPTY(&csw->d_devs)) { (kgdb) list 901 if (!(dev->si_flags & SI_ALIAS)) { 902 /* Remove from cdevsw list */ 903 LIST_REMOVE(dev, si_list); 904 905 /* If cdevsw has no more struct cdev *'s, clean it */ 906 if (LIST_EMPTY(&csw->d_devs)) { 907 fini_cdevsw(csw); 908 wakeup(&csw->d_devs); 909 } 910 } (kgdb) p csw $1 = (struct cdevsw *) 0x0 Perhaps I screwed up something myself, but here is a question - why do we have a check for NULL csw here: 873 csw = dev->si_devsw; 874 dev->si_devsw = NULL; /* already NULL for SI_ALIAS */ 875 while (csw != NULL && csw->d_purge != NULL && dev->si_threadcount) { and don't have any check where the panic occurred? About the code that called destroy_dev(): it created cdev probably too early, failed to allocate some system resource, so it went to destroy the newly created cdev. Non-null cdevsw was definitely provided to make_dev. -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Sat Jan 24 16:34: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 C22C6106566B for ; Sat, 24 Jan 2009 16:34:55 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by mx1.freebsd.org (Postfix) with ESMTP id 9900F8FC1F for ; Sat, 24 Jan 2009 16:34:55 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from compute2.internal (compute2.internal [10.202.2.42]) by out1.fastmail.fm (Postfix) with ESMTP id 3583D2569A0; Sat, 24 Jan 2009 11:34:55 -0500 (EST) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute2.internal (MEProxy); Sat, 24 Jan 2009 11:34:55 -0500 X-Sasl-enc: uXwMyrskL4CjoJb+wHAWnxDNGOPyzllHDOMX2dz1xN6s 1232814894 Received: from empiric.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTPSA id 9D8D82E539; Sat, 24 Jan 2009 11:34:54 -0500 (EST) Message-ID: <497B432C.1040802@FreeBSD.org> Date: Sat, 24 Jan 2009 16:34:52 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 2.0.0.19 (X11/20090116) MIME-Version: 1.0 To: Andriy Gapon References: <497B3237.4000708@icyb.net.ua> In-Reply-To: <497B3237.4000708@icyb.net.ua> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@FreeBSD.ORG Subject: Re: panic in destroy_devl: null si_devsw X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jan 2009 16:34:56 -0000 Andriy Gapon wrote: > ... > About the code that called destroy_dev(): it created cdev probably too > early, failed to allocate some system resource, so it went to destroy > the newly created cdev. Non-null cdevsw was definitely provided to make_dev. > > I saw a very, very similar panic with 7.1 sources and jhb's ppc locking patch yesterday. Could this be related to a difference in unit numbers between 8.x and 8.x? From owner-freebsd-stable@FreeBSD.ORG Sat Jan 24 21:15: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 03551106564A for ; Sat, 24 Jan 2009 21:15:39 +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 C313B8FC18 for ; Sat, 24 Jan 2009 21:15:38 +0000 (UTC) (envelope-from ehrmann@gmail.com) Received: from [10.0.0.171] (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 D6DCA23E3F2; Sat, 24 Jan 2009 16:15:34 -0500 (EST) Message-ID: <497B84E5.3090304@gmail.com> Date: Sat, 24 Jan 2009 13:15:17 -0800 From: David Ehrmann User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Wes Morgan References: <6e0e5340901151158n5108ba8ct6af8fb270b10b75b@mail.gmail.com> <6e0e5340901161521t30845197s9529fb5a55dbba13@mail.gmail.com> <6e0e5340901221324o33f1e2b1l53c842ebf9dad9a8@mail.gmail.com> <6e0e5340901240026o39eb4554u6d8eb8c00ee2adbb@mail.gmail.com> In-Reply-To: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jan 2009 21:15:39 -0000 Wes Morgan wrote: > You might try creating the pool, saving the first 512k of each block > device to a file, then export the pool and repeat, then import (or try > to). Run zdb on each file and compare the output. From creation to > export to import they should only differ by the "state" in the top > level of the label nvlist. If the entire label is corrupted, then > likely it's a crypto problem. > > Although, it really sounds like you've been able to eliminate zfs as a > culprit. This is pretty much what I tried. between export, geli detach, and geli attach, zdb -l went from reporting info on the pool to reporting that no labels were found. dd confirmed what zdb was saying, so I have no reason to think zfs is acting up. I just don't get why I haven't been able to reproduce this with another zpool-less disk or two md disks. Maybe the .eli device shows up before it's ready to use and something gets cached by zfs in the background. Maybe it has something to do with me using two disks. A race condition? None of these are really easy things to find. For now, the only two ideas I have are trying zfs on a single disk with this configuration, and trying it on multiple disks, when the RMA is done, with 2 disks. From owner-freebsd-stable@FreeBSD.ORG Sat Jan 24 22:01: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 0E5D0106566B for ; Sat, 24 Jan 2009 22:01:16 +0000 (UTC) (envelope-from sorin.panca@psrk.com) Received: from mail1.psrk.com (64.147.114.45.static.nyinternet.net [64.147.114.45]) by mx1.freebsd.org (Postfix) with ESMTP id DE6BA8FC1C for ; Sat, 24 Jan 2009 22:01:15 +0000 (UTC) (envelope-from sorin.panca@psrk.com) Received: from [93.122.133.67] (port=15617 helo=[192.168.0.11]) by mail1.psrk.com with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from ) id 1LQpwk-0006zK-0n for freebsd-stable@freebsd.org; Sat, 24 Jan 2009 16:21:42 -0500 Message-ID: <497B85DE.1040005@psrk.com> Date: Sat, 24 Jan 2009 23:19:26 +0200 From: Sorin Panca User-Agent: Thunderbird 2.0.0.19 (X11/20090110) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Antivirus-Scanner: Clean mail though you should still use an Antivirus Subject: Installing packages using ports after freebsd-update doesn't work on amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jan 2009 22:01:16 -0000 After upgrading the system using freebsd-update from 6.3-RELEASE to 7.0-RELEASE and after that, from 7.0 to 7.1 trying to install ports-mgmt/portupgrade fails at ruby18 with the following message: cc -shared -Wl,-soname,libruby18.so.18 array.o bignum.o class.o compar.o dir.o dln.o enum.o error.o eval.o file.o gc.o hash.o inits.o io.o marshal.o math.o numeric.o object.o pack.o parse.o process.o prec.o random.o range.o re.o regex.o ruby.o signal.o sprintf.o st.o string.o struct.o time.o util.o variable.o version.o dmyext.o -lcrypt -lm -rpath=/usr/lib:/usr/local/lib -pthread -o libruby18.so.18 /usr/bin/ld: /usr/lib/libpthread.a(thr_syscalls.o): relocation R_X86_64_32S can not be used when making a shared object; recompile with -fPIC /usr/lib/libpthread.a: could not read symbols: Bad value *** Error code 1 I added CFLAGS?= -O2 -fPIC -pipe to /etc/make.conf but the problem persists. I didn't activate pthread support for ruby18. Any ideas on what's going wrong here? Thank you! Sorin. From owner-freebsd-stable@FreeBSD.ORG Sat Jan 24 23:10: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 3A2D610657DB for ; Sat, 24 Jan 2009 23:10:15 +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 D1B7C8FC21 for ; Sat, 24 Jan 2009 23:10:14 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 29962 invoked by uid 399); 24 Jan 2009 23:10:13 -0000 Received: from localhost (HELO ?192.168.0.19?) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 24 Jan 2009 23:10:13 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <497B9FF4.30605@FreeBSD.org> Date: Sat, 24 Jan 2009 15:10:44 -0800 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: lev@FreeBSD.org References: <11410349378.20090124133733@serebryakov.spb.ru> In-Reply-To: <11410349378.20090124133733@serebryakov.spb.ru> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Subject: Re: BIND 9.4.3-P1: internal_send: 199.7.83.42#53: Device not configured, where 199.7.83.42 is RANDOM IP address X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: FreeBSD Stable List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jan 2009 23:10:17 -0000 Lev Serebryakov wrote: > Hello, Freebsd-stable. > > BIND on my new router (7.1-STABLE, BIND 9.4.3-P1) shows bunch of > errors on every start and doesn't answer on requests for 30-60 seconds > after that. Errors are like this: It's not necessary or desirable to paste in so many examples of the same message. It's also not good to cross post the same message to multiple lists. > Jan 24 12:18:12 gateway named[1455]: /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/socket.c:1567: unexpected error: > Jan 24 12:18:12 gateway named[1455]: internal_send: 193.0.14.129#53: Device not configured That message is fairly clear, the system has told named that it can talk to the outside world, but there isn't anything there for named to talk to. As you already pointed out in another message, the IP addresses are for the root name servers. The first thing named does when it starts up is to verify the information in the hints file. > Main problem is, that mount_nfs failed on startup on this router > because bind is not ready due to these errors and all system goes to > single-user mode :( Any time you are using NFS you should maintain the addresses of the critical hosts in /etc/hosts. Yes, I realize that's anachronistic (especially for a DNS guy) but it works. Obviously you should make sure to update them as needed. > Computer is Soekris net5501, with 6 network interfaces (vr0-vr3 on > board, em0 and ath0 attached). Only vr0 and vr1 are used, but adding > fake addresses to vr2 and vr3 doesn't help at all. > > Also, mpd5 creates two NG interfaces (ng0 and ng1) on startup to connect to two > providers. > > But previous installation (on faster hardware) doesn't show these > errors at all! I've never used mpd myself, but you might want to try adding the following line to /usr/local/etc/rc.d/mpd and see if it helps: # BEFORE: named Doug -- This .signature sanitized for your protection From owner-freebsd-stable@FreeBSD.ORG Sat Jan 24 23:12: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 C2E851065764 for ; Sat, 24 Jan 2009 23:12:27 +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 50A368FC30 for ; Sat, 24 Jan 2009 23:12:27 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 32125 invoked by uid 399); 24 Jan 2009 23:12:26 -0000 Received: from localhost (HELO ?192.168.0.19?) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 24 Jan 2009 23:12:26 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <497BA079.6060309@FreeBSD.org> Date: Sat, 24 Jan 2009 15:12:57 -0800 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Sorin Panca References: <497B85DE.1040005@psrk.com> In-Reply-To: <497B85DE.1040005@psrk.com> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: Installing packages using ports after freebsd-update doesn't work on amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jan 2009 23:12:28 -0000 Sorin Panca wrote: > After upgrading the system using freebsd-update from 6.3-RELEASE to > 7.0-RELEASE and after that, from 7.0 to 7.1 trying to install > ports-mgmt/portupgrade fails at ruby18 with the following message: If you haven't already you have to remove and reinstall _all_ of your ports after doing a major version upgrade (6.x -> 7.x). -- This .signature sanitized for your protection